<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Real-Time on Hugo POUSSEUR</title><link>https://www.blog-test.pouceheure.fr/tags/real-time/</link><description>Recent content in Real-Time on Hugo POUSSEUR</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 12 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.blog-test.pouceheure.fr/tags/real-time/index.xml" rel="self" type="application/rss+xml"/><item><title>Xenomai: What It Is and How It Differs from Other Real-Time OSes</title><link>https://www.blog-test.pouceheure.fr/blog/xenomai-real-time/</link><pubDate>Thu, 12 Nov 2026 00:00:00 +0000</pubDate><guid>https://www.blog-test.pouceheure.fr/blog/xenomai-real-time/</guid><description>You write a control loop that must run every millisecond. On a standard Linux, it works most of the time, then once in a while one iteration arrives 5 ms late because the kernel was busy with something else. On a desk it does not matter. On a robot or an EtherCAT bus, it is a fault.
Many solutions exist to fix this, and they do not fix the same problem.</description></item><item><title>EtherCAT in Four Steps: Understanding Its State Machine</title><link>https://www.blog-test.pouceheure.fr/blog/ethercat-state-machine/</link><pubDate>Mon, 09 Nov 2026 00:00:00 +0000</pubDate><guid>https://www.blog-test.pouceheure.fr/blog/ethercat-state-machine/</guid><description>You plug a new EtherCAT drive into the network, start your master, and the device stays in PRE-OP. Or it reaches SAFE-OP and falls back with an error code. Or it is in OP and the motor does nothing.
These three situations come from the same mechanism: the EtherCAT State Machine (ESM). Every device, called a slave in the specification, goes through four states, and each one unlocks a precise set of features.</description></item></channel></rss>