DishPVR 721 questions

[unclemiltie]

I've uploaded the PVR721 upgrade to Yahoo

This one has the Satellite ID set to 1, built for an RCU810

It's in the PVR area (not the satellite receiver area)

Thanks again to everyone for their help on this one!

[David_Levin]

Thanks - Great Work Everyone !!!

[The Robman]

And by the way Dave, welcome back, it's been a while!

[jon_armstrong]

Glad to hear you guys finally got it working. Dishplayer (old) is probably the worst situation in the JP1 world because it has a number of things going on that make it hard to understand to say the least.

There are three (and maybe more) different protocols all named $0002 in various models of remotes. Dishplayer (old) uses 16 data bits. They are in order a 6-bit byte for function (aka OBC here at JP1), a 5-bit byte for Unit code, and a 5-bit byte for Device Code. To really confuse things Dish uses bits in MSB first except for Unit code where they use LSB first. BTW, I think the term “unit code” was selected since it is decimal 0-31 and Remote ID is 1 to 32.

$0002 in most older remotes has, in order, one 8-bit byte of variable data one 8 bit-byte of fixed data. EFC's map to variable bytes. So as you observed, EFC's do change depending on Unit code in John's decoder used in IR. This is because the top two bits of variable data map to the bottom two bits of the unit code. SOME remotes need to use this (yours doesn't and any of the four possible EFC's will work.). In older remotes to change to unit codes above 3 (Remote ID 4), you have to change up to three bits in fixed data and use one of the four sets of EFC's.

In the RCU810, 2104, and 8811 series (and possibly others) it has one variable byte of 6-bits and two 5-bit bytes of fixed data. However UEIC always uses the bits starting from the left. So to convert from OBC to hex you need to multiply OBC by four then convert to hex. You also have to multiply device by 8, hence, device 16 * 8 = 128 decimal or 80 hex. But remember Unit code has its bits backwards so:

1 is 10000 XXX
2 is 01000 XXX
3 is 11000 XXX
etc…

where X can be either 1 or 0.

KM Master historically treated all bytes as LSB in Dishplayer Old. Device 16 (in MSB first) is 10000XXX but if it were LSB first then it would be device =1 and if you input that in KM master as device, then it will get the right answer.

We came to see that the device was really MSB first (with exception of unit code) and when John wrote decodeIR.dll used by IR and many other of our IR decoding tools, he followed that revised thinking. However, KM Master has not been modified to deal with that.

The 8910/9910 and I suspect the 2116/2117 and other newer remotes use another variant of Protocol ID $0002 that has five bytes of fixed data and byte 1 and byte 2 should be consistent with the RCU810, 2104, and 8811 series. I recall it being able to do the Dishplayer protocol as well and it may well use the unused two bottom bits of the variable data to call alternate devices for certain keys (like 16) and/or protocols.

[David_Levin]

And by the way Dave, welcome back, it's been a while!

Thanks Rob - I am one of the 'lucky' few with a 921 (Buggy - HD PVR).

Many people are having trouble with this puppy because it (and the new 811) remotes only send RF when they're talking to the sat boxes.

Myself (and others) have been suggesting jp1 remotes as a way to either control directly, or learn the keys to other learnables (I use a learnable with LCD assignable buttons in my theater - sorry).

Problem is getting the jp1 remote to send all the codes (especially if some are on a different device).

There's also a user trying to get a 6131 working - One-For-All was unable to find EFCs for the PIP stuff (probably because of the device 1 problem - but, they got all the other keys working).

So, I'm going to try and get the 6131 figured out (it really is a nice layout for a PVR) and send those people to Rob to buy remotes.

Dave

[ogaede]

Thanks for all the suggestions. I haven't had time to work on this anymore yet, but I will tomorrow, I hope. Right now my wife is making noises about going out to dinner for Valentine's day, and if I get absorbed in this right now I could get in big trouble.

I have two of the Dish PVRs here, so the two remotes are set to different IDs. I'll let you know if I get it to work. I changed the one on this unit from the default, so I'm thinking that may be the problem.

[ogaede]

I got it to work. The key was in entering unit code 12. I haven't had time to test all the buttons yet, but this is the first time I've been able to get any of them to work with a device upgrade.

Thanks to all.

[David_Levin]

Is the device combiner compatible with the 6131?

I loaded up unclemiltie's update

Keys are all messed up. The send light is on. But the keys don't do what they are supposed to. And, what they do seems to be inconsistant (switching to another device alters the key function).

In IR the power key appears to have the righ EFC.

I can keep playing, but want to make sure that is should have worked.

Thanks

[unclemiltie]

It appears that the discrete ON that I have coded in there is really a power toggle. I used the same ones that I had found on the DishPVR 508 that really are discretes and they appeared to work in my macros when I loaded up the remote.

But, the ON does not appear to be a discrete. the OFF is fine.

I'm searching through the remote codes but haven't found a discrete on yet. (I've been through all of the codes in the device=0 field)

Bummer!

[Mark Pierson]

Is the device combiner compatible with the 6131?

I loaded up unclemiltie's update

Keys are all messed up.

As far as I know, the DC is compatible with the 6131.

As Jon stated above, the problem you're having likely comes from the fact that unclemilite's upgrade is for an RCU810. The 'Dishplayer (Old)' protocol is different between the 2 remotes in the Fixed Data that it uses. On the RCU810, it uses 22 bytes of Fixed Data, while the 6131 version requires 5 bytes.

If you determine the correct Fixed Data bytes required by the 6131, and modify the upgrade accordingly, it should work. I think you can just append "00 00 00" to the existing Fixed Data entries in the DC table.

[David_Levin]

Thanks Mark - that gives me a great piece of information to work with....

[John Quaglino]

David,

I made a simple KM for the 6131 and 921 over the weekend. First, the 6131 controls most of the 921 using the standard 775 code. The only commands that are missing are 1)page up, 2)page down, 3)*, 4)#, 5)PIP, 6)PIP Swap, and PIP Move. For some reason my 6131 would do 30+skip but not 10- replay.

The KM file I'm using requires you to use 775 as your SAT/Cab device. I've also used IR to add advanced codes for * and #. I've set up a second device with keymoves to SAT/Cab for the PIP functions and to correct the replay button. I have not yet added the page up and down funtions. I'm trying to decide whether to use the thumbs up and down or to place them some where else.

If you would like them, I'll post them to the JP1 group.

[David_Levin]

Yes - please post them when your done....

I'd suggest either the chapter skip or thumbs for page up/down. If both are available perhaps map to both places.

So, your not using the Device Combiner? How are you getting the keymoves into the remote?

Do we still need the extender to get km supported key moves to work (I was thinking to use device combiner and avoid the extender and key moves)?

Though the PIP keys will always need key moves since they're not active in VCR/PVR mode. A small number of key moves are not a big deal to do directly on the remote.

Thanks

[John Quaglino]

It is a simple work around to get my 6131 up and running with the 921. The OFA 775 actually controls most of the 921. The rest is solely made up of keymoves.

This does not require the extender or device combiner. I might try device combiner in the future but there really aren't that many key moves. I'll post both the ir file and the km file.

[John Quaglino]

I've uploaded the KM and IR files for the 921 and 6131.