Deutsch   English   Français   Italiano  
<jg0r1j1r2cdlnhev0v1gaogd3fj0kmdiim@4ax.com>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: ...!weretis.net!feeder6.news.weretis.net!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!feeder.usenetexpress.com!tr3.iad1.usenetexpress.com!69.80.99.23.MISMATCH!local-2.nntp.ord.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Mon, 15 Apr 2024 19:41:58 +0000
From: Joe Gwinn <joegwinn@comcast.net>
Newsgroups: sci.electronics.design
Subject: Re: Predictive failures
Date: Mon, 15 Apr 2024 15:41:57 -0400
Message-ID: <jg0r1j1r2cdlnhev0v1gaogd3fj0kmdiim@4ax.com>
References: <uvjn74$d54b$1@dont-email.me>
User-Agent: ForteAgent/8.00.32.1272
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 20
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-iGidheF8Nd7K1Xtk2VpZwTjrtOnpq3VRLC451p4L6+v3OehwMogCAFW1wsBfkITB8jD9kg/fYZpwyoK!hKFKn/YX4zWxDrd8sImpdyGn35oylrQGis6jQVXrCk0M0KcI4/pzSh9p1t/BOp/y5nen7TU=
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
Bytes: 2147

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...

There is a standard approach that may work:  Measure the level and
trend of very low frequency (around a tenth of a Hertz) flicker noise.
When connections (perhaps within a package) start to fail, the flicker
level rises.  The actual frequency monitored isn't all that critical.

Joe Gwinn