Converting Protocol from URC9910 to Comcast 1067 b1

cywelchjr · Post by **cywelchjr** » Sun Jan 28, 2007 5:45 pm

I have a protocol that Robman created/setup for me for my Bose Wave radio with CD player. It works great on my 9910, but now I want to convert the upgrade to my Comcast 1067 that we normally use the bedroom. Since I plan on hooking the bedroom DVD player to the radio's aux input I want to setup that device using keymapping from the wave radio upgrade into the DVD upgrade. I tried to re-create the upgrade for the Comcast JP 1.2 remote, but even though the protocol editor seems to say it gave me a protocol, it doesn't seem to work, and I'm not sure I know how to make it happen.

What else do I need to provide to work this out? I'm hoping this is possible, since I rather like the remote, and while I could buy another 9910, I just want to figure this out if possible.

Post by **The Robman** » Sun Jan 28, 2007 6:02 pm

You can't use an S3C8 protocol in a JP1.x remote.

If the Comcast remote is really a JP1.1 remote (as I suspect), try this...
Upgrade protocol 0 = 01 23 (SST) Bose Wave Radio (PB v4.00)
11 23 01 20 10 A4 45 08 08 01 7C 77 00 7C 7D 30
DE 00 01 F9 77 CC C0 2F
End

If it really is a JP1.2 remote, try this...
Upgrade protocol 0 = 01 23 (HCS08) Bose Wave Radio (PB v4.00)
20 12 22 46 01 A4 45 08 08 00 FA 02 EE 00 FA 00
FA 61 A8 01 F4 02 EE CC FF 5F
End

cywelchjr · Post by **cywelchjr** » Sun Jan 28, 2007 10:40 pm

Ok, you came up with the same protocol code I did (I see you used the same protocol builder version I did) but it doesn't work.

The remote (according to the connector, the RDF and the fact that it works with my JP1.2 cable) is JP1.2 but the protocol doesn't appear to work. When I press any key that is attached to it it blinks the aux button ( the device that is setup to use the protocol) and switches to the cable device.

I have uploaded the IR file here:
https://www.hifi-remote.com/forums/dload ... le_id=4142

I don't know if you or any others can help, but I don't understand why it's not working as it seems like it should be working.

It did take me a while to figure out how to get the protocol into RM sinc KM doesn't seem to support the 1067a and I can't see a way to make it do so.

Post by **The Robman** » Sun Jan 28, 2007 10:58 pm

You don't actually need to get the protocol into RM as you can paste it directly into IR. As for why the protocols don't work, I can't help you there. Mike E is the expert with that stuff.

binky123 · Post by **binky123** » Sun Jan 28, 2007 11:04 pm

PB v4.00 seems to be generating an incorrect offset. Try this

Upgrade protocol 0 = 01 23 (HCS08) Bose Wave Radio (PB v4.00)
20 15 22 46 01 A4 45 08 08 00 FA 02 EE 00 FA 00
FA 61 A8 01 F4 02 EE CC FF 5F
End

cywelchjr · Post by **cywelchjr** » Mon Jan 29, 2007 2:22 pm

I'll try the updated protocol tonight. I've got the IR file ready to go, so I'll hook up the remote and upload it tonight and see how it works. If it works, I have figured out how to force the upgrade proto into the RM file via manual editing. We'll see how it works.

Thanks in advance.

cywelchjr · Post by **cywelchjr** » Wed Jan 31, 2007 2:20 am

Sorry, didn't get to it until tonight (got sucked up into a woot-off on woot.com). The change to the offset in the protocol makes it work just fine. I'm going to get the standalone upgrade all setup and clean and I'll upload it. Then I'll combine it with my DVD player so I end up with a combo device that will run both with (hopefully) sensible key mappings.

Thanks so much for the help. The question I do have, is did we find a bug in protocol builder 4.0 or did we do something wrong? It would be nice to know now that we know that the little change there made it work.

Post by **The Robman** » Wed Jan 31, 2007 7:38 am

It's a bug in PB.

Chester · Post by **Chester** » Wed Jul 18, 2007 3:11 pm

The Robman wrote:It's a bug in PB.

What is the workaround as I have one protocol I would like to convert and am also having the same problem (I just seen this post and haven't spent
too much time to figure it out but did suspect it was something with PB4).
Here it is if you could look at it I would greatly appreciate it
But would lie to fish for myself.

Upgrade protocol 0 = 01 FF (S3C8+) PB v3.11
36 71 11 8B 12 85 45 08 08 00 9F 04 01 04 21 00
7D 20 53 04 21 00 7D 8D 01 46
End
I think you made it for me in the first place.
It was for my homemade remote tv tower

Post by **The Robman** » Wed Jul 18, 2007 4:52 pm

I don't know anything about the inner workings of PB, and I don't know too much about the HCS08 protocol code either, but it appears that the bug is limited to the 2nd byte of the generated protocol code.

In the previous example, binky was able to add 3 to the byte to get it to work, maybe the same edit would work for you.

Chester · Post by **Chester** » Thu Jul 19, 2007 4:04 am

Yes it did
and Im sorry if I hijacked this thread (wasnt thinking)

Post by **The Robman** » Thu Jul 19, 2007 6:34 am

Did adjusting the 2nd byte fix the protocol?

binky123 · Post by **binky123** » Thu Jul 19, 2007 7:26 am

He has to take the original PB file and regenerate the protocol for the HCS08 processor. After that he may have to adjust the 2nd byte of the HCS08 protocol executor.

Post by **The Robman** » Thu Jul 19, 2007 8:12 am

Right, that's what I'm assuming he did.

Chester · Post by **Chester** » Fri Jul 20, 2007 9:00 am

The Robman wrote:Did adjusting the 2nd byte fix the protocol?

Yes it did it fixed the bose wave and my homemade tv tower
Thanks as I was getting frustrated