Pour la documentation en FRANÇAIS, utilisez l’outil de traduction de votre navigateur Chrome, Edge ou Safari. Voir un exemple.

Quick Nav

Have a question or need help? 

email Get in touch


Solution

OPAL-RT offers an integrated CAN solution using a standard KVaser 4 Channel PCie card allowing your real time simulator to interface with any peripheral CAN Device. CAN-FD (Flexible Data) is also supported. The driver is inherent to RTLAB and has an easy to use interface that allows you to add, define, and manipulate Channels, buses and messages. Furthermore, there is a built in recording feature allowing the user to capture data throughout the simulation. If the user has already defined a CAN bus architecture, this can also be imported onto the driver using the CANdb Import tool which supports .dbc and ARXML files. Channel and message data points would be made available to connect to your model via OpInputs and OpOutput blocks. The CAN driver gets initialized once the simulation is loaded onto the target.

Furthermore CAN is supported on the NI Platform via a range of cards or modules that are offered. Using the NI-XNET driver allows the user to communicate with external CAN devices in real-time. FIBEX (Fieldbus Exchange Format) or .dbc files can also be imported to setup the CAN architecture.

For the CANopen protocol on the RTLAB platform, a GATEWAY solution is required. The gateway is provided by Anybus X-gateway CANopen, makes it possible to communicate with peripheral CANopen devices. The way it is implemented, is that the OPAL-RT simulator communicates with the gateway using the ModBus Protocol over an ethernet cable. The Anybus gateway will output the CANopen signal over a DB9 connector.

CAN is robust protocol used in the automotive industry to allow microcontroller devices to talk with a master/host device. It's a messaged based protocol meaning, i.e. the slave device will translate the message into some form of action. The messages are also sent sequentially throughout the whole CAN bus. The CAN bus is seen as the whole architecture where the master and the slave devices are connected.


Platform Compatibility



Product Selection Guide

RT-LAB

The RT-LAB CAN Driver requires a CAN bus interface kit to be added to the Real-Time Simulator. The OP3411 kit includes a Kvaser CAN PCIe card and a software license, which support up to 4 CAN channels. For additional CAN channels, additional kits may be added if PCIe slots are available.

TypeProduct Number(s)OptionalDescription

Supported Simulators 

Additional Requirement(s)

OP4510-seriesOP5600-seriesOP5700-seriesOP5000-series

Software/Add-on module

OP3411-4510


CAN bus Interface Kit, KVASER PCIe CAN for OP4510

* OP3414 -  RT-LAB Driver included: License for 4 channels





Requires open PCIe slot. Note OP4510 only has one.

Software/Add-on module

OP3411-5600


CAN bus Interface Kit, KVASER PCIe CAN for OP5600

* OP3414 -  RT-LAB Driver included: License for 4 channels




Requires open PCIe slot.

Software/Add-on module

OP3411-5707


CAN bus Interface Kit, KVASER PCIe CAN for OP5707, OP5030, OP6200V2

* OP3414 -  RT-LAB Driver included: License for 4 channels



Requires open PCIe slot.

External Hardware

AB7308

ANYBUS AB7308 Gateway for CANopen. Contact OPAL-RT for more information.

Requires an OP3411 kit.

NI VeriStand

When using NI PXIe hardware, the PXIe8510 module supporting 2 to 6 ports is required along with the NI VeriStand Full Development System.

TypeProduct NumbersDescription
PXIe ModulePXIe8510 (784122-01 or 784121-01)2 or 6 port multi protocol interface module
Software780590-35NI VeriStand Full Development System
  • No labels