Interlocking Logic Tester (IEC 61850 / GOOSE, offline)

Write the interlocking release conditions of a bay as they are configured in the bay controller, and optionally as the specification states them. The tester evaluates every combination of switchgear positions — including intermediate and bad positions — compares the implementation with the specification, checks that a lost, invalid or test-mode GOOSE input blocks, and writes the FAT / SAT test steps.

Signals

Implemented logic

Specification (optional)

Result

Enter the signals and the logic, or load the example.

Tool guide · know before you use

What this tool is, how it works and how far to trust it

An offline tester for bay interlocking conditions: it evaluates the release logic over every combination of switchgear positions and checks it against a specification and against fail-safe rules.

Read this before relying on a result. Every method, formula, assumption and limit is stated here, so you can check the answer yourself instead of accepting it blindly.

What it can do

  • Read conditions such as QA1 = OFF & QC1 = OFF & (QB2 = OFF | BC_QA1 = ON) with double points (ON, OFF, INT, BAD) and single points.
  • Evaluate every combination (up to 65 536 per condition) with fail-safe logic and compare with the specification: unsafe and restrictive differences.
  • Show where a quality-blind implementation would still release when a GOOSE input is lost, invalid or in test, and where a BAD position satisfies a '!=' test; find contradictions and conditions that block nothing.
  • Write test steps: a released state, each input changed to the value that must block, and each GOOSE interrupted.

Why you need it

  • A misplaced bracket or a '!=' test can release a disconnector or earth switch in hundreds of position combinations that nobody tests by hand.
  • With GOOSE, positions of other bays travel over the network: the logic must block when a message is lost, invalid or from a device in test.

Understand this first

  • A double point has four states: intermediate (00), off (01), on (10) and bad (11). Only a definite position may release an operation.
  • In IEC 61850 the interlocking function (CILO) gives EnaOpn / EnaCls; the control (CSWI) refuses an operation without the release.
  • Operator precedence: NOT before AND before OR (as in IEC 61131-3). 'A & B | C' means '(A & B) | C'.
  • Fail-safe: an unknown input (bad position, invalid quality, GOOSE time allowed to live expired, test mode) must block.

What you need before you start

  • The signal list of the bay (position names, double or single point, local or GOOSE with the publishing IED).
  • The release conditions as configured in the bay controller, and the specification if available.
  • A current browser (Chrome, Edge, Firefox or Safari). Nothing is installed and your data is never uploaded; it is processed on your own computer.

How to use it

  • List the signals, then write one condition per line: name: condition. Use the same names in the specification.
  • Read each condition's findings, then the differences, released states and test steps.
  • Export the test sheet for the FAT or SAT.

What you get

  • Per condition: combinations, released states, differences from the specification, fail-safe findings and test steps; a CSV test sheet.

How to read the results

  • Released where the specification blocks: unsafe — correct the bay controller logic.
  • BAD position satisfies a '!=' test: rewrite with '= OFF' / '= ON'.
  • GOOSE input that keeps the release when lost: configure the subscriber to use the quality and GOOSE supervision so a lost input blocks.

Technical basis

  • IEC 61850-7-4 CILO / CSWI; IEC 61850-7-3 Dbpos and quality; IEC 61850-8-1 GOOSE time allowed to live and simulation. Evaluation by exhaustive enumeration with three-valued (Kleene) logic: unknown never releases.

Limits: when not to rely on it

  • It tests the logic you write, not the device: transcribe the configured logic exactly and confirm in the FAT.
  • Timing (operating times, sequences) and dynamic conditions are not modelled.

For preliminary engineering use. Results must be checked by a qualified engineer against the project's standards. How results are checked · Terms & disclaimer · Build 0473054 · 2026-11-14