GreenWave v3.6 Firmware Release Notes - Peek Traffic

ATC Traffic Controllers 

Announcing Peek ATC Firmware v3.6 

Peek Traffic is pleased to announce the release of the Version 3.6 firmware for the ATC family of traffic 

controllers. This release of the firmware is intended for the non-CBD versions of the ATC controller, 

supporting the ATC-1000 and ATC-2000 traffic intersection controllers. This update adds screen support for 

32 overlaps and 64 detectors, as well as support for all NTCIP 1202 preemption objects and NYC-style traps. 

Release Date.................................................................................. August 18 th , 2010 

This firmware is designated ATC firmware Version 3.6, build 526, 

and is released for use in all field and production ATC-1000 and 

Contents: 

ATC-2000 Traffic Controllers. It is not intended for use in the 

ATC-3000 International traffic controller. 

Compatibility...................................... 2 

Installing the Firmware ...................... 3 

Delivery Methods 

New Features .................................... 7 

Issues Addressed............................ 14 

This firmware can be delivered to the controller in a couple of ways, Additional Documentation ............... 15 

either by loading the firmware file on a USB thumbdrive which is Technical Support............................ 15 

then plugged into the USB port on the front of the controller, or by 

connecting the controller to a laptop that has IQ Link and a copy of 

the firmware file aboard. The IQ Link connection can be made via an Ethernet connection to either of the 

Ethernet ports on the front of the controller (LOCAL or SYSTEM.) 

When using either of these methods, the name of the file to use to send the update to the controller is: 

Firmware 

File name 

3.6.526 natc_v006R526.bin 

The process to update a controller to the new firmware is described on the next page. 

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. 

Copyright © 2010 Peek Traffic Corporation. All rights reserved. 

p/n 99-545 

Revision 3 

9/29/2010

Compatibility 

In order to address some confusion about the various versions of firmware that are used on the ATC-1000 

and ATC-2000 controllers, we have here added a table of board-level firmware compatibility. The ATC family 

controllers run an application known as ‘GreenWave’, also called the traffic control firmware. However, there 

are other pieces of firmware that run on these controllers. Each controller has three subassemblies, each 

with its own firmware: the Main (or ‘Host’) board, the Field Input/Output board (FIO), and the Power Supply 

Unit board (PSU). In order for the entire controller to operate correctly, the various firmwares must be at the 

correct versions so that they can function together successfully, and successfully run the hardware. This 

table describes the required firmware for each of the recent releases of GreenWave: 

Current Release 

GreenWave Version: 

Build 401 and 

below 

Build 402 to 

Build 420 

Version 3.5 

(Build 421+) 

Version 3.6 

(Build 526) 

Linux Kernel 2.6.20.14 1 2.6.20.14 2.6.20.14 2.6.20.14 

Boot Loader version 1.1.4 2 1.1.4 1.1.4 1.1.4 

Main board firmware (MAIN) 1.0.5 and below 3 1.0.6 1.0.6 1.0.6 (1.0.9) 

Field I/O firmware (FIO) 1.0.5 and below 1.0.6 1.0.6 1.0.6 (1.1.0) 

Power Supply board firmware 

(PSU) 4 Not applicable 1.0.3 [1.0.5] 1.0.3 [1.0.5] 5 1.0.4 [1.0.5] 

I/O Board: TS2 Type 1 Supported Supported Supported Supported 

I/O Board: TS2 Type 2 

(Version 2) 6 Not supported Supported Supported Supported 

I/O Board: TS2 Type 2 

(Version 3) 6 Not supported Not supported Not supported Supported 

I/O Board: HMC-1000 Not supported Not supported Not supported Not supported 

I/O Board: LMD 40 Not supported Not supported Not supported Not supported 

D Module: Traconex Not supported Not supported Not supported Not supported 

D Module: LMD9200 Not supported Not supported Not supported Not supported 

D Module: Closed Loop Not supported Not supported Not supported Not supported 

D Module: Multisonix 820A Not supported Not supported Not supported Not supported 

The current version information for all of these pieces of firmware are visible from the front panel of the 

controller by powering up and navigating to the Revision Information screen: Main Menu > 1. Status > 

5. Revisions for the SOFTWARE (GreenWave) version, Linux Kernel, and Boot Loader information, and 

-MNU > 6.REVISION INFO for the board level firmware information. 

Note: If you find that you need board-level firmware to be updated, contact the Peek Tech 

Support team (See page 15) and request additional guidance on performing the updates. 

1 The displayed Linux Kernel versions reflect the open source version that was used as the baseline. Changes made are 

indicated by the version release date (rather than the version number itself) as displayed on the ATC revision information 

screen. During the indicated generations of GreenWave firmware, there were no edits to the kernel version delivered with 

the ATC controllers that impacted any of the I/O or D Module versions, nor impacted the operation of GreenWave. Impacts 

on some functions, such as support for external modems, did change during this period because of Kernel release versions, 

but those will be covered in a separate tech note. 

2 Boot Loader versions reflect the open source version U-Boot software that was used as the baseline. Changes made are 

indicated by the version release date (rather than the version number itself) as displayed on the ATC revision information 

screen. During the indicated generations of GreenWave firmware, there were no edits to the boot loader delivered with the 

ATC controllers that impacted any of the I/O or D Module versions, nor impacted the operation of GreenWave. 

3 MAIN and FIO firmware under Greenwave 401 and below can not be updated via the USB port. Factory update required for 

those versions. 

4 The power supply board cannot be updated via the USB port. PSU firmware updates can only be performed at the factory. 

5 Versions in parentheses indicate a possible upgrade. Square brackets ( [ ] ) indicate a required upgrade. 

6 TS2 Type 2 boards shipped prior to 9/27/2010 were version 2. TS2 Type 2 boards shipped on 9/27/2010 or later are Version 

3 I/O boards. 

Release Notes: ATC-1000/2000 v3.6 Firmware Release Notes 


Page 2 of 15 

99-545, Rev 3

Installing the Firmware 

Although updates to the firmware can be performed in the field, it is highly recommended that firmware 

updates only be performed on the test bench. When a firmware update is performed, the intersection must 

spend a short period in Flash mode until the traffic engine can successfully restart with the new configuration 

in place. With these facts in mind, the following methods can be used to update the firmware on a Peek 

ATC-1000 or ATC-2000 controller. 

Database Update 

Before moving your controller from Version 3.5 to Version 3.6 firmware, we recommend that you back up 

your controller’s database, either to USB thumbdrive, to IQ Link or into IQ Central. To back the database up 

to a thumbdrive, simply plug the USB device into the port on the front of the controller during normal 

operation and use the USB Device menu to choose option 2. DATABASE->USB. If you plan to back up the 

database using IQ Link or IQ Central, simply connect to the controller the way you normally do with these 

software packages and retrieve the current database settings from the device. 

The update will modify the data structures in the ATC database. The update will automatically store your 

current database settings to flash memory, and after the firmware is updated, it will automatically attempt to 

retrieve the old database. Normally, it should have no problem doing this. If there is a problem with the 

restoration of the database, the update will restore what it can, and then show a message upon startup that 

some of the database was not restored. It will ask the user to acknowledge this message by pressing 

CLR/ESC, and then it will log exactly what happened to the Controller Message Log (Main Menu > 4.Logs 

>1.Controller Message Log). If, on the other hand, there are no problems with the restoration of the 

database, the controller will start up as it always does, and immediately display the Timing Status screen. 

Restoring the Database Manually 

If this automatic restore does not work as described above, you have the option to restore your database 

from the USB thumbdrive, IQ Link or IQ Central backup you made before you attempted the firmware update. 

This can be done by installing a default database after you update the firmware (Main Menu > 3.System 

Maintenance > 1.Database Utilities > 2.Load 8ph 2r with Coord/Preempt), and then loading the backup 

database back into the controller. This will restore all of the controller’s prior settings into an updated 

database structure. Again, during the restore, if there are any problems restoring particular blocks of the 

database, the controller will report the error on the screen and also add a message to the Controller Message 

Log. 

Updating Firmware From a Thumbdrive 

Follow these steps to update the controller firmware using a USB thumbdrive. 

1. Copy the firmware file to the USB thumbdrive from a PC. 

2. Take the USB drive to the controller. 

3. Press MNU on the controller keypad to enter the menu system 

4. Press 3 to enter the System Maintenance menu 

5. Press 3 to enter Diagnostics Mode 

Important 

Proceeding past this point will require the intersection to be placed 

in Flash mode before it can again resume normal operation. 

6. Verify that you wish to enter Diagnostics Mode by pressing the NXT button. 

7. Choose option 6 to enter the Update Firmware screen 



Page 3 of 15 

99-545, Rev 3

ATC FW Loader v2.3 

Waiting for USB 

Listening on ETH 

eth0: 128.2.60.198 

eth1: 192.168.60.199 

Figure 1 – Firmware Loader screen – Waiting for the USB drive 

8. Plug the USB thumbdrive into the USB port on the front of the traffic controller. 

9. After a few seconds, the display will switch to a list of the firmware files that are available on the drive. 

Select FW File: 

natc_v005R106.bin 




> natc_v006R526.bin 

ATC v3.6 firmware update file 

Figure 2 – Choose the firmware to load from the USB drive 

10. Use the green up and down arrow keys on the controller keypad to move the arrow cursor (‘>’) on the 

list, until it points to the firmware you wish to load. 

11. Press the ENT button to select the file. When the firmware is done loading, the screen will ask you to 

remove power and restore it so that the controller can restart and load the selected program. 

12. Upon restart, check to see if the database restore completes successfully. If the database only restores 

partially, you will see an error message on the startup screen. Otherwise, the controller will start up as 

usual and go to the Timing Status display. For more information on database restoration, you can refer 

back to the “Database Update” section (on page 3.) 



Page 4 of 15 

99-545, Rev 3

Using IQ Link 

Follow these steps to update the controller firmware using IQ Link. 

1. Copy the firmware file to the PC where IQ Link is installed (or the file should be available at a network 

location from that computer.) 

2. Attach an Ethernet cable from the PC to the Local port on the front of the traffic controller. 

3. Press MNU on the controller keypad to enter the menu system. 

4. Press 3 to enter the System Maintenance menu 

5. Press 3 to enter Diagnostics Mode 

Important 

Proceeding past this point will require the intersection to be placed 

in Flash mode before it can again resume normal operation. 

6. Verify that you wish to enter Diagnostics Mode by pressing the NXT button. 

7. Choose option 6 to enter the Update Firmware screen 

ATC FW Loader v2.3 

Waiting for USB 

Listening on ETH 

eth0: 128.2.60.198 

eth1: 192.168.60.199 

Figure 3 – Firmware Loader screen – Waiting for the IQ Link Ethernet connection 

8. After logging into IQ Link, access the ATC Firmware Loader dialog box, in one of these three ways: 

By selecting Controller firmware update from the File menu. 

Select Phase 2 from the Utils menu, and click on CU Firmware Update to open the Firmware Loader 

dialog box. 

Click the Firmware Download button on the Main Window Toolbar ( ) 

Figure 4 – Firmware Load Dialog Box 

9. Enter the controller IP address in the Controller IP field (‘eth1’ is the address for the LOCAL port). 

10. Select the firmware version to send to the controller by clicking the Select Firmware File button. The 

Firmware File window will automatically open the directory that contains files of the correct type. 



Page 5 of 15 

99-545, Rev 3

11. Select the firmware update file from the Select Firmware File window, and click OPEN. Selecting an 

invalid file type will cause the update button to become inactive and the label will change to ‘Invalid 

Firmware File Selected’. Notice that the attributes of the selected file will be reflected in the File Size, 

File Selected, MD5SUM field, and the Update Button label on the Firmware Download Dialog Box. 

12. Some applications may require verification of the MD5SUM code displayed in the Download Dialog Box, 

against the code supplied with the update. If the code displayed does not match the code supplied with 

your Firmware update, contact your Peek Distributor or the Peek Traffic Technical Support Department. 

13. Click the Update Button to begin the update procedure. You should see a status bar that shows the 

progress of the update. 

If the controller is not ready, you will receive the message shown below in Figure 5, advising that 

IQ Link could not connect to the controller. Repeat steps 1, 2, and 3 above and verify that the IP 

address and Port information are correct. Consult your controller manual if the problem persists. 

Figure 5 – ‘Could not connect’ message displayed if the controller is not ready 

14. When the update is completed successfully, the message box, shown in , will appear to advise that the 

‘Operation Completed Successfully’. Click OK. 

Figure 6 – Update is complete 

15. When the firmware is done loading, the controller screen will ask you to remove power and restore it so 

that the controller can restart and load the selected program. 

16. Upon restart, check to see if the database restore completes successfully. If the database only restores 

partially, you will see an error message on the startup screen. Otherwise, the controller will start up as 

usual and go to the Timing Status display. For more information on database restoration, you can refer 

back to the “Database Update” section (on page 3.) 



Page 6 of 15 

99-545, Rev 3

New Features 

Version 3.6 of the ATC-1000/ATC-2000 firmware is the second full release of the firmware for these products. 

It includes quite a few new features and capabilities. 

Additional Overlaps from the Front Panel 

We have added the ability to program up to 32 overlaps from the front panel screen. All of the 32 overlaps 

have been available since version 3.5, but only overlaps 1 through 4 could be programmed from the front 

panel. (Overlaps 5 through 32 were previously only available through IQ Link. ) Now, the Overlaps screens 

include all of the fields to program all 32 overlaps: 

2.2.0.1.28 VEH OVL CONFIG PG28of32 

OVERLAP 28 

---------------------------------------- 

1 1 1 1 1 1 1 

1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 

PARENTS X X 

MODIFIER X 

TRAIL GREEN ... 0 

TRAIL YELLOW .. 3.0 

TRAIL RED ..... 0.0 

Figure 7 – Overlap Screen (Page 28 of the available 32) 

One other change was made on this screen. Previously, there was an available overlap TYPE value, but that 

setting has been made read-only in the front panel interface to support the new NTCIP 1202 standard. 

Additional Detectors from the Front Panel 

(Case #5103) Ability to program up to 64 vehicle detectors from the front panel (detectors 33 through 64 were 

previously only available through IQ Link). The Vehicle Detectors screens (Main Menu > 2.Programming > 

5.Detectors > Commands 1 through 4 for all of the vehicle detector screens) now display the parameters for 

all 64 of the available detectors: 

2.5.1.4 VEH DETECTOR OPTIONS PG 4of 4 

4 5 5 5 5 5 5 5 5 5 5 6 6 6 6 6 

DET NO. 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 

OPTION: 

CALL..... 

QUEUE.... 

ADD INIT. 

PASSAGE.. 

RED LOCK. 

YEL LOCK. 

OCC DET.. 

VOL DET.. 

RESET.... 

Figure 8 – Vehicle Detector Options 

Use the DWN– button to step to the next screen in any of these areas. 



Page 7 of 15 

99-545, Rev 3

Detector Status Indicates Recall States 

Detector status displays now indicate four states on the Controller Runtime Status screen: 

no call (blank) 

physical call (‘C’) 

minimum recall (‘m’) 

Max recall (‘M’) 

1.1.1 TS2 Tue 17-Aug-2010. P1:OK 

TIMING STATUS 08:53:22 FFFF 

R1 02 EXT 00.0 M1 005 

DW 

PRE INP 

R2 06 GRN REST 

PRE KBD 

DW 

R3 RED REST 

DW 

R4 RED REST 

DW 

CALL STATUS 1111111 

1234567890123456 CRD CMD:254 

VEH C C mC SYS CMD: 0 

PED M m TOD CMD: 1 

PHS 

Figure 9 – Runtime Status screen showing new detector status tags 



Page 8 of 15 

99-545, Rev 3

Full Featured Transit Signal Priority Released for Operation 

In the Version 3.5 firmware, a set of Transit Signal Priority (TSP) fields and programming screens were made 

available, but we recommended that they not be used at that time. We have completed extensive live onstreet 

testing of the TSP functionality and with Version 3.6, can announce that the ATC-1000/2000 TSP 

engine is robust, extermely adaptable, stable, and reliable. 

(MAIN MENU > 2.PROGRAMMING > 8.TRANSIT SIGNAL PRIORITY > 1.UNIT PARAMETERS) 

2.8.1 TRANSIT UNIT PARAMETERS PG 1 OF 1 

TSP ENABLE: 

OFF 

DEFAULT COORD PATTERN: 000 (0-253) 

SYSTEM TSP ACTION PLAN: 00 (0-48) 

DEFAULT TSP ACTION PLAN: 00 (0-48) 

UTILIZATION PERIOD: 00 (0-24) 

Figure 10 – TSP Unit Parameters screen 

The Unit Parameter screens show the global TSP values. The individual transit runs are defined on a matrix 

of screens that describe up to eight runs for up to eight run configurations. The Transit Run Configuration 

screen shown in Figure 11 on page 9 is a typical example of a TSP setup screen. 

(MAIN MENU > 2.PROGRAMMING > 8.TRANSIT SIGNAL PRIORITY > 4.RUN CONFIGURATION) 

2.8.4 TRANSIT RUN CONFIGURATION 1 OF 8 

Number keys select Run Configuration 

Run 1 of 8 Page Up/Down for more 

Delay 000 Ext 000 Fail 000 Reserve 00000 

11111111112222222222333 

Ph/Ivl 12345678901234567890123456789012 

Calls X X 

Q Jump X 

Skip X X 

Shift X 

Reduce XXXX 

Reserve X 

Figure 11 – TSP Run Configuration screen (Run 1, Config 1) 

The full TSP environment and how to program Transit Priority runs is described in Chapter 9 of the ATC-1000 

Operating Manual. 



Page 9 of 15 

99-545, Rev 3

Support for All NTCIP 1202 Preemption Data 

The Preemption programming environment has been extensively modified in the Version 3.6 firmware as 

well. Previously, the preemption screens were simply six screens, one for each programmable run, with the 

following parameters available for programming: 

2.6.1 PREEMPT 1 PG 1 of 6 

NON-LOCK CALL.. OVERRIDE FL... 

FLASH DWELL....X PRTY OVERRIDE. 

1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 

TRACK Ph. X X 

DWELL Ph. X X 

DWELL Pd. 

EXIT Ph. 

EXIT Pd. 

DELAY......... 0 TRACK GREEN... 5 

MIN GREEN..... 1 DWELL GREEN... 1 

MIN WALK...... 1 MIN DURATION..00040 

ENT PED CLEAR. 1 MAX PRESENCE..00060 

RED DWL TIME.. 0 LINK.......... 0 

Figure 12 – Version 3.5 Preemption programming screen 

In the Version 3.6 firmware, Preemption now has its own menu with two available sets of screens, the first for 

parameters that affect the entire run, the second so one can program the run’s intervals. 

2.6 PREEMPTION MENU 

1. CONTROL AND TIMING 

2. PHASE PEDESTRIAN OVERLAPS 

Figure 13 – Version 3.6 Preemption Menu 

The Preemption Control and Timings screens (one for each of the available preemption runs) allow one to 

program the overall behavior of each run. This is similar to the basic preemption run programming screen 

that was available in version 3.5. 

2.6.1 CONTROL AND TIMING PG 1 of 6 

NON-LOCK CALL. 

PRTY OVERRIDE. 

OVERRIDE FL...X 

FLASH DWELL...X 

LINK.......... 0 DELAY......... 0 

MIN DURATION..00040 MAX PRESENCE..00060 

MIN GREEN..... 2 MIN WALK...... 2 

ENT PED CLEAR. 2 ENT YEL CHNG.. 0 

ENT RED CLEAR. 0 

TRACK GREEN... 5 TRACK Y CHNG.. 0 

TRACK RED CLR. 0 

DWELL GREEN... 1 DWELL RED..... 0 

Figure 14 – Version 3.5 Preemption programming screen (example) 

The screen has been reorganized, with the Track, Dwell, and Exit phase definitions being moved over to the 

other preemption programming screens. New to this screen are these parameters: 

ENT YEL CHNG — The Entry Yellow Change time is a value in seconds between 0 and 255 seconds that 

controls the timing for the Yellow portion of a phase that has been interrupted by a preemption call. The 



Page 10 of 15 

99-545, Rev 3

transition to the preemption run will display the Yellow signal for either this value or the parent phase’s own 

yellow clearance time, whichever is less. 

ENT PED CLEAR — Enter Pedestrian Clear Time is a value in seconds between 0 and 255 seconds that 

controls the timing for a normal walk that has been terminated by a preemption call. The transition to the 

preemption run will display the walk signal for either this value or the ped phase’s own pedestrian clearance 

time, whichever is less. 

TRACK Y CHNG — The Track Clear Yellow Change time is a value in tenths of a second (0.0 to 25.5 

seconds). Whichever is less between this value and the phase’s own yellow change time determines the 

yellow timing for a track clearing movement. (Which phases are track phases is determined on the TRACK 

Ph row.) 

TRACK RED CLR — The Track Red Clear time is a value in tenths of a second (0.0 to 25.5 seconds). 

Whichever is less between this value and the phase’s own red clearance time determines the red timing for a 

track clearing movement. (Which phases are track phases is determined on the TRACK Ph row.) CAUTION: 

DWELL GREEN — The Dwell Green time is a value in seconds between 0 and 255 seconds that controls 

the timing for the main green portion of the preemption run. Important – Note that if this value is left at zero 

(0), even if the preemption run is enabled and called, the run will not work. A non-zero time must be entered 

here for the run to function. 

DWELL RED — This was previously labeled as RED DWL TIME, but it has the same function. When set to a 

non-zero value, when there are no track phases defined in the preemption run, this value will cause any main 

street phases that were programmed as dwell phases to terminate. The intention of this function is to avoid 

the “left turn trap” scenario. 

The second option on the Preemption Menu is the Phases, Peds and Overlaps definition screens for each of 

the preemption runs. Here is an example: 

2.6.2 PHASES/PEDS/OVERLAPS PG 1 of 6 

1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 

TRACK Ph. X X 

TRACK OV. 

DWELL Ph. X X 

DWELL Pd. X X 

DWELL OV. 

CYCLE Ph. 

CYCLE Pd. 

CYCLE OV. 

EXIT Ph. X X 

EXIT Pd. 

Figure 15 – Preemption Phases/Peds/Overlaps screen 

This screen provides five more interval type options for each phase: Track Overlap, Dwell Overlap, Cycling 

Phase, Cycling Ped, and Cycling Overlap. 



Page 11 of 15 

99-545, Rev 3

Updated Status Menus with Additional Status Screens 

Previously, the Status menu included all of the status screens from the main list: 

1 STATUS MENU 

1. CONTROLLER 8. SDLC & FIO STATUS 

2. INPUTS 9. ALARMS 

3. OUTPUTS 0. OVERLAPS 

4. COORDINATION A. MMU 

5. TIME OF DAY B. T.S.P 

6. PREEMPTION C. ABS ZERO 

7. DETECTORS D. REVISIONS 

Figure 16 – Old Status Menu in Version 3.5 

The old Status menu has been replaced with: 

1 STATUS MENU 

1. CONTROLLER 

2. INPUTS/OUTPUTS 

3. ALARMS 

4. MMU 

5. REVISIONS 

Figure 17 – New Status Menu in Version 3.6 

The status menu now includes several submenus, where one can access all of the old status screens, plus 

several new ones. On the Controller Status menu, we have nine options: 

1.1 CONTROLLER STATUS MENU 

1. RUNTIME STATUS 

2. COORDINATION 

3. TIME OF DAY 

4. PREEMPTION 

5. DETECTORS 

6. T.S.P 

7. OVERLAPS 

8. SEQUENCING 

9. TEXAS DIAMOND 

Figure 18 – Controller Status submenu 

What was previously called the ‘Controller’ status menu is now called the RunTime Status menu and is the 

default status screen for the ATC controller, and the screen that appears whenever anyone presses the HME 

button from anywhere in the menu system. The Coordination, Time of Day, Preemption, Detectors, TSP, and 

Overlaps status screens were all part of the main Status screen in the previous firmware. The Sequencing 

status screen is new in Version 3.6. 



Page 12 of 15 

99-545, Rev 3

1.1.8 SEQUENCE STATUS PG1OF1 

Loaded Plan : 1 Loaded Seq : 1 

Sequence Data 

R1 Len 4: 1 2 3 4 

R2 Len 4: 5 6 7 8 

Barrier Numbers 

R1 Len 4: 1 1 2 2 

R2 Len 4: 1 1 2 2 

Barrier bits 

B1: 0x33, B2: 0xCC, 

Current Phase On in Ring 

R1: 2, R2: 6, R3: 0, R4: 0, 

Figure 19 – Sequence Status screen 

As you can see from the sample screen above, the Sequence Status screen displays the intersection status 

in a traditional NEMA phase/ring/barrier layout, as well as indicating the current phase that is ON in each 

ring. 

The Alarms, MMU and Revisions status commands on the new Status screen are the same as in the 

previous firmware. The ABS Zero status screen that was previously available on the Status menu has now 

been moved to the bottom of the Programming > Unit Configuration menu (Option 8, not visible). 

The second option on the new Status menu is the Inputs/Outputs menu, which shows three options, all from 

the old Status screen: 

1.2 INPUTS/OUTPUTS STATUS MENU 

1. INPUTS 

2. OUTPUTS 

3. SDLC & FIO 

Figure 20 – Inputs/Outputs Status Menu 



Page 13 of 15 

99-545, Rev 3

Issues Addressed 

Version 3.6 of the ATC-1000/ATC-2000 firmware addressed the following issues that were reported in 

previous releases: 

Table 1 – Issues addressed in the Version 3.6 firmware 

Issue Resolution Case # 

Min & Max Recall displays and 

operation 

TOD Actions screens incorrectly 

labeled actions as ‘events’ 

Vehicle calls were not always 

being correctly reported on the 

controller’s main status screen 

Phase recalls not being stored 

properly when programmed from 

the controller front panel 

Inconsistent recovery method 

from TSP operation 

There were some reports that Min and Max recalls 

programmed from the front panel interface were not 

being serviced. This has been corrected and the 

correct operation has been verified. The addition of 

the ‘M’ and ‘m’ indicators on the Runtime Status 

display are an extra assist in verifying correct 

operation. 

The labels on the TOD Action screens now correctly 

call the items ‘actions’ 

The Timing Status screen has been updated to not 

only correctly show vehicle call status, but also to 

indicate max and min recalls 

Recalls placed on individual phases were being 

stored one phase to the left of the correct location. 

Recall assignments are now being stored correctly 

from the front panel interface. (Recall programming 

using IQ Link was never affected by this issue.) 

A TSP call resulting in Green extension on a main 

street was reported to generate both negative and 

positive recover methods in subsequent cycles after 

the TSP call has been removed. This has been 

corrected so that the user defined recovery method 

will always be used. 

Additional minor bug fixes were included to improve the front panel interface consistency, as well as 

improvements to data consistency checking, the firmware update tools, data logging, USB database 

transfers, and the management of flash memory. 

5059 

5239 

5290 

5749 

6086 



Page 14 of 15 

99-545, Rev 3

Additional Documentation 

These documents provide useful information about ATC-1000 or ATC-2000 controllers and other related 

products : 

Document 

Part Number 

ATC-1000 Operating Manual 81-1285 

IQ Central Operating Manual 81-1105 

IQ Central Release Notes 99-427 

IQ Central Administrator’s Guide 81-1317 

IQ Link Operating Manual 81-1202 

IQ Link Release Notes 99-490 

Additional information is also available at the Peek Traffic website: www.peektraffic.com 

Technical Support 

This contact information will connect you with the technical support staff of Peek Traffic Corporation, should 

you require additional help concerning the ATC-1000 and ATC-2000 traffic controllers. 

Peek Traffic Corporation - Technical Support Center 

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 



Page 15 of 15 

99-545, Rev 3

GreenWave v3.6 Firmware Release Notes - Peek Traffic

Create successful ePaper yourself

Delete template?

Save as template?