# Difference between revisions of "Finding damaged cables"

### Or, measuring stuff for nerds :-)

You know when you have a long non working cable that is built into the fabric of a building, you can see both ends, and they don't appear to be connected but you know they should be?

It might be an existing cable that used to work, but a rodent, or a careless picture hanger with hammer and nail, has got too close to it. Perhaps it is one you just spent hours pulling through conduit, under floors, into cable ducts, and plaster chases, but now you know something you did damaged it. The immediate question is then, how do I find the damage and fix it, without ripping it all out and starting again?

### Here are a few ways

#### Cable resistance

If you have a sensitive low ohms meter, then sometimes you can use some careful measurements of cable resistance to find the location of a fault. This tends to work best when the fault is a short circuit, typically caused by something metal penetrating a cable like a screw or a nail.

Say you have and length of twin and earth cable, that is tripping the MCB as soon as you power it. With both ends disconnected, a quick resistance check between the cores might show that there is a Live to Earth fault on the cable. Now using a resistance table like this, you can quickly get a feeling for how far away from your end of the cable the short might be. If you then deliberately add a short at the far end between a couple of the other cores, then you can also get a feel for the resistance of the total length of cable. Repeating the test at the far end should give more confidence of the location.

#### Cable capacitance

A capacitor is created by having two conductors separated by a small insulated gap. It can store electrical charge in the electrical field created between the two conductors. This means that a cable will show some (very small) capacitance between the cores. So if you can measure the capacitance between the cores of a cable, and know (or can measure) the capacitance between the cores of a known length of cable. You can estimate how far from one end to the other, or one end to a break.

The snag is that the capacitance of a length of cable is typically tiny, we are usually talking pico Farads per meter (where 1 pF = 0.000000000001 Farad!). So to use this directly you will need a sensitive meter designed for this kind of measurement. Some multimeters can measure capacitance, but they normally can't read much below 1 nano Farad. However this may give a rough idea on very long cable runs. A dedicated LCR meter will give a much more accurate result.

Many network cable testers, are also able to measure cable lengths using this method. So for example you have a CAT 5E network cable with a broken pair, you may be able to use your cable tester to measure the capacitance on a couple of different sets of pairs. The one with the break will typically show a lower capacitance. The ratio of readings giving an indication of the location of the break.

#### Time Domain Reflectometry

Another way to take advantage of the cable's capacitance to make measurements is using a Time Domain Reflectometer (TDR). If you inject a signal into a cable, there will be a brief period where the cable's capacitance will allow it to "charge up" in response to the injected signal. This charge then propagates along the cable. Should it reach the end (or an interruption), and find there is no attached "load" for it to flow into, that stored energy needs somewhere to go. So it will bounce back down the cable like a wave bouncing back from the edge of a pool.

At the injection end of the cable, there will be a brief period of time where you can see the effective load of the cable on the signal change while it charges initially, and then when when any reflections return.

A dedicated TDR is a sophisticated (and expensive) bit of test equipment, that can make measurements on cables by injecting a sharp electrical pulse or "edge" into a cable, and looking for the characteristic reflection that will tend to "bounce back" from with the end of the cable (or from the place that a step change occurs in the cable's characteristics occur). By measuring the time between the pulse and its echo or reflection, it can estimate how far away the reflection was generated based on the propagation speed of the cable (which will typically be a significant proportion of the speed of light)

TDRs can be bought on their own, but the facility will often be found in the more expensive network cable testers.

One can cobble together a basic TDR capability using off the shelf test gear like an oscilloscope. So long as you have a way of injecting a pulse into your cable under test, the scope should be able to measure the time between injection and echo.

Here are some experiments made using a simple home made pulse generator and an oscilloscope.

##### The circuit

The pulse generator circuit used here is very simple and you can find examples similar to this dotted about the internet - here is a good explanation of the principle of operation from what may be the original author of this particular design.

This circuit uses a common IC that contains 6 simple "inverter" logic gates. (an inverter simply changes a "low" signal into an "high" signal, or a "high" signal into a "low"). If you connect the output of an inverter back to its own input, then it will switch back and fourth between high and low furiously trying desperately to keep up with its own output! This turns it into an oscillator. By adding a resister and capacitor to this feedback loop we can slow it down to get a moderate speed output. (the values used here give a square (ish) wave output at around 3.7kHz - the actual value does not really matter).

To get a good pulse for TDR style measurements, it ideally needs a nice fast "rise time". I.e. the change in voltage from off to on needs to happen very quickly. To get this a "Schmitt trigger" inverter is used. This has the advantage of not only a fast rise time, but it also gives very clean high or low outputs, without any indeterminate value should the input not be clearly defined.