by Clear-Vu Lighting clearNET · 900 MHz wireless mesh · built for tunnels · NYCT spec 16ES

clearNET. We set it up once. After that, it runs itself.

A 900 MHz self-healing wireless mesh carried on the fixture itself. Every MTLx is a node and a repeater; the gateway sits at the station platform, so there is no cabling in the bore. Light levels, Work Mode, NFPA 130 self-tests and fault reports run on schedule and arrive in your inbox. In NYCT revenue service since 2018.

BABA / BAA compliant Made in Central Islip, NY Standard on MTLx Pro · CN1 on MTLx OG AES-encrypted · OT/IT segmented
clearNET tunnel map dashboard showing a live fixture-by-fixture schematic with healthy, Work Mode, warning and critical states Tunnel map · live fixture schematic
2018
In NYCT revenue service
900MHz
Licence-free · outside 2.4 GHz CBTC
3,000ft
Node-to-node hop demonstrated
5,000+
Fixtures deployed
01 · How it works · in revenue service since 2018

One gateway at the platform. Every fixture is the network.

clearNET is a 900 MHz self-healing wireless mesh built for one environment: the inside of a tunnel. Not a building protocol asked to survive underground — a radio designed for concrete, steel, curvature and moving trains, carried on the fixture itself. In NYCT revenue service since 2018 and tuned to NYCT specification 16ES.

01 · How it gets deployed

We commission it

Clear-Vu provisions every fixture, verifies node-to-node margin and hands over a mesh that is already reporting. No agency IT project.

02

It heals itself

Nodes discover their own neighbours and re-route around a failed or removed fixture. Adding fixtures extends the mesh; nothing is re-planned.

03

You get autopilot

Light levels, Work Mode windows, NFPA 130 self-tests and fault reporting run on schedule. The agency is notified, not asked to go looking.

900 MHz
Licence-free band · outside 2.4 GHz CBTC
3,000 ft
Node-to-node reach
5,000+
Fixtures deployed
clearNET tunnel map dashboard showing a live fixture-by-fixture schematic with healthy, Work Mode, warning and critical states
Operating surface 1 · dashboard

Reports come to your inbox.

Two surfaces, and an agency only needs one of them. The dashboard is there when someone wants to look; everything that matters arrives on its own. Scheduled reports export daily, weekly or monthly, with a master-admin audit log of every control action.

Tunnel map · live schematicHealthyWork ModeWarningCritical
Track worker touching a magnet wand to the underside of an MTLx fixture from the tunnel walkway to trigger Work Mode
Operating surface 2 · magnet wand

Work Mode comes off a magnet.

A crew touches a magnet wand to the underside of any fixture from the walkway. clearNET propagates Work Mode across the entire tunnel segment for eight hours, then reverts every fixture to NFPA 130 egress on its own. No app, no login, no dispatcher, no site visit to turn it back off.

One touchWhole segmentEight hoursAuto-revert
Integration hooks

Read-only and control endpoints for SCADA, BMS and EAM platforms, so lighting state and fault data land in the systems an agency already watches.

Fixture mesh · 900 MHz→Gateway→SCADA · stateBMS · schedulesEAM · faultsAPI / BACnet

Frequency separation from CBTC

900 MHz operation sits outside the 2.4 GHz band used by most U.S. CBTC deployments. Across five-plus years and 3,000+ monitored fixtures, no CBTC interference incident attributable to the system has been identified by the host agencies.

Encrypted, segmented

AES-encrypted mesh traffic with OT/IT segmentation at the gateway — a defense-in-depth posture mapped to TSA SD 1582-21-01, IEC 62443 and NIST SP 800-82r3.

A floor no command can cross

The command dictionary contains no wireless instruction whose minimum legal argument falls below the NFPA 130 egress floor. Out-of-range commands are rejected at the firmware parser and logged. The worst attainable wireless attack is brighter light.

Linear-topology engineering

Tunnels behave as lossy waveguides with 21–32 dB train shadowing. Sub-GHz propagation and 1:1 fixture-to-node density keep margin through curves, crossovers and passing trains.

Get the wireless mesh whitepaper
Specifications · radio · topology · functions · integration

What the mesh is, in the language of a spec.

Values below are drawn from the 2026 MTLx family brochure and the Wireless Mesh Networks in Subway Tunnel Environments whitepaper. Project-specific radio surveys, node counts and gateway placement are confirmed by Clear-Vu engineering during commissioning.

Radio & topologyclearNET
Band900 MHz licence-free (902–928 MHz ISM, FCC Part 15.247)
Separation from signallingSub-GHz — outside the 2.4 GHz band used by most U.S. CBTC deployments
TopologySelf-healing linear “string-of-pearls” mesh; every fixture is a node and a repeater
Node density1:1 fixture-to-node
Node-to-node reachUp to ~3,000 ft demonstrated in straight bore; typical fixture spacing 15–30 ft
GatewayOne gateway at the station platform, outside the bore — no in-tunnel control cabling
BackhaulAgency network at the gateway; cellular backhaul supported (Amtrak Hudson River Line)
HealingNodes discover neighbours and re-route around a failed or removed fixture; adding fixtures extends the mesh
Node locationIntegrated in the MTLx end-can; sealed quick-connect to the housing
AvailabilityStandard on MTLx Pro (TL4064P) · option CN1 on MTLx OG (TL4064) · not offered on MTLx Mini
Functions, integration & securityclearNET
Light controlPer-fixture, per-zone or per-tunnel light level; presets from the 6 W NFPA 130 baseline through 1 fc and 2 fc settings
Work ModeMagnet-wand trigger from the walkway; propagates across the segment; eight-hour timed cycle, auto-revert to egress
MonitoringFixture, driver, battery and thermal status; optional ambient temperature sensor (HS1)
NFPA 130Scheduled battery self-tests and emergency-lighting status reporting
ReportingScheduled exports daily, weekly or monthly; master-admin audit log of every control action
DashboardTunnel map with live fixture-by-fixture states: healthy, Work Mode, warning, critical
IntegrationRead-only and control endpoints for SCADA, BMS and EAM platforms; API / BACnet
SecurityAES-encrypted mesh traffic; OT/IT segmentation at the gateway; posture mapped to TSA SD 1582-21-01, IEC 62443 and NIST SP 800-82r3
Egress floorNo wireless command can set output below the NFPA 130 egress floor; out-of-range commands are rejected at the firmware parser and logged
Specification & originNYCT spec 16ES · BABA / BAA compliant · Made in Central Islip, NY

Fixture power figures published for MTLx (6 / 10 / 16 / 60 W) include the clearNET node. Commissioning: Clear-Vu provisions every fixture, verifies node-to-node margin and hands over a mesh that is already reporting — no agency IT project.

Where clearNET runs underground

In revenue service with MTA New York City Transit and Amtrak, and field-tested on the London Underground.

MTA/NYCT Rutgers Tunnel — MTLx tunnel light with clearNET wireless monitoring installed on the under-river tunnel wall
MTA/NYCT Rutgers Tunnel
~700 MTLx fixtures · 700 mesh nodes · 2021
Amtrak Hudson River rail tunnel — historic under-river tube with modern LED tunnel lighting and wireless monitoring
Amtrak Hudson River Tunnel
~1,100 MTLx · clearNET on cellular backhaul
London Underground tube environment where clearNET wireless mesh was field-tested
London Underground
Transport for London · clearNET field test — no active installation
Downloads

The brochure, the whitepaper and the fixture it rides on.

The whitepaper benchmarks nine wireless protocols for tunnel use and documents the 900 MHz field results. Design and configuration guides are issued per project by Clear-Vu engineering.

Ready to Specify clearNET?

Our controls engineering team provides network design layouts, node placement recommendations, and integration specifications for your project.