Agreed on all of this. Even eMMC is susceptible to FS corruption due to no protection of the write cycle at unexpected power down. It is an issue that needs to be addressed. Meanwhile, my micros just don’t ever die. Even if they do, i can preconfigure one, throw it in the mail, and it’s a five minute swap out.
My rationale for a standalone Linux box was manifold, but the crux was that not all devices live on the internet constantly, and being able to pull databases periodically and/or view it without WAN access seemed like a pretty reasonable endeavor. I’m pretty over that. It’s a minuscule fraction of application cases I can live without (or use GSM). C > On Feb 21, 2019, at 14:54, Stefano Miccoli via Owfs-developers > <owfs-developers@lists.sourceforge.net> wrote: > > Quite an interesting discussion, please forgive me if I throw in my 1cent. > > We should not forget that normal RPis are educational boards, not meant for > professional use. OS on a SD is a terrible idea, with regard to card > corruption, but at least it is *impossible* to brick your board. Something > wrong? just swap SDs and start over… I think that this is a key point for > educational/hobby use. > > For industrial application there is the compute module > <https://www.raspberrypi.org/products/compute-module-3/>, with up to 32GB > eMMC, and, as already mentioned, newer RPis can boot from USB but also from > network. If you are familiar with setting up a DHCP, TFTP, NFS server, you > can also try a fully storage less network client setup. (Of course this makes > sense if you are going to deploy a cluster of at least five RPis. But with a > reasonable server and network this easily scales up to tens of nodes.) > > However the main point, in my opinion, is that for most application you do > not need the power of a full fledged linux system-on-chip (with 8GB+ storage, > 1GB ram, 4 cores, GPU, hdmi port, ethernet, etc.) Moreover linux systems need > administration and security updates, etc. so for a great number of > applications it is just over kill. > > So if you are not going to use the distributed “intelligence” and compute > power sleeping in your SOC nodes, the µcontroller is for sure the way to go. > > Stefano > >> On 21 Feb 2019, at 06:29, Colin Reese <colin.re...@gmail.com> wrote: >> >> Joe, >> >> I transitioned from Pis to ESP32. I was all-in on Pis, trust me. I love >> linux. The issues: >> >> It's not just the power supply. SDCards in this environment will corrupt >> eventually, absolutely. There is nothing that can protect the operating >> system from eventual corruption. Yes, I too, have been lucky and had them >> run for years. You simply cannot count on this with consumer-grade sd cards. >> You can buy industrial quality flash or eMMC, but at this point you are >> spending more for your memory than you are on the board, and often much, >> much more. If you do enough research, you will find that this is simply >> something you cannot practically avoid, unless you go to these expensive >> cards, or do work to make a frozen, read-only operating system image that >> offloads all data that need to be permanently stored onto something like a >> flash drive, where you do not care if it becomes partially corrupted. It's >> sad, but true. I have talked to dozens of people who use these. Every single >> one has had these issues, regardless of how good their power supply is. If >> your application cannot tolerate a reformat periodically (remote devices >> come to mind), this situation is simply a non-option. >> >> The operating system is constantly being updated, and if you want things >> like, I dunno, support for Python 3.5+, you have to deal with the fact that >> it is often times a bleeding edge operating system, and things simply break. >> LSB was non-functional for a period ... it has at many times simply been a >> mess. >> >> For me, I do not need a local database. I push it to a cloud service (my own >> servers, in this case), and handle it there, and serve it to anywhere on the >> net. For this reason, the complexity of a Pi solution simply does not >> outweigh the above issues. >> >> Now, you can get an ESP32, which has WiFi, 4MB flash, bluetooth, in a tiny >> package, for $10. You can get one with a nice little oled display for $19. >> You can get one with an sdcard and wired ethernet for $30. You can get >> another version with 4MB more of program space via PSRAM for a little more. >> You can get em with relays, IR transceivers, CAN, RS485 .. lots of things. >> It's not quite as diverse as the arduino ecosystem, but it is getting there >> for sure. Best, you can run micropython on it and avoid having to write any >> C whatsoever. I ported a ton of code over from my Pi projects. Best of all, >> it is rock solid. Mine reboots once an hour, stores data in a little json >> file to pick up after it reboots, and loads config from a set of json files. >> It posts to a web API, hosts its own web page for web-based config ... it's >> just ... wonderful. >> >> Should probably contact me off-list if you want, as this is not germane to >> OWFS, but happy to give you any info you like. >> >> Cheers, >> C >> >>> On 2/20/2019 7:38 PM, joep wrote: >>> Hi All, >>> To some extent this follows from thread: *Reliability and Robustness of >>> the DS2482-100 or DS2482-800* >>> I've been using a couple of Raspberry Pi's (RPi 1 Model A+) to manage >>> the temperature, humidity and lighting in a terrarium since 2014/2015. One >>> Pi is in active use while the other is used as a development platform to >>> try things out on. Overall I'm impressed by how much one can do without >>> spending a fortune and I'm quite keen to explore further. >>> One thing which always bothered me with the Pi's is the SD card. I've >>> had a few corruptions (all power supply related). Even with a clean and >>> stable supply I am still doubtful if one can achieve "industrial grade" >>> reliability if using SD cards. So I'm now looking for other microcontroller >>> options to control my 1-wire based system as I'm intending to extend >>> management to my greenhouses where reliability is more important. >>> Options I have looked at so far include the Arduino (Uno, Zero or DUE) >>> and the ESP32. Haven't fully explored the latter but it seems to have an >>> incredible number of interfaces. I'm quite impressed by the Arduino - it's >>> simple, there's a big choice of units and it's easily extensible (with a >>> lot of pre-built modules available). My design will involve power switching >>> and (ideally) more than one 1-wire bus (so a DS2482-100 is likely to be >>> involved). The system will also interface to my network for monitoring and >>> management. >>> What are your opinions re. suitable microcontrollers where reliability >>> and ease of extensibility are requirements. >>> -- >>> Regards >>> Joe P. >>> _______________________________________________ >>> Owfs-developers mailing list >>> Owfs-developers@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/owfs-developers >> >> >> _______________________________________________ >> Owfs-developers mailing list >> Owfs-developers@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/owfs-developers > > _______________________________________________ > Owfs-developers mailing list > Owfs-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/owfs-developers
_______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
