Instruction manual

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. Weekly means the counter will create a new file once per

week.

If you select Weekly files, you will be asked:

Select the day of the week that should become the FIRST day of your weekly file.

Choices are Sun, Mon, Tue, Wed, Thu, Fri, or Sat. The file will start at midnight.

This option tells the counter the baud rate a modem connected to it can

send/receive data at. For example, if you are connecting a Hayes Smart modem

2400 to the counter you should set this value at 2400. YOU HAVE TO CALL

THE COUNTER AT THIS RATE! You can change the rate for future calls by

using a communications package such as Centurion Gold and programming the

counter to accept future calls at a different rate. Your choices are 300, 600, 1200,

2400, 4800, 9600, 19200, 33600, 57600, and 115.2K.

This option enables or disables the Lane Grouping Function. If you select No,

then Lane Grouping is disabled and the counter will not ask questions pertaining

to it in the Start Collecting option (see Section 4.c.2.)

The Following configure questions are only asked if either Binned or Raw Storage has been selected.

Requests either U.S. feet and MPH, or Metric centimeters and KPH Format. The

Phoenix II operates in Metric and converts into feet and inches. This Conversion

can occasionally result in numerical values you key in to be displayed 1/10 of a

feet different due to rounding.

This option is used to select what the counter should do with sensor miss

information. Sensor misses occur when a vehicle does not cross both sensors or

fails to trip a sensor (see lid instructions on Phoenix II field unit for a description of

each sensor miss code).

View only will display sensor misses on the screen when monitoring, but

will not store these misses to memory.

View and Store displays the misses and stores them into memory for

later retrieval. Note that storing sensor misses in memory does use up

memory that could be used for data.

Disabled causes the counter to ignore sensor misses.

This option determines the longest spacing between any two axles to be allowed

when collecting Raw or Binned data using two axle sensors. The counter uses

this length to determine where the end of a vehicle is, and starts looking for the 1

axle of a new vehicle. Most trucks in the U.S.A. do not exceed 40’ between axles,

and on the highway, most vehicles do not travel closer than 35’ to each other.

The Phoenix II has mathematical algorithms that look for one or more tailgating

cars and place them in Bin 2.

The following is always asked regardless of storage mode: