I mean, the simplest answer is to lay a new cable, and that is definitely what I am going to do - that’s not my question.

But this is a long run, and it would be neat if I could salvage some of that cable. How can I discover where the cable is damaged?

One stupid solution would be to halve the cable and crimp each end, and then test each new cable. Repeat iteratively. I would end up with a few broken cables and a bunch of tested cables, but they might be short.

How do the pro’s do this? (Short of throwing the whole thing away!)

You are viewing a single thread.
View all comments
1 point
*

Wire tracker maybe? You might want a higher quality version than that particular one if the cable run is long, one of the reviews suggest that the distance is limited.

permalink
report
reply
5 points

This one here does time domain reflectiometry which will tell you exactly where the break is:

https://www.amazon.com/Ethernet-NF-8209-Distance-Location-Measurement/dp/B08M3SRB2Q/

permalink
report
parent
reply
1 point

I was curious if that would work on ethernet cable! I’ve seen it done on coax, wasn’t sure if it would work well enough on UTP to be useful outside a lab setting. Cheap too. Cool!

permalink
report
parent
reply
1 point
*

Some of the reviews say it didn’t work for them to find a break, but I have that exact one and have had good luck with it. So YMMV. Obviously the ten times the price Fluke will do better.

TDR isn’t exactly rocket science and the speeds needed to do it are surprisingly reasonable. You can build your own for a few bucks if you have an oscilloscope as well.

permalink
report
parent
reply

Selfhosted

!selfhosted@lemmy.world

Create post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

Community stats

  • 3.5K

    Monthly active users

  • 3.4K

    Posts

  • 77K

    Comments