Re: [mh] runaway condition

[Matthew C. <dv...@gm...>]

I have a couple old TMs still installed and running, no problems seen.

Matt
 On Feb 9, 2011 6:24 PM, "Ron Blout" <rb...@be...> wrote:
>
> "Ron Blout" <rb...@be...> wrote in message
> news:iivcte$f2l$1...@do......
>> "mh" has been running flawlessly for the last two days using a usb PLM.
>> Today I added in a . followed the
>> instruction in the weki to link and all seemed fine. I could control the
>> X10 devices and a light plugged into the 2457D2. Left home for about an
>> hour. Upon return I noticed that lights were not on.
>>
>> It seems that "mh" is in a runaway state.
>> the start up looks clean.
>>
>> here are the errors in the print log:
>>
>> 2/09/11 19:41:07 X10: Got XMM, but cannot dim anything because no prior
>> device was actuated for house code M
>> 02/09/11 19:41:07 [Insteon_PLM] received x10 data: XMM
>> 02/09/11 19:41:08 [Insteon_PLM] Parsing serial data: 02520480
>> 02/09/11 19:41:08 X10: Got XMM, but cannot dim anything because no prior
>> device was actuated for house code M
>> 02/09/11 19:41:08 X10: Unmatched incoming data_chunk=XM ( )
>> 02/09/11 19:41:08 [Insteon_PLM] received x10 data: XMM
>> 02/09/11 19:41:08 [Insteon_PLM] Parsing serial data: 02520480
>> 02/09/11 19:41:08 X10: Got XMM, but cannot dim anything because no prior
>> device was actuated for house code M
>> 02/09/11 19:41:08 X10: Unmatched incoming data=XMM
>> 02/09/11 19:41:08 [Insteon_PLM] Parsing serial data: 15
>> 02/09/11 19:41:08 [Insteon_PLM] Interface extremely busy. Resending
>> command
>> after delaying for 1 second
>> 02/09/11 19:41:08 [Insteon_PLM] Parsing serial data: 02520480
>> 02/09/11 19:41:09 [Insteon_PLM] Parsing serial data: 02520480
>> 02/09/11 19:41:09 [Insteon_PLM] Parsing serial data: 02520480
>> 02/09/11 19:41:09 [Insteon_PLM] Parsing serial data: 15
>> 02/09/11 19:41:09 [Insteon_PLM] Interface extremely busy. Resending
>> command
>> after delaying for 1 second
>> 02/09/11 19:41:10 [Insteon_PLM] Parsing serial data: 02520480
>> 02/09/11 19:41:10 [Insteon_PLM] Parsing serial data: 02520480
>> 02/09/11 19:41:10 [Insteon_PLM] Parsing serial data: 02520480
>> 02/09/11 19:41:10 [Insteon_PLM] Parsing serial data: 15
>> 02/09/11 19:41:10 [Insteon_PLM] Interface extremely busy. Resending
>> command
>> after delaying for 1 second
>> 02/09/11 19:41:11 [Insteon_PLM] Parsing serial data: 02520480
>> 02/09/11 19:41:11 [Insteon_PLM] Parsing serial data: 02520480
>>
> The above errors seem to have been caused by a "stuck" TM751.
> What follows is the scenario I went through. I publish this in the hopes
> that it will
> be beneficial to others.
>
> I unpluged the PLM, waited 10 seconds. Pressing and holding the set button

> I
> plugged the PLM back into the wall while continuing to hold the set button

> for
> another 3 or so seconds.
>
> Restarted "mh". This time there was an error in startup having to do with
> /dev/ttyUSB0. It no longer existed. Unplugged the PLM's usb cable from
> the pc and replugged. /dev/ttyUSB0 restored. Restared "mh". Above errors
> continued. I unplugged
> 4 of the 5 TM751 X10 modules. Above errors continued. Finally I got to
> the last
> remaining TM751 hit its "on/off" button. No good. Errors continued.
> Unplugged it
> errors STOPPED. No more TM751s are plugged in but this will have an effect
> on motion stuff. Able to control X10 devices and the insteon dual band
> #2457D2 lamplinc
> device. I plugged in the 5th TM751 that was causing me the problem and so
> far all
> is quiet. I will replug the remaining ones tomorrow.
>
> Is the TM751 prolematic with INSTEON? Has anyone experienced this.
>
> I have been running these TM751 for years with 32bit "mh" on a CM11A
> controller
> without issues.
>
>> the only device I have with house code M is in a custom script. The
>> device
>> is an X10 appliance
>> ($audible_alarm = new X10_Appliance('M16');)
>>
>> I have disabled this script in the custom code section and tried
resetting
>> the PLM from the web page. Removed the dual band lamplinc dimmer. And
>> still the problem continues.
>>
>> I stuck. Any ideas.
>>
>>
>>
>>
------------------------------------------------------------------------------
>> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
>> Pinpoint memory and threading errors before they happen.
>> Find and fix more than 250 security defects in the development cycle.
>> Locate bottlenecks in serial and parallel code that limit performance.
>> http://p.sf.net/sfu/intel-dev2devfeb
>> ________________________________________________________
>> To unsubscribe from this list, go to:
>> http://sourceforge.net/mail/?group_id=1365
>>
>>
>
>
>
>
------------------------------------------------------------------------------
> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> ________________________________________________________
> To unsubscribe from this list, go to:
http://sourceforge.net/mail/?group_id=1365
>