BUSMASTER XCP: Troubleshoot connection, acquisition and communication
Applies to BUSMASTER 3.2.2.50. Screenshots use the Chinese interface.
9. Start troubleshooting from the relevant state
Section titled “9. Start troubleshooting from the relevant state”| Symptom | Check first | Next step |
|---|---|---|
| A2L is loaded but there are no live values | CAN and XCP ECU are each connected; target rows are selected for Read Now | Connect CAN and the XCP ECU, complete a single read, then start continuous acquisition. |
| XCP connection times out | ECU/simulator readiness, physical wiring, matching 500 kbit/s, standard frames and 0x555 / 0x556 | Check channels and termination at both ends. Confirm that the two endpoints use different physical channels and that other programs are not occupying them. Use the real ECU’s own parameters. |
| An object is unsupported or has no address | Object properties, type, conversion, address and current MODULE | Check the address, type, conversion and MODULE in object properties. MissingAddress has no ECU address; start with EngineSpeed and SpeedLimit. |
| Dynamic DAQ fails to start | ECU Dynamic DAQ support and the selected event channel | Check Log / Diagnostics at the bottom of the main window. The simulator uses event 3. Correct the event using the ECU definition, or use polling to check basic reading. |
| Values update but curves are not visible | XCP physical-value elements have been added, samples exist, and the axis range contains the data | Use Auto Range first. Select Follow Latest to follow the newest time while running; inspect the historical interval after stopping. |
| Values become stale after stopping | Measurement has stopped or the connection is disconnected | This indicates cache freshness. Reconnect and read or acquire to obtain new values. |
| Export or Configure is disabled | The main CAN connection is still connected | Stop acquisition, disconnect XCP, then disconnect main CAN and export the retained buffer. |
| A communication timeout is followed by a desynchronization message | Current diagnostics and commands with no confirmed result | Disconnect XCP, disconnect and reconnect main CAN, then establish the XCP session again. Read the actual value of an unconfirmed calibration write first. |
| XCP times out after CAN transmit-task changes | CAN tasks were added, removed or edited while XCP was acquiring or waiting for a response | Stop acquisition and disconnect XCP before adjusting CAN transmit tasks, then reconnect XCP when finished. If communication is already desynchronized, disconnect and reconnect main CAN before establishing the XCP session. |
After this tutorial, you should be able to identify the correct ECU connection, read current values in the correct units, relate continuous acquisition to the curves, and save data and settings separately using CSV and CFX.
Further reading: XCP main window reference and XCP operations reference.
For further troubleshooting, save the A2L import message, XCP settings and CAN capture for the same time range. Use Collect support logs and submit feedback to find the A2L diagnostics for your build.
Series overview · Previous: CSV export and project storage
Use the download center for current and archived BUSMASTER releases.