Gateway Mapping Builder — IEC 61850 to IEC 104, Modbus and DNP3

Build the signal list of a station gateway from the SCD: every value the IEDs report to the gateway and every controllable object, with an IEC 60870-5-104 type and information object address, a Modbus register and a DNP3 point allocated by rules you set — then compare it with the point list exported from the gateway tool.

SCD

Allocation rules

Gateway point list (optional)

Export from the gateway tool: a column with the 61850 reference, one with the IOA, optionally CA and type.

Result

Open an SCD or load the sample.

Tool guide · know before you use

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

A builder that derives the station gateway's signal list from the SCD and allocates IEC 104, Modbus and DNP3 addresses by rules — and checks the gateway's own point list against it.

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

  • Collect the members of data sets used by report control blocks whose client is the gateway, and the controllable objects with a control model other than status-only.
  • Resolve each signal's common data class (also sub-objects such as A.phsA) and description from the SCD.
  • Allocate IEC 104 types (with or without time tag) and IOAs per IED and kind of signal; Modbus discrete inputs, input registers, coils and holding registers (32-bit values in two registers, word order selectable); DNP3 points with event classes.
  • Check duplicates, overflowing ranges, commands without position feedback, double control objects (CSWI and XCBR); compare a gateway point list by 61850 reference for missing, extra, wrong-type and different-address points.

Why you need it

  • The gateway signal list is usually retyped from the SCD by hand — the most error-prone step of SCADA engineering. Errors appear only at point-to-point testing.
  • Deriving the list by fixed rules and comparing the gateway's export with it removes typing errors before testing.

Understand this first

  • The gateway receives IED data through reports: only the members of the data sets of report control blocks enabled for the gateway can reach SCADA.
  • Each common data class has a natural telecontrol type: SPS/ACT/ACD → single point, DPS/DPC → double point, MV/CMV → measured value, INS/ENS → scaled value, BCR → integrated total; SPC/DPC/APC/INC/BSC controls → single, double, set-point and step commands (IEC 61850-80-1 gives the detailed mapping).
  • Modbus has no quality and no time stamp; IEC 104 types with time tag keep the IED's event time; DNP3 event classes decide what is reported as events.

What you need before you start

  • The SCD with the IEDs, data sets, report control blocks (with ClientLN) and data type templates.
  • The control centre's addressing convention, to set the ranges.
  • Optionally the point list exported from the gateway tool (CSV).
  • 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

  • Open the SCD (or load the sample) and choose the gateway IED.
  • Set the common address, the first IOA, the block per IED and the offsets per kind of signal, and whether time-tagged types are used.
  • Untick signals that must not be mapped (for example XCBR.Pos control when control goes through CSWI).
  • Export the mapping, enter it in the gateway tool, export the gateway point list and open it here to compare.

What you get

  • The mapping table in IEC 104, Modbus and DNP3 views, findings, and the comparison with the gateway list; CSV export.

How to read the results

  • Wrong type in the gateway (a double point sent as a single point): the control centre decodes the value wrongly — correct before testing.
  • Gateway points not in the SCD: wrong reference, or a data-set member removed — the point would never update.
  • SCD signals missing in the gateway: SCADA will not see them.

Technical basis

  • IEC 61850-6 data sets, report control blocks, ClientLN and templates; IEC 61850-7-3 common data classes; IEC 61850-80-1 mapping principles; IEC 60870-5-101/104 type identifications and IOA (3 octets, 1–16 777 215); Modbus data tables; IEEE 1815 object groups.
  • Allocation is deterministic: IEDs in SCD order, signals in data-set order, controls after.

Limits: when not to rely on it

  • The allocation rules are a proposal; the control centre's convention governs.
  • The tool does not write gateway configuration files.
  • References are compared after removing the attribute (stVal, general, mag.f, ctlVal); vendor-specific reference formats may need adjusting in the CSV.

Sample files for this tool

Download, open and compare with what the guide says you should see.

All sample files and what to expect →

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