<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Esp32 on SensorRig — Real Raspberry Pi Sensor Monitoring</title><link>https://sensorrig.com/tags/esp32/</link><description>Recent content in Esp32 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/esp32/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></channel></rss>