Page 1 of 1

8910/9910 extender documentation error?

Posted: Tue Dec 28, 2004 7:37 pm
by Capn Trips
The Read Me for the 8910/9910 extender seems to refer to a different remote than an 8910 when it discusses Keysets.

The readme says:
KEY SETS:
=========

Trans = Rew, Play, FFwd, Rec, Stop, Pause
Vol = Vol+, Vol-, Mute
Chan = Ch+, CH-, digits, Enter, Last, Sleep, Info, TV/Video
Menu = Menu, Guide, Up, Down, Left, Right, Select, Exit
PIP = Pip, Freeze, Swap, Move, +100
Other = P{Setup}, {Light}, Power, Fav/Scan, device keys, phantoms
This overlooks the "M" and "L" keys, "Com Skip" and "F.Rew" and F.Fwd" and includes mythical keys like "Freeze" and "+100". Further, some keys are improperly named ("Last" vs. "Prev"; "P" vs. "set"), which leads me to suspect this is simply a cut/paste from another readme.

I can guess where most of the keys go, but am not sure. Can someone please clarify what keys are in what keysets in this extender?

Posted: Sat Jan 01, 2005 3:08 pm
by Capn Trips
Bump!

Anybody home?

Bueller? Bueller?

Since I've been playing with the extender and IR a bit longer, a follow-up question:

Does the Dev_cancel command only appply to the currently running nested macro in which it appears? or does it cancel all previous Dev commands, relegating subsequent commands within the sequence to rely on the current Dev_X, Set_xxx_Keys setting?

I'd appreciate a reply from the extender author.

Posted: Sat Jan 01, 2005 3:48 pm
by johnsfine
Capn Trips wrote: Does the Dev_cancel command only appply to the currently running nested macro in which it appears? or does it cancel all previous Dev commands, relegating subsequent commands within the sequence to rely on the current Dev_X, Set_xxx_Keys setting?
At most one Dev_ command is active. When that is canceled the extender does revert to the normal device processing based on the Set_xxx commands.

Also, as you nest macros, the extender remembers only the single list of pending keys. It does not remember which macro it's executing nor what level it's nested to. It has no idea where a nested macro ends and the calling macro resumes. Nesting a macro just means that it replaces (within the pending list) the keycode invoking that macro with the list of keycodes from that macro definition.
Capn Trips wrote:I'd appreciate a reply from the extender author.
Maybe you'll get one. I didn't write that extender (nor ever used it) but I understand it enough to answer these questions.

Posted: Sat Jan 01, 2005 9:25 pm
by The Robman
It sounds like those keys are reffering to the 15-2116, which is very similar internally to the URC-8910. The author of both extenders is David Vasquez.

Posted: Sun Jan 02, 2005 11:46 am
by vasqued2
Here's the key mappings as described in the manual for the 8910. Well almost. It looks like One For All copied from the 2116 manual too. They still reference the Last Key instead of the Prev key. :-)

Trans = Rew, F.REW, Play, Fwd, FFwd, Rec, Stop, Pause
Vol = Vol+, Vol-, Mute
Chan = Ch+, CH-, digits, Enter, Prev, Sleep, Info, TV/Video
Menu = Menu, Guide, Up, Down, Left, Right, Select, Exit
PIP = Pip, Swap, Move
Other = Set, {Light}, Power, Fav, M1, M1, M3, L1, L2, L3, L4,
device keys, phantoms

As John stated, the Dev_Cancel only cancels a temporary active device set in a macro. There is no 'device stack', so it's not like Dev_Cancel is popping a previous device setting off of the stack. It just goes back to whatever was defined w/ the Set_xxx_Keys.

David