I am trying to output my Operator Message as the last block within my End of Path Events, However, it always outputs the message before it even triggers the End of Path.
I have the proc PB_CMD_MOM_operator_message in the End of Path area but this outputs it both before AND within the End of Path.
I don't really want to write another UDE just for this, if I can get away using the existing Operator Message UDE, that would be a treat.
Do any of you know how to govern where the End of Path Event UDE's are output?
For ref. I am using NX 7.5.
Any help is much appreciated.
In case you are not aware, if you are putting this in the end of path UDEs, then the order of the events being sent to the post is fixed. The procs are called when the events are received.
From the docs:
When you post process a tool path, the data is output in the following order:
Start of program
User-defined events (UDEs) attached to the program
Start of parent group (program, machine tool, geometry, method)
UDEs attached to the parent group
UDEs attached to the geometry with program, machine tool, geometry, method commands
UDEs attached to the method with Start Events
UDEs attached to the cutting tool with Start Events
UDEs attached to the machine tool with Start Events
Start of operation
Tool change (not Load tool)
UDEs attached to the operation with Start Events
UDEs attached to the operation with End Events
End of operation
UDEs attached to the geometry with End Events
UDEs attached to the method with End Events
UDEs attached to the cutting tool with End Events
UDEs attached to the machine tool with End Events
End of program
I don't if you can delay the output in yout post.
1) Note the above is when you post an OPERATION, - if you post a GROUP, it is slightly different. (yes, there is an IR somewhere on this - hopefully it will be added to the docs soon)
2) To a certain extent, you can effect the above using the "marker" UDEs (tool_change_marker, start_marker, return_marker, etc.), but note that these events have to exist (start_marker is meaningless if there is no avoidance "start" point). And primarily it only tweaks the output in steps 10-13 of Mark's list.
3) If you need more control that the above gives you, you need to do "post magic" to store the data when the UDE event gets triggered (i.e. NOT output anything RIGHT THERE) and then output it where you want.
Production: NX10.0.3.5 MP5 + patch/TC11.2
I'd rather be e-steemed than e-diseaseled