Path: ...!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Martin Rid Newsgroups: sci.electronics.design Subject: Re:Predictive failures Date: Mon, 15 Apr 2024 13:32:41 -0400 (EDT) Organization: news.eternal-september.org Lines: 11 Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Injection-Date: Mon, 15 Apr 2024 19:32:44 +0200 (CEST) Injection-Info: dont-email.me; posting-host="e56ebcc5079992aa5316bd0409afecd3"; logging-data="441922"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19igk7GNms2Abj1uIL/oYBj" Cancel-Lock: sha1:UENGkPx7P+2dMizC/j5ntazP+Tk= X-Newsreader: PiaoHong.Usenet.Client.Free:2.02 Bytes: 1638 Don Y Wrote in message:r > Is there a general rule of thumb for signalling the likelihood ofan "imminent" (for some value of "imminent") hardware failure?I suspect most would involve *relative* changes that would besuggestive of changing conditions in the components (and notdirectly related to environmental influences).So, perhaps, a good strategy is to just "watch" everything andnotice the sorts of changes you "typically" encounter in the hopethat something of greater magnitude would be a harbinger... Current and voltages outside of normal operation? Cheers -- ----Android NewsGroup Reader---- https://piaohong.s3-us-west-2.amazonaws.com/usenet/index.html