Technical Documents
For product-specific support including datasheets, design guides, configuration guides, installation guides, release notes, and operating guides, make selections from the menus below.
Products
- Installation & Configuration Reference Guide
- Datasheet - FlexMag Flush and Deep Sensors
- Installation Guide - FlexMag and MicroRadar Sensors
- Quick Start Guide - FlexMag Deep Sensor
- Quick Start Guide - FlexMag Flush Sensor
- Safe Sensor Handling Instructions
- Datasheet - Sealant VSN240-EPX-SOT
- Safety Datasheet - Sealant VSN240-EPX-SOT Part A
- Safety Datasheet - Sealant VSN240-EPX-SOT Part B
- Installation & Configuration Reference Guide
- Datasheet - MicroRadar
- Quick Start Guide - MicroRadar for Bicycle Counts
- Quick Start Guide - MicroRadar for Bicycle Presence
- Datasheet - MicroRadar for Parking
- Quick Start Guide - MicroRadar for Parking
- Safe Sensor Handling Instructions
- Datasheet - Sealant VSN240-EPX-LOT
- Safety Datasheet - Sealant VSN240-EPX-LOT Part A
- Safety Datasheet - Sealant VSN240-EPX-LOT Part B
- Installation & Configuration Reference Guide
- Datasheet - FlexControl Module
- Quick Start Guide - FlexControl Module
- Datasheet - FlexConnect
- Quick Start Guide - FlexConnect
- Assembly Instructions - Bracket & DIN Mounts
- Datasheet - FlexControl Card (APCC)
- Datasheet - FlexControl Card (APCC) Enclosure
- Quick Start Guide - FlexControl Card (APCC)
- Installation Guide - FlexControl Card (APCC) and FlexControl Module
- Datasheet - FlexIsolator
- Datasheet - FlexRadio Cabinet
- Quick Start Guide - FlexRadio Cabinet
- Datasheet - Radio
- Datasheet - Contact Closure (CC) & Expansion (EX) Cards
- Installation Guide - Radio (SPP) and FlexRadio Cabinet
- Installation Guide - Contact Closure (CC) & Expansion (EX) Cards
- Release Notes - SncLog v4.2.1
- Release Notes - SncLog v4.2.0
- Installation & Configuration Reference Guide
- Datasheet - FlexAP
- Quick Start Guide - FlexAP (non-Serial Interface)
- Quick Start Guide - FlexAP (Serial Interface)
- Datasheet - FlexConnect
- Quick Start Guide - FlexConnect
- Assembly Instructions - Bracket & DIN Mounts
- Datasheet - Contact Closure (CC) & Expansion (EX) Cards
- Installation Guide - Contact Closure (CC) & Expansion (EX) Cards
- Datasheet - Access Point (AP240) (replaced by FlexAP)
- Installation Guide - FlexAP and AP240 Access Point
- Quick Start Guide - Access Point (AP240) non-Serial models (replaced by FlexAP)
- Quick Start Guide - Access Point (AP240) Serial models (replaced by FlexAP)
- Installation Guide - Ethernet Cable to Access Point Installation Instructions
- Installation & Configuration Reference Guide
- Datasheet - FlexRepeat Solar
- Quick Start Guide - FlexRepeat Solar
- Datasheet - FlexRepeat Long-Life & Repeat Long-Life
- Quick Start Guide - FlexRepeat Long-Life & Repeat Long-Life
- Datasheet - FlexNode Line Powered
- Quick Start Guide - FlexNode Line Powered
- Datasheet - External Antennas
- Datasheet - FLEX Repeater (replaced by FlexRepeat Long-Life)
- Quick Start Guide - FLEX Repeater & FLEX Long-Life Repeater (replaced by FlexRepeat Long-Life)
- Installation Guide - RP240/FLEX Repeater (replaced by Repeat Long-Life &FlexRepeat Long-Life)
- Datasheet - Repeater RP240-BH-LL-2 (replaced by Repeat Long-Life)
- Quick Start Guide - Repeater RP240-BH-LL-2 (replaced by Repeat Long-Life)
- Datasheet - Standard Repeater (replaced by Repeat Long-Life)
- Quick Start Guide - Standard Repeater (replaced by Repeat Long-Life)
- Datasheet - FLEX Solar Repeater (replaced by FlexRepeat Solar)
- Quick Start Guide - FLEX Solar Repeater (replaced by FlexRepeat Solar)
- Security Guide
- Datasheet - SNAPS Professional v2.20
- Datasheet - SensDiag
- Datasheet - SensMetrics
- Datasheet - SensTurn
- SNAPS Server Installation Preparation
- Set Up & Operating Guide - SNAPS Professional v2.18.x
- Set Up & Operating Guide - SNAPS Professional v2.16.x
- Release Notes - SNAPS Professional v2.20.7
- Release Notes - SNAPS Professional v2.20.6
- Release Notes - SNAPS Professional v2.20.2
- Release Notes - SNAPS Professional v2.20.1
- Release Notes - SNAPS Professional v2.18.13
- Release Notes - SNAPS Professional v2.18.12
- Release Notes - SNAPS Professional v2.18.11
- Release Notes - SNAPS Professional v2.18.10
- Release Notes - SNAPS Professional v2.18.9
- Release Notes - SNAPS Professional v2.18.8
- Release Notes - SNAPS Professional v2.18.7
- Release Notes - SNAPS Professional v2.18.6
- Release Notes - SNAPS Professional v2.18.5
- Release Notes - SNAPS Professional v2.18.4
- Release Notes - SNAPS Professional v2.18.3
- Release Notes - SNAPS Professional v2.18.2
- Release Notes - SNAPS Professional v2.18.1
- Release Notes - SNAPS Professional v2.18.0
- Release Notes - SNAPS Professional v2.16.5
- Release Notes - SNAPS Professional v2.16.0
- Release Notes - SNAPS Professional v2.14.0
- Release Notes - SNAPS Professional v2.12.3
- Release Notes - SNAPS Professional v2.12.2
- Release Notes - SNAPS Professional v2.12.1
- Release Notes - SNAPS Professional v2.12.0
- Release Notes - Arterial Travel Time v2.4
- Set Up & Operating Guide - Arterial Travel Time v2.4
- Datasheet - Cloud Connect
- Installation & Configuration Reference Guide
- Security Guide
- Set Up and Operating Guide - TrafficDOT v2.16.x
- Configuration Guide - Freeway and Arterial Applications
- Configuration Guide - Intersection Applications
- Release Notes - TrafficDOT v2.16.10
- Release Notes - TrafficDOT v2.16.9
- Release Notes - TrafficDOT v2.16.8
- Release Notes - TrafficDOT v2.16.7
- Release Notes - TrafficDOT v2.16.6
- Release Notes - TrafficDOT v2.16.5
- Release Notes - TrafficDOT v2.16.4
- Release Notes - TrafficDOT v2.16.1
- Release Notes - TrafficDOT v2.14.11
- Release Notes - TrafficDOT v2.14.10
- Release Notes - TrafficDOT v2.14.9
- Release Notes - TrafficDOT v2.14.7
- Release Notes - TrafficDOT v2.14.6
- Release Notes - TrafficDOT v2.14.4
- Release Notes - TrafficDOT v2.14.2
- Release Notes - TrafficDOT v2.14.0
- Release Notes - TrafficDOT v2.12.17
- Release Notes - TrafficDOT v2.12.15
- Release Notes - TrafficDOT v2.12.12
- Release Notes - TrafficDOT v2.12.9
- Release Notes - TrafficDOT v2.12.8
- Release Notes - TrafficDOT v2.12.7
- Release Notes - TrafficDOT v2.12.6
- Release Notes - TrafficDOT v2.12.2
- Release Notes - TrafficDOT v2.12.1
- Release Notes - TrafficDOT v2.12.0
- Release Notes - TrafficDOT v2.10.5
- Release Notes - TrafficDOT v2.10.3
- Release Notes - TrafficDOT v2.10.2
- Release Notes - TrafficDOT v2.10.1
- Release Notes - TrafficDOT v2.10.0
Document Types
- Datasheet - FlexMag Flush and Deep Sensors
- Datasheet - Original VSN240 Sensor
- Datasheet - MicroRadar
- Datasheet - MicroRadar for Parking
- Datasheet - GiveMeGreen!
- Datasheet - FlexControl Module
- Datasheet - FlexAP
- Datasheet - FlexIsolator
- Datasheet - FlexRadio Cabinet
- Datasheet - Radio
- Datasheet - FlexControl Card (APCC)
- Datasheet - FlexControl Card (APCC) Enclosure
- Datasheet - Contact Closure (CC) & Expansion (EX) Cards
- Datasheet - FlexConnect
- Datasheet - FlexDetect
- Datasheet - FlexRepeat Solar
- Datasheet - FlexRepeat Long-Life & Repeat Long-Life
- Datasheet - FlexNode Line Powered
- Datasheet - FLEX Repeater (replaced by FlexRepeat Long-Life)
- Datasheet - Repeater RP240-BH-LL-2 (replaced by Repeat Long-Life)
- Datasheet - Standard Repeater (replaced by Repeat Long-Life)
- Datasheet - FLEX Solar Repeater (replaced by FlexRepeat Solar)
- Datasheet - SNAPS Professional v2.20
- Datasheet - SensConfig
- Datasheet - SensDiag
- Datasheet - SensTurn
- Datasheet - SensMetrics
- Datasheet - SensID (Bluetooth or Wi-Fi Vehicle Re-ID)
- Datasheet - FlexID for Bluetooth based Re-Identification (SensID/VIMS)
- Datasheet - FlexID for Wi-Fi based Re-Identification (SensID/VIMS)
- Datasheet - Cloud Connect
- Datasheet - Access Point (AP240) (replaced by FlexAP)
- Datasheet - External Antennas
- Datasheet - Sealant VSN240-EPX-LOT
- Datasheet - Sealant VSN240-EPX-SOT
- Safety Datasheet - Sealant VSN240-EPX-LOT Part A
- Safety Datasheet - Sealant VSN240-EPX-LOT Part B
- Safety Datasheet - Sealant VSN240-EPX-SOT Part A
- Safety Datasheet - Sealant VSN240-EPX-SOT Part B
- Installation Guide - FlexMag and MicroRadar Sensors
- Installation and Configuration Guide - GiveMeGreen!
- Installation Guide - FlexControl Card (APCC) and FlexControl Module
- Installation Guide - Radio (SPP) and FlexRadio Cabinet
- Installation Guide - FlexAP and AP240 Access Point
- Installation Guide - Contact Closure (CC) & Expansion (EX) Cards
- Installation Guide - Ethernet Cable to Access Point Installation Instructions
- Installation Guide - RP240/FLEX Repeater (replaced by Repeat Long-Life & FlexRepeat Long-Life)
- Installation Guide - SensID
- Assembly Instructions - Bracket & DIN Mounts (for FlexControl, FlexIsolator & FlexConnect)
- Quick Start Guide - FlexMag Deep Sensor
- Quick Start Guide - FlexMag Flush Sensor
- Quick Start Guide - MicroRadar for Bicycle Counts
- Quick Start Guide - MicroRadar for Bicycle Presence
- Quick Start Guide - MicroRadar for Parking
- Quick Start Guide - FlexControl Module
- Quick Start Guide - FlexRadio Cabinet
- Quick Start Guide - FlexAP (non-Serial Interface)
- Quick Start Guide - FlexAP (Serial Interface)
- Quick Start Guide - FlexControl Card (APCC)
- Quick Start Guide - FlexConnect
- Quick Start Guide - FlexDetect Adapter
- Quick Start Guide - FlexRepeat Solar
- Quick Start Guide - FlexRepeat Long-Life & Repeat Long-Life
- Quick Start Guide - FlexNode Line Powered
- Quick Start Guide - FLEX Repeater & FLEX Long-Life Repeater (replaced by FlexRepeat Long-Life)
- Quick Start Guide - Repeater RP240-BH-LL-2 (replaced by Repeat Long-Life)
- Quick Start Guide - Standard Repeater (replaced by Repeat Long-Life)
- Quick Start Guide - FLEX Solar Repeater (replaced by FlexRepeat Solar)
- Quick Start Guide - Access Point (AP240) non-Serial models (replaced by FlexAP)
- Quick Start Guide - Access Point (AP240) Serial models (replaced by FlexAP)
- Tech Note - Network Connectivity VDS v4.2.2
- Release Notes - Vehicle Detection System v4.2.2
- Release Notes - Vehicle Detection System v4.2.1
- Release Notes - Vehicle Detection System v3.0.13
- Release Notes - Vehicle Detection System v3.0.12
- Release Notes - Vehicle Detection System v3.0.11
- Release Notes - Vehicle Detection System v3.0.10
- Release Notes - Vehicle Detection System v3.0.9
- Release Notes - Vehicle Detection System v3.0.6
- Release Notes - Vehicle Detection System v3.0.3
- Release Notes - Vehicle Detection System v2.10.14
- Release Notes - Vehicle Detection System v2.10.13
- Release Notes - Vehicle Detection System v2.10.12
- Release Notes - Vehicle Detection System v2.10.11
- Release Notes - Vehicle Detection System v2.10.10
- Release Notes - Vehicle Detection System v2.10.9
- Release Notes - Vehicle Detection System v2.10.7
- Release Notes - Vehicle Detection System v2.10.3
- Release Notes - Vehicle Detection System v2.10.2
- Release Notes - Vehicle Detection System v2.10.1
- Release Notes - Vehicle Detection System v2.10.0
- Release Notes - Vehicle Detection System v2.6.4
- Release Notes - Vehicle Detection System v2.6.3
- Release Notes - Vehicle Detection System v2.6.2
- Release Notes - Vehicle Detection System v2.6.1
- Release Notes - Vehicle Detection System v1.8.16
- Release Notes - Vehicle Detection System v1.8.9
- Release Notes - Vehicle Detection System v1.8.15
- Release Notes - SensConfig v1.4.1
- Release Notes - SensConfig v1.4.0
- Release Notes - SensConfig v1.2.1
- Release Notes - SensConfig v1.2.0
- Release Notes - TrafficDOT v2.16.10
- Release Notes - TrafficDOT v2.16.9
- Release Notes - TrafficDOT v2.16.8
- Release Notes - TrafficDOT v2.16.7
- Release Notes - TrafficDOT v2.16.6
- Release Notes - TrafficDOT v2.16.5
- Release Notes - TrafficDOT v2.16.4
- Release Notes - TrafficDOT v2.16.1
- Release Notes - TrafficDOT v2.14.11
- Release Notes - TrafficDOT v2.14.10
- Release Notes - TrafficDOT v2.14.9
- Release Notes - TrafficDOT v2.14.7
- Release Notes - TrafficDOT v2.14.6
- Release Notes - TrafficDOT v2.14.4
- Release Notes - TrafficDOT v2.14.2
- Release Notes - TrafficDOT v2.14.0
- Release Notes - TrafficDOT v2.12.17
- Release Notes - TrafficDOT v2.12.15
- Release Notes - TrafficDOT v2.12.12
- Release Notes - TrafficDOT v2.12.9
- Release Notes - TrafficDOT v2.12.8
- Release Notes - TrafficDOT v2.12.7
- Release Notes - TrafficDOT v2.12.6
- Release Notes - TrafficDOT v2.12.2
- Release Notes - TrafficDOT v2.12.1
- Release Notes - TrafficDOT v2.12.0
- Release Notes - TrafficDOT v2.10.5
- Release Notes - TrafficDOT v2.10.3
- Release Notes - TrafficDOT v2.10.2
- Release Notes - TrafficDOT v2.10.1
- Release Notes - TrafficDOT v2.10.0
- Release Notes - SNAPS Professional v2.20.7
- Release Notes - SNAPS Professional v2.20.6
- Release Notes - SNAPS Professional v2.20.2
- Release Notes - SNAPS Professional v2.20.1
- Release Notes - SNAPS Professional v2.18.13
- Release Notes - SNAPS Professional v2.18.12
- Release Notes - SNAPS Professional v2.18.11
- Release Notes - SNAPS Professional v2.18.10
- Release Notes - SNAPS Professional v2.18.9
- Release Notes - SNAPS Professional v2.18.8
- Release Notes - SNAPS Professional v2.18.7
- Release Notes - SNAPS Professional v2.18.6
- Release Notes - SNAPS Professional v2.18.5
- Release Notes - SNAPS Professional v2.18.4
- Release Notes - SNAPS Professional v2.18.3
- Release Notes - SNAPS Professional v2.18.2
- Release Notes - SNAPS Professional v2.18.1
- Release Notes - SNAPS Professional v2.18.0
- Release Notes - SNAPS Professional v2.16.5
- Release Notes - SNAPS Professional v2.16.0
- Release Notes - SNAPS Professional v2.14.0
- Release Notes - SNAPS Professional v2.12.3
- Release Notes - SNAPS Professional v2.12.2
- Release Notes - SNAPS Professional v2.12.1
- Release Notes - SNAPS Professional v2.12.0
- Release Notes - VIMS v4.2.0
- Release Notes - SncLog v4.2.1
- Release Notes - SncLog v4.2.0
- Release Notes - Arterial Travel Time v2.4
Software
Software | Current Version* | Latest Release Notes |
---|---|---|
SensConfig | 1.4.1 | 1.4.1 |
TrafficDOT | 2.16.10 | 2.16.10 |
SNAPS | 2.20.7 | 2.20.7 |
VIMS | 4.2.0 | 4.2.0 |
SncLog | 4.2.1 | 4.2.1 |
Arterial Travel Time | 2.4.0 | 2.4.0 |
Firmware | Current Version | Latest Release Notes |
AP | 1.8.16 | VDS 1.8.16 |
FlexControl Card (APCC) | 4.2.2 | VDS 4.2.2 |
FlexControl Module | 4.2.2 | VDS 4.2.2 |
FlexAP | 4.2.2 | VDS 4.2.2 |
CC/EX Cards | 61 | VDS 4.2.2 |
SPP | 208 | VDS 4.2.1 |
FlexConnect | 25 | VDS 4.2.2 |
FlexDetect | 9.2.24 | VDS 4.2.1 |
Repeaters (SW *.2.7) | 218.2.7 | VDS 4.2.2 |
FlexRepeat (SW *.3.7) | 218.3.7 | VDS 4.2.2 |
FlexNode (SW *.4.7) | 218.4.7 | VDS 4.2.2 |
FlexMag F Sensors (F-2 & F-GR) | 219.5.3 | VDS 4.2.2 |
FlexMag T Sensors (T-2 & T-GR) | 219.5.8 | VDS 4.2.2 |
MicroRadar Sensor | 217.6.14 | VDS 4.2.2 |
TrafficDOT
Features of TrafficDOT
- Real-time system configuration and monitoring of all connected Sensys Networks devices
- Primary control interface for your wireless sensor network installation
- Multiple levels of security for connections to Sensys Network devices
- User roles to support multiple levels of configuration and automation
- Runs as an Adobe AIR application
Frequently Asked Questions
Click on any topic to view more information.
Installation (4)
The upgrades are controlled using TrafficDot, where the TrafficDot and access point software that implements the upgrade process has been designed to work even when the IP connection suffers dropouts. As a result, firmware upgrades can even be performed for devices where the IP connectivity to the access point is supported by cellular data services.
Note that the Sensys Networks VSN240-T flush-mount wireless sensor can only support presence detection applications and is not suitable for count station applications. The VSN240-F flush-mount wireless sensor, however, can be configured to support both types of applications.
System (7)
Certain applications, however, can still require multiple access points – for example, stop bar detection combined with advance detection at four approaches of an intersection may require two or more access points pointed in different directions to fully provide coverage to the sensors and repeaters at all the approaches. Multiple access points may also be necessary in order to support a large number of sensors with minimum data latency, especially in traffic signal control applications. Note that each access point would typically be configured to operate on a different frequency channel.
If the access points are powered from a single traffic controller, care must be taken that there is adequate power available. Each access point requires its own CC card to support the data interface to the traffic controller, as required by the application.
If the data interface is via IP connectivity, each access point requires its own IP connectivity to support the interface to upstream servers. Future versions of the access point, however, will allow it to be configured as a router so that a single IP connection can be shared among many IP devices, including other access points.
Replacing a loop in this way – effectively retrofitting an old vehicle detection installation – is especially feasible because the Sensys Networks Wireless Vehicle Detection System supports contact closure interfaces to standard traffic controllers. By properly configuring the Sensys Networks Contact Closure (CC) and Extension (EX) cards, Sensys Networks wireless sensors can provide the same presence or pulse signals in the same phase and detector groups as the loops that they replace.
In general, however, a sensor should not be installed near power stations, underground power lines, high-tension (> 5 kV) power lines, light rail tracks (unless detection of light rail vehicles is desired), or any other place where large changing magnetic fields are present.
Tunnel, bridges, elevated freeways, and the presence of rebar in reinforced concrete do not necessarily affect operation of a Sensys Networks wireless sensor. The proximity of large steel structures, however, including large metal bridges, may reduce the sensitivity of a sensor because a vehicle will have less effect on the local magnetic field than in steel-free environments.
The motion of a bridge may also generate low-frequency electro-magnetic noise as it vibrates that can affect a sensor’s measurements and its ability to self-calibrate. The impact of this effect can be minimized by locating the sensors over a bridge’s piers.
For more information about advanced Sensys Networks technology from Sensys Networks, please visit www.Sensys NetworksNetworks.com.
Performance (23)
These particular batteries were selected based on their low-drain, long-term operating characteristics and their ability to operate over a wide range of temperatures (from -67 °F / -55 °C to +185 °F / +85 °C). Sensys Networks then estimated an average battery pack life of 10 years based on the likely number of vehicles that would be detected over that period, a typical sensor configuration, and worst-case extremes over the sensor’s specified temperature range (-40 °F / -40 °C to +185 °F / +85 °C).
Sensys Networks has completed over 3.5 million hours of independent testing on batteries from various manufacturers, cell configurations, environmental conditions and product load profiles to characterize the performance of these cells in our product.
For example, as described in the Sensys Networks whitepaper, “Measurement of Sensys Networks Wireless Sensor Battery Life”, Sensys Networks investigated the remaining lifetime of battery packs obtained from three sensors that had been installed on a Texas highway for a year and a half. During the sensors’ operation, the installation site experienced air temperatures as low as 21 °F / -6.1 °C and as high as 100 °F / 37.8 °C, with a maximum daily temperature swing of 40 °F / 20.2 °C. Over the year and a half that these sensors were deployed, each sensor detected approximately 5 to 8 million vehicles, depending on what lane it was in. As part of this particular installation, the sensors were configured to transmit each vehicle detection event to the access point as it occurred, a configuration that Sensys Networks does not recommend for count stations because it does not conserve battery power. Nonetheless, analysis of the battery packs recovered from the sensors reveal an estimated total battery life of approximately 8.5 to 13.0 years.
Another Sensys Networks whitepaper, “Battery Life Analysis of the Sensys Networks Wireless Vehicle Detection System by ARRB Consulting/La Trobe University”, describes an analytical estimate of the sensor battery life developed by researchers at ARRB Consulting and La Trobe University (Melbourne, Australia). Working under contract to several Australian state road and traffic authorities, their work reveals that a sensor’s current consumption depends in part on the number of vehicles detected over its lifetime. Given the capacity of the battery used by the Sensys Networks wireless sensor and the number of vehicles that can be detected, the report concludes that the claimed average battery life of 10 years is likely to be achieved.
In general, the failure of a single sensor is independent of the other installed sensors, so any lack of data in one traffic lane does not affect the data from the other lanes. Contrast this situation to that of a radar or video system, where equipment failure means that data for all lanes is lost.
Options are available for either 36-58VDC isolated power input (nominally, 48VDC) or, if solar power is to be used, 9-20VDC power input (nominally, 12VDC). Power is delivered to the Sensys Networks access point via Power over Ethernet (PoE) twisted-pair cable, either using a 48VDC (standard) or 12VDC (non-standard) PoE implementation.
If the access point will provide detection data to a roadside traffic controller, then the Sensys Networks CC card will support that interface and will provide power from the traffic controller backplane to the access point.
If the access point will not provide detection data to a traffic controller and no CC card will be used, then power can be provided from a nearby traffic controller or power pedestal or any available source of 110-240VAC, 50-60Hz power by using a 48VDC power supply and PoE power injector that can be purchased from Sensys Networks.
If the access point will be powered by solar panels and backup batteries, a 12VDC PoE power injector is available from Sensys Networks.
If the access point will be powered by solar panels and backup batteries, a non-standard 12VDC PoE power injector is available from Sensys Networks
From that point on, whether the sensor can be “found” physically is more or less irrelevant – its detection data can be received and its performance can be monitored without ever touching the device. If a sensor is lost in the sense that it does not have radio communications with the access point (or repeater), the access point (or repeater) can be manually swept across the sixteen different frequency channels in order to “find” the sensor and then reconfigure the sensor to the desired channel. If this step does not succeed and the sensor itself has failed – either at the end of its battery life or prematurely for whatever reason – it can be left where it was installed.
Significant sources of data latency in the system include the TDMA latency due to the 125 ms frames used to support sensor communications with an access point or repeater – if a detection event occurs immediately after a specific sensor’s time slot has passed, that sensor will need to wait 1/8th of a second until the next slot is available before it can communicate its detection data – and any retransmission latency that may be incurred if a sensor must re-transmit its data to an access point or repeater because earlier transmissions were not successfully acknowledged.
The presence of latency does not, however, imply that vehicles are detected late. Each sensor measures the x-, y-, and z-axis components of the local magnetic field at a 128 Hz sampling rate or every 7.8 ms. An ON event occurs when the absolute value of the measured magnetic field exceeds the Detect threshold, and an OFF event occurs when the value returns below the Undetect threshold. These detection events are communicated to the Sensys Networks access point as time-stamped data, where the time reference for all sensors is established by the access point. If the access point has IP connectivity and is locked to timing signals generated by the National Institute of Science and Technology (NIST), the timestamps are accurate to within 1 ms.
For 48VDC access points, the power and data lines are similarly protected with SIDACtor surge arrestors and TeleLink resettable fuses.
For 12VDC access points, the expectation is that the solar panel and backup batteries providing the input power will be mounted on the same pole as the access point. As a result, any lightning strike likely to induce a power surge on the power and data lines will be a direct hit, in which case no amount of protection would suffice. Consequently, the only protection provided in the access point 12VDC power circuitry is a triac-based overvoltage protection circuit.
Communications between a Sensys Networks wireless sensor and its corresponding access point or repeater or between a Sensys Networks access point and a repeater can be on any of sixteen different frequency channels. The channel should be selected to achieve the best Sensys Networks radio performance. If possible, the system should be located away from sources of 2.4 GHz radiation such as Wi-Fi hotspots and microwave ovens, but, even if radio frequency interference is present, the Sensys Networks Wireless Vehicle Detection System has the flexibility to operate on a frequency channel where the impact of interference is minimized. In North America, because of the way Wi- Fi channels are defined, Sensys Networks channels 14 and 15 are least affected by the presence of Wi-Fi devices.
If desired, one can use a Wi-Fi-enabled laptop and its software to determine which Wi-Fi channels are in use nearby and then configure the Sensys Networks channels so that the frequency offset from the Wi-Fi channels is as large as possible. Generally, however, such a site survey is unnecessary.
Measurement results can be obtained from the access point using the TrafficDot application, either remotely via the access point’s IP connectivity or with a laptop PC connected directly to the access point’s Ethernet port in the field.
Sensys Networks recommends that a clear line-of-sight exist between all sensors and their supporting access point or repeater and between all repeaters and their supporting access point. In general, an access point or repeater should be oriented so that all the Sensys Networks radio devices that are intended to be supported are within an approximate 120° field of view (±60° in both elevation and azimuth from boresight). Beyond this angular extent, power levels drop off significantly.
Barrier walls, nearby buildings and structures, and stationary or moving vehicles, however, can all create reflections that interfere with proper reception. The radios and the communications protocols employed by the Sensys Networks wireless system are designed to recover from dynamic changes in the radio environment such as created by moving vehicles. Static conditions, however, should be addressed upon installation by ensuring that the RSSI and LQI values are in their desired ranges.
If the RSSI and LQI values for specific sensors or repeaters are not above their respective recommended values, they may be beyond the range of the access point or repeater or may be subject to interference due to reflections or local spurious emissions. To correct any such problem, different frequency channels can be selected, the angles at which the access point or repeaters are aimed can be changed, the access point or repeaters can be mounted at a higher elevation point, or the distance between devices can be reduced by choosing or installing different mounting locations for the access point or repeaters.
Wireless communications between each sensor and its communicating access point or repeater involve an ARQ (Automatic Repeat-reQuest) protocol where, after a sensor transmits data, it waits for an acknowledgement from the repeater. If an acknowledgement is not received before a timeout period elapses, the sensor assumes the transmission has failed and re-sends the data. Up to 16 detection events can be buffered by the sensor.
Within an access point, 130 kilobytes (kB) are reserved for event caching to buffer the raw detection data prior to transmission upstream. This ability to buffer event data becomes crucial, especially when IP connectivity to the access point is supported by cellular data services that can suffer temporary outages. Depending on how many detection events are actually recorded by all the sensors connected to the access point, typically several minutes of raw data can be buffered until communications upstream are again available.
Additionally, if APSTAT is configured to run on the access point, then 500 kB are reserved for storage of data that has been processed by APSTAT. Depending on how what statistics are compiled and what interval is configured, up to weeks of data can be stored on the access point.
Troubleshooting
TrafficDOT
- Verify that Master Mode is enabled for SPP(s) (SPP 0 and SPP1).
- Verify SPP connection is on (SPP text displays black for active connection, red for not connected).
- Identify configured SPP radios and RF channels.
- Confirm the proper height and orientation of SPPs and RPs.
- Confirm sensors are within range of SPP or RP.
If SPP 0/1 link light is off.
- Check cable between SPP and Isolator.
- Check cable between APCC and Isolator.
- Check that Isolator power and link lights are on.
- Confirm RF channels.
- Scan all SPP, RP RF channels for missing sensors (may need to wait at least 2 minutes per channel).
- Confirm SPP or RP is within range, proper height, and orientation.
- Reset Keep RF command.
- Perform hard reset (sets sensors back to factory-default RF channel 0).
- Confirm that battery is connected to RP.
- Check if equipment is damaged or missing.
- Confirm RF channels.
- Scan all RF channels for missing RPs (may need to wait at least 2 minutes per channel).
- Reset Keep RF command.
- Perform hard reset (sets RPs back to factory-default RF channels 0 -> 1).
- Confirm that SPP or RP is within range, proper height, and orientation..
- Confirm that battery is connected to RP.
Confirm that battery has sufficient charge.
- Sufficiently charged battery – LEDs flash red and green when initially powered, then flash red about every 3 seconds.
- Insufficiently charged battery – LEDs flash red and green consistently or not flash at all.
- Check if equipment is damaged or missing.
Confirm RF settings (RSSI, LQI, and Timeslot) are within specs.
- If RSSI value is low, try changing geometry of SPP or RP.
- If LQI value is low, select a different (available) RF channel.
- If Timeslot is red, click the Auto-Assign Timeslots button.
Check if active sensor is stuck high.
- If sensor stuck high, recalibrate sensor.
- Check for magnetic noise source.
- Check the recalibrate timeout values (under the AP's Detection tab). Five minutes is default.
Check cable between APCC card and EX card(s).
Confirm proper SW1 and SW2 settings.
- Confirm each card has a unique address (shelf ID and slot ID configuration).
Check communication with EX card(s).
- Verify that cable is connected to the 'In' port of the EX card from the 'Out' port of the previous card.
Check for damaged EX card (Swap cards if necessary).
- Check if Fault Indicator light is on (indicates damage).
- Visually inspect circuit board for damage (such as black marks).
- Press reset button to see if all lights display.
- Check for proper input voltage (.5 amps at 12v is nominal for TS2 and .2 amps at 24v is nominal for TS1).
- Verify that there is nothing in the adjacent slot (if using 4-channel mode).
- If 2070/TS2 type controller, verify that APCC/EX card TS-mode DIP switch is set to TS2 (SW1 position 3 should be OFF).
- Check for proper BIU operation.
- Check for stuck sensor.
- Confirm sensor zone assignment.
- Verify proper input backplane assignment.
- Verify that there is nothing in the adjacent slot (if using 4-channel mode).
- If 2070/TS2 type controller, verify that CC/EX card TS-mode DIP switch is set to TS2 (SW1 position 3 should be OFF).
- Check for proper BIU operation.
- Check that detection zones are assigned properly.
- Check that no detection occurs when no vehicle is present (magnetic noise).
- Check if sensor is detecting adjacent lane traffic.
- Check the Checksum failure count (under Controller Card>Info tab). (Too many can cause a false call or cause the card to reboot.)
- Check failsafe mode (default is OFF).
Sensor(s) missing vehicle detections.
- Check if sensor is installed too deep.
- Check if RSSI value is too high (<-90 dBm) when no vehicles are present.
- Verify that the Delay setting is set properly.
- Check connectivity and verify that all sensors are assigned to proper card address.
- Verify that there are no timeslot conflicts.
Check the detection default settings
- For F-model sensors, check the detect Z threshold (Default value is 12. Lowering the value increases sensitivity.)
- For T-model sensors, check the Stop Bar mode (Default value is Stop Bar mode 5. Lowering the value increases sensitivity.)
- Confirm valid sensor zone name and position for each assigned sensor.
- Verify that Master Mode is enabled.
- Confirm RF channel.
- Confirm AP or RP is within range, proper height, and orientation.
- Confirm RF channel.
- Confirm AP or RP is within range, proper height, and orientation.
- Reset Keep RF command.
- Perform hard reset (sets sensors back to factory-default RF channels 0).
- Confirm that battery is connected to RP.
- Check if equipment is damaged or missing.
- Confirm RF channels.
- Scan all RF channels for missing RPs (may need to wait at least 2 minutes per channel).
- Reset Keep RF command.
- Perform hard reset (sets RPs back to factory-default RF channels 0 -> 1).
- Confirm that AP or RP is within range, proper height, and orientation.
- Confirm that battery is connected to RP.
Confirm that battery has sufficient charge.
- Sufficiently charged battery - LEDs flash red and green when initially powered, then flash red about every 3 seconds.
- Insufficiently charged battery - LEDs flash red and green consistently or not flash at all.
- Check if equipment is damaged or missing.
Confirm RF settings (RSSI, LQI, and Timeslot) are within specs.
- If RSSI value is weak, try changing geometry of AP or RP.
- If LQI value is low, select a different (available) RF channel.
- If Timeslot is red, click the Auto-Assign Timeslots button.
Check if active sensor is stuck on.
- If sensor stuck high, recalibrate sensor.
- Check for magnetic noise source.
- Check the recalibrate timeout values (under the AP's Detection tab). Five minutes is default.
- Check cable between CC card and EX card(s).
Confirm proper SW1 and SW2 settings.
- Confirm each card has a unique address (shelf ID and slot ID configuration).
Check communication with EX card(s).
- Verify that cable is connected to the 'In' port of the EX card from the 'Out' port of the previous card.
Check for damaged CC/EX card (Swap cards if necessary).
- Check if Fault Indicator light is on (indicates damage).
- Visually inspect circuit board for damage (such as black marks).
- Press reset button to see if all lights display.
- Check for proper input voltage (.5 amps at 12v is nominal for TS2 and .2 amps at 24v is nominal for TS1).
- Check that detection zones are assigned properly.
- Check that no detection occurs when no vehicle is present (magnetic noise).
- Check if sensor is detecting adjacent lane traffic.
- Check the Checksum failure count (under Controller Card>Info tab). (Too many can cause a false call or cause the card to reboot.)
- Check failsafe mode (default is OFF).
Sensor(s) missing vehicle detections.
- Check if sensor is installed too deep.
- Check if RSSI value is too high (<-90 dBm) when no vehicles are present.
- Verify that the Delay setting is set properly.
- Check connectivity and verify that all sensors are assigned to valid card address.
- Verify that there are no timeslot conflicts.
Check the detection default settings
- For F-model sensors, check the detect Z threshold (Default value is 12. Lowering the value increases sensitivity.)
- For T-model sensors, check the Stop Bar mode. (Default value is Stop Bar mode 5. Lowering the value increases sensitivity.)
- Verify proper input backplane assignment.
- Verify that there is nothing in the adjacent slot (if using 4-channel mode).
- If 2070/TS2 type controller, verify that CC/EX card TS-mode DIP switch is set to TS2 (SW1 position 3 should be OFF).
- Check for proper BIU operation.
- Set correct IP settings (address, mask, gateway), default AP IP address is 192.168.2.100, subnet mask is 255.255.255.0, set laptop static IP address 192.168.2.200 (May require administrator rights.)
- Ensure that laptop firewall is disabled. (May require administrator rights.)
- Ensure that the laptop's local network adapter is enabled.
- Verify the link light adapter on the laptop is on.
- Check that laptop's alternative IP configuration is not in use. (May require administrator rights.)
- Ensure proper physical connections.
- Inspect ports for visible damage.
Test cable for correct PIN out assignment (T-568B).
- If cable is damaged, re-terminate the connectors or replace the cable (as needed).
- If damaged, contact Sensys Networks for replacement of APCC.
- Set correct IP settings (address, mask, gateway), default AP IP address is 192.168.2.100, subnet mask is 255.255.255.0, set laptop static IP address 192.168.2.200. (May require administrator rights.)
- Ensure that laptop firewall is disabled. (May require administrator rights.)
- Ensure that the laptop's local network adapter is enabled.
- Verify the link light adapter on the laptop is on.
- Check that laptop's alternative IP configuration is not in use. (May require administrator rights.)
- Ensure valid physical connections.
- Inspect ports for visible damage. (If damaged, contact Sensys Networks for replacement of AccessBox.)
- If connections are correct, contact Sensys Networks for replacement of AccessBox.
Test cable for valid PIN out (T-568B). (Use cable tester.)
- If cable is damaged, re-terminate the connectors or replace the cable (as needed).
- Verify that the backplane voltage from the rack to the CC card is sufficient. (~11-24 VDC is required)
- Verify that BIU is powered and functioning properly (if applicable).
- Check for damaged Sensys Networks equipment; if damaged contact Sensys Networks for equipment replacement.
- Ensure valid physical connections in proper ports. (“RJ45” connects to the AP, “switch hub” connects to laptop)
- If power light on the POE is dim there is a short between the POE and AP.
- Crossover cable may be required for connection to some laptop Ethernet adapters.
- If green power light on POE is off, check for power.
SNAPS
- Verify that correct URL has been entered.
- Check that SNAPS IP address and DNS name are valid.
- Ping the SNAPS server.
- Check that browser is online (supported browser).
- If SNAPS splash screen displays, but you are unable to log onto SNAPS, have the SNAPS administrator validate your SNAPS login ID and password.
- Check for missing information (required fields not completed).
- Check for duplicate labels.
- Check that only allowable characters are used.
- Check that AP/APCC naming conventions are followed. (SNAPS 2.6.1 validates names automatically)
- Confirm that user account has sufficient rights.
If you can successfully ping the AP from the SNAPS console, check the AP entries in SNAPS.
Check the AP configuration entries in SNAPS
- IP address or DNS name
- HTTP port
- TCP port
- VPN name and password
- If the AP configuration entries in SNAPS are correct, verify that all of the necessary ports are open on the firewall.
If you cannot successfully ping the AP from SNAPS, try to ping the router from SNAPS console.
If you cannot successfully ping the router from SNAPS console, contact your IT department for further assistance.
If you can successfully ping the router from SNAPS console, get someone to go onsite and have them ping their local router from APCC.
- If you cannot ping local router from APCC, contact IT department.
- If a cellular modem is used, confirm that equipment and service has been activated.
Verify VPN configuration on SNAPS and TrafficDOT.
- If the VPN user name and password match those on the AP, check the AP modem page.
Verify that the NTPD service is running.
Check the IP address(es) or host name(s) of the NTP servers designated on the systems configuration network tab in TrafficDOT.
- If the information is not correct, make correct entries and then restart the AP.
- If the information is correct, ping the NTP server from the AP.
- If you are unable to successfully ping the NTP server, contact your IT department for assistance.
Check if NTP ports are blocked (firewall).
- If the NTP ports are blocked, have your IT department unblock them.
- If the NTP ports are not blocked, contact Sensys Networks for assistance.
The NTPD service is not running.
- Start NTPD service or ask your IT department to do so.
- After NTPD service is started, check the date on the AP.
- If the date on the AP is still not set, contact Sensys Networks.
- Verify that none of the AP/APCC logging Statuses are red. Check connection and configuration.
- Verify that there is data for date which the report is being run.
Confirm that none of the AP/APCC processes are red.
- Receiving Data?
- TimeSync?
- DotTable in sync?
- Verify that AP/APCC's current sensor positions are synchronized in DotTable.
- Verify that AP/APCC's IP configuration is correct.
- Verify that multiple AP/APCC's are not assigned to the same IP address.
- Verify that report is running for intended AP/APCC's.
- Verify that the Dot tables contain accurate and relevant sensor information.
- If any configuration changes are made, reboot the AP/APCC (to immediately resynchronize AP with SNAPS server).
- Verify that you are using a supported browser.
- Verify that you have selected Plots as the display format.
- Verify that recipient is a valid user..
- Verify that the SNAPS user configuration is using valid email address.
- Verify that report was run and not just saved.
- If report was sent as a scheduled report, verify that delivery date and time have passed and that SNAPS server reflects the proper date and time.
- Verify that email account/server for the SNAPS have been set up. (Check with Sensys Networks.)
- Verify that your email server is up and running. (Check with IT department.)
Travel Time
- Verify Internet access.
- Verify that correct URL has been entered.
- Check that SNAPS IP address and DNS name is valid.
- Ping the SNAPS server.
- Check that browser is online (supported browser).
- Check the map settings elements (including accurate latitude and longitude coordinates).
- Check configuration settings for complete and correct information.
- Check the segments and links.
- Check the health of your APs in SNAPS.
- Check the health of your Sensors by running a Device Diagnostics report.
- Verify that there is sufficient traffic.
- Check the health of your APs in SNAPS.
- Check the health of your Sensors by running a Device Diagnostics report.
- Verify that there is sufficient traffic.
- Check the health of your APs in SNAPS.
- Check the health of your Sensors by running a Device Diagnostics report.
- Verify that there is sufficient traffic.
- Verify that the proper Travel Time AP Group was selected.
- Check configuration settings for complete and correct segment/link information.
- Check the historic health of the equipment by running a Device Diagnostics report.
- Verify that the browser being used is supported.
- Check AP Group (in SNAPS) for Travel Time inclusion.