<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Foxborne: field notes on failure</title>
    <link>https://foxborne.com/blog</link>
    <atom:link href="https://foxborne.com/blog/rss.xml" rel="self" type="application/rss+xml" />
    <description>Source-level write-ups for reliability and flight test engineers.</description>
    <language>en-us</language>
    <item>
      <title>Boot time, wall time, arrival time: one incident, three clocks</title>
      <link>https://foxborne.com/blog/three-clocks</link>
      <guid isPermaLink="true">https://foxborne.com/blog/three-clocks</guid>
      <pubDate>Sat, 26 Sep 2026 12:00:00 GMT</pubDate>
      <category>Time and clocks</category>
      <description>A PX4 flight log counts from boot, the companion journal keeps wall time and the ground station logs arrival. Give each an explicit error bound, and you know which events you can put in order and which you cannot.</description>
    </item>
    <item>
      <title>Reading an OOM kill in a journalctl export</title>
      <link>https://foxborne.com/blog/reading-an-oom-kill</link>
      <guid isPermaLink="true">https://foxborne.com/blog/reading-an-oom-kill</guid>
      <pubDate>Sat, 26 Sep 2026 12:00:00 GMT</pubDate>
      <category>Companion computers</category>
      <description>The kernel’s out-of-memory report names the thread that asked, the process it killed and every page it counted. systemd then records the unit’s result, and two settings decide what happens next.</description>
    </item>
    <item>
      <title>When BindsTo= takes your MAVLink router down with it</title>
      <link>https://foxborne.com/blog/bindsto-mavlink-router</link>
      <guid isPermaLink="true">https://foxborne.com/blog/bindsto-mavlink-router</guid>
      <pubDate>Sat, 26 Sep 2026 12:00:00 GMT</pubDate>
      <category>Companion computers</category>
      <description>A dependency in the unit graph can silence telemetry with no radio fault at all. Here is how to spot one in the journal, and how to prove it on the bench before anyone swaps a radio.</description>
    </item>
    <item>
      <title>A telemetry gap is not a radio failure</title>
      <link>https://foxborne.com/blog/telemetry-gap-not-radio</link>
      <guid isPermaLink="true">https://foxborne.com/blog/telemetry-gap-not-radio</guid>
      <pubDate>Sat, 26 Sep 2026 12:00:00 GMT</pubDate>
      <category>Ground links</category>
      <description>A hole in the ground receive log proves only that nothing arrived. A stopped router, a radio that left the USB bus and a berm all look the same there, and other logs tell them apart.</description>
    </item>
    <item>
      <title>CUI on page one: what 32 CFR 2002 and DoDI 5200.48 ask of an engineering report</title>
      <link>https://foxborne.com/blog/cui-on-page-one</link>
      <guid isPermaLink="true">https://foxborne.com/blog/cui-on-page-one</guid>
      <pubDate>Sat, 26 Sep 2026 12:00:00 GMT</pubDate>
      <category>CUI and handling</category>
      <description>The government-wide rule asks for the same banner on every page and a designation indicator on the first. DoD practice prints plain CUI at top and bottom and moves the codes and a point of contact into a five-line block.</description>
    </item>
    <item>
      <title>IRIG 106 for people who live in PX4 logs</title>
      <link>https://foxborne.com/blog/irig-106-for-px4-people</link>
      <guid isPermaLink="true">https://foxborne.com/blog/irig-106-for-px4-people</guid>
      <pubDate>Sat, 26 Sep 2026 12:00:00 GMT</pubDate>
      <category>Flight test</category>
      <description>A range recorder stamps every packet with a 48-bit counter that ticks at 10 MHz, and it records absolute time as a channel of its own. If you can put a ULog on UTC, you already know the method.</description>
    </item>
    <item>
      <title>At jet speed, clock error is distance</title>
      <link>https://foxborne.com/blog/jet-speed-clock-error</link>
      <guid isPermaLink="true">https://foxborne.com/blog/jet-speed-clock-error</guid>
      <pubDate>Sat, 26 Sep 2026 12:00:00 GMT</pubDate>
      <category>Flight test</category>
      <description>At 170 m/s, a ±40 ms clock bound is ±6.8 m of track; on a quad it is ±0.48 m. Draw it along the track, and you can see when a log cannot say which side of a line an event fell on.</description>
    </item>
    <item>
      <title>Why PX4’s 10-second link-loss failsafe fires late</title>
      <link>https://foxborne.com/blog/px4-link-loss-timer</link>
      <guid isPermaLink="true">https://foxborne.com/blog/px4-link-loss-timer</guid>
      <pubDate>Sat, 26 Sep 2026 12:00:00 GMT</pubDate>
      <category>PX4 internals</category>
      <description>COM_DL_LOSS_T does not start at the last heartbeat. It starts at the last status report that still carried it, which on a real vehicle adds one and a half to almost four seconds.</description>
    </item>
  </channel>
</rss>
