From: Hans, David M <David.Hans@MW.Boeing.com> - 2000-01-26 19:00:28
I was having a problem using a X10 light module at address D5. Seems that
sending a 'D5' word generates a 0xa5 checksum which then sets the clock.
There is a check in the send routine that seems to recognize that this might
happen, but the read routine has already detected it and responded. I
commented out the if ($datad_d == 165) block in read and it solved my
problem but I think that needs to be moved to somewhere else in case I ever
do get a powerfail.
Has anyone else seen this? I just joined the maillist and I didn't look
too far back, but I didn't see this mentioned.
Linux is my hobby and passion
From: Bruce Winter <bruce@mi...> - 2000-01-29 20:16:12
> I was having a problem using a X10 light module at address D5.
> Seems that
> sending a 'D5' word generates a 0xa5 checksum which then sets the clock.
We ran into a similar problem last march with a DIM-30 command. In that
case it cased a loop in CM11, so the problem stood out a bit more!
I just updated CM11.pm to fix this problem. It now turns of the check for
the clock reset flag whenever it is looking for checksums.
You can pick up CM11.pm version 2.08 here: