If there isn't a RMB option, then it's not implemented by default. The workaround is to introduce a custom solution (I forget the exact term), and call out the correct SMISC number associated with that type of result in the database. Another option would be to introduce an APDL command object and script using apdl commands to take a print screen of the model with the reactions displayed. You could also setup that same script to export the results to a text or csv file for further post processing.

Quote (STpipe)

The workaround is to introduce a custom solution (I forget the exact term), and call out the correct SMISC number associated with that type of result in the database.

I believe you are referring to User Defined Result (UDR). I tried that today, but I had no success. I'm using v2022R2. At that version, there is no way to scope the UDR to the joints. I learned that that feature came available at v2023R2.

Quote (STpipe)

Another option would be to introduce an APDL command object and script using apdl commands to take a print screen of the model with the reactions displayed. You could also setup that same script to export the results to a text or csv file for further post processing.

No, that will not work either. On Solution Combination, there is no RMB option to insert Command Objects unfortunately.

With this much little information its difficult to guess what you are looking for.

Are you looking for reaction forces at joints? This link might help. You need to use APDL commands in solution.

Quote:

On Solution Combination, there is no RMB option to insert Command Objects unfortunately.

You need to insert command snippet before solving the model.

Quote:

I believe you are referring to User Defined Result (UDR). I tried that today, but I had no success. I'm using v2022R2. At that version, there is no way to scope the UDR to the joints. I learned that that feature came available at v2023R2.

That's because "joint" is not something that is recognized by the apdl solver. It only knows nodes and elements. So any user defined results would have to be scoping towards one of these two items. I'm not sure if you can scope it directly to nodes within Ansys Mechanical, however the other option would be to extract the nodes into a list or assign the support nodes to variables to post-process within the apdl script. Another possibility (I can't recall specifically if this is possible or how to do it) is to use the named selections.

I believe if you have a named selection for the joints being supported, you can convert it to nodes, and that named selection gets transferred to APDL with a defined name which the software can use later on to reference when assigning loads or boundary conditions.

Quote:

No, that will not work either. On Solution Combination, there is no RMB option to insert Command Objects unfortunately.

Maybe not within the solution combination part of the tree, but within the solution part of the tree you could define a command object and generate the plots and extract the data.

I don't have access to Ansys anymore in my current position, but a lot of this comes from memory, so there might be a few tweaks needed on my advice to find the correct workaround. The important thing to recognize is that anything that is available in Ansys classic (and was saved to the database after the solving), can be pulled from the database within Ansys Mechanical.