<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>ir on toorun.dev</title><link>https://toorun.dev/tags/ir/</link><description>Recent content in ir on toorun.dev</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sun, 11 Oct 2026 09:00:00 +0000</lastBuildDate><atom:link href="https://toorun.dev/tags/ir/index.xml" rel="self" type="application/rss+xml"/><item><title>TV Remote Control Protocols Explained: IR, RC5, RC6, NEC, CEC, and Practical API Examples</title><link>https://toorun.dev/posts/tv-remote-control-protocols-explained-ir-rc5-rc6-nec-cec-api/</link><pubDate>Sun, 11 Oct 2026 09:00:00 +0000</pubDate><guid>https://toorun.dev/posts/tv-remote-control-protocols-explained-ir-rc5-rc6-nec-cec-api/</guid><description>TV Remote Control Protocols Explained: IR, RC5, RC6, NEC, CEC, and Practical API Examples Remote controls are one of the simplest and most practical embedded communication examples. A TV remote may look trivial, but behind it are real protocol choices, timing constraints, carrier frequencies, and command encodings. If you want to build a DIY infrared controller, an IR blaster, or a home automation bridge, you need to understand the difference between raw IR, standard IR protocols, and HDMI-based control systems like CEC.</description></item></channel></rss>