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

RTI CAN MultiMessage Blockset

For combining dSPACE systems with CAN communication networks

The RTI CAN MultiMessage 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.

Application Areas

The RTI CAN MultiMessage 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. 

Configuration of CAN Interfaces

Working with large hardware-in-the-loop (HIL) systems means working with a considerable volume of CAN messages. Moreover, test environments and database container (DBC, FIBEX, AUTOSAR) files change frequently during the development process. CAN configuration updates in large models and parameter changes can be done with just a few clicks.

Parameters and Messages

Parameters can be accessed directly in ControlDesk and AutomationDesk via user trace files. The Bus Navigator is also supported for easy handling of CAN configurations, including messages and signal manipulation in ControlDesk. Numerous test cases can be created via flexible manipulation at the message and signal levels. The current value of the signals in messages can be defined. Messages can be transmitted spontaneously (kick-out) and can also be enabled. They can also be transferred directly between two CAN buses, unidirectionally or bidirectionally, via the Gateway block, without message or signal manipulation. The message transmission and signal manipulation option can be changed during run time.

Benefits

The strong point of the RTI CAN Multi Message Blockset is handling complex CAN setups, especially in hardware-in-the-loop applications. You can control, configure, and manipulate a very high number of CAN messages from one single Simulink® block. Not only does handling become very straightforward, but the size of the model files is also reduced. This cuts code generation time and build time. CAN descriptions can easily be read in from communication matrix description files such as database container files (DBC), ASAM-MCD2D (FIBEX), AUTOSAR System Template files or ARXML files. CAN, J1939 formats and also the CAN FD (Flexible Data Rate) protocol with a much higher data rate and an extended payload data length are supported as well. These functions make the RTI CAN MultiMessage Blockset a time-efficient and cost-effective solution for managing complex CAN setups.

Functionality Description
General
  • Database-file-oriented Simulink blockset for combining dSPACE systems with CAN communication networks and for configuring these CAN networks
  • Managing a very high number of messages from one Simulink block
  • Supports ControlDesk Bus Navigator
  • Support of CAN FD (ISO and Non-ISO)
  • Support of partial networking
  • Supports dynamic changes in communication behavior such as signal manipulations and error simulation/detection
Initialization and configuration
  • Importing database files
  • Configuring baud rate, sample mode, bit timing parameters, termination resistors, etc.
  • Supports DBC, FIBEX and AUTOSAR files1)
  • User-defined database support via custom parser
  • Multiple database file support allowing simultaneous use of several database files for one model
  • Supports multiple database file variants that can be switched between during run time
Signal and message handling
  • Multiple, fast, and ECU-dependent selection of transmit and receive messages
  • Trigger reactions for sending messages as result events for a received message
  • Message composition read-only (given by database file)
  • All transmit (TX) messages are received automatically (loop-back) for transmit confirmation
  • Gateway block to transfer messages between two CAN buses unidirectionally or bidirectionally, without message or signal manipulation
  • Message transfer between two CAN buses configurable during run time (gateway)
  • Direct switch from gateway signal to other sources such as counters
  • Various options for manipulating signals and messages
  • Providing all messages, signals, and status information via Simulink bus for easy access everywhere in the model
  • Block outputs for time stamp information: receive time, transmit time, delta time, delay time
  • Internal scheduler to support different cycle times of messages and CAN-compliant scheduling by priority and bus load. Automatic handling of bus load to avoid turnaround time peaks
  • Different sample times and tasks only for complete bus configurations
  • No support of remote/request messages
  • No interrupt handling (e.g., received interrupts)
  • Custom CRC functionality
  • Internal parity calculation
  • Internal counter
  • Internal toggle Custom Code functionality to manipulate raw data or signals
  • Raw data as input to or output from Simulink
  • Raw data manipulation from within experiment software (AutomationDesk, ControlDesk)
  • Configuration of database-independent (“free”) raw messages
  • Capture messages: receiving messages in a given filter range as a stream to Simulink
  • Changing CAN signals from experiment software for special signal behaviors such as different counter or signal values for a defined number of transmissions
  • Changing CAN messages during run time
  • Dynamic message triggering: global enabling, spontaneous transmission (kick-out), cyclic message activation, etc.
  • Message definitions including IDs and lengths changeable at run time
Interrupts
  • No interrupts supported
  • Supports trigger reactions
J1939 support
  • J1939 support in RTI CAN MultiMessage Blockset
  • Support of the J1939 DBC Format
  • Support of J1939 Network Management (Address Claim)
  • Support of J1939 Broadcast Announce Messages (BAM)
  • Support of J1939 Request to Send/Clear to Send (RTS/CTS)
  • For more information, please contact dSPACE
NEW: Support of new AUTOSAR functions2)
  • Support of container IPDUs
  • Support of end-to-end protection
  • Support of secure onboard communication
  • Support of global time synchronization
  • For more information, please contact dSPACE
1) Please contact dSPACE for appropriate version.

2) In combination with SCALEXIO systems.

More Information Related Topics Contact Information