Connectors

Connectors are the critical bridge between field devices and the Splight platform. They enable real-time, bidirectional communication by implementing industry-standard protocols to ingest telemetry and issue control commands. Whether you're monitoring a solar inverter, reading from a substation RTU, or sending a curtailment command to a battery controller, connectors are what make it all possible.

What is a Connector?

A Connector is a continuously running program that maintains an active connection to one or more field devices—such as RTUs, PLCs, SCADA systems, or gateways—using a specific communication protocol. It performs two essential functions:

  • Real-time Data Ingestion: Reads live measurements from devices in the field and maps them to Input Attributes of Splight Assets.

  • Command Execution: Sends commands (e.g., “ramp down,” “turn off,” “set point”) to the field when triggered by Splight solutions such as DCM (Dynamic Contingency Management).

How It Works

Each connector implementation supports a specific protocol (e.g., MQTT, DNP3, Modbus), and runs as a long-lived process. It performs the following:

  1. Establishes a connection with a field device using the configured protocol and credentials.

  2. Continuously polls or listens for telemetry from the field (e.g., current, voltage, breaker status).

  3. Maps incoming variables to the correct Input Attributes on one or more Assets, based on a user-defined routine.

  4. Listens for command triggers from Splight (e.g., triggered by a solution like DCM).

  5. Translates commands to the appropriate protocol format and writes them back to the device.

Routines: Mapping Data

Each connector has a routine—a configuration that defines how protocol-specific variables (e.g., Modbus registers or MQTT topics) are mapped to:

  • Input Attributes: Real-time values that update Splight assets.

  • Command Attributes: Outgoing control signals that Splight sends to the field.

This routine defines both the read path (device → Splight) and the write path (Splight → device), making the connector fully bidirectional.

Node Architecture

Connectors run inside Nodes, which are execution environments that host one or more connectors. A node can be:

  • Splight-Hosted: Managed and operated by Splight in a secure cloud environment.

  • Self-Hosted: Deployed and managed by your organization on any machine (e.g., laptop, industrial PC, edge server).

You can manage your organization's nodes from the Settings > Organization > Nodes section in the Splight UI.

💡 Self-hosting a connector allows you to run secure, low-latency integrations directly inside substations, power plants, or data centers.

Supported Protocols

Splight natively supports the following protocols:

  • MQTT

  • DNP3

  • Modbus

  • IEC 61850

  • IEC 104

  • SFTP (for file-based ingestion)

Each protocol is fully integrated into Splight’s asset model and RBAC system, ensuring secure and consistent behavior across all environments.

Custom Connectors

Need support for a proprietary or industry-specific protocol? Splight offers custom connector development for enterprise customers.

To request a custom connector:

Why Connectors Matter

Connectors are a foundational component of Splight’s real-time grid technology. They:

  • Enable telemetry-driven decisions across your platform.

  • Power solutions like real-time contingency management (DCM), simulations, and battery optimization.

  • Make Splight interoperable with your existing field infrastructure—no rip-and-replace required.

By unifying data flow and control across protocols, devices, and assets, connectors unlock the full value of your grid edge data.

How to Create a Connector

⚙️ This section walks you through the process of setting up a connector via the Splight UI.

Step 1: Create a New Connector

  1. Go to Connectors in the left-hand menu.

  2. Click New Connector.

  3. Give your connector a name, description, and select the protocol it will use (e.g., Modbus, MQTT).

Step 2: Configure Inputs & Protocol Details

Configure how the connector will communicate with your field device.

  • Set up the connection settings based on the selected protocol (e.g., IP address, port, credentials, polling rate).

  • Define input attributes to link telemetry from the field to your assets.

Step 3: Define Your Routine

A routine maps each protocol variable to an asset’s input or command attribute.

  • For telemetry, map the incoming field variable to an input attribute (e.g., register 40001 → breaker_status)

  • For control, define how commands are translated into protocol writes (e.g., turn_off → write 0 to address 00002)

Step 4: Deploy the Connector

Decide where the connector will run:

  • Select a Node: Choose between a Splight-hosted or self-hosted node

  • Deploy: Confirm and launch the connector

Once deployed, the connector will begin maintaining a persistent connection with the field device and syncing data with the Splight platform.

Monitoring & Status

After deployment, you can:

  • View live status of the connector

  • Monitor communication errors or timeouts

  • See the last successful read/write

  • Re-deploy or edit configuration as needed

Need Help?

If you encounter issues during setup, reach out to your Implementation Manager or contact [email protected] for help configuring protocols, routines, or nodes.

PreviousFilesNextDynamic Congestion Manager (DCM)

Last updated

Was this helpful?