JP1 Remotes

seiko wrote:wonder if the site would benefit from a learned output file generated by omni-remote for the palm?

I don't remember if I've ever tried to decode those files. I probably can make another try now anyway.

It probably would help if you did one device per file (assuming you have a choice) and got some devices with very different protocols, and of course identified the expected contents (by choosing devices that we can find signals for elsewhere or knowing the UEI setup code or compatible JP1 upgrade).

Hmmm let's see if I understand:

It's a little hellish without having the users guide for the reciever...

By appearances the original INRC-42 remote appears to only control the 4200 sat receiver. So if this is what you mean by only one device, it's a safe bet that you will see only one device in whatever I post as a data file.

There is a sat/tv toggle, but I believe all it does is toggle the sat receiver to pass through any cable and off-air signals through the box. Interestingly enough the remote does not feature a power on/off key, ao again, I'm guessing that the sat/tv toggle serves this purpose. The receiver display goes black when toggled between sat/tv. A reasonable assumption in absense of hard copy.


I'll give it a whirl...

BTW OmniRemote does offer a utility to convert ccf>>omniremote. Food for thought?

johnsfine wrote:

seiko wrote:wonder if the site would benefit from a learned output file generated by omni-remote for the palm?

I don't remember if I've ever tried to decode those files. I probably can make another try now anyway.

It probably would help if you did one device per file (assuming you have a choice) and got some devices with very different protocols, and of course identified the expected contents (by choosing devices that we can find signals for elsewhere or knowing the UEI setup code or compatible JP1 upgrade).

What John means is this.

Step 1: Learn the signals from your 4200 remote using the Omni and save it as the first file.

Step 2: Learn the signals from some other remote and save that as the second file. This second file will be a "control" file so you should use a signal that we're very familiar with. I would recommend that you learn the signals from your Maestro, just tell us what setup code you are learning from.

Ok. Thanks for clearing me up on that. Will do. And I guess uploading to Diag is the right place?

The Robman wrote:What John means is this.

Step 1: Learn the signals from your 4200 remote using the Omni and save it as the first file.

Step 2: Learn the signals from some other remote and save that as the second file. This second file will be a "control" file so you should use a signal that we're very familiar with. I would recommend that you learn the signals from your Maestro, just tell us what setup code you are learning from.

johnsfine wrote:

seiko wrote:wonder if the site would benefit from a learned output file generated by omni-remote for the palm?

I don't remember if I've ever tried to decode those files. I probably can make another try now anyway

If you start with post 12 in this thread, there are links to some other framents of information that will probably help you out.

This is the best info I found from Dave Houston:

The first octet is carrier frequency * 2. For example, 00012EA6 is 77478/2 = 38769KHz carrier.

The remaining octets are a bitmap of the signal with each bit representing a sample at 1/5 the carrier frequency. IOW, each bit represents 5 cycles of carrier. A 1-bit represents carrier present, a 0-bit repesents no carrier.

If the first octet is 00004856, it's an RF file and each bit represents ~550µS.