RE: [misterhouse-users] Bad MR26 Framing?

[Bruce W. <br...@mi...>]

> I tried to reply to this last night, but it didn't seem to go. I
> think this is a bug in X10_MR26.pm. It reads the serial port too
> fast, and then complains about the partial MR26 packet ( the MR26
> is in raw mode). The BX24 module is also set up for raw mode, but
> has code to save a partial string and cat it to the current
> string, thus handling the serial port getting read too fast.
> Since I am a mh newbie, It would be nice if someone could confirm
> my hypothesis that this is indeed a bug in X10_MR26.pm. See
> lib/X10_BX24.pm for details on how this module handles reading
> the serial port too fast. I think similar code needs to be added
> to X10_MR26.pm. Does this make sense?

I think maybe the BX24 processes data differently.   I just looked at the
MR26 code and I don't see anything that looks for or drops \n and \r like
the BX24 does.  I also set -debug MR26 and looked at the raw data and didn't
see any \r or \n reflected in the console.

If the data did come in 'records', we could have the main mh code cache it
up, sending data only after it found a break character, like \n.

Bruce