CW Edge Computing Gateway
Aggregates lighting circuit data and connects project-confirmed third-party interfaces
Tunnel and road lighting should first establish a register by lighting circuit, section and operating mode. CW then aggregates consumption and status, and CC100, I/O and HMI can serve as candidates for local control. Traffic, illuminance and environmental data usually come from third-party systems. Control strategies must meet lighting safety and traffic operation requirements and be validated in a small, reversible pilot; an energy saving figure cannot be committed on the basis of a product combination alone.
The solution is positioned as zoned lighting monitoring and a controlled optimization pilot. It protects lighting function and safety boundaries first, then evaluates changes in energy use.
Aggregates lighting circuit data and connects project-confirmed third-party interfaces
Candidate local controller; logic and I/O capability are validated by model and program
Expansion modules selected for lighting status, analog or environmental interface requirements
Configured where local operation, status display or maintenance mode is required
Builds zoned energy, operating strategy, alarm and pilot records
Candidate for on-site data aggregation and edge processing
Lighting circuit status and energy data, together with third-party traffic, illuminance or environmental data, form the inputs.
CC100 with I/O can execute local strategies within the pilot scope, retaining manual and fallback modes.
FEXLINK records zoned data, strategy versions and test results.
M&E staff review operating status and evaluate lighting and energy use changes.
Lighting circuit status and energy data, together with third-party traffic, illuminance…
CW Edge Computing Gateway · CC100 PLC Local Controller
Lighting sections, circuits, controlled objects and operating modes correspond one-to-one
The solution does not commit to a fixed energy saving rate or automatic adaptation to every tunnel scenario
It requires reliable traffic and environmental data, a dimming-capable interface and a safety strategy, and must be validated in a pilot.
The I/O, relay or communication method and the lighting circuit design must be confirmed. It cannot be judged from the PLC name alone.
Follow the project lighting standards and emergency requirements, set minimum lighting, manual and fallback modes, and confirm them through site inspection.
No uniform figure can be committed. It depends on luminaires, traffic, climate, control strategy and reference period, and must be measured.
It depends on whether existing traffic, illuminance and environmental data is available. Third-party interfaces must be verified first.
Share the application, circuit conditions and existing system interfaces so engineers can confirm selection and implementation boundaries.
Contact FEXLINK