JP1 Remotes

Early on, when I couldn't get any of my JP1 remotes to learn the signals, I contacted customer support for Venturer.
Methinks there might be a lack of Engrish ranguage skills at the place.
They said I shouldn't have been able to control the box with another remote.
MWUHAHAHA!


"I am sorry but the ...

Why, oh why, didn't they set up the receivers to have the 2nd tuner be IR or UHF, depending?
Because IR doesn't work through walls and in most cases the 2nd tuner will be running a TV in a separate distance room in the house.

Dishnet's solution for a person like you is a HD DVR

I was willing to ...

I found an old post by KenL on PlanetReplay that discussed using "MakeLearned" for creating a custom Dish .RID file. Using MakeLearned to generate Pronto Hex into RIDGEN, I was able to get a working Venturer .RID file.

The MakeLearned documentation wasn't clear as to whether EFCs or OBCs should be ...

Usually I do a lot more online research before I make such a decision, but the bundle savings of $40/month got me excited.

I jumped from cable to Dish, thinking I could control one 322 receiver with 2 Replay units. BUZZZ!!!! The 2nd tuner in the receiver is UHF-controlled only. :evil: I could get ...

It's New Year's Eve and you're monitoring the forum?

Dude, that's dedication.
If you're still living in the Chicago area, you have about 5 minutes.
Rock in the New Year and forgot about my troubles for while!

I tried that RID file and no luck.

Using this RM file:
http://www.hifi-remote.com/forums/dload.php?action=file&file_id=6054

RIDGen is ignoring the subdevice code, 187.
It has no effect on the output HEX file and when I open the generated .rid file, the subdevice code is missing.

The OBCs and EFCs all match up in the saved file, but ...

Now that the JP1 portion has been completed, I'm starting a new thread in the ReplayTV section.
Robman: Please feel free to move this thread to the "CLOSED" area.

RIDGen is ignoring the subdevice code, 187.
It has no effect on the output HEX file and when I open the .rid file, the subdevice code is ...

Now to dig back into the .rid brewing!

Also quite rusty....

Success!

"Signal" was OBC 152.

Now a complete RMDU for someone else to use.

mdavej had all the numbers needed to make a .rid file, but I figured while I was at it, I might as well flesh out the RMDU for anyone else getting the Venturer for the February change.

http://www.hifi-remote.com/forums ...

I found a correction to "CC" in your file.
It should be OBC 140.

Still working on "signal" code.....

Had one of these in my closet. Man those learns were a b***h! I think they're right, but you'll need to check them all, as some still weren't clean and others were guesses. HERE it is.

Great and so close!!!

It didn't like OBC 138 for "0" at first, then it did. :?

Still struggling with signal ...

Second learn of "0" was 37558 frequency.

Grrr..

OK, IR got the learned-learned signal decoded.
NEC1, Device 66, Sub-device 187

Some of the buttons have strange data, but that's probably from OEM -> Harmony -> JP1 learning
("0" is showing a 37735 frequency, no protocol)
Select and Info are NEC1, device 1.

OK, maybe it's been too long and I've forgotten something, but IR should be showing me the learned codes from the RCU810.
It's showing nothing but the raw data.

Someone kick me in the right direction.

Thanks.

<EDIT>
Scratch that.
It wasn't seeing the RDF files, even though it wasn't telling me it ...

No luck with fresh batts, press length, or distance.

I got a killer deal on a new Harmony 520 a few weeks back. ($30 shipped)
The RCU810 learned the Venturer codes from the Harmony.

Now I have to find my JP1 cable! If I can't figure out the protocol, I'll post here for the experts to decode ...