The Callout · a true story
The Callout: The Red Light That Was Perfectly Normal
The machine wouldn't run. A card had a blinking red light, so it got swapped. When that did nothing, so did the controller. The light was red because nothing was plugged into it — exactly what it's supposed to do.
A real callout · written by a working maintenance professional
A tech called for help: the machine wouldn't run. By the time I got there he'd already swapped a ControlNet card, because it had a blinking red light.
A red light isn't a verdict
Here's what that light was telling him: nothing was wrong. That card wasn't in use, and there was no cable plugged into it. An unused network card with no connection shows red by design — it's the card announcing that it's idle. He'd taken normal behavior for a fault.
The swap didn't change anything, of course, because there was nothing to fix. And then — for reasons he couldn't really explain — he swapped the controller too.
The swap you now own
Swapping a controller isn't a part change. It commits you to a whole recovery job, and now he was stuck: he couldn't set the controller's IP address. By then it was obvious he didn't have a method for working this system, so I didn't ask why he'd done any of it. There was no point.
I had to set the controller up from scratch, load the correct firmware revision, and download the program to get the machine running again. Through all of it he was completely unfazed. Two guesses, nothing fixed, no concern.
What this one teaches
Know your normal. Before you call an indicator abnormal, learn what that indicator does on a healthy, idle, or unconnected module. Manufacturers document this; five minutes with the manual beats a controller swap.
Two swaps, zero faults found, is the parts cannon. Each swap felt like action, but neither was based on a measurement or a symptom that matched.
Know what a swap commits you to. A controller swap means IP, firmware and program, every time. If you haven't proven the controller is bad, you've turned a small problem into a big one.
Reading about it is one thing. Doing it under pressure is another.
faultline101 drops you into scenarios where the readings respond to your choices — and where chasing the wrong theory costs you exactly like a real callout. You build the habit on equipment you can't break. Module 1 is free, no card required.
Works with no signal. Install it on your phone and the whole course — 35 modules, 210 faults — comes with you into the plant.
Try the trainer freeThe machine got running in the end, but the actual problem was never the card and never the controller. A red light is a clue, not a verdict.
This one's part of a set of real callouts I collected — they ended up drawn as a comic, because they're funnier on paper than they were to live through: Tales of a Troubleshooter, eighteen true rescues where the fault is never the thing the crew swore it was.