Jump to content

All Activity

This stream auto-updates     

  1. Today
  2. Hi, I have a problem with optistruct.. There were 4 error messages during input processing. The first message is repeated below: *** See next message about line 4624 from file: C:/Users/kjm96/Desktop/Frame/HW/FRFInal.fem "PWELD 7 1" *** ERROR # 1000 *** in the input data: Incorrect data in field # 4. I did assign all of property and I can't find the error thank you
  3. Yes @Andy, when I reduce yield stress (or increase sheet thickness) the wrinkles disappear, but only in a level that is too far from reality. I believe too that the problem can also be related to element size. The problem is that I can`t reduce it due run time, and I can`t increase it due geometry. Maybe you can help me on an suggestion: My whole simulation path, if displacement were to be imposed in seconds, is taking 591s, what with a timestep of 1e-6 will take 10 days to run (which is kind of a problem here). The problem is if I increase element to a huge size (like 15mm lenght), I can only reduce the time step to I would say 2.5e-6, then it takes 5 days. So, still doesn`t help a lot (and we loose all the precision). Another thing I am noticing, is that even when I don`t use DT/NODA, with zero mass added, I always have 99.9% error. Maybe because my simulation is too long? What can be the reason? Do you think its possible to imposed the displacement in milli seconds? What do you think about the dynamic effects on the Single point incremental forming? I need to find a way to run it faster.... As always, thank you very much for the help.
  4. MOHAMED HAMDALLA

    Crosstalk

    Thank you for your help. Sorry, It is in GHz.
  5. acupro

    AcuSolve Log file issue

    I understand from the support team that you were able to resolve the issue by 'rebuilding' your machine. This was definitely strange behavior...
  6. If your script runs very fast => don't need progress bar If your script runs in a short time => use smoothy updated progress bar, because it's not expensive so make it nice If your script runs in a long time => use periodically updated progress bar, because it's expensive so make it ugly! Ugly is better than none (hm frozen)
  7. Thank you. Is autoclean up the only solution?
  8. Ok tinh, so then I won't put the progress bar... I need to show if the script is running or not, because HyperMesh freezes in a short period of time, so I will put a text showing "running" and it will update when the script finish. Do you think is a good way? Or could be better?
  9. try to use "autoclean up" tool. but you should add mesh parameters which you use for meshing yellow body. you can create this. (i am talking about shell mesh, because autoclean up uses this params) better to use smaller el size parameters than your mesh will be. exmpl if you want 2 mm tetra you should use 1 mm for clean up tool.
  10. Yes, because update cmd will invoke various cmds, it slows down script. So do not make it runs smooth (look beautiful, but expensive!) The progress bar is stuck sometimes because a certain cmd takes much time, If you want it runs smoother, you have to put "update" inside that cmd. If the cmd is a tcl proc, it is possible Otherwise is not.
  11. Mrt

    ERROR : RIGID BODY UNSTABLE

    you can do RB instead rbe+shell because your rbe+shell=rigid body=)
  12. Hello, I have two solids which are in contact (Figures 1, 2 & 3). Correct me if I'm wrong, but my understanding is to use theboolean operations in solid edit [{A-B,B} (cut A with B method)] to get a common surface so that the two meshes have matching nodes at the end of the workflow. One problem I find with this method is that even if I toggle off some edges they appear again after a boleean operation. Another problem is the boundary edges (Figure 4) of the common surface between the two objects in contact are sharp and the mesh generated will be bad. Is there a way to solve this or altogether a different method please? Model is attached (Hypermesh 2017) Thank you for your help. sent.hm
  13. rea2

    ERROR : RIGID BODY UNSTABLE

    Thank you for your effort! However, I need to keep the rigid body, I cannot solve the problem by just removing it. Anyone else? I keep getting this error message from time to time, but unfortunately cannot identify the problem.
  14. Thank you very much the answers guys. Yes @Ivan, that was exactly my doubt. Now I understand it, its good to know that I can use small elements attached to Rbody without increasing running time. And also, very useful information about the relation between stiffness and contact, I wasn't aware of that. About adding mass to the Rbody, if I am using impdisp on this specific Rbody the whole time, does the mass on it affect time step too? I mean, the inertia effect are controlled by my impdisp, right?
  15. Hi tinh, "body" would correspond with the old script I mentioned before. There a lot of loops, and nested loops. I added update cmd like you said, and now I can see that the progress bar is working, but I can notice sometimes it get stuck. I wonder if there is a way to resolve this... Another question, update command makes the script runs slower? Thanks you tinh
  16. Hi Meerten As far as I know, you cannot call a function that uses POSTFEKO commands directly from within a CADFEKO script like in your example. The commands will be executed in CADFEKO at that point and "pf", the POSTFEKO namespace would not be available (see the User Manual chapter "Scripts and Application Programming Interface (API)" or Example Guide I1 "Introduction to Application Automation" for more information). You would have to use a command in the CADFEKO script that opens POSTFEKO with the post-processing script that you wish to execute. You could try something like the following: cf.Launcher.Run("postfeko", {"modelname.fek", "--run-script", "createAndExportGraph.lua", "--non-interactive"}) You can run POSTFEKO in non-interactive mode, or you can leave out the last command if you wish to see the execution of commands or interact with POSTFEKO as the commands are being executed. You can close POSTFEKO in the post-processing script by using app:Close(). Here is a very simple example where CADFEKO is only used to run POSTFEKO to export a graph image: runPostfekoScriptFromCadfeko.lua (main CADFEKO script) createAndExportGraph.lua (script that gets executed in POSTFEKO when running the main CADFEKO script) As to sending parameters from CADFEKO to POSTFEKO, I'm not sure about the most elegant way to do this. One option would be to write/read the parameters to/from a (text) file using standard Lua commands. Hope this helps. Kind regards Madelé
  17. What is body of main proc? Add update cmd into every loop of it
  18. Prakash Pagadala

    I need to run solver manager

    https://forum.altair.com/topic/28370-unable-to-save-the-model-nor-the-session/?tab=comments#comment-72924
  19. Prakash Pagadala

    I need to run solver manager

    Can you change the working directory and try again?
  20. Farper

    I need to run solver manager

    The simple way to show my problem is the tutorial : OS-3300: Using the Lattice Optimization Process in OptiStruct
  21. Farper

    I need to run solver manager

    And also when I use the optimization option and check the lattice box and entering the numbers there is an error for running the optistruct which says no permission.
  22. Farper

    I need to run solver manager

    My thesis is about lattice structures so I need to apply the lattice properties either in the optimization section of the software or using the command window.
  23. Prakash Pagadala

    I need to run solver manager

    Why do you need a command window? Go to Analysis page after setting up all the analysis>> hit OptiStruct to start analysis!!!
  24. Farper

    I need to run solver manager

    Thank you for your quick response. the version is 2017.2
  25. Hi all, I am trying to create my first GUI for an old script I did, and I don't know if I am doing in the best way. The GUI has a progress bar indeterminate (in the future I would want to do determinate), which should start when the user press a button and should stop when the script finish. However, when the script is running, GUI freezes and progress bar doesn't update. I have the GUI and the script in two different procedures, like this (only the relevant info is showed, but I can show the whole script): proc interface {} { # ------------------------------------------------------------------------------------------------ # set progress_frame [hwtk::labelframe $gui.progress_frame -text "Progress" -padding 5] pack $progress_frame -padx 1 -pady 3 -anchor n -fill x -side top set progress [hwtk::progressbar $progress_frame.progress -mode indeterminate -length 350] pack $progress # ------------------------------------------------------------------------------------------------ # set button_start [hwtk::button $bottom_frame.button_start -text "BURN IT!" -width 10 -command [list BarCommand start $progress_frame.progress]] pack $button_start -pady 1 -padx 3 -anchor e -side right -ipadx 4 -ipady 2 } proc BarCommand {op args} { foreach w $args { $w $op } update main } proc main {} { # A lot of commands here } I have only found two topics related with problem: Unfreeze the HyperMesh GUI (I added command "update" in the proc) Progress bar / status bar creation inside HM But the GUI is still not working. I add command "update" in the proc which is changing the progress bar, but it doesn't work. The GUI is like the one I show in the image below. I think I am missing something but I don't know what... Thanks in advance, Alex
  26. MarcoPoliTO

    Problem during FEA analysis

    Perfect, thanks.
  1. Load more activity
×