Cable work often happens under pressure, in poor conditions, and with little room for uncertainty. When a low-resistance fault refuses to produce a clear acoustic signal, pinpointing becomes much harder, especially when you are relying on surge-based methods to confirm the exact fault location.
That is why teams turn to fault-burning in the first place. Used carefully, fault conditioning can help move a difficult fault towards a state that is easier to locate. The problem starts when that process is pushed too far. At that point, fault burning stops helping the job forward and starts making pinpointing much harder. M-THUMP5 supports fault conditioning, Burn ARM prelocation, and a guided sequence from fault identification to fault prelocation and pinpointing.
To understand why over-burning creates problems, it helps to look at why operators use the technique in the first place.
When a cable fault is unstable or does not produce a dependable flashover, operators may use burning or fault conditioning to change the fault state and make it easier to locate. The aim is to alter the resistance to a usable level and create a more stable condition for surge-based pinpointing. In M-THUMP5, this sits within a broader workflow that includes DC proof testing, insulation resistance measurement, prelocation methods such as TDR, ARM, ICE and Burn ARM, and then pinpointing once the fault condition is clearer.
When applied correctly, fault burning can be a useful step in the process. The problem is not fault burning itself. The problem is fault burning without enough visibility to know when the fault has reached the point you need.
Fault burning becomes risky when the operator is relying only on experience and indirect feedback to judge when the fault is properly conditioned.
Once the insulation has carbonised, continuing to push current through the fault can generate enough heat to melt the copper or aluminium conductors. Those metals can then fuse together, creating what the industry refers to as a bolted fault. Instead of a resistive path or small gap that allows energy to build and flash over, you are left with a solid low-resistance connection between conductor and screen, or conductor and earth. The visual explainer and draft video script you attached both describe this tipping point as the moment where a difficult fault becomes bolted and the process starts working against the team.
That is the threshold operators need to avoid. A step that was meant to help the fault reveal itself can now remove the conditions needed for acoustic pinpointing altogether.
A bolted fault creates a very different problem from the one you started with.
For a surge wave generator to produce a thump, the energy needs to jump across a gap or break down a resistive path, creating an arc and the acoustic signal that crews use for pinpointing. In a bolted fault, the surge energy flows across fused metal instead. There is no meaningful gap to break down, no arc, and therefore no dependable sound to follow. By over-burning the fault, you can eliminate the very acoustic signal you were trying to create.
Once that happens, crews can be left walking the line listening for a sound that no longer exists. The job slows down, confidence drops, and the whole process becomes more uncertain.
When the fault goes silent, operators lose their primary method of pinpointing. A TDR may still help with prelocation, but prelocation alone does not confirm the exact excavation point. Without a usable acoustic signal, crews can end up working from estimates rather than clear confirmation. The product materials themselves distinguish between fault prelocation and fault pinpointing, which supports this point well.
That is where the practical cost starts to build:
And when the acoustic method no longer gives you a clear answer, the temptation is often to keep pushing harder.
The real issue is not fault conditioning itself. It is fault conditioning without visibility.
A stronger approach combines burning with real-time monitoring, so the operator is not relying entirely on instinct to decide when the fault has reached a usable state. M-THUMP5 supports this through Burn ARM prelocation, along with proof testing, TDR-based prelocation, ARM, ICE, and E-TRAY workflow guidance. Megger’s product literature describes E-TRAY as a pull-through, workflow-driven sequence that guides the user through fault identification, prelocation, and pinpointing, and suggests the next logical step.
That matters because visibility changes the decision. Instead of hoping the fault is ready, you can monitor the trace as it forms and stop at the point where the fault is sufficiently conditioned for the next step, without pushing further than necessary. The attached visual explainer and controlled-process video script both reinforce this exact story: visibility helps teams stop before the fault becomes bolted.
When you can see what is happening during conditioning, the whole process becomes easier to manage.
You are no longer relying on blind burning and delayed feedback. You are working from clearer condition data, making better decisions about when to stop, and improving your chances of preserving the acoustic signal needed for pinpointing. That helps reduce guesswork, avoid unnecessary excavation, and keep the job moving in a more controlled direction.
This is also where integrated workflow matters. M-THUMP5 combines multiple methods in one unit, including DC proof testing, fault conditioning, TDR prelocation, ARM, ICE, Burn ARM, surging/thumping, and voltage-gradient methods, with E-TRAY designed to reduce the training burden compared with a traditional thumper-only system. It also includes Quick Steps for less frequent users and Expert Mode for more experienced ones.
Fault burning remains a useful procedure, but only when it is handled with restraint and clear visibility of what the fault is doing.
Push a low-resistance fault too far, and you can turn a difficult pinpointing job into a much more uncertain one. Take a more controlled approach, and you give yourself a better chance of conditioning the fault without destroying the signal you need to finish the job cleanly.
That is why visibility matters. It helps you stop at the right point, preserve a clearer route to pinpointing, and work through difficult faults with more confidence and less guesswork.
When fault burning is pushed too far, a difficult low-resistance fault can become even harder to pinpoint. A more controlled process helps you see what is happening sooner, stop at the right point, and protect the acoustic signal you need to finish the job cleanly.
