Skip to main content
Version: Ver.4.10

Burst Transmission

This page describes modes for continuous transmission of frames or logs. Applying definitions from Catalog to transmission slots is a separate operation; see the Send Frame procedure.

Burst transmission creates a high-load state on the CAN bus by transmitting messages continuously without waiting between them.
Use burst transmission to evaluate transmission and reception under high CAN bus loads.

Usage Example​

Burst transmission provides the following two modes:

  • 1Frame Mode: Burst transmission of a single frame
  • Log Mode: Burst transmission using a log file

1Frame Mode​

Use:Burst 1Frame

In 1Frame Mode, a single frame is transmitted continuously without waiting between transmissions.
The CAN bus load can approach 100%, allowing you to evaluate whether the target ECU can transmit and receive under high bus loads.
You can specify any CAN ID and Payload for the frame transmitted in 1Frame Mode.

Log Mode​

Use:Burst Log

In Log Mode, normal data frames and remote frames loaded from a log file are transmitted continuously without waiting between them. By preparing transmitted frames in the log file to match the frames received by the target ECU, you can evaluate continuous frame reception processing.

Up to 3 million eligible records can be loaded. If this limit is exceeded, a limit-exceeded message appears, and up to 3 million eligible records are loaded from the start of the file.


Basic Operations​

The following procedure explains how to use burst transmission. This example uses burst transmission of a single frame.

  1. Select BurstTransmit in Simulation Window
    Select Simulation Window from the menu or toolbar.
    Select BurstTransmit for Simulation Mode in Simulation Window to display the burst transmission settings.
    Burst transmission is now available.
BurstTransmit
  1. Verify that 1 Frame Mode is selected
    Verify that the 1 Frame Mode radio button is selected.
    By default, the settings continuously transmit a CAN FD frame with CAN ID 000 and DLC 64byte.
BurstTransmit 1 Frame Mode settings
  1. Start Monitoring

After configuring burst transmission, start monitoring to execute burst transmission.
Start monitoring by selecting Command → Start from the menu bar, clicking the GUI Start button on the toolbar, or pressing F5. Frames are then transmitted.

GUI Start

BurstTransmit Reference​

BurstTransmit
ModeItemDescription
1 Frame ModeprotocolSelect CAN or CAN FD. Select from the following drop-down options.
Std./ExtSelect a standard ID (Std) or extended ID (Ext).
IDSpecify the CAN ID in Hex.
TypeSelect a data (Data) or remote (Remote) frame.
Available only when Protocol is set to CAN. This field cannot be edited when CAN-FD is selected.
DLCSpecify the DLC. Select from the following drop-down options.
- When Protocol is CAN: 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15
- When Protocol is CAN-FD: 0,1,2,3,4,5,6,7,8,12,16,20,24,32,48,64
Data Set buttonSpecify the frame data. Click Set to open the Data Setting dialog.
Bit Rate SwitchAvailable when a CAN FD frame is selected.
- Checked: Use the baud rate configured in Device Window for the CAN FD data phase.
- Unchecked: Do not use the CAN FD data-phase baud rate configured in Device Window. Use the arbitration-phase baud rate throughout the frame.
Stop buttonClick to stop burst transmission.
Log ModeLog FileDisplays the path and name of the log file to load.
SelectFile button buttonClick to open the file selection dialog and select the log file to load.
Note: Selecting a file does not load it. Click Load to read the data. (Note 1)
Load buttonLoads the log file.
LoopSelect whether to repeat log replay transmission.
If unchecked, transmission enters the waiting state after all log data has been transmitted.
OffsetSpecify the time from the start of monitoring to the start of log replay transmission.
When an event trigger is configured, this specifies the time from event detection to the start of log replay transmission. (Note 2)
Stop buttonClick during log replay transmission to stop it.
Log data displayDisplays the contents of the loaded log file. (Note 3)

Note 1: Supported legacy MicroPecker Analyzer CSV files can also be loaded. For the legacy format, normal CAN frames are included and error records are excluded.
Note 2: Up/down buttons buttons can also increase or decrease the value in increments of 1 or 0.1.
Note 3: In the loaded log file, data frames and remote frames are included, and error records are ignored.

Event Trigger Settings​

You can configure burst transmission to start when an event trigger condition is detected.

BurstTransmit event trigger settings
ItemDescription
Delay TimeSpecify the delay from event detection to the start of burst transmission.
NoneNo event trigger is used.
Receive TriggerDetects reception of a CAN frame with the specified CAN ID as an event.
Receive Trigger(CAN-FD)Detects reception of a CAN FD frame with the specified CAN ID as an event.
Ext TriggerDetects a port input as an event. (Note 1)
Log TriggerDetects the specified monitoring log as an event.
Key TriggerDetects the specified key input as an event.

Note 1: Ext Trigger is under development and is not available.

Receive Trigger / Receive Trigger(CAN-FD) Settings​

Select Receive Trigger to specify the CAN ID of received frames to detect as events.
For example, you can transmit a frame when a particular CAN ID is received.

Selecting Receive Trigger displays its settings area. Specify the CAN ID of received frames to use as the event trigger.

Receive Trigger Format, ID, and Type settings
ItemDescription
FormatSelect a standard ID (Std) or extended ID (Ext).
IDSpecify the CAN ID to use as the trigger.
TypeSelect a data (Data) or remote (Remote) frame. Available for CAN frames only.

Log Trigger Settings​

Select Log Trigger to specify the log to detect as an event.
Log Trigger supports detailed trigger conditions, such as specific data values and error frames.

Log Trigger condition display and edit button

For Log Trigger, click the Edit button button to open the Log Trigger settings dialog. Then click Data Setting to open the Data Setting dialog.

Log Trigger Reference​

Log Trigger condition display and edit button
ControlDescription
Settings displayDisplays the log information used as the trigger. Double-click to open the Log Trigger settings dialog.
Edit button buttonClick to open the Log Trigger settings dialog.
Log Trigger Settings Dialog Reference​

Specify the log conditions to detect as a trigger.

Trigger Setting : Log Trigger dialog
ItemDescriptionSettings
ChCH to use as the trigger (MicroPeckerX unit)Select from the following drop-down options.
ALL / 1 / 2 / 3 / 4
InnerChCH to use as the trigger (internal MicroPeckerX CH)Select from the following drop-down options.
ALL / 1 / 2
DirectionSpecify received/transmitted framesR: Received frames / T: Transmitted frames / R or T: Both received and transmitted frames
StateSpecify normal or error framesSelect from the following drop-down options.
OK / NG
TypeSpecify the target 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 selectionSelect a standard (Std.) or extended (Ext.) CAN ID.
The CAN ID is displayed in Hex. Enter an asterisk (*) to ignore the CAN ID when matching.
DLCCAN data lengthEnter an asterisk (*) to ignore DLC when matching.
Data Setting buttonOpen the Data Setting dialog-
Data areaData areaDisplays the data specified in the Data Setting dialog.
Data Setting Dialog Reference​

Click Data Setting in the Log Trigger settings dialog to open the Data Setting dialog.
Specify data conditions for the logs to detect as triggers. Use the tabs to switch between Hex (hexadecimal) and Binary (binary) notation. This dialog configures log matching conditions and is separate from Frame Data - Text Edit, which edits the bytes to transmit.

Data Setting for editing log matching conditions
ItemDescriptionDetails
IDCAN IDThe CAN ID cannot be edited in Data Setting.
DLCData lengthThe byte entry fields and Editor data area change according to the DLC setting.
Enter an asterisk (*) to ignore DLC when matching.
Hex / BinaryDisplay format tabsSwitch the data display between Hex and Binary.
Byte entry fieldsData entry area for individual bytes (Note 1)Each cell holds one byte of data. The upper-left cell is Data1.
Enter an asterisk (*) to ignore that data when matching.
EditorEditor area (Note 1)Enter individual bytes separated by commas.
Enter an asterisk (*) to ignore that data when matching.
Settings can be saved to and loaded from a CSV file.
Load button buttonLoad a Data Setting settings fileLoads a CSV file saved in Data Setting.
Save button buttonSave a Data Setting settings fileSaves Data Setting settings to a CSV file. The settings in the Editor are saved.

Note 1: You can edit data in either the byte entry fields or the Editor. Both displays stay synchronized.

Key Trigger Settings​

Select Key Trigger to detect keyboard input as an event.
For example, you can configure frame transmission in response to a key press.

Key Trigger modifier and main key settings
ItemDescriptionDetails
Right-hand selection fieldMain key settingSpecify the key to use as the trigger.
Available keys: 0–9, A–Z, F1–F12, SPACE
Left-hand selection fieldModifier key settingSpecify a modifier key to combine with the main key.
Available keys: Shift, Ctrl, Alt