ADR Sabre
ADR Sabre
™
ADR SABRE
Automatic Data Recorder
Operating Manual
ADR Sabre
Automatic Data Recorder
10/29/2013
p/n: 99-585 Rev 1
Contents
Information furnished here is believed to be accurate and reliable, however Peek Traffic does not warranty
the accuracy, completeness, or fitness for use of any of the information furnished. No license is granted by
implication or otherwise under any intellectual property. Peek reserves the right to alter any of the
Company's products or published technical data relating thereto at any time without notice.
No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or
via any electronic or mechanical means for any purpose other than the purchaser’s personal use without
the expressed, written permission of Peek Traffic Corporation.
Trademarks
ADR Sabre is a trademark of Peek Traffic Corporation, in the USA and other countries. Idris and Idris
Products are registered trademarks of Diamond Consulting Services, Ltd. Microsoft and Windows are
trademarks or registered trademarks of Microsoft Corporation. Other brands and their products are
trademarks or registered trademarks of their respective holders and should be noted as such.
WARNING:
This equipment generates uses and can radiate radio-frequency energy, and if not installed and used
properly as described in the product manual, may cause interference to radio communications. It has been
designed to comply with the limits of a class A computing device pursuant to Subpart J of Part 15 of FCC
rules, which are designed to provide reasonable protection against such interference when operated in a
commercial environment. Operation of this equipment in a residential area is likely to cause interference, in
which case, users, at their own expense, would be required to take whatever measures may be required to
correct the interference.
TABLE OF FIGURES
Assumptions
This manual makes these assumptions about the installation environment and the
personnel who will be operating the ADR Sabre:
The installers and operators of the ADR Sabre are field qualified to work in and
around traffic recording sites and have been approved for such actions by the
local/regional traffic regulating agency.
The personnel who will be installing and operating the equipment are familiar
with and will follow all necessary work-site and public safety procedures when
installing and using the equipment.
Related Documents
These documents provide additional information which may be useful during the
installation and operation of an ADR Sabre:
Table 1 – Related documentation
Title p/n
Getting Started with ADR Sabre 99-587
Release Notes 99-584
Tech Note - Recording Event Files for Reuse, Post-collection 99-595
Technical Assistance
If you need assistance or have questions related to the use of this product, contact
Peek Traffic Customer Service.
The following conventions are used in this manual to convey and underline certain
types of information.
Typographic Conventions
Whenever the following fonts or symbols are used, they indicate a specific situation or
meaning as noted.
Table 2 — Typographic conventions used in this manual
Description Example
Menu items or parameter values On the arrays menu line, select Fwd.
that must be selected by the user
appear in bold.
Some keypad keys are indicated by When finished selecting the desired
BOLD CAPS. parameter, press the ENT key, or the
ESC key to revert to previous setting.
Some device keypad buttons are Press the ← key to select the <config>
indicated with symbols, such as: menu.
← left arrow key Press the ↑ or ↓ key to select the array
→ right arrow key type.
↑ up arrow key
↓ down arrow key
Symbol Conventions
The following symbols are used in this manual to indicate a raised level of notice for
the accompanying text in the context of the associated topic or steps.
Table 4 — Symbol conventions used in this manual
Symbol Description
Note – indicates a pointer or tip concerning the current topic or step.
This chapter introduces the ADR Sabre. The following topics are discussed in this chapter:
Sabre features, p. 14
Sabre connectors, p. 15
Ancillary Hardware Options, p. 16
Array selection options, p. 19
The ADR Sabre Automatic Data Recorder is a portable, easily configurable, and
comprehensive automatic vehicle count and classification (AVCC) device. The Sabre
has advanced recording features, accurately collects a variety of vehicle study data,
and supports a range of sensor technologies.
Additional connector
port location (unused)
Figure 3 – Back of Sabre with connectors (example)
GPS Connector cable (p/n 81-933): Use to connect a GPS device to ADR Sabre
RS-232 port.
Street-Link™
Street-Link (p/n 81-xxxx) is a portable, hand-held interface device; use it to check the
Sabre device status (battery level, free memory, and road tube input connections and
operation), or provide the GPS location and/or satellite time sync to the Sabre.
On LED
Connected LED
Power On/Off button
Low Battery LED
Memory LED
Security
A lock and a set of keys are supplied with the ADR Sabre. Use the lock and a chain to
lock the unit to a secure post, pole or bridge when you use the Sabre for unattended
studies. One method is to wrap the chain around the post, drop both ends of the
chain through the ADR handle, and then bring one end of the chain to the left, the
other to the right, around to the front of the Sabre and hook the lock through the left
chain end, then the right chain end, then the Sabre hasp, and then lock the lock.
Remember to take the keys, and keep them in a secure place.
Road Tubes
Road tubes can provide great flexibility and portability for traffic studies, as
permanent, involved installation is not necessary. The array below uses two wider
spaced tubes, and can provide data on vehicle speed, class, length (wheelbase),
volume, headway, or gap, by direction (channel), or a combination of these.
Loops
The inductive loop used for vehicle detection provides greater accuracy for vehicle
presence than a road tube. The array below uses a single loop per lane, and can
provide data on volume, headway, or gap, by lane, or a combination of these. You
can use up to 16 one-loop lane arrays with the Sabre.
Piezo (Axle)
In many applications the piezo array is installed where it is desirable to collect data
that is directly comparable to historic road tube counts, but on a permanent or long
term basis. The array below uses two single piezo arrays, one in each of two lanes,
and can provide data on volume, headway or gap by lane, or a combination of these.
You can use up to 16 one-piezo arrays with the Sabre.
loop inputs, respectively, setting up and utilizing the arrays accordingly – see “Loops”
and “Piezo (Axle)” headings above.
Weight-in-Motion (WIM)
Weight-in-Motion (WIM) arrays are those arrays used for the collection of Weigh-In-
Motion data with the Sabre, and typically use a “class 1” piezo sensor which has been
certified by the manufacturer for accurate linear response along its length.
Hybrid (Mixed)
Combined sensor arrays are used to take advantage of the strengths of each sensor
and provide improved accuracy of data. The array type below uses two axle (piezo)
sensors flanking a loop sensor, and can provide data on speed, class, length
(chassis), volume, headway, gap, or direction by lane, or a combination of these.
Using this array, the Sabre can measure speed very accurately and can then
determine classification by axle spacing and wheelbase.
A
D
Figure 16 – RExample - Axle-Loop-Axle arrays diagram
This chapter describes how to get started using the ADR Sabre. The following topics are
discussed in this chapter:
INITIAL STEPS
Wakeup LCD
Press any key on the keypad to “wake up” the Sabre LCD (the screen goes blank
after a set time to preserve battery). The LCD initially displays the startup screen:
FW: 01.02_275-Mar_27_2013-08:12:57
240 T45
Status Beacons
Status Beacons: A – Always on, low level, when ADR Sabre is not asleep
B – B flashes on, bright, every 60 sec. (watchdog) when the
Sabre CPU’s operation is normal.
FW: 01.02_1275-MAR_27_2013-08:12:57
240 T45
With the startup screen displayed, use the keypad to do the following:
Sleep Timeout – Default LCD timeout is 60
seconds, after which, if no keys have been
pressed, the screen goes blank. To increase
timeout count (max. 300 sec.), press and
hold the ↑ key (from the startup screen
only). Count resets to the new value upon
any keystroke; if a timeout occurs, the Sabre
reverts to 60 sec. timeout upon wakeup.
DST
On
Date and PEEK TRAFFIC ADRsabre
Time Wed Apr 17,2013 16:01:59 DST
IDLE
Firmware FW: 01.02_275-Mar_27_2013-08:12:57
version 240 T45
LCD
Contrast Timeout
setting Count
Figure 19 – The ADR Sabre LCD and startup menu
Note Date and Time: Check the date and time on the startup screen. If time
and/or date are incorrect, see “Set Date, Time, and DST,” p. 33.
Battery Check
To quickly check the battery level, press the ← or → key on the keypad to select the
<status> heading on the Setup menu. Read the voltage on line 1):
Battery <CONFIG><SITE><STUDY><FILES><status>
voltage 0) SN-330033001547303439310000
1) 6.21V 009.2mA 001mA 000mA +073.5F
2) COUNT_MON_01 00000 00000 00000 00000
3) pvr_mon >
Note To return to the Startup Screen from the Setup menu, from the
top headings, press the ESC or BACK button on the keypad.
For more information on navigating the setup screen – see the next section.
Note Never begin a study if battery level is at 6.0 v or less. This may allow
the ADR Sabre operation to stop before study completion. Instead,
recharge the battery first (see “Recharging the Battery,” p. 138).
SETUP MENU
To setup traffic studies, you will use the Setup menu. From the Startup menu (see
Figure 19, p. 26), press the ← or → key on the keypad to enter the Setup menu:
<config><SITE><STUDY><FILES><STATUS>
0) LANGUAGE-ENGLISH
1) DATE-Mon May 14, 2012 16:46:29 DST:On
2) COMMS-UsbDev:O Rs232:115200
3) COMM_ID–00001
043T
Figure 21 –Setup menu (“config” content shown)
Note To return to the Startup Screen from the Setup menu, from the
top headings, press the ESC or BACK button on the keypad.
<CONFIG><site><STUDY><FILES><STATUS>
<site> content
Press ENT or the ↓key to advance through listings, or press the number (such
as 1, for arrays) for a specific item line:
1) arrays is
selected <CONFIG><site><STUDY><FILES><STATUS>
0) SITE-000000000000000 STA-1111111111111111
1) arrays Loop L 02 Ln/s Fwd >
2) GPS-Lat:00d00,000’ Lon:000d00,000’
3) CTREE-FHWA_USA defADR3 HiBit 051508
Setting Parameters
Press ENT or the ↓key to advance through listings, or press the number (such as 1,
for arrays). Once a line is selected, such as 1) arrays, set parameters – for example:
1. Press ENT or the ← or → keys to select a menu line item, such as arrays
type (Tube, Loop, etc.). When you select a parameter, it blinks:
arrays line is
selected Loop is selected
<CONFIG><site><STUDY><FILES><STATUS>
(blinks)
0) SITE-000000000000000 STA-1111111111111111
1) arrays Loop L_L 01 Ln/s Fwd >
2) GPS-Lat:00d00,000’ Lon:000d00,000’
3) CTREE-FHWA_USA defADR3 HiBit 051508
Note Changing some settings, such as arrays type (Tube, Loop, etc.),
causes other parameters to change accordingly.
Tip: After selecting a value, you press the ENT or ← and → keys to move to
another field and register the change, or press ESC to revert to the prior setting.
Alpha-numeric entries – In some fields, you enter alpha-numeric digits – such as for
the SITE or STA fields (site and station names) on the <site> menu:
Move along character places using arrow keys, ↓ = left, ↑ = right, or hold the
SHIFT key and then press ← or → to move left or right along the places. The
parameter characters all blink, except for the current place selected:
Alpha-numeric
<CONFIG><site><STUDY><FILES><STATUS> entries
0) SITE-MainSt00000000 STA-1111111111111111
Current place 1) arrays Tube T_T 02 Ln/s Fwd >
selected 2) GPS-Lat:00d00,000’ Lon:000d00,000’
3) CTREE-FHWA_USA defADR3 HiBit 051508
<CONFIG><site><STUDY><FILES><STATUS>
0) SITE- Hwy_23_at_0000 STA-1111111111111111
1) arrays Tube T_T 02 Ln/s Fwd >
2) GPS-Lat:00d00,000’ Lon:000d00,000’
3) CTREE-FHWA_USA defADR3 HiBit 051508
<CONFIG><SITE><STUDY><files><STATUS>
0) M0: 0139MB-0150MB_00512-27859-30724 R *
1) USB:Off
2) STUDY:None
3) EVT:12151527=00005757 Evts
Battery <CONFIG><SITE><STUDY><FILES><status>
voltage 0) SN-330033001547303439310000
1) 6.21V 009.2mA 001mA 000mA +073.5F
2) COUNT_MON_01 00000 00000 00000 00000
3) pvr_mon >
Date and time settings may be incorrect on occasion. As a practical example of using
the Sabre menu, here’s how to set the date, time, and daylight savings time (DST):
1. On the Setup menu, select the <config> heading.
<config><SITE><STUDY><FILES><STATUS>
0) LANGUAGE-ENGLISH
1) DATE-Tue May 15, 2012 16:46:29 DST:On
2) COMMS-UsbDev:Off Rs232:115200
3) COMM_ID–00001
Figure 36 – <config> heading contents
2. Select 1) DATE by pressing “1” on the keypad.
<config><SITE><STUDY><FILES><STATUS>
0) LANGUAGE-ENGLISH
1) date-Tue May 15,2012 16:46:29 DST:On
2) COMMS-UsbDev:Off Rs232:115200
3) COMM_ID–00001
Figure 37 – Select 1) date
3. With date selected, press the → or ENT key to select the month field. Press
the ↑or ↓ keys to change the month. Press ENT to enter the setting and
select the next field. Or press ESC to exit the field without changing.
<config><SITE><STUDY><FILES><STATUS>
0) LANGUAGE-ENGLISH
1) date-Wed Jun 26, 2013 16:46:29 DST:On
2) COMMS-UsbDev:Off Rs232:115200
3) COMM_ID–00001
Figure 38 – Set date
4. Likewise, use the arrow keys to select and set the day of month, year, and
time (HR:MIN:SEC).
The day of week (Mon-Sun) displayed is set automatically when the rest of
the date is set, and is not manually selectable.
5. Set DST (On or Off, or Set). With DST on, the Sabre automatically adjusts
for daylight savings time (according to DST settings; see next step).
Note DST automatically sets the time one hour ahead at the DST start
time, and one hour back at end time.
6. To set the DST start and end times, select DST: Set, then ENT. This
displays the DST_START and DST_END (date and time). Press ENT to
select and the ↑or ↓ keys to set the parameters:
WK DOW MON HR
0) dst_start -04 Sun Mar 02
1) DST_END -01 Sun Nov 02
<config><SITE><STUDY><FILES><STATUS>
0) LANGUAGE-ENGLISH
1) date-Mon May 14, 2012 16:46:29 DST:On
2) COMMS-UsbDev:Off Rs232:115200
3) COMM_ID–00001
This chapter using the communication ports on the ADR Sabre. The following topics are
discussed in detail in this chapter:
You can easily operate the Sabre as a standalone device, without any connection to a
PC or network. Nonetheless, the Sabre has an RS-232 serial port, and USB micro B
(“Device”) port for connecting a PC or other devices to the Sabre. There is also a slot
for USB memory devices (jump drives) for transferring data and setup files.
RS-232 Port
The eight-pin Sabre RS-232 port connector is located on the rear of the Sabre (the
same connector is used for attaching power supply/charger). Use the RS-232 serial
port and suitable connector cable device (see “Ancillary Hardware Options,” p. 16) to
connect to a PC, modem, or GPS device.
To connect to the RS-232 port you must set the ADR Sabre to the same baud rate as
the device connected.
RS-232 Settings
Baud Rate: To set the baud rate on the Sabre:
1. On the setup menu, use ← and → keys to select the <config> menu, then
select 2) COMMS.
<config><SITE><STUDY><FILES><STATUS>
0) LANGUAGE-ENGLISH UNITS–US
1) DATE-Mon May 20, 2013 16:46:29 DST:On
2) comms-UsbDev:Off Rs232:115200
3) COMM_ID–00001
Figure 42 – Select the COMMS parameters
2. Select RS-232 field by pressing the → key, the baud rate blinks when
selected. Select a baud the using ↑or ↓ key. Press ENT key to save the
new baud rate, ESC to revert to previous value.
Comm ID: You can set a Comm ID (communications ID). This is useful if you have
devices you are connecting on a network system. By default, the Sabre COMM_ID
value is 00001, but can be set to any number from 00001-65535.
1. On the <config> menu, select 3) comm_id by pressing the ↓ key, or ENT
key, or “3” on the keypad.
<config><SITE><STUDY><FILES><STATUS>
0) LANGUAGE-ENGLISH UNITS–US
1) DATE-Mon May 20, 2013 16:46:29 DST:On
2) COMMS-UsbDev:O Rs232:115200
3) comm_id–00001
Figure 43 – Change COMM_ID
2. Select the numeric field by pressing the → key.
3. Move along character places using arrow keys, ↓ = left, ↑ = right, or hold
the SHIFT key and then press ← or → to move left or right along the
places. The character places all blink, except for the current place selected.
4. Press a number key on the keypad to enter the respective numeric value for
each digital place as needed (numeric range 00001-65535).
Note Any new GPS setting obtained remains on the Sabre until
changed by a subsequent GPS reading.
TM
You can use Peek’s Street-Link hand-held device to provide GPS (and time sync)
using the Sabre’s “Device” USB port (see Figure 46, p. 39). Or you can use the
Sabre’s RS-232 serial port for connecting to a GPS device using a serial connection
(see “Ancillary Hardware Options,” p. 16, for more device and cable information).
Serial Device Connection: Connect a GPS device which is capable of NEMA serial
communication protocol, and set to 4800 baud. Connect GPS device to the Sabre’s
RS-232 port with serial cable. When you connect the GPS device, and attempt
retrieve the GPS input, the Sabre looks for the input at 4800 baud rate for GPS
information transfer.
To get the GPS input, with a qualified GPS device correctly connected (either via
serial port, or using Street-Link connected to the USB “Device” port):
1. Go to the <site> menu, and press ENT or the 2 key to select GPS (see
Figure 44, p. 38).
2. With GPS selected, press ENT to select “GET.” The Sabre waits for the GPS
input to be automatically transferred from the GPS device.
<CONFIG><site><STUDY><FILES><STATUS>
0) SITE- Hwy_23_at_0000 STA-111111111111111
1) ARRAYS Tube T_T 02 Ln/s Fwd >
2) GET-…Waiting for GPS
3) CTREE-FHWA_USA defADR3 HiBit 051508
<CONFIG><site><STUDY><FILES><STATUS>
0) SITE- Hwy_23_at_0000 STA-111111111111111
1) ARRAYS Tube T_T 02 Ln/s Fwd >
2) GPS-Lat:27d32,574’ Lon:-82d33,780’
3) CTREE-FHWA_USA defADR3 HiBit 051508
Note With Street-Link connected, you can check the Street-Link LEDs
for Sabre battery and memory status (see Figure 10, p. 18).
To send GPS location (and sync time, if need be), do the following:
1. Press the Sync Location button on the Street-Link; while the Street-Link
seeks the GPS satellite data, the GPS Lock LED flashes. The Sync
Location button LED also flashes.
2. When the GPS data has been obtained, the GPS Lock LED remains ON
steady. The GPS location is transferred to the Sabre automatically. When
this happens successfully, the LED on the Sync Location button goes ON
steady.
3. Verify the GPS location entry on Sabre’s <site> menu (see Figure 45).
4. If desired, press the Sync Time button to load the satellite time to the Sabre.
When successful, the LED on the Sync Time button goes ON.
Note The PC must recognize the USB device connection, and the
software used must also; refer to the respective software
documentation for instructions on device connection.
2. If inactive for 300 seconds, the DEVICE connection shuts down. To reopen
USB communication, on the <config> menu, select 2) Comms. Set to
UsbDev:On and press ENT to select. The Sabre begins a 300-second
timeout (listed in parentheses next to setting – see Figure 47, p. 39):
<CONFIG><SITE><STUDY><files><STATUS>
0) M0: 0139MB-0150MB_00512-27859-30724 R
1) USB:Off
2) STUDY:None
3) EVT:12151527=00005757 Evts
Figure 49 – The USB slot setting
usb:Off USB not in use
usb:New+ Transfer any “new” files to the USB drive – those not sent
before – plus the current study setup file (if saved – see
“Save Study and Classification Tree Files,” p. 63).
usb:New Transfer any “new” files – those not sent before.
usb:All Transfer to the USB drive all stored data files and setup files.
usb:Get Retrieve data and setup files from the USB jump drive
When you transfer files, file transfer information is displayed on the screen:
<CONFIG><SITE><STUDY><files><STATUS>
0018 File/s,0000226 UsbBlocks,8710KB
0) M0:0149MBB_0150B_00512-30716-30724 *
1) usb:All Free:044022
2) STUDY:Study_1=02-T,02Min,Cont
3) EVT:12151527=00005757 Evts
Copied-0018, Mark-0000, Skip-000
For example, with USB drive inserted, you can select the 2) study line, and
press ENT then select Get to retrieve a study (if you have a study saved);
you are prompted for the Study IDs (use the ↑or ↓ key to select, then press
ENT). When retrieved, you are prompted to arm the Sabre (use the ↑or ↓
key to select Yes, then press ENT to arm).
<CONFIG><SITE><STUDY><files><STATUS>
0) M0:0149MBB_0150B_00512-30716-30724 *
1) USB:Off
2) study:ARM_UNIT_NOW?-No
3) EVT:12151527=00005757 Evts
Figure 51 – Study prompt to arm unit
File Types
Study (.stp) – Study setup files contain all the settings for a study, and/or can also
contain the Classification tree (CTREE).
Event (.evt) – Event files contain the recorded raw, time-stamped event (sensor
activation) data from the respective study.
PVR (.pvr) – Per-vehicle records. PVR data files include records of each vehicle
recorded, and whatever data is possible via the sensor array in use – time, gap,
headway, class, and other data – per vehicle.
Binned (.bin) – This file contains the accumulated, categorized (or “binned”) data as
outlined in the array configurations (gap, headway, speed, class, etc.), with a count of
number of vehicles detected in each “bin,” or range of values.
ASCII Event File (.aef) – This file has the same raw event data as the Event file, but
in a readable form – ASCII text.
USING A MODEM
Contact Peek Technical Support for information on modems that can be used, and for
connection and configuration instructions (see “Technical Assistance,” p. 9).
This Chapter discusses the basic settings and features common to all studies, regardless of
sensor types and array types in used. For detailed setup information on specific sensor and
array types, refer to the Chapters 5-9 in this manual. The following topics are discussed in
detail in this chapter:
The physical location of study site (where sensors are installed and deployed).
The type(s) of information to be collected and stored
The number and direction of traffic lanes that will be studied.
The type of sensors to be used for the study (tube, piezo, loops, mixed, etc.).
The array layout (Single Tube, Loop/Axle/Loop, etc.).
Proper and safe sensor installation as needed.
Accurate array spacing and dimension measurements.
GPS input, if used, for geographical location identification.
Site ID and Station number (for identifying the device and location of the study)
File type selection – PVR, Event, Binned, ASCII Event
Study setup – volume, count, gaps, class, etc., per study
Bin headers (data categories) and bin ranges, if binned data is used
Study file interval (nonstop, 1 minutes, 2 minutes, 5 minutes, … 60 minutes) –
data files are generated per interval.
Study length and time – start and end settings, and whether daily or continuous;
including when and how to start and end the study (by date/time, next interval, or
manual).
Test and adjustment of sensors – tube debounce, loop hysteresis, etc.
Arm the Sabre and conduct the study.
Close and lock the ADR Sabre unit as necessary for extended, unattended
studies (see “Security,” p. 19).
Gather study results – data files, for volume, count, gaps, class, etc.
This section describes typical pre-study checks and settings for any study setup,
regardless of array or sensors used.
Note Never begin a study if battery level is at 6.0 v or less. This may allow
the ADR Sabre operation to stop before study completion. Instead,
recharge the battery first (see “Recharging the Battery,” p. 138).
GPS <CONFIG><site><STUDY><FILES><STATUS>
coordinates 0) SITE-000000000000000 STA-1111111111111111
1) arrays Loop L 02 Ln/s Fwd >
2) GPS-Lat:00d00,000’ Lon:000d00,000’
3) CTREE-FHWA_USA defADR3 HiBit 051508
Figure 57 – GPS coordinates
This section describes the basic steps needed to configure the Sabre for a study, with
topics listed in general order of completion. These steps are useful for any type of
array or sensors used (details specific to each array type are described in later
chapters).
<CONFIG><site><STUDY><FILES><STATUS>
0) site- 00000000000000 STA-1111111111111111
1) ARRAYS Tube T_T 02 Ln/s Fwd >
2) GPS-Lat:00d00,000’ Lon:000d00,000’
3) CTREE-FHWA_USA defADR3 HiBit 051508
Figure 58 – <site> menu selected
3. Press ENT or → keys to select site (ID) and set the site name in 16 alpha-
numeric characters as appropriate (the field blinks when selected, except for
the currently selected digit). Move along digit places using arrows: ↓ key =
left, ↑key = right. Or hold SHIFT and press the ← or → key to move the
cursor left or right, respectively.
To enter a numeral – press that number on the
keypad.
<CONFIG><site><STUDY><FILES><STATUS>
0) SITE- 00000000000000 STA-1111111111111111
1) arrays Tube T_T 02 Ln/s Fwd >
2) GPS-Lat:00d00,000’ Lon:000d00,000’
3) CTREE-FHWA_USA defADR3 HiBit 051508
Figure 61 – <site> content with arrays selected
3. Using the arrow keys, select the array type (Tube, Loop, Mixed, etc.) you are
using, the configuration (T_T, etc.), number of lanes, direction, etc.
For further details on the arrays – spacings, count ratios, sensor debounce time, loop
length, hysteresis, sensitivity, etc. – refer to Chapters 5-9, depending on the sensor
array you are using (Chapter 5 for road tubes, Chapter 6 for loops, etc.).
After doing the settings for array(s), refer back to the remaining steps in this chapter.
Note If you record the events during a study, you can later run the events
file, but with changed settings, get new data (see Appendix C, p. 150).
AEF (ASCII Event File) (.aef) – This file has the same raw event data as the Event
file, but in a readable form – ASCII text. This file requires much more memory than
other data, and is therefore not typically recommended for longer term study usage, if
there are memory storage limits or concerns.
Bin Sub-menu
You select the “headers” (categories) of data to record on the BIN sub-menu, and set
the value or range for each “bin” for that category. When the study is done, the count
of vehicles detected in each “bin,” or range of values, is stored in that bin.
To display the BIN sub-menu:
1. Under the <study> heading, select the 0) record line.
2. Press → to select file type BIN, then press ↑ or ↓ key to select “>.”
CONFIG><SITE><study><FILES><STATUS>
0) record: PVR+ BIN> EVT+ AEF+
1) START-NextInt
2) END-NeverEnd BIN “>”
3) REC_INT-15 Min FREQ-Daily selected
Note Bin “headers” and ranges are preselected for you, by default,
depending on array type selected. These are subject to your
adjustment or removal. You can also add more headers, more
columns, and/or more study pages.
For example, for 2-Gap, the BIN01 value is 03000, which is 3000 hundredths
of a second, or 30 seconds. In the study, this bin would contain the count of
vehicles with a time gap from the previous vehicle of 30 seconds or less.
Likewise, BIN02 will contain the count of vehicles with a time gap of between
30 seconds and 60 seconds, etc. You can add columns to expand the
number of “bins” for a category.
Set up bin categories and ranges for your study using the BIN sub-menu:
1. Under the <study> heading (above), press “0” to select the 0) record line.
2. Press → to select file type BIN, then press ↑ or ↓ key to select “>”:
CONFIG><SITE><study><FILES><STATUS>
0) record: PVR+ BIN> EVT+ AEF+
1) START-NextInt BIN “>”
2) END-NeverEnd selected
3) REC_INT-15 Min FREQ-Daily
Figure 71 – Selecting BIN “>”
3. Press ENT to display the BIN sub-menu (for this array, default headings
and values are entered as shown):
study-1_Of_1 #HDR1-15 #HDR2-12 #HDR3-03
HEADER BIN01 BIN02 BIN03 BIN04 BIN05 >
1-Class 01 02 03 04 05
2-Speed 00025 00030 00035 00040 00045
3-Channel 001 002 003 ––– –––
Figure 72 – BIN sub-menu
The headers needed are already selected by default:
Class – The Class line cannot be edited – the bins are already set to contain bins for
all classes according to the class tree in effect (see “Load Study Setups and/or
Classification Tree,” p. 65, to change the classes used).
Speed – We will need to change number of bin columns, and the values.
Channel – The Channel line, which will hold the volume counts for the three
lanes, using three bins, one for each lane, cannot be edited.
We will need to add another page and set a header for “Gap.”
4. Change the number of SPEED columns:
a. On the BIN sub-menu, use the arrow keys to navigate to the top line so
that study is selected (blinks).
b. Press → to move right to the corresponding header value (#HDR2)
(number blinks when selected).
c. Press ↓ key decrease the #HDR2 value from 12 to 05. Then press
ENT. This changes the number of columns for Speed:
study-1_Of_1 #HDR1-15 #HDR2-05 #HDR3-03
No. of HEADER 2
HEADER BIN01 BIN02 BIN03 BIN04 BIN05 > columns
1-Class 01 02 03 04 05
(“05”)
2-Speed 00025 00030 00035 00040 00147
3-Channel 001 002 003 ––– –––
Figure 73 – Changing number of bins for Speed
5. To set the Speed values press 2 to select the “2-Speed” line, press the →
key to select the second bin field, and use the arrows and keypad to change
its value from 00030, to 00035.
6. Likewise, set the next two Speed columns to 00045, and 00055. The last
column is preset to 00147 by default (just an arbitrary high number).
This completes the bins for the example study.
Record Interval
The Sabre can record and help sort traffic data into time periods, or intervals, to more
accurately reflect traffic at given times. This setting (REC_INT) determines the time
spans for the data collection intervals.
Set the interval as required for your data collection resolution; settings are 1-minute,
2-minute, 5-minute, 6-minute, 10- minute, 15-minute, or 60-minute. Or, set to 0 Min.
for continuous recording, without including time intervals.
Be sure to set at least the minimum interval (and maximum resolution) you require.
For example, if you need data for 15-minute intervals, but set to record in hourly
intervals, you cannot expect to get data accurately reflecting 15-minute intervals.
Conversely, if you need hourly information, but set up for 15-min. intervals, you can
always combine the interval counts to get hourly totals, if required.
Study intervals are hourly divisions and are aligned so that an interval starts at the top
of each hour. That is, for example, a 15-minute interval restarts the data counts each
15 minutes, on the hour, quarter-past, half-past, and quarter ‘til.
1. Under the <study> heading, press “3” to select the 2) rec_int line.
2. On the 3) rec_int line, press the → key to select the rec_int option field (the
selected option blinks).
3. Use the ↑or ↓ keys to select the rec_int option (1-min, 2-min, 5-min, etc.,
or 0 min for continuous).
Press ENT to set the rec_int option, and move to FREQ (frequency) field or
ESC to revert to prior setting.
Record Frequency
The frequency setting allows you to get the data organized into daily totals (for longer
studies), or for one continuous study without daily
1. Under the <study> heading, press “3” to select the 2) rec_int line.
2. On the 3) rec_int line, press the → key to select the FREQ (frequency) field.
3. At the FREQ field, use the ↑or ↓ keys to select the FREQ option:
Daily – Organizes study data for multi-day studies into per-day files.
Continuous – Organizes data on multi-day studies as a continuous
sequence of files without day distinctions.
4. Press ENT to set the FREQ option selected, or ESC to revert to prior setting.
a. Press ENT to go to the month field, and use the ↑or ↓ keys to select
the month, then press ENT to go to the day field.
b. Use the ↑or ↓ keys to select month, then press ENT to go to the day,
press ENT to go to the hour field, select the hour, then press ENT, etc.:
CONFIG><SITE><study><FILES><STATUS>
0) record: PVR+ BIN+ EVT+ AEF+
1) start-
2) END-Set NextInt Wed May 29, 2013 10:45
3) REC_INT-15 Min FREQ-Daily
Figure 75 – Set end time
When the start interval occurs, the Sabre starts recording as configured. The
indication on the screen changes from “ARMED” to “REC.” The Sabre runs
the study for the selected period or until end time selected. If you selected
NeverEnd for the End setting, you must manually stop the recording.
If the Sabre set to ARMED, you can disarm the Sabre. You can also
manually stop the recording in progress (see below).
Manually Disarm the Sabre or Stop Recording
You can always disarm the ADR Sabre (and prevent the study from beginning),
or manually stop the recording as need be, whatever the End setting.
To manually disarm the “armed” Sabre:
1. Press BACK as needed to display startup screen, and at the startup screen,
press the ENT key to select armed (blinks in lower case), or press
FUNCTION and 1 from menu heading content, to display the prompt:
2. Press ↑or ↓ key to set the prompt:
Quit Armed? Yes – select and press ENT to stop, and return to Idle status.
Quit Armed? No – select and press ENT to remain in armed mode.
To manually stop a recording in progress, the procedure is similar:
1. Press BACK as needed to display to startup screen, and from the startup
screen, press the ENT key to select rec (blinks in lower case), or press
FUNCTION and 1 from any screen, to display the prompt.
2. Press ↑or ↓ key to set the prompt:
Quit Rec? Yes – select Yes, press ENT to stop study, and return to IDLE.
Quit Rec? No – select No, press ENT to continue recording.
Note A study must complete at least one full interval in order to produce any
data; otherwise, If a recording is stopped before an interval is
complete, an empty file is created, and no report can be created.
File Transfers
You can transfer the files to a PC for further analysis by connecting using the RS-232
port or USB Device port, or store on a thumb drive using the USB Host slot (for more
information, see “Using the Communications Ports,” p. 36, and “Data File Types,” p.
41).
when renaming, and include no spaces, or special characters other than hyphen
(-) or underscore (_).
3. Insert the USB with the renamed files back into the Sabre “Host” slot, then use
the USB:get on the Sabre (see “USB “HOST” Slot,” p. 40).
The Sabre can store as many of these files as memory space allows, as long as
they have followed naming conventions, and are named differently than the
default names.
Sabre comes with a default set of vehicle classification definitions; these are standard
industry vehicle classifications. If you have a different classification tree you need to
use, you can load it into the Sabre from a USB drive.
Caution Be sure you have properly structured classification tree data. For
additional guidance, please contact Peek Technical Support (see
“Technical Assistance,” p. 9).
To install the new file, which will be used for the study you will create:
1. Place the USB thumb drive with the new CTREE file in the HOST slot on the
front panel of the Sabre.
2. Go to the <files> menu.
3. In the <files> menu, press “2” to select the 1) usb line.
<CONFIG><SITE><STUDY><files><STATUS>
0) M0: 0139MB-0150MB_00512-27859-30724 R *
1) USB:Get
2) STUDY:None
3) EVT:None
Figure 82 – usb:Get selected
4. Press the → key to select the parameter to the right of usb: (it blinks).
5. Press the ↑or ↓ key to select Get. Press the ENT key, this starts the file
transfer from the thumb drive. The Sabre recognizes the classification file
type by its contents, even though it has the same suffix as study files (stp).
6. To view the CTREE file, press the ↑or BACK key to go to the menu
headings, and then press ← or → to select the <site> heading. You can see
the new CTREE file listed.
<CONFIG><site><STUDY><FILES><STATUS>
0) SITE- Hwy_23_at_Main STA-001__________
1) arrays Tube T 01 Ln/s Fwd >
2) GPS-Lat:00d00,000’ Lon:000d00,000’
3) CTREE-FHWA_USA defADR3 HiBit 051508
Figure 83 – <site> heading with CTREE listed
This section describes how you can use a single road tube sensor with the Sabre and
set up a simple volume count in one lane (see “T” array in Table 5, p. 22). The data
that can be collected from this array would include volume, headway, or gap, in one
channel. The number of vehicles is estimated based on axle count.
Note Before performing an actual study, please refer to the road tube
installation guidelines, and observe all applicable safety guidelines.
<CONFIG><site><STUDY><FILES><STATUS>
0) site- 00000000000000 STA-1111111111111111
1) ARRAYS Tube T_T 02 Ln/s Fwd >
2) GPS-Lat:00d00,000’ Lon:000d00,000’
3) CTREE-FHWA_USA defADR3 HiBit 051508
Figure 85 – <site> menu selected
4. Press ENT or → keys to select site (ID) and set the site name in 16 alpha-
numeric characters as appropriate (the field blinks when selected, except for
the currently selected digit). Move along digit places using arrows:
↓ key = left, ↑key = right. Or hold SHIFT and press the ← or → key to
move the cursor left or right, respectively.
To enter a numeral – press that number on the
keypad.
<CONFIG><site><STUDY><FILES><STATUS>
0) SITE- Hwy_23_at_Main STA-001__________
1) arrays Tube T 01 Ln/s Fwd >
2) GPS-Lat:00d00,000’ Lon:000d00,000’
3) CTREE-FHWA_USA defADR3 HiBit 051508
Figure 88 – Setting array parameters
7. Press ENT or → to select the “>” and press ENT to display a sub-menu:
8. Press ENT or → keys to select the “T” and press ENT to display the
debounce menu. Then press ENT or → keys again to select the Deb
(debounce) field. Use the number keypad to enter debounce value
(milliseconds) and press ENT. Press BACK when finished to return to
previous menu.
*BIN sub-menu: BIN has a third option, “>” used to display the bin sub-
menu. Select “>” for the BIN value, then press ENT to display the sub-
menu:
study-1_Of_1 #HDR1-01 #HDR2-00 #HDR3-00
HEADER BIN01 BIN02 BIN03 BIN04
1-Channel 001 ----- ----- -----
2-None ----- ----- ----- -----
3-None ----- ----- ----- -----
Figure 92 – Setting array
15. On the sub-menu, from study, press ENT to select the page field (1_Of_1) to
set the number of study pages; you can set up from 1-3 study pages.
16. Press 1 to edit the first line of the study menu. For an array type T, you can
select Channel, Gap or Headway (more headings are available for other
array types that record speed, class, etc.):
Channel: Default setting, record a single vehicle count for a lane.
Gap: Distance between tail of one vehicle and front of next, binned by gap
times. Set the range value for each bin.
Headway: Distance between front of one vehicle and front of next, binned
by headway times. Set the range value for each bin
17. Select 2 and set to Gap, and 3, set to Headway. The respective bins appear
on the line, with default time settings (in hundredths of a second). Each bin
increments its count for each incident of a gap or headway of the respective
amount of time set for each. Set bin values as needed with keypad.
18. With the bins set, press BACK button as needed to return to <study> menu.
19. Next set the START – select either of two choices.
Next Int: Starts at the next recording interval as set. For example, if the
study interval has been set to 15 minutes, the intervals start at each quarter
hour on the clock, and the study starts at the next interval’s start time.
Set: Allows you to set the date and time to start the study. The study starts
at the start of the next available interval after the designated start time.
<CONFIG><SITE><study><FILES><STATUS>
0) RECORD: PVR+ BIN+ EVT+ AEF+
1) start-Set Mon Jun 10,2013 14:16
2) END-NeverEnd
3) REC_INT-15 Min FREQ-Daily
Note The recording interval is the period of time a study will record the study
data before storing the interval data, and restarting the counts for the
subsequent interval of recording.
Sabre startup screen indicates “REC” and runs the study for the selected
time period or until the selected end time.
You can always manually disarm the ADR Sabre before starting the study,
(or stop the recording in progress). If you selected never end, you must
manually stop the ADR Sabre recording in progress.
26. To manually stop the recording, from the startup screen, press ENT key to
select rec (blinks), then press ↑or ↓ keys to set the question (or press
FUNCTION and 1 to get to the prompt from any menu heading):
Quit REC? Yes – select and press ENT to stop the study, and return to Idle
status.
Quit REC? No – select and press ENT to remain in record mode.
You can check your study configuration using the Sabre’s per-vehicle record (PVR)
monitor. This can provide “real-time” feedback, with count statistics per vehicle based
on the running activation data provided by the sensor array.
To enable the PVR monitor:
1. Go to the <status> menu, and press ENT to select PVR_MON:
<CONFIG><SITE><STUDY><FILES><status>
0) SN-330033001547303439310000
1) 6.21V 009.2mA 001mA 000mA +073.5F
2) COUNT_MON_01 00000 00000 00000 00000
3) pvr_mon >
Figure 99 – PVR Monitor selected
2. Press the → key to select the > at the right of the screen, then press ENT.
This actives the monitor, which then begins to accumulate statistics for the
array as configured for current traffic, and display the “live” counts on the
LCD with appropriate headings:
HH:MM:SS Ln Vnum AxAx Cl
>
This chapter contains detailed setup information on road tube sensors and arrays.
This chapter describes manually using the setup menu specifically to define the road tube
study parameters for each array type. For more information on general study settings, such as
setting the Site ID and station name, setting start and end times, selecting file types to capture,
etc., see Chapter 4, Setup Basics. The following topics are discussed in detail in this chapter:
Read Tube Array Selection, p. 78
Configuring Road Tube Arrays, p. 79
Setting Tube parameters, p. 79
Example Single-Tube Counting Array, p. 81
Road Tube Installation guidelines, p. 92
Road Tube Calibration, p. 95
Special Setup Considerations for Multiple Tube Arrays, p. 95
Before setting up your road tube-based study, first determine just what data is sought.
Refer to Table 11 below for general guidance in array configuration and study types,
using road tubes only.
Table 11 — Type of data available (by axle), listed by Tube Array Selection
Tube Arrays Data Types, per Array and Layout
Tube Tube Volume
Description Gap Headway Speed Class Wheelbase
Array Layout Count
One-lane,
One- tube, one-
T non-dir. Yes Yes No No No
channel volume
* The T_T and T_T-2 settings are much alike, except the T_T-2 setting provides for more accuracy and
enables two-direction counts, while using smaller tube spacing (2- ft. default for T_T-2, compared to 10-ft.
for T_T).
<CONFIG><site><STUDY><FILES><STATUS>
0) site-00000000000000 STA-1111111111111111
1) arrays Tube T 01 Ln/s Fwd >
2) GPS-Lat:00d00,000’ Lon:000d00,000’
3) CTREE-FHWA_USA defADR3 HiBit 051508
Figure 101 – Entering Tube array information
Press the → key to select the “>”, and press ENT to display the array sub-menu:
Debounce Adjustments
Some road tube sensors are subject to possible signal “bounce” – that is, there may
be reverberations in the tube after the initial tube activation that could cause a single
axle to be counted multiple times by the Sabre. You can set a “debounce” time for
each tube input. This sets a time interval after a sensor input signal is received,
during which any further signals for that sensor are ignored. This is so possible signal
noise or “bounce” is not added as a count.
The best setting for a tube can depend on expected speeds. For example, in an area
with a typical vehicle speed of 35 mph, a setting of 80 msec may work well. Or, at 50
mph, 30 msec is more typical.
Debounce Adjustments: If there is evidence of false counts, increase the debounce
time slightly, and retest. If there are skipped counts occurring, decrease the debounce
time, and retest. Continue adjusting until results are satisfactory. Skipped counts can
also occur due to other factors, such as a faulty tube or connections. Be sure to check
the integrity of your array and connections.
Single-Tube Array
This array includes a single road tube sensor, across a single traffic lane. Here the
Sabre records the vehicle axles passing over the tube. The data that can be collected
from this array is: volume, headway, or gap in one channel. Per-lane headway and
gap counts are valid only for the single lane tube array.
Figure 104 – Single-tube counting arrays – 1-lane or 2-lane (totaled in one channel)
Table 12 — Parameters for single-tube array
Menu Parameter Description
<site> (Tube, etc.) (sensor type) – Set to Tube.
1) array (T, T_T, etc.) (array type) – Set to T.
Ln/s No. of lanes – Set to 1.
(direction) Fwd – not changeable here.
> (array/sensor sub-menus – press ENT to view).
array Press → key to select Ratio (Axle to vehicle); when selected, an
sub-menu x.xx is displayed. Set as needed (default 2.0). This value is used
to calculate a vehicle count based on axles counted.
Press → key to select 1AxVTO (timeout after which Sabre stops
looking for next axle as part of vehicle, and next is counted as
start of a new vehicle).*
sensor On array sub-menu, select T on a sensor listing and press ENT
sub-menu to view.
Deb (debounce) – Set as required for accuracy (msec).Default is
35 msec.
<study> record On 0) record line, press → key to select each file type (PVR etc.),
settings use the ↓or ↑key to enable (+) or disable (–).
For Bin files, use the ↓or ↑key to select (>) and press ENT to
view study page(s). Set up bins (see “Setting Up the Bins,” p. 52)
for channel, gap, and/or headway, and their respective bin
ranges, as desired.
* 1AxVTO – Without using this setting, a vehicle with an odd number of axles will
result in the Sabre remaining on while awaiting the next axle strike. This will keep
the Sabre on for longer periods until the next odd-number axle vehicle, causing
the Sabre to use up its battery faster.
Note Typically with a single road tube, you would connect to input 1.
to select the Deb (debounce) field. Use the keypad to enter debounce value
(milliseconds) and press ENT. This can be adjusted later as needed.
14. Change the number of columns for the HEADER “2-Gap” to accommodate
the ranges needed:
a. Use the BACK key on the Sabre keypad to navigate to the 2-Gap
Header, then use ↑ key so that study is selected (blinks).
study study-1_Of_1 #HDR1-04 #HDR2-05 #HDR3-05
selected No. of header 2
HEADER BIN01 BIN02 BIN03 BIN04 BIN05
columns (“05”)
1-Channel 001 ----- ----- ----- -----
2-Gap 03000 06000 09000 01200 65534
3-None ----- ----- ----- -----
Figure 111 – Changing number of columns
b. Press → to move right to the corresponding header value (#HDR2 for 2-
Gap; number blinks when selected).
c. Press ↑ key increase the value from 05 to 06. Press ENT to save
changes. When you add more columns for a header, the new columns
are automatically populated with default values
15. To set the Gap values, press 2 to select the “2-Gap” line, press the → key to
select the first bin field, and use the arrows and keypad to change its value
from 03000, to 00200.
Likewise, set the next Gap columns to 00300, 00400, 00500, and 00600.
The last column is preset to 65534 by default (arbitrary high number). Press
the → key to display the rightmost column.
study-1_Of_1 #HDR1-04 #HDR2-06 #HDR3-00
HEADER BIN01 BIN02 BIN03 BIN04 BIN05 >
1-Channel 001 ----- ----- ----- -----
2-Gap 00200 00300 00400 00500 00600
3-None ----- ----- ----- ----- -----
Figure 112 – Setting up bin study headings
During the recording, each bin increments its count for each incident of a
gap of the respective amount of time range for each. The first bin (BIN01) for
Gap records the count of vehicles with gap of up to 2 seconds from previous
vehicle. The second bin (BIN02) counts vehicles with gap of 2 to 3 seconds,
etc.
16. With the bins set, press BACK button as needed to return to <study> menu.
At the point, the settings are ready for the array.
Note For more information on other study settings, such as start and end
times, intervals, or to arm the Sabre, see Chapter 4, Setup Basics.
Note Measure the same length of tube from the edge of the road to the ADR
for both tubes. Connect the short tube to the Sabre on road tube input 1,
the long tube to input number 2.
Note As indicated in Figure 113, always configure the array relative to traffic
flow direction, such that traffic in the short tube lane hits the short tube
before the long tube.
Typically, vehicle axles crossing the short (tube 1) then long tube (tube 2) would be counted in
Channel 1 in the study bins; vehicle axles detected only on the long tube would be counted in
Channel 2. The parameters you would set in a short / long tube count array are as follows:
Table 13 — Parameters for shot-long tube array
Menu Parameter Description
<site> (Tube, etc.) (sensor type) – Set to Tube.
1) array (T, T_T, etc.) (array type) – Set to tT.
Ln/s No. of Lanes – Set as needed, one “lane” per array.
(direction) Fwd – not changeable here.
> (Array/sensor sub-menus – select “>” and press ENT to view).
array Press → key to select Spc1, enter the measured distance between
sub-menu short long tube (in .01 ft. or .01 m). Default is 1 ft. (0.31 m)
Press → key to select ratio (Axle to vehicle); set as needed
(default 2.0). This value is used to calculate a vehicle count based
on axles count.
Note Measure the same length of tube from the near edge of the road to the
Sabre for each tube in a pair. At least 20-feet recommended. Both
tubes should also be of equal total length to maintain accuracy.
Typically, vehicle axles crossing the tube 1 first would be counted in Channel Bin 01 in the
study bins; vehicle axles detected crossing tube 2 first would be counted in Bin 02.
Note Measure the same length of tube from the near edge of the road to the
Sabre for each tube in a pair. At least 20-feet recommended. Both
tubes should also be of equal total length to maintain accuracy.
The parameters you would set in this tube count array (see Table 16, p. 89):
Figure 117 – Four-tube class-by-lane lanes / channel assignments (for “Sep” directions only)
Note Measure the same length of tube from the near edge of the road to the
Sabre for each tube in a pair. At least 20 feet is recommended. Both
tubes should also be of equal total length to maintain accuracy.
When you have selected your study type (see “Road Tube Array Selection,” p. 78),
installed your road tubes (see for recommendations) and set up your study (see
Study Setup Example), attach your road tubes securely to the road tube inputs on
the back side of the ADR Sabre.
Road Tube
inputs (1-4)
Site Safety
This is not a safety manual nor is it a “how to” book for safely installing road tubes or
other sensors in or on the roadway. This manual assumes that anyone using this
guide for study site installation is a locally qualified technician and is thus qualified to
safely set up and execute traffic counting studies on the study site, and is trained in
addressing the public and personal safety factors that arise when working in such an
environment.
Safety for the installer, and for the public, should be foremost in mind at all times,
especially on site.
Warning: Consult your local authority for the best safety practices and installation
requirements in your area, before working on or near the roadway or
any such study site. Failure to do so can result in injury or even death,
or damage to equipment. Do not compromise safety.
Site Selection
A major factor in collecting usable data is the location. In selecting a location:
Choose a location such that vehicles are traveling straight at a constant
speed when passing over the installed road tubes.
Avoid proximity to any area where a driver may have increased tendency to
change lanes or speeds. Thus, avoid intersections, curves, hills and valleys,
turning lanes and passing lanes.
Also avoid bumps, cracks, loose gravel or dirt, bridges, or culverts.
Spacing Requirements
When installing an array with more than a single tube, setting the distance between
tubes is a strategic consideration and accuracy is a must. Make sure tube array
spacings are set up correctly and accurate measurements are taken. Then when
configuring the array in the study, make sure to enter accurate spacing values, or
data will be skewed and inaccurate.
For example, for the tT_tT array, four tubes (two-long short pairs) are used.
Recommend spacing of close pairs is one foot (this is the default).
You will need to space the two pairs according to expected speed range. In low
speed urban areas a spacing of 8 feet is recommended. In higher speed areas, a
spacing of 16 feet is recommended. The default spacing is 10 feet (1000 x .01 ft.).
This chapter contains detailed setup information on loop sensors and arrays.
This chapter describes manually using the setup menu specifically to define the loop study
parameters for each array type. For more information on general study settings, such as
setting the Site ID and station name, setting start and end times, selecting file types to capture,
etc., see Chapter 4, Set up Basics. The following topics are discussed in detail in this chapter:
<CONFIG><site><STUDY><FILES><STATUS>
0) site-00000000000000 STA-1111111111111111
1) arrays Loop L 02 Ln/s Fwd >
2) GPS-Lat:00d00,000’ Lon:000d00,000’
3) CTREE-FHWA_USA defADR3 HiBit 051508
Figure 120 – Entering Loop array information
Press the → key to select the “>”, and press ENT to display array sub-menu:
Note If hysteresis is set too high, low slung vehicles (like luxury sedans)
may be detected as being over 100 feet long, as the loop vehicle
detection may tend to stay “on.” If you observe this and find that
reducing the hysteresis value to a lower setting is not acceptable,
reducing the sensitivity by one setting may achieve the desired result.
3 4
1 2
The diagram shows two arrays, one in each of two lanes. Notice the numbering;
typical the sensor inputs are analogous to this – that is, the lead sensor input is odd,
followed by the lag sensor input, which is the subsequent, even-numbered input.
The inductive loop as used for vehicle detection is comprised of two elements: the
electronic detector module; and the wire which makes up the inductive loop coil in the
road and its connecting lead in cable. The loop wire and its connecting lead in cable
are the inductive elements of the detection system and possess a combination of
resistance and capacitance (both inter-wire and wire to earth capacitance). The loop
wire is wound to form a coil (usually 4 turns) where the magnetic field becomes more
concentrated, creating the zone of detection. All conductors or wires carry an
electrical current produce magnetic flux as long as the current is flowing through the
wire. The effect of this flux is the electrical property called inductance, which is
measured in henrys (h).
Loop Construction
Quality loops, carefully installed as consistently matched equals, are recommended.
Loop Wire
Inductive loops, connecting lead in wire and cables typically use multi-stranded #12 or
#14 AWG copper wire with low AC and DC resistance. The wire thickness is
important, however, most critical is the quality, thickness and type of insulation
covering the wire. Several types of insulation are available but only cross-linked
polyethylene (XHHW) should be used for vehicle detection loops. The insulation
must withstand wear and abrasion from shifting streets as they expand and contract
from high summer heat and winter cold as well as attacks from moisture, solvents and
oils. Multi-stranded copper wire is recommended as better than solid wire because of
its mechanical characteristics and is easier to correctly install without damage.
Stranded wires withstand bending and stretching better than solid wire.
Size of Loops
Loops for vehicle detection in traffic data applications are commonly 6‘ x 6’ (or 2m x
2m) dimension, with 4 complete wraps (turns) of wire around the sensing area.
Although described as a square, the actual installation requires rounded corners to
eliminate stress points at the corners. If two loops are used for speed measurement,
exact pairs are required in a lane.
Note For operation within permitted guidelines, install loops and equipment
as specified. Any changes or modifications not expressly approved for
use by Peek Traffic could void the user's authority to legally operate
the equipment. For more information, consult with Peek Traffic
Technical Support (see “Technical Assistance,” p. 9).
Loops smaller than 6 ’x 6’ may result in the early loss of detection for high body
vehicles and should not be used if accurate truck traffic data is expected. Loops are
usually installed as wide enough to span the path where detection is required, without
being so wide as to detect vehicles in adjacent lanes or adjacent loops. Install loops
three feet away from the nearest edge of lane line, if possible, and six feet away from
any other loops. All loops should always be at least 4’ away from any moving metal
objects, gates or doors. On narrow two lane roads with a loop in each lane it is better
to keep the loops apart from each other than to make them smaller.
For large vehicle detection, such as trucks and tractor trailers or semis, use 6’ x 6’
loops or greater. With smaller loops the high ground clearance between axles can
cause detection drop out problems, where each axle or group of axles will be seen as
a separate detection on a small loop.
Height of Detection
The height of detection is the maximum height above the installed loop at which a
reliable detection can be achieved. Normally, in the field test measurements will
achieve a height of detection equal to one-half to two-thirds the length of the shortest
side of a loop; that is, for example, a 6’ x 6’ loop would produce reliable detection to a
height of 3’ to 4’ above the loop wires.
Site Safety
This is not a safety manual nor is it a “how to” book for safely installing road tubes or
other sensors in or on the roadway. This manual assumes that one using this guide is
a locally qualified technician and is thus qualified to safely set up and execute traffic
counting studies on the study site, and is trained in addressing the public and
personal safety factors that arise when working in such an environment.
Safety for the installer, and for the public, should be foremost in mind at all times,
especially on site.
Warning Consult your local authority for the best safety practices and
installation requirements in your area, before working on or near the
roadway or any such study site. Failure to do so can result in injury
or even death, or damage to equipment. Do not compromise safety.
Site Selection
A major factor in collecting usable data is the location. In selecting a location:
Choose a location such that vehicles are traveling straight at a constant
speed when passing over the installed loops.
Avoid proximity to any area where a driver may have increased tendency to
change lanes or speeds. Thus, avoid intersections, curves, hills and valleys,
turning lanes and passing lanes.
Also avoid bumps, cracks, loose gravel or dirt, bridges, or culverts.
Note The 300 meter maximum connecting lead in length makes the assumption
that there is at least 2” (50 mm) separation between the loop and any
reinforcing in the roadway and that the connecting lead in wire used has an
inductance per meter not greater than 0.73 uh. A normal value for the total
inductance of the loop and connecting lead in wire is approximately 200 uh.
Any new installation measured at less than 100uh should be suspect and
checked, and corrected.
For connecting lead in wire and loop tails, use at least 5 twists per foot (15 twists per
meter). Loop tails can be untwisted over a short distance where the loop tails are
taken across a lane to a connection point immediately at the roadside. The maximum
length of the untwisted loop tails must not exceed 100 feet (30 meters). The purpose
of the twisting is a self-canceling effect on the unwanted detection field which exists
on the connecting wires from the sensing area (detection zone) back to the detector
electronics. It is not advisable to have loop tails from different detectors in the same
common slot. Not more than 50 feet (15 meters) of tails from any other loop should
be laid in a common slot without twisting and shielding. It is not advisable to mix pairs
from different detectors in a multi pair cable.
The loops and connecting lead in wire must have an insulation resistance to earth
greater than 10 megohms measured at 500 volts and a series resistance of less than
10 ohms. New loops should test to better than 100 megohms measured at 500 volts
and a series resistance of less than 5 ohms.
TO ADR
TO LOOP TWISTED PAIR W/ SHIELD
Any unused sensor connection wires should be isolated from earth ground. This helps
prevent the possible electrical noise from being served as an unwanted input by the
Sabre.
Note Do not connect the shields to the earth ground wire. If you are using
shielded twisted pair loop lead-in cables, the shields should only be
connected to earth ground in the cabinet, and not in the pull box or at the
loop end. It is preferred to have the shields be left “floating” or isolated
completely from earth.
This chapter contains detailed setup information on piezo (axle) sensors and arrays.
This chapter describes manually using the setup menu specifically to define the piezo study
parameters for each array type. For more information on general study settings, such as
setting the Site ID and station name, setting start and end times, selecting file types to capture,
etc., see Chapter 4, Set up Basics. The following topics are discussed in detail in this chapter.
The following topics are discussed in detail in this chapter:
The piezo array is installed to collect data that is directly comparable to road tube
counts, but possibly on a permanent or long-term basis.
It is recommended that the piezo sensor be installed so as to only have wheels on
one side of the vehicles “hit” the piezo sensor. In a 12-foot wide lane this might be
achieved by using a 7-foot long piezo installed on the right side of the lane as shown
in the diagram.
<CONFIG><site><STUDY><FILES><STATUS>
0) site-00000000000000 STA-1111111111111111
1) arrays Axle A_A 01 Ln/s Fwd >
2) GPS-Lat:00d00,000’ Lon:000d00,000’
3) CTREE-FHWA_USA defADR3 HiBit 051508
Figure 128 – Entering Tube array information
Press the → key to select the “>”, and press ENT to display the array sub-menu:
Debounce Setting
Some piezo sensors are subject to possible signal “bounce” – that is, there may be
reverberations in the sensor after the initial activation that might cause a single axle to
be counted multiple times by the Sabre.
For this reason, when you configure a piezo array, you can set a “debounce” time for
each piezo input. This sets a time interval after a sensor input signal is received,
during which any further signals for that sensor are ignored. This is so possible signal
noise or “bounce” is not added as a count.
The best setting for your array can depend on the expected vehicle speeds. For
example, in an area with a typical average vehicle speed of 35 mph, a setting of 60
msec may work well. Or, with an average speed of 50 mph, 40 msec is more typical.
Debounce Adjustments: If there is evidence of false counts, increase the debounce
time slightly, and retest; if there are skipped counts occurring, decrease the debounce
time, and retest. Continue adjusting until results are satisfactory.
Sensitivity Setting
The Sabre allows you to adjust the sensitivity of the piezo sensors input. Different
sensor installations may be more subject to false triggering, or may fail to pick up a
vehicle when it passes over the sensor. Thus you can set the “sensitivity” of the input
from 1 (very low) to 8 (highly sensitive). A setting of 0 disables the sensor input.
Sensitivity Adjustments: If there is evidence of false counts, try decreasing the
sensitivity slightly, and retest; if there are skipped counts occurring, increase the
setting, and retest. Continue adjusting until results are satisfactory.
Piezo-Piezo Array
The data types to be collected from this array are: speed, class, length (wheelbase),
volume, headway, gap, or a combination of these, by direction and by lane.
2
Figure 132 – Piezo-piezo array
The diagram shows two piezo-piezo arrays, one in each of two lanes. Using this
array, you can measure speed very accurately and also determine classification by
axle spacing and wheelbase. Use in free-flowing highway conditions where a loop
detector is not needed. The space between the opposing lane piezos would ideally be
more than the maximum expected width of wheel track for traffic on the road. This
spacing would help prevent one vehicle from being sensed in both lanes while
supporting detection of all traffic in each lane.
This chapter contains detailed setup information for using Weight in Motion (WIM) arrays.
This chapter describes manually using the setup menu specifically to define the study
parameters for each mixed array type. For more information on general study settings, such as
setting the Site ID and station name, setting start and end times, setting the interval, selecting
file types to capture, etc., see Chapter 4, Set up Basics.
The following topics are discussed in detail in this chapter:
Weight-in-motion (WIM) arrays are those arrays used for the collection of weigh-in-
motion data with the Sabre. WIM arrays typically include “class 1” piezo sensors for
weight detection, which are certified for accurate, linear response along their length.
This chapter includes mixed array types, such as the WIM-loop-WIM arrays, which
are often used in WIM applications. For more information on the sensor types
included in these arrays, such as installation guidelines for a specific type of sensor,
see the respective chapter for that sensor array type in this manual.
Debounce Setting
Some WIM sensors are subject to possible signal “bounce” – that is, there may be
reverberations in the sensor after the initial activation that might cause a single axle to
be counted multiple times by the Sabre. For this reason, when you configure a WIM
array, you can set a “debounce” time for each piezo input. This sets a time interval
after a sensor input signal is received, during which any further signals for that sensor
are ignored. This is so possible signal noise or “bounce” is not added as a count.
The best setting for your array can depend on the expected vehicle speeds. For
example, in an area with a typical average vehicle speed of 35 mph, a setting of 60
msec may work well. Or, with an average speed of 50 mph, 40 msec is more typical.
Debounce Adjustments: If there is evidence of false counts, increase the debounce
time slightly, and retest; if there are skipped counts occurring, decrease the debounce
time, and retest. Continue adjusting until results are satisfactory.
Sensitivity Setting
The Sabre allows you to adjust the sensitivity of the piezo sensors input. Different
sensor installations may be more subject to false triggering, or may fail to pick up a
vehicle when it passes over the sensor. Thus you can set the “sensitivity” of the input
from 1 (very low) to 8 (highly sensitive). A setting of 0 would disable the input.
Sensitivity Adjustments: If there is evidence of false counts, try decreasing the
sensitivity slightly, and retest; if there are skipped counts occurring, increase the
setting, and retest. Continue adjusting until results are satisfactory.
Piezo Offset
The Sabre allows you to adjust the “offset” to accommodate the different types of
piezo sensor input from different manufacturers. The appropriate offset value range
differs, depending on piezo type (see Figure 136, p. 116, for setting sub-menu):
(000 thru 099): Setting to 000-099 sets the level to 0-99% for positive going signals
from Piezo sensors (MSI, Phillips, IRD and ECM). Piezo sensors with high positive
signals and a slight negative signal may require a user to lower the Offset setting to
adjust for the higher signal.
Alternatively, piezo sensors with low positive signals and a considerable negative
signal may require a user to raise the Offset setting to allow for the additional
negative signals.
(200 thru 299): Setting to 200-299 sets the level to 0-99% for negative going signals
from piezo sensors (Kistler). This gives the ADR the ability to interface directly (to the
Kistler Lineas-Quartz sensor) without the use .of a separate charge amplifier.
Calibration Factor
The calibration factor is a multiplier that effectively adjusts the associated WIM (piezo)
sensor reading. This allows the Sabre to accommodate the ongoing variations in a
WIM sensor input level, variations that can be due to temperature changes and/or
other outside factors.
The calibration factor has two four-digit fields – the left field is the “current” value and
is manually settable, and the right field is the “base” value, which is read only (see
figure below). The base factor is the calibration factor that is being applied. The
current factor is manually set, and sets or affects the base factor.
Arr-01 Id E Count Deb Sens Off _CalFac__ Current value
W_W Base value
1)W-07 1 00000 0000 6 035 1121-1000
1)W-08 1 00000 0000 6 035 1012-1000
AutoCal Settings
The WIM array sub-menu includes a section of settings under the “AutoCal” sub-
heading. Use these AutoCal settings to set up how the Sabre will automatically
update the calibration factor (as described in section above).
How it works: The AutoCal feature collects a sample of WIM sensor readings from
passing vehicles, but only for the first axle of vehicles of the selected class. You set
the class (“Cl”) for which you will take axle weight samples. You set the expected
reading (.01Kp) for the axles to be sampled. You set the sample size. The Sabre
then collects readings as vehicles traverse the sensor, and compares the sample
average to the .01Kp setting, to determine how much to increase or decrease the
calibration factor base value (see section above).
Arrln ArrTyp _____AutoCal_____
< E Cl .01Kp Num Cur >
01_01-W_W 1 09 1000 025 025
02_02-W_W 1 09 1000 025 025
Figure 138 – WIM array sub-menu with AutoCal settings
The AutoCal settings are used for the following (see Figure 138, p. 118):
E Use the ↑or ↓ keys to set to 0 (disable) or 1 (enable) to enable/disable the
Autocal feature.
Cl Set from 1-15, to select the specific class of vehicle you will be sampling.
.01Kp Use this to set the kp (kilo-pounds of force) value to what you expect to see
for the first axle weight of the vehicles you are sampling. For class 9, you
might expect 10 kp, so you would set to 1000 (1000 x .01kp = 10 kp).
Num Set this value from 001-999, to set the number of vehicles per sample.
Cur This value is read-only, and counts down the remaining vehicles left to
complete the sample number (as set in the Num column). Thus it starts at
the number set in the Num column, and decrements each time a qualified
vehicle axle reading is added to the sample.
When “Cur” (current) value reaches 0, the sample is complete, and the
Autocal calculation is performed. At this point, the calibration factor “base” is
updated according to the calculation. The “Cur” value is reset to the Num
value, and the countdown for the next sampling starts.
Calibration results: The AutoCal works integrally with the calibration factor “current”
and “base” values. As the AutoCal sample readings are collected, the readings are
compared to the “.01Kp” setting. If sampled values are trending higher than the
“.01Kp” setting, then the “current” value of the calibration factor is set to a value
proportionately lower than 1000 to accommodate for the higher readings, so that the
results are closer to the set .01kP value. If sampled values are lower than the “.01Kp”
setting, then the "current” value of the calibration factor is set proportionately higher
than 1000 to bring the sensor reading values up to the set .01Kp value.
The “current” value of the calibration factor, then, reflects the up-to-the-minute
calculations of the AutoCal feature as the sampling of sensor readings is collected.
When the sample number is completed (“Cur” value is “0”), the “current” value of the
calibration factor becomes the new “base” value of the calibration factor. Then a new
sample group is started.
Example – how to set the AutoCal parameters:
On the WIM array submenu (see Figure 138, p. 118):
1. Press ENT or → key to select the “E” value, and use the ↑or ↓ keys to set
to 1 (enable).
2. Press ENT or → key to select the “Cl” value, and use the ↑or ↓ keys to set
the class (“Cl”) for which you will take axle weight samples. Typically this is
class “09.”
3. Press ENT or → key to select (.01Kp), then enter the value for axle
readings. For class “09” this might be 1000 (.01kp) or 10 kp (10,000 lbs.).
4. Press ENT or → keys to select the “Num” value to set the sample size.
WIM-WIM Array
This array utilizes two WIM sensors only. Data types that can be collected from this
array are: gross vehicle weight, axle weight, speed, class, length (wheelbase),
volume, headway, gap, or direction, by lane, or a combination of these. You can
connect and use up to four of these arrays with the Sabre.
Note In the array selections, for WIM, you can select the “W” option for
single WIM sensor. This single WIM sensor array is not typically usable
in actual studies, but is provided on the Sabre for single sensor testing
purposes only.
WIM-Loop-WIM Array
This array utilizes two WIM sensors flanking a loop sensor. The data types that can
be collected from this array are: gross vehicle weight, axle weight, group weight, kips,
and, speed, class, length (wheelbase), volume, headway, gap, or direction, by lane,
or a combination of these. You can connect and use up to four of these arrays with
the Sabre.
Note For clarity in the diagram, the connecting wiring for the axle sensors in
lane 2 are shown as going to the far side of the road. Normally this
would go to a “hand” or “pull” box on the far side and then return to the
ADR in conduit bored under the road. The return wiring and conduit are
not shown.
The standard distance from the first WIM sensor “hit” by a vehicle wheel to the
second piezo in the same lane is 16 feet. The loop is shown as a standard 6 foot
square and is centered between the WIM sensors. It is recommended that the sensor
loops be installed in the middle of the traffic path to avoid detection of vehicles in
adjacent lanes. In a 12-foot wide lane this is usually a 6-foot square or octagon with 4
Loop-WIM-Loop Array
This array utilizes two loop sensors flanking a WIM sensor. The data types that can
be collected from this array are: gross vehicle weight, axle weight, speed, class,
length (wheelbase), volume, headway, gap, or direction, by lane, or a combination of
these. You can connect and use up to two of these arrays with the Sabre.
This chapter contains detailed setup information for using mixed arrays, and describes
manually using the setup menu specifically to define the study parameters for each mixed
array type.
For mixed array types with WIM sensors, refer to Chapter 8, Weight in Motion (WIM) Arrays (p.
115). For more information on general study settings, such as setting the Site ID and station
name, setting start and end times, selecting file types to capture, etc., see Chapter 4, Set up
Basics.
The following topics are discussed in detail in this chapter:
Combined sensor arrays are used to take advantage of the strengths of each sensor
and provide improved accuracy of data. Included in this chapter are the setup
instructions for axle / loop arrays (Axle-Loop-Axle and Loop-Axle-Loop), and road
tube / loop arrays (Tube-Loop-Tube and Loop-Tube-Loop).
Note For mixed array types with WIM sensors, refer to Chapter 8 (see p. 115).
Axle-Loop-Axle Array
This array utilizes two axle (piezo) sensors flanking a loop sensor. The data types that
can be collected from this array are: speed, class, length (chassis), volume, headway,
gap, or direction by lane, or a combination of these. You can connect and use up to
four of these arrays with the Sabre.
The diagram above (Figure 142) shows two axle-loop-axle arrays, one in each of two
lanes. The axle-loop-axle array calculates the same data as the two-piezo array and
uses the loop to improve classification accuracy in situations where tailgating is a
problem. Using this array, the Sabre can measure speed very accurately and can
then determine classification by axle spacing and wheelbase.
The standard distance from the first piezo “hit” by a vehicle wheel to the second piezo
in the same lane is 16 feet. The loop standard size is a 6 foot square; the loop
centered between the piezos.
Note For clarity in the diagram (see Figure 142, p. 128) the connecting
wiring normally would go to connector box on the far side and then
return to the Sabre in conduit beneath the road surface (not shown).
Loop-Axle-Loop Array
This array utilizes two loop sensors flanking an axle (piezo) sensor. The data types
that can be collected from this array are: speed, class, length (chassis), volume,
headway, gap, or direction by lane, or a combination of these. You can connect and
use up to four of these arrays with the Sabre.
3 4
1 2
A
D
Figure 143 –RLoop-Axle-Loop arrays
The diagram above shows two loop-axle-loop arrays, one in each of two lanes. Very
comparable to the axle-loop-axle array, the loop-axle-loop array can usually be
installed at a lower cost.
Using this array, the Sabre can measure speed very accurately and can then
determine classification by axle spacing and wheelbase.
The standard distance from the first loop edge crossed by a vehicles front bumper to
the second loops first edge in the same lane is 16 feet. The loops are shown as
standard 6 foot squares and the piezo is centered between the loops. Many agencies
place the piezo centered between the leading edges, which would be 2 feet behind
the first loop. This placement is not critical to the study settings
Parameters on the <site> heading for loop-axle-loop array (see Table 27, p. 130):
Tube-Loop-Tube Array
This array utilizes two road tube sensors flanking a loop sensor. The data types that
can be collected from this array are: speed, class, length (chassis), volume, headway,
gap, or direction by lane, or a combination of these.
You can connect and use up to two of these arrays with the Sabre, but single-lane
usage is recommended, since a tube would not be lane-specific. For two lanes, use of
a piezo sensor would be recommended instead of the tube.
Parameters on the <site> heading for tube-loop-tube array (see Table 28, p. 133):
Loop-Tube-Loop Array
This array utilizes two loop sensors flanking a road tube sensor. The data types that
can be collected from this array are: speed, class, length (chassis), volume, headway,
gap, or direction by lane, or a combination of these. You can connect and use up to
four of these arrays with the Sabre, but single-lane usage is recommended, since a
tube would not be lane-specific. For multiple lanes, use of a piezo sensor would be
recommended instead of the tube.
SABRE MAINTENANCE
Battery Usage
After a full charge of a good battery, the ADR Sabre should operate (with only
roadtube sensors) for six months without a re-charge being required (with road tubes
only). Note that battery capacity is affected by extreme cold temperatures. Battery
manufacturers recomend that lead-gel batteries used in critical or severe service
applications should be replaced after 200 service cycles of charge and discharge or
every four years, which ever occurs first. With proper care in normal service, your
Sabre battery should last for 5 to 10 years.
The ADR Sabre is an extremely power-efficient device, designed to operate on
minimal power for long periods of time. Nonetheless, be sure to check, prior to any
study, that adequate power remains in the device to serve at least for the life of the
study.
Warning Observe all safety precautions when working with electrical circuitry and
equipment. Failure to do so can result in injury or damage to equipment.
Note When the charge is fully completed, the charging circuit will
continue in “trickle” mode, so that overcharging does not occur,
and the full charge is maintained.
1. Go to the <files> heading. Select evt: press ENT, and use ↑or ↓ key to
set to Del.
<CONFIG><SITE><STUDY><files><STATUS>
0) M0: 0139MB-0150MB_00512-27859-30724 R
1) usb:Off
2) STUDY:None
3) evt:Del 12151527-Yes
Figure 147 – Deleting event file
2. Press ENT, and then use ↑or ↓ keys to select the name of file to delete.
3. Using ↑or ↓ keys, select Yes to delete, or select No to not delete the file,
and press ENT.
To delete study files (from the SD card, if installed):
1. Go to the <files> heading. Select study and press ENT, and use ↑or ↓
key to set to Del.
<CONFIG><SITE><STUDY><files><STATUS>
0) M0: 0139MB-0150MB_00512-27859-30724 R
1) usb:Off
2) STUDY:None
3) evt:Del 12151527-Yes
Figure 148 – Deleting study file
2. Press ENT, and then use ↑or ↓ keys to select the name of file to delete.
3. Using ↑or ↓ keys, select Yes to delete, or select No to not delete the file,
and press ENT.
Note Before reformatting memory, save files first, if needed, to a USB jump
drive or to a PC (see “Using the Communications Ports,” p. 36).
2. Press the “0” key as needed to toggle the memory select – M0 or M1. M0 is
the internal memory, and M1 (if installed) is the SD card.
3. To format the selected memory, press the “6” key on the keypad. This
displays a prompt to format, and whether to include new files, with a prompt
No as default response:
<CONFIG><SITE><STUDY><files><STATUS>
Format M1:011 New Files? No
0) m1:0018GB-0018_32768-61015-61086
1) usb:Off
2) STUDY:None
3) EVT:None
Other Maintenance
TROUBLESHOOTING
Battery Troubleshooting
If the display does not turn on at all, try replacing the battery with a known good one.
If the main battery is removed, all data files and the internal clock are retained for
approximately 7 years by a separate lithium battery mounted on the CPU board. The
ADR battery charger may be connected to a unit with the main battery removed
without damage to the unit or the charger.
Also, for road tubes, check the road clamps for pinching of the tubes. Check for
blockages in tubes, and blow out the tubes. If the tubes (or piezos, as well) appear
old or worn, you may need to replace them.
Check whether undercounting could be attributable to axles on different vehicles
hitting the tube sensors simultaneously. If this appears to be the case, either move
the sensor to a different location to reduce the chance of simultaneous hits, or
increase the number of channels by using additional available sensor inputs.
Sabre Reset
To reset the Sabre, at the startup screen:
1. Press the ↑and 0 key, then hold down the ESC key about 5 seconds, until
the prompt for reset appears:
Reset: No?
2. Press the ↑key to select Reset? Yes, then press ENT. This causes the
Sabre to shut down, and restart. When reset finishes, the startup screen
appears.
This appendix discusses connecting the Sabre battery, in cases where the Sabre is shipped
with battery disconnected.
If the ADR Sabre is shipped with battery disconnected, or if there are indications that
the battery may be disconnected, such as if the LCD does not display when the key is
pressed, you can open the Sabre, to see if the internal battery is connected, and
connect if needed.
Warning: Observe all safety precautions when working with electrical circuitry within
the unit. Also take care to prevent damage from electrostatic discharge, and
avoid contact with circuit board traces and components. Failure to do so can
result in personal injury or damage to equipment.
Battery cable
(connected)
5. To connect, align the battery cable connector with the receptor on the circuit
board. The plug and socket are keyed to match for correct insertion.
6. Insert the aligned battery cable plug. The detent lever on the side of the
connector will snap into place and hold when fully inserted.
Battery cable
detent latch
FW: 01.02_1139-MAY_04_2012-14:14:14
240 T45
This appendix describes the procedure to set up the ADR Sabre for event (EVT) file recording
during a study, and then “play back” this file with different study settings.
This appendix describes how to set up the ADR Sabre for event (EVT) file recording
during a study, and then “play back” this file with different study settings. That is, you
can set up and perform a study, recording the event data, and, after reconfiguring the
study, replay event data. You get new results – new .bin files – using the same data,
but with different parameters. You can process the new .bin files as normal.
Note This procedure presumes the user is familiar with how to configure the
Sabre, and that the ADR Sabre has already configured to perform the
required traffic study. The procedure here describes only the steps for
enabling the recording of the EVT file, starting the study, and playing back
the file.
<CONFIG><SITE><study><FILES><STATUS>
0) record: PVR+ BIN+ EVT+ AEF+
1) START-NextInt
2) END-NeverEnd
3) REC_INT-15 Min FREQ-Daily
Note This step only applies if replaying the same study, unchanged. If
you will be making changes to the study, skip this step.
<CONFIG><SITE><STUDY><files><STATUS>
0) M1 :0018GB-0018_32768-61015-61086 *
1) usb:Off
2) STUDY:None
3) EVT:Get 12151537=00002382 Evts
<CONFIG><SITE><STUDY><files><STATUS>
0) M1 :0018GB-0018_32768-61015-61086 *
1) usb:Off
2) STUDY:None
3) EVT:Run 12151537-Yes
0) M1 :0018GB-0018_32768-61015-6108 *
1) usb:Off
2) STUDY:None
3) EVT: 12151537=>0525096_00000000_100%
This section provides additional details for using the harnesses to connect different types of
sensors to the ADR Sabre sensor inputs. The following topics are discussed in detail in this
appendix:
Road tube
inputs
Figure 160 – Sensor connector harnesses – loop/piezo (top) and contact closure
Note Connect the center wire for each sensor lead to the colored wire of the
twisted pair. Connect the shield wire to the black wire of the twisted pair.
For more information on the specific array installation, refer to Chapter 7, Piezo
Arrays, p. 109, or to Chapter 8, WIM Arrays, p. 115.
either separating the data from one array or lane (by “flow” direction) or can combine
the data from a set of arrays into one total.
Channel Mapping – The Channel Mapping setting causes the count of vehicles to
be stored in one or more “channels”. The Channel Mapping option has the following
settings (Separated, Reverse, and Both are not available for array types that cannot
determine a vehicle’s direction):
Both – The count is incremented each time a vehicle passes the array, no matter
in which direction it is traveling. Channel 1 is for array 1, Channel 2 for array 2,
etc.
Separated (by direction) – Count of vehicles from each array is stored in two
channels. Channel 1 contains the count of vehicles in the forward direction
across array 1. Vehicles that are traveling in the reverse direction across array 1
are contained in Channel 2. Note that if more arrays are used, each subsequent
array will have two channels associated with it. The forward direction is defined
as those vehicles that are traveling from the lead sensor to the lag sensor.
Forward –The count is incremented each time a vehicle passes the array in the
forward direction only. The forward direction is defined as those vehicles that are
traveling from the lead sensor to the lag sensor. Vehicles traveling in the reverse
direction are ignored. Each array will have only one channel associated with it.
Reverse –The count is incremented each time a vehicle passes the array in the
reverse direction only. The reverse direction is defined as those vehicles that are
traveling from the lag sensor to the lead sensor. Vehicles traveling in the forward
direction are ignored. Each array will have only one channel associated with it.
User– When using an array in multiple lanes (instances), this setting allows you
to assign a direction per array. For example, one array could be set to “Fwd,” and
another could be “Sep,” for applications where lane usage changes.
Class – The classification of vehicles according to a preset vehicle classification
scheme. The defining criteria of a scheme are called a Class Tree or Class table. The
widely used scheme is Scheme “F” which uses the number, spacing and grouping of
axles to assign each vehicle to one of thirteen definitions of vehicle type. Scheme “F”
is the default scheme in the ADR as supplied, with the addition of a fourteenth “Other”
type and a fifteenth category for “unclassified.”
Classification – The ADR can sort vehicles based on a variety of criteria. Commonly
used criteria are CLASS, SPEED, LENGTH (either wheelbase or chassis), GAP, or
HEADWAY. In setting up the ADR, operators can set the ranges for the criteria (which
are called “Bins”), for example in classification by SPEED, operators can specify the
number of “Speed Bins” and then can specify the limits of each of the bins as 0 to 20
mph and 20 to 30 mph and so on.
Comm ID – Option setting, value from 1 to 65534. This setting is useful when
several units are connected to the same communication device and a communication
with only a specific unit is required.
Continuous File – A binned or PVR file which has one header that includes all set-
up information including the start date and time and will not include an end date time
until a user ends the current recording session. This recording session could span
several days, weeks or months depending on the amount of time users desire to
allow the recorder to continue to recorder without stopping or ending the recording
session.
Daily Files – Is a binned or PVR file which is one file with a file header for each day
that includes all set-up information including the start and end date and time for each
day. These files will have a maximum of 24 hours of data from midnight to midnight or
until a user has stopped the ADR from recording data.
Debounce – Debounce value ensures that phantom signals in tubes or piezo
sensors are not regarded as axles. It is the time set to ignore any pulse after valid
axle detection. The range of possible values is from 1 to 998 msec. If the ADR is
undercounting, reduce the debounce time; if the ADR is over-counting, increase the
debounce time.
DST – Is the Daylight Saving Time adjustment, users have the option to allow the
ADR to automatically adjust for the new time
Factory Default Settings – These settings are the default settings as defined by
the firmware which have been defined and set by Peek Traffic Corp. The default
value settings may be different from one version firmware to another.
Flow – When any vehicle crosses any sensor array, it is assigned a “flow,” indicating
direction of travel. The assigned flow on single sensor arrays is a + (plus) or forward.
Arrays with two sensors in the same lane assign either a (+) plus or a (-) minus to a
vehicle passage as determined by the sequence of lead and lag sensor activations
(the lead is the first sensor activated by a vehicle traveling in the given traffic
direction, lag is the second). Travel from lead to lag sensor is assigned (+) flow
(forward) and travel from lag to lead is assigned (-) flow (reverse).
Gap – Gap is the time (in milliseconds) between the trailing axle of a vehicle and the
leading axle of the next vehicle going in the same direction. This measurement is
available when using piezo or tube sensors. Alternatively, it is the time between the
rear of one vehicle and the front of the following vehicle when using loop sensors.
Gap studies using road tube sensors should use a count ratio setting of 2.00 (or some
other means) to determine the end of a vehicle and to prevent inter-axle times
(spacings) from being recorded as gap times. One method is to combine studies as a
matrix, such as classification by gap by lane (channel) using 2 or four road tubes.
GPS – Global Positioning System. A GPS device can be connected to the ADR
Sabre to provide the precise latitude and longitude coordinates for the study location.
Headway – The time (in milliseconds) between the front axle of one vehicle and the
front axle of the next vehicle going in the same direction. This measurement is
available when using piezo or tube sensors. Alternatively, it is the time between the
front of one vehicle and the front of the next vehicle when using loop sensors.
Idle – Status indicating the ADR is not currently recording (“not armed”).
Inductive Loop (Loop) – A inductive loop detector is the (Loop and lead-in wire)
which forms an electrical circuit in each lane of traffic which are then connected to a
loop module.
Lag Sensor – This indicates the second sensor typically activated in a two-sensor
array, relative to a “forward” vehicle travel (in a “reverse” or opposite vehicle direction,
the lag sensor is activated first).
Lane – Within the Sabre array assignments, lane refers to an instance of the
selected array type. If you select two lanes, for example, this actually means you are
using two arrays of the selected type, not one array across two lanes. The term "lane"
is also used to refer to a physical lane on the road, typically delineated from the rest
of the road with a painted line or physical barrier.
LCD – Liquid Crystal Display refers to the ADR Sabre’s screen which displays the
menus for setup.
Length – Length is the total wheelbase length when measured by piezo or tube
sensors, or the overall length (chassis) when using loop sensors.
Loop – Loop, an inductive wire loop sensor. Typically used in long-term testing sites.
Marked Files – Binned, event, or PVR files that have previously been transferred or
marked as a read file; these will not be included in file transfers of “New” files.
Memory – Is the available room for storing files such as bin, PVR and set-up files in
the Sabre.
New Files – data files such binned or PVR files that have never been downloaded
and marked as “read,” these files may be shown as closed book in the pc software
(such as Viper) which indicates that the file has never been read before.
Per-Vehicle-Record (PVR) – Per-Vehicle-Records are individual records of each
vehicle that passes over sensors that are interfaced to the Sabre. Each record can
include items such as (if the ADR is equipped and configured for) Number of Axles,
Speed, Class, Headway, Gap, Vehicle Status, Loop Length, Total Wheelbase, Axle
Spacing, Gross Weight, Axle Weights, Temperature and Alarm codes.
Piezo (Axle) Sensor – An in-the-road or over-the-road axle sensor that is used in
an array to sense axle presence for vehicle classification, counting, etc.
PVR –Per vehicle records. Data gathered about individual vehicles that pass over the
Sabre’s sensors, such as weight and speed.
Road Tube – a simple rubber tube that can be used to send pressure pulses to any
ADR unit that accepts road tube inputs, whenever a vehicle drives over the tube.
Suited to short-term studies because of its portability, this Is a pneumatic axle sensor
that is used as part of portable traffic data collection system.
RT – see Road Tube.
Serial Cable– A cable that is used between the serial port of the Sabre and a
computer’s serial port
Study File – Unique instructions that can be saved as a “setup file” (.stp) and the file
can then be reloaded as needed. Loading a “setup file” can be faster and easier than
configuring a study anew.
Site –The physical location of traffic data collection equipment, and also the name
entered for the study identification, such as “Route 301 and Smith Road. The “Site”
and “STA” information can be used in combination to uniquely identify the Sabre unit
and the study data which is collected with it. For example, “Site” may specify the
general location, while the STA is used to distinguish specific device sites within the
area; in this way, recording from multiple sites in the area can help create a
comprehensive study of the overall area traffic flow of the area.
Speed – Speed is the scalar velocity of a vehicle as measured by the travel time
between from point A (lead) to point B (lag). Point A and point B can be two sensors
in the same lane of travel. Speed may be displayed as either miles per hour (mph) or
kilometers per hour (kph).
Station – A “Station” (“STA”) name is useful in uniquely identifying a study location.
When setting up an ADR Sabre for operation at a location, you can enter a Site and a
Station identifier. You can set the Station field to contain any useful reference
information desired in conjunction with the Site field.
Street-Link – Hand-held device that can provide operational status and feedback for
Sabre and other devices, and also provide GPS location and time sync.
Study – The study is the result of collecting data on vehicle traffic. Depending on the
sensor arrays selected a user may have the following to select from – Volume,
Speed, Class, Headway, Gap, and Vehicle Length.
TOPS™ – Traffic Operations and Planning Software. This is a Windows-based central
system software package available from Peek Traffic that allows users of Peek ADR
devices to store their data in a central location. The software manages the data and
can be used to automate data gathering and to generate data reports and exports.
USB – Universal Serial Bus, a type of serial connection. The ADR Sabre has a slot for
a USB jump drive (DEVICE), and a slot for connecting to a pc via a micro B USB
cable plug (HOST).
Viper – Windows software application for use with Peek’s line of ADR advanced
traffic counters, Viper is a central data collection and processing tool for use with
traffic count and classification data generated by Peek’s ADR line of advanced traffic
counters. Part of the AVCC line, Viper performs common processing operations such
as data retrieval and file conversion in the background, after set up, without need of
additional user interaction
Vision – Windows software application for use with Peek’s line of ADR advanced
traffic counters (a “field” version of the full-featured Viper software).
Volume – Volume is the count of vehicles. In the Setup procedure, the volume study
type is called “Channel Study Type.”
Comm ID ..................................................... 37
A Common Study Settings .............................. 49
communication............................................. 35
Ancillary Hardware...... 13, 16, 36, 37, 142, 143
Communications Ports ................................. 36
arm the Sabre ........................................ 63, 77
config ........................................................... 30
ASCII Event File .......................................... 41
Configure and Run Study to Record Event File
AutoCal ..................................................... 122
.............................................................. 154
Axle (Piezo) and Loop Arrays .................... 132
Connecting contact closure devices ........... 160
Axle-Loop-Axle Array ......... 124, 126, 128, 132
Connecting inductive loops ........................ 159
Connecting mixed arrays ........................... 160
B Connecting road tubes ................................. 96
BASIC LOOP THEORY ............................. 106 Connecting the battery ....................... 149, 150
Battery ....................................................... 142 Connecting to the sabre ............................. 158
Battery Check .............................................. 26 Connecting WIM or Piezo Sensors............. 159
Battery Troubleshooting ............................. 146 Connectors .................................................. 16
battery voltage ........................................... 142 Conventions ................................................. 10
baud rate ..................................................... 36 CTREE .................................................. 31, 70
Bin Range Values ........................................ 56
Bin Settings ................................................. 54 D
Bin Setup, example...................................... 59
Data File Types............................................ 53
Bin Sub-menu .............................................. 55
Data Files .................................................... 69
Binned ............................................. 41, 43, 54
Date and time .............................................. 33
debounce ....................... 83, 99, 115, 121, 147
C Debounce Adjustments, roead tube ............. 83
calibration factor ........................................ 122 Debounce Setting, piezo ............................ 115
channel bins ................................................ 57 Debounce Setting, WIM ............................. 121
Check Battery Status ................................... 45 Delete Stored Files .................................... 143
Check Date and Time .................................. 48 Device port ............................................ 39, 40
Check Memory Status ................................. 46 Directional Tube Count Array ....................... 89
Checking the Battery ................................. 142 Disarm the ADR ........................................... 64
Checking the Condition of the Sensors ...... 145 DST ............................................................. 33
Classification Tree File ................................ 69
Cleaning the ADR Sabre............................ 145 E
Clearing Memory ................................. 46, 143
Event File Retrieval and Playback .............. 155
Columns (Bins) ............................................ 57
Event files ...................................... 41, 54, 143
81-1425