Meet the HG1v4

One HG1v4 can act as HART master for a Pepperl+Fuchs KFD2-HMM-16 multiplexer — up to 16 field transmitters per gateway across the MUX's channel bank. The web UI's Scan Devices tool discovers what the KFD2 sees on its loops and imports the transmitters you tick. Commissioning, Modbus mapping, and remote access all work the same as in standard gateway mode.

When enabled, every networked feature — the web UI, the HART modem (via the virtual COM port tool), Modbus TCP, firmware updates — is reachable from anywhere in the world through an integrated secure tunnel, free of charge — no subscription and no per-device fees. Traffic is carried over TLS with a trusted, publicly-signed HTTPS certificate — no self-signed warnings, no certificate management on your side. The gateway makes an outbound connection only, so there are no firewall ports to open and no VPN to run.

Disabled by default. For sites that don't want their device exposed at all, remote access stays off and the gateway is reachable only on the local network. When the operator chooses to enable it from the web UI, two strong role-based passwords are securely generated on the device and shown once for safe capture — they are not recoverable afterwards:

• Operator — view live data, run diagnostics and export configuration.
• Engineer — full edit rights over configuration, commissioning and firmware.

Remote access can be revoked at any time from the same page, immediately closing the tunnel and invalidating both credentials.

Remote access is provided at no additional charge and requires no subscription. It is opt-in per device and requires the gateway to have outbound internet access. Service terms may change for future products or releases.

The gateway periodically checks a signed download channel and notifies the operator when a new release is available. Updates are applied to a redundant root partition, so a failed update automatically rolls back to the previous working image. A choice of stable and beta channels lets you opt in to early access when you want it.

A dedicated Commissioning page in the web UI covers the everyday setup actions — setting the transmitter Tag, Descriptor, Message and Date; changing the polling address; trimming zero and span; and issuing standard HART universal and common-practice commands. Fields are automatically hidden or shown based on what each device actually supports, so you don't need a device-specific host tool for routine work.

Not a replacement for PACTware, FieldCare or SIMATIC PDM. For DD/FDT-based configuration — advanced calibration, method wizards, vendor-specific diagnostic screens — keep using those tools; the HG1v4 exposes a HART modem over USB serial or a virtual COM port so they work exactly as before.

A new Modbus Map page in the web UI lets you generate a minimal map tailored to the actual transmitters you have connected, a custom map hand-built to match an existing host system, or a legacy-compatible map that preserves v2-style register addressing for drop-in replacement. Preview the map before saving; the gateway restarts with the new layout in seconds.

HG1Discover is an all-new Windows app with the Lawnswood Technology look and feel. It finds HG1v4 gateways on the local network, opens the on-device web UI in one click, and pushes signed firmware bundles when you'd rather not wait for the OTA channel. Installer available from the Downloads page.

Live process data, device status and the running Modbus map are available as static files under /live/ — data.json, status.xml, dbexport.json and mbmap1.csv. Any HTTP client works: curl, PowerShell, Python requests, a browser tab, or an existing SCADA HTTP driver. The same endpoints are reachable locally on the LAN and remotely through the secure tunnel, so dashboards, historians and asset registers can pull data from field devices without any custom protocol work.

v4 was designed from the start around the security-by-design expectations set by the EU Cyber Resilience Act (CRA) and the industrial-automation standard IEC 62443, which is the framework most UK, US and international asset owners specify against. Firmware is signed and installed to a standby A/B partition with automatic rollback on boot failure; remote access is an outbound TLS-only tunnel with no inbound ports; SSH is disabled for interactive login; and every release ships with published notes and a version-pinned update channel. A published vulnerability-disclosure policy and per-release Software Bill of Materials (SBOM) will follow ahead of the September 2026 and December 2027 CRA milestones — giving asset owners a clear path to CRA-compliant procurement and to the equivalent obligations emerging in the UK (Cyber Security and Resilience Bill) and US (federal SBOM / SSDF procurement rules).