Hi, could be very interesting if in the pretension window definition, we could have an option to request also the history output of the section loads. I´m doing a small assembly with 14 bolts and creating also the 14 history output requests…was a pain 
Maybe for some other kind of loads that could be interesting also.
Regards
Do you mean RF node output from pretension section nodes ? In Abaqus, you can request that directly for bolt load (one such load definition can span multiple bolts):
This is converted to *Node output from the pretension section reference node.
I´m talking about this section output in PrePomax. By the way, could be defined/selected multiples bolts loads with only one pretension definition in Prepomax??? That would be great if all loads are the same.
Ok, I see. Normally, forces at the pretension section node would be better, but I don’t think you can get their correct values from CalculiX.
Yes, but all bolts will use the same pretension section node and will be loaded by a proper fraction of the specified load.
I think I understand the request. So if there are multiple bolts with the same pretension load, UI should allow for the selection of all of them and, if necessary, output the section forces.
I wll have to look into this if it is possible and how.
Well, if the output section forces can be added…why not also add the mesh offset to the combo? That will make the bolt loading definition in one operation .
Another similar aplication would be in the contact pair definition, allowing also to create the contact output request directly in the same window.
For consistency, I’d rather keep all the output request options in their current place, but maybe the aforementioned special features could automatically create output requests (since they are mostly needed anyway, and history output is light). Especially contact output could always be requested by default - Abaqus also does it (see screenshot below), and it’s very often the case that you have a contact pair, but forget *CONTACT FILE and have to rerun just to see CPRESS.
I also think that all the output request options should remain in their current place. But maybe automatically adding some history outputs for some items (prestress, contact) makes sense. I only worry about what happens if those items are changed, deactivated, renamed, …
I think that is a good idea also adding those automatic history/field outputs for some loadings. If the loads are eliminated, will the solver run at least leaving the history output empty at least? That would be the best scenary, gaving some warnings to the user but with the solver running.
By the way, I have tested the procedures for creating history outuputs after solving, and they work very well, great feature. Problem is when there are too many (bolts in my case), or some field outputs suchs a contact outputs are not created (that is unsolvable, and worst is for models with long solving time)
