Can the activate key be changed from the power key?
Moderator: Moderators
Can the activate key be changed from the power key?
In the various extenders like the 6012 for the 88XX series, can the activation key (TV-Power) be changed to another key via the upgrade? I have a feeling it requires rewriting the assembly code and make a different upgrade for TV/1800 protocol 180? Is it easy to do? The only reason I ask, if the remote somehow needs to be reactivated and I am not around, my wife knows to press the M3 key on my 8810w to reset the HT system without the extender. I want to add the extender to get my addition whole-house audio/video system integrated (my Elan stuff-RECS80-90) without running out of key move memory. If I tell her to press it and wait for the 4 flashes then everything is ok, that would save me the from the raging "b" mode that she inflicts if the remote is not working correctly. Too many steps cause problems for many low-tech family and friends of mine.
The activation key is decided by a KeyMove stored in the old KeyMove area. You don't see it in IR because the RDF file specifies the location of the new KeyMove area.
The assembly code of the extender DOES include that activation KeyMove, even though it is not part of what one would normally think of as the assembler code of the extender. It's included there just as a convenience for programmers porting and modifying the extender.
For a non expert, it is probably easier to modify the KeyMove directly in the eeprom image rather than in the original source code.
To do that, you need to hide the extender's RDF file and then rename a copy of the 6012/8811 etc. ordinary RDF file so it has the filename the extender's RDF is supposed to have. Then if you open the eeprom image file in IR you'll see (and be able to edit) the old KeyMove area. You can edit the KeyMove and change the bound key to whatever you like. Be sure to put the right RDF file back when you're done.
The assembly code of the extender DOES include that activation KeyMove, even though it is not part of what one would normally think of as the assembler code of the extender. It's included there just as a convenience for programmers porting and modifying the extender.
For a non expert, it is probably easier to modify the KeyMove directly in the eeprom image rather than in the original source code.
To do that, you need to hide the extender's RDF file and then rename a copy of the 6012/8811 etc. ordinary RDF file so it has the filename the extender's RDF is supposed to have. Then if you open the eeprom image file in IR you'll see (and be able to edit) the old KeyMove area. You can edit the KeyMove and change the bound key to whatever you like. Be sure to put the right RDF file back when you're done.
I got the keymove section to show the tv-power as the only move and changed the bound key. Now when I revert the RDF's back to their original versions and later make changes using the original extender RDF, will the bound key revert back to power? Or will the change for the activator be permanent for this image file?
It looks like it changes address $0000 and $0001 to $FC & $03 (from $ED & $12) and address $0024 to the mapped key from the move from the device key $03 (power). I can see what the $0024 address does, but on the assembly level, what are the two changes at the first address doing? I'm curious.
Also, does the remote default to TV when/if the extender resets?
It looks like it changes address $0000 and $0001 to $FC & $03 (from $ED & $12) and address $0024 to the mapped key from the move from the device key $03 (power). I can see what the $0024 address does, but on the assembly level, what are the two changes at the first address doing? I'm curious.
Also, does the remote default to TV when/if the extender resets?
No.jetskier wrote:Now when I revert the RDF's back to their original versions and later make changes using the original extender RDF, will the bound key revert back to power?
That's a checksum which changes as a side effect of almost any other change.jetskier wrote: It looks like it changes address $0000 and $0001
So you could use the raw data tab to check or change that, now that you know why physical byte that KeyMove ends up it (which won't change, unlike the locations of ordinary KeyMoves).jetskier wrote:address $0024 to the mapped key from the move from the device key $03 (power).
When the remote resets it does default to TV mode. But if it resets due to a battery glitch or a configuration bug you might press some other device key after the reset and before noticing it is reset, so you might not be able to rely on that default.jetskier wrote: Also, does the remote default to TV when/if the extender resets?
Could you assign the activator keymove (default TV-Power) to a phantom as a bound key on device TV then use a macro on let say key M3 to (TV)(phantomx). So if the remote has not be activated, M3 in any device mode would active it? Then the activate takes control of all of the key after that? Or is the TV 1800 upgrade not setup for that advance of a scheme?When the remote resets it does default to TV mode. But if it resets due to a battery glitch or a configuration bug you might press some other device key after the reset and before noticing it is reset, so you might not be able to rely on that default.
-
Nils_Ekberg
- Expert
- Posts: 1689
- Joined: Sat Aug 02, 2003 2:08 pm
- Location: Near Albany, NY