Good afternood everyone, i planning to make a proyect that basically has a 9v motor, a 9v computer-like fan and a temperture sensor. It will have to set ups, with the motor and fan on at the same time or one on while the other one is off, in bith cases with the sensor measuring. So the question is very simple how long do you think the arduino will work, in both cases without breaking? Im looking for an estimate because i dont have money to use my arduino UNO til it burns and then buy anotherone. So please people how long do you think the arduino will work continously in a safe way and then te other day the same thing over and over...Thank you so much!!
3.4 Data RetentionReliability Qualification results show that the projected data retention failure rate is much less than 1 PPM over 20 years at 85°C or 100 years at 25°C.
there are two parts to thiselectro / mechanical , yep the thing should keep going for decades, BUT: its a small bit of silicon, with a few electrons per bit in the program. one strike via a stray neutron , esd spike or what ever, and the program will glitch. now that glitch might be to some where that the program can recover, or it might be to some where that causes the mirco to 'crash'.and over years, the code will glitch at some point,
Interesting...........not convinced............but interesting
Quote from: retrolefty on Dec 14, 2013, 02:47 pmInteresting...........not convinced............but interesting It definitely is an issue, ECC memory is not uncommon. I have no idea how much of an issue it is in the microcontroller world or how it might be mitigated in MCUs. For smaller processors, where there may not be as much incentive to miniaturize, just sticking to older lithography technology might go a long way, physically larger memory cells being less susceptible.
its a small bit of silicon, with a few electrons per bit in the program. one strike via a stray neutron , esd spike or what ever, and the program will glitch. now that glitch might be to some where that the program can recover, or it might be to some where that causes the mirco to 'crash'.and over years, the code will glitch at some point,
it does happen it is a problemhow oftern has one had to reset a computer, your tv gone 'silly' or the washing machine gone funny, I bet every one who has a few micros around the house has had a few funnies over the years.if it does not matter to your design, then your ok, but random none programmed behaviour can not be ignored,if you decide a random crash is not a problem, then thats a good solution, most arduinos I would suggest are like this. if it goes wrong the user cycles the power,ways to mitigate include, power reset the processor regularly, have an external watchdog timer that resets the processor if an error is detected, there are many other harder and simpler methods, which might suit your application , but these two are a good starting point.As an example, I for one would not have a processor controlling a large motor without their being a limit system in place that kicks in if the arduino system for what ever reason goes wrong.