Automotive RTI Connext Drive architecture
Shared memory transports Memory-mapped network interfaces Intra-process communication
Thriving towards compliance On top of mapping type systems and APIs in a performant way, the automotive product focus of AUTOSAR brings an additional
challenge: functional safety compliance.
Implementation type instances may be stack or heap-allocated directly by the application, which causes the internal type implementation to use AUTOSAR’s in-memory PSM types. When passed to the underlying framework, these data types must be converted and/or serialized according to the required target data format (i.e., DDS auto- generated types from DDS-IDL or DDS-XML) When seeking zero-copy transfers,
applications may also leverage the standard Allocate() method provided by events and fi eld notifi ers. In this case, the network binding will, whenever possible, ask the underlying framework to “loan” an internally allocated data sample that will, in turn, be “returned” when fi lled and sent back by the application The latter is an extremely powerful mechanism, allowing size-independent constant-time transfers in several scenarios:
Assessment of any DDS implementation as a Safety Element out of Context (SEooC) in any ISO-26262 ASIL level is a challenge in itself, which RTI is already successfully addressing in its Connext Drive line of products. Given the nature and expense of functional safety assessments, trading functionality for codebase size and footprint can be a strategic necessity.
Such constraints inform RTI’s ara::com design choices and future AUTOSAR standard directions: C is the one and only DDS language PSM allowed in the implementation of
DDS Network Bindings, thus allowing easy adaptability for DDS implementations of many varieties (small footprint, safety-aware) Multi-binding support is a must, as certainly more than one DDS Network Binding will need to be provided in order to support the aforementioned variety of DDS implementations A leaner approach to service discovery and binding features in the AUTOSAR Adaptive DDS Network Binding specifi cation, using common DDS features (topics, instances) that are easier to fi nd in most DDS middleware implementations As RTI‘s involvement in AUTOSAR Adaptive now goes beyond standards publishing, it includes the specification, maintenance and further development of the DDS network binding that enables AUTOSAR Adaptive applications to interoperate with existing and future DDS systems. The goal is to enable easy setup and operation in any environment, as well as flexibility for all types of network bindings, and thus also to be independent of AUTOSAR third-party vendors.
https://www.rti.com/industries/automotive
• TFT, LCD, OLED, & E-Paper Technologies • Available in many sizes • Customisable brightness & interface options • Customisable coverglass to meet protection needs
• Customisable PCAP & RTP touch panels *Midas touch panels are ISO standard, including ISO 13485 for medical devices
Displays For Medical
Applications
sales@midasdisplays.com
www.cieonline.co.uk. +44(0)1493 602602
midasdisplays.com Components in Electronics May 2023 29
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56 |
Page 57 |
Page 58 |
Page 59 |
Page 60 |
Page 61 |
Page 62 |
Page 63 |
Page 64 |
Page 65 |
Page 66
