![]() And picked up 3 of the newer raspberry pi 3 B+ models when they came out.ġ runs Pihole, a DNS server adblocker: I got 1 older Raspberry Pi 1B+ I'm not using at moment. It's a LOT more than just the Pi though, which is lost on you. I'm not some closet hack, this is a properly engineered and supported industrial platform. So, before you spout off paranoia and technical ineptitude, do your research. We also work VERY closely with the USDA and have achieved some of the highest certifications for food safety possible - being the first in this state for several types of certification at ALL. I can tell you the (calibrated and redundant) temperature for every minute it was in the tank, and send you alerts the moment anything goes out of spec. they couldn't tell you what's happened to their beer whatsoever over the 2-3 weeks it ferments, other than maybe what a little red LED said the temp was once or twice a day when they happened to look, if you're lucky. I'd be more worried drinking beer at any brewery that DOESN'T have our system. Of course I've built in redundancy, fail-safes, watchdogs (hardware and software), etc., to ensure things are exceedingly safe and reliable. ![]() so it's rare, but significant when it happens.įor an AC that clearly knows NOTHING about our particular system (nor the Raspberry Pi in general, it seems), you're making some pretty ludicrous accusations. On 400+ systems in the field, it may happen once every three months or so. We tend to avoid using USB devices due to this, and I've implemented a hardware-based watchdog into our board to reset the pi if this ever happens. It's worst when I'm bit-banging the GPIO's to do serial on pins other than the built-in UARTS. There's an extreme edge case where if I'm using a GPIO pin at the exact same time as certain things happen on the USB bus, the system will freeze. My biggest issue is actually with the USB bus on the Pi. Most of the times we've had that as a problem it was due to simple human carelessness when installing, or when attaching sensors/etc. ![]() The GPIO shorting issue is a real hardware issue - they should be opto-isolated on the Pi board itself, however we take care of most of that in our board where the Pi plugs into it (the Pi is almost a "hat" for our system, in the end). I get latency under 0.02 seconds worst case (from analysis) which is orders of magnitude more than required for these applications. The systems we run don't need real-time timing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |