Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > sci.electronics.design > #431028
| From | Don Y <blockedofcourse@foo.invalid> |
|---|---|
| Newsgroups | sci.electronics.design, comp.arch.embedded |
| Subject | "On-line" 100BaseTX hardware diagnostics |
| Date | 2016-10-12 12:33 -0700 |
| Organization | A noiseless patient Spider |
| Message-ID | <ntm35f$4pp$1@dont-email.me> (permalink) |
Cross-posted to 2 groups.
What sorts of hooks can I include in my designs to allow run-time testing of 100BaseTX hardware? Obviously, I can monitor traffic, throughput, CRC errors, etc. to give me a feel for degradation of the overall link. But, what can I do to diagnose things like cabling problems and failures without impacting the quality of the link hardware "otherwise"? (think "built in cable tester") An even tougher question: can I leverage a *partially* functional cable/interface to provide *limited* connectivity in the event of a failure that impacts the normal NIC-pair? (even if this is an either-or implementation)
Back to sci.electronics.design | Previous | Next — Next in thread | Find similar | Unroll thread
"On-line" 100BaseTX hardware diagnostics Don Y <blockedofcourse@foo.invalid> - 2016-10-12 12:33 -0700
Re: "On-line" 100BaseTX hardware diagnostics Grant Edwards <invalid@invalid.invalid> - 2016-10-12 20:33 +0000
Re: "On-line" 100BaseTX hardware diagnostics Don Y <blockedofcourse@foo.invalid> - 2016-10-12 15:48 -0700
Re: "On-line" 100BaseTX hardware diagnostics Robert Wessel <robertwessel2@yahoo.com> - 2016-10-12 17:47 -0500
Re: "On-line" 100BaseTX hardware diagnostics Don Y <blockedofcourse@foo.invalid> - 2016-10-12 16:07 -0700
csiph-web