What is the most robust/reliable IR format for transmission? #1278
-
Hello folks, I'm creating two pieces of hardware. One is a transmitter and one a receiver. They are ESP32S3 based, 240Mhz with 8MB of SDRAM. The transmitter is a custom chip and the receiver is a Seeed Studio XIAO ESP32S3. The Arduino-IRremote library will be used on both the sender and receiver, so I can choose the format to be used. The transmitter operates via gyroscope/accelerometer, like a wand, so it's being waved around a bunch. The receiver is likely to be placed about 5 to 10 feet away. Because sending a command is going to take some time to input since it's done by the accelerometer rather than a single button push, I want to ensure the transmission is received because it's going to be frustrating to repeat if the command does not get received. So I think what I'm looking for is a format that:
NEC is obviously the most widely used protocol, but is it the most robust and reliable for such a situation? I'm curious what others would recommend in a situation where they get to choose the protocol. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
Answering my own question from my research: With this library, the FAST Protocol looks like it would be the best bet because:
These factors would make FAST a well-suited protocol for my application. Unfortunately, I need TWO receivers in my application, pointed in opposite directions that receive different signals. This library is not capable of multiple receivers with separate signals (only multiple receivers with a shared signal), so the whole question is moot; since I can't use this library at all. Other than using multiple Arduinos (which I don't want to do for maintenance purposes), I'm switching to using a separate dedicated decoder chip which uses exclusively NEC. These are fairly rare, but these are available choices:
That said, I learned a lot using this library and although I won't be able to use it, I appreciate the vast resources that have gone into creating and maintaining it; including its expansive examples, support for different protocols, and wide device support. Thank you for the work on this project! |
Beta Was this translation helpful? Give feedback.
Answering my own question from my research:
With this library, the FAST Protocol looks like it would be the best bet because:
These factors would make FAST a well-suited protocol for my application.
Unfortunately, I need TWO receivers in my application, pointed in opposite directions that receive different signals. This li…