Simplicity,
elegance, durability.
One all-in-one luminaire: panel, battery, optic and IoT node in a single casting. Talos I covers 20–90 W, Talos II 100–200 W, and both report to the same cloud — no trenching, no cabling, no electricity bill.
One pole,
everything on it.
Talos generates its own power, stores it, and decides what to do with it — no trench, no meter, no grid connection to wait for. Panel, pack, controller and luminaire share one die-cast body, which is what lets it go up on a spigot in an afternoon. Select a part in the viewer to isolate it.
Philips Lumileds, eight optics
210–220 lm/W from one to four LED modules, over 50,000 h, in four colour-temperature bands. The lens is chosen per road rather than per catalogue: eight IES distributions, from a 60×100° throw down a carriageway to a 150° wash over a yard.
02 — The controllerMPPT charge and IoT in one
An MPPT controller tracking above 99.9%, with five-stage dimming, motion mode and — on Controller C — dusk-to-dawn and a time-of-turn-off that works back from sunrise. The IoT node rides the same board and reports what it did.
03 — The supplyPanel and pack in one body
A monocrystalline module at 24% and a LiFePO₄ pack good for more than 4000 cycles, sized together against a six-hour charge. Both are inside the same housing as the light, so there is nothing on the pole to align, cable or steal.
04 — The platformOne console over all of it
Every pole reports to iNET Cloud: dimming schedules and policy out, energy, state of charge and faults back. Dashboards, a live map, alarms pushed as they are raised, and reporting an energy contract can be settled on — from a browser, with no software to install and nothing on site to maintain.
Generation, storage,
light, intelligence.
Four subsystems and a sensor set, all inside one housing. The figures here are common to Talos I and Talos II; where they are sized per model — panel wattage, pack capacity — the model table under Specification carries the per-part numbers.
Monocrystalline, multi-busbar
Multi-busbar monocrystalline cells at 23% conversion, 24% at module level, with output held to ±3%. PID-resistant and tested to IEC 62804, rated to 2400 Pa wind and 5400 Pa snow, and warranted 10 years on materials against a 25-year linear output curve — longer than the pole is usually specified for.
LiFePO₄, Grade A+ cells
More than 4000 cycles, with two cell grades: standard cells charge from 0 °C, and advanced cells charge down to −20 °C for winter sites where a standard pack would simply refuse. Both discharge across the full −20…60 °C range. Capacity is measured, not estimated — see the coulometer below — and maintenance is guaranteed for 10 years.
Up to 220 lm/W, IK08
Philips Lumileds in one to four modules, over 50,000 h, CRI 70 nominal, in four CCT bands from 2500–3500 K to 5500–6500 K. Eight IES distributions cover the roads a solar light actually gets specified for. IP66 and IK08 in RAL9005, on a slip fitter with a 0°–90° adjustable spigot.
The controller is the node
The charge controller and the IoT radio are the same device, so what the light decides and what the platform sees cannot drift apart. IP67 with 3000 V TVS surge protection. Work mode, dimming profile and thresholds are all set remotely; a pole with no signal falls back on its own programme rather than on darkness.
What the pole knows about itself
Dusk to dawn
The panel is the sensor: the controller switches on the falling panel voltage against a programmable 3.0–8.0 V threshold, with a 0–30 minute delay so passing cloud does not cycle the light.
Two power levels
In motion mode the light holds 100/60/30/70% while something is moving and drops to 30/20/10/20% when nothing is — the saving that buys the small hours without leaving a street dark.
Measured, not modelled
A high-precision coulometer reports voltage, current, power, real capacity and time remaining. A pack that is ageing shows up as a falling capacity years before it shows up as a dark pole.
Permanently powered GPS
A mini tracker on its own supply, hidden in a part of the fixture an installer cannot reach, followed live from the app. It is there for the poles that leave site on the back of somebody's truck.
Gyroscope and accelerometer
The installed angle is locked at commissioning. A knock, a lean or an attempt to unbolt the head raises an alarm at the operation centre and sends an SMS from the management system.
0 °C charge protection
Lithium is not charged below freezing. The controller holds charge off until the pack is warm enough to take it, which is the single thing that most shortens a solar light's life in a cold climate.
One console
for the whole estate.
A cloud central management system for provisioning, monitoring, controlling and analysing lighting. Multi-tenant, reached from a browser on a laptop, tablet or phone, and scaling to thousands of locations under a single interface.
A lit street, in real time.
Three poles on one kerb of a four-lane carriageway, spaced at 3.5× mounting height so the throws cross and the road lights evenly. Take one light or all three, dim them, switch them — or leave the photocell to it and watch a whole day pass in seventy-five seconds.
A working simulation of the live iNET Cloud console — every rail item, filter, dropdown, toolbar icon, page control, row action and top-bar control responds, opens and closes as it does in the real thing. Nothing writes: commands end in a notice saying so, and every identifier, coordinate, reading and credential on screen is synthetic. Hover a control for a hint; each screen explains itself on arrival. Map data © OpenStreetMap contributors, ODbL.
Every pole, on the map
Create, import and edit device attributes — pole coordinates and type, fixture wattage before and after retrofit, lamp type. iNET performs GIS to GPS matching to correlate pole IDs with the devices on them, so nobody records device IDs during installation.
Map and floor plan
A map-based interface for status, health and overrides, extended to floor plans for indoor structures such as parking garages. Faulty devices are located from the same view that reported them.
Groups and priority
Assets group logically for event scheduling, and a group can hold several schedules at once — regular and special events kept apart, with the engine resolving the day from event priority rather than from the operator remembering.
Collected several times a day
Light level, energy use and faults, with per-point monitoring levels for voltage, current and power factor when a circuit needs investigating.
Failure finds you
Built-in alarms per asset class, configurable to e-mail and SMS. The system watches for lamp failure, night outages and day burners, and the logs export as CSV.
Asset, selection or city
Energy reports compare performance across lighting assets; data logs trend light level, wattage and schedules over a period. Everything exports to CSV or PDF.
Every interface to iNET uses SSL with AES encryption. Access is role-based and can be restricted at different levels of a geozone hierarchy, password policy follows industrial standards, and a timeout after repeated failed logins closes the obvious attack.
Multi-tenant and built on current web technology, so it ports across platforms and web interfaces. Supported on Chrome, Firefox and Edge.
Every node
relays for its neighbours.
The gateway talks to the server over cellular or ethernet, and to the nodes over SUB-1GHz radio. Between the nodes it is a mesh: any node can act as a repeater, so an instruction from the server reaches a light that cannot hear the gateway directly.
SUB-1GHz, ten channels
IEEE 802.15.4 on ISM 315 / 433 / 490 / 868 / 915 / 928 MHz, 10-channel direct sequence spread spectrum at +22 dBm from the node and +24 dBm from the gateway. Node to node and node to gateway both reach 1 km line of sight.
Wired or wireless
Where there is structured cabling the gateway takes a 10/100 ethernet link through a router. Where there is not, it uses a built-in 4G modem on any carrier. The nodes below it are unaffected either way.
300 nodes, 2000 m across
One gateway carries up to 300 controllers out to 1000 m line of sight, and the mesh between them spans a network up to 2000 m in diameter. Beyond that, add a gateway rather than a trench.
A gateway.
A node per light.
Two devices carry the whole system. The gateway is the bridge to the server; the node is the part that actually holds a luminaire's behaviour, and there is one in every fixture.
The bridge to the server
Connects the field controllers to the management system through an ethernet link for LAN, or a 4G link through an integrated cellular modem. Star-mesh repeater topology, wall or pole mounted, with a built-in lightning surge arrester on every antenna port and a 5-year limited warranty.
Two ways to fit it
Standard installs inside the fixture, normally in the drive box — the choice for new luminaires and for retrofits where the housing opens. NEMA fits the NEMA 7-pin socket on top of a street light or area fixture, with an onboard photocell, and needs no one inside the housing at all.
Talos I
and Talos II.
From the Talos I and Talos II product specifications. Panel and battery are sized on 6 hours of charging. Values marked TBC are not stated in the brochures and are pending confirmation against the production build. The table follows the series selected in the hero.