10.3. What’s New in 4.3.0¶
RTI Connext Micro 4.3.0 is an LTS release. See the Connext Releases page on the RTI website for more information on RTI’s software release model.
The following features are new since Connext Micro 4.2.0.
10.3.1. Build Connext Micro applications for MicroSAR platforms¶
This release adds support for MicroSAR platforms. Refer to MicroSAR Platforms for more details.
10.3.2. Generate AUTOSAR code with Micro Application Generator¶
This release adds several new features to Micro Application Generator (MAG) which, taken together, enable you to generate AUTOSAR applications from XML configuration files. Refer to Generating AUTOSAR Applications for a walkthrough of the process. These new features include:
10.3.2.1. DDS System XML model support¶
MAG now supports the DDS System XML schema flow for application generation, which extends the capabilities of the standard XML configuration model. Refer to Define your system in DDS system XML for details.
10.3.2.2. Deployment-targeted code generation¶
A new -deployment <name> command-line option lets you generate code
for a single deployment instance selected from a deployment scenario defined in
the XML. Refer to MAG Command-Line Options for more information.
10.3.2.3. Application type selection¶
A new -applicationType <type> option controls the structure and templates
used in code generation. Valid values are micro4, cert, and
autosar_cdd. Refer to MAG Command-Line Options for more
information.
Attention
Currently, only autosar_cdd is fully supported for deployment-based code
generation; see the Known Issues section. This type generates
AUTOSAR-compliant code structure, including adapter layer separation and
AUTOSAR resource configuration templates. Other application types may be
supported in future releases.
10.3.3. Speed up initialization on AUTOSAR systems with configurable thread safety¶
This release adds a new AUTOSAR port property, enable_thread_safe_heap,
that allows the application to control whether heap allocation is protected by
a mutex. When enabled,
OSAPI_Heap_allocate_buffer()
acquires and releases a mutex around memory allocation to ensure thread safety.
When disabled, the mutex is neither created nor used, reducing overhead in
single-threaded or non-preemptive environments.
10.3.4. Generate native applications with deployment-aware code generation¶
Attention
This is an experimental feature in Connext Micro 4.3.0. It is not guaranteed to be consistent or supported and should not be used in production.
Refer to Experimental Features for more information.
This release adds a new -deployment <name> command-line option to Micro
Application Generator that lets you generate code for a specific deployment
instance, selected from a deployment scenario defined in the XML. You can
generate code for native Connext Micro applications with the micro4 option, as
described in Generating native DDS applications with deployment-aware code generation.
10.3.5. Content filtering no longer experimental¶
Connext Micro 4.2.0 introduced the content filtering feature, enabling DataReaders to filter incoming sample data. Instructions for implementing this feature are provided in the Content Filtering section.
In release 4.2.0, this feature was experimental, but in release 4.3.0, content filtering is ready for production use.
10.3.6. Stabilized builtin DDS SQL Content Filter configuration¶
This release moves the configuration options for the builtin DDS SQL content
filter from the DDS_FilterResourceLimits to a new DDS_SqlFilterProperty.
See Content Filtering for how to configure the filter with this
new property.
10.3.7. Expanded SQL content filter capabilities and improved robustness¶
This release extends the syntax accepted by Connext Micro’s built-in SQL content filter and improves its robustness, including support in SQL filter expressions for nested struct field references with dotted notation and typedef alias resolution. The SQL parser and evaluator were also improved to better handle edge conditions relating to unsigned integers, malformed literals, and incompatible type comparisons. See Content Filtering for more details.
10.3.8. Reduce network and CPU usage with custom content filters¶
This release builds on the addition of DDS SQL filter support in Connext Micro 4.2.0 by allowing the use of custom content filters. Content filtering can be used to reduce network and CPU usage by only sending samples over the network which reader’s are interested in. See Content Filtering for details on how to use this feature.
10.3.9. Restart discovery after CPU suspension¶
This release adds the ability for a DomainParticipant to restart the discovery process during runtime. This feature allows your application to return to a known state after suspending and resuming a CPU, among other use cases. See Restarting Discovery for more information.
10.3.10. Prioritize data with the TRANSPORT_PRIORITY QoS policy¶
This release introduces support for the TRANSPORT_PRIORITY QoS policy in Connext Micro. This feature allows applications to assign priorities to outgoing network traffic so that the underlying operating system (OS) and network infrastructure can treat higher-priority messages preferentially.
When enabled, the transport priority value specified in the QoS policy is mapped to the network packet’s priority field, such as the IP Type of Service (TOS) or Differentiated Services Code Point (DSCP) field. This allows applications to influence packet scheduling and prioritization in the network stack, which can be useful for latency-sensitive data flows.
Connext Micro currently supports this feature on UDP transports. You can configure the mapping from DDS transport priority values to network packet priority through transport properties.
Note
The actual prioritization behavior depends on the operating system and network configuration. Connext Micro sets the packet priority value, but enforcement of traffic prioritization is handled by the OS networking stack and network infrastructure.
For more information on this feature, refer to the Transport Priority section.
10.3.11. Integrate rotating or on-demand credentials with Lightweight Security Plugin¶
This release introduces the passphrase tracker, a mechanism that enables runtime passphrase rotation for the Lightweight Security Plugin. Previously, the pre-shared key (PSK) passphrase was fixed at initialization time. With the passphrase tracker, applications can now update the active passphrase without restarting, allowing integration with key management workflows that rotate credentials on a schedule or on demand.
The passphrase tracker is designed around a pluggable provider model. Applications supply a provider implementation at configuration time, and the tracker automatically notifies the Lightweight Security Plugin whenever a new passphrase is available, re-deriving session keys transparently.
Connext Micro ships a reference implementation: the file passtracker, available in the
rti_me_psl PSL library. This implementation monitors a passphrase file on
the file system and propagates any changes to the Lightweight Security Plugin
automatically. The polling interval and startup behavior are configurable.
Note
The file passtracker is only available on POSIX and Windows systems. Applications targeting other platforms or requiring a different passphrase source can provide a custom PSL implementation through the passphrase tracker provider interface.
For more information, refer to the Lightweight Security Plugin section.
10.3.12. Reduced heap memory usage¶
This version of Connext Micro uses less dynamically allocated memory on average than the previous release. Refer to the RTI Connext Performance Benchmarks on RTI Community for more details.
10.3.13. Resume DDS traffic without restarting ECUs with socket recovery¶
This release adds automatic socket recovery support for AUTOSAR NoCom/FullCom transitions. When the TcpIp stack closes sockets during a NoCom event (e.g., network management, diagnostic session, or bus-off), Connext Micro now tracks affected receive sockets and automatically re-binds them when communication is restored (FullCom). This allows DDS traffic to resume without requiring an ECU restart.
See NoCom/FullCom socket recovery for more information. This feature is not available in CERT builds.
10.3.14. Default UDP transport name changed¶
Previously, Micro Application Generator (MAG) automatically appended an index
to the UDP transport name; this has been disabled by default. It can be
re-enabled by using the new command line parameter -incrementUdpName. The
default name for the UDP transport name has also been changed from udp to
udpv4. See Application Generation Using XML for more information.
10.3.15. Streamlined default MAG messages¶
Previously, running rtiddsmag without specifying verbosity
(-verbosity <number>) would default to info level, which prints informative
messages as well as warnings. This has been changed to warning level by
default. See MAG Command-Line Options for more information.
10.3.16. Reduced runtime memory usage of MAG-generated code¶
Starting with this release, all configuration structures generated by Micro
Application Generator are now const. This may reduce RAM usage significantly
if read-only sections are not loaded in memory and instead remain in NVRAM.
10.3.17. Third-party and open source software changes¶
The following third-party software used by Micro Application Generator has been upgraded:
Third-Party Software |
Old Version |
New Version |
|---|---|---|
Apache Log4j |
2.17.1 |
2.25.3 |
JAXB Runtime |
2.3.1 |
2.3.9 |
The following third-party software used by rtiddsgen has also been upgraded:
Third-Party Software |
Old Version |
New Version |
|---|---|---|
Apache Log4j |
2.17.1 |
2.25.3 |
For more information, see the Third-Party and Open Source Software section.