202608 Charter OCAP C4000 URC-1060BC2

3FG · Post by **3FG** » Sat Dec 13, 2014 6:57 pm

OK, that confirms that the button numbers were all OK. The segment files showed that the 1060BC3 is capable of Transport Punchthrough, which is similar to Volume or Channel Punchthrough, except it works with buttons like play or Rewind.

The primary issue seems to be be that when RMIR uploads an upgrade with a new setup code, the remote rejects the setup code, and reverts to a default value. It doesn't actually reset the remote. We can see in your two RMIR files that you asked for and presumably uploaded setup code 0000, but after downloading the remote has changed the setup code to 1376.

I've again changed the RDF file to add a segment type 11, which I believe tells the remote about setup codes which you've added. Please try this RDF file, with your upgrade and check if the setup code persists through an upload/disconnect cable/reconnect/download cycle. BTW, just for completeness, on the Buttons or Layout tabs, assign the functions to buttons.

Jim-W · Post by **Jim-W** » Sat Dec 13, 2014 7:37 pm

Still not working, not sure this remote is worth messing with.

I dug up an Insignia I'll probably just use that.

Post by **mathdon** » Sun Dec 14, 2014 7:23 am

Dave, in Simpleset remotes at least, a type 11 segment is indeed a list of upgrades but it is only used in a setup search procedure. It has no effect on whether or not an upgrade setup code is recognised.

Jim-W · Post by **Jim-W** » Sun Dec 14, 2014 10:29 am

Jim-W wrote:Still not working, not sure this remote is worth messing with.

I dug up an Insignia I'll probably just use that.

That sounded like I'm giving up but I'm very willing to try anything you want.

3FG · Post by **3FG** » Sun Dec 14, 2014 11:29 am

The only thing that comes to mind is to verify that an upgrade has successfully been loaded into the remote and then to try manually to assign the setup code associated with the upgrade. So if you have uploaded an upgrade of TV type with a defined setup code of 1234 and verified by download that the upgrade is resident in the remote, try manually assigning 1234 to the TV button. Does it blink twice?

Jim-W · Post by **Jim-W** » Sun Dec 14, 2014 12:19 pm

Does not blink twice. If you're done, I'm done.

Thank you very much for your help. After setting up the Insignia looks like it should be just fine. Macros on the device keys, love that.

Thanks again

Jim

ruidosobruce · Post by **ruidosobruce** » Tue Feb 10, 2015 4:11 pm

3FG,
Did the RDF for the URC-1060BC3 ever get sorted out? Following a suggestion from mdavej in another thread, I got the URC-1060 C4000 remote, but mine is version BC3 (signature 202608, MaxQ processor and uses 5-digit device codes). It appears that devices assigned in RMIR using upgrades, do not function when uploaded to the remote. After upload, the device codes in the remote are unchanged, both in blink-back and in subequent RMIR download. But, if I use the device codes from the UEI manual in RMIR, they do upload and change correctly.

I have examined the RDF for this signature, but the file name and internal name of the RDF is URC-1060BC2. Thanks for any more info.

3FG · Post by **3FG** » Wed Feb 11, 2015 12:11 am

Bruce sent me a RMIR file from a un-programmed Charter 1060-BC3 remote which is interesting and likely explains why our upgrades haven't been accepted by the remote. There's good news and bad news: We can see 4 upgrades in the E2 area, but they are included in Type 0E segments rather than the standard Type 10. So the remote can accept upgrades, but RMIR doesn't know how to format them. Here are the 4 upgrades:

Code: Select all

00 6C 0E FF 00 00 00 04 A3 02 04 01 6C 00 AE FE 
FE FC F8 85 06 0F 44 12 00 00 01 00 02 00 03 00 
04 00 05 00 06 00 07 00 08 00 09 00 0D 00 0E 00 
54 00 1A 00 16 00 17 00 18 00 19 00 85 00 11 00 
1B 00 14 00 51 00 86 00 87 00 88 00 21 00 25 00 
20 00 22 00 24 00 23 00 92 00 27 00 53 00 50 00 
28 00 84 00 89 00 83 00 81 00 52 00 

00 44 0E FF 00 00 00 08 8B 01 08 01 2A 00 FE FE
2E FC F9 A9 32 95 55 5A 96 55 95 00 01 02 03 04
05 06 07 08 09 B1 B2 B3 0D 0E B0 54 1A 16 17 18
19 85 11 1B 52 26 21 25 20 22 24 23 51 27 53 50
28 84 83 80 

00 4C 0E FF 00 00 02 08 04 02 06 00 7E 00 BE CE 
F9 7A 7E 00 00 00 0A FA 01 7A 01 BA 01 3A 01 DA 
01 5A 01 9A 01 1A 01 EA 01 6A 01 43 01 83 01 C2 
01 63 01 A3 01 C3 01 23 01 E3 01 62 01 DE 00 5E 
00 1E 00 9E 00 08 01 38 01 D0 01 00

00 32 0E FF 00 00 02 0A 91 01 03 00 5A 00 BE DE
FF 20 5D 52 AF 7F BF 3F DF 5F 9F 1F EF 6F DB 3B
FC BC FF 67 37 D7 06 DE FE 7E 75 4D 7B 97 BB 2B
2B 00

The last one is probably the most familiar; it uses the NEC1 005A executor, device 69.181 (seen as 5D 52), setup code 2705 (0A 91). The apparent difference to the Type 10 segment is that the 2 byte field which indicates the offset to an executor isn't present. Perhaps we can accommodate this different structure into RMIR-- I'm not sure. Bruce, please upload your RMIR file to the Diagnotics area in case others want to see it.

ruidosobruce · Post by **ruidosobruce** » Wed Feb 11, 2015 8:45 am

The RMIR file downloaded from a new Charter URC-1060bc3 remote is OEM Charter URC-1060bc3.rmir straight out of sealed packaging.

Post by **mathdon** » Wed Feb 11, 2015 1:21 pm

3FG wrote:Perhaps we can accommodate this different structure into RMIR-- I'm not sure.

No problem. I'll post a build for testing, with this in, tomorrow.

ruidosobruce · Post by **ruidosobruce** » Wed Feb 11, 2015 3:09 pm

Thank you Graham. I will watch for the post.

Bruce

Post by **mathdon** » Thu Feb 12, 2015 10:02 am

Bruce, I'm not sure what version of RMIR you have. If you have something earlier than RMIR v2.03 Alpha 28 build 6, please first install that version. See this thread for instructions. The download is a complete package, including RDFs. All you have to do is unzip it into a new (writeable) folder.

Then please download this upgrade to build 9. Unzip that into the folder containing build 6, overwriting any existing files when prompted.

The .rmir file you posted for your Charter remote will load into build 9 but will still not show anything on the Devices tab. You need to do a fresh download from the remote for the devices to show up. Alternatively you can convert the file you posted as follows:

1. Load it into build 9.
2. Open the Raw Data tab. You will see a lot of hex values in black, many of them in bold.
3. Open the Advanced menu and click "Preserve original data". The hex values will be replaced by new ones in BLUE.
4. On the File menu, open Save As and change the dropdown box "Files of type" to "IR file (*.ir)". You can leave the filename unchanged, as the .rmir extension will be changed to .ir when you save it, but of course you can change the name if you like.
5. Now open this .ir file in RMIR. It should be the top file in the "Recent Files" list. The Devices tab should now display four devices.
6. Use Save As again to save this setup as a .rmir file under a new name.

This process forces RMIR to reinterpret the data.

Dave (3FG), I am somewhat confused by the version numbers for the Charter remote. The RDF repository contained one called "202608 (Charter OCAP C4000 URC-1060BC2).rdf". These recent posts speak of a signature 202608 but version BC3. I have assumed these are the same remote, and have updated that existing RDF to use the new support in RMIR for segment type 0x0E. I hope this is OK. The RMIR upgrade file contains this revised RDF, also your recent one for URC-8820BC1.3, as well as the new RMIR jar file.

ruidosobruce · Post by **ruidosobruce** » Thu Feb 12, 2015 1:27 pm

First to Graham: Thank you! I had no difficulty following your instructions and running the updated RMIR. With one exception it appears to upload my device files to the remote without errors*, and those devices function as expected, so it seems like RMIR is formatting the upgrades in the way the URC-1060BC3 expects. That part seems like a success.
*there is a new warning message "An upload overwrites the entire memory area for upgrades ...."

But, to everyone: Help! I cannot put the Dish Network device on any key. I can put the Apple remote upgrade on the Cable key with no problems, along with the TV and Audio upgrades, but not the Dish Network Receiver. I tried several Dish upgrades with device codes of 0775 and 1775 but none of them work. After uploading to the remote, a subsequent blink back or download shows the device code changed back to cable stb 01877. It seems that something must be locked in the remote.

I am able to turn off the other locks, Channel Lock for example, but I have no idea how to work around this.

The URC-1060BC3 is a beautiful remote with lots of well-placed buttons, but I'm stuck.

mdavej · Post by **mdavej** » Thu Feb 12, 2015 2:08 pm

Have you tried changing the device type on the general tab of RM to match the device type of the target device button?

ruidosobruce · Post by **ruidosobruce** » Thu Feb 12, 2015 3:03 pm

Dave, I have tried it both ways. Here are RMIR screen images, first as uploaded and then after immediately downloading from remote. Only Dish seems to get changed. (Dish also disappears from the Device tab)

General Tab for uploaded RMIR File:

General Tab for subsequent downloaded RMIR File: