Ilumen charging stations

Supported Devices

Device Type	Variants	Modbus TCP (Ethernet)	RS485
Ilumen	/	✅	❌

Wiring

Ethernet

For communication with Eniris (Modbus TCP) the Ilumen charging station must be connected to a local IP network.

• The charger must have a fixed/static IP address (recommended) or a DHCP reservation.
• The Eniris gateway must be able to reach the charger's IP address on TCP port 502.
• Use standard Ethernet cabling and switches; follow the general Ethernet wiring guidelines.

warning

Port 502 (Modbus TCP) is commonly used across the network. Ensure firewall rules allow TCP traffic between the Eniris gateway and the charger's IP on port 502. Do NOT expose port 502 to the public internet.

RS485

Ilumen devices supported by this driver communicate over Modbus TCP only. RS485/Modbus RTU is not supported by the Ilumen driver described here.

RS485 Wiring

• For correct RS485 wiring: Follow the guidelines for RS485 wiring.
• If the wiring shown in the table below is incorrect, please let us know.
• There is no general consensus in the industry about the usage of A and B for the RS485 polarity, so it may be counterintuitive and opposite of what you might expect for some devices.

Device	Sofar EMS model OM1	Sofar EMS model IG8	RS485-USB converter	RS485-Ethernet converter
Not applicable	RS485 A	RS485_POS	RS485 A	TX+
Not applicable	RS485 B	RS485_NEG	RS485 B	TX-
Not applicable	RS GND	GND	Not available	G

Configuration

Follow these steps to enable Modbus TCP communication between an Ilumen charging station and the Eniris gateway. The steps assume the charger is already powered and reachable on the local network.

1. Access the charge station network configuration:

   • Use the Ilumen configuration UI (web interface) or the vendor-provided configuration tool.
   • If the charger uses DHCP by default, set a static IP or reserve an IP in your DHCP server for the charger.

2. Network settings:

   • Set IP address within the same subnet as the Eniris gateway (for example: 192.168.1.50).
   • Set subnet mask and gateway consistent with your local network.
   • DNS is optional for Modbus TCP but may be required for firmware updates or vendor tools.

3. Modbus TCP server settings:

   • Enable Modbus communication and select "Modbus TCP/IP" as the communication mode.
   • Set the server port to 502 (the Eniris Modbus driver expects port 502).
   • Confirm the Modbus unit/slave ID (also called Device ID). Typical range: 1–247. Note this ID is required by the Eniris Modbus driver configuration.

tip

The Ilumen driver in Eniris expects Modbus slave IDs in the 1–247 range. Use a unique ID on the network to avoid collisions with other Modbus/TCP devices.

4. Ensure the device is reachable:

   • From the Eniris gateway, verify TCP connectivity: e.g., use telnet 502 or an equivalent network test.
   • If connectivity fails, check switch/router VLANs, firewall rules, and physical cabling.

5. Configure the Eniris gateway:

   • In Eniris device configuration, create a device entry with:
     • Protocol: "Ilumen EV Charger protocol V1"
     • Connection mode: Modbus TCP
     • IP address: the charger's static IP (or DNS name)
     • Port: 502
     • Modbus slave/unit ID: the configured Device ID on the charger
   • Optionally provide serial number and model in the driver parameters to help device identification.

6. Match communication parameters:

   • Modbus TCP: no serial line parameters required (baud/parity/stopbits do not apply).
   • Ensure the Eniris gateway's Modbus client is configured to use Modbus TCP framing.

7. Discovery and verification:

   • After adding the device in Eniris, run a device scan/discovery.
   • The driver validates the device by reading specific registers (e.g., voltage measurement registers). Successful reads confirm the charger is online.
   • In Eniris logs you should see the charger appear with a nodeId like: SGW-Ilumen-EVC-.