Tunnel Lighting Monitoring

The problem

Tunnel entrance lighting runs at full stages regardless of outside luminance, wasting energy, and failed circuits are found only on night inspections.

Solution overview

MILESGO gateways collect data from lighting control panels, luminance meters, electricity meters, run/stop and fault dry contacts over Modbus RTU / Modbus TCP / DyNet, and deliver it to SCADA, the energy management system, SMS, email and messaging alarms as OPC UA / MQTT / Modbus TCP. Field equipment keeps its own protocol and control logic; integration is done by configuration and point mapping, not custom code.

Typical scope

lighting control panels
luminance meters
electricity meters
run/stop and fault dry contacts

Protocol path

Modbus RTU / Modbus TCP / DyNet → OPC UA / MQTT / Modbus TCP

Implementation checklist for the project manager

Write the control sequence (start/stop order, interlocks, set-points, fallback on communication loss) and have it approved before programming.
For hard-wired signals, list each DI/DO/AI/AO with its type (dry contact, 4–20 mA, 0–10 V, PT1000) and choose I/O modules accordingly.
Commission in read-only mode first; enable write / control points only after the client approves each one.
Record CT ratios, meter IDs and multipliers in the point table; wrong multipliers are the usual cause of billing errors.
Define an alarm matrix (priority, recipient, escalation) and test every alarm end to end at SAT.
Hand over configuration backups, point table, IP plan and as-built drawings, with a short operator training.

Project deliverables

Signed point table and protocol mapping
Gateway configuration files and backups
IP address plan and network drawing
FAT and SAT test records
As-built documentation and operator training

System architecture

Field layer: lighting control panels, luminance meters, electricity meters, run/stop and fault dry contacts, connected over Modbus RTU / Modbus TCP / DyNet. Edge and integration layer: MILESGO protocol gateways and edge controllers, mounted on DIN rail in existing panels, polling each device, time-stamping values and buffering them locally. Upper layer: SCADA, the energy management system, SMS, email and messaging alarms, which receives the data as OPC UA / MQTT / Modbus TCP. Remote access for maintenance runs over VPN rather than open internet ports.

System composition

Field devices: lighting control panels, luminance meters, electricity meters, run/stop and fault dry contacts
Edge / integration: MILESGO protocol gateways and edge controllers
Upper systems: SCADA, the energy management system, SMS, email and messaging alarms (OPC UA / MQTT / Modbus TCP)
Tools and commissioning: Web-based configuration, point table import/export (Excel), off-site simulation and on-site diagnostic tools

Software and AI capabilities

Consumption baseline and deviation alertsRoadmap

Delivery steps

1
Site survey and point list
Inventory devices, protocols, register maps, panel space, power and network paths.
2
Design and point table sign-off
Map every point to the target protocol and system; agree it with the client and the upper-system contractor.
3
Configuration and FAT
Build the gateway configuration off site, simulate it and test against the signed point table.
4
Installation and wiring
Mount gateways on DIN rail, wire RS-485 / I/O / Ethernet, apply the IP plan.
5
SAT and alarm tests
Verify values against local readings, test every alarm and command end to end.
6
Handover and support
Hand over configuration backups, point table and as-built documents; train operators.

Customer value

Consumption visible by area, system and time period
Alarms reach the right person by SMS, email or messaging apps
Reliable trend data for optimisation and fault diagnosis
Open interfaces (BACnet, Modbus, OPC UA, MQTT, HTTP) avoid lock-in to one vendor

Tell us about your project

Send the protocols, point count and target system. A sales and engineering pair reviews every submission.

Discuss Your Project