3000E Operating Manual

Operating Manual
3000/3000E Controller ®
3000 Series TS1/TS2/NTCIP Traffic Signal Controllers

®
Operating Manual
3000 and 3000E ®

Traffic Signal Controllers
NEMA TS1/TS2 TRAFFIC CONTROLLERS
11/10/2008
Copyright © 2008 Peek Traffic Corporation
All rights reserved.
Information furnished by Peek Traffic is believed to be accurate and reliable, however Peek does not
warranty the accuracy, completeness, or fitness for use of any of the information furnished. No license is
granted by implication or otherwise under any intellectual property. Peek reserves the right to alter any of
the Company's products or published technical data relating thereto at any time without notice.
No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or
via any electronic or mechanical means for any purpose other than the purchaser’s personal use without
the expressed, written permission of Peek Traffic Corporation, a Signal Group Company.
Peek Traffic Corporation.

2906 Corporate Way
Palmetto, FL 34221
U.S.A.
Trademarks
The 3000, 3000E, 3000 Series, M3000, CLMATS, and IQ Central are trademarks or registered trademarks
of Peek Traffic Corporation in the USA and other countries. Microsoft and Windows are trademarks or
registered trademarks of Microsoft Corporation. Other brands and their products are trademarks or
registered trademarks of their respective holders.
8204C - 3000/3000E Operating Manual Assembly

8202A - 3000/3000E Operating Manual Contents (Rev 4)
99-343 - 3000/3000E Operating Manual Cover
Quick Contents
Figures .......................................................................................................................xii
Preface — About This Manual ...................................................................................1
Chapter 1 — Introduction to the 3000 Series ...........................................................5
Chapter 2 — Status Displays ...................................................................................27
Chapter 3 — Programming Instructions.................................................................83
Chapter 4 — Detectors .......................................................................................... 163
Chapter 5 — Overlaps............................................................................................ 181
Chapter 6 — The Basics of Coordination ............................................................ 211
Chapter 7 — Coordination Programming ............................................................ 221
Chapter 8 — Time of Day Functions .................................................................... 275
Chapter 9 — Preemption ....................................................................................... 291
Chapter 10 — Comm and System Setup ............................................................. 345
Chapter 11 — Unit Configuration and Security Codes ...................................... 373
Chapter 12 — TS 2 Type 1 Operation................................................................... 395
Chapter 13 — Utilities ............................................................................................ 417
Appendix A — Time of Day Circuit Descriptions................................................ 429
Appendix B — Preemption Programming Forms ............................................... 433
Appendix C — 3000/3000E Connector Pins ........................................................ 437
Appendix D — Passage Time Settings ................................................................ 461
Glossary .................................................................................................................. 465
Index ........................................................................................................................ 505
3000 Series Traffic Controllers iii

Contents
Figures....................................................................................................................... xii
Preface — About This Manual................................................................................... 1
Purpose and Scope ................................................................................................................................. 1
Assumptions ............................................................................................................................................ 1
Related Documents ................................................................................................................................. 2
Technical Assistance............................................................................................................................... 2
Conventions Used in this Manual ............................................................................................................ 3
Typographic Conventions ................................................................................................................. 3
Keyboard and Menu Conventions..................................................................................................... 3
Symbol Conventions ......................................................................................................................... 4
Chapter 1 — Introduction to the 3000 Series........................................................... 5
Overview.................................................................................................................................................. 6
Hardware in the 3000 Series ................................................................................................................... 8
Version 3000 Traffic Controller Hardware......................................................................................... 8
Version 3000E Traffic Controller Hardware ...................................................................................... 9
User Interface.................................................................................................................................. 12
Display ............................................................................................................................................ 13
Keypad ............................................................................................................................................ 14
Communication Ports...................................................................................................................... 17
Other Features of the 3000 Series Hardware ................................................................................. 19
Configuration Options............................................................................................................................ 24
NEMA TS 1 ..................................................................................................................................... 24
NEMA TS 2, Type 1 (TS 2-1) .......................................................................................................... 24
NEMA TS 2, Type 2 (TS 2-2) .......................................................................................................... 24
Optional Modules ............................................................................................................................ 25
Usage With Conflict Monitors & Malfunction Management Units.................................................... 26
iv 3000 Series Traffic Controllers

Contents
Chapter 2 — Status Displays ...................................................................................27

Status Check Upon Startup ................................................................................................................... 28
Primary Controller Status Screen .......................................................................................................... 30
Controller Status Screen................................................................................................................. 30
Status Screen Navigation ............................................................................................................... 31
Layout of the Controller Status Screen ........................................................................................... 32
TS 2 Flash Error Messages ............................................................................................................ 36
Controller Status Screen Abbreviations .......................................................................................... 36
Alternate Controller Status Screen ........................................................................................................ 38
Additional Status Screens ..................................................................................................................... 39
Normal I/O Screen .......................................................................................................................... 40
Density Status Screen .................................................................................................................... 41
Outputs Status Screens .................................................................................................................. 43
Inputs Status Screens ..................................................................................................................... 45
Dynamic Detector Display Screens ................................................................................................ 47
I/O Configuration Status Screens ................................................................................................... 49
Coordination Status Screen ............................................................................................................ 54
Time of Day Status Screen ............................................................................................................. 57
TOD Dynamic Circuits Status Screens ........................................................................................... 58
Preemption Status Screens ............................................................................................................ 59
Coordination Functions Screen ............................................................................................................. 62
Time of Day Functions Screens ............................................................................................................ 62
Preemption Functions Screens ............................................................................................................. 62
Voltages Screen .................................................................................................................................... 63
Overlap Functions Status Screens ........................................................................................................ 64
Program Level & Revision Screen......................................................................................................... 65
Log Menu............................................................................................................................................... 66
MOE Log ......................................................................................................................................... 66
Volume/Occupancy Log.................................................................................................................. 68
Detector Failure Log ....................................................................................................................... 68
Event Log ........................................................................................................................................ 69
Keyboard Log.................................................................................................................................. 71
Pattern Change Log........................................................................................................................ 71
MMU Fault Log ............................................................................................................................... 72
Checksum Status Screens .................................................................................................................... 73
Clearing a Checksum Failure.......................................................................................................... 73
Special Case Checksum Errors ...................................................................................................... 74
Comm Status Screens........................................................................................................................... 75
UTCS Status Display ...................................................................................................................... 78
TS 2 Dynamic Help Screens ................................................................................................................. 80
BIU Failure Help Screen ................................................................................................................. 80
MMU Flash Help Screen................................................................................................................. 80
MMU Incompatibility Help Screen................................................................................................... 80
Diagnostics ............................................................................................................................................ 81
MMU Status Screen .............................................................................................................................. 82
Chapter 3 — Programming Instructions.................................................................83
First Time Setup of the 3000 Series Controller ..................................................................................... 84
Introduction ..................................................................................................................................... 84
Fundamental Requirements for Operation...................................................................................... 84
Additional Commonly-Used Options ............................................................................................... 84
Coordination, Time of Day, Preemption.......................................................................................... 84
Procedures to Set Up a New 3000 Controller ....................................................................................... 85
Summarized Setup Steps ............................................................................................................... 85
Detailed Setup Steps for Minimal Requirements ............................................................................ 86
Load a Default For Basic Programming.......................................................................................... 86
3000 Series Traffic Controllers v

Edit The Startup Phases And Interval ............................................................................................. 88
Edit Phases Enabled If Default Is not an Exact Match.................................................................... 89
Edit Phase Functions (Phase Recall Modes).................................................................................. 90
Editing Phase Times ....................................................................................................................... 94
Setting Up a Coordination Plan....................................................................................................... 95
Basic Procedure For Setting Up a TOD Plan.................................................................................. 95
Setting Up a Preemption Run ......................................................................................................... 96
Using First Time Setup Menus .............................................................................................................. 97
Menu Descriptions .......................................................................................................................... 98
Using the Controller Menu................................................................................................................... 101
Sequence/Start-up Configuration Screens.................................................................................... 102
Enhanced Sequence Configuration and Exclusive Ped................................................................ 104
Library of Default Sequence Diagrams ......................................................................................... 107
Phases, Rings, Co-Phase Groups and Barriers............................................................................ 108
Examples Using Co-Phase Groups .............................................................................................. 112
Exclusive Pedestrian Operation .................................................................................................... 117
Phase Recalls and Modes ................................................................................................................... 122
Timing Plan Assignable Recall Modes (Menu 1 Recall Modes) ................................................... 122
Timing Plan Assignable Phase Recall Definitions ........................................................................ 123
Per Unit Assignable Phase Functions........................................................................................... 128
Per Unit Phase Recall Definitions ................................................................................................. 129
Phase Times ................................................................................................................................. 133
Terms Used in Phase Timing........................................................................................................ 134
Volume Density Discussion ................................................................................................................. 139
Variable Initial Function................................................................................................................. 139
Gap Reduction Function ............................................................................................................... 141
Dual Entry ............................................................................................................................................ 143
Dual Entry by Time Plan Screens ................................................................................................. 143
Dual Entry Example ...................................................................................................................... 143
Dual Entry Misconception ............................................................................................................. 144
Single Entry Mode......................................................................................................................... 144
Conditional Service.............................................................................................................................. 145
Criteria for Conditional Service ..................................................................................................... 145
Conditional Service Example ........................................................................................................ 145
Conditional Service by Time Plan Screens ................................................................................... 146
Ped Options ......................................................................................................................................... 147
Auto Ped Clear With Manual Control Enable (MCE)..................................................................... 147
Enhanced Pedestrian Operation ................................................................................................... 147
Dual Ped Control........................................................................................................................... 147
Enhanced Options ............................................................................................................................... 148
Dynamic Omits.............................................................................................................................. 148
Dynamic Recalls ........................................................................................................................... 149
Uniform Controlled Flash .............................................................................................................. 150
Density Enables and Last Car Passage........................................................................................ 151
Simultaneous Gap Out.................................................................................................................. 152
Max 3 Options ............................................................................................................................... 153
Passage Sequential, Red Revert, Preempt Override ................................................................... 154
Dimming ........................................................................................................................................ 155
Lead Lag Phasing ......................................................................................................................... 156
Soft Flash ...................................................................................................................................... 159
Chapter 4 — Detectors........................................................................................... 163
Detector Menu ..................................................................................................................................... 164
Detector Assignments ......................................................................................................................... 164
Detection Modes.................................................................................................................................. 166
Call/Extend – Mode 0.................................................................................................................... 166
Call – Mode 1 ................................................................................................................................ 166
vi 3000 Series Traffic Controllers

Contents
Stretch/Delay – Mode 2 ................................................................................................................ 166

Stop Bar – Modes 3 and 4 ............................................................................................................ 167
Detector Lock Mode...................................................................................................................... 168
Detector Times (delay, stretch/stop bar) ............................................................................................. 169
Detector Delay Inhibits.................................................................................................................. 169
Detector Switch and Copy ................................................................................................................... 171
Switch And Copy Enables............................................................................................................. 171
Detector Switch and Copy Clock Disable ..................................................................................... 171
Switch And Copy Pattern Screens ................................................................................................ 172
Detector Failure Monitoring ................................................................................................................. 174
Absence Monitor Time Of Day, Erratic Monitor Enable ................................................................ 174
Lock Times.................................................................................................................................... 175
Absence Of Call ............................................................................................................................ 175
Minimum Presence ....................................................................................................................... 176
Erratic Counts Per Minute (TS 2).................................................................................................. 176
Loop Length .................................................................................................................................. 177
Failed Detector Phase and Fail Max Recall Times ....................................................................... 177
Pedestrian Detector Diagnostics................................................................................................... 178
System Sensor Assignment ................................................................................................................ 179
Third Car Detection Feature ................................................................................................................ 180
Chapter 5 — Overlaps............................................................................................ 181
General Description............................................................................................................................. 182
Overlap Channels and Compatibility............................................................................................. 183
Overlap Programming ......................................................................................................................... 185
Assignments & Types ................................................................................................................... 185
Start-Up, Card, Alternate Flash..................................................................................................... 191
Double Clearing Overlaps ................................................................................................................... 192
Double Clear Overlap Programming............................................................................................. 193
Double Clearing Overlaps–Example 1.......................................................................................... 195
Double Clearing Overlaps–Example 2.......................................................................................... 196
Pedestrian Overlaps ............................................................................................................................ 197
Ped Overlap Mode Screen............................................................................................................ 198
Advance Warning Logic (TS 2 Only) ................................................................................................... 202
Advance Warning Example........................................................................................................... 202
Advance Warning Set-Up Procedure............................................................................................ 203
Lead/Advance Green Overlaps ........................................................................................................... 207
Inhibiting Overlaps............................................................................................................................... 209
Chapter 6 — The Basics of Coordination ............................................................ 211
General Overview of Coordination ...................................................................................................... 212
Signal Timing in a Coordinated Environment ...................................................................................... 213
Cycle Length ................................................................................................................................. 213
Local Cycle ................................................................................................................................... 213
Split (Phase Allocation)................................................................................................................. 213
Local Cycle Reference Point......................................................................................................... 213
Master Cycle ................................................................................................................................. 214
Offset ............................................................................................................................................ 215
Synchronization Methods .................................................................................................................... 216
Historical Sources of Sync Pulses ................................................................................................ 216
Offset Seeking .............................................................................................................................. 216
Coordination of an Actuated Controller Unit ........................................................................................ 217
Functions Used to Coordinate an Actuated Controller.................................................................. 217
Example of Force Off And Permissive Placement ........................................................................ 217
Chapter 7 — Coordination Programming ............................................................ 221
Understanding the Coordination Menu................................................................................................ 222
3000 Series Traffic Controllers vii

Clear/Load Defaults............................................................................................................................. 223
Selection Sources................................................................................................................................ 224
Notes about Selection Sources..................................................................................................... 224
Basic Options ...................................................................................................................................... 225
Reference to End of Main St. ........................................................................................................ 225
Use % for Phase Allocation (Splits) ............................................................................................. 225
Offset Entry in % ........................................................................................................................... 225
Use of Fixed vs. Floating Force-Offs............................................................................................. 226
Permissive Type............................................................................................................................ 229
Computation Of Force Offs And Permissives ............................................................................... 235
Phase Re-Service and Early Coord Phase Return ....................................................................... 235
Cycles and Offset Times ..................................................................................................................... 236
Adjusting Offset Times in the Field ............................................................................................... 237
Minimum Cycle Length or Max Dwell............................................................................................ 237
4 Splits Per Cycle Mode................................................................................................................ 238
Coordination Phase Programming ...................................................................................................... 239
Phase Allocation.................................................................................................................................. 240
Entering Phase Allocation Times .................................................................................................. 240
Additional Details Concerning Phase Allocation ........................................................................... 242
Adjusting Allocation Times in the Field ......................................................................................... 242
Offset Seeking ..................................................................................................................................... 243
Types of Offset Seeking................................................................................................................ 243
Coordination Plan (COS/F) to TOD Circuits ........................................................................................ 245
Programming a Plan ..................................................................................................................... 245
Enhanced Coordination Options.......................................................................................................... 246
Operating Options ......................................................................................................................... 246
Cycle Sync Options....................................................................................................................... 252
Local Split Modes.......................................................................................................................... 257
No Early Release .......................................................................................................................... 262
C/S to Timing Plan ........................................................................................................................ 263
COS to LEAD/LAG........................................................................................................................ 264
Offset to Free ................................................................................................................................ 264
Using the Check Coordination Plan Feature ....................................................................................... 265
Setting Up a Check Coordination Plan.......................................................................................... 265
Executing the Check Coordination Plan........................................................................................ 267
Basic Coordination - An Example........................................................................................................ 269
Overview of This Example ............................................................................................................ 269
Defining the Selection Source....................................................................................................... 269
Basic Operating Modes................................................................................................................. 270
Cycle and Offset Times................................................................................................................. 271
Phase Allocations.......................................................................................................................... 272
Chapter 8 — Time of Day Functions..................................................................... 275
Overview.............................................................................................................................................. 276
TOD Data Entry Modes ....................................................................................................................... 277
Day Plans (event programming).......................................................................................................... 278
Erasing A Day Plan ....................................................................................................................... 278
Editing a Day Plan......................................................................................................................... 278
Deleting Events ............................................................................................................................. 279
Event Times .................................................................................................................................. 279
Types Of Events............................................................................................................................ 279
Circuit Plan Events........................................................................................................................ 279
C/O/S Pattern Events.................................................................................................................... 279
Circuit ON/OFF Events ................................................................................................................. 279
Event Screen Selection Shortcut .................................................................................................. 280
Automatic Circuit Reset At Midnight.............................................................................................. 280
Typical Day Plan Example................................................................................................................... 280
viii 3000 Series Traffic Controllers

Contents
Configuring Circuit Plans ..................................................................................................................... 282

Programming a Circuit Plan .......................................................................................................... 282
Configuring Week Plans ...................................................................................................................... 283
Configuring a Year Plan ...................................................................................................................... 284
Defining Exception Days ..................................................................................................................... 285
Circuit Overrides.................................................................................................................................. 286
Daylight Savings Time......................................................................................................................... 287
Sync Reference ................................................................................................................................... 288
Sync Reference Modes................................................................................................................. 288
Comparing Time Dependent And C/O/S Event Modes................................................................. 288
Sync Reference Times.................................................................................................................. 289
External Clock Reset Time ........................................................................................................... 289
Interrupter Mode ........................................................................................................................... 289
Setting the Date and Time................................................................................................................... 290
Chapter 9 — Preemption ....................................................................................... 291
Overview.............................................................................................................................................. 292
Basic Description of Preemption Operation .................................................................................. 292
Key Concepts Used in Preemption ............................................................................................... 293
Preemption Programming.................................................................................................................... 295
Viewing and Programming a Single Preemption Run................................................................... 295
Clearing a Single Preemption Run................................................................................................ 295
Clearing All Preemption Runs ....................................................................................................... 295
Loading Default Values to a Single Preemption Run.................................................................... 295
Editing A Preemption Run ................................................................................................................... 296
Per Run Data ................................................................................................................................ 296
Interval Data.................................................................................................................................. 308
Comparison of Cyclic, Fixed, and Dwell Intervals......................................................................... 315
Applying Exclusive PED During Preemption................................................................................. 320
Documents and Charts Supporting Preemption Programming..................................................... 321
Preemption Interval Table............................................................................................................. 321
Description Of Preempt Run Rejection (‘Run Invalid’) .................................................................. 322
Flash Plans ................................................................................................................................... 323
Quick Set-Up Procedures ............................................................................................................. 324
Placing a Manual Preemption Call ...................................................................................................... 332
Examples of Preemption Programming............................................................................................... 333
Chapter 10 — Comm and System Setup ............................................................. 345
Overview.............................................................................................................................................. 346
Closed Loop ID.................................................................................................................................... 347
Comm Setup........................................................................................................................................ 348
Setting Up Comm Port 2 ............................................................................................................... 349
Setting Up Comm Port 3 ............................................................................................................... 351
Setting Up an AT Modem String ................................................................................................... 352
Ethernet Setup .............................................................................................................................. 353
Additional Notes About Configuring Modems ............................................................................... 354
Phone Numbers................................................................................................................................... 361
Event Call-In ........................................................................................................................................ 362
Log Data .............................................................................................................................................. 364
Port 1 Setup......................................................................................................................................... 366
System Name ...................................................................................................................................... 370
Contact Name...................................................................................................................................... 371
HDLC Address..................................................................................................................................... 372
Chapter 11 — Unit Configuration and Security Codes ...................................... 373
Overview.............................................................................................................................................. 374
Security Codes .................................................................................................................................... 375
3000 Series Traffic Controllers ix

Restricting Access to Menus ............................................................................................................... 376
Restricting a Menu Selection ........................................................................................................ 376
Restoring a Menu Selection Back To Full Access ........................................................................ 376
Adding and Deleting Menus ................................................................................................................ 377
Adding/Deleting Menus ................................................................................................................. 377
To Restore a Menu Item ............................................................................................................... 377
Setting the Intersection Name ............................................................................................................. 378
EEPROM Settings/Audio Adjustment.................................................................................................. 379
Updating the Controller Firmware........................................................................................................ 380
Firmware Tools for Flash-Enabled Controllers.............................................................................. 382
Loading the New Firmware ........................................................................................................... 386
Updating the Modem Setup String ................................................................................................ 391
I/O Steering ......................................................................................................................................... 392
Output (Signal Head) Steering Programming ............................................................................... 392
Output Steering Examples ............................................................................................................ 394
Using Overlaps in Output Steering................................................................................................ 394
Chapter 12 — TS 2 Type 1 Operation ................................................................... 395
Overview.............................................................................................................................................. 396
The NEMA Standards for Controller Input and Output ................................................................. 396
Cabinet Components........................................................................................................................... 397
BIUs .............................................................................................................................................. 399
MMU.............................................................................................................................................. 400
Default BIU Input/Output Mapping....................................................................................................... 400
Customizing BIU Input and Output Mapping................................................................................. 404
Activating/Deactivating BIU I/O Mapping............................................................................................. 406
Activating I/O Mapping .................................................................................................................. 406
Deactivating the I/O Mapping........................................................................................................ 407
Clearing BIU I/O Mappings ........................................................................................................... 407
Configuring Input Mappings................................................................................................................. 408
Using Logical Operators with Input Mappings............................................................................... 409
Configuring Output Mappings.............................................................................................................. 410
Loading a Default NEMA Mapping ...................................................................................................... 410
Copying MMU Channels ............................................................................................................... 411
I/O Mapping Screen Abbreviations...................................................................................................... 413
Input and Output Pin Mapping Options ......................................................................................... 414
Chapter 13 — Utilities ............................................................................................ 417
Overview.............................................................................................................................................. 418
Default Data Load................................................................................................................................ 419
Transfer Menu ..................................................................................................................................... 420
Clear Logs ........................................................................................................................................... 420
EEPROM - RAM Copy ........................................................................................................................ 421
Restart Machine .................................................................................................................................. 422
Printer Menu ........................................................................................................................................ 423
Printer Setup ................................................................................................................................. 423
Printing Portions of the Controller Database................................................................................. 424
Copy Functions.................................................................................................................................... 425
Controller....................................................................................................................................... 425
Coordination Copy ........................................................................................................................ 426
Time of Day Copy ......................................................................................................................... 426
Preemption Copy .......................................................................................................................... 427
Request Download .............................................................................................................................. 428
BIU I/O Mapping .................................................................................................................................. 428
Appendix A — Time of Day Circuit Descriptions ................................................ 429
TOD Circuit Descriptions ..................................................................................................................... 430
x 3000 Series Traffic Controllers

Contents
Notes on the Definitions ...................................................................................................................... 431

Appendix B — Preemption Programming Forms ............................................... 433
Preemption Programming Forms ........................................................................................................ 434
Appendix C — 3000/3000E Connector Pins ........................................................ 437
Pin Assignments: MS-A Connector (TS 1 Controllers)........................................................................ 438
Pin Assignments: MS-B Connector (TS 1 Controllers)........................................................................ 440
Pin Assignments: MS-C Connector (TS 1 Controllers) ...................................................................... 442
Pin Assignments: 10-Pin MS-A Connector for TS 2 Type 1 ................................................................ 443
Pin Assignments: TS 2 Type 2 Through A-B-C Connectors ............................................................... 444
Inputs ............................................................................................................................................ 444
Outputs ......................................................................................................................................... 445
Pin Assignments: Closed Loop D Module ........................................................................................... 446
Auxiliary Connector (37 Pin) ......................................................................................................... 446
Preemption Connector (25 Pin) .................................................................................................... 447
Coordination Connector (26 Pin) .................................................................................................. 448
Pin Assignments: 12 Phase D Module ................................................................................................ 449
Pin Assignments: LMD D Module (63 pin CPC) .................................................................................. 452
Pin Assignments: Texas D Module...................................................................................................... 454
Circular Connector (57 Pin) .......................................................................................................... 454
AUX Connector (37 Pin) ............................................................................................................... 455
Pin Assignments: Las Vegas D Module .............................................................................................. 457
Circular Connector (57 Pin) .......................................................................................................... 457
25 Pin Connector .......................................................................................................................... 458
Communication Ports .......................................................................................................................... 459
Port 1–SDLC Connector ............................................................................................................... 459
Port 2–EIA-232 (RS-232C) Connector.......................................................................................... 459
Aux Connector .............................................................................................................................. 460
Port 3–Modem Connector............................................................................................................. 460
Appendix D — Passage Time Settings ................................................................ 461
Overview.............................................................................................................................................. 462
Selecting a Passage Time................................................................................................................... 462
Examples ...................................................................................................................................... 462
Glossary .................................................................................................................. 465
Quick Guide to Controller Functions.................................................................................................... 466
Quick Guide to Coordination Functions............................................................................................... 487
Quick Guide to Preemption Functions................................................................................................. 498
Acronyms............................................................................................................................................. 503
Index ........................................................................................................................ 505
3000 Series Traffic Controllers xi

Figures
Figure 1 – 3000 Controller ..................................................................................................................................................8
Figure 2 – 3000E Controller, typical TS 1 and TS 2 Type 2 configuration ...........................................................................9
Figure 3 – 3000E Controller, typical TS 2 Type 1 configuration...........................................................................................9
Figure 4 – Flash-enabled 3000E Controller (TS 2 Type 2 version)....................................................................................11
Figure 5 – ‘Flash Memory Enabled’ logo ...........................................................................................................................11
Figure 6 – Sample representation of a 3000 Series screen...............................................................................................13
Figure 7 – 3000E Keypad .................................................................................................................................................14
Figure 9 – Ports with DSP modem installed as Port 3 .......................................................................................................17
Figure 10 – Ports with second serial port installed as Port 3 .............................................................................................18
Figure 11 – Ports with fiber optic modem installed as Port 3 .............................................................................................18
Figure 12 – Ports with serial/Ethernet card installed as Port 3 ..........................................................................................18
Figure 13 – Self-test screen that appears upon power up .................................................................................................28
Figure 14 – Power-on Error Message with 3 database errors detected.............................................................................28
Figure 15 – Controller Status screen.................................................................................................................................30
Figure 16 – Navigating the status screens ........................................................................................................................31
Figure 17 – Detail: Top three lines of the controller status screen.....................................................................................32
Figure 18 – Detail: Middle four lines..................................................................................................................................33
Figure 19 – Alternate Controller Status screen..................................................................................................................38
Figure 20 – Normal I/O Status screen ...............................................................................................................................40
Figure 21 – Density Status screen ....................................................................................................................................41
Figure 22 – Density Status screen - Example 1 ................................................................................................................42
Figure 26 – Output Status screen - page 1 .......................................................................................................................43
Figure 27 – Output Status screen - page 2 .......................................................................................................................43
Figure 28 – Inputs Status screen - page 1 ........................................................................................................................45
Figure 29 – Inputs Status screen - page 2 - Ring Inputs ...................................................................................................45
Figure 30 – Inputs Status screen - page 3 - Machine Inputs .............................................................................................45
Figure 31 – Dynamic Detector Display screen - page 1 (TS 1)..........................................................................................47
Figure 32 – Dynamic Detector Display screen - page 1 (TS 2)..........................................................................................47
Figure 33 – Dynamic Detector Display screen - page 2 (TS 1 or 2)...................................................................................47
Figure 34 – I/O Module Configuration screen (TS 1 or TS 2 Type 2).................................................................................49
Figure 35 – I/O Module Configuration screen (TS 1 or TS 2 Type 2).................................................................................49
Figure 36 – I/O Module Configuration screen (TS 2 Type 1) .............................................................................................50
Figure 37 – I/O Module Configuration screen - Page 1 (TS 2 Type 1)...............................................................................50
Figure 38 – I/O Module Configuration screen - Page 2 (TS 2 Type 1)...............................................................................50
Figure 39 – D Module Status screen - page 1 ...................................................................................................................52
Figure 43 – Coordination Status screen ............................................................................................................................54
Figure 44 – Time of Day Status screen .............................................................................................................................57
Figure 45 – Time of Day Dynamic Circuits screen - page 1 ..............................................................................................58
Figure 46 – Preemption Run Status screen - page 1 ........................................................................................................59
Figure 49 – Voltages screen .............................................................................................................................................63
Figure 50 – Overlap Functions Status screen ...................................................................................................................64
Figure 51 – Program Level & Revision screen ..................................................................................................................65
Figure 52 – Log Menu.......................................................................................................................................................66
Figure 53 – MOE Log - type 1 ...........................................................................................................................................66
Figure 54 – MOE Log - type 2 ...........................................................................................................................................66
xii 3000 Series Traffic Controllers

Contents
Figure 55 – MOE Log - type 3...........................................................................................................................................67

Figure 56 – MOE Log - type 4...........................................................................................................................................67
Figure 57 – Volume/Occupancy Log screen .....................................................................................................................68
Figure 58 – Detector Failure Log screen...........................................................................................................................68
Figure 59 – Event Log screen ...........................................................................................................................................69
Figure 60 – Keyboard Log screen .....................................................................................................................................71
Figure 61 – Pattern Change Log screen ...........................................................................................................................71
Figure 62 – MMU Fault Log screen...................................................................................................................................72
Figure 63 – Reported checksum failure screen.................................................................................................................73
Figure 64 – Cleared checksum screen..............................................................................................................................74
Figure 65 – No checksum failures detected ......................................................................................................................74
Figure 66 – Special errors reported on the Checksum Error screen..................................................................................74
Figure 67 – Mizbat Dynamic Status Screen ......................................................................................................................75
Figure 68 – Mizbat Dynamic Status Screen after a cleared override.................................................................................75
Figure 69 – Port 2 Status screen ......................................................................................................................................76
Figure 70 – Port 3 Status screen ......................................................................................................................................77
Figure 71 – UTCS Dynamic Display Screen when UTCS set to None ..............................................................................78
Figure 72 – UTCS Dynamic Display Screen when UTCS set to Protocol90......................................................................78
Figure 73 – UTCS Dynamic Display Screen when UTCS set to Stamford ........................................................................79
Figure 71 – Diagnostics Warning screen ..........................................................................................................................81
Figure 72 – Diagnostics Menu ..........................................................................................................................................81
Figure 73 – MMU Status screen .......................................................................................................................................82
Figure 74 – Locate ‘First Time Setup’ on the Main Menu ..................................................................................................86
Figure 75 – Controller default data load ............................................................................................................................86
Figure 76 – Screen indicating a default data load .............................................................................................................87
Figure 77 – Editing startup phases and intervals ..............................................................................................................88
Figure 78 – Sequence Configuration - Ring setup.............................................................................................................89
Figure 79 – Sequence Configuration - Setting Up co-phases............................................................................................89
Figure 80 – Configuring Phase Functions .........................................................................................................................91
Figure 81 – Configuring Phase Functions - page 2 ...........................................................................................................92
Figure 82 – Configuring Phase Functions - page 3 ...........................................................................................................92
Figure 83 – Editing Once-Per-Unit Recalls........................................................................................................................93
Figure 84 – Editing Once-Per-Unit Recalls - page 2.........................................................................................................93
Figure 85 – Editing phase times........................................................................................................................................94
Figure 86 – Editing phase times - page 2..........................................................................................................................94
Figure 87 – Go to the Main Menu and choose 6.First Time Setup ....................................................................................97
Figure 88 – Basic Setup Procedure screen.......................................................................................................................97
Figure 89 – Basic Setup Procedure screen - page 2........................................................................................................97
Figure 90 – Press the selection from the Quick Start menu to see topic ...........................................................................98
Figure 91 – Main Menu .....................................................................................................................................................98
Figure 92 – Dynamic Menu ...............................................................................................................................................99
Figure 93 – Change Data Menu........................................................................................................................................99
Figure 94 – Main Menu ................................................................................................................................................... 101
Figure 95 – Change Data Menu...................................................................................................................................... 101
Figure 96 – Controller Menu ........................................................................................................................................... 101
Figure 97 – Sequence/Startup Configuration Screen - page 1 ........................................................................................ 102
Figure 98 – Adding and deleting phases from preset configuration................................................................................. 103
Figure 99 – Adding/deleting co-phases to configuration.................................................................................................. 104
Figure 100 – Phase enable/disable and Ring assignment............................................................................................... 105
Figure 101 – Assigning phases to co-phase groups........................................................................................................ 105
Figure 102 – Exclusive Pedestrian phase programming ................................................................................................. 106
Figure 103 – Rings and Co-phases Example 1............................................................................................................... 109
Figure 103 – Ring, Barrier, and Co-phase Relationship (Sd 8 phase quad left) .............................................................. 110
Figure 104 – Example of Co-phase programming........................................................................................................... 111
Figure 105 – Altering co-phase assignments - example 1............................................................................................... 112
Figure 106 – Changing sequence order - example 1 ...................................................................................................... 112
Figure 107 – Ring assignments - example 2 ................................................................................................................... 113
Figure 108 – Co-phase assignments - example 2 .......................................................................................................... 113
Figure 109 – Ring assignments - example 3 ................................................................................................................. 114
Figure 111 – Ring assignments - example 4 .................................................................................................................. 115
3000 Series Traffic Controllers xiii

Figure 113 – Ring assignment of an exclusive ped phase .............................................................................................117
Figure 114 – Co-phase assignment for an exclusive ped phase ....................................................................................118
Figure 115 – Another co-phase assignment for an XPED phase ...................................................................................118
Figure 116 – Setting up XPED operation .......................................................................................................................118
Figure 117 – Compatibility card jumpers for an XPED phase.........................................................................................120
Figure 118 – Ring and co-phase topography for an XPED as phase 7 ..........................................................................121
Figure 119 – Exclusive ped phase in an intersection......................................................................................................121
Figure 120 – Exclusive ped with overlap programming ..................................................................................................121
Figure 121 – Phase Recalls/Modes Menu......................................................................................................................122
Figure 122 – Timing plan assignable recall modes ........................................................................................................122
Figure 123 – Phase Recalls/Modes Menu - page 2........................................................................................................123
Figure 124 – Timing plan assignable recall modes - page 3..........................................................................................123
Figure 125 – No Skip example .......................................................................................................................................127
Figure 126 – Per Unit Assignable Phase Functions .......................................................................................................128
Figure 127 – Per Unit Assignable Phase Functions - page 2 .........................................................................................128
Figure 128 – Per Unit Assignable Phase Functions - page 3 .........................................................................................128
Figure 129 – Phase timing configuration - page 1 ..........................................................................................................133
Figure 132 – Cars are counted during red.......................................................................................................................139
Figure 133 – Classic Case of Gap Reduction..................................................................................................................141
Figure 134 – Passage Timer during Gap Reduction .......................................................................................................142
Figure 135 – Dual Entry programming screen................................................................................................................143
Figure 136 – Dual Entry by Time Plan screen ................................................................................................................143
Figure 137 – Conditional Service screen........................................................................................................................145
Figure 138 – Conditional Service by Time Plan screen ..................................................................................................146
Figure 139 – Ped Options screen...................................................................................................................................147
Figure 140 – Enhanced Options Menu...........................................................................................................................148
Figure 141 – Dynamic Omits screen ..............................................................................................................................148
Figure 142 – Dynamic Recalls screen............................................................................................................................149
Figure 143 – UCF Setup screen.....................................................................................................................................150
Figure 144 – Density Setup screen ................................................................................................................................151
Figure 145 – Simultaneous Gap Out Setup screen ........................................................................................................152
Figure 146 – Max 3 Options Setup screen .....................................................................................................................153
Figure 147 – Passage Sequential/Red Revert/PE Override screen................................................................................154
Figure 148 – Phase Dimming Setup screen - page 1 .....................................................................................................155
Figure 149 – Phase Dimming Setup screen - page 2 .....................................................................................................155
Figure 150 – Lead/Lag Setup screen .............................................................................................................................156
Figure 151 – Multiple Lead-Lag pairs..............................................................................................................................158
Figure 152 – Soft Flash Setup screen ............................................................................................................................159
Figure 153 – Detector Menu ..........................................................................................................................................164
Figure 154 – Detector Assignments screen (aka ‘Veh. Assignments’) ...........................................................................164
Figure 155 – Pedestrian Detector Assignments screen..................................................................................................165
Figure 156 – Detection Modes screen............................................................................................................................166
Figure 157 – Detector Lock Setup screen ......................................................................................................................168
Figure 158 – Detector Timing Setup screen...................................................................................................................169
Figure 159 – Detector Delay Inhibits screen ..................................................................................................................169
Figure 160 – Detector Switch/Copy Setup screen..........................................................................................................171
Figure 161 – Switch Setting ...........................................................................................................................................172
Figure 162 – Detector Failure Monitoring Menu .............................................................................................................174
Figure 163 – Detector Absence/Erratic Behavior Monitoring ..........................................................................................174
Figure 164 – Locked Call Monitoring Setup screen........................................................................................................175
Figure 165 – ‘Absence of Call’ Monitoring Setup screen ................................................................................................175
Figure 166 – Minimum Presence Monitoring Setup screen ............................................................................................176
Figure 167 – Erratic Counts-Per-Minute Monitoring Setup screen .................................................................................176
Figure 168 – Detector Loop Length screen ....................................................................................................................177
Figure 169 – Failed Max Recall Time screen .................................................................................................................177
Figure 170 – Failed Detector Max Recall Settings .........................................................................................................177
Figure 171 – Pedestrian Detector Diagnostics Setup screen .........................................................................................178
Figure 172 – System Sensor Assignment screen...........................................................................................................179
Figure 173 – Simple Overlap ..........................................................................................................................................182
Figure 174 – Typical multi-ring overlap ...........................................................................................................................183
Figure 175 – Typical Load Switch assignments ..............................................................................................................183
Figure 176 – Overlap Menu ............................................................................................................................................185
Figure 177 – Individual overlap programming screen 1...................................................................................................185
xiv 3000 Series Traffic Controllers

Contents
Figure 178 – Timing diagram of an overlap programmed with a delay ............................................................................ 187
Figure 179 – Individual overlap programming screen 2................................................................................................... 191
Figure 180 – Double Clearing Overlap setup screen....................................................................................................... 193
Figure 181 – Offset Intersection with Double Clearing Overlaps ..................................................................................... 195
Figure 182 – Standard Overlap settings - Example 1...................................................................................................... 195
Figure 183 – Double Clearing Overlap settings - Example 1........................................................................................... 196
Figure 184 – Double Clearing Overlap Used for a Track Clearance................................................................................ 196
Figure 185 – Double Clearing Overlap settings - Example 2........................................................................................... 196
Figure 186 — Setting pedestrian overlap modes ............................................................................................................ 198
Figure 187 — Setting Ped Overlap parent phases .......................................................................................................... 200
Figure 188 — Example of Ped Overlap operation ........................................................................................................... 200
Figure 189 — Using Ped Overlap for Carryover operation .............................................................................................. 201
Figure 190 – Double Clearing Overlap used for Advanced Warning ............................................................................... 203
Figure 191 — Setup a standard overlap ......................................................................................................................... 204
Figure 192 — Setup overlap for double-clearing operation ............................................................................................. 204
Figure 193 — Programming advance-warn logic ............................................................................................................ 205
Figure 194 — Advance warning logic screen .................................................................................................................. 206
Figure 195 — Comparison - Leading and Advance Leading Overlaps............................................................................ 207
Figure 196 – Lead Overlap setup screen - Overlap A ..................................................................................................... 207
Figure 197 – Three types of coordinated progression ..................................................................................................... 212
Figure 198 – Two intersections with the same Local Cycle length .................................................................................. 213
Figure 199 – Local Cycle Reference Point ...................................................................................................................... 214
Figure 200 – Example of Coordinated Intersection Offsets ............................................................................................. 215
Figure 201 – Typical placements of fixed force offs and permissives.............................................................................. 218
Figure 202 — Coordination Menu ................................................................................................................................... 222
Figure 203 — Coord Clear and Load Defaults Menu ...................................................................................................... 223
Figure 204 — Clearing all coord values .......................................................................................................................... 223
Figure 205 — Coord Selection Source screen ................................................................................................................ 224
Figure 206 — Coordination Basic Options screen........................................................................................................... 225
Figure 207 – Relative allocation times for an 8 phase intersection.................................................................................. 226
Figure 208 – Fixed and Floating Force Offs - Full demand on all phases........................................................................ 227
Figure 209 – Fixed and Floating Force Offs – Differing Timing on Gap Outs ..................................................................227
Figure 210 – Operation of Yield Permissives .................................................................................................................. 230
Figure 211 – Single Mode Permissives (when in coordinated phases) ...........................................................................231
Figure 212 – Multiple Mode Permissives (when in Coordinated phases) ........................................................................ 233
Figure 213 — Cycles and offset times screen................................................................................................................. 236
Figure 214 — Setting timing for 4 splits per cycle mode.................................................................................................. 238
Figure 215 — Coordinated phases screen...................................................................................................................... 239
Figure 216 — Coordinated phases screen - 4 splits per cycle mode............................................................................... 239
Figure 217 — Programming phase allocation times - example 1 .................................................................................... 241
Figure 218 — Programming phase allocation times - example 2 .................................................................................... 241
Figure 219 — Coordination plan to TOD circuits screen ................................................................................................. 245
Figure 220 — Enhanced Coordination Options Menu ..................................................................................................... 246
Figure 221 — Coordination enhanced operating modes ................................................................................................. 246
Figure 222 — Coordination enhanced operating modes - page 2 ................................................................................... 246
Figure 223 — Cycle Sync Options screen....................................................................................................................... 252
Figure 224 — Permissives and Force-offs Menu ............................................................................................................ 254
Figure 225 — Selecting a permissives mode .................................................................................................................. 254
Figure 226 — Loading manual permissives times (24 splits/cycle mode)........................................................................256
Figure 227 — Loading manual force-offs for cycle 1 ....................................................................................................... 257
Figure 228 — Adaptive Split control screen .................................................................................................................... 258
Figure 229 — Adaptive Split Control - example 1............................................................................................................ 259
Figure 230 — Adaptive Split Control - example 2............................................................................................................ 259
Figure 231 — Adaptive Split Inhibits screen.................................................................................................................... 260
Figure 232 — Split Matrix setup screen - 4 split per cycle mode ..................................................................................... 261
Figure 233 — Split Matrix setup screen - 24 split mode .................................................................................................. 261
Figure 234 — No Early Release setup screen ................................................................................................................ 262
Figure 235 — Cycle/split to timing plan screen ............................................................................................................... 263
Figure 236 — Cycle/split to timing plan screen - 24 split mode ....................................................................................... 263
Figure 237 — COS to lead/lag screen ............................................................................................................................ 264
Figure 238 — Offset to free setup screen ....................................................................................................................... 264
Figure 239 — Checking the coordination plan ................................................................................................................ 265
Figure 240 — Setting the selection source...................................................................................................................... 269
Figure 241 — Basic operating modes ............................................................................................................................. 270
3000 Series Traffic Controllers xv

Figure 242 — Setting cycle and offset times ...................................................................................................................271
Figure 243 — CNA usage example.................................................................................................................................272
Figure 244 — Phase allocations as percentages ............................................................................................................272
Figure 245 — Phase allocations in seconds ...................................................................................................................273
Figure 246 — Time of Day Menu ....................................................................................................................................276
Figure 247 — Day Plan selection screen ........................................................................................................................278
Figure 248 — Editing a day plan .....................................................................................................................................278
Figure 249 — Typical day plan example - screen 1 ........................................................................................................280
Figure 252 — Configuring circuit plans ...........................................................................................................................282
Figure 253 — Week Plans editing screen .......................................................................................................................283
Figure 254 — Year Plan Editing screen ..........................................................................................................................284
Figure 255 — Exception Day configuration screen .........................................................................................................285
Figure 256 — Circuit Override setup screen ...................................................................................................................286
Figure 257 — Daylight Savings Time setup screen.........................................................................................................287
Figure 258 — Sync Reference Setup screen ..................................................................................................................288
Figure 259 — Set Date and Time screen ........................................................................................................................290
Figure 260 – Preemption Options list ..............................................................................................................................295
Figure 261 – Erase All Preemption Runs verification screen...........................................................................................295
Figure 262 – Preemption Run 1 Menu ............................................................................................................................296
Figure 263 – Per Run Menu for preemption run 1 ...........................................................................................................296
Figure 264 – Per Run Parameters, Screen 1 ..................................................................................................................297
Figure 265 – Per Run Parameters, Screen 2 ..................................................................................................................299
Figure 266 – Per Run Times ...........................................................................................................................................301
Figure 267 – Preemption Entry Parameters screen ........................................................................................................303
Figure 268 – Per Run/Per Interval Parameters screen 1.................................................................................................305
Figure 269 – Per Run/Per Interval Parameters screen 2.................................................................................................305
Figure 270 – Per Run Exit Parameters screen ................................................................................................................306
Figure 271 – Preemption Interval Data screen 1 .............................................................................................................308
Figure 274 – Example of Preemption Interval Data screen 1 ..........................................................................................312
Figure 275 – Preemption Interval Data screen 2 - details................................................................................................313
Figure 276 – Preemption Interval Data screen 3 - details................................................................................................314
Figure 277 – Per Run Options screen 1 ..........................................................................................................................317
Figure 278 – Per Run Options - Enabling Coordination...................................................................................................317
Figure 279 – Preemption Flash Plan pogramming screen...............................................................................................323
Figure 280 – Open the Preemption menu for a particular run..........................................................................................324
Figure 281 – Quick Setup Options screen.......................................................................................................................325
Figure 282 – Fire Run Setup screen ...............................................................................................................................325
Figure 283 – Fire Run Interval screen.............................................................................................................................328
Figure 284 – Railroad Run Interval screen......................................................................................................................329
Figure 285 – Railroad Run Interval screen - second interval ...........................................................................................330
Figure 286 – Railroad Run Interval screen - third interval ...............................................................................................330
Figure 287 – R1 Cyclic Group A Time screen .................................................................................................................331
Figure 288 – A keyboard-entered call for preemption run 1 ............................................................................................332
Figure 289 – Preemption Status screen showing keyboard call on run 1 ........................................................................332
Figure 290 – Example preemption with typical fire runs ..................................................................................................333
Figure 291 – Preemption Example 1 - Disabling run .......................................................................................................333
Figure 292 –Preemption Example 1 - Setting duration timer ...........................................................................................334
Figure 293 –Preemption Example 1 - Setting entry times ...............................................................................................334
Figure 294 –Preemption Example 1 - Setting exit controls..............................................................................................335
Figure 295 –Preemption Example 1 - Setting interval data .............................................................................................335
Figure 296 – Preemption Example 2 - Fire runs and railroad crossing ............................................................................336
Figure 297 –Preemption Example 2 - Setting run parameters.........................................................................................337
Figure 298 –Preemption Example 2 - Setting run times ..................................................................................................338
Figure 299 –Preemption Example 2 - Setting entry times ...............................................................................................338
Figure 300 –Preemption Example 2 - Setting exit controls..............................................................................................339
Figure 301 –Preemption Example 2 - Interval 1 phase colors .........................................................................................339
Figure 302 –Preemption Example 2 - Interval 1 overlap colors .......................................................................................340
Figure 304 –Preemption Example 2 - Interval 2 overlap colors .......................................................................................340
xvi 3000 Series Traffic Controllers

Contents
Figure 307 –Preemption Example 2 - Interval 4 phase colors ......................................................................................... 342

Figure 310 –Preemption Example 3 - Interval 4 overlap colors ....................................................................................... 343
Figure 311 – Preemption Example 3 - Programming the Flash plan ............................................................................... 344
Figure 312 – Comm/System Setup menu (TS 1)............................................................................................................. 346
Figure 313 – Comm/System Setup menu (TS 2)............................................................................................................. 346
Figure 314 – Closed Loop Master/ID Setup screen......................................................................................................... 347
Figure 315 – Comm Port 2 Setup screen ........................................................................................................................ 349
Figure 316 – Comm Port 3 Setup screen with Hardware set to “Ethernet” ...................................................................... 351
Figure 317 – Setup Modem String screen....................................................................................................................... 352
Figure 318 – Ethernet Setup screen ............................................................................................................................... 353
Figure 319 – Ethernet Setup screen showing DHCP retrieval error ................................................................................ 353
Figure 320 – Modem attached to a 3000 series controller............................................................................................... 354
Figure 321 – Phone Numbers setup screen.................................................................................................................... 361
Figure 322 – Event Call-in triggers - screen 1 ................................................................................................................. 362
Figure 323 – Event Call-in triggers - screen 2 ................................................................................................................. 362
Figure 324 – Log Data Settings - page 1 ........................................................................................................................ 364
Figure 325 – Log Data Settings - page 2 ........................................................................................................................ 364
Figure 326 – Measuring the distance between speed trap detectors .............................................................................. 364
Figure 327 – Log Data Settings - page 3 (Event Log Enable settings) ............................................................................ 365
Figure 328 – Port 1 Setup - screen 1 (BIU Enables) ....................................................................................................... 366
Figure 329 – Port 1 Setup - screen 2 (MMU Secondary Enables)................................................................................... 367
Figure 330 – Port 1 Setup - screen 3 (MMU Channel Assignments) ............................................................................... 368
Figure 334 – Port 1 Setup - screen 7 (Secondary-to-Secondary Addresses) .................................................................. 369
Figure 335 – System Name screen................................................................................................................................. 370
Figure 336 – Contact Name screen ................................................................................................................................ 371
Figure 337 – HDLC Address screen ............................................................................................................................... 372
Figure 338 – Unit Configuration Menu ............................................................................................................................ 374
Figure 339 – Security Codes screen ............................................................................................................................... 375
Figure 340 – Intersection Name screen .......................................................................................................................... 378
Figure 341 – EEPROM/Audio Adjust screen................................................................................................................... 379
Figure 342 – 3000E Series device’s screen when in Firmware Update Mode................................................................. 382
Figure 343 – First connect the PC to the 3000E device via a serial cable ....................................................................... 383
Figure 344 – Locations of Flash/EPROM chips and jumper links .................................................................................... 384
Figure 345 – Proper jumper settings on the 3000E motherboard for Flash/EPROM operation ....................................... 385
Figure 346 – Power-on Self Test Error Message ............................................................................................................ 387
Figure 347 – Power-on Self Test Error Message ............................................................................................................ 389
Figure 348 – I/O Steering setup screen - page 1............................................................................................................. 392
Figure 351 – I/O Steering - Example 1............................................................................................................................ 394
Figure 352 – I/O Steering - Example 2............................................................................................................................ 394
Figure 353 – Typical Connections to a TS 2 Type 1 controller ........................................................................................ 397
Figure 354 – Simple TS 2 Type 1 configuration .............................................................................................................. 398
Figure 356 – Peek’s BIU Card ........................................................................................................................................ 399
Figure 357 – I/O Mapping Menu (before activation) ........................................................................................................ 405
Figure 358 – I/O Mapping Menu (with mapping active) ................................................................................................... 405
Figure 359 – Warning message when Activating the User Map ...................................................................................... 406
Figure 360 – Status screen showing that the mapping has been activated ..................................................................... 406
Figure 361 – I/O Mapping Menu with the user's map activated ....................................................................................... 407
Figure 362 – Warning message when clearing the Input Map......................................................................................... 407
Figure 363 – Verification of the cleared BIU mapping ..................................................................................................... 408
Figure 364 – Input mappings .......................................................................................................................................... 408
Figure 365 – Output mapping assignments..................................................................................................................... 410
Figure 366 – Warning message when loading the default NEMA mapping .....................................................................411
Figure 367 – Verification of a successful load of NEMA defaults..................................................................................... 411
Figure 368 – Warning message when copying MMU channels....................................................................................... 411
Figure 369 – Verification of successful copy of MMU channels to output mappings........................................................ 412
Figure 370 – Warning message when EEPROM mapping data is missing or corrupted ................................................. 412
Figure 371 – Utilities Menu ............................................................................................................................................. 418
3000 Series Traffic Controllers xvii

Figure 372 – Default Data Load Menu ............................................................................................................................419
Figure 373 – Transfer Menu............................................................................................................................................420
Figure 374 – Clear Logs screen ......................................................................................................................................420
Figure 375 – EEPROM-RAM Copy screen .....................................................................................................................421
Figure 376 – EEPROM-RAM Copy screen .....................................................................................................................422
Figure 377 – Printer Menu ..............................................................................................................................................423
Figure 378 – Printing portions of database or logs ..........................................................................................................424
Figure 379 – Print-out status display...............................................................................................................................424
Figure 380 – Copy Functions Menu ................................................................................................................................425
Figure 381 – Controller Copy screen ..............................................................................................................................425
Figure 382 – Coordination Copy screen..........................................................................................................................426
Figure 383 – Time of Day Copy screen...........................................................................................................................426
Figure 384 – Preemption Copy screen............................................................................................................................427
Figure 385 – Field Requested Download screen.............................................................................................................428
Figure 386 – BIU I/O Mapping Menu (v2.0).....................................................................................................................428
Figure 387 – Setting passage time..................................................................................................................................463
xviii 3000 Series Traffic Controllers

Contents
Tables
Table 1 – Documents related to the 3000 Series Traffic Controllers....................................................................................2

Table 2 – Typographic conventions used in this manual .....................................................................................................3
Table 3 – Keyboard conventions used in this manual..........................................................................................................3
Table 4 – Symbol conventions used in this manual .............................................................................................................4
Table 5 – History of the 3000 Series controllers ..................................................................................................................6
Table 6 – Communications/Optional Modules available for 3000 Series units...................................................................25
Table 7 – Phase/Overlap Indicators (in increasing order of priority) ..................................................................................32
Table 8 – Vehicle Demand codes, in order of priority ........................................................................................................33
Table 9 – Pedestrian Demand codes ................................................................................................................................34
Table 10 – Error/Failure Status Indicators .........................................................................................................................35
Table 11 – Vehicle and pedestrian demand codes ............................................................................................................36
Table 12 – Interval Abbreviations ......................................................................................................................................37
Table 13 – Max and Termination Abbreviations ................................................................................................................37
Table 14 – Normal I/O screen key .....................................................................................................................................40
Table 15 – Density Status screen key ...............................................................................................................................41
Table 16 – Outputs Status screen key...............................................................................................................................43
Table 17 – Output Status Bit definitions ............................................................................................................................44
Table 18 – Input Status screen key ...................................................................................................................................46
Table 19 – Possible Detector ‘Route’ settings ...................................................................................................................48
Table 20 – I/O Module Configuration Status screen key...................................................................................................51
Table 21 – Coordination Status screen key .......................................................................................................................56
Table 22 – TOD Dynamic Circuits Status codes................................................................................................................58
Table 22 – Key to the Preemption Status screens.............................................................................................................60
Table 23 – Key to the Voltage screen................................................................................................................................63
Table 24 – Key to the MOE Log screens...........................................................................................................................67
Table 25 – Codes that appear on the Mizbat Dynamic Status screen ...............................................................................76
Table 26 – Modem Status Messages ................................................................................................................................77
Table 27 – Minimal Requirements For A New Controller ...................................................................................................85
Table 28 – Possible Additional (But Commonly Used) Requirements ...............................................................................85
Table 29 – Typical Use Of Recall Modes ..........................................................................................................................90
Table 30 – Max Variable Initial settings ........................................................................................................................... 140
Table 31 – Lead/Lag Phasing Modes .............................................................................................................................. 156
Table 32 – Lead/Lag Activation Inputs ............................................................................................................................ 157
Table 33 – Soft Flash Modes........................................................................................................................................... 159
Table 34 – Detector configuration for Third Car Detection............................................................................................... 180
Table 35 – Type of Overlap ............................................................................................................................................. 188
Table 36 – Flash Codes .................................................................................................................................................. 189
Table 37 – Pins Used for Common TS 2 Modes ............................................................................................................. 203
Table 38 – Coordination Source Codes........................................................................................................................... 224
Table 39 – Splits under 4 splits/cycle and 24 split plans.................................................................................................. 248
Table 40 – Interval Timing Effects ................................................................................................................................... 311
Table 41 – Preemption Intervals...................................................................................................................................... 321
Table 42 – Column Codes in a Flash Plan ...................................................................................................................... 323
Table 43 – Proper ‘Hardware’ settings for various Port 2 and Port 3 devices .................................................................. 349
Table 44 – Special characters for phone numbers .......................................................................................................... 361
Table 45 – Event type codes ........................................................................................................................................... 363
Table 46 – Log Enable Codes ......................................................................................................................................... 365
Table 47 – Checksums for various 3000 series firmware (8216 series)........................................................................... 381
Table 48 – Output Steering source codes ....................................................................................................................... 393
Table 49 – I/O Mapping Codes for BIUs 1 and 2 ............................................................................................................. 400
Table 50 – I/O Mapping Codes for BIUs 3 and 4 ............................................................................................................. 402
Table 51 – I/O Mapping Codes for BIUs 9 and 10 ........................................................................................................... 403
Table 52 – I/O Mapping Codes for BIUs 11 and 12 ......................................................................................................... 403
3000 Series Traffic Controllers xix

Table 53 – Logical I/O Mapping operators.......................................................................................................................409
Table 54 – Input Mapping Abbreviations .........................................................................................................................413
Table 55 – Output Mapping Abbreviations.......................................................................................................................414
Table 56 – Input and Output Availability of BIU Pins .......................................................................................................415
Table 57 – TOD circuit assignments................................................................................................................................430
xx 3000 Series Traffic Controllers

Preface — About This Manual
PURPOSE AND SCOPE

This manual introduces and discusses the 3000 and 3000E Traffic Controllers from
Peek Traffic. It covers how to operate, configure, and test these units, describing the
hardware and firmware environment used to control them. Although these controllers
can be controlled and data remotely gathered using central software systems such as
CLMATS and IQ Central, this manual does not discuss CLMATS or IQ Cenral in any
detail.
ASSUMPTIONS
It is assumed that the reader and user of this manual and the hardware described
herein are authorized to work in and around traffic cabinets by the local traffic
governing body. The reader should be familiar with the operation and wiring of traffic
control cabinets in their area, and must be aware of, and follow, all safety and security
protocols of the traffic agency. It’s also assumed that the operator of the 3000 or
3000E traffic controller knows what signal standard is being used inside the cabinet
(NEMA TS 1, TS 2, NTCIP, etc.)
3000 Series Traffic Controllers 1

RELATED DOCUMENTS
These documents provide additional information that may be useful when working
with a 3000 Series Traffic Controller:
Table 1 – Documents related to the 3000 Series Traffic Controllers
Document Part Number
3000 Series Operating Manual 8204C
3000 Series TS1 Firmware (8216B) Release Notes 99-331
3000 Series TS2 Firmware (8216A) Release Notes 99-332
3000 Series Protocol-90 Firmware (8216F) Release Notes 99-371
CLMATS Installation Manual 81-858
CLMATS Operating Manual 81-883
CLMATS Release Notes 99-275
CLMATS Preemption Management Module Release Notes 99-365
Double Diamond MMU Operating Manual 8314B
M3000 Operating Manual 5928
M3000 Firmware Release Notes 99-329
TECHNICAL ASSISTANCE
If you need assistance or have questions related to the use of this product, call Peek
Traffic’s Technical Support Group using the information listed below.
Peek Traffic — Technical Support

2906 Corporate Way
Palmetto, FL 34221
toll free in the U.S.: 1 (800) 245-7660
tel: 1 (941) 845-1200
fax: 1 (941) 845-1504
email: tech.support@peektraffic.com
Additional information is also available at the Peek Traffic website:
www.peektraffic.com
2 3000 Series Traffic Controllers

Conventions Used in this Manual
CONVENTIONS USED IN THIS MANUAL

When referring to any of the product manuals from Peek Traffic, the following
typographical conventions will aid in understanding the intent of the various topics
and procedures.
Typographic Conventions
As shown in the following table, whenever text appears in the following fonts and
styles, it indicates a special situation or meaning for the user.
Table 2 – Typographic conventions used in this manual
Description Example
Commands or controls that must be In the Print dialog box, select Options.
selected by the user appear in bold.
Switches or keyboard keys appear in When finished selecting parameters, press the
SMALL CAPS. PAGEDOWN key.
Things that the user needs to type at a Type a:\setup.exe at the prompt.
prompt or entry window exactly as
shown appear in this font.
Items italicized inside slanted brackets Type c:\<install_directory>
< > are variables that need to be \product and press ENTER.
replaced while typing a command. The
slanted brackets should not be typed.
Keyboard and Menu Conventions

Some commands are accomplished with a pair or sequence of keystrokes or
command entries. The way these should be done is indicated by the way they are
shown in the instructions, as listed here.
Table 3 – Keyboard conventions used in this manual
Description Example
A series of commands that need to be Go to Start > Programs > CLMATS and
completed in sequence will be separated by select Configuration.
a right slant bracket (>)
A dash, or hyphen, ( - ) indicates keys or Press CTRL-p to print the file.
controls that need to be pressed at the
same time to activate the command
A comma ( , ) indicates keystrokes that To print the file, press ALT-f, p.
need to be pressed one after the other.

Symbol Conventions
The following symbols are used in this manual to indicate special messages for the
user. Each indicates the level of importance that should be assigned to the
associated text.
Table 4 – Symbol conventions used in this manual
Symbol Description
Note — This icon accompanies a general note or tip about the current
topic.
Caution — This icon represents a general hazard. If the operator is
not paying attention, some action that is undesired may occur.
Warning — This icon represents a situation where some real risk
exists, whether of electrical shock or some other form of personal or
property damage. Be very careful when dealing with Warning
situations.

Chapter 1 — Introduction to the 3000 Series
This chapter introduces the product and explains the layout of this manual, along with
type conventions and other topic. The following topics are discussed in detail in this
chapter:
• Overview of the 3000 Series, on page 6.
• Introduction to the hardware, on page 8.
• The purpose of the keypad keys, on page 13.
• A rundown of the features of 3000 Series controllers, on page 19.
• Configuration options, on page 24.

OVERVIEW
The 3000 Series of traffic controllers from Peek Traffic Corporation provide
intersection control for NEMA TS 1, NEMA TS 2, 170, or NTCIP cabinets. They can
be programmed to run in either timed or free operation, and can be set up to function
in independent intersections or coordinated intersection ‘corridors.’ The controllers in
this family can be programmed locally using a keypad and display, or remotely via a
central software suite, such as Peek’s CLMATS or IQ Central systems.
These controllers can handle sensor and pedestrian calls, preemption calls, time of
day/week/month/year programming, and coordinated operation, as well as a variety of
other programmable options.
Evolution of the 3000 Series Controller

The 3000 Series controller has evolved over the past ten years. The following timeline
lists the most significant events in the history of the product line. At any given time
during this period, there was always just one 3000 series product and one official
firmware version, but with several hardware options available as add-ons.
Table 5 – History of the 3000 Series controllers
Year Event
1995 The 3000 controller was introduced by Peek Traffic Corporation.
1995-2000 Several D-Module hardware add-on modules were released for the 3000
controller. Firmware was updated several times until it reached version
3.0.
2000 The 3000E controller was released. This significant hardware update
changed the appearance of the front panel keypads, and consolidated the
front panel circuit boards to improve the ease of accessing the inside of
the unit and of performing hardware upgrades (ports, D-modules, firmware
EPROMs, etc.)
2002 Firmware v3.1.1 released. Minor improvements to Preemption operation,
preemption checking, and double clearing overlaps. Release of an
updated 3000 series operating manual.
2003 Release of Firmware v3.1.2. Minor improvements in preemption, side-
street servicing, and coordination with central software.
Release of Firmware v3.3. Improvements in lead-lag operation and
coordination with central software. Matched updates in the capabilities of
the CLMATS software package.
2004 Release of Firmware v3.4. Added the capability to update firmware to
flash memory on units that are marked ‘Flash Memory Enabled.’ Added
the boot block startup routine for administering firmware loads and low-
level hardware function changes. Added capability to Inhibit Ped
Overrides. This update fixed numerous minor issues and improved the
operation of permissives, preemption, overlaps, coordination and flash
operation. Also improved CVM (Controller volt monitoring) and CRC check
operations.
An optional Ethernet card that can be installed as Port 3 of the 3000E
controller was released.

Overview
Year Event
Firmware version 3.6 was released, which added dramatic new capabilities
to the controller. Full support for the new Flash Memory Enabled 3000E
controllers. Supports full TS 2 Type 1 operation with BIU Input/Output
mapping. Improved COMMS setup screens and general improvements to
communications reliability. Addition of NTCIP communications parameters.
Addition of one new Ped Overlap mode (mode 3) and two new vehicular
overlap modes (modes 7 and 8.)
Quixote Corporation of Chicago, IL purchased Peek Traffic Corporation.
After the purchase Peek Traffic and U.S. Traffic were combined to become
Quixote Traffic Corporation.
2005 The release of PC and Pocket PC based utilities that can be used to
update the flash firmware in a 3000E controller.
The release of firmware v3.6.2, which dramatically improved the reliability
of overlaps and preemption, and improved support for Ethernet operation.
2007 An Ethernet card option was added for the 3000E controller
2008 IQ Connect support for 3000E added, making the controllers compatible
with the NTCIP standard and with the IQ Central software.
Signal Group, Inc. of Houston, TX purchases the companies of Quixote
Traffic and renames them Peek Traffic Corporation.
Checking the Firmware Version

The most important fact determining how your controller operates and can be programmed
is the version of firmware that is installed within the unit. Since much work has been done
to improve the 3000 series controllers over the past several years, it may be a good idea
to update the firmware in your controllers. However, it is unwise to update firmware if you
have well seasoned controllers operating in the field which have no problems. The Peek
Traffic support team recommends that a firmware update should only be performed in
order to fix a bug that is severely interfering with the operation of the controller, or to add a
new feature that is highly needed for your application. Otherwise, it’s best to leave the
controller’s firmware alone.
Before determining whether or not your controller(s) should have new firmware installed,
you should check to see what firmware is currently installed in the hardware, as described
in the following procedure. This procedure can be used to safely determine what firmware
is installed in a 3000 series unit, even as the device is actively controlling an intersection.
1. With the unit powered up and running, press the MENU button until the Main Menu
appears.
2. Press the keypad number 1 to open the Dynamic Menu.
3. Press the number 7 * to open the Program Level and Rev screen. Write down the
current version of firmware that is installed in the unit.
4. Pressing SHIFT -ENTER returns the controller to the main status screen.
For instructions on how to update the firmware in the controller, see “Updating the
Controller Firmware” on page 380.
*
On some older controllers and firmware, the Program Level and Rev command is option 6.

HARDWARE IN THE 3000 SERIES

There are several variants of the 3000 Series controllers, which can be identified both
by their hardware configuration and through the firmware they run. The next section
shows the most common appearance for each major type of controller in the 3000
Series, but to verify which type of unit is involved, the most direct method is to check
the version of the firmware being run in the unit.
Version 3000 Traffic Controller Hardware

The 3000 version of the Peek Traffic controller is the older variant of the series,
although it performs nearly all of the same functions of the newer 3000E unit.
Historically, the largest majority of 3000 controllers have been supplied in a NEMA TS
1 format, as shown here. In addition, they introduced the “D Module”, where an
optional Peek proprietary connector or set of connectors could be installed.
Display Keypad
Power LED
Fuses
Comm
Connectors
Cabinet
Connectors
Figure 1 – 3000 Controller D Module
The comm connectors, cabinet connectors, and D Module connectors included with
any 3000 controller will vary based on the requirements of each municipality, state, or
province.
Note 3000 controllers can have the same variety of cabinet connector ports (A, B, C,
and D) as 3000E controllers, however the most commonly shipped version of the
basic 3000 controller is shown in Figure 1, namely the 3000 TS 1 (16 Phase)
controller.

Hardware in the 3000 Series
Version 3000E Traffic Controller Hardware

The 3000E version of the Peek Traffic controller comes in two primary layouts:
Display Keypad
Comm
Connectors
Power LED
Fuses
Cabinet Connectors
D Module
Figure 2 – 3000E Controller, typical TS 1 and TS 2 Type 2 configuration
Display Keypad
Cabinet Comm
Connector Connectors
Power LED
Fuses
TS2-Type1
units rarely
Figure 3 – 3000E Controller, typical TS 2 Type 1 configuration have a D
Module

The 3000E is the newer of the 3000 series controllers. As with the 3000, the 3000E
has the “D Module” available, where a proprietary Peek connector or set of
connectors may be installed.
As can be seen in the two figures, the TS 1 (and TS 2 Type 2) version of the 3000E
has three cabinet connector ports: A, B, and C. The TS 2 Type 1 version, on the other
hand, has a single Port A cabinet connector.
Note TS 1 controllers have hardwired pins in the A, B, and C connectors to physically

connect to the various cabinet signals. Refer to page 438 for pin assignments for
these three ports.
TS 2 controllers, on the other hand, communicate with the cabinet using
communications protocols rather than direct connections of electrical signals. A
Type 1 controller uses its single A connector primarily for power outputs and status
signals; most cabinet information is passed to and from the controller over Port 1,
the RS-485 connector. These communications are then routed through BIU units
in the cabinet to communicate the cabinet signals to the controller. TS 2 Type 2
controllers use the same communications protocols, but they route the comm
signals through the typical A, B, and C ports. Refer to page 443 for these pin
assignments.
As in the 3000 units, the comm connectors, cabinet connectors, and D Module
connectors included with any 3000E controller will vary based on the requirements of
each municipality and state or province.
Flash Memory Enabled 3000E Controllers

The 3000E controller line now includes a flash memory option. Previously, the
memory used to store firmware, programming and data in the controller was EPROM
memory. But flash memory has now been included as an option. Unlike EPROMS,
flash memory can be used to update the firmware in the controller without the
necessity of removing the memory chips.
All variants of the 3000E Traffic Controller are now available in a flash-memory
enabled version. Figure 4 shows the TS 2 Type 2 version.

Figure 4 – Flash-enabled 3000E Controller (TS 2 Type 2 version)

The updated controllers are identifiable by the ‘Flash Memory Enabled’ logo on the
front panel. Flash Memory Enabled 3000E controllers are shipped with Flash
memory installed, however they can be switched back to use the older EPROM
memory chips. This modification requires only the repositioning of five jumpers on the
controller’s motherboard. (For details, see page 384.)
Figure 5 – ‘Flash Memory Enabled’ logo

The directions to change a flash-enabled controller from flash to EPROM operation,
and the directions to load updated firmware in a flash-enabled controller using a
laptop or a Pocket PC device, are available in Chapter 11:Unit Configuration and
Security on page 380.

User Interface
The configuration and operation of a 3000 Series controller is managed using the
onboard keypad and display, or it can be managed remotely using a software
package like CLMATS. The onboard interface is composed of these three
components:
An 8 x 40 character LCD Display provides status feedback and configuration
options to the operator.
A 24-key keypad is used to navigate the firmware screens. This allows an
operator to view status or configure the operation of the controller. (See page
14.)
The 3000 Series firmware defines what appears on the display screen and
how the keypad is used to navigate between the various status and
configuration screens. The top level menu is called the MAIN MENU. The
firmware also handles the internal operation of the controller, defining how
inputs and outputs are processed, and basically controlling all functions of the
unit.
Note This manual does not discuss any specific version of 3000 firmware, since there
are a large variety of versions available, covering the various controller standards
(TS 1, 170, NTCIP, etc.) and local requirements.
It does, however, primarily deal with firmware that has been released in year 2004
or later (generally version 3.4.0 or higher.) For details about the specific firmware
loaded on your controller, refer to the firmware release notes that were supplied
with the unit. If you do not have the release notes for your version of firmware,
contact your Peek Technical Support Representative (page 2 of this manual) to
request a copy.

Display
The front panel display of a 3000 Series controller is an 8 row by 40 column ‘super-
twist’ LCD screen with graphics capability. The LCD includes an electro-luminescent
backlight for night or low light viewing. The backlight is automatically activated by any
keypress. If no keys are pressed for 5 minutes, it automatically turns off.
Throughout this manual, we constantly refer to these screens. Rather than using
difficult-to-see images of the screen itself, text representations of the screens have
been used instead, as shown here.
11:17:38 COMM: Off-Line 1 1 1 -O/L-
PH/OL 1 2 3 4 5 6 7 8 9 0 1 2 A B C D
INDIC r G r r r G r r - - - - R R R R
V DEMAND 0.H.0 0.0.H.0.0 - - - - |Cyc 1
P DEMAND 0 0 0 0 0 0 0 0 - - - - | 76%
EXTEND |EXTEND | Ofs1
MX1 30 PSG 1 |MX1 30 PSG 4 | 0%
TP 1, COORD, Time of Day |Spl 1
Figure 6 – Sample representation of a 3000 Series screen

Keypad
Manual data entry is accomplished with a 24 key silicone rubber tactile feedback
keypad. The 3000 and 3000E both have the same keys, but they are laid out
differently on the two devices. A 3000 controller has a vertical keypad, while the
3000E has a horizontal layout.
Figure 7 – 3000E Keypad

Audible feedback is also provided with a keypress
tone, which can be adjusted for duration. Erroneous
entries are signaled with a special tone (3 rapid beeps)
regardless of the audible feedback volume. A list of
the keys and their associated functions is given below:
1-9 The number keys are used to enter numerical
data such as timing values and modes of operation.
They are also used to select numbered menus, where
pressing the corresponding number selects that menu.
To select menus 10 - 19, press the SHIFT key and a
number 0 - 9, where SHIFT -0 = 10, SHIFT -1 = 11, etc.
0 (Y/N) The 0 key is used to enter numerical data, but
also toggles yes/no data entry fields.
ENTER This key is used to load previously entered
data into memory. SHIFT plus ENTER displays the
main controller dynamic screen regardless of which
screen is currently displayed.
CLEAR Used to clear previously entered data and
prevent it from being stored in memory in case a
mistake was made during data entry.
HOME This key returns the cursor to the beginning
(left end) of the line. When used together with the
SHIFT key, it moves the cursor to the first data entry
field on the current page. Figure 8 – 3000 Keypad

END The opposite of HOME , END moves the cursor to the right end of a line, and
when used in conjunction with the SHIFT key, it moves the cursor to the last data entry
field on the screen.
PGUP In a multi-page data entry screen, this key displays the page immediately
prior to the currently displayed page, if one exists. If the current page is the first
page, the controller will display a message to this effect.
PGDN Displays the next page in a multi-page data entry screen, if there is one. If
the current page is the last page, the controller will display a last page message.
ÏÐÍÎ The cursor control keys move the cursor up, down, left and right,
respectively. The cursor position determines which field will be edited. In general,
the cursor must first be moved to a field in order to change its data. In some screens,
SHIFT plus the Í or Î Key will display more data entry fields that are logically to the
right or left of the current page. For most data screens, pressing any cursor key will
load data that has been keyed into a data field (as if the ENTER key was pressed.)
MENU The Menu Key returns to the previous menu, i.e., the one from which the
current screen was entered. As an example, starting at the Main Menu pressing 3 will
cause the CHANGE DATA menu to be displayed. Pressing the MENU key will then
return to MAIN MENU. By pressing the SHIFT and MENU keys simultaneously, the
user can return to the MAIN MENU from any menu, data entry screen or dynamic
display.
SHIFT This key performs no function on its own, rather it modifies the function of
another key that is pressed together with it.
DISP ADJ (DIS ADJ on the 3000E) This key adjusts the contrast of the liquid crystal
display to improve the readability of the display. Successively pressing the DISP ADJ
key by itself darkens the display through the eight available settings and then back to
the lightest setting. Pressing SHIFT - DISP ADJ lightens the screen.
HELP This key, when pressed, activates the controller's help system to display one
or more pages of help related to the screen that is currently being programmed
(context sensitive). If the help description is more than one page, use the PGDN and
PGUP keys to maneuver through pages. Press HELP again to return to the original
data screen or menu.

Using the Keypad

USE ARROW KEYS TO MOVE THE CURSOR TO THE FIELD containing the
value to be edited.
ENTER THE NEW DATA. As you enter data, the field will change to ‘reverse
video’ (white text on a black background) to indicate that a change has been
made. At this point, the data is stored in a temporary buffer and has not been
loaded into the database yet.
IF AN ENTRY MISTAKE IS MADE, press the CLEAR key to restore the original
value.
TO PERMANENTLY STORE THE DATA, press ENTER or any key that will
move the CURSOR such as HOME, END, or any ARROW key. Pressing
MENU, PGUP, or PGDN causes the controller to beep 3 times to indicate that
the data load is incomplete. Once the data is loaded (stored in memory), the
display will return to normal (no reverse video) and the original data will be lost.
CURSOR MOVEMENT AND THE TYPEMATIC MODE. The 3000 Series
Controller implements a ‘typematic’ keyboard mode. To use this feature, hold a
key down (for example, a cursor key) and after a short delay, the key will be
reentered over and over as if it had been pressed several times. This makes it
easier to move the cursor through a large number of data entry fields. All keys
except the SHIFT key behave this way, and it is especially useful when using
the cursor keys.
FOR REPETITIVE DATA ENTRY OF THE SAME VALUE, there is an
automatic entry mode. To use this feature, load a value, then press and hold
the ENTER key while pressing an arrow key to move to a new field. As the
cursor moves to each new field it repeats the last value programmed. For
example, to change the initial time for phases 1 through 8 to 6 seconds:
ENTER THE INITIAL VALUE (6) for phase 1 in the normal fashion, but
hold down the ENTER key.
NOW PRESS THE Î KEY (Enter still pressed). The Î key can be
toggled or held down. The initial value that was entered for phase 1 (6
seconds) is copied to each phase in turn as the cursor moves to the right.
When the data has been entered for all 8 phases, release both keys and
press ENTER or any cursor key once to load the last value into memory.
To Quickly Return to the Main Menu

Hit SHIFT-MENU (both keys simultaneously)
To Quickly Return to the Top Dynamic Screen

Hit SHIFT-ENTER (both keys simultaneously)

To Review the First Time Setup Menu

For a complete description of the First Time Setup screens, refer to page 97.
For many enable functions, instead of moving the cursor to each column and
enabling, simply move to the row then type in the Phase numbers (or O/L’s, etc.). For
example, to enter Max Recall for phases 1-4, go to Main Menu-3-1-2-1, then cursor to
Max Recall row and type 1, 2, 3, 4.
To Implement Security
To implement security codes, go to Main Menu-3-6-1.
To restrict access to menus, go to Main Menu-3-6-2 for instructions. Security codes
are required for this capability.
To add or delete menus as desired, go to Main Menu-3-6-3 for instructions.
To Adjust the Volume of the Keypad Beep

To adjust the keyboard beeper volume, go to Main Menu-3-6-5. A value of 0 = Off, 10
is loudest.
Communication Ports
There are, at most, three Comm ports on a 3000 series controller. Port 1 is always an
RS-485 high speed serial port. Port 1 is used by TS 2 controllers for communications
with an MMU, or to BIUs in TS 2 Type 1 operation. Port 2 is typically an EIA-232
asynchronous port (formerly known as an RS-232 port) which is used to connect to
an external modem, to a PC or laptop, to an MMU for log retrieval, or to a serial
printer. Port 3 can be configured with one of several communications options. It can
be either an DSP modem which drives local twisted pair telephone wires, a fiber optic
modem, a second EIA-232 serial port, or a Serial/Ethernet combination port,
depending on the hardware module installed in this location.
PORT 1 PORT 2 PORT 3
T
MASTER
R
T
REPEATER
R
RS-485 RS-232 COMM
Figure 9 – Ports with DSP modem installed as Port 3

Figure 10 – Ports with second serial port installed as Port 3

T
MASTER
R
T
REPEATER
R
RS-485 RS-232 COMM
Figure 11 – Ports with fiber optic modem installed as Port 3

T
MASTER
R
T
REPEATER
R
RS-485 RS-232 COMM
Figure 12 – Ports with serial/Ethernet card installed as Port 3

Increasingly, there is no “typical” communications setup. But some configurations are
more common than others. On a TS 1 controller, Port 1 is not used, Port 2 is usually
used to connect with a conflict monitor, and port 3 is usually used to connect with a
master. If there is no master, then port 3 is usually used as a modem or direct serial
connection to a central software system (such as CLMATS.)
On a TS 2 controller (both Type 1 and Type 2), Port 1 is defined in the TS 2 standard
to function as the main path for data flowing back and forth between the cabinet and
the controller, particularly to the MMU and to the BIUs. Port 2 might be used to
connect to the MMU for log retrieval, and Port 3 is often used to connect to a master
controller. If the controller is operating without a master, and no MMU logs are being
retrieved across by central, then either Port 2 or 3 may be used to connect the
controller to the central software system.

Other Features of the 3000 Series Hardware

A 3000 Series Traffic Signal Controller is a state-of-the-art controller that is designed
to handle the needs of the traffic industry. For ease of transition, the 3000 and 3000E
are backward compatible with the Transyt Model 1880EL, TCT LMD series, and all
NEMA controllers (containing connectors MSA, B and C.)
Keyboard & Displays

Ease of programming is a major priority in the 3000, which includes a large 8 row by
40 column LCD and a 24 key keypad with tactile and audible feedback. Help screens
are included to guide the user through data entry. Also a SHIFT key is provided to
modify the operation of the other keys.
Clock
Every 3000 Controller includes a 99 year battery-backed real-time clock to provide
complete time keeping functions, including daylight savings time adjustment and leap
year corrections. The clock is fully Y2K compliant.
EEPROM Memory
Database portability is provided by the EEPROM module that contains 32 Kbytes of
EEPROM. If so programmed, data in the EEPROM is automatically updated when
the main database is changed. Also, checksum calculations are performed on both
the EEPROM and main memory to insure that no corrupt data is used. If a checksum
failure occurs, the intersection is put into flash until the error is cleared manually.
Note Peek Traffic Tech Support recommends that the EEPROM Memory feature not
be used on a regular basis. After the upload of a tested database, the EEPROM
Memory backup should be removed, labeled, and stored in the cabinet’s
document protector.
Power Supply
The power supply in the 3000 is a state-of-the-art line powered switched mode type,
which provides very cool and efficient operation with over one second of storage
capacity. The incoming line voltage is rectified and directly down converted to all the
necessary voltages, none more than 30 VDC. In this application, the switched mode
supply usually operates at least 15°C cooler than an equivalent linear supply, thus
contributing to longer life for all surrounding components. The power supply includes
an Analog to Digital (A/D) converter that the 3000 uses to monitor supply voltages
and currents inside the unit.
Communications Ports
An EIA-232 (RS-232C) serial port, Port 2, is included standard with each controller for
connecting to a printer, monitor, personal computer, or modem (including radio
modems). The data rate is programmable from 1200 to 19,200 bps.

The optional System Interface permits FSK TDM 1200 baud communications over
twisted pair wire using a Digital Signal Processor (DSP) internal modem (3000E only).
This scheme is typical of UTCS and closed loop applications, and provides
compatibility with NEMA Traffic Standards (TS 2) Port 3. The transceiver is
compatible with the BELL-202 modem standard. Also available instead of the DSP
modem is a family of Fiber Optic Transceivers capable of baud rates of up to 19200.
The transceiver module can accommodate a variety of emitters and detectors
including, 850nm multi-mode, 1300nm multi-mode (3000 only), and 1300nm single-
mode (3000 only). A second RS-232 port is also available as an option to drive an
external modem or for connection to a CMU or an Opticom unit.
The TS 2 3000 Controller meets and exceeds the NEMA 2003 TS 2 standard and
contains a RS-485 connector in Port 1 for Bus Interface Unit (BIU) Communications.
This feature is standard for TS 2 Controllers.
In 2004, a new Ethernet/Serial port combination card was made available for slot 3 of
the TS 2 3000E controller, and the firmware was modified to include the appropriate
communications parameters for an Ethernet connection (i.e. IP address, subnet
mask, etc.) When installed, a standard Ethernet connection can be made with the
3000E controller across any TCP/IP network.
CPU
The heart of the system is a Motorola 32 bit 68302 Integrated Multiprotocol Processor
running at 16.667MHz. The processor addresses 1Mbyte of ROM and 256Kbytes of
battery-backed RAM with no wait states.
Input Filtering
NEMA control inputs in the 3000 do not use capacitors, RC networks or any other
analog filtering. All NEMA control inputs use digital sampling and filtering techniques
to reject frequencies outside the required specification.
Sequence Configuration
The 3000 Series controller employs a very flexible approach to sequence
configuration. It will support up to 16 each of vehicle and pedestrian phases plus 16
vehicle and pedestrian overlaps. Each phase may be assigned to any of 4 rings and
up to 8 barriers. Barriers (or compatibility lines) may be inserted anywhere within the
sequence. This flexibility allows the user to program very complex sequences. A
number of commonly used sequences are pre-programmed and can be loaded with a
single key.
Channel Assignments
The TS 2 Controllers (Type 1 and Type 2) contain the capability to assign
responsibilities for the 16 available channels monitored by the Malfunction
Management Unit (MMU). MMU is the TS 2 definition for a conflict voltage monitor.
The 16 channels each contain three (3) inputs (R, Y, G) that can be assigned to any
combination of vehicle movements, pedestrian movements, vehicle overlaps and/or
pedestrian overlaps.

Controller Timing Plans

There are 4 sets of phase interval timing parameters, called timing plans, that can be
called by the time-of-day scheduler or by manual override. Intervals included are;
Initial, Passage, Max 1, Max 2, Yellow, Red Clearance, Walk, and Pedestrian
Clearance. Volume density parameters included are of Time to Reduce, Time before
Reduction, Last Car Passage, Minimum Gap, Added Initial per Actuation, and Max
Initial. Phase control functions included are; Minimum, Maximum, Pedestrian and
Soft Recall modes, memory Lock/Non-Lock, Phase & Pedestrian Omits, Walk Rest
mode, Max 2 by phase, Red Rest by phase, and No Skip by phase.
Lead/Lag Operation
There are 4 sets of lead/lag (phase reversal) patterns, any of which may be called by
time clock, day plan, pattern number, external input or manual entry. These lead/lag
plans provide for dynamic sequence adjustment that is often required for complex
intersection configurations.
Max 3 (demand adjusted max time)

A dynamically adjusting phase max time, called Max 3, can be implemented in the
3000 Series controller. If this feature is enabled, each phase may independently
adjust its own Max Time depending on the traffic load (Max’s, Gap-outs) on that
phase.
Dimming
Load switch dimming is user programmable by phase and signal color. AC power
factor is automatically balanced by assigning some outputs to be dimmed on the
positive half-cycle and others to be dimmed on the negative half-cycle. Dimming may
be activated by Time of Day (TOD) circuit or an external input on the “D” Module.
Soft Flash Operation (controller flashes load switches)

Soft flash is also programmable by phase and signal color and may be called by the
time clock or external input. A two-circuit flash (Wig/Wag) is provided so that outputs
may be programmed to operate Wig or Wag flash or Dark (vehicle phases and
overlaps only). This is the primary method used to send a 3000 Series TS2 Type 1
controller into flash operation, since no CVM or UCF exists for this
controller/environment.
Detectors
Detectors may be programmed to operate in one of 5 modes of operation and may be
assigned to any phase or set of phases. The 5 modes are Call/Extend (NEMA), Call
only, Stretch/Delay and Stop Bar 1 or 2. In addition, conditional detector switching
and copying enables special sequences without requiring external detector
manipulation. Detector switching and copying takes place only when the programmed
phase-on conditions are met. This is a very useful feature for lead/lag or diamond
intersection control.

The 3000 Series Controller monitors for and logs 4 types of detector failures. The four
failures are Absence, Locked, Erratic and Minimum Presence. Also, failing
detectors can optionally place specified phases on recall.
Dynamic recall and omits

Two other features that are used to modify the normal sequence, are Dynamic Recall
and Dynamic Omits. These allow phases to be recalled or omitted when specified
phases or overlaps are green to create special conditional sequences.
I/O Steering
The 3000 Series Controller allows certain signal outputs (vehicle or pedestrian
movements as well as overlaps) to be ‘redirected’ or “steered” to another output. This
allows access to outputs that would not normally have a physical pin associated
without a custom D module inserted. For example, the Overlap E Red, Yellow and
Green outputs can be redirected to the phase 2 Red, Yellow and Green output pins
on the MS-A connector. In TS 2 Type 1, these outputs are directed from the RS 485,
Port 1, through the BIUs to their appropriate destinations. This technique may be
useful for ‘diamond’ sequences where all output signals are actually overlaps. Also,
the ON, NEXT, and CHECK outputs are available for reassignment if they are not
otherwise needed for external logic.
Preemption
The flexible approach to sequencing has been extended to preemption giving the
user complete control to generate complex preempt sequences including the ability to
flash signals and leave signals dark if so desired.
Time of Day Control

The calendar scheduler allows the selection of operating patterns and special
conditions on a calendar basis. Patterns and conditions are known as events, and
may be selected by time of day (TOD), day of week, day of month and day of year.
The controller keeps track of the week of year so that cyclic functions most typical of
traffic control may use repeating weeks. The TOD capabilities of the 3000 Series
include 220 events, 20 week plans, 32 day plans, and 50 exception days that may be
programmed by date or by day of week and week of month. In addition, the time
clock may be reset to a specified time by an external input. Each event time may
select a timing pattern (cycle, offset and split) and control conditions through the use
of time clock circuits. There are 166 circuits available and this number can be
expanded to 255. Examples of conditions that may be controlled by time of day
include phase and ped omits, call to (CNA), timing plans 1-4, free operation and most
NEMA inputs such as ped recycle, omit red clearance, etc.
Dynamic Displays
A number of dynamic displays are included to better monitor the operation of the
controller. In addition to the main display that shows vehicle & pedestrian demand
and interval information, there are displays that indicate the status of all inputs and
outputs, density, coordination, time of day, logs, and preemption.

Security Codes
There is a two level security system available that, when implemented, allows some
users access to all data, and others access only to less critical data areas. If there is
no keyboard activity for 5 minutes, the user is required to reenter the security code to
gain access to the data programming screens if security is enabled. A security code
of 0 will disable the security system. The security system also permits a user with the
privileged security code to restrict access to sensitive data. A user with the restricted
security code will not be able to change data in these restricted areas. The privileged
security code also enables the removal of menu items that are not needed in order to
simplify the user interface.
Adding and Deleting Menus

The 3000 Series unit is shipped with its full compliment of menus available. A feature
is provided, however, that allows the user to delete menus that will not be used to
streamline and simplify the menu set. Deleted menus can be restored at any time.
Coordination
The internal coordination system provides for 6 cycles, 5 offsets per cycle and 4 splits
per cycle. Phase allocation (Split) programming may be done in seconds, or percent
of cycle length, at the user's option. Offsets may also be entered in seconds or
percent independently of the split entry mode. An automatic permissive calculation
feature is included with three modes of operation: single permissive, multiple
permissive and yield permissive. For maximum flexibility, Manual Permissives are
available for each phase per Cycle/Split combination. When offset seeking is
required, there are three ways to get back in sync: Shortway (Short Route), Add Only
and Dwell. TOD circuits and lead/lag plans may be activated by cycle, offset, split,
and free patterns.
The 3000 Series controller can be programmed to revert to free operation, if it
receives no sync pulses for a selected number of cycles. Free operation may also be
activated if no offset line is active or multiple offset inputs are active for a selected
number of seconds.
Indexing
An Index feature is available to assist in providing quick access to the controller’s
databases via the keyboard. If, for instance, an operator wishes to learn what
keystrokes would be required to configure the controller for Dual Entry operation, she
could use the Index feature to find the proper sequence of keystrokes. To access
Indexing, press SHIFT - CLEAR from within any of the Read Data or Change Data
screens. (Or you can choose option 9 on the main Read Data and Change Data
menus to access the Index feature.) Once the desired data item is located in the
index list (items are arranged alphabetically), the operator can place the cursor on the
item in question and press ENTER to go directly to the data screen where that
parameter is stored.

CONFIGURATION OPTIONS
NEMA TS 1
The Standard I/O configuration for the 3000 Series controller includes basic 2 - 8
phase operation by utilizing the MS-A, B, and C connectors. Special I/O
requirements, such as use of phases 9 - 16, are met through the use of a number of
‘D’ connector options. ‘D’ connectors available at this time include preemption,
closed loop (which includes preempt), and 12 phase. Custom modules are available
for the states of Texas and Idaho, the cities of Las Vegas and Phoenix. A module is
also available that is compatible with the CPC connector used on the LMD line of
controllers. Custom ‘D’ modules are available by request; please contact the Peek
Traffic Sales Department for information on special I/O requirements.
Note Peek Traffic no longer produces TS1 controller firmware for the 3000 Series.
TS 1 operation can be achieved by using the TS 2 firmware in a TS 2 controller
and simply not programming the TS 2 features.
NEMA TS 2, Type 1 (TS 2-1)

Standard I/O configuration for the TS 2-1,3000 Controller includes basic 2,4, 8, and
12 phase operation by utilizing channel assignments received through the BIUs. BIU
channel assignment is programmable within controller menus. A 10 pin MS-A
Connector is installed to provide power and fault monitor output functions only. The
TS 2-1 MS-A Connector contains AC(+), AC(-), logic ground, earth ground and the
fault monitor output. The TS 2 Type 1 standard interface shall control all Inputs and
Outputs through Port 1, the high speed RS-485 serial data bus, which uses digital
addressing to assign all cabinet functions. The Port 1 physically interfaces to the
cabinet terminals and facilities and other devices via a TS 2 compatible Bus Interface
Unit (BIU). Other devices include a TS 2 compatible Malfunction Management Unit
(MMU) and TS 2 compatible detector rack(s). The controller also provides an EIA-
232 (RS-232C) terminal (Port 2) and a telemetry interface (Port 3) for systems
communications.
NEMA TS 2, Type 2 (TS 2-2)

The TS 2 Type 2 standard includes the features of the Type 1 unit plus the TS 1
standard MSA, MSB, and MSC connectors for downward compatibility with NEMA TS
1 cabinet facilities. This type also provides an EIA-232 (RS-232C) terminal (Port 2)
and a telemetry interface (Port 3) for systems communications.
The TS 2 3000 Series modularity supports NEMA TS 2 Port-3, UTCS applications,
integral Fiber Optics and radio interconnect operation for conventional narrowband and
spread-spectrum radio equipment making the TS 2 3000 compatible with existing TS 1.

Configuration Options
Optional Modules
The following are optional 3000 Series modules. A brief description of the module’s
significant function is provided. Refer to Appendix C for detailed pin-out listings for
each of these modules.
Table 6 – Communications/Optional Modules available for 3000 Series units
Module Pin Count Significant Functions Provided
Port 1 Comm 15 pin (Standard, not optional) TS 2 port 1, High
Speed Serial (SDLC)
Port 2 Comm 25 pin (Standard, not optional) TS 2 port 2, RS-232
Closed Loop ‘D’ Auxiliary 37 pin User defined inputs, alarms, coord outputs,
Module opto isolated inputs, preempt outputs, detectors
29-32
Closed Loop ‘D’ Preempt 25 pin Preempt 1-6 inputs, Det’s 9-16, misc. I/O
Module
Closed Loop ‘D’ Coord Module 26 pin Det’s 17-32, FSK xmit/recv, misc. I/O
LMD ‘D’ CPC Module 63 pin Compatible with TCT LMD series ‘D’
LMD ‘D’ Auxiliary Module 15 pin Det’s 17-32, FSK xmit/recv, misc. I/O
12 phase ‘D’ Module 100 pin Provides I/O for 12 phase operation
Texas ‘D’ 57 pin Coord interconnect functions (No longer
available for the 3000E)
Texas ‘D’ Auxiliary Module 37 pin Det’s 17-24, FSK xmit/recv, misc. I/O (No
longer available for the 3000E)
Las Vegas ‘D’ Module 57 pin Pre-empt & Coord interconnect functions (No
longer available for the 3000E)
Las Vegas ‘D’ Auxiliary Module 25 pin (No longer available for the 3000E)

Usage With Conflict Monitors & Malfunction Management Units

The 3000 and 3000E are fully compatible with NEMA conflict monitors (CMUs) and
malfunction management units (MMUs). CMUs are a TS 1 standard for monitoring
controller operation, while MMUs are a TS 2 standard that performs the same
function. The 3000 series controllers output a steady CVM signal on Pin C of the A
connector of TS 1 and TS 2 Type 2 controllers. A similar call fault monitor signal is
provided on Pin F of the A connector of TS 2 Type 1 controllers. The CMU (or MMU)
monitors this signal to verify that the controller is receiving the electrical voltage it
requires. If this CVM/fault monitor signal drops, the CMU or MMU will kick the
intersection into flash as a safety precaution.
During the startup of the controller, most monitoring units are designed to give the
controller a few seconds of lee-way on the generation of the CVM, while the controller
performs its initialization and time-sync operations. This is to prevent the CMU from
immediately kicking the intersection into flash when the controller takes the time it
needs to get up and running.
The CMU typically monitors the CVM output and the outputs of the load switches in
the cabinet with no other intelligent connection to the controller. An MMU, on the
other hand, also has the CVM/Fault Monitor connection and the load switch
monitoring, but it also usually has an intelligent link with the controller via the
controller’s Port 1, a serial RS-485 connection.

Chapter 2 — Status Displays
This section explains the contents of option 1 of the 3000 and 3000E Main Menu: the Dynamic
Displays, as well as a few other screens that are important for the normal operation of the
controller. The following topics are discussed in detail in this chapter:
“Status Check Upon Startup”, on page 28

“Primary Controller Status Screen”, on page 30.
“Additional Status Screens”, on page 39
“Coordination Status Screen”, on page 54
“Time of Day Status Screen”, on page 57
“Preemption Status Screens”, on page 59
“Voltages Screen”, on page 63
“Overlap Functions Status Screens”, on page 64
“Program Level & Revision Screen”, on page 65
“Log Menu”, on page 66
“Checksum Status Screens”, on page 73
“Comm Status Screens”, on page 75
“TS 2 Dynamic Help Screens”, on page 77
“Diagnostics”, on page 81

STATUS CHECK UPON STARTUP

In firmware releases prior to version 3.6, the configuration databases in the controller
were tested every time the system was started using a somewhat confusing set of
Checksum tests, followed by a set of screens that could be used to override the test
results if any errors were found. But beginning with the version 3.6 firmware, the
controller’s firmware simply tests the seven controller databases upon startup and
reports immediately if any problems are found.
RUNNING POWER ON SELF TEST
Figure 13 – Self-test screen that appears upon power up

If any problems are discovered, an error screen appears, showing all of the
databases where problems were detected. This is what the screen looks like when
(for example) three of the databases have errors:
Database sections are corrupt!
[Time of Day] [Preemption] [Special]
Press the [CLEAR] key to clear the

above sections and continue.
Figure 14 – Power-on Error Message with 3 database errors detected
Previously, the tests were performed and the controller went ahead and started up,
even if it did detect a ‘Checksum’ error. As a result, the operator had to look very
carefully at the main dynamic status screen to see if there were problems, the new
system uses a CRC test (Cyclic Redundancy Check) and it won’t allow you to start
the controller unless you acknowledge that you’ve seen the error by pressing the
CLE AR key.
An error followed by a CLE AR entry also clears the database contents to a blank
state. This is judged to be safer than allowing a corrupted database to be used to run
an intersection.

Status Check Upon Startup
After such an error, the controller’s database should be reset to default, or a good
database should be loaded into the controller via CLMATS, an EEPROM card, or by
using the Pocket Central software on a Pocket PC handheld device.
Note For details about the way that the CRC check is performed in
CLMATS and the 3000 series controllers, refer to the MIZBAT
Protocol Manual, available from Peek Traffic Corporation.
To be sent a copy of this document, the customer must sign a
Non-Disclosure Agreement.
Two other related version 3.6 changes to the interface are in the Dynamic Controller
Display screen and the Checksum Status screen. The Status of the controller is still
shown on the bottom line of the Dynamic Controller Display screen (MM > 1 > 1), but
since checksums are no longer tested, these kinds of errors no longer appear in this
location. (Error status is shown upon startup as described above.)
The other item is on the Dynamic Display menu (MM > 1), where the Checksum
Status option still appears (Option 9), but it now only shows this message: “NO
CHECKSUM FAILURES PRESENT”. The controller no longer allows an operator to
reset the checksum calculation so that the controller will run with a faulty database in
memory for safety reasons.
Cleaned Up Override Clearance

Prior to the version 3.6 firmware, the controller’s Central Override states could be
cleared from the Comm dynamic display screen (MM > 1 > shift-0). However, an
effort has been made to remove all data entry and modification functions from the
dynamic display screens. These areas are intended to be safe areas where controller
status is viewed, but not modified. As a result, the clearance of Central Overrides is
now performed elsewhere.
Clearing a Central Override

1. To clear a central override, go to the Coordination Menu and then into the
Enhanced Options screens. (The exact path is M M > 3 . C h a n g e D a t a >
2.Coordination > 9.Enhanced Options > 1.Operating
O p t i o n s .)
2. To clear the overrides, change the value of Central Override to N if Y is
displayed, or to Y if N is displayed..
3. Check the Dynamic Screen’s Comm option to verify that there are no overrides
still active. (M M > 1 . D y n a m i c D i s p l a y s > 1 0 [ S h i f t - 0 ) . C o m m )

PRIMARY CONTROLLER STATUS SCREEN

The Primary Controller Status Display screen can be accessed by pressing option 1
on the Dynamic Menu. However, a shortcut method to this screen is always available;
press SHIFT -ENTER .
The Controller Funcs display allow the user to view the real-time operation of the
controller, with emphasis on phase related items, such as interval, timing, signal head
color, detectors, etc. This Controller status screen is the primary status display for the
3000 Series, however there are a whole set of status display screens that can be
reached by paging down from it.
Note There is a method to place Vehicle and Pedestrian phase calls manually while viewing
either the Primary or the Alternate Controller Status Screens. To place vehicle calls on
Phases 1-8, press the Up-Arrow and the corresponding keypad number
simultaneously. To place Ped calls on Phases 1-8, press the Left Arrow and the
corresponding keypad number simultaneously. These controls also work on the
Coordination Status screen.
Controller Status Screen

The Controller Status screen shows phase (1-12) and overlap (A-D) indicators
(current state), phases next to be served, vehicle and pedestrian demand on all
phases, phase interval timers, the state of the phase (ring), and the mode of
termination. Coord/free status is also shown with the active cycle and offset timers.
Unused phases and overlaps are not shown.
13:10:07 COMM: On-Line 1 1 1 -O/L-

PH/OL 1 2 3 4 5 6 7 8 9 0 1 2 A B C D
INDIC. G r r - G r - - - - - - R - - -
V DEMAND X R M - X R - - - - - - |Cyc 1
P DEMAND R X - R - - - - - - - | XYZ
MIN XY WLK XY |MIN XY WLK XY |Ofs 1
MX1 XY PSG XY |MX1 XY PSG XY | XYZ
TP1, FREE, Closed Loop |Spl 1
Figure 15 – Controller Status screen
Although the Controller Status screen only shows phases 1 through 12, rings 1 and 2,
and overlaps A through D, this is typically sufficient for the majority of applications.
However, if a particular application requires more than these, the Alternate Controller
Status screen can be used instead (Refer to Page 38.) This alternate status screen
shows all 16 phases and all 4 rings ( when used) on a single screen.
The advantage of this Controller Functions Status screen, as shown above, is that it
packs a lot of information on one screen. Once familiar with this display, there is little
need for accessing the other status screens.
Note Since this is the standard operating screen for the 3000 and 3000E Traffic
Controllers, a user can always access this screen from anywhere within the menu
structure by pressing SHIFT – ENTER .

Primary Controller Status Screen
Status Screen Navigation
Figure 16 – Navigating the status screens

Layout of the Controller Status Screen

2 3
13:10:07 COMM: On-Line 1 1 1 -O/L- 4

PH/OL 1 2 3 4 5 6 7 8 9 0 1 2 A B C D
INDIC. G r r - G r - - - - - - R - - -
V DEMAND X R M - X R - - - - - - |Cyc 1
P DEMAND R X - R - - - - - - - | 79%
MIN 12 WLK 4 |MIN 8 WLK 2 |Ofs 1 5
MX1 4 PSG 2 |MX1 3 PSG 1 | 2S
TP1, FREE, Closed Loop |Spl 1
Figure 17 – Detail: Top three lines of the controller status screen
The following are functions of the various parts of the Controller Functions Status
screen.
1. ROW 1 LEFT, TIME OF DAY — Shows time of day in the format HH:MM:SS.
2. ROW 1 MIDDLE, COMM ON/OFF LINE —
On Line = Comm active and OK
Off Line = Not programmed for Comm, not supposed to be on
FAIL = Programmed for Comm but carrier has been lost, not working
3. ROW 1 RIGHT, “ 1 1 1 --O/L--” — (Phase/Overlap column titles)
The right side of row 1 is for the tens designation of phases 10-12, and the
“O/L” designation for overlaps (static text).
4. ROW 2 STATIC, “PH/OL 1 2 3 …” — Phase and Overlap labels
5. ROW 3, “INDIC. G r r…” — Indications/Intervals for phases and overlaps.
Table 7 – Phase/Overlap* Indicators (in increasing order of priority)
Letter code Meaning
– Phase is not used (no signal indication)
N This phase next
R Phase is in red clearance
Y Phase is in yellow interval
W Phase is in walk
D Phase is in ped clear (FDW)
G Phase is in green (no walk or ped clear)
r Phase is red, not ON (other phases are in service)
*
Only G, Y, R, and “–“ are applicable for overlaps A through D. An O/L is considered not
used if no parents are assigned to it.
13:10:07 COMM: On-Line 1 1 1 -O/L-

PH/OL 1 2 3 4 5 6 7 8 9 0 1 2 A B C D
INDIC. G r r - G r - - - - - - R - - -
9
6 V DEMAND X R M - X R - - - - - - |Cyc 1
P DEMAND R X - R - - - - - - - | 79%
7 MIN 12 WLK 4 |MIN 8 WLK 2 |Ofs 1
MX1 4 PSG 2 |MX1 3 PSG 1 | 2S
8 TP 1, COORD, Time of Day |Spl 1 10
Figure 18 – Detail: Middle four lines
6. ROW 4, “V DEMAND” — Vehicle Demand. Shows phase input and recall
status. Codes are shown In order of priority when more than one state is true.
Table 8 – Vehicle Demand codes, in order of priority
Code Description Note
– Phase not used
P Preempt Call applied Preempt overrides Omit
O Phase omitted no vehicle call
O. Phase omitted with vehicle call
H Phase hold applied no vehicle call
H. Phase hold applied with vehicle call
R Max Recall applied no vehicle call
R. Max Recall applied with vehicle call
r Min Recall applied no vehicle call
r. Min Recall applied with vehicle call
X Vehicle detect input physically active no preemption, no omits,

no hold, no recalls
M Vehicle detect call stored in memory lock mode
(blank) None of the above phase is used, but no

preemptions, omits,
holds, recalls, or demand

7. ROW 5, “P DEMAND” — Pedestrian Demand. Shows pedestrian input and

recall status. Codes are shown In order of priority when more than one state is
true.
Table 9 – Pedestrian Demand codes
P Demand Code Description
– Phase not used
X Pedestrian input physically active
R Ped Recall
M Ped call stored in memory
(blank) No demand, phase is used but none of the above apply (no
calls, etc.)
8. ROW 6 & 7, left side, Phase Timers (by Ring) — There are eight positions
for timers and status, four on the left side for ring 1 and four on the right for ring
2. These are grouped into four groups of two labels side-by-side. Each position
can display a label and an associated time value, if appropriate to the label.
Other labels may appear in these positions that indicate a general status (for
example GRN REST.)
9. ROW 4 through 8, Right Side: Timing Plan and Coordination Timers —
Top row = “Free” if the controller is running in free operation (i.e. no
coordination.)
Or, if in the system is configured for coordinated operation:
Top 2 rows = “Cyc 1-6” with active local cycle timer shown below, displayed in
either seconds or a percentage.
Next 2 rows = “Ofs 1-5” (offset) and its timer shown below. However, if the unit
is offset seeking, these rows will say “SEEK” with the current offset timer value
shown below.
Bottom row = “Spl 1-24” (split, no timer).
10. ROW 8. Left Side: Controller Status — Used to indicate the unit’s current
operating state. There are two general states:
Normal Operating Status — If the unit is running normally with no special
condtions, the following status will be displayed: TP# FREE or COORD, and
TOD or CL.
Override/Fault Status Indicators — These messages indicate that the unit is
being overridden in some way (UCF, preempt, etc.,) something is incorrect in
the configuration of the controller, or the unit has failed.

The information in Table 10 should help you interpret the message.

Table 10 – Error/Failure Status Indicators
Message Displayed Description
24 VOLT FAILURE The TS 1/TS 2 Controller is monitoring an internal 24 VDC
Failure. The actual voltage reading is also shown.
BAD COORD PLAN The controller is running in a Free Mode due to an error in the
requested coordination pattern.
BIU FAILURES: SEE HELP One or more BIU’s have failed. Pressing the HELP button in
this situation will open a help screen especially designed for
this situation.
CENTRAL OVER,OVR Indicates that Central has overriden the current controller
CENTRAL, OVR UCF operation.
CHECKSUM FAILURE Indicates a corrupted database (See Dynamic Menu, Item # 9,
Checksum status for specific information) (TS 1/TS 2). Check
values in indicated area. Any keyboard entry in indicated area
will clear checksum (see checksum latch below).
CHECKSUM LATCH A checksum failure has been cleared but the fault remains
latched until the unit is re-started.
CLEARING BIU FAILURES A restart has been conducted to eliminate BIU failures. This
message indicates the Controller is in the process of rectifying
all BIU failures.
COORD FAULT A coordinator failed to serve a valid phase call within two
cycles.
CONTROLLER CONFLICT The controller detects a conflict via information sent from the
FLASH MMU via Port 1, but the MMU has not entered the fault state.
CYCLING FAILURE-FLASH The TS 1/TS 2 Controller has failed to answer a serviceable
conflicting call within two times the longest path between
barriers during Free operation.
EEPROM FAILURE During the start up sequence the TS 1/TS 2 Controller did not
detect it’s required EEPROM.
EPROM FAILURE Failure during the EPROM diagnostic test.
ESTABLISHING BIU LINK At power up this message displays until communications with
all BIUs are established.
EXTERNAL START External start is active.
FLASH EXIT ERROR Indicates incompatible programming of the UCF Flash Phases
with the UCF Exit Phases. (TS 1/TS 2.)
I/O FAILURE The TS 1/TS 2 Controller cannot recognize the current
input/output configuration.
MCE Manual Control Enable input is active.
MMU FLASH: SEE HELP Occurs when the MMU puts the intersection in flash. Pressing
the HELP button will open a special screen designed for this
situation.
MMU INCOMPATIBLE: SEE
HELP
OVERLAP CARD ERROR At power up the TS 1/TS 2 detected an overlap card is
enabled in the programmed configuration (Controller >
Overlaps menu) but no card is present.

Message Displayed Description

PORT 1 FAIL: FRAME 18 Frame 18 was not sent out within 0.5 seconds.
RAM FAILURE Failure during RAM diagnostic test.
RUN ACTIVE + 1, ACTIVE
RUN IN,SEE A fault has occurred which stopped execution of the current
HELP,PREFAULT = preemption run.
RUN X ACTIVE Preempt number X is active.
SOFT FLASH The controller is flashing signals via the load-switches.
STARTUP PE RUN ACTIVE The TS 1/TS 2 Controller was powered up with a preempt
active which will keep the intersection in flash.
STARTUP, FLASH ACTIVE A flash command was called for during the power up process
(TS 1/TS 2).
STOP TIME Stop time inputs are active.
TOD-LOST COMM
TS 2 Flash Indications
TYPE 2 I/O MODE ERROR Database I/O mode does not match the I/O mode that was set
via the MS-A connector’s I/O mode bits A, B, and C.
UCF CENTRAL (if central Same as above but command received from central.
override)
UCF FLASH The TS 1/TS 2 Controller has received an enter flash
command and has entered flash.
WATCHDOG FAILURE The microprocessor's watchdog input has not been serviced
within the specified time.
TS 2 Flash Error Messages

“MMU FLASH” and “CONTROLLER CONFLICT FLASH” are TS 2 error messages
related to information received on port 1. “MMU FAULT” indicates that the MMU has
declared a fault, such as conflict, red fail, etc. and that it has placed the intersection in
flash. “CONTROLLER CONFLICT FLASH,” indicates that the controller has detected
a conflict but the MMU has not placed the intersection in flash.
Controller Status Screen Abbreviations

The abbreviations used on the Controller Status screen are listed below.
Table 11 – Vehicle and pedestrian demand codes
Code Description
V Vehicle Call (Actuation)
P Ped Call (Actuation)
M Veh or Ped Call in Memory
O Omit
H Hold
r Min Recall

R Max Recall
Table 12 – Interval Abbreviations

Abbreviation Description
DCL Double Clearing Overlap
DWK Don’t Walk
GRST Green Rest

HRST Hold Rest
INIT Initial
LCP Last Car Passage
PASS Passage
PCL Ped Clearance

PHD CNA Green/Don’t Walk Rest
PREP Green Prep
RED Red Clearance

RRST Red Rest
RRVT Red Revert
WK Walk
WR Walk Rest
WRM Walk Rest Modifier
YEL Yellow Clearance
Table 13 – Max and Termination Abbreviations

MX1 Max 1 timer value
MX2 Max 2 timer value

MX1+ Max 3 timer overriding Max 1
MX2+ Max 3 timer overriding Max 2
GAP TERM Phase term. due to gap out condition

MAX TERM Phase term. due to max out
FORCE TERM Phase forced off

RREST TERM Phase terminating to Red Rest
M ADV TERM Phase terminating due to MCE Interval Advance

ALTERNATE CONTROLLER STATUS SCREEN

If you page down from the top Controller Status screen, you will see the Alternate
Status screen. This is the interface that was used on the original 3000 Controller for
status display. It is somewhat less detailed than the new display, but some user’s
prefer it, since it provides information on all 16 phases on a single screen.
Status information is shown in the top left corner of the screen. During normal
operation, the current timing plan and coordination plan are shown. If coordination is
active, the local cycle counter is also displayed, otherwise, the word “FREE” is
displayed. If the controller is in an abnormal situation (e.g., preemption, UCF,
checksum failure) a message is shown in this area that describes the reason for the
abnormal operation.
TP1 1/3/1: 75 1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
V DEMAND O R r V O R r r V M M M r r
P DEMAND M M O O O O O
R1 2 ON 3 NX YEL 2.1 DWK GAP TERM
R2 6 ON 7 NX YEL 2.1 DWK GAP TERM
R3 10 ON 0 NX PREP DWK MX1 0
R4 14 ON 0 NX PASS 2.6 DWK MX1 23
Figure 19 – Alternate Controller Status screen
The top line of this display is used for special messages.
Note There is a method to place Vehicle and Pedestrian phase calls manually while
viewing either the Primary or the Alternate Controller Status Screens. To place
vehicle calls on Phases 1-8, press the Up-Arrow and the corresponding keypad
number simultaneously. To place Ped calls on Phases 1-8, press the Left Arrow
and the corresponding keypad number simultaneously. These controls also work
on the Coordination Status screen.

Additional Status Screens
ADDITIONAL STATUS SCREENS

All of these screens are varying ways of viewing the controller’s current status. They
can be accessed by choosing Dynamic Displays from the Main Menu, and then
choosing Controller Funcs. These pages are then accessed by paging down from
the Controller Status screen.
Refer to the following pages for details about each of these status screens:
Normal I/O Status screen, on page 40.
Density Status screen, on page 41.
Outputs Status screens, on page 42.
Inputs Status screens, on page 45.
Detector Status screens, on page 47.
I/O Configuration Status screen (TS 1 or TS 2), on page 49.
D Module Outputs Status screen, on page 52.
Coordination Status Screen on page 54.
Time of Day Status screen, on page 57.
TOD Dynamic Circuits Status screens, on page 58
Preemption Run Duration Timer screens, on page 58.

Normal I/O Screen

This screen can be accessed by paging down from the Alternate Controller Status
screen. Here is a sample of a Normal I/O screen:
1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
V OUTPUT R G R R R G R R
P OUTPUT D W D D D W D D
ON/NX O O
V MEMORY M V M
P MEMORY M P M
OMITS B V
Figure 20 – Normal I/O Status screen
The Normal I/O dynamic screen shows the current status of the controller's phase
related inputs and outputs. Phase outputs, pedestrian outputs, calls, memory and
omits are all displayed.
Table 14 – Normal I/O screen key
Display Value
V(ehicle) OUTPUT R=Red
Y=Yellow
G=Green
P(edestrian) OUTPUT D=Don't Walk
W=Walk
P-C=Ped/Clear (toggling)
ON/NX O=Phase On
N=Phase Next
V MEMORY V=Vehicle Call
M=Memory
P MEMORY P=Pedestrian Call
M=Memory
OMITS V=Vehicle Omit
P=Ped Omit
B=Both Veh & Ped Omit

Density Status Screen

The Density Status screen can be accessed by paging down from the Normal I/O
Status screen. It shows density information for up to four rings on a single screen.
Here’s a sample of a Density Status screen:
** DENSITY **
R1 PH 2 R2 PH 6 R3 PH R4 PH
PASS 4.0 LCP 0
MGAP 0.0 PTMR 0.0
TBR 0 TBR 0.0
TTR 0 TTR 0
PTMR 0.0 PTMR 0.0
MX 1 30 MX 1 30
Figure 21 – Density Status screen
The Density dynamic screen can be used to watch phase timing on both density and
non-density phases. For non-density phases, the initial, passage and max timers will
be displayed, as well as yellow and all red. For density phases, the passage, max
timers and all density settings will be displayed. The passage timer will show its
reduced state after reduction begins.
Table 15 – Density Status screen key
Abbreviation Description Static/Dynamic Density/Non-Density
APA Added Initial per Actuation STATIC DENSITY
INIT Initial Time STATIC BOTH
ITMR Current Value of Initial Timer DYNAMIC BOTH
LCP Last Car Passage STATIC DENSITY
MGAP Minimum Gap STATIC DENSITY
MXIN Max Initial STATIC DENSITY
MXn Current Value of Max Timer DYNAMIC BOTH
(a + indicates MX3)
PASS Passage Time STATIC BOTH
PTMR Current Value of Passage DYNAMIC BOTH
Timer
RED Red Time STATIC BOTH
RTMR Current Value of Red Timer DYNAMIC BOTH
TBR Time Before Reduction STATIC DENSITY
TTR Time To Reduce STATIC DENSITY
YEL Yellow Time STATIC BOTH
YTMR Current Value of Yellow DYNAMIC BOTH
Timer

Example Density Status Screens

In the following example screens, phase 2 is a density phase and phase 6 is not.
** DENSITY **
INIT 10 INIT 10
MXIN 20 MXIN 0
APA 2.0 APA 0
ITMR 12.0 ITMR 8.0
MX 1 19 MX 1 19
Figure 22 – Density Status screen - Example 1

** DENSITY **
PASS 4.0 PASS 4.0
MGAP 20 MGAP 0
TBR 5 TBR 0
TTR 10 TTR 0
PTMR 3.2 PTMR 4.0
MX 1 19 MX 1 19
** DENSITY **
YEL 3.0 YEL 3.0
YTMR 2.1 YTMR 2.1

** DENSITY **
RED 2.0 RED 2.0
RTMR 1.2 RTMR 1.2

Outputs Status Screens

The Outputs Status screen can be accessed by paging down from the Density Status
screen.
PG1 ** OUTPUTS ** 1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
CHECK C C C C C C
ON/NEXT O N O N
VEH HEAD R G R R R G R R
PED HEAD D W D D D D D D
VOL HEAD R R R R R R R R R R R R R R R R
POL HEAD D D D D D D D D D D D D D D D D
Figure 26 – Output Status screen - page 1
Outputs allow the user to see the status of phase outputs as well as per ring status
bits.
PG2 ** MACHINE OUTPUTS **
STATUS BITS DEC STAT RING
CBA CODE NAME INTERVAL
RING 1 000 0 MIN GRN INIT- DWK
RING 2 001 1 EXTENSION PASS- DWK
RING 3
RING 4
FL LOGIC ON
Figure 27 – Output Status screen - page 2
Table 16 – Outputs Status screen key

Label Value
CHECK C = Phase Check On
ON/NEXT O = On
N = Next
VEH HEAD & R = Red
VOL HEAD Y = Yellow
G = Green
PED HEAD & D = Don't Walk
POL HEAD W = Walk
P-C = Ped/Clear (toggling)
The ring interval is shown in a phase-ped pair. The different phase and ped ring
intervals are discussed in the NORMAL STATUS section. Flashing Logic should
always be switching between ON and OFF.
Status bits are defined as bits C, B and A. These bits represent a decimal code that
indicates the ring status and interval. Refer to Table 17.

Table 17 – Output Status Bit definitions

CBA Value Decimal Equivalent Description CNA Phase
000 0 MIN GRN WALK TIMING
001 1 EXTENSION WALK HOLD or REST
010 2 MAXIMUM PED CLEAR
011 3 GRN REST GRN REST
100 4 YEL YEL
101 5 RED CLEAR RED CLEAR
110 6 RED REST RED REST
111 7 NOT USED NOT USED

Inputs Status Screens

The Inputs Status screen can be accessed by paging down from the Outputs Status
screen. Here is an example.
PG1 ** INPUTS ** 1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
PED OMIT P P
VEH OMIT V V
HOLD H H
PED CALL P P
VEH CALL V
Figure 28 – Inputs Status screen - page 1

This screen shows the status of inputs to the controller, including vehicle omits, holds,
and calls. In addition, the other NEMA input functions are shown. These screens are
very useful for observing the actual state of the inputs in relationship to the general
operation of the controller.
Paging down again will display pages 2 and 3 of the Input Status screens. For ring
and machine inputs, an ‘X’ indicates that the input is active.
PG2 ** RING INPUTS **
FUNCTION 1 2 3 4 FUNCTION 1 2 3 4
ST TIME RED OMIT
INH MAX X X PED RECY X X
MAX II FORC OFF
RED RST
Figure 29 – Inputs Status screen - page 2 - Ring Inputs
PG3 ** MACHINE INPUTS **

EX STRT WRM X TEST A MODE A
MCE CNA1 X TEST B X MODE B
INT ADV CNA2 TEST C MODE C
RCL ALL IND CTL X
REV PR1 REV PR2 REV PR3 REV PR4
CVS SPARE2 SPARE3 SPARE4
SPARE5
Figure 30 – Inputs Status screen - page 3 - Machine Inputs

The Input Status screens show a variety of abbreviations and labels. This table
explains their purpose and possible values.
Table 18 – Input Status screen key
Label Description
CNA1 Call to non-actuated 1
CNA2 Call to non-actuated 2
EX STRT External Start
FORC OFF Force Off
HOLD H=Hold
IND CTL Indicator Control
INH MAX Inhibit Max Termination
INT ADV Interval Advance
MAX II Max II Timer
MCE Manual Control Enable
MODE A,B and C TS 2 Mode input
PED CALL P=Pedestrian Call
PED OMIT P=Pedestrian Omit
PED RECY Ped Recycle
RCL ALL Recall All
RED OMIT Red Omit
RED RST Red Rest
REV PR1, PR2, PR3, PR4 Reverse phase pair (Lead/Lag)
ST TIME Stop Time
TEST A,B and C NEMA Test input
VEH CALL V=Vehicle Call
VEH OMIT V=Vehicle Omit
WRM Walk Rest Modifier

Dynamic Detector Display Screens

The Dynamic Detector Display screens can be accessed by paging down from the
Inputs Status screens.. The number of Detector Display screens that appear depends
on two things: TS 1 controllers allow up to 32 detectors, while TS 2 controllers can
use up to 64, and the actual number of detectors being used also changes the
number of screens.
There are actually two types of screens in the Detector Display Screens. The first
screen is an overview of the detector connections. The TS 1 version looks like this:
PG1 *** DYNAMIC DETECTOR DISPLAY *** DP1
1 1 1 1 1 1 1
DETECTOR 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
1 - 16
17 - 32
>>PGDN FOR DISPLAY AND STRETCH TIMERS<<

Figure 31 – Dynamic Detector Display screen - page 1 (TS 1)
The TS 2 version of this screen has places for an additional 32 detectors:
PG1 *** DYNAMIC DETECTOR DISPLAY *** DP1
1 1 1 1 1 1 1
DETECTOR 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
1 - 16
17 - 32
33 - 48
49 - 64
>>PGDN FOR DISPLAY AND STRETCH TIMERS <<
Figure 32 – Dynamic Detector Display screen - page 1 (TS 2)
The second type of screen in the Detector Display screens are the detailed detector
screens. Each of these detail screens can show six detectors. The TS 1 version of
the firmware has six of these screens to display all 32 detectors. The TS 2 version
has 13 of these screens. An example:
PG2 ** DYNAMIC DETECTOR DISPLAY ** DP1
NO. IN-OUT MODE STRETCH DELAY ROUTE
1 X X NORMAL 0.0 0.0 1
2 X STR/DEL 5.0 0.0 2
3 X X NORMAL 0.0 0.0 4
4 X STR/DEL 0.0 10.0 8
5 X STP/BAR 3.0 0.0 22
6 NORMAL 0.0 0.0 20
Figure 33 – Dynamic Detector Display screen - page 2 (TS 1 or 2)
In-Out — These detailed screens display six items for each detector. The second and
third columns show the inputs to and outputs from the detector processing module.
An active detector is indicated by an ‘X’. Under normal operation, the inputs and

outputs will match, but when the detector is in a special mode (stretch or delay for
example), the input may be active and the output inactive or vice versa. An ‘F’ next to
one of the detectors in the IN column indicates that the detector is in a ‘Fault’
condition.
Mode — The third column shows the mode that the detector is operating in is
displayed. This value can be Normal, Stretch/Delay, or Stop Bar.
Note Pages 7 through 12 of the Dynamic Display screens are TS 2 only,

(Showing detectors 33 through 64.)
Stretch/Delay — Next to the Mode column are two timers - the stretch and delay
timers. If the detector is in the stretch mode, the stretch timer will begin to time when
the call on the detector becomes inactive. Note that during the time when the timer is
timing, the input is inactive, but the output remains active.
The delay timer is similar to the stretch timer, except that it operates in the other
direction. When the input becomes active, the delay timer begins to time and the
output does not become active until the timer expires. If a detector is operating in the
stop bar mode, the stretch timer displays the time left before the stop bar detector is
disconnected.
Route — This value indicates the phases to which the detector is assigned. The
value is a hexadecimal representation of a binary mapping to the 16 possible phases,
with each digit representing the binary state of four phases. For example ‘1’ equals
0000 0001, so the detector is mapped only to phase 1. This is a four digit hex
number, even though the leading zeros are not displayed. So ‘1’ is actually 0001. If
the detector is assigned to all four phases, it is represented by an ‘F’. So a detector
that is assigned to all 16 phases would look like this: FFFF. Some more examples:
Table 19 – Possible Detector ‘Route’ settings
Route Value Binary Representation Meaning
1 0000 0000 0000 0001 Detector is assigned only to phase 1
80 0000 0000 1000 0000 Phase 8
8000 1000 0000 0000 0000 Phase 16
4000 0100 0000 0000 0000 Phase 15
4002 0100 0000 0000 0010 Phases 2 and 15
204 0000 0010 0000 0100 Phases 3 and 10
F 0000 0000 0000 1111 Phases 1 through 4
F001 1111 0000 0000 0001 Phases 1, 13, 14, 15, and 16
FFFF 1111 1111 1111 1111 Phases 1 through 16

I/O Configuration Status Screens

The I/O Configuration Status screens are accessed by paging down from the Detector
Status screen. These screens vary greatly depending on the type of controller, and in
the case of a TS 2 Type 2 controller, the I/O mode that is selected.
I/O Configuration Status Screens for TS 1 Controllers

The 3000 Controller automatically configures itself for the input/output hardware that
is installed. The I/O Module Configuration screen provides a diagnostic tool to show
the user what hardware the controller has recognized. Four items are displayed. First
is the basic A, B, and C modules (2, 4 or 8 phase). Then the type of D module (if any)
is displayed. Finally, if an overlap card or EEPROM module is present, they are
indicated here.
I/O MODULE CONFIGURATION
BASIC A,B,C MODULE: MS A, B, & C

D MODULE TYPE: PE, COORD & TBC
OVERLAP CARD INSTALLED: NO
EEPROM CARD INSTALLED: NO
Figure 34 – I/O Module Configuration screen (TS 1 or TS 2 Type 2)

The above shows the most typical configuration of I/O modules.
I/O Configuration Status Screens for TS 2, Type 2 Controllers

The 3000 Controller automatically configures itself for the input/output hardware that
is installed. The I/O Module Configuration screen provides a diagnostic tool to show
the user what hardware the controller has recognized. Four items are displayed. First
is the basic A, B, and C modules (2, 4 or 8 phase). Then the type of D module (if any)
is displayed. Finally, if an overlap card or EEPROM module is present, they are
indicated here.
BASIC A,B,C MODULE: MS A, B, & C

D MODULE TYPE: PE, COORD, & TBC
Figure 35 – I/O Module Configuration screen (TS 1 or TS 2 Type 2)

The above shows the most typical configuration of I/O modules.

I/O Configuration Status Screens for TS 2, Type 1 Controllers

On TS 2 Type 1 controllers, there are three screens of I/O Configuration data rather
than just the one shown for TS 1 and TS 2 Type 2 controllers.
BASIC A,B,C MODULE: TYPE 1

D MODULE TYPE: TYPE 1
Figure 36 – I/O Module Configuration screen (TS 2 Type 1)

In addition to the slightly modified main I/O Module screen, a Type 1 controller also
shows two additional screens:
OUTPUTS: TYPE 1 (1 OF 2) (X = ON)
PE 1 2 3 4 5 6 UD 1 2 3
C2 C3 S2 S3 O1 O2 O3 FR UCF
X
Figure 37 – I/O Module Configuration screen - Page 1 (TS 2 Type 1)
This screen indicates functions not found in the TS 1 and TS 2 Type 2 software.
Table 20 shows the definitions of the abbreviations used on this screen.
INPUTS: TYPE 1 (2 OF 2) (X = ON)
PE 1 2 3 4 5 6 DIM TBC LFL MMU ALM 1 2
C2 C3 S2 S3 O1 O2 O3 FR UCF
Figure 38 – I/O Module Configuration screen - Page 2 (TS 2 Type 1)

Table 20 – I/O Module Configuration Status screen key

ALM Alarm 1-2 Inputs
C Cycle outputs/inputs
DIM Dim Signal Outputs
FR Free Outputs/inputs
LFL Local Flash Input Status
MMU Monitor Flash Input Status
O Offset outputs/inputs
PE Preempt 1-6 outputs/inputs
S Split outputs/inputs
TBC Go To TOD Mode of Operation
UCF Flash outputs/inputs
UD TOD user defined 1-3 outputs/inputs
Mode I/O choice 0-7 plus free depending on I/O Mode Inputs A, B, and C as specified
by NEMA Standard Publication No. TS 2 standards. The Help screens for these
displays show each Pin # Mode, also specified by the NEMA TS 2 standards of 2003.
.

D Module I/O Status Screens

The D Module I/O Status screen is accessed by paging down from the Alternate
Controller Status screen.
If an optional D Module is installed in the controller, the active inputs and outputs are
displayed on this screen. This can be an effective diagnostic tool if outputs are not
being activated when they should or inputs do not produce the expected results. By
examining this screen, the user can at least see which inputs the controller is
recognizing and the outputs that it is activating.
The first of the four screens show the D Module Outputs:
D MODULE OUTPUTS (1 OF 4) (X = ON)

D25# (PE01)23 (PE02)21 (UD1)22
D37# 37 3 2 1 20 21 22
UD2-UD4 PE03-6
C2 C3 S2 01 02 03 FR FL
D37# 32 34 33 24 31 5 25 30
COORD X
Figure 39 – D Module Status screen - page 1
The remaining three screens show the D Module Inputs:
D MODULE INPUTS (2 OF 4) (X = ON)
D25# 6 7 8 9 10 11 12 13
DET 9-16
CIR CON# A S b a Z Y M L
DET 17-24
D25# 1 2 3 4 5 17
pe 1-6
D25# (GRP2)25 (XPED)24 (CBFL)15 (UCF)14
D25# (DIM)18 (TBC)20 (FREE)19 (RTCR)16
A1 TC A5 A8 A7 A6 RC A4
D37# 10 13 12 8 11 9 15 16
ALARM

CIR CON# K L H G X W T B
D37# 28 29 35 36
DET 25-32
CIR CON# R(FL ST) P(MON FL)
D37# 4 6
Note The format of these D Module Status screens vary depending on the type of
D module installed in the machine. The D module I/O can only be used by the TS 1
and TS 2-Type 2, I/O Mode 7 software. Several D Module variants are described in
Appendix C, on page 446.
NEMA standards define I/O Mode 7 as a manufacturer-specific mode.

Coordination Status Screen

If one continues to page down through the 3000 status screens, eventually the
Coordination Status screen will appear. Although not labeled as such, this screen is
designed to provide key status information when the unit is operating in a
Coordinated network of controllers.
A B
LOCAL C3/S01: 35% 50 sec. MASTER: 79

C LOCAL OFST 1: 50 (01= 60) 1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
COLORS r r r G r r r G D
E PERMS P P P P
F FORCES
G HOLDS
COORD STATUS: COORD, Local TOD-Keyboard H
Figure 43 – Coordination Status screen
The Coordination Functions dynamic screen allows the user to watch coordination
related functions, such as cycle counters, offset seeking, sync pulse, permissives,
force offs and holds.
Note This screen can also be accessed directly from the Dynamic Menu by selecting
option 2 , C o o r d F u n c t i o n s .
Note There is a method to place Vehicle and Pedestrian phase calls manually from the
Coordination Status screen. To place vehicle calls on Phases 1-8, press the Up-Arrow
and the corresponding keypad number simultaneously. To place Ped calls on Phases
1-8, press the Left Arrow and the corresponding keypad number simultaneously.
These controls also work on the Primary and Alternate Controller Status screens.
The LOCAL CYCLE/SPLIT (A) is the selected local cycle and split. The local cycle
timer is shown to the right of this timing in percent, then timing in seconds to the right
of that.
The MASTER cycle counter (B) is based at zero offset. The counter is displayed in
seconds if the permissives and phase allocations are programmed in seconds,
otherwise, the counter will be displayed in percent.
The LOCAL OFFSET (C) value is used to indicate the current value of difference
between the local cycle and master cycle zero points. This value will equal the
programmed offset when the unit is in sync. During transition the display will indicate
SEEK OFFSET as it seeks to the programmed offset. This display will also indicate
SYNC PULSE during a sync point. This parameter will be displayed in seconds if the
offsets are programmed in seconds, otherwise it will be shown in percent.

Note that the actual offset may differ from the programmed offset (even while not
offset seeking) when using end of main street mode. This is because the displayed
offset is the offset to the main street force off point, not the end of main street green.
For example, “(01=60)” above indicates that Offset 1 is programmed for 60 seconds
and Local (or Actual) Offset in effect is 50 seconds. This difference is from CNA
Coord Phases with Ped Clear = 10 sec. in order to reference to end of green instead
of end of walk when “End of Main Street” is enabled.
The PROGRAMMED OFFSET is shown in parenthesis to the right of the dynamic
offset value.
The phase colors are indicated in real-time, along with phase and ped permissives,
force offs and holds. Permissives will indicate ‘V’ for vehicle permissive and ‘P’ for
ped/vehicle permissive. A ped permissive can only be active if a vehicle permissive is
also active at the same time for a given phase.
The COORD STATUS, the origin and mode of coordinated operation, is displayed at
the bottom of the screen.

Table 21 – Coordination Status screen key

Callout Display Definition
A LOCAL Local cycle & split in effect. Local cycle timer shown in
CYCLE/SPLIT, percent, then seconds to the right.
TIMERS
B MASTER Cycle counter. Sync Point /Zero Offset reference. Shown in
seconds or percent.
C LOCAL Local offset in effect and current offset value. Shows seek if
OFFSET offset seeking. Programmed offset shown in parenthesis, eg.
(01=10) = Offset 1 is in effect and is set to 10 secs.
D COLORS r=Red
Y=Yellow
G=Green/Don’t Walk
W=Walk
D=Ped Clear
E PERMS V=Vehicle Perm
P=Ped and Veh Perm
F FORCES F=Force Off active for these phases
G HOLDS H=Hold active for these phases
H COORD Origin/Mode of coordinated operation
STATUS COORD, TIME OF DAY
COORD, INTERCONNECT
COORD, TOD OVERRIDE
COORD, COORD FAULT
COORD, Local TOD-Keyboard
FREE, TIME OF DAY
FREE, GOING TO COORD, TOD
FREE, MCE
FREE, GOING TO COORD, INTER
FREE, INTERCONNECT
COORD, TOD REVERT
FREE, TOD OVERRIDE
FREE, TOD REVERT
FREE, PE RUN n ACTIVE
FREE, INPUT OVERRIDE
FREE, UCF (DROP CVM)
FREE, SOFT FLASH
FREE, FLASH EXIT ERROR
FREE, STOP TIME
FREE, COORD FAILURE
FREE, COORD OUT OF STEP

Time of Day Status Screen

If one continues to page down through the 3000 status screens, past the Coordination
Status screen, the Time of Day status screen will appear. This screen is designed to
provide the current status of TOD operations.
TIME OF DAY STATUS 08/03/2005 17:28:56

CLOSED LOOP :C/O/S= 1/3/05
( ) ( ) ( )
CYCLE TIMER: 27 INTERRUPTER: NONE
(REFERENCE CYCLE 1 TIMER)
WEEK PLAN DAY PLAN C/O/S
4 2 5/3/2
DAY OF WEEK= WEDNESDAY WEEK OF YEAR= 32
Figure 44 – Time of Day Status screen
option 3 , T o d F u n c t i o n s .
The cycle timer is displayed counting down in seconds. The week plan and day plan
in effect are shown along with the cycle-offset-split. An interrupter counter is also
displayed if the offset interrupter has been configured to be active in the Sync
Reference portion of TOD programming (Note: Offset interrupter is used for hard-
wired interconnect systems.) The date and time are displayed along with the
currently active day of week and week of year.
If no TOD program is active, this display will indicate the default values of week plan
1, day plan 1, and c/o/s=1/3/2. In such a case, a 60 second timer is displayed for the
cycle timer.
Additional information is displayed on this screen if Closed Loop is functioning,
including the closed loop COS.
Note The reference cycle timer indicates the cycle number being used by the TOD Sync
Pulse References (Choices 1-6).
Paging down from this screen will take the operator to a set of screens that show the
current state of all of the TOD circuits.

TOD Dynamic Circuits Status Screens

The status of all 255 Time of Day circuits can be displayed by using the PGUP and
PGDN keys in the status screen list. They start just below the main Time of Day
Status screen.
There are 16 TOD circuit status screens, each displaying 16 circuits.
TOD DYNAMIC CIRCUITS 17:30:43

CIRCUIT 1 2 3 4 5 6 7 8
FUNCTION CY2 CY3 CY4 SL2 SL3 OF1 OF2 OF3
STATUS X X X
CIRCUIT 9 10 11 12 13 14 15 16
FUNCTION OF4 OF5 FRE RFL TP1 TP2 TP3 TP4
SPARE5 X
Figure 45 – Time of Day Dynamic Circuits screen - page 1
option 3 , T o d F u n c t i o n s and using P G D N to step through the 16 screens.
For each of the 255 circuits, the circuit number and a three character reference tag
are displayed. In firmware build v408 and lower, an 'X' below these indicates that a
particular circuit is currently active, while a blank indicates it is not active. This does
not include overrides. In the version 409 firmware and higher, this display has been
modified to show a bit more information. To better see the true ‘state’ of each time of
day circuit, these now display a code:
Table 22 – TOD Dynamic Circuits Status codes
Code Definition
O The circuit was set to ‘ON’ via central override
o The circuit was set to ‘OFF’ via central override
M The circuit was set to ‘ON’ manually via the keyboard
m The circuit was set to ‘OFF’ manually via the keyboard
X The circuit is ‘ON’ naturally by the TOD Day Plan selection

(blank) The circuit is ‘OFF’ naturally by the TOD Day Plan selection
Hit the HELP button or refer to Appendix A on page 430 for details concerning TOD
circuit assignment and definition.

Preemption Status Screens

The three Dynamic Preemption Status screens allow the user to watch the current
preemption run in operation, including outputs, timers, and other values, and to view
the status of all six available preemption runs. There are three screens of preemption
information, labeled ‘PG 1’, ‘PG 2’, and ‘PG 3’ in the upper left corner of the screen.
The first dynamic screen shows information regarding the current preempt run. The
user will see the preempt run id #, along with the run duration timer, current interval
and interval timer. The output states of all vehicle, pedestrian, and overlap signals
are also displayed here.
PG 1 ACTIVE RUN 1 DURATION TIMER 15.4

INTERVAL: 1 INTERVAL TIMER: 4.5
QUEUE: 1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
PED HEAD D W D D D W D D
VOL HEAD R R R R R R R R
POL HEAD D D D D D D D D
Figure 46 – Preemption Run Status screen - page 1
Note Preemption runs can be activated from any of the three Dynamic Preemption
Status screens by holding shift and pressing the 1 through 6 buttons to activate
the corresponding preemption runs 1 through 6.
Paging down from the first Preemption status screen will take you to the other two.
The second and third dynamic screens (accessed by pressing PGDN ) show
information on the current run in progress, as well as information on the other
preemption runs. See Table 23 on page 60 for more details about the information
displayed on these screens.
PG2 PREEMPT CONTROLS 1 1 1 1 1 1 1

FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
COLORS r G r r r G r r
HOLD/FO
P/V OMIT
P/V CALL
RED REST
PREEMPT STATUS: Not In Preempt

Here is a sample of page 3 of the preemption status screens.

PG 3 RUN 1 2 3 4 5 6
INPUT M K D D D D
PRIORITY 2 1 3 4 5 6
RECOGN TMR 0 0 0 0 0 0
DELAY TMR 0 0 0 0 0 0
RESERVE TMR 0 0 0 0 0 0
EXTEND TMR 0 0 0 0 0 0
FAIL TIMER IN SECONDS: 0
Table 23 – Key to the Preemption Status screens

Label Description
ACTIVE RUN # Which of the six available preemption runs is currently being serviced
INTERVAL The interval within the preemption run that is currently being serviced
DURATION TIMER Starts at the first non-fixed interval and counts down the time from the
Duration setting on the Per-Run Times screen. The controller must stay
in preemption at least until this time expires.
INTERVAL TIMER Countdown timer showing number of seconds until current interval ends
QUEUE A listing of preemption calls waiting, in the order they will get serviced
VEH HEAD Vehicle signal
R = Red
Y = Yellow
G = Green
VOL HEAD Vehicle overlap signal
R = Red
Y = Yellow
G = Green
PED HEAD Pedestrian Signal
D = Don’t Walk
W = Walk
P/C = Ped Clear
POL HEAD Pedestrian Overlap Signal
D = Don’t Walk
W = Walk
P/C = Ped Clear
COLORS Shows the current color displayed by the vehicle phases of the currently
running preemption.
R = Red
Y = Yellow
G = Green
HOLD/FO Indicates if a hold or force-off is active for this phase within the
preemption.
H = Hold
F = Force Off

Label Description
P/V OMIT Pedestrian/Vehicular omits.
P = Ped Omit
V = Vehicle Omit
B = Both Ped and Veh Omits
P/V CALL Pedestrian/Vehicular Calls.
P = Ped Call
V = Vehicle Call
B = Both Ped and Vehicle Calls
C = CNA (Call to Non-Actuated)
RED REST X indicates the phase is in Red Rest.
PREEMPT STATUS Displays one of the following status messages about the current
preemption run: “Not In Preempt”, “Going to Preempt Run X”, “In
Preempt Run X”, “Leaving Preempt Run X”, or “Releasing Preempt Run
X”.
INPUT Shows the input state for each run can show any of these single-
character values:
D = run disabled in database
K = keyboard preempt
X = field input active
E = input artificially extended (ie, railroad)
R = input recognition debounce (ie, railroad)
M = input locked in memory until serviced
F = failed preempt input
‘ ‘ = blank when none of the above exist, i.e. the run is enabled, but
there are no calls or special conditions on the input
PRIORITY Shows the priority level for each run that will be used to prioritize
preemption calls in the case of multiple calls at once.
RECOGN TMR Recognition Timer. A timer indicating the recognition of a debounced
input (Railroad = Y)
DELAY TMR If a delay has been programmed for this run, this shows the countdown
timer for the delay.
RESERVE TMR This shows the time count-down of the re-service timer, or the amount
of time following a preemption run that must expire before preemption
can be re-serviced.
EXTEND TMR Timer indicating the extension of an input (e.g. Railroad = Y)
FAIL TIMER IN The current value of the Fail Max Time counter. (Refer to the Fail Max
SECONDS Time setting on the second Per Run Options screen. See page 302.)
The Preemption Run Duration status screens are the bottom of the connected list of
status screens for the 3000 and 3000E controllers. The other status screens
described in the next sections can be accessed from the Dynamic Menu.

COORDINATION FUNCTIONS SCREEN

This screen is described in the Additional Status Screens section, since it can be
accessed by paging down from the main controller status screen. Refer to
“Coordination Status Screen” on page 54.
TIME OF DAY FUNCTIONS SCREENS

This screen is described in the Additional Status Screens section, since it can be
accessed by paging down from the main controller status screen. Refer to “Time of
Day Status Screen” on page 57.
PREEMPTION FUNCTIONS SCREENS

These screens are described in the Additional Status Screens section, since they can
be accessed by paging down from the main controller status screen. Refer to
“Preemption Status Screens” on page 59.

Voltages Screen
VOLTAGES SCREEN
Item 5 on the Dynamic Menu displays a set of current electrical parameters within the
3000 Series controller.
BATTERY = 3.5 VOLTS

INTERNAL 8v = 8.5 VOLTS
24V SUPPLY CURRENT = 0.1 AMPERE
UNREGULATED 25V = 29.9 VOLTS
HIGH REGULATED 25V = 25.4 VOLTS
INTERNAL 24V = 24.5 VOLTS
EXTERNAL 24V = 25.4 VOLTS
Figure 49 – Voltages screen
The electrical properties described, and the normal ranges for these, are listed in
Table 24.
Table 24 – Key to the Voltage screen
Parameter Definition Min Max
Battery Internal Battery for RAM backup and 2.5 VDC 3.5 VDC
real time clock
Internal 8V Internal 8V generated by power 7.5 VDC 9.0 VDC
supply as controller 5V source
24V Supply Current Draw on the 24 volt supply 0 amps 1 amp
Unregulated 25V Power Supply generated voltage for 28 VDC 32 VDC
24 volt supply
High regulated 25V Unregulated voltage source after the 22 VDC 27 VDC
regulator
Internal 24V 24 volt internal source 22 VDC 26 VDC
External 24V 24 volt external source 22 VDC n/a
To return to the Dynamic Menu from the Voltage screen, press the MENU button.

OVERLAP FUNCTIONS STATUS SCREENS

Previously, Option 6 on the Dynamic Menu opened a screen that displayed the
jumper settings on an overlap card inside the controller unit. However, overlap cards
are rarely used now that overlap programming is included directly in the firmware. So
this option now displays the overlap outputs and timers, as well as the state of all
vehicle and pedestrian phase outputs.
Overlap A Timers 1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7
8 9 0 1 2 3 4 5 6
V OUTPUT R G R R R G R
R
P OUTPUT D D D D D D D
D
VOL HEAD R R R R R R R
R R R R R R R R R
Green: Ø.Ø Delay: Ø.Ø
Yellow: Ø.Ø Red Revert: Ø.Ø
Red: Ø.Ø Advance Warning: Ø.Ø
Figure 50 – Overlap Functions Status screen
The six values shown at the bottom of the screen show the current timing counter for
each parameter of this particular overlap. The three lines of status show the current
color of the Vehicle output, the pedestrian output, and the vehicle overlap head
output.
Use the PGUP and PGDN keys to navigate to the same screens for the rest of the
sixteen available overlaps. To return to the Dynamic Menu from the Overlap
Functions screen, press the MENU button.

Program Level & Revision Screen
PROGRAM LEVEL & REVISION SCREEN

Option 7 on the Dynamic Menu provides information about the current firmware
running in the controller.
TS2 TYPE 2 MODE 7
3000 Series Controller

8216A 3.6.7 build 409 (c) 1993-2009
Peek Traffic Corporation
INTERSECTION: PARK AVE & BROADWAY
Figure 51 – Program Level & Revision screen
This Program Level & Revision screen is the same as the controller's start-up screen.
The Peek Traffic logo is displayed, along with the software revision level and build
number. The copyright message and intersection name, if programmed, are also
displayed.
To return to the Dynamic Menu, press the MENU button.

LOG MENU
The Log Dynamic Menu allows a user to access the available data logs gathered
during controller operation, including: measures of effectiveness (MOE),
volume/occupancy, events, keyboard activity, detector failures, pattern changes and
MMU faults.
LOG DYNAMIC MENU
1.MOE LOG 4.EVENTS

2.VOL/OCC 5.KEYBOARD
3.DETECTOR FAILURES 6.PATTERN CHANGE
7.MMU FAULT LOG
Figure 52 – Log Menu

Logs are available as a single, rolling log over a number of days. Log sample periods
are setup under Comm/system setup, log data (MM-3-5-5). Logs are enabled to
record by TOD circuits 125 (volume) and 126 (MOE).
MOE Log
The Measure of Effectiveness log is recorded in 0 to 60 minute increments. There are
4 different types of MOE's for phases 1-8.
The heading of the first display of measures of effectiveness shows the current mode
of operation and the number of cycles during the displayed period.
MOE LOG PERIOD: 5 ENTRY 1 OF 95

MODE: SYSTEM OP 4/3/13 CYCLES: 9
FUNC\PH 1 2 3 4 5 6 7 8
AVG GRN 18 41 22 22 18 41 24 22
The first log shows green
MAX GRN 13 36 18 22 13 36 18 22 time operation and stop
GRN UTL% 127 58 112 93 127 58 93 93 time delay
STP-DEL 30 0 74 71 37 0 73 71
>>PGDN<< DATE: 4/20/00 TIME: 14:50
Figure 53 – MOE Log - type 1

MODE: SYSTEM OP 4/3/13 CYCLES: 9
FUNC\PH 1 2 3 4 5 6 7 8
WALKS 0 9 0 0 0 9 0 0
The second log shows
GAP-OUTS 0 3 0 0 0 3 0 0
phase terminations and
FORCES 2 6 4 6 2 6 4 3 walks
MAX-OUTS 7 0 5 3 7 0 5 6
>>PGDN<< DATE: 4/20/00 TIME: 14:50
Log Menu
The third type uses detector headway and occupancy calculations.

DETECTOR 1 2 3 4 5 6 7 8
OCCUP’Y 0 0 0 0 0 0 0 0
HWAY(.1) 0 3 0 0 0 3 0 0
DETECTOR 9 10 11 12 13 14 15 16
OCCUP’Y 0 0 0 0 0 0 0 0
HWAY(.1) 0 3 0 0 0 3 0 0
>>PGDN<< DATE: 4/20/00 TIME: 14:50
The fourth MOE Log screen is for speed traps using two detectors.

MODE:SYSTEM OP 4/3/13 CYCLES: 9
SPEED TRAPS 1 2 3 4
LEADING DET 0 0 0 0
TRAILING DET 0 0 0 0
DISTANCE 0 0 0 0
AVE SPEED 0 0 0 0
>>PGDN<< DATE: 4/20/00 TIME: 14:50
Table 25 – Key to the MOE Log screens
Term Description
PERIOD Number of minutes of period, based on MM-3-5-5
setup.
ENTRY The number of this entry. A different value can be
typed in to jump ahead many periods instead of
paging down.
PLAN IN EFFECT and number indicates COS if any; number of complete cycles
of cycles over period.
AVE GRN Average length of green, in seconds.
MAX GRN Green time allowed based on allocation.
GRN UTL %
STP DEL Average time to service an actuation.
WALKS, GAP-OUTS, FOR- Number of times each termination occurs over
CES, MAX-OUTS period.
OCCUPANCY % of time the detector has a vehicle in its sensor
field occupied over the period.
HEADWAY average length of time in tenths of seconds be-
tween successive detections (vehicles) over
period.
In all cases, press the MENU button to return to the Logs Menu.

Volume/Occupancy Log
The volume-occupancy log contains raw volumes and occupancy data for the first 32
detectors, averaged over 0-60 minute intervals. The user can view time intervals by
paging down to the desired date and time in the upper right corner of the screen.
VOL/OCC/LOG PERIOD: 1 PAGE 1 OF 24

DATE: 5:14/00 TIME 11:10
DET 1 2 3 4 5 6 7 8
V 0 0 0 0 0 0 0 0
O 0 0 0 0 0 0 0 0
DET 9 10 11 12 13 14 15 16
V 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0
Figure 57 – Volume/Occupancy Log screen
Press the SHIFT and Î keys at the same time to view log data for detectors 17
through 32 (TS 1 and TS 2). (TS 2 detectors 33 through 64 are not available in
volume/occupancy logs.)
Press MENU to return to the Log Menu screen.
Detector Failure Log

The detector failure log allows the user to view the status and failures of the 32 TS 1
and 64 TS 2 detectors. Four types of failures are logged: absence (no calls for the
specified time), locked (continuous ON the specified time), erratic (chattering), and
minimum presence (pulse too short.)
DETECTOR FAILURE LOG PAGE 1 OF 3

DET#...FAILURE MODE DATE TIME
22 -- RETURN TO NORMAL 6/05/05 08:34
22 -- ABSENCE 6/04/05 17:42
16 -- RETURN TO NORMAL 5/31/05 02:19
2 -- OPEN LOOP 5/30/05 01:17
2 -- RETURN TO NORMAL 5/30/05 01:05
Figure 58 – Detector Failure Log screen

If the detector returns to normal operation, this is also logged. This log is a ‘rolling log’
as opposed to the yesterday and today type of log. This means that only the 204 most
recent events will be stored; when event number 205 occurs, it will overwrite event
number 1. The user can view any page directly by entering the page number at the
top of the screen.
Additional log failures are available in TS 2. They are retrieved directly from the
diagnostic function of the TS 2 detectors via the Detector BIU(s). Those failures are:
Open Loop, Shorted Loop, Excessive Inductance Change and Watchdog Failure. As
per the NEMA TS 2 (2003) standard, an Open Loop is reported when the terminal
inductance is greater than 2500 μH. A Shorted Loop is reported when the terminal
inductance is less than 50 μH. An Excessive Inductance Change failure will be

Log Menu
reported if the inductance at the terminals changes by my than 25% in either

direction.
Press MENU to return to the Log Menu screen.
Event Log
The event log displays the last 300 events (such as monitor flash or preemption) that
have occurred in the controller. This is a ‘rolling’ log, meaning that when the end of
the table is reached, data will begin writing over the beginning of the table, i.e. event
number 301 will overwrite event number 1.
EVENT LOG PAGE 1 OF 10

S/MESSAGE DATE TIME
POWER UP 6/05/05 16:33
POWER DOWN 6/05/05 16:30
DETECTOR FAILURES LOGGED 5/31/05 15:53
EEPROM FAILURE 5/31/05 15:53
START-UP SEQUENCE ERROR 5/30/05 15:41
CABINET DOOR OPEN 5/30/05 15:35
Figure 59 – Event Log screen
To directly access a specific page of the log, enter the page number in the upper
right-hand corner of the screen. When an event has been reported to central (through
a log upload), a ‘+’ will appear in the leftmost column next to that event entry.
These types of events are logged to the Event table for both TS 1 and TS 2
controllers.
Checksum failure Bad Cabinet Door Switch
Manual Control Enable Active Watchdog Failure
Monitor Flash I/O Failure
Uniform Code Flash Startup Failure
Uniform Code Soft Flash Preemption Active at Startup
Time-of-Day Soft Flash UCF Active at Startup
Cabinet Flash EEPROM Module Failure
User Defined Alarms 1 - 8 Local (controller) Flash
Preemption Active MMU Flash TS 2 only
Detector Failure MMU Failure
Self Test Diagnostic Failure
Coordination Failure
Cycling Failure
Cabinet Door Open

On TS 2 controllers, these additional events are also logged:
TYPE 2 I/O MODE BAD MMU FIXED

TYPE 2 I/O MODE FIXED FRAME 18 FAILURE
MMU FRAME 128 BAD FRAME 18 FIXED
MMU FRAME 129 BAD CYCLE FAULT
MMU FRAME 131 BAD COORD ACTIVE
BIU 1 FRAME 138 BAD COORD FAULT
BIU 2 FRAME 139 BAD COORD FAILURE
BIU 3 FRAME 140 BAD MMU CVM FAILURE
BIU 4 FRAME 141 BAD MMU 24V1 FAILURE
BIU 9 FRAME 148 BAD MMU 24V2 FAILURE
BIU 10 FRAME 149 BAD MMU CONFLICT
BIU 11 FRAME 150 BAD MMU RED FAILURE
BIU 12 FRAME 151 BAD MMU FIELD CK FAULT
BIU 9 FRAME 152 BAD MMU BND FAULT
BIU 10 FRAME 153 BAD MMU DUAL-GY FAULT
BIU 11 FRAME 154 BAD MMU WATCHDOG FAULT
BIU 12 FRAME 155 FIXED MMU YEL+RED FAULT
MMU FRAME 128 FIXED MMU DIAG. FAILURE
MMU FRAME 129 FIXED MMU MIN CLR FAULT
MMU FRAME 131 FIXED MMU PORT1 FAILURE
BIU 1 FRAME 138 FIXED MMU CVM FIXED
BIU 2 FRAME 139 FIXED MU 24V1 FIXED
BIU 3 FRAME 140 FIXED MMU 24V2 FIXED
BIU 4 FRAME 141 FIXED MMU CONFLICT FIXED
BIU 9 FRAME 148 FIXED MMU RED FAIL FIXED
BIU 10 FRAME 149 FIXED MMU FIELD CK FIXED
BIU 11 FRAME 150 FIXED MMU BND FIXED
BIU 12 FRAME 151 FIXED MMU DUAL-GY FIXED
BIU 9 FRAME 152 FIXED MMU WATCHDOG FIXED
BIU 10 FRAME 153 FIXED MMU YEL+RED FIXED
BIU 11 FRAME 154 FIXED MMU DIAG. FIXED
BIU 12 FRAME 155 FIXED MMU MIN CLR FIXED
MMU INCOMPATIBLE MMU PORT1 FIXED
COMPATIBILITY FIXED MMU LOCAL FLASH

Log Menu
Keyboard Log
The keyboard log is a record of the last 30 keyboard accesses.
KEYBOARD LOG PAGE 1 OF 6

SECURITY DATE TIME
RESTRICTED 5/30/05 15:36
SUPERVISORY 5/25/05 09:30
SUPERVISORY 4/28/05 11:02
Figure 60 – Keyboard Log screen

This log does not record all keystrokes, but rather only keyboard commands that
require a restricted or supervisor security code to gain access to the database. If no
security code is active, no entry is recorded to the log.
Additional pages may be viewed by using the PGUP and PGDN keys, or as with the
other logs, log pages may be accessed directly by entering the page number in the
upper right portion of the screen.
To return to the Log Menu, press the MENU button.
Pattern Change Log

The Pattern Change Log is a record of the 120 most recent changes in coordination
status, including any transitions from free to coordination.
PATTERN CHANGE LOG PAGE 1 OF 1

C/O/S-MODE FLASH DATE TIME
1/2/01-TOD BY BACKUP ----- 6/13/94 17:23
1/3/01-MASTER CONTROL----- 6/13/94 07:30
FREE-BY COMMAND ----- 6/12/94 18:30
Figure 61 – Pattern Change Log screen

For each entry in the log, the cycle, split and offset are displayed (if coordinated) as is
the reason for running this pattern (TOD, master, etc.).
Additional pages may be viewed by using the PGUP and PGDN keys, or a specific
page can be accessed by entering the page number in the field in the top right corner
of the screen.
To return to the Log Menu, press the MENU button.

MMU Fault Log

If the controller is attached to a data-logging malfunction management unit and it has
a data retrieval path configured through the front ports, the MMU’s fault logs are
visible on the controller on this screen.
MMU FAULT LOG PAGE 1 OF 16

DATE: 8/12/05 TIME: 10:55
FAULT: +24 Volt Monitor I
1 1 1 1 1 1 1
CHANNEL: 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
RED
YELLOW
GREEN
Figure 62 – MMU Fault Log screen
Each fault recorded by the MMU is displayed on a single screen, the most recent fault
shown first and older faults shown on screens that can be accessed by pressing
PGDN .
The top of the screen shows how many faults are in the log, the date and time that
the fault was recorded, and the type of fault that was detected.
The bottom of the screen shows the state of all of the controller outputs at the time
the fault occured.

Checksum Status Screens
CHECKSUM STATUS SCREENS

A checksum is a method that the 3000 series controllers use to verify that the
firmware and programming is still in good order. It indicates that no glitches or
tampering have occurred that would cause logical flaws in the operation of the unit.
The current state of the checksum in the device can be viewed by going to the
D y n a m i c M e n u and choosing option 9 . C h e c k s u m S t a t u s .
The checksum status dynamic display allows the user to see if any checksum failures
have occurred on data in the controller. When data is entered through the keyboard,
by transfer or by any other valid means, new checksums are generated and stored.
The controller is constantly verifying the checksums. If data changes without proper
cause, a checksum failure will occur and the controller will go to flash. “CHECKSUM
FAILURE” will appear on the NORMAL STATUS display.
Once a checksum failure has occurred, the operator needs to go to the Checksum
Status screen and clear the failure. After the checksum failure has been cleared, the
user must perform an external restart (or power interrupt) to restart the controller.
If the checksums are correct after the restart, the controller will operate. If data is bad
and the checksums are still incorrect, the controller will once again report a checksum
failure and go to flash.
Checksum failures can register individually on the controller, coordination, time of
day, preemption, and special databases.
Clearing a Checksum Failure

If a failure occurs, and a checksum error is reported, follow these steps to clear it and
restart the controller:
1. Go to the D y n a m i c M e n u and choose option 9 . C h e c k s u m S t a t u s . If
an error exists, the screen will show something like this:
CHECKSUM FAILURES PRESENT IN THE MACHINE
1. CONTROLLER 4. PREEMPTION
2. COORDINATION
3. TIME OF DAY 6. SPECIAL-OPTIONS
>>CHECKSUM CAN BE CLEARED BY SELECTING A

NUMBER FROM ABOVE, BUT DATA MAY BE BAD<<
Figure 63 – Reported checksum failure screen

2. Clear the checksum failures by pressing each number 1-6 as directed above.
No checksum failures present in

the machine, but the unit will
remain in flash until a restart occurs.
Figure 64 – Cleared checksum screen

3. Restart the machine. If the checksum errors have been fixed, it will report:
NO CHECKSUM FAILURES PRESENT
Figure 65 – No checksum failures detected
Special Case Checksum Errors

In addition to the normal data categories, checksum failures can occur on options
programmed under the SPECIAL Menu. An example would be programming the use
of the EEPROM without an EEPROM present in the machine. If this task was
performed, the intersection would flash and the checksum dynamic screen would
display:
NO CHECKSUM FAILURES PRESENT
EE PROM BAD OR NOT PRESENT
Figure 66 – Special errors reported on the Checksum Error screen

Comm Status Screens
COMM STATUS SCREENS

The 3000 Controller also contains four communications status screens that allow the
user to understand how communications are operating between the local and a
master, and in general on Ports 2 and 3 of the controller. These are accessed from
the Dynamic Status Menu by pressing SHIFT -0 and using the PGUP and PGDN keys to
navigate between the three screens. To navigate to this screen, use this sequence:
MM > 1.Dynamic Displays > SHIFT -0.Comm.
The first screen is called the Mizbat Dynamic Status screen, which displays the last
command received, the last command transmitted, and the current count on the
master polling timer. Mizbat is the communications protocol used by 3000 Series
controllers, M3000 master controllers, and CLMATS to transmit controller status
information back and forth between the network elements.
Mizbat dynamic status
Last command received : sp

Last command transmitted : nk
Master polling timer : 23.2
Press ONE to remove circuit overrides

from central: no overrides active!
Figure 67 – Mizbat Dynamic Status Screen
The Mizbat values that appear on this screen are described in Table 26. The Master
Polling Timer indicates how long the M3000 has been waiting for a response; its
maximum value is 60 seconds.
From this display the user can also remove any circuit overrides sent from Central.
When the ‘1’ button is pressed, the screen indicates that the central override
command has been cleared, as shown in Figure 68.
Mizbat dynamic status
Last command received : sp

Last command transmitted : nk
Master polling timer : 23.2
Overrides cleared - Press clear key to

continue
Figure 68 – Mizbat Dynamic Status Screen after a cleared override
Overrides can be activated either by an M3000 Master, or by the MATS or CLMATS
central software. These refer to external overrides received via comm and should not
be confused with TOD ckt overrides which are always available through the keyboard.
As indicated on the above display, press the CLE AR button to return to the navigation
screens.
Pressing PGDN from the Mizbat Dynamic Status screen will display the Port 2 and 3
status screens.

Table 26 – Codes that appear on the Mizbat Dynamic Status screen

Code Meaning Code Meaning
ak Acknowledge ox Override Circuit
as Send List of Active Sensors pr Program Revision Return
ca Call Accept rc Read Real-time Clock
cc Central Calling rl Restart Local and Clear Logs
cp Configure Port rm Restart Master and Clear Logs
cr Call Request (Wake up/sleep) rp Restart & Clear Logs Verification
dr Detector Failure Status Reply rr Request Program Revision
ds Detector Failurs Status Request rs Request Sensor Data
ep Restore Port sa Sensors Active
lc Local Calling sc Set Real-time Clock in Remote Unit
lp Load/Remove Password sp Closed Loop Standard Poll Request
lr Log Request to Retrieve sq Closed Loop Standard Poll Response
lt Log Transmit sr Request Status Data
ma Monitor Reply st Transmit Status Data
mb Monitor Request Data vc Request Last Min/Cyc Comp. Chnl Data
mc Master Calling - Special vd Transmit Last Min/Cyc Comp. Chnl Data
me MATS Short Data Request vr Request Last ½ Min Sensor Data
mf MATS Short Data Transmit vt Transmit Last 1/2 Min Sensor Data
mp MATS Standard Poll x7 Switch to 7 bit mode
mr MATS Data Request x8 Switch to 8 bit mode
mt MATS Data Transmit xd Initiate a Database Download
nk Not Acknowledged xe End a Database Download
oc Override Confirmation xp Transmit Password
ol Override Local xs Transmit Sensor Data
om Override Master (or Zone) xt Transfer Database (Upload or Download)
os Override Section xu Upload Database to Central
Paging down from the first Comm status screen (the Mizbat Dynamic Status screen)
will open the Port 2 and Port 3 status screens.
Status comm PORT 2
CD : No Modem : No modem
CTS : No Timer : 0
DTR : Yes Unused : 0
TXBD : 0
RXBD : 0
Figure 69 – Port 2 Status screen

Use the PGDN key to switch to the Port 3 version of this status screen. These screens
cannot be edited in any way; they are simply there to provide feedback on the status
of the two comm ports on the 3000E.

Comm Status Screens
Status comm PORT 3
CD : Yes Modem : No modem

CTS : Yes Timer : 0
DTR : Yes Unused : 23
TXBD : 0
RXBD : 0
Figure 70 – Port 3 Status screen

The top three parameters on the left side of the screen show the communication
signal line states. CD stands for ‘Communications Device’. CTS stands for ‘Clear to
Send’. DTR stands for ‘Data Terminal Ready’. The bottom two (TXBD and RXBD) are
the Transmit Buffer Descriptor (which should always be 0) and the Receive Buffer
Descriptor (which rapidly steps from 0 to 7 and then wraps back to 0.)
Modem – This line displays a status message showing the current state of the device
(assumed to be a modem) connected to the port. The possible messages that can
show up here are listed in Table 27.
Table 27 – Modem Status Messages
Modem Status Notes
DTR LOW/DTR HIGH This switching tells the modem attached to the port to reset. After these
changes happen, the controller sends the modem initialization string that is
programmed. The screen to set the init string is available at MM > 3.Change
Data > 5.Comm/System Setup > 2.Comm Setup > PGDN > PGDN .
INITIALIZING After the initialization string has been sent, but before the modem is back up
and operating under the new settings.
Waiting This is the message displayed when the modem is up and running, and the
controller is waiting for an incoming call.
Answering Displayed when an incoming call has been detected, but normal
communications haven’t been established yet.
Connected Displayed after good communications have been established.
Dialing Ph#1 Displayed when the modem is calling out, using the primary phone number.
Dialing Ph#2 If the Alternate Phone Number circuit is active (TOD circuit 121:’PH2’) and a
Secondary phone number has been entered in the Phone settings screen, then
this number will be tried, but only after ‘Dialing Ph#1’ fails. When this event
occurs, the Modem status line will display this message.
No modem This message appears when no modem is attached to the port, or the modem
is off.
Timer – This countdown timer shows the timeout count when an incoming or
outgoing call is attempted.
Unused – This shows the number of ‘trash’ characters that have been detected in the
communications stream.

UTCS Status Display

A new status display screen was added to the bottom of the Comm Status display list
in 3000 series firmware v3.6.6. This display is used when the controller is configured
to communicate with a UTCS central system. (This configuration is done on the
Comm Setup --> Closed Loop Master/ID screen, see page 347.)
a dynamic display of communications between the controller and the UTCS central
system. The U.T.C.S. Dynamic Display is the last page of the Communications
Dynamic Menu (Main Menu, 1, shift+0, and then page down 3 times). The
appearance of this screen depends on the setting that is chosen for the UTCS
Protocol parameter, on the Closed Loop Master/ID comm setup screen.
If USCS Protocol is set to None, the UTCS Dynamic Display looks like this:
No UTCS Protocol Selected
A UTCS Protocol is selected via MM, 3,5,

1 and using the Y/N key to toggle the
UTCS Protocol field to appropriate value
Figure 71 – UTCS Dynamic Display Screen when UTCS set to None

If USCS Protocol is set to Protocol90, the UTCS Dynamic Display looks like this:
Protocol90 Dynamic Status
HOL:X FLash:X Drop:X Comm: 0 Page: 0

Phase 1 2 3 4 5 6 7 8 | Ring 1 2
Calls X X X X X X X X | Force X X
Omits X X X X X X X X | Inh Max X X
Holds X X X X X X X X | Last Cmd Rx: 0
Spfcs X X X X X X X X | Last Cmd Tx: 0
Figure 72 – UTCS Dynamic Display Screen when UTCS set to Protocol90
In Figure 72, the following items warrant clarification:
HOL — Hold-On-Line
Drop — Local drop. Activated by pressing the Down Arrow key and
deactivated by pressing the Up Arrow key.
Comm — Communication timer that resets with each valid command.
Page — Open page timer.
Spfcs — Special function outputs.
Last Cmd Rx — The most recent command received.
Last Cmd Tx — The most recent command transmitted.

Comm Status Screens
If, on the other hand, USCS Protocol is set to Stamford, the UTCS Dynamic Display
will look like this:
Stamford Dynamic Status
Cmd: 01 00 00 01
Rsp: 22 33 00 00 00 00 00 00 11
Timer: 0
HOL:X Free:X Flash:X
Time Sync:X Yield:X Recall:X
Force Off:R1 R2 Sp Fcns:1 2 3 4 5 6 7 8
Figure 73 – UTCS Dynamic Display Screen when UTCS set to Stamford
In Figure 73, the following items warrant clarification:
HOL — Hold-On-Line
Cmd — Last command received in hexadecimal byte notation starting with the
least significant byte. Each byte starts with the most significant bit.
Rsp — Last response sent to central. Same convention as ‘Cmd’.
Timer — Communications timer that resets with each valid command.
Recall — Applies maximum recall to all phases
Time Sync — Sets controller’s clock to the hour and minute to the pre-defined
Clock Reset user parameters found in the time of day section.
Yield — Removes hold command on the coordinated phases.
Sp Fcns — Special Function outputs
Note To make it easier to view commands in real-time on the MIZBAT Dynamic Display
screen, the ‘Clear’ key can be used to clear the last command transmitted and the
last command received.

TS 2 DYNAMIC HELP SCREENS
BIU Failure Help Screen

The BIU Failure Dynamic Help Screen will only appear if a failure has occurred.
Pressing the Help Button will reveal another screen indicating the failed (non-
responsive) BIU or BIUs.
MMU Flash Help Screen

The MMU Flash Dynamic Help Screen will only appear if the MMU has created a
flash output. Pressing the Help Button will reveal another screen which indicates the
active colors on each channel and the failure conditions.
MMU Incompatibility Help Screen

MMU Incompatibility Dynamic Help Screen will only appear if jumpers exist that are
not required or if additional jumpers are required. Pressing the help button will reveal
another screen which will delineate the specific jumper(s). The screen has limited
space to provide information, so if a large number of jumpers are incorrect, Peek
Traffic Tech Support recommends checking this screen again (after addressing the
jumpers listed first) to be sure that more jumpers are not listed.

Diagnostics
DIAGNOSTICS
When selecting option 4 - DIAGNOSTICS on the Main Menu, a warning will appear.
Read this warning carefully. Diagnostics should never be performed at a live
intersection.
WARNING!!! CONTROLLER IS GOING TO RED

REST FOLLOWED BY FLASHING OPERATION.
>> HIT ENTER IF YOU WISH TO DO SO <<
>> MENU TO CANCEL <<
Figure 74 – Diagnostics Warning screen

After pressing enter, the Diagnostic Menu will appear......
DIAGNOSTIC MENU
1. INPUTS 4. KEYBOARD
2. OUTPUTS 5. RAM
3. DISPLAY 6. EPROM
>RESTART CONTROLLER TO EXIT DIAGNOSTICS<

>>WARNING,CONTROLLER CVM/FVM INACTIVE <<
SELECT TEST
Figure 75 – Diagnostics Menu
To run a diagnostic, choose the number (1-6) of the area you wish to test. After each
test is run, press the MENU button to return to this menu so you can select another
test, if necessary.

MMU STATUS SCREEN

The MMU Status option is available only on TS 2 controllers. The screen can be
accessed by selecting option 5 on the M a i n M e n u of the 3000 Series controller.
MMU FLASH STATUS

1 1 1 1 1 1 1
CHANNELS 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
RED / DW X
YEL / PCLR
GRN / WALK X X
Figure 76 – MMU Status screen

The display indicates the status of a malfunction management unit (MMU), if one is
attached. The second and third lines display the reason why the MMU has put the
intersection into flash. An X next to the channel indications represent an active input
under the channel numbers. See the TS 2 section of the Event Log listing.
Note This screen will not report accurate information if the MMU option is disabled within
the 3000 Series Controller. The MMU setting is configured on the Main Menu >
Change Data > Comm/System Setup > Port 1 Setup screens. The MMU
Enabled option is on page 2 of the Port 1 settings, (press PGDN to access it).

Chapter 3 — Programming Instructions
This section explains the basic strategies of programming a 3000 Series controller for field
operation. The following topics are discussed in detail in this chapter:
First time setup of a 3000 Series controller, on page 84.

Setup procedures, on page 85.
Using the first time setup menus, on page 97.
Use of the Controller Menu for setup tasks, on page 101.
Phase recalls and modes, on page 120.
A discussion of volume density control, on page 139.
Dual entry, on page 143.
Conditional Service, on page 145.
Pedestrian options, on page 147.
Enhanced options, such as dynamic omits and recalls, simultaneous gap outs, etc. on
page 148.

FIRST TIME SETUP OF THE 3000 SERIES CONTROLLER
Introduction
The 3000E controller has many options and features that will be explained in detail in
the sections that follow. This section, however, defines a basic procedure that is
recommended for ease of set-up. Many applications, such as isolated intersection
control, require only basic set-up and programming and can quickly be set-up by
following this procedure.
This procedure is especially useful for users that have a fundamental knowledge of
traffic controllers and are familiar with basic terminology. It provides a guide for the
order of doing things and the items that are necessary for basic set-up. Refer to the
sections that follow for detailed explanations of individual functions.
Fundamental Requirements for Operation

In order for the 3000 to operate, as a minimum, the following basic functions must be
programmed:
1. The start-up phases and interval (Red, Yellow, or Green)
2. The controller sequence and phases enabled (used), with co-phases
3. Basic phase service functions such as recall modes and lock/non-lock detector
modes
4. Basic phase timings such as initial (min grn), passage, yellow, red, walks,
max’s, etc.
Additional Commonly-Used Options

These commonly-used options may also be required:
1. Overlaps (and double clearance overlaps)
2. Ped and vehicle detector assignments other than basic defaults
3. Conditional service operation
4. Dual entry operation
5. Simultaneous gap out programming
Coordination, Time of Day, Preemption

More sophisticated applications may also require Coordination, TOD, and Preemption
functions. Basic guidelines are given for these on page 95, but will refer to more
detailed sections.

Procedures to Set Up a New 3000 Controller
PROCEDURES TO SET UP A NEW 3000 CONTROLLER

The first portion of this section is for setting up a basic 3000E for the first time, or re-
programming from scratch. This should not be confused with editing a pre-existing
unit already running in the field.
Summarized Setup Steps

Setting up a new unit will consist of the following steps in the order shown. Note for
the keystrokes are to access the appropriate screen, where MM = Main Menu, which
can be obtained by pressing SHIFT and MENU, or by successively hitting MENU
until Main Menu appears.
Table 28 – Minimal Requirements For A New Controller
ITEM DESCRIPTION KEYSTROKES
1 Load a default program MM-3-8-1-1-(1-6)
2 Edit the start-up phases and interval MM-3-1-1
3 Edit sequence phases/co-phases MM-3-1-1-PGDN
enabled
4 Edit recall mode phase functions (CNA, MM-3-1-2-1 and/or 2
Min, Max, etc.)
5 Edit phase times MM-3-1-3
Table 29 – Possible Additional (But Commonly Used) Requirements

ITEM DESCRIPTION KEYSTROKES
6 Overlaps MM-3-1-5
7 Ped and vehicle detector assignments MM-3-1-4-1
other than defaults
8 Dual Entry operation MM-3-1-6
9 Conditional service operation MM-3-1-7
12 Simultaneous gap out programming MM-3-1-9-4

Detailed Setup Steps for Minimal Requirements

The following section provides detail to the summarized steps above for minimal
requirements.
Load a Default For Basic Programming

The 3000E unit has a number of pre-programmed defaults for commonly used
phasing such as 2 phase sequential, 3 phase sequential, etc. to 8 phase dual ring.
These can be selected and loaded into the 3000’s operating data base from the
Utilities Menu. It is highly recommended that this approach be used when
programming a new unit. The defaults will likely not exactly match your application but
it will be easier to simply load these then edit as necessary. Use of defaults also
tends to reduce the likelihood of forgetting or leaving out necessary programming.
Finding the Default Load Menu

First find the Main menu by successively hitting the MENU key or by hitting SHIFT-
MENU (hold SHIFT key in while hitting MENU but be sure to press SHIFT first).....
Main Menu
1.Dynamic Displays 4.Diagnostics

2.Read Data 5.MMU Status
3.Change Data 6.First Time Setup
Figure 77 – Locate ‘First Time Setup’ on the Main Menu

From this screen go to the Default Data Load screen by navigating to 3.Change Data
> 8.Utilities > 1. Default Data Load. Select item 1. Controller to load a default timing
plan into the active database of the controller.
Controller Timing Plan to be Loaded 12/56 + 4

1.2 Phase Sequential 4.5 Phase Dual Ring
2.3 Phase Sequential 5.6 Phase Dual Ring
3.4 Phase Sequential 6.8 Phase Dual Ring 12/56 + 34
Figure 78 – Controller default data load

To Implement a Default
Select the phasing scheme that best fits your application by pressing the associated
number 1-6.
Don’t worry if yours is not an exact match—you can always add or delete by editing.
Upon selection the screen will indicate.....
DEFAULT DATA LOADED
PRESS MENU KEY TO EXIT THIS SCREEN
Figure 79 – Screen indicating a default data load

Edit The Startup Phases And Interval

The start-up interval and phases per the default load may already be correct for your
application, however, you should at least access this screen to determine if this is so.
Go to Sequence/Start-up under the Controller Options Menu....
MM-3-1-1...
X = Initialization phase(s). Initialization interval (0=Red, 1=Yel, 2=Grn)

Use 0(Y/N) key to toggle
values Duration of start up flash. Note: this
should be done by the MMU or Conflict
Monitor and set to 0 in the controller.
Seq/Strt-Up (Val=Yes/No) 1 1 1 1 1 1 1
Start-Up 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
Phases X
Interval : 2 | (0=Red, 1=Yel, 2=Grn)
Flash : 0 | (0-255 Secs)
Red : 0.0 | (0-25.5 Secs)
Sequence : 2 | (2=Sr,3=Dr...see help)
-pgdn For Seq. Config & Phase enables
Duration of start up red if initialization

interval is red.
Used only on start-up.
Normal red times after that.
Sequence type: 2 = single ring, 3 = dual ring,

see detailed section for types.
Figure 80 – Editing startup phases and intervals

You can change these values by the using arrow buttons to position the cursor, and
then entering the desired codes.
Note If a ped call is received during the startup phase, the controller only responds to
the call if real times have been entered into the phase’s Walk and Ped
Clearance timing fields. Otherwise, the controller waits to service the ped call
until a phase is reached that can safely service it and for which Walk and Ped
Clearance times have been entered.

Edit Phases Enabled If Default Is not an Exact Match

If there is no default that has the exact phasing desired, then the phasing must be
edited. To do so, page down from the Sequence/Startup screen. In this case, it is
assumed that the basic sequence type will not change (1st page).
For example, suppose it is desired that the phasing be the same as the 5 phase dual
ring default except that phase 3 will be used instead of phase 4 for the side street
(non dual ring street).
MM-3-1-1-PGDN.....
Add 3 and delete 4
SEQUENCE CONFIGURATION
VALUE (YES/NO) 1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
Ring 1 X X X
Ring 2 X X
Ring 3
Ring 4
PgDn for Co-PHASES/XPED
Figure 81 – Sequence Configuration - Ring setup
To do so, move the cursor under phase 3 in ring 1 and hit 0 (Y/N) to toggle it on
(X appears). Next move the cursor to phase 4 in ring 1and hit 0 (Y/N) and toggle it off
(X disappears).
Add 3 and delete 4 in co-phase group 2

Page down to co-phases... .
SEQUENCE CONFIGURATION >>PGDN FOR MORE<<
VALUE (YES/NO) RINGS (0=4) 1 1 1 1 1 1 1
FUNC/PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
RINGS 1 1 1 2 2
CO PH 1 X X X X
CO PH 2 X
CO PH 3
CO PH 4
Figure 82 – Sequence Configuration - Setting Up co-phases
Note The co-phase screen must be edited as well to delete the co-phase assignment of
the deleted phase and add it for the new phase. Failure to do so results in a start-
up error. For a more detailed explanation of co-phases, see page 108.

Edit Phase Functions (Phase Recall Modes)

In the Default mode all phases are actuated (no recalls), so if other recall modes like
min recall, max recall, ped recall, CNA, etc. are required, then they must be so
programmed.
Prior to actual programming, you may wish to review the following chart which
illustrates typical use of recall modes for many common intersections.
Table 30 – Typical Use Of Recall Modes
INTERSECTION DESCRIPTION PHASES RECALL MODE
1. Fully actuated, all phases have Main St. Min recall or Soft recall
detectors, peds actuated (or none), rest or Other ph’s No recall (actuated)
hold* in Main St. green/don’t walk.
2. Fully actuated, peds actuated (or none) Main St. No recall (actuated)
rest in last phase served green/don’t walk. Other ph’s No recall (actuated)
3. Semi-actuated, no Main St. detection, Main St. Max recall
peds actuated (or none) rest or hold* in Other ph’s No recall (actuated)
Main St. green/don’t walk.
4. Semi-actuated, Main St. peds always Main St. Ped rec or CNA (WRM off)
come-up, rest or hold* in Main St. grn/dw. Other ph’s No recall (actuated)
5. Semi-actuated, Main St. peds always Main St. CNA (WRM on)
come-up, rest or hold* in Main St. grn/walk. Other ph’s No recall (actuated)
6. Fixed-timed, no detection, no peds, Main St. Max recall ***
always cycles, hold* in Main St. green/dw. Other ph’s Max recall ***
7. Fixed-timed, no detection, with peds, Main St. Ped recall
always cycles, hold* in Main St. green/dw. Other ph’s Ped recall or max rec
8. Fixed-timed, no detection, with peds, Main St. CNA
always cycles, hold* in Main St. green/walk. Other ph’s Ped recall or max rec
*References to rest indicates how the unit acts when there are no calls. References to hold
indicate how the main street will hold during the hold period if coordination is used. The condition
for both is either in green/don’t walk or green/walk of the phase indicated.
**Operating without any recalls at all is not recommended for coordinated operation. The coord
phases (Main St.) should have some type of recall applied during coordinated operation.
***It is generally considered not good practice to invoke pre-timed operation by setting phases to
min recall and using the initial (min green) time for the full green time. Instead, use max recall
and set the initial to just a base value of 5-15 seconds and use max time I or II for green time.
This is especially important if coordinated operation is to be used.
WRM = Walk Rest Modifier. When active, a CNA phase can rest in Walk even when
hold is not applied if there are no serviceable conflicting calls.

Phase Recalls Edit Procedure

There are two menus under recall modes. One is for Timing Plan Functions like min
recall, max recall, ped recall, etc. Up to 4 sets of these can be programmed and are
selectable by TOD. The other is for once per unit recalls and are mostly for CNA
Modes.
Edit Timing Plan Recall Modes and Other Related Options

The timing plan recall modes include such modes as min recall, max recall, ped
recall, soft recall, lock/non-lock mode, etc. These tend to be the more common
modes for non-coordinated phases, or all phases at free running intersections
(no coord).
Note that these modes can programmed per timing plans 1-4. Thus, alternate
plans can be selected by Time of Day (TOD) or by combination of Cycle, Offset
Split (COS)—thereby selecting a completely new set of recall modes and other
functions.
When no alternate plans are desired, simply program the following modes for
Timing Plan 1 only.
To edit timing plan recall modes go the controller menu, then Phase Recalls/Modes
then Min/Max…;
MM-3-1-2-1.....
Phase Functions (1 of 12)
Value(YES/NO)
Timing Plan: 1 1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
MIN RCL X
MAX RCL
PED RCL
SOFT RCL
NON-LOCK
Figure 83 – Configuring Phase Functions

PGDN ....
Phase Functions
Value(YES/NO)
Timing Plan: 1 1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
VEH OMIT
PED OMIT
WLK REST
MAX II
RED REST
Figure 84 – Configuring Phase Functions - page 2
PGDN ....
Phase Functions
Value(YES/NO)
Timing Plan: 1 1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
NO SKIP
Figure 85 – Configuring Phase Functions - page 3

Enable/disable a function for a phase as desired by moving the cursor to the function
and phase and toggling 0(Y/N). When a “X” is shown the function is enabled for that
phase.
BRIEF TIMING PLAN RECALL DESCRIPTIONS

(see detailed section pg. 122 for full description)
Min Recall - Applies call for initial green only, extends by detector after that.
Max Recall - Applies call for max green. Always times max regardless of SCC∗.
Ped Recall - Applies call for pedestrian service (walk-flashing don’t walk).
Soft Recall - Similar to min recall but only applies call if no other “real” calls.
Non-Lock - Call not locked in memory, det. must be occupied for service.
Veh Omit - Phase omitted when this plan is in effect (no vehicle or ped).
Ped Omit - Ped omitted when this plan is in effect (phase can still be served).
Wlk Rest - Allows ped recall phase or ped actuated phase to rest in walk.
Max II - Calls for Max II timing on phase when this plan is in effect.
Red Rest - Calls for phase to rest in red when this plan is in effect.
∗
SCC = Serviceable Conflicting Call – The phase has opposing call which will require it to clear.

No Skip - Phase called if phase after it is called when this plan is in effect.
Edit Once Per Unit Recalls (CNA Modes, Inh Max, Ped Options)
The first area below is largely used for CNA modes and some other special options.
Skip this section and move to standard recalls if no CNA modes or special ped
options are used.
Note that the following modes are one-time settings, there are no alternate plans
selectable by time of day like the timing plan recall modes (i.e. min recall, max recall,
etc. modes can have alternate TOD plans).
MM-3-1-2-2.....
Value(YES/NO)
1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
CNA 1 X X
CNA 2 X X
CNA 3 X X X X
CNA 4
WRM X X
Figure 86 – Editing Once-Per-Unit Recalls
Note This section is primarily for CNA modes.
Note that the Walk Rest Modifier (WRM) will automatically be applied to phases
enabled by the default load.
PGDN .....
Value(YES/NO)
1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
INH MAX X X
PED RECY X X
FL WALK
FDW->YEL
FDW->RED
Figure 87 – Editing Once-Per-Unit Recalls - page 2
Note that inhibit max (INH MAX) and ped recycle (PED RECY) will automatically be
applied to phases enabled by the default load.
Enable/disable a function for a phase as desired by moving the cursor to the function
and phase and toggling 0(Y/N).

Editing Phase Times

The phase times required for your application may not be the same as in the Default
mode. If they are not, they must be edited.
MM-3-1-3....
TP:1 Phase 1 2 3 4 5 6 7 8
Initial 8 10 0 0 0 0 0 0
Passage 4.0 4.0 0.0 0.0 0.0 0.0 0.0 0.0
Yellow 4.0 4.0 0.0 0.0 0.0 0.0 0.0 0.0
Red 2.0 2.0 0.0 0.0 0.0 0.0 0.0 0.0
Walk 0 0 0 0 0 0 0 0
Ped Clr 0 0 0 0 0 0 0 0
--pgdn for more, SHIFT-> for Ph’s 9-16--
Figure 88 – Editing phase times
PGDN .....
TP:1 Phase 1 2 3 4 5 6 7 8
Max 1 30 30 0 0 0 0 0 0
Max 2 30 30 0 0 0 0 0 0
Mx 3 Lim 0 0 0 0 0 0 0 0
Mx 3 Adj 0 0 0 0 0 0 0 0
--pgdn for more, SHIFT-> for Ph’s 9-16--

Figure 89 – Editing phase times - page 2
Press SHIFT RIGHT ARROW for phases 9 through 16.
Brief Phase Times Description

(see detailed section for full description)
INITIAL -Guaranteed portion of green. Also called minimum green (see note 2)
PASSAGE -Incremental amount by which green is extended by each actuation
YELLOW -Yellow clearance interval
RED -Red clearance interval (all red before next green in ring starts)
WALK -Phase walk time (use 7 seconds or more if walk signals displayed)
PED CLR -Phase Ped Clearance (Flashing Don’t Walk) time (see note 3)
MAX 1 -Normal maximum allowed green due to extensions or max recall
MAX 2 -Alternate maximum selected by clock, input, or plan call (see recalls)
MX 3 LIM-Upper limit to max time due to adaptive max adjustment (see note 4)
MX 3 ADJ -Amount by which max extended after “X” max outs (see note 4)

Notes:
1. Each of the above is programmable in up to 4 plans, each plan selectable by
COS or Clock. Use only plan 1 if no TOD, COS changes are required.
2. For Initial time the typical settings are:
10-15 seconds for main street
5-7 seconds for left turns and commercial exits
6-10 seconds for actuated major side (cross) streets
3. For ped clearance time use X seconds, where X = distance in ft. curb to curb
at the ped crossing divided by 4 ft/sec, or the distance in meters divided by 1.2
meters/sec.
4. Max 3 also requires Max 3, Max/Gap-outs programming, which can be found in
the enhanced menu (Controller MM-3-1-9-5). Also see Max 3 explanation in
the detailed section, page 153.
Setting Up a Coordination Plan

1. Load a coordination default from the Utilities menu (coord only, do not load a
controller default if you have already set controller phasing, times, etc.). Use
the default coord plan that closest fits your application, but don’t worry if the
values and and/or phasing are not exactly the same as your application. These
values can be edited.
2. Use the example at the end of the detailed Coordination Section (pg. 269) as a
guide in editing for your application. Edit all coordination screens shown in the
example as necessary. Observe the CNA note at the end if CNA is required
on the coord phases. Use the Coord check function to verify your work (MM-3-
2-0).
3. Read the descriptions on other specific coordination features and implement
as necessary if the basic example does not fully meet your requirements.
Basic Procedure For Setting Up a TOD Plan

1. Determine how many day plans and week plans will be necessary. Many
applications will consist of just 2 day plans and one week plan (used all year).
This week plan (1) consists of day plan 1 Monday - Friday and day plan 2 on
Saturday and Sunday.
2. Go to the Time of Day menu and load the week and year plan. For example, if
the above case is true, program week 1 with day 1 assigned to M-F and day 2
assigned to Saturday and Sunday. Assign week plan 1 to all 53 weeks of the
year.
3. If daylight savings is used in your area, go to the Daylight Savings menu (MM-
3-3-7) and program the appropriate month and week for Spring and Fall
(program 0’s if DST not used).
4. The standard sync reference mode is the Time Dependent mode with a
midnight reference for all cycles. This is the most commonly used mode, but if

your application is different (sometimes reference times are different), go to the

Sync Reference Menu (MM-3-3-8) and change this now, otherwise go to
step 5.
5. Go to the Day plan menu and program each day plan as required. Use the
Typical Day Plan example in the Time of Day section (pg. 280) as a guide.
Also note that;
An event which turns the Free Ckt (11) off must be included for
coordination to operate. This is to offset the fact that the 3000 Series
controllers turn Free Ckt 11 ON every night at midnight.
Never activate INH MAX by clock event (use only COS/F to TOD CKTs
from the coordination menu if INH MAX is to be used so that it will not be
invoked in Free operation, as a cycling failure will occur.)
Each event is either a CKT PLAN, a COS, or a CKT ON/OFF (not more
than one).
In general, many functions relating to coord (e.g. Max 2, CNA, etc.) can be
either applied via COS/F to TOD CKTs in the coordination menu (MM-3-2-
8), or can be activated strictly on a time of day basis by day plan events.
When COS/F to TOD CKTs are used, the function is not actually
implemented until coordination itself is fully active. Clock event ckt’s are
activated at the designated time and may precede the start-up of
coordination. The implications of this should be considered (this is the
reason for INH MAX note above).
6. After all clock programming is complete, go to the Set Date and Time menu
(MM-3-3-9) and set the date and time. Note that for Time Based Coordination
to operate properly, the clocks of all units in he system must be the same,
within a second or two.
Setting Up a Preemption Run

Refer to the examples at the end of the detailed Preempt section (pg 332).

Using First Time Setup Menus
USING FIRST TIME SETUP MENUS

There is menu process in the 3000 controller that automates the much of what has
been described in this section. It is called the First Time Setup menu and is accessed
from the Main Menu.
Main Menu
1.Dynamic Displays 4.Diagnostics

2.Read Data 5.MMU Status
3.Change Data 6.First Time Setup
Figure 90 – Go to the Main Menu and choose 6.First Time Setup

First Time Setup….
Basic Setup Procedure (Begins next page)
To setup a new 3000 for basic oper-

ation, follow procedures below (Pgdn).
Procedures explain order of things that
need to be done. To go straight to the
menu described, press the number of the
procedure. Clear menu returns you here.
Figure 91 – Basic Setup Procedure screen
This menu explains how to use the procedure.
PGDN ….
1.Load a default (Utilities Menu). Find

closest controller default to your
phasing & load. Load coord if used.
2.Seq/startup (Controller, Seq/Startup

Menu). After default load, edit startup
data & phasing for your intersection.
Add & delete phases on 2nd & 3rd page.
Figure 92 – Basic Setup Procedure screen - page 2
Each procedure description explains what must be done, but the actual task must be
performed in the menu area described.

To go right to that menu, simply press the procedure number key.

For example, press 1….
Utilities Menu
1.Default Data Load 6.Printer Menu

2.Transfer Menu 7.Copy Functions
3.Clear Logs 8.Request Download
4.EEPROM Copy
5.Restart machine
Figure 93 – Press the selection from the Quick Start menu to see topic
The referenced menu immediately appears (Utilities). Once in the menu, execute the
task required. In this case, execute the Default Data Load procedure and load the
desired defaults.
Once the task is complete, press CLE AR - MENU to return to the First Time Setup
procedure. Then go on to the next procedure. Each procedure will go to a different
menu, but CLEAR - MENU will always to return to the First Time Setup menu at the
point last exited.
Note that procedures 1 through 5 are sufficient to set up basic operations, (and 5 is
only needed if CNA is used.) Procedures 6 through 10 are for options that may be
required. More complex functions such as coordination and preemption must be
programmed using the normal menu structure.
Menu Descriptions
Main Menu
The main menu is the base menu from which all other menus are accessed. The
main menu itself can be accessed by hitting the MENU key successively or by hitting
SHIFT-MENU (both keys at the same time).
Main Menu
1. Dynamic Displays 4. Diagnostics

2. Read Data 5. MMU Status
3. Change Data 6. First Time Setup
Figure 94 – Main Menu

Using First Time Setup Menus
Dynamic Display Menu

The dynamic menu provides access to various unit status screens. In general, the
selected screens indicate status of various functions, timers timing, condition of
inputs, etc. The term “dynamic” is used because the screens continuously change
and update as the function status changes. Detailed Dynamic Menu descriptions
begin on page 28.
Dynamic Menu
1. Controller Funcs 6. Overlap Functions

2. Coord Functions 7. Prgm Level & Rev
3. Tod Functions 8. Log Menu
4. Preempt Function 9. Checksum Status
5. Voltages 10. Comm
Figure 95 – Dynamic Menu
Read Data Menu

The Read data menu is a “Read Only.” It is the same menu as the Change Data
menu following except that data parameters can be viewed only and not changed.
The Read Data Menu can be used in conjunction with passwords and restricting
access to menus such that some users have Read Only privileges. In that case, their
password allows access to the Read Data menu, but not the Change data menu.
See page 375.
Change Data Menu

The Change Data menu is the base menu from which all unit programming begins. It
is also called the “Program Menu” since it allows data base parameters to be
programmed.
Change Data Menu (Press 9 for Index)
1. Controller 5. Comm/System setup

2. Coordination 6. Unit Config/Sec.code
3. Time Of Day 7. I/O Steering
4. Preemption 8. Utilities
>Shift-Clear From Data Screens to Index<

Figure 96 – Change Data Menu
Each selection pertains to a related area of the 3000’s data base. Most of the
selections shown above are major categories themselves and will display another set
of sub menus when selected. Each further narrows down the specific area of the data
base. For example, the Controller Menu generally pertains to phase/overlap
sequencing & timing issues, but has 9 submenus to deal with all the related topics.

Diagnostics Menu
The Diagnostics menu is a procedure for testing the unit. It is not a field procedure
and should never be executed at an operating intersection (see page 81).
MMU Menu
The MMU menu is only available when the unit is operating in the TS 2 mode and
port is operational. This display indicates status of field channels “as seen” by the
MMU, i.e. the channel color indications shown are as reported by the MMU via port 1
comm (see page 82).
First Time Setup Menu

The First Time Setup menu is a set of guidelines and procedures for setting up a
3000 for the first time. It explains the minimal requirements to set-up a unit a provides
a direct link to the appropriate programming screens (see page 97).

Using the Controller Menu
USING THE CONTROLLER MENU

To access the controller menu, first select the Main Menu by successively hitting the
MENU key or by pressing the SHIFT and MENU keys simultaneously.
Select Main Menu...
Main Menu
1. Dynamic Displays 4. Diagnostics

2. Read Data 5. MMU Status
3. Change Data 6. First Time Setup
Figure 97 – Main Menu

Then Select 3, Change Data....
Change Data Menu (Press 9 for Index)
1. Controller 5. Comm/System setup

2. Coordination 6. Unit Config/Sec. code
3. Time Of Day 7. I/O Steering
4. Preemption 8. Utilities
>Shift-Clear From Data Screens to Index<

Figure 98 – Change Data Menu
Then Select 1, Controller....
Controller Menu
1.Sequence/Startup 6. Dual Entry

2.Phase Recalls/Modes 7. Cond. Service
3.Phase Times 8. Ped Options
4.Detectors 9. Enhanced Options
5.Overlaps
Figure 99 – Controller Menu

Sequence/Start-up Configuration Screens

Select 1 from the controller menu....
Seq/Startup (val=yes/no) 1 1 1 1 1 1 1
Startup 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
Phases X
Interval : 2 | (0=red, 1=yel, 2=grn)
Flash : 0 | (0-255 secs)
Red : 0.0 | (0-25.5 secs)
Sequence : 2 | (2=sr,3=dr...see help)
-Pgdn for seq. config & phase enables
Figure 100 – Sequence/Startup Configuration Screen - page 1
Start-Up Screen Parameter Definitions

START-UP PHASES - Toggle YES/NO under selected phases, where “X” indicates
enabled phase. Enable phase or phases (must be compatible if more than 1) that will
become active upon controller initialization or when the external start input is true.
The phase color is determined by the start-up interval setting.
START-UP INTERVAL - Code 0-2. Determines the start-up color, 0 = Red, 1 = Yel, 2
= Grn.
START-UP FLASH - 0-255 seconds. This value determines the controller start-up
flash period before the Controller Voltage Monitor (CVM) output is allowed to go to
the good state. Note, however, that it is recommended to program start up flash via
the setting on the Conflict Monitor (or MMU) and not the controller. The controller
flash is usually set to zero.
START-UP RED - 0-25.5 seconds. This red timing occurs only if the start-up interval
is red and only occurs once after initial power-up or external start. Normal red timing
occurs after that.
TYPICAL SETTINGS FOR START-UP PARAMETERS. The start up phase and
interval is usually determined by how the intersection flashes. If the intersection
flashes main street yellow and side street red, then the start-up phase(s) should be
the main street phase(s) and the interval should be yellow or green—where green is
preferable. Start up red has no effect in this case. If the intersection flashes all red,
the start up phase(s) should be the phase(s) immediately preceding the main street
phase(s) and the interval should be red. Start up red is usually set to 3-5 seconds in
this case.
SEQUENCE - 1-9 selects a specific type of sequence from the library of sequences
as follows;
1. Clear sequence. This clears all phases from ring, co-phase and
exclusive ped assignments.
2. 8 phase sequential (single ring). This assigns phases 1-8 to ring 1
and co-phase group 1. The unit will cycle phases one at a time
sequentially.

3. 8 phase quad left (dual ring). This assigns phases 1-4 to ring 1 and 5-
8 to ring 2. Phases 1, 2, 5, and 6 are assigned to co-phase group 1 and 3,
4, 7, and 8 are assigned to co-phase group 2.
4-9 Special sequences. For a description of available sequences hit
HELP from the sequence start-up menu. Hit HELP again to return. Also see
the chart on page 107.
Note Modifications to the sequence only take affect after a controller restart.
Typical procedure for loading sequence information

Since the appropriate sequence for most intersections is a simple sub-set of one of
the Utility Menu defaults or Library sequences, the user usually will need only;
1a. Load a default from the Utilities Menu and then edit phases enabled (used)
by entering the SEQUENCE/START-UP menu and paging down to the phase
enable/disable and ring assignment screen.
or,
1b. Enter the SEQUENCE/START-UP menu directly, select a sequence from the
library and then edit phases enabled (used) by paging down to the phase
enable/disable and ring assignment screen.
2. Page down again to edit co-phases to reflect the new phasing for phases
added or deleted. Failure to do so will result in a start-up error. For many cases
of simple phase addition or deletion, the co-phase programming is simple
addition and deletion within the same co-phase group as well. Review the
detailed co-phase explanations on the next page if co-phase programming
involves more sophisticated re-structuring.
Addition & Deletion of Phases to Preset Configurations

For example, suppose it is desired that the phasing be the same as the 5 phase dual
ring default except that phase 3 will be used instead of phase 4 for the side street.
Add 3 and delete 4

MM-3-1-1-PGDN .....
VALUE (YES/NO) 1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
Ring 1 X X X
Ring 2 X X
Ring 3
Ring 4
PGDN for Co-PHASES/XPED
Figure 101 – Adding and deleting phases from preset configuration

To do so, move the cursor under phase 3 in ring 1 and hit 0 (Y/N) to toggle it on (X
appears). Next move the cursor to phase 4 in ring 1and hit 0 (Y/N) and toggle it off (X
disappears).
Add 3 and delete 4

PGDN to co-phases...

VALUE (YES/NO) RINGS(Ø=4) 1 1 1 1 1 1 1
FUNC/PH 1 2 3 4 5 6 7 8 9 Ø 1 2 3 4 5 6
RINGS 1 1 1 2 2
CO PH 1 X X X X
CO PH 2 X
CO PH 3
CO PH 4
Figure 102 – Adding/deleting co-phases to configuration
Note The co-phase screen must be edited as well to delete the co-phase assignment of
the deleted phase and add it for the new phase. Failure to do so results in a start-
up error. For a more detailed explanation of co-phases, see page 108.
Enhanced Sequence Configuration and Exclusive Ped

In some cases, the required sequence may be more complex or unusual and will
require greater use of the 3000’s sequence capabilities as well as a greater
understanding of the operation.
The 3000 Controller has a library of sequences from which the user can select. Once
a configuration has been loaded, sequences can be modified as desired.
Alternatively, a sequence can be developed from scratch. The sequence library is
shown on page 107. Enter a 1 to clear the currently loaded sequence, or the number
of the desired sequence. Note that the programmed sequence only takes effect
following a restart.
When a sequence is first implemented from the library, all phases (usually 8)
associated with the sequence are automatically loaded along with ring and co-phase
assignments. This only happens when the digit (1-9) is first entered. If then edited by
any of the screens below, the last edited values will remain in effect through power
interruption even though the selection digit will remain displayed.
Caution Be careful when re-entering the sequence number—it will re-load from
library defaults and overwrite any previously edited sequence entries.

Pgdn from start-up programming screen....

Phase Enable/Disable And Ring Assignment
VALUE (YES/NO) 1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 Ø 1 2 3 4 5 6
Ring 1 X X X X
Ring 2 X X X X
Ring 3
Ring 4
PGDN for Co-PHASES/XPED
Figure 103 – Phase enable/disable and Ring assignment

This screen allows phases to be enabled and assigned to rings. A phase is enabled if
an “X” appears below the phase in one of the four rings. A phase is disabled (will not
be used) if no “X” appears below the phase in any ring. The example is an 8 phase
quad left.
Change the phasing as desired by moving the cursor to the phase and ring position
and toggling the 0(Y/N) key to the opposite mode.
PGDN....
Phase Assignment To Co-Phase Groups
VALUE (YES/NO) RINGS (Ø-4) 1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 Ø 1 2 3 4 5 6
RINGS 1 1 1 1 2 2 2 2
CO PH 1 X X X X
CO PH 2 X X X X
CO PH 3
CO PH 4
Figure 104 – Assigning phases to co-phase groups

PGDN for Co-Phase groups 5 through 8

The above screens allow phases to be assigned to rings and co-phase groups. Note
that the ring must be assigned before a phase can be assigned to a co-phase group
or the unit will beep (see rings, barriers & co-phases definition).
PGDN....for Exclusive PED Programming
EXCLUSIVE PED 1 VALUE (YES/NO)
XPED IN N: PED 1: N PED 3: N TOD:N
1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
XPED PH
OUTPUTS
SOFT RET
PGDN FOR EXCLUSIVE PED 2
Figure 105 – Exclusive Pedestrian phase programming
This screen allows exclusive ped programming (see exclusive ped definition page
114).

Library of Default Sequence Diagrams

The library of default sequences are defined as follows:
R1 1 2 3 4 5 6 7 8 R1 1 2 3 4 7 8
R2 5 6
8 phase sequential (code 2)
1234/56 + 78 (code 6)
R1 1 2 3 4 R1 1 2 3 4
R2 5 6 7 8 R2 5 6 7 8
8 phase quad left (code 3) 1234/5678 (code 7)
R1 1 2 3 4 8 R1 1 2 3 4 R3 9 10 11 12
R2 5 6 7 R2 5 6 7 8
R4 13 14 15 16
123/567 + 48 (code 4)
Dual Quad Left (code 8)
R1 1 2 3 4 7 8 R1 1 2 3 4 5 6
R2 5 6 7 8 9 10 11 12
R2
12/56 + 3478 (code 5)
12 phase Six-Left (code 9)
There are 8 possible co-phase groups (8 barriers). Each group contains a set of
phases that are defined as co-phases. The defaults use from 1 to 4 groups.
All necessary ring and co-phase data will automatically appear for selected default
sequences.

Phases, Rings, Co-Phase Groups and Barriers

These definitions describe some of the key concepts important in programming an
intersection controller such as the 3000/E.
Phase — A Phase is one or more movements of traffic given right-of-way at the same
time, with its own position in the sequence and a set of parameters.
Ring — A Ring is two or more phases that must be timed sequentially.
Ring Rule: All phases in a Ring conflict with each other. A phase must be assigned to
one and only one ring.
Co-phase Group — A Co-phase Group is a group of phases that determine if phases
in different Rings are compatible or conflicting.
Co-phase Rule — A set of phases, each in different Rings, are compatible if they are
in the same Co-phase Group. In all other cases, the set of phases are conflicting. A
phase may be assigned to multiple Co-phase Groups.
Sequencing — The phase sequencing process cycles through phases in ascending
order of Co-phase Groups, and by ascending phase number within each Ring of a
Co-phase Group (subject to Lead-Lag adjustments, see Lead-Lag in Enhanced
Options section). After the last Co-Phase Group serves, the sequencing 'wraps' to the
first Co-Phase Group. This process continues forever.
In the active Co-phase Group, the highest-ordered phase with a serviceable call
in each Ring is termed the "barrier phase". If a "barrier phase" is active, the ring
has cycled as far as it can (based on demand) in the active Co-phase Group.
The Phase Sequencer seeks the 'next Co-phase Group' with a serviceable call
on phases that are not in the active Co-phase Group.
When the subset of "barrier phases" that are not in the 'next Co-phase Group'
are green timed out (ie, gap out), the subset of "barrier phases" transfer to
yellow simultaneously to advance to the 'next Co-Phase Group'. The subset of
"barrier phases" that exist in the next Co-phase Group remain green because
they are compatible.
When clearance intervals finish, the new phases in the 'next Co-phase Group'
turn on.
During the "barrier phase" clearance timings, if a ring remains green because it
is in the 'next Co-phase Group', the ring may terminate to serve a newly-
identified serviceable call for a phase in the 'next Co-phase Group'.
The sequencing rules are simple when each of the phases is in one and only one
Co-phase Group. The rules become more complex when individual phases are
assigned to more than one Co-phase Group. This is best explained with three
examples in order of increasing complexity (assuming every phase has a call) shown
below.

Rings and Co-phases Example 1

The key point of this example is to show a simple case where all greens must
terminate when moving to a new Co-Phase Group.
Figure 106 – Rings and Co-phases Example 1

Starting with phases 1/5, the next phases for service are 2/6. The transitions from 1-
>2 and 5->6 occur independently because they are in the same Co-Phase Group.
From 2/6, the next phases for service are 3/7. Because 2/6 are "barrier phases" and
2/6 are not in the 'next Co-Phase Group' c-2, 2/6 terminate together (after both are
timed out) to serve 3/7. The process continues.

The key point of this example is to illustrate how all greens do not always terminate
when moving to a new Co-Phase Group.

Starting with phases 2/5, the next phase for service is 6. The transition from 5->6
occurs while phase 2 is timing because 2/6 are in the same Co-Phase Group. From
2/6, the next phase for service is phase 1. Because 2/6 become "barrier phases" and
phase 6 is in the 'next Co-Phase' c-2, only phase 2 terminates to advance to c-2.
From 1/6, the 'next Co-Phase' is c-3. Phases 1/6 become "barrier phases" and since
they are not in the 'next C-Phase Group' both phases terminate to transition to 3/7.
The process continues.

Starting with phases 1/7/11, the next phases for service are 2/8/12. The transitions
from 1->2, 7->8 and 11->12 occur independently because they are in the same Co-
phase Group. From 2/8/12, the 'next Co-Phase Group' is c-2 and 2/8/12 become the
"barrier phases". The 'next Co-Phase Group' is c-2 with next phases 3/0/13. The next

transition is 2/8/12 -> 3/0/13. All 3 rings must terminate to serve 3/0/13. From 3/0/13,
the next phases for service are 4/0/14. The transitions from 3->4 and 13->14 occur
independently because they are in the same Co-phase Group. From 4/0/14, the 'next
Co-Phase Group' is c-3, with next phases 5/9/15. The process continues.
The key point of this example is when determining the next phases in the 'next Co-
Phase Group', the first phases in the Co-Phase with a call are not always the desired
next phases. The process must identify active phases in the next Co-Phase and start
checking for calls on phases after that phase. Even though phase 11 is the first phase
in c-2 r-3 with a call, phase 13 is the next phase because phase 12 is on and in both
c-1 and c-2. If there were no phases in c-2 after 12 or phases 13,14 had no call,
phase 12 would remain green during the transition from 2/8/12 -> 3/0/12.
Phase Selection Points

The next phase to be serviced is determined at the end of the green interval of the
terminating phase, unless the decision cannot be made then. If that happens, then
the decision is made at the end of all yellow and red clearance intervals. Once the
next decision is made, the controller commits to the selected phase.
EXAMPLE:
In a standard 8 phase dual ring quad sequence, Ring 1 consists of phases 1, 2, 3 & 4
and Ring 2 consists of phases 5, 6, 7 & 8. Combinations of phases 1 or 2 & 5 or 6
can all be on at the same time because they are in the same Co-Phase Group. But 1
or 2 & 7 or 8 can never be on at the same time, because the barrier separates phases
1 & 2 in Ring 1 from phases 7 & 8 in Ring 2. This is also true for 3 & 4 in Ring 1 from
5 & 6 in Ring 2. In this example, phases 1, 2, 5 & 6 are in the same Co-Phase Group.
Note In the standard dual ring controller set up as shown in the example below, phases
2, 4, 6, and 8 are normally considered the “barrier” phases. However, if there is no
call on phase 6 (or it is omitted or not used) then phase 5 becomes the barrier
phase when on. The operation is similar for phases 1, 3, or 7 in the same
configuration.
Barriers
1 2 3 4 Ring 1
5 6 7 8 Ring 2
Co-phase Co-phase
group 1 group 2
Figure 109 – Ring, Barrier, and Co-phase Relationship (Sd 8 phase quad left)

The co-phase programming screen for this example sequence is shown here:
VALUE (YES/NO) RINGS (0-4) 1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
RINGS 1 1 1 1 2 2 2 2
CO PH 1 X X X X
CO PH 2 X X X X
CO PH 3
CO PH 4
Figure 110 – Example of Co-phase programming
Note that phases 1, 2, 5 and 6 are in co-phase group 1, while phases 3, 4, 7 and 8
are in co-phase group 2. Phases 1, 2, 3, and 4 are in ring 1 and phases 5, 6, 7 and 8
are in ring 2.
Co-phase group 1 phases are followed by co-phase group 2 phases, then back to
group 1. All phases in each co-phase group must clear before a phase in the other
co-phase group can time.
Phase 1 can time with 5 or 6 because 5 and 6 are in the same co-phase group but in
different rings. Similarly, phase 2 can time with 5 or 6, ph 3 can time with 7 or 8,
phase 4 can time with 7 or 8, etc.

Examples Using Co-Phase Groups

As an illustration of the effect of Co-Phase Group programming, review the following
examples.
Example 1: Altering the Order of Phases

Suppose it is desired to use the Co-Phase Group feature to provide a phase 1-3-2
sequence in a 3-phase controller instead of the normal phase 1-2-3 sequence
(without using the lead-lag feature).
The normal co-phase assignment for a 3 phase sequential (such as from the Utilities
Menu default load) is as follows......
1-2-3
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
RINGS 1 1 1
CO PH 1 X X X
CO PH 2
CO PH 3
CO PH 4
Figure 111 – Altering co-phase assignments - example 1
To change the sequence order to 1-3-2:
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
RINGS 1 1 1
CO PH 1 X
CO PH 2 X
CO PH 3 X
CO PH 4
Figure 112 – Changing sequence order - example 1
By moving phase 3 to co-phase group 2 and phase 2 to group 3 as shown, phase 3
will time before phase 2. This occurs because they are in different co-phase groups
where the order of co-phase group takes precedence over the order of phase
number.

Example 2: Adding a 9th Phase to an 8 Phase Quad

Suppose it is desired to use the co-phase feature to add a 9th phase that will come
up between main street (1, 2, 5, 6) and major side street (3, 4, 7, 8).
First load an 8 phase quad from the Sequence Library or default load, then add phase
9 to ring 1 on the ring assignment screen:
VALUE (YES/NO) 1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
Ring 1 X X X X X
Ring 2 X X X X
Ring 3
Ring 4
Phase 9 is enabled in
ring 1 row
Figure 113 – Ring assignments - example 2

Then page down to the co-phase screen and change it so that phases 3, 4, 7, and 8
are moved to co-phase group 3, and phase 9 is inserted in co-phase group 2 (and
ring 1).
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
RINGS 1 1 1 1 2 2 2 2 1
CO PH 1 X X X X
CO PH 2 X
CO PH 3 X X X X
CO PH 4
Phases 3, 4, 7, & 8 are

shifted down to co-phase
group 3 and phase 9 is
inserted in group 2.
Figure 114 – Co-phase assignments - example 2
Thus, phase 9 will come up after 1, 2, 5, and 6 and before phases 3, 4, 7, and 8. The
sequence runs otherwise like a normal 8 phase. To actually use this sequence, an
available set of outputs would need to be determined and signal head steering used
to drive them with phase 9 (see page 380).

The ring structure is now the following:
Co-Phs Grp 1 Co-Phs Grp 2 Co-Phs Grp 3

Ring 1 1 2 9 3 4
Ring 2 5 6 -- 7 8
Example 3: Lagging Phase 1

This example shows how to Lag Phase 1 while preventing Phases 1 & 5 from timing
concurrently, and without activating the Lead-Lag option. Suppose the intersection
topography is such that Phases 1 and 5 cannot operate concurrently. This requires
advanced Co-Phase programming.
First load an 8 phase quad from the Sequence Library or default load:
VALUE (YES/NO) 1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
Ring 1 X X X X
Ring 2 X X X X
Ring 3
Ring 4
Then page down to the co-phase screen and change it so that phases 2, 5 & 6 are in
Co-Phase Set 1, phases 1 & 6 are in Co-Phase Set 2 and phases 3, 4, 7, and 8 are
moved to co-phase group 3.
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
RINGS 1 1 1 1 2 2 2 2
CO PH 1 X X X
CO PH 2 X X X
CO PH 3 X X X X
CO PH 4
Phases 3, 4, 7, & 8 are

shifted down to co-phase
group 3.

Phases 1 & 5, now being in different co-phase groups, cannot be timed concurrently.

Co-Phs Grp 1 Co-Phs Grp 2 Co-Phs Grp 3

Ring 1 2 2 1 3 4
Ring 2 5 6 6 7 8
Example 4: Leading and Lagging the Same Left Turn Movement

In an 8-phase quad left, suppose the left turn storage bay for Phase 1 can only hold a
few vehicles and it is prudent to serve the left turn twice per cycle as a lead and lag
left turn. This will require adding phase 9 to the ring structure where phase 1 is the
leading left turn and phase 9 is the lagging left turn.
First load an 8 phase quad from the Sequence Library or default load, then add phase
9 to ring 1 on the ring assignment screen:
VALUE (YES/NO) 1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
Ring 1 X X X X X
Ring 2 X X X X
Ring 3
Ring 4
Phase 9 is enabled in
ring 1 row

Then page down to the co-phase screen and add phase 9 to Co-Phase Group 1.
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
RINGS 1 1 1 1 2 2 2 2 1
CO PH 1 X X X X X
CO PH 2 X X X X
CO PH 3
CO PH 4
Phase 9 is added to Co-

Phase Group 1

Co-Phs Grp 1 Co-Phs Grp 2

Ring 1 1 2 9 3 4
Ring 2 5 6 7 8
An Overlap must be used to drive the left turn outputs when phases 1 and 9 are
timed. See Chapter 5 for information on Overlap operation. I/O Steering could be
used to bring Overlap E out on Channel 1 (assuming Channel 1 is Phase 1). See
section on I/O Steering in Chapter 12. The left turn detector(s) would also be
assigned to call and extend phases 1 and 9 (see Chapter 6 for detector details).

Exclusive Pedestrian Operation

Exclusive Pedestrian Operation (Xped) provides a unique timing movement
exclusively for pedestrian movements (no Phases on during this movement, but non-
conflicting Overlaps are allowed.) An Xped movement is an integral part of the
sequence and is programmed as a special EXCLUSIVE PED PHASE. The 3000
Controller provides 2 different Xped movements, Xped #1 and Xped #2.
The ped timing and its relative order in the sequence is determined by the exclusive
ped phase, but the Walk and Don’t Walk outputs can come out on any number of
selected output phases.
Once an Xped has been enabled, a ped call on any of its output phases will activate
the Xped movement at the appropriate point in the sequence. If no enable selection
is programmed, the Xped movement cannot be activated.
XPED Example
EXAMPLE DEFINITION: The following example will provide an exclusive ped
movement for a standard 8 phase dual ring quad sequence. The exclusive ped
movement will follow phases 4 and 8.
Step 1.
Set up a unique phase to provide a position in the sequence and exclusive ped
timing. The phase can be any phase but must not be used for vehicular signals. Since
the example controller uses the first 8 phases for vehicular signals, phase 9 will be
chosen.
a.) RING ASSIGNMENT of XPED PHASE

From the second page of the Sequence/Start-up Menu (MM-3-1-1-PGDN )....
VALUE (YES/NO) 1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
Ring 1 X X X X X
Ring 2 X X X X
Ring 3
Ring 4
Pgdn For Co-PHASES X/PED
Figure 119 – Ring assignment of an exclusive ped phase
Add phase 9 to ring 1 as shown above.
b.) XPED CO-PHASE ASSIGNMENT

Next, set up the exclusive ped phase’s order in the sequence by assignment
to co-phase groups. The example definition called for exclusive ped to follow
phases 4 and 8. Thus, phase 9 is simply added to co-phase group 3 in the
standard 8 phase quad co-phase arrangement.

PGDN ....
XPED follows phases 4 and 8:

FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
RINGS 1 1 1 1 2 2 2 2 1
CO PH 1 X X X X
CO PH 2 X X X X
CO PH 3 X
CO PH 4
Figure 120 – Co-phase assignment for an exclusive ped phase
Had it been desired for the exclusive ped to follow phases 2 and 6, then
phases 3, 4, 7, and 8 would be shifted down to co-phase group 3 and phase
9 inserted in group 2.
XPED follows phases 2 and 6:

FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
RINGS 1 1 1 1 2 2 2 2 1
CO PH 1 X X X X
CO PH 2 X
CO PH 3 X X X X
CO PH 4
Figure 121 – Another co-phase assignment for an XPED phase
Step 2.
Set up the Exclusive PED operation screen. Chooses enable source.
Source itself then must
A pedestrian call on any output phase calls Xped. be activated, e.g. ckt 108
Soft return applied. See def. next pg. (EP1) = ON.
PGDN ...

XPED IN: N PED 1: N PED 3: N TOD: Y
1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
XPED PH X
OUTPUTS X X X X See conflict monitor
compatibility note
SOFT RET X X
below.
PGDN FOR ECLUSIVE PED 2
Figure 122 – Setting up XPED operation

Note The unit must be re-booted to activate new entries when any Exclusive PED
parameter is changed.
XPED Enable Source Selection

Exclusive ped must be enabled to allow operation. The enable can be on all the time or
part time (only certain times of day). An Xped movement may be enabled by one or
more of the following enable sources: 1) ‘D’ module Xped input, 2) Ped Detector 1 or 3)
or TOD circuits 108 & 109. An input is likely to be used if Exclusive Ped was designed
into the cabinet. If not, the easiest way to enable exclusive ped for an existing cabinet
is to enable TOD then simply turn on circuit 108 (XPED 1) or 109 (XPED 2) in the clock
ckt. overrides menu (MM-3-3-6-PGDN , etc.).
Note that selecting the enable source (Y/N) on the Xped screen does not directly
enable exclusive ped—the source itself must also be activated. In the previous
example, the enable source is TOD. To actually enable exclusive ped 1, ckt 108 must
then be activated. If an input is chosen, the input must be true (DC gnd = true). Once
enabled, a ped call must also be placed for the exclusive ped to come up. The ped
call comes from any output phase ped call.
XPED Phase Selection

In the example, phase 9 has been chosen as the exclusive ped phase. An Xped
movement must be a unique phase containing Walk and Ped Clear timing,
programmed in an existing ring, and in its own co-phase group (separate barrier). The
phase must not be used for vehicular signals.
XPED Output Phases

The output phase(s) determine where the physical Walks and Don’t Walks come out.
In the example, phase 2, 4, 6, and 8 walk outputs will all simultaneously activate
when the exclusive ped walk is on (see compatibility note below). The output phases
also determine where the exclusive ped call comes from. A ped call from any output
phase calls for exclusive ped. Automatic Ped Omits are applied to Xped output
phases (2, 4, 6 & 8 in this example) to prevent the ped from normal timing with the
associated green.
Conflict Monitor (MMU) Compatibility

By definition, all exclusive walks (output phases) are compatible with each other, but
conflict with all other vehicular channels—or at least with any vehicular channels that
cross that walk’s path. It is best if all Exclusive Ped output phase walks are monitored
on their own separate channels.
It is not permissible to use Exclusive Ped operation when any of its walks are
monitored on a walk input of a channel that is shared by phase which is either
incompatible with any exclusive walk or any other phase on an exclusive walk
channel. This is because a walk channel input is part of the same channel as phase
colors and any jumpers make both walks and phase colors compatible with each
other. Thus, in most cases Exclusive Ped walks must be monitored on separate
channels.

This is generally not a problem with the TS 2 MMU when in the type 16 mode,
because walks are all on separate channels anyway and appropriate jumpers can be
added. However, this can be a problem when trying to add an exclusive ped
movement to an existing cabinet with a TS 1 monitor (or MMU in type 12 mode) and
walks are on phase channels. If so, they must be re-wired so that the walks are
monitored on separate channels. The previous example could not be used as an
Exclusive ped if phases 2, 4, 6, and 8 walks are monitored on channels with phases.
Xped Compatibility Card Jumper Example

If the exclusive ped has been set up with the following monitor (MMU) channels;
Channel 1 2 3 4 5 6 7 8 9 10 11 12
Movement φ1 φ2 φ3 φ4 φ5 φ6 φ7 φ8 φ2 φ4 φ6 φ8
Wlk Wlk Wlk Wlk
Figure 123 – Compatibility card jumpers for an XPED phase
The standard jumpers for the dual ring would be:
1-5, 1-6, 2-5, 2-6, 3-7, 3-8, 4-7, 4-8
The additional jumpers required if Xped operation is to be full time (always runs Xped,
never with phases) are:
9-10, 9-11, 9-12, 10-11, 10-12, 11-12 (compatible with each other)
The additional jumpers required if Xped operation is to be part time (sometimes runs
Xped, sometimes runs normal 2, 4, 6, 8 peds) are:
1-11, 2-9, 2-11, 3-12, 4-10, 4-12, 5-9, 6-9, 6-11, 7-10, 8-10, 8-12
(compatible with phases)
9-10, 9-11, 9-12, 10-11, 10-12, 11-12 (compatible with each other)
Xped Soft Return Phases

If there is no other demand, the exclusive ped phase will time walk then ped clear,
then rest in red. Thus is generally not desired, so if there are no normal recalls the
soft return feature should be used to insure the unit cycles out of exclusive ped to
some other phase (usually main street).
Note A Red Clearance Time may be programmed for the Xped Phase to provide a
period of steady don’t walk before the next greens appear.

Xped and Overlaps

An Overlap may contain the Xped as a parent phase. The following is an application
where an Xped could be timed concurrently with a right-turn Overlap. See Chapter 5
for Overlap details (page 182).
Ring Structure: Load default sequence #5 and remove phase 8 from Ring 1 and Co-
Phase Group 2.
Ring 1 1 2 3 4 7
Ring 2 5 6 --
Figure 124 – Ring and co-phase topography for an XPED as phase 7

Intersection:
Φ3
P2
Φ2
P3 Φ5
Φ1
Φ6
Φ4 OLA OL A = 4, 5, 7; Xped Phs = 7,

Outputs = 2 & 3
Figure 125 – Exclusive ped phase in an intersection

Xped Programming:
XPED IN: N PED 1: N PED 3: N TOD: Y
1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
XPED PH X
OUTPUTS X X
SOFT RET X X
PGDN FOR ECLUSIVE PED 2
Figure 126 – Exclusive ped with overlap programming

PHASE RECALLS AND MODES

Phase recalls and modes define the phase service mode for each phase. The 3000
Series controller allows up to 4 unique timing plans. These plans include some of the
recall modes, others are programmed only once (not subject to TOD or Cycle-Split
timing plan changes).
From the Controller Menu, select 2, Phase Recalls/Modes...
Phase Recalls/Modes Menu
1.Rcl, Omit, Non-lock, MAXII, etc.

2.CNA, WRM, Ped Recy, Inh Max, etc.
Menu 1 items programmed per TP1-4. Use

TP1 only if no changes by TOD or coord.
Menu 2 items are one setting per unit.
Figure 127 – Phase Recalls/Modes Menu
Recall menu selection 1 area contains recall parameters that are assigned to
timing plans 1-4. These are mostly standard recalls like min recall, max recall,
ped recall, etc. Because they are assigned to timing plans, they can change by
TOD or Cycle-Split. Use only Timing Plan 1, if no TOD or Cycle-Split changes
are desired.
Recall menu selection 2 area contains recall parameters that are programmed
once per unit, and are mostly CNA modes and ped options. These do not
change by TOD or by Cycle-Split.
Timing Plan Assignable Recall Modes (Menu 1 Recall Modes)

These are programmable in up to 4 timing plans (use TP1 if no changes by TOD or
Cycle-Split are desired).....
Menu selection 1....
Phase Functions (1 of 12) Value(YES/NO)
Timing Plan: 1 1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
MIN RCL X
MAX RCL
PED RCL
SOFT RCL
NON-LOCK
Figure 128 – Timing plan assignable recall modes

Phase Recalls and Modes
PGDN ....

Timing Plan: 1 1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
VEH OMIT
PED OMIT
WLK REST
MAX II
RED REST
Figure 129 – Phase Recalls/Modes Menu - page 2
PGDN ....

Timing Plan: 1 1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
NO SKIP
Figure 130 – Timing plan assignable recall modes - page 3

Page down to continue to the three screens of functions for each timing plan.
Phase functions are programmed selectively for each phase by moving the cursor to
the appropriate phase and pressing the Y/N key or simply toggling the value by
pressing the associated phase number. Numbered keys 1 through 9 represent
phases 1-9. The SHIFT key plus keys 0-6 toggle phases 10-16. During entry, an ‘X’
indicates this function has been selected for this phase.
Timing Plan Assignable Phase Recall Definitions
Min Recall
Places a Minimum Recall on the selected phases. Assures phase will always be
serviced and will time Initial, but any further green is dependent on detector
extensions (can time up to max time). If there is no demand on the phase, the
controller will time the Initial interval only then will either rest (no other demand) or
advance to the next phase with demand.
Typical use:
On an actuated main street, it causes the unit to always return to and serve the main
street. It will rest in main street green when there is no demand (see soft recall
below).
Note In addition, Min Recall can be activated per phase by a TOD circuit (CKTS 145-
160) or activated for all phases using MIN (CKT 78).

Max Recall
Places a Maximum Recall on the selected phases. This is similar to min recall except
that the phase will time the entire max time regardless of demand. Upon termination
of the max timer the phase will either rest or advance to a phase with demand. Max 1
is the default and Max 2 can be selected via an external input or TOD circuit.
Note In addition, Max Recall can be activated for any individual phase by TOD circuits
49 through 64.
Typical use:
Max Recall is typically used for any phase that is to be “pre-timed” i.e. it has no
detection but must be served. Often used on a main street with no peds (or actuated
peds) in a semi-actuated application where the side is actuated but the main street is
not. Note that Max Recall should not be applied to phases with functional detection. It
is sometimes applied to an actuated phase temporarily when detection fails.
Ped Recall
This option places a Ped Recall on the selected phases. The pedestrian movement
on this phase will be serviced once per cycle. In the normal ped recall mode the
phase will not rest in walk. The phase can be programmed to rest in walk by enabling
WALK REST (page down from this screen, see walk rest definition next page).
Note This Ped Recall operation applies a constant Ped call. As a result, in the absence
of conflicting calls, the ped alternates between Walk and Ped Clearance.
Typical use:
Main street with ped signals, see Walk Rest (Actuated Rest in Walk.)
Note Ped Recall can be activated per Phase by using TOD circuits 161 through 176.
Soft Recall
Soft Recall will only place a call on the selected phases if no calls exist and the
controller is not already resting in one of these phases. It allows the unit to cycle
between all phases, and when demand ceases, rest in the programmed phase(s).
It should be noted that there is a distinct difference between Soft and Min Recall,
even when used in a 2-Phase operation. The difference is apparent if, for example,
Phases 1 and 2 both have Max Times of 20 seconds, there is no real call on Phase 2,
and Soft Recall is applied to Phase 2. In this case, Phase 1 can extend in Passage
indefinitely. (Phase 1’s Max timer does not count down.) If Min Recall were applied to
Phase 2 in this situation, Phase 1 would max out after 20 seconds and then serve
“demand lacking” Phase 2, despite there still being demand on Phase 1.

Typical use:
Typically used on a fully actuated intersection. Soft Recall allows the unit to always go
back to and rest in main street Green when there is no demand (or recalls)—but
without interfering with other phase service.
For example, at a 3 phase intersection say that phase 2 is the main street with Soft
Recall mode set. If there is demand on Phases 1 and 3 only, the controller will cycle
between Phases 1 and 3 only, without servicing Phase 2*. It is only when there is no
demand at all that Soft Recall will be applied to Phase 2. If Min Recall had been
applied to Phase 2, the unit will always cycle through Phase 2 when going from
Phase 1 to 3.
Note In order for Soft Recall to work properly, the Soft Recall programmed phase(s)
must have detection.
Non-Lock (memory off)

Non-Lock disables vehicle call memory on selected phases. The phase only
recognizes vehicle presence so that the detector must be continuously occupied in
order to maintain a call for service. Note that the default mode is non-lock disabled
(no “X”), which means that memory is on. Program an “X“ for phases to operate in
Non-Lock mode (i.e. memory off, presence mode).
When Non-Lock is not enabled (locking mode), if the phase terminates with time
remaining in the Passage Timer (i.e. Max, Force Off, Interval Advance), a call will be
left on the phase and the unit will cycle back to it.
Typical use:
Non lock enabled (X) should be used for phases where the detection zone is
sufficient for presence type detection and vehicles must occupy the detector zone to
be served. If these vehicles leave before phase service, the call is forgotten, (ie,
Right Turn on Red or Permissive Left Turn completed). Non-Lock disabled (no “X”)
should be used when the detector call must be retained until phase service, such as
when the detection zone is set back from the stop bar, or when it is easy for a vehicle
to overrun the stop bar detector.
Veh Omit
Places phase omit on the selected phase(s). The phase(s) will no longer be served
regardless of demand.
Typical use:
Time of day phase omitting. Typically where two or more timing plans are used and
the phase is allowed in some plans but omitted in others. Say for an advance left turn
into a factory entrance that operates mornings only. It is not recommended to use this
feature to disable phases never used in a sequence, especially if operating in
coordinated mode. Instead, a better approach is to edit the sequence to remove any
unused phases altogether.
*
Phase 2 will be served normally if there is real demand. (Cars are actually on the detector.)

Alternate use:
Another usage of Veh Omit is for phases used exclusively for preemption. The
preempt phase is omitted so that it will not service during normal operation.
Note Do not use Veh Omit on Exclusive Ped (X-Ped) phases.
Ped Omit
Places ped omit on the selected phase(s).
Typical use:
Time of day ped omitting. Typically where two or more timing plans are used and the
phase ped is allowed in some plans but omitted in others.
Walk Rest (Actuated Rest in Walk)

Allows selected phase(s) to rest in Green-Walk instead of Green-Don’t Walk. Walk
Rest is similar to the WALK REST MODIFIER used in conjunction with CNA mode
except that it applies to standard actuated walks. Walk Rest does not automatically
put in another PED call to re-time the phase if a conflicting call clears before the end
of the current phase’s Ped clearance. (Also see Walk Rest Modifier, page 130.)
Typical use:
When it is desired that the main street rest in Walk, but not as a CNA phase. Perhaps
the main street is vehicle actuated and extendible, but it is desired to rest in Ped-
recalled Walk, in the absence of conflicting demand. Once demand arrives, the Ped
clears and the phase may extend in Green/Don’t Walk. CNA mode does not allow
vehicle extensions.
MAX II
Selects MAX II operation without the MAX II input being active.
Typical use:
Time of day Max II timing on selected phases only. Typically two or more timing plans
are used. Max II is applied to some phases in some plans but not in others.
Note If all phases are to go to max II timing, then simple activation of the Max II input, or
clock circuit, will suffice without the need for multiple timing plans.
Red Rest
This option causes the controller to rest in red for the selected phases when no
conflicting calls are present. (The Ring 1 Red Rest and Ring 2 Red Rest inputs need
not be active; this function has precedence.)
Typical use:
To accomplish a specific special requirement. It is not recommended in normal
practice to rest in red at an operating intersection.

No Skip
This option forces the controller to service phase(s) if a call comes in on a phase
normally serviced after that phase. For example, if the controller is resting in Phase
2, No Skip is enabled for Phase 3 and a call comes in on Phase 4. Thanks to No
Skip, Phase 3 will be serviced for its minimum time before the controller proceeds to
Phase 4.
Typical use:
Sometimes used in coordinated operation, to insure service to certain phases. Also
may be used when an intermediate phase serves as a special clearance of some
kind, perhaps an inside clearance. (Also see the discussion of Double Clear Overlaps
on page 192.)
Example:

Ring 1 2 3 4
Ring 2 6 6 7
Φ4 Φ7
Φ2 No Skip is enabled for

phase 3. Phase 3 is a
dummy phase that
provides downstream
clearance for Phase 2
Φ6 before Phase 4 begins
timing.
Figure 131 – No Skip example

Per Unit Assignable Phase Functions

These are the functions on Menu 2 under the Recall Modes menu. These phase
functions are configurable once-per-unit, and apply to all four timing plans. Except for
Flashing Walk, Ped Clear Thru Yellow and Red, and Conditional Ped, they must be
enabled by an external input or TOD circuit (e.g. CNA I, etc.). Per phase
programming activates the function for selected phases only if the function is enabled.
Menu Selection 2 From The Recall Modes Menu (MM-3-1-2-2)....
1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
CNA 1 X X
CNA 2
CNA 3
CNA 4
WRM X X
Figure 132 – Per Unit Assignable Phase Functions
This section is primarily for CNA modes.
PGDN .....

1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
INH MAX X X
PED RECY X X
FL WALK
FDW->YEL
FDW->RED
Figure 133 – Per Unit Assignable Phase Functions - page 2
PGDN .....

1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
COND PED X X
Figure 134 – Per Unit Assignable Phase Functions - page 3

Enable/disable phases as desired by moving the cursor to the function and phase and
toggling 0(Y/N).

Per Unit Phase Recall Definitions
CNA Definition
CNA stands for “Call to Non-Actuated”. CNA mode applies non-actuated operation to
selected phases. Min Recall and Ped Recall are automatically activated and phase
detectors are disabled for these phases. The most significant aspect of the CNA
mode is that, during the hold period while in coordination, the CNA phase will hold at
the end of walk instead of the end of green. Ped Clear then follows just before phase
termination. The advantage of using CNA for coord phases is that the length of walk
is determined by the coord phase split time. In this way, the walk duration varies
depending on the cycle and split selection, i.e. walk time = split time - (pcl + yel +
red).
Typical Uses for CNA Mode

CNA may be used for any phase for which it is desired to recall the ped then rest in
green/walk in absence of conflicting calls (WRM must be ON). This could be for a
main street with walk signals operating in a semi-actuated mode, i.e. there are no
detectors on main street, but there are detectors on side street.
CNA is most often used when it is desired to hold (main street) coord phases in walk
during coordination.
CNA 1 - Selects phases for CNA I operation.
CNA 2 - operates the same as CNA I, but it provides an alternative phase
selection for Call to Non-Actuated operation, perhaps for cross-arterial
coordination.
CNA 3, 4 - identical in operation to CNA 1 & 2, but can also be activated by an
external input or TOD circuit.
A CNA phase contains four Green states, defined by NEMA as States A, B, C and D.
State A is Walk Timing, State B is Walk Rest or Walk Hold, State C is Ped Clearance,
and State D is Green Dwell/Select.
State A: Walk Timing – Upon initial entry into phase, Walk times provided Ped
Omit is not on.
State B: Walk Hold – Upon completion of Walk Timing, the phase “holds” in
walk if Hold is applied.
State B: Walk Rest– The phase “rests” in Walk if Hold is not applied, the Walk
Rest Modifier (WRM) is applied, and no serviceable conflicting calls exist.
The phase leaves the Walk Rest/Hold state and advances to Ped Clearance
when:
a.) The phase is in Walk Rest and a serviceable conflicting call is

registered, or
b.) The phase is in Walk Hold, a serviceable conflicting call exists and
Force Off is applied, or

c.) Hold is released and the WRM is not active, regardless of the presence
of a serviceable conflicting call.
State C: Ped Clearance – The phase times the Ped Clearance setting, and
then advances to the Green Dwell/Select state.
State D: Green Dwell/Select – This is the state in which the controller does
one of the following things, based on the current conditions:
a.) Immediately selects the next phase to be serviced and proceeds to yellow
clearance, or
b.) it rests in Green/Don’t Walk if a call exists and concurrent timing constraints
exist, or if WRM and Ped Recycle are not active, or
c.) it returns to Walk if no serviceable conflicting call exists and either WRM or
Ped Recycle are active, and Ped Omit is not active.
Once a CNA phase has left Walk, Hold and Force Off do not have an effect
on the termination of the phase. That is, Force Off does not have to be
maintained throughout Ped Clearance in order to terminate the green, nor
will Hold maintain the phase in Green/Don’t Walk.
WRM (Walk Rest Modifier)

As described above, CNA phases rest in walk during the hold period when in
coordination. When Hold is removed, if there are no alternate (side street) calls, Walk
Rest Modifier allows the controller to continue to rest in green-walk instead of ped
clearing to green-don't walk. It also allows the CNA phase to re-time walk if the call
from the conflicting phase goes away (lock = off) before Ped Clearance has
completed and yellow starts. Note that if WRM is not applied, the unit will not rest in
walk without hold applied.
Typical use. Non-actuated main street phases that are to rest in walk without hold
applied when no conflicting calls exist.
Inhibit Max
Inhibit Max prevents any phase in its ring from terminating due to a Max Timer (but
can gap out or force off). Max Timer times as normal, but the phase cannot terminate
when the Timer = 0. Inhibit Max termination is sometimes used for actuated phases
during coordinated operation. During coordinated operation, phases are typically
terminated either due to a gap condition or by a force off as applied by the
coordinator. The basic idea behind ”Inhibit Max” during coordination is to prevent
phases from maxing out before being forced off, thus allowing the coordinator to
determine the length of green—rather than the max times doing it.
Typical use:
During coordination by use of COS/F to TOD CKTS such that INH MAX is not applied
until the coordinator and associated force offs are in effect. (See the notes in the next
topic.)

Inhibit Max Warnings

1. Using Inhibit Max during non-coordinated operation is not recommended.
Inhibit max with no other constraints would allow a phase to extend indefinitely.
A busy street or malfunctioning detector (constant calling) would then lock up
the controller in green. It could also prevent the controller from entering
coordination correctly since the controller requires the termination of all greens
before a coordination sequence can begin.
2. Using Inhibit Max during non-coord operation may also cause a Cycling
Failure. The operator should use the “COS/F to TOD CKTS” option in the
COORDINATION MENU to activate this feature.
Note In controller software versions 2.0 (TS 1) and 3.0 (TS 2) and higher, activating
Inhibit Max only affects operation during Coordination (ignored during FREE
operation).
3. Another way (and perhaps a better one) to accomplish the goal of preventing
phases from maxing out before forcing off is to use Max 2 timing during
coordination, where Max 2 times are set high enough to prevent this. Max 2
can then selected by the “COS/F to TOD CKTS” option as mentioned in 2.
above.
Ped Recycle
Ped Recycle operates on both CNA and actuated phases. A “ped recycle” shall be
defined as any start of walk after the parent green has already started. It can refer to
a late start, or a second (or third, etc) service within the same green interval.
For CNA phases – If the phase has finished timing Ped Clearance and no
serviceable conflicting call exists, the phase returns to Walk if Ped Recycle is active.
If WRM is applied, Ped Recycle is trivial because WRM does the recycling. The
effects of Ped Recycle are only seen if WRM is off.
For non-CNA phases – Activated Ped Recycle allows a pedestrian movement to be
‘re-serviced’ during the same cycle if Hold is applied to the phase when a ped call
comes in, regardless of the presence of a serviceable conflicting call.
Note In the absence of a serviceable conflicting call without Hold applied, a phase
in the actuated mode will always recycle the Ped, regardless of the setting of
this function (provided that Ped Omit is not applied).
Typical use:
Non-CNA Coordinated phases with Peds and Ped push buttons. Allows a late (after
start of green) service to walk. One case in which ped recycle can be used is in fully
actuated applications where the yield point (release of hold) is well before the coord
phase force off. This is the “extendible green band” (EGB) operation where the
coordinated phase can either gap-out any time after the yield point, or extend up until
the force off. Hold can then be set to release early enough to allow late ped service
without serious disruption to other phase timing. If it is a relatively large coord phase
ped interval, the EGB Period will probably not satisfy the above case.

Alternate use:
For CNA Coordinated phases in which WRM is OFF and Ped Recycle is ON. This
results in all coord phases advancing to Ped Clearance upon release of Hold
regardless of calls on non-coord phases.
In this situation, the controller is in a favorable position to serve any subsequent non-
coord phase call (all Ped Clearances are timing regardless of calls) that may arrive
without having to terminate the coord peds at different times if initially a call arrives on
a non-coord phase able to be served by the termination of just one coord phase walk,
then cross-barrier calls arrive late.
Note The “Alternate Use” above is seen primarily with Multiple Permissive Mode.
Flashing Walk
This option allows flashing of the walk signal on selected pedestrian signals. The
Flashing Walk feature does not require an external input or TOD circuit. Any phase
selection of this function will automatically activate the function for the selected
phases.
Typical use:
Use of this feature is no longer common in the United States.
Ped Clearance Through Yellow

This option allows the ped clearance interval to remain active through the yellow
clearance interval of the parent phase, i.e., the Don’t Walk continues flashing through
yellow.
Typical use:
This feature should be used with caution. In the normal mode, the Don’t walk
indication goes solid during yellow and red clearance—which is a good signal to
pedestrians that they should be out of the street and have a few more seconds to do
so.
Ped Clearance Through Red

This option allows the ped clearance interval to remain active through the all red
clearance interval of the parent phase, that is, the Don’t Walk continues flashing
through red. If this operation is desired, Ped Clearance Through Yellow must be
programmed active as well.
Typical use:
See Ped Clearance Through Yellow use. When both these options are applied, the
indications go right from flashing Don’t Walk to opposing green.
Conditional Ped
This is a function that is available only in the TS 2 version of the 3000 Series
controller.

This option allows a late start or second service to the pedestrian movement (walk) if
there is enough time. Normally a ped call must be registered before the start of green
or it will not be serviced until the next cycle. Also, only one ped can normally time per
cycle. When Conditional Ped is enabled, walk can start after green has started or be
serviced a second time if the Max timer value (time left) of the active phase is greater
than WALK + PCL when the call is registered. On second calls, the FDW (Ped clear)
will complete before the second walk comes up.
Typical Use:
Whenever the ped is push-button actuated and late or second time service to the ped
will not be particularly disruptive to coordination or other phase timing. It is a feature
that is well appreciated by pedestrians (though they do not necessarily understand
the underlying operation) and helps to encourage them to wait for the walk signal.
Phase Times
Phase Times are the basic timing values that operate each phase. Phase times are
programmed by entering a value of 0-255 for parameters where no decimal point is
displayed or 0-25.5 for parameters where a decimal point is displayed.
From the Controller Menu, Select 3, Phase Times (MM-3-1-3)....
TP:1 Phase 1 2 3 4 5 6 7 8
Initial 0 0 0 0 0 0 0 0
Passage 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
Yellow 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
Red 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
Walk 0 0 0 0 0 0 0 0
Ped Clr 0 0 0 0 0 0 0 0
--PgDn for Max, SHIFT-> for ph’s 9-16--
Figure 135 – Phase timing configuration - page 1
PGDN .....
TP:1 Phase 1 2 3 4 5 6 7 8
Max 1 0 0 0 0 0 0 0 0
Max 2 0 0 0 0 0 0 0 0
Mx 3 Lim 0 0 0 0 0 0 0 0
Mx 3 Adj 0 0 0 0 0 0 0 0
--PgDn for Dens, SHIFT-> for ph’s 9-16--


PGDN .....
TP:1 Phase 1 2 3 4 5 6 7 8
TBR 0 0 0 0 0 0 0 0
TTR 0 0 0 0 0 0 0 0
Min Gap 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
AI/ACT 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
Max In 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
--PgDn for Additional Timing Plans.

Use SHIFT – RIGHT ARROW for Phases 9 through 16. Use PGDN For Timing Plans 2
through 4.
Note If passage, yellow, or red exceeds 9.9 on these screens there will be no space
between value fields. It is quite rare, however, to use values greater than 9.9 for
these functions.
Timing Plans
The phase timings as above are per timing plan 1 (TP1). They are also
programmable in Timing Plans 2-4 (TP2-4), accessed by paging down. Individual
timing plans can then be selected by an external input or TOD circuit. This flexibility
allows basic timing parameters to change by TOD or a cycle and split (CS)
combination to better respond to known traffic patterns. If no TOD or CS changes
are desired, only program TP1 timing parameters. TP1 is the default plan.
Terms Used in Phase Timing
Initial
Initial is the first portion of green, often referred to as Minimum Green. The controller
must time the Initial Interval any time the phase is served. Further green time is
dependent on the recall mode and extensions.
Typical settings: 10-15 secs for main street
5-7 secs for left turns and commercial exits
6-10 secs for actuated side (cross) streets
Initial timer notes:
1. It is not recommended to use less than four (4) seconds for initial timing for any
phase unless the phase itself does not determine the actual minimum length of
a signal green.
2. Avoid using the Initial time value as the total “phase green” time. If a phase has
no detection and is to operate in a “fixed time” (pre-timed) mode, use either
max recall, ped recall, or CNA. The phase green time will then be determined
by max time or walk + ped clear.

Passage
A vehicle detector input calls for phase service when an actuated phase is red, but
serves to extend the phase once it is green. Passage is the increment of time by
which the phase green is extended. The passage value sets to full value when a
detector input is present and times down when no input is present. If vehicles keep
hitting the detector before time out, the phase extends. If it times out, the phase
“gap’s out” and terminates. The phase can extend until either a gap occurs, a force
off is applied or the max timer times out. The passage interval will time concurrently
with initial unless passage sequential mode is enabled (see enhanced options).
Typical settings: 2.5 – 5.0 seconds for loops of 30’ or less
0.5 – 5.0 seconds for loops of 30’ or more
Passage value notes:
1. Because the passage timer is held at full value while the loop is occupied (start
to end), the length of the loop effectively adds to passage value. Thus, very
short passage times can be used with long loops, while still providing effective
passage values that are quite acceptable. The combination of long loops and
short passage values have the advantage of allowing the phase to immediately
gap out as soon as the last car passes over the loop. It is one the reasons why
many agencies have tended toward longer loops in recent years
2. The passage timer value settings in general have a significant effect on the
timing and operation of the intersection. A tendency toward shorter passage
values will make the intersection run “snappier” with less waiting for green.
Values that are too short, however, particularly if the loops aren’t very long, will
cause driver irritation and initiate complaints. A tendency toward long passage
times will reduce “the green is too short” complaints, but after a point will cause
the intersection to run “sluggishly” and thereby reduce efficiency.
Note In the presence of a continuous vehicle actuation, the phase will not gap out even
if Passage Time is set at zero. Gap termination requires Passage Timer timed out
and no vehicle actuation present.
Yellow
The yellow clearance interval.
Typical settings: 3.5 - 4.5 seconds. Based on travel speed and width of
intersection. Note that the minimum tme allowed by the 3000 to be entered for yellow
is 3.0 seconds.
Red
The red clearance interval when all phases in a ring are red before the next phase
green starts.
Typical settings: 0 - 2.5 seconds. Note: Use of 1 second or more is
recommended.

Walk
The pedestrian Walk movement time. The controller will remain in the Green interval
during Walk.
Typical settings: 7 - N seconds. Note: MUTCD requires a minimum of 7 seconds.
Ped Clearance
The Pedestrian Clearance interval (flashing don't walk). The controller will typically
remain in the Green interval during Ped Clearance; however, the Ped Clearance can
be optionally extended throughout the Yellow and Red clearance intervals, though not
recommended.
Typical settings: ‘N’ seconds where N = distance in ft. curb to curb at the ped
crossing divided by 4 ft/sec, or the distance in meters divided by 1.2 meters/sec.
Max 1
Max 1 timing is the default value used for max timing. Max time is the upper limit for
phase timing when the phase is actuated or in Max Recall mode.
Max Timer Operation:
For an actuated phase with Max Recall inactive, the max timer times down
only when a serviceable conflicting call is present. The phase remains green
until it gaps out or the max timer reaches zero, whichever comes first. The max
timer will cease timing and reset if all serviceable calls go away. The max timer
will re-start if a new call arrives and the active conflicting phases are in the
Passage interval.
For Max Recall phases, the phase is always served and the max timer always
times, regardless of demand. It will rest only when the max timer has timed out.
Note Max timing will not override initial or ped timing (walk + ped clear) should those
values be longer that max time itself. Also note that max timing is ignored by the
CNA mode. (WLK plus Hold State Duration plus Ped Clearance determine the
green time for CNA , provided the initial interval is satisfied.)
Typical settings: 5 - N seconds, where N the maximum allowed green duration.

These can vary widely, but to give a feel for the range, they might typically be 8 - 17
seconds for left turns, 12 - 25 seconds for side street, and 22-40 seconds for main
street.
Note If the Max time value is set to a very low number (such as zero) then minimum
timing requirements for the phase, such as Min Green, will override it.

Max 2
Max 2 is an alternate value for max timing. Max 2 is activated by ring by an external
input or TOD circuit. When Max 2 is active the Max timer will be loaded with the Max
2 time instead of the usual Max 1 time.
Typical settings: same concept as Max I except an alternate value used. Max 2 is
sometimes used during peak traffic periods (longer times), and is sometimes used
during coordination so phases won’t max out before forcing off (also longer values).
Note If the Max time value is set to a very low number (such as zero) then minimum
timing requirements for the phase, such as Min Green, will override it.
Max 3 Limit
The maximum value that Max 3 can attain. Used in conjunction with the Max 3 adjust
amount, which allows max time to vary based on demand. The Max 3 Limit is then the
“Max” Max (see max 3 definition previous).
Refer to the Max 3 Options section under Enhanced Options, on page 153.
Typical settings: Some value higher than the normal max time.
Max 3 Adjust
The amount of time to adjust the Max 3 timer based on successive Max terminations
or Gap terminations. The Max 3 timer will be incremented by this amount after
successive Max terminations, and decremented after successive Gap terminations
(see max 3 definition below and enabling max 3 timing).
Refer to the Max 3 Options section under Enhanced Options, on page 153.
Typical settings: 1 - 10 seconds.
TBR (Time Before Reduction)

Enter the amount of time before the controller can begin reducing the gap to the
minimum gap. Time Before Reduction (TBR) starts timing when a conflicting call is
received, which is often the beginning of green. If all conflicting calls are removed
before TBR has completed timing, the TBR timer will reset. Range: 0-255 seconds.
Also refer to the Volume Density Discussion on page 139.
Typical settings: 8 - 20 seconds. Allow enough time for queued vehicles to begin
moving. It should be at least initial (min green) plus 1 second.
TTR (Time To Reduce)

Time to Reduce establishes the time frame in which the controller will begin a linear
reduction of the phase gap (passage time) down to the minimum gap time. The
range is 0-255 seconds. If all conflicting calls are removed before TTR has completed
timing, the TTR timer will reset.
Typical settings: 4 - 12 seconds. Depends on how quickly the operator wishes to
close the timing gap.

Minimum Gap
The minimum gap value establishes the lowest acceptable gap (passage time) in
traffic. The gap will not be reduced below this amount. Range: 0-25.5 secs. Also
see Last Car Passage in the Enhanced Options menu under Density Enables.
Typical settings: 1 - 3 seconds. This will effectively determine the lowest passage
value.
Note In the presence of a continuous vehicle actuation, the phase will not gap out even
if Minimum Gap is set at zero.
Added Initial per Actuation

Also known as ”AI/Act”, Added Initial is a calculated value based on demand during
the non-Green intervals of a phase. The Added Initial Per Actuation value for a phase
is multiplied times the number of cars (detections) that are received while the phase is
in the Yellow and Red states (non-Green). The initial timing for a phase will be the
Added Initial if (and only if) it is greater than the Phase Initial and less than the
Maximum Initial.
Typical settings: 2 - 3 seconds. About enough to move each vehicle.
Maximum Initial
Maximum Initial sets a limit on the amount of Added Initial. Added Initial can never
exceed the maximum initial value. Also known as Max In, or Max Variable Initial.
Typical settings: Refer to Table 31 on page 140. The Max Initial setting is normally
set equal to the Initial interval that would be used if Volume Density were not used.

Volume Density Discussion
VOLUME DENSITY DISCUSSION

Volume Density operation is a broad term which actually combines two functions
which are not necessary related, Variable Initial density management, and Gap
Reduction density management. Variable Initial is used in situations where a phase
has set-back detection. Gap Reduction can be used with either set back or stop bar
detection.These methods are described in more detail in the next two sections.
For additional details, refer to the description of Density under the Enhanced Options
menu as described on page 151.
Variable Initial Function

Allows the normal initial green (min green) setting to be increased by counting cars
and adding the corresponding time increments when the phase is not green. The
parameters associated with this operation are called Added Initial per Actuation (AIA)
and Max Variable Initial (MVI). Variable Initial is normally associated with set-back
loops when there is no stop bar loop. Because vehicles can queue on the set-back,
the initial green must be long enough to exhaust that queue (it cannot be assumed
that other vehicles will arrive and extend). Thus, rather than just setting the initial at
the maximum requirement, it is allowed to vary by counting cars as they cross the set-
back during non-green. This increases efficiency and reduces delays.
Figure 138 – Cars are counted during red
Typical Settings for Variable Initial

Added Initial per Actuation (AIA) is usually set at in the range of 2.2 - 3.0 seconds.
Note that the initial green is only varied when the sum of Added Initial Actuations is
greater than normal initial. For example, if the initial setting is 5 seconds and AIA is
2.2, then it will take 3 actuations (3 x 2.2 = 6.6) before the initial setting is varied.

Max Variable Initial (MVI) can be set according to the table below. Note that the
purpose for max variable initial is to prevent an oscillating detector from causing an
extreme initial. To use the chart, estimate the number of vehicles that can be stored
on the stop bar side of the set-back detector and look up the value in the chart.
Table 31 – Max Variable Initial settings
Possible # (n) vehicles stored Max Variable Initial setting
1 5
2 7
3 9
4 12
5 14
6 16
n =7 and over 16 + [(n-6) x 2.1]

Volume Density Discussion
Gap Reduction Function

Gap reduction allows the normal passage time value to be reduced linearly during the
green portion of the phase. The parameters associated with this operation are called
Time Before Reduction (TBR), Time To Reduce (TTR) and Min Gap—which is the
minimum passage value allowed. Thus, the longer demand holds a phase green with
a conflicting call present, the closer the vehicles must be spaced to retain the existing
green interval.
The last car detected at the time of gap out at the reduced level can be provided with
the full value of the normal passage. This is called the Last Car Passage option. Last
Car Passage is enabled in the Enhanced Options menu (see p. 151). Gap reduction
can be used with set back or stop bar loops.
The following are the two typical uses of gap reduction:
Classic Case Gap Reduction

In this case set back loops, perhaps as far as several hundred feet are used to extend
the phase. There may or may not be stop bar detectors as well (it is recommended
that there are).
Figure 139 – Classic Case of Gap Reduction

The passage time value is set based on the travel time from the set-back detector to
the intersection. This value could be fairly long and left alone would tend to cause the
intersection to run sluggishly because the phase would constantly extend even with
widely gapped traffic. By using gap reduction, the passage value can be reduced
down enough to provide good gap control. Then by using Last Car Passage, after gap
out at reduced level, a value equivalent to the amount by which the passage has
been reduced will be added to the last vehicle extension. This allows that last vehicle
to get through the intersection if no max out or force off occurs. Note that Last Car
Passage is enabled under Density which is found in the Enhanced options section.
Gap Reduction as an Efficiency Tool

Even with normal stop bar detectors, Gap Reduction can be an effective way to
increase efficiency without getting “the green is too short” complaints. The idea is to
begin the phase with a fairly long passage time when vehicles are moving slow, then
move to a shorter time later when they are moving at the flow rate. Gap reduction is
thus a good way to obtain “snappy” operation so that phases cycle crisply without
long waits, but also without complaints.which is often the case if passage values are
simply set low.

Possible settings to use gap reduction for efficiency:

Passage = 4-5 seconds
TBR = Min Green value + 2-15 seconds
TTR = 4 - 15 seconds
Min Gap = 1.2 - 2.2 seconds
Last car passage = off
Gap Reduction Timing Diagram

The diagram below illustrates the changing value of the passage timer during gap
reduction.
Figure 140 – Passage Timer during Gap Reduction

The mechanism for gap reduction is detailed on the diagram. When the phase gaps-
out at reduced gap, one of two things occurs:
If Last Car Passage (LCP) is in effect, the controller commits to gaping out,
but will time one full passage timer for that last car.
If LCP is not in effect the phase gaps out with the “in-progress” reduced gap
value.
The control for Last Car Passage mode (Y/N) is set under the Enhanced Options
Menu (MM-3-1-9-3).

Dual Entry
DUAL ENTRY
Dual Entry will place calls on the selected phase when going to a specific phase next
only when “crossing a barrier” and only one ring has a call. This ensures that there
will always be a phase on in each ring when the sequence permits it. Dual Entry
requires only phase selection to be activated.
The first 4 screens provide standard Dual Entry for phases 1-16.
Dual Entry (1 Of 12) VALUE (YES/NO)
Dual Entry Enable: Y
1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
PH 1 X
PH 2
PH 3
PH 4 X
Figure 141 – Dual Entry programming screen
PGDN for more dual entry programming.
Typical use:
For Dual Ring controllers, to prevent a single phase from being served. In an 8 phase
quad, typically 4 calls 8 and 8 calls 4. This assumes the main street phases 2 and 6
are on some type of recall and don’t require Dual Entry.
Dual Entry by Time Plan Screens

Dual entry screens 5-12 provide alternative dual entry programming selectable by
Time Plan. The dual entry programming on these screens goes into effect when
normal Dual Entry is disabled and the appropriate time plan is selected.
Dual Entry (5 Of 12) VALUE(YES/NO)
Enable: Y TP1 Activated By Time Plan
when normal Dual Entry disabled.
PH\CALLS 1 2 3 4 5 6 7 8
PH 1 X
PH 2
PH 3
PH 4 X
Figure 142 – Dual Entry by Time Plan screen
Note that these Dual Entry plans only include phases 1-8.
Dual Entry Example

In the above screen, phase 5 is programmed for Dual Entry when going to phase 1
and phase 8 is programmed for Dual Entry from phase 4. In the phase 5 case, if
phase 1 is served (real call) and no real call exists on phase 5 or 6, a call will be
placed on phase 5. Phases 1 & 5 will then both be served instead of only phase 1.

However, if a call exists on phase 6, the controller will proceed to phases 1 & 6. The
operation would be similar for phase 8 when 4 is served.
Dual Entry Misconception

A common misconception about Dual Entry is that the phases associated with the
Dual Entry programming will always time together. As an example, consider the case
where Dual Entry is programmed for Phase 4 when going to phase 8, and phases 3
and 7 are green, with calls on Phases 1, 2, 5, 6, and 8, and no call on Phase 4. In
such a situation, a Dual Entry call will not be applied to phase 4 when phase 7 clears
to phase 8 because there is already a phase on in Ring 1 and a barrier is not crossed.
In this example, the controller would move from 3/7 to 3/8, then to 1/5, and on to 2/6.
To serve Phase 4 with Phase 8, Dynamic Recalls would also be required in addition
to Dual Entry.
Single Entry Mode

Single Entry Mode occurs when Dual Entry is disabled. In multiple ring configurations,
it allows a single phase to be selected and timed alone if there is no demand in the
other ring(s).

Conditional Service
CONDITIONAL SERVICE
Conditional Service is a function that enables selected phases to be serviced if the
conflicting co-phase in the same ring has gapped or maxed out and time is available
in all rings to service the phase. For a leading left turn phase, Conditional Service
can allow that phase to be re-serviced within the same cycle.
Conditional Service(1 OF 12)) VALUE(Y/N)

Conditional Service By Input: N
1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
PH 1 CSV
PH 2 CSV X
PH 3 CSV
PH 4 CSV
Figure 143 – Conditional Service screen
Criteria for Conditional Service

1. The controller unit is in Free Mode.
2. There must be a call on the actuated phase to be conditionally serviced.
3. The conflicting co-phase in the same ring must be gapped or maxed out.
4. There must be sufficient time remaining on the Max Timer(s) of the concurrent
phase(s) to time the yellow and red clearance of the conflicting co-phase and
the Initial interval of the phase to be conditionally serviced.
Conditional Service requires an external input or TOD circuit to enable the function.
The controller must be restarted after changing conditional service programming
before the change is implemented by the controller.
Note Conditional Service requires input or clock CKT 80 = ON to operate. Use time of
day circuit overrides for full time operation. Conditional Service is not operable in
Coordination Mode.
As shown in the screen above, the columns are the conditionally serviced phases, the
phases on the left are the phases that must clear for the conditionally serviced phase
(both must be in same ring, co-phase group).
Typical use:
In dual ring controllers where protected-only left turns are to be allowed second
service when there is enough time. Note that conditional service should never be
used for protected/permissive left turns such as 5 section heads.
Conditional Service Example

In a standard 8 phase dual ring quad, assume that the controller has already serviced
(or skipped) Phases 1 & 5 and is currently timing Phases 2 & 6. Phase 2 has gapped

out and a call exists on Phase 1 (Phase 1 & 2 are co-phases within the same ring). If
enough time is available (based on the Phase 6 Max Timer in this case) to service
ring 2 and to ‘re-service’ Phase 1, then phase 1 will be conditionally serviced. The
appropriate programming is shown above for phase 1.
Note For Conditional Service to work properly, the two phases associated with the “X”
entry must be in the same ring and same co-phase set.
Conditional Service by Time Plan Screens

Conditional service screens 5-12 provide alternative conditional service programming
selectable by Time Plan. The conditional service programming on these screens goes
into effect when normal Conditional Service is disabled and the appropriate time plan
is selected.
Conditional Service(5 Of 12) Value (Y/N)
Enable: Y TP1 Activated By Time Plan
when Normal Condtional Service disabled
FUNC\PH 1 2 3 4 5 6 7 8
PH 1 CSV
PH 2 CSV
PH 3 CSV
PH 4 CSV
Figure 144 – Conditional Service by Time Plan screen
Note that these conditional service plans only include phases 1-8.

Ped Options
PED OPTIONS
There are several options which modify pedestrian operation as determined by the
ped options screen.
Auto Ped Clear, Enhanced Ped
Auto Ped Clear with MCE: N |Val (yes/no)

Enhanced Ped: N |Val (yes/no)
Auto Ped clr = Ped Clr Protected by MCE

Enhanced Ped = Uses Max times for walks
on CNA Ph’s When CNA=OFF
Figure 145 – Ped Options screen
Auto Ped Clear With Manual Control Enable (MCE)

MCE normally protects only the Yellow and Red Clearance intervals by refusing
Interval Advance actuations from a police pushbutton, timing the Yellow and Red
automatically. Therefore, Ped Clearance is under control of Interval Advance and not
automatically timed. However, when enabled (i.e. set to ‘Y’), Auto Ped Clear adds all
pedestrian clearance intervals to this protected group so that they are automatically
timed.
Enhanced Pedestrian Operation

Enhanced ped is a feature that modifies the ped timing for phases programmed for
CNA and Walk Rest Modifier. For these phases, when Enhanced Ped is enabled but
CNA is not active, the normal walk times are replaced with the Max times for those
phases. When CNA is active, the normal walk times are used on all phases in
accordance with NEMA. Ped clearance times are not affected. Recycling of the ped
movements always uses the normal walk times. To enable this function, enter a ‘Y’ in
the field provided.
Application note: If varying the walk time is the principal goal in the decision to use
Enhanced Ped operation, a better choice might be to use the multiple timing plan
capability (see page 134).
Dual Ped Control

Dual Ped Control is enabled via TOD circuit “EDP CKT 129”.
There are ped calls on both even numbered compatible phases and they start at
different times, the first walk interval that times out will rest in walk and wait for the
other walk to time out and the two peds then enter Ped Clearance together. For this
to be seen, ped calls must exist on both compatible even phases.

ENHANCED OPTIONS
The Enhanced Options menu contains a number of miscellaneous remaining
controller features and options. They are not necessarily for the enhanced user, but
perhaps just less frequently programmed than the features listed previously.
Enhanced Options Menu
1.Dynamic Omit/Rcl 5.MAX 3 Setup
2.Ucf (TOD Flash) 6.Psg Seq/RedR/PE Ovr
3.Density Enables 7.Dimmming
4.Simult. Gap Out 8.Lead/Lag
9.Soft Flash
Figure 146 – Enhanced Options Menu
Dynamic Omits
Dynamic Omit plans are used to omit selected phases when other phases/overlaps
are on/green. The programmed phases/overlaps that are on/green must exactly
match the current state of the machine to omit the selected phases.
Dynamic Omit GRP 1(1 OF 8) VALUE(YES/NO)
Enable: N 1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
OMIT PHS X
IF PH ON X X
OR
IF O/L A B C D E F G H I J K L M N O P
GRN
Figure 147 – Dynamic Omits screen
In the example below, phase 1 is to be omitted during phases 2 & 6. Please note that
phase 1 will only be omitted when both 2 and 6 are active. It will not be omitted when
just phase 2 or phases 2 & 5 are active.
There are a total of 16 Dynamic Omit plans available. Dynamic Omit Enable must be
programmed ‘Y’ to enable any Dynamic Omit plan (Group 1 or Group 2). The first 8
plans are referenced as Dynamic Omits Group 1 plans 1-8 and only require the
enable function to be programmed. The second 8 plans are referenced as Dynamic
Omits Group 2 plans 1-8 and will be activated upon programming of the enable
function and the activation of an external input or TOD circuit (Circuit #96 GR2).
To access the Group 2 plans, the user may page down until the desired plan is
displayed or enter a ‘2’ in the data entry field provided at the top of the screen (GRP
x). Also to access a given plan directly (without the need to page down to it) the user
may enter the plan number in the next field (x of 8). Group 2 plans, when enabled,
will override Group 1 plans.
Typical use:
For dual ring controllers to prevent “backing up” on protected/permissive left turns
used (5 section heads) from main street through’s. For example, phase 2 would
dynamically omit phase 1 and phase 6 would dynamically omit phase 5.

Enhanced Options
Dynamic Recalls
Dynamic Recall plans are used to recall selected phases when other phases/overlaps
are on/green. The programmed phases/overlaps that are on/green must be an exact
match to recall the selected phases.
If Phase 1 is to be recalled during Phases 2 & 6, phase 1 will only be recalled when
both 2 and 6 are active. It will not be recalled when just phase 2 or phases 2 & 5 are
active.
Dynamic RCLS GRP 1(1 0F 8) VALUE(YES/NO)
Enable: N 1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
RCL PHS X
IF PH ON X X
OR
IF O/L A B C D E F G H I J K L M N O P
GRN
Figure 148 – Dynamic Recalls screen
There are a total of 16 Dynamic Recall plans available. Dynamic Recall Enable must
be programmed ‘Y’ to enable any Dynamic Recall plan (Group 1 or Group 2). The first
8 plans are referenced as Dynamic Recalls Group 1 plans 1-8 and only require the
enable function to be programmed. The second 8 plans are referenced as Dynamic
Recalls Group 2 plans 1-8 and will be activated upon programming of the enable
function and the activation of an external input or TOD circuit (Circuit #96, GR2).
To access the Group 2 plans, the user may page down until the desired plan is
displayed or enter a ‘2’ in the data entry field provided at the top of the screen (GRP
x). Also to access a given plan directly (without the need to page down to it) the user
may enter the plan number in the next field (x of 8). Group 2 plans, when enabled,
will override Group 1 plans.
Typical use:
When a certain phase or set of phases must be followed by another phase or set of
phases—such as “inside clearance” phases.
Alternate Use:
A semi-actuated “tee” intersection where the main street left is phase 1 (no detection),
main street thru is phase 2 (no detection) and side street is phase 3 (detection) and
the left lane on main street is for left turn protected/permissive or thru movement. It is
desired to introduce a short “fixed time” lead left turn that would only serve after
phase 3. A Dynamic Recall to call 1 when 3 is green would be used to always serve
phase 1 after phase 3, but not serve phase 1 directly from phase 2..

Uniform Controlled Flash

Uniform Controlled Flash (UCF) operation, also known as “Automatic Flash”, allows
the controller to place the intersection in flash on a scheduled, orderly basis. This
section deals with setting up the controller to enter and exit flash. Refer to the time
clock section for how to call for flashing operation by TOD. UCF programming
consists of Entry and Exit phases for entry into and exit out of UCF. In addition, there
are other options for entry into UCF.
TS 1 and TS 2 Type 2 Controllers may use UCF for planned flash operations by
manipulation of Controller Volt Monitor (drop CVM). TS 2 Type 1 Controllers must use
Soft Flash for planned flashing operations discussed on Page 178.
UCF Setup VALUE(YES/NO)

UCF Override Hold: N
UCF Test A or B: 2 (0=Neither, A or B,
1=A. 2=B) 1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
UCF Last X X
UCF Exit X X
(TOD, CL, Inter, under Coord Basic Op)
Figure 149 – UCF Setup screen
UCF Override Hold
This option, when programmed active (‘Y’), will defeat Hold applied to any phase to
allow the controller to advance quickly to the UCF entry phases (rather than waiting
for the Hold to be released). This feature is useful for transferring an entire arterial
from Coordination into Flash at the same time.
UCF Test A or B (TS 1 and TS 2 Type 2)

Test A and Test B are alternate controller inputs that can be programmed to activate
UCF. A zero entry indicates that UCF will be activated via the standard UCF Controller
input on the ‘D’ Module. Program ‘1’ to utilize the Test A input or a ‘2’ to utilize the Test
B input on the ‘A’ connector. Test A and B may be applicable in controllers that do not
have a ‘D’ module that require a Uniform Code Flash input.
UCF Test A or B (TS 2 Type 1)

Test A and Test B are alternative controller inputs that can by programmed to activate
UCF by dropping CVM to the Conflict Monitor or MMU. But since TS 2 Type 1
controllers do not have CVM, the controller has to flash using a programmed Soft
Flash. The UCF setup does still need to have flash entry and exit phases. UCF Test A
or B needs to be set to the zero value (‘Neither’). A zero entry indicates that Soft
Falsh will be activated via the first terminals and facilities (T/F) BIU, which is BIU #1.
This information is processed through the RS-485, Port 1.
Note Soft Flash is typically called for by internal time clock and usually needs no
external input such as Test A or B. For more details, refer to page 159.

Enhanced Options
UCF/Soft Flash Last Phases (Entry Phases)

UCF/Soft Flash will begin immediately following the clearance intervals for these
selected phases. These are the last phases served prior to UCF, and are also known
as Flash Entry Phases.
Note There does not have to be a real call for the “Last Phases” in order to transition
into UCF/Soft Flash. The controller will place artificial calls for these phases, serve
them for Initial interval only, and transition into UCF/Soft Flash in accordance with
the TOD setting.
UCF Exit Phases

These phases will be served immediately following UCF/Soft Flash.
Density Enables and Last Car Passage

Density VALUE(YES/NO)
Density Enable: Y
Last Car Passage: N
1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
Enable X X X X X X X X X X X X X X X X
(Density times found under phase times)

Figure 150 – Density Setup screen
The density functions of TTR, TBR, MIN GAP, and Added Initial can be
enabled/disabled on a per unit or phase basis. Note that the default setting is enabled
per unit and for all phases. The actual functions, however, are not activated unless
non-zero values are programmed in the phase times menu. Thus, in the default
mode, simply programming values into TTR, TBR, etc. will enable the function.
To enable density on a per unit basis, change Density Enable to Y. To disable,
change Density Enable to N.
To enable/disable density on a per phase basis, program Y for Density Enable, then
individually enable/disable specific phases.
Last Car Passage

Last Car Passage (LCP) will extend the green for a Density phase by the Passage
(Gap) amount to insure that the last car before the Gap termination has adequate
time to proceed through the intersection. LCP is programmed with a Y/N value. The
LCP value is used by all timing plans and is not unique to each timing plan (it is only
programmed once).

Simultaneous Gap Out

The condition for Simultaneous Gap Out (SGO) is that the controller is timing phases
concurrently with the next serviceable call in another Co-Phase Group (about to cross
a barrier.) When enabled (with a ‘Y’), SGO allows a phase’s passage timer to re-start
if it has timed out and the phase is waiting to cross a barrier. With SGO enabled and
calls on Phases 2 and 6, the Phase 4 passage timer can start again if a new vehicle
arrives. If Phase 4 then extends and Phase 8 gaps out, Phase 8 can start its passage
timer again. This operation can continue back and forth until both phases max or
they both “simultaneously gap out” (thus the term).
Simultaneous Gap Out Setup VALUE(YES/NO)
Simultaneous Gap Out Enable: Y
1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
Sim Gap X X X X X X
Figure 151 – Simultaneous Gap Out Setup screen

When Simultaneous Gap Out is disabled (i.e. set to ‘N’), the phase passage timer
cannot restart once it times out for the selected phases and is waiting to cross the
barrier. If phase 4 goes to rest while 8 is extending, then 4 cannot start its passage
timer again. Both phases will then gap out as soon as phase 8 does. The phases will
thus tend to gap out sooner with SGO disabled than when it is enabled.
Typical use:
SGO is used in any situation where the operator wants the controller to recognize any
demand during the green state and extend the phase accordingly. Disabling SGO
generally produces “snappier” cycling at the expense of a reduction in throughput by
not allowing new demand to extend.
To fully understand the operation, it is important for the user to know whether a given
state is an SGO Condition or not: (for these two examples, assume SGO is enabled
on phases 3 and 7.)
Non-Simultaneous Gap Out Condition: In an 8-phase quad left, if Phases 3 and 7
are green with calls on all phases, as soon as Phase 3 gaps out, Phase 4 is the next
phase decision; Phase 3 terminates while Phase 7 continues timing until it terminates,
and Phase 8 is the next phase decision (no barrier is crossed, so no SGO).
Simultaneous Gap Out Condition: In the above scenario, if no calls exist on Phases
4 and 8, then if Phase 3 gaps out, it will rest waiting for Phase 7 to gap or max. While
waiting, new demand on Phase 3 will restart passage timing, provided the Max Timer
not timed out. When Phases 3 and 7 simultaneously terminate, the barrier is crossed
with Phases 1 and 5 being the next phases.

Enhanced Options
Max 3 Options
Max 3 is an override max timer that will increase the current max timer after a
specified number of successive max terminations. Max 3 operation is activated by
assigning non-zero values to the Max 3 parameters for selected phases.
Max Outs to Adjust MX3 VALUE(0-255)

PH 1 2 3 4 5 6 7 8
0 0 0 0 0 0 0 0
Gap Outs to Adjust MX3

PH 1 2 3 4 5 6 7 8
0 0 0 0 0 0 0 0
SHIFT-RT.-> TO VIEW OR ENTER PHASES 9-16
Figure 152 – Max 3 Options Setup screen
More information about Max 3 timing is available in the Phase Timing section on page 133.
What is Max 3?
Max 3 timing provides the ability to vary max times dynamically at Free running
intersections or for those Coordinated intersections that do not use Inhibit Max. The
basic concept is that if a phase max’s out a specified number of times in a row (max
outs to adjust) then the normal max time value will be increased by one value of the
adjustment amount (Max 3 Adjust). If it max's out the specified number in a row again,
it increases by one more adjustment amount. This can continue until the Max Limit
value is reached. Once the max has been increased by successive max outs, it can
be decreased in the same way by successive gap-outs (gap outs to adjust), until it
gets back down to the normal value. Refer to page 137 for details about the Max 3
Limit and the Max 3 Adjust values.
The “normal” max time is the routinely selected maximum values of 1 or 2. This is the
base value from which to start, and Max 3 will never be less. It can only be more,
since successive max's adjust it up to the limit, and successive gap-outs decrease it
back to the base value (normal max).
Enabling The Max 3 Feature

1. Max 3 Limit must be set to a value higher than the normally selected max*
2. Max 3 Adjust must be set to a reasonable value (6-10 secs is typical)*
3. Max-outs to adjust Max 3 must be set (typically 1-4)
4. Gap-outs to adjust Max 3 must be set (typically 1-4)*
Typical use of Max 3:
When it is desired to “ramp-up” a phase’s overall green time slowly as demand
increases, then slowly ramp back down as it decreases. This would result in a more
*
Max 3 Limit and Max 3 Adjust are set in the Phase Timing section, while max-outs and gap-outs are set
in this section (Max 3 Options).

gradual transition than say, simply setting the max timer to the highest required value
and letting demand use the available green time immediately as needed.
Passage Sequential, Red Revert, Preempt Override

These are some miscellaneous remaining options that have been consolidated onto
one screen under the Enhanced Options menu.
Passage Seq/Red Rev/PE Overrides
Red Revert Time: 0.0|(0-25.5 Sec)

Passage Seq. Enable: N |(Y Or N)
Min Red Revert= 2 sec: Y |(Y Or N)
Ext Start Override PE: N |(Y Or N)
PE Override Stop Time: N |(Y Or N)
Figure 153 – Passage Sequential/Red Revert/PE Override screen
Red Revert Time

Red Revert provides a special minimum red time when a phase clears, then goes
right back to the same phase green. Red revert time will override normal red
clearance if the normal red clearance is shorter. The Red Revert time range is 0-25.5
seconds. Also see the Minimum Red Revert Enable definition below. Red revert most
often comes into operation during Preemption or when Red Rest is enabled. When
red resting, a phase can be served, clear to red rest, then get a call right back to the
same phase again.
Passage Sequential
When Passage Sequential is enabled (set to ‘Y’), the Passage Timer will begin timing
upon completion of the Initial interval. In this mode at least one Passage interval is
always timed after Initial, regardless of traffic demand (provided Max Out or Force Off
does not occur first.) If Passage Sequential is disabled (i.e. set to ‘N’), otherwise
known as Passage Concurrent, the Passage Timer is timed during the Initial interval.
If a gap exists at the end of Initial, the controller will immediately proceed to the
Yellow Clearance Interval.
Note The phase will not gap until Passage times out, if Passage is longer than Initial.
Minimum Red Revert = 2 Second Enable

When enabled (Y), the Red Revert time will be the greater of 2 seconds or the red
revert programmed value. When disabled (N), the Red Revert time is the
programmed value regardless of length (including 0).

Enhanced Options
Dimming
The Dimming operation provides a ‘half-wave’ signal output to achieve 50% power
reduction (in accordance with NEMA recommendations). Dimming can be selectively
chosen for each Phase, Pedestrian, Overlap and Ped Overlap output (Red, Yellow,
Green, Don't Walk, Ped Clear and Walk) by selecting Y under the desired phases or
overlaps.
Phase Dimming VALUE(Y/N) 1 1 1 1 1 1 1

FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
Red
Yellow
Green
Dont Wk
Ped Clr
Walk
Figure 154 – Phase Dimming Setup screen - page 1
Press the PGDN key to bring up the overlap programming screen:
Overlap Dimming VALUE(Y/N)
FUNC\OL A B C D E F G H I J K L M N O P
Red
Yellow
Green
Dont Wk
Ped Clr
Walk
Figure 155 – Phase Dimming Setup screen - page 2
Note that this screen applies to both vehicle and pedestrian overlaps.
Dimming operation is activated by a TOD circuit or an external input. When
activated, the selected phase, ped, overlap, and ped overlap indication outputs will be
dimmed. Dimming is intended for night time operation in intersections with
incandescent signals, when signals need not be as bright. Dimming both reduces
nighttime glare and saves energy. Dimming is not intended for signal heads with
LEDs installed.
Typical use:
To illustrate the energy saving benefits of dimming, say an intersection has 8 heads,
all using 135 watt bulbs. Also say the energy rate is 12 cents per kilowatt hour. Each
bulb then uses .135 x .12 or $.0162 (1.62 cents) per hour. While dimmed, the same
bulb will cost half that for a savings of $.0081 per hour. If the intersection can be
dimmed 8 hours a day, each bulb will save $06.48 a day. For 8 bulbs this is $.5184 a
day, or $15.77 a month (30.42 days ave.) or $189.22 saved per year per intersection.
This is not bad for a couple of minutes of programming.

Lead Lag Phasing

Lead Lag Phasing is also known as Phase Reversal or Alternate Sequence phasing.
This feature allows the user to reverse the rotation of selected pairs of phases. By
using combinations of lead-lag phasing, leading and lagging turning movements can
be achieved.
There are eight lead-lag patterns that can be individually programmed and selected.
Each pattern consists of a pattern mode and up to 4 phase pairs for reversal. When a
pattern is chosen, all four of its lead/lag pairs are implemented.
Note The two phases associated with the lead-lag entry must be in the same ring and
the same co-phase group.
In the example below the controller will reverse phases 1 & 2 and 5 & 6 when pattern
1 is selected. Pattern 2 will reverse phases 3 & 4 only. Values set to “1--1” are
default values and indicate that no reversal will be performed.
Lead/Lag Patterns VALUE(1-16= PHS 1-16)

(Mode: 0=TOD/Coord, 1=Coord, 2=TOD
3=by Input, 4=Always On, 5=Always Off)
Patt Mode PH_S PH_S PH_S PH_S
1 1 1--2 5--6 1--1 1--1
2 0 3--4 1--1 1--1 1--1
3 0 1--1 1--1 1--1 1--1
4 0 1--1 1--1 1--1 1--1
Figure 156 – Lead/Lag Setup screen
The mode determines the means of pattern selection, as described in the following
table.
Table 32 – Lead/Lag Phasing Modes
Mode Function Description
0 TOD/COORD Activated either by coord or TOD ckt
1 COORD only Activated by coordination C/O/S combination only
2 TOD only Activated by TOD ckt only
3 By Input Activated by input (see input table below)
4 Always On Always activated
5 Always Off Never activated
Lead/Lag also sets a flag telling the coordinator that it is active. (This feature was
added in firmware v3.3.6.) This flag survives power outages, so that the coordinator
recognizes that the intersection was in Lead/Lag operation before the interruption,
and can return the intersection to the normal phase rotation after power is restored.

Enhanced Options
Defining a Lead/Lag Pattern

To define a lead lag pattern, program the mode for each pattern and all phase pairs to
be reversed (up to 4). To implement a lead lag pattern, go to the appropriate areas as
defined by the mode (coord, clock etc.) Note that detector switching can be useful in
conjunction with lead/lag.
Lead Lag Selection by Input
TS 1 and TS 2 Type 2 (MODE 7)
Lead-Lag patterns may also be programmed for activation by inputs on the MS-B
connector, when operating in TS 2 Type 2 mode with mode 7 selected and/or using a
TS 1 3000 controller. The following table identifies which lead-lag pair is activated by
input. Lead-lag pair 1 is the leftmost pair on the programming screen, and pair 4 is
the rightmost.
Table 33 – Lead/Lag Activation Inputs
TS 1 / TS 2 Type 2 TS 2 Type 1
Lead/Lag Pair MS-B Pin Label RS-485 T/F BIU #3 - Alternate Sequence
1 B A
2 W B
3 X C
4 v D
TS 2 Type 1
The above listed BY INPUT is the same for TS 2-1 with all inputs coming from RS-
485, Port1.
Note When Lead-Lag is used, phase concurrency is not affected. For example, in an
8-phase quad left, if Lead-Lag is used to reverse Phases 1 & 2, Phases 1 & 5 are
still allowed concurrently. Lead-Lag only reverses the ring rotation.

Multiple Lead-Lag
Lead-Lag patterns can also be applied in order to reverse more than a single pair of
phases within a co-phase group. For example, if the normal sequence is:
Ring 1 1 2 3 4 8
Ring 2 5 6
and you want to cycle 8, 4, 3 rather than the normal 3, 4, 8, you can either modify the
sequence to use four cophase groups, such as:
Co-Phs Grp 1 Co-Phs Grp 2 Co-Phs Grp 3 Co-Phs Grp 4
Ring 1 1 2 8 4 3
Ring 2 5 6
OR, you can use three Lead-Lag pairs to perform the same function, as shown in
Figure 157.
Lead/Lag Patterns VALUE(1-16= PHS 1-16)
(Mode: 0=TOD/Coord, 1=Coord, 2=TOD
3=by Input, 4=Always On, 5=Always Off)
Patt Mode PH_S PH_S PH_S PH_S
1 1 4--8 3--8 3--4 1--1
2 0 1--1 1--1 1--1 1--1
3 0 1--1 1--1 1--1 1--1
4 0 1--1 1--1 1--1 1--1
Figure 157 – Multiple Lead-Lag pairs

Enhanced Options
Soft Flash
Soft Flash is an alternate method of flashing operation performed entirely by
controller outputs to the load switches.
Soft Flash under TS 1 and TS 2 Type 2

The standard UCF mode is performed by the controller by dropping CVM (Controller
Volt Monitor). This causes the Signal Monitor to put the intersection into flash. There
are mechanical flash transfer relays within the cabinet involved in this process to
transfer from load switch control to the cabinet flasher.
Soft Flash VALUE(0= DARK, 1= FL Y WIG

2= FL Y WAG, 3= FL R WIG, 4= FL R WAG)
UCF Soft Flash: Y 1 1 1 1 1 1 1
Phase 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
Mode 1 4 1 4
Overlap A B C D E F G H I J K L M N O P
Mode
Figure 158 – Soft Flash Setup screen
Since Soft Flash is implemented through load switches, there is no need for the flash
relay transfers to be utilized. Since it is controlled by software, there is flexibility to
provide different flash patterns. When Soft Flash is enabled and programmed
properly, it will be used for remote flash.
Note Standard UCF entry and exit must also be programmed (refer to UCF on page
150) . Enabling UCF Soft Flash simply tells the controller to use the Soft Flash
mode instead of dropping CVM to the monitor. Thus, to activate Soft Flash, enter a
‘Y’ for UCF Soft Flash.
Then select a Soft Flash mode value for each phase and overlap as follows:
Table 34 – Soft Flash Modes
Soft Flash Mode Description
0 or blank Dark
1 Flash Yellow WIG
2 Flash Yellow WAG
3 Flash Red WIG
4 Flash Red WAG
WIG-WAG operation provides alternating flashing signals (i.e. wig and wag are 180
degrees out of phase with each other).
If an invalid Soft Flash mode-phase/overlap configuration is programmed, the
controller will not go to UCF. An example of an invalid program is a program
containing conflicting flashing Yellow movements.

Typical Uses Of Soft Flash

Soft flash is typically used for one (or both) of the following reasons:
To reduce wear and tear on mechanical relays. This is especially true if the
intersection is placed in flash every night and comes out every morning.
To provide a different signal flash display when in UCF mode vs. cabinet
flash. For example, if the intersection fails and is placed in flash by the monitor,
an all red flash mode may be preferred. For nighttime UCF however, the
preferred flash mode might be flashing yellows and reds. This can only be
accomplished with soft flash because conventional UCF (dropping CVM) uses
the same flash as cabinet flash.
Soft Flash Limitations under TS 1

Unfortunately, it is not always possible to use Soft Flash in TS 1 if certain outputs are
set Dark. Examples include Peds that are monitored on separate channels that are
set to go Dark, or left turn phases set to go Dark. Additionally, not all monitors,
especially older ones, can tolerate soft flash. The problem in each case has to do with
the Red Fail recognition time of the conflict monitor.
Since Soft Flash is implemented strictly through the load switches, and no relay
transfers are involved, the monitor runs normally and must continue to “think”
everything is OK. The red monitoring function of the monitor typically remains
active.If a “red failure” is recognized by the monitor it will place the intersection in
cabinet flash and soft flash will be useless (the monitor will also require a reset).
Fortunately, most newer monitors can tolerate channels that flash because the signal
is off for less than the red fail recognition time. Some older ones, however, cannot.
Peds only present a problem when monitored on a separate channel and both Walk
and Don’t Walk are monitored. Red fail will then occur if the ped is turned completely
off. Peds are not a problem if the Walk only is monitored, either on a separate
channel where the red is tied high or in TS 1 Mode where the walk is the 4th input per
monitor channel. In these cases, the Ped channel can go dark without causing red
fail.
Note Some monitors do have a DC input that inhibits Red Fail monitoring. If this is the
case, the controller can drive this input with a clock output to defeat red fail
monitoring during soft flash.
Soft Flash under TS 2 Type 1

Soft Flash must be used in TS 2 Type 1 controllers. The TS 2 Type 1 3000 Series
controller does not have a CVM output; therefore, a selection of ‘N’ causes the
controller to think it has dropped CVM when, in fact, the controller has no such output.
Therefore, Soft Flash is a necessity.
Careful attention must be paid to programming requirements when programming UCF
Soft Flash.

Enhanced Options
Port 1 Communications for TS 2 Soft Flash

The Type O Command Frame from Controller to MMU via the RS-485 port will inform
the MMU that the controller is in planned flashing operation (i.e. Soft Flash or
Preemption Flash). This is done so that Red Failures (absence faults) do not occur
when the controller is in No Fault Flash operation when outputs are to be set Dark, or
if the controller’s flashing output does not satisfy the MMU’s Red Fail recognition time.


Chapter 4 — Detectors
This section explains how to configure and use a variety of traffic and pedestrian detectors with
the 3000 Series controllers. The following topics are discussed in detail in this chapter:
The Detector Menu, on page 164.

Assigning vehicle and pedestrian detectors to phases, on page 164.
Available detection modes, on page 166.
Detector timing, on page 169.
Switch and copy functions for detectors, on page 171.
Detection failure monitoring, on page 174.
System sensor assignments, on page 179.
Third car detection, on page 180.

DETECTOR MENU
The Detector Menu allows the user to define and configure various features of
Vehicle Detectors for a controller. The 3000 Controller allows 32 (64 with TS 2)
assignable detectors.
From the Controller Menu Select 4, Detectors....
Detector Menu
1. Veh. Assignment 6. Switch & Copy

2. Ped. Assignment 7. Fail Monitoring
3. Modes 8. System Sensor
4. Detector Times Assignments
5. Delay Inhibits
Figure 159 – Detector Menu
DETECTOR ASSIGNMENTS
Each of the 8 pedestrian and 32 (64 for TS 2) vehicle detectors can be selectively
assigned to 1 or more phases. Detector assignment is made by selecting one or
more phases for each detector by moving the cursor to the phase number and
pressing the Y/N key, or by simply pressing the phase number (1-9 = Phases 1-9,
SHIFT + 0-6 = Phases 10-16).
Selection 1, Vehicle Detector Assignments....
Detector Assignments Value(YES/NO)
1 1 1 1 1 1 1
DET\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
1 X
2 X
3 X
4 X
PGDN FOR MORE DETECTORS
Figure 160 – Detector Assignments screen (aka ‘Veh. Assignments’)
PGDN for detectors 5-32 (TS 1) or 5-64 (TS 2)

Detector Assignments
By default, detector 1 is assigned to phase 1, detector 2 to phase 2, etc. However,

operation is not limited to just these assignments. A detector can be assigned to any
phase or combination of phases.
Ped Det. Assignments
Value(YES/NO)
1 1 1 1 1 1 1
DET\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
1 X
2 X
3 X
4 X
Figure 161 – Pedestrian Detector Assignments screen
Ped detectors can be assigned in similar fashion.

DETECTION MODES
Each of the 32 (64 for TS 2) detectors can be assigned to operate in one of five
modes. The user programs a detector mode for each detector and Delay, Stretch and
Stop Bar Times for detectors requiring these parameters.
Detector Mode (0-4=CALL/EXT, CALLING,

STR/DELAY, STOP BAR 1/2) 1 1 1 1 1 1 1
DET 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
Mode 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
1 1 1 2 2 2 2 2 2 2 2 2 2 3 3 3
DET 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2
Mode 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Figure 162 – Detection Modes screen
PGDN for detectors 33-64 (TS 2 only).
Call/Extend – Mode 0
A call/extend detector is a normal NEMA detector. The detector calls its programmed
phases when the phases are not green, and extends when they are green (passage
interval).
Typical use:
For normal stop bar detectors which are allowed to both call and extend.
Call – Mode 1
A call detector will call its programmed phases when the phases are not green, but
will not extend the passage timer during the phase greens.
Typical use:
Where the detector is to call only. Typically used when there are both stop bar and
set back loops. This can be done in one of two ways:
The first way is to set the passage time based on the stop bar loop and set it to
a normal call and extend, then set the set back loop as a call detector. The set
back is then used to simply place an early call for service but does not extend.
The second way is to set the passage time based on the set back loop and set it
to a normal call and extend, then set the set stop bar loop as a call detector.
The stop bar loop is then used as a fail-safe to ensure that a vehicle gets a call
for green, but does not extend.
Stretch/Delay – Mode 2
A Stretch/Delay detector extends the detector call by a programmed stretch value
when the programmed phase is green and delays the detector call by the delay value
when the programmed phase is not green. This type of detector mode requires

Detection Modes
programming of the stretch (0-25.5 sec) and delay (0-255 sec) times. A detector can
be just stretch or just delay (or both) by the time value settings (a zero value for
stretch and a non-zero value for delay = a delay detector).
Note Stretch and delay can be disabled via TOD circuits (See Appendix A). If Delay
Detector Disable is active, the controller uses ZERO for all detector delay times.
Likewise for stretch times if Stretch Detector Disable is active.
Typical use:
Delay is typically used for side streets with right on red allowed or for protected/
permissive left turns (such as 5 section heads). Delays placing of call so that when
the controller is resting in main street green, it will not immediately clear for vehicle(s)
that could have proceeded anyway, or vehicle(s) that have already proceeded by the
time the left turn starts.
Delay can also be used to prevent momentary calls from being locked in memory
(Non-Lock = N) when wrong-way vehicles pass over the detector (left turners make a
sharp turn and pass over left turn detector). Rather than enable Non-Lock to stop
wrong-way calls and risk stranding vehicles that stop beyond the stop bar, the delay
can be used to stop wrong-way false calls.
Stretch is typically used when there are detectors of varying distances from the stop
bar but on the same phase. Since there is only one passage timer in effect at any
one time per phase, the passage time can be set based on the closer detectors and
stretch can be used to add time to detectors that are farther away.
Stop Bar – Modes 3 and 4

Mode 3 is the Stop Bar 1 detector mode. Stop Bar 1 operates as follows:
1. When the phase associated with a Stop Bar detector turns green, the stop bar
timer will begin timing. As long as there is a call present on the detector, and
the stop bar timer has not reached zero, the phase will be extended (the
passage timer will remain reset).
2. If there is any break in demand (no call active on the detector) or the stop bar
timer reaches zero, the detector will be disconnected for the duration of green
on that phase.
3. When the phase is not green, the detector will place calls on the phase.
Typical use:
For stop bar detectors which are fairly long* and are used in applications where there
are both stop bar detectors and set back loops. The passage timer is then set based
on the set back loop and tends to be fairly long. Gap reduction may be used (and
probably should be). The stop bar is used to place calls and then to exhaust the
queue. Once the queue exhausts or the stop bar timer times out, the stop bar
detector is disconnected and only the set back detector can extend. This increases
* Loops long enough so that there is usually no break in demand while exhausting the queue.

efficiency, since the last car will not initiate yet another extension while crossing the
stop bar and adding unnecessary green time.
Mode 4 is the Stop Bar 2 detector mode. Stop Bar 2 is the same as Stop Bar 1
except that detector actuations will reset the timer. It therefore does not require
continuous calls to stops itself from being disconnected.
Typical use:
Same as Stop Bar 1 except the loops are typically shorter and there would likely be
breaks in demand even while exhausting the queue.
Stop Bar operation can be disabled by a TOD circuit. When disabled, all STOP BAR
detectors will function in the normal CALL/EXTEND mode.
Detector Lock Mode

It may be desirable to provide detector locking at the detector level rather than at the
phase level as programmed in the Phase Recalls Menu. This might be the case
when there are several detectors calling a phase and some require lock mode
operation and some require non-lock mode. Program ‘Y’ for lock mode for each
desired detector. The call is locked upon actuation until the assigned phase goes
green.
When providing lock vs. non-lock mode at the detector level, the phase level (Phase
Recalls Menu) must be set to the Non-Lock Mode. Otherwise all calls are locked
regardless of detector level programming.
Note If a detector calls more than one phase, the lock is cleared as soon as the first of
any of the assigned phases go green.
Detector lock screen (MM-3-1-4-3-PGDN -PGDN )…..

Detector Lock VALUE(YES/NO)
1 1 1 1 1 1 1
DET 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
Lock X
1 1 1 2 2 2 2 2 2 2 2 2 2 3 3 3
DET 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2
Lock
Figure 163 – Detector Lock Setup screen
PGDN for detectors 33-64 (TS 2 units only).

Detector Times (delay, stretch/stop bar)
DETECTOR TIMES (DELAY, STRETCH/STOP BAR)

When operated as a stretch, delay, or stop bar detector, there are associated times
that must be programmed as well.
MM-3-1-4-4….
TP:1 Det Delay, Stretch/Stop Bar Times

Det 1 2 3 4 5 6 7 8
Delay 0 0 0 0 0 0 0 0
Str/Stp 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
Det 9 10 11 12 13 14 15 16
Delay 0 0 0 0 0 0 0 0
Str/Stp 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
Figure 164 – Detector Timing Setup screen
PGDN for detectors 17 through 32 (17 through 64 for TS 2 controllers), and continue
paging down for timing plans 2 and 3.
Program appropriate values for delay, stretch or stop bar. The value fields are the
same for stretch or stop bar, the function of the value is determined by the mode
setting. A detector can be just stretch or just delay (or both) by the time value
settings. For example, a zero value for stretch and a non-zero value for delay results
in a delay detector only.
Note that delay and stretch/stop bar times are per detector timing plan 1-3. These
are independent of the phase timing plans and can be used for implementing
alternate stretch and delay times as well as delay inhibits via the time of day
scheduler or by assignment of clock ckts. to Cycle/Split combinations. Detector plan 1
is by default and plans 2 and 3 are called by clock ckts 122 and 123. Program only
TP1 if no TOD or COS changes are desired. Plans 2 and 3 only apply to detectors 1-
12.
Detector Delay Inhibits

The Delay Inhibit feature allows detector delay to be defeated when certain phases
are active. For each detector, enter the phase or phases that will deactivate delay for
that detector by placing an ‘X’ in the column for the phase.
MM-3-1-4-5….
Detector Delay Inhibits VALUE(YES/NO)
Plan 1 1 1 1 1 1 1 1
DET\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
1 X
2
3
4
PgDn FOR More Detectors
Figure 165 – Detector Delay Inhibits screen

Note The Delay Inhibit feature is provided only for Detectors 1-12 (for each of the
three detector plans.)
Typical use:
On protected/permissive left turns where the side street phase inhibits the left turn
phase delay. For example, say in a 3 phase controller, phase 1 is the main street left
turn, phase 2 is the main street thru, and phase 3 is the side street. The goal is to
provide delay only when resting in the main street (ph 2), but not when in the side
street (ph 3).
If delay is unconditioned by inhibits, the left turn will often be skipped even at busy
times if the left turn vehicles arrive towards the end of phase 3. By inhibiting the delay
during phase 3, this will not occur. The programming in this case would be as shown
on the above example screen.
Delay Inhibits are per detector timing plan 1-3. These are independent of the phase
timing plans and can be used for implementing alternate inhibit combinations by the
time of day scheduler or by assignment of clock ckts. to Cycle/Offset/Split
combinations. Program only TP1 if no TOD or COS changes are desired.
Also note that detector delay inhibits are not provided for all 32 detectors (64 for TS 2)
in detector plan 1. Detector plans 1, 2, and 3 only include delay inhibits for detectors
1 through 12.

Detector Switch and Copy
DETECTOR SWITCH AND COPY

Detector Switch and Copy allows calls on a specific phase to be switched or copied to
a different phase during the green interval(s) of a specified group of phases. There
are 16 such unique detector switch and copy plans.
Detector Switching disconnects calls from the original phase and transfers them to
the secondary phase.
Detector Copy is similar to Detector Switching, except that the original call is kept on
the ‘copy from’ phase and an additional call is placed on the ‘copy to’ phase.
Det Switch/Copy Enables (Value Yes/No)
Detector Switching Enable : N
Detector Copy Group 1 Enable : N
Detector Copy Group 2 Input Enable : N
Det Copy Grp 2 plans 1-16 used instead

Of Gp1 if enable = Y and input active.
--PgDn for Det sw & copy patterns 1-16--
Figure 166 – Detector Switch/Copy Setup screen
Switch And Copy Enables

The first screen sets the enable modes of switch and copy.
For Detector Switching, there is one set of enable phases for each of the 16
switch/copy patterns. Set Detector Switching Enable = “Y” to allow detector
switching to operate. The Actual switching is then determined by the pattern
screens that follow.
For Detector Copy, there are two groups of enable phases for each of the
16 patterns. The first is enabled by setting Detector Copy Group 1 Enable = “Y”
The second is enabled by setting Detector Copy Group 2 Input Enable = “Y” and
the activating the input (or clock circuit). Thus, to operate alternate copy
patterns, set both = “Y” and activate the input (or clock circuit) when Group 2 is
desired (only one is in effect at a time). The actual copying is then determined
by the pattern screens that follow.
Detector Switch and Copy Clock Disable

Both detector switching and detector copy can be disabled by TOD circuit. When the
corresponding circuit is active, no switch or copy functions will be performed.

Switch And Copy Pattern Screens

Each screen defines a set of phase patterns and “FROM” and “TO” phases. The
phases enabled (X) on the switch row determine the set of greens that are required
for calls to switch from the “FROM” phase to the “TO” phase under the “Swtch”
column (lower right portion of the display.) The machine state must exactly match the
programmed phase greens for the switching to occur (except for TS 2 units which
only require “From and To” phases for switching.) The Switch and Copy pattern
number must match the number of the detector’s assigned phase. For example, to
switch from Phase 1 to Phase 6, detector pattern number 1 must be used. To switch
from Phase 6 to Phase 1, detector plan number 6 must be used. This pattern
assignment also applies to the Copy feature, but for patterns 1 through 16 only.
Does not appear for TS 2. Switch phase greens do not have

to be specified--only From & To phases.
Det Sw & Copy 1 of 64 1 1 1 1 1 1 1

Ph Grns 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
Switch Important Note:
G1 Copy Number corresponds
G2 Copy to detector number
Sw or Copy Per --> |(Ph’s) Swtch G1C G2C
When Above Are grn |From Ph: 0 0 0
(Pgdn For More) | To Ph: 0 0 0
Figure 167 – Switch Setting
Note If a Phase 2 Switch to Phase 5 is programmed on Pattern page 2, no switch will

occur.
Use PGDN to see patterns 2 through 16.

The copy patterns are programmed in the same way except that there are two
possible groups of enable phases and two possible “FROM” and “TO” phase sets per
screen (G1C = Group 1 copy phases, G2C = Group 2 copy phases.) The group in
effect is determined by the enables and the state of the copy input (see enables
description above). Only one copy group from each pattern screen is in effect at any
one time.
Multiple Patterns Active: It should be noted that the each of 16 pattern screens
represents a unique set of conditions that result in a certain switch and/or copy
outcome. These outcomes are then simply determined by the state of controller
phases and all patterns are taken into account simultaneously. It is then possible that
more than one pattern may match at any one time. In this sense, they are not like
“plans” where only one is active at a time. The copy group selection simply
determines which copy pattern set is used within each pattern screen.
Detector Switching Example: Say that a left lane is a protected/permissive left turn
lane, where phase 1 is the protected phase and phase 6 is the permissive phase (a 5
section head signal is typically used). Detector switching can be used to switch the

Detector Switch and Copy
demand from phase 1 to phase 6 after phase 1 clears. Thus, the left lane detector
calls phase 1 and extends phase 1, but switches to extend phase 6 after phase 1 is
completed. This allows the permissive portion of the movement (phase 6) to be
extended by the left turn lane detection.
Note that the TS 2 controller unit does the detector switching simply when the “from”
phase is not active and the “to” phase is active (selecting phase greens not required).

DETECTOR FAILURE MONITORING

Failure Monitoring allows the controller to monitor the 32 (64 for TS 2) detectors for
possible failure conditions. Detectors are monitored for Absence of Calls, Locked
Calls, Minimum Presence failures and Erratic Operation.
Detector Fail Monitor Menu
1. Abs/Erratic Enab 4.Detector Loop

2. Lock, Absence Times Length
3. Minimum Presence/ 5.Failed detector
Erratic Counts/Min Phase
Recall/Max
6.Ped Det Diag
Figure 168 – Detector Failure Monitoring Menu
Absence Monitor Time Of Day, Erratic Monitor Enable

Absence of Call monitoring checks for no activity on detector inputs. Since this might
be a normal occurrence in the early morning hours, a start hour and stop hour can be
programmed. Absence monitoring is only performed between these times. These
values are programmed with the military hour only (i.e. 6 = 6AM, 23 = 11PM)
ABSENCE/ERRATIC ENABLE
START ABSENCE MONITORING HOUR(0-23): 6

END ABSENCE MONITORING HOUR(0-23): 23
ERRATIC ENABLE: Y
VALUE (YES/NO)
Figure 169 – Detector Absence/Erratic Behavior Monitoring

Erratic enable (Y) allows erratic (chattering) input detector monitoring on all detectors.
For TS 1 the condition is fixed; if the count volume exceeds 8 counts in a 10 second
period of time, the detector is considered to be chattering and will be logged as a
failed detector. For TS 2 the condition is user definable—see Erratic Counts per
minute.
Note Absence of Call, Locked Call and Minimum Presence Monitoring can be disabled
for any detector by programming a zero value for that function.

Detector Failure Monitoring
Lock Times
Program a value between 0 and 255 minutes for Locked Call Monitoring. If a detector
is active continuously for this many minutes, a locked call failure is recorded. Thirty
minutes is a common value for this function.
LOCK 1: 0 2: 0 3: 0 4: 0
TIMES: 5: 0 6: 0 7: 0 8: 0
(0-255 9: 0 10: 0 11: 0 12: 0
MIN) 13: 0 14: 0 15: 0 16: 0
17: 0 18: 0 19: 0 20: 0
21: 0 22: 0 23: 0 24: 0
25: 0 26: 0 27: 0 28: 0
29: 0 30: 0 31: 0 32: 0
Figure 170 – Locked Call Monitoring Setup screen
PGDN for more Lock times and Absence of Call times.
Absence Of Call
Program a value between 0 and 255 minutes for Absence of Call Monitoring. If a
detector does not receive a single detection within this time period, an absence of call
failure is recorded (also see absence monitor time of day programming above). Thirty
minutes is a common value for this function—depending on the Absence Monitor
Time Of Day setting above.
ABSENCE 1: 0 2: 0 3: 0 4: 0
TIMES: 5: 0 6: 0 7: 0 8: 0
(0-255 9: 0 10: 0 11: 0 12: 0
MIN) 13: 0 14: 0 15: 0 16: 0
17: 0 18: 0 19: 0 20: 0
21: 0 22: 0 23: 0 24: 0
25: 0 26: 0 27: 0 28: 0
29: 0 30: 0 31: 0 32: 0
Figure 171 – ‘Absence of Call’ Monitoring Setup screen

Minimum Presence
Program a value between 0 and 255 milliseconds for Minimum Presence Monitoring.
If call is received for a shorter time period than this value, a minimum presence failure
is recorded.
For example, a small car traveling 70 mph over a 6 foot loop will generate a pulse of
somewhat less than 200 ms or so. This is about as short a pulse as should be
detected, so the range of about 50 - 150 ms is good value range for minimum
presence. Minimum Presence is only available for detectors 1 through 32. This is
true for both TS 1 and TS 2 controllers.
MINIMUM 1: 0 2: 0 3: 0 4: 0
PRESENCE 5: 0 6: 0 7: 0 8: 0
(0-255 9: 0 10: 0 11: 0 12: 0
MILLI- 13: 0 14: 0 15: 0 16: 0
SECONDS) 17: 0 18: 0 19: 0 20: 0
21: 0 22: 0 23: 0 24: 0
25: 0 26: 0 27: 0 28: 0
29: 0 30: 0 31: 0 32: 0
Figure 172 – Minimum Presence Monitoring Setup screen
Erratic Counts Per Minute (TS 2)

Program a value between 0 and 255 for the minimum number of erratic counts in a
minute to register an Erratic failure. This applies to TS 2 mode only.
PGDN from Minimum Presence times…
ERRATIC 1: 0 2: 0 3: 0 4: 0
COUNTS/ 5: 0 6: 0 7: 0 8: 0
MIN 9: 0 10: 0 11: 0 12: 0
(0-255) 13: 0 14: 0 15: 0 16: 0
17: 0 18: 0 19: 0 20: 0
21: 0 22: 0 23: 0 24: 0
25: 0 26: 0 27: 0 28: 0
29: 0 30: 0 31: 0 32: 0
Figure 173 – Erratic Counts-Per-Minute Monitoring Setup screen
PGDN for more Erratic Counts per minute (TS 2 only).

Detector Failure Monitoring
Loop Length
Program the Loop length for each detector to be monitored. The Loop length is used
in Speed calculations, as well as in Headway determination and other MOE's. The
Loop Length range is 0 to 255 feet. Note that the single loop speed calculation is
approximate and is not as accurate as two detector speed trap measurements. These
values only apply to the first 32 detectors of a TS 2 controller.
Detector 1: 0 2: 0 3: 0 4: 0
Loop 5: 0 6: 0 7: 0 8: 0
Length: 9: 0 10: 0 11: 0 12: 0
(0-255 13: 0 14: 0 15: 0 16: 0
FT) 17: 0 18: 0 19: 0 20: 0
21: 0 22: 0 23: 0 24: 0
25: 0 26: 0 27: 0 28: 0
29: 0 30: 0 31: 0 32: 0
Figure 174 – Detector Loop Length screen
Failed Detector Phase and Fail Max Recall Times

Fail Max Recall Times can be placed on selected phases as a way to prepare for a
future failed detector. The sixteen different timing periods can be programmed on
the following screen. Valid values run from 0 to 255 seconds.
FAIL MAX 1: O 2: 0 3: 0 4: 0
RCL TIME 5: O 6: 0 7: 0 8: 0
(0-255) 9: 0 10: 0 11: 0 12: 0
13: O 14: 0 15: 0 16: 0
PGDN FOR MORE RECALLS

Figure 175 – Failed Max Recall Time screen
To use this feature, first program the fail max recall max times used for each phase....
FAILED DET MAX RECALL PHS VALUE(YES/NO)
1 1 1 1 1 1 1
DET\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
1 X
2
3
4
Figure 176 – Failed Detector Max Recall Settings
Then page down to the detector to phase assignments.....

The 2nd page assigns the phases that are to be placed on fail max recall for up to 32
(64 for TS 2) detectors, should the detector fail. If the detector recovers from the
failed mode, the controller will resume normal operation (fail max recalls will be
removed and normal max times used).
Use of Fail Max Recall and times:
If a detector fails it is prudent to place the associated phase on Max Recall. However,
since the normal max may be undesirably long, a special “Fail Max Recall” time is
provided. The Fail Max Time is only used if the phase is placed in Fail Max Recall.
Pedestrian Detector Diagnostics

PED DETECTOR DIAGNOSTICS
(VALUE: 0-255 SECS)
DETECTOR 1 2 3 4 5 6 7 8
ABSENCE 0 0 0 0 0 0 0 0
LOCK 0 0 0 0 0 0 0 0
(VALUE: 0-255 COUNTS/MIN)
ERRATIC 0 0 0 0 0 0 0 0
Figure 177 – Pedestrian Detector Diagnostics Setup screen

Pedestrian detectors 1-8 can also be programmed for failure monitoring. Pedestrian
detector diagnostics involves the same parameters as previously discussed for
vehicle detectors, but they are provided all on one screen due to the limited number
of ped detectors.
Note that the ped will be placed on recall if the associated detector fails. The call is
removed if the detector returns to normal.

System Sensor Assignment
SYSTEM SENSOR ASSIGNMENT

The 3000 Controller has 16 system sensors available for closed loop operation. A
system sensor is a detector that is used to collect volume, occupancy and speed
data. These data collections are reported to the master and/or central system and can
be used for traffic responsive calculations, capture incident detection, etc.
System Sensor Assignments

Local Detector Value(0-32)
SYS 1 2 3 4 5 6 7 8
17 0 18 19 0 0 0 0
SYS 9 10 11 12 13 14 15 16
0 0 0 0 0 0 0 0
Figure 178 – System Sensor Assignment screen

These 16 sensors can be allocated from any of the first 32 detectors. To assign a
detector to a system sensor, enter the detector number under the sensor number it is
assigned to. Assigning a detector to a system sensor does not prevent it from
functioning as a normal detector. If the 3000 Series controller is used in a closed loop
system with the 3800EL master, sensors 1-8 are used for system sensors, and
sensors 9-16 are used for graphics channels.

THIRD CAR DETECTION FEATURE

This is a feature implemented on Time of Day timing circuit 124. There is no
programming screen in the 3000 Series controller interface for this feature.
This feature uses “detector pairs” to place a call for left turn phases when both
detectors are occupied at the same time. Once the left turn phase is green, both
detectors extend the phase. Time of Day Circuit “3CD” (CKT 124) activates Third Car
Detection when the appropriate detector configuration is programmed as described in
this table:
Table 35 – Detector configuration for Third Car Detection
Detectors Phase Assignment
1, 13 1
3, 14 3
5, 15 5
7, 16 7
Note The controller must be power cycled for Circuit 124 to go into effect.
Typical Use:
This feature is used to prevent a call being registered for a protected left turn until
three vehicles are queued. One detector is at the stop bar and the other is placed
three car lengths back. The idea behind this feature is that one or two cars can be
served from just the permissive left turn indication, rather than having to time out a
protected left turn.

Chapter 5 — Overlaps
This section explains the configuration and usage of overlaps, or signal outputs resulting from
a combination of phases rather than any single phase or detector state. The following topics
are discussed in detail in this chapter:
A general description of the use of Overlaps, on page 182.

How to program vehicle overlaps, on page 185.
Double-Clearing overlaps, on page 192.
Pedestrian overlaps, on page 197.
The use of advanced warning logic in TS 2 controllers, on page 202.
Using Leading and Advance Green overlaps, on page 207.
Inhibiting overlaps using TOD circuits, on page 209.

GENERAL DESCRIPTION
An Overlap is a set of G-Y-R outputs that are associated with one or more phases.
The overlap forms a separate movement that derives its operation from its assigned
phases, commonly called “parent phases” or “included phases.” A typical overlap will
be active during two or more parent phases such that if any parent is green, the
overlap is green as well.
If the controller makes a “phase next” decision to clear from one parent phase to
another, the overlap will remain green throughout. If the controller decides to clear
from a parent to a non-parent, the overlap will clear with the parent using the parent’s
yellow and red duration. Furthermore, in multiple ring configurations, more than one
parent phase may be active at a given time. If a “phase next” decision is made to
clear from a parent to a non-parent, and a parent phase is green in another ring, the
Overlap remains green.
The figure below illustrates an overlap that may be used in controllers with only
single-ring capability:
Figure 179 – Simple Overlap

The overlap is “A” which would be programmed as a simple 1 + 2 overlap. In special
cases, overlaps can be used to provide double clearing capability on a phase. Also,
the 3000 Controller has the capability of providing pedestrian overlaps.

General Description
phase 2
phase 5
phase 4
phase 7
phase 3
phase 8
(OL A = φ6 + φ7)
phase 1
overlap A
phase 6
Figure 180 – Typical multi-ring overlap

Overlaps can either be generated by an overlap card which plugs into the I/O board
or internally by programming the interface. The card can only control overlaps A
through D, and is rarely used any more.
Overlap Channels and Compatibility

Overlap operation is sometimes a source of confusion for users, especially when it
comes to overlap compatibility. To help clear this confusion, the figure below shows a
typical assignment of phases and overlaps to monitor channels for the example
phasing as applied in a typical cabinet. Load switches 1-5 are shown with typical
assignments.
Figure 181 – Typical Load Switch assignments

Note that the overlap is on a separate load switch which is driven by OVERLAP A,
which in turn has been assigned phases 1+2 as parents. CH1-CH5 indicates the
Conflict Monitor (or MMU) channel assignments.
Note also that the appropriate channel compatibilities are:
1-5
2-5

The channel compatibilities are definitely not 1+2 as is sometimes thought. It is

important to be able to make the distinction between the overlap and its
compatibilities vs. its parents and their compatibilities. The overlap is a separate
movement and its parents are not necessarily compatible with each other (and are
usually not).

Overlap Programming
OVERLAP PROGRAMMING
Overlaps include a variety of modes of operation and uses. To get to this menu, go to
the Controller menu and choose option 5. Overlaps. The full path is MM > 3.Change
Data > 1.Controller > 5.Overlaps.
Overlap Menu
1. Assignments & Types

2. Startup, Card & Alternate Flash
3. Double Clear (Trailing)
4. Pedestrian Overlaps
5. Advanced Warning Logic
6. Leading/Advance Green Overlaps
Figure 182 – Overlap Menu
This menu is used to set up and modify all of the parameters for vehicle and
pedestrian overlaps. The operation of these controls are described in the next
sections.
Assignments & Types

Basic overlap parents and modes are programmed from this menu. The 3000 Series
controller is capable of providing 16 overlaps. To distinguish from Phases 1-16, these
overlaps are referenced as overlaps A through P. Each page of the Overlap
programming section contains all of the information needed to program one Overlap.
To access a specific overlap screen, move the cursor to the top by pressing the
SHIFT and HOME keys together, and enter the number that corresponds to the
overlap to be programmed (1 for A, 2 for B and so on). For example, to see overlap
12 (aka overlap ‘L’), place the cursor in the ‘1’ field and enter 1,2 and press ENTER .
Or you can press the PGUP and PGDN keys to navigate between the 16 available
overlaps.
Assign O/L A (1 Of 16) 1 1 1 1 1 1 1

Phase 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
Parents
Fl Enab
MOD PHS
Del Enab
O/L Type: 0 STANDARD Fl Code: 0
Grn: 0 Yel: 0.0 Red: 0.0 Del: 0.0
Figure 183 – Individual overlap programming screen 1
To program the parent phases of an overlap, move the cursor to the appropriate line
and select the phases by either pressing the phase numbers or by moving the cursor
under a phase and pressing the Y/N key. An ‘X’ indicates that a phase has been
selected. For standard overlaps, this is all the programming required.

The signal outputs for overlaps A through D are available on the standard MS-B
connector. Overlaps E through P are generally made available by use of I/O Steering
(see page 380), or by BIU Mapping on a TS 2 Type 1 controller (page 400).
Overlap Assignments and Types Parameters

PARENTS—Phases during which the overlap is allowed to be green (see Overlap
general description previous). For standard overlaps, only the parent phases need to
be programmed. The flash code and type are both set = 0. Standard overlaps behave
in the basic overlap mode with no special logic or timing.
FL ENAB—Flash Enable and the Flash Code (near the bottom of the screen) work
together. The Flash Enable row determines which parent phases will trigger the
overlap to flash. These are called the overlap’s ‘flash parent’. The way that this trigger
occurs is determined by the selected Flash Code. The flash code defines how the
overlap will synchronize with this ‘flash parent.’ (See Flash Codes on page 189.)
Phase Modifiers Row

The row of settings on this screen just beneath “FL Enab” is used to display per-
phase on-off settings that change depending on the type of Overlap selected. The
label for the row changes to indicate what is being set here. This row can contain
values for Phase Modifier (MOD PHS), Not Ped settings (NOT PED), Left-turn
adjustment (ADJ LT), or Through adjustment (ADJ Thru). Each modifier type is
described below:
MOD PHS—This is the label on the phase modifier row when the overlap type is set
to 0 (Standard) or 9 (Include All). It has different functions for Standard and Include
All operation.
In Standard mode, a selection in this row under a parent phase causes special
overlap operation for (1) 5-Section “Dallas-style” Protection-Permissive Left Turn
operation, and (2) 4-Section Flashing Yellow Left Turn Arrow Protected-Permissive
operation. Contact Peek Tech Support for setup details. (Refer to page 2.)
In Include All mode (Overlap mode 9), a selection in this MOD PHS row under a
parent phase tells the overlap to follow this phase off even if one or more of the
other parent phases are still green. If the selection is under a non-parent phase,
this modifier tells the overlap to darken whenever this phase is on, even if one
or more of its parent phases are green.
NOT PED—The modifier row shows this label when the overlap type is set to Mode 2
(Not Ped). This row then determines which parent phases are treated as Not Ped
parents. When this condition is set for a phase, it is disabled as a parent when its Ped
movement is active (during Walk and Ped Clearance.) Typically used when a right
turn overlap turns into pedestrian movements (i.e. the ped phase is the Not Ped
parent.) To program for Not Ped mode, set the overlap type to 2, then program the
overlap parents normally—including any that will operate as Not Ped parent phases.
Then add ‘X’s to the Not Ped modifier row under these Not Ped phases to condition
the overlap during the normal parent. In addition, Green, Yellow, and Red times are
used to clear the overlap and serve ped calls on the “Not-Ped Phase” while the
parent phase’s vehicle movement remains green.

Overlap Programming
ADJ LT—This modifier row label appears when the overlap type is set to either 3
(Five-section Left Turn, single indication only) or 4 (Five-section Left Turn, single
indication, red over arrows.) The settings in this row then determine which parent
phases will allow the overlap to operate with ‘Five-section head’ logic. All overlap
parents are programmed normally, including any that will enable five-section head
logic. These five-section head modifiers are added to condition the overlap during the
normal parent.
ADJ THRU — This modifier row label appears when the overlap type is set to either 5
(Five-section Left Turn, dual indication except yellow) or 6 (Not Right Turn On
Through Green.)
Type 5 is commonly known as the Illinois Left Turn configuration, which requires that
the overlap drives the left turn movement on a five section signal. To accomplish this,
the adjacent through phase must be specified using this modifier setting.
Type 6 is commonly known as the Illinois Right Turn configuration, which requires
that the overlap drives the right turn movement. In this mode, the green right turn
arrow is not allowed to be active when the adjacent through phase is green. So this
modifier row is used to specify which of the parent phases is this adjacent through
phase.
Delay Enable
The DEL Enab row on the Overlap programming screen determines if a delay is
applied to the start of the overlap. The delay would be relative to the parent phase
turning Green. The delay value set at the bottom of the screen determines how many
seconds the overlap green will wait before starting each time it is triggered by that
parent phase.
If an overlap is set up for both delay and leading timing on a given phase, the delay
timing will occur and the leading time will be ignored.
Note Delay timing is only available for overlaps A through H. Overlaps I through P
do not have the DEL Enab row, nor the Del time at the bottom of the screen.
1 GRN 1 YEL 1 RED 2 GRN

A RED A DELAY A GRN
Figure 184 – Timing diagram of an overlap programmed with a delay

Overlap Type
The type mode determines the logic that will be used by the overlap. The options are
shown in . Each type is described in more detail below the table.
Table 36 – Type of Overlap
Mode Overlap Type
0 Standard
1 Not Vehicle (Not available in the current firmware)
2 Not Ped
3 Five-section Left Turn, single indication only
4 Five-section Left Turn, single indication, red over arrows
5 Five-section Left Turn, dual indication except yellow
6 Not ‘Right Turn On Through Green’ (Illlinois right turn)
7 Walk Overlap Red
8 Walk Overlap Dark
9 Include All
Mode 0 — This is the Standard overlap mode. The phase modifer row displays MOD
PHS and has different intents for parent and non-parent phases, as described in the
‘Phase Modifiers Row:MOD PHS’ topic.
Mode 1 — This is the Not Vehicle overlap mode, but it is not currently implemented.
Mode 2 — This is the Not Ped mode. When a phase is conditioned as a “not ped”
parent, that phase is disabled as a parent when its ped movement is active (Walk +
Ped clearance.) See the ‘Phase Modifiers Row: NOT PED’ topic, as described above.
Mode 3 — This option only allows one signal in the five-section head to be active at a
time. In this mode, it is assumed that an overlap drives the five-section ball
indications, and the left turn phase that is adjacent to it must be specified on the ADJ
LT line by enabling that phase. The overlap operates as a Standard Overlap, except
when the ADJ LT phase is Green or Yellow, in which case the overlap is Dark.
Mode 4 — Mode 4 is similar to mode 3 except that the red indication is allowed to be
active with either of the yellow or green left turn arrows. The adjacent left turn phase
must be specified as in mode 3. Modes 3 and 4 are also known as Oklahoma left
turn logic.
Note In Modes 3 and 4, the MMU Red Input associated with the Overlap
must be tied to 120 VAC to prevent Red Failure when Overlap goes
Dark. Dual Indication must also be disabled so that G or Y with R
does not cause a fault.
Mode 5 — This mode allows dual indications except in the case of dual yellows. In
other words, any of the through indications are permitted with either of the left turn
arrows except for the yellow left turn arrow and the through yellow. This case
requires that an overlap drive the left turn. Therefore the adjacent through phase must

Overlap Programming
be specified on the ADJ THRU modifier line. This is commonly known as Illinois left
turn logic.
Mode 6 — This is also called Illinois right turn logic. In this mode the green arrow is
not allowed to be active when the adjacent through phase is green. The overlap is
assumed to be the right turn (generally the adjacent through and a left turn across the
barrier are parent phases) and the ADJ THRU modifier line is used to specify which of
these is the adjacent through phase.
Note In Modes 5 and 6, the MMU Channel associated with the Overlap
must have Yellow Monitoring Disabled, because the Overlap goes
straight from Green to Red.
Mode 7 — This O/L Type was added to the firmware in version 3.6 and is the WALK
OL RED mode. Mode 7 operates the same way as the Not Ped Overlap, except that
during the Ped Clearance interval of any phases programmed with the “MIN WALK”
entry, the Overlap will turn green. (The Not Ped (Type 2) Overlap does not turn the
Overlap green until the Ped Clearance finishes.)
Mode 8 — This O/L Type was added to the firmware in version 3.6 and is the WALK
OL DARK mode. Mode 8 operates in the same manner as Mode 7, except that during
the Walk interval of any phases programmed with the “MIN WALK” entry, the Overlap
signal will go dark.
Mode 9 — This is the INCLUDE ALL overlap type, which was added to the controller
in the version 3.6.2 firmware. This mode tells the overlap not to turn green until ALL
of its parent phases are green. The phase modifier row displays MOD PHS and
serves different functions for parent and non-parent phases. (See the Phase Modifier
Rows:MOD PHS topic for more details.)
Flash Codes
For an overlap to flash, it must first have a flash parent selected. This is done by
placing an X in the FL Enab row below the desired flash parent. When the overlap
phase matches the color of the flash parent phase, the overlap flashes. The color in
the flash parent that determines if the overlap flashes is set using this Flash Code.
The flash codes are defined in the table below.
Table 37 – Flash Codes
Code Flash (this color) if the Flash Parent is (this color) and the overlap
matches (this color):
0 None
1 Green
2 Yellow
3 Green or Yellow
4 Red
5 Red or Green
6 Red or Yellow
7 All (Red, Yellow, or Green)

For example, a flash code of 2 means to flash the overlap in yellow if the parent
phase is yellow AND the flash parent is yellow. The color of the overlap is determined
by the parent phase, NOT by the flash parent phase. So, in this scenario, if the parent
phase is green, the overlap will be a steady green; the overlap will not flash even if
the flash parent is yellow.
Note that the overlap flash rate is 1 Hz unless an alternate flash rate is specified on
the Green, Yellow, Red Timings screen. (See page 190.)
Hint: Using Overlap Flash Enable and Flash Codes

You may wish to set an overlap to flash during some parent phases, but not during
others. To program the overlap for this, set the flash code as desired, then program
the overlap parent phases as you normally would, but include any that you want to
use to enable overlap flashing. Then add ‘X’s to the Flash enable row to further
condition the overlap during the normal parent.
Note Phase enables do not pertain to Flash Code 4, since code 4 is the red flash
code. In such a situation, the overlap is red only when none of its parents are
active anyway.
Green, Yellow, Red Timings

The timers at the bottom of the screen determine how long (in seconds) the overlap
spends in green, yellow, and red, at a minimum. If these values are left at 0 seconds
(or 0.0 seconds in the case of Yellow and Red) then the parent phase’s timings will be
used for these overlap segments.
The Green time value is the minimum number of seconds that the overlap must
spend in green, and the parent phase cannot leave its green until this period has
ended. The yellow and red are also minimum times for these signals on the overlap
movement, but unlike the green value, they do not impact the operation of the parent
phase.
Delay Time
The Del: control at the bottom right corner of the screen specifies how many seconds
of delay will be applied to those overlap phases where a delay is enabled, (i.e. the
delay timing is only used if one or more of the parent phases has an X in the DEL
Enab row on the screen above.)

Overlap Programming
Start-Up, Card, Alternate Flash

This section deals with some per unit choices relative to overlap operation.
--O/L Startup, Card, Alt Rate--
Start Up Interval: 0 | 0=R, 1=Y, 2=G

O/L Card Enable: N | Y=Card, N=K’brd
Alternate Fl Rate: 0 | 0-300 FPM
(Alternate flash rate used for Canadian

fast flash overlaps)
Figure 185 – Individual overlap programming screen 2
Start-Up Interval Color—If an overlap is active upon start-up of the controller, in
theory, this value indicates its initial color. However in practical reality, this setting is
ONLY useful if the parent phase starts in Yellow. If the parent phase starts in Green
or Red, the overlap will follow the parent and ignore this setting.
So, back to the only case where this setting works; if the parent phase starts in
Yellow, the overlap will also start in yellow (i.e. it will follow the parent phase as it
normally does), unless this setting is set to Red. So, to sum up the situation, a Red
Start-up Interval color when the parent phase starts in yellow is the only case where
this setting changes the output on the overlap. In that case, the overlap will start in
red.
O/L Card Enable—If enabled, overlaps A-D must be programmed through the use of
a plug-in overlap card. When not enabled, A-D are programmed strictly through
programming screens. Overlaps E-P are always defined through the programming
screens since the overlap card only supports overlaps A-D.
Alternate (Fast Flash) Rate—Alternate flash allows selected overlaps to flash at the
programmed alternate flash rate. This is used primarily for 'fast flash' operation which
is widely used in Canada, or any “in-cycle” flashing requirement such as for left turns.
Enter the number of flashes per minute if this feature will be used. The overlaps to be
flashed are defined on the overlap set-up screens . Note that a rate value of 0 defaults
to a 1 Hz flash rate (60 FPM). Values commonly used are 120, 150, and 180 FPM.
Note “In-Cycle” flashing signals are accomplished with Overlaps.

DOUBLE CLEARING OVERLAPS

A Double Clearing Overlap provides a delay period of green between the start of its
yellow and its parent’s yellow. The start of any next non-parent phase will also be
delayed until the overlap is cleared. This is done by adding a Red Rest period to the
end of the parent phase. The following two timing diagrams show how a double
clearing overlap is different from a normal overlap.
Normal Overlap
1 Green 1Y 1R 2 Green
Overlap A Green O/L A Yellow O/L A Red
Double Clearing Overlap

1 Green 1Y 1R Red Rest 2 Green
Overlap A Green O/L A Doubleclearing Green O/L A Yellow O/L A Red O/L A Red Rest
Because the parent phase would have already cleared, a double clearing overlap
must time its own yellow and red. So in addition to the overlap delay green time,
these overlap yellow and red values must be programmed in on the Double Clearing
Overlap screens. In addition to these double clearing parameters, any double
clearing overlap must also be programmed for its standard overlap settings, i.e.
parent phases, leading time, delay time, etc.
Double clear overlaps are sometimes called “trailing” overlaps and are typically used
to provide additional green clearing time to a downstream signal when an approach
has multiple signals. Such operation provides what is called an “inside clearance” and
prevents traffic from getting trapped in a zone between two sets of signals. The first
signal is usually controlled by a standard phase and the second signal by a double
clearing overlap. The first signal’s phase is usually the parent of the double clearing
overlap, and may be the only parent, although other parent phases may be included
as well.
To accommodate special sequences and requirements, a double clearing overlap can
also be conditional upon a certain set of phase yellow and phase next values. The
double clearing part of the operation will then be activated only when the state of the
controller meets these programmed values; otherwise, the overlap will function as a
normal overlap.

Double Clearing Overlaps
Double Clear Overlap Programming

To access the double clearing overlap parameters of the 3000 series controllers,
select 3.Double Clear (Delayed/Trailing) from the Overlaps Menu. The full path to this
screen is MM > 3.Change Data > 1.Controller > 5.Overlaps >3.Double Clear
(Trailing). It is important to remember that unlike ped overlaps, which are sixteen
separate entities from the regular sixteen overlaps, double clearing is just an extra
parameter that can be assigned to the regular sixteen overlaps. Any of the sixteen
overlap phases can be set to be double clearing.
Note In addition to the double clear programming shown on these screens, a Double
Clearing Overlap also must be programmed with standard Overlap settings as
well, using the ‘Assignments and Types’, and ‘Startup, Card, & Alternate Flash’
screens on the Overlap menu. Those are where the parent phases and other
basic paremeters of the double clearing overlap are configured.
When you first enter the programming screens, you will see Overlap A. To navigate to
the overlap you wish to configure as a double clearing overlap, either use the PGUP
and PGDN buttons, or place the cursor on the ‘1’ in the “(X of 16)” field at the top of
the screen and type in the number of the overlap you want. (Press ENTER to go to the
selected overlap.)
Double Clear O/L A ( 1 OF 16) Enable: Y

Grn: 5 Yel: 9.9 Red: 8.5 1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
PH YEL X X
PH NXT X
GRP YEL
GRP NXT
RELEASE
Figure 186 – Double Clearing Overlap setup screen
Enable — This setting turns double clearing timing on or off for this overlap. The
general settings for each overlap are set in the
Grn, Yel, Red — These are the times, in seconds, used by the overlap. The green
time is the amount of extra green that the overlap extends beyond the parent phase.
The yellow and red timings are necessary because a double clearing overlap must
time its own clearance separate from the timing of the parent phase.

Triggering Conditions
The next four lines on the Double Clearing Overlap screen (PH YEL, PH NXT, GRP
YEL, and GRP NXT) set up additional conditions that can be used to limit when the
double clearing feature of this overlap is triggered. These define the logic of the
double clearing overlap by monitoring the ‘yellow’ and ‘phase next’ signals from the
selected phases. (An ‘X’ indicates a selection.) The following rules apply:
USING PH YEL & PH NXT ROWS. If any yellow from the PH YEL row is ON at
the same time as any phase next from the PH NXT row, the double clear is
triggered.
USING GRP YEL & GRP NXT ROWS. If all the yellows from the GRP YEL row
are on with all the phase nexts from the GRP NXT row, the double clear is
triggered.
Release Modifier
The Release option at the bottom of the Double Clearing overlap screen can be set
ON or OFF for each phase. Normally, when a Double Clearing Overlap is active,
phases will wait in red for the overlap to finish timing. (In these timing examples,
overlap A is double clearing and linked to Phase 8 as its parent phase.)
Double Clearing Overlap

The Release modifier is a per phase entry that allows the selected phase or phases
to start at their normal times while the double clearing overlap finishes. So if the
Release modifier is ON for phase 2 in our example, the intersection timing will change
and operate like this:
Double Clearing Overlap with Release on Phase 2
3 Green 3Y 3R 2 Green

Double Clearing Overlaps
Double Clearing Overlaps–Example 1

This example is an offset intersection with two double clearing overlaps. Overlap A is
a 1+2 overlap and overlap B is a 2+3 overlap. When phase 1 is clearing to phase 2,
the overlap remains green (normal overlap operation). However, when phase 2 clears
to phase 3, overlap A will double clear.
The double clear would also occur from phase 1 to 3, but since phase 2 is the main
street, if it is on Min, Max, or Ped Recall this transition would not occur. Overlap B
double clears when clearing from either phase 3 to 1 or from phase 2 to 1. Both these
transitions are likely if 1 and 3 are actuated.
Figure 187 – Offset Intersection with Double Clearing Overlaps

The Overlap set-up programming screen for O/L A for example 1 would look like this:
Assign O/L A ( 1 of 16) 1 1 1 1 1 1 1

Phase 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
Parents X X
Fl Enab
MOD PHS
Del Enab
O/L Type: 0 STANDARD Fl Code: 0
Grn: 0 Yel: 0.0 Red: 0.0 Del: 0.0
Figure 188 – Standard Overlap settings - Example 1

The Double Clear programming screen for O/L A for example 1 would look like this:

Grn: 1 Yel: 4.0 Red: 2.0 1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
PH YEL X X
PH NXT X
GRP YEL
GRP NXT
RELEASE
Figure 189 – Double Clearing Overlap settings - Example 1
Overlap B would be programmed in similar fashion except the parents would be 2 and
3, the double clear PH YEL’s would be 2 & 3, and the double clear PH NXT would
be 1.
Double Clearing Overlaps–Example 2

This example of double clearing is a railroad crossing where overlap A is simply a
Phase 4 Overlap. When Phase 4 is clearing to Phase 2 and/or Phase 6, the Double
Clearing Overlap is timed to allow traffic on the track to clear.
Figure 190 – Double Clearing Overlap Used for a Track Clearance

The example 2 double clearing programming screen would be as follows:
Grn: 1 Yel: 4.0 Red: 2.0 1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
PH YEL X
PH NXT X X
GRP YEL
GRP NXT
RELEASE
Figure 191 – Double Clearing Overlap settings - Example 2

Pedestrian Overlaps
PEDESTRIAN OVERLAPS
Ped Overlaps allow a pedestrian movement to be active with more than one phase.
A ped overlap will be serviced any time a phase that is designated a parent phase is
serviced. The ped overlap timing is generated from the active parent phase's ped
timing (Walk and Ped Clearance.) There are sixteen Ped Overlap phases available in
a 3000 series controller and all of their parameters are programmed in this area of the
interface. The Ped Overlap programming screens can be accessed by choosing
option 4.Pedestrian Overlaps from the Overlaps Menu. The full path to the screen is
MM > 3.Change Data > 1.Controller > 5.Overlaps > 4.Pedestrian Overlaps.
Note that ped overlaps do not drive any physical outputs in the default mode. To use
a ped overlap, it must be assigned as shown in this section, then I/O steering must be
used to get the outputs to drive accessible pins. Standard pedestrian outputs of a
specific phase are typically used (if not needed in their normal mode). See I/O
Steering (on page 380) for TS 1 or TS 2 Type 2 operation, or BIU I/O Mapping
(starting on page 400) for TS 2 Type 1 operation.
There are three types of ped overlaps:
Mode 1 Ped Overlaps — If a parent phase is clearing to another parent phase, the
ped overlap will clear prior to servicing the ped for the next parent phase, but will then
come up in Walk again when the next phase’s Walk does.
Mode 2 Ped Overlaps — If a parent phase transitions to another parent phase that
also has a ped call on record, the ped overlap remains in Walk instead of switching to
Ped Clearance. Mode 2 Ped overlaps are similar to vehicle overlaps. Ped overlaps
are typically used in Diamond or other special sequences where a walk is compatible
with two or more phases that use Peds.
Mode 3 Ped Overlaps — This ped overlap mode was added in firmware version 3.6
and is a slight variation on the previous two. If a parent phase transitions to another
parent phase that also has a ped call on record, the ped overlap goes into Ped
Clearance when the first parent phase enters clearance, and the ped overlap stays in
Ped Clearance all the way through the second parent phase’s Walk and Ped
Clearance period.

Ped Overlap Mode Screen

There are five screens of Ped Clearance settings, accessible by paging down from
the first screen. The first screen in this section defines which of the three modes will
be used by each of the sixteen Ped Overlap phases.
Pedestrian Overlaps VALUE(YES/NO)
MODE 3 2 1 1 2 3 1 1 1 1 1 1 1 1 1 1
Use Y/N Key to toggle between modes

PgDn for Ped Overlap Enables
and Parent Phase Programming
Figure 192 — Setting pedestrian overlap modes
A ‘1’ in the column below an overlap phase letter indicates that that overlap will use
Mode 1 logic. Program any ped overlap to operate in mode 2 by placing a ‘2’ in the
corresponding column. And to program an overlap for mode 3 operation, place a ‘3’ in
the column. Toggle between the 1, 2, and 3 values by pressing the Y / N button.
Press PGDN to go to the rest of the Ped Overlap programming screens.

Pedestrian Overlaps
Difference Between Ped Overlap and Ped Compatibility

Ped Overlaps are one method to assign a pedestrian phase to more than one vehicle
phase. Ped compatibility is another. However, they do not function in quite the same
way, which is an important thing to understand. The following timing diagrams show
how a pedestrian phase times relative to the parent (or compatible) vehicle phases. In
all of these diagrams, the vehicle phases are phases 1 and 2. The overlap method
shows a pedestrian overlap A. The compatibility method shows pedestrian phase
number 6, which is in a separate ring.
Ped Overlap Method (Mode 1 logic)

1 Walk 1 Ped Clear 1Y 1R 2 Walk 2 Ped Clear 2Y 2R 3G
Ped Overlap A Walk A Ped Clear A Dnt Walk A Walk A Ped Clear A Dnt Walk

Ped Overlap A Walk A Ped Clear A Dnt Walk

Ped Overlap A Walk A Ped Clear A Dnt Walk
Ped Compatibility Method

Now compare this to the ped phase compatibility method, as shown here:
6 Walk 6 Ped Clear 6 Dnt Walk
The most important difference between the pedestrian overlap method and the
compatibility method is how the ped movement is timed relative to the vehicle
movements. When using an overlap, the ped phase is strictly timed with the parent
phases. But when using the compatibility method, the timing of the ped phase is
independent of the compatible vehicle phases. It is an important distinction.

Pedestrian Overlaps VALUE(YES/NO)

Ped Overlaps Enable: Y
(1 OF 4) 1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
O/L A X X
O/L B
O/L C
O/L D
Figure 193 — Setting Ped Overlap parent phases
Press PGDN to program the parent phases for the ped overlaps.....
Enable each of up to 4 ped overlaps by entering a ‘Y’ for enable. Once the function
has been enabled, assign parent phases for each ped overlap. Parent phase
selection is performed by moving the cursor to a Ped overlap and selecting the parent
phases by either pressing the Phase number or by moving the cursor under a phase
and pressing the Y/N key. An ‘X’ indicates that a phase has been selected for an
overlap.
Ped Overlap Application
Φ3 Ped Overlap A = P1 + P2
Ped Overlap B = P2 + P3
POL A
OL A Φ2
P3 P1
Φ2 OL B
POL B
Ped Push Button

Φ1
calls phase 2
Figure 194 — Example of Ped Overlap operation

Pedestrian Overlaps
Using Ped Driver for “Carryover” Operation
Co-Ph Grp 1 Co-Ph Grp 2

Φ4 Ring 1 1 2 3 4
Ring 2 6 --
P6
OL A = 1 + 2
Φ1
Φ2
Φ3
1 GRN 1 CLR 2 GRN 2 CLR 3 GRN 3 CLR 4 GRN 4 CLR

6 WK 6 PED CLR 6 DWK
Figure 195 — Using Ped Overlap for Carryover operation

After a quick glance, the above may seem like Ped Overlap operation, but it is quite
different than Ped Overlap modes 1, 2, or 3. Ring 2 is used to drive ped 6, which
carries over between phases 1, 2 and 3. Since phase 3 is “left turn only”, ped 6 times
while the controller cycles between phases 1, 2 and 3, thereby reducing delay on
these phases and maximizing the efficiency of the intersection.

ADVANCE WARNING LOGIC (TS 2 ONLY)

This feature provides an advance warning system for overlaps A-H. Advanced
warning has a special set-up screen, but must also be used in conjunction with
Standard Overlap Assignment and Double Clear timing for the overlap. Signal
head (output) steering can be used to substitute an overlap for phase to provide
advance warning when the phase itself drives the signal (instead of the overlap).
Advance warning consists a special output for each overlap that activates when the
normal movement decides to terminate by gap-out, max-out, force-off, etc. The actual
termination of the movement green is then delayed by Double Clear Timing for a user
definable period during which the advance warning output is active. The output
remains active through yellow and red until the overlap once again returns green and
the Advance Warning De-activation Delay times out. The advance warning outputs
are the normal cycle, offset, split, free, and flash outputs, enabled when the overlap
has been enabled for Advance Warning mode. Internal selection of time of day
coordination functions would be unaffected by this operation, as only the physical
outputs would be used.
Typical use:
Since the output activates some time before the movement goes to yellow, advance
warning is typically used to drive a “Prepare to Stop” or a flashing beacon sign. It
might be used on a blind or high speed approach. The De-activation delay feature
allows some time at the beginning of green before the output goes off to allow for
queued vehicles to get moving.
Advance Warning Example

Since Advance Warning Logic involves some choices, and uses other features
(Double Clear Timing), it is best understood by going right to an example and
procedure.
For the example intersection below, it is desired to provide a 6 second advance
warning signal on a blind approach. The signal is a “Prepare to Stop” light board
signal placed at point prior to the bend. It is also desired that the Advance Warning
sign remain on for 7 seconds into phase 4 green.

Advance Warning Logic (TS 2 Only)
O/L A
1) Is assigned with phase 4 only as its parent
in the O/L assignment screen.
2) Is enabled as a double clear overlap with 6
second delay green timing.
“Prepare to Stop” sign board. The sign will

come on 6 seconds before phase 4 goes to
yellow and will remain on until 7 seconds into
the next phase 4 green.
Figure 196 – Double Clearing Overlap used for Advanced Warning
Advance Warning Set-Up Procedure

1. Choose signal drivers for the movement. Advanced warning logic must be
implemented via one of the overlaps A-H. There are two ways of
accomplishing this;
a.) Use the overlap outputs directly. For the example, overlap A drivers would
be used to drive the phase 4 movement.
b.) Use the phase outputs directly and use signal head (output) steering to
substitute an overlap for the phase. For the example, phase 4 drivers would
be used to drive the phase 4 movement, but signal head steering would be
used to bring overlap A out on phase 4 drivers.
2. Determine the advance warning output. Refer to the table below:
Table 38 – Pins Used for Common TS 2 Modes
AW Designation TS 2 Mode 1 Mode 7 Idaho Mode 7 CL Normal Function
O/L or 2 Pin ‘D’ Module Pins ‘D’ Pin
A AW1 A-d D-55 D-30 Flash out
B AW2 C-N D-59 D-32 Cycle 2 out
C AW3 -- -- D-33 Cycle 4 out
D AW4 C-GG D-57 D-31 Offset 2 out
E AW5 C-CC D-60 D-34 Cycle 3 out
F AW6 C-NN D-56 D-24 Offset 1 out
G AW7 C-M D-58 D-5 Offset 3 out
H AW8 A-u D-47 D-25 Free out

The table lists the associated pins for commonly used TS 2 modes. If mode 7
is used with some other “D” module variation, cross reference the listed normal
function to the appropriate pin of the D module per Appendix B. For the
example, since Overlap A is to be used, the Advanced Warning Output is on
‘D’ module, pin D-30 (normal function = Flash out).
Note It may be prudent to avoid using O/L C for Advanced Warning unless one
of the “D’ option modules that support Cycle 4 are inserted.
3. Set-up the standard overlap. The overlap must be set-up by Assignment &
Type. The Overlap A set-up for this example would appear like this:
Assign O/L A (1 Of 16) 1 1 1 1 1 1 1
Phase 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
Parents X
Fl Enab
O/L Type: 0 Flash Code: 0 (See help)

Green: 6 Yellow 4.0 Red: 1.0
The information on this line

is a result of the double clear
programming in step 2
Figure 197 — Setup a standard overlap
The overlap is a simple phase 4 overlap, indicating that, other than the Double
Clear and Advance Warning Logic to follow, it behaves as if it is phase 4.
4. Set-up the overlap up for double clear. The overlap must also be set-up as a
double clear overlap in the double clear screen for Overlap A. The Double
Clear O/L A set-up for this example would look like this:
Double Clear O/L A (1 0f 16) Value(Y/N)
Delay Grn: 6 O/L Yel: 4.0 O/L Red: 1.0
Enable: Y 1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
PH YEL X
PH NXT X X
GRP YEL
GRP NXT
Figure 198 — Setup overlap for double-clearing operation
The Delay Green time (6 seconds) is the Advance Warning time. Overlap
yellow and red time must be provided as well. As with any double clear
overlap, the overlap must provide its own clearance timing.

Advance Warning Logic (TS 2 Only)
5. Set-up advanced warning. The overlap must finally be set up for Advanced
Warning. For this example, it would look like this:
Advanced Warning Logic
Overlap A B C D E F G H
Enable X
Adv Deact-Delay 10 0 0 0 0 0 0 0
(0-99 Sec)
Cond Overlap
Cond Overlap
VALUE (0-8, 0= none, 1-8= Overlap A-H)
Figure 199 — Programming advance-warn logic
Overlap A is enabled for advanced warning with a 7 second de-activation delay
(Advance warning output doesn’t go off until 7 seconds into green). Note that
the Advance Warning time is determined by the green delay time in the double
clear overlap programming.
Advanced Warning Definitions

ENABLE—Enables the overlap for Advanced Warning Logic and the corresponding
Advanced Warning output. Note that standard and double clear programming must
also be applied.
ADV DEACT-DELAY—Advanced Warning De-activation Delay. The period of time
after the overlap goes green before the output goes off. Allows for queued vehicles to
get moving.
COND OVERLAPS—Conditional Overlaps. Up to two per overlap, entered below the
subject Advance Warning Overlap by entering 0-8, where 0 = none, 1-8 = Overlap A-
H. Conditional Overlaps would typically be used for applications where two Advance
Warning movements terminate together but have different warning periods. An
example of this would be when AW overlaps are assigned to phase 2 and phase 6,
but with different warning periods.
Note The conditional overlap double-clearing green time must be larger than the
parent overlap. (Overlap A in this case.)
When the two are about to terminate, the longer (conditional) overlap starts its
warning timing but the shorter waits until the first times down to a value equivalent to
its own delay. It then activates its own warning output and then times out and clears
with the conditional overlap. If this programming were not applied, the warnings
would incorrectly start together.
Note that the original overlap warning (delay) timer only waits if the conditional
overlap warning (delay) timer is timing or has been enabled to time, i.e. it is going to
terminate. A delay timer may be enabled to time but not actually timing if that
movement has its own conditional phase and is waiting as well. This allows cascading
of advance warnings. The only time the original timer does not wait is if the
conditional overlap is not going to terminate.

Overlap A (shown below) is a phase 2 overlap with Advanced Warning. It has been
set-up for a case in which Overlap B is a phase 6 overlap with a longer warning time
(double clear green time).
Advanced Warning Logic
Overlap A B C D E F G H
Enable X X
Adv Deact-Delay 10 15 0 0 0 0 0 0
(0-99 Sec)
Cond Overlap B
Cond Overlap
VALUE (0-8, 0= none, 1-8= Overlap A-D)
Figure 200 — Advance warning logic screen
As shown above, overlap B is a double clearing overlap conditional upon overlap A.

Lead/Advance Green Overlaps
LEAD/ADVANCE GREEN OVERLAPS

A special modifier to overlap timing was added to the 3000 series controllers in
firmware v3.6.2. Leading Overlaps and Advance Green Leading Overlaps allow
overlaps to start before their parent phase goes green. A ‘leading’ overlap adds a red
rest period before the parent phase to accomodate this lead timing. An ‘advance
green leading’ overlap starts even earlier, at start of the previous phase’s yellow.
Leading Overlap
Next Phase is Phase 2
Overlap A Red (Phase 2 is parent) Overlap A Leading Green Overlap A Green
Advance Green Leading Overlap

Next Phase is Phase 2
Overlap A Red Overlap A Leading Green Overlap A Green
Figure 201 — Comparison - Leading and Advance Leading Overlaps
Leading and Advance green leading timing can be assigned to any of the first eight
vehicle overlaps. It is not available for overlaps I through P. To set up such timing on
an overlap, first configure the overlap as desired using the normal overlap setup
screens, then choose option 6.Leading/Advance Green Overlaps on the Overlap
Menu to add the early timing. The full path to this screen is: MM > 3.Change Data >
1.Controller > 5.Overlaps > 6.Leading/Advance Green Overlaps.
Lead Overlap O/L A ( 1 OF 8) Value(Y/N)

Lead Overlap Green Time: 14
Enable: Y 1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
PH NXT X
GRP NXT X X
Advance Green Enable: Y

Figure 202 – Lead Overlap setup screen - Overlap A
Enter these screens and use either the PGUP and PGDN keys to switch between the
eight available leading overlaps, or place the cursor over the ‘1’ in the ( 1 OF 8) item
at the top of the screen and type in the number of the overlap you wish to edit. (Press
ENTER to go to the desired overlap.)
Lead Overlap Green Time — This is the amount of time that the leading or advance
green leading overlap will be green ahead of the parent phase. If this is a Leading
overlap, this time will be created by adding a red rest period to the end of the previous
phase’s red segment. If, however, this is an Advance Green Leading overlap, this
time is compared to the Yellow and Red of the previous phase. If the Yellow and Red
timing is longer than this setting, the normal Yellow and Red timing is used. If the
Yellow and Red timing is less than this setting, however, an extra red rest period is

added to the end of the red segment. In all cases, the time spent in the leading green
overlap is at least this value.
Enable — This settings turns ON (Y) or OFF (N) leading and advance green leading
timing for this particular overlap.
PH NXT — Phase Next and Group Next are used together to decide when to start
timing ahead of a parent phase. The Phase Next signal comes on when a phase
reaches its yellow segment and the controller must decide which phase will be served
next. If, for example, phase 2 will be served next, then the Phase 2 Phase Next
signal will go ON. In this screen, this setting tells the leading overlap to watch these
particular Phase Next signals and turn the overlap green based upon them. (At the
same time, for Advance Green Leading overlaps, but for simple Leading overlaps, the
overlaps comes on some time after the Phase Next signal, during the red segment.)
GRP NXT — The Group Next is used to determine which previous phase will start to
time the leading overlap. Group Next is a logical AND signal built out of the Phase
Next signals of all of the items checked on this row. So, if phases 2 and 12 are
checked on the GRP NXT row, the Group Next signal will only go ON when the
Phase Next signal goes ON for both phase 2 and phase 12. So the leading overlap
will not start timing until this Group Next signal goes active.
Note Group Next and Phase Next are either-or decisions for when to start the leading
overlap. So if the Phase Next condition is met, the leading overlap will start,
even if the Group Next condition is not met. The Phase Next condition is tested
first, and then the Group Next condition is tested.
Advance Green Enable — This setting determines whether this is a regular Leading
overlap (N) or an Advance Green Leading overlap (Y). If set to NO, then the leading
overlap starts during an added ‘red rest’ segment added on to the previous phase’s
red segment. If Advance Green Enable is set to YES, on the other hand, the leading
overlap starts with the yellow segment of the previous phase.
Note If an overlap has both a lead time and a delay time assigned for the same
parent phase, the delay timing will be used and the leading time will be ignored.
This is true for both Leading overlaps and Advance Green Leading overlaps.

Inhibiting Overlaps
INHIBITING OVERLAPS
It is possible to inhibit the operation of overlaps by using a Time of Day circuit. TOD
circuits 177 through 192 will prevent overlaps A through P (respectively) from
occuring.
An overlap inhibit circuit forces the overlap to stay red. It does not take effect until the
overlap is red. The overlap will clear using the yellow and red timings assigned to the
overlap, unless those happen to be set to 0 (zero). If the yellow time is set to zero, as
it probably will be unless this is a double-clearing overlap, the overlap will use a value
of 3.0 seconds to transition to the inhibited state.
See page 430 for more details.


Chapter 6 — The Basics of Coordination
This section introduces the basic concepts of multiple-intersection traffic flow coordination. The
following topics are discussed in detail in this chapter:
An overview of traffic coordination, on page 212.

Signal timing in a coordinated environment, on page 213.
Synchronization methods, on page 216.
Coordination using actuated controllers, on page 217.

GENERAL OVERVIEW OF COORDINATION

Coordination of traffic signals is a term used to describe a process in which two or
more intersections are synchronized so that vehicles can pass through each
intersection without stopping. Coordinated Operation is then a system mode of traffic
management. Each controller within the system will operate with a cycle length,
offset and split (set of phase allocations). The cycle length will typically be at any
one time common to all intersections in the coordinated system, but each intersection
will use its own offset and split.
Intersections set up this way will establish what is called progression of signals.
There are three basic types of coordinated progressions. For example, consider the
following 4 intersections with the indicated progressions.
Figure 203 – Three types of coordinated progression

Differences in the offset values of each intersection determine the type of
progression. In order for synchronization and therefore the progression to be a
continuous process, the return to the main street green of each intersection must be
on a cyclical basis. This cycle, or time to serve all phases, must be the same as, or a
multiple of, the common cycle for all intersections within the system. A technique
called “double cycling” is sometimes used such that multiphase intersections might
use a 90 second cycle while the 2 phase intersections use 45. Each 2 phase
intersection then cycles twice for each one multi-phase cycle.

Signal Timing in a Coordinated Environment
SIGNAL TIMING IN A COORDINATED ENVIRONMENT

The terms defined in the following section explain how coordination is achieved
across multiple intersections, each being timed by its own controller unit.
Cycle Length
The cycle length is the total time to serve all phases, i.e. the time from the start of
phase n green until the next start of phase n green. All intersections coordinated at
any one time must use the same cycle length or a multiple thereof.
Local Cycle
This term refers to the cycle timer active in each unit that actually controls phase
timing. This differs from the Master Cycle, which is used as a common reference, but
does not control phase timing. The zero point of the local cycle is then referenced to
the master cycle by an offset value. The offsets at each intersection may differ, but
the master cycle zero point should be the same for all.
The first two intersections in the system for the inbound progression are shown
below. Both intersections have the same local cycle length (90 seconds).
Figure 204 – Two intersections with the same Local Cycle length
Split (Phase Allocation)

A split plan is the allocation of times within the cycle for each phase. The sum of all
of these split times, including the green, pedestrian, yellow, and red intervals, creates
the full cycle time. Note that the splits of the various intersections that make up a
coordinated corridor do not need to be the same. In the above example, the number
of phases and the split times of intersection #2 are not the same as intersection #1.
But since both have the same full cycle length, synchronization can still be
accomplished.
Local Cycle Reference Point

Each intersection has a reference point within its local cycle that has to remain
synchronized with a master reference. This master reference is transmitted
throughout the entire coordinated corridor, keeping all of the intersections in sync.

Usually the local reference point for each intersection is the start or end of the Main
Green phase. That is the point that is used to reference to the master reference
signal.
Reference point...
End of Main Street Green (φA).
Figure 205 – Local Cycle Reference Point
Master Cycle
This cycle issues the common reference signal and therefore establishes
synchronization between all of the intersections in the coordinated corridor.

Signal Timing in a Coordinated Environment
Offset
An offset determines where the local reference at each intersection (beginning or end
of coord phase green) should occur relative to the common master cycle. For
example, for the inbound offset, intersections 1 and 2 would be set up as follows:
Figure 206 – Example of Coordinated Intersection Offsets

Intersection #1 has zero offset. It is the intersection from which all others are
referenced. The end of its phase A (main street) occurs at the same time as the
master cycle zero point.
Intersection #2 is offset 7 seconds to allow for travel time. The end of its phase
A (main street) occurs 7 seconds after the master cycle zero point.
Each successive intersection has a unique offset value as determined by the travel
speed and distance.

SYNCHRONIZATION METHODS
Historical Sources of Sync Pulses

The traditional master cycle used for referencing in years past was a 3-second pulse
of zero volts from a 115VAC signal via a hardwire interconnect. All intersections
would reference and synchronize themselves to these "Sync Pulses” as generated by
a master dial unit. Over the years, however, other methods of providing referencing
sync pulses have been incorporated and have for the most part replaced the 115VAC
hardwire interconnect.
One of the more popular methods today is Time Based Coordination in which there is
no interconnect at all, but each controller internally generates its own master cycle
based on its internal clock and the time of day. This is a very popular technique
because no interconnect system has to be installed.
Another method is through a communications link such as 2 twisted pair wire, radio,
or fiber optics. Under such communications links, far more sophisticated information
can be passed to and from each intersection, not just simple sync pulse commands.
Offset Seeking
The local cycle timer is not always at the proper offset relative to the master cycle. It
can be “out of step” upon system start-up, if cycle or offset changes are made, or
after preemption. Offset seeking describes the process of getting the local cycle back
into step with the master cycle. The local cycle can either time a percentage faster,
slower, or stop until the proper reference is achieved.
Each method avoids abruptness, so as not to disrupt traffic. Offset seeking can
sometimes take five cycles to get back in step. This seeking process is necessary to
ensure a smooth transition from one pattern to another without skipping, over-timing
or short-timing phases.

Coordination of an Actuated Controller Unit
COORDINATION OF AN ACTUATED CONTROLLER UNIT

In this discussion of Coordination thus far, no mention has been made of the various
types of controllers, specifically pre-timed controllers versus actuated controllers. In a
pre-timed controller the cycle length is fixed and does not vary from cycle to cycle.
Thus, if any point within the cycle is synchronized, the entire cycle must be
synchronized as well. Therefore, to synchronize a pre-timed controller, one need only
to worry about the synchronization process (offset seeking) and the cycle length
selection of each controller.
When an actuated controller is considered, however, just the establishment of a cycle
length is a considerable process in itself. This is because the cycle length of an
actuated controller will normally vary from cycle to cycle depending on vehicle
demand. A cycle length must then be artificially imposed on an actuated controller to
achieve coordinated operation.
To accomplish this, there are certain functions that the controller uses, such as
permissive periods, holds, and force offs. These functions force the controller to
operate within the constraints of a background cycle while still allowing the controller
to operate in the actuated mode and allowing basic intervals such as initial (minimum)
greens, walk, ped clear, yellow, red, etc., to time normally.
Functions Used to Coordinate an Actuated Controller

HOLD - Holds the coordinated phase (main street) during a specific period of the
cycle (when no permissive periods are active.)
PERMISSIVES - Allow a "window of time" in which the phase can be serviced.
Permissives have a “start” and “end” time, and prevent a phase from being serviced
too late to be properly forced off. A phase cannot be forced off during its initial
(minimum) green or ped timing, thus the permissive must take this into account, i.e. a
given phase permissive will end sufficiently before the force off so that if the phase is
serviced, it will be able to time at least its initial green and/or ped before force off
occurs.
FORCE OFF - Terminates a phase at the designated point in the background cycle.
Note that Force Off is a rather mild command and can only terminate an actuated
green that has timed past the Initial or ped times. It cannot force out of initial, walk or
ped clear. It has no effect on yellows or reds.
It is important to note that the coordinator only uses the above commands to
constrain the controller phasing and phase next decisions. It does not interfere with or
modify intervals such as minimum greens, walk, ped clear, yellow, red, etc. This is a
common misconception.
Example of Force Off And Permissive Placement

This example shows how an actuated controller may be set up using the Force Off
and Permissive functions in an 8 phase dual ring.
Shown is a 90 second “background” cycle with the typical placement of “fixed” force
offs and permissives. Each force off establishes the point at which the phases will be
terminated and move on.

Phases can “gap-out” before they “force off”. If a phase does gap out, the next phase
can get more time*. Notice that each permissive ends somewhat before the force off
for the indicated phase pair. Under full demand on all phases, permissives generally
don’t do much. However, under light demand, particularly if the coordinated phase is
likely to “rest” or if other phases are likely to be skipped (no demand), permissives
make sure that phases are only allowed service at such a point that they can be
forced off at their designated time.
Figure 207 – Typical placements of fixed force offs and permissives

Coordination of actuated controllers can be tricky business. Two seemingly
contradictory concepts are employed at once. On the one hand, because the
controller is actuated, the benefits associated with an actuated controller are desired,
i.e. a controller that is responsive to traffic, skips phases with no demand, varies the
green appropriately for phases with demand, and finally, one that rests in the main
street in absence of any demand. On the other hand, to accomplish coordination, one
must constrain the timing so that the controller operates within the confines of the
background cycle.
Coordination of actuated signals is often a complex matter, and requires a great deal
of effort on the part of the responsible agency to provide the analysis (traffic studies,
etc.) required for proper programming and subsequent operation.
Coordination of actuated signals can often be controversial as well. This is primarily
due to the nature of their operation. In the case of pre-timed controllers, signal
progression tends be well behaved and each signal “nicely” displays its green in just
the proper order. Actuated signals, however, do not always seem to behave so nicely.
For example, if at a given intersection, all the side street phases do not use all their
green time (they "gap-out" before they "force off"), then there will be an "early return"
to the main street. The "platoon" of vehicles at that intersection will then be released
and may arrive at the next intersection too early, before the green appears. These
vehicles will have to stop, which, of course, defeats the purpose of coordination.
There are, however, a couple of things to consider relative to this issue. Firstly,
despite the lack of appearance of coordination under such circumstances, the system
may actually be more efficient. Even though the pre-timed system may be well
coordinated, it often does so by arbitrarily holding the main street red as the side
* The 3000 controller has an optional feature in which “fixed” force offs are disabled and the force offs are
allowed to “float.” This operation disallows any phase but the coordinated phase (usually main street)
from getting more than its allocated time. Thus, when a phase gaps-out early, the next phase doesn’t get
any additional time since its force off is based on when it starts rather than a fixed point in the cycle.

Coordination of an Actuated Controller Unit
streets are provided with a fixed duration green time, whether needed or not.
Conversely, the actuated machine returns to the main street as soon as it can. Since
some main street vehicles may turn off before they reach the next intersection, an
early return is certainly beneficial to them. For those that proceed through the next
intersection, although they may be hampered by arriving too early, they may also
have the luck that the next intersection returns to main street early as well, and can
proceed unimpeded. This type of operation provides maximum efficiency although it
can occasionally appears sporadic and unpredictable.
This leads to the second point: proper coordination using actuated controllers
requires that the responsible agency provides the proper cycle and split settings for
the level and distribution of traffic at any given time of day. If the cycle length and split
times are appropriate for the conditions at all times of the day, non-beneficial early
returns to the main street can be minimized.


Chapter 7 — Coordination Programming
This section explains the details of how to configure coordination on a 3000 Series controller.
The following topics are discussed in detail in this chapter:
The Coordination Menu, on page 222.

How to load and clear coordination defaults, on page 223.
Specifying a coordination source, on page 224.
Basic options, on page 225.
Cycles and offset times, on page 236.
Working with coordinated phases, on page 239.
Allocating times to phases, on page 240.
Setting up offset seeking, on page 243.
Activating Time of Day circuits from coordinated operation, on page 245.
Enhanced options, on page 246.
Using the check coordination plan, on page 265.

UNDERSTANDING THE COORDINATION MENU

To open the Coordination Menu, start at the Main Menu and select option 3. Change
Data to open the Program Menu. Then select item 2. Coordination to open this menu:
Coordination Menu
1.Clr/Load Defaults 6.Phase Allocations

2.Selection Source 7.Ofst Seeking Mode
3.Basic Options 8.COS/F To TOD Ckts
4.Cycles & Offsets 9.Enhanced Options
5.Coord Phases 10.Check Coord Plan
Figure 208 — Coordination Menu

The controls available in this menu are described in detail in the rest of this chapter.

Clear/Load Defaults
CLEAR/LOAD DEFAULTS
Before programming Coordination for the first time in a new unit, or to completely re-
program an existing unit, it is generally a good idea to clear the data base or set it to
defaults.
Coord Clear and Load Defaults Menu
(see Utilities to copy splits)
1.Clear all Coord values
2.Set all Coord options to defaults
3.Set Enhanced Options to defaults
4.Set Coord Phases to Ph 1 all cycles
5.Set Coord Phases to Ph 2 all cycles
6.Set Coord Phases to Ph 2, 6 all cycles
Figure 209 — Coord Clear and Load Defaults Menu
Clearing all coord values sets all cycles, offsets, phase allocations and perms to
zero. It does not affect Y/N, numeric options or enabled phases (e.g. coord phases).
Loading defaults only affects those items as specified per screen descriptions.
These do not clear or modify cycles, phase allocation, etc.
If you choose option 1, Clear all Coord values, you will see:
All coord values will be cleared
--Press ENTER to execute

--Press CLEAR to cancel
Figure 210 — Clearing all coord values

Such a verification screen will also appear if you choose any of the other Coord Clear
and Load Defaults options (2 through 6) except that the screens will display,
respectively:
All Coord Options will be set to defaults (ENTER/CLEAR?)
All Enhanced Coord Options will be set to defaults (ENTER/CLEAR?)
All Coord Phases will be set to phase 1 (ENTER/CLEAR?)
All Coord Phases will be set to phase 2 (ENTER/CLEAR?)
All Coord Phases will be set to phases 2, 6 (ENTER/CLEAR?)

SELECTION SOURCES
The Selection Source specifies the “source” or means of selecting various
coordination values - Cycle, Offset, Split, Free and Flash. Each can be selected
independently, though they are usually the same for any given application.
Coord Selection Source
(0= TOD, 1= CL, 2= INT)

Cycle Source: 0 Free Source: 0
Split Source: 0 Flash Source: 0
Offset Source: 0 Inter TOD Revert: 0
(0-255 SEC)
Figure 211 — Coord Selection Source screen

The values shown are from execution of Set All Coord Options to Defaults. Not
affected by Clear All Coord Values or Set Enhanced Coord Options to Defaults.
In the example screen shown above, all coordination parameters are selected by the
local TOD plan.
INTER TOD REVERT—A time-out value (0-255 secs) for interconnect mode. If no
sync pulses are received for this period, the unit will revert to TOD control.
To program coordination sources, simply enter a value (0-2) for each coordination
feature.
Table 39 – Coordination Source Codes
Code Coordination Source
0 Time of Day (TOD), time-based coordination
1 Closed Loop (Master)
2 Interconnect (hard wire)
Notes about Selection Sources

1. The unit will automatically revert to TOD control if it’s in closed loop mode and
the carrier is lost for 15 seconds.
2. Split Matrix (when enabled, see definition) will override the split sourcing
option.
3. If the master is taken off-line or carrier (comm) is lost, all of the values (cycle,
offset, split, free, & flash) would be selected by the local TOD plan.
4. When NOT in interconnect mode, the inputs normally associated with Cycle 2
and Split 2 can be used for TOD Override and time Clock Reset inputs,
respectively.

Basic Options
BASIC OPTIONS
Option 3 on the Coordination menu, the Basic Options screen provides for
programming of commonly used coordination options, i.e. functions that are likely to
be programmed and not just set to defaults.
Coordination Basic Options
Reference to end (vs. beg) of Main St.: Y

Use % (vs. secs) for Phase Allocation: Y
Use % (vs. secs) for Offset Entry: N
Use fixed (vs. floating) Force Offs: Y
Permissive Type: 2
(Perm type: 0=Yield, 1=Single, 2=Mult.)
Figure 212 — Coordination Basic Options screen
Values shown are from execution of Set All Coord Options to Defaults. Not affected
by Set Enhanced Coord Options to Defaults or Clr All Coord Values.
Reference to End of Main St.

This programming establishes the Local Zero reference point. The Local Cycle Zero
Reference point is the point that offsets are referenced to. It is also the basis for
computing permissives when the Auto Perm mode is enabled.
Enabled (Y) = The end of main street (coord phases) will be the Local Zero point
reference within the local cycle. The end of main street service occurs at the yellow
clearance for standard coordinated phases or at the beginning of the ped clearance
interval if the coordinated phases are CNA phases with WRM applied.
Disabled (N) = The beginning of main street green(coord phases) will be the Local
Zero point reference within the local cycle.
Use % for Phase Allocation (Splits)

This option specifies whether permissive and phase allocation entry is to be in
percent (Y) or seconds (N). If %, the total allocations must add up to 100% regardless
of cycle length. If seconds, the allocations must add up to the cycle length in seconds.
Also see the phase allocation menu (page 240) .
Offset Entry in %
This option specifies whether offset values are to be entered percent (Y) of cycle or
seconds (N). If programmed in percent, the offsets will occur as a percent of the
cycle. If programmed in seconds (‘N’), the offsets will always occur at that number of
seconds, regardless of cycle length. If programming in seconds, an offset should
never be programmed larger than the cycle length or else the controller will never
reach the offset value. The offset shown in the coordination dynamic screen will
reflect the way this parameter is programmed.

Use of Fixed vs. Floating Force-Offs

This option determines how Force Off values will be automatically calculated based
on the programmed phase allocations (split) and clearance interval timing.
When enabled (Y), Force Offs are computed in the “fixed” mode where the force off
point within a cycle for any phase n is given by the equation:
FOn = FOn-1 + CLRn-1 + PHASE ALLOCATIONn – CLRn
Where CLR = Yellow plus Red for an actuated phase, and Yellow plus Red plus Ped
Clearance for a CNA phase.
Force Off for the coord phase (FOCP) = ZERO or (PHASE ALLOCATION – CLR)
depending on the “End of Main Street” setting.
A fixed-point value within the local cycle is then computed for each phase.
When Fixed = enabled (Y), Fixed Force Offs operation tends to distribute unused
cycle time to all other phases—if needed, and also discourages an early return. This
occurs because if one phase gaps out the next will start early, but its force remains
fixed at the same position in each cycle. The phase then gets more time if it extends
up to its force off.
When Fixed = disabled (N), the force off point is based on the start of the phase
green. The Phase Allocation times act like Max times, and are referred to as
“Floating” Force Offs. This operation allocates unused time only to the main street
because if a side street phase gaps out, the next phase in sequence will time its
phase allocation beginning at that point and will force off after it has been timed.
It should be noted that only early-starting phases are affected by the Fixed Force Offs
(Y/N) entry. When Fixed is disabled (N), both the Fixed and Floating Force Off points
are in effect and whichever occurs first will “force off” the phase. This is done to “lock”
phases to the background cycle.
Example of Fixed and Floating Force Offs
Figure 213 – Relative allocation times for an 8 phase intersection

If there is full demand on all phases, then there is no difference between fixed and
floating force offs, as indicated below.

Basic Options
Figure 214 – Fixed and Floating Force Offs - Full demand on all phases
However, if phase ‘3 & 7’ gaps out, then there will be a difference in timing as follows:
In the fixed mode, assuming all other phases have full demand, they can each
extend up to their fixed point. The main street will start early only if the side
streets don’t use all their time and the last of the side phases gap out early.
In the floating mode, the extra time from the ph 3 & 7 early gap out will surely be
given to the main street because each subsequent phase can time no more
than its allocation.
The following diagram illustrates this difference:
Phase ‘4 & 8’ gets all of the extra time
If phase ‘3 & 7’ because it starts earlier, then it gets
gaps-out early… extended up to the fixed force-off time
φ3 & 7 φ4 & 8 φ1 & 5 φ2 & 6

FIXED
φ3 & 7 φ4 & 8 φ1 & 5 φ2 & 6

FLOATING
These phases end early The coordination phase receives

because they started all of the extra time
early
Figure 215 – Fixed and Floating Force Offs – Differing Timing on Gap Outs

Typical Reasons for Selecting Fixed vs. Floating Force Offs

This decision should be based on which provides maximum benefit to the
intersection. If the best thing to do is give the main street every spare second it can
get, then choose Floating (N). If the best thing to do is give the side street, especially
thru’s, any extra time that might occur from skipped phases or early gap outs, then
use fixed (Y).
Questions to ask are, “Is there much benefit in starting the main street early?” or
“Where are volumes presenting a problem (if any)?” “Where is storage most
critical?” Answers to these will give insights as to which mode is best.
Note that in the case of multiphase intersections, use of both floating force offs and
Single Permissives can provide unused time to both the beginning and end of main
street where Floating force offs and Multiple Permissives will provide all unused time
to the beginning of main street only (see permissives definitions). Fixed Mode is
usually a better choice when the cross street through is coordinated (as in a grid)
because it will not force the cross street to end early when it starts early.
Phase MAX TIME settings also play an important role in phase timing during
coordination. If the max time in effect for a phase during coordination is about the
same as its phase allocation, then the operation will be much like Floating Force-Offs
— even if fixed mode is programmed. This is because if the phase starts early it will
max out before being forced off, (unless it is a coordination phase.)
Note When Fixed Force Offs are enabled, without the Max Timer influencing termination
a phase that starts early with no Gap Out will use all of the unused time from the
previous phase. This leaves none of the unused time for subsequent non-
coordinated phases. A phase’s Max Time can be used to control the distribution of
unused time to subsequent non-coord phases (Inhibit Max unused.)

Basic Options
Permissive Type
This entry selects the type of permissive to be used when Auto Permissive operation
is enabled (enabled in Enhanced Modes menu, default mode = enable). The choices
are; Yield (0), Single (1) and Multiple (2) as described below.
General Discussion Of Permissive Types

A permissive period is a window that defines when a specified phase or group of
phases are allowed service. Permissives are bounded by a start and end value.
Permissives may be simple, short, and one period for all, like yield permissives, or
they may be more sophisticated like single and multiple permissives which extend the
end of permissives as much as possible. These are usually associated with
multiphase actuated control where the permissive attempts to accommodate late
arriving calls, allowing each phase to service its minimum times and still be able to
force off on time.
Note that the single and multiple permissives have their greatest effect during less
than peak demand times. During peak times, when calls are likely present
everywhere, the coord phase will leave at the beginning of the first permissive
anyway—there is little difference between these and yield permissives. During off
peak times, however, demand may be absent or late arriving and the more
sophisticated permissives become useful.

Yield Permissives
Typically used for pre-timed mode, if the cycle is short, for simple phasing, or to
heavily favor main street. Yield Permissive operation opens one relatively small (0-
10%) window in which all non-coord phases are allowed service. Once the window
closes, no side phase service is allowed until the window re-opens during the next
cycle. Yield Operation tends to give preferential service to the Coordinated Phases.
The yield percent must also be programmed for this mode, as found in the Enhanced
Operating Modes, second screen (set to 10% by default).
F.O. F.O. F.O. F.O.

2&6 3&7 4&8 1&5
End main street green One Yield period for all non coord
phases (1, 3, 4, 5, 7, 8)
Figure 216 – Operation of Yield Permissives

The closing of a yield permissive period actually occurs only if there is no side street
demand and the unit rests in the coord phase. In that case, the period will end as
scheduled and no other phases will be served until the next cycle. If another phase
has demand and is served, however, the yield permissive will remain open for all
successive phases until each are served. If the unit did not do this, the yield
permissive period would end during the first phase served and would not allow any
other phases besides the coord phase. This would not be desirable, particularly in
multiphase operation.
Typical use:
Yield permissives are often used when the unit is operating in a pre-timed mode
where there is some type of recall on each phase (such as for urban grid systems.)
Yield permissives are adequate in this case because there is no need to extend the
end of permissive periods to accommodate late calls. Yield permissives can also be
used when it is desired to heavily favor the main street (coord phases) by allowing
only one small permissive for all phases. If they do not get their calls in before or
during the yield period, they simply wait until the next cycle. Floating Force-Offs with
Yield Permissives encourages early return.

Basic Options
Single Permissives
Typically used with multi-phase actuated controllers. As the name implies, single
permissive operation allows 1 permitted phase per ring to be active at any one time.
The first period starts at the end of the coord phase and allows only the phases that
directly follow the coordinated phase. This period then ends and the next period starts
for the phases after that, etc. For each non-coord phase, if the controller yields to the
phase from the coord phase at the Start Permissive Point, the phase will begin at its
normal time in the “background cycle”.
When the AUTO PERM mode is enabled, the coordinator automatically enables
Enhanced Permissive operation for Single Mode Permissives. This function modifies
typical Single Perm operation by dropping the start permissives back to the end of
Main Street once a side street phase has been serviced (see Enhanced Permissives
discussion).
F.O. F.O. F.O. F.O.

2&6 3&7 4&8 1&5
End main street green Perm 1 & 5

Perm 3 & 7
Perm 4 & 8
Figure 217 – Single Mode Permissives (when in coordinated phases)

Also note that In the event that true or “strict” single permissive operation is desired,
permissives must be entered manually, without the Enhanced Perm mode enabled
(both Auto Perm and Enhanced Perm are disabled). Keep in mind that if this done,
the unit will return to the coord phase any time a phase gaps out before the next perm
starts.
Typical use:
Single mode permissives are beneficial if any or any combination of the following are
true (or similar):
1. When the side street has an advance left turn (or dual ring pair) and there is
some benefit in providing extra green time to the end the coordinated phase.
Because they are the only phases allowed during the first permissive, absence
of demand on the left turns will cause the unit to rest in the coord phase green
until the side st. through phase permissive starts, increasing green-band
throughput. The Side St. through phases cannot start early in place of the left
turns.
2. There is advance left turn phasing on the side street as above and it is desired
to provide a “window” of opportunity for left turn demand. The idea is to allow
slightly late arriving left turn demand to still be serviced instead of immediately
proceeding to the side street through (as in the case of multiple permissives).
3. Again the same phasing as above and there is some disadvantage to starting
the side street through phases very early. Again, a very early start would be
the case if there is no demand on the left turns and the thru’s could start

immediately in their place (multiple). The desire to use single permissives and
wait might be the case in a grid environment where the side street is also
coordinated with other intersections. Note that the side street thru’s can still
start somewhat early if the left turns are served but gap out. If this is not
desired, the No Early Release feature can also be applied to left turn phases
so they cannot not gap-out early. Single permissives and No Early Release on
the left turns will then fully ensure that the side street thru’s do not start at all
early.
The appropriate formulas for single permissives are shown below:
FOn = FOn-1 + CLRn-1 + PHASE ALLOCATIONn - CLRn
EPn = FOn - INITn - MSCLR
EPPn = FOn - WALKn - PED CLRn – MSCLR
SPn = FOn - (PAn - CLRn) - MSCLR
SPPn = SPn
The Main Street clearance term is appropriate when the coordinated phases are
on. But for any phase “i” in the ring that is on, the clearance time sum of that
phase is placed in the two equations above yielding the following:
EPn = FOn - INITn - CLRi
EPPn = FOn - WALKn - PED CLRn – CLRi
Where:
n = The phase in question INIT = Initial
n-1 = The previous phase. EP = End permissive
i = The phase on in the associated Ring EPP = End pedestrian permissive
FO = Force Off SP = Start permissive
MSCLR = Main St. Clearance (Yel + Red + PCL) SPP = Start pedestrian permissive
PA = Phase Allocation WALK = Walk
CLR = Phase Clearance PED CLR = Pedestrian clearance

Basic Options
Multiple Permissive
Typically used with multi-phase actuated controllers. Delays on late arriving non-
coord phases are minimized when this type of perm is used. Multiple Permissive
operation allows all phase/ped permissives periods to begin at the main street force
off point but end at different points within the cycle depending on the relative position
of their force off(s). This operation allows the controller to go to any phase with
demand following the main street force off. After time, if the controller continues to
rest in main street green, phases will be denied service during that cycle in order of
their occurrence (3 & 7 first denied, then 4 & 8, etc.)
Figure 218 – Multiple Mode Permissives (when in Coordinated phases)

The appropriate formulas for multiple permissives are shown below:
FOn = MSCLR + FOn-1 + PAn - CLRn
EPn = FOn - INITn - MSCLR
EPPn = FOn - WALKn - PED CLRn – MSCLR
Actually, the Main Street Clear term is appropriate for coordinated phases, but
when any phase “i” in the ring is on, the clearance time sum of that phase is
placed in the two equations, above yielding the following:
EPn = FOn - INITn - CLRi
EPPn = FOn - WALKn - PED CLRn – CLRi
SPn = FO COORD PHASE
SPPn = SPn
Note that other than start of permissives, these are the same as single mode
permissives. It should be noted that multiple permissive operation tends to effectively
reduce the permissive “window” down to a permissive “point” for all but the last of the
permitted phases. This is because the unit is allowed to immediately proceed from the

coord phase(s) to the next set of phases with demand since all perms start at the end
of the coord phase green.
Typical use:
Review the single mode typical use cases. Given similar phasing and there is no
significant benefit from any of those cases, then multiple mode might be the correct
choice. This is particularly so if the side street thru’s have fairly heavy demand while
there is no major advantage to remaining in main street green.
It might also be that the side street left turn is protected/permissive (e.g. 5 section
head) and the need for extending a permissive “window” to the left turns is not critical.
The desire then is to simply get to the side street thru’s as soon as possible. Fixed
Force offs would be the likely choice in this case as well so that the side street thru’s
can get extra time if started early.

Basic Options
Computation Of Force Offs And Permissives
Force Offs
Force Offs are applied by the coordinator to terminate a phase if the phase has not
already terminated due to a gap or a max. If the yield point in the cycle (Local Zero)
is referenced to the end of main street green, then the main street force off is
calculated to occur at the cycle zero point. If the yield point is referenced to the
beginning of main street green, the main street force off will be calculated as cycle
zero + (main street phase allocation - main street clearance). In the fixed mode, side
street force off points are then computed sequentially from the coord phase force off
point. In the Floating Force Off Mode (Fixed Mode = N) the force off’s are more like
max times.
Permissives
Permissives are applied by the coordinator to allow the main street to terminate and
serve other phases. They are computed based on the type of permissive mode only
and not whether Fixed Mode force offs are enabled or not. Permissives are then
essentially fixed (cycle dependent) in both modes. Thus, such permissives are
calculated as if the force offs are fixed so that phases are allowed service from the
coord phase at the same specified points within the cycle. The floating aspect comes
into play mainly when the phase is served early due to a previous phase gap-out or
skip. The phase can then only get its allocated time amount based on its starting
point, and all accumulated extra time goes to the coord phase.
Phase Re-Service and Early Coord Phase Return

If the coordinated phases return early and perms are open with calls for associated
phases, the coordinator will attempt to re-service those phases.
CNA Coord Phases:
If the coord phases are in CNA Mode, the re-servicing will occur regardless of traffic
demand on the coord phases because they are in the non-actuated mode. To defeat
the re-service operation, No Early release can be programmed on the coord phases.
Actuated Coord Phases:
If the coord phases are in the Actuated Mode and return early, re-service will occur
only if the coord phases gap out before the perm closes. No Early Release can be
used to defeat re-service.

CYCLES AND OFFSET TIMES

There are a maximum of 6 cycles available in the TS 1 mode. The TS 1 cycles and
offset screen appears as follows....
‘s’ = offset values are seconds

‘%’ = offset values are in percent
Cycle # 1 2 3 4 5 6
Length 0 0 0 0 0 0
Offset 1 s 0 0 0 0 0 0
Offset 2 s 0 0 0 0 0 0
Offset 3 s 0 0 0 0 0 0
Offset 4 s 0 0 0 0 0 0
Offset 5 s 0 0 0 0 0 0
Min Length 0 0 0 0 0 0
Changes to ‘MAX DWELL’ if dwell offset seeking. See

Offset Seeking modes, page 101.
Figure 219 — Cycles and offset times screen

Values shown are from execution of Clear all Coord Parameter Values. These are not
affected by Set All Coord Options to Defaults or by Set Enhanced Coord Options to
Defaults.
CYCLE LENGTH—The cycle is the amount of time required to service all phases.
There are 6 unique cycles that each have a value range of 0-255 seconds.
It is often beneficial to program cycle lengths such that the Cycles 1 through 6 are of
ascending order. This is particularly useful for traffic responsive systems where the
3000 Master selects a particular cycle based on volume or occupancy, then and
issues the cycle (along with offset and split) command to all local intersections.
OFFSETS—Up to 5 offset values, ranging from 0 to 255 seconds, can be assigned to
each cycle (cycle 1 offset 1, etc.) Offset represents the amount of time that Local
Cycle Zero follows Master Cycle Zero. The Offset at any given point is determined by
Master Cycle Timer Value minus Local Cycle Timer value. If this yields a negative
number, add this number to the Cycle Length to yield a value between 0 and Cycle
Length –1.
Offsets determine the relative position of main street green with respect to other
intersections within the system. Offsets can be programmed in either percent or
seconds depending on the USE % FOR OFFSET ENTRY parameter setting (Basic
Operating Modes). There is a unique value for each offset (1-5) for each cycle (1-6).

Cycles and Offset Times
When programming offsets in percent, any offset can be used with any cycle because
the offset value will always be a percentage of the cycle length. When programming
offsets in seconds, if the offset is greater than the cycle length, the controller will use
modulo arithmetic to determine the proper offset. In other words, it will divide the
offset by the cycle length and use the remainder as the offset. For example, if an
offset of 90 seconds is programmed, and the cycle length is 80 seconds, the
controller will use an offset of 10 seconds.
It is often beneficial to program offsets in a consistent manner where each offset
represents a specific objective. For example, at each intersection offset 1 might
always be heavy Inbound, offset 2 might be light inbound, 3 is average, 4 light
outbound, and 5 heavy outbound. A consistent theme like this is particularly useful for
traffic responsive systems where the M3000 Master selects a particular offset based
on volume and direction of traffic, then and issues the offset (along with cycle and
split) command to all local intersections.
Adjusting Offset Times in the Field

Offset values determine relationship of the phase timing to other intersections within
the system. As a result, offset values tend to be a frequently adjusted parameter set.
Offset values are typically adjusted when a specific green (often the coord phase, but
could be any phase) is observed to be either early or late relative to other
intersections.
For example, suppose it is observed that the coordination phase green is a little late
in starting, i.e. cars in the coordinated platoon arrive then usually wait 6 or 7 seconds
for green. The offset then needs to be “moved up.’’ To do this, the coord plan actively
operating first needs to be determined. To do this, go the 1st Controller Dynamic
Display. From this determine the active cycle, and local offset. Say that Cycle 3,
offset 2 is in effect (split doesn’t matter in this case).
Now go to the Cycle and Offset programming data screen and find the Cycle 3, Offset
2 value. Say that this value is 24. To move it up by 7, change the value to 17, (or 24
minus 7). If it were desired to move it back by 7 to get the green to occur later,
change it to 31 (or 24 plus 7.)
The cycle length has to be taken into account if subtracting would be a negative
number or adding would be greater than the cycle. For example, say the current
offset is 5 for a 70 second cycle and you wish to subtract 10 seconds. A negative
number of 5 -10 = -5 will result. To get the new offset value, add the negative value to
the cycle (or subtract the absolute value). Since the cycle is 70, then 70 + (-5) = 65 is
the right offset in this case. In the other case, if adding would result in a number
greater than the cycle, use the sum minus the cycle length as the offset. For
example, for the same 70 second cycle, say 16 seconds is to be added to a current
offset of 60, then 60 + 16 = 76. Since this is greater than 70, then 76 - 70 = 6
becomes the offset.
Minimum Cycle Length or Max Dwell

One of these two parameters will appear on the line below cycle length depending on
the offset seeking mode programmed.

Minimum Cycle Length—This parameter set appears if the offset seeking mode is
short route. The values programmed determine the shortest cycle than can result
from fast timing the cycle to get in step. If a shorter cycle would be required, the 3000
will instead use add only offset seeking (cycle is longer only).
Max Dwell Times—This parameter set appears if the offset seeking mode is dwell.
The values limit the time the unit can “dwell” in the coordinated phases in any one
cycle when trying to get in step. If the unit is not in sync at cycle zero, it stops the
local cycle timer and begins to dwell until sync is achieved or the max dwell period
times out. The local cycle timer then begins timing again. If still not in sync at the next
cycle zero point it will dwell again until in sync or the max dwell period times out. This
process continues until sync is achieved.
4 Splits Per Cycle Mode

Data screens for Cycle, Dwell, and Offset times appear differently when in 4 Splits
Per Cycle mode. If 4 Splits/Cycle is set to ‘N’, the Menu appears as described in the
previous topics. However, if 4 Splits/Cycle is set to ‘Y’, the unit will display 4 splits for
each of the 6 cycles as indicated below.
Cycle # 1/1 1/2 1/3 1/4 2/1 2/2
Length 0 0 0 0 0 0
Offset 1 s 0 0 0 0 0 0
Offset 2 s 0 0 0 0 0 0
Offset 3 s 0 0 0 0 0 0
Offset 4 s 0 0 0 0 0 0
Offset 5 s 0 0 0 0 0 0
Min Length 0 0 0 0 0 0
Figure 220 — Setting timing for 4 splits per cycle mode
1/1 is cycle 1, split 1, etc. Page down for the remaining cycle/split combinations, up to
6/4.

Coordination Phase Programming
COORDINATION PHASE PROGRAMMING

Coordination phases (or just “Coord phases”) are those that are to be coordinated
with other signals in the system. Coord phases are usually “main street” phases.
Because of their special status, these phases need to be specified.
A different set of coordinated phases can be specified per cycle. This option allows
for different main street phases during different times of the day (by using cycle-offset
combinations).
For example, cycle 5 and cycle 6 may both be 110 seconds long, but when cycle 5 is
active, the main street phases are 2-6 and when cycle 6 is active the main street
phases are 4-8. The user can then alternate the coordinate phases by selecting cycle
5 or 6 per TOD plan.
Coord Phases VALUE(Y/N) 1 1 1 1 1 1 1
Cycle 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
1 X X
2 X X
3 X X
4 X X
5 X X
6 X X
Figure 221 — Coordinated phases screen
The values shown are resultant from executing Set Coord Phases To Ph 2, 6 All
Cycles. They are not affected by Clr All Coord Values, Set all Coord Options to
Defaults or Set Enhanced Coord Options to Defaults.
To individually program the coordinated phases, simply select which phases are the
coordinated phases for each cycle. Select the phases by moving the cursor to a
cycle and pressing the associated phase key or by moving under the number and
pressing the Y/N key. An ‘X’ indicates that the phase has been selected.
The screen changes if the controller is using TS 2 operation with four (4) splits/cycle
selected. The screen would then appear like this:
CYC/SPL 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
1 1
1 2
1 3
1 4
2 1
2 2
Figure 222 — Coordinated phases screen - 4 splits per cycle mode
Progressive Menu Screens display the remainder of cycle 2-6 with split 1-4 allocated
for each cycle. In TS 2, this function allows the user to select the coordination
phases on each cycle with its respective splits.

PHASE ALLOCATION
Phase allocations determine the “split times” or amount of cycle time available to
each phase during coordinated operation. If a phase has not “gapped out” by the end
of its allocation time, the coordinator will apply a force-off to proceed to the clearance
interval of that phase.
A set of phase allocations for all 16 phases is called a split plan. There are 24
available split plans. Each split plan consists of a phase allocation for all 16 phases.
Phase allocation/split plan entries depend on USE % (VS SECS) FOR PHASE
ALLOCATION as set in the Basic Operation Modes section and 4 SPLITS/CYCLE
programming as set in the Enhanced Operating Modes section.
Entering Phase Allocation Times

Percent — In this mode the 3000 requires that total sum of the phase allocations for
all rings must equal 100% provided there are no vacant Co-Phase Group-Ring cells.
Co-Phase Group-Ring cells that contain vacancies are allowed to be less than 100%.
A major benefit of programming in percent is that any split plan can be used with any
cycle. Since the phase allocation is a percent, the actual time allocated (in seconds)
will be adjusted as a percent of cycle.
Seconds — In this mode the total sum of the phase allocations for all rings must
equal the Cycle Length if all phases in sequence are used. Rings that have phases
omitted are allowed to be less than the Cycle Length. If a split plan is used with a
cycle whose length is greater than the sum of the phase allocations across a ring, a
coordination failure will occur.
EXAMPLE:
A. If sequence is 12/56 + 34/78, then Phases 1+2 must equal Phases 5+6, Phases
3+4 must equal Phases 7+8 and Phases 1+2+3+4 and 5+6+7+8 must equal Cycle
Length or 100%.
B. If sequence is 12/56 + 34, then Phases 1+2 must equal Phases 5+6 and Phases
1+2+3+4 must equal Cycle Length or 100%. In this case it is not possible to satisfy
Ring 2 summing to 100%.
Coord allocation screens are shown below. Note that these screen are examples with
appropriate values for 8 phase dual ring operation. Had Clr All Coord Values been
executed, all allocations would be set to 0’s. Allocation screens are not affected by
Set All Coord Options to Defaults or Set Enhanced Options Only to Defaults.

Phase Allocation
Example 1, allocation mode in percent:

Shows cycle 1-6 if in Not an entry, shows value from
4 splits/cycle mode cycles & offsets screen (blank if not
or split 1, 5, 9, 13, 4 splits/cycle mode).
etc. if 24 split plans. Shows ‘%’ if in percent mode or
‘sec’ if in seconds mode.
Cycle 1 = 90 Totals: R1: 100 R2: 100

Not an entry, shows
Phase Allocations in % R3: 000 R4: 000
running total per ring
Phase 1 2 3 4 5 6 7 8
from split 1-4. Split
Split 1 20 35 18 27 20 35 18 27 shown depends on
Split 2 0 0 0 0 0 0 0 0 which split row cursor
Split 3 0 0 0 0 0 0 0 0 is currently in.
Split 4 0 0 0 0 0 0 0 0
SHIFT-RT.-> TO VIEW OR ENTER PHASES 9-16 The values shown are
0-100% if in % mode,
or 0-255 secs if in
Phase allocation entries
seconds mode.
Figure 223 — Programming phase allocation times - example 1
Page down for cycles 2-6 if 4 splits/cycle mode, or splits 5-24 if the controller is set to
the 24 split plan mode.
For the example above, assume the cursor is in the split 1 row. Note that the
allocation values add up to 100% in each ring as indicated by the totals display (only
rings 1 and 2 are used).
Example 2, allocation mode in seconds:
Cycle 1 = 90 Totals: R1: 90 R2: 90
Phase Allocations in sec R3: 000 R4: 000
Phase 1 2 3 4 5 6 7 8
Split 1 18 32 16 24 18 32 16 24
Split 2 0 0 0 0 0 0 0 0
Split 3 0 0 0 0 0 0 0 0
Split 4 0 0 0 0 0 0 0 0
Figure 224 — Programming phase allocation times - example 2
Again, assume the cursor is in the split 1 row. Note that in this case the allocation
values add up to 90 seconds in each ring as indicated by the totals display (only rings
1 and 2 are used). These are the same relative values as example 1, only in seconds.

Additional Details Concerning Phase Allocation

1. Phase allocations include the phase green + yel + red clear time (not just
green). The green time thus provided is the equivalent allocation value in
seconds minus (yel + red).
2. Phase allocations must be sufficiently large to provide at least basic phase
timing. As a minimum, the allocation must equal the phase INITIAL + YEL +
RED CLEAR + 1 second. If insufficient time is provided to meet this
requirement, the value will be accepted but will result in a “Bad Coord Plan”
failure when the plan is activated. If the phase has ped timing, substitute WLK
+ PCL for INITIAL above. Ped timing can be excluded from the check coord
plan algorithm (see Check Coord Plan description page 265).
3. When in the 4 Splits Per Cycle Mode (Enhanced Options) there are 4 splits
(1-4) per cycle. When 4 Splits Per Cycle is disabled, there are 24 splits (1-24)
total for all cycles.
4. Specific data fields can be selected for any specific split (4 Splits/Cycle=‘N’) or
cycle (4 Splits/Cycle=‘Y’) by entering the split or cycle number at the SPLIT or
CYCLE menu item in the upper left corner of the screen. The PGUP and
PGDN keys also move the cursor through the different splits and cycles.
5. Phase allocations must be entered for all active phases. Unused phases may
be left with zero allocation values.
Adjusting Allocation Times in the Field

Phase allocations determine each phase’s green time during coordinated operation.
Thus, along with offset values, phase allocations tend to be a frequently adjusted
value set. Such adjustment is typically required when it is observed that a phase or
phase pair have too much or too little green time. When adjusting an allocation time
for a given phase, however, the time for another or several phases must also be
adjusted as well so that the total split plan time remains the same. Each ring must
equal either the cycle length if in seconds mode, or 100% if in percent mode.

Offset Seeking
OFFSET SEEKING
This option specifies which type of Offset Seeking to use during transition from Free
to Coordination, between patterns such as Cycle or Offset changes, or after
Preemption. Sync pulses may be physically received in a hardwire interconnect
system or they may be internally generated by a time base reference (a function of
the time of day and current cycle length).
In either case, when the cycle or offset changes, the controller must usually adjust the
local cycle timer to the new reference. Since the controller cannot simply jump to any
percent within the cycle (if so, phases and permissives could be skipped), the
controller utilizes an Offset Seeking method to gradually seek the new sync point with
minimal disturbance to the signal operation.
Offset Seeking Mode: 2
Mode determines how cyc timer seeks ofst

0 = Add only, times 20% slow only.
1 = Dwell, stops at cyc 0, but no more
than max dwell setting per cycle.
2 = Short Route, times 20% fast or slow
depending on which syncs fastest
Offset seeking mode is set to 2 (short route) by execution of Set All Coord Options to
Defaults. The offset seeking mode is not affected by Clr All Coord Values or Set
Enhanced Options Only to Defaults.
Types of Offset Seeking

There are 3 types of offset seeking that can be selected, as described below.
Add Only (Program ‘0’)

This procedure moves Local Zero to the offset by lengthening the cycle only. This is
accomplished by actually timing 1.2 seconds for each second in the cycle that
elapses until the new offset is reached (local times slow). This represents a 20
percent increase in cycle time and is evenly distributed among all phases in the cycle.
Because the seeking is in one direction only, it may take up to five cycles to get in
sync. See the Short Route method, described on the next page.
However, phases can only time longer and never shorter than their allocation time.
Short route is generally preferred in most cases, but Add Only may be preferred when
phase timing is critical, such as with long pedestrian phases.
Dwell (Program ‘1’)

Dwell seeking allows the controller to rest in the coordinated phases until the new
offset point is reached. If dwell offset seeking is chosen, a maximum dwell time
should be programmed in the cycle length programming screen. If the dwell timer for
the coordinated phases times out before the new offset point is reached, the
controller will leave the coordinated phases, cycle around and then will begin dwelling

again during the coordinated phases. Dwell mode is similar to the technique
electromechanical controllers use to get in step and is not widely used anymore.
Short Route (program ‘2’)

Short Route offset seeking moves Local Zero to the offset by a process that either
shortens or lengthens the cycle time by 17 and 20 percent, respectively - whichever
achieves sync fastest. The +20% long or –17% short is evenly distributed among all
phases in the cycle. Because it can seek in either direction, the most out-of-sync the
unit can be is 50% of the cycle. The unit accomplishes this by actually timing either
0.83 or 1.2 seconds for each second in the cycle that elapses until the new offset is
reached.
Although similar in operation to Add Only, the ability to shorten the cycle can
considerably speed up the seeking process. For example, say that the Local Zero
point arrives a few seconds late relative to where it should be. With dwell or add only,
since the cycle can only be increased, the unit has to essentially seek “all the way
around” the cycle to get in step. With short route, it can simply speed up the cycle for
a brief period and get in step quickly.
If short route offset seeking is enabled, a Minimum Cycle Time may be defined in the
Cycle Time programming screen. That time is recognized when offset seeking in the
shorten direction is considered. If such seeking would cause the cycle to time less
than the minimum, add only offset seeking will be used instead.

Coordination Plan (COS/F) to TOD Circuits
COORDINATION PLAN (COS/F) TO TOD CIRCUITS

This option provides for activation of TOD circuits when the status of current cycle,
offset, split or free operation matches the specified combination. A “wildcard” value
(don’t care state) for any of the entries can also be specified to activate the circuit for
any value of that entry. For example, 7/6/25/1 is a typical combination that activates
the associated circuits whenever the unit is in coordination, regardless of the
particular cycle, offset or split. (7, 6, 25 = activates for all for cycles, offsets, and splits
respectively).
There are 10 C/O/S/FREE plans with 5 available circuits.
Programming a Plan
1. Enter non-zero values for the desired combination of cycle, offset, split and
free status (0=free, 1=coord, 2=either) to activate the circuits. Programming a
“don’t care” cycle value of 7 indicates all cycles, 6=all offsets, 25=all splits,
2=free or coord.
2. Once the C/O/S/FREE values have been entered, program up to 5 TOD circuit
numbers for activation. Refer to Appendix A for a detailed listing of available
TOD circuits.
Upon entering a circuit number, the display will show a 3 character
representation of the selected circuit (e.g., Max Recall Phase 8 = MR8). A zero
circuit number will erase any existing circuit number.
Cos/Fre To TOD Ckts Value: Ckts 0-255
0= No Ckt, Dont Care C/O/S/Free=7/6/25/2
# C/O/ S/FRE Ckt Ckt Ckt Ckt Ckt
1 1/3/2 /1 VO3
2 7/6/25/1 IM1 IM2 CN1 WRM
3 / / /
4 / / /
5 / / /
Figure 225 — Coordination plan to TOD circuits screen
Note Because TOD circuits 1 through 11 are the COS/Free circuits themselves,
they cannot be used as activated circuits. Such use would result in
“circular” logic.
The screen above shows an example where ph 3 vehicle omit will be applied during
Cycle 1, Offset 3, Split 2 of coordinated operation. The second line tells the system
that Inhibit max 1 & 2, CNA I, and the Walk Rest Modifier (WRM) will be applied when
in coord operation for any cycle, offset, and split. All three are set to ‘don’t cares’
except the “1” for coord).
The COS/F to TOD ckts are all cleared by execution of Set All Coord Options to
Defaults. However, this programming is not affected by Clr All Coord Values or Set
Enhanced Options Only to Defaults.

ENHANCED COORDINATION OPTIONS

The Enhanced Options menu covers a variety coordination functions that are
somewhat less frequently programmed, i.e., they are less frequently used or are less
likely to be changed from the default value.
Coordination Enhanced Options Menu
1.Operating Options 5.No Early Release

2.Cycle Sync Options 6.C/S To Time Plan
3.Man/Auto/FO. Perms 7.COS To Lead Lag
4.Local Split Modes 8.Offset to Free
Figure 226 — Enhanced Coordination Options Menu
Operating Options
These are miscellaneous per unit parameters that affect coordinated operation.
Coordination Enhanced Operating Modes
Enhanced Perm: N Invert Free In: N

Central Override: N Split Matrix: N
No PCL Ofst Adj: N 4 Splits/Cycle: Y
No Early Coord Ped: N
Pgdn For More Enhanced Operating Modes

Figure 227 — Coordination enhanced operating modes
To see the rest of the options, press PGDN :
Enhanced Operating Modes Continued...
Yield Percent: 10 (0-10%)

EGB%: O (0-100%)
RGB%: O (0-100%)
# of Cycles To
out of step: 0 (0=disable)
Figure 228 — Coordination enhanced operating modes - page 2

The enhanced screens above reflect the state as set by execution of Set All Coord
Options to Defaults or Set Enhanced Options Only to Defaults. Not affected by Clr All
Coord Values.

Enhanced Coordination Options
Enhanced Perm
Enhanced Permissive operation modifies Manual Perm operation by dropping the
start of permissives back to zero once a side street phase has been serviced. This
mode should be enabled in most cases whenever permissives are programmed
manually—and especially if programmed in a sequential fashion similar to single
mode permissives, where not all perms start at the same time.
Purpose: The purpose of this function is to insure that downstream phases don’t get
skipped if the first phase after the coord phase gaps out before the next permissive
starts. Under such a circumstance the unit would see no other phases permitted and
would cycle back to the coord phase (this is undesirable). This will not occur if perms
go back to zero once a side street starts.
Enhanced Permissive operation has no effect on Yield and Multi Perms because the
permissives for all phases start at the same time. Auto Perm Single Permissives
always drop the start of permissives back to zero once a side street has been
serviced regardless of enhanced perm programming (see permissive types page
229).
Central Override
This parameter controls the ability to override coordination patterns (including Flash
and Free operation) from a central computer. If a ‘Y’ is programmed, central overrides
will be allowed. If it is programmed with an ‘N’, an operator at central will not be able
to remotely control coordination patterns or other features. If a Central Override is in
effect when this value is changed, control will revert to the normal coordination plan (if
any) as defined by the sourcing parameters at the end of the current cycle.
No PCL Offset Adj

This feature applies when the coord phases are in CNA Mode and End of Main St
referencing is used. Normally when this feature is disabled (N), the offset value is
internally adjusted so that the end of green is the offset reference point even though
the unit rests in walk while permissives start at the end of walk (zero). No Ped
Clearance Offset Adjust prevents this adjustment forcing the coordinator to reference
the Offset to the end of Walk.
This feature is used only in very specific applications, where Offsets may have been
previously established and have already taken Ped Clearance timing into account.
EXAMPLE: Offset is Zero, Coord Phase Ped Clearance = 20 seconds and Cycle =
100 seconds, End of Main St = (Y). If No PCL Offset Adj is disabled, Master Zero
occurs at Local 20 (end of green) and “Actual Offset” = 80. However, if it’s enabled,
Master Zero occurs at Local Zero (end of Walk.)
Invert Free In
This option allows the ‘free’ signal in a hardwire interconnect system to be inverted.
Typically a ground (0 volts) on the free input (D-module) initiates free operation (not
coordinated). This option allows a ground to be the default (coordinated) and a
120VAC signal to initiate free. It can also be used as a way to manually initiate
coordination.

Split Matrix
The split matrix is a matrix of split plan values for each cycle-offset combination.
When enabled, the controller will reference this matrix based on the current cycle and
offset to determine which split plan to implement. Any other source of split (Master,
TOD, etc.) is ignored by the controller.
4 Splits/Cycle
This option enables 4 split plans per cycle, rather than 24 split plans. If this option is
enabled, splits 1-4 are associated with cycle 1, splits 5-8 with cycle 2, etc., but are
referenced as splits 1-4 for each cycle n. If this option is not enabled, all data entry
dealing with splits will be displayed in a split 1-24 for all cycles format. If the user
changes the value of 4 Splits/Cycle, the programmed values will automatically be
adjusted to the new format.
Table 40 – Splits under 4 splits/cycle and 24 split plans
4 SPLITS/CYCLE=“NO” 4 SPLITS/CYCLE=“YES”
SPLIT 1 SPLIT 1 for CYCLE 1
SPLITS 9-12 SPLITS 1-4 for CYCLE 3
No Early Coordinated Phase Ped Service

This option applies only to actuated mode on the coordinated phases.
If it is enabled, the peds will not be serviced until the point in the cycle at which the
coordinated phases would have been serviced had all phases been extended to their
force off points.
If it is disabled, pedestrian movements on the coordinated phases will be serviced at
the same time as the vehicle movements on those phases.
Typical Use:
To prevent coord peds from defeating “phase re-service” during actuated coordinated
phases. If the coord phase returns early with a ped call in memory, the ped call will be
stored until all perms are timed out, giving an opportunity to re-service permitted
phases if the coord phases gap out.

Ped Override Mode (TOD Circuit Activated)

There is no programming for Ped Override mode; it is activated by TOD circuit 97
(labeled POM). If this circuit is active and an actuated ped is serviced, the local cycle
counter is ‘frozen’ at the force off point of that phase until the end of the pedestrian
clearance interval. Then the counter resumes timing from where it left off and the
controller immediately begins offset seeking until it gets back into step. The
coordinator also sets EPPn equal to EPn when this feature is active.
There is also a TOD circuit available to inhibit such Ped Overrides. Time Of Day
circuit #133 Is labeled ‘IPM’ and prevents the local cycle timer from pausing when a
phase cannot be forced off due to a large pedestrian movement. This circuit also
allows the coordinator to run a pattern that has an actuated ped phase that is longer
than the time allocated to the phase.
Typical use:
Ped Override Mode is typically used for any actuated Ped that is seldomly used. The
split plan timing then is set-up for normal vehicular demand and does not take into
account ped timing. When the occasional ped occurs, the cycle timer stops to
accommodate it, a late return occurs, then offset seeks to get in step.
Ped Override must be ON if (Walk + Ped Clearance + Yellow + Red) is greater than
the Phase Allocation and when executing “Check Coord Plan”, answer N to “Include
Ped Times”. If Ped Override is not ON in this case, the 3000E will not run in
Coordination (a Bad Coord Plan error will be generated.)
Note Ped Override works best when Short Route Offset Seeking is selected. Many times
the relatively small offset error can be corrected in one cycle versus up to 5 with
Dwell or Add Only Modes.
Yield Percent
The yield percent determines the percent of cycle the yield permissive period will be
open. The period starts at the main street force off point. For example, if the yield
percent value is 10% and the cycle is 100 seconds, the yield permissive will last for
10 seconds from the main street force off point. This value must be non-zero and less
than 11 if the yield type auto permissive calculation is chosen, otherwise Check
Coord Plan will not pass.
EGB% (Extended Green Band Percent)

Extended Green Band (EGB) percent (of cycle) is used to allow the coordinated
phase to extend beyond the normal yield point in the presence of coordinated phase
demand without regard to side street demand. The extension capability does not
occur when CNA is active. The extension period is ended if the coord phase(s) gap
out. Max timing is usually not a factor because the Max Timer does not start until the
coord phase yield point occurs. EGB% should be used cautiously because the extra
time “cuts into” the non-coordinated phase’s allocation time, and can even cause
phases to be skipped.
Typical use:

This function must be used carefully because the EGB time extends into the non-
coordinated phase’s time. It may even skip phases if the percent (of cycle) is large
enough to time past the end of the first permissive. For this reason, the amount of
time that EGB% will encroach into the next phase(s) must be accounted for so that
phases will not be skipped or short timed. It is generally recommended that EGB%
only be used when the next phase(s) in service has a large enough relative allocation.
This is most likely with 2 phase operation and least likely with multi-phase operation
like 8 phase quad.
EGB Compensation:
One way to compensate for EGB% is to set the normal coord phase allocation times
so that they are based on less than peak periods and then slightly over-allocate the
first non-coord phases. EGB% can then be used to extend the coord phase so that it
cuts into the non-coord phase over-allocation. If necessary, Max Times on the first
non-coord phases can be used to limit their green time when they start early due to
lack of coord phase demand. This will help to distribute the extra time to downstream
phases.
RGB% (Reduced Green Band Percent)

Reduced Green Band (RGB%) percent (or cycle) is used to allow the coordinated
phase gap out some time prior to the normal yield point when there is lack of demand.
The coordinated phase in effect is allowed to gap out early.
Typical use:
This function can be used more confidently because the coordinated phase will not
time past its normal allocation, only less. There is not the problem of inadvertently
short-timing or skipping non-coord phases.
Many times in a given cycle, the “tail end” of the green band may contain no demand
and it is more efficient for this time to be used by demanding phases. This reduces
delays on all phases and avoids wasting green time (compared to CNA or Max Recall
methods.) Floating Force Offs and RGB maximizes early return, which can be
beneficial to clear standing queues in preparation for the green band. Fixed Force
Offs and RGB also allows the first phases (i.e., 3 & 7) after the coord phases to
receive extra time. With CNA, these phases will never start early and therefore the
Force Mode used has no effect on these phases.
EGB% and RGB% General Notes

Either or both of these options can be used when the main street has detection and
there is a desire is to allow the main street green to vary somewhat based on
demand. This might be the case when the coord phase demand surges during peak
demand (EGB%) or slacks off during off-peak periods (RGB%). Note that in the
normal mode (zero EGB% & RGB%), the coord phase cannot extend beyond or
terminate before the yield point regardless of demand.
The yield point is the time in the cycle is when the coord phase(s) (main street) is
permitted to serve other phases. The yield point is local cycle zero if the offset is
referenced to the end of Main Street Green (Basic Options Menu), or it is cycle zero
plus the coord phase allocation time less clearances if the offset is referenced to the
beginning of Main Street Green. In the normal mode the coord phase(s) cannot

terminate early because hold is applied until the yield point occurs. Conversely, the
coord phase(s) cannot extend beyond the yield point because it is forced off.
Number of Cycles to Out-of-Step

This feature will check for the coordinated phases being ON each cycle around the
Local Zero mark. If the coordinator has determined that the above is not satisfied for
the consecutive number of cycles programmed, the coordinator reverts to Free with
“Free: Coord Out of Step” displayed. Setting Zero disables this monitoring feature.
Once in Free, the controller must be powered down to clear the fault.

Cycle Sync Options

Sync Options
Sync Source: 0 (0=TOD/CL/Inter, 1=City

Zero, 2=Absolute)
(0-Cycle time-1 for City Zero/Absolute)

Cycle 1: 0 Cycle 2: 0 Cycle 3: 0
Cycle 4: 0 Cycle 5: 0 Cycle 6: 0
Figure 229 — Cycle Sync Options screen
There are two programming screens in this section; the first deals with the sync
source mode which determines how sync pulses are referenced to the clock. The
second screen deals with setting up sync pulse monitoring to establish criteria for
going free based on problems with sync pulses or offset lines.
The programming of the sync screens above reflect the state as set by execution of
Set All Coord Options to Defaults or Set Enhanced Options Only to Defaults. Not
affected by Clr All Coord Values.
SYNC SOURCE programming provides the time clock sync reference during
coordinated operation. Note that this referencing determines how the master cycle is
to be referenced to the clock. The local cycle then references itself to the master
cycle by offset seeking. There are 3 sync reference options: TOD/CL/INTER (0), CITY
ZERO (1), or ABSOLUTE (2).
If City Zero or Absolute are selected, the City Zero or Absolute adjustment factor must
also be programmed. The sync reference is automatically calculated upon entry of
this data. City Zero and Absolute sync reference programming also require that valid
cycle lengths be entered for all cycles used.
Sync Source Terms

TOD/CL/INTER—Time of Day, Closed Loop or Interconnect. This mode is based on a
once per day reference point. The controller finds the master cycle sync point by
calculating where the current cycle should be currently by determining the number of
cycles that would have elapsed from the reference point.
For example, if the cycle is 60 and reference point is 00:00 (midnight), then the unit
would compute a master sync point each minute on the minute. For a 70 second
cycle with the same time reference, the first master cycle would be at midnight, then
00:01:10, then 00:02:20, etc. The cycle is reset each day at this same point no matter
where it is in its current cycle. This is a once per day referencing scheme.
The reference point is entered in the Sync Reference programming under Time of
Day. The INTER mode refers to hardwire interconnect systems and the sync point is
a physical sync pulse received by the controller.
CITY ZERO—City Zero sync reference calculates the sync point by using a
programmed reference from midnight. The first time a value is entered (or edited) for
each cycle for City Zero, it becomes the reference from the previous midnight. From
this reference point, the controller calculates the sync points by cumulatively adding

cycle lengths. Upon reaching the subsequent midnight’s, new sync reference values
are calculated by finding the first sync point past midnight at the end of the whole
cycle. The value entered for each cycle must be less than the cycle length.
ABSOLUTE—Absolute sync reference is similar to City Zero except that the sync
reference is calculated based on the current time. When the value is entered for
Absolute sync reference, the controller adds that value to the current time and then
calculates the cycle length backwards to midnight to find the first sync point after
midnight. This value becomes the sync reference for the current day. Subsequent
days are calculated on a moving sync reference the same as City Zero.
When data is entered for absolute, the value on the screen will change to show the
actual sync reference point (past midnight). The data entered for absolute is the
number of seconds past the current time until the next sync point. The controller then
calculates back to midnight to obtain the sync reference.
TOD/CL/Inter vs. City Zero Or Absolute Modes

The TOD/CL/INTER mode references once per day at the same time every day. The
master cycle thus gets reset at this point every day regardless of where it is at the
time. This is the preferred method if synchronizing with all digital units of similar
capability, but is not if attempting to synchronize with a non stopping, free running
reference like a dial unit. This is particularly the case for cycles that do not divide
evenly into 24 hours like a 70 second cycle. A TOD/CL/INTER type reference would
drift away from a 70 second dial after the first day because it would re-sync each day
while the dial would not.
The CITY ZERO and ABSOLUTE methods are designed to accommodate free
running referencing systems by finding the reference at a point in time, then
continually re-computing the reference each day based on the cycle length. These
methods can be used to sync with free running electromechanical dial units.
Typical Uses of the Various Sync Referencing Modes

TOD/CL/INTER mode. This mode is the most commonly used mode of sync
referencing, with midnight as the most common reference point (although 2 AM and 3
AM are also relatively common). This mode should be used unless one the of other
two modes below are specifically required.
City Zero Or Absolute mode. These two modes basically accomplish the same
thing; to sync to a free running dial or city wide tone system. The mode is chosen by
preference. The Absolute Mode is, however, generally easier to use.
How To Use The City Zero And Absolute Modes

City Zero—To use this mode, the offset from midnight must first be determined for
that day. For example, suppose it is 08:11:55 AM when the tone (or end of observed
cycle) occurs. This represents (8 x 3600) + (11 x 60) + (55) = 29,515 seconds from
midnight, or 29515 / 70 = 421.6429 cycles from midnight. The product of the fractional
portion only, times the cycle is .6429 x 70 = 45 seconds. This means that if the cycle
had been midnight referenced, it would have been 45 seconds into its last cycle at the
observation point. Since it should be 0 at that point, it needs to be moved up by 45
seconds. The programmed reference value thus becomes 45 in this case.

Absolute—To use this mode, simply enter a zero into the Absolute Cycle Time value
for the desired cycle, but do not hit Enter or an Arrow key yet. Listen for the tone or
observe the end of the reference cycle (say the main street yellow at the reference
intersection) then hit Enter (or an Arrow key) at that precise moment. The 0 value will
then change to the computed offset reference from midnight for that cycle.
Manual/Auto Mode of Force Offs and Permissives

This option menu allows force offs and vehicle and ped permissives to be set to the
manual mode rather than auto-calculated by the unit based on allocation values. The
default mode is AUTO.
Permissives & Force Off Menu
1. Set Manual/Auto Mode (FO. Perm. Ped)

2. Load Manual Permissives
3. Load Manual Force Offs
Figure 230 — Permissives and Force-offs Menu

Choose option 1. Set Manual/Auto Mode (FO. Perm. Ped)
Permissives Mode
Auto Perm
& Fo: Y (N For Manual Perm & Fo)
Ped Perm: 0 (0 = Auto, Or 1-255 Secs)
Note: Man Perm % vs sec mode set by Ph

Allocation setting in Basic Options
Figure 231 — Selecting a permissives mode

The screens above reflect the state as set by execution of Set All Coord Options to
Defaults or Set Enhanced Options Only to Defaults. Not affected by Clr All Coord
Values.
Auto Perm (Manual vs. Auto Mode for Vehicle Perms & Force Offs)
This option determines whether Force offs and Permissives will be automatically
calculated from the Phase Allocation settings or manually programmed. When
enabled (Y), the automatic mode is chosen and the subsequent calculations are
based on the user defined Phase Allocation values (see page 240) and the relative
position of force offs within the cycle. The calculations are also based on various
control settings in the Basic Options menu, such as Reference to End (vs. Beginning)
of Main St., Fixed vs. Floating Force Offs, and Permissive Type.
When the Auto Mode is used (Y), the user is saved the effort of computing, then
manually entering permissives and force offs. When the manual mode is chosen (N),

the user must individually program each force off and permissive, but can do so
according to his/her own preferences.
Ped Perm (Manual vs. Auto Mode for Pedestrian Permissives)

This option defines Auto or Manual Permissives for pedestrian movements. If Auto
Ped is selected by programming a ‘0’, then the permissive periods will be calculated
automatically from the Manual or Auto Force Offs. If a positive value (1-255 seconds)
is programmed, the Ped Permissive will start with the phase permissive (SPPn =
SPn) and then end after this programmed value (SPPn + value = EPPn). Note that
the start of ped permissive is dependent on the phase permissive, which may vary
depending on the type perm selection. Also note that Auto Perm calculations may be
used for the vehicle permissives (AUTO PERM: Y) and Manual Permissives for Peds,
or vice versa.
Time of Day Activation of Auto and Manual Perm Mode

Time of Day Circuit 130 “APM” Auto Permissive Enable, when active, causes the
Auto Permissive Mode to determine permissive and force off points. Time of Day
Circuit 131 “MPM” Manual Permissive Enable, when active, causes the Manual
Permissive entries to determine the permissive and force off points. These circuits
have priority over the “Auto Perm & FO” entry in the above screen. If both APM and
MPM Circuits are active, APM will have priority.
Note Per pattern Manual or Auto Perm & FO can be achieved by using “C/O/S to TOD
Circuits” programming using 130 and 131 as noted above.

Load Manual Permissives

Manual Permissive entry is only required if AUTO PERM & FO operation is
programmed ‘N’ (not auto). Select 2 from the Permissives And Force Offs Menu
above to manually program permissives. Note that a detailed description of
permissives operation can be found earlier in this section. Recall that if demand
occurs on a phase during that phase’s permissive window (between start and end in
the cycle), that phase may be serviced during the current cycle; otherwise, the phase
will not be serviced (not “permitted”).
For manually entered permissive operation, the start and end permissive values for
each used phase for each split plan must be entered. Data Entry will be different
depending on the Use % (Vs Secs) For Phase Allocation setting from the Basic
Options screen. If the setting is in percent, then manual permissive must be in
percent as well. If seconds, then they are loaded as seconds.
Choose option 2 from the Permissives And Force Offs Menu
Cycle 1 Perms (0-255 Secs)
SPL 1/PH 1 2 3 4 5 6 7 8
Start 10 0 0 5 10 0 0 5
End 50 0 7 30 50 0 7 30
SPLIT 2
Start 10 0 0 4 10 0 0 4
End 48 0 4 30 48 0 4 30
Figure 232 — Loading manual permissives times (24 splits/cycle mode)
Shown in the 24 Splits/Cycle mode, with time in entered in seconds. Had the Use %
(vs. seconds) for Phase Allocation been set to ‘Y’, the values would loaded as
percents and the upper right corner would display VALUE (%:0-100) instead of 0-255
seconds.
Remember, these values are cleared to zero by Clear all Coord Parameters.
Note Permissive values for the coordinated phases are ignored. Other phases are
permitted from the coord phases (coord phase are always permitted).

Load Manual Force-Offs

Manual Force off entry is only required if AUTO PERM & FO operation is
programmed ‘N’ (not auto). Select item 3 from the Permissives And Force Offs Menu
above to manually program Force Offs.
CYCLE 1 (0-255 secs)

Force Off Points 4 Slits/Cycle: Y
Phase 1 2 3 4 5 6 7 8
Split 1 63 0 19 46 63 0 19 46
Phase 1 2 3 4 5 6 7 8
Split 2 60 0 15 44 60 0 15 44
Figure 233 — Loading manual force-offs for cycle 1
Shown in the 4 Splits/Cycle mode, with time entered in seconds. Had the Use % (vs.
seconds) for Phase Allocation been set to ‘Y’, the values would loaded as percents
and the upper right corner would display VALUE (%:0-100) instead of 0-255 secs.
For each split and phase, program the appropriate force off point based on where the
coord phase ends and the relative position of the phase. In the example above, the
coord phases are 2 and 6 and force off at cycle 0. The next phases are 3 and 7, then
4 and 8, then 1 and 5.
Note Manual Force Offs with Fixed Force Offs do not require the user to enter Phase
Allocations.
Phase Allocations must be entered when Floating Force Offs are used regardless
of whether Manual or Auto Perm is used.
Local Split Modes

The Local Split Modes screens provide for two special means of selecting local split.
The first is an adaptive split mode, which is a demand based means of split selection.
The second uses a matrix that filters split selections.
Adaptive Split
Adaptive split allows various splits to be automatically selected based on demand.
Each split is assigned a set of selective phases which apply to selection of that split.
The selection technique is based on choosing the split with the greatest number force
offs occurring on its selected phases for a defined number of cycles. Ties go the
lower number split. The minimum number of total force offs required to make a
change is also specified. The concept is derived from the fact that, if a phase (or
phase pair) is constantly being forced off, then it is using all its split time in the base
split (typically split 1).

The split associated with those phases would typically be programmed to favor them
in terms of phase allocation.
Adaptive Split Control Value (0-255)
Cycles/Period: 0 MIN FORCE OFFS: 0
VALUE YES/NO) 1 1 1 1 1 1 1
Split\Ph 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
1
2
3
4
Figure 234 — Adaptive Split control screen
Enabling Adaptive Split

Adaptive split must be enabled by clock ckt. 127 in addition to the above
programming. For full time adaptive split, go to the Time of Day Menu, Circuit
overrides, and set ckt 127 ON. For time of day adaptive split, leave ckt. 127 in the
TOD mode and program ckt 127 ON/OFF by time of day in a day plan.
Cycles/Period—This setting determines the number of cycles the sample will be
based on. Typical values are 1-5 cycles. Each split will then tally the total force offs
occurring on its selected phases for this number of cycles. The number of cycles also
determines how often the split can change.
Min Force Offs—This setting determines the minimum number of force offs that must
occur for an adaptive split to be selected. Typical settings are from 1 up to the highest
number of force-offs possible over the period. The highest number possible would be
the number of phases assigned to each split times the cycles/period setting. For
example, if 2 phases are assigned to each split (dual ring) and the number of
cycles/period is 3, then 6 would be the highest number of force offs that could occur.
The Min Force Offs setting could be no more than 6 in this case or adaptive split
could never occur. If the Min Force Offs equals the maximum possible number, then
every phase must force off every cycle for its split to be selected. They must then
continue to force off every time to remain in that split or it will go back to the default
split (1).
Split 1 as Base Split

Split 1 is typically set up to be the base split. This is done by simply not assigning any
phases to split 1. Operation will then default to split 1 as long as no other split
exceeds the minimum number of force offs (based on its assigned phases) over the
number of cycles period.

Assigning Phases to Splits

Typically for splits 2 - 4, assign each a phase or compatible phase pair (e.g. 1 & 5, 3
& 7, 4 & 8). The coordinated phases are usually not included because the base split
(1) is set up to accommodate them. Adaptive split is then used for side phases. In
simple cases, only one adaptive split (split 2) will be assigned.
Example 1: Simple 2 phase, where Phase 1 is Main Street and 2 is a side street
Adaptive Split Control VALUE (0-255)
VALUE YES/NO) 1 1 1 1 1 1 1
SPLIT\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
1
2 X
3
4
Figure 235 — Adaptive Split Control - example 1
In this case only one adaptive split is used based on a 2 cycle period. Split 1 is the
base split and has no phases assigned. Split 2 is the adaptive split and is assigned
phase 2. Split 2 is set up to allocate more time to phase 2. As long as phase 2 doesn’t
force off every time (min force offs = max possible force offs), then split 1 will remain
in effect. If phase 2 forces off both sample cycles, then split 2 is selected. Split 2 will
remain in effect as long as phase 2 keeps forcing off every time. If not, it returns to
split 1 at the end of the 2 cycle period.
Example 2: 8 phase, where Phases 2 and 6 are Main Street
Adaptive Split Control VALUE (0-255)
VALUE YES/NO) 1 1 1 1 1 1 1
SPLIT\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
1
2 X X
3 X X
4 X X
Figure 236 — Adaptive Split Control - example 2
In this case all adaptive splits are used, but again based on a 2 cycle period. Split 1 is
the base split and has no phases assigned. Split 2 is assigned phase 4 and 8, split 3
is assigned 3 and 7, and split 4 is assigned 1 and 5. This order is chosen based on
the fact that ties go to the lower numbered split and, in this case, 4 and 8 are deemed
the most important adaptive split phases. Thus, if all phases force off all the time,
then split 2 will be selected, which would favor 4 and 8.

Adaptive Split Inhibits (2nd page Local Split Modes)

If you page down from the Adaptive Split Control screen, you will see this screen:
Adaptive Split Inhibits

VALUE(YES/NO)
CYC 1 1 1 2 2 2 3 3 3 4 4 4 5 5 5 6 6 6
SPL 2 3 4 2 3 4 2 3 4 2 3 4 2 3 4 2 3 4
OFF1 X
OFF2 X
OFF3 X
OFF4
OFF5
Figure 237 — Adaptive Split Inhibits screen
Adaptive split selection of splits 2-4 can be inhibited when certain combinations of
cycle and offset are in effect. In the example screen above, split 2 cannot be selected
by Adaptive Split* if Cycle 1, Offset 1 is in effect. Similarly, split 3 cannot be selected
if Cycle 1, Offset 2 is in effect, and split 4 cannot be selected if Cycle 1, Offset 3 is in
effect.
Note The inhibited split may still be selected by the Normal Split Source. These inhibits
only apply to Adaptive Split selection.

Split Matrix
The Split Matrix (on the third page of Local Split Modes) is a table of split values that
covers all of the possible cycle-offset combinations. This option gives the user full
control of specifying split plans regardless of the pattern source. When Split Matrix is
enabled, the controller will always use the split specified here.
For example, the controller may be operating traffic responsive per a closed loop
master. The master is calling for cycle 3 - offset 2 - split 3. If the split matrix is
enabled, the controller will ignore the split 3 from the master and will look to see what
split is specified for cycle 3-offset 2 in the split matrix.
To enable the split matrix, enter a ‘Y’ for Enable Split Matrix. The programming
of 4 Splits/Cycle will alter the data entry within the split matrix itself.
If 4 Splits/Cycle is active, then specify a split 1-4 for each cycle n-offset
combination.
If 4 Splits/Cycle is not active, then specify a split 1-24 for each cycle-offset
combination.
The value of the 4 Splits/Cycle option can be changed from this screen without having
to return to the Operating Modes screen by entering a ‘Y’ or a ‘N’ for the 4
Splits/Cycle menu option. The data entry format will change automatically for this
screen as well as for all other screens relative to 4 Splits/Cycle.
To use the Split Matrix option, page down from the Adaptive Split Inhibits screen.
It looks like this in 4 Split/Cycle Mode:
Enable Split Matrix: Y VALUE(0-4)
4 Splits/Cycle: Y
Cycle 1 2 3 4 5 6
OFFSET 1 1 2 2 2 1 2
OFFSET 2 2 1 4 1 2 1
OFFSET 3 4 2 1 1 2 2
OFFSET 4 3 2 2 1 2 2
OFFSET 5 1 1 2 1 1 1
Figure 238 — Split Matrix setup screen - 4 split per cycle mode
And like this in 24 Split Mode.
Enable Split Matrix: Y VALUE(0-24)
4 Splits/Cycle: N
Cycle 1 2 3 4 5 6
OFFSET 1 1 2 2 2 1 2
OFFSET 2 23 16 6 6 2 1
OFFSET 3 18 2 11 7 2 2
OFFSET 4 2 2 2 1 2 2
OFFSET 5 2 2 2 1 1 1
Figure 239 — Split Matrix setup screen - 24 split mode

No Early Release
No Early Release provides non-gap operation for selected phases by applying a
constant Hold. When no Early Release is activated for a phase it cannot gap out. If
served, the phase will remain in service until the Force Off occurs, regardless of traffic
demand.
No Early Release VALUE(YES/NO)

Cycle 1 4 Splits/Cycle: Y
1 1 1 1 1 1 1
Split 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
1 X X
2
3
4
Figure 240 — No Early Release setup screen
No Early Release can be selected by phase on a per split plan basis. To program no
early release on a per split or split/cycle basis, move the cursor to a split plan and
select the phases for no early release by pressing the associated phase number or by
moving to that phase and pressing the Y/N key.
The value of the 4 Splits/Cycle option can be changed from this screen and new split
screens can be selected as in other similar screens as previously described.
Typical use:
This feature is typically used when an early start of the phases that follow is
detrimental. For example, say that in a 8 phase quad, 2 and 6 are the coord phases
and for specific reasons it is very undesirable for phases 4 and 8 to start early. Single
permissives could be used to prevent 4 and 8 from starting in place of 3 and 7 if they
are skipped, but 3 and 7 could be served then gap-out early. No early release on 3
and 7 as shown above would prevent this.
Alternate Use:
No Early Release can also be applied to the coord phases to prevent multiple
terminations in the same cycle if perms are relatively long and the coord phases
return early and subsequent demands arrive. By applying a constant Hold to the
coord phases, upon early return, it must remain until it is forced off in the next cycle.

C/S to Timing Plan

This option allows selection of timing plans based on the current cycle, offset, and
split patterns.
If 4 Splits/Cycle is activated, then a timing plan is assigned to each split from 1
to 24.
If 4 Splits/Cycle is programmed ‘Y’ then a timing plan is assigned to each
Cycle/Split from 1 to 4.
The selected timing plan will be used when in coordination (not free) and the
corresponding Cycle-Split is in effect, regardless of the timing plan currently in effect.
The 4 Splits/Cycle option can be changed from this screen without having to return to
the Operating Modes screen by entering a ‘Y’ or a ‘N’ for the 4 Splits/Cycle menu
option. The data entry format will change automatically for this screen as well as for
all other screens relative to 4 Splits/Cycle.
4 Splits per cycle mode....
Cycle/Split To Time Plan VALUE(0-4)
4 Splits/Cycle: Y
Cycle 1 2 3 4 5 6
Split 1 1 1 3 2 4 0
Split 2 0 0 0 0 0 0
Split 3 0 0 0 0 0 0
Split 4 0 0 0 0 0 0
pgdn for COS To Lead/Lag
Figure 241 — Cycle/split to timing plan screen
24 splits mode......
Split To Time Plan VALUE(0-4)
Splits 4 Splits/Cycle: N
1 2 3 4 5 6 7 8 9 10 11 12
1 1 3 2 4 0 0 0 0 0 0 0
13 14 15 16 17 18 19 20 21 22 23 24
0 0 0 0 0 0 0 0 0 0 0 0
pgdn for COS To Lead/Lag
Figure 242 — Cycle/split to timing plan screen - 24 split mode

COS to LEAD/LAG
This option allows assignment of any of the 8 lead/lag patterns to a specific cycle-
offset-split. The lead lag patterns must first be assigned in the controller programming
area under controller options (MM-3-1-8-6). The mode and phases to be reversed are
specified there. The mode needs to be 0 or 1 to be enacted by C/O/S.
Cycle/Offset/Split To Lead/Lag
Don't Care C/O/S = 7/6/25, L/L Patt= 0-8
# C/O/ S L/L Patt # C/O/ S L/L Patt
1 1/3/2 1 6 / /
2 2/6/25 2 7 / /
3 / / / 8 / /
4 / / / 9 / /
5 / / / 10 / /
Figure 243 — COS to lead/lag screen
There are up to 10 C/O/S TO LEAD/LAG entries. Use only as many as are required
and leave the remaining blank.
For each combination needed, specify the C/O/S and associated lead lag pattern to
be activated. When the C/O/S in effect matches one of the programmed C/O/S TO
LEAD/LAG C/O/S patterns, the specified lead/lag pattern will be activated.
Cycle, offset and split “Don’t Care” values can be used to allow all instead of a
specific value. A cycle value of 7 indicates all cycles, 6=all offsets, and 25=all splits.
The above programming will invoke lead/lag pattern #1 when cycle 1, offset 3, and split
2 are active. The “Don’t Cares” on line 2 will invoke lead/lag pattern #2 all other times.
Offset to Free
The 3000 Controller has the capability of forcing its operation in the coordinator to
free when any of the three below listed limits are exceeded:
0 = Disabled
# Sync Pulses : 0 (1-255 Cycles Without

Pulses to Free)
No Offset Line : 0 (1-255 Secs Without
Active Line to Free)
Multi Offsets : 0 (1-255 Secs Multiple
Offsets to Free)
Figure 244 — Offset to free setup screen
# Sync Pulses—This entry defines the number of cycles the controller will run
without receiving a sync pulse before it reverts to Free operation.
No Offset Line—This entry defines the number of seconds the controller will wait for
the receipt of an Offset Line input from T/F BIU #4, before it reverts to Free operation.
Multi Offsets—This entry defines the number of seconds the controller will tolerate
Multiple Offset inputs received from T/F BIU #4, before it reverts to Free operation.

Using the Check Coordination Plan Feature
USING THE CHECK COORDINATION PLAN FEATURE

The 3000 Controller automatically tests the validity of the selected coordination plan
when it is in the coordinated mode of operation. If a problem is detected, the
controller will operate in the free mode and a ‘BAD COORD PLAN’ message will be
displayed in the coordination dynamic screen. The check coordination plan screen
allows the user to test a coord plan in advance to make sure it is legitimate. This
feature can also be used to find out why a faulty coord plan has failed.
To check coord plan, load value & ENTER
->: (0=Current, 101-624 = C1S1-C6S24)
...Results Of Check Displayed Here......

Options: Include Pedestrian Times: Y
CNA Used On Coord Phases: N
Check Timing Plan 1-4 Or 5=All : 1
Load Perms & Force Offs W/ Check : N
To execute, enter XYZ for a specific

CS to be tested (e.g. 101 = C1S1).
Or,
Enter ‘0’ for current plan in effect
Enter ‘725’ for all cycles & splits
Figure 245 — Checking the coordination plan
Setting Up a Check Coordination Plan

After timing and coordination plans have been programmed, they may be checked
after first determining the following set-up parameters;
Include Pedestrian Times—This parameter controls whether or not the walk and
pedestrian clearance times will be considered when testing the coordination plan. If
an Actuated Mode Ped is greater than the phase allocation, this question must be
answered “N” and Ped Override Mode (Circuit 97) must be turned on. Ped Times on a
CNA Mode phase must be less than the phase allocation time.
CNA Used On Coord Phases—Enter a ‘Y’ only if the coord phases are to operate in
the CNA mode.
Timing Plan 1-4—This selects the timing plan to be used for the test. Enter a value of
1 through 4 for timing plans 1-4, or a value of 5 to examine all 4 timing plans.
Load Perms & Force Offs W/Check—This feature will convert the phase allocation
values to equivalent manual permissive and force off values and load them into the
respective manual entry fields (see “Manual/Auto Mode of Force Offs and
Permissives” on page 254). This may be useful for those that prefer the manual
technique of adjusting force offs and permissives in the field, but would like to initially
set them up by allocation.

To do this:
1. Set up all desired cycle lengths & basic coord options
2. Enter phase allocations
3. Set “Load Perms & Force Offs W/Check” to Y
4. Load 725 in check plan field
5. Execute check coord plan (Enter)
6. Once check is complete and satisfactory Set “Load Perms & Force Offs
W/Check” back to N*
7. Enable Manual Mode of Force offs and Permissives (disable Auto) on the
Enhanced Coord Options menu. This will cause the unit to operate on manual
values instead of directly from allocation values.
Note If the intent is to initially (once) load the manual force off and permissives areas
and then field adjust them after that, then it is important to set “Load Perms &
Force Offs W/Check” back to N. Otherwise, the field adjusted values will be written
over if coord check is ever executed again.

Using the Check Coordination Plan Feature
Executing the Check Coordination Plan

To execute the check coord plan once it has been set up, specify the cycle and split
to be tested. Enter data to the right of the colon after the arrow. Specify “0” for the
current plan in effect or a cycle and split in the in the form XYY, where X is the cycle
number to be tested and YY is the split number to be tested (e.g. 101 = C1S1). A
cycle value of 7 will select all 6 cycles and a split value of 25 will select all splits.
The 3000 Controller checks for 8 possible errors:
1. YIELD PERM selected but YIELD % equal to 0 or greater than 10
2. Cycle Time = 0
3. Coord Phases NOT compatible
4. No Coord Phase in ring
5. Ring allocation GREATER THAN 100%
6. Ring allocation NOT EQUAL to 100%
7. Minimum phase time GREATER THAN or EQUAL TO phase allocation
8. Co-phase/Ring allocations NOT EQUAL
Error #1 occurs when the operator selects YIELD Permissive operation but has entered ‘0’ or a
value greater than 10% for the Yield Percentage.
Error #2 occurs if the selected cycle has a length of ZERO.
Error #3 occurs when the user selects incompatible coord phases. (i.e. phases 2 and 8, rather
than 2 and 6 in a typical 8-phase quad).
Error #4 occurs when only one coord phase has been selected. The user must select a coord
phase from each ring, provided there is a phase to select. For example, if the sequence is
12 + 34/78, either Phase 1 or 2 can be the only coord phase, because there is no eligible phase
in Ring 2.
Error #5 occurs when the user has allocated more than 100% of the cycle time for a particular
ring. For example, in a standard 8 phase quad, ring 1 = phases 1, 2, 3, 4; ring 2 = phases 5,
6, 7, 8. If the phase allocations for phases 1 through 4 are programmed 20%, 40%, 20% and
30%, respectively, then the total for ring 1 would be 110%.
Error #6 occurs when the user allocates less than 100% of the cycle time for a particular ring (at
least one ring must total 100%), and all co-phases across the ring must contain phases.
Error #7 occurs when the minimum time assigned to a phase is greater than or equal to the
maximum phase allocation. For example, if phase 4 has the following parameters:
Initial (Min) GRN = 5 seconds
YEL = 4 seconds
Red Clearance = 1 seconds
Total = 10 seconds
If the total phase 4 allocation (split) is 10 secondsor less, then the 3000 Controller would flag
this as a Bad Coord Plan.
Error #8 occurs when co-phase sets do not have equal phase allocations. A typical 8-phase
quad intersection can be represented as follows:
1 2 | 3 4 Co-phase set 1 = 1-2/5-6
5 6 | 7 8 Co-phase set 2 = 3-4/7-8
If the phase allocations (splits) for phases 1+2 are NOT EQUAL to phases 5+6 or phases 3+4
are NOT EQUAL to phases 7+8 then the 3000 Controller will flag a Bad Coord Plan.

Note Version 1.15 of the 3000 Series firmware allows unequal Co-Phase Allocations if a
phase is in more than one Co-phase Set.
For example, to lag Phase 3 and disallow Phases 3 & 7 concurrently, without using
Lead/Lag:
1 2 | 4 I_3_ Co-phase set 1 = 1-2/5-6;

5 6 | 7 8I 8 Co-phase set 2 = 4/7-8;
Co-phase set 3 = 3/8
In this example, Phases 7 and 8 do not have to equal Phase 4, nor does Phase 3
have to equal Phase 8, but each Ring must sum to the Cycle length.

Basic Coordination - An Example
BASIC COORDINATION - AN EXAMPLE

This section provides a concrete example of coordination programming.
Overview of This Example

The following example is based on values obtained by executing the Coordination
Default Data Load from the Utilities Menu for an 8 Phase Dual Ring. The example
discusses operation directly based on those values as well as alternative operation by
making changes to certain values. The example is intended as guide for users to
follow to set their own basic coordination. Many applications can be satisfied by
simply loading the appropriate default then following this example and making
changes as necessary.
Only the basic required menus will be discussed, others are either not needed for
basic operation or are left to default values. Thus, this example also serves as a
guide as to which screens really need to be visited in order to accomplish basic
coordination. Your application may, of course, require more sophisticated use of
features which can be determined from detailed explanations given previously.
Note Only screens that are likely to have changes made are shown. All others remain
as set with default values.
Defining the Selection Source

The defaults are set up for TOD operation (0’s) and will remain so for these
examples.
Coordination Selection Source
(0= TOD, 1= CL, 2= INT)

Cycle Source: 0 Free Source: 0
Split Source: 0 Flash Source: 0
Offset Source: 0 Inter TOD Revert: 0
(0-255 SEC)
Figure 246 — Setting the selection source

Basic Operating Modes

Change this to ‘N’ if it is desired to start Main St.
green at cycle 0 (i.e. the offset reference point).
Coordination Basic Options

Change this to ‘N’
to load allocations
Reference to end (vs. beg) of Main St.: Y
in seconds. (Also
Use % (vs. secs) for Phase Allocation: Y see notes below.)
Use % (vs. secs) for Offset Entry: N
Use fixed (vs. floating) Force Offs: Y
Permissive Type: 2
(Perm type: 0=Yield, 1=Single,2=Mult.)
Permissive Type is set to “multiple.”

This opens up permissives for all other phases at end of
coord ph green. See brief perm definitions below.
Fixed Force offs are fixed to the cycle. If a side (non-coord) phase starts
early it can get more green if it doesn’t max out. Change this to ‘N’ if
“floating” force offs are desired. Floating force offs mean the allocation
times are like max times & start with green. Side phases can’t time more
than their allocation. All unused green time goes back to coord phases.
Figure 247 — Basic operating modes

When the allocation entries are in % as shown above, then the phase allocations
must be in % and must add up to 100% for each ring.
When the allocation entries are in seconds, then the phase allocations must be in
seconds and must add up to the cycle length for each ring.
Brief Permissive Type Definitions

(Detailed discussions of this were included in the previous chapter.)
Yield—One short permissive to all phases, starting at end of coord phase green.
Must specify yield percent (0-10%).
Single—Permissives start at the end of coord phase green in sequential fashion and
each has only one phase or compatible phase pair associated with it. The first
permissive is open only to phases that immediately follow the coord phases (say 3 &
7 in a standard 8 ph quad). The second is to the next set (say 4 & 8), etc. The
permissives end based on when their associated phase force off occurs, less
allowances for initial and clearances. Single permissives tend to provide occasional
extra green time at end of the coord phase when there is no call on the first set (3 &
7) because the second set (4 & 8) can’t start until later when their permissive does.
Multiple—Permissives all start together at the end of coord phase green. Any phase
with demand can start at this point. The permissives end based on when their
associated phase force off occurs, less allowances for initial and clearances. Multiple

Basic Coordination - An Example
permissive are useful when there is no great need to try to provide extra green time at
the end of the coord phase when the next set of phases (say 3 & 7) have no demand.
Instead it is more beneficial to get to the next set (say 4 & 8) as soon as possible.
Set these to the desired offset values.
Cycle and Offset Times
Cycle # 1 2 3 4 5 6
Length 90 100 110 120 0 0
Offset 1 s 0 0 0 0 0 0
Offset 2 s 0 0 0 0 0 0
Offset 3 s 0 0 0 0 0 0
Offset 4 s 0 0 0 0 0 0
Offset 5 s 0 0 0 0 0 0
Min Length 30 30 30 30 0 0
s = values in seconds
Min Length is shortest cycle allowed % = values in percent
due to short route offset seeking.
Max Dwell will appear here if Dwell

offset seeking used.
Figure 248 — Setting cycle and offset times
CNA Usage
The 3000 will automatically adjust for CNA coord phases, assuming the phase
allocations are sufficient for walk and ped clear. The NO PCL OFST ADJ setting in
the enhanced options menu does deal with CNA. If set to ‘N’, it adjusts the offset for
CNA coord phases only to adjust for ped clear time when the reference is set to the
end of MSG. WRM and Ped Recycle both also deal with CNA.
The main effort in CNA usage is implementing it. This is a two step process:
1. Select the CNA phases in the Controller Phase Recalls menu and then,
2. Activate the CNA mode. CNA phases can be activated by assigning CKT 73
(or 74-76) in the Coordination, COS/F to TOD CKTS menu, or by a clock event
in the Time of Day menu.
In the first case CNA is activated by a specific COS or any time coord is active
(COS/F = 7/6/25/1). In the second case CNA is activated strictly by time of day.

Change these to the appropriate coord phase(s)

for your application, as necessary.

Cycle 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
1 X X
2 X X
3 X X
4 X X
5
6
Figure 249 — CNA usage example
CNA Application Note 1: If CNA is applied to the coord phases, either Walk Rest
Modifier or Ped Recycle must be activated, otherwise the permissive period operation
will not operate as expected due to the nature of the end permissive logic when a
CNA coord phase leaves walk.
CNA Application Note 2: If CNA is used with a sequence where the coord phases
are the “barrier phases” and the field-adjusted coord phase Ped Clearance times are
unequal, the full progression is not guaranteed on the lesser-timed coord ped
(assuming two rings) if calls only exist in the coord phase Co-Phase Set. Therefore it
is wise to use actuated coord phases when this condition exists.
Phase Allocations
These are the direct Default Data Load values that are in percent as is the allocation
mode setting in the Basic Options screen.
Because phase allocations are in percent, total
values for each ring must add up to 100%.
Cycle 1 = 90 Totals: R1: 100 R2: 100

Phase Allocations in % R3: 000 R4: 000
Note: Only load
Phase 1 2 3 4 5 6 7 8
values for phases
Split 1 19 40 19 22 19 40 19 22 enabled (used).
Split 2 20 30 20 30 20 30 20 30 Unused phases
Split 3 21 30 24 25 21 30 24 25 are left 0. This
Split 4 22 30 25 23 22 30 25 23 example uses 8
SHIFT-RT.-> TO VIEW OR ENTER PHASES 9-16 phases.
Figure 250 — Phase allocations as percentages
Seconds Mode—The Default Data Load values are changed to the equivalent values
in seconds after changing Use % (Vs Secs) For Phase Allocation to ‘N’ in the Basic
Options screen.

Because allocations are in seconds, each ring must
add up to the cycle length (90 sec. in this case).
Cycle 1 = 90 Totals: R1: 90 R2: 90

Phase Allocations in sec:R3: 000 R4: 000
Phase 1 2 3 4 5 6 7 8 Totals show the
Split 1 17 36 17 20 17 36 17 20 values for the Split
Split 2 18 27 18 27 18 27 18 27 row where the cursor
is currently located.
Split 3 19 27 21 23 19 27 21 23
Split 4 20 27 22 21 20 27 22 21
Figure 251 — Phase allocations in seconds
Times are based on using the version 1 allocations as a percent of 90 seconds and
rounding appropriately.
Note Whether in percent or seconds, the allocation time includes the entire phase
time, including yellow & red clearances.
Also note that the default mode for Auto Perm and FO mode is Y = ON. When in the
auto mode, force offs and permissives are computed automatically and there is no
need to program them. This option can be found in the Enhanced Options Menu. If
Auto Perm and FO mode is set to N, then all permissive periods must be manually
entered (also see Coord Check page 265).
General note about defaults. This example is based on the back up plan default which
sets many of the coord options to their default values. It should be understood that,
unless you are going to actually program them all, it is important to get all options to
their default state. One way to do this is to load one of the Utilities Menu default plans
as in this example.
Another way is to use the clear and default codes from the Coordination Menu. The
order to do this is, before programming;
1. Execute Clear All Coord Parameter Values. This sets all cycles, offsets,
allocations to zero.*
2. Execute Set All Coord Options To Defaults. This will set the options in the
basic default mode.
*
Obviously, do not Clear All if there are pre-existing values to be saved.


Chapter 8 — Time of Day Functions
This section explains Time of Day (TOD) programming of the 3000 Series of controllers. TOD
is an alternative to coordinated programming. The following topics are discussed in detail in
this chapter:
An overview of TOD operation, on page 276.

Data entry modes for TOD data, on page 277.
Using day plans, on page 278.
Typical example of a day plan, on page 280.
Configuring circuit plans, on page 282.
Configuring week plans, on page 283.
Configuring a yearly plan, on page 284.
Defining exception days, on page 285.
Using circuit overrides, on page 286.
Daylight savings time, on page 287.
Working with synchronization references, on page 288.
Setting the controller’s date and time, on page 290.

OVERVIEW
Time of day (TOD) functions provide for scheduling a variety of events to occur at
fixed times during the day. These events include changing patterns (cycle, offset and
split), enabling or disabling controller functions such as dimming or volume density,
and activating user defined outputs.
A TOD program is composed of a hierarchy of plans from the year plan at the top to
the day plan at the bottom. A year plan consists of 53 week plans, a week plan
consists of 7 day plans, and a day plan consists of a set of change points which
activate or deactivate individual functions at specific times of the day. In addition,
there are up to 50 exception day plans for special ‘one time only’ days such as
holidays or special events.
The TOD menu is shown below, denoting the various programming options.
Time Of Day Menu
1.Day Plans 1-32 6.Circuit Overrides

2.Circuit Plans 1-50 7.Daylight Savings
3.Week Plans 1-20 8.Sync Reference
4.Year Plan,53 Week 9.Set Date And Time
5.Except Days 1-50
Figure 252 — Time of Day Menu
Note The available TOD circuits in the 3000/E controllers is listed in Table 58, on
page 430.

TOD Data Entry Modes
TOD DATA ENTRY MODES

There are two modes of data entry for programming TOD events. These are called
INSERT and EDIT, where EDIT is the default mode. To toggle modes, press the
SHIFT key and the mode indication in the upper left corner of the screen will change to
reflect the current data entry mode. The primary difference between the two modes is
that in EDIT mode, if a change point is modified, the original data in the change point
is replaced by the new data. In INSERT mode, modifying an event stores a new
event.
Insert Mode
The INSERT mode is useful for initially entering change point (event) data. The insert
mode basically allows entering over the top of previously entered CIRCUIT PLAN,
COS, or CKT-ON/OFF fields to create new change points (events) when the times
are the same. For example, when initially programming a day plan, say it is desired to
activate circuit plan 1 at 7:00 am and begin running C/O/S pattern 3/2/3 at the same
time. SHIFT is first pressed to enter insert mode, then the circuit plan is entered at
7:00 AM normally including the time. Now instead of re-entering the time again, the
cursor is simply moved to the C/O/S column on the same line and the pattern is
entered. After pressing ENTER, a new change point (event) line is created while the
original one remains intact.
Edit Mode
The EDIT mode is best used to change events that have previously been
programmed. Typing over the top of any field changes that change point (event) field
and no new event is created.

DAY PLANS (EVENT PROGRAMMING)

Option 1 on the Time of Day Menu takes you to the Day Plan configuration screen.
The first page allows an operator to select one of 32 day plans and to specify what
action is to be taken. A day plan can be accessed for editing, or one or all day plans
can be deleted.
To View or Enter Day Plan Change Points

Enter 1-32: _
To Erase One Day Plan

Enter 1-32:
To Erase All Day Plan Change Points

Enter 99:
Figure 253 — Day Plan selection screen
The minimum requirements for successful TOD control of events: the 3000 Controller
requires a Year Plan with at least one Week Plan, and a Day Plan with some TOD
events. Week Plan 1 all year with Day Plan 1 assigned all week are the defaults if
nothing else is programmed. Refer to the explanations that follow for details.
Erasing A Day Plan

This option will clear all events in the Day Plan. Move the cursor down to the second
row and enter the plan number to clear, followed by the ENTER key. A prompt will
ask for the Y/N key to confirm the operation, or the MENU key to cancel it.
To Erase All Of The Day Plans

Move the cursor to the last row and enter 99. A prompt will ask to confirm or cancel
the operation as above.
Editing a Day Plan

To edit a Day Plan, enter the plan number at the top of the Day Plan screen and
press the ENTER key.
If Day Plan 1 is selected, the following screen will appear.
Day Plan 1 Hour: 0 HH=99 To Erase Event
Edit (1-50) (6/5/4) (1-255)
HH:MM Circuit-Plan C/O/S CKT-ON/OFF
**:** / /
**:** / /
**:** / /
**:** / /
Use (YES/NO) to Toggle ON/OFF
Figure 254 — Editing a day plan

Day Plans (event programming)
This screen is where the actual events that make up a Day Plan are defined. In this
case, the screen is shown as it appears before any change points are programmed
(no events). On the left side of the screen are the times at which a TOD event will
occur.
Deleting Events
To erase (delete) a TOD change point (event), move the cursor to the HH field for the
event, enter a value of 99, and press ENTER.
Event Times
Event times determine the hour and minute that the event will be activated. To enter a
time, move the cursor to the change point to be edited, enter the hour, move the
cursor to the right, then enter the minute. Note that the event times are programmed
on a 24 hour clock basis where 08:00 = 8 AM and 20:00 = 8 PM.
Types Of Events
There are three types of events that may be programmed, each with their own field.
These are Circuit Plans, C/O/S coordination patterns, and individual Circuits. One
(and only one) of these event types can be programmed on each change point line,
however, there may be multiple change points at the same time of day. The available
TOD circuits in the 3000/E controllers is listed in Table 58, on page 430.
Circuit Plan Events

Circuit plans are user defined groups (1-50) of up to 4 circuits each that are to be
activated or de-activated together, instead of individually activating them as in the
case of the CKT-ON/OFF field. Circuit Plans are activated in this menu (Day Plans)
but the circuits are assigned to plans under the CIRCUIT PLAN menu. To activate a
previously assigned circuit plan, move the cursor to the column labeled CIRCUIT
PLAN and enter the number of the plan that is to be activated. As the plan number is
entered, a description of the plan appears on the bottom row of the display. If this is
the correct plan number, pressing the ENTER key will load the data into memory.
C/O/S Pattern Events

A cycle, offset and split combination defines the coordination pattern to be activated
at the event time. To program a pattern, move the cursor to the column labeled
C/O/S. Enter the desired cycle, offset and split into the appropriate spaces and load
the data by pressing the ENTER key.
Circuit ON/OFF Events

A circuit is a function that can be activated (or deactivated) by TOD. In some cases a
circuit can be a physical output from the machine. Most circuits, however, are “virtual”
circuits in the sense that they activate an internal function but produce no physical
output. For a list of available circuits, refer to Appendix A. Pressing the HELP key will
also display a list of the TOD circuits.

To program a circuit, move the cursor to the column labeled CKT and enter the circuit
number. As the number is entered, the abbreviation for that circuit is printed above
within the parenthesis. After the circuit is selected, move the cursor one column to the
right to define the state of the circuit (ON or OFF). Pressing the Y/N key will toggle the
state between ON and OFF. At this point, ENTER will load the data into memory and
the circuit abbreviation replaces the circuit number. Note that the FREE circuit (11) is
activated by default at midnight. To run in coordinated mode by TOD, this circuit must
first be turned off by a change point on or before the first coordination plan change
point.
Event Screen Selection Shortcut

At the top of the screen, there is an entry field labeled HOUR. This allows a shortcut
method of accessing a change point that may be several pages down. For example,
suppose it is desired to modify a change point at 10:00 PM, and this change point
happens to be 3 or 4 pages down. The PGDN key could be pressed until the change
point appears, but a quicker method would be to enter 22 (for 10PM) in the HOUR
field and the correct page will be displayed immediately.
Automatic Circuit Reset At Midnight

A very important property of TOD programming is the fact that the scheduler
automatically resets (de-activates) all active circuits at midnight every day. The
exception to this is the FREE circuit (number 11) which re-activates at midnight. If it is
desired for a circuit to remain active through the midnight transition, it must be
reactivated at time 00:00. Conversely, the Free ckt (11) must be de-activated at time
00:00 if coordination is to remain in effect through midnight.
TYPICAL DAY PLAN EXAMPLE

A set of screens as they might appear for a typical Day Plan are shown here:
Day Plan 1 Hour: 6 HH=99 to Erase Event
EDIT (1-50) (6/5/4) (1-255)
HH:MM Circuit-Plan C/O/S CKT-ON/OFF The SHIFT key toggles
06:30 1/1/1 between EDIT and
06:30 / / FRE OFF INSERT modes.
06:30 / / M21 ON
06:30 / / M22 ON
Figure 255 — Typical day plan example - screen 1

Typical Day Plan Example
P G D N to see this screen:

Day Plan 1 Hour: 6 HH=99 To Erase Event
EDIT (1-50) (6/5/4) (1-255)
20:00 1/1/1
23:00 / / FRE ON
23:00 / / M21 OFF
23:00 / / M22 OFF
P G D N to see this screen:
Day Plan 1 Hour: 6 HH=99 to Erase Event
EDIT (1-50) (6/5/4) (1-255)
07:00 3/1/1
09:00 2/1/1
15:30 3/2/2
18:00 2/1/1
The FREE circuit (ckt 11) must be turned OFF to activate coordination. This is
equivalent to Coord = ON. The M21 and M22 circuits (ckt’s 93, 94) call for Max II
timing, rings 1 & 2. It is a common practice to call for Max II timing during coordinated
operation, because Max II times are typically longer. Their phases don’t tend to max
out before forcing off.
However, there are several other ways to accomplish this same operation. One way
would to be to use a circuit plan for all three circuits (see sample screen under Circuit
Plans). Another would be to use only the Free circuit in the day event screen, and
assign the Max ckts (ckt’s 93 & 94) in the coordination COS/F to TOD CKT’s
assignments. These would operate whenever the unit is in coordination (set
C/O/S/FRE = 7/6/25/1).
One consideration is the fact that C/O/S to TOD CKTs are not invoked until
coordination is actually running, while clock circuits may slightly precede the actual
start of coordination. If it is not disruptive to do so (like Inh. Max), however, clock
events do consolidate circuit programming in one area. In this way, the clock events
show everything that is occurring without having to refer to other menus.

CONFIGURING CIRCUIT PLANS

There are 50 circuit plans available in the 3000 controller for activation by day plan
event. Each plan may contain up to 4 circuits to be activated or deactivated in any
combination at once.
Circuit Plans 1-50 VALUE:Ckts 0-255

0= No Ckt, use (Yes/No) to Toggle ON/OFF
Plan Ckt-on? Ckt-on? Ckt-on? Ckt-on?
1 FRE OFF M21 ON M22 ON
2 FRE ON M21 OFF M22 OFF
3
4
5
Figure 258 — Configuring circuit plans
The PGUP and PGDN keys move through the list of available circuit plans by page, but
a faster method is to simply move the cursor to the column labeled PLAN and enter
the desired plan number. Pressing the ENTER key will display the page containing the
plan.
Programming a Circuit Plan

1. To program a plan, move the cursor to any column labeled CKT across from
the plan that is to be modified.
2. Enter the plan number (a list of circuits can be found in Appendix A or by
pressing HELP) and move the cursor to the right.
3. Now use the Y/N key to set the state of the circuit to either ON or OFF.
4. If more circuits are to be included, simply move the cursor right or left to an
empty column and repeat the procedure until all the desired circuits have been
defined.
It is not necessary to program all four circuits in each plan.
Circuit plans are typically used in pairs, where there is one plan which sets circuits to
one state and another plan which sets them to the other. For example, the sample
screen above has been set up to provide the same operation as the typical day
program example on the previous page. In this case, circuit plan 1 would be invoked
at 6:30 in the morning and plan 2 at 23:00 at night.

Configuring Week Plans
CONFIGURING WEEK PLANS

The Week Plan data screen is accessed by pressing 3 from the TIME OF DAY menu.
Week Plans 1-20 VALUE:Day Plans 0-32

(0 & 1 = DP 1)
Plan SUN MON TUE WED THU FRI SAT
1 2 1 1 1 1 1 2
2 3 1 1 1 1 1 2
3 4 1 1 1 1 2 3
4 1 14 14 14 14 14 1
5
Figure 259 — Week Plans editing screen
There are 20 week plans available in the controller; each plan consists of 7 day plans,
one for each day of the week. To program a week plan, move the cursor to the plan
and enter a day plan for each day of the week, SUN through SAT. Note that if a day
plan is blank, day plan 1 will be used as a default. Entering a value of 0 will clear a
day plan.
The PGUP and PGDN keys will display plans above and below the currently displayed
plan. Week plans may also be accessed directly by entering the plan number in the
top location underneath the PLAN heading.
Note At least one week plan must be assigned for TOD control to operate. A zero
(blank) is considered day plan 1.

CONFIGURING A YEAR PLAN

A year plan is a set of 53 week plans over the course of an entire year. There are 53
because usually there is a partial week at the beginning and end of the year. This
screen is accessed by entering a 4 in the TIME OF DAY menu.
Year Plan VALUE:Week Plans 1-20
Week Of Year
1: 1 2: 1 3: 1 4: 1 5: 1
6: 1 7: 1 8: 1 9: 1 10: 1
11: 1 12: 1 13: 1 14: 1 15: 1
16: 1 17: 1 18: 1 19: 1 20: 1
21: 1 22: 1 23: 1 24: 1 25: 1
26: 1 27: 1 28: 1 29: 1 30: 1
Figure 260 — Year Plan Editing screen
To enter a week plan, move the cursor to the week to be edited, and enter the
number of the week plan (1 through 20). Pressing the ENTER key or a cursor key
loads the data. The first 30 week plans are on the first page. To access week plans
31 - 53, press the PGDN key.
Note Although blanks in the year program are interpreted as “week 1”, it is a good idea
to assign all 53 weeks to a week program. This will avoid confusion even if the
year plan consists of week program 1 all 53 weeks.
The repetitive data entry procedure as described on page 16 is very useful for loading
the year program.

Defining Exception Days
DEFINING EXCEPTION DAYS

To enter the exception day programming screen, enter a 5 at the TIME OF DAY
menu.
Exception Days 1-50 WOM=5 is Last Wk
EXC (0-12) (0-31,0-7) (0-5) (0-32)
Day Month DOM-DOW WOM Day Plan
1 1 1 2
2 5 2 5 2
3 7 4 2
4
5
Figure 261 — Exception Day configuration screen
There are 2 types of exception days as follows,
Date specific exceptions days are intended for holidays or events that occur
on the same date every year. Examples are Christmas, New Year’s day, or U.S.
Independence day. Exception day 1 in the screen above is New Year’s day
which obviously occurs on January 1st every year.
Day of week, week of month, month of year exception days are for holidays
that occur on a specific day of a specific week of a specific month (many of
these are the so-called “Monday” Holidays). Examples are U.S. Memorial Day
which is the last Monday in May, or Canadian Thanksgiving which is the first
Monday in October. Exception day 2 above is for U.S. Memorial Day, which is
the last Monday of May. A value of 5 in the week-of-month field (WOM)
denotes the last week of the month.
No value appears in the WOM column, the value in the DOM-DOW column is
assumed to be a day-of-month (1-31) and the exception day is date specific. If there
is a value in the WOM field, the DOM-DOW value is taken to be a day-of-week (1-7,
where Sunday = 1, etc.).
Entering a ‘0’ in any particular field clears the previous entry.
There are 50 exception days available. PGUP and PGDN will display plans above or
below the current one. Also, by moving the cursor to the field directly below the
EXC DAY heading, the user can enter a number and display the page containing that
exception day plan.

CIRCUIT OVERRIDES
Any circuit that can be activated by TOD can also be manually turned on or off. This
screen is accessed by entering a 6 from the TIME OF DAY menu.
Circuit Override (Y/N) Æ On/Off/TOD

Circuit 1 2 3 4 5 6 7 8
Function CY2 CY3 CY4 SL2 SL3 OF1 OF2 OF3
State TOD TOD TOD TOD TOD TOD TOD TOD
Circuit 9 10 11 12 13 14 15 16
Function OF4 OF5 FRE RFL TP1 TP2 TP3 TP4
State TOD TOD ON OFF TOD TOD TOD TOD
Figure 262 — Circuit Override setup screen
To override a circuit, move the cursor to the appropriate circuit and use the Y/N key
to rotate the state of the circuit from TOD to ON to OFF and back to TOD.
TOD = Default state. The circuit automatically turns ON and OFF per the TOD
program.
ON = The circuit is manually forced to ON (TOD commands are ignored).
OFF = The circuit is manually forced to OFF (TOD commands are ignored).
The circuit will remain in a manual state until changed by the user.
More circuits can be viewed by using the PGUP and PGDN keys to scroll up and down
through the list. Go directly to the page containing a given circuit by entering the
circuit number in the first field in any screen. The cursor can be moved to this field by
pressing the SHIFT and HOME keys simultaneously.
A list of available circuits and their functions can be viewed by pressing the HELP key
and paging up and down. Pressing HELP again will return to the programming screen.
This list can also be found in Appendix A of this manual.

Daylight Savings Time
DAYLIGHT SAVINGS TIME

When programmed to do so, the 3000 Controller automatically adjusts its internal
clock for daylight savings time. The programming screen for this function is found
under option 7 of the TIME OF DAY menu.
Daylight Savings WOM=5 is Last Wk The default for

daylight savings is
Spring Fall OFF (blanks=off),
(0-12) (0-5) (0-12) (0-5) so it must be
Month WOM Month WOM programmed if DST
4 1 10 5 is used in your
area.
WOM= Week Of Month
Figure 263 — Daylight Savings Time setup screen
Daylight savings is programmed for Spring and Fall by month and week of month (5 =
last week of month). The 3000 assumes Sunday morning at 2:00 AM of the specified
week. To program the daylight savings parameters, move the cursor to the
appropriate field and enter the desired values. Press the ENTER key or a cursor key
to load the data. The sample screen above is the typical programming for daylight
savings areas (1st Sunday in April, last Sunday in October). Program ‘0’ s if daylight
savings is not used in your area.

SYNC REFERENCE
This screen performs several functions. It allows the operator to set up the reference
time for syncing to the master cycle timers, and it also allows the user to define the
time to use when the controller’s internal clock is reset, and to set Interrupter mode.
Sync Reference HH:MM

Mode: 0 Time Clk Rst: 00:00
0 = Time Dependent Interrupter Y/N: N
1 = C/O/S Event Pulses/Cycle: 0
Time Dependent Cycle References
HH:MM HH:MM HH:MM
CYC 1: 00:00 CYC 2: 00:00 CYC 3: 00:00
CYC 4: 00:00 CYC 5: 00:00 CYC 6: 00:00
Figure 264 — Sync Reference Setup screen
Sync Reference Modes

The Sync Reference determines how the coordinator’s master cycle timers are
referenced to the internal clock of this controller. The sync reference programming
screen is selected by entering 8 at the TIME OF DAY menu. This screen defines the
mode and times that sync pulses will be referenced to.
There are two modes for sync reference: time dependent and C/O/S event.
In the time dependent mode (0), a fixed time is used for the reference point for
each cycle. Each cycle may have a different reference point. Note that these
times apply only when the SYNC SOURCE mode is programmed for
TOD/CL/INTER on the 4th page of the coord operating modes (MM-3-2-1-PGDN
3 times). These times do not apply to City Zero & Absolute modes which define
their own reference times.
In C/O/S event mode (1), a pattern change generates a new reference point for
that pattern. That reference will remain in effect until another pattern change
occurs. The reference time values do not apply to this mode though they remain
displayed if programmed.
Comparing Time Dependent And C/O/S Event Modes

The time dependent mode tends to be the most widely used mode because it is not
sensitive to event history. Since each cycle has a specific reference time, and
assuming all intersections in the system use the same reference times, then any two
intersections calling for the same cycle will be in sync regardless of previous event
history. This especially comes into play when intersections are zoned and perhaps
one group goes to a different cycle for a period, then later comes back to the same
cycle with the main group.
The C/O/S event mode is event history sensitive. As a result, all intersections must
have the exact same C/O/S changes and at the exact same times. If not, depending
on cycle lengths, there may well be differences in reference points and intersections

Sync Reference
may be out of sync. This, of course, depends on the C/O/S change points and the
cycle length. One advantage the C/O/S event mode has is that it does not necessarily
have to offset seek when cycle only changes are made (as does the time dependent
mode).
Sync Reference Times

At the bottom of the screen are six fields for entering the sync reference times for
each cycle when using the time dependent sync reference mode. If not using this
mode, these times are ignored. The most widely used time is midnight (00:00) for all
cycles, which is the default. Times of 02:00 AM and 03:00 AM are also common.
External Clock Reset Time

The field In the upper right corner defines what the time clock will be set to when the
external time clock reset input is activated and then deactivated (trailing edge). Enter
the time in 24 hour format. Note that if the controller is NOT in interconnect mode, the
SPLIT2 input can be used as the Time Clock Reset Input.
Interrupter Mode
Below the clock reset time field is a field to enable interrupter pulses. If a Y is entered
in this field, the controller will superimpose extra pulses each cycle on the offset lines
in addition to the master sync pulse. Interrupter pulses are distributed over the cycle
and each is 1.5 seconds in duration. If INTERRUPTER (Y) is selected, a choice of 0-6
additional sync pulses may be added to the cycle. This feature allows regional
programmability in place of the older standard of four.
Interrupter pulses are typically used when the 3000 is used as a master to drive an
interconnect with electromechanical controllers as secondaries (slaves). Interrupter
pulses prevent a mechanical dial from excessive dwelling because the time between
interrupters establishes the max dwell time. The interrupters are asynchronous with
the master cycle timer so the slaves will not sync on an interrupter.

SETTING THE DATE AND TIME

This screen is used to set the date and time; it is accessed from option 9 from the
TIME OF DAY menu.
Set Time And Date
Time Date
HH:MM:SS MM/DD/YYYY
14:20:54 07/15/1993
Day Of Week= THURSDAY Week Of Year= 29

Figure 265 — Set Date and Time screen
To set or change the time, enter values for the hour (HH), minute (MM) and seconds
(SS) in 24 hour format. Hit ENTER or a cursor key for each value.
The time of day is critical when time based coordination is used. This time must be
exactly the same for all intersections within the system. To do so, set a watch to one
of the existing intersections, then set the time in this unit slightly ahead of the watch
and then wait before hitting ENTER after loading the seconds until the precise time.
To set or change the date, enter values for the month (MM), day of month (DD) and
year (YYYY). Hit ENTER or a cursor key for each value. When the date has been
entered, the day-of-week and week-of-year are displayed at the bottom of the screen.
There is no need to enter day-of-week or week-of-year; this information is calculated
automatically.

Chapter 9 — Preemption
This section explains the usage and configuration of Preemption in a 3000 Series controller.
The following topics are discussed in detail in this chapter:
An overview of preemption, on page 292.

Key concepts of preemption operation, on page 293.
Basic preemption run programming, on page 295.
Editing Per-run settings, on page 296.
Programming Interval data, on page 308.
Setting up preemption run flash plans, on page 323.
Using the pre-programmed runs in the Quick Setup screens, on page 324.
Examples of preemption programming, on page 332.

OVERVIEW
Preemption describes a process in which the normal operation of the controller is
suspended so that it can immediately (in most cases) cycle to a specific phase set, a
special sequence, or to the flashing state. Preemption occurs in response to special
preempt inputs and is typically used to prepare the intersection for emergency
vehicles or to clear tracks for trains.
Preemption may also be used to clear an exit ramp off a highway when it backs up.
Internal preemption executed within the controller has largely replaced older style
external logic preemption devices (e.g. ‘phase selectors’). A modern controller like the
3000E only needs a signal input to indicate that preemption is required, and will do
the rest itself.
Basic Description of Preemption Operation

When a preempt input becomes active:
1. If a preempt has previously occurred and the minimum re-service timer is still
timing (if used), the preempt input will be refused until this time period is
complete.
2. If a Delay is programmed for the preemption run, the delay must time-out
before the run will activate. (However, unlike a vehicle detection delay, the
preemption demand is recognized as soon as it appears.)
3. Once the run begins, the unit will proceed to interval #1, clearing any active
phases as necessary and acknowledging any preempt entry times as it does
so.
4. Starting with interval #1, each interval will:
time its TIME amount if it’s a fixed interval
time its TIME amount, then hold on the PE input if it’s a dwell interval
cycle between cyclic intervals, using the TIME as max times (or using
normal phase max times if TIME is set to zero (0))
generate flashing operation on phases, peds, overlaps, or PE outputs if any
of these are assigned to a flash plan
5. Intervals will activate, in order, after interval 1. Dwell or fixed intervals must be
served, unless preempt exit occurs first. Cyclic intervals are only served if
normal phase calls are present. The unit cycles between cyclic intervals until
the exit criteria is met. (Cyclic intervals are usually the last intervals of the run.)
6. If a higher priority preempt input becomes active and the current run is enabled
to Go to Higher PE, it will exit this run to go to the higher run. To make this
transition, the controller will execute any appropriate clearances.
7. Once the preempt input goes away and the preempt Duration Timer has timed
out, the unit will exit preemption as soon as it reaches an interval for which the
‘Exit’ parameter is enabled. The unit will exit according to its exit control
programming, which defines the next phases to be served and the placement
of exit calls.

Overview
Key Concepts Used in Preemption

PE — Throughout this section, the terms ‘preemption’, ‘preempt’, and ‘PE’ are used
interchangably to refer to the preemption process. This is the situation when the
normal operation of the controller is temporarily suspended by an external signal,
during which time the controller provides an alternate sequence of signals. This
alternate sequence is known as a ‘preemption run’.
Run — A preemption sequence that consists of some number of intervals and
parameters that defines the way the sequence is executed. There are six preemption
runs available in the 3000E, each activated by a separate hardware input. Each run
may consist of as many as 32 of the 72 available intervals. When a run becomes
active the intervals are executed in sequence until the criteria for exiting the
preemption run are satisfied.
Interval — An interval defines a period of time in which the machine outputs are
programmed to be in a given state. There are several types of intervals:
Fixed interval — An interval that is timed for a specified amount of time, the
controller then advances to the next interval. An example of a fixed preempt
interval is a track clearance at the beginning of a railroad type preemption.
Dwell interval — An interval in which the controller rests until the criteria for exit
are satisfied, at which time it will terminate the preemption run and return to
normal operation.
Cyclic interval — An interval that will only be executed if there is demand on the
phases served by the interval. Normally, a cyclic interval would not be used
alone, but in conjunction with several other cyclic intervals. An interval is
considered cyclic if it is programmed as neither fixed nor dwell. Cyclic intervals
derive their timing from the normal phase timing associated with the phases that
are serviced in the interval. Intervals may include definitions for flash plans,
which are sets of flashing or dark outputs. Also, an interval may define a set of
outputs (sign power, for example) that are to be activated while the interval is in
effect.
Preemption operation and service control — These are any of a number of
miscellaneous set up times and controls relative to each preempt run. These include
items like the number of intervals required, input priorities, input lock and non-lock
mode, delay before preempt, how long before the preempt can be re-serviced, etc.
Preemption entry control — This defines how the normal control will be interrupted
to go to preemption. For example, preempt minimum green determines the minimum
amount of green will be serviced on a phase before interruption by the specific
preempt run is allowed. These times can be different from the normal phase times
and apply to entry into preempt only.
Preemption Call/Input/Demand — These terms are used interchangably in this
section to describe the electrical signal that appears at the controller’s physical pin or
BIU input connector showing that a preemption signal has been received at the
controller. This source of the call/input/demand, for example, could be a train
approaching a crossing or an emergency vehicle that has triggered a preemption
sensor at an intersection. There is no difference between a preemption call, a
preemption demand, and a preemption input.

Flash plan — This is a programming set that can be associated with an interval. It
modifies the interval when one wants it to flash some or all signal outputs based on
some condition. Flash plans are not required if the preemption plan does not involve
any flashing signals.
Exit interval — A specific interval to which the controller will exit after the last
preempt interval. It is optional to use a specific exit interval, or to exit to the next
phase with demand, or to the last phase served prior to preemption.

Preemption Programming
PREEMPTION PROGRAMMING
The Preemption programming area is accessed from the Program Menu by selecting
option 4.Preemption. The full path to this screen is: MM > 3.Change Data >
4.Preemption.
To View/Prog Preempt Run Enter 1-6:
To Erase One Preempt Run Enter 1-6:
To Erase All Preempt Runs Enter 99:
To Load Default Values Enter 1-6:
Figure 266 – Preemption Options list

Viewing and Programming a Single Preemption Run
The process of viewing and editing a preemption run is described in much greater
detail starting on the next page. However to get started, just place the cursor in the
first row of this Preemption Options list and enter the number of the preemption run
(between 1 and 6) that you wish to edit. Press ENTER to proceed.
Clearing a Single Preemption Run

To clear the current values for any one of the six preemption runs, move the cursor
down to the second row and enter number of the run to be cleared. Then press the
ENTER key. A prompt will then ask to press the Y/N key to confirm the operation, or
press the MENU key to cancel it.
Clearing All Preemption Runs

Move the cursor to the third row and enter 99, and then press the ENTER button. A
prompt will then ask to confirm or cancel the operation as above.
Are You Sure You Want to Clear

All Preemption Runs?
Use (Y/N) to Execute, MENU to Cancel

Figure 267 – Erase All Preemption Runs verification screen
Loading Default Values to a Single Preemption Run
To set values and options in a run to standard defaults, move the cursor to the last
row in the Preemption Options list. Enter the number of the run you wish to revert to
defaults. A prompt will then ask to confirm or cancel the operation.

EDITING A PREEMPTION RUN

After you’ve selected a particular preemption run to view or edit on the Preemption
Options list and pressed enter, the Preemption Menu will be displayed for that run.
Preemption Run 1 Menu
1.Per Run Data

2.Interval Data
3.Flash Plan for Run 1 Intervals
4.Quick Setup Procedures
When Changing Run Data, 1st Disable Run

Figure 268 – Preemption Run 1 Menu
The first three options in this menu are considered part of the “Detailed Setup.”
Option 1, “Per Run Data” is used to program parameters that apply to the run as a
whole. The second item, “Interval Data” is used to program the timing intervals that
make up the preempt run. And the third command, “Flash Plan for Run # Intervals” is
used to establish flash plans for the run, if this option is required.
The fourth option, “Quick Setup Procedures,” provides a simpler set of programming
options that can be used if one is setting up one of two specific types of preemption
runs: ‘Basic Fire’ and ‘Railroad’. For more information about the quick setup
procedures, see page 324.
Per Run Data

Each preemption run has five screens of per-run parameters that can be accessed
using the Per Run Menu.
Per Run 1 Menu
1.Per Run Parameters

2.Per Run Times
3.Entry Parameters
4.Per Interval Parameters
5.Exit Parameters
Figure 269 – Per Run Menu for preemption run 1

Editing A Preemption Run
Per Run Parameters

This screen is displayed when a 1 is entered from the Per Run Menu. It allows the
programming of various parameters that control how the overall preemption run that
is currently being edited will operate.
Run 1 Enable, RR, Lock, Priority

VALUE(YES/NO)
Run Enable: N Override FLASH: N
Railroad: N Go To Higher PE: Y
PE Input Lock: Y NEMA Priority: Y
Early PE Out: Y Hold Only: N
Max Intervals: 6 User Priority: 1
VALUE(0-32) VALUE(1-6)
Figure 270 – Per Run Parameters, Screen 1
Paging down from this screen will display one more screen of Per Run Parameters.
(See page # for details.)
Note The Preempt Run must be disabled before editing. The 3000 unit will not allow a
preempt run to be edited while it is enabled. It must then be re-enabled after
programming to allow preempt to operate (see description below).
Run Enable
Each preempt run has an input associated with it, but for the input to activate its run,
the run also has to be enabled. Otherwise, the input will be ignored. Program a ‘Y’ to
enable this preempt run. The 3000 does not allow a preempt run to be programmed
without first disabling the run. Conversely, a run cannot be disabled while the
associated input is active.
Railroad
When enabled (Y) the preempt is considered a railroad run. This affects input
operation (debounce criteria) such that the input must remain active for 1.5 seconds
before it is recognized. It must then remain inactive for 3 seconds before it is
considered gone. When disabled (N), the run input operates the same as any other
input (NEMA). This parameter also modifies the way that the preempt re-service time
is treated, see below.
PE Input Lock
This parameter is only meaningful when a preemption delay is used. (See the
description of ‘Delay’.) If enabled with a ‘Y’, the preemption call is retained in memory
during the preemption delay, until the run is activated, even if the input is already
gone. This mode might be used for something like a fire house pushbutton where the
run is called for, but delayed for a period after the button is pushed. When lock is not
enabled (N), the input must still be present when the Delay Timer has timed out for
the run to be activated. This mode might be used with a ramp spill back detector at
the top of the ramp where a steady active input throughout the delay period is an

indication that the ramp is backed up (presence detector, input stays active when
vehicles are not moving).
Early PE Out
Early preemption output tells the controller to turn ON all Interval 1 outputs associated
with this preemption run as soon as the controller begins clearing the active phases.
When this option is set to NO, these outputs will not activate until the controller is
actually in the preemption run ‘Interval 1’ phases.
Max Intervals (VALUE 0-32)

Any given preempt run may contain up to 32 intervals, but the maximum total of all 6
runs is 72 (thus, not all runs can use all 32 intervals). The max interval parameter
defines the number of intervals that each run will have. This number can be changed
at any time, i.e., intervals can be added or deleted from existing preempt runs.
Override FLASH
When enabled (Y) the controller is allowed to exit UCF or Soft Flash to serve the
Preempt run. When disabled (N) the Controller is not allowed to exit UCF or Soft
Flash. However, if disabled when a Preempt call arrives during Flash, the controller
will remain in Flash until both the Preempt and Flash call are inactive.
Go To Higher PE
When enabled (Y), the controller is allowed to suspend an active preemption run and
immediately proceed to service another run of a higher priority. Following the
completion of the higher run, the suspended run will start over, if its preemption call is
still active.
NEMA Priority
When NEMA Priority is enabled (Y), the User Priority value (1-6) is ignored and run 1
always carries the highest priority and run 6 the lowest. This is in accordance with the
NEMA TS 2 Standard. When NEMA Priority is disabled (N), the priority of each
preempt run can be specified in User Priority field (value range 1-6, where 1 =
highest, 6 = lowest). Two or more runs may have the same priority and if so, are
serviced on a “first come, first serve” basis.
It is important to remember that this value is a global setting for the controller. Even
though NEMA Priority is displayed in each run’s Per Run Parameters screens, this
one setting applies to all runs and the same setting will always appear in the Per Run
parameter screen for all six preemption runs.
Note The order of priority defines which preempt will be served first when two or more
preemption inputs become active. Preemptions of higher priority will only override
an already active preempt run if they are allowed to do so by the lower run (see
“Go to Higher PE “under Per Run Programming). When overriding to a higher call,
the lower run is left immediately without waiting for its duration timer to time out.

Hold Only
This option places a ‘hold’ on the first interval’s phases for the duration of the run. All
other intervals in the preemption run are then ignored. If used, the preemptor does
not skip or force-off any phases.
User Priority
The importance of preemption calls is ranked by their ‘priority level’. User Priority is
only used if the default NEMA priorities are not being used (i.e. the ‘NEMA Priority’
setting on this screen is set to ‘N’.) However, if NEMA priority is off, then this user
priority setting for each run is used to determine which run should take precidence
when multiple calls are received.
Note This kind of priority-based switching between runs is only allowed if the ‘Go to
Higher PE’ setting on the run with the lower priority setting is set to Yes.
Run Options Screen

This screen is accessed by paging down from the Per Run Parameters screen. The
full navigation to this screen is MM > 3.Change Data > 4.Preemption > # ENTER (to
pick a preemption run to edit) > 1.Per Run Data > 1.Per Run Parameters > PGDN .
It provides additional parameters that determine, overall, how this particular
preemption run operates.
Run 1 Options
Double Clear Overlap Enable: N

Lead Overlap Enable: N
Delay Overlap Enable: N
Force Off to First Interval: Y
Use Interval Data for Overlaps: Y
Enable Coord During Cyclic Intervals: N
Figure 271 – Per Run Parameters, Screen 2
The following six Per Run parameters are boolean settings (Y/N) that enable or
disable special capabilities for this preemption run.
Note The first three ‘enable’ functions on this screen will not function unless the ‘Use
Interval Data for Overlaps’ parameter is set to ‘Y’.
Double Clear Overlap Enable

This option allows overlaps programmed for preemption to double clear during
preemption interval operation. The double clearing parameters are taken from the
normal overlap database, because there is no provision for double-clear overlap
programming in the Preemption database. If the overlap is not used during normal
operation, do not program any parent phases for the overlap. The preemption

programming will determine the parent phases on an interval-by-interval basis. If the

‘Use of Interval Data for Overlaps’ parameter is set to NO, this setting is not used.
Lead Overlap Enable

This option allows overlaps programmed for preemption to lead parent phases during
preemption interval operation. The leading overlap parameters are taken from the
normal overlap database, since there is no provision for leading overlap programming
in the Preemption database. If the overlap is not used in normal operation, do not
program any parent phases for the overlap. The Preemptor will determine the parent
phases on an interval-by-interval basis. If the ‘Use of Interval Data for Overlaps’
parameter is set to NO, this setting is not used.
Delay Overlap Enable

This option allows overlaps programmed for preemption to delay their parent phase
(or phases) during preemption interval operation. The delay parameters are taken
from the normal overlap database, since there is no provision for delay programming
in the Preemption database. If the overlap is not used in normal operation, do not
program any parent phases for the overlap. The Preemptor will determine the parent
phases on an interval-by-interval basis. If the ‘Use of Interval Data for Overlaps’
parameter is set to NO, then this setting is not used.
Force Off to First Interval

This option determines whether the preemption will force-off the active greens when
transitioning to preemption. The default value is ‘Y’.
Use Interval Data for Overlaps

This option is available to simplify overlap programming. The default value is Y. When
set to Y, the preemptor operates as it did in earlier versions of firmware (i.e. prior to
version 3.6.) When set to N, the normal overlap data is used during the preemption,
and overlaps are not specified in each Interval. It is important to remember that during
the process of entering preemption, the overlap entry parameters that have been
entered into the preemption run itself are always used. Normal operating overlap
settings are not used until the transition into the preemption run has been completed.
Enable Coord During Cyclic Intervals

This feature allows coordination and preemption to run concurrently during Cyclic
Intervals. If multiple Cyclic intervals are used, care must be taken in programming the
order of the intervals so that they match the normal phase rotation sequence.
Therefore, we recommend you use one Cyclic interval if the rotation can change by
time of day or coordination pattern. The coordinator will be set free during the
beginning stages of the preemption, until the Cyclic interval or intervals have begun.

Per Run Times

This screen is accessed from the PER RUN MENU by entering a 2. (The full
navigation path is MM > 3.Change Data > 4.Preemption > #, ENTER (to pick a
preemption run to edit) > 1.Per Run Data > 1.Per Run Times.)
Run 1 Times
Duration Time: 30 secs

Delay Time: 0 secs
Reservice Time: 0 secs
Omit All last portion of Delay: 0 secs
Fail Max Time: 15 mins
Duration Timer as Gap Timer: Y
Figure 272 – Per Run Times
Duration Time
The valid range is 0 to 255 seconds. The Duration Time is a way to guarantee a
minimum Preemption time. This timer begins upon entry into the first Cyclic or Dwell
interval. The run will not terminate until this timer has expired and the preempt call
has become inactive. Note that when the Duration Timer Used as Gap Timer feature
is enabled (Y), the duration timer acts much like a phase Passage Timer but for the
preempt input. It is useful for a preempt signal that is intended to be steady but may
be intermittent.
Delay Time
The valid range is 0 to 255 seconds. This parameter will delay the entry into
preemption by the programmed amount. If the preempt call goes away before the
Delay time has passed, the run will not be serviced unless the call is locked (see
above). This timer is concurrent with the Re-Service Timer (see below). If a Preempt
Input becomes active before the Delay Time and the Re-Service Time have expired,
the call will not be serviced until both timers have reached zero. All types of runs
respect the Delay Timer.
Reservice Time
The valid range is 0 to 255 seconds. Occasionally, one might wish to prohibit a
previously served preemption run from being run again for a certain amount of time.
To enable this feature, program a non-zero time into the Reservice Time field. The
timer will begin upon activation of each preemption input. If a preemption input
becomes active again while the Reservice Timer is still timing from a previous
service, the call will be ignored until the timer expires. If the input is still active when
the timer times out, it will be serviced at that time. Note that the re-service parameter
is ignored by railroad preemption runs. A Railroad Preemption will always be serviced
if the call meets the railroad de-bounce criteria.
Omit All last portion of Delay

The valid range is 0 to 255 seconds. This parameter only applies if the preemption
run has a non-zero delay time. When the delay timer is less than or equal to this

parameter, omits are applied to all phases and peds, and a hold is applied to all
greens. Once the delay timer reaches zero, the normal preemption transition occurs.
Fail Max Time

The valid range is 0 - 255 minutes. This parameter starts timing with the duration
timer. It forces an exit from preemption and disables the run until the input again
becomes inactive. This can be used to prevent false preemptions if an emergency
vehicle is parked within range of the preemption detector, inadvertently keeping the
preemption input ON when it is not intended.
Duration Timer as Gap Timer

When the Duration Timer Used as Gap Timer feature is enabled (Y), the duration
timer acts much like a phase Passage Timer, but for the preempt input. It is useful for
a preemption signal that is intended to be steady but may be intermittent.

Entry Parameters
Preempt entry controls are found under item 3 of the Per Run Menu. The full
navigation path to this screen is: MM > 3.Change Data > 4.Preemption > #, ENTER
(to pick a preemption run to edit) > 1.Per Run Data > 3.Entry Parameters.)
Run 1 Entry Parameters
Double Clear Overlap Mode: 0 NORMAL

Red Revert Override: N
Green: 5.0 Yellow: 4.0

Walk: 0 Red: 2.0
Ped Clr: 7 Overlap Yellow: 4.0
Figure 273 – Preemption Entry Parameters screen
Double Clear Overlap Mode

This setting provides a mechanism to double clear an overlap when transitioning into
preemption when the first interval is all red. This parameter specifies how a double
clearing overlap behaves when transitioning into preemption. The options are:
0 = normal double clear
1 = no double clearing
2 = double clear normal or if going to red rest
3 = double clear only if going to red rest
Red Revert Override

This parameter determines whether to override the red revert setting when
transitioning into preemption. This is applicable in cases where the “soon-to-be-
preempted” phases are yellow in normal operation and a preemption call occurs.
Entry Times
The fields at the bottom (Green, Yellow, Red, Ped Clr, etc.) are used to insure that a
certain amount of time is timed for the various intervals before proceeding with the
preempt run. This is to prevent the situation where a run becomes active soon after a
phase turns green (for example), causing a short green time. Note that the times
entered here override normal times. For example the normal initial time (minimum
green) value for a phase might be 10 seconds, but if the preemption run green value
is 5 seconds, then the green can terminate after 5 seconds upon entry into the
preemption run.
Note If the Minimum Entry time for any interval is set to zero (0.0), the preemption run
will use the normal phase time. It will not omit the interval.
Also note that Entry Times can be larger than normal times.

Walk
This entry time differs from the other times because it was a new addition in the
v3.6.2 firmware in mid-2005. In the other entry times, a value of zero causes the
normal phase time to be used. In prior firmware revisions, the walk always advanced
to ped clearance when preemption occurred, because there was no entry Walk
parameter. Therefore, to provide backward-compatibility, if the value is zero and
preemption occurs during the walk interval, the phase advances to ped clearance. But
if the value is non-zero, the walk interval timed will be the amount of time set here.

Per Interval Parameters

It should be noted that all data programmed on these screens are also contained in the
Interval Data screens (when taken as a whole). Any changes made here are
automatically updated on the Interval Data screens and vice versa. The Interval Data
screens, however, contain additional information that is not included here, such as times,
phase colors, and flash plans. The Interval Data screens (in toto) provide all
programming data relative to intervals, while the Interval Control screens provide only
some of the data. The Interval Control screens are provided mainly for programming and
viewing convenience. It is sometimes easier to view or program certain portions of the
data for a preempt run if all of the intervals can be viewed on one programming screen.
Some users will prefer to use these screens to program the parameters
available, then go to the Interval Data screens to program the remaining Interval
data such as Times, Phase colors, Flash plans, etc.
Most users will prefer to program all Interval Data from the Interval Data
screens and use the Interval Control screens for later viewing and editing.
To access the first screen of Per Interval Parameters, choose option 4.Per Interval
Parameters from the Per Run menu. (The full navigation path for this screen is MM >
3.Change Data > 4.Preemption > #, ENTER (to pick a preemption run to edit) > 1.Per
Run Data > 4.Per Interval Parameters.)
Run 1 Per Interval Data VALUE(YES/NO)

PgDn for More 1 1 1 1 1 1 1
Fcn\Ivl 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
Valid X X X X X X X X X
Dwell X
Fixed X X X X X X
Tenth X X X X X X
SHIFT-RT.-> for Intervals 17-32
Figure 274 – Per Run/Per Interval Parameters screen 1
There are six options for each interval. To program them, move the cursor to the row
containing the type of parameter and the column for the interval of interest. Then use
the Y/N key to toggle the state of the flag on or off. The ON state is indicated by an
‘X’. Press the SHIFT key and the Î key together to access intervals 17 - 32.
Use the PGDN button to display the second page of Per Interval parameters available
here under the Per Run menu.
Run 1 Per Interval Data VALUE(YES/NO)

1 1 1 1 1 1 1
Fcn\Ivl 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
Exit X X X
PC->Yel
SHIFT-RT.-> for Intervals 17-32

Figure 275 – Per Run/Per Interval Parameters screen 2

See the manual section that discusses the Interval Data item (on the Preemption Run
Menu, page 308) for the definitions of these parameters.
Exit Parameters
The last item on the Per Run menu are the preemption exit parameters. These
settings define how the controller will terminate a preemption run and return to normal
operation. The full path to this screen is MM > 3.Change Data > 4.Preemption > #,
ENTER (to pick a preemption run to edit) > 1.Per Run Data > 5.Exit Parameters.
Run 1 Exit Controls

Exit Mode: 1 = Go To the Next Demand
(0-3) 1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
Phases X X
Veh Call
Ped Call X
Figure 276 – Per Run Exit Parameters screen
Note It is true that in previous 3000 series firmware versions, a preemption run
required a specific exit interval to be programmed, however with the release of
the version 3.6.2 firmware in mid-2005, this requirement has gone away. If no
exit interval is specified, the Preemptor will exit the run when it reaches the last
programmed interval.
Exit Modes
There are four options available for terminating a preemption run.
Go to Exit Phases (0). This mode causes the controller upon exit to go to the
programmed set of phases at the bottom of the screen. If no exit phases are
programmed, the run exits to ‘Next Demand’. Also see the important note below
concerning the function of exit phases.
Go to Next Demand (1). This mode allows the controller to service the next
phase with demand in the normal sequence.
Resume Interrupted Seq (2). This mode causes the controller to resume
normal operation at the point in the sequence from which it left to service
preemption. The controller in essence “picks up where it left off.”
Exit to Coordination (3). In this mode the controller will resume normal
coordination force offs and permissives immediately upon run completion. Any
Exit Phases programmed are ignored. The controller exits to the next
demanding phase with an open permissive status.
Exit Phases
Selects phases that are to be serviced immediately following the preempt run. Exit
phases are ignored for exit modes 1, 2, and 3. Select phases by toggling with the Y/N
key or entering the phase number.

Important If the programmed phases are incompatible (conflicting), the preemption

run will be refused because it would never be able to return from
preemption. The Preemption Check feature tests Exit phases to verify
that only compatible phases can be called from the end of a preemption
run.
Vehicle Call
If so desired, the controller can place calls on selected phases when exiting
preemption under any mode. Pressing the Y/N key, or a key that corresponds to the
phase number will toggle a phase to be called upon exit.
Ped Call
Calls to pedestrian phases can also be placed upon exiting a preemption run. Use the
Y/N button to toggle ped phases. An ‘X’ under a phase indicates that a call will be
placed to that pedestrian phase when the preemption run is exiting.

Interval Data
The signals displayed and the timing of each interval in this preemption run are
programmed on these screens. There are three screens of data available for each
interval. These screens can be navigated by paging down through the three screens
and then to then next interval, or by going to the Interval field at the top of the screen,
entering a number, and pressing the ENTER button.
Important The number of intervals that are available to program here are defined
on the Per Run screens, under Per Run Parameters. The Max Intervals
setting must be non-zero for the Interval Data screens to be accessible.
(See page 298.)
It should be noted that some of the data entries on these screens can also be
programmed by going to the Per Interval Parameters screens under the Per Run
menu (selection 4) as described on page 305. Any changes made here are updated
there as well, and vice versa. The Interval Data screens of this section, however,
contain all settings concerning this preemption run’s intervals, including times, phase
colors, and flash plans, some of which are not provided there. As a result, most users
prefer to program the interval settings on the screens here and will only use the Per
Interval screens under the Per Run menu for later viewing and editing purposes.
The first of the three screens of per interval data for an interval is shown in Figure
277. This one concerns phase and ped colors.
Run 1 Interval 1 Valid: X Dwell:
Tenths: PC-Yel: X Exit: Fixed: X
Time: 15 Ph Flash: 0 Ped Flash: 0
VALUE(0=R/D, 1=Y/P, 2=G/W) 1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
Color G G
Ped Col W W
PgDn for Overlaps
Figure 277 – Preemption Interval Data screen 1
This one concerns the preemption interval’s overlap settings:
Time: 15 OL Flash: 0 Ped Flash: 0
VALUE(0=R/D, 1=Y/P, 2=G/W)
FUNC\PH A B C D E F G H I J K L M N O P
Color
Ped Col
PgDn for PE Outs

And the final screen for Interval 1 concerns the preemption outputs generated by this
interval:
Time: 15 Ped Flash: 0
VALUE(YES/NO) 1 1 1 1 1 1 1
FUNC\Out 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
PE Out
PgDn for Next Interval

Paging down again will take you to the screens for Interval 2.
Interval Screen Selection

The interval number is displayed at the top of the screen. There are three screens for
each interval. Each contains the interval control parameters*, and in addition,
-Screen 1 contains programming to define phase and ped colors, time, and flash
plans
-Screen 2 contains programming to overlap and ped overlap colors, time, and flash
plans
-Screen 3 contains programming to define preempt outputs, time, and flash plans
A particular interval can be selected by paging down successively, but it may be more
convenient to enter the interval number. This method takes you to the specified
interval. This may be preferable if the former process requires many page downs.
Fields on the First Interval Screen

The fields of the first of the three screens for each interval are defined below.
Run
This is a reminder to show which preemption run is currently being viewed or edited.
Interval
This field shows which interval is being viewed or edited on this screen. This field can
be used as a method to switch between intervals within the series of data screens. By
placing the cursor in this field, entering the desired interval number, and pressing
ENTER , you can switch directly to the interval you wish to edit. The Interval Data Ped
and Phase Color screen for that interval will appear.
*
Although the Interval control parameters of Valid, Dwell, Exit, Fixed Time, PC->Yel, appear on
each of the three Per Interval screens for each interval, they are not different settings. Actually
they are the same value, and if changed on one screen, the change is made on all three
screens.

Valid
This indicates whether or not the interval in question is to be executed during the
preemption run. It is useful if one wishes to leave unused programmed intervals in
place for future use or expansion. It can be set to valid (X) or not valid (blank).
Dwell
A Dwell interval is one in which the controller will “rest” until the termination of
preemption. Typically there is no more than one Dwell interval per run. There is
usually either a Dwell interval or a set of Cyclic intervals in each run. Once a run is in
Dwell, it will remain there until the exit criteria is met.
See the “Comparison of Cyclic, Fixed, and Dwell Intervals” on page 313 for more
details about using the three types of preemption intervals.
Tenths
When enabled (X), time is entered in tenths of seconds and the valid range is from
0.0 to 25.5 seconds. When disabled (blank), time is entered in whole seconds and the
range is 0 to 255 seconds. By default, Tenths is disabled. It is typically enabled for
short duration fixed intervals like yellow and red clearances, where short duration,
accurate timing is required.
PC-Yel
PC-Yel stands for ‘Ped Clearance through Yellow’. When enabled (X), the Ped
Clearance interval is allowed to extend through the Yellow interval (i.e. ‘Don’t Walk’
flashes through yellow.) Note that this is independent of the programming in the
Phase Functions screen, or in other words, it is possible to flash ‘Don’t Walk’ through
yellow during a preemption run, but not normally. Caution should be exercised when
using this feature, since pedestrians will see a shorter steady Don’t Walk period
before the opposing green occurs.
Exit
The Exit designation specifies intervals from which the controller is allowed to exit
preemption. The controller will not terminate preemption until an exit interval has been
reached and the criteria for exit (Duration Timer timed out and absence of call) have
been satisfied. There may be more than 1 exit interval programmed, exit simply states
that it is OK to leave preempt at this point, which may apply to several intervals
(especially Cyclic). If an Exit interval is not specified, the run exits when it gets to the
end.
Fixed
A Fixed interval is executed for a fixed amount of time, then proceeds to the next valid
interval. If a Run contains only a single Fixed Green interval operation, the operation
will be similar to a Dwell interval. The controller will rest in the Green until exit criteria
is met and Yellow and Red Intervals are not required. Yellow and Red intervals could
be used to time unique yellow and red times for exiting the Run.
See the “Comparison of Cyclic, Fixed, and Dwell Intervals” topic on page 313 for
more details about using the three types of preemption intervals.

Cyclic
An interval is considered Cyclic if it is neither Fixed nor Dwell. Cyclic intervals are only
executed if there is demand on the phases selected by the interval. If phases are
incompatible, the run will cycle between them. Normally, a Cyclic interval would be
used in conjunction with several other Cyclic intervals that are the last set of intervals
in the Run. Each Cyclic interval is programmed as an exit interval and the 3000 will
cycle between this set of Cyclic intervals, serving specified phases with demand until
the exit criteria is met and the unit returns to normal operation. Phases specified
within Cyclic intervals derive their timing from their normal phase timing.
See page 313 for more details about using the three types of preemption intervals.
Time
This parameter is used to set the primary timing value for the interval. The exact
purpose depends on the type of interval this is. For example, for Fixed intervals, this
value specifies the fixed time the interval will be active. For Cyclic intervals, if this
value is 0, then phases specified by the interval will use their normal max times. If a
non zero value is specified, the value becomes the max time for all phases serviced
in the interval. This allows the user to program alternate max times that are only in
effect during preemption. A summary of the uses of the Time parameter based on the
type of interval is shown in Table 41.
Table 41 – Interval Timing Effects
Interval Type How ‘Time’ Parameter is Used
Fixed green Initial time
Fixed yellow Yellow time
Fixed red Red clearance time
Cyclic green Max time, if Time is set to a value greater than zero
Dwell green Initial time
Fixed green and walk Walk time
Fixed green and ped clear Ped clearance time
Dwell walk Walk time
Ph Flash
There are 5 flash plan associations possible for each interval, each assigned from a
choice of 16 flash plans (or none). This and the other flash plan associations are for
specific output groups, and are only required when some type of flashing indication is
required for the interval. This field is the first of those associations, for the normal
phases of the interval. Ph Flash and the other flash plan associations can be set to
one of the 16 available preemption run flash plans, or to none of them (Ph Flash = 0.)
The first two associations are on the first screen of each interval and apply to Phase
Flash and Ped Flash. The 3rd and 4th are on the second screen (page down from
first) and apply to the overlap flash plan (OL Flash) and the pedestrian overlap flash
plan (the Ped Flash field on the second Interval Data screen.) The fifth is on the third
screen and applies to Preempt (output) Flash. The flash plan associated with each of

these 5 groups, depending on the group, determines which phase, overlap, or PE

output will flash and how it will function (i.e. normal, wig, wag, or dark.)
The configuration of the flash plans is described on page 323.
Ped Flash
This tells the interval which flash plan to use for pedestrian phases. This can be set to
one of the 16 available flash plans, or to none of them (Ped Flash = 0.) The
configuration of the flash plans is described on page 323.
Color/Ped Col
These two rows of per-phase settings refer to phase and pedestrian colors; this area
defines the colors of the phases and peds for this interval. (The two lines above these
rows show how to program the settings.) For each vehicle phase, enter 0 = Red (D), 1
= Yellow, or 2 = Green. All signals are Red by default, so it is only necessary to
program phases that are to be something else. Reds (D’s) appear as blanks on this
screen. For the Ped Col row, program the colors of the pedestrian phases desired for
this interval using these values: 0 = Solid Don't walk, or 1 = Flashing Don’t Walk, or 2
= Walk. All ped phases are Solid Don’t Walk unless programmed otherwise.
Example of First Screen Interval Data

Below is an example of a simple, one interval long, ‘Dwell’ preemption run. When
Preempt 1 is activated, the controller will go to phases 1 and 6 and remain there until
the preemption input is removed.
Run 1 Interval 1 Valid: X Dwell: X

Tenths: PC-Yel: Exit: X Fixed:
Time: 0 Ph Flash: 0 Ped Flash: 0
VALUE(0=R/D, 1=Y/P, 2=G/W) 1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
Color G G
Ped Col
PgDn for Overlaps
Figure 280 – Example of Preemption Interval Data screen 1

Fields on the Second Interval Screen

The fields of the second of the three screens for each interval are defined below.
Most of the top of the screen is identical to the first Interval Data screen. These are
the same values as shown on the last screen, and editing them on any of the three
screens will change them on all three. These duplicated items are not described
below.
Time: 15 OL Flash: 0 Ped Flash: 0
FUNC\PH A B C D E F G H I J K L M N O P
Color
Ped Col
PgDn for PE Outs
Figure 281 – Preemption Interval Data screen 2 - details
You can page down from this screen to see this interval’s Preemption Output settings.
OL Flash
This field defines which flash plan will be used for the overlap phases during this
interval of the preemption run. The overlap phases can be assigned to one of the 16
available run flash plans, or to none of them (OL Flash = 0.) The configuration of the
flash plans is described on page 323.
Ped Flash
This is NOT the same value as the one shown on the first Interval Data screen. This
refers to the Ped Overlap Flash plan. The pedestrian overlap phases can be assigned
to one of the 16 available run flash plans, or to none of them (Ped Flash = 0.) The
configuration of the flash plans is described on page 323.
Color/Ped Col
These two rows of per-phase settings refer to overlap phase and overlap pedestrian
colors; this area defines the colors of the overlap phases and peds for this interval.
These use the same inputs to program the phase colors as the regular phase Color
and Ped Col settings on the previous screen. For each vehicle overlap, enter 0 = Red
(D), 1 = Yellow, or 2 = Green. All signals are Red by default, so it is only necessary to
program overlap phases that are to be something else. For the Ped Col row, program
the colors of the pedestrian overlap phases desired for this interval using these
values: 0 = Solid Don't walk, or 1 = Flashing Don’t Walk, or 2 = Walk. All ped overlap
phases are Solid Don’t Walk unless programmed otherwise.

Fields on the Third Interval Screen

The fields of the third of the three screens for each interval are defined below. Most of
the top of the screen is identical to the first two Interval Data screens. These are the
same values as shown on the previous screens, and editing them on any of the three
screens will change them on all three. These duplicated items are not described
below.
Time: 15 PE Flash: 0
VALUE(YES/NO) 1 1 1 1 1 1 1
FUNC\Out 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
PE Out
PgDn for Next Interval

Figure 282 – Preemption Interval Data screen 3 - details
You can page down from this screen to go to the next interval’s Data screens.
Sixteen (16) user-defined outputs are provided for use during preemption when the
corresponding interval is active. However, unless you are using TS 2 Type 1
hardware with BIU output mapping, only 6 of this outputs are physically available as
pin outputs on the unit. Outputs may be steady or they may optionally be flashed by
using a flash plan.
PE Flash
This field defines which flash plan will be used for preemption outputs during this
interval. The outputs can be assigned to use one of the 16 available run flash plans,
or to none of them (PE Flash = 0.) The configuration of flash plans is described on
page 323.
PE Out
Specify which outputs are to be active during the interval by using the Y/N key to
toggle the value for each output.
At this point, the interval is completely specified. Press PGDN to access the next
interval and continue until all active intervals in the run are defined.

Comparison of Cyclic, Fixed, and Dwell Intervals

Every interval in a preemption run must be either a Cyclic interval, a Fixed interval, or
a Dwell interval.
Cyclic Intervals
A Cyclic interval is also known as a ‘Limited Cycle Preemption’ interval.
Note An interval is considered to be ‘Cyclic’ if both Fixed and Dwell are OFF.
For example, to program a cyclic preemption run in which phases 2 and 6 are
serviced, followed by phase 3, only two intervals are required. The first interval
specifies phases 2 & 6 green (and Walk if pedestrian operation is needed) and the
second interval specifies phase 3 only. The controller will function as a normal
actuated controller, but with the other phases omitted. The 3000 will cycle between
the two (or however many there are) cyclic intervals, serving the specified phases
with demand, until the exit criteria is met and the unit returns to normal operation.
In versions of firmware prior to version 3.6.2 (released in mid-2005), once the
Preemptor got into a cyclic interval, it would cycle between the first cyclic interval and
the last interval in the run. But now the Preemptor cycles between the first and last
cyclic intervals (and all intervals between) unless it hits a dwell interval, as long as the
preemption input is active. The last intervals can be Fixed and will then be serviced
when the preemption demand goes away, as described in the “Fixed Intervals” topic
on page 318.
Interval 1: Fixed Green, Phase 3/8, 10 seconds
Interval 2: Cyclic Green, Phase 2/5
Interval 3: Cyclic Green, Phase 2/6
Interval 4: Cyclic Green, Phase 7
Interval 6: Fixed Green, Phase 2/6, 20 seconds, Exit = Y
In the above example, the Preemptor will serve Interval 1, then cycle between
Intervals 2, 3 and 4 until the preemption input is removed. When removed, it serves
Intervals 5 and 6, then exits according to the programmed exit mode.
The next two topics explain why the only reason to use multiple Cyclic intervals is if
the preemption run has one or more of the following special requirements:
1. It requires a different order of service than the active sequence.
2. The run’s overlap configuration must act differently than the normal operation.

Overlap Operation Within Preemption Intervals

It’s important to realize that overlaps can operate differently in cyclic intervals. There
are two ways that overlaps can operate within a preemption run, based on the setting
chosen for the Per Run parameter ‘Use Interval Data for Overlaps’. (See page 300 for
details.)
When the ‘Use Interval Data for Overlaps’ setting is YES, then overlaps operate
differently within the preemption run than they do during normal operation. In such a
case, only the overlap green movements during intervals in which the parent phases
are green require programming. Overlaps are essentially re-programmed in
preemption. Similar to normal overlap operation, the controller automatically
determines if an Overlap needs to clear depending upon whether the next interval
contains that Overlap or not.
As an example, assume a three interval preempt run in which phase 1 is serviced in
interval 1, phase 2 in interval 2 and phase 3 in interval 3. Overlap A is programmed to
be green in interval 1 and 3. During the preempt run, if the controller is currently in
interval 1 and there is demand on phase 2 (therefore interval 2 is next), the Overlap
will clear with phase 1. If there is demand on phase 3 and none on phase 2 (interval 3
is next), the Overlap will remain green as phase 1 clears.
Also note that Double-clearing, Leading, and Delayed overlaps are also now available
within a preemption run. However, since these values are not stored within the
preemption database, these settings should be assigned to normal overlaps. If the
preemption run overlaps are special cases that are not used during normal operation,
assign these settings to overlaps that have no parent phases during normal
operation. The Preemptor will determine the parent phases of the overlaps used by
the way they are called within the run.
Conflicting Phases Within Cyclic Intervals

In versions of firmware prior to version 3.6.2 (released in mid-2005), an interval was
not allowed to contain conflicting phases. A simple Railroad preemption involving a
track clearance followed by cyclic intervals could only be programmed as follows:
Interval 2: Fixed Yellow, Phase 3/8, 4 seconds
Interval 3: Fixed Red, 3 seconds
Interval 4: Cyclic Green, Phase 2/5, Exit = Y
Interval 5: Cyclic Green, Phase 2/6, Exit = Y
Interval 6: Cyclic Green, Phase 7, Exit = Y
But the newer versions of firmware simplify this programming by allowing conflicting
phases in Cyclic intervals. (Fixed and Dwell intervals cannot have incompatible
phases.) As a result, the above preemption run can now be programmed like this:
Interval 2: Cyclic Green, Phases 2, 5, 6, 7, Exit = Y

Use of Coordination During Cyclic Preemption Intervals

This feature allows coordination and preemption to run concurrently during Cyclic
intervals. The setting to allow this capability is called ‘Enable Coord During Cyclic
Intervals’ and is available on the preemption run’s Options screen as shown below,
and described on page 300. If multiple Cyclic intervals are used, care must be taken
in programming the order of the intervals so that they match the normal phase
rotation sequence. Therefore if the rotation can change by time of day or coordination
pattern, it is recommended that you use one Cyclic interval rather than many, as
described in the previous example. The coordinator will be set free during the
beginning stages of the preemption until the first Cyclic interval(s) begin.
Run 1 Options, Page Down for more
Run Enable: Y Override FLASH: Y

Railroad: N Go to Higher PE: Y
PE Input Lock: N NEMA Priority: Y
Early PE Out: Y Hold Only: N
Figure 283 – Per Run Options screen 1
Page down to the second screen of Per Run Options for this preemption run:
Run 1 Options
Double Clear Overlap Enable: N

Lead Overlap Enable: N
Delay Overlap Enable: N
Force Off to First Interval: Y
Use Interval Data for Overlaps: Y
Enable Coord during Cyclic Intervals: Y Set to ‘Y’ for coordinated
operation during cyclic
Figure 284 – Per Run Options - Enabling Coordination intervals of the run
Fixed Intervals
An interval functions as Fixed interval if the ‘Fixed’ field is enabled on the Interval
Data screens. (An ‘X’ indicates the parameters is enabled.)
A fixed interval times a fixed value and advances to the next serviceable interval. As
an example, notice the following three fixed intervals:
Interval 1: Fixed Green
Interval 2: Fixed Yellow
Interval 3: Fixed Red
At the end of interval 1, the preemptor sees no reason to advance to Interval 2 and 3,
which would result in the preemption dwelling in red until the preemption input goes
away. Instead the run will rest in interval 1 until the preemption input goes away.

Consecutive Fixed Red Intervals

Consecutive Fixed Red intervals are permitted during a preemption run. In versions of
3000 Series firmware prior to v3.6.2, they were not permitted.
Fixed Red before Dwell Red

Previously, the controller firmware would not allow the following preemption
sequence:
Interval 2: Dwell Red
Interval 3: Fixed Red, 5 seconds, Exit = Y
The firmware would have invalidated the run because of Interval 1. This sequence of
intervals is now acceptable to the preemption tests.
Fixed Yellow and Fixed Red Intervals

Fixed Yellow and Fixed Red Intervals are no longer mandatory. In firmware versions
prior to v3.6.2, a fixed yellow interval had to follow a fixed green interval (unless the
fixed green was the only interval) and a Fixed Red had to follow a Fixed Yellow.
A typical dwell railroad preemption would be programmed like this:
Interval 1: Fixed Green, Phase 3/8 10 seconds
Interval 2: Fixed Yellow, Phase 3/8 4 seconds
Interval 4: Dwell Green, Phase 2/6, Exit = Y
But now programming has been simplified by allowing the above preemption run to
be programmed like this:
Interval 1: Fixed Green, Phase 3/8, 10 seconds, Exit = Y
Interval 2: Dwell Green, Phase 2/6, Exit = Y
Before going to Interval 2, the controller will time the normal yellow and red clearance
times after Interval 1.
Note However, if one opts to use a Fixed Yellow interval, a Fixed Red interval must be
inserted immediately after it.
There is no need to program any yellow or red intervals if the preemption does not
require unique times.
Note In a railroad preempt, it is recommended that all intervals are set as exit intervals.
This enables a new preempt call when the track clearance phases are in yellow to
immediately revert to the track clearance phase greens.
If the dwell interval is the only exit interval, the preemptor will proceed to the dwell
phases, then revert to the track clearance phases to serve the new preempt call.

Fixed Intervals before Preemption Exit

When the preemption input is removed, if the Cyclic intervals are not exit intervals,
the preemptor will cycle through any Fixed intervals that follow them until it reaches
the last interval, or an exit interval, whichever comes first. When it hits this point, it will
process the Exit Mode and exit the run accordingly. See “Cyclic Intervals” on page
315 for more details.
Dwell Intervals
Dwell Intervals are similar to Cyclic intervals in that only the right-of-way intervals
need to be specified. Dwell intervals typically define the “hold phase” green, and let
the Preemptor manage the rest of the run.
Timing also operates differently in various types of intervals. See the Time definition
on page 311.
All Red Dwells

In versions of the firmware prior to v3.6.2 (released in mid-2005), a dummy phase
was required for an all red dwell interval. If the user programmed the following
preemption run, it would result in a “bad plan” error when exiting the run programming
screens. In order to dwell in red as described in the example below, the user would
have had to dwell in a dummy phase.
Interval 2: Fixed Yellow, Phase 3/8, 4 seconds
Interval 4: Dwell Red, Exit = Y
However, now, an all red dwell interval is permitted within a run without the need for a
dummy phase.
Dwell in Ped Clearance

A Dwell in Ped Clearance interval is not allowed.
Dwell in Yellow
Dwell in Yellow is not allowed during a preemption run.

Applying Exclusive PED During Preemption

It is possible to set up preemption to run exclusive pedestrian (XPED) phases only
during a preempt run but NOT in normal operation. The operator must set up the
controller as follows:
1. Set up a unique phase in the controller sequence for XPED (i.e. phase 9 in ring
1 and co-phase set to 3.)
2. Program that phase as the exclusive ped phase under Xped 1.
3. Program the appropriate outputs for WALK.
4. Program the XPED enable to be the XPED INPUT on the d-module preempt
connector pin 24.
5. Program the Preempt Run: (only 1 interval is needed).
Interval 1: XPED phase (i.e. phase 9) GRN and WLK only
No other colors need to be programmed; the controller will activate the others based
on the exclusive ped programming. Although the PED CLR times can be set to zero,
non-zero values are recommended. Programming a red clearance for the XPED
phase (i.e. phase 9) to allow a clearance between PED CLR and the exit greens is
also recommended.

Documents and Charts Supporting Preemption Programming

There are forms in Appendix B (page 434) that can be used to assist in programming
preemption runs. There is a good deal of data involved in programming preemption,
but the task can be simplified by good organization and some “up front” work to lay
out the run. Once this is done, entering the data is relatively simple.
Preemption Interval Table

The following is a table which illustrates how various preemption runs will behave.
Table 42 – Preemption Intervals
# of Intvls Run Intervals Operation
Remains in 1/6 green until exit criteria are
1 Dwell 1/6 G
met
Remains in 1/6 green until exit criteria; exits
1 Fixed 1/6 G
with normal phase yellow and red
Serves 3/8 green, then cycles through 1, 2,
Fixed 3/8 G, Cyclic 1, 2, 6,
2 6, and 7, until exit criteria are met, when it
7=Exit
exits out from 7.
Serves 3/8, then dwells in 2 and 6 green
2 Fixed 3/8, Dwell 2/6 G = Exit
until the exit criteria are met.
Remains in 1/6 green until exit criteria; exits
3 Fixed 1/6 G-Y-R
with programmed yellow and red times.
Fixed R, Dwell R, A fixed red is served, then the intersection
3
Fixed R = Exit dwells in red until the exit criteria are met.
Fixed 3/8 G, Dwell R, Serves 3 and 8 with green, then dwells in all
3
Fixed R = Exit red until the exit criteria are met.
Fixed 3/8 G-Y-R, Dwell 2/6 G, Serves 3/8 G-Y-R, then dwells in 2/6 until
4 exit criteria are met
Exit = Dwell 2/6
Serves 3/8 G-Y-R, then serves 7, 2/5 and
Fixed 3/8 G-Y-R, Cyclic 7, 2/5, 2/6 for Initial regardless of demand on “first
6 2/6 pass” thru, then cycles between 7, 2/5, 2/6
Exit = Cyclic 7, 2/5, 2/6 according to demand until exit criteria are
met
Serves 2/5 G-Y-R and then Cyclic 1, 7 for
Fixed 2/5 G-Y-R, Cyclic 1, 7, Initial time on “first pass” thru and cycles
6 Dwell 4/8 G between 1 & 7 until exit criteria met or
Exit = Cyclic 1,7 Dwell 4/8 demand on 4/8 exists. Once 4/8 serve, it
dwells until exit criteria are met
Fixed 3/8 G-Y-R, Dwell 2/6 G, Same as above except when exit critieria
7 Fixed 4/7 G-Y-R, Exit = Fixed are met, it serves Fixed 4/7 G-Y-R, then
4/7 resumes normal operation
Serves 3/8 G-Y-R, then serves 2/5 and 2/6
Fixed 3/8 G-Y-R, Cyclic 2/5, for Initial regardless of demand on “first
2/6, Fixed 7 G-Y-R pass” thru, then Fixed 7 G-Y-R. Then it
8
cycles between 2/5, 2/6 according to
Exit = Cyclic 2/5, 2/6 & Fixed 7 demand until exit criteria are met. If it serves
2/5 or 2/6, it will serve Fixed 7

Description Of Preempt Run Rejection (‘Run Invalid’)

The 3000 controller will recognize certain types of programming errors once the
preemption input has been activated and a run is attempted. If such a problem is
detected, the run will not be executed and ‘RUN x INVALID’ will be displayed on the
Dynamic Normal Status screen (x = the preempt run number.)
The 3000 checks preempt programming for the following problems:
1. Max intervals > 32
2. Number of valid intervals is > Max intervals
3. No green with a walk or ped clear
4. Overlap green or yellow does not follow parent phase’s color (for example, OL
A is yellow while parent phases 3/8 are green)
5. Fixed Red must follow a Fixed Yellow
6. Incompatible phases in dwell or fixed intervals
7. Exclusive PED interval(s) programmed but Exclusive PED function is not
enabled.
8. Exclusive PED phase programmed to service concurrently with vehicle
movement and XPED function enabled. (e.g. XPED = peds 2+ 4+ 8, but PE
runs programmed to service phase 2 GRN and phase 2 PED.)
9. A yellow dwell interval
10. First interval is yellow
11. Incompatible exit phases
12. Ped overlap with ped clearance does not follow parent phases (e.g. Parent
phases 2/6 are in green and walk, while OL A is in ped clear.)
13. Dwelling in ped clearance
14. First interval is ped clearance
15. Max intervals = 0
16. Valid intervals = 0
17. Fixed Yellow after a Fixed Green doesn’t match (e.g. 3/8 G followed by 4/8 Y)

Flash Plans
Sixteen (16) Flash Plans are provided to enable any of the signal heads or user
defined outputs to be flashed (or remain) dark if so desired during Preemption. To
program a flash plan, enter a 3 at the main PREEMPTION menu.
Run 1 Flash Plan 1-16 VALUE(0= Normal,

1= Fl Wig, 2= Fl Wag, 3= Dark)
(1-16= Ph 1-16 or O/L A-P) 1 1 1 1 1 1 1
Plan\Out 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
1 1 0 0 0 2 0 0 0 3 0 0 0 0 0 0 0
2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Figure 285 – Preemption Flash Plan pogramming screen
Flash Plan Description

Columns 1 through 16 for each Flash Plan generically define the state of either
phases 1-16, peds 1-16, overlaps A-P, ped overlaps A-P, or preempt outputs 1-16.
The particular type of output intended by a plan is determined by how the plan is
assigned in the Per Interval section. There are up to 5 such assignments per interval
(see Per Interval definition). For example, if Flash Plan 1 is assigned to “Ph Flash,”
then flash plan 1 determines how phases 1-16 flash. If flash plan 2 is assigned to Ped
Flash, it determines how peds 1-16 flash, etc.
Each column in a flash plan specifies one of the following codes:
Table 43 – Column Codes in a Flash Plan
Code Heading
0 Normal (the state of the phase, ped, etc. is not affected by
the flash plan)
1 Flash “WIG” (the phase, ped, etc. flashes 180 degrees
out-of-phase with WIG)
2 Flash “WAG” ((the phase, ped, etc. flashes 180 degrees
out of phase with WIG)
3 Go Dark (the phase, ped, etc.) is dark
Flash plans do not determine the color that flashes for phases, peds, overlaps, nor
ped overlaps. These are determined by the color assigned in the Per Interval
programming. For example, say that Ph Flash is assigned Flash Plan 1 while phase 1
is programmed “Y” on the color row in an interval. If Flash Plan 1 flashes Phase 1
WIG, then phase 1 will flash Yellow WIG during that interval. An exception to this is in
the case of dark, where it doesn’t matter which color is specified. Another is for
Preempt Outputs where there is no color, so the flashing state directly pertains to that
output.
In general, one flash plan is required for each type of output group that needs to flash
one or more outputs. For example, if an interval is required to flash phase colors only,
then a single flash plan could be used to define how phases flash (colors themselves

are defined by the interval). If an interval is to flash both phases and overlaps, then it
would likely take two flash plans, etc. There could as many as 5 flash plans assigned
in one interval, though unlikely. The exception to the one-plan-per-group concept
would be only when two groups coincidentally flash all their like numbered (and used)
items the same. For example, phase 1 & O/L A, phase 2 & O/L B, phase 3 & O/L C,
etc. Although rare, flash plans could be shared in such a case.
To define a flash plan, move the cursor to the line for that plan and define the normal,
flashing, or dark state of each output for the intended group (phases, peds, O/L’s etc.)
All states default to 0 for normal operation (i.e. the signal will be steady when active)
so that if no flashing operation is desired, no programming is necessary. PGDN to
access more flash plans. Once flash plans are programmed they can be assigned to
intervals in the Per Interval programming section.
Quick Set-Up Procedures

Many preempt applications can be satisfied by one of the following two basic Preempt
schemes:
1. Simple fire run — The units preempts to a specific phase (or compatible
phase pair) and holds for a specific time or until the input goes away. Note that
this type applies to any preempt that simply goes to a specific phase (or phase
pair), it does not have to specifically be a “fire” run.
2. RR with track clear — The unit preempts to a specific phase (or phase pair)
to clear the tracks, and then either goes to a phase (or phase pair) and holds
until the RR input goes away, or, cycles a restricted set of phases until the RR
input goes away.
If any preempt run 1-6 fits one of the above, then the preempt quick set-up procedure
may prove to be useful. Quick set-up allows a specific type of preempt to be
programmed without requiring all the detailed parameters to be programmed. Values
programmed in quick set-up area, however, will be reflected in the detail mode
screens. The detailed parameters can still be accessed and edited if the requirements
go beyond the scope of the quick set-up programming.
Quick set-up greatly reduces the level of understanding normally required to program
preempt in the detailed mode.
To use Quick Set-up, select a run from the first preempt menu. In this example, Run 1
was selected.
Preemption Run 1 Menu
1.Per Run Data

2.Interval Data
3.Flash Plan for Run 1 Intervals
4.Quick Setup Procedures
When Changing Run Data, 1st Disable Run

Figure 286 – Open the Preemption menu for a particular run

Then select 4, Quick Set-up Procedures......

Preempt Run 1 Quick Setup Options
1. Setup as Basic Fire Run - Hold Phase

2. Setup as Basic RR w/ Track Clearance
3. Set Run 1 Detail to Fire Run Defaults
4. Set Run 1 Detail to RR Run Defaults
Current Detail Defaults Setting: None

Figure 287 – Quick Setup Options screen
Menu selections 1 and 2 advance to programming for Quick set-up fire run and RR
respectively. preempt. Selections 3 and 4 set all other detailed parameters (not
accessed in quick set-up menus) to appropriate defaults for the type of run selected—
fire or RR.
The default loads should be executed once when setting up a Quick Setup run for the
first time, prior to programming the actual run itself. It should be understood that the
detailed menu parameters are still used and must be properly set up. Menus 3 and 4
accomplish this without having to access the detailed mode screens or understand
their content. The current default setting is shown on the bottom of the screen, where:
None = The run has been cleared* or has never been defaulted in the Quick
Setup menu.
Fire = The run detail defaults were last set up for Fire.
RR = The run detail defaults were last set up for RR.
Quick set up for a fire run has one each set-up and interval screen. RR has 1 set up
and 7 interval screens.
Fire Run/RR Set-up Screen

Access setup screens to configure the specific sequence after having loaded a
default the first time programmed. The first page of the quick set up option is the
same for both Fire Run and RR. Only the interval programming screens that follow
differ between the two types.
Select menu 1, Quick Set-Up Procedure For Fire Run 1.....
-Run 1 As Fire Run Data- Run Enable: N
For many runs, the
PCL-Yel: N
default values
Gap (Duration) Time: 3 Entry GRN: 5.0 (as shown) are
Priority 1-6: 2 Entry YEL: 4.0 suitable as they are.
Delay Before Preempt: 0 Entry RED: 2.0 If so, only the interval
Reservice Time: 0 Entry PCL: 7 data will need to be
Input Lock (Y/N): N O/L YEL: 4.0 edited.
>>PgDn for Interval Colors<<
Figure 288 – Fire Run Setup screen
* st
Loading an overall Default from the 1 Preempt menu will clear Quick Setup defaults back to “None.”

The default option values are same for Fire Run or RR as shown above.
The first screen is the Fire run or RR set-up screen. The options provided are those
typically needed for a basic fire run. Note that all quick set-up data parameters are the
same as detailed data base values, just presented differently. Once loaded they can
be accessed from detail menus.
The following definitions are essentially the same as in the detailed mode but are
repeated here for convenience.
Run Enable (Y/N)

This option must be set to ‘N’ to program the run, and back to ‘Y’ to allow the run to
execute when activated by input. Its purpose is so that a run does not attempt to
execute when only “half” programmed.
Gap (Duration) Time (0-255 secs)

This value acts much like a phase passage timer but for the preempt input. It is useful
for a preempt signal that is intended to be steady but may be intermittent. Note that
this timer is called the “Duration” timer in the detailed menu and has option to serve
as gap timer. The gap option is set to “Y” by Quick Setup defaults. The timer can be
set back to duration mode in menu 2 under Per Run Data of the detailed preempt
section. In this mode, the value determines the overall duration of the preempt run
from activation of the input to exit.
Priority 1-6
This value determines the priority of the preempt run, where 1 is highest and 6 is
lowest. Used when there is more than 1 preempt run and it desired to prioritize them.
Set them all the same if a 1st-come-1st serve operation is desired. The Quick Setup
defaults set these to 1 for all RR runs and 2 for all fire runs.
Delay Before Preempt (0-255 secs)

This parameter will delay the entry into preemption by the programmed amount. If the
preempt call goes away before the delay time has passed, the run will not be serviced
unless the call is locked. This timer is concurrent with the re-service timer (see
below). If a preempt input becomes active before the delay time and the re-service
time have expired, the call will not be serviced until both timers have reached zero.
Re-Service Time (0-255 secs)

Occasionally it is desired to prohibit re-entry into a previously served fire run preempt
for a certain time. The re-service timer will begin upon activation of each preempt
input. If a preempt input becomes active while the re-service timer is still timing from a
previous service, the call will be ignored until the timer expires. If the input is still
active when the timer times out, it will be serviced at that time. Re-service time is
ignored by RR preempt.
Input Lock (Y/N)

This parameter is mainly used when delay before preempt is used (see delay
description). If enabled (Y), the preempt call is retained in memory through the delay
until the run is activated—even after the input is gone,. This mode might be used for

something like a fire house pushbutton where the run is called for, but delayed for a
period after the button is pushed. When lock is not enabled (N), the input must still be
present when the Delay Timer has timed out for the run to be activated. This mode
might be used with a ramp spill back detector at the top of the ramp where a steady
active input throughout the delay period is an indication that the ramp is backed up
(presence detector, input stays active when vehicles are not moving).
PCL-YEL (Ped Clearance Through Yellow)

When enabled (Y) the Ped Clearance interval is allowed to extend through the Yellow
interval (don’t walk flashes through yellow). Note that this is independent of the
programming in the Phase Functions screen, i.e. it is possible to flash don’t walk
through yellow upon entry into preemption but not normally.
Caution Caution should be exercised when using this feature since pedestrians will
see a shorter solid don’t walk period before the opposing green occurs. It is
not recommended unless absolutely necessary—which is not usually the
case for a fire run.
Entry GRN, YEL, RED, PCL (0-25.5 secs, except PCL, which is 0-255 secs)
These values are used to insure that a certain amount of time is timed for the various
intervals before proceeding with the preempt run. This is to prevent the situation
where a run becomes active soon after a phase turns green (for example), causing a
short green time. Note that the times entered here override normal times. For
example the normal initial time (minimum green) value for a phase might be 10
seconds, but if the preempt run green value is 5 seconds, then the green can
terminate after 5 seconds for entry into the preempt run.
O/L YEL
Provides a yellow duration time for overlaps should an overlap be forced to clear
independently of its parent phase and must time its own yellow.

Fire Run Interval Screen

The fire run interval screen is a single screen that provides for phase and overlap
color designations plus interval timing.
Page down from page 1 of the Quick Set-Up Procedure For Fire Run 1
Interval Time (0-255 sec) — This is a minimum

value, the interval will hold on preempt input until
it goes away.
Fire Run 1 Intvl Time: 43|1 1 1 1 1 1 1

FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 For many runs, simply
Ph Col G G changing the ph
Ped Col greens (if not 2 & 6)
VO/L Col will complete the
PO/L Col Quick Setup program.
PE Out X
Col Val, 0=R/Dw 1=Y/PCL 2=G/W PE Out=Y/N
Q setup default sets PE out to

1 for run 1, 2 for run 2, etc.
Figure 289 – Fire Run Interval screen
The default interval values for Fire Run are as shown above (10 sec, phases 2 and
6.)
The interval time determines the minimum length green of the hold phase. If the run is
a hold-on-input type then this value is fairly short, 5 -12 seconds or so because the
input will hold the phase longer if needed. If the run is a pulse-and-time like a fire
house push-button, this value provides the full green time.
The go-to phases and overlaps are specified by loading 2’s (greens only). Once the
hold phase is achieved it re-mains there for the interval time value or until the input
goes away. This preempt scheme can also be used for any go-to-phase & hold
preempt—like a ramp clearance.
Specify any Preempt outputs by loading Y’s (appears as ‘X’) under desired outputs 1-
16. The Quick Setup default load procedure sets PE out 1 for run 1, 2 for run 2, etc.

Railroad Run Interval Screens

The Railroad Run consists of up to 7 intervals, with at least 4 typically used. The
intervals are very specific in their order and intent. Upon activation of the RR input,
Quick Set-up RR will first preempt to a track clear green, then yellow, then red. These
are defaulted to “Fixed” intervals by the Set Run x Detail To RR Defaults option. The
track clearance intervals are then followed by up to 4 more “cyclic” intervals,
designated A-D. Cyclic intervals basically mean that the unit will cycle between the
phases specified within the intervals based on normal demand. One or all of these
cyclic intervals may be used.
PGDN from RR set up screen:
Fixed Interval Time (0-255 sec)
R1 Track Clr Grn Time: 103|1 1 1 1 1 1 1

FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 Change track clear
Ph Col G G greens as desired
Ped Col by entering greens
VO/L Col and deleting the
PO/L Col default values (if
PE Out X not 4 and 7).
Q setup default sets PE out

1 for run 1, 2 for run 2, etc.
Figure 290 – Railroad Run Interval screen
The first interval is the track clear green interval. Specify the time and the phase
colors (usually 2’s for greens). Also specify any ped, overlap, and ped overlap colors.
Activate PE outs 1-16 by programming ‘Y’s in the appropriate columns. Note that the
time is 0-255 seconds for the track clear green time (this can be changed in the
detailed mode).

PGDN
The 2nd interval is the track clear yellow interval. Similar to track clear green
except specify yellows (1’s). Note that time is 0-25.5 seconds for the track clear
yellow.
Fixed Interval Time (0-25.5 sec)
R1 Track Clr Yel Time: 4.0|1 1 1 1 1 1 1

FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
Ph Col Y Y Change track clear
Ped Col yellows as desired by
VO/L Col entering yellows and
PO/L Col deleting the default
PE Out X values (if not 4 & 7).
Figure 291 – Railroad Run Interval screen - second interval
The third interval is the track clear red interval. Similar to track clear green &
yellow except specify reds, which usually means doing nothing since they are likely
already red, (0 = red, which appears as blank on the screen). Note also that time is 0-
25.5 seconds for the track clear red.
Fixed Interval Time (0-25.5 sec)
R1 Track Clr Red Time: 5.3|1 1 1 1 1 1 1

FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
All red interval is
Ph Col already set up
Ped Col (blanks = red).
VO/L Col Adjust time if
PO/L Col necessary
PE Out (0-25.5 secs).
Figure 292 – Railroad Run Interval screen - third interval

PGDN ...
Note: For cyclic group phases, an interval
Interval Time (0-255 sec) time of “0” means use normal phase max
times. Values of 1-255 become the max time
for all phases in this group.
R1 Cyclic Grp A Time: 0|1 1 1 1 1 1 1

FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
Ph Col G G
Ped Col
VO/L Col
PO/L Col
PE Out
Figure 293 – R1 Cyclic Group A Time screen
PGDN etc. for groups B through D
The 4th through 7th intervals are cyclical intervals. Up to 4 groups of phases can
cycle after the track clear phases by specifying phases within these groups. For each
group, specify only greens of a phase or compatible phase set, plus overlaps . Use
groups A-D only as needed until all phases to be allowed are specified. The unit will
cycle phases with calls from all groups until preempt ends.
If the time value used is 0, the phases use their own max times. If the value is other
than 0, that value becomes the max time (during preempt) for all phases enabled by
the interval.
Important The memory space allocated for intervals in the 3000 is determined by the
max intervals setting in the preempt per run detail menu. This value is
defaulted to 7 for both Fire and RR quick setup procedures. If this value is
changed it can affect higher numbered preempts. For example, if the Max
intervals of run 1 is changed, then runs 2-5 will be affected and will require
re-programming.
Thus, if run 1 is requires detail menu programming, and the max number
of intervals is subsequently changed, then runs 2-6 (if used) will have to be
re-entered. Because there is a greater chance that the max intervals may
change, it is best to make any detail menu run a higher numbered run (if
possible). For example, if there are to be two Quick setup runs and one
Detailed Menu run, make the Quick setup runs 1 and 2 and make the
detailed run 3 or higher.

PLACING A MANUAL PREEMPTION CALL

There is a way to place a preemption call to the controller using the front panel
interface, although the method used to do this was changed slightly with the v3.6.2
release of the controller firmware. A manual preemption call can be placed from any
of the Dynamic Preemption Status screens.
1. First, go to one of the Dynamic Preemption Status Screens by either a)
switching to the Main Dynamic Status screen and paging down the list to the
bottom where the three preemption status screens are located, or more
directly, by b) navigating to the Dynamic Status Menu and selecting the
Preemption screen option (MM > 1.Dynamic Displays > 4.Preempt Function.)
2. To place the preemption call, press the shift button and the number of the
preemption run you wish to call. For instance, to call run 4, press SHIFT -4.
3. To clear the all preemption call, press the clear button on any of the three
Dynamic Preemption Status screens. Note that the keyboard call will clear, but
the memory of the call will not clear unless the PE Input Lock setting in the
runs ‘Per Run’ settings is set to NO.
The fact that the controller recognized the call can be seen in two places in the three
preemption screens, although the call can be input on any of the three. The first
indication is on the first of the Preemption Status screens, where the call will appear
in the QUEUE: field. This example shows that a call has been place for run 1.
PG 1 ACTIVE RUN 1 DURATION TIMER 15.4

INTERVAL 1 INTERVAL TIMER: 4.5
QUEUE: 1 1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
PED HEAD D W D D D W D D
Call placed for
VOL HEAD R R R R R R R R
preemption run 1
POL HEAD D D D D D D D D
Figure 294 – A keyboard-entered call for preemption run 1
The second place where the keyboard-placed preemption call is indicated is on the
third of the three preemption status screens: a ‘K’ indicates a call for a particular run,
and an ‘M’ indicates a call-in-memory. The full range of values available in the INPUT
setting on this screen are described in Table 23 on page 60.
PG 3 RUN 1 2 3 4 5 6
INPUT K D D D D
PRIORITY 2 1 3 4 5 6
RECOGN TMR 0 0 0 0 0 0
DELAY TMR 0 0 0 0 0 0 Call placed for
RESERVE TMR 0 0 0 0 0 0 preemption run 1
EXTEND TMR 0 0 0 0 0 0
FAIL TIMER IN SECONDS: 0
Figure 295 – Preemption Status screen showing keyboard call on run 1

Examples of Preemption Programming
EXAMPLES OF PREEMPTION PROGRAMMING

Example 1: 2 phases with typical fire runs activated by steady input during run
Goal: Preempt run 1 goes to phase 1 and holds (dwell) until the preempt input goes
away, then returns to phase 2. Preempt run 2 goes to phase 2 and holds (dwell) until
the preempt input goes away, then returns to phase 1. Typically activated by a fire
truck equipped with a transmitting signal that issues the calls.
φ2
Fire run 1 phase.
φ1
φ1
φ2 Fire run 2 phase.
Figure 296 – Example preemption with typical fire runs
To Implement Example 1
1. Go to Run 1, Per Run Data menu, selection 1.
a.) Set Run enable to ‘N’ to allow preempt programming. It will be set back to ‘Y’
after all PE programming is complete and the run is ready for testing.
Set to ‘N’ to program PE

Set back to ‘Y’ to run PE
Run 1 Options, Page Down for more

This will be set
Run Enable: N Override FLASH: N to ‘Y’ in example
2A & 2B.
Railroad: N Go To Higher PE: N
PE Input Lock: N NEMA Priority: N
Early PE Out: N Hold Only: N
Only 1 interval required for this preempt run
Figure 297 – Preemption Example 1 - Disabling run
b.) Complete programming on this screen similar to the example above, in this
case set Max intervals and priority to 1, everything else to N.

2. Go to Per Run Data menu, selection 2. Per Run Times. Program it as

required, similar to the example below.
Duration timer used as gap timer. Useful in case

signal from the truck is slightly intermittent.
Run 1 Time

Delay Time: 0 secs
Set to ‘Y’ to enable
gap mode.
Figure 298 –Preemption Example 1 - Setting duration timer
The gap timer mode is used in case the signal from the truck is lost
momentarily and then re-appears within 5 seconds. Without this timer, a briefly
lost signal would cause the unit to exit preemption and start over.
3. Go to Per Run Data menu, selection 3, Entry Parameters. The screen below
has typical entry time values.

Red Revert Override: N Typical Entry times

Walk: 0 Red: 2.0
Figure 299 –Preemption Example 1 - Setting entry times
Note Per Run Data menu, selection 4 will be skipped. This menu is not
required because all Interval related data will be programmed in the
Per Interval menu. This menu is, however, useful later for viewing
and editing after the runs have been programmed.

4. Go to Per Run Data menu, selection 5, Exit Parameters. Program as required,

similar to the example below.
Exit to specific phase mode
Run 1 Exit Controls

Exit Mode: 0 = Go to the Exit Phases
(0 - 3) 1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
Phases X
Veh Call
Ped Call
Exit to phase 2
Figure 300 –Preemption Example 1 - Setting exit controls
5. Go back to the Preemption Run Menu and choose Interval Data. Program as
required, similar to the example below.
Identifies interval as valid (used) Identifies interval as
Dwell, which means
Can exit from this interval it holds here until
the PE input goes
Run 1 Interval 1 Valid: X Dwell: X away.
Tenths: X PC-Yel: Exit: X Fixed:
Time: 10.0 Ph Flash: 0 Ped Flash: 0 Fixed mode not
VALUE (0=R/D, 1=Y/P, 2=G/W) 1 1 1 1 1 1 1 enabled. When in
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 fixed mode, acts
Color G like a pre-timed
Ped Col unit. Yellow and red
intervals must then
PgDn for Overlaps
be provided as well
as green.
Phase 1 green is the dwell (hold) phase.
If this were an 8 phase quad, compatible
phases such as ph 1 & 5 or 1& 6 could be
green as well. Reds are implied by blanks
(default state).
Figure 301 –Preemption Example 1 - Setting interval data
Note If preemption outputs are required for this interval, page down twice from
the above screen and set desired output(s) on.
6. Since there are no overlaps or PE outputs to program, and this run requires no
flash plans, programming of run 1 is now complete. To complete run 2 for
phase 2, follow the same procedure as for run 1 only with phase 2 as the hold
phase and 1 as the exit phase. After all runs are complete, go back to Per
Run Data menu, selection 1 for each run and set Run Enable back to ‘Y’ to
allow the preemption run to operate. The runs are ready for testing.

Example 2: RR track clearance with 2 fire runs. Cycle 2&5, 2&6 after track clear.
Goals:
Fire run 1 is: Go to phase 2 and 6 and hold (dwell) until the preemption input
goes away.
Fire run 2 is: Go to phase 3 and hold (dwell) until the preemption input goes
away.
The RR run is:
Go to phase 4 for track clearance period of 14 seconds (ph 4 only used
during RR PE). Phase 4 is set up as a “dummy” phase, meaning it is
programmed in the sequence with at least Initial, Yellow, and Red times. It
is not placed on recall and not assigned to any real detectors. Vehicle Omit
is applied to it, so it is only called for and served during RR preemption. It
will not come on during either the start-up routine or normal operation.
After track clear, cycle 2 & 5, then 2 & 6 if calls (cyclic). These are phases
that don’t cross the track. Cyclic phases continue as long as train calls for
Preempt.
Exit RR run in phase 3 green after RR input goes away.
Note RR preemption will override any fire run.
φ3
-Run 1 is a fire run, phases 2 & 6
-Run 2 is a fire run, phase 3
-Run 3 is RR w/track clear
φ6
φ5 φ1
φ2
Phase 4 for RR preempt only.
O/L A (3+4) Normally uses only phase 3
with a double clear overlap.
φ3
Figure 302 – Preemption Example 2 - Fire runs and railroad crossing

To Implement Example 2, Fire Runs:

Follow the procedure used in example 1, with these changes:
From Per Run Menu selection 1, change Go To Higher PE to ‘Y’ for both and
change User Priority to ‘2’. This will allow fire runs to be overridden by the RR
crossing (fire trucks can stop, trains can’t).
From Per Run, Exit Controls menu, change the exit phase mode for both to
Next Demand. Phases need not be specified.
From the Interval Data menu, change the phase colors appropriately for each
fire run; phases 2 & 6 Green for run 1 and phase 3 Green for run 2. Be sure to
page down to the overlaps portion of the interval for run 2 and add O/L A green.
1. Go to Per Run Data menu, selection 1.

a.) Set Run enable to ‘N’ to allow preempt programming. It will be set back to ‘Y’
after all PE programming is complete and the run is ready for testing.
Set to ‘N’ to program PE

Set back to ‘Y’ to run PE
‘Y’ sets up
Run 3 Options, Page Down for more input response
for railroad.
Run Enable: N Override FLASH: N
Railroad: Y Go To Higher PE: N
PE Input Lock: N NEMA Priority: N
Early PE Out: N Hold Only: N
5 intervals required for this preempt

run. This value will be set to 4 in
example 2A.
Figure 303 –Preemption Example 2 - Setting run parameters
b.) Complete programming on this screen similar to the example above.

2. Go to the Per Run Data menu, and selection option 2. Per Run Times.
Program as required:
Duration timer used as standard duration

timer for RR. Remains in RR PE for a
minimum of 40 seconds.
Run 3 Time

Delay Time: 0 secs
Set to ‘Y’ to enable
gap mode.
Figure 304 –Preemption Example 2 - Setting run times
3. Go to Per Run Data menu, selection 2, Entry Times. The screen below has
typical entry time values (same as fire runs).

Red Revert Override: N Typical Entry times

Walk: 0 Red: 2.0
Figure 305 –Preemption Example 2 - Setting entry times
Note Per Run Data menu, selection 4 will be skipped. This menu is not required
because all Interval related data will be programmed on the Preemption
Run Menu > Per Interval menu. However, this command here on the Per
Run Data menu is useful later for editing after the runs have been
programmed.

4. Go to the Per Run Data menu and choose selection 5. Exit Parameters.
Program as required, as shown in the example below.
Exit to specific phase mode
Run 3 Exit Controls

Exit Mode: 0 = Go to the Exit Phases
(0 - 3) 1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
Phases X
Veh Call
Ped Call
The RR run exits to phase 3

Figure 306 –Preemption Example 2 - Setting exit controls
5. Go back to the Preemption Run Menu and select Interval Data. This
programming is going to be more extensive than the fire runs because there
are more intervals and an overlap is involved. Keep Paging down to get from
one screen to the next (there are 3 screens per interval).
a.) Example 2, Interval 1 - Track clear green
Identifies interval as valid (used).

Note that all intervals in the
examples are ‘Valid.”
Not a dwell interval
Cannot exit from this interval
Run 3 Interval 1 Valid: X Dwell: Fixed mode

Tenths: X PC-Yel: Exit: Fixed: X enabled. When in
Time: 14.0 Ph Flash: 0 Ped Flash: 0 fixed mode, runs
VALUE (0-R/D, 1=Y/P, 2=G/W) 1 1 1 1 1 1 1 like pre-timed unit.
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 Yellow and red
Color G intervals must then
Ped Col be provided as well
as green.
PgDn for Overlaps
Enter a 2 here and press ENTER . (It will turn

into a G.) Phase 4 green is the fixed interval
phase. This is actually a dummy phase used to
get overlap A only to be green. Phase 4
outputs aren’t actually used, but it needs to be
specified for the control logic.
14 seconds interval duration

(track clear time).
Figure 307 –Preemption Example 2 - Interval 1 phase colors

Page down to the Interval 1 overlap settings.

Tenths: X PC-Yel: Exit: Fixed: X
Time: 14.0 OL Flash: 0 Ped Flash: 0
VALUE(0-R/D, 1=Y/P, 2=G/W)
Color G
Ped Col
PgDn for PE Outs
O/L A green is specified. All other control

parameters remain as set on the first page above.
Figure 308 –Preemption Example 2 - Interval 1 overlap colors

Page down again to set PE OUTS, should any be required for this interval.
Page down again to program interval 2.
b.) Example 2, Interval 2 - Track clear yellow.
Time: 4.0 Ph Flash: 0 Ped Flash: 0
VALUE (0-R/D, 1=Y/P, 2=G/W) 1 1 1 1 1 1 1
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
Color Y
Ped Col
PgDn for Overlaps
Phase 4 yellow
4 second interval duration

Color Y
Ped Col
O/L A yellow
PgDn for PE Outs

c.) Example 2, Interval 3 - Track clear red.

VALUE(0=R/D, 1=Y/P, 2=G/W) 1 1 1 1 1 1 1
FUNC\OL 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
Color
Ped Col
PgDn for Overlaps
Phase 4 red (blank = red)
2 seconds interval duration

Color
Ped Col
PgDn for PE Outs
O/L A red (blank = red). Note that no programming

should be required for this screen since the controls
were set in the 1st screen and the color defaults are
already red.

d.) Example 2, Interval 4 - Cyclic, phases 2 & 5.

Can exit from this interval Not Dwell and not
Fixed makes this a
RUN 3 INTERVAL 4 VALID: X DWELL: Cyclic interval. This
TENTHS:X PC-YEL: EXIT: X FIXED: means when this
TIME: 0.0 PH FLASH: 0 PED FLASH: 0 interval is active, it
VALUE (0-R/D, 1=Y/P, 2=G/W) 1 1 1 1 1 1 1 cycles selected
FUNC\PH 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 phases normally with
COLOR G G their own timings if
PED COL they have demand.
PgDn FOR OVERLAPS
Phases 2 and 5 are the compatible

phase pair for this cyclic interval.
Time set to 0 for the cyclic interval
indicates that phases use their own max
times. A non-zero value loaded here
becomes the max time for all cyclic
phases in this interval.
Since this cyclic interval does not involve an overlap green, no programming
is required on the second and third pages of this interval other than to check
that the red (blank) defaults are indeed in place.
e.) Example 2, Interval 5 - Cyclic, phases 2 and 6
Tenths: X PC-Yel: Exit: X Fixed:
VALUE(0=R/D, 1=Y/P, 2=G/W) 1 1 1 1 1 1 1
FUNC\OL 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
Color G G
Ped Col
PgDn for Overlaps
Phases 2 and 6 are the compatible phase pair

for this cyclic interval.
The unit will cycle amongst phases associated with cyclic intervals 4 and 5
(if they have demand) until the RR PE input goes away. The unit will then
exit to phase 3.
6. Programming of all runs is now complete. Go back to the Per Run Data menu,
and choose selection 1 for each run and set Run Enable back to ‘Y’ to allow
the preemption run to operate. These runs are ready for testing.

Example 3: RR track clearance with two fire runs. Flash all red after track clear.
This is the same as Example 2, with the following changes:

After track clear, go to all red flashing dwell operation. Phases 1 and 5 will go
dark.
Exit RR flash to phase 3 green after an all fixed red interval.
Example 3, Interval 4 - Flash interval (Dwell in Red)

Not dwell, not
Can exit from this interval
fixed = cyclic
interval. A Cyclic
Run 3 Interval 4 Valid: X Dwell: interval is chosen
Tenths: X PC-Yel: Exit: X Fixed: in this case
Time: 10.0 Ph Flash: 1 Ped Flash: 0 because the unit
VALUE(0=R/D, 1=Y/P, 2=G/W) 1 1 1 1 1 1 1 can exit directly
FUNC\OL 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 from this interval
(controller
Color
automatically
Ped Col
provides
PgDn for Overlaps clearances).
Flash plan 1 will define
flashing phases.

The flash colors are determined by this interval, which is all red. The flash plans
will determine the nature of the flashing operation.

Color
Ped Col
PgDn for PE Outs
Flash plan 2 will define
flashing overlaps.
O/L A red will flash (red = blank)

Set-up flash plans. Go to the Flash Plan for Run 3 Intervals. Since there are two types
of outputs that flash in interval 5, two flash plans will be required; plan 1 for phases
and 2 for overlaps.

Run 3 Flash Plan 1-16 VALUE(0= Normal, 1

= Fl Wig, 2 = Fl Wag, 3=Dark)
(1-16= Ph 1-16 or O/L A-P) 1 1 1 1 1 1 1
Plan\Out 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
1 3 1 2 0 3 1 0 0 0 0 0 0 0 0 0 0
2 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Unused phase are left 0 = normal

since their outputs are not used.
Plan 1 = Phases 1 and 5 go dark, 2 and 6 flashes wig and
3 flashes wag.
Plan 2 = O/L A flashes wag.
Flashing Colors determined by interval 4.
Figure 317 – Preemption Example 3 - Programming the Flash plan

Programming of all runs is now complete. Go back to Per Run Data menu, selection 1
for each run and set Run Enable back to ‘Y’ to allow the preempt run to operate. The
preempt runs are ready for testing.

Chapter 10 — Comm and System Setup
This section explains how to set up communications and other internal parameters in a 3000
Series controller. The following topics are discussed in detail in this chapter:
An overview of the Communication and Setup Menu, on page 346.

Setting the Closed Loop ID, on page 347.
Configuring the communications ports (Ports 1-3), on page 348.
Setting up a modem, on page 354.
Setting the phone numbers the controller will dial, on page 361.
Defining what events trigger a call-in, on page 362
Specify what type of data should be logged, on page 364.
Setting up Speed Trap detectors, on page 364.
To configure Port 1 for use with MMUs or BIUs, refer to page 366.
Setting an NTCIP System Name, on page 370.
Setting an NTCIP Contact Name, on page 371.
Setting HDLC Addresses for Port 2 and 3, on page 372.

OVERVIEW
The Comm and System Setup menu is used to program the communications ports for
various types of interfaces and system uses. It is also used to program phone
numbers, system logging operation, etc. It can be accessed from the Main Menu by
selecting Option 3. Change Data to access the Program Menu, and then selecting
item 5. Comm/System Setup.
Since there are slightly different communications options for TS 1 and TS 2
controllers, the Communications & System Setup Menu appears somewhat differently
for each type of controller. A TS 1 Comm/System Setup menu looks like this:
Communications & System Setup Menu
1.Closed Loop ID 4.Event Call In

2.Comm Setup 5.Log Data
3.Phone Numbers
Figure 318 – Comm/System Setup menu (TS 1)
And a TS 2 controller will display this as the Comm/System Setup menu:
Communications & System Setup Menu
1.Closed Loop ID 6.Port 1 Setup

2.Comm Setup 7.System Name
3.Phone Numbers 8.Contact Name
4.Event Call In 9.HDLC Address
5.Log Data
Figure 319 – Comm/System Setup menu (TS 2)

The usage of each of these menu commands to set up 3000 series communications
is described in the rest of this chapter.

Closed Loop ID
CLOSED LOOP ID
The first item on the Comm/System Setup menu is Closed Loop ID, (MM > 3.Change
Data > 5.Comm/System setup > 1.Closed Loop ID.) This screen allows
programming of the master type and ID as well as the local ID in a closed-loop
system.
Closed Loop Master/ID

Master Type: 0 (0= NONE,
1= 3000 Series Master/2= 3800EL Master)
Intersection ID: 6 (0-255)
Master Identification: 3 (0-255)
UTCS Address: 0 (0-15)

UTCS Protocol: None
Figure 320 – Closed Loop Master/ID Setup screen
Master Type — The master type needs to be specified because a 3800EL master
uses a different communications protocol than an M3000 master.
Intersection ID — The intersection ID is the number by which this controller is to be
known to its master. The master ID is the number of the master that controls this unit.
Master Identification — Smartways® and CLMATS both require every controller to
®
have a Master Identification number regardless of whether or not an actual master is

connected to the 3000 Controller.
UTCS Address/Protocol — Two parameters were added to this screen in the v3.6.6
3000/E firmware that support the UTCS central system protocol. When the UTCS
Protocol value is set to something other than None, it remaps the controller’s inputs
and outputs, and activates the corresponding protocol handler. This value survives a
default data load and also a ‘Startup Menu-Home’ command. It resides in flash
memory (and is thus not dependent on battery-backed RAM). The 0(Y/N) key can be
used to toggle the UTCS Protocol value setting to the desired setting. The UTCS
Protocol value will also be used to determine which version of the display will appear
when you navigate to the UTCS Dynamic Display screen. (Refer to page 78.)
Important However, if you are not using a UTCS Central System, the UTCS
Protocol parameter must be set to None. Neither CLMATS nor
IQ Central currently support this protocol. The value of the two UTCS
settings in the controller’s memory is maintained when uploading and
downloading from these other central software systems.
Note At one point, this screen had an additional command that enabled transferring
data between ports 2 and 3. This function is still available, however since it had
nothing to do with setting up the Closed Loop ID or other identification
parameters, it has been moved over to the Comms Setup screen (MM >
3.Change Data > 5.Comm/System setup > 2.Comm Setup) and is now called
“Comm copy”. (See page 348.)

COMM SETUP
The second item on the Comm/System Setup menu is Comm Setup, and as the
name might suggest, it allows the operator to specify the parameters of the 3000
series controller’s various communications ports. It can be accessed by navigating
from the Main Menu along this path: MM > 3.Change Data > 5.Comm/System setup
> 2.Comm Setup.
With the release of 3000 series firmware v3.6, the Comm Port Setup screens were
reorganized so that the parameters are easier to understand and use. Previously,
when one entered the Comm Setup Screens, the controller presented four setup
screens (accessible by paging down.) The first of these was a screen where the
Master Port, Monitor Port, and Central Port were assigned. This screen has been
removed. Now, the controller goes straight to the Comm Port 2 Setup screen. Paging
down now takes you to the Port 3 setup screen, the modem string setup screen, and
the Ethernet port settings (but this last screen only appears if Port 3 is assigned to
have Ethernet hardware.)
Removed Printer Comm Port Settings

A confusing aspect of communications setup in the 3000 Series controllers prior to
the version 3.6 firmware was the fact that comm settings were stored in multiple
locations, depending on the intended use. The best example of this were the
communications settings on the Utilities > Printer Menu, where option 1 allowed one
to set communications settings for a serial printer attached to Ports 2 or 3. This
screen has been removed. Although the option is still there, selecting it now shows a
help window that explains the change.
Instead, a printer will now use the communications settings that are assigned to
whichever port it is plugged into, as configured on the normal Comm Setup screen.
(Main Menu > 3 > 5 > 2).
Assigning a Central Port

The Port Type settings on the Setup Comm Port 2 and Setup Comm Port 3 screens
define which port is used for an isolated controller link (i.e. no Master is being used)
to the central computer. This is typically either port 2 using an EIA-232 connection to
a dial-up modem or port 3 using an Ethernet connection. If the controller has an event
logging monitor (ELRA, ELRB or Double Diamond), then an AUX EIA-232 port can be
substituted in the port 3 position to be used for the dial-up modem, while port 2 is
used for the logging monitor connection.
Assigning a Master Port

define which port is used to connect to the closed loop system master. This is
typically port 3 and, depending on the hardware module inserted, can be an FSK
modem (wires), a Fiber Optic port, an Ethernet port, or an EIA-232 connection to an
external modem.

Comm Setup
Assigning a Monitor Port

define which port is used to connect to the event logging monitor for purposes of
uploading event log information. This is typically port 2 and usually applies to TS 1
monitors like the ELRA or ELRB or the Double Diamond MMU in TS 1 mode, or with
Port 1 disabled. This information can be transferred via Port 1 for TS 2 mode Double
Diamond MMU’s in cabinets with Port 1 capability. In this case, neither port would be
set to Monitor. If there is no Port 1, however, the DD MMU can be connected in the
same manner as an ELRA or ELRB using the standard monitor port assignment and
an EIA-232 connection.
Setting Up Comm Port 2

Whenever Port 2 on the front of the 3000 Series controller is accessed, these settings
are used. Use the arrow keys to navigate, and the Y / N key to change the value for a
parameter.
Setup comm PORT 2
Port type : None Baudrate : 19200

Hardware : Normal Data bits : 8
Comm Copy : No Parity : No
RTS-> CTS : 00ms
PgDn for more comm setup

Figure 321 – Comm Port 2 Setup screen
Port type – This setting is only used by the controller when it is set to ‘Monitor’,
indicating that an intersection monitor is connected via this port. Note that this setting
also allows a monitor to be connected via a modem (if anyone should desire to do
so.)
Hardware – This tells the controller what type of hardware is attached to this port: It
can be set to either an ‘AT Modem’ (i.e. a ‘Hayes compatible’ modem), ‘Normal’ or
‘Ethernet’. (Port 2 does not have the ‘Ethernet’ option.)
Table 44 – Proper ‘Hardware’ settings for various Port 2 and Port 3 devices
Port card or hardware Proper ‘Hardware’ Setting
RS232 (direct connect) Normal
RS232 (with external modem) AT Modem
Serial/Ethernet combo card Ethernet
Fiber Normal
FSK Modem Normal
Comm Copy – This setting replaces the parameter that was formerly located in the
Closed Loop Master/ID screen and called ‘Allow Comm Transfer Between Ports 2&3’.
What this command does is tell the controller to echo the input on this port to the
other port. (This works for data input to either port.) Although this setting appears on

both the Port 2 and Port 3 screens, there is only a single value for this parameter in
the database. So setting this value to Y or N on one port automatically sets it to the
same value on the other port screen.
When enabled (‘Y’), this function allows ports 2 and 3 to act in a “repeater” mode. The
repeated port depends on which port has been selected as the Master port as defined
by the Port Type setting on the two screens.
If port 3 is the Master port then port 2 repeats (echo’s) the signal coming in on port 3.
If port 2 is the Master port then port 3 repeats (echo’s) the signal coming in on port 2.
RTS->CTS – This parameter has been added to assist older communications
equipment such as older radio modems and the Peek DSP modem. Some of these
modems require a short, but significant, amount of time after a Request-to-Send
(RTS) signal is asserted by the controller before they are ready to transmit.
Previously, the 3000E asserted RTS and began transmitting data immediately. This
RTS->CTS delay time tells the controller to wait a defined number of milliseconds
before assuming the comm device is ready. This parameter can be set to any value
between 0 and 99 milliseconds. The default value is 0ms. A typical usage of this
feature is when the 3000E is connected to an older radio-modem that requires
approximately 15ms to get up and running when activated from a resting state, and
which has no input buffering. The typical entry in these situations would be a value
between 20 and 30ms, to ensure that the controller doesn’t begin transmitting data
before the modem is ready to pass it along. (Another possible use for this feature is to
allow a DSP modem to transmit at 9600 baud when using the 3.6.x generation of
3000 series firmware.)
Baudrate – Sets the data transfer speed for this port. To change the baud rate, move
the cursor to the appropriate line, and press the Y/N key to advance to the next higher
data rate. When the maximum rate is reached it will ‘roll over’ to the minimum rate.
The firmware will accept values of : 1200, 2400, 4800, 9600, 14400, 19200, 38400,
57600, and 115200 baud. (But the selected rate can only be achieved if the device
attached to this port can also communicate at this speed.) This parameter is not
displayed if Hardware is set to Ethernet.
Data bits – The number of bits per byte. (Can be either 7 or 8.) This parameter is not
displayed if Hardware is set to Ethernet.
Parity – The type of parity check used on bytes to verify that no bit-level changes
have occurred during transmission. (Even, Odd, or No parity check). This parameter
is not displayed if Hardware is set to Ethernet.
Note The only time Even parity and 7 data bits is used is when the controller is installed
in a closed loop system with a 3800EL Master or EL series event logging monitors.
Otherwise, select no parity, 8 data bits and the fastest data rate that the
communication medium can handle.
Pressing PGDN from this screen will allow you to set the same parameters for Comm
Port 3.

Comm Setup
Setting Up Comm Port 3

The Setup Comm Port 3 screen is identical to the Port 2 screen, except that there is
an additional Hardware setting: Ethernet. If Hardware is set to Ethernet, the right
column parameters are hidden. (Ethernet forces these values to their fixed Ethernet
values: 115200, 8, No.)
Setup comm PORT 3
Port type : None

Hardware : Ethernet (Fixed IP)
Comm Copy : No
PgDn for more comm setup

Figure 322 – Comm Port 3 Setup screen with Hardware set to “Ethernet”
Paging down yet again will take you to the screen where the modem’s ‘AT’ setup
string is entered.

Setting Up an AT Modem String

In firmware v3.6, this screen was modified to make it easier to enter the desired
string. (Note that the firmware automatically puts an ‘AT’ at the beginning of this
string, so you do not need to enter these letters.)
In systems requiring dial-up function, a setup string must be entered to allow the 3000
to communicate with a modem attached to either port 2 or 3. (The same string is used
for both ports.) Since any number of different modems may be used, the user must
consult their particular modem operator’s manual for the correct character sequence.
(Some hints are provided starting on page 354.)
Setup AT Modem String
AT&F
^
ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789,\%&
Press HELP to display help screen

Figure 323 – Setup Modem String screen
The caret symbol (^) shows where the next character will be added on the third line.
To add a character, move the highlight cursor (within the row showing the alphabet-
symbol listing) to the desired letter using the left and right arrow keys, and then press
ENTER to insert the selected character into the AT string above.
Continue this process until the entire setup string has been entered. It is important to
note that this set-up string will periodically be sent to the modem to ensure that it’s
always ready to communicate with the controller.

Comm Setup
Ethernet Setup
Settings for Ethernet communications are assigned on the next screen if one pages
down from the Setup AT Modem String screen. The Ethernet setup screen that
appears depends on the type of hardware that has been configured on the Setup
comm Port 3 screen (as shown in Figure 323.) If the Hardware setting on the Port 3
screen is set to be either Normal or AT Modem, then no Ethernet Setup screen will
appear. However, if Port 3 is set to Hardware = Ethernet (Fixed IP) or Hardware =
Ethernet (DHCP), then this Ethernet setup screen will appear when one pages down
from the Setup AT Modem String screen.
Ethernet Setup
Local
IP : 10.120. 1. 99 Port : 10001
Mask : 255.255.252. 0
Figure 324 – Ethernet Setup screen

The four segments of the IP address and the Mask address are numbers between 0
and 255, but a valid address and mask setting needs to be supplied by the network
administrator. The same is true of the IP address’s port number. A valid port number
is particularly important in setups that include a firewall, since the firewall must be
configured to allow communications on this port for successful communciations to be
achieved.
If the Port 3 Hardware is set to Ethernet (DHCP), the controller is already attached to
the Ethernet network, and the DHCP server is visible from the controller’s location,
then the fields in the Ethernet Setup screen will be filled in automatically using the
information provided by the DHCP server. If not, then an error will be reported on this
screen until the DHCP server becomes available to the controller, as shown in Figure
325.
Ethernet Setup (error)

Local
IP : ---.---.---.--- Port : 10001
Mask : ---.---.---.---
Figure 325 – Ethernet Setup screen showing DHCP retrieval error

When in Ethernet (DHCP) mode, the fields on this screen cannot be edited. The
information must be provided by the server. If this is not possible, switch to the Fixed
IP version of Ethernet and fill in the correct address and port information.

Additional Notes About Configuring Modems

A modem is usually attached to a 3000 series controller when it will be used in
conjunction with a central software system, such as Peek Traffic’s CLMATS software.
To make this work, you will need a field modem attached to the controller and a
modem attached to (or installed within) the central computer.
1 2 3 HOME PGUP
4 5 6 MENU
7 8 9 END PGDN
CLEAR 0(Y/N) ENTER SHIFT DIS ADS HELP
T
MASTER
R
T
REPEATER
R
RS-485 RS-232 COMM
AUXILIARY
3000E CONTROLLER PREEMPT
GREEN/OK
RED/FAULT COORD
A B C
24VDC
AGC1.0A
AC LINE
MDL 1.25A
Central System
Computer 3000 Series
Controller
Modem (Internal or External) Field Modem

Figure 326 – Modem attached to a 3000 series controller
For the communication to work correctly, the central modem must have the proper
Windows drivers installed on the computer, and the proper initialization string must be
programmed for both modems. The next topics provide some guidance on configuring
these two modems.
Configuring a Peek Traffic LPM336 Field Modem

For long-term reliability, be sure to use environmentally rugged modems in the field.
After the modem is plugged into the 9 pin serial port (typically Port 3) of the 3000
series controller, you will need to set the modem’s initialization string and give the
controller the phone number of the central modem. The former item is described here,
the latter is described on page 361.
The following modem strings have been thoroughly tested and are released for use
with the Peek LPM336 Modem:
When the modem is attached to a 3000 or 3000E Series Isolated Controller, use:
&FE0W2X0&K0\N2S0=0S7=90&Y0&WO
When the modem is attached to an M3000 or M3000E Series Master, use:
&FE0W2X0&K0\N3S0=1S7=90&Y0&WO

Comm Setup
Configuring Other Types of Field Modems

In the past, a periodic Engineering Change Notice (ECN) issued by Peek Traffic listed
the numerous modem strings that could be used for third party hardware. However,
now we are attempting to generalize the process by listing the requirements of each
controller so that users can develop their own modem strings for use with other types
of modems (beyond the LPM line.)
Modem String Requirements of 3000 Series Devices

An isolated 3000 Series Controller has the following modem initialization
requirements:
1. Restore the factory defaults as a baseline.
2. Echo OFF.
3. Connect message reports modem speed.
4. Disable extended result code.
5. Disable flow control.
6. Error correction should be ON. (It should be OFF if using firmware older than
v3.6.)
7. Auto Answer must be OFF. (It should be ON if using firmware older than v3.6.)
8. Number of seconds to wait for Carrier Detect (CD).
9. Set Non-Volatile Read Only Memory (NVRAM) 0 (Zero) template as default on
power up.
10. Write configuration (modem string) to NVRAM template 0.
11. Modem ignores RTS
Modem String Requirements of M3000 Series Devices

The M3000/M3000E Series Master has the following modem initialization
requirements:
1. Restore the factory defaults as a baseline.
2. Echo off.
3. Connect message reports modem speed.
4. Disable extended result code.
5. Disable flow control.
6. Enable error correction.
7. Auto Answer on the first ring.
8. Number of seconds to wait for Carrier Detect (CD).
9. Set Non-Volatile Read Only Memory (NVRAM) 0 (Zero) template as default on
power up.
10. Write configuration (modem string) to NVRAM template 0.

Obtaining the Proper Init Strings for Your Modem

Every manufacturers modem use slightly different variations of the standard AT
command sets. AT commands are simple ASCII text codes sent to a standard
modem, used to configure it to use a certain set of operating parameters.
The Internet is the most convenient method to look up current AT Command Sets.
Listed below are links to several of the more commonly used modems:
http://www.56k.com
http://www.conexant.com
http://www.ModemHelp.net
http://www.ModemHelp.org
http://www.modemsite.com
http://www.usr.com/home.asp
http://www.zoom.com/ts1/analog/v92conexant.shtml
Computer Manufacturers
Often, the best place to look for modem support is from the manufacturer. Below are
several links to manufacturers' modem support pages:
Acer (http://us.acer.com/)
Alienware (http://www.alienware.com/)
Averatec (http://www.averatec.com/)
Compaq Computers (http://www.compaq.com)
Dell Computers (http://www.dell.com)
eMachines (http://www.emachines.com/)
Gateway Computers (http://www.gateway.com)
HP Computers (http://www.hp.com)
Sony Computers (http://www.ita.sel.sony.com/support/)
Retail Modem Manufacturers Using Conexant Modem Chipset

ActionTec (http://www.actiontec.com)
Best Data (http://www.bestdata.com)
Broadxent (http://www.broadxent.com)
Creative (http://www.creative.com/)
Diamond/SonicBlue/Supra (http://www.diamondmm.com)
U.S. Robotics (http://www.usr.com/home.asp )
Zoom Telephonics (http://www.zoom.com)

Comm Setup
Example – GDI Model SM336SA Modem for the M3000 Series

Following the Peek Traffic guideline of using ruggedized modems, the following string
was developed for the General Devices & Instruments, Inc. (GDI) Model SM336SA,
33.6 K Smart Modem Standalone for an M3000E Master. Each of the M3000 Series
modem command requirements (listed on page 355) were found in the GDI
SM336SA User’s Manual, Rev. B (in the AT Command section which starts on Page
7 of that document.)
&F .............reset to factory template 0.

Q0 ..............enable result codes to be sent.
&C1 ...........causes the Data Carrier Detect to reflect the remote carrier status.
&D2 ...........when the Data Terminal Ready goes from an ON state to OFF the modem
changes to on-hook, disables auto-answer, and ends in the command state.
M0 .............disables modem speaker. Use M1 to enable modem speaker.
V1 ..............result codes returned by the modem in verbose (words).
E0...............do not echo commands sent to modem while in the command state.
S0=1...........set modem to answer an incoming call.
S7=90.........modem waits for carrier detect for 90 seconds before hanging up.
&Y0 ...........use NVRAM* profile 0 upon power up. *NON-VOLATILE RANDOM
ACCESS MEMORY.
&W0 ..........save command characters to NVRAM profile 0.
When you combine the above AT Commands into a single command, it forms the
correct modem string for a GDI SM336SA modem to work with a Peek
M3000/M3000E Master. The full string is:
&FQ0&C1&D2M0V1E0S0=1S7=90&Y0&W0
Sending the Modem String from the Controller to the Modem.

The 3000 Series controllers have an embedded feature to load and send the
initialization string to the modem. These steps describe how to do it:
1. Select 3 . C H AN G E D AT E > 5 . C O M M / S Y S T E M S E T - U P >
2 . C O M M S E T U P and then P G D N twice.
2. The modem setup string screen will appear. Read the entire screen carefully.
3. To edit the modem string, use the Left and Right Arrow keys on the keypad to
move the Cursor to the Character you would like to add to the AT string. (The
AT is already entered for you when you get to this screen.) Highlight the
character you would like to add to the field and press ENTER.
4. Repeat the process until you have the entire string entered. Check your work.
It is easy to make a mistake.
5. When the string is complete and correct, make sure the modem is properly
connected to the master or controller, and is powered and turned on. Make
note of the port number where the modem is connected.
6. If the modem is attached to Port 2, press the SHIFT and 2 buttons
simultaneously. This sends the string to the modem via Port 2. If the modem is

attached to Port 3, press the SHIFT and 3 buttons simultaneously. This sends
the string to the modem via Port 3.
Note Since all modems have a limited amount of memory space available in their
NVRAM, it is recommended that once the correct modem string is loaded
into Profile 0, the modem string in the Controller can then be changed to
ATZ. ATZ will cause the modem to read the string in Profile 0, and not
rewrite this string to this limited memory space repeatedly. Some AT
command sets like those in US Robotics Modems use Z 1 = profile 0 and
Z 2 = profile 1.
Troubleshooting a Field Modem Setup

After you have installed the modem that is attached to the Master or Isolated
Controller, you should test the connection between your central software and the field
equipment. If you continue to have a problem, you may need to try a different
configuration for the field modem. Try editing the modem file and configuring the
modem again, and then retest. Once you find a successful set of modem parameters
for a particular brand and model of modem, it should be reused. This is an excellent
reason to standardize on a single type of modem for all your UTC Devices.
Some of the following issues may also affect the consistency of your connections:
Bad or noisy phone lines
Bad or intermittent lightning protection on the phone line
Dirty contacts on the phone line connections
Non-environmentally rugged modems used in the field
Improper power to the modem
Modem configured at the wrong baud rate (should be configured at
the same baud rate as the Central Software Computer’s
Communication Port)
Some old-style analog telephone switches (PBXs) may contribute
to noisy phone lines

Comm Setup
Setting Up the Central Modem

The central system software usually used with 3000 series controllers is Peek
Traffic’s CLMATS, or Closed Loop Multi-Arterial Traffic Software. Each Version of
CLMATS is issued with a set of Release Notes (p/n 99-275) listing the most current
modem requirements of the central software. Most recently manufactured computers
are provided with an internally installed modem.
The development and loading of a modem string at the central system computer is
rarely required, as it is done behind the scenes by a driver previously loaded into the
Operating System. However, these steps provide a good procedure to follow so that
one can be clear about what hardware is being used, and that one’s central modem is
properly configured.
Note It is not currently possible to use one of the Peek Low Power (LPM)
Series Modems as an external modem attached to the CLMATS
computer, since no Windows drivers have been developed for these
modems.
1. Examine the documents that accompanied the computer when it was new.
Record the complete modem name and model.
2. Using Windows, open the S t a r t Menu and then open S e t t i n g s > C o n t r o l
P a n e l > P h o n e a n d M o d e m O p t i o n s . Once the control panel for
modem operation is open, select the M o d e m T a b . Check the name and
model number to insure that it is an exact match with the provided
documentation.
3. Also at this time, record the Com Port where the modem is attached.
4. If no modem name is displayed on the Modem Tab, then click the Add…
button and follow the Device Installation Wizard’s instructions.
Note If an external modem is required at Central, repeat the same process

listed above, but load the proper Windows modem driver during the
Device Installation Wizard’s instructions. (Usually, this can be retrieved
from the modem drivers floppy disk or CD that was provided with the
external modem, or over the Internet from the manufacturer’s website.)
5. Once completed, record the complete modem name with model and Com Port.
6. Back on the Windows desktop, right-click on the My Computer icon and select
Properties. Open the Network Identification > Properties options and record
the Computer Name.
7. Start the CLMATS Kernel.
8. Start the CLMATS Comm Server.
9. Open the CLMATS® Main Menu. Select Set Up > Configure Channels, and
then open the Modem tab.

10. Place a check in the box to the left of the line that contains the previously
recorded Computer Name, IP Address and exact Modem Name. Click the
Apply button and then the OK button.
11. From the CLMATS Main Menu, select a known good Master or Isolated Local
Intersection, and choose Action > Master (or Local) and then Get Software
Revision. This action will send a command string to the modem.
This final step should result in seeing the software revision level of the selected field
hardware in your CLMATS window. If this does occur, the entire modme
communications channel is configured properly.

Phone Numbers
PHONE NUMBERS
Phone numbers are typically used in an isolated controller for reporting of alarms to a
central computer that is running Smartways™ or CLMATS™ closed loop software.
These numbers are used if the port assigned to the Central function is assigned to
use an AT Modem. Two numbers may be programmed, each 25 digits long: phone
number 1 is the default and phone number 2 will be used if the controller cannot get
through on phone number 1.
Phone Numbers:
Phone 1: 9,5551212
Phone 2: 9,5551213
SHIFT+(0=W 1=, 2=; 3=# 4=' ' 5=T 6=P)

Figure 327 – Phone Numbers setup screen
Special characters can be entered by pressing the SHIFT key with one of the number
keys 0 - 6. The table below summarizes these special characters. For information on
what functions these characters perform, refer to the user's manual supplied with your
modem.
Table 45 – Special characters for phone numbers
SHIFT + Character Entered Typical Function
0 W Wait for a second dial tone
1 , Pause a moment during dialing
2 ; Stay connected even if no carrier is
detected. (i.e. “Off Hook” but no “Carrier
Detect”)
3 # Special terminate code for some pagers
4 (space) Phone number terminator
5 T Tone dialing, usually comes before the
phone number
6 P Pulse dialing, usually comes before the
phone number

EVENT CALL-IN
The 3000 Controller can be programmed to report specific types of events to Central
based on the priority level assigned to each event type. Events can be assigned to
either be ‘High’ priority, ‘Low’ priority, or ‘Disabled’. Use the keypad arrows to
navigate on the screen. To assign a value to a trigger, use the y/n button to switch
between the ‘H’, ‘L’, and ‘D’ settings. By default, all of the triggers are set to the Low
setting.
Event Log Call-In Priority

VALUE High / Low / Disable
ALM1 TBC RRTC ALM4 ALM5 ALM6 ALM7 ALM8
H L L L D D D D
CKSF STUF MONF DETF CRDF CYCF CABO DIAG

L D L L L H L D
Figure 328 – Event Call-in triggers - screen 1

To program an immediate call-in for a specific type of event, place an ‘H’ under the
event. A Low priority event, when detected, will be recorded, but a call will not be
made to Central until a high priority event (H) is detected, thus triggering a call-in. (i.e.
a Low priority event will only reach Central by piggy-backing on a high priority event.)
Paging down from this screen opens a second set of potential event call-in triggers. A
Disabled event will never be reported to Central, except in the form of line items in
manually retrieved Event Logs.
Event Log Call-In Immediate

VALUE High / Low / Disable
MCE UCF SFL KBLD CABF HPRE PWRU DNLD
D H L L L L L L
Figure 329 – Event Call-in triggers - screen 2

The types of events that can trigger a call are listed in Table 46.

Event Call-In
Table 46 – Event type codes

Code Description
ALM1, 4-8 Alarms 1 - 8
CABF Cabinet Flash
CABO Cabinet Open
CKSF Checksum Failure
CRDF Coordination Failure
CYCF Cycling Failure
DETF Detector Failure
DNLD Download
HPRE High Priority Preempt
KBLD Keyboard Load
MCE Manual Control Enable
MMUF MMU Failure
MONF Monitor Flash
PWRU Power-up
RRTC Reset real time clock
SFL Soft Flash
STUF Start-up Failure
TBC TOD override input
UCF Uniform Cabinet Flash

LOG DATA
This menu provides for setting up data that may be logged by the 3000 controller for
retrieval by a central system software package (such as CLMATS, IQCentral, or
SmartWays.) Volume, MOE, and speed trap data may be logged. There are three
pages of Log Data settings, accessible by paging down from the first.
The first page sets up the log period time for the Volume and MOE logs.
Log Data >>PgDn for Speed Traps<<
(VALUE: Sample Period Divisible Into 60)
Volume Log Sample Period: 15 Minute(s)

(Enabled by TOD Ckt 125(EVL))
MOE Log Sample Period: 15 Minute(s)

(Enabled by TOD Ckt 126(EML))
Figure 330 – Log Data Settings - page 1
Note that acceptable period values must divide evenly into 60, i.e. the following
values are acceptable: 1, 2, 3, 4, 5, 6, 10, 12, 15, 20, and 30.
Press the PGDN button to define the detectors for speed traps.
Log Data (Detectors:0-32, 0-NONE)
Speed Trap 1 2 3 4
Leading Det 14 0 0 0
Trailing Det 15 0 0 0
Distance 195 0 0 0
(in feet)
>>PgDn for Event Log Enables<<
Figure 331 – Log Data Settings - page 2
The second screen configures up to 4 speed traps. For each trap, specify the channel
of the leading detector (1-32), the channel of the trailing detector (1-32), and the
distance between them in feet (0-255 ft).
Figure 332 – Measuring the distance between speed trap detectors

Press the PGDN button to set the Event Log Enables.

Log Data
The third screen determines what data will be stored in the Event Log. Refer to the
table below for the definitions of the abbreviations on this screen.
Event Log Enables VALUE (YES/NO)
CRDF MMUF LFSH HPRE LFRE PWRU LBAT RFLT

Y Y Y Y Y Y Y Y
ALM1 ALM2 CYCF

Y Y Y
Figure 333 – Log Data Settings - page 3 (Event Log Enable settings)
Table 47 – Log Enable Codes

Code Description
ALM1, 2 Alarms 1, 2
CRDF Coordination Failure
CYCF Cycling Failure
HPRE High Priority Preempt
LBAT Low Battery
LFSH Local Flash
LPRE Low Priority Preempt
MMUF MMU Failure
MONF Monitor Failure
PWRU Power-up
RFLT Response Fault

PORT 1 SETUP
A controller designed to the TS 2 Type 1 standard will communicate with one MMU,
up to four T/F (Terminal and Facility) BIUs (Bus Interface Units) and up to four
Detector BIUs through its Port 1 communications port. The user must enable
communication with those units installed in their respective TS 2 cabinets. The
controller will only send Command Frames to those devices that are enabled via this
programming screen.
A TS 2 MMU monitors up to 16 channels. These channel must also be mapped
(assigned) to the vehicle/ped phases and overlaps programmed in the Controller
section of the 3000 controller. It is important to note that any phase or overlap signal
output to the street must be assigned a channel number, regardless of whether or not
a TS 2 MMU is used in the system.
Note Much more information about TS 2 Type 1 operation is available in Chapter 12

of this manual, starting on page 395.
Page 1 of the Port 1 Setup screens assigns BIU Enables, as shown in Figure 334.
BIU Enables Type 2 I/O Mode : 1

Modes 0 – 2 are
VALUE (YES/NO)
determined by
T/F 1 2 3 4 5 6 7 8 MS-A I/O select
BIU Y Y Y Y N N N N input bits. This
entry must match,
DET 9 10 11 12 13 14 15 16 otherwise a Type
BIU Y Y N N N N N N 2 I/O Mode Error
will occur.
Figure 334 – Port 1 Setup - screen 1 (BIU Enables)
This section specifies the controller I/O mode and configures BIU’s to communicate
with the MMU.
Type 2 I/O Mode — The mode is normally selected by the MS-A I/O Mode select
inputs (bits A, B, C). The entry in this field must match the I/O Mode selected by these
bits. Mode 7 is a special mode that allows a TS 2 controller to recognize a ‘D”
module in a TS 2 cabinet. The I/O select bits A, B, and C must all be OFF to
recognize Mode 7. The MS-A I/O select modes currently available are Modes 0, 1
and 2. Mode 0 is the same as TS 1 (downward compatible), mode 0 and 1 include
more preempts, detectors and other functions. Refer to the TS 2 I/O mode table in
Appendix C, page 444. The unit will automatically default to mode 0 operation in a TS
1 cabinet because the I/O select inputs were former spares in TS 1 and would
presumably be off.
BIU Enables — Activates those BIUs that are used in your cabinet. Terminals and
Facilities (T/F) BIUs are normally used with TS 2 Type 1 controllers only, which have
no MS-A, B, C, or D connectors. Type 2 controllers (which have MS-A, B, and C
connectors) normally do not use T/F BIUs, so all of them are programmed to ‘N’
(disabled.) Detector BIUs must be used by Type 1 controllers, but can also be used
by Type 2 controllers, especially if many detectors are used.

Port 1 Setup
Selections 1-4 are terminal and facilities (T/F) BIUs. Selections 5-6 are reserved by
NEMA. Selections 7-8 are manufacturer specific, but not currently used by Peek.
Selections 9-12 are Detector BIUs. Selections 13-14 are reserved by NEMA.
Selections 15-16 are manufacturer specific, but not currently used by Peek.
Note ®
In TS 2 Type 2 applications, a Peek Traffic VideoTrak Unit can act as a detector
BIU and use Port 1 to send detector data to the controller. In this case, all other I/O
is via the A, B, C Connectors. Port 1 must be used to communicate with the
Controller, the MMU and the Video Trak Unit. To determine phase colors, Video
Trak “listens” to theType 0 Command Frame between the Controller and the
MMU.
In simple TS 2 Type 2 operation, where an MMU is used and Port 1 is enabled, but
there are no T/F or DET BIUs in use, all values above should be set to ‘N’. Only the
MMU Enable setting (shown in Figure 335) needs to be set to ‘Y’.
Press PGDN to access the MMU and Secondary to Secondary controls
MMU/Secondary to Secondary Enables
VALUE(YES/NO)
MMU Enable: Y
Secondary To Secondary Enable: N
Compatibility Check Disable: N
>> PgDn for Channel Assignments <<

Figure 335 – Port 1 Setup - screen 2 (MMU Secondary Enables)
MMU Enable — Set MMU Enable = Y whenever an MMU is used in the Type 16
Mode and Port 1 comm is to be operable. Set to N if no MMU is used, if the MMU is
operating in type 12 mode, or if the MMU port 1 comm has been defeated at the
MMU, usually by jumper on the MMU port 1 connector.
Secondary to Secondary Enable — Secondary Addressing is not implemented at
this time.
Compatibility Check Disable — In addition to MMU monitoring and checks against
the field terminals on its Jumper Card (TS1 style), the Controller and the MMU
provide redundant checks against each other for added monitoring ability. The
Controller reads a Type 129 Response Frame from MMU, which is a reflection of the
field channels and colors the MMU registered as active within the last 100ms. The
Controller compares this to its sequence configuration and channel programming in
the screens below. If the Controller determines an incompatibility exists, it will place
the intersection in flash, if the MMU has not already done so. In addition, the MMU
reads a Type 0 Command Frame from the Controller, which reflects the channel
colors that the Controller is about to send to the T/F outputs. The MMU compares this
to its Jumper Card and if deemed invalid, it places the intersection in flash before the
controller sets the T/F outputs. Enter “Y” here to disable this operation.

PGDN to the MMU Channel Assignments screen:

MMU Channel Assignments Phases 1-16
(0-16, 0= None, 1-16= Channel 1-16)
PH 1 2 3 4 5 6 7 8
CH 1 2 3 4 5 6 7 8
PH 9 10 11 12 13 14 15 16
CH 0 0 0 0 0 0 0 0
Figure 336 – Port 1 Setup - screen 3 (MMU Channel Assignments)

PGDN to continue:
MMU Channel Assignments Peds 1-16
(0-16, 0= None, 1-16= Channel 1-16)
PED 1 2 3 4 5 6 7 8
CH 0 9 0 10 0 11 0 12
PED 9 10 11 12 13 14 15 16
CH 0 0 0 0 0 0 0 0

PGDN ...
MMU Channel Assignments Overlaps A-P

(0-16, 0= None, 1-16= Channel 1-16)
O/L A B C D E F G H
CH 0 0 0 0 0 0 0 0
O/L I J K L M N O P
CH 0 0 0 0 0 0 0 0

PGDN ...
MMU Channel Assignments Ped Overlaps A-P

(0-16, 0= None, 1-16= Channel 1-16)
PED A B C D E F G H
CH 0 0 0 0 0 0 0 0
PED I J K L M N O P
CH 0 0 0 0 0 0 0 0

Port 1 Setup
For TS 2 operation, channel assignment must be selected to insure proper

communication through the correct BIUs. Channels 1-8 are contained in T/F BIU #1
and channels 9-16 are contained in T/F BIU #2. Any phase not assigned to a channel
will not activate any outputs on the BIUs. Vehicle and Pedestrian movements,
overlaps and pedestrian overlaps must be assigned if used as the control signal.
Note Any Dummy Phases present do not need to be assigned to an MMU channel.
Secondary to secondary addresses are used to poll for service to exchange

information between secondary devices. Secondary Addressing is not implemented at
this time.
Secondary to Secondary Addresses

VALUE(0-255)
1 2 3 4 5 6 7 8
0 0 0 0 0 0 0 0
9 10 11 12 13 14 15 16
0 0 0 0 0 0 0 0
Figure 340 – Port 1 Setup - screen 7 (Secondary-to-Secondary Addresses)

SYSTEM NAME
Option 7 on the Comm/System Setup menu is the System Name screen. Navigating
to it (MM > 3.Change Data > 5.Comm/System setup > 2.Comm Setup > 7.System
Name) will display this screen:
System SHIFT-1 Erases Name
Name: MAIN ST & 4TH
ABCDEFGHIJKLMNOPQRSTUVWXYZ 0123456789#&.
RIGHT & LEFT ARROW POSITIONS CURSOR.

Up & Down Arrows Select Character.
Figure 341 – System Name screen
The System Name, Contact Name, and HDLC Address screens were added to the
3000 Series firmware in version 3.6 and support NTCIP operation. Although a System
Name is unique to NTCIP, it is not required for successful communication. “System
Name”, or sysName as it is known in the MIB tree, is additional information for the
users of the system. It is typically set to a string describing the overall System. As
an example, one might set this string to “Southeast Section” while the intersection’s
name might be “Main & First St.”
You enter a name on this screen by positioning the cursor in the Name: row, and then
using the cursor on the alphanumeric line to select characters to enter into the name.
The right and left arrow keys move the cursor along the Name: and alphanumeric
rows. Press the down arrow once to push the cursor down into the alphanumeric row.
Once the cursor is in the alphanumeric row, either the up or down arrow will send the
currently highlighted letter up into the name and position the cursor in the next
character space in the Name field. Press SHIFT and 1 together to clear the entire
name. Or you can move the cursor to the left in the Name field and ‘overwrite’ the
current character with your next selection. A space character is available between
the ‘Z’ and the ‘0’ in the alphanumeric row. The last three characters in the
alphanumeric row provide some punctuation marks.
When you are finished, press the MENU button to return to the Comm/System Setup
menu.

Contact Name
CONTACT NAME
Option 8 on the Comm/System Setup menu is the Contact Name screen. Navigating
to it (MM > 3.Change Data > 5.Comm/System setup > 2.Comm Setup > 8.Contact
Name) will display this screen:
Contact SHIFT-1 Erases Name
Name:
RIGHT & LEFT ARROW POSITIONS CURSOR.

Figure 342 – Contact Name screen
The System Name, Contact Name, and HDLC Address screens were added to the
3000 Series firmware in version 3.6 and support NTCIP operation. This is also not
required for NTCIP operation, but instead is additional information defined in the
<required> system NODE of the MIB tree. “Contact Name” is used to identify a
person or agency responsible for this unit, particularly in the case of a fault or problem
condition.
You enter a contact name on this screen by positioning the cursor in the Contact: row,
and then using the cursor on the alphanumeric line to select characters to enter into
the name. The right and left arrow keys move the cursor along the Contact: and
alphanumeric rows. Press the down arrow once to push the cursor down into the
alphanumeric row. Once the cursor is in the alphanumeric row, either the up or down
arrow will send the currently highlighted letter up into the contact and position the
cursor in the next character space in the Contact: field. Press SHIFT and 1 together to
clear the entire contact name. Or you can move the cursor to the left in the Contact:
field and ‘overwrite’ the current character with your next selection. A space character
is available between the ‘Z’ and the ‘0’ in the alphanumeric row. The last three
characters in the alphanumeric row provide some punctuation marks.
When you are finished, press the MENU button to return to the Comm/System Setup
menu.

HDLC ADDRESS
Option 9 on the Comm/System Setup menu is the HDLC Address screen and is the
place where one can add physical/HDLC network addresses for an NTCIP controller.
Navigating to it (MM > 3.Change Data > 5.Comm/System setup > 2.Comm Setup >
9.HDLC Address) will display this screen:
PHYSICAL/HDLC NETWORK ADDRESSES
PORT 2: PHYSICAL ADDRESS : 0

HDLC GROUP ADDRESS: 0
PORT 3: PHYSICAL ADDRESS : 0
HDLC GROUP ADDRESS: 0
Figure 343 – HDLC Address screen

If the controller is to be used as an NTCIP unit, the operator must specify the
controller’s physical address. This is similar to the “Intersection ID” number for TS 1
and non-NTCIP TS 2 units. The physical address range is 1 to 8191. Physical
address 63 is a test address. This special test address tells the controller to respond
to ANY Physical Address. If the controller’s Physical Address is set to 63, then the
controller will accept any incoming message regardless of how it is addressed.
However, this is typically used for testing purposes and should not be implemented in
an active intersection as communication “collisions” are likely to occur.
The HDLC Group Address is used if Central needs to send a “broadcast” message to
more than one controller at a time. Group addresses range from 1 to 8191, although
address 63 is reserved as an “all stations address.” A group address 63 message
must always be transmitted as a single byte (with all bits set.) A message received
with a Group Address of 63 will force the controller to respond, regardless of its actual
Group Address setting.
Since the NTCIP 3000-series controller can communicate on either Port 2 or Port 3,
the user has the option to enter physical and HDLC addresses for either port.
Note The NEMA-defined object, sysLocation, also under the system NODE of the
MIB tree, corresponds to the Controller’s database value for “Intersection
Name”. This entry can be found in the controller’s programming in the “Unit
Config/Sec. Code” menu.

Chapter 11 — Unit Configuration and
Security Codes
This section explains system security, intersection naming, and several other internal settings
of the 3000 Series controllers. The following topics are discussed in detail in this chapter:
An overview of the Unit Configuration menu, on page 374.

Security codes, on page 375.
Restricting access to controller menus, on page 376.
Adding and deleting screens, on page 377.
Updating the controller’s firmware, on page 380.
Setting the intersection name of a controller, on page 378.
EEPROM and Audio settings, on page 379.
I/O Steering, on page 380.

Chapter 11 — Unit Configuration and Security Codes
OVERVIEW
The Unit Configuration menu can be accessed from the Main Menu by selecting
option 3. Change Data to open the Program Menu, and then selecting item 6. Unit
Config/Sec. Code.
This menu is used for functions not directly related to intersection operation, but
rather configuration of the unit. The screen contains keyboard security code enables,
restricting access to menus, programming an alphanumeric intersection name,
enabling the use of an EEPROM module, and adjusting the audio level of the
controller's internal speaker.
Unit Configuration
1. Security Codes (Superv. & Restricted)

2. Restricting Access to Menus
3. Adding & Deleting Menus
4. Intersection Name
5. EEPROM & Audio Setup
Figure 344 – Unit Configuration Menu

These items are described in detail in the rest of this chapter.

Security Codes
SECURITY CODES
The 3000 Controller provides 3 levels of security - Supervisor, Restricted and Read
Only. The user can program a Supervisor and Restricted numeric security code by
entering a value between 1 and 9999. A value of ‘0’ is no security code. Once loaded,
access using the old security code is required to change to a new one.
The Supervisor code enables change data of all functions.
The Restricted code enables change data of all functions except those that
have been restricted by the supervisor (see Restricted Menus below).
Failure to enter either of the security codes (when codes are used) results in
Read Only privileges.
The entry of either security code activates security for the controller. Every time
the CHANGE DATA menu is accessed, the user will be prompted for a security
code.
Security Codes VALUE(0-9999)
Supervisory Security Code:
Restricted Security Code:
>>0 Disables Security<<

Figure 345 – Security Codes screen
Note that is possible to have a restricted security only (no supervisory) code. If so, the
user will be prompted for a security code as above, and once entered, will have full
access to all change menus (no restrictions).
The controller has a built in security timer. If the controller has been accessed with a
security code and no key has been pressed within 5 minutes, the controller will beep
and return to the NORMAL STATUS dynamic display, requiring the user to re-enter
the security code.

RESTRICTING ACCESS TO MENUS

The 3000 Controller allows the Supervisor to restrict access to the controller's
database. The supervisor always has complete access, but for security reasons, may
wish to allow other users to program only certain areas of the controller. This feature
is only active if both a supervisor and a restricted security code have been entered.
When selecting “Restricting Access to Menus” or “Adding/Deleting Menus” from the
Unit Configuration Menu, a series of instructional screens only will follow, there are no
data entries in these areas. These options involve techniques accomplished within
the individual menus themselves, and not by specific data base entries. The purpose
for these menu items are to inform users of these features and to instruct them in
their usage. The following instructions are a more detailed version of those controller
screens.
Restricting a Menu Selection

1. There must be both a supervisory and restricted security code entered (non-
zero). If not, they must be loaded now by entering a number (1 - 9999) in each.
2. To restrict a menu, after accessing the supervisory code, go to the menu
containing the item to be disabled and simultaneously press SHIFT* and the
Menu Number Key of the item.
The number next to the selection will be displayed in reverse video (a white number
on a dark background) to indicate that this item is restricted. If a restricted user
attempts to access a feature that has been so disabled, the controller will sound the
error tone and deny access to that feature.
For example, to deny access to the preemption area of the database, from
supervisory access, go to the Data Entry Menu and press SHIFT and 4 together. The
4 will now be displayed in reverse video indicating that access to preemption is limited
to the supervisor only.
Restoring a Menu Selection Back To Full Access

Press SHIFT and the Menu Number Key again to toggle the menu item back to its
original state.
*
Actually press SHIFT (and hold in) slightly before the item key.

Adding and Deleting Menus
ADDING AND DELETING MENUS

Menus can be added or deleted from the display. By doing so, functions that are
never used can be eliminated to simplify the look of the 3000 menus. This process
can be performed if security codes are not used, but if security codes are used, only
the supervisory code can do so.
Adding/Deleting Menus
See note above under Restricting Access to Menus. The note applies to
Adding/Deleting Menus as well.
To Delete a Menu:
1. If security codes are used, first access the supervisory code. If not used, go to
step 2 below.
2. Go to the menu screen of the item to be deleted and simultaneously press
*
CLE AR and the menu number key of the menu item to deleted. In this case,
the selection will be completely removed from the menu.
To Restore a Menu Item

Repeat the key sequence above to toggle back to the original state.
To View All Menus, including any that have been deleted,
Press SHIFT and HELP simultaneously.
*
Actually, press CLE AR (and hold in) slightly before the item key.

SETTING THE INTERSECTION NAME

Intersection SHIFT+1 Erases Name
Name: MAIN ST & 4TH AVE
Right & Left Arrows Position Cursor.

Figure 346 – Intersection Name screen
This option allows entry of up to a 26 character alphanumeric name for this controller
(or intersection). This name will appear on reports generated by the controller,
database printouts and on the copyright screen. Entry is performed by moving the
cursor to any position within the 26 character name with the right/left arrow keys.
Then press the down arrow key and move the cursor to the desired character within
the “character line” and press the up arrow to insert that character into the selected
position in the name.

EEPROM Settings/Audio Adjustment
EEPROM SETTINGS/AUDIO ADJUSTMENT

EEPROM/Audio Adjust VALUE(YES/NO)
EEPROM Loaded with Keyboard Entry: Y

(EEPROM Copied To RAM On Power-Up)
Audio Adjust(0-10): 5
Figure 347 – EEPROM/Audio Adjust screen

The first option instructs the controller to write to the EEPROM every time data is
entered through the keyboard. The second option adjusts the controller's speaker
audio level.
If the EEPROM feature is enabled (by entering a ‘Y’), then data loaded through the
keyboard will also be stored in the EEPROM module. This feature allows data to be
kept in a non-volatile backup area in case of failure of the controller's main memory.
Also, data stored in an EEPROM module can be transported from one 3000 to
another. In addition, the entire contents of the EEPROM can be copied into main
memory or vice versa (see the “Utilities” section).
Caution If the EEPROM feature is enabled and the EEPROM is not present or
inoperative, the controller will put the intersection into flash on power-up as
a precaution against corrupt data. If this happens, a message will be
displayed in the Checksum Dynamic Display. Checksums in the EEPROM
module are maintained and checked constantly just as they are in main
RAM. If a checksum error occurs, the intersection will go into flash.
The Audio Adjust value allows the user to adjust the level of audio feedback. The
larger the number, the longer the tone will sound when a key is pressed. A zero value
inhibits the tone. Erroneous entries will cause the error tone to sound regardless of
the Audio Adj. value.

UPDATING THE CONTROLLER FIRMWARE

The program running inside the controller determines how the unit sequences the
intersection, handles calls and timing, maintains logs, and presents the user interface;
basically the firmware determines how the controller performs all of its functions.
Firmware is installed in the factory, but existing devices can be updated to newer
versions of the firmware. However, such updates should only be performed in a
bench-test setting, unless the firmware and configuration are copied in whole cloth
from one working intersection to another.
There are two tracks of firmware in the 3000 series controllers. The older line of
firmware is designated the 5900 series firmware and is intended to maintain
compatibility with older utility software and hardware, such as the old Peek DOS
application called ‘SmartWays’. This line of firmware no longer receives all of the
current updates, but it is supported in existing installations by the Peek Technical
Support team.
The other firmware track is the 8216 series. This is the type of firmware that is
installed in all newly shipped 3000E controllers. It includes all the latest updates and
improvements for the controller.
Firmware can be upgraded from the 5900 series to the 8216 series. However, if this is
done, the controller will no longer be compatible with the Smartways software. Also,
be aware that an update from the 5900 series firmware to the 8216 series firmware
requires that all Special and Restricted Menu settings be cleared before the update is
applied.
Maintaining Firmware Flavor

There are several ‘flavors’ of firmware installed in 3000 series controllers, each aimed
at a different cabinet standard. There are TS 1, TS 2, NTCIP, and Protocol-90
versions of firmware. An upgrade of the firmware should always be done using only
the proper flavor for the type of unit involved. (i.e. Do not attempt to install a TS 2
version of the firmware on a TS 1 unit.) This is because each requires different
hardware, and because each version of the firmware requires different amounts of
controller memory, and some controllers do not have enough memory to host other
types of firmware. It is highly recommended that you stick with the same flavor of
firmware that was installed in the unit at the factory.
Installation Methods
This firmware may be delivered to the controller in one of two ways: either as two
binary files that can be burned to the controller’s EPROM memory chips, or as a
single binary file that can be loaded into Flash memory via the controller’s Port 2
serial port. This latter option is only available for 3000E controllers that are
designated ‘Flash Memory Enabled’. (It is labeled such on the front of the unit.)
If you are updating EPROM chips that will be placed into your 3000 or 3000E
controller, the proper checksums for the two binary files are listed in Table 48. These
checksum numbers can be used to verify that the firmware has been successfully
received from Peek and successfully burned to the EPROMS.

Updating the Controller Firmware
Table 48 – Checksums for various 3000 series firmware (8216 series)

Firmware EPROM 0 Checksum value (hex) EPROM 1 Checksum value (hex)
TS 1 v3.1.1 282A 29B5
TS 2 v3.1.1 21E8 0FAE
NTCIP v3.1.1 6086 CE06
TS 2 v3.1.2 1F63 1A88
TS 1 v3.3.6 9474 0070
TS 2 v3.3.6 8478 C765
Protocol-90 v3.3.6 1A07 F6BB
TS 1 v3.4 83CC 417A
TS 2 v3.4 5D96 C0C2
NTCIP v3.4 26E2 8629
Protocol-90 v3.4 67E8 4B4B
TS 1 v3.6 9378 2CDB
TS 2 v3.6 6F7E 3FDC
TS 2 v3.6.2 7A04 15C2

Firmware Tools for Flash-Enabled Controllers

The Flash memory capability of the 3000E traffic controllers is accomplished with a
slightly modified motherboard and a new boot monitoring software component stored
in the controller’s memory. These changes became available in the 3000 Series
controllers in late 2004. Just as with the EPROM memory previously used, the Flash
memory is made up of a pair of chips located near the top edge of the controller’s
motherboard. In fact, the Flash memory utilizes the same sockets that were
previously used by EPROMS. This feature allows the unit to be used with either Flash
memory or EPROM memory, but only if the motherboard is reconfigured using a set
of jumpers. This modification is described on page 384.
Boot monitor software is preinstalled on all Flash Enabled 3000E controllers. This
piece of software is used to monitor and update the firmware loaded in the 3000E.
Normally upon startup, the Boot monitor simply verifies that valid firmware is available
in memory, and then immediately passes control of the unit on to this firmware.
However, the monitor software can also be used to place the unit into firmware
update mode, ready to communicate with one of the firmware update packages that
are described below. To place a 3000E controller into firmware update mode, the
operator simply needs to hold down the SHIFT and PGUP keys together while
restarting the unit.
After entering firmware update mode, the screen of the 3000E controller will display
the following message:
Ready to receive new firmware on PORT 2
3000E Boot Block v0.10 (build 11)
Copyright (c) 2004 Peek Traffic Corp.
[DISP ADJ] for contrast [END] to exit

Figure 348 – 3000E Series device’s screen when in Firmware Update Mode
With this screen displayed on the 3000E Series device, you can either use the
Firmware Upgrade Utility (or Pocket Central) to connect to the device, or you can
press END on the controller’s keypad to return to normal operation.

Flash Update Utility for Windows

This package runs on a Windows-based computer and can be used to send firmware
to a Flash Enabled 3000E Controller (in the form of a pre-packaged .pfw file available
from Peek.) The basic process to update the firmware of a Flash Enabled 3000E
Controller is as follows:
• Connect the PC to the controller using a serial cable
• Open the Firmware Upgrade Utility on the PC
• Place the controller into Flash Memory Program mode
• Use the Utility to query the device about its current firmware
• Load a firmware file into the Utility’s memory
• Load the new firmware onto the device
Figure 349 – First connect the PC to the 3000E device via a serial cable
For more details about this product, refer to the Release Notes for the Firmware
Upgrade Utility for 3000E Series Devices (p/n 99-395.)
Pocket Central for Pocket PC

Pocket Central is similar to the Flash Update Utility for Windows, but with an
important extra capability. Like the Windows utility, Pocket Central can be used to
update the firmware in a Flash Enabled 3000E controller, only using a Pocket PC
handheld device. But Pocket Central also can be used to transfer 3000E controller
configurations between controllers, and between controllers and the CLMATS central
software system. For additional details about the operation and methods of Pocket
Central, refer to the Pocket Central Release Notes (p/n 99-393.)

Switching the Controller to Use EPROM Memory

Follow these steps to switch a Flash Memory Enabled 3000E Controller from Flash
memory operation to EPROM memory operation.
Important This procedure involves changing hardware on the interior of a 3000E

controller. It should only be performed on a controller that has been removed
from intersection service, and powered down long enough so that any
residual charges in the power supply have dissipated. Follow normal safety
precautions when working around and within electrical hardware. In
particular, be aware that EPROM and Flash memory chips are vulnerable to
damage from static discharges.
1. Locate a pair of EPROM chips containing the appropriate firmware for a 3000E
controller. Make sure they are labeled EPROM 0 and EPROM 1.
2. Open the front face of the 3000E controller.
3. Locate the two flash memory chips on the top (or front) edge of the main
controller circuit board. They are labeled on the motherboard as U603 and
U604.
Figure 350 – Locations of Flash/EPROM chips and jumper links

4. Remove the Flash memory chips from sockets U603 and U604 and set them
aside.
5. Locate the motherboard link labeled X900. It is just behind the EPROM 0
socket. The jumper installed on X900 is currently installed in the A19 position.
Move this jumper to the 5V position.
6. Move the X901 jumper to the X610 position.

7. Move the X902 jumper to the X610 position.

8. Move the X903 jumper to the UDS position.
9. Move the X904 jumper to the LDS position.
10. Insert EPROM 0 into U604.
11. Insert EPROM 1 into U603.
That completes the conversion of a 3000E to EPROM operation.
Converting a Flash Enabled 3000E controller from EPROM to

Flash Operation
If a Flash Enabled 3000E controller has previously been switched to EPROM
operation, it can be converted back to Flash operation by simply reversing the
EPROM procedure. (Replace the EPROMS with Flash memory chips, and move the
jumpers back to their Flash positions.)
The following table shows the proper positions for all of the 3000E motherboard links
for both EPROM and Flash operation.
Figure 351 – Proper jumper settings on the 3000E motherboard for

Flash/EPROM operation

Loading the New Firmware

Whether your controller uses programmable EPROMS or internal, flashable RAM to
install new firmware, there are two steps to the upgrade process. First, you will need
to load the new firmware onto the hardware. The next two sections describe how to
do this on EPROM and Flash memory controllers. Then, after the firmware update, go
to the next section to update the modem setup string (if an external modem is used
with your 3000 series controller.) This latter step is only required if you are upgrading
to one of the v3.6.x firmware versions.
Installing Updated Firmware to EPROMS

To upgrade an EPROM-equipped 3000 or 3000E Traffic Controller in the field, follow
these instructions:
1. If you ordered updated EPROMS from Peek rather than just the binary
firmware files, skip down to step 6.
2. Locate the following items in order to burn the updated firmware to EPROMS:
Two 4MB EPROMs (28 pin DIP package), these may be recycled out of
field units
an EPROM burner capable of holding a 4MB EPROM
EPROM burning software
the two binary files containing the updated firmware
3. If the EPROMs were used previously, erase them.
4. Insert one of these blank EPROMs into the burner and burn the firmware file
that ends in “- 0 . b i n ” onto it. Label it with the firmware version number and
‘E P R O M 0 ’.
5. Insert the other blank EPROM into the burner and burn the firmware file that
ends in “- 1 . b i n ” onto it. Label it with the firmware version number and
’E P R O M 1 ’.
6. Observing all safety and other municipal ordinances, place the intersection to
be updated into flash.
7. Power down the 3000 Series Traffic Controller.
8. Open the front panel and remove the two EPROMS that are currently installed
in the unit. Replace them with your updated versions, being sure to place the
properly labeled EPROM in each socket.
9. Restore power to the unit.
10. As the unit powers up, it performs a series of database verification tests. If any
of the seven databases in the controller’s memory have been corrupted in any
way, this test will detect the problem. If any problems are seen, the unit will
display an error screen, as shown in the next figure. Any databases that have
problems are listed on this screen. The only way to proceed to a running state
is to acknowledge this error screen by pressing the CLE AR button. Any of the
following controller databases may be discovered to have been corrupted
during the firmware upgrade: Controller, Coordination, Time of Day,
Preemption, Option, Special, and BIU I/O Mapping.

Note The BIU I/O Mapping database error message will not appear (even if
there is corruption in this database area of memory) unless I/O mapping
is currently configured to be ACTIVE.
[Controller] [Coordination]

Figure 352 – Power-on Self Test Error Message
If this window appears, press the CLEAR key to go ahead and start the
controller.
11. If any database errors were detected, you will need to load good files into the
controller before using the controller to run an intersection. This can be done
by choosing to load default databases (MM > 3. Change Data > 8. Utilities > 1.
Default Data Load menu,) or you can load a good set of databases from
CLMATS, an EPROM card, or by using a PC or Pocket PC device with the
3000 series firmware upgrade utility software loaded.
If there were no database errors detected, proceed to the next step.
12. Press 1 for Dynamic Displays.
13. Press 1 for Controller Func(tions).
14. Examine the Normal Status screen for proper operation and cycling.
15. If everything appears to operating correctly, return the intersection to normal
operation.*
*
In the past, customers have also been told to clear any central overrides that may be active in the controller
whenever attempting to create a ‘Healthy Controller’ situation. If overrides are an issue, the clearance
process has changed, as described on page 29.

Installing Updated Firmware to Flash Memory

If the 3000 or 3000E controller shows the ‘Flash Memory Enabled’ logo on its front
panel, it should be updated using: a single binary firmware file from Peek Traffic, and
a laptop computer or Pocket PC handheld device connected to Port 2.
Note Additional information about these types of upgrades are available in the
release notes for the Firmware Upgrade Utility for Windows (99-395) and for the
Pocket Central Utility for Pocket PC (99-393).
The following hardware and software are required in order to perform this type of
upgrade:
a 3000E controller that is designated ‘Flash Memory Enabled’
Either a laptop PC running Windows NT, Windows 2000, or Windows XP
OR a Pocket PC device running Pocket PC 2002 or Pocket PC 2003
a serial cable to connect the PC or Pocket PC device to Port 2 of the traffic
controller
If using a PC for the upgrade, you will also need the 3000E Firmware
Upgrade Utility for Windows, which is available from Peek Traffic
If using a Pocket PC device for the upgrade, you will need the Pocket
Central software, which is available from Peek Traffic
Important Although previous 3000E products were updated using

removable and programmable EPROM memory chips,
and although it is possible to remove the Flash chips
from the newer devices, it is highly recommended that
you do not remove these chips from the units.
Firmware updates for Flash Memory Enabled units
should only be performed using the following procedure.

The basic steps required to upgrade a Flash memory-equipped 3000E controller in

the field are listed here:
1. Locate the binary firmware file that you received from Peek Traffic. (It will
follow the form: “8 2 1 6 X v. v. v b u i l d # # # . p fw ” )
2. Store the firmware file in a known location on the PC or Pocket PC where the
update utility will be run.
3. Observing all safety and other municipal ordinances, place the intersection to
be updated into flash.
4. Power down the 3000 Series Traffic Controller.
5. Connect the PC or Pocket PC to the device using the required serial cable.
6. Open the Firmware Upgrade Utility on the PC (or the Pocket Central software
on the Pocket PC device.)
7. Place the controller into Flash Memory mode by powering up while holding
down the SHIFT and PGUP keys.
8. Use the Utility to query the device about its current firmware. Verify that the
controller has the current firmware version you expect it to have.
9. Load the . p fw firmware file into the Utility’s memory.
10. Send the new firmware to the controller.
11. When both the PC and the controller show that the firmware update has
completed, press the END key on the 3000E to restart the unit with the new
firmware. Disconnect the PC or Pocket PC from the controller.
12. As the unit powers up, it performs a series of database verification tests. If any
of the seven databases in the controller’s memory have been corrupted in any
way, this test will detect it. If any problems are seen, the unit will display an
error screen, as shown in the next figure. Any databases that have problems
are listed on this screen. The only way to proceed to a running state is to
acknowledge this error screen by pressing the CLE AR button. Any of the
controller databases may be seen to be corrupt: Controller, Coordination, Time
of Day, Preemption, Option, Special, and BIU I/O Mapping.
Note The BIU I/O Mapping database error message will not appear
(even if there is corruption in this database area of memory) unless
I/O mapping is currently configured to be ACTIVE.
[Controller] [Coordination]

Figure 353 – Power-on Self Test Error Message

If this window appears, press the CLEAR key to go ahead and start the
controller.
13. If any database errors were detected, you will need to load good files into the
controller before using the controller to run an intersection. This can be done
by choosing to load default databases (MM > 3. Change Data > 8. Utilities > 1.
Default Data Load menu,) or you can load a good set of databases from
CLMATS, an EPROM card, or by using a Pocket PC handheld device with the
Pocket Central utility software loaded. Or, of course, you also have the option
of reprogramming the controller using the keyboard interface.
If there were no database errors detected, proceed to the next step.
14. Press 1 for Dynamic Displays.
15. Press 1 for Controller Func(tions).
16. Examine the Normal Status screen for proper operation and cycling.
17. If everything appears to operating normally, return the intersection to normal
operation.*
*
In the past, customers have also been told to clear any central overrides that may be active in the controller
whenever attempting to create a ‘Healthy Controller’ situation. If overrides are an issue, the clearance
process has changed, as described on page 29.

Updating the Modem Setup String

Significant improvements were made to the 3000 Series communications processing
logic in the version 3.6 firmware. As a result of this, after performing a firmware
upgrade, a couple of changes should be made to the modem setup string for the
controller (if your controller uses an attached modem for communications with
CLMATS.)
To change the setup string, you will need to go to the Communications & System
Setup Menu (MM > 3. Change Data > 5. Comm/System Setup.) On this menu, select
option 2. Comm Setup, and then page down to the third screen. (These Com Setup
screens also changed in firmware v3.6, as is described in the Firmware v3.6 release
notes.
The following changes should be made to the string:
Auto answer must be OFF. Previously it was ON for 3000 series controllers, but
with the new firmware, answering the modem is handled by the controller
firmware rather than by the modem. (typically: ‘S0=0’)
Error correction should now be set to ON. In the past, we had recommended
that it be turned OFF. (The commands are ‘&M4’ for U.S. Robotics modems
and ‘\N2’ for LPM modems.)

I/O STEERING
I/O Steering allows outputs to be logically re-configured to other than the normal
NEMA defaults. This feature could be used in either TS 1 or TS 2 Type 2 Mode. One
of the more likely uses is to provide operation called phases as overlaps. For
example, if it is desired to operate phase 1 as a left turn overlap on a 5-section head,
then overlap A can be steered to the phase 1 load switch driver outputs without
revising cabinet wiring. Output steering is also useful for accessing overlaps E-P or
ped overlaps, which have no dedicated outputs normally assigned to them.
To access I/O steering, navigate to the Change Data menu and choose option 7.I/O
Steering. (The full path is: MM > 3.Change Data > 7.I/O Steering)
Output (Signal Head) Steering Programming

Output steering applies to vehicle, pedestrian, and overlap signal outputs. Signals are
steered in groups of three; green-yellow-red or Walk-PCL-Don't Walk. Individual
indications (e.g., phase 1 green) cannot be steered by themselves.
All of the normal vehicle, ped, and overlap outputs from the MS-A, B and C are
available, as are any additional outputs on custom D modules. In addition, the on,
next, and check outputs are available for signal steering. If these outputs are used,
the ons will be used for green and walk, the next for yellow and ped clearance, and
checks for red and don't walk.
In TS 2, these functions remain available for TS 2, Type 2 only.
>>Program Signal Head Configurations

Before Enabling Signal Head Program.<<
Enable Signal Head Program: Y

(N = NEMA Configuration)
PgDn for Signal Head Programming

>> Signal Head Programming of 0=NEMA <<
Figure 354 – I/O Steering setup screen - page 1
To program output (signal head) steering, it is best to first disable the function by
putting a ‘N’ on the enable line of the first page. After programming has been
completed, return to this screen to enable the new configuration.

I/O Steering
Press PGDN to access the signal programming screens.
1: 0 2: 0 3: 0 4: 0
Phase Sig 5: 0 6: 0 7: 0 8: 0
Heads: 9: 0 10: 0 11: 0 12: 0
(0-80) 13: 0 14: 0 15: 0 16: 0
1: 0 2: 0 3: 0 4: 0
Ped Sig 5: 0 6: 0 7: 0 8: 0
Heads: 9: 0 10: 0 11: 0 12: 0
(0-80) 13: 0 14: 0 15: 0 16: 0
PGDN to go to Overlaps & Pedestrian Overlaps.
A: 0 B: 0 C: 0 D: 0
O/L Sig E: 0 F: 0 G: 0 H: 0
Heads: I: 0 J: 0 K: 0 L: 0
(0-80) M: 0 N: 0 O: 0 P: 0
A: 0 B: 0 C: 0 D: 0
Ped O/L E: 0 F: 0 G: 0 H: 0
Heads: I: 0 J: 0 K: 0 L: 0
(0-80) M: 0 N: 0 O: 0 P: 0
Choose PGDN again to see and assign phase 1 through 16 check/next/on values.
Each fixed number (or letter for overlaps) represents the destination pin set of the
output steering configuration. The corresponding programmable value represents the
source function of the steering configuration. A value ‘0’ (default) indicates the
destination is sourced from its standard signal driver, i.e. phase 1 is sourced from
phase 1, O/L A is sourced from O/L A, etc.
To implement steering, program a non-zero source code value next to the desired
destination. A table listing the codes is given below. This same information can also
be displayed by pressing the HELP key:
Table 49 – Output Steering source codes
Steering Code Signals
1-16 Normal phase outputs 1 - 16.
17-32 Pedestrian phase outputs 1 - 16.
33-48 Check (red), next (yel), on (grn) outputs phases 1-16
49-64 Vehicle overlap outputs A - P.
65-80 Pedestrian overlap outputs A - P

Output Steering Examples

Example 1. Phases as Overlaps, steering O/L A to phase 1 driver:
1: 49 2: 0 3: 0 4: 0
PHASE SIG 5: 0 6: 0 7: 0 8: 0
HEADS: 9: 0 10: 0 11: 0 12: 0
(0-80) 13: 0 14: 0 15: 0 16: 0
1: 0 2: 0 3: 0 4: 0
PED SIG 5: 0 6: 0 7: 0 8: 0
HEADS: 9: 0 10: 0 11: 0 12: 0
(0-80) 13: 0 14: 0 15: 0 16: 0
Figure 357 – I/O Steering - Example 1
Phase 1 above (destination) is assigned with the code ‘49’ (source). Per the table
above, code ‘49’ represents ‘O/L A.’ The set of G, Y, R outputs normally referred to as
“phase 1” will now behave as overlap A.
Example 2. Bringing phase 9 out on phase 2 check next on:
CHECK 1: 0 2: 9 3: 0 4: 0
NEXT, ON 5: 0 6: 0 7: 0 8: 0
OUTPUTS 9: 0 10: 0 11: 0 12: 0
(0-80) 13: 0 14: 0 15: 0 16: 0
CHECK = RED, NEXT = YELLOW, ON = GREEN
Figure 358 – I/O Steering - Example 2

Phase 2 above (destination) is assigned with the code ‘9’ (source). Per the table code
9 represents ‘Phase 9.’ Phase 9 green, yellow, and red will now come out on phase 2
check/next/on outputs.
Using Overlaps in Output Steering

When a set of outputs is “steered” to a new destination set, it can actually be thought
of as “copied.” That is, the set of drivers associated with the source code remain
intact and continue to output the source code signal on their normal outputs (if they
normally have outputs associated with them). For instance, as a result of the
programming in example 1, overlap A comes out on phase 1, but continues to come
out on overlap A as well—unless the overlap A destination is modified. For this
reason when programming phases as overlaps, it is generally good practice to use
overlaps E and higher since these are not assigned to real outputs anyway. In this
way the useable overlaps A-D are not “used up.”
Note Rememeber to enable Signal Head steering after programming is complete.

Chapter 12 — TS 2 Type 1 Operation
This chapter explains how to set up a 3000 Series controller that has been configured with TS
2 Type 1 hardware and firmware. In particular, it describes how to route controller input and
output through Bus Interface Units within the cabinet. The following topics are discussed in
detail in this chapter:
An introduction to TS 2 Type 1 operation, on page 396.

The cabinet components of a Type 1 configuration, on page 397.
Default BIU Mappings, on page 400.
Activating/Deactivating BIU mapping, on page 406.
Configuring Input Mappings, on page 408.
Configuring Output Mappings, on page 410.
Loading default NEMA mappings, on page 410.
I/O mapping screen abbreviations, on page 413.

OVERVIEW
The NEMA standard defines a system to map the inputs and outputs of a TS 2
controller to the various internal functions of the controller. This I/O Mapping standard
has now been implemented in the TS 2 version of the 3000 Series firmware. This
section explains these new cabinet interconnection options for 3000 Series TS 2 Type
1 controllers. In particular, it discusses the usage of Bus Interface Units (BIUs) with a
3000 series controller and an MMU. It explains how to map the signals from the
controller's port 1 connector to the various BIU input and output pins.
The NEMA Standards for Controller Input and Output

The 3000 and 3000E Traffic Signal Controllers are available in several flavors,
meeting the requirements of the most common cabinet standards. The oldest
standard covered is the NEMA TS 1 standard. The 3000 Series are also available in
TS 2 Type 1 and Type 2 variants. The TS 2 firmware also now supports the NTCIP
communications protocol. But what exactly do all of these letters mean when one is
dealing with a controller out in the field, standing next to a busy roadway? A basic
description of these controller I/O standards follows. The rest of this chapter goes on
to describe one of them in particular; the use of a 3000 series controller in a TS 2
Type 1 cabinet.
TS 1
In a TS 1 cabinet, the connections to the cabinet hardware are made through three
standard, round, multi-pin connectors, typically labeled A, B, and C. These
connectors are military specification (aka 'MilSpec' or sometimes refered to by the
best known manufacturer of these parts: ‘Amphenol’) connectors. In a TS 1 controller,
the outputs of the controller are permanently connected to the pins on these three
connectors. The pin assignments for these connectors on a TS 1 type 3000 series
controller are listed on pages 438-442.
TS 2 Type 1
With the TS 2 standard, NEMA applied a more sophisticated method of connecting
the controller to the cabinet. Instead of hardwired pins, control inputs and outputs are
routed using high-speed serial instructions. The Type 1 standard replaces the three
TS 1 connectors with a single, 10-pin, round, power connector (usually labeled 'A')
and an RS-485 data port (labeled 'Port 1'). Instead of one pin for each function, data
is sent and received serially via this data port. Port 1 is also known as the SDLC port,
which stands for the Synchronous Data Link Control protocol. SDLC was defined by
IBM. In the Type 1 standard, data is routed through Port 1 to two or more Bus
Interface Units, or BIUs, and then to the rest of the cabinet and intersection hardware.
The power connector (port 'A') pins are defined on page 443. The Port 1 pins are
defined on page 459. Peek uses I/O codes to map input and output signals to the pins
on the BIUs. These codes are listed beginning on page 400 of this chapter, and page
404 describes how to create custom mappings.

Cabinet Components
TS 2 Type 2
The Type 2 variant of the TS 2 standard is a sort of hybrid between TS 1 and TS 2
Type 1. Internally, it uses the same communications protocols used in the TS 2 Type
1 controller to map the controller's outputs, but it maps them to the same three
MilSpec (MS-A, B, C) connectors that are used in a TS 1 controller. However, the TS
2 Type 2 controller also has the ability to move its outputs around on the pins of the
three connectors. This is known as "Signal Head Steering." A Type 2 controller may
also include the communications ports of a Type 1 controller to facilitate additional
data exchange between the controller, an MMU, detector racks, a master controller,
and a PC. The input and output mapping of a standard 3000 Series Type 2 controller
are listed on pages 444-445. Type 2 port configuration is described in Chapter 12:
“Comm and System Setup”.
CABINET COMPONENTS
A typical TS 2 Type 1 controller is designed to communicate with up to four terminal
and facility (T/F) BIU units, four detector (DET) BIUs, and one malfunction
management unit (MMU).
Figure 359 – Typical Connections to a TS 2 Type 1 controller

But most cabinets will require considerably less hardware. The simplest TS 2 Type 1
configuration for a typical cabinet would have only one BIU to route signal outputs
and pedestrian inputs, and an MMU to monitor operations.
Figure 360 – Simple TS 2 Type 1 configuration

Cabinet Components
BIUs
A Bus Interface Unit (BIU) is a standard piece of hardware in a TS 2 Type 1 cabinet
that acts as a communications interface between the controller, the backplane
(terminals, load switches, facilities, etc.), and the detector racks. Its functions include
accepting controller digital signals, routing and controlling load switch outputs, and
conditioning and converting call inputs coming to the controller from terminals,
facilities, and detectors. A BIU is defined as part of the NEMA TS 2 standard and
there are a variety of manufacturers of compatible BIU units in the industry. Any of
these will work with the 3000 Series TS 2 Type 1 controller as long as they have an
up-to-date version of firmware installed.
Row A
Row B
pin1A
TOP of card
Figure 362 – Peek’s BIU Card
The rear connector of the BIU is where the

cabinet inputs and outputs are connected.
Each rear connector has two vertical rows of
32 pins, with the rows labeled 'A' and 'B'. In
the standard, Pin 1A is defined to appear at
the top right when looking at the back of the
card from the rear. From this angle, the B
row of pins is on the left side.
Figure 361 – Pins on a BIU card

MMU
An MMU, such as Peek Traffic's “Double Diamond” Malfunction Management Unit,
compares the output of the controller to the actual signals at the field terminals. It has
a customized Programming Card installed in the slot at the lower left corner of the
unit. The MMU uses this to check the operation of the controller and the various
signal lines for conditions that cannot be allowed to occur in the intersection. The
controller also double-checks the operation of the MMU. If a problem is detected,
either the MMU or the controller can then place the intersection into the Flash state.
DEFAULT BIU INPUT/OUTPUT MAPPING

By default, a 3000 Series controller that has been configured for TS 2 Type 1
operation will route its inputs and outputs through Port 1 using these I/O Codes,
which correspond to the following BIU pins.
Table 50 – I/O Mapping Codes for BIUs 1 and 2
BIU 1 Pins I/O Code NEMA Functions BIU 2 Pins I/O Code NEMA Functions
2a 1021 Ch 1 Red Driver (O) 2a 2021 Ch 9 Red Driver (O)
2b 1022 Ch 1 Yellow Driver (O) 2b 2022 Ch 9 Yellow Driver (O)
3a 1031 Ch 1 Green Driver (O) 3a 2031 Ch 9 Green Driver (O)
3b 1032 Ch 2 Red Driver (O) 3b 2032 Ch 10 Red Driver (O)
4a 1041 Ch 2 Yellow Driver (O) 4a 2041 Ch 10 Yellow Driver (O)
4b 1042 Ch 2 Green Driver (O) 4b 2042 Ch 10 Green Driver (O)
14a 1141 TBC Auxiliary 1 (O) 14a 2141 TBC Auxiliary 3 (O)
14b 1142 TBC Auxiliary 2 (O) 14b 2142 Free / Coord Status (O)
15a 1151 Preempt 1 Status (O) 15a 2151 Preempt 3 Status (O)
15b 1152 Preempt 2 Status (O) 15b 2152 Preempt 4 Status (O)
16a 1161 Preempt 1 Detector (I) 16a 2161 Preempt 5 Status (O)
16b 1162 Preempt 2 Detector (I) 16b 2162 Preempt 6 Status (O)
17a 1171 Test A (I) 17a 2171 Preempt 3 Detector (I)
17b 1172 Test B (I) 17b 2172 Preempt 4 Detector (I)
18a 1181 Automatic Flash (I) 18a 2181 Preempt 5 Detector (I)

Default BIU Input/Output Mapping
18b 1182 Dimming Enable (I) 18b 2182 Preempt 6 Detector (I)
19a 1191 Manual Control Enable (I) 19a 2191 CNA II (I)
19b 1192 Interval Advance (I) 19b 2192 Spare
20a 1201 Min Recall all Phases (I) 20a 2201 Spare
20b 1202 External Start (I) 20b 2202 Spare
21a 1211 TBC On Line (I) 21a 2211 Spare
21b 1212 Stop Time Ring 1 (I) 21b 2212 Inhibit Max Ring 1 (I)
22a 1221 Stop Time Ring 2 (I) 22a 2221 Inhibit Max Ring 2 (I)
22b 1222 Max II Ring 1 (I) 22b 2222 Local Flash Status (I)
23a 1231 Max II Ring 2 (I) 23a 2231 MMU Flash Status (I)
23b 1232 Force Off Ring 1 (I) 23b 2232 Alarm 1 (I)
24a 1241 Force Off Ring 2 (I) 24a 2241 Alarm 2 (I)
24b 1242 CNA I (I) 24b 2242 Free (I)
25a 1251 Walk Rest Modifier (I) 25a 2251 Test C (I)
25b 1252 Opto Ped Detector 1 (I) 25b 2252 Opto Ped Det 5 (Sig
Plan A) (I)
26a 1261 Opto Ped Detector 2 (I) 26a 2261 Opto Ped Det 6 (Sig
Plan B) (I)
26b 1262 Opto Ped Detector 3 (I) 26b 2262 Opto Ped Detector 7 (I)
27a 1271 Opto Ped Detector 4 (I) 27a 2271 Opto Ped Detector 8 (I)
In the standard NEMA TS 2 Type 1 mapping, BIUs 1 through 4 are used for terminal
and facilities connections, with BIU01 providing the core critical connections, such as
signal outputs and pedestrian and preemption inputs. BIU02 expands these
capabilities for more signals and detectors.

BIUs 3 and 4 provide more phase and status information connections.

BIU 3 Pins I/O Code NEMA Function BIU 4 Pins I/O Code NEMA Function
2a 3021 Timing Plan A (O) 2a 4021 Phase 1 On (O)
2b 3022 Timing Plan B (O) 2b 4022 Phase 2 On (O)
3a 3031 Timing Plan C (O) 3a 4031 Phase 3 On (O)
3b 3032 Timing Plan D (O) 3b 4032 Phase 4 On (O)
4a 3041 Offset 1 (O) 4a 4041 Phase 5 On (O)
4b 3042 Offset 2 (O) 4b 4042 Phase 6 On (O)
5a 3051 Offset 3 (O) 5a 4051 Phase 7 On (O)
5b 3052 Automatic Flash Status (O) 5b 4052 Phase 8 On (O)
6a 3061 Syst Spec Function 1 (O) 6a 4061 Phase 1 Next (O)
6b 3062 Syst Spec Function 2 (O) 6b 4062 Phase 2 Next (O)
7a 3071 Syst Spec Function 3 (O) 7a 4071 Phase 3 Next (O)
7b 3072 Syst Spec Function 4 (O) 7b 4072 Phase 4 Next (O)
8a 3081 Reserved 8a 4081 Phase 5 Next (O)
8b 3082 Reserved 8b 4082 Phase 6 Next (O)
9a 3091 Reserved 9a 4091 Phase 7 Next (O)
9b 3092 Status Bit A Ring 1 (O) 9b 4092 Phase 8 Next (O)
10a 3101 Status Bit B Ring 1 (O) 10a 4101 Phase 1 Check (O)
10b 3102 Status Bit C Ring 1 (O) 10b 4102 Phase 2 Check (O)
11a 3111 Status Bit A Ring 2 (O) 11a 4111 Phase 3 Check (O)
11b 3112 Status Bit B Ring 2 (O) 11b 4112 Phase 4 Check (O)
12a 3121 Status Bit C Ring 2 (O) 12a 4121 Phase 5 Check (O)
12b 3122 Red Rest Ring 1 (I) 12b 4122 Phase 6 Check (O)
13a 3131 Red Rest Ring 2 (I) 13a 4131 Phase 7 Check (O)
13b 3132 Omit Red Clear Ring 1 (I) 13b 4132 Phase 8 Check (O)
14a 3141 Omit Red Clear Ring 2 (I) 14a 4141 Address Bit 0 (I)
14b 3142 Ped Recycle Ring 1 (I) 14b 4142 Address Bit 1 (I)
15a 3151 Ped Recycle Ring 2 (I) 15a 4151 Address Bit 2 (I)
15b 3152 Alternate Sequence A (I) 15b 4152 Address Bit 3 (I)
16a 3161 Alternate Sequence B (I) 16a 4161 Address Bit 4 (I)
16b 3162 Alternate Sequence C (I) 16b 4162 Spare
17a 3171 Alternate Sequence D (I) 17a 4171 Spare
17b 3172 Phase 1 Omit (I) 17b 4172 Spare
18a 3181 Phase 2 Omit (I) 18a 4181 Spare
18b 3182 Phase 3 Omit (I) 18b 4182 Spare
19a 3191 Phase 4 Omit (I) 19a 4191 Reserved
19b 3192 Phase 5 Omit (I) 19b 4192 Reserved
20b 3202 Phase 7 Omit (I) 20b 4202 Reserved
21b 3212 Phase 1 Hold (I) 21b 4212 Phase 1 Ped Omit (I)
22a 3221 Phase 2 Hold (I) 22a 4221 Phase 2 Ped Omit (I)
25b 3252 Opto In Timing Plan A (I) 25b 4252 Opto In Offset 1 (I)

26a 3261 Optp In Timing Plan B (I) 26a 4261 Optp In Offset 2 (I)
26b 3262 Opto In Timing Plan C (I) 26b 4262 Opto In Offset 3 (I)
27a 3271 Opto In Timing Plan D (I) 27a 4271 Spare
If used, BIUs 9, 10, 11, and 12 are installed into detector racks and provide inputs for
standard detectors, such as loop, WIM, or video detectors. Unlike the T/F BIUs, the default
definitions for detection BIUs only use 32 of the 64 backplane pins.
9b 9092 Channel 1 Call (I) 9b A092 Channel 17 Call (I)
10a 9101 Channel 2 Call (I) 10a A101 Channel 18 Call (I)
BIUs 11 and 12 provide another 32 detector inputs.

9b B092 Channel 33 Call (I) 9b C092 Channel 49 Call (I)
10a B101 Channel 34 Call (I) 10a C101 Channel 50 Call (I)

Note On BIUs 9, 10, 11, and 12, the detector outputs, such as Detector Reset Slots 1, 2,
3 and 4, are not mappable.
These are the default pin inputs and outputs for the eight available BIUs in a TS 2
Type 1 cabinet. If you wish to program the inputs/outputs of the BIUs to be something
other than what is shown in these four tables, refer to the next topic.
Customizing BIU Input and Output Mapping

BIU I/O Mapping allows the operator of a 3000 Series traffic controller to assign any
controller input or output to any physical BIU input or output pin. Outputs are always
directly assigned to BIU output pins. But for inputs, a given BIU input can be driven by
a logical combination of two other inputs, two other outputs, or an input and an output.
These “virtual” inputs and outputs can be combined to set the state of a BIU input
using one of six possible logical operators: AND, OR, NOR, NAND, AND-, or OR-.
Note A logical NOT can be achieved by using the OR- (the ‘OR NOT’) operator. To
achieve a signal inversion, place a 0 (zero) in the A input of the operator, and the
signal you wish to invert in the NOT B input. Since A is always OFF in this case,
the output is then just NOT B.
This flexibility allows a controller's seldom-used inputs and outputs to be reassigned

for additional input and output availability, or it can be used to reduce the number of
BIUs required in a given cabinet, and finally, it can give the user more power
compared to existing functions such as Dynamic Omits, Dynamic Recalls, etc.
Note The mapping of BIU inputs and outputs is NOT part of the NEMA TS 2 standard.
This is a modification of otherwise NEMA compatible hardware to perform a non-
standard function.
All of these mappings are done using four-digit I/O Mapping Codes which follow a
specific pattern, based on which BIU is being addressed and which pin and row on
that BIU is being used for the function. The previous section provided the default
mapping of I/O Codes to controller functions, but any input or output can be mapped
to nearly any BIU pin, with the exception that some pins are hard-designated as
inputs only, and some others are designated outputs only. See Table 57 (page 415)
for details on which pins can be mapped as inputs and which can be outputs.
Each Map code has four digits of the form XYYZ, where:
X = the BIU number. If using BIUs 10, 11, or 12, the codes are A, B, and C,
respectively. (To type an A on the 3000 interface: press SHIFT -0, to type a B:
SHIFT -1, and to type a C: SHIFT -2.)
YY = the pin number, from 01 to 32. Pins are numbered from the top of the card
to the bottom.
Z = the Row indicator, where Row A = 1 and Row B = 2
For example, if one wanted to map to the 12th pin in the B row of BIU 11, the I/O Mapping
Code to use would be B122.

All of the TS 2 Type 2 BIU I/O Mapping tools are controlled from a single menu under the
Change Data > Utilities menu. When navigating from the Main Menu of a 3000 Series
controller, press 3 > 8 > 9 to access the I/O Mapping Menu.
Note Option 9 (the I/O Mapping Menu) is only available on the Utilities menu of the TS 2
version of the 3000 Series firmware. The TS 1 version of the firmware does not have
an Option 9 on the Utilities menu.
BIU I/O Mapping (v2.0) Menu
1.Activate Mapping 5.Load Nema map

2.Clear BIU I/O Map 6.Copy MMU Channels
3.Input mapping 7.Copy to EEPROM
4.Output mapping 8.Copy from EEPROM
Figure 363 – I/O Mapping Menu (before activation)

If you select option 1 on this screen and activate BIU I/O Mapping, the screen will
change, displaying:
1.Deactivate Mapping 5.Load Nema map

MAPPING IS ACTIVE!
Figure 364 – I/O Mapping Menu (with mapping active)
Caution Selecting Items 1 or 2 on the above menu while the controller is

operating an intersection will cause an MMU Fault and place the
intersection in Flash. It is recommended that I/O Mapping be set up
in a bench environment only.
One other note about using the custom BIU I/O Mapping with a 3000 Series
controller: if you opt to use the custom input/output mapping feature, be aware that
the Dimming feature cannot be used. If a given output that normally drives a phase or
pedestrian indication is set to use dimming, and the output is mapped to provide a
different output, then the output would not be "steady". To avoid this possibility,
Dimming is ignored if I/O Mapping is active.

ACTIVATING/DEACTIVATING BIU I/O MAPPING

The default state is to have BIU I/O Mapping deactivated, as is indicated by the first
option on the BIU I/O Mapping Menu (Figure 363). This means that the TS 2 Type 1
controller will use the default mapping as shown in the "Default BIU Input Output
Mapping" tables (Table 50, Table 51, Table 52, and Table 53.) However, if you wish
to create a custom mapping for the BIU inputs and outputs, after all the map setting
changes have been made, the last step is to select option 1 on the I/O Mapping Menu
(M a i n M e n u > 3 > 8 > 9 ) to activate the mapping function.
Activating I/O Mapping

When you select the activation option, the following warning will appear:
WARNING:
The controller will remap all inputs and

outputs to reflect any changes made!
Press ENTER to proceed or MENU to cancel

Figure 365 – Warning message when Activating the User Map
If the ENTER button is pressed at this point, the controller will go ahead and activate
the custom mapping. (Press MENU instead to cancel out of this process.)
BIU I/O MAP LOADED
Press MENU key to exit this screen

Figure 366 – Status screen showing that the mapping has been activated

Activating/Deactivating BIU I/O Mapping
After the mapping has been activated, the I/O Mapping Menu will display a new,
rather understated message at the bottom:
BIU I/O Mapping Menu
1.Deactivate Mapping 5.Load Nema map

MAPPING IS ACTIVE!
Figure 367 – I/O Mapping Menu with the user's map activated
Deactivating the I/O Mapping

If a custom mapping is already implemented and you wish to deactivate it, first go to
the BIU I/O Mapping Menu
(M a i n M e n u > 3 > 8 > 9 ), verify that the bottom of the screen shows the
"MAPPING IS ACTIVE!" message. If you are sure that you do actually want to
deactivate the mapping, then select 1 . D e a c t i va t e U s e r M a p and press the
ENTER key.
Deactivating the user-defined mapping will return the 3000 Series controller to using
the factory default, i.e. NEMA-standard, BIU mapping scheme.
Clearing BIU I/O Mappings

The number 2 item on the BIU I/O Mapping Menu is the Clear BIU I/O Map control.
This command will clear out whatever is currently stored in the input and output map
fields, as well as the virtual input and output states in the controller, and replace them
with zeros. After selecting this command, a warning message appears:
WARNING:
The controller will clear the entire

BIU I/O map!

Figure 368 – Warning message when clearing the Input Map
If the user is certain that she wishes to clear these user-defined values, pressing the
ENTER button will erase them.

The following screen will verify that the data has been erased:
BIU I/O MAP CLEARED

Figure 369 – Verification of the cleared BIU mapping
CONFIGURING INPUT MAPPINGS

Selection 3 on the BIU I/O Mapping Menu displays a series of screens where input
signals can be assigned. To assign a signal to a pin, enter the code numbers for
Inputs and Virtual Inputs, or Virtual Outputs. Use the Y/N key to toggle between AND,
AND-, NAND, OR, OR-, and NOR on the logical operator line of the screen.
VD: Puts a vehicle call when activated
VD01 VD02 VD03 VD04 VD05 VD06 VD07 VDO8

Line 1 Input or Output 9092 9161 9102 9111 0 0 0 0
Logical Operator OR AND AND- OR- OR- OR OR OR
Line 2 Input or Output 9171 9162 4022 4071 9151 0 0 0
PGDN or PGUP for more inputs

Figure 370 – Input mappings
Here are some examples of how to use this screen:
1. Vehicle Detector 1 Input (VDø1) will be active when Vehicle Detector 1 Input
(9092) is active, OR when Vehicle Detector 16 Input (9171) is active.
(9161) AND Vehicle Detector 15 Input (9162) are both active.
(9102) is active AND Phase 2 is not active (4022, AND-). Here 4022 will be
entered in the Phase 2 On output field also. However , Phase 2 On can be
mapped to any available output pin on any BIU (See Table 57 on page 414.)
4. Vehicle Detector 4 Input (VDø4) shall be active when Vehicle Detector 4 Input
(9111) is active OR Phase 3 is not next (4071, OR-). Here 4071 will be
entered in Phase 3 Next Output field also, however Phase 3 Next can be
mapped to any available output pin on any BIU (See Table 57 on page 414.)

Configuring Input Mappings
5. Vehicle Detector 5 Input (VDø5) is the inverse of the Vehicle Detector 12 Input
(9151).
See page 413 for a table of the abbreviations used in these screens. (Table 55)
Using Logical Operators with Input Mappings

The programmable inputs of the BIUs can be programmed to respond to a pair of
logical inputs using one of these six logical operators. These operators specify what
signal will be reported to the controller, based on the logical state of each of the two
input sources.
Table 54 – Logical I/O Mapping operators
Operator Logical Meaning Description
AND (A AND B) If Line 1 AND Line 2 are ON, the Input is ON
AND- (A AND NOT B) If Line 1 is ON AND Line 2 is OFF, the Input is ON
NAND (NOT(A AND B)) If Line 1 is OFF AND Line 2 is OFF, the Input is ON
OR (A OR B) If either Line 1 OR Line 2 are ON, the Input is ON
OR- (A OR NOT B) If either Line 1 is ON OR Line 2 is OFF, the Input is ON
NOR (Neither A NOR B) If Line 1 is OFF AND Line 2 is OFF, the input is ON
Note To create a ‘NOT’ input using the above operators, simply use the OR- operator
and enter the signal to be inverted in the line 2 input. Then set line 1 to 0 (zero).
The output of this logical operation is just the inverse of the input signal.

CONFIGURING OUTPUT MAPPINGS

Selection 4 on the BIU I/O Mapping Menu displays a series of screens where the
output signals can be assigned. Unlike inputs, outputs are always simple one-to-one
assignments; outputs cannot be combined logically.
RD: Vehicle phase red signal
RD01 RD02 RD03 RD04 RD05 RD06 RD07 RDO8

1021 1092 1032 1062 0 0 0 0
PGDN for more outputs

Figure 371 – Output mapping assignments
In the example screen above, Phase 1 Red will come out on the Channel 1 Red
Output (1021), Phase 2 Red will come out on the Channel 6 Red Output (1092),
Phase 3 Red will come out on the Channel 2 Red Output (1032), and Phase 4 Red
will come out on the Channel 4 Red Output (1062).
Important In order for an Output to drive an Input it must first be programmed to an

available output pin. See Table 57 on page 414 for a listing of pin
availability.
LOADING A DEFAULT NEMA MAPPING

Menu option number 5 on the BIU I/O Mapping Menu sets the input and output I/O pin
mappings to those defined in the NEMA standard. This mapping is based on the
current channel assignments, using the following process:
1. The whole BIU I/O mapping is cleared. (i..e. all mappings between algorithm
inputs, outputs, and pins are erased.)
2. Non-channel outputs are mapped as defined by the NEMA standard.
3. Inputs are mapped as defined by the NEMA standard.
4. Channel outputs are mapped as defined by the NEMA standard. The channel
assignments displayed in the MMU Channel Assignments menu will be used.

Loading a Default NEMA Mapping
Before the default settings are loaded into the appropriate fields, the controller will
display a warning message.
WARNING:
The standard NEMA map will be loaded

into the BIU I/O map!

Figure 372 – Warning message when loading the default NEMA mapping
If the user accepts this process by pressing ENT ER , the controller will load the
mappings and display this screen:
NEMA MAP LOADED

Figure 373 – Verification of a successful load of NEMA defaults
Copying MMU Channels

Menu option number 6 on the BIU I/O Mapping Menu will copy the MMU channels, as
assigned in the MMU Channels Assignments menu, to the BIU I/O output map. The
I/O map codes will automatically be loaded into the appropriate fields. As usual, when
the Copy MMU Channels option is selected, the user will be presented with a warning
screen and an option to cancel the operation.
WARNING:
The channels as assigned in the

MMU Channel Assignments menu
will be copied into the BIU I/O map!

Figure 374 – Warning message when copying MMU channels

If the user accepts this process by pressing ENT ER , the controller will copy the
channels assignments and display this screen:
MMU CHANNELS LOADED

Figure 375 – Verification of successful copy of MMU channels to output
mappings
Copying the BIU I/O Map to an EEPROM Card

Commands 7 and 8 on the BIU I/O mapping screen allow an operator to copy a
customized I/O mapping from one controller to another, using an EEPROM card.
Selecting menu option 7 will copy the I/O mapping that is currently stored in memory
onto an EEPROM card (but only if a card is currently inserted into the controller’s
EEPROM card socket, of course.) If this option is chosen, a warning message similar
to those shown above will be displayed. Selecting ENT ER will proceed with the copy
process, while selecting MEN U will cancel it. A status screen will indicate when the
copy process has finished. Choose ME NU again to exit from this status screen.
Copying a Mapping from an EEPROM Card into the Controller

Selecting menu option 8 from the BIU I/O Mapping Menu will copy an I/O mapping
that is currently stored on an EEPROM card into the controller’s BIU I/O mapping
fields. Just as with the other commands on the BIU I/O Mapping Menu, a warning
message will be displayed. Selecting ENT ER will proceed with the copy process, while
selecting MEN U will cancel it. A status screen will indicate when the copy process has
finished. Choose MENU again to exit from this status screen.
However, if no valid I/O mapping data is found on the EEPROM card, the mapping
will not be copied and the following error message will be displayed:
NO VALID BIU I/O MAP ON EEPROM!
NO DATA COPIED!

Figure 376 – Warning message when EEPROM mapping data is missing or
corrupted

I/O Mapping Screen Abbreviations
I/O MAPPING SCREEN ABBREVIATIONS

Input and output mappings are configured on separate screens under the I/O
Mapping Menu, utilizing these abbreviations to indicate the source or target of each
signal.
Table 55 – Input Mapping Abbreviations
Abbreviation Description of Input
ALMn Alarm signals 1 through 8
ALTA Alternate sequences A through D
CNAn Call to non-actuated (1 and 2)
CNT Unit control signals
COI Coordination input signals
CYCn Cycle inputs (2 through 4)
DMD D-Module Inputs
DOOR Cabinet door open
EXTS External start
FLASH Flash status inputs
FOFF Force off, Ring n input function
FREE Free input
GRP2
HDnn Hold - Inhibits termination of green service, 1 through 16
IADV Interval advance
INHM Max timing inhibit, Ring n input function
LCLF Local flash status
MAX2 Alternate maximum timing, Ring n input function
MCE Manual control enabled
MINR Min Recall all phases
MMUF MMU flash status
OFFn Offset inputs 1-3
OPTn Optical Input signals, 3 through 8
ORCL Omit Red Clearance, Ring n input function
PDnn Puts a ped call when activated, Ped calls 1 through 16
PEDR Ped recycle, Ring n input function
POnn Pedestrian Omits 1 through 16
PRIn Preempt input signals 1 through 8
PR-n Phase reversals 1 through 8 (alternate sequence, Lead-Lag)
Rn Ring 1 through 4 input function screens
RRST Red rest, Ring n input function
RTCR Real-time clock reset
SPL2 Split input 2
STOP Stop timing, Ring n input function
TBCI Time of Day override input
TBnn Test bits, I/O mode bits, 1 through 8, but only 1-3 are used as test bits for
Ports A, B, & C.
UCFL Uniform code flash
VDnn Vehicle detected 1 through 64. Puts a vehicle call when activated.
VOID Input not used
VOnn Vehicle Omit (1 through 16)
WRM Walk rest modifier
XPED Exclusive pedestrian operation

Table 56 – Output Mapping Abbreviations

Abbreviation Description of Output
ACnn Active user-defined TOD circuits, 1 through 8
AFLS Automatic flash
AWLn Advanced Warning signals 1 through 8
CKnn Active when a call is present and the phase is not green, 1 through 16.
CYCn Cycle outputs 2, 3 & 4
DWnn Pedestrian don't walk signals 1 through 16
FREE Free output
GRnn Vehicle phase green signal
NXnn Next output, Active when selected as next phase, 1 through 16
OFFn Offset outputs 1 through 5
ONnn ON signal, Active when in green, yel or red-clr
PCnn Pedestrian clearance signals 1 through 16
POCA Ped Overlap Clearance signals A through P (1-16)
PODA Ped Overlap Don't walk signals A through P (1-16)
POWA Ped Overlap Walk signals A through P (1-16)
PRnn Preempt outputs 1 through 16
RDnn Vehicle phase red signals 1 through 16
SPLn Split outputs 1 through 5
ST-an Status bits for ports A, B, & C. (a = A, B, C.) (n = Rings 1-4.)
VOGa Vehicle Overlap Green signals A through P (1-16)
VOID Output not used
VORa Vehicle Overlap Red signals A through P (1-16)
VOYa Vehicle Overlap Yellow signals A though P (1-16)
WKnn Pedestrian Walk signals 1 through 16
YEnn Vehicle phase yellow signals 1 through 16
Input and Output Pin Mapping Options

Table 57 shows which of the BIU pins may be used as inputs, outputs, or either one.
The top block of pins are used for Outputs, but an internal status channel may be
mapped to these Output pins to logically activate the channel. However, that same
pin must be mapped to an Output function that will drive the logic. If mapping to one
of the detector BIUs (BIU09, 10, 11, or 12), this top block is not used.
The middle block of pins can be mapped to either Input or Output functions.
The bottom block of pins can only be assigned to Input functions. For example, if a
user attempts to assign Pin 22b (on any BIU) to Phase 1 Red, the entry will be
rejected by the controller.

I/O Mapping Screen Abbreviations
Table 57 – Input and Output Availability of BIU Pins

Pin BIU01 BIU02 BIU03 BIU04 Detector BIUs (09-12)
2a Output Output Output Output Not used (for mapping)
2b Output Output Output Output Not used (for mapping)
9b Output Output Output Output Input
10a Output Output Output Output Input
12b Output Output Input or Output Output Input
13a Output Output Input or Output Output Input
13b Output Output Input or Output Output Input
14a Output Output Input or Output Input or Output Input
14b Output Output Input or Output Input or Output Input
15a Output Output Input or Output Input or Output Input
15b Output Output Input or Output Input or Output Input
16a Input or Output Output Input or Output Input or Output Input
16b Input or Output Output Input or Output Input or Output Input
17a Input or Output Input or Output Input or Output Input or Output Input
17b Input or Output Input or Output Input or Output Input or Output Not used (for mapping)
18a Input or Output Input or Output Input or Output Input or Output Not used (for mapping)
21b Input Input Input Input Not used (for mapping)
22a Input Input Input Input Not used (for mapping)


Chapter 13 — Utilities
This section explains the utilities that are available for a 3000 Series controller, mostly dealing
with moving data and settings from one place to another. These controls also allow printing
and to restart the controller. The following topics are discussed in detail in this chapter:
An overview of the available utilities, on page 418.

Loading default settings into the controller, on page 419.
Transferring data between controllers, on page 420.
Clearing data logs, on page 420.
Copying data between RAM and the EEPROM, on page 421.
Restarting the controller, on page 422.
Printing logs on a printer attached to Port 2, on page 423.
Copying controller parameters between screens, on page 425.
Copying data and configuration files from a central computer, on page 428.

OVERVIEW
The Utilities Menu is not used for programming data, but allows the user to perform a
variety of functions related to database maintenance.
This menu can be accessed from the Main Menu by selecting option 3. Change Data
to open the Program Menu, and then selecting item 8. Utilities.
Utilities Menu
1.Default Data Load 6.Printer Menu

2.Transfer Menu 7.Copy Functions
3.Clear Logs 8.Request Download
4.EEPROM Copy 9.BIU I/O Mapping
5.Restart Machine
Figure 377 – Utilities Menu

The intent and usage of all of these commands are detailed in the rest of this chapter.
Option 9, BIU I/O Mapping, is described in Chapter 12 — TS 2 Type 1 Operation,
starting on page 404.

Default Data Load
DEFAULT DATA LOAD

This option allows the user to quickly load basic data into the controller. Each of the 5
data areas (Controller, Coordination, Time of Day, Preemption, and Enhanced
Options) can be loaded separately or all 5 can be loaded at once by selecting the ALL
option.
If controller default data is loaded, the machine will be programmed for a standard
dual-ring 8 phase quad sequence. Coordination loads 4 cycles with allocations typical
for the described phasing. Default timing parameters are provided to allow the
controller to cycle. The data that is loaded resembles the same data provided in a
new controller received from the factory. The user should review all settings before
using these settings in the street; default data is provided as a programming
convenience only.
Default Load Menu
1.Controller 4.Preemption
2.Coordination 5.Enh. Options
3.Time Of Day 6.All
>>TO CANCEL, PRESS MENU<<

Figure 378 – Default Data Load Menu
The Time of Day, Preemption, and Enh. Options commands load generic data,
consisting mostly of zero data. In essence, these are disabled, with zero
programming parameters.

TRANSFER MENU
This menu allows the user to copy some or all of the parameter database from one
controller to another through the EIA-232 port (Port 2). Options 1 through 5 copy the
selected areas to the remote unit, whereas the entire database is copied if option 6 is
chosen. Option 7 sets the time in the real-time clock of the remote unit to that of the
local controller.
Unit to Unit Transfer Menu
1.Controller 5.Enh. Options

2.Coordination 6.All Database
3.Time Of Day 7.Real Time
4.Preemption
>CHECKSUM FAILURES WILL ABORT TRANSFERS<

Figure 379 – Transfer Menu
Once a transfer has started, pressing the CLEAR key will abort the transfer. A 25-to-
25 pin, male-male, null modem cable (Peek part number 4917,) or a 9-to-25 pin,
male-male, null modem cable (Peek part number 4916) is required for this function.
CLEAR LOGS
CLEAR LOGS(Y/N)
PATTERN CHANGE: DETECTOR FAIL:

EVENTS: KEYBOARD:
MOE: VOLUME:
MMU FAULTS:
Figure 380 – Clear Logs screen

This option allows the user to selectively clear the controller's: pattern change logs,
event logs, MOE logs, MMU fault logs, detector failure logs, keyboard logs or volume
logs. To clear a log, move the cursor to the selected log and enter a ‘Y‘ (Press the Y / N
key, then either move off the field using the arrow keys or press ENTER .)
There is no onscreen feedback to indicate that a log has been cleared.

EEPROM - RAM Copy
EEPROM - RAM COPY

This function allows the user to copy all data stored in the EEPROM module into main
system RAM (loading stored data) or to copy main system RAM to the EEPROM
module (backing up data). Enter a ‘Y’ by pressing the Y/N key then ENTER next to
the desired function. The data transfer will occur immediately.
If there is no EEPROM module installed in the controller, an error tone will sound to
indicate that no data transfer occurred. If the restart is successful, the message ”Copy
Completed” will appear on the bottom of the screen.
If an EEPROM is installed in the controller and an error message (beep) sounds, then
the most likely problem is that the EEPROM was not installed during power-up and
therefore has not been recognized. Restart the controller and try the copy function
again.
EEPROM<--)RAM Copying
Copy from EEPROM to RAM:

Copy from RAM TO EEPROM:

Figure 381 – EEPROM-RAM Copy screen
This feature allows data to be transferred from one controller to another by copying
the data to EEPROM on the source machine and loading to RAM on the destination
controller.

RESTART MACHINE
This function performs a “soft reboot” of the controller. The controller will drop CVM
and restart all controller operations (identical to a power-up start). Restart is required
for sequence and overlap database changes to take effect. This “internal” Restart is
an alternative to a “hard” power on/off Restart or External Start.
Caution Caution should be used when performing a restart, especially if the

intersection is currently operating in a non-Flash mode, as the restart
will cause a Flash condition followed by the programmed Start-Up
sequence.
Restart Machine
Press (Y/N) to restart machine
>>WARNING: MACHINE WILL GO TO START-UP

PHASES AFTER RED REST WHEN EXECUTED.<<
PRESS MENU TO CANCEL

Figure 382 – EEPROM-RAM Copy screen
To restart the controller, press the Y/N key; to cancel the restart operation, press
MENU .

Printer Menu
PRINTER MENU
This menu allows you to print out various portions of the 3000 series databases and
log files to a serial printer attached to Port 2.
1.Printer Setup 9.MOE Log
2.Controller 10.Not Used
3.Coordination 11.Volume Log
4.Time of Day 12.Not Used
5.Preemption 13.Detector Failures
6.Enh. Options 14.Event Log
7.Not Used 15.Keyboard Log
8.All database 16.Pattern Change Log
Figure 383 – Printer Menu
Item 1 was a configuration screen that is no longer used, but items 2 through 16
specify which part of the controller’s memory will be sent out as a serial data stream
to Port 2.
This function assumes that there is a serial printer that can print at least 40 columns
of text attached to the controller at Port 2. For this to function properly, Port 2 must be
properly configured, based on the requirements of the printer attached, using the Port
Setup screens under the Comm/System Setup menu. (MM > 3.Change Data >
5.Comm/System Setup menu > 2.Comm Setup)
Printer Setup
This command is no longer used. Prior to firmware version 3.6, this command was
used to set up Port 2 as a printer port, however now that Ports 2 and 3 have generic
setup parameters defined on the Comm Setup screen, a printer attached to either
Port 2 or Port 3 will simply use the port’s assigned values to communicate with an
attached serial printer.
Consequently, this command now opens a window displaying Help text describing
this change.

Printing Portions of the Controller Database

1.Printer Set-Up 9.MOE Log
2.Controller 10.Not Used
3.Coordination 11.Volume Log
4.Time Of Day 12.Not Used
5.Preemption 13.Detector Failures
6.Enh. Options 14.Event Log
7.Not Used 15.Keyboard Log
8.All Database 16.Pattern Change Log
Figure 384 – Printing portions of database or logs
Any of the various programming areas may be printed individually by entering the
appropriate number. Printing will begin immediately after you make the selection. The
entire database can be printed by pressing 8. In addition to portions of the database,
the various logs can also be printed using options 9 - 16. To select menu items 10
through 19, press the SHIFT key and a number between 0 and 9 (e.g. SHIFT -0 = 10,
SHIFT -1 = 11, etc.) After choosing any of the database or log items to print, the
display will show the following status screen.
Items 7, 10, and 12 do not generate any output.
Data presently being Printed
>>TO TERMINATE PRINTOUT: PRESS CLEAR<<

Figure 385 – Print-out status display
If you wish to halt the print-out, or you pressed a print option by mistake, just press
the CLE AR button to halt the printout and return to the Printing Menu (above).

Copy Functions
COPY FUNCTIONS
This feature allows portions of the controller's database to be copied to other areas,
thus reducing the amount of data that must be entered manually through the
interface. For example, if timing plan 2 is identical to timing plan 1 except for a few
values, it would be much easier to copy plan 1 to plan 2, then modify only the
parameters that were different.
Copy Functions Menu
1.Controller 3.Time of Day

2.Coordination 4.Preemption
Figure 386 – Copy Functions Menu

The commands on this menu allow you to copy different parts of the database
separately. Selecting each of these commands will take you to a screen that will allow
you to more carefully control the copy process.
Controller
CONTROLLER COPY
COPY TIMING PLAN X TO TIMING PLAN Y:

(VALUE: XY, X = 1-4, Y = 1-5, 5=ALL)
COPY PHASE 1 TIMES TO ALL PHASES:

COPY PHASE 1 TO ODD, PHASE 2 TO EVEN:
(VALUE: 1-4= TIMING PLAN, 5= ALL PLANS)
Figure 387 – Controller Copy screen
There are three options in the controller section of the database. The first allows the
user to copy all data associated with one timing plan to another timing plan. To do so,
move the cursor to the top line and enter a two digit number in which the first digit is
the timing plan to copy from and the second digit is the timing plan to copy to. In the
case of the destination timing plan, the value ‘5’ will copy the source timing plan to all
of the other timing plans.
The second copy mode copies timing parameters from phase 1 to all other phases.
The third mode copies timing parameters from phase 1 to all odd phases and phase 2
to all even phases. To perform one of these functions, move the cursor to the
appropriate line and enter the timing plan number of the data to be copied. A value of
5 will copy all 4 timing plans.
Pressing ENTER will trigger the copy function.

Coordination Copy
COORDINATION COPY
COPY SPLIT PLAN XX TO SPLIT PLAN YY: _
(VALUE: XXYY, XX=1-24, Y=01-25, 25=ALL)
COPY CYCLE X SPLIT PLANS TO CYCLE Y:

(VALUE: XY, X= 1-6, Y= 1-7, 7= ALL)
>>CYCLE 1-6= SPLIT PLANS 1-4, 5-8, 9-12,
13-16, 17-20, 21-24 RESPECTIVELY<<
Figure 388 – Coordination Copy screen
In the coordination database area there are two copy functions available. The first
allows the user to copy phase allocation values from one split plan to another. In this
case, a 4 digit value should be entered, the first two digits specify the source split plan
and the second two define the destination split. If the source split is less than 10, the
leading zero need not be entered, but it is required for the destination split plan. A
value of 25 for the destination split plan specifies all splits.
The other copy function available in the coordination section copies all splits of one
cycle to all splits of another. Enter 2 digits: the first is the source cycle, and the
second is the destination cycle. A value of 7 for the destination specifies all cycles. 4
splits per cycle is assumed for the purposes of this feature, therefore a value of 12 will
copy splits 1-4 to splits 5-8.
Time of Day Copy

TIME OF DAY COPY
COPY DAY PLAN XX TO DAY PLAN YY:

(VALUE: XXYY, XX=1-32, Y=01-32)
Figure 389 – Time of Day Copy screen

There is only one option under Time of Day Copy: it copies one day plan to another.
Enter 4 digits where the first two define the source day plan, and the second two the
destination. If the source day plan is less than 10, the leading zero is optional, but it is
required if the destination day plan is less than 10.

Copy Functions
Preemption Copy
PREEMPTION COPY
COPY PREEMPTION RUN X TO RUN Y: _

(VALUE: XY, X= 1-6, Y= 1-6)
Figure 390 – Preemption Copy screen

The lone preemption copy function copies one preemption run to another one. Enter a
two digit value, the first is the source preemption run, and the second is the
destination run. Pressing ENTER will trigger the copy function.

REQUEST DOWNLOAD
This allows a user to request a full controller database download from the central
computer. Note that the controller will need to be in a networked system to use this
feature. Field requested downloads from isolated intersections are only supported by
Smartways™ closed loop software (Version 3.5 and higher), CLMATS™ software
(Version 2.0 and higher), and in the 3000 series software (Version 2.6 and higher.)
Field Requested Download VALUE(YES/NO)
Enter ‘Y‘ For Download:
>>USE CLEAR KEY TO TERMINATE REQUEST>>
Figure 391 – Field Requested Download screen
BIU I/O MAPPING

This area of controller setup concerns configuring the communications of the
controller when it is operating in TS 2 Type 1 mode. These features are described in
detail in Chapter 12: TS 2 Type 1 Operation, starting on page 395.
1.Activate mapping 5.Load Nema map

3.Input Mapping 7.Copy to EEPROM
Figure 392 – BIU I/O Mapping Menu (v2.0)

Appendix A — Time of Day
Circuit Descriptions
This section explains the circuits (both physical and logical) used by the 3000 Series for Time
of Day planning and operation. The following topics are discussed in detail in this appendix:
TOD Circuit definitions, on page 430.

Notes on the TOD Circuits, on page 431.

Appendix A — Time of Day Circuit Descriptions
TOD CIRCUIT DESCRIPTIONS

Table 58 – TOD circuit assignments
Ckt # Symbol Description Ckt # Symbol Description
1 CY2 Cycle 2 99 DSD Det. Switching Disable
2 CY3 Cycle 3 100 CDD Copy Det. Disable
3 CY4 Cycle 4 101 VDD Vol. Density Disable
4 SL2 Split 2 102 DDD Delay Det. Disable
5 SL3 Split 3 103 SDD Stretch Det. Disable
6 OF1 Offset 1 104 SBD Stop bar Det. Disable
7 OF2 Offset 2 105 IM1 Inhibit Max Ring 1
8 OF3 Offset 3 106 IM2 Inhibit Max Ring 2
9 OF4 Offset 4 107 CTC Call to Time Clock
10 OF5 Offset 5 108 EP1 Exclusive Ped 1
11 FRE Free 109 EP2 Exclusive Ped 2
12 UCF UCF, Auto Flash 110 DSM Disable Split Matrix
13 TP1 Timing Plan 1 111 DDE Disable Dual Entry
14 TP2 Timing Plan 2 112 FRO Free Override
15 TP3 Timing Plan 3 113-120 UD1-8 User Defined Outputs 1-8
16 TP4 Timing Plan 4 121 PH2 Use Alternate Phone No.2
17-25 VO1-9 Vehicle Omit 1-9 122 DP2 Activate Detector Plan 2
26-32 O10-16 Vehicle Omit 10-16 123 DP3 Activate Detector Plan 3
33-41 PO1-9 Ped Omit 1-9 124 3CD Third Car Detection
42-48 P10-16 Ped Omit 10-16 125 EVL Enable Volume Logging
49-57 MR1-9 Max Recall 1-9 126 EML Enable MOE Logging
58-64 M10-16 Max Recall 10-16 127 ASC Adaptive Split Control
65-72 LL1-8 Lead/Lag Pattern 1-8 128 DCP Disable Conditional Ped
73 CN1 CNA 1 129 EDP Enable Dual Ped
74 CN2 CNA 2 130 APM Auto Permissive enable
75 CN3 CNA 3 131 MPM Manual Permissive enable
76 CN4 CNA 4 132 N/U Not Used
77 WRM Walk Rest Modifier 133 IPM Inhibit Pedestrian Override
78 MIN Min Recall All Phs 134-144 N/U Not Used
79 DIM Dimming 145-160 VC1-16 Min Recall phases 1-16
80 CVS Conditional Service 161-176 PC1-16 Ped Recall phases 1-16
81 TIA Test Input A 177 OLA Overlap A inhibit
82 TIB Test Input B 178 OLB Overlap B inhibit
83 TIC Test Input C 179 OLC Overlap C inhibit
84 N/U NOT USED 180 OLD Overlap D inhibit
85 N/U NOT USED 181 OLE Overlap E inhibit
86 N/U NOT USED 182 OLF Overlap F inhibit
87 PR1 Ped Recycle Ring 1 183 OLG Overlap G inhibit
88 PR2 Ped Recycle Ring 2 184 OLH Overlap H inhibit
89 OR1 Omit Red Clr Ring 1 185 OLI Overlap I inhibit
90 OR2 Omit Red Clr Ring 2 186 OLJ Overlap J inhibit
91 RR1 Red Rest Ring 1 187 OLK Overlap K inhibit
92 RR2 Red Rest Ring 2 188 OLL Overlap L inhibit
93 M21 Max 2 Ring 1 189 OLM Overlap M inhibit
94 M22 Max 2 Ring 2 190 OLN Overlap N inhibit
95 DM3 Disable Max 3 191 OLO Overlap O inhibit
96 GR2 Group 2 Input 192 OLP Overlap P inhibit
97 POM Pedestrian Override Mode 193-255 N/U Not Used
98 SFL Soft Flash

Notes on the Definitions
NOTES ON THE DEFINITIONS

Most circuits are self-explanatory. For example, ‘Walk Rest Modifier’ (#77), ‘Red Rest’
(#91-92), and ‘Inhibit Max’ (#105-106) perform the same functions as the hardware
inputs of the same names. A few circuits, however, need some explanation.
The Free circuit (FRE, #11) initiates free operation, but only if the free source is
programmed for TOD (see Coord Operating Modes). This differs from the Free
Override circuit (FRO, ckt 112), which always causes the controller to go into free
operation. It operates like the Free Override hardware input.
Similarly, the Call to Time Clock circuit (CTC, #107) forces the controller into TOD
operation regardless of the sourcing parameters.
Circuits 113 through 120 (UD1 - UD8) are user-definable hardware outputs that can
be used for any purpose desired. These outputs are available on certain ‘D’ modules
for TS 1 and TS 2, Type2, Mode 7 controllers.
Circuits 122 and 123 (DP2 & DP3) activate alternate detector plans 2 and 3. User
defined circuits (UD 1 through 3) are routed on the appropriate BIUs for TS 2 Type 2
controllers.
The Inhibit Circuits (177-192) modify an overlap to appear only with 'modifier phase
parent phases'. If there are no 'modifier phase parent phases', the overlap remains
red.

Appendix A — Time of Day Circuit Descriptions

Appendix B — Preemption
Programming Forms
This section provides two forms that aid in preemption programming of the 3000 or 3000E
Traffic Controller:
Preemption Programming Form 1, on page 434.

Preemption Programming Form 2, on page 435.

Appendix B — Preemption Programming Forms
PREEMPTION PROGRAMMING FORMS
Preemption Form 1
RUN INTERVALS MIN. ENTRY TIMES

RR GREEN INH. DCL O/L ON ENTRY
LOCK DURATION YELLOW
OVERRIDE DELAY RED EXIT MODE
NEMA PRI. RE-SERVICE PED CL
PRIORITY O/L YEL
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
EXIT PHS
EXIT CALLS

Preemption Programming Forms
Preemption Form 2

Appendix B — Preemption Programming Forms

Appendix C — 3000/3000E Connector Pins
This section provides details about the purpose of each pin on each of the available ports on a
3000 or 3000E controller. The following ports are described in this appendix:
“A” connector, on page 438.

“B” connector, on page 440.
“C” connector, on page 442.
“A” connector on a TS 2 Type 1 controller, on page 443.
Connectors “A”, “B”, and “C” on a TS 2 Type 2 controller, on page 444.
“D” module connectors: Closed Loop D Module, on page 446.
“D” module connectors: Twelve Phase D Module, on page 449.
“D” module connectors: LMD D Module, on page 452.
“D” module connectors: Texas D Module, on page 454.
“D” module connectors: Las Vegas D Module, on page 457.
Port 1 communications connector, on page 459.
Auxiliary communications connector, on page 460.

PIN ASSIGNMENTS: MS-A CONNECTOR (TS 1 CONTROLLERS)

Pin Function Description I/O
A Fault Monitor Optional, used in TS 2 mode only --
B +24VDC 24 Volt D.C. output. O
C CVM The Controller Voltage Monitoring signal is present here when the O
controller is not in UCF Flash, no checksum failures are present,
and operating voltages are all good.
D φ1 Red Vehicle Phase 1 Red signal. O
E φ1 Don't Walk Pedestrian Phase 1 Don't Walk signal. O
F φ2 Red Vehicle Phase 2 Red signal. O

G φ2 Don't Walk Pedestrian Phase 2 Don't Walk signal. O
H φ2 Ped Clr Pedestrian Phase 2 Ped Clearance signal. O
J φ2 Walk Pedestrian Phase 2 Walk signal. O
K Detector 2 Puts call on phase assigned to detector 2 when activated. I
L Ped. Det. 2 Puts a ped call on phase 2 when activated. I
M φ2 Hold When controller is not in CNA mode, activating this input inhibits I
termination of Green service to vehicle Phase 1, and inhibits
concurrent ped. service recycle. When in CNA mode, termination of
Walk is inhibited.
N Ring 1 Stop Time Suspends all interval timing for ring 1. I
P Ring 1 Inhibit Max Prevents max termination of ring 1 vehicle phases when extending. I
Term
R External Start Initiates start up sequence. I
S Interval Advance Provides manual advance of controller sequencing. If MCE is active, I
clearance intervals will be timed.
T Ind. Lamp Control LCD backlight control / Door Open Event I
U AC Neutral Common lead of AC supply AC -
V Chassis Ground Chassis ground Cgnd
W Logic Ground DC I/O logic ground reference Lgnd
X Flashing Logic Alternating True/False output at 1 pulse per second, 50% duty cycle. O
Y Ring 1 Status Bit C Coded Status Bit C for ring 1. O
Z φ1 Yellow Vehicle Phase 1 Yellow signal. O
a φ1 Ped Clr Pedestrian Phase 1 Ped Clearance signal. O
b φ2 Yellow Vehicle Phase 2 Yellow signal. O
c φ2 Green Vehicle Phase 2 Green signal. O
d φ2 Check Active when a call is present on phase 2 but unit is not in phase 2. O
e φ2 On Active when phase 2 is in Green, Yellow, or Red Clearance. O
f Detector 1 Puts call on phase assigned to detector 1 when activated. I
g Ped. Det. 1 Puts a ped call on phase 1 when activated. I
h φ1 Hold See φ2 Hold description above I
i Ring 1 Force Off Terminates Green service in ring 1 provided a conflicting call is I
present and Walk or Ped Clearance are not timing.
j Ext. Min Recall Places all phases on min recall. I

Pin Assignments: MS-A Connector (TS 1 Controllers)

k Manual Control Enable Places termination of Green and Walk intervals under control of the I
Interval Advance input and places calls on all phases. Clearance
intervals will time normally.
m CNA 1 Activates CNA mode for the programmed phases. In this mode, ped I
movements are recalled so that they are serviced with the concurrent
vehicle phase.
n Test A Can be used to activate UCF. I
p AC+ AC Supply Voltage AC +
q I/O Mode A Defines the I/O Mode in TS 2 I
r Ring 1 Status Bit B Coded Status Bit B for Ring 1. O
s φ1 Green Vehicle Phase 1 Green signal. O
t φ1 Walk Pedestrian Phase 1 Walk signal. O
u φ1 Check Active when a call is present on phase 1 but unit is not in phase 1. O
v φ2 Ped Omit Prevents ped service on phase 2. I
w Ring 1 Omit Red Causes programmed red clearance timing for ring 1 vehicle phases I
Clearance to be omitted.
x Ring 1 Red Rest Causes ring 1 phases to rest in red when no conflicting calls are I
present.
y I/O Mode B Defines the I/O Mode in TS 2 I
z CNA 2 See CNA 1 (pin m) I
AA Test B Can be used to activate UCF I
BB Walk Rest Modifier Modifies CNA operation. When active, CNA phases remain in the I
timed out Walk state in the absence of a conflicting call regardless of
the Hold input.
CC Ring 1 Status Bit A Coded Status Bit A for Ring 1 O
DD φ1 On Active when phase 1 is in Green, Yellow, or Red Clearance. O
EE φ1 Ped Omit Prevents ped service on Phase 1 I
FF Ring 1 Ped In CNA mode, if the phase has reached a green dwell state, and the I
Recycle Ped Omit is not active, and a serviceable conflicting call does not
exist, the ped movement will be recycled if the input is active.
In non-CNA mode, if a serviceable ped call exists and Hold is active,
the ped movement will be recycled when the input is active
regardless of conflicting calls.
GG Ring 1 Max 2 Selects Max 2 timing instead of Max 1 I
HH I/O Mode C Defines the I/O Mode in TS 2 I

PIN ASSIGNMENTS: MS-B CONNECTOR (TS 1 CONTROLLERS)

A φ1 Next Active when phase 1 has been selected for next service. O
B Lead/Lag 1 Activates Phase Pair 4 in all Lead/Lag Patterns. I
C φ2 Next Active when phase 2 has been selected for next service. O
D φ3 Green Vehicle Phase 3 Green signal. O
E φ3 Yellow Vehicle Phase 3 Yellow signal. O
G φ4 Red Vehicle Phase 4 Red signal. O
H φ4 Ped Clr Pedestrian Phase 4 Ped Clearance signal. O
J φ4 Don't Walk Pedestrian Phase 4 Don't Walk signal. O
K φ4 Check Active when a call is present on Phase 4 but unit is not in Phase O
4 green.
L Detector 4 Puts call on phase assigned to detector 4 when activated. I
M Ped. Det. 4 Puts a Ped call on phase assigned to ped detector 4 when I
activated.
N Detector 3 Puts call on phase assigned to detector 3 when activated. I
P Ped. Det. 3 Puts a Ped call on phase assigned to ped detector 3 when I
activated.
R φ3 Omit Prevents service on phase 3 when active. I
S φ2 Omit Prevents service on phase 2 when active. I
T φ5 Ped Omit Prevents ped service on phase 5. I
U φ1 Omit Prevents service on phase 1 when active. I
V Ring 2 Ped In CNA mode, if the phase has reached a green dwell state, and I
Recycle the Ped Omit is not active, and a serviceable conflicting call
does not exist, the ped movement will be recycled if the input is
active.
In non-CNA mode, if a serviceable ped call exists and Hold is
active, the ped movement will be recycled when the input is
active regardless of conflicting calls.
W Lead/Lag 2 Activates Phase Pair 2 in all Lead/Lag Patterns. I
X Lead/Lag 3 Activates Phase Pair 3 in all Lead/Lag Patterns. I
Y φ3 Walk Pedestrian Phase 3 Walk Signal. O
Z φ3 Ped Clr Pedestrian Phase 3 Ped Clearance .signal. O
a φ3 Don’t Walk Pedestrian Phase 3 Don't Walk signal. O
b φ4 Green Vehicle Phase 4 Green signal. O
c φ4 Yellow Vehicle Phase 4 Yellow signal. O

d φ4 Walk Pedestrian Phase 4 Walk signal. O
e φ4 On Active when Phase 4 is in Green, Yellow, or Red Clearance. O
f φ4 Next Active when phase 4 has been selected for next service. O
g φ4 Omit Prevents service on phase 4 when active. I
h φ4 Hold When controller is not in CNA mode, activating this input inhibits I
termination of Green service to vehicle phase 4, and inhibits
concurrent ped. service recycle. When in CNA mode,
termination of Walk is inhibited.

Pin Assignments: MS-B Connector (TS 1 Controllers)

i φ3 Hold Same as φ4 Hold description above. I
j φ3 Ped Omit Prevents ped service on phase 3. I
k φ6 Ped Omit Prevents ped service on phase 6. I
m φ7 Ped Omit Prevents ped service on phase 7. I
n φ8 Ped Omit Prevents ped service on phase 8. I
p OLA Yellow Vehicle Overlap A Yellow signal. O
q OLA Red Vehicle Overlap A Red signal. O
r φ3 Check Active when a call is present on phase 3 but unit is not in phase O
3.
s φ3 On Active when phase 3 is in Green, Yellow, or Red Clearance. O
t φ3 Next Active when phase 3 has been selected for next service. O
u OLD Red Vehicle Overlap D Red signal. O
v Lead/Lag 4 Activates Phase Pair 4 in all Lead/Lag Patterns. I
w OLD Green Vehicle Overlap D Green signal. O
x φ4 Ped Omit Prevents ped service on phase 4. I
y Spare 5 Unused. --
z Ring 2 Max 2 Selects Max 2 timing instead of Max 1. I
AA OLA Green Vehicle Overlap A Green signal. O
BB OLB Yellow Vehicle Overlap B Yellow signal. O
CC OLB Red Vehicle Overlap B Red signal. O
DD OLC Red Vehicle Overlap C Red signal. O
EE OLD Yellow Vehicle Overlap D Yellow signal. O
FF OLC Green Vehicle Overlap C Green signal. O
GG OLB Green Vehicle Overlap B Green signal. O
HH OLC Yellow Vehicle Overlap C Yellow signal. O

PIN ASSIGNMENTS: MS-C CONNECTOR (TS 1 CONTROLLERS)

A Ring 2 Status Bit A Coded Status Bit A for Ring 2. O
B Ring 2 Status Bit B Coded Status Bit B for Ring 2. O
C φ8 Don't Walk Pedestrian Phase 8 Don't Walk signal. O
D φ8 Red Vehicle Phase 8 Red signal. O
E φ7 Yellow Vehicle Phase 7 Yellow signal. O
G φ6 Red Vehicle Phase 6 Red signal. O
H φ5 Red Vehicle Phase 5 Red signal. O
J φ5 Yellow Vehicle Phase 5 Yellow signal. O
K φ5 Ped Clr Pedestrian Phase 5 Ped Clearance signal. O
L φ5 Don't Walk Pedestrian Phase 5 Don't Walk signal. O
M φ5 Next Active when phase 5 has been selected for next service. O
N φ5 On Active when phase 5 is in Green, Yellow, or Red Clearance. O
P Detector 5 Puts call on phase assigned to detector 5 when activated. I
R Ped. Det. 5 Puts a ped call on phase 5 when activated. I
S Detector 6 Puts call on phase assigned to detector 6 when activated. I
T Ped. Det. 6 Puts a ped call on phase 6 when activated. I
U Ped. Det. 7 Puts a ped call on phase 7 when activated. I
V Detector 7 Puts call on phase assigned to detector 7 when activated. I
W Ped. Det. 8 Puts a ped call on phase 8 when activated. I
X φ8 Hold When controller is not in CNA mode, activating this input inhibits I
termination of Green service to vehicle phase 8, and inhibits concurrent
ped. service recycle. When in CNA mode, termination of Walk is
inhibited.
Y Ring 2 Force Off Terminates Green service in ring 2 provided a conflicting call is present I
and Walk or Ped Clearance are not timing.
Z Ring 2 Stop Time Suspends all interval timing for ring 2. I
a Ring 2 Inhibit Max Prevents max termination of ring 2 vehicle phases when extending. I
Term
b Spare 1 Unused. --
c Ring 2 Status Bit C Coded Status Bit C for Rng 2. O
d φ8 Walk Pedestrian Phase 8 Walk signal. O
e φ8 Yellow Vehicle Phase 8 Yellow signal. O
f φ7 Green Vehicle Phase 7 Green signal. O
g φ6 Green Vehicle Phase 6 Green signal. O
h φ6 Yellow Vehicle Phase 6 Yellow signal. O
i φ5 Green Vehicle Phase 5 Green signal. O
j φ5 Walk Pedestrian Phase 5 Walk signal. O
k φ5 Check Active when a call is present on phase 5 but unit is not in phase 5 O
green.
m φ5 Hold Same as previous hold descriptions. I
n φ5 Omit Prevents service on phase 5 when active. I

Pin Assignments: 10-Pin MS-A Connector for TS 2 Type 1

p φ6 Hold Same as previous hold descriptions. I
q φ6 Omit Prevents service on phase 6 when active. I
r φ7 Omit Prevents service on phase 7 when active. I
s φ8 Omit Prevents service on phase 8 when active. I
t Detector 8 Puts call on phase assigned to detector 8 when activated. I
u Ring 2 Red Rest Causes ring 2 phases to rest in red when no conflicting calls are I
present.
v Ring 2 Omit Red Causes programmed red clearance timing for ring 2 vehicle phases to I
Clearance be omitted.
w φ8 Ped Clr Pedestrian Phase 8 Ped Clearance signal. O
x φ8 Green Vehicle Phase 8 Green signal. O
y φ7 Don't Walk Pedestrian Phase 7 Don't Walk signal. O
z φ6 Don't Walk Pedestrian Phase 8 Don't Walk signal. O
AA φ6 Ped Clr Pedestrian Phase 6 Ped Clearance signal. O
BB φ6 Check Active when a ccall is present on phase 6 but unit is not in phase 6. O
CC φ6 On Active when phase 6 is in Green. Yellow, or Red Clearance. O
DD φ6 Next Active when phase 6 has been selected for next service. O
EE φ7 Hold Same as previous hold descriptions. I
FF φ8 Check Active when a ccall is present on phase 8 but unit is not in phase 8 O
green.
GG φ8 On Active when phase 8 is in Green, Yellow, or Red Clearance. O
HH φ8 Next Active when phase 8 has been selected for next service. O
JJ φ7 Walk Pedestrian Phase 7 Walk signal. O
KK φ7 Ped Clr Pedestrian Phase 7 Ped Clearance signal. O
LL φ6 Walk Pedestrian Phase 6 Walk signal. O
MM φ7 Check Active when a ccall is present on phase 7 but unit is not in phase 7. O
NN φ7 On Active when phase 7 is in Green, Yellow, or Red Clearance. O
PP φ7 Next Active when phase 7 has been selected for next service. O
PIN ASSIGNMENTS: 10-PIN MS-A CONNECTOR FOR TS 2 TYPE 1

Pin Function I/O
A AC Neutral Input
B Not Used
C AC Line Input
D Not Used
E Not Used
F Fault Monitor Output
G Logic Ground Output
H Earth Ground Input
I Not Used
J Not Used

PIN ASSIGNMENTS: TS 2 TYPE 2 THROUGH A-B-C CONNECTORS

When the TS 2 Type 2 firmware is running in a 3000 Series controller that is using the
older A, B, and C connectors, these are the pin assignments. Pins are shown in the
format Connector–Pin. (For example: A-h, which indicates pin h on the A connector
port.) Newer TS 2 units tend to communicate via RS-485 Port 1.
Inputs
Pin Mode # MODE 0 (TS 1) MODE 1 MODE 2
A-h Input 1 Phase 1 Hold Preempt 1 Preempt 1
A-M Input 2 Phase 2 Hold Preempt 3 Preempt 3
B-i Input 3 Phase 3 Hold Veh Det 9 Veh Det 9
B-h Input 4 Phase 4 Hold Veh Det 10 Veh Det 10
C-m Input 5 Phase 5 Hold Veh Det 13 Veh Det 13
C-p Input 6 Phase 6 Hold Veh Det 14 Veh Det 14
C-EE Input 7 Phase 7 Hold Veh Det 15 Veh Det 15
C-X Input 8 Phase 8 Hold Veh Det 16 Veh Det 16
B-U Input 9 Phase 1 Phase Omit Veh Det 11 Veh Det 11
B-S Input 10 Phase 2 Phase Omit Veh Det 12 Veh Det 12
B-R Input 11 Phase 3 Phase Omit Timing Plan C Veh Det 17
B-g Input 12 Phase 4 Phase Omit Timing Plan D Veh Det 18
C-n Input 13 Phase 5 Phase Omit Alternate sequence A Veh Det 19
C-q Input 14 Phase 6 Phase Omit Alternate sequence B Veh Det 20
C-r Input 15 Phase 7 Phase Omit Alternate sequence C Alarm 1
C-s Input 16 Phase 8 Phase Omit Alternate sequence D Alarm 2
A-EE Input 17 Phase 1 Ped Omit Dimming Enable Dimming Enable
A-v Input 18 Phase 2 Ped Omit Automatic (UCF) Flash Local Flash Status
B-j Input 19 Phase 3 Ped Omit Timing Plan A Address bit 0
B-x Input 20 Phase 4 Ped Omit Timing Plan B Address bit 1
B-T Input 21 Phase 5 Ped Omit Offset 1 Address bit 2
B-k Input 22 Phase 6 Ped Omit Offset 2 Address bit 3
B-m Input 23 Phase 7 Ped Omit Offset 3 Address bit 4
B-n Input 24 Phase 8 Ped Omit TBC On Line MMU Flash Status

Pin Assignments: TS 2 Type 2 Through A-B-C Connectors
Outputs
Pin Mode # MODE 0 (TS 1) MODE 1 MODE 2
A-DD Output 1 Phase 1 Phase ON Preempt 1 Status Preempt 1 Status
A-e Output 2 Phase 2 Phase ON Preempt 3 Status Preempt 3 Status
B-s Output 3 Phase 3 Phase ON TBC Aux 1 Out TBC Aux 1 Out
B-e Output 4 Phase 4 Phase ON TBC Aux 2 Out TBC Aux 2 Out
C-N Output 5 Phase 5 Phase ON Timing Plan A Output Timing Plan A Output
C-CC Output 6 Phase 6 Phase ON Timing Plan B Output Timing Plan B Output
C-NN Output 7 Phase 7 Phase ON Offset 1 Out Offset 1 Out
C-GG Output 8 Phase 8 Phase ON Offset 2 Out Offset 2 Out
B-A Output 9 Phase 1 Phase Next Preempt 2 Status Preempt 2 Status
B-C Output 10 Phase 2 Phase Next Preempt 4 Status Preempt 4 Status
B-t Output 11 Phase 3 Phase Next Preempt 5 Status Preempt 5 Status
B-f Output 12 Phase 4 Phase Next Preempt 6 Status Preempt 6 Status
C-M Output 13 Phase 5 Phase Next Offset 3 Out Offset 3 Out
C-DD Output 14 Phase 6 Phase Next Timing Plan C Output Timing Plan C Output
C-PP Output 15 Phase 7 Phase Next Timing Plan D Output Timing Plan D Output
C-HH Output 16 Phase 8 Phase Next Reserved Reserved
A-u Output 17 Phase 1 Phase Check Free/Coord status Free/Coord status
A-d Output 18 Phase 2 Phase Check Automatic (UCF) Flash Automatic (UCF)
Out Flash Out
B-r Output 19 Phase 3 Phase Check TBC Aux 3 Out TBC Aux 3 Out
B-K Output 20 Phase 4 Phase Check Reserved Reserved
C-k Output 21 Phase 5 Phase Check Reserved System Special
Function 1
C-BB Output 22 Phase 6 Phase Check Reserved System Special
Function 2
C-MM Output 23 Phase 7 Phase Check Reserved System Special
Function 3
C-FF Output 24 Phase 8 Phase Check Reserved System Special
Function 4
TS 2 mode configurations are selected by TS 2 Type 2

I/O mode bit input pins A, B, C as follows:
I/O mode Input A = A-q
I/O mode Input B = A-y
I/O mode Input C = A-HH
Selection State table (Inputs are DC gnd = ON)
Mode A B C State
0 Off Off Off TS 1 Mode
1 On Off Off TS 2 Hardwire Inter.
2 Off On Off TS 2 System
6 Off On On Mode 6 for Boston (Requires power cycling)

PIN ASSIGNMENTS: CLOSED LOOP D MODULE
Auxiliary Connector (37 Pin)

1 User Defined 5 Preempt Output #3 O
2 User Defined 4 User Defined Output #4 O
3 User Defined 3 User Defined Output #3 O
4 Flash Status Input to denote cabinet is in manual flash opto-I
5 Offset 3 Out Offset 3 Interconnect Output O
6 Monitor Status Input to denote cabinet is in Monitor Flash opto-I
7 Optical Input 3 Not currently used opto-I
8 Offset 1 In Offset 1 Interconnect Input opto-I
Alarm 8 Alarm Input 8
10 Cycle 2 In Cycle 2 Interconnect Input opto-I
12 Cycle 4/Split 2 In Cycle 4 or Split 2 Interconnect Input opto-I
13 Cycle 3 In Cycle 3 Interconnect Input opto-I
14 Optocom 1 Common for Optical Inputs 8-16 on this connector. Opto
com*
15 Split 2/Split 3 In Split 2/Split 3 Interconnect Input opto-I
16 Free Input Free Interconnect Input opto-I
17 +24 V 24 VDC Output +24V
18 Ground Logic Ground Lgnd
19 N/U Not Used --
23 N/U Not Used --
25 Free Out Free Interconnect Output O
*
Pins designated as “opto-I” indicate an opto-isolated input. If its ‘common’ is tied to 24V, then the input is Logic Ground = True (NEMA
input). If the input’s common is tied to AC-, then the input is 115VAC = True. External resistors are externally provided to reduce AC
voltage. There are two independent common references, Optocom 1 and Optocom 2. Review the descriptions for each to determine which
opto inputs are referenced by that common.

Pin Assignments: Closed Loop D Module

26* Optocom 2 Common for Optical Inputs 4, 6, 28, 29, 35, 36 on Opto
this connector and Optical Inputs B, P, R, T, W, & X com
on Coord Connector.
27 Optical Input 4 Not currently used --
28 Detector 29 Detector 29 Input opto-I
30 Flash Out Flash Interconnect Output O
32 Cycle 2 Out Cycle 2 Interconnect Output O
33 Cycle 4/Split 2 Out Cycle 4/Split 2 Interconnect Output O
37 User Defined 2 User Defined Output 2 O
Preemption Connector (25 Pin)

1 Preempt 1 In Activates Preempt Run 1 I
6 Detector 9 Detector 9 Input I
14 UCF Activates Uniform Code Flash I
15 Cabinet Flash Input to denote cabinet is in manual flash I
16 RTC Reset Resets the Real-Time Clock to a programmed time. I
18 Dimming Activates loadswitch dimming if enabled in the I
controller.
19 Free Override Forces the controller to operate in Free mode. I
20 TOD Override Forces the controller to operate in time-based I
coordination mode.


21 Preempt Out 2 User programmable output for preemption O
22 User Def. Out 1 User defined TOD Output 1 O
24 Xped Enables Exclusive Pedestrian Operation I
25 Group 2 Activates Group 2 Detector Switching and Dynamic I
Omits & Recalls
Coordination Connector (26 Pin)

A Detector 17 Detector 17 Input I
B Detector 32 Detector 32 Input opto-I
C RX+ Transceiver Pos. Input I
D RX- Transceiver Neg. Input I
E TX+ Transceiver Pos. Output O
F TX- Transceiver Neg. Output O
G Detector 28 Detector 28 Input I
H Detector 27 Detector 27 Input I
J Detector 26 Detector 26 Input I
K Detector 25 Detector 25 Input I
L Detector 24 Detector 24 Input I
M Detector 23 Detector 23 Input I
N* Optocom2 Common for Optical Inputs 4, 6, 28, 29, 35, 36 on opto
Aux connector and Optical Inputs B, P, R, T, W, & X com
on Coord Connector.
P Monitor Status Active if in Monitor Flash opto-I
R Flash Monitor Active when cabinet is in flash opto-I
S Detector 18 Detector 18 Input I
T Detector 31 Detector 31 Input opto-I
U RX Shield Shield for Transceiver Input --
V TX Shield Shield for Transceiver Output --
W Detector 30 Detector 30 Input opto-I
X Detector 29 Detector 29 Input opto-I
Y Detector 22 Detector 22 Input I
Z Detector 21 Detector 21 Input I
a Detector 20 Detector 20 Input I
b Detector 19 Detector 19 Input I
c N/U Not Used --

Pin Assignments: 12 Phase D Module
PIN ASSIGNMENTS: 12 PHASE D MODULE

1 φ10 Ped Omit Prevents ped service on phase 10. I
2 Detector 11 Puts call on phase assigned to detector 11 when I
activated.
3 Ped Det 11 Puts a ped call on the phase assigned to ped I
detector 11 when activated.
4 φ9 Red Vehicle Phase 9 Red signal. O
5 φ10 On Active when phase 10 is in Green, Yellow, or Red O
Clearance.
6 φ10 Green Vehicle Phase 10 Green signal. O
7 φ10 Walk Pedestrian Phase 10 Walk signal. O
8 Aux Detector 2 Puts call on phase assigned to detector 18 when I
activated.
activated.
10 φ10 Hold When controller is not in CNA mode, activating this I
input inhibits termination of Green service to vehicle
phase 10, and inhibits concurrent ped. service
recycle. When in CNA mode, termination of Walk is
inhibited.
11 φ11 Omit Prevents service on phase 11 when active. I
12 φ10 Don't Walk Pedestrian Phase 10 Don't Walk signal. O
13 φ10 Ped Clr Pedestrian Phase 10 Ped Clearance signal. O
14 φ9 Check Active when a call is present on phase 9 but unit is O
not in phase 9 green.
17 φ12 Hold Same as φ10 Hold description. I
activated.
19 φ11 Hold Same as φ10 Hold description. I
20 φ9 Yellow Vehicle Phase 9 Yellow signal. O
21 φ10 Next Active when phase 10 has been selected for next O
service.
25 Pre Act 4 Activates Preempt Run 4. I
26 Ped. Det. 12 Puts a ped call on the phase assigned to detector 12 I
when activated.
27 Ped. Det. 9 Puts a ped call on phase assigned to ped detector 9 I
when activated.
activated.
30 OLF Red Vehicle Overlap F Red signal. O


31 φ11 Check Active when a call is present on phase11 but unit is O
not in phase11 green.
33 φ11 Ped Clr Pedestrian Phase 11 Ped Clearance signal.
activated.
activated.
38 Cabinet Flash Input to indicate that the cabinet is in manual flash I
mode.
40 φ9 Hold Same as φ9 Hold description above. I
41 OLE Red Vehicle Overlap E Red signal. O
49 Ped. Det. 10 Puts a ped call on phase 10 when activated. I
Clearance.
52 Pre Mon 2 Preempt Output 2. O
Clearance.
55 φ10 Check Active when a call is present on phase10 but unit is O
not in phase10 green.
56 Aux Detector 8 Puts call on phase assigned to detector 24 when i
activated.
activated.
activated.
60 Group 2 Enable Enables Group 2 functions for dynamic recall and I
detector copy.
service.
62 OLF Yellow Vehicle Overlap F Yellow signal. O

Pin Assignments: 12 Phase D Module

activated.
71 TOD Out 3 User defined TOD Output 3. O
74 OLE Yellow Vehicle Overlap E Yellow signal. O
Clearance.
service.
79 TBC In Forces controller into Time Base Coordination I
operation.
80 DIM Activates loadswitch dimming if enabled in the I
controller.
service.
85 OLE Green Vehicle Overlap E Green signal. O
activated.
87 Free In Forces controller to operate in Free mode when I
active.
88 UCF Causes controller to enter UCF mode when active I
and flash source is Interconnect.
89 RTC Reset Resets clock to preset value. I
91 OLF Green Vehicle Overlap F Green signal. O
93 φ12 Check Active when a call is present on phase 12 but unit is O
not in phase 12 green.
95 XPed Enables Exclusive Ped operation if programmed to I
do so.

PIN ASSIGNMENTS: LMD D MODULE (63 PIN CPC)

Pin Function Description I/O Level Previous LMD Function
1 UCF Flash Calls for UCF flash opto-I See note
2 Ofst 1/alarm 8 in Offset 1 in or alarm 8 if not opto-I See note
interconnect mode
3 Inter. common Common ref. for opto inputs com See note
4 Enable excl. ped Enables exclusive ped I 0 VDC User Defined Input 6
interconnect mode
interconnect mode
7 Cycle 2/alarm 1 in Cycle 2 in or alarm 1 if not opto-I See note
interconnect mode
8 Group 2 switching Activates group 2 detector I 0 VDC User Defined Input 7
switching
9 Spare Spare I 0 VDC User Defined Input 8
10 Call to Free Calls to free operation for all I 0 VDC
coord select modes
11 Det input 31 Activates Detector input 31 I 0 VDC Call To Week Program
10
12 Cycle 3/alarm 2 in Cycle 3 in or alarm 2 if not opto-I See note
interconnect mode
13 Split 2/alarm 5 in Split 2 in or alarm 5 if not opto-I See note
interconnect mode
14 Split 3/alarm 3 in Split 3 in or alarm 3 if not opto-I See note
interconnect mode
15 Det input 25 Detector input 25 I 0 VDC Lag Phase 1
18 Dimming Calls for signal dimming I 0 VDC
operation
19 Dual Entry Calls for dual entry operation I 0 VDC
20 System/alarm 4 in System in or alarm 4 if not opto-I See note
interconnect mode
22 Det input 30 Detector input 30 I 0 VDC Spare Input
23 Det input 32 Detector input 32 I 0 VDC Spare Input
24 Det input 13 Detector input 13 I 0 VDC
27 Ped. Det. 9 Puts a ped call on phase 9 I 0 VDC
when activated
28 Not Used No Wire -- --
33 Cond. Service Activates Conditional Service I 0 VDC
when programmed to activate
by input
34 Preempt 5 input Activates preempt 5 run I 0 VDC
35 Preempt 1 output Activated by preempt O 0 VDC
programming
programming
37 Interconnect Inhib. Inhibits interconnect, calls TBC I 0 VDC
38 Time Clock Sync Sets clock to preset time of I 0 VDC
day
39 Det input 26 Detector input 26 I 0 VDC Sync Inhibit

Pin Assignments: LMD D Module (63 pin CPC)
Pin Function Description I/O Level Previous LMD Function

programming
44 Not Used No Wire -- --
45 Preempt 4 output Activated by preempt O 0 VDC Fast Flash Active
programming
46 Preempt 5 output Activated by preempt O 0 VDC Fast Flash Image
programming
47 System output Active when coordination O 0 VDC
achieved
48 PE 6/Flash output Preempt 6 out or remote flash O 0 VDC
ac-hieved
50 User 1 out User defined output 1 O 0 VDC
53 Spare Spare O 0 VDC Clock Ckt 13 (System)
55 Ckt 8 (Flash) out Clock Ckt 8 output O 0 VDC
56 Ckt 3 (Ofst 1) out Clock Ckt 3 output O 0 VDC
59 Ckt 1 (Cyc 2) out Clock Ckt 1 output O 0 VDC
60 Ckt 2 (Cyc 3) out Clock Ckt 2 output O 0 VDC
61 Ckt 6 (Splt 2) out Clock Ckt 6 output O 0 VDC
62 Ckt 7 (Splt 3) out Clock Ckt 7 output O 0 VDC
NOTE : Pins designated as “opto-I” indicate an opto-isolated input. If Inter. common is tied to 24V, then
the input is Logic Ground = True (NEMA input) and the input function is not interconnect mode. If Int.
common is tied to AC-, then the input is 115VAC = True and the input function is interconnect mode.
External resistors must be externally provided to reduce AC voltage.

PIN ASSIGNMENTS: TEXAS D MODULE
Circular Connector (57 Pin)

1 Offset 1 In Offset 1 Interconnect Input I
2 Cycle 2 In Cycle 2 Interconnect Input I
4 Flash In Flash Interconnect Input I
6 Offset 3 in Offset 3 Interconnect Input I
7 Free In Free Interconnect Input I
8 Split 2 In Split 2 Interconnect Input I
10 TOD 2 Out User Defined TOD Output O
11 Free Override Free Override Input I
12 N/U Not Used --
13 N/U Not Used --
14 N/U Not Used --
15 N/U Not Used --
16 N/U Not Used --
17 N/U Not Used --
18 N/U Not Used --
22 N/U Not Used --
23 N/U Not Used --
24 N/U Not Used --
25 N/U Not Used --
26 N/U Not Used --
27 N/U Not Used --
28 N/U Not Used --
29 N/U Not Used --
30 N/U Not Used --
31 N/U Not Used --
32 N/U Not Used --
33 Alarm 1 In Alarm Input 1 I
34 Alarm 2 In Alarm Input 2 I
35 N/U Not Used --
36 N/U Not Used --
37 N/U Not Used --
38 N/U Not Used --
39 N/U Not Used --

Pin Assignments: Texas D Module

40 N/U Not Used --
41 N/U Not Used --
42 N/U Not Used --
43 TOD 1 Out User Defined TOD Output O
44 Split 3 Out Split 3 Interconnect Output O
45 Split 2 Out Split 2 Interconnect Output O
46 Free Out Free Interconnect Output O
49 Flash Out Flash Interconnect Output O
53 +24VDC External 24 Volt Supply +24
54 Logic Gnd Logic Ground Lgnd
55 Chassis Gnd Chassis Ground Cgnd
56 N/U Not Used --
57 N/U Not Used --
AUX Connector (37 Pin)

1 Spare 2 In Spare --
2 Cabinet Flash Input to indicate cabinet is in manual flash mode i
3 RX Shield Shield for receiver pair --
4 TX+ Transceiver Positive Output O
5 TX- Transceiver Negative Output O
7 Group 2 Activates Alt. Detector Switching, Dynamic I
Omits & Recalls
8 Dimming Activates loadswitch dimming if enabled in the I
controller
9 N/U --
10 N/U --
11 Preempt Out 1 User programmable output for use during O
preemption
12 TOD 4 Out User defined TOD output O
16 Monitor Status Input to indicate Cabinet is in Monitor Flash I


20 Spare 1 In Spare --
21 Transceiver Positive Input I
22 RX- Transceiver Negative Input I
23 TX Shield Shield for transmitter pair --
24 N/U --
26 Xped Enables Exclusive Pedestrian Operation. I
28 TOD Override In Forces controller to operate in time-based I
coordination mode
29 N/U --
30 N/U --
32 TOD 7 Our User defined TOD output O
34 Common
35 Flash Monitor Active when cabinet is in flash I

Pin Assignments: Las Vegas D Module
PIN ASSIGNMENTS: LAS VEGAS D MODULE
Circular Connector (57 Pin)

3 N/U Not Used --
4 N/U Not Used --
5 N/U Not Used --
7 N/U Not Used --
8 N/U Not Used --
11 N/U Not Used --
14 N/U Not Used --
15 N/U Not Used --
16 N/U Not Used --
19 N/U Not Used --
20 N/U Not Used --
21 N/U Not Used --
24 N/U Not Used --
25 N/U Not Used --
26 Free In Free Interconnect Input I
27 N/U Not Used --
28 N/U Not Used --


37 N/U Not Used --
38 N/U Not Used --
41 N/U Not Used --
43 N/U Not Used --
45 N/U Not Used --
50 N/U Not Used --
54 N/U Not Used --
55 N/U Not Used --
56 UCF Activates Uniform Code Flash I
25 Pin Connector
The ‘Las Vegas’ D Module also includes a 25 pin connector in a DB-25 format (not
shown). Only the ‘Cabinet Flash’ input (pin 20) is used on this connector at this time.

Communication Ports
COMMUNICATION PORTS
There are four possible communication ports available on 3000 Series controllers.
Not all of these are available on every version of the 3000 Series, but when present,
they have the following pin assignments.
Port 1–SDLC Connector

Port 1 is the Synchronous Data Link Control (RS-485) port. This connector is used by
most TS 2 controllers to communicate with BIUs and MMUs, and from there to the
rest of the cabinet. This is a 15 pin connector that is optional on both the 3000 and
3000E units. Port 1 is required on TS 2 Type 1 controllers.
Pin Function
1 Tx Data +
2 Logic Ground
3 Tx Clock +
4 Logic Ground
5 Rx Data +
6 Logic Ground
7 Rx Clock +
8 Logic Ground
9 Tx Data -
10 Port 1 Disable (0VDC=disable)
11 Tx Clock -
12 Earth Ground
13 Rx Data -
14 Reserved
15 Rx Clock -
Port 2–EIA-232 (RS-232C) Connector

Port 2 has 25 pins and is the RS-232C connector. It is optional on both the 3000 and
3000E controllers.
Pin Function
1 Chassis GND
2 TD
3 RD
4 RTS
5 CTS
6 DSR
7 LOGIC GND
8 CD
20 DTR
22 R1

Aux Connector
The AUX port is an Auxiliary EIA-232 (RS-232C) port with 25 pins that is an option on
3000 controllers (though not on 3000E’s.)
Pin Function
1 Chassis GND
2 TD
3 RD
4 RTS
5 CTS
6 DSR
7 LOGIC GND
8 CD
20 DTR
22 R1
Port 3–Modem Connector

Port 3 is available in two orientations, either as a 9 pin (DB-9) Modem connector, or
as a four input optical connector. On 3000 controllers it is labeled ‘FON’; on 3000E
units it is labeled COMM. This is the port where M3000 masters are typically
connected to individual intersection controllers.
Pin Function
1 Transmit 1
2 Transmit 2
3 Reserved
4 Receive 1
5 Receive 2
6 Earth Ground
7 Reserved
8 Reserved
9 Earth Ground

Appendix D — Passage Time Settings
This section explains timing settings for 3000 series controllers when they are operating in an
actuated mode environment. The following topics are discussed in detail in this chapter:
An overview of Passage Timing in the 3000 Series, on page 462.

An explanation of how to configure the timing in this environment, on page 462.
An example of assigning Passage Times, on page 462.

OVERVIEW
All 3000 Series traffic controllers operating in actuated mode use information
collected from traffic detectors. These traffic detectors measure the arrival of vehicles
at various points on the approaches to an intersection in the form of an actuation and
the controller will respond to these actuations in a manner that is dependent on the
controller settings.
One of the responses to an actuation by the controller is the extension of the active
phase green interval. The length of time that the green interval is extended is
determined based by a setting in the 3000 Series referred to as Passage Time. The
terms Vehicle Interval, Vehicle Extension, Gap, Allowable Gap or Extension Interval
share the same meaning as Passage Time. The terminology is not consistent in
various literature or in the industry, but the meaning is the same.
Passage Time for a phase serves two purposes:
1. It sets the allowable gap, which is the amount of gap tolerated between
successive vehicles without causing termination of the phase and,
2. It provides passage time, which is the time to reach the intersection after
crossing the detector, for a vehicle traveling at the approach speed.
SELECTING A PASSAGE TIME

The value entered for Passage Time can be based on allowable gap or passage time
calculations. However, it will still serve the two purposes listed above regardless of
the value entered for the setting.
For example, if a value of 3.0 seconds is entered for the Passage Time then the
controller will extend the green interval 3.0 seconds after a car passes the detector
and the controller will terminate the phase (via gap out) if the gap between successive
vehicles is greater than 3.0 seconds. So, the Passage Time setting provides a time
of 3.0 seconds for a vehicle to get to the intersection from the detector and provides
3.0 seconds for another vehicle actuation to extend the green following behind.
The distinction is made between the two purposes because there may be instances
where one of the purposes will be of little use.
Examples
In Figure 393, note that there are two phases shown, each with a different detector
location. In the case of Phase 1, both purposes of the vehicle extension would be
quite useful and the value specified should be acceptable for both purposes. For the
Passage Time setting to be useful, the setting should be equal to or greater than the
time it would take a vehicle, traveling at the approach speed, to reach the intersection
from the detector. However, care must be taken that the Passage Time is within a
practical range of allowable gap (i.e., 3.0 to 4.0 seconds). Volume Density would
compliment this situation.
In the case of Phase 2, only one of the purposes of the Passage Time would be
useful. This is because the detector is at the stop bar and the passage time
calculation would be zero. So the value used for the Passage Time setting on Phase
2 need only be reasonable in the context of allowable gaps to retain the existing

Selecting a Passage Time
green interval. The smaller the value, the closer together vehicles must be to retain
the green interval. Some agencies have been known to use Passage times as low as
one second, especially for left turns with long loops so that as soon as the last car
passes, the phase turns yellow almost instantly.
Multiple detectors are used for high-speed approaches and for approaches with
multiple lanes. The use of multiple detectors increases the likelihood and frequency
of actuation on an approach, can register shorter gaps, and can result in green times
that are too long. In instances where multiple detectors are used, the specification of
Passage Time must take into account the longest path between (1) successive
detectors and (2) the stop bar and closest detector. It typically requires the use of
smaller Passage Time values. Once the settings are specified they are adjusted in
the field to make sure the signal is operating as efficiently as possible.
Phase 1
Phase 2
Figure 393 – Setting passage time


Glossary
This section defines and explains the terms used when discussing the very complex topics of
traffic control using the 3000 Series controllers. The following lists divide the technical terms up
by general topics:
General controller functions, beginning on page 466.

Coordination functions, beginning on page 487.
Preemption functions, beginning on page 498.
Other common acronyms, beginning on page 503.

Glossary
QUICK GUIDE TO CONTROLLER FUNCTIONS

5-Section Illinois Left Turn Logic (Dual Yellows Prohibited)
Overlap drives the G & Y Left Turn indications. Controller immediately changes
Yellow Arrow to Red when Adjacent thru is Yellow.
Signal Head Steering used to bring Overlap out on the left turn driver.
To prevent MMU fault, Yellow Monitoring must be disabled on the left turn
Overlap Channel.
5-Section Right Turn Illinois Logic

Green Right Turn arrow is forced red when [1] adjacent thru green and [2]
adjacent thru yellow and phase next not parent phase, otherwise operates as a
standard overlap.
Yellow Monitoring must be disabled on this channel because the Overlap goes
from Green directly to Red.
Added Initial
Volume Density function, multiplies Added Initial Time by the # of actuations
received during non-green state.
Uses computed value if > Initial Time and < Max Initial Time.
Auto Ped Clear with MCE (Manual Control Enable)

When enabled, controller internally times Ped Clearance interval. Interval
Advance is inhibited during this interval and Stop Timing is applied only during
Green/Walk.
A single Interval Advance activation is required to go from green/walk to next
green/walk.
When disabled, Ped Clearance duration is under manual control—Interval
Advance is not inhibited during Ped Clearance and Stop Timing is applied
during Green/Walk and Ped Clearance.
Two Interval Advance activations are required to go from green/walk to next
green/walk.
MCE is typically activated via toggle switch on police panel.
Barrier
Compatibility line that prevents conflicting phases in different rings from timing
simultaneously.
3000E uses Co-phase Set programming to implicitly determine the Barriers.
“Barrier crossing”, or “crossing a barrier” refers to operation where the “phases
ON” and “phases NEXT” are in different Co-Phase Groups.

Glossary
When “crossing barrier” all “phases on” set to end will start Yellow
simultaneously and the “phases next” will not start until all Red Clearance
Timers = 0.
Call Only Detector

Operates only when phase is not green; does not extend green interval.
Call-Extend Detector
Normal detector, calls for service when non-green and extends service when
green.
Check
Purpose: To indicate an unanswered call exists on a phase.
NEMA per phase output function.
Active when the phase is NOT Green and a call exists.
Phase Omit has no effect on Check state.
CNA (Call-To-Non-Actuated)
Purpose: To serve a phase without requiring vehicle or ped detection devices.
Per Unit NEMA function. Program phases that will respond to this function when
it is activated.
CNA must be activated (Ext Input, TOD CKT) in order for CNA to be seen in the
programmed phases.
4 Green States: [A] Walk Timer, [B] Walk Hold or Rest, [C] Ped Clearance, [D]
Green Dwell/Select State (green/steady don’t walk).
[A] Walk Timing State starts upon entry into Green provided Ped Omit is
not active.
[B] Walk Hold State (Hold applied); Walk Rest State (Walk Rest Modifier
applied and no serv confl calls (Hold off)).
[C] Ped Clearance State occurs when (a) Force Off with serv confl call, (b)
Hold released with Walk Rest Modifier inactive, or (c) Walk Rest and serv
confl call arrives. Always advances to State [D] Green Dwell/Select State
after Ped Clearance.
[D] Green Dwell/Select State is where phase will (a) immediately select a
phase next and begin yellow if serv confl call exists and no concurrent
timing constraints exist. If concurrent timing constraints exist, the phase
rests in this state until the “phase next decision” can be made.
If the phase is in the Green Dwell/Select State and no serv confl call exists,
(a) the phase rests in this state if Walk Rest Modifier and Ped Recycle are

Glossary
inactive, or (b) returns to walk (State A) immediately if WRM or Ped

Recycle are active.
Force Off terminates Walk Hold (provided Walk Timer done and serv confl call
exists).
Force Off has no effect when not in the timed out Walk Hold state.
Hold has no effect except during Walk (with Walk Timer = 0).
CNA can be used on coordinated phases so the walk duration is determined
from Phase Allocation and an automatic Hold issued by the coordinator.
Conditional Ped
Alternate ped service option where a ped call arriving during parent phase
green with a serv confl call present will serve immediately if time remaining on
max timer is > walk plus ped clearance. This may occur two times in a row in
the same green interval.
Without Conditional Ped, the ped call after the onset of green will not serve until
the conflicting calls are serviced (unless Hold and Red Recycle are active).
Applies whether Hold and Ped Recycle are on or off.
Applies for actuated peds only.
Conditional Service
Purpose: To allow re-servicing of a left turn movement if time remains before
the controller must “cross a barrier”.
With 2 & 6 timing, call on phases 3, 4, 7 & 8 plus call on phase 1, if phase 2 is
gapped or maxed out and phase 6 has enough time on max timer to clear 2 and
time 1 Initial, then it will cycle 1/5 > 2/6 > 1/6 > 3/7 > 4/8 > 1/5….
In more generic terms, the controller reverts to a previous phase within the
active Co-Phase Set if the concurrent phase has enough time remaining on the
Max Timer as noted above.
Co-Phase Groups
Method of sequence programming in the 3000E that determines whether
phases in different rings are compatible or conflicting.
Phases in the same Co-Phase Group and in different Rings are compatible.
Phases not in the same Co-Phase Group are conflicting.
Co-Phase Groups may be used to reverse order of a single ring sequence
without using Lead-Lag option.
A Phase may be assigned to more than one Co-Phase Group.

Glossary
Controller cycles in order of Co-Phase Groups from lowest order to highest

order. Within a Co-Phase Group, cycles from lowest order phase to highest
order phase within each Ring.
Defined sequences in 3000E can be considered as a table as shown below:
Co-Phase Set 1 Co-Phase Set 2

Ring 1 1 2 3 4
Ring 2 5 6 7 8
Delay Inhibit (Detector)

Inhibit delay when programmed phases are green, operates in call extend
mode.
When more than one phase is set to inhibit delay, it is an “OR” condition.
Useful on a main street 5-section left turn that is delayed when the main street
is green to give chance for permissive left turns before call is placed, but
requires immediate calls placed when the side street is green.
Detector Copy
Copies the call from one phase to another when programmed phases are
active.
Original call is retained.
Detector Lock (Per Detector)

Detector Level option to lock or non-lock calls.
Non-Lock at the phase level must be enabled for it to work per detector.
A Locking Detector in Delay Mode will lock the demand immediately and the
controller will receive call for service when Delay Timer = 0.
Useful for setting Non-Lock on Right Turn only lanes and setting Locking Mode
for Thru and Left Turn lanes with all lanes associated with the same phase.
Detector Switching
Switches call from one phase to another.
TS 1: Program phase greens that must be on for switch to occur, plus “from”
and “to” phases.
TS 2: Program “from” and “to” phase only. When “from” phase is red and the
“to” phase is green, the switch occurs.
Useful for 5-section left turn control where left turn detector extends adjacent
thru phase instead of calling for protected left turn.

Glossary
Double Clearance Overlaps

Purpose: To prevent vehicles from getting trapped between two sets of signals
when the first signal terminates.
Delays Overlap termination when parent phase terminates and programmed
“phase on” and “phase next” (gated with OR) –OR— “group on” and “group
next” (gated with AND) are selected next.
Double Clearance Green time is entered for the Overlap, plus unique Yellow
and Red Clearance times.
Double Clearance Overlap Green timing begins at the Yellow of parent
phase(s).
Dual Entry
Purpose: To ensure there is always a phase ON in each Ring when Rings
without demand would otherwise be “all red” with a single phase selected and
timed alone.
As long as a phase is on in each Ring via real demand or recall, Dual Entry
parameters do not affect operation.
When a “crossing a barrier” (a new Co-Phase Group is entered) and there is a
call in only one Ring, a pre-determined phase can be optionally serviced in the
other Ring.
Programming allows a Dual Entry phase assigned to each demanding phase in
a matrix format.
Same concept applies for 3 and 4 Ring sequence control.
Dual Entry calls are automatically placed at the “barrier crossing” point such that
both the “dual entry phase” and “demanding phase” are selected next at the end
of green of the terminating phases.
Dual Ped Control

When enabled, and there are ped calls on both even numbered compatible
phases and they start at different times, the first walk interval that times out will
rest in walk and wait for the other walk to time out and the two peds then enter
Ped Clearance together.
Activated by TOD CKT 129 only; all phases effected.
Does not require cross-barrier calls to perform the walk rest.
Dynamic Omit
Omits selected phases when programmed phases are on, gated with “AND”
Omit plan activated by “enabled” or by Ext Input or TOD.

Glossary
Some use this to omit main street protected/permissive left turn phases when
main street is green to prevent “yellow trap” situations.
Dynamic Recall
Places a Minimum Recall on selected phases when programmed phases are
on, gated with “AND”.
Dynamic Recall plan activated by “enabled” or by Ext Input or TOD.
Dummy Phase
Not explicitly programmed in the controller.
Phase that is timed “behind the scenes” to achieve special operating
requirements.
No Load Switch or MMU Channel association required.
Examples:
Used to start walk before green to give peds a chance to get into the
crosswalk.
Used in left turn yellow trap applications.
Used in dilemma zone downstream clearance requirements where only one
set of signals is present.
Used for a phase exclusively for Preemption where the phase will not time
during Free or Coord operation.
Enhanced Ped Operation

Applies for phases programmed for CNA & WRM, but not when CNA is turned
on (TOD CKT and external input inactive).
Walk Time is replaced with Max Time.
Recycle of walk uses normal walk time.
When CNA & WRM are turned on, phase operates normally.
Exclusive Ped
Purpose: To provide an interval for ped timing only.
Enabled by [1] D-Mod Xped Input, [2] Ped Detector 1, [3] Ped Detector 3, [4]
TOD CKT
Program XPED Phase with Walk, Ped Clearance Times
Program OUTPUTS (parent phases of the Xped), these phases will ignore their
normal ped times and ped omit will be applied to these phases.
Soft Return: returns to set phases after Xped if no recalls or real calls exist.

Glossary
Set XPED Phase Red Clear Time > 0 for a period of all red before exit greens
begin.
Phases not permitted during Xped, but non-conflicting Overlaps are allowed.
Coordination, XPED Phase Allocation = Walk + Ped Clear + Red Clear + 1” for
Auto Perm.
Force Off
Per Ring NEMA function.
Force Off has a different effect depending on whether applied to an actuated
phase or a CNA phase.
For actuated phase, it terminates the green interval provided Initial, Walk or Ped
Clearance are not timing (and phase next decision can be made immediately
and a serv confl call exists).
For a CNA phase, it terminates the Walk Hold interval. If phase is not in the
timed out walk state with Hold applied, Force Off has no effect.
Force Off is not “remembered” and therefore it is effective only as long as it is
sustained (if phase does not terminate from a momentary activation).
In the absence of serv confl calls, force off will not advance the phase.
Used in coordination and preemption.
Internal Coordinator issues Force Off commands automatically or based on
user-defined points.
Gap Out
Describes a phase state where the Passage Timer = 0.
“Gap Out” normally refers to phases timing out Passage and immediately
entering Yellow Clearance with a “next phase” selected (Gap Termination).
Also a phase may “gap out” and enter a green rest state if [1] no serv confl calls
exist, or [2] concurrent timing constraints exist that prevent immediate “phase
next decision” from being made.
Green Prep Interval (Prepared to Terminate)

Typical conditions will place a phase in Green Prep:
Passage Timer = 0 (gapped out phase), a serv confl call exists, concurrent
timing constraints exist and Simultaneous Gap Out is disabled for the phase.
Max Timer = 0, a serv confl call exists and concurrent timing constraints exist.
A CNA phase that has reached Green Dwell/Select State with a serviceable
conflicting call present.

Glossary
Green Rest Interval

Three typical conditions will place a phase in Green Rest:
Passage Timer = 0 and no serv confl calls exist,
Max Timer = 0 and no serv confl calls exist (Max Recall active),
Passage Timer = 0, Max Timer not = 0, a serv confl call exists, concurrent
timing constraints exist and Simultaneous Gap Out is enabled for the phase.
Phase in Green Rest with Max Timer not timed out will always restart Passage
timing if demand arrives.
Hold
Per phase NEMA function
Function that has a different effect depending on whether applied to an actuated
phase or a CNA phase.
For Actuated phase, Hold maintains the phase in green/don’t walk and does not
affect a ped in the process of timing. When in green/don’t walk with hold
applied, ped recycle/service is inhibited unless Ped Recycle is active.
For CNA phase, Hold maintains the phase in the timed out walk state once the
Walk Timer = 0.
The only way to terminate the phase with Hold applied is to activate Force Off.
A max out in the presence of Hold does not terminate the phase.
Used in coordination and preemption.
Internal Coordinator issues Hold commands automatically based on user-
defined or automatically calculated permissive periods.
The No Early Release option in the Internal Coordinator issues a constant Hold
to the programmed phases.
Hold Rest
Applies to Actuated Phase only.
A rest interval where Passage Timer = 0 and Hold is applied to the phase.
New demand may restart Passage Timer and timing will be revealed upon
release of Hold.
Inhibit Max Termination

Per Ring NEMA Input function.
Purpose: In Coordination Mode, to allow Phase Allocations to determine the
“max” time instead of the Maximum Green Time (Max 1 or Max 2) in control.
Per phase programming for phases to respond to this function when activated.

Glossary
Requires External Input or TOD Circuit activation.

Prevents a phase from terminating via Max Time Out, but does not stop normal
Max Timer operation.
In coordination, if Max is not inhibited and not properly set, phases may max out
before force off point, never receiving their intended allocation.
Initial Timer
First portion of Green; must be timed for Actuated or CNA phase before green
may terminate.
Not preempted by a Maximum Green Time out.
Interval Advance
Per Unit NEMA Input function.
An “on-off” activation causes immediate advance to the next serviceable interval
(serviceable interval is based on presence of a serv confl call) that would occur
next without such activation.
Typically used with Stop Timing during Bench Tests.
Also used with Manual Control Enabled to produce manual control of green and
ped intervals with Vehicle Clearances timed internally. See Manual Control
Enable.
Lead-Lag
Reverses the order of adjacent phase pairs that are in the same Co-phase
Group and Ring.
8 possible Lead-Lag Patterns containing up to 4 pairs for reversal.
6 Pattern Activation Modes: 0=TOD/COORD, 1=COORD only, 2=TOD only,
3=By Input, 4=Always On, 5=Always Off.
Lead-Lag does not impose any compatibility restrictions. In an 8-phase quad
left, if Phases 1 & 2 are reversed via Lead-Lag, Phases 1 & 5 are still allowed to
time concurrently.
Lead-Lag can be programmed using additional Co-phase Groups without using
Lead-Lag option in the controller, especially if the user wishes to stop lead and
lag left turn concurrency.
Manual Control Enable (MCE)

Per Unit NEMA Input function.
Places vehicle and ped calls on all phases in memory.
Activates Stop Timing in all intervals except Yellow and Red Clearance.

Glossary
Inhibits Interval Advance during Yellow and Red Clearance.

Also activates Stop Timing during Ped Clearance if Auto Ped Clearance with
MCE is disabled. See Auto Ped Clearance with MCE.
Max 3 Mode
Max 3 set > normal Max 1 or Max 2.
If phase maxes out for the set # of times (# of Max Outs to Adjust), Max 3 Timer
will be loaded with higher value (Max 3 Adjust Value) in the next green.
If it gaps out for the set # of times (# of gap outs to adjust), the Max 3 Timer will
be loaded with a smaller value (Max 3 Adjust value deducted).
Each cycle it can increment Max Timer in response to max outs until Max 3
Limit is reached and decrement in response to gap outs until returning to normal
Max 1 or Max 2.
Per phase function activated by entering non-zero for Max 3 parameters.
Maximum Initial
Volume Density function
The largest possible value of Initial Timer regardless of how many cars are
stored on the phase.
Typically set equal to the normal Initial that assumes 100% storage between
detector and stop bar.
Maximum Green Timer with Max Recall OFF (Actuated Phase Mode)
Purpose: To establish the maximum amount of time that a call must wait when
any conflicting phases have demand.
NEMA definition: The longest time that a phase may be held green in the
presence of a serv confl call.
If no serv confl call exists, Max Timer remains reset.
If Max timing and all serv confl calls are withdrawn, Max Timer is reset
immediately and waits for next serv confl call to arrive.
An actuated phase green Max Recall off with Passage Timer active will not
terminate immediately upon registration of a serv confl call, but instead begin
Max Timing and gap or max out accordingly.
Maximum Green Timer with Max Recall ON (Actuated Phase Mode)

Special operation where Max Timer starts at the onset of green whether a serv
confl call exists or not.
Phase must time the Max Timer out before terminating regardless of demand.

Glossary
If no serv confl calls arrive, when Max Timer reaches zero the phase rests in a
latched maxed out gapped out state.
A call randomly arriving will wait for remainder of Max Timer to finish, or receive
immediate service if Max Timer = 0 (regardless of phase demand).
Max Recall differs from a constant vehicle detector call in that (a) the constant
detector call would cause a serv confl call to wait the entire Max time, while (b)
the Max Recall would cause the serv confl call to wait for the remainder of Max
Timer to finish.
Min Recall
Sequence control option where a call is placed for the phase when it is not
green.
Results in phase always demanding service for at least Initial interval even if no
real demand waiting, then real demand can extend the green as normal.
With no recalls of any type and Red Rest not enabled, the controller rests in the
green of the last phase with demand.
Minimum Gap
Value of Passage Timer required for a gapped out state after Time To Reduce
is finished.
Phase will not gap out in presence of a constant actuation even if Min Gap = 0.
If all serv confl calls are withdrawn, Passage Timer reverts to the normal setting.
Next (Phase Next)

Purpose: To indicate that a phase is committed to being served next.
Per phase output that is active from the time the “phase on” terminates until the
“phase next” begins timing.
The “phase next decision” is made at the end of the Green interval of the
terminating phase, except that if the decision cannot be made at the end of the
Green interval, it shall be made after all Yellow and Red Clearance Timers = 0.
An example where decision cannot be made at the end of the Green interval is
if Phases 2 & 6 terminate with a call on Phase 3 only (Dual Entry disabled) and
during 2 & 6 Yellow, a call arrives for Phase 8, followed by Phase 7. In this
case, Phase 3 is selected next when 2 & 6 terminate Green and Phase 7 is
selected next at the end of 2 & 6 Red Clearance.
Once a phase is next, controller is “locked” to the phase and removal of call or
activation of phase omit do not prevent service.

Glossary
Non-Lock (Phase Level)

When enabled (lock off), detector must be continuously occupied in order to
maintain the call.
When disabled (lock on), a call is locked once received during yellow and red
and will be serviced even if the detection zone is empty.
When disabled (lock on), a call is left on the phase when it terminates with time
remaining in the Passage Timer. Setting Non-Lock Mode defeats this operation.
There is also Lock/Non-Lock at the detector level and phase level; Non-Lock at
phase level must be enabled for detector level operation to work.
No Skip
Sequence control option that forces the controller to serve the programmed
phase for a “Min Recall” before proceeding to the phase with actual demand.
Useful for ensuring clearance movements are serviced before upstream starts.
Not Ped Overlap

Purpose: To allow Standard Overlap operation, except when a parent phase
conflicting ped serves.
It is a Standard Overlap that is modified by a “not ped” assignment, the “not
ped” is also a parent phase.
When the “not ped” serves, the controller will terminate the Overlap before
starting ped.
Overlap requires a Green, Yellow and Red Clearance Timer. Green provides a
guaranteed green time before a ped actuation ‘negates’ the overlap.
Oklahoma 5-Section Single Indication Left Turn Logic

Purpose: To only allow one indication to be active at any given time.
An Overlap drives the 5-section permissive G-Y-R indications.
The Parent Phase is the Adjacent Thru and the associated Left Turn phase is
the “modifier phase” as specified by user.
Overlap acts as a Standard Overlap with Adjacent Thru phase except Overlap
goes DARK when the associated Left Turn phase is Green or Yellow.
Either [1] Dummy Red Load, or [2] MMU Red Input tied to 120VAC with Dual
Indications disabled, is required to prevent MMU absence fault.
Oklahoma 5-Section Single Indication, Red-Over-Arrows Allowed

Purpose: Same as Single Indication Logic except Red-Over-Arrow is allowed.
An Overlap drives the 5-section permissive G-Y-R indications.

Glossary
The associated Left Turn phase is the modifier phase specified by user.
Overlap acts as in Single Indication Mode except the Overlap is not DARK when
the Adjacent Thru Phase is Red.
Either [1] Dummy Red Load, or [2] MMU Red Input tied to 120VAC with Dual
Indications disabled, is required to prevent MMU absence fault.
Omit Red Clearance

Per Ring NEMA input function.
Causes Red Clearance interval to be omitted for associated ring.
On (Phase On)
Purpose: To indicate which phase (if any) is currently timing in a given Ring.
Per phase NEMA output function.
Active when a phase is timing any interval (G-Y-R-W-PCL-DW).
Overlap
An output associated with one or more phases.
See Standard Overlap
Passage Sequential Timing

Normal Passage Timing is concurrent with Initial. This feature does not start
Passage Timing until Initial is complete.
When enabled, shortest possible green time is Initial + Passage (provided no
max out or force off).
When disabled, shortest possible green time is the greater of Initial & Passage
(provided no max out or force off).
Passage Timer
Timer that responds to vehicle detector actuations during green.
Remains reset as long as an actuation input exists. Starts timing down when
actuation is removed. Stays in Passage when gap between actuations is less
than Passage Time setting.
Always times during green whether a serv confl call exists or not, except when
maxed out or when Simultaneous Gap is inactive and phase is gapped out. See
Simultaneous Gap Out.
In presence of a continuous actuation, phase will not gap terminate even if
Passage Time is set at zero. Both Passage Timer timed out and absence of
actuation must occur for a gap termination.

Glossary
Ped Clearance Thru Red

Ped Clearance Timer rests during Yellow and Red Clearance.
Peds do not see a shorter Ped Clearance during Green.
Must enable Ped Clearance Thru Yellow also.
Ped Clearance Thru Yellow

Ped Clearance Timer rests during Yellow Clearance.
Peds do not see a shorter Ped Clearance during Green.
Ped Clearance Timer

Flashing don’t walk portion of ped interval. Controller activates its Ped
Clearance output and flashes its Don’t Walk output.
Ped Clearance interval cannot be interrupted in normal operation. Normal refers
to no Preemption or Manual Control Enable active.
Ped Omit
Prevents ped service, normally used for TOD operation.
Ped Omit will inhibit a ped not that has not yet started timing.
Does not have an effect on a ped interval in the process of timing.
The Internal Coordinator automatically activates and deactivates ped omit
according to the permissive period control settings to achieve proper
coordinated operation.
Ped Overlaps
Purpose: To allow a given ped movement to be displayed with one or more
(non-conflicting) ped movements.
Do not confuse this with “to allow a given ped to be displayed with one or more
(non-conflicting) phases,” or vice versa. This is simply phase compatibility, ring
and co-phase group concepts.
Each Ped Overlap can be set to operate in Mode 1 or Mode 2.
Mode 1: Allows the ped overlap to appear with a parent phase ped interval, but
not remain in walk when transitioning between overlapping peds.
Mode 2: To allow a given ped movement to remain in walk while a parent phase
ped clears and the next phase is also a parent phase with a ped call in memory
(makes a ‘this ped next’ decision at end of parent phase walk).
Ped Overlap will only appear if a parent phase ped call is present. Vehicle calls
have nothing to do with Ped Overlap service.

Glossary
Ped Recall
Sequence control function that issues a constant ped call to the programmed
phase.
Ped Recycle
Per Ring NEMA Function that produces different phase responses depending
on actuated or CNA Mode.
Function can be assigned per phase in controller. The function itself is activated
via External Input or TOD CKT.
Actuated Mode: Only has an effect if Hold is applied (i.e., Coordination). If Hold
is applied, Ped Recycle is active and Ped Omit is not active, a ped call will serve
immediately regardless of the presence of a serv confl call. See “Ped Service in
the Actuated Mode” for more details.
CNA Mode: If the phase is in the green dwell/select state (green/don’t walk) and
no serv confl call exists, walk is recycled immediately.
Phase
One or more movements of traffic given right-of-way at the same time with a
unique position in the sequence and set of control parameters (timing, recalls).
Phases as Overlaps, Signals to Overlaps

Strategy where some or all field signals are outputs from controller Overlaps A-
P instead of Phases 1-16.
Very useful for non-standard intersections, diamond sequences, etc.
Ped Service in the Actuated Mode (Hold not applied)

A stored ped call will start at the onset of green if Ped Omit is not active.
Once green already starts, a ped call will serve immediately if [1] no serv confl
call exists, or [2] a serv confl call exists, Max Time remaining is greater than
walk plus ped clearance and Conditional Ped is enabled and Ped Omit is not
active. See Conditional Ped.
NEMA defines Ped Recycle as “any start of ped service after the onset of
green.”
Ped Service in the Call-To-Non-Actuated (CNA) Mode

Upon entry into green, walk will start provided Ped Omit is not active.
WRM and Ped Recycle will both recycle walk within same green interval if no
serv confl call exist and phase is in green dwell/select state (and no ped omit).

Glossary
If WRM and Ped Recycle are not active, ped will not serve again until a
conflicting phase is serviced and the CNA phase returns to green/walk.
Hold will maintain the phase in the timed out walk state.
Priority of Input Functions

The priority of input functions shall be in the following order:
1. Power-Up
2. External Start
3. Preemption
4. Phase/Vehicle Omit
5. Ped Omit
6. Interval Advance
7. Stop Timing
8. Automatic Flash
9. Manual Control Enable
10. Force Off
11. Hold
12. Ped Recycle
Recall
A means to provide recurring vehicle or ped demand on a phase even when no
real demand exists on such phase.
See Min Recall, Max Recall, Ped Recall and Soft Recall for details of recall
options.
Red Clearance Timer

Red Clearance Time that determines the period of all red in the timing ring
before the next conflicting phase begins.
Red Rest
Per Ring NEMA Input function activated by Ext Input or TOD Circuit
Additional Red Rest function is supplied by separate per phase programming
area in controller that takes precedence over NEMA Red Rest Ring Inputs.
Phase will gap out into red rest at the end of its actuated processing if no serv
confl calls exist.
Once in Red Rest, registration of a serviceable call will result in phase serving
immediately.
See Red Revert below.

Glossary
Red Revert (Min Red Revert)

Provides a guaranteed red time when terminating a phase before returning back
to it again.
Times concurrently with Red Clearance Timer.
Typically seen in Red Rest or Preemption.
Up to the point of phase re-entry, a serv confl call will cause phase termination
in the normal manner.
Red Revert is unaffected by Omit Red Clearance input.
If an Overlap is inhibited from returning to Green due to Red Revert Timer, any
Parent Phase of the Overlap is also inhibited from turning Green.
Controller provides an optional 2-second Minimum Red Revert feature.
Ring
Two or more phases that must be sequentially timed
Phases in the same ring are conflicting
Serviceable Conflicting Call

A call for a phase that conflicts with the active phase in question.
Phase/Vehicle Omit is not active on the calling phase, enabling such phase to
be serviced.
Signal Head Steering

Powerful option where any set of Vehicle, Ped, Overlap, Ped Overlap and On-
Next-Check outputs can be steered (in groups of three) out any of the NEMA
MSA, B, C connectors (Veh 1-8, Ped 1-8, OVL A-D, On-Next-Check 1-8).
Allows access to phases and overlaps that do not normally have dedicated
outputs (i.e., OVLS E-P, Ped OVLS A-P, Phases 9-16, On-Next-Check 9-16
etc).
Eliminates need for custom cabinets or revised cabinet wiring.
Enter Steering Code (see operating manual) and enable “Signal Head
Program”.
Simultaneous Gap Out (SGO)

Only applies when the next phase(s) in the sequence are in a separate Co-
phase Group and a call exists for one of these phases (multiple ring only).
When enabled and a phase gaps out and the concurrent phase is still in
Passage, the phase enters Green Rest and will restart its Passage Timer if new

Glossary
demand arrives. This can happen back and forth across the two phases until
they reach a simultaneous point of gap termination.
When disabled and a phase gaps out, the phase is “latched” into a rest state
called Green Prep waiting for the concurrent phase and will not restart Passage
Timing if new demand arrives.
Applies to any phases in ring structure that may “cross the barrier”, (i.e., not just
2/6 and 4/8) when controller is as far “against” the Barrier as it can get due to
calls.
SGO has no effect when walk and ped clearance are timing.
Same concepts apply for 3 and 4 Ring operation.
Single Entry
Occurs when Dual Entry is not enabled.
Allows a single phase to be selected and timed alone if there is no compatible
phase with demand in the other Ring.
When the single phase is timed alone, a call registering for a compatible phase
in the other ring will start timing immediately regardless of other calls present
(provided coordination permissive period is not closed or any other restrictions
are imposed).
Soft Flash
Flashing operation achieved through the controller outputs to load switches.
Soft Flash must be used in TS 2 Type 1 applications.
TS 1 Limitation exists for any outputs to be Dark (i.e., peds monitored on
separate channels) in that a Red Fail fault will occur. Also, TS 1 Monitor Red
Fail recognition time must satisfy Soft Flash.
TS 2 can tolerate Dark outputs because Controller sends a flash bit to MMU that
prevents Red Failure.
Wig-Wag = Circuit 1-Circuit 2 flashing operation.
Entry: Phase/Ped Omit is applied to all phases except “UCF Last” phases so it
cycles to these phases and enters Soft Flash after serving them.
Exit: Phase/Ped Omit is applied to all phases except “UCF Exit” phases and
force off to all rings so that it cycles to these phases and then exits Soft Flash.
During Soft Flash, controller cycles in the “background” according to detector
activity.
Soft Flash may be activated by MS-A Test A or Test B Inputs; set UCF Test A,
Test B = Y, and enable Soft Flash.

Glossary
Soft Recall
Sequence control function that applies an automatic call to the programmed
phase(s) when [1] the unit is not in these phase(s), and [2] no phase detector
inputs are active.
Example: 4-Phase Ring, Soft Recall is set for phase 2. Operation is the
following: If phases 1, 3, 4 have constant calls, it will cycle to all phases except
phase 2. If 1, 3, 4 calls are removed, it will go to phase 2 and rest. If only phase
4 has a call, it will stay in phase 4 indefinitely (with 4 Max Timer not timing).
Standard Overlap
A set of G-Y-R outputs associated with “parent phases”.
An Overlap remains green when a parent phase is terminating and another
parent phase is next.
Overlap terminates with parent phase if next phase is not a parent phase and
no parent phases are active in other ring(s).
Overlap uses the Yellow and Red Clearance times from the terminating parent
phase.
Stop Bar Mode 1

Detector calls the phase during yellow and red.
During Green, detector extends phase as long as there is no break in detection
zone.
As soon as zone is empty, or Stop Bar Timer = 0, the detector is disconnected
for rest of green state.
Stop Bar Mode 2

Detector calls the phase during yellow and red.
During Green, detector extends the phase and Stop Bar Timer acts just like
Passage Timer.
Once Stop Bar Timer = 0, the detector is disconnected for rest of green state.
Stop Timing
Per Ring NEMA input function.
Causes controller ring timing to cease (freezes controller).
When applied, activation of Interval Advance is the only way to terminate the
current ring interval.
Vehicle and ped calls are recognized as normal.

Glossary
Operators typically use this function in conjunction with Interval Advance during
Bench Tests to see controller cycle interval-by-interval.
When an MMU/CMU Fault occurs, Stop Timing in all rings is applied to the
controller.
Stretch/Delay Detector
Two modes in one: Stretch & Delay
Stretch causes an actuation during green to be artificially extended by the
Stretch Time. Useful when a phase with multiple lanes have stop bars at
different positions, requiring different ‘passage’ times to clear the intersection.
Delay mode delays calls to controller once detection zone is occupied and
phase is not green. Useful for right-turn-only lane or protected-permissive left
turn.
Time Before Reduction

Purpose: To delay onset of Gap Reduction to give the phase an opportunity to
gap out at the normal level.
Gap reduction (Time to Reduce) does not begin until this Timer = 0.
If all serv confl calls are withdrawn, this Timer is reset immediately and waits for
the next call.
Time To Reduce
Volume Density interval that begins timing at the end of Time Before Reduction.
During this interval, Passage time required for a gap out is reduced each
second by a value equal to ((Normal Passage – Min Gap)/Time to Reduce).
When Time to Reduce = 0, phase reaches level of Min Gap.
If all serv confl calls are withdrawn, Time to Reduce is reset and Passage Timer
returns to normal value.
Uniform Code Flash (UCF), Automatic Flash

Controller drops CVM, causing MMU/CMU to place intersection in fault (flash)
condition. Only applicable for TS 1 and TS 2 Type 2 applications.
UCF Last Phases: Phases serviced before entering UCF. Phase/Ped Omit is
applied to all other phases when UCF is called.
UCF Exit Phases: Phases serviced immediately when UCF is finished.
Override Hold: Allows quick entry into Flash even if Hold is applied to the
coordinated phases, allowing entire corridor to enter at the same time.
UCF Test A, Test B: Causes MS-A Test A or Test B inputs to call UCF.

Glossary
Vehicle Omit (Phase Omit)

Prevents a phase from being selected next.
Once phase is on or next, phase omit activation has no effect on phase.
When programmed through keyboard, it is normally used for TOD omitting.
The internal coordinator automatically activates and deactivates vehicle omit
according to the permissive period settings to achieve proper coordinated
operation.
Preemption overrides Vehicle Omit so that phases exclusively for Preemption
can have Vehicle Omit applied to prevent service during non-preempt operation.
Volume Density
Two aspects in one: [1] Volume=varying Initial, [2] Density=reducing the time
required for a gap out.
Volume: Phase times a cycle-by-cycle varying Initial interval that is dependent
on the number of vehicles stored on the phase between detector and stop bar.
Used for setback loops to eliminate the need for a ‘large’ Initial every cycle,
assuming 100% storage between detector and stop bar.
Density: The longer the green is held in Passage with a serv confl call, the
closer the vehicle spacing has to be in order to retain the green interval.
Volume Controls: Added Initial, Initial, Max Initial
Density Controls: Time Before Reduction, Time to Reduce, Passage, Min Gap
Every application can use the Density aspect (high speed set back loops or for
snappier cycling with stop bar loops).
Volume aspect is only useful if setback loops exist.
Walk Rest (in the Actuated Mode)

Allows an actuated phase to rest in walk instead of green/don’t walk.
When a serv confl call arrives, phase enters Ped Clearance, Max Timer starts,
and phase may extend in green/steady don’t walk according to demand.
Walk Rest Modifier

A NEMA per unit function that affects a phase in the CNA Mode only.
The state of this function has no effect unless CNA is active.
Per phase programming of phases that will respond to this function when it is
activated.
External Input or TOD activates the function.

Glossary
Causes a CNA phase to remain in the timed out walk state in the absence of a
serv confl call regardless of the Hold state.
Also causes a CNA phase to return to walk when in the green dwell/select state
and no serv confl call exists.
See Enhanced Ped Operation
QUICK GUIDE TO COORDINATION FUNCTIONS

4 Splits Per Cycle
Provides 4 Splits for each Cycle 1-6 instead of 24 Splits.
4 Splits per Cycle = Y typically used when Phase Allocs are in seconds.
4 Splits per Cycle = N typically used when Phase Allocs are in % so any of the
24 Splits can be used with any Cycle.
Auto Permissive Mode

Powerful utility that calculates permissives and force offs automatically.
Permissive calculation is determined by a choice of three Permissive
Modes/Types: Yield, Single, Multiple Permissive.
Auto Permissive Mode automatically enables Enhanced Perm so that the
normal phase rotation takes place and demanding phases will serve provided
they are able to force off on time. See Enhanced Perm for details.
Background Cycle
The cycle that occurs if constant calls exist on all phases and they are forced
off.
Appears as a Fixed Time controller.
Used in generating the time-space plot (green band development).
Check Coord Plan

Routine that checks validity of each Cycle-Split combo.
Checks for [1] Cycle = 0, [2] Coord Phases incompatible, [3] No Coord Phase in
each Ring when applicable, [4] Ring Alloc Sum not = 100%, [5] Phase Min Time
+ 1” < Phase Alloc, [6] Yield % = 0 or greater than 10 when Yield selected, [7]
Equal Co-Phase Group Allocations.
Co-Phase Group Allocations do not have to be equal in sequences where a
phase is in more than one Co-Phase Group.
Coord Failure
Coordinator is in a latched Free state due to two consecutive Cycle Faults.

Glossary
Power down is the only way to clear this fault.
Coord Out of Step

Occurs when “Number of Cycles to Out of Step” is set non-zero and coordinated
phases are not on at Local Zero for the consecutive number of cycles specified
by the non-zero value.
Coordinator reverts to Free and power down is the only way to clear this fault.
Coordinated Phases
The phases that are synchronized with neighboring intersections to provide the
required movement of vehicles along the street at a planned speed.
The coordinator requires designation because automatic Hold is applied when
no permissive periods are active and no perm is calculated for coord phases.
Coordinated Phases are not given a permissive period—they are the phases
that yield to non-coord phases according to their permissive periods.
When not in CNA Mode, the coordinator allows an actuated coord phase to
operate without being on recall. Therefore, if coord phase recall is required and
is not normally set for the active Timing Plan, it must be programmed using an
additional Timing Plan, then “C/O/S to Timing Plan” feature.
Coordination
Process in which a series of intersections have main street phases
synchronized to provide progression through a series of intersections at a
planned speed.
Accomplished by [1] “holding” coord phases until the yield point, [2] “forcing off”
non-coord phases at pre-determined points and [3] allowing selective service to
non-coord phases and peds as determined by the permissive periods.
Basic coord functions are Hold, Force Off, Vehicle/Ped Omit, CNA, WRM, Ped
Recycle and Inhibit Max. A given application may not use all of these.
Typically, all intersections have same Cycle Length or a multiple thereof.
Double Cycling: an intersection set at twice the dominant cycle length used.
Half Cycling: an intersection set at half the dominant cycle length used.
Cycle
Total time to serve all phases.
Coordinator allows up to 6 distinct Cycle lengths with 4 Splits per Cycle =Y or 24
Cycles associated with 24 Splits.

Glossary
Cycle Fault
A fault occurring because the controller has not answered a call within two times
the cycle length, starting from the time the call is registered.
Coordinator releases to Free and attempts to serve the demand. If served, it
retries Coord Mode with “Coord: Coord Fault” status for the next two cycles.
If a second Cycle Fault occurs within two cycles following the Coord retry
(during “Coord: Coord Fault”), the coordinator latches into Free with “Free:
Coord Failure” displayed.
Power down is the only way to clear the fault.
Cycle/Offset/Split to Lead-Lag
Allows pattern-related lead-lag operation.
Must select lead-lag Mode 0 (TOD/COORD) or Mode 1 (COORD) in Controller
Options area for it to work for the programmed C/O/S pattern.
Cycle/Offset/Split to TOD Circuits

Allows pattern-related TOD Circuit Activation.
Value for Cycle = 1-6, 7 = any Cycle
Value for Offset = 1-5, 6 = any Offset
Value for Split = 1-4, 5 = any Split
Value for Free: 0= Free, 1 = Coord, 2 = Free or Coord
Cycle/Split to Timing Plan

Allows any of the 4 Timing Plans to be activated by Cycle/Split combination.
Matrix entry format.
EGB Percent (Extended Green Band)

Allows a 0-100% period of coordinated phase extension due to demand.
Coord phase demand times more than its Phase Allocation Time even when
starting at normal point—“steals” time from the first non-coord phase
Must set End of Main Street = N.
One EGB value in effect for all patterns involving actuated coord phases.
Coordinated Phases must have detection and be in actuated mode (CNA off).
Coord phase force off does not occur at normal point, coord phase demand
causes it to “cut into” next phase’s split, then forces off or gaps out.
To prevent skipping first phases after coord phases, over-allocate those phases
and use Max Timer in case the coord phases do not extend.

Glossary
Equivalent operation can be achieved with Manual Perm and Force Off and
overcome bullet item 4 above (allow extension by TOD or C/O/S).
End of Main Street

Option to place local zero at end or start of coord phase.
When enabled, local zero is at [1] end of coord phase green when actuated and
[2] end of walk when CNA is applied and Lead-Lag is not active.
When enabled, Lead-Lag is programmed (for the coord phase Co-phase set),
and Auto Perm is enabled, Local Zero occurs at the lag left Force Off point.
When disabled, Local Zero occurs at first coord phase that normally starts.
End Permissive Point

Point in the cycle at which the phase in question can no longer be selected as
next phase and subsequently serviced (no longer able to satisfy its force off
obligation if served).
Phase Omit is applied at End Permissive Point
Value determined by Auto or Manual Permissive Mode.
Auto End Perm: EP = FO – INITIAL – PhaseOnClearance
Auto End Ped Perm: EPP = FO – WALK – PED CLR - PhaseOnClearance
Enhanced Permissive
An option where when a non-coord phase is on, all perms operate as if their
start perms were all set at zero.
This feature only has an effect when all the perms do not start at the same
point.
Auto Perm automatically enables Enhanced Perm; it should be enabled in
Manual Perm Mode in almost all cases.
End result is that all remaining perms activate when the non-coord phase starts
so that the normal phase rotation occurs.
When disabled, a phase’s start perm occurs as programmed and preceding
phases may gap out and return to the coord phases despite demand on the
next phase.
Take into consideration which phases start or end at Local Zero when using
Enhanced Permissive with Manual Perm & FO Mode.
Fixed Force Offs

Force Off option that maintains the force off point at its normal fixed position in
the cycle.

Glossary
If a phase starts early, it receives extra time if it does not gap or max; per unit
option.
Fixed Force Offs per phase can be achieved by using the Max Timer (Max =
Alloc – Y – R) for phases that will not operate in Fixed Force Mode so that these
phases will max out before forcing off if they start early.
Floating Force Offs

Force Off option that provides all unused non-coord phase time to the start of
coord phases; per unit option.
If a non-coord phase begins early, it will force off early.
Coord phase force off point always remains fixed in the cycle.
In the 3000E, the fixed force off point acts to “lock phases to the background
cycle” by forcing off late-starting phases.
Floating Force Off can also be achieved with Max Timer regardless of Force
Mode selected.
Fixed Force Offs per phase can be achieved by using Max Timer = “Phase Alloc
– Y – R” of phases not desiring Fixed Force Offs.
Free Mode
Mode of non-coordinated operation of the controller as if it were isolated.
During very low volume periods, arterials are usually set to Free Mode or Flash.
Free Mode automatically occurs if no coordination pattern is called and no Flash
event is active by Circuit 11 (FRE).
The Internal Coordinator releases coord controls and sets the unit Free when
Stop Timing, Manual Control, Flash, External Start or Preemption is active.
Fully Actuated Coordination

Allows (1) early coord termination via gap out and (2) re-service within the same
cycle after an early return if coord phases gap out before perm closes.
All phases must have detection (main street set back loops work best).
Early Termination: Coord phase consists of a guaranteed portion (Hold applied)
and a variable portion (time between Hold release and Force Off point).
Unused time at tail end of coord phase (coord gap out) can be awarded to
start of coord phases or non-coord phases for maximum efficiency.
Auto and Manual Perm supports fully actuated coord; see RGB and EGB.
Re-Service: If coord phase returns early and perms are open with calls on
associated phases, these phases can be serviced within the current cycle if the
coord phases gap out before the perm ends.

Glossary
Local Cycle Timer

Local Cycle Timer that counts up.
The Local Cycle Timer reaches zero “x” seconds after the Master Cycle Timer
reaches zero where “x” is the Offset.
Local Zero
The zero point in the cycle where the coord phases normally Begin or End as
determined by “End of Main Street” setting.
Manual Permissive and Force Off

Option allowing user to customize perms and force offs.
Enhanced Perm should be enabled to ensure normal phase rotation.
Phase Allocations not required if Fixed Force Offs enabled.
Phase Allocations must be set for Floating Force Offs enabled because
coordinator to use Phase Allocations to determine when to issue force off.
Master Cycle Timer

Master Reference Cycle Timer that counts up.
Provides the reference for all offsets.
Maximum Dwell Time

Per cycle entry
Determines maximum dwell time per transition cycle when Dwell Offset
Seeking.
Minimum Cycle Length

Determines the shortest transition cycle possible when Short Route Offset
Seeking.
If it is not set more than 17% less than the Cycle, Short Route Mode will do Add
Only if Offset change is > 17% and < 50% away.
Multiple Permissive
One of three Auto Permissive Modes.
Starts all permissives at coord phase force off point and proceeds to any phase
with demand.
Each permissive ends sequentially when Initial interval cannot be completed
prior to force off if phase were serviced.

Glossary
Minimizes delays on non-coord phases by providing the longest possible perm

for each phase to let the coordinator “wait” for late demand.
No Early Coordinated Phase Ped

Applies to actuated coord phases only.
Prevents coord peds from starting prior to normal time in background cycle by
temporarily applying Ped Omit.
Useful during re-service operation so that coord ped does not interfere with
coord phase termination until all perms have ended.
No Early Release
Per Cycle/Split combination
Applies a constant Hold to all phases programmed—even coord phases.
Does not call the phase. Phase requires other means to place call.
Phase can only terminate via Force Off.
Use on non-coord phases to minimize excessive non-beneficial early returns to
coord phases via gap outs.
Use for cross-artery coordination if early start of cross street is not desired;
Single Perms with No Early Release to 3/7 can prevent early starting 4/8 cross
street. Then use No Early on 4/8 if you want to time to force off every cycle.
Use on coord phases to prevent terminating multiple times in the same cycle if
long perms are used and coord phases return early in a given cycle.
No Ped Clearance Offset Adjust

Applies only to CNA coord phases and End of Main St = Y.
Zero still occurs at end of walk.
When enabled, prevents coordinator from adjusting “actual offset” to account for
Ped Clearance interval.
If enabled and if Offset 1 = 0” and coord phase Ped Clearance = 20”, “Local
Offset” is 0” (not adjusted for Ped Clearance).
If not enabled and if Cycle = 100 and Offset 1 = 0” and coord phase Ped
Clearance = 20”, “Local Offset” is 80” (adjusted for Ped Clearance).
Adjust formula: “Local Offset” = Programmed Offset – Ped Clearance time.
Number of Cycles to Out of Step

Value of 0 disables, value 0-255 activates.

Glossary
If coord phases are not ON at Local Zero for the consecutive number of cycles
specified, coordinator reverts to latched Free Mode with “Free: Coord Out of
Step” displayed as Coord Status.
Power down is only way to clear.
Offset
Time to account for vehicle travel time throughout an arterial.
Amount of time that Local Zero follows Master Zero.
Current Offset at any given time = Master Cycle Timer – Local Cycle Timer. If
subtraction yields negative number, add one cycle length to yield a value
between 0 and Cycle-1.
Offset Seeking, Add Only

Seeks offset by lengthening the cycle timer up to 20% each transition cycle.
Local Cycle Timer counts up at a slower rate.
Extra time is evenly distributed among all phases.
Should never take more than 5 cycles to get in step.
Offset Seeking, Dwell

Seeks offset by dwelling in coord phases at the Local Zero point.
Cycle is lengthened by extra time to coord phases
Dwells until in step or Max Dwell Timer expires.
Max Dwell Time determines how many transition cycles will be required.
Offset Seeking, Short Route

Seeks offset by shortening or lengthening cycle timer (times 17% fast or 20%
slow) each transition cycle until offset is reached.
Minimum Cycle Length can override “fast timing” and cause “slow timing” (Add-
Only) instead if the coordinator’s calculations determine “fast timing” will violate
Minimum Cycle Length.
Ped Override Mode

Activated by Time of Day Circuit 97.
Used for a low volume actuated ped that is oversized (Walk+Pclr+Y+R > Phase
Alloc), and it is acceptable to occasionally go out of step when ped serves.
At Force Off point, local cycle timer pauses until ped clearance is done, offset
seeking begins immediately, cycle timer resumes when ped done, subsequent
phases are not skipped or short timed.

Glossary
Ped Override Mode sets EPPn = EPn.

To allow oversized ped to short-time subsequent phases without going out of
step, over-allocated ped phase and under allocate subsequent phases and use
max timer when ped does not serve. To allow skipping (i.e., 5-section left turns),
use Manual Perms & Force Offs.
Ped Override Mode works best with Short Route Seeking because it can usually
re-sync in one cycle if the ped is not more than 17% larger than allocation.
Ped Permissive
Per Unit Manual Ped Perm Value for all peds
Ped Perm Value of 0 sets Auto Ped Perm
May use Auto Ped Perm and Manual Vehicle Perm, or vice versa
Start Ped Perm always equals Start Vehicle Perm in Auto or Manual.
Manual Ped Perm: End Ped Perm = Start Perm + Non-Zero Ped Perm Value.
Auto Ped Perm: EPPn = FOn – WALKn – PCLRn – PhaseOnClearance.
If Ped Override Mode active, EPPn = EPn.
Permissive Period
A period bound by start and end points where the controller may selectively
service non-coord phase vehicle and ped demands as controlled by the
application of vehicle and ped omit.
In times of heavy traffic with calls on every phase, the beneficial effects of
various permissive strategies start to diminish; the unit behaves like a fixed time
unit.
Phase Allocation
Amount of time given to each phase in sequence.
Phase Alloc includes Green + Yellow + Red (and Walk and Ped Clearance if
applicable).
Phase Allocation must be one second or more larger than [1] Initial + Yellow +
Red if Ped Override Mode is enabled, or [2] one second or more larger than
MAX(Initial, (Walk + Ped Clearance)) + Yellow + Red if Ped Override Mode
disabled.
Set of Phase Allocations for all phases is called a Split Plan.
Phase Allocations are used by coordinator in [1] Auto Perm Mode, and [2] in
Manual Perm & FO with Floating Force Off enabled.
Fixed Force Off with Auto Perm disabled does not require Phase Allocation
entries; Force Off points determine the green times.

Glossary
RGB Percent (Reduced Green Band)

Actuated Coord phases only, must have detection
Must set End of Main Street = N.
One RGB value in effect for all patterns involving actuated coord phases.
Allows 0-100% “early yield” point, Hold is released on coord phases and perms
open, but does not force off until the normal point.
Allows a more responsive system when platoon size and arrival time varies
each cycle. If end of green band contains no demand, that time is better used
on other demanding phases.
If coord phases are allowed to end early, that unused time can be given to start
of coord phases (Floating Force Offs) for extra queue discharge time before
platoon arrives, improving efficiency and progressions.
Equivalent operation can be achieved with Manual Perm and Force Off and
overcome bullet item 3 above (allow part-time early yield only).
Semi-Actuated Coordination
CNA or Max Recall applied to coord phases.
Coord phase must time its full Phase Allocation regardless of demand.
Actuated non-coord phases dependent on detector actuations for service and
extension of green.
Single Permissive
Provides unused time to the end of coord phases.
Each perm starts sequentially such that a yield to the phase directly from the
coord phases will start the phase at its normal position in the background cycle.
When a call is not present for the current permitted phase, the unused time is
awarded to the end of the coord phases.
Used with Floating Force Offs can give unused time to start and end of coord
phases, widening the green band.
Enhanced Perms automatically enabled. See Enhanced Permissive.
Best suited for heavy coord phase demand even when not in the green band
portion and the goal is to widen the end of green band instead of widening the
start of it (early return discouraged).
If coord phase demand is light when not in the green band portion, staying in
the coord phases too long may waste time if no call on 3/7, but calls exist on 4,
8, 1 & 5.

Glossary
Split
Set of Phase Allocations
Division of Cycle Time to each phase in the sequence.
Split Matrix
When enabled, the matrix Split value for a Cycle-Offset combination is used to
select Split regardless of the source.
A zero value for a Cycle/Offset combo causes the source to determine the Split.
Start Permissive Point

Point in the cycle during which the coordinator is allowed to service/select a
non-coord phase as next phase. Vehicle and Ped Omit is removed.
Typically set to provide unused time to the end of the coord phases by starting
perms at different points.
For example, if 3/7 do not have a call and it is desired to give 2/6 coord phases
10 extra seconds before moving to demand on phase 4/8, simply set 4/8 start
perm = 10 (assuming coord phase force off = 0).
• Auto Single Permissive Mode automatically sets Start Permissive Points in a
sequential manner to provide unused time to the end of coord phases.
Transition Cycle (see Offset Seeking)

An intermediate Cycle between pattern changes.
May be larger or smaller cycle depending on Offset Seeking Mode selected.
Cycle and/or Offset changes typically require Offset Seeking and Transition
Cycles.
For larger Transition Cycles, extra time may be distributed among all phases
(Add Only) or given to the coord phases (Dwell).
Yield Percent
1-10% valid range used in Yield Permissive Mode.
Yield Permissive
Provides a 1-10% window of opportunity for non-coord phase demand to be
allowed service in the current cycle.
Demand arriving after the Yield Window closes must wait until the window
reopens in next cycle.
Once demand arrives during Yield Window, perms are fully opened (as in
Multiple Permissive operation) and all phases are allowed in the normal order.

Glossary
Coordinated Phase receives a constant Hold.

Best suited for a mainline that is heavily traveled even outside the green band
portion and it is desired to return to coord phases as soon as possible.
Yield Point
Point in the cycle when the first permissive period(s) start and coord phases
may terminate via deactivation of Hold and/or activation of Force Off.
QUICK GUIDE TO PREEMPTION FUNCTIONS

Cyclic Interval
Interval that behaves like an actuated phase.
Cyclic is programmed by not setting Interval as Fixed or Dwell.
A time entered for interval loads Max Timer with that value—dedicated max
timer per Cyclic Interval per Run.
On first “pass” through, all cyclic intervals are serviced in a Min Recall fashion.
Only one interval is required for Cyclic. Green/Don’t Walk=only vehicle allowed
service OR Green/Walk = ped and vehicle allowed, but only if ped and vehicle
calls.
All Cyclic Intervals must be Exit unless a Fixed Interval follows.
Any interval type may follow Cyclic Intervals.
Cyclic Intervals may be serviced multiple times along with any Fixed Intervals
that normally follow.
Delay Time
Delay time prior to entering Preemption Run.
Controller continues normal operation (does not force off or omit any phases).
If Preempt Call goes away during Delay Timer and Input Lock is disabled, the
Run will not be serviced.
Dummy Preemption Phase

Phase used exclusively for Preemption only.
Must be programmed in Ring and Co-Phase Group and programmed in
appropriate PE Intervals in order to appear during Preemption Run.
Apply Vehicle Omit to prevent phase from timing during start-up and normal
operation (omitted phase can still serve during Preemption).
Dummy Phase must be used for Intervals involving Overlap service only.

Glossary
Duration Timer
Timer determines a “minimum” Preempt Run Time.
Begins timing at the first Cyclic or Dwell Interval.
Exit from Preemption occurs when [1] Duration Timer = 0, [2] Preempt Call is
not present and [3] an Exit Interval is reached.
Duration Timer as Gap Timer

Duration Timer acts like Passage Timer.
If Preempt Input is not steady, the call is maintained as long as time between
calls is less than Duration Timer value.
Dwell Interval
Interval where controller will rest until exit criteria are met.
Time for Dwell Interval is ignored.
Once in a Dwell interval, it remains there until Duration Timer = 0 and Preempt
call is not present.
When Duration Timer = 0 and Preempt call gone, it exits to normal operation (if
Dwell is an Exit Interval) or exits to a Fixed or Cyclic Interval (if Dwell is not an
Exit Interval), then to normal operation.
Only one interval (G/W or G/DW) is required; phase uses its normal clearances.
Should a Dwell Interval follow Cyclic Intervals, the Dwell Interval is only serviced
if demand exists.
Exit Calls
Temporary Min Recalls are placed when exiting to ensure these phases are
serviced.
Exit Interval
Interval in which the unit may exit from Preemption.
Only restriction is that all Cyclic Intervals must be Exit when not followed by a
Fixed Interval.
Exit to Coordination
Exits to Coordination in step with Permissive controls.
Offset Seeking not required.
Controller serves next phase in the sequence with an open permissive period.

Glossary
Exit to “Exit Phases”

Exits to the programmed phases in Free Mode.
Performs Free-To-Coord Transition if Coord active.
Exit to Next Phases With Demand

Exits to the next phases with demand in Free Mode.
Exit to Resume Interrupted Sequence

Controller exits to the phases that were forced off to enter Preemption Run.
Fixed interval
Always demands service and times a Fixed interval and advances to the next
serviceable interval. Can “dwell” green if there is no serviceable interval to
follow.
For a Run consisting of just a Fixed interval, only one interval (G/W or G/DW) is
required. Such a Run behaves like a Dwell Run.
Flash Plan
16 Flash Plans provided.
Wig and Wag = Circuit 1 and Circuit 2, Flash Yellow, Red or Dark Output
Plans 1-16 can be associated with each Interval.
0=Normal Steady Color, 1=Flash Wig, 2=Flash Wag, 3=Dark.
Go To Higher Run
Allows current run to be suspended and control transfer to a Higher Priority
Run.
After Higher Priority Run is done, the interrupted Run resumes if call is still
present.
Input Lock
Locks Preempt Call and will serve the Run.
With a Delay Timer > 0, the Run is still served if call is removed during Delay
Timing.
Interval
Amount of time where controller outputs are in the programmed state.

Glossary
Fixed, Dwell, Cyclic, All Red, Dark Signals, Flashing.
Interval Controls
Fixed Intervals after Cyclic Intervals may be re-serviced, but not a Fixed Interval
with no Cyclic Interval before it.
A Dwell Interval followed by Cyclic Intervals is only serviced if demand exists.
On the first “pass” through”, all Cyclic Intervals serve in a Min Recall fashion
regardless of demand.
Interval Data
Valid Interval Y/N
Dwell Interval Y/N
If Dwell and Fixed = N, it is Cyclic Interval
Tenths Y/N
Ped Clearance Thru Yellow Y/N
Exit Interval Y/N
Fixed Interval Y/N
Time (0-255 or 0-25.5)
Phase Flash Plan (1-16)
Ped Flash Plan (1-16)
Phase and Ped Colors (G-Y-R-W-P-D)
Max Intervals
Maximum of 32 Intervals per Run
Total of 72 Intervals allocated among 6 Runs
Overlaps in Cyclic Intervals

Program the Overlap Greens with the associated Phases included in the
Interval.
Double Clearing Overlaps are not respected in Cyclic intervals.
Ped Clearance Thru Yellow

Independent of the Ped Clearance Thru Yellow in the phase options menu.
Priority
NEMA Priority (per unit parameter): Run 1 Highest, Run 6 Lowest.

Glossary
User Priority: Each Run given value 1-6. Runs with same Priority are served first
come, first serve basis.
Railroad Run
Input must remain active for 1.5 seconds before recognition.
Must remain inactive for 3 seconds before terminating the Run.
Re-Service Timer ignored.
Re-Service Timer
Prohibits re-servicing the Run until Timer = 0.
Ignored for Railroad Runs.
Run Enable
Enable must be activated in order for controller to respond to Preempt Input.
When changing Run parameters, Run Enable must be set at “N”.
Run parameters cannot be changed when Run is active.
Tenth Interval
Per Interval allowing data entry in one second or one-tenth second increments
(0-255 or 0-25.5).
Valid Interval
Allows Interval to be timed during the Run.
Useful for leaving unused intervals in place for future expansion.

Glossary
ACRONYMS
3000 Series — A line of traffic controller hardware produced by Peek Traffic.
AC — Alternating Current
Barrier — A logical term to describe a line of compatibility in a multi-ring signal plan in which all rings are
interlocked. Barriers assure that there will be no concurrent selection and timing of conflicting phases for traffic
phases on different rings.
BIU — Bus Interface Unit, required to interface a TS 2, Type 1 controller to any type of cabinet hardware.
CA — Controller Assembly
Cabinet — An outdoor enclosure for housing controller units, master units, detector electronics and other
associated equipment.
CLMATS — A software package created and maintained by Peek Traffic Systems that allows traffic
management personnel to interact with and control a variety of Master and Controller hardware. Stands for
Closed Loop Multi-Arterial Traffic Control System.
CLR — Phase Clearance. Includes Ped Clearance times for CNA phases.
CNA — Call to Non-Actuated. Provides a method of phase timing where vehicle and pedestrian detectors are
not required to serve the associated phases, with operation as defined by NEMA.
Coordination — The state where two or more intersections are configured to communicate with each other in
order to time their signals in some manner that improves the greater system performance, rather than being
timed independently at each intersection.
CRC — Cyclical Redundancy Check
DCMATS — The software predecessor to CLMATS, originally only communicated with single controllers
DLL — dynamically linked libraries, in the Windows environment, programs store data, graphics and other
resources in these linked libraries. CLMATS uses a number of them.
EEPROM — Electronically eraseable/programmable read-only memory, the programmable memory storage
area on the LMD-40 and several other traffic control components.
EGB — Extended Green Band
EP — End of Permissive
EPP — End of Pedestrian Permissive
FO — Force-Off
FOM — Fiber Optic Modem, a device that modulates a signal appropriately for transmission over fiber optic
cables
FSK — Frequency shift key
Greenband Analysis — a method of analyzing the amount of green light time available in a set of coordinated
traffic intersections.
Hz — Hertz, a unit of frequency indicating cycles per second
INIT — Initial or Initialization
Intersection — a Controller assigned to a location
Interval — A unit of time that is assigned a certain of controller behavior and signal output in a time-based
(non-NEMA) controller.
ITS — Intelligent traffic systems
Local — Connection to a Controller unit
M3000 — The model number of a master unit manufactured by Peek Traffic. Often used in conjunction with
Peeks’ Series 3000 and Series 3000E Traffic Controllers
MCE — Manual Control Enable
MIZBAT — A communications protocol used with some of the traffic control electronic hardware supplied by
Peek Traffic Corporation in the United States. It is used with the 3000 and 3000E series of traffic controllers,
as well as for communications with the M3000 master controller, and also LMD-40 and LMD-9200 controllers

Glossary
that have the MATS software installed. MIZBAT is used to communicate between a PC and any of the above
devices, as well as for communications between any of these devices that are connected to one another (such
as between an M3000 and local controllers.)
MMU — Malfunction Management Unit
MOE — Methods of efficiency
MSCLR — Main Street Clearance
NEMA — National Electrical Manufacturers Association. The industry group that has designed one of a couple
of competing standards for intelligent traffic control systems.
PA — Phase Allocation
PE — Preemption
Ped — Pedestrian or Pedestrian phase
PED CLR — Pedestrian Clearance Interval
Phase — a single traffic movement. NEMA compatible controllers typically manage the intersection in terms of
phases, while earlier controllers use intervals and circuits instead.
PTSI — Peek Traffic Systems Inc.
RAM — Random Access Memory. The main memory of a computer while power is on. Typically does not
maintain its memory when power is turned off.
RGB — Reduced Green Band
ROM — Read Only Memory, hard written memory in a computer that is maintained even when power is
removed. Typically used to store basic OS code and firmware programs.
SP — Start Permissive Period
SPL — Split, in a coordinated traffic system, each intersection in an artery must have the same cycle time. So
instead of set times for each phase, a coordinated intersection has a split assigned to each phase. A split is a
percentage of the total time available in the cycle.
SPP — Start Pedestrian Permissive Period
TCP/IP — The most common pair of protocols used to send data across an Ethernet or the Internet. Each
component in such a system is assigned a unique IP address. IP addressing is used by the various
components of CLMATS.
T/F — Terminal and Facilities
TOD — Time of Day
WALK — Walk Interval Time
WRM — Walk Rest Modifier

Index
12 phase D module....................................... 25, 449 acronyms ............................................................. 503

170 .......................................................................... 6 activate
1880EL ................................................................. 19 security............................................................. 17
24 split mode ...................................................... 261 activate mapping................................................. 405
24 volt failure ....................................................... 35 activating
24V supply current ............................................... 63 I/O mapping ................................................... 406
3000 controller ....................................................... 8 activation inputs.................................................. 157
3000 series.......................................................... 503 active ..................................................................... 36
3000E active run............................................................... 60
flash memory enabled ..................................... 10 active user-defined TOD circuits........................ 414
3000E controller..................................................... 9 actuated mode .............................................462, 480
3800EL ............................................................... 347 actuated phase mode ........................................... 475
3800EL master ................................................... 350 actuated rest in walk ........................................... 126
3CD............................................................. 180, 430 adaptive split ....................................................... 257
4 splits per cycle................................................. 487 add only............................................................... 243
4 splits per cycle mode ....................................... 238 added initial......................................................... 466
4 splits/cycle ............................................... 248, 262 added initial per actuation................................... 138
5900 series firmware .......................................... 380 adding
5-Section Illinois Left Turn Logic ..................... 466 menus .........................................17, 23, 374, 377
5-Section Right Turn Illinois Logic ................... 466 adj lt .................................................................... 187
8 phase quad left......................................... 103, 115 adj thru ........................................................187, 188
8216 series firmware .......................................... 380 adjusting
A port.......................................................... 438, 444 audio............................................................... 379
abbreviations phase allocation times.................................... 242
interval............................................................. 37 adjusting the interface........................................... 23
max and termination........................................ 37 ADV DEACT-DELAY ...................................... 205
absence ................................................................. 68 advance green enable.......................................... 208
absence failure...................................................... 22 advance green overlap ........................................ 207
absence monitoring ............................................ 174 advance warning ................................................... 64
absence of call .................................................... 175 advance warning logic ........................................ 202
absolute cycle time ............................................. 254 deactivation delay .......................................... 202
absolute sync ...................................................... 253 definitions ...................................................... 205
AC....................................................................... 503 enable ............................................................. 205
accessing the main menu...................................... 85 example.......................................................... 202
ACnn .................................................................. 414 setup procedure.............................................. 203

Index
advanced warning signals................................... 414 barriers ................................................................503

AFLS .................................................................. 414 basic operating modes.........................................270
AIA ..................................................................... 139 basic options .......................................................225
ak .......................................................................... 76 battery ...................................................................63
alarm signal ........................................................ 413 baud rate........................................................19, 350
all red dwell ........................................................ 319 beep volume ........................................................374
allowable gap...................................................... 462 BIU....................... 7, 10, 18, 22, 366, 397, 459, 503
ALMn ........................................... 51, 362, 365, 413 combining logic .............................................404
ALT A ................................................................. 413 definition ........................................................399
alternate flash ..................................................... 191 I/O mapping ...................................................404
alternate maximum timing ................................. 413 pin availability ...............................................415
alternate sequence phasing ................................. 156 rear pin layout ................................................399
alternate sequences ............................................. 413 BIU failure ............................................................35
alternate status screen........................................... 38 BIU failure help screen .........................................80
Amphenol ........................................................... 396 BIU I/O mapping ................................387, 411, 418
AND ................................................................... 409 BIU IO mapping .................................................197
answering.............................................................. 77 blank
APA ...................................................................... 41 input .................................................................61
APM ................................................................... 430 boot monitor........................................................382
arrow keys ............................................................ 15 buttons...................................................................14
as........................................................................... 76 C ............................................................................51
ASC .................................................................... 430 C port ..........................................................442, 444
assigning C/O/S to lead-lag ................................................489
central port..................................................... 348 C/O/S to TOD circuits ........................................489
master port..................................................... 348 C/S to time plan ..................................................263
monitor port................................................... 349 ca ...........................................................................76
assignments ........................................................ 164 CA .......................................................................503
associations CABF ..................................................................362
flash plan to interval...................................... 311 cabinet .................................................................503
assumptions ............................................................ 1 cabinet connectors.........................................8, 9, 10
AT commands .................................................... 358 cabinet door open................................................413
AT modem.......................................... 349, 352, 361 CABO .................................................................362
ATZ .................................................................... 358 call.........................................................................61
audio adjustment................................................. 379 manual preemption ........................................332
audio setup.......................................................... 374 call active ............................................................414
auto answer................................................. 355, 391 call mode.............................................................166
auto ped clear...................................................... 147 call only.................................................................21
Auto Ped Clear with MCE ................................. 466 call only detector.................................................467
auto perm ............................................................ 231 call to non-actuated.....................................129, 413
programming ................................................. 254 call,preemption ...................................................293
types............................................................... 229 call/extend .............................................................21
auto permissive mode......................................... 487 call/extend mode .................................................166
auto-answer ........................................................ 355 call-extend detector.............................................467
automatic flash ........................................... 414, 485 call-in priority .....................................................362
autoOFF................................................................ 13 calls
AUX ................................................................... 348 exit..................................................................307
aux port................................................................. 25 manual..............................................................30
auxiliary connector ..................................... 446, 460 Canadian fast flash..............................................191
AVE GRN ............................................................ 67 car detect .............................................................180
average flow ....................................................... 212 caret symbol ........................................................352
AWL ................................................................... 202 carrier detect........................................................355
AWLn ................................................................. 414 carryover operation .............................................201
B port .......................................................... 440, 444 caution symbol........................................................ 4
background cycle................................................ 487 CD .........................................................................76
backlight ............................................................... 13 CDD ....................................................................430
barrier ................................................................. 466 central modem.............................................354, 359

Index
central override........................................... 247, 387 CLR.............................................................226, 503

clearing a ......................................................... 29 cmd........................................................................ 79
central port.......................................................... 348 CNA90, 96, 129, 131, 136, 147, 247, 271, 467, 503
central system coordinated phase .......................................... 235
phone number to call..................................... 361 in coordinated phases....................................... 95
change data menu ................................................. 99 modes ............................................................... 91
channel assignment .............................................. 20 CNA modes........................................................... 93
channel assignmentsSee MMU: channel assignments CNAn ............................................................46, 413
check................................................................... 467 CNn ..................................................................... 430
CHECK ................................................................ 60 CNT..................................................................... 413
check coord plan................................................. 487 codes ..................................................................... 23
check coordination plan ............................. 265, 267 coordination source........................................ 224
checking firmware.................................................. 7 event call-in ................................................... 363
checksum error ..................................................... 28 flash................................................................ 188
checksum errors.................................................. 387 flash plan........................................................ 323
checksum failure .................................................. 35 I/O steering .................................................... 393
checksum latch ..................................................... 35 log enabling ................................................... 365
checksum status.................................................... 73 max and termination ........................................ 37
checksum values for firmware ........................... 381 output status bits .............................................. 44
circuit descriptions ............................................. 430 output steering ............................................... 393
circuit diagrams ...................................................... 2 override status.................................................. 35
circuit overrides.................................................. 286 pedestrian demand ........................................... 34
circuit plan............................................................ 96 security........................................................... 375
circuit plans special phone number chars........................... 361
configuring .................................................... 282 TS2 modes ..................................................... 203
circuit reset ......................................................... 280 vehicle and pedestrian demand........................ 36
circuits vehicle demand ................................................ 33
TOD circuits status.......................................... 58 COI...................................................................... 413
city zero ...................................................... 252, 253 colors..................................................................... 60
CKnn .................................................................. 414 combining inputs ................................................ 409
CKSF .................................................................. 362 example.......................................................... 408
clear BIU I/O map .............................................. 405 comm..................................................................... 78
clear key ............................................................... 14 comm connectors .......................................... 8, 9, 10
clear logs....................................................... 98, 418 comm copy.......................................................... 349
clear sequence .................................................... 102 comm ports ........................................................... 19
clearance comm setup .................................................346, 348
ped through yellow........................................ 310 comm transfer ..................................................... 350
cleared-to-send ................................................... 350 comms delay ....................................................... 350
clearing communication status screen ................................ 75
I/O mapping................................................... 407 communications
intersection name .......................................... 378 menu............................................................... 346
overrides .......................................................... 29 ports ............................................................... 459
preemption run .............................................. 295 communications setup ........................................ 391
clearing a checksum failure.................................. 73 compatibility
clearing BIU failures ............................................ 35 MMU ............................................................. 119
clearing coordination defaults............................ 223 computation of force-offs ................................... 235
clearing logs ....................................................... 420 conditional overlaps............................................ 205
clearing mistakes .................................................. 16 conditional ped............................................133, 468
clear-to-send ....................................................... 349 conditional service ......................................145, 468
CLMATS.............. 1, 2, 6, 18, 75, 76, 361, 428, 503 by time plan ................................................... 146
modem setup ......................................... 354, 359 conflicting co-phase....................................... 145
clock ..................................................................... 19 dual ring ......................................................... 145
clock reset time................................................... 289 example.......................................................... 145
closed loop............................................................ 57 condtional service
closed loop D module........................................... 25 circuit ............................................................. 145
closed loop ID ............................................ 346, 347 configuration

Index
I/O configurations ........................................... 24 basic options ..................................................225

sequence .......................................................... 20 basic procedure description .............................95
configuring check plan ......................................................265
advance warning logic................................... 203 connector........................................................448
BIU I/O mapping........................................... 404 copying...........................................................426
central modem ............................................... 359 cycles and offsets...........................................236
circuit overrides............................................. 286 defaults...........................................................223
circuit plans ................................................... 282 definition ........................................................503
communications ............................................ 348 display ..............................................................54
coordination plan............................................. 95 during cyclic preemption intervals ................317
date and time ................................................. 290 enhanced options ...........................................246
double clearing overlap ................................. 193 examples ........................................................269
Ethernet communications...................... 351, 353 general discussion..........................................212
exception days ............................................... 285 introduction......................................................23
I/O module....................................................... 49 overview.........................................................212
input mapping................................................ 408 pattern sources ...............................................224
intersection name........................................... 378 phase allocation .............................................240
modem ........................................................... 354 phase programming .......................................239
output mapping.............................................. 410 plan...................................................................95
passage time .................................................. 462 programming..................................................222
port 1.............................................................. 366 status screen .....................................................54
port 2.............................................................. 349 coordination functions screen ...............................62
port 3.............................................................. 351 coordination input signals...................................413
preemption entry ........................................... 303 coordination phases ............................................239
printing .......................................................... 423 coordination plan
week plans ..................................................... 283 checking .........................................................267
year plan ........................................................ 284 errors ..............................................................267
conflict monitor .............................. 26, 88, 119, 183 cophase group
connect reports modem speed ............................ 355 example ..........................................112, 113, 114
connected.............................................................. 77 co-phase groups ..................................................468
connector co-phases.............................................................104
A 438, 444 copmatibility check disable ................................367
AUX ...................................................... 446, 460 copy.....................................................................172
B 440, 444 copy functions.......................................98, 418, 425
C 442, 444 copying
coordination................................................... 448 database..........................................................425
modem ........................................................... 460 day plans ........................................................426
port 2.............................................................. 459 detectors .........................................................171
preemption..................................................... 447 I/O map to EEPROM.....................................412
SDLC............................................................. 459 I/O mapping from EEPROM.........................412
connectors........................................................... 392 mapping from an EEPROM ..........................405
contact name............................... 346, 370, 371, 372 mapping to an EEPROM ...............................405
controller conflict flash ........................................ 35 MMU channels ......................................405, 411
controller functions ............................................ 128 phases.............................................................425
Controller Functions........................................... 122 preemption runs .............................................427
controller menu................................................... 101 split plans .......................................................426
controller options................................................ 154 timing plans....................................................425
controller status screen ......................................... 30 corridors .................................................................. 6
converting flash controller to EPROM .............. 385 corrupt database detected......................................28
coord failure ....................................................... 487 corrupted database ................................................35
coord out of step ................................................. 488 COS.......................................................................91
coord port.............................................................. 25 COS to lead/lag ...................................................264
coord selection source ........................................ 224 COS/F .................................................................245
coordinated phases ............................................. 488 CPU.......................................................................20
coordination........................................................ 488 cr............................................................................76
actuated controllers ....................................... 217 CRC...............................................................28, 503

Index
CRDF.......................................................... 362, 365 database transfer ................................................. 420

creating date...................................................................... 290
coordination plan............................................. 95 day plan............................................................... 281
flash plans...................................................... 323 copying........................................................... 426
manual preemption call ................................. 332 editing ............................................................ 278
creating a NOT input.......................................... 409 erasing............................................................ 278
csv....................................................................... 146 example.......................................................... 280
CTC ............................................................ 430, 431 daylight savings time ....................................95, 287
CTS....................................................... 76, 349, 350 DCL....................................................................... 37
CU......................................................................... 26 DCMATS............................................................ 503
current................................................................... 63 DCP..................................................................... 430
24V supply ...................................................... 63 DDD.................................................................... 430
custom menus ..................................................... 377 DDE .................................................................... 430
customer support .................................................... 2 deactivating
customing BIU I/O mapping.............................. 404 I/O mapping ...........................................406, 407
CVM ................................................................... 159 default data
CVM signal .......................................................... 26 loading ........................................................... 419
CVS .................................................................... 430 preemption ..................................................... 295
cyc......................................................................... 30 default data load....................................98, 418, 419
CYC 1-6 ............................................................... 34 default NEMA mapping ..................................... 410
cyc timer ............................................................. 243 default setup.......................................................... 86
CYCF.......................................................... 362, 365 del........................................................................ 190
cycle............................................................ 212, 488 del enab ...............................................187, 190, 195
definition ....................................................... 213 delay....................................167, 169, 205, 292, 485
programming ................................................. 236 preempt .......................................................... 301
cycle fault ........................................................... 489 delay before preempt .......................................... 326
cycle inputs......................................................... 413 delay enable ........................................................ 187
cycle length................................................. 213, 236 delay inhibit ........................................................ 469
cycle outputs....................................................... 414 delay inhibits....................................................... 169
cycle source ........................................................ 224 delay overlap enable ...................................299, 300
cycle sync ........................................................... 252 delay preemption ................................................ 301
cycle/period ........................................................ 258 delay timer ..............................................48, 59, 326
cycles .................................................................. 236 delay tmr ............................................................... 61
cyclic interval ............................. 293, 311, 329, 498 deleting
cyclic intervals............................................ 300, 316 events ............................................................. 279
conflicting phases.......................................... 316 I/O mapping ................................................... 407
cyclic redundancy check ...................................... 28 menus .........................................17, 23, 374, 377
cycling failure............................................... 35, 131 preemption run............................................... 295
CYCn.......................................................... 413, 414 density ................................................................. 486
CYn..................................................................... 430 added initial ................................................... 138
D ........................................................................... 32 enables ........................................................... 151
input................................................................. 61 last car passage ......................................142, 151
D module ........................................ 8, 9, 10, 25, 366 maximum initial............................................. 138
12 phase......................................................... 449 minimum gap .........................................138, 142
closed loop..................................................... 446 overview......................................................... 139
coordination port ........................................... 448 time before reduction..................................... 137
Las Vegas ...................................................... 457 time to reduce ................................................ 137
LMD .............................................................. 452 viewing display................................................ 41
preemption connector.................................... 447 density status screen ............................................. 41
status screens ................................................... 52 DET MEM ............................................................ 60
Texas ............................................................. 454 detector
data bits............................................................... 350 assignment ..................................................... 164
database copy................................................................ 171
copy ............................................................... 425 delay inhibits.................................................. 169
printing .......................................................... 423 fail recall phase .............................................. 177
database corruption ...................................... 28, 387 failure monitoring .......................................... 174

Index
failures ............................................................. 22 outputs..............................................................43

general info...................................................... 21 preemption .......................................................59
loop length..................................................... 177 TOD circuits ....................................................58
modes............................................. 166, 168, 169 TOD status .......................................................57
call ............................................................ 166 DLL.....................................................................503
call/extend ................................................ 166 DM3 ....................................................................430
stop bar ..................................................... 167 DMD ...................................................................413
stretch/delay.............................................. 166 D-module ................................................................ 6
pedestrian detector diagnostics ..................... 178 D-module inputs .................................................413
status screen..................................................... 47 DNLD .................................................................362
switching ............................................... 171, 172 documents, other..................................................... 2
system sensor assignment ............................. 179 DOOR .................................................................413
times .............................................................. 169 double clear.........................................................202
Detector double clearance overlaps...................................470
Fail Recall Phase ........................................... 177 double clearing overlap.......................................193
detector copy ...................................................... 469 example ..................................................195, 196
detector failure log................................................ 68 in preemption .................................................299
detector failures release modifier..............................................194
printing .......................................................... 423 track clearance ...............................................196
detector lock ....................................................... 469 triggers ...........................................................194
detector lock mode ............................................. 168 double clearing overlap enable ...........................299
detector menu ..................................................... 164 double clearing overlaps .............................192, 303
detector pairs ...................................................... 180 Double Diamond.................................................349
detector switching............................................... 469 Double Diamond MMU......................................400
DETF .................................................................. 362 download request ................................................428
DHCP ................................................................. 353 DPn..............................................................430, 431
diagnostic menu.................................................... 81 drop .......................................................................78
diagnostics ............................................................ 81 DSD.....................................................................430
pedestrian detectors ....................................... 178 DSM ....................................................................430
diagnostics menu ................................................ 100 DSP modem ....................................................2, 350
diagram DST .....................................................................287
preemption fire run........................................ 333 DTR.......................................................................76
diagrams DTR high ..............................................................77
default sequences........................................... 107 DTR low................................................................77
fixed vs floating force-offs............................ 227 dual entry ............................................143, 144, 470
dialing ph# ............................................................ 77 dual indication.....................................................188
DIM .............................................................. 51, 430 dual ped control ..........................................147, 470
dimming........................................................ 21, 155 circuit .............................................................147
example ......................................................... 155 dual ring ......................................................103, 110
use with I/O mapping .................................... 405 dual yellows ........................................................188
direct connect ..................................................... 349 dual yellows prohibited.......................................466
dis adj key............................................................. 15 dummy phase ......................................................471
disabling duration time ...............................................301, 326
security .......................................................... 375 duration timer..........................................59, 60, 292
display............................................... 8, 9, 10, 12, 13 duration timer as gap timer .................................302
checksum status............................................... 73 dwell in ped clearance ........................................319
coordination functions..................................... 54 dwell in yellow....................................................319
D module I/O................................................... 52 dwell interval ......................................293, 310, 319
density.............................................................. 41 dwell red..............................................................318
detectors........................................................... 47 dwell seeking ......................................................243
diagnostics ....................................................... 81 dwell times ..........................................................238
I/O configuration ............................................. 49 DWK .....................................................................37
inputs ............................................................... 45 DWnn ..................................................................414
logs .................................................................. 66 dynamic controller display ...................................29
normal I/O ....................................................... 40 dynamic display ....................................................30
normal status.................................................... 30 dynamic display menu ..........................................99

Index
dynamic displays ............................................ 22, 39 entry control........................................................ 293

dynamic omit...................................................... 470 entry GRN........................................................... 327
dynamic omits .............................................. 22, 148 entry offset .......................................................... 225
dynamic recall .............................................. 22, 471 entry parameters.................................................. 303
dynamic recalls........................................... 144, 149 entry times........................................................... 303
E EP........................................................................ 503
input................................................................. 61 EPn...................................................................... 430
early PE out ................................................ 297, 298 EPP...................................................................... 503
early release........................................................ 262 EPROM................................................................. 10
echo..................................................................... 355 burner ............................................................. 386
editing specs............................................................... 386
enabled phases................................................. 89 EPROM chip....................................................... 382
flash plans...................................................... 323 EPROM chips .............................................380, 384
intersection name .......................................... 378 EPROM diagnostics ............................................. 81
modem string................................................. 357 EPROM failure ..................................................... 35
output mapping.............................................. 410 EPROM firmware
phase recall modes .......................................... 90 converting to flash memory........................... 385
phase times ...................................................... 94 EPROM memory chips....................................... 388
preemption run .............................................. 296 equations
recalls............................................................... 93 single permissives.......................................... 232
startup phases .................................................. 88 erasing
timing plan recall modes ................................. 91 day plan.......................................................... 278
EDP............................................................. 147, 430 preemption ..................................................... 295
EEPROM...................................... 74, 374, 379, 503 erratic counts....................................................... 176
failure............................................................... 35 erratic detector ...................................................... 68
Module............................................................. 19 erratic failure......................................................... 22
RAM copy ..................................................... 421 error
EEPROM copy............................................. 98, 418 startup............................................................... 28
EGB .................................................... 249, 250, 503 error correction ...........................................355, 391
EIA-232 .......................................... 17, 24, 348, 459 establishing BIU link ............................................ 35
electrical status ..................................................... 63 Ethernet .........................................6, 7, 17, 351, 353
ELRA.................................................................. 349 card................................................................... 18
ELRB.................................................................. 349 event call in......................................................... 346
email ....................................................................... 2 event call-in......................................................... 362
EML.................................................................... 430 event log........................................................69, 348
enable printing........................................................... 423
security ............................................................ 17 event times .......................................................... 279
enable coord during cyclic intervals .......... 299, 300 events
enable source selection....................................... 119 deleting........................................................... 279
enabled phases...................................................... 89 EVL..................................................................... 430
enabling evolution of 3000 controllers.................................. 6
coordination during preemption.................... 300 EX STRT .............................................................. 46
leading overlaps in preemption ..................... 300 example
preemption run .............................................. 297 preemption ..................................................... 333
end key ................................................................. 15 examples
end of main street ....................................... 225, 490 output steering ............................................... 394
end permissive point .......................................... 490 exception days .................................................... 285
enhanced controller options ............................... 148 excessive inductance change failure..................... 68
enhanced coordination ....................................... 246 exclusive ped.......................................104, 320, 471
enhanced ped ...................................................... 147 exclusive pedestrian............................................ 117
enhanced ped operation...................................... 471 Exclusive Pedestrian........................................... 117
enhanced perm.................................................... 247 exclusive pedestrian operation ........................... 413
enhanced permissive .......................................... 490 exit calls .............................................................. 307
enhanced sequence configuration ...................... 104 exit interval ......................................................... 294
enter key ............................................................... 14 exit modes ........................................................... 306
ENTRY................................................................. 67 exit parameters............................................306, 319

Index
exit phase ............................................................ 306 fixed force offs....................................................490

exit phases .......................................................... 151 fixed force-off .............................................226, 228
exit to coordination............................................. 306 fixed interval .......................................293, 310, 317
extend timer .......................................................... 61 fixed intervals .....................................................305
extended green band................................... 249, 489 fixed intervals before preemption exit................319
extended result code ........................................... 355 fixed IP................................................................353
external start ................................................. 35, 413 fixed red before dwell red...........................315, 318
external voltage .................................................... 63 fixed red interval.................................................318
EXTS .................................................................. 413 fixed red intervals in preemption........................318
F fixed yellow interal .............................................318
input................................................................. 61 fl code..................................................................195
FAIL ..................................................................... 32 fl enab..................................................186, 189, 195
fail max recall time............................................. 177 fl walk ...................................................................93
fail max time................................................. 61, 302 flash
fail timer in seconds ............................................. 61 failures..............................................................36
failed detector phase........................................... 177 FLASH ................................................................413
failure monitoring............................................... 174 flash code ............................................................189
fast flash.............................................................. 191 flash exit error .......................................................35
fault status indicators............................................ 34 flash memory controllers ......................................10
faults flash memory enabled.................380, 382, 383, 388
MMU fault log ................................................ 72 converting to EPROM ...................................385
fax number.............................................................. 2 flash override ......................................................298
FDW ................................................................... 133 flash parent..........................................................189
fdw->red ............................................................... 93 flash plan.....................................294, 296, 311, 323
fdw->yel ............................................................... 93 flash red WIG/WAG...........................................159
field modem........................................................ 354 flash source .........................................................224
figures flash status inputs................................................413
table of ............................................................. xii flash yellow WIG/WAG .....................................159
filtering input........................................................ 20 flashing walk.......................................................132
fimrware floating force offs................................................491
upgrade .......................................................... 386 floating force-off.........................................226, 228
fire run ................................................................ 324 flow control.........................................................355
fire run interval................................................... 328 FO..................................................................60, 503
firewall................................................................ 353 FOFF ...................................................................413
firmware ........................................................... 7, 12 FOM ....................................................................503
binary files..................................................... 386 FORC OFF............................................................46
checking version................................................ 7 force off...............................................125, 217, 472
checksum values............................................ 381 FORCE TERM .....................................................37
chip location .................................................. 384 force-off ..............................................................226
flavor.............................................................. 380 definition ........................................................235
history ................................................................ 6 formula...........................................................226
installation methods....................................... 380 load manual....................................................257
updating the ................................................... 380 force-off ring input function ...............................413
upgrade cable................................................. 383 force-off to first interval .............................299, 300
upgrade utility................................................ 382 forms
firmware release notes............................................ 2 preemption .....................................................434
firmware revision ................................................. 65 preemption programming ..............................321
firmware update...................................................... 7 formula
firmware upgrade multiple permissive........................................233
via EPROM chips.......................................... 384 four splits/cycle...................................................248
firmware upgrade utility..................................... 383 FR..........................................................................51
firmware version................................................... 12 FRE .............................................................430, 431
first interval ........................................................ 292 FREE...........................................................413, 414
first time setup ................................................ 84, 86 free circuit .....................................................96, 281
menu .............................................................. 100 free input .............................................................413
first time setup menus .......................................... 97 free mode ............................................................491

Index
free output........................................................... 414 hold rest............................................................... 473

free source .......................................................... 224 home key............................................................... 14
FRO ............................................................ 430, 431 hours of operation ................................................... 2
FSK............................................................... 17, 503 HPRE ..........................................................362, 365
FSK TDM............................................................. 20 HRST .................................................................... 37
fully actuated coordination................................. 491 Hz........................................................................ 503
fuses.............................................................. 8, 9, 10 I/O board ............................................................... 64
G ........................................................................... 32 I/O codes ............................................................. 400
gap ...................................................................... 138 I/O configuration status screen ............................. 49
simultaneous.................................................. 152 I/O failure.............................................................. 35
gap out ........................................................ 228, 472 I/O mapping .................................................... 7, 404
gap reduction ...................................................... 141 abbreviations.................................................. 413
last car passage .............................................. 142 activating/deactivating................................... 406
gap reduction diagram........................................ 142 I/O mapping codes......................................400, 404
GAP TERM.......................................................... 37 I/O mode 7 ............................................................ 53
gap time .............................................................. 326 I/O mode error ...................................................... 36
gap timer............................................................. 302 I/O module configuration ..................................... 49
getting help ............................................................. 2 I/O steering ...................................................22, 392
glossary............................................................... 465 IADV................................................................... 413
go to exit phases ................................................. 306 ID ........................................................................ 347
go to higher PE........................................... 297, 298 Illinois left turn configuration ............................ 187
go to next demand .............................................. 306 Illinois right turn configuration .......................... 187
going to a higher preemption run....................... 298 Illinois right turn logic........................................ 189
GR2..................................................................... 430 immediate call-in ................................................ 362
green band .......................................................... 249 IMn...................................................................... 430
green prep interval.............................................. 472 inbound ............................................................... 212
green rest ............................................................ 130 include all............................................................ 189
green rest interval ............................................... 473 in-cycle falsh....................................................... 191
greenband analysis ............................................. 503 IND CTL............................................................... 46
GRN REST........................................................... 34 INDIC ............................................................. 30, 32
GRN UTL % ........................................................ 67 inh max ...................................................93, 96, 131
GRnn .................................................................. 414 INH MAX ............................................................. 46
group address...................................................... 372 inhibit double clearing overlaps ......................... 303
group next........................................................... 194 inhibit max ..................................................130, 431
group yellow....................................................... 194 inhibit max termination ...................................... 473
grp nxt......................................................... 194, 208 inhibiting
grp yel................................................................. 194 overlaps.......................................................... 209
GRP2 .................................................................. 413 INHM.................................................................. 413
GRST.................................................................... 37 INIT.........................................................37, 41, 503
H ..................................................................... 33, 36 initial ..................................................................... 94
hardware ......................................... 8, 349, 351, 353 initial timer.......................................................... 474
diagnostics....................................................... 81 initialization interval............................................. 88
HDLC initialization phase ................................................ 88
group address................................................. 372 initialization string ......................................352, 357
HDLC address ............................ 346, 370, 371, 372 initializing ............................................................. 77
HDnn .................................................................. 413 input ...................................................................... 61
headway................................................................ 67 input diagnostics ................................................... 81
help ......................................................................... 2 input filtering ........................................................ 20
help key ................................................................ 15 input lock ....................................................297, 326
high regulated voltage .......................................... 63 input/output availability...................................... 415
history ..................................................................... 6 inputs status screen ............................................... 45
synchronization ............................................. 216 installing
HOL................................................................ 78, 79 firmware upgrade........................................... 380
hold ............................................... 60, 217, 413, 473 new firmware ................................................. 386
HOLD ................................................................... 46 INT ADV .............................................................. 46
hold only..................................................... 297, 299 inter tod revert..................................................... 224

Index
internal voltage ..................................................... 63 LCD.......................................................................13

Internet address....................................................... 2 LCP .................................................37, 41, 142, 151
interrupter ............................................................. 57 LDLF...................................................................413
interrupter mode ................................................. 289 lead overlap enable .....................................299, 300
intersection ......................................................... 503 lead/lag ................................................................264
intersection label................................................... 65 activation inputs.............................................157
intersection name........................................ 374, 378 flag .................................................................156
interval.................................................. 60, 293, 503 mode...............................................................158
controls .......................................................... 305 multiple ..........................................................158
ped clearance ................................................. 136 pattern ............................................................157
yellow clearance ............................................ 135 phase concurrency .........................................157
interval abbreviations ........................................... 37 phasing ...........................................................156
interval advance.................................. 125, 413, 474 selection by input ...........................................157
interval data ................................................ 296, 308 lead/lag operation..................................................21
interval timer ........................................................ 60 leading overlap....................................................207
intervals advance green enable.....................................208
editing .............................................................. 88 enable .............................................................208
introduction ............................................................ 6 green time ......................................................207
invert free in ....................................................... 247 grp nxt ............................................................208
IO steering .......................................................... 197 inpreemption ..................................................300
IP address............................................................ 353 ph nxt .............................................................208
IPM ............................................................. 249, 430 lead-lag........................................................115, 474
IQ Central ............................................................... 7 LFL........................................................................51
IQ Connect.............................................................. 7 LFSH...................................................................365
ITMR .................................................................... 41 library of sequences ............................................104
ITS ...................................................................... 503 links.....................................................................385
jumpers ............................................................... 385 LLn......................................................................430
K LLP......................................................................156
input................................................................. 61 LMD D module.............................................25, 452
KBLD ................................................................. 362 LMD series controllers .........................................19
key load manual force-off .........................................257
comm status screen.......................................... 76 load manual permissives.....................................256
common TS2 modes...................................... 203 load switch ..........................................................183
coordination status screen ......................... 56, 58 loading
density screen .................................................. 41 coordination defaults .....................................223
I/O configuration status screen ....................... 51 default data.....................................................419
inputs status screen.......................................... 46 default preemption data .................................295
MOE logs screen ............................................. 67 sequence info .................................................103
normal I/O screen ............................................ 40 loading a default NEMA mapping......................410
outputs status screen........................................ 43 loading a default setup ..........................................86
preemption run duration screens ..................... 60 loading NEMA map............................................405
voltage status screen........................................ 63 local.....................................................................503
keyboard conventions............................................. 3 local cycle ...........................................................213
keyboard diagnostics ............................................ 81 local cycle reference point ..................................213
keyboard log ......................................................... 71 local cycle timer..................................................492
printing .......................................................... 423 local cycle zero ...................................................225
keyboard shortcuts................................................ 30 LOCAL CYCLE/SPLIT .......................................54
keypad......................................... 8, 9, 10, 12, 14, 16 local flash status..................................................413
Las Vegas D module .................................... 25, 457 local offset.............................................................54
last car passage ................................... 141, 142, 151 local split modes .................................................257
Last Car Passage................................................. 151 local zero .............................................................492
last cmd rx ............................................................ 78 location of firmware chips ..................................384
last cmd tx............................................................. 78 lock times ............................................................175
last phases........................................................... 151 locked detector......................................................68
LBAT.................................................................. 365 locked failure ........................................................22
lc ........................................................................... 76 log

Index
enable codes .................................................. 365 MAX 3 .................................................................. 94

log data ....................................................... 346, 364 definition........................................................ 153
log menu ............................................................... 66 options............................................................ 153
logical operators ......................................... 408, 409 MAX 3 ADJ.......................................................... 94
logo max 3 adjust ........................................................ 137
flash memory enabled ..................................... 11 max 3 limit .......................................................... 137
logs Max 3 mode ........................................................ 475
clearing .......................................................... 420 max and termination abbreviations ...................... 37
detector failure................................................. 68 max dwell............................................................ 236
event ................................................................ 69 max dwell times .................................................. 238
keyboard .......................................................... 71 MAX GRN............................................................ 67
MMU fault log ................................................ 72 max II ..............................................90, 96, 131, 137
pattern change ................................................. 71 Max II ................................................................... 92
printing .................................................. 423, 424 MAX II .........................................................46, 126
viewing ............................................................ 66 max interval ........................................................ 331
volume ............................................................. 68 max intervals...............................................297, 298
loop length.......................................................... 177 max recall......................................................90, 124
lp ........................................................................... 76 circuits............................................................ 124
LPM modem Max recall ............................................................. 92
as central system modem .............................. 359 MAX TERM ......................................................... 37
LPM336 field modem ........................................ 354 max time ............................................................. 228
LPRE .................................................................. 365 max timing inhibit............................................... 413
lr............................................................................ 76 max variable initial ............................................. 140
lt76 MAX2 ................................................................. 413
M............................................................... 33, 34, 36 maximum dwell time .......................................... 492
input................................................................. 61 maximum green timer with max recall off......... 475
M ADV TERM..................................................... 37 maximum initial..........................................138, 475
M2n..................................................................... 430 mb ......................................................................... 76
M3000 .......................................................... 75, 503 mc.......................................................................... 76
ma ......................................................................... 76 MCE........................35, 46, 147, 362, 413, 474, 503
main menu ............................................................ 98 me.......................................................................... 76
accessing.......................................................... 85 memory .......................................................125, 331
Main menu.............................................................. 7 memory management ......................................... 421
manual control enable ........................................ 147 menu
Manual Control Enable ...................................... 466 adding and deleting........................................ 377
manual control enabled ...................................... 413 change data ...................................................... 99
manual force-off................................................. 257 comm and system setup................................. 346
manual overrides ................................................ 286 controller........................................................ 101
manual ped calls ................................................... 38 customizing.................................................... 377
manual permissive and force off........................ 492 detector........................................................... 164
manual preemption calls .................................... 332 diagnostics ..................................................... 100
map codes ........................................................... 404 dynamic display ............................................... 99
mask.................................................................... 353 first time setup ............................................... 100
master controller................................................. 347 main .........................................................98, 101
master cycle................................................ 213, 214 MMU ............................................................. 100
MASTER cycle counter ....................................... 54 read data........................................................... 99
master cycle timer .............................................. 492 restricting access............................................ 376
master identification number ............................. 347 transfer ........................................................... 420
master polling timer ............................................. 75 unit configuration .......................................... 374
master port.......................................................... 348 utilities ........................................................... 418
matrix,split.......................................................... 261 menu 2 recall modes ........................................... 128
MATS ................................................................... 76 menu key............................................................... 15
max ............................................................. 125, 195 menu number key .......................................376, 377
MAX 1.......................................................... 94, 136 menus
MAX 2.................................................................. 94 adding and deleting.......................................... 17
Max 3.................................................................... 21 Adding, deleting ............................................ 377

Index
restoring access ..................................... 376, 377 mode 9.................................................................189

restricting access ........................................... 374 MODE n................................................................46
mf.......................................................................... 76 modem.................................................................350
MGAP................................................................... 41 connector........................................................460
MIB tree.............................................. 370, 371, 372 fiber optic.........................................................17
midnight.............................................................. 280 LPM336 .........................................................354
milspec................................................................ 396 manufacturers.................................................356
min ...................................................................... 195 requirements...................................................355
MIN .................................................................... 430 setup string.....................................................391
min force-offs ..................................................... 258 unused parameter .............................................77
min gap ............................................................... 141 modem configuration..........................................354
MIN GAP ........................................................... 151 modem seetup
min green ...................................................... 90, 136 example ..........................................................357
min recall .............................................. 90, 123, 476 modem setup
all phases ....................................................... 413 troubleshooting ..............................................358
Min recall.............................................................. 92 modem status messages ........................................77
min red revert ..................................................... 482 modem string ..............................................352, 355
min walk ............................................................. 189 LPM336 .........................................................354
minimum cycle length................................ 238, 492 sending to controller’s modem ......................357
minimum gap.............................................. 138, 476 modem type...........................................................76
minimum presence ....................................... 68, 176 MOE..............................................................66, 504
minimum presence failure.................................... 22 log ..................................................................364
minimum red revert ............................................ 154 MOE log
MINR.................................................................. 413 printing...........................................................423
Mizbat................................................................... 75 MOE logs ..............................................................66
Mizbat dynamic status screen .............................. 75 MONF .........................................................362, 365
MIZBAT protocol manual ................................... 29 monitor port ........................................................349
mm ............................................................ 30, 32, 76 motherboard ........................................................385
MMU18, 20, 24, 26, 51, 88, 161, 183, 349, 397, 400, moving the cursor .................................................16
504 MPM ...................................................................430
channel assignments.............................. 366, 369 mr ..........................................................................76
channel incompatibility ................................... 80 MRn ....................................................................430
compatibility.................................................. 119 MSA ....................................................................366
failure............................................................... 35 MS-A port ...................................................438, 444
flash help screen .............................................. 80 MS-B port ...................................................440, 444
menu .............................................................. 100 MS-C port ...................................................442, 444
programming card ......................................... 400 MSCLR ...............................................................504
status screen..................................................... 82 mt ..........................................................................76
MMU channels ................................................... 411 multi offsets ........................................................264
MMU enable....................................................... 367 multiple lead/lag .................................................158
MMU fault log...................................................... 72 multiple permissive.............................................492
MMU flash ........................................................... 35 example ..........................................................234
MMU flash status ............................................... 413 formulae .........................................................233
MMU log retrieval ............................................... 17 multiple permissives ...........................................233
MMUF................................................ 362, 365, 413 multiple timing plan operation ...........................147
Mnn..................................................................... 430 MVI.............................................................139, 140
mod phs .............................................. 186, 188, 195 MX1 ......................................................................37
mode 0 ........................................................ 166, 188 MX1+....................................................................37
mode 1 ........................................................ 166, 188 MX2 ......................................................................37
mode 2 ........................................................ 166, 188 MXIN ....................................................................41
mode 3 ........................................................ 167, 188 MXn ......................................................................41
mode 4 ................................................................ 188 N............................................................................32
mode 5 ................................................................ 188 N/U......................................................................430
mode 6 ................................................................ 189 name
mode 7 .................................................. 53, 189, 366 intersection.....................................................378
mode 8 ................................................................ 189 naming an intersection........................................378

Index
NAND ................................................................ 409 Offset

navigating status screens ...................................... 31 Reference ....................................................... 225
NEMA .................................................................. 53 offset entry in percent ......................................... 225
definition ....................................................... 504 offset inputs......................................................... 413
NEMA 1992 ......................................................... 20 offset intersection................................................ 195
NEMA controllers ................................................ 19 offset outputs ...................................................... 414
NEMA map ........................................................ 405 offset seeking ..............................................216, 494
NEMA mapping ................................................. 410 add only.......................................................... 243
NEMA priority ........................................... 297, 298 dwell............................................................... 243
NEMA TS1........................................................... 24 overview......................................................... 243
NEMA TS2 Type 1 .............................................. 24 short route ...................................................... 244
NEMA TS2 type 2................................................ 24 offset source........................................................ 224
next output.......................................................... 414 offset time ........................................................... 236
nk .......................................................................... 76 offset to free ........................................................ 264
no early coordinated phase ped.......................... 493 OFn ..................................................................... 430
no early release........................................... 262, 493 ofs.......................................................................... 30
no fault flash....................................................... 161 OFST..................................................................... 34
no offset line....................................................... 264 Oklahoma 5-Section Single Indication Left Turn
NO PCL .............................................................. 271 Logic................................................................. 477
No PCL offset ADJ ............................................ 247 Oklahoma left turn logic..................................... 188
no ped clearance offset adjust ............................ 493 ol ........................................................................... 76
no skip ........................................................ 127, 477 OL card enable.................................................... 191
No skip ................................................................. 93 OL type ............................................................... 195
node .................................................................... 371 OLa ..................................................................... 430
non-lock...................................................... 125, 477 om ......................................................................... 76
Non-Lock.............................................................. 92 omit ....................................................................... 61
NOR.................................................................... 409 omit all last portion of delay............................... 301
normal I/O status screen....................................... 40 omit red clearance.......................................413, 478
normal operating status ........................................ 34 omits
normal status ........................................................ 73 dynamic....................................................22, 148
NOT.................................................................... 409 status ................................................................ 45
not ped ................................................................ 186 OMITS .................................................................. 40
not ped overlap ................................................... 477 ON signal ............................................................ 414
note symbol ............................................................ 4 ON/NEXT....................................................... 43, 60
NTCIP .................................... 6, 370, 371, 372, 396 ON/NX.................................................................. 40
comm parameters .............................................. 7 on-line ................................................................... 32
release notes ...................................................... 2 Onn...................................................................... 430
number keys ......................................................... 14 ONnn................................................................... 414
number of cycles to out of step .......................... 493 open loop failure ................................................... 68
NVRAM ..................................................... 355, 358 optical input signals ............................................ 413
NXnn .................................................................. 414 optional modules................................................... 25
O ............................................................... 33, 36, 51 OPTn ................................................................... 413
O/L........................................................................ 32 Optocom.............................................................. 448
O/L type.............................................................. 186 opto-I................................................................... 448
O/L YEL............................................................. 327 OR ....................................................................... 409
oc .......................................................................... 76 ORCL.................................................................. 413
occupancy............................................................. 67 ORn ..................................................................... 430
occupancy log....................................................... 68 os ........................................................................... 76
OFFn........................................................... 413, 414 outbound ............................................................. 212
offset ................................................... 212, 261, 494 output diagnostics ................................................. 81
adjusting in the field...................................... 237 output mapping ...........................................405, 410
definition ....................................................... 215 output mapping abbreviations ............................ 414
multi............................................................... 264 output steering
programmed .................................................... 55 overlaps.......................................................... 394
programming ................................................. 236 outputs
reference ........................................................ 225 preempt .......................................................... 314

Index
outputs status screen............................................. 43 P MEMORY .........................................................40

overlap ........................................................ 182, 478 P omit ....................................................................61
advance green ................................................ 207 P OUTPUT............................................................40
assignments ................................................... 185 PA........................................................................504
card ................................................................ 183 page .......................................................................78
card display...................................................... 64 parent phase ........................................185, 192, 208
card enable..................................................... 191 parent phases.......................................................182
channels ......................................................... 183 parents .................................................................186
conditional double clearing ........................... 192 parity ...................................................................350
delay .............................................................. 187 part numbers ........................................................... 2
in preemption............................................ 300 PASS ...............................................................37, 41
delay time ...................................................... 190 passage ..........................................................94, 135
double clearing ...................................... 192, 193 passage sequential...............................................154
example ................................................. 116, 182 passage sequential timing ...................................478
five section head............................................ 188 passage timer.......................................125, 302, 478
flash during parent......................................... 190 passage timing.....................................................462
green, yellow, red timings............................. 190 patt.......................................................................158
in preemption................................................. 300 pattern change
include all ...................................................... 189 log ..................................................................423
inhibiting ....................................................... 209 pattern change log.................................................71
leading ........................................................... 207 pattern screens.....................................................172
modes............................................................. 186 PCL ...............................................................37, 133
modifiers........................................................ 187 PCL-YEL ............................................................327
not ped ........................................................... 188 PCnn............................................................414, 430
not vehicle ..................................................... 188 PDnn ...................................................................413
parent phase................................................... 185 PE ..........................................................51, 293, 504
pedestrian....................................................... 197 PE flash ...............................................................314
programming ................................................. 185 PE input lock.......................................................297
release modifier ............................................. 194 PE out..................................................................314
standard ......................................................... 185 ped.......................................................................504
start-up........................................................... 191 ped call ................................................................307
type 5 ............................................................. 187 PED CALL............................................................46
type 6 ............................................................. 187 ped call during startup phase ................................88
type modes..................................................... 188 ped calls
types............................................................... 185 manual..............................................................38
Overlap ped clearance.......................124, 130, 136, 147, 197
Double Clearing ............................................ 192 auto with MCE...............................................147
overlap card .......................................................... 64 dwell...............................................................319
overlap card error ................................................. 35 ped clearance through red...................................132
overlap indicators ........................................... 30, 32 ped clearance through yellow .....................132, 310
overlap inhibit circuits........................................ 209 ped clearance thru red .........................................479
overlaps ped clearance thru yellow ...................................479
double clearing .............................................. 303 ped clearance timer .............................................479
in output steering........................................... 394 PED CLR ......................................................94, 504
override................................................................. 75 ped compatibility ................................................199
central ............................................................ 387 vs ped overlap ................................................199
override clearance................................................. 29 ped flash ..............................................................311
override flash ...................................................... 297 ped head ................................................................60
override status indicators...................................... 35 PED HEAD.....................................................43, 60
override UCF ...................................................... 298 ped omit ......................................................126, 479
override/fault status indicators ............................. 34 Ped Omit ...............................................................92
overrides ............................................................... 76 PED OMIT............................................................46
ownership ............................................................... 7 ped options ....................................................93, 147
P33, 36 ped overlap
P call ..................................................................... 61 carryover ........................................................201
P demand ........................................................ 30, 34 example ..........................................................200

Index
mode logic ..................................................... 199 pgdn key................................................................ 15

modes............................................................. 198 pgup key................................................................ 15
parent phases ................................................. 198 ph nxt ..................................................194, 196, 207
vs ped compatibility ...................................... 199 ph yel...........................................................194, 196
ped overlaps................................................ 197, 479 PH/OL ............................................................. 30, 32
ped override PH2 ..................................................................... 430
circuit............................................................. 249 phase ................................................................... 480
ped override mode.............................................. 494 copying........................................................... 425
Ped Override Mode ............................................ 249 definition........................................................ 504
ped perm ............................................................. 255 exit ................................................................. 306
ped permissive.................................................... 495 next................................................................. 476
ped recall ............................................ 124, 195, 480 on 478
Ped recall .............................................................. 92 reversal........................................................... 156
ped recy ................................................................ 93 phase allocation ..........................................272, 495
PED RECY........................................................... 46 by percentage ................................................. 225
ped recycle.................................................. 131, 480 phase allocations................................................. 240
ped recylce.......................................................... 413 phase enable........................................................ 190
ped service in the actuated mode ....................... 480 phase flash........................................................... 311
ped service in the call-to-non-actuated (CNA) mode phase indicators .................................................... 32
.......................................................................... 480 phase modifiers ................................................... 188
pedestrian phase next ........................................................... 194
exclusive........................................................ 117 phase omit ........................................................... 486
pedestrian calls ..................................................... 30 phase recall
pedestrian clearance signals ............................... 414 timing plan assignable ................................... 123
pedestrian demand codes................................ 34, 36 phase recall modes................................................ 90
pedestrian don’t walk signals ............................. 414 phase recalls..................................................91, 122
pedestrian omits.................................................. 413 Phase Recalls ...................................................... 122
pedestrian overlap clearance signals .................. 414 phase reversal...................................................... 156
pedestrian overlap don’t walk signals................ 414 phase reversals .................................................... 413
pedestrian overlap walk signals ......................... 414 phase timers .......................................................... 34
pedestrian walk signals ...................................... 414 phase times............................................94, 133, 134
PEDR.................................................................. 413 phase yellow ....................................................... 194
Peek modem ....................................................... 354 phase/overlap indicators ....................................... 32
Peek Traffic ........................................................ 2, 7 phases
per run data......................................................... 296 coordinated .................................................... 239
per run parameters.............................................. 297 enabled ............................................................. 89
per unit recall modes .......................................... 128 PHD....................................................................... 37
permission phone numbers........................................2, 346, 361
multiple.......................................................... 270 special characters ........................................... 361
single ............................................................. 270 special characters ........................................... 361
yield ............................................................... 270 physical address .................................................. 372
permissive........................................................... 217 pin assignment
computation ................................................... 235 CVM signal...................................................... 26
definition ............................................... 229, 235 pin assignments
enhanced........................................................ 231 BIU................................................................. 400
enhanced........................................................ 247 pin connections ................................................... 396
manual ........................................................... 256 placing
multiple.......................................................... 233 ped calls ........................................................... 30
pedestrian ...................................................... 254 placing a manual preemption call....................... 332
pedestrian ...................................................... 255 plan
single ............................................................. 231 split................................................................. 213
type ................................................................ 229 plan in effect ......................................................... 67
yield ............................................................... 230 plus symbol ........................................................... 69
Permissive Pnn ...................................................................... 430
Pedestrian ...................................................... 255 POCA.................................................................. 414
permissive period ............................................... 495 Pocket Central..................................................... 383

Index
Pocket Central software ..................................... 388 D module port ................................................447

Pocket PC default values .................................................295
firmware upgrade utility........................ 382, 383 definitions ......................................................293
PODA ................................................................. 414 delay...............................................292, 299, 301
pol head ................................................................ 60 delay overlap enable ......................................300
POL HEAD .................................................... 43, 60 demand...........................................................293
POM ................................................................... 430 double clearing overlap..................................299
POn ..................................................................... 430 duration ..........................................................301
POnn ................................................................... 413 duration timer.................................................292
port duration timer as gap timer............................302
configurations............................................ 17, 18 dwell in ped clearance ...................................319
port 1....................................... 17, 24, 157, 444, 459 dwell in yellow...............................................319
setup....................................... 366, 370, 371, 372 early output ....................................................298
Port 1 .................................................................... 10 enable coord during cyclic intervals..............300
soft flash ........................................................ 161 entry control...................................................293
port 2............................................... 17, 24, 350, 459 entry parameters.............................................303
configuration ................................................. 349 entry walk ......................................................304
installing firmware via .................................. 380 erasing ............................................................295
status ................................................................ 76 examples ........................................................333
to port 3 transfer ............................................ 347 exit parameters...............................................306
Port 2 .................................................................... 18 fail max time ..................................................302
port 3............................. 17, 350, 351, 353, 459, 460 fixed intervals upon exit ................................319
status ................................................................ 76 fixed red before dwell red......................315, 318
to port 2 transfer ............................................ 347 fixed yellow and fixed red intervals ..............318
Port 3 ............................................................ 18, 349 flash override .................................................298
port A.......................................................... 438, 444 flash plan........................................................323
port B .......................................................... 440, 444 force-off to first interval ........................299, 300
port C .......................................................... 442, 444 forms ..............................................................321
port fail error ........................................................ 36 going to a higher run......................................298
port number ........................................................ 353 hold only ........................................................299
port type...................................................... 348, 349 input ...............................................................293
ports ...................................................................... 19 input lock .......................................................297
POST .................................................................. 387 interval controls .............................................305
power supply .................................................. 19, 63 interval data....................................................308
power-on self test ......................................... 28, 387 interval table ..................................................321
pr........................................................................... 76 leading overlap...............................................299
PRE CALL ........................................................... 60 leading overlap enable ...................................300
preempt ............................................................... 293 max intervals..................................................298
preempt delay ..................................................... 301 NEMA priority...............................................298
preempt input signals ......................................... 413 omit all last portion of delay..........................301
preempt override................................................. 154 outputs............................................................314
preempt status....................................................... 61 overlap....................................................299, 300
preemption............................................................ 22 overlaps within cyclic intervals .....................316
all red dwell ................................................... 319 overview.........................................................292
applying exclusive PED ................................ 320 PE out.............................................................314
assigning flash plans...................................... 314 priority............................................................292
basic operation............................................... 292 programming..................................................295
call ................................................................. 293 examples ...................................................333
clearing all runs ............................................. 295 flash plans .................................................323
configuration ................................................... 96 forms .................................................321, 434
consecutive fixed red intervals...................... 318 quick setup .....................................................324
coordination................................................... 299 railroad ...................................................297, 336
coordination during cyclic intervals.............. 317 red revert override..........................................303
copying .......................................................... 427 reservice .........................................................301
cyclic interval ................................................ 315 reservice time.................................................301
cyclic intervals............................................... 300 run ..................................................................293

Index
run enable ...................................................... 297 preemption run............................................... 296

run invalid ..................................................... 322 Quixote Traffic ....................................................... 7
service control ............................................... 293 r 32, 33, 36
startup ............................................................ 300 R ..........................................................32, 33, 34, 36
use interval data for overlaps ................ 299, 300 input ................................................................. 61
user priority ................................................... 299 radio-modem delay .....................................349, 350
viewing operation............................................ 59 railroad ........................................297, 324, 329, 336
Preemption RAM ................................................................... 504
Error Checking .............................................. 322 copying to EEPROM ..................................... 421
Programming RAM diagnostics .................................................. 81
Operating Mode ....................................... 297 RAM failure.......................................................... 36
preemption flash................................................. 161 rc ........................................................................... 76
preemption functions screen ................................ 62 RCL ALL.............................................................. 46
preemption outputs............................................. 414 RDnn ................................................................... 414
preemption port .................................................... 25 read data menu ...................................................... 99
preemption run read only ............................................................. 375
editing............................................................ 296 ready-to-send ...................................................... 349
preemption status screen ...................................... 59 real-time clock reset............................................ 413
prefault.................................................................. 36 reboot .................................................................. 422
PREP .................................................................... 37 recall..............................................................79, 481
prepare to stop .................................................... 202 dynamic............................................................ 22
primary status screen............................................ 30 max................................................................. 124
PRIn.................................................................... 413 recall modes .......................................................... 90
printer per unit assignable ......................................... 128
print options................................................... 424 timing plan assignable ................................... 122
setup............................................................... 423 recalls .................................................................. 122
printer menu ......................................... 98, 418, 423 dynamic.......................................................... 149
printing recogn tmr ............................................................. 61
database sections ........................................... 423 RED...........................................................37, 41, 94
logs ................................................................ 423 red clearance time ............................................... 120
priority .......................................... 61, 298, 299, 326 red clearance timer.............................................. 481
event call-in ................................................... 362 red failure....................................................161, 188
of phase indicators........................................... 32 red interval .......................................................... 135
priority of input functions .................................. 481 RED OMIT ........................................................... 46
PRn ..................................................................... 430 red rest...........................61, 126, 192, 413, 431, 481
PR-n.................................................................... 413 Red Rest................................................................ 92
PRnn ................................................................... 414 red revert .....................................................154, 482
Processor .............................................................. 20 red revert override............................................... 303
program level & revision ..................................... 65 red revert time..................................................... 154
programmed offset ............................................... 55 RED RST .............................................................. 46
programming reduced green band .....................................250, 496
circuit plans ................................................... 282 reference.............................................................. 225
double clearing overlap ................................. 193 release modifier .................................................. 194
preemption..................................................... 295 release notes............................................................ 2
preemption forms .......................................... 434 repetitive data entry .............................................. 16
signal head steering ....................................... 392 request download ..................................98, 418, 428
programming card .............................................. 400 Request Download.............................................. 428
programming coordination................................. 222 request-to-send.................................................... 350
progression ......................................................... 212 reserve timer ......................................................... 61
Protocol-90 ................................................... 78, 380 reservice .............................................................. 326
PTMR ................................................................... 41 reservice time...................................................... 301
PTSI.................................................................... 504 response frame .................................................... 367
put a ped call....................................................... 413 restart machine..............................................98, 418
PWRU ........................................................ 362, 365 restarting ............................................................. 422
queue............................................................. 60, 332 restoring
quick setup menus ............................................................. 377

Index
restricted access code ......................................... 374 security code .......................................374, 376, 377
restricted security code....................................... 375 security codes................................................23, 375
restricting access to menus......................... 374, 376 selection sources .................................................224
resume interrupted sequence .............................. 306 self-test..................................................................28
REV PRn .............................................................. 46 semi-actuated coordination.................................496
revision ................................................................. 65 sequence..............................................................102
RFLT .................................................................. 365 library.............................................................104
RGB ............................................................ 250, 504 Sequence .............................................................102
ring.............................................................. 114, 482 Defaults ..........................................................107
ring and cophase diagram................................... 110 sequence configuration ...............................104, 111
ring assignment................................................... 105 sequence diagrams ..............................................107
ring interval .......................................................... 43 serial printing ......................................................423
ring n input function screens .............................. 413 service control.....................................................293
ring timers............................................................. 34 serviceable conflicting call ...........................92, 482
rl............................................................................ 76 set NVRAM ........................................................355
rm.......................................................................... 76 setting
Rn........................................................................ 413 date and time..................................................290
ROM ................................................................... 504 EEPROM settings..........................................379
rp........................................................................... 76 settings
rr............................................................................ 76 max variable...................................................140
RREST TERM ..................................................... 37 setup ......................................................................84
RRn..................................................................... 430 options..............................................................84
RRST ............................................................ 37, 413 prerequisites .....................................................84
RRTC.................................................................. 362 summary...........................................................85
RRVT ................................................................... 37 setup string ..................................................352, 354
rs ........................................................................... 76 requirements...................................................355
RS232 ................................................................. 349 SFL..............................................................362, 430
RS-232.................................................................. 17 SGO.............................................................152, 482
RS-232C ....................................................... 24, 459 shift key.................................................................15
RS-485........ 10, 17, 24, 444, 459, See TS2, RS-485 short route seeking ..............................................244
rsp ......................................................................... 79 shortcut
RTCR.................................................................. 413 primary status screen .......................................30
RTMR................................................................... 41 shorted loop failure ...............................................68
RTS..................................................... 349, 350, 355 si ............................................................................76
run....................................................................... 293 Signal Group ........................................................... 7
run active .............................................................. 36 signal head steering.............................392, 397, 482
run enable ................................................... 297, 326 signal timing .......................................................213
run in..................................................................... 36 simultaneous gap.................................................152
run interval............................................................ 59 simultaneous gap out ..........................................482
run invalid........................................................... 322 single entry..................................................144, 483
run rejection........................................................ 322 single permissive.................................228, 231, 496
RXBD ................................................................... 76 single ring............................................................102
S51 SLn ......................................................................430
sa........................................................................... 76 Smartways...........................................347, 361, 428
safety....................................................................... 1 soft boot ..............................................................422
SBD .................................................................... 430 soft flash..........................21, 36, 159, 160, 298, 483
sc........................................................................... 76 example ..........................................................160
SCC............................................................... 92, 482 limitations under TS1 ....................................160
scope ....................................................................... 1 port 1 communications ..................................161
SDD .................................................................... 430 recognition time .............................................161
SDLC .................................................................. 396 under TS2 Type 1 ..........................................160
SDLC connector ................................................. 459 soft recall.............................................124, 125, 484
se........................................................................... 76 Soft recall ..............................................................92
secondary to secondary enable........................... 367 sound level ..........................................................379
seconds mode ..................................................... 272 source ..................................................................224
security ................................................................. 17 SP ........................................................................504

Index
sp fcns................................................................... 79 modem status messages ................................... 77

speaker volume................................................... 374 normal I/O........................................................ 40
special case checksum errors ............................... 74 other screens .................................................... 39
special sequences................................................ 103 outputs.............................................................. 43
speed trap overlap card ..................................................... 64
setup............................................................... 364 port 2 ................................................................ 76
speed trap detector separation ............................ 364 port 3 ................................................................ 76
spfcs...................................................................... 78 preemption status screen.................................. 59
spl ......................................................................... 30 time of day screen............................................ 57
SPL ..................................................................... 504 TOD circuits .................................................... 58
SPL2 ................................................................... 413 UTCS ............................................................... 78
split ............................................................. 212, 497 voltage screen .................................................. 63
adaptive ......................................................... 257 status bits............................................................... 43
definition ....................................................... 213 status bits for ports A, B, and C.......................... 414
modes............................................................. 257 status screen .......................................................... 30
split plan ........................................................ 240 status screen navigation ........................................ 31
split input............................................................ 413 STOP................................................................... 413
split matrix.......................................... 248, 261, 497 stop bar 1 or 2 ....................................................... 21
split outputs ........................................................ 414 stop bar mode..............................................167, 484
split plan ..................................................... 213, 240 stop time................................................................ 36
split source.......................................................... 224 stop timing ..................................................413, 484
splits.................................................................... 238 storing data............................................................ 16
4 splits/cycle.................................................. 248 STP DEL............................................................... 67
SPLn ................................................................... 414 stretch..........................................................167, 485
SPP ..................................................................... 504 stretch timer .......................................................... 48
sr ........................................................................... 76 stretch/delay .......................................................... 21
st ........................................................................... 76 stretch/delay mode .............................................. 166
ST TIME............................................................... 46 STUF................................................................... 362
ST-an .................................................................. 414 supervisor............................................................ 375
standard overlap ................................................. 484 supervisor code ...........................................374, 376
standard overlap assignment .............................. 202 support .................................................................... 2
start permissive point ......................................... 497 switch .................................................................. 172
start up flash ....................................................... 102 switching............................................................. 469
start up interval................................................... 102 switching detectors ............................................. 171
start up phases .................................................... 102 symbols ................................................................... 4
start up red .......................................................... 102 sync
startup checks ....................................................... 28 reference......................................................... 288
startup flash active................................................ 36 sync pulse.............................................................. 54
start-up interval color ......................................... 191 sync pulses .......................................................... 216
startup parameters .............................................. 102 sync reference ..................................................... 288
startup PE run active ............................................ 36 sync reference mode ............................................. 95
startup phases sync source.......................................................... 252
editing.............................................................. 88 synchronization methods .................................... 216
startup timing synchronous data link control............................. 459
ped call ............................................................ 88 system name................................346, 370, 371, 372
status system sensor assignment................................... 179
alternate screen................................................ 38 systems
coordination status screen ............................... 54 menu............................................................... 346
D module output screens................................. 52 T/F...............................................................397, 504
density ............................................................. 41 tables ....................................................................xix
detector ............................................................ 47 tags
I/O configuration screen.................................. 49 TOD circuit ...................................................... 58
inputs screen.................................................... 45 TBC...............................................................51, 362
menu ................................................................ 99 TBCI ................................................................... 413
Mizbat status ................................................... 75 TBnn ................................................................... 413
MMU status screen ......................................... 82 TBR...............................................41, 137, 141, 151

Index
TCP/IP ................................................................ 504 phase allocation .............................................240

TCT....................................................................... 19 timing
technical assistance................................................. 2 gap reduction diagram ...................................142
Telephone Numbers ........................................... 361 normal phyase times ........................................94
test bits................................................................ 413 signals in a coordinated environment ............213
TEST n.................................................................. 46 timing plan
tests on hardware .................................................. 81 copying...........................................................425
Texas D module............................................ 25, 454 timing plan assignable recall modes...................122
third car detection............................................... 180 timing plan recall ..................................................92
TIa....................................................................... 430 timing plans.............................................21, 91, 134
time TOD ............................................................276, 504
daylight savings............................................. 287 circuit overrides .............................................286
gap ................................................................. 326 circuit plan .....................................................279
intervals ......................................................... 311 circuits............................................................430
setting ............................................................ 290 data entry modes ............................................277
time before reduction ................................. 137, 485 day plan example ...........................................280
time dependent mode ........................................... 95 daylight savings time .....................................287
time of day edit mode........................................................277
basic procedure description............................. 95 editing ............................................................278
circuit descriptions ........................................ 430 event programming........................................278
circuit plan ..................................................... 279 exception days................................................285
circuit plans ................................................... 282 insert mode.....................................................277
circuit status display ........................................ 58 ON/OFF events ..............................................279
circuits ........................................................... 279 sync reference ................................................288
date and time ................................................. 290 week plans......................................................283
definition ....................................................... 276 year plan.........................................................284
exception days ............................................... 285 TOD circuit overrides ...........................................76
general info...................................................... 22 TOD circuits .................................................57, 245
manual overrides ........................................... 286 TOD ckt override ..................................................75
sync reference................................................ 288 TOD dynamic circuits status screen .....................58
time of day functions screen ................................ 62 TOD/CL/INTER .................................................252
time of day override input .................................. 413 TOD/COORD .....................................................156
time of day status screen ...................................... 57 tools for flash memory update ............................382
time plans TPn ......................................................................430
conditional service......................................... 146 track clear............................................................324
dual entry ....................................................... 143 track clearance ....................................................196
time sync............................................................... 79 transfer menu ................................................98, 418
time to reduce ............................................. 137, 485 transferring databases .........................................420
timer................................................................ 60, 79 transition cycle ....................................................497
delay .................................................. 59, 61, 326 Transyt 1880EL ....................................................19
duration.................................................... 59, 301 triggering conditions...........................................194
duration as gap timer ..................................... 302 troubleshooting
extend .............................................................. 61 field modem setup..........................................358
fail.................................................................... 61 TS 1 operation.....................................................396
master polling .................................................. 75 TS 2 Type 1 operation
modem ............................................................. 77 cabinet components .......................................397
passage........................................................... 135 concise............................................................396
port 2................................................................ 76 I/O mapping ...................................................401
port 3................................................................ 76 MMU..............................................................400
preemption delay ........................................... 301 overview.........................................................396
recognition....................................................... 61 simple setup ...................................................398
reserve.............................................................. 61 TS 2 Type 2 operation ........................................397
reservice......................................................... 301 TS1
timers .................................................................... 34 release notes....................................................... 2
detector ............................................................ 48 TS2
times 4 splits per cycle ............................................238

Index
advance warning logic................................... 202 use interval data for overlaps..............299, 300, 316
configuration ............................. 24, 49, 150, 157 use percentage for phase allocation.................... 225
detector failures ............................................... 68 user interface......................................................... 12
detectors........................................................... 48 user priority.................................................297, 299
flash indications .............................................. 36 uses of soft flash ................................................. 160
general ............................................... 20, 22, 239 using the keypad ................................................... 16
HELP screens .................................................. 80 UTCS address ..................................................... 347
I/O configuration ............................................. 53 UTCS protocol..............................................78, 347
logged events................................................... 70 UTCS status display ............................................. 78
MMU ............................................................. 160 utilities menu ...................................................... 418
output pin assignments.................................. 445 V............................................................................ 36
release notes ...................................................... 2 V call..................................................................... 61
RS-485 communication................................... 24 V demand ........................................................ 30, 33
RS-485 Communication............ 20, 22, 150, 157 V MEMORY ........................................................ 40
TF BIUs......................................................... 369 V omit ................................................................... 61
TS2 - type 1 only........................... 150, 160, 366 V OUTPUT........................................................... 40
TS2 - type 2 only................................... 157, 392 valid interval ....................................................... 310
TS-2 valid intervals...................................................... 305
flash error messages ........................................ 36 variable initial ..................................................... 139
TS-2 vc........................................................................... 76
Type 2 connectors ......................................... 444 VCnn ................................................................... 430
TS-2 vd........................................................................... 76
input pin assignments.................................... 444 VDD.................................................................... 430
TS2 Type 1 ............................................................. 9 veh call ................................................................ 307
TS2 Type 2 ............................................................. 9 VEH CALL........................................................... 46
TTR............................................... 41, 137, 141, 151 veh head ................................................................ 60
TXBD ................................................................... 76 VEH HEAD .................................................... 43, 60
type 0 command ................................................. 367 veh omit .............................................................. 125
type 1 .............................................................. 24, 50 Veh Omit............................................................... 92
type 2 .............................................................. 24, 49 VEH OMIT ........................................................... 46
type 2 I/O mode error ........................................... 36 vehicle calls........................................................... 30
type conventions..................................................... 3 manual.............................................................. 38
typematic mode .................................................... 16 vehicle demand codes..................................... 33, 36
types of events...................................................... 69 vehicle detected inputs........................................ 413
typical startup parameters .................................. 102 vehicle omit.................................................413, 486
UCF .............................................. 51, 362, 430, 485 vehicle overlap green signals.............................. 414
exit phases ..................................................... 151 vehicle overlap red signals ................................. 414
last phases...................................................... 151 vehicle overlap yellow signals............................ 414
override.......................................................... 298 vehicle phase green signal .................................. 414
override hold ................................................. 150 vehicle phase red signals .................................... 414
programming ................................................. 150 vehicle phase yellow signals .............................. 414
soft flash ........................................................ 160 version 3.4............................................................... 6
test A or B ..................................................... 150 version 3.6............................................................... 7
UCF central .......................................................... 36 version 3.6.2............................................................ 7
UCF flash ............................................................. 36 viewing
UD ........................................................................ 51 preemption run............................................... 295
UDn ............................................................ 430, 431 virtual outputs ..................................................... 408
uniform code flash...................................... 150, 413 virutal inputs ....................................................... 408
unit configuration menu ..................................... 374 VOGa .................................................................. 414
unit control signals ............................................. 413 VOID................................................................... 414
unit figure ........................................................... 8, 9 vol head................................................................. 60
unregulated voltage .............................................. 63 VOL HEAD .................................................... 43, 60
unused................................................................... 77 voltage................................................................... 63
updating controller firmware ............................. 380 volume ........................................................374, 379
upgrade utility for firmware ............................... 382 volume adjustment................................................ 17
upgrading firmware ............................................ 386 volume density............................................139, 486

Index
volume log .................................................... 68, 364 WRM................ 46, 90, 93, 126, 130, 247, 430, 504
printing .......................................................... 423 X......................................................................33, 34
VOn .................................................................... 430 input .................................................................61
VORa .................................................................. 414 x7...........................................................................76
VOYa.................................................................. 414 x8...........................................................................76
vr........................................................................... 76 xd...........................................................................76
vt ........................................................................... 76 xe...........................................................................76
W .......................................................................... 32 xp...........................................................................76
waiting .................................................................. 77 xped.....................................................................117
walk .................................................... 124, 133, 197 compatibility card jumpers ............................120
in preemption entry ....................................... 304 enable source selection ..................................119
WALK .......................................................... 94, 504 output phases..................................................119
walk hold state.................................................... 129 phase selection ...............................................119
walk interval ....................................................... 136 soft return phases ...................................120, 121
walk OL dark...................................................... 189 XPED ..................................................................320
walk OL red........................................................ 189 xs ...........................................................................76
walk rest.............................................. 124, 126, 486 xt............................................................................76
walk rest modifier......... 90, 130, 147, 413, 431, 486 xu...........................................................................76
walk rest state ..................................................... 129 Y............................................................................32
walk timing state ................................................ 129 year plan..............................................................284
warning symbol ...................................................... 4 YEL.................................................................37, 41
watchdog failure ............................................. 36, 68 yellow....................................................................94
website.................................................................... 2 yellow offset .......................................................247
week plans .......................................................... 283 YEnn ...................................................................414
WIG-WAG ................................................. 159, 323 yield.......................................................................79
wildcards............................................................. 245 yield percent................................................249, 497
WK........................................................................ 37 yield permissive ..................................................497
WKnn ................................................................. 414 yield permissives.................................................230
Wlk Rest ............................................................... 92 yield point ...........................................................498
WR........................................................................ 37 YTMR ...................................................................41
write configuration ............................................. 355

Peek Traffic Corporation
2906 Corporate Way
Palmetto, FL 34221
ph: (941) 845-1200
toll free in U.S.: (800) 245-7660
fax: (941) 845-1504
email: tech.support@peektraffic.com
8204C

3000E Operating Manual

Hochgeladen von

Dokumentinformationen

Copyright

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

3000E Operating Manual

Hochgeladen von

Copyright:

Operating Manual

3000 Series TS1/TS2/NTCIP Traffic Signal Controllers

3000 and 3000E ®

NEMA TS1/TS2 TRAFFIC CONTROLLERS

Peek Traffic Corporation.

8204C - 3000/3000E Operating Manual Assembly

3000 Series Traffic Controllers iii

iv 3000 Series Traffic Controllers

Chapter 2 — Status Displays ...................................................................................27

3000 Series Traffic Controllers v

vi 3000 Series Traffic Controllers

Stretch/Delay – Mode 2 ................................................................................................................ 166

3000 Series Traffic Controllers vii

viii 3000 Series Traffic Controllers

Configuring Circuit Plans ..................................................................................................................... 282

3000 Series Traffic Controllers ix

x 3000 Series Traffic Controllers

Notes on the Definitions ...................................................................................................................... 431

3000 Series Traffic Controllers xi

xii 3000 Series Traffic Controllers

Figure 55 – MOE Log - type 3...........................................................................................................................................67

3000 Series Traffic Controllers xiii

xiv 3000 Series Traffic Controllers

3000 Series Traffic Controllers xv

xvi 3000 Series Traffic Controllers

Figure 307 –Preemption Example 2 - Interval 4 phase colors ......................................................................................... 342

3000 Series Traffic Controllers xvii

xviii 3000 Series Traffic Controllers

Table 1 – Documents related to the 3000 Series Traffic Controllers....................................................................................2

3000 Series Traffic Controllers xix

xx 3000 Series Traffic Controllers

PURPOSE AND SCOPE

3000 Series Traffic Controllers 1

Peek Traffic — Technical Support

Additional information is also available at the Peek Traffic website:

2 3000 Series Traffic Controllers

CONVENTIONS USED IN THIS MANUAL

Keyboard and Menu Conventions

3000 Series Traffic Controllers 3

4 3000 Series Traffic Controllers

3000 Series Traffic Controllers 5

Evolution of the 3000 Series Controller

6 3000 Series Traffic Controllers

Checking the Firmware Version

3000 Series Traffic Controllers 7

HARDWARE IN THE 3000 SERIES

Version 3000 Traffic Controller Hardware

Figure 1 – 3000 Controller D Module

8 3000 Series Traffic Controllers

Version 3000E Traffic Controller Hardware

3000 Series Traffic Controllers 9

Note TS 1 controllers have hardwired pins in the A, B, and C connectors to physically

Flash Memory Enabled 3000E Controllers

10 3000 Series Traffic Controllers

Figure 4 – Flash-enabled 3000E Controller (TS 2 Type 2 version)

Figure 5 – ‘Flash Memory Enabled’ logo

3000 Series Traffic Controllers 11

12 3000 Series Traffic Controllers

3000 Series Traffic Controllers 13

Figure 7 – 3000E Keypad

14 3000 Series Traffic Controllers

3000 Series Traffic Controllers 15

Using the Keypad

To Quickly Return to the Main Menu

To Quickly Return to the Top Dynamic Screen

16 3000 Series Traffic Controllers

To Review the First Time Setup Menu