Instruction manual

Example:

Let’s say we have two Loop sensors in a road, 10 feet from the leading edge. In the Phoenix II, we turn on Lane

#1 and Lane #2 and select Loop as the sensor.

A record of strikes might appear as such:

1:14:38:56 (3369138) P On

2:14:38:56 (3367017) P On

1:14:38:56 (3366577) P Off

2:14:38:56 (3364057) P Off

Now, what this means is that the Loop Sensor in Lane 1 was activated at 14:38:56 (2:38pm + 56 seconds) when

the timer was at 3,369,138. Lane 2 was activated when the timer was at 3,367,017. Lane 1 lost presence of a

vehicle when the timer was at 3,366,577. Lane 2 lost presence of a vehicle when the timer was at 3,364,057.

The question you might ask now is, “OK, so what’s the point?” Well, we know:

The distance (10 Feet)

The time from activating the first sensor to activating the second sensor, this is a 3,369,138 - 3,367,017 = 2,121

timer cycle.

Since we know the timer is running at 10,695 cycles per second, we can divide the number of cycles by the cycles per

second rate and get the amount of time, or 2,121/10,695 = .198317 seconds. Now, since distance = rate X time, then

rate = distance/time, or 10 feet/.198317 seconds = @50.42 feet per second. Using some conversions, this comes out to

about 34.4 Mph.

Since you know the loop length, and have calculated the vehicle speed, you could also calculate the length of the

vehicle. This is the exact process the Phoenix II used in Binned and Per-Vehicle (Raw) Modes.

If you were using tubes, you could calculate speed, number of axles, axle length between individual axles, and overall

axle length. Combine the two (using the option of Axle-Loop-Axle or Loop-Axle-Loop) and you can calculate everything

the tubes can, plus overall vehicle length. This is quite a bit of information from just a few timer counts.

As with other storage modes, during testing or collection you can monitor any or all lanes.