CAN Vendor

R2026b

CAN hardware vendor for XCP on CAN external mode communication

Since R2026b

Model Configuration Pane: Hardware Implementation / Hardware board settings / Target hardware resources / Groups / Host-board connection

Description

Select the CAN hardware vendor for the host-side CAN interface used during XCP on CAN external mode communication. The available vendors are determined by querying the CAN hardware interfaces connected to the host computer using the canChannelList (Vehicle Network Toolbox) function.

The CAN vendor, along with the CAN Device and CAN Channel parameters, identifies the specific CAN hardware interface on the host computer that communicates with the Arduino board during external mode simulation.

Note

  • A Vehicle Network Toolbox™ license is required to use XCP on CAN external mode with Simulink® as the host interface.

  • Virtual CAN devices are filtered from the list. Only physical CAN hardware connected to the host computer appears.

Dependencies

To enable this parameter:

  1. Set Hardware board to one of these boards:

    • Arduino® Due

    • Arduino Uno R4 Wi-Fi®

    • Arduino Uno R4 Minima

    • Arduino Nano R4

    • Teensy 4.0 (Arduino compatible)

    • Teensy 4.1 (Arduino compatible)

  2. Set Communication interface to XCP on CAN.

  3. Set Host interface to Simulink.

Settings

first available vendor (default) | dynamically populated from connected CAN hardware

Select the CAN hardware vendor from the drop-down list. The list is dynamically populated based on the physical CAN hardware interfaces connected to the host computer.

Supported Vendors

These CAN hardware vendors are supported:

  • Vector

  • Kvaser

  • PEAK-System

Recommended Settings

No recommendation.

Programmatic Use

No programmatic use is available.

Version History

Introduced in R2026b

See Also

| | | (Vehicle Network Toolbox) | | | | |