33303330 TWC Atlas 1056B01 RDF

If you have a new remote that isn't recognized by RMIR, post the details here so we can help create a new RDF for it. Or, if there is an issue with an existing RDF or map, this is the place.
Post Reply
r3acer
Posts: 3
Joined: Sun Mar 02, 2014 9:58 am

33303330 TWC Atlas 1056B01 RDF

Post by r3acer »

I got a Time Warner Cable Atlas 1056B01 remote after reading that it's one of the supported remotes that's been around for a while, but when I click on "Download from remote" in RMIR I get an error message saying "No RDF matches signature starting 3330".

Doing a raw download and trying to open it in IR produces a message that "no definition file could be found for this remote (333033S*)". That last character after S is some garbled character that I can't even reproduce (could screenshot if that helps).

This is the raw download off this remote:
https://www.hifi-remote.com/forums/dload ... e_id=12404

Thoughts? I'm new to this and any help would be appreciated. Thanks.
mdavej
Expert
Posts: 4635
Joined: Wed Oct 08, 2003 7:08 am

Post by mdavej »

The 1056B01 is 3033 as far as we know. So try this with the latest version of RMIR:
https://www.hifi-remote.com/forums/dload ... e_id=10210
r3acer
Posts: 3
Joined: Sun Mar 02, 2014 9:58 am

Post by r3acer »

Replaced the existing file under RDF folder, but still no dice...

The interesting thing is that JP1xTEST.exe correctly identifies my remote:

jp1xtest version 0.00

*** FOUND A JP1.2/3 COMPATIBLE REMOTE ON COM4! ***
Signature is 30333033
Memory address is $0600
Memory size is $1400 (5120)

Any reason why RMIR.exe is misreading the signature as starting with 3330?
3FG
Expert
Posts: 3435
Joined: Mon May 18, 2009 11:48 pm

Post by 3FG »

The Raw Download starts with AF 50, which looks like a JP1 (not JP1.2/1.3) checksum since it adds to FF and is in the first two bytes. I used a text editor to replace AF 50 with 33 30, saved that file as 3330B.ir, and it loaded fine into a 1056B01. My first reaction is that somehow the signature stored in the E2 section has become corrupted. The first 8 bytes of the Raw Download should start 33 30 33 33 33 30 33 33, and not AF 50 33 33 33 30 33 33.

I would edit 3330.ir as I did and upload that to the remote. Then I think the correct signature will stick. If not, we'll want to know which interfae cable you're using and all of the version numbers from Help\About.
r3acer
Posts: 3
Joined: Sun Mar 02, 2014 9:58 am

Post by r3acer »

That worked! Thank you!
timg11
Posts: 42
Joined: Mon Aug 15, 2005 8:57 am

Post by timg11 »

I have a very similar remote. I'm having trouble getting it to function properly. Some buttons work, but some seem to do nothing although I have programmed them.


JP1XTEST returns:

jp1xtest version 0.00
*** FOUND A JP1.2/3 COMPATIBLE REMOTE ON COM1! ***
Signature is 30333033
Memory address is $0600
Memory size is $1400 (5120)


The raw download looks like this:
0600: 33 30 33 33 33 30 33 33 01 FE 07 55 14 E2 25 D2
0610: 35 79 27 D0 00 04 03 FF 00 11 00 0F 0F 00 00 00

So I don't have the issue with starting with AF 50.

I have previously used the RemoteMaster Remote selection of "Atlas OCAP URC-1056 JP1.3 (Black)" with this remote.
Is there a different choice that I should use?
3FG
Expert
Posts: 3435
Joined: Mon May 18, 2009 11:48 pm

Post by 3FG »

Seems like that is the correct RDF to use. Have you started by doing a 981 reset manually, downloading from the remote and then adding a single upgrade?
timg11
Posts: 42
Joined: Mon Aug 15, 2005 8:57 am

Post by timg11 »

It turns out that the remote is defective. The buttons in question don't work even after the 981 reset.
mdavej
Expert
Posts: 4635
Joined: Wed Oct 08, 2003 7:08 am

Post by mdavej »

If the some that don't work happen to be channels, numbers and OK, then you simply need to turn off cable lock.
Post Reply