Feature: Embedded design
Many systems are increasingly being designed to operate as edge devices within larger cyber-physical setups
not limited to EtherCAT, OPC-UA, CAN bus, I2 C, RS485, local
wireless connections such as Bluetooth, and more. Furthermore, as end user demands continue to intensify and
Meeting modern embedded design
challenges head-on
By Jonathan Hacker, Chief Technology Officer, TeleCANesis
T
he world is increasingly connected. More robust and faster communications are required in many applications that include intelligent condition monitors, machine controllers, AGVs and robots in industrial applications, smart systems in medical applications, and various systems in
automotive applications. Design complexities imposed by this greater connectivity
include better determination of data flows between diverse subsystems, and seamless communication between different technologies, protocols and interfaces that may include but are
38 December 2025/January 2026
www.electronicsworld.co.uk
organisations pursue digital transformation, many systems are increasingly being designed to operate as edge devices within larger cyber-physical setups. Tey are required to filter and process data, enact time critical decisions, and interact with other edge devices and services in cloud hosting applications – such as analytics, machine learning, digital twins and over-the-air (OTA) updates. As a result, connectivity technologies that need to be supported include Ethernet and cellular, whilst communicating via protocols commonly used in the IoT world, like MQTT and ZeroMQ. As these connectivity trends continue, the role of embedded
systems is changing: they are increasingly becoming distributed, multi-interface systems that present complex and time- consuming engineering challenges for development teams. At the system architect level, tasks like defining data flows have become significantly more complicated and demanding and there is an even greater need for careful connectivity orchestration so that robustness and reliability are guaranteed. At the soſtware engineering level, working out the details of
interface initialisation on the target platform now involves time consuming, laborious and repetitive efforts. For example, if signals need to be moved from CAN or a fieldbus to an endpoint such as an HMI display or cloud telemetry gateway, this will require complex connection, routing and translation. Such tasks are increasingly difficult to manage using conventional approaches that oſten involve writing tens or hundreds of thousands of lines of boilerplate and basic plumbing code. To meet these challenges head on, engineers require access
to increasingly powerful tools that can help them to simplify soſtware provisioning so that time to market can be shortened and development costs reduced. As the complexity of distributed, multi-interface systems
continues to grow, it has become ever more important to have tools to hand that can save hours of soſtware engineering time while cutting down on expenditure levels for initial development as well as on future projects.
Automated code generation Against the backdrop of established techniques and tools no longer being sufficient for tackling these challenges, TeleCANesis has created a configurable runtime core supported by tools
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
