Raylux 0.31.0: four drivers, an OPC UA server, and 21 CFR Part 11

A large release: four new protocol drivers, OPC UA server support, electronic signatures, and the Edge product tier.

Four new drivers

DNP3 (with sequence-of-events timestamps and unsolicited data), BACnet/IP, Siemens S7 over ISO-on-TCP, and Omron FINS over TCP and UDP. All five drivers the gateway can run are now creatable from the gateway interface.

The gateway is now an OPC UA server

Raylux has been an OPC UA client for a long time. It now serves as well, with application certificates, client-certificate quarantine, and a configuration check that refuses a setup no client could connect to.

21 CFR Part 11 electronic signatures

Electronic signatures over a tamper-evident audit trail. Requiring a signature is an enforced tag policy, not advisory, and screen controls opt in individually. This is the compliance feature regulated industries ask for first.

Raylux Edge

Two licensed products on one signed field: Edge Panel, a local HMI for a single panel, and Edge I/O, field data collection with no visualisation. They behave oppositely, so the licence carries them as two distinct kinds and deliberately refuses an ambiguous "edge" rather than guessing.

Studio

• Visual version control and component-level screen comparison, against the live project.
• Copy and paste as JSON for tags, types, tag groups, screens and components, plus file-level export and import.
• Tag group assignment when a tag is created, and starter groups for fast, slow and historised tags.

Alarm notification

Not finished at this release, but the design-time half landed, and two real faults were found only by actually sending:

• Every secure configuration used the wrong connection method, so the shipped default port could not reach any of the common mail providers.
• Attachments were encoded twice, so every scheduled PDF report would have arrived unopenable.

Configurations that parsed and resolved but would have reached nobody are now either warned about or refused.

Also fixed

• The OPC UA server bypassed the electronic-signature requirement entirely.
• Saving a device through the gateway interface dropped most of its settings.
• The gateway failed to start on Windows in a particular start-up ordering.