I hope MakeHex (and changing the frequency) solves it for you. But those new samples make me less confident that it will.
Those are pretty consistent at the higher frequency. I don't expect NG Protos to be that consistent when learning frequency incorrectly.
I think your issue may have more to do with the process of relaying IR through RF than with the signals themselves. I don't know enough about either your physical setup or the Pronto NG RF system to give you much help with that. Hopefully you can get another expert interested.
On general principles of IR/RF relay, the first thing I would investigate is whether there is a second (or more) path for the signal to ultimately reach the device as IR. Any time there are two paths there is the possibility for them to interfere with each other. If I understand correctly (don't bet on it) the NG Pronto itself sends either IR or RF but not both together, so the common (in other IR/RF remotes) two path problem (direct IR from remote and IR via RF) shouldn't be an issue. But do you have multiple emitters or other ways to get two path issues?
The other big issue is emitter placement. Are you really sure you know the spot on the device where it receives IR? Even knowing that, is the emmiter too strong or too weak? Does it need to be further away or does it need to be aimed better or what?
On 08/29/05 11:09 ET, oferpeleg said...
As i said before it's clearly not an IR emitter
problem (replaced IR emitters,switched places
and etc)
Maybe you know a lot more about emitter issues than I do. But I don't see how the above statement could be valid. There are so many ways in which a problem like thos could be an emitter problem, and the testing gives you such poor information about which direction thing are flawed in. I think you never know it wasn't an emitter problem until you solve whatever it actually was.