Phoenix II Automatic Traffic Recorder Classifier / Counter User Instruction Manual Version 3.2 Revised January 2012 For Firmware Versions 2.97 and above. Diamond Traffic Products P.O. Box 1455 76433 Alder Street Oakridge, OR 97463 www.diamondtraffic.com support@diamondtraffic.
FCC Compliance Note: This equipment has been tested and found to comply with the limits for Class B digital devices, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications.
Table of Contents Section 1 Introduction 1a. How to Use This Manual …………………………………………….. 1b. Communication with the Phoenix II ………………………………….. 1c. System Components ……. …………………………………………….. 1d. Features not available from the Keypad …………………………….. 1e. Loop Board Monitoring ….. …………………………………………….. 1f. Counter Firmware Configuration.…………..………………………….. 1 2 2 2 3 4 4 Section 2 Modes, Sensors, and how to use them 2a. Four Basic Storage Modes ……... …………………………………….. 2b. Sensors and Sensor Modes …….
c1. Questions Asked with Any Storage Mode …………….. 4c2. Lane Grouping Questions …………………………….. 4c3. Questions Asked with Raw Storage Mode …………….. 4c4. Questions Asked with Binned Storage Mode …….. 4c5. Questions Asked with Count Storage Mode …….. 4c6. Questions Asked with Sensor Storage Mode …….. 4c7. Final Start Questions …………………………………….. Delete Files …………………………………………………………….. Show Status …………………………………………………………….. Test Sensors …………………………………………………………….. Time of Shutdown ……………………………………………………..
Appendix D Default Bin Tables 65 Appendix E Road Tubes Problems and Solutions Appendix E1. Missed Axles …………………………………….. Appendix E2. Extra Axles …………………………………………….. Appendix E3. Bad Speed and/or Length …………………………….. Appendix E4. SnMis (Sensor Miss) for Entire Vehicle …………….. Appendix E5. One Vehicle Shown as Two …………………….. Appendix E6. Two Vehicles Shown as One …………………….. Appendix E7. Road Tube Setup that Does Not Cause Errors ……..
Introduction Thank you for purchasing Diamond Traffic Products Phoenix II Traffic Classifier Field Unit. You have purchased one of the finest advanced traffic classification recorders available today. This manual describes the operation and programming of the Phoenix II Field Unit. Please take the time to read and understand this manual in order to fully operate your Phoenix II unit to its full capabilities.
1.a. How to Use This Manual This manual completely describes the use of the Phoenix II. Not covered in this manual is programming & retrieving data from the serial port with a PC Computer. PC Interface operation is handled by the Centurion Software and covered by the Communication Protocol Documentation provided upon request. Q: Do I Have To Read The Whole Manual? A: Anybody using a Phoenix II should read all of Section 1, 2 and 3 of this manual.
Equipment required when using the Phoenix II Counter: You must have the following equipment in order to use the Phoenix II. All of this equipment can be purchased from Diamond Traffic Products as well as from several other sources. Sensors: You must have the appropriate type and quality of sensors (Loop, Piezo, Contact Closure, Road Tube, etc…) if using tubes, you will need nails and road tube grips to install road tubes. Computer: Ideally a PC computer with Microsoft Windows XP/Vista/Win7 installed.
Counter Serial Number: The counter contains a built in firmware serial number, which is set at the factory. This is included with all data files so that determining which counter collected that data can be easily identified. You can optionally set your own serial number using the Alt+F10 function from the main counter link screen in Centurion Software.
manufacturer (Diamond Traffic Products). The Phoenix II has flash upgradeable firmware and can be uploaded through the serial or USB ports via a PC computer either through direct connection or remotely via telemetry). Some firmware is made custom to certain customers that request different unit operation of defaults. These are denoted at the letter at the end of the firmware version (ex: 3.01w “w” = special settings for Washington DOT).
2. Modes, Sensors, and How to Use Them This section of the manual discusses the various ways the Phoenix II can collect data, and what types of sensors are required to collect each type of data. Please read this section carefully. The Phoenix II is a very sophisticated counter/classifier with many options. Reading and understanding this section first will greatly simplify operation later. Sensor Miss Code Definitions: SnMis #0 - Occurs only with Axle-Loop-Axle or Loop-Axle-Loop combinations.
2.b. Sensor and Sensor Modes The Phoenix II supports Road Tube Air Switches, Inductive Loops, Remote Inputs, Piezo Resistive and Piezo Electric Inputs. Road Tubes, Remote Inputs, and Piezo Sensors are considered “axle” sensors, since they are activated by individual axles. Inductive Loops are considered “presence” sensors, since they become activated by the metal in the vehicle passing over, and deactivate when the vehicle leaves.
Sensor and Count Modes always use the same lane number as the sensor number for input to that lane. Per-Vehicle (Raw) and Binned Modes will always use two inputs for each lane, with the sensor numbers shown in the table. Per-Vehicle (Raw) and Binned modes are the classification modes, so they can also take advantage of two slightly more complicated sensor modes, “Axle-Loop-Axle” and “Loop-Axle-Loop”. The first and last sensors, either the two Axle or the two Loop, are ALWAYS the same as shown in Table 1.
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.
Note that the directional lane is not an actual separate lane – it is the same physical lane but simply traffic moving in the opposite direction. It is recommended that the directional option be used whenever the possibility of two-way traffic exists, such as a one-lane road or an area on a two lane highway where there is much passing of slower vehicles, thereby using the oncoming lane. Four separate modes of Per-Vehicle (Raw) Storage are available.
IMPORTANT NOTE: You must make sure that for each road tube pair that the longer tube is always equal to or longer than the short tube in the pair when measures from the edge of the pavement closest to the counter. For example, when doing Same Direction road tube 3 (of pair 1 & 3) must be equal to or longer from the edge of the pavement to the counter than road tube 1 is from the edge of the pavement to the counter. The same is true for pairs 2 & 4.
2.e. Count Storage and Specific Functions In Count Storage Mode, the only information stored is the number of vehicles that have been detected in each lane. Up to 16 lanes are supported (depending on the number and type of sensors input boards installed) in this mode. Normally, each lane will use one sensor to collect the count. When a Road Tube or Piezo Sensor is used as the lane sensor, the count may be divided by two.
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.
3: Hardware This section describes the hardware components associated with the Phoenix II system. 3.a. Keypad The Phoenix II contains a built in 16-key keypad. With this keypad and the built in Liquid Crystal Display (LCD) you can program and operate the Phoenix II. When the ALT key is held down while you are pressing another key, an alternate set of keys is available to the user. The table below shows the alternate keys.
3.b. LCD Display The Phoenix II is equipped with a four line Liquid Crystal Display (LCD). Each line displays up to 20 letters or numbers. This display is used in conjunction with the keypad to program and operate the Phoenix II. You will see various questions and information displayed at different times. Please refer to the appropriate section of this manual for more information on specific questions and displays.
3.c.2 Auxiliary Serial Port (optional) An optional second or third serial port can be installed and utilized for counter communication for other purposes such as real time vehicle output via two standard formats. The serial ports are an optional component available with the WIM or Piezo cards and are installed during manufacturing or upgrading. The serial ports have the following features: Baud Rate communications from 300 to 115.
4) Turn on Phoenix II. The counter screen should display (after a self test): Counter is now initializing the modem. The counter will perform this step every time you hang up after a connection & automatically at midnight and 2 p.m. or a.m. of each day. Note: “Vx.xx“ is the current Phoenix II version number. 5) If everything is done correctly, the Phoenix II configures the modem and sets it properly. The counter will then display: Counter is now ready to accept incoming calls.
4) Using the Arrow Keys, select the speed of transfer you want to be able to call the counter at. Make sure it’s not faster than the modem can handle. 5) Keep pressing ENTER until you return to the main menu. 6) Follow the steps under Standard Modem Hook Up. Notes about switch settings If you are using a non-programmable dumb modem, all configuration of it is usually done through switch settings. Follow the below guidelines when setting these switches.
Follow these guidelines when using Tubes with the Phoenix II: The counter will work with road tubes between 20’ and 100’ (7 to 30 meters) long. Tube lengths 30’ to 60’ (10 to 20 meters) are generally more accurate so use these lengths when possible. Make sure the tubes are placed as squarely as possible to the oncoming traffic (so that both wheels of a vehicle strike the tubes simultaneously). After each use, check the tubes for punctures or other damage.
Note: If you are not familiar with installing Piezo Axle Sensors, please contact your Piezo manufacturer or contact Diamond Traffic Products for a Piezo installation guide. How to use Piezo Sensors with the Phoenix II Install the Piezo Sensors perpendicular to the oncoming traffic in a single lane. (SEE NOTE ABOVE) The Phoenix II defaults with a sensitivity of the Piezo Detection circuitry set to the most common value (52%).
3.e. Outputs Outputs are used to interface with external devices such as VMS (Variable Message Signs), static message boards, Traffic Controllers (170/2070 signal controllers), secondary data recorders, ITS devices (Intelligent Transportation Systems) and other useful roadside electronics. Although the Phoenix is self contained it is sometimes useful to connect and control other electronics to provide additional functionality. 3.e.1.
Phoenix II/ Unicorn/Pegasus 7 Pin Power Connector Pin Number Internal Wire Color Function #1 #2 #3 #4 #5 #6 #7 N/A N/A Green Blue White Green Black NONE NONE AC Input #1 Solar/12V DC Input User Voltage Output (6V) AC Input #2 GROUND 3.f.1. Power Loss Recovery Watchdog When the unit is in collection mode (collecting data) it is crucial that data collection continue even when power failures occur.
4: Keypad Operation This section describes the operation of the Phoenix II Field Unit using the built in keypad. For more information on operations using the serial port, please refer to the Centurion Software Help Menu. 4.a. How to Use the Menus The Phoenix II menu system has been designed so that only those options which may be needed at any particular point are available. Viewing the selection of an option from within a menu is a simple matter of using the arrow keys.
Time of Shutdown - Displays the Time and Date the system was last shut down (power turned off, not stopped the collecting time) View Lane Totals - This option displays the total number of vehicles (Raw & Binned) or sensor activations (Count & Sensor) since the data collection file was started. Configure System - Configure System allows the user to configure options such as Storage Mode, Date and Time Formats, File Handling, Speed and Length Formats, and Maximum Allowable Axle Spacings, etc.
You have used the configure system option to tell the counter what type of data you want to collect (Per-Vehicle [Raw], Binned, Count, or Sensor [Timestamp]). Note that if you have previously set the counter, you will not need to configure the system again as long as you plan to collect the same type of data, using the same setup. 4.c.1. Questions Asked With Any Storage Mode Enter the current Site ID, up to 15 characters long.
Enter the enabled lanes by pressing the corresponding number below the lane. For example, pressing the “1” key will toggle lane 1 on and off. You must enable at least one lane before proceeding. If no lanes are selected, the Phoenix II will display an error message and will not allow the user to go any farther until at least one lane is enabled. 4.c.2. Lane Grouping Questions The Phoenix II has the ability to group lanes together inside of the counter prior to storing them in memory.
Set this value to indicate the spacing in between your sensors. This can be set from 0.2 feet (6cm) to 99.9 feet. See Section 3.d (Sensors) for recommended spacing. This question is asked if you selected any combination that includes Loops in the Sensor selection screen. You must enter the Length of the loop used for this lane. If you have entered Loop-Loop, it is the length of the Second Loop. The Phoenix II uses this information in calculating vehicle length.
This question is asked if you selected any combination that includes Loops in the Sensor selection screen. You must enter the Length of the loop used for this lane. If you have entered Loop-Loop, it is the length of the Second Loop. The Phoenix II uses this information in calculating vehicle length. If you are doing length classification and the Phoenix is giving over or under lengths, use this value to correct the length. The following questions ask which bins you want to enable for data collection.
The Phoenix II will now display the message “Tuning Loops” followed by “Waiting for Any Vehicle”. Once a vehicle has passed and the data viewed is correct, press ENTER to continue. From here, the final start questions are asked. 4.c.5. Questions Asked With Count Storage Mode The following questions are asked for each lane you have enabled. Enter the appropriate information for this lane, up to 15 characters. This info is normally used to indicate lane direction. Choices are Axle or Loop.
4.c.6. Questions Asked With Sensor (Timestamp) Storage Mode The following questions are for each lane you have enabled: Enter the appropriate information for this lane, up to 15 characters. This info is normally used to indicate lane direction. Enter the sensor type for lane #n. Options are Axle-Only, Loop Only, or AxleLoop-Axle, Loop-Axle-Loop. The screen will display “Tuning Loops” if loops are selected, and them “Waiting For Any Sensor”.
4.d. Deleted Files The Delete Files option allows you to delete any or all files in the current memory. Press “2” from the menu and the display will show: Press ENTER to begin deleting files. If there have been no files created in memory, the counter shows: If files have been created, the display will show: “n” is the number of files currently resident is memory. By pressing the arrow keys the options of All Files, Single, or Retrieved may be selected.
4.e. Show Status The Show Status option allows display of the Phoenix II System Status. This should always be performed prior to Starting Collection to ensure correct time/date and that there is enough memory free to collect files. From the menu press “3” and the display will show: Press ENTER to show the status of the counter. If no loop boards are installed in the counter, the display shows: Displays the total amount of memory in your counter, and how much is left after use.
This screen shows the current voltage on the battery, to the nearest tenth of a volt. 4.f. Test Sensors The Test Sensors option is for testing sensors and system response. Press “4” from the menu and the display will show: Press ENTER to begin Testing Sensors. If no loop boards are installed in the counter, the display shows: The display is automatically set for eight axle sensors, and will indicate when a respective sensor has been activated.
To adjust using Centurion software select either Test Sensors or Monitor Lanes and select the Set Piezo Button. The display will show the following: These are the default settings: GAIN feature, key in #1 key. Gain has a range of 1-8 THRESHOLD press the #2 key; range is 5-255 TIME press the #3 key; range is 5-10K PERCENTAGE press #4 key; range is 5-95% When you have the desired feature displayed on the screen, key in the new desired number value.
This asks if you want to continue collecting data when the memory is full, or should the counter delete the oldest file to make new space for new data. If you select No the Phoenix II will stop collecting when the memory is full. The user may select to create new files Manually, Daily, or Weekly. Manually means that the counter will start a file when you manually start it and will close the file when you manually stop it. Daily means the counter will create a new file each day at midnight.
Select the voltage you want the counter to warn you that the battery is low. Use the left arrow key to decrease the voltage or the right arrow key to increase the voltage (default is 5.8). 4.i. View Lane Totals This option allows you to view the total amount of vehicles (Raw “Per-Vehicle” and Binned Storage Modes) or Sensor (Timestamp) activations (Count and Sensor Storage Modes) that have occurred from the last time you Started Collection to the last time you Stopped Collection.
The system has now been completely reset to the factory defaults. 4.k. Stop Collecting Stopping data collection command is the only way to return to the Start Collecting Data Menu. Press 1 from the menu and the display will show: Press ENTER to select the option. Use the arrow Keys to toggle to Yes. Pressing ENTER will close the current file. “n” is the file number. Pressing ENTER again will return the user to the Start Collecting Data Menu. 4.l.
While monitoring, you may press the following keys: 1-8 – Tells the counter to only display the lane number you press. 0 – Tells the counter to display all lanes. CLEAR – aborts and returns to the menu. SPACE – Freezes the display. This allows you to view a vehicle for a longer period of time. Press SPACE again to un-freeze the display. ALT 1-8 – You can set piezo sensitivity levels with the counter keypad keys. See section 4.f for more information. ARROW KEYS – Allows you to see other spacings.
5: Keypad Operation Examples The following section provides seven examples using the keypad of the Phoenix II. The first six give examples of setting up the counter to collect Raw Data, monitoring Data, stopping Collection, and Collecting Binned, Count and Sensor Mode data. The last one is an example of Deleting Files. Note that these examples are not complete descriptions. You should refer back to Section 4 for more in-depth information. As the examples are worked through, files will be created in memory.
Select the required mode (Raw, Binned, Count, or Sensor) by using the arrow keys; Press ENTER. Which mode you select depends on which of the following examples you are using. Select this format by pressing ENTER, or select a different format with the arrow keys and then press ENTER. Since we want the counter to stop when memory is full, press ENTER to select No. The user may select to create new files Manually, Daily, or Weekly.
This Setting is used when two or more units are connected to the same modem or communication line. Typically used in larger sites where two units are needed in the same location. 0=disabled, 1=Master, 2-16=Slave or client. (See Section 3c4 for more details) This allows the user to modify the contrast on the counter LCD to be darker or lighter and toggle between the 16x2 and 20x4 display modes. This will enable the counter to write any temperature changes into the recorded data file.
Note the position of the cursor in the first digit of the time. Start entering the time with hour, minute, and then second. For example, 3:30pm would be 15:30:00 and zero seconds. Press ENTER when done. Note once again the position of the cursor & that the date is in the format set in Configure System. Enter the date, and press ENTER. Use the arrow keys to toggle to the correct day. Press ENTER when done. Press the number on the keypad which corresponds to the lanes you want to turn “on”.
The asterisk (*) means no data is being stored yet. Wait for vehicles in both lanes two pass, and if data is correct, press ENTER. Since we want to start collecting right now, press ENTER. Since we are running a test file, press ENTER. Press the ENTER key. The counter is now collecting data as vehicles pass. The display should be blank. Raw (Per-Vehicle) data collection has started. After a few vehicles have passed you may want to try the Stop Collecting Example (5.
Note once again the position of the cursor & that the date is in the format set in Configure System. Enter the date, and press ENTER. Use the arrow keys to toggle to the correct day. Press ENTER when done. Press the number on the keypad which corresponds to the lanes you want to turn “on”. n = not collecting y = yes collecting. Use the keypad to enter the direction or some other piece of information about the lane, for example: Eastbound Press ENTER when done.
Leave this at No by pressing ENTER. Leave this at No by pressing ENTER. Leave this at No by pressing ENTER. Leave this at No by pressing ENTER. Select the Record Interval length; this should remain at 00:15, so press ENTER. At this point, the next vehicle to cross the Axle Sensors will show as a test vehicle. The first vehicle to cross in lane # 1 will show something like below. The asterisk (*) means no data is being stored yet.
5.d. Collecting Count Data This section will give an example of collecting Count Data. Use Example 5.a first to configure the system to collect Count Data. After that example, the display should show: Press ENTER. Note the blinking curser on the character line. Use the keypad (section 3.a.) to enter in a site ID, for example HWY 58. Press ENTER when Done. Optionally enter a line of information, for example: “System Test” or GPS coordinates (Lat) can be entered here.
Since we have set our road tubes for lane subtraction, change this to Subtraction with the arrow keys and press ENTER. To change selection use the arrow keys, using No as default. Press ENTER when done. Use the keypad to enter the direction or some other piece of information about the lane, for example: Westbound. Press ENTER when done. Choose the sensor type to be used, Choose Axle for Road Tube setup. Press ENTER when done. To change selection use the arrow keys, using No as default.
5.e. Collect Sensor (Timestamp) Data This section will give an example of collecting Sensor (Timestamp) data. Use Example 5.a. first to configure the system to collect Sensor Data. After that example, the display should show: Press ENTER. Note the blinking curser on the character line. Use the keypad (section 3.a.) to enter in a site ID, for example HWY 58. Press ENTER when Done. Optionally enter a line of information, for example: “System Test” or GPS coordinates (Lat) can be entered here.
Use the keypad to enter the direction or some other piece of information about the lane, for example: Westbound. Press ENTER when done. Choose the sensor type to be used, Choose Axle for Road Tube setup. Press ENTER when done. At this point, the next vehicle to cross the tubes will show as a sensor activation and will look something like below: The asterisk (*) means no data is being stored yet. Wait for sensor activations in both lanes, and if data is correct, press ENTER.
Press ENTER to select option. The next screen depends on the type of data you are collecting, for Raw (Per-Vehicle), and Binned you will see: When the next vehicle data is collected, the display will show the vehicle on the Screen. If you are collecting Count data, your screen will show something like: The actual lane numbers and totals depend on your current setup. As each sensor is activated the new totals for that lane are displayed.
This informs you that no WIM (weight in motion) board is installed and that an MMC (multimedia card – Flash Memory) is not present. Press ENTER when done. Shows the current military time and date. Press ENTER. This is the battery voltage status message. It will tell you if your battery is getting to low. Press ENTER. You have completed the Show Status Option. Press CLEAR. The display will go blank. The Phoenix II is still collecting data and is now in a low power sleep mode. DO NOT turn off the unit! 5.g.
5.h. File Deletion If all the examples have been followed, several files will have been created in memory. You may remove unwanted files, using the Delete Files Option, available from either “Collecting or Not Collecting” Menu. If the system is in sleep mode, press ENTER to wake the counter up. The display will show: Press the arrow (or press “2”) until the display shows: Press ENTER to select the option. This example shows that there are 4 files in memory.
5.i Collecting Data Using Lane Grouping This section will show you how to enable the Lane Grouping function to collect Grouped Count Data on four lanes. To collect grouped binned data, simply change the storage mode. First, follow example 5.a to configure the system to collect Count Data. Stop when you get to the following question in the Configure System option. Press right arrow to select Yes then press ENTER to continue. Follow through the remainder of 5.a to finish the system configuration.
6: In-day Times The Phoenix II has a special function called In-Day Times. In-Day Times are time periods in the day that you wish to Start and Stop collecting data. This is similar to the Daily files function, except you can Start and Stop collection at several different times during a 24 hour period. The basic purpose of this function is to handle very large data collection requirements where you only have enough memory in the counter to store part of a day.
Appendix A. Trouble Shooting This Section is intended as a guide towards installation troubleshooting. It is in no way intended for the service or repair of any type of the Phoenix II system. Some basic problems can always occur during operation. Generally, they will be some small error in setup or sensor installation. Listed below are some basic problems and possible solutions.
Appendix B. 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 II field unit may collect data before retrieval of data files. Note that this is only a guide. It is recommended to retrieve data as often as is practical from the units and deleting retrieved files from the memory. Different configurations may store different amounts of data.
Appendix B.2 Binned Data Collection Binned data stores data as the total number of vehicles in each bin category in every record interval. The three most important factors are: which bin categories are enabled, what the record interval length is, and how many lanes are enabled. Follow the steps below to calculate how long your Phoenix II can collect data with any given setup. Using the table below, calculate the base number of bytes in a single record period, for a single lane.
1. 2. 3. 4. 5. 6.
Appendix B.3 Count Data Collection Count data stores the total number of vehicles or the total number of axles that have crossed the sensors for a given time period. The two factors to consider are: how many lanes are enabled, and what the record interval length is? Follow the steps outlined below to calculate how long a Phoenix II will collect count data into memory: Multiply the total number of enabled lanes by 2. Add one to the number. This is the Total number of bytes per record interval.
Appendix C. Plugs & Connectors This section describes the physical hardware connections for connectors on the Phoenix II. Note that the Unicorn, Phoenix II, & Pegasus all use identical and interchangeable (in most cases) connectors.
Phoenix II/Unicorn/Pegasus 25 Pin Female Serial Interface Cable Phoenix II/Unicorn/Pegasus 9 Pin Connector (front view) #7 – Receive Data (RXD) #6 – Carrier Detect (DCD) #5 – Data Terminal Ready (DTR) #4 – Ready To Send (RTS) #3 – Serial Port Enabled (ENA) #2 – Signal Ground (GND) #8 – Transmit Data (TXD) #9 – Clear To Send (CTS) 25 Pin Female Sub-D Connector #2 – Transmit Data (TXD) #20 – Data Terminal Ready (DTR) #6 – Data Set Ready (DSR) #8 – Carrier Detect (DCD) #5 – Clear To Send (CTS) #1 – Frame Gr
Phoenix II/Unicorn/Pegasus USB connector 4 Pin USB Female “B” Panel connector (front view) 4 pin Male USB “A” Side (PC side) Phoenix II/Unicorn/Pegasus 25 Pin Male Modem Interface Cable Phoenix II/Unicorn/Pegasus 9 Pin Connector (front view) #7 – Receive Data (RXD) #6 – Carrier Detect (DCD) #5 – Data Terminal Ready (DTR) #3 – Serial Port Enabled (ENA) #2 – Signal Ground (GND) #8 – Transmit Data (TXD) 25 Pin Female Sub-D Connector #3 – Receive Data (RXD) #8 – Carrier Detect (DCD) #20 – Data Terminal Rea
NOTE: On the Phoenix II/ Unicorn/Pegasus 9 Pin connector, pins #9 and #4 are shorted together and have no wires inserted, pin #5 and #6 are shorted together, pin #1 is not used, the RTS (#7) and CTS (#8) wires from the 9 Pin Sub-D are soldered together and then sealed with heat shrink tubing, and pin#2 gets two wires.
Phoenix II/Unicorn/Pegasus 4 Input Piezo Electric Harness Cable Piezo Electric Input Number Wire Pair (Black is Ground) #1 #2 #3 #4 Red/Black White/Black Green/Black Blue/Black Phoenix II/ Unicorn/Pegasus 7 Pin Power Connector Pin Number Internal Wire Color Function #1 #2 #3 #4 #5 #6 #7 N/A N/A Green Blue White Green Black NONE NONE AC Input #1 Solar/12V DC Input User Voltage Output (6V) AC Input #2 GROUND The following diagram shows the pin numbers of the Phoenix II/Unicorn/Pegasus 7 Input Conne
Appendix D. Default Bin Tables This appendix describes the default bin categories that are used with the Phoenix II. These “Bins” are used to total up all vehicles meeting a predetermined set of criteria. Note that this information is ONLY used if you configure the Phoenix II to collect data in its Binned Mode. Raw (Per-Vehicle), Sensor (Timestamp), and Count Modes do not Bin data. Default Axle Bin Classification Table (Scheme- ‘F’) (defaultx.
Appendix E. Road Tube Problems & Solutions This appendix discusses the various problems that road tubes can cause. Road tubes present their own unique set of problems for automatic vehicle classifiers & counters. Being aware of these before installing your road tubes can greatly reduce the frequency of these errors. This appendix divides each problem (or “error”) into a separate section, and then lists the known causes of the problem. Appendix E.
3) The first axle is detected with no problem. 4) The second axle (the first axle of the first tandem pair) hits the road tube. This causes FOUR sound waves to be generated, TWO from each tire. 5) The Left Tire will send two sound waves from it (1 in each direction) and the Right Tire will send two waves from it as well.
Appendix E.2 Extra Axles This error, while not frequent, does happen. It is almost always a problem with the actual road tube installation, or with the road surface. Causes of extra axles are listed below: Road Tube Bounce (slap). Since the road tubes are made of flexible rubber, they move when they are hit.
Appendix E.5 One vehicle Shown as Two This error is normally caused by a vehicle with an axle spacing greater than the maximum axle spacing setting in the configure system option. The counter defaults to 40.0ft. This value can be changed in the unit by the user if needed. If you increase this value, you run the risk of counting vehicles traveling close together as one vehicle (two tailgating cars become one vehicle, usually turned into a four axle Class #8 under Scheme-F).
