What is a Phoenix Field Unit?
The Phoenix is a data gathering instrument for use in the field (roadway). By using the Phoenix and one of several possible combinations of sensors, traffic data and vehicle classification can be recorded and later retrieved. Speed, Length, Number of Axles, Vehicle Class Type are just a few typ ...
- Phoenix II Features & Specifications
The Phoenix II is a stand alone unit that is designed to work with sensors to detect and classify vehicular traffic on interstates, highways and roads. Robust military specification connectors provide easy wiring of sensors, inputs and outputs of the Phoenix II unit. The Phoenix II comes with ...
- Real Time Clock Adjust During Collection (UPP Series)
Command available in UPP 4.16 and 4.56 and higher Firmware. When subtracting minutes from the clock – This function causes the counter to reset the clock back one minute at the beginning of each new minute for the duration of time you specify. For example, if you tell it to subtract 10 ...
- Modes, Sensors, and How to Use Them
Overview Below we discuss the various ways the Phoenix MDK can collect data, and what types of sensors are required to collect each type of data. Please read this section carefully. The Phoenix MDK is a very sophisticated counter/classifier with many options. Reading and understanding this secti ...
- Memory Usage
Each mode uses a different amount of memory for storing traffic data. This appendix is intended to give the user an approximation of how long a Phoenix MDK Field Unit may collect data before retrieval must be performed. Note that this is only a guide – it is recommended to retrieve data a ...
- Naming conventions and Station ID’s used in Centurions Database.
It is important to note that the Station ID referenced in Centurion’s Database is the Same Site ID that is referenced in our counters and classifiers. Each Location that you collect data from needs to have a unique name that can NOT be used elsewhere for data collection purposes. If you ...
- Piezo Termination for UPP units.
Terminating Piezo sensors usually is done one of two ways. Either the termination is done using a terminal block and then connected to the counter using the UPP piezo harness or by individual BNC connectors. With the Terminal strips the wiring must be done on site to "land" the piezo sensors ...
- Phoenix Technical Specifications
Features Count 1 to 16 lanes Count methods include direction, lane subtraction and normal Classify 1 to 8 lanes Possible sensor arrangements per lane for classification: Two Axle sensors Two presence sensor Two axle sensors and one presence sensor Two presence sensors and one axle sens ...
- Trouble Shooting - The Phoenix MDK
Some basic problems can occur during normal operation of your Phoenix MDK. Generally, they are caused by some small error in setup or sensor installation. Listed below are some basic problems and possible solutions. If you cannot solve an installation problem, or if you find a new solution to a ...
- Default Bin Tables - Pegasus, Phoenix and Unicorn MDK
Overview The tables below describes the default bins categories that are used with the Pegasus, Phoenix and Unicorn MDK units. These “Bins” are used to total up all vehicles meeting a predetermined set of criteria. Note that this information is ONLY to be used if you are seekging ...
- Using the Phoenix MDK with a Modem
Overview All Phoenix MDK counters come fully operable for use with a modem. You will need some type of telephone communication package to access the counter through the modem. Diamond Traffic Products offers our Centurion Gold for Windows® Telemetry software. The features include: Dis ...
- What units are compatible with Centurion?
The following is a list for known compatibility: Apollo: All Versions DataHog: 1.50+ Pegasus: 2.39 - 2.45 Phoenix: 2.39 - 2.45 Unicorn: 2.39 - 2.45 Unicorn Limited: All Versions Sprite: 1.40+ Trail Counter: All Versions Some older units can be upgraded to be compatible with Centurion. Contact u ...
