ATC Controller Operating Manual - Rev 4

Transcription

Operating Manual
Peek ATC Controllers
ATC-1000, ATC-2000 and ATC-3000 Advanced Traffic Controllers
Featuring
Version 3.8
Peek ATC Controllers Operating Manual Cover Art
p/n 99-538 Rev 4
Operating Manual
Peek ATC Controller
ATC-1000, ATC-2000 & ATC-3000 Advanced Traffic Controllers
1/19/2012
p/n: 99-537, Rev 4
Copyright © 2012 Peek Traffic Corporation.
All rights reserved.
Information furnished by Peek is believed to be accurate and reliable, however Peek does not warranty the
accuracy, completeness, or fitness for use of any of the information furnished. No license is granted by
implication or otherwise under any intellectual property. Peek Traffic reserves the right to alter any of the
Company's products or published technical data relating thereto at any time without notice.
No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or via
any electronic or mechanical means for any purpose other than the purchaser’s personal use without the
expressed, written permission of Peek Traffic Corporation.
Peek Traffic Corporation
2906 Corporate Way
Palmetto, FL 34221 U.S.A.
Trademarks
Peek ATC Controller, ATC-1000, ATC-2000, ATC-3000, IQ-Link, ATCLink, GREENWave, and IQ Central are
trademarks or registered trademarks of Peek Traffic Corporation in the United States and other countries.
TransCore and TransSuite are registered trademarks of Roper Industries, Inc. Microsoft and Windows are
trademarks or registered trademarks of Microsoft Corporation. Other brands and their products are
trademarks or registered trademarks of their respective holders and should be noted as such.
manual assembly: 81-1285
manual content: 99-537, Rev 4 (Greenwave v3.8)
manual cover art: 99-538
Contents
Preface — About This Manual ................................................................................... 1 Purpose and Scope ................................................................................................................................. 1 Assumptions ............................................................................................................................................ 1 Controller Software Version .................................................................................................................... 2 Related Documents ................................................................................................................................. 2 Technical Assistance............................................................................................................................... 3 Conventions Used in this Manual ............................................................................................................ 3 Typographic Conventions ................................................................................................................. 3 Keyboard and Menu Conventions .................................................................................................... 4 Symbol Conventions ......................................................................................................................... 4 Chapter 1 — Introduction to the ATC Controllers ................................................... 5 ATC-1000 Controller ......................................................................................................................... 6 ATC-2000 Controller ......................................................................................................................... 7 ATC-3000 Controller ......................................................................................................................... 8 Traffic Engine .................................................................................................................................... 9 Controller Hardware .............................................................................................................................. 11 Enclosure ........................................................................................................................................ 11 Operating System, Software, Firmware and Memory ..................................................................... 12 Display ............................................................................................................................................ 12 Keypad ............................................................................................................................................ 12 Comms and Utility Connectors ....................................................................................................... 15 I/O Module Connectors ................................................................................................................... 19 Heartbeat LED ................................................................................................................................ 20 Data Key Port ................................................................................................................................. 20 Power System ................................................................................................................................. 20 Basic Operations ................................................................................................................................... 21 Adjusting Screen Contrast .............................................................................................................. 21 Turning the Backlight On and Off ................................................................................................... 22 Entering Edit Mode ......................................................................................................................... 23 Entering the Utilities Menus ............................................................................................................ 23 Viewing Help Screens ..................................................................................................................... 24 GreenWave ATC Series Software ........................................................................................................ 25 Checking the Current Version of Firmware..................................................................................... 25 Updating GreenWave Using a USB Memory Device...................................................................... 26 Chapter 2 — Quick Start: Getting an ATC Set Up and Running .......................... 31 Overview ............................................................................................................................................... 32 Hardware Setup Checklist ..................................................................................................................... 32 Configuring the Ethernet Ports .............................................................................................................. 32 Configuring ATC Link and the SNMP Manager .................................................................................... 33 Loading a Default Database into the Controller .................................................................................... 34 Field Deployment .................................................................................................................................. 35 Programming a Basic Intersection ........................................................................................................ 36 Programming a Basic Phase-Based Intersection ........................................................................... 36 Programming a Basic Interval-Based Intersection.......................................................................... 37 ATC Controller Operating Manual
iii
Contents
Chapter 3 — Introduction to the Interface ............................................................. 39 Overview ................................................................................................................................................ 40 Navigating in the Environment ............................................................................................................... 40 Firmware Flow Chart ............................................................................................................................. 42 Flow Chart of the Entire Menu System .................................................................................................. 43 Chapter 4 — Status Displays .................................................................................. 45 Overview of the Status Screens ............................................................................................................ 46 Status Menu .................................................................................................................................... 46 Navigating the Status Screens ........................................................................................................ 46 Controller Status Menu .......................................................................................................................... 47 Runtime Status Screen ................................................................................................................... 47 Coordination Status Screen ............................................................................................................ 53 Time of Day Status Screen ............................................................................................................. 57 Preemption Status Screen .............................................................................................................. 58 Detector Status Menu ..................................................................................................................... 60 TSP Status Screens ........................................................................................................................ 62 Overlaps Status Menu ..................................................................................................................... 66 Sequencing Status Screen .............................................................................................................. 68 Texas Diamond Status Screen ....................................................................................................... 70 Inputs/Outputs Status Menu .................................................................................................................. 71 Inputs Status Screen ....................................................................................................................... 71 Outputs Status Screen .................................................................................................................... 73 SDLC & FIO Status Screens ........................................................................................................... 74 Alarms Status Menu .............................................................................................................................. 75 Unit Alarm Status 1 & 2 Screen ...................................................................................................... 75 Short Alarm Status Screen .............................................................................................................. 76 MMU Status Screens ............................................................................................................................. 77 Revisions Screen ................................................................................................................................... 78 Chapter 5 — Programming Menus ......................................................................... 79 Overview of the Programming Screens ................................................................................................. 80 Unit Configuration Menu ........................................................................................................................ 80 Start-Up Configuration Screen ........................................................................................................ 81 Program Flash Screen (MUTCD Flash) .......................................................................................... 83 Phase Compatibility Screens .......................................................................................................... 85 Channels Screens ........................................................................................................................... 88 Comms and I/O Setup Menu ........................................................................................................... 90 Ring Sequencing Screens ............................................................................................................. 119 USTC Miscellaneous Screen ........................................................................................................ 121 Absolute Zero Screen (ABS ZERO) .............................................................................................. 124 Logic Processing Menu ................................................................................................................. 126 Exclusive Pedestrian Operation .................................................................................................... 128 Controller Menu ................................................................................................................................... 136 Phase Enables Screen .................................................................................................................. 137 Green Timing Screens .................................................................................................................. 138 Clearance Timing Screens ............................................................................................................ 140 Pedestrian Timing Screens ........................................................................................................... 141 Added Initial Timing Screens ........................................................................................................ 142 Gap Reduction Timing Screens .................................................................................................... 143 Dynamic Max Timing Screens ...................................................................................................... 146 Phase Options Screens ................................................................................................................ 147 Recalls........................................................................................................................................... 151 Overlap Menu ................................................................................................................................ 153 Coordination Menu .............................................................................................................................. 154 Time of Day Menu ............................................................................................................................... 155 Time of Day Actions Menu ............................................................................................................ 156 iv
Contents
Day Plan Screens ......................................................................................................................... 160 Schedule Screens ......................................................................................................................... 161 Override Commands Screen ........................................................................................................ 163 Set Local Time Screen ................................................................................................................. 166 Advanced Time Setup Screen ...................................................................................................... 167 Daylight Saving Setup Screen ...................................................................................................... 169 Detectors Menu ................................................................................................................................... 173 Vehicle Detector Options Screens ................................................................................................ 174 Vehicle Detector Timing Screens ................................................................................................. 176 Detector Call Phases Screen........................................................................................................ 177 Switch Phases Screen .................................................................................................................. 178 Pedestrian Detectors Screen ........................................................................................................ 178 Enhanced Vehicle Detectors Screen ............................................................................................ 180 Enhanced Pedestrian Detectors Screen....................................................................................... 180 Preemption Menu ................................................................................................................................ 182 Using the Interval Menu ...................................................................................................................... 183 Transit Signal Priority Menu ................................................................................................................ 184 Chapter 6 — Coordinated Operation .................................................................... 185 General Overview of Coordination ...................................................................................................... 186 Pattern Changes in a Coordinated Environment .......................................................................... 188 Coordination Menu .............................................................................................................................. 190 Coordination Variables Screen ..................................................................................................... 190 Pattern Table Screens .................................................................................................................. 195 Split Table Screens ....................................................................................................................... 202 Offset Correction Ext/Reduce ....................................................................................................... 204 Coordination Pattern Consistency Checks .......................................................................................... 205 Calculating “Required Clearance” (Checks 10 and 11) ................................................................ 206 Required Clearance Calculation Reason and Example................................................................ 207 Additional Functions Used to Coordinatean Actuated ATC .......................................................... 208 Example of FO And Permissive Placement .................................................................................. 208 Chapter 7 — Interval Operation ............................................................................ 213 Overview ............................................................................................................................................. 214 Calling the Plans ........................................................................................................................... 215 Using the Interval Programming Screens ........................................................................................... 217 Timing Plan Menu ......................................................................................................................... 217 Signal Plans Menu ........................................................................................................................ 220 Interval-based Preemption ............................................................................................................ 225 Interval-Based Preemption Programming Screens ............................................................................. 228 Modifiers Screens ......................................................................................................................... 228 Track Interval Data Menu and Screens ........................................................................................ 230 Dwell Interval Data Menu and Screens ........................................................................................ 233 Exit Interval Data Menu and Screens ........................................................................................... 236 Interval Skipping Screens ............................................................................................................. 239 Interval Preemption Priority ................................................................................................................. 242 Input Priority .................................................................................................................................. 242 Setting up an Actuated Leading or Lagging Left Turn ......................................................................... 244 Wrong Way to Program a Leading Left Turn ................................................................................ 244 Correct Way to Program a Leading Left Turn ............................................................................... 246 Correct Way to Program a Lagging Left Turn ............................................................................... 248 Chapter 8 — Phase-based Preemption ................................................................ 251 Overview ............................................................................................................................................. 252 Programming Phase-Based Preemption ............................................................................................. 255 Preemption Menu ......................................................................................................................... 255 Enable/Input Params Screens ...................................................................................................... 256 ATC Controller Operating Manual
v
Contents
Entry Screens ................................................................................................................................ 258 Track Clearance Screens .............................................................................................................. 260 Dwell / Cyclic Screens ................................................................................................................... 262 Exit Screens .................................................................................................................................. 264 ICC Preemption ................................................................................................................................... 265 Chapter 9 — Overlaps............................................................................................ 267 Overview .............................................................................................................................................. 268 Overlaps Menu .............................................................................................................................. 269 Overlap Types and Modifiers ........................................................................................................ 270 Overlaps and Compatibility ........................................................................................................... 275 Vehicle Overlaps.................................................................................................................................. 276 Leading or Delayed Vehicular Overlaps ........................................................................................ 278 Creating an Overlap ...................................................................................................................... 279 Pedestrian Overlaps ............................................................................................................................ 280 Pedestrian Overlap Types ............................................................................................................. 281 Creating a Ped Overlap ................................................................................................................. 283 Chapter 10 — Transit Signal Priority ................................................................... 285 What is TSP? ....................................................................................................................................... 286 How TSP Functions ............................................................................................................................. 287 Prioritization Methods .................................................................................................................... 289 Getting TSP Set Up ............................................................................................................................. 290 TSP Screens and Parameters ............................................................................................................. 292 Unit Parameters ............................................................................................................................ 293 Run Parameters ............................................................................................................................ 294 TSP Action Plans .......................................................................................................................... 301 Run Configuration ......................................................................................................................... 302 Queue Jumping ............................................................................................................................. 306 Split Table ..................................................................................................................................... 307 TSP Status Monitoring ......................................................................................................................... 308 TSP Troubleshooting ........................................................................................................................... 308 Chapter 11 — System Maintenance ..................................................................... 309 Database Utilities Screen .................................................................................................................... 311 Copying Database Entries ................................................................................................................... 314 Diagnostics Mode ................................................................................................................................ 317 Diagnostics Mode Interface ........................................................................................................... 318 Chapter 12 — Configuration and Troubleshooting ............................................ 327 Overview .............................................................................................................................................. 328 Utilities Menus ..................................................................................................................................... 328 Utilities Menu for the Keyboard and Display ................................................................................. 328 Additional Details About the Utilities Screens ............................................................................... 329 USB Operations ................................................................................................................................... 331 USB Menu ..................................................................................................................................... 331 Moving Databases Using a USB Drive ......................................................................................... 332 Moving Logs Using a USB Drive ................................................................................................... 333 USB File System ........................................................................................................................... 334 Data Logging ....................................................................................................................................... 335 Controller Message Log ................................................................................................................ 335 NTCIP Event Log .......................................................................................................................... 337 Advanced Controller Logging Menu .............................................................................................. 337 Setup Logging Options .................................................................................................................. 337 View Logs Screen ......................................................................................................................... 339 Preventative Maintenance and Calibration .......................................................................................... 342 Diagnosing Controller Operation ................................................................................................... 342 vi
Contents
Troubleshooting................................................................................................................................... 343 Troubleshooting Transit Signal Priority Operation ........................................................................ 344 Chapter 13 — Controller Specifications............................................................... 347 Overview of Controller Specifications ................................................................................................. 348 Physical/Environmental Specifications ......................................................................................... 349 NTCIP Compliance ....................................................................................................................... 350 Chapter 14 — Serial and Data Connectors .......................................................... 351 Overview ............................................................................................................................................. 352 Port 1 - SDLC Connector .................................................................................................................... 352 Port 2 – RS-232C Connector .............................................................................................................. 353 Port 3 – Communications Module Port ............................................................................................... 354 Port 4 - Local Connector ..................................................................................................................... 354 Port 5 – Spare/UPS Connector ........................................................................................................... 355 Ethernet Connectors ........................................................................................................................... 356 USB Connectors.................................................................................................................................. 357 Chapter 15 — I/O Module Connector Details ....................................................... 359 Connector Details ................................................................................................................................ 360 NEMA TS2 Type 1 I/O Module ............................................................................................................ 360 Port A Connector .......................................................................................................................... 360 NEMA TS2 Type 2 I/O Module ............................................................................................................ 361 Port A Connector .......................................................................................................................... 361 Port B Connector .......................................................................................................................... 366 Port C Connector .......................................................................................................................... 368 HMC-1000 I/O Module ........................................................................................................................ 371 HMC Input / Output Connector ..................................................................................................... 371 Stop Time Switch .......................................................................................................................... 373 LMD40 I/O Module .............................................................................................................................. 374 LMD40 Port A Connector.............................................................................................................. 374 LMD40 Port B Connector.............................................................................................................. 376 LMD40 Communication Inputs Connector .................................................................................... 377 LMD Port D Connector ................................................................................................................. 378 Closed Loop D Module ........................................................................................................................ 381 Auxiliary Connector (37 Pin) ......................................................................................................... 381 Preemption Connector (25 Pin) .................................................................................................... 382 Coordination Connector (26 Pin) .................................................................................................. 383 LMD9200 D Module ............................................................................................................................ 384 Aux Connector .............................................................................................................................. 384 D Connector .................................................................................................................................. 384 Traconex D Module ............................................................................................................................. 386 Multisonics D Module .......................................................................................................................... 388 Glossary .................................................................................................................. 391 Index ........................................................................................................................ 399 ATC Controller Operating Manual
vii
Contents
Table of Figures
Figure 1 – The ATC-1000 traffic controller ........................................................................................................ 6 Figure 2 – Module locations .............................................................................................................................. 7 Figure 3 – ATC-2000 Controller ........................................................................................................................ 8 Figure 4 – ATC-3000 Controller ........................................................................................................................ 8 Figure 5 – Front view of the ATC-1000 controller Main Module....................................................................... 11 Figure 6 – ATC Series keypad ........................................................................................................................ 13 Figure 7 – Comms and Utility Ports................................................................................................................. 16 Figure 8 – USB Command menu .................................................................................................................... 16 Figure 9 – Example I/O Modules ..................................................................................................................... 19 Figure 10 – Datakey type data receptacle ....................................................................................................... 20 Figure 11 – Contrast Adjust screen ................................................................................................................. 21 Figure 12 – Utilities > Miscellaneous status menu, showing Backlight Timeout .............................................. 22 Figure 13 – Utilities Menu ............................................................................................................................... 24 Figure 14 – Revisions Screen ......................................................................................................................... 25 Figure 15 – Firmware Revision Screen in the Utilities menus ......................................................................... 26 Figure 16 – Write USB Files/Folders in ATC Link............................................................................................ 27 Figure 17 – ATCLink creates the folders and files on the USB drive ............................................................... 27 Figure 18 – Directory on the USB drive........................................................................................................... 27 Figure 19 – ATC FW Loader screen ............................................................................................................... 28 Figure 20 – Select a software or firmware file and press Enter key ................................................................. 28 Figure 21 – Verify the correct firmware version ............................................................................................... 29 Figure 22 – Utilities menu Revisions Screen for Firmware .............................................................................. 30 Figure 23 – IP/Cabinet Address Setup screen ................................................................................................ 33 Figure 24 – Firmware flowchart ....................................................................................................................... 42 Figure 25 – Top-down view of the ATC-1000 Menu System ........................................................................... 44 Figure 26 – Status categories available in GreenWave v3.8 ........................................................................... 46 Figure 27 – Controller Status menu ................................................................................................................ 47 Figure 28 – Sample Controller Runtime Status screen – Phase version ......................................................... 47 Figure 29 – Runtime Status screen – Interval version ..................................................................................... 50 Figure 30 – Sample Controller Status screen – Pretimed Pattern – Details .................................................... 50 Figure 31 – Sample Coordination Status Screen ............................................................................................ 53 Figure 32 – Example of additional information about a ‘Bad Plan’................................................................... 56 Figure 33 – Sample Time of Day Status Screen ............................................................................................. 57 Figure 34 – Sample Preemption Status Screen .............................................................................................. 58 Figure 35 – Detector Status Menu .................................................................................................................. 60 Figure 36 – Sample Vehicle Detector Status Screen ...................................................................................... 60 Figure 37 – Sample Pedestrian Detector Status Screen ................................................................................. 61 Figure 38 – TSP Status Menu ......................................................................................................................... 62 Figure 39 – Sample TSP Input Status screen ................................................................................................. 62 Figure 40 – TSP Output Status screen ........................................................................................................... 65 Figure 41 – Overlaps Status Menu.................................................................................................................. 66 Figure 42 – Sample Vehicle Overlaps Status screen ...................................................................................... 66 Figure 43 – Sample Pedestrian Overlaps Status screen ................................................................................. 67 Figure 44 – Sequence Status screen .............................................................................................................. 68 Figure 45 – Texas Diamond Status screen ..................................................................................................... 70 Figure 46 – Inputs/Outputs Status Menu ......................................................................................................... 71 Figure 47 – Sample Inputs Status Screen ....................................................................................................... 71 Figure 48 – The functional sections of the Inputs Status screen ..................................................................... 72 Figure 49 – Sample Outputs Status Screen .................................................................................................... 73 Figure 50 – Page 2 of the Outputs Status Screens ......................................................................................... 73 Figure 51 – SDLC Status Screens .................................................................................................................. 74 Figure 52 – Alarms/Event Status Menu ........................................................................................................... 75 Figure 53 – Alarm Status display .................................................................................................................... 75 Figure 54 – Short Alarm Status screen ........................................................................................................... 76 Figure 55 – Sample MMU Status screen ........................................................................................................ 77 Figure 56 – Revision Details Screen ............................................................................................................... 78 Figure 57 – Programming Menu ..................................................................................................................... 80 Figure 58 – Configuration Menu ...................................................................................................................... 80 Figure 59 – Start-Up Screen ........................................................................................................................... 81 viii
Contents
Figure 60 – MUTCD Flash Screen ................................................................................................................. 83 Figure 61 – Phase Compatibility Screen (Page 1) .......................................................................................... 85 Figure 62 – Example Phase Compatibility Screen (Page 1) ........................................................................... 86 Figure 63 – Example Phase Compatibility Screen (Page 2) ........................................................................... 86 Figure 64 – Example of consistent Ring Sequencing programming ............................................................... 86 Figure 65 – Resulting Sequence Status screen ............................................................................................. 87 Figure 66 – Channels Screen (Page 1) .......................................................................................................... 88 Figure 67 – Channels Screen (Page 2) .......................................................................................................... 89 Figure 68 – Comms and I/O Setup Menu ....................................................................................................... 90 Figure 69 – Port 1 Setup Screen .................................................................................................................... 91 Figure 70 – Ports 2 through 5 Setup Screen .................................................................................................. 92 Figure 71 – IP/CAB Address setup screen ..................................................................................................... 93 Figure 72 – I/O Cabinet Setup Screen ........................................................................................................... 95 Figure 75 – I/O Cabinet Setup Screen ........................................................................................................... 98 Figure 76 – Available I/O Functions list .......................................................................................................... 99 Figure 78 – I/O Cabinet Setup Screen with new TSP Det 1 pin assignment ..................................................100 Figure 79 – Example remapping showing MSB connector ............................................................................101 Figure 80 – Available I/O Functions list .........................................................................................................101 Figure 81 – Available I/O Functions list – page 2 ..........................................................................................102 Figure 83 – Beginnning the D Module I/O mapping process .........................................................................103 Figure 84 – Selecting a D module pin for remapping.....................................................................................103 Figure 85 – Opening the I/O Functions list ....................................................................................................104 Figure 86 – Page 18 of the I/O Functions list ................................................................................................104 Figure 87 – Example remapping of a pin on the D module ............................................................................105 Figure 88 – DHCP Setup screen ...................................................................................................................106 Figure 89 – Process Control screen ..............................................................................................................107 Figure 90 – Process Control Setup screen with port 3 Not Assigned ............................................................108 Figure 91 – Process Control Setup screen ....................................................................................................109 Figure 92 – Setting Port 3 process to Not Assigned ......................................................................................110 Figure 93 – Process Control screen showing MIZBAT Client started and running.........................................111 Figure 94 – Internation Load Switch Menu ....................................................................................................112 Figure 95 – International load switches in a cabinet rack (green labels optional) ..........................................112 Figure 96 – Typical International load switch, side view ................................................................................113 Figure 97 – Internation Load Switch Board Setup screen..............................................................................113 Figure 98 – Internation Load Switch Channel Status screen .........................................................................114 Figure 99 – Internation Load Switch LSW Current Monitor configuration ......................................................115 Figure 100 – International iRMS load switch current display .........................................................................116 Figure 101 – Interanational load switch time sync response screen ..............................................................116 Figure 102 – Get / Display LSW Logs screen................................................................................................117 Figure 103 –Internation load switch errror counts screen ..............................................................................118 Figure 104 – Ring Sequencing Screen (Page 1) ...........................................................................................119 Figure 105 – Ring Sequencing Screen (Page 16) .........................................................................................119 Figure 106 – USTC Miscellaneous Screen....................................................................................................121 Figure 107 – Absolute Zero screen, page 1 of 2 ...........................................................................................124 Figure 108 – Absolute Zero screen, page 2 of 2 ...........................................................................................124 Figure 109 – Logic Processing menu ............................................................................................................126 Figure 110 – Anti-Backup & Recall Screen ...................................................................................................126 Figure 111 – Exclusive Pedestrian Screen ....................................................................................................128 Figure 112 – Phase Enables Screen with Phase 9 added .............................................................................129 Figure 113 – Adding the XPED phase to the ring sequence screen ..............................................................130 Figure 114 – Ped Timing Screen (Page 2) for XPED movement ...................................................................130 Figure 115 – Split time added to the Coord Split table for the XPED movement ...........................................131 Figure 116 – Setting Global Enable on the XPED screen..............................................................................131 Figure 117 – Setting XPED Enable on the TOD Override Commands screen ...............................................132 Figure 118 – Calling the XPED enable command from a TOD action ...........................................................132 Figure 119 – Setting destination phases on the XPED screen ......................................................................133 Figure 120 – Matching destination phase timings with XPED timing .............................................................133 Figure 121 – Ped Detectors Screen ..............................................................................................................134 Figure 122 – Exclusive Pedestrian Screen ....................................................................................................134 Figure 123 – Actuated Rest in Walk applied to XPEDs source phase ...........................................................135 Figure 124 – Controller Menu........................................................................................................................136 Figure 125 – Phase Enables Screen .............................................................................................................137 Figure 126 – Green Timing Screen (page 1) .................................................................................................138 Figure 127 – Clearance Timing Screen (Page 1) ..........................................................................................140 ATC Controller Operating Manual
ix
Contents
Figure 128 – Ped Timing Screen (Page 1) .................................................................................................... 141 Figure 129 – Added Initial Timing Screen (Page 1) ....................................................................................... 142 Figure 130 – Gap Reduction Timing Screen ................................................................................................. 143 Figure 131 – Classic Case of Gap Reduction ............................................................................................... 145 Figure 132 – Dynamic Max Timing Screen ................................................................................................... 146 Figure 133 – Phase Options Screen ............................................................................................................. 147 Figure 134 – Recalls Screen ......................................................................................................................... 151 Figure 135 – Overlaps Menu......................................................................................................................... 153 Figure 136 – Coordination Menu ................................................................................................................... 154 Figure 137 – Time of Day menu .................................................................................................................... 155 Figure 138 – Time of Day Actions menu ....................................................................................................... 156 Figure 139 – Time of Day Actions screen ..................................................................................................... 156 Figure 140 – Time of Day Action COMMAND - Example .............................................................................. 158 Figure 141 – Auxiliary/Special Function Assignment..................................................................................... 159 Figure 142 – Auxiliary outputs in the I/O mapping screens ........................................................................... 159 Figure 143 – Special Function outputs in the I/O mapping screens............................................................... 160 Figure 144 – Time of Day - Day Plan Screen ............................................................................................... 160 Figure 145 – Time of Day Schedules Screen ................................................................................................ 161 Figure 146 – Typical Weekday Schedule Day Plan, valid all year ................................................................. 162 Figure 147 – Typical Weekend Schedule Day Plan, valid all year ................................................................. 162 Figure 148 – Day Schedule Day Plan for New Year’s Day ............................................................................ 163 Figure 149 – Override Commands Screen .................................................................................................... 163 Figure 150 – Example Override Commands screen...................................................................................... 165 Figure 151 – Time Set Screen ...................................................................................................................... 166 Figure 152 – Advanced Time Setup screen .................................................................................................. 167 Figure 153 – Daylight Saving Time Settings screen ...................................................................................... 169 Figure 154 – Default DST Enabled values .................................................................................................... 170 Figure 155 – DST parameter editing screen (Default values)........................................................................ 170 Figure 156 – DST editing by exact date ........................................................................................................ 171 Figure 157 – Detectors Menu........................................................................................................................ 173 Figure 158 – Vehicle Detector Options Screen ............................................................................................. 174 Figure 159 – Vehicle Detector Timing Screen ............................................................................................... 176 Figure 160 – Detector Call Phases Screen ................................................................................................... 177 Figure 161 – Switch-to Phases Screen ......................................................................................................... 178 Figure 162 – Ped Detectors Screen .............................................................................................................. 178 Figure 163 – Enhanced Vehicle Detectors screens....................................................................................... 180 Figure 164 – Enhanced Pedestrian Detetectors screen ................................................................................ 180 Figure 165 – Preemption Menu..................................................................................................................... 182 Figure 166 – Interval Menu ........................................................................................................................... 183 Figure 167 – Transit Signal Priority Menu ..................................................................................................... 184 Figure 168 – Master Cycle Timer and Local Cycle Timer illustration ............................................................. 186 Figure 169 – Coordination Database Structure ............................................................................................. 187 Figure 170 – Pattern Selection...................................................................................................................... 188 Figure 171 – Postponing Pattern Change to Sync Faster ............................................................................. 189 Figure 172 – Coordination Menu ................................................................................................................... 190 Figure 173 – Coordination Variables Screen................................................................................................. 190 Figure 174 – Force mode comparisons ......................................................................................................... 193 Figure 175 – Pattern Table screen (48 pages, one page per pattern) ........................................................... 195 Figure 176 – Early Yield Time Example using Multiple Permissive Strategy ................................................. 197 Figure 177 – Yield Permissive Strategy ........................................................................................................ 198 Figure 178 – Single Permissive Strategy ...................................................................................................... 199 Figure 179 – Hold, Yield Point and Force Offs .............................................................................................. 200 Figure 180 – Split Table Screen.................................................................................................................... 202 Figure 181 – Split Mode 6 (Maximum and Pedestrian Recall) timing ............................................................ 203 Figure 182 – Offset Correction Extend/Reduce Split Table ........................................................................... 204 Figure 183 – Unequal Yellow and Red Time Scenarios ................................................................................ 207 Figure 184 – Typical placements of fixed force offs and permissives ............................................................ 208 Figure 185 – Interval menu ........................................................................................................................... 217 Figure 186 – Timing Plan Menu .................................................................................................................... 217 Figure 187 – Interval Cycle/Offset/Split Data (Page 1) .................................................................................. 218 Figure 188 – Interval Cycle/Offset/Split Data ................................................................................................ 219 Figure 189 – Signal Plan screen ................................................................................................................... 220 Figure 190 – Signal Plan Per Interval Modifiers (Screen 1 for Plan 1) ........................................................... 221 Figure 191 – Interval Channels-to-Intervals Map – Page 1 for Signal Plan 1 ................................................ 223 x
Contents
Figure 192 – Outputs-to-Intervals Map screen ..............................................................................................224 Figure 193 –Preemption Interval menu .........................................................................................................225 Figure 194 – Interval-based preemption run logic .........................................................................................226 Figure 195 – Wig-wag signals during pre-timed preemption using Cycle Dwell .............................................227 Figure 196 – Interval Preemption Modifiers screen .......................................................................................228 Figure 197 – Track Interval Data Menu .........................................................................................................230 Figure 198 – Track Interval Timers screen ....................................................................................................230 Figure 199 – Track Interval Channels to Intervals screen..............................................................................231 Figure 200 – Track Output Setup screen ......................................................................................................232 Figure 201 – Dwell Interval Data Menu .........................................................................................................233 Figure 202 – Dwell Interval Timers screen ....................................................................................................234 Figure 203 – Dwell Interval Channels to Intervals screen ..............................................................................234 Figure 204 – Dwell Output Setup screen .......................................................................................................235 Figure 205 – Exit Interval Data Menu ............................................................................................................236 Figure 206 – Exit Interval Timers screen .......................................................................................................236 Figure 207 – Exit Interval Channels to Intervals screen ................................................................................237 Figure 208 – Exit Output Setup screen .........................................................................................................237 Figure 209 – Interval Skipping screen ...........................................................................................................239 Figure 210 – Actuated intervals in theATCLink Interval table ........................................................................240 Figure 211 – Wrong way to program a leading left turn in interval mode (ATCLink) ......................................244 Figure 212 – Correct Programming for a Leading left turn in ATCLink ..........................................................246 Figure 213 – Programming a lagging left turn ...............................................................................................248 Figure 214 – Inserting pedestrian clearance intervals to support a lagging left .............................................249 Figure 215 – Sections of a phase-based ATC Preemption Run ....................................................................252 Figure 216 – Preemption run with a Cyclic section ........................................................................................253 Figure 217 – Preemption run linking..............................................................................................................254 Figure 218 – Preemption Menu .....................................................................................................................255 Figure 219 – Preemption Enable/Input Parameters screen ...........................................................................256 Figure 220 – Preemption Entry parameters screen .......................................................................................258 Figure 221 – Track Clearance Parameter screen ..........................................................................................260 Figure 222 – Dwell / Cyclic Parameters screen .............................................................................................262 Figure 223 – Exit Parameters screen ............................................................................................................264 Figure 224 – USTC Miscellaneous Screen....................................................................................................265 Figure 225 – Simple Overlap example ..........................................................................................................268 Figure 226 – Overlaps Menu .........................................................................................................................269 Figure 227 – Vehicular Overlap, type ntcip (1) with Parent Phases = phase 2 and phase 3 .........................270 Figure 228 – Type ntcip (1), Minus Green-Yellow version: Parent Phases = 2+3 and Modifier Phase = 2 ...271 Figure 229 – Minus Walk Ped Clear Type, Parent Phases = 2 & 3, Modifier Phase = 2 ................................271 Figure 230 – Minus Walk Red type overlap with Parent Phase = 2 & 3 and Modifier Phase = 2 ..................272 Figure 231 – Minus Walk Dark type overlap with Parent Phases = 2 & 3 and Modifier Phase = 2................272 Figure 232 – Vehicular Overlap, type Protected/Permissive (6) with Parent Phases = 1+2, Modifier Phase = 1,
Green Flash = 1+2 ...............................................................................................................................272 Figure 233 – Normal pedestrian overlap with two parent phases (phases 1 and 2).......................................273 Figure 234 – Always Clear pedestrian overlap with two parent phases (phases 1 and 2) .............................273 Figure 235 – Carryover (4) pedestrian overlap example ...............................................................................274 Figure 236 – Overlap compatiblity .................................................................................................................275 Figure 237 – Vehicle Overlaps screen ..........................................................................................................276 Figure 238 – Lead/Delay parameters on the Vehicle Overlaps screen ..........................................................278 Figure 239 – Leading, Early Leading, and Delayed Overlaps........................................................................278 Figure 240 – Pedestrian Overlap Screen ......................................................................................................280 Figure 241 – Normal pedestrian overlap with two parent phases (phases 1 and 2).......................................281 Figure 242 – Always Clear pedestrian overlap with two parent phases (phases 1 and 2) .............................281 Figure 243 – Carryover pedestrian overlap with 2 parent phases (ph. 1 and 2) and 1 modifer (ph. 1) ..........282 Figure 244 – TSP Timing Adjustment in an Intersection ................................................................................286 Figure 245 – Transit Priority Menu ................................................................................................................287 Figure 246 – TSP Action Plans, Run Configs and Runs ................................................................................288 Figure 247 – Transit Priority Menu ................................................................................................................292 Figure 248 – Unit Parameters screen............................................................................................................293 Figure 249 – Run Parameters screen ...........................................................................................................294 Figure 250 – Green Extend Mode 0: Extensions during Green/Solid Don’t Walk (SDW) ...............................296 Figure 251 – Green Extend Mode 1: Extensions during Green/Solid Don’t Walk (SDW) ...............................297 Figure 252 – Green Extend Mode 2: Extensions during Green/Walk ............................................................298 Figure 253 – Green Extend Mode 3: Extensions during Green/Walk and Green/Solid Don’t Walk ................299 Figure 254 – Green Extend Mode 4: Extensions during Green/Walk and/or Green/Solid Don’t Walk with Two
ATC Controller Operating Manual
xi
Contents
Detection Zones .................................................................................................................................. 300 Figure 255 – TSP Action Plan screen ........................................................................................................... 301 Figure 256 – TSP Run Configuration screen (Run 1, Config 1) ..................................................................... 302 Figure 257 – Navigating Run Configuration screens ..................................................................................... 303 Figure 258 – TSP Queue Jumping screen .................................................................................................... 306 Figure 259 – Split Table screen .................................................................................................................... 307 Figure 260 – System Maintenance Menu ...................................................................................................... 310 Figure 261 – Database Utilities menu ........................................................................................................... 311 Figure 262 – Hardware/Software mismatch message ................................................................................... 312 Figure 263 – Empty Database Runtime Status screen.................................................................................. 312 Figure 264 – Database Utilities screen ......................................................................................................... 313 Figure 265 – Copy Database Functions screen ............................................................................................ 314 Figure 266 – Copying Actuated Data menu .................................................................................................. 315 Figure 267 – Copying Phase Data screen .................................................................................................... 315 Figure 268 – Copying Coord Data menu ....................................................................................................... 316 Figure 269 – Copying Coord Pattern Plan data screen ................................................................................. 316 Figure 270 – Diagnostics Warning screen..................................................................................................... 317 Figure 271 – Diagnostics Menu screen ......................................................................................................... 317 Figure 272 – Diagnostics Menu screen ......................................................................................................... 318 Figure 273 – I/O Diagnostic Menu................................................................................................................. 318 Figure 274 – IO Production (Type 2) Loopback Test screen ......................................................................... 319 Figure 275 – Standard Input Test screen ...................................................................................................... 319 Figure 276 – Outputs Diagnostics Test screen ............................................................................................. 320 Figure 277 – Communication Diagnostics screen ......................................................................................... 321 Figure 278 – Memory Diagnostics screen – Before Testing Starts ................................................................ 321 Figure 279 – Diagnostic Memory Test screen ............................................................................................... 322 Figure 280 – Testing Real Time Clock – test in progress .............................................................................. 322 Figure 281 – Testing Real Time Clock screen – Status result ....................................................................... 322 Figure 282 – Testing USB Device screen ..................................................................................................... 323 Figure 283 – Testing USB Device screen when USB device is detected ...................................................... 323 Figure 284 – Launching the FW Loader screens .......................................................................................... 324 Figure 285 – Waiting for firmware file on USB or Ethernet ............................................................................ 324 Figure 286 – Update Firmware file list ........................................................................................................... 325 Figure 287 – Hardware/Software mismatch message ................................................................................... 325 Figure 288 – Keyboard/Display Utilities menu............................................................................................... 328 Figure 289 – Miscellaneous Status screen.................................................................................................... 329 Figure 290 – USB Menu ............................................................................................................................... 331 Figure 291 – ATC USB thumbdrive file system ............................................................................................. 334 Figure 292 – Log Data menu ........................................................................................................................ 335 Figure 293 – Controller Message Log ........................................................................................................... 335 Figure 294 – Sample log entry ...................................................................................................................... 336 Figure 295 – Controller Log Clear message.................................................................................................. 336 Figure 296 – Controller Message Log ........................................................................................................... 336 Figure 297 – NTCIP Event Log screen ......................................................................................................... 337 Figure 298 – Advanced Controller Log menu ................................................................................................ 337 Figure 299 – Setup Logging Options screen ................................................................................................. 338 Figure 300 – View Advanced Log Screen ..................................................................................................... 339 Figure 301 – Choose Log Data to view ......................................................................................................... 340 Figure 302 – ATC Data Collection Log (page 1 of 8)..................................................................................... 341 Figure 303 – Pin assignment looking into the Port 1 connector ..................................................................... 352 Figure 304 – Pin assignment looking into the Port 2 connector ..................................................................... 353 Figure 305 – Pin assignment, looking into the male Port 4 connector ........................................................... 354 Figure 306 – Pin assignment looking into the Port 5 connector ..................................................................... 355 Figure 307 – Pin assignment looking into the Ethernet ports ........................................................................ 356 Figure 308 – Pin assignments looking into the USB port............................................................................... 357 Figure 309 – TS2 Type 1 MS-A Connector ................................................................................................... 360 Figure 310 – Pin assignment, looking INTO the male Port A connector ........................................................ 361 Figure 311 – Pin assignment, looking INTO the female Port B connector ..................................................... 366 Figure 312 – Pin assignment, looking INTO the female Port C connector ..................................................... 368 Figure 313 – HMC-1000 Input/Output Connector .......................................................................................... 371 Figure 314 – LMD40 I/O Module - Port A ...................................................................................................... 374 Figure 315 – LMD40 I/O Module - Port B ...................................................................................................... 376 Figure 316 – LMD40 I/O Module – Communication Inputs Connector .......................................................... 377 Figure 317 – LMD I/O Module - Port D.......................................................................................................... 378
xii
Contents
Table of Tables
Table 1 – Related Documentation .................................................................................................................... 2 Table 2 – Typographic conventions used in this manual .................................................................................. 3 Table 3 – Keyboard conventions used in this manual ....................................................................................... 4 Table 4 – Symbol conventions used in this manual .......................................................................................... 4 Table 5 – Vehicle Call codes on the Runtime Status Screen .......................................................................... 48 Table 6 – Pedestrian Call codes on the Runtime Status Screen ..................................................................... 49 Table 7 – PHS codes on the Runtime Status Screeen ................................................................................... 49 Table 8 – Pattern command codes on the Runtime status screen .................................................................. 51 Table 9 – Coordination Check Faults.............................................................................................................. 55 Table 10 – Ring Status messages on the Preempt Status screen .................................................................. 59 Table 11 – TSP Inputs .................................................................................................................................... 62 Table 12 – TSP Status messages on the TSP Input Status screen ................................................................ 64 Table 13 – Sequence Consistency Checks .................................................................................................... 69 Table 14 – Module Type options .................................................................................................................... 96 Table 15 – Map Commands ........................................................................................................................... 97 Table 16 – International Load Switch Fault Codes.........................................................................................114 Table 17 – LSW board error count codes ......................................................................................................118 Table 18 – Available Interface Languages .....................................................................................................121 Table 19 – Texas Diamond operating modes ................................................................................................122 Table 20 – XPED Checklist ...........................................................................................................................129 Table 21 – Available TOD Override Commands ............................................................................................164 Table 22 – Pattern Number Descriptions .......................................................................................................187 Table 23 – Operational Mode values .............................................................................................................191 Table 24 – Coordination Correction modes ...................................................................................................191 Table 25 – Coordination Maximum modes ....................................................................................................192 Table 26 – Coordination Force Mode options ................................................................................................192 Table 27 – System Pattern modes ................................................................................................................193 Table 28 – Pattern Table Data Type ..............................................................................................................194 Table 30 – Local Zero Options ......................................................................................................................196 Table 31 – Permissive Strategies ..................................................................................................................197 Table 32 – Max Dwell/Add/Reduce................................................................................................................199 Table 33 – Split Modes ..................................................................................................................................202 Table 34 – Coordination Error Messages (Peek indicates non-NTCIP) .........................................................205 Table 35 – Traffic Responsive Split modes....................................................................................................211 Table 36 – Traffic Responsive Pattern data ...................................................................................................211 Table 37 – Pattern to Pretimed Signal Plan and Timing Plan assignments....................................................216 Table 38 – Input Priority ................................................................................................................................242 Table 39 – Troubleshooting an ATC Controller..............................................................................................343 Table 40 – TSP Troubleshooting Checklist ....................................................................................................345 Table 41 – Physical and Environmental Specifications ..................................................................................349 Table 42 – Pin Assignments for Port 1 SDLC ................................................................................................352 Table 43 – Pin Assignments for Port 2 RS-232C ...........................................................................................353 Table 44 – Pin Assignments for Port 4 ..........................................................................................................354 Table 45 – Pin Assignments for Port 5 ..........................................................................................................355 Table 46 – Pin Assignments for the Ethernet ports ........................................................................................356 Table 47 – Pin Assignments for the ATC USB port........................................................................................357 Table 48 – Pin Assignments for the ATC-1000 TS2 Type 1 MS-A connector ................................................360 Table 49 – Port A Pin Functions ....................................................................................................................361 Table 50 – To set the TS2/2 Input/Output Mode, set these inputs to these values: .......................................363 Table 51 – Cabinet Port Input Changes, by Mode .........................................................................................364 Table 52 – Cabinet Port Output Changes, by Mode ......................................................................................365 Table 53 – Port B Pin Functions ....................................................................................................................366 Table 54 – Port C Pin Functions ....................................................................................................................368 Table 55 – HMC-1000 Input/Output Connector Pin Functions .......................................................................371 Table 56 – LMD40 Port A Pin Functions ........................................................................................................374 Table 57 – LMD40 Port B Pin Functions ........................................................................................................376 Table 58 – LMD40 Communication Inputs Connector ...................................................................................377 Table 59 – LMD Port D Pin Functions ...........................................................................................................378 ATC Controller Operating Manual
xiii
Contents
xiv
Preface — About This Manual
PURPOSE AND SCOPE
This manual describes the installation and operation of the Peek ATC-Series™
Advanced Traffic Controllers, referred to as simply ATCs throughout this manual. It
discusses the options available for I/O and D modules for the controllers.
ASSUMPTIONS
It is assumed that the reader and user of this manual, the hardware, and the software
tools described herein are authorized to work in traffic cabinets by the local traffic
agency. The reader should be familiar with the operation and wiring of traffic control
cabinets and must follow all safety and security protocols of the traffic agency. It is also
assumed that the operator of an ATC is aware of what signal standards are being used
in the cabinet and follows those standards.
The Peek ATCs comply with the following standards:
NEMA TS1 – NEMA (the National Electrical Manufacturer’s Association) is a North
American trade organization that first defined the TS1 standard in 1978. This
standard was formally declared obsolete in 1992.
NEMA TS2 – This standard replaced the TS1 standard in the United States and
Canada. The current published standard is TS2-2003. It specifies operational
features and interchangeability requirements for manufacturers of traffic
equipment.
Advanced Transportation Controller (ATC) – The ATC standard, currently at
Version 5.2b, published on September 25, 2006 was defined as a new standard
integrating some features of TS2. ATC is primarily a North American standard. It
was defined by a joint committee that included the U.S. Department of
Transportation, AASHTO (the American Association of State Highway and
Transportation Officials), the ITE (Institute of Transportation Engineers), and
NEMA.
NTCIP – Compliant with the NTCIP 1201 and 1202 standards (National
Transportation Communications for ITS Protocol)
Wherever standards do not define the operation of the controller or the cabinet, Peek’s
strategy has been to use best practices combined with the most reliable, leading-edge
technologies available for each application. This is particularly true of the Peek ATC
Controller’s Preemption, Transit Signal Priority, and Interval-based traffic engines.
1
CONTROLLER SOFTWARE VERSION
This manual was written to describe Peek’s GreenWave ATC Controller software,
covering this release of the software:
Version 3.8
If your ATC is running software other than the version listed above, there may be some
differences between the screens and functions described here and the capabilities of
your controller.
RELATED DOCUMENTS
These documents provide additional information which may be useful during the
installation and configuration of a Peek ATC-Series controller:
Table 1 – Related Documentation
Document
2
Part Number
GREENWave Software Release Notes
99-545
ATC Link Operating Manual
81-1366
ATC Link Release Notes
99-577
IQ Central Operating Manual
81-1105
IQ Central Release Notes
99-427
FSK Modem Operating Manual
81-1371
ATC D Module Installation Instructions
99-562
ATC I/O Module Installation Instructions
99-563
ATC Main Board Firmware Update Instructions
99-564
ATC I/O Board Firmware Update Instructions
99-565
ATC PSU Board Firmware Update Instructions
99-566
Technical Assistance
TECHNICAL ASSISTANCE
If you need assistance or have questions related to the use of this product, please
contact Peek Traffic’s Product Support team.
Contact Information
Hours of Operation
Toll free in the U.S.: (800) 245-7660
phone: (941) 845-1200, ext 1288, 1289, or
1229
fax: (941) 845-1504
email: [email protected]
web: www.peektraffic.com/portal
M-F, 8am-5pm, Eastern Time
www.peektraffic.com
CONVENTIONS USED IN THIS MANUAL
When referring to any of the product manuals from Peek Traffic, the following
typographical conventions will aid in understanding the intent of the various topics and
procedures.
Typographic Conventions
As shown in the following table, whenever text appears in the following fonts and styles,
it indicates a special situation or meaning for the user.
Table 2 – Typographic conventions used in this manual
Description
Example
Commands or controls that must be
selected by the user appear in bold.
In the Print dialog box, select Options.
Switches or keyboard keys appear in
SMALL CAPS.
When finished selecting parameters, press
the PAGEDOWN key.
Things that the user needs to type at a
prompt or entry window, exactly as
shown, appear in this font.
Type a:\setup.exe at the prompt.
Items italicized inside slanted brackets
< > are variables that need to be
replaced while typing a command. The
slanted brackets should not be typed.
Type
c:\<install directory>\product and
press ENTER.
3
Keyboard and Menu Conventions
Some commands are accomplished with a pair or sequence of keystrokes or command
entries. The way these should be done is indicated by the way they are shown in the
instructions, as listed here.
Table 3 – Keyboard conventions used in this manual
Description
Example
A series of commands that need to be
completed in sequence will be separated by
a right slant bracket (>)
Go to Start > Programs > IQCentral
and select IQCentral.
A dash, or hyphen, ( - ) indicates keys or
controls that need to be pressed at the
same time to activate the command
Press CTRL- p to print the file.
A comma ( , ) indicates keystrokes that
need to be pressed one-after-the-other.
To print the file, press ALT-f, p.
Symbol Conventions
The following symbols are used in this manual to indicate special messages for the user.
Each indicates the level of importance that should be assigned to the associated text.
Table 4 – Symbol conventions used in this manual
Symbol
Description
Note — This icon accompanies a general note or tip about the current
topic.
Caution — This icon represents a general hazard. If the operator is
not paying attention, some action that is undesired may occur.
Important — This is a detail about the product that may not be a
hazard, but is critical to the operator’s proper understanding and use
of the product.
Warning — This icon represents a situation where some real risk
exists, whether of electrical shock or some other form of personal or
property damage. Be very careful when dealing with Warning
situations.
4
Chapter 1 — Introduction to the ATC Controllers
This chapter introduces the components, software and basic usage of the Peek ATC
Traffic Controllers. The following topics are discussed in detail in this chapter:
•
An overview of the controller, starting on page 6.
•
Details about the hardware of the various ATC controllers, page 11.
•
The basic operation of an ATC controller, on page 21.
•
An introduction to the GreenWave software, on page 25.
5
OVERVIEW OF THE CONTROLLERS
ATC-1000 Controller
This is a picture of the ATC-1000 controller, with a TS2 Type 1 Input/Output module
installed and an FSK modem in the communications slot.
Figure 1 – The ATC-1000 traffic controller
The ATC-1000 is a multi-standard traffic controller. It will fit into a variety of traffic control
cabinets, based on the hardware installed and the software settings used. It can function
as either a phase-based (NEMA) or interval-based (pre-timed) controller. With the
various I/O modules, D modules and Communications modules that can be installed into
the unit, it can be mated to a variety of cabinet wiring harnesses.
Following the ATC standard, the ATC-1000 uses the Linux operating system. It has an
engine board attached to the rear of the display and keypad modules. The engine board
runs Linux and the traffic engines that determine what outputs will be sent to which
connectors, and which inputs will be read at what time. A unique feature for the ATCSeries controllers is that they have dual traffic software engines, which allows them to
switch easilty between phase-based and interval-based operation. This is accomplished
by a simple pattern change. The ATC can be set to operate in any of the 255 NTCIP
patterns. Patterns 1 to 48 cause the ATC to operate in NEMA phase-based mode.
Patterns 101 to 228 cause the ATC to operate in interval-based mode. Pattern 254 is
Free. Pattern 255 is MUTCD Flash. Selecting any other pattern puts the ATC into
‘Backup Free’ operation.
6
Conventions Used in this Manual
Comms/Modem/2070
Module Slot
Main Module
(Display, Keypad,
Engine Board, Serial
Connectors)
Power Module
(Behind)
Input/Output Module
D Module
Slot
Figure 2 – Module locations
Power is supplied to the controller via the I/O module. The exact pins to use for power
depends on which I/O module is installed.Complete pin assignments are listed in
“Chapter 14 — Serial and Data Connectors”, starting on page 351.
Power Input on TS2 Type 1 I/O Module
This I/O module only has a single, small ‘A’ connector, which is primarily used to supply
power to the controller. Most of the other communications between the controller and
cabinet occur on the controller’s serial connectors.
Power Input on TS2 Type 2 I/O Module
There are three connectors on the TS2 Type 2 I/O module, but power is still supplied
through the left-most one, labeled ‘A’.
Power Input on LMD I/O Module
The LMD I/O module has two connectors, A and B, but power is yet again supplied on
the ‘A’ connector.
Power Input on HMC-1000 I/O Module
The HMC controllers were a line of devices manufactured by Honeywell Corporation in
the 1970s and 1980s. They were among the earliest traffic controllers that implemented
the NEMA TS1 standard. The HMC-1000 I/O module has 1 connector and a switch. The
main connector is labeled connector ‘INPUT/OUTPUT’.
ATC-2000 Controller
The ATC-2000 Advanced Transportation Controller is the same as the ATC-1000 with a
couple of additions. While the ATC-1000 is compatible with the ATC standard, the
ATC-2000 includes all of the extra features required to make it fully ATC compliant,
including a full complement of four Ethernet ports, and an On/Off switch on the front
panel.
7
Figure 3 – ATC-2000 Controller
The ATC-2000 uses the same I/O modules, D Modules and Comms modules that are
available for the ATC-1000); and it runs the same operating system and software as the
ATC-1000.
ATC-3000 Controller
The ATC-3000 is the international version of the Peek ATC controller. It is similar to the
ATC-1000, however it features a rack-mounted enclosure suitable for many of the
interval based cabinets that are used outside of North America. As a result, it does not
use the same I/O and D modules of the other two controllers. Instead, cabinet I/O is
routed through the backplane of the controller.
Figure 4 – ATC-3000 Controller
The ATC-3000 controller also runs the Linux operating system. Despite the changes to
the physical hardware, the ATC-3000 still uses the same GreenWave software as the
otehr ATC-Family controllers. The ATC-3000 can accept any of the Comms/Modem
modules that are availble for the ATC-1000 in its front panel modem slot.
8
Conventions Used in this Manual
Traffic Engine
The Peek ATC controllers and the GREENWave firmware are unique in that they
provide two distinct traffic engines, or software applications that cycle an intersection
through the desired signal sequences. The controller determines which engine to use
the pattern that is selected.
NEMA Operation
An ATC will run as a NEMA, phase-based controller as long as a pattern between 1 and
48 has been selected, or one of the two special patterns defined by NEMA as Pattern
254: Free operation, and Pattern 255: Flash. As a NEMA controller, the ATCs configure
movements within an intersection based on phases rather than intervals. A phase, as
defined in the NEMA standard, is a traffic movement that includes a sequence of signal
outputs for each movement of traffic in the order: Red --> Green --> Amber (Yellow) -->
Red. Within this environment, the ATC-Family controllers have the following capabilities:
Up to 16 phases of vehicle and pedestrian movement
Up to 16 phases in 4 rings
Up to 48 coordination patterns
Up to 16 split configurations
Up to 32 vehicle overlaps
Up to 16 pedestrian overlaps
Up to 6 preemption plans
Up to 64 vehicle detector inputs
Up to 8 pedestrian detector inputs
Up to 48 Time of Day action plans
Up to 32 Time of Day day plans
Up to 32 Time of Day schedules
The ability to communicate with a Central System via the NTCIP protocol
The ATC controllers use the US Department of Transportation sponsored and ITE
(Institute of Transportation Engineers) published Advanced Transportation Controller
standard. The physical connections that are made to the cabinet depend on which I/O
and D Modules have been installed in the unit. The ATC can be configured to use TS2
Type 1, TS2 Type 2, HMC-1000, or LMD connections. Available D modules include:
Closed Loop (3000E), LMD9200, Traconex and Multisonics.
Interval-based Operation
A Peek ATC will run interval-based patterns as long as a pattern between 101 and 228
is selected. An interval is defined as a period of time during which all of the signal
outputs generated by the controller are in a fixed state. Whenever any signal output
needs to change, that marks the beginning of a new interval.
Interval-based operation is used by most of the world other than the United States and
Canada, and even in those two countries, some cities, states, and provinces use
interval-based programming rather than NEMA programming. Although originally a
simpler programming methodology, Interval-based operation has evolved to include
9
many features that have long been standard in phase-based operation, including
preemption, TSP operation, and detector actuation to adjust timing .
Transitioning Between NEMA and Interval-Based Operation
All switches between NEMA and Interval-based operation is managed by transitioning
into and out of the Red Rest state.1 Both NEMA and Interval-based operation recognize
the Red Rest state. Peek ATC controllers utilize this area of commonality to allow the
traffic engine to transition without the need to send the intersection into Flash.
Cabinet Environment
A Peek ATC controller can function as an upgrade or replacement in any cabinets that
currently hosts an interval-based, NEMA TS1, TS2 Type 1, TS2 Type 2, HMC-1000,
LMD 40, LMD 9200, Traconex, or Multisonics traffic controller, as long as it is fitted with
the proper I/O and D modules.
1
10
Patent pending.
Controller Hardware
CONTROLLER HARDWARE
The user input and output interface, the digital and serial ports, fuses and power LEDs
are parts of the ATC ‘Main Module’. This is housed in the top left corner of the controller
enclosure and should never need to be removed from the housing.
Function Keypad
LCD Display - 40 Character × 16 Row
Alphanumeric Keypad
Heartbeat
LED
Transmit/Receive
LEDs for
each port
Fuses
Power
Status
LEDs
USB port
Serial Ports
Ethernet
Ports
Figure 5 – Front view of the ATC-1000 controller Main Module
Enclosure
The Peek ATC controllers use a modular design. All fuses, connectors, and controls are
accessible from the front of the unit, as defined in the Advanced Transportation
Controller standard. The top of the ATC housings are closed and free of any openings,
to prevent dirt, dust, water or other debris from dropping into the units. Ventilation holes
are provided on the rear of the unit. The resulting ventilation is more than enough to cool
the electronics. The design is such that foreign debris and water cannot easily enter the
case.
The controller is constructed so that it can be shipped easily via common carrier, without
the need to disassemble the unit.
11
Operating System, Software, Firmware and Memory
When an ATC controller is powered on, it loads a copy of the Linux operating system
from BIOS into flash memory and runs it. The operating system then loads the software
and stored data it needs to operate its programmed intersection. Firmware files are
stored in the Main Board, the I/O Module, and the Power Supply Unit (PSU).
The ATC’s basic functionality is defined by its programming files. These files are
maintained as data in non-volatile Flash memory. Software and firmware can be stored
or updated in the unit in two ways: either from a USB drive via the USB port at the front
of the unit, or via a Comm port (Serial or Ethernet) using an attached Microsoft Windows
PC that is running the ATCLink software utility.
The controller’s ‘database’ is a set of operating parameters that tells the software what
type of intersection is being controlled. This database can be loaded in three possible
ways: via the USB port, via an Comm port connection to a PC running ATCLink, or via
Peek’s IQ Central central traffic management software.
The controller’s Linux operating system continuously checks the integrity of the unit’s
internal memory, the loaded software, and the local database of configured parameters.
If the controller detects a fault, it will immediately terminate its watchdog output (i.e. the
‘CVM’ or ‘Fault Monitor’ signal) to the CMU or MMU. This will place the intersection into
FLASH mode. When this situation occurs, the ATC’s Heartbeat LED will stop flashing
and the front panel display will show a message indicating the cause of the condition.
Display
The front panel display of the controller is a 40 character wide by 16 row tall LCD
screen. The display can be used to view the ATC’s menu system, its currently
configured parameters, a of set status screens that display the current situation, as well
as an interface for viewing log files.
The display is fully operable over the temperature range of –4 to +158°F (–20 to +70°
C). The display will not be damaged by lower temperatures, however it is possible that
the contrast of the screen will be very light in cold conditions. In this situation, many
users simply place an ungloved hand over the display for about 20 seconds and legibility
is improved.
Contrast Control
The ATC LCD screen includes user-configurable contrast controls. To modify the
contrast of the screen, the ATC must be beyond its initial startup routine. Press the blue
function key
on the controller’s keypad, then use the contrast up and contrast down
keys to change the screen display. Contrast Up =
. Contrast Down =
.
Keypad
ATC controllers include a two section keypad to the right of the display window. The left
part includes 16 keys for alphanumeric entry and selection. The right section provides
functional keys, including the blue ‘Function’ key, the green navigation arrow keys, the
Yes, No, and ENT(Enter) buttons, and eight other function keys.
12
Controller Hardware
Figure 6 – ATC Series keypad
—
The ‘special function’ key for the controller. Pressing this button before
pressing one of the other keys showing a blue label above or around it
will command that button’s secondary function. These include opening
the Voltage/Utilities menu (MNU button), changing the controller
display brightness (UP+ and DOWN- buttons), and forcing the display
backlight on and off (YES button).
The most important function key combination is used to enter and exit
database Edit mode, using the key sequence:
,
.
1 to 0 —
Numbered keys are used to enter values into parameter screens, and
to choose numbered menu items.
A to F —
Used to enter values into hexadecimal or text fields. Some keys have
additional functions that are available on some screens of the
interface. (As described below.)
A—
Used to ‘Select All’ on the Database Copy screens.
C—
Some screens accept this as a Cancel/Clear command. The Database
Copy screens use this key with a number (e.g. ‘C4’) to indicate
copying up to instance # of the available entries.
E—
The E key on the keypad has an important secondary function. The
key, followed by E toggles the controller into and out of database
Edit mode. Pressing the
-E combination again saves any changed
values and returns the controller to read-only mode.
—
Anywhere in the ATC interface, the HME (Home) button returns the
user to the 1.1.1 Runtime Status screen. This screen can also be
accessed by choosing the first option (Runtime Status) on the
Controller Status menu. (
> 1 > 1 > 1)
13
—
—
Arrow Keys – When in Edit mode, the green arrow buttons are used
to navigate between parameter fields on database screens.
When in sections of the database with multiple screens, such as the
six screens of Preemption (
> 2 > 6), the Up and Down keys are
used to switch between screens. The
button moves you to the
screen closer to the beginning of the list (e.g. 2 -> 1, 6->5). This also
works in the Help screens.
If the
key is pressed first, the
ATC display.
button is used to lighten the
The Up and Down buttons are also used to switch between the
various Status screens. The Runtime status screen is at the top of this
list, and it follows the order down the Status menu.
—
The HLP key toggles the help information for the current screen ON
and OFF. When in Edit mode, it displays the help information for the
currently selected field.
Pressing any key other than
environment.
or
exits from the help
—
The Enter button is used in a variety of places in the interface to
proceed past warning or error messages. It is also used to select a file
or value in the interface, such as a test in the Diagnostics screens or
an input/output in the I/O Mapping interface.
—
The Menu button opens the Main Menu of the controller from any
displayed screen. Note that this doesn’t work when in the Diagnostics
menus or the Help screens. In those cases, you must first exit from
those environments to navigate to the Main Menu.
The
,
key sequence will open the Utilities menus.
—
The Previous button moves the interface one step up the menu tree.
For instance, pressing PRV on the Set Local Time screen (Screen
2.4.5) will move the interface up one level to the Time of Day Menu
(Screen 2.4).
—
When in sections of the database with multiple screens, the Up and
Down keys are used to switch between screens.
The
button moves you to the screen closer to the end of the list
(e.g. 1 -> 2, 5->6). This also works in the Help screens.
14
Controller Hardware
If the
key is pressed first, the
ATC display.
button is used to darken the
The Up and Down buttons are also used to switch between the
various Status screens. The Runtime status screen is at the top of this
list, and it follows the order down the Status menu.
—
The Next button is used to enter into the Diagnostics mode under the
System Maintenance menu. It is also used to cycle through any
preset, non-numeric values in the parameter programming screens.
—
—
Used to turn parameter settings on and off in the parameter screens of
the interface. Typically, a Yes is indicated in the interface by an ‘X’
next to a setting. The Yes and No keys are used whenever a
parameter value is binary in nature, which may appear as ‘yes’/’no’,
‘enable’/’disable’, or ‘on’/’off’ in the interface.
The Clear/Escape key is used to return a field to its default value
(usually all zeros for numerical values, or OFF for binary parameters.)
This button is also used to exit out of the Utilities menus and the Help
screens.
Comms and Utility Connectors
Just below the keypad on the front panel are four D-sub type serial ports and a USB
port. These ports have a variety of uses.
local file transfers
connection to a central system
connection to the ATCLink utility software
connection to the cabinet (for TS2 Type 1 operations)
connection to an external backup power supply monitoring circuit
connection to a logging conflict monitor or malfunction management unit
connection to upload software/firmware or a traffic database (via the USB port)
15
Figure 7 – Comms and Utility Ports
Details about each port, from left to right, are described below.
USB Port
An ATC-1000 includes a single USB port. It functions in much the same way as a USB
port on a PC. The port is designed to allow easy transfer of files using small portable
memory devices such as USB memory sticks. Only passive RAM devices will work in
this port. Other types of USB devices, such as external USB hard drives, mice,
keyboards, and cameras will not be recognized.
The USB port is hot-swappable. The ATC controller does not need to be shut down and
restarted to attach or remove a USB memory device; simply plug the device into the
USB port and the controller will automatically detect it. A detected USB device triggers
the USB Command menu.
USB device detected
1.USB->DATABASE
2.DATABASE->USB
3.LOG->USB
4.CMU_LOG->USB
– remove to exit
5.UPS_LOG->USB
6.DBG CORE->USB
7.DBG FLASH->USB
8.ICC EDIT DB
Figure 8 – USB Command menu
Press the number key corresponding to a command to make a selection. The
commands on this menu are described in “USB Operations” on page 331. To exit from
this menu, simply unplug the USB device from the port.
16
Controller Hardware
Port 1 - SDLC
Port 1 is an SDLC port (physically, it is an RS-485 port, now known as an EIA-485
differential serial communications interface.) Port 1 is always used in a TS2 Type 1
cabinet to communicate with Buss Interface Units (BIUs) and the cabinet MMU. TS2
Type 2 controllers may use Port 1 to connect to the MMU and/or a Detector BIU.
This 15 pin female port uses the SDLC (synchronous data link) communication protocol
with a bit rate of 153.6 Kbps, as required by the NEMA TS2-2003 Standard. This port’s
TX LED is on when transmitting data. The RX LED is on when receiving data.
The port’s high speed full duplex data channels utilize four twisted pairs: two transmit
and receive data pairs, and two transmit and receive clock pairs. The pin assignments
for Port 1 are detailed on page 352.
Port 4 - Local
The Local port, or Port 4, is a male 9-pin serial port often used to connect to Conflict
Monitor (CMU) or Malfunction Monitor (MMU) logging ports. This port is configured on
Screen 2.1.5.2. This port can also be used to directly attach a PC that is running
ATCLink or IQ Central, thus allowing software/firmware updates and database changes
on-site.
Just as with Port 1, Port 4’s TX LED is on when the port is transmitting data, and the RX
LED is on when receiving data. The pin assignments for Port 4 are detailed on page
354.
Port 5 – UPS/Spare
Port 5, or the ‘Spare’ port, is a 9 pin male RS-232 port used to connect to a cabinet UPS
system. It can also be used to directly attach a PC running ATCLink or IQ Central, thus
allowing software/firmware updates and database changes on-site. This port is
configured on Screen 2.1.5.2.
The Port 5 TX LED is on when the controller is transmitting data and the RX LED is on
when receiving data. The pin assignments for Port 5 are detailed on page 355.
Port 2 - Central
Port 2, a 25 pin female connector, is also known as the Central Port. Port 2 is often used
to connect to a central system like IQ Central, either by a direct serial connection, or by
a modem (e.g. dial-up, fiber optic, or radio.) Port 2 is configured on the Port 2-5
Parameters screen, or Screen 2.1.5.2.
Port 2’s TX LED is on when transmitting data. The RX LED is on when receiving data.
The pin assignments for Port 2 are detailed on page 353.
Ethernet Ports
The ATC-1000 has two RJ-45 Ethernet ports as a standard configuration. The ATC2000 includes the full complement of four Ethernet ports, as specified in the FHWA
Advanced Transportation Controller standard. The Ethernet ports use the standard
10/100Base-T network interface, and conform to IEEE 802.3 standards. The network
interface supports transmission at the full 100Mbps rate. Each ATC has a unique MAC
17
network address, displayed on the Revision Information screen. These ports support
TCP/IP, SNMP, or NTCIP networking communications protocols.
Unlike the other ports, the Ethernet ports have built in LEDs that indicate status in a
slightly different way. The yellow “LINK” LED means a device connected to the controller
has acknowledged that this port is on the network and ready to transmit and recieve
data. The green “ACT” LED shows transmission and reception of data.
Optional Expansion Slot Ports
Along the right edge of the unit, the ATC-1000 and 2000 Controllers have a slot
available behind a removable front panel. This slot can accommodate any of the comms
modules available for the Peek 3000E controllers, including the 3000E fiber optic
module and the FSK Modem. The connector in the slot is the 96 socket contact DIN
41612 as specified in the CalTrans TEES – 1999 to support a 2X wide board. The serial
ports that result from installing these cards can be configured in the software by setting
Port 3 parameters on Screen 2.1.5.2. The pin assignments for these cards are available
in the documentation provided with those optional add-on cards.
18
Controller Hardware
I/O Module Connectors
Note
This whole topic pertains to the ATC-1000 and ATC-2000 controllers only. The
ATC-3000 controller uses a dedicated backplane I/O.
In the space just below the main display, keypad, and comms connector panel is the
location of the ATC Input/Output (I/O) module. There are four I/O modules available:
TS2 Type I
TS2 Type 2
LMD 40
HMC-1000
The type of I/O module installed in the controller determines cabinet compatibility.
Figure 9 – Example I/O Modules
The ATC automatically detects the I/O type installed soon after powered up. A single
cable connects the I/O module to the Main board. Two cables connect it to the PSU. If a
D module is installed, either one or two connectors will be attached to the back of the I/O
module from that unit as well. (D modules are always connected to the rest of the ATC
via the I/O module.)
The pin assignments and voltage and current requirements of the various I/O module
connectors are defined in “Chapter 15 — I/O Module Connector Details”, starting on
page 359.
19
Heartbeat LED
The front panel also includes a “Heartbeat” LED, which flashes at a rate of four times per
second as long as the fault monitor (or ‘CVM’) output is being generated and the traffic
engine is running. If the ATC is powered on, but has a serious problem, the Heartbeat
LED will stay on without blinking.
Data Key Port
A Data Key port is part of the FHWA ATC standard and is known as a ‘keyceptical’. This
port is available as an option on all of the ATC controllers. The actual ‘key’ used in this
port is a non-volatile computer memory device used to store the ATC traffic database
and CMU or MMU programming card settings. It functions similar to a USB thumbdrive,
with one additional feature. If the data key contains CMU or MMU programming
information, the ATC and the CMU/MMU will communicate with one another to verify
that the phase compatibility on Screen 2.1.3.1 is valid and identical.
Figure 10 – Datakey type data receptacle
Compatible data keys are available from DataKey Electronics,
Inc. of Minneapolis, Minnesota.
(www.datakeyelectronics.com). The ATC controllers can accept SFK series SPI 5V
Flash & EEPROM type serial memory keys.
Power System
The ATC-1000 and ATC-2000 controllers are powered through the I/O Module. The
ATC-3000 is powered through the backplane. The exact port and pins used to provide
power to the controller depends on the I/O module used. It is typically the left most
connector.
There is no internal battery to maintain memory storage or the real time clock in the ATC
controllers. Whenever the unit is off, static memory (SRAM) and the real-time clock are
powered by two super-capacitors. These capacitors provide sufficient power to maintain
the SRAM contents and the function of the real time clock for at least seven days.
AC power goes to the Power Supply Unit, or PSU, which is located behind the front face
of the main controller module, along the left side of the enclosure. The six power LEDs
and two fuses on the front panel of the controller are actually part of the PSU.
Fuses
The controller is fitted with a pair of easily replaced fuses. These are located in the lower
left corner of the front panel.
The bottom fuse is a 1 Amp fuse that protects the internal circuitry of the controller from
excess current coming from AC power. The top fuse protects the controller from overcurrent situations occurring on the CVM/Fault Monitor output pin of the I/O module
connectors. In all I/O modules, this fuse is designed to blow if the 24VDC output
exceeds 1 Amp of current.
20
Basic Operation
BASIC OPERATION
Adjusting Screen Contrast
Follow these steps to adjust the contrast of the ATC controller’s front panel display:
1.
From any screen, press the blue function button (
the upper right corner of the display.
2.
Press either the
or
). An asterisk will appear in
key to open the Contrast Adjust screen.
CONTRAST ADJUST
◄ ▌▌▌▌▌▌▌▌▌▌
►
109
<+> <-> Adjusts <any other key> Exits
Figure 11 – Contrast Adjust screen
3.
Use the UP+ and DWN– buttons to change the brightness of the display. It can
be any value between 0 and 255, but typically a value between 80 and 150 is the
normal range for display contrast. (This normal range can shift with the ambient
temperature of the LCD screen.) Set the value for comfortable viewing.
4.
Press any other key on the keypad to exit from the Contrast Adjust screen.
21
Turning the Backlight On and Off
The backlight for the ATC’s display will automatically turn on and stay on for a preset
period of time whenever a key is pressed. The default value is 10 seconds.
The length of time the backlight stays on can be programmed from the Utilities menu. (
+ MNU > 5. Use the
and
keys to adjust the “B ACKLIGHT T IMOUT ”
value, the only value on this screen that can be modified by the operator.). The timeout
value is between 10 and 630 seconds (10 seconds to 10½ minutes).
Press
menu.
again to return to the main Utillities menu. Press
to exit from the Utilities
** Miscellaneous Status **
<B>Check Buzzer:
ESW1 Init Status:
EEPROM Init Status:
Backlight Mode:
Backlight Timeout:
Temp Sensor:
Contrast Value:
--GOOD
GOOD
ON
600 [SEC]
25C [77F]
109
<MENU> Return to Main
Figure 12 – Utilities > Miscellaneous status menu, showing Backlight Timeout
To manually force the backlight on or off, press
,
. This toggles the display
backlight on and off. If turned off, the backlight will not turn on when a key is pressed,
until you press
,
again to turn the backlight function back on. When the
backlight is toggled on, the light will turn on and stay on for the defined timeout period, or
until
22
,
is pressed again to turn the display off.
Basic Operation
Entering Edit Mode
All of ATC screens are displayed in a ‘read-only’ format when first shown. However, you
have the option to modify the settings stored in the controller database by entering Edit
mode. This is done by navigating to the screen where the desired
parameter is stored and then pressing the
followed by the
key.
An asterisk (‘*’) appears in the upper right corner of the screen after the
key is pressed, which is then replaced by an ‘E’ when Edit mode is
entered. Once in the Edit mode, one of the data fields will flash, indicating which field is
currently selected.
Note
Status screens do not have any editable fields. The only exception to this is the
Backlight Timeout value previously discussed.
Use the
keys to change which field is selected. The currently selected
field is indicated by alternating between a blinking value and underscores. Typing in a
number or other value will replace the value in the currently highlighted field. The
and
buttons are used to toggle binary values, such as ‘Phase Enabled’. For array
binary values, the
The
button will place an ‘X’ and the
button will remove it.
button is used to step through a series of values. All changed values will
continue to blink until saved by pressing the
from Edit mode.
,
key combination again to exit
Entering the Utilities Menus
The Utility menus are separate from the Main Menu system of the ATC. These menus
are directly linked to the hardware and are accessed in a different way. Open the Utilities
menus by pressing the Blue function button followed by the MNU button (
,
).
23
** ATC TS2 Utilities Main Menu **
<
<
<
<
<
<
<
1
2
3
4
5
6
7
>
>
>
>
>
>
>
Keypad Test
Display Test
Voltage Status
Operational Status
Miscellaneous Status
Revision Info
Engineering Utilities
<ESC> Quit
Figure 13 – Utilities Menu
Press a keypad number button to enter the desired Utility menu item. To exit out of a
Utilities submenu back to the top Utilities menu, use the
button. To exit out of the
main Utilities Menu back to the regular menu system, press the
indicated.
button, as
Viewing Help Screens
Interactive help screens are available for most of the parameter, menu, and status
screens of the controller. To open the help description for a given screen, navigate to
that screen in the menus, and then press the
more than one page. use the
screens.
and
button. Some Help screens have
buttons to scroll through multiple Help
To see the help information for a particular field on a database screen, switch into Edit
mode by pressing
,
, use the arrows to move to the desired field, and press the
HLP button to see the description for that particular parameter.
Press any key other than
24
or
to exit out of the Help screens.
GreenWave ATC Series Software
GREENWAVE ATC SERIES SOFTWARE
The software in the ATC Controllers is called GreenWave. Greenwave is a program
running on the ATC’s Linux operating system. It defines the menus and available
parameters displayed from the controller’s database. The software is the program that
applies the controller database values to the operation of the intersection.
The ATC also has ‘on-board’ firmware in the Main Board, the I/O Module, and the PSU.
The on-board firmware for the Main Board and I/O Module can be upgraded in the same
manner as the software. The firmware for the PSU, however, can only be upgraded
externally in a jig.
Because of its importance, and the fact that the ATC software and firmware can be
updated by customers, the following details on how to check the current
software/firmware revisions, and the instructions listed below on how to update both are
paramount.
Checking the Current Version of Firmware
The operating system and software that are currently loaded in the ATC controller are
displayed on the Revisions Information screen (Screen 1.5). To view this data, follow
these steps:
1.
Power up the unit
2.
Press the
3.
Select
for the Status menu.
4.
Select
to open the Revisions screen.
1.5
button to enter the menu system.
REVISION INFORMATION
MODEL
: Peek Model ATC
GREENWave: 03.008.1315
DB ver
: 6
BOOT LOADER VERSION:
U-Boot 1.1.4 (Apr 13 2010 - 12:18:49)
Linux 2.6.20.14 Version:
#23 PREEMPT Mon Oct 18 23:23:54 EDT 2010
IO Module : TS2 TYPE 2
IO D Module: LMD9200 CPC SUB 15IN
MAC ADDR : 1A-B6-1F-B2-3C-C6
Figure 14 – Revisions Screen
Make note of the third line of text on this screen, showing the GreenWave version
information. The version must match with compatible firmware loaded on the Main
board and the PSU. That firmware version information can be viewed on the previously
discussed Utilities Menu, by following these steps:
25
1.
Press
and then
2.
Press the
to open the Utilities menu.
button to select Revision Info.
** Revision Info **
MAIN: v1.0.11 01/26/11
TS2
PSU: v1.0.5
09/17/10
Type A
IO: v1.1.2
01/26/11
Type 2
** Firmware Loader Info **
MAIN: v1.0.1
04/06/10
Figure 15 – Firmware Revision Screen in the Utilities menus
Peek’s product release notes for each release of GreenWave software will always
include a matrix of compatible board firmware revisions.
Caution
Do not upgrade the GreenWave software without first upgrading to
compatible firmware in accordance with the GreenWave Release notes.
Certain upgrades will require a longer process using a .wfi file format
upgrade. The Release Notes will specifically identify this requirement.
Performing a software/firmware upgrade without first reading the entire
Release Notes document is not adviseable.
Updating GreenWave Using a USB Memory Device
Follow these steps to update the software in an ATC controller:
26
1.
For ATC software/firmware transport, the USB device must be formatted with the
proper folder structure and signature file so that the ATC unit recognizes it. If the
drive is not formatted, plug it into a Windows-based PC, locate the drive in
Windows Explorer, right-click on it, and choose ‘Format’. Note the name and
location of the USB device on your system for the next step.
2.
Open ATCLink on the Windows system where the USB drive is attached. Select
the U t i l s menu and choose Phase 2 > W r i t e U S B F i l e s / F o l d e r s , as
shown in Figure 16.
Figure 16 – Write USB Files/Folders in ATC Link
3.
Navigate to the drive letter where the USB drive is connected and click on S AVE .
A dialog box will open to acknowledge completion of the task creating the
necessary signature file and folders.
Figure 17 – ATCLink creates the folders and files on the USB drive
4.
Click OK.
5.
Open Windows Explorer and navigate to the USB drive. The required directory
structure is illustrated in Figure 18.
Figure 18 – Directory on the USB drive
The ‘Signature File’ that identifies the drive to the ATC controller is called
ASTC_DATA_DISK. The Peek Traffic Product Support team can also email this
folder and file structure.
6.
Store the ATC software update file(s) on the USB drive. Place the file(s) in the
\ATC_LINUX\USTC_firmware folder. These files, with the associated release
notes, are available from the Peek Traffic Product Support Team or authorized
Local Distributor. A typical software file is named ‘natc_v00#R###.wfi’ where the
#’s indicate the version and build of the software. The file for version 3.8, build
1184 of the software would be called ‘natc_v008R1184.wfi’. Firmware files for the
Main Board look like this: ATC_TS2_MAIN_LPC23xx_v10_11.fpu. Firmware files
for the I/O Board look like this: ATC_TS2_IO_LPC23xx_v1_1_2.fio.
7.
On the controller, select the System Maintenance area of the ATC menus and
choose the Diagnostics Mode. (Main Menu > 3. S YSTEM M AINTENANCE > 3.
E NTER D IAGNOSTICS M ODE )
27
Caution
8.
Press the
9.
Choose
The next step will put the ATC into Flash mode.
button to proceed into Diagnostics Mode.
to select Update Firmware.
10. The FWLoader utility will start. When the following screen is displayed, plug the
USB drive containing the new software/firmware into the ATC’s USB port. (The
Ethernet addresses that appear on this screen depend on current ATC
programming.)
ATC FW Loader v2.4
Waiting for USB
Listening on ETH
eth0: 119.2.59.12
eth1: 192.168.60.199
Figure 19 – ATC FW Loader screen
11. Software/firmware files that are stored on the USB drive are displayed on the
screen. Use the
and
file you wish to be loaded.
buttons to move the cursor (‘>’) to the left of the
Select FW File:
u-boot-20080806.btt
> natc_v008R1235.wfi
natc_v007R889.bin
ATC_TS2_MAIN_LPC23xx_v1_0_11.fpu
ATC_TS2_IO_LPC23xx-v1_1_2.fio
natc_v007R889.wfi
Figure 20 – Select a software or firmware file and press Enter key
12. When you have the correct file selected, press the
28
button to start the install.
13. The controller will report that it is “Updating the Traffic Application”. When
finished, a Firmware Update Complete message is displayed.
14. When the installation completes, remove the USB drive from the USB port. The
ATC must now be completely powered down and restarted.
15. A Firmware/Hardware sync screen will appear. As the screen states, press the
following buttons in the exact order to proceed:
,
,
,
,
. If
the upgrade was successful without major database changes, the controller will
start up and return to the Runtime Status screen. If major database changes were
introduced, the screen will state so and require the
reorganize the data. After pressing
Status screen.
button to be pressed to
, the ATC will return to the Runtime
16. After the status screen appears, check the applicable software/firmware version
by going to the two Revision screens (M a i n M e n u > 1 . S t a t u s > 5 .
R e vi s i o n for Software.
1.5
MODEL
: Peek Model ATC
DB ver
: 6
U-Boot 1.1.4 (Apr 13 2010 - 12:18:49)
#23 PREEMPT Mon Oct 18 23:23:54 EDT
2010
IO D Module: TRACONEX
Figure 21 – Verify the correct firmware version
And
,
to check the firmware version information.
29
** Revision Info **
MAIN: v1.0.11 01/26/11 TS2
PSU: v1.0.5 09/17/10 Type A
IO: v1.1.2 01/26/11 Type 2 -- TRCNX
** Firmware Loader Info **
MAIN: v1.0.1 04/06/10
Figure 22 – Utilities menu Revisions Screen for Firmware
Insure the Software and Firmware revisions loaded now appear on the appropriate
screens.
30
Chapter 2 — Quick Start: Getting an ATC Set
Up and Running
This chapter discusses how to get a new ATC controller operating and describes the
basics of installing the unit in an intersection cabinet. The following topics are discussed
in detail in this chapter:
•
Hardware setup checklist, on page 32.
•
Setting an IP address, on page 32.
•
Loading a default database, on page 34.
•
Field deployment, on page 35.
•
Programming a basic intersection, on page 36.
31
Chapter 2 — Quick Start: Getting an ATC Set Up and Running
OVERVIEW
When an ATC controller is shipped from the factory, it is pre-configured with software,
firmware, a MAC address, an IP address, and a cabinet address. These instructions
explain how to configure such a unit for use in a traffic cabinet.
HARDWARE SETUP CHECKLIST
To operate properly, an ATC must be installed in a traffic cabinet that matches the type
of hardware, software and firmware that is installed in the unit. Before installation, verify
the following hardware components:
Proper I/O module and D module (optional) to match your cabinet hardware (TS2
Type 1, TS2 Type 2, HMC-1000, or LMD 40)
The cabinet connector(s) must match the I/O module connector(s). In particular,
verify that the power supplied on the pins of the ‘A’ connector match the required
pin assignments of the installed I/O module.
If connecting to an NTCIP central system, use the correct communications
hardware. This can include serial, Ethernet, or FSK cabling to the cabinet, an
external modem, or a radio modem.
A properly formatted USB drive to transport controller software, firmware and/or
databases to and from the controller. If updates have occurred since the ATC was
shipped from the factory .
Cabling to connect to the logging port of a conflict monitor (CMU) or malfunction
management unit (MMU) Error! Reference source not found.Error! Reference
source not found.
Cabling for the data connection to an uninterruptable power supply (UPS) system
Data key for transferring controller databases and/or CMU compatibility matrices.
Serial or Ethernet cable to connect to a PC running an ATC application or utility
(such as ATC Link).
Properly jumpered programming card for the CMU or MMU. Error! Reference
source not found.Error! Reference source not found.Error! Reference source
not found.
CONFIGURING THE ETHERNET PORTS
This procedure is intended to guide the user through the process of setting the local
ATC controller IP address and Ethernet settings. The Local settings are used to connect
ATC Link to the controller over the controller’s “Local” Ethernet port.
32
1.
If not already on, power on the controller.
2.
Navigate to the IP/Cabinet Address Setup screen. ( > 2 > 1 > 5 > 3)
Configuring ATC Link and the SNMP Manager
2.1.5.3
IP/CAB ADDR SETUP
Cabinet Address: FFFF
IP Address SYSTEM: 128.002.060.198
IP Address LOCAL : 192.168.060.199
SubNetAddr SYSTEM: 255.240.000.000
SubNetAddr LOCAL : 255.240.000.000
Reboot required for following items:
Gateway
Gateway
SYSTEM: 128.002.002.002
LOCAL : 000.000.000.000
SNMP Port: 00000
Figure 23 – IP/Cabinet Address Setup screen
3.
Press the function key
4.
Press the
and then the E button (‘Edit’) to enter Edit mode.
button to go to the first octet of the IP Address LOCAL field. Use
the number keys on the controller to enter the new Local IP address. The
key can be used to move to the next octet.
5.
(Optional) Use the arrow keys to navigate to the SubNetAddr LOCAL field and
use the number keys to set the required Subnet Mask value for your network.
6.
(Optional) Use the arrow keys to navigate to the Gateway LOCAL field. Again,
use the number keys to set the Gateway address for your Ethernet network, if
one is required in order to reach the central system.
7.
Once you’ve set the LOCAL IP address and other Local network parameters,
press the
8.
-
combination to save the values and exit Edit mode.
While still on this screen, write down the current values set for the Local Ethernet
addressing of this controller. These will be required when configuring ATCLink.
This completes the configuration of the controller’s Local IP Ethernet network settings.
CONFIGURING ATC LINK AND THE SNMP MANAGER
The next step in getting the ATC controller running is to install ATC Link on a laptopt PC,
and to make sure that the PC has the SNMP Management service activated. (The
SNMP service is only required if you plan to connect to the controller via a serial cable.)
To accomplish these steps, you will need to have Administrative access to the computer,
and either the Windows installation CDs or the .cab files of the Windows installation.
The full instructions for installing and configuring ATC Link is available in the ATC Link
Operating Manual, (p/n 81-1366), which is available on the peektraffic.com website.
33
Note
ATC Link is not strictly required in order to set up and operate the ATC controllers.
(Unlike the ATC-1000, ATC-2000 and ATC-3000, the ATC CBD controllers are not
programmable from the front interface, so IQ Link is required for their setup.) In
contrast, the ATC-1000, 2000 and 3000 can be programmed entirely from their front
panel interface. However programming and maintaining a network of ATC controllers
can be done more easily and conveniently when used in conjunction with the ATC
Link and IQ Central software tools.
LOADING A DEFAULT DATABASE INTO THE CONTROLLER
The process to load a database into the ATC is very simple. The controller stores default
databases internally as a backup system. To load one of the available databases into
the controller’s active memory, follow these steps.
1.
Power up the controller.
2.
Navigate to the System Maintenance menu, and select Database Utilities
(
>
)
3.
Select 0 (zero) to remove all Flash data, or a value between 1 and 7 to load the
desired default database. Choosing 0.Remove ALL Flash Data will set all saved
parameter values to zero. The database will be completely empty. (Note that this
does not affect the stored default databases, just the active memory.) Values 1
through 7 will load a complete database from memory, preconfigured to provide
the described type of intersection function.
4.
At the completion of the loading process, the screen will demand that the
controller be restarted. This means that you must remove power until the screen
goes blank, at which point reapply power to restart the controller.
Note
34
>
Loading a default database will not change the stored values for either Cabinet
Address or Ethernet settings.
Field Deployment
FIELD DEPLOYMENT
Because of the large number of I/O options, comms options, and operating parameters
of the ATCs, the exact method to install the controller into a field cabinets is highly
variable. The basic processhas these recommended steps:
1.
Power the ATC in the Shop.
2.
Program the unit with intersection-specific database settings.
3.
Check the operating sequence on a Light Board.
4.
Save the programming by plugging in a USB drive. When a properly formatted
USB drive is inserted in the ATC’s USB port, the USB menu will appear. Choose
option 2. DATABASE->USB.
5.
Ensure that all circuit breakers in the cabinet power distribution panel are off.
Ensure that the input power is connected to the cabinet power panel and the
appropriate buss bars. The cabinet must be wired properly for the intersection.
6.
Ensure that all Signal light connections and detector input connections are
properly made in the cabinet, including any necessary pedestrian inputs.
7.
Place the controller on a shelf in the cabinet.
8.
Plug the cabinet connectors into the I/O module of the ATC. This may be from
one to six cables, depending on the type of I/O and D Modules utilized.
9.
If using a TS2 Type 1 I/O module, connect the SDLC communication cable from
the cabinet’s serial panel to the controller’s Port 1 connector. Ensure that the
connection clips on the communication cable properly latch onto the locking
blocks. If the MMU has not already been set up for this installation, program the
MMU and jumper the compatible phases on the MMU’s programming card.
Reinsert the programming card into the MMU.
10. Turn on all circuit breakers in the cabinet. For normal signal operation in a Peek
cabinet, check that the SIGNAL AUTO/FLASH switch of the cabinet is in the
AUTO position and that the SIGNAL ON/OFF switch is in the ON position.
11. Verify that the controller powers on and has all six front panel power LEDs
glowing green. Verify that the power up sequence clears successfully and the
ATC progresses to show the 1.1.1 Runtime Status screen. Verify that the
Heartbeat LED is flashing steadily at approximately 4 flashes per second.
12. Observe the operation of the intersection signals and detection inputs to verify
that the intersection is operating safely, as expected.
This completes the typical field deployment process.
35
PROGRAMMING A BASIC INTERSECTION
Because of the numerous operating modes and options in a Peek ATC controller,
programming can be a complex process.
Programming a Basic Phase-Based Intersection
These are the basic steps for setting up the parameters to run a NEMA intersection
using keypad programming.
Note
NTCIP Consistency Checks (See Annex B of the NTCIP 1202, v02.18 standard)
require parameter programming in the following order to avoid NTCIP fault
messages.
1.
Start with Phase Compatibility: (
>
2.
Define the Program Ring Sequence: (
3.
Set up the Signal Channels: (
4.
Enable the phases you wish to use: (
5.
Now the remaining menu options on the Configuration Menu can be programmed,
>
>
>
)
>
)
)
>
>
)
>
>
>
)
All seven items on the Time of Day Menu should be programmed next. The only
exception is for those who do not require automatic adjustments for Daylight
Saving Time: (
9.
>
)
Even if the intersection is not going to run in Coordination, the sequence number
programmed in step 2 above must now be entered in the Coord Pattern Table,
under Pattern 1: (
8.
>
>
>
>
)
Next, complete the menu items applicable to the intersection on the Controller
Phase Function list: (
7.
>
>
>
if applicable to the intersection: (
6.
>
>
>
)
Set up vehicle and pedestrian detectors: (
>
>
)
These are the basic settings NEMA intersections. There are more featured capabilities
that can be configured using the rest of the ATC programming screens. Remember to
always power cycle the ATC after the programming changes have been completed.
36
Programming a Basic Intersection
Programming a Basic Interval-Based Intersection
Programming an interval-based intersection is much easier. Use of the following
programming order is recommended to avoid NTCIP Consistancy Check Fault
messages.
1.
Start with Signal Plans: (
2.
Program the Timing Plans: (
>
3.
Preemption: (
>
>
>
>
>
>
>
>
)
>
)
) and Interval-Skipping: (
>
>
) are intersection-dependent and optional.
These are the basic settings for an interval-based intersection. There are more featured
capabilities that can be configured within the four sections of the ATC interface-based
programming screens. Remember to always power cycle the ATC after the
programming changes have been completed.
37
38
Chapter 3 — Introduction to the Interface
This chapter describes the keypad and front panel display interfaces of the Peek ATC controllers.
The following topics are discussed:
•
An overview of the menu and status screen environment, on page 40.
•
Navigating in the Menus, on page 40.
•
Firmware flowchart, on page 42.
39
OVERVIEW
When an ATC controller running the GreenWave firmware is powered on, it will go
through a startup sequence. After it displays its splash screen, showing the Peek Traffic
logo and some information about the firmware, the display will show the standard
Controller Runtime Status screen. From there, the controller’s menu system can be
accessed using the Main Menu button (
).
Help information is available throughout the interface by pressing the
key.
Status screens cannot be edited, but certain inputs can be applied from some Status
screens. These are discussed in “Chapter 4 — Status Displays”, starting on page 45.
For more details about how to navigate around in the menu system, see the next topic.
Navigating in the Environment
To navigate around in an ATC controller’s menu system requires an understanding of a few
simple rules on how the menus and status screens work. These are the rules:
To go from the Controller Status screen to the Main Menu, just press the
To go to the Main Menu from anywhere in the menu system, press the
To go from any menu back to the main status screen, press the
button.
button.
key.
To select an item on a menu, press the keypad number corresponding to that item.
To move upward in the menus structure, press the
button.
The entire interface toggles between Read-Only and Edit modes using the
-
key
combination. (So if a user enters Edit mode on one screen, returns to the menus, and
goes into another parameter screen, the interface will still be in Edit mode.) Just be aware
that changes to the values are not stored to the permanent database until the interface
returns to Read-Only mode.
When working in parameter screens that have multiple pages, use the
buttons to switch between pages. Use the
back to the menus. The
and
button to exit from parameter screens
key will also return you to the menus, but it will take you
straight to the Main Menu. Some parameter screens have two dimensions of screens (for
example, the TSP Run Configuration Screens: Configurations 1 through 8, and Runs 1
through 8.) The first dimension is selected using Page Up and Page Down, the second
dimension is selected using the numbered keys on the keypad.
Help Topics – The
key displays the help topic for whatever menu, status screen or
data screen that is currently visible. Topics that have multiple pages of information can be
40
Overview
navigated using the
and
keys. To view the help topic about a single parameter,
go to the screen, switch to Edit mode (
and then press the
-
), navigate to the parameter in question,
key. Pressing any key other than
or
will exit Help.
41
FIRMWARE FLOW CHART
The following chart provides an overview of the basic theory on how the ATC selects
which traffic pattern to use in the intersection.
Figure 24 – Firmware flowchart
After going though startup self-tests and any startup flash routine, the ATC enters a loop
looking for an external (SYS) or override (CRD) pattern. If no SYS or CRD pattern is
42
Flow Chart of the Entire Menu System
present, it looks for a valid TOD pattern for the current date and time. If no valid TOD
pattern is programmed, the ATC reverts to the backup Free pattern. If there is no valid
Free pattern defined, the controller will run the MUTCD soft flash pattern. If absent even
that last fallback position, the ATC will force the cabinet to a hard flash mode by
dropping the CVM or Fault Monitor signal to the MMU.
FLOW CHART OF THE ENTIRE MENU SYSTEM
The diagram on the next page (Figure 25) shows the locations of all of the screens in the
Main Menu system, including menus, status screens, and parameter screens.
Commands that open one or more parameter screens indicate the number of parameter
screens next to the box. Commands that perform a function as soon as you press the
button are shown in blue. Commands in light gray are not yet implemented.
This menu diagram is also displayed on the inside of the back cover of this manual.
43
GreenWave v3.8 Menu System
(same screen)
1.1 Status - Controller Status
Chapter“Home”
3 — Introduction
to the Interface
1.0 Status Menu
“Menu”
Main Menu
1. Status
2. Programming
3. System Maintenance
4. Logs
1.1 Controller
1.2 Inputs/Outputs
1.3 Alarms
1.4 MMU
1.5 Revisions
1.1 Controller Status Menu
1.2 I/O Status Menu
2 screens
1.2.1 Inputs Status
1.2.2 Outputs Status
1.2.3 SDLC & FIO Status
2 screens
1.1.1 Runtime Status
1.1.2 Coordination Status
1.1.3 Time of Day Status
1.1.4 Preemption Status
1.1.5 Detectors Status
1.1.6 TSP Status
1.1.7 Overlaps Status
1.1.8 Sequencing Status
1.1.9 Texas Diamond Status
1.1.5 Detector Status Menu
1.1.5.1 Vehicle Detector Status
2 screens
1.1.5.2 Pedestrian Detector Status
1.3 Alarm Status Menu
Figure 25 – Top-down view of the ATC-1000
Menu System
1.3.1 Unit Alarm Status 1&2
1.3.2 Short Alarm Status
2.0 Programming Menu
1. Unit Configuration
2. Controller
3. Coordination
4. Time of Day
5. Detectors
6. Preemption
7. Interval
8. Transit Signal Priority
2.1 Configuration Menu
2.1.1 Startup
2.1.2 Program Flash
2.1.3 Phase Compatibility
2.1.4 Channels
2.1.5 Comms & I/O Setup
2.1.6 Ring Sequencing
2.1.7 USTC Miscellaneous
2.1.8. Abs Zero
2.1.9. Logic Processing
2.1.0 Exclusive Pedestrian
2 screens
2 screens
16 screens
2 screens
2 screens
2.2 Controller Menu
2.2.1 Phase Enables
2.2.2 Green Timing
2.2.3 Clearance Timing
2.2.4 Pedestrian Timing
2.2.5 Added Initial Timing
2.2.6 Gap Reduction Timing
2.2.7 Dynamic Max Timing
2.2.8 Phase Options
2.2.9 Recalls
2.2.0 Overlaps
2 screens
2 screens
2 screens
2 screens
2 screens
2 screens
2 screens
2 screens
2.1.5.1
2.1.5.2
2.1.5.3
2.1.5.4
2.1.5.5
2.1.5.6
2.1.5.7
Port 1
Port 2-5
IP/Cabinet Address
I/O Mapping
DHCP Setup
Process Control
Int’l Load Switch Menu
2.1.9 Logic Processing Menu
8 screens
2.2.0 Overlaps Menu
2.2.0.1 Vehicle Overlap Variables
2.2.0.2 Pedestrian Overlaps
2.3 Coordination Menu
32 screens
16 screens
2.3.1 Coordination Variables
2.3.2 Pattern Table
48 screens
2.3.3 Split Table
16 screens
2.3.4 Offset Correction Ext/Reduce 16 screens
2.4 Time of Day Menu
2.4.1 Actions
2.4.2 Day Plans
2.4.3 Schedules
2.4.4 Override Commands
2.4.5 Set Local Time
2.4.6 Advanced Time Setup
2.4.7 Daylight Saving Setup
32 screens
32 screens
10 screens
2.4.1 Time of Day Actions
2.4.1.1 Plans
2.4.1.2 Auxiliary & Special Fctns
6 screens
6 screens
2.5 Detectors Menu
2.5.1 Vehicle Detectors Options
2.5.2 Vehicle Detectors Timing
2.5.3 Detectors Call Phase
2.5.4 Detectors Switch Phase
2.5.5 Pedestrian Detectors
2.5.6 Enhanced Vehicle Detectors
2.5.5 Enhanced Ped Detectors
4 screens
8 screens
2 screens
2 screens
64 screens
8 screens
2.6 Preemption Menu
2.6.1 Enables/Inputs
2.6.2 Entry
2.6.3 Track Clearance
2.6.4 Dwell / Cyclic
2.6.5 Exit
6 screens
6 screens
6 screens
6 screens
6 screens
2.7.1 Timing Plans
2.7.2 Signal Plans
2.7.3 Preemption
2.7.4 Interval Skipping
16 screens
32 screens
2.7.2 Interval Menu
2 screens
2.8 Transit Priority Menu
2.8.1 Unit Parameters
2.8.2 Run Parameters
2.8.3 Action Plans
2.8.4 Run Configuration
2.8.5 Queue Jumping
2.8.6 Split Table
2.7.1 Timing Plan Menu
2.7.1.1 Cycle/Offset/Split Data
2.7.1.2 Timing Plan Setup
2.7 Interval Menu
2×4 matrix of screens
2.7.2.1 Interval Modifiers
2.7.2.2 Channel-Interval Mapping 2×4 matrix of screens
2.7.2.3 Output-Interval Mapping 11×4 matrix of screens
2.7.3.2 Track Intv’l Data Menu
2.7.3 Preempt Int’vls
48 screens
8×8 matrix
6 screens
16 screens
2.7.3.2.1 Track Intv’l Time
2.7.3.2.2 Track Channels-to-Intv’ls
2.7.3.2.3 Track Outputs-to-Intv’ls
2.7.3.1 Modifiers
6 screens
2.7.3.2 Track Interval Data
2.7.3.3 Dwell Interval Data
2.7.3.4 Exit Interval Data
2.7.3.3 Dwell Intv’l Data Menu
2.7.3.3.1 Dwell Intv’l Time
2.7.3.3.2 Dwell Channels-to-Intv’ls
2.7.3.3.3 Dwell Outputs-to-Intv’ls
3.0 System Maintenance
3.1.0 Database Utilities Menu
3.1 Database Utilities
3.2 Copy Database Data
3.3 Enter Diagnostics Mode
3.1.0
3.1.1
3.1.2
3.1.3
3.1.4
3.1.5
3.1.6
3.1.7
Remove ALL Flash Data
8Ph Sequential
4Ph Dual Rng Main/4Ph Sequential Side
8Ph Quad-Left Dual Ring
4Ph Sequential Main/4Ph Dual Rng Side
Exclusive Pedestrian
Coordinated 8Ph Quad-Left
8Ph Quad-Left Preempt (Opticom Style)
3.2.1 Actuated Data
3.2.2 Interval Data
“Previous”
4.0 Log Menu
4.1 Controller Message Log
4.2 NTCIP Event Log
4.3 Advanced Controller Log
44
Diagnostics Mode Warning Screen
9 screens
3 screens
“Next”
6 screens
2.7.3.4 Exit Intv’l Data Menu
2.7.3.4.1 Exit Intv’l Time
2.7.3.4.2 Exit Channels-to-Intv’ls
2.7.3.4.3 Exit Outputs-to-Intv’ls
Return from these screens requires a controller restart
Diagnostics Menu
3.2.0 Copy Data Menu
6 screens
1. Inputs/Outputs Test
2. Comms
3. Memory Test (RAM, SRAM, Flash)
4. Time Test (RTC)
5. USB (Write/Read)
6. SD Card Test
7. Update Firmware
6 tests
7 tests
5 tests
ATC FW Loader v2.4
4.3.1 Setup Logging Options
4.3.2 View Log
6 screens
Chapter 4 — Status Displays
This chapter describes the Status Displays of the ATC controllers. The following topics are
discussed in detail in this chapter:
•
Overview of the Status menus, on page 46.
•
The Controller Runtime Status screen, on page 47.
•
The Coordination Status screen, on page 53.
•
The Time of Day Status screen, on page 57.
•
The Preemption Status screen, on page 58.
•
The Detectors Status screen, on page 60.
•
The Transit Signal Priority Status screens, on page 62.
•
The Overlaps Status screen, on page 66.
•
The Sequencing Status screen, on page 68.
•
The Texas Diamond Status screen, on page 68.
•
The Inputs Status screen, on page 71.
•
The Outputs Status screen, on page 73.
•
The SDLC & FIO Status screen, on page 74.
•
The Unit Alarms Status screens, on page 75.
•
The Short Alarm Status screen, on page 76.
•
The MMU Status screen, on page 77.
•
The Revisions screen, on page 78.
45
OVERVIEW OF THE STATUS SCREENS
The ATC controllers have five categories of status screens with a total of 18 Status
displays, some with multiple screens.) Each status display shows a set of critical data
pertaining to a single area of controller operation, such as coodinated operation or
preemption.
Status Menu
The Status Menu hosts all of the status screens of the ATC controller, in a set of five
>
functional groupings. (
1
)
STATUS MENU
1. CONTROLLER
2. INPUTS/OUTPUTS
3. ALARMS
4. MMU
5. REVISIONS
Figure 26 – Status categories available in GreenWave v3.8
Navigating the Status Screens
After access into any of the individual Status screens, these are the navigation options:
– Go to the next higher status screen. Think of the status screens as a vertical stack of
displays, with the 1.1.1 Controller Runtime Status screen at the top of the stack, and the
1.5 Revision Information screen at the bottom.
– Go to the next lower status screen.
– Return to the Main Menu
– Return to the top of the Status display stack, to the 1.1.1 Controller Runtime Status
screen
– Return to the previous screen that was just visited. Not applicable to the 1.1.1
Controller Runtime Status screen, as it is the top of the status screen stack.
– All of the status screens include a set of help screens, describing the labels used and
the information displayed on that status screen.
Pressing any button other than
you started.
46
or
will return you to the status screen where
Controller Status Menu
CONTROLLER STATUS MENU
Option 1 from the Status menu will take you into the Controller Status menu, which lists
all of the available status screens pertaining to general traffic engine operation.
1.1
1.
2.
3.
4.
5.
6.
7.
8.
9.
CONTROLLER MENU
RUNTIME STATUS
COORDINATION
TIME OF DAY
PREEMPTION
DETECTORS
T.S.P
OVERLAPS
SEQUENCING
TEXAS DIAMOND
Figure 27 – Controller Status menu
Select any of the options on this menu to see the status screen related to that data.
Once in the status screens, you can return here using the
navigate up and down on the status screen list using the
button, or you can
and
buttons.
Runtime Status Screen
The Controller Runtime Status Screen is the default display after ATC power up. It can
be reached by pressing:
>
>
>
or by pressing the
button.
There are two versions of the Runtime Status screen, a phase version and an interval
version, depending on which type of pattern is currently running in the controller. Figure
29 on page 50 displays a sample of the interval-based version.
Phase Version of the Runtime Status Screen
1.1.1 TS21 Mon 04-Apr-2011. P1:OK
RING STATUS
08:53:22
CAB:00F7
R1 02 EXT 00.0 M1 005
DW
PRE INP
R2 06 GRN REST
PRE KBD
DW
R3
RED REST
DW
R4
RED REST
DW
CALL STATUS 1111111
1234567890123456 CRD CMD:
VEH
C
SYS CMD:
PED C
TOD CMD:
PHS
0
0
1f
Figure 28 – Sample Controller Runtime Status screen – Phase version
47
The top left of the Runtime Status screen is the number ‘1.1.1’. All of the ATC
screens show the screen number derived from the button presses that are needed to
reach it, starting from the Main Menu. The next entry to the right is I/O type, shown
below as ‘TS21’ which represents TS2 Type 1. The other possible I/O types are: TS22,
HMC, LMD4, INT and OTH. The next entry to right is a three letter abbreviation for the
Day of the Week. The next entry to the right is the current date expressed in Day of the
Month, Month, and Year. A period ‘.’ , immediately after the year indicates that DST
(Daylight Savings Time) is enabled and actively adjusting the time. The last entry on
the right is the Port 1 status indicator ‘P1:OK’ means good SDLC
communications. ‘P1:Err’ indicates a problem. Check cable connections and Port
1 programming on Screen 2.1.5.1. P1:OK also indicates TS2/Type 2 communications
status. It displays the communications status between the front panel/engine board
module and whatever I/O board is installed. See page 74, ‘SDLC & FIO Status Screens’
for more details.
The second line from the top is the static text ‘RING STATUS’ and the clock in
HH:MM:SS (24 hour time) format: ‘16:51:20’. The four character string at the end of
line 2 (‘00F7’ in this case) is the cabinet address for this controller, in hexidecimal
format. On the right side of the screen the two PRE lines indicate active in[puts for the
six NEMA preemption runs.
The center left of the screen shows the timing status of all four rings, next to the labels
R 1 through R 4 . Vehicle and pedestrian timers with interval terminations are shown.
On the right side of the screen, to the right of the R1 and R2 indicators, the two PRE
lines indicate the current activity on the six available Preemption run inputs. Active run
numbers will appear to the right of these labels. PRE KBD indicates that a keypad call
has been placed for that preemption from the front panel of this controller. A manual
preemption call can be entered from the Preemption Status screen (
>
>
>
) That is also the only place where this kind of preemption call can be cleared, by
pressing the same keypad number again.
Call Status for all 16 vehicle (V E H ) and pedestrian (P E D ) phases appear in the bottom
left corner of the display. Single character codes indicate the type or status of the call on
that phase using this key:
Table 5 – Vehicle Call codes on the Runtime Status Screen
Code
48
Description
K
Call generated by keypad input on controller
V
Call from vehicle detector
R
Max Recall
r
Min Recall
S
Soft Recall
L
Locked Call
Table 6 – Pedestrian Call codes on the Runtime Status Screen
Code
Description
O
Omit call
K
Call generated by keypad input on this controller
P
Call generated by a Ped detector input
L
Locked Call
R
Ped Recall
Table 7 – PHS codes on the Runtime Status Screeen
Code
Description
O
Omit
N
Next Decision
C
CNA (Call to non-actuated)
c
Call
The three CMD lines at the bottom of the screen describe the commanded pattern or
patterns currently active within the controller. See “CMD Pattern Indicators” on page 51
for more details.
49
Interval Version of the Runtime Status Screen
If you are running a pretimed pattern (any pattern between 101 and 228) then the
controller status screen shows a different set of information.
1.1.1 TS22
P1:OK
PRETIMED PLAN
CALL STATUS 1111111
TP:01 SP:01 OFS:016
1234567890123456
M000
PL002 025.0
DET
INT:06 00.0 03.2
VEH
PED
CHN
DATE
Tue 27-Apr-2010.
TIME
16:11:21
CRD CMD:101t
SYS CMD: 0 ACTIVE 1 2 3 4 5 6
TOD CMD : 0 PREEMPT
FFFF
Figure 29 – Runtime Status screen – Interval version
The status screen is divided into sections with different functions,
as shown in Figure 30.
Plan and interval timing information:
TP = Timing plan, SP = Signal plan, OFS = Offset time
M = Master time, L = Local time. The difference between M & L = the offset time.
A ‘P’ will occasionally appear to the left of the L, indicating the time sync pulse. The time in the
bottom right corner (“025.0” in this example) is the accumulated split time for the cycle.
Interval #, Minimum time
counter,
interval counter
Signal Plan
modifiers
Current pattern as
commanded by
coordination (CRD), System
command (SYS), or Time-ofDay schedule (TOD)
1.1 TS22
P1:OK
PRETIMED PLAN OFLNE CALL STATUS 1111111
TP:01 SP:01 OFS:016
1234567890123456
M000 PL002 025.0
DET
INT:06 02.6
07.1
VEH X
PED
X
SEMI-ACTUATED
SKIPOK
CHN
DATE
Tue 27-Apr-2010.
TIME
16:11:21
CRD CMD:101t
SYS CMD: 0 ACTIVE 1 2 3 4 5 6
TOD CMD : 0 PREEMPT
Call status for vehicular and
pedestrian detectors
Signal outputs
Controller’s current
internal date & time
FFFF
Cabinet address
Preemption call status
Figure 30 – Sample Controller Status screen – Pretimed Pattern – Details
As on the phase-based Runtime status screen, the three lines of CMD information at the
bottom of the interval-based Runtime status screen show which commanded pattern or
patterns are active within the controller, as detailed in the next topic.
50
CMD Pattern Indicators
The commanded patterns on the lower right portion of the Runtime Status screen are
displayed like this:
CRD CMD: 254 (Coord Operational Mode 0-255; See Screen 2.3.1 on p.190)
SYS CMD:
6 (System Pattern Control 0-255; See Screen 2.3.1 on p.190)
TOD CMD: 11 (TOD Action Pattern 0-255; See Screen 2.4.1.1 on p.156)
NTCIP supports the calling of individual intersection patterns, of which there 255 preprogrammed patterns available. Each NTCIP pattern consists of a cycle length (30-255
sec), an offset (0-254 sec), a split table number (1-16), and a sequence number (1-16).
The NTCIP pattern selection process uses a three-layered hierarchy. The bottom layer
(in terms of priority) is the Time of Day (TOD) pattern. A TOD schedule calls a Day Plan.
A TOD Day Plan calls ‘Action’ items at HH:MM change points throughout the day. Each
Action item points to a pattern, numbered from 1-255. This pattern selection method will
be the most common process for ATCs that are not connected to an NTCIP Central
System.
The second layer of the pattern selection hierarchy occurs when the TOD CMD pattern
is overridden by a System pattern control (SYS CMD). A SYS CMD can call any of the
255 available NTCIP patterns. When a system pattern control object is received from the
Central System, it consists of a pattern number and a SET command. System pattern
commands operate in conjuction with the system backup timer, which is set using the
Back-up Time parameter on Screen 2.1.1. Whenever a system SET command is
received, the ATC starts counting down using this Backup Time value. The backup time
can be any value between 0 and 65,535 seconds, or slightly more than 18 hours. The
controller will continue to run the commanded System pattern until the backup timer
counts down to zero (0), unless another SET command is received in the interim. When
a new Set command is recieved, the backup timer is reset and the countdown starts
again. This is a failsafe mechanism to protect against communications failures between
the central system and the controller. If the timer does reach zero, the ATC will
automatically drop back to the pattern defined in its TOD schedule.
And the third level of the pattern selection hierarchy is the coodinated operational mode
pattern. AT any time, any active TOD or SYS pattern can be overridden by a Coord
Operational Mode (CRD CMD) pattern. A single CRD pattern is defined for each
controller as defined by the OPERATIONAL MODE parameter on Screen 2.3.1. It’s
easiest to think of CRD CMD as a manual pattern override.
On the Runtime Status screen, the displayed CRD CMD, SYS CMD, and TOD CMD
pattern numbers may be followed by a lower-case letter code, as defined in Table 8.
Table 8 – Pattern command codes on the Runtime status screen
Code
Description
f
Commanded to run Free; Coordination has an error causing it to run
FREE, or is just starting in a new Pattern
t
Coordination is in transition between Patterns, or offset seeking
s
Coordination is ‘in synchronization’, or running correctly
n
Coordination is still in its first coordinated cycle
51
Placing Manual Calls from the Runtime Status Screen
Beginning with GREENWave version 3.7, manual calls can be placed on both vehicular
and pedestrian phases using the keypad while viewing the phase-based version of the
Runtime Status screen (also known as the ‘Ring Status’ screen.) These commands do
not work from the interval-based version of this screen (the ‘Pretimed Plan’ status
screen), nor do they function from the other status screens.
To place vehicular calls on phases 1 through 8, press this sequence of keys:
,
,
..
Example: Or, in other words, to place a call on vehicular phase 1, press these three
keys in sequence:
,
,
.
To place a call on vehicular phase 7, press
below work in a similar manner.
,
,
. The commands shown
To place vehicular calls on phases 9 through 16, press this sequence of keys:
,
,
..
To place pedestrian calls on phases 1 through 8, press this sequence of keys:
,
,
..
To place pedestrian calls on phases 9 through 16, press this sequence of keys:
,
,
..
Calls placed in this way are indicated on the Ring Status screen in the bottom left corner
of the screen, in the Call Status array. Calls placed this way are indicated by a ‘K’ to
indicate that the call was placed from the keypad.
Important
Calls placed in this way will not clear on their own. You must press the
keypad sequence again to clear each manual call.
The Inputs status screen will show that a call exists on these phases and ped phases,
however it will not indicate any difference between those that are real field-based calls
and those generated from the keypad. Both are indicated by a simple ‘X’ in the VEH C
or PED C row under the phase in question.
52
Coordination Status Screen
The Coordination status screen shows the states of all of the phases, permissives, and
holds and force-offs, as well as global coordination parameters such as the local cycle
time, the offset from the coordination signal, the current pattern being run, and the
coordination status.
M AIN M ENU > 1.S TATUS > 1.C ONTROLLER > 2.C OORDINATION
1.1.2 COORDINATION STATUS
PG1OF1
Local : 66s Master: 66s Ptn:001 Spl:01
Offset: 0s Status:In sync
Phase
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
Color :r P r r r P r r
Perm
: C
C
Hold-FO: H
H
Phase :
1
2
3
4
5
6
7
8
Patn s: 20 30 20 30 20 30 20 30
Cmnd s: 200 300 200 300 200 300 200 300
Delta :R
0
0
0
0 Cyc
0
Sum :R
0
0
0
0 Cyc
0
ExtPt :
-1
-1
-1
-1
TSP Phases: 0 0 0 0 | TSP Actn Pln: 0
Run
:1 2 3 4 5 6 7 8 | Sequence Num: 1
Status:
| CIC:Idle
Figure 31 – Sample Coordination Status Screen
Local – Local Cycle time (s=sec). Up to three digits to the right of Local: is the Local
Cycle time in seconds.
Master – Master Cycle time (s=sec). If Master and Local times count up to the currently
commanded cycle length end, reset to zero and start counting again, the ATC
is in Coordination.
Ptn – The currently commanded pattern being run.
Spl – The current split plan being run.
Offset – The currently selected Offset being run. A zero (000) Offset usually indicates
the first intersection on the coordinated corridor.
Status – The ‘Status’ label in the top middle of the screen shows the current status of
phase based operation from a coordination perspective. This field can display
any of these values:
Free – No coordination, or Interval Pattern
Transfer – Transistioning into Coord -- Waiting for Green termination
1 Cycle – Less than 1 complete cycle since the ATC got in sync
In sync – In sync for more than 1 cycle
Seeking Fast X -- X is the number of cycles remaining until synched.
Seeking Slow X -- X is the number of cycles remaining until synched.
Seeking Dwell --Not in sync but attempting to achieve sync by dwelling at LO.
Fault – A phase with a call didn’t serve for two cycles
Retry – Returning to coordination after a “Fault”
Bad Plan – Invalid coordination pattern data detected. Additional information
about the possible messages that may appear is shown on page 55.
Failure – Coordination has failed due to two consecutive ‘Faults’
TSP Active – Cycling to selected TSP phases for green reduction and/or green
Extension and possibly other TSP modifications
TSP +Recovery -- extending splits to sync
TSP –Recovery -- reducing splits to sync
53
TSP Balance – Correcting the offset error resulting from a ‘TSP Active’ event
by extending non-TSP phases and reducing TSP phases.
TSP Pending Idle – TSP has completed and the ATC is now awaiting the next
Local Zero to return to ‘In sync’ operation.
Color – Current color shown by the phase: G=Green/Don’t Walk, W=Green/Walk,
Y=Yellow/Amber, r=Red/Ph Off, R=Red clearance, P=Flashing Don’t Walk
(Ped Clr).
Perm – Permissive status by phase: V=Vehicle permitted/ped not permitted,
C=Coordinated phase, B=Both vehicle and peds permitted.
Hold-FO – Shows whether a Hold or a Force-Off are currently active for this phase
(H=Hold, F=Force-Off)
Patn s – Shows the split times, in seconds, for the current pattern
Cmnd s – Shows the split times, in tenths of seconds, for a CIC or TSP pattern
Delta – The split deltas (time differences, in seconds) for Rings 1 through 4, projected
for the current cycle, after the most recent split adjustment caused by TSP.
Sum – These are the remaining delta times for Rings 1 through 4 and the current cycle.
At the local Zero, the Deltas are reset.
ExtPt – Local Cycle count in seconds, where TSP extensions start by Ring. ‘-1’ indicates
no extention points are yet identified.
TSP Phases – Phases numbers receiving TSP activity
Run Status – Enabled TSP Run Status, using the following letter codes:
R
Request
A
Active Extension of TSP Phase Green
T
Truncate
F
Failed Detector inhibiting Run
S
Success, call dropped during Green Extention
M
Removed, call dropped before Green Extension
D
Delay of Input Timing
I
Invalid Run, with Call
E
Extension of Input Timing
C
Clearance Failure, TSP Phase Forced-Off
r
Re-service, inhibiting run
O
Override, Run inhibited by higher priority
TSP Actn Pln – Current TSP Action (0-48), see Screen 2.8.3.
Sequence Num – Current Sequence Number called by the Pattern (Ptn) on Line 2 that
is active in the current TOD Plan.
CIC – Critical Intersection Control operational status of: Idle = ATC is running with no
CIC cycle, offets, splits (C/O/S) and no CIC Set command from the Central
System; Pending = CIC C/O/S and Set command accepted in same Pattern
Number currently running, waiting for top of cycle; Success = ATC is currently
running CIC C/O/S and has no valid exit commands; Error = ATC has rejected
CIC C/O/S because they violate one or more Coordination Consistency
54
Run Status – Shows the status of the TSP runs, if any are enabled.
Uses the following letter codes:
R
A
T
F
S
M
D
I
E
C
r
O
Request
Active Split Modification
Truncate
Failed
Success
Removed
Delay
Invalid Run
Extend
Clearance Failure
Reservice
Override
Ext Pts – Local Cycle count in seconds, where TSP extensions start by Ring.
A value of ‘-1’ indicates no extension points have been identified yet.
Coordination Check Faults (i.e. the ‘Bad Plan’ message)
If a Bad Plan message appears on the Coordination Status screen, next to the Status
field on line three, then the controller’s coordination testing algorithm has detected a
problem with the phase parameters. Such a problem is specifically related to
coordinated operation. The ATC’s Coord Plan Check evaluates the currently defined
coordination values for eleven possible faults.
Table 9 – Coordination Check Faults
Fault
Description
Invalid Cycle Time
The cycle length must be zero or greater than or equal to 30 seconds.
No Coord Phase in an
Eligible Ring
Each utilized ring must have one coordinated phase assigned.
Diamond Sequence Ring
Sum greater than Cycle
Time
The sum of the rings in a Texas Diamond sequence must equal the
cycle length.
Diamond Sequence Ring
Sum less than Cycle Time
The sum of the rings in a Texas Diamond sequence must equal the
cycle length.
Barrier Sum greater than
Cycle Length
Either the sum of barrier split times or the critical path through the
sequence exceeds the cycle length.
Barrier Ring Split Sums not
equal Sums
The sum of the splits in each barrier must be equal.
Initial plus Clearance
greater than Split
Minimum green time plus clearance must be equal to or less than the
split time.
Ped Time plus Clearance is
greater than Split
Walk plus pedestrian clearance plus clearance must be equal to or less
than the split time. Again, clearance is defined as the larger of the
trailing overlap trailing yellow plus trailing red or phase yellow plus allred.
Offset Time greater than
Cycle Time
Offset time must be equal to or less than cycle length.
More than 1 coord phase in
ring
Coordinated phases must be mutually compatible, per Screen 2.1.3.1/2.
(Refer to “Phase Compatibility Screens” on page 85.)
Min Barrier sum greater
than cycle time
The Sum of all Min Split Times within each Barrier must be equal to or
less than the Cycle Length along the critical path through the Sequence.
Minimum Split Time is the Split’s Minimum Green Time plus Clearance.
55
If such a ‘Bad Plan’ message appears on the Coordination status display, press the
button to see more details about the reason for the Coordination Plan Failure. An
example is shown here:
Free: Phase 2 Walk 4 plus Ped Clear 11
plus required clearance 4.0 exceeds Split
Time in seconds 15.0.
This message tells the End-User that the
Split for Phase 2 is 15.0 seconds. The
sum of Phase 2 Walk + Ped Clear + Yellow
+ Red exceeds the 15.0 second split.
To fix this bad plan, the End-User can
reduce the Ped + Clr to match the Split;
increase the Split/Cycle length to match
the Ped + Clr; or enable Ped Override
Mode on Screen 2.3.2.1-48.
Figure 32 – Example of additional information about a ‘Bad Plan’
In the case shown above, Walk Time + Ped Clearance Time + Yellow Time + All Red
Time adds up to a value in seconds that is greater than the Phase 2 Split value. The
sum of the Walk, Ped Clearance, Yellow and All Red times must be reduced, or the
Cycle Length must be increased to accomidate a longer Phase 2 Split.
56
Time of Day Status Screen
The TOD Status screen shows critical details about the controller’s operation when it is
controlled by a Time of Day schedule.
>
1.1.3
.S TATUS >
.C ONTROLLER >
.T IME
OF
D AY
TIME OF DAY STATUS
Time
: 09:03:10
Date
: Mon 19-Dec-2011
Local Cycle Zero : X
Current command : TOD/BKP COORD
Day Plan Status : 1
Action Number
: 1
Event Number
: 1
Control Plan
: 254
Backup Timer
: 0
TSP Action Plan : 0
Auxillary Outputs: ---Special Function
: -------Commanded Action Mask : 1-------
Figure 33 – Sample Time of Day Status Screen
This screen is helpful in determining if the ATC is correctly following its TOD
programming. In addition to the Time functions, this display shows each time the
coordinator passes over the ‘Local Cycle Zero’ point in the cycle.
Current Command — Text description of the currently operating pattern.
Day Plan Status — The Day Plan number (1-48) currently in effect.
Action Number — The TOD Action within the current Day Plan that is currently in
effect.
Event Number --- The current TOD Event # within the current Day Plan.
Current Control Plan — The pattern number currently running in the controller. Note
that this pattern could be the result of the Time of Day schedule, coordinated operational
mode, a central override, or central system control.
Backup Timer — If any of the objects under the backup timer have been set, the NTCIP
Backup Timer will show the current value as it counts down (in tenths of a second).
TSP Action Plan --- Current TSP Action (0-48) in effect, see Screen 2.8.3.
Auxiliary Outputs ---Enabled outputs (4) under TOD control, see Screen 2.4.1.2.
Special Function --- Enabled outputs (8) under TOD control, see Screen 2.4.1.2.
Commanded Action Mask – One of eight sets (1-8) of up to 100 TOD Commanded
Actions. Enabled when an ‘X’ has been placed under the current TOD Action.
Programmed using Screen 2.4.1.1.
57
Preemption Status Screen
This screen shows the status of any current preemption activity.
M AIN
MENU
> 1.S TATUS > 1.C ONTROLLER > 4.P REEMPTION (
>
>
>
)
1.1.4
PREEMPT STATUS
Active Preempt: 00
Inputs:
Key Inputs: 2
Ring Status:
R1: .. R2: .. R3: .. R4: ..
Min Dur: 00000 Max Pres: 00000
Min Dwl: 00000 Track G : 00000
Dwl Red: 00000 Extnd
: 00000
Input Delays
1:000 2:010 3:000
4:000 5:000 6:000
Figure 34 – Sample Preemption Status Screen
Active Preempt – Shows the two-digit number of the preemption run (01-06) being
serviced. ‘00’ indicates no runs active.
Inputs – Actual preemption run input (1-6) being received by the controller.
Key Inputs – This array of six characters shows if any manual preemption keypad
inputs have been placed on this screen. This screen can be used to place a manual
preemption call into the controller. Press a number between 1 and 6 on the front panel
keypad to place the call. The correponding number will appear next to ‘Key Inputs’. (It
will also show up as a number next to PRE KBD on the Controller Status screen (Either
HME or > 1.S TATUS > 1.C ONTROLLER ) But be aware that this is placing an active
preemption call into the controller. On this Preemption Status screen, the number
keys toggle these calls on and off. So press the number again to clear the preemption
call. Or, if multiple preemption calls have been placed here, press the
clear all of them simultaneously.
Caution
Note
58
button to
Keypad preemption calls will remain active until they are
cleared on this screen, or the ATC power is cycled.
The manually keyed preemption inputs that are available on this screen
are temporarily disabled during an ICC preemption.
Ring Status – Shows the current preemption status of the four rings. Each ring can
show one of these thirteen status messages:
Table 10 – Ring Status messages on the Preempt Status screen
Code
Meaning
IG
Initial Clearance Green. (Clearing non-preemption phases)
IY
Initial Clearance Yellow (Clearing non-preemption phases)
IR
Initial Clearance Red (Clearing non-preemption phases)
TG
Track Clearance Green
TY
Track Clearance Yellow
TR
Track Clearance Red
HG
Holding Track Clear Phase Green (Waiting for other Track Clear
Phases to turn Green)
DI
Waiting for All-Red Dwell
DR
Dwelling in All-Red
DL
Dwelling in Green or Cyclic Interval
DF
Dwelling in Flash
EX
Exiting in Yellow/Red Clearances
EF
Exiting Dwell Flash
Min Dur – Minimum Duration. Shows the current value, in seconds, for the preemption
run’s Min Duration timer
Max Pres – Maximum Presence. Shows the current value, in seconds, for the
preemption run’s Max Presence timer
Min Dwl – Minimum Dwell. Shows the current value, in seconds, for the preemption
run’s Min Dwell timer
Track G – Track Green. Current value, in tenths of seconds, for the run’s Track Green
Timer
Dwl Red – Red Dwell. Current value, in tenths of seconds, for the run’s Red Dwell
Timer.
Extnd – Extension. Current value, in tenths of seconds, for the run’s Extension Timer.
Input Delays – Shows the current value, in tenths of seconds, for each run’s Input Delay
timer.
59
Detector Status Menu
The Detector Status menu is used to access the vehicular and pedestrian detector
status screens.
M AIN M ENU > 1.S TATUS > 1.C ONTROLLER > 5.D ETECTORS
1.1.5
DETECTOR STATUS
1. VEHICLE DETECTOR STATUS
2. PEDESTRIAN DETECTOR STATUS
Figure 35 – Detector Status Menu
Vehicle Detector Status Screen
The Vehicle Detectors Status screens show the current state of all 64 vehicle detector
and 8 pedestrian detector inputs. It also shows if any detectors that have been placed
into a ‘failed’ state by the detection input diagnostics. An ‘X’ under any detector number
indicates that that detector is either active or has been judged to have failed.
M AIN M ENU > 1.S TATUS > 1.C ONTROLLER > 5.D ETECTORS > 1.V EHICLE D ETECTOR
S TATUS
1.1.5.1
ACTIVE
FAILED
ALARM
RALARM
ACTIVE
FAILED
ALARM
RALARM
VECHICLE DETECTOR STATUS PG1of2
1 1 1 1 1 1 1
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
X X X X
X X X
X
1 1 1 2 2 2 2 2 2 2 2 2 2 3 3 3
7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2
0=Oth,C=Coms,E=ErrCnts,M=MaxP,N=NoAct
X=ExsivChng,S=ShrtedL,L=OpenL,W=WatchD
Figure 36 – Sample Vehicle Detector Status Screen
For details on the detection input diagnostics, refer to page 176. The number at the top
of each column indicates the detector channel number. Use the
status of detector inputs 33 through 64.
button to see the
Active – An ‘X’ means the ATC is receiving a valid input from the this Detector channel.
Failed – An ‘X’ means that a failed condition has been detected on this channel. this
could mean that the detector has exceeded the time set for Max Presence (M),
exceeded the set counts per minute (E), and/or there is negative Channel Status
60
reporting (E, S, L, W or O) in accordance with NTCIP and NEMA TS2-2003, Paragraph
6.5.2.26.3.
Alarm – A letter code here indicates a Detector Diagnostics Failure which can be any of
the following: exceeded the set counts per minute (E), exceeded the time set for Max
Presence (M), exceeded set minute limit of no detector activity (N), or Negative Channel
Status reporting from the Detector for one or more of the following conditions: O=Other
(Report of a reserved [undefined] distinct status state), or lack of communications from
the Detector (C).
RAlarm – A Reported Alarm of Negative Channel Status has been received from the
Detector due to one or more of the following conditions: E=Excessive Inductance
Change (+ or – 25%), S=Shorted Loop (<20 microhenries), L=Open Loop (>2500
microhenries), W=Watch Dog Time Out, or O=Other (Report of a reserved [undefined]
status state).
Pedestrian Detector Status Screen
The Pedestrian Detector Status screen shows the current state of all eight of the
pedestrian detector input channels. It also shows if any of the channels have been
placed into a Failed state, along with information about any alarms that have occurred
on each detection channel.
M AIN M ENU > 1.S TATUS > 1.C ONTROLLER > 5.D ETECTORS > 2.P EDESTRIAN
D ETECTOR S TATUS
1.1.5.2 PED DETECTOR STATUS
ACTIVE
FAILED
ALARM
PG1of1
1 2 3 4 5 6 7 8
X
X
X
X
0=Oth,C=Coms,E=ErrCnts,M=MaxP,N=NoAct
Figure 37 – Sample Pedestrian Detector Status Screen
Again, for details on the detection input diagnostics, refer to page 176. The number at
the top of the column indicates the pedestrian detector channel. (1 through 8)
Active – An ‘X’ means the controller is receiving a valid input from this pedestrian
detector.
Failed – An ‘X’ here means that a failed condition has been detected on this channel.
Tthe Ped detector has either exceeded the time set for Max Presence (M), exceeded the
set counts per minute (E), and/or there is negative Channel Status reporting (E, S, L, W
or O) in accordance with NTCIP and NEMA TS2-2003, Paragraph 6.5.2.26.3.
Alarm – Either a Detector Diagnostics Failure of exceeded the set counts per minute
(E), exceeded the time set for Max Presence (M), exceeded set minute limit of no
detector activity (N), or Negative Channel Status reporting from the Detector for one or
more of the following conditions: O=Other (Report of a reserved [undefined] distinct
status state), lack of communications from the Detector (C).
61
TSP Status Screens
The Transit Signal Priority Input and Output Status screens can be used to monitor the
controller’s TSP function. The setup and functioning of TSP is described in detail in
“Chapter 10 — Transit Signal Priority”, starting on page 285.
M AIN M ENU > 1. S TATUS > 1.C ONTROLLER > 6. T.S.P
1.1.6
T.S.P Status
1. Inputs
2. Outputs
Figure 38 – TSP Status Menu
TSP Input Status Screen
Selecting option 1 from the TSP Status Menu will open the TSP Input Status screen,
which shows information about both the TSP inputs and the current state of the TSP
runs.
M AIN M ENU > 1.S TATUS > 1.C ONTROLLER > 6. T.S.P > 1.I NPUTS
1.1.6.1
TSP Input Status
3 inputs
per 8
Runs = 24
|Check- |Check- |Advance |
|In
|Out
|Cancel |
|Runs 1-8|Runs 1-8|Runs 1-8|
|
| 1111111|11122222|
|12345678|90123456|78901234|
Inputs |
|
|
|
Run Status |
|
|
|
1 1 1 1 1 1 1
Phase : 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
Color : r G r r r G r r r r r r r r r r
TSP Phases: 0 0 0 0
Status: Idle Pending
Figure 39 – Sample TSP Input Status screen
Inputs 1-24 represent the status of the raw TSP inputs, as follows:
Table 11 – TSP Inputs
Input
1
62
Function
Run 1 check-in/constant call
Input
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Function
Run
Run
Run
Run
Run
Run
Run
Run
Run
Run
Run
Run
Run
Run
Run
Run
Run
Run
Run
Run
Run
Run
Run
2
3
4
5
6
7
8
1
2
3
4
5
6
7
8
1
2
3
4
5
6
7
8
check-in/constant
check-in/constant
check-in/constant
check-in/constant
check-in/constant
check-in/constant
check-in/constant
check-out
check-out
check-out
check-out
check-out
check-out
check-out
check-out
advance cancel
advance cancel
advance cancel
advance cancel
advance cancel
advance cancel
advance cancel
advance cancel
call
call
call
call
call
call
call
An 'X' means that the input is active. A space (‘ ') means that the input is inactive.
R UN S TATUS – This represent the status of each TSP run, with a single character code
showing its current state:
“ ” (space) = Input inactive or disabled. Disabling could be caused by any of these
three situations: No TSP Action Plan, TSP Enabled is OFF, or TSP Run
Enabled is OFF.
R = Valid request
A = Active extending beyond normal point
T = Truncating non-tsp phases
F = Failed due to fail timer expiration
S = Success, request removed during extension
M = Removed before extension
D = Delay timing
E = Extend timing
C = Clearance fail, tsp call present when tsp phase turns off
r = Reservice inhibit
O = Priority override
I = Invalid, necessary programming is missing
63
C OLOR – This row of values indicates the current phase color:
G = green/steady don’t walk
Y = yellow
R = red clearance
W = green/walk
P = green/ped clearance
R = phase off
TSP P HASES : 0 0 0
from all contributing Runs.
0 – These represent the current compatible TSP phases
Status – The TSP input screen shows a general TSP status message on the bottom
line. It will always show one of these five messages:
Table 12 – TSP Status messages on the TSP Input Status screen
64
Message
Description
Active
TSP Active - Currently reducing intermediate phases’ splits
and/or extending TSP phase’s split
Balance
TSP is currently working to correct a timing offset by
performing Split Balancing. (See the Mode 2 topic under
“TSP Action Plans”, starting on page 301.)
Idle
TSP is not currently active
Idle Pending
TSP action has been completed and is waiting for Local
Zero
Recovery
TSP is currently correcting the offset error by extending or
reducing splits. (See Recovery Strategy, on page 301.)
TSP Output Status Screen
Choosing option 2 on the TSP Status menu displays the TSP Output Status screen.
M AIN M ENU > 1.S TATUS > 1.C ONTROLLER > 6.T.S.P > 2.O UTPUTS
1.1.6.2
Outputs:
Q Jumps:
TSP Output Status
_
1
2
2
_
3
4
4
Pattern Splits(1-16):
10 20 10 20
0
0
0
0
_
5
_
6
_
_
_
__
10
0
20
0
10
0
20
0
Commanded Splits(1-16):
8 28 10 20 10
0
0
0
0
0
20
0
7
0
18
0
Figure 40 – TSP Output Status screen
Outputs – 1-8 represent 'confirmation' outputs for each run. Outputs 9 and 10 are
currently not used. The number appears when the output is active.
Q Jumps – These represent ‘confirmation’ outputs for the six queue jump outputs
Pattern Splits – These represent the normal programmed split times that are used
when there is no TSP action
Commanded Splits – These represent the TSP-adjusted split times.
65
Overlaps Status Menu
The Overlaps Status screens provide a simple status display of the 32 vehicle overlaps
and 16 pedestrian overlaps. The Vehicle and Pedestrian Overlap Status screens can be
used to monitor the operation of NTCIP numbered Overlaps.
M AIN M ENU > 1. S TATUS > 1.C ONTROLLER > 7. O VERLAPS
1.1.7
OVERLAPS Status
1. Vehicle
2. Pedestrian
Figure 41 – Overlaps Status Menu
Vehicular Overlaps Status Screens
The Vehicular Overlaps Status screens consist of four status screens to display the
current state of the 32 available vehicular overlap phases. The setup and functioning of
overlaps is described in the “Overlap Menu” section, starting on page 153.
M AIN M ENU > 1.S TATUS > 1.C ONTROLLER > 7.O VERLAPS > 1.V EHICLE
1.1.7.1
VEH OVERLAP STATUS
1 RED 00.0
2
OFF
3
OFF
4
RED 00.0
5
RED 00.0
6
UNUSED
7
UNUSED
8
UNUSED
PG1of4
Figure 42 – Sample Vehicle Overlaps Status screen
Each of the programmed NTCIP numbered Vehicle Overlaps will display its current
interval color and time counting down. Overlaps not programmed will display UNUSED.
Press the
66
button to scroll though each of the four screens.
Pedestrian Overlaps Status Screens
Option 2 on the Overlaps Status menu will open the pedestrian overlaps status screen,
as shown in Figure 43, which displays the current output state of all 16 of the available
pedestrian overlaps of an ATC controller.
M AIN M ENU > 1.S TATUS > 1. C ONTROLLER > 7.O VERLAPS > 2. P EDESTRIAN
1.1.7.2
PED OVERLAP STATUS
1 DONT WALK
9 WALK
PG1of1
2 WALK
10 DONT WALK
3 DONT WALK
11 DONT WALK
4 WALK
12 DONT WALK
5 DONT WALK
13 DONT WALK
6 DONT WALK
14 DONT WALK
7 DONT WALK
15 DONT WALK
8 DONT WALK
16 DONT WALK
Figure 43 – Sample Pedestrian Overlaps Status screen
Each of the programmed NTCIP numbered Pedestrian Overlaps will display its current
interval. Overlaps not programmed will display a constant DONT WALK.
67
Sequencing Status Screen
Option 8 on the Controller Status menu is the Sequencing or Sequence Details status
screen. The Sequence Status screen provides a resultant status of programming
entered on the Phase Compatibility, Ring Sequencing, and Phase Enables screens for
the sequence in the current pattern. Just keep in mind that a ring sequence is inherently
a phase-based or NEMA representation of intersection operation, and means nothing in
an interval-based environment. The setup and functioning of the Sequence Numbers are
described in detail in the “Ring Sequencing Screens” topic, starting on Page 119.
M AIN M ENU > 1. S TATUS > 1. > C ONTROLLER > 8. S EQUENCING
1.1.8
SEQUENCE STATUS
Loaded Plan : 1
PG1OF1
Loaded Seq : 1
Barrier/Concurrency Groups:
|---------|
| 12 | 34 |
| 56 | 78 |
|
|
|
|---------|
Phases 10-16 are displayed as A-G
Figure 44 – Sequence Status screen
The sequencing in the intersection is a result of the programming that has been entered
on the Phase Compatibility Screens (2.1.3.1 and 2.1.3.2), the Ring Sequnecing screens
(2.1.6.1- through 2.1.6.16), and the Phase Enables screen (2.2.1). The concept of
“Concurrency Groups” (CGs) grows out of theinteraction between these settings, and is
represented in the Sequence Status diagram by vertical barrier lines separating CGs
and rows representing rings.
Loaded Plan– Shows the currently active pattern number. (Valid values are 1 - 48.)
These values are programmed on screen 2.3.2.1 through 2.3.2.3. The loaded plan is
displayed, whether it is a phase-based plan (1-48) or an interval-based plan (101-253).
Loaded Sequence – Currently programmed sequence number, in the range 1-16.
These values are programmed on screen 2.1.6.1. Refer to “Ring Sequencing Screens”
on page 119.
Barriers – Compatibility barriers are indicated by vertical lines in the diagram.
Concurrency Groups – Phase numbers inside the barriers. Each horizontal row
(across the barriers) is a ring. Each box is a group of compatible phases. A concurrency
group is a phase group whose phasees are mutually compatible. (Phases in the same
ring are mutually conflicting.) The top row (Ring 1) is compatible with bottom row (Ring
2) phases between the barriers. To program these values, refer to screens 2.1.3.1 and
2.1.3.2. Refer to “Phase Compatibility Screens” on page 85.
68
NTCIP Sequence Consistency Checks
After the formation of concurrency groups, as displayed in Figure 44, the ATC will
automatically conduct a series of NTCIP Consistency Checks. The checks are explained
in the following table.
2
Table 13 – Sequence Consistency Checks
PHASE P CONCURRENCY FAULT
PHASE P MUTUAL FAULT
SEQ S SAME PHASE FAULT
SEQ S RING R FAULT
SEQ S RING R PHASE OMITTED
SEQ S RING SEQ FAULT
SEQ S CG SEQ FAULT
SEQ S SEQUENCING FAULT
2
Phase P’s Compatible Phases must be in a different Ring than Phase
P’s Ring assignment.
Example: Phase 2’s compatible Phases are 5 and 6. Phase 2 is in
Ring 1. Phases 5 and 6 cannot be in Ring 1.
If Phase X is programmed compatible with Phase P, then Phase P
must be programmed compatible with Phase X.
No repeated phases allowed in Sequence S’s Ring.
Example: Ring 1 Sequence of 1-2-3-4-3 is not allowed.
Repeating phases must be done using an extra phase and on Overlap
driving the field signals. Instead make above Ring 1 Sequence 1-2-34-x and use Overlap 1/A with included (parent) phases 3+x to drive the
field signals (where x is an available phase).
Each Phase assigned to a Ring R sequence on RING SEQUENCING
Screen 2.1.6.S, must have its Ring Assignment equal to zero (0) to
disable the phase OR R on PHASE COMPATIBILITY Screen
2.1.3.1/2.
Each Phase assigned to a non-zero Ring R on PHASE
COMPATIBILITY Screen 2.1.3.1/2, MUST EXIST in Sequence S, Ring
R’s SEQUENCING Screen 2.1.6.S.
Sequence S’s Concurrency Group (CG) satisfies each Ring’s
Sequence, but the CGs cannot be arranged without running one or
more phases more than once before every phase has a chance to run.
Example Compatibilities: 1->5,6; 2->5,6; 3->7,8; 4->7,8; 5->1,2
6->1,2; 7->3,4; 8->3,4.
Example Sequence: R1 = 1-3-2-4; R2 = 5-6-7-8.
Example CGs created: 1| 3| 2| 4|
5-6|7-8|5-6|7-8|
The example CGs are unacceptable because they cannot be arranged
without serving Phases 5, 6, 7 and 8 a second time when Phases 2
and 4 run.
Sequence S cannot arrange its CGs to satisfy each Ring’s Sequence.
Example Compatibilities: 1->6; 2->5,6; 3->7,8; 4->7,8; 5->2
6->1,2; 7->3,4; 8->3,4.
Example Sequence: R1 = 2-1-3-4; R2 = 6-5-7-8.
Example CGs created: 2|1| 3-4|
6-5|6| 7-8|
Ring 2’s Sequence is a violation, as Phase 6 is repeated.
Sequence S can arrange CGs in multiple ways to satisfy each Rings
Sequence.
Example Compatibilities: 1->5,6; 2->5,6; 4->4; 5->1,2
6->1,2; 8->8.
Example Sequence: R1 = 1-2-4; R2 = 5-6-8.
Example CGs created: 1-2|4| x| or 1-2| x|4|
5-6| x|8|
5-6|8| x|
The example CGs are unacceptable because the CGs must satisfy
each Ring’s Sequence with only one solution.
In this table, S=Sequence Number, P=Phase Number, R=Ring Number
69
Texas Diamond Status Screen
The Texas Diamond Status screen provides a simple status display of ATC operation
during the implementation of a Texas Diamond sequence, which is an intersection
where a single controller is charged with coordinating the signals for both intersections
on either side of a highway interchange. (Typically a surface street that intersects a
highway, and provides on and off ramps to the highway on either side of the actual
highway, which crosses either over or under the surface street.) The Texas Diamond
function can be enabled/disabled on Screen 2.1.7. Refer to “USTC Miscellaneous
Screen” on page 121 for details.
M AIN M ENU > 1.S TATUS > 1. > C ONTROLLER > 9. T EXAS D IAMOND S TATUS
1.1.9
TEXAS DIAMOND STATUS
Commanded Mode
:4 Phase
Current Mode
:4 Phase
Transition Status:Separate
Omit Phases
:1 2 3 5
Call Phases
:1 2 3 5
Extend Phases
:1 2 3 5
Dual Entry Phases:1 2 3 5
Figure 45 – Texas Diamond Status screen
Commanded Mode– The last received mode of operation. The possible settings are:
None (0), 4 Phase (1), 3 Phase (2), Separate (3), Nema (4)
Current Mode – The present operating mode. The possible values are: None (0), 4
Phase (1), 3 Phase (2), Separate (3), Nema (4)
Transition Status – Shows the current state of the Texas Diamond management
pattern. It can have one of three values: Idle, Transitioning, or Separate.
The value will show ‘Idle’ if the Commanded Mode = None;
It will show ‘Transisitioning’ if the Commanded Mode and Current Mode are
different; And it will show ‘Separate’ if the Commanded Mode and Current
Mode both have the same value that is something other than ‘None’.
For the final four values, keep in mind that the Texas Diamond operating mode is an
active, smart manager of intersection operation. It will disregard any preset phase
omits, calls, extensions and dual entry settings you have defined, and set those values
based on the number of enabled phases, and the Texas Diamond mode that is currently
running. The final four parameters on this screen show the Texas Diamond defined
settings for those values.
Omit Phases – Mode of operation designed, dynamic omitted phases
Call Phases – Mode of operation designed, dynamic recalled phases
Extend Phases – Mode of operation designed, dynamic extended phases
Dual Entry Phases – Mode of operation designed, dynamic dual entry phases
70
Inputs/Outputs Status Menu
INPUTS/OUTPUTS STATUS MENU
Option 2 from the Status menu will take you into the Inputs/Outputs Status menu, which
provides a set of status screens pertaining to the operation of the physical inputs to and
outputs from the controller.
M AIN M ENU > 1.S TATUS > 2. > I NPUTS /O UTPUTS
1.2
INPUTS/OUTPUTS MENU
1. INPUTS
2. OUTPUTS
3. SDLC & FIO
Figure 46 – Inputs/Outputs Status Menu
Inputs Status Screen
The Input Status screen shows the state of all of the important input signals coming into
the controller. These include the vehicle and pedestrian calls, force-offs, overrides, ring
inputs and unit or machine input parameters.
M AIN M ENU > 1.S TATUS > 2.I NPUTS /O UTPUTS > 1.I NPUTS
1.2.1
INPUTS TS2
PG1of1
PHASE
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
VEH O
X
X
X X X X X X X X
PED O
X
X
X X X X X X X X
VEH H
X
X
F/O
VEH C
PED C
RING INPUTS
1 2 3 4 MACHINE INPUTS
STOP TIME......
MIN RCL.X
FORCE OFF......
WRM.....
MAX 2..........
CNA 1...
MAX INHIBIT....X X X X CNA 2...
PED RECYCLE....X X
MCE.....
RED REST.......
INT ADV.
OMIT RED CLEAR.
EXT ST..
Figure 47 – Sample Inputs Status Screen
The Inputs Status screen is divided into three regions:
Phase (affecting only that phase)
Ring (affects any phase active in a ring)
and Machine (affecting all phases)
71
1.2
INPUTS TS2
PG1of1
PHASE
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
VEH O
X
X
X X X X X X X X
PED O
X
X
X X X X X X X X
VEH H
X
X
F/O
VEH C
PED C
RING INPUTS
1 2 3 4 MACHINE INPUTS
STOP TIME......
MIN RCL.X
FORCE OFF......
WRM.....
MAX 2..........
CNA 1...
MAX INHIBIT....X X X X CNA 2...
PED RECYCLE....X X
MCE.....
RED REST.......
INT ADV.
OMIT RED CLEAR.
EXT ST..
phase data
machine inputs
ring data
Figure 48 – The functional sections of the Inputs Status screen
The Input screen is used to troubleshoot and validate the state of the controller inputs.
The Ring inputs are fairly self-explanatory, but some of the abbreviations may cause
confusion.
Phase inputs:
VEH O – Vehicle Omit input for this phase
PED O – Pedestrian Omit input for this phase
VEH H – Vehicle Hold input for this phase
F/O – Force-Off input for this phase
VEH C – Vehicle Call on this phase. Could be the result of a recall placed on the phase
PED C – Pedestrian Call on this phase, may be a result of a recall placed on the phase
Ring (1-4) inputs:
STOP TIME – Stops Timing all Phases assigned to numbered Ring
FORCE OFF – Terminates all Phases assigned to numbered Ring
MAX 2 – Applies programmed Maximum 2 times to all Phases in Ring
MAX INHIBIT – Stops Max Outs for all Phases in Ring
PED RECYCLE – Allows Ring Peds to run again, if remaining time is sufficient
RED REST – Allows Ring Phases to Rest in Red
OMIT RED CLEAR – Stops timing of Red Clearance for Ring Phases
Unit or Machine (All Phases) Inputs:
MIN RCL – Minimum recall input (an OR on all 16 inputs)
WRM – Walk Rest Modifier input on all CNA Peds
CNA 1 & 2 – Call to Non-Actuated 1 and 2 enabled inputs
MCE – Manual Control Enabled input, often the result of a ‘Police’ key switch being
turned within the cabinet
INT ADV – Interval Advance input (used in conjunction with MCE to manually ‘step
through’ an intersection’s cycle
EXT ST – External Start enabled input
72
Inputs/Outputs Status Menu
Outputs Status Screen
The Outputs Status screens (there are two) show the output signal states of the ATC
controller, phase by phase. These include the red, yellow, green, walk, don’t walk,
pedestrian clear, phase next , phase on, and phase check outputs for each of the 16
possible phases. A ‘ ‘ (blank) below the phase means it is off. An ‘X’ below the phase
means it is on.
M AIN M ENU > 1. S TATUS > 2. I NPUTS /O UTPUTS > 2. Outputs
1.2.1
PHASE
RED
YELLOW
GREEN
PED DW
PED CLR
WALK
P NEXT
P ON
P CHECK
OUTPUTS
PG1of2
1 1 1 1 1 1 1
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
X
X X X
X X
X
X
X
X
X
X
X
X
X
X
Figure 49 – Sample Outputs Status Screen
Use the
and
buttons to move between the two Output Status screens.
The second Outputs Status screen provides an alterante view of outputs, but also
includes the output signal states for Vehicle and Pedestrian Overlaps. These include the
red, yellow, green, don’t walk, pedestrian clear, and walk. The channel outputs for each
of the 16 possible channels is a representation of how the signals will appear on each
numbered load switch after any routing, such as back panel wiring or IO mapping, has
been applied.
1.2.2
OUTPUTS
PG2of2
11111111112222222222333
VEH OVL 12345678901234567890123456789012
RED
XXXX
YELLOW
GREEN
1 1 1 1 1 1 1
PED OVL 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
DONT W X X X X X X X X X X X X X x X X
CLEAR
WALK
1 1 1 1 1 1 1
CHANNEL 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
RED
X X X
X X
X X
X X
YELLOW
GREEN
X
X
X
Figure 50 – Page 2 of the Outputs Status Screens
73
SDLC & FIO Status Screens
This screen is helpful in determining if the ATC controller has any errors on the
Synchronous Data Link Control (SDLC) communication port – commonly referred to by
NEMA as Port 1. SDLC communications during NEMA TS2 Type 1 operation include
interactions with Terminal & Facilities Buss Interface Units (BIUs), Detector Buss
Interface Units (BIUs), and the MMU. TS2 Type 2 can optionally utilize SDLC
communications between Detector Buss Interface Units (BIUs), and/or the MMU.
M AIN M ENU > 1.S TATUS > 2. I NPUTS /O UTPUTS > 3. SDLC S TATUS )
Terminal &
Facilities BIUs
Detector BIUs
MMU
Front panel to
I/O Module
communications
1.8
SDLC & Field I/O STATUS
SDLC OVR:00000 CRC:00000
T1T00000000 R00000000 n00000000
T2T00000000 R00000000 n00000000
T3T00000000 R00000000 n00000000
T4T00000000 R00000000 n00000000
D1T00000000 R00000000 n00000000
D2T00000000 R00000000 n00000000
D3T00000000 R00000000 n00000000
D4T00000000 R00000000 n00000000
MUT00000000 R00000000 n00000000
t00
t00
t00
t00
t00
t00
t00
t00
t00
F000550179 R00183393 n00366784
t00 r00
r00
r00
r00
r00
r00
r00
r00
r00
r00
Error counts on each BIU
communications line:
T = Transmitted
R = Received
n = No Responses
t = Transmit Errors
r = Response Errors
Figure 51 – SDLC Status Screens
At any suspected failure of the ATC controller, this screen should be viewed and the
result documented for analysis.
SDLC OVR – Number of SDLC overruns, or in other words, the number of times the
data flow into the controller has exceeded its capability to handle the flow.
CRC – Number of Cyclical Redundancy Check errors. CRC is a method to check that
the data sent is the same as the data received by encoding a piece of data within a
packet that is dependent on the contents of the rest of the packet. A CRC error tells the
device to request a retransmission of the data packet until it is received without such an
error. A high count in this field indicates that the transmission line is ‘noisy’, which could
indicate interference or a mechanical problem with the wire or connectors.
The rows show communications statistics for the four Terminal and Facility BIUs (T1-4),
four Detector BIUs (D1-4), and MMU (MU) data. Front Panel (F) communications to the
other components of the ATC is the bottom row. This data is cleared on power up. The
columns show the numbers of transmissions (T), receive packets (R), and not
acknowledged responses (n). Transmit packet errors (t00) and receive packet errors
(r00) quantities are the last two columns.
74
Alarms Status Menu
ALARMS STATUS MENU
There are two Alarm Status screens, available from the Alarm Status menu.
M AIN M ENU > 1.S TATUS > 3.A LARMS
1.3
ALARM STATUS MENU
1. UNIT ALARM STATUS 1 & 2
2. SHORT ALARM STATUS
Figure 52 – Alarms/Event Status Menu
Unit Alarm Status 1 & 2 Screen
Option 1 will display the first of the Alarm Status displays.
1.3.1
ALARM STATUS 1 & 2
STOP TIME......
EXT START......
RESPONSE FAULT.
POWER RESTART..X
COORD ACTIVE...
LOCAL FREE.....X
LOCAL FLASH....
COORD FAIL.....
CYCLE FAULT....
COORD FAULT....
Figure 53 – Alarm Status display
This screen shows the status of NTCIP Status data objects (These are called ‘unit Alarm
Status 1’ and ‘unit Alarm Status 2’ in the controller database and in standard NTCIP data
structures.) An ‘X’ next to one of these binary data objects indicates that that alarm has
been triggered at some point. Most are cleared as soon as the alarm condition ends,
however some items ‘latch’, or remain ON until some event clears them. The Power
Restart bit will stay active until a read from the central system takes place. The
Response Fault is triggered by a NEMA TS2 Port 1 error and will remain until the
condition is corrected. The remaining alarms are cleared as the alarm conditions end.
75
Short Alarm Status Screen
Option 2 on the Alarm Status menu will display the Short Alarm Status screen, as shown
in Figure 54.
M AIN M ENU > 1.S TATUS > 3.A L ARMS > 2.S HORT A LARM S TATUS
1.3.2 SHORT ALARM STATUS
CRITICAL ALARM.....
NON CRITICAL ALARM.
DETECTOR FAULT.....
LOCAL OVERRIDE.....
LOCAL CYCLE ZERO...
T AND F FLASH......
PREEMPT............
Figure 54 – Short Alarm Status screen
This screen represents the data stored in the NTCIP database object called ‘short Alarm
Status’. Often, central system software polls the controller for this data on a second-bysecond basis.
Critical Alarm — This is raised as a result of the Stop Time input being ON
NON-Critical Alarm — This is the Cabinet Door switch or Lamp Indicator control
Detector Fault – One or more detectors have been found to be ‘faulty’ by the detector
input diagnostics. (Refer to page 176 for details.)
Local Override — MCE (Manual Control Enabled) active
Local Cycle Zero — This bit is set each time the controller passes the top of a new
cycle
T and F Flash – Terminals and Facilities flash mode
Preempt – The controller has received a preemption input and is currently serving a
preemption run
76
MMU Status Screens
MMU STATUS SCREENS
The MMU Status screen shows the current channel states, inputs received and outputs
from the connected CMU/MMU.
(M AIN M ENU > 1.S T AT US > 4.MMU)
1.A.1
MMU INPUTS
PG1of2
1 1 1 1 1 1 1
CHANNEL 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
RED
:
YELLOW:
GREEN :
CVM : X 24V1: X 24V2: X 24V_INHIB:
RESET:
R-EN:
CONF:
RED FAIL :
DIAGF:
MINC:
P1TO:
O RELAY :
RESP TO FAIL:
STARTUP CALL:
LOCAL FLASH :
Figure 55 – Sample MMU Status screen
This screen shows the current data from the MMU’s frame 129 response. This screen is valuable
for troubleshooting suspected cabinet issues. Inputs (I) and Outputs (O) are listed below.
CVM – Controller Voltage Monitor or Fault Monitor (I)
24V1 – +24V DC Monitor 1 (O)
24V2 – +24V DC Monitor 2 (O)
24V_INHIB – +24V DC Inhibit Input (I)
Reset – Reset button or input (I)
R-EN – Red Enabled input (I)
CONF – Conflict fault detected, indicating some combination of incompatible greens or yellows
occurred at the same time for a period longer than the allowable recognition time. (O)
Red Fail – Red Fail flag. No red signal visible in preset amount of time. One or more channels has no
indications at all above the required signal thresholds. (O)
DIAGF – Diagnostic failure. A software diag failure indicates the unit has failed its program-based
diagnostics. A hardware diag failure indicates that the controller is not toggling the watchdog circuit.
(O)
MINC – Multiple indications failure. This is a result of more than one signal being ON within the same
channel, e.g. both yellow and red are being displayed on channel 2. (O)
P1TO – Port 1 Type 0 failure. In certain modes, the MMU must be in constant communications with the
controller. If the MMU does not receive a Type 0 command frame from the controller within 300
milliseconds, a Port 1 failure will be declared.
O RELAY – Output relay fault indicates that this relay is de-energized, which could indicate that the
MMU has lost power, or the MMU has placed the cabinet in flash mode.
RESP TO FAIL – An ‘X’ next to this message indicates that the CMU/MMU responded immediately to
a detected fault.
STARTUP CALL – The MMU has commanded the controller to restart, by sending the ‘Startup
Call’ bit for two or more consecutive messages.
LOCAL FLASH – The monitor’s local flash switch has been turned ON. This is usually the input
used for a ‘Police Flash’ button or cabinet switch.
The second screen of MMU status information is reserved for future use.
77
REVISIONS SCREEN
This screen provides details about the versions of software and firmware installed in the
ATC.
M AIN M ENU > 1. Status > 5. Revisions
1.5
MODEL
: Peek Model ATC
DB ver
: 6
U-Boot 1.1.4 (Apr 13 2010 - 12:18:49)
#23 PREEMPT Mon Oct 18 23:23:54 EDT 2010
IO D Module: LMD9200 CPC SUB 15IN
Figure 56 – Revision Details Screen
Model – Describes the hardware platform. For ATC-1000, ATC-2000 and ATC-3000
devices, it will indicate ‘Peek Model ATC’.
GREENWave – This is the release version of ATC Firmware that is currently installed in
your controller. This number should change whenever you use a USB thumbdrive, or
ATC Link, to update the firmware on your controller. This piece of information may be
useful when attempting to troubleshoot the controller, or whenever communicating with
Peek Traffic customer support.
DB ver – The internal database version used to store the controller’s parameters.
Boot Loader Version – The boot loader and utilities screen are hosted on the
controller’s video/keyboard PCB and are managed separately from the GREENWave
firmware.
Linux Version – Indicates the current version of the controller’s operating system.
IO Module – The type of installed I/O module that is detected by the controller’s Main
board. Make sure this matches the physical hardware that is installed.
IO D Module – The type of optional D Module that is installed in the bottom right corner
of the controller’s front panel, as detected by the controller’s Main board. Make sure that
this matches the physical hardware that is actually installed.
MAC ADDR – This screen also shows the unique identifier of the controller’s Ethernet
network port, the MAC address. The MAC address is set at the Peek factory and is
unique to each individual ATC controller.
78
Chapter 5 — Programming Menus
This chapter describes the programming portion of the controller menu system. The following
topics are discussed in detail in this chapter:
•
Overview of the Programming screens, on page 80.
•
Unit Configuration screens, starting on page 80.
•
Controller configuration screens, starting on page 136.
•
Coordination configuration screens, starting on page 190.
•
Time of Day configuration screens, starting on page 155.
•
Detectors configuration screens, starting on page 173.
•
Preemption configuration screens, starting on page 182.
•
Interval-based configuration, starting on page 183.
•
Transit Signal Priority configuration, starting on page 184.
79
OVERVIEW OF THE PROGRAMMING SCREENS
Option 2 on the Main Menu is the Programming menu, where the intersection and trafficspecific settings of the controller can be viewed and modified.
M AIN M ENU > 2. P ROGRAMMING
2
1.
2.
3.
4.
5.
6.
7.
8.
PROGRAMMING MENU
UNIT CONFIGURATION
CONTROLLER
COORDINATION
TIME OF DAY
DETECTORS
PREEMPTION
INTERVAL
TRANSIT SIGNAL PRIORITY
Figure 57 – Programming Menu
UNIT CONFIGURATION MENU
The Configuration Menu hosts parameter screens that define the general operation of
the controller, meaning items that define the startup modes, communications, general
flash, and other global operating parameters of the unit.
M AIN M ENU > 2 . P r o g r a m m i n g > 1 . U n i t C o n f i g u r a t i o n
2.1
1.
2.
3.
4.
5.
6.
7.
8.
9.
0.
CONFIGURATION MENU
STARTUP
PROGRAM FLASH
PHASE COMPATIBILITY
CHANNELS
COMMS AND I/O SETUP MENU
RING SEQUENCING
USTC MISCELLANEOUS
ABS ZERO
LOGIC PROCESSING
EXCLUSIVE PEDESTRIAN
Figure 58 – Configuration Menu
80
Unit Configuration Menu
Start-Up Configuration Screen
The parameters on this screen determine how the ATC will operate when power is
applied to the unit after an outage that has lasted longer than a few seconds.
M AIN M ENU > 2. P ROGRAMMING > 1. U NIT C ONFIGURATION > 1. S TART -U P
2.1.1
START-UP MENU
MIN FLASH...............001
AUTO PEDCLEAR(ON/OFF)...ON
BACK-UP TIME..........00600
RED REVERT.............00.0
YELLOW CLEARANCE.......00.0
RED CLEARANCE..........00.0
1 1 1 1 1 1 1
START-UP 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
GREEN
X
X
WALK
X
X
YELLOW
RED
Figure 59 – Start-Up Screen
Min Flash – The number of seconds after power-up that the unit should stay in Flash
mode before initiating normal phase or interval operation. This can be any value from 0
to 255 seconds.
Auto PedClear (ON/OFF) – This parameter determines how pedestrian signals (e.g.
Walk/Flashing Walk/Don’t Walk) operate after a local override by an official at the
cabinet, such as a police officer, occurs. Such an action taken by an official is known as
an MCE (Manual Control Enable) event. When OFF, the MCE override takes immediate
effect, even if the pedestrian WALK signal has not finished timing. If the parameter is
ON, then pedestrian movements are cleared as normally defined (FDW) no matter how
many times the MCE push button is pressed. The default value is OFF.
Back-Up Time – A value between 0 and 65,535 seconds (18+ hours). If the controller is
operating in an environment where it is being told to use a particular traffic pattern by a
central computer or a central coordinating controller (i.e. ‘Traffic Responsive’ operation,)
it will expect to receive an NTCIP ‘Set’ command across its communications ports at
regular intervals. If the controller fails to hear a Set command for one of these ‘system
control parameters’ within the backup time period, the controller will first try to run its
own scheduled Time of Day pattern. If that also fails, then the controller will fall back to
its default pattern.
Red Revert – This global setting determines how short a red signal is allowed to display.
So, say that an override or a preemption comes in that tells a particular traffic movement
to go green. But that movement has just turned yellow. The Red Revert time, which is a
value in tenths of seconds between 0.0 and 25.5 seconds, tells the controller to show a
red signal of at least that long before switching to the green display.
Yellow Clearance – This setting determines how long a phase programmed to start in
yellow will display that yellow. The Yellow Clearance time can be any value between 0.0
and 25.5 seconds. A value of zero (0) entered here will cause the ATC to use the
programmed Yellow Clearance Time from the Clearance Timing Menu Screen (MM.
2.2.3.1).
81
Red Clearance – If a phase is programmed to start in red, this setting determines how
long the red will display. The Red Clearance time can be any value between 0.0 and
25.5 seconds. A value of zero (0) entered here will cause the ATC to use the
programmed red clearance time from the Clearance Timings Menu Screen (MM.2.2.3.1).
Start-Up (Green/Walk/Yellow/Red) Settings – These values define the signal outputs
to use for each phase after the controller completes its start-up flashing period (as
defined by the Min Flash parameter on this screen.) Once these phase signal states are
in place and then time-out, normal operation of the intersection can begin. It is important
to remember to follow safety rules when setting these phase states. Multiple start-up
phase colors and walks MUST be compatible, or an NTCIP consistency check error will
occur.
The controller will not allow an unsafe initial condition to be entered, but it does not
monitor these inputs as you enter them. It merely checks to see if the whole table is valid
when you use the
key combination to commit the changes to the controller’s
database. If any invalid phase settings exist (for example, if more than one color for a
phase has been defined), GreenWave will display an error screen and require that
changes are made to these settings.. The error message does not indicate all of the
problems within the table, merely the first one that was detected.
82
Program Flash Screen (MUTCD Flash)
This screen defines how Soft Flash or MUTCD Flash outputs are displayed. Soft or
MUTCD Flash (the terms are synonymous) originates from the ATC itself, rather than
through the cabinet’s flasher. The other flash modes used in NEMA cabients are merely
triggered by the controller. In those other cases, the flash signals themselves are
actually generated by the cabinet’s flash transfer relays. By generating its own flash
signals during MUTCD Flash mode, the controller maintains direct control of the
intersection, and can therefore switch back to normal operation on a time-of-day basis.
M AIN M ENU > 2. P ROGRAMMING > 1. U NIT C ONFIGURATION > 2.P ROGRAM F LASH
2.1.2
MUTCD FLASH MENU
PHASE CHANNEL
PG1OF1
1111111
1234567890123456
ENTER MUTCD FLASH...... X
X
EXIT MUTCD FLASH......
X
X
YELLOW FLASH CHANNEL... X
X
RED FLASH CHANNEL...X XXX XX
ALT. HALF HZ. CHANNEL... X
X
MINIMUM FLASH TIME(SEC)..........010
FLASH EXIT YELLOW TIME(SEC)......010
FLASH EXIT RED TIME(SEC).........005
Figure 60 – MUTCD Flash Screen
Caution
Note
The values shown in Figure 60 are not valid for all intersections. Be very
aware of safety considerations when programming this important
screen.
Program Flash is Pattern 255 when used in the TOD screens or overrides, or
when commanded by a central system or Coord Operational Mode.
Enter MUTCD Flash – When these selected phases or channels are finished being
served,the intersection will go to all red and then into MUTCD Flash mode.
Exit MUTCD Flash – These settings define which phases will be served with green first
upon leaving MUTCD Flash mode, as an entry point into the next programmed or
commanded pattern.
Note
The Enter MUTCD Flash and Exit MUTCD Flash parameters are used by the
traffic engine when switching between NEMA phase-based and interval-based
operation.
83
Yellow Flash Channel – This array of 16 on/off values defines which phases or
channels will flash yellow during MUTCD Flash operation. The same phase cannot be
flashed in both red and yellow.
Red Flash Channel – These define which phases will flash red during MUTCD Flash
operation. The same phase cannot be flashed in both red and yellow.
Alt Half Hz Channel – These define which phases or channels will flash on an
alternating time cycle. A normal MUTCD flash signal is a 1 second cycle with a 50% duty
cycle, meaning the signal will be on for a half second, and then off for a half second.
Normally, the controller flashes all phases set to yellow and red flash on the same cycle.
This option tells the selected phases to flash in the opposite schedule. Sometimes
known as ‘Wig-Wag’ flash operation, this tells the controller to flash the phases that are
set to Alternate Half Herz ON, when the other flash signals are OFF.
Minimum Flash Time(Sec) – This is the minimum amount of time, in seconds, that the
controller must stay in the MUTCD flash pattern before it can be switched away to
another pattern. The range of values is from 0 to 255 seconds.
Flash Exit Yellow Time (Sec) – This is the amount of time, in seconds, that all Exit
phases are placed into a steady yellow state, before the controller switches to the next
programmed or commanded pattern. The range of values is from 0 to 255 seconds.
Flash Exit Red Time (Sec) – This is the amount of time, in seconds, that all phases are
placed into a steady red state, before the controller switches to the next programmed or
commanded pattern. The range of values is from 0 to 255 seconds.
84
Phase Compatibility Screens
The top part of this screen allows one to set which phases belong to which rings. The
valid values are 0 through 4. A value of 0 (zero) disables that phase.
The bottom part of the screen is used to define which phases can be green at the same
time as other phases, i.e. which phases can run concurrently. The first of these two
screens covers compatible phases 1 through 8, and the second screen covers
compatible phases 9 through 16. (The phase to ring settings are identical on both
pages.)
M AIN M ENU > 2. P ROGRAMMING > 1. U NIT C ONFIGURATION > 3. P HASE
C OMPATIBILITY
2.1.3.1
PHASE
PHASE COMPATIBILITY PG1OF2
1 1 1 1 1 1 1
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
RING
1 1 1 1 2 2 2 2 0 0 0 0 0 0 0 0
COMPATIBILITY PHASES PHASE 1
X X
PHASE 2
X X
PHASE 3
X X
PHASE 4
X X
PHASE 5 X X
PHASE 6 X X
PHASE 7
X X
PHASE 8
X X
Figure 61 – Phase Compatibility Screen (Page 1)
Use the
button to switch to the second screen of settings, to see and edit the
compatibility settings for phases 9 through 16.
Ring – This number can be set to a value between 0 and 4, which indicates to what ring
the phase number shown just above the Ring row belongs. Choosing 0 indicates that the
phase is not part of any ring, which effectively disables that phase.
Compatible With – An ‘X’ in this grid indicates that the phase indicated by the row
number and the phase indicated by the column are compatible phases.
Important!
NTCIP does not follow the “Co-Phase” rules that were used in the Peek
3000E controller.
One can look at the Sequence status display to make sure the sequence is as expected,
once you are done with this page of programming.
Additional Notes About Programming Phase Compatibility
A significant link exists between the formation of compatibility groups created by the
settings on the Phase Compatibility screen and the programming on the Ring
Sequencing Screens (MM.2.1.6.1-16). This link is applied by the NTCIP standard and
85
it requires further explanation. If the next two figures provide the phase compatibility
programming . . .
2.1.3.1
PHASE
PHASE COMPATIBILITY PG1of2
1 1 1 1 1 1 1
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
RING
1 1 1 2 2 2 3 3 3 3 0 0 0 0 0 0
COMPATIBILITY PHASES
PHASE 1
X
PHASE 2
X
PHASE 3
X
PHASE 4 X
PHASE 5
X
PHASE 6
X
PHASE 7 X X
X X
PHASE 8 X X
X X
–
X X
X X X
X X
X X X
X
X
Figure 62 – Example Phase Compatibility Screen (Page 1)
2.1.3.2
PHASE
PHASE COMPATIBILITY PG2of2
1 1 1 1 1 1 1
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
RING
1 1 1 2 2 2 3 3 3 3 0 0 0 0 0 0
COMPATIBILITY PHASES -PHASE 9
X
X
PHASE 10
X
X
PHASE 11
PHASE 12
PHASE 13
PHASE 14
PHASE 15
PHASE 16
Figure 63 – Example Phase Compatibility Screen (Page 2)
...then the Ring values repeated on the above screens must match the programming on
the Ring Sequencing screens, as shown in Figure 64.
2.1.6.1
RING SEQUENCING
PG 1of16
SEQUENCE NUM 1
RING
1 1 2 3 . . . . . . . . . . . . .
2 4 5 6 . . . . . . . . . . . . .
3 7 8 9 10. . . . . . . . . . . .
4 . . . . . . . . . . . . . . . .
Figure
RING 64 – Example of consistent Ring Sequencing programming
86
These example values for phase compatibility and ring sequencing will generate the
following sequence diagram on the Sequence Status screen:
1.1.8
SEQUENCE STATUS
Loaded Plan : 1
Pg1OF1
Loaded Sequence : 1
Barrier/Concurrency Groups
|--------------|
| 1 | 2
| 3 |
| 4 | 5
| 6 |
| 78 | 789 | A |
|--------------|
Ring 1
Ring 2
Ring 3
Phases 10-16 are displayed as A-G
Figure 65 – Resulting Sequence Status screen
In this example, if phases 1, 4 and 8 are being serviced and valid calls exist on all ten
phases, the ATC will advance to Phases 2, 5 and 9. It will not advance to Phases 2, 5
and 7. Phase 7 had a chance and might have been serviced with Phases 1 and 4, in
Concurrency Group 1; however, the ring sequencing definitions give the answer, not the
barrier/concurrency group structure shown on the Sequence Status screen, of what
phases will be serviced next.
87
Channels Screens
A Control Channel is a Load Switch assignment. An ‘X’ below a Control Channel to the
right of VEH, PED, VEH OVL or PED OVL indicates which type of signal is routed to that
Load Switch. The NTCIP protocol requires channel assignments no matter what type of
cabinet environment is being used. The Source value on this screen defines which VEH,
PED, VEH OVL or PED OVL number is controlling that output. One change from the
typical NEMA channel assignment process is that NTCIP vehicle and pedestrian
overlaps are numbered, not lettered.
M AIN M ENU > 2. P ROGRAMMING > 1. U NIT C ONFIGURATION > 4. C HANNELS
2.1.4.1
CONTROL
VEH
PED
VEH OVL
PED OVL
CHANNEL SET-UP MENU PG 1of 2
1
2
3
4
5
6
7
8
X
X
X
X
X
X
X
X
SOURCE
1
2
3
4
5
6
7
8
PHASE(1..16)/V OVL(1.32)/P OVL(1..16)
1
2
3
4
5
6
7
8
DIMMING:
GREEN
YELLOW
RED
ALT1/2
Figure 66 – Channels Screen (Page 1)
The four rows below the CONTROL row are used to indicate which type of connection is
set on that channel. A channel can either be a vehicle phase (VEH), a pedestrian phase
(PED), a vehicle overlap, (VEH OVL or V OVL) or a pedestrian overlap (PED OVL or P
OVL).
Use the
button to switch to the assignments screen for channels 9 through 16.
The bottom four rows of this screen are used to define how signal dimming works for this
intersection. These settings can be used to tell the controller whether to dim the green,
yellow, and/or red signals for a particular phase, and whether or not to use the ALT ½
power balancing feature when using dimming on a particular phase.
Note
As of GreenWave v3.8, Dimming of outputs is not yet a functioning
option in the ATC controllers.
Caution
88
Dimming should NOT be used with LED signal heads. It is only
appropriate for use with incandenscent light bulbs.
2.1.4.2
CONTROL
VEH
PED
VEH OVL
PED OVL
CHANNEL SET-UP MENU PG 2of 2
9 10 11 12 13 14 15 16
X
X
X
X
X
X
X
X
SOURCE
9 10 11 12 13 14 15 16
PHASE(1..16)/VEH OVL(1..4)/PED OVL(1..8)
1
2
3
4
2
4
6
8
DIMMING:
GREEN
YELLOW
RED
ALT1/2
Figure 67 – Channels Screen (Page 2)
The programming shown in Figure 66 and Figure 67 are for a sixteen (16) load switch
cabinet. This example shows eight vehicle phases assigned to loadswitches 1 through 8,
respectively, the four vehicle overlaps 1 through 4 assigned to load switches 9 through
12, respectively, and four pedestrian outputs (2, 4, 6 and 8), assigned to load switches
13 through 16, respectively.
Note
If the back panel of a TS2 Type 2 cabinet is not wired for the selected channels,
then I/O Mapping must be employed to get the ATC to send the correct signals
out the desired pins. In a TS2 Type 1 cabinet, on the other hand, the selected
channels will route signals as programmed without any further I/O mapping
required.
89
Comms and I/O Setup Menu
The Comms and I/O Setup menu is used to configure the communications ports, assign
cabinet and IP addresses, map inputs and outputs, and permit remote IP assignments.
M AIN M ENU > 2. P ROGRAMMING > 1. U NIT C ONFIGURATION > 5. C OMMS
S ETUP M ENU
2.1.5
AND
I/O
COMMS AND I/O SETUP MENU
1. PORT 1
2. PORT 2-5 PARAMETERS
3. IP/CABINET ADDRESS
4. I/O MAPPING
5. DHCP Setup
6. PROCESS CONTROL
7. INTERNATIONAL LOAD SWITCH MENU
Figure 68 – Comms and I/O Setup Menu
The Port 1 option gives you the controls to the port normally used for TS2 Type 1
connections, namely for connecting to the cabinet BIUs and MMU. (See page 91.)
The ports 2 through 5 settings are more for general serial connections, including a port 3
that may be available on an add-on comms module. The settings on these screens are
for general serial connection settings, such as baud rate, parity, flow control, etc. These
ports are often used for conflict monitors, UPS or power management data lines, or
external modems. (See page 92.)
The IP/Cabinet settings are used to configure the operation of the ethernet ports on the
controller. (See page 93.)
I/O Mapping is used to view and define input/output pin mappings on the controller’s I/O
ports and also to any BIUs that may be attached in a TS2 Type 1 cabinet. (See page 95
for details.)
DHCP Setup is used to allow the controller to dynamically request and be assigned IP
addresses by a DHCP server on your network for either of its Ethernet ports. (See page
106.)
The Process Control screens are used to monitor and configure individual processes (or
applications) running under the controller’s Linux operating system, including the ports
assigned for use with each. (See page 107.)
The International Load Swith Menu provides a full set of options to configure an ATC
controller to operate in an international traffic control cabinet. (Refer to page 112.)
90
Port 1
Option 1 opens a screen to edit the settings for communications port 1, the SDLC port.
S ETUP M ENU > 1. P ORT 1
2.1.5.1
PORT 1
1
TERM & FACILS.....
AND
I/O
PG1OF1
2
BIU NUMBER
3 4 5 6
7
8
9 10 11 12 13 14 15 16
DETECTOR RACK.....
DETECTOR DIAG.....
MMU ENABLE........X
Figure 69 – Port 1 Setup Screen
A TS2-type controller communicates to cabinet components through Port 1. Place an “X”
under the components (BIUs and MMU) that the ATC needs to communicate with. A
TS2, Type 1 cabinet will use one or more Terminal & Facilities (T&F) BIUs along with an
MMU. Terminal and Facilities BIUs connect to signal heads, preemption inputs, etc. in
the cabinet. Detector BIUs are optional. A TS2 Type 2 cabinet will not use T&F BIUs,
however the use of detector BIUs and MMU are optional.
T e r m & F a c i l s — These eight checkboxes indicate whether or not each numbered
T&F BIU is present.
D e t e c t o r R a c k — BIUs 9 through 16 are typically sometimes used to connect to the
detector inputs and outputs of the cabinet. These checkboxes indicate whether each
numbered BIU is present or not in the cabinet.
D e t e c t o r D i a g — These switches on each of the detector BIU channels indicate
whether or not to process alarm information from the detector BIUs. These alarms are
distinct from the internal detector alarms that the controller performs on detectors that
are connected directly to the controller. These BIU alarms are generated by logic within
the BIUs. These flags tell the controller that such logic is available on a particular BIU
channel. There are four possible reported BIU detector alarms, reported on the Detector
Status screens (1.1.5, refer to page 60) on the RALARM row:
1 = Watchdog Fault, displayed as ‘W’
2 = Open Loop Fault, displayed as ‘L’
3 = Shorted Loop Fault, displayed as ‘S’
4 = Excessive Change Fault, displayed as ‘E’
These errors follow the NEMA Para. 6.5.2.26.3 Channel Status Message standard for
detector unit failure (Watchdog), open loop, shorted loop, and excessive inductance
change faults.
91
MMU Enable — In a TS2 Type 2 cabinet, there usually aren’t any BIUs involved, so Port
1 is typically used to connect the controller to the MMU. In that case, the MMU ENABLE
option is set to ON (‘X’). But if BIUs will be used with the controller, one should disable
the MMU on this port and define which BIUs will be used for which Terminals and
Facilities connection, and which BIUs will be used by each detector rack.
Note that communications between a controller and the cabinet BIUs is handled using
predefined data ‘frames’, as specified in the NEMA TS2-2003 Standard document,
Section 3.3.1.4.1.15.
Port 2-5 Parameters Screen
Option 2 on the Comms and I/O Setup menu shows the Port 2-5 Parameters screen,
where the communications settings for Ports 2 through 7 can be viewed or modified.
S ETUP M ENU > 2. P ORT 2-5
2.1.5.2
AND
I/O
PORT 2-5 PARAMETERS
PORT
ENABLED
2 3 4 5
0 1 0 0
[SP3,SP1,SP4,SP2]
0=DISABLED 1=ENABLED
PARITY
0 0 0 0
0=NONE,1=ODD,2=EVEN
STOP BITS 0 1 0 0
BAUD RATE 0 1 0 0
1= 1200,2= 4800
3= 9600,4= 19200
5=38400,6=57600,7=115200
HW FLOW
0 0 0 0 0=NONE,1=HW FLOW
HDLC Group Address: 1
Figure 70 – Ports 2 through 5 Setup Screen
The Parity, Stop Bits, Handshaking mode, and Baud Rate settings for each of the ports
are defined in the columns below the port numbers. Baud rate is set by entering a onedigit number in the Baud Rate row of the port’s column, using the values shown to the
right in the Baud Rate key. The values shown in Figure 70 shows the programming
required to operate an FSK modem in the Port 3 slot of the controller. (For clarity in this
example, the other ports are shown disabled.)
HDLC Group Address – The HDLC address is the physical network address for an
NTCIP device on a network. This is similar to the “Intersection ID” number for TS 1 and
non-NTCIP TS 2 controllers. The HDLC Group Address is used if Central needs to send
a “broadcast” message to more than one controller at a time. Group addresses range
from 1 to 8191. Address 63 is reserved as an “all stations” address. A group address 63
message will always be transmitted as a single byte with all bits set. A message
received with a Group Address of 63 will force the controller to respond, regardless of its
actual Group Address setting. Conversely, if the controller’s Physical Address is set to
be 63, then it will accept any incoming message regardless of how it is addressed. A
physical address setting of 63 is typically used for testing purposes and should not be
implemented in an active intersection, as communication collisions are likely to occur.
92
IP/CAB Address Setup Screen
This screen is used to set the cabinet address, the hard-coded Ethernet port and
gateway addresses, and subnet mask values for both the System and Local Etherent
ports. Note that dynamically configured Ethernet settings are not configured here, but on
the DHCP Setup screen, which can be found up one level on the Comms and I/O Setup
menu.
S ETUP M ENU > 3. IP/C ABINET A DDRESS
2.1.5.3
AND
I/O
IP/CAB ADDR SETUP
Cabinet Address: 3CC6
IP Address SYSTEM: 128.002.060.198
IP Address LOCAL : 010.247.001.002
SubNetAddr SYSTEM: 255.255.000.000
SubNetAddr LOCAL : 255.255.000.000
Reboot required for the following items:
Gateway
Gateway
SYSTEM: 128.002.002.002
LOCAL : 000.000.000.000
SNMP Port: 00000
Figure 71 – IP/CAB Address setup screen
Cabinet Address – This is a four digit hexadecimal number that can be typed in using
the hex keypad on the front of the controller. This four digit number is used to address
the ATC whenever the IP address is not. When in Edit Mode, if the Cabinet Address is
changed and saved by coming out of Edit Mode, the last two octets of the System IP
Address will change to match. The converse will also change the Cabinet Address. The
Cabinet Address must match to transfer databases by USB.
IP Address SYSTEM – This is where you can set the IP Address for the ‘System’
Ethernet port. This port is typically used to connect the controller to an NTCIP central
system, such as IQ Central or TranSuite. Note that changing the last two numbers of this
address will automatically change the Cabinet Address (above) to a matching value
displayed in hexidecimal format.
IP Address LOCAL – Used to set the IP address for the ‘Local’ Ethernet port. This port
is often used to connect a laptop while next to the cabinet, for use with ATCLink, or for a
telnet or SSH connection to the device.
S u b N e t Ad d r S Y S T E M – The subnet mask that will be used on all Ethernet ports
located on the controller’s ‘system’ Ethernet hub. For most ATC controllers, this is just
the single ‘System’ port. If the subnet mask lists 255 in an octet, that same octet at the
central system must be identical. If the subnet address is programmed as in Figure 71,
the first two octets of the Central System and ATC’s IP address must be identical. Any
part of the IP address that isn’t masked by a subnet mask must be unique to avoid
transmission collisions.
S u b N e t Ad d r L O C AL – The subnet mask that will be used on all Ethernet ports
located on the controller’s ‘local’ Ethernet hub. For most ATC controllers, this is just the
single ‘Local’ port.
93
G a t ew a y S Y S T E M – The address of an Ethernet Gateway server, if one is used on
your network, on the network visible to the ports on the System hub of the ATC
controller. This is the path for one network to connect to another. For most ATC
controllers, this is just the single ‘System’ port. If Dynamic Host Configuration Protocol
(DHCP) is enabled, then this Gateway is the address of the DHCP server network used
to connect the NTCIP central system network through the DHCP server to the ATC.
G a t ew a y L O C AL – The address of an Ethernet Gateway server, if one is used on
your network, on the network that is visible to the ports on the Local hub of the ATC
controller. For most ATC controllers, this is just the single ‘Local’ port.
S N M P P o r t – The Ethernet port number on which the controller will listen for NTCIP
SNMP messages through the system and local ethernet interfaces. Simple Network
Management Protocol Port is an Internet-standard protocol Port that the ATC listens to
for both IP Addresses. When set to a value of 0, port 00161 will be used automatically. If
a non-standard SNMP Port number is desired, enter that Port number in five digits.
Note
94
For ATC controllers with more than two physical RJ-45 Ethernet
connectors, such as the ATC-2000’s four connectors, the ATC standard
only defines two Ethernet hubs, a System hub and a Local hub, as
indicated by the parameters on this screen. With more than two
connectors, these two hubs are merely mapped to the additional
connectors. For example, the ATC-2000 has two connectors on the
System hub (the left two connectors), and two on the Local hub (the right
two connectors.)
I/O Mapping
Each of the seven available I/O modules for the ATC-1000 controller has a defined set
of pin assignments. These assignments determine how the inputs and outputs of the
controller will be routed to individual pins on the various connectors of the I/O modules.
For each of the module types, there is a default set of pin assignments.
Note
For the TS/2 Type 1, this is actually a default set of pin assignments for
the cabinet Bus Interface Units (BIUs), as fed to the cabinet through the
controller’s Port 1, SDLC connector. The TS/2 Type 1 standard calls for
digital output of the controller outputs through Port 1, that are then
routed to physical pins located on external devices (the BIUs). This is
per the NEMA TS2-2003 standard, Para. 5.3.1.4.2.
I/O Mapping is a powerful tool that allows these assignments to be modified and/or
rerouted by programming. Please note that in v3.7 and earlier versions of GreenWave,
the I/O mapping functions were hosted on a set of submenus under an I/O Mapping
menu. In GreenWave v3.8, all of those functions have been moved directly to a set of
I/O Cabinet Setup screens in place of the old menu.
S ETUP M ENU > 4. I/O M APPING
AND
I/O
2.1.5.4 I/O CABINET SETUP
PG1OF5
Type.TS2 Type1(1)
Map Cmd.default(0)
DEV.TF BIU 1 (Active)
01-OUTPUT 1 : Load SW 1 Red Driver [O]
02-OUTPUT 2 : Load SW 1 Yel Driver [O]
03-OUTPUT 3 : Load SW 1 Grn Driver [O]
10-OUTPUT 10: Load SW 4 Red Driver [O]
11-OUTPUT 11: Load SW 4 Yel Driver [O]
[ENT] SET PIN FUNCTION [A] Select Dev
[C] Clear DEV Map [D] Load Dev Default
Figure 72 – I/O Cabinet Setup Screen
Type – The type of I/O module hardware to map against.
Map Cmd – Whether the mapping is currently set to the default values or an alternate
mapping for this I/O type and device.
DEV – The device being mapped, namely a BIU or a controller connector.
Pin Assignments (Table) – Several screens of pin assignment values, the length of the
table depending on the number of pins available on the selected device. Use the
and
buttons to switch between the screens. Use the
switch between individual pin assignment rows. Use the
assignment row and open the Function Selection screens.
and
buttons to
button to select a pin
95
Details About Programming I/O Mapping
This multi-purpose screen starts with the selection of any of the seven I/O Module types.
First, place the controller into Edit Mode.The flashing cursor will pulse to the right of
Type., and reveal the Module Type that was installed in the ATC at the last power up.
Press the
Button to cycle through the preset options that are available, as shown in
Table 14 and Table 15.
Table 14 – Module Type options
Number
1
2
3
4
5
6
7
0
Module Type
TS2 Type 1
TS2 Type 2
HMC
LMD 40
ASTC 6 channel
ASTC 12 channel
International controller
Other mapping
The selection you make for Module Type will determine what default mapping values will
be shown in the table below it. This value will be set automatically to the correct value if
you install a different type of I/O module into the controller, but you can also go in and
change this setting manually. The ability to change this value provides flexibility to the
end-user should a rare occasion arise where a TS2 Type 2 equipped ATC is needed as
a temporary replacement in a TS2 Type 1 Cabinet. TS2 Type 1 can be selected and
power cycled. It will now operate as a TS2 Type 1 ATC.
Note
If an operator changes the module type to a type that does not match the actual
physical hardware that is installed within the controller, the firmware will accept
the change. However, the next time the controller is restarted, the boot check
functions will notice this mismatch and report a “Hardware / Software Type
Mismatch” error. This halts the startup process at the check screen. To proceed
past these screens to access the rest of the interface, you will need to enter a
special key sequence:
However, doing so will load the default I/O map for the connected device and all
I/O map data will be lost.
After the I/O module Type has been selected, the next option is to select whether to use
the default or an alternate mapping. The selection of which of the I/O mappings to use is
done by choosing the Map Command (Map Cmd) value. Use the
navigate to that field on the screen.
button to
The standard values for Map Cmd are listed in Table 15. The alternate map can be
defined in IQ Central, in ATC-Link, or here on the front panel display. The Default (0)
setting will automatically change to AltMap(1) as soon as any I/O Mapping change is
saved.
96
Table 15 – Map Commands
Number
0
1
Caution
Mapping Set
Default Map
I/O Alternate Map 1
If the MMU LCD or LEDs are not showing the saved channels from the
Channel Set-Up menu (MM.2.1.4.1), then the mapping within the
controller has NOT occurred. If this happens, check the I/O Mapping
screen to see if Map Cmd is set to AltMap(1). If it is, edit it to show
default (0) and then cycle the controller’s power.
I/O mapping for a TS2 Type 1 module is rarely required. Channel assignments of vehicle
phases, pedestrian phases, vehicle overlaps and pedestrian overlaps are defined on the
Channel Setup Scree (MM.2.1.4.1/2). The channel assignments for these same
functions are output to the specific load switches by BIUs 1 and 2, based on their
channel programming. An example of I/O Mapping required for Transit Signal Priority
(TSP) operation using a TS2 Type1 I/O Module will be explained in “X” on page Y.
Mapping Example #1: TSP I/O Using a TS2 Type 1 Module
This example continues from the previous discussion of the I/O Mapping setup screen.
With the Type set to TS2 Type 1(1) and the Map Cmd value still set to default(0), follow
these steps to program necessary inputs and outputs for TSP operation.
PG1OF5
Type.TS2 Type1(1)
Map Cmd.default(0)
DEV.TF BIU 1 (Active)
10-OUTPUT 10: Load SW 4 Red Driver [O]
11-OUTPUT 11: Load SW 4 Yel Driver [O]
Figure 73 – Example I/O Cabinet Setup screen for TSP mapping
The third line from the top the I/O Cabinet Setup screen (Figure 72) identifies the device
and its status. With the cursor still flashing Map Cmd. default(0), press the
button to
switch between the available mappable devices (BIUs and connectors). For example the
Dev. value may change from TF BIU 1 (Active) to TF BIU 2 (Active). If the device is
listed as (Inactive), it is not enabled on the PORT 1 Screen (MM.2.1.5.1). Press the [A]
button one more time to display TF BIU 3 (Active), as shown below.
Pressing
repeatedly will cycle through the full list of available devices and back to
the beginning.
97
PG1OF5
Type.TS2 Type1(1)
Map Cmd.default(0)
DEV.TF BIU 3(Active)
01-OUTPUT 1 : Timing Plan a
[O]*
02-OUTPUT 2 : Timing Plan b
[O]
03-OUTPUT 3 : Timing Plan C
[O]
04-OUTPUT 4 : Timing Plan d
[O]
05-OUTPUT 5 : Offset a
[O]
06-OUTPUT 6 : Offset b
[O]
07-OUTPUT 7 : Offset c
[O]
08-OUTPUT 8 : Auto Flash Status
[O]
09-OUTPUT 9 : Sys Special Func 1
[O]
10-OUTPUT 10: Sys Special Func 2
[O]
[O]
Figure 74 – I/O Cabinet Setup Screen after selecting a new device
For a TS2 Type 1 I/O module, the first available (i.e. unassigned by default) input to map
to is the combination function Terminal 16, located on Page 2 of 5, on TF BIU 3. Press
the
button once to reveal Page 2 of 5. When you first open this screen, it should
look like this:
PG2OF5
Type.TS2 Type1(1)
Map Cmd.default(0)
[O]*
13-OUTPUT 13: Not Assigned
[O]
[O]
[O]
16-IN&OUT 1 : Ring 1 Status Bit a [O]
17-IN&OUT 2 : Ring 1 Status Bit b [O]
18-IN&OUT 3 : Ring 1 Status Bit c [O]
22-IN&OUT 7 : Ring 1 Red Rest
[O]
Figure 75 – I/O Cabinet Setup Screen
Notice that the Edit Mode cursor, the asterisk (‘*’), is visible to the right of the first row of
pin assignments on this page: 12-OUTPUT 12: Sys Special Func 4 [O]*.
Use the
button to move the cursor down to the fifth row of the table: the output at
Terminal 16. The symbol [O] on these screens indicates the function is currently
assigned to be an output. The symbol [I] indicates the function is an input. The symbol
[X] indicates the function is not assigned. Some functions with an [X] symbol cannot be
reassigned. An attempt to do so will result in an NTCIP Consistancy Check error
message.
With the cursor in the proper place next to Terminal 16 on BIU 3, press the
to set a new function for this pin. The I/O Function Select screen will appear.
98
button
I/O FUNCTION SELECT SCREEN
Not Assigned
Address Select
Address Select
Address Select
Address Select
Det Reset Slot
Det Reset Slot
Det Reset Slot
Det Reset Slot
Det Reset Slot
Det Reset Slot
Det Reset Slot
0
1
2
3
1&2
3&4
5&6
7&8
9&10
11&12
13&14
(~) ARE ASSIGNED
PG01of63 E
[X]*
[0]
[0]
[0]
[0]
[O]
[O]
[O]
[O]
[O]
[O]
[O]
[HLP] HELP SCREEN
Figure 76 – Available I/O Functions list
Press the
on this page.
utton repeatedly to get to Page 56 of 63. The TSP detector inputs start
Ring 1 Red Rest
Ring 2 Red Rest
Ring 3 Red Rest
Ring 4 Red Rest
Ring 1 Stop Time
Ring 2 Stop Time
Ring 3 Stop Time
Ring 4 Stop Time
SW Time Source
TSP Det 1
TSP Det 2
TSP Det 3
(~) ARE ASSIGNED
PG056of63 E
[I]~
[I]~
[I]
[I]
[I]~
[I]~
[I]
[I]
[I]
[I]*
[I]
[I]
[HLP] HELP SCREEN
Figure 77 – Page 56 of the I/O Functions list
Press
to move the cursor to the right of TSP Det 1 [I], and press the
button
again. This selects the new function and saves it to BIU 3 pin 16. At the same time, this
will return the screen back to the original TF BIU 3 Screen, showing the Terminal 16
position.
99
PG2OF5
Type.TS2 Type1(1)
Map Cmd.AltMap(1)
[O]
[O]
[O]
[O]
16-IN&OUT 1 : TSP Det 1
[I]*
22-IN&OUT 7 : Ring 1 Red Rest
[O]
Figure 78 – I/O Cabinet Setup Screen with new TSP Det 1 pin assignment
Repeat this procedure until all twenty-four TSP detectors have been reassigned to
terminals 16 through 39 on BIU 3. Save this I/O mapping by exiting from Edit mode. The
cursors will stop flashing and the Map Cmd. value will change to AltMap(1). The
procedure is complete. TSP Detector inputs can now be wired to TF BIU 3 Terminals 16
to 39, and properly programmed TSP Runs will respond to them.
Note
Detector BIUs 1-4 can be mapped using the same procedures as T&F BIUs 1-4.
This completes I/O Mapping example #1.
100
Mapping Example #2: Limited Load Switches in a TS2 Type 2 Cabinet
Another common use for I/O Mapping is in TS2 Type 2 (TS1) cabinets that have a
limited number of load switches. This example maps overlap 1 to unused load switch #3.
To accomplish this task, select:
S ETUP M ENU > 4. I/O M APPING
AND
I/O
Enter the Edit Mode with the
-E. Press
once to change the selected device
(connector). Press the A button until the Dev. field shows the MS B Connector.
2.1.5.4 I/O CABINET SETUP PG1OF5 E
Type.TS2 TYPE2(2)
Map Cmd.default(0)
DEV.TS2 MSB CONN (Active)
MSB-A
: Phase next_1
[0]
MSB-B
: Not Assigned
[X]
MSB-C
: Phase Next_2
[0]
MSB-D
: Phase 3 Grn Driver
[O]*
MSB-E
: Phase 3 Yel Driver
[O]
MSB-F
: Phase 3 Red Driver
[O]
MSB-G
[O]
MSB-H
: Phase 3 Ped Clr Drvr [O]
MSB-J
: Phase 3 DWLK Driver [O]
MSB-K
: Phase Check 4
[O]
MSB-L
: Det Channel 4 Call
[I]
[ENT] Set PIN Function [A] Select Dev
[C] Clear Dev Map [D] Load Dev Default
Figure 79 – Example remapping showing MSB connector
Use
to move the cursor (*) down to the MSB-D pin: Phase 3 Grn Driver, as shown
in Figure 79.
Press
to open the I/O Function Select screen.
E
Not Assigned
Address Select
Address Select
Address Select
Address Select
Det Reset Slot
Det Reset Slot
Det Reset Slot
Det Reset Slot
Det Reset Slot
Det Reset Slot
Det Reset Slot
0
1
2
3
1&2
3&4
5&6
7&8
9&10
11&12
13&14
(~) ARE ASSIGNED
PG01of41
[X]*
[0]
[0]
[0]
[0]
[O]
[O]
[O]
[O]
[O]
[O]
[O]
[HLP] HELP SCREEN
Figure 80 – Available I/O Functions list
Page down (
) until the page 29 is displayed.
101
E
Ovlp
Ovlp
Ovlp
Ovlp
Ovlp
Ovlp
Ovlp
Ovlp
Ovlp
Ovlp
Ovlp
Ovlp
30DD Yel Driver
31EE Yel Driver
32FF Yel Driver
1a Grn Driver
2b Grn Driver
3c Grn Driver
4d Grn Driver
5e Grn Driver
6f Grn Driver
7g Grn Driver
8h Grn Driver
9i Grn Driver
(~) ARE ASSIGNED
PG29of41
[O]
[0]
[O]
[0]*
[O]~
[0]~
[O]~
[0]
[O]
[0]
[O]
[O]
[HLP] HELP SCREEN
Figure 81 – Available I/O Functions list – page 2
Press
to move the cursor down so that it is to the right of Overlap 1a Grn Driver.
Press
so that the Overlap 1a Grn Driver function is assigned to pin MSB-D.
Type.TS2 TYPE2(2)
Map Cmd.default(0)
DEV.TS2 MSB CONN (Active)
MSB-A
: Phase next_1
[0]
MSB-B
: Not Assigned
[X]
MSB-C
: Phase Next_2
[0]
MSB-D
: Ovlp 1a Grn Driver
[O]*
MSB-E
: Phase 3 Yel Driver
[O]
MSB-F
[O]
MSB-G
[O]
MSB-H
MSB-J
MSB-K
: Phase Check 4
[O]
MSB-L
[I]
Figure 82 – Example of Overlap Green Driver remapped to MSB connector
Repeat this procedure to map the Yellow and Red overlap drivers to MSB-E and MSB-F,
respectively.
When finished, exit from Edit mode to save the changes. The Overlap 1a outputs will
now come out on Load Switch 3.
This completes I/O mapping example #2.
102
Mapping Example #3: ‘D’ Module I/O Mapping
TS2 Type 2 I/O modules are likely to be installed in ATCs along with proprietary ‘D’
modules. The options include the legacy 3000E Closed Loop/Preemption/Auxillary D
module, the MultiSonics 820A D module, the Traconex 390 D, and the LMD 9200
CPC/Sub D module.
Start by navigating to the I/O Mapping screen: (MM.2.1.5.4)
Type.TS2 TYPE2(2)
Map Cmd.default(0)
DEV.TS2 MSA CONN (Active)
MSA-A
: Fault Monitor
[0]*
MSA-B
: DC+ (24V)
[X]
MSA-C
: Voltage Monitor
[0]
MSA-D
[O]
MSA-E
MSA-F
[O]
MSA-G
MSA-H
MSA-J
: Phase 2 Walk Driver [O]
MSA-K
[I]
MSA-L
: Pedestrian Det 2
[I]
Figure 83 – Beginnning the D Module I/O mapping process
To start mapping the D Module connector, enter Edit mode using the
key
combination. The flashing cursor will pulse to the right of Type., showing a value of TS2
Type2(2) Module, which was the module installed in the ATC at the last power up.
The first available connector will appear in the DEV field. For a TS2 Type 2 controller,
this will be the TS2 MSA connector, as displayed above. Press the
button until the
‘D’ Module appropriate to your unit is selected. In this example, we’ll map to the 3000E
D module, which is called the DTYPE CLOOP COOR device in the GreenWave
interface. Here, we will map a TOD Special Function, which is an NTCIP term for a userdefined output, to a legacy 3000 Series D module MS coord pin.
Type.TS2 TYPE2(2)
Map Cmd.default(0)
DEV.DTYPE CLOOP COOR (Active)
COOR-A
: Det Channel 17 Call [I]
COOR-B
COOR-G
COOR-H
COOR-J
COOR-K
COOR-L
COOR-M
COOR-P
: Not Assigned
[X]*
COOR-R
: Not Assigned
[X]
COOR-S
Figure 84 – Selecting a D module pin for remapping
103
If assigned functions do not appear to the right of COORD Pins A through S, check that
the DTYPE CLOOP COORD status is (Active). If it is not, check the ‘D’ Module for
proper installation and cycle the power on the controller. If the status is (Active) and the
functions still do not appear, press
Caution
Using the
to Load Device Default functions.
button to load device defaults will overwrite any previous
I/O mapping work that has been performed on this connector’s pin
assignments. However, it will not overwrite any customizations that have
been done on any of the other connectors on your controller.
Press the
button to move the cursor down to the right of the first Not Assigned
function, which in our example is the COOR-P pin.
Press the
button to open the I/O Function Select screen.
Not Assigned
Address Bit 1
Address Bit 2
Address Bit 3
Address Bit 4
Address Bit Parity
Det Channel 1 Call
Det Channel 2 Call
Det Channel 3 Call
Det Channel 4 Call
Det Channel 5 Call
Det Channel 6 Call
(~) ARE ASSIGNED
PG01of22 E
[X]*
[I]
[I]
[I]
[I]
[I]
[I]~
[I]~
[I]~
[I]~
[I]~
[I]~
Note that a tilde (‘~’) appears
next to every function that is
already asigned to a pin
[HLP] HELP SCREEN
Figure 85 – Opening the I/O Functions list
Page down (
) to page 18 of 22.
TSP Det 22
TSP Det 23
TSP Det 24
Sys Special Func 1
Sys Special Func 2
Sys Special Func 3
Sys Special Func 4
Sys Special Func 5
Sys Special Func 6
Sys Special Func 7
Sys Special Func 8
Indicator Lamp Ctrl1
(~) ARE ASSIGNED
PG18of22 E
[I]*
[I]
[I]
[I]~
[I]~
[I]~
[I]~
[I]~
[I]~
[I]
[I]
[I]~
[HLP] HELP SCREEN
Figure 86 – Page 18 of the I/O Functions list
104
Press the
button several times to move the cursor down to the first System Special
Function that hasn’t been assigned to a pin. In this case, we choose Sys Special Func
7.
Press
to assign the new function.
This remaps System Special Function 7 to pin P on the Closed-loop, Coord D module.
This assignment of the TOD Special Function (User Defined Output), is shown below.
2.1.5.4 I/O CABINET SETUP PG1OF5
Type.TS2 TYPE2(2)
Map Cmd.AltMap(1)
DEV.DTYPE CLOOP COOR (Active)
COOR-A
COOR-B
COOR-G
COOR-H
COOR-J
COOR-K
COOR-L
COOR-M
COOR-P
: Sys Special Func 7 [I]
COOR-R
: Not Assigned
[X]
COOR-S
Figure 87 – Example remapping of a pin on the D module
Save this I/O Mapping by exiting from Edit mode. (
flashing and the Map Cmd. will change to AltMap(1).
) The cursors will stop
This completes I/O Mapping example #3.
105
DHCP Setup Screen
This screen is used to set up a DHCP server connection for the controller. DHCP, or the
Dynamic Host Configuration Protocol, is an Ethernet protocol used to allow devices to
request and receive network identifying information automatically from a server over the
network, including their IP address, subnet mask and gateway. Upon power up or
connection to an Ethernet network, if DHCP is enabled, the controller will sends out a
broadcast query asking for its network information from any DHCP server that may be
listening. DHCP discovery and assignment uses two ports: UDP port 67 for sending data
to the server and UDP port 68 for data coming to the controller. A broadcast is sent out
over the local physical subnet.
M AIN M ENU > 2.P ROGRAMMING > 1.U NIT C ONFIGURATION > 5.C OMMS
S ETUP M ENU > 5.DHCP S ETUP
2.1.5.5
AND
I/O
IP/CAB ADDR SETUP
Current SYSTEM IP
Current Local IP
: 128.002.060.198
: 192.168.060.199
Current System Subnet
Current Local Subnet
: 255.240.000.000
: 255.240.000.000
Current System Gateway : 128.002.002.002
Current Local Gateway : 000.000.000.000
DHCP Enable:
SYSTEM( )
LOCAL( )
Figure 88 – DHCP Setup screen
The top six lines on this screen show the settings that have been assigned to this
controller by a DHCP server, or if DHCP is disabled, that was assigned on the
controller’s own IP/Cabinet Address screen. (Screen 2.1.5.3, refer to page 93.)
The only parameters on this screen that can be edited are the two DHCP Enable flags.
There are separate flags for the System and Local ethernet hubs of the controller to
allow dynamic addressing to be used on either or both of the Ethernet ports.
Use the
and
keys to toggle the enable flags ON and OFF. An ‘X’ indicates that
DHCP is enabled on that hub.
106
Process Control Screen
The ATC controllers run the Linux operating system and are capable of running multiple
processes at the same time. The Process Control screens (one for each running
process) are used to manage how these processes start up, are maintained, and use
controller ports.
Functionally, this screen is mainly used to program an ATC to replace a Peek 3000
Series or LMD controller in a closed loop system that is being managed by an M3000/E
master. It can also be used to configure an ATC controller to completely replace both the
3000 controller and the M3000/E master in such a closed loop system.
M AIN M ENU > 2.P ROGRAMMING > 1.U NIT C ONFIGURATION > 5.C OMMS
S ETUP M ENU > 6.P ROCESS C ONTROL
2.1.5.6 PROCESS CONTROL
AND
I/O
PG 1 OF 4
Process [NTCIP]
Control.................Auto-Restart (2)
Status..................1-Running
Ethernet Comms Enable...1
Command Process Restart.0
Port Assigned Processes
Port Process
Status
----------------------------------------(2) NTCIP (1)
1 – NTCIP
(3) NTCIP (1)
1 – NTCIP
(4) SHELL (4)
4 – SHELL
(5) Not Assigned (0) 0 – Not Assigned
Figure 89 – Process Control screen
In GreenWave v3.8, Process Control consists of four pages. Each page controls a
specific type of communications protocol or process. Page 1 of 4 is the default ATC
communication NTCIP protocol. The ATC was designed to be completely NTCIP
compliant.
Legacy users of Peek equipment may have the need to temporarily place an ATC into a
Peek closed loop system as a start toward a system upgrade. Page 2 is a proprietary
Peek protocol used by the M3000/E master to communicate with 3000 Series
controllers. The process is called MIZBAT Master.
Page 3 is another proprietary Peek protocol called MIZBAT client. MIZBAT client is used
by a 3000 Series controller when it’s being managed by an M3000/E master to form a
closed loop system.
Page 4 is a Shell process. A shell is a command line interface normally assigned to a
serial port.
107
Replacing a 3000E with an ATC in an M3000 Closed Loop System
To replace a 3000 Series Controller with an ATC in a Closed Loop System, follow these
steps:
1.
Install the desired 3000E Communications Card (Fiber Optic or DSP Modem) into
Port 3 of the ATC. Set the appropriate jumper on the Communications Card to
‘LOCAL’.
2.
Program the ATC’s Port 3 communication parameters on Screen 2.1.5.2 to match
the existing Closed Loop System parameters.
3.
Press
4.
Enter Edit mode by pressing
5.
Use the green arrow buttons to move the cursor to the Control line and press
twice to switch to page 3, for the MIZBAT Client Process page.
,
.
until Don’t Start (0) is the parameter value.
6.
Press
to move the cursor down to the bottom portion of the screen. Go to
Port Process (3). Press the
button until Not Assigned (0) is selected.
7.
Exit from Edit mode by pressing
,
8.
Power down the ATC waiting until all six green LEDs go out, and then reapply
power.
9.
Navigate back to Screen 2.1.5.6, Page 3 of 4. The Screen should confirm the Port
3 Status as 0-Not Assigned.
again, which will save the changes.
PG 3 OF 4
Process [MIZBAT Client]
Control . . . . . . . . Don’t Start (0)
Status . . . . . . . . 0-Not Running
Ethernet Comms Enable . 0
Port Process
Status
--------------------------------------(2) NTCIP (1)
1 – NTCIP
(4) SHELL (4)
4 – SHELL
Figure 90 – Process Control Setup screen with port 3 Not Assigned
The previous NTCIP Process has been stopped and unassigned on Port 3. This
is a mandatory step before the MIZBAT Client can be started.
10. Place the controller back in to Edit mode. Use the
to the Control line and press
108
button to move the cursor
until Start (1) is selected.
11. Continue to arrow down, moving the cursor to the Port Process for Port 3. Press
until MIZBAT Client (3) is selected.
12. Exit from Edit Mode again to save the changes.
13. The MIZBAT client process should now start up:
PG 3 OF 4
Control . . . . . . . . Start (1)
Status . . . . . . . . 1-Running
Port Process
Status
--------------------------------------(2) NTCIP (1)
1 – NTCIP
(3) MIZBAT Client(3) 3 – MIZBAT Client
(4) SHELL (4)
4 – SHELL
Figure 91 – Process Control Setup screen
14. Navigate to the USTC Misc Menu (MM.2.1.7), and set the MIZBAT Master ID
number to the value stored in the M3000 master controller.
15. Connect the communications cable from the M3000 master to this ATC. At 30
seconds past the next minute, the master will transmit the MIZBAT Set Clock (sc)
command. The ATC’s time should now update to that of the Master.
This completes the 3000E replacement procedure.
Replacing a 3000E or M3000E in a Closed Loop System
To replace an M3000/E Master with an ATC providing time sync pulses in a closed loop
system, follow these steps:
1.
Install the desired 3000E Communications Card (Fiber Optic or DSP Modem) into
Port 3 of the ATC. Set the appropriate jumper on the Communications Card to
‘MASTER.”
2.
Program the ATC’s Port 3 communication parameters on Screen 2.1.5.2 (Port 2-5
Parameters) to match the existing closed loop system parameters.
3.
Back on the Process Control screen (MM.2.1.5.6), use the
to Page 2, so we can edit the MIZBAT Master Process page.
4.
Place the controller into Edit mode, by pressing
5.
Use
to move the cursor to the Control line and press
(0) is selected.
,
button to move
.
until Don’t Start
109
6.
Continue to arrow down, moving the cursor to the Port Process for Port 3. Press
the
until Not Assigned (0) is selected.
7.
Exit from Edit mode, which saves these changes.
8.
Power down the ATC, waiting until all six green LEDs go out. Reapply power.
9.
Navigate back to Screen 2.1.5.6 (Process Control) and page down to Page 2.
The screen should confirm that the Port 3 status is 0-Not Assigned.
PG 2 OF 4
Process [MIZBAT Master]
Control . . . . . . . . Don’t Start (0)
Status . . . . . . . . 0-Not Running
Port Process
Status
--------------------------------------(2) NTCIP (1)
1 – NTCIP
(4) SHELL (4)
4 – SHELL
Figure 92 – Setting Port 3 process to Not Assigned
The previous NTCIP Process has been stopped and unassigned on Port 3. This
is a mandatory requirement before the MIZBAT Master can be started.
10. Press
process.
to page down to page 3, so that we can edit the MIZBAT Client
11. Place the controller into Edit mode (
,
).
12. Use the
button to move the cursor to the Control line and press
Start (1) is selected.
until
13. Continue to arrow down, moving the cursor to the port process for Port (3). Press
the
button until MIZBAT Master (2) is selected.
14. Exit from Edit mode to save your changes.
15. The process should start and and appear as it does in Figure 93.
110
PG 3 OF 4
Control . . . . . . . . Start (1)
Status . . . . . . . . 1-Running
Port Process
Status
----------------------------------------(2) NTCIP (1)
1 – NTCIP
(3) MIZBAT Master(2) 2 – MIZBAT Master
(4) SHELL (4)
4 – SHELL
Figure 93 – Process Control screen showing MIZBAT Client started and running
16. Navigate to the USTC Misc Menu (MM.2.1.7), and save the proper Master ID
Number to the MIZBAT Master ID field. (The master and controller values for this
need to match.)
17. Connect the communications cable from this ATC to the next cabinet’s Peek
controller, and any others downstream that need to receive the same sync clock.
At 30 seconds past the next minute, the ATC will transmit the MIZBAT Set Clock
(sc) command, as if it were an M3000. The time on the downstream controllers
should now update to match that of the ATC.
This completes the process to replace an M3000 closed loop with an ATC providing time
sync pulses.
111
International Load Switch Menu
An international load switch is a self-monitoring device compatible with the international
Ccabinet design cited in the specifications of several countries. This menu provides the
controls to configure an ATC controller to operate with such load switches. Peek is one
of the companies that manufactures these load switches.
S ETUP M ENU > 7. I NTERNATIONAL L OAD S WITCH M ENU
AND
I/O
2.1.5.7 INTERNATIONAL LOAD SWITCH MENU
1. BOARD SETUP
2. BOARD STATUS
3. CURRENT MONITOR CONFIGURATION
4. SHOW CURRENT iRMS VALUES
5. SYNCH TYPE
6. GET / DISPLAY LOGS
7. LSW BOARD ERROR COUNTS
Figure 94 – Internation Load Switch Menu
Figure 95 and Figure 96 show how typical international load switches appear within a
cabinet, and when extracted.
Figure 95 – International load switches in a cabinet rack (green labels optional)
112
Figure 96 – Typical International load switch, side view
Board Setup Screen
Option 1 on the International Load Switch menu is the Board Setup screen, where
individual board slots can be enabled or disabled.
M AIN M ENU > 2. P ROGRAMMING > 1. U NIT C ONFIGURATION > 5. C OMMS AND I/O
S ETUP M ENU > 7. I NTERNATIONAL L OAD S WITCH M ENU > 1.B OARD S ETUP
2.1.5.7.1 Load Switch Board Setup
BOARD SLOTS
1
ENABLE. . . . . . X
2
X
3
X
4
X
5
X
6
X
7
8
Figure 97 – Internation Load Switch Board Setup screen
Use the
and
buttons to enable or disable individual slots.
To enable Load Switch Monitoring as discussed in the rest of this section, load switch
monitoring needs to be programmed for each specific slot. To enable an slots, put the
screen into Edit mode and place an ‘X’ under any of the eight board slots that have an
international load switch installed. Exit from Edit mode to save the settings. The
example above matches Figure 95, with six switches installed in the cabinet.
113
Board Status Screen
Using the various screens available under the International Load Switch menu, such
load switches can be configured in manner consistent with the way that conflict monitors
or MMUs are employed in NEMA and 330 type cabinets. The Load Switch Channel
Status Screen is the first of these screens. No editing is needed or allowed on this
screen; this is merely a way to check the status of these load switches.
S ETUP M ENU > 7. I NTERNATIONAL L OAD S WITCH M ENU > 2.B OARD S TATUS
2.1.5.7.2 Load Switch Channel Status
Comm. . . . .OK
BOARD SLOT ..1 of 8
CHANNEL. . . 1 2 3 4 5 6 7 8
ACTIVE . . . x X X X X X X X
IN FAULT . . NO
LO FAULT . . D D D D D D D D
HI FAULT . . D D D D D D D D
DATE 7 TIME.00/00/00 00:00:00
________________________________________
L
H
M
D
=
=
=
=
Low Current Fault
High Current Fault
Current Monitor Confiq Fault
Current Monitor Off
Figure 98 – Internation Load Switch Channel Status screen
There are eight status screens provided here. One load switch slot is detailed on each
screen. To switch between the status screens, use the
and
buttons.
Comm — Shows whether or not the load switch in this slot is communicating.
Channel — These column headers define the eight channels for each load switch, with
status appearing in the rows below.
Active — Indicates whether each channel is active on the load switch. An ‘X’ indicates
that a channel is active.
In Fault — A global flag for the switch which indicates if any electrical current faults
have been detected on the device. This can either be Yes or No.
Lo Fault / Hi Fault — These letter codes indicate if any faults, and what types of faults,
exist on each of the load switch’s channels.
Table 16 – International Load Switch Fault Codes
Code
Meaning
L
Low current detected on this channel
H
High current detected on this channel
M
There is a problem with current monitoring on this channel
D
Current monitoring has been turned off on this channel
Date & Time — The current date and time being reported by the load switch’s internal
clock.
114
Current Monitor Configuration Screen
Each international load switch has eight assignable channels of monitoring. The
channels must be programmed with the minimum and maximum current assignments
based on the number and types of devices attached to that channel. The minimum and
maximum current levels are expressed in milliamps. This is the place to enter those
values.
S ETUP M ENU > 7. I NTERNATIONAL L OAD S WITCH M ENU > 3.C URRENT M ONITOR
C ONFIGURATION
2.1.5.7.3 LSW CURRENT MONITOR CONFIG
BOARD SLOT.. 1 of 8
CHANNEL CURRENT (mA)
MIN
MAX
1. . . . . . . . . . 0000
0000
2. . . . . . . . . . 0000
0000
3. . . . . . . . . . 0000
0000
4. . . . . . . . . . 0000
0000
5. . . . . . . . . . 0000
0000
6. . . . . . . . . . 0000
0000
7. . . . . . . . . . 0000
0000
8. . . . . . . . . . 0000
0000
________________________________________
A VALUE OF 0000 DISABLES MONITORING
Figure 99 – Internation Load Switch LSW Current Monitor configuration
To enter the minimum and maximum current levels, place the ATC into Edit mode. Move
the cursor to the Min or Max value you wish to edit using the
,
,
, and
buttons. Using the number keypad on the front panel of the controller, enter a milliamp
level between 0001-9999 mA. Be sure to enter Min and Max values for each utilized
channel on the Load Switch assigned to this Board Slot. Use the
down through all eight slots.
button to page
When complete, exit from Edit Mode to save all of the changes.
Note
The End-User is responsible to accurately develop the Current budget for each
of the eight utilized channels on each of the eight utilized slots.
115
Show Current iRMS Values Screen
The Current iRMS Values Screen 2.1.5.7.4 is a status display showing the root mean
square (RMS) values of the electrical current (i) measurements for each of the utilized
load switch channels.
S ETUP M ENU > 7. I NTERNATIONAL L OAD S WITCH M ENU > 4.S HOW C URRENT I RMS
V ALUES
2.1.5.7.4 LSW Current iRMS Values
BOARD SLOT.. 1 of 8
CHANNEL CURRENT (mA)
MIN
MAX
1. . . . . . . . . . 0000
0000
2. . . . . . . . . . 0000
0000
3. . . . . . . . . . 0000
0000
4. . . . . . . . . . 0000
0000
5. . . . . . . . . . 0000
0000
6. . . . . . . . . . 0000
0000
7. . . . . . . . . . 0000
0000
8. . . . . . . . . . 0000
0000
_________________________________________
Figure 100 – International iRMS load switch current display
Use the
and
eight board slots.
buttons to switch between the status displays for each of the
Sync Time Function
Option 5 on the International Load Switch menu does not open a status screen or a
parameter screen, but rather immediately triggers an attempt to synchronize the time
stored on all of the load switch boards. A message will be sent to each enabled
international load switch slot to set the real time clock on each board to match the
current time of the ATC’s own clock. The controller will immediately show whether the
attempt succeeded or failed.
S ETUP M ENU > 7. I NTERNATIONAL L OAD S WITCH M ENU > 5.S YNC T IME
AND
I/O
********************************
*
*
* LOAD SWITCH TIME SET
*
*
*
* Status: Succeeded
*
*
*
* Press [ESC] to continue
*
*
*
*
*
********************************
Figure 101 – Interanational load switch time sync response screen
This time synchronization process is done so that current monitoring logs can be
correlated.
116
Get / Display Logs Screen
International load switches automatically generate current monitoring logs. The Get /
Display LSW Logs screen is used to retrieve those logs and view their content on the
controller’s screen.
S ETUP M ENU > 7. I NTERNATIONAL L OAD S WITCH M ENU > 6.G ET / D ISPLAY L OGS
2.1.5.7.6 GET / DISPLAY LSW LOGS
BOARD SLOT ..1 of 8
Log Number ..1 of 0
No Log Entries Available
To navigate through the LSW Logs
Press KEY [A] PREV LOG [B] NEXT LOG
Use number keys to jump to a log
Figure 102 – Get / Display LSW Logs screen
Important
Valid international load switch logs will only be generated once the load
switches have been configured to provide the type of monitoring desired,
using the LSW Current Monitor Configuration screen (MM.2.1.5.7.3)
To retrieve the logs, select the slot containing the load switch to be retrieved. This can
be done by using the
and
buttons to switch between selected board slots.
Once the proper board slot is selected, use the
and
buttons to select which
log number to retrieve or view. To view the next log in order, press
. To view the
previous log in the list, press
. Or, individual log files can be selected by pressing
the numbered button corresponding to the log number.
117
LSW Board Error Counts Screen
Option 7 on the International Load Switch Menu is used to view a listing key counting
statistics about the operation and faults detected on each load switch.
S ETUP M ENU > 7. I NTERNATIONAL L OAD S WITCH M ENU > 7.LSW B OARD E RROR
C OUNTS
2.1.5.7.7 LSW Board Error Counts
BOARD SLOT ..1 of 8
Get / Set Current Confiq
S:00000000 F:0000000 L:0000000 B:0000000
S:00000000 F:0000000 L:0000000 B:0000000
Get LSW Fault Status / Get iRMS Values
S:00000000 F:0000000 L:0000000 B:0000000
S:00000000 F:0000000 L:0000000 B:0000000
Get LSW Log Index & Size
S:00000000 F:0000000 L:0000000 B:0000000
S:00000000 F:0000000 L:0000000 B:0000000
Get LSW Log Data
S:00000000 F:0000000 L:0000000 B:0000000
Set & Get Time
S:00000000 F:0000000 L:0000000 B:0000000
S=Success
B=Bad Data
F=FIO no Resp. L=LSW No Resp.
Figure 103 –Internation load switch errror counts screen
Important
Use the
and
Proper international load switch error counts will only be generated once
the load switches have been configured to provide the type of monitoring
desired, using the LSW Current Monitor Configuration screen
(MM.2.1.5.7.3)
buttons to select the slot for which error count statistics are to be
viewed. Error counts are listed by Get Data and Send Data actions. The four bins in
which activity is recorded use the following letter codes:
Table 17 – LSW board error count codes
Code
118
Meaning
S
Successful action
B
Comms successful, but bad data received
F
Field I/O, no response
L
Load switch, no response
Ring Sequencing Screens
This screen is used to set the order of phases within each ring of a NEMA pattern. There
are 16 screens of ring sequencing available, meaning that the four rings can be
programmed to sequence through their phases in 16 possible sequences. Any of the 16
sequences can then be called from within the Coordinated Pattern tables; each pattern
calls one sequence number. Ring sequences are not called by the Interval-based
patterns.
M AIN M ENU > 2 . P r o g r a m m i n g > 1 . U n i t C o n f i g u r a t i o n > 6 . R i n g
Sequencing
2.1.6.1
RING SEQUENCING
PG 1of16
SEQUENCE NUM 1
RING
1 1 2 3 4 . . . . . . . . . . . .
2 5 6 7 8 . . . . . . . . . . . .
3 . . . . . . . . . . . . . . . .
4 . . . . . . . . . . . . . . . .
Figure 104 – Ring Sequencing Screen (Page 1)
The numbers down the left edge of the screen show the four rings. The numbers to the
right of each ring number shows the order of the phases that will be served during the
ring. For example, the above ring sequence settings will produce the following sequence
of phases:
1/5
2/6
3/7
4/8
and
keys to switch between sequence screens. Each screen defines
Use the
one ring sequence. For example, Ring Sequence number 16 could be defined as:
2.1.6.16
RING SEQUENCING
PG16of16
SEQUENCE NUM 16
RING
1 1 2 3 4 . . . . . . . . . . . .
2 6 5 7 8 . . . . . . . . . . . .
3 . . . . . . . . . . . . . . . .
4 . . . . . . . . . . . . . . . .
Figure 105 – Ring Sequencing Screen (Page 16)
119
The sequence defined in Figure 105 is an example of a Lead/Lag sequence:
1/6
2/6
Note
2/5
3/7
4/8
These settings can be used with the Phase Compatibility programming of
the controller (Screen 2.1.3) to develop any sequence desired.
Using Ring Sequences to Create Concurrency Groups
Specifying a sequence also defines the construction of concurrency groups in
conjunction with programming previously done on the Phase Compatibility screen
(MM.2.1.3). A concurrency group (CG) is a logical grouping of phases in different rings
that are mutually compatible (while also understanding that phases in the same ring are
mutually conflicting).
GreenWave calculates the CG sequence by:
1.
Building non-redundant concurrency groups using every compatible phase
combination from the defined phase compability parameters, the ring sequencing
parameters, and the phase enable settings.
2.
Running NTCIP consistency checks to catch user errors. See Table 13 on page
69 for more details.
3.
Setting the order of the CGs to satisfy each ring’s sequence programming.
The resulting CG sequence is displayed on the Sequence Status screen (MM.1.1.8.)
Phase-based cycling obeys both this calculated CG sequence and the selected ring
sequence programming.
120
USTC Miscellaneous Screen
USTC stands for U.S. Traffic Corporation. These are proprietary parameters created for
the ATC controllers that are not part of the standard NTCIP data structures. They
support certain advanced features of the controller and are supported within ATC Link
and IQ Central.
M AIN M ENU > 2.P ROGRAMMING > 1.U NIT C ONFIGURATION > 7.USTC M ISCELLANEOUS
2.1.7
USTC MISC MENU
PG1OF1
LANGUAGE
:English(0)
STEADY RED
DURING FLASH
:000
REQUEST TIME SYNC :OFF
PHASE NEXT CONTROL:PERSISTENT(0)
TEXAS DIAMOND MODE:None(0)
ICC ENABLE
:OFF
MIZBAT MASTER ID : 0
MIZBAT LOCAL ID
: 0
SIMULTANEOUS FDW :OFF
Figure 106 – USTC Miscellaneous Screen
Language – The controller can display its front panel interface in one of four languages.
Some of the displayed parameters may remain in English. Once a change is made to
this selection, press
for the new language to be visible.
Table 18 – Available Interface Languages
Language Value
Displayed Language
0
English (North American)
1
Afrikaans
2
Spanish (Español)
3
French (Français Canadien)
Steady Red During Flash – When the controller is in MUTCD or Soft Flash mode, this
value determines the number of seconds (a value between 0 and 255 seconds) that all
channels flashing red are held at a steady red before the flash state can be exited. While
the steady red is held, the yellow flash channels will continue to flash yellow.
Request Time Sync – This feature is in support of the NTCIP AASHTO 1210 standard,
also known as Signal System Master (SSM) support. This provides controller time
synchronization using a local input. At present, the only local input recognized is done
via the front panel interface. When this value is set to 1, the management station should
see the transition and set the global time value. Once that occurs, this controller will
clear this object back to zero. If the value is cleared on this controller before the
management station notices the change to 1, nothing will be sent and operation will
continue as if nothing happened.
121
Phase Next Control – This setting determines how the controller handles the ‘Phase
Next’ decision within an intersection cycle. Possible values are: Persistent (0) or Not
Persistent (1). If Phase Next is set to persistent, at the end of Green, the controller will
attempt to make a Phase Next decision. If a phase next is found, that decision will be
retained unless a higher priority event occurs and causes the controller to re-comit the
ring. If a decisions cannot be made at the end of green, it will try again at the end of red
clearance.
If the Phase Next Control is set to Not Persistent, again, at the end of green, the
controller will attempt to make a Phase Next decision. Even if it decides on a next
phase, that decision will continue to be tested during the clearance phase, until the last
possible tenth of a second is reached, just before the end of red clearance. Once red
clearance is reached, the Phase Next decision will bring up the new phases. This is a
‘real-time’ approach to the Phase Next decision process. It allows for truly ‘real-time’
actuated operations.
Caution
In some cases, using Not Persistent control will cause overlaps to
terminate when the Phase Next decision is changed and is no longer a
Parent phase of the overlap. In such a case, the controller would hold
the ring in red until the overlap clears.
Texas Diamond Mode – This switch is used to enable and disable Texas Diamond
mode, which allows a pair of intersections on either side of a highway to be managed in
a coordinated fashion by a single controller, i.e. an intersection with a highway with four
ramps leading to and from a coordinated corridor. Texas Diamond mode uses
automatically programmed Dynamic Omits and Recalls to time the two intersections.
There are four available Texas Diamond modes:
Table 19 – Texas Diamond operating modes
Mode
Description
None(0)
No Texas Diamond database loaded
4 Phase(1)
Texas Diamond associated with service roads parallel
to the coordinated corridor
3 Phase(2)
Texas Diamond with no service roads parallel to the
coordinated corridor
Separate(3)
Operates similar to a quad-left intersection where the
Highway Ramps are phases 3 and 7
NEMA(4)
Dual quad-left intersection
Selection of a Texas Diamond mode will cause the controller to load of a default
database from Flash memory that matches that mode. A power recycle is required to
start Texas Diamond operation.
ICC Enable – When ON is selected, the Illinois Commerce Commission (ICC) CRC
validating feature is activated for use with ICC preemptions. Use the
buttons to change binary values.
122
and
MIZBAT Master ID – If an ATC is replacing a 3000, 3000E, or LMD controller in an oldstyle closed loop system managed by a M3000 Master, or if the ATC is replacing an
M3000 master in an old-style closed loop system, the value stored here must be the
system address (aka ‘Master ID’) for that device. The allowed values are 0 to 099. Refer
to “Process Control Screen” on page 107 (MM.2.1.5.6) for additional programming
parameters and notes.
MIZBAT Local ID – If an ATC is replacing a 3000, 3000E, or LMD controller in an oldstyle closed loop system managed by a M3000 Master, this value is the Device Address
or Device ID for that controller. The values allowed are 0 to 099. Refer to “Process
Control Screen” on page 107 (MM.2.1.5.6) for additional programming parameters and
notes.
Simultaneous FDW – This proprietary feature is designed for intersections that employ
audio pedestrian signals, such as Peek’s APS-10 signal, for blind persons. This feature
will cause pedestrian programming with unequal walk times to walk hold the shortest
walk time, then enter and exit the Flashing Don’t Walk (FDW) pedestrian clearance time.
This allows for concurrent operation of audible signals on concurrent pedestrian phases.
Saving the ‘ON’ value enables this feature globally (on all the time).
Note
For simultaneous FDW by time of day rather than as a global setting, activate TOD
Override Circuit 21 – unit SimPedClr on the Commanded TOD Action screen
(MM.2.4.4 ), and place an ‘X’ to the right of the numbered Command line, under
the action for the desired time period of a day plan.
123
Absolute Zero Screen (ABS ZERO)
The ABS Zero Status screens provides an interface to view and set 48 absolute zero
times for the controller. This feature is a test feature and is likely to change in future
builds of the software.
M AIN M ENU > 2.Programming > 1. Unit Configuration > 8. ABS ZERO
2.1.8
ABSOLUTE ZERO MENU
Current CU Time
:10:41:28
Current Timing Plan: 001
Absolute Zero Times
01.00.00.00 02.00.00.00
04.00.00.00 05.00.00.00
07.00.00.00 08.00.00.00
10.00.00.00 11.00.00.00
13.00.00.00 14.00.00.00
16.00.00.00 17.00.00.00
19.00.00.00 20.00.00.00
22.00.00.00 23.00.00.00
PG1of 2
03.00.00.00
06.00.00.00
09.00.00.00
12.00.00.00
15.00.00.00
18.00.00.00
21.00.00.00
24.00.00.00
ENT = Set Time ESC = Clear Time
Figure 107 – Absolute Zero screen, page 1 of 2
2.1.8
ABSOLUTE ZERO MENU
Current CU Time
:10:41:28
Current Pattern
: 001
Absolute Zero Times
25.00.00.00 26.00.00.00
28.00.00.00 29.00.00.00
31.00.00.00 32.00.00.00
34.00.00.00 35.00.00.00
37.00.00.00 38.00.00.00
40.00.00.00 41.00.00.00
43.00.00.00 44.00.00.00
46.00.00.00 47.00.00.00
PG2of 2
27.00.00.00
30.00.00.00
33.00.00.00
36.00.00.00
39.00.00.00
42.00.00.00
45.00.00.00
48.00.00.00
ENT = Set Time ESC = Clear Time
Figure 108 – Absolute Zero screen, page 2 of 2
This interface applies to any ATC equipped with an I/O Module and operated in either
the interval or phase-based mode. The Absolute Zero Reference Method is a non-onceper-day synchronization where each Timing Plan is individually referenced to a single
point in time by a keyboard initiated reset command. The ATC will continuously update
its reference from this point for each programmed timing plan or pattern number. The
default time, 00:00:00, indicates midnight local time.
The current plan or pattern is displayed on the lower right side of the Runtime Status
Screen (
). The Absolute Zero screen displays the time and current pattern for
whichever mode the ATC is running at the time of screen selection. The time entered for
each plan/pattern will serve as the Master Local Zero (L0) reference henceforth. When
these values are set, the Pattern Sync parameter on the Advanced Time Set screen
(MM.2.4.6), will be ignored.
124
Editing Individual Absolute Zero Times
After entering Edit mode, navigate using the green arrow buttons to the desired pattern
number. Press
to insert the current controller clock timef or the selected pattern
number. Press
to clear the current pattern’s absolute zero time value to zero
(’00:00:00’). Exiting Edit mode will save any changes that have been made.
Simultaneously Editing the Absolute Zero Times for All Patterns
These commands do not require one to enter Edit mode. Simply select 1=Set All to set
all 32 Plans or 48 Patterns to the current time. Selecting 2=Clear All will set all values to
00:00:00 (midnight).
125
Logic Processing Menu
The Logic Processing menu is where screens permitting an operator to create
conditional logic that dynamically runs the traffic engine can be programmed. In
GreenWave v3.8, there is a single set of Logic Processing parameters, those dealing
with dynamic omits and dynamic recalls to control anti-backup situations.
2.1.9
LOGIC PROCESSING MENU
1. ANTI BACKUP & RECALLS GROUP
Figure 109 – Logic Processing menu
Anti-Backup and Recall Screens
There are eight available programmable Anti-Backup & Recall screens, which can either
be globally active or called by TOD action.
M AIN M ENU > 2. P ROGRAMMING > 1. U NIT C ONFIGURATION > 9. L OGIC P ROCESSING
> 1. A NTI -B ACKUP & R ECALL P AGES
2.1.9.1 Anti-Backup & Recall
PG1of8
GLOBAL ENABLE.No(0)
1111111
FUNC/PH
1234567890123456
DYNAMIC OMIT PHASES. . . X
DYNAMIC RECALL PHASES. .
1111111
1234567890123456
IF PH ON. . . . . . . . .
X
AND
111111111122222222222333
IF O/L 123456789012345678901234566789012
GRN. . .
Figure 110 – Anti-Backup & Recall Screen
The basic logic of this screen is that IF the select phases AND overlaps at the bottom of
the screen are either the NEXT phase or green, THEN the controller should dynamically
omit AND recall the selected phases at the top of the screen. There are eight pages
available to store different sets of Logic Processing. Use the
and
access pages 1 through 8 of these programmable omits and recalls.
buttons to
The example shown in Figure 110 indicates a test that will occur when activated by the
current TOD plan. The test will activate a dynamic omit on phase 1 whenever phase 5 is
either NEXT or green.
126
Global Enable — This Yes/No value is used to determine if the specified logical test
should be applied at all times or only when called by a Time of Day action. When set to
Yes(1), the detected conditions will activate the dynamic omit or recall whenever they
occur. If set to No(0), then dynamic omits and recalls will only be performed if this page
is called by a Commanded TOD Action (MM.2.4.4), and the detected condition occurs
when that commanded pattern and action are active. Global Enable is set on a per
screen basis. The default value is No.
Dynamic Omit Phases – Place an ‘X’ under each phase number that should be omitted
when all of the conditions at the bottom of the screen are detected.
Dynamic Recall Phases – Place an ‘X’ under each phase number that should be
recalled when all of the conditions at the bottom of the screen are detected.
If PH On / IF O/L GRN – These are the test conditions to determine whether the
conditional omits and recalls should be applied to the intersection. These are AND’ed
test conditions. If you just want to test for a phase being NEXT or green, simply place an
X under that phase number. If testing for an overlap, an X must be placed under both
the overlap and at least one of its parent phases, otherwise the omits and recalls will not
occur.
127
Exclusive Pedestrian Operation
An Exclusive Pedestrian (XPed) movement is a programmed operation that stops all
vehicle movements in order to allow high volume pedestrian traffic to cross in all
permitted cross-walks of an intersection.
M AIN M ENU > 2. P ROGRAMMING > 1. U NIT C ONFIGURATION > 0. E XCLUSIVE
P EDESTRIAN
2.1.0.1 EXCLUSIVE PEDESTRIAN
PG 1 OF 2
EXCLUSIVE PEDESTRIAN # 1
SOURCE PHASE.. 9
GLOBAL ENABLE. YES
1 1 1 1 1 1 1
PHASE
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
DEST PHS
X
X
X
X
SOFT RET
SOURCE PHASE.. 0
GLOBAL ENABLE.No
1 1 1 1 1 1 1
PHASE
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
DEST PHS
SOFT RET
Figure 111 – Exclusive Pedestrian Screen
An XPed movement is usually needed when the pedestrian volume is high and vehicle
volume is low. XPed requires programming on here on the Exclusive Pedestrian screens
as well as on several other screens. GreenWave v3.8 provides four exclusive pedestrian
movements available for programming.
Source phase – This links to an enabled phase in your phase sequence that serves as
a placeholder and trigger for the XPED movement.
Global Enable – This flag determines whether the defined XPED movement runs all of
the time, or must be called by a TOD commanded action. If set to YES, then the XPED
always runs. If set to NO, then the XPED movement will only be included in the
sequence when the current TOD pattern enables it via an Action.
Dest PHS – An XPED movement has the capability to replace the regular pedestrian
movements associated with the other vehicular phases in the intersection. The
Destination Phases marked here indicate those regular pedestrian phases that should
be replaced by this XPED movement. If marked as an XPED destination phase, that
phase’s normal pedestrian movement will NOT be served. On the other hand, any
phases that are not marked as XPED destination phases will serve their pedestrian
movements as they normally would.
Soft Ret – Phases marked with this ‘soft return’ feature will cause the XPED to exit to
these designated phases in the absence of either red rest or any real calls or recalls on
any other vehicular or pedestrian phases. This defines a way to exit from the exclusive
pedestrian movement in those situations where there is no actuated guidance to tell the
controller where to proceed in the sequence. If no Soft Ret phases are defined and there
are no calls on any other phases in the intersection, then the default behavior is to keep
the intersection in XPED with all vehicular signals showing red; sort of an ‘all-Walk Red
Rest’ mode.
128
There is more to the process than simply programming this screen to achieve a working
XPED movement within an intersection. Table 20 on page 129 defines the steps to
program XPED. This is followed by a couple of XPED programming examples.
Table 20 – XPED Checklist
Task #
XPed Requirement
1
Program the Exclusive Pedestrian screen as required (MM.2.1.0)
2
Enable the XPed source phase (MM.2.2.1)
3
Add the XPed source phase to the sequence (MM.2.1.6)
4
Program the XPed source phase and destination phase’s Walk (MM.2.2.4.1) + Ped
Clearance times (MM.2.4.2.2)
5
Program the XPed source phase’s split time (MM.2.3.3)
6
Either set Global Enable to YES (MM.2.4.4), or program a TOD override
(MM.2.4.1.1)
7
Program the pedestrian detectors (MM.2.5.5) and/or to call the destination phases
(MM.2.5.7)
8
Test by placing ped detector calls on each of the destination phases
Example: Exclusive Pedestrian Programming
The following example will be used to demonstrate all the required programming for an
Xped movement to operate. This will be a standard quad-left intersection with four
pedestrian phases using XPed. Exclusive Pedestrian #1 is programmed as shown in
Figure 111. Since the source phase is programmed as Phase 9, that source phase must
be enabled on the Phase Enable screen (MM.2.2.1). That change is shown here:
2.2.1
PHASE ENABLE MENU
PG1 of 1
PHASE
1 1 1 1 1 1 1
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
ENABLE
X X X X X X X X X
Figure 112 – Phase Enables Screen with Phase 9 added
Next, we need to add the Source Phase to the phase sequence at the desired position
for the XPED movement. (MM.2.1.6.1)
129
2.1.6.1
RING SEQUENCING
PG 1of16
SEQUENCE NUM 1
RING
1 1 2 3 4 . . . . . . . . . . . .
2 5 6 7 8 9 . . . . . . . . . . .
3 . . . . . . . . . . . . . . . .
4 . . . . . . . . . . . . . . . .
Figure 113 – Adding the XPED phase to the ring sequence screen
With Phase 9 programmed as shown above, the XPed will occur after Phases 4 and 8,
and before Phases 1 and 5, assuming vehicle calls exist for all phases.
The source phase must have a non-zero walk time and a non-zero pedestrian clear time
programmed. The screen below (MM.2.2.4.2) shows the new phase 9 times added for
our example.
2.2.4.2
PHASE TIMINGS MENU
PG 1 of 2
PHS 9 - 10 - 11 - 12 - 13 - 14 - 15 - 16
---------------------------------------PED WALK
0-255 Seconds
7
0
0
0
0
0
0
0
PED CLEARANCE
21
0
0
0
0
0-255 Seconds
0
0
0
----------------------------------------
Figure 114 – Ped Timing Screen (Page 2) for XPED movement
The source phase also needs a non-zero split time, if the intersection is operating in
coordination. Figure 115 (MM.2.3.3.1) shows a programmed split time for Phase 9.
Note
130
If the Zero (0) Cycle Length option is selected to run Free in patterns 1 through
48, it is not mandatory to have non-zero Pattern Split Table values to operate
XPEDs.
2.3.3. 1
TABLE #
COORD SPLIT TABLE PG 1of16
1 TIMES IN SECONDS
PHASE
: 1
2
3
4
5
6
7
8
SPLIT
:008 038 008 018 008 038 008 018
MODE
: 2
2
2
2
2
2
2
2
COORD PH:
X
X
ST PERM : 0
0
0
0
0
0
0
0
END PERM: 0
0
0
0
0
0
0
0
PHASE
: 9 10 11 12 13 14 15 16
SPLIT
:028 000 000 000 000 000 000 000
MODE
: 2
2
2
2
2
2
2
2
COORD PH:
ST PERM : 0
0
0
0
0
0
0
0
END PERM: 0
0
0
0
0
0
0
0
Figure 115 – Split time added to the Coord Split table for the XPED movement
The above example shows a 100 second cycle, programmed in seconds.
Now, we need to go back to the XPED screen to make a couple of changes:
PG 1 OF 2
SOURCE PHASE.. 9
GLOBAL ENABLE. NO
1 1 1 1 1 1 1
PHASE
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
DEST PHS
X
X
X
X
SOFT RET
SOURCE PHASE.. 0
GLOBAL ENABLE.No
1 1 1 1 1 1 1
PHASE
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
DEST PHS
SOFT RET
Figure 116 – Setting Global Enable on the XPED screen
At this point, we can set the Global Enable parameter on the Exclusive Pedestrian
screen to be either Yes or No. It should be programmed to Yes if XPed is to be enabled
all of the time. It should be programmed to No if, instead, time of day programming will
be added to activate XPeds only at certain times of the day. The required TOD
programming is outlined below.
131
Activating XPED by Time of Day Action
The following steps describe how to enable an exclusive pedestrian movement by
setting up a TOD action. The basic step is to program the selected XPED number into
the desired TOD Action Screen (MM.2.4.4), under Commanded Actions. Action number
1, line 0 below shows a typical action call to the exclusive pedestrian movement.
2.4.4 COMMANDED
TOD
ACTION Number 1
PG 1of10
0.excl ped enab(20) : 1
1.not assigned(0)
:
2.not assigned(0)
:
3.not assigned(0)
:
4.not assigned(0)
:
5.not assigned(0)
:
6.not assigned(0)
:
7.not assigned(0)
:
8.not assigned(0)
:
9.not assigned(0)
:
NO will clear last entry
Page Up or Down To scroll Events
0=10 A=11 B=12 C=13 D=14 E=15 F=16
Figure 117 – Setting XPED Enable on the TOD Override Commands screen
Exclusive pedestrian #1 is now assigned to Conmanded TOD action number 1. To
complete the connection, this commanded action must then be assigned to a pattern, so
that XPed #1 will run during that pattern. This is done on the TOD Action screen
(MM.2.4.1.1), as shown in Figure 118.
2.4.1.1
TOD ACTION
1 of 6
PAT = 0..255
TSP = 0..48
Actn:
1
2
3
4
5
6
7
8
PATT :
TSP :
1
0
2
0
0
0
0
0
0
0
0
0
0
0
0
0
C
O
M
M
A
N
D
X
X
1:
2:
3:
4:
5:
6:
7:
8:
Figure 118 – Calling the XPED enable command from a TOD action
As shown above, exclusive pedestrian #1 will now run with Patterns 1 and 2.
132
Setting XPED Destination Phases
To operate in the typical manner, all of the normal pedestrian phases in the intersection
should be programmed to be ‘destination phases’ on the Exclusive Pedestrian screen.
This tells the controller to replace the per-phase pedestrian movements of all of those
phases with the one exclusive pedestrian movement later in the sequence.
PG 1 OF 2
SOURCE PHASE.. 9
GLOBAL ENABLE. NO
1 1 1 1 1 1 1
PHASE
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
DEST PHS
X
X
X
X
SOFT RET
SOURCE PHASE.. 0
GLOBAL ENABLE.No
1 1 1 1 1 1 1
PHASE
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
DEST PHS
SOFT RET
Figure 119 – Setting destination phases on the XPED screen
In this case, the destination phases have been defined to be phases 2, 4, 6 and 8. Be
sure that the pedestrian timings for those phases have been properly configured, as one
example shows in Figure 120. (MM.2.4.2.1)
2.2.4.1
PHASE TIMINGS MENU
PG 1 of 2
PHS 1 -- 2 -- 3 -- 4 -- 5 -- 6 -- 7 -- 8
---------------------------------------PED WALK
0-255 Seconds
0
7
0
7
0
7
0
7
PED CLEARANCE
0
11
0
11
0
0-255 Seconds
11
0
11
----------------------------------------
Figure 120 – Matching destination phase timings with XPED timing
Another important step to remember is that the pedestrian detectors for the destination
phases (in this case, phases 2, 4, 6 and 8) must also be programmed. See Figure 121
for an example of typical ped detector programming. (MM.2.5.5)
133
2.5.5
PEDESTRIAN DETECTORS PG 1 OF 1
PED DET#
1
2
3
4
5
6
7
8
CALL PH:
0
2
0
4
0
6
0
8
NO ACTIV:
0
0
0
0
0
0
0
0
MAX PRES:
0
0
0
0
0
0
0
0
ERR CNT:
0
0
0
0
0
0
0
0
Figure 121 – Ped Detectors Screen
In the above example, we have a simple one-to-one match between ped detectors
and pedestrian phases. (detector 2 calls phase 2, 4 calls 4, etc.)
Programming Soft Return Phases for XPED Operation
The Peek proprietary feature called Soft Return will cause the XPED to exit to
designated phases in the absence of Red Rest or any real vehicle/pedestrian calls or
recalls in the intersection.
PG 1 OF 2
SOURCE PHASE.. 9
GLOBAL ENABLE. NO
1 1 1 1 1 1 1
PHASE
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
DEST PHS
X
X
X
X
SOFT RET
X
X
SOURCE PHASE.. 0
GLOBAL ENABLE.No
1 1 1 1 1 1 1
PHASE
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
DEST PHS
SOFT RET
Figure 122 – Exclusive Pedestrian Screen
In the example above, XPED #1 will return and rest in Walk on phases 2 and 6 until a
valid call or recall is invoked.
A slight variation is to rest an XPED in walk on all destination phases. To accomplish
this, apply the Actuated Rest in Walk option to the XPED’s source phase, as shown in
Figure 123. (MM.2.2.8.2) In our example, the source phase is phase 9, so that is where
we need to apply the Actuated Rest in Walk flag.
134
2.2.8.2
PHASE OPTIONS
PG 2of 2
1 1 1 1 1 1 1
PHASE:
9 0 1 2 3 4 5 6
CALL TO NON-ACT 1.......
DUAL ENTRY..............
SIMULTANEOUS GAP OUT....
GUARANTEED PASSAGE......
ACTUATED REST IN WALK...X
CONDITIONAL SERVICE.....
ADDED INITIAL CALC......
FDW THRU YEL…………………………..
FDW THRU YEL & RED…………..
Figure 123 – Actuated Rest in Walk applied to XPEDs source phase
There are a couple of additional issues to consider about how XPED operates in a
coordinated environment. A programmed XPed movement will run, as long as:
1.
The source phase’s pedestrian permissive window is open during coordination.
2.
The source phase is not omitted.
3.
At least one of the Destination phases’ pedestrian call has been received and
stored for action by the ATC.
135
CONTROLLER MENU
The screens on the Controller Menu are used to define the operation of phased
signaling in the intersection. These values are not used when the controller is running an
interval-based pattern.
M AIN M ENU > 2. P ROGRAMMING > 2. C ONTROLLER
2.2
CONTROLLER PHASE FUNCTIONS MENU
1. PHASE ENABLES
8. PHASE OPTIONS
2. GREEN TIMING
9. RECALLS
3. CLEARANCE TIMING
0. OVERLAPS
4. PEDESTRIAN TIMING
5. ADDED INITIAL TIMING
6. GAP REDUCTION TIMING
7. DYNAMIC MAX TIMING
Figure 124 – Controller Menu
Phase enables are the on/off switches for phases. The next three options on this menu,
the Green Timing Screens, the Clearance Timing Screens, and the Ped Timing Screens,
function as the primary timing definition screens for all of the phases. Each of these
screens have two pages, the first for the first eight phases and the second for phases 9
through 16.
The rest of the options on this menu function as modifiers to standard phase operations.
For Phase Enables, refer to page 137.
For Green Timing, refer to page 138.
For Clearance Timing, refer to page 140.
For Pedestrian Timing, refer to page 141.
For Added Initial Timing, refer to page 142.
For Gap Reduction Timing, refer to page 143.
For Dynamic Max Timing, refer to page 146.
For Phase Options, refer to page 147.
For Recalls, refer to page 151.
For Overlaps, refer to “Chapter 9 — Overlaps”, beginning on page 267.
136
Controller Menu
Phase Enables Screen
This screen turns phases on and off for operation within the intersection, and activates
their parameters on the other Controller screens. If a phase is not enabled, it will not be
serviced, even if it is assigned as a start-up phase or as part of a ring. These are the
master on/off switches for phase movements.
M AIN M ENU > 2.P ROGRAMMING > 2.C ONTROLLER > 1.P HASE E NABLES
2.2.1
PHASE ENABLE MENU
PG1 of 1
PHASE
1 1 1 1 1 1 1
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
ENABLE
X X X X X X X X
Figure 125 – Phase Enables Screen
137
Green Timing Screens
The next three options on the Controller Menu, the Green Timing screens, the
Clearance Timing screens, and the Ped Timing screens, function as the primary timing
definition screens for the intersection. Each of these screens have two pages, the first
for the first eight phases and the second for phases 9 through 16.
Also known as the Phase Timings Menu, the Green Timing screens are used to define
the basic duration values, in seconds, to be used for the ‘Go’ portion of each phase.
M AIN M ENU > 2.P ROGRAMMING > 2.C ONTROLLER > 2.G REEN T IMING
2.2.2.1
PHASE TIMINGS MENU 1 PG 1of 2
PHS 1 -- 2 -- 3 -- 4 -- 5 -- 6 -- 7 -- 8
---------------------------------------MINIMUM GREEN
1-255 Seconds
5
5
5
5
5
5
5
5
PASSAGE
5.0 5.0
5.0
5.0
MAXIMUM 1
30
30
30
30
0.0-25.5 Seconds
5.0 5.0 5.0 5.0
30
1-255 Seconds
30
30
30
MAXIMUM 2
1-255 Seconds
1
1
1
1
1
1
1
1
----------------------------------------
Figure 126 – Green Timing Screen (page 1)
These are the standard NEMA timing parameters for the green portion of each enabled
phase.
Minimum Green – The least amount of time, in seconds, to be allowed for the green
movement of this phase. The minimum green can be any value from 1 to 255 seconds.
The default value is 5 seconds. When a phase is serviced, no matter what other events
occur within the intersection or timing modifiers are activated, including actuation,
preemption, or transit priority, the phase will always show a green light for at least this
many seconds.
Passage – For detector actuated and modified operation, the passage timer is
influenced by vehicle detector inputs. When a phase is red, the vehicle detector input
calls for the phase to be serviced, but when the phase is already being serviced, a
vehicle detector input instead serves to ‘extend’ the phase’s green period. Passage is
the increment of time by which the phase green is extended. The passage timer counts
down when no detector input is present, but it gets reset to its full value whenever a
detector input is present. The phase is extended until either a gap occurs in vehicle flow,
a force-off is applied, or if either of the maximum timers time out. Typical settings for
Passage are from 0.5 to 5 seconds, depending on how sensitive or large the detector
zones are. The possible range of values for Passage is 0.0 to 25.5 seconds. The default
value is 5.0 seconds.
Note
138
Throughout this book, the time when the passage timer doesn’t get extended
because a gap between vehicles of sufficient length has occurred is called the
Gap-Out.
Controller Menu
Maximum 1 – The maximum amount of green time allowed for each phase. For an
actuated phase, this is the upper limit of the amount of green time allowed, as long as
the phase is not in Maximum Recall mode. When Maximum Recall is not set to be ON
for this phase, the Maximum 1 timer times down only when a serviceable, conflicting call
is present. The phase remains green until the Passage timer fails to be reset by a
vehicle detection, or until the Maximum 1 timer reaches zero, whichever comes first.
This timer will cease timing and reset if all serviceable calls go away. The timer will restart, if a new call arrives and the active conflicting phases are in the Passage interval.
However, when Maximum Recall is ON for this phase, the phase is always served and
the Maximum 1 timer always counts down, without regard to any detector calls.
The value of Maximum 1 can vary widely, but to give a feel for the range, its value is
typically between 8 and 17 seconds for left turns, between 12 and 25 seconds for side
streets, and between 22 and 40 seconds for main streets. The default value is 10
seconds.
Note
If the Maximum 1 value is set to a very low number (such as 1 second) then
minimum timing requirements for the phase, such as Min Green, will override it.
Maximum 2 – Maximum 2 is an alternate value for the maximum allowed amount of
time allowed for this phase to be green. Max 2 is activated, on a ring by ring basis, by
either an external input or by a TOD pattern change. When Max 2 is active the
Maximum countdown timer will be loaded with the Maximum 2 value instead of the usual
Maximum 1 time. When setting a value for the Maximum 2 field, the same concepts
apply as with Maximum 1, except an alternate value is used. Maximum 2 is sometimes
used during peak traffic periods (i.e. to generate longer main street flow times.) It is also
sometimes used during coordination, so that phases won’t time out before being forced
off.
Again, if Max 2 time is set to a very low number (such as 1 second) then minimum
timing requirements for the phase, such as Minimum Green, will override it.
139
Clearance Timing Screens
The Clearance Timing Screens set timing values for the yellow and red portions of each
phase.
M AIN M ENU > 2.P ROGRAMMING > 2.C ONTROLLER > 3.C LEARANCE T IMING
2.2.3.1 CLEARANCE TIMINGS MENU PG 1of 2
PHS 1 -- 2 -- 3 -- 4 -- 5 -- 6 -- 7 -- 8
---------------------------------------YELLOW CLEARANCE
3.0-25.5 Seconds
3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0
RED CLEARANCE
2.0 2.0 2.0
2.0
0.0-25.5 Seconds
2.0 2.0 2.0 2.0
RED REVERT
0.0 0.0
0.0
0.0-25.5 Seconds
0.0 0.0 0.0 0.0
0.0
----------------------------------------
Figure 127 – Clearance Timing Screen (Page 1)
Yellow Clearance – Quite simply, this is the amount of time the phase will spend
showing the yellow signal. Yellow clearance can be set to any value between 3.0 and
25.5 seconds. Typical settings are from 3.5 to 5 seconds, based on the travel speed of
traffic and the width of the intersection. The default value is 3.0 seconds.
Red Clearance – Obviously, phases sit in red whenever other phases are being served,
but there is a short period in the interval when switching from the service of one phase to
the next when the entire intersection must display ‘All Red’. Red Clearance defines how
long this ‘rest’ period is. Values from 0.0 to 25.5 seconds can be entered, but typically
this value is between 0 and 2.5 seconds. It is recommended that you use a time of at
least 1 second for the Red Clearance value. The default value is 2.0 seconds.
Red Revert – Red Revert time is designed to deal with special occasions when a phase
may complete its service, and the timing circuit or the coordinator of the controller decides
to service the exact same phase again. When this occurs, the red revert time serves as
the minimum red time before the phase is switched to green again. This avoids the
possibility of a green to yellow to green display. Red Revert is usually set to a value that is
higher than Red Clearance. Typically, this parameter comes up when the controller is
asked to switch into a preemption sequence, or when switching patterns during TOD
operation. Values from 0.0 to 25.5 seconds can be entered. The default value is set to 0.0
to allow the global Red Revert value on the Start-up menu to take precidence.
Note
Use the
140
The Red Revert time shown here varies from the Red Revert parameter visible on
the Start-up Menu. The Red Revert shown there is a unit global value. The
parameter shown here, on the other hand, allows the user to set a red revert value
per phase that is longer than the global value. The greater of the two values will be
used.
and
keys to switch between the two clearance timing screens.
Controller Menu
Pedestrian Timing Screens
This screen is used to set the timing for the Walk/Don’t Walk signals of phase-based
patterns. Pedestrian phases are linked to the Vehicle phases of the same number.
M AIN M ENU > 2.P ROGRAMMING > 2.C ONTROLLER > 4.P EDESTRIAN T IMING
2.2.4.1
PED TIMINGS MENU
PG 1of 2
PHS 1 -- 2 -- 3 -- 4 -- 5 -- 6 -- 7 -- 8
---------------------------------------PED WALK
0-255 Seconds
0
5
0
5
0
5
0
5
PED CLEARANCE
0
5
0
5
0
0-255 Seconds
5
0
5
----------------------------------------
Figure 128 – Ped Timing Screen (Page 1)
Ped Walk – The amount of time, in seconds, that the Walk signal is displayed, starting
at the beginning of the phase’s vehicular green period. Valid values range from 0 to 255
seconds. Default values are 5.0 seconds for phases 2, 4, 6, and 8.
Ped Clearance – The amount of time, in seconds, after the end of the Ped Walk period,
when the flashing Don’t Walk signal will be displayed. Valid times range from 0 to 255
seconds. Default values are 5.0 seconds for phases 2, 4, 6, and 8. These values are
probably the bare minimum pedestrian timings to allow for crossing a two lane street.
Generally, pedestrian timings are simple. They can be modified by some phase-based
parameters on other screens, such as the Actuated Rest in Walk, FDW thru Yellow, and
RDW Thru Yel & Red options on the Phase Options screen. (Screen 2.2.8.1, See page
147.)
The pedestrian signals for overlaps are defined in the Overlaps menu. (Screen 2.2.0,
Refer to page 153.)
Interval-based patterns use user-defined channel and signal mappings to determine
pedestrian outputs, and are handled in the Interval menus. (Screen 2.7, See the
“Chapter 7 — Interval Operation”, starting on page 213.)
141
Added Initial Timing Screens
The next two screens concern a modification of basic actuated-phase operation, often
called “Volume/Density” operation. Volume density is a way for an intersection to adapt
to changes in traffic volume based on inputs from detectors. Volume density is
composed of two parts: Initial time adjustments and gap reduction. Initial timing is set
here on the Added Initial screen; gap reduction parameters are set on the next screen.
M AIN M ENU > 2.P ROGRAMMING > 2.C ONTROLLER > 5.A DDED I NITIAL T IMING
This screen allows the operator to program the optional Added Initial parameter for each
phase, as well as associated parameters. There are two pages for these parameters,
the first one for phases 1 through 8 and the second page for phases 9 through 16.
2.2.5.1 ADDED INITIAL TIMINGS
PG 1of 2
PHS 1 -- 2 -- 3 -- 4 -- 5 -- 6 -- 7 -- 8
---------------------------------------SEC/ACTUATION
0.0-25.5 Seconds
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
MAX INITIAL
0
0
0
0
0
0-255 Seconds
0
0
0
----------------------------------------
Figure 129 – Added Initial Timing Screen (Page 1)
Sec/Actuation – Also known as ”Added Initial” timing, this parameter is used to
calculate an Added Initial timing period, based on detections during the non-Green
intervals of a phase. The Sec/Actuation value for a phase is multiplied times the number
of vehicles (detections) that are received while the phase is in the Yellow and Red
states. This modified initial timing for a phase will be used only if the calculated Added
Initial value is greater than the Min Green time and less than the Maximum time. (This is
normally Maximum1, but Maximum 2 will be used instead, if it has been invoked.)
Typical settings: 2 - 3 seconds. About enough to move each vehicle.
Max Initial – Maximum Initial sets a limit on the amount of Added Initial. Added Initial
can never exceed the maximum initial value. Also known as Max In, or Max Variable
Initial. Typical settings: The Max Initial setting is normally set equal to the Initial
interval that would be used if Volume Density were not used.
Important
142
Since both Added Initial and Gap Reduction use vehicle detections for
red phases, both methods are based on the assumption that set-back
detectors are installed. When the vehicle actuators are installed back at
least several car length from the stop bar, this allows multiple vehicle
detections to occur on phases where traffic is facing a red light.
Controller Menu
Gap Reduction Timing Screens
Gap Reduction, along with the previous screen’s Initial Timing parameters, are
modifications of the basic actuated phase operation called “Volume/Density” operation.
Volume/Density is a way for an intersection to adapt to changes in traffic volume based
on inputs from detectors. Gap reduction is a method to dynamically reduce the time
allowed between cars that is required to keep the green passage timer going, based on
how long the green has continued and how many cars have been detected on other
phases within the intersection.
M AIN M ENU > 2.P ROGRAMMING > 2.C ONTROLLER > 6.G AP R EDUCTION T IMING
This screen allows an operator to set up Gap Reduction on the ATC-1000 controller.
There are two pages of parameters, the first covers the parameters for phases 1 through
8 and the second for phases 9 through 16.
2.2.6.1 GAP REDUCTION TIMING PG 1of 2
PHS 1 -- 2 -- 3 -- 4 -- 5 -- 6 -- 7 -- 8
---------------------------------------TIME B4 GAP REDUCTION
0-255 Seconds
0
0
0
0
0
0
0
0
CARS B4 GAP REDUCTION
0
0
0
0
0
0-255 Vehicles
0
0
0
TIME TO REDUCE
0
0
0
0
0-255 Seconds
0
0
0
0
MINIMUM GAP
0.0-25.5 Seconds
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
----------------------------------------
Figure 130 – Gap Reduction Timing Screen
Time B4 Gap Reduction – Also known as TBR, this NEMA parameter sets the Time
Before Reduction value for Gap Reduction operations for this phase. The value can be
between 0 and 255 seconds. This is the amount of time the controller will wait before it
begins reducing the passage gap test to the Minimum Gap value. Time Before
Reduction (TBR) starts timing when a conflicting call is received (i.e. when someone is
waiting at another stop bar in the intersection,) which is often the beginning of green. If
the TBR period counts down completely, or the Cars B4 Gap Reduction parameter is
satisfied (whichever comes first), the controller will begin reducing the allowed gap in the
Passage time for this phase. (Passage time is described on page 138.)
If all conflicting calls are removed before TBR has completed timing, the TBR timer will
reset. Typical settings: 8 to 20 seconds. You need to allow enough time for queued
vehicles to begin moving, since their initial speed will be slow, meaning their gap values
will take too long, and gap reduction will begin too quickly. The value of Time B4 Gap
Reduction (TBR) should be at least the value of Minimum Green plus 1 second.
Cars B4 Gap Reduction – This is an NTCIP object that is a slight addition to the normal
NEMA Gap Reduction process. This parameter gives another way for gap reduction to
begin. This value, which can be any setting between 0 and 255 detected vehicles, tells
the controller to begin reducing the passage timer test whenever more than this number
of vehicles are waiting at other stop bars in the intersection. Gap reduction will begin
whenever either the TBR or the Cars B4 Gap Reduction thresholds are crossed.
143
Time to Reduce – Time to Reduce (TTR) is a NEMA parameter that establishes the
time reduction step that the controller will use to begin a linear reduction of the phase
gap (passage time) down to the minimum gap time. This value can be anything between
0 and 255 seconds, but typical settings are between 4 and 12 seconds. The size of TTR
depends on how quickly the operator wishes to close the timing gap. A larger TTR
closes the gap more quickly. If one wishes to close the gap immediately in one reduction
step, the value of TTR should be the entire difference between the Passage time and
the Minimum Gap value.
Minimum Gap – Minimum Gap is another standard NEMA parameter of the gap
reduction process. The minimum gap value establishes the lowest acceptable gap
(passage time) in traffic. The gap test will not be reduced below this amount. So if cars
continue to cross the vehicle detectors at a rate that leaves no gaps larger than this
Minimum Gap value, the Passage timer for the green portion of this phase will be
extended right up until the Maximum timer times out. The acceptable range for
minimum gap is from 0.0 to 25.5 seconds. Typical settings for Minimum Gap are from 1
to 3 seconds.
Note
In the presence of a continuous vehicle actuation, the phase will not gap out even
if Minimum Gap is set at zero.
Notes About the Usage of Gap Reduction
Gap reduction allows the normal passage time for a phase to be reduced linearly during
the green portion of the phase. The parameters associated with this operation are called
Time Before Reduction (TBR), Cars Before Reduction, Time To Reduce (TTR) and Min
Gap. Thus, the longer demand holds a phase green even though a conflicting call is
present, the closer the vehicles must be spaced to retain the existing green interval.
The following are the two typical uses of gap reduction:
144
Controller Menu
Gap Reduction – the Classic Case
In this example, loops are set back from the intersection, perhaps as far as several
hundred feet back from the stop bar. These are used to extend the phase. There may or
may not be stop bar detectors, as well. (It is recommended that there are.)
travel time
setback loop
Figure 131 – Classic Case of Gap Reduction
The Passage timer value is set based on the travel time for a vehicle to get from the setback detector to the intersection. This value could be fairly long; if left alone, this would
tend to cause the intersection to run sluggishly, since the phase would constantly
extend, even with widely gapped traffic. By using gap reduction, the passage value can
be reduced down enough to provide good gap control.
Gap Reduction as an Efficiency Tool
Even with normal stop bar detectors, Gap Reduction can be an effective way to increase
efficiency without getting “the green is too short” complaints. The idea is to begin the
phase with a fairly long passage time when vehicles are moving slowly, then move to a
shorter time later, when they are moving at the flow rate. Gap reduction is thus a good
way to obtain “snappy” operation, so that phases cycle crisply without long waits, but
also without complaints. which are often the case when Passage times are simply set to
low values.
145
Dynamic Max Timing Screens
This screen allows the operator to program the values to configure Dynamic Maximum
operation. This is a system to modify the maximum green period allowed for a phase.
The ‘dynamic’ in the title indicates that this modification is done on the fly, as the
intersection operates. There are two pages of Dynamic Max parameters, the first covers
phases 1 through 8; the second covers phases 9 through 16.
M AIN M ENU > 2.P ROGRAMMING > 2.C ONTROLLER > 7.D YNAMIC M AX T IMING
2.2.7.1 DYNAMIC MAX TIMING
PG 1of 2
PHS 1 -- 2 -- 3 -- 4 -- 5 -- 6 -- 7 -- 8
---------------------------------------DYNAMIC MAX LIMIT
0-255 Seconds
0
0
0
0
0
0
0
0
DYNAMIC MAX STEP
0.0 0.0 0.0 0.0
0.0-25.5 Seconds
0.0 0.0 0.0 0.0
----------------------------------------
Figure 132 – Dynamic Max Timing Screen
Dynamic Maximum operation can be activated for a particular phase by setting
non-zero values to the following parameters. Dynamic Maximum operation
functions in NEMA phase-based patterns only. It functions on top of the normal
Max1 and Max 2 parameters for a given phase. It functions like this: if a phase
‘Maxes Out’ twice in a row, the maximum value of the phase begins stepping
upward. Each time after that the phase maxes out again, the maximum steps
upward again, until an ultimate maximum is reached. If this upward stepping is
active and the phase gaps out rather than maxing out, the dynamic maximum
steps downward instead.
Dynamic Max Limit – This is the upper limit on the duration of the green, in seconds,
that the phase can be granted as a result of Dynamic Max adjustments. Note that if this
value is lower than the Max1 and Max 2 limits, then the downward stepping mode of
Dynamic Max operation can actually shorten the maximum green time for this phase all
the way down to this lower value. This can be any value between 0 and 255 seconds.
Dynamic Max Step – This is the number of seconds that are added to the phase’s
maximum green value after the phase has maxed out twice in a row. This stepping
upward continues until the Dynamic Max Limit is reached or the phase fails to max out
once. Dynamic Max stepping will also be deactivated if one of these conditions exist for
this phase:
A failed detector on the phase
Maximum recall is triggered
Dynamic Max Step can be set to any value between 0.0 and 25.5 seconds, in tenths of a
second. The size of this step depends on how quickly you would like the intersection to
respond to a sudden flux of traffic. Larger step values can be used to make the
intersection respond more quickly.
146
Controller Menu
Phase Options Screens
The Phase Options screens allow the user to activate or deactivate special per-phase
functions, including CNA operation, Dual entry, Simultaneous gap-out, and others. There
are two pages of settings. The first allows the setting of these ten parameters for phases
1 through 8. The second page sets the same ten parameters for phases 9 through 16.
M AIN M ENU > 2.P ROGRAMMING > 2.C ONTROLLER > 8.P HASE O PTIONS
2.2.8.1
PHASE OPTIONS
PG 1of 2
PHASE:
1 2 3 4 5 6 7 8
CALL TO NON-ACT 1....... X
X
X
X
DUAL ENTRY..............
SIMULTANEOUS GAP OUT....
GUARANTEED PASSAGE......
ACTUATED REST IN WALK...
CONDITIONAL SERVICE.....
ADDED INITIAL CALC......
FDW THRU YEL............
FDW THRU YEL & RED......
Figure 133 – Phase Options Screen
Press the
button to see the Phase Options for phases 9 through 16.
Call to Non-Act 1 — Call to Non-Actuated, or “CNA” operation, is a method of phase
timing (in NEMA phase-based patterns only) in which vehicles and pedestrian detectors
are not required in order to serve the phase. CNA is described in detail in the TS2-2003
standard, under paragraph 3.5.3.2.3. CNA is often used when it is desired to hold the
coordinated phase in Walk during coordination. Min-Recall and Ped Recall are
automatically activated, and phase detectors are disabled for phases set to CNA. The
most significant aspect of the CNA mode is that during the hold period while in
coordination, the CNA phase will hold at the end of walk instead of the end of green.
Ped Clear then follows just before phase termination. The advantage of using CNA for
coordinated phases is that the length of walk is determined by the coordinated phase
split time. In this way, the walk duration varies depending on the cycle and split
selection, i.e. Walk time = split time – (PedClearance + Yellow + Red). Place a check
(‘X’) in this row to set this phase to be a CNA1 phase.
A CNA phase contains four Green states, defined by NEMA as States A, B, C and D.
State A is Walk Timing, State B is Walk Rest or Walk Hold, State C is Ped Clearance,
and State D is Green Dwell/Select.
State A: Walk Timing – Upon initial entry into phase, Walk times provided Ped
Omit is not on.
State B: Walk Hold – Upon completion of Walk Timing, the phase “holds” in walk
if Hold is applied.
147
State B: Walk Rest– The phase “rests” in Walk if Hold is not applied, the Walk
Rest Modifier (WRM) is applied, and no serviceable conflicting calls exist.
The phase leaves the Walk Rest/Hold state and advances to Ped Clearance when:
a.) The phase is in Walk Rest and a serviceable conflicting call is registered,
or
b.) The phase is in Walk Hold, a serviceable conflicting call exists and Force
Off is applied, or
c.) Hold is released and the WRM is not active, regardless of the presence of
a serviceable conflicting call.
State C: Ped Clearance – The phase times the Ped Clearance setting, and then
advances to the Green Dwell/Select state.
State D: Green Dwell/Select – This is the state in which the controller does one of
the following things, based on the current conditions:
a.) Immediately selects the next phase to be serviced and proceeds to yellow
clearance, or
b.) it rests in Green/Don’t Walk if a call exists and concurrent timing constraints
exist, or if WRM and Ped Recycle are not active, or
c.) it returns to Walk if no serviceable conflicting call exists and either WRM or Ped
Recycle are active, and Ped Omit is not active.
Once a CNA phase has left the Walk state, Hold and Force Off do not have an
effect on the termination of the phase. That is, Force Off does not have to be
maintained throughout Ped Clearance in order to terminate the green, nor will
Hold maintain the phase in Green/Don’t Walk.
Call to Non-Act 2 — Place a check (‘X’) in this row to set this phase to be a CNA2
phase. CNA2 operates the same as CNA1, but it provides an alternative phase selection
method for Call to Non-Actuated operation, usually for cross-arterial coordination.
Note
Either CNA or CNA2 can be enabled by a TOD override without the need to
place an ‘X’ here in phase options along with a machine input. TOD overrides
are discussed starting on page 162.
Dual Entry — Place a check (‘X’) in this row to set this phase to be a Dual Entry phase.
Dual Entry works in conjunction with the compatibility matrix of phases. (See page 85)
Dual Entry is a flag on a phase that tells the controller that if a phase in the other ring
comes on by itself, the controller can look across the barrier for a compatible phase that
is marked as Dual Entry, and it will select one to turn on. This ensures that there will
always be a phase on in each ring whenever the compatibility matrix permits it. Dual
Entry is typically used during multi ring operation, to prevent a single phase from being
served at a time. For example, suppose phase 8 gets called. The controller might serve
it alone, except it notices that across the ring barrier, phase 4 is listed as both
148
Controller Menu
compatible with 8, AND it is a Dual Entry phase, so the controller goes ahead and turns
phase 4 on at the same time.
Simultaneous Gap Out — Place a check (‘X’) in this row to set this phase to be a
Simultaneous Gap Out phase. Simultaneous Gap Out, sometimes known as ‘SGO’,
allows a phase’s passage timer to re-start if it has timed out and the phase is waiting to
cross a barrier. With SGO enabled and calls on Phases 2 and 6, the Phase 4 passage
timer can start again if a new vehicle arrives. If Phase 4 then extends and Phase 8 gaps
out, Phase 8 can start its passage timer again. This operation can continue back and
forth until both phases Max Out or they both “Simultaneously Gap Out”, hence the
name. When Simultaneous Gap Out is disabled, the phase passage timer cannot restart
once it times out for the selected phases and is waiting to cross the barrier. If phase 4
goes to rest while 8 is extending, then 4 cannot start its passage timer again. Both
phases will then gap out as soon as phase 8 does. So phases will tend to gap out
sooner with SGO disabled than when it is enabled.
Guaranteed Passage — Place a check (‘X’) in this row to set this phase to be a
Guaranteed Passage phase. When this is enabled for a phase that is operating in
volume density mode, meaning it is using gap reduction, it allows the phase to retain the
right-of-way for the unexpired portion of its Passage timer, following the decision to
terminate the Green due to a reduced gap.
Actuated Rest in Walk — Place a check (‘X’) in this row to set this phase to be an
Actuated Rest-in-Walk phase. This was called ‘Walk Rest’ or ‘WR’ in the 3000E
controller. Allows the selected phase to rest in Green-Walk instead of Green-Don’t Walk,
as long as there is no serviceable conflicting call at the end of the Walk timing.
Conditional Service — Place a check (‘X’) in this row to set this phase to be a
Conditional Service phase. This is typically used to allow a left turn phase to be served
twice in the same cycle; once as a leading phase and once as a lagging phase. This is
only possible in a non-coordinated intersection. The following conditions are required to
allow a conditional service phase to function in this way:
there is a call for service on a leading left-turn phase
the intersection is not working in coordination with any other intersection
There is a conflicting call on the opposite side of the barrier. Otherwise, the leftturn phase would be serviced automatically by standard actuated controller
behavior, and conditional service isn’t required.
The through phase of the phase pair that includes this left turn has Gapped out.
The time remaining on the through phase’s maximum timer is larger than the leftturn’s minimum conditional service time.
Note that although conditional service is usually used to allow a second left turn during a
cycle, it can in fact be used for any phase that meets the above criteria; just replace the
‘left-turn phase’ term in the requirement with ‘the conditional phase’.
Added Initial Calc — Place a check (‘X’) in this row to set this phase to be an ‘Added
Initial’ phase. Added Initial is a form of Variable Initial timing, which increases the initial
green interval of a phase based on the demand for that phase that is measured during
the preceding yellow and red periods. The extra time allows a platoon of vehicles to
proceed through the intersection before the passage time becomes active. The addedATC Controller Operating Manual
149
initial option is generally used when long minimum green times are specified. This
method counts the number of detector counts during the non-green portion of the phase
and uses that to add a multiple of the added initial time to the minimum green time. The
total initial time will not exceed the defined Max initial time. The controller will compare
all of the detectors associated with this phase and use the one that collected the largest
number of vehicle counts. The values used in these calculations are entered on the
“Added Initial Timing Screens”; see page 142.
FDW Thru YEL — Flashing Don’t Walk through the Yellow portion of the phase. The
‘clearance’ portion of the walk movement is normally timed using the values stored on
the Ped Timings screen (on the Controller menu). This switch overlays a new condition
on the pedestrian timing. The controller uses the Ped timings, but also goes to flashing
don’t walk during the Yellow section of the vehicular parent phase, and then to steady
Don’t Walk for the Red portion.
FDW Thru YEL & RED — Similar to ‘FDW Thru YEL’, but instead of just flashing Don’t
Walk through the Yellow portion of the phase, the controller flashes Don’t Walk through
both the Yellow and Red portions of the phase. With this flag on, the pedestrian signal
doesn’t go to steady Don’t Walk until the end of the vehicular phase. FDW thru Red
allows ped clearance to continue into all red. Solid Don’t Walk will start as all red
terminates.
Caution
150
Peek Traffic Corporation does not recommend the use of either FDW
Thru YEL or FDW Thru Yel & Red.
Controller Menu
Recalls
The Recall screen is used to define phase-by-phase recall options for the controller. A
recall is a way to create recurring calls for service by phases, even when no real call
exists. It’s a call placed from within the programming of the controller, rather than
generated by an external source such as a detector input. A recall is a way to ensure
that phases are serviced in the case that detectors are faulty, vehicles miss the detector
hot zone, or the pedestrian fails to push the button properly. Recalls can be set for the
vehicle and the pedestrian portions of a phase separately. There are two pages of recall
screens; the first allows the operator to set the five recall options for phases 1 through 8,
the second page for phases 9 through 16.
M AIN M ENU > 2.P ROGRAMMING > 2.C ONTROLLER > 9.R ECALLS
2.2.9.1
PHASE RECALLS
PHASE/
FUNCTION:
PG 1of 2
1 2 3 4 5 6 7 8
VEHICLE MINIMUM.........
VEHICLE MAXIMUM.........
PEDESTRIAN RECALL.......
X
DETECTOR NON LOCK.......
SOFT RECALL.............
Figure 134 – Recalls Screen
The above example shows that a recall has been programmed for the pedestrian portion
of Phase 2. This will ensure that the Phase 2 Walk signal will appear during each cycle,
no matter what happens with the intersection detectors and push button inputs.
Press the
button to see the Recall settings for phases 9 through 16.
Use the
and
buttons toggle the Checks for each type of recall for each phase.
An ‘X’ indicates that that type of recall will be applied to the phase.
Vehicle Minimum – Place a check (‘X’) in this row to set this phase to have a Vehicle
Minimum Recall, also sometimes known as just a ‘Min Recall’. A minimum recall assures
that the phase will always be serviced and will time the Initial green, but any further
green is dependent on detector extensions. (If detections are present, the phase can
time up to the Max time.) If there is no demand on the phase, the controller will time the
Initial interval only, then it will either rest (if there is no other demand) or advance to the
next phase that has demand. A phase can operate in either Min Recall or Max Recall,
but not both. If both are selected, then Max Recall will be used.
Vehicle Maximum – Place a check (‘X’) in this row to set this phase to have a Vehicle
Maximum Recall, also sometimes known as just a ‘Max Recall’. This is similar to Min
Recall, except that the phase will time the entire max time regardless of demand. Upon
termination of the Max timer, the phase will either rest or advance to a phase that has
demand. Maximum 1 is the default maximum used. Maximum 2 can be selected via an
151
external input or via a Time of Day Action. Max Recall is typically used for any phase
that is to be “pre-timed” i.e. it has no detection but must be served. Often used on a
main street with no peds (or actuated peds) in a semi-actuated application where the
side is actuated but the main street is not. Note that Max Recall should not be applied to
phases with functional detection. It is sometimes applied to an actuated phase
temporarily when detection fails. A phase can operate in either Min Recall or Max
Recall, but not both. If both are selected, then Max Recall will be used.
Pedestrian Recall – Place a check (‘X’) in this row to set this phase to have a
Pedestrian Recall, also sometimes known as just a ‘Ped Recall’. The pedestrian
movement on this phase will be serviced once per cycle.
Detector Non Lock – Non-Lock disables vehicle call memory on selected phases. The
phase only recognizes vehicle presence so that the detector must be continuously
occupied in order to maintain a call for service. Note that the default mode is non-lock
disabled (no “X”), which means that memory is on. Program an “X“ for phases to operate
in Non-Lock mode (i.e. memory off, presence mode).
When Non-Lock is not enabled (locking mode), if the phase terminates with time
remaining in the Passage Timer (i.e. Max, Force Off, Interval Advance), a call will be left
on the phase and the unit will cycle back to it until the call is serviced.
Non lock enabled (X) should be used for phases where the detection zone is sufficient
for presence type detection and vehicles must occupy the detector zone to be served. If
these vehicles leave before phase service, the call is forgotten, (i.e. Right Turn on Red
or Permissive Left Turn completed). Non-Lock disabled (no “X”) should be used when
the detector call must be retained until phase service, such as when the detection zone
is set back from the stop bar, or when it is easy for a vehicle to overrun the stop bar
detector.
Soft Recall – Place a check (‘X’) in this row to set this phase to have a Soft Recall. Soft
Recall will only place a call on the selected phases if no real calls exist and the controller
is not already resting in one of these phases. It allows the unit to cycle between all
phases, and when demand ceases, rest in the programmed phase(s).
Note
If Soft, Min and Max recalls are all set for the same phase, Max Recall will
take precedence.
It should be noted that there is a distinct difference between Soft and Min Recall, even
when used in a 2-Phase operation. The difference is apparent if, for example, Phases 1
and 2 both have Max Times of 20 seconds, there is no real call on Phase 2, and Soft
Recall is applied to Phase 2. In this case, Phase 1 can extend in Passage indefinitely.
(Phase 1’s Max timer does not count down.) If Min Recall were applied to Phase 2 in this
situation, Phase 1 would max out after 20 seconds and then serve “demand lacking”
Phase 2, despite there still being demand on Phase 1.
Soft Recall is typically used on a fully actuated intersection. Soft Recall allows the unit to
always go back to and rest in main street Green when there is no demand (or recalls)—
but without interfering with other phase service.
For example, at a 3 phase intersection, say that phase 2 is the main street with Soft
Recall mode set. If there is demand on Phases 1 and 3 only, the controller will cycle
152
Controller Menu
between Phases 1 and 3 only, without servicing Phase 2*. It is only when there is no
demand at all that Soft Recall will be applied to Phase 2. If Min Recall had been applied
to Phase 2, the unit will always cycle through Phase 2 when going from Phase 1 to 3.
Note
In order for Soft Recall to work properly, the Soft Recall programmed
phase(s) must have detection.
Just as an added function that can be used during testing, manual calls can be placed
on either vehicular or pedestrian phases from the controller’s main status screen, as
long as the controller is running a phase-based pattern. This capability is described on
page 51.
Overlap Menu
This menu is used to access the two overlap setup screens, one for vehicle overlap
phases and the other for pedestrian overlap phases.
M AIN M ENU > 2.P ROGRAMMING > 2.C ONTROLLER > 0.O VERLAPS
2.2.0
OVERLAPS MENU
1. VEHICLE OVERLAPS
2. PEDESTRIAN OVERLAPS
Figure 135 – Overlaps Menu
The timing concepts involved in programming overlaps can be very complex. The whole
variety of overlaps that are available in the ATC controllers are described in detail in
“Chapter 9 — Overlaps”, starting on page 267.
*
Phase 2 will be served normally if there is real demand. (i.e. Cars are actually on the detector.)
153
COORDINATION MENU
This menu is used to access the coordination-specific setup screens.
M AIN M ENU > 2.P ROGRAMMING > 2.C OORDINATION
2.3
COORDINATION MENU
1. COORDINATION VARIABLES
2. PATTERN TABLE
3. SPLIT TABLE
4. OFFSET CORRECTION EXT/REDUCE
Figure 136 – Coordination Menu
The concepts involved in programming coordination are complex enough to warrant their
own chapter. Please refer to “Chapter 6 — Coordinated Operation”, starting on page
185.
154
Time of Day Menu
TIME OF DAY MENU
The Time of Day (TOD) functions allow the controller to switch between coordinated or
interval-based patterns at preset times throughout a day, and throughout the year.
M AIN M ENU > 2.P ROGRAMMING > 4.T IME
2.4
OF
D AY
TIME OF DAY MENU
1. ACTIONS
2. DAY PLANS
3. SCHEDULES
4. OVERRIDE COMMANDS
5. SET LOCAL TIME
6. ADVANCED TIME SETUP
7. DAYLIGHT SAVING SETUP
Figure 137 – Time of Day menu
Actions are programmed calls to pattern changes, transit action plans, TOD
override commands, auxiliary functions or special functions.
A Day Plan specifies what actions happen during the course of a day. Up to 16
actions can be called in a single day plan.
A Schedule is a Year Plan, which specifies what days of the year a given Day Plan
will be used.
Note
Generally, TOD programming is the easiest for first time controller programmers
to understand, especially if programming is performed starting with schedules
(page 161), followed by day plans (page 160), and finally actions (page 156).
155
Time of Day Actions Menu
This menu provides access to the two kinds of Time of Day actions: Event Plans and
Auxiliary/Special Functions.
2.4.1
OF
D AY > 1.A CTIONS
TIME OF DAY ACTIONS
1. PLANS
2. AUXILIARY & SPECIAL FUNCTIONS
Figure 138 – Time of Day Actions menu
Action Plans Screens
The Actions screens provide slots for the definitions of up to 48 Time of Day actions (6
pages of actions, eight independent actions defined on each page.) Actions are calls
upon a specific ‘pattern’, which is used to change the parameters controlling the
intersection at the programmed time of day. An action can also order a change in the
active TSP action plan and/or place several calls to TOD override commands.
M AIN M ENU > 4.T IME
OF
D AY > 1.A CTIONS > 1.P LANS
2.4.1.1
TOD ACTION
1 of 6
PAT = 0..255
TSP = 0..48
Actn :
1
2
3
4
5
6
7
8
PATT :
TSP :
1
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
C
O
M
M
A
N
D
X
1:
2:
3:
4:
5:
6:
7:
8:
Figure 139 – Time of Day Actions screen
Actn – This is the Action number that can be called by a Time of Day plan. A Day Plan
calls this number to perform one of these user-defined actions.
PATT – This is the NTCIP pattern that is initiated when this TOD Action is called. This is
the pattern that this action is ‘calling’. The value can be any of the NEMA patterns (1
through 48) as defined on the Coord pattern screens (MM.2.3.2), any of the Interval156
Time of Day Menu
based patterns (101 through 228) as defined on the Timing COS Data screens
(MM.2.7.1.1), the Free pattern (254) or the Soft Flash pattern (254).
TSP – This is the Transit Signal Priority Plan (0 through 48) that goes into effect
whenever this TOD Action is called. (Refer to “Chapter 10 — Transit Signal Priority”
starting on page 285.)
COMMAND – The eight numbered ‘COMMAND’ rows that align under each action
column, correspond to the eight Commanded TOD Action Numbers on Screen 2.4.4 (i.e.
‘Override Commands’). When a set of Override Commands are programmed and saved
under a given Commanded TOD Action Number, that numbered set of commands can
be called from within the TOD schedule. This is done by placing an ‘X’ to the right of the
COMMAND row and under the desired TOD ACTION event column.
The example shown in Figure 140, will turn on all of the Override Commands that
are linked to COMMANDED TOD ACTION Number 1, during the Days and Times
that TOD ACTION event 1 is programmed to be on. Up to 99 commands can be
assigned to each override command. (See “Example of Schedule Programming
The following three examples show some commonly programmed schedules for time of
day operation.
2.4.3.2
TOD SCHEDULES
PG 2of32
ENTRY 02
SCHEDULE J F M A M J J A S O N D
MONTH
X X X X X X X X X X X X
SCHEDULE S M T W T F S
DAY
X X X X X
1111111111222222222233
SCHEDULE 1234567890123456789012345678901
DATE
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
SCHEDULE DAY PLAN
2
Figure 146 – Typical Weekday Schedule Day Plan, valid all year
2.4.3.3
TOD SCHEDULES
PG 3of32
ENTRY 03
MONTH
DAY
X
X
1111111111222222222233
SCHEDULE 1234567890123456789012345678901
DATE
SCHEDULE DAY PLAN
3
Figure 147 – Typical Weekend Schedule Day Plan, valid all year
157
2.4.3.4
TOD SCHEDULES
PG 4of32
ENTRY 04
MONTH
X
DAY
X X X X X X X
1111111111222222222233
SCHEDULE 1234567890123456789012345678901
DATE
X
SCHEDULE DAY PLAN
4
Figure 148 – Day Schedule Day Plan for New Year’s Day
The schedule shown in Figure 148 would be called an ‘Exception’ or an ‘Exception Plan’
in some older NEMA controllers. The ATC does not have explicit exception plans,
instead one must simply program an alternate schedule that is valid for the desired
dates.
Override Commands Screen” on page 162 for directions on programming these
commands.)
2.4.1.1
PAT = 0..255
EVENT:
1
2
3
PATT :
TSP :
1
1
C
O
M
M
A
N
D
X
1:
2:
3:
4:
5:
6:
7:
8:
2
1
3
1
TOD ACTION
1 of 6
TSP = 0..48
4
5
6
7
8
4
1
5
1
6
1
7
1
8
1
Figure 140 – Time of Day Action COMMAND - Example
Use the
158
button to access the other TOD Action Plan screens.
Time of Day Menu
Auxiliary and Special Functions Screens
These screens are used to attach auxiliary and special function outputs to any of the
available TOD Actions. These actions and special functions (six screens, each showing
eight action columns) are just amended to each of the 48 available TOD actions
described in the previous topic.
M AIN M ENU > 4.T IME
OF
2.4.1.2
D AY > 1.A CTIONS > 2.A UXILIARY & S PECIAL F UNCTIONS
TOD ACTION
Actn :
1
AUX 1:
2:
3:
SPC 1:
2:
3:
4:
5:
6:
7:
8:
X
2
3
4
5
6
1 of 6
7
8
X
X
Figure 141 – Auxiliary/Special Function Assignment
Use the
and
buttons to navigate between the six auxiliary/special function
assignment screens, to access any of the 48 available TOD actions.
AUX – Once activated on this screen against a scheduled TOD Action, this output will
go low (0 VDC). To use the specified output, it will need to be mapped to a connector or
BIU pin using the I/O Mapping features (MM.2.1.5.4). In the function assignment
screens under I/O mapping, these outptus are shown as TBC Auxiliary 1, 2, and 3,
visible on Page 7 of 63 of the TS2 function screens, as shown below. (The exact screen
number will depend on which I/O module type and connectors are being mapped.)
Disabled Red Monitor
TBC Auxiliary 1
TBC Auxiliary 2
TBC Auxiliary 3
Watchdog
Phase Check 1
Phase Check 2
Phase Check 3
Phase Check 4
Phase Check 5
Phase Check 6
Phase Check 7
(~) ARE ASSIGNED
PG07of63
[O]
[O]
[O]
[O]
[O]
[O]~
[O]~
[O]~
[O]~
[O]~
[O]~
[O]~
[HLP] HELP SCREEN
Figure 142 – Auxiliary outputs in the I/O mapping screens
SPC – When a check (‘X’) is placed in one of these slots, the TOD Action Event will
activate this Auxiliary output on the controller. There are eight available Special Function
outputs. These NTCIP functions are User Defined outputs.
159
Once activated on this screen against a scheduled TOD Action, a special function output
will go low (0 VDC). To be used in the cabinet, the output will need to be mapped to the
desired connector or BIU pin using the I/O Mapping feature (MM.2.1.5.4). The Special
function outputs are shown as ‘Sys Special Func 1-8’, visible on Pages 12 and 13 of the
TS2 function screens, as shown below. (The exact screen number where these
functions appear depends on which I/O module type and connectors are being mapped.)
Sys Special Func
Sys Special Func
Sys Special Func
Sys Special Func
Sys Special Func
Sys Special Func
Sys Special Func
Queue Jump 1
Queue Jump 2
Queue Jump 3
Queue Jump 4
Queue Jump 5
(~) ARE ASSIGNED
2
3
4
5
6
7
8
PG13of63
[O]
[O]
[O]
[O]
[O]
[O]
[O]
[O]
[O]
[O]
[O]
[O]
[HLP] HELP SCREEN
Figure 143 – Special Function outputs in the I/O mapping screens
Day Plan Screens
Up to 32 day plans can be configured using these screens, one per page. Each day plan
calls out one or more of the action plans configured on the Action Plans screens of the
TOD menu (MM.2.4.1). Each event during the day plan is composed of an action,
along with an hour (military time) and minute for the action to occur. Day plans are then
called out in Schedules.
2.4.2.1
TOD DAY PLANS
DAY PLAN
OF
D AY > 2.D AY P LANS
PG 1of32
1
EVENT #
HOUR
MIN
ACTION
1
22
30
1
2
23
0
15
3
0
0
0
4
0
0
0
5
0
0
0
6
0
0
0
7
0
0
0
8
0
0
0
EVENT #
HOUR
MIN
ACTION
9
0
0
0
10
0
0
0
11
0
0
0
12
0
0
0
13
0
0
0
14
0
0
0
15
0
0
0
16
0
0
0
Figure 144 – Time of Day - Day Plan Screen
The above example will call TOD Action number 1 at 10:30pm and then action number
15 at 11:00pm. Use the
plan screens.
160
and
keys to navigate between the 32 available day
Time of Day Menu
Event # – Each Day Plan can have up to 16 events, each defined by the time of day that
the event occurs, and the Action to call at that time. This is non-editable piece of text
that labels each event ‘box’ in the day plan. If the action associated with the event is ‘0’
(zero), then that particular event is ignored.
Hour – This is a two digit number that indicates the hour in which the action should
occur. This is a military representation of the time, so the hour after midnight would be
represented by ‘0’, and 2:00 in the afternoon would be represented by ‘14’.
Min – This is the minute in the hour when the action will be called. Valid values for Min
are any number between 0 and 59.
Action – This is the number of the Action that will be called at this event’s time. If the
value is ‘0’ (zero), then the event is ignored by the controller. Actions are defined on the
screens located at MM.2.4.1.1 and MM.2.4.1.2.
Schedule Screens
A Schedule is also known as a Year Plan. The Schedule makes the connection between
the controller’s internal clock/calendar and the programmed Day Plans/Events/Actions of
the Time of Day programming. Specifically, it defines what months, days of the week,
and days of the month of a generic year will call each of the controller’s Day Plans.
There are 32 schedules that can be configured, one per screen. All schedules are
followed by the controller, but if the same day is assigned to multiple day plans, the
highest numbered Schedule will take precedence.
2.4.3.1
TOD SCHEDULES
OF
D AY > 3.S CHEDULES
PG 1of32
ENTRY 01
MONTH
DAY
X X X X X X X
1111111111222222222233
SCHEDULE 1234567890123456789012345678901
DATE
SCHEDULE DAY PLAN
1
Figure 145 – Time of Day Schedules Screen
Use the
and
keys to navigate to the rest of the TOD Schedule screens.
Entry – This is the number of the currently visible Schedule. This indicates the priority
of the Schedule. Schedule 1 has the highest priority, and Schedule 32 has the lowest. If
a day is not defined in the higher priority schedule, the controller looks in the next lower
priority Schedule to see if a Day Plan for it is defined there, and so on.
Month – Selects which month or months of the year to apply this schedule’s Day Plan.
Day – Selects which days of the week in the above month to apply this schedule’s Day
Plan. The Day and Date selections are mandatory. Both day and date values must be
entered.
161
Date – Selects which dates of the month to apply this schedule’s Day Plan. The Day and
Date selections are mandatory. Both day and date values must be entered.
Schedule Day Plan – This is the Day Plan that is called by this Schedule on the months
and days selected above.
Note
Do not assign the same Day Plan number to multiple entries/schedules. The
highest numbered schedule will take precedence and cause a programmed
entry/schedule to be skipped. Use a scheduled Day Plan number only once.
Example of Schedule Programming
The following three examples show some commonly programmed schedules for time of
day operation.
2.4.3.2
TOD SCHEDULES
PG 2of32
ENTRY 02
MONTH
DAY
X X X X X
1111111111222222222233
SCHEDULE 1234567890123456789012345678901
DATE
SCHEDULE DAY PLAN
2
Figure 146 – Typical Weekday Schedule Day Plan, valid all year
2.4.3.3
TOD SCHEDULES
PG 3of32
ENTRY 03
MONTH
DAY
X
X
1111111111222222222233
SCHEDULE 1234567890123456789012345678901
DATE
SCHEDULE DAY PLAN
3
Figure 147 – Typical Weekend Schedule Day Plan, valid all year
162
Time of Day Menu
2.4.3.4
TOD SCHEDULES
PG 4of32
ENTRY 04
MONTH
X
DAY
X X X X X X X
1111111111222222222233
SCHEDULE 1234567890123456789012345678901
DATE
X
SCHEDULE DAY PLAN
4
Figure 148 – Day Schedule Day Plan for New Year’s Day
The schedule shown in Figure 148 would be called an ‘Exception’ or an ‘Exception Plan’
in some older NEMA controllers. The ATC does not have explicit exception plans,
instead one must simply program an alternate schedule that is valid for the desired
dates.
Override Commands Screen
This is an array of screens (Actions 1 through 8, Events 0 through 99) that is 8 screens
wide by 10 screens up and down. Use the number keys on the keypad to jump between
Actions 1 through 8. Use the
and
keys to scroll up and down between the 10
event screens. These are commands that can be called by individual TOD plans, or by a
central override, to change the operation of the intersection or to call special functions
within the cabinet hardware.
2.4.4
COMMANDED
TOD
ACTION Number 1
OF
D AY > 4.O VERRIDE C OMMANDS
PG 1of10
0.not assigned(0)
:
1.not assigned(0)
:
2.not assigned(0)
:
3.not assigned(0)
:
4.not assigned(0)
:
5.not assigned(0)
:
6.not assigned(0)
:
7.not assigned(0)
:
8.not assigned(0)
:
9.not assigned(0)
:
NXT to select event, 0 to clear event
Press 1 to 8 to select Action Number
Figure 149 – Override Commands Screen
To change an event setting, press a number key to select a command in the range of 1
to 8, then the
/
keys to navigate to the correct screen, and press the
key combination to enter Edit mode. Once in edit mode, use the
and
,
keys to
163
move the blinking cursor to the event you wish to change, then press the
select one of the following event calls:
key to
Table 21 – Available TOD Override Commands
Parameter value
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
Override Command
Not Assigned
Unit Min Recall
Unit W.R.M. (Walk Rest Modifier)
Phase CNA1 (Call-to-Non-Actuated)
Phase CNA2
Phase Min Recall
Phase Max Recall
Phase Ped Recall
Phase Soft Recall
Phase Dual Entry
Phase SimGap Dis (Simultaneous Gap-Out Disable)
Phase Actd Riw (Actuated Rest-in-Walk)
Phase Omit
Peds Omit
Ring Max 2
Ring Max Inhibit
Ring Red Rest
Ring Omit Rclr (Ring Omit Red Clearance)
Ring Ped Recle (Ring Pedestrian Recycle)
Per Phs FDW (Per-phase flashing don’t walk)
Exc Ped Enab (Exclusive Pedestrian Enable)
Unit SimPedClr (Simultaneous Pedestrian Clearance)
Generally, there are four types of circuit overrides: Unit, Phase, Ring and Feature. If a
unit circuit override is selected, no further action is required to define the command.
However, if a phase, ring or feature circuit override is selected, use the
key to
navigate to the right side of the colon (:) and enter the desired ring number(s), phase
number(s) or feature number(s) the circuit override needs to be applied against. Use the
alphanumeric keypad to type in all of the ring or phase numbers to which the command
should be applied. Use the
button to backspace over a typed character. When
finished editing all desired command lines, press
save the changes.
,
again to exit Edit mode and
Commands 1 through 18 have been standard NEMA inputs for four decades and should
not require further explanation. The subsequent three override commands are described
below.
per phase FDW – This is the TOD activated feature FDW THRU YEL and FDW THRU
YEL & RED that are globally enabled by phase on the Phase Options screen
(MM.2.2.8). This feature will extend Pedestrian Clearance (FDW) into the Yellow, or
Yellow and Red, Clearances programmed for a particular phase. This feature is not
recommended by Peek, but exists for end-user requirements.
164
Time of Day Menu
excl ped enab – This is the TOD activated feature for Exclusive Pedestrian (XPED) that
can be globally activated on the Exclusive Pedestrian screen (MM.2.1.0). Each of the
four XPEDs can be run by TOD here, if GLOBAL ENABLE has been set to NO, and all
six required programming entries are correctly accomplished. Use the Green Arrow Key
to move the cursor to the right of the column of colons, enter and save the desired
XPED number. It can be any value from 1 to 4. See page 128 for more details on XPED
programming.
unit SimPedClr – This is the TOD activated feature for Simultaneous Pedestrian
Clearance that can be globally activated on the USTC Misc Menu screen (MM.2.1.7).
Simultaneous flashing Don’t Walk for concurrent pedestrian phases with unequal walks
can be run by time of day programming here, as long as Simultaneous FDW has been
set to NO. Moving the cursor to the right of the column of colons is not required here, as
this is a Unit override feature. Refer to page 121.
Example of a Set of TOD Override Commands
2.4.4 COMMANDED
TOD
ACTION Number 1
PG 1of10
0.unit min recall(1):
1.phs ped recall(7) :2468
2.ring max2(14)
:12
3.excl ped enab(20) :1
4.not assigned(0)
:
5.not assigned(0)
:
6.not assigned(0)
:
7.not assigned(0)
:
8.not assigned(0)
:
9.not assigned(0)
:
Press 1 to 8 to select Action Number
Figure 150 – Example Override Commands screen
The TOD override programming shown above will activate a unit (i.e. all 16 vehicle
phases’) minimum recall; place pedestrian recalls on phases 2, 4, 6 and 8; apply Max 2
limits on all phases assigned to rings 1 and 2; and enable the exclusive pedestrian #1
feature. These four circuit overrides will become active any time an ‘X’ appears to the
right of Command 1, aligned under an Action column on the Action screen (MM.2.4.1.1)
and that action has been called by the currently active day plan.
165
Set Local Time Screen
This screen sets the date and time for the internal real-time clock of the ATC.
2.4.5
YEAR: 2012
HOUR: 8
SET LOCAL TIME
MONTH: 01
MINUTE: 52
OF
D AY > 5.S ET L OCAL T IME
PG1OF1
DAY: 11
SECOND: 52
Current Timezone: EASTERN
DST Status: Enabled
Timezone and DST cannot be edited from
this page. Use the Advanced Time Setup
and Daylight Saving Settings pages,
accessible from the previous menu.
Figure 151 – Time Set Screen
As the screen states, the Current Timezone and DST Status values cannot be edited on
this screen. Timezone is set on the Advanced Time Setup screen (MM.2.4.6). DST is
set on the Daylight Saving Setup screen (MM.2.4.7).
Setting the date and time settings here is fairly straightforward, however we recommend
that you choose your timezone and DST values first, and then return here to set the
clock and calendar.
166
Time of Day Menu
Advanced Time Setup Screen
This screen should be the first one programmed to set the controller’s time and date
values. The easiest way to manage time and date programming on the ATC is to set the
Local Time Differential here, then return to the Time Set screen (MM.2.4.5) to set the
local Standard time and date. This will automatically fill in the global time values on this
screen. Or one can program everything from right here, if one is comfortable entering
the time and date to match Greenwich Mean Time (GMT). Either method will work.
2.4.6
ADVANCED TIME SET
OF
D AY > 6.A DVANCE T IME S ETUP
PG1OF1
GLOBAL TIME HOUR...............13
GLOBAL TIME MINUTE.............53
GLOBAL TIME SECOND.............21
GLOBAL YEAR....................2012
GLOBAL MONTH...................01
GLOBAL DAY.....................11
LOCAL TIME DIFFERENTIAL........-18000
PATTERN SYNC...................00000
(MINUTES AFTER MIDNIGHT)
Figure 152 – Advanced Time Setup screen
Use the
,
keypad combination to enter and exit Edit mode. An ‘E’ will show up
in the upper right corner when you are in Edit mode. Use the up and down arrow buttons
to switch between the fields. The Global Time and Date values are the numerical values
of the current date and time at Greenwich, England. The Differential is the offset, in
seconds, from Greenwich time. There are 3600 seconds for each hour your time zone is
offset from GMT. Time zones to the West of the Meridian are a negative differential (i.e.
the time is earlier), and zones to the East of the Meridian have a positive differential (the
time is later.)
Global Time Hour – Two-digit value, in 24-hour format, for current GMT hour (00-23).
This value will be calculated automatically if the Local Time Differential is set on this
screen and then the local time is entered on the Set Local Time screen.
Global Time Minute – Two-digit value indicating the current minutes past the hour at
Greenwich (00-59). This value will be calculated automatically if the Local Time
Differential is set on this screen and then the local time is entered on the Set Local Time
screen.
Global Time Second – Two-digit value indicating the current seconds past the minute
at Greenwich (00-59). This value will be calculated automatically if the Local Time
Differential is set on this screen and then the local time is entered on the Set Local Time
screen.
Global Year – Four-digit value for current year date in GMT. This value will be
calculated automatically if the Local Time Differential is set on this screen and then the
local time is entered on the Set Local Time screen.
167
Global Month – Two-digit value for current calendar month in GMT (01-12). This value
will be calculated automatically if the Local Time Differential is set on this screen and
then the local time is entered on the Set Local Time screen.
Global Day – Two-digit value for current calendar day in GMT (01-31). This value will be
calculated automatically if the Local Time Differential is set on this screen and then the
local time is entered on the Set Local Time screen.
Local Time Differential – This is a six-digit value representing the amount of time, in
seconds, between GMT and local Standard time. You will need to set the plus or minus
symbol first (using the
and
buttons), and then press the
button to switch
to the numeric part of the time differential value. Negative values indicate times to the
west of Greenwich. Positive values indicate times east of Greenwich.
In the Western hemisphere, some common Local Time Differential values are:
Eastern Time Zone – 5 hours or -18000 seconds.
Central Time Zone – 6 hours or -21600 seconds.
Mountain Time Zone – 7 hours or -25200 seconds.
West Coast Time Zone – 8 hours or 28800 seconds.
More generally, to calculate this value use this formula:
LTD = X hours (between GMT and local Standard time) × 60 minutes/hour × 60 seconds/minute
Pattern Sync — For coordinated operation, all of the controllers in the artery need to
have a common ‘zero’ point to use to calculate their offset timers. Typically, the default
time when the cycle offset is set back to zero is midnight of every day. But if all of the
controllers along the artery suddenly generate a large offset at midnight due to this
syncing action, they will all suddenly start large offset seeking timing actions, which
could cause sudden changes in split times right after midnight. Many municipalities have
opted to set this sync time to occur later, when traffic is lighter. This value is the number
of minutes after midnight when this pattern sync should occur. For example, if the
pattern sync is to occur at 2:00 am, all of the controllers in the system should have the
Pattern Sync parameter set to 120.
168
Time of Day Menu
Daylight Saving Setup Screen
This screen provides options to view, modify, or disable the daylight saving parameters
for the ATC controller. Daylight saving time, or ‘Summer Time’ in some countries, is the
adjustment of local time to allow for a longer daylight period in the afternoon and a
shorter amount of daylight in the morning. This is typically started in early Spring as the
days begin to get longer, and ended in late Fall as the days shorten. (This is, of course,
true in both the Northern and Southern hemispheres, although Spring starts in March in
the north and in September in the south, so the dates will be different.)
The appearance of this screen is modal; it changes based on whether DST is enabled or
not. Keyboard shortcuts at the bottom of this screen provide context-sensitive controls
for enabling, disabling, and perform other actions on the DST settings.
2.4.7 DST Entry Disabled
OF
D AY > 7.D AYLIGHT S AVING S ETUP
PG1of8
[C]Clear Entry, [D]Load Entry Default
[F]Disable DST (All Entries)
Figure 153 – Daylight Saving Time Settings screen
Daylight Savings Time (DST) as shown on the screen above is set to DST Entry
Disabled until programmed for the first time. The three command choices at the bottom
of the screen are selected by pressing the keypad letter indicated in the brackets, [C],
[D] and [F]. Since DST is currently disabled, the selections of [C] and [F] will have no
effect. If automatic DST time corrections are desired, press [D] which loads the current
DST set of parameters corresponding to the published DST values in North America:
The Default DST begins on the second Sunday in March, at 2:00 AM local time.
Local time is set forward one hour, so it becomes 3:00 AM local time.
The Default DST ends on the first Sunday in November, at 1:00 AM local time.
Local time is set backward one hour, so it becomes 12:00 midnight.
When enabled, DST presents a summary view, showing the current programmed values
for when time changes will occur. The default load will look like this:
169
2.4.7 DST by Occurences of DOW
PG1of8
DST Begins in the month of <March>
on the <Second> <Sunday>
at 01:00:00 o’clock.
that occurs on or after the <1st>
DST Ends in the month of <November>
on the <First> <Sunday>
at 01:00:00 o’clock.
that occurs on or after the <1st>
Minutes to Adjust time: 60
[C]Clear Entry, [D]Load Entry Default
[F]Disable DST (All Entries)
Figure 154 – Default DST Enabled values
For most locations, that is all the DST programming that’s required. Some users may
need to refine these parameters further depending on their local laws. To edit any of the
DST parameters, press
appear:
,
to enter Edit mode and the following screen will
2.4.7 DST by Occurrences of DOW
PG1of8 E
Begin Month:....... 03
Begin Occur:....... 2
Begin Day of Week: 1
Begin Day of Month: 1
Begin Mins from Midnight: 0060
End Month:......... 11
End Occur:......... 1
End Day of Week:... 1
End Day of Month:.. 01
End Mins from Midnight: 0060
Minutes to Adjust Time: 0060
Week of the month
1 = Sunday
Week of the month
1 = Sunday
[A] Switch DST Entry Type to Absolute
Figure 155 – DST parameter editing screen (Default values)
This is the view that provides the most detailed parameters. There are two programming
screens available: Generic (shown above) and Absolute (Figure 156.) If the Generic
view is too extensive, press the
button to switch to the ‘Absolute’ screen, which is a
bit simpler to program but doesn’t provide all of the possible programming options.
170
Time of Day Menu
2.4.7 DST by Exact Date
PG1of8 E
Begin Date: 01/01/2000
Begin Time: 00:00:00
End Date: 01/01/2000
End Time: 00:00:00
Minutes to Adjust Time: 0060
[B] Switch DST Entry Type to Generic
Figure 156 – DST editing by exact date
The Begin Date and Time is the exact date and time to which the real time clock in the
ATC will be set forward. The End Date and Time are the exact date and time to which
the real time clock will be set backward.
Begin Month — The month of the year expressed as a number between 1 and 12 when
daylight saving should begin by setting the clock ahead one hour.
Begin Occur — If you specify a Day of the Week, below, on which occurrence in the
month should DST begin.
Begin Day of Week — Which day of the week, expressed as a number between 1
(Sunday) and 7 (Saturday) should DST begin. Combined with the above value to specify
which day of the month. (e.g. if Begin Occur = 3, and Begin Day of Week = 4, then DST
will begin on the 3rd Wednesday of the month.)
Begin Day of Month — If you specify a Begin Occur and Begin Day of Month, skip this
parameter. This is the date of the month on this screen.
Begin Mins from Midnight — The time for the Beginning DST clock adjustment to
occur, in minutes after midnight on the above day.
End Month — The month of the year expressed as a number between 1 and 12 when
daylight saving should end,
End Occur — If you specify a Day of the Week, below, on which occurrence in the
month should DST end.
End Day of Week — Which day of the week, expressed as a number between 1
(Sunday) and 7 (Saturday) should DST end.
End Day of Month — If you specify an End Occur and End Day of Month, skip this
parameter. This is the date of the month on this screen.
End Mins from Midnight — The time for the Ending DST clock adjustment to occur, in
minutes after midnight on the above day.
Minutes to Adjust Time — This option allows the real-time clock to be modified
slowly over this number of minutes, so that a sudden shift in the current time will not
cause large offset seeking activity in coordinated operation. When a non-zero number of
171
minutes are specified, the change in time will be equally divided over the duration of the
period. A typical value might be 10 to 20 minutes.
Remember to save the desired entries by exiting from Edit mode before leaving the
programming screen.
Important
After edits have been made to one or more of these settings, you
must exit Edit mode to save the new values, otherwise the values
will be lost.
As a final step, go to the Set Local Time screen (MM.2.4.5) and verify that the DST
Status shows DST Status as being ‘Enabled’.
172
Detectors Menu
DETECTORS MENU
The screens on this menu allow the configuration of detectors, including defining how
they operate and mapping them to phases.
M AIN M ENU > 2.P ROGRAMMING > 5. D ETECTORS
2.5
DETECTORS MENU
1. VEHICLE DETECTORS OPTIONS
2. VEHICLE DETECTORS TIMING
3. DETECTORS CALL PHASE
4. DETECTORS SWITCH PHASE
5. PEDESTRIAN DETECTORS
6. ENHANCED VEHICLE DETECTORS
7. ENHANCED PEDESTRIAN DETECTORS
Figure 157 – Detectors Menu
173
Vehicle Detector Options Screens
This screen is used to manually set values for individual detectors, to determine how the
detector channel functions or to change the current state of the channel. This is where
one can place a call on a detector, for example. Use the
and
keys to see the
other three screens, which show the same parameters for detectors 17 through 64.
M AIN M ENU > 2.P ROGRAMMING > 5. D ETECTORS > 1.V EHICLE D ETECTOR O PTIONS
2.5.1.1
VEH DETECTOR OPTIONS PG 1of 2
1 1 1 1 1 1 1
DET NO. 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
OPTION:
CALL.....
QUEUE....
ADD INIT.
PASSAGE..X X X X X X X X
RED LOCK.
YEL LOCK.
OCC DET..
VOL DET..
RESET....
Figure 158 – Vehicle Detector Options Screen
Note
Despite all of these per-detector functions, it’s important to remember that
detectors are not associated with individual phases on this screen. The
Detector Call Phases screen (MM.2.5.3 ) and Vehicle Detector Options
screens (MM.2.5.1 ) must also be programmed.
Call – Placing a check (‘X’) in this row under a detector indicates that a detection will
place a call for service on the phase associated with this detector. This call will appear
whenever the phase in question is not timing a Green interval.
Queue – Place a check (‘X’) on this row under a detector to indicate that this detector is
used for gap detection. A queue detector will extend the Green interval of the assigned
phase until a gap occurs, or until the Green phase times longer than the optional queue
limit.
Add Init – An ‘X’ placed in this row beneath a detector indicates that that detector will be
used to generate detection inputs for the Added Init function of Initial Green extension.
The method used is to count the vehicle detections from all detectors associated with
the phase, take the detector with the highest count total, and multiply that count total by
the Added Init time step. This extra time is then compared to the minimum and
maximum time in effect and utilized, but only if it is greater than the minimum and less
than the maximum.
Passage – When this row is checked (‘X’) the controller will maintain a reset of the
associated phase’s Passage Timer for the duration of the detector actuation, while the
phase is green.
174
Detectors Menu
Red Lock – When this row is checked (‘X’) the controller will lock a call to the assigned
phase(s), if an actuation occurs while the phase is not timing Green or Yellow.
Yel Lock – When this row is checked (‘X’) the controller will lock a call to the assigned
phase, if an actuation occurs while the phase is not timing Green.
Occ Det – When this row is checked (‘X’) then this detector is marked as an ‘occupancy
detector’. An occupancy detector collects data for the associated phase’s occupancy
calculations, allowing it to calculate the percentage of time a vehicle is in the sensing
field for that detector..
Vol Det – When this row is checked (‘X’) then this detector is marked as a ‘volume
detector’. A volume detector collects data for the associated phase’s volume
calculations.
Reset – This sends a reset command to the detector, forcing it to return to FALSE (0)
after the reset command. A reset command is an interactive control that is not saved in
the ATC database. To activate this Reset command, place this screen in Edit mode,
navigate the cursor under the detector number to be reset. Press the
button, and
the reset will be sent. When Edit mode is exited, the ‘X’ will not be saved.
Note
A reset command may reset more than one detector, if other detectors are
attached to a common reset channel, as is often the case.
Note
For all of these per-detector functions, it’s important to remember that the
detectors are not associated with individual phases on this screen. That
mapping is defined on the “Detector Call Phases Screen”, which is described on
page 177.
175
Vehicle Detector Timing Screens
This screen is used to enter timing modifications to the operation of each of the 64
detection channels.
M AIN M ENU > 2.P ROGRAMMING > 5.D ETECTORS > 2.V EHICLE D ETECTOR T IMING
2.5.2.1
VEH DETECTOR TIMING PG 1 of 8
DET NO.
DELAY:
1
0
2
0
3
0
4
0
5
0
6
0
7
10
8
0
EXTEND:
0
0
0
0
0
0
0
0
QUEUE:
0
0
0
0
0
0
0
0
NO ACT:
0
0
0
0
0
0
0
0
MAX PRS:
0
0
0
0
0
0
0
0
ERR CTS:
0
0
0
0
0
0
0
0
FAIL T:
0
0
0
0
0
0
0
0
Figure 159 – Vehicle Detector Timing Screen
Delay – A number between 0.0 and 255.0 that indicates the number of seconds that are
added as a delay on the input whenever the detector’s output goes ON. (True). This
delay is added whenever the detector’s assigned phase is not green.
Extend – Previously known as the ‘Stretch’ parameter, this is the number of seconds (025.5) that a call is extended beyond the point where the actual detector’s output goes Off.
This extention is added only when the detector’s assigned phase is Green.
Queue – A number between 0 and 255 that indicates the number of seconds that the
actuation from a queue detector will continue into the associated phase’s green. This
time begins when the phase becomes green and when this count expires, associated
detection inputs will be ignored. (This time may be shortened by other overriding
parameters assigned to this phase, including Max times, Force-Offs, etc.)
No Act – A number between 0 and 255 that indicates the number of minutes used by
the detector’s No Activity diagnostic. If an active detector does not exhibit an actuation
for the specified period of time, it is considered a fault and the detector is classified as
‘failed’. A value of ‘0’ disables the No Activity diagnostic for this detector. A failed
detector can disable the Add-Init, passage, and extension timers on the associated
phase, among other side effects, so use this feature with care.
Max PRS – This is the length of time in minutes, from 0 to 255 minutes used by the
detector’s Maximum Presence diagnostic. If an active detector exhibits continuous
detection for too long a period, it is considered a fault and the detector is classified as
‘failed’. A value of ‘0’ disables the Maximum Presence diagnostic for this detector. A
failed detector can disable the Add-Init, passage, and extension timers on the
associated phase, among other side effects, so use this feature with care.
ERR CTS – Used by the Detector Erratic Counts diagnostic, this is the number of counts
per minute, over which, the detector will be considered faulty. This can be any value
between 0 and 255 counts per minute. If an active detector exhibits excessive
actuations, it could be a sign of an intermittent connection in the wiring or some other
“chattering” problem. A failed detector can disable the Add-Init, passage, and extension
176
Detectors Menu
timers on the associated phase, among other side effects, so use this feature with care.
A value of ‘0’ (zero) disables the Erratic Counts diagnostic for this detector.
Fail T – The amount of time, from 0 to 255 seconds, used as the Detector Fail Time. If a
detector diagnostic (one of the above three functions) has tagged a detector input as
‘failed’, this function tells the controller to place an artificial call on the associated phase
for this many seconds during all non-green intervals. The call remains ON for this many
seconds into the green section of the phase.
Detector Call Phases Screen
This screen is used to assign the 64 detector channels to individual phases within the
intersection. Multiple detectors can be assigned to call a single phase.
M AIN M ENU > 2.P ROGRAMMING > 5.D ETECTORS > 3.D ETECTOR C ALL P HASE
2.5.3
DETECTOR CALL PHASES PG 1of 2
DET NO.
PHASE NO.
1
1
2
2
3
3
4
4
5
5
6
6
7
7
8
8
DET NO.
PHASE NO.
9
0
10
0
11
0
12
0
13
0
14
0
15
0
16
0
DET NO.
17
PHASE NO. 0
18
0
19
0
20
0
21
0
22
0
23
0
24
0
DET NO.
25
PHASE NO. 0
26
0
27
0
28
0
29
0
30
0
31
0
32
0
Figure 160 – Detector Call Phases Screen
When a detector is mapped to a phase, all of the detector functions and timings defined
on the previous two screens will be applied to that phase. Valid phase numbers run from
1 to 16. Values outside of this range will generate an error and require the operator to
enter a number within the proper range. If the phase number is defined as ‘0’, the
detector will not call any phase when it detects a vehicle.
Press the
button to get to page 2 of the Detector Call Phases screens, which hosts
the phase assignments for Detectors 33 through 64.
177
Switch Phases Screen
This option allows a detector’s output to be switched to another phase when its primary
phase is yellow or red. This switch of detector output only occurs when the new phase is
Green AND the detector’s normal phase is either yellow or red.
M AIN M ENU > 2.P ROGRAMMING > 5.D ETECTORS > 4.D ETECTORS S WITCH P HASE
2.5.4
DETECTOR SWITCH PHASES PG 1of 2
DET NO.
PHASE NO:
1
0
2
0
3
0
4
0
5
0
6
0
7
0
8
0
DET NO.
PHASE NO:
9
0
10
0
11
0
12
0
13
0
14
0
15
0
16
0
DET NO.
17
PHASE NO: 0
18
0
19
0
20
0
21
0
22
0
23
0
24
0
DET NO.
25
PHASE NO: 0
26
0
27
0
28
0
29
0
30
0
31
0
32
0
Figure 161 – Switch-to Phases Screen
Press the
button to get to page 2 of the Detector Switch Phases screens, which
hosts the switch assignments for Detectors 33 through 64.
Pedestrian Detectors Screen
This screen is used to configure the eight available pedestrian detector inputs.
M AIN M ENU > 2.P ROGRAMMING > 5.D ETECTORS > 5.P EDESTRIAN D ETECTORS
2.5.5
PEDESTRIAN DETECTORS PG 1of 1
PED DET#
1
2
3
4
5
6
7
8
CALL PH:
0
2
0
4
0
6
0
8
NO ACTIV:
0
0
0
0
0
0
0
0
MAX PRES:
0
0
0
0
0
0
0
0
ERR CNT:
0
0
0
0
0
0
0
0
Figure 162 – Ped Detectors Screen
Call Ph – This is the phase number associated with this detector input. When this
detector’s input goes ON, the associated phase will receive a Ped Call. A ‘0’ (zero)
indicates that there is no phase associated with this ped detector input.
No Activ – A number between 0 and 255 that indicates the number of minutes used by
this pedestrian detector’s No Activity diagnostic. If an active detector does not exhibit an
178
Detectors Menu
actuation for the specified period of time, it is considered a fault and the detector is
classified as ‘failed’. A value of ‘0’ disables the No Activity diagnostic for this detector.
Max Pres – This is the length of time in minutes, from 0 to 255 minutes used by the ped
detector’s Maximum Presence diagnostic. If an active pedestrian detector exhibits
continuous detection for too long a period, it is considered a fault and the detector is
classified as ‘failed’. A value of ‘0’ disables the Maximum Presence diagnostic for this
ped detector.
ERR CNT – Used by the Ped Detector Erratic Counts diagnostic, this is the number of
counts per minute, if exceeded, which will cause the ped detector to be considered
faulty. This can be any value between 0 and 255 counts per minute. If an active detector
exhibits excessive actuations, it could be a sign of an intermittent connection in the
wiring or some other “chattering” problem. A value of ‘0’ (zero) disables the Erratic
Counts diagnostic for this pedestrian detector input.
179
Enhanced Vehicle Detectors Screen
This screen is used to configure one vehicle detector input to call multiple vehicle
phases.
M AIN M ENU > 2.P ROGRAMMING > 5.D ETECTORS > 6.E NHANCED V EHICLE
D ETECTORS
2.5.6.1
ENH VEH DET
PG 1of64
1 1 1 1 1 1 1
PHASES 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
CALL....
X
Figure 163 – Enhanced Vehicle Detectors screens
Use the
and
keys to navigate between the 64 detector assignment screens.
The page number (1-64) corresponds to the vehicle detector. This programming is in
addition to that programmed on the Detector Call screen (MM.2.5.3). This screen’s
value(s) take precedence over the Detector Call screen values.
CALL – An ’X’ under a phase number will allow that numbered detector to call that
vehicle phase. Multiple phase numbers are permitted. A space ‘ ‘ under a phase
number indicates that this phase is not associated with this vehicle detector’s input.
Enhanced Pedestrian Detectors Screen
This screen is used to configure one pedestrian detector input to call multiple pedestrian
phases.
M AIN M ENU > 2.P ROGRAMMING > 5.D ETECTORS > 7.E NHANCED P EDESTRIAN
D ETECTORS
2.5.7.1
ENH PED DET
PG 1of 8
1 1 1 1 1 1 1
PHASES
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
CALL.... X X
Figure 164 – Enhanced Pedestrian Detetectors screen
180
Detectors Menu
The page number (1-8) corresponds to the pedestrian detector. Use the
and
keys to navigate between the 64 detector assignment screens.This programming is in
addition to that programmed on Pedestrian Detectors screen (MM.2.5.5). This screen’s
values take precedence over the Pedestrian Detectors screen’s (MM.2.5.4) values.
CALL – An ’X’ placed under a phase number will allow that numbered detector to call
that pedestrian phase. Multiple phase numbers are permitted. A space (‘ ‘) under a
phase number indicates that this phase is not associated with this pedestrian detector’s
input.
181
PREEMPTION MENU
Preemption is the process of interrupting the normal operation of the intersection in
order to run a special ‘preemption’ run, as triggered by some external signal, such as a
police, fire, train crossing, or emergency vehicle preemption call.
2.6
1.
2.
3.
4.
5.
PREEMPTION PARAMETERS MENU
ENABLES/INPUTS
ENTRY
TRACK CLEARANCE
DWELL/CYCLIC
EXIT
Figure 165 – Preemption Menu
The Preemption portion of the ATC front panel interface is described in “Chapter 8 —
Phase-based Preemption”, starting on page 251. That chapter describes phase-based
preemption.
Note
182
Interval-based preemption is handled separately under the Interval menus.
Interval-based preemption is discussed starting on page 225.
Using the Interval Menu
USING THE INTERVAL MENU
Many of the interface controls for the GREENWave software have an implicit
assumption that most users of the controller will be working with a NEMA style,
actuated, phase-based operation in their traffic cabinets. This includes the preemption,
TSP and most other parts of the interface. However, the Interval menu, located on the
Programming menu, is where most of the settings are located to operate the other type
of traffic pattern control: pre-timed intervals rather than NEMA phases.
Whereas phases assume signals are output to provide traffic ‘movements’, intervalbased operation is more concerned with what electrical outputs to activate during fixed
intervals of time. There are proponents of either type of programming, each having its
own strengths and weaknesses. Yet either method is well capable of controlling an
actuated intersection with all of the fine control one would ever need.
M AIN M ENU > 2.P ROGRAMMING > 7.P RETIMED
2.7
INTERVAL MENU
1. TIMING PLANS
2. SIGNAL PLANS
3. PREEMPTION
4. INTERVAL SKIPPING
Figure 166 – Interval Menu
Interval-based operation is described in detail in “Chapter 7 — Interval Operation”,
starting on page 213.
183
TRANSIT SIGNAL PRIORITY MENU
M AIN M ENU > 2.P ROGRAMMING > 8.T RANSIT S IGNAL P RIORITY
2.8
TRANSIT PRIORITY MENU
1. UNIT PARAMETERS
2. RUN PARAMETERS
3. ACTIONS PLANS
4. RUN CONFIGURATION
5. QUEUE JUMPING
6. SPLIT TABLE
Figure 167 – Transit Signal Priority Menu
The screens, parameters and functions of Transit Signal Priority are described in detail
in “Chapter 10 — Transit Signal Priority”, starting on page 285.
184
Chapter 6 — Coordinated Operation
This chapter describes how to set up coordinated operation on an ATC controller. The following
•
General overview of coordination, on page 186.
•
Details about the Coordination programming screens, on page 190
•
Coordination pattern consistency checking, on page 205.
185
GENERAL OVERVIEW OF COORDINATION
Coordination is the process of keeping multiple intersections working together in a
‘coordinated’ timing pattern. Coordinated timing establishes a “green wave” or “green
band” along a corridor containing multiple intersections, in order to maximize the “main
street” traffic flow. This is done by restricting when each intersection's phases can be
green, using a Master Cycle Timer. The Free Mode does not restrict when phases are
green.
The following concepts are important to understand prior to attempting coordinated
programming:
Offset – The timing difference between each intersection in a corridor and the first
intersection’s cycle timer.
Master Cycle Timer (Reference Timer) – A timer that each intersection shares which
synchronizes their Local Cycle timers to the offset time for each intersection.
Master Cycle Timer Generation – Each intersection must have the same time of day.
(1) Pattern Sync Control (Screen 2.4.6) – When 65535, a Pattern's Master Cycle
Timer starts counting from zero at the Time Base Schedule's Event calling the Pattern.
When not 65535, it is the number of minutes past Midnight (00:00:00) when the Master
Cycle Timer gets abruptly zeroed (M0) each day and begins counting from that point.
(2) Absolute Zero (screen 2.1.8) – a keyboard command that sets each Pattern's
Master Cycle Timer to zero (M0) at a pre-determined Time of Day and the timer counts
without getting abruptly zeroed.
Local Cycle Offset Reference
Point (L0) – Each intersection
has a unique point called Local
Zero that must be synchronized
to the Master Cycle
Timer/Reference Timer (common
to all intersections) with the
Pattern’s Offset Time.
Offset Seeking – An algorithm
that runs in coordinated
controllers. When the offset for
one of the controllers varies from
its assigned value, this algorithm
modifies the intersection’s timings
to restore the proper offset value.
Many of these concepts are
represented graphically in Figure
168.
Figure 168 – Master Cycle
Timer and Local Cycle Timer
illustration
186
General Overview of Coordination
In a controller running GreenWave, coordinated programming parameters are stored in
the database using the following logic:
Figure 169 – Coordination Database Structure
Table 22 – Pattern Number Descriptions
Pattern Number
1-48
Description
Phase-based Patterns – Free if Cycle Time = 0, otherwise
Coordination is assumed
49-100
Unused
101-228
Interval-Based Patterns – See “Chapter 7 — Interval Operation”,
starting on page 213 (MM.2.7.1.1, screens 1 through 16)
229-253
Unused
254
Phase-based Free – running Sequence Number 1
255
Flash
187
Pattern Changes in a Coordinated Environment
The following illustration shows how the controller decides which pattern to run at any
given time, particularly when it is running in a coordinated environment.
Figure 170 – Pattern Selection
188
1.
A new Pattern loads when the first Coordinated Phase normally starts.
2.
Offset Seeking calculations determine the optimal Pattern load point to cause the
shortest Offset Seeking time measured from the normal load point. See Figure
171 for an illustration of this process.
General Overview of Coordination
Figure 171 – Postponing Pattern Change to Sync Faster
189
COORDINATION MENU
The screens under the Coordination menu allow one to configure an ATC controller to
function using coordinated timing.
M AIN M ENU > 2.P ROGRAMMING > 3.C OORDINATION
2.3
COORDINATION MENU
1. COORDINATION VARIABLES
2. PATTERN TABLE
3. SPLIT TABLE
4. OFFSET CORRECTION EXT/REDUCE
Figure 172 – Coordination Menu
Coordination Variables Screen
This screen is where global coordination parameters are set, including default patterns,
methods of correction, and overall coordination operating modes.
M AIN M ENU > 2.P ROGRAMMING > 3.C OORDINATION > 1.C OORDINATION V ARI ABLES
2.3.1
COORD VARIABLES
PG1OF1
OPERATIONAL MODE.....000 (0-255)
CORRECTION MODE......dwell(2)
MAXIMUM MODE.........maxInhibit(4)
FORCE MODE...........fixed(3)
SYSTEM PATTERN.......000
PATT TABLE DATA TYPE.secs/ntcip/other(1)
SPLT TABLE DATA TYPE.secs/ntcip/other(1)
YIELD WINDOW PERCENT.000
Figure 173 – Coordination Variables Screen
190
Coordination Menu
Operational Mode – This number (a value between 000 and 255) sets the overall
operational mode for coordination on the ATC controller. This is a default pattern for the
controller that will override Time of Day and Sys Cmd pattern calls. This is almost
always set to zero, since any other value will prevent TOD and central system patterns
to be commanded.
Table 23 – Operational Mode values
Operational Mode
0
Definition
Automatic mode – This mode provides for coordinated operation, Free
and Flash to be determined automatically by all possible sources: Time
Based events or System Commands. This is the normal default mode for
most systems.
001 - 253
Manual Pattern mode – Coordinated operation running the specified
number pattern (Pattern 001 to Pattern 253). This selection of pattern
overrides all other pattern commands, including System Commands.
254
Manual Free mode – This mode provides for Free operation without
coordination, or Automatic Flash from any source.
255
Manual Flash mode – This mode causes the controller to run in the
Automatic Flash state, without coordination or phase-based Free
operation.
Correction Mode – Defines which coordination correction method will be used when
establishing a new or different offset from the coordinated time. This is usually used
when changing from one pattern to another. These modes are also used for recovery
from TSP operation, with some conditions. A per pattern user-selectable Max
Dwell/Add/Reduce Time (MM.2.3.2) feature controls cycle length extensions and
reductions subject to minimum phase times. The local cycle timer can be “out of sync”
with the master cycle timer upon system start-up, during pattern changes, after
preemption, or after ped override mode(POM).
Table 24 – Coordination Correction modes
Correction Mode
dwell (2)
shortway (3)
Description
When changing the offset time, the coordinator will dwell in the
coordinated phases until the desired offset is reached.
When changing the offset time, the coordinator adds or subtracts time
to/from phase timings with the aim to limit the amount of time the cycle
length changes.
addonly (4)
When changing the offset time, the coordinator adds time to phase
timings with the aim to limit the amount of time the cycle length changes.
offsetPercent
(3)
The coordinator establishes a new offset by using a user-defined, per-split,
extend/reduce timing correction strategy. Refer to “Error! Reference
source not found.” on page Error! Bookmark not defined.. This
method is used only for TSP recovery. When this option is selected, TSP
will use it, but normal coordination pattern changing recovery will use the
dwell(0) method instead.
shortway
dwell(6)
Extends the cycle length by dwelling in coordinated phase green, or
reduces the cycle length, depending on the fastest sync direction.
191
Note
In a previous version of GreenWave, there was an additional parameter used to set
the correction mode, called ‘USTC Correction Mode’. USTC Correction Mode has
been eliminated. It’s functionality has been rolled into the standard correction mode
parameter as the ‘offsetPercent (3)’ option, although it is now limited to TSP
recovery.
Maximum Mode – This parameter determines which maximum time, if any, is used
during coordinated operation. The possible values are:
Table 25 – Coordination Maximum modes
Maximum mode value
Description
maximum1 (2)
While coordination is running a pattern, the coordinator will use
Max 1 as the maximum phase time.
maximum2 (3)
While coordination is running a pattern, the coordinator will use
Max 2 as the maximum phase time.
maxInhibit (4)
Internal maximum timing is inhibited while coordination is
running a pattern.
Note
If maximum1(2) or maximum2(3) is selected for the Maximum Mode setting,
Peek recommends a max time greater than or equal to the split time to insure a
phase does not max-out before its force-off.
Force Mode – This parameter determines which ‘pattern force mode’ the ATC
coordinator will use. The possible values are:
Table 26 – Coordination Force Mode options
Mode
Description
Unused Time Allocation
Each phase will be forced to the new split
time after the phase becomes active. This
allows unused split time to be passed to the
coordinated phase.
All unused time goes to
coordinated phases.
fixed (3)
Each phase will be forced to the new split
time at a fixed position in the cycle. This
allows unused split time to pass to the
following phase.
(1)Previous phase(s)’
unused time goes to
subsequent phases and
(2)Next phase(s)’ unused
time goes to coordinated
phases.
forward(4)
Moves a green-extending phase’s force off
point forward if the next open-permissive
phase(s) have no call(s).
(1) Previous phase(s)’
unused time goes to
subsequent phases and
(2) Next phase(s)’ unused
time goes to active
floating (2)
192
Coordination Menu
phases.
Figure 174 – Force mode comparisons
System Pattern – This parameter stores a SYS CMD pattern number. This is the value
set by the central system to control the device’s pattern from central. The possible
values are:
Table 27 – System Pattern modes
System Pattern mode
Description
0
Standby mode – The system relinquishes control of the device. The
controller runs the pattern specified by TOD.
1 - 253
Pattern # – The pattern specified by TOD if Operational Mode = 0 or
the pattern equal to Operational Mode's value (1-255).
254
Free mode – The controller runs in Free mode.
255
Flash mode – A call for the device to enter Automatic Flash.
If an unsupported or invalid pattern is called by the central system, the ATC will run in
Free mode. The value of System Pattern is ignored if the controller is in Backup mode.
Any changes sent to this value will reset the Backup timer to zero (0).
193
Patt Table Data Type –The pattern table data type affects the pattern tables at MM.2.3.2,
including the values for offset, offset correction threshold, early yield time and max
dwell/add/reduce time. The default value is 1.
Table 28 – Pattern Table Data Type
Data Type
Description
(1)
secs/ntcip/other – The Pattern Tables will state TIMES IN SECONDS;
offset parameter measured in whole seconds.
(2)
percent – The Pattern Tables will state TIMES IN PERCENT; offset
parameter measured in percentage (0-100%) of cycle length.
Splt Table Data Type – The Split Table Data type affects split tables at MM.2.3.3 including the
values: split, start perm and end perm, and all of the parameters in the Offset Correction Split
Table (MM.2.3.4) as well as the Transit Signal Priority Split Table (MM.2.8.6.) The default value
is 1.
Table 29 – Split Table Data Type
Data Type
Description
(1)
secs/ntcip/other – The split tables will state times in
seconds; split parameter measured in whole seconds.
(2)
percent – The split tables will state times in percent; split
parameter measured in percentage (0-100%) of cycle
length.
Yield Window Percentage – The amount of time (as a percent of cycle length) after the
last coordinated phase yield point during yield permissive strategy that all permissive
windows close if no non-coordinated phase calls occur during the coordinated phases.
The default value is 0. The Yield Window Percentage setting does nothing in these
situations:
194
1.
Non-coordinated phases are "on"
2.
A manual permissive strategy is selected
3.
A single permissive strategy is selected
4.
A multiple permissive strategy is selected
Coordination Menu
Pattern Table Screens
The second item on the Coordination Menu accesses the Pattern Table screens.
Coordinated intersections don’t function using a single cycle time. Rather, they work with
a cycle, offset, and split goal that is then coordinated with the other intersections on a
roadway artery. These screens allow an operator to define up to 48 cycle-offset-split
patterns, one per screen. Each cycle-offset-split combination is known as a ‘pattern’.
Note
All of the interval-based timing patterns are defined on the Interval
menu screens. They are separate from the 48 phase-based patterns
defined here.
M AIN M ENU > 2.P ROGRAMMING > 3.C OORDINATION > 2.P ATTERN T ABLE
2.3.2.1 COORD PATTERN TABLE PG1of48
PATTERN # 1
TIMES IN SECONDS
CYCLE. . .120
OFFSET. . .
0
SPLIT NO ..1
SEQUENCE NO. 1
OFFSET CORRECTION THRESHOLD . 0
LOCAL ZERO PHASE. . . . . . . 2
LOCAL ZERO MODE . . . . . . . green(2)
EARLY YIELD MODE. . . . . . .
0
PERMISSIVE STRATEGY . . . . . yield(3)
MAX DWELL/ADD/REDUCE TIME . .
0
PEDESTRIAN OVERRIDE . . . . . NO
Changes to TIMES IN PERCENT
if the Patt Table Data Type is set so
Figure 175 – Pattern Table screen (48 pages, one page per pattern)
CYCLE – (NTCIP 1202, default = zero, Range = 0, 30-255): the total time (in whole
seconds) to run every phase in the Sequence once. See Table M Checks 1, 2, 3 and 6.
A zero (0) CYCLE time causes Free Mode. The Pattern’s SPLIT NO uses: non-zero
Split Times as new Maximum Green times; AND all Split Modes values except none (2).
The Pattern’s SEQUENCE NO is the running Sequence.
Note: A Time of Day Sequence change during Free Mode must be done using a
Zero CYCLE TIME Pattern 1-48 with the desired SEQUENCE NO.
OFFSET – (NTCIP 1202, default 0, Range 0-254) -- The time (in whole seconds or
percent of Cycle Time) to sync the Pattern’s Local Cycle Timer to the Master Cycle
Timer. The actual offset is the Master Cycle Timer value minus the Local Cycle Timer
value. When “In Sync,” the actual offset equals this parameter’s value in whole seconds
or percent of Cycle Time as specified by Patt Table Data Type, on Screen 2.3.1.
SPLIT NO – (NTCIP 1202, default 1, Range 1-16) -- Determines the Split Tables
(screens 2.3.3.1-16, 2.3.4 pages 1-16, 2.8.6 pages 1-16) to run during the Pattern.
SEQUENCE NO – (NTCIP 1202, default 1, Range 1-16) -- Determines the Sequence
(screens 2.1.6.1-16) to run during the Pattern.
195
OFFSET CORRECTION THRESHOLD – (Peek, default 0, Range 0-255) -- Applies
during TSP Recovery and if the Correction Mode (Screen 2.3.1 Coord Variables) is
offsetPercent (3). If TSP causes the Coordinated Phases to return to Offset Correction
Threshold seconds/percent later than normal, then Screen 2.3.4’s Max Extend times
sync, otherwise Screen 2.3.4’s Max Reduce times sync (per Patt Table Data Type).
Dwell Offset Correction occurs during:
1.
Pattern changes
2.
TSP recovery with zero Max Extend and Max Reduce times.
3.
TSP recovery and this parameter (when converted to seconds) is zero or exceeds
the Cycle Length.
Note: A future firmware version will support this parameter and Offset Percent
Correction Mode during non-Transit Signal Priority.
LOCAL ZERO PHASE (Peek, default 0, Range 0-16) and LOCAL ZERO MODE (Peek,
default 2, Range 2-4) determine the Local Zero location according to Table 30.
Table 30 – Local Zero Options
Local Zero Phase value
Local Zero Mode
value
The point when Local Zero occurs (assuming
every phase uses its full split)
0
does not matter
The first Coordinated Phase's green starting
point (NEMA TS2 para 3.6.2.2).
1-16
If Local Zero Phase disabled,
not in Sequence, omitted, or
zero Split Time, then Local Zero
occurs at NEMA TS2 First
Coordinated Phase’s green
starting point.
green (2)
The Local Zero Phase's green starting point.
yellow (3)
The Local Zero Phase's yellow starting point.
pedClear (4)
An Actuated Mode Local Zero Phase’s Yellow
starting Point.
A Non-Actuated Mode Local Zero Phase's Ped
Clearance starting point.
EARLY YIELD TIME – (Peek, default 0, range 0-255) The amount of time (seconds or
percentage of Cycle length) that an actuated-mode coordinated phase’s yield point
occurs prior to its force-off point to permit a gap-out. When zero, each coordinated
phase must use its full split time measured from its normal starting point (falls under Patt
Table Data Type’s jurisdiction).
For the following sequence:
Sequence: 2-1 | 4 |
6|8|
196
Coordination Menu
Figure 176 – Early Yield Time Example using Multiple Permissive Strategy
Permissive Strategy (Peek, default 4, Range 2-5) - A permissive start time and a
permissive end time form a per-phase Permissive Window that determines when the
Coordinated Phases terminate to answer calls without disrupting the Coordinated
Phases.
During all Permissive Strategies, Pedestrian Permissive Periods are calculated
automatically.
During yield(3), multiple(4) and single(5) Permissive Strategy, (1) the Coordinated
Phases are always permitted and (2) non-Coordinated Phase Vehicle Permissive
Periods are calculated automatically. Refer to Table 31.
Table 31 – Permissive Strategies
Value
(2)
(3)
Description
Benefit when phase demand varies (no benefit if
every phase uses its full split time)
manual – Screen 2.3.3.1-16 ST PERM
(Permissive Start Time) and END PERM
(Permissive End Time) determine nonCoordinated Vehicle Permissive Windows during
the Coordinated Phase(s).
During non-Coordinated Phases, Vehicle and
Pedestrian Permissive Windows extend to allow
proper sequencing.
The Coordinated Phases require valid ST PERM
and END PERM times because they will not turn
on until their Vehicle Permissive Window opens.
User controls when the Coordinated Phases
can terminate to answer non-Coordinated
Phase Calls
yield – provides a Yield % (Screen 2.3.1 Yield
Percentage) length Permissive Window for all
phases during the Coordinated Phases. If the
Coordinated Phases advance to non-
A small Yield % favors the Coordinated
Phases if late calls occur.
User controls how early the Coordinated
Phases can start.
197
Value
Benefit when phase demand varies (no benefit if
every phase uses its full split time)
Description
Coordinated Phases, Vehicle and Pedestrian
Permissive Windows extend to allow proper
sequencing until the Coordinated Phases turn
on. See Figure 11.
(4)
multiple – Opens all Permissive Windows at the
first Coordinated Phase Yield Point. Closes each
phase’s Vehicle and Pedestrian Permissive
Window when minimum times cannot finish
prior to its Fixed Force Off Point.
Minimizes Non-Coordinated Phase delay via longer
Permissive Windows.
(5)
Single – Sequentially opens each Phase’s
Vehicle and Pedestrian Permissive Window at
the normal Split start point minus the
Coordinated Phase(s) Clearance Time.
Opens remaining Permissive Windows when a
non-Coordinated Phase turns on to ensure
proper sequencing.
Closes each phase’s Vehicle and Pedestrian
Permissive Window when minimum times
cannot finish prior to its Fixed Force Off Point.
See Figure 12.
Widens the green band’s ending by staying
in the Coordinated Phases if no call exists
on the currently-permitted phases.
Figure 177 – Yield Permissive Strategy
198
Coordination Menu
Figure 178 – Single Permissive Strategy
MAX DWELL/ADD/REDUCE TIME (Peek, default 0, Range 0 – 255) – All cycle
adjustments except dwelling are evenly distributed to phases subject to minimum times
(falls under Patt Table Data Type’s jurisdiction).
Table 32 – Max Dwell/Add/Reduce
Correction Mode
Max Dwell/Add/Reduce Time’s affect on Correction Mode
dwell (2)
Zero synchs in one dwell period.
Non-zero dwells until in synch or the Max Dwell/Add/Reduce time
expires.
shortway (3)
Zero extends or reduces the cycle 20% each transition cycle until
in synch.
Non-zero extends or reduces the cycle by that amount until in
synch.
addOnly (4)
Zero extends the cycle 20% each transition cycle until in synch.
Non-zero extends the cycle by that amount until in synch.
offsetPercent (5)
shortwayDwell (6)
Ignored.
Zero synchs in one dwell period or reduces the cycle 20% each
transition cycle.
Non-zero dwells until in synch or the Max Dwell/Add/Reduce time
expires, or reduces the cycle by that amount.
Pedestrian Override – (POM) (Peek, default 0, Range 0(NO) – 1(YES)) – When set
1(YES):
(1)Table 34, Check #10 passes if an Actuated-Mode non-Ped Recalled phase’s ped time
exceeds its Split time (the Split time can represent only vehicle demand).
(2) the Local Cycle Timer stops at an Actuated-Mode phase’s Fixed Force Off Point until
walk and ped clearance finish, causing an Offset error (because the Master Cycle Timer
maintains counting) corrected by the Coord Correction Mode when the Local Cycle
Timer resumes.
199
When set 0(NO): Table 34 Check #10 fails if a phase’s ped time exceeds its split time.
Peek Recommendations –
(1) Use Shortway or Shortway Dwell Coord Correction Mode during POM because
small offset errors can be corrected within one cycle.
(2) Use POM when ped demand is less than three ped calls per hour because
frequent ped calls will cause more time in Offset Seeking than In Sync
Automatic Hold, Yield Point and Force-Off Calculations
Coordinated Phase Yield Point: Local Cycle Timer value when Coordinated Phase
"hold" drops allowing Coordinated Phase termination.
Non-Actuated Mode (C.N.A.) Coordinated Phase: Yield Point = projected split end
point minus Vehicle Clearance time minus Ped Clearance time.
Actuated Mode Coordinated Phase: Yield Point = projected split end point minus
Vehicle Clearance time minus Early Yield Time.
Note
The Coordinated Phases will have unequal Yield Points if (1) running C.N.A.
Mode with unequal Ped Clear times or (2) they end at different times (i.e., “leadlag”).
Coordinated Phase Hold Window
(1) begins when the last permissive window prior to the coordinated phases ends.
(2) ends at coordinated phase's yield point
This sequence applies to the illustration in Figure 179.
Sequence: 2-1 | 4 |
5-6 | 8 |
Figure 179 – Hold, Yield Point and Force Offs
200
Coordination Menu
Coordinated Phase Pedestrian
Non-Actuated-Mode (C.N.A.):
1.
If Walk Rest Modifier active, Coordinated Phases leave walk if a conflicting openpermissive call occurs.
2.
If Walk Rest Modifier not active, (a) Coordinated Phases advance to Ped
Clearance at the Yield Point and dwell green/dont walk during permissive
windows if no calls occur, (b) walk automatically recycles at Coordinated Phase
Hold Window's beginning if Coordinated Phases do not terminate.
Actuated Mode:
1.
A ped call recycles walk during the Hold Window if Ped Recycle active and Walk
plus Ped Clearance time less than the time remaining until the Force Off point.
2.
A ped-called or recalled Actuated-Rest-in-Walk Mode phase rests green/walk
during the Coordinated Phase Hold Window until the Local Cycle Timer equals
the Force Off Point minus Early Yield Time minus Ped Clearance time. Outside
the Hold Window the phase rests green/steady don't walk.
3.
A ped call recycles walk outside the Hold Window if (1) no conflicting call exists or
(2) walk and ped clearance can finish timing without interfering with futureopening Permissive Periods with a call.
201
Split Table Screens
The split table is used to define what ‘split’ of the overall cycle time each phase will take.
(For coordinated operation, each phase doesn’t operate simply based on a set timer,
but rather on a portion of the overall cycle length, called its ‘split time’.) An ATC
controller can be programmed with up to 16 different defined splits for the intersection.
A split table number is referenced in each column of the Pattern table screens, so each
defined pattern calls one of these defined split tables, which is a large part of what
defines each pattern. Each split is defined on its own screen. To navigate between the
various split table screens, use the
and
keys.
M AIN M ENU > 2.P ROGRAMMING > 3.C OORDINATION > 3.S PLIT T ABLE
2.3.3. 1
TABLE #
COORD SPLIT TABLE PG 1of16
1 TIMES IN SECONDS
PHASE
: 1
2
3
4
5
6
7
8
SPLIT
:015 035 015 025 015 035 015 025
MODE
: 2
2
2
2
2
2
2
2
COORD PH:
X
X
ST PERM : 0
0
0
0
0
0
0
0
END PERM: 0
0
0
0
0
0
0
0
Changes to TIMES IN PERCENT
if the Splt Table Data Type is set so
PHASE
: 9 10 11 12 13 14 15 16
SPLIT
:000 000 000 000 000 000 000 000
MODE
: 2
2
2
2
2
2
2
2
COORD PH:
ST PERM : 0
0
0
0
0
0
0
0
END PERM: 0
0
0
0
0
0
0
0
Figure 180 – Split Table Screen
Split — The time, in seconds, the split/phase will use, before any Force-Off is applied,
whenever there are constant demands on all phases. The exact operation depends on
which Force Mode has been selected on the Coordination Variables screen
(MM.2.3.1). If Force Mode is set to Floating, this split time is always the maximum time
a non-coordinated phase is allowed to use. If Force Mode is set to Fixed, then the actual
time for the split may be longer, if a previous phase gapped out to end. Keep in mind
that thie programmed split time will need to include all of the clearance time associated
with the phase in addition to the Green time. So a fundamental requirement when
programming splits is that the split time must be bigger than the sum of the phase
minimum service times for the phase (i.e. Minimum Green, Passage time, Yellow
Clearance, and Red Clearance times.)
Mode — The programmed split mode for this split. These modes determine how a split
deals with recall requests during coordination. These are the available split modes:
Table 33 – Split Modes
Mode
none (2)
202
Description
No split mode control of recalls. The default
recall settings for this phase, as
programmed on the Recalls screen (MM > 2
> 2 > 9) will be used instead.
Are Phase Recall screen’s
Minimum, Maximum, & Pedestrian
Recalls Ignored or Applied?
Applied
Coordination Menu
Mode
Description
Are Phase Recall screen’s
Minimum, Maximum, & Pedestrian
Recalls Ignored or Applied?
minimum Vehicle Recall
(3)
The phase operates with a minimum vehicle
recall. This overrides any Recalls
programmed in the default phase Recalls
screen. (MM > 2 > 2 > 9)
Ignored
maximum Vehicle Recall
(4)
The phase operates with a maximum
vehicle recall. This overrides any Recalls
programmed in the default phase Recalls
screen. (MM > 2 > 2 > 9)
Ignored
pedestrian Recall (5)
The phase operates witha pedestrian recall.
This overrides any Recalls programmed in
the default phase Recalls screen. (MM > 2
> 2 > 9)
Ignored
maximum Vehicle and
Pedestrian Recall (6)
The phase operates with both a maximum
vehicle and a pedestrian recall. This
overrides any Recalls programmed in the
default phase Recalls screen. (MM > 2 > 2
> 9)
Ignored
phase Omitted (7)
The phase is omitted. The phase will not be
shown during a cycle, except when needed
for special circumstances, such as during a
preemption run when it is programmed as a
track clearance phase or something similar.
Ignored
No early release(8)
No Early Release (no gap outs permitted):
holds phase green until (1) its Force Off
point during Coordination or (2) its Max Out
point during Free.
Applied
Note
Minimum, maximum and pedestrian recalls and phase omits from the
Commanded TOD Actions screen (MM.2.4.4 ), when called by hardware
inputs, work during all split modes.
Figure 181 – Split Mode 6 (Maximum and Pedestrian Recall) timing
203
COORD PH — A flag to mark whether this is a Coordinated Phase or not. An ‘X’
indicates that the phase should be timed in coordination with an arterial. Usually, this is
activated only for the main street ‘through’ movements.
Note
For "cross street" coordination, set the "main street" phases as CRDPH and use
C.N.A on the "cross street" and Fixed or Forward Force Mode.
ST PERM – The start permissive time (in seconds or percentage of the cycle time) when
using the manual permissive strategy. The default value is 0.
END PERM – (Peek, default 0, Range = 0-255) – The end permissive time (in seconds
or percent of the cycle time) when using the manual permissive strategy. The default
value is 0.
Offset Correction Ext/Reduce
The values on these screens (Options 4 and 5 on the Coordination menu) are used only
when the value for Correction Mode = o f f s e t P e r c e n t ( 3 ) on the Coord Variables
screen. This method of coordination offset correction allows the operator to set a specific
number of seconds to be extended or reduced for each phase, in each of the 16
available split tables. Use the
and
keys to navigate between the 16 split plans.
M AIN M ENU > 2.P ROGRAMMING > 3.C OORDINATION > 4.O FFSET C ORRECTION
E XT /R EDUCE
2.3.4 OFFSET CORRECTION EXTND/REDUCE
TIMES IN SECONDS
SPLIT 1 of 16
PHASE
1
2
3
4
5
6
7
8
EXTEND :000 000 000 000 000 000 000 000
REDUCE :000 000 000 000 000 000 000 000
PHASE
9 10 11 12 13 14 15 16
EXTEND :000 000 000 000 000 000 000 000
REDUCE :000 000 000 000 000 000 000 000
This changes to ‘TIMES IN PERCENT’
if the Splt Table Data Type on the
Coordination Variables screen is set to
percent(2)
PAGE DOWN FOR MORE SPLITS
Figure 182 – Offset Correction Extend/Reduce Split Table
Extend – The number of seconds to add to a phase if offset correction is required and
this numbered split table is in effect as the current pattern for the intersection. Also, the
maximum time a phase’s green split time can extend during Offset Percent Correction
mode. The default value is 000.
Reduce – The number of seconds to reduce a phase length if offset correction is
required and split table N is in effect as the current pattern for this intersection. Or, the
maximum time a phase’s green split time can reduce during Offset Percent Correction
mode (subject to minimum times). The default value is 000.
204
Coordination Pattern Consistency Checks
COORDINATION PATTERN CONSISTENCY CHECKS
GreenWave automatically performs consistency checks on a coordinated pattern
whenever it is called to run. If the message “Bad Plan, Press HLP” appears on the
Coordination Status Screen (MM.1.1.2), next to the Status field at the top middle of the
display, press the
to see more information. During a “Bad Plan”, Free mode occurs
until either the user corrects the database or the user switches to an error-free pattern.
Table 34 – Coordination Error Messages (Peek indicates non-NTCIP)
Check#
Error Message
Note
1
Free: Offset Time t seconds exceeds Cycle
Length c.
Subtract Cycle Length from Offset
Value
2
Free: Cycle Length c invalid
Must be between 30 and 255.
3
Free: Min Split Time Sum through the Sequence
Path in
seconds t exceeds Cycle Length c
The Sequence Path does not multicount
phases in multiple Concurrency
Groups.
4 (Peek)
Free: Incompatible Coordinated Phases
Correct Coordinated Phase
assignment or Phase Compatibility
5 (Peek)
Free: No Coordinated Phase in eligible Ring r
Cannot have a non-Coordinated
Phase
compatible with every
Coordinated Phase.
6
Free: Split Time Sum through the Sequence
Path in seconds
s exceeds Cycle Length c
The Sequence Path does not multicount
phases in multiple Concurrency
Groups.
7 (Peek)
Free: Total Split Percent Sum s exceeds 100
Split % sum must = 100
8 (Peek)
Free: Concurrency Group g Ring r Split Time
Sum in seconds
s must equal t
Example: standard 8-phase 2-ring
sequence,
phases 1+2 split time must equal
phases
5+6, where t is the larger of 1+2
and 5+6.
9 (Peek)
Free: Concurrency Group g Ring r Split Percent
Sum s must
equal t
Same as Check #8.
10
Free: Phase p Walk w plus Ped Clear c plus
Required
Clearance x.y exceeds Split Time in seconds
u.v
Skips this check for actuated-mode
phases
and Ped Override active.
11
Free: Phase p Min Green/Max Initial time g plus
Required
Clearance x.y exceeds Split Time in seconds
u.v
Uses the larger of Initial/Min Green
and
Maximum Initial times
205
Calculating “Required Clearance” (Checks 10 and 11)
Step 1: Determine each Phase’s Required Clearance Time
Required Clearance Time = larger of Phase’s’ [Yellow plus Red Clear] and
[Trailing Overlap’s Trail Green plus Trail Yellow plus Trail Red] times (use the
longest Trailing Overlap if multiple Overlaps).
Step 2: Identify Barrier Phases
A Barrier Phase is a Phase P whose next phase(s) are not compatible with
Phase P’s compatible phase(s) (see Phase Concurrency Screen 2.1.3.1-2).
Step 3: Adjust Barrier Phase’s Required Clearance Time
A Barrier Phase’s Required Clearance Time = the largest Required Clearance
Time (Step 1) of the Barrier Phase and the Barrier Phase’s Concurrency
Phases (menu 2.1.3).
206
Required Clearance Calculation Reason and Example
During a “Concurrency Group change”, phases go Yellow simultaneously and the
longest “Yellow+Red time” phase extends the shorter-timed phase(s)’ Red Clearance.
The Required Clearance calculation ensures every Barrier Phase’s next phase(s)
always start at the same point. When a phase turns on, Force Off points adjust to give
each phase the maximum possible green time.
Required Clearance Example focusing on Phase 4 using Sequence:
2|
4|
6 | 7-8 |
Step 1:
Every phase's Required Clearance
is its "Yellow+Red" time because no
Trailing Overlaps exist.
Step 2:
Phase 4 is a Barrier Phase because
Phase 4’s next phases 2,6 are not
compatible with Phase 4’s
compatible Phases 7 and 8.
Step 3:
Phase 4’s Required Clearance is the
largest Required Clearance of
Phase 4 and its Concurrency
Phases 7 and 8.
Figure 183 – Unequal Yellow and Red Time Scenarios
In Figure 16 Phase 4’s green time
changes depending on which
phases turn yellow with it to ensure
Phases 2 and 6 always start at Local
Zero. Phase 7 has the largest
“Yellow+Red” time and phase 4 has
the smallest.
207
Additional Functions Used to Coordinatean Actuated ATC
HOLD -- Holds the coordinated phase (Main Street) during a specific period of the cycle,
when no permissive periods are active.
FORCE OFF (FO) -- Terminates a phase at the designated point in the master
background cycle. Note that FO is a rather mild command and can only terminate an
actuated green that has timed past the minimum (Initial) or ped times. It cannot FO in
minimum green, walk or ped clear. It has no effect on yellows or reds.
It is important to note that the coordinator (coordination algorithm) only uses the above
commands to constrain the ATC phasing and phase-next decisions. It does not interfere
with or modify intervals such as minimum greens, walk, ped clear, yellow, or red. This is
a common misconception.
Example of FO And Permissive Placement
This example shows how an actuated ATC may be set up using the FO and Permissive
functions in an 8 phase, dual-ring sequence.
Shown is a 90 second ‘master background cycle’ with the typical placement of ‘fixed’
FOs and permissives. Each FO establishes the point at which the phases will be
terminated and move on.
Phases can ‘gap-out’ before the FO. If a phase does gap-out, the next phase/phase pair
can get more time. Notice that each permissive ends somewhat before the FO for the
indicated phase pair. Under full demand on all phases, permissives generally don’t do
much. Under light demand, particularly if the coordinated phase is likely to “rest” or if
other phases are likely to be skipped (no demand), permissives make sure that phases
are only allowed service at such a point that they can be forced off at their designated
time.
Figure 184 – Typical placements of fixed force offs and permissives
Coordination of actuated ATCs can be complex. Two seemingly contradictory concepts
are employed at once. If the ATC is actuated, the benefits associated with an actuated
controller are desired. An ATC that is responsive to traffic, skips phases with no
demand, varies the green appropriately for phases with demand, and rests in the Main
Street in the absence of any demand. To accomplish coordination, the algorithm must
constrain the timing so operation continues within the confines of the master background
cycle.
208
Coordination of actuated signals can be controversial. This is primarily due to the nature
of their operation. Interval-based (pre-timed) signal progression tends to be wellbehaved and each signal displays its green in just the proper order. The ATC has the
ability to perform Interval-based coordination. Actuated signals do not always seem to
behave. If at a given intersection, all the side street phases do not use all their green
time by ‘gapping-out’ before FO, then there will be an ‘early return’ to the Main Street.
The platoon of vehicles at that intersection will then be released and may arrive at the
next intersection too early, before the green appears. These vehicles will have to stop,
which, defeats the purpose of coordination.
There are some considerations relative to this issue. Despite the lack of appearance of
coordination, the system may actually be more efficient. Even though the Interval-based
(pre-timed) system appears well coordinated, it often does so by arbitrarily holding the
main street red, as the side streets are provided with a fixed duration green time,
whether needed or not. The actuated ATC returns to the Main Street as soon as it can.
Some Main Street vehicles may turn off before they reach the next intersection, an early
return is certainly beneficial to them. For those that proceed through the intersection,
although they may be hampered by arriving too early, they may also have the luck that
the next intersection returns early and can proceed unimpeded. This type of operation
provides maximum efficiency although it can occasionally appear sporadic and
unpredictable.
Proper coordination using actuated ATCs requires the proper cycle and split values for
the level and distribution of traffic at any given time of day. If the cycle length and split
times are appropriate for the conditions at all times of the day, non-beneficial early
returns to the main street can be minimized.
The ATC uses a dynamic or ‘auto-calculation’ method to manage Permissive (windows)
depending on the Permissive Strategy selected. Permissive Periods are not applied to
Coordinated Phases. Each Coordinated Phase has a pre-calculated Yield Point. This
Yield Point occurs when Hold drops and Force Off activates, allowing the Coordinated
Phase(s) to advance to ped clearance if CNA is applied, or yellow clearance if no CNA
and permitted conflicting call(s) exist.
Actuated Phase Yield Point = split end point - (yellow + red clearance)
CNA Phase Yield Point = actuated phase yield point - ped clearance time
MinGreen is defined as the larger of the phase's Min Green (Initial) time and Max Initial
time, if Volume Density is active to ensure a proper force off with the extra Min Green.
PedTime is the smaller of the phase's Walk + Ped Clear and (Split - Yellow - RedClear)
to ensure a long enough permissive period, if the ped time is greater than split time.
VehClearFactor is the largest conflicting green phase's yellow + red clearance time.
PedClearFactor is the largest conflicting CNA green/walk phase's ped clearance time.
Note
VehClearFactor and PedClearFactor add separately because conflicting ped
clearances finish prior to conflicting greens going yellow.
The following are three scenario examples of how the permissive algorithms work:
Calculating EndVehPermissive for Phase 1 -- Phase 1's FixedForceOff = 50.
209
Phase Times:
Phase
1
MinGreen 10
Yellow
5
RedClr
0
PedClr
0
2
10
4
1
10
3
10
6
1
0
4
10
3
3
8
5
10
3
4
0
6
10
3
3
16
7
10
4
2
0
8
10
3
2
5
Scenario 1:
• Phase 3 is green
• Phase 8 is in CNA green/walk
• VehClearFactor
= ph 3 y+r = 6+1 = 7
ph 8 y+r = 3+2 = 5
max[7,5] = 7
• PedClearFactor
= ph 8 ped clear time = 5
max[8] = 5
• EndVehPermissive phase 1 = 50 - 10 - (7 + 5) = 28
Scenario 2:
• Phase 3 is green
• Phase 8 is in CNA green/pclr
• VehClearFactor
= ph 3 y+r = 6+1 = 7
ph 8 y+r = 3+2 = 5
max[7,5] = 7
• PedClearFactor
= 0 (no CNA walks conflicting with phase 1)
• EndVehPermissive Phase 1 = 50 - 10 - (7 + 0) = 33
Scenario 3:
• Phase 3 is yellow/4 next
• Phase 8 is in CNA green/pclr
• VehClearFactor
= ph 8 y+r 3+2 = 5
= max[5] = 5
• PedClearFactor
= 0 (no CNA walks conflicting with phase 1)
• EndVehPermissive phase 1 = 50 - 10 - (0 + 5) = 35
• Coordination Programming for Central-System based Traffic Responsive
Operation
• The ATC accepts pattern commands from IQ Central that provide Traffic
Responsive arterial coordination. See the IQ Central Operating Manual.
210
Table 35 and Table 36 contain Peek’s recommended four progressive Pattern Cycle
Time(s) arranged from shortest to longest; three Pattern Offset Time(s) arranged as
Inbound (I), Balanced (B) and Outbound (O); and four splits for Balanced (B), Slightly
(S), Moderately (M) and Heavily (H) favoring the Main Street Coordinated Phases.
Table 35 – Traffic Responsive Split modes
Split Mode
Split Time by Phase Pair (in Percentage (%)of Cycle Time)
1/5
2/6
3/7
4/8
B (Balanced)
25%
25%
25%
25%
S (Slightly)
23%
29%
23%
25%
M (Moderately)
15%
40%
15%
30%
H (Heavily)
15%
45%
15%
25%
Table 36 – Traffic Responsive Pattern data
Pattern #
Cycle
Offset
Split Mode/
Number
Pattern #
Cycle
Offset
Split Mode/
Number
1
2
3
4
5
6
7
8
9
10
11
12
90
90
90
90
90
90
90
90
90
90
90
90
I
B
O
I
B
O
I
B
O
I
B
O
B/1
B/1
B/1
S/2
S/2
S/2
M/3
M/3
M/3
H/4
H/4
H/4
25
26
27
28
29
30
31
32
33
34
35
36
130
130
130
130
130
130
130
130
130
130
130
130
I
B
O
I
B
O
I
B
O
I
B
O
B/9
B/9
B/9
S/10
S/10
S/10
M/11
M/11
M/11
H/12
H/12
H/12
13
14
15
16
17
18
19
20
21
22
23
24
110
110
110
110
110
110
110
110
110
110
110
110
I
B
O
I
B
O
I
B
O
I
B
O
B/5
B/5
B/5
S/6
S/6
S/6
M/7
M/7
M/7
H/8
H/8
H/8
37
38
39
40
41
42
43
44
45
46
47
48
150
150
150
150
150
150
150
150
150
150
150
150
I
B
O
I
B
O
I
B
O
I
B
O
B/13
B/13
B/13
S/14
S/14
S/14
M/15
M/15
M/15
H/16
H/16
H/16
211
212
Chapter 7 — Interval Operation
This chapter describes the interface and methods used to program an ATC controller for intervalbased operation. The following topics are discussed in detail in this chapter:
•
Overview of Interval-based operation, on page 214.
•
Pattern to Interval Plan mapping, on page 216.
•
Using the Interval programming screens, on page 217.
•
Details about interval-based preemption, on page 242.
•
Setting up Leading or Lagging left turns using interval plans, on page 244.
213
OVERVIEW
As has been mentioned elsewhere in this manual, the basic control that determines what
timing will be used in an intersection is the pattern number that is currently selected. The
bottom 48 patterns are programmed using a NEMA phase-based theory of operation.
Patterns 101 through 228, however, are programmed using the interval-based theory of
timing an intersection. With the exception of some global parameters and controls that
are common to both timing methodologies (such as database management tools, tools
to manage the controller clock, time-of-day programming, and I/O port management),
almost all programming for interval-based operation occurs in one part of the
GreenWave interface, namely on the Interval menu under the Programming section of
the interface.
(MM >2.P ROGRAMMING >7.I NTERV AL )
The Interval menu is where the operator goes to define any of the available intervalbased patterns, as well as interval-based preemption runs.
Timing Plans
There are 32 available timing plans. Each timing plan defines how many intervals will be
used in the pattern. A timing plan can use up to 24 intervals. The plan also includes a
cycle length, an offset, and a set of split times, one for each of the intervals in the plan.
Signal Plans
There are four signal plans available. A signal plan is basically a mapping of the signals
and outputs during each interval. The signal plan is the sequence of color indications for
all used channel outputs that will appear on the street. The signal plan also includes
minimum times for all used intervals and programmable options for each interval
covering manual control, transitional control, and semi-actuation of vehicle or pedestrian.
Plan Processing
When an interval-based pattern is in effect, the controller starts the associated timing
plan, using the associated signal plan signal output assignments for the intervals. The
timing plan starts at interval #1 when the controller powers up, or when a new pattern is
called. When one interval ends, the next in the sequence starts automatically. Unless
options have been set for manual control (such as MCE or Actuated) in the signal plan,
the timing plan sequence will only pause at ‘All Red’ intervals. As an example of how the
sequence may be paused in a given state, a signal plan may be configured to be
‘Actuated’ so that the interval sequence will rest on main street green until an actuation
is received.
Exiting a Timing Plan Sequence
Signal plans can be exited at a specified interval so that they can transition either to
another signal plan, another timing plan, or to automatic flash.
Interval-based Preemption
As with phase-based preemption, there are six available preemption runs when
operating an interval-based pattern. (If the controller is running an interval-based pattern
214
Overview
and a call comes in on preemption input 2, interval based preemption run 2 will be used.
If the controller is running a phase-based pattern, it would run phase-based preemption
run #2.) Preemption runs have an entry portion, an optional Track (railroad track
clearance) portion, a Dwell portion, and finally an Exit portion. And each Track, Dwell,
and Exit portion of each run can have anywhere from 1 to 24 intervals defined.
Calling the Plans
How are interval-based plans called into operation? It’s all based on Pattern. When a
pattern number between 101 and 228 is called, either by the time of day scheduler, or by
a central command or override, each pattern automatically invokes a preset Signal plan
and Timing plan. (For example, pattern 101 calls Timing Plan 1 and Signal Plan 1.)
These timing plan/signal plan to pattern assignments are hard coded into the ATC
controller and are shown in Table 37 on the next page.
Note
These assignments are also visible on the ATC front panel interface,
along with some additional information, on the Timing Plan >
Signal/Offset/Split Data screen. ( > 2 . P r o g r a m m i n g >
7.Inter val > 1.Timing Plans > 1.Cycle / Offset /
S p l i t D a t a ) However, the assignments cannot be modified on
these screens.
215
Table 37 – Pattern to Interval Signal Plan and Timing Plan assignments
Pattern
Timing Plan
Signal Plan
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
1
2
3
4
5
6
7
8
9
10
11
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
2
2
2
2
2
2
2
2
2
2
2
216
Pattern Timing Plan
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
Signal Plan
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
Pattern Timing Plan
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
23
24
25
26
27
28
29
30
31
32
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
Signal Plan
3
3
3
3
3
3
3
3
3
3
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
Using the Interval Programming Screens
USING THE INTERVAL PROGRAMMING SCREENS
Interval-based patterns, which run from 101 to 228, are managed and programmed
within the GreenWave software on the Interval menu, located under the Programming
area of the interface.
(M AIN M ENU > 2.P ROGRAMMING > 7.I NTERVAL )
2.7
INTERVAL MENU
1. TIMING PLANS
2. SIGNAL PLANS
3. PREEMPTION
4. INTERVAL SKIPPING
Figure 185 – Interval menu
Timing Plan Menu
The Timing Plans menu of the ATC controllers is where you can program the cycle
length, offset, the number of intervals used, and the split times for each of those
intervals within each pattern.
( > 2.P ROGRAMMING > 7.I NTERVAL > 1.T IMING P LANS )
2.7.1
TIMING PLAN MENU
1. CYCLE / OFFSET / SPLIT DATA
2. TIMING PLAN SETUP
Figure 186 – Timing Plan Menu
Cycle/Offset/Split Data — This table, displayed on a series of 16 screens, is primarily a
read-only way to view the current status of pretimed operations. It does however provide
a single editable field at the bottom of the screen: the Commanded Plan field can be
used to perform a manual override of the current pattern selection.
Timing Plan Setup — This is where all of the timing information is actually programmed
for each of the 32 timing plans, including split times, cycle length, and offset.
217
Cycle / Offset / Split Data Screens
The Cycle / Offset / Split (COS) Data Screens show the current status of interval-based
operation, including the current pattern, timing plan and signal plan in effect. But most of
the screens are occupied by a table, eight rows at a time, showing the fixed mapping of
pattern numbers to each timing plan/signal plan combination. Each row also shows the
programmed values within those timing plans for cycle length and offset times. Note that
the times for cycle and offset cannot be entered here; they are merely reported here.
(MM > 2.P ROG R AM M ING > 7.I NTERV AL > 1.T I M ING P L AN S > 1.C YCLE /O FF S ET /S PLIT D AT A )
2.7.1.1.1 TIMING COS DATA PG 1 of 16
|Pattern|Timing|Signal|Cycle|Offset|
| 101 | 001 | 001 | 060 | 000 S|
| 102 | 002 | 001 | 070 | 000 S|
| 103 | 003 | 001 | 080 | 000 S|
| 104 | 004 | 001 | 090 | 000 S|
| 105 | 005 | 001 | 100 | 000 S|
| 106 | 006 | 001 | 120 | 000 S|
| 107 | 007 | 001 | 060 | 010 S|
| 108 | 008 | 001 | 060 | 020 S|
Current Pattern
Current Timing Plan
Current Signal Plan
Commanded Plan
101
001
001
000
Figure 187 – Interval Cycle/Offset/Split Data (Page 1)
The table will show the currently running pattern number, along with the associated
timing plan and signal plan that is currently being used to run the intersection. The readonly table shows what timing plans and signal plans are assigned to each pattern, as
well as the current values for Cycle length and offset times for each of the 32 timing
plans.
Note
The same timing plan data is shown four times in the table, one for each
of the four signal plans.
The only value that can be entered directly on this screen is the Commanded Plan. This
is the location where pretimed operation can be set directly by entering a pattern number
to run. Otherwise, the pattern number is selected by time of day, or by central command.
This Commanded Plan number is the same database object as the Operational Mode
parameter on the Coord Variables screen. (MM.2.3.1)
Press the D WN – button to navigate to the other 15 screens to see the Timing/Signal
Plan mappings for Patterns 101 through 228.
218
Timing Plan Setup Screens
These are screens where the actual times are entered for each of the 32 timing plans,
each with its own set of 24 interval split times.
(MM > 2.P ROGRAMMING > 7.I NTERVAL > 1.T IMING P LANS > 2.T IMING P LAN S ETUP )
2.7.1.2.1
TIMING PLAN 1
PG 1of32
Cycle Length....000 (ent = split sum)
Offset..........000 Offset Type..sec
Intervals used..00
SPLIT 1
Type..sec
Time..000
SPLIT 9
Type..sec
Time..000
SPLIT 17
Type..sec
Time..000
2
sec
000
10
sec
000
18
sec
000
3
sec
000
11
sec
000
19
sec
000
4
sec
000
12
sec
000
20
sec
000
5
sec
000
13
sec
000
21
sec
000
6
sec
000
14
sec
000
22
sec
000
7
sec
000
15
sec
000
23
sec
000
8
sec
000
16
sec
000
24
sec
000
Figure 188 – Interval Cycle/Offset/Split Data
Cycle Length — This is the length of time to complete an entire loop of the timing plan,
from interval 1 to the last ‘Interval used’ in the plan, and then back to interval 1. The
cycle length is calculated automatically if the Split Type is seconds or tenths of seconds.
You will need to enter the cycle length manually (in seconds) if the Split Type is
Percentage (“per”).
Offset — This is the offset time that this intersection will start the cycle after a new
pattern is called, assuming this controller is part of a coordination plan. Pretimed
coordination is based on synchronized clocks. Each intersection has the same cycle
length, and each intersection switches to a new pattern at the same time of the day. This
offset value then allows the intersection signals to be coordinated. This value can either
be a number in seconds (0 to 254 seconds) or a percentage (0 to 100%). The units are
set using the Offset Type parameter (below.)
Offset Type — Use the right arrow to navigate to this field to set the units that will be
used with Offset (above). This value can be either sec (seconds) or per (percentage),
which tells the ATC how to interpret the value you enetered for Offset.
Intervals used — This is the number of intervals (out of 24) that will be used in this
timing plan. Even if times are entered for splits beyond this number, only the first number
of splits up to this value will actually be used in the plan. So if you call for the Intervals
used to be 13, then the first 13 splits in the table below are the ones that will be timed
during the pretimed cycle.
Split Type — Each intervale can be defined in terms of sec (seconds), ten (tenths of
seconds), or per (percentage of the cycle length.) In practice, avoid mixing percentage
and real-time definitions in your active intervals.
Split Time — A three digit number for each split that represents either seconds, tenths
of seconds, or percentage of cycle time, depending on what Split Type has been
chosen. Valid values are between 000 and 255, so 0 to 255 seconds, 0.0 to 25.5
219
seconds, or 0 to 100 percent. (Values over 100 if the Split Type is ‘per’ are not
accepted.) After you have entered all of your split times, if the times are all seconds or
tenths of a second, then the cycle length will be calculated automatically as soon as you
exit Edit mode. If you have entered your split times as percentages, you will need to
supply the Cycle length, in seconds, yourself.
All 24 splits possible for the current timing plan are shown on this one screen.
Press the
button to navigate to all 32 of the available pretimed Timing Plans.
Signal Plans Menu
This menu is where all the interval-based signal plan parameters can be programmed,
from one of the three available input screens.
(M AIN M ENU > 2.P ROGRAMMING > 7.I NTERVAL > 2.S IGNAL P LANS )
2.7.2
INTERVAL MENU
1. INTERVAL MODIFIERS
2. CHANNELS TO INTERVALS MAPPING
3. OUTPUTS
TO INTERVALS MAPPING
Figure 189 – Signal Plan screen
Interval Modifiers — This is the place to assign transfer, flash entry, and flash exit
intervals, as well as special modifier tags for individual intervals, such as actuation,
recalls, and dwells.
Channels to Interval Mapping — This is where the channel signal assignments
(Green, Yellow, Red, Walk, Flashing Don’t Walk, Don’t Walk) are set for each interval
and each of the channels in each of the four signal plans.
Outputs to Intervals Mapping — This is the place to assign more granular output
assignments for all of the intervals in the signal plan.
220
Interval Modifiers
This is the screen that defines special functions and roles for all of the intervals in the
signal plan. This includes minimum timings, transfer intervals (in and out of the plan),
actuation, dwell and recall, as well as several other functions.
(MM > 2.P ROG R AM M ING > 7.I NTERV AL > 2.S I GN AL P L AN S > 1.I NTERV AL M O DIFIERS )
2.7.2.1 INTERVAL MODIFIERS PG 1of 2
Signal Plan..001 Press 1-4 to select
Timing Plan Transfer Interval..00
Signal Plan Transfer Interval..00
Flash Entry Interval...........00
Flash Exit Interval............00
1 1 1
Interval -> 1 2 3 4 5 6 7 8 9 0 1 2
M.C.E.......
Actuated....
Recall......
Non-Lock....
Dwell.......
min(1-6)
0.0 0.0 0.0 0.0 0.0 0.0
min(7-12) 0.0 0.0 0.0 0.0 0.0 0.0
Figure 190 – Signal Plan Per Interval Modifiers (Screen 1 for Plan 1)
Signal Plan — This number shows which signal plan is being edited. This screen can
be used to edit all four of the available signal plans. To switch to another signal plan,
press the number button for the signal plan in question (1, 2, 3, or 4).
Timing Plan Transfer Interval — In each Signal Plan, you can specify one interval as
the Timing Plan Transfer interval. When a call is made to change to a different timing
plan, the controller waits until the end of this interval before it switches to the new plan.
Signal Plan Transfer Interval — Similarly, in each Signal Plan, you can specify one
interval as the Signal Plan Transfer interval. When a call is made to change to a
different signal plan, the controller waits until the end of this interval before it switches to
the new plan.
Flash Entry Interval — In each Signal Plan, one interval can be specified as the Flash
Entry Interval. If the controller is switching to Automatic Flash mode, it will wait until the
end of this specified interval before making the switch.
Flash Exit Interval — In each Signal Plan, one interval can be specified as the Flash
Exit Interval. If the controller is switching from Automatic Flash mode and will be starting
this signal plan, the controller will launch the plan by going directly to the beginning of
this specified interval.
M.C.E. — (Manual Control Enabled) This value is either OFF or ON for each interval in
the plan. When this value is ON (‘X’) for an interval, it is available for variable operation,
including a police button advance of the intersection, force-offs, and offset correction
timing. By selecting which of the intervals is enabled in this way, you can control how a
police button stepping through the cycle will function. Only those intervals with the X
next to MCE will respond to the button.
Actuated — An ‘X’ placed in an interval’s column indicates that the interval is actuated
by a detector input. However, the assignment of which detector or detectors (including
221
pedestrian detectors) will cause this actuation is not available from the controller front
panel in build 304 of the firmware. To make the detector assignment for each interval,
you will need to edit the device database using ATCLink or IQ Central.
Recall — When checked, it indicates that an interval MUST be serviced during the
cycle. In effect, this is an artificial call on that interval ; one that isn’t being generated by
a detector input.
Non-Lock — By default, intervals are locking on detector inputs, meaning that if a call is
placed (and the interval is ‘Actuated’), then the demand for service on that interval
remains, even if the call goes away. If you set Non-Lock to ON (‘X’), then this interval’s
detectors do not latch in this manner, meaning that if the call goes away, then the
demand for service on this interval also goes away.
Note
Pedestrian detector calls are always locking, no matter how the Non-Lock
parameter is set.
Dwell — An interval marked as Dwell is used by the traffic engine to get the intersection
back into coordination. Since pretimed operation does not have other methods for
coordination offset recovery, Dwell is the only option available for the coordinator to
modify the cycle time in order to resynchronize the intersection with the coordination
timing. Typically, only one interval is marked as the Dwell interval, and it’s usually the
interval that supplies the Green light to the main traffic artery. However, the ATC
firmware will allow multiple intervals to be available for Dwell operation. If more than one
are checked (‘X’), and the coordinator needs to Dwell to resync coordination, then it will
use the first interval encountered that has the Dwell function flagged.
Note
If no Dwell inerval is programmed, the controller will never get into step.
min — These are the minimum times required for each interval. Valid values can be
anything from 0.0 to 25.5 seconds. This is typically used to protect a minimum time for
the amber (yellow) portion of a cycle to prevent it from falling below the legal limit for that
signal (This is 3.0 seconds in the United States, but the operator can set this minimum to
any value in the range mentioned previously.) As of build 304 of the controller firmware,
the only function that may potentially shorten an interval, and which must be protected
against using this min value, is Transit Signal Priority (TSP) operation. TSP can shorten
some intervals in order to recover after a transit vehicle has taken priority in the
intersection and knocked the intersection out of coordination.
The Pre-timed Interval Modifiers area forms a 4 x 2 array of screens. Press the numbers
1 through 4 to see the four signal plan screens, and press the
modifiers for intervals 13 through 24 for each plan.
222
button to see the
Channels to Intervals Mapping
This is the area in the interface where signal channels are assigned to the intervals in
your signal plans.
(M AIN M E NU > 2.P ROGR AM M ING > 7.I NTER V AL > 2.S IGN AL P L AN S > 2.C H AN N ELS TO
I NTERV AL S M APPING )
2.7.2.2.1 CHANNEL SETUP PG1of2
1 1 1 1 1 1 1
chnl->1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
I 1..
I 2..
I 3..
I 4..
I 5..
I 6..
I 7..
I 8..
I 9..
I 10..
I 11..
I 12..
Figure 191 – Interval Channels-to-Intervals Map – Page 1 for Signal Plan 1
Each signal plan features two pages of channel output to interval # assignments, all in a
24 row x 16 column table. Each location in the table allows the operator to assign a
signal output on a particular channel for that interval. Each cell in the table can be set to
one of these available signal options:
G — Solid green
Y — Solid yellow (amber)
R — Solid Red
W — Walk
F — Flashing Don’t Walk
D — Don’t Walk
g — Flashing green
y — Flashing yellow
r — Flashing red
‘ ‘ (blank) — No signal on this channel for this interval
These screens form a 4 x 2 array of screens. (Press the numbers 1 through 4 to see the
four signal plan screens, and press the
intervals 13 through 24 for each plan.)
button to see the channel assignments for
223
Outputs to Intervals Mapping
These screens allow you to define which intervals will be linked to which controller
outputs. There are four available sign output plans.
(M AIN M E NU > 2.P ROGR AM M ING > 7.P RETIM E D > 2.S IGN AL P L AN S > 3.O UT P UTS TO
I NTERV AL S M APPING )
2.7.2.3. 1 OUTPUT SETUP PG 1of11
Intvl(1-12) 1 2 3 4 5 6 7 8 9 0 1 2
Out 1.......
Out 2.......
Out 3.......
Out 4.......
Out 5.......
Out 6.......
Intvl(13-24)3 4 5 6 7 8 9 0 1 2 3 4
Out 1.......
Out 2.......
Out 3.......
Out 4.......
Out 5.......
Out 6.......
Figure 192 – Outputs-to-Intervals Map screen
This is a way to control the controller’s physical pin outputs directly from your interval
signal plan. These function alongside your Channels-to-Intervals assignments.
For each of the 24 intervals in the signal plan, you can specify an output on any of the
64 available outputs. The exact pins that these outputs trigger depend on how you have
configured your I/O Mapping for this controller. (Refer to “I/O Mapping”, on page 95)
Each output can be set to one of three states:
‘ ‘ (blank) — Output is OFF
X — Output is ON
F — Output is FLASHING
You can toggle the value for each input using any of these three keypad keys: YES, NO,
or NXT.
These screens form a 4 x 11 array of screens, each screen showing 6 outputs for all 24
intervals of one of the signal plans. Press the numbers 1 through 4 to see the output
assignments for each of the four signal plan screens, and use the
navigate between the screens showing all 64 outputs.
224
and
keys to
Interval-based Preemption
This screen hosts the parameters used to program the six available interval-based
preemption runs.
(M AIN M ENU > 2.P ROGRAMMING > 7.I NTERVAL > 3.P REEMPTION )
2.7.3
PREEMPTION INTERVAL MENU
1. MODIFIERS
2. TRACK INTERVAL DATA
3. DWELL INTERVAL DATA
4. EXIT INTERVAL DATA
Figure 193 –Preemption Interval menu
The screens under this menu allow an operator to configure the six available intervalbased preemption runs. The modifiers command is for global values that determine how
each run functions as a whole. The Track, Dwell, and Exit interval data screens are used
to define intervals for the three portions of a interval-based preeemption run.
How Preemption Works Under Interval Operation
A preemption interrupts the normal sequence of vehicle and pedestrian movements to
allow an emergency vehicle or train to have priority through the intersection. The
controller creates an orderly green-amber-red sequence of new intervals to reach the
preprogrammed preemption plan. If a signal is green and this matches the programmed
preempt plan, that signal will stay green while all other signals transition to the preempt
plan.
After the preemption has ended, the controller will use its programmed timing and signal
plans to operate the intersection. If preempt occurs, the controller advances to main
street green (interval 1) when the time-based plan would normally have caused this; for
example, at a specific time of the internal clock of the controller.
The specifications dictate a priority level for all inputs: preempt input is a higher priority
than stop time and cab flash. The result of this is that the controller does not stop
preempt processing if the cabinet is put into MCE.
There are several stages to preemption processing:
Preemption input is received by the controller

Preparation of intervals before going into preempt - these are the intervals that
cycle the intersection from the current signal conditions (red/amber/green) to
the first interval in the track clearance definition (if present) or the first interval in
the dwell definition.
225
The controller uses default times for these new intervals (three seconds for
amber, two seconds for red, and three seconds for flashing Don’t Walk). These
times can be changed on the Interval Skipping screen, available on the
Interval menu of the ATC interface. This screen has entries for pedestrian
clearance, amber clearance, and red time for each channel.

Preempt Track Clearance intervals - These intervals are optional and are often
used for handling train crossings, but they can be used for other purposes. If
they are not configured, then the first interval run during the actual preempt will
be the first dwell interval that follows. If a road crosses a railroad track, a track
clearance interval would need to be defined so that the road can be cleared
before the train comes through.

Preempt Dwell stage intervals - these are the actual intervals that run during
preempt. These intervals give priority to emergency vehicles.

Preempt Exit stage intervals - After the dwell times are completed, these
intervals return the intersection to normal operation. Typically, normal operation
starts in Interval 1 so the controller will appear to dwell in the last preempt
interval until the proper coordinated time is ready to advance to Interval 1.
(Assuming Interval 1 is programmed as the Dwell interval.) This advance to
Interval 1 is the TBC time as determined by the controller’s clock and the
current timing plan. Because of this dwell it may appear that the controller has
hung. The controller will return to Interval 1 at the same coordinated time, as if
the preemption did not occur.
Figure 194 – Interval-based preemption run logic
226
Flashing in Dwell
It is possible to configure preempt to flash the dwell intervals. By using the preempt
option to cycle the dwell phases and having two alternate intervals of one half second
each, the intersection can be doing a flash sequence while in preemption. In the
example ATCLink preemption configuration screen shown below, channels 1 and 5 are
flashing red simultaneously with channels 2 and 6, which are flashing yellow. Channels
3, 4, 7, and 8 will flash red, but on the alternate half of the 30 second in a wig-wag
fashion.
Figure 195 – Wig-wag signals during pre-timed preemption using Cycle Dwell
Preemption intervals can have of maximum duration of 25.5 seconds, so if an interval
time greater than 25.5 seconds is desired, duplicate the interval and use times that add
up to the desired total time.
227
INTERVAL-BASED PREEMPTION PROGRAMMING SCREENS
Modifiers Screens
There are six interval-based preemption Modifiers screens. Each defines a set of
parameters that determine how the whole run will function. Use
navigate between the modifier screens for the six runs.
and
to
M AIN M ENU > 2.P ROGRAMMING > 7.I NTERVAL > 3.P REEMPTION > 1.M ODIFIERS
2.7.3.1
PREEMPT 1 MODIFIERS
PG1of6
E
Cycle Dwell.............OFF
Override Flash..........ON
Non Locking.............OFF
Delay(0..600)........... 20
Min Duration(0..65535)..00000
Max Duration(0..65535)..01800
Figure 196 – Interval Preemption Modifiers screen
These parameters can be set independently for each of the six preemption runs.
Cycle Dwell – This switch is used to tell the preemption run to cycle through its dwell
intervals repeatedly. When set to ON, the preemption run will repeat the Dwell intervals
over and over until the preemption input call is no longer present, at which point the run
will proceed to the Exit intervals. When Cycle Dwell is set to OFF, the run will go through
the Dwell intervals once and then wait in the last interval until the preemption input call
goes away, at which point it will proceed to the Exit intervals.
Override Flash – This switch determines how the controller acts when in the flash state
and a preemption call then comes in. If Override Flash is ON, when the preemption
input arrives the controller will exit flash and initiate the preemption run. If this is set to
OFF, then the controller remains in Flash operation and does not initiate the preemption
run.
Non Locking – This switch tells the interval-based preemption to use a non-locking
preemption call input, which means that if the call goes away before the controller has a
chance to launch the run, the preemption will be ignored. If Non Locking is set to OFF,
then the preemption call will latch until serviced, even if the physical call goes away. And
if the run starts, then it will last at least the programmed Min Duration period.
Delay – The time, in seconds, that the controller will wait to recognize a preemption
input. The preemption input call must be active for at least this many seconds before the
controller will start a preemption sequence.
228
Interval-Based Preemption Programming Screens
Min Duration – The minimum amount of time, in seconds, that the controller will run a
preemption, once one it is started. Valid values are from 0 to 65535 seconds (18.2
hours). This timer begins counting at the end of the Delay timer. If Delay is set to 0
(zero), then the Min Duration timer begins counting as soon as the preemption input
arrives. Min Duration prevents the Dwell state from ending until this time limit has been
met. Min Duration is ignored if an Auto Flash request comes in and Override Flash is set
to ON.
Max Presence – This is an upper limit on how long a preemption input can be ON
before the controller considers it invalid. Valid values are from 0 to 65535 seconds. If the
input stays high longer than this time, the controller will return to normal operation,
exiting out of the preemption run in the normal manner. The input will be considered
invalid until the input returns to the OFF state. A value of 0 means that this test is
disabled.
229
Track Interval Data Menu and Screens
The items on this menu are used to define the optional ‘track clearance’ portion of your
interval-based preemption runs. These are programmed in much the same way that the
normal operating signal plan is programmed.
M AI N M EN U > 2.P ROGR AM M ING > 7. I NTER V AL > 3.P REEM PTIO N > 2. T R AC K I NTERV AL D AT A
2.7.3.2
TRACK INTERVAL DATA MENU
1. TRACK INTERVAL TIME
2. TRACK CHANNELS TO INTERVALS
3. TRACK OUTPUTS TO INTERVALS
Figure 197 – Track Interval Data Menu
If you wish to use a Track portion to your preemption run, you must program the interval
times, and either the channel-to-interval or outputs-to-interval mappings. First, start with
the timings by choosing option 1 . T r a c k I n t e r va l T i m e .
2.7.3.2.1
TRACK INTERVAL TIMERS
Preempt#..001 Press 1-6 to select
Intervals ->
1
2
3
2.0 5.0 10.2
4
5.0
5
2.5
6
4.0
7
2.0
8
0.0
9
0.0
1
0
0.0
1
1
0.0
1
2
0.0
1
3
0.0
1
4
0.0
1
5
0.0
1
6
0.0
1
7
0.0
1
8
0.0
1
9
0.0
2
0
0.0
2
1
0.0
2
2
0.0
2
3
0.0
2
4
0.0
Figure 198 – Track Interval Timers screen
The Track Interval Timers screen is used to define which intervals will be active during
the Track portion of an interval-based preemption run. Notice on the third line of this
screen that you must first choose which of the six available preemption runs you wish to
program. You can switch between the runs by pressing the number of the run
(keys
through
.)
Once you’ve chosen the run you wish to program, enter times other than zero to activate
the intervals within the run. Only intervals with non-zero time are served during a run. (If
all 24 of the intervals are set to 0.0 time, then the track portion of the run will be skipped
230
entirely.) The screen displays the times for intervals 1 (top left corner) to 24 (bottom right
corner.) Interval times can be any value from 0.0 to 25.5 seconds. Unused intervals
must be placed at the end of the Track Clear section, i.e. don’t put any timed intervals
after any zero intervals. If the time for all of these Track Clear intervals are zero, then
there will be no track clearance used during the run, and the preemption will proceed
directly to the Dwell section of the run (which is the normal setup for emergency vehicle
preemption.)
Once you’ve decided which track intervals will be used in the run, press
to return to
the Track Interval Data Menu, and then choose either option 2. Track Channels to
Intervals or option 3. Track Outputs to Intervals. Option 2 is a bit simpler to program, as
it assumes that controller outputs are mapped through standard channels to the green,
yellow, red signal heads of the cabinet in the typical manner. But Option 3 gives the
operator more leeway in programming the outputs of the controller for any given interval,
including the option to send outputs to other signal outputs such as warning signals, or
to multiple signal heads at once, such as flashing yellow and red together. Choosing the
Outputs to Intervals programming option will require the controller to have an accurate
I/O Mapping plan in place, so it knows where to route the outputs to physical pins on the
controller or BIUs of the cabinet. (Refer to “I/O Mapping ” on page 95.)
Let’s start with the Track Channel Setup screen:
2.7.3.2.2 TRACK CHANNEL SETUP PG1of2
1 1 1 1 1 1 1
chnl->1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
I 1..r R r R
I 2..G R G R
I 3..Y R Y R
I 4..R R R R
I 5..R G R G
I 6..R Y R Y
I 7..r R r y
I 8..G R G R
I 9..Y R Y R
I 10..
I 11..
I 12..
Figure 199 – Track Interval Channels to Intervals screen
Again, first choose from the numbered keypad keys
through
to select which
preemption run you wish to program. The run being programmed is shown next to the
Preempt#.. label.
This screen allows an operator to define the interval signal sequence of the Track
portion of the preemption run. The table allows each interval to be programmed with a
channel/signal output. For example, during interval number 1, we may want to start with
an all red intersection, so we’ll tell the controller to use the Red signal of all of the
channels. In example shown in Figure 200, we see how a typical nine interval track run
with four channels of output might be programmed. In a way, the screen can be thought
of as a player piano roll, or a music box cylinder, which is ‘played’ by the controller by
running from the top of the table to the bottom. It spends the times that were defined on
the previous screen (‘Track Interval Time’) in each interval.
231
As with the standard intersection interval-based programming, during an interval, a
channel can have any of these possible outputs:
Each cell in the table can be set to one of these available signal options:
G — Solid green
R — Solid Red
W — Walk
D — Don’t Walk
r — Flashing red
In our example, the track run is using flashing red signals to indicate that an channel is
about to get the Green.
The other option for programming the Track intervals is to define outputs for each
interval, rather than channel/signals. Again, to use the interval-to-output programming,
you will need to know how you have defined the controllers I/O map under the Unit
Configuration > Comms and I/O Setup menu.
(M M > 2 > 1 > 5 > 4 .)
2.7.3.2.3 TRACK OUTPUT SETUP PG 1of11
Preempt #....1 Press 1-4 to select
Intvl(1-12) 1 2 3 4 5 6 7 8 9 0 1 2
Out 1.......X
Out 2....... X
Out 3.......
X
Out 4.......
X
Out 5.......
X
Out 6.......
X
Intvl(13-24)3 4 5 6 7 8 9 0 1 2 3 4
Out 1.......
Out 2.......
Out 3.......
Out 4.......
Out 5.......
Out 6.......
Figure 200 – Track Output Setup screen
Again, you will need to program the outputs for each interval that has a non-zero time in
the Track portion of your preemption run. Make sure you are programming the correct
run (from the six available), as indicated next to the Preempt #.... label. Since there are
a lot more outputs than there were channels, this no longer fits on a single screen. The
rest of the 64 available outputs for each interval can be accessed by using the
and
keys.
Each output can be set to be ON, OFF, or flashing during the interval. Cycle through the
three values using the Yes or No keys. ON is indicated by an ‘X’. OFF is shown as a
blank. And Flashing is indicated by an ‘F’.
232
Dwell Interval Data Menu and Screens
The Dwell portion of the interval-based preemption runs is programmed exactly in the
same way the Track portion is. You have three screens of information: time per interval,
channel-to-interval mapping, and output-to-interval mapping. As with the Track portion of
the run, there are 24 programmable intervals available during the Dwell portion.
M AI N M EN U > 2.P ROGR AM M ING > 7. I NTE RV AL > 3.P REEM PT ION > 3. D W ELL I NTERV AL D AT A
2.7.3.3
DWELL INTERVAL DATA MENU
1. DWELL INTERVAL TIME
2. DWELL CHANNELS TO INTERVALS
3. DWELL OUTPUTS TO INTERVALS
Figure 201 – Dwell Interval Data Menu
Unlike the Track portion, Dwell is not optional. If you do not correctly program the Dwell
portion of the preemption run, you will not have a valid preemption program. Also, the
Dwell portion operates slightly differently than Track. By default, the Dwell run will run
through the interval and then remain in the last interval until the run call clears. (Or, you
have the option to use the Cycle Dwell command on the PREEMPT MODIFIERS screen
(MM > 2 > 7 > 3), which instructs the ATC to run the sequence of Dwell intervals over
and over until the run call clears.)
As with the Track portion, we must first define which intervals will be used during the
Dwell run by setting their times to something other than 0.0. Choose among the number
keys
to
these screens.
to select which preemption run you wish to program within each of
233
M AI N M EN U > 2.P ROGR AM M ING > 7. I NTE RV AL > 3.P REEM PT ION > 3. D W ELL I NTERV AL
D AT A > 1.D WE LL I NTER V AL T I M E
2.7.3.3.1
DWELL INTERVAL TIMERS
Intervals ->
1
2
3
2.0 5.0 10.2
4
5.0
5
2.5
6
4.0
7
2.0
8
0.0
9
0.0
1
0
0.0
1
1
0.0
1
2
0.0
1
3
0.0
1
4
0.0
1
5
0.0
1
6
0.0
1
7
0.0
1
8
0.0
1
9
0.0
2
0
0.0
2
1
0.0
2
2
0.0
2
3
0.0
2
4
0.0
Figure 202 – Dwell Interval Timers screen
Interval times can be any value from 0.0 to 25.5 seconds. Any unused intervals during
the Dwell portion of the run should be placed at the end of the Dwell section (i.e. Don’t
program any intervals with non-zero times after one that is set to 0.0 . . .they won’t be
serviced.) If ALL of the Dwell intervals have a zero time, then the controller will
automatically dwell in all red during the run.
After you’ve defined which Dwell intervals will be used, use the Channel-to-Interval and
Outputs-to-Interval programming screens to define what signals and outputs are shown
during each interval period. This programming is done exactly the same way as
described in the Track portion. For that discussion, see page 230.
D AT A > 2.D WE LL C H AN NELS T O I NTER V ALS
2.7.3.3.2 DWELL CHANNEL SETUP PG1of2
1 1 1 1 1 1 1
chnl->1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
I 1..
I 2..
I 3..
I 4..
I 5..
I 6..
I 7..
I 8..
I 9..
I 10..
I 11..
I 12..
Figure 203 – Dwell Interval Channels to Intervals screen
234
Again, the available signal outputs for each channel are:
G — Solid green
R — Solid Red
W — Walk
D — Don’t Walk
r — Flashing red
D AT A > 3.D WE LL O U TPUT T O I NTERV AL S
2.7.3.3.3 DWELL OUTPUT SETUP PG 1of11
Preempt #....1 Press 1-4 to select
Intvl(1-12) 1 2 3 4 5 6 7 8 9 0 1 2
Out 1.......X
Out 2....... X
Out 3.......
X
Out 4.......
X
Out 5.......
X
Out 6.......
X
Intvl(13-24)3 4 5 6 7 8 9 0 1 2 3 4
Out 1.......
Out 2.......
Out 3.......
Out 4.......
Out 5.......
Out 6.......
Figure 204 – Dwell Output Setup screen
Dwell outputs can be programmed to be ON (‘X’), OFF (‘blank’), or Flashing (‘F’). The
outputs you are mapping to are defined in “I/O Mapping”, described on page 95.
235
Exit Interval Data Menu and Screens
The Exit Interval Data Menu is used to program the exit portion of an interval-based
preemption run. Just as with the Track and Dwell portions, there are up to 24 intervals
that can be used to transition the run from the end of the Dwell portion, back to normal
intersection operation.
M AI N M EN U > 2.P ROGR AM M ING > 7. I NTE RV AL > 3.P REEM PT ION > 4. E XIT I NTERV AL D AT A
2.7.3.4
EXIT INTERVAL DATA MENU
1. EXIT INTERVAL TIME
2. EXIT CHANNELS TO INTERVALS
3. EXIT OUTPUTS TO INTERVALS
Figure 205 – Exit Interval Data Menu
To program the Exit portion of an preemption run, first define which intervals will be used
by setting their times to something other than zero on the Exit Interval Time screen. On
all of these programming screens, start by selecting which run you wish to program by
pressing one of the number keys from
to
.
> 1.E XIT I NTE R V AL T IM E
2.7.3.4.1
EXIT INTERVAL TIMERS
Intervals ->
1
2
3
2.0 5.0 10.2
4
5.0
5
2.5
6
4.0
7
2.0
8
0.0
9
0.0
1
0
0.0
1
1
0.0
1
2
0.0
1
3
0.0
1
4
0.0
1
5
0.0
1
6
0.0
1
7
0.0
1
8
0.0
1
9
0.0
2
0
0.0
2
1
0.0
2
2
0.0
2
3
0.0
2
4
0.0
Figure 206 – Exit Interval Timers screen
Interval times can be any value from 0.0 to 25.5 seconds.
236
> 2.E XIT C H AN NELS TO I NTER V AL S
2.7.3.4.2 EXIT CHANNEL SETUP PG1of2
1 1 1 1 1 1 1
chnl->1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
I 1..
I 2..
I 3..
I 4..
I 5..
I 6..
I 7..
I 8..
I 9..
I 10..
I 11..
I 12..
Figure 207 – Exit Interval Channels to Intervals screen
The per-interval programming of the Exit phase of the preemption run is handled in
exactly the same way as it is in the Dwell and Track portions. For a detailed description
of the use of the Channels-to-Intervals and Outputs-to-Intervals programming screens,
refer to the Track programming section (See page 230.)
> 3.E XIT O UTP UTS TO I NTERV AL S
2.7.3.4.3 EXIT OUTPUT SETUP
Preempt #....1 Press 1-4 to
Intvl(1-12) 1 2 3 4 5 6 7 8
Out 1.......X
Out 2....... X
Out 3.......
X
Out 4.......
X
Out 5.......
X
Out 6.......
X
Intvl(13-24)3 4 5 6 7 8 9 0
Out 1.......
Out 2.......
Out 3.......
Out 4.......
Out 5.......
Out 6.......
PG 1of11
select
9 0 1 2
1 2 3 4
Figure 208 – Exit Output Setup screen
The Channels-to-Intervals table can be filled in with any of these values for each
channel for each interval. (Again, only those intervals with non-zero times assigned will
be served, no matter what values are chosen on these two screens.
G — Solid green
R — Solid Red
W — Walk
D — Don’t Walk
237
r — Flashing red
And any of the Outputs can be set to one of these three values:
X — Output is ON
‘ ‘ (blank) — Output is OFF
R — Solid Red
238
Interval Skipping Screens
This screen is used to set interval skipping conditional parameters, which also function
as ped timings for interval-based preemption. These are extra performance
requirements placed on the outputs of interval-based operation during either preemption
or interval skipping operation.
Note
An interval, during normal operation, is available for skipping if it is both
A) Actuated and B) NOT Recalled.
M AI N M EN U > 2.P ROGR AM M ING > 7.I NTER V AL > 4.I NTERV AL S KIPPING
2.7.4
INTERVAL SKIPPING
PG1of2
CNL 1 -- 2 -- 3 -- 4 -- 5 -- 6 -- 7 -- 8
---------------------------------------PED CLEARANCE
0-255 Seconds
000 000 000 000 000 000 000 000
YELLOW CLEARANCE
0.0 0.0 0.0 0.0
3.0-25.5 Seconds
0.0 0.0 0.0 0.0
RED CLEARANCE
0.0 0.0 0.0
0.0-25.5 Seconds
0.0 0.0 0.0 0.0
0.0
----------------------------------------
Figure 209 – Interval Skipping screen
Channels 1 through 16 — The parameters on this screen are set PER LOAD SWITCH,
so the output channel in your cabinet will have the following restrictions during normal
interval or interval preemption operations. Use the
and
keys to switch
between the screen for Channels (‘CNL’) 1 through 8 and the screen for Channels 9
through 16.
Ped Clearance — This is a minimum time placed on the pedestrian clearance portion of
a pre-timed plan if either interval skipping or a preemption run become active. This is a
value in seconds between 0 and 255 that the flashing Don’t Walk signal must be
displayed (if present in the plan). If no value is set, there is no minimum ped clearance
time requirement during operation.
Amber Clearance — This is a minimum time placed on the vehicular clearance
(Yellow/Amber) portion of a pre-timed plan if either interval skipping or a preemption run
become active. This is a value in seconds between 0.0 and 25.5. If no value is set, there
is no minimum clearance time requirement during operation. The requirement in the
NTCIP standard for this feature is: “Following the termination of the Green interval of
each channel the controller shall provide a minimum Amber Clearance interval during
initial preemption or interval skipping.”
Red Time — After a vehicular clearance (Yellow or Amber) signal and a Ped Clearance
signal, this is the minimum time that the controller must show the red signal when
transitioning to interval skipping or a preemption run. Valid values are 0.0 to 25.5
seconds.
239
Additional Details about Skipping and Preemption Transitions
Pre-timed signal plans are based on a predefined sequence of intervals. These intervals
have a specific signal light pattern. A series of intervals that control a specific direction of
vehicle movements (green, amber, red) is what drives a channel and the output of that
channel feeds a load switch.
If more than one interval is defined as actuated, the controller will be able to skip
intervals that do not have an associated call on them. The skipping of intervals is from
one actuated interval to another actuated interval. For some signal plan configurations,
the specific interval defined as actuated might have to be adjusted to achieve the correct
color operation on the signal head. Typically, this means that Interval 3 will need to be
set as actuated.
Another point to note is that if the signal plan or timing plan transfer interval is not
reached, the signal plan or timing plan is not reloaded. This only becomes a factor if the
timing or signal plan has been changed via the ATC Link software or some other NTCIP
central system. However, the plans will always be loaded when a plan change occurs
due to a time-of-day event.
Just like with preempt processing, the controller will have to create new intervals to
achieve an orderly and proper transition between intervals. If new intervals need to be
created, the controller will use the same minimums for interval skipping as it uses for
preempt processing: three seconds for amber, two seconds for red, and three seconds
for flashing Don’t Walks. These values can be set on the Preempt & Interval Skipping
tab. This tab has entries for pedestrian clearance, amber clearance and red time for
each channel. Note that the controller has a minimum three second delay for any amber
interval. The below is an example of interval skipping, shown in the ATCLink window.
Figure 210 – Actuated intervals in theATCLink Interval table
In the above example, intervals 6 and 10 are actuated. The controller will dwell in
Interval 1 until a call is placed on Vehicle 1 or Pedestrian 1 (for interval 6) or Vehicle 2 or
Pedestrian 2 (for interval 10). If a call is placed on both 1 (either pedestrian or vehicle)
and 2 (either pedestrian or vehicle), the controller will cycle through all 12 intervals. If a
240
call is placed on 1 (either pedestrian or vehicle) and no call on 2 (either pedestrian or
vehicle), the controller will go from Interval 1 to 6, 7, 8, and 9, then back to Interval 1. If a
call is placed on 2 (either pedestrian or vehicle), the controller will go from Interval 1 to
10, 11, and 12 then back to Interval 1.
Note
The controller skips from actuated interval to actuated interval (Interval 1
is an actuated interval by default). If there is a specific signal pattern that
has to run after Interval 1 but before the actuated Interval 6 (for example
to bring up an arrow), then Interval 3 should be defined as actuated and
not Interval 6.
Note
All interval-skipping configurations must be tested in a cabinet with a
correctly configured conflict monitor. Each actuated interval should be
tested and watched closely to verify proper three-color operation.
241
INTERVAL PREEMPTION PRIORITY
Interval Preemption is a special program that operates within the controller. The
preemption program accepts commands from six preempt inputs and provides the timing
and signal display programmed to occur in response to each.
Preemption controls are applied using any NTCIP management station.
The preemption program reads the current signal display at the time of preempt and
provides transition timing, and signal display, to a specified preempt setting. Once
preempt has been satisfied, the preemption program provides an exit transition timing
and signal display to a programmed (one for each of the six preempt inputs) return-tonormal condition.
Input Priority
The Preemption program allows you to set priorities of the preemption inputs. The
priorities are as follows:
Table 38 – Input Priority
Input Priority
242
Description
Preempt 1
Normally has priority over Preempt 2. If Preempt 1 becomes active while the
Preemption program is in the Preempt 2 routine, the controller immediately
terminates the Preempt 2 routine and enters the Preempt 1 routine. When
Preempt 2 has been terminated by Preempt 1, control will not return to Preempt
2 at the end of Preempt 1 except when Preempt 2 demand is still present at the
end of Preempt 1.
The priority of Preempt 1 over Preempt 2 can be cancelled. If the priority has
been canceled and the Preempt 1 becomes active while the preemption
program is in the Preempt 2 routine, the Preempt 2 completes normally. After
Preempt 2 is complete, the controller enters the Preempt 1 routine only if the
Preempt 1 demand is still present.
When Preempt 2 becomes active while the preemption program is in the
Preempt 1 routine, the Preempt 1 routine complete normally regardless of the
priority of Preempt 1 versus Preempt 2. After Preempt 1 is complete, the
controller enters the Preempt 2 routine only if the Preempt 2 demand is still
present. Whenever both inputs become active at the same time, Preempt 1
occurs first.
Preempt 2
Normally has priority over Preempt 3. The priority of Preempt 2 over Preempt 3
can be cancelled via program entry.
Interval Preemption Priority
Input Priority
Description
Preempt 3, 4, 5, and 6
Normally has equal status (priority cancelled). A priority of Preempt 3 over
Preempt 4, Preempt 4 over Preempt 5, and Preempt 5 over Preempt 6 can be
set using the ATC Link software.
Operation capability as described above for Preempt 1 and 2 is provided for
Preempt 2 and 3, 3 and 4, 4 and 5, and 5 and 6.
The default priorities above were established assuming Preempt 1 and Preempt
2 were set as railroad and Preempt 3 to Preempt 6 as emergency vehicle
(Authorized Engineering Information).
Automatic Flash
All Preempt routines will normally have priority over Automatic Flash. If any
Preempt becomes active while the controller is in Automatic Flash, Automatic
Flash terminates normally and the controller enters the Preempt routine.
The priority of Preempt over Automatic Flash can be cancelled using the
ATC Link software. If the priority of Preempt over Automatic Flash has been
cancelled, and a Preempt input becomes active while the controller is in
Automatic Flash, the controller will remain in Automatic Flash until the demand
(both Automatic Flash and Preempt) is terminated
Start Up Flash
Start-Up Flash will always have priority over all Preempt routines. If a Preempt
input becomes active or is active during Start-Up Flash, the controller maintains
the Start-Up Flash condition for the duration of the both Preempt demand and
Start-Up Flash time
External Start
External Start always has priority over all Preempt routines. If External Start
becomes active during a Preempt routine, the controller reverts to Start-Up
Flash rather than the Initialization condition. The controller maintains the StartUp Flash condition for the duration of the External Start, Preempt demand, and
Start-Up Flash time
Memory
The controller provides input memory which can set to locking or non-locking.
When input memory is set for non-locking, termination of the input prior to
implementation of the routine will not initiate preempt operation
243
SETTING UP AN ACTUATED LEADING OR LAGGING LEFT TURN
Some special attention is required when using pre-timed operations to set up an ATC
controller for a split main street, a leading left turn movement, and skipping on both the
side street and the left turn. The actuated interval for the side street must be placed
before the interval where the side street turns green, otherwise both sides of the main
street will already have changed to red before the side street is skipped. This is
because the actuated intervals are the “skip from” and “skip to” points.
Wrong Way to Program a Leading Left Turn
Take this example of a pre-timed signal plan 1:
Figure 211 – Wrong way to program a leading left turn in interval mode (ATCLink)
This is the intuitive way to set the side street actuated interval; however when the side
street (intervals 6-9) are skipped the start point has both sides of the main street already
red. This has channel 2 clear unnecessarily.
244
Setting up an Actuated Leading or Lagging Left Turn
The pattern with no skipping is as follows:
INT SPL
1 5.0
2 6.0
3 10.0
4 3.0
5 2.0
6 6.0
7 12.0
8 3.0
9 2.0
10 6.0
11 3.0
12 2.0
ACC MIN CH1 2 3 4 5
5.0 1.0
G G
R W
11.0 1.0
G G
R W
21.0 1.0
G G
R F
24.0 3.0
Y Y
R D
26.0 1.0
R R
R D
32.0 1.0
R R
G D
44.0 1.0
R R
G D
47.0 3.0
R R
Y D
49.0 1.0
R R
R D
55.0 1.0
R G G R D
58.0 1.0
R G Y R D
60.0 1.0
R G
R D
6
D
D
D
D
D
W
F
D
D
D
D
D
When the leading left is skipped to serve the cross street, the skipping sequencer
generates this pattern:
INT ORG SPL
ACC
MIN CH1 2 3 4 5 6
1
1
5.0
5.0 1.0 G G
R W D
2
2 17.0
22.0 1.0 G G
R W D
3
3 10.0
32.0 1.0 G G
R F D
4
4
3.0
35.0 3.0 Y Y
R D D
5
5
2.0
37.0 1.0 R R
R D D
6
6
6.0
43.0 1.0 R R
G D W
7
7 12.0
55.0 1.0 R R
G D F
8
8
3.0
58.0 3.0 R R
Y D D
9
9
2.0
60.0 1.0 R R
R D D
And when the side street is skipped to serve the left turn, this is the generated pattern:
INT ORG SPL
ACC
MIN CH1 2 3 4 5 6
1
1
5.0
5.0 1.0 G G
R W D
2
2 29.0
34.0 1.0 G G
R W D
3
3 10.0
44.0 1.0 G G
R F D
4
4
3.0
47.0 3.0 Y Y
R D D
5
5
2.0
49.0 1.0 R R
R D D
6 10
6.0
55.0 1.0 R G G R D D
7 11
3.0
58.0 1.0 R G Y R D D
8 12
2.0
60.0 1.0 R G
R D D
The ATC skips from interval 5 to interval 10. Note that because the skipping starts with
interval 6, channel 2 has been cleared but it then reverts to green.
245
Correct Way to Program a Leading Left Turn
The revised signal plan 1 has the actuated interval for the side street moved to interval 3:
Figure 212 – Correct Programming for a Leading left turn in ATCLink
Red cells have been modified from the previous example.
The pattern with no skipping will be the same as before:
INT SPL
ACC MIN CH1 2 3 4 5 6
1 5.0
5.0 1.0
G G
R W D
2 6.0 11.0 1.0
G G
R W D
3 10.0 21.0 1.0
G G
R F D
4 3.0 24.0 3.0
Y Y
R D D
5 2.0 26.0 1.0
R R
R D D
6 6.0 32.0 1.0
R R
G D W
7 12.0 44.0 1.0
R R
G D F
8 3.0 47.0 3.0
R R
Y D D
9 2.0 49.0 1.0
R R
R D D
10 6.0 55.0 1.0
R G G R D D
11 3.0 58.0 1.0
R G Y R D D
12 2.0 60.0 1.0
R G
R D D
And the pattern when skipping the leading left turn to serve the cross street is the same
as before:
246
INT ORG SPL
ACC
MIN CH1 2 3 4 5 6
1
1
5.0
5.0 1.0 G G
R W D
2
2 17.0
22.0 1.0 G G
R W D
3
3 10.0
32.0 1.0 G G
R F D
4
4
3.0
35.0 3.0 Y Y
R D D
5
5
2.0
37.0 1.0 R R
R D D
6
6
6.0
43.0 1.0 R R
G D W
7
7 12.0
55.0 1.0 R R
G D F
8
8
3.0
58.0 3.0 R R
Y D D
9
9
2.0
60.0 1.0 R R
R D D
But when the side street is skipped to serve the leading left turn, channel 2 now remains
green:
INT ORG SPL
ACC
MIN CH1 2 3 4 5 6
1
1
5.0
5.0 1.0 G G
R W D
2
2 36.0
41.0 1.0 G G
R W D
3
0
3.0
44.0 3.0 G G
R F D
4
0
3.0
47.0 3.0 Y G
R D D
5
0
2.0
49.0 2.0 R G
R D D
6 10
6.0
55.0 1.0 R G G R D D
7 11
3.0
58.0 1.0 R G Y R D D
8 12
2.0
60.0 1.0 R G
R D D
The ATC skips from interval 2 to interval 10, generating new clearance intervals for
channel 1 with channel 2 remaining green.
Note that in the modifications the “do not lock here” intervals for actuated interval 3
extend from interval 3 to interval 7. This means that detector calls for interval 3 will not
lock during these intervals. This is not a problem since intervals 3-5 only ever occur
when the side street is not skipped, so there is already a locked call, and if any
additional calls were locked they would just be cleared in interval 6 anyway. Whenever
the ATC is dwelling at main street green, or while the side street is being skipped, any
calls will be locked.
247
Correct Way to Program a Lagging Left Turn
The following example shows the correct way to implement a lagging left turn. This
configuration of signal plan 2 uses the same vehicle detector inputs and pedestrian call
inputs as the previous example of signal plan 1; vehicle detector one and pedestrian call
input one bring service to the cross street whereas vehicle detector two serves the left
turn.
Note that the order of vehicle detectors is independent of intervals or interval sequence.
Actuated interval seven is not assigned any vehicle detector but is used to indicate the
desire to skip the termination of channel 2 (the concurrent main street green) when the
left turn terminates in order to return to both directions of main street traffic vehicle
movements. Because the intervals for the left turn and cross street are at different
locations in the sequence of intervals for signal plans 1 and 2 then different timing plans
must be used that have matching timings for the two different signal sequences.
However, if the correct timing plans are invoked for each signal plan then it is possible
for a change from a leading left turn to a lagging left turn based on time of day operation
using these two signal plans.
Figure 213 – Programming a lagging left turn
It should be noted that preempt and interval skipping table should be programmed with
the desired minimums for Ped Clearance, Amber Clearance and Red Clearance times
for the corresponding channels, as shown in Figure 214.
248
These values will be used during the skipping operation of the controller for any intervals
that may be generated on the fly when the controller goes to service the calling detector.
Intervals in the signal plan will be skipped but coordination will be fooled into thinking the
interval progression is normal. Furthermore, the controller will have to create intervals in
order to terminate pedestrian and vehicle movements safely by inserting new pedestrian
clearance indications, yellow change and red clearance indications.
Figure 214 – Inserting pedestrian clearance intervals to support a lagging left
249
250
Chapter 8 — Phase-based Preemption
This chapter describes how to set up phase-based preemption on an ATC controller, including
configuring a set of preemption intervals and configuring how preemption is triggered. Intervalbased preemption is discussed in the previous chapter. The following topics are discussed in
detail in this chapter:
•
Overview of Preemption, on page 252
•
The sections of a Preemption Run, on page 252
•
Preemption Linking, on page 253
•
Programming a phase-based preemption run, on page 255.
•
Details about ICC preemption, on page 265.
251
OVERVIEW
The ATC controller has separate engines and programming screens for when the
controller is running a phase-based versus an interval-based pattern. Interval-based
preemption runs were discussed in “Chapter 7 — Interval Operation”, the section
starting on page 225. Phase based preemption, on the other hand, is performed using
the screens under the 2. Programming > 6.Preemption menu, and are discussed in this
chapter.
ATC controllers can accept programming for up to six phase-based preemption runs.
(See “Chapter 14 — Serial and Data Connectors” starting on page 351 for details on pin
assignments.)
Phase-based preemption allows the operator to define three different intersection cycles
to run during a single run (TRACK, DWELL, and EXIT.) A forth option, CYCLE, can be
used in place of the DWELL portion of a run. Phase-based preemption runs allow for the
normal use of pedestrian signals, and also allow the use of overlap phases. This kind of
preemption uses the phases, rings and sequences that have already been defined in
your controller, but handles them with special preemption control and timing parameters
to customize the run to the needs of the preemption.
Sections of a Preemption Run
Before we get into the meanings of each of the parameters on the Preemption screens,
we must first introduce the basic operating theory of phase-based preemption in the
Peek ATC controllers. The ATC has six available preemption runs, each associated with
a Preemption Call input. So preemption input 1 calls Preemption Run #1, and so on.
Each of the Preemption Runs can have up to four sections, but not all of these sections
need to be used in each run. Figure 215 shows the basic sections of a preemption run.
Figure 215 – Sections of a phase-based ATC Preemption Run
A preemption run goes through the four sections in sequence, and it does not repeat the
sequence. Preemption is a ‘once through’ set of steps. However, it can be programmed
to remain in the dwell section or to use a cycle sequence. (See the next topic for details.)
The ‘Track’ section is optional. Most of the time used for a preemption run is typically
taken up by Dwell, which is normally the section in which the green signal is shown
along the street on which an emergency vehicle, or other prioritized traffic, will travel.
252
Overview
The values for all portions of a Preemption run are defined from the Preemption
Parameters menu (MM.2.6).
Cyclic Portion of a Preemption Run
Each of the sections of a preemption run are essentially programmed to perform a single
movement of traffic. There may be some ancillary overlaps providing additional
movements, and there may be pedestrian movement, but each portion of the run is
essentially a single set of signals to move one phase (or a set of compatible phases )of
traffic. The Cycle section of the run has been added to allow the heart of the preemption
run to include a set of cycling signals. If any phases are defined for the Cycle portion of
the run, it will take the place of the Dwell portion of the run. The Entry, Track, Exit and
Dwell portions of the run are tested for phase compatibility, because all of the selected
phases are assumed to be operating simulataneously. The Cycle section, on the other
hand, does not check for phase compatibility, because it assumes that the phases will
be served in sequence, as defined in the programmed Sequence that is in effect at the
time of the preemption call.
Figure 216 – Preemption run with a Cyclic section
Note that the Dwell parameters set on the Control and Timing screen under the
Preemption menu are not used during a Cycle. The only exception to this is the Flash
Dwell flag, which will prevent the Cycle from occuring. If Flash Dwell is ON, then the
Cycle phases will be ignored, and the Dwell phases will be served using the Flash logic.
(Selected phases flash Yellow, Non-selected phases flash Red.)
Preemption Linking
Another feature of phase-based preemption is the ability to link one preemption run to
another. A run with a defined link switches to that run after it completes its own Dwell
phase. And it links to the new run at the beginning of the new run’s Track phase. This
Link can be defined in each of the runs, but only to a higher number run (so run 5 can
link to 4 or 3 or 2 or 1, but 4 cannot be linked to 5, and run 1 cannot be linked to any
other run.) The new run is maintained as long as the initial preemption call input is
active. When the call goes away, the new run exits as it normally would. This is shown in
Figure 217 on page 254.
253
It is possible to link multiple preemption runs in this way, so one could link all six
preemption runs in this way, creating a single preemption call that generates one entry,
six different track and dwell sections, and one exit section.
Figure 217 – Preemption run linking
254
Programming Phase-Based Preemption
PROGRAMMING PHASE-BASED PREEMPTION
Preemption Menu
Phase-based preemption is defined on the parameter screens under the Preemption
menu.
M AIN M ENU > 2.P ROGRAMMING > 6. P REEMPTION
2.6
1.
2.
3.
4.
5.
PREEMPTION MENU
ENABLES/INPUTS
ENTRY
TRACK CLEARANCE
DWELL/CYCLIC
EXIT
Figure 218 – Preemption Menu
The Enables/Inputs screens are used to define preemption run global parameters, such
as the run enable flag, delays and run links. The other four sets of screens are used to
define the operation of the four sections of each run.
255
Enable/Input Params Screens
Option 1 on the phase-based Preemptions menu is the Enables/Inputs screen. Use the
and
keys to switch between the six preemption run definition screens.
M AIN M ENU > 2.P ROGRAMMING > 6.P REEMPTION > 1.E NABLES /I NPUTS
2.6.1
ENABLE/INPUT PARAMS
TIMES:
ENBL/DWL GRN. 0
MAX PRESENCE.00000
DELAY........ 0
LINK............ 0
INPUT MIRROR....
OVERRIDE FLASH..
1 OF 6
INPUT EXTEND.. 0
MIN DURATION..00000
IMMEDIATE EXIT....
PRIORITY OVERRIDE.
NON-LOCK INPUT....
Figure 219 – Preemption Enable/Input Parameters screen
Each parameters on each screen (1 through 6) define the global operating parameters
for that numbered preemption run.
ENBL/ DWL GRN — Important: if a value is programmed here, it enables the
preemption run. If no value is programmed here then the preempt run is disabled. This
parameter controls the minimum timing for the Dwell portion of the Preemption run. This
is a value in seconds in the range from 1 to 255 seconds. The phase or phases that
have been enabled for this preemption run will not terminate before all of these
conditions have been met:
a.) the completion of the Preemption Duration Timer (MIN DURATION on this
screen),
b.) The completion of this preemption Dwell timer (ENB/C”YL/DWL G),
c.) and the preemption call input is no longer active
Input Extend — Like the Dwell Extension, the Input Extension parameter is a value, in
seconds from 0 to 600) that the preemption input will be held ON after the actual
physical input has gone away. Note that this applies to the entire preemption run, not
just the Dwell portion, as the Dwell Extend parameter does. If both Dwell Extend and
Input Extend are programmed, both parameters will be honored, but will be timed
simultaneously, and whichever value times out last will determine when the preemption
call is allowed to go OFF.
Max Presence — This is the time in seconds that the controller will consider a
preemption input valid. If the preemption detector is faulty, or if a vehicle parks within
sight-line of the preemption receiver and keeps the intersection input high the whole
time, this timer functions as a ‘time out’ for the preemption input.
256
Min Duration — This is the minimum length of time, in seconds, that the full preemption
is allowed to run. This timer begins at the end of any Delay time you’ve placed on the
run input, and it will prevent the Dwell phase from ending until this time has elapsed.
Delay — This is a delay time, in seconds, that the controller will wait after the
preemption input goes active before the controller will begin executing the Entry phase
of the run. Note that if the input goes OFF before the delay time is over, and the NonLock Call option is selected above, the run will not start.
Link — This is a way to link the operation of one preemption run to another, but it only
works if you are linking to a higher priority run (i.e. Run #2 links to Run#1 is valid, but
Run#1 cannot link to any other run) The link is activated at the end of the Dwell phase of
the current run, and jumps to the beginning of the Track phase of the linked run. The
rest of the new run is performed as defined, however it’s input is controlled by the
original run’s preemption call input.
Immediate Exit — This switch tells the run to immediately exit for a higher priority
preemption call. When this parameter is set and a higher priority (higher number)
preemption input becomes active, it causes the current preemption run to terminate. The
Exit phases of the current run get replaced with the track clearance or Dwell phases of
the new run. If the current run is in Dwell, and the minimum dwell time hasn’t been met
yet, the run waits for this limit before terminating. If the Dwell flash is active, a normal
exit from flash to stop/go operation is enforced before the termination. When this
parameter is NOT set, the normal term of the preemption run, including its Exit phases,
are used to allow a graceful transition back to normal operation before servicing the
higher priority run.
Input Mirror — This is a feature that is used to check for cabinet wiring errors in
connecting preemption inputs. The controller will test a preemption input and one other
input to verify that they are opposite in state from one another. For example, if
Preemption input #3 is low, the input mirror input should be high. If Preempt#3 goes
high, then the mirror must switch low. The channel to watch for this preemption input
mirror must be defined in the cabinet I/O Map by assigning the Function ‘Preempt Mirror’
to an input pin. (Refer to “I/O Mapping” on page 95.) This Preempt Mirror function can
only be applied to one physical input in the I/O map.
Priority Override — Normally, preemption calls are able to interrupt one another with
no priority, the Priority Override command, however, tells this preemption run that the
priority order of the preemption numbers will apply to this run. If this option is checked,
the number order of the call is important, Preemption run 1 is a higher priority than 2 and
so on. So, if the controller is running Preemption Run #3, and a Preemption #2 call
comes in, and the PRTY Override for run #3 is set to ‘X’, then Preemption #2 will
interrupt Run 3 and begin operating. If PRTY Override was set to ‘ ‘, Run #3 would
continue and the controller would ignore the Preemption #2 call.
Override Flash — Do not allow preemption to override flash. If this option is checked
‘X’, a preemption call will not override automatic flash mode.
Non-Lock Input — This toggles on (‘X’) or off (‘ ‘) to indicate whether this preemption
run has a non-locking input call. This means that if Non-Lock Call has an ‘X’, and if a call
is placed on this Preemption input, but the call goes away before the Delay timer has
completed (see ‘Delay’, below), the call will be discarded and no preemption run will
result.
257
Entry Screens
Option 2 on the phase-based Preemptions menu are the Entry screens. Use the
and
run.
keys to switch between the six Entry definition screens, one per preemption
M AIN M ENU > 2.P ROGRAMMING > 6.P REEMPTION > 2.E NTRY
2.6.2
ENTRY PARAMS
1 OF 6
ENTRY TIMES MODE.min/other(1)
TIMES:
ENTRY WALK....
ENTRY MIN GRN.
ENTRY RED CLR.
0 ENTRY PED CLR..
0 ENTRY YELLOW...
0.0 ENTRY DWELL RED
0
0.0
0
FDW THRU YELLOW.......................
OVERRIDE STARTUP YELLOW AND RED TIMES.X
Figure 220 – Preemption Entry parameters screen
Entry Times Mode — Preemption Entry Time Mode to use. This setting applies to every
interval in the run. If set to min/other(1), the run uses the smaller value compared
between the preemption entry time and the phase time. If set to max(2), the run uses
the larger value compared between the preemption entry time and the phase time.
Finally, if set to preempt(3), the run always uses the preemption entry time value.
Entry Walk — This is similar to the Min Green function for preemption, only it prevents
any Pedestrian Walk phase during the preemption run from being cut off by the sudden
removal of the preemption input signal. This is the minimum time, in seconds, that
should be allowed for preemption run Walk signals. This minimum walk time also applies
to the normal operation pedestrians phases that are being serviced when the
Preemption run is first activated.
Entry Ped Clr — This is the amount of clearance time that is allotted to a pedestrian
phase that is interrupted by the preemption run. The actual amount of time that is used
for pedestrian clearance is either this time, or the time stored in the normal pedestrian
phase, whichever is the lower value.
Entry Min Grn — Also known as the Preempt Minimum Green Time, this is the
minimum amount of time, in seconds, that any of the preemption phases can be allowed
to show a green signal. This is to prevent a Dwell or other phase from being truncated in
an unsafe manner should the preemption input suddenly go away. This minimum time
also applies to the normal operation greens that are active when the Preemption run is
first activated. In the case of entry phase greens, the controller will compare this value
with the green phase’s own Min Green time and use the lesser value.
Entry Yellow — Entry Yellow Change time, in tenths of a second. The value can be
anything from 0.0 to 25.5 seconds. This limits the change of timing for a normal Yellow
258
that is terminated by a preemption initiated transition. The value will be compared to the
phase’s Yellow Change time, and the lesser value will be used. CAUTION: If this value
is set to 0.0, the phase’s yellow will be terminated immediately.
Entry Red Clr — Entry Red Change time, in tenths of a second. The value can be
anything from 0.0 to 25.5 seconds. This controls the timing of a red signal that is
interrupted by a preemption call. The red will not be terminated before the lesser of this
value or the phase’s own Red Clearance timer. CAUTION: If this value is set to 0.0., the
phase’s red will be terminated immediately.
Entry Dwell Red — When this parameter is set to a non-zero value, and there are no
Track phases programmed for this preemption run, will automatically terminate any main
street phases that are programmed as Dwell phases. This is done to prevent the ‘left
turn trap’ scenario. Please note that if this value is non-zero and the dwell phases are
programmed as phases 2 and 6, and a red interval is programmed, and there are no
track phases programmed, the controller will terminate phases 2 and 6, rest in Red for
the programmed time, and then bring phases 2 and 6 back on.
FDW Thru Yellow — When checked, this causes a flashing ‘Don’t Walk’ signal through
the yellow signal during entry into the preemption run.
Override Startup Yellow and Red Times — This flag determines how the ATC should
operate if a preemption input becomes active during the controller’s startup timing. If
checked, a preemption that occurs during the startup sequence will override the startup
yellow and red timing with that preemption run’s calculated yellow and red timings. If
unchecked, the programmed startup timings will be honored before the controller goes
into the preemption run.
259
Track Clearance Screens
Option 3 on the phase-based Preemptions menu are the Track Clearance screens. Use
the
and
keys to switch between the six Track Clearance definition screens.
M AIN M ENU > 2.P ROGRAMMING > 6.P REEMPTION > 3.T RACK C LE ARANCE
2.6.3
TRACK CLEAR PARAMS
TRACK PH
TRACK OL
1 OF 6
1 1 1 1 1 1 1
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
TRACK GREEN TIME...................
TRACK YELLOW TIME..................
TRACK RED CLEAR TIME...............
INHIBIT TRACK OVERLAP TRAIL GREEN..
TRACK GREEN RESERVICE IF NEW CALL..
0
0.0
0.0
Figure 221 – Track Clearance Parameter screen
Track Ph — Use these check boxes to select which phases will be green during the
‘Track clearance’ section of the run. This portion of the run is optional. (i.e. You do not
need to have any phases selected for Track Ph and the run can still be valid.) Press
to insert an ‘X’ and
to clear an ‘X’.
Track OV — Which of the 16 available overlaps will be used during the Track clearance
section of the run. These will be tested for compatibility with the Track Phases chosen
above. If any are found to be incompatible, the controller will ask for the selection to be
changed. Press
Track Green Time — The amount of time, in seconds, that is allotted to the Track
phases portion of this pedestrian run. The default value is zero.
Track Yellow Time — Track clearance yellow change time in tenths of seconds (0.0 to
25.5 seconds.) The lesser value between this parameter and the yellow change time of
the phases designated as Track phases controls the yellow timing for the track
clearance movement. Track phases are enabled by placing a check in the Track Ph row
on the Phase/Pedestrian/Overlaps screen of the Preemption menu. (MM > 2 > 6 > 2)
Track Red Clear Time — The Track Red Clear time, in tenths of seconds. Valid values
can be in the range 0.0 to 25.5 seconds. The lesser value of this parameter or the
phase’s own red clearance timing value (of whichever phase or phases have been
assigned to be Track phases during this preemption run) will be used. Track phases are
enabled by placing an ‘X’ in the Track Ph row on the Phase/Pedestrian/Overlaps screen
of the Preemption menu. (MM > 2 > 6 > 2)
Inhibit Track Overlap Trail Green — Inhibit Overlaps After Track Clearance. This
parameter will cause the termination of any overlaps that are currently timing after the
track green interval. For example, if the Track Clearance phase includes a trailling
260
overlap with Green/Yellow/Red times assigned, this setting will force the overlap to
terminate with the parent phase.
Track Green Reservice If New Call — Force a reservice of the track phase while the
preemption input is still active. Prevents the run from moving to the Exit portion of the
run. If the preempt call is removed and comes back, then do not serve the exit phase
and go directly to the track phase.
261
Dwell / Cyclic Screens
Option 4 on the phase-based Preemptions menu are the Dwell / Cyclic Parameter
screens. Use the
and
keys to switch between the six Dwell/Cyclic screens.
M AIN M ENU > 2.P ROGRAMMING > 6.P REEMPTION > 4.D WELL /C YCLIC
2.6.4
DWELL
DWELL
DWELL
CYCLE
CYCLE
CYCLE
DWELL/CYCLIC PARAMS 1 OF 6
1 1 1 1 1 1 1
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
PH
PD
OL
PH
PD
OL
DWELL EXTEND TIME...................
FLASH DWELL PHASE YELLOW............
ENABLE EXCLUSIVE PEDS DURING DWELL..
0
Figure 222 – Dwell / Cyclic Parameters screen
Dwell Ph — Use the Yes and No buttons to select which of the intersection phases will
be Green during the Dwell portion of the preemption run. An ‘X’ indicates that this phase
will be a Dwell phase during the run. Press
At least one Dwell phase is required in order for the controller to judge this is a valid
preemption run. If the Flash Dwell option is checked, above, then these phases will be
displayed as flashing yellow rather than green. The phases selected here will be tested
for compatibility with one another. Also, the Dwell phases will be ignored if any phases
are programmed as Cycle phases, as the Cycle will take precedence. (Unless ‘Flash
Dwell’ is selected.)
Dwell Pd — Use this array to select which of the intersection phases will be pedestrian
Walk phases during the Dwell portion of the preemption run. Press
to insert an ‘X’
and
to clear an ‘X’. During preemption, pedestrian phases don’t automatically run
with their parent vehicular phases. That is why these selections are available for the
Dwell, Cycle, and Exit portions of the preemption run programming.
Dwell OL — Select which overlaps will be used during the Dwell portion of the
preemption run. These overlaps will be tested for compatibility with the selected Dwell
Phases.
Cycle Ph — Unlike the other portions of the run, the Cycle portion may serve multiple
movements of vehicles during the run. When programmed, the Cycle portion will take
the place of the Dwell portion of the run, and it will serve a selection of phases in
sequence, as defined by the phase sequence programming that was in effect when the
preemption run was called. The only exception to this is if the Dwell portion is
programmed with the ‘Flash Dwell’ flag set, in which case the Dwell portion will be
262
served, with all selected phases flashing yellow, and all non-selected phases flashing
Red. Press
Cycle Pd — Selects which pedestrian phases will be served during the Cycle portion of
the preemption run. If more than one are selected, the phases will be served based on
the programmed Sequence of the Vehicular parent phases. Press
and
to insert an ‘X’
Cycle OL — Used to select which overlaps will be served during the Cycle portion of the
preemption run. These will be served using the overlaps’ defined parent/modifier phase
programming. Press
Dwell Extend Time — Dwell Extension time, in seconds. This value, which can be
anything between 0 and 255 seconds, determines the time that the preemption call will
be kept active during the Dwell interval after a physical call on the input has been
removed.
Flash Dwell Phase Yellow — This is an option that tells the preemption run how to
handle phases that are marked as a ‘DWELL Ph’. When this option is checked ‘X’, dwell
phases in the run flash Yellow during the dwell period. Phases not selected as dwell
phases will flash Red. Note that this flag is the only control that will override the
programming of a Cycle portion to the preemption run. Normally, Cycle will take the
place of the Dwell portion if any Cycle phases are selected. However, Flash Dwell will
override this; the Cycle portion will be ignored and the selected Dwell phases will flash
Yellow and unselected Dwell phases will flash Red, until the preemption input goes
away.
Enable Exclusive Peds During Dwell — When this option is checked, Exclusive
Pedestrian phases (XPED) as programmed on the Exclusive Pedestrian screen
(MM.2.1.0, refer to page 128) will be served during the preemption run. If not checked,
XPED programming will not be active during the preemption run. This flag will determine
XPED operation during this preemption run, no matter what value is assigned to the
XPED’s Global Enable parameter.
263
Exit Screens
Option 5 on the phase-based Preemptions menu are the Exit Parameter screens. Use
the
and
keys to switch between the six Exit screens.
M AIN M ENU > 2.P ROGRAMMING > 6.P REEMPTION > 5.E XIT
2.6.5
EXIT
EXIT
EXIT PARAMS
PH
PD
1 OF 6
1 1 1 1 1 1 1
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
Figure 223 – Exit Parameters screen
Exit Ph — Use this array of checkboxes to select which of the intersection phases will
be green during the Exit portion of the preemption run. Press
Exit Pd — Select which pedestrian phases will be served during the Exit portion of the
preemption run. Press
264
ICC Preemption
ICC PREEMPTION
An Illinois Commerce Commission (ICC) Railroad preemption is a unique preemption
specification to which the ATC is compliant. To envoke an ICC railroad preemption, you
will first need to change the ICC ENABLE field on the USTC Misc Menu (MM.2.1.7) from
OFF to ON.
2.1.7
USTC MISC MENU
PG1OF1
LANGUAGE
:English(0)
STEADY RED
DURING FLASH
:000
REQUEST TIME SYNC :OFF
NEXT PHASE CONTROL:PERSISTENT(0)
TEXAS DIAMOND
:None(0)
ICC ENABLE
:ON
MIZBAT MASTER ID : 0
Figure 224 – USTC Miscellaneous Screen
To modify the data within the critical operation area (Cyclical Redundancy Check [CRC]
block), it is required that a formatted USB flash drive be inserted into the ATC. Once
inserted, the ATC will verify the presence of a required folder/file. If present, the ATC will
show a new menu item named ‘Unlock database’. If the required folder/file is not found
or is incorrect, the ATC will not present the option to ‘Unlock database’.
When the Unlock database is selected, the ATC will move to the flash entry phases and
after serving/clearing will drop the Volt Monitor/Fault Monitor and enter flash. The USB
flash drive can now be removed and the database is unlocked and the objects within the
CRC block will be able to be edited using the ATC Preemption Parameter screens.
(MM.2.6.1)
After the Preempt programming is complete and saved to the database, a utility will
display the new calculated CRC. An additional message will be displayed that indicates
if the calculated CRC and the cabinet CRC match. The CRC will then be configured on
the cabinet CRC card. Once the card is configured to match the calculated CRC, a utility
will lock the database. After the Database Lock operation, a restart of the ATC will be
required. I/O mapping will be used to configure which of the field I/O bits from the ‘D’
Module form the 16 bit hard wired address.
After restart, the ATC will begin a process of validating the data within the critical block
and comparing it against the hardwired CRC on the cabinet address card once per
second. If a difference or error is detected (can’t read the CRC card), then the ATC will
enter an all Red Flash state and set the CRC Failure Alarm.
In addition to the creation of the CRC block and subsequent once per second testing,
the activation of the NTCIP formatted iccPreemptionOperationControl object will cause
the ATC to invert the logical state of the Remote Flash input. The intent is that if a NonICC compliant Controller was installed into an ICC wired cabinet, the Remote Flash
265
input would be active, even with the cabinet flash switch in the OFF position, and cause
the Non-ICC compliant Controller to remain in flash.
The following features previous described on Preemption Parameter screens
(MM.2.6.1), are features required by the ICC specification. ICC activation is not
required to use the below listed ICC features.
FDW THRU YELLOW = Yellow Clearance during Preemption (MM.2.6.2) —
According to the ICC specification, during Railroad Preemption, the FDW time on a
phase will be limited to the value of the Yellow clearance and will time this FDW period
concurrently with the Yellow Clearance. This will be accomplished withan ATC option in
the preemptControl object called FDW THRU YELLOW in each Preemption Run.
TRACK GREEN RESERVICE IF NEW CALL = Immediate Track Green Reservice
(MM.2.6.3) — According to the ICC specification, during Railroad Preemption, this
option will allow the ATC to return to the Track Clearance Green without having to
complete the Preemption run and exit. If the preemption input is dropped and re-applied
during the Run, then the ATC will respect all the phase clearance intervals (including
Red-Revert) and bring the Track Green on ASAP. This will be accomplished with an
ATC option in the preemptControl object called TRACK GREEN RESERVICE IF NEW
CALL in each Preempt Run.
Controller Data Security (16-bit cabinet CRC) — This process works by enabling the
iccPreemptionControl object. When activated, the ATC places a group of objects into a
special block and continuously runs a CRC check on the block. The calculated CRC of
the block is then compared to an external hard wired CRC via the controller’s ‘D’
Module. Additional safety features prevent the objects from being modified using the
ATC’s keypad or NTCIP download.
INPUT MIRROR = Inverted Remote Flash Input (MM.2.6.1) — The ICC Preemption
specification requires that the ATC’s Remote Flash input be inverted from normal
operation. This is to prevent the use of a Non-ICC compliant Controller in a cabinet
wired for ICC Preemption. This will be accomplished with an ATC option in the
preemptControl object called ICC ENABLE.
Controller Preempt Input Verification — According to the ICC specification, during
Railroad Preemption, a secondary preemption input is used to validate the primary
Railroad Preemption input. This Input must be in the opposite state of the primary
Railroad Preemption input signal. The ATC will use a spare input on the ‘D’ module that
is named Preempt #x input mirror. This will be accomplished with an ATC option in the
preemptControl object called INPUT MIRROR in each Preempt Run.
DWELL EXTEND TIME = Preemption input Dwell extension (MM.2.6.4) — The ICC
Preemption specification requires that a new parameter to be added to the Preempt
database that provides for an extension of the Preempt input during the dwell interval.
The resolution of the extension is in seconds (0-255). This will be accomplished with an
ATC option in the preemptControl object called DWELL EXTEND TIME in each Preempt
Run.
266
Chapter 9 — Overlaps
This section explains phase-based Overlaps, or conditiional phases that can run at the same time as
other phases. The following topics are discussed in detail in this chapter:
•
A discussion of the basic theory of overlap operation, on page 268.
•
Programming vehicular overlaps, starting on page 276.
•
Programming pedestrian overlaps, starting on page 280.
267
OVERVIEW
An Overlap is a set of Green-Yellow-Red outputs that are associated with one or more other
phases. An overlap forms a separate movement that derives its operation from these
assigned phases, commonly called “parent phases” or “included phases.”
A typical overlap will be active during two or more parent phases. When any parent is green,
the overlap is green as well. If the controller makes a “phase next” decision to clear from one
parent phase to another, the overlap will remain green throughout. If the controller decides to
clear from a parent to a non-parent, the overlap will clear with the parent using the parent’s
yellow and red duration.
The above describes a basic overlap. There are several variants to this basic operation which
modify the timing described above, as determined by the overlap’s parameter settings and
the ‘type’ of overlap that has been selected.. And there are overlaps available for both
vehicles and pedestrians, each having their own set of ‘types’ and intriciacies.
The figure below illustrates a basic vehicular overlap in a simple, standard 8-phase 2-ring
sequence. Phases are usually numbered, but overlaps are almost always given letter
designators (A through F). However in the ATC controller environment the 32 available
vehicular overlaps and the 16 available pedestrian overlaps are simply numbered.
Parent phases for OL1:
Phases 6 and 7
Overlap 1
Figure 225 – Simple Overlap example
Overlaps are only applicable to phase based patterns (patterns 1 through 48, and phasebased ‘Free’ pattern 254.) Overlaps are programmed using the Overlaps menu, located under
the Programming > Controller menu, and described on the next page. The status of overlaps
are indicated on the Vehicular and Pedestrian Overlaps status screens, described on page
66.
268
Overview
Overlaps Menu
The Overlaps menu is used to access the two overlap setup screens, one for vehicle overlap
phases and the other for pedestrian overlap phases. It is available from the main interface
used to program phase-based operations, the Controller menu under Programming.
( M AIN M ENU > 2.P ROGRAMMING > 2.C ONTROLLER > 0.O VERLAPS )
2.2.0
OVERLAPS MENU
1. VEHICLE OVERLAPS
2. PEDESTRIAN OVERLAPS
Figure 226 – Overlaps Menu
Overlaps are ‘vehicular’ or ‘pedestrian’ based on the type of traffic that will be moving during
that overlap. The Parent and Modifier phases of vehicular overlaps are vehicular phases.The
Parent and Modifier phases of pedestrian overlaps are pedestrian phases.
Overlaps are programmed by going into the overlap screen for either vehicles or pedestrians
by chosing either
or
on the above menu, and then using the
and
buttons
to navigate to the overlap number you wish to program. Keep in mind that the number of the
overlap does not indicate priority. Any overlap that is programmed to have at least one parent
phase will be served, (or at least one ‘Included’ phase, in the case of pedestrian overlaps) as
long as the parent phase is currently Enabled and is served at some point during the currently
selected Pattern.
269
Overlap Types and Modifiers
There are a variety of programming parameters provided for ATC overlaps which modify the
basic operation of how an overlap functions. For vehicular overlaps, you have parent and
modifier phases. The parent phases are the ones that you want the overlap to mirror (with
some variation, based on the type of overlap mode chosen, see below.) The modifier phase is
a different kind of overlap-to-phase relationship, based on the overlap type chosen. And a
modifier phase has a different function based on whether it is also a parent phase or not. For
example, a parent phase that is also a modifier phase could tell the overlap to flash green.
But if the modifier phase is NOT a parent phase, it could tell the overlap to follow this phase
into red, even if the parent phases are still green. And these modifier behaviors are different
for each overlap mode.
In addition to parent phases and modifiers, overlaps have extra complexities provided by
special Lead/Delay modes that can be programmed, other per-phase optional flags that can
be thrown, such as Flashing Green, Flashing Red, or Conflicting Phase, and timing options
such as Minimum Green, Trailing Yellow, Trailing Red, Trailing Green, and Lead/Delay.
And pedestrian overlaps have their own versions of these complexities. For example, when
programming a pedestrian phase, parent phases = “included phases”, modifier phases =
“modifiers”, and overlap modes = “types”.
So it is clear why some people become confused about why a particular overlap performs the
way that it does at any given point in a cycle. In this chapter, we will attempt to provide a clear
description of what should occur during any programmed overlap, based on the selected
parent and modifier phases, as well as the programmed signal timers and any flags that have
been selected, for each of the available overlap “types”.
Types of Vehicular Overlaps
Just as an introduction, these are the vehicular overlap modes that are available in the ATC
controller firmware. The number in parentheses is the actual stored value, showing the ATCstandard numerical value for each overlap type.
In GreenWave v3.8, there are six types of vehicular overlap types. The type is chosen by
modifying the TYPE parameter on screen 2.2.0.1.x (‘Vehicle Overlap Configuration’):
ntcip/other (1): Also known as a Standard or Normal overlap. A Standard/Normal Type
occurs when Parent Phases exist and no Modifier Phases exist. The Overlap turns
green when a Parent Phase turns green. The Overlap terminates if a Parent Phase is
not green and, a Parent Phase terminates and the traffic engine is not advancing to a
Parent Phase. (Refer to Figure 227.)
Ph2 Green
Overlap Green
Ph2 Yellow
Red Clear
Ph3 Green
Ph3Yellow
Ph3Red Clear
Yellow
Red Clear
Ph4 Green
Figure 227 – Vehicular Overlap, type ntcip (1) with Parent Phases = phase 2 and
phase 3
If the ntcip (1) type has both parent and modifier phases defined, this is known as a
‘Minus Green Yellow’ overlap. This type of Overlap turns green when a Parent Phase
270
Overview
either turns green and no green Modifier Phases exist, or when a Parent Phase turns
yellow and the engine is advancing to a Parent Phase and no Modifier Phase is
currently green. This kind of overlap terminates if a Parent Phase terminates and a
Parent Phase is not green and the traffic engine is not advancing to another Parent
Phase. This type overlap terminates green-to-red if a Modifier Phase turns green. (Refer
to Figure 228.)
Ph2 Green
Ph2 Yellow
Overlap Red
Overlap Green
Ph2 Red
Ph3 Green
Ph3 Yellow
Ph3 Red
Ph 4 Green
Overlap Yellow
Overlap Red
Figure 228 – Type ntcip (1), Minus Green-Yellow version: Parent Phases = 2+3 and
Modifier Phase = 2
Note
Whether or not it has Modifier phases, a Type ntcip (1) overlap will not use any of
the non-NTCIP features available to the other overlap types: Flash Green Phases,
Flash Red Phases, Conflicting Phases, Lead/Delay Phases, Lead/Delay Mode,
Lead/Delay Time, Min Green, Flash Rate, and Use Conflicting Phases.
ntcip plus (2): Operates exactly the same as an nctip (1) type overlap, except that it
will respond to the additional proprietary parameters. So an ntcip plus (2) vehicular
overlap will use the settings stored in the following parameters: Flash Green Phases,
Flash Red Phases, Conflicting Phases, Lead/Delay Phases, Lead/Delay Mode,
Lead/Delay Time, Min Green, Flash Rate, and Use Conflicting Phases.
minus walk ped clear (3): This type of overlap operates the same as a
normal/standard overlap except the overlap is red during a Modifier Parent Phase
Green/Walk and Green/Ped Clearance. The Overlap turns green after the Modifier Phase
Green/Ped Clearance if the Modifier Parent Phase runs Green/Dont Walk or advancing
to a Parent Phase and not advancing to a Conflicting Phase.For this type of overlap, it’s
important to set a Min Green time in order to prevent a ‘short’ overlap green prior to the
ped recycle, or prior to the Parent Phase going Yellow.
Ph2 Green
Ph2
Walk
Ph2
Yellow
Ph2 Ped
Clear
Overlap Red
Ph2 Red
Ph3 Green
Ph3 Yellow
Ph3 Red
Ph4 Green
Overlap Yellow
Overlap Red
Ph2 Don’t Walk
Overlap Green
Figure 229 – Minus Walk Ped Clear Type, Parent Phases = 2 & 3, Modifier Phase = 2
271
minus walk red (4): This type of vehicular overlap is the same as “minus walk ped clear
(3)” except that the overlap stays Red during a parent Modifier phase’s Walk. This type
of overlap turns Green when its parent Modifier phase pedestrian output enters ped
clearance.
Ph2 Green
Ph2 Yellow
Ph2 Walk
Ph2 Ped Clear
Overlap Red
Overlap Green
Ph2 Red
Ph3 Green
Ph3 Yellow
Ph3 Red
O’lap Yellow
Overlap Red
Ph4 Green
Ph2 Don’t Walk
Figure 230 – Minus Walk Red type overlap with Parent Phase = 2 & 3 and
Modifier Phase = 2
minus walk dark (5): This type of overlap is the same as “minus walk red (4)”, except
this overlap keeps all of its outputs OFF during its parent Modifier phase’s Walk.
Ph2 Green
Ph2 Yellow
Ph2 Walk
Ph2 Ped Clear
Overlap Dark
Overlap Green
Ph2 Red
Ph3 Green
Ph3 Yellow
Ph3 Red
Ph4 Green
Ph2 Don’t Walk
O’lap Yellow
Overlap Red
Figure 231 – Minus Walk Dark type overlap with Parent Phases = 2 & 3 and
Modifier Phase = 2
protected permissive (6): (Also known as the MUTCD Flashing Yellow Left Turn Arrow
overlap) This overlap type is the same as the ntcip (1) type, except the Overlap stays
dark during a parent Modifier phase’s Green output. It clears in sync with a parent
Modifier phase. And it turns Green when all of its Modifier non-parent phases turn
green. (Refer to Figure 232.)
Ph1 Green
Yellow
Red Clear
Ph2 Green
Yellow
Red Clear
Green Flash
Ph6 Green
Overlap Dark
Yellow
Red Clear
Ph3 G
Yellow
Red Clear
Ph7 G
Yellow
Red Clear
Red Rest
Figure 232 – Vehicular Overlap, type Protected/Permissive (6) with
Parent Phases = 1+2, Modifier Phase = 1, Green Flash = 1+2
In the above example, Overlap Green Flash drives the Flashing Yellow Arrow, Phase 1
Green drives the Green Arrow, Overlap Yellow drives the Solid Yellow Arrow, and
Overlap Red drives the Red Arrow of a four section left turn head. Phase 1 Yellow and
Phase 1 Red outputs are unused.
272
Overview
Types of Pedestrian Overlaps
There are three types of pedestrian overlaps available. The main difference between them is
in how they deal with a series of parent phases in a row. Specifically, Ped Overlap types
normal(2) and alwaysClear(3) ignore Modifier Phases.
normal (2): With a single parent ped phase, the overlap displays Walk for the number
of seconds defined in the Ped Overlap WALK TIME field. It then times Ped Clearance
for the number of seconds defined in the Ped Overlap CLEAR TIME field. If WALK
TIME and CLEAR TIME are set to 0.0, the overlap times in sync with the parent ped
phase. In the case of multiple ped parent phases, the overlap rests in Walk when the
controller goes from one parent ped phase to another contiguous parent ped phase.
(Refer to ‘Walk Transfer’ in Figure 233.) So, if the overlap has two parent ped phases,
the overlap will remain in Walk during the time that the first parent phase goes into
flashing don’t walk. It will stay in Walk right through to the end of the second parent
phase’s Walk period. This continuous Walk will remain on as long as there is another
parent ped phase still to occur (in the general case where there may be more than two
ped parents.)
Figure 233 – Normal pedestrian overlap with two parent phases (phases 1 and 2)
always clear (3): With a single parent pedestrian phase, the ‘always clear’ ped overlap
functions exactly as the ‘normal’ type does. But in the case of multiple parent ped
phases it acts differently. In that case, the ‘always clear’ pedestrian overlap type goes
into ped clearance (flashing Don’t Walk) only when all parent pedestrian phases have
gone into clearance and when no parent ped phases are still in Walk.
Figure 234 – Always Clear pedestrian overlap with two parent phases (phases 1 and 2)
273
carryover (4): Again, with a single parent pedestrian phase, the ‘carryover’ ped overlap
functions exactly as the ‘normal’ type does. But if there are multiple parent phases, and
one of them is marked as a ‘Modifier’ phase, then the ped overlap will time its Walk and
Ped Clearance either using the Walk Time and Clear Time values stored on the Ped
Overlap Config screen (2.2.0.2.x), or it will time along with the first parent. The big
change from the other types, however, is that the carryover ped overlap then times its
ped clearance signal out over the ped clearance and Don’t Walk portion of the modifier
parent phase, timing out its ped clearance timer and going to Don’t Walk indpendently
of the parent phases. If the Clear Time value is not high enough to take it into the next
parent phase’s time, Carryover will hold the overlap in Walk until the last parent phase
reaches Ped Clearance, at which point it will clear.
Figure 235 – Carryover (4) pedestrian overlap example
The above example shows a Carryover(4) ped overlap with 2 parent phases (ph. 1 and
2) and 1 modifer phase (ph. 1), and the Ped Overlap Ped Clearance time is larger than
Phase 2 Walk plus Ped Clearance time.
274
Overview
Overlaps and Compatibility
Overlap operation is sometimes a source of confusion when it comes to overlap compatibility.
An overlap channel’s compatibility is definitely not equal to the sum of its parent phases’
compatibilitiies, as is sometimes thought. It is important to be able to make the distinction
between the overlap and its compatibilities vs. its parents and their compatibilities. The
overlap is a separate movement and its parents are not necessarily compatible with each
other (and are usually not). The overlap is monitored separately, with its own compatibility
programming. An example of this can be seen in our earlier overlap example:
Parent phases for OL1:
Phases 6 and 7
Figure 236 – Overlap compatiblity
Clearly, in Figure 236, phases 6 and 7 are not compatible phases, so the monitoring of the
overlap cannot simply be the monitoring of phases 6 AND 7. It must be monitored on its own
channel, with its own programming. (OL1 is compatible with Ph6 OR Ph7.)
275
VEHICLE OVERLAPS
The Vehicle Overlaps screens are used to configure the 32 available overlaps for use in
phase-based patterns. As described previously, an overlap is a secondary phase that is
separate from the normal 16 available phases of the intersection cycle, and it is served
conditionally, meaning that its state is linked to one or more of the main 16 phases. Overlaps
are identified by their number. (‘OVL1’ through ‘OVL32’.)
M AI N M EN U > 2.P ROGR AM M ING > 2.C ONTR OLL ER > 0.O VERL APS > 1.V EHI CLE O VE RL APS
2.2.0.1.1
VEH OVL 1 CONFIG PG 1of32
1 1 1 1 1 1 1
PHASES 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
PARENTS
MODIFIER
FLSH GRN
FLSH RED
CONF PHS
LEAD/DEL
TYPE ........ ntcip (1)
LEAD/DEL MODE none (2)
TRAIL GREEN .
0
MIN GREEN ..
0
TRAIL YELLOW. 3.0 FLASH RATE.. 60 (2)
TRAIL RED ... 0.0 USE CONF PHS NO
LEAD/DEL .... 0.0
Figure 237 – Vehicle Overlaps screen
Use the
and
keys on the keypad to navigate between the 32 vehicle overlap
definition screens. Each screen defines one overlap, as indicated in the title row.
Parents – A parent phase triggers an overlap. It is a phase that functions as part of the
normal sequence of the intersection (or as an actuated phase during the normal sequence)
and serves as the trigger to tell the controller that an overlap should be served. For standard
overlaps, only the parent phases need to be programmed. Per the NTCIP 1202 standard,
section 2.10.2.3, the overlap will be green whenever a parent phase’s output is green, and
whenever the controller is changing between parent phases. That standard operation can be
modified extensively using the rest of the parameters on this screen.
Modifier — Like ‘Parents’, this is a per-phase selection row. If a phase is marked as a
‘Modifier’ phase (with an ‘X’), then it will impact the operation of this overlap. The precise way
that the modifier changes the operation of the overlap is determined by the type of overlap.
Refer to “Overlap Types and Modifiers” on page 270 for details. A modifier phase does not
need to be a parent phase.
FLSH Green — This option can only be set for phases that are also marked as Parent
phases. When set, during the green of the parent phase, the overlap will flash green. If the
parent is clearing to another phase that is also marked with this FLSH GREEN flag, then the
overlap will continue to flash green. Also, if the Trail Green time is non-zero for this overlap,
the green will continue to flash during the trailing period. This option uses the FLASH RATE
value as the frequency with which to flash the overlap signal head. This parameter is ignored
if the overlap type is set to ‘ntcip (1)’.
FLSH Red — This option can be set for any phases, whether they are Parent phases or not.
When set for a non-parent phase, the overlap will flash red during the phase’s green. If set for
276
Vehicle Overlaps
a parent phase, the overlap flashes red during the Red timed-out portion of the parent phase.
This option uses the FLASH RATE value as the frequency with which to flash the overlap
signal head. This parameter is ignored if the overlap type is set to ‘ntcip (1)’.
CONF Phs — These can be used to define which phases conflict with this overlap. These
values are only used if the USE CONF PHS flag is set to YES. If that value is set to NO, then
the overlap’s conflicting phases are automatically set to its parent phases’ conflicting phases.
This parameter is ignored if the overlap type is set to ‘ntcip (1)’.
LEAD/DEL — Used to indicate which phases will use the Lead/Del logic and timer. These are
basically ways that an overlap can be configured to lead (occur before) or be delayed (occur
after) a parent phase. Refer to “Leading or Delayed Vehicular Overlaps” on page 278. This
parameter is ignored if the overlap type is set to ‘ntcip (1)’.
Type – The type of overlap determines the logic that will be used by the overlap. The types of
vehicular overlaps are described in “Overlap Types and Modifiers” on page 270. The ‘types’
are used to provide different ways for an overlap to respond to parent and modifier phases.
LEAD/DEL Mode — This setting determines which lead or delay logic will be used for all of
the phases that are marked as LEAD/DEL in the array on the screen above. The available
Lead/Del modes include: none (2) which cause no change in the overlap behavior, delay (3)
which causes the overlap to be delayed relative to the parent phase, lead (4) which cause the
overlap to start before the parent phase (at the start of the previous vehicular phase’s red rest
period), and early lead (5) which causes the overlap to start even earlier prior to the parent
phase (at the start of the previous phase's yellow clearance.) This parameter is ignored if the
overlap type is set to ‘ntcip (1)’.
Trailing values (TRAIL GREEN, TRAIL YELLOW, TRAIL RED) – These numbers represent
the time, in seconds, that the overlap signals are delayed (i.e. a double-clearing overlap)
relative to the parent phase. A zero Trail Green Time turns the overlap yellow with the Parent
Phase. A non-zero Trail Green time extends the overlap green when the Parent Phase turns
yellow. Following Trail Green, the Overlap runs the Trail Yellow Time, the Trail Red Time and
the next conflicting phases turn on. The terminating phase finishes Yellow and Red Clearance
and compatible next phases turn on while the Overlap finishes Trail timing. Trail Yellow and
Trail Red Range is 0-25.5 seconds and Trail Green Range is 0-255 seconds.
LEAD/DEL — This timer value is the number of seconds, in the range 0.0 to 25.5 seconds,
that the overlap will lead or be delayed relative to the parent phase. This value determines
how much Red Rest time will be added to the previous parent phase in order to accomodate
a leading or early leading overlap, or how much green time will be added to the parent phase
to accomodate a delay. This parameter is ignored if the overlap type is set to ‘ntcip (1)’.
MIN Green — The number of seconds, from 0 to 255, that represents the minimum amount of
time a green signal should be shown during the overlap. If non-zero, the Min Green timing
postpones a parent phase going yellow if not advancing to another parent phase. This
parameter is ignored if the overlap type is set to ‘ntcip (1)’.
Flash Rate — The rate at which the overlap signal will flash, if the FLASH GREEN, FLASH
YELLOW, or FLASH RED options are used. The available rates are: 60, 100, 150, or 300
flashes per minute. (i.e. rates of 1, 1.6, 2.5, or 5 Hz.) The internal values to set these are 2, 3,
4 or 5. This parameter is ignored if the overlap type is set to ‘ntcip (1)’.
Use CONF Phs — Tells whether the overlap should use user-defined conflicting phase
assignments or auto-calculated conflicting phases from parent phases. If set to YES, then the
phases defined as conflicting phases on the screen above (in the CONF PHS array) will be
used for testing. If this is set to NO, then the overlap’s parent phases’ conflicting phases will
be used instead. This parameter is ignored if the overlap type is set to ‘ntcip (1)’.
277
Leading or Delayed Vehicular Overlaps
On the Vehicle Overlaps screens, the Lead/Del per-phase switches, the Lead/Del Mode
selector and the Lead/Del timer value are all used to program the Leading/Delayed Overlaps
function.
2.2.0.1.1
VEH OVL 1 CONFIG PG 1of32
1 1 1 1 1 1 1
PHASES 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
PARENTS X
X
MODIFIER
X
FLSH GRN
FLSH RED
CONF PHS
LEAD/DEL X
X
per-phase switches
TYPE ........ ntcip (1)
LEAD/DEL MODE lead (4)
TRAIL GREEN .
0
MIN GREEN ..
0
TRAIL YELLOW. 3.0 FLASH RATE.. 60 (2)
TRAIL RED ... 0.0 USE CONF PHS NO
LEAD/DEL .... 0.0
mode selector
timer setting
Figure 238 – Lead/Delay parameters on the Vehicle Overlaps screen
Overlaps now have the option to either lead or be delayed relative to the parent phase. Uses
the LEAD/DEL switch, the LEAD/DEL MODE, and the LEAD/DEL timer value on screen
2.2.0.1.x (‘Vehicle Overlap Configuration’). Leading can either be a standard Lead or an Early
Lead. A ‘leading’ overlap adds a red rest period before the parent phase to accomodate this
lead timing. An ‘early leading’ overlap starts even earlier, at the start of the previous phase’s
yellow. (Early Leading overlap was known as ‘Advance Green Leading Overlap’ in the 3000E
controller.) Again, Leading and Delay capabilities go beyond the NTCIP standard and do not
function in the ‘ntcip (1)’ overlap type. (Refer to Figure 239.)
Delayed Overlap
Red Rest
Phase 2 Green
Ph 2 Yellow
Ph 3 Red
Overlap A Red
(Ph 2 is parent)
OL A Delay
Timer
Overlap A
Yellow
Overlap A Red
Overlap A Green
Red Rest
Figure 239 – Leading, Early Leading, and Delayed Overlaps
278
Vehicle Overlaps
Creating an Overlap
This is just to clarify how overlaps are actually activated and used. All that is needed to set up
a vehicular overlap is:
1.
Be sure that the controller is running a phase-based pattern. If an interval-based
pattern is running, overlaps are not used.
2.
Select an overlap number to implement by going to the Overlaps screen (MM >
2.Programming > 2.Controller > 0.Overlaps > 1.Vehicle Overlaps) and using the
and
keys to navigate between the 32 that are available.
3.
Go into Edit mode. (
4.
Once in the desired overlap screen, all that is required is that one or more parent
phases be defined. For the overlap to be called, these selected parent phases must be
served at some time during the operation of the controller.
5.
All of the rest of the parameters on the Vehicle Overlaps screen are merely there to
provide ways to ‘tweak’ the operation of the overlap. If you are happy with a standard
overlap that follows the parent phases, just make sure that TYPE is set to ntcip(1) and
you are done.
6.
Press
7.
Go to the Overlaps Status screen to verify that the overlap runs as expected. (MM >
1.Status > 1.Controller Menu > 7. Overlaps > 1.Vehicle)
,
,
)
again to exit from Edit mode, which saves the new overlap.
Warning
The user must verify that Lead/Delay and Minimum Green
timing does not disrupt Split timing and cause a Cycle Fault.
The Coordinator does not perform Consistency Checks on
these parameters.
279
PEDESTRIAN OVERLAPS
This screen allows for the configuration of up to 16 pedestrian overlap phases. Ped overlaps
are pedestrian phases that are separate from the normal 16 pedestrian phases that run in
association with the 16 vehicular phases. They are conditional, meaning that their states are
linked to one or more of the main 16 vehicular phases. Overlaps are labeled by number (PED
OVL 1 to PED OVL 16).
( > 2.P ROGRAMMING > 2.C ONTROLLER > 0.O VERLAPS > 2.P EDESTRIAN O VERLAPS )
2.2.0.2.1
PED OVL CONFIG PG 1of16
OVERLAP 1
---------------------------------------1 1 1 1 1 1 1
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
INCLUDED X X
MODIFIER X
TYPE ........normal (2)
WALK TIME ... 5
CLEAR TIME .. 8
Figure 240 – Pedestrian Overlap Screen
Use the
screens.
and
keys to navigate to the other seven pedestrian overlap parameter
Included –
Vehicle phase or phases with which the Ped/Ped Clear overlap will be
displayed. (The parent phase)
Modifier –
An array of per-phase selections will indicate which vehicular phases are
‘Modifier’ phass. For the normal(2) type of ped overlap, a modifier is an included
phase during which the pedestrian overlap output will transition from Don’t Walk
to Walk. The other ped overlap types use the modifier phase differently (Refer
to “Pedestrian Overlap Types” on page 281.)
Type –
The ‘type’ of ped overlap is used to select how the overlap will respond to a
series of Included phases that occur in a row. See the “Pedestrian Overlap
Types” topic on page 281 for more details.
Walk Time – This parameter is used to tell pedestrian overlaps how long to hold their Walk
signal on, depending on the logic of the ped overlap type. If this value is set to
0.0, the overlap times with the included phase(s). Valid times go from 0 to 255
seconds.
Clear Time – Used to tell pedestrian overlaps how long to hold their flashing Don’t Walk
signal, again, depending on the logic of the ped overlap type being used. If this
value is set to 0.0, the overlap times with the Included phases’ timers. Valid
times go from 0 to 255 seconds.
280
Pedestrian Overlaps
Pedestrian Overlap Types
There are currently three types of pedestrian overlaps available. The main difference between
them is in how they deal with a series of parent phases in a row. The value is selected by
choosing a valid number value for the TYPE parameter on the Ped Overlaps screens. The
number in parenthesis indicates the number to press to select that type (or you can use the
key to step through the available values.
Note
In the case of Pedestrian overlaps within the GREENWave firmware, the
overlap parent phases are known as ‘Included’ phases.
normal (2): With a single Included ped phase, the overlap displays Walk for the number
of seconds defined in the Ped Overlap WALK TIME field. It then times Ped Clearance
for the number of seconds defined in the Ped Overlap CLEAR TIME field. If WALK
TIME and CLEAR TIME are set to 0.0, the overlap times in sync with the Included ped
phase. In the case of multiple ped Included phases, the overlap rests in Walk when the
controller goes from one Included ped phase to another contiguous Included ped phase.
So, if the overlap has two Included ped phases, the overlap will remain in Walk during
the time that the first Included phase goes into Flashing Don’t Walk. It will stay in Walk
right through to the end of the second Included phase’s Walk period. This continuous
Walk will remain on as long as there is another Included ped phase still to occur (in the
general case where there may be more than two ped Included phases.)
Included
Ph1
Green/Walk
Ped Clear
Overlap
Ped OL Walk
Walk Transfer
Yellow
Red
Ph2
Green/Walk
Ped Clear
Yellow
Walk
Ped Clear
Don’t Walk
Red
Ph3
Green/Walk
Figure 241 – Normal pedestrian overlap with two parent phases (phases 1 and 2)
always clear (3): With a single Included pedestrian phase, the ‘always clear’ ped
overlap functions exactly as the ‘normal’ type does. But in the case of multiple Included
ped phases, it acts differently. In that case, the ‘always clear’ pedestrian overlap type
goes into ped clearance (Flashing Don’t Walk) only when all Included pedestrian
phases have gone into clearance and when no Included ped phases are still in Walk.
Included
1 Green/Walk
Ped Clear
Yellow
Overlap
Ped OL Walk
Ped Clear
Don’t Walk
Red
2 Green/Walk
Ped Clear
Yellow
Walk
Ped Clear
Don’t Walk
Red
3 Green/Walk
Figure 242 – Always Clear pedestrian overlap with two parent phases (phases 1 and 2)
carryover (4): Again, with a single parent pedestrian phase, the ‘carryover’ ped overlap
functions exactly as the ‘normal’ type does. But if there are multiple parent phases, and
one of them is marked as a ‘Modifier’ phase, then the ped overlap will time its Walk and
Ped Clearance either using the Walk Time and Clear Time values stored on the Ped
Overlap Config screen (2.2.0.2.x), or it will time along with the first parent. The big
change from the other types, however, is that the carryover ped overlap then times its
ped clearance signal out over the ped clearance and Don’t Walk portion of the modifier
281
parent phase, timing out its ped clearance timer and going to Don’t Walk indpendently
of the parent phases. If the Clear Time value is not high enough to take it into the next
Included phase’s time, Carryover will hold the overlap in Walk until the last Included
phase reaches Ped Clearance, at which point it will clear.
Included
Overlap
Ph1 Green/Walk
Ped Clear
Ped OL Walk
Ped Clear
Yellow
Red
Ph2 Green/Walk
Ped Clear
Yellow
Red
Ph3 Green/Walk
Don’t Walk
Figure 243 – Carryover pedestrian overlap with 2 parent phases (ph. 1 and 2)
and 1 modifer (ph. 1)
282
Pedestrian Overlaps
Creating a Ped Overlap
Follow these steps to create a Pedestrian Overlap phase:
1.
Be sure that the controller is running a phase-based pattern. If an interval-based
pattern is running, overlaps (both vehicular and pedestrian) are not used.
2.
Select a ped overlap number to implement by going to the Overlaps menu (MM >
2.Programming > 2.Controller > 0.Overlaps), opening the Pedestrian Overlaps
screens, and using the
available.
and
3.
Go into Edit mode. (
4.
Once in the desired ped overlap screen, all that is required is that one or more
Included phase be defined. For the ped overlap to be called, these selected Included
Phase Peds must be served at some time during the operation of the controller.
5.
All of the rest of the parameters on the Ped Overlaps screens are merely there to
provide ways to ‘tweak’ the operation of the overlap. If you are happy with a standard
ped overlap that follows the parent phases, just make sure that TYPE is set to normal
(2) and you are done.
6.
Press
again to exit from Edit mode, which saves the new
pedestrian overlap phase.
7.
Go to the Overlaps Status screen to verify that the ped overlap runs as expected. (MM
> 1.Status > 1.Controller Menu > 7. Overlaps > 2.Pedestrian)
Warning
-
keys to navigate between the 16 that are
)
The user must verify that a Ped Overlap does not disrupt Split
timing and cause a Cycle Fault. The Coordinator does not
perform Consistency Checks on these parameters.
283
284
Chapter 10 — Transit Signal Priority
This chapter describes how to set up transit signal priority in an ATC controller. The following
•
An introduction to what TSP is, on page 286
•
A discussion of how TSP is implemented in the ATC, on page 287
•
A quick description of how to set up TSP, on page 290
•
A detailed description of the ATC TSP screens and parameters, starting on page 292
285
WHAT IS TSP?
TSP stands for ‘Transit Signal Priority’. In a way, TSP is similar to preemption, but
instead of being triggered by emergency vehicles such as ambulances, police cars and
fire trucks, it is triggered by public transportation vehicles, usually buses. And rather than
triggering a hard ‘preemption’ of the normal intersection pattern, a TSP call provides a
more subtle adjustment of traffic flow. It creates a ‘priority’ change in the intersection
operation, meaning the transit vehicle is given preference by the traffic controller when it
comes to timing and signal changes.
Figure 244 – TSP Timing Adjustment in an Intersection
For example, if the light is green in the direction the transit vehicle is currently travelling,
the controller will hold the green long enough for the bus to get through the light. If the
light is red in the direction of travel, the controller will shorten the cross street’s greens to
bring up the green light for the transit vehicle more quickly. These are the basics of how
TSP functions; however, there are complexities to how this is implemented and how it
functions on real city streets. These are discussed in greater detail in the rest of this
chapter.
TSP calls can be handled from either a phase-based or an interval-based pattern.
286
How TSP Functions
HOW TSP FUNCTIONS
Although TSP has been defined in general terms by the U.S. Department of
Transportation, there is not a true ‘standard’ way that it is to be implemented. Each city
and equipment manufacturer has been required to decide how to implement the
capability. In the Peek ATC controllers, TSP has been implemented using the
parameters stored in the TSP menu, shown in Figure 245.
( > 2.Programming > 8.Transit Signal Priority)
2.8
TRANSIT PRIORITY MENU
1. UNIT PARAMETERS
2. RUN PARAMETERS
3. ACTIONS PLANS
5. QUEUE JUMPING
6. SPLIT TABLE
Figure 245 – Transit Priority Menu
It is important to take a moment to understand the way that Transit Signal Priority is
applied to intersection operation in the Peek ATC controllers, as it can be a bit confusing
to those unfamiliar with the process. As shown in Figure 246, the operator can select
one of 48 ‘TSP Action Plans’ which are composed of a Run Config number and a couple
other parameters. This Run Config calls one of eight TSP Run Configurations. Each
Run Configuration includes 8 individual TSP ‘Runs’ that can be called at any time when
that Run Configuration is active. A TSP Run is somewhat equivalent to a Preemption
Run, meaning it is a sequence of events that occur when a TSP call is detected. There
are eight Runs in each Run Configuration, to allow TSP on 8 user-selectable traffic
approaches/phases. This also corresponds to the eight TSP inputs available on the ATC
controllers.
Although there are only 8 sets of Runs that can be chosen by your TSP Action Plans,
each Action Plan can also enable/disable individual runs, and also change the re-service
time and recover strategy to be used by all of the runs in the current active plan. This
provides some additional options beyond the eight basic Run Configurations.
287
Figure 246 – TSP Action Plans, Run Configs and Runs
So, as you can see from the above illustration, there are 48 available TSP Action plans
in the ATC controller. Each Action plan can call one and only one of the eight available
Run Configurations, however each Action plan can enable or disable individual runs
within the selected Run Configuration. Which TSP Action Plan the controller uses at any
given time is normally defined by the TOD schedule, however there are also default
action plans that can be defined for whenever the controller is under central system
control. TSP operation is not supported when the controller is running in Free mode.
Each Run Configuration is a set of 8 individual runs that are all available at the same
time in the intersection. The fact that multiple ‘runs’ are available allows you to set up a
different signal behavior based on which TSP input is detected, meaning if you detect a
288
How TSP Functions
bus coming southbound, you might call Run 1, but if you detect a bus coming
eastbound, you can call Run 2 instead.
Each run is a set of time changes and methods that grant the transit vehicle a higher
priority to green lights within the intersection. The time changes are set in the TSP Split
table (option 6 on the Transit Priority menu). The methods to be used are specified by
the user in each Run Configuration.
Prioritization Methods
The Peek ATC controllers actually provide the higher priority for the transit vehicle in a
number of ways. Four are described in the US DOT TSP Handbook, and Peek supplies
an additional method not described there. Any or all of these methods may be used in
conjunction with one another:
Green Extension — This is the primary method used by most TSP systems.
Green extension simply extends the amount of time available to the transit
vehicle’s green light. The ATC controllers provide a number of options on how to
deal with the associated pedestrian phases or intervals.
Early Green — The most common secondary method used in most TSP systems
is to shorten the green times on the other phases in the intersection. So if the
North/Southbound lanes are currently being serviced in green, and a bus
approaches in the Eastbound direction, the Early Green method would reduce the
amount of time the green is displayed to North and Southbound traffic; bringing the
green to the bus more quickly. This method is known as ‘Reduction’ in the ATC
interface.
Phase Insertion — This method is used when there is a dedicated signalized
transit lane or turn lane that is only activated when a transit vehicle is present. This
is possible in the ATC interface by setting up dedicated phases for transit vehicles
with zero split times. The phase can then be activated via the normal Green
Extension function, which takes the phase to a non-zero split time, which then gets
serviced. This method of phase insertion is sometimes known as “Phase-OnDemand”.
Phase Rotation — This method can be used if more than one phase must be
served before the transit phase can be served. If phase rotation is configured, the
two upcoming phases are ‘rotated’, thus serving the transit phase first, and then
going back to serve the other rotated phase, before going back to the normal
order. In the ATC environment, this is labeled as a phase ‘Shift’.
Phase Skipping — This option is not described in the US DOT TSP handbook but
is provided in the ATC environment. This is a simpler version of rotation, in that the
intervening phase is simply skipped during the current cycle so that the transit
phase can be serviced more quickly. This is often used to skip a dedicated turn
signal, since any vehicles that might be stranded in that phase can usually proceed
during the subsequent through-phase.
289
The ATC environment provides options to serve TSP TSP during Phase-Based
Coordination Patterns 1-48 and Interval-Based Patterns 101-228.
Individual Run Configurations can be set up with their own input signal extend, delay,
and failure detection options. And a modification of the basic operation is available to
allow a bus to jump ahead of the normal traffic queue. This is known as ‘Q Jumping’.
GETTING TSP SET UP
These are the basic steps to get started with Transit Signal Priority Operation.
290
1.
Choose and install a vehicle detection system on your transit vehicles and at the
intersections to be given TSP response.
2.
Determine which approach detection output will be fed into which input on the
Controller. The particular input/output module installed in your ATC-1000 will
determine which pins or input method should be used to connect the detection
signals to the controller. (See “Chapter 14 — Serial and Data Connectors”,
starting on page 351 for pin assignment information.) The ATC-1000 can accept
up to 6 inputs for TSP signals.
3.
Go into the Run Parameters screen and enter the type of TSP Inputs you wish to
use. ( > 2.P ROGRAMMING > 8.T RANSIT S IGNAL P RIORITY > 2.R UN
P ARAMETERS )
4.
We’re going to start out by setting up one TSP Action Plan (Number 1) and one
Run Configuration (also Number 1). Go into the Action Plans screens ( >
2.P ROGRAMMING > 8.T RANSIT S IGNAL P RIORITY > 3.A CTION P LANS ), and on
screen 1 (the first one that appears), enable all of the TSP inputs that you will be
using.
5.
Now go into the Run Configuration screen ( > 2.P ROGRAMMING > 8.T RANSIT
S IGNAL P RIORITY > 4.R UN C ONFIGURATION ) and on the first Run screen (“Run
#1 of 8”) put ‘X’s under each Call to indicate which phases will be extended based
on TSP Input 1. Enter which phases will be active Queue Jumps based on TSP
Input 1. (Be sure the Queue Jump phases are also checked in the Calls array.) And
finally, put X’s next to each phase that will be skipped, shifted, or reduced as a
result of this TSP Input 1.
6.
Press the DWN – button to go to the screen for Run 2 in Run Configuration 1.
Repeat the actions of Step 5 for the phases that will be affected by TSP Input 2.
7.
Repeat the above two steps for each of the 8 Runs in Run Configuration 1.
8.
Go into the TSP Split Tables screens ( > 2.P ROGRAMMING > 8.T RANSIT
S IGNAL P RIORITY > 6.S PLIT T ABLE ) and enter values for GRN EXT for each
phase on each of the 16 split tables screens. (You will need to know how your
normal split tables are timed in order to do this wisely.)
Note here that we are assuming that you are using the normal Green Extend,
which also extends your Solid Don’t Walk pedestrian phases. If you wish to use a
different Green Extend mode, that value would be set in step 3 above, on the Run
Parameters screen.)
Getting TSP Set Up
9.
Go to the Time of Day Actions screens ( > 4.T IME OF D AY > 1.A CTIONS ) and
place a value of ‘1’ under each TOD event that gets used in your system. (This is
calling TSP Action Plan 1 for all of your TOD values.)
10. Go onto the Unit Parameters screen in the TSP menu ( > 2.P ROGRAMMING >
8.T RANSIT S IGNAL P RIORITY > 1.U NIT P ARAMETERS ) and put a ‘1’ next to
Default Coord Pattern, Systems TSP Action Plan, and Default TSP Action Plan.
11. Finally, on the same screen (Unit Parameters), change the value of TSP Enable
from OFF to ON (using the Y ES button). This will enable TSP actions in the
intersection whenever TSP calls are detected and passed to the controller.
Note
The above procedure assumes a very simplified TSP configuration
with only a single Action Plan and Run Configuration, and the default
methods used for Green extend and other variables. You can, of
course, modify these steps to make your TSP plan as simple or
complex as are needed within each intersection, including placing
delays and extends on individual TSP inputs, setting up multiple run
configurations called by multiple TSP action plans that can then be
called by events in your TOD schedule, or by other triggering events
such as Central pattern changes. The rest of this chapter describes
the details of those features, should you wish to utilize them.
Important
There are numerous places in the chain of requirements
where you may run into problems setting up TSP operation
on the ATC controller. To help with these, we’ve added a
TSP Troubleshooting section to “Chapter 12 — Configuration
and ”, starting on page 344.
291
TSP SCREENS AND PARAMETERS
Aside from I/O Mapping and Time of Day TSP Action Plan enabling, all of the parameters
and screens used to set up Transit Signal Priority on a Peek ATC controller are located
under the Transit Priority Menu
M AI N M EN U > 2.P ROGR AM M ING > 8.T R AN SIT S IGN AL P RI ORI TY
2.8 TRANSIT PRIORITY MENU
1. UNIT PARAMETERS
2. RUN PARAMETERS
3. ACTIONS PLANS
5. QUEUE JUMPING
6. SPLIT TABLE
Figure 247 – Transit Priority Menu
The only parts of the ATC interface that concern TSP operation that are not under this
menu are the Time of Day action plan settings, which are stored under the Time of Day
menu, on the Actions screens ( > 2.P ROGRAMMING > 4. T IME OF D AY > 1. A CTIONS ),
and the TSP Status screens, which can be accessed from the Status menu ( > 1.
S TATUS > B. T.S.P) and I/O Mapping TSP Inputs. ( > 2 . P R O G R A M M I N G > 1 . U N I T
CONFIGURATION > 5.COMMS AND I/O SETUP MENU > 4.I/O M APPING)
292
TSP Screens and Parameters
Unit Parameters
The Unit Parameters screen under the Transit Priority menu is used to set and store
values related to global TSP operation.
M AI N M EN U > 2.P ROGR AM M ING > 8.T R AN SIT S IGN AL P RI ORI TY > 1.U NIT P AR AM ETE RS
2.8.1 TRANSIT UNIT PARAMETERS PG 1 OF 1
TSP ENABLE:
ON
DEFAULT COORD PATTERN:
000 (0-253)
SYSTEM TSP ACTION PLAN:
00 (0-48)
DEFAULT TSP ACTION PLAN: 00 (0-48)
UTILIZATION PERIOD:
00 (0-24)
Figure 248 – Unit Parameters screen
TSP Enable — This is the ‘master switch’ to turn the TSP capability ON and OFF in the
ATC controller. TSP ENABLE is OFF by default, but it must be ON for TSP to be used
in the intersection.
Default Coord Pattern — This is the TSP Action plan to use when the controller goes
into NEMA Free operation (Pattern 254) and a transit vehicle is detected. A value of 0
(zero) means that the ATC controller should not use TSP during NEMA Free operation.
The default value is 0. (An upcoming release of the GreenWave firmware will support
TSP during Free mode.)
System TSP Action Plan — If the controller is under central system control (i.e. there
currently exists a Central Override, Traffic Responsive, or Adaptive pattern call from a
central system), then this is the TSP Action plan to run whenever a transit vehicle is
detected and the current pattern is in the range from 1 to 48. You can call any of the 48
TSP action plans, or set it to 0 (zero) to disable TSP operation whenever the controller is
under System control. If the controller is not under a system command and not currently
in Free operation, it will use whatever TSP Action plan is specified in your TOD table.
The default value is 0.
Default TSP Action Plan — This is the TSP Action plan to use when the controller goes
into NEMA Free operation (Pattern 254) and a transit vehicle is detected. A value of 0
(zero) means that the ATC controller should not use TSP during Pretimed Free
operation. The default value is 0. (An upcoming release of the GreenWave firmware will
support TSP during Free mode.)
Utilization Period — This parameter is used for logging the effectiveness of TSP
operations in the intersection. This Peek-specific parameter tells the controller how often
(in hours) to log data on the operating effectiveness of TSP actions. This is similar to the
Peek MOE (Measure-of-Effectiveness) logging feature of the 3000E controllers. A value
of 0 (zero) disables this form of logging. The default value is 0. There is more detail
about configuring and managing data logging services in the ATC controller starting on
page 331.
293
Run Parameters
This screen provides a location to enter parameters that are global values, per Run.
M AI N M EN U > 2.P ROGR AM M ING > 8.T R AN SIT S IGN AL P RI ORI TY > 2.R UN P AR AM ETE RS
2.8.2 TRANSIT RUN PARAMETERS
PG1OF1
RUN 1 2 3 4 5 6 7 8
INPUT MODE 0 0 0 0 0 0 0 0
VALUES:
0 = Constant Call, 1 = Check-In/Out
2 = Check-In Plus Time
GRN EXTEND MODE 0 0 0 0 0 0 0 0
VALUES:
0 = Grn/SDW, end of FDW decision
1 = Grn/SDW, end of Walk decision
2 = Grn/Walk, end of Walk decision
3 = Grn/Walk+SDW, end of Walk decision
4 = Mode 3 with Advance Cancel Input
Figure 249 – Run Parameters screen
Input Mode — Each TSP input channel can be assigned to use one of three input
methods to generate a ‘TSP Request’, depending on what type of detection equipment
(and the resulting detection output method) is installed at the intersection.
Note
A ‘Run Request’ is an internal ATC controller concept that functionally
means the Run Input + the Input Mode method for determining the request
length.
Mode 0 — Constant Call. Uses Check-In input as a steady signal. This tells
the TSP algorithms that the input signal on that channel stays on the entire
time that the transit vehicle is in range of the detector. In Mode 0, the
detection signal is assumed to stay ‘True’ from the time the detector first
detects the vehicle, until the vehicle passes through the intersection or out of
sight/range of the detector. This is the most common type of signal generated
by devices that use a single output channel per detector. This is the default
mode for all Run inputs.
Mode 1 — Check-in Check-out. This input mode uses both the Check-In and
Check-Out inputs. This mode assumes that the detector generates a short
pulse on one channel when the transit vehicle is first detected, and a second
short pulse on the other channel when the detector loses sight of the vehicle.
Mode 2 — Check-in Plus Time. This input mode uses the Check-In input
channel, when the detector only sends a short High signal pulse when the
transit vehicle is first detected. The ‘TSP Request’ that results from this signal
is then active for a preset number of seconds, defined by the Extend time that
you define for each Run on the Run Configuration screen.
294
Green Extend Mode — This value determines how the green extend prioritization
method deals with the extra phase time for related pedestrian phases, on a run-by-run
basis. In all cases, the FDW (Flashing Don’t Walk) portion of the pedestrian phase is not
changed. It remains at the value defined in the current pattern. This mode also
determines whether or not the TSP modification will be allowed to occur, based on
where the associated pedestrian phase is in its signal processing. Meaning, the way that
TSP Green Extend operates also depends on at what point in the pedestrian phase the
TSP input signal arrives.
Mode 0 — Don’t Walk mode. For TSP Green Extend to be granted, the TSP input
must arrive before the end of the flashing Don’t Walk (FDW) portion of the
Pedestrian phase. When TSP Green Extend is allowed to occur, the extra time is
also added to the Solid Don’t Walk portion of the pedestrian phase. This is the
default mode for all Runs. Please note that TSP operation assumes that
Pedestrian Phases are present. If the TSP intersection does not support
Pedestrian signals, TSP will still work, however only Mode 0 can be selected as
the Green Extend Mode. The decision point will be the Phase Force-Off.
Mode 1 — Don’t Walk mode with an End of Walk decision. For TSP Green Extend
to be granted, the TSP input must arrive before the end of the Walk portion of the
associated Pedestrian phase. When TSP Green Extend is allowed to occur, the
extra time is added to the Solid Don’t Walk (SDW) portion of the pedestrian phase.
Mode 2 — Walk mode. For TSP Green Extend to be granted, the TSP input must
arrive before the end of the Walk portion of the Pedestrian phase. When TSP
Green Extend does occur, the extra time is added to the Walk portion of the
pedestrian phase.
Mode 3 — Walk and Don’t Walk mode. For TSP Green Extend to be granted, the
TSP input must arrive before the end of the Walk portion of the Pedestrian phase.
When TSP Green Extend is allowed to occur, the extra time is split between the
Walk and Solid Don’t Walk portion of the pedestrian phase.
Mode 4 — Walk and Don’t Walk mode, plus Advance Cancel. Mode 4 is the same
as Mode 3, except that it is aware of the Advance Cancel input. If the Advance
Cancel Input transitions from active to inactive, this mode terminates the Walk
extension and the pedestrian phase advances to the Flashing Don’t Walk portion
of the ped phase.
295
More Details About the Green Extension Modes
1. Decision Point
(End of FDW phase):
Locks TSP Run Request
2. If POZ is active, extend
Green with Don’t Walk
3. When POZ becomes
inactive, terminate and
go to Amber
1. Emitter Reception
Point must be at or
beyond
3. Cancel Point lost reception
terminates extension in
Green/SDW (go to Amber)
Priority Operating Zone (POZ)
2. At end of FDW: Extension in
Green/SDW
Figure 250 – Green Extend Mode 0: Extensions during Green/Solid Don’t Walk (SDW)
296
1. Decision Point
(End of Walk):
2. If POZ is active, extend
3. When POZ becomes
go to Amber
DFDFD
Point must be at or beyond
the Decision Point
2. At end of Walk: Extension in
Green/SDW
Figure 251 – Green Extend Mode 1: Extensions during Green/Solid Don’t Walk (SDW)
297
2. If POZ is active,
extend Green with Walk
1. Decision Point
(End of Walk phase):
3. When POZ becomes
go to FDW
Green/Walk (go to FDW))
the Decision Point
2. At end of Walk: Extension
in Green/Walk
Figure 252 – Green Extend Mode 2: Extensions during Green/Walk
298
2. If POZ is active,
extend Green with Walk
3. When POZ becomes
go to FDW
1. Decision Point
(End of Walk):
Lock TSP Run Request
4. If POZ was active at
Decision Point, and is
still active, extend
5. When POZ becomes
go to Amber
Green/Walk (go to FDW)
the Decision Point
DFDFD
2. Extension in Green/Walk
Green/SDW
Figure 253 – Green Extend Mode 3: Extensions during Green/Walk and Green/Solid
Don’t Walk
299
2. If Zone 1 and Zone 2
are active, extend Green
with Walk
3. When Zone 1 or Zone 2
become inactive,
terminate and go to
FDW
1. Decision Point
(End of Walk): POZ 1* and
POZ 2** TSP Run Request
4. If Zone 2 was active at
Decision Point, and is
still active, extend
Green with SDW
5. When Zone 2 becomes
go to Amber
the Decision Point
POZ 1 terminates extension in
Green/Walk (go to FDW)
POZ 2 terminates extension in
Green/SDW (go to amber)
* Priority Operating Zone 1
** Priority Operating Zone 2
2. Extension in Green/Walk
Green/SDW
Figure 254 – Green Extend Mode 4: Extensions during Green/Walk and/or Green/Solid
Don’t Walk with Two Detection Zones
300
TSP Action Plans
Option 3 under the Transit Priority menu is where TSP Action Plans are defined. Use the
and
keys to switch between the 48 available action plan definition screens.
M AI N M EN U > 2.P ROGR AM M ING > 8.T R AN SIT S IGN AL P RI ORI TY > 3.A C TI ON P L AN S
2.8.3 TRANSIT ACTION PLAN 1 OF 48
RUN #
Run Enable:
1
2
3
Run Configuration:
Master Reservice Time:
Recovery Strategy:
0 = Normal
1 = Offset Correction
2 = Offset Correction
4
5
6
7
8
001
(1-8)
00000 (0-65535)
0
(0-3)
TSP-Phase Delayed
Figure 255 – TSP Action Plan screen
Run Enable settings — In each of the 48 TSP action plans, it is possible to disable one
or more of the 8 available runs in the selected Run Configuration (See next item). Place
an ‘X’ under the run number (by pressing the Y ES button) to enable that run. By default,
all runs are disabled.
Run Config — This is where one of the eight available Run Configurations is chosen for
use in this TSP Action plan. This tells the action plan which set of 8 Runs will be
available in the intersection while this Action Plan is in effect. The default value is Run
Config = 1.
Master Reservice Time — Reservice time is the amount of time that the controller locks
out all additional TSP requests after completion of a TSP Run. A value of 0 (zero)
means that this reservice limit is deactivated, meaning a second TSP call will be
accepted immediately after the first call. This is the ‘Master’ reservice time. Note that
there is also a reservice time value associated with each Run Configuration. Whichever
value is greater (either the Master Reservice Time stored here in the selected Action
Plan, or the Reservice Time stored in the associated Run Configuration) will be the
active requirement in the intersection. Applies only if the TSP request adjusts phase
times.
Recovery Strategy — This is a parameter that is only used with the ambient pattern
that the TSP action interrupts is a NEMA coordinated pattern. It defines how the
controller will respond after the transit vehicle has gone through the intersection to
recover from the changed timing, and its effect on coordinated operation. The three
possible modes are:
Mode 0 — ‘Normal’ recovery. TSP restores a negative offset error by
extending splits and restores a positive offset error by reducing splits, using
Menu 2.8.6 TSP Split Table Grn Ext (Extend) and Grn Rdc (Reduce) Times.
301
Mode 1 — ‘Offset Correction’ recovery. This option forces the Coordinator
module to use its Correction mode to recover the offset. In this option,
recovery begins during the TSP phase. Refer to the “Offset Correction
Ext/Reduce” topic in the Coordination section of the manual, on page 204.
Mode 2 — ‘Offset Correction TSP-Phase Delayed’ recovery. This works the
same way as Mode 1, however it waits until the end of the TSP prioritized
phase(s) before beginning the offset correction back to normal timing.
Run Configuration
The Run Configuration screens form an 8 by 8 matrix of screens that allow the operator
to define the parameter values for the eight Run Configurations, and the eight Runs
included in each Run Configuration.
M AI N M EN U > 2.P ROGR AM M ING > 8.T R AN SIT S IGN AL P RI ORI TY > 4.R UN C O NFIGUR AT ION
2.8.4 TRANSIT RUN CONFIGURATION 1 OF 8
Number keys select Run Configuration
Run 1 of 8 Page Up/Down for more
Run Input Times:
Delay 000 Ext 000 Fail 000 Reserve 00000
Max Requests During Offset Corr 000
11111111112222222222333
Ph/Ivl 12345678901234567890123456789012
Calls X
X
Q Jump X
Skip
X X
Shift X
Reduce
XXXX
Reserve X
Figure 256 – TSP Run Configuration screen (Run 1, Config 1)
Press the numbers
through
on the keypad to switch to the desired Run
Configuration. Using the
and
keys will allow you to switch between individual
Run screens within each Run Configuration. Figure 257 shows graphically how to
navigate between the screens.
302
Figure 257 – Navigating Run Configuration screens
Run Configuration # — This is the Run Configuration number for this set of Run
screens. This can be any value between 1 and 8, and is changed by pressing the 1
through 8 buttons on the ATC keypad at any time. When you do so, you are not
changing this value, but instead switching to another set of Run Configuration screens.
(See above.)
Run # — This indicates which of the eight runs within the Run Configuration you are
currently viewing or editing. You can navigate between the Run screens by using the
and
buttons.
Delay — This is a modification on the TSP input that feeds this run. When set, the TSP
Run waits this number of seconds before processing the request. An example use could
be that a bus has non-directional TSP indicator and crosses the street upstream in one
direction of the intersection. You would not want that bus to trigger TSP activity in this
intersection, so you could put a delay in to cover the period when the bus may be visible
by this intersection’s TSP detector. The default value is 0.
Ext — (Extend) This is also a modification on the TSP input that feeds this run. If
Extend is set, the input is artificially maintained ON for this number of seconds beyond
303
the time it would normally turn OFF in each of the three input modes. (For a discussion
of ‘Input Mode”, see page 294.) The default value is 0.
Note
The Extend value on this screen is NOT the amount of time that the green
is extended when the TSP Input is received. The actual extension time
values for TSP operation are set on the TSP Split Table screens.
(MM > 2.P ROGRAMMING > 8.T RANSIT S IGNAL P RIORITY >
6.S PLIT T ABLE )
Fail — This is a test on the TSP input. If the input stays ON for this number of seconds,
the input is ignored, and no further inputs on this channel will be accepted until the ON
signal goes away. This has a couple of purposes. It can take care of the case where a
transit vehicle may be stopped near an intersection for repair, or for some other activity,
and the TSP emitter on the vehicle remains on and visible to the intersection’s TSP
detector. Or it can also handle the case where the detector or input line are faulty and
keep the input ON in error. The default value is 0.
Reserve — (Reservice) Reservice time is the amount of time that the controller locks
out all additional TSP Requests after a TSP Run has finished. (Actually, for reservice
criteria, the test is actually the time since the TSP Request went away OR there is a
Clearance Fail.) A value of 0 (zero) means that this reservice limit is deactivated,
meaning a second TSP call will be accepted immediately after the first request. The
value stored on this screen is the ‘Per Run’ reservice time. Note that there is also a
reservice time value associated with the overall TSP Action Plan, known as the Master
Reservice Time. Whichever value is greater (either the Master Reservice Time
described on page 301, or the Reservice Time stored here in the individual Run) will be
the active requirement within the intersection. Applies only if the TSP Request adjusts
phase times.
Max Requests During Offset Corr — The maximum number of times a TSP Request
can extend an already-extending phase (due to TSP Recovery), to prevent toggling TSP
Requests from infinitely extending a phase.
Calls — This is the master list of phases or intervals that will be serviced by TSP actions
whenever this TSP Input is activated and this TSP Run Configuration group is the
selected group. When an ‘X’ is placed under one of these calls, the associated phase
number, or interval if running in a Pre-timed pattern, will receive the calls to Green
Extend. Green Extend is the default action of a TSP priority call. If you wish to apply the
additional Q Jump function available below, the phases also need to be selected here in
the Calls array. Use the Y ES button to place an ‘X’ and the N O button to remove an ‘X’.
Q Jumps — This array of values is used to enable and disable Queue jumping on the
selected phases or intervals when a TSP input is received on this channel. Typically, this
is an extra phase or interval that is only activated during TSP actions. For a Q Jump
action to occur, an ‘X’ must be placed in that phase/interval, and the associated Call
phase above must also be checked. Use the Y ES and N O buttons to control which Q
Jump phases are checked.
Skip phases — Use the Y ES and N O buttons to places ‘X’s next to those phases that
should be skipped over during the upcoming cycle as a result of this TSP input. If the
same phase is called above in the Call array and also here in the Skip array, the Skip
304
action will be ignored. In US DOT vernacular, this is known as the ‘Phase Skipping’
capability. This TSP method will not be used if the controller is currently operating in a
Pre-timed pattern.
Shift phases — Use the Y ES and N O buttons to places ‘X’s next to those phases that
will be shifted to the most favorable sequence position within the phase’s concurrency
group, causing quicker transit vehicle service.
Example: Standard 8-phase dual ring sequence, TSP phase = 4/8, Shift phase = 4/8.
If a TSP call occurs during 2/6, shifting causes 2/6 -> 4/8 -> 3/7 -> 2/6.
If a TSP call occurs during 3/7, no shifting occurs because 4/8 are in the most favorable
position.
Reduce phases — Use the Y ES and N O buttons to places ‘X’s next to those phases
that should be split reduced. The normal way to use this is to have all of the phases that
are not selected as Calls (above) be selected (‘X’) to allow them to be split reduced. In
US DOT vernacular, this is known as the ‘Early Green’ capability. This TSP method will
not be used if the controller is currently operating in a Pre-timed pattern. The Reduce
flag shortens intermediate phase splits, thus causing an earlier TSP phase start than
would be possible otherwise.
Reserve phases — This option allows a TSP-called Shift phase to run twice per cycle.
In the Shift Phases example above, if Reserve Phases = 4,8, a constant TSP Run
Request activating during 2/6 and calling phases 4/8 causes cycling: 2/6 -> 4,8 -> 3/7 ->
4/8 (via Reserve) -> 1/5 -> 2/6.
305
Queue Jumping
‘Queue jumping’ inserts a “Transit-Vehicle Signal” into the cycle, while holding the
associated phase Red, thus allowing the transit vehicle to jump out ahead of the rest of
the queue waiting at the lights. The way that queue jumping operates is defined on the
Queue Jumping screens under the Transit Priority menu. Each screen corresponds to
one of the six Queue Jump outputs on the controller.
M AI N M EN U > 2.P ROGR AM M ING > 8.T R AN SIT S IGN AL P RI ORIT Y > 5.Q U EUE J UM PING
2.8.5 TRANSIT Q JUMPING OUTPUT 1of6
Queue Jump Time: 000
Enabled Phases:
1 1 1 1 1 1 1
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
Enabled Intervals:
1 1 1 1 1 1 1
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
cont.
1 1 1 2 2 2 2 2
7 8 9 0 1 2 3 4
Figure 258 – TSP Queue Jumping screen
When a phase is marked as a QJump phase in the Run Configuration screens, the
controller searches the Queue Jumping Output screens to see which screen has an ‘X’
next to that phase as well. If you say that phase 2 is a QJump phase on the Run
screens, the controller will then look through the six Queue Jumping output screens to
find one that has phase 2 selected. When the phase is found, the output pin
corresponding to that screen (Output 1, in our example above) is sent High for the
number of seconds specified on that screen. (or ‘8’ seconds in our example.) This
search only looks for the first instance of that phase on the six Queue Jumping Output
screens, and then discontinues so that the TSP Run can continue.
Queue Jump Time — This is the time, in seconds, that this Transit Vehicle Signal
output (aka ‘Queue Jumping Output’) goes High.
Enabled phases — If the controller is running a phase-based pattern, this array
indicates which phases in the cycle, if indicated with a QJump ‘X’ in the TSP Run
screens, will trigger this Queue Jump output.
Enabled intervals — If the controller is running an interval-based pattern, these ‘X’s
indicate which intervals will trigger a Queue Jump output.
306
Split Table
These tables are the times, in seconds, that are applied on a phase-by-phase basis,
when TSP is activated on the given phase. These times are the maximum allowable
extension and reduction times that are used on the associated split table. If the current
pattern is running split table 10, then all TSP Runs use TSP Split Table 10 to extend and
reduce phases.
M AI N M EN U > 2.P ROGR AM M ING > 8.T R AN SIT S IGN AL P RI ORIT Y > 6.S PLIT T ABLE
2.8.6 TSP SPLIT TABLE
1 of 16
PHASE
1
GRN EXT:000
GRN RED:000
WLK EXT:000
WLK RDC:000
2
000
000
000
000
3
000
000
000
000
4
000
000
000
000
5
000
000
000
000
6
000
000
000
000
7
000
000
000
000
8
000
000
000
000
PHASE
9
GRN EXT:000
GRN RED:000
WLK EXT:000
WLK RDC:000
10
000
000
000
000
11
000
000
000
000
12
000
000
000
000
13
000
000
000
000
14
000
000
000
000
15
000
000
000
000
16
000
000
000
000
ALL VALUES 0-255 SECS
PAGE DOWN FOR MORE SPLITS
Figure 259 – Split Table screen
The sixteen screen correspond to the 16 screens in the coordination split tables.
(MM.1. 3. 3) You can define how times will be added to and reduced from the 16
available phases (in NEMA Phase-based pattern operation) when TSP operations
causes that phase to be Green Extended. All times are in seconds.
GRN EXT — (Green Extend Maximum) This is the maximum time that can be added
to the phase/ped phase combination when you are using Green Extend modes 0, 1,
3, and 4. The time to be added to the split when the phase’s TSP action is Called.
GRN RED — (Green/SDW Reduction Maximum) When a phase is allowed to TSP
Reduce by the Run settings, this is the maximum time that each split is allowed to be
reduced, in seconds. This is the maximum time that can be reduced using a
shortened solid Don’t Walk ped phase for this split.
WLK EXT — (Green/Walk Extension Maximum) The maximum amount of time that
can be added to the Walk portion of the phase when the TSP Request is Called
before the end of the Walk portion of the associated Pedestrian phase. This is only
used when you’ve set the run to use Green Extend modes 2, 3 or 4. The extra time
will be added to the Walk portion of the associated Pedestrian phase.
WLK RDC — (Green/Walk Reduction Maximum) When a phase is allowed to TSP
Reduce by the Run settings, this is the maximum time that each split is allowed to be
reduced, in seconds, using a shortened Walk phase for this split.
Note
The Flashing Don’t Walk (FDW) portion of the Pedestrian phase will
never be adjusted by any TSP operation.
307
TSP STATUS MONITORING
There are three Status screens that can be used to monitor the current state of TSP
operations:
The Time of Day Status screen always shows the current TSP Action Plan
assignment. (MM.1.1.3)
The TSP Inputs Status screen shows the current TSP inputs, the status of each of
the eight TSP Runs, the signal colors of all of the NEMA phases. (MM.1.1.6.1)
The TSP Outputs Status screen shows the TSP outputs, the Q Jump outputs, the
default programmed splits, and the TSP adjusted splits. (MM.1.1.6.2)
TSP TROUBLESHOOTING
Details are provided to help with the initial setup of TSP operations, and also for
troubleshooting ongoing operation, in “Troubleshooting Transit Signal Priority Operation”
with the TSP materials starting on page 344.
308
Chapter 11 — System Maintenance
This section explains the tools available under the System Maintenance menu of the ATC
interface. The following topics are discussed in detail in this chapter:
•
An overview of system maintenance on the ATC, on page 310
•
Using the database utilities, on page 311.
•
The Copy function, on page 314.
•
Greenwave’s diagnostics mode, on page 317.
309
OVERVIEW
The System Maintenance menu on the ATC controllers is used to load and copy
controller databases and to access the diagnostics system. It is also the menu to use to
update the firmware of the controller. Be aware that entering the diagnostics mode on
the System Maintenance menu will take the intersection into Flash operation. Ultimately,
the controller must be powered down and restarted in order to exit these diagnostics
screens, once they have been accessed.
M AIN M ENU > 3.S YSTEM M AINTENANCE
Note
The Diagnostics available here are different from those available when
pressing
+
(Utilities) on the keypad. Those diagnostics are a
lower level hardware-based set, particularly aimed at the interface circuit
board and the operation of the keyboard and display. (Refer to “Utilities
Menu” on page 328.)
3
SYSTEM MAINTENANCE MENU
1. DATABASE UTILITIES
2. COPY DATABASE DATA
3. ENTER DIAGNOSTICS MODE
Figure 260 – System Maintenance Menu
310
Database Utilities Screen
DATABASE UTILITIES SCREEN
The ATC controllers retains several pre-configured intersection databases in Flash
memory that can be retrieved and stored into your primary database. This is a quick way
to get a new controller configured with a basic set of parameters that can then be
modified to meet the requirements of a particular intersection. It also provides a way to
zero out the controller’s internal memory (‘Remove ALL Flash Data.’)
M AIN M ENU > 3.S YSTEM M AINTENANCE > 1.D ATABASE U TILITIES
3.1
DATABASE UTILITIES
0. Remove ALL Flash Data
1.8PH Sequential
2.4PH Dual Rng Main/4PH Sequential Side
3.8PH Quad-Left Dual Ring
4.4PH Sequential Main/4PH Dual Rng Side
5.Exclusive Pedestrian
6.Coordinated 8PH Quad-Left
7.8PH Quad-Left Preempt (Opticom Style)
Figure 261 – Database Utilities menu
Caution
Choosing any of the options on this menu will over-write all of your
current settings.
Option 0. Remove ALL Flash Data will set all database parameters to default settings.
Most of these settings are zero (0). The cabinet address will be changed to FFFF. This
also changes the last two octets of the IP Address to 183.128. The first two octets will
remain unchanged.
Caution
The entire database will be lost as soon as the ZERO (0) button is
pressed. There are no warning screens. The ATC will require a power
cycle to restart. THE INTERSECTION WILL GO INTO FLASH.
After pressing the 0. button, the screen will state “REMOVING FLASH DATA.” When all
of the database programming in Flash memory has been reloaded to default values, the
LCD will display “DONE REMOVING FLASH DATA,” followed momentarily by the
message: !!!! RESTART CONTROLLER!!!!
At this time the ATC must be powered down until all six of the small, green LEDs just
above the fuses extinguish completely. Reapply power.
The ATC has deleted the record of its hardware and software type. The ‘Abort Process’
screen below will display.
311
...HARDWARE / SOFTWARE TYPE MISMATCH
HW = TS22, SW = OTH
DHW = OTH , DSW = OTH
“E C Yes * E” WILL FORCE HW TYPE
SYST:128.002.183.128 LOC: 192.168.183.128
Figure 262 – Hardware/Software mismatch message
Press the following buttons firmly, one at a time, in order, to restore normal operation:
Caution
They keypad buttons are typomatic, or they will input the button’s
character multiple times if held down too long. Watch the space to the
left of word ‘HARDWARE’ on the screen above. A period (.) will appear
for each button press. If multiple periods appear for one button press,
power down, repeat the button press entry, but press each button
quickly to achieve one period per button press.
The ATC will now match its software to its hardware and boot to Screen 1.1.1, Runtime
Status. The ATC will be in Red Rest/DW for all four Rings. The TOD CMD will show
Pattern 0f, which is Soft Flash.
1.1.1 TS22 Tue 24-May-2011. P1:OK
RING STATUS
08:53:22 CAB:FFFF
R1
RED REST
DW
PRE INP
R2
RED REST
PRE KBD
DW
R3
RED REST
DW
R4
RED REST
DW
CALL STATUS 1111111
1234567890123456 CRD CMD:
VEH
SYS CMD:
PED
TOD CMD:
PHS
0
0
0f
Figure 263 – Empty Database Runtime Status screen
To load any of the seven default databases, press the numbered keypad button for the
desired database. When all of the the selected database’s programming in Flash
Memory has been reloaded to the selected database values, the LCD will display
“DONE DECOMPRESSING DATA,” followed momentarily by
312
Database Utilities Screen
!!!! RESTART CONTROLLER!!!! At this time, the ATC must be powered down until all
six of the small, green LEDs just above the fuses extinguish completely. Reapply power.
3.1
DATABASE UTILITIES
0. Remove ALL Flash Data
1.8PH Sequential
2.4PH Dual Rng Main/4PH Sequential Side
3.8PH Quad-Left Dual Ring
4.4PH Sequential Main/4PH Dual Rng Side
5.Exclusive Pedestrian
6.Coordinated 8PH Quad-Left
7.8PH Quad-Left Preempt (Opticom Style)
Figure 264 – Database Utilities screen
NOTE
These seven default intersection databases are for example/training
purposes only. They are not recommended to be utilized as a starting point
for a database to operate an actual intersection. It is strongly recommended
that Option 0. be employed to empty the database, and the complete
database be programmed by the end-user to insure that unintended features
do not affect live traffic.
313
COPYING DATABASE ENTRIES
The Copy Database Data screens provide a method to copy the contents of one area of
database memory into other similar areas. There are many places in the controller
database where multiple instances of the same type of data exist:
16 NEMA phases
48 TSP Action Plans
64 Detectors
32 Vehicular Overlaps
16 Pedestrian Overlaps
These are just a few examples. In any location where multiple instances of a particular
data type exist, the Copy Database Data menus provide a screen to copy data from one
instance to another, to several others, or to all of the others. This is a quick way to set up
one phase, detector, or overlap in the manner you wish, and then copy that data over to
the others as a template that can be modified for each.
There are separate sets of copy screens for the Actuated and Interval portions of the
database. First, choose which type of data you wish to copy.
M AI N M EN U > 3.S YSTEM M AI NTEN AN CE > 2.C OPY D AT AB AS E D AT A
3.2
COPY DATA MENU
1. ACTUATED DATA
2. INTERVAL DATA
Figure 265 – Copy Database Functions screen
Next, when you get into the Actuated or Interval Copy Data menu (We’ll show the
Actuated Copy menu here, just as an example) you need to pick which type of data you
would like to copy.
314
Copying Database Entries
M AI N M EN U > 3.S YSTEM M AI NTEN AN CE > 2.C OPY D AT AB AS E D AT A > 1.A C TU ATED
ACTUATED DATA
1.PHASE
6.DETECTOR
2.COORDINATION
7.PRREMPT
3.SEQUENCE
8.CHANNEL
4.OVERLAPS
9.SCHEDULE
[sic]
5.T.S.P
Figure 266 – Copying Actuated Data menu
In this example, we’ll choose the first option, Phase data.
M AI N M EN U > 3.S YSTEM M AINT EN ANCE > 2.C O PY D AT AB AS E D AT A > 1.A C TU AT E D > 1.P H AS E
3.2.1.1 COPY ACTUATED PHASE DATA
COPY FROM:
001
COPY TO
0000
A
C#
16
:
= ALL
= all data up to # element
= allowed max
Figure 267 – Copying Phase Data screen
Once you’ve chosen the type of data you would like to copy, you will be presented with
the same type of screen no matter what the exact data is. On it, you only need to specify
a source (COPY FROM) and destination (COPY TO) for the copy function.
COPY FROM – The Copy From field is the simpler one to fill in. It must be a single
instance of the data type. Usually one edits the first instance, and copies Phase 1 into all
of the other phases you wish to use, say phases 2 through 8. In this case, we just enter
the number ‘1’ in this field.
COPY TO – The Copy To field has a few options, as shown in the description just below
the Copy To field.
You can specify a single instance of the data, say ‘2’, so you would copy phase ‘1’
data into the phase 2 instance. The bottom row of hints shows you what the
highest acceptable number instance is for this type of data.
You can specify the letter ‘A’, using the A key on the controller’s keypad, to
indicate that you want to copy the source instance into all of the other instance of
this type of data in the controller.
315
Or you can copy into all instances up to the instance you specify. You do this by
entering the letter ‘C’ in the Copy To field, followed immediately by the number of
the instance. So if I wish to copy the data from Phase 1 into Phases 2 through 12, I
would enter ‘C12’ in the Copy To field.
To provide another example of the Copy Data function, let’s go back up to the
Coordination option on the Actuated Data menu. This presents a Copy Coord Data
menu, where we can choose to copy either pattern data or split data. Let’s choose
Pattern.
M AI N M EN U > 3.S YSTEM M AINT EN ANCE > 2.C O PY D AT AB AS E D AT A > 1.A C TU AT E D > 2.C OOR D
3.2.1.2
COPY COORD DATA MENU
1.PATTERN
2.SPLIT
Figure 268 – Copying Coord Data menu
This results in a display that is very similar to the one we saw before for Phase data.
M AI N M EN U > 3.S YSTEM M AINT EN ANCE > 2.C O PY D AT AB AS E D AT A > 1.A C TU AT E D >
2.C OORD > 1.P AT T ERN
3.2.1.2.1 COPY COORD PAT PLAN DATA
COPY FROM:
001
COPY TO
0000
A
C#
48
:
= ALL
= all data up to # element
= allowed max
Figure 269 – Copying Coord Pattern Plan data screen
As you can see from the hint text at the bottom of the screen, we can copy any single
defined Pattern instance into one or all 48 of the other Pattern instances, or into all
patterns up to the instance we specify using the
key.
All of the copy data screens function in this same way, across all types of data, including
Actuated Detector, TOD Schedule instances, Pretimed Timing Plans, Signal Plans, and
Preemption definitions.
316
Diagnostics Mode
DIAGNOSTICS MODE
The Enter Diagnostics Mode option on the System Maintenance menu is used to enter a
special mode of the ATC controller that allows you to troubleshooting the operation of
the hardware and firmware, as well as load new firmware and restart the controller.
Caution
Entering Diagnostics mode will automatically place the intersection into
Flashing operation, and will require a controller power down and restart to
exit.
When you select the option, you will be given the option to cancel out of the operation in
order to avoid placing the intersection into Flash.
M AIN M ENU > 3.S YSTEM M AINTENANCE > 3.E NTER D IAGNOSTICS M ODE
ENTERING DIAGNOSTICS MODE!
WARNING!!!! CONTROLLER IS GOING TO
RED REST FOLLOWED BY FLASHING OPERATION.
>>HIT 'NEXT' IF YOU WISH TO DO SO<<
>>'PREV' TO CANCEL<<
Figure 270 – Diagnostics Warning screen
If you truly wish to enter the Diagnostics screens, you can do so by pressing the
button at this point. Or you can press the
button to exit out of the Diagnostics mode
warning screen, in which case the operation of the intersection will not be interrupted.
If you proceed into the Diagnostics screen, you will be presented with a menu of options
on the Diagnostics Menu, as shown in Figure 271.
M AIN M ENU > 3.S YSTEM M AINTENANCE > 3.E NTER D IAGNOSTICS M ODE > NXT
DIAGNOSTICS MENU
1.INPUTS/OUTPUTS TEST
2.COMMS
3.MEMORY TEST (RAM, SRAM, FLASH)
4.TIME TEST (RTC)
5.USB (WRITE/READ)
6.SD CARD TEST
7.UPDATE FIRMWARE
Figure 271 – Diagnostics Menu screen
317
Diagnostics Mode Interface
The Diagnostics menus can be used to test the inputs, outputs, communications,
memory, real time clock and USB port of the controller.
M AI N M EN U > 3.S YSTEM M AINT EN ANCE > 3.E N TER D I AG NOS TI CS M ODE > NXT
DIAGNOSTICS MENU
1.INPUTS/OUTPUTS TEST
2.COMMS
3.MEMORY TEST (RAM, SRAM, FLASH)
4.TIME TEST (RTC)
5.USB (WRITE/READ)
6.SD CARD TEST
7.UPDATE FIRMWARE
Figure 272 – Diagnostics Menu screen
Inputs/Outputs Diagnostic Menu
Inputs and outputs can be tested from a single menu. The I/O Diagnostic Menu is for
ATC controllers with TS2, Type 2 I/O Modules.
M AI N M EN U > 3.S YSTEM M AI NTEN AN CE > 3.E NTER D I AG NO STICS M O DE > NXT >
1.I NPUTS /O U TP UTS T E ST
I/O DIAGNOSTIC MENU
1.IO PRODUCTION LOOPBACK TEST
2.STANDARD INPUTS
3.STANDARD OUTPUTS
4.D-TYPE MODULE INPUTS
5.D-TYPE MODULE OUTPUTS
6.D-TYPE MODULE LOOPBACK TEST
Only visible when
“D” module is installed and
recognized
Figure 273 – I/O Diagnostic Menu
IO TYPE 2 LOOPBACK TEST
This screen requires that an IO loopback harness be attached to the controller IO
module connectors. This is used by Peek factory personnel to verify the operation of the
controller and the IO module. Keypad commands can be used to start (
), resume (
), and stop (
) these automated tests. The screen will show the resulting data
generated. (MM.3.3.1.1)
318
Diagnostics Mode
SELECT: 1)START
TEST NUMBER
ACTIVE OUTPUT
ACTIVE INPUT
2)RESUME
3)STOP
: 0
: NONE
: NONE
>>’PREV’ TO GO BACK<<
Figure 274 – IO Production (Type 2) Loopback Test screen
This test is used by factory personnel to test the ATC utilizing a Peek Traffic/Transyt
Corporation 3000 Series Controller Diagnostic Test Unit. The IO Production Loopback
Test only applies to ATCs with TS2, Type 2 I/O Modules installed.
Standard Inputs Test Screen
This screen is used to test the physical inputs of the controller. (MM.3.3.1.2)
DIAGNOSTIC INPUT TEST
>>’PREV’ TO GO BACK<<
Figure 275 – Standard Input Test screen
To perform the Standard Input Test, attach the ATC-1000 to any NEMA light board
(such as a Transyt TB-1800 test board). Activate each switch. Check the Diagnostic
Input Test screen to see that the corresponding NEMA input is displayed as the correct
MS Connector (A, B, & C) and assigned pin. For example, vehicle detection phase 1
should be displayed as A-f.
319
Standard Outputs Diagnostics
Use this screen to test the outputs of the controller. (MM.3.3.1.3)
DIAGNOSTIC OUTPUT TEST
1.Start Output Cycling
2.Pause Output Cycling
3.Resume Output Cycling
4.Stop Output Cycling
ACTIVE OUTPUT : NONE
Output Number : 0
>>'PREV' TO GO BACK<<
Figure 276 – Outputs Diagnostics Test screen
To perform a standard output test, connect the ATC controller to a NEMA light board
(such as the Transyt TB-1800 Test Board). Apply power to the controller through the test
board. Navigate to the above screen, and choose option 1. Start Output Cycling.
Observe the output LEDs on the light board for proper operation. Pause the output
cycling using the
button if something suspect is observed. The output will halt the
changing of the output LEDs so that the issue can be recorded. Resume output cycling
to continue the LED sequence. Use the Stop Output Cycling command (
test after you have confirmed the proper operation of all outputs.
) to halt the
D Module Input Diagnostics
If a D-type module is installed in the ATC, this is the screen to use to analyze its physical
inputs. (MM.3.3.1.4)This D-Module input test operates in the same fashion as the
Standard Inputs test.
D Module Output Diagnostics
If a D-type module is installed in the ATC controller, this is the screen used to analyze
the outputs generated at its pins. (MM.3.3.1.5) Install the D-type module loopback
adapters to thea ppropriate connectors to perform these tests. This D-Module output test
operates in the same manner described for the Standard output test.
D Module Loopback Test Diagnostics
If a D-type module is installed in the ATC, use this screen to analyze generated inputs
and outputs. (MM.3.3.1.6)
This D-Module Loopback Test operates in the same manner described for the 1. IO
Production Loopback Test.
320
Diagnostics Mode
Communications Diagnostics
This screen can be used to test any of the serial ports on the controller.
M AI N M EN U > 3.S YSTEM M AINT EN ANCE > 3.E N TER D I AG NOS TI CS M ODE > NXT > 2.C OM M S
COMMUNICATION DIAGNOSTICS
1.SDLC Port 1 (SP5) Loopback Test
2.Port
3.Port
4.Port
5.Port
2
3
4
5
(SP3)
(SP1)
(SP4)
(SP2)
Loopback
Loopback
Loopback
Loopback
Test
Test
Test
Test
6.Run All Async Port Loopback Tests
7.Flow Control Test (PORT 2,3,5)
>>'PREV' TO GO BACK<<
Figure 277 – Communication Diagnostics screen
Install the communication port loopback adaptors to the appropriate connectors. Press
the option number (1-7) to start each test.
Memory Test
Also known as memory diagnostics, use this screen to run a series of tests on the
controller’s RAM, SRAM and Flash memory.
M AI N M EN U > 3.S YSTEM M AINT EN ANCE > 3.E N TER D I AG NOS TI CS M ODE > NXT >
3.M EM ORY T E S T
DIAGNOSTIC MEMORY TEST
Testing available RAM
Test 0: 13 %
Status: Testing...
Test 1:
0 %
Status: Testing...
Test 2:
0 %
Status: Testing...
Testing RAM
Memory: In Progress...
Testing SRAM
Memory: Not yet started.
Testing Flash Memory: Not yet started.
Figure 278 – Memory Diagnostics screen – Before Testing Starts
After the testing has started, if the controller passes them successfully, you will see the
following screen. If the test takes longer than four minutes, the test has failed.
321
DIAGNOSTIC MEMORY TEST
Testing
Test 0:
Test 1:
Test 2:
available
100 %
100 %
100 %
RAM
Status: Complete
Status: Complete
Status: Complete
Testing RAM
Memory: Passed
Testing SRAM
Memory: Passed
Testing Flash Memory: Passed
Figure 279 – Diagnostic Memory Test screen
Time Diagnostics
This screen is used to perform an internal diagnostic on the controller’s real-time clock.
M AI N M EN U > 3.S YSTEM M AINT EN ANCE > 3.E N TER D I AG NOS TI CS M ODE > NXT > 4.T IM E T ES T
Testing Real Time Clock
RTC Time: 13:22:37
Status: Testing...
Figure 280 – Testing Real Time Clock – test in progress
A successful test should be visible within 30 seconds.
Testing Real Time Clock
RTC Time: 13:22:54
Status: Passed.
Figure 281 – Testing Real Time Clock screen – Status result
322
Diagnostics Mode
USB Diagnostics
This screen can be used to test the USB hub, port, and any device you plug into them.
Start this screen first, and then insert the USB thumbdrive or memory device you wish to
use for testing. Data stored on the device will not be damaged.
M AI N M EN U > 3.S YSTEM M AINT EN ANCE > 3.E N TER D I AG NOS TI CS M ODE > NXT > 5.USB
Testing USB Device
USB Detected: No
Status: Not testing.
Insert a USB storage device
Press <Enter> after the USB device has
been detected to begin the test.
Do not remove the USB device during
the test.
Note: Device detection may take up to
9 seconds
Figure 282 – Testing USB Device screen
When a USB device is detected:
Testing USB Device
USB Detected: Yes
Status: Passing
Press <Enter> after the USB device has
been detected to begin the test.
Do not remove the USB device during
the test.
Note: Device detection may take up to
9 seconds
Figure 283 – Testing USB Device screen when USB device is detected
SD Card Test
An SD Card can be installed as a source of onboard memory storage (for example, for
large log file generation or retrieval, or for Advanced Data Logging. The SD card slot is
located on the back of the Home board of the controller. Contact Peek tech support for
addtional information about using this feature of the controller. This test screen will test
any installed SD card that is inserted into the ATC controller’s SD slot. The card will be
detected automatically, if it is present.
323
Updating the Firmware
Use this control to activate an update of the controller’s firmware from an attached USB
device, or across an Ethernet connection when the ATC firmware loader application is
connected to the controller.
Starting FW Loader
Figure 284 – Launching the FW Loader screens
After the Firmware Loader application loads, you will see:
ATC FW Loader v2.0
Waiting for SUB
Listening on ETH
eth0: 128.2.60.198
eth1: 192.168.60.199
Figure 285 – Waiting for firmware file on USB or Ethernet
At this point you will want to initiate the ATCLink Ethernet connection, or plug a USB
drive containing the updated firmware into the controller’s USB port.
If the files are properly detected, the listing of available firmware files will be displayed.
An example of this is shown in Figure 286.
324
Diagnostics Mode
Select FW File:
natc_v002R106.bin
natc_v003R148.bin
natc_v005R184.bin
natc_v005R186.bin
natc_v005R188.bin
natc_v005R259.bin
natc_v005R297.bin
> natc_v007R868.bin
natc_v007R993.bin
natc_v0081315.wfi
Figure 286 – Update Firmware file list
Use the green down arrow button to move the “>” cursor to the left of the desired
firmware revisions. Press the
button to select that file. A screen will appear
showing the progress of the traffic application update process. The message “Firmware
Update Complete, Restart is required. Cycle controller power OFF/ON or press
to
update again” will display. Power the controller completely down. (Wait for any text
visible on the controller’s screen to disappear.) Remove the USB drive or disconnect the
cable to the ATCLink computer. Reapply power to the controller. The screen shown in
Figure 287 will only appear if the database has been changed between upgrade
versions.
HARDWARE / SOFTWARE TYPE MISMATCH
HW = TS22, SW = TS22
DHW = OTH , DSW = OTH
“E C Yes * E” WILL FORCE HW TYPE
SYST:128.002.060.198 LOC: 192.168.060.199
Figure 287 – Hardware/Software mismatch message
The hardware/software type mismatch error shows up because the default state of the
new firmware probably does not match the I/O configuration of your controller. Press the
following buttons, one at a time, in order, to restore normal operation:
325
Caution
They keypad buttons are typomatic, or they will input the button’s character
multiple times if held down too long. Watch the space to the left of word
‘HARDWARE’ on the screen above. A period (.) will appear for each button
press. If multiple periods appear for one button press, power down, repeat the
button press entry, but press each button quickly to achieve one period per
button press.
Verify that the controller has returned to normal operation. As part of its next shutdown,
the ATC will automatically update its stored information about the current I/O
configuration, so the HW/SW error message should not reappear.
326
Chapter 12 — Configuration and
Troubleshooting
This chapter describes the Utilities configuration menu of an ATC controller, as well as several
hardware tools and techniques to troubleshoot the operations of the unit. The following topics are
•
Accessing the Utilities menus, on page 328
•
Firmware diagnostics mode, on page 342
•
Data Logging, on page 335
•
Preventative maintenance and calibration , on page 342.
•
General troubleshooting hints, on page 343
•
TSP Configuration hints, on page 345
327
Chapter 12 — Configuration and Troubleshooting
OVERVIEW
This chapter describes the utilities, diagnostics and troubleshooting techniques that may
be employed to configure the controller and to respond to issues with its operation.
These are divided into tools available from the keyboard and display interface, hardware
status indicators, and a general troubleshooting checklist.
UTILITIES MENUS
There are several configuration and diagnostics tools available from within the
controller’s firmware. The diagnostics available in the normal menu system, under the
System Maintenance menu, are described starting on page 317, as part of “Chapter 11
— System Maintenance.” The tools available under the Utilities menu, however, are
described here.
Utilities Menu for the Keyboard and Display
The Utilities menu can be opened from the controller’s keypad by pressing the Blue
function button (
) and then the
button (i.e. the “Utilities” button). The question
has been asked, “Why do the Peek ATC controllers have two separate diagnostics/test
environments?” This is an excellent question with a real-world answer: The Diagnostics
mode available in the normal menu system of the controller (as described in “Chapter 11
— System Maintenance”) are part of the normal firmware of the controller and are run on
the ATC Engine board processor. These tests on the Utilities menus, on the other hand,
are NOT part of the main firmware. They are run on the display/keyboard circuit board
processor and operate at a level much closer to the physical hardware.
** ATC TS2 Utilities Main Menu **
<
<
<
<
<
<
1
2
3
4
5
6
>
>
>
>
>
>
Keypad Test
Display Test
Voltage Status
Operational Status
Miscellaneous Status
Revision Info
<ESC> Quit
Figure 288 – Keyboard/Display Utilities menu
Press the keypad numbers corresponding to the test or status screens listed on the
Utilities menu. To return to this menu from a test or status screen, press the
button.
To exit out of the Utilities menu back to the regular menu system and status displays,
press the
328
key.
Utilities Menus
Additional Details About the Utilities Screens
Use these screens to test the operation of your keypad, the display and to show the
current operating voltages within the controller. Access each screen by pressing the
number button associated with it (i.e.
to access the Keypad Test screen, etc.)
When finished working in the test and status screens, use the
the main Utilities menu.
Note
The keypad test screen requires you to press
button to return to
twice to return to the Utilities
menu.
The Operational Status screen provides information about internal monitoring variables
used to track the overall health of the controller.
The Miscellaneous Status screen can be used to test the backlight, set the backlight
timer, view the internal temperature of the display module, view the contrast value, and
test the controller’s buzzer, amongst a few other miscellaneous items.
** Miscellaneous Status **
<B>Check Buzzer:
ESW1 Init Status:
EEPROM Init Satus:
Backlight Mode:
Backlight timeout:
Internal Temp:
Contrast Value:
--GOOD
GOOD
ON
560 [SEC]
28C [82F]
110
Figure 289 – Miscellaneous Status screen
The backlight and contrast controls on the front panel work as usual in this environment:
Pressing the
button will sound the controller’s internal buzzer momentarily.
,
to turn the backlight on and off. The status of the Backlight Mode field on this
screen will be updated to show the current state.
,
and
,
can be used to change the Contrast Value for the display,
whose value will also be updated on the associated field on the Miscellaneous Status
screen.
Use the
and
buttons to change the value of the backlight timeout value. Using
the arrows will raise and lower the value of this timeout field by 10 seconds for each
329
button press. The value can be anything between 10 and 630 seconds, and it will be
retained when you leave this screen. This value is used to determine how long the
backlight will stay on after a button press when using the front panel interface of the
controller.
The Revision Info screen gives the revision level and release date information of the
firmware running on the hardware components of the ATC: the main (or ‘host’) board,
the power supply unit, and the I/O interface board. This screen doesn’t show revision
information about the GreenWave firmware or the operating system of the controller.
That information can be accessed by returning to the main menu system (
going to the Rivisions screen under the Status menu. (MM.1.5)
330
) and
USB Operations
USB OPERATIONS
The USB port on the front of the ATC controller is typically used to move data, in the
form of controller databases, log files, and software/firmware updates, to and from the
controller.
USB Menu
The following menu will appear automatically whenever you plug a USB thumbdrive or
other passive device into the USB port on the ATC controller. Note that the appearance
of this menu does not interrupt the normal operation of the controller.
USB device detected – remove to exit
1.USB->DATABASE
5.UPS_LOG->USB
2.DATABASE->USB
6.DBG CORE->USB
3.LOG->USB
7.DBG FLASH->USB
4.CMU_LOG->USB
8.ICC EDIT DB
Figure 290 – USB Menu
To select an option on this menu, press the keypad number corresponding to the
command (
through
).
The entries on this menu do exactly what they describe; they move data from one
location to another. The USB tag indicates whether data will be going to the USB
thumbdrive (‘-->USB’) or coming off of the USB drive and being stored on the controller
(‘USB-->’). The other object in each menu item specifies what type of data or file is being
moved. Those items where multiple files may be available provide a second display that
allows the operator to select which file should be transferred.
To get out of this menu and return to the screen you were on when prior to inserting the
USB drive, simply remove the device from the controller’s USB port.
Note
The USB menu will not appear if the controller is already in the Diagnostics
menu.
Legend
DATABASE = Collection of all intersection parameters. LOG = Event , Controller
Message, and Advanced Data Logs. CMU_LOG = Conflict Monitor logs. UPS_LOG =
Uninterruptable power supply logs. DBG = Debug log files. ICC = Illinois Commerce
Commission preemption database.
331
Details about the first five commands available on the USB menu are provided below.
Options 6 and 7 are used by Peek personnel to collect debugging information about the
operation of the controller. Option 8 is used to modify an ICC Preemption. (Refer to page
265.)
Moving Databases Using a USB Drive
The controller database, or the set of all operating parameters stored in the controller,
can be moved to a USB thumbdrive so that it can be copied from controller to controller,
or to be retrieved by a PC-based application such as ATCLink or IQ Central.
To move a database from a USB drive to the Controller
1.
If the USB device has not been formatted previously to work with Peek ATC
controllers, use ATC Link to format the USB device.
2.
Place a copy of the database you want to use on the controller onto the USB
drive. It must be stored into the \ATC_LINUX\USTC_data directory. This can be
done either by writing it there using ATC Link, storing it on the USB device out of
IQ Central, copying the database out of another controller onto the USB device,
or even by copying it from an attachment to an email.
3.
Plug the USB drive containing the database into the controller to be updated.
4.
When the USB Menu appears, press the
USB->DATABASE command.
5.
The controller will ask for verification: “Download astc0235 ? ENT=Y ESC=N” The
name ‘astc0235’ is the standard filename for an ATC database. If you agree that
you want to overwrite all of the settings currently stored in your controller, press
key on the keypad to select the
the
key. If you realize that you do not want to do this, press the
to exit out of the copy process without overwriting the current database.
6.
If you press
, the file will be copied into the controller and decompressed into
memory. Note that the new settings will start to control the controller’s
operation immediately.
7.
Next, the controller will ask if you wish to “Download the IO Map?” Again, press
the
button if you do want to overwrite the current I/O output mapping data to
the controller, or press
8.
if you do NOT want to overwrite these settings.
Finally, the controller will ask if you wish to copy over the UPS objects. Press
to copy those items into the controller. Press
process.
9.
332
button
if you wish to cancel that
You will be returned to the USB menu. Remove the USB drive from the port. Note
that you need to restart the controller for the new settings to take effect Verify that
the new database values are correct and functioning.
USB Operations
To store the controller database on a USB drive
1.
If the USB device has not been formatted previously to work with a Peek ATC
controllers, use ATCLink to format the USB device.
2.
Plug the USB drive into the controller.
3.
When the USB Menu appears, press the
>USB command.
4.
If a database is already stored on the drive, you will be asked if you want to
overwrite it. Press the
button to overwrite the database file currently stored
on the USB thumbdrive, or press
5.
key to select the DATABASE--
to cancel out of the process.
If
was selected, the overwrite operation will occur. The controller will report
the action and then return you to the USB menu. Remove the thumbdrive from
the USB port.
This completes the storage of an ATC database onto a USB thumbdrive.
Moving Logs Using a USB Drive
There are three types of logs stored on an ATC controller that can be accessed by the
USB drive: Event logs (or just ‘LOG”), CMU logs, and UPS logs. You will have the option
to choose which one to store on the USB thumbdrive in step 3 below.
1.
If the USB device has not been formatted previously to work with Peek ATC
controllers, use ATCLink to format the USB device.
2.
Plug the USB drive into the controller.
3.
When the USB Menu appears, decide which log file you would like to retrieve.
You can choose one or more of these options at this stage:
4.
Press the
key to move the event log files to the USB drive.
Press the
key to move the conflict monitor log files to the USB drive.
press the
key to move the UPS log files to the USB drive.
The controller will report the data transfer action and then return you to the USB
menu. Remove the thumbdrive from the USB port.
This completes the storage of various log files onto a USB thumbdrive.
333
USB File System
The directories and files stored on a thumbdrive to be used with a Peek ATC controller
follow a standard arrangement and naming conventions. The file system is structured
like this:
Figure 291 – ATC USB thumbdrive file system
The ASTC_DATA_DISK file stored in the root directory tells the ATC controller and
ATC Link that the thumbdrive has been formatted and arranged specifically for use with
Peek ATC controllers.
The \USTC_data folder is where log data and controller database files are stored.
The \USTC_firmware folder is where software/firmware files for a Peek ATC controller
are stored. If the filename starts with ‘natc’, then the firmware is intended for a NEMAtype ATC controller, such as the ATC-1000 or ATC-2000 controllers. If the filename
starts with ‘atc’, then the firmware is intended for a New York CBD-type ATC controller.
Each controller will only recognize the firmware files of the correct type when attempting
an update.
334
Data Logging
DATA LOGGING
All of the logging functions of the ATC controllers, as well as the onscreen viewers of the
various data logs, are all accessed by going into the Logs menu on the controller’s main
menu. A variety of data logging options are available on the screens under this menu.
( > 4.L OGS )
4
LOGS MENU
1. CONTROLLER MESSAGE LOG
2. NTCIP EVENT LOG
3. ADVANCED CONTROLLER LOG
Figure 292 – Log Data menu
Log files can either be retrieved by a central system, such as IQ Central, or some of
them may be offloaded from the ATC controller by using the USB menu to store the files
on a USB thumb drive. (Refer to ”Moving Logs Using a USB Drive” on page 333.) At the
present time, only the Controller Message Log can be moved in this manner.
Controller Message Log
Press 1 on the Logs menu to see the data in the Controller Message Log onscreen, with
the newest data shown first.
M AI N M EN U > 4.L OGS > 1.C O NTROLL ER M ES S AG E L OG
4.1
CONTROLLER MESSAGE LOG 1..57
1. 2009-Jan-24 00:01:27 Tue:
CMU Control Changed to 0
2. 2009-Jan-26 00:01:27 Tue:
POWER UP status 0x00 (b0-4: flash, stop
time, alarm, minrcall, MCE)
3. 2009-Jan-26 00:02:32 Tue:
External restart: command 1 pattern 255
cycle 0
4. 2009-Jan-26 23:40:33 Tue:
CMU Control Changed to 0
5. 2009-Jan-26 23:40:33 Tue:
Figure 293 – Controller Message Log
335
Use the
button to see additional screens of the log. Use the
toward the beginning of the log, one screen at a time.
button to go back
A typical log entry shows the sequential entry number, followed by the date, time, and
day of the week that the entry was recorded, then the type of event that occurred,
followed by any details about that event. Here is an example entry:
130. 2009-Oct-13 06:21:57 Tue:
External restart: command 1 pattern 255
cycle 0
Figure 294 – Sample log entry
The current log(s) can be deleted or cleared by pressing the key sequence:
,
.
CLEAR CONTROLLER MESSAGE LOG!
WARNING!!!!
YOU ARE ABOUT TO CLEAR THE CONTROLLERS
MESSAGE LOG! ALL DATA WILL BE LOST!
HIT ‘NEXT’ IF YOU WISH TO DO SO
‘PREV’ TO CANCEL
Figure 295 – Controller Log Clear message
Select the Next (NXT) button to clear all data. The screen below will appear.
4.1
CONTROLLER MESSAGE LOG 1..1
No Message Log Entries!
Figure 296 – Controller Message Log
336
Data Logging
NTCIP Event Log
This log shows a listing, from most recent to oldest, of the NTCIP communications
events.
M AI N M EN U > 4.L OGS > 2.NTCIP E VENT L OG
4.2
NTCIP EVENT LOG
Figure 297 – NTCIP Event Log screen
Advanced Controller Logging Menu
The Advanced Controller Logging Menus provide the capability to set up custom data
logging by selecting options in the onscreen interface. Advanced Controller logging is
divided into two areas: Logging Setup and the Advanced Logging Viewer.
( > 4.L OGS > 3.A DV ANCED C ONTROLLER L OG )
4.3
ADVANCED CONTROLLER LOG
1. SETUP LOGGING OPTIONS
2. VIEW LOG
Figure 298 – Advanced Controller Log menu
The Advanced Logging feature allows the controller to gather data at one tenth of a
second resolution.
Setup Logging Options
This screen is where the Advanced logging feature is configured. Use the parameters on
this screen to select what data points that will be collected and visible on the Advanced
Loggging > View Log screen.
337
( > 4.L OGS > 3.A DV ANCED C ONTROLLER L OG > 1.S ETUP L OGGING O PTIONS )
4.3.1
ADVANCED CU LOG SETUP
ADVANCED LOGGING ENABLED..X
PHASE STATUS..X
PHASE TIMING..
DET VOL/OCC ..
PREEMPT.......X
UNIT..........
CHANNELS......
PHASE CONTROL..
DETECTORS......
OVERLAPS.......
COORD..........
DET ALARMS.....
ALARMS.........X
Figure 299 – Setup Logging Options screen
To change the current Advanced logging options, enter Edit mode (
) and use
the arrow keys to navigate to the setting you wish to modify. Use the Y ES and N O
buttons to either place or remove an X next to a data type. An X indicates that that piece
of data will be recorded in the Advanced logs, with tenth-of-a-second resolution.
The controller can gather event data for the following controller events:
Phase status (changes) — Phase ON, Phase OFF, Begin phase Next, Begin
phase green, yellow, and red, and begin ped walk, clear, and don’t walk.
Phase control — ON and OFF events for each of the following control events:
Phase Hold, Phase Omit, Phase Force OFF, Ped Omit, Vehicle Call, and Ped Call.
Phase timing — Phase Min Complete, Phase Termination Gap-Out, Phase
Termination Max-Out, Phase Termination Force-Off, and begin and end of
Allocated Split.
Detectors — On and Off events for vehicle detectors and ped detectors
Detector Volume/Occupancy — Volume/Occupancy sequence change, Vehicle
detector volume change, and Vehicle detector occupancy change.
Overlaps — Overlap On and OFF, Begin overlap green, green extension, yellow,
and red clear.
Preemption events — Preemption input ON and OFF, Preemptor in control ON
and OFF.
Coordination events — Pattern status change, free status change, cycle length
change, offset length change, and split change.
Unit events — Changes to the following parameters are recorded: Pattern,
Control status, Flash status, Alarm status 1 and 2, Short alarm status, as well as
Special function ON and OFF events
338
Data Logging
Detector Alarms — Vehicle detector alarm changes and Pedestrian detector
alarm changes
Channel events — Begin channel green, yellow and red events
Alarms — Power interrupt ON and OFF, Manual control enabled ON and OFF,
and Interval advance ON and OFF.
Export of Advanced Log Data
With the normal USB log transfer controls, the above data points in a comma-delimited
text file can be transferred to a USB thumbdrive. With these data points and an external
data processing system, it is possible to replay the entire operation of an intersection.
View Logs Screen
This screen is used to display the list of files that store the data gathered by the
Advanced Logging function. The files are listed alphabetically, with each file name
indicating the IP address and the date and time that the file was saved.
( > 4.L OGS > 3.A DV ANCED C ONTROLLER L OG > 2.V IEW L OG )
4.3.2 CHOOSE FILE TO VIEW
1of
LOG_10.120.0.247_2011_3_10_16.dat
LOG_10.120.0.247_2011_3_14_15.dat
LOG_10.120.0.247_2011_3_16_15.dat
LOG_10.120.0.247_2011_3_18_14.dat
LOG_10.120.0.247_2011_3_1_17.dat
LOG_10.120.0.247_2011_3_20_2.dat
LOG_10.120.0.247_2011_3_22_1.dat
LOG_10.120.0.247_2011_3_25_12.dat
LOG_10.120.0.247_2011_3_29_8.dat
LOG_10.120.0.247_2011_3_31_15.dat
LOG_10.120.0.247_2011_4_1_4.dat
LOG_10.120.0.247_2011_4_3_22.dat
LOG_10.120.0.247_2011_4_4_2.dat
LOG_10.120.0.247_2011_4_5_1.dat
LOG_10.120.0.247_2011_4_7_12.dat
2
Figure 300 – View Advanced Log Screen
The blinking row indicates which log file is currently selected. Use the
and
keys to change the data file that is selected. If there are more files than will fit on one
screen, it will be indicated in the top left corner of the screen. To see items on the other
screens, use the
adn
keys. When the desired file is selected, press the
key to open the file for viewing. When a file is opened, you will see a screen requesting
which information from the dataset you wish to view:
339
4.3.2
Choose Data to View
A = ALL
PHASE STATUS..
PHASE TIMING..
DET VOL/OCC...
PREEMPT.......
UNIT..........
CHANNELS......
NXT = CONTINUE
C = NONE
PHASE CONTROL..
DETECTORS......
OVERLAPS.......
COORD..........
DET ALARMS.....
ALARMS.........
Figure 301 – Choose Log Data to view
If you wish to view all of the advanced log data, press the
key to place an ‘X’ next
to every category on the screen at once. To clear all of the selections on the screen,
press the
button to clear all of the ‘X’s. Once you have all of the data objects
selected that wish to see in the onscreen report, press the
key to view the data.
The data file is displayed as a series of screens of text. The data file always starts out
with the data collection format version on the top row. Below that will appear the file
name of the data file you are viewing, the IP address of the controller in question (useful
when the data file is offloaded from the controller), the MAC address of the controller in
question, and the time of day that the data file began recording, in the format
SECONDS: MINUTES: HOUR. It then shows which phases or intervals were in use
(enabled) during the data logging period. What follows is the meat of the data, namely a
textual representation of binary data showing all of the events (of the selected type) that
occurred during the period. The number following each event description shows the time
that the event occurred (in tenths of seconds since the time that the data file started
recording.)
Use the
and
data are available.
340
keys to step through the data file display, if multiple pages of
Data Logging
Example of Advanced Log Viewing
The following screen shows an example Advanced Log as displayed on the ATC screen.
4.3.2
LOG
1of
ATC Data Collection Format Version 4
LOG_10.247.1.80_2011_1_21_14.dat
IP Address 10.247.1.80
MAC Address 0:50:C2:B6:50:34
Data Log Beginning 0:0:0
Phases in use: 2,3,4,6,7,8,9
Binary Data Follows:
Phase Term Gap Out :18805 3
Phase Term Gap Out :18805 7
Unit Ctrl Sta Chng :18805 3
Phase Omit on/off
:18805 1 ON
Ped Omit on/off
:18805 1 ON
Begin Overlap Yellow:18805 1
Phase Omit on/off
:18805 2 ON
Ped Omit on/off
:18805 2 ON
8
Figure 302 – ATC Data Collection Log (page 1 of 8)
LOG_10.247.1.80_2011_1_21_14.dat – This is the file name for the currently displayed
data log.
10.247.1.80 — the ATC IP address at the time the log was recorded.
2011_1_21_14 — the date and time the log was initiated. This date/time group is
January 21, 2011 at 2PM.
MAC Address 0:50:C2:B6:50:34 — the specific address of the ATC Controller
assigned to the hardware unit, which never changes.
Data Log Beginning 0:0:0 — means this log begins precisely at 2PM to the 10th of a
second. An ATC time tick is 0.1 second.
Phase Term Gap Out :18805 3 — This means Phase 3 terminated due to a Gap Out at
1880.5 seconds past 14:00 hours (2PM).
From this screen, press the PRV or MNU buttons to exit the Advanced Logging Viewer.
341
PREVENTATIVE MAINTENANCE AND CALIBRATION
The ATC controllers are designed to require minimal maintenance; however, certain
simple steps should be taken to insure proper operation. It is a good idea to periodically
check the unit’s wiring, terminals, and connectors for signs of breakage and wear.
Replace, if necessary. Vacuuming dust out of the unit and cleaning the front panel is a
valuable step in maintaining good air circulation.
The controller should also be checked after it has been installed for six months, and then
at least annually thereafter. Once the initial check is performed, a regular interval for
preventive maintenance should be established based on the installation and
environmental conditions. During such a maintenance visit, the following procedures
should be performed:
Check all wiring connections for tightness, corrosion, damaged insulation, etc.
Check all mounting hardware for proper tightness.
It is also recommended that the controller’s software be updated with the latest
revisions, when updates are warranted. This will allow more efficient and trouble-free
operation. Contact your Peek Traffic support representative to find out if updated
firmware is available.
Diagnosing Controller Operation
Heartbeat LED
A 3mm RED LED is located on the front panel just above and to the right of the USB
port. This will flash about twice per second to indicate that the controller’s Engine Board
is functioning correctly. The LED will double its flash rate whenever changes to the ATC
database are executed. If lit continuously or continuously dark, this indicates that the
Engine Board CPU has stalled.
Important
When the LED flashes in its ‘double-speed’ mode, be sure to allow it to finish the
memory write operation before attempting to navigate the menus or make further
changes to the database.
PC Communications
The controller must be powered up and in its normal operating mode in order to
communicate with a PC. When having problems establishing communications, check the
LEDs above the port to see if communications are occurring. If none are, or no
connection can be established, be sure the controller’s port settings (baud rate, bit
length, etc.) are set correctly in the controller’s Comms and I/O Setup menu
(MM.2.1.5), and make sure they match the settings of the computer’s COM port and
within the PC application being run (i.e. ATC Link, HyperTerminal, IQ Central,
TransSuite, etc.)
342
Troubleshooting
TROUBLESHOOTING
When a failure occurs during normal operation, after isolating the problem, most
problems can be corrected using a screwdriver, a multimeter and/or simply replacing
one of the modules or boards. The most common problems are directly related to loose
connections or broken wires. The second most likely is a failed ATC Engine board. The
controller diagnostics will easily identify if the controller has a problem. If the controller is
suspected, run its diagnostics and note any failures.
All procedures relative to good troubleshooting techniques should be followed. Also refer
to the suggestions in “Table 39 – Troubleshooting an ATC Controller” on page 343.
Clearly identify the problem.
Verify fuse conditions.
Check all breakers for proper position.
Visually check all cables, harnesses and plugs for loose or worn connections.
Replace defective parts as required.
When troubleshooting, refer to the cabinet prints and parts lists.
If a defective ATC module is found, contact your local Peek Traffic distributor or service
representative (see page 3 for contact information) so you can arrange to repair or
replace the faulty unit. Returns and factory repairs require an RMA (Returned Material
Authorization) number.
Table 39 – Troubleshooting an ATC Controller
Symptoms
Possible Cause
Corrective Action
Controller does not have power.
Power cord not plugged into controller
receptacle.
Plug in power cord to controller
receptacle.
Blown fuse or open circuit reaker in the
cabinet PDA panel.
Determine the cause of the blown fuse
or breaker. Correct and install new
fuse
Blown fuse in the controller’s front panel
Determine the cause of the blown fuse.
Correct and install new fuse
BIU FAULT light flashing.
Controller Heartbeat LED not
flashing.
Controller TX LEDs not flashing.
No valid communication with controller.
Replace faulty communication cable.
Faulty BIU.
Replace BIU.
Faulty controller.
Replace controller.
No valid communication with MMU.
Faulty MMU.
Replace MMU.
Faulty controller.
Replace controller
No valid communication through Serial
Port.
Faulty Serial Port Unit (PC, etc.)
Replace faulty Serial Port Unit.
Faulty controller.
Replace controller.
343
Symptoms
Possible Cause
Corrective Action
Controller’s RX LEDs not flashing.
No valid communication through Serial
Port
Faulty Serial Port Unit (PC, etc.)
Replace faulty Serial Port Unit
Faulty controller.
Replace controller.
Controller’s LINK LED not on.
Controller’s ACT LED not flashing.
No valid communication through LAN Port
Faulty LAN Port Unit (PC, etc.)
Replace faulty LAN Port Unit
Faulty controller.
Replace controller.
No valid communication through LAN Port
Faulty LAN Port Unit (PC, etc.)
Replace faulty LAN Port Unit
Faulty controller.
Replace controller.
Troubleshooting Transit Signal Priority Operation
There are two areas of TSP troubleshooting we’ll address. First, when setting up TSP for
the first time, it can be a bit confusing and it is possible to miss a step that prevents TSP
from operating.
Getting Up and Running
Here is a simple list of items that might prevent TSP from functioning when you first set
up the function:
Are the signal lines from the transit vehicle sensor correctly wired to the controller
inputs?
Is the TSP master Enable switch tuned ON? ( > 2.P ROGRAMMING > 8.T RANSIT
S IGNAL P RIORITY > 1.U NIT P ARAMETERS > TSP E NABLE = ON)
Is TSP set up to expect the correct input type from your transit vehicle detection
system. ( > 2.P ROGRAMMING > 8.T RANSIT S IGNAL P RIORITY > 2. R UN
P ARAMETERS > I NPUT M ODE VALUES )
Is the correct TSP Action plan being called in your Time of Day schedule? ( >
2.P ROGRAMMING > 4.T IME OF D AY > 1.A CTIONS > 1.P LANS > TSP = A CTION
P LAN #)
Does the currently active TSP Action Plan have the correct Runs enabled? ( >
2.P ROGRAMMING > 8.T RANSIT S IGNAL P RIORITY >3. A CTION P LAN (P ICK THE
CORRECT PLAN ) > R UN E NABLE = “X”)
Does the currently active TSP Action Plan call the correct Run Configuration? ( >
2.P ROGRAMMING > 8.T RANSIT S IGNAL P RIORITY >3. A CTION P LAN (P ICK THE
CORRECT PLAN ) > R UN C ONFIGURATION = #)
Is the Run calling the correct phase or phases for Green Extension? (M AIN M ENU
> 2.P ROGRAMMING > 8.T RANSIT S IGNAL P RIORITY > 4.R UN C ONFIGURATION >
D WN OR U P TO R UN = TSP I NPUT # > C ALLS = P HASES TO EXTEND )
344
Troubleshooting
Is the TSP Split Table for that Phase properly configured with extension and
reduction times? ( > 2.P ROGRAMMING > 8.T RANSIT S IGNAL P RIORITY > 6.
S PLIT T ABLE > U SE
AND
TO
S WITCH
TSP S PLIT
THAT
S PLIT TABLE THAT IS BEING CALLED BY THE
P ATTERN > V ERIFY T IMES FOR GRN EXT AND GRN RDC)
CORRESPONDS TO THE
ACTIVE
TO
CURRENT
TSP Symptoms and Remedies
Second, if you are having problems with TSP operation, this checklist should help
assess and correct such problems.
Table 40 – TSP Troubleshooting Checklist
Symptom
Possible Causes
Suggested Remedies
TSP Run never
activates
Coordination is not active. TSP
does not function during Free
operation (Pattern = 254)
Make sure the controller is not
running in FREE mode (pattern
254) when the TSP call is
received.
Running an interval pattern. TSP
does not function from interval
patterns.
Switch to a phase-based pattern
(patterns between 1 and 48)
TSP signal not reaching the
controller
Verify output from the TSP
vehicle detector
TSP signal is being input on the
incorrect pin or connector
Verify TSP input pin in the IO
mapping table of the ATC
controller
TSP is not enabled
Make sure main TSP ENABLE is
ON (MM.2.8.1)
TSP Run is not enabled
Make sure the Run being called is
enabled in the TSP Action Plan
TSP Input type is not correct
Make sure the TSP Input Mode
for the input in question is set to
the proper Input Mode (MM > 2
> 8 > 2)
TSP input delay is too high
Make sure the Delay on the TSP
Input is not too high (MM > 2 >
8 > 4 > R UN C ONFIG # >
D EL AY V ALUE )
TSP Reservice delay is too long
There are two places where
Reservice time can be input, in
the Action Plan, and in the Run
Configuration. The higher value is
the one that takes precedence.
TSP Run for the active Run
Configuration does not place a
Call on a valid Phase
Go into the Run Configuration
screen for this TSP Run and
make sure an ‘X’ is placed under
the desired phase(s) in the Call
array.
TSP Status displays
an ‘R’ under Run
Status, but there is
no TSP phase green
extension
345
Symptom
TSP Status displays
an ‘R’ under Run
Status, but there is
no non-TSP phase
reduction
346
Possible Causes
Suggested Remedies
Extension times on the TSP Split
table are zero
Make sure you’ve entered times
in the correct TSP Split screen.
Make sure you’re entering
extension times for the proper
Green Extend mode. Double
check which Green Extend mode
you intend to use.
Reduce is not active for the
desired phases
Make sure an ‘X’ is placed under
the desired phase(s) to reduce in
the Reduce array on the Run
screen for the active TSP Run
Configuration.
Reduction times in the TSP Split
tables are set to zero
Make sure valid reduction times
are placed in the phases for the
correct TSP Split plan. Make sure
the TSP Split plan matches the
active Coordination Split plan.
Reduction times cause times that
are lower than the phase
minimum in the split table
Increase the minimum value in
the split table, or lower the
reduction time to use.
Chapter 13 — Controller Specifications
This section details some of the physical characteristics of the ATC-1000 controller. The following
topics are discussed in detail in this appendix:
•
An overview of the controller’s design, on page 348.
•
Physical/environmental specifications, on page 349.
•
NTCIP compliance specifications, on page 350.
347
OVERVIEW OF CONTROLLER SPECIFICATIONS
The ATC controllers from Peek are modular, standards-based units that use the
Freescale Power Quix 2 hardware platform, with a memory management unit and
floating point capabilities. They use the Linux operating system with memory
management for process isolation and to ensure operational integrity. They fully support
NEMA TS2 Type 1 and TS2 Type 2 functionality and are compliant with NTCIP 1201
and 1202. All of the ATC controllers have three built-in front panel serial ports, two
10/100 Base-T Ethernet ports, a high speed SDLC port for communications to the
cabinet BIU(s), and a 3000E-compatible modem slot with full modem flow control
support where an optional internal modem can be installed. A high speed USB2 port is
standard.
All of the ATC timing functions and clocks are referenced to the 60 Hz AC power line
when AC power is available. Thus, the ATC’s timing will track any frequency drift of AC
power.
The ATC does not use battery backup for memory storage or the real time clock. Rather,
all static memory (SRAM) and the real time clock are powered by a pair of super
capacitors, which provide sufficient power to operate the SRAM and clock functions of
the controller for up to seven days without AC power. Programs and operation database
information is stored and preserved indefinitely in non-volatile flash memory.
The controllers continuously monitor the STOP TIMING function from a conflict monitor,
CMU or MMU. They use the transition from ON to OFF to resume proper traffic
operation. An ATC controller also sends a watchdog signal (CVM) to the cabinet conflict
monitor or fault monitor signal to an MMU, which prevents the cabinet from going into
FLASH.
The ATC enforces a minimum time of 3 seconds for each yellow signal. A shorter time
for any yellow signal is not allowed, because the CMU identifies a short yellow time as a
fault and would automatically put the cabinet into FLASH. This minimum time value is
preset in the CMU (2.7 seconds) and is called out in the CMU specification.
The Peek ATC controllers can be interrogated by a Microsoft Windows®-based software
package known as ATC Link™ running on an external computer for setting and
retrieving data from the unit via the front panel serial or Ethernet ports. This same
capability is also available from Peek’s central system software package: IQ Central™.
The front panel display and keypad can be used to view the status of the controller, view
most of the available program parameters, and also to modify the programming of the
unit.
All of the ATC controllers feature dual traffic applications, so they can handle either
interval-based or phase-based operations. These applications are fully NTCIP-compliant
implementations that easily integrate into any NTCIP-compliant ITS or central traffic
control system.
348
Overview of Controller Specifications
Physical/Environmental Specifications
Table 41 – Physical and Environmental Specifications
Property
Value
Temperature Range
Relative Humidity
Input Supply Voltage and
Frequency
Power Consumption
Dimensions
–35° to +165° F (–37° to +74° C)
0% to 95%
95 to 135 VAC, 60 ± 3 Hz
Weight
Mounting
Wiring
CPU / Clock Speed
Non-volatile Memory
RAM
SRAM
Display
Contrast
Serial Ports
Ethernet Port
Fuse
Keypad
USB
Lamps
Modem Slot
DataKey
Language Support in the front
panel interface
Cabinet I/O
<25 VA (nominal w/o display backlight or heater on)
10¼” H x 14¾” W x 10½” D (ATC-1000 & 2000)
261mm × 375mm × 267mm
9 to 11 pounds (4 to 5 kg) depending on which I/O
modules, D modules and modem options are installed
Cabinet shelf mounted (ATC-1000/2000) or rackmounted (ATC-3000 and ATCi)
MIL-W 16878D, Type B or better
Freescale Power Quix 2 at 300 MHz
16 MB Flash
64 MB SDRAM
1 MB
40 character by 16 line, alpha-numeric, LED-backlit
LCD
Keypad contrast adjustment
4 Ports with 2 DB-9 male (RS-232); 1 DB-15 female
High speed (SDLC), and 1 DB-25 Modem
Two 10/100 Base-T
2A slow-blow fuses on AC Line and 24VDC
32 key softtouch keypad in two parts: 16 key hex
alphanumeric keypad. 16 key function-based keypad
with color-coded navigation and function keys
High Speed USB-2 port
6 power monitor LEDs. Heartbeat LED, and 12 port
status LEDs
Optional modem slot with full modem control support
Optional Datakey slot
English
Spanish
Afrikaans
French
Field swappable I/O and D Modules are available to
support these cabinet types:
NEMA TS2 Type 1
Traconex 390
NEMA TS2 Type 2
Multisonics 820
HMC-1000 (Honeywell)
LMD-9200 / 40
Modules are auto-recognized by the controller
349
NTCIP Compliance
The Peek ATC Series controllers can use serial, modem or Ethernet ports to
communicate with the central computer using NTCIP (National Transportation
Communications for ITS Protocol). NTCIP conforms to NEMA TS2-2003 for Pretimed
Type 1 (P1N Level 2) controllers.
NTCIP communications protocols and the full object seet associated with them have not
yet been completely specified by the FHWA. The NTCIP communications support
adheres to the following timing constraints: whenever a message is received by the
controller and that requires the controller to respond, (e.g. all messages except a
broadcast message) the controller will initiate its response (i.e., start the transmission of
data) within 40 ms. Further, the data is transmitted continuously (i.e., no gaps between
characters) until the transmission is complete.
Once-per-second communications will be critical to the central management of the
controllers. NTCIP relies on “dynamic object” capability to allow the central system to
program a list of data items to be returned in response to a “short-hand” request. ATC
controllers support dynamic objects.
To support get (uploading) and send ( downloading) calls of the controller database over
relatively slow channels, the ATC controllers support the concept of “logical blocks”.
Peek Traffic has defined NTCIP manufacturer proprietary objects that encapsulate a
group of data elements (e.g., phase timings block, coordination plan block, detector
configuration block, etc.). By grouping the objects into blocks, the number of objects
required to transfer the data is reduced, and, since the bulk of the NTCIP overhead is in
the object headers and identifiers, transfer time is much more sensitive to the number of
blocks than to the size of each block. Upon receipt of a database download block, the
controller responds within the timing envelope described. In addition, the receipt of
multiple database download blocks in rapid succession does not result in any
communications errors, NTCIP (SNMP) error codes, or communications turn-around
delays.
350
Chapter 14 — Serial and Data Connectors
This appendix provides details about the serial ports and data connectors of the ATC-1000 and
ATC-2000 controllers, including pin locations and functions. The following topics are discussed in
detail in this chapter:
•
Port 1, the SDLC port, on page 352.
•
Port 2, the RS-232 connector, on page 353.
•
Port 3, the optional modem port, on page 354.
•
Port 4, the Local serial connector, on page 354.
•
Port 5, the SPARE port, on page 355.
•
Ethernet ports, on page 356.
•
USB ports, on page 357.
351
OVERVIEW
The following topics describe the functions of the pins for each of the port connectors on
the front of a Peek ATC controller. Here, we list the per-pin functions of the
communications ports and then the cabinet connectors. The USB ports use the standard
USB layout.
PORT 1 - SDLC CONNECTOR
Port 1 has a female 15-pin, metal shell, D-type connector and mates
with a male connector of the same form factor.
Figure 303 – Pin assignment looking into the Port 1 connector
Table 42 – Pin Assignments for Port 1 SDLC
352
PIN
FUNCTION
I/O
1
Tx Data +
Output
2
Logic Ground
3
Tx Clock +
4
Logic Ground
5
Rx Data +
6
Logic Ground
7
Rx Clock +
8
Logic Ground
Output
Input
Tx Data –
Output
Port 1 Disable
Input
11
Tx Clock -
Output
12
Earth Ground
Rx Data Reserved
15
Rx Clock -
4
5
6
7
9
10
11
12
13
14
15
Input
9
14
3
8
10
13
1
2
Input
Input
Port 2 – RS-232C Connector
PORT 2 – RS-232C CONNECTOR
Port 2 is a 25 pin, female, D-sub connector which functions as the
RS-232C port for the ATC controllers and is pinned per the ATC
V5.2b Standard.
Figure 304 – Pin assignment looking into the Port 2
connector
Table 43 – Pin Assignments for Port 2 RS-232C
1
2
3
Pin
Function
4
1
Chassis GND
5
2
TD
6
3
RD
4
RTS
7
5
CTS
8
6
No connection
9
7
LOGIC GND
8
CD
10
20
No connection
11
22
No connection
12
13
14
15
16
17
18
19
20
21
22
23
24
25
353
PORT 3 – COMMUNICATIONS MODULE PORT
Port 3 on the ATC-1000 and ATC-2000 controllers is the name assigned to whatever
communications module is installed in the modem slot of the controller (e.g. DSP/FSK or
850 nm MM Fiber Optic.) Details about the connector pin assignments for specific
modems are defined in the modem documentation.
PORT 4 - LOCAL CONNECTOR
Port 4 of the controller’s front panel is a reduced pin assigned version of a standard PC
serial port. Cables designed for PCs can be used with the ATC
controllers. This communication port mates with a 9-pin, metal shell,
D-sub female connector. Connections are made as shown in Figure
305.
5
Figure 305 – Pin assignment, looking into the male Port 4
connector
Table 44 – Pin Assignments for Port 4
FUNCTION
1
No connection
2
Rx DATA
Input
3
Tx DATA
Output
No connection
5
SIGNAL GROUND
6
No connection
7
No connection
8
No connection
9
No connection
8
3
PIN
4
9
4
I/O
7
2
1
6
The firmware in the ATC-1000 Controller can be used to enable or disable the port, set
the parity, stop bits, baud rate, and type of HW flow control to be used on the port.
354
Port 5 – Spare/UPS Connector
PORT 5 – SPARE/UPS CONNECTOR
Port 5 is a n RS-232 serial port that has a pin assignment that meets the ATC V5.2b
Standard, and that has the additional capability, thanks to the firmware, to communicate
via the NTCIP protocol. This means that it can be used either for a local serial
connection, for instance to an on-site PC or a USB monitoring channel, or as a
connection point to a central system that speaks the NTCIP protocol, such as IQ
Central. The firmware in the controller can be used to enable or disable the port. set the
parity, stop bits, and baud rate of the port, as well as define the type of hardware flow
control to be used.
5
9
4
8
3
7
2
1
6
Figure 306 – Pin assignment looking into the Port 5 connector
Table 45 – Pin Assignments for Port 5
PIN
FUNCTION
I/O
1
2
3
4
5
6
7
8
9
DCD
Rx DATA
Tx DATA
No Connection
SIGNAL GROUND
No Connection
RTS
CTS
No Connection
Input
Input
Output
Output
Input
355
ETHERNET CONNECTORS
The two (or optionally, four) Ethernet connectors on the front panel
of the ATC controllers are 10/100Base-T, using a standard RJ-45
socket.
Figure 307 – Pin assignment looking into the Ethernet ports
Table 46 – Pin Assignments for the Ethernet ports
PIN
FUNCTION
1
2
3
4
5
6
7
8
TX+
TX–
RX+
No Connection
No Connection
RX–
No Connection
No Connection
The left-most of the Ethernet ports is the standard NTCIP port, intended for connection
to the central system software. The right (if there are two) Ethernet port is typically used
to connect your local laptop running ATC Link. The two ports have different IP
addresses, which can be set on the IP/Cabinet Address screen. (See page 93). If there
are four ports on your unit, the first and third (from the left) are the central ports and are
on one Ethernet hub, and the second and fourth ports (again, from the left) are the local
ports and are on the other Ethernet hub.
356
USB Connectors
USB CONNECTORS
The single USB (Universal Serial Bus) port on the front of an ATC controller is a
standard USB 2.0 port and will accept any standard USB Flash device. Devices can be
‘hot swapped’ into and out of this USB port just like on a PC. Inserting a device will
trigger the USB menu on the front panel interface.
4
3
2
1
Figure 308 – Pin assignments looking into the USB port
Table 47 – Pin Assignments for the ATC USB port
PIN
Function
Cable Color
1
+VCC
Red
2
Data –
White
3
Data +
Green
4
GND
Black
The USB port on the Peek ATC controllers follows the Universal Serial Bus standard
and improve plug-and-play capabilities by allowing devices to be hot swapped or added
to the system without rebooting the controller. When a new device first plugs in, the host
board enumerates it and loads the device driver necessary to run it. The loading of the
appropriate driver is done using a PID/VID (Product ID/Vendor ID) combination supplied
by the attached hardware. The USB host controller in the Peek ATC controllers uses the
EHCI (Enhanced Host Controller Interface), meaning it is compatible with USB 2.0
devices, however the Controllers will only recognize passive USB devices such as RAM
or Flash memory devices, but not cameras, external hard drives, or other active devices.
The USB specification limits the cable length of a cable between full speed devices to
16 feet, 4.8 inches (5.0 meters). For low speed devices, the computer cable limit is 9
feet, 10 inches (3.0 meters).
357
358
Chapter 15 — I/O Module Connector Details
This chapter provides details about the ports and connectors on the various Input/Output modules
available for the ATC controllers, including pin locations and functions. The following topics are
•
TS2 Type 1 Connectors, on page 360.
•
TS2 Type 2 I/O Connectors, on page 361.
•
HMC-1000 I/O Connectors, on page 371.
•
LMD I/O Connectors, on page 374.
•
Closed Loop D Module, on page 381.
•
LMD 9200 D Module, on page 384.
•
Traconex D Module, on page 386.
•
Multisonics D Module, on page 388.
359
CONNECTOR DETAILS
The following topics describe the functions of the pins for each of the port connectors on
the front of the ATC controller. Here, we list the per-pin functions of the communications
ports and then the cabinet connectors. We don’t define the USB ports pin assignments
here, since they use the standard USB layout.
NEMA TS2 TYPE 1 I/O MODULE
The ATC TS2 Type 1 I/O Module has a single I/O connector, the round, screw attached
Port A connector specified in the TS2 Type 1 standard. It’s primary purpose is to provide
the controller with power, fault monitoring and ground
lines through the front panel of the device.
Port A Connector
H
Figure 309 – TS2 Type 1 MS-A Connector
Table 48 – Pin Assignments for the ATC-1000 TS2 Type 1
MS-A connector
Pin
360
Function
I/O
A
AC Neutral
Input
B
Not Used
N/A
C
AC Line
Input
D
Not Used
N/A
E
Not Used
N/A
F
Fault Monitor
Output
G
Logic Ground
Output
H
Earth Ground
Input
I
Not Used
N/A
J
Not Used
N/A
A
G
I
B
F
J
C
E
D
NEMA TS2 TYPE 2 I/O MODULE
The ATC’s NEMA TS2 Type 2 I/O module has three standard connectors for attaching
the controller to the cabinet hardware. The three connectors are keyed circular MilSpec
Amphenol connectors, each with a different pin count. They are known, from left to right,
as Connectors A, B, and C, and they are described in the next three topics.
Port A Connector
Port A is a standard of the NEMA TS2 Type 2 controller specification. It is a circular
keyed male pin MilSpec connector with 55 pins in the following arrangement:
Figure 310 – Pin assignment, looking INTO the male Port A connector
These are the pin function assignments for the Port A connector when the controller is
operating in its default input/output mode (i.e. Mode 0). For details on switching to one of
the other input/output modes, refer to “Alternate Input/Output Mode Selection” on page
363.
Table 49 – Port A Pin Functions
Pin
Function
Description
A
Fault Monitor
Optional, used in TS 2-1 mode only
I/O
--
B
+24VDC
24 Volt D.C. output.
O
C
CVM
The Controller Voltage Monitoring signal is present here when
the controller is not in UCF Flash, no checksum failures are
present, and operating voltages are all good.
O
D
φ1 Red
Vehicle Phase 1 Red signal.
O
E
φ1 Don't Walk
Pedestrian Phase 1 Don't Walk signal.
O
F
φ2 Red
O
361
Pin
362
Function
Description
G
φ2 Don't Walk
I/O
O
H
φ2 Ped Clr
Pedestrian Phase 2 Ped Clearance signal.
O
J
φ2 Walk
Pedestrian Phase 2 Walk signal.
O
K
Detector 2
Puts call on phase assigned to detector 2 when activated.
I
L
Ped. Det. 2
Puts a ped call on phase 2 when activated.
I
M
φ2 Hold
When controller is not in CNA mode, activating this input inhibits
termination of Green service to vehicle Phase 1, and inhibits
concurrent ped. service recycle. When in CNA mode,
termination of Walk is inhibited.
I
N
Ring 1 Stop Time
Suspends all interval timing for ring 1.
I
P
Ring 1 Inhibit Max
Term
Prevents max termination of ring 1 vehicle phases when
extending.
I
R
External Start
Initiates start up sequence.
I
S
Interval Advance
Provides manual advance of controller sequencing. If MCE is
active, clearance intervals will be timed.
I
T
Ind. Lamp Control
LCD backlight control / Door Open event
U
AC Neutral
Common lead of AC supply
AC -
I
V
Chassis Ground
Chassis ground
Cgnd
W
Logic Ground
DC I/O logic ground reference
Lgnd
X
Flashing Logic
Alternating True/False output at 1 pulse per second, 50% duty
cycle.
Y
Ring 1 Status Bit C
Coded Status Bit C for ring 1.
O
Z
φ1 Yellow
Vehicle Phase 1 Yellow signal.
O
a
φ1 Ped Clr
O
b
φ2 Yellow
O
c
φ2 Green
Vehicle Phase 2 Green signal.
O
d
φ2 Check
Active when a call is present on phase 2 but unit is not in phase
2.
O
e
φ2 On
Active when phase 2 is in Green, Yellow, or Red Clearance.
O
f
Detector 1
I
g
Ped. Det. 1
I
h
φ1 Hold
See φ2 Hold description above
I
i
Ring 1 Force Off
Terminates Green service in ring 1 provided a conflicting call is
present and Walk or Ped Clearance are not timing.
I
O
j
Ext. Min Recall
Places all phases on min recall.
I
k
Manual Control Enable
Places termination of Green and Walk intervals under control of
the Interval Advance input and places calls on all phases.
Clearance intervals will time normally.
I
m
CNA 1
Activates CNA mode for the programmed phases. In this mode,
ped movements are recalled so that they are serviced with the
concurrent vehicle phase.
I
n
Test A
Can be used to activate UCF.
p
AC+
AC Supply Voltage
I
q
I/O Mode A
One of the three pins used to set the I/O Mode for a TS 2 Type
2 controller (Also A-z, and A-HH)
I
r
Ring 1 Status Bit B
Coded Status Bit B for Ring 1.
O
AC +
Pin
Function
Description
s
φ1 Green
I/O
O
t
φ1 Walk
O
u
φ1 Check
1.
O
v
φ2 Ped Omit
Prevents ped service on phase 2.
I
w
Ring 1 Omit Red
Clearance
Causes programmed red clearance timing for ring 1 vehicle
phases to be omitted.
I
x
Ring 1 Red Rest
Causes ring 1 phases to rest in red when no conflicting calls are
present.
I
y
I/O Mode B
See CNA 1 (pin m)
I
z
CNA 2
2 controller (Also A-q, and A-HH)
I
AA
Test B
Can be used to activate UCF
I
BB
Walk Rest Modifier
Modifies CNA operation. When active, CNA phases remain in
the timed out Walk state in the absence of a conflicting call
regardless of the Hold input.
I
CC
Ring 1 Status Bit A
Coded Status Bit A for Ring 1
O
DD
φ1 On
O
EE
φ1 Ped Omit
Prevents ped service on Phase 1
I
FF
Ring 1 Ped
Recycle
In CNA mode, if the phase has reached a green dwell state, and
the Ped Omit is not active, and a serviceable conflicting call
does not exist, the ped movement will be recycled if the input is
active.
In non-CNA mode, if a serviceable ped call exists and Hold is
active, the ped movement will be recycled when the input is
active regardless of conflicting calls.
I
GG
Ring 1 Max 2
Selects Max 2 timing instead of Max 1
I
HH
I/O Mode C
2 controller (Also A-q, and A-z)
I
Alternate Input/Output Mode Selection
A TS2 Type 2 controller can map the outputs on its A, B and C connectors in a number
of ways. Three of the pins on the Port A connector are used to define the input/output
mode that the controller will operate in. This mode selection is part of the standard for a
NEMA TS2 Type 2 controller. These modes determine which pin on the four cabinet
connectors are used for which function. As with all of these inputs and outputs, the
inputs used to set the mode follow the NEMA signal standard, i.e. TRUE = 0VDC and
FALSE = 24VDC.
Table 50 – To set the TS2/2 Input/Output Mode, set these inputs to these values:
I/O Mode
Description
Pin ‘q’ on Port A
Pin ‘z’ on Port A
Pin ‘HH’ on Port A
0
TS1 pin assignments
OFF
OFF
OFF
1
TS2 hardware
interoperability mode
ON
OFF
OFF
2
TS2 System mode
OFF
ON
OFF
6
Boston standard
OFF
ON
ON
7
D Module standard
ON
ON
ON
363
When the ATC-1000 controller is switched to one of the other Input/Output modes,
some, but not all, of the default pin function assignments on the Port A, B, and C
connectors are modified. These changes are listed in the next two tables. The ATC-1000
auto-recognizes each “D” module and self-activates Mode 7.
Table 51 – Cabinet Port Input Changes, by Mode
Pin
364
Input #
MODE 0 (TS 1)
MODE 1
MODE 2
MODE 7
Default
A-M
Input 2
Phase 2 Hold
Preempt 3
Preempt 3
A-h
Input 1
Phase 1 Hold
Preempt 1
Preempt 1
Default
A-v
Input 18
Phase 2 Ped Omit
Automatic (UCF)
Flash
Local Flash Status
Default
A-EE
Input 17
Phase 1 Ped Omit
Dimming Enable
Dimming Enable
Default
B-R
Input 11
Phase 3 Phase Omit
Timing Plan C
Veh Det 17
Default
B-S
Input 10
Phase 2 Phase Omit
Veh Det 12
Veh Det 12
Default
B-T
Input 21
Phase 5 Ped Omit
Offset 1
Address bit 2
Default
B-U
Input 9
Phase 1 Phase Omit
Veh Det 11
Veh Det 11
Default
B-g
Input 12
Phase 4 Phase Omit
Timing Plan D
Veh Det 18
Default
B-h
Input 4
Phase 4 Hold
Veh Det 10
Veh Det 10
Default
B-i
Input 3
Phase 3 Hold
Veh Det 9
Veh Det 9
Default
B-j
Input 19
Phase 3 Ped Omit
Timing Plan A
Address bit 0
Default
B-k
Input 22
Phase 6 Ped Omit
Offset 2
Address bit 3
Default
B-m
Input 23
Phase 7 Ped Omit
Offset 3
Address bit 4
Default
B-n
Input 24
Phase 8 Ped Omit
TBC On Line
MMU Flash Status
Default
B-x
Input 20
Phase 4 Ped Omit
Timing Plan B
Address bit 1
Default
C-X
Input 8
Phase 8 Hold
Veh Det 16
Veh Det 16
Default
C-m
Input 5
Phase 5 Hold
Veh Det 13
Veh Det 13
Default
C-n
Input 13
Phase 5 Phase Omit
Alternate sequence
A
Veh Det 19
Default
C-p
Input 6
Phase 6 Hold
Veh Det 14
Veh Det 14
Default
C-q
Input 14
Phase 6 Phase Omit
Alternate sequence
B
Veh Det 20
Default
C-r
Input 15
Phase 7 Phase Omit
Alternate sequence
C
Alarm 1
Default
C-s
Input 16
Phase 8 Phase Omit
Alternate sequence
D
Alarm 2
Default
C-EE
Input 7
Phase 7 Hold
Veh Det 15
Veh Det 15
Default
D-All
--
Inactive
Inactive
Inactive
Active
Table 52 – Cabinet Port Output Changes, by Mode
Pin
Output #
MODE 0 (TS 1)
MODE 1
MODE 2
MODE 7
A-d
Output 18
Phase 2 Phase Check
Automatic (UCF)
Flash Out
Automatic (UCF)
Flash Out
Default
A-e
Output 2
Phase 2 Phase ON
Preempt 3 Status
Preempt 3 Status
Default
A-u
Output 17
Phase 1 Phase Check
Free/Coord status
Free/Coord status
Default
A-DD
Output 1
Phase 1 Phase ON
Preempt 1 Status
Preempt 1 Status
Default
B-A
Output 9
Phase 1 Phase Next
Preempt 2 Status
Preempt 2 Status
Default
B-C
Output 10
Phase 2 Phase Next
Preempt 4 Status
Preempt 4 Status
Default
B-K
Output 20
Phase 4 Phase Check
Reserved
Reserved
Default
B-e
Output 4
Phase 4 Phase ON
TBC Aux 2 Out
TBC Aux 2 Out
Default
B-f
Output 12
Phase 4 Phase Next
Preempt 6 Status
Preempt 6 Status
Default
B-r
Output 19
Phase 3 Phase Check
TBC Aux 3 Out
TBC Aux 3 Out
Default
B-s
Output 3
Phase 3 Phase ON
TBC Aux 1 Out
TBC Aux 1 Out
Default
B-t
Output 11
Phase 3 Phase Next
Preempt 5 Status
Preempt 5 Status
Default
C-M
Output 13
Phase 5 Phase Next
Offset 3 Out
Offset 3 Out
Default
C-N
Output 5
Phase 5 Phase ON
Timing Plan A Output
Timing Plan A Output
Default
C-k
Output 21
Phase 5 Phase Check
Reserved
System Special
Function 1
Default
C-BB
Output 22
Phase 6 Phase Check
Reserved
System Special
Function 2
Default
C-CC
Output 6
Phase 6 Phase ON
Timing Plan B Output
Timing Plan B Output
Default
C-DD
Output 14
Phase 6 Phase Next
Timing Plan C Output
Timing Plan C Output
Default
C-FF
Output 24
Phase 8 Phase Check
Reserved
System Special
Function 4
Default
C-GG
Output 8
Phase 8 Phase ON
Offset 2 Out
Offset 2 Out
Default
C-HH
Output 16
Phase 8 Phase Next
Reserved
Reserved
Default
C-MM
Output 23
Phase 7 Phase Check
Reserved
System Special
Function 3
Default
C-NN
Output 7
Phase 7 Phase ON
Offset 1 Out
Offset 1 Out
Default
C-PP
Output 15
Phase 7 Phase Next
Timing Plan D Output
Timing Plan D Output
Default
D-All
--
Inactive
Inactive
Inactive
Active
365
Port B Connector
Port B is a standard of the NEMA TS2 Type 2 controller specification. It is a circular
keyed female socket MilSpec connector with 55 holes in the following arrangement:
Figure 311 – Pin assignment, looking INTO the female Port B connector
These are the pin function assignments for the Port B connector when the ATC-1000
controller is operating in its default input/output mode (i.e. Mode 0). For details on
switching to one of the other input/output modes, refer to “Alternate Input/Output Mode
Selection” on page 363.
Table 53 – Port B Pin Functions
Pin
366
Function
Description
A
φ1 Next
Active when phase 1 has been selected for next service.
I/O
B
Lead/Lag 1
Activates Phase Pair 4 in all Lead/Lag Patterns.
I
C
φ2 Next
O
D
φ3 Green
O
E
φ3 Yellow
O
F
φ3 Red
O
G
φ4 Red
O
H
φ4 Ped Clr
O
O
J
φ4 Don't Walk
O
K
φ4 Check
Active when a call is present on Phase 4 but unit is not in
Phase 4 green.
O
L
Detector 4
I
M
Ped. Det. 4
Puts a Ped call on phase assigned to ped detector 4 when
activated.
I
N
Detector 3
I
P
Ped. Det. 3
Puts a Ped call on phase assigned to ped detector 3 when
I
Pin
Function
Description
I/O
activated.
R
φ3 Omit
Prevents service on phase 3 when active.
I
S
φ2 Omit
I
T
φ5 Ped Omit
I
U
φ1 Omit
I
V
Ring 2 Ped
Recycle
In CNA mode, if the phase has reached a green dwell
state, and the Ped Omit is not active, and a serviceable
conflicting call does not exist, the ped movement will be
recycled if the input is active.
In non-CNA mode, if a serviceable ped call exists and
Hold is active, the ped movement will be recycled when
the input is active regardless of conflicting calls.
I
I
W
Lead/Lag 2
X
Lead/Lag 3
I
Y
φ3 Walk
Pedestrian Phase 3 Walk Signal.
O
Z
φ3 Ped Clr
Pedestrian Phase 3 Ped Clearance .signal.
O
a
φ3 Don’t Walk
O
b
φ4 Green
O
c
φ4 Yellow
O
d
φ4 Walk
O
e
φ4 On
Active when Phase 4 is in Green, Yellow, or Red
Clearance.
O
f
φ4 Next
O
g
φ4 Omit
I
h
φ4 Hold
When controller is not in CNA mode, activating this input
inhibits termination of Green service to vehicle phase 4,
and inhibits concurrent ped. service recycle. When in
CNA mode, termination of Walk is inhibited.
I
i
φ3 Hold
Same as φ4 Hold description above.
I
j
φ3 Ped Omit
I
I
k
φ6 Ped Omit
m
φ7 Ped Omit
I
n
φ8 Ped Omit
I
p
OLA Yellow
Vehicle Overlap A Yellow signal.
O
q
OLA Red
Vehicle Overlap A Red signal.
O
r
φ3 Check
Active when a call is present on phase 3 but unit is not in
phase 3.
O
s
φ3 On
Active when phase 3 is in Green, Yellow, or Red
Clearance.
O
t
φ3 Next
O
u
OLD Red
Vehicle Overlap D Red signal.
O
v
Lead/Lag 4
I
w
OLD Green
Vehicle Overlap D Green signal.
O
x
φ4 Ped Omit
I
y
Spare 5
Unused.
--
367
Pin
z
Function
Description
I/O
Ring 2 Max 2
Selects Max 2 timing instead of Max 1.
I
AA
OLA Green
Vehicle Overlap A Green signal.
O
O
BB
OLB Yellow
Vehicle Overlap B Yellow signal.
CC
OLB Red
Vehicle Overlap B Red signal.
O
DD
OLC Red
Vehicle Overlap C Red signal.
O
EE
OLD Yellow
Vehicle Overlap D Yellow signal.
O
FF
OLC Green
Vehicle Overlap C Green signal.
O
GG
OLB Green
Vehicle Overlap B Green signal.
O
HH
OLC Yellow
Vehicle Overlap C Yellow signal.
O
Port C Connector
Port C is a standard of the NEMA TS2 Type 2 controller specification. It is a circular
keyed female socket MilSpec connector with 61 holes in the following arrangement:
Figure 312 – Pin assignment, looking INTO the female Port C connector
These are the pin function assignments for the Port C connector when the ATC-1000
controller is operating in its default input/output mode (i.e. Mode 0). For details on
switching to one of the other input/output modes, refer to “Alternate Input/Output Mode
Selection” on page 363.
Table 54 – Port C Pin Functions
Pin
368
Function
Description
I/O
Pin
Function
Description
I/O
A
Ring 2 Status Bit A
Coded Status Bit A for Ring 2.
B
Ring 2 Status Bit B
Coded Status Bit B for Ring 2.
O
C
φ8 Don't Walk
O
D
φ8 Red
O
E
φ7 Yellow
O
O
O
F
φ7 Red
G
φ6 Red
O
H
φ5 Red
O
J
φ5 Yellow
O
O
K
φ5 Ped Clr
L
φ5 Don't Walk
O
M
φ5 Next
O
N
φ5 On
O
P
Detector 5
I
R
Ped. Det. 5
I
S
Detector 6
I
T
Ped. Det. 6
I
U
Ped. Det. 7
I
I
V
Detector 7
W
Ped. Det. 8
I
X
φ8 Hold
When controller is not in CNA mode, activating this input inhibits
termination of Green service to vehicle phase 8, and inhibits
concurrent ped. service recycle. When in CNA mode,
termination of Walk is inhibited.
I
Y
Ring 2 Force Off
Terminates Green service in ring 2 provided a conflicting call is
present and Walk or Ped Clearance are not timing.
I
I
Z
Ring 2 Stop Time
Suspends all interval timing for
a
Ring 2 Inhibit Max
Term
Prevents max termination of ring 2 vehicle phases when
extending.
ring 2.
b
Spare 1
Unused.
--
c
Ring 2 Status Bit C
Coded Status Bit C for Rng 2.
O
d
φ8 Walk
O
e
φ8 Yellow
O
f
φ7 Green
O
g
φ6 Green
O
I
h
φ6 Yellow
O
i
φ5 Green
O
j
φ5 Walk
O
k
φ5 Check
5 green.
O
m
φ5 Hold
Same as previous hold descriptions.
I
n
φ5 Omit
I
p
φ6 Hold
I
369
Pin
370
Function
Description
I/O
q
φ6 Omit
r
φ7 Omit
I
s
φ8 Omit
I
I
t
Detector 8
I
u
Ring 2 Red Rest
Causes ring 2 phases to rest in red when no conflicting calls are
present.
I
v
Ring 2 Omit Red
Clearance
Causes programmed red clearance timing for ring 2 vehicle
phases to be omitted.
I
w
φ8 Ped Clr
O
x
φ8 Green
O
y
φ7 Don't Walk
O
z
O
φ6 Don't Walk
AA
φ6 Ped Clr
O
BB
φ6 Check
6.
O
CC
φ6 On
Active when phase 6 is in Green. Yellow, or Red Clearance.
O
DD
φ6 Next
O
EE
φ7 Hold
I
FF
φ8 Check
8 green.
O
GG
φ8 On
O
HH
φ8 Next
O
JJ
φ7 Walk
O
KK
φ7 Ped Clr
O
LL
φ6 Walk
O
MM
φ7 Check
7.
O
NN
φ7 On
O
PP
φ7 Next
O
HMC-1000 I/O MODULE
The HMC-1000 I/O Module has a single round MIL-SPEC style connector with keys and
a switch for Stop Time input.
HMC Input / Output Connector
Figure 313 – HMC-1000 Input/Output Connector
Table 55 – HMC-1000 Input/Output Connector Pin Functions
Pin
Function
1
Output-21
2
Output-11
3
MAN-ADV
4
STOP-TIME
5
Output-24
6
OFFSET1
7
OFFSET3
8
Output-15
9
Preemption 2
10
Advance
11
Output-23
12
Restart
371
372
Pin
Function
13
Output-32
14
Offset 2
15
Output-16
16
Preemption 1
17
Output-25
18
Output-28
19
Spare 1
20
Spare 2
21
Output-7
22
Output-18
23
Output-21
24
Output-22
25
Dial 3
26
Dial 2
27
Output-1
28
Output-14
29
Output-4
30
Output-29
31
Output-27
32
Output-17
33
Output-9
34
Output-19
35
Dial-4
36
Online
37
Flash Bus
38
Manual
39
Output-30
40
Output-31
41
Output-12
42
Output-10
43
Output-2
44
Output-3
45
Output-13
46
Output-8
47
Output-26
48
0V
49
Input-16
50
Input-17
51
Output-5
52
Output-6
53
0V
54
0V
Pin
Function
55
Input-18
56
Input-19
57
Input-20
58
Input-21
59
24V External
60
Input-22
61
AC Live (120VAC Line Voltage)
62
AC-Neutral
63
AC Ground
Stop Time Switch
Use to set the value of the Stop Time reference channel.
373
LMD40 I/O MODULE
The LMD40 I/O Module has three round MIL-SPEC connectors: A, B, and D, and a 15
pin D-sub connector (C).
LMD40 Port A Connector
Figure 314 – LMD40 I/O Module - Port A
Table 56 – LMD40 Port A Pin Functions
Pin
A
B
C
D
E
F
G
H
J
K
L
M
N
P
R
374
Function
ACTUATION 3
+24V EXTERNAL
VOLTAGE MONITOR
ACTUATION 1
ACTUATION 2
PRE-EMPT 2
PRE-EMPT 1
INTERVAL ADVANCE
STOP TIME
MAN. CONTROL ENABLE
EXTERNAL CSO
SIGNAL PLAN 2
SIGNAL PLAN 3
SYSTEM CONT/AZ RESET
EXTERNAL START
Signal
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
Pin
S
T
U
V
W
X
Y
Z
a
b
c
d
e
f
g
h
i
j
k
m
n
p
q
r
s
t
u
v
w
x
y
z
AA
BB
CC
DD
EE
FF
GG
HH
Function
REMOTE FLASH (AC)
INTERCONNECT COM
AC- (COMMON)
CHASSIS GND
LOGICGND
OUTPUT 1
OUTPUT 2
OUTPUT 3
OUTPUT 4
OUTPUT 5
OUTPUT 6
OUTPUT 7
OUTPUT 8
OUTPUT 9
OUTPUT 10
OUTPUT 11
OUTPUT 12
OUTPUT 13
OUTPUT 14
OUTPUT 15
OUTPUT 16
AC+
OUTPUT 17
OUTPUT 18
OUTPUT 19
OUTPUT 20
OUTPUT 21
SPARE OUTPUT
SPARE OUTPUT
SPARE OUTPUT
CYCLE 2 (User Defined 2)
CYCLE 3 (User Defined 3)
SPLIT 2 (User Defined 4)
SPLIT 3 (User Defined 5)
OUTPUT 22
OUTPUT 23
OFFSET 1
OFFSET 2
OFFSET 3 (User Defined 1)
OUTPUT 24
Signal
115 VAC
115 VAC
AC
EARTH
DC REF.
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
115 VAC
DC
DC
DC
DC
DC
DC
DC
DC
115 VAC
115 VAC
115 VAC
115 VAC
DC
DC
115VAC
115VAC
115VAC
DC
375
LMD40 Port B Connector
Figure 315 – LMD40 I/O Module - Port B
Table 57 – LMD40 Port B Pin Functions
Pin
A
B
C
D
E
F
G
H
J
K
L
M
N
P
R
S
T
U
V
376
Function
Output 25
Output 25
Output 25
Output 25
Output 25
Output 25
Output 25
Output 25
Output 25
Output 25
Output 25
Output 25
Output 25
Output 25
Output 25
Output 25
Actuation 4
Hold
Force-Off
Signal
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
LMD40 Communication Inputs Connector
Figure 316 – LMD40 I/O Module – Communication Inputs Connector
Table 58 – LMD40 Communication Inputs Connector
Pin
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
Function
Vehicle Detector 17
Vehicle Detector 18
Vehicle Detector 19
Vehicle Detector 20
Vehicle Detector 21
Vehicle Detector 22
Vehicle Detector 23
Vehicle Detector 24
Monitor Status B
Monitor Status A
Monitor Status C
User Defined 1
Ground – Logic
User Defined 2
User Defined 3
Signal
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
DC
Input and Output pin functions are defined within the ATC controller by the I/O Map. The
I/O Map has the ability to be mapped to custom input and output locations. (See “I/O
Mapping ”, starting on page 95.)
377
LMD Port D Connector
Figure 317 – LMD I/O Module - Port D
On the LMD 40, LMD 9200, and the 3000E controllers, this connector was included on a
separate D Module. Although the port operates in the exact same way as the D port on
those earlier controller, the Peek ATC versions of the LMD D port has been included as
a standard connector on the basic LMD40 I/O Module, so no separate ‘D Module’ for the
ATC is required to fully support LMD40 cabinets.
Table 59 – LMD Port D Pin Functions
378
Pin
Function
Description
I/O
Level
1
UCF Flash
Calls for UCF flash
opto-I
See note
opto-I
See note
com
See note
I
0 VDC
See note
2
Ofst 1/alarm 8 in
Offset 1 in or alarm 8 if not interconnect mode
3
Inter. common
Common ref. for opto inputs
4
Enable excl. ped
Enables exclusive ped operation
5
Ofst 2/alarm 7 in
opto-I
6
Ofst 3/alarm 6 in
opto-I
See note
7
Cycle 2/alarm 1 in
Cycle 2 in or alarm 1 if not interconnect mode
opto-I
See note
8
Group 2 switching
Activates group 2 detector switching
I
0 VDC
9
Spare
Spare
I
0 VDC
10
Call to Free
Calls to free operation for all coord select modes
I
0 VDC
11
Det input 31
Activates Detector input 31
I
0 VDC
12
Cycle 3/alarm 2 in
Cycle 3 in or alarm 2 if not interconnect mode
opto-I
See note
Pin
Function
Description
I/O
Level
13
Split 2/alarm 5 in
Split 2 in or alarm 5 if not interconnect mode
opto-I
See note
14
Split 3/alarm 3 in
Split 3 in or alarm 3 if not interconnect mode
opto-I
See note
15
Det input 25
Detector input 25
I
0 VDC
16
Det input 27
Detector input 27
I
0 VDC
17
Det input 28
Detector input 28
I
0 VDC
18
Dimming
Calls for signal dimming operation
I
0 VDC
19
Dual Entry
Calls for dual entry operation
20
System/alarm 4 in
System in or alarm 4 if not interconnect mode
21
Det input 29
22
Det input 30
23
I
0 VDC
opto-I
See note
Detector input 29
I
0 VDC
Detector input 30
I
0 VDC
Det input 32
Detector input 32
I
0 VDC
24
Det input 13
Detector input 13
I
0 VDC
25
26
Det input 9
Det input 10
Detector input 9
Detector input 10
I
I
0 VDC
0 VDC
0 VDC
27
Ped. Det. 9
Puts a ped call on phase 9 when activated
I
28
Not Used
No Wire
--
--
29
Det input 12
Detector input 12
I
0 VDC
30
Det input 14
Detector input 14
I
0 VDC
31
Det input 15
Detector input 15
I
0 VDC
32
Det input 16
Detector input 16
I
0 VDC
33
Cond. Service
Activates Conditional Service when programmed to
activate by input
I
0 VDC
34
Preempt 5 input
Activates preempt 5 run
I
0 VDC
35
Preempt 1 output
Activated by preempt programming
O
0 VDC
36
Preempt 2 output
O
0 VDC
37
Interconnect Inhib.
Inhibits interconnect, calls TBC
I
0 VDC
38
Time Clock Sync
Sets clock to preset time of day
I
0 VDC
39
Det input 26
Detector input 26
I
0 VDC
40
Preempt 1 input
I
0 VDC
41
Preempt 2 input
I
0 VDC
42
Preempt 3 input
I
0 VDC
43
Preempt 3 output
O
0 VDC
44
Not Used
No Wire
--
--
45
Preempt 4 output
O
0 VDC
46
Preempt 5 output
O
0 VDC
47
System output
Active when coordination achieved
O
0 VDC
48
PE 6/Flash output
Preempt 6 out or remote flash achieved
O
0 VDC
49
Preempt 4 input
I
0 VDC
50
User 1 out
User defined output 1
O
0 VDC
51
User 2 out
O
0 VDC
52
User 3 out
O
0 VDC
53
Spare
Spare
O
0 VDC
54
User 4 out
O
0 VDC
55
Ckt 8 (Flash) out
Clock Ckt 8 output
O
0 VDC
379
Pin
Function
Description
I/O
Level
56
Ckt 3 (Ofst 1) out
Clock Ckt 3 output
O
0 VDC
57
Ckt 4 (Ofst 2) out
Clock Ckt 4 output
O
0 VDC
58
Ckt 5 (Ofst 3) out
Clock Ckt 5 output
O
0 VDC
59
Ckt 1 (Cyc 2) out
Clock Ckt 1 output
O
0 VDC
60
Ckt 2 (Cyc 3) out
Clock Ckt 2 output
O
0 VDC
61
Ckt 6 (Splt 2) out
Clock Ckt 6 output
O
0 VDC
62
Ckt 7 (Splt 3) out
Clock Ckt 7 output
O
0 VDC
63
Preempt 6 input
I
0 VDC
NOTE : Pins designated as “opto-I” indicate an opto-isolated input. If Inter. common is
tied to 24V, then the input is Logic Ground = True (NEMA input) and the input function is
not interconnect mode. If Int. common is tied to AC-, then the input is 115VAC = True
and the input function is interconnect mode. External resistors must be externally
provided to reduce AC voltage.
380
CLOSED LOOP D MODULE
As with the inputs and outputs on the other cabinet connectors, the inputs and outputs
on the D connectors follow the NEMA signal standard, i.e. TRUE = 0VDC and FALSE =
24VDC. There are two connectors on the Closed Loop D Module, a 26 pin MS connector
and a DB25 pin male connector.
Auxiliary Connector (37 Pin)
Pin
Function
Description
I/O
1
User Defined 5
Preempt Output #3
O
2
User Defined 4
User Defined Output #4
O
3
User Defined 3
User Defined Output #3
4
Flash Status
Input to denote cabinet is in manual flash
O
5
Offset 3 Out
Offset 3 Interconnect Output
6
Monitor Status
Input to denote cabinet is in Monitor Flash
opto-I
7
Optical Input 3
Not currently used
opto-I
8
Offset 1 In
Alarm 8
Offset 1 Interconnect Input
Alarm Input 8
opto-I
9
Offset 3 In
Alarm 6
Alarm Input 6
opto-I
10
Cycle 2 In
Alarm 1
Cycle 2 Interconnect Input
Alarm Input 1
opto-I
11
Offset 2 In
Alarm 7
Alarm Input 7
opto-I
12
Cycle 4/Split 2 In
Alarm 5
Cycle 4 or Split 2 Interconnect Input
Alarm Input 5
opto-I
13
Cycle 3 In
Alarm 2
Cycle 3 Interconnect Input
Alarm Input 2
opto-I
14
Optocom 1
Common for Optical Inputs 8-16 on this connector.
Opto
com
15
Split 2/Split 3 In
Alarm 3
Split 2/Split 3 Interconnect Input
Alarm Input 3
opto-I
16
Free Input
Alarm 4
Free Interconnect Input
Alarm Input 4
opto-I
17
+24 V
24 VDC Output
+24V
18
Ground
Logic Ground
Lgnd
19
N/U
Not Used
--
20
User Defined 6
Preempt Output #4
O
21
User Defined 7
Preempt Output #5
O
O
opto-I
O
22
User Defined 8
Preempt Output #6
23
N/U
Not Used
--
24
Offset 1 Out
O
381
Pin
Function
Description
I/O
25
Free Out
Free Interconnect Output
26
Optocom 2
Common for Optical Inputs 4, 6, 28, 29, 35, 36 on
this connector and Optical Inputs B, P, R, T, W, & X
on Coord Connector.
O
27
Optical Input 4
Not currently used
--
28
Detector 29
Detector 29 Input
opto-I
29
Detector 30
Detector 30 Input
opto-I
30
Flash Out
Flash Interconnect Output
31
Offset 2 Out
O
32
Cycle 2 Out
Cycle 2 Interconnect Output
O
33
Cycle 4/Split 2 Out
Cycle 4/Split 2 Interconnect Output
O
Opto
com
O
34
Cycle 3 Out
Cycle 3 Interconnect Output
35
Detector 31
Detector 31 Input
opto-I
O
36
Detector 32
Detector 32 Input
opto-I
37
User Defined 2
User Defined Output 2
O
Preemption Connector (25 Pin)
Pin
382
Function
Description
1
Preempt 1 In
Activates Preempt Run 1
I/O
I
2
Preempt 2 In
I
3
Preempt 3 In
I
4
Preempt 4 In
I
5
Preempt 5 In
I
6
Detector 9
Detector 9 Input
I
7
Detector 10
Detector 10 Input
I
8
Detector 11
Detector 11 Input
I
9
Detector 12
Detector 12 Input
I
10
Detector 13
Detector 13 Input
I
11
Detector 14
Detector 14 Input
I
12
Detector 15
Detector 15 Input
I
13
Detector 16
Detector 16 Input
I
14
UCF
Activates Uniform Code Flash
I
15
Cabinet Flash
Input to denote cabinet is in manual flash
I
16
RTC Reset
Resets the Real-Time Clock to a programmed time.
I
17
Preempt 6 In
I
18
Dimming
Activates loadswitch dimming if enabled in the
controller.
I
19
Free Override
Forces the controller to operate in Free mode.
I
Pin
Function
Description
I/O
20
TOD Override
Forces the controller to operate in time-based
coordination mode.
21
Preempt Out 2
User programmable output for preemption
O
22
User Def. Out 1
User defined TOD Output 1
O
23
Preempt Out 1
User programmable output for preemption
O
24
Xped
Enables Exclusive Pedestrian Operation
I
25
Group 2
Activates Group 2 Detector Switching and Dynamic
Omits & Recalls
I
I
Coordination Connector (26 Pin)
Pin
Function
Description
A
Detector 17
Detector 17 Input
I/O
I
B
Detector 32
Detector 32 Input
opto-I
C
RX+
Transceiver Pos. Input
D
RX-
Transceiver Neg. Input
I
E
TX+
Transceiver Pos. Output
O
O
I
F
TX-
Transceiver Neg. Output
G
Detector 28
Detector 28 Input
I
H
Detector 27
Detector 27 Input
I
J
Detector 26
Detector 26 Input
I
K
Detector 25
Detector 25 Input
I
L
Detector 24
Detector 24 Input
I
M
Detector 23
Detector 23 Input
I
N
Optocom2
Common for Optical Inputs 4, 6, 28, 29, 35, 36 on
Aux connector and Optical Inputs B, P, R, T, W, & X
on Coord Connector.
opto
com
P
Monitor Status
Active if in Monitor Flash
opto-I
R
Flash Monitor
Active when cabinet is in flash
opto-I
S
Detector 18
Detector 18 Input
I
T
Detector 31
Detector 31 Input
opto-I
U
RX Shield
Shield for Transceiver Input
V
TX Shield
Shield for Transceiver Output
--
W
Detector 30
Detector 30 Input
opto-I
--
X
Detector 29
Detector 29 Input
opto-I
Y
Detector 22
Detector 22 Input
I
Z
Detector 21
Detector 21 Input
I
a
Detector 20
Detector 20 Input
I
b
Detector 19
Detector 19 Input
I
c
N/U
Not Used
--
383
LMD9200 D MODULE
Aux Connector
Pin
Function
E-01
Vehicle Detector 17
E-02
Vehicle Detector 18
E-03
Vehicle Detector 19
E-04
Vehicle Detector 20
E-05
Vehicle Detector 21
E-06
Vehicle Detector 22
E-07
Vehicle Detector 23
E-08
Vehicle Detector 24
E-09
Monitor Status B
E-10
Monitor Status A
E-11
Monitor Status C
E-12
User Defined 1
E-14
User Defined 2
E-15
User Defined 3
D Connector
Pin
Code
Function
1
IN8
Usf Flash (Opto)
2
IN5
Ofst 1/Alarm 8 In (Opto)
3
384
Inter Common (Opto Common)
4
IN36
Enable Excl
5
IN3
6
IN6
7
IN1
Cycle 2/Alarm 1 In (Opto)
8
IN22
Group 2 Switching
9
IN25
Spare
10
IN15
Call To Free
11
IN17
Det Input 31
12
IN7
Cycle 3/Alarm 2 In (Opto)
13
IN9
Split 2/Alarm 5 In (Opto)
14
IN4
Split 3/Alarm 3 In (Opto)
15
IN26
Det Input 25
Pin
Code
Function
16
IN21
Det Input 27
17
IN38
Det Input 28
18
IN35
Dimming
19
IN39
Dual Entry
20
IN2
System Alarm 4 In (Opto)
21
IN30
Det Input 29
22
IN32
Det Input 30
23
IN34
Det Input 32
24
IN19
Det Input 13
25
IN13
Det Input 9
26
IN31
Det Input 10
27
IN37
Ped Det 9
29
IN28
Det Input 12
30
IN20
Det Input 14
31
IN18
Det Input 15
32
IN40
Det Input 16
28
(Not Used)
33
IN12
Det Input Cond Service
34
IN29
Preempt 5 Input
35
OUT18
Preempt 1 Output
36
OUT20
Preempt 2 Output
37
IN16
Interconnect Inhib
38
IN14
Time Clock Sync
39
IN10
Det Input 26
40
IN24
Preempt 1 Input
41
IN11
Preempt 2 Input
42
IN27
Preempt 3 Input
43
OUT16
44
Preempt 3 Output
(Not Used)
45
OUT2
Preempt 4 Output
46
OUT4
Preempt 5 Output
47
OUT6
System Output
48
OUT10
49
IN23
50
OUT11
User 1 Out
51
OUT15
User 2 Out
52
OUT19
User 3 Out
53
OUT8
Spare
Pe 6/Flash Output
Preempt 4 Input
385
Pin
Code
Function
54
OUT12
User 4 Out
55
OUT3
Ckt 8 (Flash) Out
56
OUT5
Ckt 3 (Ofst1) Out
57
OUT9
Ckt 4 (Ofst2) Out
58
OUT13
Ckt 5 (Ofst3) Out
59
OUT17
Ckt 1 (Cyc 2) Out
60
OUT1
Ckt 2 (Cyc 3) Out
61
OUT14
Ckt 6 (Split2) Out
62
OUT7
Ckt 7 (Split3) Out
63
IN33
Preempt 6 Input
TRACONEX D MODULE
63 pin circular MilSpec connector
386
Pin
Code
Function
1
OUT3
EMERG PR 4 OUT
2
OUT4
3
IN7
OFFSET 4 (ADD BIT 3)
4
IN3
ONLINE
5
OUT8
SPARE
6
IN19
DIAL (CYCLE PLAN) 4
7
IN15
DIAL (CYCLE PLAN) 6
8
OUT6
SPEC FUNCT 2
OFFSET 3 OUT
9
IN5
SPLIT 3
10
IN16
11
OUT1
FLASH OUT
12
IN27
13
IN24
SYST DET 8
14
IN22
DIAL (CYCLE PLAN) 5
15
OUT5
SPEC FUNCT 3
16
IN20
SPLIT 2
17
IN14
SYST DET 1 <SEQ 1>
18
IN10
SYST DET 4 <SEQ 4>
19
IN8
SYSTEM ENABLE
20
IN31
DIMMING
21
OUT11
SPLIT 2 OUT
Pin
Code
Function
22
OUT9
EMERG PR 2 OUT
23
OUT10
RAILROAD PR OUT
24
OUT7
SPARE
25
IN12
DIAL (CYCLE PLAN) 2 (SPEC FUNCT 2)
26
IN6
FREE/COORD (SPEC FUNCT 1)
27
OUT2
FREE/COORD OUT
28
OUT13
SPEC FUNCT 1
29
OUT14
DIAL (CYCLE PLAN) 4 OUT
30
IN23
SYST DET 5
31
IN21
SYST DET 3 <SEQ 3>
32
OUT12
EMERG PR 1 OUT
33
OUT16
OFFSET 1 OUT
34
OUT21
EMERG PR 4 OUT
35
IN4
DIAL (CYCLE PLAN) 3 (SPEC FUNCT 3)
36
IN2
37
IN28
FLASH STATUS
38
IN26
39
IN29
SYST DET 6
40
IN17
SYST DET 7
41
OUT15
OFFSET 4 OUT
42
OUT18
OFFSET 2 OUT
43
OUT17
44
OUT23
45
OUT20
OFFSET 5 OUT
46
OUT19
SPLIT 3 OUT
47
IN30
48
SYST DET 2 <SEQ 2>
LOGIC GND
49
IN11
EMERG PREEMPT 1
50
IN1
EMERG PREEMPT 2
51
OUT22
52
OUT24
53
LOGIC GND
54
LOGIC GND
55
IN25
56
IN13
EMERG PREEMPT 4
57
IN9
RAILROAD PREEMPT
58
IN18
CONFLICT
59
EMERG PREEMPT 3
RESERVED
387
Pin
Code
Function
60
IN32
MUTCD FLASH
61
RESERVED
62
RESERVED
63
CHASSIS GND
NOTES:
1.
WITH 'SYSTEM ENABLE' (PIN 19) GROUNDED, FREE/COORD, DIAL (CYCLE
PLAN) 2 AND 3 ARE USED AS SPECIAL FUNCTION INPUTS 1, 2 AND 3
RESPECTIVELY
2.
WITH 'SYSTEM ENABLE' (PIN 19) GROUNDED, OFFSETS 1 TO 5 ARE USED
AS ADDRESS LINES
3.
WITH SQE=2, SYST. DET 1 TO 4 ARE USED AS SEQ 1 TO 4 RESPECTIVELY
MULTISONICS D MODULE
Pin
I/O
A
IN1
Function
SPECIAL FUNCTION IN 4
B
IN2
PREEMPT 5
C
OUT1
PREEMPT INTERVAL 1
D
OUT2
PREEMPT INTERVAL 2
E
OUT3
PREEMPT INTERVAL 3
F
OUT4
PREEMPT INTERVAL 4
G
OUT5
PREEMPT INTERVAL 5
H
OUT6
PREEMPT INTERVAL 6
J
OUT7
PREEMPT INTERVAL 7
K
OUT8
PREEMPT 5
L
388
AC OPTO COMMON
M
IN24>
AC CABINET FLASH
N
OUT9
UCF SOFT FLASH
P
IN3
R
IN25 or OUT21
S
OUT10
LOCAL SPECIAL FUNCTION 1 / LOW
PRIORITY PREEMPT PLAN 1 RIGHT-OFWAY
T
OUT11
U
OUT12
PRIORITY PREEMPT PLAN 3 RIGHT-OF-
HARDWIRE SYSTEM
Pin
I/O
Function
V
OUT13
W
OUT14
OSAM SPECIAL FUNCTION 1 / LOW
X
OUT15
Y
IN4
Z
IN5
WAY
OSAM SPECIAL FUNCTION 2 OUT
a
IN6
PREEMPT 1 IN
b
IN7
PREEMPT 2 IN
c
IN8
PREEMP 3 IN
d
IN9
PREEMPT 4 IN
e
IN10
NO COOR IN
f
IN26 or OUT22
HARDWIRE SPLIT 2
g
IN27 or OUT23
HARDWIRE SPLIT 3
h
OUT16
SYSTEM COOR OUT
j
OUT17
PREEMPT 1 OUT
k
OUT18
PREEMPT 2 OUT
m
OUT19
PREEMPT 3 OUT
n
OUT20
p
IN11
i
<LOGIC GROUND>
PREEMPT 4 OUT
UCF FLASH IN
q
IN26 or OUT 24
r
IN27 or *OUT25
HW FLASH
HW OFFSET 1
s
IN28 or *OUT26
HW OFFSET 2
t
IN29 or *OUT27
HW OFFSET 3
u
IN30 or *OUT28
HW DIAL 2
v
IN31 or *OUT29
w
IN12
x
IN13
y
IN14
CABINET DOOR OPEN MONITOR
z
IN24
D CABINET FLASH
AA
IN15
SYSTEM DET 1
HW DIAL 3
BB
IN16
SYSTEM DET 2
CC
IN17
SYSTEM DET 3
DD
IN18
SYSTEM DET 4
EE
IN19
SYSTEM DET 5
389
Pin
I/O
Function
FF
IN20
SYSTEM DET 6
GG
IN21
SYSTEM DET 7
HH
IN22
SYSTEM DET 8
JJ
IN23
KK
EXTERNAL RE-SYNC IN
<EXTERNAL 24VDC OUT>
LL
TX-
TELEMETRY COMMS
MM
TX+
TELEMETRY COMMS
NN
RX-
TELEMETRY COMMS
PP
RX+
TELEMETRY COMMS
*OUTx PINS ARE ON SEPARATE I2C DEVICE
Note: IN24 Cabinet Flash input is selectable as AC Input (Pin M) Or DC Input (Pin Z) by
jumper J3
390
Glossary
Glossary
3000E — A traffic controller produced by Peek Traffic Corporation.
AC — Alternating Current
Actuated — Identifies a type of controller which responds to calling signals generated by the
actions of either vehicles or pedestrians. See also Semi-actuated and Fully-actuated.
Adaptive Split Control — A means of intersection split selection based on vehicular activity.
ADC — Analog-to-Digital Converter
ACD, Advance Call Detector — A detector located a considerable distance upstream from an
intersection which calls the green to that approach.
AW, Advance Warning — A per-movement output used to give advance notice of an upcoming
yellow or red indication. Typically used at hidden intersections with “prepare to stop” indicators.
ASCII — American standard code of information interchange. A standard code that assigns eightbit codes to individual alphanumeric characters.
ASTC — Advanced Solid State Traffic Controller: the name given to a controller design specified by
New York City DOT. This acronym was chosen to distinguish it from the more general ATC
standards development program. The ATC-1000 controller is an ASTC controller.
ATC — Advanced Traffic Controller, a design developed per the ATC standards development
program of the State of California and the Federal Highway Administration. Requires the controller
to have a separate engine board and run the Linux operating system. The ATC-1000 controller is
not an ATC controller.
Auto/Manual Switch — A cabinet switch, when operated, discontinues normal signal operation
and permits manual operation.
AWG — American Wire Gauge – used to identify wire thickness
Backplane — A printed circuit connector interface board, typically with no active or passive
components. However, the use of passive components is accepted for most applications.
Back Panel — A board within the controller cabinet upon which are mounted field terminals, fuse
receptacles or circuit breakers, and other components of controller operation not included in the
controller unit itself, or its ancillary devices. Such back panels are typical in older traffic control
cabinets.
Barrier — A logical term to describe a line of compatibility in a multi-ring signal plan in which all
rings are interlocked. Barriers assure that there will be no concurrent selection and timing of
conflicting phases for traffic phases on different rings.
Baud rate — The data transfer rate of data transmission to a communications channel, usually
expressed in ‘bits per second’.
BIU — Bus Interface Unit, required to interface a TS-2, Type 1 controller to any type of cabinet
hardware. Converts NEMA TS2-Type 1 EIA/TIA-485 Serial Data to cabinet discrete inputs and
outputs.
391
Glossary
BPS — Bits Per Second - a measure of data transmission speed
Buffer — A temporary storage location for data. The buffer accumulates backed-up information for
later release. A device or section of memory used to compensate for differences in data transfer
flow speeds or variable latencies in a communications channel.
CA — Controller Assembly
Cabinet — An outdoor enclosure for housing controller units, master units, detector electronics and
other associated equipment.
Call — The result of a detector or signal activation by either a pedestrian or a vehicle. A signal to
the controller indicating that a vehicle or pedestrian is present and is ‘requesting’ the right-of-way.
Capacity — The maximum number of vehicles that can pass over a given lane or roadway during a
given period, under prevailing traffic conditions.
CBD — Central business district. The portion of a municipality in which the dominant land use is
intense business activity.
CH, CHAN, Channel — An information path from a discrete input to a discrete output.
Checksum — A numerical value that is calculated by applying a predefined algorithm to a set of
data. It is used to determine if a portion of memory or a message has been corrupted in any way.
CIC — Critical Intersection Control
Clearance Interval — The interval from the end of the right-of-way of one phase to the beginning
of a conflicting phase.
Closed-Loop System — A software and hardware system in which a computer controls an
external process using information received from the process. For example, the closed loop in a
traffic control system is from the computer to the controllers and then from the detectors back
(through the controller) to the computer.
CLR — Phase Clearance. Includes Ped Clearance times for CNA phases.
CMU/MMU — Conflict Monitor Unit – Also known as MMU (Multifunction Management Unit). This
device monitors the green, yellow, and red AC loadswitch outputs for conflicts, the absence of a
proper red signal and the watchdog signal from the controller. Any real and potential unsafe
condition will force the cabinet into flash.
CMOS — Complementary Metal Oxide Semiconductor – a type of integrated circuit chip used on
electronic boards.
CNA — Call to Non-Actuated. Provides a method of phase timing where vehicle and pedestrian
detectors are not required to serve the associated phases, with operation as defined by NEMA. An
actuated controller feature in which the associated phase will always serve the Walk plus Ped Clear
time, regardless of detector inputs.
Compatibility Line — The dividing line crossing both rings (in dual ring operation) that separates
compatible phase combinations. Usually, it divides phases associated with North/South from those
associated with East/West. Also known as the Barrier.
Conditional Service — A dual-ring feature which allows re-service to an odd phase (i.e. a left turn
phase) once the opposite ‘through’ phase has gapped out. The service is conditional upon the time
remaining in the adjacent ‘through’ phase’s Max timer.
Conflict Monitor — A device used to continually check for the presence of conflicting signal
indications coming from the controller, and to provide an output in response to the conflict (usually
All Flash).
392
Glossary
Conflicting Phases — Two or more traffic flows which would result in interfering traffic
movements if operated concurrently.
Controller — A device which, through software and firmware programming, manages the
sequence and duration of traffic signals.
CRD, COORD — Coordination
Coordination — The state where two or more intersections are configured to communicate with
each other in order to time their signals in some manner that improves the greater system
performance, rather than being timed independently at each intersection. This independent
operation, by contrast, is known as Free operation.
COTS — Commercial off the Shelf – standard product offering available for purchase from
commercial vendors.
CPU — Central Processing Unit - The chip that controls all computer operations and performs
computations. Also may refer to the entire physical unit housing the chip.
CRC — Cyclic Redundancy Check
Critical Intersection — A selected, heavily traveled intersection within a coordinated traffic artery.
This intersection would be employed to dynamically control the split at other intersections within the
artery, based on its vehicle detector inputs.
controller — Controller Unit, another term used to describe the overall traffic controller unit.
CU — Controller unit, in some standards documents, notably those from the States of California
and New York in the United States, traffic controllers are often refered to by this two-letter acronym.
Occasionally, this abbreviation sneaks into the documentation from Peek.
CVM — Controller voltage monitor. An open collector output that is maintained ‘low’ by the
controller as long as the internally generated operating voltages are within tolerances. This output is
used by a conflict monitor to place the intersection in Flash, should all voltages fail in the controller.
Cycle — The total time required to complete one complete set of signal states around an
intersection. In basic, pre-timed control, the cycle length is fixed. In actuated systems the cycle
length can be increased up to a predetermined maximum, based on the continued detection of
vehicles.
Cycle Zero Point — See ‘Time Reference Point’
Database — Traffic controllers and central system software typically uses two distinctly different
meanings for the term ‘database’. The first is the typical one used in most computer systems: a
central system stores and maintains all of the information it gathers from the field about all
connected controllers in a set of database files on the central computer. The second meaning of
database is the complete set of operating parameters stored in a single controller or master
controller.
Density — A measure of the concentration of vehicles in an intersection, stated as the number of
vehicles per mile (space density) or as the flow volume divided by the average speed (point
density.)
Detection Zone — The area of the roadway in which a vehicle will be detected by a vehicle
detector.
Detector — A device that senses the presence or absence of a vehicle in a particular area (the
Detection Zone). Vehicle detection methods include inductance detecting loops (the most common
type), piezo pressure sensors, light beam sensors, radio ID sensors, air tube sensors, and
mechanical switches.
393
Glossary
Detector Failure — A detector which fails to indicate that vehicle is present when it is, or fails to
go off when a vehicle is absent. Types of failures include non-operation, chattering, and erroneous
signaling.
Detector Memory — A feature of some controllers in which the actuation of a detector is retained
in memory until the corresponding phase is serviced.
Dimming — This feature of some controllers allows the brightness of selected traffic signal
indicators to be lowered during night time operation, typically by lowering the voltage applied to the
output.
DLL — A dynamically linked library file. In the Windows environment, programs store data,
graphics, and other resources in these linked libraries. CLMATS, TOPS, Z-Link and most other
Windows applications use them.
Dual Entry — A mode of dual-ring operation in which one phase in each ring must be in service. If
a Call does not exist in a ring when the controller crosses the barrier to activate a phase within the
ring, a phase is selected in that ring to be activated in a predetermined manner.
Duplex — Two-way communications over a single communications link.
EPROM — Erasable Programmable Read–Only Memory (typically using UV light to erase)
EEPROM — Electronically erasable/programmable read-only memory, the programmable memory
storage area in many traffic control components.
EGB — Extended Green Band
EP — End of Permissive
EPP — End of Pedestrian Permissive
EVP — Emergency Vehicle Preemption. Occasionally used by state and municipal agencies to
describe the basic intersection preemption capability.
Flash memory — Flash memory is a type of nonvolatile memory. The data stored in flash will be
saved during long periods of power outage. It is a variation of electrically erasable programmable
read-only memory.
FO — Force Off
FOM — Fiber Optic Modem, a device that modulates a signal appropriately for transmission over
fiber optic cables
Force Off — Action taken by an external source which generates a signal to the intersection
controller, causing termination to begin in the phase currently exhibiting the right-of-way. Used in
Preemption and Coordinated operation.
FSK — Frequency shift key, A form of digital frequency modulation employing discrete frequencies
for specific signals, for example for marking signals. The transmitter is changed from one
frequency to another, keyed to represent a different information character with each frequency.
Fully-actuated — Identifies a type of intersection control in which every phase has a vehicle
detector input capability
Gap Out — This is what occurs when the passage timer (the Green portion of a phase-based
intersection) does not get extended because the gap between sequential vehicles of sufficient
length has occurred.
Green Band — The time, in seconds, elapsed between the passing of the first vehicle and the last
possible vehicle in a group of vehicles moving in accordance with the designed speed of a
progressive traffic control system.
394
Glossary
Greenband Analysis — a method of analyzing the amount of green light time available in a set of
coordinated traffic intersections.
Hz — Hertz, a unit of frequency indicating cycles per second
INIT — Initial or Initialization
Intersection — The location where two roadways meet or cross, or a Controller assigned to such a
location.
INT — Interval
Interval — A unit of time that is assigned a certain of controller behavior and signal output in a
time-based (non-NEMA) controller.
ITS — Intelligent transportation systems
Jumper — A means of connecting/disconnecting two or more conductive points by soldering/desoldering a conductive wire or a removable short.
10
kb — One thousand bytes (actually 2 or 1,024 bytes). Computer RAM memories are usually
defined in terms of kilobytes. Thus when a computer has 128K of memory, it has 131,072 bytes of
memory.
LCD — Liquid Crystal Display – used for alphanumeric displays; very low power consumption,
which operates using reflective or transmission properties of display material.
Lead/Lag Operation — A feature of some traffic controllers which makes it possible to reverse the
phase sequence on a phase-pair basis. When the phase pairs (such as 1-2, 3-4, 5-6, 7-8) are
reversed, the odd phase will lag the even phase instead of leading it as it does in normal operation.
LED — Light Emitting Diode - low-power colored lights
Local — Connection to a Controller unit
M3000 — The model number of a master unit manufactured by Peek Traffic Corporation. Often
used in conjunction with Peeks’ Series 3000 and 3000E Traffic Controllers
MAC Address — The unique numerical identifier for a physical device that is attached to the
Internet. Stands for ‘Media Access Control’ Address.
MAX — Maximum time
20
MB — One million bytes (actually 2 or 1,048,576 bytes). Used to define a large volume of data.
Hard disk storage capacity is measured in megabytes.
MCE — Manual Control Enable
MIN — Minimum (usually time)
MMU — Malfunction Management Unit
Module — A functional unit that plugs into an assembly
MOE — Methods of efficiency
ms — Milliseconds
MSB — Most significant bit / byte
MSCLR — Main Street Clearance
MTBF — Mean time between failures
MTTR — Mean time to repair
395
Glossary
MUTCD — The MUTCD is the Manual on Uniform Traffic Control Devices, written by and
maintained by the U.S. Federal Highway Administration. The MUTCD is the oldest baseline source
for the definition of how in-road flashing beacons should function in the United States.
n/a, N/A — Not assigned; not available; not applicable.
N/C — Not connected
NEMA — National Electrical Manufacturers Association. The industry group that has designed one
of a couple of competing standards for intelligent traffic control systems.
NASCAR — The National Association of Stock Car Auto Racing
NTCIP — The National Transportation Communications for ITS Protocol. The NTCIP protocol
conforms to NEMA TS2-1998, Section 3.3.6.
OID — Object Identifier. A way to identify a unique piece of information within a device that uses
the SNMP protocol for data management and communications, or that uses its more pertinent
descendant protocol: NTCIP.
OLA — Overlap A (for example)
PA — Phase Allocation
PC — Personal computer
PE — Preemption
Ped — Pedestrian or Pedestrian phase
PED CLR — Pedestrian Clearance Interval
Phase — a single traffic movement. NEMA compatible controllers typically manage the intersection
in terms of phases, while earlier controllers use intervals and circuits instead.
POM — Pedestrian Override Mode
Port — A channel (outlet) that connects the controller to external devices. May be parallel or serial.
Power failure — Incoming Line Voltage falls below 95 (93 ± 2) VAC for 50 milliseconds or more.
Power restoration — Incoming Line Voltage rises above 96 VAC (or into the range of 98 ± 2 VAC)
for 50 milliseconds or more.
PROM — Programmable Read-Only memory
RAM — Random Access Memory. The main memory of a computer while power is on. Typically
does not maintain its contents when power is turned off.
RU — Remote Communications Unit – Used in some cities to interface the controller to a coaxial
cable communications facility.
RGB — Reduced Green Band
ROM — Read Only Memory, hard written memory in a computer that is maintained even when
power is removed. Typically used to store basic OS code and firmware programs.
RX — Reception
SDLC — Synchronous Data Link Control
Semi-actuated — Identifies a type of intersection control that has one or more phases that lack a
vehicle detector input capability.
396
Glossary
Serial interface — A device, which processes information one (1) bit at a time from the computer
to a printer or another peripheral unit.
SNMP — Simple Network Management Protocol. The basis for the NTCIP protocol.
SP — Start Permissive Period (for Phase-based operation) or Signal Plan (for Pre-timed operation)
SPL — Split, in a coordinated traffic system, each intersection in an artery must have the same
cycle time. So instead of set times for each phase, a coordinated intersection has a split assigned
to each phase. A split is a percentage of the total time available in the cycle.
SPP — Start Pedestrian Permissive Period
TANSTAAFL — "There ain't no such thing as a free lunch"
TBC — Time-based coordination. Indicates that coordination or plan selection is based upon the
time of day using an internal clock.
T/F — Terminal and Facilities
TCP/IP — Transmission Control Protocol/Internet Protocol. The most common pair of protocols
used to send data across an Ethernet or the Internet. Each component in such a system is
assigned a unique IP address.
TIC — Time Implemented Command
TRP, Time Reference Point — A point in time which serves as the time reference for an entire
artery or region of traffic flow. For example, in the timing diagram for a single street, each
intersection has a time offset between the start of its cycle and one arterial signal which serves as
the Time Reference Signal. The start of the Green time reference signal in this system is known as
the Time Reference Point.
TOD — Time of Day
TP — Timing plan. Interval times for use when running an interval-based pattern (i.e. pre-timed
operation)
TSP — Transit Signal Priority. The system in place where transit vehicles, typically buses, transmit
a signal to a detector in the intersection, and the intersection controller responds by giving the
transit vehicle additional green time, and/or if the light is currently red, shortens the side street
green times to bring the green back to the bus’s light more quickly. The intersection gets back into
sync fast or tries to stay in sync by reducing and extending in the same cycle.
TX — Transmission
USB — Universal Serial Bus. A common computer peripheral interface.
USTC — U.S. Traffic Corporation
UV — Ultraviolet
VAC — Volts (RMS), Alternating Current
VDC — Volts, Direct Current
WLK, WALK — Walk Interval Time
Watchdog — A monitoring circuit external to the IQ ASTC which senses an ASTC output via the
BIU. No change in state of this output for a CMU programmed period (typically 1 second) denotes
an ATC unit error and the CMU or MMU will put the cabinet in FLASH.
WRM — Walk Rest Modifier
397
Glossary
398
Index
1
10Base-T ................................................... 17
2
2070-6A Async card ................................... 18
24v_inhib .................................................. 77
24v1 ......................................................... 77
3
3000 Series ............................................. 391
A
A connector ............................................. 360
A to F keys ................................................ 13
AASHTO .............................................. 1, 121
ABS Zero screen ...................................... 124
absolute zero ........................................... 186
AC .......................................................... 391
access diagnostics .................................... 317
accessing the utilities menu ........................ 23
act LED ..................................................... 18
action ...................................................... 161
action mask ............................................... 57
action number ........................................... 57
action plan
TSP ..................................................... 288
action plans
TSP ..................................................... 301
actions .............................................155, 156
activated xped by TOD ............................. 132
activating edit mode................................... 13
active ................................................ 64, 114
active detectors ......................................... 60
active preempt........................................... 58
actuated ................................... 221, 222, 240
Actuated.................................................. 391
actuated mode......................................... 201
actuated mode coordinated phase ............ 200
actuated phase yield point ........................209
actuated rest in walk ................................149
actuated rest-in-walk ................................164
Adaptive Split Control ...............................391
ADC .........................................................391
add init ....................................................174
add time ..................................................199
added initial .............................................149
added initial timing screens .......................142
adding SNMP manager............................... 33
addonly ...................................................199
address
HDLC group address .............................. 92
adjusting screen contrast ........................... 21
Advance Call Detector ...............................391
Advance Warning .....................................391
advanced logging .....................................337
advanced time setup ................................167
advanced transportation controller ............... 1
Afrikaans .................................................121
alarm ........................................................ 61
alarm logging ...........................................339
alarms ...................................................... 76
alarms/event log screen ............................. 75
alphabetic keys ......................................... 13
alt half hz channel ..................................... 83
alt half Hz channel ..................................... 84
alt1/2 ....................................................... 88
altmap .....................................................100
always clear ped overlap ................... 273, 281
amber clearance .......................................239
anti-backup ..............................................126
arrow buttons ...................................... 14, 23
arrow keys ................................................ 14
ARW ........................................................149
ASCII .......................................................391
assigning a detector to a phase .................177
assumptions ................................................ 1
ASTC .......................................................391
ASTC cabinet install guide .......................... 35
ASTC controller
display .................................................. 12
399
Index
ATC......................................................... 391
definition ................................................. 1
ATC Link....................................... 17, 33, 348
communications..................................... 17
ATC Link manual .......................................... 2
ATC-1000
housing ................................................. 11
maintenance........................................ 342
photo ...................................................... 6
ATC-2000 controller ..................................... 7
ATC-3000 controller ..................................... 8
auto .......................................................... 35
auto pedclear ............................................ 81
Auto/Manual Switch ................................. 391
autodetect ................................................. 19
automatic mode ....................................... 191
AUX ........................................................ 159
auxiliary connector ................................... 381
auxiliary functions ...................................... 57
auxiliary outputs ...................................... 159
available overrides ................................... 163
available types of overlap ......................... 277
AWG ....................................................... 391
B
Back Panel............................................... 391
back plan message..................................... 56
backlight ................................................... 22
backlight timer ........................................... 22
backplane ................................................ 391
backup power ............................................ 20
back-up time ............................................. 81
bad plan .................................................... 55
balance ..................................................... 64
balanced mode ........................................ 211
Barrier ..................................................... 391
barrier ring split sums not equal sums ......... 55
barrier sum greater than cycle length .......... 55
barriers ..................................................... 68
baud rate .......................................... 92, 391
begin day of month .................................. 171
begin day of week.................................... 171
begin mins from midnight ......................... 171
begin month ............................................ 171
begin occur ............................................. 171
bin file ....................................................... 27
BIOS ......................................................... 12
BIOS version.............................................. 78
BIU ............................................ 90, 391, 397
BIUs .......................................................... 92
blue function key ....................................... 23
blue key .................................................... 13
board setup ............................................. 113
400
board status .............................................114
boot loader .......................................... 26, 78
bps ..........................................................392
buffer ......................................................392
build number..........................................2, 29
build rev ................................................... 78
buttons ..................................................... 12
numbers ............................................... 13
C
CA 392
cabinet .....................................225, 241, 392
cabinet address .................................... 32, 93
cabinet environment .................................. 10
cable lengths attached to USB port ............357
calibration ................................................342
call .................................................. 174, 392
call codes .................................................. 48
call ph ......................................178, 180, 181
call phases ................................................ 70
call to non act ..........................................147
call to non-actuated ................................... 72
calling an interval-based plan ....................215
calls
TSP .....................................................304
calls from the keypad ................................ 52
CalTrans TEES ........................................... 18
cancel ....................................................... 13
cancel function .......................................... 13
capabilities .................................................. 7
capacitor power backup ............................. 20
capacity ...................................................392
carryover ped overlap ....................... 274, 281
cars B4 gap reduction ...............................143
caution ....................................................... 4
CBD .........................................................392
CBD controller ............................................. 2
central communications ............................. 17
central system ..........................................240
channel ............................. 114, 226, 240, 392
green ................................................... 88
red ....................................................... 88
channel event logging ...............................339
channel to interval map ............................220
channels
copying................................................314
channels screen......................................... 88
channels to interval map ...........................223
check-in check-out ...................................294
check-in plus time ....................................294
checking firmware version.......................... 25
checking for install components .................. 32
checklist
Index
field deployment .................................... 35
checksum ................................................ 392
CHN .......................................................... 50
choosing an interface language................. 121
CIC ......................................................... 392
clear.......................................................... 15
clear time ................................................ 280
clearance fail ........................................... 304
clearance Interval .................................... 392
clearance timing ...................................... 136
clearance timing screens .......................... 140
clearing manual calls .................................. 52
clock ......................................................... 20
closed loop D module ............................... 381
closed-loop system................................... 392
CLR ......................................................... 392
CLR button ................................................ 15
CMD pattern indicators ............................... 49
cmnd ........................................................ 54
CMOS ...................................................... 392
CMU .......................... 12, 17, 20, 77, 348, 392
CMU log .................................................. 333
cna ............................................ 72, 200, 201
CNA ................................... 72, 147, 164, 392
CNA override ........................................... 164
CNA phase yield point .............................. 209
CNA2 ...................................................... 148
color codes ................................................ 53
comm...................................................... 114
comm ports screen .................................... 90
commanded action mask ............................ 57
commanded mode ..................................... 70
commanded plan ..............................218, 220
commands ............................................... 157
comms connectors ..................................... 15
communications diagnostics ..................... 321
compatibility line ...................................... 392
compatibility settings.................................. 85
compliance with NTCIP............................. 350
concurrency groups .................................... 68
conditional service ............................149, 392
CONF ........................................................ 77
conf phs .................................................. 277
config number ......................................... 303
configuration
overview ............................................. 328
configuration menu .............................. 44, 80
configuring controller operation ................ 328
configuring SNMP manager......................... 33
conflict monitor ........................................ 392
conflicting phases .................................... 393
connecting multiple preemption runs ......... 253
connections
I/O module............................................ 19
connector
AUX .....................................................381
coordination .........................................383
port 2 ..................................................353
preemption ..........................................382
connector details .............................. 352, 360
TS2 Type 2 ..........................................361
consistency checks ...................................205
constant call .............................................294
contact information ..................................... 3
contrast .................................................... 21
contrast control ......................................... 12
control ...................................................... 88
control and timing ......256, 258, 260, 262, 264
controller .................................................393
controller data security .............................266
controller menu .................................. 44, 136
controller message log ..............................335
controller preemptive verification ...............266
controller status ........................................ 47
controller status display ............................312
controller status menu ............................... 47
controller unit...........................................393
coord .......................................................393
coord active .............................................. 75
coord correction mode ..............................190
coord fail .................................................. 75
coord fault ................................................ 75
coord force mode .....................................190
coord maximum mode ..............................190
coord operational mode ............................190
coord pattern consistency checks ..............205
coord patterns ..........................................195
coord ph ..................................................204
coordinated patterns.................................... 9
coordinated phase ....................................200
coordinated phase yield point ....................200
coordination .............................................393
connector ............................................383
definition .............................................393
coordination check faults ........................... 55
coordination data
copying................................................316
coordination events logging ......................338
coordination menu.............................. 44, 190
coordination status screen ......................... 53
coordination variables ...............................190
co-phase ................................................... 85
co-phases ................................................. 85
copy from ................................................315
copy to ....................................................315
copying
wildcard commands ..............................315
copying the database................................314
401
Index
correction mode ................................191, 204
COTS ...................................................... 393
CPU ......................................... 342, 348, 393
crc ................................................................
.......................................................... 265
CRC .................................................. 74, 393
CRD ........................................................ 393
CRD CMD .................................................. 51
crdphase ................................................. 202
creating a ped overlap.............................. 283
creating an overlap .................................. 279
critical alarm .............................................. 76
critical intersection ................................... 393
critical intersection control ........................ 392
CU .......................................................... 393
current control plan .................................... 57
current mode ............................................. 70
current monitoring ................................... 115
current pattern .................................218, 220
current protection ...................................... 20
current signal plan ............................218, 220
current time............................................. 124
current timezone ...................................... 166
current timing plan............................218, 220
cursor ....................................................... 40
customer service .......................................... 3
cvm........................................................... 77
CVM ........................................................ 393
cycle ....................................................... 393
cycle dwell............................................... 228
cycle fault .................................................. 75
cycle length ......................................195, 219
cycle overlaps .......................................... 263
cycle ped ................................................. 263
cycle phases ............................................ 262
cycle portion ............................................ 253
cycle zero point........................................ 393
cycle/offset/split data ............................... 217
cycle-offset-split patterns ......................... 195
D
D module .................................................... 9
closed loops ........................................ 381
coordination port ................................. 383
LMD-9200 ........................................... 384
Multisonics .......................................... 388
preemption connector .......................... 382
Traconex ............................................. 386
data key .................................................... 20
database ........................................... 12, 393
copy ................................................... 314
default .................................................. 34
moving................................................ 332
402
DataKey Electronics ................................... 20
date
day plan ..............................................162
day ..........................................................166
day plan ..............................................161
day plan...................................................161
day plan screens ......................................160
day plan status .......................................... 57
day plans ............................................. 9, 155
daylight saving settings.............................169
daylight saving time
default settings ....................................169
daylight savings time ................................166
DB ver ...................................................... 78
DC monitor ............................................... 77
deactivating the backlight .......................... 22
debris ....................................................... 11
default coord pattern ................................293
default database........................................ 34
default database load ...............................311
default DST settings .................................169
default TSP action plan .............................293
delay ......... 182, 228, 256, 257, 258, 260, 262
detector ...............................................176
TSP .....................................................303
delay mode ..............................................277
density.....................................................393
maximum initial....................................142
time before reduction ...........................143
time to reduce .....................................144
dest phs...................................................128
destination ph ases ...................................133
detection zone..........................................393
detector ...................................................393
active ................................................... 60
fail time ...............................................177
failed .................................................... 60
maximum presence ..............................179
no activity diagnostic ............................178
reseting a ............................................175
detector alarms logging ............................339
detector call phases screen .......................177
detector diag ............................................. 91
detector failure .........................................394
detector fault ............................................ 76
detector inputs ............................................ 9
detector logging .......................................338
detector memory ......................................394
detector menu.................................... 44, 173
detector non-lock .....................................152
detector rack ........................................ 91, 92
detector to phase assignment ...................177
detectors
copying................................................314
Index
detectors status screens ............................. 60
DHCP setup ............................................. 106
DIAGF ....................................................... 77
diagnostics ................................................ 14
diagnostics mode ...................... 310, 317, 318
diamond sequence ring sum greater than cycle
time ...................................................... 55
dimming ............................................ 88, 394
directory structure on USB thumbdrives .... 334
disabling DST .......................................... 169
display ................................................ 11, 12
display backlight ........................................ 22
display button ............................................ 40
display contrast ......................................... 21
display current DST settings ..................... 169
display language ...................................... 121
display logs ............................................. 117
display test .............................................. 329
DLL ......................................................... 394
documentation ............................................. 2
DST status............................................... 166
dual entry ................................. 148, 164, 394
dual entry phases ...................................... 70
duplex ..................................................... 394
dwell ....................................................... 222
interval ............................................... 222
dwell extend ............................................ 263
dwell extend time .................................... 266
dwell green ............... 182, 256, 258, 260, 262
dwell overlap ........................................... 262
dwell pd .................................................. 262
dwell ph .................... 182, 256, 258, 260, 262
dwell phase ......................................252, 262
dwell portion
interval-based preemption .................... 233
dwell red ................................................. 259
dwell stage .............................................. 226
Dwl Red .................................................... 59
DWN button .............................................. 14
dynamic host configuration ....................... 106
dynamic max limit .................................... 146
dynamic max step .................................... 146
dynamic max timing screens ..................... 146
dynamic objects ....................................... 350
dynamic omit phases................................ 127
dynamic recall phases .............................. 127
dynamically linked library ......................... 394
E
E key......................................................... 13
early green .......................................289, 305
early lead ................................................ 277
edit mode ................................. 13, 14, 23, 40
EEPROM ..................................................394
EGB .........................................................394
ehci .........................................................357
EIA-232 ...................................................353
email address .............................................. 3
enable exclusive peds during dwell ............263
enabled intervals ......................................306
enabled phases ........................................306
enabling ICC .................................... 122, 123
enabling phases .......................................137
enabling/disabling Texas Diamond mode ...122
ENB/CYL/DWL G .......................................256
enclosure .................................................. 11
end day of month .....................................171
end day of week .......................................171
end mins from midnight ............................171
end month ...............................................171
end occur.................................................171
end perm .................................................204
endvehpermissive .....................................209
English.....................................................121
Ent green .................................................258
ENT key .................................................... 14
ent ped clear ..............182, 256, 258, 260, 262
ent red clear ............................................259
ENT time use ...........................................258
ent yel chng .............................................258
Enter button.............................................. 14
enter MUTCD flash .................................... 83
entering diagnostics mode ........................317
entering edit mode ............................... 13, 23
entry
TOD schedule ......................................161
entry phase ..............................................252
entry time mode
preemption ..........................................258
environmental specs .................................349
EP ...........................................................394
EPP .........................................................394
EPROM ....................................................394
err cnt .....................................................179
err cts .............................................. 176, 177
erratic counts diagnostic ................... 176, 179
esc button ................................................. 40
ESC button ................................................ 15
escape ...................................................... 15
ethernet
addresses ............................................. 93
connector ............................................356
ethernet comms enable ............................107
Ethernet hubs ........................................... 94
ethernet port .............................. 17, 349, 356
Ethernet port ............................................ 15
ethernet ports ..........................................348
403
Index
event ...................................................... 156
event data ............................................... 336
event log status ......................................... 75
event number .................................... 57, 161
evp ......................................................... 394
exclusive pedestrian operation .................. 128
exit intervals
interval-based preemption .................... 236
exit MUTCD flash ....................................... 83
exit pedestrian phases.............................. 264
exit ph ...............182, 256, 258, 260, 262, 264
exit phase
preemption.......................................... 252
exit stage ................................................ 226
exiting a pre-timed timing plan ................. 214
expansion slots .......................................... 18
exporting advanced logs ........................... 339
ext st ........................................................ 72
ext start .................................................... 75
extend..............................................177, 204
detector .............................................. 176
TSP ..................................................... 303
extend green ........................................... 138
extend phases ........................................... 70
external start ..................................... 72, 243
Extnd ........................................................ 59
F
f/o72
fail
TSP ..................................................... 304
fail T ....................................................... 177
fail time ................................................... 177
failed detectors .......................................... 60
fault .................................................... 75, 76
fault codes
ILS...................................................... 114
fault monitor output ................................... 20
fault monitoring ....................................... 397
fax .................................................................. 3
FDW through yellow ................................. 150
FDW through yellow and red .................... 150
fdw thru yellow ........................................ 266
FDW with YEL .......................................... 259
field deployment ........................................ 35
file system ................................................. 27
USB .................................................... 334
firmware....................................... 12, 25, 324
build# ..................................................... 2
firmware file names ................................... 28
firmware flowchart ..................................... 42
firmware update ........................................ 26
firmware upgrade ...................................... 16
404
firmware version ....................................... 78
fixed force................................................192
fixed timing menu ....................................217
fl enab .....................................................276
flash ............................................ 75, 83, 225
slow ..................................................... 84
steady red during .................................121
flash dwell ......... 182, 256, 258, 260, 262, 263
flash entry interval............................ 221, 222
flash exit interval .............................. 221, 222
flash exit red time ................................ 83, 84
flash exit yellow time ............................ 83, 84
flash memory ...........................................394
flash mode ...............................................193
flash rate .................................................277
flashing an output ....................................224
flashing don’t walk....................................150
flashing dwell intervals..............................227
flashing green ................... 223, 232, 235, 238
flashing yellow or red ........ 223, 232, 235, 238
floating force ............................................192
flowchart of firmware logic ......................... 42
FLSH green ..............................................276
FLSH red ..................................................276
FO ...........................................................394
FOM ........................................................394
force mode ..............................................192
force off .............................. 72, 152, 208, 394
force track G ............................................261
force-off...................................................138
frame 129 ................................................. 77
frame 40 ................................................... 92
free .......................................................... 75
free mode ................................................193
free run mode ........................................... 42
French .....................................................121
front panel ................................................ 11
FSK .........................................................394
FSK modem .............................................. 18
fully-actuated ...........................................394
function key ......................................... 13, 23
fuse ............................................. 11, 20, 349
G
gap..........................................................144
gap reduction ............................142, 144, 145
gap reduction timing .................................143
gap-out....................................................164
simultaneous........................................149
gapping out .............................................138
gateway addresses .................................... 94
global enable ................................... 127, 128
global time ...............................................167
Index
glossary................................................... 391
GMT ........................................................ 166
green
minimum ............................................. 138
green arrows ............................................. 14
green band .............................................. 394
green extend ........................................... 304
green extend mode .................................. 295
green extension ....................................... 289
green rest................................................ 148
green timing screens .........................136, 138
greenband analysis .................................. 395
GreenWave
version .................................................. 78
GreenWave firmware.................................. 25
grn ext .................................................... 307
grn red .................................................... 307
ground connection ....................................... 7
group address............................................ 92
guaranteed passage ................................. 149
H
half power balancing .................................. 88
handshake ................................................. 92
hard flash .................................................. 42
hardware checklist ..................................... 32
HDLC group address .................................. 92
heartbeat LED......................... 11, 15, 20, 342
heater ....................................................... 12
help button ................................................ 40
help system ............................................... 24
hi-fault .................................................... 114
HLP key ..................................................... 14
HMC
I/O ....................................................... 96
HMC input/output port ............................. 371
HMC-1000 module ................................. 7, 19
HME .......................................................... 13
hold ........................................................ 208
hold-fo ...................................................... 54
home button .............................................. 13
Honeywell ................................................... 7
hour .................................................161, 166
hours of operation ....................................... 3
housing ..................................................... 11
hub
Ethernet ................................................ 94
Hz 395
I
I/O mapping ...................................... 95, 101
I/O module
NEMA TS2 Type 1 ................................360
NEMA TS2 Type 2 ................................361
I/O modules ................................................ 7
overview ............................................... 19
ICC .................................................. 122, 123
icc preemption .........................................265
idle ........................................................... 64
idle pending .............................................. 64
if PH on ...................................................127
illinois commerce commission ....................265
ILS ...............................................................
...........................................................112
board setup .........................................113
current monitoring ...............................115
error counts .........................................118
ILS fault codes .........................................114
immediate EXT .........................................257
important .................................................... 4
included ...................................................280
in-fault .....................................................114
INH OL ATG .............................................260
inhibit overlaps .........................................260
INIT ........................................................395
initial plus clearance greater than split ........ 55
input delay ................................................ 59
input extend.............................................256
input mirror...................................... 257, 266
input mode
TSP .....................................................294
input priority ............................................242
input status screen .................................... 71
inputs
TSP ...................................................... 62
inputs/outputs status menu........................ 71
insertion ..................................................289
int adv ...................................................... 72
interface navigation ................................... 40
international load switch menu ..................112
Internet site ................................................ 3
intersection ...................................... 226, 395
intersection programming .......................... 36
intersection startup.................................... 82
interval .......... 9, 222, 225, 226, 240, 241, 395
interval advance ................................. 72, 152
interval menu ...........................................183
interval modifiers .............................. 220, 221
interval operation .....................................214
overview ..............................................214
interval skipping ............................... 239, 240
interval-based
lagging left turn ............ 244, 246, 248, 249
leading left turn ............ 244, 246, 248, 249
interval-based operation .............................. 9
interval-based preemption ........................225
405
Index
signal output options............................ 232
intervals used .......................................... 219
invalid cycle timer ...................................... 55
IO D module .............................................. 78
IO module ................................................. 78
IP addr high word ...................................... 92
IP address ................................................. 34
setting the ............................................. 32
IP address local ......................................... 93
IP address system ...................................... 93
IP/Cabinet address ..................................... 93
IP/Cabinet setup screen ............................. 90
IPL ................................................................ 78
IQ Central ......................................... 93, 210
communication ...................................... 17
IQCentral
communication ...................................... 17
IQCentral manual ......................................... 2
irms ........................................................ 116
ITE ............................................................. 1
ITS ......................................................... 395
J
jumper .................................................... 395
jumpers
spare port configuration ......................... 17
K
kb .......................................................... 395
Kern controller
firmware ............................................... 25
key inputs ................................................. 58
keyboard conventions .................................. 4
keycode
hardware mismatch override .................. 96
keypad ...................................................... 12
numbers................................................ 13
keypad shortcuts
placing calls ........................................... 52
keypad test ............................................. 329
L
L0 ...................................................186, 196
lagging left turn ......... 244, 245, 246, 248, 249
language selection ................................... 121
last car passage ....................................... 144
launching an interval-based timing plan..... 215
LCD........................................................... 12
contrast ................................................ 12
definition ............................................. 395
LCD specs ................................................. 11
406
lead/del ...................................................277
lead/lag operation ....................................395
leading left turn ..........244, 245, 246, 248, 249
LEDs .................................................. 11, 349
definition .............................................395
ethernet ............................................... 18
heartbeat .............................................. 20
link .................... 182, 256, 257, 258, 260, 262
link LED .................................................... 18
linking......................................................253
Linux ....................................... 7, 25, 78, 348
version ................................................. 78
LMD 40
I/O ....................................................... 96
LMD module ...........................................7, 19
LMD9200 D module ..................................384
load switches ...........................................112
loaded plan ............................................... 68
loaded sequence ....................................... 68
loading a database from a USB thumbdrive 332
loading a default database ......................... 34
loading default DST settings......................169
loadswitch ................................................392
local .................................................. 53, 395
local address ............................................. 93
local connector .........................................354
local cycle reference point .........................186
local cycle zero ..................................... 57, 76
local flash ............................................ 75, 77
local free ................................................... 75
local override ............................................ 76
local time differential ........................ 166, 168
local time differentiation ...........................167
local zero phase .......................................196
lo-fault .....................................................114
log data ...................................................336
copying................................................335
logic processing ........................................126
logs
moving log data on USB thumbdrives ....333
loopback test ...........................................321
lsw board error counts ..............................118
M
M0 ...........................................................186
M3000 .....................................................395
MAC address ................................ 17, 78, 395
main menu................................................ 44
main menu button ..................................... 40
main module ..........................................6, 11
maintenance ............................................342
overview ..............................................328
malfunction management unit ........... 392, 395
Index
Manhattan RCU.......................................... 17
manual calls from Runtime status screen ..... 52
manual control enabled ...................... 72, 221
manual flash mode................................... 191
manual free mode .................................... 191
manual pattern mode ............................... 191
manuals ...................................................... 2
mapping ............................................ 95, 121
master ...................................................... 53
master cycle ............................................ 186
master operation ..................................... 121
master reservice time ........................301, 304
master time zero ...................................... 186
max .................................................152, 395
MAX 1 ..................................................... 139
max 2 ....................................................... 72
max duration ........................................... 257
max dwell ................................................ 199
max II ..................................................... 139
max inhibit ................................................ 72
max initial................................................ 142
max pres ................................................. 179
max presence .....182, 229, 256, 258, 260, 262
max prs ............................................176, 177
max recall.........................................151, 164
maximum 1 ............................................. 138
maximum initial ....................................... 142
maximum mode ....................................... 192
maximum patterns ................................... 190
maximum presence .................................... 59
maximum vehicle recall ............................ 202
maximum1 .............................................. 192
maximum2 .............................................. 192
maxinhibit ............................................... 192
MB ................................................................
.......................................................... 395
mce .................................................. 72, 222
MCE .................................................221, 395
media access control address ................... 395
memory ............................152, 243, 348, 394
memory diagnostics ................................. 321
menu
alarms/event log .................................... 44
configuration ................................... 44, 80
controller............................................. 136
coordination .................................. 44, 190
detector ................................................ 44
detectors ............................................. 173
I/O mapping .......................................... 95
main ..................................................... 44
status.............................................. 44, 46
TOD plans ............................................. 44
menu button .............................................. 14
menu diagram ........................................... 43
menu help system ..................................... 40
menu navigation........................................ 40
menu news ............................................... 40
menus
controller .............................................. 44
interval ................................................183
system maintenance .............................310
transit signal priority .............................292
USB .....................................................331
utilities ................................................328
microprocessor heartbeat LED ...................342
min...........................................161, 222, 395
min barrier sum greater than cycle time ...... 55
min duration ...... 182, 229, 256, 258, 260, 262
min flash ................................................... 81
min gap ...................................................144
min green .. 139, 182, 256, 258, 260, 262, 277
min rcl ...................................................... 72
min recall ......................................... 151, 164
min times
interval ................................................222
min walk ....................182, 256, 258, 260, 262
MINC ........................................................ 77
minimum duration ..................................... 59
minimum dwell .......................................... 59
minimum flash time .............................. 83, 84
minimum gap ...........................................144
minimum green ........................................138
minimum vehicle recall .............................202
minus walk dark .......................................272
minus walk ped clear ................................271
minus walk red .........................................272
minute .....................................................166
minutes to adjust time ..............................171
misc setup screen ...................................... 90
miscellaneous status .................................329
mizbat master id ......................................111
mm .................................. 223, 232, 235, 238
MMU .................. 17, 20, 35, 88, 392, 395, 397
connection ............................................ 17
enable .................................................. 92
MMU status screens ................................... 77
MNU ......................................................... 14
MNU button .............................................. 13
mode .......................................................202
model ....................................................... 78
modem slot ..............................................349
modifier ........................................... 276, 280
modifiers on overlaps................................270
module ....................................................395
module locations ......................................... 7
moe .........................................................293
MOE ........................................................395
month......................................................166
407
Index
day plan .............................................. 161
more than 1 coord phase in ring ................. 55
motherboard.............................................. 78
moving databases .................................... 332
moving logs using a USB drive .................. 333
ms ................................................................
.......................................................... 395
MSB ........................................................ 395
MSCLR .................................................... 395
MTBF ...................................................... 395
MTTR ...................................................... 395
Multisonics D module ............................... 388
MUTCD flash screen ................................... 83
N
n/a .......................................................... 396
n/c ................................................................
.......................................................... 396
navigating status screens ........................... 14
navigating the interface .............................. 40
navigating the status screens...................... 46
navigating the TSP screens ....................... 303
NEMA ...................................................... 1, 7
definition ......................................... 9, 396
gap reduction ...................................... 143
TS2 ......................................................... 9
NEMA I/O version ...................................... 78
NEMA operation ........................................... 9
NEMA standard ........................................ 348
NEMA timing ............................................ 138
NEMA TS2-1998 spec ................................. 17
NEMA-Interval-based transitions ................. 10
new install ................................................. 32
next .......................................................... 15
no act ..............................................176, 177
no activ ................................................... 178
no coord phase in an eligible ring................ 55
no early release ....................................... 203
NO key ...................................................... 15
non actuated mode coordinated phase ...... 200
non-critical alarm ....................................... 76
non-lock ...........................................152, 222
interval ............................................... 222
non-lock call .......182, 256, 257, 258, 260, 262
non-locking.............................................. 228
normal ped overlap ...........................273, 281
normal recovery ....................................... 301
note ............................................................ 4
NTCIP ........................................... 9, 17, 240
definition ............................................. 396
NTCIP compliance .................................... 350
NTCIP event log ....................................... 337
ntcip overlap type .................................... 270
408
ntcip plus .................................................271
NTCIP protocol .........................................397
number buttons......................................... 13
NXT button ............................................... 15
O
O Relay ..................................................... 77
object identifier ........................................396
occ det ....................................................175
offset .................................. 53, 186, 195, 219
offset correction
extend .................................................204
reduce .................................................204
offset correction recovery .........................302
offset correction screen ............................204
offset correction threshold ........................196
offset percent ...........................................199
offset seeking...........................................186
offset time greater than cycle time ............. 55
offset type ...............................................219
OFS .......................................................... 50
OID .........................................................396
OLA .........................................................396
omit a phase ............................................164
omit phases .............................................. 70
omit red clear ............................................ 72
opening help screens ................................. 24
operating system .............................. 9, 12, 25
operational mode .....................................191
operational status .....................................329
options for phases ....................................147
Optocom ..................................................383
opto-I ......................................................383
ordering a data key ................................... 20
output diagnostics ....................................320
output to interval map ...................... 220, 224
outputs ................................................ 65, 68
TSP ...................................................... 65
outputs status screen ................................ 73
overlap ...................................... 88, 268, 396
channels ..............................................275
example...............................................268
type modes ..........................................277
types ...................................................270
overlap compatibility .................................275
overlap FL ................................................257
overlap logging ........................................338
overlap screens ................................ 276, 280
overlap status screen ............................ 66, 68
overlap types ...........................................270
overlaps
copying................................................314
inhibit ..................................................260
Index
overlaps menu ......................................... 269
override..................................................... 76
PRTY................................................... 257
override commands .................................. 163
override fl .................. 182, 256, 258, 260, 262
override flash........................................... 228
override of hardware mismatch................... 96
override startup yellow and red times........ 259
overview ..................................................... 6
menu system ......................................... 40
ovl ...................................................... 66, 68
P
P1TO......................................................... 77
PA .......................................................... 396
page down button ...................................... 15
page up/down buttons ............................... 40
parent phases .......................................... 268
parents.................................................... 276
parity ........................................................ 92
passage............................................138, 174
passage timer ...................................145, 152
passage timing ........................................ 138
patn .......................................................... 54
patt ......................................................... 156
patt table data type.................................. 194
pattern .............................................218, 220
system ................................................ 193
pattern call .............................................. 193
pattern changes in a coordinated environment188
pattern command codes ............................. 51
pattern selection ...................................... 156
pattern sync ............................. 166, 167, 168
pattern sync control ................................. 186
pattern table screens ............................... 195
pattern to timing plan map ....................... 216
patterns .................................................. 6, 9
PC .......................................................... 396
PC communications .................................. 342
PC port ...................................................... 17
PE .......................................................... 396
ped ......................................................... 396
ped c ........................................................ 72
ped call codes ............................................ 48
ped clearance ........................... 141, 148, 239
PED CLR .................................................. 396
ped o ........................................................ 72
ped omit.................................................. 164
ped overlap
types .................................................. 273
ped overlap types .................................... 281
ped overlaps ............................................ 280
ped phs ..................................................... 88
ped recall .................................................164
ped recycle ............................................... 72
ped time plus clearance is greater than split 55
ped timing ...............................................136
ped walk ..................................................141
pedestrian detectors screen .............. 178, 180
pedestrian inputs ......................................... 9
pedestrian overlaps status screen ............... 67
pedestrian override ...................................199
pedestrian override mode .........................396
pedestrian recall ............................... 152, 203
pedestrian timing screens .........................141
Peek Traffic ................................................. 3
per interval modifiers ................................222
perm ........................................................ 53
permissive........................................ 204, 272
placement ............................................208
permissive left turn ...................................152
permissive strategy...................................197
persistence ..............................................122
phase ......................................................202
definition .............................................396
phase call .................................178, 180, 181
phase changes logging .............................338
phase compatibility ...................................120
phase compatibility screens ........................ 85
phase concurrency fault ............................. 69
phase control logging ...............................338
phase enables screen ...............................137
phase insertion .........................................289
phase max recall ......................................164
phase min recall .......................................164
phase next control ....................................122
phase omit ...............................................164
phase omitted ..........................................203
phase option screens ................................147
phase rotation ..........................................289
phase skipping ................................. 289, 304
phase timing ............................................140
phase timings ...........................................138
phase-on-demand ....................................289
phases ........................................................ 9
copying................................................314
phone number............................................. 3
photo
comms ports ......................................... 15
photo of ATC-1000 ...................................... 6
phs codes ................................................. 49
pid................................................................
...........................................................357
pin assignments .......................................101
HMC ....................................................371
LMD port A ..........................................374
LMD port B ..........................................376
409
Index
LMD port C .......................................... 377
LMD port D.......................................... 378
port A ................................................. 361
port B ................................................. 366
port C ................................................. 368
placement of force off .............................. 208
placing manual calls ................................... 52
plan processing ........................................ 214
police button ........................................... 221
pom ........................................................ 199
POM ........................................................ 396
port
USB .................................................... 357
port 1 ................................................ 17, 352
enable ................................................... 92
port 1 screen ............................................. 90
port 1 settings screen................................. 92
port 2 ........................................................ 17
port 3 ........................................................ 17
port 4 ................................................ 17, 354
port 5 ................................................ 17, 355
port A...................................................... 361
LMD .................................................... 374
port B...................................................... 366
LMD .................................................... 376
port C...................................................... 368
LMD .................................................... 377
port D
LMD .................................................... 378
port process ............................................ 107
ports
2 through 5 setup screen ....................... 92
communications..................................... 15
data key ................................................ 20
definition ............................................. 396
ethernet ................................................ 17
expansion slots ...................................... 18
HMC.................................................... 371
input/output ........................................ 371
LMD port A .......................................... 374
LMD port B .......................................... 376
LMD port C .......................................... 377
LMD port D.......................................... 378
MSA .................................................... 361
MSB .................................................... 366
MSC .................................................... 368
PC 17
SDLC..................................................... 17
spare .................................................... 17
specifications ....................................... 349
system .................................................. 17
USB ...................................................... 16
power failure ........................................... 396
power inputs ............................................... 7
410
power module ............................................. 6
power restart ............................................ 75
power restoration .....................................396
power supply ............................................ 20
power supply status................................... 11
preempt ..................................... 76, 226, 240
control and timing ..256, 258, 260, 262, 264
interval-based ......................................225
preemption ................................................. 9
cycle phase ..........................................253
D module port ......................................382
icc .......................................................265
linking .................................................253
phases .................................................252
pre-timed interval skipping....................239
priority ................................................257
preemption events logging ........................338
preemption menu .....................................255
preemption modifiers ................................228
preemption screens ..................................252
preemption status screen ........................... 58
pretimed
flashing output .....................................224
pre-timed
interval modifiers .................................221
signal output options ............................223
pre-timed
actuated interval operation ...................240
pre-timed
leading left turn ...................................245
pre-timed
lagging left turn ...................................245
pretimed modifiers ...................................222
pre-timed pattern to plan assignments.......216
pretimed status screen .............................. 50
prev menu button...................................... 40
previous button ......................................... 14
priority
interval-based preemption ....................242
TSP .....................................................289
priority of preemption calls ........................257
process control .........................................107
programmed splits .......................... 65, 68, 70
programming IO mapping .......................... 96
programming menu ................................... 80
programming the controller ........................ 36
PROM ......................................................396
protected permissive ................................272
PRS .........................................................176
prty override ..............182, 256, 258, 260, 262
PRTY override ..........................................257
PRV .......................................................... 14
ptn ........................................................... 53
Index
Q
q jujmp ................................................... 304
q jump .................................................... 304
q jumping ................................................ 290
q jumps ............................................... 65, 68
queue ...................................... 174, 176, 177
queue jump time ..................................... 306
queue jumping......................................... 306
quick start ................................................. 32
R
R1W .......................................................... 55
RAlarm ...................................................... 61
RAM ........................................................ 396
RAM devices .............................................. 16
range copying .......................................... 315
RCU .................................................. 17, 396
real-time clock ........................................... 20
recall ........................................ 139, 164, 222
interval ............................................... 222
pedestrian ........................................... 152
recall screens........................................... 151
receive LEDs .............................................. 11
recovery .................................................... 64
recovery strategy ..................................... 301
red clearance ..................................... 82, 140
red fail ...................................................... 77
red flash channel ................................. 83, 84
red lock ................................................... 175
red rest ........................................ 10, 72, 164
red revert .......................................... 81, 140
red time .................................................. 239
reduce..................................................... 204
reduce phase ........................................... 305
reduce time ............................................. 199
reduction ................................................. 289
related documents ....................................... 2
release notes ............................................. 25
r-en .......................................................... 77
request time sync .................................... 121
reservice ................................................. 304
reservice time .......................................... 301
reset ................................................. 77, 175
RESP to FAIL ............................................. 77
response fault ............................................ 75
rest-in-walk ............................................. 164
restoration of power................................. 396
revision info ....................................... 78, 329
revisions screen ......................................... 78
RGB ........................................................ 396
right turn on red ...................................... 152
ring compatibility ....................................... 85
ring max 2 ...............................................164
ring max inhibit ........................................164
ring omit reclear .......................................164
ring ped reclear ........................................164
ring R phase omitted ................................. 69
ring red rest .............................................164
ring sequencing screens ............................119
ring status ................................................ 59
rings ........................................................... 9
copying................................................314
ROM ........................................................396
rotation ....................................................289
RS232 ....................................................... 17
RS-232C ..................................................353
RS485 ....................................................... 17
RS-485 ..................................................... 17
run
TSP .....................................................288
run config .................................288, 290, 301
run configuration
TSP .....................................................302
run enable ...............................................301
run number ..............................................303
run parameters
TSP .....................................................294
run request ..............................................294
run status ............................................ 54, 55
run status codes ........................................ 63
runtime status ........................................... 47
interval version ..................................... 50
rx 396
S
safety ......................................................... 1
same phase fault ....................................... 69
schedule ..................................................155
copying................................................314
schedule date ...........................................161
schedule day ............................................161
schedule day plan............................. 161, 162
schedule month ........................................161
schedule screens ......................................161
schedules .................................................... 9
scope .......................................................... 1
screen backlight ........................................ 22
screen contrast.......................................... 21
SDLC .......................................................396
SDLC cable................................................ 35
SDLC connector ........................................352
SDLC port ................................................. 17
SDLC status screen .................................... 74
sec/actuation ...........................................142
second .....................................................166
411
Index
select all .................................................... 13
selecting an interface language ................. 121
semi-actuated .......................................... 396
SEQ faults ................................................. 69
sequence consistency checks ...................... 69
sequence status ................................... 68, 87
sequencing .............................................. 119
serial interface ......................................... 397
serial ports ................................................ 15
service information....................................... 3
set DST by day of week............................ 169
set DST by exact date .............................. 169
set local time ........................................... 166
setting IP address ...................................... 32
setting screen contrast ............................... 21
setting the length of the timing plan ......... 219
setting up a basic intersection..................... 36
setting up advanced logging ..................... 337
setting up daylight saving time ................. 169
setting up TSP ......................................... 290
setup checklist ........................................... 35
seuence number ...................................... 195
SGO ........................................................ 149
shift ........................................................ 289
shift phase .............................................. 305
shipping .................................................... 11
short alarm status screen ........................... 76
shortway ................................................. 199
shortway dwell......................................... 199
signal codes............................................... 64
signal on/off .............................................. 35
signal output options .........................223, 232
signal plan ............................................... 221
signal plan transfer interval ...............221, 222
signal plans ............................................. 214
pattern map ........................................ 216
signal plans menu .................................... 220
signal system master................................ 121
signature file.............................................. 27
simple network management protocol ....... 397
simultaneous FDW ................................... 123
simultaneous gap out ............................... 149
simultaneous gap-out ............................... 164
skills needed ................................................ 1
skip phase ............................................... 304
skipping .................................................. 289
slow flash .................................................. 84
SNMP ......................................... 17, 396, 397
SNMP manager .......................................... 33
SNMP port ................................................. 94
soft flash ................................................... 42
soft recall .........................................152, 164
soft ret .................................................... 128
soft return phases .................................... 134
412
software .............................................. 25, 78
software update ........................................ 26
software version ........................................ 78
software version info ................................. 25
software version number ........................... 29
source phase ...................................... 88, 128
SP ..................................................... 50, 397
Spanish....................................................121
spare connector .......................................355
spare port ................................................. 17
SPC .........................................................159
special function ......................................... 13
special function outputs ............................159
special functions ........................................ 57
specifications ...........................................348
basic ...................................................... 9
SPL ..........................................................397
split .........................................................202
split number .............................................195
split table
TSP .....................................................307
split table data type ..................................194
split table screens .....................................202
split time..................................................219
split type ..................................................219
splits
TSP ................................................. 65, 68
SPP .........................................................397
SRAM................................................. 20, 348
SSM .........................................................121
st perm ....................................................204
stalled CPU ..............................................342
standards .................................................... 9
definition ................................................ 1
standby mode ..........................................193
start up flash ............................................243
startup call ................................................ 77
start-up configuration screen...................... 81
startup settings ......................................... 82
start-up timing .......................................... 81
status
controller status display ......................... 47
coord .................................................... 53
coordination status screen ..................... 53
detectors status screens ........................ 60
inputs status screen .............................. 71
MMU..................................................... 77
outputs status display ............................ 73
overlap status screen........................ 66, 68
preemption status screen ....................... 58
pretimed status display .......................... 50
SDLC .................................................... 74
short alarms.......................................... 76
TOD status screen ................................. 57
Index
TSP ........................................... 62, 66, 68
voltage ................................................ 329
status menu ........................................ 44, 46
status screen ............................................. 40
status screens............................................ 13
navigation ............................................. 46
steady red during flash ............................. 121
stop bits .................................................... 92
stop time ............................................. 72, 75
stop time switch....................................... 373
stop timing .............................................. 348
storing a controller database on a USB
thumbdrive .......................................... 332
subnet masks ............................................ 93
subnetaddr local ........................................ 93
super capacitor ........................................ 348
super capacitors......................................... 20
switch-to phase screen ............................. 178
symbols used in the manual ......................... 4
sync time function .................................... 116
synchronous data link................................. 17
synchronous data link control ..................... 74
SYS CMD ................................................... 51
system address .......................................... 93
system maintenance ................................ 342
system maintenance menu ....................... 310
system pattern..................................190, 193
system port ............................................... 17
system TSP action plan ............................ 293
T
t and f flash ............................................... 76
T/F.......................................................... 397
TBC ......................................................... 397
TBR..................................................143, 144
TCP/IP .............................................. 17, 397
tech support ................................................ 3
temperature range for LCD ......................... 12
temperature response of display ................. 21
term & facils .............................................. 92
term and facils ........................................... 91
Texas Diamond mode............................... 122
Texas Diamond status screen ..................... 70
threshold ................................................. 196
thumb drive ......................................... 26, 27
thumb drives ............................................. 16
TIC ......................................................... 397
time
back-up ................................................. 81
time B4 gap reduction .............................. 143
time before reduction ........................143, 144
time diagnostics ....................................... 322
time of day action .................................... 151
time of day action plans ............................... 9
time of day actions ...................................156
time of day functions ................................155
time reference point .................................397
time set screen.........................................166
time setup
advanced .............................................167
time sync
requesting ...........................................121
time to reduce ..........................................144
timer on the screen light ............................ 22
timezone ..................................................166
timing
start-up ................................................ 81
timing logs ...............................................338
timing plan ................................226, 240, 397
timing plan screen ....................................217
timing plan setup......................................217
timing plan transfer interval .............. 221, 222
timing plans .............................................214
pattern map .........................................216
pretimed ...................................... 218, 219
timing status ............................................. 47
timings ....................................................138
timings at startup ...................................... 82
TOD ........................................................397
TOD CMD.................................................. 51
TOD commands........................................157
TOD menu ...............................................155
TOD plans menu ....................................... 44
TOD status screen ..................................... 57
Toronto offset correction method ..............204
TP ..................................................... 50, 397
track channel setup ..................................231
track clearance using pre-timed preemption226
track G ..................................................... 59
track green ................182, 256, 258, 260, 262
track green reservice if new call ................266
track interval data menu ...........................230
track interval timers ..................................230
track overlap ............................................260
track ph .....................182, 256, 258, 260, 262
track phase ...................................... 252, 260
track red clearance time ...........................260
track yellow change time ..........................260
Traconex D module ..................................386
traffic engines ............................................. 9
traffic responsive ......................................210
traffic responsive operation ........................ 81
trail green/yellow/red ...............................277
trailing values ...........................................277
transfer interval ................................ 221, 222
transit signal priority 62, 66, 68, 157, 286, 397
transition status ........................................ 70
413
Index
transitions between NEMA and interval-based10
transmit LEDs ............................................ 11
TranSuite .................................................. 93
troubleshooting ........................................ 343
TSP ..................................................... 344
trp .......................................................... 397
TS1 ............................................................. 1
TS2 ....................................................... 1, 19
TS2 standard ............................................... 9
TS2 Type 2 ................................................ 17
TS2/2 output ............................................. 20
tsp .......................................................... 157
TSP ......................................................... 397
action plans ......................................... 301
configuration ....................................... 290
copying ............................................... 314
definition ............................................. 286
delay................................................... 303
extend ................................................ 303
extension modes.................................. 295
inputs ................................................... 62
menu .................................................. 292
methods .............................................. 289
overview ............................................. 287
run parameters .................................... 294
split tables ........................................... 307
status.............................................. 54, 55
troubleshooting ................................... 344
TSP action plan .......................................... 57
TSP active ................................................. 64
TSP enable .............................................. 293
TSP output status ...................................... 65
TSP splits ............................................ 65, 68
TSP status ................................................. 64
TSP status screens ......................... 62, 66, 68
TTR......................................................... 144
turning on the backlight ............................. 22
tx .......................................................... 397
TX/RX ....................................................... 11
type
ped overlap ......................................... 280
U
unit events logging .................................. 338
unit min recall override ............................. 164
unit parameters screen ............................. 293
unit WRM override ................................... 164
universal time .......................................... 166
up button .................................................. 14
updating firmware ...................................... 26
updating the firmware .............................. 324
UPS ........................................................... 17
UPS connector ......................................... 355
414
UPS log ....................................................333
US DOT ...................................................... 1
USB ................................................... 16, 397
distance limits ......................................357
specification .........................................349
version ................................................357
USB connector .........................................357
USB diagnostics ........................................323
USB file system ........................................334
USB firmware install .................................. 12
USB menu .......................................... 16, 331
USB port ................................................... 26
USB ports.................................................. 15
use conf phs ............................................277
USTC .......................................................397
USTC correction mode ..............................204
USTC miscellaneous ..................................121
utilities menu ..................................... 23, 328
utilization period .......................................293
uv 397
V
VAC .........................................................397
variable density ........................................143
variable density operation .........................142
VDC .........................................................397
veh c ........................................................ 72
veh h ........................................................ 72
veh o ........................................................ 72
veh phs..................................................... 88
vehicle detector options screens ................174
vehicle detector timing screens .................176
vehicle interval .........................................240
vehicle maximum .....................................151
vehicle minimum ......................................151
vehicle movement ............................ 225, 240
vehicle overlap programming ....................276
ventilation ................................................. 11
version info ............................................... 25
vid ................................................................
...........................................................357
viewing logs .............................................339
vol det .....................................................175
voltage status ..........................................329
volume/occupancy logging ........................338
W
WALK ......................................................397
walk hold state .........................................147
walk rest ..................................................149
walk rest modifier ............................. 164, 397
walk rest state..........................................148
Index
walk time ................................................ 280
walk timing .............................................. 141
walk timing state ..................................... 147
warning ....................................................... 4
watchdog ................................... 12, 348, 397
water intrusion .......................................... 11
web site ...................................................... 3
where to find a data key............................. 20
wig wag preemption signals...................... 227
wig-wag flash ............................................ 84
Windows install disks ................................. 33
wlk ext .................................................... 307
wlk red .................................................... 307
working with status displays ....................... 46
wrm .................................................. 72, 201
WRM ........................................ 149, 164, 397
exclusive during dwell...........................263
soft return phases ................................134
Y
year .........................................................166
year plan .................................................155
yel lock ....................................................175
yellow clearance ................................. 81, 140
yellow flash channel ............................. 83, 84
YES key .................................................... 15
yes/no buttons .......................................... 23
yield early time.........................................196
yield point ........................................ 200, 209
yield window percentage...........................194
Z
X
xped ................................................128, 129
activated by TOD action ....................... 132
destination phases ............................... 133
zero times ................................................124
zulu time..................................................166
415
Index
416
GreenWave v3.8 Menu System
(same screen)
1.1 Status - Controller Status
“Home”
“Menu”
Main Menu
1. Status
2. Programming
3. System Maintenance
4. Logs
1.1 Controller Status Menu
1.0 Status Menu
1.1 Controller
1.2 Inputs/Outputs
1.3 Alarms
1.4 MMU
1.5 Revisions
1.2 I/O Status Menu
2 screens
1.2.1 Inputs Status
1.2.2 Outputs Status
1.2.3 SDLC & FIO Status
2 screens
1.3 Alarm Status Menu
1.3.1 Unit Alarm Status 1&2
1.3.2 Short Alarm Status
1.1.1 Runtime Status
1.1.2 Coordination Status
1.1.3 Time of Day Status
1.1.4 Preemption Status
1.1.5 Detectors Status
1.1.6 TSP Status
1.1.7 Overlaps Status
1.1.8 Sequencing Status
1.1.9 Texas Diamond Status
1.1.5 Detector Status Menu
1.1.5.1 Vehicle Detector Status
2 screens
1.1.5.2 Pedestrian Detector Status
2.0 Programming Menu
1. Unit Configuration
2. Controller
3. Coordination
4. Time of Day
5. Detectors
6. Preemption
7. Interval
8. Transit Signal Priority
2.1 Configuration Menu
2.1.1 Startup
2.1.2 Program Flash
2.1.3 Phase Compatibility
2.1.4 Channels
2.1.6 Ring Sequencing
2.1.7 USTC Miscellaneous
2.1.8. Abs Zero
2.1.9. Logic Processing
2.1.0 Exclusive Pedestrian
2 screens
2 screens
16 screens
2 screens
2 screens
2.2 Controller Menu
2.2.1 Phase Enables
2.2.2 Green Timing
2.2.3 Clearance Timing
2.2.4 Pedestrian Timing
2.2.5 Added Initial Timing
2.2.6 Gap Reduction Timing
2.2.7 Dynamic Max Timing
2.2.8 Phase Options
2.2.9 Recalls
2.2.0 Overlaps
2 screens
2 screens
2 screens
2 screens
2 screens
2 screens
2 screens
2 screens
2.1.5.1
2.1.5.2
2.1.5.3
2.1.5.4
2.1.5.5
2.1.5.6
2.1.5.7
Port 1
Port 2-5
IP/Cabinet Address
I/O Mapping
DHCP Setup
Process Control
Int’l Load Switch Menu
2.1.9 Logic Processing Menu
2.1.9.1 Anti-Backup & Recall
8 screens
2.2.0 Overlaps Menu
2.2.0.1 Vehicle Overlap Variables
2.2.0.2 Pedestrian Overlaps
2.3 Coordination Menu
32 screens
16 screens
2.3.1 Coordination Variables
2.3.2 Pattern Table
48 screens
2.3.3 Split Table
16 screens
2.3.4 Offset Correction Ext/Reduce 16 screens
2.4 Time of Day Menu
2.4.1 Actions
2.4.2 Day Plans
2.4.3 Schedules
2.4.4 Override Commands
2.4.5 Set Local Time
2.4.6 Advanced Time Setup
2.4.7 Daylight Saving Setup
2.4.1 Time of Day Actions
32 screens
32 screens
10 screens
2.4.1.1 Plans
2.4.1.2 Auxiliary & Special Fctns
6 screens
6 screens
2.5 Detectors Menu
2.5.1 Vehicle Detectors Options
2.5.2 Vehicle Detectors Timing
2.5.3 Detectors Call Phase
2.5.4 Detectors Switch Phase
2.5.5 Pedestrian Detectors
2.5.6 Enhanced Vehicle Detectors
2.5.5 Enhanced Ped Detectors
4 screens
8 screens
2 screens
2 screens
64 screens
8 screens
2.6 Preemption Menu
2.6.1 Enables/Inputs
2.6.2 Entry
2.6.3 Track Clearance
2.6.4 Dwell / Cyclic
2.6.5 Exit
6 screens
6 screens
6 screens
6 screens
6 screens
2.7.1 Timing Plans
2.7.2 Signal Plans
2.7.3 Preemption
2.7.4 Interval Skipping
16 screens
32 screens
2.7.2 Interval Menu
2 screens
2.8 Transit Priority Menu
2.8.1 Unit Parameters
2.8.2 Run Parameters
2.8.3 Action Plans
2.8.4 Run Configuration
2.8.5 Queue Jumping
2.8.6 Split Table
2.7.1 Timing Plan Menu
2.7.1.1 Cycle/Offset/Split Data
2.7.1.2 Timing Plan Setup
2.7 Interval Menu
2.7.2.1 Interval Modifiers
2.7.2.2 Channel-Interval Mapping 2×4 matrix of screens
2.7.2.3 Output-Interval Mapping 11×4 matrix of screens
2.7.3.2 Track Intv’l Data Menu
2.7.3 Preempt Int’vls
48 screens
8×8 matrix
6 screens
16 screens
2.7.3.2.1 Track Intv’l Time
2.7.3.2.2 Track Channels-to-Intv’ls
2.7.3.2.3 Track Outputs-to-Intv’ls
6 screens
2.7.3.1 Modifiers
2.7.3.2 Track Interval Data
2.7.3.3 Dwell Interval Data
2.7.3.4 Exit Interval Data
2.7.3.3 Dwell Intv’l Data Menu
2.7.3.3.1 Dwell Intv’l Time
2.7.3.3.2 Dwell Channels-to-Intv’ls
2.7.3.3.3 Dwell Outputs-to-Intv’ls
3.0 System Maintenance
3.1.0 Database Utilities Menu
3.1 Database Utilities
3.2 Copy Database Data
3.3 Enter Diagnostics Mode
3.1.0
3.1.1
3.1.2
3.1.3
3.1.4
3.1.5
3.1.6
3.1.7
Remove ALL Flash Data
8Ph Sequential
4Ph Dual Rng Main/4Ph Sequential Side
8Ph Quad-Left Dual Ring
4Ph Sequential Main/4Ph Dual Rng Side
Exclusive Pedestrian
Coordinated 8Ph Quad-Left
8Ph Quad-Left Preempt (Opticom Style)
3.2.1 Actuated Data
3.2.2 Interval Data
Diagnostics Mode Warning Screen
“Previous”
4.0 Log Menu
4.1 Controller Message Log
4.2 NTCIP Event Log
4.3.1 Setup Logging Options
4.3.2 View Log
9 screens
3 screens
“Next”
6 screens
2.7.3.4 Exit Intv’l Data Menu
2.7.3.4.1 Exit Intv’l Time
2.7.3.4.2 Exit Channels-to-Intv’ls
2.7.3.4.3 Exit Outputs-to-Intv’ls
Return from these screens requires a controller restart
Diagnostics Menu
3.2.0 Copy Data Menu
6 screens
1. Inputs/Outputs Test
2. Comms
3. Memory Test (RAM, SRAM, Flash)
4. Time Test (RTC)
5. USB (Write/Read)
6. SD Card Test
7. Update Firmware
6 tests
7 tests
5 tests
ATC FW Loader v2.4
6 screens
Peek Traffic Corporation
2906 Corporate Way
Palmetto, FL 34221
ph: (941) 845-1200
toll free in U.S.: (800) 245-7660
fax: (941) 845-1504
email: [email protected]
web: www.peektraffic.com
81-1285