<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hc12 on SensorRig — Real Raspberry Pi Sensor Monitoring</title><link>https://sensorrig.com/tags/hc12/</link><description>Recent content in Hc12 on SensorRig — Real Raspberry Pi Sensor Monitoring</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 18 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://sensorrig.com/tags/hc12/index.xml" rel="self" type="application/rss+xml"/><item><title>HC-12 Packet Loss and Retry Protocol</title><link>https://sensorrig.com/posts/hc12-packet-loss-retry-protocol/</link><pubDate>Tue, 18 Aug 2026 00:00:00 +0000</pubDate><guid>https://sensorrig.com/posts/hc12-packet-loss-retry-protocol/</guid><description>The problem The HC-12 module is marketed as a wireless serial link. You wire it to a UART, set the same baud rate on both ends, and bytes flow. That framing works perfectly — until a byte is corrupted or a channel glitch drops a transmission entirely. There is no CRC at the module level, no retry, no acknowledgement, and no way to tell from the receiving UART alone whether the data that arrived is intact.</description></item><item><title>ESP32-C3 Deep Sleep Current: What the Datasheet Doesn't Tell You About Your Dev Board</title><link>https://sensorrig.com/posts/esp32c3-deep-sleep-current-real-measurement/</link><pubDate>Sun, 16 Aug 2026 00:00:00 +0000</pubDate><guid>https://sensorrig.com/posts/esp32c3-deep-sleep-current-real-measurement/</guid><description>The ESP32-C3 datasheet specifies a deep-sleep current of approximately 5–7 µA with the RTC timer on (ESP32-C3 Technical Reference Manual, Section 3.5.3). On my Seeed Studio XIAO ESP32C3, that number is useless. My node is part of a 100-yard shed link running off a 12 V solar panel and a tractor battery, connected to the house over an HC-12 433 MHz serial radio, and the XIAO&amp;rsquo;s on-board components keep the MCU from ever approaching the silicon floor.</description></item><item><title>HC-12 vs WiFi for Remote Sensor Nodes: What 433 MHz Actually Buys You</title><link>https://sensorrig.com/posts/hc12-vs-wifi-remote-sensor-nodes/</link><pubDate>Mon, 03 Aug 2026 00:00:00 +0000</pubDate><guid>https://sensorrig.com/posts/hc12-vs-wifi-remote-sensor-nodes/</guid><description>Every home-monitoring tutorial assumes WiFi reaches your sensor. Mine didn&amp;rsquo;t — and for my shed node, it fundamentally couldn&amp;rsquo;t. The shed sits about 100 yards (~90 m) from the house, runs off-grid on a 12 V solar panel, and its only buffer is the tractor battery wired in for charging only. There is no grid power, no ethernet, and no convenient place to put an access point halfway between.
For a node like that, &amp;ldquo;just use WiFi&amp;rdquo; collapses immediately: a WiFi board at that distance needs either an outdoor AP and a PoE run (a whole infrastructure project for one sensor), or it simply won&amp;rsquo;t hold a link.</description></item></channel></rss>