Enapter Link

Enapter Link is a wired bus for connecting hardware UCMs together and to the Enapter Gateway, enabling centralized management, monitoring, and Lua-based control logic for all connected devices. It provides a fully wired alternative to wireless connectivity for installations where Wi-Fi is not suitable or preferred.

Physical Connection

At least one UCM of the ENP-RS-CAN-USB M2 type is required to use Enapter Link. It serves as the LINK Master: it connects to the Gateway via its built-in USB-C connector, and to other UCMs via the two-wire Enapter Link bus using the BL and WH pins.

For wiring details, refer to the datasheet of your UCM at handbook.enapter.com/modules.

Setup and Device Registration

Navigating to Enapter Link Settings

On the Gateway home page, open Settings → Enapter Link.

When all bus modules are connected and powered, this section shows the LINK Master (ENP-RS-CAN-USB M2) entry and the current bus status.

Enapter Link Bus Status

Discovering and Provisioning Devices

To find UCMs connected to the bus, click Run Device Discovery. Once discovery completes:

• Click Provision All to register all discovered devices at once, or
• Click Provision next to a specific device to register it individually.

All provisioned devices receive the provisioned status and become available for management, monitoring, firmware updates, and Lua control logic.

Discovered and Provisioned UCM (ENP-RL6 Example)

Managing Enapter Link Devices

After provisioning, all Enapter Link devices appear under the Communication tab in Energy Management System on the Gateway main page.

Communication Devices Including Hardware and Virtual UCMs

To integrate a third-party device that a UCM controls, click → Another Device and select the UCM physically connected to your device as the runtime. The UCM runs the Lua script that implements communication with the third-party device and exposes its data and controls to the Gateway.

Some UCMs — such as ENP-RL6 — expose executive interfaces like relay outputs and can act as endpoint devices directly, without requiring a separate third-party device entry. Devices that provide only digital bus interfaces, such as ENP-CAN, usually cannot act as endpoint devices directly and are instead used as communication bridges to external devices. However, this is not a strict rule — the role of any UCM ultimately depends on its Lua script, and even a bus-interface device may be configured as a passive endpoint that exposes only a virtual register map.

Uploaded Blueprint Example

Ready-to-use blueprints from the Enapter Marketplace are available to simplify integration. For example, the Generic IO for ENP-RL6 blueprint provides relay control with no additional logic required. After loading a blueprint, the device's Commands and Telemetry tabs display the available controls and monitoring parameters for the device dashboard.