TOP BAR

About

About

We will continue to build sustainable AI-driven infrastructure.

Cases
LEOTEK cases around the world!

Sustainability
LEOTEK's Sustainable Actions.

Newsroom
Latest news, exhibition events, award information.

Careers
Welcome talents to join us!

LEOLab

Integration of sustainable innovation technologies and products.

ComfortView™

Human Centric Lighting

ECOridge™

Ecological Lighting.

Interlux™

AI Traffic Signal.

RenAI™

AI Road Asset Management System.
Products
Product Type
Outdoor Lighting
Street Lighting

Off Roadway

Site & Area

Flood Lighting

Architectural & Decorative
Traffic Signal
Ball Signal

Arrow Signal

Vehicle Traffic Signal
Pedestrian Signal
Pedestrian Signal
Railroad Signal
Railroad Signal
AI Infrastructure
ILS Solutions

Smart Node (Hardware)

AI Platforms (Saas)
Energy Infrastructure
EV Charger
Solutions

LEOLink ILS™
Smart Lighting Control solution with LEOLink smart node & RenAI platforms

Interlux™
Intelligence intersection management
Resources

Blog
Smart Mobility Insights

Documents
Outdoor & Signal Lighting Library

Agent Portal

Agent User Guide
Contact

Purchases & Inquiries

Agents & Channels
(Under Construction now)

LEOLink

Compare LEOLink NB01-Plus and embedded EB01 smart lighting controllers. Review model specifications and documents, then explore LEOLink and RenAI.

Showing all 2 results

LEOTEK Electronics U.S.A. Corporation

LEOTEK, with headquarters in Silicon Valley and Taipei, is a global leader in smart traffic signals and roadway lighting. Since 1992, we’ve advanced safety and sustainability with AI- and IoT-powered solutions that drive urban decarbonization and smarter, greener cities.

Company

Resources

LEOLAB

Our Locations

Silicon Valley HQ

Regions Served

PROJECT SUPPORT

LEOLink FAQs

Answers to common questions about product selection, installation and procurement.

Should we choose external NB01-Plus or embedded EB01?

NB01-Plus mounts at an ANSI C136.41 seven-pin receptacle and uses a 0–10V dimming interface. EB01 is installed inside an approved factory luminaire configuration and uses DALI D4i. The LEOLink data sheet lists 110–277V for NB01-Plus and 110–480V for EB01, but the selected fixture’s ordering restrictions also apply—for example, KC1 D4i options are MV only. Hardware voltage capability does not override the luminaire configuration.

LEOLink node selection comparison
Selection item	NB01-Plus / EB01
Installation	NB01-Plus: external ANSI C136.41 seven-pin mounting. EB01: embedded in an approved factory luminaire configuration.
Dimming interface	NB01-Plus: 0–10V. EB01: DALI D4i. Match the ordered driver and wiring to the node.
Node supply rating	NB01-Plus: 110–277V. EB01: 110–480V. These hardware ratings do not override restrictions in the selected luminaire order table.
KC1 example	Its D4i/EB01 route requires MV 120–277V and excludes PS. Verify other luminaire families against their own sheets.
Pilot record	Retain luminaire code, driver, node model, firmware, supply, CMS/data term and the measured response to commanded dimming.

Specifications & documents
LeoLink Data Sheet 09.15.2025 · KC1-Spec-Sheet

Further reading
Streetlight CMS Architecture: Nodes, Networks and Central Management

Can NB01-Plus be added to another manufacturer’s fixture?

The external node is a retrofit candidate where the fixture provides a compatible, correctly wired ANSI seven-pin receptacle and 0–10V driver within the node’s approved voltage range. A physically matching socket alone is insufficient: verify power pins, dimming connections, driver response and node operation. EB01 is the factory-embedded route, not a universal field retrofit for other manufacturers’ fixtures.

Specifications & documents
LeoLink Data Sheet 09.15.2025

Further reading
Streetlight CMS Architecture: Nodes, Networks and Central Management

Does the controller’s backup power keep the streetlight illuminated?

No. The data sheet describes supercapacitor backup of at least 15 seconds for the controller. It is not a battery-backed luminaire or a promise that the LED engine stays on during a power outage. Keep streetlight backup power, if required, as a separate electrical-system scope. The public sheet also does not define a guaranteed offline schedule or reconnection sequence; those requirements belong in a verified pilot acceptance plan.

Specifications & documents
LeoLink Data Sheet 09.15.2025

Further reading
Streetlight CMS Architecture: Nodes, Networks and Central Management

How do the nodes communicate with RenAI?

The published LEOLink architecture uses NB-IoT/CAT-M1 cellular connectivity and MQTT with TLS 1.3. The deployment therefore needs a compatible cellular service and the selected RenAI CMS subscription. Confirm coverage at actual poles, including obstructed and edge-of-coverage locations. A successful node installation at one pole does not establish reliable communications across the entire city.

Specifications & documents
LeoLink Data Sheet 09.15.2025 · KC1-Spec-Sheet

Further reading
Streetlight CMS Architecture: Nodes, Networks and Central Management

What operating data can a smart-lighting project evaluate?

The data sheet identifies energy metering, GPS, tilt sensing and light sensing among the LEOLink capabilities, with an energy-metering accuracy claim of 0.5%. Use a pilot to compare reported energy against a suitable reference and to check location/tilt and fault events on the ordered hardware. These hardware capabilities do not themselves define municipal data ownership, export rights or a particular GIS integration contract.

Specifications & documents
LeoLink Data Sheet 09.15.2025

Further reading
Streetlight CMS Architecture: Nodes, Networks and Central Management

What costs belong in the LEOLink deployment budget?

Budget the compatible luminaire configuration, controller, installation, commissioning and ongoing CMS/data services separately. Current KC1 ordering uses RXX RenAI and DXX data-plan terms of 1, 5 or 10 years; R00/D00 needs prior LEOTEK approval. Match the service term to the operating budget and specify renewal/support responsibilities. A control-ready fixture or purchased node should not be treated as a perpetual software-and-connectivity entitlement.

Specifications & documents
KC1-Spec-Sheet

Further reading
Streetlight CMS Architecture: Nodes, Networks and Central Management

Can the PS field selector and an EB01 D4i configuration be combined?

On current KC1, PS is intended for the standard 0–10V driver and is not compatible with DALI D4i. EB01 requires D4i, while NB01-Plus uses the external seven-pin/0–10V route. If local field adjustment is required, select the supported architecture first. Combining every individually available control option can produce an invalid order rather than a more flexible system.

Specifications & documents
KC1-Spec-Sheet

Further reading
Streetlight CMS Architecture: Nodes, Networks and Central Management

Does a ten-year luminaire warranty also cover every controller and service?

No. Current ordering distinguishes NB01P05’s five-year controller coverage from NB01P10 and EB01P10’s ten-year controller options. Luminaire, optional sensor and controller terms must be identified separately. CMS subscriptions and cellular data are service terms, not a luminaire warranty. The submittal should show the selected hardware coverage and service duration instead of applying the fixture’s warranty headline to the whole deployment.

Specifications & documents
KC1-Spec-Sheet · Leotek General Illumination Products Warranty North America

What should a pilot prove before citywide rollout?

Test the exact node/driver/voltage combinations proposed for the fleet. Verify commanded dimming and measured fixture response, cellular coverage, mapped asset identity, energy reporting and representative fault alerts. Separately test power loss, communications loss and recovery against a written acceptance requirement; the public data sheet does not fully define those behaviors. Record hardware, firmware and service configuration so rollout units match what passed the pilot.

Specifications & documents
LeoLink Data Sheet 09.15.2025 · KC1-Spec-Sheet

Further reading
Streetlight CMS Architecture: Nodes, Networks and Central Management

Selection & project planning

Plan connected lighting as a complete operating system: luminaire, controller, communications, management software and support. Define the city’s operating requirements first, then compare hardware configurations and validate the complete solution in a representative pilot.

Compare external and embedded controllers

NB01-Plus is the external controller option, using a NEMA seven-pin interface for compatible fixtures. EB01 is an embedded option for selected luminaires. Confirm driver and control-interface compatibility, supply conditions and the exact luminaire configuration. The published LEOLink architecture includes cellular communications and the RenAI management platform; availability and service scope should be confirmed for the project.

Define the operating workflow

List the required schedules, dimming levels, exception handling, outage reporting and asset information. Agree on who receives alerts, how issues become work orders and what information maintenance crews need. Define user roles, access responsibilities and acceptance criteria before commissioning so software functions support the agency’s daily operations.

Validate connectivity and resilience

Pilot representative streets, fixture types and coverage conditions. Test commissioning, commands, status reporting and recovery after communications interruptions. Specify the expected local behavior during an outage and verify it on the selected hardware and service configuration. Include a practical process for failed devices, controller replacement and asset-record updates.

Specify integration and data requirements

Identify existing GIS, asset-management and work-order systems and the information each needs. Request confirmation of supported interfaces, export formats, permissions, frequency, costs and version responsibilities. If multi-vendor equipment is required, name the hardware and software combinations and test them. A standards reference alone does not establish interoperability with every third-party system.

Compare the complete ownership cost

Separate controller hardware, installation, commissioning, communications, software subscriptions, integrations, training, support and replacement costs. Define contract duration, renewal assumptions and service responsibilities. Request written terms for data ownership, retention, export and transition at the end of the agreement so the city can evaluate both operating costs and future migration requirements.

LEOLink architecture and RenAI overview LEOLink hardware models LEOLink data sheet Discuss a pilot or deployment scope

Pixelated & Incandescent Look Available

Pixelated & Incandescent Look Available

LEOLink EB01 (Embedded)

LEOLink NB01-Plus