<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Troubleshooting on SensorRig — Real Raspberry Pi Sensor Monitoring</title>
    <link>https://sensorrig.com/tags/troubleshooting/</link>
    <description>Recent content in Troubleshooting on SensorRig — Real Raspberry Pi Sensor Monitoring</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 04 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://sensorrig.com/tags/troubleshooting/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>My DS18B20 Cable Was Fine and I Still Got 15 CRC Errors Per 1000 Reads</title>
      <link>https://sensorrig.com/posts/ds18b20-crc-errors-short-cable/</link>
      <pubDate>Tue, 04 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://sensorrig.com/posts/ds18b20-crc-errors-short-cable/</guid>
      <description>Search for DS18B20 CRC errors and you get one answer: your cable is too long, drop the pull-up to 2.2k. It is good advice and it is repeated everywhere, which is exactly why I want to write about the case where it does not apply.&#xA;My install is eight DS18B20 probes on a Raspberry Pi 4, wired with 3M 3811/10 ribbon, runs of 2-3 m, spec&amp;rsquo;d at roughly 45 pF/m. Standard 4.</description>
    </item>
  </channel>
</rss>
