The Buster PiX10Hub is here! Created by the Community, for the Community.
Since the version of 3.236 you are using is not the US one, but the Marmitek one, there are significant differences. Try giving each .ahx file a different, distinctive name. I've never seen the US/Canada version of AHP ever do what you posted on a reboot of the PC.Does Marmitek run a board similar to this one, see if any of the Marmitek users across the pond have ever had that problem before.
Ver 3.204:When a LM14a is activated from the desktop the desktop status is correct and Activity Monitor shows the outgoing extended Code commandWhen a macro that uses a LM14a is executed - if the macro uses a dim or bright command (extended code) the outgoing command is not shown in activity monitor and the desktop status is not updated. Note that the LM14a status is updated if you issue a simple ON/OFF command (uses standard command formats). The upshot is that if you are using a dim/bright command with a LM14a (extended code) in a macro, you cannot use the "device status" command in smart macros to qualify macro execution. Ver 3.228:When a LM14a is activated from the desktop the desktop status is correct and Activity Monitor shows the outgoing extended Code command - so far so goodWhen a macro that uses a LM14a is executed - if the macro uses a dim or bright command (extended code) the outgoing command is shown in activity monitor, but it is shown at the module address +1.. To be more specific, if a macro issues a bright 90% to A1 the desktop icon for A2 will turn on and indicate 90%. Activity monitor also shows the A2 module extended code command. Meanwhile, the lamp at A1 responds properly and my testerlinc indicates an extended code command to A1 (as it should). The above could at best be referred to as "backward progress". The incorrect interpretation of the extended codes now affect other units that were functioning properly.On to 3.236:LM14a Desktop functions properly - so far so goodLM14a Macro functions are indicated properly within activity monitor and display properly on the desktop. Unfortunately, although the desktop status is updated, the "monitored status" for the LM14a remains "off" when using bright commands. This means that you won't be able to use the smart macro "device status" command with the LM14a interfaced modules.Nonetheless, 3.236 is an improvement. I am not sure what other changes were made in going from 3.228 to 3.236, but if you are using LM14a interfaces, the 3.236 seems to function far better.
Since the version of 3.236 you are using is not the US one, but the Marmitek one, there are significant differences.
The only 3.236 on the X10 site is this one: Version Size Primary Alternate3.236 - Released Sept 05, 2008 - Windows XP, 2000 1.0MB x10drivers.exe x10drivers.exe For XRay Vision, MultiView, WebView, Vanguard, Sentinel, iWatchout, and ShowTime.It's not Marmitek, where is that version available here?
...so it was 140 when I posted this - how high can it go?
For those wishing to Update here is the link: AHP_3.236Note: This is from X10 USA not the European version