Analysis function

Whether it’s sending, monitoring, or replaying messages, TSMaster enables you to simulate various commu-nication scenarios, allowing you to assess communication effectiveness and conduct in-depth analyses using real-world data replays.

Exploring the Potential of 8 Essential Analysis Functions

Message Transmission

Message Monitoring

Bus Statistics

Bus logging

Message Playback

Video Playback

Graphical Curves & Numerical Displays


  • Manual, shortcut key, and periodic message sending options.
  • Signal generator creates sine, square, triangle waves, and custom patterns.
  • Add custom messages or pull from the database.
  • Copy messages to C scripts for flexible sending.
  • Display absolute and relative time.
  • Choose between scrolling and fixed display modes.
  • Instantly view signal values with DBC parsing.
  • Show frame rate or message cycle.
  • Apply channel and ID filters.
  • Bold highlighting of changing message bytes.
Includes metrics like bus load rate, peak load rate, data frame rate, data frame count, error frame rate, error frame count, controller status, and transmit error count.

Experience comprehensive monitoring of CAN bus performance with detailed statistics, displayed conveniently in panels or graphs using system variables.
  • Default recording format is BLF, with the ability to convert to ASC or MAT formats later.
  • Options to automatically start recording to the hard disk upon analysis startup, eliminating the risk of oversight.
  • Choice for unlimited recording.
  • Automatic file splitting after recording 5 million messages or reaching 500MB per file.
  • Customizable naming rules, allowing inclusion of username, system time, startup time, project name, etc.
  • Supports BLF/ASC formats and offers online and offline playback options.
  • Offline playback functions similarly to direct opening, allowing for post-processing functions and playback range selection.
  • Supports common video formats like MP4, AVI, WMV, and more.
  • Can be linked to the bus playback engine.
  • Configure time offset for synchronized video and bus data analysis.
  • Flexible Y-axis configuration with support for multiple and separate display modes.
  • Precise data point display instead of fuzzy curve shapes.
  • X and Y-axis cursors for detailed data analysis.
  • Abundant shortcut keys for quick graphic attri-bute adjustments.
  • Load DBC, ARXML, LDF, XML databases.
  • Display database structure view, signal commu-nication matrix view, and message communica-tion matrix view.


There are various methods to send CAN messages, including:

  1. Manual sending
  2. Shortcut key sending
  3. Periodic sending
  4. Adding custom messages and retrieving sending messages from the database
  5. CAN RBS simulation sending
  6. C script sending, which includes:
    • Single-frame sending function
    • Periodic sending function
    • Sequence sending module

There are several methods for message filtering, including:

1. Message ID filtering
2. String filtering
3. Filter settings within measurements
4. Programmable filters

The issue with only one DBC file being loaded by default for all four CAN channels was due to the customer using the same database network name for each channel. This resulted in a conflict where the software could only load one DBC file associated with that network name.

The problem was successfully resolved by modifying the network names for each CAN channel. By assigning unique network names to each channel, the software was able to differentiate between the DBC files and load them correctly, allowing for the intended functionality with multiple DBC files for different CAN channels.

The maximum supported time is 255ms, and this limitation is by design due to hardware constraints.

The active sending of error frames is a feature related to LIN interference, and it is currently not supported

The verification algorithm in the node ECU contains an error, leading to a verification error when the schedule table is executed. This is an expected outcome. However, during single-frame message transmission, verification is intentionally not performed as part of the design, which is why no errors are triggered in that scenario.

Continuous FlexRay message errors and the inability to communicate normally may be attributed to channel configuration issues. To address this, it is advisable to follow these steps:

  1. Verify that there are at least two or more cold-start nodes within the network.

  2. Ensure that there are no conflicting messages being sent between nodes.

These are among the most frequent causes of communication failures reported by most customers.

There is a significant likelihood that this particular signal may require end-to-end (e2e) verification to ensure proper reception and functionality.

You can hold down the ‘shift’ or ‘ctrl’ key to select multiple signals and, while keeping the ‘shift’ or ‘ctrl’ key pressed, drag them to another graph window using the left mouse button.

Reason: The graph cannot display the entire message; it can only show signals.


  1. Add a custom signal to the graph.
  2. Input the message ID.
  3. Define the starting bit, length, amplification factor, etc., for the signal.
  4. analysis_Q10-1-1
  5. analysis_Q10-1-2

Yes. The bus playback window can replay CAN, CAN FD, LIN, FlexRay, and Automotive Ethernet messages from external log files in BLF file format. We provide both offline replay and online replay functions.

Scroll to Top
Apply for TSMaster Trial

Tosun offers a free, no-commitment 30-day trial of TSMaster. Complete the form below to get your free software download link!