Cable: assembling case incorrect ?

Cable: assembling case incorrect ?

benoit.thiry
Contributor Contributor
772 Views
9 Replies
Message 1 of 10

Cable: assembling case incorrect ?

benoit.thiry
Contributor
Contributor

Hello,

I used the FO field of a calbe to define the initial tension in the cable.
The software obviously does not consider the force F0 as an initial tension in the cable but as the projection of the final
load in the cable projected on the undeformed position of the cable.
my model is pretty simple: 14m horizontal cable. section 1.33cm2, E=1886 MPa.
the cable support a vertical distributed load of 0.26kN/m.
introducing F0 = 2.5kN Robot computes
deflection = 259.8cm, F in cable= -3.09kN , reactions: Fhorizontal = 2.5kN, Fvertical=1.82kN   ??????

introducing F0 =0kN Robot computes
deflection = 125.5cm, F in cable= -5.48kN , reactions: Fhorizontal = 2.5kN, Fvertical=1.82kN
now introducing the initial tension via a thermal shrink of the cable
deflection = 105.5cm, F in cable= -6.42kN , reactions: Fhorizontal = 6.16kN, Fvertical=1.82kN
which is the correct value.
I believe there is a problem with the assembling case !!!

Many thanks in advance, to check / advise !

Benoît







 

0 Likes
Accepted solutions (1)
773 Views
9 Replies
Replies (9)
Message 2 of 10

Krzysztof_Wasik
Autodesk Support
Autodesk Support

Hi @benoit.thiry

Have you used Large Displacement calculation method. It is recommended for cables

Krzysztof_Wasik_0-1666634030038.png

 

 



Krzysztof Wasik
0 Likes
Message 3 of 10

benoit.thiry
Contributor
Contributor

Hello,
I tried both options, results are the same.
The problem is not related to convergence.
My understanding (I might be wrong) of what Robot calls assembling case is:
it represent the state of the cable when it is initially installed. Either an initial
tension force is applied or an initial shrink.
after that the cable will support the loads or structure it is designed for and this will somehow
increase( or decrease..) the tension in the cable and create extra cable sagging.


the issue is that when I specify an initial force to the cable
ROBOT solves for a case where the inward pull of the said cable matches the initial tension, whatever external loads are applied to the cable...  while actually one expects the tension in the cable to increase when suspended loads are applied to the cable.

introducing  F0=2.5kN to the cable ROBOT computes deflection as 259.8cm !!!
introducing  F0=0.0kN to the cable ROBOT computes deflection as 125.5cm!!! ???
(Robot models attached)


-> initial tension increases the deflection ?????
with initial tension F0=0.0kN

benoitthiry_0-1666683580599.png
with initial tension F0=2.5kN

benoitthiry_1-1666683637018.png
Now defining initial tension via a temperature case, correct behavior is observed

benoitthiry_2-1666683900741.png

 

questions:

what is the actual meaning of the assembling case?
can we define several independent load cases in a model containing cables. It seems that the load cases are additive?
Apparently deleting one load case in a cable model deletes the cable elements ?

many thanks in advance  for your help,

Benoît




 

 

 

0 Likes
Message 4 of 10

Krzysztof_Wasik
Autodesk Support
Autodesk Support

Hi @benoit.thiry 

Share your model



Krzysztof Wasik
0 Likes
Message 5 of 10

benoit.thiry
Contributor
Contributor

it is in the zip file attached to previous message

 

0 Likes
Message 6 of 10

benoit.thiry
Contributor
Contributor

did you find it ?
here it is again.

Benoît

0 Likes
Message 7 of 10

Krzysztof_Wasik
Autodesk Support
Autodesk Support

Hi @benoit.thiry 

Defie assembly conditions (initial force ,or enlogation) in the first load case. It is regarded as assembly load case and determines structure stiffness (usually self weight may be included in that case). If you need to consider only prestressing forces in assembly case leave it empty- (with no loads defined in load table) 

All other load cases: wind, live etc should be defined in next, separate load cases.

 

While analysis program applies prestressing conditions to first load cases (assembly) which determines structure stiffness. All next load cases are applied on prestresses model. When load cases are calculated assembly load case is always regarded (in behind)

Results for wind = wind load + assembly case

Results for live= live load + assembly case.

 

 

In case of your model with Fo force

When wind is defined in case 2 and case 1 has no forces defined in load table

 

Assembly case 1 (with no loads defined) gives expected prestress force (and no visible deformation).

Krzysztof_Wasik_0-1666686471262.png

Wind aplied in  load case 2 gives final tension (depending on prestressing force and wind load) and corresponding deformation.

Wind load case 2 results  for prestressing 2.5

Krzysztof_Wasik_1-1666686541147.png

Wind load case 2 for increased prestressing force - F0=5 kN (smaller displacement bigger tension as expected)

Krzysztof_Wasik_2-1666686596672.png

 

 

When generating combinations, all loads defined in load table are multiplied by defined coefficients

It means that when assembly case is used in combinations, all loads defined for assembly case in load table - for instance dead load if considered in assembly case) are multiplied by defined combination factor, but prestressing force defined in cable properties is not modified (regardless coefficient used in combination for case 1).

 

While cable structrure analysis large displacement effect should be activated for load cases and combinations.

 

I hope it will help

 

 

 

 



Krzysztof Wasik
Message 8 of 10

benoit.thiry
Contributor
Contributor

Thank you very much Krysztof,
this is now very clear to me.  I suggest that the user manual / on line help is modified/updated to
include your useful explanation. The user can hardly imagine hat he needs to consider
one extra initial load case for the cables, as initial data are already included in the cable data..
Benoît

Message 9 of 10

Krzysztof_Wasik
Autodesk Support
Autodesk Support
0 Likes
Message 10 of 10

benoit.thiry
Contributor
Contributor
Accepted solution

Indeed, it is obvious that when using non-linear element every load case and of course
every load case combination becomes a non linear case to be run separately.

What I wanted to say is that "the assembling load case" is not described in the Robot documentation
It must be documented.  Your explanation was very clear.
Had it been present in the documentation, we wouldn't have this discussion ....

Thank you again,

Benoît 

0 Likes