CAN Frame Not Transmitting With NI Vehicle Communications Toolkit, NI-XNET Error 0xBFF6309F In VCOM Online Core Log

Updated Jun 19, 2026

Reported In

Software

  • Vehicle Communication Toolkit
  • VeriStand

Issue Details

I am using the NI Vehicle Communications Toolkit 2025 Q3 with the VCOM Toolkit custom device in VeriStand 2025 Q3. When I deploy my VeriStand project, one specific CAN frame is not transmitted on the CAN bus.  I do not see any error in the status channels from the VCOM Toolkit custom device, and other CAN frames are transmitting correctly.
 
 
When checking the Online Core log, I see the following error message from NI-XNET:
 
 
Error: CANNIXnetDevice_CAN1 (Code: 0): Error in NI-XNET interface: error getting session state (NI-XNET: (Hex 0xBFF6309F) The length of the payload written is larger than the maximum payload size allowed.)

Solution

This behavior is typically caused by a mismatch between the CAN frame type and its configured payload size. Standard CAN frames support a maximum payload of 8 bytes, while CAN FD frames support payloads larger than 8 bytes.
 
To resolve the issue, complete the following steps:
 
  1. Inspect the AUTOSAR database file (.arxml)
    • Locate the CAN frame definition associated with the non-transmitting signal.
    • Identify the configured payload size.
  2. Verify the frame format
    • Confirm whether the frame is defined as standard CAN or CAN FD.
    • If the payload size exceeds 8 bytes, the frame must not be configured as standard CAN.
  3. Update the frame configuration
    • Change the frame type from standard CAN to CAN FD if the payload is larger than 8 bytes.
  4. Re-import or update the database in VeriStand
    • Reload the updated .arxml file in the NI Vehicle Communications Toolkit configuration.
  5. Redeploy the VeriStand project
    • Deploy the system again and monitor the CAN bus.
 
After making this change, the CAN frame should transmit successfully on the bus.