The product workspace

Ask the demo cell a real question.

This is the actual BlueRidgePLC workspace, running against a sanitized deterministic demonstration cell. No customer PLC is connected. Every answer declares its mode, cites only supplied evidence, and names what’s missing.

Fault, change, and recovery-readiness analysisL5X logic ingestion · other formats are evidence packs: received, not parsed into logicDeterministic safety gate before any answer

CONTROL BRAINEvidence-grounded PLC decision support

SANITIZED DEMO FIXTURE · DETERMINISTICdemo-pt104

Public demo workspace. Uploads here are ephemeral sample evidence packs, not stored projects. Do not upload confidential plant logic or production data — customer L5X projects are uploaded inside the authenticated product workspace after qualification.

Your question (editable)

Sample scope: this project answers one fault question — why Pump 4 will not start — plus the change-diff and recovery-readiness scenarios. Unknown equipment and unsupported symptoms are declined, never guessed.

Supported sample questions

Control Brain finding

LS-104 low-low is blocking the start permissive.

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. The normally closed LS_104_LLO instruction therefore evaluates false, breaking rung continuity before P104_START_PERM. This establishes the blocking condition for that snapshot only; the physical root cause (a true low-low level versus a switch, wiring, or input-channel fault) is not yet established and requires field corroboration.

Confidencehigh · qualitative

Next approved actionVerify the field state

Under the approved read-only procedure, compare the LS-104 field indication with terminal X2-17 and the slot 4 channel 7 input LED. Capture a photo in Mobile Field Check. Do not bypass the interlock.

read-only

Check my cell’s fit

Evidence cited4

1Routine P104, rung 27

P104_START_PERM requires START_REQ, AUTO_MODE, NOT ESTOP_ACTIVE, NOT LS_104_LLO, and VFD_READY.

Source: Routine P104, rung 27Source version: L5X sample export BRPLC-PT104-V12State: verifiedEV-R27

2Read-only sample tag export

START_REQ=true AUTO_MODE=true ESTOP_ACTIVE=false LS_104_LLO=true P104_START_PERM=false

Source: Read-only sample tag export 2026-08-29T14:12ZObserved: 2026-08-29T14:12ZState: observedEV-SNAPSHOT

3PowerFlex sample fault export

VFD_READY=true Active fault count=0

Source: PowerFlex sample fault export 2026-08-29T14:12ZObserved: 2026-08-29T14:12ZState: extractedEV-VFD

4Electrical drawing E-104

LS-104 terminates at X2-17 and maps to slot 4 channel 7.

Source: Drawing E-104 page 6Source version: Drawing E-104 rev CState: verifiedEV-E104

BOUNDED ANALYSIS

INC-PT104-001 · ROUTINE P104 / RUNG 27

System ready

IEC 61131 LOGIC TRACEINC-PT104-001 · ROUTINE P104 · RUNG 27 · SAMPLE SNAPSHOT 2026-08-29 14:12Z · NOT LIVE

satisfiedblockingnot energized

Read-only observation of a sample snapshot. Interpreting a status does not validate a safety function.

Normalize

Trace

Correlate

Policy

Answer

Signals / normalized facts · SAMPLE 2026-08-29 14:12Z · NOT LIVE PLANT STATE

Tag / factStateValueRole

START_REQon1Operator start request

AUTO_MODEon1Automatic mode enabled

ESTOP_ACTIVEoff0Emergency-stop chain clear

LS_104_LLOon1Low-low level interlock active

VFD_READYready1Drive ready, no active fault

P104_START_PERMblocked0Output permissive not energized

Bounded hypotheses

Process low-low interlock is legitimately activeThe logic and read-only snapshot agree that LS_104_LLO is active while the rest of the start chain is satisfied.

Field switch, wiring, or input-channel faultThe drawing maps the signal to X2-17 and slot 4 channel 7, but no current field evidence confirms the physical state.

Unexpected logic or drive faultThe reviewed rung and drive export do not support either condition.

AI observes, explains, compares, and drafts. Qualified humans control every production action. Interpreting a status does not validate a safety function. Logic ingestion is L5X-only; other uploads are evidence packs: received, not parsed into logic.Ready

Why this is not a PLC chatbot

Answers are produced by a deterministic trace engine over your parsed logic, the same engine that refuses to guess when a tag doesn’t exist. A language model, when one is configured, only narrates what the engine already proved. The system has no controller connection and no production-write surface.

01Evidence first

The engine works from normalized sources with stable IDs, not an open-ended description of the plant.

02Cited, bounded conclusions

Findings, citations, missing evidence, stop conditions, and escalation are validated before display, and conclusions stay qualitative.

03Field handoff

The approved read-only next step can become a Mobile Field Check task with the same evidence lineage.

Your cell, answered the same way.

A control cell is one machine and its controls — a pump skid, a conveyor section, a packaging machine. Tell us about one of yours and we’ll confirm whether it qualifies for the 90-day PLC First Response Pilot, usually within two business days.

Check my cell’s fit See a sample incident report See a verified equipment record (sample)