OSS + ELC EU 2026

Many spacecraft avionics and payload systems are already distributed embedded systems: onboard computers, payload controllers, sensors, and links must coordinate under strict reliability constraints. Aerospace has long used controlled onboard networks, from MIL-STD-1553 to Ethernet-based approaches such as TTEthernet. The next question is how open standards such as IEEE Time-Sensitive Networking (TSN) can work in open RTOS ecosystems such as Zephyr.

Based on my experience with TTEthernet, Zephyr, micro-ROS, and space OBC development, this talk asks what TSN on Zephyr should become. TSN is not one feature: traffic shaping, scheduled transmission, redundancy, policing, configuration, time synchronization, and hardware support all matter. Linux already has a mature TSN operations model around user-space tools such as tc and linuxptp. Zephyr has no Linux-style userland, so TSN needs Zephyr-native APIs, shell commands, samples, diagnostics, and management interfaces.

Attendees will learn why TSN matters for Zephyr, why Zephyr cannot simply copy Linux tooling, and what design questions remain for TSN-capable endpoints.