RTI Connext Integration Toolkit for AUTOSAR

RTI Connext Integration for AUTOSAR Classic

Introduction

RTI Connext Integration Toolkit for AUTOSAR Classic complements Connext Micro and Connext Cert with AUTOSAR-specific code generation. The toolkit enables automatic conversion of data type definitions across standard formats (OMG IDL, OMG DDS-XML and AUTOSAR ARXML) and generates C code for data conversion and marshaling between the RTE and DDS communication frameworks.

• Features

  
  
  

  • ARXML to DDS IDL conversion of AUTOSAR base, implementation, CompuMethod and union types
  • ARXML to DDS XML conversion of AUTOSAR base, implementation, CompuMethod and union types
  • DDS XML to ARXML conversion of AUTOSAR base, implementation, CompuMethod and union types
  • Code generation for run-time conversions between DDS and RTE C language type representations
  • Code generation for Complex Device Driver Runnables of marshaling routines between RTE provided and/or required PortPrototypes
  • Code generation of DDS configuration and RTE mapping module template

• Benefits

  RTI Connext Integration Toolkit for AUTOSAR Classic enhances the AUTOSAR Classic software architecture and methodology with DDS connectivity.

  This is made possible by allowing AUTOSAR ECU designers to define data types, port interfaces and Software Component (SW-C) interfaces using the AUTOSAR ECU design tools of their choice.

  Once the design is ready for DDS integration, users only need an ARXML export of relevant SW-C models in order for the Toolkit’s AUTOSAR Runtime Complex Device Driver Code Generator (rtiarcgen) to produce all the necessary artifacts:

  • DDS-compatible type declarations (in either DDS-IDL or DDS-XML formats)
  • Type conversion routines
  • Data marshaling routines matching the SW-C’s runnables
  • DDS middleware configuration/mappings module templates

  
  The Toolkit can be integrated into a repeatable and automated pipeline to support iterative development of the ECU, allowing DDS interoperability to grow along with ECU design evolution.

  The integration process is simple, scalable and efficient. The AUTOSAR Runtime CDD Code Generator can analyze your type catalog and produce optimized “zero-copy” marshaling routines for most AUTOSAR/DDS type combinations, saving execution time and code size.

RTI Connext Integration for AUTOSAR Adaptive

Introduction

RTI Connext Integration Toolkit for AUTOSAR Adaptive complements Connext Professional, Connext Micro and Connext Cert. It provides a code generator for application-specific DDS Network Binding assets plus a source library implementing the AUTOSAR Communications Management DDS Network Binding.

In this release, the Vector MICROSAR Adaptive integration is experimental. As an experimental release, interfaces and behavior are subject to change. A production-ready release of this component is expected in the future.

• Features

  • AUTOSAR Runtime Adaptive Code Generator
    • ARXML to DDS IDL conversion of AUTOSAR standard and custom types
    • ARXML to DDS XML conversion of AUTOSAR standard and custom types
    • DDS XML to ARXML conversion of AUTOSAR standard and custom types
    • Code generation for run-time conversions between C DDS and C++ Adaptive Platform type representations
    • Code generation for Common, Skeleton, Proxy and DDS-specific C++ assets
    • Code generation of DDS Network Binding deployment configuration files
      
      
  • AUTOSAR DDS Network Binding Library (requires Code Generator described above)
    • Service Instance Discovery
    • Event (incl. zero-copy), Method, Field and Trigger-based Communication
    • Service Availability
      
      
  • AUTOSAR DDS Network Binding for Vector MICROSAR Adaptive (requires Code Generator and Library described above)
    • Service Instance Discovery
    • Event-based (incl. zero-copy) Communication
    • Service Availability

• Benefits

  RTI Connext Integration Toolkit for AUTOSAR Adaptive extends the AUTOSAR Adaptive software architecture and methodology with standards-based DDS connectivity.

  This is made possible by allowing AUTOSAR ECU designers to define data types, service interfaces and their deployment using the AUTOSAR ECU design tools of their choice.

  Once the design is ready for DDS integration, users only need an ARXML export of relevant Executable declarations in order for the Toolkit’s AUTOSAR Runtime Adaptive Code Generator to produce all the necessary artifacts:

  • DDS-compatible type and interface declarations (in either DDS-IDL or DDS-XML formats)
  • Type conversion routines
  • DDS Network Binding integration and deployment assets

  
  This is an iterative, incremental process that can be repeated and even automated as the ECU design grows, allowing DDS interoperability to grow along with ECU design evolution.

  The integration process is simple, scalable and efficient. The AUTOSAR Runtime Adaptive Code Generator can analyze your data type catalog and produce optimized “zero-copy” marshaling routines for most AUTOSAR/DDS type combinations, saving execution time and code size.

  Once application-specific DDS artifacts are generated, these can be used in combination with AUTOSAR DDS Network Binding Library in two ways:

  • Standalone: the user’s C++ application directly calls the AUTOSAR DDS Network Binding Library ara::com-like APIs
  • Integrated: the user’s AUTOSAR Adaptive Application indirectly calls the AUTOSAR DDS Network Binding Library through its supported ara::com stack of choice (e.g. using the DDS Network Binding for Vector MICROSAR Adaptive described above)

Additional Information

• Details

  Intent: AUTOSAR Classic and AUTOSAR Adaptive Platforms interoperability

  Feedback: Contact support@rti.com 

  Product Version Information: 3.1 (Classic Platform) / 3.1 (Adaptive Platform)

  Platform Support: Windows 10 (or higher), MacOS and Linux

  Product components compatibility:

  • Classic Platform: Connext Micro 2.4.14.2,
  • Adaptive Platform: Connext Pro 7.3.0 Connext Micro 2.4.14.2, Connext Cert 2.4.15.1

  
  Where can I find it: Connext Integration Toolkit for AUTOSAR can be found in Connext Drive 3.1 installation directory.

  Documentation: Connext Integration Toolkit for AUTOSAR Documentation is located in the Connext Drive 3.1 installation directory. You can also browse it here.

• Next Steps

  To start working with Connext Integration Toolkit for AUTOSAR refer to the documentation in our community portal.

  Join the RTI Community.

  Post your questions, search through our Knowledge Base, and get the most from your DDS experience by joining the RTI Community!