JP1 Remotes

Hi

I have found an upgrade I would like to use (sky+ satellite) in Remote Master format, but my pc will not be happy with remote master, but is happy with Keymaster - can the file be converted to keymaster format ?

Thanks Keith

From your other posts, I assume this is for a Topline 8 remote. I think that will complicate things, so I just wanted to point it out to whichever of the other experts might try to help you with that.

In case I'm wrong about that, which remote is it for?

I don't know enough about the Topline 8 to help.

Thanks for the thoughts John, the the topline is one I would want to use it on, but also possiblbly others.

I assumed it would just be a file conversion to a .txt file and in KM I would set the remote type.

Looks like its not as simple as I thought.

Keith

kdp99,

The simple approach might be to ask for help here on getting RM to work on your computer. A lot of people have made it work and maybe some have seen your particular problem. Just a thought.

kdp99 wrote: I assumed it would just be a file conversion to a .txt file and in KM I would set the remote type.

There is no file conversion process from RM to KM.

If it were an ordinary protocol then anyone who has both RM and KM working on the same machine could easily copy/paste the functions column and OBC column from RM to KM and manually enter a few values on the setup sheet to give you a good starting point for your KM upgrade.

But, this sky+ upgrade is based on the RC6-M-20n protocol that I wrote myself. I'm pretty sure KM doesn't have RC6-M-20n.

There was a manual mode version of this upgrade for KM discussed recently, but it was for S3C80 remotes. It used pid 0020, but it doesn't seem to be compatible with the pid 0020 that is built into KM. If it were compatible them KM could convert from the S3C80 version to the P8/740 version.

Even if you could use RM, you probably need help from some P8/740 expert to see how to generate RC6-M-20n signals on a P8/740.

I would have thought this was one you could get One For All to download over the phone for you (or via the internet).

I looked on the internet area but it didn't seem obvious what upgrade was what, so I picked one (Sky 12) played it into the modem and got an upgrade device 855 and protocol $20. I don't have a sky+ box so can't tell if this is the one, but I do no the EFCs don't match those in the .rmdu for Sky+.

pgk wrote:I would have thought this was one you could get One For All to download over the phone for you (or via the internet).

I looked on the internet area but it didn't seem obvious what upgrade was what, so I picked one (Sky 12) played it into the modem and got an upgrade device 855 and protocol $20. I don't have a sky+ box so can't tell if this is the one, but I do no the EFCs don't match those in the .rmdu for Sky+.

I didn't guess the topline was one with internet download available (but that's mainly because I know nothing about the Topline).

I'm surprised you got 0855 for Sky. I thought there were only two UEI setup codes SAT/0847 and SAT/1175. One is Sky, the other is Sky+ but I don't recall which is which. The EFCs are mostly the same and the fixed data is different. I think they use a version of pid 0020 that is different from both KM's version and RM's version, but I think only the interpretation of fixed data varies. The EFCs should all match.

It's not the clearest thing in the world to know which upgrade is the on you need from the internet site.

It's got:
@SKY
British Sky Broadcasting 1 thru 10
Sky 1 thru 12
Skyplus

@Sky = 1134 and 1350

BskyB = 1847-1851 , 1855, 855, 0847, 1175, 1176

I'd have a guess that some of these may apply to the older analogue boxes rather than the Digital ones.

If there going to be any use the two John mentions are:

0847 = British Sky Broadcasting 9
1175 = British Sky Broadcasting 1

Depending on how things go I might download them later and see what they contain.

Well I download the 847 device and it does having match EFCs to the SKY+ rmdu, uses protocol $20 (also downloaded), has the REC key defined so looks like it is the SKY+ upgrade.

I can put together a KM upgrade with this, is it OK to post the OFA protocol code?

The SAT-1175.txt KM file in the file section has protocol code for both S3C8 and 740 remotes.

My guess is 1175 is correct, not 0847. But my info on 0847 says it doesn't include the record key.

I expect the only important difference between the two is fixed data, so if you post either you might want to mention the fixed data change needed to get the other instead.

pgk wrote: I can put together a KM upgrade with this, is it OK to post the OFA protocol code?

I assume the TopLine is a P8/740 model. You can select "pid: 00 20" (as Protocol name) in KM for a P8/740 model and see KM's version of the protocol. If the version you got from UEI is the same then it's better to use the pid 00 20 setting in KM than to paste in the protocol.

It was only for S3C80 that I had noticed a downloaded UEI version was different from the KM version and each different from the one I wrote myself for RM.

OK here's what I found.

Bottom line: Robs Sat-1175 is the way to go just ignore the $20 protocol from KM and use the one in the Notes/3rd Party Protocol area, which is identical to the OFA one.


The 1175 and 847 downloads from OFA were identical (including the keymap) except the final byte of fixed data $A5 for 1175 and $55 for 875.
847 works my normal sky box, so 1175 I guess is for Sky+.

The rec button was defined in 875 since it's also "Yellow" on the topline. (Should've checked the EFC matched record)

So Rob's SAT-1175 upgrade is Sky Plus.

On the protocol front the $20 protocol for 740 generated by KM doesn't work.
(1) It only expects two bytes of fixed data not five, so the keymap gets messed up when protocol and device are copied to IR.
(2) The disassembly in IR looks junk.
(Skipping the first three bytes)
0135: A9 60 LDA #$60
0137: 20 DB $20
0138: DB CLB 6,A
0139: 00 BRK
013A: A2 16 LDX #$16

The $0020 protocol in the notes/3rd party protocol matches the OFA one.

pgk wrote:Bottom line: Robs Sat-1175 is the way to go just ignore the $20 protocol from KM and use the one in the Notes/3rd Party Protocol area, which is identical to the OFA one.

Actually, when there's a protocol in the 3rd party area, KM will use it instead of the built in protocol.

The Robman wrote:KM will use it instead of the built in protocol.

Well... it's supposed to anyway!

There's a minor problem in the file Rob posted that is preventing the p-code from being used. The line in the Notes section that reads:

Upgrade Protocol 0 = 00 20 (740)

needs to be changed to:

Upgrade Protocol 0 = 00 20 (P8/740)

KM looks for P8/740 and not just 740 by itself, so it's not using the p-code from the Notes for P8/740 remotes.

NOTE: I edited the posted file in Rob's link to include the P8/740.

pgk wrote:(2) The disassembly in IR looks junk.
(Skipping the first three bytes)
0135: A9 60 LDA #$60
0137: 20 DB $20
0138: DB CLB 6,A
0139: 00 BRK
013A: A2 16 LDX #$16

Just for future reference, in case anyone got the idea that the built-in P8/740 pid 0020 code in KM is corrupt, the above must be a problem with IR's disassembly. In PB, it looks just fine:
0135: A9 60 LDA #$60
0137: 20 DB 00 JSR $00DB
013A: A2 16 LDX #$16