I imagine you could log the dialog message events coming from PCDLRN, and even filter events to those specifically containing collision messages.
It should be enough to catch the event PCD_ApplicationEventsEndExecution(...) as there is a parameter TerminationType in that call. You will get this event regardless of how the part program stopped.
To also detect that PC-DMIS itself has crashed, you could have a watchdog timer (for a fairly long time) that gets reset on any event from PC-DMIS ('gotta catch them all' in that case), and signals an alarm if it finally triggers, which means that PC-DMIS has stopped in an uncontrolled way.
I imagine you could log the dialog message events coming from PCDLRN, and even filter events to those specifically containing collision messages.
It should be enough to catch the event PCD_ApplicationEventsEndExecution(...) as there is a parameter TerminationType in that call. You will get this event regardless of how the part program stopped.
To also detect that PC-DMIS itself has crashed, you could have a watchdog timer (for a fairly long time) that gets reset on any event from PC-DMIS ('gotta catch them all' in that case), and signals an alarm if it finally triggers, which means that PC-DMIS has stopped in an uncontrolled way.
