30333033 Identifying JP1.3 Atlas PVR

kupakai · Post by **kupakai** » Tue Jan 16, 2007 11:51 am

I was thinking of getting the Atlas PVR (Day) remote to play around with, and I'm a little confused as to which one that is. It seems very similar to an old model with a similar name, and I don't want to get the wrong one.

Can anyone tell me is this the right one?
http://cgi.ebay.com/ws/eBayISAPI.dll?Vi ... 0069084508

I asked the seller if the buttons on the left of left arrow says "Day" instead of "Settings" (it looks like "Day" in the picture). Is that what identifies it?

Post by **The Robman** » Tue Jan 16, 2007 5:30 pm

I don't think you can use the button names to differentiate versions, as these will change depending on which OEM ordered the remotes. You'll have to ask him if it says JP1.3 by the 6-pin.

johnsfine · Post by **johnsfine** » Tue Apr 17, 2007 5:17 pm

I'm trying to answer an Atlas JP1.3 question at
http://www.remotecentral.com/cgi-bin/mb ... ?5238,2#24

But I'm unsure of details. Someone correct me if I'm wrong about any of the following:

1) To use IR.exe you need the rdf file (not yet in the main collection of rdf files). Get it from:
https://www.hifi-remote.com/forums/dload ... le_id=3953

2) To use RemoteMaster.jar you need that rdf, plus the Atlas Jp1.3 files at:
https://www.hifi-remote.com/forums/dload ... le_id=3622

3) KM support?? (I have no clue. I'd use RemoteMaster instead of KM anyway).

4) Cable: A JP1.2 serial cable is used for JP1.3

5) General level of support: I assume you can build and install upgrades as well as doing other basic operations (in other words "JP1.3" doesn't indicate any important software features that we haven't supported yet in IR and RM).

speaker.guy · Post by **speaker.guy** » Tue Apr 17, 2007 5:39 pm

"Day" refers to that functionality that some cable operators use for fast navigation in the guides. I have actually seen remote references that do refer to the remote that has the day buttons as the "day"remote.

I saw a page somewhere which had a picture of half a dozen variants of the Atlas remote, and one of them was called the "day" remote.

EDIT: at this website:
http://www.urcsupport.com/

Post by **The Robman** » Wed Apr 18, 2007 11:49 am

JP1.3 remotes use a Samsung flash processor, so the protocol executor code is the same as that which is used for regular Saumsung S3C8 JP1 remotes. JP1.2 remotes use a Motorola flash processor, so they use different exectors.

But apart from that, JP1.3 and JP1.2 remotes are the same as far as what sort of cable is needed and the I/O routines.

insaneoctane · Post by **insaneoctane** » Tue Apr 24, 2007 11:14 pm

When I plug my Atlas DVR (day) remote and try to download using IR.exe, it complains that it doesn't find 30333033 in the RDF database, and it doesn't come up with much of anything populated (that I can tell). How do I proceed?

kupakai · Post by **kupakai** » Wed Apr 25, 2007 4:30 am

insaneoctane wrote:When I plug my Atlas DVR (day) remote and try to download using IR.exe, it complains that it doesn't find 30333033 in the RDF database, and it doesn't come up with much of anything populated (that I can tell). How do I proceed?

Welcome insaneoctane, so you got your JP1 cable! And it looks like you found a new remote. A new RDF will have to be create to work with your remote. Save it as a file in IR.exe and upload it to the Diagnosis area in the File Section and post the link to it and people here will help you create an RDF file for the remote.

insaneoctane · Post by **insaneoctane** » Wed Apr 25, 2007 9:34 am

I am at work now, so I can't run the dump program right now, but I did VPN into my machine and this is the ir file that resulted when I did a "download remote" button and saved the file:

0000: 33 30 33 33 33 30 33 33 B7 48 05 60 10 3C 22 1B
0010: 22 1B 20 3C 01 0C 01 FF 11 11 11 0F 0F 00 00 00
0020: 00 00 00 00 00 00 B8 10 04 05 60 4C 30 9F 8F 08
0030: 1F 1A 1E 19 02 39 02 02 B9 10 04 05 60 08 52 34
0040: 9F 03 09 02 38 35 9F 04 09 1F 1F 15 36 9F 03 09
0050: 02 39 27 10 04 05 60 FC AD FF FF FF FF FF FF FF
The rest of this dump can be found here:
https://www.hifi-remote.com/forums/dload ... le_id=4499

If this is the wrong data, I'll be happy to do the dump when I get home tonight. Thanks.

PS- Kupakai, would you recommend this thread/forum vs the remotecentral one? I don't want to waste people's time on two forums, so which ever is the best please let me know your opinion.

insaneoctane · Post by **insaneoctane** » Wed Apr 25, 2007 8:07 pm

Still having trouble...
I tested comm with jp1xtest program with the following SUCCESSFUL results:

E:\Remote Control\TestGroup>jp1xtest
jp1xtest version 0.00

**** FOUND A JP1.x COMPATIBLE REMOTE ON COM1! ****
Signature is 30333033
Memory address is $0600
Memory size is $1400 (5120)

E:\Remote Control\TestGroup>pause
Press any key to continue . . .

By the way, when I ran your program, the "TV" device blinked twice
So, what's up?

HERE is a link to the raw data in the .ir file that I saved from ir.exe and uploaded to the diagnosis area:
https://www.hifi-remote.com/forums/dload ... le_id=4499

binky123 · Post by **binky123** » Thu Apr 26, 2007 9:34 am

I've uploaded a rough RDF based on the 30003000 RDF. There seems to be a descrepancy in your device upgrade for CBL/0476 as it seems to be offset by 1 byte as it has a leading 00 byte before the C4 byte. The upgrade should be

Code: Select all

Upgrade Code 0 = 01 DC (CBL/0476)
C4 00 FE FE FE E0 FF 00 80 40 C0 20 A0 60 E0 10 
90 B0 70 F0 D0 30 50 98 88 2C AC 6C EC 48 C8 CC 
0C 28 A8 5C DC 1C F8 78 B8 9C 8C 68 08 1C 9C E8 
E4 14 
End

Here is the rough RDF:
https://www.hifi-remote.com/forums/dload ... le_id=4502

insaneoctane · Post by **insaneoctane** » Thu Apr 26, 2007 10:14 am

Thanks for the quick reply!
I have a couple questions:
I'm fairly new to the JP1 scene, so I'm not sure what the descrepancy in my device upgrade for 0476 means? Is there a problem with my remote? My remote seems to work fine... Does this mean that the RDF file many not work properly? Does it mean only device 0476 is in question? Just not sure what is "at risk" or what to look out for with this descrepancy...

Also, before I load this new RDF, and starting playing with my remote, I want to make sure I can get back to my original remote state...have I done all that is necessary to get my remote back to it's original state by clicking "download remote" and saving the resulting .ir file? Or, is there more for me to do?

Lastly, is there any recommended specific things I should check to verify the validity of this new RDF file? Or, should I just assume it works find and proceed forward and only report if I run into trouble?
Sorry, if these are bonehead questions.
Thanks, again.

binky123 · Post by **binky123** » Thu Apr 26, 2007 2:10 pm

The discrepancy means that IR7 reports an error as the format of the data is incorrect. You are not using CBL/0476 setup code so you aren't affected if you delete this entry. You can either change the data to this

Code: Select all

0400:  6F  90  0A  38  0A  3E  C4  00  FE  FE  FE  E0  FF  00  80  40
0410:  C0  20  A0  60  E0  10  90  B0  70  F0  D0  30  50  98  88  2C
0420:  AC  6C  EC  48  C8  CC  0C  28  A8  5C  DC  1C  F8  78  B8  9C
0430:  8C  68  08  1C  9C  E8  E4  14  00  01  01  DC  0A  06  00  00
0440:  FF  FF  FF  FF  FF  FF  FF  FF  FF  FF  FF  FF  FF  FF  FF  FF

or you can delete the CBL/0476 entry and replace it with

Code: Select all

0400:  00  FF  0A  06  0A  06  00  00  FF  FF  FF  FF  FF  FF  FF  FF
0410:  FF  FF  FF  FF  FF  FF  FF  FF  FF  FF  FF  FF  FF  FF  FF  FF
0420:  FF  FF  FF  FF  FF  FF  FF  FF  FF  FF  FF  FF  FF  FF  FF  FF
0430:  FF  FF  FF  FF  FF  FF  FF  FF  FF  FF  FF  FF  FF  FF  FF  FF
0440:  FF  FF  FF  FF  FF  FF  FF  FF  FF  FF  FF  FF  FF  FF  FF  FF

insaneoctane · Post by **insaneoctane** » Thu Apr 26, 2007 3:11 pm

Okay, I'll probably edit as suggested. Just out of curiosity, what would your GUESS be as to how the code gets out of wack by one byte like this??

Post by **The Robman** » Thu Apr 26, 2007 6:09 pm

An easier edit to the file would be to change this...

0400: 90 6F 0A 39 0A 3F 00 C4 00 FE FE FE E0 FF 00 80
0410: 40 C0 20 A0 60 E0 10 90 B0 70 F0 D0 30 50 98 88
0420: 2C AC 6C EC 48 C8 CC 0C 28 A8 5C DC 1C F8 78 B8
0430: 9C 8C 68 08 1C 9C E8 E4 14 00 01 01 DC 0A 06 00

to this...

0400: 90 6F 0A 39 0A 3F 00 C4 00 FE FE FE E0 FF 00 80
0410: 40 C0 20 A0 60 E0 10 90 B0 70 F0 D0 30 50 98 88
0420: 2C AC 6C EC 48 C8 CC 0C 28 A8 5C DC 1C F8 78 B8
0430: 9C 8C 68 08 1C 9C E8 E4 14 00 01 01 DC 0A 07 00

Here's a brief high level description of what the issue is (and this is way more info than you need, it's just in case you're curious). This little chunk of code is the entire contents of your upgrade section. The first word (2 bytes) is a checksum, so don't worry about that. The next word is the address of the upgrade setup code list (ie, $0A39) and the following word is the address of the upgrade protocol list (ie, $0A3F). Because we start the IR file contents at address $0000 (rather than $0600, which is the true address in this case) those 2 addresses actually show up as $0439 and $043F in this file.

At address $0439 you will find...
00 01 01 DC 0A 06

Here's what that data means...
00 01 = 1 upgrade setup code to follow
01 DC = the hex code for CBL/0476
0A 06 = the address where you'll find the CBL/0476 code (ie, $0406 in the IR file)

At address $043F you'll find "00 00" which means there are no protocol upgrades.

If you look at the data at $0406 you'll find this...
00 C4 00 FE FE FE E0 FF 00 80 etc ...

The first byte of the upgrade data gives you the 2nd byte of the protocol id. In this case you would assume that 2nd byte of the protocol id is "00", but we happen to know that the 2nd byte of the real protocol id is "C4". We're also quite familiar with the format of upgrades and it's obvious to us that the upgrade data really starts with the "C4" byte.

As to your question of how this screwy data got into your remote, we have no idea. It was obviously loaded that way at the factory. As to why they even tried loading CBL/0476 into the remote, that's an even better question, as this code is pre-installed in just about every UEI remote, so I would be very surprised if it isn't resident in the ROM of your remote. But, none the less, it's nothing to worry about. You can delete this upgrade, and once we have the RDF finalized, you will be able to add your own upgrades.

insaneoctane · Post by **insaneoctane** » Thu Apr 26, 2007 11:59 pm

When I use ir.exe and choose "download remote" it pops up an error dialog box titled "ir" with the message "list out of bounds (195)". After I click "OK", I notice in the RAW DATA tab the data goes has data to 19F0...which I think is too far (I think 1400 was max from the test program)?? Also, the raw data now starts at 0600?? Anyway, anybody know why I get this error message? Is it something I can ignore?