ASC/3 Controller Technical Manual

NEMA TS2 Fully-Actuated Advanced Traffic Controller

This specification is fully met by the following Econolite models:

ASC/3-1000 Fully Actuated Controller

ASC/3-2100 Fully Actuated Controller

TABLE OF CONTENTS

1. INTRODUCTION

2. HARDWARE

2.1. Enclosure

2.2. Electronics

2.3. Front Panel

2.4. Data Key

2.5. Connectors

2.6. Serviceability

3. DISPLAYS

3.1. Dynamic Displays

3.2. Programming Displays

4. PROGRAMMING

4.1. Programming Methods

4.2. Programming Security

4.3. Programming Utility Functions

5. ACTUATED CONTROL FUNCTIONS

5.1. Phase Sequence

5.2. Timing Intervals

5.3. Overlaps

5.4. Conditional Service

5.5. Additional Features

6. COORDINATION

6.1. Coordination Patterns

6.2. Cycle Length

6.3. Synchronization

6.4. Offset

6.5. Split

6.6. Permissive Periods

6.7. Phase Re-service

6.8. Transition Cycles

6.9. Crossing Artery Control

6.10. Local Split Demand

6.11. Adaptive Split Demand

6.12. Free Mode

6.13. Manual Control

6.14. Interconnect Modes

6.15. Master Coordinator

7. PREEMPTION

7.1. Railroad-Fire-Emergency Vehicle Preemption

7.2. Bus Preemption

7.3. Preemption Safeguards

7.4. Transit Signal Priority

8. TIME-BASED CONTROL & NON-INTERCONNECTED COORDINATION

8.1. Clock/Calendar Functions

8.2. Time-Based Control

8.3. Non-Interconnected Coordination

9. DETECTORS

9.1. Detector Functions

9.2. Detector Cross Switching

9.3. Detector Types

9.4. System Detectors

10. SYSTEM COMMUNICATIONS

10.1. On-Street Master Communications

10.2. Telemetry

10.3. Communications Protocols

10.4. Ethernet Communications

10.5. External Clock

10.6. Communications Ports

11. DIAGNOSTICS

11.1. General Diagnostics Features

11.2. Detector Diagnostics

12. LOGGING

12.1. Detector Logging

12.2. Detector Failure Logging

12.3. Event Logging

12.4. MOE logging

NEMA TS2 / NTCIP FULLY-ACTUATED TRAFFIC CONTROLLER

1. INTRODUCTION

This specification sets forth the minimum requirements for a shelf-mounted, two through sixteen phase, fully-actuated, digital, solid-state traffic controller. The controller shall meet, as a minimum, all applicable sections of the NEMA Standards Publications for TS2 and NTCIP. Where differences occur, these specifications shall govern. Controller versions shall be available to comply with NEMA TS2 Types 1 and 2. Type 2 versions of the controller shall be capable of operating as a Type 1 controller.

2. HARDWARE

2.1. Enclosure

2.1.1. The controller shall be compact so as to fit in limited cabinet space. It shall rest on a shelf that is not more than 7" deep. External dimensions shall not be larger than 10 1/4" x 15 1/4" x 9" (H x W x D).

2.1.2. The enclosure shall be constructed of aluminum and shall be finished with an attractive and durable protective coating. Model, serial number, and program information shall be permanently displayed on the top surface.

2.2.1. The electronics shall be modular and shall consist of vertical circuit boards. Horizontal circuit cards shall not acceptable.

2.2.2. A microprocessor shall be used for all timing and control functions. Continuing operation of the microprocessor shall be verified by an independent monitor circuit, which shall set an output and indicate an error message if a pulse is not received from the microprocessor within a defined period.

2.2.3. In the interest of reliability, no sockets shall only be used for any electronic device. All devices shall be directly soldered to the printed circuit board. Surface mount parts shall be used for the majority of the electronic components in the controller.

2.2.4. A built-in, high-efficiency switching power supply shall generate all required internal voltages as well as 24 VDC for external use. All voltages shall be regulated and shall be monitored with control signals. Fuses shall be mounted on the front of the controller for 120 VAC input and 24 VDC output.

2.2.5. Timing of the controller shall be derived from the 120 VAC power line.

2.2.6. User-programmed settings and intersection configuration data shall be stored in Flash Memory. Memory requiring an energy storage device (battery or capacitor) to maintain user data shall not be acceptable. To facilitate the transfer of user-programmed data from one controller to another, a data transfer module (data key) using a separate serial flash memory device shall be an option. This data transfer module shall be easily removable and directly accessible from the front of the controller. The controller will not require this module to be present for proper operation.

2.2.7. All controller software shall be stored in Flash Memory devices. The controller software shall be easily updated without the removal of any memory device from the controller. The use of removable PROMS or EPROMS from the controller shall not be acceptable. The controller shall include an option that allows updating software using a Windows based computer. This option shall allow updating the controller software via a serial or Ethernet port from the front of the controller. Updating the controller software shall require the intersection to be in flash for no more than ten seconds using Ethernet file transfer.

2.2.8. All printed circuit boards shall meet the requirements of the NEMA Standard plus the following requirements to enhance reliability:

2.3.1. The front of the controller shall consist of a panel for the display, keyboard and connectors for all necessary user connections. It shall only be necessary to open the front panel during option installation and maintenance of the electronic circuits.

2.3.2. A 16-line by 40-character/line alphanumeric liquid crystal display (LCD) shall be used to show program and status information. The display area shall have nominal measurements of 2 1/2" x 4 1/2" (H x W) or larger. For ease of viewing, backlighting by light emitting diodes and multiple levels of contrast adjustment shall be provided. Display contrast shall be adjustable with front panel mounted push buttons. The use of user potentiometers for display contrast will not be acceptable.

2.3.3. Front-panel operator inputs shall be via clearly labeled and environmentally-sealed electrometric keys. These shall include a 10-digit numeric keypad, nine function keys, an oversize ENTER key, and an oversize four-arrow cursor control key.

2.3.3.1. The nine function keys shall be clearly labeled and provide the following operation:

2.2. Electronics

2.3. Front Panel

a. All plated-through holes and exposed circuit traces shall be plated with solder.

b. Both sides of the printed circuit board shall be covered with a solder mask material.

c. The circuit reference designation for all components and the polarity of all capacitors and diodes shall be clearly marked adjacent to the component. Pin 1 for all integrated circuit packages shall be designated on both sides of all printed circuit boards.

d. All printed circuit board assemblies, except power supplies, shall be coated on both sides with a clear moisture-proof and fungus-proof sealant.

MAIN MENU - Pressing the Main Menu key shall display the main menu.

SUBMENU - Pressing the Sub Menu key from any data screen shall display the current submenu.

NEXT DATA - Pressing the Next Data key shall search for the first non-zero data field, thus allowing rapid search for valid entries.

NEXT SCREEN - Pressing the Next Screen key shall display the next screen, thus allowing rapid advancement from screen to screen.

HELP - Pressing the Help key at any data entry field shall display a help screen about that field.

STATUS DISPLAY - Pressing the Status Display key shall present the intersection status display.

NEXT PAGE - Pressing the Next Page key shall advance to the previous or next group of data entry screens in a submenu.

BACKLIGHT - Pressing up and down arrow-shaped keys shall adjust the backlighting of the LCD display screen for brighter or dimmer contrast.

SPECIAL FUNCTION - Pressing the special function key shall place Pedestrian Calls while viewing the main status display, lock access to controller data until supervisor or data change access codes are entered, and enter hexadecimal values

CLEAR - Pressing the clear key shall abort a data entry and restore the current value.

2.4. Data Key

2.4.1. A data key shall be available for use as a database storage device (backup) or as a database transfer module. It shall be capable of storing a minimum 256KB of data.

2.4.2. The data key shall be hot swappable, so that it can be inserted and removed without powering down the controller.

2.4.3. The data key shall be capable of storing the entire controller database and shall retain the information without use of battery or capacitor backup.

2.4.4. The controller shall not require this key to be present during normal operation.

2.5.1. All interface connectors shall be accessible from the front of the controller. Controller models shall be offered to accommodate different versions, as follows:

2.5. Connectors

a. NEMA TS2 Type 1

b. NEMA TS2 Type 2

c. NEMA TS1

d. Connectors and signals compatible with the Econolite Model ASC/2, ASC/2S & ASC-8000 25 pin telemetry port and D connector.

2.5.2. To facilitate special applications the controller shall have the capability of assignment of any input or output function to any input or output pin respectively on the interface connectors, with the exception of Flashing Monitor, Controller Voltage Monitor, AC+, AC-, Chassis Ground, 24VDC, Logic Ground and TS2 Mode bits.

2.6. Serviceability

2.6.1. All electronic modules including the power supply shall be easily removable from the front of the controller using a screwdriver as the only tool. All power and signal connections to the circuit boards shall be via plug-in connectors.

2.6.2. The controller layout shall allow the removal and replacement of any circuit board without unplugging or removing other circuit boards, except for the power supply. No more than two boards shall be attached together to form a circuit assembly.

2.6.3. The controller enclosure shall be designed so that one side of any circuit board is accessible for troubleshooting and testing while the controller is still in operation. This capability shall be accomplished without the use of extender cards or card pullers.

3.1.1. Dynamic displays listed below shall be provided to show the operational status of the controller. Additional displays shall be offered for programming. It shall be possible to place vehicle, pedestrian and preemption calls from the keyboard while displaying status information.

3.1.2. Intersection status display shall indicate a summary of ring, phase, coordination, preemption and time-based control status.

3.1.3. Controller status display shall indicate current interval, pedestrian, density, maximum, and maximum extension timing by phase and ring. The status of vehicle and pedestrian signal outputs shall be displayed in combination with vehicle and pedestrian calls.

3.1.4. Coordinator status display shall indicate the command source, current coordination pattern information, local and system cycle count, commanded/actual offset, offset correction, time-based control status, hold, force-off, vehicle permissive, split count down, split extension, offset from ring 1 and green band indications.

3.1.5. Preemptor status display shall indicate priority (railroad, fire, emergency) preemptors and bus preemptors with calls, preemptor active, inhibit, and delay status. When a preemptor is active, the display shall also indicate preemptor interval, timing, duration, and hold status. A portion of the display shall indicate the controller status during preemption including current status, interval, and timing by phase and ring and the status of vehicle and pedestrian signals for each phase.

3.1.6. Time base status display shall indicate the current time and date, the current day and week program, the active program step for both coordination pattern and time-of-day functions, the start time of the next program step, and the highest step used. The programmed selections of the active coordination pattern and time-of-day pattern shall also be displayed.

3.1.7. There shall be communications status displays for Port 1 (SDLC), Port 2 (terminal) Port 3, Ethernet and NTCIP.

3.1.7.1. Port 1 (SDLC) status display shall indicate the frame responses from the MMU, the terminal and facilities BIUs and the detector BIUs.

3.1.7.2. Ports 2 and 3 status display shall indicate the interconnect format, transmit, valid data, data error, carrier detect and the last valid command.

3.1.7.3. An Ethernet status display shall indicate the line speed, the line status, the total number of transmit and receive counts and the number of transmit and receive error counts.

3.1.7.4. An NTCIP status display shall indicate the total number of SNMP and STMP transmit and receive counts.

3.1.8. A detector status display shall indicate activity for up to 64 detectors. The display shall show detector calls as they are processed by the controller.

3.1.9. Flash/malfunction management unit (MMU) status display shall indicate flash status plus MMU channel, conflict, and monitoring function status. A separate display shall indicate the results of the controller’s comparison of its MMU programming to the programming in the controller.

3.1.10. An input and output status display shall indicate the activity of all of the logic level inputs and outputs to the controller.

3.2.1. Programming displays in the form of menus shall aid the operator in entering data from the front-panel keyboard.

3.2.2. A main menu shall allow the user to select a major function of the controller. A submenu shall then be displayed to allow the user to select a sub-function within the major function. A four-arrow cursor key shall allow the user to scroll through all programmed data.

3.2.3. English language and traffic engineering terminology shall be used throughout to facilitate programming. The display organization shall allow traffic personnel to program the controller without using reference cards or manuals. All data entry and data screens shall be in logical order.

3.2.4. Programming entries shall consist of alpha-numerical values, YES/NO and ON/OFF entries. During program entry, the new data shall be displayed as it is entered. Entries shall only be validated and stored when the consistency check is preformed for entries that are constrained by other programmed data or when the ENTER or cursor key is pressed when they are not.

3.2.5. The keyboard entry software shall include context sensitive help screens. Help information shall be accessed by placing the cursor on the data entry in question then pressing the HELP key. Help screens shall be provided for all keyboard-entered data and shall include at a minimum range, description, and functional operation information for the data entry.

3.1. Dynamic Displays

3.2. Programming Displays

4.1. Programming Methods

3. DISPLAYS

a. An example of constrained data is the sequence of the phases within a ring. They need to be checked with the phase compatibility, phases in the ring and start phases among others.

b. An example of non-constrained data is the vehicular extension time entry.

4. PROGRAMMING

The methods listed below shall be available for controller configuration and timing entries. The manufacturer shall be able to provide as off-the-shelf items all of the firmware and software required to affect the listed methods and to implement network operation with system masters and host PC's.

a. Manual data entry via the front panel keyboard

b. Downloading via telemetry from a system master connected to a host PC in a closed-loop system.

c. Downloading from a portable PC-compatible computer via an Ethernet or serial cable.

d. Transfer from one controller to another using the Ethernet port on each controller.

e. Transfer from one controller to another, or restoring for a back-up copy, using a data transfer module (data key).

4.2. Programming Security

4.2.1. A minimum of three access levels shall be available to provide programming security.

4.2.1.1. The highest or supervisor level shall have access to all programming entries including setting access codes.

4.2.1.2. The second or data change level shall have access to all programming entries except access codes.

4.2.1.3. The third or data display level shall only have access to displayed data. No access code shall be required to display data.

4.2.2. User selectable, four-digit access codes shall be provided for the supervisor and data change access levels. Access codes shall initially be set to provide unrestricted access.

4.2.3. If there has been no keyboard activity the controller shall automatically logoff the user after 30 minutes.

4.3.1. A copy function shall permit copying all timing data from one phase to another. It shall also permit copying all timing plan from one timing plan to another, one detector plan and detector options plan to another, all coordination pattern data from one pattern to another and one sequence to another. This feature will facilitate data entry when programming any two or more phases with the same timing values, or detectors with the same programming, and/or two or more coordination patterns with the same pattern data.

4.3.2. The controller unit shall contain a backup data base with user specified values stored in non-volatile memory. A copy function shall permit transferring the backup database to the active database.

4.3.3. A memory-clear function shall permit the user to clear data entries for the following controller functions, either individually or all at once:

4.3.4. A sign-on message shall allow the user to view the controller software version number. This message shall be displayed upon power-up until a key is depressed. It shall also be possible to display the sign-on message by keyboard selection. The sign-on display shall allow a user-defined message of up to two lines with 38 characters per line.

4.3.5. The controller shall have the capability to output a memory image of the user programmed settings and intersection configuration data in binary format. This shall allow transferring the memory image data to a data key.

4.3. Programming Utility Functions

a. Configuration

b. Controller

c. Coordinator

d. Preemptor

e. Time base

f. Detectors

g. Logic Processor

5. ACTUATED CONTROL FUNCTIONS

The controller shall provide all actuated control functions and operations required by the NEMA TS2 Standard. In addition, it shall provide the features described in the following paragraphs.

5.1. Phase Sequence

5.1.1. The phase sequence of the controller shall be programmable in any combination of sixteen phases, eight concurrent groups and four timing rings.

5.1.2. Phase sequence information shall be changeable from the keyboard and stored in EEPROM data memory.

5.1.3. The standard phase sequence of the controller shall also be capable of being altered by coordination, time-of-day or external alternate sequence command. The alternate sequence commands shall allow reversing the normal phase sequence of each phase pair as shown below:

a. Command A reverses phases 1 and 2

b. Command B reverses phases 3 and 4

c. Command C reverses phases 5 and 6

d. Command D reverses phases 7 and 8

e. Command E reverses phases 9 and 10

f. Command F reverses phases 11 and 12

5.1.4. The operator shall be able to select from a library of standard sequences. As a minimum the following shall be provided

5.1.5. An exclusive pedestrian clearance movement shall be provided which will time and display the pedestrian indications with the vehicle movements remaining in all red.

a. Standard NTCIP sequence

b. Two through eight phase controller

c. Sixteen phase quad left turn controller

d. Four single ring 4 phase controllers

e. Dual TS2 eight phase quad controllers

f. TXDOT three phase diamond controller

g. TXDOT four phase diamond controller

5.2. Timing Intervals

5.2.1. Timing intervals shall be programmable from 0-255 in one second increments or from 0-25.5 in one-tenth second increments, depending on the function.

5.2.1.1. Four independent timing plans shall be provided and selectable on a time-of-day basis or by coordination pattern. Each plan shall contain the following interval timings:

Minimum Green	Maximum 3
Delay GreenWalk	Dynamic Maximum SYellow Clearance
Walk Maximu	Red Maximum
PedestPedest	Actuations before RSeconds per Actua
Vehicle	Time before Red
Maximum 1 Maximum 2	Time to ReduceMin Gap

a. Minimum gre
c. Pedestrian clearance
f. Red revert


Walk and Pe	time base action
interval shall
5

5.2.7. The Pedestrian Walk interval shall extend from Walk to the smaller of the Walk Max time or the phase maximum in effect with a constant input from the “Walk Extension detector”.

Volume den

a user-specified number of a

ovide a user specified nu

uction shall be initiate

vehicle demand. Three maximum green intervals shall be selectable per phase based on either time-of-day, coordination pattern or external input. The initial interval shall be selectable as Max 1, Max 2, or M

extended by a dynamic max step interval on each successive cycle until it is equal to dynamic maximum. If the phasegaps out for two successive cycles, then the maximum green time shall be redu

5.2.10. Each phase shall have a red maximum timing

assigned phase to be able to extend the all red period. If this detector fails then the all red extension feature shall bedisabled.

5.3. Overlaps

programmable as standard, other (see section 5.3.2) or minus green / yellow. The green, yellow and red intervals shall be individually programmable following termination of the parent phase. The overlaps programmed as minus green / yellow overlaps shall provide overlap green when any of the overlap phases are green or when in transitionbetween overlapped phases and a modifier phase is not green. The overlap will be yellow when an overlapped phase is yell

5.3.2. The other overlap option shall provide for protected, pedestrian protected, not overlap, trailing, leading and advance green programming. 5.3.2.1. A protected overlap shall be green, yellow or red like a normal overlap except its outputs shall be blank when the protected phase is green, or the controller is transitioning to a non-included phase. 5.3.2.2. A pedestrian protected overlap

b. When the controller is in transition between included phases and a pedestrian protected phase is not next c. After servicing an included phase pedestrian demand if there is enough time before max out to servithe overlap minimum green

overlapping the pe

5.3.4. Overlap functions shall be programmable from the controller keyboard. As an option, the four internalgenerated standard overlaps may be programmed with a NEMA overlap card.

5.4. Conditional Service

service an odd-numbered phase once normal service to that phase has been completed and enough time for nal service exists on the concurrent even phase.

5.4.2. A conditional service minimum green time shall be programmable for each phas

green if the phase is conditionally served.

It shall be possible to program the controller to re-service the even phase after conditionally serving an odd e an even phase has been co

5.5. Additional Features

5.5.1. The following features shall be programmable for each phase in each of four separate detector plans: a. Locking/non-locking detector memory

g. Enable Added In

5.5.2. Also programmed by phase shall be: a. Phase in use b. Exclusive Pedestrian phase

5.5.3. Soft recall shall return the controller to the programmed phase in the absence of other calls.

5.5.5. The controller shall permit power start and external start to be individually programmed by phase and interval. Start intervals shall be green, yellow red, or yellow wi

5.5.6. During a power start con

The controller shall provide guaranteed pas

vide a full passage (

extension interval (prese

The controller sh

r to ensure that one p

concurent group.

b. Flashing WALK output

e. Pedestrian indications remain dark with no call

5.5.11. Programming shall be provided to inhibit re-service of odd phases (left tu

5.5.12. The controller shall provide a programmable sim

5.5.13. The controller shall provide automatic flash selection per the requirements of the MUTCD. Both the flash entrance and exit phases shall be progr

desired through the load switches, both the phase and overlap outputs shall be flashed either yellow or red as selected by the operator. Automatic flash shall be selectab

5.5.14. The contro

day and an external input; both functions must be TRUE for dimming to occur. Programming

6.1. Coordination Patterns

independent cycle length, offset value and split pattern. The coordination patterns shall be selected using telemetr(system), hardwire, or non-interconnected (time base) coordination commands.

6.1.2. The coordination patterns shall be selected by the coordination command using the following formats: a. Pattern - This format shall allow selecting the coordination patterns directly, that is, commanding Plan selects Pattern 1. Pattern command shall include 1-120 patterns, pattern 254 shall select free and pattern 255 shall select flash. b. Standard - This format shall allow selecting the coordination patterns using a pattern number derived from

Offset)). c. TS2 - This format shall allow selecting the coordination patterns as a function of Timing Plan and one of three offsets. With this format a minimum of 20 Timing Plans shall be available for selection of one of sixcoordination patterns.

The controller shall provide the fo

g of the Green/Walk, Yellow/Ped Cle

ORINATION

ation functions to control intersection cycle lengths, s

provided as a standard feature, with no need for additional modules or software.

6.1.3. The following fun

b. Split pattern c. Offset value

e. Split and offset in s

i. Coordinated phase split extension j. Timing plan k. Actuated rest in walk

m. Ring extension

n. Split demand pattern Ring displacement Directed split preferences

q. Special function outputs following functions shall be programmable for each of the 120 Split patterns: Coordina

b. Split value by phase Omit by phase Min recall by phase

f. Pedestrian recall

the system sync pulse during each subsequent cycle. If a sync pulse does not occur, the co

g. Max and Pedes

ycle Length

One cycle length shall be provided for each co

5 sconds in 1-second incre

The cycle length s

ynchronization

For systems with a single

se, which shall serve a

For hardwire systems with

t syncs and checking for reoccurr

tinue to operate with the la

pulse does not occur with

ertto the non-interco

ffse

Offset shall normally be defined

of the lagging coordina

6.4.2. Offsets shall be programmable using both percent and seconds. The range shall be from 0-99% of the cycle length in 1% increments or 0-254 seconds in

6.4.3. Offset changes shall be achieved by adding or subtracting cycle time over a maximum of three cycle periods to allow a smooth transition to the new offset. Other offset change methods sha

correctn using dwell shall also be selectable.

6.5.1. Each split shall provide a split interval for each of sixteen phases. The split interval shall be programmable using percent or seconds. The range shall be from 0-99% of the cycle length in 1% increments or 0-255 seconds in 1-second increments.

shall be selectable to be a fixed point within the cycle or allowed to float. If floating force-offs are selected each phase shall time no more than its own split interval.

coordinted phase is actuated, vehicle detections shall permit the coordinator to extend a phase beyond the normal yield point. Extended coordinated phase green shall be selectable using the same range as split interval settin

(walk rest) pedestrian movements. 6.6. Permissive Periods

6.6.2. All permissive timing shall begin at the lead coordinated phase yield point. A yield point shall be automaticalcomputed for the coordinated phase in each ring. The coordinated phase yield points shall allow the coordinated phases to yield indep

the coodinated phase split interval plus pedestrian and vehicle clearance times. 6.6.3. Automatic permissive period operation shall be provided by automatically calculating a permissive period foeach non-coordinated phase. The permissive period shall consist of a separate vehicle and pedestrian period computed from the phase split interval and the

all remining phases shall be served in normal sequence. 6.6.4. Single permissive period operation shall be provided by defining a single time period per cycle beginning with the yield point during which the controller is allowed to answer phase calls for any phase. The duration of this periodshall be selectable in each coordina

during this period, calls on the remaining phases are served in normal rotation. During the second permissive period, the controller shall answer calls on all remain

each cordination pattern. 6.7. Phase Re-service

6.7.1. If actuated coordinated phases are in use it shall be possible to re-service non-coordinated phases within the same cycle if sufficient time remains. A phase shall be re-serviced only if the permissive period for the phase inthere is sufficient time remaining in the cycle to service the phase. 6.7.2. Phase re-service shall be capable of being enabled

6.8. Transition Cycles 6.8.1. The controller shall provide a smooth and orde

6.8.2. During a free-to-coordinated transition, the controller shall initiate a pick-up cycle beginning upon receipt of a sync pulse and a valid coordination command. The controller shall then enter coordination mode upon crossing a barrier or if resting in the coordinated phases. 6.8.3. Each coordination c

under control of separate masters. 6.9.2. An external input shall enable dual coordination. Once ena

6.9.4. Dual coordination shall force a selectable crossing artery split plan to be used so as to allow a particular split to be optimized for dual coordination in each coordination pa

6.10. Lcal Split Demand 6.10.1. The coordinator shall provide a minimu

6.10.2. If the split demand detector indicates continuous vehicle presence during a

6.11. Adaptive Split Demand

6.11.1.The coordinator shall provide a method to select the split using measurement of each phase’s green utilization. From the measurement the coordinator shall determine which phase or phases had excess time that was ot used during the last measurement period. Then the excess time shall be added to the first se

be addd to a second set of preferential phases. If both sets of preferential phases gapped out during the last measurement period

6.12. Free Mode

6.12.3. The coordinator shall revert to the free mode wh

a. Manual control enable b. Stop time c. Automatic flash d. Preemption

6.13. Manual Control The controller shall allow manual override of the current coordination command from the keyboard. The manual command shall allow selection of any coordination pattern to be in effect.

a. Non-interconnected coordination (time-based)

c. Hardwired

6.14.2. The coordinator shall be compatible with fixed-time interconnect, which provides the sync pulse superimposed on the offset lines. It shall also operate within an int

to be used as a time-of-day master in a hardwired interconnected system.

non-coordinate

to service cal

6.6.5. Dual-permissive per

phase split interval.

durin the next cycle. This splitlan hall be capable of being

6.12.4. The coordinator shall provide an a

-interconnected coordination

aster Coordinator

emergency or bus vehicle preemption sequences. Preemption capability shall be standard and shall not require additional modules or software.

7.1. Railroad-Fire-Emerge

7.1.1. The ten railroad-fire-emergency vehicle preemptors shall be selectable as a priority or non-

preemptor calls shall override non-priority preempto

umbered priority

7.1.2. Each preemptor shall provide a locking and non-locking memory feature for preemptor calls. If a in the non-locking mode and a call is received and dropped during the delay time, the preemptor shall not be servic

tenth second increments, d

7.1.4. A programmable delay time interval shall be provided to inhibit the

one second incremen

7.1.5. An inhibit time shall be provided as the last portion of the delay time interval. During this time, phases that arenot part of the preempt sequence shall be inhibited from service. This time shall be programmable from 0-65535 seconds in one second incremen

7.1.6 A programmable extend input shall cause the

This time shall be programmable from 0-25.5 seconds in one-tenth second increments. 7.1.7. A programmable duration time shall be provided to control the minimum time that a preemptor remains

7.1.8. A programmable maximum time shall be provided to control the maximum time that a preemptor input

recogned again. 7.1.9. Phases timing at the beginning of a preemption sequence

preemptor minimum time, the controller shall immediately advance to the next sequential interval. Minimum times shall be programmable for the following intervals: a. Green/walk/p

c. Red 7.1.10. A phase shall advance imme

interval, or alternately to advance immediately to yellow. During preemption, pedestrian indicators shall be selectable as being a solid DONT WALK, OFF (blank) or fully operational.

that it remains red for the remainder of the preemption sequence. Overlaps terminating or forced to terminate shall time the preemptor minimum yellow and red clearance times.

7.1.12.Each preemptor shall provide user-programmable green, yellow and red track clearance intervals. Thesbegin timing immediately after the preemptor minimum red interval.

period, the selected phases shall time the track clearance green, yellow and red intervals once, and then advance to the hold interval. If track clearance phases are not selected the track clearance interval shall be omitted from the preempt sequence. Controller interval timing shall be used if track clearance interval times have been programmedzero.

The preem

preemptor maximum time has been exceeded. During the preemption hold interval, any one of the following conditions shall be selectable: a. Hold phase green b. Limited phase service

d. Flash 7.1.15. Any valid phase, except a track clearance phase, shal

permissive phases shall be selectable to flash yellow, and the remaining phases shall flash red. Overlaps associated with the phases flashing yellow shall also flash yellow unless they ha

7.1.16. The preemptor shall immediately cause flashing operation if the preemption input and the track interlock inputare not in opposite states and the track interlock function is enabled. 7.1.17

completion of the hold green interval, the controller shall time the hold yellow and red clearance intervals prior to transfer to the exit phases. 7.1.18. Up to four permissive e

sequence, this time shall serve as the maximum green time in effect for one controller cycle for all phases except holdphases. 7.1.20. Preemptor linking shall permit preemption sequences, where lower-priority preemptors may call the higher-priority preemptor

7.1.21. Preemptor active outputs shall be provided for each of the preemptors. The output shall be set to ON when the preemption sequence begins and shall remain ON for the duration

program the non-active, non-priority preemptor outputs to flash while another preemptor is active. 7.1.22. Preemptors shall normally override automatic flash. It shall be possible to inhibit this feature for each preemptor.

7.2. Bus Preemption 7.2.1. Ten bus preemptors shall provide control for bus or other low-priority vehicles. Bus preemptors shall have lopriority and shall be overridden by railroad-fire-emergency veh

7.2.2. The preemptor shall be programmed to accept either a 6.25 pulse-per-second signal with a 50% duty a solid input to identify a bus preemptor call. Bus preemptor calls shall be capable of preemptor call memory and shall be served

7.2.3. Bus preemptor timing intervals shall be programmable from 0-255 in one second increments or 0-25.5 in ontenth second increments depending on the function.

7.2.4. A re-service time shall be provided to avoid excessive utilization of the same bus preemptor. If a call is received before the re-service time has elapsed, the bus preemptor shall not be re-serviced. If re-service time has nbeen entered then all phases with a call when leaving the bus preemption sequence shall be serviced before thepreemptor may be served again.

7.2.5. Bus preemptors shall provide delay, inhibit, and maximum time functions similar to those for railroad-fiemergency v

ed. These shall serve a

cals on selected phases upon e

mption to the

7.2.6. Bus preemptors shall p

b. Yellow c. Red

7.2.7. At the completion of the entrance red clearance, the bus preemptor shall advance to the hold green interval. During this interval, up to four permissive phases shall be selectable to remain green until the minimum hold time has elapsed and the bus preemptor c

7.2.8. It shall be possible to program the controller to allow concurrent phases to be serviced for a bus preemptor with only one phase selected as the hold interval pha

7.3. Preemption Safeguards 7.3.1. If a preemptor call is active when power is restored to a controller, the fault/voltage monitor output shall be setto FALSE, placing the intersection

and the preemptor duration time has elapsed.

7.4. Transit Signal Priority 7.4.1. The controller shall include a transit signal priority algorithm that provides for transit vehicle movemen

7.4.2. A check-in detector input shall be provided that se

7.4.4. A check-out detector input shall determine the departure of the transit vehicle. 7.4.5. Assignment of a single pulse from the c

requires TSP) shall be through EVP 1-4, for a controller with a C1 connector, or through Preemptor inputs 3 – 6, o

7.4.6. When under coordination the TSP sequence shall use alternate split times to accommodate transit vehwhile maintaining coordination.

8. TIME-BASED CONTROL & NON-INTERCONNECTED COORDINATION

additioal modules or software.

functios. The only required clock settings shall be the current time (hour, minute and s

possibl to set the number of hours that the local standard time is ahead or behind Greenwich Mean Time. 8.1.2. During normal operation, the TOD clock shall use the power line frequency as its time base. When power is removed, the time shall be mainta

Standard.

anothe controller, a computer or a system master.

vehicle while not skipping ph

A preemptor safety interlock shall be pro

er has been re

time reset input is TRUE.

8.1.5. The TOD clock shall automatically compensate for leap year and shall be programmable to automaticallswitch to daylight savings time.

8.2. Time-Based Control

8.2.1. Time-based control shall utilize a day plan program format. The month program shall consist of 200 programmable schedules, each assignable to one of sixteen day programs. Each day program shall consist of from 1 to 50 program steps which define a program for the entire day. Each program step shall be programmed with a starting time and an action plan number. The day plans shall also be assigned to days of the week and days

8.2.2. Time based control shall use action plans to assign: a. Coordination pattern number b.

d. Timing plan e. Vehicle detector diagnostic plan

8.2.3. Time based contro

b. System override c. Detector log

g. By-Phase functions - Pedestrian recall - Walk 2 enable - Vehicle extension 2 enable

- Max 2 enable

e. Special functions

- Max 3 enable

- Conditional service inhibit

- Phase omit

There shall be a minimum of 36 holid

prorams shall be capable of being set a

the following year.

It shall be possible to m

all be entered from the keybo

on-Interconnected Coord

A minimum of 200 time ba

be entered in any sp

g any other day-p

a. Day program assignment

b. Start time

c. Action plan

Selection of sys

ide the current telemetry or h

referened to a user selected reference time (sync reference), last event or last sync as selected from the keyboard. The sync reference time is that time at which all cycles shall be reset to zero. 8.3.4. If the sync r

occur whenever the present time is such that an even number of cycle length periods has occurred since the sync reference time.

9. DETECTORS

9.1. Detector Functions The controller shall provide a minimum of 64 vehicle detector inputs. Each input shall be assignable to any phase and

rammable as to detector functio

capable of opera

ian detector inputs

9.2. Detector Cross Switching

their assigned phases and their assigned cross switch phases. If the assigned phase is not green and the cross-switch phase is green, the detector shall place calls on the cross switch phase. If the assigned phase is omitted for any reason, the detector shall place calls on the cross switch phase.

9.3. Detector Types 9.3.1. Each vehicle detector shall be user-programmable to operate as one of the following 3 detector types:

Type 1: (GR

received be

recognized only if continuously present for a period equal to the programmed delay time AND the delayed signal is NOT extended. The first detection received when the phase goes green, whether present when green starts or received later, is recognized immediately. Detections received bthe first timeout of the extension interval are also recognized immediate

Type 2: (STOP BAR WIT

input is true when phase green starts the extension timer is reset while the input remains true. Whenthe detector input is removed the extension timer begins running. If another detector input is recbefore extension time expires, the extension timer is reset for the duration of the input and once agabegins timing when the input goes false. This action is rep

Vehicle detectors shall be capable of being assigned to a minimum of 16 speed detectors. Speed shall be oth one and two detector configurations. Speed shall be computed using a keyboard entered length and loop length for a one-detector configuration. When using two detectors, speed shall be a keyboard entered distance between detectors and travel time between detectors. OMMUNICATIONS Master Communications troller shall be capable of communicating with an on-street system master. This capability shall beparate telemetry module, which sh

ations. The telemetry module shall receive system master commands and data transmissions. In addition, ie controller status, data base and system detector information to the system master. Commands

a. Cycle, offset, a

c. Special function commands (minimum of four)

e. Time and date f. Request for local status g. Recall to Max

between controller and system mas

10.1.3. Status Data – The status of each of the following functions shall be transmitted to the system master in response to a local status request: a. Green and yellow status for all phases and overlaps b. Walk and pedestrian clearance status for all phases

d. Phase termination

h. Sync or transitioning status of coordinator

10.1.4. Split Reporting – The status of each of the following parameters shall be calculated on a per-cycle b

a. Actual time spent in each phase b. Time of day at end of cycle

d. Type of coordination operation e. Whether transitioning to

10.2.3. Parity and error checking s

The controller shall have the capability of supporting communications with traffic management systems using industandard protocols with the installation of appropriate optional software. At a minimum the controller shall have optional software to support the following protocols: a. CalTrans AB3418

data via vendor specific objects. These and all other objects supported by the controller shall be definein a standard MIB file.

The controller shall have the capability of supporti

10.5. External Clock

set its internal time of day clock.

c. NTCIP

i. Conflict flash status

j. Local flash statu

k. Preempt activity and calls

l. Volume and occupancy data from

m. Speed data from

n. Maintenance required (cabi

o. Status of two u

f. Cycle, offset, and split in effect during last cycle

g. Flash status if operation is Free

Upload/Download Capability –

tersection databa

ontroller operation. It shall

shall not require the inter

elemetry

Telemetry shall utilize TDM/FS

aybe leased lines (Type 3002, voice grade, unconditioned) or dedicated c

ications capability shall also be available.

The nominal transmitter output level sh

provided on the telemetry module to s

In te event of a telemetry failure, th

lf-synchronized for a number of cycles, w

ommunications Protocols

a. Port 1 SDLC for communications to other devices in the cabinet b. Port 2 Terminal port for communications with a computer for the purposes of uploading, downloadinupgrading the controller software

c. Port 3 Systems comm

master or

d. An option circuit board shall be available to expand communications by adding two additional serial communications ports ial communications sha

11. DIAGNOSTICS

11.1. General Diagnostics Features

standard feature and s

11.1.2. Automatic diagnostics shall verify memory, MMU compatibility programming, and microprocessor operation each time power is reapplied to th

microprocessor.

11.1.3. Operator initiated diagnostics shall allow the operator to verify proper operation of all

ications, keyboard, and display functions. Both manual and automati

tor Diagnostics

e-of-day controlled detector diagnostic

r no activity, maximum presence, and erratic output.

day basis. This shall allow varying the detector diagnostic intervals to c

11.2.3. If a detector i

a. Detector fail recall from 1

c. Disable the detector from calling or extending.

Unit (BIU) shall also include detection of watchdog, open and shorted loop, and excessive inductance change failure 12. LOGGING The controller sha

12.1. Detector Logging

12.1.2. The detector-logging interval shall be keyboard selectabl

12.1.3. Detector logging shall be capable of being enabled or disabled by time-of-day.

12.2. Detector Failure Logging

12.2.2. All detector diagnostic failures shall be recorded in the detector failure log including: no

12.1.1. The controller shall in

The controller shall include a detector failure log b

d detector failure events

city is exceeded at which time the oldest detecto

presence, erratic output, watchdog failure, open loop, shorted loop, and excessive inductance change. If a detector

12.2.3. Detector failure logging shall be capable of being disabled.

events or alarms. Once logged, events shall remain in the buffer until cleared or the log buffer capacity is exceeded at which time the oldest events shall be ov

12.3.2. At a minimum the following events shall be logged: communication failures, coordinatio

event shall be logged when an event or alarm returns to normal status.

12.3.4. Event logging shall be capable of being enabled or disabled for each category of event or alarm.

12.4.1. The controller shall accumulate phase utilization data, phase termination data and detector data for a numbeof cycles selectable by the operator.

12.4.2. The MOE log shall include the number of gap outs, force off

operating free, the log shall include the timing plan (1 – 4), the maximum in effect and the average phase maximum for each period.

12.4.5. Each log period shall record the number of times a phase was skipped and the number of times walk wasserved per phase.

user’s ID. It is necessary to log t

12.4.3. The MOE log shall in

FaLang translation system by Faboba