PLC troubleshooting for maintenance teams
By Blue Ridge Electric Service
Trace supported Rockwell logic to the blocking condition, see the cited rung, and give your team a clear next check.
A control cell is one machine and its controls: a pump skid, a conveyor section, a packaging machine. The pilot proves the workflow on one of yours.
Rockwell-first. Read-only. Scheduled engineer review.
Static logic establishes dependencies and candidate blocking conditions; only timestamped state evidence can establish an actual blocking condition. The trace names the exact check to make next.
A stopped line with the answer in the logic. The 90-day pilot proves cited, field-verified fault tracing on one of your cells.
Rockwell ControlLogix and CompactLogix cells, ingested from an L5X export. Read-only always: no writes, forces, downloads, or bypasses, and no live controller connection. Non-safety-critical cells only. Answers are deterministic and cited to the exact rung; a controls engineer reviews on a scheduled basis.
Recurring communication faults or undocumented cabling serving production equipment, scoped, tested, and documented by the same shop.
Physical connections serving PLCs, drives, HMIs, and switches: inspected, tested, and documented against what is actually installed. Fiber inspection, cleaning, testing, and repair where scope and qualified personnel support it. Unknown connections are marked unknown, never guessed. Scope, technician fit, and availability are confirmed before scheduling.
Where this fits
A packaging line won’t cycle. A pump won’t start. A drive sits ready but the permissive chain says no, and someone is reading ladder rungs under pressure. BlueRidgePLC traces the supported logic to the blocking condition and cites the exact rung, so the first check happens in minutes, at the right terminal.
The guard-door fault clears, returns, clears again. Each visit starts from zero because the last diagnosis lived in someone’s head or a contractor’s notebook. Every incident in the pilot cell keeps its trace, its cited rungs, and its field evidence, so the repeat fault starts from what was already proven.
The veteran who can read the press logic by heart is retiring, or simply not on shift. That know-how is worth preserving, not replacing. BlueRidgePLC makes the cell’s logic legible to the whole team, with the senior technician’s judgment captured in reviewed scenarios.
Guided incident demonstration
This is the PT-104 sample pump cell: sanitized deterministic sample evidence and a simulated review, not a customer PLC. Follow incident INC-PT104-001 the way your team would: ask the question, read the finding, verify in the field.
No special syntax. Edit it: the engine resolves equipment names against the loaded sample project, or says it cannot. Try “Pump 99”.
In the read-only sample snapshot observed 2026-08-29 14:12Z, the start request, automatic mode, emergency-stop chain, and PowerFlex-ready state are satisfied while LS_104_LLO is active, so the normally closed instruction evaluates false and P104_START_PERM stays de-energized. Timestamped state evidence establishes the blocking condition for that snapshot. The physical root cause is not yet established: a true low-low level, or a switch, wiring, or input-channel fault, is exactly what the field check must observe and record.
The read-only sample snapshot observed 2026-08-29 14:12Z shows LS_104_LLO active while every other permissive on the rung is satisfied, so continuity stops at the highlighted contact and P104_START_PERM stays de-energized. Timestamped state evidence establishes the blocking condition for that snapshot; the physical root cause (a true low-low level, or a switch, wiring, or input-channel fault) is not yet established and is exactly what the field check must observe and record.
Read-only sample observation. Interpreting a status does not validate a safety function.
Routine P104 · Rung 27 · L5X sample export BRPLC-PT104-V12
XIC(START_REQ)XIC(AUTO_MODE)XIO(ESTOP_ACTIVE)XIO(LS_104_LLO)XIC(VFD_READY)OTE(P104_START_PERM);Static logic establishes the dependency chain and the candidate blocking conditions; only timestamped state evidence can establish an actual blocking condition. Drawing E-104 page 6 maps LS-104 to terminal X2-17, slot 4 channel 7.
A deterministic parser reads the L5X export and builds a control graph of the cell: every tag, rung, and routine with its exact location. The trace engine walks the blocking chain from the target output to the first unsatisfied permissive and cites the exact program, routine, and rung. Conclusions stay qualitative: satisfied, blocking, unknown, never numeric confidence. Unknown tags return cannot-determine and unknown equipment returns equipment-not-found; the engine never invents tags, rungs, assets, or plant state.
The task asks the technician to observe and record the actual state; it never assumes an answer. The observation is logged as agreeing, disagreeing, or missing evidence, and the trace plus field record stay attached to INC-PT104-001 for the scheduled controls-engineer review. The sample snapshot (2026-08-29 14:12Z) reported this input active; only the field observation can corroborate the physical state.
Illustrative photograph, not a Blue Ridge person or facility. Task text is the real observe-and-record format.
See a sample incident report and the verified equipment record — the records your team keeps after a verified incident, generated from this same INC-PT104-001 fixture.
The PLC pilot
Ninety days, one control cell, one fixed price. Success is measured the way we agreed at the start: the five engineer-reviewed acceptance scenarios, answered by your team, verified in the field.
We confirm your cell qualifies: non-safety-critical Rockwell, with an L5X export your controls person or integrator can provide. The export is ingested into a plant-specific workspace. If the cell doesn’t qualify, we say so before anyone invoices anything.
Your effort: one L5X export and a walkthrough conversation.
Together we pick five acceptance scenarios: real fault questions your team actually faces. A controls engineer reviews each trace against the logic before your team ever relies on it.
Your effort: one review session with the people who know the cell.
Your technicians (2–5 accounts) work live incidents in the workspace and verify cited answers at the cabinet with Mobile Field Check: observe-and-record tasks with explicit stop conditions.
Your effort: normal incident response, with the tool alongside.
We review the five acceptance scenarios against what actually happened, hand over the incident history and the final results report, and discuss what, if anything, comes next.
Your effort: one closing review. The report is yours either way.
Scope and cell eligibility are confirmed before kickoff. If your cell doesn’t qualify, we tell you before anyone invoices anything.
Engineer review is scheduled within the business scope agreed at qualification. This is not a 24/7 emergency service.
Preview the pilot scope — the one-page scope document reviewed during qualification.
L5X logic ingestion only: other formats are evidence packs, received and cited, not parsed into logic. Rockwell first: other platforms are not supported today. Read-only always: no PLC writes, forces, downloads, bypasses, or setpoint changes. Deterministic by default: answers are engine-derived and cited to the rung. No safety-instrumented systems. Engineer review is scheduled, not 24/7.
How the work progresses
You own and can export every report your engagement produces, pilot or otherwise.
Enter a downtime cost per hour above to see the break-even point. No values are assumed for you.
Assumptions shown: pilot price $24,000 for 90 days; the savings figure is an annual rate from your inputs; downtime only, no labor, scrap, or other costs counted. Illustrative arithmetic on your own inputs, not validated or promised savings. Any future savings depend on continuation access after the pilot, ongoing costs, when stoppages actually occur, and improvement demonstrated during the pilot. Qualification confirms whether your cell fits the pilot before anyone invoices anything.
Additional field services
Recurring communication faults, damaged connections, or undocumented cabling? Discuss a scoped assessment of the connections serving your production equipment.
Physical connections serving PLCs, drives, HMIs, and switches: inspected, tested, and documented against what is actually installed.
Plant fiber inspected, cleaned, tested, and repaired where the scope and qualified personnel support it, with measured results recorded.
Endpoint and port records, labels, and approved photographs, with unknown connections marked as unknown, never guessed.
Scope, technician fit, and availability are confirmed before scheduling.
Who stands behind this
BlueRidgePLC is a department of Blue Ridge Electric Service, an industrial electrical and controls service company in Winchester, Virginia. The software exists because our own field work kept hitting the same wall: plants with solid maintenance teams and no one left who could read the logic.
The pilot proves the model one cell at a time: cited, verified in the field, and honest about what the evidence can’t determine. When the evidence runs out, a human controls engineer reviews the incident on a scheduled basis.
Buyer questions
Straight answers, including the honest edges. Anything that depends on your plant is discussed during qualification; we don’t publish commitments we haven’t scoped.
Rockwell ControlLogix and CompactLogix, ingested from an L5X export out of Studio 5000. Siemens, Mitsubishi, and other platforms are not supported today. Pilot cells must be non-safety-critical; no safety-instrumented systems.
One L5X export per pilot cell, produced by whoever holds your Studio 5000 project: your controls person or your integrator. Logic ingestion is L5X-only. Other materials (drawings, documents, photos) can be attached to an incident as evidence packs: received and cited, not parsed into logic. BlueRidgePLC is read-only software: it never writes to, forces, or downloads to a controller, and it has no live controller connection.
Engineer review is scheduled, not round-the-clock. The five acceptance scenarios are reviewed before team use, and field verification results feed a scheduled review. Response timing and any on-site involvement are discussed during qualification; we don’t promise coverage we haven’t scoped with you. This is not an emergency service.
Provide the L5X export, nominate 2–5 technicians, and have them use the workspace and field checks on real incidents. Your people keep every production decision; the software never authorizes work, and every field task keeps its stop conditions on screen.
You keep the incident history and the final results report either way. Continuation terms and any post-pilot pricing are discussed at the final results review; nothing renews automatically and there is no obligation past the pilot.
You can, with what you already have: every report and the incident history are yours to keep and export, so your own team can carry them forward. If you would rather we keep the cell’s records current with scheduled reviews, that is an optional ongoing service discussed during qualification, with scope and terms confirmed separately. Nothing renews automatically, and the pilot does not depend on it.
It does not guess: unknown tags return a cannot-determine answer, and missing field evidence is shown as missing, never filled in. It does not touch safety systems, does not bypass interlocks, and does not give anyone new electrical qualifications. Your technicians verify; they don’t improvise.
Next step
Tell us about one control cell — one machine and its controls, like a pump skid or a conveyor section. We’ll confirm whether it qualifies for the pilot, usually within two business days. A short conversation, not a commitment.
Want to see the product first? Open the full demonstration workspace or see how Mobile Field Check works.