RDF Sync 3 file for Sc Atlanta AT2000 4 device remote

[7FC]

I have to indicate in my last reply that I was using the in-progress version.. I download the beta version and tried. it is much better than the in-progress version.

There are 5 keys that I could never get it to work are the ABC keys and the # and the PPV keys.

Ther are a bunch of keys named hexcodedXXX keys in the beta version..what are these keys??

on dump question...which key is the shift key for the AT-2000 (SA-40).

finally, I tried to setup a macro for the power key ..ie.

with cable device..the power key would press the following sequence
to tuen on both TV and cable box, or turn them off.. am I correct if it is programmed as

POWER=TV;power;cable;power


thx in advance

[mr_d_p_gumby]

Ther are a bunch of keys named hexcodedXXX keys in the beta version..what are these keys??

Also, all of the unused keycodes are listed as "KeyCodeHex??" pending testing for use as phantom keys.

There are 5 keys that I could never get it to work are the ABC keys and the # and the PPV keys

You haven't included enough detail here for me to understand what the problem is, if any.

on dump question...which key is the shift key for the AT-2000 (SA-40)

The shift key on a JP1 remote is the Setup button. If this is one of those remotes that requires you to hold down two buttons to enter a setup code, then you must do the same to enter a shift, which makes it really inconvenient to use.

finally, I tried to setup a macro for the power key ..ie.
with cable device..the power key would press the following sequence
to tuen on both TV and cable box, or turn them off.. am I correct if it is programmed as
POWER=TV;power;cable;power

The macro itself should work, but you can't assign it to the power button, since the macro will keep calling itself. Try:
POWER=TV;Shift-Power;Cable;Shift-Power
This uses a trick we call "shift-cloaking" to prevent the macro calling itself, while still allowing access to the IR command assigned to the Power button.

[7FC]

Hi, Mike,

Thank you for your explanantion.

Regarding tomy second question. I am referring to the A, B ,C keys and the keys PPV/* and the #/enter key.

I have assinged these keys a function unique for each keys. after upload to the remote. These keys does not respond at all the functions I assigned. For an example ..I assigned the # key to be a open/close tray . The DVD wont respond. As this remote does not blink when you press the keys. therefore, I have no way to know whether it has sent any signal..however, if I assign sam function to other FFW for experiment. the DVD repsonded. Therfore the code is correct . It was the key in my case. I wonder anyone else has the same experience.

I will try the shift-power for the macro.

thx in advance, and your patience.

[new-guy]

my experimentation to date has shown me that there are some buttons that are only enabled or usable in cable mode. These include the a b c # and * keys, along with a couple others. This goes for the select key as well.
I dont know if there is a way to free these buttons up using IR (eventually) or if they will also be locked out.
You can verify which buttons are not usable by selecting any mode other than cable (TV, VCR, AUX) and then hit each button one by one. If the light blinks it is good, if not then it is locked.

[mr_d_p_gumby]

You can verify which buttons are not usable by selecting any mode other than cable (TV, VCR, AUX) and then hit each button one by one. If the light blinks it is good, if not then it is locked.

This does not sound like the normal way a UEI remote does the "lock to cable" function. Typically, the locked buttons will output the cable commands regardless of which device is active in the remote. Normally, only the ch+/-, digits and enter/# key are locked to cable. What you are describing seems to indicate that no commands are assigned to those buttons in the non-cable devices, which would I would consider normal for the A, B & C buttons and the enter key. You would have to load an upgrade that has the buttons assigned to functions to test if they work. For that, we need a working RDF, which is currently in progress.

[new-guy]

What you are describing seems to indicate that no commands are assigned to those buttons in the non-cable devices, which would I would consider normal for the A, B & C buttons and the enter key. You would have to load an upgrade that has the buttons assigned to functions to test if they work. For that, we need a working RDF, which is currently in progress.

That makes sense... thanks for the clarification

[7FC]

If Í selected either TV,VCR,or AUX..Ths above keys does noteven blink..

would U like me upd load my IR file for U to take a look??
I donot check my email often..may take sometime

[7FC]

You may take a look and comment..

[new-guy]

First thing I noticed about your power macro..
you dont really need to have a macro for that....
under the general tab, under "other settings" you can select which devices will be turned on/off with the power button. If you select all of them then when you hit the power button it will turn everything on. If you just want a couple components on, then select what you want. To turn anything else on hit the component key (TV, VCR, AUX etc) and then hit the power.

as far as the a b c * # key not working.. we are still figuring that one out.

[new-guy]

7FC

I have made a change to the map file and jpg file for use with RM. You can find both in the file section under tools...
here is a link:

ScExplorer.zip

[finaddict]

An RDF file must be named such that the remote signature is the first part of the name.

Generally speaking, how does one know what a remote's signature is?

I've added an option for Master Power in the RDF.

Where in the RDF file is this feature indicated?

Learning the IR signals this remote sends out for each key would only tell us what the IR signal is for each key. That would provide the information necessary to build a device upgrade that can duplicate the IR signals generated by the remote.

It would not tell us the internal keycodes for the keys, which IR, RM, and KM need to know in order to correctly program macros, keymoves, or device upgrades.

So, we are trying to associate the outgoing IR signals to particular internal keycodes, and coincidentally to particular buttons, correct?

Are these internal keycodes that gfb107 speaks of the same thing as hex codes?

Your best bet at this point is to follow up on the PM I sent you.

Is this PM anything I should be concerned with? It's hard to follow a thread with holes in it.

I am still working on the other experiment we talked about...

?

Better yet, a cleaner picture of the remote would help, if you have the means.

I haven't yet experimented with RM, but nonetheless I wanted to point out that new-guy has included a jpg image in his most recent uploaded file 3250HD.zip.

[mr_d_p_gumby]

An RDF file must be named such that the remote signature is the first part of the name.

Generally speaking, how does one know what a remote's signature is?

The signature is contained within the EEPROM, and can be examined in an IR download. It starts at the third byte, and is usually 8 or 4 bytes long.

I've added an option for Master Power in the RDF.

Where in the RDF file is this feature indicated?

In the [Settings] section.

Learning the IR signals this remote sends out for each key would only tell us what the IR signal is for each key. That would provide the information necessary to build a device upgrade that can duplicate the IR signals generated by the remote.

It would not tell us the internal keycodes for the keys, which IR, RM, and KM need to know in order to correctly program macros, keymoves, or device upgrades.

So, we are trying to associate the outgoing IR signals to particular internal keycodes, and coincidentally to particular buttons, correct?
Are these internal keycodes that gfb107 speaks of the same thing as hex codes?

Learning the IR signals in this case is used as a means of identifying the specific IR signal associated with a specific key. If you know the keycode to which that IR signal is assigned, then you can associate the button name with the keycode by this means.

No, the internal keycodes are not the hex codes Greg refers to. The hex codes are a representation of part of the data needed by the remote to construct the IR signal.

Your best bet at this point is to follow up on the PM I sent you.

Is this PM anything I should be concerned with? It's hard to follow a thread with holes in it.

I am still working on the other experiment we talked about...

?

Better yet, a cleaner picture of the remote would help, if you have the means.

The PM reference was not meant to leave holes in the thread, only to imply that people are working on this. The instructions in the PMs tend to be quite tedious and detailed, and very specific to the remote in question, so repeating them in the forum posts is of dubious benefit.

I haven't yet experimented with RM, but nonetheless I wanted to point out that new-guy has included a jpg image in his most recent uploaded file 3250HD.zip.

Thanks. I have the image file that new-guy posted. When the RDF is ready for release, Nils will include the image as well.

A progress report: We are getting very close to releasing a new version of the RDF file. There are still a few items we need to clear up, but progress is being made. The next release of KM will support the AT2000. Unfortunately, this remote uses a 6805 processor, and it seems I'm the only one around here who knows how to work with these remotes.

[7FC]

thx new-guy for the new map. TI is better looking than what I had done.The # key is not showing up on the map..

My power on macro is not functioing as what I want.. I will try your suggestion sometime...thx

[finaddict]

See if the button names in the RDF are correct and all accounted for.

I've downloaded what I believe to be the most recent RDF [SA40 (Scientific-Atlanta Explorer AT2000 BETA).rdf] for this remote and did a "Download From Remote" using IR. In looking at the resulting information under the Devices tab, I notice that the following buttons are not accounted for: AUX, VCR, TV, CBL, GUIDE, NEXT, PREV, Yellow Triangle "A," Blue Square "B," Red Circle "C," PPV, REWIND, PLAY, FAST FORWARD, PAUSE, STOP, VOD, and one other button the function of which is unkown to me and whose markings have long worn off due to use (it's in the bottom right corner of the number pad next to the nine and the zero). What is the status of the next version of the RDF? Thanks.

[new-guy]

we should have a finalized RDF very soon. I think most of the work on it has been completed..