Page 1 of 1
Should I try Blast upper memory on Insignia 67100?
Posted: Mon Jan 18, 2016 3:28 pm
by jeajea
I have an Insignia 67100 remote with extender 3.03 that has stopped working.
Pressing any button except setup turns on the LED for about 30 seconds. Pressing the setup for 30 seconds doesn’t deactivate the extender. When setup is released the LED comes on for about 30 seconds.
I can still upload to and download from the remote and the downloaded information looks correct.
I uploaded a file with all the devices set to zero and all upgrades, key moves and macros deleted and it still acts the same.
Should I try Blast upper memory or?
Posted: Mon Jan 18, 2016 3:50 pm
by mdavej
That's normal low battery behavior, so try fresh batteries first. Blasting upper memory won't remove the extender and may make matters worse.
Posted: Mon Jan 18, 2016 4:48 pm
by jeajea
I just tried two new alkaline batteries – no change
Batteries measure1.6+ volts
This remote is the model with a backlight
Posted: Mon Jan 18, 2016 9:09 pm
by mdavej
Shoot. I was hoping it was something simple like that. Need to get the heavy hitters involved now.
Posted: Sat Feb 20, 2016 10:17 pm
by jeajea
A big thanks to Bill Jackson who figured out what I needed to do to fix the 67100.
Posted: Wed Feb 24, 2016 11:48 pm
by unclemiltie
The JP1.3 remotes have a number of setup bytes in the EEPROM area above the setup codes and before the advance code start. Not all of them are well understood but if they are not "right" the remote fails to work properly.
Each remote has different bytes in this area so the safest way to ensure your remote is good is to:
1: save a "virgin" version of the RMIR file before you start anything with the remote
2: if you start having issues look at the bytes after the setup codes in the raw data up to the beginning of the advance codes. If they're not what they are in the virgin file then put them back.
That was the case with the remote in this thread. Several of those bytes were wrong causing the remote to not work.
PS. At one point I toyed with putting some "fixed data" into the RDF's that would set these bytes correctly but lost ambition when life got in the way of doing remote hacking. If someone would like to take this on, I can provide you a collection of virgin RMIR files as well as how to tell which bytes need to be set correctly.