LINK11 results (WB)
LINK11 results (WB)
(OP)
I changed a spring element to link11 actuator element in a command object and defined an axial
force to the actuator.
Spring object:
Environment branch:
Solution branch:
I am getting the following message in the output file. How can I get the force in the actuator?
SELECT FOR ITEM=ENAM COMPONENT=
IN RANGE 11 TO 11 STEP 1
1 ELEMENTS (OF 1623 DEFINED) SELECTED BY ESEL COMMAND.
STORE CYLFORCE FROM ITEM=SMIS COMP= 1 FOR ALL SELECTED ELEMENTS
*** WARNING *** CP = 1.047 TIME= 02:08:22
The requested database is not available. The ETAB command is ignored.
PRINT ELEMENT TABLE ITEMS PER ELEMENT
*** WARNING *** CP = 1.047 TIME= 02:08:22
No element table items are available. The PRETAB command is ignored.
force to the actuator.
Spring object:
CODE --> apdl
actuator = _sid ET,actuator,11 R,actuator,1000,,10 !stiffness 1000, mass 10
Environment branch:
CODE --> apdl
SFE,2431,2,PRES,0,1000 !2431 is the element number, axial force 1000
Solution branch:
CODE --> apdl
ESEL,S,ENAME,,LINK11 ETAB,CYLFORCE,SMISC,1 PRET,CYLFORCE
I am getting the following message in the output file. How can I get the force in the actuator?
SELECT FOR ITEM=ENAM COMPONENT=
IN RANGE 11 TO 11 STEP 1
1 ELEMENTS (OF 1623 DEFINED) SELECTED BY ESEL COMMAND.
STORE CYLFORCE FROM ITEM=SMIS COMP= 1 FOR ALL SELECTED ELEMENTS
*** WARNING *** CP = 1.047 TIME= 02:08:22
The requested database is not available. The ETAB command is ignored.
PRINT ELEMENT TABLE ITEMS PER ELEMENT
*** WARNING *** CP = 1.047 TIME= 02:08:22
No element table items are available. The PRETAB command is ignored.
RE: LINK11 results (WB)
This should work if you put in the solution branch of Mechanical:
CODE --> APDL
RE: LINK11 results (WB)
It seems to be working as expected not taking into account the actuator force table.
Your suggestion seems to be working,thanks!
RE: LINK11 results (WB)
/peter