Event-Based Transmission
Event transmission sends frames when a trigger condition occurs. The following triggers are available:
- Receive Trigger: Detect a specific CAN ID.
- Log Trigger: Detect a frame that matches conditions in the monitoring log.
- Key Trigger: Detect a keyboard shortcut.
Slot Transmission Modes
Use these modes with event triggers (configured per slot in Send Frame):
| Mode | Description | Behavior |
|---|---|---|
| Periodic | Periodic transmission | Sends at the defined cycle continuously. |
| Periodic Trigger | Periodic triggered | Waits for the event, then starts periodic transmission. |
| Event | Event transmission | Sends once when the event fires. |
| Event Periodic | Event + periodic | Runs periodic transmission and issues an additional event-driven send whenever the trigger fires. |
See the diagram for timing differences between the modes.
Event Trigger Settings
Within the CAN/CAN-FD Frame Setting dialog, the Event Trigger section lets you configure:
- Delay Time: Delay between detecting the event and sending (0.1 ms resolution).
- None / Receive Trigger / Receive Trigger (CAN FD) / Ext Trigger / Log Trigger / Key Trigger*.
Ext Trigger is reserved for future use.
Receive Trigger Configuration
Specify the ID format (Std/Ext), ID value, and frame type (Data/Remote) for the incoming frame that fires the event.
Log Trigger Configuration
Open the Log Trigger dialog to define rich conditions (channel, direction, ID, data bytes, error states, etc.). An optional Data Setting dialog helps specify payload patterns.
Direct Transmit (Reference)
Direct Transmit lets you send a predefined frame instantly via the Send button while monitoring:
- Configure protocol, ID, DLC, data, and Bit Rate Switch as needed.
- Press Send during monitoring to transmit the frame once.
Use event triggers to automate complex stimulus patterns while retaining the ability to inject manual frames when required.