Arduino Unoの信頼性と耐久性に興味があります。
過度の使用のために誰かを「殺す」経験がありますか?
もしそうなら、ボードが故障するのにどれくらい時間がかかりましたか?
Arduino Unoの信頼性と耐久性に興味があります。
過度の使用のために誰かを「殺す」経験がありますか?
もしそうなら、ボードが故障するのにどれくらい時間がかかりましたか?
回答:
I have powered the board for days at a time. The code that was running was very simple, but there was absolutely no damage. It is worth it to note that it was being powered by a pre-regulated 5v source so the on-board regulators were not burning up.
9v未満ではハードウェアが損傷する可能性があるとは思いませんが、電圧が高いとオンボードレギュレータが非常に熱くなり始める可能性があります。
I've had one operating a simple weather station which sat online for a couple of months without any problems - I don't see anything that would cause it to break down beyond that time either.
The only real killer (aside from external factors) would be heat, so I'd advise trialling it for your usage application and seeing how it does. If you're worried it's getting too hot, then adding a heatsink shouldn't be too hard an addition to stop temps becoming a concern.
Keep in mind that the Arduino is meant to be used as a prototyping device. This means there has been very limited endurance testing of the board.
Once the board reaches a steady state temperature, there is nothing in the design that would cause it to go into thermal runaway on its own.
How you program it and what you hook it up to, however, may be a different story.
I've done it while playing around with one (I kept it on for two days, with a simple program). Nothing happens, though it gets warm.
I would suggest that you ensure that it stays cool, especially if your code is rather heavy on the processor. A heat sink ought to do the trick, or you can attach a small fan.
Aside from that, make sure that all input voltages (power, input pins) are not prone to fluctuations. While there are enough safety resistors in the Arduino to make it less affected by fluctuations than, say, the Raspberry Pi, you can still burn one up if the input voltage is too much.
Excessive heat would be the only long term threat. It works like this: through the power supply you continuously add energy, most of it in the form of heat. On the other hand the Arduino will also lose heat to the environment: the higher the temperature, the more it will give off.
When the Arduino has been running for half an hour or so equilibrium will have been reached: it has reached a temperature at which the released energy matches the absorbed energy. If the temperature is OK then (less than 85 degrees centigrade) it will be OK forever. So make sure it doesn't get hot quickly. An Arduino without enclosure will reach equilibrium within minutes and the temperature will be OK. In an enclosure you'll have to provide cooling vents, or for a metal case you can mount it on another metal structure which functions as a heatsink.
All in all, if your device doesn't get hot after an hour it's probably safe to operate it 24/7.
I run a fleet of what I call Piduinos - paired Rpi3 and Arduino Uno for data collection and remote control.
They run 24/7 in all kinds of environmental conditions.
You can see real-time data produced by a half-dozen of them at https://www.SDsolarBlog.com/montage
Never have had an Uno completely fail after the first few days (the old bathtub curve)
Mind you, this is at a desert southwest USA solar power plant, where the outside portion experiences wild daily temperature swings.
As for what makes them fail there is always one single thing: dust. It gets into the pin header sockets. For digital devices like DHT22 temperature sensors you know it has happened because the readings simply stop. For analog voltage inputs it is obvious it has happened because voltage divider readings either begin to get too high (meaning resistance in a ground lead) or too low (meaning resistance in the sensing lead).
If you go to the montage link above it is obvious that the outside battery voltage monitor ground lead is ailing. A new board has been constructed and will be installed soon. But for now, the normal settling voltage overnight is showing way above the 12.7 the voltmeter shows at the batteries.
Thus, the term "fail" is relative. Total failure has proven to be caused by the poor quality control of suppliers. But degradation happens much more frequently and is gradual.
Of course it will, I usually make my own boards, I leave them for months turned on without any problem. Sometimes, like 3 or 4 times, I had to turn it off then on so that it continue working.
The Arduino was designed for prototyping but gets regular use in art installations and other 24/7 applications. There really isn't anything to wear out under normal conditions even running for years.
Even if one's code was very heavy on the CPU, it would be the regulator that would get warm, not the MCU, and it would be just fine.
The only issue I can see is you attach several watts of load to it and overload the regulator to just below its automatic shutdown level. It would probably still be just fine.
If an Arduino is going to die, it's most likely going to be the flash wearing out, a short circuit/overvoltage, static electricity, or connector failure/other mechanical issues/sledgehammer attack
Mine has been running since May 2014. Since it's solar powered, it is always ON everyday and OFF automatically at nights (so not really 24/7).
http://epxhilon.blogspot.com.au/2015/04/cheapest-commuting-challenge.html
I've created an incubator for growing cells(LA-4, MCF-7, etc) in a laboratory, where I work. It is powering 2 relays, 1 bipolar transistor, reading 4 sensors and displaying values on LCD screen since May 2017. It was only shut down twice, when the inside of the incubator was cleaned, then turned back on. I'm powering it with 12VDC from a very steady power supply, which has low ripple output (<5mV).
Fun fact: The sensors are constantly on rh=95-100%.