RTMaps Interface Blockset

Enabling full-stack prototyping across multisensor applications and hard real-time controllers

The dSPACE RTMaps Interface Blockset for Simulink® enables a bidirectional and low-latency UDP/IP communication between RTMaps from Intempora and dSPACE real-time systems or the PC-based simulation platform dSPACE VEOS.

Application Areas

The conventional vehicle software stack is at its limits, as hard real-time controller-based prototyping is no longer sufficient for advanced driving assistance systems and autonomous driving (ADAS/AD). As a result, two prototyping worlds arose, where one is dedicated for perception and data fusion, and the other is aimed at hard real-time execution.

Typically, data processing and fusion algorithms are implemented in a high-level programming language such as C++, while the development of application functions rests on the model-based design approach using MATLAB®/Simulink® and dSPACE real-time systems. RTMaps from Intempora is an established tool with an unparalleled performance for prototyping C++-based multisensor applications by using block diagrams. In addition, RTMaps provides capabilities to precisely time-stamp, record and play back data.

The dSPACE RTMaps Interface Blockset connects dSPACE platforms, such as dSPACE real-time systems, or VEOS with RTMaps via UDP/IP. 

Key Benefits

The dSPACE RTMaps Interface Blockset provides a bidirectional, low-latency communication via UDP/IP between RTMaps from Intempora and dSPACE real-time systems or the PC-based simulation platform dSPACE VEOS. In just a few steps, developers can connect their applications in Simulink to the appropriate communication blocks via signal buses and establish data connections to multisensor applications in RTMaps. The required description of the data to be transmitted or received is generated as an XML file from the corresponding signal buses in Simulink at the push of a button. In addition, the blockset allows the clock in RTMaps to be synchronized with the simulation time or the real-time clock on dSPACE platforms. This makes it possible, for example, to capture, record, and precisely time-correlate vehicle bus data on dSPACE MicroAutoBox and camera data in RTMaps. A further use case is the open-loop (data replay) test of ECUs for image processing. In this use case, RTMaps on a PC serves to play back time-correlated video and bus data, while the bus signals are sent to a hardware-in-the-loop (HIL) system. This ensures a low-jitter restbus simulation.

The RTMaps Interface Blockset establishes a powerful connection between RTMaps and dSPACE platforms and facilitates the development and testing of perception and application algorithms for ADAS and automated driving. 

Functionality Description
General
  • Low-latency communication between RTMaps from Intempora and dSPACE platforms via UDP/IP
  • Simulink blocks for encoding/decoding data from Simulink buses into byte streams and vice versa
  • High-level communication protocol with clock synchronization regarding simulation time or (with MicroAutoBox) the real-time clock
  • Detection of packet losses and data corruption by means of counter and checksum mechanisms
Ethernet communication
  • Blockset for TCP/IP- and UDP/IP-based communication with MicroAutoBox
  • Up to 16 sockets or connections with combined sending and receiving queues
  • Multi-rate modeling and data pockets of variable length

  • RTMaps Interface Blockset Product Information, PDF, English, 937 KB
Contact Information

혁신을 추진하세요. 항상 기술 개발의 동향을 주시해야 합니다.

저희 전문 지식 서비스에 가입하세요. dSPACE의 성공적인 프로젝트 사례를 확인해 보세요. 시뮬레이션 및 검증에 대한 최신 정보를 받아보세요. 지금 바로 dSPACE 다이렉트(뉴스레터)를 구독하세요.

Enable form call

At this point, an input form from Click Dimensions is integrated. This enables us to process your newsletter subscription. The form is currently hidden due to your privacy settings for our website.

External input form

By activating the input form, you consent to personal data being transmitted to Click Dimensions within the EU, in the USA, Canada or Australia. More on this in our privacy policy.