This content is not available in your preferred language.

The content is shown in another available language. Your browser may include features that can help translate the text.

Troubleshooting XCP or CCP Master Custom Device in VeriStand™

Updated Jul 31, 2026

Reported In

Software

  • ECU Measurement and Calibration Toolkit
  • VeriStand Custom Devices
  • VeriStand

Issue Details

I am having problems using the XCP or CPP Master Custom Device in VeriStand to connect to my ECU or retrieve measurement data. The connection may fail, or measurement channels may not return values. I may also see error codes or connection status issues in the Workspace or UI Manager.

Solution

Ensure the Custom Device is configured correctly and follow a structured troubleshooting approach:

 

  1. Verify that the setup follows the procedure in Getting Started with CAN Calibration in VeriStand. Confirm that communication parameters match the ECU configuration.
  2. Open your VeriStand Workspace or UI Manager to retrieve Connection Status and Error Code values. Review the Error Log located in the same directory as the Protocol Log.
  3. Modify the Custom Device settings based on the reported error code.
    • Common error codes include:
      • -301007: Incorrect Communication Parameters
      • -301017: Insufficient Free DAQ Lists
      • -301020: Unsupported Signal Size
      • -301055: Invalid Event Channel
      • -301096: Timeout Error
      • -301075: Access Locked
      • -301109: Memory Overflown
      • -301147: Calibration Pages Not Found
    • Refer to the attached VeriStand_ECUMC_CD_TroubleshootingGuide(EN v1.5) document for detailed explanations and resolution steps for each error code.
  4. Analyze communication behavior when basic troubleshooting is insufficient
    • Enable and analyze the Protocol Log to inspect communication between the host and ECU.
    • Use the attached BusMonitorGuide document for guidance on performing low-level XCP/CCP communication analysis.
    • Use tools such as A2L Viewer or a text editor to inspect the A2L file.
  5. Validate A2L file usage
    • Ensure the A2L file contains correct communication parameters and channel definitions.
    • Use a reduced version of the A2L file when full access is not available.
    • Do not upload or share proprietary A2L files externally.

Additional Information

The attachment VeriStand_ECUMC_CD_TroubleshootingGuide(EN v1.5) includes further details on:

 

  • Connect Channel
  • Multiple Measurement Tasks
  • Static and Dynamic DAQ List
  • Optional Commands

 

The attachment BusMonitorGuide provides guidance on analyzing XCP/CCP communication at the bus level for advanced troubleshooting scenarios.