JP1 Remotes

Hi,

I created RV file which works with a Solo slingbox without any issues. After I've transfered it PL for a Pro HD and try it, the remote becomes un-responsive to the STB.

This has happen on the Kabel Deutschland AG DVR20 which has the Protocol: nokia 32
Device: 38
Sub device: 112
X: 38
X: 166 (toggle but it seem to work fine as constant for RV)

I've tried toggle constant and Release none seem to work for PL So I suppect the issue may lay in the protocol.

Files can be found;
https://www.hifi-remote.com/forums/dload ... e_id=11016

Thanks Phil

I found the RDF that you were using for the JB model and it was mis-named, it has BINPL at the beginning rather than BINJB, so I have fixed it.

https://www.hifi-remote.com/forums/dload ... e_id=10911

You don't need to re-download it, just rename your file.

If that alone doesn't fix it, your next step should be to try removing the 0173 entry from the [Protocols] section of the RDF, which will force it to include a protocol upgrade in the generated bin file.

The Robman wrote:I found the RDF that you were using for the JB model and it was mis-named, it has BINPL at the beginning rather than BINJB, so I have fixed it.

Hi Rob,

The name of the JB file is correct and it should be exported as PL file. The encryption algorithm is same for PL and JB chip, hence same RDF should work for both. Though they do have different protocol which work for the newer JB chipset.

The process and files I have used to build the remote has work many times in the past, which is what make this problem so confusing...

Cheers Phil

Have you ever tried loading a JB file into the box? My guess is that it would work and if it does, there's no need to have a mis-named RDF which creates mis-named bin files. (I'm not doubting that it also accepts PL files).

Have you tried removing the 0173 protocol from the JB RDF like I suggested?

Noirfire wrote:The name of the JB file is correct and it should be exported as PL file. The encryption algorithm is same for PL and JB chip, hence same RDF should work for both. Though they do have different protocol which work for the newer JB chipset.

The process and files I have used to build the remote has work many times in the past, which is what make this problem so confusing...

Cheers Phil

I can't find where JB came into the mix, but if the RDF has a protocol 0173 that could certainly be giving RM fits. As Rob said, remove the protocol entry for 0173 from the RDF and see if this clears things up.

Hi,

So I've tried renaming the RDF file and deleting the protocol 0173 and then receating the bin file, unfortunately it still has the same problem.

I'm not sure what the problem could be I've tried creating a PL and JB bin both don't work on the Pro-HD's.

Cheer Phil

Is this summary correct:
1) You have created other PL and JB files for the Pro-HD and both work
2) The Nokia32 file you created for the RV works the Kabel (note: RV doesn't need a protocol upgrade)
3) The earlier Nokia32 files (with no protocol upgrade) didn't work the Kabel in the Pro-HD
4) The new Nokia32 files (with a protocol upgrade) don't work the Kabel in the Pro-HD

How recent is the Pro-HD? Do you have access to one where you have loaded upgrades that work?

The Robman wrote:Is this summary correct:
1) You have created other PL and JB files for the Pro-HD and both work
2) The Nokia32 file you created for the RV works the Kabel (note: RV doesn't need a protocol upgrade)
3) The earlier Nokia32 files (with no protocol upgrade) didn't work the Kabel in the Pro-HD
4) The new Nokia32 files (with a protocol upgrade) don't work the Kabel in the Pro-HD

How recent is the Pro-HD? Do you have access to one where you have loaded upgrades that work?

Hi Rob,

1) Yeah I have created at least a hundred PL and JB for Pro-HD's and and never had this problem.

2) Yep the RV file is work fine.

3 & 4) Yes thats correct.

The Pro-HD's are about 2yrs old and yeah I have access to Pro-HD with working remotes.

Noirfire wrote:I have access to Pro-HD with working remotes.

Can you check whether any of the working upgrades required a protocol upgrade (ie, check the Output tab in RM)?

If it appears that all of them use built in protocols (ie, it says "Upgrade protocol not required" in the Output tab of RM), here's what I'd like to do.

Pick one of the working upgrades, then (temporarily) modify the RDF and remove the reference to that protocol from the [Protocols] section. After re-starting RM (so that it picks up the modified RDF), re-create the upgrade so that it does have a protocol upgrade and re-test it.

This should indicate whether there's anything strange about the protocols used by the Pro-HD.

Might be a total red herring but have you tried building the BIN file with a generic code (2012?). Like you I have built hundreds of PL BIN files for the Pro-HD and never seen this problem.

Also, this Custom Remote I built also uses the Nokia32 38.112 protocol and was proven to work:

https://www.hifi-remote.com/forums/dload ... e_id=10889

Does it work for you ?

vickyg2003 wrote:I can't find where JB came into the mix, but if the RDF has a protocol 0173 that could certainly be giving RM fits. As Rob said, remove the protocol entry for 0173 from the RDF and see if this clears things up.

The upgrade in the zip that Phil posted had a JB Slingbox selected.

I don't have any remotes with the 0173 protocol built in so I don't know exactly what the built in protocol sends. I do see however that many of the captures in the IR files have two values for x, 38 and 166. I loaded up the custom protocol in a comcast and it doesn't toggle this x value, everything just comes out as 38 and has a lot of repeats. Perhaps the High-X Bit should not be set to constant.


Is the JB family one of the chips that runs a little fast. Perhaps a capture of the IR output could show if there are any timing issues that need to be addressed as well.

The Robman wrote: here's what I'd like to do.

Hi Rob,

I have tired what you've said and when try the working remote with the removed protocol it works fine just like the orignal PL file.

alanrichey wrote: Also, this Custom Remote I built also uses the Nokia32 38.112 protocol and was proven to work:

Hi Alan,

I've also tried your file it loads correctly and I can see the IR signals being sent so that looks to be working too.

vickyg2003 wrote:Is the JB family one of the chips that runs a little fast. Perhaps a capture of the IR output could show if there are any timing issues that need to be addressed as well.

Hi Vicky,

I'm in the UK capture the signals sent from a solo with a RV chipset, does it matter wihich remote I use for this?

Cheers Phil

Noirfire wrote:

vickyg2003 wrote:Is the JB family one of the chips that runs a little fast. Perhaps a capture of the IR output could show if there are any timing issues that need to be addressed as well.

Hi Vicky,

I'm in the UK capture the signals sent from a solo with a RV chipset, does it matter wihich remote I use for this?

Cheers Phil

Hi again Phil. I see that your original captures were done on the 8910, I have one of those somewhere, so I could duplicate your setup here.

Since it is the JB unit that is not working, can you capture the output from that JB unit to the 8910? If so we'll be able to tell which way the protocol the frequency/timings need to be adjusted to get things working on the JB chipset.


Vicky

vickyg2003 wrote:Since it is the JB unit that is not working, can you capture the output from that JB unit to the 8910? If so we'll be able to tell which way the protocol the frequency/timings need to be adjusted to get things working on the JB chipset.

Hi vicky,

I have captured the files they can be found here;

https://www.hifi-remote.com/forums/dload ... e_id=11021

Let me know if you need anything else.

cheers Phil