Module 37 - A208

A208: Using the ATC 5401 Application Programming Interface Standard to Leverage ITS Infrastructures

HTML of the PowerPoint Presentation

(Note: This document has been converted from a PowerPoint presentation to 508-compliant HTML. The formatting has been adjusted for 508 compliance, but all the original text content is included, plus additional text descriptions for the images, photos and/or diagrams have been provided below.)

Slide 1:

(Extended Text Description: Slide 1: Welcome - Graphic image of introductory slide. A large dark blue rectangle with a wide, light grid pattern at the top half and bands of dark and lighter blue bands below. There is a white square ITS logo box with words "Standards ITS Training" in green and blue on the middle left side. The word "Welcome" in white is to the right of the logo. Under the logo box are the words "RITA Intelligent Transportation Systems Joint Program Office.")

Slide 2:

Welcome

Ken Leonard, Director

ITS Joint Program Office

Ken.Leonard@dot.gov

(Extended Text Description: Intro Slide: Screen capture snapshot of RITA website - for illustration only. Below this image is a link to the current website: https://www.its.dot.gov/pcb - this screen capture snapshot shows an example from the RITA website from April 2013. At the top of the page it shows the RITA logo with the text U.S. Department of Transportation Research and Innovative Technology Administration - Intelligent Transportation Systems Joint Program Office - ITS Professional Capacity Building Program/Advanced ITS Education. Below the main site banner, it shows the main navigation menu with the following items: About, ITS Training, Knowledge Exchange, Technology Transfer, ITS in Academics, and Media Library. Below the main navigation menu, the page shows various content of the website, including a graphic image of professionals seated in a room during a training program. A text overlay has the text Welcome to ITS Professional Capacity Building. Additional content on the page includes a box entitled What's New and sections entitled Available E-Training (free), Free ITS Training and T3 Webinars. Again, this image serves for illustration only. The current website link is: https://www.its.dot.gov/pcb)

ITS PCB Home

(Note: There is additional text attached to this slide that includes the following introductory information from Ken Leonard):

"ITS Standards can make your life easier. Your procurements will go more smoothly and you'll encourage competition, but only if you know how to write them into your specifications and test them. This module is one in a series that covers practical applications for acquiring and testing standards-based ITS systems.

I am Ken Leonard, director of the ITS Joint Program Office for USDOT and I want to welcome you to our newly redesigned ITS standards training program of which this module is a part. We are pleased to be working with our partner, the Institute of Transportation Engineers, to deliver this new approach to training that combines web based modules with instructor interaction to bring the latest in ITS learning to busy professionals like yourself.

This combined approach allows interested professionals to schedule training at your convenience, without the need to travel. After you complete this training, we hope that you will tell colleagues and customers about the latest ITS standards and encourage them to take advantage of the archived version of the webinars.

ITS Standards training is one of the first offerings of our updated Professional Capacity Training Program. Through the PCB program we prepare professionals to adopt proven and emerging ITS technologies that will make surface transportation safer, smarter and greener which improves livability for us all. You can find information on additional modules and training programs on our web site ITS PCB Home

Please help us make even more improvements to our training modules through the evaluation process. We look forward to hearing your comments. Thank you again for participating and we hope you find this module helpful."

Slide 3:

Slide 4:

A208:

Using the ATC 5401 Application Programming Interface Standard to Leverage ITS Infrastructures

Slide 5:

Instructor

Ralph W. Boaz

President

Pillar Consulting, Inc.

San Diego, CA, USA

Slide 6:

Target Audience

• Engineering Staff
• TMC/Operations Staff
• System Developers
• Software Developers
• Manufacturers
• Private and Public Sectors Users

Slide 7:

Recommended Prerequisite(s)

• I101: Using ITS Standards: An Overview
• A101: Introduction to Acquiring Standards-based ITS Systems
• A102: Introduction to User Needs Identification
• A201: Details On Acquiring Standards-based ITS Systems
• A202: Identifying and Writing User Needs When ITS Standards Do Not Have SEP Content
• A103: Introduction to ITS Standards Requirements Development

Slide 8:

Recommended Prerequisite(s) (cont.)

• A203: Writing Requirements When ITS Standards Do Not Have SEP Content
• C101: Introduction to the Communications Protocols and Their Uses in ITS Applications
• A207a: Building an ITS infrastructure Based on the ATC 5201 Standard Part 1 of 2
• A207b: Building an ITS infrastructure Based on the ATC 5201 Standard Part 2 of 2

Slide 9:

Curriculum Path (Non-SEP)

(Extended Text Description: This slide contains a graphic illustration indicating the sequence of training modules that lead up to this course. Each module is represented by a box with the name of the module in it and arrows showing the logical flow of the modules. There are 8 boxes in total; two rows of 3 boxes and a row with 2 boxes. The first box is labeled "I101 Using ITS Standards: An Overview." An arrow from this box connects it to a box labeled "A101 Introduction to Acquiring Standards-Based ITS Systems." An arrow from this box connects it to a box labeled "A102 Introduction to User Needs Identification." An arrow from this box connects it to a box located at the start of the next row labeled "A201 Details on Acquiring Standards-based ITS Systems." An arrow from this box connects it to a box labeled "C101 Introduction to Communications To Comm. Protocols and Their Use in ITS Applications." An arrow from this box connects it to a box labeled "A207a Building an ITS Infrastructure Based on the ATC 5201 Standard Part 1 of 2." An arrow from this box connects it to a box located at the start of the next row labeled "A207b Building an ITS Infrastructure Based on the ATC 5201 Standard Part 2 of 2." An arrow from this box connects it to a box labeled "A208 Using the ATC 5401 API Standard to Leverage ITS Infrastructures." The last box is highlighted indicating that it represents the current module in the series.)

Slide 10:

Learning Objectives

1. Identify the features of the ATC 5401 Application Programming Interface (API) Standard
2. Describe the ATC 5401 Architecture
3. Describe how the ATC 5401 Standard works with other ITS Standards
4. Specify API Software for system and equipment procurements

Slide 11:

Learning Objective #1 - Identify the Features of the ATC 5401 Application Programming Interface (API) Standard

• Sharing resources of the controller and transportation field cabinet system
• Structure of the ATC 5401 Standard
• Features for API Software

Slide 12:

Learning Objective #1

Uses for ATC Controller Units Identified

• Traffic Signal Control/Traffic Management
• Transit/Light Rail Priority
• Emergency Management
• Lane Use
• Red Light Enforcement
• Speed Monitoring/Enforcement
• Access Control
• Advanced Traveler Information Systems (ATIS)
• Data Collection Systems / Data Distribution
• Connected Vehicle (CV) Applications
  • Safety
  • Eco Driving

Slide 13:

Learning Objective #1

Sharing Resources of the Controller and Transportation Field Cabinet System (TFCS)

(Extended Text Description: This slide is entitled "Sharing Resources of the Controller and Transportation Field Cabinet System (TFCS)." The intent of the slide is to illustrate that the field cabinet contains various equipment. There are two large graphics. The leftmost graphic is the aluminum looking cabinet. The cabinet has a door with a horizontal handle on the left side of the cabinet and two vent slots in the center top. The cabinet is about 2.5 times high as it is long. It is about 40% of the slide height. Above it is the word "Housing." The rightmost graphic is an enlargement of the aluminum cabinet showing the contents of the cabinet. It is about 70% of the slide height. Inside the cabinet are six labeled cuboids that extend almost the width of the cabinet and evenly distributed vertically. Starting from the top the cuboids are labeled "Input," "Controller," "Outputs," "Monitoring," "Power Supply," and "Internal Bus." There is a large left bracket between the cabinet graphic and the enlargement emphasizing that the right graphic represents the contents of the cabinet.)

Graphics: Ralph W. Boaz

Slide 14:

Learning Objective #1

Basic TFCS Operation

(Extended Text Description: This slide is entitled "Basic TFCS Operation." On the upper right side of the slide is a graphic of an intersection. It is depicted as two two-lane roads intersecting perpendicularly North/South and East/West (it is assumed that the top of the slide is North) in the shape of a cross that is approximately 20% of the height and width of the slide. There is a centerline on each road to differentiate the northbound lane from the southbound lane and the eastbound lane from the westbound lane. The area where the roads cross (center of the cross) is blank (no lines running through it). In each lane representing the southbound, northbound, westbound, and eastbound approaches to the intersection, there are rectangles extending across the width of the lane (total four lanes). The rectangles have one edge at the point where the blank center area begins and extends back into the lane about 1 ½ times their width. This graphic is labeled "Field Sensors." In the lower right of the slide is a graphic of a traffic signal mast arm. On the mast are three traffic signal heads. This graphic is labeled "Field Displays." On the left side of the slide are four cuboids each the same size and about 5 times wider than their height or depth. They are evenly spaced and aligned with each other. They are labeled top to bottom "Inputs, Controller, Outputs and Monitoring." There are arrows showing the flow of information through the TFCS. There is an arrow extending out of the top of the Field Sensors graphic into the Inputs cuboid. There is an arrow extending out of the bottom of the of the Inputs cuboid to the Controller cuboid. There is an arrow extending out of the Controller cuboid to the Outputs cuboid. There is an arrow extending out of the Outputs cuboid to the Monitoring cuboid. There is a double arrow extending from the left side of the Monitoring cuboid back up to the left side of the Controller cuboid. This line has a label associated with via a dotted line. The label says "Controller/Monitor Communications Used in NEMA TS 2 and ITS Cabinets." There is a line extending from the ride side of the Outputs cuboid to the top of the Field Displays graphic.)

Graphics: Ralph W. Boaz

Slide 15:

Learning Objective #1

Sharing Resources of the Controller and TFCS

(Extended Text Description: This slide, entitled "Sharing the Resources of the Controller and TFCS," contains a graphic illustrating a TFCS being used in multiple applications areas. There is an aluminum looking cabinet in the center of the slide. The cabinet has a door with a horizontal handle on the left side of the cabinet and two vent slots in the center top. The cabinet is about 2.5 times high as it is long. It is about 20% of the slide height. To the left, to the right, lower left and lower right of the cabinet graphic are four rounded rectangles. There are double arrows between the cabinet and the rounded rectangles. The left and right rounded rectangles are about 25% of the height and 25% of the width of the slide. The lower rounded rectangles are about 15% the height of the slide and 25% of the width of the slide. The rounded rectangle to the left has a label "Intersection Control" on the inside top. The remainder of the rounded rectangle is a graphic of a roadway intersection. The view of the intersection is such that two traffic signals are shown. The rounded rectangle to the right has a label "Ramp Metering" on the inside top. The remainder of the rounded rectangle is a graphic of freeway on-ramp. A freeway is depicted and a traffic signal with a sign "One Vehicle Per Green" is shown at the edge of the onramp. The rounded rectangle to the lower left has a label "Connected Vehicle V2I" on the inside top. The remainder of the rounded rectangle is a graphic of a 2-door sedan sitting next to a TFCS. The rounded rectangle to the lower right has a label "Other Application" centered within the rectangle with no other graphics included. In the upper part of the slide is a square about 20% the height of the slide representing a LCD screen and keypads portion of a transportation controller.)

Graphics: Ralph W. Boaz

Slide 16:

Slide 17:

Learning Objective #1

Which of the following elements of the TFCS is not shared by API Software?

Answer Choices

1. Outputs
2. Inputs
3. Controller
4. Power

Slide 18:

Learning Objective #1

Review of answers

a) Outputs
Incorrect. API Software allows application programs to share the output devices of the TFCS.

b) Inputs
Incorrect. API Software allows application programs to share the input devices of the TFCS.

c) Controller
Incorrect. API Software allows application programs to share the controller unit of the TFCS.

d) Power
Correct. API Software has nothing to do with the distribution of power within the cabinet. The fourth element shared is Monitoring.

Slide 19:

Learning Objective #1

Structure of the ATC 5401 Standard

• Section 1 Introduction
• Section 2 Overall Description
• Section 3 Specific Requirements
• Section 4 Application Programming Interface
• Appendices
• Index

Slide 20:

Learning Objective #1

Clarification of Terms

• ATC 5401 Standard (aka API Standard) specifies software (aka API Software or "the API")
• API Software operates on ATC controller units allowing application programs to share the resources of the TFCS

Slide 21:

Learning Objective #1

Two Types of Users of API Software

• Operational Users
  • Technicians or transportation engineers that use application programs that run on controllers to perform their operational tasks
• User Developers
  • Software developers that design and develop application programs for ATC equipment

Slide 22:

Learning Objective #1

Two Types of Interfaces Provided by

API Software

• User Interfaces
  • Interfaces defined for Operational Users so that multiple programs can run concurrently on a ATC controller unit
• Software Interfaces
  • C language function calls that allow User Developers to create application programs that share the resources of a TFCS

Slide 23:

Learning Objective #1

ATC 5401 Sections of Interest to Operational Users

(Extended Text Description: This slide has a bulleted list with the following items:

• Section 1 Introduction
• Section 2 Overall Description
• Section 3 Specific Requirements
• Section 4 Application Programming Interface
• Appendices
• Index

As the instructor presents the slide, two rounded rectangles surround portions of the bulleted items representing the outline of the ATC 5401 Standard. One rounded rectangle surrounds the items "Section 1 Introduction," "Section 2 Overall Description" and "Section 3 Specific Requirements." A second rounded rectangle surrounds the item "Index." There is a rectangle to the right of the text with the enclosed text "Sections of Interest to Operational Users." There are arrows extending from the left of the rectangle to the rounded rectangles.)

Slide 24:

Learning Objective #1

Features for API Software

• Front Panel Management
• Field Input/Output (I/O) Management
• Real-Time Clock
• API Utilities

Slide 25:

Learning Objective #1

Front Panel Management

• Front Panel Manager Window
• C function interface
• Application programs able to use dedicated window(s)
• Operational Users interact with window/application program in "focus"
• "Default Window" is the window that has focus when the controller unit is powered up
• Works with screen sizes up to 24 lines x 80 characters
• Screen and keypad defined by the ATC 5201 Standard

Slide 26:

Learning Objective #1

ATC Controller Minimum Keypad

(Extended Text Description: This slide, entitled "ATC Controller Minimum Keypad," is a picture of a portion of a transportation controller that shows two keypads distributed horizontally. The keypad on the left is 4 rows X 4 columns with keys as follows: Row 1 – 1, 2, 3, A; Row 2 – 4, 5, 6, B; Row 3 – 7, 8, 9, C; Row 4 – 0, F, E, D. The keypad on the right is 4 rows X 3 columns with keys as follows: Row 1 – ESC, ˄ (up arrow), NEXT; Row 2 – ˂ (left arrow), *, ˃ (right arrow); Row 3 – +, ˅, -; Row 4 – YES, NO, ENT.)

Photo: Ralph W. Boaz

Slide 27:

Learning Objective #1

Front Panel Manager Window

(Extended Text Description: This slide, entitled "Front Panel Manager Window," is a graphic illustrating how multiple concurrently running programs can operate on a single ATC controller unit. In the upper part of the slide is a square about 1/8 the height of the slide representing a LCD screen and keypads (see Slide #25) portion of a transportation controller. Below the square is an enlargement of the LCD screen. There are dotted lines extending from the LCD in the square to the edges of the enlargement. The enlarged LCD screen is about 25% of the height of the slide and extends almost the entire width of the slide. There are 8 lines x 40 fixed width characters across shown in the LCD as follows:

1. "FRONT PANEL MANAGER VER 1.00"
2. "SELECT WINDOW: 0-F SET DEFAULT: *,0-F"
3. "0 Ramp Meter Prgrm 1*Signal Program"
4. "2 Emergency Mngmnt 3 Data Distributor"
5. "4 System Checker        5"
6. "6                                  7"
7. "8                                  9"
8. "[MORE - UP/DN ARROW] [CONFIG INFO-NEXT]"

)

[Application programs shown are for example purposes only and not included in API Software]

Graphics: Ralph W. Boaz

Slide 28:

Learning Objective #1

Example Application Programs

(Extended Text Description: This slide, entitled "Example Application Programs," is a graphic illustrating a possible user interface for a ramp meter program. In the upper part of the slide is a square about 1/8 the height of the slide representing a LCD screen and keypads (see Slide #25) portion of a transportation controller. Below the square is an enlargement of the LCD screen. There are dotted lines extending from the LCD in the square to the edges of the enlargement. The enlarged LCD screen is about 25% of the height of the slide and extends almost the entire width of the slide. There are 8 lines x 40 fixed width characters across shown in the LCD as follows:

1. "RAMP METER CONTROL"
2. " "
3. "1. Metered Lanes         6. Time of Day"
4. "2. Mainline                   7. Communications"
5. "3. Addnl Detect            8. General"
6. "4. Traff Resp Plns         9. Utilities"
7. "5. Command Source    A. Status"
8. " "

)

[Application programs shown are for example purposes only and not included in API Software]

Graphics: Ralph W. Boaz

Slide 29:

Learning Objective #1

Example Application Programs (cont.)

(Extended Text Description: This slide, entitled "Example Application Programs (cont.)," is a graphic illustrating a possible user interface for an intersection control program. In the upper part of the slide is a square about 1/8 the height of the slide representing a LCD screen and keypads (see Slide #25) portion of a transportation controller. Below the square is an enlargement of the LCD screen. There are dotted lines extending from the LCD in the square to the edges of the enlargement. The enlarged LCD screen is about 25% of the height of the slide and extends almost the entire width of the slide. There are 8 lines x 40 fixed width characters across shown in the LCD as follows:

1. "INTERSECTION CONTROL"
2. " "
3. "1. TIMING DATA           6. START/FLASH DATA"
4. "2. PH OVLP ASSIGN     7. NO SERVE PHASES"
5. "3. PED CARRYOVER     8. DIMMING"
6. "4. RECALL DATA           9. OPTION DATA"
7. "5. OVERLAP DATA"
8. "PRESS KEYS 1..9 TO SELECT  F=HELP"

)

[Application programs shown are for example purposes only and not included in API Software]

Graphics: Ralph W. Boaz

Slide 30:

Learning Objective #1

Example Application Programs (cont.)

(Extended Text Description: This slide, entitled "Example Application Programs (cont.)," is a graphic illustrating a possible user interface for an emergency management n intersection control program. In the upper part of the slide is a square about 1/8 the height of the slide representing a LCD screen and keypads (see Slide #25) portion of a transportation controller. Below the square is an enlargement of the LCD screen. There are dotted lines extending from the LCD in the square to the edges of the enlargement. The enlarged LCD screen is about 25% of the height of the slide and extends almost the entire width of the slide. There are 8 lines x 40 fixed width characters across shown in the LCD as follows:

1. "EMERGENCY MANAGEMENT OPERATIONS"
2. " "
3. "1. Local Operations"
4. "2. Regional Operations"
5. "3. Evacuation Routing Plan North 1"
6. "4. Evacuation Routing Plan East 1"
7. "5. Evacuation Routing South 1"
8. "[MORE - UP/DN ARROW]"

)

[Application programs shown are for example purposes only and not included in API Software]

Graphics: Ralph W. Boaz

Slide 31:

Learning Objective #1

C Function Interface for Front Panel Management

• General Functions
  • Open, Close, Refresh, Clear Windows
• Window Attribute Functions
  • Character Blink, Backlight, Reverse Video, Underline, Auto Wrap, Scrolling
• Read Functions
  • Poll for Input, Read Character, Read String
• Write Functions
  • Write Character, Write String, Write at Position

Slide 32:

Slide 33:

Learning Objective #1

Which of the following statements is TRUE regarding the operation of the Front Panel Manager Window?

Answer Choices

1. The Default Window is always position [1] on the Front Panel Manager Window
2. An Intersection Control window comes standard with the API Software
3. Pressing {**,<ESC>} causes the Front Panel Manager Window to be put in focus
4. The Front Panel Manager is designed for an 8 line display only

Slide 34:

Learning Objective #1

Review of answers

a) The Default Window is always position [0] on the front panel manager window
Incorrect. The Default Window is user selectable by pressing {*,[0-F],<ENT>} while in the Front Panel Manager Window.

b) An Intersection Control Window comes standard with API Software
Incorrect. API Software is defined by the ATC 5401 Standard which does not contain specifications for an Intersection Control Window.

c) Pressing {**,<ESC>} causes the Front Panel Manager Window to be put in focus
Correct. This action works regardless of the window that is in focus at the time.

d) The Front Panel Manager is designed for an 8 line display only
Incorrect. The Front Panel Manager will work with various size controller screens.

Slide 35:

Learning Objective #1

Field Input/Output (I/O) Management

• C function interface only
• Facilitates application programs to be written so they operate in the various TFCS architectures
  • Caltrans 332-Type Cabinets
  • NEMA TS 1, TS 2 Type 1, TS 2 Type 2 Cabinets
  • ITS Cabinets
• Application programs able to query the API to determine what types of devices are used in the TFCS

Slide 36:

Learning Objective #1

Field Input/Output (I/O) Management (cont.)

• Application programs "register" to access a Field I/O device
• Application programs have "read access" to all input and output field devices
• Application programs "reserve" exclusive "write access" to output points of a Field I/O Device

Slide 37:

Learning Objective #1

Application Programs Reserving Outputs

(Extended Text Description: This slide, entitled "Application Programs Reserving Outputs," is a graphic illustrating how application programs can share the field outputs (load switches) of a TFCS. The lower left of the slide is a graphic representation of the ITS Cabinet v02 architecture. It shows 6 rectangles about 20% the width of the slide and stacked vertically so that together they are about 50% of the height of the slide. The first (top) rectangle is labeled "CONTROLLER." The second rectangle is labeled "INPUT CAGE." The right 10% of the INPUT CAGE is sectioned and labeled SIU. The third rectangle is identical to the second. The fourth rectangle is labeled "PWR DISTRIBUTION ASSEMBLY." The right 10% of the PWR DISTRIBUTION ASSEMBLY is sectioned and labeled CMU. The fifth rectangle is labeled "OUTPUT CAGE." The right 20% of the OUTPUT CAGE is sectioned into two parts with each part representing 10% of the OUTPUT CAGE. These subsections are labeled "AMU" and "SIU." The sixth rectangle is identical to the fifth. There is a heavy arrow extending out the left side of the CONTROLLER and then points upward to a large graphic representation of an LCD screen of a controller. This LCD screen is about 25% of the height of the slide and extends almost the entire width of the slide. There are 8 lines x 40 fixed width characters across shown in the LCD as follows:

1. "FRONT PANEL MANAGER VER 1.00"
2. "SELECT WINDOW: 0-F SET DEFAULT: *,0-F"
3. "0 Ramp Meter Prgrm 1*Signal Program"
4. "2 Emergency Mngmnt 3 Data Distributor"
5. "4 System Checker        5"
6. "6                                     7"
7. "8                                    9"
8. "[MORE - UP/DN ARROW] [CONFIG INFO-NEXT]"

There is a heavy arrow extending out the right side of the OUTPUT CAGE and then points upward to an enlargement of the OUTPUT CAGE which is about 60% the length of the slide. This enlargement shows that the majority of the OUTPUT CAGE is made up of load switches which are represented as sections of the OUTPUT CAGE with three LEDs aligned vertically and centered within the load switch. Seven load switches are shown followed by the AMU and SIU. There is an oval highlighting the first two load switches. There is an oval highlighting the third load switch. There is an oval highlighting the last four load switches. There is an arrow extending from the "Ramp Meter Prgrm" text in the LCD graphic to the first oval. There is an arrow extending from the "Emergency Mngmnt" text in the LCD graphic to the second oval. There is an arrow extending from the "Signal Program" text in the LCD graphic to the third oval.)

Graphics: Ralph W. Boaz

Slide 38:

Learning Objective #1

C Function Interface for Field I/O Management

• General Functions
  • Register/Deregister, Enable/Disable Field I/O, Get/Reset Field I/O Status
• Input Configuration Functions
  • Get Field Inputs, Get/Set Input Filter
• Output Configuration Functions
  • Set/Get Field Output Reservations, Set/Get Field Outputs
• Frame Functions
  • Set/Get Frame Schedule, Read/Write Frames
• Transition Buffer Functions
  • Set/Get/Read Transition Buffer

Slide 39:

Learning Objective #1

C Function Interface for Field I/O Management (cont.)

• Watchdog/Health Monitor Functions
  • Watchdog Register/Deregister, Watchdog Set/Get Reservation, Health Monitor Register/Deregister, Health Monitor Heartbeat, Health Monitor Reset
• Fault/Volt Monitor Functions
  • Set/Get Volt Monitor
• CMU/MMU/Channel Functions
  • Set/Get Faults, Channel Mapping

Slide 40:

Learning Objective #1

C Function Interface for Real-Time Clock Management

• Set/Get Time Functions
• Daylight Saving Time (DST) Functions
• Time Source and Signaling Functions

Slide 41:

Slide 42:

Learning Objective #1

Which of the following is TRUE in regards to the Field I/O Management of API Software?

Answer Choices

1. All application programs may have read access to all of the input points
2. All application programs may have write access to all of the input points
3. All application programs may have write access to all of the output points
4. Application programs must communicate with each other to avoid writing to the same output points

Slide 43:

Learning Objective #1

Review of Answers

a) All application programs may have read access to all of the input points
Correct. There are no restrictions on applications reading input points.

b) All application programs may have write access to all of the input points
Incorrect. No application program has write access to input points.

c) All application programs may have write access to all of the output points
Incorrect. Application programs must reserve exclusive write access to modify an output point.

d) Application programs must communicate with each other to avoid writing to the same output points
Incorrect. The reservation system used by API Software makes communication unnecessary for this purpose.

Slide 44:

Learning Objective #1

API Utilities

• ATC Configuration Window
• Standard Utilities
  • Setting System Time
  • Setting Ethernet Ports
  • Selecting System Services
  • Getting Linux and API information
  • Viewing Host EEPROM Information
• Extensible so additional utilities may be added
• Utilities differ from application programs
• C function interface

Slide 45:

Learning Objective #1

ATC Configuration Window

(Extended Text Description: This slide, entitled "ATC Configuration Window," is a graphic illustrating the ATC Configuration Window and standard utility programs. In the upper part of the slide is a square about 1/8 the height of the slide representing a LCD screen and keypads (see Slide #25) portion of a transportation controller. Below the square is an enlargement of the LCD screen. There are dotted lines extending from the LCD in the square to the edges of the enlargement. The enlarged LCD screen is about 25% of the height of the slide and extends almost the entire width of the slide. There are 8 lines x 40 fixed width characters across shown in the LCD as follows:

1. "ATC CONFIGURATION INFORMATION"
2. "SELECT ITEM: 0 – F"
3. "0 System Time          1 Ethernet Config"
4. "2 System Services     3 Linux/API Info"
5. "4 Host EEPROM Info  5 "
6. "6                                  7 "
7. "8                                  9 "
8. "[UP/DN ARROW]      [CONFIG INFO-NEXT]"

)

Graphics: Ralph W. Boaz

Slide 46:

Learning Objective #1

System Time Utility

(Extended Text Description: This slide, entitled "System Time Utility," is a graphic illustrating the user interface for the System Time Utility program. In the upper part of the slide is a square about 1/8 the height of the slide representing a LCD screen and keypads (see Slide #25) portion of a transportation controller. Below the square is an enlargement of the LCD screen. There are dotted lines extending from the LCD in the square to the edges of the enlargement. The enlarged LCD screen is about 25% of the height of the slide and extends almost the entire width of the slide. There are 8 lines x 40 fixed width characters across shown in the LCD as follows:

1. "SYSTEM TIME"
2. "DATE             TIME      T-ZONE      DST/Status"
3. "06/13/2013     01:00:00  -07:00          Enable/Active"
4. " "
5. "CHANGE "
6. "DATE             TIME      T-ZONE       DST/Status"
7. "MM/DD/YYYY hh:mm:ss shh:mm      enadis"
8. "[UP/DN ARROW]   [APPLY-ENT]   [QUIT-**NEXT]"

)

Graphics: Ralph W. Boaz

Slide 47:

Learning Objective #1

Ethernet Configuration Utility

(Extended Text Description: This slide, entitled "Ethernet Configuration Utility," is a graphic illustrating the user interface for the Ethernet Configuration Utility program. In the upper part of the slide is a square about 1/8 the height of the slide representing a LCD screen and keypads (see Slide #25) portion of a transportation controller. Below the square is an enlargement of the LCD screen. There are dotted lines extending from the LCD in the square to the edges of the enlargement. The enlarged LCD screen is about 25% of the height of the slide and extends almost the entire width of the slide. There are 8 lines x 40 fixed width characters across shown in the LCD as follows:

1. "ETHERNET CONFIGURATION"
2. "ETHERNET PORT 1"
3. "Packets Sent GD: 120154243 BD:    9898416"
4. "Packets Rcvd GD: 782143860 BD:  28328078"
5. "IP Address:        192.168.001.065"
6. "Subnet Mask:    255.255.255.000"
7. "MM/DD/YYYY hh:mm:ss shh:mm      enadis"
8. "[UP/DN ARROW]   [APPLY-ENT]   [QUIT-**NEXT]"

)

Slide 48:

Learning Objective #1

Systems Services Utility

(Extended Text Description: This slide, entitled "Systems Services Utility," is a graphic illustrating the user interface for the Systems Services Utility program. In the upper part of the slide is a square about 1/8 the height of the slide representing a LCD screen and keypads (see Slide #25) portion of a transportation controller. Below the square is an enlargement of the LCD screen. There are dotted lines extending from the LCD in the square to the edges of the enlargement. The enlarged LCD screen is about 25% of the height of the slide and extends almost the entire width of the slide. There are 8 lines x 40 fixed width characters across shown in the LCD as follows:

1. "ENABLE/DISABLE SYSTEM SERVICES"
2. "SERVICE                          STATUS   CHANGE"
3. "Bluetooth                            Enabled   enaordis"
4. "Signal Phase & Timing         Enabled   enaordis"
5. "                                                          enaordis"
6. "                                                          enaordis"
7. "                                                          enaordis"
8. "[UP/DN ARROW]   [APPLY-ENT]   [QUIT-**NEXT]"

)

Graphics: Ralph W. Boaz

Slide 49:

Learning Objective #1

C Function Interface for API Utilities

• General Functions - Open/Close Configuration Window, Reserve/Release Resource
• Time of Day Functions - Set/Get Time, Set/Get DST, Time Source Selection
• "ATCConfigurationMenu.txt" file for adding utilities to ATC Configuration Window

configitemname1, executablepathname1

configitemname2, executablepathname2

configitemname3, executablepathname3

configitemname4, executablepathname4

Slide 50:

Slide 51:

Learning Objective #1

Which of the following is not a standard utility provided in API Software?

Answer Choices

1. Ethernet Configuration
2. Bluetooth Configuration
3. Linux/API Information
4. System Time

Slide 52:

Learning Objective #1

Review of answers

a) Ethernet Configuration
Incorrect. Ethernet is a standard utility allowing Operational Users to set the Ethernet ports of the controller.

b) Bluetooth Configuration
Correct. There is no utility for Bluetooth communications currently in the API Software. A utility could be created and added for Bluetooth, however.

c) Linux and API Information
Incorrect. Linux/API information is a standard utility in API Software allowing Operational Users to get information on the Linux Board Support Package and the API Software libraries.

d) System Time
Incorrect. Setting system time is a standard utility in API Software allowing Operational Users to set the time.

Slide 53:

Summary of Learning Objective #1

Identify the features of the ATC 5401 Application Programming Interface (API) Standard

• Sharing Resources of the Controller and Transportation Field Cabinet System
• Structure of the ATC 5401 Standard
• Features for API Software

Slide 54:

Learning Objective #2 - Describe the ATC 5401 Architecture

• Key Elements of the ATC 5401 Architecture
• Describe How the ATC 5401 Standard and ATC 5201 Standard Work Together
• ATC Software Portability, Compatibility and Interchangeability

Slide 55:

Learning Objective #2

Key Elements of the ATC 5401 Architecture

• Based on an "Engine Board" concept specified in ATC 5201
• Uses Linux operating system
  • Open source, multi-process, multi-application
• Allows multiple application programs to operate concurrently ATC controller units
• Shares resources of the front panel, field I/O elements of the TFCS, and the real-time clock
• Source code portability, compatibility and interchangeability for application programs

Slide 56:

Learning Objective #2

ATC Engine Board

(Extended Text Description: This slide, entitled "ATC Engine Board," is a graphic representation of a circuit board. It is approximately 40% of the height of the slide twice as wide as it is tall. There are seven variously shaped labeled rectangles representative of electronic components on the board. They are labeled "ENET 1," "ENET 2," "USB," "RTC," "CPU + LINUX O/S," "MEMORY" and "SERIAL I/O." There are two additional rectangles, identical in shape, representative of electronic connectors at the top and bottom of the board.)

Graphics: Ralph W. Boaz

Slide 57:

Learning Objective #2

Example Engine Board

(Extended Text Description: This slide, entitled "Example Engine Board," is photograph of an actual 5"W X 4"H Engine Board. There are various electronic chips on the board that have a rounded rectangle graphics surrounding them. The rounded rectangles have curved lines extending outside the picture with labels to identify the chips on the Engine Board. Just left of center of the board is a large chip that is approximately 1"W X 1"H. It is labeled "CPU." To the left and slightly higher than the CPU are two chips that are approximately .33"W X .67"H. The chips are aligned side by side. They are labeled "DRAM." Below the DRAM are two other chips approximately .5"W X .5"H each. The chips are side by side. They are labeled "Flash Memory." Below the left Flash Memory chip is a chip approximately .25"W X .25"H. The chip is labeled "SRAM." Below the right Flash Memory chip is a chip approximately .25"W X .25"H. The chip is labeled "USB." To the right of the CPU is a chip approximately .5"W X .5"H. The chip is labeled "ENET 1&2." Right of the ENET 1&2 chip, near the right edge of the Engine Board, is a chip approximately .25"W X .25"H. It is labeled "RTC." Near the right lower corner of the Engine Board is a chip approximately .33"W X .67"H. It is labeled "Serial I/O.")

Slide 58:

Learning Objective #2

ATC Layered S/W Architecture

(Extended Text Description: This slide, entitled "ATC Layered S/W Architecture," illustrates the layered architecture defined by the ATC 5201 and ATC 5401 standards. At the bottom of the graphic, centered on the slide, is a side view of an Engine Board graphic as described in Slide 55 (no labels shown). The Engine Board is about 60% the width of the slide. Above the Engine Board is a large rectangle that is as wide as the Engine Board and twice the height. It is labeled "LINUX OS & DEVICE DRIVERS." Above the LINUX OS & DEVICE DRIVERS rectangle is a smaller rectangle that is approximately 1/3 the width and 1/2 the height of the LINUX OS & DEVICE DRIVERS rectangle. It is labeled "API" and centered over the LINUX OS & DEVICE DRIVERS rectangle. Above the API rectangle is another rectangle of the same width and height. It is labeled "APPLICATION SW." The APPLICATION SW rectangle is aligned to the right so that only 25% of the APPLICATION SW rectangle is over the API rectangle. Above the APPLICATION SW rectangle is a slightly smaller rounded rectangle. It is approximately 1/3 the width and the same height as the APPLICATION SW rectangle below it. It is labeled "OPERATIONAL USER" and it is centered above the API rectangle, the LINUX OS & DEVICE DRIVERS rectangle and the Engine Board. Between the Engine Board and the LINUX OS & DEVICE DRIVERS rectangle and between each of the rectangles above them are single heavy dashed lines running in parallel horizontally from a point just beyond the left side of the engine board to nearly the right side of the slide (total of four lines). Between the Engine Board and the LINUX OS & DEVICE DRIVERS rectangle and between the LINUX OS & DEVICE DRIVERS rectangle and the API rectangle are heavy solid double arrows pointing upwards and downwards. Between the right side of the API rectangle and the left side of the APPLICATION SW rectangle is a heavy solid double arrow pointing upwards and downwards. Between the right side of the API rectangle and the left side of the APPLICATION SW rectangle is heavy solid double arrow pointing upwards and downwards. Between the right side of the LINUX OS & DEVICE DRIVERS rectangle and the right side of the APPLICATION SW rectangle is a heavy solid double arrow pointing upwards and downwards. Centered between the API rectangle and the OPERATIONAL USER rounded rectangle is a heavy solid double arrow pointing upwards and downwards. There is a heavy solid double arrow pointing to the right side of the OPERATIONAL USER rounded rectangle and making a 90 degree turn downward to the top of the APPLICATION SW rectangle. Below each dashed line, to the right of the Engine Board and rectangles, are the labels "APPLICATION LAYER," "API SOFTWARE LAYER," "ATC BOARD SUPPORT PACKAGE LAYER" and "HARDWARE LAYER" (top to bottom). To the left of the Engine Board and LINUX OS & DEVICE DRIVERS rectangle is a label "HARDWARE & OS DEFINED BY ATC 5201 STANDARD" set in a rounded rectangle. Adjacent to the right of the rounded rectangle and left of the Engine Board is a large left bracket indicating that the label in the rounded rectangle applies to the Engine Board and LINUX OS & DEVICE DRIVERS rectangle. To the left of the API rectangle is a label "INTERFACE & BEHAVIOR DEFINED BY ATC 5401 STANDARD" set in a rounded rectangle. Adjacent to the right of the rounded rectangle and left of the Engine Board is a smaller left bracket indicating that the label in the rounded rectangle applies to the API rectangle.)

Graphics: Ralph W. Boaz

Slide 59:

Learning Objective #2

API Software manages access to Front Panel, Field I/O Ports, and Real-Time Clock

(Extended Text Description: This slide is an enlarged graphic representation of a circuit board. It is twice as tall as it is wide. In the bottom left of the board is the label "ENGINE BOARD." There are eleven identically shaped smaller rectangles representative of electronic interfaces for an Engine Board. These rectangles are about 5% of the engine board in height and about 5 times as wide as they are tall. There are five rectangles centered on the left edge of the engine board and six rectangles centered on the right edge of the engine board. The rectangles on the right are distributed evenly along the right edge of the Engine Board. The five rectangles on the left are distributed so that they are at the same heights as the first five rectangles on the right. All of the rectangles have a short line extending out of the left side, for the rectangles on the left, and out of the right side for the rectangles on the right. The five rectangles on the left are labeled "CONSOLE," "SERIAL PORT 1," "SERIAL PORT 2," "SERIAL PORT 3," and "FRONT PANEL" (top to bottom). The six rectangles on the right are labeled "FIELD I/O DEV 1," "FIELD I/O DEV 2," "USB MEM DEV," "DATAKEY," "ETHERNET 1," and "ETHERNET 2" (top to bottom). To the left of the graphic is a label "TO HOST MODULE" running vertically bottom to top. To the right of the graphic is a label "TO HOST MODULE" running vertically top to bottom. There is animation as the instructor speaks. A small colored square approximately 4% of the slide height appears in the lower left area of the slide. There is a label to the right of the square "Resources managed by the API." There is a small rectangle of the same color as the small colored square that appears near the bottom of the Engine Board labeled "RTC." The FRONT PANEL, FIELD I/O DEV 1, and FIELD I/O DEV 2 rectangles turn the same color as the small colored square during the animation.)

Graphics: Ralph W. Boaz

Slide 60:

Learning Objective #2

ATC Software Portability, Compatibility and Interchangeability

Portability

• The ease with which applications software and data can be transferred from one application platform to another
• Ability to move, with minimal changes, application software between computers

Slide 61:

Learning Objective #2

Portability Achieved Through Compiling and Linking Software

(Extended Text Description: This slide, entitled "Portability Achieved Through Compiling and Linking Software," illustrates the method used to make an application program portable to ATC Engine Boards built by different vendors. At the top of the graphic is a rounded rectangle about 1/4 the width and 1/10 the height of the slide. It is centered with the label "Application Software." At the bottom of the graphic are three Engine Boards as described in Slide 55 except they are about 1/8 the width and 1/10 the height of the slide. They are evenly distributed across the bottom portion of the slide. Beneath the three Engine Boards are three corresponding labels "ATC Engine Board From Vendor 1," "ATC Engine Board From Vendor 2" and "ATC Engine Board From Vendor 3." There are three solid arrows pointing downward from the bottom of the rounded rectangle to the three Engine Boards. There is an oval that overlays the middle areas of the arrows (not the points connecting to the rounded rectangles or the Engine Boards). It is about 1/2 the width of the slide and 1/5 the height. It is centered on the slide and it is outlined with a dashed line. It is labeled "Compiling and Linking Using Application Source Code and API Software Libraries.")

Graphics: Ralph W. Boaz

Slide 62:

Learning Objective #2

ATC Software Portability, Compatibility and Interchangeability

Compatibility

• Two or more systems or components perform their required functions while sharing the same environment
• The two components (or systems) do not need to communicate with each other

Slide 63:

Learning Objective #2

Compatibility Achieved Through Linux O/S and API Software

(Extended Text Description: This slide, entitled "Compatibility Achieved Through Linux O/S and API Software," illustrates how the Linux operating system and API Software allow application programs to be compatible on a single Engine Board. At the top of the graphic are three rounded rectangles about 1/8 the width and 1/10 the height of the slide. They are closely spaced and evenly distributed in the center of the slide horizontally. They are labeled "Application Software 1," "Application Software 2" and "Application Software 3," respectively. At the bottom of the graphic is an Engine Board as described in Slide 55 except they it is about 1/8 the width and 1/10 the height of the slide. It is centered horizontally. Beneath the Engine Boards is a label "ATC Engine Board From Vendor." Centered above the Engine Board and below the three Application Software rectangles is a rounded rectangle that is about 1/8 the width and 1/10 the height of the slide. It is labeled "Linux O/S and API Software." There is a heavy double arrow from the center bottom Application Software 1 rounded rectangle to the upper left corner of the Linux O/S rounded rectangle. There is a heavy double arrow from the center bottom Application Software 2 rounded rectangle to the center top of the Linux O/S rounded rectangle. There is a heavy double arrow from the center bottom Application Software 3 rounded rectangle to the upper right corner of the Linux O/S rounded rectangle. There is a heavy double arrow from the center bottom Linux O/S rounded rectangle to the Engine Board.)

Graphics: Ralph W. Boaz

Slide 64:

Learning Objective #2

ATC Software Portability, Compatibility and Interchangeability

Interchangeability

• Same functional and physical characteristics so as to be equivalent in performance and durability (subjective)
• Ability to exchange devices of the same type without alteration to the device or adjoining items (adjustments permitted, subjective)

Slide 65:

Learning Objective #2

Interchangeability Possible If Application Features Are Equivalent

(Extended Text Description: This slide, entitled "Interchangeability Possible If Application Features Are Equivalent (subjective)," illustrates how application program interchangeability is possible using the Linux operating system and API Software. This slide contains the graphic as described in Slide 63. The graphic is aligned slightly to left of the center of this slide. The third (rightmost) rounded rectangle at the top of the graphic (see Slide 48) is labeled "Application Software 3*." There is a fourth rounded rectangle that is the same size as Application Software 3* but it is located at the level of the Linux O/S rounded rectangle (see Slide 48). It is labeled "Application Software 4*." There is a solid curved arrow extending from the top of the Application Software 4* rounded rectangle to the right side of the Application Software 3* rounded rectangle. There is a solid curved arrow extending from the bottom of the Application Software 3* rounded rectangle to the left side of the Application Software 4* rounded rectangle. Below the Application Software 4* rectangle is a rectangle (not rounded) that is about 1/3 the width and 1/10 the height of the slide. It is located slightly higher than the Engine Board (see Slide 48). The rectangle has the label "* Indicates applications are of the same type.")

Graphics: Ralph W. Boaz

Slide 66:

Slide 67:

Learning Objective #2

Which of following parts of the ATC Engine Board is not managed by API Software?

Answer Choices

1. Front Panel Port
2. Real-Time Clock
3. General Purpose Serial I/O Ports
4. Field I/O Ports

Slide 68:

Learning Objective #2

Review of answer

a) Front Panel Port
Incorrect. API Software controls the front panel port providing a windowing capability for application programs.

b) Real-Time Clock
Incorrect. API Software a System Time Utility and clock functions to allow users and application programs to set the real-time clock.

c) General Purpose Serial I/O Ports
Correct. Use of the general purpose serial ports is controlled by Linux not the API Software.

d) Field I/O Ports
Incorrect. API Software manages the Field I/O ports of the engine board.

Slide 69:

Summary of Learning Objective #2

Describe the ATC 5401 Architecture

• Key Elements of the ATC 5401 Architecture
• Describe How the ATC 5401 Standard and ATC 5201 Standard Work Together
• ATC Software Portability, Compatibility and Interchangeability

Slide 70:

Learning Objective #3 - Describe How the ATC 5401 Standard Works With Other ITS Standards

• Transportation Field Cabinet Systems
• ITS Communications Standards
• Consider New Ways To Solve ITS Issues

Slide 71:

Learning Objective #3

ATC 5401 Standard Works with all of the Major Transportation Field Cabinet Systems

• ATC 5201 Standard specifies controller units that work with Model 332 Cabinets, NEMA TS 1 and TS 2 Type 2 Cabinets, NEMA TS 2 Type 1 Cabinets and ITS Cabinets
• API Software provides internal cabinet interfaces suitable for all of the major TFCSs
• Application software can be made portable, compatible, and interchangeable to controllers designed for any TFCS through compilation with API libraries

Slide 72:

Learning Objective #3

ATC 5201 Standard and ATC 5401 Standard

Provide Computational Power and Interfaces for ITS Communications

• Most TFCSs that use 170 controller units will require replacement hardware in order to fully utilize NTCIP Actuated Signal Control (ASC) communications
• ATC standards provide the capability to support multiple applications using different (or same) types of NTCIP communications simultaneously
• ATC standards provide interface and computational power for applications such as Adaptive Control and Vehicle to Infrastructure (V2I) Integration

Slide 73:

Learning Objective #3

ATC Controller Units in Different TFCSs

(Extended Text Description: This slide, entitled "ATC Controller Units in Different TFCSs," illustrates that ATC 5201 conforming controller units can be designed to be used in existing TFCSs. The left of the slide is a graphic of the interior Model 332 Cabinet. The graphic is about 65% of the height of the slide and 25% of the width. There are side rails of an equipment rack which run along the left and right sides of the front of the cabinet interior. There are four sections of the equipment that extend edge to edge of the cabinet interior attaching to the side rails of the rack.

• The first (top) section is a controller unit. It is located about 5% of the way down from the top of the rack vertically. LCD, keypads, and various connectors are shown. The controller itself takes up approximately 15% of the vertical rack space. It has the letters "ATC" on the upper right of the controller.
• The second section takes up approximately 15% of vertical rack space and is made up of three areas distributed horizontally across the section. The first area on the left is approximately 40% of the horizontal rack. It contains two rectangles representing components. 50% of the middle area holds two other rectangular components. The third area has lights and/or knobs on its left side and a handle extending down the middle of the subassembly.
• The third section takes up approximately 25% of vertical rack space and is made up of three areas distributed horizontally across the section. The left area takes up approximately 15% of the horizontal width of the assembly. Aligned down the left area are four rounded rectangles. The middle area takes up approximately 75% of the horizontal width of the assembly. It contains two rows of 6 rectangular devices evenly distributed. The right area takes up approximately 5% of the horizontal width of the assembly.
• The fourth section takes up approximately 25% of vertical rack space and is made up of two rows of similar thin rectangular devices. The top row has six of such devices. The bottom row has for of the devices.

There is a label "Model 332 Cabinet" centered below the cabinet graphic.

The right of the slide is a graphic of the interior of a NEMA TS 2 Type 1 cabinet. The graphic is about 65% of the height of the slide and 40% of the width. There are three sections within the cabinet graphic, two on upper part of the graphic and a larger section below the other two that takes up most remainder of the cabinet.

• The upper left section of the graphic is a controller unit. It is located about 25% of the height and 40% of the width of the graphic. LCD, keypads, four large circular connectors and various other connectors are shown. It has the letters "ATC" at the center top of the controller.
• The upper right section of the graphic (bottom aligned with the controller) is a single device that takes up approximately 30% of height and 10% of the width of the width. It has a thin slot running along the left side of the device, a rectangular connector in lower center of the device, and three round connectors on the right side of the device. It has the letters "MMU" at the center top of the device.
• The lower section of the graphic is a rectangular assembly that takes up approximately 55% of the height and 85% of the width of the graphic cabinet graphic. Within this lower section there are many smaller devices of various shapes and sizes aligned in five rows.
  • The first row consists of an assembly of devices that take up about 80% of the width of the lower section and 20% of the height. There is an additional device to the right of this assembly that is almost square.
    • Starting from the left of the assembly is a rectangular device that is about twice as tall as it is wide. It has three connectors (two round connectors and one rectangular connector) on the left side of the device. It has the letters "BIU" at the top center of the device. To the right of the BIU are eight evenly spaced rectangular devices the same height as the BIU but slightly thinner. Each has a handle. There are two additional devices of the same size as the previous but they are closer together and have no handle.
    • The device to the right of the assembly has two circular connectors in the lower left corner. It has the words "POWER SUPPLY" centered at the top.
  • The second row consists of an assembly of devices that take up about the width of the lower section and 20% of the height. Starting from the left of the assembly is a rectangular device that is about twice as tall as it is wide. It has three connectors (two round connector and one rectangular connector) on the left side of the device. It has the letters "BIU" at the top center of the device. To the right of the BIU are eight evenly spaced nine rectangular devices. These devices consist of a smaller rectangle with three lights (except for the far right one has two lights) attached to a thick line that extends to the same height of the BIU.
  • The third row consists of four squares about 5% of the lower section height. The four squares are evenly spaced and take up the left half of the row.
  • The fourth row has a single long rectangular rack of 54 round connectors arranged in in 2 rows and evenly spaced.
  • The fifth row is the same as the fourth.
• There is a thin cable extending from a rectangular connector on the controller downward then to a small square near the left side of the graphic just above the lower section. There is a thin cable extending downward from the MMU then leftward to the small square. A thin cable extends downward from the small square then to the right to connect to a rectangular connector on the BIU in row one of the lower section. There is another thin cable that extends downward from the small square then to the right to connect a rectangular connector on the BIU in row two of the lower section. There are two thick cables which extend from round connectors on the MMU to the right and then downward along the right outside of the lower section then to the left across the lower section in between rows 4 and 5.

There is a label "NEMA TS 2 Type 1" centered below the cabinet graphic.)

Graphics: Ralph W. Boaz

Slide 74:

Learning Objective #3

ATC 5401 Working With Other ITS Standards

(Extended Text Description: This slide, entitled "ATC 5401 Working With Other ITS Standards," illustrates how the ATC 5401 Standard enables the use of other ITS standards. There is a graphic on the left 2/3 of the slide. On the right 1/3 of the slide are labels that identify the standards that are used at each level.

Level 1 of the graphic shows the top portions of the graphic illustrations of the Caltrans 332 and the NEMA TS 2 cabinets from the previous slide aligned side by side. In the Caltrans 332 cabinet, the ATC controller is shown. In the NEMA TS 2 Type 1 Cabinet the ATC controller and the MMU are shown. To the right of the cabinets is the label "TFCS Standards & Specifications."

Level 2 of the graphic shows two Engine Board graphics as described in Slide 55 except they are about 1/8 the width and 1/10 the height of the slide. They are aligned side by side and centered above the cabinet graphics (one over each cabinet). There are thick curved arrows extending out of the left side of each Engine Board and pointing to the left side of the controller in the cabinets below them. To the right of the cabinets is the label "ATC 5201 Standard."

Level 3 of the graphic shows a rectangle labeled "API Software" above each of the two Engine Boards. They are aligned side by side and centered above the Engine Board graphics (one over each Engine Board). There are thick curved arrows extending out of the left side of the API Software rectangles and pointing to the left side of the Engine Boards below them. To the right of the API Software rectangles is the label "ATC 5401 Standard."

Level 4 is a large rounded rectangle that is about 25% of the height of the slide and 40% of the width of the slide. It is aligned so that it is centered above the two API Software rectangles. At the top of the rounded rectangle is the label "Example Applications."  The remainder of the large rounded rectangle is made up of four identically sized rounded rectangles. The upper left rounded rectangle is labeled "Single Control App w/ASC." The upper right rounded rectangle is labeled "Field Master App w/FMS." The lower left rounded rectangle is labeled "Ramp Meter App w/RMC." The lower right rounded rectangle is labeled "SPAT Message Service." There is a thick curved arrow extending out of the left side of the large rounded rectangle and pointing to the left side of the API Software rectangle to the lower left. There is a thick curved arrow extending out of the right side of the large rounded rectangle and pointing to the right side of the API Software rectangle to the lower right. To the right of the large rounded rectangle is the label "NTCIP, Other Standards.")

Graphics: Ralph W. Boaz

Slide 75:

Learning Objective #3

Consider New Ways To Solve ITS Issues

• Open systems promotes innovation from more sources
• ATC 5401 Standard is opening up new markets for 3rd party software
• New methods to solve ITS problems
  • Software duplicated in field devices may be able to run as applications on an ATC controller
  • Field devices may be more cost effective
  • Custom applications
• Good system engineering practices essential

Slide 76:

Slide 77:

Learning Objective #3

What must a User Developer do to make an application portable and compatible on two different ATC controllers in different TFCS architectures? Choose the best answer.

Answer Choices

1. Write the application software so that it uses the ATC 5401 function calls whenever they are applicable
2. Compile and link the application source code with API libraries
3. Compile and link the application source code for the ATC Engine Board used in each controller
4. All the above

Slide 78:

Learning Objective #3

Review of answers

a) Write the application software so that it uses the ATC 5401 function calls whenever they are applicable
Incorrect. This is an essential part of making the software portable and compatible but there are others. Note that software will also need to use function calls appropriate for appropriate TFCS architectures.

b) Compile and link the application source code with API libraries
Incorrect. This is an essential part of making the software portable and compatible between TFCS architectures but there are others.

c) Compile and link the application source code for the ATC Engine Board used in each controller
Incorrect. This is an essential part of making the software portable and compatible between TFCS architectures but there are others.

d) All of the above
Correct. This is the best answer.

Slide 79:

Summary of Learning Objective #3

Describe How the ATC 5401 Standard Works With Other ITS Standards

• Transportation Field Cabinet Systems
• ITS Communications Standards
• Consider New Ways To Solve ITS Issues

Slide 80:

Learning Objective #4 - Specify API Software for System and Equipment Procurements

• Discuss how ATC 5401 fits in the Systems Life Cycle
• Develop migration strategies and mitigate deployment issues
• Creating a specification based on the ATC 5401 Standard

Slide 81:

Learning Objective #4

How ATC 5401 Fits in the Systems Life Cycle

• TFCSs (including controllers) can be considered a subsystem of a Center-to-Field (C2F) system
• TFCSs may be in place for multiple C2F systems and generations of C2F systems
• ATC controller units may extend the life of a C2F system
• Deployment of the ATC 5201 and ATC 5401 standards my occur at any stage in the life of a C2F system

Slide 82:

Learning Objective #4

Develop Migration Strategies

• Have a written plan and policy for deploying ATC equipment as part of a strategic plan
• Procurement specifications and procurement process must be integrated with the strategic plan
• Factors that may influence the migration strategy:
  • Working with existing TFCS
  • Moving to new TFCS architectures
  • New projects
  • Scheduled maintenance (cont.)

Slide 83:

Learning Objective #4

Develop Migration Strategies (cont.)

• Factors that may influence the migration strategy: (cont.)
  • Upgrading to ATC hardware while using an agency's current application software
  • Upgrading to new operational software
  • Compatibility with existing or planned system software
  • Training operational staff

Slide 84:

Learning Objective #4

Mitigating Deployment Issues

• Although the API 5401 v02 has been published, complete API Software meeting the standard is not yet available
• USDOT has started a project to create a reference implementation of API Software (APIRI) for public use in 2015
• APIRI project includes development of a validation suite (APIVS) to test API Software on an ATC Engine Board

Slide 85:

Learning Objective #4

Open Source API Reference Implementation

(Extended Text Description: This slide, entitled "Open Source API Reference Implementation," illustrates the concept of how the transportation industry can maintain the reference implementation of the APIRI software. In the center of the slide is picture of a computer tower. It is about 15% of the height of the slide and 5% of the width of the slide. It is a cuboid shape. There are buttons in the upper right of the tower, two horizontal slots for DVDs towards the top, a smaller slot for a 3.5" floppy disk and slats running down the lower 2/3 of the tower. Above the tower is the label "Open Source APIRI." There are four pictures arranged in an arch pattern over the tower. Each picture is approximately 15% of the height of the slide and 15% of the width of the slide. There are thick lined arrows pointing from each of the pictures to the computer tower.

• On the left side of slide and aligned with the computer tower is a picture of a female electronics technician sitting at an electronics workbench with various tools. The technician is testing the components on a printed circuit board. Beneath the picture is the label "Manufacturers."
• Not as far left as the Manufacturers picture and slightly above the level of the computer tower is a picture of a male computer professional working at a laptop computer. He is wearing a telephone earpiece. To the left of the picture is the label "Software Vendors."
• On the right side of slide and aligned with the computer tower is a picture two male transportation professionals sitting in front of computer workstations. All or parts of six flat screen computer monitors are directly in front of them. In the background of the picture two walls can be seen. They are completely covered in video screens and monitors (approximately 50 in total). Beneath the picture is the label "Agencies."
• Not as far right as the Agencies picture and slightly above the level of the computer tower is a picture of two males wearing neckties in front of two workstations with flat screen computer monitors. One of the males is pointing to the screen of the other. To the right of the picture is the label "Consultants."

Below the picture of the computer tower, is a large thick lined bracket. It is turned so that the open part of the bracket faces downward and extends almost the entire width of the slide. Below the bracket are pictures of four ATC controller units evenly distributed along the lower portion of the slide. The pictures are approximately 10% of the slide height and 15%-20% of the slide width. They are described below starting from the left.

• The first controller is angled to the right. The unit is 10.75" W X 7.75" D X 10.5" H. On the lower 1/3 of the controller are four circular connectors evenly spaced across the width of the controller. They are labeled left to right "A," "B," "C" and "D." To the left of the A connector are two small knobs. Above the circular connectors, on the left 1/8 of the controller are electronic cable connectors rotated 90 degrees so they are shown taller than wider. These include four RJ45 jacks, two 25 pin Sub D connectors, a 9 pin Sub D connector and a 15 pin Sub D connector. There are numerous small LEDs adjacent to the RJ45 jacks. Centered in the upper 1/3 area of the controller is an LCD screen. Below the screen are additional electronic connectors including four USB ports, six RJ45 jacks. To the right of the LCD screen is a keypad with 28 keys. Below the keypad and above the D connector is a knob. Facing the left side of the controller are two panels (1.5" W X 7" H each) which are held in place by two round thumbscrews (each).
• The second controller is facing forward. The unit is 10" W X 10.5" D X 7" H. There is an LCD screen on the upper left portion of the controller. It is about 30% of the height and 40% of the width of the controller. To the right of the LCD screen is a keypad with 28 keys four of which appear to be arrows. Below the LCD screen is a knob and four RJ45 jacks. Below the knob is a circular connector. To the left of the circular connector are a knob and a small rectangular toggle switch. Beneath the RJ45 jacks are a 15 pin Sub D connector and three 9 pin Sub D connectors. To the right of the 9 pin Sub D connector and aligned with the right edge of the key pad are four USB ports. To the right of the keypad and USB ports is a panel (1.5" W X 7" H) which is held in place by two round thumbscrews.
• The third controller is facing forward. The unit is 14.84" W X 6.13" D X 8.50" H. On the left 1/8 of the controller there are electronic cable connectors rotated 90 degrees so they are shown taller than wider. These include two USB ports, four RJ45 jacks, a 25 pin Sub D connector, a 9 pin Sub D connector and a 15 pin Sub D connector. On the lower 1/3 of the controller and to the right of the electronic cable connectors are four circular connectors evenly spaced across the remaining width of the controller. They are labeled left to right "D," "C," "B" and "A." To the right of the A connector is a plastic screw about .25" in diameter. Above the D and C connectors is a LCD screen that takes up about 50% of the height and 40% of the width of the controller. To the right of the screen above the B and A connectors is a keypad with 24 keys. One of the keys is a large diamond shape which appears to have arrows on its corners.

The fourth controller is angled to the right. The unit is 19" W x 10.5" D x 7" H. There is an LCD screen on the upper left portion of the controller. It is about 25% of the width and 50% of the height of the controller. To the right of the LCD screen is a keypad with 32 keys. In the lower left front of the controller are two plastic screws about .25" in diameter. To the right of the screws below the left side of the LCD screen are two RJ45 jacks. To the right of the RJ45 jacks aligned with the right side of the LCD screen is a USB port. Below the key pad are a 15 pin Sub D connector, two 9 pin Sub D connectors, and a 25 pin Sub D connector. To the right of the 25 pin Sub D connector is a metal posted toggle switch. On the left and right sides of the controller are wire pull handles that are about 50% of the height of the controller aligned and centered vertically.)

Photos: Intelight, McCain, Econolite, Peek

Graphics: Ralph W. Boaz

Slide 86:

Learning Objective #4

Benefits of Open Source API Reference Implementation

• Consistent with the Linux O/S open source concept
• Promotes collaboration of developers across transportation industry
• Provides forum for users to express ideas and concerns
• Promotes quick bug fixes and alternative solutions to issues
• Facilitates introduction of new application developers
• Lowers cost to the industry
• Best opportunity for consistent API Software behavior

Slide 87:

Learning Objective #4

API Validation Suite (APIVS)

• APIVS software runs on a PC
• Test fixture used to host an ATC Engine Board with API Software
• PC uses test scripts written in XML (Extensible Markup Language) to drive testing of the Engine Board and API Software on the test fixture
• Crossover cables used to connect inputs to outputs of the Engine Board and exercise API Software functionality
• To be made available as open source project

Slide 88:

Learning Objective #4

API Validation Suite Test Fixture

(Extended Text Description: This slide, entitled "API Validation Suite Test Fixture," contains graphic illustrations of a possible design for a test fixture that could be used in validating API software on an Engine Board. There are two graphics on the slide.

The main graphic is a top down view of a test fixture. It is represented as a large rectangle that is approximately 60% of the slide height and width. It is positioned slightly to the right of the slide center. The upper left corner of the square has the label "API TEST FIXTURE." Centered on the test fixture is a square that takes up approximately 85% of the height and 60% of the width of the test fixture. In the other graphic on this slide we see that this square represents the mounting area of the test fixture. Centered on the mounting area is an Engine Board similar to that described in Slide 55 but turned sideways so that it is taller than it is wide. The Engine Board is about 90% of the width and height of the mounting area. The upper right corner of the Engine Board has the label "ATC ENGINE BOARD." To the right and left of the mounting area are 25 pin serial "D" connectors with three on the aligned down the left side of the test fixture and four aligned down the right side of the test fixture. Each connector on the left side of the test fixture is aligned with the connector on the right of the test fixture except that there is no connector in the third position on the left. The 25 pin connectors are represented as isosceles trapezoids (small end down) with dots representing pins. The connectors on the left side have labels underneath them "SP2," "SP5," and "SP8." The connectors on the right side have labels underneath them "SP1," "SP3," "SP4 Console," and "SP6 Front Panel." Extending out of the left side of the test fixture is a heavy cable with the label "External Power" above it.

There is second graphic showing an angled view of the test fixture. The graphic is 25% of the height of the slide and 20% of the width of the slide. The engine board and the test fixture are separate in this view exposing a mounting area in the center of the test fixture. The mounting area has four screw positions in each corner and electronic connectors on the sides of the mounting area matching those on the engine board. The Engine Board is centered above the test fixture there are dotted lines going from each corner of the Engine Board to the screw positions on the mounting area of the test fixture. The front of the test fixture is labeled "TEST FIXTURE.")

Graphics: Ralph W. Boaz

Slide 89:

Learning Objective #4

API Validation Suite Test Environment

(Extended Text Description: This slide, entitled "API Validation Test Environment," contains a graphic illustration of a proposed test environment for the API software on an Engine Board. Overall the graphic takes up about 50% of the height of the slide and the entire width. Positioned just left of center is an angled left view of the test fixture from the Slide 88 with an Engine Board attached. There is a two pronged curled electrical cable extending out of the left side of the test fixture. It has the label "POWER CABLE" above it. There is a crooked looking cable connecting the second connector on the left side of the Engine Board to the second connector on the right side of the engine board. The cable appears to have slack and is shown looping above the test fixture. It has the label "CROSSOVER CABLE" above it. Extending out of the third connector of the test fixture is a curved cable connecting to a laptop computer (also an angled left). The cable has the label "CONSOLE CABLE" above it.)

Graphics: Ralph W. Boaz

Slide 90:

Learning Objective #4

Creating a Specification Based on the ATC 5401 Standard

• Specification for API Software a part of ATC controller (or Engine Board) procurement (see PCB Module A207b)
• Require API Software that conforms to ATC 5401 v02.17 when the APIRI is available
• Establish a contractual commitment from Engine Board suppliers to provide operational API Software for their Engine Boards once the APIRI is available
• Require the Tool Chain and Source Code Used to Produce the Linux Environment for the Engine Board

Slide 91:

Learning Objective #4

Creating a Specification Based on the ATC 5401 Standard

• Require demonstration from manufacturers that each of the API interfaces are operational and multiple programs run concurrently
• Have a certification from manufacturer that the ATC being purchased passed testing using the APIVS (when it is available)

Slide 92:

Learning Objective #4

Additional Guidance When Procuring Application Software

• Prior to purchase, have application providers demonstrate their software on the agency's current ATC units
• Establish a contractual commitment from application software providers to supply software compatible with the API once the APIRI is available
• Purchase support services with application software
• Separate specifications for ATC 5201 and ATC 5401 equipment from that of any application programs

Slide 93:

Slide 94:

Learning Objective #4

What is NOT a benefit of the API Reference Implementation?

Answer Choices

1. Guarantees bug-free software
2. Lowers development cost to the industry
3. Best opportunity for consistent API Software behavior
4. Promotes collaboration of developers across the transportation industry

Slide 95:

Learning Objective #4

Review of Answers

a) Guarantees bug-free software
Correct. This is not a benefit of the APIRI. In any non-trivial software, there are bound to be unexpected behaviors.

b) Lowers development cost to the industry
Incorrect. This is a benefit of the APIRI. In this joint effort of industry developers, costs are reduced for everyone.

c) Best opportunity for consistent API Software behavior
Incorrect. This is a benefit of the APIRI. A common source defining proper software behavior creates the most consistency.

d) Promotes collaboration of developers across the transportation industry
Incorrect. This is a benefit of the APIRI. Solutions and improvements by individuals are discussed, assessed and tested by a group of developers prior to being added to the APIRI.

Slide 96:

Summary of Learning Objective #4

Specify API Software for System and Equipment Procurements

• Discuss how ATC 5401 fits in the Systems Life Cycle
• Develop migration strategies and mitigate Deployment Issues
• Creating a specification based on the ATC 5401 Standard

Slide 97:

What We Have Learned

1. API Software is grouped into the following feature areas: Front Panel Management, Field I/O Management, Real-Time Clock Management and API Utilities.
2. The ATC 5201 and ATC 5401 define a layered architecture that provides for application software portability, compatibility and interchangeability.
3. ATC 5401 Standard defines API Software which will work with all major TFCS architectures in use today.
4. The API Open Source Reference Implementation will promote collaboration of developers across the transportation industry.

Slide 98:

Resources

• Caltrans Transportation Electrical Equipment Specifications (TEES), 12 March 2009
• Intelligent Transportation System (ITS) Standard Specification for Roadside Cabinets v01.02.17b
• NEMA Standards Publication TS 1-1989 Traffic Control Systems
• NEMA Standards Publication TS 2-2003 v02.06 Traffic Controller Assemblies with NTCIP Requirements
• Institute of Transportation Engineers http://www.ite.org/standards/
• ITS PCB Training http://www. pcb.its.dot.gov/

Slide 99: