Mechanical to ACT.

Hello together,
I have created a post-processing script in ANSYS Mechanical to insert coordinate systems at certain positions.
Deformation probes are based on the created coordinate systems and the tabular results will be exported.
The script itself does the job.
I want to create an ACT, but i am struggling. I can pass the mandatory inputs from details window.
But from ACTlog i am getting a read-only error.
I assume i am getting the error because i am creating the object in Solution of the branch, while trying to create coordinate systems in the pre-processor.
Is there a possibility to trigger the script via ACT in a solved model, so that the coordinate system and probes will be created?
Thanks in advance
Jan-Christopher
Answers
-
The error indicates you have this property set to a parameter and is therefore read only. When you have items are parameters the control goes to Workbench and the parameter set (similar to in the UI). I don't see this in the screenshots, but this seems to be the error message.
To know more you would need to post the code that is generating the error, or debug it to the particular line that is causing it and post.
1 -
Hello Mike,
thank you very much for your reply. I was debugging the code further and was able to identify the position where the problem occurs.The creation of the coordinate system (line 197) is succesful. But the change of scoping method to named selection and further manipulation is not possible.
Is there a possible work-around?
E.g. by changing the location of the details window from "post" to "pre", shown in xml-screenshot of previous post. Or dividing the my script into a pre part to create the coordinate system and a post part to create the deformation probes and write the results to an ASCII file.Would be glad to get any further explanation.
Best regards
Jan-Christopher0 -
@Pierre Thieffry If I remember correctly you faced this issue when developing the Relative Displacement app, did you find a workaround?
1 -
@Pierre Thieffry have you faced a similiar issue, while developing the Relative Displacement app, like mentioned by @Pernelle Marone-Hitz.
If my current way of implementing is a dead end, I just have to know and i´ll try to find a workaround.
Thanks in advance :-)
0