From: Scott R. <sc...@th...> - 2005-11-30 14:45:52
|
David Mark wrote: > Scott Reston <scott <at> therestons.com> writes: > >> i was working with my dad today on some updates to his MH install and >> noticed what i beleive to be a bug in the way multireceive delay is >> working with x10. he's running 2.10 >> >> he has a transceiver on housecode E and an MR26. he needs to keep the >> transceiver b/c of some reception issues. both the cm11 and mr26 pass > > Phase coupler needed? no - it's just a crappy stick-a-switch that he's using. they're weak and the mr26 can't hear it, so he put in a transceiver near it. >> anyone else experiencing this? i'm transceiver-less at my place, so i >> haven't had this issue... > > I don't think it has anything to do with the transceiver. The logic in the > main mh module that handles dupes has a flaw. In short, it checks a list of > previously executed X10 commands, but does not include RF commands in that > list. So if an A1 comes in from the RF receiver, followed by the slower > serial A1 from the cm11, the dupe check would fail as the first wasn't pushed > to the list. This should probably be addressed in the next version. yes - i think this is the issue. the commenting around the multireceive dupe-checking suggests that it was meant to make sure that a transmission wasn't duplicated when received by a cm11 and an mr26 which is what appears to be happening. multiple mr26 transmissions are dupe-cleaned and multiple cm11s seem to be as well. >>> 11/29/05 11:37:06 AM X10: Unmatched incoming data=XE5EJ >>> 11/29/05 11:37:06 AM X10: Unmatched incoming data_chunk=XEJ (E ON) >>> 11/29/05 11:37:06 AM X10: Unmatched incoming data_chunk=XE5EJ (E 5) >>> 11/29/05 11:37:03 AM X10: Unmatched incoming data=XE5EJ >>> 11/29/05 11:37:03 AM X10: Unmatched incoming data_chunk=XEJ (E ON) >>> 11/29/05 11:37:03 AM X10: Unmatched incoming data_chunk=XE5EJ (E 5) >>> > > This is just a device that is not defined. It can't match E5 ON, so it tries > to match E ON and fails again. Then the repeater sends the same thing three > seconds later. You just can't get rid of those in the log. If you turn > multireceive up to three seconds, you will effectively disable double and > triple-clicks. > right - i just wanted to show that the code was hitting the logs twice without generating a debug that also sent info back out... i have the same problem of duplicate codes (rf and powerline) if i set the multireceive really high (like 10sec). > BTW, you guys are using the cm11 controller? I seem to remember you were > having problems with it. I have found that mine is faster since discarding > the serial to USB adapter. I thought I might have tuned the cm11 code for the > adapter due to several issues reported from people with serial connections, > but apparently not. i've switched to a lynx10, but my dad's using a cm11. s:r |