Recording Logs with Conditions
Triggers automatically start and stop logging when the following predefined conditions are detected during monitoring.
- A specific log is detected (Log Trigger)
- A specific key is pressed (Key Trigger)
- A specific signal value meets a threshold condition (Signal Trigger)
This lets you efficiently save logs for just the periods you need.
Configure triggers in Trigger Window.
Trigger Modes
To control log recording with trigger conditions, turn on Save Log File on the main toolbar. Start and stop behavior depends on the mode.
| Trigger mode | Behavior |
|---|---|
| Free Run | Disables triggers. Logging starts and stops together with monitoring. |
| Triggered | Recording starts when a start condition is met. If no start condition is configured, recording starts together with monitoring. When a stop condition is met during recording, both recording and monitoring stop. |
| ReTriggered | Recording starts when a start condition is met. When a stop condition is met during recording, the interval ends and the application waits for the next start. Monitoring also stops when 64 recording intervals have been completed. |
A stop condition met while waiting for a start does not end monitoring or increment the interval count. ReTriggered requires a start condition. Configure a stop condition as well for repeated recording. When a start condition is met, the recording interval's start time is recorded. Communication log CSV files are output for each interval after monitoring stops. If a later interval has no log records for the target channel, a file may not be created for that interval.
Types of Conditions
| Condition | Use |
|---|---|
| Signal Trigger | Compares numeric values extracted from LIN frames against thresholds. |
| Log Trigger | Matches IDs, data, and other frame log conditions. |
| Key Trigger | Detects the configured key input. |
For each start/stop side, any enabled Signal, Log, or Key condition can trigger the action. Configure alerts, which notify you of condition activation/recovery, separately.
Configuring Signal Triggers
- Stop monitoring. Add the target signal to a Set in Signal Catalog, assign a LIN CH, and make the Set Current.
- Set Trigger Mode in Trigger Window to Triggered or ReTriggered.
- Open Select Signal for Start Signal Trigger or Stop Signal Trigger. Verify the target CH, ID, bit range, and unit, then select the signal.
- Enter Condition (Above/Below), Threshold, and Hys, and click OK.
- Enable the Start/Stop Signal Trigger to use. To record using only signal conditions, disable Log/Key conditions on both the start and stop sides.
- Turn on Save Log File on the main toolbar, set Log Folder, and select Start. If a start condition is configured, check the transition from Wait Start Trigger to logging, then check the destination for communication logs after completion. For termination conditions, see Trigger Modes.
The selection list contains numeric bus signals with CH assignments in the Current Set and valid frame conditions and conversion settings. Derived signals, ASCII, and Value Tables returning only Logical state names are excluded. If a signal is missing, also check Search and Protocol filters. For a saved trigger, the Set used at selection need not remain Current as long as its definition and CH references remain valid.
Example: Starting and Stopping Recording with Speed
Use the same definitions and Set as Reusing Definitions (Figure 13) on the previous page. After loading, check Default [Current], Speed's In Set status, CH1-1, LIN ID 10, and SensorFrame before selecting the signal in Trigger Window.
Use Speed in SensorFrame, LIN ID 0x10 on CH1-1. In Select Signal, verify not only the signal name but CH1-1, Protocol LIN, ID 0x10, Start 0, Length 8, and Unit km/h.
Figure 1: Checking Speed's frame conditions, bit range, and unit in Select Signal.
Set Trigger Mode to Triggered, enable Start/Stop Signal Trigger, disable Start/Stop Log Trigger and Key Trigger, and configure the following conditions.
| Side | Comparison condition and recovery width |
|---|---|
| Start Signal Trigger | Above Threshold:10 km/h Hys:2 km/h |
| Stop Signal Trigger | Below Threshold:8 km/h Hys:2 km/h |
Figure 2: Configuring recording start/stop conditions using Speed.
Hys for the start condition is the width required to rearm that condition after activation. Configure the recording stop condition separately in Stop Signal Trigger. The table shows configured thresholds; distinguish these from current monitoring values and the start/stop values in the saved communication log.
Threshold and Hys Evaluation
Use the same units for Threshold and Hys as the signal's converted numeric value. If the definition converts Speed to physical values, compare in km/h; if it returns raw numeric values, compare raw values. Switching the Signal Window display does not change the evaluated value.
| Condition | Activation | Rearm condition |
|---|---|---|
| Above | Value at or above Threshold | Value becomes less than Threshold minus Hys |
| Below | Value at or below Threshold | Value becomes greater than Threshold plus Hys |
If the first valid value meets the condition, it activates immediately. Subsequent activations are detected only after the rearm condition has been met. Invalid values and data not matching the frame conditions do not change the evaluation state.
For example, set Speed to Above, Threshold 10 km/h, and Hys 2 km/h. If the first valid value is 10 km/h at 1 second, the condition activates. Exactly 8 km/h at 2 seconds does not rearm it. A value of 7.5 km/h at 3 seconds rearms it, and 10 km/h at 4 seconds activates it again. Recording starts/stops according to the Trigger Mode and recording state at that time.
After changing definitions, devices, or CH assignments, check saved trigger references. If Signal Trigger reference is invalid. Select Signal again. appears, reselect the signal using Select Signal.
Checking Recording Results
Figures 3–5 show an actual recording using the Signal Trigger settings in Figure 2 with Save Log File enabled. Check both the status bar and Values while waiting, recording, and after stopping. The configured start threshold is 10 km/h and the stop threshold is 8 km/h.
This example actually transmits SensorFrame with ID 0x10 as Dir=T from Master Sim. on CH1-1. Speed changes approximately every 10 seconds through 7→12→9→7 km/h. It is not a capture of a board's ID 0x10 responses. For transmission setup, see Linking Signal Definitions and Transmission Settings.
Status Bar Indicators
Figures 3–5 combine excerpts of Values and the bottom status bar captured at the same instant. On this screen, Last Trigger shows [Log] Logging Start/[Log] Logging Stop even when using Signal Triggers. Check the enabled settings in Figure 2 for the condition type and Status on the left for the current operating state.
Figure 3: Wait Start Trigger while waiting for the start condition.
Speed shows No Data in Figure 3. Do not interpret the waiting display as 0 km/h; verify that Status is Wait Start Trigger.
Figure 4: Checking Logging and Speed after the start condition activates.
In Figure 4, Time is +0000020.002580, Speed is 12 km/h, and Status in Values is Received. The bottom status shows Logging and Last Trigger [Log] Logging Start. Recording began at 12 km/h, meeting the Above 10 start condition.
Figure 5: Checking Setting and Logging Complete. after the stop condition activates.
In Figure 5, Time is +0000040.002583, Speed is 7 km/h, and Status in Values is Value Changed. In Triggered, the Below 8 stop condition stops both recording and monitoring. The bottom status shows Setting, Logging Complete., and Last Trigger [Log] Logging Stop.
Recording Intervals and Communication Logs
After stopping, analyze the Monitor buffer in Signal Analysis and set the Export CSV range to Selected trigger interval to check the recording interval. In this recording, the start is +0000020.002580, the end is +0000040.002583, and the difference is 20.000003 s. The signal-value CSV includes the start time and excludes the end time, as indicated by end excluded.
In the communication log LN1SpeedTrigger_1-1.csv automatically saved by Save Log File, check CH1-1, Protocol LIN, Dir T, Type Response, ID 10 (hexadecimal 0x10), and DL 2. The Response rows in this recording include both the start and stop frames.
| Communication log time | D1/D2 | Speed |
|---|---|---|
| First: +0000020.002580 | 22 01 | Starts at 12 km/h |
| Intermediate: +0000030.002580 | 1C 01 | Continues recording at 9 km/h |
| Last: +0000040.002583 | 18 01 | Stops at 7 km/h |
The configured stop threshold is 8 km/h; the actual recorded stop value is 7 km/h. Recording continues at 9 km/h because it does not meet the stop condition. The saved communication log CSV includes the Response at the end time (7 km/h). When checking the signal-value CSV, check the export range and keep in mind that LIN Header frames generate no signal samples on their own.
Figure 6 uses a separate Ver.4.10 ReTriggered recording with 3 intervals. The interval immediately before the last one is selected: +000:00:04.002.476–+000:00:05.002.478 (end excluded). Its times and start/stop conditions differ from the 20–40 s Signal Trigger example above. Select the intended interval in the graph, then verify its start and end in Export CSV.
Figure 6. Selecting the interval immediately before the last one in a ReTriggered recording.
The interval's communication log, MPXLogData_1-1_0001.csv, contains Response (4.002476 s, 7 km/h), Header (5.000762 s), and Response (5.002478 s, 12 km/h). Exporting Speed with Selected trigger interval and Value changes only OFF produces 1 data row at 7 km/h: Header generates no sample, and the last Response is at the excluded end time. Opening the saved communication log and exporting Entire analysis produces 2 Response rows at 7 and 12 km/h. See the verified CSV results (Figures 7–8) and the saved-log comparison.
Basic Operation
The following procedures configure Log Trigger and Key Trigger individually. The overview reuses Figure 2. When configuring other conditions, disable unused Start/Stop Signal, Log, and Key Triggers so that only the intended conditions are enabled.
Configuring Log Triggers
1. Open Trigger Window
Select Trigger Window from the menu or toolbar.

2. Enable triggers
In Trigger Mode, select the Triggered or ReTriggered radio button. This enables triggers and makes the following items configurable.
- Start Log Trigger
- Stop Log Trigger
- Start Key Trigger
- Stop Key Trigger
- Start Signal Trigger
- Stop Signal Trigger

Triggered is selected in the example above.
3. Enable a start or stop Log Trigger
Check Start Log Trigger or Stop Log Trigger to enable the corresponding trigger.

The example above enables Stop Log Trigger by checking its checkbox.
4. Open the Trigger Setting dialog
In the area enabled in step 3, click the
button or double-click the trigger condition display area to open Trigger Setting.

5. Set the Log Trigger conditions
In the Trigger Setting dialog, set the Log Trigger conditions, such as protocol, channel, and transmission/reception direction.

The example above uses reception of a response with ID 2DH as the stop Log Trigger condition.
For details, see the Trigger Setting Dialog.
6. Register the Log Trigger conditions
In the Trigger Setting dialog, click the
button.
The configured Log Trigger conditions are registered and displayed in the trigger condition area of Trigger Window.


7. Monitor
When monitoring starts, logging starts or stops as the configured trigger conditions are detected.
Configuring Key Triggers
1. Open Trigger Window
Select Trigger Window from the menu or toolbar.

2. Enable triggers
In Trigger Mode, select the Triggered or ReTriggered radio button. This enables triggers and makes the following items configurable.
- Start Log Trigger
- Stop Log Trigger
- Start Key Trigger
- Stop Key Trigger
- Start Signal Trigger
- Stop Signal Trigger

Triggered is selected in the example above.
3. Enable a start or stop Key Trigger
Check Start Key Trigger or Stop Key Trigger to enable the corresponding trigger.

The example above enables Stop Key Trigger by checking its checkbox.
4. Set the Key Trigger conditions
Use the main key and sub-key drop-down menus to select the keys for the trigger condition.

The example above uses the Space key as the stop Key Trigger condition.
For details of Key Trigger settings, see Key Trigger Controls.
5. Monitor
When monitoring starts, logging starts or stops in response to the key inputs configured as trigger conditions.
Trigger Window

This is the same Signal Trigger example as Figure 2. Log is at the top, Key in the middle, and Signal at the bottom; start conditions are on the left and stop conditions on the right.
| Item | Description | Additional information |
|---|---|---|
| Trigger Mode | Selects the trigger mode using the Free Run, Triggered, or ReTriggered radio button. | See Trigger Modes. |
| Start Log Trigger | Configures a start Log Trigger that starts logging when the specified log is detected. | See Log Trigger Controls. |
| Stop Log Trigger | Configures a stop Log Trigger that stops logging when the specified log is detected. | See Log Trigger Controls. |
| Start Key Trigger | Configures a start Key Trigger that starts logging when the specified key input is detected. | See Key Trigger Controls. |
| Stop Key Trigger | Configures a stop Key Trigger that stops logging when the specified key input is detected. | See Key Trigger Controls. |
| Start Signal Trigger/Stop Signal Trigger | Starts/stops logging based on numeric signal threshold conditions. Configure the signal, Condition, Threshold, and Hys using Select Signal. | See Configuring Signal Triggers. |
button | Opens the following dialog.![]() Click Yes to delete all trigger conditions and change the trigger mode to Free Run. |
Log Trigger Controls

| Item | Description | Additional information | |
|---|---|---|---|
| Start Log Trigger | Start Log Trigger | Enables/disables the start Log Trigger. [ON] Enabled. [OFF] Disabled. | Disabled when Trigger Mode is Free Run. |
| Trigger condition display area (area ①) | Displays start Log Trigger conditions. | Double-click this area or click the button to open Trigger Setting and configure start Log Trigger conditions. | |
button | Opens Trigger Setting to configure start Log Trigger conditions. | ||
button | Scrolls start Log Trigger conditions to the previous page. | ||
button | Scrolls start Log Trigger conditions to the next page. | ||
| Stop Log Trigger | Stop Log Trigger | Enables/disables the stop Log Trigger. [ON] Enabled. [OFF] Disabled. | Disabled when Trigger Mode is Free Run. |
| Trigger condition display area (area ②) | Displays stop Log Trigger conditions. | Double-click this area or click the button to open Trigger Setting and configure stop Log Trigger conditions. | |
button | Opens Trigger Setting to configure stop Log Trigger conditions. | ||
button | Scrolls stop Log Trigger conditions to the previous page. | ||
button | Scrolls stop Log Trigger conditions to the next page. | ||
Trigger Setting Dialog
Configure start or stop trigger conditions.

| Item | Description | Additional information | |
|---|---|---|---|
| Ch | Ch | Sets the log channel (the number assigned to each MicroPeckerX unit) used as a Log Trigger condition. Drop-down options: ALL, 1, 2, 3, 4 | ALL targets every CH. |
| InnerCh | Sets the log internal channel (an internal channel number within a MicroPeckerX unit) used as a Log Trigger condition. Drop-down options: ALL, 1, 2 | ALL targets every internal channel. | |
| Protocol | Sets the log protocol used as a Log Trigger condition. Radio button options: CAN/CAN-FD, LIN, CXPI, DIO, AD | CXPI cannot be selected. | |
| Direction | Sets the log direction used as a Log Trigger condition. Radio button options: R, T, R or T | R means received only, T transmitted only, and R or T both. Unavailable when Protocol is DIO or AD. | |
| Protocol-specific settings (area ①) | Displays settings for the selected Protocol. | For protocol-specific settings, see: [CAN/CAN FD] CAN/CAN FD Settings [LIN] LIN Settings [DIO] DIO Settings [AD] AD Settings | |
button | Saves the configured Log Trigger conditions and closes the dialog. | ||
button | Discards the configured Log Trigger conditions and closes the dialog. | ||
CAN/CAN FD Settings

| Item | Description | Additional information | |
|---|---|---|---|
| State | Sets the log state used as a Log Trigger condition. Drop-down options: OK, NG | ||
| Type | Sets the log type used as a Log Trigger condition. Drop-down options depend on State: [OK] CAN-FD Frame, CAN Data Frame, CAN Remote Frame [NG] All Error, Bus Error, Error Warning, Error Passive, Bus Off Entry, Bus Off Recovery, Overload, Bus Lock, Arbitration Lost, Stuff Error, Form Error, Ack Error, CRC Error, Recessive Bit Error, Dominant Bit Error, Ack Delimiter Error | ||
| ID Format | Sets the CAN ID format used as a Log Trigger condition. Drop-down options: Std., Ext. | Only displayed when State is OK. | |
| ID (area ①) | Sets the CAN ID used as a Log Trigger condition in hexadecimal. | Only displayed when State is OK. | |
| DLC | Sets the data length used as a Log Trigger condition. Drop-down options: 0, 1, 2, 3, 4, 5, 6, 7, 8, 12, 16, 20, 24, 32, 48, 64, * | Only displayed when State is OK. | |
button | Opens Data Setting to configure byte-by-byte log data used as a Log Trigger condition. | Only displayed when State is OK. | |
| Data display area (area ②) | Displays byte-by-byte log data configured in Data Setting for the Log Trigger condition. | Double-click this area or click the button to open Data Setting and configure byte-by-byte log data for the Log Trigger condition.Only displayed when State is OK. | |
CAN/CAN FD Data Setting Dialog
Configure log data used as a Log Trigger condition.
Switch tabs to display Hex (hexadecimal) or Binary data.


| Item | Description | Notes |
|---|---|---|
| ID | Displays the CAN ID configured in Trigger Setting in hexadecimal. | You cannot change the ID in this dialog. |
| DLC | Sets the data length used as a Log Trigger condition. Drop-down options: 0, 1, 2, 3, 4, 5, 6, 7, 8, 12, 16, 20, 24, 32, 48, 64, * | Changing the data length changes the editable range in the data setting area and Editor. An asterisk (*) is equivalent to 8, or 64 when Type in Trigger Setting is CAN-FD Frame. |
| Display format tabs (area ①) | Switch between Hex (hexadecimal) and Binary display. | |
| Data setting area (area ②) | Configures byte-by-byte log data for the Log Trigger condition. Enter hexadecimal values in Hex or binary values in Binary. | An asterisk (*) can be used in data values. Bits specified by an asterisk are not evaluated for the trigger condition. |
| Editor area | Configures each byte in CSV format. Enter hexadecimal values in Hex or binary values in Binary. | An asterisk (*) can be used in data values. Bits specified by an asterisk are not evaluated for the trigger condition. |
button | Opens a file dialog to load a CSV saved using and apply its contents to Editor. | |
button | Opens a file dialog to save Editor contents to a CSV file of your choice. | |
button | Saves settings and closes the dialog. | |
button | Discards settings and closes the dialog. |
The data setting area and Editor are linked. Changing values in either automatically updates the other.
LIN Settings

| Item | Description | Additional information | |
|---|---|---|---|
| State | Sets the log state used as a Log Trigger condition. Drop-down options: OK, NG | ||
| Type | Sets the log type used as a Log Trigger condition. Drop-down options depend on State: [OK] Header, Response/Frm., Wakeup, Sleep, B-Sleep [NG] All Error, SyncBrk. Long, SyncBrk. Short, Parity Err., ShortMsg Err., Checksum Err., NoRes. Err., Bit Err., Framing Err., SyncField Err., H. Timeout, UART Err. | ||
| ID | Sets the LIN ID used as a Log Trigger condition in hexadecimal. | Only displayed for the following Type values: Header, Response/Frm. | |
| DL | Sets the data length used as a Log Trigger condition. Drop-down options: 1, 2, 3, 4, 5, 6, 7, 8, * | Only displayed when Type is Response/Frm. | |
button | Opens Data Setting to configure byte-by-byte log data used as a Log Trigger condition. | Only displayed when Type is Response/Frm. | |
| Data display area (area ①) | Displays byte-by-byte log data configured in Data Setting for the Log Trigger condition. | Double-click this area or click the button to open Data Setting and configure byte-by-byte log data for the Log Trigger condition.Only displayed when Type is Response/Frm. | |
LIN Data Setting Dialog
Configure log data used as a Log Trigger condition.
Switch tabs to display Hex (hexadecimal) or Binary data.


| Item | Description | Notes |
|---|---|---|
| ID | Displays the LIN ID configured in Trigger Setting in hexadecimal. | You cannot change the ID in this dialog. |
| DL | Sets the data length used as a Log Trigger condition. Drop-down options: 1, 2, 3, 4, 5, 6, 7, 8, * | Changing the data length changes the editable range in the data setting area and Editor. An asterisk (*) is equivalent to 8. |
| Display format tabs (area ①) | Switch between Hex (hexadecimal) and Binary display. | |
| Data setting area (area ②) | Configures byte-by-byte log data for the Log Trigger condition. Enter hexadecimal values in Hex or binary values in Binary. | An asterisk (*) can be used in data values. Bits specified by an asterisk are not evaluated for the trigger condition. |
| Editor area | Configures each byte in CSV format. Enter hexadecimal values in Hex or binary values in Binary. | An asterisk (*) can be used in data values. Bits specified by an asterisk are not evaluated for the trigger condition. |
button | Opens a file dialog to load a CSV saved using and apply its contents to Editor. | |
button | Opens a file dialog to save Editor contents to a CSV file of your choice. | |
button | Saves settings and closes the dialog. | |
button | Discards settings and closes the dialog. |
The data setting area and Editor are linked. Changing values in either automatically updates the other.
DIO Settings

| Item | Description | Additional information | |
|---|---|---|---|
| DIO1 | Sets the DIO data level used as a Log Trigger condition. Drop-down options: *, 0(Lo), 1(Hi), 0(Lo)->1(Hi), 1(Hi)->0(Lo) | 0(Lo)->1(Hi) detects a transition from 0(Lo) to 1(Hi); 1(Hi)->0(Lo) detects a transition from 1(Hi) to 0(Lo). Selecting * excludes that DIO data level from the Log Trigger condition. | |
| DIO2 | |||
| DIO3 | |||
| DIO4 | |||
AD Settings

| Item | Description | Additional information | |
|---|---|---|---|
| Voltage | Area ① | Sets the AD threshold comparison used as a Log Trigger condition. Drop-down options: >=, <= | >= means at or above the threshold; <= means at or below the threshold. |
| Area ② | Sets the AD data threshold used as a Log Trigger condition, in increments of 0.1V. | Enter two digits for the integer part of the threshold (prefix values of 9 or less with 0). | |
| Duration | Sets how long AD data must meet the threshold for the Log Trigger condition, in milliseconds. The range is 10–1000. | ||
An AD Log Trigger activates when the AD value meets the threshold set in Voltage and remains in that state for at least the time set in Duration, measured from when the threshold was first met.
Key Trigger Controls

| Item | Description | Additional information | |
|---|---|---|---|
| Start Key Trigger | Start Key Trigger | Enables/disables the start Key Trigger. [ON] Enabled. [OFF] Disabled. | Disabled when Trigger Mode is Free Run. |
| Main key (area ①) | Sets the start Key Trigger key. Drop-down options: None, A, B, ..., Z, 0, 1, ..., 9, F1, F2, ..., F12, SPACE | Setting the main key to None disables the start Key Trigger. | |
| Sub-key (area ②) | Sets the sub-key combined with the main key for the start Key Trigger. Drop-down options: None, Alt, Ctrl, Shift Select None if no sub-key is required. | A sub-key alone cannot be used as a start Key Trigger condition. | |
| Stop Key Trigger | Stop Key Trigger | Enables/disables the stop Key Trigger. [ON] Enabled. [OFF] Disabled. | Disabled when Trigger Mode is Free Run. |
| Main key (area ③) | Sets the stop Key Trigger key. Drop-down options: None, A, B, ..., Z, 0, 1, ..., 9, F1, F2, ..., F12, SPACE | Setting the main key to None disables the stop Key Trigger. | |
| Sub-key (area ④) | Sets the sub-key combined with the main key for the stop Key Trigger. Drop-down options: None, Alt, Ctrl, Shift Select None if no sub-key is required. | A sub-key alone cannot be used as a stop Key Trigger condition. | |
Forcing Logging to Start
With a start trigger enabled, either of the following operations forces logging to start before the start trigger is detected.
- Select Command → Forced Logging Start from the menu bar.
- Click the toolbar
button.
button
button
button
button
button
button
button
and apply its contents to Editor.
button
button