Adding a Device

Common SEMS workflow for creating a smart meter, inverter, hybrid inverter, battery or EV charger connection.

Purpose

This guide explains the common SEMS device-creation workflow that the current UI exposes for meters, inverters, hybrid inverters, batteries and EV chargers.

CyberSun SEMS device onboarding flow
Common onboarding logic: select device type, choose the correct profile, define TCP or RS485 parameters, then validate polling and live values.
CyberSun SEMS device management page
Current Devices page: configured devices, profile assignments and edit/debug entry points.

Current device form fields

The current inspected device-management UI exposes the following verified field groups:

  • Device name
  • Device type
  • Profile
  • Connection
  • Channel / TCP endpoint
  • TCP host and TCP port
  • Unit ID
  • RS485 parameters such as baud rate, parity, stop bits and byte size
  • Polling enable and polling interval

Public documentation can therefore refer to these fields directly.

General procedure

  1. Open the Devices page.
  2. Select Create device.
  3. Enter a meaningful device name.
  4. Select the correct device type.
  5. Select the reviewed device profile.
  6. Choose the transport:
    • Modbus TCP for IP devices
    • serial / RS485 for RTU devices
  7. Enter the communication parameters:
    • host and TCP port for network devices
    • channel/port and serial settings for RS485 devices
    • unit ID / slave ID where required
  8. Save the device.
  9. Poll or refresh the device list and verify live communication.

Modbus TCP vs Modbus RTU

Modbus TCP

Use when the device is reachable by IP address and port.

Typical required inputs:

  • host
  • TCP port
  • unit ID where the vendor requires it

Modbus RTU / RS485

Use when the device is on a serial bus.

Typical required inputs:

  • serial channel or RS485 port
  • baud rate
  • parity
  • stop bits
  • unit ID

Validation after saving

After creating the device:

  • confirm that polling does not immediately fail;
  • confirm the device status becomes live/healthy;
  • verify at least one expected measurement against the device itself;
  • continue with the device-specific commissioning guide where available.

Discovery boundary

The current product includes bounded, read-only discovery support in the setup flow. Public documentation must keep the current boundary explicit: discovery does not automatically enable or activate control by itself.

Was this helpful?

Did this article answer your question?