Instruction manual

Copyright ©2006 Diamond Traffic Products
ALL RIGHTS RESERVED
9
Table 4 – Example 2
Mode
Lane 1
Lane 2
Axle-Loop-Axle
Axle 1,Loop 1, Axle 2
-------------------
Loop-Loop
-------------------
Loop 3, Loop 4
Now, there is no conflict and the system can operate. When the system does detect a sensor conflict with another lane
(and note that the higher number lane will always be the lane in conflict, so lane # 1 will never be in conflict since it is the
lowest lane number), you will receive an error message and the software will not continue operation.
The Phoenix II also contains many advanced sensor analysis routines to improve data accuracy, including examining
both sets of axle and presence sensors, the tossing out of too short spacings ( for example: eliminating a road tube
bounce, which can cause a false count), and the determination of missed axles.
Dynamic Sensor Assigning:
Since the Phoenix II uses sensors in a certain order depending on setup, sometimes your configuration is limited by the
default assignment of sensors or hardwiring. To accommodate unconventional sensor inputs, the Phoenix II allows for
the sensors to be rearranged or reassigned to different inputs. This feature is only available during serial port
programming via the PC. The assignment of sensors is done by lane and is done using the Centurion software.
Sensors can be assigned to any lane in any combination with the exception that the sensor is not assigned more than
once.
As an example you may have a site that was wired incorrectly and cannot be rewired easily. In this case it may be
easier to just reassign the sensor inputs to allow the unit to count or classify traffic correctly. In the following table the
scenario represented would be that of a site that was “wired” backwards. By reassigning the sensor inputs we have
allowed the lane assignments to appear correctly:
Before Reassignment
After Reassignment
Sensor
Lane
Sensor
Lane
Axle 1
5
Axle 1
1
Axle 2
6
Axle 2
2
Axle 3
7
Axle 3
3
Axle 4
8
Axle 4
4
Axle 5
1
Axle 5
5
Axle 6
2
Axle 6
6
Axle 7
3
Axle 7
7
Axle 8
4
Axle 8
8
2.c. Per-Vehicle (Raw) Storage and Specific Functions
In this mode, an individual record is kept for each vehicle encountered. Any combination of one to eight lanes
(depending on how many and what type of sensor inputs the boards are installed) can be enabled. If any lane is
configured for directional mode (the ability to classify traffic travelling in either direction), an additional lane of traffic data
is created. For example, if lane # 1 is enabled and is configured in directional mode, the counter would create lane # 9
for vehicles traveling in the opposite direction on lane # 1.
Physical Lane
Opposite Lane Direction
Lane #1
Lane #9
Lane #2
Lane #10
Lane #3
Lane #11
Lane #4
Lane #12
Lane #5
Lane #13
Lane #6
Lane #14
Lane #7
Lane #15
Lane #8
Lane #16