From: David N. <dno...@ya...> - 2007-03-25 04:00:17
|
Try setting this ini parameter: x10_interface=cm11 It shouldn't be required. But looking at the code, I think it might help. David ----- Original Message ----- From: "James Armstrong" <ja...@ar...> To: <mis...@li...> Sent: Saturday, March 24, 2007 7:14 PM Subject: Re: [mh] CM11 not working after upgrade to 2.103 from 2.102 > Setting debug=serial;cm11 does not show much in the way of the cm11. > Shows > w800 module info. This is all it shows: > > Debugging for serial turned on > Debugging for cm11 turned on > > - creating W800 port on /dev/ttyUSB1 > - creating cm11 port on /dev/ttyUSB2 > > (These look like they are X10MS (wireless motion) and is a warning): > 03/24/07 10:02:14 PM Evaluating user code > for id N4, x10 interface not supplied, supported by Serial_Item cm11 > 03/24/07 10:02:14 PM Calling Serial_match_add_hook > for id N2, x10 interface not supplied, supported by Serial_Item cm11 > for id N1, x10 interface not supplied, supported by Serial_Item cm11 > for id N6, x10 interface not supplied, supported by Serial_Item cm11 > for id N8, x10 interface not supplied, supported by Serial_Item cm11 > for id N9, x10 interface not supplied, supported by Serial_Item cm11 > for id NA, x10 interface not supplied, supported by Serial_Item cm11 > for id NB, x10 interface not supplied, supported by Serial_Item cm11 > ... > > db1 CM11: Sending x10 data: XB2 > cm11 send failed > db1 CM11: Sending x10 data: XBK > > Mh.private.ini: > cm11_port=/dev/ttyUSB2 > > I don't see any debug when it tries to send out X10 except for the lines > above about db1 CM11: Sending... > The CM11 is on a USB serial port if that matters. I am using the same > mh.private.ini and user code / items.mht between 2.102 and 2.103. I can > switch back and forth between them 2.102 works with X10, 2.103 does not. > > - James > > On 3/24/07 2:15 PM, "Matthew Williams" > <mat...@us...> > wrote: > >> James Armstrong wrote: >>> Does anyone use the CM11 on a mh linux machine and use v2.103? I have >>> been running fine since day one, but when I went from 2.102 to 2.103 the >>> CM11 stopped working. If I downgrade it starts working again. All I get >>> is a timeout while sending. I see some changes were made to the >>> Serial_Item file between 2.102 and 2.103. What can I turn on (debug >>> wise) and look at that would help? >> >> I've been running off subversion since we moved from CVS, including >> during >> the transition from 2.102 to 2.103 with no CM11 issues. However, the >> Serial_Item stuff was completely reworked in 2.103 so you may have found >> a >> new bug. Try setting debug=serial;cm11 to see if that gives you any >> clues. >> Post your debug logs and the relevant lines from your .ini files (cm11, >> x10_interface, any other interface declarations). >> >> Another place to increase debug info is by editing mh/lib/X10_Items.pm >> and >> changing $localDebug=1 in &set_interface. It is possible that mh is >> trying >> to use a different interface from your CM11. >> >> Matt >> >> ------------------------------------------------------------------------- >> Take Surveys. Earn Cash. Influence the Future of IT >> Join SourceForge.net's Techsay panel and you'll get the chance to share >> your >> opinions on IT & business topics through brief surveys-and earn cash >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >> ________________________________________________________ >> To unsubscribe from this list, go to: >> http://sourceforge.net/mail/?group_id=1365 >> > > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > ________________________________________________________ > To unsubscribe from this list, go to: > http://sourceforge.net/mail/?group_id=1365 > |