item 683.01042108 – led parking space sign assembly …the manufacturer of the led parking space...

ITEM 683.01042108 – LED PARKING SPACE SIGN ASSEMBLY – TYPE 1 ITEM 683.01042208 – LED PARKING SPACE SIGN ASSEMBLY – TYPE 2

of 70 04/14/2017 Rev. 07/07/2017

DESCRIPTION:

This work shall consist of furnishing, installing and testing of Parking Space Sign (PSS) Assemblies at locations indicated in the Contract Documents or as directed by the Engineer. The Parking Space Sign Assembly shall consist of a static sign panel with an LED line or character matrix variable message sign assembly, the associated sign controller, bracket supports, cabling and all necessary assembly hardware. The two types of Parking Space Sign assemblies are identical in all respects except for the size of the sign panel. MATERIALS:

Requirements The Type 1 Parking Space Sign shall consist of one line of four characters, eighteen (18) inch tall, and the Type 2 Parking Space Sign shall consist of one line of four characters, twelve (12) inch tall. Either character or line matrix technology may be proposed. Access to the sign shall be from the front. The size of the sign panel and orientation of the four-character line shall be as shown in the Contract Documents. The following requirements apply to both the Type 1 and the Type 2 signs except where explicitly noted.

1 Quality Assurance Requirements

The manufacturer of the LED Parking Space Sign Assembly shall meet the following requirements:

1.1 ISO 9001 Certified.

1.2 Experience:

The sign manufacturer shall have installed in North America a minimum of forty signs of similar technology that have been successfully operating for at least four years and have been installed as part of at least five separate projects.

As part of the thirty day submission, the Contractor shall submit proof of compliance with their experience requirements. This shall include, but not be limited to, a list of sign installations with photographs and names, addresses and telephone numbers of operating personnel who can be contacted regarding the signs. If requested by the Engineer, the Contractor shall arrange for a demonstration of an installed sign from the proposed manufacturer.

2 General Requirements

The LED Parking Space Sign Assembly of the type specified in the Contract Documents shall meet the following requirements:

2.1 Power: Each sign will receive either 120 VAC, 208 VAC, or 240 VAC, as indicated on the contract documents. A transformer shall be provided, if required, to provide the voltage required by the sign and electrical outlets in the cabinet. The cost for the transformer shall be included in this pay item.

2.2 The equipment shall meet all of its specified requirements when the supply voltage indicated in §2.1 is within ±15%, 60 ±1 Hz, 3-wire single phase plus ground.

2.3 Electrical

2.3.1 All wiring interconnecting individual components or assemblies shall be modular


of 70 04/14/2017 Rev. 07/07/2017

harness assemblies and shall be mechanically keyed to prevent insertion into wrong socket or connector.

2.3.2 Signals that could adversely affect any other electrical or electronic device, as per FCC rule Part 15, Class B shall be provided.

2.3.3 The presence of ambient noise generated within 1 foot of any of the components of the PSS shall not adversely affect the performance of the PSS. The sources of ambient noise shall include, but not be limited to, radio signals, magnetic or electromagnetic interface, including those from power lines, roadway lights, transformers or motors.

2.3.4 120 Volt, 15 Amp Quadraplex outlets shall be provided for communications equipment and other equipment, and a 120 Volt, 15 Amp GFI outlet shall be provide for use by maintenance personnel. A transformer shall be provided to obtain the proper voltage if necessary.

2.4 Mechanical:

2.4.1 Fabrication shall be such that performance shall not be impaired after the equipment has been subjected to shock and vibration caused by normal installation, transportation and maintenance handling.

2.4.2 Particular attention shall be given to neatness and thoroughness of soldering, wiring, welding, plating, riveting, finishes and machine operations.

2.5 The equipment shall meet all operational requirements under the following environmental conditions:

Temperature Range: -30° F to +140° F.

Humidity: 5 to 95% noncondensing

3 Static Sign

The sign dimensions, message, character size and mounting configuration shall be as shown in the Contract Documents with Class B Reflective Sheeting used. Signs, brackets and mounting posts furnished as part of these items shall meet the following requirements:

3.1 §730-01 Aluminum Sign Panels 3.2 §730-05 Reflective Sheeting - ASTM Type III (Class B) 3.3 §730-12 Reflectorized Sheeting Sign Characters (Type IV) 3.4 §730-22 Stiffeners, Brackets and Miscellaneous Hardware

4 Variable Message Sign Assembly

The PSS shall consist of tri-color (R+G) Light Emitting Diode (LED) pixel based matrix modules arranged to form a character matrix display or line matrix display, the sign controller and associated electronics. The PSS modular display shall contain the number of characters specified in Section 4.1.

For Type 1 signs, the nominal height of each character shall be 18 inches high and 12 inches wide


of 70 04/14/2017 Rev. 07/07/2017

(when measured from the bottom most edge of the lowest pixel to the top most edge of the upper pixel in the character matrix using) a 7x5 pixel matrix for each character. If a line matrix is used, it shall have a height of 18 inches and a width to allow for four (4) characters per line.

For Type 2 signs, the nominal height of each character shall be 12 inches high and 8 inches wide (when measured from the bottom most edge of the lowest pixel to the top most edge of the upper pixel in the character matrix using) a 7x5 pixel matrix for each character. If a line matrix is used, it shall have a height of 12 inches and a width to allow for four (4) characters per line.

4.1 The character modules shall be mounted in housing as described in Section 3. Each Sign Assembly shall consist of one lines. Each line shall consist of either one line matrix module or of three character-modules. The 4 character assembly should be enclosed in its own enclosure.

4.2 Orientation of the lines shall be as shown in the Contract Documents.

4.3 All pixel modules, assemblies, and components compatible and interchangeable between signs provided under this item.

4.4 The replacement of any display module, or pixel on a display module, shall not require any other unit to be removed, and shall not require the use of any special tools. All display modules shall be replaceable from the front of the sign assembly.

4.5 Each pixel shall be individually addressable and controllable to allow for the display, on any portion of the message face, of static text or the flashing of all or any part of the text, together with message formation by alternating between two or more static or flashing text messages.

4.6 The electronics for the PSS shall be fully configured to drive the total required number of LEDs. The failure of any one pixel shall not affect the operation of any other pixel.

4.7 The power driver circuitry shall be designed to minimize power consumption.

4.8 Each pixel shall be comprised of a symmetrical cluster of LEDs.

4.9 LED lighting source for the pixels shall be as follows:

4.9.1 Each pixel shall be capable of displaying either red, amber, or green. Each pixel shall consist, at a minimum, of a red LED and a green LED (R+G). An additional blue LED is allowed, but not required.

4.9.2 Red LEDs shall utilize AlInGaP semiconductor technology, and shall emit red light that has a peak wavelength of 625 ± 10 nm.

4.9.3 Green LEDs shall utilize InGaN semiconductor technology and shall emit green light that has a peak wavelength of 525 ± 10 nm.

4.9.4 The quantity of LEDs used in each pixel shall be sufficient to provide a minimum pixel output of 19.5 candelas for any available color at full brightness.

4.9.5 LED grouping and mounting angle shall be optimized for maximum readability.

4.9.6 LEDs shall have a 30o viewing cone with a half power angle of 15o measured from the longitudinal axis of the LED.


of 70 04/14/2017 Rev. 07/07/2017

4.9.7 The LED mean time before failure (MTBF) shall be a minimum of 100,000 hours of permanent use at an operating temperature of 140° F, when driven at the specific forward current used for normal daylight LED PSS display operation. Where failure is defined as a maximum drop in candela output of 70% over 100,000 hours.

4.9.8 The Contractor shall provide LED manufacturer’s data to the Engineer on the LEDs intended for the signs in this Contract.

4.9.9 As part of the LED manufacturer’s technical specification sheet submittal, the specific forward current shall be noted.

4.9.10 Each LED shall be individually installed and separately connected to the circuit board (display module).

4.9.11 The LEDs used in the display shall be obtained from batches sorted for luminous output, where the highest luminosity LED in the batch shall not be more than fifteen percent (15%) more luminous than the lowest luminosity LED in the batch.

4.9.12 To ensure uniformity of display and operational life, all LEDs used to make up a display module shall be obtained from the same manufacturing batch. The Contractor shall submit LED manufacturer’s certification identifying the batch and bin numbers of the LEDs used.

4.9.13 Monitoring of each pixel by the PSS controller for subsequent transmission of pixel status information to the control center.

4.10 The LED display modules shall be protected from degradation due to sunlight. The method and design of the LED PSS sunlight protection shall be approved by the Engineer.

5 PSS Enclosure

The PSS sign enclosure shall as a minimum house the LED display modules and the light sensors. One or more enclosures may be proposed based on the sign configuration specified in the Contract Documents. The enclosure(s) shall open from the front of the sign assembly and shall meet the following requirements:

5.1 The housing shall conform to the requirements of a NEMA 3R enclosure.

5.2 The maximum exterior depth of the enclosure shall be 9 inches. The maximum height and width shall be as shown in the contract drawings.

5.3 The enclosure shall be constructed of aluminum alloy 6061-T6 or 5052-H32 for the internal structural members and aluminum alloy 5052-H32 exterior skin or as specified on approved shop drawings. The minimum thickness shall be 0.1 inch. Seams shall be continuously welded by an inert gas process only in the shop.

5.4 The enclosure shall protect internal components from rain, dust, ice and corrosion in accordance with NEMA Type 3R standards as described in NEMA Standards Publication 250-2003, Enclosures for Electrical Equipment. All gaskets shall be fabricated out of neoprene.

5.5 All hinged access panels and windows shall be equipped with hold-open devices either mechanical or gravitational which shall not release accidentally or by the action of wind. The


of 70 04/14/2017 Rev. 07/07/2017

hold-open devices shall not interfere with the operation of the display, nor with the repair or replacement of user serviceable components.

5.6 The enclosure shall be constructed to present a clean, neat appearance. Seals, baffles and screens to prevent the entry of water, dust and insects shall be used, as required to protect equipment located within the housing from moisture, dust, dirt and corrosion.

5.7 Any interior metal cage support frames required to mount the display elements shall be non-corrosive and shall withstand and minimize vibration when the sign is mounted with the number of display elements specified in these Contract Documents.

5.8 A weatherproof, secure front access lift face shall be provided to provide access to all replaceable components within the enclosure.

5.9 The lift face shall be lockable from the outside to prevent intrusion or vandalism

5.10 The lift face(s) status shall be monitored with an electrical contact(s), such that the contact shall be closed when the lift face is closed and open when the lift face is open. The contact(s) shall be wired to the PSS controller and shall cause a bit to be set in the status message returned to the CCS (Central Control System) when the contact is open.

5.11 Either a device shall be provided or gravity used to hold the lift face open in a 90 degree or greater position.

5.12 When multiple enclosures are used, the enclosures shall be mounted such that when the front face of one panel is opened, it shall not come in contact with the front face of an adjacent panel.

5.13 The locks shall be keyed the same as the locks provided in other items of this contract. Two keys shall be provided to the Engineer for each lock.

5.14 The front face of the PSS enclosure shall be extended beyond the message area of the sign, as indicated in the Contract Documents, creating a blank, flat black border area that is integral to the housing. Add-on elements to create the border are not allowed.

5.15 All exterior seams shall be continuously welded by an inert process only in the shop such that each weld has a uniform flow. Welding shall be in accordance with ANSI/AWS D1-2/D1.2M, Structural Welding Code-Aluminum.

5.16 Louvered vents shall be provided on both sides of the enclosure and below the enclosure, as necessary, to provide sufficient ventilation. All fans or other forced air devices, if necessary for operation of the sign over its specified operating temperature range, shall be thermostatically controlled and shall use standard-size removable dust filters. The dust filters shall be rated MERV (Minimum Efficiency Reporting Value) 8. All fans shall have ball or roller bearings.

5.17 Screened weep holes shall be provided at each corner of the enclosure(s) to allow the drainage of any water that may collect in the housing.

5.18 All metallic exterior surfaces visually exposed to motorist traffic, including the face (lens panel aluminum mask), top, bottom and sides extending forward of the static sign panel as indicated in the Contract Documents are to be coated with a matte-black Kynar 500 finish or semi-gloss automotive grade acrylic urethane finish. The finish shall be uniform in


of 70 04/14/2017 Rev. 07/07/2017

appearance and completely free from gouges and any other flaws or defects.

All other exterior surfaces, extending behind the static sign panel, as indicated in the Contract Documents, shall be a natural aluminum mill finish. All interior surfaces shall be a natural aluminum mill finish.

5.19 The pixels within the message area of the sign shall be covered and protected with a UV stabilized polycarbonate front panel. The panel shall be a minimum of 1/4 inch thick. The front panel shall be mounted to withstand applicable wind load criteria specified in §30.27, Permanent Variable Message Signs, without deflecting sufficiently to obscure any of the pixels in the sign. The panel shall be replaceable and shatter resistant.

5.20 The lens panel shall be heated to prevent fogging, frost or ice and snow build-up.

5.21 All internal diagonals and other structural supports shall be spaced so as not to interfere with the maintenance or replacement of any of the components mounted within the sign.

5.22 Markings: The contract number, pay-item number, and month and year of installation shall be marked using permanent ink, paint or stamping into the wall. Characters shall be 1-1 3/4 inches high, horizontal when the variable message sign is in its final position, and be located on the inside near the middle of the panel opposite the lift face. The markings shall not be visible when viewing the LED Parking Space Sign Assembly head-on.

5.23 The manufacturer’s name, product name, model number, serial number, and city and state or province of manufacturer shall be permanently marked on the outside and an easily accessible location inside the enclosure.

6 PSS Controller

Each sign shall be operated by a microprocessor-based controller that provides the electronics necessary to receive and interpret commands from the Central Control System (CCS), provided by others, to issue a response to the CCS, and to display messages on the sign. The PSS controller shall be housed in a cabinet provided as part of this item. The cabinet shall be ground mounted, pole mounted, or mounted on the sign structure, as indicated in the contract documents. The PSS controller shall meet the following requirements:

6.1 Designed to mount in a standard 19-inch rack, occupying a maximum of 10U rack space with a depth not exceeding 15 inches.

6.2 Support TCP/IP communications between the CCS and the PSS controller.

6.3 Communications Interface:

6.3.1 Provide two NTCIP-compatible Ethernet ports for communication between the sign controller and the CCS or a local laptop, with each port connected to a separate communication channel through an external communications device. The controller shall respond to the last command received, which may be on

either channel, and respond on both channels. The CCS will only transmit commands over one channel at a time.

6.3.2 Provide an NTCIP-compatible RS-232 port for communication between the sign controller and a local laptop (provided under a separate bid item) for configuration,


of 70 04/14/2017 Rev. 07/07/2017

running diagnostics, selecting messages, monitoring status and downloading/uploading messages through a direct null-modem connection.. A password must be entered for commands from the notebook to be considered valid.

6.3.3 The Ethernet ports shall have a standard RJ45 connector.

Communications on Ethernet ports shall comply with NTCIP 2104 and NTCIP 2202 Internet transport profile. This shall permit the controller to be operated on any typical Ethernet network using the TCP/IP and UDP/IP protocols. The IP address shall be configurable.

For the serial port, the baud rate, connection type, and NTCIP communication protocol shall be configurable. The baud rate for each port for each of the serial ports shall be settable to any typical serial baud rate ranging from 1200 to 115,200. The serial port shall be capable of supporting either of the following sub network profiles: NTCIP 2101 (PMPP) or NTCIP 2103 (PPP). It shall also be capable of supporting either NTCIP 2201 (Null) or NTCIP 2202 (Internet) profiles. Only one each of the transport and sub network profiles shall be active at any time on each port. The default settings of the serial port shall be as follows:

Port

Baud Rate

Connection Type

NTCIP Sub network

NTCIP Transport

Local 9600 Direct NTCIP 2103 – PPP NTCIP 2201 – Null

6.4 Communications between the PSS controller and the CCS and notebook computer shall comply with the NTCIP as detailed in the following NEMA Standards Publications:

6.4.1 NTCIP 1101:1996 and Amendment 1 – Simple Transportation Management Framework (STMF)

6.4.2 NTCIP 1102 v1.12 – Octet Encoding Rules (OER) Based Protocol

6.4.3 NTCIP 1201 v02.32 – Global Object (GO) Definitions

6.4.4 NTCIP 1203:1997 and Amendment 1 – NTCIP Object Definitions for Dynamic Message Signs

6.4.5 NTCIP 2001 v01.19 – NTCIP Class B Profile

6.4.6 NTCIP 2101:2001 – Point-to-MultiPoint Protocol (PMPP) Using RS-232 Subnetwork Profile

6.4.7 NTCIP 2103 v1.13 – Point-to-Point Protocol Over RS-232 Subnetwork Profile

6.4.8 NTCIP 2201 v1.15 – Transportation Transport Profile

6.4.9 NTCIP 2202:2001 – Internet (TCP/IP and UDP/IP) Transport Profile

6.4.10 NTCIP 2301 – AP-STMF (Simple Transportation Management Framework)

6.5 Unless otherwise stated in these Contract Documents, the software shall comply with the versions of the NTCIP standards that are current at the date of Contract award.


of 70 04/14/2017 Rev. 07/07/2017

6.6 As part of the 30-day submission the PSS manufacturer shall submit details of the specific standards to be implemented, applicable conformance groups, applicable data objects and their associated range values, and any other information, including, but not limited to manufacturer specific MIBs, that are pertinent to the implementation of this specification.

6.7 Have sufficient non-volatile memory for downloading and uploading messages, and configuration, status, and alarm data as specified herein.

6.8 Storage of all local messages and configuration parameters in non-volatile memory that shall not be affected by complete loss of power at any point in its operation.

6.9 Perform all messaging operations, including but not limited to flashing on and off, writing any message at a minimum effective rate of 60 characters per second.

6.10 Incorporate a watchdog timer to detect an out-of-program condition and reset the microprocessor.

6.11 Operate on a TCP/IP network, with a user-assigned and user-adjustable IP address.

6.12 Provide a means for the user to configure I/O parameters. The I/O configuration shall be stored in non-volatile memory, and may be changed either at the controller or via the CCS.

6.13 Designed for fail-safe prevention of improper information display in the case of malfunction. As a minimum, this shall include an automatic blanking feature that immediately clears the message displayed on the sign in the event of a power failure, communication failure or invalid transmission from the CCS.

6.14 Diagnostic software to detect and identify failed pixels, display drivers, power supplies, and alarm conditions shall be provided.

6.15 Have a local control mode where the following operations may be initiated:

6.15.1 Operator selection of dimming levels

6.15.2 Operator selection of configuration parameters

6.15.3 Diagnostic routines capable of testing full sign operation

6.16 Provide a switch on the front of the PSS controller to activate local control and a keypad and menu- driven LCD display on the controller's front panel to select the operations. The switch must be in the local position to permit entry from the keypad.

6.16.1 A valid password must be entered to permit local entry.

6.16.2 A timeout function shall be provided such that if no activity is detected from any of the local control interfaces within a user specified time, the PSS shall revert to the remote controlled mode.

6.16.3 While in the local control mode, the CCS software will continue to monitor the sign's status and display. The PSS controller, however, shall not respond to any commands from the CCS while in local control mode.

6.17 The sign controller’s front panel shall be capable of performing the following functions with the sign controller and the PSS:

6.17.1 Monitor the current status of the sign controller, including the status of all


of 70 04/14/2017 Rev. 07/07/2017

sensors and a representation of the message visible on the display face.

6.17.2 Perform diagnostics testing of various system components, including pixels, power systems and sensors.

6.17.3 Activate messages stored in memory.

6.17.4 Configure display parameters, including display size, colors, and communications.

6.18 The front panel interface shall also include:

6.18.1 Power switch to turn the controller on and off and an LED “on” indicator.

6.18.2 A “local/remote” switch with an LED indicator that places the controller in local mode such that it can be controlled from the front panel interface, instead of via the primary communication channel.

6.18.3 Reset switch to quickly restart the controller.

6.18.4 LED “Active” indicator blinks when the controller is operating.

6.18.5 LED to indicate when any of the NTCIP communication channels are active.

6.19 Provide for the continuous monitoring of the temperature within the sign enclosure and automatically activate the enclosure’s ventilating system, if required, when the temperature exceeds a user defined limit. If the temperature exceeds a second user defined temperature limit, an error condition shall be generated and reported to the TMC when the sign is polled. If a manufacture’s set temperature limit is exceeded, the sign shall automatically shut down and an error condition shall be generated and reported to the TMC when the sign is polled.

7 Sign Dimming System

Each sign shall be provided with a system that senses the background ambient light level and provides field- adjustable intensities (dimming). Pixel luminance levels shall be controlled both directly (through operator input) and automatically (based on ambient light levels obtained from the photocells).

The sign dimming system shall meet the following requirements:

7.1 It shall consist of commercially available photo-electric sensors either installed in watertight metal enclosures on the sign enclosure(s) or as part of the LED displays. The method of dimming shall produce a consistent intensity level across all of the LED displays used to make up the sign assembly. If the photoelectric sensors are mounted on the sign enclosure, it shall be placed in an easily accessible location for maintenance, as approved by the Engineer and shall be capable of having its aiming angle adjusted.

7.2 Each of the photo-electric sensors shall be capable of being continually exposed to direct sunlight without impairment of performance.

7.3 Luminance levels shall be stored in the PSS Controller and shall be adjustable, in a range of 3% to 100%, on either:

7.3.1 A continuous logarithmic basis, to match the normal human eye luminous


of 70 04/14/2017 Rev. 07/07/2017

response characteristic.

7.3.2 A half incremental dimming basis, where each lower dimming level is half the previous level.

7.4 Dimming sign circuitry shall be provided to select an illuminance level based on the ambient light sensed by the photocells and a lookup table of intensity level vs. photocell reading. A minimum of 100 intensity levels shall be supported.

7.5 The lookup tables shall be downloadable from the CCS. Each row shall contain a range of photocell readings.

7.6 The dimming level selected shall be determined by the row whose range corresponds to the sensed level of ambient light.

7.7 Overlap shall be provided in the table’s ranges to prevent flickering of the sign caused by subtle changes in the ambient light.

7.8 The intensity levels shall be adjustable by means of a software control through the field controller, or other method approved by the Engineer.

7.9 Continuous current drive shall be used at the maximum brightness level and at all lower levels of brightness.

7.10 The current used for maximum brightness shall not exceed the current used to achieve the rated MTBF. The current used for maximum brightness shall be indicated as part of the shop drawing submittal.

7.11 The LED dimming circuit shall incorporate temperature controlled dimming, which shall reduce the current through the LEDs based on the temperature inside the sign enclosure, such that the LED current does not exceed the rated LED current at that temperature.

7.12 If the temperature of the sign exceeds the rated operating temperature of the LEDs, the sign shall blank-out until the temperature has returned to safe operating levels.

7.13 A complete schematic of the LED display power, driver and dimming circuits shall be provided for approval by the Engineer.

8 Power Supplies

8.1 The LED display shall be operated on DC voltage.

8.2 Multiple power supplies shall be provided and employed such that the failure of any individual power supply does not inhibit full operation of the PSS.

8.3 The quantity of power supplies shall also provide at least 50% spare capacity over that required to light every pixel of the LED PSS. The Contractor shall provide details of methodology proposed for the integration of the spare capacity to Engineer for approval

8.4 All power supply voltages shall be continuously measured by the sign controller. The sign controller shall provide these voltage readings to the central controller or laptop computer when the sign controller is polled by the CCS or notebook computer.

8.5 The PSS Controller shall have either redundant power sources or a backup UPS/battery wired so that the failure of one power source shall not interrupt the operation of the controller


of 70 04/14/2017 Rev. 07/07/2017

8.6 The power supplies shall be short circuit protected. They shall also have suitable overcurrent protection devices and shall reset automatically after 5 seconds of AC power off.

8.7 Power supplies shall be UL listed, have an efficiency rating of 80% minimum, and operate over an ambient temperature range of -30 degrees Fahrenheit to +140 degrees Fahrenheit.

9 Electrical Circuit Protection

9.1 Circuit breakers shall be installed in the controller cabinet. Payment for these breakers shall be included in the cost bid for this PSS item. The main breaker shall protect the cabinet and the sign enclosure and shall be rated for 30 amps. Activation of the main breaker shall result in the removal of all power from the cabinet and sign enclosures. All breakers shall be approved and listed by the UL. The operating mechanism shall be enclosed, trip free from the operating handle on overload and trip indicating. Contacts shall be silver alloy enclosed in an arc quenching chamber. Breakers shall have a minimum interrupt capacity of 5000 A. Thermal magnetic breakers are not acceptable.

Secondary breakers shall be installed to protect the following circuits:

9.1.1 To protect the equipment in the controller cabinet.

9.1.2 As required to energize the PSS enclosure.

9.1.3 15 amps for the maintenance lights.

9.1.4 15 amps for the maintenance outlets.

9.1.5 15 amps for communications equipment.

9.2 Appropriate devices shall be installed in the sign enclosure and local control cabinets to protect all external cabling entering the controller cabinet and sign housing from over- voltage situations, such as lightning strikes and power surges over the lines. The surge protectors shall be grounding in accordance with the manufacturer’s recommendation. Circuitry protection shall include, but not limited to the following:

9.2.1 Overcurrent protection devices. All AC power circuit(s) to the LED PSS and associated control equipment enclosures shall be protected by Ground Fault Circuit Interrupting type devices.

9.2.2 Surge protector to guard against circuit damage resulting from voltage surges on all incoming power lines. The surge suppressor shall meet the following minimum specifications:

9.2.2.1 Working voltage rating: 130 Vrms, each leg to ground.

9.2.2.2 Surge voltage: Limit the surge voltage applied to the equipment to 650 V peak while conducting a peak surge current of 20,000 A. The peak surge current shall be an 8x20 us unsymmetrical triangle wave.

9.2.2.3 Response Time: 5 nanoseconds.

9.2.2.4 Occurrences: 20 times at peak current.


of 70 04/14/2017 Rev. 07/07/2017

9.2.2.5 Maximum Series Inductance: 200 micro henries.

9.2.3 Data Line protectors to guard against circuit damage resulting from voltage surges on all data/communication lines between the sign enclosures and controller cabinet if applicable.

10 Central Control of the PSS

The PSS system uses a poll-response method of communications over a multi-drop channel or link. The CCS (Central Control System) initiates all communications and only one PSS controller on the channel will respond to a command from the CCS. Each controller on a channel is given a unique drop address. One drop address is reserved as a broadcast address. All controllers on a channel listen to transmissions to the broadcast address, but no controllers respond, thus avoiding any conflicts on the channel.

10.1 The IP address shall be user configurable, stored in non-volatile memory, and may be changed only at the controller.

10.2 For message creation, the PSS, PSS sign controller, and PSS control software shall

support the storage and use of a minimum of two (2) alphanumeric character font files. Each font file shall include the following characters:

10.2.1 The letters “A” through “Z”, in both upper and lower case

10.2.2 Decimal digits “0” through “9”

10.2.3 A blank or space

10.2.4 Eight (8) directional arrows

10.2.5 Punctuation marks, such as: .,!?-‘’ “”

10.2.6 Other characters, such as: #&*+/( )[ ] < >

10.3 The following character font file shall be supplied with the PSS, at a minimum:

o 7x5 Single Stroke – a typical font is seven (7) pixel rows high by five (5) pixel columns wide and has a single-pixel stroke width.

o 7x4 Single Stroke – a typical font is seven (7) pixel rows high by four (4) pixel columns wide and has a single-pixel stroke width.

11 NTCIP

11.1 Each NTCIP Component covered by these project specifications shall implement the most recent version of the standard that is at the stage of “Recommended” or higher as of

the date of this letting, including any and all Approved or Recommended Amendments to these standards as of the letting date. It is the ultimate responsibility of the sign manufacturer to monitor NTCIP activities to discover any more recent documents.

11.2 Variable Message Sign assemblies shall be compliant with the latest version of the NTCIP

Standards, as defined by AASHTO, ITE, and NEMA.


of 70 04/14/2017 Rev. 07/07/2017

11.3 SUBNETWORK PROFILES

11.3.1 Each serial or modem port on each NTCIP device shall be configurable to support both NTCIP 2101 and NTCIP 2103. Only one of these profiles shall be active at any given time. Serial ports shall support external dial-up, leased line, radio, cellular and fiber optic modems.

11.3.2 The NTCIP device(s) may support additional Subnet Profiles at the manufacturer’s option. At any one time, only one subnet profile shall be active on a given port of the NTCIP device. All response datagram packets shall use the same transport profile used in the request. The NTCIP device shall be configurable to allow a field technician to activate the desired subnet profile and shall provide a visual indication of the currently selected subnet profile.

11.4 TRANSPORT PROFILES

11.4.1 Each serial or modem port on each NTCIP device shall be configurable to support both NTCIP 2201 and NTCIP 2202.

11.4.2 Each Ethernet port on the NTCIP device shall comply with NTCIP 2202.

11.4.3 The NTCIP device(s) may support additional transport profiles at the manufacturer’s option. Response datagrams shall use the same transport profile used in the request. Each NTCIP device shall support the receipt of datagrams conforming to any of the supported transport profiles at any time.

11.5 APPLICATION PROFILES

11.5.1 Each NTCIP device shall comply with NTCIP 2301 and shall meet the requirements for Conformance Level 1.

11.5.2 An NTCIP device may support additional application profiles at the manufacturer’s option. Responses shall use the same application profile used by the request. Each NTCIP device shall support the receipt of application data packets at any time allowed by the subject standards.

11.5.3 The following conformance groups within the NTCIP 1203:1997 and Amendment 1 standard shall be supported with the values defined in these tables. For the purposes of this specification NTCIP 1203 Conformance Statements shall be considered mandatory, except where noted.

11.6 Each NTCIP device shall support all mandatory objects in all optional conformance groups that are required herein. All optional objects listed in these specifications as mandatory, shall be supported.

11.7 CONFORMANCESTATEMENTS Reference Conformance

Configuration NTCIP 1201:1996 Mandatory Time Management NTCIP 1201:1996 Mandatory Timebase Event Schedule NTCIP 1201:1996 Mandatory Report NTCIP 1201:1996 Mandatory STMF NTCIP 1201:1996 Optional


of 70 04/14/2017 Rev. 07/07/2017

PMPP NTCIP 1201:1996 Mandatory Sign Configuration NTCIP 1203:1997 Mandatory GUI Appearance NTCIP 1203:1997 OptionalFont Configuration NTCIP 1203:1997 Mandatory VMS Sign Configuration NTCIP 1203:1997 Mandatory MULTI Configuration NTCIP 1203:1997 Mandatory Message Table NTCIP 1203:1997 Mandatory Sign Control NTCIP 1203:1997 Mandatory Default Message Control NTCIP 1203:1997 OptionalPixel Service Control NTCIP 1203:1997 OptionalMULTI Error Control NTCIP 1203:1997 Mandatory

Illumination/Brightness Control NTCIP 1203:1997 Mandatory Scheduling NTCIP 1203:1997 Mandatory Auxiliary I/O NTCIP 1203:1997 Mandatory Sign Status NTCIP 1203:1997 Mandatory Status Error NTCIP 1203:1997 Mandatory Pixel Error Status NTCIP 1203:1997 Mandatory Fan Error Status NTCIP 1203:1997 Mandatory Temperature Status NTCIP 1203:1997 Mandatory

Note: In the following tables where a value differs for a character matrix and a line matrix sign, the line matrix value will be indicted in brackets - [value].

11.8 SIGN CONFIGURATION CONFORMANCE GROUP

MIB Object Or Table Name NTCIP Reference

NYSDOT Specification Reference

Expected Value

2.2.1.1.1.1 dmsSignAccess NTCIP 1203:1997 5.8 32.2.1.1.1.2 dmsSignType NTCIP 1203:1997 4 4 [5]2.2.1.1.1.8 dmsBeaconType NTCIP 1203:1997 - 3

11.9 FONT CONFIGURATION CONFORMANCE GROUP

MIB

Object Or Table Name

NTCIP Reference


Expected Value

2.4.1.1.1.1 numFonts NTCIP 1203:1997 10.3 8..2552.4.1.1.1.2 fontTable NTCIP 1203:1997 10.3 Sequence2.4.1.1.1.3 maxFontCharacters NTCIP 1203:1997 10.3 1..655352.4.1.1.1.4 characterTable NTCIP 1203:1997 10.3 Sequence

11.10 VMS SIGN CONFIGURATION CONFORMANCE GROUP


of 70 04/14/2017 Rev. 07/07/2017

MIB


NTCIP Reference


Expected Value

2.3.1.1.1.1 vmsCharacterHeightPixels NTCIP 1203:1997 4 72.3.1.1.1.2 vmsCharacterWidthPixels NTCIP 1203:1997 4 5 [0]2.3.1.1.1.3 vmsSignHeightPixels NTCIP 1203:1997 4 27..655352.3.1.1.1.4 vmsSignWidthPixels NTCIP 1203:1997 4 120..655352.3.1.1.1.5 vmsHorizontalPitch NTCIP 1203:1997 4 0..682.3.1.1.1.6 vmsVerticalPitch NTCIP 1203:1997 4 0..68

11.11 MULTI CONFIGURATION CONFORMANCE GROUP

MIB


NTCIP Reference


Expected Value

2.5.1.1.1.1 defaultBackgroundColor NTCIP 1203:1997 5.14 02.5.1.1.1.2 defaultForegroundColor NTCIP 1203:1997 4.9.1 92.5.1.1.1.3 defaultFlashOn NTCIP 1203:1997 - 1..992.5.1.1.1.4 defaultFlashOff NTCIP 1203:1997 - 1..992.5.1.1.1.5 defaultFont NTCIP 1203:1997 10.3 1..2552.5.1.1.1.6 defaultJustificationLine NTCIP 1203:1997 - 42.5.1.1.1.7 defaultJustificationPage NTCIP 1203:1997 - 1..42.5.1.1.1.8 defaultPageOnTime NTCIP 1203:1997 - 1..2552.5.1.1.1.9 defaultPageOffTime NTCIP 1203:1997 - 0..2552.5.1.1.1.10 defaultCharacterSet NTCIP 1203:1997 - 1,2

11.12 MESSAGE TABLE CONFORMANCE GROUP

MIB


NTCIP Reference


Expected Value

2.6.1.1.1.1 dmsNumPermanentMsg NTCIP 1203:1997 - 0..655352.6.1.1.1.2 dmsNumChangeableMsg NTCIP 1203:1997 - 0..655352.6.1.1.1.3 dmsMaxChangeableMsg NTCIP 1203:1997 - 128..655352.6.1.1.1.4 dmsFreeChangeableMemor NTCIP 1203:1997 - 0..4294967292.6.1.1.1.5 dmsNumVolatileMsg NTCIP 1203:1997 - 0..655352.6.1.1.1.6 dmsMaxVolatileMsg NTCIP 1203:1997 - 0..655352.6.1.1.1.7 dmsFreeVolatileMemory NTCIP 1203:1997 - 0..4294967292.6.1.1.1.8 dmsMessageTable NTCIP 1203:1997 Sequence2.6.1.1.2 dmsValidateMessageError NTCIP 1203:1997 - 1..5

11.13 SIGN CONTROL CONFORMANCE GROUP

MIB


NTCIP Reference


Expected Value

2.7.1.1.1.1 dmsControlMode NTCIP 1203:19975 1..6


of 70 04/14/2017 Rev. 07/07/2017

2.7.1.1.1.2 dmsSWReset NTCIP 1203:1997- 0..12.7.1.1.1.3 dmsActivateMessage NTCIP 1203:1997 Code2.7.1.1.1.4 dmsMessageTimeRemaining NTCIP 1203:1997- 0..655352.7.1.1.1.5 dmsMsgTableSource NTCIP 1203:1997- MessageIDCo2.7.1.1.1.6 dmsMsgRequesterID NTCIP 1203:1997- IP Address2.7.1.1.1.7 dmsMsgSourceMode NTCIP 1203:1997- 1..142.7.1.1.1.8 dmsShortPowerRecoveryMessage NTCIP 1203:19975.14 MessageIDCo2.7.1.1.1.9 dmsLongPowerRecoveryMessage NTCIP 1203:19975.14 MessageIDCo2.7.1.1.1.10 dmsShortPowerLossTime NTCIP 1203:1997 0..65535

2.7.1.1.1.11 dmsResetMessage NTCIP 1203:1997 MessageIDCo2.7.1.1.1.12 dmsCommunicationsLossMessage NTCIP 1203:19975.14 MessageIDCo2.7.1.1.1.13 dmsTimeCommLoss NTCIP 1203:19975.14 0..65535

2.7.1.1.1.14 dmsPowerLossMessage NTCIP 1203:19975.14 MessageIDCo2.7.1.1.1.15 dmsEndDurationMessageParamet NTCIP 1203:1997 MessageIDCo2.7.1.1.1.16 dmsMemoryMgmt NTCIP 1203:1997- 1..42.7.1.1.1.17 dmsActivateMsgError NTCIP 1203:1997- 1..9

11.14 MULTI ERROR CONFORMANCE GROUP

MIB


NTCIP Reference


Expected Value

2.7.1.1.1.18 dmsMultiSyntaxError NTCIP 1203:1997 - 1..122.7.1.1.1.19 dmsMultiSyntaxErrorPosition NTCIP 1203:1997 - 0..655352.7.1.1.1.20 dmsMultiOtherErrorDescriptio NTCIP 1203:1997 - 0..50

11.15 ILLUMINATION/BRIGHTNESS CONFORMANCE GROUP

MIB


NTCIP Reference


Expected Value

2.8.1.1.1.1 dmsIllumControl NTCIP 1203:1997 7.1 1..42.8.1.1.1.2 dmsIllumMaxPhotocellLevel NTCIP 1203:1997 7.3 0..655352.8.1.1.1.3 dmsIllumPhotocellLevelStatus NTCIP 1203:1997 7.4 0..655352.8.1.1.1.4 dmsIllumNumBrightLevels NTCIP 1203:1997 7.3 0..2552.8.1.1.1.5 dmsIllumBrightLevelStatus NTCIP 1203:1997 7.3 0..2552.8.1.1.1.6 dmsIllumManLevel NTCIP 1203:1997 7.9 0..2552.8.1.1.1.7 dmsIllumBrightnessValues NTCIP 1203:1997 7.4 Octet String2.8.1.1.1.8 dmsIllumBrightnessValuesErro NTCIP 1203:1997 - 1..62.8.1.1.1.9 dmsIllumLightOutputStatus NTCIP 1203:1997 7.4 0.65535


of 70 04/14/2017 Rev. 07/07/2017

11.16 SCHEDULING CONFORMANCE GROUP

MIB


NTCIP Reference

NYSDOT Specification Section Reference

Expected

Value

2.4.3.1 maxTimeBaseScheduleEntries NTCIP 1201:1996 - 0..655352.4.3.2 timebaseScheduleTable NTCIP 1201:1996 - Sequence2.4.4.2 maxDayPlanEvents NTCIP 1201:1996 - 1..2552.4.4.3 timeBaseDayPlanTable NTCIP 1201:1996 - Sequence2.4.4.4 dayPlanStatus NTCIP 1201:1996 - 0..255

2.9.1.1.1.1 numActionTableEntries NTCIP 1203:1997 - 0..2552.9.1.1.1.2 dmsActionTable NTCIP 1203:1997 Sequence

11.17 SIGN STATUS CONFORMANCE GROUP

MIB


NTCIP Reference

NYSDOT Specification Section Reference

Expected

Value

2.11.1.1.1.1 statMultiFieldRows NTCIP 1203:1997 - 0..2552.11.1.1.1.2 statMultiFieldTable NTCIP 1203:1997 - Sequence2.11.1.1.1.5 watchdogFailureCount NTCIP 1203:1997 5.11 Counter2.11.1.1.1.6 dmsStatDoorOpen NTCIP 1203:1997 4.10 0..255

11.18 STATUS ERROR SUBCONFORMANCE GROUP

MIB


NTCIP Reference


Expected Value

2.11.2.1.1.1 shortErrorStatus NTCIP 1203:1997 - 0..655352.11.2.1.1.10 controllerErrorStatus NTCIP 1203:1997 - 0..255

11.19 PIXEL ERROR STATUS SUBCONFORMANCE GROUP

MIB


NTCIP Reference


Expected Value

2.11.2.1.1.2 pixelFailureTableNumRows NTCIP 1203:1997 - 0..655352.11.2.1.1.3 pixelFailureTable NTCIP 1203:1997 Sequence2.11.2.1.1.4 pixelTestActivation NTCIP 1203:1997 5.15 1..4

11.20 Multi Tags


of 70 04/14/2017 Rev. 07/07/2017

11.20.1 Each NTCIP device shall support the following message formatting MULTI

tags. The manufacturer may choose to support additional standard or manufacturer-specific MULTI tags.

MULTI Tag Description

Fo Font

jl2 Justification - line left

Jl3 Justification - line center

Jl4 Justification - line right

11.21 Documentation

11.21.1 NTCIP documentation shall be provided on a CD-ROM and shall contain ASCII versions of the following Management Information Base (MIB) files in Abstract Syntax Notation 1 (ASN.1) format:

11.21.1.1 The relevant version of each official standard MIB modules referenced by the device functionality.

11.21.1.2 If the device does not support the full range of any given object within a standard MIB Module, a manufacturer specific version of the official standard MIB Module with the supported range indicated in ASN.1 format in the SYNTAX and/or DESCRIPTION fields of the associated OBJECT TYPE macro. The filename of this file shall be identical to the standard MIB Module except that it will have the extension “.man”.

11.21.1.3 A MIB module in ASN.1 format containing any and all manufacturer specific objects supported by the device with accurate and meaningful DESCRIPTION fields and supported ranges indicated in the SYNTAX field of the OBJECT- TYPE macros.

11.21.1.4 A MIB containing any other objects supported by the device

11.22 Acceptance Testing

11.22.1 The acceptance test will use the NTCIP Exerciser, Trevilon’s NTester, and Intelligent Devices’ Device Tester for NTCIP, or other testing tool approved by the Engineer. If the vendor implements any vendor-specific Multi tags, the VMS shall provide meaningful error messages within the NTCIP Standard DMS MIB 2.7.1.1.1.20 DMSMULTIOTHERERRORDESCRIPTION whenever one of these tags generates an error.

11.22.2 The VMS manufacturer will submit an NTCIP test plan to the Engineer a minimum of 90 days prior to NTCIP acceptance testing. NTCIP acceptance testing will be performed on one of the VMS manufactured under this contract. Testing will be performed at the manufacturer’s or agency’s facility.

11.23 Interpretation Resolution


of 70 04/14/2017 Rev. 07/07/2017

11.23.1 If the Engineer or PSS manufacturer discovers an ambiguous statement in the

standards referenced by this procurement specification, the issue shall be submitted to the NTCIP DMS Working Group for resolution. If the Working Group fails to respond within 90 days, the Engineer shall provide an interpretation of the specification for use on the project.

CONSTRUCTION DETAILS:

12 Installation

The Contractor shall install the LED Parking Space Sign Assemblies in accordance with the Contract Documents. This item shall include all sign modules, sign housing(s), PSS controller, fittings, grounding and all cabling in the sign, PSS controller, and between the sign and controller required for a fully operational PSS. Installation of the controller cabinet shall be included as part of this item. The exact installation locations shall be field staked and approved by the Engineer prior to the start of construction.

12.1 The permanent PSS shall be mounted to support structures as shown in the Contract Documents and as approved by the Engineer. Construction methods and details for the sign panel assembly shall be in accordance with §644-3, Sign Structures, Construction Details and Standard Drawings except as modified under this Contract to accommodate the installation of the Variable Message Sign (VMS) Assembly and the controller cabinet.

12.1.1 The Contractor shall submit shop drawings for the LED Parking Space Sign Assembly. The shop drawings shall include the proposed method of mounting the PSS Assembly and controller cabinet to the flat panel sign and sign posts and show the size of all members.

12.1.2 All structural steel elements shall be hot dipped and galvanized

12.2 Field measurements and adjustments to height/orientation shall be completed to ensure that minimum vertical clearance, as shown on the Contract Drawings, and legibility distances are achieved. Adjustments to the photosensor control thresholds shall be made to ensure the legibility distance is maintained under all ambient light conditions.

12.3 The Contractor shall make all power connections to the LED Parking Space Sign Assembly. All power shall be routed through the main circuit breaker in the controller cabinet. The neutral bus shall be isolated from the cabinet and equipment ground. The Contractor shall ground the sign in accordance with §680-3.12, Grounding. A direct ground wire shall be installed between the power distribution panel within the sign and the nearest ground rod. Grounding through the sign structure is not acceptable. The controller cabinet shall be grounded through the same ground rod.

12.4 The The Contractor shall connect the PSS controller and the modem of the type specified in the Contract Documents. Payment for installation of the modem and connection to either the optic fiber cable plant or to an antenna shall be paid for as part of other bid items. Where a fiber optic modem is specified, the connection to the fiber optic cable plant shall be through the fiber optic patch panel contained in the controller cabinet. Where


of 70 04/14/2017 Rev. 07/07/2017

fiber is installed, the fiber shall be neatly racked in the controller cabinet complying with the minimum bend radius for the cable. The optical fiber cable shall be fusion spliced to the patch panel pig tails. Slack fiber shall be stored in the patch panel. Where a wireless modem is installed, the Contractor shall install the antenna as shown in the Contract Documents.

12.5 All wire shall be cut to the appropriate length prior to installation. All cabling shall be neatly routed and tied back so as not to interfere with access to other cabling or equipment or maintenance of the sign. Doubling back of wiring is not permitted. All cabling shall be permanently identified as to its termination point.

12.6 All cable shields shall be grounded using an approved grounding termination kit.

12.7 After installation of all cables into the sign housing(s) and controller cabinet, all of the conduit entries shall be sealed with duct seal or an approved equivalent, to prevent water or rodent ingress.

12.8 The Contractor shall touch up all painted surfaces of the sign assembly that were scratched, chipped or damaged during installation with a matching color of paint.

13 Test Software

The Contractor shall provide test software that will run on a notebook computer under the Windows operating system to emulate the central software. This software shall permit downloading and uploading of the commands and responses through the Ethernet port of the PSS controller. Three copies of the test software on disk or CD-ROM shall be delivered to the Engineer.

14 Documentation

Sign Control Parameters

14.1 As part of the thirty-day submission, the Contractor shall include a definition of all required control parameters necessary for the proper operation of this sign and not defined in this document. These shall include but not be limited to the following:

14.1.1 Range and definition of photocell readings.

14.1.2 Diagnostic tests.

14.1.3 Error and status bits.

14.1.4 Manufacturer specific NTCIP data objects and their associated range values.

Shop Drawings 14.2 The Contractor shall submit ten (10) copies of manufacturer's shop drawings,

schematics, performance specifications, circuit descriptions, and catalog cut sheets to the Engineer for approval prior to ordering the piece of equipment.

14.2.1 The Contractor shall develop and deliver calculations, approved by a New York State Licensed Professional Engineer, demonstrating the PSS enclosure’s ability to withstand the design loads.

14.2.2 Included in the shop drawings shall be parts lists, schematics, wiring lists,


of 70 04/14/2017 Rev. 07/07/2017

mechanical details including material, dimensions, and finish, and assembly drawings.

14.2.3 The Contractor shall develop and deliver shop drawings approved by a licensed New York State Professional Engineer which illustrates, in detail, how to mount and connect the PSS enclosure to the structure shown in the plans.

14.2.4 The submission shall be of adequate detail for the Engineer to determine compliance with the specification and shall be neatly drawn and legible.

14.2.5 The submission shall be complete and clearly indicate the contract item number for which the submission is being made and the model or part number for which approval is being sought.

14.2.6 Incomplete submissions will be returned for re-submission.

14.2.7 Manuals

14.3 Manuals that detail the operation of the system shall be furnished as part of the LED Parking Space Sign Assembly.

14.3.1 User Manuals shall be provided for each system component. The User Manuals shall fully identify the system's, or the component's, features and functions and give detailed step-by-step instructions on how to operate and adjust the system or component and how to respond to system or component failures.

14.3.2 Operations Manuals shall be provided and shall, as a minimum, include:

14.3.3 Detailed description of normal system operation.

14.3.4 Detailed description of sign control software operation and procedures. The manual shall clearly describe all functions supported by the sign control software. The software operations manual shall be written for beginner personal computer users who are not familiar with detailed computer operations and terms. It shall contain step-by-step procedures with examples containing pictures of the computer screens.

14.3.5 Error and alarm handling procedures, including recovery from communications failures.

14.3.6 System start-up and shutdown procedures.

14.3.7 Detailed Maintenance Manuals shall be provided and shall, as a minimum, include.

14.3.7.1 Diagnostic routines for trouble shooting the system from the system computer and from each sign location. The manuals shall contain theory of operation, specifications, installation instructions, mechanical details, detailed alignment procedures, schematic drawings, photographs or drawings detailing component layouts, parts lists, including manufacturer's part numbers, and trouble shooting procedures for repair/replacement of all component parts, including printed circuit board replacement.


of 70 04/14/2017 Rev. 07/07/2017

14.3.7.2 All the requirements for the Operations manuals.

14.3.7.3 Detailed description of procedures for modifying the LED PSS, sign controller and sign control software configuration settings.

14.3.7.4 Description of operating procedures and troubleshooting procedures for each subsystem. This shall include step-by-step field and bench troubleshooting procedures to isolate and repair faults, as well as normal waveforms and test voltages.

14.3.7.5 Hard copy listing for all non-volatile or similar memory devices used in the equipment. The Contractor shall also supply complete instructions for the hardware and software equipment that shall enable NYSDOT to change, add and delete messages stored in non-volatile memory.

14.3.7.6 As installed color-coded interconnection wiring diagrams, both "factory" and "field."

14.3.7.7 Equipment wiring and all circuit board schematic diagrams indicating "factory" and "field" wiring. This shall include drawings showing the physical location of each component, as well as logic diagrams and stage-by-stage explanation of the circuit theory for each circuit board.

14.3.7.8 Complete nomenclature and commercial number of replacement parts, including current prices, listing of spare parts initially provided, and a second source of supply where applicable, cross-referenced as to component designation.

14.3.7.9 Each manufacturer's product data sheet annotated to clearly identify product or part.

14.3.7.10 Each manufacturer's printed operating and maintenance instructions.

14.3.7.11 List of recommended cleaning agents, maintenance procedures and schedules.

14.3.7.12 List of recommended test equipment including manufacturer’s name, address, and model number.

14.3.8 Three (3) copies of each manual shall be furnished with each PSS. These manuals are in addition to the manuals provided during training courses. All manuals of each type shall be identical and shall be originals, not reproduced copies.

14.3.9 Options identified in a manual, which are not furnished with the PSS System shall be marked "NOT USED."

14.3.10 The manuals shall consist of sturdy, hard cover, 3-ring, loose-leaf binders made for 8 ½" by 11" sheets. They shall be provided with a table of contents clearly itemizing the catalog and with loose-leaf hole reinforcements, except for those sheets where the full length of the fastener-edge is, in an approved manner, either reinforced or made of


of 70 04/14/2017 Rev. 07/07/2017

a high-strength material.

Loose-leaf holes shall not be punched through the body of drawings or other sheets. They shall be punched in the margin only, and each drawing and other large sheet shall have the margin trimmed and the sheet properly folded so that it may be unfolded and viewed without the need to remove it from the binder. Labels, protected by plastic covering, shall be securely affixed to both the face and spine of each binder. The labels shall contain the title of the manual, the manual number, the Contract title, and the Contract number.

14.4 For all custom application software necessary to operate the PSS, the Contractor shall provide NYSDOT with the software source code, and compiler necessary to compile it. The Contractor shall also demonstrate the compiling, linking, and loading of the source code as part of this test.

14.5 Electronic copies of all manuals shall be provided on CD in PDF format. Three

copies of the CD’s shall be provided.

14.6 NYSDOT shall have the right to make copies of all manuals both hard copy and electronic.

15 Testing

Design Approval Tests

15.1 The following tests shall be performed as part of the design approval test in addition to those specified in the Special Notes. The Design Approval Test shall be performed on a complete PSS assembly. While performing these tests a test set shall be used to issue commands to the sign controller to verify that the sign remains operational throughout the test:

15.1.1 Power variation: Test the sign with the line voltage at the maximum,

minimum and nominal specified values. Using a power interruption meter, at each of these voltages interrupt the power for 0.1 seconds five times. Repeat for a 0.5 second interruption and for a 1 second interruption.

15.1.2 Transient immunity: Using a transient generator set to the following conditions:

15.1.3 Amplitude: 300 volts ±5 percent, positive and negative polarity

15.1.4 Peak power: 5000 watts

15.1.5 Repetition: One pulse every other cycle moving uniformly over the full wave in order to sweep once every 3 seconds across 360 degrees of line cycle.

15.1.6 Pulse rise time: 500 ns.

15.1.7 Power line surge: Discharge a 25 uF capacitor charged to plus and minus 2000 volts applied directly across the incoming AC line at a rate of once every 10 seconds. Perform the test 10 times for each polarity. The unit shall be operated at 120 ± 12 VAC.


of 70 04/14/2017 Rev. 07/07/2017

15.1.8 Temperature: All functional operations of the equipment shall be successfully performed under the following conditions and in the order specified below:

15.1.8.1.1 The equipment shall be stabilized at -30 degrees Fahrenheit. After stabilization at this temperature, the equipment shall be operated without degradation for two (2) hours.

15.1.8.1.2 The equipment shall be stabilized at 140 degrees Fahrenheit. After stabilization, the equipment shall be operated without degradation for two (2) hours.

15.1.8.1.3 The equipment shall be subjected to temperature shock of 30 degrees Fahrenheit per hour, during which time the relative humidity shall not exceed 95%. The equipment shall be operated without failure during and after the temperature shock.

15.1.9 Relative Humidity: All equipment shall meet its performance requirements when subjected to temperature and relative humidity of 110 degrees Fahrenheit and 95%, respectively. The equipment shall be maintained at this condition for 48 hours. At the conclusion of the soak, within 30 minutes, the equipment shall meet all of its operational requirements.

15.1.10 Vibration: The equipment shall show no degradation of mechanical structure, soldered components, plug-in components or satisfactory operation in accordance with the manufacturer's specification after being subjected to the following vibration test:

15.1.10.1 The equipment shall be secured to the head of suitable electro- mechanical shaker in the vertical, lateral, and longitudinal planes, respectively. The object of the test is to vibrate the equipment in each of the three (3) mutually perpendicular axes, in accordance with the following parameters:

Amplitude: 1/16 in. "Double Amplitude" (peak to

peak) Linear Acceleration (g's): 5 maximum

Linear Velocity: approximately 7 ½ in/s

Frequency: 40 Hz

Duration: five (5) minute dwell in each axis

15.1.11 If the equipment fails the design approval test, the design fault shall be corrected and the entire design approval test shall be repeated. All deliverable equipment shall be modified, without additional cost to the New York State Department of Transportation, to include design changes required to pass the design approval tests.

Factory Demonstration Tests

15.2 Following Design Acceptance Testing and prior to shipping of any signs, the Contractor


of 70 04/14/2017 Rev. 07/07/2017

shall perform a factory demonstration test on a single sign. Factory Demonstration Tests shall test the full functionality of a sign, controller, central control and maintenance software and communications between them.

15.2.1 Using a notebook computer loaded with test software provided by the sign manufacturer demonstrate the following with the computer connected to the input (remote) port of the controller:

15.2.2 Exercising of all sign functions as defined in this document.

15.2.3 Simulation of error and fault conditions to demonstrate the detection and reporting of the status conditions defined in this document. Including, but not limited to, open cabinet door, bad pixels, bad drivers, illegal message, and illegal character.

15.2.4 With the notebook computer loaded with the test software provided by the sign manufacturer demonstrate operation through the local port of the sign controller.

15.2.5 Demonstrate compliance with the NTCIP specific standards to be implemented, applicable conformance groups, applicable data objects and their associated range values that are pertinent to the implementation of this specification.

15.2.6 Water Test: A water spray test shall be performed to demonstrate that the enclosure meets the NEMA 3R rating. At the completion of the test, verify that the inside of the housing is dry.

15.2.7 For all custom application software necessary to operate the LED Parking Space Sign Assembly, the Contractor shall provide NYSDOT with the software source code, and compiler necessary to compile it. The Contractor shall also demonstrate the compiling, linking, and loading of the source code as part of this test.

15.2.8 If the LED Parking Space Sign Assembly fails the factory demonstration test, the fault(s) shall be corrected and the entire factory demonstration test shall be repeated. All deliverable equipment shall be modified, without additional cost to the NYSDOT, to include any changes required to satisfactorily complete the factory demonstration tests.

Stand Alone Tests

The following stand-alone tests shall be performed after the sign is installed:

15.3 Insulation, continuity and ground tests shall be performed in accordance with §680-3.32, Tests.

15.4 After installation and prior to integration of the PSS into the system, the Contractor shall perform an operational stand-alone test in the field for each unit. The test, as a minimum, shall demonstrate operation of the LED Parking Space Sign Assembly using the test software running on a notebook computer provided by the Contractor.

15.5 Using a notebook computer loaded with test software provided by the sign manufacturer demonstrate the following with the notebook computer connected to the input (remote)


of 70 04/14/2017 Rev. 07/07/2017

port of the controller:

15.5.1 Exercising of all sign functions as defined by the Contract.

15.5.2 Simulation of error and fault conditions to demonstrate the detection and reporting of the status conditions defined in this document. Including, but not limited to, open cabinet door, bad pixels, bad drivers, illegal message, and illegal character.

15.5.3 With the notebook computer loaded with the test software provided by the sign manufacturer demonstrate operation through the local port of the sign controller.

15.5.4 Operate the sign for thirty-days in a test mode that shall continuously exercise the display. At the end of the thirty-day period, operation of the sign using the test software shall again be demonstrated. If a failure occurs, the sign shall be repaired and the thirty-day test repeated. A test pattern, approved by the Engineer, shall be displayed during the test.

Remote Site Verification Test

15.6 The Contractor shall verify the operations of the sign by operating it from the control center via the communications network.

System Acceptance Tests

15.7 Following the satisfactory completion of the Site Verification Tests, a system acceptance test shall be performed. Testing shall meet the requirements of the Contract Documents.

15 Training

15.1 The Contractor shall provide training courses to NYSDOT personnel as specified in the Special Notes section of this package.

16 Spare Parts

16.1 The following spare parts identified in the table below shall be provided by the Contractor and handed over to the Engineer after completion of system acceptance, for use by maintenance personnel.

16.2 The spare parts shall not be used by the Contractor during the construction period, and shall be delivered to the Engineer in a new and working condition.

16.3 All spare parts shall be certified by the manufacturer that they are suitable for use on the signs provided under this contract, and are in a working condition. Manufacturer’s certification shall include tests conducted, date of such tests, and the pass/fail criteria for these tests.

16.4 The Engineer reserves the right to witness any such testing of spare parts.

Item Description Quantity of SparesPSS Controller (including all associated cards and

2

Display Modules 2 or 5% of each type, whichever is greater

Driver Boards 2 or 5% of each type, whichever is greater


of 70 04/14/2017 Rev. 07/07/2017

Diagnostic Boards 2 or 5% of each type, whichever is greater

Power Supplies 2 of each type

Photo-Electric Sensors 2 of each type

LEDs 50 or 5% of those contained in one sign, whichever is greater

METHOD OF MEASUREMENT:

This work will be measured as the number of LED Parking Space Sign Assemblies of the type specified furnished, completely installed, successfully tested, and operational. Any necessary conduit and cabling required for the power feed and communications to the LED Parking Space Sign Assembly will be paid for separately under the applicable items. The static sign panel shall be paid for under § 645. 03010011, Ground-Mounted Sign Panels.

BASIS OF PAYMENT:

The unit price for each LED Parking Space Sign Assembly of the type specified shall include the cost of furnishing all labor, materials and equipment necessary to complete the work. All miscellaneous hardware and software, required for the installation and testing of the unit shall be included under this item. Payment for the communication equipment will be made under their respective items. Payment for all documentation, testing, test equipment, spare parts and software shall be included under this item.

Progress payment will be made as follows:

Ten percent (10%) of the bid price for the sign will be paid upon approval of the shop drawings.

Thirty percent (30%) of the bid price for each item will be paid upon satisfactory completion of installation of the assembly at the job site.

Forty percent (40%) of the bid price for each item will be paid upon satisfactory completion of the operational stand-alone test.

Ten percent (10%) of the bid price for each item will be paid upon satisfactory completion of the remote site verification test.

Ten percent (10%) of the bid price will be paid upon system acceptance.

NTCIP Test Procedures for VMS LED Parking Space Sign Assemblies July, 2007

Revision List

Document:Date Author Checked By Notes


of 70 04/14/2017 Rev. 07/07/2017

Table of Contents

1 Introduction – Purpose of Document ................................................. 30

1.1 Reference Documentation ........................................................................................ 30 1.2 Field Device Test Environment ............................................................................... 30

2 Test Cases ............................................................................................. 33

2.1 TC001 – Sign Interrogation ..................................................................................... 33 2.2 TC002 – Download and Display a Changeable Message ........................................ 35 2.3 TC003 – Font Configuration .................................................................................... 37 2.4 TC004 – Display all Permanent Messages .............................................................. 38 2.5 TC005 – Download and Display all Changeable Messages .................................... 40 2.6 TC006 – MULTI Tags ............................................................................................. 41 2.7 TC007 – Message Errors ......................................................................................... 43 2.8 TC008 – Activate Message ...................................................................................... 45 2.9 TC009 – Default MULTI Message Attributes ......................................................... 46 2.10 TC010 – Default Messages .................................................................................. 47 2.11 TC011 – Time .................................................................................................... 50 2.12 TC012 – Scheduling ............................................................................................ 52 2.13 TC013 – Security ............................................................................................... 56 2.14 TC014 – Pixel Failures ........................................................................................ 58 2.15 TC015 – Power Supply Error Status .................................................................. 61 2.16 TC016 – Temperature and Status ....................................................................... 62 2.17 TC017 – Field Display ....................................................................................... 63 2.18 TC018 – Reports .................................................................................................. 63 2.19 TC019 – Brightness Control ............................................................................... 67

List of Figures

Figure 1-1 Test Environment for Variable Message Sign .......................................................................................................................................................3

1 Introduction – Purpose of Document

The National Transportation Communications for ITS Protocols (NTCIP) standards are intended to promote the development of interoperable equipment within the Intelligent Transportation Systems (ITS) industry. Any component that does not fully follow the rules defined by the NTCIP standards will inhibit or preclude interoperability from being realized. As a result, the industry needs a well-defined and consistent way to test equipment that claims conformance to the NTCIP standards. This document is intended to be used as an appendix to Special Specifications for LED based character matrix Parking Space Signs without regard to any one Special Specification.

ITEM 683.01041008: LED PARKING SPACE SIGN ASSEMBLY - TYPE 1ITEM 683.01042008: LED PARKING SPACE SIGN ASSEMBLY - TYPE 2APPENDIX AA: NTCIP TEST PROCEDURE FOR VMS

of 70 04/14/2017 Rev. 07/07/2017

1.1 Reference Documentation

Some of the documents reviewed during the development of this test procedure are listed below:

ITEM 683.XX04M - LED Parking Space Sign Assemblies

NTCIP 1203:1997 – Object Definitions for Dynamic Message Signs (DMS)

NTCIP 8007v01-20a – Testing and Conformity Assessment Documentation within NTCIP Standards Publications v01

NTCIP 9012v01.24c – Testing and Conformity Assessment User Guide for NTCIP Field Devices and Center-to-Field Communications

1.2 Field Device Test Environment

Testing shall be performed either at the manufacturer’s facility or at a mutually agreed to location, such as a Contractor’s field office, or vendor’s facility. The following shall be made available for the purposes of testing:

Mains power for the device under test (DUT), notebook computer, and any other devices requiring electrical power during the performance of the test.

Two Variable Message Signs representative of each sign being procured for the contract.

Notebook computer pre-loaded with latest version of NTCIP testing software. The notebook computer shall also be equipped with a Ethernet port for TCP/IP communications to the sign.

Communications interface(s) to simulate the communications link from the central location to the field device. The simulated communications interface shall match the functional requirements of the actual interface.

All necessary cables and converters.

Test report from a “Dry Run” of the testing for the Variable Message Signs, with a written explanation of any failures, and the action taken to correct the errors.

Figure 1-1 is the test set up for a Variable Message Sign. In each test, the set up shall be identical, and the same test shall be run on each sign. Figure 1-1 shows a test environment where communication is over optical fiber using modems. The test environment shall simulate the actual communication environment.

In the test cases described in Section 2 of this document one, or all, of the tests shall be set to run and repeat over a fixed period of time to verify the reliability of the DUT.


of 70 04/14/2017 Rev. 07/07/2017

Figure 1-1 Test Case for Variable Message Sign

NYSDOTNOTEBOOK COMPUTERRUNNING NTCIPTEST SOFTWARE

EIA-232 DATA

EIA-232 DATA

FIBERPATCH CABLE


of 70 04/14/2017 Rev. 07/07/2017

2 Test Cases

2.1 TC001 – Sign Interrogation

Test Case:

TC001

Title: Sign Interrogation Description: The purpose of this test is to verify that the sign reports the

applicable parameters required for the Central System to know the sign size, configuration, manufacturer and version.

Pass/Fail Criteria:

The DUT shall pass every step described in this test case in order topass this test.

Step Test Procedure Results

1. Get globalMaxModules.0 Pass / Fail

2. Verify that the Response Value for globalMaxModules.0 (X) is greater than 0.

Pass / Fail

3. For each value of N, from 1 though X (obtained is Step 2), perform steps 4 through 15

4. Get moduleNumber.N Pass / Fail

5. Verify that the Response Value for moduleNumber.N equals N. Pass / Fail

6. Get moduleDeviceNode.N Pass / Fail

7. Verify that the Response Value for moduleDeviceNode.N equals 1.3.6.1.4.1.1206.4.2.3. (dms)

Pass / Fail

8. Get moduleMake.N Pass / Fail

9. Verify that the Response Value for moduleMake.N indicates the manufacturer of the module.

Pass / Fail

10. Get moduleModel.N Pass / Fail

11. Verify that the Response Value for moduleModel.N indicates the correct model number for the component

Pass / Fail

12. Get moduleVersion.N Pass / Fail

13. Verify that the Response Value for moduleVersion.N indicates the correct version number of the component.

Pass / Fail

14. Get moduleType.N Pass / Fail


of 70 04/14/2017 Rev. 07/07/2017

15. Verify that the Response Value for moduleType.N indicates the correct type: Note: 1 (other) 2 (hardware) 3 (software)

Pass / Fail

16 Verify that at least one Response Value for moduleType.N is 3 – software.

Pass / Fail

17. Get dmsSignType.0 Pass / Fail

18. Verify that the Response Value for dmsSignType.0 indicates the correct sign type: 4 (vms character matrix)

Pass / Fail

19. Get dmsBeaconType.0 Pass / Fail

20. Verify that the Response Value for dmsBeaconType.0 indicates the correct Beacon Type: 3 (One)

Pass / Fail

21. Get dmsSignAccess.0 Pass / Fail

22. Verify that the Response Value for dmsSignAccess.0 indicates the correct Sign Access: 8 (front access)

Pass / Fail

23. Get dmsSignHeight.0 Pass / Fail

24. Verify that the Response Value for dmsSignHeight.0 indicates the correct Sign Height in millimeters.

Pass / Fail

25. Get dmsSignWidth.0 Pass / Fail

26. Verify that the Response Value indicates the correct Sign Width in millimeters.

Pass / Fail

27. Get dmsHorizontalBorder.0 Pass / Fail

28. Verify that the Response Value for dmsHorizontalBorder.0 indicates the actual Horizontal Border in millimeters.

Pass / Fail

29. Get dmsVerticalBorder.0 Pass / Fail

30. Verify that the Response Value for dmsVerticalBorder.0 indicates the actual Vertical Border in millimeters.

Pass / Fail

31. Get dmsLegend.0 Pass / Fail

32. Verify that the Response Value for dmsLegend.0 indicates the correct Legend: 2 (noLegend)

Pass / Fail

33. Get dmsSignTechnology.0 Pass / Fail


of 70 04/14/2017 Rev. 07/07/2017

34. Verify that the Response Value for dmsSignTechnology.0 equals 2(LED).

Pass / Fail

35. Get vmsCharacterHeightPixels.0 Pass / Fail

36. Verify that the Response Value for vmsCharacterHeightPixels.0 indicates the correct Character Height: 7

Pass / Fail

37. Get vmsCharacterWidthPixels.0 Pass / Fail

38. Verify that the Response Value for vmsCharacterWidthPixels.0 indicates the correct Character Width measured in pixels: 5

Pass / Fail

39. Get vmsSignHeightPixels.0 Pass / Fail

40. Verify that the Response Value for vmsSignHeightPixels.0 indicates the correct Sign Height measured in pixels: 27

Pass / Fail

41. Get vmsSignWidthPixels.0 Pass / Fail

42. Verify that the Response Value for vmsSignWidthPixels.0 indicates the correct Sign Width measured in pixels: 21

Pass / Fail

43. Get vmsHorizontalPitch.0 Pass / Fail

44. Verify that the Response Value for vmsHorizontalPitch.0 indicates the correct Horizontal Pitch in millimeters.

Pass / Fail

45. Get vmsVerticalPitch.0 Pass / Fail

46. Verify that the Response Value for vmsVerticalPitch.0 indicates the correct Vertical Pitch in millimeters.

Pass / Fail

Test Case Result:

Pass / Fail

Test Case Notes:

2.2 TC002 – Download and Display a Changeable Message

Test Case:

TC002

Title: Download and Display a Changeable Message

Description: The purpose of this test is to verify that the sign will download and display a changeable message.

Pass/Fail Criteria:



of 70 04/14/2017 Rev. 07/07/2017


1. Download Changeable Message 1. Pass / Fail

2. Set dmsMessageStatus.3.1 to 6 (modifyReq) Pass / Fail

3. Set dmsMessageMultiString.3.1 to 123[nl]456 Pass / Fail

4. Set dmsMessageOwner.3.1 to Customer Pass / Fail

5. Set dmsMessageBeacon.3.1 to 1 Pass / Fail

6. Set dmsMessagePixelService.3.1 to 0 Pass / Fail

7. Set dmsMessageRunTimePriority.3.1 to 255 Pass / Fail

8. Set dmsMessageStatus.3.1 to 7 (validateReq) Pass / Fail

9. Verify that no errors are reported. Pass / Fail

10. Check Changeable Message 1 validation status.

11. Get dmsMessageStatus.3.1 Pass / Fail

12. Verify that the Response Value for dmsMessageStatus.3.1 is 4 (valid).

Pass / Fail

13. Get dmsValidateMessageError.0 Pass / Fail

14. Verify that the Response Value for dmsValidateMessageError.0 is 2 (none)

Pass / Fail

15. Get dmsMultiSyntaxError.0 Pass / Fail

16. Verify that the Response Value for dmsMultiSyntaxError.0 is 2 (none)

Pass / Fail

17. Activate Changeable Message 1

18. Get dmsMessageCRC.3.1 Pass / Fail

19. Verify that the Response Value for dmsMessageCRC.3.1 is a positive integer.

Pass / Fail

20. Construct a 12 byte MessageActivationCode using the following parameters:

i. Duration ii. Priority iii. Memory Type iv. Message Number v. CRC vi. IP Address

Pass / Fail


of 70 04/14/2017 Rev. 07/07/2017

21. Set dmsActivateMessage.0 with the MessageActivationCode Pass / Fail

22. Verify that the message is displayed on the sign. Pass / Fail

23. Get dmsMessageMultiString.5.1 (the current message) Pass / Fail

24. Verify that the message is reported. Pass / Fail

25. Get dmsActivateMsgError.0 Pass / Fail

26. Verify that the Response Value for dmsActivateMsgError.0 is 2 (none).

Pass / Fail

Test Case Result:

Test Case Notes:

2.3 TC003 – Font Configuration

Test Case:

TC002



Pass/Fail Criteria:





3. Set dmsMessageMultiString.3.1 to 789[nl]A0+ Pass / Fail







of 70 04/14/2017 Rev. 07/07/2017





Pass / Fail



Pass / Fail



Pass / Fail




Pass / Fail

20. Construct a 12 byte MessageActivationCode using the following parameters: i. Duration ii. Priority iii. Memory Type iv. Message Number v. CRC vi. IP Address

Pass / Fail







Pass / Fail

Test Case Result:


of 70 04/14/2017 Rev. 07/07/2017

Test Case Notes:

2.4 TC004 – Display all Permanent Messages

Test Case:

TC002



Pass/Fail Criteria:





3. Set dmsMessageMultiString.3.1 for a two line sign to BCD[nl]EF or for a three line sign to BCD[nl]EF[nl]abc

Pass / Fail










Pass / Fail



Pass / Fail



Pass / Fail


of 70 04/14/2017 Rev. 07/07/2017




Pass / Fail

20. Construct a 12 byte MessageActivationCode using the following parameters: i. Duration ii. Priority iii. Memory Type iv. Message Number v. CRC vi. IP Address

Pass / Fail







Pass / Fail

Test Case Result:

Test Case Notes:

2.5 TC005 – Download and Display all Changeable Messages

Test Case:

TC002



Pass/Fail Criteria:

The DUT shall pass every step described in this test case in order to passthis test.



of 70 04/14/2017 Rev. 07/07/2017



3. Set dmsMessageMultiString.3.1 for a two line sign to GHI[nl]JKL or for a three line sign to GHI[nl]JKL[nl]JKL

Pass / Fail









12. Verify that the Response Value for dmsMessageStatus.3.1 is 4 (valid). Pass / Fail



Pass / Fail


16. Verify that the Response Value for dmsMultiSyntaxError.0 is 2 (none) Pass / Fail




Pass / Fail

20. Construct a 12 byte MessageActivationCode using the following parameters:

i. Duration ii. Priority iii. Memory Type iv. Message Number v. CRC vi. IP Address

Pass / Fail


of 70 04/14/2017 Rev. 07/07/2017







Pass / Fail

Test Case Result:

Test Case Notes:

2.6 TC006 – MULTI Tags

Test Case:

TC006

Title: MULTI Tags

Description: The purpose of this test is to verify that the sign will correctly display various messages that contain MULTI tags that are required to be supported.

Pass/Fail Criteria:



1. Set the default message parameters for normal message display as follows:

2. Set defaultBackgroundColor.0 to 0 (black). Pass / Fail

3. Set defaultForegroundColor.0 to 9. Pass / Fail

4. Set defaultFlashOn.0 to 4. Pass / Fail

5. Set defaultFlashOff.0 to 4. Pass / Fail

6. Set defaultFont.0 to 1. Pass / Fail

7. Set defaultJustificationLine.0 to 4 (right). Pass / Fail

8. Set defaultJustificationPage.0 to 3 (middle). Pass / Fail


of 70 04/14/2017 Rev. 07/07/2017

9. Set defaultPageOnTime.0 to 20. Pass / Fail

10. Set defaultPageOffTime.0 to 0. Pass / Fail

11. Set defaultCharacterSet.0 to 2 (eightBit). Pass / Fail

12. Use the procedure from Test Case TC002 to download and display each of the following messages to Changeable Message 1, and verify that the message is correctly displayed:

13. a. For a two line sign to message: PAG[nl]ONE[np]PAG[nl]TWO

or for a three line sign to message: TST[nl]PAG[nl]ONE[np]TST[nl]PAG[nl]TWO

i. Description: Two pages, 2 second duration per page, no flashing, center justified.

Pass / Fail

14. Verify that the message is correctly displayed. Pass / Fail

15. b. For a two line sign to message: PAG[nl]ONE[np]PAG[nl]TWO[np]PAG[nl]]THR

or for a three line sign to message: TST[nl]PAG[nl]ONE[np]TST[nl]PAG[nl]TWO[np]TST[nl]P AG[nl]]THR

i. Description: Three pages, 2 second duration per page, no flashing, center justified.

Pass / Fail


17. c. For a two line sign to message: [pt20o10]PG[nl]1[np]PG[nl]2[np]PA

G[nl]3 or for a three line sign to message: [pt20o10]TST[nl]PG[nl]1[np]TST[nl]PG[nl]2[np]PAG[nl ]3

i. Description: Three pages, 2 second on time, one second off time per page, no flashing, center justified.

Pass / Fail



of 70 04/14/2017 Rev. 07/07/2017

19. d. For a two line sign to message:[jl2][pt20o10]PG[nl]1[np]PG[nl]2[np]P

G[nl]3 or for a three line sign to message: [jl2][pt20o10]TST[nl]PG[nl]1[np]TST[nl]PG[nl]2[np]PG [nl]3

Pass / Fail


21. e. For a two line sign to message:[jl3][pt20o10]PG[nl]1[np]PG[nl]2[np]P

G[nl]3 or for a three line sign to message: [jl3][pt20o10]TST[nl]PG[nl]1[np]TST[nl]PG[nl]2[np]TST[nl]PG [nl]3

i. Description: Three pages, 2 second on time, one second off time per page, no flashing, center justified.

Pass / Fail

Test Case Result:

Pass / Fail

Test Case Notes:

2.7 TC007 – Message Errors

Test Case:

TC007

Title: Message Errors

Description: The purpose of this test is to verify that incorrect messages will not be validated or displayed on the sign

Pass/Fail Criteria:



1. Use the procedure from Test Case TC002 to download and display each of the following messages to Changeable Message 1, and verify that the message is NOT displayed, and the correct error value is reported by dmsMessageStatus.3.1, dmsValidateMessageError.0, dmsMultiSyntaxError.0, and dmsMultiSyntaxErrorPosition.0


of 70 04/14/2017 Rev. 07/07/2017

2. Message: TST[nl]BIG MESSAGE TOO LONG TO FIT Third line too big to fit on the sign.

Pass / Fail

3. Verify that the message is NOT displayed. Pass / Fail

4. Verify that the correct error value is reported by the following objects:

dmsMessageStatus.3.1 5 (error)

dmsValidateMessageError.0 5 (syntaxMULTI)

dmsMultiSyntaxError.0 5 (textTooBig)

dmsMultiSyntaxErrorPosition.0 6 (approximately)

Pass / Fail

5. For two line message sign, message: TST[nl]1[nl]2 Three line message too big to fit on the sign.

For three line sign message: TST[nl]1[nl]3[nl]4 Four line message too big to fit on the sign.

Pass / Fail


7. Verify that the correct error value is reported by the following objects:



dmsMultiSyntaxError.0 5 (textTooBig)

dmsMultiSyntaxErrorPosition.0 6 (approximately) for two line sign 9 (approximately) for three line sign

Pass / Fail

8. Message: TST[nl1 Unsupported tag (missing closing “]”).

Pass / Fail



of 70 04/14/2017 Rev. 07/07/2017

10. Verify that the correct error value is reported by by the following objects:



dmsMultiSyntaxError.0 3 (unsupportedTag) or 4 (unsupportedTagValue)

dmsMultiSyntaxErrorPosition.0 7(approximately)

Pass / Fail

Test Case Result:

Pass / Fail

Test Case Notes:

2.8 TC008 – Activate Message

Test Case:

TC008

Title: Activate Message

Description: The purpose of this test is to verify that the messages are activated using the message priority and CRC attributes correctly

Pass/Fail Criteria:



1. Use the procedure from Test Case TC002 to download and display the following message to Changeable Message 1.

a. Message: HP [nl]MSG b. Runtime Priority: 100 c. Activate Priority: 255 d. Pixel Service 0

Pass / Fail



of 70 04/14/2017 Rev. 07/07/2017

3. Use the procedure from Test Case TC002 to download and display the following message to Changeable Message 1,

a. Message: LP[nl]MSG b. Runtime Priority: 100 c. Activate Priority: 99 d. Pixel Service 0

Pass / Fail

4. Verify that the message is correctly downloaded, but NOT displayed. Pass / Fail

5. Verify that the Response Value for dmsActivateMsgError.0 is 3 (priority).

Pass / Fail

6. Set dmsActivateMessage.0 to

hex value 00 0F 64 03 00 01 24

Pass / Fail

7. Verify that the low priority message (LP MSG)is now displayed. Pass / Fail

8. Get dmsMessageCRC.3.1. Pass / Fail

9. Verify that the Response Value for dmsMessageCRC.3.1 is 24 4F hex (integer 9295), and the Response Value for dmsActivateMsgError.0 is 2 (noError).

Pass / Fail

10. Activate Permanent Message 1. Pass / Fail

11. Verify that it is correctly displayed on the sign. Pass / Fail

12. Set dmsActivateMessage.0 to hex value 00 0F 64 03 00 01 24 4E 01 02 03 04

Pass / Fail

13. Verify that the Set returns a genErr, and dmsActivateMsgError.0 reports a value of 7 (messageCRC)

Pass / Fail

14. Verify that the Low Priority Message is NOT displayed. Pass / Fail

Test Case Result:

Pass / Fail

Test Case Notes:


of 70 04/14/2017 Rev. 07/07/2017

2.9 TC009 – Default MULTI Message Attributes

Test Case: Title:

TC009

Default MULTI Message Attributes

Description: The purpose of this test is to verify that the sign will respondcorrectly to the default page time and justification parameters.

Pass/Fail The DUT shall pass every step described in this test case in order to Criteria: pass this test.


1. Get defaultJustificationLine.0 Pass / Fail

2. Record the Response Value for defaultJustificationLine.0

3. Get defaultFlashOn.0 Pass / Fail

4. Record the Response Value for defaultFlashOn.0

5. Get defaultFlashOff.0 Pass / Fail

6. Record the Response Value for defaultFlashOff.0

7. Set defaultJustificationLine.0 to 3 (center ). Pass / Fail



10. Use ththe fol

a. b. c. d. e.

e procedure from Test Case TC002lowing to Changeable Message 1.

Message: TST[np]1 Runtime Priority: 100 Activate Priority: 255 Beacons 1 Pixel Service

to download and display Pass / Fail

11. Verify that the message is displayed centered on line 2. Pass / Fail

12. Set defaultJustificationLine.0 to 2 (left). Pass / Fail




of 70 04/14/2017 Rev. 07/07/2017

15. Get dmsActivateMessage.0. Set the value received back to Pass / Fail dmsActivateMessage.0 to re-activate the message.

16. Verify that the message is displayed on the top line of the sign, left justified.

Pass / Fail

17. Set defaultJustificationLine.0 to 4 (right). Pass / Fail

18. Set defaultJustificationPage.0 to 4 (bottom). Pass / Fail



21. Get dmsActivateMessage.0. Pass / Fail

22. Set the Response Value received back to dmsActivateMessage.0 to re-activate the message.

Pass / Fail

23. Verify that the message is displayed on second line of the sign, right justified.

Pass / Fail

Test Case Result:

Pass / Fail

Test Case Notes:

2.10 TC010 – Default Messages

Test Case:

TC0010

Title: Default Messages

Description: The purpose of this test is to verify that the sign will correctly perform the following operations: 1. Display a message for a given duration, and then, after that duration has expired, display the configured End Duration message. 2. Display the configured Short Power Loss message after a brief power

failure. 3. Display the configured Long Power Loss message after a long power

failure. 4. Display the Comm Loss Message after the Central System has been silent for longer than the Comm Loss Timer.


of 70 04/14/2017 Rev. 07/07/2017

Pass/Fail Criteria:



1. Using the download procedure from Test 2, configure changeable messages as follows:

Changeable Message 2: END[nl]DUR Changeable Message 3: SHT[nl]PWL Changeable Message 4: LNG[nl]PWL Changeable Message 5: COM[nl]LOS Beacon 1 (Changeable Message 2 - 5) Pixel Service 0 (Changeable Message 2 - 5)

Pass / Fail

2. Set dmsEndDurationMessage.0 to the hex value 03 00 02 60 AD Pass / Fail

3. Using Test Case TC002, download and display the message “TST[nl]MSG” using a duration of 3 (minutes).

Pass / Fail


5. Get dmsMessaGetimeRemaining.0 Pass / Fail

Verify that the Response Value for dmsMessaGetimeRemaining.0 is 3.

Pass / Fail

6. Verify that the value decrements as each minute elapses. Pass / Fail

7. After 3 minutes (and not more that 4 minutes) verify that the message “END DUR” is displayed.

Pass / Fail

8. Get dmsMsgSourceMode.0. Pass / Fail

9. Verify that the Response Value for dmsMsgSourceMode.0 is14 (endDuration).

Pass / Fail

10. Set dmsShortPowerLossTime.0 to 30 (seconds). Pass / Fail

11. Set dmsShortPowerRecoveryMessage.0 to 03 00 03 AF 37 Pass / Fail

12. Set dmsLongPowerRecoveryMessage.0 to 03 00 04 F6 DE Pass / Fail

13. Using Test Case TC002 download and display the message Pass / Fail

“TST[nl]MSG” using a duration of 10 (minutes).


of 70 04/14/2017 Rev. 07/07/2017


15. Remove power to the sign for 5 to 10 seconds, and then reapply power.

16. Verify that after power up the message “SHT PWL” is displayed. Pass / Fail

17. Using Test Case TC002 download and display the message “TST[nl]MSG” using a duration of 10 (minutes).

Pass / Fail


19. Remove power from the sign for 1 to 2 minutes, and then reapply power.

Pass / Fail

20. Verify that after power up the message “LNG PWL” is displayed. Pass / Fail

21. Set dmsCommunicationsLossMessage.0 to 03 00 05 12 50 Pass / Fail

22. Set the dmsTimeCommLoss.0 to 2 (minutes). Pass / Fail

23. Using Test Case TC002, download and display the message “TST[nl]MSG” using a duration of 10 (minutes).

Pass / Fail


25. Do not communicate with the sign for 3 minutes. Pass / Fail

26. Verify that after 2 minutes and before 3 minutes the message “COM LOS” is displayed.

Pass / Fail

27. Return objects to a benign state as follows:

28. Set dmsTimeCommLoss.0 to 0 Pass / Fail

29. Set dmsShortPowerLossTime.0 to 0 Pass / Fail

30. Set dmsMemoryMgmt.0 to 3 (to clear the changeable messages). Pass / Fail

Test Case Result:

Pass / Fail

Test Case Notes:


of 70 04/14/2017 Rev. 07/07/2017

Test Case:

TC011

Title: Time

Description: The purpose of this test is to verify that the sign will keep the time, and has support for daylight saving time, regular year change and leap year change.

Pass/Fail The DUT shall pass every step described in this test case in order toCriteria: pass this test.


1. Get globalTime.0, and record the Response Value for globalTime.0. Pass / Fail

2. Wait for twenty seconds.

3. Get globalTime.0. Pass / Fail

4. Verithan

y that the Response Value for globalTime.0 is twenty more the value recorded in step 1.

Pass / Fail

5. Get controllerBeginDSTMonth.0 Pass / Fail

6. Set controllerBeginDSTMonth.0 to 3 (March) Pass / Fail

7. Get controllerBeginDSTWeek.0 Pass / Fail

8. Set controllerBeginDSTWeek.0 to (2nd Week) Pass / Fail

9. Get controllerBeginDSTDay.0 Pass / Fail

10. Set controllerBeginDSTDay.0 to 1 (Sunday) Pass / Fail

11. Get controllerBeginDSTHour.0 Pass / Fail

12. Set controllerBeginDSTHour.0 to 2 Pass / Fail

13. Get controllerEndDSTMonth.0 Pass / Fail

14. Set controllerEndDSTMonth.0 to 11 (November) Pass / Fail

15. Get controllerEndDSTWeek.0 Pass / Fail

16. Set controllerEndDSTWeek.0 to 1 (1st Week) Pass / Fail

17. Get controllerEndDSTDay.0 Pass / Fail

18. Set controllerEndDSTDay.0 to 1 (1st Week) Pass / Fail

19. Get controllerEndDSTHour.0 Pass / Fail

20. Set controllerEndDSTHour.0 to 2 Pass / Fail

21. Get controllerDSTStatus.0 Pass / Fail


of 70 04/14/2017 Rev. 07/07/2017

22. Get controllerStandardTimeZone.0 Pass / Fail

23. Set controllerDSTStatus.0 to 2 (enable DST) Pass / Fail

24. Set controllerStandardTimeZone.0 to -14400 (for eastern time zone) Pass / Fail

25. Set globalTime.0 to 1205114340. (This will set the clock in the sign to a time in US daylight time 03/09/2008 1:59:00 AM).

(Daylight Savings Time Change)

Pass / Fail

26. Wait 75 seconds.

27. Get controllerLocalTime.0 Pass / Fail

28. Verify that the Response Value for controllerLocalTime is 1205103615 which corresponds to 03/09/2008 3:00:15 AM. (May be off by a second or two)

Pass / Fail

29. Set globalTime.0 to 1225504740. (This will set the clock in the sign to a time in US daylight time 11/01/2008 1:59:00 AM).

(Daylight Savings Time Change)

Pass / Fail

30. Wait 75 seconds. Pass / Fail

31. Get controllerLocalTime.0 Pass / Fail

32. Verify that the Response Value for controllerLocalTime is 1225486815 which corresponds to 11/01/2008 1:00:15 AM. (May be off by a second or two)

Pass / Fail

33. Set globalTime.0 to 1065453611 (12/31/2005

11:59:00 PM) (Regular year change test)

Pass / Fail


35. Get globalTime.0. Pass / Fail

36. Verify that the Response Value for globalTime.0 is 1136073615 which corresponds to 1/1/2006 12:00:15 AM. (May be off by a second or two)

Pass / Fail

37. Set globalTime.0 to 1204243139 (2/28/2008

11:59:00 PM) (Leap year change test)

Pass / Fail



of 70 04/14/2017 Rev. 07/07/2017

39. Verify that the Response Value for globalTime.0 is 1204243215 which corresponds to 2/29/2008 12:00:15 AM. (May be off by a second or two)

Pass / Fail

Test Case Result:

2.12 TC012 – Scheduling

Test Case: Title:

TC012

Scheduling

Description: The purpose of this test is to verify that the sign will displaymessages on a time based schedule, and this schedule will be correctly executed during winter (standard time) and summer (daylight saving time).



1. Get globalTime.0 Pass / Fail

2. Record the Response Value for globalTime.0

3. Get controllerBeginDSTMonth.0. Pass / Fail

4. Record the Response Value for controllerBeginDSTMonth.0

3. Get controllerBeginDSTWeek.0. Pass / Fail

4. Record the Response Value for controllerBeginDSTWeek.0

3. Get controllerBeginDSTDay.0. Pass / Fail

4. Record the Response Value for controllerBeginDSTDay.0

3. Get controllerBeginDSTHour.0. Pass / Fail

4. Record the Response Value for controllerBeginDSTHour.0

5. Get controllerStandardTimeZone.0 Pass / Fail

6. Record the Response Value for controllerStandardTimeZone.0

Test Case Notes:


of 70 04/14/2017 Rev. 07/07/2017

7. Get maxTimeBaseScheduleEntries.0 Pass / Fail

8. Record the Response Value for maxTimeBaseScheduleEntries.0

10. Get maxDayPlans.0 Pass / Fail

11. Record the Response Value for maxDayPlans.0 13. Get maxDayPlanEvents.0 Pass / Fail

14. Record the Response Value for maxDayPlanEvents.0

16. Get numActionTableEntries.0 Pass / Fail

17. Record the Response Value for numActionTableEntries.0

19. Set up Schedule 1 and Day Plan 1. Pass / Fail

20. Set timeBaseScheduleMonth.1 to 8190 (every month.) Pass / Fail

21. Set timeBaseScheduleDay.1 to 254 (every day). Pass / Fail

22. Set timeBaseScheduleDate.1 to 214748346 (every date). Pass / Fail

23. Set timeBaseScheduleDayPlan.1 to 1. Pass / Fail

24. Set dayPlanHour.1.1 to 17 (5 PM). Pass / Fail

25. Set dayPlanMinute.1.1 to 30 (5:30 PM). Pass / Fail

26. Set dayPlanActionNumberOID.1.1 to 1.3.6.1.4.1.1206.4.2.3.8.2.1.1.3 (dmsActionMsgIndex.3).

Pass / Fail

27. Set dayPlanHour.1.2 to 19 (7 PM). Pass / Fail

28. Set dayPlanMinute.1.2 to 45 (7:45 PM). Pass / Fail


Pass / Fail

30. Set dayPlanHour.1.3 to 6 (6 AM). Pass / Fail

31. Set dayPlanMinute.1.3 to 23 (6:23 AM). Pass / Fail


Pass / Fail

33. Using the download procedure from Test Case TC002, configure changeable messages as follows:

34. Changeable 1: CHG[nl]MG1 Pass / Fail

35. Changeable 3: TST[nl]MG1 Pass / Fail


of 70 04/14/2017 Rev. 07/07/2017

36. Changeable 4: TST[nl]MG2 Pass / Fail

37. Beacon 1 (Changeable Message 1,3,4). Pass / Fail

38. Pixel Service (Changeable Message 1,3,4). Pass / Fail

39. Runtime Priority 100 (Changeable Message 1,3,4). Pass / Fail

40. Set dmsActionMsgCode.1 to hex 03 00 03 21 C3 Pass / Fail

41. Set dmsActionMsgCode.2 to hex 03 00 01 20 90 Pass / Fail

42. Set dmsActionMsgCode.3 to hex 03 00 04 45 2C Pass / Fail

43. Blank the sign: Set dmsActivateMessage.0 to hex value FF FF FF 07 00 01 00 00 01 02 03 04

Pass / Fail

44. Activate the schedule: Set dmsActivateMessage.0 to hex value FF FF FF 06 00 01 00 00 01 02 03 04

Pass / Fail

45. Set controllerDSTStatus.0 to 2 (enable DST) Pass / Fail

46. Modify the time in the sign: Set globalTime.0 to 1031765310 (9/11/2002 5:28:30 PM) Set controllerStandardTimeZone.0 to 0

Pass / Fail

47. Wait for up to three minutes for the schedule to activate. Pass / Fail

48. Verify that “TST MG 2” is displayed. Pass / Fail


Pass / Fail


Pass / Fail

51. Modify the time in the sign: Set globalTime.0 to 1031773410 (9/11/2002 7:43:30 PM) Set controllerStandardTimeZone.0 to 0

Pass / Fail


53. Verify that “TST MG1” is displayed. Pass / Fail


Pass / Fail


of 70 04/14/2017 Rev. 07/07/2017


Pass / Fail

56. Modify the time in the sign:Set globalTime.0 to 1031725290 (9/11/2002 6:21:30 AM) Set controllerStandardTimeZone.0 to 0

Pass / Fail


58. Verify that “CHG MG 1” is displayed. Pass / Fail


Pass / Fail


Pass / Fail

61. Modify the time in the sign.Set globalTime.0 to 1031761710 (9/11/2002 4:28:30 PM) Set controllerStandardTimeZone.0 to 3600 (1 hour)

Pass / Fail

62. Wait for up to three minutes for the schedule to activate.

63. Verify that “TST MG2” is displayed. Pass / Fail


Pass / Fail


Pass / Fail

66. Modify the time in the sign:Set globalTime.0 to 1031769810 (9/11/2002 6:43:30 PM) Set controllerStandardTimeZone.0 to 3600 (1 hour)

Pass / Fail


68. Verify that “TST MG 1” is displayed. Pass / Fail


Pass / Fail


Pass / Fail


of 70 04/14/2017 Rev. 07/07/2017

71. Modify the time in the sign:Set globalTime.0 to 1031721690 (9/11/2002 5:21:30 AM) Set controllerStandardTimeZone.0 to 3600 (1 hour)

Pass / Fail


73. Verify that “CHG MG 1” is displayed. Pass / Fail

74. Set dmsMemoryMgmt.0 to 3 (clearChangeableMessages), to clear all the changeable messages on completion of the test.

Pass / Fail


Pass / Fail

Test Case Result:

Pass / Fail

Test Case Notes:

Test Case:

TC013

Title: Security

Description: The purpose of this test is to verify that the global security conformance group objects have been correctly implemented, to provide security over the communication link.

Pass/Fail Criteria:



1. Set the community name to the “administrator” community name. By default, this should be administrator unless a prior user has changed this to a different value.

Pass / Fail

2. Inspect the security objects as follows:

3. Get communityNamesMax.0. Pass / Fail

4. Verify the Response Value for communityNamesMax.0 equals or exceeds 4.

Pass / Fail

5. Get communityNameAdmin.0 Pass / Fail

6. Verify that the Response Value for communityNameAdmin.0 is administrator or the valid administrator community name.

Pass / Fail


of 70 04/14/2017 Rev. 07/07/2017

7. For N equals 1, Get the following table entries, and Verify that valid values are returned:

Pass / Fail

8. Get communityNameIndex.N Pass / Fail

9. Verify that the Response Value for communityNameIndex.N is N Pass / Fail

10. Get communityNameUser.N Pass / Fail

11. Verify that the correct Response Value for communityNameUser.N is returned.

Pass / Fail

12. Get communityNameAccessMask.N Pass / Fail

13. Verify that the Response Value for communityNameAccessMask.N is valid.

Pass / Fail

14. Set communityNameUser.1 to NewYork Pass / Fail

15. Set communityNameAccessMask.1 to 0. (Read only access). Pass / Fail

16. Change the community name in the test application to NewYork. Pass / Fail


18. Verify that the Response Value for globalTime.0 is valid.. Pass / Fail

19. Set globalTime.0 to 1000000000. Pass / Fail

20. Verify that the Set is rejected. Pass / Fail


22. Verify that the Response Value for globalTime.0 is valid, incremented by the time that elapsed between step 17 and step 21, and that the Set attempt from step 19 was ignored.

Pass / Fail

23. Change the community name in the test application to administrator, or the valid the administrator community name.

Pass / Fail

24. Set communityNameAccessMask.1 to 4294967295. (Read-write access).

Pass / Fail

25. Change the community name in the test application to NewYork. Pass / Fail


27. Verify that the Response Value for globalTime.0 is valid. Pass / Fail

28. Set globalTime.0 to 1000000000. Pass / Fail

29. Verify that the Set is accepted without error. Pass / Fail


of 70 04/14/2017 Rev. 07/07/2017


31. Verify that the Response Value for globalTime.0 is valid, incremented by the time that elapsed between step 20 and step 29.

Pass / Fail

32. Get communityNamesMax.0. Pass / Fail

33. Verify that the Get is rejected. Pass / Fail



36. Get communityNameIndex.1 Pass / Fail


38. Get communityNameUser.1 Pass / Fail


40. Get communityNameAccessMask.1 Pass / Fail


42. Change the community name in the test application to administrator, or the valid the administrator community name.

Pass / Fail

43. Set communityNameAdmin.0 to NewYorkadmin. Pass / Fail

44. Without changing the community name in the test application, Set communityNameAdmin.0 to NewYorkadmin1.

Pass / Fail

45. Verify the Set attempt is rejected. Pass / Fail

46. Change the community name in the test application to NewYorkadmin.

Pass / Fail

47. Get communityNamesMax.0 Pass / Fail

48. Verify that the Response Value for communityNamesMax.0 is valid. Pass / Fail


50. Verify that the Response Value for communityNameAdmin.0 is valid. Pass / Fail

51. Get communityNameIndex.1 Pass / Fail

52. Verify that the Response Value for communityNameIndex.1 is valid. Pass / Fail

53. Get communityNameUser.1 Pass / Fail


of 70 04/14/2017 Rev. 07/07/2017

54. Verify that the Response Value for communityNameUser.1 is valid. Pass / Fail

55. Get communityNameAccessMask.1 Pass / Fail

56. Verify that the Response Value for communityNameAccessMask.1 is valid.

Pass / Fail

57. Restore communityNameUser.1 to the original value from step 7. Pass / Fail

58. Restore communityNameAccessMask.1 to the original value from step 7.

Pass / Fail

59. Restore communityNameAdmin.0 to the original value from step 5. Pass / Fail

Test Case Result:

Pass / Fail

Test Case Notes:

2.14 TC014 – Pixel Failures

Test Case: Title: TC014

Pixel Failures

Description: The purpose of this test is to verify that the sign correctly reportspixel failures.

Pass/Fail The DUT shall pass every step described in this test case in order toCriteria: pass this test.


1. Set dmsActivateMessage.0 to FF FF FF 07 00 01 00 00 01 03 03 Pass / Fail 04 to blank the display.

2. Set pixelTestActivation.0 to 4 (clearTable) to clear the pixel error table. Pass / Fail

3. Get pixelFailureTableNumRows.0 Pass / Fail

4. Verify that the Response Value for pixelFailureTableNumRows.0 is 0. Pass / Fail

5. Set pixelTestActivation.0 to 3 (test) to carry out a pixel test. Pass / Fail

6. Wait until the pixel test is complete and the display is blank.

7. Get pixelTestActivation.0 Pass / Fail

8. Verify that the Response Value for pixelTes ation.0 is 2 (no test). Pass / Fail

9. Get pixelFailureTableNumRow.0 Pass / Fail


of 70 04/14/2017 Rev. 07/07/2017

10. Verify that the Response Value for pixelFailureTableNumRow.0 is 0 Pass / Fail

11. Remove one LED panel from the sign.

12. Calculate the expected number of failures by computing the module rows X module columns (example 35 for a 5 X 7 module).





17. Verify that the Response Value for pixelTestActivation.0 is 2 (no test). Pass / Fail

18. Verify that the Response Value for pixelFailureTableNumRows.0 is valid.

Pass / Fail

19. Get pixelFailureDetectionType.2.1 Pass / Fail

20. Verify that the Response Value for pixelFailureDetectionType.2.1 is 2.

Pass / Fail

21. Get pixelfailureIndex.2.1 Pass / Fail

22. Verify that the Response Value for pixelfailureIndex.2.1 is 1. Pass / Fail

23. Get pixelFailureXLocation.2.1 Pass / Fail

24. Verify that the Response Value for pixelFailureXLocation.2.1 equals the column number of one of the failed pixels as counted from the left side of the sign.

Pass / Fail

25. Get pixelFailureYLocation.2.1 Pass / Fail

26. Verify that the Response Value for pixelFailureYLocation.2.1 equals the row number of one of the failed pixels as counted from the top of the sign.

Pass / Fail

27. Get pixelFailureStatus.2.1 Pass / Fail

28. Verify that the Response Value for pixelFailureStatus.2.1 is 1. Pass / Fail

29. Get pixelFailureDetectionType.2.X Pass / Fail

30. Verify that the Response Value for pixelFailureDetectionType.2.X is 2 Pass / Fail

31. Get pixelfailureIndex.2.X Pass / Fail

32. Verify that the Response Value for pixelfailureIndex.2.X is 1. Pass / Fail

33. Get pixelFailureXLocation.2.X Pass / Fail


of 70 04/14/2017 Rev. 07/07/2017

34. Verify that the Response Value for pixelFailureXLocation.2.X equals the column number of one of the failed pixels as counted from the left side of the sign.

Pass / Fail

35. Get pixelFailureYLocation.2.X Pass / Fail

36. Verify that the Response Value for pixelFailureYLocation.2.X equals the row number of one of the failed pixels as counted from the top of the sign.

Pass / Fail

37. Get pixelFailureStatus.2.X Pass / Fail

38. Verify that the Response Value for pixelFailureStatus.2.X is 1. Pass / Fail

39. Replace the Module.




43. Verify that the Response Value for pixelTestActivation.0 is 2 (no test). Pass / Fail


45. Verify that the Response Value for pixelFailureTableNumRows.0 is 0. Pass / Fail

Test Case Result:

Pass / Fail

Test Case Notes:

2.15 TC015 – Power Supply Error Status

Test Case:

TC015

Title: Power Supply Error Status

Description: The purpose of this test is to verify that the sign reports power supply errors.

Pass/Fail Criteria: The DUT shall pass every step described in this test case in order to

pass this test.



of 70 04/14/2017 Rev. 07/07/2017

1. Get lineVolts.0 Pass / Fail

2. Verify that the Response Value for lineVolts.0 is 110 (or the value Pass / Fail of the AC line voltage on the sign)

3. Get powerSource.0 Pass / Fail

4. Verify that the Response Value for power .0 is 4 (acLine). Pass / Fail

5. Get shortErrorStatus.0 Pass / Fail

6. Verify that the Response Value for shorterrors).

ErrorStatus.0 is 0 (no Pass / Fail

7. Disconnect the AC power to the sign.

8. Verify that the sign controller continues to run from the UPS power supply.

Pass / Fail


10. Verify that the Response Value for powerSource.0 is either 3 (no sign power) or 7 (battery).

Pass / Fail


12. Verify that the Response Value for lineVolts.0 is 0 (to reflect that AC Power is absent).

Pass / Fail


14. Verify that the Response Value for short ErrorStatus.0 is 4 (power error).

Pass / Fail

15. Restore AC Power to the sign.


17. Verify that the Response Value for lineVolts.0 is 110 (or the value of the AC line voltage on the sign)

Pass / Fail


19. Verify that the Response Value for powerSource.0 is 4 (AC Line). Pass / Fail


21. Verify that the Response Value for short ErrorStatus.0 is 0 (no errors).

Pass / Fail

22. Disconnect a power supply in the sign.



of 70 04/14/2017 Rev. 07/07/2017


25. Reconnect the power supply.


27. Verify that the Response Value for lineVolts.0 is 110 (or the value of the AC line voltage on the sign)

Pass / Fail




31. Verify that the Response Value for short ErrorStatus.0 is 0 (no errors).

Pass / Fail

Test Case Result:

Pass / Fail

Test Case Notes:

2.16 TC016 – Temperature and Status

Test Case:

TC016

Title: Temperature and Status

Description: The purpose of this test is to verify that the sign correctly implements the temperature reporting requirements.

Pass/Fail Criteria:



1. Get the following objects: tempMinSignHousing.0 tempMaxSignHousing.0

Pass / Fail

2. Verify that the Response Values for tempMinSignHousing.0 and tempMaxSignHousing.0 reflect the temperature range within the sign

Pass / Fail

3. Using a heat gun, heat the temperature probe (or one of the temperature probes) in the sign.


of 70 04/14/2017 Rev. 07/07/2017


Pass / Fail

5. Verify that the Response Values for tempMinSignHousing.0 and tempMaxSignHousing.0 reflect the temperature range within the sign housing, reflecting the increase in temperature due to the application of heat with the heat gun.

Pass / Fail

6. Remove the heat gun, and allow the temperature probe that was heated in step 3 to cool.


Pass / Fail

8. Verify that the Response Values for tempMinSignHousing.0 and tempMaxSignHousing.0 reflect the temperature range within the sign housing, reflecting the decrease in temperature due to the

Pass / Fail

Test Case Result:

Pass / Fail

Test Case Notes:

2.17 TC017 – Field Display

Not applicable to this type of sign.

2.18 TC018 – Reports

Test Case: Title: TC018

Reports

Description: The purpose of this test is to verify that the sign correctly responds to the report objects for logging events in the sign.




of 70 04/14/2017 Rev. 07/07/2017

1. Note:

This test Sets up monitoring on the following sign functions:

1. Change in the Current Message. 2. Change in the door status from closed to open and back to

closed. 2. Set globalTime.0 to 1098711600 (10/25/04 1:40:00 PM) Pass / Fail

3. Set co ntrollerStandardTimeZone.0 to 0 Pass / Fail

4. Set controllerDSTStatus.0 to 2 (enable DST). Pass / Fail

5. Get maxEventClasses.0 Pass / Fail

6. Verify that the Response Value for maxEventClasses.0 is greater Pass / Fail than or equal to 16.

7. Record the Response Value for maxEventClasses.0 as “X”.

8. Get maxEventLogSize.0 Pass / Fail

9. Verify that the Response Value for maxEventLogSize.0 is greater than or equal to 255.

Pass / Fail

10. Get maxEventLogConfigs.0 Pass / Fail

11. Verify that the Response Value for maxEventLogConfigs.0 is greater than or equal to 60.

Pass / Fail

12. Record the Response Value for maxEventLogConfigs.0 as “Y”.

13. For each value of N from 1 to “X” (maxEventClasses.0):

Set eventClassLimit.N to 0 Set eventClassClearTime.N to 4294967295 Get eventClassNumRowsInLog.N Verify that the Response Value for eventClassNumRowsInLog.N is0. Increment N until N is greater than “X” (maxEventClasses.0)

Pass / Fail

14. For each value of N from 1 to “Y” (maxEventLogConfigs.0):

Set eventConfigAction.N to 2 (disabled) Increment N until N is greater than “Y” (maxEventLogConfigs.0)

Pass / Fail

15. Set eventClassLimit.1 to 20 Pass / Fail

16. Set eventClassDescription.1 to “CURRENT MESSAGES” Pass / Fail


of 70 04/14/2017 Rev. 07/07/2017


18. Set eventClassDescription.6 to “DOOR STATUS” Pass / Fail


20. Set eventClassDescription.16 to “AC VOLTAGE” Pass / Fail

21. Set eventConfigClass.1 to 1 Pass / Fail

22. Set eventConfigMode.1 to 2 (on change) Pass / Fail

23. Set eventConfigCompareOID.1 to 1.3.6.1.4.1206.4.2.3.5.8.1.3.5.1 (current message multi string).

Pass / Fail

24. Set eventConfigLogOID.1 to 1.3.6.1.4.1206.4.2.3.5.8.1.3.5.1 (current message multi string).

Pass / Fail

25. Set eventConfigAction.1 to 3 (log). Pass / Fail


27. Set eventConfigMode.7 to 2 (on change). Pass / Fail

28. Set eventConfigCompareOID.7 to 1.3.6.1.4.1.1206.4.2.3.9.6.0 (dmsStatDoorOpen.0)

Pass / Fail

29. Set eventConfigLogOID.7 to 1.3.6.1.4.1.1206.4.2.3.9.6.0 (dmsStatDoorOpen.0)

Pass / Fail

30. Set eventConfigAction.7 to 3 (log). Pass / Fail


32. Set eventConfigMode.47 to 4 (Smaller Than Value) Pass / Fail

33. Set eventConfigCompareValue.47 to 100 (volts) Pass / Fail

34. Set eventConfigCompareOID.47 to 1.3.6.1.4.1.1206.4.2.3.9.8.5.0 (line volts)

Pass / Fail

35. Set eventConfigLogOID.47 to 1.3.6.1.4.1.1206.4.2.3.9.8.5.0 (line volts) Pass / Fail

36. Set eventConfigAction.47 to 3 (log) Pass / Fail


38. Set eventConfigMode.48 to 3 (Greater Than Value) Pass / Fail



Pass / Fail


of 70 04/14/2017 Rev. 07/07/2017

41. Set eventConfigLogOID.48 to 1.3.6.1.4.1.1206.4.2.3.9.8.5.0 (line volts) Pass / Fail



44. Set eventConfigMode.49 to 4 (Smaller Than Value) Pass / Fail



Pass / Fail

47. Set eventConfigLogOID.49 to 1.3.6.1.4.1.1206.4.2.3.9.8.1.0 (sign volts) Pass / Fail


49. Set eventConfigMode.50 to 3 (Greater Than Value) Pass / Fail



Pass / Fail

52. Set eventConfigLogOID.50 to 1.3.6.1.4.1.1206.4.2.3.9.8.1.0 (sign volts)

Pass / Fail


54. Using the dialog from Test Case TC002, download and display Changeable Message 1 “TEST 1”.

Pass / Fail


56. Using the dialog from Test Case TC002, download and display Changeable Message 2 “TEST 2”.

Pass / Fail


58. Set dmsActivateMessage.0 to FF FF FF 07 00 01 00 00 01 02 03 04 (blank the display).

Pass / Fail


60. Get eventClassNumRowsInLog.1 Pass / Fail

61. Verify that the Response Value for eventClassNumRowsInLog.1 is 3. Pass / Fail

62. Get the following objects: eventLogID.1.1 eventLogID.1.2 eventLogID.1.3

Pass / Fail


of 70 04/14/2017 Rev. 07/07/2017

63. Verify that the Response Value for: eventLogID.1.1, eventLogID.1.2, and eventLogID.1.3 is 1.

Pass / Fail

64. Get the following objects: eventLogTime.1.1 eventLogTime.1.2 eventLogTime.1.3

Pass / Fail

65. Verify that the Response Value for eventLogTime.1.1 is 109871600 plus the elapsed duration between Step 2 and Step 54.

Pass / Fail

66. Verify that the Response Value for eventLogTime.1.2 is 10 to 20 greater than the Response Value for eventLogTime.1.1.

Pass / Fail

67. Verify that the Response Value for eventLogTime.1.3 is 10 to 20 greater than the Response Value for eventLogTime.1.2.

Pass / Fail

68. Get eventLogValue.1.1 Pass / Fail

69. Verify that the Response Value for eventLogValue.1.1 is 44 08 04 05 54 45 53 54 20 31

Pass / Fail


71. Verify that the Response Value for eventLogValue.1.2 is 44 08 04 05 54 45 53 54 20 32

Pass / Fail


73. Verify that the Response Value for eventLogValue.1.3 is 44 02 04 00 Pass / Fail

Test Case Result:

Pass / Fail

Test Case Notes:

2.19 TC019 – Brightness Control

Test Case:

TC019

Title: Brightness Control

Description: The purpose of this test is to verify that the sign correctly utilizes brightness


of 70 04/14/2017 Rev. 07/07/2017

Pass/Fail Criteria: The DUT shall pass every step described in this test case in order to pass this test.


1. Get dmsIllumControl.0 Pass / Fail

2. Get dmsIllumMaxPhotocellLevel.0 Pass / Fail

3. Get dmsIllumPhotocellLevelStatus.0 Pass / Fail

4. Get dmsIllumNumBrightLevels.0 Pass / Fail

5. Verify that the Response Value for dmsIllumNumBrightLevels.0 (x) equals or exceeds 16.

Pass / Fail

6. Get dmsIllumBrightLevelStatus.0 Pass / Fail

7. Get dmsIllumManLevel.0 Pass / Fail

8. Get dmsIllumBrightnessValues.0 Pass / Fail

9. Get dmsIllumBrightnessValuesError.0 Pass / Fail

10. Get dmsIllumLightOutputStatus.0 Pass / Fail

11. Set dmsIllumControl.0 to 2 (photocell). Pass / Fail

12. Change the light value entering the photocell, by covering it if the ambient light is bright, or by shining a light on it if the ambient light is low.

Pass / Fail

13. Verify that the following objects change to reflect the new value of light entering the photocell: dmsIllumPhotocellLevelStatus.0 dmsIllumBrightLevelStatus.0 dmsIllumLightOutputStatus.0

Pass / Fail

14. Verify that the actual brightness of the sign has changed in accordance with the new parameters.

Pass / Fail

15. Set dmsIllumControl.0 to 4 (manual). Pass / Fail

16. Set the dmsIllumManLevel.0 to 1 Pass / Fail

17. Verify that this sign is dim. Pass / Fail




of 70 04/14/2017 Rev. 07/07/2017

20. Set dmsIllumManLevel.0 to the value (x) returned by dmsIllumNumBrightLevels.0

Pass / Fail

21. Verify that the sign is bright. Pass / Fail


23 Verify that the value equals (x). Pass / Fail


25. Restore dmsIllumControl.0 and dmsIllumManLevel.0 to their original values.

Pass / Fail

Test Case Result:

Pass / Fail

Test Case Notes: