Set up the Energy module

State: the switch, entry points, status bar item and walkthrough are modelled: covered by Electron tests on Linux. The keys have not been tried on Windows or macOS or with non-US keyboard layouts.

Requirements

No extra runtime is needed: TLS runs on the Editor's own Node runtime, and nothing is fetched at run time.

Turn the Energy environment on

1. Open a folder with SCL files (.scd .ssd .icd .iid .cid .sed) or COMTRADE records (.cff, or a .cfg with its .dat) and trust it.
2. A notification offers once to enable the Energy environment. Accept it, or run Neural Inverse: Enable Energy Environment from the Command Palette. This turns on neuralInverse.energy.enabled (off by default, window scope). The Editor never turns it on by itself.
3. Disable Energy Environment turns everything off again: views, commands, title bar items, the status bar item, keys, the walkthrough and the agent tools. Online connections are closed and a live capture stops.

Detection for the offer lists folders only, three levels deep, skipping build and dependency folders.

Work on copies of your station files, under Git: the change record can use the version committed at Git HEAD as the previous version of a file (see confRev and the change record).

Entry points

All commands are under Neural Inverse Energy in the Command Palette.

The walkthrough

On the Welcome page (Welcome: Open Walkthrough...), Get Started with IEC 61850 Substations has eight steps: open your station, check the station, follow the data flow, see the single line, review relay settings, analyse a disturbance record, check a GOOSE and Sampled Values capture, export an IED configuration. A step is ticked only when its outcome is shown (the file in its editor, the Station view with files, a .cid file written), not when you press its button.

The Energy log

The module writes to the Energy output channel (View > Output, then pick Energy). Its file is logs/<window>/neuralInverse.energy.log. It records schema folder loading, imports and upgrades with their changes, vendor tool command lines and output, online associations, browses, confirmed writes and disconnections, and live capture command lines. See Approvals and the Energy log.

Settings

Details are in the reference.

On Windows

The module is written for a managed Windows laptop: offline, without administrator rights and without an extra runtime. Nothing has run on Windows yet. The code was reviewed line by line for Windows, offline, proxy and no-administrator use, and 18 items were fixed, each tested with Windows rules on Linux. Among them:

• registry values are read with the reg.exe Windows ships, through a UTF-16 export so install paths in any language keep their letters; nothing is written to the registry or Program Files;
• tool paths pasted with quotes ("Copy as path") or typed without .exe are accepted;
• downloads and exports refuse names Windows treats as devices (CON, COM1) or changes (a trailing dot or space);
• CSV files written for Excel start with a UTF-8 byte order mark, and Export Signal List for Excel... uses your regional list and decimal separators;
• DER .cer certificates (the Windows default export) are read;
• COMTRADE records whose names are not UTF-8 open in Windows-1252, with a choice of 14 code pages.

Keys held in the Windows certificate store, on smart cards or in a TPM cannot be used for TLS; export the certificate with its key to a PKCS#12 file (see MMS over TLS and credentials).

Smoke test

With a folder of station files open and the environment on:

1. The Explorer shows the IEC 61850 Station view listing your SCL files, and the Vendor Tools view.
2. The status bar shows the number of SCL files and the errors and warnings Problems lists for them.
3. Press Ctrl+Shift+Alt+D and pick an SCD: it opens in the IEC 61850 System editor.
4. Run Disable Energy Environment: the title bar buttons, keys, status bar item and walkthrough go away.