<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Telemetry on Inorderly.com</title>
    <link>https://inorderly.com/tags/telemetry/</link>
    <description>Recent content in Telemetry on Inorderly.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 18 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://inorderly.com/tags/telemetry/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Ordering Sensor Telemetry From Devices With Bad Clocks and Late Uploads</title>
      <link>https://inorderly.com/ordering-sensor-telemetry-from-devices-with-bad-clocks-and-late-uploads/</link>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://inorderly.com/ordering-sensor-telemetry-from-devices-with-bad-clocks-and-late-uploads/</guid>
      <description>&lt;p&gt;Sensors are the worst-behaved producers there are. Their clocks drift. Some sit behind a gateway that forwards readings in batches. Some lose their connection for a while, keep what they measured, and send it all at once when they&amp;rsquo;re back. A few readings just never arrive.&lt;/p&gt;&#xA;&lt;p&gt;This worked example has 200 devices sending a temperature reading every 10 seconds for three hours, 216,000 readings in all. Their clocks are up to 3 seconds out. Fifty of them sit behind five gateways that forward every 45 to 90 seconds. Twenty go offline for 2 to 12 minutes and ten for 25 to 40 minutes. 634 readings are lost on the way. Each reading carries its device&amp;rsquo;s sequence number. The readings are uploaded three times, with different network delays and gateway timing each time.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
