@cwebber If I have to be a furry, lashes are a pain, but liner is a must.
@mike Follow up: do we really believe that Geordi isn't cheating with his VISOR (even if the cards aren't transparent to infrared, he'd still see physiological tells)?
Hardware documentation says a space is used as a delimiter between fields and fails to mention that if you put it into a mode where not all fields are output, you still get the spaces delimiting the suppressed output. Also indicates \r\n as a line terminator and apparently that really means usually just \r but sometimes just \n and never actually \r\n. This is why I have trust issues.
Pushed a new version of the software to the computer at the coffee roaster. It's working. Also investigated why one of my sensors wasn't reading on the little roaster. One of the channels on the data logger isn't working right so I've just moved the wires over to a different channel and will need to adjust the software configuration to match later. Oddly, the diagnostic tool that I used to sort this out was screen and issuing commands to the logger manually.
Finally unboxed my case of SCAA cupping bowls. Yes, that's right, SCAA, not SCA. Got them a while back after helping out with a class at a lab that had a whole bunch of extra cases. Plus side: none of them were broken. Minus side: no lids. There's enough new coffees that I need to sort out that I figured it was time to pull these out of storage.
@yomimono Hopefully there aren't any.
Previously I just used a library on Windows which was also kind of nasty to work with (it exposed some truly strange implementation choices), but if I just implement the communications protocol myself it should just work everywhere including on platforms that were never officially supported by the hardware.
Author of Typica software for coffee roasters.