https://blanpa.github.io/tags/io-link/Recent content in IO-Link on blanpaHugo -- gohugo.ioenblanpa@pm.me (blanpa)blanpa@pm.me (blanpa)© 2026 blanpaFri, 04 Sep 2026 00:00:00 +0000https://blanpa.github.io/projects/iolink-suite/Fri, 04 Sep 2026 00:00:00 +0000blanpa@pm.me (blanpa)https://blanpa.github.io/projects/iolink-suite/<h2 class="relative group">The Problem <div id="the-problem" class="anchor"></div> <span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"> <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#the-problem" aria-label="Anchor">#</a> </span> </h2> <p>IO-Link is the last metre of the shop floor: the sensor on the cylinder, the valve on the manifold, the pressure switch on the line. An IO-Link master hands that data to Node-RED as raw bytes — <code>092B0929</code> — and leaves the rest to you. Which bits are the temperature, whether a raw <code>2347</code> means 23.47 °C, what a parameter at ISDU index 100 is called: all of that is written down in the device&rsquo;s IODD, an XML file every vendor publishes and hardly any integration reads. The usual result is a flow full of hand-typed bit offsets and scaling factors that silently breaks when a sensor is swapped for the next revision.</p>