JP1 Remotes

crosstalk · Joined: 30 Apr 2006 Posts: 45 Location: PA

Hello. I am having a problem getting the device upgrade for the CBL/1982 Pace DC50x digital transport adapter loaded into my Comcast 1067 remote. This is the file I am using: http://www.hifi-remote.com/forums/dload.php?action=file&file_id=6326

I load the upgrade into RM, change the remote from 6131 to comcast urc-1067 jp1.3, do the keymapping, then cut/paste the device and protocol upgrades into IR. I turned off "lock cable setup code" and set the code to cbl/1982. I noticed, however, that after I cut/paste, a lot of the button mappings in IR just show "n/a" instead of the proper codes. What am I doing wrong? I just upgraded to the latest RM and IR, so hopefully that's not an issue. Thanks.

mdavej · Expert Joined: 08 Oct 2003 Posts: 4501

Post your version of the RM file and your IR file. Sounds like you didn't set your device button to 1982 on the general tab.

crosstalk · Joined: 30 Apr 2006 Posts: 45 Location: PA

Sorry my mistake. I actually have the JP1.2 version of this comcast remote (urc-1067a, signature CS301009, processor HCS08). So is there any way to adapt the protocol of this Pace device upgrade to the HCS08 processor-based remote?

3FG · Expert Joined: 19 May 2009 Posts: 3367

Well, there is a way to adapt the protocol, but it takes the effort of one of the few experts who understand both HCS08 and S3F80/S3C80 assembly language. [In this context, a protocol upgrade is really a short subroutine.] Remotes designed several years ago use the Samsung S3C80 microprocessor, and the remotes being designed now use the S3F80. Those assembly languages are effectively identical. In between, howver, UEI used the Motorola/Freescale HCS08 processor. So older remotes(JP1) or new remotes (JP1.3) can use the upgrade but "slightly old" (JP1.2) remotes can't. In principle, the protocol assembly language can be translated to the HCS08 assembly language, but this particular protocol (XMP) is very sensitive to timing variations, and the job promises to be time consuming.

In your case, you can probably easily get around the issue by taking your 1067 to Comcast and asking for a different remote, which will probably be a 1067BX3 (has a red select/OK button). Then you can use the upgrade, or more simply use the Cable 1982 setup code built into the remote. Just tell Comcast that the old one doesn't work.

I know the 1067BX3 will work either with the upgrade or with the built-in setup code, because I have tried it both ways.

vickyg2003 · Posted: Thu Oct 29, 2009 5:41 am Post subject:

I downloaded this and took a look at how huge the protocol was. I was a little apprehensive about how much code needed to be written, but to my delight when I changed the remote the the 1067, the HCS08 was already written!! Whew! Hopefully, all you need to do is select the correct remote.
_________________
Remember to provide feedback to let us know how the problem was solved and share your upgrades.

Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.

crosstalk · Joined: 30 Apr 2006 Posts: 45 Location: PA

I noticed that in KM when I change the remote to 1067, something appears in the protocol box as HCS08 code. In RM, I just get an error that the manual settings are wrong and the remote will not work. So should I try the code that automagically appears in KM? I was assuming it was some kind of glitch and not actual code that was going to work.

I guess I could try getting a new remote from comcast or maybe just switch to one of the atlas ocap remotes that I have collecting dust. The comcast form factor seems a little better than the atlas, which is why I have been hanging on to it.

Thanks for all the help.

crosstalk · Joined: 30 Apr 2006 Posts: 45 Location: PA

Well, it looks like I might be able to answer my own question here! I noticed that the release notes for KM 9.18 indicated Dreambox (XMP) protocol support, so I selected that protocol and deleted the third-party (manual) one. This appears to be correct because KM generates the protocol upgrade for the urc-1067a, but not the 1067b (which apparently has support for XMP in the ROM). Although I can't test it until later today, I am hopeful that it is going to work. If it works, it seems like I should submit a new device upgrade file to replace the older one in the files section.

mr_d_p_gumby · Posted: Thu Oct 29, 2009 2:21 pm Post subject:

crosstalk · Joined: 30 Apr 2006 Posts: 45 Location: PA

Thanks. Just to clarify--the 5-digit EFC and 3-digit EFC columns appear to be decimal numbers, so I should just type over those with the data from the Hex column (transposed)? For example, for function channel up, the 3-digit EFC is 042 and the hex is 00 0D. So I should type 0D 00 in the 3-digit EFC column?

mr_d_p_gumby · Posted: Fri Oct 30, 2009 10:53 am Post subject:

crosstalk · Joined: 30 Apr 2006 Posts: 45 Location: PA

I tested the output of KM and it didn't work so I tried swapping the bytes by typing them into the 3-digit EFC column. This didn't work either--KM gave me the exact same upgrade output. I could be doing something wrong, so I guess I'll wait for the next version. Thanks for the help.

mr_d_p_gumby · Posted: Fri Oct 30, 2009 10:30 pm Post subject:

Try this:

crosstalk · Joined: 30 Apr 2006 Posts: 45 Location: PA

Thanks for posting the upgrade. It works!

mr_d_p_gumby · Posted: Sat Oct 31, 2009 11:00 pm Post subject:

Great. I've posted a modified KM upgrade file here. Note that because of the bug in KM v9.18, you must leave the Functions tab set to EFC5 mode. KM v9.18 will not compute the correct OBC or EFC3 values. This will be fixed in the next release of KM. I doubt this will work in RM until the Dreambox protocol is fixed there too.
_________________
Mike England

JP1 Group at Yahoo!, JP1 Files Area

mr_d_p_gumby · Posted: Sun Jan 31, 2010 12:34 pm Post subject:

I have updated the Pace upgrade to use the new XMP (JP1) protocol available in KM v9.19.
_________________
Mike England

JP1 Group at Yahoo!, JP1 Files Area