View previous topic :: View next topic |
Author |
Message |
mdavej Expert
Joined: 08 Oct 2003 Posts: 4501
|
Posted: Fri Oct 10, 2008 9:17 am Post subject: Multiplexer in unextended Atlas 3033 |
|
|
What's the device and protocol code? Is there I way to get it from the special protocol spreadsheet? If so, what remote should I pick? Or can I just change the 5th byte in the protocol code? Alternately, could I just use the code from the extender?
Thanks |
|
Back to top |
|
|
binky123 Expert
Joined: 14 Feb 2004 Posts: 1292
|
Posted: Fri Oct 10, 2008 9:51 am Post subject: |
|
|
Usually, device multiplexor is protocol 01FE as specified in the RDF. If protocol 01FE is loaded, the Special Protocols entry is enabled in IR.exe. However, for the Atlas 3000 and 3033, the normal multiplexor of changing the RAM version of the device setup codes doesn't work anymore as the remote loads it in from EEPROM on every keypress. To make it work on an unextended remote, you'd have to change the RAM version and then update the EEPROM. |
|
Back to top |
|
|
mdavej Expert
Joined: 08 Oct 2003 Posts: 4501
|
Posted: Fri Oct 10, 2008 10:26 am Post subject: |
|
|
I see. Thanks. |
|
Back to top |
|
|
unclemiltie Expert
Joined: 21 Jan 2004 Posts: 1795 Location: Pittsburgh, PA |
Posted: Fri Oct 10, 2008 7:04 pm Post subject: |
|
|
Dave
Binky is right on this one, there really is no way to get the Atlas (and RS 15-13x) remotes to deal with the multiplexor unless it's using the extender.
The base remote reads the setup info for every keypress (unlike the older JP1 remotes which read it only at startup) so the multiplexor can't work without some surgery on the base remote.
The exender "patches" the base remote to skip over the read of the setup information on every keypress, which is why this works in the extender. The patches are done during extender activation (and restores are done during deactivation)
-bill _________________ this JP1 stuff is a sickness! |
|
Back to top |
|
|
|