For combining dSPACE systems with CAN communication networks
- Ideal for handling complex CAN setups, especially in hardware-in-the-loop applications
- Convenient configuration of CAN setups
- Database file import
- CAN raw data access
- Managing a very high number of messages from one Simulink® block
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. The RTI CAN MultiMessage Blockset and the RTI CAN Blockset differ with regard to their features and application areas (rapid control prototyping / hardware-in-the-loop simulation).
The strong point of the RTI CAN MultiMessage 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 configurations can easily be read in from communication matrix description files such as database container (DBC) files. The RTI CAN MultiMessage Blockset is a time-efficient and cost-efficient solution for managing complex CAN setups.
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) 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 directly accessed in ControlDesk® and AutomationDesk® via user trace files. The CAN 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 on message and signal level. The current value of the signals in messages can be defined. Messages can be transmitted spontaneously (kick-out) and can also be enabled. In addition, they can 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.