I've updated (though not packaged up) the 2117 extender2 to alter the way the backlight works. Details below.
When I've finished what's the process for uploading this to Yahoo. Do I just upload it, or does someone need to check it first?
Details of the change are, by default the light key does nothing and is just another key. A new protocol/device allows the following actions:
(1) Toggle the light on keypress as normal.
(2) Activate the light on keypress.
(3) Deactive the light on keypress.
(4) Turn the light on as a one off.
(5) Turn the light off as a one off.
New extender available for 15-2116 & 15-2117
Moderator: Moderators
Since I've not had a response over a couple of days I though I'd upload this to the Diagnosis area.
Normal sort of disclaimers apply, try at your own risk etc. (Not that there is much risk with JP1 just make sure you keep a copy of your original config).
I've updated it slightly beyond my original note. It's all detailed in the readme and protocol notes.
I've added an extra function to toggle the light on/off without changing the flag for light on keypress.
I've put a default macro and keymove in so the light key acts as would be expected without the extender. Clearly these will need to be removed if you want to change the light function.
I've called it extender 3 which is probably exagerating it a bit, since there is only a one byte change to the main loop of extender 2, with most of the work in the protocol.
It's here
If anyone has any comments on the working/not working or details comments on problems/issues with the code please let me know.
Thanks.
Normal sort of disclaimers apply, try at your own risk etc. (Not that there is much risk with JP1 just make sure you keep a copy of your original config).
I've updated it slightly beyond my original note. It's all detailed in the readme and protocol notes.
I've added an extra function to toggle the light on/off without changing the flag for light on keypress.
I've put a default macro and keymove in so the light key acts as would be expected without the extender. Clearly these will need to be removed if you want to change the light function.
I've called it extender 3 which is probably exagerating it a bit, since there is only a one byte change to the main loop of extender 2, with most of the work in the protocol.
It's here
If anyone has any comments on the working/not working or details comments on problems/issues with the code please let me know.
Thanks.
It's great to see someone doing active work on the extender. I was going
to try it out, but then I realized I'm very low on upgrade/protocol memory
and don't have the time to rearrange stuff to be more efficient right now.
How much memory does the protocol take above what ext2 (and included
protocols) already takes up?
to try it out, but then I realized I'm very low on upgrade/protocol memory
and don't have the time to rearrange stuff to be more efficient right now.
How much memory does the protocol take above what ext2 (and included
protocols) already takes up?
-
The Robman
- Site Owner
- Posts: 21886
- Joined: Fri Aug 01, 2003 9:37 am
- Location: Chicago, IL
- Contact:
Thanks for your efforts Paul. Just FYI, I moved your file from the Diagnosis Area over to the Extenders folder (and I updated your link).
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
Good question, I think it's aboutHow much memory does the protocol take above what ext2 (and included
protocols) already takes up?
Protocol 41
Device 7
So 48 total.
Most of this is the protocol, it's easy enough to produce a simplified version though if you only want to do a subset of the functions. Let me know how much space you have and what you need and I'll see if I can give you a cut down version. (e.g. For a protocol to just turn the light on as a one off it would be 10)