IDT logo


  • Wirelessly link remote vehicle detectors to Traffic Signal Controllers
  • Supports any detector with open collector outputs including TrafiCam®, Heimdall® and inductive loops
  • Follows TRL guidance on wireless detection
  • iMesh-compliant so can be used as mid-span repeater
  Download a datasheet


Traffic control managers sometimes need to get vehicle detection data back to a controller for example, from upstream inductive loops. The traditional way to link the detection site with the controller is via duct along the footway or slot cutting. Sometimes these options are not feasible for reasons such as disruption or cost.  meshI/O is a technical alternative to ducts which enables vehicle detectors to be wirelessly linked to a nearby traffic signal controller.


The figure below shows meshI/O installed upstream of a traffic signal controller. The remote (upstream) end of the link is connected to a pair of inductive loops. The detector (in this installation) is contained inside the meshI/O enclosure.    Each time a vehicle traverses the loop the detector's output is transmitted immediately over the wireless link to a meshI/O unit installed inside the controller cabinet.

Click image to enlarge

Multiple channels

meshI/O actually supports 6 channels of simultaneous data transmission. So, for example, a pair of loops could be installed on each of three approaches to a junction and all 6 loops would be transmitted to the signal controller via the single meshI/O unit in the controller cabinet.


All meshI/O data transmission is bi-directional so, for example, a stage on a Puffin crossing could be inhibited by the signal controller at an adjacent junction.


As meshI/O uses the iMesh technology used by many UK local authorities for their UTC networks it means that meshI/O can act as a mid-span repeater. So, for example, two junctions could be be linked with a meshI/O unit between them simultaneously transmitting UTC data and detector data.


Six channels of digital (opto-isolated) inputs and outputs via screw terminals
Wireless Security
WPA, WPA2 Authentication
MAC Address Access Control
VPN (SSL & IPsec)
Hidden SSID
Netfilter - rule-based, multizone firewalling with NAT and masquerade
Port forwarding
Reserved bandwidth and priority by application or IP address

Internal option

WAN port
10/100 MB Auto-switching (RJ-45 connectors)
MDI/MDI-X Auto-switching
Static IP or DHCP client
-30 to +70°C, 5 – 95% RH
IP54 (cabinet mounting)
246 x 166 x 43 mm (width x depth x height)
0.8 Kg

External option

240 x 240 x 70 mm (width x depth x height)
with integral 15dBi directional antenna
220Vac or Power over Ethernet
0.8 Kg
-30 to +70°C, 5 – 95% RH
IP67 (outdoor) with integral 15dBi directional antenna


One i3G router can be used as a backhaul router to connect a UTC instation with an on-street, sub-network of iMesh routers. iMesh routers provide revenue-free, wireless communications links for traffic signal controllers, variable message signs and car park counters. iMesh is fully open-standard and can be used in conjunction with other technologies such as xDSL, i3G or fibre optic.
View details »


If you have a network of iMesh routers out on-street, you need a link (known as the 'backhaul') between the iMesh network and your UTC instation. One iCell router located alongside an iMesh router enables a backhaul link to be deployed rapidly without the need for a BT circuit or xDSL service.
View details »