Sujet : Re: Predictive failures
De : jl (at) *nospam* 650pot.com (john larkin)
Groupes : sci.electronics.designDate : 15. Apr 2024, 20:28:13
Autres entêtes
Message-ID : <u1sq1j1ikum0b2vrp0vji6mu115bp2s12l@4ax.com>
References : 1
User-Agent : ForteAgent/8.00.32.1272
On Mon, 15 Apr 2024 10:13:02 -0700, Don Y
<
blockedofcourse@foo.invalid> wrote:
Is there a general rule of thumb for signalling the likelihood of
an "imminent" (for some value of "imminent") hardware failure?
>
I suspect most would involve *relative* changes that would be
suggestive of changing conditions in the components (and not
directly related to environmental influences).
>
So, perhaps, a good strategy is to just "watch" everything and
notice the sorts of changes you "typically" encounter in the hope
that something of greater magnitude would be a harbinger...
Checking temperatures is good. An overload or a fan failure can be bad
news.
We put temp sensors on most products. Some parts, like ADCs and FPGAs,
have free built-in temp sensors.
I have tried various ideas to put an air flow sensor on boards, but so
far none have worked very well. We do check fan tachs to be sure they
are still spinning.
Blocking air flow generally makes fan speed *increase*.