Page 1 of 1
Cox Cable mini URC2220 CC HEX code
Posted: Wed Dec 20, 2017 4:43 pm
by marchewd
I am trying to program an RTi system with a Cox Cable Mini Box. I cannot find this IR command isn't in the database. I can add it as a HEX code, but I do not know what it is. I was hoping someone here might have this remote and could learn in the button and get the HEX code out of it. I do not have a working JP1 remote any longer, so I cannot do it myself.
Thanks for anyone's help,
Dan
Posted: Wed Dec 20, 2017 8:24 pm
by MrMoody
There's a Cox Mini Box upgrade in the file section, and CC is a function within it. It shows as OBC 67, Hex 3D. I'm not sure if that's what the RTI expects.
Posted: Thu Dec 21, 2017 11:03 am
by mdavej
By HEX, he means pronto hex. So using the Cox Mini upgrade, marchewd, open it in IR Scrutinizer and convert to pronto hex. If that doesn't work, open the upgrade in Remote Master, note all the OBCs, Protocol, device and subdevice and enter that info into IR Scrutinizer and convert to pronto hex in batches.
You don't need a JP1 remote. You can do all of this just with our software.
Posted: Thu Dec 28, 2017 10:21 am
by marchewd
Thanks mdavej. I get the rmdu file open in IR Scrutinizer, but it keeps reporting errors. I can't seem to figure out what I am doing wrong. Where do I put in the raw values to get the pronto hex code out of it? The values are NEC1, EFC 171, ODC 67 and Hex 3D.
Thanks and sorry for the late reply, as I have been off of work all week.
Dan
Posted: Thu Dec 28, 2017 11:04 am
by mdavej
You need protocol, device, sub device and function (OBC)
Posted: Thu Dec 28, 2017 11:19 am
by marchewd
The protocol is NEC1, Device is 175 and the Sub Device is 96. I fat fingered the OBC to ODC. It is 67.
Posted: Thu Dec 28, 2017 11:52 am
by mdavej
Posted: Thu Dec 28, 2017 11:56 am
by marchewd
Thank you. I assume the Pronto Hex is the code it generates in the below box?
Posted: Thu Dec 28, 2017 12:09 pm
by mdavej
Correct, so long as you pick Pronto Hex for the output format in the settings. Should look like a string of about 20 four-digit hex numbers.
Posted: Sun Apr 15, 2018 10:08 am
by The Robman
marchewd wrote:The protocol is NEC1, Device is 175 and the Sub Device is 96. I fat fingered the OBC to ODC. It is 67.
That generates to the following, did you get the same and does it work?
0000 006C 0022 0002 015B 00AD 0016 0041 0016 0041 0016 0041 0016 0041 0016 0016 0016 0041 0016 0016 0016 0041 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0041 0016 0041 0016 0016 0016 0041 0016 0041 0016 0016 0016 0016 0016 0016 0016 0016 0016 0041 0016 0016 0016 0016 0016 0016 0016 0041 0016 0041 0016 0041 0016 0041 0016 0016 0016 0041 0016 05F7 015B 0057 0016 0E6C
Posted: Sun Apr 15, 2018 9:16 pm
by marchewd
Yes Rob, that is what I got and it works!
Thanks for following up with me!