JP1 Remotes

It looks like SA40 (Sc Explorer).rdf might be close, but it's a sync 2 format. The three device RDF doesn't seem to help. Where do I go next?

When I try to download from remote this msg appears "The RDF file is not in sync with the version of the program. "etc. The RDF it goes to shows "RDFSync=2" in line 9. I couldn't find any other Sync=2 RDF files, they appear to be RDFSync=3 except for SA40 (Sc Explorer).rdf

The actual remote is a Scientific Atlanta AT2000-4 and it has a JP1 plug already installed in it. Does anybody have an rdcf file that is "close enough" or right on?

have you had any luck with this???
I am also interested in using jp-1 with this same remote...

nosmotnodrog wrote:When I try to download from remote this msg appears "The RDF file is not in sync with the version of the program. "etc. The RDF it goes to shows "RDFSync=2" in line 9. I couldn't find any other Sync=2 RDF files, they appear to be RDFSync=3 except for SA40 (Sc Explorer).rdf

I don't recall the history behind the SA40 RDF file, but it most likely started life as a "starter" RDF that never got completed. Perhaps the original user never followed up on completing it. The issue with starter RDFs is that they are probably not correct, especially in regard to matching the button names up with the button codes.

Having said that, you can certainly go ahead and try to fix this one up and see if it works at all with your remote. Here is the existing General section:

• [General]
  Name=Scientific Atlanta Explorer
  EepromSize=$400
  PunchThruBase=$012
  VPTStatusBit=$013.7.1
  AdvCodeAddr=$018..$0FF
  UpgradeAddr=$100..$3FE
  Processor=6805
  RDFSync=2
  ImageMap=Generic.map

Change it to this, and add the Settings section:

• [General]
  Name=Scientific Atlanta AT2000
  EepromSize=$400
  AdvCodeAddr=$018..$0FF
  UpgradeAddr=$100..$3FE
  Processor=6805
  RDFSync=3
  ImageMap=Generic.map
  
  [Settings]
  VPT Device=$012.6.7.1.0 DeviceButtons
  VPT Status=$013.7.1.0.0 (On;Off)

Add this line to the end of the existing [DeviceTypeAliases]section:

• AUX = CD,Tuner,DAT,Home Auto,Misc Audio,Phono,Amp

I can't promise that anything about this RDF is correct, but the above changes will at least make it compatible with the current version of IR.

While the RDF indicates that this remote uses a 6805 processor, I suspect that may just be a SWAG.

thanks.
I will have to try this.

I made my JP1 cable on friday and i was able to download info off of the remote. I still dont fully understand everything that is happening but i am finding this to be very cool. I will try and remember to post the IR file i downloaded to see if anybody can continue helping me along.

So i tried making the changes you recommended, and saved the file with a different name.
first, when I now make a download it still select the SA40 file. So i Just modified it and it is fine.

Now my second problem is this. When i see what codes were programmed into the remote to control my components, the number does not match what i programmed. For example, I used TV code 0264 for Panasonic Tv, as indicated in manual. But IR shows that it is programmed with 0250. The number is off by 14. I noticed this for all 4 components (including cable box). I am guessing this is obviously an offset issue, but how do I fix it. Also, I thought i set the remote so that volume control is on TV.. this seems to be mixed up in IR as well...
I have uploaded the file here

new-guy wrote:So i tried making the changes you recommended, and saved the file with a different name.
first, when I now make a download it still select the SA40 file. So i Just modified it and it is fine.

An RDF file must be named such that the remote signature is the first part of the name. In this case, that means your RDF must start with "SA40".

new-guy wrote:Now my second problem is this. When i see what codes were programmed into the remote to control my components, the number does not match what i programmed. For example, I used TV code 0264 for Panasonic Tv, as indicated in manual. But IR shows that it is programmed with 0250. The number is off by 14. I noticed this for all 4 components (including cable box). I am guessing this is obviously an offset issue, but how do I fix it.

UEI sometimes applies an offset to the setup codes on OEM remotes. It sounds like this is one of those. In the [General] section of the RDF, add:

• DevCodeOffset = 14

new-guy wrote:Also, I thought i set the remote so that volume control is on TV.. this seems to be mixed up in IR as well...

That is probably because some of the settings in the RDF are not correct, causing IR to display incorrect information. Fixing this will take a little experimentation, but we'll get to that later.

You should also add the following to the RDF right after the [Checksums] section

• # 2nd signature at FC-FF "SA40"
  [FixedData]
  $0FC = $53 $41 $34 $30

The next thing to try is to make a keymove or macro on the remote itself, and then see if it shows correctly in IR so that we can determine if the AdvCodeAddr setting is correct. If possible, start with the remote loaded with the IR file you posted so we can compare the differences.

The manual does not say anything about key moves or macros... all it has is the setup codes for various components....

Should I try to make a macro in IR?

Would it help if I post the pdf of the remote manual? It shows all the codes and it also has a nice picture of the remote. This lets you see all the buttons that are on the remote.
It is 500k pdf, so should I post it in the file section or host it somewhere else? I dont want to be using up server space if it means someone else cannot post their files...

new-guy wrote:The manual does not say anything about key moves or macros... all it has is the setup codes for various components....
Should I try to make a macro in IR?

No, you need to create one on the remote itself since we are not sure that the RDF file is telling IR the correct information about where the data is stored in the EEPROM.

Most of the time keymoves and/or macros will work to some extent, even if not documented. Some of the OEM remotes won't allow macros, some only allow them on certain buttons, some won't allow keymoves, and so on. We won't know much until you try. Look at any of the manuals on Rob's site for instructions on doing the 994 and 995 sequences & just try them on various buttons.

new-guy wrote:Would it help if I post the pdf of the remote manual?

No, it probably won't be of much help at this point.

I will try that.
I just noticed on the manual that I can use a 998 command to turn on TV, CBL, and AUX all at once. I will try that and get the memory dump.
I will also try the 993 command to switch volume control to my receiver and get that memory dump.
I am not sure i fully understand the 994 and 995 commands in the other manuals, but i will give it a try anyways. It will probably take me a few days before I get a chance to do all this.

Hey guys,

I just switched my cable box to the 3250HD and now I have this remote as well the at2000-4. Have either of you made any progress yet? I thought I read in another thread that this remote was not jp1-able.

we are still working on it...
The remote does have the JP1 header and I have been able to successfully download off it.
We are still figuring how everything work on this remote.

Thanks for the update. I'm going to try some of the things suggested in this thread myself too. I'm very new to this so I don't have any particular expertise but I like to fiddle.

I was able to get my previous cable box's remote, the er1, even with its limitations, to do the essential things I needed it to do. I think this one has more potential though.

I have updated my file in the diagnostics area.
The zip file has been updated to include the recent changes to the RDF file and also includes a second ir file.
This second IR file is with the 998 code enabled. This makes the power button turn on/off all 4 components.

I still have not tried using the 994 or 995 code, but will try that as soon as i can.

I just received the cable box and remote yesterday and I was too busy soaking up the HD that I didn't have much time to experiment with the remote. I did however, try entering the 994 code and it gave a acknowledgement response - two blinks, which seems to indicate that the remote accepted the code. I didn't actually do anything afterward so I can't say for sure but the same code on the er1 gave one long blink