Every trigger identifies the trigger event type, which identifies when the trigger will be executed.
The trigger event types are described in the Trigger event type reference. In addition to the standard trigger event types, the Apex Cleco driver makes available additional trigger event types that are associated with tool rundown events on an Apex Cleco controller.
When the Apex Cleco device is started, the driver will subscribe with the controller for either single spindle tightening result messages, which are known in the Open Protocol Specification as MID0061 messages, or for multi-spindle result messages, which are known as MID0101 messages. The controller will send these messages to the node when a tightening occurs. Additionally when the device is started, the driver will query the Apex Cleco controller to see if there are any jobs defined. If there are, the driver will also subscribe with the controller to receive information about the active job. The job information will be sent to the node whenever a job is selected and whenever a tightening occurs.
Apex Cleco event types
The Apex Cleco category is available in the Trigger Event Type list when defining or editing a trigger. This example shows a new trigger being defined with the Canvas Editor:
When the Apex Cleco Event Message trigger event type is selected, the Event tab becomes active with parameters that accommodate the Apex Cleco Event Message event.
| Parameter | Description |
|---|---|
| Device Name | Select an Apex Cleco device. This list will contain both Power Focus type devices and Power MACS type devices. |
| Event Message |
Select one of the available tool rundown messages from the list:
|
Selecting the appropriate Event Message
The Event Message option selected for a trigger will depend upon the configuration of the controller, as well as the actions that you will define in the trigger.
- mPro400 controllers support both single-spindle and multi-spindle event messages. Apex Cleco trigger event type triggers interfacing with these types of devices can be used to capture either MID0061 Last Tightening Result or MID0101 Multi-spindle Result event messages.
- If the controllers have jobs defined and you are interested in tracking tool rundowns at the job level, then the MID0035 Job Info event message should be selected.
Different triggers can be developed to process the different event messages. For example, for a controller that has jobs defined, a trigger could be defined to execute upon receipt of the MID0035 Job Info event message and a second trigger defined to execute upon receipt of the MID0061 Last Tightening Result event message.
Each event message option contains the data that is unique to the event message it represents. These data items are available to the trigger as trigger event variables.