Soft start module use with V3.236We've all been drilled in the fact that the LM14a 2-way lamp module interface should be used when interfacing to the newer "soft start" units. Using the LM14a interface with LM465 lamp modules gets around problems related to the "resume dim" feature. Using the LM14a interface with WS467 (and other) switches gets around problems with the switches not activating in response to a bright/dim command.
Unfortunately, there are still some "gotchas" with this interface.
While V3.236 is a minor improvement over V3.204, it's a huge improvement over V3.228. Original post related to V3.228 is located here:
Changes in V3.236Update 12/22/08: Encountered a number of problems with V3.236 (see following post). At this point I am reverting to 3.204 - it has some problems, but they are problems I know.Problems remaining in the V3.236 implementation of the LM14a interface include:1) The LM14a module interface will not work at the A1 addressIf you configure a LM14a 2-way lamp module at address A1,
and download to the interface, it will function as a normal module (LM465, WS 467) and use standard bright/dim commands. In short - if you use a new Soft Start WS467 at address A1 (AHP interfaced as a LM14a) and try to turn the unit on to 90% -
it will not work! AHP will send a bright 100% command followed by a dim 10% command. The soft start WS467 will not activate in response to the bright 100% - net result is no lamp activity.
Using the LM14a interface at any other housecode/address results in normal extended code operation.
Correction - The above applies to AHP Driver Update 3.236 available here:
Support Software.
The full update of 3.236 does not exhibit this A1 problem. The full update is available here:
http://software.x10.com/pub/applications/activehome/ahp_updt_236.exeIt figures we'd have multiple configurations for V3.236...
2) Cannot monitor status of LM14a modulesAHP cannot monitor the status of a module that uses extended codes. The GUI will update when extended codes are sent, however neither the "on" or "dim" status are updated (Reports/Status). The result is you can't use a "Module Status" command to qualify your macros for a LM14a interfaced unit.
Work around (macro):
Set LM14a ON (note: a simple ON/OFF command will set the status for the unit. It will also activate the unit's resume dim feature).
Set LM14a 90% (this command will be sent as an extended code and will override the resume dim).