Re: [misterhouse-users] Automatic CM11A reset upon lockup?

[Pete F. <pj...@ca...>]

I use quite a few of the MR26's (only a couple actually transmit ot a
reciever but they are relatively busy ones(and out of CM17 range)). I
havn't noticed any lockups for a really long time

Or 

How about a heartbeat using the cm17 to transmit a short series of codes
(say P1ON P1DIM P1DIM ) every few (3*) minutes IF there hasn't been any
activity ( X10 recieve) for say 3* minutes.
That way the series ( or any part thereof) being received would indicate
that the CM11 was ok, and the the transmit timer would be reset on ANY
X10 incoming ( thus reducing chatter to quiet times and self resetting
in fairly short order)

* pick an interval that is offbeat to the usual timers say
3,13,22...minutes

On Wed, 2003-09-24 at 20:00, Gary Sanders wrote:
> I've been attempting to devise a method to automatically reset my CM11A 
> when it decides to lock itself up. This usually occurs when we have a 
> short-duration power failure.
> 
> As most folks know, an easy way to reset a locked-up CM11A is to simply 
> transmit an X10 code from another transmitter. This is received by the 
> CM11, and in practically all cases I've seen, the CM11 then operates 
> normally (at least until the next time :) ).
> 
> So far, what I've done is the following:
> 
> I created an entry in items.mht called reset_cm11, on code P1, utilizing 
> the CM17 interface.
> 
> I wrote a simple script to set $reset_cm11 'ON', then 'OFF' once an 
> hour. THis is transmitted by the CM17 via rf to a transceiver, which 
> passes it on to the power line.
> 
> The script works as expected, but of course the problem is the CM11 
> could remain locked up for as much as an hour before getting reset.
> 
> I really would prefer a method where the reset attempt would happen as 
> soon as the system became aware of a possible locked-up CM11.
> 
> One indication of a locked-up CM11 is the following partial log entry,
> "Bad checksum in CM11 send:" when an attempt is made to transmit via the 
> cm11.
> 
> I found that this entry is generated by cm11.pm here:
> 
>      if ($checksum != $data_d) {
>          print "Bad checksum in cm11 send: cs1=$checksum cs2=$data_d. 
> Will retry\n";
>          goto RETRY if $retry_cnt++ < 3;
>      }
> 
> I thought I could simply insert two lines setting $reset_cm11 ON and 
> then OFF, after the print statement, which would reset the CM11, then 
> retry the transmission.
> 
> I use a proxy for X10, so it didn't work, I assume because the proxy 
> wasn't aware of the $reset_cm11 variable.
> 
> Any ideas on how I can resolve this, and automate reset of the CM11?
> 
> Gary Sanders
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> ________________________________________________________
> To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365
-- 
--------------
"No trees were killed in the sending of this message. However, a
large number of electrons were terribly inconvenienced." 
   Author unknown 
--------------
-Pete Flaherty
pj...@ca...
http://vsa.cape.com/~pjf/MrAudrey.html