State: modelled; a verification kit for PCM600 is shipped and waiting for its report. Not run against PCM600 or any vendor tool, and not run on Windows. The PCM600Cmd contract comes from PCM600Cmd 2.14's own help and behaviour captured on a real installation; versions 2.11 to 2.13 are untested.
Vendor tools run as separate processes with your own rights. Nothing is written to the registry or Program Files.
Detect vendor tools (Windows)
- Run Detect Vendor Tools, or open the Vendor Tools view in the Explorer (it detects when first shown).
- The view lists what is installed, with versions: Hitachi Energy PCM600, Siemens DIGSI 5, SEL AcSELerator QuickSet and Architect, Helinks STS and OMICRON IEDScout.
Detection reads the Windows Uninstall registry keys with the reg.exe Windows ships (no administrator rights) and, for PCM600, its PCM600_<version> folders. On other operating systems the view says detection is for Windows.
Open a tool
Open in <tool> starts the tool on its own, without a file: no tool documents a file argument. The program is the one its installer registered, or one you pick once. To fix the program per tool, set neuralInverse.energy.vendorToolExecutables, an object with one entry per tool: pcm600, digsi5, selQuickSet, selArchitect, helinksSts and iedScout, each the program that opens it.
DIGSI 5, the SEL tools, Helinks STS and IEDScout offer detection and Open only: no automation interface was found for them.
Exchange the SCD with PCM600
Set neuralInverse.energy.paths.pcm600Cmd to PCM600Cmd.exe or its folder, or leave it empty to use the newest PCM600 found. Paths of 260 characters or more are refused.
Use a copy of a project or a scratch project, never a production project.
- Export SCD from PCM600 Project writes a project's SCD without opening PCM600, then opens the file.
- Import SCD into PCM600 Project imports an SCD into a project. The confirmation says how many IEDs the file has, because PCM600 by default leaves out IEDs of unknown type without an error, and says that no PCM600 command takes an import back.
PCM600Cmd's exit code is 0 even on failure, so the module decides the outcome from PCM600's log lines and the written file, never from the exit code alone. Each run gets its own log file, decoded by its byte order mark. The command lines and their output go to the Energy output channel.
Not verified
- Any run against PCM600 or another vendor tool;
reg queryoutput on a real Windows, including non-English Windows. - The Uninstall names and install folders of DIGSI 5, SEL, Helinks and IEDScout.
- Which program opens the PCM600 window.
- Launching tools from a folder whose name holds
, ; =(tested with Windows rules on Linux only).