Corrected from:
L_TT1P_TechnologyModules_LM (V3.14.2.58)
Response of the new version:
Profiles stopped via xPathStop or xPathHalt, can be aborted via a rising edge at the xAbort input. The profile is started with a rising edge at the xExecutePickAndPlace input from scPar.
What happens?
The newly selected profile is not executed.
When does this behaviour occur?
The selected profile has stopped at a breakpoint (xPathHold status = TRUE).
The profile is aborted.
- Variant 1: xPathStop and xAbort
- Variant 2: directly via xAbort
Which products are affected?
L_TT1P_PickAndPlaceHighHigh function block in the L_TT1P_TechnologyModules_LM library (V3.14.1.50 and higher)
Short-term measures:
For aborting a profile at a breakpoint:
xPathStop = TRUE -> TM changes to the STOP state.
- When the technology module is in the STOP state, the xAckPathHalt input has to be acknowledged with a rising edge (FALSE-> TRUE -> FALSE). xAckPathHalt can also be set when the technology module is not at a breakpoint.
At least one clock cycle later, the profile has to be cancelled with a rising edge at the xAbort input (FALSE-> TRUE -> FALSE).
