Timeline for Does an Arduino get worn out by too much command execution?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 22, 2017 at 12:40 | comment | added | Luaan | @Mast It only makes a difference when parts of the system are actually powered-off when not in use - that's actually quite a complex thing to do, especially while taking latency into account (it takes a while to power things on - e.g. Intel Skylake takes about 70 clock cycles to enable the whole AVX). Checking what helps is easy enough - just measure how much power is being consumed; that's pretty much how much heat is being generated. Also, consider total energy use, not just power - e.g. slower code taking more time while saving power might be less efficient that faster code for a task. | |
| May 22, 2017 at 9:27 | comment | added | VisualMelon |
You can very quickly ruin your EEPROM if you write to it aggressively. To make life a little easier, AVRC provides dedicated update commands which only perform the write if the value has changed, which has many use-cases (e.g. a regularly written but rarely changed status code), but is no silver bullet. I believe EEPROM fails on a byte or word level, so you can work around this to some extent if you must.
|
|
| May 22, 2017 at 8:10 | comment | added | ahmadx87 | Thank you for your reply. Now I can lean back and write codes as complex as I want and do not worry about life span of my Arduino! But is it also the case for constantly interacting with external components? Reading sensors, SPI communication and so on? | |
| May 22, 2017 at 8:05 | vote | accept | ahmadx87 | ||
| May 21, 2017 at 15:04 | comment | added | Majenko | Only a very tiny tiny amount. Even when doing 'nothing' it is working hard and processing. | |
| May 21, 2017 at 15:03 | comment | added | Mast | Won't code indirectly influence generated heat? Hot components could wear down faster. | |
| May 20, 2017 at 22:48 | comment | added | Majenko | @MV. Yes, but what you run on the microcontroller doesn't really affect it. Whatever you are doing you are running the CPU at (roughly) the same level. You're using all of it (pretty much) all of the time. | |
| May 20, 2017 at 18:50 | comment | added | MV. | But all semiconductos age, don't they? hot carrier injection and bias temperature instability are the mechanisms I remember. Of course it would take many many years. | |
| May 20, 2017 at 13:16 | history | answered | Majenko | CC BY-SA 3.0 |