BUSMASTER E2E: Verify received frames and troubleshoot
Start by identifying where the expected behavior stops. Check whether BUSMASTER transmitted, whether the peer received the frame, and whether the peer accepted its E2E settings.
1. Check the right view
Section titled “1. Check the right view”| View | What it shows |
|---|---|
| Transmit list, Data Bytes and Signal Details | Transmit settings and the application template. |
| Message Window Tx record | Local transmit observation. |
| Rx on a separate wired interface or device | ID, frame type, length, payload and order received by the peer. |
| E2E diagnostic log | Algorithm, configuration, protection and submission results. |
| ECU E2E Check | Whether the ECU accepts a frame under its communication specification. |
In overwrite mode, a new frame with the same ID can replace the displayed row. Use an append view or a CAN log to compare a sequence of frames.
2. Find the E2E diagnostic log
Section titled “2. Find the E2E diagnostic log”Use the log layout for the running BUSMASTER Build. The 3.2.2.51 (Build 571) used in these exercises writes separate module logs. On builds with the unified layout, look for source=E2E in BusMustSupport.log. See Collect support logs and submit feedback for the location, older file names and archives to collect.
Copy the files after reproducing the problem. A normal exit can add the closing summary. Use the diagnostic log for algorithm, configuration, protection, submission and state information. For frame-by-frame checks, include the CAN capture and received payloads from the same time range.
3. Read the relevant fields
Section titled “3. Read the relevant fields”| Field | Use |
|---|---|
process_id, session_id, operation_id |
Identify the process, session and operation. |
item, channel, message_id |
Match the log to a transmit row, logical channel and CAN ID. |
stage, result, code |
Locate the first failing stage, such as DLL resolution, protection or submission. |
accepted, rejected, outcome_unknown |
Interpret local submission status. Verify peer reception separately. |
first_counter, last_counter, next_counter |
Compare the counter sequence after reset, resume or reconnect. |
logger_queue_drops |
A value above zero indicates missing diagnostic entries. Keep the log and use a CAN capture for exact frame counts. |
4. Troubleshoot by symptom
Section titled “4. Troubleshoot by symptom”| Symptom | What to check or do |
|---|---|
| E2E or Dynamic Message is missing | Check the BUSMASTER version and open the CAN transmit window. Find the manager next to Database on the CAN ribbon. |
| Algorithm settings are hidden | Select the correct row and open its E2E tab, or widen the window to see it alongside Signal Details. |
| E2E parameters and Reset are disabled | If CAN is connected and the row is periodic, clear Repetition or disconnect CAN before editing. |
| CRC or counter remains static in the editor | The editor shows the application template. Inspect actual Tx/Rx or the CAN log. |
| An edit is rejected | Check the restored value, selected profile, length, header offset, field widths and overlaps. Correct the parameters before sending. |
| Send becomes unavailable after Esc | Check CAN connection state. Esc disconnects CAN in the main window. |
| CRC differs despite matching DataID | Compare mode, counter, application bytes, length and layout. |
| The first P02 counter is 1 | This is the default. Set 0 explicitly if required by the peer. |
| Changes in the manager do not reach an existing row | Reselect the algorithm in that row and verify the copied settings. |
| An existing row still uses a removed algorithm | The row retains its copy. Change its Dynamic Message setting to change the processing. |
| DLL not found or load fails | Check the path, architecture, file and dependencies. Use the log to locate the failing stage. |
| Connected but no Rx | Verify channel mapping, bit rates, wiring, termination, filters and peer state. Establish ordinary CAN communication first. |
| Too many periodic frames | Check other enabled rows and additional manual sends. Compare the per-row task against the receiver capture. |
| Counter restarts on reopening | CFX stores configuration. Runtime Context and counter progress are initialized from that configuration. |
5. Send information to technical support
Section titled “5. Send information to technical support”Include the exact BUSMASTER version and Build, analyzer model and channel setup, CFX and DBC, plus the external DLL version and parameters if applicable. Identify the row by CAN ID and include the frame type, length, profile, DataID or list, first counter and field positions. Provide short reproduction steps, timestamp, expected and actual results, the E2E support log and any archives for your build, the CAN capture or full payloads, and screenshots of relevant settings or messages.
Previous: Periodic transmission and saving · Series overview
Use the download center for current and archived BUSMASTER releases.