Also, the solver progress bar doesn't display properly, and solution info folder is always marked as unsolved (both, I guess, b/c solver is tracking progress against a dummy end time: 1000 s). If you defined named selections in Workbench, and would like to re-select these in APDL, use the command: CMSEL,s,YourNamedSelectionHere. However I'm inherently skeptical of this, as the dummy time value persists for a short time in each loadstep, before the snippet is executed, and I can't be sure it's not affecting anything.

that can be parameterised with snippet arguments (dt = ARG1). This overwrites the dummy time value with a new value, based on a timestep, etc. Settime = dt*(nloadstep+1) ! (+1 is needed)Įxecuted at all load steps. I added an LS-DYNA command snippet directly to my line body, but I'm not sure what commands I need to make the edges into link167 elements. I had link180 in the comments by mistake - I need to use link167. This is a pain, and I cannot parameterize any these variables (timestep, etc).Ī clunky workaround I have is to leave an dummy loadstep time vector in analysis settings, e.g. Madeline Subscriber Hello - I realized that I need to use LS-DYNA commands since I'm using an explicit dynamics model. I have to re-edit this, and the substepping options, whenever the timestep, etc. , and insert that into the step control tabular data (Analysis Settings).

The is problem is, to define the load step time data, I have to externally create a vector, e.g. (I'm not using USRCAL as I don't know how). The use of load steps over substeps is so an APDL command snippet can be exectued at each load step to apply the feedback load. Background: So I have a transient structural analysis that uses a large number of load steps (>1000) to simulate a system with load feedback (an aerodynamic model which takes velocities, angles, etc.

Ansys apdl wait command