JP1 Remotes

Keep in mind that that trick will just work for protocols that get sent with a call to $0146 or $0149. The more complicated protocols often need to be crafted manually, in which case you will likely see a call to $010A somewhere in there. That is the call that asks whether the button is still being held, so you will see some conditional logic following it where one branch exits and another repeats. You could delete the $010A call and any code supporting the repeating branch in order to make it not repeat.

Sorry, coming to this a bit late, as for some reason I wasn't notified of the postings.

Fascinating stuff and I followed it, and most importantly IT WORKS !!!

Rebuilt my Custom Sky Remote and now no more double-skipping

Well done to all. Now we just need another guinea pig.

alanrichey wrote:Well done to all. Now we just need another guinea pig.

You could always go back to the thread (http://answers.slingbox.com/message/13616#13616) on the Sling Media forums that instigated you to create this one. Maybe recreate bin files for the Olevia ZMT-621FTA+ without the repeat.

There's one more thing that you also need to keep in mind. Protocol $0020 is not present in the RV Slingbox, so it's added as an upgrade using the code found in protocols.ini, so as you're using an RV box, you got the code that you changed.

However, if you had tested this using a PL box, which does have the $0020 protocol installed, it would not have worked because RM would not have used a protocol upgrade.

To make it work in the PL box, you would also need to edit the RDF where you would delete the 0020 entry in the protocol list at the bottom.

Interesting. Are you sure ? All my testing was done on a Pro-HD with the JB chip but I used the PL BIN file and it definitely solved my problem.

And when you select the PL chip it shows the protocol upgrade under the output tab.

Al

Sorry, I was still thinking of the Thomson protocol that you had a problem with, which IS in the RV box and is NOT in the PL box.

But regardless, you still need to keep what I said in mind because if you change the code in protocols.ini for a protocol that's resident in your Slingbox, it won't fix the issue unless you delete it from the RDF for your Slingbox.

OK. So am I right in thinking that if we see an 'Update Protocol' entry in the Output Tab of RM then we are OK. But if we don't see one then it is built-in and we need to remove the entry?

I tried to use a search for the "0020" pattern within the document and couldn't find it. I took another screenshot of the respective RDF that I think you're referring, "BINPL (Slingbox with UEI PL Chip).rdf". Just to verify whether or not I'm looking at the right file. Maybe I'm using a older version of the RDF?



Uploaded with ImageShack.us

Ooo... I did find it in the "BINRV (Slingbox with UEI RV Chip).rdf". Does that mean I would have to delete it from the RV's rdf in order to import an RV binary to transcode it to a PL binary?



Uploaded with ImageShack.us

I already corrected myself in my previous post, use the Thomson protocol instead ($004B).

From the RV-RDF:

[Protocols]
0000, 0002, 000D, 0014, 001C, 001F, 0020, 0027, 0034, 0045,
004B, 0058, 005A, 005C, 005D, 005E, 0065, 0066, 0073, 007E,
0087, 0098, 009C, 00A5, 00AB, 00AF, 00B6, 00B9, 00BD, 00C4,
00C9, 00CA, 00CD, 00DE, 00E8, 00ED, 00F0, 00F8, 0111, 0112,
011A, 011B, 011E, 015E, 0161, 016C, 0173, 0176, 017E, 0182,
018C

From the PL-RDF:

[Protocols]
0000, 0002, 0006, 000D, 0014, 0015, 001A, 001C, 001F, 0022,
0027, 0029, 002F, 0034, 003F, 0045, 0058, 005A, 005C, 005D,
005E, 0060, 0061, 0065, 006A, 0073, 007E:3, 0098, 009C, 009E,
00A4, 00AF, 00B6, 00C4, 00C9, 00CA, 00CD, 00DE, 00E2, 00E3,
00E7, 00E8, 00F2, 00F5, 00F8, 010F, 0111, 0114, 011A, 011E,
012A, 0162, 016C, 016D, 017A, 0186, 018B, 01A4

Does that mean I would have to delete the missing protocol from the "Import Binary Upgrade" RDF in order to "Export Binary Upgrade" to a different RDF?

For example,
If I am attempting to "Import Binaryy Upgrade" from an x####_RV.bin and intending on exporting to an x####_PL.bin then I should make sure to delete the respective protocol if they are not present in both RDFs?

The only RDF that matters is the one for the Slingbox that you are creating the upgrade for.