← All posts
Maintenance Operations

Maintenance Technician Troubleshooting Tool for Live Faults

Learn what a maintenance technician troubleshooting tool should do during a live fault: plain-language symptoms, ranked causes, and one check at a time.

Open motor terminal box on a stopped conveyor drive, with multimeter test leads and a screwdriver resting beside it on the steel frame.

Using a maintenance technician troubleshooting tool during a live fault

A maintenance technician troubleshooting tool should do three things when a machine is down: accept a plain description of what the machine is doing, return a ranked list of likely causes, and offer one check at a time, each with a reason. Used this way, it helps the technician narrow the fault as results come in. It suggests causes and checks from a plain-language description, and you run the checks and record the results yourself. It is only as useful as the checks you actually perform and the safety steps your site requires.

What a troubleshooting tool has to do in the first minutes of a fault

On the factory floor the machine is stopped, production is waiting, and the manual is often in a cabinet at the other end of the line. The colleague who knows that machine may be on another shift or another line. Under that pressure, a generic web search returns articles that don't match your equipment, and a forty-page manual section describes every possible cause at once.

A useful tool needs a minimum set of behaviors. It must accept symptoms in ordinary words, because the technician describes what they see and hear, not a fault code from a table. It must rank causes so the most likely ones come first. It must give one next check rather than a full procedure, and state why that check matters. And it must work in a plain web browser, so the technician can switch between the control panel, the motor, and the cabinet without a heavy system to set up.

Missing any one of these is costly. Without ranking, the technician reads the whole list. Without a reason, the check looks arbitrary and gets skipped or run blindly. Without one check at a time, the list becomes a to-do list nobody finishes.

Walking through a motor that hums but won't turn

Describing the symptom the way the machine shows it

Start with what the machine does, not with what you guess is wrong. Motor hums but won't turn is a good description: it says power reaches the motor, something opposes rotation, and the shaft does not move. Add what changed. Did the fault appear at start-up or after running? Did it follow a maintenance task? Was the sound steady or pulsing? Each detail narrows the candidates. A hum that started after the machine sat idle over a weekend points toward different causes than one that began mid-shift under load.

Avoid naming a part you have not checked. Typing bad capacitor into a tool narrows the search to one answer before you have any evidence. Describe observations and let the ranked list show the options.

Reading the ranked causes and the reason beside each check

Once the symptom is entered, the list usually places mechanical and electrical causes side by side. For a humming motor that will not turn, the general families are a binding load or seized drive train, a supply problem such as a missing phase or low voltage, a failed starting component, and an obstruction outside the motor. The exact order depends on the tool, but the principle holds: quick checks that rule out a large group should usually come first.

The reason beside each check is the part to read. A reason such as rules out a mechanical lock before testing the electrical supply tells you why this check comes now. If the reason does not fit the machine in front of you, that is a signal to consult the machine's own documentation before continuing.

Electrical work on a motor requires de-energizing, verifying zero energy, and following your site's lockout and tagout procedure. No tool replaces those steps.

How results re-rank the list as checks pass and fail

After each check, record the result. A failed check removes or lowers the cause it was testing. A passed check can mark a cause as confirmed, and that is where the rest of the list changes. The next check is recalculated from what you now know, not from the original list.

This loop works better than a long list of possibilities for a practical reason. A list of twelve causes forces you to choose what to test, usually by intuition. A one-step loop makes each decision on evidence. After two failed checks, the remaining candidates are different, and so is the next action.

Fault Line AI does this re-ranking: when you mark a check passed or failed, the list is re-ordered and the next check changes to match. Keep the same discipline when you note results on paper, so a colleague taking over the fault can see what was tested and what it showed.

Before acting on any confirmed cause, verify it against the OEM documentation for that machine: the wiring diagram, the specified values, and the recommended replacement part. A confirmed cause in a tool is a hypothesis you have tested, not a repair instruction.

Where the tool stops: faults outside the built-in families

Be clear about scope. Fault Line AI has built-in guided checks for four fault families: motor hum or no start, hydraulic pressure loss, drive overcurrent or trips, and overheating or shutdown. For a fault outside those four, it gives a general list of checks rather than a guided sequence. Read that list as a starting point, not a diagnosis.

It also does not ask follow-up questions in a conversation. Guidance is a fixed set of checks, so if your situation differs from the description, you adjust the reasoning yourself. It does not search past repairs, so it cannot tell you what your plant fixed last time. It has no library of standard repair procedures beyond its built-in checks, and it does not record parts used or repair outcomes.

For those cases, use other sources. The OEM manual is the authority for specifications, values, and wiring. Your site's lockout and tagout procedure governs how the machine is isolated before anyone touches it. A senior colleague who has seen the machine fail before brings history no tool has. To decide which source to trust for which fault, start with the OEM manual for specifications and wiring, and use the lockout and tagout procedure for isolation.

Keeping the record: what is saved and when you need an account

You can use guided troubleshooting without signing in. Those results are not saved, so they cannot be picked up later or on another device. If the next shift needs to know what you tested, write it down before you leave the machine.

To keep a record in the product, sign up and log in. Saved symptom reports include the machine name, asset tag, and severity, and they stay on your account. The equipment catalog currently lists one machine, the Line 3 Belt Conveyor, with its manual and wiring diagram titles.

The product does not record the parts you used or the outcome of a repair, does not share diagnoses or repair records with other people, does not export your data, and sends no email, notifications, or reminders. Plan your handover around that: the symptom report holds the description and severity, and your own notes must hold the check results and the fix.

Try guided troubleshooting on Fault Line AI with a real symptom from your own machine. You can start without an account, and sign up if you want to save symptom reports.

FAQ

Can a troubleshooting tool replace the OEM manual or the site's lockout and tagout procedure?

No. A troubleshooting tool suggests likely causes and the next check to run. The OEM manual gives the machine's specifications and wiring, and the lockout and tagout procedure governs isolation and safe work. Use the tool to narrow the search, then confirm with those sources before acting.

Do I need an account to use a troubleshooting tool on the factory floor?

No. Guided troubleshooting in Fault Line AI can be used without signing in, but those results are not saved. Sign up only if you want to keep symptom reports with machine name, asset tag, and severity.

Will my diagnosis be saved for the next shift or another technician?

Guided troubleshooting results are not saved and cannot be picked up later or on another device. Symptom reports you save stay on your account, but they are not shared with other people, and the product does not record repair outcomes. Write down your check results for the next shift.