RoadOne

How it fits together

RoadOne, part by part

Scroll or tap a part. Press “See the 3D CAD design” to watch the model, built from our CAD, light each part up and show how it connects.

See the 3D CAD designShow the concept

Real-time 3D render · drag to rotate · final design may varySwipe sideways to rotate

1. 01

   The whole RoadOne

   The crossing's own near-side signal head runs the crossing's detection: an approach camera behind the door's bottom road-side corner watches the vehicles coming, a crossing camera in the road-side wall sees the stop line and the whole crossing, a kerb radar in the back wall finds people waiting and stepping off, clamps on the head's own lamp feeds tell the brain which phase is showing, and the brain on the head floor turns that into walk demand, crossing extension, vehicle demand, counts, speed, red-light, near-miss, blocked-crossing and fault calls, placed on the controller's own detector inputs and sent to one app over LTE-M.

2. 02Brain

   Raspberry Pi 5 (on the signal head floor)

   The brain: it runs the roadone-fw program

3. 

   03

   Approach and crossing cameras

   The approach camera behind a window in the door's solid bottom road-side corner (below the green module), 25 degrees down the approach, sees every vehicle and cyclist coming (demand, queue, counts, class, speed); the crossing camera in the road-side wall sees the stop line and the whole crossing (red-light running, people still crossing, near misses, a blocked crossing)

   Raspberry Pi 5 (on the signal head floor) · CSI-2 ribbons (both on the Pi 5's two camera ports, inside the head) · Frames at 10 fps by day and 5 fps on a quiet night; 10 s clips around calls

4. 

   04

   Kerb radar

   In the back wall, 30 degrees down towards the crossing: people waiting at the kerb and people stepping on to and still in the near lane of the crossing, in rain, fog and the dark

   Raspberry Pi 5 (on the signal head floor) · UART · Up to 3 targets with position at 10 Hz

5. 

   05

   Lamp clamps and head sensor

   A clamp on each of the red, amber and green module feeds tells the brain which phase the controller is showing and whether a module is dark; the IMU finds the head hit or turned

   Raspberry Pi 5 (on the signal head floor) · Clamps into the ADS1115, then I²C (ADS1115 and LSM6DSOX) · Module currents at 50 Hz, shock and tilt

6. 

   06

   Controller contacts, call lights and tone

   Three dry contacts on the controller's own detector inputs (walk demand, crossing extension, vehicle demand); the 'seen you' and red confirmation lights behind slots in the back wall and a tone through the floor

   Raspberry Pi 5 (on the signal head floor) · GPIO (relays and piezo) + one data wire (lights) · Demand and extension contacts, light colour, tone

7. 07

   Secure element and tamper switch

   Every call signed; the tamper switch marks the log when the door opens

   Raspberry Pi 5 (on the signal head floor) · I²C + GPIO · Signatures, tamper flag

8. 08

   Power, backup and LTE-M

   5 V from the head's own feed; a LiPo keeps the Walter board sending the log and a power-cut or knockdown fault when the head is dark

   Raspberry Pi 5 (on the signal head floor) · 5 V rail + UART to the brain · Power about 6.5 W by day, 4.5 W at night (est.); calls and the 15-minute counts over LTE-M

9. 09

   All connected

   7 key parts, one program, and your phone

Our circuit board · rev A-0

One board of our own inside RoadOne

Every chip on one board we design, shaped to fit: the processor, cameras and sensors, Wi-Fi and Bluetooth, lights, sound and power. No plugs, ribbons or adapters. It is checked in our CAD against every part around it, and it arrives from the maker ready to run our software from a microSD card. Turn the model, or pick a part below to see where it sits.

Demo · 6 real-world moments

See RoadOne work

Short animated scenes of real moments: what happens today, what RoadOne does about it, and what lands on your phone. The same scenes play in the IEMI app.

Demo scenes show how RoadOne and its app are designed to behave. RoadOne is in design; nothing here is recorded from real equipment yet.

The idea

The crossing's own traffic light sees who is waiting, who is still crossing and every vehicle coming

How the parts connect

RoadOne, wired up

Every part, what links it to the brain, and how the data reaches your phone. A solid line is a cable; a dashed line is a radio link.

The program

What controls RoadOne

while True:
    phase = lamps.phase()                 # from the three clamps
    people = track(radar.read(), person_model(cam_x.frame()))
    relay_walk.set(people.waiting(2.0))     # demand, like a push button
    relay_ext.set(people.on_crossing())    # controller keeps its own maximum
    cars = track_vehicles(vehicle_model(cam_app.frame()))
    relay_veh.set(cars.in_zone())
    calls = count_rule(cars) + speed_rule(cars)
    calls += redlight_rule(phase, cars) + nearmiss_rule(cars, people)
    calls += blocked_rule(cars) + fault_rule(lamps, imu)
    for c in calls:
        if c.conf < c.line: c.kind = 'check'   # never guess
        atecc.sign(c); lights.show(c); uplink.send(c)
    time.sleep(0.1)

To your phone

How the data reaches RoadOne crossings app

Traffic signal engineers, road safety officers, the signal maintenance contractor and the transport planning team; a web page and open data feed for the council (Android, iPhone, web)

1. RoadOne signal head
2. LTE-M · MQTT over TLS
3. IEMI cloud (the authority's account)
4. Push, SMS and web; CSV, open data API and webhook to the traffic centre and the fault system
5. Signal engineers, road safety officers, the maintenance contractor and planners

Key specs

Targets for production units; they may change during development.

Pricing

Target pricing. Bought separately per approach: a plain 12 in 3-section head (about $320, est.), RoadSense AI ($1,490 + $95/month) and video detection (about $3,750 an approach, est. from a $15,000 four-approach quote): about $5,560 + $95/month (est.).

Indicative launch pricing in USD, excluding taxes and shipping. Final pricing is confirmed before any balance is charged.

1. 4 Nov 2026, 07:50LatestA council or DOT buys RoadOne as the near-side signal head at a signalised crossing: the same 3-section 12 in head on the same pole, with the bottom 8 to 19 ft above the footway (MUTCD 4D.15, https://mutcd.fhwa.dot.gov/htm/2009/part4/part4d.htm). So the electronics must be boards an assembly house makes and tests the same way every time, inside that head behind its own LED modules, without touching the controller's lamp drive.

   • What we designed: boards of our own inside the signal head, behind its own three LED modules, which stay the controller's. An 8-layer main board lies flat on the head floor with the processor and a heat block to an aluminium spreader bolted to the steel pole bracket, memory, the security chip, the latched microSD card, a motion chip and a small buzzer over the tone holes. A small corner board stands behind the door's bottom road-side corner with the approach camera and the door tamper sensor. A back strip carries the kerb radar chip, the white "seen you" and red confirmation lights, and LTE-M and Bluetooth at the far side of the head from the pole. A side strip carries the crossing camera. A power board on the left wall holds the supply, current sensors the lamp wires pass through, three isolated contacts for the controller and a backup cell.
   • How we checked it: the boards are written as code and opened in KiCad (0 design-rule violations). The code places 68 parts at their sizes and checks no overlaps, the heights in every gap, every board behind the 100 mm module zone, the corner board clear of the green module, the lights behind their slots, the antennas away from the pole, the lead voltage drop, and that every call from the CAD (the first car waiting, the queue, a vehicle 60 m out, a cyclist, the opposing lane; a car over the stop line, people in both lanes and at the far kerb, a near miss, a car on the studs; people waiting at the kerb and still crossing) passes through its window from where each lens really sits. The shared design review gives 16 pass, 3 fixed, 10 to prove on the first boards and 0 fail, and writes the quote pack.
   • What we learned: from a window in the head's floor, the count line 60 m up the approach lies 88° off the floor, so no floor window could show it. The door faces the approach, and its bottom corner below the green module is solid, so the approach camera now looks out of a 24 × 24 window there. The crossing window grew from a round 18 mm to 56 × 28 because a car over the stop line lies 70° off the road-side wall. We also found that a plain head has only its three switched lamp feeds, and a supply on one could hide a dead red module from the controller's lamp-out check, so the boards take an unswitched feed on a spare conductor and only sense the lamp feeds. The CAD moved the same day. There were no new CricketOne board decisions since the last update, and every other board was re-run and still passes.
   • What is next: the spreader, tab brackets and boards inside the head CAD with every part checked in 3D; the head's temperature in full summer sun; the highway authority's wiring rules for the feed and the controller contacts; LTE-M beside the steel pole; and the last board, SiteOne. See the boards at /build/roadone-boards.

   See it in 3DFull research and design

2. 29 Oct 2026, 05:06A city, county or state road team needs every signalised crossing to call the green man for people waiting, hold it for slow walkers, place vehicle demand, count every road user all year and report a dark lamp, mostly with nobody watching. Today it buys the plain signal head on an annual parts bid ($285-295 in public bids) and detection and data separately: a Washington State contract lists Miovision detection licences at $3,000-6,500 per intersection plus $195-750 a year per service, on extra cameras.

   • Buyer check with sources: 3-section LED head prices from the City of Tulsa bid ($295) and a distributor list ($285), the Florida DOT planning table ($800 with fitting), the Washington State Miovision contract (detection licences $3,000-6,500 per intersection, $195-750 a year per service) and an Iteris city contract (about $4 million for 100 intersections)
   • What we learned: the head is a cheap routine bid item, while detection and data are sold per intersection as licences and yearly services on extra cameras; nobody puts the detection inside the head that is already replaced on a schedule
   • Parts list prices checked on the Adafruit pages today: $749 per approach at qty 1, of which $405 is our electronics; the 4 GB Raspberry Pi 5 is now $130, so the brain is the same-size 2 GB at $90, and the cameras cost more than we had
   • Price kept at $2,990 + $59 a month per approach; cost about $989 at qty 1 and $730 at qty 100, a 67 % to 76 % margin (est.) that funds crossing video recording and pilots beside existing detection
   • All 21 part fit checks and 15 camera and radar views in the CAD still pass; about 12 h of fault reporting in a power cut rechecked; CAD review clean with no floating parts and no collisions
   • Product page: the first three FAQs answer why not the detection already bought, what it costs, and whether it fits the poles and controller; a power and size spec group
   • Next: three questions for signal teams in customer reviews (new heads or a kit, which call matters most and what proof qualifies it, per approach or per intersection), then the phase 1 close-out: shared parts across the line

   See it in 3DFull research and design

3. 28 Oct 2026, 13:45A council or DOT needs one thing at each signalised crossing that calls the green man for people waiting, holds it for slow walkers, places vehicle demand and counts every road user all year. The MUTCD keeps phases with the controller and lets detectors place calls; video detection needs a camera per approach, often on its own arm (about $15,000 for a four-approach intersection in a Cal Poly study), and street counters go on lamp columns; US DOT Safe Streets and Roads for All grants fund this safety data.

   • Market check: who buys one product per crossing (city, county and state traffic and road safety teams, UK highway authorities, their signal contractors), the rules (MUTCD Part 4 and 4D.15 mounting heights, detector inputs only, 80 in footway headroom), what they pay separately (a plain head, RoadSense AI, video detection at about $3,750 an approach, est.) and the competitors (Iteris, Econolite, Miovision, VivaCity); sources in DESIGN.md
   • New CAD: the crossing's 3-section 12 in near-side signal head (356 x 254 x 1,067 mm, bottom 8.7 ft above the footway) on its pole at the stop line, with a Raspberry Pi 5 brain, an approach camera behind a floor window, a crossing camera in the road-side wall, a kerb radar, lamp clamps, three controller contacts, call lights, a tone, LTE-M, a backup cell, a secure element and a tamper switch behind its own LED modules; 21/21 parts fit from datasheets, 15 camera and radar views checked with a new test that the pole and the visors do not hide them, no collisions, no floating parts
   • Design lesson: the approach camera first sat between the green and amber sections, but the green visor would hide its near view, so it moved to a window in the head's floor
   • equipment.json: 10 rules met (mounting height, LED sections, detector inputs only, nothing over the roadway, footway headroom, same size, no tickets, electrical, privacy, radio); 8 calls (6 alone), 4 impact cases and every security key
   • idea.json crossing plan, integration.json (6 parts, 5 app screens with a No one watching the crossing mode), bom.csv (about $710 an approach with the plain head, est.), buy.json with 10 key parts
   • New product page at /products/roadone/ in Public Sector: $2,990 + $59/month per approach against about $5,560 + $95/month bought separately (est.); folds RoadSense AI; AirfieldWatch AI, FlowCount AI and SmokeSentinel AI stay listed (zones with no signal head). Every flagship in the plan now has a first design; next: CAD review backlog and drawn idea plans for older catalogue products

   See it in 3DFull research and design

4. 28 Oct 2026, 13:45A council or DOT needs one thing at each signalised crossing that calls the green man for people waiting, holds it for slow walkers, places vehicle demand and counts every road user all year. The MUTCD keeps phases with the controller and lets detectors place calls; video detection needs a camera per approach, often on its own arm (about $15,000 for a four-approach intersection in a Cal Poly study), and street counters go on lamp columns; US DOT Safe Streets and Roads for All grants fund this safety data.

   • Now part of RoadOne: https://iemilabs.com/products/roadone/

   See it in 3DFull research and design

Smart equipment · legal on the field

RoadOne is the near-side vehicle signal head at a signalised pedestrian crossing, made smart

It replaces the approach's plain near-side signal head on the same pole, at the same height, on the same bracket and lamp feeds from the same controller, with the same three LED signal modules driven by the controller's own load switches, with every part built in. Everything inside the plain 356 x 254 x 1,067 mm signal head behind its own LED modules: brain, approach and crossing cameras, kerb radar, lamp clamps, controller relays, call lights, tone, LTE-M, backup cell, secure element and tamper switch. About +0.7 kg over a plain head of about 14 kg (est.); no counter on a lamp column, no detection camera on its own mast arm, no box on the pole.