RDF Sync 3 file for Sc Atlanta AT2000 4 device remote

[mr_d_p_gumby]

I see where you are going with this (macros). Basically if we know which 15 buttons i assigned to a macro then we will be able to decipher each buttons hex value??

Yes.

when i do a file difference between these two I see that there are 4 bytes that change. The bytes that change on 3250hd are: 0000 (0x94 to 0xe4), 0001 (0x6b to 0x1b), 0014 (0x07 to 0xf7), and 0015 (0x80 to 0x00). The change you made to the rdf is affecting 00, 01, and 15... 15 is ok, and it looks like 00 and 01 are reversed (14 EB, instead of E4 1B) and you are missing the change to address 14.

The bytes at 0000 and 0001 are a checksum, and will change when almost any byte changes. The byte at 0015 looks like it controls the Master Power option, but as I said, I need you to test this on the remote. I'm not sure if the change to byte 0014 is needed or not. If so, it will have to be listed as a separate option in the RDF, since each option can only modify the bits in one byte.

[new-guy]

is there a tutorial or some document somewhere that explains everything in the RDF file... ?? I am trying to figure stuff out so I can understand it all and it is not that easy when you dont know what expect and where to expect it....

[gfb107]

There is the RDF3Spec.doc that is included in the IR600.zip file.

[new-guy]

The byte at 0015 looks like it controls the Master Power option, but as I said, I need you to test this on the remote. I'm not sure if the change to byte 0014 is needed or not. If so, it will have to be listed as a separate option in the RDF, since each option can only modify the bits in one byte.

I have a hunch about 0014.... I will try some experiments to help confirm this later (looks like I wont get to experiment until thursday evening). I believe that this offset determines which components will be powered on/off. I had one IR file which i never included as it was messed up... I had done a lot changes and it was just a mess. Long story short, I opened that file in IR with the new RDF and was able to reverse the chaos... comparing to my base file again the difference was only in 14 and 15. I had programmed the remote to do master power on TV, CBL, and AUX, NO VCR.... When I had it power all components 0014 went from $07 to $F7. With no vcr 0014 was $D7. When expressed in binary this is 1111 (F) and 1101 (D). SO i am guessing that each bit in represents a component. I can play around with the 998 code and figure out what bit controls what component, or at least verify my theory... does my logic here make sense? do any other JP1 remotes work this way?

[new-guy]

I am catching on with the RDF file... I made these changes in [settings], though not sure if it is what is needed....

Power on CBL=$014.7.1.1.0 (No;Yes)
Power on TV=$014.6.1.1.0 (No;Yes)
Power on VCR=$014.5.1.1.0 (No;Yes)
Power on AUX=$014.4.1.1.0 (No;Yes)

I am guessing which bit is used for what except for VCR... from my other file I am sure its bit is correct

[new-guy]

I was looking at my IR files and I noticed something that is not included or mentioned in the RDF... maybe somebody can explain...

On all my IR files I have the same data at offset $0300 ($41, $51) (ASCII A P)... does this mean anything? If i open ir and select the RDF this is not included in the raw data...
Another thing, when I had been last playing around with my remote I was trying to assign volume punch through either to my TV or Receiver (AUX). When i set it to AUX the remote will blink 2x indicating it was programmed correctly... when I try to program it for the TV it will give one long blink, as though it didnt like that selection....

[new-guy]

On all my IR files I have the same data at offset $0300 ($41, $51) (ASCII A P)... does this mean anything? If i open ir and select the RDF this is not included in the raw data...

OK... i have updated my zip file. I discovered lots of stuff. I used the macro function to capture every key except for "select". This key is what the remote would use to finalize or complete the macro program and so i could never capture it... I guess i could have done a keymove..
I also discovered the 981 command, so the files in the zip are based on a factory reset. I also discovered why i could not do volume control on other components.. apparantly I had locked it to the CBL component with a 993 command. I think in the RDF master power and VPT are reversed.. not sure....

SO what is the next step? and what about my previous question which is quoted here?

Here is my new file

thanks

[mr_d_p_gumby]

On all my IR files I have the same data at offset $0300 ($41, $51) (ASCII A P)... does this mean anything? If i open ir and select the RDF this is not included in the raw data...

and what about my previous question which is quoted here?

I don't think those bytes are significant. They're probably just left-over data. You should start with a "clean" EEPROM by using the Advanced|Initialize to $FF option in IR, uploading to the remote, doing a 981-reset, then downloading and saving the result as a blank starting point for further experimentation.

...every key except for "select". This key is what the remote would use to finalize or complete the macro program and so i could never capture it... I guess i could have done a keymove..

Yes, you can either assign a keymove or a macro to the select button, and then find the hex code that way.

I think in the RDF master power and VPT are reversed.. not sure....

You'll need to be a little more specific if we're to help you with this. Do the RDF settings control the correct options? If so, is On/Off reversed?

[new-guy]

I think in the RDF master power and VPT are reversed.. not sure....

You'll need to be a little more specific if we're to help you with this. Do the RDF settings control the correct options? If so, is On/Off reversed?

I maybe did not express myself the proper way... what I meant to say is that "master power" is indicating VPT status... I noticed this after I did the 981 reset and then started playing with volume punch through. If you do a comparison with the files i sent.. take a look at "981-pluscomponents" and compare to "993-auxvolumectrl" (filenames may not be exactly correct). In that 993 file no matter what setting I am in the volume will be controlled on the AUX device. Then when you look at "993-volume-locked-out" the status bit is different... this last 993 the volume was locked into cbl mode. No matter what i did to change it would not work. I looked in the manual and there is a snippet about unlocking components.. once i did that I could change it. Interesting, when locked out and I would try the 993 to get AUX control the remote would blink 2x as if it was accepted... but when i would download the data it still indicated CBL control...



BTW- thanks a ton for the help so far. sorry if i seem impatient sometimes but this is cool and am getting really into this

[new-guy]

...every key except for "select". This key is what the remote would use to finalize or complete the macro program and so i could never capture it... I guess i could have done a keymove..

Yes, you can either assign a keymove or a macro to the select button, and then find the hex code that way.

I tried doing a keymove and a macro with the select button but was not able to ... The select key seems to be only available in CBL mode. When in any other mode pressing it does not light the LED. I noticed this also with the A B C keys (triangle square circle). I even tried doing a keymove from CBL mode to TV mode and all i got was a single long blink. I think it may be due to the fact that the "select" key is also used as a setup key. To start any command i need to hit "select" plus a component key until the LED blinks twice.. I noticed for macros to finish off the macro i just needed to hit "select"... i didnt need to hit it with the component key.
once we get things going, will it be possible to enable these keys in the other modes?? I am thinking it would be nice to use some of these as discrete buttons in other modes...

[mr_d_p_gumby]

I think it may be due to the fact that the "select" key is also used as a setup key. To start any command i need to hit "select" plus a component key until the LED blinks twice.

UEI has done this before on other OEM remotes, so you're probably correct that you can't make a keymove for the select button on the remote. We'll set it aside for now. There are other methods we can use to identify key codes, but they are more involved. Your best bet at this point is to follow up on the PM I sent you. The A, B, C & Select buttons will be contained in the Cable keymap, so once we know that we can narrow them down to a few possibilities.

[new-guy]

On all my IR files I have the same data at offset $0300 ($41, $51) (ASCII A P)... does this mean anything? If i open ir and select the RDF this is not included in the raw data...

and what about my previous question which is quoted here?

I don't think those bytes are significant. They're probably just left-over data. You should start with a "clean" EEPROM by using the Advanced|Initialize to $FF option in IR, uploading to the remote, doing a 981-reset, then downloading and saving the result as a blank starting point for further experimentation.

SO I set these two byte to FF and uploaded to the remote. I downloaded to make sure the change stuck and it did.. I then did a 981 reset and downloaded again. The data was once again there...
I am still working on the other experiment we talked about...

[finaddict]

I am in a similar situation in that I too have a Scientific Atlanta AT2000 that I wish to program via the JP1 tools. I purchased a JP1 cable and have read the articles written by Rob Crowe, Don Grovestine and Tommy Tyler. But I have come to the conclusion that I am at a disadvantage with these tutorials for two reasons. First, the AT2000 is not a "learning remote," and Rob Crowe's tutorial only glosses over the ways in which upgrades can be created using non-learning remotes. Second, the AT2000 is not even included in Keymap Master's list of remotes. So, even if I were able to learn the OBC's I still wouldn't be able to create and load an upgrade. It is this latter disadvantage that I hope to get resolved here in this thread.

Now, I understand that the JP1 support group is a volunteer army, but to log in to this thread after two weeks only to discover that nothing new has been posted is agonizing. To recap;

The next step is to identify the key codes for all the buttons on the remote. The easiest way to do this is to create a series of macros. Fill each macro with 15 different buttons. Download into IR (using the RDF I posted), and make a note of the hex key code associated with each button in the macro. It will help if you post the IR file along with your notes, as you did before.

OK... i have updated my zip file. I discovered lots of stuff. I used the macro function to capture every key except for "select". This key is what the remote would use to finalize or complete the macro program and so i could never capture it... I guess i could have done a keymove..
I also discovered the 981 command, so the files in the zip are based on a factory reset. I also discovered why i could not do volume control on other components.. apparantly I had locked it to the CBL component with a 993 command. I think in the RDF master power and VPT are reversed.. not sure....

The dialogue above leaves me with three questions.

1) Are the macros posted by "new-guy" adequate for use in determining the remote's hex codes?

2) If yes, when will the information be made available to readers of this thread? If no, what needs to be done next?

3) What can I do if anything to expedite this process? I don't think it would be any benefit for me to post my IR file at this point since so much effort has already been put into "new-guy's" files, and for me to post my file would be like starting all over again.

[mr_d_p_gumby]

I've posted an updated RDF for this remote, based on work done by new-guy. You can get the file here. The RDF is still to be considered a beta version, but most things should work correctly. We are still working out some of the options on IR's General tab. Also, all of the unused keycodes are listed as "KeyCodeHex??" pending testing for use as phantom keys. We'll have to wait until new-guy gets back from vacation for further work on this.

Second, the AT2000 is not even included in Keymap Master's list of remotes. So, even if I were able to learn the OBC's I still wouldn't be able to create and load an upgrade. It is this latter disadvantage that I hope to get resolved here in this thread.

Once we've got the RDF file finalized, Mark will add the remote to KM. Until then, perhaps you can use RM with the beta RDF, though the results may be bogus until we've confirmed certain aspects of the RDF settings.

Now, I understand that the JP1 support group is a volunteer army, but to log in to this thread after two weeks only to discover that nothing new has been posted is agonizing.

Sometimes that's the nature of the beast. New-guy is on vacation, and we did not know you were waiting for progress on this. Often, in situations like this, much goes on in the background (PMs, emails, etc.) since the back-and-forth details would bore everyone to death.

1) Are the macros posted by "new-guy" adequate for use in determining the remote's hex codes?
2) If yes, when will the information be made available to readers of this thread? If no, what needs to be done next?

I think items 1 and 2 have been taken care of.

3) What can I do if anything to expedite this process?

Give the new RDF a try and let us know your results. Of course, since you are new to JP1, you might want to try walking before running. Test out some keymoves and/or macros. See if the button names in the RDF are correct and all accounted for. Developing an upgrade would be a little more ambitious, but perhaps you could download an existing upgrade for a piece of equipment you own and try modifying it in RM to see if anything works. The picture of the remote used in RM is quite fuzzy, and Nils would need information on the buttons that are not called out yet. Better yet, a cleaner picture of the remote would help, if you have the means.

[7FC]

I tried using the RDU file. I used the RM and the SA40.map does not come out with the right keys.

It seem the PPV and # key does no accept function in AUX position or in TV postion.


The # key for cable is locked for the format change for the HD box.

The rdu file has 5 buttom map while the altas 4 rdu has only 4 button map. I do not know what this mean.

At the end I have to use the extra key to prgramme my DVD into the remote. If I use the RM output - it is allover the place.. my dvd control is Malata dav- 3600.

I also use JVC widescreen code and combo code to look for the some function EFC..

so far ok..