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:

Welcome - Graphic image of introductory slide. Please see the Extended Text Description below.

(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

Head shot photo of Ken Leonard, Director - ITS Joint Program Office

Ken Leonard, Director

ITS Joint Program Office

Ken.Leonard@dot.gov

Screen capture snapshot of RITA website - for illustration only - see the extended text description below.

(Extended Text Description: Intro Slide: Screen capture snapshot of RITA website - for illustration only. Below this image is a link to the current website: http://www.pcb.its.dot.gov - 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: http://www.pcb.its.dot.gov)

www.pcb.its.dot.gov

(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 www.pcb.its.dot.gov

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:

Activity. A placeholder graphic with an image of hand over a computer keyboard to show that an activity is taking place.

 

Slide 4:

A208:

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

 

Slide 5:

Instructor

Portrait image of Ralph W. Boaz - President, Pillar Consulting, Inc. San Diego, CA, USA

Ralph W. Boaz

President

Pillar Consulting, Inc.

San Diego, CA, USA

 

Slide 6:

Target Audience

 

Slide 7:

Recommended Prerequisite(s)

 

Slide 8:

Recommended Prerequisite(s) (cont.)

 

Slide 9:

Curriculum Path (Non-SEP)

This slide contains a graphic illustration indicating the sequence of training modules that lead up to this course. Please see the Extended Text Description below.

(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

 

Slide 12:

Learning Objective #1

Uses for ATC Controller Units Identified

 

Slide 13:

Learning Objective #1

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

Sharing Resources of the Controller and Transportation Field Cabinet System (TFCS). Please see the Extended Text Description below.

(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

Basic TFCS Operation. Please see the Extended Text Description below.

(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

Sharing Resources of the Controller and TFCS. Please see the Extended Text Description below.

(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:

Activity. A placeholder graphic with an image of hand over a computer keyboard to show that an activity is taking place.

 

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 small graphical red and yellow X representing incorrect.a) Outputs
Incorrect. API Software allows application programs to share the output devices of the TFCS.

A small graphical red and yellow X representing incorrect.b) Inputs
Incorrect. API Software allows application programs to share the input devices of the TFCS.

A small graphical red and yellow X representing incorrect.c) Controller
Incorrect. API Software allows application programs to share the controller unit of the TFCS.

A small graphical green and yellow check mark representing correct.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

 

Slide 20:

Learning Objective #1

Clarification of Terms

 

Slide 21:

Learning Objective #1

Two Types of Users of API Software

 

Slide 22:

Learning Objective #1

Two Types of Interfaces Provided by

API Software

 

Slide 23:

Learning Objective #1

ATC 5401 Sections of Interest to Operational Users

ATC 5401 Sections of Interest to Operational Users. Please see the Extended Text Description below.

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

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

 

Slide 25:

Learning Objective #1

Front Panel Management

 

Slide 26:

Learning Objective #1

ATC Controller Minimum Keypad

ATC Controller Minimum Keypad. Please see the Extended Text Description below.

(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

Front Panel Manager Window. Please see the Extended Text Description below.

(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

Example Application Programs. Please see the Extended Text Description below.

(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.)

Example Application Programs (cont.). Please see the Extended Text Description below.

(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.)

Example Application Programs (cont.). Please see the Extended Text Description below.

(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

 

Slide 32:

Activity. A placeholder graphic with an image of hand over a computer keyboard to show that an activity is taking place.

 

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 small graphical red and yellow X representing incorrect.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.

A small graphical red and yellow X representing incorrect.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.

A small graphical green and yellow check mark representing correct.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.

A small graphical red and yellow X representing incorrect.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

 

Slide 36:

Learning Objective #1

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

 

Slide 37:

Learning Objective #1

Application Programs Reserving Outputs

Application Programs Reserving Outputs. Please see the Extended Text Description below.

(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

 

Slide 39:

Learning Objective #1

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

 

Slide 40:

Learning Objective #1

C Function Interface for Real-Time Clock Management

 

Slide 41:

Activity. A placeholder graphic with an image of hand over a computer keyboard to show that an activity is taking place.

 

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 small graphical green and yellow check mark representing correct.a) All application programs may have read access to all of the input points
Correct. There are no restrictions on applications reading input points.

A small graphical red and yellow X representing incorrect.b) All application programs may have write access to all of the input points
Incorrect. No application program has write access to input points.

A small graphical red and yellow X representing incorrect.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.

A small graphical red and yellow X representing incorrect.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

 

Slide 45:

Learning Objective #1

ATC Configuration Window

ATC Configuration Window. Please see the Extended Text Description below.

(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

System Time Utility. Please see the Extended Text Description below.

(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

Ethernet Configuration Utility. Please see the Extended Text Description below.

(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

Systems Services Utility. Please see the Extended Text Description below.

(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

configitemname1, executablepathname1

configitemname2, executablepathname2

configitemname3, executablepathname3

configitemname4, executablepathname4

 

Slide 50:

Activity. A placeholder graphic with an image of hand over a computer keyboard to show that an activity is taking place.

 

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 small graphical red and yellow X representing incorrect.a) Ethernet Configuration
Incorrect. Ethernet is a standard utility allowing Operational Users to set the Ethernet ports of the controller.

A small graphical green and yellow check mark representing correct.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.

A small graphical red and yellow X representing incorrect.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.

A small graphical red and yellow X representing incorrect.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

 

Slide 54:

Learning Objective #2 - Describe the ATC 5401 Architecture

 

Slide 55:

Learning Objective #2

Key Elements of the ATC 5401 Architecture

 

Slide 56:

Learning Objective #2

ATC Engine Board

ATC Engine Board. Please see the Extended Text Description below.

(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

Example Engine Board. Please see the Extended Text Description below.

(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

ATC Layered S/W Architecture. Please see the Extended Text Description below.

(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

API Software manages access to Front Panel, Field I/O Ports, and Real-Time Clock. Please see the Extended Text Description below.

(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

 

Slide 61:

Learning Objective #2

Portability Achieved Through Compiling and Linking Software

Portability Achieved Through Compiling and Linking Software. Please see the Extended Text Description below.

(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

 

Slide 63:

Learning Objective #2

Compatibility Achieved Through Linux O/S and API Software

Compatibility Achieved Through Linux O/S and API Software. Please see the Extended Text Description below.

(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

 

Slide 65:

Learning Objective #2

Interchangeability Possible If Application Features Are Equivalent

Interchangeability Possible If Application Features Are Equivalent. Please see the Extended Text Description below.

(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:

Activity. A placeholder graphic with an image of hand over a computer keyboard to show that an activity is taking place.

 

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 small graphical red and yellow X representing incorrect.a) Front Panel Port
Incorrect. API Software controls the front panel port providing a windowing capability for application programs.

A small graphical red and yellow X representing incorrect.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.

A small graphical green and yellow check mark representing correct.c) General Purpose Serial I/O Ports
Correct. Use of the general purpose serial ports is controlled by Linux not the API Software.

A small graphical red and yellow X representing incorrect.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

 

Slide 70:

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

 

Slide 71:

Learning Objective #3

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

 

Slide 72:

Learning Objective #3

ATC 5201 Standard and ATC 5401 Standard

Provide Computational Power and Interfaces for ITS Communications

 

Slide 73:

Learning Objective #3

ATC Controller Units in Different TFCSs

ATC Controller Units in Different TFCSs. Please see the Extended Text Description below.

(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.

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.

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

ATC 5401 Working With Other ITS Standards. Please see the Extended Text Description below.

(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

 

Slide 76:

Activity. A placeholder graphic with an image of hand over a computer keyboard to show that an activity is taking place.

 

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 small graphical red and yellow X representing incorrect.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.

A small graphical red and yellow X representing incorrect.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.

A small graphical red and yellow X representing incorrect.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.

A small graphical green and yellow check mark representing correct.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

 

Slide 80:

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

 

Slide 81:

Learning Objective #4

How ATC 5401 Fits in the Systems Life Cycle

 

Slide 82:

Learning Objective #4

Develop Migration Strategies

 

Slide 83:

Learning Objective #4

Develop Migration Strategies (cont.)

 

Slide 84:

Learning Objective #4

Mitigating Deployment Issues

 

Slide 85:

Learning Objective #4

Open Source API Reference Implementation

Open Source API Reference Implementation. Please see the Extended Text Description below.

(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.

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 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

 

Slide 87:

Learning Objective #4

API Validation Suite (APIVS)

 

Slide 88:

Learning Objective #4

API Validation Suite Test Fixture

API Validation Suite Test Fixture. Please see the Extended Text Description below.

(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

API Validation Suite Test Environment. Please see the Extended Text Description below.

(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

 

Slide 91:

Learning Objective #4

Creating a Specification Based on the ATC 5401 Standard

 

Slide 92:

Learning Objective #4

Additional Guidance When Procuring Application Software

 

Slide 93:

Activity. A placeholder graphic with an image of hand over a computer keyboard to show that an activity is taking place.

 

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 small graphical green and yellow check mark representing correct.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.

A small graphical red and yellow X representing incorrect.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.

A small graphical red and yellow X representing incorrect.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.

A small graphical red and yellow X representing incorrect.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

 

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

 

Slide 99:

Questions? A placeholder graphic image with word Questions? at the top, and an image of a lit light bulb on the lower right side.