4 ms·

I have probably 8-9 Zero W boards in projects at this point, running everything from cat cams, temperature sensors in various rooms, even my stereo amplifier is

I have probably 8-9 Zero W boards in projects at this point, running everything from cat cams, temperature sensors in various rooms, even my stereo amplifier is controlled by (but not passing audio through) a Pi Zero W. All of them now have a very specific model industrial MicroSD card in them, and none have lost or corrupted data, or refused to boot, since those cards were added. They had SanDisk ultra cards before that, and they had to be reinstalled all the time. I picked the card because it's an aMLC* model (cheap overall, $15 for 4GB, $25-28 for 8GB), which significantly improves write endurance even compared to MLC cards, and because the controller is designed to handle sudden power loss, which is where a lot of these Pi+SD problems come from; consumer MicroSD cards are generally designed for use in devices that have batteries and rarely if ever lose power suddenly, so the controller can take risks for optimization that it wouldn't otherwise want to take. They're also rated down to 0C, which I can say is definitely true as I have some operating close to that right now. This is the card: https://www.digikey.com/product-detail/en/atp-electronics-inc/AF4GUD3A-OEM/AF4GUD3A-OEM-ND/5361062 https://www.digikey.com/product-detail/en/atp-electronics-in... 4GB isn't huge in a world where 32/64GB cards are common for a similar price, but a full headless OS installation doesn't even take half of that, and there's no real use for more space most of the time. * with aMLC mode, it's still MLC flash (so cheaper than SLC), but each cell only stores a single bit rather than 2 (MLC) or 3 (TLC), so there are only 2 voltage states it needs to be able to measure, rather than 4 (MLC) or 8 (TLC). That means you lose some storage capacity (half vs MLC), but the tolerances for the voltage measured in each cell is significantly relaxed, so it remains usable long past the point where a plain MLC mode card would not be able to accurately program and measure the voltages that represent the 2-bit values of 00, 01, 10, or 11 anymore.

StavrosK 8y ago
You should use something else for most of these, as the Raspi is hugely overkill. Something like an ESP8266 is much better suited for sensors and things like that, and it comes with onboard storage that it uses to run its code from. Plus, it costs $3 each, is stamp-sized and has Wifi.
- andyidsinga 8y ago
  I use the ESP8266 and ESP32 for projects too - but the PI is sooo much easier to work with with a full linux distro and programming languages and libs to go with. the ESPs are most definitely better for higher volume solutions
  - StavrosK 8y ago
    Hmm, you think so? I hate having to always keep Linux up to date. I prefer to just load micropython onto an ESP and be done. I use the Pi for heavier workloads, but that does mean it very rarely gets used.
    - andyidsinga 8y ago
      well trade offs ¯\_(ツ)_/¯ EDIT : now that you mention it - micropython is pretty cool -- and I haven't used it - need to try that on the ESP :)
- mrsteveman1 8y ago
  The Pi boards actually replaced ESP32 boards running ESP-IDF firmware I wrote, I probably have 15+ of them at this point and still plan to use them for other things. The ESP32s were routinely dropping from WiFi (some being crashes, some just disassociating and never connecting again). ESP-IDF has had quite a few WiFi fixes, but it's difficult to guarantee that your own code isn't directly causing the problem (which you get for free running in userland on Linux), and dealing with it was becoming a huge time sink. Most of the Pi Zero W boards I have were $5 at Microcenter, the MicroSD adds to the cost a little but they're extremely reliable as a result, and my own code is no longer running in the same address space with the scheduler and WiFi driver under extremely tight memory constraints :)

StavrosK 8y ago

You should use something else for most of these, as the Raspi is hugely overkill. Something like an ESP8266 is much better suited for sensors and things like that, and it comes with onboard storage that it uses to run its code from. Plus, it costs $3 each, is stamp-sized and has Wifi.

andyidsinga 8y ago
I use the ESP8266 and ESP32 for projects too - but the PI is sooo much easier to work with with a full linux distro and programming languages and libs to go with. the ESPs are most definitely better for higher volume solutions
- StavrosK 8y ago
  Hmm, you think so? I hate having to always keep Linux up to date. I prefer to just load micropython onto an ESP and be done. I use the Pi for heavier workloads, but that does mean it very rarely gets used.
  - andyidsinga 8y ago
    well trade offs ¯\_(ツ)_/¯ EDIT : now that you mention it - micropython is pretty cool -- and I haven't used it - need to try that on the ESP :)
mrsteveman1 8y ago
The Pi boards actually replaced ESP32 boards running ESP-IDF firmware I wrote, I probably have 15+ of them at this point and still plan to use them for other things. The ESP32s were routinely dropping from WiFi (some being crashes, some just disassociating and never connecting again). ESP-IDF has had quite a few WiFi fixes, but it's difficult to guarantee that your own code isn't directly causing the problem (which you get for free running in userland on Linux), and dealing with it was becoming a huge time sink. Most of the Pi Zero W boards I have were $5 at Microcenter, the MicroSD adds to the cost a little but they're extremely reliable as a result, and my own code is no longer running in the same address space with the scheduler and WiFi driver under extremely tight memory constraints :)