Re: [mh] Insteon PLM Error

[Rick B. <ric...@gm...>]

Also... is the PLM transmitting to both X10 and PLM devices on your 
house wiring?

One hypothesis I have is that the PLM becomes "latched" switching 
between the X10 xmitter and the Insteon xmitter (although I don't have a 
schematic of the PLM nor its' firmware code). On occasion I've seen the 
~"PLM extreamely busy" message precede the freeze... and I don't have a 
busy configuration at the moment, with only one insteon switch in the 
mix w/~5 X10 switches.

Lastly, the one time I had (intrusive) software serial monitoring in 
place (my current sniffer config is non-intrusive), and experienced the 
freeze, the PLM was returning a stream of 0xFC (or 0xF<something>).  I 
don't believe this stream appeared in the Insteon logging within MH.

I'm in a much better position to capture what happens "on-the-wire" 
now... if I could only repro.

Rick

Troy Carpenter wrote:
> Rick Bolen wrote:
>   
>> I've been experiencing a similar situation for several weeks now. I 
>> currently have a serial sniffer in place waiting for this to recur, but 
>> so far, no dice.
>>
>> I have a TED energy monitor communicating on my house wiring, and it is 
>> relatively chatty. I'm wondering what, if any, contribution it makes to 
>> the issue.
>>
>> Are you running any other communication devices over your house wiring 
>> besides Insteon? Compact flourescents? Motors? Other things that 
>> generate hf hash?
>>
>>   
>>     
> I only have two devices that transmit X10 on the powerline other than 
> the Insteon PLM, and even those only transmit via manual interaction 
> either in the morning or before bedtime.
>
>   
>> I haven't tried detecting the condition and and attempting recovery. 
>> There is a plm_reset command, but I dont' know the proper syntax for 
>> its' use... and until I can repro at will, I don't think I can test it 
>> with confidence.
>>
>>   
>>     
> I may have to look at that command and see if it will recover the system 
> from this condition. Once it happens, no commands go out on the 
> powerline and it appears the system is dead for all intents an purposes, 
> especially when it appears the system doesn't respond to any of the 
> motion sensors.
>
>   
>> I also don't know the best way to avoid memory leaks cause I don't know 
>> how to best destroy the plm serial object during runtime to avoid leaks.
>>
>> Rick
>>
>>
>> Troy Carpenter wrote:
>>   
>>     
>>> I'm seeing the following message after about a day of MH running.  
>>>
>>> WARN: No acknowledgement from PLM to last command requires forced abort of 
>>> current command. This may reflect a problem with your environment.
>>>
>>> When this happens, no traffic goes in or out of the PLM. 
>>>     
>>>       
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> ________________________________________________________
> To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365
>
>