On November 9, 2014 at 17:00, Rondon said...
I was able to isolate the problem. When my receiver is RF controlled, the commands are not executed even if the IR emitters do light up when signal is sent and received. I created a "directional key" page that I jump to when I use the net functions. It works only if Im in direct line of sight sending IR signals to my device instead of RF.
I know now the problem seems to be lodged somewhere in my RMF 350. Not sure what
You should never have your device sending IR/RF at the same time. I can't understand how URC didn't root that out of being an option when they upgraded the stand alones to CCP. For each device in your system, you should choose one type of signal or the other, not both. That is guaranteed to be a problem.
While the IR signal should, in theory, reach the device before the RF translated to IR signal does (through the base station and emitter), the emitter usrually sits directly ontop of the IR receiver of the device. So it can partially block some of the IR only signal from reaching the device, then BAM! ms later, it is blasted with a code through the IR emmiter. Maybe it's circuitry inside starts to recognize part of the IR only code because of whatever surfaced through the emitter, then ignores the IR signal from the emitter that it could receive fully. Or maybe some crazy variation of that. Perhaps your device doesn't go IR blind properly after receiving a command and that second burst confuses it more.
I'm confused just thinking about it. Best practice: ONE type of signal or the other.
