30333033 Identifying JP1.3 Atlas PVR

binky123 · Post by **binky123** » Wed Jun 27, 2007 9:25 am

No, I'm not talking about the [FixedData] section in the RDF. You shouldn't be editing the RDF. I'm talking about the RAW Data Tab in IR. If you go to F200, you will see the corrupted bytes.

Your base .IR file should actually be your original .IR file that you first downloaded from the remote. Like I said previously, the data at F200 should have the CBL/1376 device upgrade data.

speaker.guy · Post by **speaker.guy** » Wed Jun 27, 2007 2:58 pm

I corrected the raw data as above, doesn't help. I created an upgrade with just the Replay (I used device code 1614 to avoid conflict with the built in code), copied it to IR, uploaded it to the remote....Nothing.
https://www.hifi-remote.com/forums/dload ... le_id=4696
https://www.hifi-remote.com/forums/dload ... le_id=4695

binky123 · Post by **binky123** » Wed Jun 27, 2007 3:29 pm

I looked at remotemaster's protocols.ini and there is a variant 3 for the HCS08 JP1.2 I've uploaded a new RDF that has 0092:3 in the [Protocols] section. Please rebuild your upgrade by reselecting the replay protcol and making sure the fixed data is 6 bytes A9 30 55 56 55 55. Your current fixed data is E0 01. I've also made the RDF changes to the 3000 and 3033 Atlas RDFs.

speaker.guy · Post by **speaker.guy** » Wed Jun 27, 2007 4:02 pm

OK. I'm dense! Where are the new files??
Found it. But it does have the underscores instead of spaces!

speaker.guy · Post by **speaker.guy** » Wed Jun 27, 2007 4:24 pm

It communicates now, but it appears that some of the buttons are scrambled. So far, I have only seen that channel+, channel- and Settings
are wrong. Channel + does Return to live, channel - does replay, settings does some strange channel display thing, and so on. Numbers are OK. So the rdf still is apparently not ready for prime time!
Thank you very much for aall your efforts today

speaker.guy · Post by **speaker.guy** » Wed Jun 27, 2007 9:25 pm

BTW: I attempted to learn signals that weren't working, and I got garbage.

binky123 · Post by **binky123** » Wed Jun 27, 2007 10:21 pm

Once again, the issue with the underscores is IE. I'm using FireFox to upload/download and I don't see the underscores.

If some of the buttons are not mapped correctly, it might be your device upgrade. Cross reference the IR7 device upgrade keycode list and button with what is listed in RM.

speaker.guy · Post by **speaker.guy** » Wed Jun 27, 2007 10:41 pm

Cross reference-they are identical...

binky123 · Post by **binky123** » Thu Jun 28, 2007 7:57 am

You'll have to upload your .IR and RMDU file and I'll load it in and see what's going on. List what buttons work or don't work or what symptoms you see.

speaker.guy · Post by **speaker.guy** » Thu Jun 28, 2007 8:50 am

I will do a button by button today and document ALL of the bad ones...
Thank you again!

speaker.guy · Post by **speaker.guy** » Fri Jun 29, 2007 3:23 pm

https://www.hifi-remote.com/forums/dload ... le_id=4708
https://www.hifi-remote.com/forums/dload ... le_id=4709

RMDU and IR with this result for replayTV0614. Other devices all work correctly. This format doesn't accept spaces....
Button Is

0-9 OK
Mute OK
Chan+ QS
Chan- Replay
Power Live
Play FF
Pause Stop
Rewind Record
FF No obvious action
Stop RG
Rec ?
Source Pause
Select ?
Last Rewind
Info Play
Exit ?
Settings ?
Up Right
Down Info
Left Pwr Off
Right Zones
#/Enter ?
Guide FR
PageUp Info
PageDown Input?
B No obvious action
C Menu
Replay ChannelGuide
List No Obvious Action
Live Info
TuneIn11 Input
? - I'm not sure

But you get the picture

binky123 · Post by **binky123** » Sat Jun 30, 2007 5:57 pm

I looked at RM's list of functions and correlated that list with your list and it seems that the actual function code sent is offset by 3. So for example, find channel + in the functions list and go 3 down and you find Quick Skip.

I loaded your .IR file into my Atlas5 and used the URC-10820 and it learned the correct code(Play==Play OBC/EFC in RM's list). Learned on Atlas5 3000 remote and it also learned the correct code(Play==Play).

Try changing the setup code to 1612 to see if that makes a difference.

I'm using RM v1.78 Java 1.5.0_08. IR7.03.

speaker.guy · Post by **speaker.guy** » Sat Jun 30, 2007 11:18 pm

All of my Atlas are not learning.
Why do we have that 3 offset?
Can I alter my function table in RTM to make it work?
What is the significance of setup code 1612?
Thanks for the help...
I will try something tomorrow.

speaker.guy · Post by **speaker.guy** » Sat Jun 30, 2007 11:40 pm

1612 by itself didn't do anything. I notice that a vol up and vol down function appear in IR with a hex of 00, but have an efc. In the rm, they have both values, but have no meaning. I tried deleting them in the RM function list, but they still appear incorrectly in IR. Also efc appearing in IR are not the 5 digit code required by the remote. Are these anomalies that need attention?

johnsfine · Post by **johnsfine** » Sun Jul 01, 2007 7:24 am

speaker.guy wrote:I notice that a vol up and vol down function appear in IR with a hex of 00, but have an efc. In the rm, they have both values, but have no meaning. I tried deleting them in the RM function list, but they still appear incorrectly in IR.

The vol+, vol-, and mute keys are grouped. The remote cannot have any one of those three defined without having all three defined. If you tell RM to put a function on Mute but not on the two Vol keys, it has to put something on the two Vol keys.

speaker.guy wrote:Also efc appearing in IR are not the 5 digit code required by the remote. Are these anomalies that need attention?

The remote does not use EFC numbers inside device upgrades. IR.exe shows you EFC numbers for functions within an upgrade (but translating from the info that is really there) just to help you compare those functions to functions you may see elsewhere (such as decodes of learned signals). In most cases, I think a three digit EFC is the form that would make the signal easiest to compare to external data. I don't know whether IR.exe still shows that as three digits in cases where three digits won't compare meaningfully, and if so, I don't know whether that is worth the effort of the IR maintainer to improve.