For a better experience on dSPACE.com, enable JavaScript in your browser. Thank you!

RTI CAN Blockset

For combining dSPACE systems with CAN communication networks

The RTI CAN Blockset is especially suited for developing and testing control functions that communicate via a CAN bus system.

Application Areas

The RTI CAN Blockset is an extension for Real-Time Interface and can be used for combining dSPACE systems with CAN communication networks and for configuring these CAN networks. The RTI CAN Blockset and the RTI CAN MultiMessage Blockset differ with regard to their features and application areas (rapid control prototyping/hardware-in-the-loop simulation).

Benefits

The RTI CAN Blockset is especially suited for developing and testing control functions that communicate via a CAN bus system. To set up a message with the RTI CAN Blockset, simply choose the appropriate block from the CAN block library and connect it to your Simulink model. Configuration information such as the baud rate, identifier, message length, and interrupts can be entered in dialogs.

The blockset’s multiple support allows simultaneous use of several DBC files for one model, so the DBC file variants are easier to handle and can be switched during run time. With the blockset, CAN raw data can be accessed directly from within Simulink. This means that, using the raw data, protocols can be created on the Simulink model level.

Functionality Description
General
  • Message-oriented Simulink blockset for combining dSPACE systems with CAN communication networks and for configuring these CAN networks
  • One Simulink block for each functionality/each message
Initialization and configuration
  • Importing database files (see below)
  • Configuring baud rate, sample mode, bit timing parameters, termination resistors, etc.
  • DBC file support
  • User-defined database support via custom parser
  • Multiple DBC file support allowing simultaneous use of several DBC files for one model
Signal and message handling
  • Dialog-based setup of receive, transmit, request and remote messages (for example, format, identifier, signal composition, and encoding/decoding)
  • Loop-back functionality: CAN messages sent by one CAN controller can be made available to the same CAN controller
  • Gateway block to transfer messages between two CAN buses unidirectionally or bidirectionally, without message or signal manipulation (not applicable to DS1103)
  • Displaying status information on CAN controller
  • Various options for manipulating signals and messages n Multiple message access: The same CAN messages can be sent and received from within different model subsystems
  • Block outputs for time stamp information: receive time, transmit time, delta time, delay time
  • Different sample times and tasks for different messages (each message represented by its own block)
  • Custom encoding and decoding for the generation (TX) and verification (RX) of checksums and parity bits
  • Raw data manipulation directly from Simulink
  • User-defined messages with signal representation n Manipulating CAN signals at model design
  • Fixed message cycle time
Interrupts
  • Supported interrupts: receive, transmit, request and remote messages, bus off

Related Topics