202608 Charter OCAP C4000 URC-1060BC2

ncoig · Post by **ncoig** » Sun Sep 13, 2015 12:55 am

mathdon wrote: As for the PID, there is already an official UEI protocol with PID=0160 that is not Roomba, so that cannot be used in protocols.ini. I chose a value higher than any known PID, but 02 60 would be equally suitable. Note that many remotes will not accept PIDs greater than 01FF, but the MAXQ remotes do so and there are now quite a lot of protocols that start with 02.

Is the existing PID for the Roomba, aka, "manual settings" that is set to 01 60 overwriting the existing protocol? Perhaps that is what the asterisk near the protocol ID designates?

-N

ncoig · Post by **ncoig** » Sun Sep 13, 2015 1:13 am

mathdon wrote:Looking back, I see that the S3C80 protocol repeats every signal at least three times. I forgot to put that into the MAXQ version. Try changing the code line to
Code: Select all
Code.MAXQ610=32 64 01 0A 6F 00 27 00 24 00 70 00 37 07 00 00 63 10 01 03 70
which has these repeats.

Boom! This appears to work as expected. Nothing like tossing in the box another remote I no longer need lingering around!

Thank you, sir.

I've posted my working upgrade below for those interested.

http://www.hifi-remote.com/forums/dload ... e_id=13555

-N

Post by **mathdon** » Sun Sep 13, 2015 5:47 am

ncoig wrote:Is the existing PID for the Roomba, aka, "manual settings" that is set to 01 60 overwriting the existing protocol? Perhaps that is what the asterisk near the protocol ID designates?

A protocol upgrade doesn't overwrite a built-in protocol with the same PID, i.e. the built-in one remains in the remote, but it does take precedence over it. This is only a problem in a remote that (a) has a built-in protocol with PID 0160, and (b) is using a setup code that uses this built-in protocol. For an individual user this would just be an unfortunate coincidence, but if a home-made protocol is added to protocols.ini then it is available for all users, so such a PID clash needs to be avoided.

This situation usually arises when we use an apparently unused PID, often beyond the highest value we have seen used, but UEI later adds more protocols to newer remotes and itself uses the PID we have chosen.

The asterisk simply denotes that the device upgrade is using a protocol upgrade rather than a built-in protocol.

Post by **The Robman** » Sun Sep 13, 2015 9:28 am

mathdon wrote:This is only a problem in a remote that (a) has a built-in protocol with PID 0160, and (b) is using a setup code that uses this built-in protocol.

A very minor clarification, built-in setup codes always use built-in protocols, even if a protocol upgrade is present in the remote. So, if you just want to make a minor tweak to a protocol, you will have to also load a device upgrade, even if you didn't want to change any of the button mappings.