Sort out serComm about mrfreeze HOT 4 OPEN

Controller comm parameters are 4800 baud, 8 data bits, 1 stop bit, no parity and no flow (so 9 bits total per word - I'm assuming it's a 16 bit word size but I have no good idea). No other comm options.

TimePerBit (in sec) is 1 / baud rate, so that's ~208 microseconds per bit right there. With 9 bits per word, and 265 bytes total, that's 0.497 sec right there without any overhead or anything else. So 0.5 seconds is definitely too short. Le sigh.

from mrfreeze.

The way to fix this is to change serComm to read until the buffer is empty, not read for however long the timeout happens to be. I should just do that.

from mrfreeze.

Since I'm using pyserial, if I open the socket with timeout=0 it implies that it'll read up to the specified number of bytes and return immediately. But I'm pretty sure I enabled the timeout because I was getting network hiccups/hangups, so idk what (if anything) to really do here. Maybe call 0.75 sec better than 1 second and call it an evening with the other speedups.

See https://pyserial.readthedocs.io/en/latest/pyserial_api.html#serial.Serial.__init__

from mrfreeze.

Had to fall back to 1.0 seconds because the LS325 and the Sunpower controllers were dropping/mangling responses! Annoying.

from mrfreeze.