JP1 Remotes

MaximusPlank wrote:Ok, the test learns are done and posted here: http://www.hifi-remote.com/forums/dload ... le_id=6104
I got the IR file to load correctly by removing the remote's batteries for a while, then loading the test file. Whew, feel lucky as I had no idea what was going on.

Since you only did learns from the buttons in Cable mode, I was only able to map out the cable mode's keymap, but that may be enough. So far, it matches the original Navigator RDF exactly, so I went ahead and modified the STARTER 4 RDF based on that assumption.

These older remotes are very finicky about the EEPROM contents, and once they decide there's something wrong they will act as if the EEPROM is not there. It can be difficult to get it back to normal, as you have found out. (Next time, try pressing lots of buttons while the batteries are out as it may speed up the process.)

As before, unverified buttons have "__" at the end of their names. I also added a bunch of "Key_XX" buttons that may be usable as phantoms. Watch out for Key_11, Key_12 and Key_13 as they may act strange (they are possible multi-macro buttons).

mr_d_p_gumby wrote:Since you only did learns from the buttons in Cable mode, I was only able to map out the cable mode's keymap, but that may be enough. So far, it matches the original Navigator RDF exactly, so I went ahead and modified the STARTER 4 RDF based on that assumption.

Sorry about that, wasn't sure of the whats or whys so I errored on the side of laziness.
Thank you, I appreciate all your help, I couldn't have done any of this alone. I put the learns from CBL TV VCR and AUX at the same link above and here. Test file was loaded using the Starter2 RDF.

I tried using the latest rdf v4 but could not get the upgrade to operate the intended device. Recently with rdf2 I was able to load an upgrade and get the expected responses from the then known buttons and most of the lower 12. Today I can't get any button to operate with either rdf. I'll leave the test file loaded for now just in case, since it's hit or miss getting it loaded. There's something in the manual stating not to worry about losing upgrades by removing batteries, and maybe that has something to do with the quirky behavior.

Sorry for the confusion about what needed to be done. Those learns confirm that the [ButtonMaps] section of the RDF is exactly the same as the Navigator. They also confirm my guess that the C-TV/VCR key number is correct, so you could remove the "__" at the end.

I'm not sure why the remote is being so difficult. I do know that this was the first series of JP1 remotes, and they can dismiss the entire EEPROM contents if even one byte doesn't make them happy. Your remote is displaying some rather odd characteristics, though. For example, your FF-981-Reset raw download assigns setup code 0000 to all except the OEM device. Normally, some valid default setup codes are assigned. Also, this is the only remote I know of in this series that has a second half signature stored in the EEPROM ("CYC0" at $00FC). However, that signature does not show up in your 981-reset raw download. It only shows up later in other downloads. Maybe you should re-do the whole FF-fill/981 Reset raw download to make sure something didn't go wrong the first time.

The best advice I can offer at this point is to always start changes with a download of a working EEPROM image.

Sorry for the delay, I made the new raw dumps and put them here: Second set FF-981-RAW.zip.

Eventhough RM and IR have stabilized with the new rdf & map, currently the remote is being stubborn and again won't operate the upgrade no matter how simple ie: just using a native upgrade [panasonic tv 0250], IR can't program it. Loading an upgrade of my own won't work anymore either. Now trying to leave the batteries out for a day to see if that changes anything. When writing FF and such, every now and then the remote blinks back 4 times, probably meaning a full "981". I don't have an original image to load but this weekend I will have access to another one of these that's still untouched. I'll get that image and see if that helps things.

every now and then the remote blinks back 4 times, probably meaning a full "981".

This sounds a lot like defective batteries. If the batteries are weak or if they came from the dollar store and are not quite the right size, all of the weird operational problems could be a result.

I would start by totally discharging the remote, and letting it sit over night, and then put new batteries in.

vickyg2003 wrote:

every now and then the remote blinks back 4 times, probably meaning a full "981".

This sounds a lot like defective batteries. If the batteries are weak or if they came from the dollar store and are not quite the right size, all of the weird operational problems could be a result.

That's entirely possible. When you do a 981 reset, the first two blinks indicate that the remote successfully initialized itself, and the second two blinks signify that the EEPROM was initialized. Given the age of this remote, it could be that this particular EEPROM is more sensitive to the battery voltage than normal.

Thanks for the suggestions. I checked the batteries, they all measured +/- 1.57vdc, which was ok but a bit low for alkaline so I tried new ones with the same results. Leaving the batteries out for 24hrs didn't prove any help in clearing the memory.

Upon further, more thorough investigation, some buttons DO work after loading an upgrade. Most that don't work [and used to work before] are the ones we disabled with the test rdf, basically the donut and number buttons and power. I should clarify that rdf2a is the one that 17 of the buttons work, rdf4 has 3 buttons working. All details are in the text doc here along with rdf2a and rdf4.

I got ahold of another of these remotes, still in the packaging and probably never has had batteries installed. I was able to get a raw download from it, also a download letting IR select the rdf and posted them here. Next I tried loading this virgin raw image to the other stubborn remote but it didn't change operability. Buttons from the top down to middle are still not functioning as expected. Maybe this new raw info will help some.