Skip to main content
Version: Ver.4.10

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 modeBehavior
Free RunDisables triggers. Logging starts and stops together with monitoring.
TriggeredRecording 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.
ReTriggeredRecording 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.
tip

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 Recording Conditions​

ConditionUse
Signal TriggerEvaluate signal values
Log TriggerEvaluate frame ID, channel, data, and other properties
Key TriggerStart and stop recording through operator key input

When multiple condition types are enabled on the same start or stop side, any one of them can trigger the action. Turn off Log Trigger and Key Trigger on a side that should use only a signal condition.

Configuring Signal Triggers​

Signal Window alerts provide notifications of condition activation/recovery and a history for review. Enabling an alert alone does not make it a log recording start or stop condition.

  1. Stop monitoring and add the target signal to the Set to use in Signal Catalog. Assign the channel and make that Set the Current Set.
  2. Set Trigger Mode in Trigger Window to Triggered or ReTriggered.
  3. Open Select Signal for Start Signal Trigger or Stop Signal Trigger.
  4. From the Current Set candidates, select a numeric bus signal with a channel assigned. For unavailable candidates such as derived signals, ASCII signals, or signals without channel assignments, check the reason shown on screen.
  5. Set Condition (Above/Below), Threshold, and Hys, then click OK. Comparisons use numeric values converted according to the definition. If a factor or offset is defined, enter values in physical units.
  6. Enable the Start Signal Trigger/Stop Signal Trigger to use. Turn on Save Log File, specify the destination, and start monitoring.
Simulated_RPM_demo selected as the start condition: CH1-1, CAN-FD, ID 0x310, Start 16, Length 16, unit rpm

Figure 1a: Selecting the target signal in Select Signal.

Figure 1a shows an input candidate list. Select Simulated_RPM_demo in the second row. Check the signal name and Start column to distinguish it from the target speed in the first row. The actual rotational speed row has CH1-1, ID 0x310, Start 16, Length 16, and Unit rpm.

Actual settings with Triggered selected and red outlines around Start/Stop Signal Trigger for Simulated_RPM_demo CH1-1 ID0x310: start Above 2200, stop Below 1800, Hys 100 each

Figure 1b: Recording start and stop conditions based on actual rotational speed.

Figure 1b shows actual settings using FanDemo's Simulated_RPM_demo. The target is CH1-1, CAN FD, ID 0x310, start bit 16, signal length 16 bits, unit rpm. Triggered is selected; Start/Stop Signal Trigger are on, and Log Trigger and Key Trigger are off.

SideComparison condition and recovery width
Start Signal TriggerAbove
Threshold:2200 rpm
Hys:100 rpm
Stop Signal TriggerBelow
Threshold:1800 rpm
Hys:100 rpm

These are the configured thresholds. Distinguish them from the current Values readings at screenshot capture time and the boundary values in the recorded CSV. The Speed example below illustrates evaluation logic; its signal and units differ from Figure 1b.

Threshold and Hys​

ConditionValue that activates the condition while waitingValue that rearms it after activation
AboveAt or above ThresholdLess than Threshold minus Hys
BelowAt or below ThresholdGreater than Threshold plus Hys

If the first valid frame received already meets the condition, it activates immediately. Once activated, the same condition does not activate again until a value that rearms it is received. Frames with mismatched channel, ID, direction, length, or other properties, and invalid values, do not change this state.

For example, configure Speed in the sample DBC with Above, Threshold 10 km/h, and Hys 2 km/h.

Example reception timeSpeedEvaluation
0.0 s10 km/hFirst activation
0.1 s8 km/hEqual to the rearm boundary, so not rearmed
0.2 s7.5 km/hRearmed for the next activation
0.3 s10 km/hActivates again

This table illustrates evaluation of the same condition. Actual recording behavior follows the start/stop settings and trigger mode.

The signal definition and channel at selection time are recorded in Trigger Setting. After switching Current Set or changing signal definitions or channel assignments, recheck the conditions in Select Signal.

Basic Operation​

Configuring Log Triggers​

1. Open Trigger Window
Select Trigger Window from the menu or toolbar.

Trigger Window with Start/Stop Log, Key, and Signal Triggers; Free Run selected

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

Current Trigger Window with Triggered selected and Start/Stop Signal Trigger in the lower area

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.

Log Trigger 3

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 Edit button, or double-click the trigger condition display area, to open the Trigger Setting dialog.

Log Trigger 4

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

Log Trigger 5

The example above uses reception of a CAN FD frame with ID 300H as the stop Log Trigger condition.

tip

For details of the Trigger Setting dialog, see Log Trigger Setting Dialog.

6. Register the Log Trigger conditions
In the Trigger Setting dialog, click the OK 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.

Trigger Window in Free Run: Key Triggers in the middle left/right areas and Signal Triggers below

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

Current Trigger Window with Triggered selected and Start/Stop Key Trigger in the middle

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.

Key Trigger 3

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.

Key Trigger 4

The example above uses the Space key as the stop Key Trigger condition.

tip

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​

Trigger Window showing Trigger Mode, Start/Stop Log Trigger, Start/Stop Key Trigger, and Start/Stop Signal Trigger

The figure has Free Run selected. Log Triggers are at the top, Key Triggers in the middle, and Signal Triggers at the bottom. Start conditions are on the left and stop conditions on the right. No signal has been selected yet. Switch to Triggered or ReTriggered to configure conditions.

ItemDescription
Trigger ModeSelects the trigger operating mode.
• Free Run: Triggers disabled
• Triggered: Operates once when conditions are met
• ReTriggered: Repeats whenever conditions are met
Start Log TriggerStarts log recording when log data is received as the trigger.
Select the checkbox to enable.
Stop Log TriggerStops log recording when log data is received as the trigger.
Select the checkbox to enable.
Start Key TriggerStarts log recording on the specified key input.
Select the checkbox to enable.
Stop Key TriggerStops log recording on the specified key input.
Select the checkbox to enable.
Start Signal Trigger/Stop Signal TriggerStarts/stops log recording based on signal threshold conditions. Select the target signal using Select Signal.
Clear buttonResets (deletes) all configured trigger conditions.

Log Trigger Setting Dialog​

Configure the log conditions to detect as a trigger.

Log TriggerSetting
ItemDescriptionSettings
ChTarget channel (MicroPeckerX unit)Select from the following drop-down options.
ALL / 1 / 2 / 3 / 4
InnerChTarget channel (internal MicroPeckerX channel)Select from the following drop-down options.
ALL / 1 / 2
DirectionTransmission/reception framesR: Received frames / T: Transmitted frames / R or T: Both
StateValid frames or error framesSelect from the following drop-down options.
OK / NG
TypeTarget frame typeSelect from the following drop-down options.
[When Status: OK is selected]
• CAN-FD Frame
• CAN Data Frame
• Remote Frame
[When Status: NG is selected]
• 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 FormatCAN ID formatSelect standard (Std.) or extended (Ext.) CAN ID.
CAN IDs are specified in Hex. Enter an asterisk (*) to skip CAN ID matching.
DLCCAN data lengthEnter an asterisk (*) to skip DLC matching.
Data Setting buttonOpens the Data Setting dialog-
[1]Data sectionDisplays the data configured in the Data Setting dialog.

Data Setting Dialog​

Click Data Setting in the Log Trigger setting dialog to open the Data Setting dialog.
Configure data conditions for the log to detect as a trigger. Switch between Hex (hexadecimal) and Binary display using the tabs.

Log Trigger DataSetting
ItemDescriptionDetails
IDCAN IDThe CAN ID cannot be edited in Data Setting.
DLCData lengthThe data setting areas [2] and [3] change according to the DLC setting.
Enter an asterisk (*) to skip DLC matching.
[1]Hex/Binary tabsSwitches the data display between Hex and Binary.
[2]Byte-by-byte data setting area (Note 1)Each cell represents one byte and can be edited. The upper-left cell is Data1.
Enter an asterisk (*) to skip matching that data.
[3]Editor area (Note 1)Enter data as comma-separated bytes.
Enter an asterisk (*) to skip matching that data.
Settings can be saved to and loaded from a CSV file.
Load button buttonLoad Data Setting configuration fileLoads a CSV file saved in Data Setting.
Save button buttonSave Data Setting configuration fileSaves Data Setting to a CSV file. The settings in [3] are saved.

Note 1: Data can be edited in either [2] or [3]. The settings displayed in [2] and [3] are linked.

Key Trigger Controls​
key Trigger Setting
ItemDescriptionDetails
[1]Main keySets the key to use as a trigger.
Available keys: 0–9, A–Z, F1–F12, SPACE
[2]Sub-keySets a modifier key to combine with the main key.
Available keys: Shift, Ctrl, Alt

Checking Recording Results​

Check waiting, recording start, and recording stop states in the status bar. After stopping, check the target channel, times, and frames in the communication log at the specified destination. For Triggered and ReTriggered termination conditions, see Trigger Modes.

After stopping with the settings in Figure 1b, analyze the Signal Analysis Monitor buffer (trigger intervals 1) and set the Export CSV range to Selected trigger interval to check the recorded interval. Figure 2 shows the signal-value CSV output range confirmation screen.

Export Signal CSV with Selected trigger interval from +000:00:08.084.160 to +000:00:38.999.996, end excluded, and CH1 Simulated_RPM_demo selected

Figure 2: Checking one recorded interval using the signal-value CSV output range.

The interval starts at +000:00:08.084.160 and ends at +000:00:38.999.996, a difference of 30.915836 s. As indicated by end excluded on screen, the signal-value CSV excludes the end timestamp.

In the CH1-1 communication log CSV automatically saved by Save Log File (Offset 0), both the first and last records were received frames (R) on CH1-1 with ID 0x310. D3 and D4 represent actual rotational speed as a 16-bit Little Endian value.

  • First: Time is +000:00:08.084.160. D3 and D4 are 98 08, representing 2200 rpm.
  • Last: Time is +000:00:38.999.996. D3 and D4 are 06 07, representing 1798 rpm.

This communication log CSV includes the final stop frame. The configured start threshold is 2200 rpm and the stop threshold is 1800 rpm, while the recorded stop value is 1798 rpm. Check the signal-value CSV selection range and the communication log CSV boundaries separately.

Forcing Logging to Start​

You can force logging to start before a logging start trigger is detected.
Select Command → Forced Logging Start from the menu bar.
You can also use the toolbar Forced Logging Start button button to force logging to start.

Force Logging Start

Status Bar Indicators​

The status bar shows trigger waiting, recording, and stopped states. Figures 3–5 are actual screens captured with the Signal Trigger settings in Figure 1b.

On this screen, Last Trigger displays [Log] Logging Start/[Log] Logging Stop even when using Signal Triggers. Do not infer Log Trigger configuration from [Log] alone; check the enabled conditions in Figure 1b. Use Status on the left to check the current operating state.

At capture time, Values showed 1451 rpm while waiting (+000:00:02.464.888) and 2491 rpm while recording (+000:00:10.263.866). These are current readings at capture time. Check the configured thresholds in Figure 1b and actual recorded start/stop values in Recording Results.

Waiting for a Logging Start Trigger​

Status bar while waiting to start, with red outlines around Wait Start Trigger and Last Trigger [Log] Logging Stop

Figure 3: Wait Start Trigger while waiting for the start condition.

Last Trigger is the most recently displayed trigger information. In Figure 3, check [Log] Logging Stop separately from the left-hand status indicating that the application is currently waiting to start.

Logging Started​

Status bar during recording, with red outlines around Logging and Last Trigger [Log] Logging Start

Figure 4: Logging displayed after the start condition is met.

Logging Stopped​

Status bar after stopping, with red outlines around Setting, Logging Complete., and Last Trigger [Log] Logging Stop

Figure 5: Display after stopping and saving completes.

With the Triggered settings in Figure 1b, meeting the stop condition stops recording and monitoring. Figure 5 displays Setting and Logging Complete..

The status bar displays trigger information when a logging start or stop trigger is detected.