wat is Mean time between failures (MTBF)

hi guys I'm using the Arduino Micro Board in a commercial USB-product and after long hours of work it finally came out to life. Off course I had to modify some of the original code but it is looking great !!!

However I have a question, Does anyone knows what is the MTBF (Mean Time between failures ) for the Arduino Micro board. I looked in the data sheet but nothing there ?

Thanks

PS: Mean time between failures (MTBF)

bemin:
hi guys I'm using the Arduino Micro Board in a commercial USB-product and after long hours of work it finally came out to life. Off course I had to modify some of the original code but it is looking great !!!

However I have a question, Does anyone knows what is the MTBF (Mean Time between failures ) for the Arduino Micro board. I looked in the data sheet but nothing there ?

Thanks

PS: Mean time between failures (MTBF)

You'll want to read the licensing agreement as well for a commercial product.
Make sure your management is aware.

.

ieee488:
You'll want to read the licensing agreement as well for a commercial product.
Make sure your management is aware.
https://www.postscapes.com/forum/arduino/47-if-arduino-is-for-prototyping-how/when-do-you-make-the-actual-product/

.

Thanks I really appreciate the link!!

Also, MTBF if you don't abuse the board, and MTBF if you treat it like the people on these forums usually do are very different numbers :wink:

DrAzzy:
Also, MTBF if you don't abuse the board, and MTBF if you treat it like the people on these forums usually do are very different numbers :wink:

LOL I need the number that was done at the original testing in the Manufacture LOL
I don't need a random number

no one knows or what ?

bemin:
no one knows or what ?

It didn't start out as a commercial product.
You'll have to contact them directly for that information I would guess.

What makes you think that the MTBF of the arduino board has been characterized? MTBF is typically characterized (at considerable testing expense) for industrial products, but the arduino is a development and prototyping platform targeted at hobbyists and educational market.

The MTBF of the arduino board itself is also not very useful, since the MTBF will be impacted by what it's connected to - and maybe even what code it's running. An arduino micro board just sitting not connected to anything should have an essentially indefinite lifespan (the full sized boards use electrolytic caps, which do have a limited lifetime, but the micro doesnt), barring abuse; it's not like a mechanical device that experiences wear and tear and is expected to fail after some length of time.

Each component has a different lifespan depending on quite a lot of variables.

Voltage, Current, Operating Temperature range, Memory writes (both V and Non V and EEPROM vs EPROM), Humidity, and a few more besides.

The only way to know is for YOU to work out what that is as you have given zero detail in any of that regards and it is simply beyond the scope of the forum to do that work for you.
Then use your application of those figures as a measure of how far you will be pushing each of those items and use the shortest lifespan as a very basic MTBF.

ballscrewbob:
Each component has a different lifespan depending on quite a lot of variables.

Voltage, Current, Operating Temperature range, Memory writes (both V and Non V and EEPROM vs EPROM), Humidity, and a few more besides.

The only way to know is for YOU to work out what that is as you have given zero detail in any of that regards and it is simply beyond the scope of the forum to do that work for you.
Then use your application of those figures as a measure of how far you will be pushing each of those items and use the shortest lifespan as a very basic MTBF.

I think he was "assuming" that the MTBF analysis was done.
Otherwise, his company would have pay for it themselves if such an analysis is important to their customer base.

.