Embed Size (px)
Citation preview
1
INTELIGHT™
MaxTimeTM
TRAFFIC CONTROLLER
SYSTEM SOFTWARE
Technical Reference Manual
MaxTimeTM Technical Reference Manual
This manual covers all configurations
Rev. Number 1.6.8
Document Number: MAN0012, Rev. B
Date of Last Revision July 3, 2012
Copyright © 2012, Intelight, Inc.
All rights reserved.
Printed in the United States of America
Copyrights and Trademarks The Intelight™ and MaxTime™ names are trademarks of Intelight, Inc.
Other products or company names mentioned herein may be the trademarks or registered trademarks of their respective companies.
Reproduction Rights This manual contains proprietary information and is furnished for the sole purpose of assisting in the installation, use, and maintenance support of the Intelight, Inc. products described herein. Permission to reproduce or otherwise use portions of the material presented herein is reserved. Intelight, Inc. reserves the right to make changes in the contents of this document without warning and assumes no responsibility for any damages, direct or consequential, caused by relying on this document.
2
Disclaimers Intelight, Inc. shall not be liable for technical or editorial errors or omissions contained herein; nor for incidental or consequential damages resulting from the furnishing, performance or use of this material.
Intelight, Inc. shall not be liable for damages due to delays in deliveries or use of the products described herein and will in no event be liable for incidental or consequential damages of any kind, whether arising from contract, tort, negligence, including, but not limited to, loss of goodwill, overhead or other like damages.
Changes and Addendum Information and specifications contained in this document are subject to change without prior notice and do not represent a commitment on the part of Intelight, Inc. However, Intelight, Inc. may provide changed material as separate sheets included with this manual or separately in the form of a change package, as it deems necessary.
Contact Information Intelight, Inc. 3450 S. Broadmont Drive Suite 126 Tucson, Arizona USA 85713 Phone: 1-520-795-8808 Fax: 1-520-795-8811 Web: www.intelight-its.com To contact Intelight by e-mail:
• Sales: [email protected] • Customer Service: [email protected] • Technical Support: [email protected]
3
Intelight™ Warranty Information For a period of 90 days following delivery to the contracting End-User agency, Intelight, Inc. will correct errors present at time of delivery which do not conform to the latest Intelight, Inc. last specifications published prior to Buyer’s acceptance.
Product specifications as defined supersede previous specifications and are complete. Any parameter that is not specifically defined in the specifications is expressly excluded from the warranty. This warranty does not apply to any product which have been subject to alteration, copied or if the software has been resold to others.
Intelight’s sole obligation to Buyer for products failing to meet specifications shall be, at Intelight’s discretion, to repair or replace the non-conforming product.
Following the warrantee period, End-User agency may continue to receive maintenance services by execution of an Intelight, Inc. Software Maintenance Agreement for the subject software.
THE FOREGOING WARRANTY AND REMEDIES ARE EXCLUSIVE A ND ARE MADE EXPRESSLY IN LIEU OF ALL OTHER WARRANTIES EXPRESSED OR IMPLIED, EITHER IN FACT OR BY OPERATION OF LAW, STATUTORY OR OTHERWISE , INCLUDING WARRANTIES OR MERCHANTABILITY AND FITNESS FOR USE. INTELIGHT, INC. NEITHER ASSUMES NOR AUTHORIZES ANY OTHER PERSON TO ASSUME F OR IT ANY OTHER LIABILITY IN CONNECTION WITH THE SALE, INSTALLATION OR USE OF ITS PRODUCTS AND INTELIGHT, INC. MAKES NO WARRANTY WHATSOEVER FO R PRODUCTS NOT MANUFACTURED BY INTELIGHT, INC.
Product Returns If, after inspection, you note any product discrepancies, please contact us promptly within warrantee period.
All items returned to Intelight require a Return Material Authorization number (RMA). Please contact Intelights’ Service department to request an RMA number.
4
Intelight™ ATC Product Configuration Guide The Intelight™ Advanced Transportation Controller (ATC) Software systems are designed for use inside a variety of standard controller hardware configurations.
A suffix applied to the model number identifies the configuration ID as shown below:
MaxTime™
Hardware/OS Configuration
2070 = Caltrans TEES Hardware w/ OS-9
ATC = Joint Committee ATC Engine Board Hardware w/ Linux
Options
/AC - Adaptive Control (requires ATC hardware w/ Linux OS configuration and peer to peer IP signal interconnect network)
/WS - Web Server – Implemented on the Controller (requires ATC hardware w/ Linux OS configuration)
/OSR - On-Street Relay Master (requires ATC hardware w/ Linux OS configuration and WS option at Master Station)
5
Table of Contents 1 Overview .......................................... ..................................................................................... 14
1.1 About this Manual .......................................................................................................... 14
1.2 About the ATC Hardware History .................................................................................. 14
1.3 The latest ATC Hardware Standards ............................................................................. 15
1.4 Display ........................................................................................................................... 15
1.5 Built-in Display Data Entry Concepts ............................................................................. 15
1.5.1 Numeric Fields ........................................................................................................... 15
1.5.2 Bit fields ..................................................................................................................... 16
1.5.3 Enumeration fields ..................................................................................................... 17
1.5.4 Text Fields ................................................................................................................. 17
1.5.5 Sequence of numeric values ..................................................................................... 18
2 Remote Front Panel ................................ ............................................................................. 19
2.1 Keypad Operation .......................................................................................................... 19
2.2 Navigating Menus .......................................................................................................... 20
2.3 Navigating Grids and Edit Controls ............................................................................... 20
2.3.1 Using the Soft Key Bar .............................................................................................. 21
2.3.2 Editing Numeric Fields ............................................................................................... 21
2.3.3 Editing Text Fields ..................................................................................................... 22
2.3.4 Editing Bitfield Groups ............................................................................................... 22
2.3.5 Editing Dropdown Lists .............................................................................................. 23
2.3.6 Completing Confirmation Boxes ................................................................................ 23
3 Getting Started ................................... .................................................................................. 24
4 Installing a New Version of MaxTime™ Software ..... ........................................................ 27
5 Main menu ......................................... .................................................................................... 28
6 Status Menus ...................................... .................................................................................. 29
6.1 Summary Screen ........................................................................................................... 30
6.1.1 Summary screen coordination status ........................................................................ 31
6.1.2 Summary screen Phase Status ................................................................................. 32
6.1.3 Summary Screen phase calls .................................................................................... 33
6.1.4 Summary screen Overlap Status ............................................................................... 33
6.2 Unit Coord Status .......................................................................................................... 34
6.2.1 Main Status ................................................................................................................ 35
6.2.2 Coord Status .............................................................................................................. 36
6.3 Phases ........................................................................................................................... 37
6.3.1 Ring Status ................................................................................................................ 38
6.3.2 Phase Status ............................................................................................................. 39
6
6.4 Detectors ....................................................................................................................... 40
6.4.1 Vehicle Detectors ....................................................................................................... 40
6.4.2 Vehicle Detector Alarms ............................................................................................ 41
6.4.3 Volume Occupancy .................................................................................................... 42
6.4.4 Ped Detectors Alarms ................................................................................................ 43
6.5 Overlap Status ............................................................................................................... 43
6.5.1 Overlap Timing .......................................................................................................... 44
6.5.2 Overlap Colors ........................................................................................................... 46
6.6 Recorded Splits ............................................................................................................. 47
6.7 Preemption Status ......................................................................................................... 47
6.8 Alarms ............................................................................................................................ 48
6.8.1 Short Alarm ................................................................................................................ 48
6.8.2 Unit Alarm 1 ............................................................................................................... 49
6.8.3 Unit Alarm 2 ............................................................................................................... 50
6.9 Channels ........................................................................................................................ 51
6.10 Input Status .................................................................................................................... 52
6.11 Output Status ................................................................................................................. 52
6.12 Peer ............................................................................................................................... 52
6.13 Master ............................................................................................................................ 53
6.13.1 Sections ................................................................................................................. 54
6.13.2 Controllers ............................................................................................................. 55
6.13.3 Detectors ............................................................................................................... 56
6.14 Prioritor .......................................................................................................................... 58
6.15 Cabinet Status ............................................................................................................... 60
7 Controller Menu ................................... ................................................................................. 62
7.1 Unit Parameters ............................................................................................................. 63
7.2 Phase Menu ................................................................................................................... 64
7.2.1 Phase Times .............................................................................................................. 64
7.2.2 Phase Options ........................................................................................................... 69
7.2.3 Phase Configuration .................................................................................................. 73
7.2.4 Phase Times Copy .................................................................................................... 74
7.3 Sequence ....................................................................................................................... 75
7.4 Detector ......................................................................................................................... 77
7.4.1 Vehicle Detector Parameters ..................................................................................... 77
7.4.2 Vehicle Detector Options ........................................................................................... 80
7.4.3 Volume and Occupancy Settings .............................................................................. 82
7.4.4 Pedestrian Detector Parameters ............................................................................... 82
7
7.5 Overlap .......................................................................................................................... 83
7.5.1 Overlap Phase Settings ............................................................................................. 84
7.5.2 Overlap Parameters ................................................................................................... 85
7.6 Coordination Menu ........................................................................................................ 88
7.6.1 Coordination Parameters ........................................................................................... 88
7.6.2 Patterns...................................................................................................................... 90
7.6.3 Splits .......................................................................................................................... 92
7.6.4 Ring Offsets ............................................................................................................... 93
7.6.5 Split Copy .................................................................................................................. 94
7.7 Scheduler ....................................................................................................................... 94
7.7.1 Schedules .................................................................................................................. 94
7.7.2 Day Plans .................................................................................................................. 95
7.7.3 Actions ....................................................................................................................... 96
7.7.4 Day Plan Copy ........................................................................................................... 97
7.8 Preemptions ................................................................................................................... 98
7.8.1 Preemption Parameters ............................................................................................. 98
7.8.2 Preemption Config ................................................................................................... 100
7.8.3 Preemption Flag ...................................................................................................... 101
7.9 Advanced IO Menu ...................................................................................................... 102
7.9.1 Channels .................................................................................................................. 102
7.9.2 IO Modules .............................................................................................................. 106
7.9.3 Input Pins ................................................................................................................. 109
7.9.4 Output Pins .............................................................................................................. 109
7.9.5 Phase Intervals ........................................................................................................ 110
7.9.6 Pedestrian Intervals ................................................................................................. 111
7.10 Countdown Displays .................................................................................................... 112
7.11 Manual Control ............................................................................................................ 112
7.12 Peer ............................................................................................................................. 113
7.13 Master .......................................................................................................................... 114
7.13.1 Sections ............................................................................................................... 114
7.13.2 Detectors ............................................................................................................. 115
7.13.3 Signatures ............................................................................................................ 116
7.13.4 Signature Criteria ................................................................................................. 117
7.14 Prioritors ...................................................................................................................... 118
7.14.1 Unit Settings ........................................................................................................ 118
7.14.2 Timing Settings .................................................................................................... 118
7.14.3 Prioritor Phases ................................................................................................... 118
8
7.15 Loopback ..................................................................................................................... 119
7.16 User Programs ............................................................................................................. 120
7.16.1 General Concept .................................................................................................. 120
7.16.2 Variables .............................................................................................................. 120
7.16.3 User programs Description .................................................................................. 120
7.16.4 Operations ........................................................................................................... 122
7.16.5 Examples ............................................................................................................. 125
8 Administration Menu ............................... ........................................................................... 127
8.1 Unit Information ........................................................................................................... 128
8.2 Communication ............................................................................................................ 129
8.3 IP Settings ................................................................................................................... 129
8.3.1 Serial Settings .......................................................................................................... 129
8.3.2 NTCIP Settings ........................................................................................................ 131
8.3.3 SNMP Statistics ....................................................................................................... 131
8.4 Date/Time .................................................................................................................... 134
8.5 Database Management ............................................................................................... 135
8.5.1 Save Database ........................................................................................................ 135
8.5.2 Reset Database ....................................................................................................... 136
8.5.3 Copy Database From USB ...................................................................................... 136
8.5.4 Copy Database To USB .......................................................................................... 136
8.6 Event logs .................................................................................................................... 136
8.7 Front Panel .................................................................................................................. 137
8.8 Onboard Diagnostics ................................................................................................... 137
8.9 App management ........................................................................................................ 138
9 Web Server User Interface.......................... ....................................................................... 138
10 Optional Components ............................... .................................................................... 140
10.1 Adaptive Control .......................................................................................................... 140
10.1.1 Adaptive Split Tuning ........................................................................................... 140
10.1.2 Adaptive Cycle Tuning ......................................................................................... 140
10.1.3 Adaptive Offset Tuning ........................................................................................ 140
10.2 Traffic Responsive ....................................................................................................... 141
10.2.1 Concept................................................................................................................ 141
10.2.2 Configuration ....................................................................................................... 141
10.2.3 Operation ............................................................................................................. 142
9
Table of Figures Figure 1-Numeric Fields Range Checking Screen ........................................................................ 15
Figure 2-Numeric Fields Example ................................................................................................. 16
Figure 3-Bit fields Example ............................................................................................................ 16
Figure 4-Enumeration Fields Example .......................................................................................... 17
Figure 5-Text Fields Example ........................................................................................................ 17
Figure 6-Text Editor ....................................................................................................................... 18
Figure 7-Sequence of numeric values Example ............................................................................ 18
Figure 8-Main Menu Screen .......................................................................................................... 19
Figure 9-QSI Keypad ..................................................................................................................... 19
Figure 10-Main Menu Selections ................................................................................................... 20
Figure 11-Soft Key Bar .................................................................................................................. 21
Figure 12-Editing Numeric Fields Example ................................................................................... 21
Figure 13-Editing Text Field Example ........................................................................................... 22
Figure 14-Editing Bitfield Group Example ..................................................................................... 22
Figure 15-Editing Dropdown List Example .................................................................................... 23
Figure 16-Confirmation Box Example............................................................................................ 23
Figure 17-Load Database Screen ................................................................................................. 24
Figure 18-Save Configuration Confirmation Screen...................................................................... 25
Figure 19-Save Database Screen ................................................................................................. 25
Figure 20-Typical NEMA 8 Phase Intersection ............................................................................. 26
Figure 21-Typical 8 Phase Ring Detail .......................................................................................... 26
Figure 22-Main Menu Front Panel Screen .................................................................................... 28
Figure 23-Status Menu Front Panel Screen .................................................................................. 29
Figure 24-Status Menu Remote Front Panel Screen .................................................................... 29
Figure 25-Summary Screen .......................................................................................................... 30
Figure 26-Summary Screen coordination status ........................................................................... 31
Figure 27-Summary Screen phase status ..................................................................................... 32
Figure 28-Summary Screen phase calls ....................................................................................... 33
Figure 29-Summary Screen overlap status ................................................................................... 34
Figure 30 - Unit Status Front Panel Screen .................................................................................. 34
Figure 31 – Unit Main Status Front Panel Screen ......................................................................... 34
Figure 32 – Unit Coord Status Front Panel Screen ....................................................................... 35
Figure 33 - Unit Status Remote Front Panel Screen ..................................................................... 35
Figure 34 – Phases Front Panel Screen ....................................................................................... 37
Figure 35 – Phases Remote Front Panel Screen .......................................................................... 37
Figure 36 – Ring Status Front Panel Screen ................................................................................. 38
10
Figure 37 – Phase Status Front Panel Screen .............................................................................. 39
Figure 38 – Detectors Status Front Panel Screen ......................................................................... 40
Figure 39 – Vehicle Detectors Front Panel Screen ....................................................................... 40
Figure 40– Vehicle Detectors Remote Front Panel Screen .......................................................... 41
Figure 41 – Vehicle Detector Alarms Front Panel Screen ............................................................ 41
Figure 42 – Vehicle Detector Occupancy Front Panel Screen ...................................................... 42
Figure 43 – Ped Detector Alarms Front Panel Screen .................................................................. 43
Figure 44 – Overlaps Front Panel Screen ..................................................................................... 43
Figure 45-Overlap Status Remote Front Panel Screen................................................................. 44
Figure 46 – Overlaps Timing Front Panel Screen ......................................................................... 44
Figure 47 – Overlap Colors Front Panel Screen ........................................................................... 46
Figure 48-Preemption Status Front Panel Screen ........................................................................ 47
Figure 49 - Alarms Front Panel Screen ......................................................................................... 48
Figure 50 - Alarm Status Remote Front Panel Screen .................................................................. 48
Figure 51 – Short Alarm Status Front Panel Screen ..................................................................... 48
Figure 52 – Unit Alarm 1 Status Front Panel Screen .................................................................... 49
Figure 53 – Unit Alarm 2 Status Front Panel Screen .................................................................... 50
Figure 54 – Channels Status Front Panel Screen ......................................................................... 51
Figure 55 - Channels Status Remote Front Panel Screen ............................................................ 51
Figure 56 – Input Status Front Panel Screen ................................................................................ 52
Figure 57 – Input Status Front Panel Screen ................................................................................ 52
Figure 58 – Peer Status Front Panel Screen ................................................................................ 52
Figure 59 - Master Front Panel Screen ......................................................................................... 53
Figure 60 – Master Sections Front Panel Screen ......................................................................... 54
Figure 61 - Master Controllers Front Panel Screen ....................................................................... 55
Figure 62 - Mater Detectors Front Panel Screen .......................................................................... 56
Figure 63 – Prioritor Status Screen ............................................................................................... 58
Figure 64 – Prioritor Unit Status Screen ........................................................................................ 59
Figure 65 – Prioritor Status Screen ............................................................................................... 59
Figure 66 – Prioritor Detector Status Screen ................................................................................ 60
Figure 67 - Monitor Status Screen................................................................................................. 60
Figure 68 – Cabinet Comm Statistics Status Screen .................................................................... 61
Figure 69 – User programs Status Screen .................................................................................... 61
Figure 70 – Processing Info Status Screen ................................................................................... 61
Figure 71 – User program custom Screen .................................................................................... 61
Figure 72 - Controller Menu Front Panel Screen .......................................................................... 62
Figure 73 - Controller Menu More Front Panel Screen ................................................................. 62
11
Figure 74 - Controller Menu Remote Front Panel Screen ............................................................. 62
Figure 75 - Unit Parameters Front Panel Screen .......................................................................... 63
Figure 76 - Phase Front Panel Screen .......................................................................................... 64
Figure 77 - Phase Remote Front Panel Screen ............................................................................ 64
Figure 78 - Phase Times Simple mode Front Panel Screen ......................................................... 65
Figure 79 - Phase Times Remote Front Panel Screens................................................................ 65
Figure 80 - Phase Times Extended Mode Front Panel Screen ..................................................... 68
Figure 81 - Phase Options Simple Mode Front Panel Screen ...................................................... 69
Figure 82 - Phase Options Remote Front Panel Screens ............................................................. 69
Figure 83 - Phase Options Extended Mode Front Panel Screen .................................................. 72
Figure 84 - Phase Configuration Front Panel Screen ................................................................... 73
Figure 85 - Phase Configuration Remote Front Panel Screen ...................................................... 73
Figure 86-Phase Times Copy Front Panel Screen ........................................................................ 74
Figure 87 – Sequence Index Selector Front Panel Screen ........................................................... 75
Figure 88 – Sequence Front Panel Screen ................................................................................... 75
Figure 89-Sequence Remote Front Panel Screen ........................................................................ 76
Figure 90 - Detector Front Panel Screen ...................................................................................... 77
Figure 91 – Detector Remote Front Panel Screen ........................................................................ 77
Figure 92 – Vehicle Detector Parameters Front Panel Screen ..................................................... 77
Figure 93 – Vehicle Detector Parameters Remote Front Panel Screen ....................................... 78
Figure 94 – Vehicle Detector Plans Extended Mode Front Panel Screen .................................... 80
Figure 95-Vehicle Detector Options Front Panel Screen .............................................................. 80
Figure 96-Vehicle Detector Options Remote Front Panel Screen ................................................ 81
Figure 97-Volume and Occupancy Settings Screen ..................................................................... 82
Figure 98 - Pedestrian Detector Parameters Front Panel Screen ................................................ 82
Figure 99 - Pedestrian Detector Parameters Remote Front Panel Screen ................................... 82
Figure 100 - Pedestrian Detector Plans Extended Mode Front Panel Screen .............................. 83
Figure 101 - Overlap Front Panel Screen ..................................................................................... 83
Figure 102 - Overlap Phase Settings Front Panel Screen ............................................................ 84
Figure 103 - Overlap Phase Settings Remote Front Panel Screen .............................................. 84
Figure 104 - Overlap Parameters Front Panel Screen .................................................................. 85
Figure 105-Coordination Front Panel Screen ................................................................................ 88
Figure 106-Coordination Remote Front Panel Screen .................................................................. 88
Figure 107-Coordination Parameters Front Panel Screen ............................................................ 88
Figure 108-Coordination Parameters Remote Front Panel Screen .............................................. 89
Figure 109 - Patterns Front Panel Screen ..................................................................................... 90
Figure 110 - Patterns Remote Front Panel Screen ....................................................................... 91
12
Figure 111- Splits Front Panel Screen .......................................................................................... 92
Figure 112- Splits Remote Front Panel Screen ............................................................................. 92
Figure 113- Ring Offsets Front Panel Screen ............................................................................... 93
Figure 114-Scheduler Front Panel Screen .................................................................................... 94
Figure 115-Scheduler Remote Front Panel Screen ...................................................................... 94
Figure 116-Schedules Front Panel Screen ................................................................................... 95
Figure 117-Day Plan Front Panel Screen ..................................................................................... 95
Figure 118 - Actions Front Panel Screen ...................................................................................... 96
Figure 119-Phase Copy Front Panel Screen ................................................................................ 97
Figure 120-Preemptions Front Panel Screen ................................................................................ 98
Figure 121-Preemption Parameters Front Panel Screen .............................................................. 98
Figure 122-Preemption Config Front Panel Screen .................................................................... 100
Figure 123-Preemption Flags Front Panel Screen ...................................................................... 101
Figure 124-Advance IO Front Panel Screen ............................................................................... 102
Figure 125 – Channels Front Panel Screen ................................................................................ 102
Figure 126 - Channel Configuration Front Panel Screen ............................................................ 102
Figure 127-Channel Options Front Panel Screen ....................................................................... 103
Figure 128-Channel Options Per Color Front Panel Screen ....................................................... 104
Figure 129-Channel Concurrency Front Panel Screen ............................................................... 104
Figure 130- Manual Channel Concurrency Front Panel Screen ................................................. 105
Figure 131- Auto Channel Concurrency Front Panel Screen ...................................................... 105
Figure 132- Conflict Monitor Card Front Panel Screen ............................................................... 106
Figure 133-TS2 type 1 for Nema controller Screen ..................................................................... 106
Figure 134-TS2 type 1 for a 2070 controller ................................................................................ 107
Figure 135-TS1 for a Nema controller ......................................................................................... 107
Figure 136-TS1 for a 2070 controller .......................................................................................... 107
Figure 137-Caltran 332 ................................................................................................................ 108
Figure 138-ITS cabinet ................................................................................................................ 108
Figure 139-Simulation ................................................................................................................. 109
Figure 140-Input Pins Front panel Screen .................................................................................. 109
Figure 141-Output Pins Front panel Screen ................................................................................ 110
Figure 142-Phase Intervals Front Panel Screen ......................................................................... 110
Figure 143-Pedestrian Intervals Front Panel Screen .................................................................. 111
Figure 144 – Countdown Displays Front Panel Screen .............................................................. 112
Figure 145 – Manual Control Front Panel Screen ....................................................................... 112
Figure 146 – Peer Front Panel Screen ........................................................................................ 113
Figure 147 – Master Front Panel Screen .................................................................................... 114
13
Figure 148 – Sections Front Panel Screen ................................................................................. 114
Figure 149 – Detectors Front Panel Screen ................................................................................ 115
Figure 150-Signatures Front Panel Screen ................................................................................. 116
Figure 151 - Signature Criteria Front Panel Screen .................................................................... 117
Figure 152 – Prioritor Front Panel Screen ................................................................................... 118
Figure 153 – Timing Settings Front Panel Screen ...................................................................... 118
Figure 154-Prioritor Phases Front Panel Screen ........................................................................ 118
Figure 155-Loopback Front Panel Screen .................................................................................. 119
Figure 156-User Program Description Screen ............................................................................ 121
Figure 157-User Program Statement Operation ......................................................................... 122
Figure 158-User Program Result = A Index B ............................................................................. 122
Figure 159-User Program example, counters ............................................................................. 126
Figure 160-User Program example, counter in seconds ............................................................. 126
Figure 161-User Program example, counter seconds last minute .............................................. 127
Figure 162-Administration Front Panel Screen ........................................................................... 127
Figure 163-Administration Remote Front Panel Screen.............................................................. 128
Figure 164-Unit Information Front Panel Screen ......................................................................... 128
Figure 165-Communication Screen ............................................................................................. 129
Figure 166-IP Settings Front Panel Screen ................................................................................. 129
Figure 167-Serial Settings Screen............................................................................................... 130
Figure 168-NTCIP Settings Front Panel Screen ......................................................................... 131
Figure 169-SNMP Statistics Front Panel Screen ........................................................................ 131
Figure 170-Date and Time Front Panel Screen .......................................................................... 134
Figure 171-Time Zone & DST Front Panel Screen ..................................................................... 134
Figure 172-NTP Settings Front Panel Screen ............................................................................. 135
Figure 173-Database Management Screen ................................................................................ 135
Figure 174-Save Database Front Panel Screen ......................................................................... 135
Figure 175-Load Database Front Panel Screen .......................................................................... 136
Figure 176-Event Logs Front Panel Screen ................................................................................ 136
Figure 177-View Logs Front Panel Screen ................................................................................. 137
Figure 178-Function Keys Front Panel Screen ........................................................................... 137
Figure 179-Web Server Target IP ............................................................................................... 138
14
1 Overview 1.1 About this Manual Intended for traffic signal technical personnel familiar with traffic control application software, this manual describes the advanced features, operations and interface capabilities of the Intelight’s ATC Traffic Controller Applications Software called MaxTime™.
The operational characteristics and terminology herein correspond to North American norms for Traffic Signal Control as generally outlined by National Electrical Manufacture’s Association (NEMA) TS-2. Strict Compliance to NEMA TS-2 is not claimed as TS-2 is a complete Hardware/Software Product Standard and MaxTime™ is a software program that will run on a variety of hardware platforms (NEMA and non-NEMA hardware).
MaxTime™ is a general purpose Traffic Signal Applications embedded software program which is highly customizable with many operational configurations which are defined by user data entries. This manual only describes its general features and configuration options. The User should always bench test the intended configuration(s) for desired functionality and safety testing in the desired equipment and communications environment. For additional detail on special options, consult the appropriate supplemental application software manuals or connected equipment documentation.
It is beyond the scope of this manual to provide operating system tutorials or information about associated hardware platform and peripheral communications equipment. This information should be available in the manuals that accompany those products.
Wherever used herein, the term “2070” applies to 2070 platforms, otherwise this manual is intended for both ATC and 2070 hardware.
NOTICE The information contained in this manual applies only to the Intelight™ MaxTime™ Revision 1.6.7. Because newer revision versions contain additional functions not found in previous versions, use of MaxTime™ software with older database files should not be attempted and may cause unexpected and unsafe results.
1.2 About the ATC Hardware History The ATC is a general purpose computing platform specifically designed for hostile field cabinet environments. Beginning in 1994, Mr. Craig Gardner, President of Intelight™, (working at JHK & Associates at the time) assisted the California Department of Transportation (Caltrans) in defining the requirements and initial Specifications for the 2070 ATC Controller. The first general release of procurement Specification for the 2070 occurred in early 1997. A joint Standards Group sanctioned by National Electrical Manufactures Association (NEMA), American Association of State Highway and Transportation Officials (AASHTO) and Institute of Transportation Engineers (ITE) has adopted a non-agency specific version of the Caltrans 2070 Specifications with only minor editorial and structuring changes as part of the set of Advanced Transportation Controller (ATC) Standards and Guides.
The latest Specifications and Errata for the 2070 ATC are available through the Caltrans TEES Specifications online at http://www.dot.ca.gov/hq/traffops/elecsys/TEES.htm
15
1.3 The latest ATC Hardware Standards
In 2003 Gardner Transportation Systems (a business unit of Siemens E&A Inc.), under contract to ITE, developed a new standard, referred to as the Version 5 ATC which expanded upon the ATC-2070 concept but includes a requirement for Linux OS support requirement as well as higher performance CPU and specific engine board requirements. Version 5.2a of this standard was approved in early 2006 as a recommended Standard by NEMA, ITE, and AASHTO actions as a supplement rather then replacement to the ATC-2070.
Intelight™ is one of the first manufactures to offer equipment configurations addressing both of the ATC-2070 and the ATC (Version 5.2a) Controller Standards thorough a single family of product offerings.
The ATC Joint Committee has also approved drafts of an ATC Applications Programming Interface (API) Standard and a Serially Interfaced ITS Cabinet Standard to compliment its new ATC controller standard. More information concerning these other standards is available from the ITE web site at: http://www.ite.org/standards/atc/
Intelight™’s MaxTime™ is the first Traffic Signal Applications Software designed at it’s inception to operate in both the Caltrans TEES 2070 ATC and the new Joint Standards Committee ATC w/Linux OS Standard Engine Board environments.
1.4 Display Local User interaction with MaxTime™ software is performed through a Keyboard and Display hardware subsystem. Depending on the controller equipment configuration, this Keyboard and Display subsystem may be integral on with the controller unit or configured as a detachable Remote Front Panel (RFP). Regardless of the hardware implementation, the operation of MaxTime™ is the same.
1.5 Built-in Display Data Entry Concepts The user interface provides several types of editable fields: numeric field, bit fields, enumeration fields, text fields and fields containing numeric sequences.
1.5.1 Numeric Fields To edit a numeric field, select the field using the cursor keys, and key in a new number. At any time, if the ESC key is pressed, the new value is discarded and the previous value is restored. The leftmost digit is entered first. Each time a new digit is entered, the previous digits are automatically shifted towards the left. If the value is a decimal number, the decimal point is inserted automatically. Certain basic range checks are done on the fly while entering data. For instance if a value cannot be greater than 99, the user would not be able to enter a value above 99. To validate the number, press the ENTER key or move the cursor to another field. The final range checks are then performed. If the value is not within the correct range, a message will appear during validation. For instance, to edit a Yellow Change time with a minimum value of 3.0 seconds, the following message will appear if the value is not within the correct range.
Figure 1-Numeric Fields Range Checking Screen
Valid range is: 3.0 - 25.5 Press ESC key to continue
16
Example
Figure 2-Numeric Fields Example
To change the Yellow Change value for phase 2, using the arrow keys, we position the cursor to phase 2 - Yellow Change. Let’s say we want to enter a value of 3.5. This can be achieved by directly pressing 3 and 5 and then moving the cursor to another field (or pressing the ENTER key).
1.5.2 Bit fields To edit bit fields, the user may position the cursor on the bit to toggle and toggle its value directly by pressing the ‘+’ key, or the ’-’ key, or the ’Yes’ key, or the ’No’ key. Bits that are OFF are displayed with a dot (‘.’). Bits that are ON are displayed by a letter representing their meaning. For instance for phase options, when an option is enabled, the bit for that option is represented by the last digit of the phase number.
Example
Figure 3-Bit fields Example
Let’s say a user would like to enable phase 9. To do that, the user may position the cursor to the phase enable row and the column for the phase to enable (9), then press the ‘Yes’ key.
1 2 > Phase 12345678901234567890123456 Enable 12345678.................. AutoFlashEnt .......................... AutoFlashExit .......................... NonActua1 .......................... NonActua2 .......................... NonLockDetMem .......................... MinVehRecall .......................... MaxVehRecall .......................... PedRecall .......................... SoftVehRe call ..........................
Phase 1 2 3 4 5 Walk 10 10 10 15 10 Clear 7 20 7 25 7 Min_Green 17 5 5 5 17 Passage 1.0 1.0 1.0 1.0 1.0 Max_1 35 45 10 55 35 Max_2 0 0 0 0 0 Yellow_Change 3.0 3.0 3.0 3.0 3.0
17
1.5.3 Enumeration fields
To edit a parameter displayed as an enumeration, position the cursor on the parameter to edit. Press the ‘+’ key to display the next item and the ‘-’ key to display the previous item in the enumeration. When the desired item is displayed, press ENTER or move the cursor to another field to validate the value. Pressing the ‘ESC’ key cancels the editing and reverts the field to its original value.
Example
Figure 4-Enumeration Fields Example
To change the type of overlap 2 to ‘normal’, move the cursor to the second row, press the ‘+’ key until ‘normal’ is displayed and press ENTER or move the cursor to another field.
1.5.4 Text Fields To edit a parameter in a text field, position the cursor on the text field, and press ENTER. A text Editor appears to edit the string. The editor follows a similar mechanism to that of cell phone text entry, where pressing one key multiple times shows different letters. Using the left and right arrow keys, position the cursor to the character to change. If the cursor is positioned after the end of the string, a blank character is added to the string. The character is now removed. Once the desired character is located on the editor display, press the corresponding digit key until the desired character is displayed. If a character needs to be deleted, position the cursor on the character to display and press the ‘-’ key. Once done, press the ENTER key to validate the text entry.
Example
Figure 5-Text Fields Example
Ring Sequence Data 1 1,2,a,3,4,b 2 5,6,a,7,8,b 3 4 5 6 7
Overlap Type Tr_Gr Tr_Yel Tr_Red > 1 other 0 0.0 0.0 2 other 0 0.0 0.0 3 other 0 0.0 0.0 4 other 0 0.0 0.0 5 other 0 0.0 0.0 6 other 0 0.0 0.0 7 other 0 0.0 0.0
18
Let’s say a user wants to edit Sequence Data for Ring 2, which is a comma delimited text string, and add phase 9 before barrier b. To achieve this, position the cursor on the second row. Press ENTER, a text editor appears containing the original text. In this case: ‘5,6,a,7,8,b ’.
Figure 6-Text Editor
Move the cursor to the end of the text using the right arrow key, and position the cursor at character ‘b’. Press the ‘9’ key, then press the right arrow key to add a new character. Press the ‘1’ key to add a coma ‘,’. Press the right arrow key again to add a new character. Press the ‘2’ key. A character ‘a’ is displayed. Press the ‘2’ key again. A character ‘b’ is displayed. Press ENTER. The editor closes and the new sequence is now 5,6,a,7,8,9,b.
1.5.5 Sequence of numeric values To edit a sequence of numeric values, position the cursor on the desired field using the left and right arrow keys and press ENTER. The field is now in edit mode and the left and right arrow keys now navigate through the sequence. To add a new number in the sequence, move the cursor to the end of the sequence and press the right arrow key. A new number is added. To delete one of the numbers, navigate to the number to delete using the left and right arrow keys and press the ‘-’ key. To edit one of the numbers, position the cursor on the number to edit and type in the new value as for a regular numerical field. If the sequence is larger than the size of the control, the field will scroll automatically. If some numbers are available on the left, a ‘<’ is displayed on the left of the control, if some numbers are available on the right, a ‘>’ is displayed on the right.
Example
Figure 7-Sequence of numeric values Example
Let’s say that a user would like to change the Included Phases numeric sequence for overlap 1 from ‘1, 2’ to ‘1,2,5,6’. The steps are: Position the cursor at the field that needs to be edited. Press ENTER. The cursor is on number ‘1’. Press the right arrow key to move the cursor to phase number 2. Press the right arrow key again to add a new number. Number ‘1’ is added automatically. To change it, type in 5, then
Overlap Included Phases Modifier Phases 1 1, 2 2 3 4 5 6 7
5,6,a,7,8,b<- ( ,1)(abc 2)(def 3) (ghi 4)(jkl 5)(mno 6) (pqrs7)(tuv 8)(wxyz9)
19
press the right arrow to get a new number and type 6. Press ENTER to validate the entry. The new sequence is now 1,2,5,6.
2 Remote Front Panel The Remote Front Panel is shipped with all of the necessary software preinstalled. The supplied DB-9 terminal cable should be connected to the C60S port on the front panel of the controller unit. This cable provides both serial communication and power to the Remote Front Panel. Once connected, the terminal will be ready to operate. Upon power-up, with MaxTime™ installed on the controller, the User will be presented with the MaxTime™ Main Menu as shown below in Figure 1:
Figure 8-Main Menu Screen
2.1 Keypad Operation
Figure 9-QSI Keypad
20
The primary data keys for data entry are the 10 numeric keys and the UP, DOWN, LEFT, and RIGHT arrow keys. Each key has a normal state and a shifted state. The shifted state can be useful for entering alphanumeric characters into a text entry box.
If the keypad is not responding make sure the SHIFT key is not active. The arrow keys, ENTER key, and ESC key for example only work in normal mode when the SHIFT key is not active.
2.2 Navigating Menus
Figure 10-Main Menu Selections
The numeric keys 0-9 are used to navigate the MaxTime™ menus. A single key press will select the desired menu item (pressing the ENTER key is not required). The ESC key is used to return to the previous submenu.
2.3 Navigating Grids and Edit Controls Use the UP, DOWN, LEFT, RIGHT arrow keys to set the focus (highlighted region) on the desired grid cell or edit box. In addition to the standard cursor keys the DIAGONAL UP and DIAGONAL DOWN keys will issue a page up or page down command for scrolling large tables up or down one page at a time.
21
2.3.1 Using the Soft Key Bar
Figure 11-Soft Key Bar
Many screens contain a soft key bar at the bottom of the screen. This region contains a context sensitive menu that may be different for each screen. Each soft key is selected by pressing F1-F5 on the keypad. In the example above pressing F1 would page the grid one screen to the left and pressing F2 would page one screen to the right. In most grid screens the first two soft keys are used to move the grid up, down, left, or right one screen at a time.
2.3.2 Editing Numeric Fields
Figure 12-Editing Numeric Fields Example
Numeric values in either single edit boxes or grids behave the same. To edit a value, move the cursor to the selected cell or edit box. Then begin entering a new value using the numeric keys 0-9. As soon as the first key is entered the cell or edit box will switch to edit mode and display a cursor. To save the new value press the ENTER key or press one of the arrow keys to move the focus to another control. To revert back to the original value without saving press the ESC key.
22
2.3.3 Editing Text Fields
Figure 13-Editing Text Field Example
To edit a text field simply move the highlighted region to the desired field and begin entering new characters. This will switch the text field to edit mode and overwrite the existing value with the new characters. Alternatively, pressing the ENTER key first will switch the text field to edit mode and allow the User to modify the current value. Unlike numeric fields a text field can not be saved be moving the focus with the arrow keys. Instead pressing the arrow keys when the control is in edit mode will move the cursor left or right. Additionally, when editing a text field a new set of soft keys will appear at the bottom of the screen. These soft keys can clear the entire field, move to the front, back, or bring up a popup symbol table that displays all of the available characters. To save a new value press the ENTER key while the control is in edit mode or press ESC to revert to the original value without saving.
2.3.4 Editing Bitfield Groups
Figure 14-Editing Bitfield Group Example
Bitfield groups are a collection of flags that specify if a particular feature is enabled or disabled. Bitfields are organized in groups of 10. The column headers along the top of the grid specify the index ranges associated with each group. If a feature is enabled a “X” will be displayed in the appropriate group. Correspondingly, a “.” indicates that a particular feature is off or disabled.
23
Bitfields can be edited by moving focus to the desired group and then pressing a numeric key (1 for index 1 through 0 for index 10).
2.3.5 Editing Dropdown Lists
Figure 15-Editing Dropdown List Example
Dropdown lists allow the User to select one of several different enumerated values. To change the current value move the highlighted region to the desired dropdown list and press ENTER. The list will switch to edit mode and display all of the available enumerations. Press the UP and DOWN arrow keys to navigate the list. Additionally, if the list is larger than can be fit on the screen the DIAGONAL UP and DIAGONAL DOWN keys can be used to page up or page down. Some dropdown lists display “other” for the first enumeration. This is a special NTCIP state that is used for representing values that are not included in the list. The dropdown list can not be explicitly set to “other” but it will display other if the associated field was changed by some other means to a value that is not included in the list.
2.3.6 Completing Confirmation Boxes
Figure 16-Confirmation Box Example
Confirmation boxes are displayed before special operations that require user input. Press the LEFT or RIGHT arrow keys to move the focused region then press ENTER to select the desired
24
choice. In general, most confirmation screens will have the focus set to “OK” by default so in most cases simply pressing ENTER will suffice.
3 Getting Started The User should first read this manual in its entirety and also become familiar with the intended target equipment configuration.
Standard setup configurations have been predefined by Intelight™ to allow the User to quickly and efficiently get started using the MaxTime™ software with a minimal amount of initial data entry required. Current standard configurations include:
� Dual Ring, 8 Phase, 2070-1B CPU in Standard 332 Cabinet � Dual Ring, 8 Phase, ATC in Intelight™-888 Cabinet
To get started quickly with one of these configuration setups, the User might select, for example, an 8 Phase, 2 Ring setup file for the 2070 with 332 cabinet configurations. To do this, the User selects the Administration option from the main Menu then selects Load Database . The User will be presented with a List of Database Initialization Files to select from (see Figure blow).
Figure 17-Load Database Screen
The Load Database screen displays both standard configurations and user created initialization files. After selecting the appropriate file, the user will be prompted to restart the controller (see Figure below), upon which the settings of the initialization file will be read into the controller’s database and override the current controller setting (Warning – This initialization permanently erases all current setting in the controller and can not be undone).
25
Figure 18-Save Configuration Confirmation Screen
If the User wishes to save the current controller database for use later as an Initialization File or for backup purposes, the Save Database menu option can be selected. The User may enter a new filename using the keypad or may overwrite a previous user created initialization file by selecting a previous file in the list box and pressing the Save button on the soft key bar. User created initialization files may also be deleted at any time by pressing Delete on the soft key bar.
Figure 19-Save Database Screen
It should be noted that Intelight’s standard distribution Initialization Files are Read Only. These supplied initialization files can not be changed by the User. The “Default” name prefix is used to distinguish standard initialization files from user created files. The number of Initialization Files which can be stored in Flash is memory size dependent. (The maximum limit for all configurations is 15 total Initialization Files).
The most typical standard configuration is a Dual Ring 8 Phase intersection. This configuration follows NEMA standard Dual Ring 8 Phase nomenclature as follows:
26
Figure 20-Typical NEMA 8 Phase Intersection
Figure 21-Typical 8 Phase Ring Detail
The predefined MaxTime™ Ring Sequence configuration with this initialization selection is:
Ring Sequence Data
1 1,2,a,3,4,b
2 5,6,a,7,8,b
27
4 Installing a New Version of MaxTime ™ Software
New versions of MaxTime™ software can be installed using the Ethernet connection. Before continuing, make sure that the TCP/IP settings of the controller have been properly configured. Specifically, the controller must respond to ping requests from the computer that will be used to install MaxTime™. The IP Address of the controller can be changed via the Remote Front Panel by accessing the Administration screen (3) followed by the Communication screen (2).
Unzip the MaxTime™ distribution archive and run the “install.bat” installation file. You will be prompted to enter the IP address of the controller. Assuming the network settings have been configured correctly, the install script will continue without further user intervention. The script will transfer the new version to the controller. The database from the previous version will not be removed. All settings from the old version will automatically be migrated to the new version.
28
5 Main m enu
Figure 22-Main Menu Front Panel Screen
The main menu shows up at startup. At the top of the main menu, the MaxTime version and build number are displayed. The Agency, main street and side street are also displayed if data is entered in those fields.
The MaxTime menus are organized in 3 main sections:
The Status sub menu let users view and control all the traffic control features.
The Controller sub menu let users edit all the parameters related to traffic.
The Administration sub menu let users manage settings that are not directly related to traffic.
Intelight MaxTime 1.6.8 #build Main_Street & Side_Stre et Agency 1.Status 2.Controller 3.Administration
29
6 Status Menus
Figure 23-Status Menu Front Panel Screen
Figure 24-Status Menu Remote Front Panel Screen
Status 1.Summary 2.Unit Coord Status 3.Phases 4.Detectors 5.Overlaps 6.Recorded Splits 7.Preempt Status 8.Alarms 9.More
Status 1.Channels 2.Input Status 3.Output Status 4.Peer 5.Master 6.Prioritor 7.Cabinet 8.User Programs
30
6.1 Summary Screen The summary screen is composed of several main sections: Date and Time, Coordination status, Ring/Phase status, Phase calls status and control and Overlap Status.
Figure 25-Summary Screen
Fri 10/08 13:52:28 Man P1 102/120 1 1[2]3,4 GrDwl 0.0 Y 1Fo3 2 5[6]7,8 GrDwl 0.0 Y 1Fo7 Phs 12345678.. .......... Veh .CM..CM... .......... Ext .......... .......... Ped .......... .......... Ovl
Current Date and Time Coordination Status
Ring and Phase Status
Phase Calls Status and Control
Overlap Status
31
6.1.1 Summary screen coordination status
Figure 26-Summary Screen coordination status
Control Source This field indicates how the controller unit is controlled if there is a pattern running (or in software free or flash) Oth: other, Sys: systemControl, Std: systemStandby, Bck: backupMode, Man: manual, TOD: timebase, Int: interconnect, IBk: interconnectBackup Current Coord Pattern This is the current pattern that the controller is running. If the current pattern is not the one that is selected, the selected pattern also appears right next to the current pattern, separated by a dash. For instance, if the controller is running pattern 1 but the user manually changes to pattern 2, the coordination status will temporarily display: Man P1-2 Local Cycle Counter This field indicates the current position in the local cycle in seconds.
Cycle Length This field indicates the length of the current cycle in seconds.
Coordination Errors This field indicates why the controller can’t go to coordination.
Fri 10/08 13:52:28 Man P1 102/120 1 1[2]3,4 GrDwl 0.0 Y 1Fo3 2 5[6]7,8 GrDwl 0.0 Y 1Fo7 Phs 12345678.. .......... Veh .CM..CM... .......... Ext .......... .......... Ped .......... .......... Ovl
Local Cycle Counter
Current Coord Pattern
Control Source
Cycle length
Error
32
TR means transition. The CU has a pattern command but is cycling to a point to begin coordination. IN means input. One of the CU inputs causes it to not respond to coordination. CO means Coordination. The CU programming for the called pattern is to run Free. BP means bad Plan. The called pattern is invalid. BC means Bad Cycle Time. The specified cycle time is not adequate to service the all phase minimum service requirements. SO means Split Overrun. The sum of the critical path splitTime values exceed the programmed patternCycleTime value IO means Invalid Offset. The programmed patternOffsetTime value exceeds the programmed patternCycleTime value FA means Failed. cycling diagnostics have called for Free. MO means mins Overrun. Timing constraints such as Min Green prevents coordination. OT means other. The controller can’t go to coordination for a reason other than those previously listed.
6.1.2 Summary screen Phase Status
Figure 27-Summary Screen phase status
Ring Number Each row represents a ring. The first field of the row is the ring number. The grid is scrollable by pressing the Up or Down arrows.
Current Phase Sequence The current phase sequence of the ring. The active phase is displayed in brackets. The next phase selected by the controller blinks. If the sequence is unusual and there is not enough space to display the full sequence, MaxTime automatically scrolls. It will always display the active phase and the next selected phase and will display as many phases as possible. If the Current Phase Description is hidden by pressing the ‘A’ key, the room is used to expand the displayed sequence.
Current Phase Description For each phase, a description can be entered in the database. Pressing the ‘A’ key hides/shows the description.
1 1[2]3,4 SBTH GrDwl 0.0 Y 1Fo3 2 5[6]7,8 NBTH GrDwl 0.0 Y 1Fo7
Ring Number
Current Phase sequence
Current Phase Description
Current Phase/Ped Interval
Current Interval Timing
Last Termination
Next Termination Timer
33
Current Phase/Ped Interval and Current Interval Tim ing The current vehicle or ped interval is displayed depending on which one is timing. If both vehicle and pedestrian intervals are timing, the pedestrian interval and its timing are displayed.
Last Termination This field indicates the reason why the previous phase was terminated. The values are: G for Gap Out M for Maximum Timeout F for Force Off Y for Yield P for Preempt O for Other
Next Termination Timer This field indicates the reason why the current phase will be terminated (Mx for Max, Fo for ForceOff and Pr for Preempt) and the remaining number of seconds before termination. It also includes an integer representing internal MaxTime calculation.
6.1.3 Summary Screen phase calls
Figure 28-Summary Screen phase calls
Under the ‘Phs ’ field, the phase number is displayed. Only phases that are in a ring sequence are displayed. The ‘Veh ’ field is used to place calls and monitor call status at the same time. A ‘C’ indicates that there is currently a call. An ‘M’ indicates that a call has been placed using the phase control object. It could be from this User Interface or from a remote call such as software. A call can be placed by moving the cursor using the left and right keys and pressing the ‘+’,’-’,’Yes’ or ‘No’ key to toggle the bit value. Or the call can be placed by pressing on the digit for the phase for which the call is wanted. The ‘Ext ’ field is used to place an Extended Call on a given phase. The cursor can be moved to this field by pressing the ‘Next’ key. A call can be placed by moving the cursor using the left and right keys and pressing the ‘+’,’-’,’Yes’ or ‘No’ key to toggle the bit value. Or the call can be placed by pressing on the digit for the phase for which the call is wanted. The ‘Ped ’ field is used to monitor the pedestrian calls. A ‘C’ indicates that there is a call.
6.1.4 Summary screen Overlap Status
Ovl Overlap Status
Phs 12345678.. .......... Veh .......... .......... Ext .......... .......... Ped .......... ..........
34
Figure 29-Summary Screen overlap status
In the ‘Ovl’ field, MaxTime displays the list of the overlaps that are green or yellow. Pressing the ‘A’ key will also display the overlap description that is entered in the database, the current interval of the overlap and the current timing of the overlap.
6.2 Unit Coord Status
Figure 30 - Unit Status Front Panel Screen
Ctrl_Src: Other, Sys Ctrl, Sys Standby, Backup Mode, Manual, Timebase, interconnect, int Backup, LangisPattern, LangisAdapt
Select_Mode: Not used, Free, RedFlash, Flash, pattern 1-128
Act_Mode: Not used, RedFlash, Flash, Pattern 1-128
Day Plan: 1-20
TB Action: 0 (disable), 1-64
Figure 31 – Unit Main Status Front Panel Screen
Cycle
Sync
Free Status: other, coord, commandFree, transitionFree, inputFree, coordFree, badPlan, badCycleTime,splitOverrun, invalidOffset, failed, minsOverrun.
Flash Status: other, notFlash, automatic, localManual, faultMonitor, mmu, startup, preempt.
Cycle Sync Free Status Flash Status 0 0 commandFree notFlash
Ctrl_Src Manual Select_Mode Free Act_Mode Free Day_Plan 1 TB_Action 0
Unit Coord Status 1.Main Status 2.Coord Status
35
Figure 32 – Unit Coord Status Front Panel Screen
Figure 33 - Unit Status Remote Front Panel Screen
6.2.1 Main Status
Control Source • systemControl - control by master or central UTC computer commands.
• systemStandby - control by local based on master or central command to use local control.
• backupMode - Backup Mode (see Terms).
• Manual - control by entry other than zero in coordOperationalMode.
• Timebase - control by the local controller’s Time Base scheduler.
• Interconnect - control by the local Interconnect inputs.
• interconnectBackup – fallback control to local TBC scheduler due to invalid Interconnect inputs or loss of sync.
• LangisPattern – control by the Langis background plan generator adaptive software
• LangisAdapt – control by the Langis adaptive real-time software
• Other - control by a source other than those listed above.
Select Mode Displays the selected or requested operational mode: Coord Pattern 1-253, Free, or Flash
Active Mode Displays the active operational mode: Coord Pattern 1-253, Free, or Flash
Day Plan
36
Displays the active day plan table as selected by the local TBC scheduler
TB Action Displays the active time base action as selected by the local TBC scheduler.
6.2.2 Coord Status
Local Cycle Represents the current position in the local coordination cycle of the running pattern (0 to 510 sec). This value counts down from patternCycleTime to Zero. This value may exceed the patternCycleTime during a coord cycle with offset correction (patternCycleTime + correction).
Sync (Master Cycle) Represents the time since the system Sync reference point for the running pattern (0 to 510 sec). This value counts down from the current Cycle Time selected to the next system reference Sync point (patternCycleTime). This value may exceed the patternCycleTime during a coord cycle in which the system reference point has changed.
Free Status • notFree: The unit is not running in free mode.
• commandFree: the current pattern command is the Free mode pattern.
• transitionFree: the CU has a pattern command but is cycling to a point to begin coordination.
• inputFree: one of the CU inputs cause it to not respond to coordination.
• coordFree: the CU programming for the called pattern is to run Free.
• badPlan: Free - the called pattern is invalid.
• badCycleTime: the pattern cycle time is less than adequate to service the minimum requirements of all phases.
• splitOverrun: Free - the sum of the critical path splitTime’s exceed the programmed patternCycleTime value.
• invalidOffset: Free - reserved / not used
• failed: cycling diagnostics have called for Free.
• other- the Controller Unit is failed for some other reason.
Flash Status • notFlash - the Controller Unit is not in Flash
• automatic -the Controller Unit is currently in an Automatic Flash state defined by a Pattern Selection of 255.
• LocalManual - the Controller Unit Local Flash input is active, MMU Flash input is not active, and Flash is not commanded by the Master.
• FaultMonitor - the Controller Unit is currently detecting a Fault Monitor State.
• MMU - the Controller Unit is sensing the Conflict Monitor Unit Flash input as active and the CU is not in Start-Up Flash.
• Startup - the Controller Unit is currently timing the Start-Up Flash period.
37
• Preempt - the Controller Unit is currently detecting the preempt Flash state.
• Other- the Controller Unit is in flash for some other reason.
6.3 Phases
Figure 34 – Phases Front Panel Screen
Figure 35 – Phases Remote Front Panel Screen
Phases 1.Ring Status 2.Phase Status
38
6.3.1 Ring Status
Figure 36 – Ring Status Front Panel Screen
Phs – READ ONLY This number identifies the currently active phase for this ring number. 0 = none active.
PhsInterval – READ ONLY This object identifies the currently active vehicle interval for this ring—{ notActive (1), dlyGreen (2), preGreen (3), minGreen (4), grnExtn (5), grnDwell (6), preClear (7), yelChange (8), redClear (9), redDwell (10), barrierHold (11) }
PhsTm – READ ONLY This object provides the current value of the vehicle interval down count timer for this ring.
PedInterval – READ ONLY This object identifies the currently active pedestrian interval for this ring.—{ notActive (1), dlyPed (2), walk (3), walkDwell (4), flshDtWlk (5), dWalk (6) }.
Rg Phs Intvl Up Down CoordCmd > 1 2 GrDwl 16.4 0.0 0 2 6 GrDwl 16.4 0.0 0 3 0 0 0.0 0.0 4 0 0 0.0 0.0 5 0 0 0.0 0.0 6 0 0 0.0 0.0 7 0 0 0.0 0.0 8 0 0 0.0 0.0 9 0 0 0.0 0.0 10 0 0 0.0 0.0 11 0 0 0.0 0.0 12 0 0 0.0 0.0 13 0 0 0.0 0.0 14 0 0 0.0 0.0 15v0 0 0.0 0.0
Ped intvl Up Down Phs Seq Nxt > dWalk 117.7 0.0 1,2,3,4 3 dWalk 117.7 0.0 5,6,7,8 7 0 0.0 0.0 0 0 0.0 0.0 0 0 0.0 0.0 0 0 0.0 0.0 0 0 0.0 0.0 0 0 0.0 0.0 0 0 0.0 0.0 0 0 0.0 0.0 0 0 0.0 0.0 0 0 0.0 0.0 0 0 0.0 0.0 0 0 0.0 0.0 0 v0 0.0 0.0 0
Rg<LastTerm Dwn Next Term 1 G 9 Fo 1 2 G 9 Fo 5 3 0 0 4 0 0 5 0 0 6 0 0 7 0 0 8 0 0 9 0 0 10 0 0 11 0 0 12 0 0 13 0 0 14 0 0 15v 0 0
39
PedTm – READ ONLY This object provides the current value of the pedestrian interval up count timer for this ring.
Next – READ ONLY This object identifies the phase number of the next phase to be serviced for this ring.
Coord – READ ONLY This object displays the coordination command for this ring.
VehCall Ctrl – ENABLED/DISABLED Phase Vehicle Call Status, when an ‘X’, the Phase vehicle currently has a call for service. When a ‘.’, the Phase vehicle currently does NOT have a call for service.
PedCall Ctrl – ENABLED/DISABLED Phase Pedestrian Call Status, when an ‘X’, the Phase pedestrian currently has a call for service. When a ‘.’, the Phase pedestrian currently does NOT have a call for service.
6.3.2 Phase Status
Figure 37 – Phase Status Front Panel Screen
PhsGrp – READ ONLY The index of the phase group and phase.
Reds – READ ONLY The phases that are currently red.
Yellows – READ ONLY The phases that are currently yellow.
Greens – READ ONLY The phases that are currently green.
Veh Call – READ ONLY Phase Vehicle Call Status, when equal to ‘1,2,etc.’, the Phase vehicle currently has a call for service. When equal to ‘.’, the Phase vehicle currently does NOT have a call for service.
Phs Grp 1 2 3 > 12345678 12345678 12345678 Reds 1.345.78 ........ ........ Yellows ........ ........ ........ Greens .2...6.. ........ ........ Veh Call 12345678 ........ ........ Ctrl ........ ........ ........ ExtCtrl ........ ........ ........ DWalk 12345678 ........ ........ Ped Clr ........ ........ ........ Walk ........ ........ ........ Ped Call ........ ........ ........ Ctrl ........ ........ ........
40
Crtl – ENABLED/DISABLED Places a call on a phase. Those calls are temporary. They get cleared after a power cycle and are affected by the backup timer.
ExtCrtl – READ ONLY Places an extended call on a phase. Those calls are temporary. They get cleared after a power cycle and are subject to the backup timer..
DWalk – READ ONLY The phases that are currently don’t walk.
Ped Clr – READ ONLY The phases that are currently ped clear.
Walk – READ ONLY The phases that are currently walk.
Ped Call – READ ONLY Phase Pedestrian Call Status, when equal to ‘1,2,etc.”,, the Phase pedestrian currently has a call for service. When equal to ‘.’, the Phase pedestrian currently does NOT have a call for service.
Crtl – ENABLED/DISABLED Places a pedestrian call on a phase. Those calls are temporary. They get cleared after a power cycle and are affected by the backup timer.
6.4 Detectors
Figure 38 – Detectors Status Front Panel Screen
6.4.1 Vehicle Detectors
Figure 39 – Vehicle Detectors Front Panel Screen
Detectors 1.Vehicle Detectors 2.Vehicle Detector Alarms 3.Volume Occupancy 4. Ped Detectors Alarms
Det Gr 1 2 3 > 12345678 12345678 12345678 Active ........ ........ ........ Alarms ........ ........ ........
41
Figure 40– Vehicle Detectors Remote Front Panel Scr een
Active – READ ONLY The detection status of each detector associated with the group. Each detector shall be represented as ON (‘X’) or OFF (‘.’).
Alarm – READ ONLY The alarm status of the detectors associated with the group. Each detector alarm status shall be represented as ON (‘X’) or OFF (‘.’). If any detector alarm is active the option shall be set to ON. If a detector alarm is not active the option is set to OFF.
6.4.2 Vehicle Detector Alarms
Figure 41 – Vehicle Detector Alarms Front Panel Scr een
No Activity – READ ONLY This detector has been flagged as non- operational due to lower than expected activity by the CU detector diagnostic. This alarms is ON if the value is ‘X’ and OFF if the value is ‘.’.
Max Presence – READ ONLY This detector has been flagged as non- operational due to a presence indicator that exceeded the maximum expected time by the CU detector diagnostic. This alarms is ON if the value is ‘X’ and OFF if the value is ‘.’.
Erratic Output – READ ONLY
1 2 > Det 1234567890123456789012345 No Activity ......................... Max Presence ......................... Erratic Output ......................... Communications ......................... Configuration ......................... Other .........................
42
This detector has been flagged as non- operational due to erratic outputs (excessive counts) by the CU detector diagnostic. This alarms is ON if the value is ‘X’ and OFF if the value is ‘.’.
Communications – READ ONLY Communications to the device (if present) have failed. This alarms is ON if the value is ‘X’ and OFF if the value is ‘.’.
Configuration – READ ONLY Detector is assigned but is not supported. This alarms is ON if the value is ‘X’ and OFF if the value is ‘.’.
Other – READ ONLY The detector has failed due to some other cause. Once set a bit shall maintain its state as long as the condition exists. This alarms is ON if the value is ‘X’ and OFF if the value is ‘.’.
6.4.3 Volume Occupancy
Figure 42 – Vehicle Detector Occupancy Front Panel Screen
Volume – READ ONLY Detector Volume data collected over the Volume / Occupancy Period. This value shall range from 0 to 254 indicating the volume of traffic crossing the associated detector during the collection period. The value 255 shall indicate volume overflow.
Occupancy – READ ONLY The occupancy or detector diagnostic information as follows:
• 0-200: Detector Occupancy in 0.5% Increments
• 210: Max Presence Fault
• 211: No Activity Fault
• 212: Open loop Fault
• 213: Shorted loop Fault
• 214: Excessive Change Fault
• 216: Watchdog Fault
• 217: Erratic Output Fault
Note: The highest numbered fault will be presented if more than one fault is active (i.e. indicate OpenLoop rather than NoActivity).
Det 1 2 3 4 5 6 7 > Volume 0 0 0 0 0 0 0 Occupancy 0 0 0 0 0 0 0
43
6.4.4 Ped Detectors Alarms
Figure 43 – Ped Detector Alarms Front Panel Screen
No Activity – READ ONLY This detector has been flagged as non- operational due to lower than expected activity by the CU detector diagnostic. This alarms is ON if the value is ‘X’ and OFF if the value is ‘.’.
Max Presence – READ ONLY This detector has been flagged as non- operational due to a presence indicator that exceeded the maximum expected time by the CU detector diagnostic. This alarms is ON if the value is ‘X’ and OFF if the value is ‘.’.
Erratic Output – READ ONLY This detector has been flagged as non- operational due to erratic outputs (excessive counts) by the CU detector diagnostic. This alarms is ON if the value is ‘X’ and OFF if the value is ‘.’.
Communications – READ ONLY Communications to the device (if present) have failed. This alarms is ON if the value is ‘X’ and OFF if the value is ‘.’.
Configuration – READ ONLY Detector is assigned but is not supported. This alarms is ON if the value is ‘X’ and OFF if the value is ‘.’.
6.5 Overlap Status
Figure 44 – Overlaps Front Panel Screen
Overlaps 1.Overlap Timing 2.Overlap Colors
1 2 > Det 1234567890123456789012345 No Activity ......................... Max Presence ......................... Erratic Output ......................... Communications ......................... Configuration .........................
44
Figure 45-Overlap Status Remote Front Panel Screen
6.5.1 Overlap Timing
Figure 46 – Overlaps Timing Front Panel Screen
Ovl Interval Down 1 notActive 0.0 2 notActive 0.0 3 notActive 0.0 4 notActive 0.0 5 notActive 0.0 6 notActive 0.0 7 notActive 0.0 8 notActive 0.0 9 notActive 0.0 10 notActive 0.0 11 notActive 0.0 12 notActive 0.0 13 notActive 0.0 14 notActive 0.0
45
Interval – READ ONLY The interval of this overlap as below:
• notActive: overlap not configured
• delay: timer which delays overlap green after start of the parent phase green
• red: overlap is red and not timing any other overlap interval
• green: overlap is displaying the green interval
• trailGreen: overlap is displaying the trailing green interval (overrides parent phase clearances)
• trailYellow: overlap is displaying the trailing yellow interval (overrides parent phase yellow clearance)
• trailRed: overlap is displaying the trailing red interval (overrides parent phase red clearance)
• bridgeGreen: if currently timing a parent phase, and a parent phase is phase next, the overlap displays green during the current parent phase’s clearance time
• clearance: overlap is displaying current parent phase’s clearance intervals
• walk: overlap is displaying the currently timing parent phase’s walk interval
• bridgeWalk: if currently timing a parent phase walk, and a parent phase is phase next, the overlap displays walk during the current parent phase’s clearance time
• pedClear: overlap is displaying the currently timing parent phase’s flash don’t walk (ped clear) interval
• dontWalk: overlap is displaying the currently timing parent phase’s steady don’t walk interval
• blank: overlap red, yellow, and green outputs are dark (not showing)
Down – READ ONLY The time in seconds remaining on this overlap interval.
46
6.5.2 Overlap Colors
Figure 47 – Overlap Colors Front Panel Screen
Reds – ENABLE/DISABLE Overlap Red Output Status, when set to enabled (‘X’), the Overlap Red is currently active. When set to disabled (‘.’), the Overlap Red is NOT currently active.
Yellows – ENABLE/DISABLE Overlap Yellow Output Status, when set to enabled (‘X’), the Overlap Yellow is currently active. When set to disabled (‘.’), the Overlap Yellow is NOT currently active.
Greens – ENABLE/DISABLE Overlap Green Output Status, when set to enabled (‘X’), the Overlap Green is currently active. When set to disabled (‘.’), the Overlap Green is NOT currently active.
Ovl 1 2 12345678 12345678 Reds ........ ........ Yellows ........ ........ Greens ........ ........
47
6.6 Recorded Splits
6.7 Preemption Status
Figure 48-Preemption Status Front Panel Screen
Control – ENABLE/DISABLE
A manual preempt call can be placed by moving the cursor using the up and down keys and pressing the ‘+’,’-’,’Yes’ or ‘No’ key to toggle the bit value. A ‘c’ indicates a call has been placed on the preempt.
State – READ ONLY The current state of the prempt as below:
• other
• notActive: preempt is not currently active
• notActiveWithCall: a call has been logged and the preempt is waiting to start (delay or another preempt is servicing)
• entryStarted: programmed entry phases are currently timing
• trackService: programmed track clearance phases are currently timing
• dwell: preempt is in dwell state. Programmed dwell phases are currently timing
• linkActive: preempt is in active link state if linked preemption routines are programmed
• exitStarted: programmed exit phases are currently timing
• maxPresence: preempt has reached its user-defined maximum presence value and will time out
Phase -1 -2 -3 -4 -5 1 9 9 9 9 9 2 9 9 9 9 9 3 9 9 9 9 9 4 9 9 9 9 9 5 9 9 9 9 9 6 9 9 9 9 9 7 9 9 9 9 9 8 v9 9 9 9 9
Prempt Control State > 1 . notActive 2 . notActive 3 . notActive 4 . notActive 5 . notActive 6 . notActive 7 . notActive 8 v. notActive
Prempt<IntvlDnTm MaxDnTm DetStatus 1 0.0 0.0 . 2 0.0 0.0 . 3 0.0 0.0 . 4 0.0 0.0 . 5 0.0 0.0 . 6 0.0 0.0 . 7 0.0 0.0 . 8 v0.0 0.0 .
48
6.8 Alarms
Figure 49 - Alarms Front Panel Screen
Figure 50 - Alarm Status Remote Front Panel Screen
6.8.1 Short Alarm
Figure 51 – Short Alarm Status Front Panel Screen
Preempt – READ ONLY When any of the CU Preempt inputs become active. Once set, a bit shall maintain it's state as long as the condition exists
Local Cycle Zero – READ ONLY When running coordinated and the Coord Cycle Status (coordCycleStatus) has passed through zero.
Preempt . T&FFlash . LocalCycleZero . LocalOverride . CoordinationAlarm . DetectorFault . NonCriticalAlarm . CriticalAlarm .
Alarms 1.Short Alarm 2.Unit Alarm 1 3.Unit Alarm 2
49
Local Override – READ ONLY When any external input or CU programming has prevented the device from responding to a system pattern command.
Coordination Alarm – READ ONLY When the CU is not running the called pattern without offset correction within three cycles of the command. An offset correction requiring less than three cycles due to cycle overrun caused by servicing a pedestrian call shall not cause a Coordination Alarm.
Detector Fault – READ ONLY When any detectorAlarm fault occurs.
Non-Critical Alarm – READ ONLY When a physical alarm input is active.
Critical Alarm – READ ONLY When the Stop Time input is active.
6.8.2 Unit Alarm 1
Figure 52 – Unit Alarm 1 Status Front Panel Screen
Cycle Fault – READ ONLY When the Controller Unit is operating in the coordinated mode and cycling diagnostics indicate that a serviceable call exists that has not been serviced for two cycles.
Coord Fault – READ ONLY When a Cycle Fault is in effect and the serviceable call has been serviced within two cycles after the Cycle Fault.
Coord Fail – READ ONLY When a Coord Fault is in effect and a Cycle Fault occurs again within two cycles of the coordination retry.
Cycle Fail – READ ONLY When a local Controller Unit is operating in the non-coordinated mode, whether the result of a Cycle Fault or Free being the current normal mode, and cycling diagnostics indicate that a serviceable call exists that has not been serviced for two cycles.
Local Flash – READ ONLY
CycleFault . CoordFault . CoordFail . CycleFail . MMUFlash . LocalFlash . LocalFree . CoordActive X
50
When the Controller Unit Local Flash input becomes active, MMU Flash input is not active, and Flash is not commanded by the system.
Local Free – READ ONLY When any of the Controller Unit inputs and/or programming cause it to not respond to coordination control.
CoordActive – READ ONLY When coordination is active and not preempted or overridden.
6.8.3 Unit Alarm 2
Figure 53 – Unit Alarm 2 Status Front Panel Screen
Low Battery – READ ONLY When any battery voltage falls below the required level.
Response Fault – READ ONLY When any NEMA TS2 Port 1 response frame fault occurs.
External Start – READ ONLY When the CU External Start becomes active.
Stop Time – READ ONLY When either CU Stop Time Input becomes active.
LowBattery . ResponseFault . ExternalStart . StopTime .
51
6.9 Channels
Figure 54 – Channels Status Front Panel Screen
Figure 55 - Channels Status Remote Front Panel Scre en
Reds – READ ONLY Phase Red Output Status, when equal to ‘1,2,3,etc.’, the Phase Red is currently active. When equal to ‘., the Phase Red is NOT currently active.
Yellows – READ ONLY Phase Yellow Output Status, when equal to ‘1,2,3,etc.’, the Phase Yellow is currently active. When equal to ‘., the Phase Yellow is NOT currently active.
Greens – READ ONLY Phase Green Output Status, when equal to ‘1,2,3,etc.’, the Phase Green is currently active. When equal to ‘.’, the Phase Green is NOT currently active.
Chn Grp 1 2 3 > 12345678 12345678 12345678 Reds 12.456.8 123456.. ........ Yellows ........ ........ ........ Greens ..3...7. ........ ........
52
6.10 Input Status
Figure 56 – Input Status Front Panel Screen
6.11 Output Status
Figure 57 – Input Status Front Panel Screen
6.12 Peer
Figure 58 – Peer Status Front Panel Screen
PeerID – READ ONLY ID of the peer the message is coming from.
CommState – READ ONLY The state of the communication with the Peer for this message. The values are:
Blank,
# PeerID CommState Function Inde> 1 0 none 0 2 0 none 0 3 0 none 0 4 0 none 0 5 0 none 0 6 0 none 0 7 0 none 0 8 0 none 0 9 0 none 0 10 0 none 0 11 0 none 0 12 0 none 0 13 0 none 0 14 0 none 0 15 v0 none 0
Output Gp 1 2 3 > 12345678 12345678 12345678 Status ..34..7. .2....78 ..3..6.. Control ........ ........ ........
Input Gp 1 2 3 > 12345678 12345678 12345678 Status ........ ........ ........ Control ........ ........ ........
53
Resolving – The controller is trying to resolve the peer hostname.
resolvErr – The peer hostname could not be resolved.
Connecting – The peer is connecting, but no message had been received yet.
Timeout – The message has not arrived within the timeout period.
connErr – There is a connection error.
Waiting – The controller has requested the message and is waiting for the response.
errorRsp - The error happened while receiving the response.
badData – The response format is not recognized.
connected – The peer is connected and communicating.
Function – READ ONLY The function that is been requested from the peer controller. The function matches the function entered in the user program statement.
Index – READ ONLY The index of function that is been requested from the peer controller. The index matches the function index entered in the user program statement.
Value – READ ONLY The value of the function that has been received from the peer controller. This value is also returned in the user program statement that requested the peer function.
6.13 Master
Figure 59 - Master Front Panel Screen
Master 1.Sections 2.Controllers 3.Detectors
54
6.13.1 Sections
Figure 60 – Master Sections Front Panel Screen
Section - READ ONLY The number of the section configured within Section configuration.
Pattern - READ ONLY The running mode or pattern output for the section. Pattern values indicate the following:
• 0: Standby - control is relinquished.
• 1-253: Pattern - the corresponding pattern is indicated.
• 254: Free - a mode of Free is indicated.
• 255: Flash - a mode of Automatic Flash is indicated.
Mode - READ ONLY The Traffic Responsive control mode for the section. The following entries are defined:
• algorithm - control by algorithm computation.
• manual - default mode / no control mode in use.
• failed - minimum controllers are not active.
Sig - READ ONLY The Signature number that provided the best match to the sample data for the section. This corresponds to a signature within the Signature configuration.
Failed - READ ONLY The number of subordinate controllers in the section that have Comm equal to 'notResponding' for more than the configured Fail Time.
Section Pattern Mode Sig > 1 0 manual 0 2 0 manual 0 3 0 manual 0 4 0 manual 0 5 0 manual 0 6 0 manual 0 7 0 manual 0 8 0 manual 0 9 0 manual 0 10 0 manual 0 11 0 manual 0 12 0 manual 0 13 0 manual 0 14 0 manual 0 15 v0 manual 0
Failed 0 0 0 0
0
0
0
0
0
55
6.13.2 Controllers
Figure 61 - Master Controllers Front Panel Screen
Ctrlr - READ ONLY The number of the controller configured within Controller configuration.
Pattern - READ ONLY The controller's current pattern / mode. The following pattern values apply:
• 0 - not used
• 1-253 - pattern
• 254 - free mode
• 255 - flash mode
Comm - READ ONLY The controller's communication status. The following values apply:
• notResponding - the controller either did not respond or produced an invalid or error response.
• responding - the controller is responding.
• noAttempt - the controller has not yet been polled.
Ctrlr Pattern Comm 1 0 noAttempt 2 0 noAttempt 3 0 noAttempt 4 0 noAttempt 5 0 noAttempt 6 0 noAttempt 7 0 noAttempt 8 0 noAttempt 9 0 noAttempt 10 0 noAttempt 11 0 noAttempt 12 0 noAttempt 13 0 noAttempt 14 0 noAttempt 15 v0 noAttempt
56
6.13.3 Detectors
Figure 62 - Mater Detectors Front Panel Screen
Sensor - READ ONLY The number of the sensor configured within the Signature Criteria configuration.
Vol - READ ONLY The number of vehicles counted within the polling period. The value 255 indicates volume overflow.
NV - READ ONLY The Vol converted to a percentage of some expected or normalized value via VF ("Volume Factor" configured within Detectors configuration.) If VF results in an overflow value, the value is set to 255. If Fault is not equal to 'none', the value is set to 0.
NV = ( 3600 x MV ) / ( VF x SP )
where:
NV = normalized volume (in percent)
MV = measured volume (in number of vehicles)
VF = volume factor (100s of vehicles per hour)
SP = sample period (in seconds)
Occ - READ ONLY The occupancy (.5%) of the gathered data, or detector diagnostic information for values greater than 200. The following values apply:
• 0-200 - detector occupancy in 0.5%
• 201-209 - reserved
• 210 - max presence fault
• 211 - no activity fault
• 212 - open loop fault
Sensor Vol NV Occ NO Fault > 1 0 0 0 0 sampling 2 0 0 0 0 sampling 3 0 0 0 0 sampling 4 0 0 0 0 sampling 5 0 0 0 0 sampling 6 0 0 0 0 sampling 7 0 0 0 0 sampling 8 0 0 0 0 sampling 9 0 0 0 0 sampling 10 0 0 0 0 sampling 11 0 0 0 0 sampling 12 0 0 0 0 sampling 13 0 0 0 0 sampling 14 0 0 0 0 sampling 15 v0 0 0 0 sampling
Seq# Period 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
57
• 213 - shorted loop fault
• 214 - excessive change fault
• 215 - reserved
• 216 - watchdog fault
• 217 - erratic output fault
• 218-255 - reserved
NO - READ ONLY The Occ converted to whole percents. The value is set equal to 0 if Fault is not equal to 'none'.
NO = MO / 2
where:
NO = normalized occupancy (in percent)
MO = measured occupancy (in number of half percents)
Fault – READ ONLY The current status of the detector. The indication is mapped from the measured occupancy value as follows:
• 0-200 - 'none'
• 210 - 'maxPresence'
• 211 - 'noActivity'
• 212 - 'openLoop'
• 213 - 'shortedLoop'
• 214 - 'excessChange'
• 215 - 'unknown'
• 216 - 'watchdog
• 217 - 'erraticOutput'
• other - 'unknown'
All possible values include the following:
• none - no fault is present.
• maxPresence -
• noActivity -
• openLoop -
• shortedLoop -
• excessChange -
• watchdog -
• erraticOutput -
• volOccPeriod - V+O period fault, if Period for the detector is not equal to Per for the section.
58
• volOverflow - if Vol is 255.
• sampling - if more than one Seq# value has been lost.
• unknown -
Seq# - READ ONLY The sample number of the data gathered from the detector. If the same sequence number is received more than once, the values are discarded. Old values are retained until a different sequence number is received.
Period – READ ONLY
The sampling period of the data gathered from the detector.
6.14 Prioritor
Figure 63 – Prioritor Status Screen
Prioritor 1.Unit Status 2.Prioritor Status 3.Detector Status
59
Figure 64 – Prioritor Unit Status Screen
Figure 65 – Prioritor Status Screen
State: off, on
SrvTime: Service Time Status
ETA: Estimated Time of Arrival
Delay: Estimated Delay Time
Pri Gr 1 12345678 CheckIn ........ CheckOut ........
PriNum 1 2 3 4 5 6 7 8 State off off off off off off off off SrvTime 0 0 0 0 0 0 0 0 ETA 0 0 0 0 0 0 0 0 Delay 0 0 0 0 0 0 0 0
Lock Out Time 0
60
Figure 66 – Prioritor Detector Status Screen
6.15 Cabinet Status
Figure 67 - Monitor Status Screen
Conflict Monitor/Fault Detail - READ ONLY Displays detailed fault condition if the monitor is in fault.
Reds – READ ONLY ‘X' indicates that the monitor is reporting red for the specified channel.
Yellows – READ ONLY ‘X' indicates that the monitor is reporting yellow for the specified channel.
Greens – READ ONLY ‘X' indicates that the monitor is reporting green for the specified channel.
Fault – READ ONLY If the Monitor is in a fault state this row will display and X for each channel that caused the fault condition.
Cabinet 1.Comm Statistics
61
Figure 68 – Cabinet Comm Statistics Status Screen
Module: This is the module that the statistic is for.
Frame: This is the frame number that the statistic is for.
Last10: This is the number of errors within the last 10 frames that were sent.
Total: This is the total number of errors for the frame listed since the controller rebooted.
Figure 69 – User programs Status Screen
Figure 70 – Processing Info Status Screen
Processing Info: displays errors detected in the user programs. For instance, if program x calls program y and program y calls program x, creating a circular dependency, a circular dependency error will be displayed.
Figure 71 – User program custom Screen
Processing Info
User Programs 1.Processing info 2.User Programs
# Module Frame Last10 Total 1 0 0 0 0 2 0 0 0 0 3 0 0 0 0 4 0 0 0 0 5 0 0 0 0 6 0 0 0 0 7 0 0 0 0 8 v0 0 0 0
This is a custom screen where user programs can display whatever they want.
62
7 Controller Menu
Figure 72 - Controller Menu Front Panel Screen
Figure 73 - Controller Menu More Front Panel Screen
Figure 74 - Controller Menu Remote Front Panel Scre en
Controller 1.Advanced IO 2.Countdown Displays 3.Manual Control 4.Peer 5.Master 6.Prioritor 7.Loopback 8.User Programs
Controller 1.Unit 2.Phase 3.Sequence 4.Detector 5.Overlap 6.Coordination 7.Scheduler 8.Preemptions 9.More
63
7.1 Unit Parameters
Figure 75 - Unit Parameters Front Panel Screen
Extended Mode – ENABLED/DISABLED When enabled, the controller is in extended mode. The extended mode includes displaying multiple phase timing and detector parameter plans for complex intersections that requires that level of flexibility.
Startup Flash - INTEGER (0..255) Unit Start up Flash time parameter in seconds (0 to 255 sec). The period/state (Start-Up Flash occurs when power is restored following a device defined power interruption. During the Start-Up Flash state, the Fault Monitor and Voltage Monitor outputs shall be inactive (if present).
Auto PedClear – ENABLED/DISABLED When enabled, the CU shall time the Pedestrian Clearance interval when Manual Control Enable is active and prevent the Pedestrian Clearance interval from being terminated by the Interval Advance input.
Red Revert - FLOAT (0..25.5) The red revert in tenth seconds ( 0.0 - 25.5 seconds). This value shall provide the minimum red revert time for all phases (i.e. if it is greater than a phaseRedRevert object value, then this value shall be used as the red revert time for the affected phase). This object provides a minimum Red indication following the Yellow Change interval and prior to the next display of Green on the same signal output driver group.
Backup Time - INTEGER (0..65535) The Backup Time in seconds (0-65535). When one of the defined system control parameters is SET by a remote command from master or Central UTC computer, the backup timer is reset and times the unitBackupTime interval. If the unitBackupTime interval expires without a SET operation to one of the system control parameters, then the CU shall revert to Backup Mode. A value of zero (0) shall disable this feature.
Startup Cl Hold Time (0..255) Startup Clearance Hold Time.
Green Flash Frequency – INTEGER (60..120)
Extended Mode Disable StartUp Flash 1 Auto PedClear Enable Red Revert 4.0 Backup Time 0 Startup Cl Hold Time 0 Green Flash Frequency 60 Yellow Flash Frequency 60 Manual Control Sequence 0 Manual Control Enable Enable Primary Start 0.0 Secondary Start 0. 0
64
This object defines the green flash frequency in number of flashes per minutes. The default value is 60 flashes per minute.
Yellow Flash Frequency – INTEGER (60..120) This object defines the yellow flash frequency in number of flashes per minutes. The default value is 60 flashes per minute.
Manual Control Sequence – INTEGER (0..20) This object defines the sequence to use when the controller is in manual control. If set to 0, the controller uses the current sequence.
Manual Control Enable – DISABLED/ENABLED This object enables the manual control feature. If disabled, the manual control feature won’t be activate even if the manual control input is ON.
Primary Start – FLOAT(0..25.5) This object defines the primary startup phase interval time in tenth seconds.
Secondary Start – FLOAT(0..25.5) This object defines the secondary startup phase interval time in tenth seconds.
7.2 Phase Menu
Figure 76 - Phase Front Panel Screen
Figure 77 - Phase Remote Front Panel Screen
7.2.1 Phase Times
Phase 1.Phase Times 2.Phase Options 3.Phase Configuration 4.Phase Times Copy
65
Figure 78 - Phase Times Simple mode Front Panel Scr een
Figure 79 - Phase Times Remote Front Panel Screens
Walk – INTEGER (0..255) Phase Walk Parameter in seconds. This shall control the amount of time the Walk indication shall be displayed.
PedClear - INTEGER (0..255) Phase Pedestrian Clear Parameter in seconds. This shall control the duration of the Pedestrian Clearance output (if present) and the flashing period of the Don't Walk output.
Phase 1 2 3 4 5 6 7 8 > Walk 0 7 0 7 0 7 0 7 PedClr 0 12 0 12 0 12 0 12 DontWlk 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0 MinGrn 5 10 5 10 5 10 5 10 Passage 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 Max 1 30 60 30 60 30 60 30 60 Max 2 0 0 0 0 0 0 0 0 Max 3 0 0 0 0 0 0 0 0 YelChg 3.0 3.0 3.0 3.0 3.0 3.0 3.0 3.0 RedClr 2.0 2.0 2.0 2.0 2.0 2.0 2.0 2.0 RedRvrt 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 DynMax 0 0 0 0 0 0 0 0 MaxStep 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 DlyGrn 0 0 0 0 0 0 0 0 DlyPed 0 0 0 0 0 0 0 0 Walk2 0 0 0 0 0 0 0 0 Walk3 0 0 0 0 0 0 0 0 PedCl2 0 0 0 0 0 0 0 0 PedCl3 0 0 0 0 0 0 0 0 PreGrn 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 PreClr 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 +RedClr 0 0 0 0 0 0 0 0
66
Don’t Walk - FLOAT (0..25.5) Phase Pedestrian Steady Don't Walk in seconds (0-25.5 sec).
MinGreen - INTEGER (0..255) Phase Minimum Green Parameter in seconds (NEMA TS 2 range: 1-255 sec). The first timed portion of the Green interval which may be set in consideration of the storage of vehicles between the zone of detection for the approach vehicle detector(s) and the stop line.
Passage - FLOAT (0..25.5) Phase Passage Parameter in tenth seconds (0-25.5 sec). Passage Time, Vehicle Interval, Preset Gap, Vehicle Extension: the extensible portion of the Green shall be a function of vehicle actuations that occur during the Green interval. The phase shall remain in the extensible portion of the Green interval as long as the passage timer is not timed out. The timing of this portion of the green interval shall be reset with each subsequent vehicle actuation and shall not commence to time again until the vehicle actuation is removed.
Max 1 - INTEGER (0..255) Phase Maximum 1 Parameter in seconds (NEMA TS 2 range: 1-255 sec). This time setting shall determine the maximum length of time this phase may be held Green in the presence of a serviceable conflicting call. In the absence of a serviceable conflicting call the Maximum Green timer shall be held reset unless Max Vehicle Recall is enabled for this phase. This is the default maximum value to use. It may be overridden via an external input, coordMaximumMode or other method.
Max 2 – INTEGER (0..255) Phase Maximum 2 Parameter in seconds (NEMA TS 2 range: 1-255 sec). This time setting shall determine the maximum length of time this phase may be held Green in the presence of a serviceable conflicting call. In the absence of a serviceable conflicting call the Maximum Green timer shall be held reset unless Max Vehicle Recall is enabled for this phase.
Max 3 – INTEGER (0..255) Phase Maximum 3 Parameter in seconds (NEMA TS 2 range: 1-255 sec). This time setting shall determine the maximum length of time this phase may be held Green in the presence of a serviceable conflicting call. In the absence of a serviceable conflicting call the Maximum Green timer shall be held reset unless Max Vehicle Recall is enabled for this phase.
YelChg - FLOAT (0..25.5) Phase Yellow Change Parameter in tenth seconds (NEMA TS 2 range: 3-25.5 sec). Following the Green interval of each phase the CU shall provide a Yellow Change interval which is timed according to the Yellow Change parameter for that phase.
Red Clear - FLOAT (0..25.5) Phase Red Clearance Parameter in tenth seconds (0-25.5 sec). Following the Yellow Change interval for each phase, the CU shall provide a Red Clearance interval which is timed according to the Red Clearance parameter for that phase.
Red Revert – FLOAT (0..25.5) Red revert time parameter in tenth seconds. A minimum Red indication to be timed following the Yellow Change interval and prior to the next display of Green on the same signal output driver group. The unitRedRevert parameter shall act as a minimum red
67
revert time for all signal displays. The phaseRedRevert parameter may increase the red revert time for a specific phase. If the phaseRedRevert parameter is less than the unitRedRevert the unitRedRevert time shall be used.
DynMax – INTEGER (0..255) This object determines either the upper or lower limit of the running max in seconds (0-255) during dynamic max operation. The normal maximum (i.e. Max1, Max2, etc.) shall determine the other limit as follows: When dynamicMaxLimit is larger than the normal maximum, it shall become the upper limit. When dynamicMaxLimit is smaller than the normal maximum, it shall become the lower limit. Setting dynamicMaxLimit greater than zero enables dynamic max operation with the normal maximum used as the initial maximum setting. See dynamicMaxStep for details on dynamic max operation. Maximum recall or a failed detector that is assigned to the associated phase shall disable dynamic max operation for the phase.
MaxStep – FLOAT (0..25.5) DlyGreen interval time Parameter in seconds (0-255 sec). If set to a non-zero value, this interval times prior to the start of any Green vehicle intervals (conditioned on a Pedestrian call or recall being present on this phase). The Delayed Green Interval (early pedestrian start) is timed concurrently with the Pedestrian intervals.
DlyGrn – INTEGER (0..255) DlyGreen interval time Parameter in seconds (0-255 sec). If set to a non-zero value, this interval times prior to the start of any Green vehicle intervals (conditioned on a Pedestrian call or recall being present on this phase). This Delayed Green Interval is also sometimes referred to as an Early Pedestrian Interval as it is timed concurrently with any active Pedestrian Interval for this phase.
DlyPed – INTEGER (0..255) Time delay before start of pedestrian timing begins Parameter in seconds. This shall control the amount of time to delay the start of pedestrian timing intervals.
Walk2 – INTEGER (0..255) Alternate Walk 2 Parameter in seconds. This shall control the amount of time the Walk indication is displayed when an alternate Walk (for special-needs pedestrian) call is being serviced.
Walk3 – INTEGER (0..255) Alternate Walk 3 Parameter in seconds. This shall control the amount of time the Walk indication is displayed when an alternate Walk (for special-needs pedestrian) call is being serviced.
PedClr2 – INTEGER (0..255) Alternate Pedestrian Clear 2 Parameter in seconds. This shall control the duration of the Pedestrian Clearance output (if present) and the flashing period of the Don’t Walk output when an alternate pedestrian call is being serviced.
PedClr3 – INTEGER (0..255) Alternate Pedestrian Clear 3 Parameter in seconds. This shall control the duration of the Pedestrian Clearance output (if present) and the flashing period of the Don’t Walk output when an alternate pedestrian call is being serviced.
PreGreen – INTEGER (0..255)
68
Pre green interval time Parameter in tenth seconds (0-25.5 sec). PreGreen (or Startup Clearance) interval time. If set to a non-zero value, this interval times prior to the start of the phase Green Interval.
PreClear – INTEGER (0..255) Pre clearance interval time Parameter in tenth seconds (0-25.5 sec). If set to a non-zero value, this interval times prior to the start of the Yellow Clearance Interval.
+RedClr – INTEGER (0..255) Add Red Clearance parameter in seconds. This parameter adds to the duration of the asc phaseRedClear parameter.
Figure 80 - Phase Times Extended Mode Front Panel S creen
Phase 1 2 3 4 5 6 > Walk 0 0 0 0 0 0 PedClr 0 0 0 0 0 0 DontWlk 0.0 0.0 0.0 0.0 0.0 0.0 MinGrn 5 5 5 5 5 5 MinGrn2 0 0 0 0 0 0 Passage 1.0 1.0 1.0 1.0 1.0 1.0 Max 1 0 0 0 0 0 0 Max 2 0 0 0 0 0 0 Max 3 0 0 0 0 0 0 CondMax 0 0 0 0 0 0 DetDis 0 0 0 0 0 0 YelChg 3.0 3.0 3.0 3.0 3.0 3.0 RedClr 1.0 1.0 1.0 1.0 1.0 1.0 +RedClr 0 0 0 0 0 0 RedRvrtv0.0 0.0 0.0 0.0 0.0 0.0
DynMax 0 0 0 0 0 0 MaxStep 0.0 0.0 0.0 0.0 0.0 0.0 DlyGrn 0 0 0 0 0 0 DlyPed 0 0 0 0 0 0 Walk2 0 0 0 0 0 0 PedCl2 0 0 0 0 0 0 PedCl3 0 0 0 0 0 0 PreGrn 0.0 0.0 0.0 0.0 0.0 0.0 PreClr 0.0 0.0 0.0 0.0 0.0 0.0 Walk3 0 0 0 0 0 0 AdvWalk 0 0 0 0 0 0 Walk2En 0 0 0 0 0 0 PdCl2En 0 0 0 0 0 0 VarLeft 0 0 0 0 0 0 PdClOvl 0 0 0 0 0 0
69
7.2.2 Phase Options
Figure 81 - Phase Options Simple Mode Front Panel S creen
Figure 82 - Phase Options Remote Front Panel Screen s
Enabled – ENABLED/DISABLED
1 2 > Phase 12345678901234567890123456 Enable 12345678.................. AutoFlashEnt .......................... AutoFlashExit .......................... NonActua1 .......................... NonActua2 .......................... NonLockDetMem .......................... MinVehRecall 12345678.................. MaxVehRecall .......................... PedRecall .......................... SoftVehRecall .......................... DualEntry .2.4.6.8.................. SimGapDis .......................... ActuaRestWalk .......................... CondService v..........................
PedClrYel ....................... PedClrRed ....................... CondReservice ....................... YelChangeMin ....................... NoStartupCall 1...................... AdvWarning ....................... NoPedStartCall ....................... PedClrDuringOVTG ....................... FlashExitCall ....................... FlashExitPedCall ....................... Min2VehRecall ....................... Max2VehRecall ....................... Max3VehRecall ....................... Ped2Recall .......................
70
Provides a means to define whether this phase is used in the current configuration. A disabled phase shall not provide any outputs nor respond to any phase inputs.
AutoFlashEntPhs – ENABLED/DISABLED Automatic Flash Entry Phase - When Automatic Flash is called, the CU shall service the Entry Phase(s), clear to an All Red, then initiate flashing operation.
AutoFlashExitPhs – ENABLED/DISABLED Automatic Flash Exit Phase - The CU shall move immediately to the beginning of the phase(s) programmed as Exit Phase(s) when Automatic Flash terminates.
NonActua1 – ENABLED/DISABLED Non-Actuated 1 - when set to enabled causes a phase to respond to the Call To Non-Actuated 1 input (if present) or other method.
NonActua2 – ENABLED/DISABLED Non-Actuated 2 - when set to enabled causes a phase to respond to the Call To Non-Actuated 2 input (if present) or other method.
NonLockDetMem – ENABLED/DISABLED Non Lock Detector Memory - when set to disabled will cause the call to be locked at the beginning of the yellow interval. When set to enabled call locking will depend on the detectorOptions object.
MinVehRecall – ENABLED/DISABLED Min. Vehicle Recall - when set to enabled causes recurring demand for vehicle service on the phase when that phase is not in its Green interval.
MaxVehRecall – ENABLED/DISABLED Max Vehicle Recall - when set to enabled causes a call on a phase such that the timing of the Green interval for that phase shall be extended to Maximum Green time.
PedRecall – ENABLED/DISABLED Pedestrian Recall - when set to enabled causes a recurring pedestrian demand which shall function in the same manner as an external pedestrian call except that it shall not recycle the pedestrian service until a conflicting phase is serviced.
SoftVehRecall – ENABLED/DISABLED Soft Vehicle Recall - when set to enabled causes a call on a phase when all conflicting phases are in green dwell or red dwell and there are no serviceable conflicting calls.
DualEntry – ENABLED/DISABLED Dual Entry Phase - in multi-ring configurations when set to enabled causes the phase to become active upon entry into a concurrency group (crossing a barrier) when no calls exist in its ring within its concurrency group.
SimGapDis – ENABLED/DISABLED Simultaneous Gap Disable - in multi-ring configurations when set to enabled this object disables a gapped out phase from reverting to the extensible portion.
ActRestInWalk – ENABLED/DISABLED Actuated Rest In Walk - when set to enabled, this option causes an actuated phase to rest in Walk when there is no serviceable conflicting call at the end of Walk Timing.
71
CondService – ENABLED/DISABLED Conditional Service Enable - in multi-ring configurations when set to enabled causes a gapped/maxed phase to conditionally service a preceding actuated vehicle phase when sufficient time remains before max time out of the phase(s) not prepared to terminate.
PedClrDuringYel – ENABLED/DISABLED Pedestrian Clearance During Yellow – when set to enable, the pedestrian clearance interval will flash/time through the yellow clearance time.
PedClrDuringRed – ENABLED/DISABLED Pedestrian Clearance During Red – when set to enable, the pedestrian clearance interval will flash/time through the yellow and red clearance times.
CondReservice – ENABLED/DISABLED Conditional Re-service Enable – when set to enabled, allows additional conditional services (see above) until a conflicting call is received from a different barrier group.
YelChangeMinOverride – ENABLED/DISABLED Yellow Change Minimum Override – when set to enable, the controller will allow yellow clearance times less than 3.0 seconds for this phase. Extreme caution should be used with this feature. If enabled, the mandatory, required minimum yellow clearance time for that specific phase can be violated.
No Startup Call – ENABLED/DISABLED When set to enable, the controller will not service the vehicle calls during the startup sequence.
Advance Warning – ENABLED/DISABLED When set to enable, the phase is enabled for the advance warning feature.
No Ped Startup Call – ENABLED/DISABLED When set to enable, the controller will not service the pedestrian calls during the startup sequence.
Ped Clear During OVTG – ENABLED/DISABLED When set to enable, the ped clearance interval for this phase can time concurrently with the overlap trail green interval if the phase is one of the overlap parent phase. This applies to the ped overlap type as well.
Flash Exit Call – ENABLED/DISABLED When set to enable, when the controller exits automatic flash, it puts some vehicle calls on all the enabled phases.
Flash Exit Ped Call – ENABLED/DISABLED When set to enable, when the controller exits automatic flash, it puts some ped calls on all the enabled phases.
Min 2 Vehicle Recall – ENABLED/DISABLED When set to enable, the controller will use MinGreen2 instead of the regular MinGreen time for this phase.
72
Max 2 Vehicle Recall – ENABLED/DISABLED When set to enable, the controller will use Max 2 instead of the regular Max time for this phase.
Max 3 Vehicle Recall – ENABLED/DISABLED When set to enable, the controller will use Max 3 instead of the regular Max time for this phase.
Ped2 Recall – ENABLED/DISABLED When set to enable, the controller will use the second set of pedestrian timing parameters for this phase: altWak(Walk2), altPedClear(PedCl2), instead of the regular Pedestrian timing parameters for this phase.
Figure 83 - Phase Options Extended Mode Front Panel Screen
1 2 > Phase 12345678901234567890123 Enable 12345678............... AutoFlashEnt ....................... AutoFlashExit ....................... NonActua1 ....................... NonActua2 ....................... NonLockDetMem 12345678............... MinVehRecall 12345678............... MaxVehRecall ....................... PedRecall ....................... SoftVehRecall ....................... DualEntry ....................... SimGapDis ....................... ActuaRestWalk ....................... CondService v.... ..................
YelChangeMin ....................... NoStartCall 1...................... AdvWarning ....................... NoPedStartCall ....................... PedClrDuringOVTG ....................... FlashExitCall ....................... FlashExitPedCall ....................... Min2VehRecall ....................... Max2VehRecall ....................... Max3VehRecall ....................... Ped2Recall .......................
73
7.2.3 Phase Configuration
Figure 84 - Phase Configuration Front Panel Screen
Figure 85 - Phase Configuration Remote Front Panel Screen
Startup – DROPDOWN The Phase Startup parameter selects the startup state for each phase after restoration of a defined power interruption or activation of the external start input. The following entries are defined:
• Other - this phase initializes in a state not defined by this standard.
• phaseNotOn - this phase initializes in a Red state (the phase is not active and no intervals are timing).
• greenWalk - this phase initializes at the beginning of the minimum green and walk timing intervals.
Phase Startup Ring Concurrency > 1 phaseNotOn 1 5,6 2 greenWalk 1 5,6 3 phaseNotOn 1 7,8 4 phaseNotOn 1 7,8 5 phaseNotOn 2 1,2 6 greenWalk 2 1,2 7 phaseNotOn 2 3,4 8 phaseNotOn 2 3,4 9 other 0 10 other 0 11 other 0 12 other 0 13 other 0 14 other 0 15 vother 0
NoServePhases Description 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 v
74
• greenNoWalk - this phase initializes at the beginning of the minimum green timing interval.
• yellowChange - this phase initializes at the beginning of the Yellow Change interval.
• redClear - this phase initializes at the beginning of the Red Clearance interval.
• secondaryStart
Ring – INTEGER (0..255) Phase ring number (1..maxRings) that identified the ring which contains the associated phase. This value must not exceed the maxRings object value. If the ring number is zero, the phase is disabled.
Concurrency - OCTET STRING Each comma delimited character sequence contains a phase number that may run concurrently with the associated phase. Phases that are contained in the same ring may NOT run concurrently.
NoServePhases - OCTET STRING Each comma delimited character sequence contains a phase number that may NOT run concurrently with the associated phase. This could be used to add some soft concurrency restrictions that can’t be entered with traditional barriers.
7.2.4 Phase Times Copy
Figure 86-Phase Times Copy Front Panel Screen
Phase – INTEGER (1..40) Copies Phase Times from Phase 1 to Phase 2.
Note: When the Phase Times data has been successfully copied the “Data copied successfully” message will be shown.
Copy Data: From Phase 1 to Phase 2 Press ENTER to copy data
75
7.3 Sequence
Figure 87 – Sequence Index Selector Front Panel Scr een
Figure 88 – Sequence Front Panel Screen
Sequence _
Ring Sequence Data 1 1,2,a,3,4,b 2 5,6,a,7,8,b 3 4 5 6 7 8 9 10 11 12 13 14 15 v
76
Figure 89-Sequence Remote Front Panel Screen
Ring – READ ONLY This number identifies the ring number this phase sequence applies to.
Sequence Data – OCTET STRING Each comma delimited character sequence is either a Phase Number or barrier ID character (a-z) for the associated ring number. The phase number value shall not exceed the maxPhases object value. The order of phase numbers determines the phase sequence for the ring. The placement of barrier ID characters in the phase sequence denotes the barrier position in the ring sequence. The phase numbers shall not be placed in a manner that would violate the devices’ phase to ring assignment. A phase may not be assigned to more than one ring and a phase shall not appear more than once in a single ring sequence
77
7.4 Detector
Figure 90 - Detector Front Panel Screen
Figure 91 – Detector Remote Front Panel Screen
7.4.1 Vehicle Detector Parameters
Figure 92 – Vehicle Detector Parameters Front Panel Screen
Detector 1 2 3 > Call Phase 1 2 2 Phs+ Switch Phase 0 0 0 Delay 0.0 0.0 0.0 Extend 0.0 0.0 0.0 Queue Limit 0 0 0 No Activity 0 0 0 Max Presence 0 0 0 Erratic Counts 0 0 0 Fail Time 0 0 0
Detector 1.Vehicle Detector Parameters 2.Vehicle Detector Options 3.Vol & Occ Settings 4.Pedestrian Detector Parameters
78
Figure 93 – Vehicle Detector Parameters Remote Fron t Panel Screen
Call Phase - INTEGER (0..255) This field contains assigned phase number for the detector input associated with this row. The associated detector call capability is enabled when this object is set to a non-zero value. The value shall not exceed the value of maxPhases.
Additional Call Phases - INTEGER (0..255) This field contains additional assigned phases for the detector input associated with this row. Use this field to assign multiple phases to a single detector. Separate phase numbers with a ‘,’
Switch Phase - INTEGER (0..40) Detector Switch Phase Parameter (i.e., Phase Number). The phase to which a vehicle detector actuation shall be switched when the assigned phase is Yellow or Red and the Switch Phase is Green.
Delay – FLOAT (0..25.5) Detector Delay Parameter in tenth seconds (0-255.0 sec). The period a detector actuation (input recognition) shall be delayed when the phase is not Green"
Extend – FLOAT (0..25.5) Detector Extend Parameter in tenth seconds (0-25.5 sec). The period a vehicle detector actuation (input duration) shall be extended from the point of termination, when the phase is Green.
Queue Limit - INTEGER (0..255) Detector Queue Limit parameter in seconds (0-255 sec). The length of time that an actuation from a queue detector may continue into the phase green. This time begins when the phase becomes green and when it expires any associated detector inputs shall be ignored. This time may be shorter due to other overriding device parameters (i.e. Maximum time, Force Off's, ...).
No Activity - INTEGER (0..255) Detector No Activity diagnostic Parameter in minutes (0-255 min.). If an active detector does not exhibit an actuation in the specified period, it is considered a fault by the
79
diagnostics and the detector is classified as Failed. A value of 0 for this object shall disable this diagnostic for this detector.
Max Presence- INTEGER (0..255) Detector Maximum Presence diagnostic Parameter in minutes (0-255 min.). If an active detector exhibits continuous detection for too long a period, it is considered a fault by the diagnostics and the detector is classified as Failed. A value of 0 for this object shall disable this diagnostic for this detector.
Erratic Counts - INTEGER (0..255) Detector Erratic Counts diagnostic Parameter in counts/minute (0-255 cpm). If an active detector exhibits excessive actuations, it is considered a fault by the diagnostics and the detector is classified as Failed. A value of 0 for this object shall disable this diagnostic for this detector.
Fail Time - INTEGER (0..255) Detector Fail Time in seconds (0..255). If a detector diagnostic indicates that the associated detector input is failed, then a call shall be placed on the associated phase during all non-green intervals. When each green interval begins the call shall be maintained for the length of time specified by this object and then removed. If the value of this object equals the maximum value (255) then a constant call shall be placed on the associated phase (max recall). If the value of this object equals zero then no call shall be placed on the associated phase for any interval (no recall). Compliant devices may support a limited capability for this object (i.e. only max recall or max recall and no recall). At a minimum the max recall setting must be supported.
80
Figure 94 – Vehicle Detector Plans Extended Mode Fr ont Panel Screen
7.4.2 Vehicle Detector Options
Figure 95-Vehicle Detector Options Front Panel Scre en
Det Call Phase Call Overlap Phs+ > 1 1 0 2 2 0 3 3 0 4 4 0 5 5 0 6 6 0 7 7 0 8 8 0 9 0 0 10 0 0 11 0 0 12 0 0 13 0 0 14 0 0 15 v0 0
Queue Limit Det Disable 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0 0 0.0
Switch Phase Delay Extend > 0 0.0 0.0 0 0.0 0.0 0 0.0 0.0 0 0.0 0.0 0 0.0 0.0 0 0.0 0.0 0 0.0 0.0 0 0.0 0.0 0 0.0 0.0 0 0.0 0.0 0 0.0 0.0 0 0.0 0.0 0 0.0 0.0 0 0.0 0.0 0 0.0 0.0
1 2 > Detector 1234567890123456789012 VolumeDetector ...................... OccupancyDetector ...................... YellowLockCall ...................... RedLockCall ...................... Passage ...................... Queue ...................... Call 123456789012..........
81
Figure 96-Vehicle Detector Options Remote Front Pan el Screen
VolumeDetector – ENABLED/DISABLED If set (‘X’) the detector collects data for the associated detector volume object(s). This capability is support only under remote master or UTC control.
OccupancyDetector – ENABLED/DISABLED If set (‘X’) the detector collects data for the associated detector occupancy object(s). This capability is supported only under remote master or UTC control.
Yellow Lock – ENABLED/DISABLED If set (‘X’) the detector will lock a call to the assigned phase if an actuation occurs while the phase is not timing Green.
Red Lock – ENABLED/DISABLED If set (‘X’) the detector will lock a call to the assigned phase if an actuation occurs while the phase is not timing Green or Yellow. This mode is optional.
Passage – ENABLED/DISABLED If set (‘X’) the CU shall maintain a reset to the associated phase passage timer for the duration of the detector actuation when the phase is green.
Occ – ENABLED/DISABLED If set (‘X’) the detector collects data for the associated detector occupancy object(s). This capability is supported only under remote master or UTC control.
Queue – ENABLED/DISABLED If set (‘X’) the detector shall extend the green interval of the assigned phase until a gap occurs (no actuation) or until the green has been active longer than the vehicleDetectorQueueLimit time.
Call – ENABLED/DISABLED If set (‘X’) the CU shall place a demand for vehicular service on the assigned phase when the phase is not timing the green interval.
82
7.4.3 Volume and Occupancy Settings
Figure 97-Volume and Occupancy Settings Screen
Data Collection Period – INTEGER (0..255) The number of seconds (0-255) that comprise the volume / occupancy collection period. When the collection period expires the device shall increment the volumeOccupancySequence, update the volumeOccupancyTable entries and reset the volume occupancy timer.
7.4.4 Pedestrian Detector Parameters
Figure 98 - Pedestrian Detector Parameters Front Pa nel Screen
Figure 99 - Pedestrian Detector Parameters Remote F ront Panel Screen
Call Phase – INTEGER (0..40) This object contains assigned phase number for the pedestrian detector input associated with this row. The associated detector call capability is enabled when this object is set to a non-zero value.
Call Ovl – INTEGER (0..32)
Detector 1 2 3 4 5 6 > Call Phase 0 2 0 4 0 6 Call Ovl 0 0 0 0 0 0 No Activity 0 0 0 0 0 0 Max Presence 0 0 0 0 0 0 Erratic Counts 0 0 0 0 0 0
Data Collection Period 0
83
This object contains assigned ovelap number for the pedestrian detector input associated with this row. The associated detector call capability is enabled when this object is set to a non-zero value.
No Activity – INTEGER (0..255) Pedestrian Detector No Activity diagnostic Parameter in minutes (0-255 min.). If an active detector does not exhibit an actuation in the specified period, it is considered a fault by the diagnostics and the detector is classified as Failed. A value of 0 for this object shall disable this diagnostic for this detector.
Max Presence – INTEGER (0..255) Pedestrian Detector Maximum Presence diagnostic Parameter in minutes (0-255 min.). If an active detector exhibits continuous detection for too long a period, it is considered a fault by the diagnostics and the detector is classified as Failed. A value of 0 for this object shall disable this diagnostic for this detector.
Erratic Counts – INTEGER (0..255) Pedestrian Detector Erratic Counts diagnostic Parameter in counts/minute (0-255 cpm). If an active detector exhibits excessive actuations, it is considered a fault by the diagnostics and the detector is classified as Failed. A value of 0 for this object shall disable this diagnostic for this detector.
Figure 100 - Pedestrian Detector Plans Extended Mod e Front Panel Screen
7.5 Overlap
Figure 101 - Overlap Front Panel Screen
Detector Call Phase Call Ovl Alt Time 1 1 0 0 2 2 0 0 3 3 0 0 4 4 0 0 5 5 0 0 6 6 0 0 7 7 0 0 8 8 0 0 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 v0 0 0
Overlap 1.Overlap Phase settings 2.Overlap Parameter s
84
7.5.1 Overlap Phase Settings
Figure 102 - Overlap Phase Settings Front Panel Scr een
Figure 103 - Overlap Phase Settings Remote Front Pa nel Screen
Overlap Number – INTEGER (0..32) The overlap number for objects in this row. The value shall not exceed the maxOverlaps supported by the CU (32). The value maps to the Overlap as follows: 1 = Overlap A, 2 = Overlap B etc.
Include Phs – OCTET STRING Included Phases - Each character string is a Phase (number) that shall be an included phase for the overlap. The phase number value should not exceed the maximum Phases defined. When an included phase output is green or when the CU is cycling between included phases, the overlap output shall be green.
Overlap Included Phases Modifier Phases 1 2 1 2 4 3 3 6 5 4 8 7 5 6 7 2,9 8 9 10 11 12 13 14 15 v
85
Mod Phs – OCTET STRING Modifier Phases - Each character string is a Phase (number) that shall be a modifier phase for the overlap.The phase number value should not exceed the maximum Phases defined. The function of the modifier phase(s) is defined by the overlapType selected.
7.5.2 Overlap Parameters
Figure 104 - Overlap Parameters Front Panel Screen
Overlap Number – INTEGER (0..32) The overlap number for objects in this row. The value shall not exceed the maxOverlaps supported by the CU (32). The value maps to the Overlap as follows: 1 = Overlap A, 2 = Overlap B etc.
Type – DROPDOWN The type of overlap operation for this row. The types are as follows:
Normal - The overlap output shall be controlled by the overlapIncludedPhases when this type is selected. The overlap output shall be green in the following situations:
• when an overlap included phase is green
• When an overlap included phase is yellow (or red clearance) and an overlap included phase is next. The overlap output shall be yellow when an included phase is yellow and an overlap included phase is not next. The overlap output shall be red whenever the overlap green and yellow are not ON.
MinusGreenYellow - The overlap output shall be controlled by the overlapIncludedPhases and the overlapModifierPhases if this type is selected. The overlap output shall be green in the following situations:
• when an overlap included phase is green and an overlap modifier phase is NOT green when an overlap included phase is yellow (or red clearance) and an overlap included phase is next and an overlap modifier phase is NOT green.
Overlap Type Tr_Gr Tr_Yel Tr_Red > 1 other 0 0.0 0.0 2 other 0 0.0 0.0 3 other 0 0.0 0.0 4 other 0 0.0 0.0 5 other 0 0.0 0.0 6 other 0 0.0 0.0 7 other 0 0.0 0.0 8 other 0 0.0 0.0 9 other 0 0.0 0.0 10 other 0 0.0 0.0 11 other 0 0.0 0.0 12 other 0 0.0 0.0 13 other 0 0.0 0.0 14 other 0 0.0 0.0 15 vother 0 0.0 0.0
Dly Flash Description 0.0 off A 0.0 off B 0.0 off C 0.0 off D 0.0 off E 0.0 off F 0.0 off G 0.0 off H 0.0 off I 0.0 off J 0.0 off K 0.0 off L 0.0 off M 0.0 off N v0.0 off O
86
• The overlap output shall be yellow when an overlap included phase is yellow and an overlap modifier phase is NOT yellow and an overlap included phase is not next. The overlap output shall be red whenever the overlap green and yellow are not ON.
Normal Ped - The overlap output shall be controlled by the overlaps included phases pedestrian intervals when this type is selected. The overlap output the following:
• when an overlap included phase is in walk the overlap will output walk
• the overlap will output walk when an overlap included phase is yellow (or red clearance) and an overlap included phase is next. The overlap output shall be yellow when an included phase is yellow and an overlap included phase is not next. The overlap output shall be red/don’t walk whenever the overlap green and yellow are not ON.
• The overlap output shall flash don’t walk (pedestrian clear) when the included phase times the ped clear interval and an included phase is not next.
MinClrPed
FYA - The overlap output shall be controlled by the overlap included phases and modifier phases when this type is selected. The FYA overlap outputs the flashing yellow arrow, yellow, and red intervals for the FYA signal head. The flashing yellow arrow is the overlap’s green output. The associated protected left-turn phase outputs the solid green arrow. The overlap green output shall flash in the following situations:
• when an overlap included phase is green
• When an overlap included phase is yellow (or red clearance) and an overlap included phase is next. The overlap output shall be yellow when an included phase is yellow and an overlap included phase is not next. The overlap output shall be red whenever the overlap green and yellow are not ON.
The overlap output shall be blanked/dark
• When an overlap modified phase is green (modifier phase is the protected left turn phase associated with the FYA signal head)
Blanking - The overlap output shall be controlled by the overlap included phases and modifier phases when this type is selected. The overlap behaves as follows:
• The overlap is red when an included phase is not green
• The overlap is green an included phase is green, or when the overlap is green and an included phase next is green.
• The overlap is yellow when an included phase is yellow and phase next is not an included phase
• The overlap is blank/dark when a modifier phase is green.
Other - The overlap is disabled.
Trail Green – INTEGER (0..255) Overlap Trailing Green Parameter in seconds (0-255 sec). When this value is greater than zero and the overlap green would normally terminate, the overlap green shall be extended by this additional time.
Trail Yellow – INTEGER (0..255)
87
Overlap Trailing Yellow Change Parameter in tenth seconds. When the overlap green has been extended (Trailing Green), this value shall determine the current length of the Yellow Change interval for the overlap.
Trail Red – INTEGER (0..255) Overlap Trailing Red Clear Parameter in tenth seconds (0-25.5 sec). When the overlap green has been extended (Trailing Green), this value shall determine the current length of the Red Clearance interval for the overlap.
Delay – INTEGER (0..255) The delay of the overlap green in seconds (0-255 seconds).
Flash – ENABLED/DISABLED If enabled, the overlap green interval will flash the green channel output instead of a steady or solid indication.
Description – STRING Description can be added for user information only to specify use of overlap. This parameter has no effect on the operation of the overlap.
88
7.6 Coordination Menu
Figure 105-Coordination Front Panel Screen
Figure 106-Coordination Remote Front Panel Screen
7.6.1 Coordination Parameters
Figure 107-Coordination Parameters Front Panel Scre en
Operational Mode Pattern 2 Correction Mode shortway Max Mode maximum1 Force Mode fixed
Coordination 1.Coordination Parameters 2.Patterns 3.Splits 4.Ring Offsets 5.Split Copy
89
Figure 108-Coordination Parameters Remote Front Pan el Screen
Operation Mode – DROPDOWN This object defines the operational mode for coordination. The possible modes are:
• Automatic - this mode provides for coord operation, free, and flash to be determined automatically by the possible sources (i.e. Interconnect, Time Base, or System Commands).
• Manual Free - this mode provides for Free operation without coordination or Automatic Flash from any source.
• Manual Flash - this mode provides for Automatic Flash without coordination or Free from any source.
• All Red Flash – this mode provides for Automatic Red Flash on all channels.
• Pattern 1-128 - these modes provides for Coord operation running this pattern. This selection of pattern overrides all other pattern commands.
Correction Mode – DROPDOWN This object defines the Coord Correction Mode. The possible modes are:
• Other - the coordinator establishes a new offset by a mechanism not defined in this standard.
• Dwell - when changing offset, the coordinator shall establish a new offset by dwelling in the coord phase(s) until the desired offset is reached.
• Shortway (Smooth) - when changing offset, the coordinator shall establish a new offset by adding or subtracting to/from the timings in a manner that limits the cycle change. This operation is performed in a device specific manner.
• AddOnly - when changing offset, the coordinator shall establish a new offset by adding to the timings in a manner that limits the cycle change. This operation is performed in a device specific manner.
Max Mode – DROPDOWN This object defines the Coord Maximum Mode. The possible modes are:
• Other the maximum mode is determined by some other mechanism not defined in this standard.
90
• maximum1 the internal Maximum 1 Timing shall be effective while coordination is running a pattern.
• maximum2 the internal Maximum 2 Timing shall be effective while coordination is running a pattern.
• maxInhibit the internal Maximum Timing shall be inhibited while coordination is running a pattern.
Force Mode - DROPDOWN This object defines the Pattern Force Mode. The possible modes are:
• Other - the CU implements the default force mode (default is Fixed as defined below).
• Floating - each phase will be forced the split time after it becomes active. This allows unused split time to revert to the coord phase.
• Fixed - each phase will be forced at a fixed position in the cycle. This allows unused split time to revert to the following phase.
7.6.2 Patterns
Figure 109 - Patterns Front Panel Screen
Pattern 1 2 3 4 5 > Cycle Time 0 0 0 0 0 Offset 1 0 0 0 0 0 Offset 2 0 0 0 0 0 Offset 3 0 0 0 0 0 Split Number 0 0 0 0 0 Sequence Number 0 0 0 0 0 Reference Point yel yel yel yel yel Max Mode max1 max1 max1 max1 max1 phPln 1 1 1 1 1 detPln 1 1 1 1 1 pedPln 1 1 1 1 1
91
Figure 110 - Patterns Remote Front Panel Screen
Cycle – INTEGER (0..255) The Cycle object specifies the length of the pattern cycle in seconds (NEMA TS 2 range: 30-255). A pattern cycle time less than adequate to service the minimum requirements of all phases shall result in Free mode. The minimum requirements of a phase with a not-actuated ped include Minimum Green, Walk, Pedestrian Clear, Yellow Clearance, and Red Clearance; the minimum requirements of a phase with an actuated pedestrian include Minimum Green, Yellow Clearance, and Red Clearance. If the pattern cycle time is zero and the associated split table (if any) contains values greater than zero, then the CU shall utilize the split time values as maximum values for each phase.
Offset 1- INTEGER (0..255) The Offset defines by how many seconds (NEMA TS 2 range: 0-254) the local time zero shall lag the system time zero (synchronization pulse) for this pattern. An offset value equal to or greater than the cycle time shall result in Free being the operational mode. While this condition exists, the Local Free bit of unitAlarmStatus and the LocalOverride bit of shortAlarmStatus shall be set to one (1).
Offset 2 - INTEGER (0..255) The second offset for a given pattern.
Offset 3 - INTEGER (0..255) The third offset for a given pattern.
Split – INTEGER (0..255) This object is used to locate information in the splitTable to use for this pattern. This value shall not exceed the maxSplits object value.
Sequence Number – INTEGER (0..16) This object is used to locate information in the sequenceTable to use with this pattern. This value shall not exceed the maxSequences object value.
Reference Point - ENUMERATION The reference point of the coordinated phase for a given pattern. The following options are available:
- RED
- YELLOW
- GREEN
patternMaxMode – ENUMERATION Max Mode for a given pattern, for it to be effective Max Mode in Coordination Parameters table should be set to other. The following options are available:
- Max1
- Max2
- Max3
phPln – INTEGER(0..10) When the extended mode is enabled, this is the phase plan number that the controller uses for the current phase parameters.
92
detPln – INTEGER(0..10) When the extended mode is enabled, this is the detector plan number that the controller uses for the current detector parameters.
pedPln – INTEGER(0..10) When the extended mode is enabled, this is the pedestrian detector plan number that the controller uses for the current pedestrians detector parameters.
7.6.3 Splits
Figure 111- Splits Front Panel Screen
Figure 112- Splits Remote Front Panel Screen
SplitTime - INTEGER (0..255) The time in seconds the splitPhase is allowed to receive (i.e. before a Force Off is applied) when constant demands exist on all phases. In floating coordForceMode, this is
Phase Time Coord Ref Point Mode 1 20 . . other 2 40 C R maxVehRcl 3 20 . . other 4 40 . . other 5 20 . . other 6 40 C . maxVehRcl 7 20 . . other 8 40 . . other 9 0 . . other 10 0 . . other 11 0 . . other 12 0 . . other 13 0 . . other 14 0 . . other 15 v0 . . other
93
always the maximum time a non-coordinated phase is allowed to receive. In fixed coordForceMode, the actual allowed time may be longer if a previous phase gapped out.
The splitTime includes all phase clearance times for the associated phase. The split time shall be longer than the sum of the phase minimum service requirements for the phase. When the time is NOT adequate to service the minimum service requirements of the phase, Free Mode shall be the result. The minimum requirements of a phase with a not-actuated ped include Minimum Green, Walk, Pedestrian Clear, Yellow Clearance, and Red Clearance; the minimum requirements of a phase with an actuated pedestrian include Minimum Green, Yellow Clearance, and Red Clearance.
If the cycleTime entry of the associated patternTable entry is zero (i.e. the device is in Free Mode), then the value of this object shall be applied, if non-zero, as a maximum time for the associated phase.
If the critical path through the phase diagram is less than the cycleTime entry of the associated patternTable entry, all extra time is alloted to the coordination phase in each ring.
If the critical path through the phase diagram is greater than the cycleTime entry of the associated patternTable entry (and the cycleTime is not zero) the device shall be set to the Free Mode.
While the Free Mode condition exists, the Local Override will be set to one (1).
Coord – ENABLED/DISABLED To select the associated phase as a coordinated phase this object shall be set to ‘C’.
Ref Point – ENABLED/DISABLED If enabled this phase will be used for reference point.
Mode – ENUMERATION This object defines operational characteristics of the phase. The following options are available:
- other; the operation is not specified in this standard none; no split mode control.
- minimumVehicleRecall; this phase operates with a minimum vehicle recall.
- maximumVehicleRecall; this phase operates with a maximum vehicle recall.
- pedestrianRecall; this phase operates with a pedestrian recall.
- maximumVehicleAndPedestrianRecall; this phase operates with a maximum vehicle & pedestrian recall.
- phaseOmitted; this phase is omitted.
7.6.4 Ring Offsets
Figure 113- Ring Offsets Front Panel Screen
Mode – INTEGER (0..5) This value will offset the corresponding ring by the number of seconds specified.
Ring 1 2 3 4 5 6 7 > Offset Num 0 0 0 0 0 0 0
94
7.6.5 Split Copy Copies Split Plans from Split Plan x to Split Plan Y
Note: When the Split Plan data has been successfully copied the “Data copied successfully” message will be shown.
7.7 Scheduler
Figure 114-Scheduler Front Panel Screen
Figure 115-Scheduler Remote Front Panel Screen
7.7.1 Schedules
Scheduler 1.Schedules 2.Day Plans 3.Actions 4.Day plan Copy
Day Plan DOW Month DOM > Sch SMTWTFS JFMAMJJASOND 123456 1 0 ....... ............ ...... 2 0 ....... ............ ...... 3 0 ....... ............ ...... 4 0 ....... ............ ...... 5 0 ....... ............ ...... 6 0 ....... ............ ...... 7 0 ....... ............ ...... 8 0 ....... ............ ...... 9 0 ....... ............ ...... 10 0 ....... ............ ...... 11 0 ....... ............ ...... 12 0 ....... ............ ...... 13 0 ....... ............ ...... 14 v0 ....... ............ ......
1 2 3 7890123456789012345678901 ......................... ......................... ......................... ......................... ......................... ......................... ......................... ......................... ......................... ......................... ......................... ......................... ......................... .........................
95
Figure 116-Schedules Front Panel Screen
The Schedule table specifies the appropriate day plan for the CU. The plan is determined by comparing the current month (MONTH), day of week (DOW) and date of month (DOM) to the appropriate fields. The settings for MONTH, DOW and DOM are connected with a logical AND. The event with the most specific date will be selected. If the current date matches multiple entries the more specific event based on the MONTH settings will be used. If the MONTH is the same, the most specific DOM will be used. If that is still the same, the most specific DOW will be used. If that is still the same, the first occurrence within the time base event table shall be selected. "More specific" means the least number of bits set within a field.
Day Plan- INTEGER (0..20) The Day Plan that will be used if the associated schedule entry is selected.
DOW – ENABLED/DISABLED The appropriate days of the week must be enabled (‘X’) for the schedule event to run on that specific day of week. If the schedule is to run on any day of the week, all days of the week (Mon-Fri) should be enabled.
Month – ENABLED/DISABLED The appropriate months of the year must be enabled (‘X’) for the schedule event to run on that specific month. If the schedule is to run on any month of the year, all months should be enabled.
DOM – ENABLED/DISABLED The appropriate days of the month must be enabled (‘X’) for the schedule event to run on that specific day of the month. If the schedule is to run on any day of the month, all days of the month should be enabled.
7.7.2 Day Plans
Figure 117-Day Plan Front Panel Screen
Event – READ ONLY Identifies the specific event within the day plan table.
Hour – INTEGER (0..23) Hour when the specified time based action will be selected
Min – INTEGER (0..59)
Event Hour Minute Action 1 6 0 1 2 0 0 0 3 0 0 0 4 0 0 0 5 0 0 0 6 0 0 0 7 0 0 0 8 0 0 0 9 0 0 0 10 0 0 0
96
Minute when the specified time based action will be selected
Time Base Action – INTEGER (0..100) Specifies when the time based action to run at the associated hour and minute during the day.
7.7.3 Actions
Figure 118 - Actions Front Panel Screen
Action – INTEGER (0..100) The time based action number for rows within this table.
Pattern – INTEGER (0..128) The Pattern that shall be active when this Action is active. The value shall not exceed the value of maxPatterns, except for flash or free. A pattern of zero indicates that no pattern is being selected. A pattern = 0 relinquishes control to an entity of a lower priority than timebase and allows that entity to control (i.e., interconnect if available).
AuxFunc – ENABLED/DISABLED If set (‘X’) the Auxiliary Function output shall be enabled when the time base action is selected
SpcFunc – ENABLED/DISABLED If set (‘X’) the Special Function output shall be enabled when the time base action is selected
Pattern Aux Special Function Action 123 12345678 1 Pattern 1 123 12...... 2 Pattern 2 ... ........ 3 0 ... ........ 4 0 ... ........ 5 0 ... ........ 6 0 ... ........ 7 0 ... ........ 8 0 ... ........ 9 0 ... ........ 10 0 ... ........ 11 0 ... ........ 12 0 ... ........ 13 0 ... ........ 14 v0 ... ........
97
7.7.4 Day Plan Copy
Figure 119-Phase Copy Front Panel Screen
Day Plan – INTEGER (1..20) Copies Day Plan Events from Day Plan x to Day Plan Y
Note: When the Day Plan Events data has been successfully copied the “Data copied successfully” message will be shown.
Copy Data: From Day Plan 1 to Day Plan 2 Press ENTER to copy data
98
7.8 Preemptions
Figure 120-Preemptions Front Panel Screen
7.8.1 Preemption Parameters
Figure 121-Preemption Parameters Front Panel Screen
Link – INTEGER (0..8) This object provides a means to define a higher priority preempt to be combined (linked) with this preempt. At the end of Dwell time, the linked preempt shall receive an automatic call which shall be maintained as long as the demand for this preempt is active. Any value that is not a higher priority preempt or a valid preempt shall be ignored. The value shall not exceed the maxPreempts object value.
Delay – INTEGER(0..600) Preempt Delay Time in seconds (0-600 sec). This value determines the time the preempt input shall be active prior to initiating any preempt sequence. A non-locking preempt input which is removed prior to the completion of this time shall not cause a preempt sequence to occur.
MinDuration – INTEGER(0..65535) Preempt Minimum Duration Time in seconds (0..65535). This value determines the minimum time during which the preempt is active. Duration begins timing at the end of Preempt Delay (if non zero) and will prevent an exit from the Dwell state until this time has elapsed.
Preempt 1 2 3 4 > Link 0 0 0 0 Delay 0 0 0 0 MinDuration 0 0 0 0 MaxPresence 0 0 0 0 MinGreen 0 0 0 0 MinWalk 0 0 0 0 EnterPedClear 0 0 0 0 EnterYelChg 25.5 25.5 25.5 25.5 EnterRedClear 25.5 25.5 25.5 25.5 TrackGreen 0 0 0 0 TrackYelChg 25.5 25.5 25.5 25.5 TrackRedClear 25.5 25.5 25.5 25.5 DwellGreen 0 0 0 0 ExitPedClear 0 0 0 0 ExitYelChg v25.5 25.5 25.5 25.5
ExitRedClear 25.5 25.5 25.5 25.5
Preemptions 1.Preempt Parameters 2.Preempt Config 3.Preempt Flags
99
MaxPresence – INTEGER (0..255) Preempt Maximum Presence time in seconds (0-65535 sec). This value determines the maximum time which a preempt call may remain active and be considered valid. When the preempt call has been active for this time period, the CU shall return to normal operation. This preempt call shall be considered invalid until such time as a change in state occurs (no longer active). When set to zero the preempt maximum presence time is disabled.
MinGreen – INTEGER (0..255) Preempt Minimum Green Time in seconds (0-255 sec). A preempt initiated transition shall not cause the termination of an existing Green prior to its display for lesser of the phase's Minimum Green time or this period.
MinWalk – INTEGER (0..255) Preempt Minimum Walk Time in seconds (0-255 sec). A preempt initiated transition shall not cause the termination of an existing Walk prior to its display for the lesser of the phase's Minimum Walk time or this period.
EnterPedClear – INTEGER (0..255) Enter Ped ClearTime in seconds (0-255 sec). This parameter controls the ped clear timing for a normal Walk signal terminated by a preempt initiated transition. A preempt initiated transition shall not cause the termination of a Pedestrian Clearance prior to its display for the lesser of the phase's Pedestrian Clearance time or this period.
EnterYelChg – FLOAT (0..25.5) Enter Yellow Change in tenth seconds (0-25.5 sec). This parameter controls the yellow change timing for a normal Yellow Change signal terminated by a preempt initiated transition. A preempt initiated transition shall not cause the termination of a Yellow Change prior to its display for the lesser of the phase’s Yellow Change time or this period.
EnterRedClear – FLOAT (0..25.5) Enter Red Clear in tenth seconds (0-25.5 sec). This parameter controls the red clearance timing for a normal Red Clear signal terminated by a preempt initiated transition. A preempt initiated transition shall not cause the termination of a Red Clear prior to its display for the lesser of the phase’s Red Clear time or this period.
TrackGreen - INTEGER (0..255) Track Clear Green Time in seconds (0-255 sec). This parameter controls the green timing for the track clearance movement. The phase(s) active during the Track Green interval are enabled in preemptTrackPhase object.
TrackYelChg - FLOAT (0..25.5) Track Clear Yellow Change time in tenth seconds (0-25.5 sec). The lesser of the phase’s Yellow Change time or this parameter controls the yellow timing for the track clearance movement. Track clear phase(s) are enabled in the preemptTrackPhase object.
TrackRedClear - FLOAT (0..25.5) Track Clear Red Clear time in tenth seconds (0-25.5 sec). The lesser of the phase’s Red Clear time or this parameter controls the Red Clear
DwellGreen – INTEGER (1..255)
100
Minimum Dwell Time in seconds (1-255 sec). This parameter controls the minimum timing for the dwell movement. The phase(s) active during the Dwell interval are enabled in preemptDwellPhase object. The Dwell interval shall not terminate prior to the completion of Preempt Duration Time, Preempt Dwell Time, & the call is no longer present.
ExitPedClear - FLOAT (0..25.5) Exit Pedestrian Clearance time in tenth seconds (0-25.5 sec). The lesser of the phase’s Pedestrian Clear time or this parameter controls the Ped Clear.
ExitYelChg - FLOAT (0..25.5) Exit Yellow Clearance time in tenth seconds (0-25.5 sec). The lesser of the phase’s Yellow Clear time or this parameter controls the Yellow Clear.
ExitRedClear - FLOAT (0..25.5) Exit Red Clearance time in tenth seconds (0-25.5 sec). The lesser of the phase’s Red Clear time or this parameter controls the Red Clear.
7.8.2 Preemption Config
Figure 122-Preemption Config Front Panel Screen
TrackPhs – OCTET STRING Each octet within the octet string contains a phaseNumber that shall be active during the Preempt Track Green interval.
DwellPhs – OCTET STRING Each octet within the octet string contains a phaseNumber that is allowed during the Preempt Dwell interval.
DwellPeds – OCTET STRING Each octet within the octet string contains a phaseNumber indicating a pedestrian movement that is allowed during the Preempt Dwell interval.
ExitPhs – OCTET STRING Each octet within the octet string contains a phaseNumber that shall be active following Preempt.
Preempt 1 2 3 > TrackPhs DwellPhs DwellPeds ExitPhs TrackOvls DwellOvls CycPhs CycPeds CycOvls
101
TrackOvls – OCTET STRING Each octet within the octet string contains an overlapNumber that shall be active during the Preempt Track Clear intervals
DwellOvls – OCTET STRING Each octet within the octet string contains an overlapNumber that is allowed during the Preempt Dwell interval
CycPhs – OCTET STRING Each octet within the octet string contains a phaseNumber that is allowed to cycle during the Preempt Dwell interval.
CycPeds – OCTET STRING Each octet within the octet string contains a phaseNumber indicating a pedestrian movement that is allowed to cycle during the Preempt Dwell interval.
CycOvls – OCTET STRING Each octet within the octet string contains an overlapNumber that is allowed to cycle during the Preempt Dwell interval.
7.8.3 Preemption Flag
Figure 123-Preemption Flags Front Panel Screen
NonLockingMemory – ENABLED/DISABLED Allows an operation which does not require detector memory. When set enabled a preempt sequence shall not occur if the preempt input terminates prior to expiration of the preemptDelay time.
NoteOverrideFlash – ENABLED/DISABLED Allows this preempt to NOT override Automatic Flash. When enabled this preempt shall not override Automatic Flash.
NotOverrideNextPreempt - ENABLED/DISABLED Allows this preempt to NOT override the next higher numbered Preempt. When enabled this preempt shall not override the next higher numbered preempt. This parameter shall be ignored when preemptNumber equals maxPreempts.
FlashDwell – ENABLED/DISABLED The phases listed will flash Yellow during the Dwell phase. All active phases not listed in the preemptDwellPhase shall flash Red. If any conflicting phase numbers are listed in the preemptDwellPhase then all active phases shall flash Red.
1 Preempt 1234567890123456 NonLockingMemory ................ NotOverideFlash ................ NotOverrideNextPreempt ................ FlashDwell ................
102
7.9 Advanced IO Menu
Figure 124-Advance IO Front Panel Screen
7.9.1 Channels
Figure 125 – Channels Front Panel Screen
7.9.1.1 Channel Config
Figure 126 - Channel Configuration Front Panel Scre en
Channels 1.Channel Config 2.Channel Options 3.Options Per Color 4.Concurrency Mode & Control 5.Manual Channel Concurrency 6.Auto Concurrency 7.Conflict Monitor Card
Channel Control Type Control Source 1 phaseVehicle 1 2 phaseVehicle 2 3 phaseVehicle 3 4 phaseVehicle 4 5 phaseVehicle 5 6 phaseVehicle 6 7 phaseVehicle 7 8 phaseVehicle 8 9 other 1 10 other 1 11 other 1 12 other 1 13 phasePedestrian 2 14 phasePedestrian 4 15 vphaseP edestrian 6
Advanced IO 1.Channels 2.IO Modules 3.Input Pins 4.Output Pins 5.Phase Intervals 6.Pedestrian Intervals
103
Channel Type – DROPDOWN This object defines the channel control type (Vehicle Phase, Pedestrian Phase, or Overlap):
• vehicle Phase - The channel controls a vehicle phase display.
• pedestrian Phase - The channel controls a pedestrian phase display.
• overlap - The channel controls an overlap display.
• Advance Warning Flash – The channel controls a advance warning flash sign.
• other - The channel controls another type of display.
Control Source – INTEGER(0..16) This object defines the channel control source device number (which Phase or Overlap). The value shall not exceed maxPhases or maxOverlaps as determined by channelControlType object:
• Value 00 = No Control (Not In Use)
• Value 01 = Phase 01 or Overlap A
• Value 02 = Phase 02 or Overlap B
• Value 15 = Phase 15 or Overlap O
• Value 16 = Phase 16 or Overlap P
7.9.1.2 Channel Options
Figure 127-Channel Options Front Panel Screen
Flash Yellow – ENABLED/DISABLED This object defines the channel state during Automatic Flash. Enabled is ‘X’ (Flash yellow), while disabled is ‘.’ (Yellow Dark)
Flash Red - ENABLED/DISABLED This object defines the channel state during Automatic Flash. Enabled is ‘X’ (Flash Red), while disabled is ‘.’ (Red Dark)
Flash Alt - ENABLED/DISABLED Flash Alternate Half Hertz - This object defines the channel state during Automatic Flash. Enabled is ‘X’, while disabled is ‘.’.
7.9.1.3 Options Per Color
1 2 > Channel 1234567890123456789012345678 FlashYellow ............................ FlashRed 12345678.................... FlashAlt ............................
104
Figure 128-Channel Options Per Color Front Panel Sc reen
Startup Clearance Hold Type – DROPDOWN This object defines the behavior of the channel during the clearance hold time period.
• Off - The channel is dark
• On - The channel is ON.
• Flash – The channel flashes.
• Alt Flash – The channel flashes in an alternate manner.
7.9.1.4 Channel Concurrency Mode & Control
Figure 129-Channel Concurrency Front Panel Screen
Mode – ENUMERATION - auto – Controller will automatically read phase permissives from conflict monitor
- manual – Controller will use user programmed permissives
Command – ENUMERATION - clear – existing programmed permissives will be cleared from controller
- copyFromConflictMonitor – copy permissives from conflict monitor
- copyFromGeneratedConcurrency – copy permissives from controller generated concurrencies. Controller calculates permissives based on sequence and channel assignments.
Color Startup Clearance Hold Type 1 red off 2 yellow off 3 green off
Mode auto Command clear
105
7.9.1.5 Manual Channel Concurrency
Figure 130- Manual Channel Concurrency Front Panel Screen
7.9.1.6 Auto Channel Concurrency
Figure 131- Auto Channel Concurrency Front Panel Sc reen
1 > 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 . . . 5 6 . . . . . . . . 5 . . . . . 2 . . 5 6 . . . . . . 3 . 5 . . . . . 3 . . . 7 8 . . . . . . . 6 . . . . 4 . . 7 8 . . . . . 4 . 6 . . . . 5 . . . . . . . 3 . . . . . . . 6 . . . . . . 3 . 5 . . . . . 7 . . . . . . 4 . . . . . . 8 . . . . . 4 . 6 . . . . 9 . . . . . . . . . . . 10 . . . . . . . . . . 11 . . . . . . . . . 12 . . . . . . . . 13 . 5 . . . . . 14v . 6 . . . .
1 > 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 . . . 5 6 . . . . . . . . 5 . . . . . 2 . . 5 6 . . . . . . 3 . 5 . . . . . 3 . . . 7 8 . . . . . . . 6 . . . . 4 . . 7 8 . . . . . 4 . 6 . . . . 5 . . . . . . . 3 . . . . . . . 6 . . . . . . 3 . 5 . . . . . 7 . . . . . . 4 . . . . . . 8 . . . . . 4 . 6 . . . . 9 . . . . . . . . . . . 10 . . . . . . . . . . 11 . . . . . . . . . 12 . . . . . . . . 13 . 5 . . . . . 14v . 6 . . . .
106
7.9.1.7 Conflict Monitor Card
Figure 132- Conflict Monitor Card Front Panel Scree n
7.9.2 IO Modules The cabinet configuration is organized by IO Modules. By declaring a list of IO modules that matches the physical IO modules in the cabinet, users can support various cabinet configurations. When the type of a module is changed, the input and output pins for this module are automatically reset to their default fun ction assignments.
The following configurations are examples for common cabinet types:
7.9.2.1 TS2 type 1 for a Nema controller:
Figure 133-TS2 type 1 for Nema controller Screen
1 > 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 . . . 5 6 . . . . . . . . 5 . . . . . 2 . . 5 6 . . . . . . 3 . 5 . . . . . 3 . . . 7 8 . . . . . . . 6 . . . . 4 . . 7 8 . . . . . 4 . 6 . . . . 5 . . . . . . . 3 . . . . . . . 6 . . . . . . 3 . 5 . . . . . 7 . . . . . . 4 . . . . . . 8 . . . . . 4 . 6 . . . . 9 . . . . . . . . . . . 10 . . . . . . . . . . 11 . . . . . . . . . 12 . . . . . . . . 13 . 5 . . . . . 14v . 6 . . . .
Module Type 1 TS2_TF1_BIU 2 TS2_TF2_BIU 3 TS2_DR1_BIU 4 TS2_DR2_BIU 5 TS2_MMU 6 TS2_Small_A_Connector 7 None 8 None 9 None 10 None
107
7.9.2.2 TS2 type 1 for a 2070 controller:
Figure 134-TS2 type 1 for a 2070 controller
7.9.2.3 TS1 for a Nema controller:
Figure 135-TS1 for a Nema controller
7.9.2.4 TS1 for a 2070 controller:
Figure 136-TS1 for a 2070 controller
Module Type 1 2070_8 2 None 3 None 4 None 5 None 6 None 7 None 8 None 9 None 10 None
Module Type 1 TS1_A_B_C_D_Connectors 2 None 3 None 4 None 5 None 6 None 7 None 8 None 9 None 10 None
Module Type 1 TS2_TF1_BIU 2 TS2_TF2_BIU 3 TS2_DR1_BIU 4 TS2_DR2_BIU 5 TS2_MMU 6 2070_2N 7 None 8 None 9 None 10 None
108
7.9.2.5 Caltran 332:
Figure 137-Caltran 332
7.9.2.6 ITS cabinet:
Figure 138-ITS cabinet
Module Type 1 ITS_OUT14_SIU1 2 ITS_OUT6_SIU3 3 ITS_IN_SIU1 4 ITS_IN_SIU2 5 ITS_IN_SIU3 6 ITS_CMU 7 None 8 None 9 None 10 None
Module Type 1 Caltran_332 2 None 3 None 4 None 5 None 6 None 7 None 8 None 9 None 10 None
109
7.9.2.7 Simulation Module:
Figure 139-Simulation
7.9.3 Input Pins
Figure 140-Input Pins Front panel Screen
Description – STRING A text description of the input.
Control Type - DROPDOWN This object defines the input function type. Each row represents one input pin assigned to one input function.
Index - INTEGER This object defines the index associated with the input function
7.9.4 Output Pins
Input Description Control Type Index 1 VehicleDetCall 1 2 VehicleDetCall 2 3 VehicleDetCall 3 4 VehicleDetCall 4 5 VehicleDetCall 5 6 VehicleDetCall 6 7 VehicleDetCall 7 8 VehicleDetCall 8 9 VehicleDetCall 9 10 VehicleDetCall 10 11 VehicleDetCall 11 12 VehicleDetCall 12
Module Type 1 SIMULATION 2 None 3 None 4 None 5 None 6 None 7 None 8 None 9 None 10 None
110
Figure 141-Output Pins Front panel Screen
Description – STRING A text description of the output.
Type – DROPDOWN This object defines the pin control type (Channel, Special Function, or other): channel - The pin is controlled by a channel output. Special Function - The pin is a special function output.
Index - INTEGER This object defines the index associated with the output function
7.9.5 Phase Intervals
Figure 142-Phase Intervals Front Panel Screen
Red - DROPDOWN
Interval Red Yellow Green Type 1 on off off red 2 on off off red 3 off off on green 4 off off on green 5 off off on green 6 off off on green 7 off off on green 8 off on off yellow 9 on off off red 10 on off off red 11 on off off red 12 on off off red
Output Description Control Type Index 1 ChRedDontWalk 1 2 ChYelPedClear 1 3 ChGreenWalk 1 4 ChRedDontWalk 2 5 ChYelPedClear 2 6 ChGreenWalk 2 7 ChRedDontWalk 3 8 ChYelPedClear 3 9 ChGreenWalk 3 10 ChRedDontWalk 4 11 ChYelPedClear 4 12 ChGreenWalk 4 13 ChRedDontWalk 5 14 ChYelPedClear 5 15 v ChGreenWalk 5
111
This parameter defines the state of the phase's Red output during the timing of this phase interval: Off, On, flashing, alternate flashing.
Yellow – DROPDOWN This parameter defines the state of the phase's Yellow output during the timing of this phase interval: Off, On, flashing, alternate flashing.
Green – DROPDOWN This parameter defines the state of the phase's Green output during the timing of this phase interval: Off, On, flashing, alternate flashing.
Type – DROPDOWN This parameter defines the type of phase interval: not_def, Red, Yellow, Green.
7.9.6 Pedestrian Intervals
Figure 143-Pedestrian Intervals Front Panel Screen
Don’t Walk – DROPDOWN Pedestrian Interval Don’t Walk Parameter - This parameter defines the state of the phase's Don't Walk output during the timing of this ped interval (Off, On, Flashing, or Alternate Flashing).
Ped Clear – DROPDOWN Pedestrian Interval Clearance Parameter - This parameter defines the state of the phase's pedestrian Clearance output during the timing of this ped interval (Off, On, Flashing, or Alternate Flashing).
Walk – DROPDOWN Pedestrian Interval Walk Parameter - This parameter defines the state of the phase's pedestrian Walk output during the timing of this pedestrian interval (Off, On, Flashing, or Alternate Flashing).
Type – DROPDOWN This parameter defines the type of pedestrian interval (undefined, Don’t Walk, Ped Clear, or Walk).
Interval Dont Walk Clear Walk > 1 on off off 2 on off off 3 off off on 4 off off on 5 flash off off 6 on off off 7 on off off 8 on off off
Type not_def not_def not_def not_def ped_clear not_def not_def not_def
112
7.10 Countdown Displays
Figure 144 – Countdown Displays Front Panel Screen
Address – INTEGER (0..255) The address of the countdown display.
Phase – INTEGER (0..40) The phase associated with this countdown display. Zero means the Display is not used.
Protected Time – INTEGER(0..255) The protected time for this countdown display in sec. The default Value is 10 seconds.
7.11 Manual Control
Figure 145 – Manual Control Front Panel Screen
Ring – READONLY The ring index value.
Phase – INTEGER (0..40) The number of the phase that should become active in the associated ring when the associated manual control group is called. 0 means that there is no phase for the associated ring and group.
Ring 1 2 3 4 5 6 > Phase 0 0 0 0 0 0
Display 1 2 3 4 5 6 > Address 0 0 0 0 0 0 Phase 0 0 0 0 0 0 Protected Time 10 10 10 10 10 10
113
7.12 Peer
Figure 146 – Peer Front Panel Screen
PeerID – INTEGER(0..65535) When using the User programs, the peer ID is used to identify the peer device in the statement definition. The peer ID is not used for the Master controller feature. It’s a globally unique ID across all devices.
IP/Host - OCTET STRING The network resolvable hostname or dot notation IP address for the Peer.
SnmpPort - INTEGER (0..65535) The controller's SNMP port, used for NTCIP communications.
HttpPort - INTEGER (0..65535) The controller's HTTP port, used for HTTP communications. This is used for the User programs feature. 0 disables the feature.
SerPort - INTEGER (0..255) The asynchronus serial port number. This could be used for the Master controller feature. 0 disables the feature.
SerAddr - INTEGER (0..255) The asynchronus serial drop address when using a serial port. 0 disables the feature.
MasterSec - INTEGER (0..255) When the peer device is used for the Master controller feature, this object is the section of which the controller is a member. Set this to 0 exclude the controller from any section.
PeerTmOut - INTEGER (0..255)
# PeerID IPAddr/Hostname SnmpPort > 1 0 161 2 0 161 3 0 161 4 0 161 5 0 161 6 0 161 7 0 161 8 v 0 161
# <HttpPort SerPort SerAddr MastrSec > 1 80 0 0 0 2 80 0 0 0 3 80 0 0 0 4 80 0 0 0 5 80 0 0 0 6 80 0 0 0 7 80 0 0 0 8 v 80 0 0 0
# <PeerTmOut Description 1 15 2 15 3 15 4 15 5 15 6 15 7 15 8 v 15
114
Description - String A textual description of the peer controller.
7.13 Master
Figure 147 – Master Front Panel Screen
7.13.1 Sections
Figure 148 – Sections Front Panel Screen
Section - READONLY The number of the section defined by the current row. The section is active only if it has an Algorithm value of 'signature'.
Control - ENUMERATION The algorithm to be used to match input data to a plan. Set to 'none' to turn off Traffic Responsive for the section. Possible values include the following:
- none - no algorithm is chosen for the section / the section is not in use.
- signature - the signature algorithm is chosen to match vehicle data to configured values.
Per - INTEGER (1..255)
Section Control Per Poll Min TTF 1 none 60 240 1 300 2 none 60 240 1 300 3 none 60 240 1 300 4 none 60 240 1 300 5 none 60 240 1 300 6 none 60 240 1 300 7 none 60 240 1 300 8 none 60 240 1 300 9 none 60 240 1 300 10 none 60 240 1 300 11 none 60 240 1 300 12 none 60 240 1 300 13 none 60 240 1 300 14 none 60 240 1 300 15 vnone 60 240 1 300
Master 1.Sections 2.Detectors 3.Signatures 4.Signature Criteria
115
The sampling period (in seconds) to be utilized by the section for polling volume and occupancy. Each controller within the section must be configured to use the same sampling period.
Poll - INTEGER (0..65535) The minimum time (in seconds) between executions of the matching algorithm. A value of 0 indicates that Per (the sampling period for the section) should be used.
Min - INTEGER (1..255) The minimum number of controllers in this section that must have Comm equal to 'responding' for it to be considered valid for control. If the number of responding controllers falls below this value, the section will be considered to have failed, with control returned to the individual controllers.
TTF - INTEGER (0..65535) Time (in seconds) in which an intersection in the section may have Comm equal to 'notResponding' before it is treated as failed.
7.13.2 Detectors
Figure 149 – Detectors Front Panel Screen
Sensor - READONLY The number of the sensor defined by the current row. A "sensor" is a re-indexing of local controllers' detector numbers, to allow for the detectors to be applied to the section as a whole.
Ctrlr - INTEGER (0..255) The controller that hosts the detector, referring to a controller defined in the Controllers configuration. A value of 0 excludes the sensor from use.
Det - INTEGER (0..255) The detector from which the data are to be gathered.
VF - INTEGER (1..80)
Sensor Ctrlr Det VF 1 0 0 10 2 0 0 10 3 0 0 10 4 0 0 10 5 0 0 10 6 0 0 10 7 0 0 10 8 0 0 10 9 0 0 10 10 0 0 10 11 0 0 10 12 0 0 10 13 0 0 10 14 0 0 10 15 v0 0 10
116
The volume factor used in producing NV (normalized volume). The value of VF is the maximum effective volume in hundreds-of-vehicles per hour at saturation. For example, a value of 80 represents the assumed maximum, resulting from 4 lanes at a saturation flow of 2000 vph.
7.13.3 Signatures
Figure 150-Signatures Front Panel Screen
Section - INTEGER (1..16) The section for which the signatures are to be edited, as defined in the Sections configuration.
Sig - INTEGER (1..16) The number of the signature defined by the current row. A "signature" is a configuration of sensors and associated criteria, a match to which indicates a change to a configured pattern.
Pattern - INTEGER (0..255) The pattern number to be selected when the signature is a match. Pattern values indicate the following:
- 0: Standby - control is relinquished.
- 1-253: Pattern - the corresponding pattern is indicated.
- 254: Free - a mode of Free is indicated.
- 255: Flash - a mode of Automatic Flash is indicated.
MinDets - INTEGER (0..255) The minimum number of operational detectors that constitute a valid input to the signature comparison routine. If the number of operational detectors falls below this value, the signature will be ignored.
Sig Pattern MinDets 1 0 2 2 0 2 3 0 2 4 0 2 5 0 2 6 0 2 7 0 2 8 0 2 9 0 2 10 0 2 11 0 2 12 0 2 13 0 2 14 0 2 15 v0 2
Section
117
7.13.4 Signature Criteria
Figure 151 - Signature Criteria Front Panel Screen
Section - INTEGER (1..16) The section for which the signature criteria are to be edited, as defined in the Sections configuration.
Signature - INTEGER (1..16) The signature for which the criteria are to be edited, as defined in the Signatures configuration.
Criteria - READONLY The number of the signature criterion defined by the current row. A "signature criterion" is a configuration of a normalized volume and occupancy associated with a sensor, the match of which helps to indicate a match to a signature. Current conditions will match the signature with the criteria that collectively provide the best match.
Sensor - INTEGER (0..255) A reference to the Sensor within Detector configuration. A value of 0 excludes the criterion from use.
NV - INTEGER (0..65535) The volume match criterion, as a percentage of some expected or normalized value. This value is compared directly to the detector's NV.
NO - INTEGER (0..100) The occupancy match criterion, as a percentage. This value is compared directly to the detector's NO.
Criteria Sensor NV NO 1 0 0 0 2 0 0 0 3 0 0 0 4 0 0 0 5 0 0 0 6 0 0 0 7 0 0 0 8 0 0 0 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 v0 0 0
Section Signature
118
7.14 Prioritors
Figure 152 – Prioritor Front Panel Screen
7.14.1 Unit Settings
Prioritor Enabled – DISABLED/ENABLED Enables or disables the prioritor feature.
Lock Out Time – INTEGER(0..255) Prioritor Lock out Time.
7.14.2 Timing Settings
Figure 153 – Timing Settings Front Panel Screen
PriNum – READONLY Prioritor number.
Out Dly – INTEGER (0..255) Prioritor Sign Output Delay Time in sec.
7.14.3 Prioritor Phases
Figure 154-Prioritor Phases Front Panel Screen
PriNum – READONLY
Prioritor Enabled no Lock Out Time 0
Prioritor 1.Unit Settings 2.Timing settings 3.Prioritor Phases
PriNum Priority Phs 1 2 3 4 5 6 7 8
PriNum 1 2 3 4 5 6 7 8 Out Dly 0 0 0 0 0 0 0 0
119
Prioritor number.
Priority Phs – OCTECT STRING Each octet contains a phase number that is associated with this prioritor.
7.15 Loopback
Figure 155-Loopback Front Panel Screen
Each row in the loopback table defines an association between an output function (source) and an input function (result). If the source output function is on then the associated result input function will be on. Likewise when the source output function turns off the result input function also turns off. This feature provides a mechanism to virtually connect an output into an input without physically connecting the two pins with a loopback wire.
This feature can be used to enable or disable any input function by time of day. If the MaxTime scheduler is setup to turn enable a special function at different times of day then that special function can be looped back to enable or disable any result input function by time of day. For example, this feature could be used to enable or disable Ring Red Rest or Max II select by time of day.
Result – DROPDOWN This dropdown contains the same list of options as the Input Pins screen.
Idx – INTEGER The first Idx column is associated with the result input function. This value specifies the index to use for the corresponding result function.
Source – DROPDOWN This dropdown contains the same list of options as the Output Pins screen.
Idx – INTEGER The second Idx column is associated with the source output function. This value specifies the index to use for the corresponding source function.
Fct Result Idx Source Idx 1 notActive 0 notActive 0 2 notActive 0 notActive 0 3 notActive 0 notActive 0 4 notActive 0 notActive 0 5 notActive 0 notActive 0 6 notActive 0 notActive 0 7 notActive 0 notActive 0 8 notActive 0 notActive 0 9 notActive 0 notActive 0 10 notActive 0 notActive 0 11 notActive 0 notActive 0 12 notActive 0 notActive 0 13 notActive 0 notActive 0 14 notActive 0 notActive 0 15 vnotActive 0 notActive 0
120
7.16 User Programs
7.16.1 General Concept The user program feature allows users to program custom logic that cannot be done (or would be too convoluted to achieve) using the regular built-in features. User programs consist of statements, which are conceptually similar to lines of code when programming using common programming languages. The main field of each statement is the “Operation” field, which defines the main behavior of the statement. Operations can use 1 or 2 parameters, called Parameter A and Parameter B. Parameters consist of a main type and optionally, an index/value. The main type defines where the value is coming from. For instance, it could be a system state, a number, or a variable. Each statement returns a result value that can optionally be assigned to one of the system functions available: variable, system inputs, etc…
When enabled, a User Program runs 10 times per seconds. Program 1 is always enabled. The other programs are sub routines that could be called from another program.
7.16.2 Variables One important concept of the user program feature is the use of variables. There are 2 types of variables: local and global.
Each program supports local variables to pass data from one statement to another. As the name implies, the visibility scope of those variables is local, which means that program X cannot access the local variables of program Y. The local variables are reset to 0 each time the program runs.
The global variables, however, are shared between programs and other parts of the application software, like output assignments. They are not reset by the application software at each iteration. Those variables are convenient to do things like counters, where the state of the counter is persistent from one iteration to the next. They can also be used for output assignments. In this case, the global variable contains the state of the output the user would like to achieve. The desired output can then be mapped to the global variable. Global variables can also be exported to another controller for peer to peer communication.
7.16.3 User programs Description
User Programs 1.Description 2.Definition
121
Figure 156-User Program Description Screen
Description – STRING String describing a User program.
Program Description 1 2 3 4 5 6 7 v
122
7.16.4 Operations Result = A
The result contains the value of Parameter A. This is the equivalent of the older loopback functions. For instance, if one wants to have detector 1 being called when phase 2 is ON, it could be achieved with the following statement:
Figure 157-User Program Statement Operation
Result = A Index B
The result contains the value of the function assigned to Parameter A but with the index returned by parameter B. For instance, if one wants to have detector 1 being called when phase x is ON, where x is the value of local variable 1, this could be achieve with:
Figure 158-User Program Result = A Index B
Result = A Peer B
# Value Result Ind > 1 0 vehDetCall 1 2 0 None 0 3 0 None 0 4 0 None 0 5 0 None 0 6 0 None 0 7 0 None 0
# <Operation Param A Ind > 1 R=A Ind B PhOn 0 2 none none 0 3 none none 0 4 none none 0 5 none none 0 6 none none 0 7 none none 0
# <Param B Ind Dlay Ext Desc 1 LocVar 1 0.0 0.0 2 none 0 0.0 0.0 3 none 0 0.0 0.0 4 none 0 0.0 0.0 5 none 0 0.0 0.0 6 none 0 0.0 0.0 7 none 0 0.0 0.0
# Value Result Ind > 1 0 vehDetCall 1 2 0 None 0 3 0 None 0 4 0 None 0 5 0 None 0 6 0 None 0 7 0 None 0
# <Operation Param A Ind > 1 R=A PhOn 2 2 none none 0 3 none none 0 4 none none 0 5 none none 0 6 none none 0 7 none none 0
123
This operation is similar to “Result=A” but the value is coming from Peer B instead of the local controller.
Result = (A if B)
The result is the value of Parameter A if the value of parameter B is not 0, otherwise it’s 0.
Result = (A if !B)
The result is the value of Parameter A if the value of parameter B is 0, otherwise it’s 0.
Result = !A
The result is 0 if A is different than 0, otherwise, it’s 1.
Result = (A AND B)
The result is the result of the logical AND between A and B
Result = (A NAND B)
The result is the result of the logical NAND between A and B
Result = (A OR B)
The result is the result of the logical OR between A and B
Result = (A NOR B)
The result is the result of the logical NOR between A and B
Result = (A XOR B)
The result is the result of the logical NOR between A and B
Result = (A XNOR B)
The result is the result of the logical XNOR between A and B
Result = Latch(A,B)
The result is 1 when A becomes different than 0, and 0 when B turns becomes different than 0. In other words, A turns the latch ON, B turns it OFF.
Result = (A == B)
The result is 1 if A is equal to B, 0 otherwise.
Result = (A != B)
The result is 1 if A is different than B, 0 otherwise.
Result = (A > B)
The result is 1 if A is strictly greater than B, 0 otherwise.
124
Result = (A>= B)
The result is 1 if A is greater than or equal to B, 0 otherwise.
Result = (A < B)
The result is 1 if A is strictly less than B, 0 otherwise.
Result = (A <= B)
The result is 1 if A is less than or equal to B, 0 otherwise.
Result = (A + B)
The result is the addition of A and B.
Result = (A - B)
The result is the subtraction of A and B.
Result = (A * B)
The result is A times B.
Result = (A / B)
The result is A divided by B.
Result = (A Mod B)
The result is the remainder of the division of A by B
Result = Min(A, B)
The result is the minimum of A and B.
Result = Max(A, B)
The result is the maximum of A and B.
Jump A Lines if B
If B is different than 0, the next A lines of the program are being skipped. This is a way to achieve complex if then else statements.
Run Program A
Runs the program which number is parameter A.
Run Program A if B
Runs the program which number is parameter A if B is different than 0.
Return A if B
125
Terminate the current program and returns A to the Run Program statement of the parent program.
Clear Display if A
This is used for the user programmable screen. If A is different than 0, cleat the screen.
Display Description Row A Col B
Displays the string in the description field at position row A, col B on the user programmable screen.
Get Last Key
Result contains the last key that was pressed.
Beep
Makes the controller beeping.
Is Module A input B ON
Result is the state of IO Module A input B.
Is Module A output B ON
Result is the state of IO Module A output B.
Display Cursor if A
Display the cursor on the user programmable screen if A is different than 0.
Set Cursor Row A Col B
Moves the cursor to the user programmable screen at location Row A Col B.
Display A if B
Display the value of parameter A on the user programmable screen at the current location if B is different than 0.
Sleep A tenths if B
Stops the execution of all the programs for A tenths of a second if B is different than 0.
7.16.5 Examples
7.16.5.1 Counters Counters implementation can be achieved by incrementing a Global Variable by 1.
For instance, the following line increments the Global Variable 1 by 1 10 times per second. In the “Result Value” column, you can see the current value of the counter.
126
Figure 159-User Program example, counters
If we would like a counter in second, this could be achieved by dividing the tenth of a second counter by 10.
Figure 160-User Program example, counter in seconds
# Value Result Ind > 1 326 GlobalVar 1 2 32 None 0 3 0 None 0 4 0 None 0 5 0 None 0 6 0 None 0 7 0 None 0
# <Operation Param A Ind > 1 R=(A + B) GlobVar 1 2 R=(A / B) Previous 0 3 none none 0 4 none none 0 5 none none 0 6 none none 0 7 none none 0
# <Param B Ind Dlay Ext Desc 1 Number 1 0.0 0.0 2 Number 10 0.0 0.0 3 none 0 0.0 0.0 4 none 0 0.0 0.0 5 none 0 0.0 0.0 6 none 0 0.0 0.0 7 none 0 0.0 0.0
# Value Result Ind > 1 326 GlobalVar 1 2 0 None 0 3 0 None 0 4 0 None 0 5 0 None 0 6 0 None 0 7 0 None 0
# <Ind Operation Param A Ind > 1 1 R=(A + B) GlobVar 1 2 0 none none 0 3 0 none none 0 4 0 none none 0 5 0 none none 0 6 0 none none 0 7 0 none none 0
# <Param B Ind Dlay Ext Desc 1 Number 1 0.0 0.0 2 none 0 0.0 0.0 3 none 0 0.0 0.0 4 none 0 0.0 0.0 5 none 0 0.0 0.0 6 none 0 0.0 0.0 7 none 0 0.0 0.0
127
If we would like to get the number of seconds in the last minute, this could be achieved by using the mod Operation.
Figure 161-User Program example, counter seconds la st minute
8 Administration Menu
Figure 162-Administration Front Panel Screen
# Value Result Ind > 1 721 GlobalVar 1 2 72 None 0 3 12 None 0 4 0 None 0 5 0 None 0 6 0 None 0 7 0 None 0
# <Operation Param A Ind > 1 R=(A + B) GlobVar 1 2 R=(A / B) Previous 0 3 R=(A % B) Previous 0 4 none none 0 5 none none 0 6 none none 0 7 none none 0
# <Param B Ind Dlay Ext Desc 1 Number 1 0.0 0.0 2 Number 10 0.0 0.0 3 Number 60 0.0 0.0 4 none 0 0.0 0.0 5 none 0 0.0 0.0 6 none 0 0.0 0.0 7 none 0 0.0 0.0
Administration 1.Unit Information 2.Communication 3.Date & Time 4.Databases 5.Event Logs 6.FrontPanel 7.Security 8.Onboard diagnostics 9.App Management
128
Figure 163-Administration Remote Front Panel Screen
8.1 Unit Information
Figure 164-Unit Information Front Panel Screen
Controller ID – INTEGER(0..65535) This object is an integer that can be used to identify the controller. For instance, it could match the central system controller ID for consistency.
Main Street – STRING This field can be used to enter the name of the main street at the intersection. If set, the main street name is displayed on the main menu.
Side Street – STRING This field can be used to enter the name of the side street at the intersection. If set, the side street name is displayed on the main menu.
Agency – STRING This field can be used to enter the name of the agency responsible for the controller. If set, the agency name is displayed on the main menu.
DB Description – STRING This field can be used to enter a database description.
Controller ID 101 Main Street Main_Street Side Street Side_Street Agency Agency DB Description DB_Description
129
8.2 Communication
Figure 165-Communication Screen
8.3 IP Settings
Figure 166-IP Settings Front Panel Screen
IP Address Specifies the IP Address for the controller Ethernet interface. Changes take effect immediately after pressing the SET button.
Subnet Mask Specifies the subnet mask for the controller Ethernet interface. Changes take effect immediately after pressing the SET button.
Default Gateway Specifies the default Gateway for the controller routing table. Changes take effect immediately after pressing the SET button.
8.3.1 Serial Settings
Port 1 2 > Description SP1 SP2 Function None NTCIP Drop Address 1 1 Speed 9600 1200 Data Bits 8 8 Stop Bits 1 1 Parity None None Flow Control None RTS_CTS CTS Delay 0 100 RTS Extension 0 100
Adapter IP Address Subnet Mask Default Gateway 1 0.0.0.0 0.0.0.0 0.0.0.0 2 0.0.0.0 0.0.0.0 0.0.0.0
Communication 1.IP Settings 2.Serial Settings 3.NTCIP Settings 4.SNMP Statistics
130
Figure 167-Serial Settings Screen
Description – READONLY Description of the port.
Function – DROPDOWN • None – The port is not in use with the exception of SP6 that is connected to the
front panel even if the port gets set to None for safety reason.
• NTCIP – The port is used for NTCIP communication.
• FP_NTCIP – The port is used for communication with the NTCIP handheld remote front panel.
• FP_TEXT – The port is used for the front panel display.
• FP_Auto – The controller automatically detects the presence of the build-in front panel. If not present, the port is used for NTCIP communication with the handheld remote front panel.
• Master – The port is used for Master communication.
• PPP – The port is used for the Point to Point Protocol. When selected, the port can be used for dial-up connection. The controller then provides over serial all the features that are available over Ethernet.
• GPS – The port is used for GPS communication.
Drop Address - INTEGER(0..255) The NTCIP drop address that the controller will listen to on this port.
Speed - INTEGER(0..115200) The speed of the serial line.
Data Bits - ENUMERATION(7..8) The data bits settings for the port on this row.
Stop Bits - ENUMERATION(1..2) The stop bits setting for the port on this row.
Parity - DROPDOWN The parity setting for the port on this row.
• None
• Odd
• Even
Flow Control - DROPDOWN The flow control setting for the port on this row.
• None
• RTS_CTS – This is used for FSK modem communication.
CTS Delay – INTEGER(0..255) • CTS delay for FSK modem communication.
131
RTS Extension – INTEGER(0..255) • RTS Extension for communication with FSK modems.
8.3.2 NTCIP Settings
Figure 168-NTCIP Settings Front Panel Screen
Admin Community Name • Administrator community name used for NTCIP communication.
8.3.3 SNMP Statistics
Figure 169-SNMP Statistics Front Panel Screen
InPkts - READONLY The total number of Messages delivered to the SNMP entity from the transport service.
OutPkts - READONLY The total number of SNMP Messages which were passed from the SNMP protocol entity to the transport service.
InPkts 0 OutPkts 0 BadVersions 0 InBadCommunityNames 0 InBadCommunityUses 0 InASNParseErrs 0 InTooBigs 0 InNoSuchNames 0 InBadValues 0 InReadOnlys 0 InGenErrs 0 InTotalReqVars 0 InTotalSetVars 0 InGetRequests 0 InGetNexts 0 InSetRequests v0
InGetResponses 0 InTraps 0 OutTooBigs 0 OutNoSuchNames 0 OutBadValues 0 OutGenErrs 0 OutGetRequests 0 OutGetNexts 0 OutSetRequests 0 OutGetResponses 0 OutTraps 0
Admin Community Name Administrator
132
BadVersions - READONLY The total number of SNMP Messages which were delivered to the SNMP protocol entity and were for an unsupported SNMP version.
InBadCommunityNames - READONLY The total number of SNMP Messages delivered to the SNMP protocol entity which used a SNMP community name not known to said entity.
InBadCommunityUses- READONLY The total number of SNMP Messages delivered to the SNMP protocol entity which represented an SNMP operation which was not allowed by the SNMP community named in the Message.
InASNParseErrs- READONLY The total number of ASN.1 or BER errors encountered by the SNMP protocol entity when decoding received SNMP Messages.
InTooBigs- READONLY The total number of SNMP PDUs which were delivered to the SNMP protocol entity and for which the value of the error-status field is `tooBig'.
InNoSuchNames- READONLY The total number of SNMP PDUs which were delivered to the SNMP protocol entity and for which the value of the error-status field is `noSuchName'.
InBadValues- READONLY The total number of SNMP PDUs which were delivered to the SNMP protocol entity and for which the value of the error-status field is `badValue'.
InReadOnlys- READONLY The total number valid SNMP PDUs which were delivered to the SNMP protocol entity and for which the value of the error-status field is `readOnly'. It should be noted that it is a protocol error to generate an SNMP PDU which contains the value `readOnly' in the error-status field, as such this object is provided as a means of detecting incorrect implementations of the SNMP.
InGenErrs- READONLY The total number of SNMP PDUs which were delivered to the SNMP protocol entity and for which the value of the error-status field is `genErr'.
InTotalReqVars- READONLY The total number of MIB objects which have been retrieved successfully by the SNMP protocol entity as the result of receiving valid SNMP Get-Request and Get-Next PDUs.
InTotalSetVars- READONLY The total number of MIB objects which have been altered successfully by the SNMP protocol entity as the result of receiving valid SNMP Set-Request PDUs.
InGetRequests- READONLY The total number of SNMP Get-Request PDUs which have been accepted and processed by the SNMP protocol entity.
InGetNexts- READONLY
133
The total number of SNMP Get-Next PDUs which have been accepted and processed by the SNMP protocol entity.
InSetRequests- READONLY The total number of SNMP Set-Request PDUs which have been accepted and processed by the SNMP protocol entity.
InGetResponses- READONLY The total number of SNMP Get-Response PDUs which have been accepted and processed by the SNMP protocol entity.
InTraps- READONLY The total number of SNMP Trap PDUs which have been accepted and processed by the SNMP protocol entity.
OutTooBigs- READONLY The total number of SNMP PDUs which were generated by the SNMP protocol entity and for which the value of the error-status field is `tooBig'.
OutNoSuchNames- READONLY The total number of SNMP PDUs which were generated by the SNMP protocol entity and for which the value of the error-status is `noSuchName'.
OutBadValues- READONLY The total number of SNMP PDUs which were generated by the SNMP protocol entity and for which the value of the error-status field is `badValue'.
OutGenErrs- READONLY The total number of SNMP PDUs which were generated by the SNMP protocol entity and for which the value of the error-status field is `genErr'.
OutGetRequests- READONLY The total number of SNMP Get-Request PDUs which have been generated by the SNMP protocol entity.
OutGetNexts- READONLY The total number of SNMP Get-Next PDUs which have been generated by the SNMP protocol entity.
OutSetRequests- READONLY The total number of SNMP Set-Request PDUs which have been generated by the SNMP protocol entity.
OutGetResponses- READONLY The total number of SNMP Get-Response PDUs which have been generated by the SNMP protocol entity.
OutTraps- READONLY The total number of SNMP Trap PDUs which have been generated by the SNMP protocol entity.
134
8.4 Date/Time
Figure 170-Date and Time Front Panel Screen
Date/Time Allows the User to set the local time on the controller. The following ranges are used: Hour (0-23), Min (0-59), Sec (0-59), Month (1-12), Day (1-31), Year (1970 -). Changes to the local Date/Time take effect immediately without requiring a controller restart.
Figure 171-Time Zone & DST Front Panel Screen
Time Zone This group of fields allows the User to change the GMT to localtime fixed offset and the Daylight savings rules. The GMT offset hour can be + or - 12 hours with 0-59 minutes.
Daylight Saving The selectable choices for Daylight Savings are: none, USA, and Europe, Australia, Tasmania, New Zealand, Brazil, Paraguay and Custom. Changes to any of the fields in the time zone group will not take effect until the controller is restarted.
Begin Month When the daylight saving field is set to Custom, this field can be used to enter the month when the daylight saving begins.
Begin Sunday Week When the daylight saving field is set to Custom, this field can be used to enter the week in the month when the daylight saving begins.
Time Zone GMT-7 MST Daylight Saving Disable DST Begin Month March Begin Sunday Week 2 End Month November End Sunday Week 1
New Date/Time Tuesday July 03 2012 16:43:29 Use <- or -> to select a field to edit. Use digit keys or +/- to change values. Press Enter to save the new time.
Date & Time 1.Date & Time 2.Time Zone & DST 3.NTP Settings
135
End Month When the daylight saving field is set to Custom, this field can be used to enter the month when the daylight saving ends.
End Sunday Week When the daylight saving field is set to Custom, this field can be used to enter the week in the month when the daylight saving ends.
Figure 172-NTP Settings Front Panel Screen
NTP Server Address This object is IP address/Hostname of the NTP server that the controller uses to sync its current time to.
8.5 Database Management
Figure 173-Database Management Screen
8.5.1 Save Database
Figure 174-Save Database Front Panel Screen
The Save Database screen is used to store a snapshot of the active database to the controller’s persistent file system. Each snapshot is stored in an initialization file that can be used to initialize the controller back to that state at any point in the future. MaxTime™ supports two different types of initialization files: default and user created. Default initialization files are prefixed with the name “Default:” and contain basic, standardized configurations to initialize the controller to a
Databases 1.Save Database 2.Select Database 3.Delete Database 4.Copy Database From USB 5.Copy Database To USB
NTP Server Address
Select DB:database.bin Press -/+ to select DB. Press 'ENTER' to delete DB.
Database Name:database.bin Press 'E' to edit. Press 'Enter' to save.
136
known default state. User initialization files are created by the user and can be used to save the current database at any time. In addition, user initialization files can be deleted or overwritten, while default files can not be modified.
The soft key bar buttons allow the user to save a new file or delete an existing user created file. The name of the new file can be edited as standard text entry field. Alternatively, if the focus is moved down to the list of available files the name in the edit box will reflect the highlighted item. Any user file can be overwritten, but if a default file is selected the buttons on the soft key bar will be disabled to prevent overwriting or deleting the default file.
8.5.2 Reset Database
Figure 175-Load Database Front Panel Screen
The Load Database screen displays both standard configurations and user created initialization files. After selecting the appropriate file, the user will be prompted to restart the controller (see Figure below), upon which the settings of the initialization file will be read into the controller’s database and override the current controller setting (Warning – This initialization permanently erases all current settings in the controller and cannot be undone).
8.5.3 Copy Database From USB Databases can be copied from a FAT formatted USB Flash Drive. Insert the flash drive into a USB port on the controller and select “Copy Database from USB” menu. Use ‘+’ and ‘-‘ key to select database to copy to controller. Press ‘Enter.’ Screen will display confirmation when database copy is complete.
8.5.4 Copy Database To USB Databases can be copied to a FAT formatted USB Flash Drive from the controller. Insert the flash drive into a USB port on the controller and select “Copy Database to USB” menu. Use ‘+’ and ‘-‘ key to select database to copy to the USB Flash Drive. Press ‘Enter.’ Screen will display confirmation when database copy is complete.
8.6 Event logs
Figure 176-Event Logs Front Panel Screen
Event Logs 1.View Logs 2.Clear Logs
Select DB:database.bin Press -/+ to select DB. Press 'ENTER' to reset DB.
137
Figure 177-View Logs Front Panel Screen
8.7 Front Panel
Figure 178-Function Keys Front Panel Screen
Function keys can be assigned to menus on this screen. However, an easier way is to go the screen that needs to be assigned, press the F key and then the desired Function key. The key is then associated with the menu that is currently being displayed.
Function Key- READONLY The function key that corresponds to the function key on the controller front panel.
Menu Address – OCTET STRING The menu address associated to the function key. The address is the sequence of key presses needed to access a given menu from the main menu, with the exception of screens that are accessed using the “9.More” button. If a menu is accessed by pressing “9.More” and then number x, the menu sub address will be 9 + x.
8.8 Onboard Diagnostics Screen will display feedback confirmation for each key pressed on the keypad. This feature is used to diagnose a bad keypad.
FrontPanel 1.Function Keys
Function Key Menu Address 1 2 1.1 3 1.6 4 3.5.1 5 2.2.1 6 2.2.2 7 2.6 8 3.4
Log Description 1 02/07/11 11:47:03 Response Fault,11 2 02/07/11 11:47:03 Response Fault,10 3 02/07/11 11:47:03 Response Fault,131 4 02/07/11 11:47:03 Response Fault,129 5 02/07/11 11:47:03 Response Fault,128 6 02/07/11 11:46:59 Response Fault,10 7 02/07/11 11:46:59 Response Fault,131 8 02/07/11 11:46:59 Response Fault,129 9 02/07/11 11:46:59 Response Fault,128 10 02/07/11 11:46:59 Response Fault,11 11 02/07/11 11:46:55 Response Fault,131 12 02/07/11 11:46:55 Response Fault,129 13 02/07/11 11:46:55 Response Fault,128 14 02/07/11 11:46:55 Response Fault,11 15 v02/07/11 11:46:55 Response Fault,10
138
8.9 App management The Application Management utility allows a user to select between software versions of MaxTime that currently reside on the controller. In addition, versions can be deleted using the ‘d’ key. Once the desired software version is selected, the controller must be power cycled to launch the new version of MaxTime.
9 Web Server User Interface
In addition to the Remote Front Panel, MaxTime™ also supports a web based user interface. Linux ATC controllers run the web server directly on the controller itself, but 2070 controllers can not support hosting the web server directly. A web interface is still supported on the 2070, but the web server must be run on a separate Windows PC which acts as a proxy between the user’s browser and the 2070 (this mode of operation is referred to as the Remote Mode web server).
The first step in setting up a Remote Mode web server is to copy the lighttpd folder from the installation disc to the c:\ drive on a Windows PC that will host the web server. Note, the PC running the web server and the PC running the web browser can be the same computer. After copying the lighttpd folder run the C:\lighttpd\sbin\start-lighttpd.bat script file which will start the web server. Open a web browser and enter the IP address of the web server in the browser address bar. If the web server and browser are running on the same machine enter “http://localhost” for the address. A page similar to the following will be displayed:
Figure 179-Web Server Target IP
In Remote Mode, the home screen will display the Target IP address. This parameter specifies the IP address used to contact the controller. This paramater does not actually modify the IP address of the controller itself, it simply specifies the send address for all communication requests
139
from the web server to the controller. The IP address of the controller can be still be changed from the web user interface, but this is a separate option located under the Administration –> Communication menu.
In general, read write parameters will only be saved on the controller when the user presses the “Apply” button. Read only variables are continuously updated and the current refresh rate is displayed at the bottom of the page. The Status, Controller, and Administration subsections on the web user interface are consistent with the layout on the QTERM handheld terminal. See the associated chapters in the MaxTime™ Technical Reference Manual for detailed descriptions of each parameter.
140
10 Optional Components 10.1 Adaptive Control The goal of the optional adaptive control feature is to prolong the time before saturated conditions occur and recover faster from saturated conditions once they have occurred. For a detailed explanation of operation and parameter entrys, the user should refer to the MaxTime™ Adaptive Control Operations Manual which accompanies this option. (Note: The MaxTime™ Adaptive Control feature is only currently available on Linux ATC hardware platforms.)
The MaxTime™ adaptive control utilizes an enhanced local controller adaptation of methods developed through the US Federal Highway Administration /Siemens Gardner Transportation ACS-Lite Project (1, 2)
1) ACS Lite Project Overview – R. Ghaman, D. Gettman, S. Shelby – presentation to Transportation Research Board Annual Meeting – Adaptive Traffic Signal Control Workshop Washington DC January 11, 2004.
2) ACS Lite FHWA Adaptive Control Closed Loop Systems – R. Ghaman presentation to Baltimore Regional Traffic Signal Forum December 14, 2005, Baltimore, Maryland.
10.1.1 Adaptive Split Tuning The Adaptive Split tuning algorithm is designed to move available time from phases that are under-saturated to phases that are over-saturated. It utilizes the EQUISAT (Equal Saturation) concept. Split tuning is accomplished in a two step process:
Step 1: Estimate Degree of Saturation for each Phase
Step 2: Minimize the maximum degree of saturation on any Phase
Multi-Ring barrier and cycle time constraints are applied. Progression is accommodated in the Split Tuning Algorithm execution by allowing coordinated phases to have priority in the adding to split allocations based on historic cyclic vehicle arrival profiles.
10.1.2 Adaptive Cycle Tuning The Adaptive Cycle Tuning Algorithm adapts (incrementally increases/decreases) the cycle time for the controller (or a group of controllers that include adjacent controllers) to better handle saturated conditions. When phase saturation levels at a critical intersection reach User defined threshold(s), cycle length is commanded to increase by a User programmable number of seconds. Multiple cycle increments are possible by programming multiple total saturation thresholds points at the designated Critical Intersection. Likewise, once saturation levels at the Critical subside back below the threshold point (minus hysterias value) , cycle length is reduced by same increment(s).
10.1.3 Adaptive Offset Tuning
The adaptive Offset Tuning Algorithm adapts to changes in the cyclic vehicle platoon arrival profiles between intersections. For each roadway link, the difference in the pattern Offsets between intersections is correlated to smoothed real-time platoon arrival profiles. Pattern Offsets are then incrementally fine-tuned to optimize throughput on heavily traveled corridors and to minimize overall stopped delays.
141
10.2 Traffic Responsive 10.2.1 Concept
Intelight Traffic Responsive employs portions of the NTCIP 1210 draft specification to create a signature-based traffic responsive system, which will operate between an Intelight MaxTime controller (as the traffic responsive "master") and any set of IP-capable ASC-compliant subordinate controllers. Each MaxTime unit can retrieve detector data from up to 255 controllers, partitioned into 1 to 16 independent sections. Based upon detector input to each section, Traffic Responsive will determine the best match to one of the configured signatures, and command all controllers within that section to the configured pattern.
10.2.2 Configuration
A Traffic Responsive configuration involves several steps, typically in the following order:
1. Configure the section or sections to be used. Each section has an algorithm evaluation period and failure criteria. Set the "Algorithm" parameter to "none" to ensure that nothing happens until configuration is complete.
2. Configure each subordinate controller within the sections. Each controller has connection point and section membership information.
3. Configure the sensors (also known as "system detectors"). Each sensor refers to a detector present on one of the subordinate controllers, and contains weighting information.
4. Configure the signatures. There may be up to 16 signatures per section, each of which may contain a set of signature criteria and a target pattern.
5. Configure the signature criteria. There may be up to 255 criteria per signature, each of which refers to a sensor and contains target volume and occupancy values.
6. Enable each configured section by setting the "Algorithm" parameter to "signature".
Note that each subordinate controller must have the corresponding patterns properly configured independent of Traffic Responsive. Also note that each subordinate controller must share the same detector polling interval of all other controllers within a given section. Failure to match polling intervals will result in a poll fault for each unmatched sensor.
Upon changing the configuration, Traffic Responsive may take up to 10 seconds to update and respond to the new configuration.
142
10.2.3 Operation
Traffic Responsive will attempt to poll all controllers within a section, one controller at a time. Upon completing a section poll, Traffic Responsive will attempt to determine a target pattern for the section, and will set that pattern to each controller if successful. Upon failure, Traffic Responsive will allow the controllers' backup timers to revert them to local control. Note that a large number of controllers running on a slow IP network may require longer poll times in order to ensure that the section has enough time to make a complete iteration.
