Missing events
Posted: Tue Jun 26, 2007 1:00 am
It's well over a year since I installed my Xanura modules. It took me some time to gather the courage to actually start writing software for the system, due to initial disappointments in the quality of the Xanura products (http://www.domoticaforum.eu/topic.asp?TOPIC_ID=66).
But now I've got my low power solid state running I decided to give it a try. Existing Linux drivers for the CM11 are either broken or don't support extended X10 codes, so I had to write my own driver. I don't mind, because that way I'm sure I've got a good driver, but these things are very typical for Linux.
While I was testing my driver, I discovered a very nasty phenomenon. If I switch two dimmers (DAIX10) shortly after another, the switch event of the second dimmer doesn’t get noticed! And ‘shortly’ in this case is everything quicker than 3 seconds! This is totally unacceptable: There’s no way I’m going to adapt the way I operate my switch to the limit of the system, let alone explain this to my girl fiend: “No honey, don’t operate more that one switch every three seconds or the silly computer will get upset.” Due to my earlier disappointments I was about to blame it on Xanura, but fortunately I remembered some limitation in the CM11 which may be causing this problem:
<i>The CM11 interface has a 10 byte output buffer. An extended message is 4 bytes long, two per event are sent by Xanura modules, one byte holds the length of the buffer and another holds a bitmask marking function bytes. So pressing the button of one dimmer fills up the CM11 buffer completely untill it's read by the computer, making his interface unsuitable to use it with Xanura modules.</i>
Now I’m using a custom firmware in my CM11 (http://www.domoticaforum.eu/topic.asp?TOPIC_ID=294), which also may be the cause of this problem. Can any body with an original CM11 please try to reproduce this problem? And can anybody with a better interface, like the CTX35, please verify if this problem doesn’t occur with such an interface? I’ll probably buy a XTB-II (http://www.domoticaforum.eu/topic.asp?TOPIC_ID=69), but that one uses an even older protocol, that of the TW523 so I’ll probably have to write my own firmware for that one too.
But now I've got my low power solid state running I decided to give it a try. Existing Linux drivers for the CM11 are either broken or don't support extended X10 codes, so I had to write my own driver. I don't mind, because that way I'm sure I've got a good driver, but these things are very typical for Linux.
While I was testing my driver, I discovered a very nasty phenomenon. If I switch two dimmers (DAIX10) shortly after another, the switch event of the second dimmer doesn’t get noticed! And ‘shortly’ in this case is everything quicker than 3 seconds! This is totally unacceptable: There’s no way I’m going to adapt the way I operate my switch to the limit of the system, let alone explain this to my girl fiend: “No honey, don’t operate more that one switch every three seconds or the silly computer will get upset.” Due to my earlier disappointments I was about to blame it on Xanura, but fortunately I remembered some limitation in the CM11 which may be causing this problem:
<i>The CM11 interface has a 10 byte output buffer. An extended message is 4 bytes long, two per event are sent by Xanura modules, one byte holds the length of the buffer and another holds a bitmask marking function bytes. So pressing the button of one dimmer fills up the CM11 buffer completely untill it's read by the computer, making his interface unsuitable to use it with Xanura modules.</i>
Now I’m using a custom firmware in my CM11 (http://www.domoticaforum.eu/topic.asp?TOPIC_ID=294), which also may be the cause of this problem. Can any body with an original CM11 please try to reproduce this problem? And can anybody with a better interface, like the CTX35, please verify if this problem doesn’t occur with such an interface? I’ll probably buy a XTB-II (http://www.domoticaforum.eu/topic.asp?TOPIC_ID=69), but that one uses an even older protocol, that of the TW523 so I’ll probably have to write my own firmware for that one too.