Log Replay
Log Replay transmits to an actual LIN bus based on a communication log. Playback in Signal Analysis only moves the displayed time and does not transmit. Use a supported communication log, not an analysis CSV or Alert History CSV, and review the Safety Precautions.
Log Replay loads LIN records to replay from a communication log CSV and replays them as a master node. Normal header-only records are excluded; only some error records are replayed. See Log data list below for details.
Up to 3 million eligible records can be replayed. If the limit is exceeded, a message appears and eligible records are loaded from the start of the file up to the 3 million record limit.
Usage Example
By recording communication between ECUs beforehand, you can simulate communication with Log Replay even without ECU:A.
Basic Operation
- Select LogReplay in Simulation Window
Open Simulation Window from the menu or toolbar and select LogReplay under LIN Simulation Mode for the Ch to use. Figure 1 shows Ch1-1 while monitoring is stopped, before loading a log file. Initial Status is grayed out.
Figure 1: LogReplay before loading a log file.
-
Specify the log file to load Click the … button for Log File. In the file dialog, specify the MicroPeckerX communication log CSV to load. Use LN1SpeedTrigger_1-1.csv, the same file as in the Communication Log CSV Saving Example.
-
Load the log file Check that Log File shows the path specified in step 2, then click Load. Review the loaded records and configure per-ID Tx / Rx in LIN LogReplay Dir Setting before starting monitoring.
In Figure 2, the three normal Header rows among the six original communication log rows are excluded, and the three Response rows are loaded. All rows have Dir Tx, ID 10 (0x10), DL 2, and ErrorCode None; D1 and D2 are 22 01 → 1C 01 → 18 01. Delay is 0 ms for the first row according to First Delay, then 10000 ms for subsequent rows. Loop is OFF and Event Trigger is None. Figures 2–4 show settings while monitoring is stopped; no replay transmission is performed.
Figure 2: Communication log CSV loading results.
- Start monitoring Start monitoring using any of the following operations:
- Select Command → Start from the menu bar.
- Click the
button on the toolbar.
- Press F5. When Event Trigger is None, transmission starts after First Delay has elapsed from the start of monitoring. When Log Trigger or Key Trigger is selected, transmission starts after detecting the specified event during monitoring and then waiting for First Delay. With the Key Trigger settings in Figure 4, pressing A without a modifier after starting monitoring starts replay with First Delay 0 ms.
Log Replay Screen Description
See Figure 2 after loading for the location of each setting.
| Item | Description | Additional information |
|---|---|---|
| Log File | Displays full path of the target log file selected in file dialog from the button. | The target log file can also be set by directly entering full path. |
Button | Click to display file dialog and select target log file to load. | The selected log file is not loaded until the |
Button | Click to load the log file shown in "Log File". | MicroPecker log files cannot be loaded. |
| Loop | Sets whether log replay transmission repeats. Meanings of checkbox ON/OFF are: [ON] After transmitting the bottom log data in the list, returns to top and transmits log data sequentially again. [OFF] After transmitting the bottom log data in the list, transmission stops and enters waiting state. | |
| First Delay | Sets time in milliseconds until transmission of the top log data in the log data list. Configurable range is "0 to 60000". If "None" is set for "Event Trigger", this is elapsed time from monitoring start. Otherwise, it is elapsed time from event detection. | When changed by spin button, value increases/decreases in 10 ms units. |
| Dir(Tx/Rx) Setting button | Opens LIN LogReplay Dir Setting to set the transmission frame type for each ID. See LIN LogReplay Dir Setting for details. | |
Button | Click to stop log data transmission. | After transmission is stopped with this button, transmission cannot be resumed. To retransmit log data, you must stop monitoring once. |
| Log data list | Displays log data included in loaded log file. | Records with any of the following Type values are excluded from the log data display: Header (normal header only), Bit Err., Nores. Err., H. Timeout, UART Err., Bus Err., B-Sleep In current-format CSV, records with the following Type values are displayed, but their responses use dummy values (00H for every byte): Parity Err., SyncBrk. Long, SyncBrk. Short, SyncField Err. In old-format CSV, all error records are excluded from display. Each record's Delay is the difference from the Time of the preceding record (microseconds are truncated). Only the first record uses the First Delay setting as its Delay. |
| Event Trigger | Sets whether to use event trigger and its occurrence condition. For details, see "Event Trigger". |
LIN LogReplay Dir Setting
The transmission direction for normal frames is set here per ID, regardless of the original log's transmit / receive direction. With Tx, the master transmits both header and response; with Rx, the master transmits the header and waits for the slave response.
Figure 3 shows a dialog setting example with only ID 10 (0x10) changed to Rx. In this example, the dialog was closed with Cancel to discard the change, so the replay lists in Figures 2 and 4 remain Tx. Close with OK to apply changes.
Figure 3: Tx / Rx settings for each ID.
| Item | Description |
|---|---|
| Dir | Sets transmission frame type. Click "Tx" or "Rx" to change to that type. |
Button | Click to save transmission frame type changes and close dialog. |
Button | Click to discard transmission frame type changes and close dialog. |
Event Trigger
Sets whether to use an event trigger and the event conditions.
Figure 4 shows Key Trigger selected with modifier None and main key A. First Delay is 0 ms, Loop is OFF, and Dir is Tx for all three loaded rows.
Figure 4: Settings for waiting for Key Trigger to start replay.
| Item | Description | Notes |
|---|---|---|
| None | Event trigger is not used. | |
| Ext Trigger | Detects port input as event. | This feature is under development and cannot be used. |
| Log Trigger | Detects specified monitoring log as event. | |
| Key Trigger | Detects specified key input as event. |
Log Trigger Settings
With Log Trigger, replay starts after a matching log is detected during monitoring and First Delay elapses. Various conditions such as specific data and errors can be configured. Here, a normal Response for LIN ID 0x10 received on CH1-1 is the replay start condition.
Log Trigger Screen Description
- While monitoring is stopped, load a communication log in LogReplay for the Ch to use.
- Select Log Trigger under Event Trigger, then click the pencil Edit button below the condition display. Double-clicking the condition display also opens Trigger Setting : Log Trigger.
- As in Figure 5, set Ch 1, Inner Ch 1, Protocol LIN, Direction R, State OK, Type Response/Frm., ID 10 (0x10), and DL 2. Leave D1 and D2 as
**in this example without specifying data comparison values.
Figure 5: Editing Log Trigger conditions for starting replay.
- Click OK to finalize and check the condition display in Figure 6. Ch is 1 - 1, Protocol LIN, Dir R, State OK, Type Res/Frm, Format -, ID 10, DL 2, and D1 and D2
**. First Delay is 0 ms and Loop is OFF. - Start monitoring and wait for a matching received log. After detection and First Delay, replay follows the settings in the list.
In Figure 6, Dir R in the start condition is the matching direction for received logs, while Dir Tx in the replay list is the transmission direction during replay. Figures 5–7 show configuration while monitoring is stopped; no replay transmission is performed.
Figure 6: Finalized Log Trigger conditions and Edit button location.
| Screen item | Description |
|---|---|
| Event condition (condition display below Log Trigger) | Displays log information set as the event condition. Double-click this area to open Trigger Setting : Log Trigger and configure log information for the event condition. |
| Edit button (pencil below condition display) | Opens Trigger Setting : Log Trigger to configure log information for the event condition. |
For details on Trigger Setting, see Trigger Setting Dialog Screen Description.
Key Trigger
Key Trigger detects keyboard input as the replay start event. Configure modifier None + main key A as in Figure 4 as follows.
- While monitoring is stopped, load a communication log in LogReplay for the Ch to use.
- Select Key Trigger under Event Trigger.
- Open the main key selection list to the right of + and select A as in Figure 7.
- Set the sub key (modifier) to the left of + to None. Check that None + A matches Figure 4, and check First Delay and Loop.
- After starting monitoring, press A without a modifier. Once key input is detected, replay starts after First Delay elapses.
Figure 7: Selecting A from the main key list. See Figure 4 for the completed settings.
| Item | Description | Notes |
|---|---|---|
| Main key (right of +) | Sets the trigger key. Options: None, A, B, ..., Z, 0, 1, ..., 9, F1, F2, ..., F12, SPACE | If Main key is None, key events are not detected, so log data cannot be transmitted. |
| Sub key / modifier (left of +) | Sets the modifier to combine with the main key for the trigger. Options: None, Alt, Ctrl, Shift Select None when no modifier is used. | A modifier alone cannot trigger an event. |
button.
Button
Button
Button
Button