Aerospace, Military & Defence Focus
arbiter of control over which data is allowed to leave the platform or control station. For instance, high-rate internal sensor data should not be permitted to automatically cross a constrained external link. In many cases, it should remain local. In other cases, it may need to be filtered or downsampled, or only routed under specific conditions.
The same principle applies to command and control traffic. Commands should not be broadcast broadly across necessary tactical links. They should only be routed to their intended destination with the correct delivery behaviour based on mission requirements.
This requires more than basic connectivity. It requires an architecture that can understand, route and govern data based on the content and purpose of the message itself. This is the role of a message router. A message router can serve as the top-level endpoint acting as the entry point for the platform, control station, or mission system. It will handle discovery across a fleet and determine which messages are allowed to cross a constrained link while enforcing routing policies that preserve network performance. It also helps to
ensure that command messages only reach their intended destination, enabling more precise data routing while conserving limited bandwidth.
Equally importantly, the message router can enforce unidirectional policies. For instance, platforms can receive targeted messages from controllers. Likewise, control stations can receive operational updates from specific platforms, preventing unnecessary peer-to-peer traffic from flooding the network. These rules would not be applied by coupling any specific platform to any other controller. Instead, they
should be applied based on the data itself and according to the mission state. This is the benefit of a data-centric approach: the ability to control data flow between systems by understanding its content, context, and intended use.
Accelerating the path to production
For unmanned systems programmes, the ability to scale is not just a future requirement. It is quickly becoming a production requirement. Programmes are moving beyond demonstrations of
individual platforms towards coordinated fleets, collaborative autonomy, distributed sensing and multi-domain mission execution. In that environment, data movement becomes one of the most important architectural decisions. The RTI ACT reference architecture was created to address this challenge. Built on the RTI Routing Service and Connext technologies, the ACT reference architecture provides a practical foundation for applying data-centric routing principles to unmanned systems. It provides development teams with a starting point for managing data flow, preserving constrained network resources and scaling command and control across distributed platforms. They can then customise the architecture to their own mission needs, reduce integration friction, and accelerate the path from prototype to deployment.
As unmanned systems continue to evolve from one-to-one control to many-to-many coordination, those that treat data control as a primary architectural requirement will be the ones that succeed.
https://www.rti.com/en/
PIC18-Q35: Processing Power Meets Programmable Logic Zero CPU Overhead, Maximum Flexibility
The PIC18-Q35 microcontroller family empowers you to design smarter, more efficient embedded systems by combining high-speed processing with advanced, on-chip programmable logic. The integrated Configurable Logic Block (CLB) with 128 Basic Logic Elements lets you create custom peripherals and timing functions, no external logic ICs required.
Free your CPU from real-time control and achieve true deterministic performance, even in the most demanding industrial, automotive and IoT applications.
microchip.com/pic18-q35
www.cieonline.co.uk
The Microchip name and logo and the Microchip logo are registered trademarks of Microchip Technology Incorporated in the U.S.A. and other countries. All other trademarks are the property of their registered owners. © 2026 Microchip Technology Inc. All rights reserved. MEC2649A-UK-05-26
Components in Electronics
September 2026 23
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
