🎉Community Raffle - Win $25

An exclusive raffle opportunity for active members like you! Complete your profile, answer questions and get your first accepted badge to enter the raffle.
Join and Win

I have a '.bat' file for automesh and boundary creation. When I execute the file with 'hm.exe' path, it works. But when I execute it with 'runhw.exe' path it does not work. Could you please help me with it?

User: "Mahesh Gutte"
Altair Community Member
Updated by Mahesh Gutte

Find more posts tagged with

Sort by:
1 - 7 of 71
    User: "Michael Herve"
    Altair Employee
    Updated by Michael Herve

    hello,

     

    do you get any specific error message? What is the command you try to execute?

     

    Best Regards,

    Michael

    User: "Mahesh Gutte"
    Altair Community Member
    OP
    Updated by Mahesh Gutte

    Hello,

    thank you for your reply!

    I do not get any error. When I execute the '.bat'-file when defined the 'runhw.exe' path, it opens the hyperworks programm with blank screens. But when I execute the same file defining 'hm.exe' path it works.

     

    The batch file is for creating,

    1) surfaces for a geometry 

    2) 2d-Mesh creation with defined mesh parameters,

    3) Boundary recognition for the geometry.

     

     

    User: "Mahesh Gutte"
    Altair Community Member
    OP
    Updated by Mahesh Gutte

    One more point,

     

    this batch file takes '.iges' file and converts it to .hm for abaqus solver. 

    Best Reagrds,

    Mahesh

    User: "Michael Herve"
    Altair Employee
    Updated by Michael Herve

    May I ask you for the exact command you used with runhw.exe?


    Regards,

    Michael

    User: "Mahesh Gutte"
    Altair Community Member
    OP
    Updated by Mahesh Gutte

    May I ask you for the exact command you used with runhw.exe?


    Regards,

    Michael

    Set CAD_INPUT=xxx.igs

    Set CAD_OUTPUT=%JOBID%_CAD%CAD_PROCESS%.hm

     

    call %File_name_EXE% %filename% %CAD_OUTPUT% %OUTPUT_MESH% %MCATE% %MESHPARA% %MAT% %File_name_PARA% NULL %ASSY_PROCESS% %NEW_MATFILE%
    echo %ERRORLEVEL%

    call %DIRECTORY%capture.bat 

    Under capture.bat 

    setlocal
    Set ALM_NO_EXPIRE_WARNING=1
    "File_path/runhw.exe" /clientconfig hwfepre.dat -nocommand -nouserprofiledialog -tcl "boundary_capture.tcl" -s1280x1024+10+10
    endlocal

     

    I hope this helps.

    User: "Michael Herve"
    Altair Employee
    Updated by Michael Herve

    Hello,

     

    generally, I define the tcl script by a path (either absolute or reltive):

    "File_path/runhw.exe" /clientconfig hwfepre.dat -nocommand -nouserprofiledialog -tcl "boundary_capture.tcl" -s1280x1024+10+10

     

    Plus, some arguments seem not to be related to runhwx.eexe (which is the new interface).. The command for runhwx.exe should look like below:

    "D:\Program Files\Altair\2022\hwdesktop\hwx\bin\win64\runhwx.exe" -client HyperWorksDesktop -plugin HyperworksLauncher -profile HyperworksLauncher -l en -sf plugins/hwd/resources/splashHyperWorks.png

     

    Best Regards,

    Michael

     

    User: "Mahesh Gutte"
    Altair Community Member
    OP
    Updated by Mahesh Gutte

    Hello,

     

    generally, I define the tcl script by a path (either absolute or reltive):

    "File_path/runhw.exe" /clientconfig hwfepre.dat -nocommand -nouserprofiledialog -tcl "boundary_capture.tcl" -s1280x1024+10+10

     

    Plus, some arguments seem not to be related to runhwx.eexe (which is the new interface).. The command for runhwx.exe should look like below:

    "D:\Program Files\Altair\2022\hwdesktop\hwx\bin\win64\runhwx.exe" -client HyperWorksDesktop -plugin HyperworksLauncher -profile HyperworksLauncher -l en -sf plugins/hwd/resources/splashHyperWorks.png

     

    Best Regards,

    Michael

     

    Hello,

    Thank you so much for your reply. I will try to edit the scripts accordingly.

    Best Regards,

    Mahesh