Menu
▾
▴
Re: [misterhouse-users] CM11 "power failure"?
|
From: Bruno P. <br...@rp...> - 2002-12-16 05:54:18
|
Thanks for the advice. I tried a combo of all the bits of advice - unplugged the CM11, removed the batteries, then plugged it back into an extension lead so I could remove the serial extension lead. Heyu now works fine (can get info with "heyu info" and can turn devices on and off). But I still get a load of "Bad CM11 data send transmition" errors from Misterhouse. Any ideas why Heyu might be able to talk to the CM11 OK and Misterhouse not? Cheers, Bruno Prior Tail end of output from ./mhl -debug X10 -Tk 0: 12/16/02 04:34:16 AM Caller ID Interface has been Initialized... 12/16/02 04:34:16 AM Read 0 trigger entries File watch set for ./../data/web/weather_forecast.txt, flag=. time=992786286 X10: interface=cm11 isfunc=0 save_unit=XA1 data=XA1 CM11 send data=A1 CM11 dim=0 header=00000100 hb=0110 cb=0110 bd=0x04,0x66 checksum=0x6a CM11 send: 0466 ..............................No data received from cm11 Bad checksum in cm11 send: cs1=106 cs2=. Will retry CM11 send: 0466 .. CM11 data=106 hex=6a CM11 ack ..............................No data received from cm11 X10: interface=cm11 isfunc=1 save_unit=XA1 data=XAK CM11 send data=AK CM11 dim=0 header=00000110 hb=0110 cb=0011 bd=0x06,0x63 checksum=0x69 CM11 send: 0663 .. CM11 data=105 hex=69 CM11 ack ..............................No data received from cm11 12/16/02 04:34:30 AM Light set to off running: play ./../sounds/sound_nature/bird1.wav 12/16/02 04:34:30 AM mh paused for 4 seconds (v=13) 12/16/02 04:35:00 AM: Saving object states ... done 12/16/02 04:35:00 AM It is 4:35 AM on Monday, December 16th. normal: It is 4:35 AM on Mon, Dec 16. testing port ... 12/16/02 04:35:00 AM Oops2: can't open device: at ../lib/Serial_Item.pm line 74 not available normal: A miser is hard to live with, but makes a fine ancestor. X10: interface=cm11 isfunc=0 save_unit=XA1 data=XA1 CM11 send data=A1 CM11 dim=0 header=00000100 hb=0110 cb=0110 bd=0x04,0x66 checksum=0x6a CM11 send: 0466 Bad cm11 data send transmition ..............................No data received from cm11 Bad checksum in cm11 send: cs1=106 cs2=. Will retry CM11 send: 0466 Bad cm11 data send transmition ..............................No data received from cm11 Bad checksum in cm11 send: cs1=106 cs2=. Will retry CM11 send: 0466 Bad cm11 data send transmition ..............................No data received from cm11 Bad checksum in cm11 send: cs1=106 cs2=. Will retry CM11 send: 0466 Bad cm11 data send transmition ....................Exit flag set in sig_handler .........No data received from cm11 Bad checksum in cm11 send: cs1=106 cs2=. Will retry CM11 ack Bad cm11 acknowledge send transmition ..............................No data received from cm11 X10: interface=cm11 isfunc=1 save_unit=XA1 data=XAJ CM11 send data=AJ CM11 dim=0 header=00000110 hb=0110 cb=0010 bd=0x06,0x62 checksum=0x68 CM11 send: 0662 Bad cm11 data send transmition ..............................No data received from cm11 Bad checksum in cm11 send: cs1=104 cs2=. Will retry CM11 send: 0662 Bad cm11 data send transmition ............Exit flag set in sig_handler .........Exit flag set in sig_handler ........No data received from cm11 Bad checksum in cm11 send: cs1=104 cs2=. Will retry CM11 send: 0662 Bad cm11 data send transmition .....Exit flag set in sig_handler ................Exit flag set in sig_handler .........No data received from cm11 Bad checksum in cm11 send: cs1=104 cs2=. Will retry CM11 send: 0662 Bad cm11 data send transmition ..............................No data received from cm11 Bad checksum in cm11 send: cs1=104 cs2=. Will retry CM11 ack Bad cm11 acknowledge send transmition ........................ ......No data received from cm11 12/16/02 04:35:00 AM Light set to on Charles Sullivan wrote: > On Sat, 14 Dec 2002 04:19:02 -0800 > mis...@li... wrote: > > >>Message: 11 >>Date: Sat, 14 Dec 2002 12:18:39 +0000 >>From: Bruno Prior <br...@rp...> >>To: mis...@li... >>Subject: [misterhouse-users] CM11 "power failure"? >>Reply-To: mis...@li... >> >>I'm trying to take my first steps with computer control of X10. The CM11 >>is connected to the serial port via a serial extension lead, because of >>a shortage of power sockets near the computer. When I try to communicate >>with the CM11, using either Misterhouse or Heyu, I am getting similar >>messages that the CM11 has experienced a power failure and requested a >>time update. It also claims that the battery has been used for 42,405 >>minutes and needed replacing. I have replaced the batteries with new >>ones and still get this message. >> >>I can't find anything about this sort of error on the web. I am >>wondering whether it could be due to: >> >>(a) me not realising I have to do something basic to initialise the CM11 >>or get it talking to the computer, >> >>(b) the communication getting scrambled by the serial extension cable, or >> >>(c) a broken CM11? >> >>Has anyone seen this sort of error message before, or got a clue what >>might cause it? >> >>Cheers, >> >>Bruno >> >> >>-------------- >> >>Output of "heyu info": >> >>Module experienced a power failure. It requested a time update. >>Battery has been used 42405 minutes. It should be replaced soon. >>Firmware revision Level = 5 >>Interface clock: Error, 332:45:165, Julian 421 >>Housecode = d >>0 = off, 1 = on, unit 16.......8...4..1 >>Last addressed device = 0xa5a5 (0011001111001100) >>Status of monitored devices = 0xa5a5 (0011001111001100) >>Status of dimmed devices = 0xa5a5 (0011001111001100) >> > > > The data being returned to Heyu is all wrong - I've seen a CM11a > do this on occasion when it is misprogrammed and it goes into a > wild loop, and a CM11a can get misprogrammed by stray pickup from > a serial cable connected to the CM11a but open at the other > end. I don't know about an extra long serial cable like you > are using. > > Try unplugging from the wall and serial cable, removing > the batteries, and let sit for about 5-10 minutes. Then replace > batteries, plug into the wall, and reconnect the serial line, > _making the final connection at the CM11a end_. > > If that doesn't solve the problem, repeat the shutdown/restart as > above but use a long 3-wire extension cord and the short serial > cable supplied with the CM11a to see if that makes a difference. > > The current release of Heyu doesn't have a feature to reset > the battery timer, so it may report battery usage of 65535 > minutes (= 0xFFFF). Ignore this for now. > > > ------------------------------------------------------- > This sf.net email is sponsored by: > With Great Power, Comes Great Responsibility > Learn to use your power at OSDN's High Performance Computing Channel > http://hpc.devchannel.org/ > ________________________________________________________ > To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365 > |