Energy
Documentation

Version Latest

Gateway signal lists

Generate an IEC 60870-5-104 or DNP3 signal list for a gateway or RTU from the SCL file, edit it as CSV, and check it against the SCL file and the gateway's reports.

State: modelled. Tested on hand-written stations. The list is the module's own CSV format: no gateway tool (SICAM, RTAC, COM600, EcoSUI) imports it yet. The proposed types are the module's own rule, shown on screen, not checked against IEC TS 61850-80-1 or IEEE 1815.1.

The list

One point per row, in the module's CSV:

  • the protocol;
  • for IEC 104: the common address, the IOA and the type identification (by name or number);
  • for DNP3: the object group, variation, index and class;
  • the IEC 61850 source: IED, logical device, logical node, data object and attribute, FC;
  • scale, offset and description.

Generate a list from SCL

  1. Run Generate Signal List from SCL... and pick the SCL file.
  2. Pick the IEDs, then IEC 104 or DNP3; for IEC 104, the common address.
  3. Pick where to save. The Gateway Signal List editor opens with the proposed points, numbered from the next free IOA or index.

The proposed types:

IEC 61850IEC 104DNP3
SPS, and the status of SPCM_SP_TB_1Group 1 variation 2
DPS, and the status of DPCM_DP_TB_1Group 3 variation 2
MV mag and CMV cVal.magM_ME_NC_1Group 30
SPC and DPC Oper.ctlValC_SC_NA_1 and C_DC_NA_1Group 12 variation 1

Check a list against SCL

  1. Open the CSV with Reopen Editor With... > Gateway Signal List, then click Check Against SCL...; or run Check Signal List Against SCL... from the Command Palette and pick the list.
  2. Pick the SCL file and the gateway among the file's report clients.
  3. Findings appear in the table and in Problems on the row's line, and follow the list and its SCL file on disk.

What is checked:

  • values: protocol, address ranges in two and three octets, known type, group, variation and class, numbers;
  • an address used twice: IEC 104 per common address and direction, DNP3 per index space;
  • a source that does not resolve in the SCL file;
  • a type, class or FC that does not fit the data: BOOLEAN for single points and commands, Dbpos for double points, numbers for measurements, SPC or DPC with FC CO for commands;
  • monitored data in no data set that a report control block sends to the gateway, where the file names report clients.

For example, an IOA used twice reads: "The address (common address 1, IOA 1 in the monitoring direction) is used by line 2 too."

Edit and export

The Gateway Signal List editor shows the table with a filter and the findings. Click a row to open its line in the text editor, where you edit it. A CSV without the module's header opens with a message naming the header line it needs.

Export Signal List for Excel... writes a separate copy with a UTF-8 byte order mark and your regional list and decimal separators (; where the decimal separator is a comma); the module's own CSV is unchanged. A leading apostrophe keeps a field from being read as a spreadsheet formula.

Size

A list of 25,980 points is generated in about 0.8 s.

Limits

  • IEC 60870-5-101 and Modbus, quality and time tag mapping, counters and step positions, command options (select before operate, pulse) and dead bands are not modelled.
  • Gateway vendor formats are not read or written.
  • Edits are made in the text editor, not in the table.

Not verified

  • A gateway tool importing or exporting a list; a real station's list or vendor SCD.
  • Excel's own reading of the export.
  • Windows.

Last reviewed 18 October 2026View as Markdown

Gateway signal lists · Docs · Neural Inverse