puzzle from a new user

[Mark E. Perkins-2]

Greetings,
Sorry for the longish post... just want to be sure all relevant info is on
the table.

I'm new to mh and have been doing some light exploring for only a few
days. I've bumped into something I don't understand.

As background, I'm running on Mac OS X 10.4.10 with a Keyspan USA-28X
USB-to-Serial adapter and a CM11 interface. Until now, I have been using
ThinkingHome successfully with this OS and hardware.

With mh, I started out with a simple mh.private.ini:

     cm11_port = /dev/tty.USA28Xb2P2.2
     gd = 0
     tk = 0

When I run mh with that (and whatever default test files that get pulled
in), I see frequent 'cm11 send failed' on the terminal and no action on the
power line (via my TesterLinc). If I start ThinkingHome after starting mh,
the 'cm11 send failed' messages go away, but I get 'cm11 send pc_ok failed'
on occasion (and I see action on the power line).  Better.

Browsing the documentation, I found (under Serial_Item):

  If 'serial_port' is not specified, then:
     For outgoing X10 data, the first valid port from this list is used:
         cm11, cm17, homevision, homebase, Weeder, serial1, serial2, ...

So on a whim, I added this to mh.private.ini:

     serial_port = cm11

Now the complaints are gone, and I see action on the power line that's
consistent with what the default mh test files seem to be doing (i.e., B1
alternates on/off every 30secs).  I can even use the http interface to mh
and change B1->P1 and watch one of my lamps go on and off.  Cool!

So it looks like the serial port is not being opened properly w/o the
'serial_port' line in the .ini file.  But why?  I can't find any
documentation that 'serial_port=whatever' is needed in an ini file, and I
haven't found the place in the mh code where this seems to be handled (I'm
a competent Perl programmer, just not properly immersed in the mh code
yet).  Can someone point me to the right place(s)?  Or should I be fixing
this problem a different way?

Thanks,
Mark

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365

[James Armstrong]

Mark E. Perkins wrote:

>
> When I run mh with that (and whatever default test files that get pulled
> in), I see frequent 'cm11 send failed' on the terminal and no action on the
> power line (via my TesterLinc). If I start ThinkingHome after starting mh,
> the 'cm11 send failed' messages go away, but I get 'cm11 send pc_ok failed'
> on occasion (and I see action on the power line).  Better.
>
> Browsing the documentation, I found (under Serial_Item):
>
>   If 'serial_port' is not specified, then:
>      For outgoing X10 data, the first valid port from this list is used:
>          cm11, cm17, homevision, homebase, Weeder, serial1, serial2, ...
>
> So on a whim, I added this to mh.private.ini:
>
>      serial_port = cm11
>
>  

I wonder if that is what my problem was when I tried to run 2.103, I am
currently stuck at 2.102 because when I tried the 103 version it would
complain about no response from cm11, it would send data and then
timeout. Something had changed between 2.102 and 2.103 that broke it for
me. I just went back and lived with the older version.

- James

> Now the complaints are gone, and I see action on the power line that's
> consistent with what the default mh test files seem to be doing (i.e., B1
> alternates on/off every 30secs).  I can even use the http interface to mh
> and change B1->P1 and watch one of my lamps go on and off.  Cool!
>
> So it looks like the serial port is not being opened properly w/o the
> 'serial_port' line in the .ini file.  But why?  I can't find any
> documentation that 'serial_port=whatever' is needed in an ini file, and I
> haven't found the place in the mh code where this seems to be handled (I'm
> a competent Perl programmer, just not properly immersed in the mh code
> yet).  Can someone point me to the right place(s)?  Or should I be fixing
> this problem a different way?
>
> Thanks,
> Mark
>
>  

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365

[Mark E. Perkins-2]

On 2007/08/31 08:43, James Armstrong wrote:

> Mark E. Perkins wrote:
>> When I run mh with that (and whatever default test files that get pulled
>> in), I see frequent 'cm11 send failed' on the terminal and no action on the
>> power line (via my TesterLinc). If I start ThinkingHome after starting mh,
>> the 'cm11 send failed' messages go away, but I get 'cm11 send pc_ok failed'
>> on occasion (and I see action on the power line).  Better.
>>
>> Browsing the documentation, I found (under Serial_Item):
>>
>>   If 'serial_port' is not specified, then:
>>      For outgoing X10 data, the first valid port from this list is used:
>>          cm11, cm17, homevision, homebase, Weeder, serial1, serial2, ...
>>
>> So on a whim, I added this to mh.private.ini:
>>
>>      serial_port = cm11
>>
>>  
> I wonder if that is what my problem was when I tried to run 2.103, I am
> currently stuck at 2.102 because when I tried the 103 version it would
> complain about no response from cm11, it would send data and then
> timeout. Something had changed between 2.102 and 2.103 that broke it for
> me. I just went back and lived with the older version.

I'll load up 2.102 later and see what happens here.

In the mean time, I added my W800RF32A to the mix; mh.private.ini like so:

    cm11_port   = /dev/tty.USA28Xb2P2.2
    serial_port = cm11

    W800_module  = X10_W800
    W800_port    = /dev/tty.USA28Xb2P1.1
    x10_relay_hc = [p]


Now I see the 'cm11 send failed' messages again (and no action on the power
line).  I do see log messages when I press a button on a remote or when I
fiddle with a door sensor (DS10A) that show what was pressed/opened/closed.
 If I remove the 'serial_port' line, everything seems to behave (none of
these complaints and I see power line activity).  But I'm *not* seeing the
keypad presses (Pn) relayed to the power line.

Am I correct to assume that the above .ini should arrange forwarding of X10
Pn commands to the power line?  Or is that too simple minded?

Thanks,
Mark

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365

[Gregg Liming]

Quoting Mark E. Perkins (8/31/07 6:11 PM):

> In the mean time, I added my W800RF32A to the mix; mh.private.ini like so:
>
>     cm11_port   = /dev/tty.USA28Xb2P2.2
>     serial_port = cm11
>
>     W800_module  = X10_W800
>     W800_port    = /dev/tty.USA28Xb2P1.1
>     x10_relay_hc = [p]
>
>
> Now I see the 'cm11 send failed' messages again (and no action on the power
> line).  I do see log messages when I press a button on a remote or when I
> fiddle with a door sensor (DS10A) that show what was pressed/opened/closed.
>  If I remove the 'serial_port' line, everything seems to behave (none of
> these complaints and I see power line activity).  But I'm *not* seeing the
> keypad presses (Pn) relayed to the power line.
>
> Am I correct to assume that the above .ini should arrange forwarding of X10
> Pn commands to the power line?  Or is that too simple minded?

also need to enable code/common/x10_rf_relay.pl

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365

[Neil Cherry-3]

Mark E. Perkins wrote:

> On 2007/08/31 08:43, James Armstrong wrote:
>> Mark E. Perkins wrote:
>>> When I run mh with that (and whatever default test files that get pulled
>>> in), I see frequent 'cm11 send failed' on the terminal and no action on the
>>> power line (via my TesterLinc). If I start ThinkingHome after starting mh,
>>> the 'cm11 send failed' messages go away, but I get 'cm11 send pc_ok failed'
>>> on occasion (and I see action on the power line).  Better.
>>>
>>> Browsing the documentation, I found (under Serial_Item):
>>>
>>>   If 'serial_port' is not specified, then:
>>>      For outgoing X10 data, the first valid port from this list is used:
>>>          cm11, cm17, homevision, homebase, Weeder, serial1, serial2, ...
>>>
>>> So on a whim, I added this to mh.private.ini:
>>>
>>>      serial_port = cm11
>>>
>>>  
>> I wonder if that is what my problem was when I tried to run 2.103, I am
>> currently stuck at 2.102 because when I tried the 103 version it would
>> complain about no response from cm11, it would send data and then
>> timeout. Something had changed between 2.102 and 2.103 that broke it for
>> me. I just went back and lived with the older version.
>
> I'll load up 2.102 later and see what happens here.
>
> In the mean time, I added my W800RF32A to the mix; mh.private.ini like so:
>
>     cm11_port   = /dev/tty.USA28Xb2P2.2
>     serial_port = cm11

I have 2.103 and I have:

cm11_port = /dev/ttyM0

but I have no serial_port. While the CM11A might be a little
flaky it does work as it's my primary X10 interface (at this
time).

--
Linux Home Automation         Neil Cherry       ncherry@...
http://www.linuxha.com/                         Main site
http://linuxha.blogspot.com/                    My HA Blog
Author of:     Linux Smart Homes For Dummies

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365

[Mark E. Perkins-2]

On 2007/08/31 18:25, Gregg Liming wrote:
> Quoting Mark E. Perkins (8/31/07 6:11 PM):
>
>> Am I correct to assume that the above .ini should arrange forwarding of X10
>> Pn commands to the power line?  Or is that too simple minded?
>
> also need to enable code/common/x10_rf_relay.pl

Right.  I found that earlier and just figured out that it's not loaded.  So
the real newbie question is:  Is code like this enabled by proper
incantations from .ini?  Or have I just stepped over the line between what
can be done via configuration (.ini) to something that needs coding?

Thanks,
Mark

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365

[Mark E. Perkins-2]

On 2007/08/31 18:51, Neil Cherry wrote:

> Mark E. Perkins wrote:
>>
>> In the mean time, I added my W800RF32A to the mix; mh.private.ini like so:
>>
>>     cm11_port   = /dev/tty.USA28Xb2P2.2
>>     serial_port = cm11
>
> I have 2.103 and I have:
>
> cm11_port = /dev/ttyM0
>
> but I have no serial_port. While the CM11A might be a little
> flaky it does work as it's my primary X10 interface (at this
> time).
>

I'm not quite following you.  By "no serial port" do you mean only USB (so
the CM11 is attached via USB/Serial adapter)?  And for that reason you
don't need the 'serial_port' line?

Thanks,
Mark

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365

[Neil Cherry-3]

Mark E. Perkins wrote:

> On 2007/08/31 18:51, Neil Cherry wrote:
>> Mark E. Perkins wrote:
>>> In the mean time, I added my W800RF32A to the mix; mh.private.ini like so:
>>>
>>>     cm11_port   = /dev/tty.USA28Xb2P2.2
>>>     serial_port = cm11
>> I have 2.103 and I have:
>>
>> cm11_port = /dev/ttyM0
>>
>> but I have no serial_port. While the CM11A might be a little
>> flaky it does work as it's my primary X10 interface (at this
>> time).
>>
> I'm not quite following you.  By "no serial port" do you mean only USB (so
> the CM11 is attached via USB/Serial adapter)?  And for that reason you
> don't need the 'serial_port' line?

Sorry I meant no serial_port in my *.ini file. I'm using a Moxa
card for the CM11A (it's a multi-port serial car not a USB
dongle).

--
Linux Home Automation         Neil Cherry       ncherry@...
http://www.linuxha.com/                         Main site
http://linuxha.blogspot.com/                    My HA Blog
Author of:     Linux Smart Homes For Dummies

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365

[Mark E. Perkins-2]

On 2007/08/31 18:58, Mark E. Perkins wrote:

> On 2007/08/31 18:25, Gregg Liming wrote:
>> Quoting Mark E. Perkins (8/31/07 6:11 PM):
>>
>>> Am I correct to assume that the above .ini should arrange forwarding of X10
>>> Pn commands to the power line?  Or is that too simple minded?
>> also need to enable code/common/x10_rf_relay.pl
>
> Right.  I found that earlier and just figured out that it's not loaded.  So
> the real newbie question is:  Is code like this enabled by proper
> incantations from .ini?  Or have I just stepped over the line between what
> can be done via configuration (.ini) to something that needs coding?

Replying to myself.... add to data/code_select.txt

Now I'm getting things like

    2007-08-31 19:47:26 X10: Unmatched incoming data_chunk=XP3PJ (P 3)
    2007-08-31 19:47:26 XPJ: motion on
    X10_Interface error, X10 string not parsed: xp3pj.

P3 isn't a motion detector (it's not anything), so I guess I need to figger
out why mh wants it to be a motion detector, and why the string is not
parsed. I'll keep digging.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365

[Gregg Liming]

Quoting Mark E. Perkins (8/31/07 6:58 PM):

> On 2007/08/31 18:25, Gregg Liming wrote:
>> Quoting Mark E. Perkins (8/31/07 6:11 PM):
>>
>>> Am I correct to assume that the above .ini should arrange forwarding of X10
>>> Pn commands to the power line?  Or is that too simple minded?
>> also need to enable code/common/x10_rf_relay.pl
>
> Right.  I found that earlier and just figured out that it's not loaded.  So
> the real newbie question is:  Is code like this enabled by proper
> incantations from .ini?  Or have I just stepped over the line between what
> can be done via configuration (.ini) to something that needs coding?

no line exists...

In general, one normally needs to enable modules or create user code.
ini "parms" are used to instantiate what is hoped to be generalized
code.  Sometimes, ini parms will/can instantiate code "automagically".
Don't count on it though.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365