Wavetronix smartsensor advance User Manual

Page 1
SmartSensor Advance
USER GUIDE
Page 2
SmartSensor Advance
USER GUIDE
www.wavetronix.com 78 East 1700 South Provo, Utah 84606 801.734.7200
Page 3
Wavetronix, SmartSensor, Click, Command, and all associated product names and logos are trademarks of Wavetronix LLC. All other products or brand names as they appear are trademarks or registered trademarks of their respective holders.
Protected by U.S. Patent Nos. 6,556,916; 6,693,557; 7,426,450; 7,427,930; 7,573,400; 7,889,097; 7,889,098; 7,924,170; 7,991,542; Canadian Patent No. 2461411; 2434756; and European Patent Nos. 1435036; 1438702; 1611458. Other U.S. and international patents pending.
e Company shall not be liable for any errors contained herein or for any damages arising out of or related to this document or the information contained therein, even if the Company has been advised of the possibility of such damages.
is document is intended for informational and instructional purposes only. e Company reserves the right to make changes in the specications and other information contained in this document without prior notication.
FCC Part 15 Compliance: e Wavetronix SmartSensor sensors comply with Part 15 of the Federal Communications Commission (FCC) rules which state that operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesirable operation. FCC compli­ance statements for applicable optional modules are to be found in the module specications. Unauthorized changes or modications not expressly approved by the party responsible for compliance with the FCC rules could void the user’s authority to operate this equipment.
Disclaimer: e advertised detection accuracy of the Wavetronix SmartSensor sensors is based on both external and internal testing, as outlined in each product’s specication document. Although our sensors are very accurate by industry standards, like all other sensor manufacturers we cannot guarantee perfection or assure that no errors will ever occur in any particular applications of our technology. erefore, beyond the express Limited Warranty that accompanies each sensor sold by the company, we oer no additional representa­tions, warranties, guarantees or remedies to our customers. It is recommended that purchasers and integrators evaluate the accuracy of each sensor to determine the acceptable margin of error for each application within their particular system(s).
WX-500-0052 2/2012
Page 4
Contents
Chapter 1 Introduction 5
SmartSensor Advance Package 6 • Selecting a Detection Method 6 • Selecting a Mounting Location 8
Part I Installing the SmartSensor Advance
Chapter 2 Installing the SmartSensor Advance 15
Selecting the Mounting Height 15 • Attaching the Mount Bracket to the Pole 16 • Attaching the Sensor to the Mount Bracket 16 • Aligning the Sensor to the Roadway 17 • Apply­ing Silicon Dielectric Compound 19 • Connecting the Smart­Sensor 6-conductor Cable 20 • Grounding the Sensor 21
Chapter 3 Connecting Power and Surge Protection 23
Mounting the Backplate 24 • Connecting AC Power 24 • Providing System Surge Protection 28 • Terminating the 6-conductor Cables 30 • Contact Closure Connections 32
Part II Using SmartSensor Manager Advance
Chapter 4 Installing SmartSensor Manager Advance 35
Installing SSMA 35
Chapter 5 Communication 39
Serial Connection 40 • Internet Connection 41 • Virtual Connection 42 • Multi-drop Network 45 • Address Book 46 •
Page 5
Viewing Connection Information 46 • Uploading the Sensor’s
Embedded Software 49
Chapter 6 Sensor Settings 51
General Tab 51 • Communication Tab 52
Chapter 7 Sensor Configuration 55
1. Installation Details 56 • 2. Automatic Radar Conguration 58 • 3. Manual Radar Adjustment 59
Chapter 8 Channels-Alerts-Zones 65
Channels 66 • Alerts 76 • Zones 76
Chapter 9 Verify Channels-Alerts-Zones 83
Right Sidebar 84 • Roadway Display 90 • Left Sidebar 97
Chapter 10 Setup Output Communications 101
Conguring Data Push Parameters 101
Chapter 11 Templates 105
Creating a Channel Template 106 • Importing a Channel Template 106 • Copying/Pasting Channels, Alerts and Zones
108
Chapter 12 Tools 109
Backup/Restore Tool 110 • Beam Alignment Tool 113 • Serial Terminal 114 • Rack Card Tools 115
Chapter 13 Programming Contact Closures 119
Click 112/114 Contact Closure Cards 119 • Click 172/174 Contact Closure Cards 120 • Click 104 Contact Closure
Module 123
Chapter 14 Appendix 127
Appendix A – Cable Connector Denitions 127 • Appendix B – Appendix B - Cable Lengths 129 • Appendix C – Direct Serial Connections 132 • Appendix D – Target Roll Angles
for Alignment 133
Page 6
In this chapter
SmartSensor Advance Package Selecting a Detection Method Selecting a Mounting Location
e Wavetronix SmartSensor Advance™ and Wavetronix SmartSensor Advance Extended Range detect and continuously monitor the progression of moving trac out to a maxi­mum range of 600 ft. (182.9 m) and 900 ft. (274.3 m) respectively.
Both trac sensors are designed for use on the approaches to signalized intersections. ey are used to alert the trac controller of a vehicle’s arrival based upon the incoming range, speed, and estimated time-of-arrival of each detected vehicle for applications such as high­speed dilemma zone protection and queue reduction. In addition, SmartSensor Advance Extended Range allows you to prioritize dilemma zone protection based upon the discov­ery range of trucks and passenger cars.
SmartSensor Advance and SmartSensor Advance Extended Range monitor vehicle trac ow through the use of a 10.525 GHz (X band) operating radio frequency. Both sen­sors utilize Digital Wave Radar™ technology to provide a reliable Frequency Modulated Continuous Wave. SmartSensor Advance Extended Range uses a new form of frequency modulation to achieve its extended reach.
e SmartSensor Advance User Guide is divided into two parts. Part one provides a step-
by-step process for installing the SmartSensor Advance and the SmartSensor Advance Extended Range, including mounting and alignment guidelines. Part two provides instruc­tions for installing and using the SmartSensor Manager Advance software, including in-
Introduction
Page 7
6 INTRODUCTION  SMARTSENSOR ADVANCE USER GUIDE
structions for both automatic and manual sensor congurations. Any questions about the information in this guide should be directed to Wavetronix or your distributor.
Caution
Do not attempt to service or repair this unit. This unit does not contain any compo­nents and/or parts serviceable in the field. Any attempt to open this unit, except as expressly written and directed by Wavetronix, will void the customer warranty. Wavetronix is not liable for any bodily harm or damage caused if service is attempted or if the back cover of the SmartSensor unit is opened. Refer all service questions to Wavetronix or an authorized distributor.
SmartSensor Advance Package
A typical SmartSensor Advance package will commonly include:
10.525 GHz SmartSensor Advance radar trac sensor SmartSensor mounting kit SmartSensor 6-conductor cable SmartSensor Advance preassembled backplate SmartSensor Manager Advance (SSMA) software SmartSensor Advance User Guide SmartSensor Advance Quick-reference Guides
Check the packing slip for actual contents. If any of these items are missing, note the serial number located on the back of the sensor and contact your distributor.
Selecting a Detection Method
Consult the Wavetronix guidelines for integration of SmartSensor Advance into your traf­c control system. For dilemma zone protection applications, integration guidelines can be found on the Wavetronix website and Wavetronix application notes. Contact your dealer or
a Wavetronix Technical Services representative if the application-specic documentation
does not fully answer your system integration and conguration questions.
Some examples of trac control applications include:
Dilemma zone protection using green extension Truck signal priority using green extension Dilemma zone protection using green extension with an Advanced Warning Sign
(AWS)
Dilemma zone protection using red extension
Page 8
INTRODUCTION  SMARTSENSOR ADVANCE USER GUIDE 7
Queue clearance Ecient green extension Queue management
Note
For queue management the SmartSensor Advance Extended Range is recommended because it allows you to see a greater range and also provides a view of the stop bar. The SmartSensor Advance Extended Range is also recommended for wrong-way detection applications. Contact Wavetronix Technical Services for more information.
If your application is dilemma zone protection and/or truck signal priority, SafeArrival™ technology is recommended because it provides signicant safety and eciency advan­tages when compared with traditional point-based protection. Conguring SafeArrival technology for dilemma zone protection is as simple as selecting the arrival times, ranges and speeds that are unsafe and warrant protection. Conguration SafeArrival technology for truck signal priority requires the additional conguration of the truck discovery range threshold available with SmartSensor Advance Extended Range.
For green extension, arrival times between 2.5 and 5.5 seconds, ranges from 100 to 500 ft. (30.5 to 152.4 m) and speeds above 35 mph (56 kph) are generally considered unsafe for passenger vehicles. For truck signal priority, arrival times between 2.5 and 7.5 seconds, ranges from 100 to 900 ft. (30.5 to 274.3 m) and speeds above 35 mph (56 kph) are gener­ally considered unsafe for trucks, buses and other large vehicles.
However, engineering judgment needs to be used in selecting these parameters. For ex­ample, 2.5 to 5.5 second arrival times are nominal values based upon general 10% and 90% stopping probabilities. Your agency may suggest protection of slightly dierent arrival times for a particular type of high-speed approach.
It may be helpful to consult your agency’s guidelines to verify which trac conditions war­rant protection at your intersections. Location of point-detection zones, passage time and design speed can often be used to infer the arrival times and ranges that warrant protection. In addition, the minimum speed that would warrant installation of a dilemma zone protec­tion system may be used as a guideline for the lowest speed to be protected.
If you elect not to use SafeArrival technology, you can also congure SmartSensor Advance to match your agency’s loop-based dilemma zone protection guidelines. Before doing so, it is recommended that you explore the benets provided by SafeArrival technology in detail.
Page 9
8 INTRODUCTION SMARTSENSOR ADVANCE USER GUIDE
Selecting a Mounting Location
Consider the following guidelines when selecting a mounting location:
Detection coverage – Position the sensor so that it will be able to reach all the speci-
ed advanced detection zones. Also consider that the sensor will track vehicles as they enter and exit desired detection zones. Accordingly, the sensor will often work better if you position detection coverage to track vehicles for several feet before they reach the rst zone. e closest detection zone provided by SmartSensor Advance and Smart­Sensor Advance Extended Range is 50 ft. (15.2 m) from the location of the sensor. e farthest detection zone provided by SmartSensor Advance Extended Range is 900 ft. (274.3 m). e farthest detection zone provided by SmartSensor Advance is 600 ft. (182.9 m). e sensor can detect incoming or outgoing trac, and lters out the opposite direction trac. Usually the sensor is used to detect incoming trac. With SmartSensor Advance Extended Range, incoming large vehicles are typically discov­ered by about 750 ft. (228.6 m) and small vehicles are typically discovered about 600 ft (182.9 m) from the sensor. With SmartSensor Advance, most incoming large vehicles are discovered by about 500 ft. (152.4 m) and most small vehicles are discovered about 400 ft (121.9) from the sensor.
Figure I.1 – Mounting Locations
Line-of-sight – Position the sensor so that it will have line-of-sight to the entire de-
tection area of interest. Avoid structural occlusion including trees, signs, and other roadside structures.
Closest roadside – If you install the sensor on the side of the road (instead of over-
head), select the location closest to the lanes of interest. is will prevent departing trac from occluding approaching detections.
Through-Movement Detection – If only through-movement detection is desired, po-
Page 10
INTRODUCTION  SMARTSENSOR ADVANCE USER GUIDE 9
sition the sensor to avoid detection of turn-only lanes. Consider using speed lters to remove the impact of turning vehicles.
Mounting Height – Mounting the sensor as high as possible is recommended to reduce
same lane occlusion. A maximum of 40 ft. (12.2 m) and minimum of 17 ft. (5.2 m) is recommended. If the sensor is higher than 30 ft. (9.1 m), the oset should be less than 50 ft. (15.2 m) to increase accuracy.
Mounting Oset – Mounting the sensor closer to the lanes of interest will usually in-
crease detection accuracies. A maximum oset of 50 ft. (152.4 m) is recommended, but the sensor will still reliably track vehicles at further osets. Mounting with a smaller oset will generally increase line-of-sight.
Cable Length – Make sure that you have sucient homerun and sensor cabling. With
the newer models, cable runs as long as 1500 ft. (457.2 m) are achievable using 24
VDC operation and RS-485 communications. Older models supported up to 600 ft.
(182.9 m). Consult Appendix B for more information.
Suspended Electrical Cables –e sensor is designed to work in the presence of
suspended power lines and other electrical cabling, however these cables should be mounted at least ten feet away from the front of the sensor.
Neighboring Structures and Parallel Walls – For best performance, it is preferred that
the sensor be mounted without signs or other at surfaces mounted directly behind it. is will help reduce multiple reection paths from a single vehicle.
e SmartSensor Advance should be mounted using one of the following options (see Figure I.1):
1 On a vertical pole – e preferred mounting location for the SmartSensor Advance or
SmartSensor Advance Extended Range is often a vertical pole near the stop bar. Verti­cal poles are typically installed on the roadside of the approach near the stop bar to support a mast arm, span wire or luminaire. ese poles often extend as high as 30 ft. (9.1 m) or more, allowing the sensor to be mounted high enough to reduce occlusion. is mounting location is typically very safe for installation.
2 On a luminaire – is mounting location will often reduce the oset and increase the
mounting height (a maximum of 40 ft. (12.2 m) is recommended). Make sure the luminaire can support the load of the sensor. is mounting location is typically very safe for installation.
3 The backside of the opposing mast arm – By mounting on the backside of the mast
arm, opposite the signal heads for the opposing direction of travel, the sensor can be placed near the lanes of interest. e minimum mounting height is 17 ft. (5.2 m), but higher mounting is recommended to minimize occlusion. When appropriate, a vertical extension can be used; the extension should have the ability to freely rotate the sensor for alignment. e sensor should be mounted as far out on the mast arm as possible to avoid potential occlusion issues with stopped vehicles in a left-turn pocket.
4 The front side of the mast arm – e sensor can be installed on the mast arm with
the signals for the approach of interest. SmartSensor Advance Extended Range is recommended at this mounting location, because typically 100 feet or more of the sensor’s range is used to cross the width of the intersection. For SmartSensor Advance Extended Range, the eective maximum range of the sensor is still as high as 800 feet
Page 11
10 INTRODUCTION  SMARTSENSOR ADVANCE USER GUIDE
from the stop bar at this mounting location. is mounting location is also recom­mended on approaches where dynamic red extension will be used in tandem with the green extension. is mounting location can also be helpful if the minimum green time is so short that vehicles in the queue clearance zone do not start moving before the minimum green timer expires.
e SmartSensor Advance or SmartSensor Advance Extended Range can also be mounted at the back of the dilemma zone on an existing luminaire or custom pole if the luminaire already exists, power is available and a wireless communication link can be used to avoid trenching. Wavetronix has integrated wireless solutions readily available for this type of installation.
Page 12
Page 13
Page 14
Part 1
Installing the SmartSensor Advance
Chapter 1 – Installing the SmartSensor Advance Chapter 2 – Connecting Power and Surge Protection
Page 15
Page 16
In this chapter
Selecting the Mounting Height Attaching the Mount Bracket to the Pole Attaching the Sensor to the Mount Bracket Aligning the Sensor to the Roadway Applying Silicon Dielectric Compound Connecting the SmartSensor Cable to the Sensor
1
Installing the SmartSensor Advance is quick and easy. Once installed, SmartSensor Ad­vance requires little or no on-site maintenance. is chapter describes the installation pro­cess, including how to attach the sensor to the pole and how to correctly align the sensor.
Warning
Caution should be used when installing any sensor on or around active roadways. Serious injury can result when installation is performed using methods that are not in accordance with authorized local safety policy and procedures. Always maintain an appropriate awareness of the trac conditions and safety procedures as they relate to specific locations and installations.
Selecting the Mounting Height
Select a mounting location within the recommended range of osets from the center of
Installing the SmartSensor Advance 1
Page 17
16 CHAPTER 1  INSTALLING THE SMARTSENSOR ADVANCE
the lanes of interest. Osets of less than 50 ft. (15.2 m) on either side of the center of the desired lanes are recommended.
e minimum recommended mounting height is 17 ft. (5.2 m) and the maximum recom­mended mounting height is 40 ft. (12.2 m). Higher than 30-ft. (9.1-m) mounting heights are acceptable if the sensor is within 50 ft. (15.2 m) of the road. Depending on the site and
type of trac, some vehicles may be momentarily occluded by other vehicles. Vehicle-based
occlusion favors detection of large vehicles, which may be acceptable for dilemma zone protection applications. It may be necessary to increase the height of the sensor to reduce occlusion, or use controller passage time to bridge the gap caused by occlusion.
Attaching the Mount Bracket to the Pole
Before attaching the mount bracket to the pole, rst make sure that your cables are long enough to support the sensor height and the distance from the sensor to the cabinet.
Follow the steps below to correctly attach the mount to the pole (see Figure 1.1):
1 Insert the stainless steel straps through the slots in the mount bracket. 2 Position the mount on the pole so that the head of the mount is pointing towards the
middle of the lanes of interest.
3 Tighten the strap screws, but keep the straps adjustable for future sensor alignment.
Figure 1.1 – Attaching the Mount Bracket to the Pole
Attaching the Sensor to the Mount Bracket
1 Align the bolts on the sensor’s backplate with the holes in the mount bracket. e
8-pin connector on the sensor should be pointing towards the ground.
2 Place the lock washers onto the bolts after the bolts are in the mount bracket holes. 3 read on the nuts and tighten (see Figure 1.2).
Page 18
CHAPTER 1  INSTALLING THE SMARTSENSOR ADVANCE 17
Figure 1.2 – Attaching the Sensor to the Mount Bracket
Aligning the Sensor to the Roadway
In most applications, the goal is to position the beam’s elliptical footprint along the road­way. is is done by pointing the hot spot of the sensor’s beam (middle of the sensor) at a target location, and then rolling the sensor so that the beam’s footprint lines up with the road.
e standard sensor mount has three axes of rotation: straps around pole, vertical and hori­zontal swivel points. Make sure that your sensor mount’s degrees of freedom are adjustable until you have completed your alignment.
Follow the steps below to correctly align the sensor:
1 Point the sensor towards the target on the road by tilting the sensor down and pan-
ning it to the left or right as necessary (see Figure 1.3). e target location is typically between 30 and 80 ft. (9.1 and 24.4 m) upstream from the sensor in the center of the
lanes of interest. See Table 1.1 below to nd the appropriate target distance.
Height (ft / m)
Oset (ft / m)
17 / 5.2 20 / 6.1 25 / 7.6 30 / 9.1 35 / 10.7 40 / 12.2
0 / 0 40 / 12.2 45 / 13.7 55 / 16.8 60 / 18.3 70 / 21.3 75 / 22.9
5 / 1.5 45 / 13.7 45 / 13.7 60 / 18.3 65 / 19.8 70 / 21.3 80 / 24.4
10 / 3 50 / 15.2 50 / 15.2 60 / 18.3 65 / 19.8 75 / 22.9 80 / 24.4
15 / 4.6 50 / 15.2 55 / 16.8 65 / 19.8 70 / 21.3 75 / 22.9 80 / 24.4
20 / 6.1 55 / 16.8 55 / 16.8 65 / 19.8 75 / 22.9 80 / 24.4 90 / 2 7.4
25 / 7.6 60 / 18.3 65 / 19.8 65 / 19.8 75 / 22.9 80 / 24.4 90 / 27.4
30 / 9.1 65 / 19.8 70 / 21.3 75 / 22.9 80 / 24.4 85 / 25.9 95 / 28.9
35 / 10.7 70 / 21.3 75 / 22.9 85 / 25.9 85 / 25.9 95 / 28.9 95 / 28.9
40 / 12.2 80 / 24.4 90 / 27.4 90 / 2 7.4 95 / 28.9 95 / 28.9 100 / 30.4
45 / 13.7 95 / 28.9 100 / 30.4 100 / 30.4 100 / 30.4 100 / 30.4 105 / 32
50 / 15.2 100 / 30.4 100 / 30.4 105 / 32 110 / 33.5 115 / 35 120 / 36.6
Table 1.1 – Target Distance (ft / m)
Page 19
18 CHAPTER 1  INSTALLING THE SMARTSENSOR ADVANCE
To verify your pointing, look at the road from directly behind the sensor. If from this
vantage point you do not see the target location, then the sensor is pointed in the right general direction.
Note
With roadside alignments, it may be beneficial to use a pointing assistant (e.g. a Quick-Grip beam clamp) for precise alignment. A beam clamp can be attached to the sensor and aimed by looking down the length of the beam to verify pointing.
Height
Oset
Target
Distance
Figure 1.3 – Pointing the Sensor
2 Roll the sensor using the backplate, while keeping it pointed at the target location, to
align the elliptical beam. If the sensor is mounted directly above the lanes of interest, you will not need to roll the sensor. (See Appendix D for target roll angles.)
3 Align the top and bottom center-tabs of the sensor with the center of the lanes of
interest. It may be benecial to use a 90 degree edge from a rafter’s square or other framing device to correctly align the sensor. Place the parallel edge of the framing de­vice on the top or bottom of the sensor and then line the perpendicular edge with the roadway (see Figure 1.4).
Page 20
CHAPTER 1  INSTALLING THE SMARTSENSOR ADVANCE 19
Center Tabs
Figure 1.4 – Aligning the Sensor with the Roadway
4 Once the sensor is correctly pointed and rolled, secure the mounting bracket screws.
e connector should be pointing towards the center of the lanes of interest.
If you are using the sensor on a curved road, you can aim the sensor so that it bisects the curve of the road and still hits your nearest and farthest ranges of interest. If the sensor is mounted near the outside edge of the curved road, you may be able to bisect the curve with little or no roll. If the road curves dramatically, you may need to reduce the down tilt of the sensor so that the beam fans out more at the far ranges. In order to help you visualize custom alignments like this, an alignment tool is available in the conguration software
(see Beam Alignment Tool).
Applying Silicon Dielectric Compound
1 Tear the tab o the tube of silicon dielectric compound. 2 Squeeze about 25% of the silicon into the connector at the base of the SmartSensor
Advance (see Figure 1.5).
3 Wipe o any excess compound.
Page 21
20 CHAPTER 1  INSTALLING THE SMARTSENSOR ADVANCE
Figure 1.5 – Connector Receptacle (left) and Grounding Lug (right)
Connecting the SmartSensor 6-conductor Cable
e next step is to plug the SmartSensor 6-conductor cable into the connector. e sensor connector is keyed to ensure proper connection (see Figure 1.6); simply twist the plug end of the connector clockwise until you hear it click into place.
Figure 1.6 – Sensor 6-conductor Cable Connector
To avoid undue movement from the wind, strap the 6-conductor cable to the pole or run it
through a conduit, but leave a small amount of slack at the top of the cable to reduce cable strain. Route the cable from the sensor location back to the main trac cabinet.
To set up your network in an orderly fashion, it is recommended that labeling be used on
the service end of each SmartSensor 6-conductor cable. A convenient way to label the cables is to mark the last seven digits of the serial number on each sensor and the direction of trac monitored (see Figure 1.7).
Page 22
CHAPTER 1  INSTALLING THE SMARTSENSOR ADVANCE 21
Figure 1.7 – Service End Labeling
Grounding the Sensor
e SmartSensor Advance must now be grounded:
1 Connect a grounding wire to the grounding lug on the bottom of the sensor (see
Figure 1.5).
2 Connect the other end of the grounding wire to the earth ground for the pole that
the sensor is mounted on. Do not attempt to run the grounding wire back to the main trac cabinet.
Page 23
Page 24
In this chapter
Mounting the Backplate Connecting AC Power Providing System Surge Protection Terminating the SmartSensor 6-conductor Cable Contact Closure Connections
2
After installation, each SmartSensor Advance will need to be integrated into the main trac cabinet for power and surge protection. is chapter contains information on how to provide power and surge protection to the intersection preassembled backplate located in the main trac cabinet.
e intersection preassembled backplate is 11 in. (28 cm) wide and 11.5 in. (29.2 cm) high. Also available to use are the intersection preassembled 19-inch rack for server racks and the intersection segmented preassembled backplate for easier installation in trac cabinets. All wiring on the rack and backplates is done using stranded wires with wire ferrules for screw terminal connections (see Figure 2.1).
Connecting Power and
Surge Protection 2
Page 25
24 CHAPTER 2  CONNECTING POWER AND SURGE PROTECTION
Figure 2.1 – Intersection Preassembled Backplate
Please refer to the Click quick-reference guides for more comprehensive product instruc­tions. Chapter 12 contains information on how Click products make the sensor compatible with all standard control cabinets.
A pinout diagram showing the sensor cable’s pin-out and appropriate connection points can be found in Appendix A of this document.
Mounting the Backplate
Use the following steps to mount the backplate in the trac cabinet:
1 Locate the area planned for mounting the backplate. e backplate can usually be
mounted on the side panel of a NEMA-style cabinet.
2 Attach the backplate with the U-channel mounting screws.
Note
If you have a 330 series (170/2070 style cabinet) with a 19-inch EIA rack, please con­tact Wavetronix Technical Services for assistance. Wavetronix can provide modified backplates that attach to a 19-inch rack.
Connecting AC Power
Since SmartSensor Advance operates on 10–28 VDC, the intersection preassembled back­plates provide an AC power conversion option. e backplate includes an AC to DC power converter, power surge and circuit breaker.
Page 26
CHAPTER 2  CONNECTING POWER AND SURGE PROTECTION 25
Warning
Make sure power to AC mains is disconnected while wiring the AC input. If your in­stallation does not require AC power, you will need to use surplus DC power inside he trac cabinet. In this case, Wavetronix recommends you use the Click 221 (8 AC surge protector) to protect the backplate and SmartSensor Advance units from DC surges.
Figure 2.2 – Connecting AC Power to the Preassembled Backplate
Use the following steps to connect power to the AC terminal block on the bottom DIN rail (see Figure 2.2):
1 Connect a neutral wire (usually a white wire) to the bottom side of the terminal block
labeled “N” for neutral.
2 Connect a ground wire (usually a green wire) to the bottom of the terminal block la-
beled “G” for ground. (see the Wiring Protective Earth Ground section below).
3 Connect a line wire (usually a black wire) to the bottom of the terminal block labeled
“L” for line.
4 Turn on AC mains power. 5 Press the circuit breaker switch on the left side of the top DIN rail to switch power to
the backplate. e switch is on if the button is below the level of the device housing; the switch is o if the button is raised above the surface of the housing.
6 Verify that DC power is properly regulated by making sure the DC OK LEDs are il-
luminated on the Click 201/202/204.
Page 27
26 CHAPTER 2  CONNECTING POWER AND SURGE PROTECTION
Caution
An authorized electrical technician should install the intersection preassembled backplate. Persons other than authorized and approved electrical technicians should NOT attempt to connect the backplate to a power supply and/or trac control cabi­net, as there is a serious risk of electrical shock through unsafe handling of the power source. Extreme caution should be used when connecting the backplate to an active power supply.
e AC power conversion section of the backplate will come pre-wired as shown in Figure
2.3. e three main components of the AC power conversion section include:
Click 201/202/204 AC to DC converter – A Click 201 provides 1 A of power and is
capable of powering a single sensor; a Click 202 provides 2 A and can power two sen­sors; a Click 204 provides 4 A and can power four sensors.
Click 210 circuit breaker – Interrupts power during overload conditions and provides
a convenient way to turn power on and o for the entire system.
Click 230 AC surge protector – Helps protect equipment from current surges on the
power lines.
Figure 2.3 – AC Power Conversion
Wiring Protective Earth Ground
All connections are surge protected when the protective earth ground is wired to the PE terminal block on the backplate. Normally, the backplate should be mounted to the chassis of the cabinet to provide a ground path. It is strongly recommended that you provide a low impedance protective earth connection.
Page 28
CHAPTER 2  CONNECTING POWER AND SURGE PROTECTION 27
Follow the steps below to provide a low impedance protective earth connection:
1 Connect one end of a protective earth ground wire to the bottom of the PE terminal
block. A 10 AWG stranded wire is recommended for protective earth ground connec­tions and is also the largest that will t in the terminal block.
2 Connect the other end of the protective earth ground wire to a protective earth screw
terminal within the main trac cabinet.
Controlling DC Power Distribution
e Click 210 circuit breakers provide a convenient way to turn power on or o for each
sensor independently (see Figure 2.4). To enable or disable DC power to the backplate,
press the main circuit breaker (left side of upper DIN rail); to enable or disable DC power to an individual sensor, press the individual circuit breaker (left side of each sensor’s set of terminal blocks).
Push this button to
turn power on or o.
Figure 2.4 – DC Power Distribution
Note
The switch is ON when the switch button is level with the device housing; the switch is OFF when the switch button is raised above the housing.
e four-approach preassembled backplate has 24 VDC power wired from the output of the AC to DC convertor into a 5-position screw terminal on the left side of the T-bus (see Figure 2.5). e green T-bus conducts DC power and RS-485 communications from the left to the right side of the modules; the gray T-bus conducts only DC power from the left
to the right side of the modules.
Page 29
28 CHAPTER 2  CONNECTING POWER AND SURGE PROTECTION
( )
( )
Power
RS-485
red wire
black wire
+24 VDC
-DC
+RS-485
GND
-RS-485
Figure 2.5 – T-bus Pinout Diagram
Providing System Surge Protection
e Click 222 system surge protector is designed to prevent electrical surges conducted along underground cables from damaging the cabinet equipment (see Figure 2.6).
Figure 2.6 – Click 222 Faceplate
Note
The SmartSensor Advance has built-in surge protection and so there is no need to use a pole-mount box for surge protection on the sensor side of the cable. However, it is strongly recommended that the sensor be connected to a surge protection device in the main trac cabinet. If you choose not to use surge protection in your main trac cabinet, please contact Wavetronix Technical Services for assistance.
When a Click 222 is present, the power and RS-485 serial connections on the T-bus and
faceplate are protected from surges on the incoming SmartSensor 6-conductor cables.
e Click 222 faceplate has four activity indicator LEDs:
PWR – Indicates that the device has power.
Page 30
CHAPTER 2  CONNECTING POWER AND SURGE PROTECTION 29
DC Surge OK – Indicates that DC surge protection is operational. TD – Indicates when data is transmitted over the T-bus or over the control bridge. is
LED does not indicate data transmitted on the A or B ports.
RD – Indicates when data is received over the T-bus or over the control bridge. is
LED does not indicate data received on the A or B ports.
Note
If the DC Surge OK LED is not on when the Click 222 is powered, call Wavetronix Tech­nical Services for assistance.
e Click 222 provides the following three independent serial connections:
Top jack – control bridge Middle jack – dedicated communications for sensor 2 detection calls Bottom jack – dedicated communications for sensor 1 detection calls
e control bridge enables a multi-drop shared communication bus between all sensors connected to the backplate. is allows control of all Advance sensors, rack cards and other connected Click devices. e remaining two serial connection ports provide communica­tions to only one sensor each, as outlined above.
On a four-sensor preassembled backplate (see Figure 2.7):
e sensor wired into the leftmost terminal blocks will be connected to ports A and C
on the Click 222 on the left. Port A is for detection calls and port C is connected to the control bridge.
e sensor wired to the second set of terminal blocks will be wired to ports B and D
on the Click 222 on the left. Port B is for detection calls and port D is connected to the control bridge.
e sensor wired to the third set of terminal block from the left will be wired to ports
A and C on the Click 222 on the right.
e sensor wired to the rightmost terminal block will be wired to ports B and D on
the Click 222 on the right.
Page 31
30 CHAPTER 2  CONNECTING POWER AND SURGE PROTECTION
SSAdvance #2
x
x
PWR
x
x
DRN
x
x
GND
x
x
485+
x
x
485-
x
x
485+
x
x
485-
x
OUT
x
IN
x
x
PWR
x
x
DRN
x
x
GND
x
x
485+
x
x
485-
x
x
485+
x
x
485-
x
OUT
x
IN
SSAdvance #3
x
x
PWR
x
x
DRN
x
x
GND
x
x
485+
x
x
485-
x
x
485+
x
x
485-
x
OUT
x
IN
SSAdvance #4
x
x
PWR
x
x
DRN
x
x
GND
x
x
485+
x
x
485-
x
x
485+
x
x
485-
x
OUT
x
IN
SAdvance #1
S
Port A & Port C Port B & Port D Port A & Port C Port B & Port D
Figure 2.7 – Click 222 Ports A, B, C and D
Terminating the 6-conductor Cables
e SmartSensor Advance will receive power once each SmartSensor 6-conductor cable
is correctly landed into the plug-in terminals on the backplate (see Figure 2.10 and Table
2.1). Each 6-conductor cable has one DC power wire pair, two RS-485 communication pairs and a drain wire. e service end of the cable connects to plug-in terminals on the backplate (see Figure 1.8).
Figure 2.8 – Color Label on Plug-in Terminals
Page 32
CHAPTER 2  CONNECTING POWER AND SURGE PROTECTION 31
Note
Do not strip the service end of the cable until after it has been routed through con­duit. The cable should be one continuous run without any splices.
Use the steps below to land the sensor cables:
1 After routing your SmartSensor 6-conductor cable into the cabinet, carefully strip
back the cable jacket and shielding on the service end of the cable.
2 Open the insulation displacement connectors on the plug by inserting a small screw-
driver into each square slot and rocking it back.
3 Insert the wire leads into the bottom side of the plug-in terminal according to the
color code shown in Table 2.1 and Figure 2.10. Make sure the wires are completely
inserted in the terminal.
4 Close the insulation displacement connector by reinserting the screwdriver into the
square slot and rocking it forward. e plug-in terminals will automatically complete the electrical connection. ere is no need to manually strip the insulation on the end of each wire.
ere are two measures in place to ensure that the plugs are always returned to their correct terminal block sections.
First, for visual conrmation, one part of the plug is blue (see Figure 2.10) and must
be visually matched up to a blue terminal block. e location of the blue piece rotates in the dierent plugs and terminal block sections: in the rst, the rst block is blue, in the second, the second is blue, etc.
Second, the plugs are keyed (see the blue piece in Figure 2.10) so they will only t into
their correct terminal block sections.
Wire Color Signal
Red (PWR) DC+
Black (GND) DC-
White with Blue stripe (485+) Control bridge 485+ (port1)
Blue (485-) Control bridge 485 - (port 1)
White with Orange stripe (485+) Data bus 485+ (port 2)
Orange (485-) Data bus 485- (port 2)
Bare metal (DRN) Drain
Table 2.1 – Cable Wiring Color Code
Page 33
32 CHAPTER 2 CONNECTING POWER AND SURGE PROTECTION
Contact Closure Connections
e SmartSensor Advance now supports both the Click 112/114 and Click 172/174 cards. SmartSensor Advance Extended Range only supports Click 112/114. Use the data bus ports (A or B) on the Click 222 to connect to the contact closure cards. In some cases, sev­eral contact closure cards can be daisy-chained together. However, if you are using the Click 172/174 cards, the chain should not be connected until each card has been independently programmed (see Figure 2.11).
Figure 2.9 – Connecting Contact Closure Modules
Note
Wait to connect contact closure communications until after the sensor is pro­grammed using the configuration software.
See Chapter 12 for more information on contact closure communications.
Page 34
Part II
Using SmartSensor Manager Advance
Chapter 3 – Installing SmartSensor Manager Advance Chapter 4 – Communication Chapter 5 – Sensor Settings Chapter 6 – Sensor Configuration Chapter 7 – Channels-Alerts-Zones Chapter 8 – Verify Channels-Alerts-Zones Chapter 9 – Setup Output Communications Chapter 10 – Templates Chapter 11 – Tools Chapter 12 – Programming Contact Closure Cards
Page 35
Page 36
In this chapter
Installing SSMA Microsoft .NET Framework
3
After the SmartSensor Advance is installed, use SmartSensor Manager Advance (SSMA) to congure the sensor to the roadway and change sensor settings. SmartSensor Manager Advance is software that enables users to congure and interact with the SmartSensor Advance (SS200).
is part of the user guide is designed to illustrate SSMA functionality and describes the basic steps and procedures needed to correctly congure the SmartSensor Advance.
Installing SSMA
e SSMA software can be run on a Windows® PC and on a handheld computer running Windows Mobile. Everything needed to install SSMA to a PC is contained in the SSM Advance v3.0 Setup.exe le.
Note
You must have administrator rights to run the setup program.
Installing SmartSensor Manager
Advance 3
Page 37
36 CHAPTER 3  INSTALLING SMARTSENSOR MANAGER ADVANCE
Note
Microsoft .NET Framework version 3.5 or higher needs to be installed on your com­puter before installing SSMHD. You can get the .NET Framework from the Microsoft website.
Follow these steps to install SSMA on a PC:
1 To download the install le, go to the Wavetronix website at www.wavetronix.com. 2 Click the Support link near the top of the page. is will bring up a page with icons
from the three dierent Wavetronix product lines.
3 Click the SmartSensor icon. is will bring up drop-down menus allowing you to
select a product by name or part number.
4 Select SmartSensor Advance and a list of links will appear. 5 Select the SmartSensor Manager Advance link (under Software) to download the
SSMA install le.
6 Once you’ve downloaded the le, double-click on it. is will execute a setup program
that will copy all the necessary les to the hard drive and place icons in the Start menu and on the desktop of the PC or laptop (see Figure 3.1).
Figure 3.1 – SSMA Setup Wizard
7 Select an installation location. e default location provided is normally “C:\Program
Files\Wavetronix.” Click Browse to choose another location (see Figure 3.2).
Page 38
CHAPTER 3  INSTALLING SMARTSENSOR MANAGER ADVANCE 37
Figure 3.2 – Location Installation
8 Click the Install Now button. 9 After SSMA is installed, you can create shortcuts to the SSMA software on the desk-
top and in the start menu using the corresponding checkboxes (see Figure 3.3). If no shortcuts are desired, uncheck the corresponding boxes.
Figure 3.3 – Shortcut Options
10 Click in the View release notes when nished checkbox to view the SSMA v3 release
notes. e release notes contain additional information about the current version of the SSMA software. A PDF reader program (i.e. Adobe Acrobat Reader) is required to view the release notes.
11 Click Finish to complete the setup process.
Installing SSMA on a Handheld Computer
If you would like to run SSMA on a handheld computer, consider purchasing a Wavetronix
Install Kit, which includes a Socket Mobile SoMo 650 handheld computer that comes
precongured with SmartSensor Manager Advance, as well as Click Supervisor and the SmartSensor Manager software programs for the other Wavetronix sensors. ese software programs are tested for and supported on the SoMo 650.
SSMA can also be installed and will function on a handheld computer other than the SoMo 650. However, because of diering handheld computer technology, Wavetronix does not support any other handheld devices.
Page 39
38 CHAPTER 3  INSTALLING SMARTSENSOR MANAGER ADVANCE
Use these steps to install SSMA on a handheld computer running Windows Mobile:
1 Ensure the handheld computer is connected to the PC and synced. 2 Click on the SSM Advance v3 Setup.exe le to run the setup program on the host
computer. e SSMA Setup Wizard will automatically check the host computer to see if Microsoft ActiveSync (Windows XP and older) or Windows Mobile Device Center
(Windows Vista) is installed. ese are programs that are used to communicate with a
handheld device. If one of these programs is found, the option of installing SSMA to a Pocket PC device will become available.
3 Click the Pocket PC checkbox and then the Next>> button to install SSMA on a con-
nected Pocket PC device (see Figure 3.4). If both the Computer and Pocket PC boxes are checked, the setup program will rst install the SSMA software to the computer.
Figure 3.4 – Pocket PC Installation Program
4 Click Continue>> to start the Pocket PC installation process (see Figure 3.5). e
setup program runs the Add/Remove Programs application for Windows handheld devices. If a Pocket PC device is connected to the computer, Add/Remove Programs will immediately begin installing SSMA on the Pocket PC device. If a Pocket PC device is not connected to the computer, SSMA will be downloaded the next time a Pocket PC device is connected to the computer.
Figure 3.5 – Adding SSMA to a Pocket PC
5 Click OK once the download is complete.
Page 40
In this chapter
Serial Connection Internet Connection Virtual Connection Multi-drop Network Address Book Viewing Connection Information Uploading the Sensor’s Embedded Software
4
Once the sensors are installed, use the SSMA software to change settings, view data and congure the sensors to the roadway.
Launch SSMA by either clicking on the icon that was placed on your desktop or clicking the icon found in the Start menu. e SSMA main screen shown in Figure 4.1 will appear.
If you are using SSMA on a laptop computer, you can use the panel in the lower left of the main screen to change the size of the user interface on your computer. Click any of the three squares to increase or decrease the size of the user interface.
Communication 4
Page 41
40 CHAPTER 4  COMMUNICATION
Figure 4.1 – SSMA Main Screen
e rst step is to make a connection to the sensor. e following three types of connec­tions can be made:
Serial connection – Made using RS-485 communication. Internet connection – Made using an IP address and Serial-to-Ethernet adapter. Virtual connection – Made for convenience in learning and demonstrating SSMA
functionality.
Communication settings are stored in the system registry each time a connection is estab­lished. After the rst connection is made to the SmartSensor Advance, the SSMA software will save the connection settings that were used. Click the lightning bolt icon on the right side of the communication job area to make a connection using the most-recently-used parameters stored in the registry.
Serial Connection
1 Click on Communication to access the Communication window (see Figure 4.2). 2 Select the Serial tab. 3 Set Port and Speed to the desired settings. e SSMA software defaults to 9600 baud;
this baud rate is recommended and most likely will not need to be changed. Click the Advanced… button for additional serial settings.
4 Click the Connect button.
Page 42
CHAPTER 4  COMMUNICATION 41
Figure 4.2 – Serial Connection (left) and Advanced Settings (right)
e Advanced Settings screen contains the following elds:
Timeout (ms) – Allows you to set an additional amount of time (in milliseconds) that
SSMA will wait for a response when communicating with the sensor.
Buer (bytes) – Contains the number of bytes used by SSMA to store data received
from the sensor.
Parity – is should always be set to None. Stop Bits – is should always be set to 1. Data Bits – is should always be set to 8.
Note
When a connection is made using the Isolated Sensor tab instead of the Multi-drop Network tab, the software will connect to the first sensor it finds. If you have multi-
ple sensors and want to be able to connect to each one, use the Multi-drop Network tab (see Multi-drop Network section below).
Internet Connection
1 Click on Communication. 2 Select the Internet tab (see Figure 4.3). 3 Enter the IP address of the Serial-to-Ethernet adapter to which the sensor of interest
is connected, or the domain name associated with the sensor in the Address eld. e IP address is four octets, each ranging from 0-255, separated by dots (“.”). An URL address can also be entered into this eld (i.e. sensor.earlink.com).
4 Enter the port number assigned to the Ethernet-to-Serial adapter in the Port eld.
is will be an integer value in the range of 0-65536. If you are using a Click 301 device, the default port number will be 10001. Click the Advanced… button for ad-
Page 43
42 CHAPTER 4  COMMUNICATION
ditional Internet settings.
5 Click the Connect button.
Figure 4.3 – Internet Connection (left) and Advanced Settings (right)
e Advanced Settings screen contains the following elds:
Timeout (ms) – Allows you to set an additional amount of time (in milliseconds) that
SSMA will wait for a response when communicating with the sensor.
Buer (bytes) – Contains the number of bytes used by SSMA to store data received
from the sensor.
Virtual Connection
A virtual connection allows you to use the SSMA software without being connected to an actual sensor. Making a virtual connection can be useful for the following reasons:
To view a saved sensor setup le. To play back previously logged trac. To demonstrate functionality for dierent applications. To create channel templates. To review how the software works.
To make a virtual connection:
1 Click the Communication button. 2 Select the Virtual tab (see Figure 4.4). 3 Select a virtual sensor le by clicking the magnifying glass icon. Click the Options…
button to select a tracker log le.
4 Click the Connect button.
Page 44
CHAPTER 4  COMMUNICATION 43
Figure 4.4 – Virtual Connection and Additional Options Screen
Virtual Sensor File
Since a virtual connection is not made to an actual sensor, a virtual sensor le (.vsf ) is used to save the conguration settings much like an actual sensor’s Flash memory. If you are making a virtual connection for the rst time, you will need to create a virtual sensor le by clicking on the magnifying glass icon and entering a le name.
When you create a new virtual sensor, you will need to complete two steps. First, you need to open the new le (see Figure 4.5).
Figure 4.5 – Open New File
Second, you will need to decide whether the new sensor is to be a virtual SmartSensor Advance Extended Range device of a virtual SmartSensor Advance device (see Figure 4.6). If you would like the virtual sensor to emulate SmartSensor Advance Extended Range, an­swer Yes to the second prompt. If you would like the virtual sensor to emulate SmartSensor Advance answer No to the second prompt.
Figure 4.6 – Type of Virtual Sensor
Page 45
44 CHAPTER 4  COMMUNICATION
Note
When you are connected using a virtual sensor file, changes that would normally be saved to a sensor’s Flash memory will automatically be saved to the virtual sensor file.
Backing up a virtual sensor le will change the le to a sensor setup le (.ssc) that can be
restored to an actual sensor. To convert a sensor setup le to a virtual sensor le, make a vir­tual connection and then use the Restore Sensor Setup tool in the Tools menu. To convert
a virtual sensor le to a sensor setup le, use the Back-up Sensor Setup tool.
Note
If you want to configure channels, alerts and zones for a future installation, you can connect using a virtual connection, create a virtual sensor file and then back up the configuration settings that you created. After the file is successfully backed up, the virtual sensor file will change to a sensor setup file and can be restored to any sensor in the field.
Selecting a Tracker Log File
A tracker log le is used to play back recorded trac. To select a tracker log le, click the
Options… button, click on the magnifying glass icon and select the tracker log le from a list of existing les. If a tracker log le doesn’t exist, the SSMA software will create a ge-
neric looping trac pattern (see the Setup Channels-Alerts-Zones screen for instructions
on how to create a tracker log le).
Note
If a successful connection uses the sensor’s Com port that was being used to push data, the data push will be suspended during the duration of the connection.
When a connection is made to the SmartSensor Advance, the main menu will appear and all conguration options will become available (see Figure 4.7).
Page 46
CHAPTER 4  COMMUNICATION 45
Figure 4.7 – SSMA Main Menu (Connected)
If you have problems connecting:
1 Make sure that all power and communication wiring is correct. 2 Check the port settings (baud rate, port ID).
Connection failure can occur for various reasons; if a failure occurs repeatedly, call Wa-
vetronix Technical Support at 801-764-0277 for assistance.
Multi-drop Network
e SSMA software automatically discovers the multi-drop ID of sensors over the selected port (normally you will auto-discover addresses over port 1).
Figure 4.8 – Multi-drop Network
Click the Automatically detect sensors radio button and then click the Connect button. e Auto-Discovery window will appear with a list of each detected sensor and its device ID, location and description (see Figure 4.9).
Page 47
46 CHAPTER 4  COMMUNICATION
Figure 4.9 – Auto-Discovery Window
e device IDs are based on the last four digits of the sensor’s serial number. If the sensor IDs conict, they can be changed in the auto-discovery window by clicking on the desired row. e Change sensor ID window will appear allowing you to change the sensor ID.
Address Book
e address book allows you to save device connection settings for future use. Click the Address Book button located at the bottom of the Communication page to add new con­nection settings to the address book (see Figure 4.10).
Edits the
selected
device
Adds a device to the
Address Book
Deletes a device
from an Address
Book
Filters Address Books
by serial or Internet
connection
Deletes an
Address
Book
Imports an
Address
Book
Exports an
Address
Book
Figure 4.10 – Address Book and Address Book Filter
Viewing Connection Information
Once connected, you can view additional information about the connection you have es­tablished by clicking on the moving arrows icon on the top-right of the main menu page or on the bottom-right of the Communication screen (see Figure 4.11).
Page 48
CHAPTER 4  COMMUNICATION 47
Figure 4.11 – Connection Info Screen
Below is a list of the information available on the Connection Info screen:
Status – Shows that you are connected. Device – Shows the Subnet and sensor ID. Type – Shows the type of connection and baud rate. Duration – Shows how long you have been connected. Failures – Shows the amount of failures during the connection, the percentage rate of
failure and a link to the Communication Error Log.
Check Hardware
After you have connected to a sensor, you can check its hardware type by right-clicking
below the Tools menu option and selecting Sensor Versions.
Figure 4.12 – Check Sensor Version
e two current hardware types are SmartSensor Advance and SmartSensor Advance Ex­tended Range.
Page 49
48 CHAPTER 4  COMMUNICATION
Figure 4.13 – Sensor Versions Window for Advance (left) and Advance Extended Range (right)
Once connected, the hardware type can also be determined from the title bar. If the sensor is and Extended Range sensor, it will say "(Ext. Range)" in the title bar of SSMA.
Communication Error Log
e error log contains all errors stored in the sensor’s memory buer. If you are having trouble connecting, using the error log may be helpful in the troubleshooting process. If you
continue having trouble, save the error log le and contact Wavetronix Technical Services.
Note
You will need to save the error log file or it will be overwritten.
Click the View Error Log link to view the communications error log (see Figure 4.14). e error log can also be accessed by clicking on the Error Log icon at the bottom of the Communication screen.
Figure 4.14 – Error Log
Page 50
CHAPTER 4  COMMUNICATION 49
Uploading the Sensor’s Embedded Software
After clicking the Connect button, the Version Control screen may appear notifying you that the sensor’s embedded software and the rmware embedded in the SSMA software
are not the same version (see Figure 4.15). To view more software version information,
right-click on the SSMA main menu page and select from the options that appear.
Figure 4.15 – Sensor’s Embedded Software Upgrade (left) and Details Table (right)
Click the Details button to view the rmware versions of both the SSMA software and the sensor.
Once the Version Control screen appears, you can do one of the following:
1 Upgrade the sensor’s embedded software by clicking the INSTALL UPGRADE but-
ton.
2 Click the close button and continue the conguration process. 3 Find the version of SSMA software that is compatible with the sensor’s embedded
software.
Note
Clicking the close button and continuing configuration without upgrading may cause problems with functionality.
Install the rmware upgrade if the SSMA rmware version date is more recent than the sensor’s embedded software version date. If the sensor’s rmware date is more recent than the SSMA rmware version date, a warning will appear notifying the user that the sensor rmware could be downgraded (see Figure 4.16).
Page 51
50 CHAPTER 4  COMMUNICATION
Figure 4.16 – Sensor Firmware Downgrade
e most recent version of SSMA can be obtained from the Wavetronix website (www. wavetronix.com) under the Support tab.
Converting Detection Zones from Previous Software Versions
Previous versions of the SSMA software supported 8 zones. SSMA version 2.0 and later supports 128 zones (8 channels, 4 alerts per channel and 4 zones per alert).
During the rmware upgrade process, SSMA will determine if the sensor is running any previous versions. If this is the case, the SSMA software will display a message asking you to convert the conguration. If you choose to convert the conguration, the SSMA software will create a new conguration out of the previous existing conguration; if you
choose NOT to convert, a default conguration will be created.
Page 52
In this chapter
General Tab Communication Tab
5
Click the Sensor Settings link on the main menu to change and save settings on the sensor.
e Sensor Settings window contains General and Communication tabs (see Figure 5.1).
Figure 5.1 – Sensor Settings Screen
General Tab
e General tab contains the following elds (see Figure 5.2):
Sensor Settings 5
Page 53
52 CHAPTER 5  SENSOR SETTINGS
Figure 5.2 – General Tab
Serial Number – Contains the sensor serial number and can only be edited if you are
in the Advanced Sensor Setup mode (conatct Wavetronix Technical Services for more
information).
Sensor ID – Allows you to enter a multi-drop address for the sensor. e ID default
is the last four digits of the sensor serial number. e sensor ID can be changed, but no two sensors should have the same ID; the ID must be unique for all sensors on a multi-drop bus.
Description – Allows you to enter a description for each sensor (i.e. its function, ap-
plication or intended use). Limited to 32 characters.
Location – Allows you to enter the location of the sensor or the approach. Limited to
32 characters.
RF Channel – Displays which radio frequency channel (or non-interference channel)
the device is transmitting on. Using multiple SmartSensor Advance devices in close proximity will require each one to be set to a dierent RF channel. Similarly, using multiple SmartSensor Advance Extended Range devices in close proximity will re­quire each one to be set to a dierent RF channel. However, a SmartSensor Advance device will not interfere with a SmartSensor Advance Extended Range device, even if they are on the same RF channel. is is because the hardware used to transmit the Digital Wave Radar signal is congured dierently on the dierent devices.
Units – Allows you to display either English (mph/feet) or metric (kph/meters) units. Source – In normal use, the source is always the radar Antenna. However, in some
cases, other sources may be used for demonstrations or evaluations. When the source is switched to Diagnostic, the antenna is no longer used. Instead, a predetermined sequence of trac will appear. is setting will always return to Antenna after reboot­ing the sensor.
Communication Tab
e Communication tab is used to specify baud rate and response delay for the sensor’s RS-485 ports (see Figure 5.3).
Page 54
CHAPTER 5  SENSOR SETTINGS 53
Figure 5.3 – Communication Tab
e Communication tab contains the following settings:
Baud Rate – is section allows you to set the baud rate for ports 1 and 2. e green
arrow indicates the communication link (Port) on which SSMA is connected. e default value is 9600 bps.
Note
If you are using a Click communication device, the baud rate for the sensor and the Click device must be the same. Port 2 is designated as the data bus and is normally left at 9600 bps in order to match the default setting on a Click 112/114 card. If you change this baud rate on the sensor, you will also need to change it on the rack card.
Response Delay – is is used to congure how long the sensor will wait before re-
sponding to a message received. is is useful for some communications devices that are unable to quickly change transmission direction. e default value is 4 milliseconds for ports 1 and 2.
Remove Multi-drop Prefix – You will only need to turn this switch ON if you are
using a device that does NOT support the use of a multi-drop prex (i.e. Click 100).
Page 55
Page 56
In this chapter
1. Installation Details 2. Automatic Radar Configuration 3. Manual Radar Adjustment
6
e Sensor Conguration screen contains installation details, an automatic conguration feature and manual conguration tools (see Figure 6.1).
Figure 6.1 – Sensor Configuration Screen
Click the lighting bolt icon on the bottom right corner of the screen to save the cur­rent conguration to the sensor’s ash memory. e sensor’s ash memory is non-volatile memory.
Sensor Configuration 6
Page 57
56 CHAPTER 6 SENSOR CONFIGURATION
1. Installation Details
e Installation Details screen allows you to position the sensor relative to the stop bar and determine the direction of trac to be monitored (see Figure 6.2).
Direction of trac
Stop bar
SmartSensor
Advance
Changes
direction of
trac
Changes
location of
stop bar
Changes
position of
sensor
Height of
sensor
Figure 6.2 – Installation Details Screen
e roadway part of the screen is used to illustrate the sensor’s position relative to the stop bar; the controls on the right side of the screen allow you to specify the direction of trac to be monitored and the sensor’s position. e distance units are displayed in the bottom­right corner of the screen.
e OK button saves the settings to the sensor; the Undo button restores the settings to the screen’s initial values; and the Cancel button closes the screen without saving changes to the sensor.
Changing the Trac Direction
e SmartSensor Advance can be congured to detect trac moving towards or away from the sensor, but will not detect stationary vehicles.
e arrow displayed on the roadway represents the direction of trac ow being detected by the sensor. Click the Trac button to change the monitored trac direction. e direc- tion of the arrow displayed on the button shows the direction that will be selected if the button is clicked, and always points in the opposite direction as the arrow on the roadway.
Positioning the Stop Bar
e ability to move the stop bar up and down the display adds exibility in representing the relative location of the sensor to the stop bar and the direction of trac ow. e loca­tion of the stop bar is always represented as a distance of zero (the sensor range is relative to the stop bar).
Position the stop bar by clicking on the stop bar or its label and dragging it anywhere on
Page 58
CHAPTER 6  SENSOR CONFIGURATION 57
the roadway, or by clicking the Stop Bar up/down arrows.
Positioning the Sensor
Position the sensor by clicking on the sensor or its label and dragging it anywhere on the roadway, or by clicking the Sensor arrow buttons.
e top number, shown in the sensor position display (next to the blue triangle), represents the sensor’s position to the right or left of the center of the lanes being monitored (Carte­sian x coordinate); the bottom number represents the sensor’s position in front of or behind the stop bar (Cartesian y coordinate), together forming a Cartesian coordinate pair (x, y). e sensor’s height is specied by setting the Height value and reects the sensor’s mount­ing height above the roadway (Cartesian z coordinate).
e resulting (x, y, z) coordinates describe the sensor’s position relative to the roadway and are used to translate the sensor’s native range measurements to range measurements that are relative to the roadway’s frame of reference. e sensor position is also used in the Beam
Alignment tool (see Tools).
Note
The sensor’s range is updated whenever the stop bar is moved.
Resetting Zones After Sensor Relocation
When the sensor location is changed, existing zones may no longer be within the sensor’s detection range and the message below will appear (see Figure 6.3):
Figure 6.3 – Sensor Location Changed
It is always recommended to rst position the sensor and then congure detection zones. However, if the sensor location is modied after zone conguration, you can do one of the following:
1 Manually check all detection zones and modify zones as needed (recommended). All
zones will still be available and their location relative to the sensor will be preserved. If left uncorrected, the zones may no longer perform the desired detection function.
2 Reload only the channel conguration from a backup le created from the existing
conguration (the out-of-range zones will be deleted and the desired detection func­tions may be compromised).
Page 59
58 CHAPTER 6 SENSOR CONFIGURATION
3 Reload the individual channel template les used in the current conguration (the
out-of-range zones will be deleted and the desired detection functions may be com­promised).
2. Automatic Radar Configuration
Click the Automatic Radar Conguration button and the Automatic Radar Congura­tion screen will appear (see Figure 6.4).
Figure 6.4 – Automatic Radar Configuration Screen for Advance (left)
and Advance Extended Range (right)
Note
The ranges displayed in the Automatic Radar Configuration window will depend upon whether you have SmartSensor Advance or SmartSensor Advance Extended Range. The scale on the right side of the road view indicates the ranges.
Click the Play button to begin the auto-conguration process. e playing time will be shown in the top-left corner of the screen. After approximately three minutes, trackers (sensor detec­tions) will begin to appear on the roadway and the process will change to Step 2 Adjusting resholds. e Pause button pauses the auto-conguration process; the Stop button will terminate auto-conguration. e Close button closes the screen and returns to the Sensor Conguration job menu. If the conguration process is running, it will continue to run after closing. To terminate the automatic radar conguration process, press the Stop button.
e semi-transparent message window can be toggled on/o by clicking the Show>> and <<Hide labels. e roadway range scale can be toggled on/o by clicking the feet label.
e following is a list of tracker display data that can be viewed by clicking the Range (ft) display bar at the base of the roadway:
Page 60
CHAPTER 6  SENSOR CONFIGURATION 59
Range – Shows the distance from the stop bar. Speed – Shows the speed. Estimated Time of Arrival – Shows the estimated time it will take to arrive at the stop
bar.
Tracker ID – Shows the ID number for each tracker. Blank – (no tracker data shown) Disabled – (no tracker shown)
3. Manual Radar Adjustment
e Manual Radar Adjustment screen is used to ne-tune the results of the automatic radar conguration process (see Figure 6.5).
Figure 6.5 – Manual Radar Adjustment Screen for Advance (left)
and Advance Extended Range (right)
Note
The ranges displayed in the Manual Radar Adjustment window will depend upon whether you have SmartSensor Advance or SmartSensor Advance Extended Range. The scale on the right side of the road view indicates the ranges. The SmartSensor Advance has 5-ft increments up to 600 ft, and the SmartSensor Advance Extended Range has 7.5-ft increments up to 900 ft.
You will notice in the button tray at the bottom of the window (see Figure 6.5) there is a Reboot button (green power button icon). When you press this button it will tell you that the reboot may take up to 20 seconds (see Figure 6.6).
Page 61
60 CHAPTER 6  SENSOR CONFIGURATION
Figure 6.6 – Reboot
If you were in the process of manually editing detection thresholds, it will ask you if you would like to save these changes to the sensor’s ash before rebooting (see Figure 6.7). If you do not save these changes they will be discarded.
Figure 6.7 – Save Changes
During the reboot time, the power button will turn red (see Figure 6.8), but once the sensor has rebooted it will go back to green again.
Figure 6.8 – Red Button During Reboot
Editing Sensitivity
If missed detections are consistently noticed, the sensor’s sensitivity can be adjusted. De­creasing the detection threshold levels in areas where trackers begin to disappear will reduce
the number of missed detections. To increase the sensor’s sensitivity, decrease the detection
threshold levels; to decrease the sensor’s sensitivity, increase the detection threshold levels.
Page 62
CHAPTER 6  SENSOR CONFIGURATION 61
Note
Do not reduce the thresholds so low that “phantom detections,” or false detections in the absence of trac, begin to appear.
If phantom detections are consistently visible, increase the sensor’s detection thresholds in these areas. Phantom detections can occur if large objects in the sensor’s eld of view move faster than 1 mph (2 kph). If the thresholds are too low, the sensor can pick up trees swaying in strong winds or fast-moving pedestrians.
Double detections from vehicles such as double-bed trailers are not considered false detec­tions. It is often benecial for the sensor to signal an actuated trac controller based on both detections. In cases of double detections, the thresholds will not need to be increased.
Follow the steps below to adjust the sensitivity:
1 Determine the ranges for which detections need to be adjusted. 2 Click and drag to select the section of the histogram (range bins) that needs to be
adjusted (see Figure 6.9).
Figure 6.9 – Editing Ranges for Advance (left)
and Advance Extended Range (right)
Note
The ranges displayed in the manual radar configuration view will depend upon whether you have SmartSensor Advance or SmartSensor Advance Extended Range. The scale between the road view and the threshold histogram bars indicates the ranges. With SmartSensor Advance each threshold is every 5 feet. With SmartSen­sor Advance Extended Range each threshold is every 7.5 feet.
Page 63
62 CHAPTER 6 SENSOR CONFIGURATION
3 Click the Edit button and the Edit Sensitivity resholds screen will appear (see Fig-
ure 6.10). e following three editing modes are available for modifying sensitivity values:
e +/- mode adds or subtracts the specied number to the existing sensitivity levels. e % mode sets the sensitivity level to be the specied percent of the existing value. e Value mode sets the sensitivity level to be the specied value.
Figure 6.10 – Edit Sensitivity Thresholds Screen for Advance (left)
and Advance Extended Range (right)
4 Click and drag again to select the exact range bins to adjust. 5 Make the sensitivity level adjustments. 6 After adjusting the sensitivity, click the Enter button to apply the adjustment. 7 Click the OK button to accept the modications and close the Edit Sensitivity win-
dow; click the Undo button to return all modied sensitivity levels to their initial values; or click the Cancel button to undo all changes made.
8 Re-evaluate the detections.
If any changes were made during the Sensor Conguration process, a pop-up window will appear prompting the user to save the changes to the sensor’s FLASH memory. Changes that were not written to FLASH will be lost the next time the sensor reboots. e process of saving to FLASH memory takes approximately ve seconds.
Selecting a Tracker Display Mode
e following is a list of tracker display data that can be changed by clicking the display bar at the base of the roadway:
Range Speed E TA ID Blank Disabled
Page 64
CHAPTER 6  SENSOR CONFIGURATION 63
Changing the PGA
e Programmable Gain Amplier (PGA) allows you to change the radar sensitivity for
the entire approach (see Figure 6.11).
Note
Consult with Wavetronix Technical Services before changing the PGA setting.
Figure 6.11 – Editing the PGA
Page 65
Page 66
In this chapter
Channels Alerts Zones
7
e Channels-Alerts-Zones (CAZ) screen allows you to set up and verify channels, alerts
and zones; set up output communications; and import/create a template (see Figure 7.1).
Figure 7.1 – Channels-Alerts-Zones Screen
is chapter will explain the dierent types of channels and how they are mapped to alerts and zones.
e CAZ Setup screen provides conguration access to all CAZ elements.
Channels-Alerts-Zones 7
Page 67
66 CHAPTER 7 CHANNELS-ALERTS-ZONES
Channels
e channel is the highest-level detection unit. e user-dened channel name, used to distinguish one channel from another, can consist of eight ASCII characters. e channel number (1–8) is used to associate sensor channels with Click contact closure channels.
e Type drop-down list allows you change the channel type from the default type. For SmartSensor Advance Extended Range, the default channel type is Priority for channels 1–3 and Simple for channels 4–8. For SmartSensor Advance, the default type is Simple for all channels. SmartSensor Advance does not have Priority channels, but both sensors have two additional types of channels: Normal and Latched (see Figure 7.2).
Figure 7.2 – Channel Configuration
e channel conguration is read from the sensor the rst time that the CAZ job is se­lected. Due to the amount of information represented in the conguration, the retrieval may take ve seconds or more, depending on the speed and quality of the connection.
Note
The channel output from a sensor is usually tied to a channel input in a controller.
Click the Enabled checkbox and all channel features will become available. When a chan­nel is enabled, the channel portion of the setup screen and its associated tab is colored gold; when a channel is disabled, the channel section is gray.
Simple Channel
A simple channel consists of one dedicated zone, which is a lower-level detection unit. e simple channel provides an easy and quick way to set up the zone (see Figure 7.3).
Page 68
CHAPTER 7  CHANNELS-ALERTS-ZONES 67
Zone 1
Channel 1
Figure 7.3 – Simple Channel Hierarchy
To create a simple channel, select Simple from the Type drop-down menu and the follow- ing screen will appear (see Figure 7.4):
Figure 7.4 – Simple Channel for Advance (left) and Advance Extended Range (right)
A simple channel allows you to congure the most basic zone settings. You can change the size of the zone by either clicking and dragging the zone arrows anywhere along the road­way or by using the up/down arrows in the Range (feet): eld.
You can set the Speed and E TA settings by rst clicking the Speed/ETA checkbox and then setting the parameters using the up/down arrows. Click OK to save the changes you make to each channel.
Note
Make sure that the Speed/ETA checkboxes are checked before you click OK. If the checkboxes are not checked, those settings will NOT be enabled.
e SmartSensor Advance is most commonly used with advance detection at signalized
Page 69
68 CHAPTER 7  CHANNELS-ALERTS-ZONES
intersections. A very powerful method of advance detection uses two simple channels: Ad­vance and QReduce.
e Advance channel provides green extension at high-speeds for safety and eciency. e QReduce channel provides green extension at low-speeds when the initial queue is dissipating.
Follow the steps below to congure the Advance channel:
1 Click on Channels-Alerts-Zones on the main menu. 2 Click the Setup Channels-Alerts-Zones button. 3 Enable a channel by checking the Enabled checkbox. 4 Select Simple from the Typ e drop down list. 5 Adjust the size of the zone by either using the Range (feet): up/down arrows or by
manually grabbing the zone’s blue arrows and dragging them anywhere on the road­way.
6 Click the Speed and E TA checkboxes to activate the Speed and ETA parameters. 7 Set the speeds from 35 mph on low end to 100 mph on high end. 8 Name the channel “Advance” and click OK to save the channel settings.
Follow the steps below to congure the QReduce channel:
1 Click the second tab on the top of the Setup Channels-Alerts-Zones screen. 2 Enable the channel by clicking the Enabled checkbox. 3 Select Simple from the Type drop-down list. 4 Adjust the size of the zone to 100 to 150 feet from the stop bar. 5 Click the Speed checkbox to activate this lter and select speeds from 1 to 35 mph. 6 Name the channel “QReduce” and click OK to save the channel settings.
e OK, Undo and Cancel buttons pertain to ALL changes made in the CAZ Setup job and not to individual channels, alerts or zones. e OK button saves the settings to the sensor; the Undo button restores the settings to the screen’s initial values; and the Cancel button closes the screen without saving any changes.
Priority Channel
A priority channel consists of three zones, each with a complementary role (see Figure
7.5). When any one of the three zones is active, the channel output is active (equivalent to a Boolean OR of the three zone outputs).
Page 70
CHAPTER 7  CHANNELS-ALERTS-ZONES 69
Channel 1
Level 1
Level 2
Queue
Clearance
Figure 7.5 – Priority Channel Zones
e rst two zones work in tandem to allow you to provide dierent levels of dilemma zone
protection based upon the discovery range of each vehicle. Vehicles discovered upstream of
the discovery range threshold are classied as level one priority and are given the highest
level of protection. Vehicles discovered downstream of the discovery range threshold are
classied as level two priority and are given a reduced but adequate level of protection.
Note
Priority channels are only available with SmartSensor Advance Extended Range. The extended range of the sensor is best matched to:
• Distinguish between large vehicles (trucks and buses) and small vehicles (pas­senger cars).
• Provide dilemma zone protection for large vehicles. Trucks have been shown to have dilemma zones a far back as 7.5 seconds. For example, an ETA of 7.5 sec­onds at 65 mph is equivalent to 715 ft. (217.9 m). This is beyond the range of SmartSensor Advance, but not SmartSensor Advance Extended Range.
By default the discovery range threshold is set at 750 feet. If necessary, adjust the discovery range threshold so that most large vehicles are discovered beyond this threshold and most small vehicles are discovered after it.
Page 71
70 CHAPTER 7  CHANNELS-ALERTS-ZONES
Figure 7.6 – Setup Channels-Alerts-Zones Screen for Priority Channel
e level-one zone will activate the channel output when a level-one priority vehicle meets the specied criteria. By default the ETAs protected are between 2.5 and 7.5 seconds be­cause trucks and other large vehicles have been found to have a larger dilemma zone.
e level-two zone will activate the channel output when a level-two priority meets the
specied criteria. By default the ETAs protected are between 2.5 and 5.5 seconds because
passenger cars and other light-duty vehicles have been found to have a smaller dilemma zone.
e third zone is a queue-clearance zone. is zone activates the channel output when the initial queue of trac is dissipating at low speeds. It is recommended that all three zones be used in combination with 1.0 seconds of passage time in the controller.
For the queue clearance zone, a 1.0 passage time is added to the maximum time headway between two vehicles occupying the zone at the same time to determine the maximum al­lowable time headway. When the zone is 50-feet wide and the vehicles are 20-feet long, the maximum time headway between two vehicles occupying the zone at the same time at 30 mph is approximately 1.6 seconds. After adding 1.0 seconds of passage time, maximum al­lowable headway for 30 mph vehicles becomes 2.6 seconds. Slower vehicles will experience a large maximum allowable headway, which is useful during the startup period of queue dissipation in order to avoid gap out.
If you need to increase the maximum allowable headway you can increase the size of the queue clearance zone, or the passage time. Normally it is recommended to keep the passage time small and increase the size of the queue clearance zone. is is because the size of the queue clearance zone will not matter when the ow speeds are above 35 mph, and because you want to keep the passage time trim when trying to nd a safe gap in high-speed trac.
Page 72
CHAPTER 7  CHANNELS-ALERTS-ZONES 71
Figure 7.7 – Providing Dilemma Zone Protection
By providing zones for level-one priority dilemma zone protection, level-two dilemma zone protection and queue clearance, a priority channel provides exceptional detection from start-of-green to end-of-green.
Note
There may be a number of uses of the discovery range feature for other applications than truck priority. For example, you could require that a vehicle be discovered at a certain range (using the discovery range threshold) and that it travels to a down­stream zone several hundred feet away before it activates a channel output. This is a way to know that we have tracked a specific vehicle over an extended range. This is better than simple using the channel delay because it isolates a single vehicle.
Normal Channel
Normal channels consist of (see Figure 7.8):
8 channels 4 alerts per channel (32 total) 4 zones per alert (128 total)
Page 73
72 CHAPTER 7  CHANNELS-ALERTS-ZONES
Channel 1
Alert 1
Zone
1
Alert 2
Alert 3
Alert 4
Zone
2
Zone
3
Zone
4
Zone
4
Zone
3
Zone
2
Zone
1
Zone
1
Zone
2
Zone 3Zone
4
Zone
1
Zone
2
Zone
3
Zone
4
Figure 7.8 – Normal Channel Hierarchy
e CAZ Setup screen below shows a tabbed view of each detection channel and its as­sociated alerts and zones (see Figure 7.9). e eight tabs at the top of the screen represent the sensor’s eight channels, with the selected tab showing the channel number and channel name; the middle portion of the screen contains alert conguration parameters; and the lower portion of the screen contains zone conguration parameters.
Channels
Alerts
Zones
Figure 7.9 – Setup Channels-Alerts-Zones Screen
e OK, Undo and Cancel buttons pertain to ALL changes made in the CAZ Setup job and not to individual channels, alerts or zones. e OK button saves the settings to the sensor; the Undo button restores the settings to the screen’s initial values; and the Cancel button closes the screen without saving any changes.
Page 74
CHAPTER 7  CHANNELS-ALERTS-ZONES 73
Normal channels consist of four alerts, each containing four zones. A normal channel’s output is a logical combination of the channel’s alert, zone, delay and extend settings (see Delay and Extend sections under Latched Channels). e normal channel’s output be­comes active when the associated alert and zone logic, the channel delay or the channel extend are satised.
Each enabled normal channel must have at least one enabled alert. If you attempt to save an invalid channel conguration, the following message is displayed (see Figure 7.10).
Figure 7.10 – Invalid Channel Configuration
Latched Channel
Latched channels consist of two alerts (ON and OFF), each containing up to four zones (see Figure 7.11). A latched channel, by denition, has exactly two enabled alerts that can­not be disabled.
Channel 1
ON
Alert
OFF
Alert
Zone 1Zone
2
Zone
3
Zone
4
Zone 1Zone
2
Zone
3
Zone
4
Figure 7.11 – Latched Channel Heirarchy
Latched channels dier from normal channels in that the channel output remains in a given state until a contradictory alert is exclusively activated, or a maximum latch time has expired (see Figure 7.12).
Page 75
74 CHAPTER 7  CHANNELS-ALERTS-ZONES
Latched
Channel
output
ON
Alert
OFF
Alert
Figure 7.12 – Latched Channels
For example, a channel’s output will become activated when an ON alert is triggered and will latch (stay active) even when the ON alert is no longer triggered. Subsequently, if an OFF alert is triggered, the channel output will be deactivated as soon as all other timing conditions are satised (e.g. the minimum ON time, channel extend).
Note
When changing a normal channel to a latched channel, alerts 1 and 2 will be used as the ON and OFF alerts, respectively (alerts 3 and 4 will be disabled).
Delay
e channel delay is used to ignore alert outputs that are shorter than the specied delay time (see Figure 7.13). Latched channels do not activate outputs until the delay require­ments have been met (only a channel’s alert and zone logic are applied during the delay period).
Delay
Channel
output
Alert
Figure 7.13 – Channel Delay
Extend
e extend feature is used to continue a channel output after the required conditions have been met (see Figure 7.14). For example, if a vehicle enters a zone and activates the channel output, that channel would remain ON for a specied extend time after the vehicle leaves the zone.
Page 76
CHAPTER 7  CHANNELS-ALERTS-ZONES 75
Channel
output
Alert
Extend
Figure 7.14 – Channel Extend
Max (s)
e channel Maximum Latch Timer is used to turn a latched channel o after it has ex­isted continuously in a latched state for a specied period of time. e latch timer, labeled Max (s), is available only when using latched channels and can be enabled/disabled by checking/unchecking the checkbox next to the Max (s) label.
If enabled, the latch timer species how long a latched channel may operate continuously in the latched state. In a case where the OFF condition was not detected, the latch timer can be used to prevent a latched channel from remaining indenitely (and unintentionally) in the ON state.
e latch timer can also be used to generate a latched output of specied duration. is timed output can be achieved by dening the OFF alert to have a conguration that is not likely (essentially impossible) to be activated.
Note
A latched channel may have its output activated indefinitely (even if the latch timer is enabled), if the ON alert is never turned o or if it is repeatedly turned o and on before the latch timer expires.
A latched channel with an impossible OFF alert could be used to drive an over-speed bea­con or any other type of ancillary signal that is based on the activating of the ON alert and whose indication has a xed duration.
Note
The extend period occurs after the latched condition is terminated. This means that the output will remain activated, after the latch timer expires, for an additional pe­riod of time (as specified by the extend setting).
Page 77
76 CHAPTER 7 CHANNELS-ALERTS-ZONES
Alerts
e alert is the mid-level detection unit and is used to dene the corresponding channel’s output (see Figure 7.15).
Figure 7.15 – Alert Configuration
Enabling an Alert
When an alert is enabled, the alert section of the setup screen turns white; when an alert is disabled, the alert section turns dark gray. A normal channel contains alerts 1 through 4 and a latched channel contains an ON alert and OFF alert that cannot be disabled.
Each enabled alert must have at least one enabled zone. If you attempt to save an invalid alert conguration, a prompt will appear asking you to activate one zone for each enabled alert.
Logic (OR/AND)
An alert’s logic setting species the Boolean logic operation to be applied to the alert’s zone outputs. e available options are OR and AND. If OR logic is selected, the alert will turn ON if one or more zones have active outputs; if AND logic is selected, the alert will turn ON only if ALL enabled zones have active outputs.
Inverted Zones
In order to provide more exibility, an alert can invert a given zone’s output BEFORE ap­plying the alert’s specied logic operator on the zone outputs.
For example, if an alert has only one enabled zone (zone1), and that zone’s output is OFF (did not nd a qualied detection in the zone), then the alert’s output will be OFF. How­ever, if the alert were congured to invert the zone’s output, then when the zone’s output is OFF, the alert’s output will be ON.
Zones
e zone is the lowest-level detection unit. A zone’s output is used to dene the corre­sponding alert’s output.
Page 78
CHAPTER 7  CHANNELS-ALERTS-ZONES 77
Click here
to open the
range editor
Figure 7.16 – Zone Configuration
Below is a description of each parameter in the zone section of the CAZ Setup screen (see
Figure 7.16).
Range (ft)
A zone is enabled when its range is dened. When a zone is enabled, the zone section of the setup screen turns yellow; when a zone is disabled, the zone section turns light gray. A detection must be within a zone’s range limits in order to activate that zone’s output. All zone ranges in a given alert are congured in a single screen and may not overlap in range. Click in the zone range display next to the range label to open the zone range editor (see Figure 7.17).
Figure 7.17 – Zone Range Editor
To add (enable) a zone, drag the desired zone icon from the zone well to the roadway; to re­move (disable) a zone, drag it from the roadway to the zone well (or anywhere o the road­way). If a zone is moved to an invalid location, it will be returned to its previous location.
To change the range of a zone, drag the blue triangle markers up or down the roadway or
click the up/down arrows on either side of the screen (see Figure 7.18). e zone can be placed anywhere on the roadway by clicking anywhere inside the zone and dragging it. e minimum range is 50 ft. (15.2 m) from the sensor and the maximum range is 600 ft. (152.4 m) from the sensor.
Page 79
78 CHAPTER 7  CHANNELS-ALERTS-ZONES
Figure 7.18 – Adjusting Zones for Advance (left) and Advance Extended Range (right)
Speed (mph) and ETA (s)
In addition to range, zone detections can also be ltered by speed and by the estimated
time of arrival to the stop bar. Click anywhere in the Speed or ETA area and the Edit Basic
Filters screen will appear (see Figure 7.19).
Figure 7.19 – Edit Basic Filters Screen
Edit the min and max values in the speed lter to set the range of qualied speeds. e minimum speed value is 1 mph (2 kph) and the maximum speed value is 100 mph (161 kph).
On the previous window, check the box to the left of the Speed label to enable the speed lter (only speeds within the range will activate zone outputs); uncheck the box to disable the speed lter (all speeds will activate zone outputs).
Edit the min and max values in the ETA lter to set the range of qualied ETAs. e minimum ETA value is 0.1 seconds and the maximum ETA value is 25.4 seconds. If you try to raise the max ETA value above 25.4, the lter will be set to INF, which will accept
any vehicle with an estimated time of arrival greater than the minimum.
On the previous window, check the box to the left of the ETA label to enable the ETA lter (only ETAs within the range will activate zone outputs); uncheck the box to disable the ETA lter (all ETAs will activate zone outputs).
Qualified Count
A qualied detection is a detection in a zone that meets the specied range, speed and ETA
Page 80
CHAPTER 7  CHANNELS-ALERTS-ZONES 79
lters. e SmartSensor Advance provides two very powerful detection qualication lters: Qualied Count and Dynamic Density™. ese lters are mutually exclusive (only one may be active at a time).
e qualied count lter is used to limit a zone’s outputs to times when there are a certain number of qualied detections in the zone at one time.
Click in the Qualied Count range and the Edit Qualied Count lter will appear. Edit the min and max values to set the qualied count range (see Figure 7.20). Only qualied detections within the set range will activate zone outputs. e minimum qualied count value is 1 and the maximum qualied count value is 25.
Figure 7.20 – Qualified Count Filter
Click the radio button to the left of the Qualied Count label to enable the qualied count lter.
Dynamic Density
Dynamic Density is a type of vehicle platoon detection that activates a zone’s output when the number of qualied detections within a zone equals or exceeds a density requirement. e following equations explain the density requirement formula, called the Dynamic Density Count Requirement (DDCR).
First, trac density is dened as the number of vehicles within a zone, divided by the area of the zone (see Figure 7.21).
Density =
Number of Vehicles in a Zone
Zone Size (ft.) x Lane Tuning Factor
Figure 7.21 – Required Density Equation
To maintain a given level of eciency, the required density increases as speeds decrease;
similarly, the required density decreases as speeds increase. erefore, to achieve a Required Flow Rate, the density of trac will dynamically change with the speed of the vehicles as shown in Figure 7.22.
Density =
Required Flow Rate
Speed
Figure 7.22 – Flow Rate Equation
In addition, the Required Flow Rate is equal to the ideal ow rate multiplied by the re­quired % Utilization. Since ideal ow rate is inversely proportional to the ideal time Head-
Page 81
80 CHAPTER 7  CHANNELS-ALERTS-ZONES
way between vehicles, this can be written as show in Figure 7.23.
%Utilization
Time Headway
Required
Flow Rate
%Utilization
Ideal
Flow Rate
=
x
=
Figure 7.23 – Equation for Dynamic Density Vehicle Count Threshold
Consequently, the Dynamic Density Count Requirement (DDCR) calculated by the Dy­namic Density lter is computed as shown in Figure 7.24.
Time Headway x Instantaneous Mean Speed in Zone
%Utilization x Lane Tuning Factor x Zone Size
Dynamic Density
Count Requirement
(DDCR)
= Round
Figure 7.24 – Dynamic Density Count Requirement Equation
If the number of qualied detections is equal to or greater than the DDCR, then the Dy­namic Density requirement has been satised and the zone output will be activated.
Table 7.1 below reviews the components of the Dynamic Density lter. e number of
qualied detections and their average speed is detected by the sensor. en based upon
values of Zone Size, % Utilization, Tuning Factor, and headway parameters entered by the
user, the DDCR will be calculated and the zone output determined.
Component Description
Detected by the Sensor
Qualified Count The number of vehicles that meet a
zone’s range, speed and ETA filters.
Speed The average speed of all qualified detec-
tions in the specified zone, as calculated by the sensor (ft per second).
Entered by the User
Zone Size The length of the specified zone (ft.).
%Utilization Specified by the user (%).
Tuning Factor Specified by the user.
Headway Specified by the user (seconds per ve-
hicle).
Table 7.1 – Description of Dynamic Density Equation
Click in the display area beneath the Dynamic Density label to edit the Dynamic Density lter (see Figure 7.25).
Page 82
CHAPTER 7  CHANNELS-ALERTS-ZONES 81
Figure 7.25 – Dynamic Density Filter
Dynamic Density allows the SS200 to generate outputs based on trac eciency. e
three lter elements (Headway, % Utilization, and Tuning Factor) are combined with the
size of the zone and the average speed of qualied detections to create a detection density threshold that changes with the uctuations in detected trac.
Headway refers to the time separation of the front edge of two consecutive vehicles travel­ing in a given lane. e headway metric is inversely proportional to the ow rate of a given lane and is widely used as a measure of how eciently trac is owing in a given lane.
A typical headway value for heavily traveled lanes is two seconds, which corresponds to a ow rate of 1800 vehicles per hour. In the Dynamic Density settings, the minimum head­way value is 0.1 seconds and the maximum headway value is 10.0 seconds.
% Utilization refers to the ratio of observed ow rate to ideal ow rate. It is a measure used to describe trac eciency in terms of the ideal eciency. In the Dynamic Density set­tings, the minimum utilization value is one percent and the maximum utilization value is 100 percent.
Note
Consider a case where a lane is operating at the lower bounds of acceptable eciency when only 75 percent of it’s ideal flow rate was realized. If the ideal flow rate were 1800 vehicles per hour, then the lane is being used adequately at a flow rate of 0.75 * 1800 vehicles/hour = 1350 vehicles/hour (or a headway of 2.67 seconds).
e Tuning Factor is a general-purpose scale factor used to adjust observed results to rep­resent actual road conditions. e tuning factor resides in the numerator of the Dynamic Density equation. e initial recommendation for the tuning factor value is to set it equal to the number of lanes being observed by the sensor. e minimum tuning value is 0.1 and the maximum tuning value is 10.0.
Page 83
Page 84
In this chapter
Right Sidebar Left Sidebar Tracker Highlighting
8
e Verify Channels-Alerts-Zones screen contains both conguration and detection infor­mation (see Figure 8.1).
Figure 8.1 – Verify CAZ Screen for Advance (left) and Advance Extended Range (right)
Verify Channels-Alerts-Zones 8
Page 85
84 CHAPTER 8  VERIFY CHANNELS-ALERTS-ZONES
Note
When verifying channels, alerts and zones, you can use the range scale to help identify whether you have SmartSensor Advance or SmartSensor Advance Extended Range.
is chapter will explain the dierent views and capabilities of the Verify Channels–Alerts– Zones screen. e main sections of the screen (the right sidebar, the left sidebar and the
roadway display) will allow you to verify that the SmartSensor Advance is functioning correctly.
Note
Simple channels are shown on the right side bar with the letter “S” next to the chan­nel LED; latched channels are shown with the letter “L.”
Right Sidebar
e right sidebar is designed to show detections and summarize conguration settings for all channels, alerts and zones (see Figure 8.2). A channel must be enabled in order to be included in the list of individual channels that can be veried.
Figure 8.2 – Right Sidebar
e right sidebar also allows you to select which CAZ element is highlighted in the roadway and displays the corresponding outputs of each congured CAZ element (see Table 8.1).
Page 86
CHAPTER 8  VERIFY CHANNELS-ALERTS-ZONES 85
Outputs ON Color OFF Color Disabled Color
Channel Red
Gray Blank
Alert Red
Zone 1 Green
Zone 2 Blue
Zone 3 Yellow
Zone 4 Red
Table 8.1 – Right Sidebar Output Colors
Click and hold the right sidebar display button to access the display mode list (see Figure 8.3).
Figure 8.3 – Right Sidebar Display Mode List
Hidden
e hidden view hides the right sidebar and is used to simplify the overall appearance of the verication screen.
(All) Channels
e (All Channels) view shows an LED for each of the SmartSensor Advance’s eight channel outputs. e channel outputs are transmitted to a contact closure device, which in turn generates an appropriate signal on the corresponding contact closure output channels.
e channel LED is colored red when a given channel’s output is activated. e channel LEDs also show the eects of the channel’s delay and extend settings.
To identify which detections are aecting the channel’s output, click on the channel output
you want to identify (see Figure 8.4). If a detection meets the selected channel’s alert and zone lter settings, the tracker will be highlighted light blue.
Page 87
86 CHAPTER 8  VERIFY CHANNELS-ALERTS-ZONES
Figure 8.4 – All Channels Mode
Tip
Click and hold on a channel LED to open the individual channel summary screen. The channel summary screen shows the channel type, delay and extend settings and all enabled alerts for that channel.
Individual Channel
e individual channel view allows you to see the CAZ elements dened for a given chan­nel (see Figure 8.5).
Figure 8.5 – Individual Channel View (Simple Channel) for Advance (left)
and Priority Channel for Advance Extended Range (right)
Page 88
CHAPTER 8  VERIFY CHANNELS-ALERTS-ZONES 87
Note
In Figure 8.5 the dashed, gray line near the top of the zone is used to indicate the location of the discovery range threshold for this priority channel. Vehicles first dis­covered before the discovery range threshold will be highlighted when viewing at the Level 1 alert and will also have a priority level of one when shown on the roadway. Vehicles first discovered after the discovery range threshold will be highlighted when viewing at the Level 2 alert and will also have a priority level of two when shown on the roadway.
Simple channels (annotated with an S) show only the channel output in the right-side bar, and priority channels (annotated with a P) go one layer deeper to the alert level. Because a priority channel only has one zone for each alert, only the alert level is shown. e normal channel (annotated with an N) and latched channel (L) go further down to the zone level (see Figure 8.6).
Figure 8.6 – Individual Channel View (Normal Channel)
A zone output is activated when its detection qualication lters are satised; an alert out­put is activated when the associated zone outputs fulll the alert’s logic lter; and a channel output is activated when the associated alert outputs (and related delay and extend settings) fulll the channel’s requirements.
Note
Only channel outputs are reported to contact closure devices. While they are reported to SSMA, zone and alert outputs are not directly associated with any contact closure outputs.
e channel name is displayed above the channel LED. Latched channels display an L
Page 89
88 CHAPTER 8  VERIFY CHANNELS-ALERTS-ZONES
next to the channel LED (see Figure 8.7). A channel’s delay, extend and max timer settings are shown next to the D:, E: and M: labels under the channel LED. An alert identier is displayed above each alert LED; the alert logic indicator (OR/AND) is located beneath each alert LED. Only one alert can be expanded at a time.
Figure 8.7 – Individual Channel View (Latched Channel)
A zone label (Z1, Z2, Z3, Z4) is displayed to the right of each zone LED. If an alert has an inverted zone, a logical NOT marker (solid black line) is displayed above the associated
zone label.
Tip
Click and hold on the alert LED to view the Alert Summary screen. The top of the Alert Summary screen shows the channel that the alert belongs to. The rest of the screen shows the logic applied to the alert, which zones are enabled and which zones are inverted (if any).
Click and hold on the Zone LED to view the Zone Summary screen. The top of the Zone Summary screen shows the channel and alert that the zone belongs to; the rest of the screen shows the zone’s Range, Speed, ETA and Qualified Count settings for the selected zone.
Channel LED
e channel LED is colored red whenever a channel’s output requirements are met (see the Display Mode section). When a channel is selected, trackers are highlighted in light blue if they meet any of the selected channel’s zone lters (see Figure 8.8). is form of tracker highlighting helps you know which detections are aecting the channel’s output.
Page 90
CHAPTER 8  VERIFY CHANNELS-ALERTS-ZONES 89
Figure 8.8 – Channel LED
Alert LED
e alert LED is colored red when an alert’s output requirements are met (see Figure 8.9). If an alert is selected, the corresponding zones will appear on the roadway, each with a unique color.
Figure 8.9 – Alert LED
Zone LED
Each of the four available zones show a dierent color. is color mapping between zone
rectangles, trackers and zone LEDs shows how trackers aect zone outputs (see Table 8.2).
Zone Color
1 Green
2 Blue
3 Yellow
4 Red
Table 8.2 – Zone Colors
Page 91
90 CHAPTER 8  VERIFY CHANNELS-ALERTS-ZONES
When an alert is selected, the alert’s enabled zones are displayed on the roadway. e other enabled zones in the corresponding alert are shown as gray rectangles (see Figure 8.10). When a zone’s detection qualication requirements are met (or NOT met, if the zone out­put is being inverted), the corresponding zone LED is colored its corresponding zone color.
Figure 8.10 – Zone Highlighting
Note
Tracker highlight behavior is determined by the selected roadway display mode.
Roadway Display
e roadway display is used to show trackers and their relationship with detection zones (see Figure 8.11).
Figure 8.11 – Roadway Display
e area between the sensor icon and the top part of the roadway display represents the
Page 92
CHAPTER 8  VERIFY CHANNELS-ALERTS-ZONES 91
sensor’s maximum detection range. e sensor icon is always displayed at the bottom of the roadway and points towards the top of the screen. Sensor detections (trackers) are displayed on the roadway in relation to their distance from the stop bar.
e CAZ selection display is located on the top of the roadway and contains the currently
selected channel, alert and zone (see Figure 8.12).
CAZ
selection
display
Figure 8.12 – Name and Range Labels
Note
Clicking on the CAZ selection display opens the CAZ Setup screen, with the tab for the current channel selected.
e stop bar icon represents placement of the sensor relative to the approach’s stop bar. A stop bar label showing the relative location of the stop bar will be displayed whenever the stop bar is not on the screen.
Click on an alert or zone in the right sidebar to display the corresponding zone(s) in the roadway. Clicking inside a zone rectangle will turn on the name and range labels for the selected zone; click anywhere outside of the zone to turn range labels o.
Various types of detection-related data can be displayed on the tracker on the roadway. e
roadway display button is used to select the type of information displayed on the trackers.
Note
Trackers are always colored gray unless a highlight is being applied.
Page 93
92 CHAPTER 8  VERIFY CHANNELS-ALERTS-ZONES
Click and hold on the roadway display selector to access the roadway display mode list (see Figure 8.13).
Figure 8.13 – Roadway Display Mode List for Advance (left)
and Advance Extended Range (right)
Left-click the roadway display button to cycle forward through the available modes; right­click to cycle backwards through the list (right-clicking is only available on the PC version of the SSMA software).
Range (ft) – Displays the range of the associated tracker to the stop bar. Speed (mph) – Shows the speed of the associated tracker. ETA (s) – Shows the tracker’s Estimated Time of Arrival (in seconds) to the stop bar. ID – Displays the ID number of the associated tracker. SSMA assigns a unique ve-
digit identication number (1 to 99999) to each tracker.
Qualified Count – e two types of Qualied Count displays available are Qualied
Count and Dynamic Density. e data displayed on the trackers depends on the type
selected in the Setup CAZ screen.
Discovery Range – Displays the range at which the tracker was rst detected. (Only
available with SmartSensor Advance Extended Range.)
Priority Level – Shows the priority level assigned to a vehicle based upon its discovery
range. Level 1 priority is the highest priority. Level 2 is the highest priority. (Only available with SmartSensor Advance Extended Range.)
Tri-view – Allows up to three user-specied modes to be displayed on each tracker. (blank) – Removes all data from the tracker displays. (disabled) – Disables the trackers on the roadway. However, the LEDs in the right
sidebar will function as normal.
Note
The disabled mode may be useful when communication is slow or unreliable.
Page 94
CHAPTER 8  VERIFY CHANNELS-ALERTS-ZONES 93
Qualified Count
When the Channel LED is activated in the right sidebar, the Qualied Count value will always be displayed as “---” because a channel may consist of up to 16 zones and the exact meaning of a channel’s Qualied Count is undened.
When using the Qualied Count display mode, the rst number on the tracker represents the number of qualied detections in the zone and the number in parentheses represents the amount of trackers needed to meet the dened requirements. If the number of qualied detections is below the Qualied Count minimum, the number in parentheses is preceded by a “-”; if the number of qualied detections is higher than the Qualied Count maximum, the number in parentheses is preceded by a “+”; if the number of qualied detections is in between the Qualied Count minimum and maximum settings, a “0” is displayed.
Figure 8.14 describes the numbers displayed when the qualied count is lower than, within the limits of, or higher than the specied settings.
Detected Qualified Count
Qualified Count Minimum
Qualified Count Maximum
Displayed Text
1 2 4 01 (-01)
3 2 4 03 (00)
6 2 4 06 (+02)
Figure 8.14 – Display Text for Qualified Count Zone Types
Note
When the selected roadway display mode shows the qualified count value on the detection, the tracker highlighting indicates whether the specific detection meets the range, speed, ETA, and priority level qualifications of the associated zone. High­lighting on an individual tracker does not indicate whether or not there are enough qualified detections to satisfy the qualified count filter for the zone.
Page 95
94 CHAPTER 8  VERIFY CHANNELS-ALERTS-ZONES
Dynamic Density
e Dynamic Density parameters determine the number of trackers that are required to meet the specied level of eciency.
Figure 8.15 describes the text displayed when the Qualied Count is lower than, equal to, or higher than the Dynamic Density thresholds. e number of qualied detections is fol­lowed by a percentage number. e percentage is the count ratio of the current number of qualied detections divided by the DDCR (see Figure 8.16).
Detected Qualified Count
Dynamic Density Threshold
Displayed Text
2 4 02 (050%)
4 4 04 (100%)
6 4 06 (150%)
Figure 8.15 – Display Text for Dynamic Density Zone Types
(DDCR)
Percentage =
Number of Qualified Detections
x 100%
Figure 8.16 – Percentage Equation
e zone output will be activated when the count ratio is equal to or greater than 100 percent. e percentage is displayed in the roadway display to help you tune the Dynamic Density parameters and extend the green light when desired.
Note
It is recommended that you adjust the Tuning Factor instead of the Headway and %Utilization parameters.
Page 96
CHAPTER 8  VERIFY CHANNELS-ALERTS-ZONES 95
Tri-view
Congure the tri-view display by clicking and holding on the roadway display selector
while the tri-view mode is active. e desired modes can then be selected on the Tri-view Trackers screen (see Figure 8.17).
Figure 8.17 – Tri-view Trackers for Advance (left) and Advance Extended Range (right)
e discovery range is abbreviated “D. Range” in the tri-view menu and abbreviated “Disc.” in the selector bar. Priority Level is abbreviated “P. Level” and “Level” respectively.
Any mode can be assigned to display on the left (1), middle (2) or right (3) side of the tracker display (see Figure 8.17 and 8.18). A mode cannot be displayed in more than one location and removing a check mark will disable the corresponding column.
Figure 8.18 – Tri-view Display Mode
Note
The tri-view Qualified Count (Q. Count) data shows only part of the data displayed in the Qualified Count display mode. The Qualified Count displays the count, but does not display the amount of trackers needed to meet the defined requirements; the Dynamic Density displays the percentage, but does not display count.
Page 97
96 CHAPTER 8  VERIFY CHANNELS-ALERTS-ZONES
Clicking anywhere else in the roadway display causes the Select Roadway View screen to
appear (see Figure 8.19). is selection screen allows you to select which channel, alert or zone is displayed on the roadway.
Figure 8.19 – Select Roadway View
When a channel is selected, light blue is used to indicate that that this track meets the
range, speed, ETA, and discovery range requirements of at least one of the channel’s zones.
It is often useful to select the alert or zone level on the right side bar to better understand how tracker highlighting works. When an alert or zone is selected, the four zone colors
are used to indicate that a tracker meets ALL of a zone’s range, speed ETA, and discovery
range requirements. When verifying alerts or zones, if a tracker is highlighted light blue, this indicates that even though the tracker does not meet ALL range, speed, ETA, and dis­covery range requirements, it does at least meet the requirement for the currently displayed
range, speed, ETA, discovery range (or priority level) property.
Tracker Highlighting
When a channel, alert or zone is selected on the right sidebar, trackers will be highlighted
to help visualize which detections meet range, speed and ETA requirements. is type of
visualization can be very helpful when verifying programming logic.
Dierent highlight colors are applied depending on whether the channel, alert or zone verication has been selected. If a tracker is highlighted, it will be either light blue or the zone color; if a tracker is not highlighted, it will be displayed with the default gray color.
Table 8.3 below explains the meaning of each color, based on the sidebar selection.
Sidebar Selection Tracker Highlight Description
Channel Light Blue
Meets ALL range, speed and ETA requirements of one of the chan­nel’s zones.
Alert or Zone
Light Blue
Meets a range, speed or ETA zone requirement.
Z1 - Green
Meets ALL range, speed and ETA zone requirements.
Z2 - Blue
Z3 - Yellow
Z4 - Red
Table 8.3 – Tracker Highlighting
Page 98
CHAPTER 8  VERIFY CHANNELS-ALERTS-ZONES 97
When a channel is selected, light blue is used to indicate that this tracker meets the range,
speed and ETA requirements of at least one of the channel’s zones. is usually indicates
that this tracker will activate the channel output. However, this is not always true when Qualied Count, Dynamic Density, zone output inversion or Boolean AND logic is used.
It is often useful to select the alert or zone level on the right side bar to better understand how tracker highlighting works. When an alert or zone is selected, the four zone colors are
used to indicate that a tracker meets ALL of a zone’s range, speed and ETA requirements.
When verifying alerts or zones, if a tracker is highlighted light blue, this indicates that even
though the tracker does not meet ALL range, speed and ETA requirements, it does at least meet the requirement for the currently displayed range, speed or ETA property.
e zone highlighting rules also apply to the corresponding sections of the tri-view dis-
play. In Figure 8.20 below, the range and ETA display sections are highlighted light blue,
meaning that those requirements have been met, but the speed section is not highlighted,
meaning that its requirement has NOT been met (and the zone LED is o ). When all
requirements are met, the entire tracker will turn the zone color.
Figure 8.20 – Tri-view Display that Does Not Meet the ETA Filter
Note
When an alert is selected for highlighting, the speed and ETA of the tracker are only highlighted light blue when the vehicle is within the range of the zone. This is nec­essary when you have multiple zones. However, because discovery range and prior­ity level can only be used with one zone, they can be highlighted before the vehicle reaches the extents of the zone.
Page 99
98 CHAPTER 8 VERIFY CHANNELS-ALERTS-ZONES
Left Sidebar
e left sidebar allows you to view the scale of the roadway and create a tracker log le. Click on the left sidebar selector to cycle through the available views or click and hold on the selector to open the view menu. Below is a list and description of the three views con­tained in the left sidebar:
Hidden View – Hides the left sidebar and is used to simplify the overall appearance of
the Verify CAZ screen.
Scale View – Shows a distance scale relative to the stop bar. e sensor is always dis-
played at the bottom and is oriented to point towards the top of the screen.
Logging View – Allows you to create a log le (see Figure 8.21). e data can then be
post-processed for performance analysis and can be used as the tracker data source when establishing a virtual connection.
Figure 8.21 – Tracker Logging View
Creating a Tracker Log File
Click on the Log File icon to select a log le. e Select Tracker Log File screen allows you to specify the name of an existing log le or to create a new le (see Figure 8.22).
Page 100
CHAPTER 8  VERIFY CHANNELS-ALERTS-ZONES 99
Figure 8.22 – Select Log File
Click the ON/OFF toggle switch icon to the ON position to begin tracker logging. Once activated, the duration of the logging session is displayed on the Elapsed: timer display. Click the toggle switch to the OFF position to end a tracker logging session.
e tracker log le is an ASCII text le and can be viewed using a standard text editor. Click on the View Log icon to view the current log le using the system’s default text editor (see Figure 8.23).
Figure 8.23 – Log File
Loading...