Verification state: detection and the enable offer are modelled, tested on Linux with unit and rendering tests. Not seen in the running Editor by a DeltaV engineer; not run on Windows.
Turn it on
The module runs only while neuralInverse.dcs.enabled is on and the workspace is trusted. It is off by default.
- Open a folder that holds
.fhxexports (copies, in a scratch folder) and trust it. - The module detects
.fhxfiles in the workspace, in either case of the extension. A notification offers, once for that folder, to enable the DCS environment. Accept it, or run Neural Inverse: Enable DCS Environment from the Command Palette. This setsneuralInverse.dcs.enabledfor the workspace. - The DeltaV Plant view appears in the Explorer.
Disable DCS Environment turns it off: views, checks, the save guard and agent tools stop, and their markers go.
In an untrusted window where the setting is already on, a notification says the environment starts only once the folder is trusted, and nothing else runs. The FHX language and its colouring are available whether or not the environment is on; nothing else is.
Requirements
| What | Needed for |
|---|---|
| FHX exports from DeltaV Explorer (File > Export), UTF-16 or UTF-8 | Everything. The module reads exports in UTF-16 LE and BE and UTF-8, with or without a byte order mark |
| A Windows DeltaV engineering station (ProfessionalPLUS or DeltaV Simulate) with a non-production database | Only for Export DeltaV Database (FHX) |
| The DeltaV import in DeltaV Explorer | Bringing an edited export back into DeltaV, which you do yourself |
Nothing else is installed: the module's readers are its own code.
Work on copies
- Work on copies of exports, under Git, in a scratch folder, never on a plant's running database.
- Do not send plant exports outside your company.
- An export is often a part of the database. Checks and impact read one export at a time, so references to modules in other exports cannot be resolved.