Got an inquiry from someone hoping to rent a commercial space to me who seems to not really get what my business is and is apparently unaware of established businesses already serving the need within the same block. I'm not in any kind of hurry to have a landlord again and even if I was, I think I'd pass on this particular opportunity as their idea of what they want in the space would likely be a deeply unprofitable money pit.
Shop has been closed today and yesterday, but that doesn't mean I'm not there. I'm between lots on some coffees so I'm doing the roast plan design and verification work that needs to happen to get the new lots out on the shelf. Currently drinking a nice coffee from Costa Rica. I've been buying from this farm for over 20 years and while their farm management practices are geared toward delivering a product that's very consistent year to year, I usually need to tweak the roast just a little.
Found the source of the bug obnoxiously far away from the behavior that triggers it. I'll need to dig into that a little more later as there's really no excuse for the segfault to have happened where it did. Also because not my code changed a related thing to something visually much worse because of course when you add functionality it's only natural to take away any UI hint that the new feature might exist. *facepalm*
Finally got some code I've been working on far enough along that I could put some debug text in and see if it's doing what I expected and get some timing data out. I started with the slower approach that doesn't involve a bunch of bit level operations to see if that's fast enough and it looks like it should be. There's more to do to properly finish the feature, but that what's already written is working correctly is a good sign.
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.
Author of Typica software for coffee roasters.