Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations cowski on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!
Coping Loads 1
- Thread starter Sam1993
- Start date
JoshPlumSE
Structural
RISA-3D or RISAFloor?
For RISA-3D, you could copy the joints that define the area loads up to the upper floor. That would do it.
For RISAFloor, when you create the floor, you should be able to base it off of an existing floor (I believe). Though I haven't used that program in a few years.
For RISA-3D, you could copy the joints that define the area loads up to the upper floor. That would do it.
For RISAFloor, when you create the floor, you should be able to base it off of an existing floor (I believe). Though I haven't used that program in a few years.
- Thread starter
- #3
If you don't have the nodes selected when you perform your copy, it won't copy the area loads as those are node dependent and not member dependent.
Also, when you click global copy, there's a check box indicating copy loads on the left hand side. You need to make sure that's clicked.
Also, when you click global copy, there's a check box indicating copy loads on the left hand side. You need to make sure that's clicked.
- Thread starter
- #7
-
1
- #9
Sam,
Yes, duplicate nodes at the same location are not, themselves, connected. So, any things that are connected to the different nodes can't talk to each other, unless you manually constrain the first node to follow the second node.
If you look at the deflected shape for members defined to 2 different nodes, they will deflect separately and spread apart from each other, because nothing is forcing them to deflect together. In general, the deflected shape is a great way to visually see if your model is all connected as you thought it should be.
As jayrod points out, the Full Model Merge command fixes duplicate nodes.
Yes, duplicate nodes at the same location are not, themselves, connected. So, any things that are connected to the different nodes can't talk to each other, unless you manually constrain the first node to follow the second node.
If you look at the deflected shape for members defined to 2 different nodes, they will deflect separately and spread apart from each other, because nothing is forcing them to deflect together. In general, the deflected shape is a great way to visually see if your model is all connected as you thought it should be.
As jayrod points out, the Full Model Merge command fixes duplicate nodes.
- Status
Similar threads
