item 683.4503 11m arterial full matrix, led based ... · mark iv ids mississauga (mark iv...

ITEM 683.4503 11M ARTERIAL FULL MATRIX, LED BASED, VARIABLE MESSAGE SIGN,

TWO ROW

of 71 10/31/2007

DESCRIPTION

This work shall consist of furnishing and installing front access Variable Message Sign (VMS)assemblies consisting of LED elements in a full matrix configuration in accordance with the Contractdocuments. The Contractor shall install the VMS on sign structures described under other items and asindicated in the plans. This item shall include all sign modules, sign housing, VMS controller, fittingsand cabling to make the sign compatible with the control software defined in this document.

MATERIALS

The VMS shall meet the requirements of §730-27, Permanent Variable Message Signs, as supplementedby this specification with the more stringent requirement governing.

To ensure compatibility and interchangeability with equipment furnished under previous projects, allVariable Message Sign assemblies shall be as manufactured by

Daktronics, Inc.331 32nd AvenueBrookings SD 57006Phone: (888) 325-8766OrSkyline Products, Inc.2903 Delta DriveColorado Springs, CO 80910Phone: (800) 759-9046OrMark IV IDS Mississauga (Mark IV Industries Ltd. - Head Office)6030 Ambler DriveMississauga, Ontario, Canada, L4W 2P1Tel: (905)624-3020

Or equal as approved by Engineer.

REQUIREMENTS

The VMS Assembly shall meet the following requirements:

1 Variable Message Sign

The VMS shall consist of amber Light Emitting Diode (LED) pixel based matrix modules arranged toform a full matrix display. The VMS modular display shall contain a minimum of 96 pixels across and 16pixels high (1,536 pixels). The matrix shall be capable of displaying, at a minimum, two (2) rows ofsixteen (16) characters each, with a nominal character size of 320 mm high and 228 mm wide using a 7x5pixel matrix for each character. The character size shall be variable with a maximum character heightequal to the display matrix height. VMS messages shall be legible within a distance range of 45.72m to


TWO ROW

of 71 10/31/2007

274.3m from the VMS display face under the following conditions: When the VMS is mounted so its bottom side is positioned between 5,350 mm and 6,096 mm

above the roadway surface. Whenever the VMS is displaying alphanumeric text that is 320 mm high. All natural lighting levels encountered 24 hours per day. During dawn and dusk hours when sunlight is shining directly on the display face or when the sun

is directly behind (silhouetting) the VMS. When viewed by motorists and travelers that have 20-20 corrected vision. When motorists’ and travelers’ eye level is 914mm to 3,658 mm above the roadway surface.

Sign and modules shall be constructed to meet the following requirements:

1.1 Front Accessible

1.2 30 Degree viewing cone, with a Pixel Pitch 46mm.

1.3 All maintenance performed from the front sign face or within the controller cabinet.

1.4 Pixel Spacing of not greater than 46 mm center-to-center.

1.5 Equal horizontal and vertical pixel spacing.

1.6 Total weight of the VMS not to exceed 500 kg.

1.7 Maximum current required by the VMS not to exceed 50 amps total.

1.8 Power source:120/240 VAC, 60 Hz, 3 wire single phase plus neutral and ground.

1.9 Each display pixel shall be comprised of multiple monochrome amber LEDs. Other pixeltechnologies, such as fiber optic, flip disk, combination flip disk-fiber optic, combination flipdisk LED, liquid crystal, and incandescent lamp, will not be accepted.

1.10 All pixel modules, assemblies and components shall be compatible and interchangeablebetween signs provided under this item.

1.11 The replacement of any display module, or pixel on a display module, shall not require anyother unit to be removed, and shall not require the use of any special tools.

1.12 All wiring interconnecting individual components or assemblies shall be modular harnessassemblies and shall be mechanically keyed to prevent insertion into the wrong socket orconnector.

1.13 Shielding of the electronics to prevent radiation of any electrical or electromagnetic signals thatcould adversely affect any other electrical or electronic device, as per FCC rule Part 15,Class B.

1.14 The presence of ambient noise generated within 0.3 m of any of the components of the VMSshall not adversely affect the performance of the VMS. The sources of ambient noise shallinclude, but not be limited to, radio signals, magnetic or electromagnetic interference, includingthose from power lines, roadway lights, transformers or motors.

1.15 Each pixel shall be individually addressable and controllable to allow for the display, on anyportion of the message face, of static text or the flashing of all or any part of the text, together


TWO ROW

of 71 10/31/2007

with message formation by alternating between two or more static or flashing text messages.

1.16 The electronics for the VMS shall be fully configured to drive the total required number ofLEDs. The failure of any one pixel shall not affect the operation of any other pixel.

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

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

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

1.19.1 The LEDs shall be amber, with a peak wavelength centered at 590 ± 5 nanometers.

1.19.2 The quantity of LEDs used in each pixel shall be sufficient to provide a minimum pixeloutput of 40 candelas for the amber color.

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

1.19.4 The LED mean time between failure (MTBF) shall be a minimum of 100,000 hours ofpermanent use at an operating temperature of 60 degrees Celsius, when driven at thespecific forward current used for normal daylight LED VMS display operation. Wherefailure is defined as a maximum drop in candela output of 70% over 100,000 hours.

1.19.5 All LEDs shall have a nominal 30 degree viewing cone with a half power angle of 15degrees measured from the vertical (longitudinal) axis of the LED. The viewing conetolerances specified in the manufacturer’s product specification shall not exceed + 3degrees. For the LEDs intended for use in the signs in this Contract the Contractorshall provide LED manufacturer’s data that includes the specified tolerances to theEngineer.

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

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

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

1.19.9 Monitoring of each pixel by the VMS controller for subsequent transmission of pixelstatus information to the control center.

1.20 The LED display modules shall be protected from degradation due to sunlight. The method anddesign of the LED VMS sunlight protection shall be approved by the Engineer.

1.21 Each pixel consists of a cluster of LEDs, switched on and off via commands from the signcontroller and warranted in accordance with Section 105-18 Warranties and Guarantees of theStandard Specification against defective operation. The LEDs in each pixel shall be


TWO ROW

of 71 10/31/2007

configured in two or more strings such that the failure of an LED in one string shall not causethe failure of the LEDs in the other strings. The strings shall be distributed in each pixel suchthat the failure of one string will not result in an asymmetrical pattern being displayed.

1.22 The removal or failure of a single pixel or module shall not effect the operation of any otherpixel or module.

1.23 Power supplies shall be redundant such that the failure of a single power supply will produce nonoticeable effect on the message display.

1.24 All printed circuit boards shall be FR4 or G10 fiberglass epoxy material, with 68 µm copper,double-sided with plated through-holes.

1.25 All etched connector fingers are to be plated with a minimum thickness of 2.5 µm of gold overnickel.

1.26 Board connectors that are not an integral part of the printed circuit are to be plated with aminimum thickness of 0.38 µm of gold over nickel.

2 VMS Housing

The VMS housing shall be a front access type and shall conform with all applicable requirements of goodEngineering practices for construction and workmanship. The equipment, including all parts andaccessories, shall be constructed in a thoroughly workmanlike manner and in accordance with bestcommercial practice. The VMS housing shall meet the following requirements:

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

2.2 The housings shall be fabricated from 3.2 mm (minimum) thick aluminum alloy 3003-H14,6061-T6 or 5154-H38, designed to withstand the loads specified under “Design Criteria” of §730-27, Permanent Variable Message Signs.

2.3 Fabrication shall be such that performance shall not be impaired after the equipment has beensubjected to shock and vibration caused by normal installation, transportation and maintenancehandling.

2.4 The housing shall be constructed to present a clean, neat appearance. Particular attention shallbe given to neatness and thoroughness of soldering, wiring, welding, plating, riveting, finishesand machine operations. All parts shall be free from burrs and sharp edges or any other defectthat could make the part or equipment unsatisfactory for the operation or function intended inthis specification.

2.5 VMS housing’s right, left, and rear walls shall be vertical. The top and bottom sides shall behorizontal. LED display modules shall be mounted parallel to the front wall with the legibleLED viewing area optimized.

2.6 Permanent corrosion protection shall be provided between all dissimilar metals.2.7 The housing shall be completely sealed to prevent the entry of water and dust. Seals, baffles,

neoprene gaskets and screens to prevent the entry of water, dust and insects shall be used, asrequired, to protect equipment located within the housing from moisture, dust, dirt andcorrosion.


TWO ROW

of 71 10/31/2007

2.8 Screened weep holes shall be provided at each corner of the enclosure to allow the drainage ofany water that may collect in the housing.

2.9 All exterior seams shall be continuously welded by an inert process only in the shop such thateach weld has a uniform flow. Alternative seam bonding methods shall be approved by theEngineer.

2.10 The housing shall contain an interior non-corrosive metal cage support frame to mount thedisplay elements. The cage support frame shall withstand and minimize vibration when the signis mounted with any number of display elements.

2.11 The housing and cage support frame shall be configured such that there shall be a continuousunobstructed horizontal clearance from electrical components as required by the NationalElectric Code.

2.12 The overall VMS housing dimensions shall no exceed 1.20m High x 5.6m Wide x .4m Deep.

2.13 The Engineer shall approve the front access method. The access panel(s) shall be fastenedclosed by means of captive fasteners. The access panel (s) or windows must be fitted withadequate hold-open devices for safety and ease of maintenance, and they shall not be releasedaccidentally or by the action of the wind on the open window. They shall not interfere with theoperation of the display when the windows are held open or when the windows are closed. Theaccess panel(s) shall be lockable from the outside to prevent intrusion or vandalism but shallallow a person to have complete access to all serviceable equipment.

2.14 If the front access is provided to the display modules by means of a top-hinged window(s) adevice shall be provided to hold the hinged window open in the 90 degree or greater position asneeded to service the equipment inside the housing.

2.15 At locations where VMS will be installed in conjunction with fixed signing, the signs shall bemounted so that the front sign faces are flush as shown on the plans. Under these items, theContractor shall furnish and install all structural members in order to extend the fixed sign inorder to accomplish this requirement.

2.16 Access to the housing shall be positioned such that a person on a lift has safe access to allcomponents within the VMS enclosure.

2.17 Conduit Provisions - Separate power and sign control conduit connections shall be provided.VMS control and power cables shall be isolated from each other in all locations. The size ofthe conduits shall be as shown on the plans. The Contractor shall provide all conduitattachment hardware as required.

2.18 Multiple mounting brackets in the form of I-beams or Z-extrusions shall be bolted to the VMShousing’s exterior rear wall to facilitate attachment of the VMS to the support structure. Mounting brackets shall be:

2.18.1 Extruded from aluminum alloy number 6061-T6.

2.18.2 Attached to the VMS structural frame members, not just the exterior sheet metal.

2.18.3 Installed at the VMS manufacturer’s factory.


TWO ROW

of 71 10/31/2007

2.18.4 Attached to the VMS using Type B-8 stainless steel bolts.

2.18.5 Attached to the VMS using direct tension indicators to verify that mounting hardwareis tightened with the proper amount of force.

2.18.6 Installed such that all bracket-to-VMS attachment points are sealed and water-tight.

2.18.7 Designed and fabricated such that the installing Contractor can drill into them withoutpenetrating the VMS housing and compromising the housing’s ability to shed water.

2.19 Louvered vents shall be provided on the sides of the housing as necessary, to provide sufficientventilation. All fans or other forced air devices shall be thermostatically controlled and shalluse standard-size removable dust filters. Filters provided with the VMS shall have a MERVrating of 8 or better. All fans shall have ball or roller bearings.

2.20 Two lifting eyes shall be provided on the VMS housings to permit lifting of the sign housing onto the sign structure. The fully assembled sign shall be lifted into place using both lifting eyes,each lifting eye shall be of sufficient structural strength to allow the sign be lifted or movedwithout damage or permanent deformation to any part of the sign.

2.21 Shop drawings and calculations that show the sign’s ability to withstand the design loads shall be submitted to the Traffic Engineering and Highway Safety Division for approval, and shall besigned by a Professional Engineer licensed and registered to practice in New York State.

2.22 The front face of the VMS housing shall be extended 300 mm beyond the message area of thesign creating a blank, flat black border area that is integral to the housing. Add-on elements tocreate the border are not allowed.

2.23 Environmental Requirements:

The equipment shall meet all of its specified requirements during and after subjection to anycombination of the following requirements:

Ambient Temperature - Range of -34 degree C to +74 degree C.

Temperature Shock - Not to exceed 17 degree per hour, during which the relative humidityshall not exceed 95%.

Relative Humidity Range - Not to exceed 95% over the temperature range of 4 degree C to +43degree C.

Moisture Condensation - On all surfaces caused by temperature changes.

2.24 Minimum access dimensions to the VMS interior housing shall be indicated in the Shopdrawings and shall be approved by the Engineer.

2.25 Access to the installed VMS housing shall be from a lift vehicle or other similar means.

2.26 Safety labels in accordance with OSHA, NEMA and NEC requirements shall be used to


TWO ROW

of 71 10/31/2007

indicate potential dangerous or hazardous situations. The contents of the labels shall be inaccordance with the ANSI Z535.4 standard, Product Safety Signs and Labels.

2.27 15 A 120 VAC duplex electrical outlets, with ground fault circuit interrupters, for use bymaintenance personnel shall be mounted along the interior panels. These outlets shall bepowered from an isolated, separately controllable electrical circuit. The outlets shall be ULlisted.

2.28 Separate circuits shall be provided to energize the VMS, power the maintenance lights andpower the maintenance outlets. A breaker box sized for a minimum of three circuits rated for120 VAC 50 AMP source shall be provided. The breaker box shall be furnished with aminimum of three circuit breakers rated at 22,000 AIC and sized as following:

2.28.1 As required to energize the VMS.

2.28.2 15 amps GFI protected for portable maintenance lights.

2.28.3 15 amps GFI protected for the maintenance outlets.

2.29 Two threaded conduit hubs shall be located on the rear wall of the VMS housing. One hub shallbe for incoming AC power and the other shall be for incoming VMS signal cabling or acommunications line.

2.30 Surge protection devices for all external cabling entering the assembly shall be provided. Thesurge protection shall be mounted as close to the cable entry as possible. The surge protectorsshall be grounded in accordance with the manufacturer’s recommendation. The AC power line surge protector shall be installed between the load side of the input power circuit breaker orfuse and ground. The surge protector shall meet the following requirements:

2.30.1 Working Voltage Rating: AC power line with a voltage rating of 130 V RMS and 184V peak.

2.30.2 Surge Voltage: Limit the surge voltage applied to the equipment to 650 V peak whileconducting a peak surge current of at least 20,000 A. The surge current shall be anunsymmetrical triangle wave (8 x 20 us) that requires 8 us to reach its peak value and20 us to fall to half the peak value.

2.30.3 Energy Rating: Dissipate 50 joules of surge energy without damage to itself and shallhave a 15watt power dissipation rating.

2.31 Sensors shall be provided to monitor the internal and external temperature of the sign. Thesensors shall be monitored continuously by the sign controller. If the temperature exceeds auser defined threshold, the sign ventilation system shall be activated and an error message shallbe returned with the sign status. If the temperature exceeds a higher preset threshold, the signshall shut down and an error message shall be returned with the sign status.

2.32 Current carrying capacity of all conductors shall comply with the NEC.

2.33 All conductors, terminals, and parts which could be hazardous to maintenance personnel shallbe protected with suitable insulating material.


TWO ROW

of 71 10/31/2007

2.34 Safety labels in accordance with OSHA, NEMA, and NEC requirements shall be used toindicate potentially dangerous or hazardous situations. The contents of safety labels shall be inaccordance with the ANSI Z535.4 standard, Product Safety Signs and Labels.

2.35 The housing shall be thoroughly cleaned and then neutralized for priming. The housing shallthen be treated with a phosphate coating solution and sealed as per U. S. GovernmentSpecification MIL-C-5541. The surface shall be prepared for priming per the manufacturer’s recommended pretreatment procedure.

2.36 All metallic exterior surfaces visually exposed are to be coated with a Urethane or TriglycidylIscocyanurate (TGIC) polyester powder to a minimum dry film thickness of 2.0 mils or coatedwith a matte-black, licensed-factory-applied, KYNAR 500 Resin, fluropolymer-based coatingsystem. Prior to application, the surfaces to be powder coated are to be mechanically etched bybrush blasting and zinc coated substrate preheated to 232 degrees Celsius for a minimum of onehour in a gas-fired convention oven. The coating shall be electrostatically applied and cured byelevating the zinc coated substrate temperature to a minimum of 177 degrees Celsius in gas-fired convention oven. The powder coating shall comply with ASTM A775 and ASHTO M284standards. The Contractor shall provide certification of compliance with these requirements. Ifthe KYNAR method is chosen, the Contractor shall provide certification from the licensed-factory KYNAR 500 coater for all aluminum materials.

2.37 The finish of all exterior surfaces of the VMS housing shall be matte black.

2.38 Front face panels shall provide a high-contrast background for the VMS display matrix. Thealuminum mask of each panel shall be painted black and contain an opening optimizing thecontrast ratio for each LED pixel. Openings shall be large enough to not block any portion ofthe LED-viewing angle.

2.39 The pixels within the message area of the sign shall be covered and protected with a singlesheet, UV stabilized, anti-glare polycarbonate front panel or other protection system approvedby the Engineer. The panel shall be a minimum of 6.35 mm thick. The front panel shall bemounted to withstand a 193 kmph wind load without deflecting sufficiently to obscure any ofthe pixels in the sign. The panel shall be replaceable and shatter resistant.

2.40 The sign shall be designed or equipped to prevent fogging or ice and snow build-up along thefaceplate and may use heater strips or a forced heated air system. The defogging / deicingsystem shall be automatically activated when conditions for fogging or ice and snow build-upoccur.

2.41 All internal diagonals and other structural supports shall be spaced so as not to hinder themovement of maintenance personnel within the sign nor interfere with the maintenance orreplacement of any of the components mounted within the sign.

2.42 Markings: The contract number, pay-item number, and month and year of installation shall bemarked using permanent ink, paint or stamping into the wall. Characters shall be 25-45 mmhigh, horizontal when the variable message sign is in its final position, and be located in thefollowing locations:2.42.1 The end panel of the VMS so as to be visible from the shoulder closest to the VMS.


TWO ROW

of 71 10/31/2007

2.42.2 On the inside near the middle of the end panels or as approved by the Engineer.2.43 The manufacturer’s name, product name, model number, serial number and city and state or

province of manufacturer also shall be permanently marked on the outside and an easilyaccessible location inside the VMS.

2.44 The markings shall not be visible when viewing the VMS straight-on from the ground.

3 VMS Controller

Each sign shall be operated by a microprocessor-based controller that provides the electronics necessaryto receive and interpret commands from the Central Control System (CSS), to issue a response to theCCS, and to display messages on the sign. The VMS controller shall be housed in an enclosure andmounted as shown in the contract drawings. At locations designated in the contract documents where theVMS controller is to be mounted in a controller cabinet external to the VMS, the cabinet shall beprovided under a separate item of the contract documents. To ensure compatibility and interchageabilitythe VMS controller specified herein shall be identical to other VMS controllers supplied on this projectby the same manufacturer; therefore, some requirements may not be used by VMS display specifiedherein.

The sign controller shall be provided with error detection and reporting features, which shall be utilized toguard against incomplete or incorrect information transmission, message generation and display on eachsign face. These features are required to prevent misinformation being displayed to the motorist user topreclude the possibility of a hazardous roadway condition developing. The Sign controller will contactthe CCS or TOC when a problem or alarm is detected.

The VMS controller shall provide the following features:

3.1 The sign controller shall be designed to mount in a standard 19-inch rack, occupying amaximum of 5U rack space. The depth of the controller shall not exceed 380mm.

3.2 The sign controller shall support full duplex serial communications between the CCS and theVMS controller.

3.3 Provide two NTCIP-compatible RS232 ports for communication between the sign controllerand the CCS with each port connected to a separate communication channel through an externalmodem. The controller shall respond to the last command received, which may be on eitherchannel, and respond on both channels. The CCS will only transmit commands over onechannel at a time.

3.4 Provide a third NTCIP-compatible RS232 port for communication between the sign controllerand a local laptop through a direct null-modem connection.

3.5 Communications between the VMS controller and the CCS and notebook computer shallcomply with the NTCIP as detailed in the following NEMA Standards Publications:

3.5.1 NTCIP 1101:1996 and Amendment 1 – Simple Transportation ManagementFramework (STMF)

ITEM 683.4503 11 M ARTERIAL FULL MATRIX, LED BASED, VARIABLEMESSAGE SIGN

of 71 10/31/2007

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

3.5.3 NTCIP 1201:1996 and Amendment 1–Global Object (GO) Definitions

3.5.4 NTCIP 1203:1997 and Amendment 1 –NTCIP Object Definitions for DynamicMessage Signs

3.5.5 NTCIP 2001:1996 and Amendment 1–NTCIP Class B Profile

3.5.6 NTCIP 2101:2001 –Point-to-MultiPoint Protocol (PMPP) Using RS-232 SubnetworkProfile

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

3.5.8 NTCIP 2104 v1.10–Ethernet Subnetwork Profile

3.5.9 NTCIP 2201 v1.14–Transportation Transport Profile

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

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

3.6 Unless otherwise stated, the software shall comply with the versions of the NTCIP standardsthat are current at the date of Contract award.

3.7 As part of the 30-day submission the VMS manufacturer shall submit details of the specificstandards to be implemented, applicable conformance groups, applicable data objects and theirassociated range values, and any other information, including, but not limited to manufacturerspecific MIBs, that are pertinent to the implementation of this specification.

3.8 The sign controller shall have sufficient non-volatile memory for downloading and uploadingmessages, and configuration, status, and alarm data as specified herein.

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

3.10 The sign controller shall instruct the LED driver circuitry in a manner that causes the desiredmessage to display on the VMS sign controller. At a minimum, the sign controller shall supportthe following features as described in the VMS specification:

3.10.1 Display of alpha numeric character fonts and graphic pictures

3.10.2 Message format details such as centering text on a display line, right justification, leftjustification, and legible spacing of letters and words

3.10.3 Selection of a particular character font style

3.10.4 Display of static messages

3.10.5 Flashing of all or part of a message

3.10.6 Message scrolling

3.10.7 Alternating between pages of a multi-page message

3.11 Operate when located up to a minimum of 100 meters from the sign electronics housed in thesign enclosure.

3.12 The sign controller shall incorporate a watchdog timer to detect an out-of-program conditionand reset the microprocessor.


of 71 10/31/2007

3.13 The sign controller shall operate on a multi-drop communications channel, with a user-assignedand user-adjustable address from 1 to 255.

3.14 The VMS controller shall have a means of reading its drop address, either from switches, an I/Oport, or via operator input at initialization. The drop address shall be stored in non-volatilememory, and may be changed either at the controller or via the CCS. The CCS expects theVMS controller to behave in a specific manner in response to commands from the central.Listed below are the various areas which define the controller's behavior.

3.15 The sign controller shall be designed for fail-safe prevention of improper information display inthe case of malfunction. As a minimum, this shall include an automatic blanking feature thatimmediately clears the message displayed on the sign in the event of a power failure,communication failure or invalid transmission from the CCS. Automatic blanking shall alsooccur if a downloaded message does not fit the sign. A message does not fit if any of the pagesof the message do not fit on the sign or if the sign does not support an operation included in themessage.

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

3.17 The sign shall have a local control mode where the following operations may be initiated:

3.17.1 Operator selection of dimming levels

3.17.2 Operator selection of configuration parameters

3.17.3 Diagnostic routines capable of testing full sign operation

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

3.19 A switch shall be provided on the front of the VMS controller to activate local control and akeypad and menu-driven LCD display on the controller's front panel to select the operations.

3.20 The switch must be in the local position to permit entry from the keypad.

3.21 While in the local control mode, the CCS software shall continue to monitor the sign's statusand display. The VMS controller, however, shall not respond to any commands from the CCSwhile in local control mode.

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

3.22.1 Monitor the current status of the sign controller, including the status of all sensors and arepresentation of the message visible on the display face

3.22.2 Perform diagnostics testing of various system components, including pixels, powersystems and sensors.

3.22.3 Activate messages stored in memory.

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

3.23 The front panel interface shall also include:


of 71 10/31/2007

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

3.23.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 primarycommunication channel

3.23.3 Reset switch to quickly restart the controller

3.23.4 LED “Active” indicator blinks when the controller is operating

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

3.24 The baud rate, connection type, and NTCIP communication protocol shall be configurable. Thebaud rate for each port shall be set to any typical serial baud rate ranging from 1200 to 115,200.All three (3) ports shall be capable of supporting either of the following sub network profiles:NTCIP 2101 (PMPP) or NTCIP 2103 (PPP). They shall also be capable of supporting eitherNTCIP 2201 (Null) or NTCIP 2202 (Internet) profiles. Only one each of the transport and subnetwork profiles shall be active at any time on each port.

3.25 Each port’s default settings shall be set as listed below:

Port Baud Rate Connection Type NTCIP Sub network Profile NTCIP Transport ProfileAuxiliary Control 9600 Modem (External) NTCIP 2103 –PPP NTCIP 2202 –InternetCentral Control 9600 Direct NTCIP 2101 –PMPP NTCIP 2201 –NullLocal 9600 Direct NTCIP 2101 –PMPP NTCIP 2201 –Null

3.26 The VMS sign controller shall contain one (1) 10/100 Ethernet communication port. This portshall be available for optional use for communicating from the central control system to theVMS sign controller when an Ethernet network is available.

3.26.1 Communications on this port shall be NTCIP-compatible using the NTCIP 2202Internet transport profile and the NTCIP 2104 Ethernet sub network profile. This shallpermit the controller to be operated on any typical Ethernet network using the TCP/IPand UDP/IP protocols.

3.27 An EIA-232 port for plugging in a notebook computer (provided under a separate bid item) forrunning diagnostics, selecting messages, monitoring status and downloading/uploadingmessages. A minimum data rate of 19.2 kbps shall be supported through this port. A passwordmust be entered for commands from the notebook to be considered valid.

3.28 The VMS sign controller shall use multiple types of addressing when operating on NTCIPcommunication networks. The addressing shall be configurable through the front panel userinterface.

3.28.1 When operating over PMPP serial networks (NTCIP 2101), the controller’s address shall be configured in the range 1 to 255. The default address shall be 1.

3.28.2 When operating on Ethernet networks (NTCIP 2104) a static IP address and subnetshall be used. If a dial-up or direct connect serial network is configured for PPP(NTCIP 2103), then no addressing shall be required.

3.29 The VMS sign controller shall be capable of automatically informing a central control systemof the occurrence of important event or subsystem failures. This shall be handled via NTCIP“traps.” When one of these events occur, the sign controller shall create a data packet for transmission to the central controller that shall contain details about the event. Traps shall begenerated for the following events:


of 71 10/31/2007

3.29.1 Sign controller restart –Indicates that the sign controller restarted due to a powerinterruption, intentional restart, or other event.

3.29.2 Power supply failure–Indicates that a diagnostic sensor detected a power supply that isnot operating correctly.

3.29.3 Door open –Indicates that one of the doors or access panel(s) on the VMS housing orcontrol equipment cabinet has been opened. Note: This feature requires that a sensor beinstalled in the sign.

3.29.4 Over Temperature Shutdown –Indicates that the maximum safe operating temperaturehas been reached or exceeded, resulting in the blanking of the display.

4 Power DistributionAll power shall be routed through the controller cabinet which shall contain a main circuit breaker toremove all power to the controller cabinet and sign housing. A separate breaker shall be provided toprotect the sign controller and communications modem. The Contractor shall run the power cables toenergize the VMS, power the maintenance lights, power the heating and ventilating equipment and powerthe maintenance outlets as separate circuits. A UL listed breaker box sized for a minimum of six circuitsand appropriately sized shall be provided. The circuit breakers shall be approved and listed by theUnderwriters Laboratories. The operating mechanism shall be enclosed, trip free from operating handleon overload and trip indicating. Contacts shall be silver alloy enclosed in an arc quenching chamber.Properly rated equipment circuit breaker(s) shall be provided for the equipment complement shown on theplans. Breakers shall have a minimum interrupt capacity of 5000 A. Thermal magnetic breakers are notacceptable.The neutral conductor from the controller cabinet to the sign enclosure shall be 200% rated.All electrical circuits shall be permanently identified.

5 Electrical Circuitry Protection

Appropriate devices shall be installed in the sign enclosure and local control cabinets to protect the LEDVMS electronics from over-voltage situations, such as lightning strikes and power surges over the lines.Circuitry protection shall include, but not be limited to:

5.1 Overcurrent protection devices. All A.C. power circuit(s) to the LED VMS and associatedcontrol equipment enclosures shall be protected by Ground Fault Circuit Interrupting typedevices.

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

5.2.1 Maximum clamp voltage: 340 V

5.2.2 Peak Current: 20,000 amps

5.2.3 Response Time: 5 nanoseconds

5.2.4 Occurrences: 20 times at peak current

5.2.5 Maximum Series Inductance: 200 micro henries

5.2.6 Temperature Range: -40 degrees Celsius to +85 degrees Celsius

5.3 Data Line protectors to guard against circuit damage resulting from voltage surges on alldata/communication lines which enter the VMS enclosure, such as between the VMS andcabinet.


of 71 10/31/2007

5.4 VMS lightning protection shall be provided by grounding its sign gantry. Separate protectiondevices shall be installed at each sign location and shall be readily accessible for ease ofreplacement. The components shall be plug-in or screw-in units. The devices shall be clearlyand permanently labeled.

5.5 The VMS shall be electrically bonded to the support structure. This bonding shall consist of anelectrical bond wire or properly prepared electrical contact point.

6 Power Supplies

6.1 The LED display shall be operated at a low internal DC nominal voltage not exceeding 24volts.

6.2 Multiple power supplies shall be provided and employed such that the failure of any individualpower supply does not inhibit full operation of the VMS.

6.3 The quantity of power supplies shall also provide at least 50% spare capacity over that requiredto light every pixel of the LED VMS. The Contractor shall provide details of methodologyproposed for the integration of the spare capacity to Engineer for approval

6.4 All power supply voltages shall be continuously measured by the sign controller. The signcontroller shall provide these voltage readings to the central controller or notebook computerwhen the sign controller is polled.

6.5 The VMS Controller shall have redundant power supplies wired so that the failure of one powersupply shall not interrupt the operation of the controller.

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

6.7 Power supplies shall be UL listed, have an efficiency rating of 85% minimum, and shall operateover an ambient temperature range of -20 degrees Celsius to +60 degrees Celsius.

7 Sign Dimming SystemEach sign shall be provided with a system that senses the background ambient light level and providesfield-adjustable intensities (dimming). Pixel luminance levels shall be controlled both directly (throughoperator input) and automatically (based on ambient light levels obtained from the photocells).The sign dimming system shall meet the following requirements:

7.1 Consist of three (3) commercially available photo-electric sensors installed as part of the VMShousing in such a manner that does not compromise the watertight integrity of the VMShousing.

7.2 Each of the photo-electric sensors will have a 161 sq. mm (minimum) photo-sensitive area andwill be capable of being continually exposed to direct sunlight without impairment ofperformance.

7.3 The photocells will each have a 645 sq. mm (minimum) glass window area to view through theVMS housing.

7.4 The photo-electric sensors shall be placed such a way that they view the front, rear, and top ofeach sign.

7.5 The photo-electric sensors shall be mounted in a way that permits adjustment of the aimingangle and shall be placed in an easily accessible location for maintenance, as approved by theEngineer.

7.6 Luminance levels shall be stored in the VMS Controller and shall be adjustable, in a range of3% to 100%, on either:


of 71 10/31/2007

7.6.1 A continuous logarithmic basis, to match the normal human eye luminous responsecharacteristic.

7.6.2 A half incremental dimming basis, where each lower dimming level is half the previouslevel.

7.7 Dimming sign circuitry shall be provided to select a luminance level based on the ambient lightsensed by the photocells and a lookup table of intensity level vs. photocell reading.

7.8 The lookup tables shall be downloadable from the CCS. Each row shall contain a range ofphotocell readings.

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

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

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

7.12 Continuous current drive shall be used at the maximum brightness level and at all lower levelsof brightness.

7.13 The current used for maximum brightness shall not exceed the current used to achieve the ratedMTBF. The current used for maximum brightness shall be indicated as part of the shopdrawing submittal.

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

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

7.16 A complete schematic of the LED display power, driver and dimming circuits shall be providedfor approval by the Engineer.

8 Central Control of the VMS

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

8.1 The VMS controller shall have a means of reading its drop address, either from switches, an I/Oport, or via operator input at initialization. The drop address shall be stored in non-volatilememory, and may be changed only at the controller.

8.2 For message creation, the VMS, VMS sign controller, and VMS control software shall supportthe storage and use of a minimum of eight (8) alphanumeric character font files. Each font fileshall include the following characters:

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

8.2.2 Decimal digits “0” through “9”

8.2.3 A blank or space

8.2.4 Eight (8) directional arrows


of 71 10/31/2007

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

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

8.3 The following character font files shall be supplied with the VMS, at a minimum:

8.3.1 7x4 Single Stroke –a typical font is seven (7) pixel rows high by four (4) pixelcolumns wide, has a single-pixel stroke width, and provides one pixel column of inter-character spacing.

8.3.2 7x6 Double Stroke–a typical font is seven (7) pixel rows high by six (6) pixel columnswide, has a two-pixel stroke width, and provides one pixel column of inter-characterspacing.

8.3.3 7x5 Single Stroke–a typical font is seven (7) pixel rows high by five (5) pixel columnswide, has a single-pixel stroke width, and provides one pixel column of inter-characterspacing.

8.3.4 11x7 Double Stroke –a typical font is eleven (11) pixel rows high by seven (7) pixelcolumns wide, has a two-pixel stroke width, and provides two pixel columns of inter-character spacing.

Communications Protocol8.4 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 ofthis letting, including any and all Approved or Recommended Amendments to these standardsas of the letting date. It is the ultimate responsibility of the sign manufacturer to monitorNTCIP activities to discover any more recent documents.

9 NTCIP9.1 Variable Message Sign assemblies shall be compliant with the latest version of the NTCIP

Standards, as defined by AASHTO, ITE, and NEMA.9.2 SUBNETWORK PROFILES

9.2.1 Each serial or modem port on each NTCIP device shall be configurable to support bothNTCIP 2101 and NTCIP 2103. Only one of these profiles shall be active at any giventime. Serial ports shall support external dial-up, leased line, radio, cellular and fiberoptic modems.

9.2.2 Each Ethernet port on the NTCIP device shall comply with NTCIP 2104.

9.2.3 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 theNTCIP device. All response datagram packets shall use the same transport profile usedin the request. The NTCIP device shall be configurable to allow a field technician toactivate the desired subnet profile and shall provide a visual indication of the currentlyselected subnet profile.

9.3 TRANSPORT PROFILES

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

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

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


of 71 10/31/2007

Each NTCIP device shall support the receipt of datagrams conforming to any of thesupported transport profiles at any time.

9.4 APPLICATION PROFILES

9.4.1 Each NTCIP device shall comply with NTCIP 2301 and shall meet the requirementsfor Conformance Level 1.

9.4.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. EachNTCIP device shall support the receipt of application data packets at any time allowedby the subject standards.

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

9.5 Each NTCIP device shall support all mandatory objects in all optional conformance groups thatare required herein. All optional objects listed in these specifications as mandatory, shall besupported.

9.6 CONFORMANCE STATEMENTSConformance Group Reference Conformance Requirement

Configuration NTCIP 1201:1996 MandatoryTime Management NTCIP 1201:1996 MandatoryTimebase Event Schedule NTCIP 1201:1996 MandatoryReport NTCIP 1201:1996 MandatorySTMF NTCIP 1201:1996 OptionalPMPP NTCIP 1201:1996 MandatorySign Configuration NTCIP 1203:1997 MandatoryGUI Appearance NTCIP 1203:1997 OptionalFont Configuration NTCIP 1203:1997 MandatoryVMS Sign Configuration NTCIP 1203:1997 MandatoryMULTI Configuration NTCIP 1203:1997 MandatoryMessage Table NTCIP 1203:1997 MandatorySign Control NTCIP 1203:1997 MandatoryDefault Message Control NTCIP 1203:1997 OptionalPixel Service Control NTCIP 1203:1997 OptionalMULTI Error Control NTCIP 1203:1997 MandatoryIllumination/Brightness Control NTCIP 1203:1997 MandatoryScheduling NTCIP 1203:1997 MandatoryAuxiliary I/O NTCIP 1203:1997 MandatorySign Status NTCIP 1203:1997 MandatoryStatus Error NTCIP 1203:1997 MandatoryPixel Error Status NTCIP 1203:1997 MandatoryFan Error Status NTCIP 1203:1997 MandatoryPower Status NTCIP 1203:1997 MandatoryTemperature Status NTCIP 1203:1997 Mandatory

9.7 SIGN CONFIGURATION CONFORMANCE GROUP


of 71 10/31/2007

MIB Object Or Table Name NTCIPReference

NYSDOTSpecification

Reference

ExpectedValue

2.2.1.1.1.2 dmsSignType NTCIP 1203:1997 1 62.2.1.1.1.8 dmsBeaconType NTCIP 1203:1997 - 2

9.8 FONT CONFIGURATION CONFORMANCE GROUP


NYSDOTSpecification

Reference

ExpectedValue

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

9.9 VMS SIGN CONFIGURATION CONFORMANCE GROUP


NYSDOTSpecification

Reference

ExpectedValue

2.3.1.1.1.1 vmsCharacterHeightPixels NTCIP 1203:1997 1 02.3.1.1.1.2 vmsCharacterWidthPixels NTCIP 1203:1997 1 02.3.1.1.1.3 vmsSignHeightPixels NTCIP 1203:1997 1 27..655352.3.1.1.1.4 vmsSignWidthPixels NTCIP 1203:1997 1 120..655352.3.1.1.1.5 vmsHorizontalPitch NTCIP 1203:1997 1.4 0..682.3.1.1.1.6 vmsVerticalPitch NTCIP 1203:1997 1.4 0..68

9.10 MULTI CONFIGURATION CONFORMANCE GROUP


NYSDOTSpecification

Reference

ExpectedValue

2.5.1.1.1.1 defaultBackgroundColor NTCIP 1203:1997 2.37 02.5.1.1.1.2 defaultForegroundColor NTCIP 1203:1997 1.9,1.19 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 9.3 1..2552.5.1.1.1.6 defaultJustificationLine NTCIP 1203:1997 3.8 1..52.5.1.1.1.7 defaultJustificationPage NTCIP 1203:1997 3.8 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

9.11 MESSAGE TABLE CONFORMANCE GROUP


NYSDOTSpecification

Reference

ExpectedValue

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


of 71 10/31/2007

2.6.1.1.1.4 dmsFreeChangeableMemory NTCIP 1203:1997 - 0..42949672952.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..42949672952.6.1.1.1.8 dmsMessageTable NTCIP 1203:1997 Sequence2.6.1.1.2 dmsValidateMessageError NTCIP 1203:1997 - 1..5

9.12 SIGN CONTROL CONFORMANCE GROUP


NYSDOTSpecification

Reference

ExpectedValue

2.7.1.1.1.1 dmsControlMode NTCIP 1203:1997 3 1..62.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 - Code2.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.16 dmsMemoryMgmt NTCIP 1203:1997 - 1..42.7.1.1.1.17 dmsActivateMsgError NTCIP 1203:1997 - 1..9

9.13 MULTI ERROR CONFORMANCE GROUP


NYSDOTSpecification

Reference

ExpectedValue

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 dmsMultiOtherErrorDescription NTCIP 1203:1997 - 0..50

9.14 ILLUMINATION/BRIGHTNESS CONFORMANCE GROUP


NYSDOTSpecification

Reference

ExpectedValue

2.8.1.1.1.1 dmsIllumControl NTCIP 1203:1997 8.1 1..42.8.1.1.1.2 dmsIllumMaxPhotocellLevel NTCIP 1203:1997 8.6 0..655352.8.1.1.1.3 dmsIllumPhotocellLevelStatus NTCIP 1203:1997 8.7 0..655352.8.1.1.1.4 dmsIllumNumBrightLevels NTCIP 1203:1997 8.6 0..2552.8.1.1.1.5 dmsIllumBrightLevelStatus NTCIP 1203:1997 8.6 0..2552.8.1.1.1.6 dmsIllumManLevel NTCIP 1203:1997 8.6 0..2552.8.1.1.1.7 dmsIllumBrightnessValues NTCIP 1203:1997 8.7 Octet String2.8.1.1.1.8 dmsIllumBrightnessValuesError NTCIP 1203:1997 - 1..62.8.1.1.1.9 dmsIllumLightOutputStatus NTCIP 1203:1997 8.7 0.65535

9.15 SCHEDULING CONFORMANCE GROUP


NYSDOTSpecification

SectionReference

ExpectedValue


of 71 10/31/2007

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

9.16 SIGN STATUS CONFORMANCE GROUP


NYSDOTSpecification

SectionReference

ExpectedValue

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 3.10 Counter2.11.1.1.1.6 dmsStatDoorOpen NTCIP 1203:1997 2.17

3.30.30..255

9.17 STATUS ERROR SUBCONFORMANCE GROUP


NYSDOTSpecification

Reference

ExpectedValue

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

9.18 PIXEL ERROR STATUS SUBCONFORMANCE GROUP


NYSDOTSpecification

Reference

ExpectedValue

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 3.22.2 1..49.19

9.20 MULTI Tags

9.20.1 Each NTCIP device shall support the following message formatting MULTI tags. Themanufacturer may choose to support additional standard or manufacturer-specificMULTI tags.

MULTITag

Description

f1 Field 1-time (12 hr)

f2 Field 1-time (24 hr)

f8 Field 8- day of month

f9 Field 9-month


of 71 10/31/2007

MULTITag

Description

f10 Field 10-2 digit year

f11 Field 11-4 digit year

fl (and /fl) Flashing text on a line-by-line basis with flash rates controllable in 0.1-secondincrements.

Fo Font

jl2 Justification- line-left

jl3 Justification- line-center

jl4 Justification- line- right

jp2 Justification- page- top

jp3 Justification- page- middle

jp4 Justification- page- bottom

mv Moving text

nl New line

np New page up to 5 instances in a message (i.e. up to 6 pages/frame in a messagecounting first page)

pt Page times controllable in 0.1-second increments9.21 Documentation

9.21.1 NTCIP documentation shall be provided on a CD-ROM and shall contain ASCIIversions of the following Management Information Base (MIB) files in AbstractSyntax Notation 1 (ASN.1) format:9.21.1.1 The relevant version of each official standard MIB modules referenced by

the device functionality.9.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 officialstandard MIB Module with the supported range indicated in ASN.1 format inthe SYNTAX and/or DESCRIPTION fields of the associated OBJECTTYPE macro. The filename of this file shall be identical to the standard MIBModule except that it will have the extension “.man”.

9.21.1.3 A MIB module in ASN.1 format containing any and all manufacturerspecific objects supported by the device with accurate and meaningfulDESCRIPTION fields and supported ranges indicated in the SYNTAX fieldof the OBJECT-TYPE macros.

9.21.1.4 A MIB containing any other objects supported by the device9.22 Acceptance Testing

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


of 71 10/31/2007

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

9.23 Interpretation Resolution9.23.1 If the Engineer or VMS manufacturer discovers an ambiguous statement in the

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

CONSTRUCTION DETAILS

10 Installation

The Contractor shall install the VMS on sign structures described under other items. This item shallinclude all sign modules, sign housing, VMS controller, Central Control System Software, fittings and allcabling in the sign, VMS controller, and between the sign and controller required for a fully operationalVMS.

10.1 The permanent VMS shall be mounted to support structures as shown on the Drawings.Construction methods and details shall be in accordance with §644-3 of the NYSDOT StandardSpecifications as modified under this Contract. All mounting fasteners and hardware shall bemade of stainless steel.

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

10.3 The Contractor shall make all power connections to the VMS assembly. The neutral bus shallbe isolated from the cabinet and equipment ground. The Contractor shall ground the sign inaccordance with §680-3.12, Grounding. A direct ground wire shall be installed between thepower distribution panel within the sign and the nearest ground rod. Grounding through thesign structure is not acceptable.

10.4 The Contractor shall connect the VMS controller and the modem, either fiber optic or wirelessmodem. Where a fiber optic modem is specified, the connection to the fiber optic cable plantshall be through the fiber optic patch panel provided under a separate item of the contractdocuments.

10.5 The fiber shall be neatly racked in the VMS enclosure or controller cabinet complying with theminimum bend radius for the cable.

10.6 All wire shall be cut to the appropriate length prior to installation. All cabling shall be neatlyrouted and tied back so as not to interfere with access to other cabling or equipment ormaintenance of the sign. All cabling shall be permanently identified as to its termination point.

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

10.8 Preconnectorized fiber shall be terminated in the patch panel and pre-terminated pig tails shallbe fusion spliced to the drop cable fiber. Slack fiber shall be stored in the patch panel.

10.9 After installation of all cables into the sign enclosure, each of the conduit entries shall be sealedwith duct seal or an approved equivalent, to prevent water or rodent ingress.


of 71 10/31/2007

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

Test Software

10.11 The Contractor shall provide test software that will run on a notebook computer under theWindows operating system to emulate the central software. This software shall permitdownloading and uploading of the commands and responses through the RS-232 port or theethernet port of the VMS controller. Three copies of the test software on disk or CD-ROM shallbe delivered to the Engineer.

11 Documentation

Sign Control Parameters11.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 thisdocument. These shall include but not be limited to the following:11.1.1 Range and definition of photocell readings.11.1.2 Diagnostic tests.11.1.3 Error and status bits.11.1.4 Manufacturer specific NTCIP data objects and their associated range values.

Shop Drawings

11.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 forapproval prior to ordering the piece of equipment.

11.3 The Contractor shall develop and deliver calculations, approved by a New York State LicensedProfessional Engineer, demonstrating the VMS enclosure’s ability to withstand the design loads.

11.4 Included in the shop drawings shall be parts lists, schematics, wiring lists, mechanical detailsincluding material, dimensions, and finish, and assembly drawings.

11.5 The Contractor shall develop and deliver shop drawings approved by a licensed New YorkState Professional Engineer which illustrates, in detail, how to mount and connect the VMSenclosure to the structure shown in the plans.

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

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

11.8 Incomplete submissions shall be returned for re-submission.

12 Manuals

12.1 Manuals that detail the operation of the system shall be furnished as part of the VMS System.

12.2 User Manuals shall be provided for each system component.

12.2.1 The User Manuals shall fully identify the system's, or the component's, features andfunctions and give detailed step-by-step instructions on how to operate and adjust thesystem or component and how to respond to system or component failures.


of 71 10/31/2007

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

12.3.1 Detailed description of normal system operation.

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

12.3.3 Error and alarm handling procedures, including recovery from communicationsfailures.

12.3.4 System start-up and shutdown procedures.

12.3.5 Detailed procedures on how to create, save, transmit and display messages, includingall graphic features, back-up and restore message libraries, sign configurations, errorand event logs.

12.3.6 The sections covering system administration features such as password management,setting access levels, installing, backing-up and restoring the sign control software shallbe contained in a separate "System Administration Operations Manual."

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

12.4.1 Maintenance Manuals shall provide diagnostic routines for trouble shooting the systemfrom the system computer and from each sign location. The manuals shall containtheory of operation, specifications, installation instructions, mechanical details, detailedalignment procedures, schematic drawings, photographs or drawings detailingcomponent layouts, parts lists, including manufacturer's part numbers, and troubleshooting procedures for repair/replacement of all component parts, including printedcircuit board replacement. The Maintenance Manuals shall include, but not be limitedto:

12.4.1.1 All the requirements for the Operations manuals.

12.4.1.2 Detailed description of procedures for modifying the LED VMS, signcontroller and sign control software configuration settings.

12.4.1.3 Description of operating procedures and troubleshooting procedures foreach subsystem. This shall include step-by-step field and benchtroubleshooting procedures to isolate and repair faults, as well as normalwaveforms and test voltages.

12.4.1.4 System message and configuration editing back-up and restore procedures,including procedures for changing any messages stored in non-volatilememory.

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

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


of 71 10/31/2007

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

12.4.1.8 Complete nomenclature and commercial number of replacement parts,including current prices, listing of spare parts initially provided, and asecond source of supply where applicable, cross-referenced as to componentdesignation.

12.4.1.9 Each manufacturer's product data sheet annotated to clearly identify productor part.

12.4.1.10 Each manufacturer's printed operating and maintenance instructions.

12.4.1.11 List of recommended cleaning agents, maintenance procedures andschedules.

12.4.1.12 List of recommended test equipment including manufacturer's name,address, and model number.

12.4.2 Three (3) copies of each manual shall be furnished with each VMS. These manuals arein addition to the manuals provided during training courses. All manuals of each typeshall be identical and shall be originals, not reproduced copies.

12.4.3 Options identified in a manual, which are not furnished with the VMS System shall bemarked "NOT USED."

12.4.4 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 thecatalog and with loose-leaf hole reinforcements, except for those sheets where the fulllength of the fastener-edge is, in an approved manner, either reinforced or made of ahigh-strength material. Loose-leaf holes shall not be punched through the body ofdrawings or other sheets. They shall be punched in the margin only, and each drawingand other large sheet shall have the margin trimmed and the sheet properly folded sothat 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 andspine of each binder. The labels shall contain the title of the manual, the manualnumber, the Contract title, and the Contract number.

12.5 For all custom application software necessary to operate the VMS, the Contractor shall provideNYSDOT with the software source code, and compiler necessary to compile it. The Contractorshall also demonstrate the compiling, linking, and loading of the source code as part of this test.

13 Testing

Design Approval Tests

13.1 The following tests shall be performed as part of the design approval test in addition to thosespecified in the General Requirements. The Design Approval Test shall be performed on acomplete VMS assembly. While performing these tests a test set shall be used to issuecommands to the sign controller to verify that the sign remains operational throughout the test.

13.2 Power variation: Test the sign with the line voltage at the maximum, minimum and nominalspecified values. Using a power interruption meter, at each of these voltages interrupt the


of 71 10/31/2007

power for 0.1 sec five times. Repeat for a 0.5 second interruption and for a 1 secondinterruption.

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

13.3.1 Amplitude: 300 volts +5 percent, positive and negative polarity

13.3.2 Peak power: 5000 watts

13.3.3 Repetition: One pulse every other cycle moving uniformly over the full wave inorder to sweep once every 3 seconds across 360 degrees of linecycle.

13.3.4 Pulse rise time: 500 ns.

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

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

13.5.1 The equipment shall be stabilized at 0 degrees Celsius. After stabilization at thistemperature, the equipment shall be operated without degradation for two (2) hours.

13.5.2 The equipment shall be stabilized at 62 degrees Celsius. After stabilization, theequipment shall be operated without degradation for two (2) hours.

13.5.3 The equipment shall be subjected to temperature shock of 17 degrees Celsius per hour,during which time the relative humidity shall not exceed 95%. The equipment shall beoperated without failure during and after the temperature shock.

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

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

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

13.7.1.1 Amplitude: 2.0 mm "Double Amplitude" (peak to peak)

13.7.1.2 Linear Acceleration (g's): 5 maximum

13.7.1.3 Linear Velocity: approximately 190 mm/s

13.7.1.4 Frequency: 40 Hz

13.7.1.5 Duration: five (5) minute dwell in each axis

13.8 If the equipment fails the design approval test, the design fault shall be corrected and the entiredesign approval test shall be repeated. All deliverable equipment shall be modified, without


of 71 10/31/2007

additional cost to the State Department of Transportation, to include design changes required topass the design approval tests.

Factory Demonstration Tests

13.9 Following Design Acceptance Testing and prior to shipping of any signs, the Contractor shallperform a factory demonstration test on each sign. Factory Demonstration Tests shall test thefull functionality of a sign, controller, central control and maintenance software andcommunications between them.

13.10 Using a notebook computer loaded with test software provided by the sign manufacturerdemonstrate the following with the computer connected to the input (remote) port of thecontroller:

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

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

13.10.3 With the fiber optic communications interface installed, operate the sign via asimulated communications network.

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

13.10.5 Demonstrate compliance with the NTCIP specific standards to be implemented,applicable conformance groups, applicable data objects and their associated rangevalues that are pertinent to the implementation of this specification. Test cases areattached as an appendix to this specification.

13.10.6 Water Test: A water spray test shall be performed to demonstrate that the enclosuremeets the requirements of the NEMA 3R rating for the VMS housing. At thecompletion of the test, verify that the inside of the housing is dry.

13.10.7 If the VMS fails the factory demonstration test, the fault(s) shall be corrected and theentire factory demonstration test shall be repeated. All deliverable equipment shall bemodified, without additional cost to the NYSDOT, to include any changes required tosatisfactorily complete the factory demonstration tests.

Pre-Installation Tests

13.11 Prior to erection, the Contractor shall perform a pre-installation test at its facility. Thistest shall include a visual inspection of the sign to verify that the sign has not beendamaged in shipment and a demonstration of operation of the sign using the testsoftware.

Stand Alone Tests

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

13.13 After installation and prior to integration of the VMS into the system, the Contractor shallperform an operational stand-alone test in the field for each unit. The test, as a minimum, shalldemonstrate operation of the VMS sign using the test software running on a notebook computer(provided under a separate bid item).


of 71 10/31/2007

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

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

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

13.14.3 With the notebook computer loaded with the test software provided by the signmanufacturer, demonstrate operation through the local port of the sign controller.

13.15 The sign shall be operated for thirty-days in a test mode that shall continuously exercise thedisplay. At the end of the thirty-day period, operation of the sign using the test software shallagain be demonstrated. If a failure occurs, the sign shall be repaired and the thirty-day testrepeated. A test pattern, approved by the Engineer, shall be displayed during the test. This testpattern shall exercise all pixels.

Remote Site Verification Test

13.16 The Contractor shall verify the operations of the sign by operating it from the control center viathe communications network using each of the remote communication ports.

System Acceptance Tests

13.17 Following the satisfactory completion of the Site Verification Tests, a system acceptance testshall be performed. Testing shall meet the requirements of the Contract documents.

14 Training

14.1 The Contractor shall provide training courses to NYSDOT personnel as specified in the SpecialNotes section of this package.

15 Spare Parts

15.1 The following spare parts identified in the table below shall be provided by the Contractor andhanded over to the Engineer after completion of system acceptance, for use by maintenancepersonnel.

No. Of Signs in Contract 1 to 5 >5Item Description Quantity of Spares Quantity of Spares

VMS Controller 2 Minimum of 2 or 20% ofinstalled number of signs,whichever is greater.

Display Modules 20 of each type Minimum of 20 of each type or20% of installed number of signs,whichever is greater.

Driver Boards 20 of each type Minimum of 20 of each type or20% of installed number of signs,whichever is greater.

Diagnostic Boards 20 of each type Minimum of 20 of each type or20% of installed number of signs,whichever is greater.

Power Supplies 4 of each type Minimum of 4 of each type or20% of installed number of signs,


of 71 10/31/2007

whichever is greater.Photo-Electric Sensors 4 of each type Minimum of 4 of each type or

20% of installed number of signs,whichever is greater.

LEDs 5,000 10,000

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

15.3 All spare parts shall be certified by the manufacturer that they are suitable for use on the signsprovided 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.

15.4 The Engineer shall reserve the right to witness any such testing of spare parts.

METHOD OF MEASUREMENT

16 Variable Message Sign Assembly, LED Full Matrix, will be measured as a unit, completely installed,successfully tested, and operational.

BASIS OF PAYMENT

17 The unit price for each VMS Assembly shall include the cost of furnishing all labor, materials andequipment necessary to complete the work. All miscellaneous hardware and software, required for theinstallation and testing of the unit shall be included under this item. Payment for the wireless modemor Fiber Optic Data Transceiver - Multidrop will be made under their respective items. Payment forall documentation, testing and test equipment and software shall be included under this item.17.1 Progress payment will be made as follows:

17.1.1 Ten percent of the bid price for the sign will be paid upon approval of the shopdrawings.

17.1.2 Forty percent of the bid price for each item will be paid upon satisfactory completion ofinstallation of the assembly at the job site.

17.1.3 Forty percent of the bid price for each item will be paid upon satisfactory completion ofthe operational stand-alone test.

17.1.4 Ten percent of the bid price will be paid upon system acceptance.


APPENDIX AA: NTCIP TEST PROCEDURES FOR VMS

of 71 10/31/2007

NTCIP Test Procedures for Variable Message SignAssemblies

March 20, 2007

New York State Department ofTransportation



of 71 10/31/2007

Revision ListDocument:

Date Author CheckedBy

Notes



of 71 10/31/2007

Table of Contents

1. Introduction –Purpose of Document ............................................34

1.1 Reference Documentation........................................................................................................................... 34

1.2 Field Device Test Environment .................................................................................................................. 34

2. Test Cases.......................................................................................36

2.1 TC001–Sign Interrogation ........................................................................................................................ 36

2.2 TC002–Download and Display a Changeable Message ........................................................................... 36

2.3 TC003–Font Configuration....................................................................................................................... 38

2.4 TC004–Display all Permanent Messages.................................................................................................. 39

2.5 TC005–Download and Display all Changeable Messages........................................................................ 41

2.6 TC006–MULTI Tags ................................................................................................................................ 42

2.7 TC007–Message Errors ............................................................................................................................ 43

2.8 TC008–Activate Message ......................................................................................................................... 46

2.9 TC009–Default MULTI Message Attributes ............................................................................................ 47

2.10 TC010–Default Messages ......................................................................................................................... 48

2.11 TC011–Time............................................................................................................................................. 50

2.12 TC012–Scheduling ................................................................................................................................... 52

2.13 TC013–Security ........................................................................................................................................ 55

2.14 TC014–Pixel Failures ............................................................................................................................... 58

2.15 TC015–Power Supply Error Status........................................................................................................... 60

2.16 TC016–Temperature and Status................................................................................................................ 62

2.17 TC017–Field Display................................................................................................................................ 64

2.18 TC018–Reports......................................................................................................................................... 65

2.19 TC019–Brightness Control ....................................................................................................................... 67



of 71 10/31/2007

List of FiguresFigure 1-1 Test Environment for Variable Message Sign........................................................................................... 35



of 71 10/31/2007

1 Introduction –Purpose of DocumentThe National Transportation Communications for ITS Protocols (NTCIP) standards are intended to promote thedevelopment of interoperable equipment within the Intelligent Transportation Systems (ITS) industry. Anycomponent that does not fully follow the rules defined by the NTCIP standards will inhibit or precludeinteroperability from being realized. As a result, the industry needs a well-defined and consistent way to testequipment that claims conformance to the NTCIP standards. This document is intended to be used as an appendix toSpecial Specifications for Full Matrix, LED Based, Variable Message Signs without regard to any one SpecialSpecification.

1.1 Reference DocumentationSome of the documents reviewed during the development of this test procedure are listed below:

ITEM 680.XX04M - Full Matrix, LED Based, Variable Message Sign

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

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

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

1.2 Field Device Test EnvironmentTesting 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 requiringelectrical 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 computershall also be equipped with a DB9 serial port for RS-232 communications to the sign.

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

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 thesame test shall be run on each sign.

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



of 71 10/31/2007

Figure 1-1 Test Environment for Variable Message Sign



of 71 10/31/2007

2 Test Cases

2.1 TC001 –Sign Interrogation

Title: Sign Interrogation

Description: The purpose of this test is to verify that the sign reports the applicable parametersrequired for the Central System to know the sign size, configuration, manufacturerand version.

Test Case:

TC001

Pass/FailCriteria:

The DUT shall pass every step described in this test case in order to pass 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 4through 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 equals1.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 ofthe module.

Pass / Fail

10. Get moduleModel.N Pass / Fail

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

Pass / Fail

12. Get moduleVersion.N Pass / Fail

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

Pass / Fail

14. Get moduleType.N Pass / Fail

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 signtype: 6 (vms full matrix)

Pass / Fail



of 71 10/31/2007

19. Get dmsBeaconType.0 Pass / Fail

20. Verify that the Response Value for dmsBeaconType.0 indicates the correctBeacon Type: 2 (None)

Pass / Fail

21. Get dmsSignAccess.0 Pass / Fail

22. Verify that the Response Value for dmsSignAccess.0 indicates the correct SignAccess: 2 (walk in access)

Pass / Fail

23. Get dmsSignHeight.0 Pass / Fail

24. Verify that the Response Value for dmsSignHeight.0 indicates the correct SignHeight 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 actualHorizontal Border in millimeters.

Pass / Fail

29. Get dmsVerticalBorder.0 Pass / Fail

30. Verify that the Response Value for dmsVerticalBorder.0 indicates the actualVertical 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

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 thecorrect Character Height: 0 (full matrix)

Pass / Fail

37. Get vmsCharacterWidthPixels.0 Pass / Fail

38. Verify that the Response Value for vmsCharacterWidthPixels.0 indicates thecorrect Character Width measured in pixels: 0 (full matrix)

Pass / Fail

39. Get vmsSignHeightPixels.0 Pass / Fail

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

Pass / Fail

41. Get vmsSignWidthPixels.0 Pass / Fail

42. Verify that the Response Value for vmsSignWidthPixels.0 indicates the correctSign Width measured in pixels: 120

Pass / Fail

43. Get vmsHorizontalPitch.0 Pass / Fail

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

Pass / Fail



of 71 10/31/2007

45. Get vmsVerticalPitch.0 Pass / Fail

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

Pass / Fail

Test CaseResult:

Pass / Fail

Test CaseNotes:

2.2 TC002 –Download and Display a Changeable Message

Title: Download and Display a Changeable Message

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

Test Case:

TC002

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


1. Download Changeable Message 1. Pass / Fail

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

3. Set dmsMessageMultiString.3.1 toABCDEFGHIJKLMNOPQRS[nl]TUVWXYZ1234567890#&*[nl]+/()[]<>abcdefghijkl

Pass / Fail

4. Set dmsMessageOwner.3.1 to Customer Pass / Fail

5. Set dmsMessageBeacon.3.1 to 0 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



of 71 10/31/2007

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. Durationii. Priorityiii. Memory Typeiv. Message Numberv. CRCvi. IP Address

Pass / Fail

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

Test CaseNotes:

2.3 TC003 –Font Configuration



Test Case:

TC002






Pass / Fail



of 71 10/31/2007



















Pass / Fail







Test CaseResult:

Test CaseNotes:



of 71 10/31/2007

2.4 TC004 –Display all Permanent Messages



Test Case:

TC002






Pass / Fail


















i. Durationii. Priorityiii. Memory Type

Pass / Fail



of 71 10/31/2007

iv. Message Numberv. CRCvi. IP Address







Test CaseResult:

Test CaseNotes:

2.5 TC005 –Download and Display all Changeable Messages



Test Case:

TC002






Pass / Fail









of 71 10/31/2007













Pass / Fail







Test CaseResult:

Test CaseNotes:

2.6 TC006 –MULTI Tags

Test Case: Title: MULTI Tags



of 71 10/31/2007

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

TC006

Pass/FailCriteria:



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 (amber). 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 3 (center). Pass / Fail

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

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 thefollowing messages to Changeable Message 1, and verify that the message iscorrectly displayed:

13. a. Message: TEST[nl]MESSAGE[nl]PAGEONE[np]PAGE TWO[nl]TEST[nl]MESSAGE.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. Message: TEST[nl]MESSAGE[nl]PAGEONE[np]PAGE TWO[nl]TEST[nl]MESSAGE[np]PAGE[nl]THREE[nl]TESTi. Description: Three pages, 2 second duration per page, noflashing, center justified.

Pass / Fail


17. c. Message: [pt20o10]TEST[nl]MESSAGE[nl]PAGEONE[np]PAGE TWO[nl]TEST[nl]MESSAGE[np]PAGE[nl]THREE[nl]TESTi. Description: Three pages, 2 second on time, one secondoff time per page, no flashing, center justified.

Pass / Fail


19. d. Message: [jl2][pt20o10]TEST[nl]MESSAGE[nl]PAGE ONE[np]PAGE TWO[nl]TEST[nl]MESSAGE[np]PAGE [nl]THREE[nl]TESTi. Description: Three pages, 2 second on time, one secondoff time per page, no flashing, left justified.

Pass / Fail



of 71 10/31/2007


21. e. Message: [jl4][pt20o10]TEST[nl]MESSAGE[nl]PAGE ONE[np]PAGE TWO[nl]TEST[nl] MESSAGE[np]PAGE [nl]THREE[nl]TESTi. Description: Three pages, 2 second on time, one secondoff time per page, no flashing, right justified.

Pass / Fail


23. f. Message: [jp2][pt20o10]TEST[np]MESSAGEi. Description: Two pages, 2 second on time, one second offtime per page, no flashing, center justified, top justified.

Pass / Fail


25. g. Message: [jp4][pt20o10]TEST[np]MESSAGEi. Description: Two pages, 2 second on time, one second offtime per page, no flashing, center justified, bottomjustified.

Pass / Fail


27. h. Message: TEST[nl]MESSAGE[nl]PAGE ONE[np][fl]PAGE TWO[/fl][nl]TEST[nl]MESSAGEi. Description: Two pages, 2 second on time per page, top

line second page flashing .4 sec on, .4 sec off, centerjustified.

Pass / Fail


29. i. Message: TEST[nl]MESSAGE[nl]PAGE ONE[np][fl]PAGE TWO[/fl][nl][flt2o2]TEST[/fl][nl]MESSAGEi. Description: Two pages, 2 second on time per page, top

line second page flashing .4 sec on, .4 sec off, second linesecond page flashing twice as fast as first line, centerjustified.

Pass / Fail


31. j. Message: [fo1]TEST[nl]MESSAGE[nl]PAGE ONEnp][fl]PAGE TWO[/fl][nl][flt2o2][fo2]TEST[/fl][nl][fo1]MESSAGEi. Description: Two pages, 2 second on time per page, top

line second page flashing .4 sec on, .4 sec off, second linesecond page flashing twice as fast as first line, centerjustified. Second line on second page in Font 2.

Pass / Fail


33. k. Message: [fo1]TEST[nl]MESSAGE[nl][mvcr32,1,3,PAGE ONE]np][mvcr32,1,3,PAGE TWO][nl]TEST[nl]MESSAGEi. Description: Two pages, Last line of first page movingcircularly to the right over 32 pixels at a rate of 1 pixel per 3 tenths of aseconds. First line of second page moving circularly to the right over 32pixels at a rate of 1 pixel per 3 tenths of a seconds.

Pass / Fail


35. l. Message: [fo1]TEST[nl]MESSAGE[nl][mvcl32,1,3,PAGE ONE]np][mvcl32,1,3,PAGE TWO][nl]TEST[nl]MESSAGEi. Description: Two pages, Last line of first page moving

Pass / Fail



of 71 10/31/2007

circularly to the left over 32 pixels at a rate of 1 pixel per 3 tenths of aseconds. First line of second page moving circularly to the left over 32pixels at a rate of 1 pixel per 3 tenths of a seconds.


Test CaseResult:

Pass / Fail

Test CaseNotes:

2.7 TC007 –Message Errors

Title: Message Errors

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

Test Case:

TC007

Pass/FailCriteria:



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

2. Message: TEST[nl]MESSAGE[nl]BIG MESSAGE TOO LONG TO FIT Thirdline 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 31 (approximately)

Pass / Fail

5. Message: TEST[nl]MESSAGE[nl]LINE 3[nl]LINE 4Four line message too big to fit on the sign.

Pass / Fail




of 71 10/31/2007

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



dmsMultiSyntaxError.0 5 (textTooBig)


Pass / Fail

8. Message: TEST[nl]MESSAGE[nlLINE 3Unsupported tag (missing closing “]”).

Pass / Fail


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



dmsMultiSyntaxError.0 3 (unsupportedTag) or 4

(unsupportedTagValue)


Pass / Fail

Test CaseResult:

Pass / Fail

Test CaseNotes:

2.8 TC008 –Activate Message

Title: Activate Message

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

Test Case:

TC008

Pass/FailCriteria:



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

a. Message: HIGH[nl]PRIORITY[nl]MESSAGEb. Runtime Priority: 100c. Activate Priority: 255

Pass / Fail



of 71 10/31/2007

d. Beacons 1e. Pixel Service 0

2. Verify that the message is correctly displayed, and the beacons are on. Pass / Fail

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

a. Message: LOW[nl]PRIORITY[nl]MESSAGEb. Runtime Priority: 100c. Activate Priority: 99d. Beacons 0e. Pixel Service 0

Pass / Fail

4. Verify that the message is correctly downloaded, but NOT displayed, and thebeacons continue to flash.

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 4F 01 02 03 04

Pass / Fail

7. Verify that the low priority message is now displayed, and the beacons are off. Pass / Fail

8. Get dmsMessageCRC.3.1. Pass / Fail

9. Verify that the Response Value for dmsMessageCRC.3.1 is 24 4F hex (integer9295), 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 valueof 7 (messageCRC)

Pass / Fail

14. Verify that the Low Priority Message is NOT displayed, and the beacons are off. Pass / Fail

Test CaseResult:

Pass / Fail

Test CaseNotes:

2.9 TC009 –Default MULTI Message Attributes

Test Case: Title: Default MULTI Message Attributes



of 71 10/31/2007

Description: The purpose of this test is to verify that the sign will respond correctly to the defaultpage time and justification parameters.

TC009

Pass/FailCriteria:



1. Get defaultJustificationLine.0 Pass / Fail

2. Record the Response Value for defaultJustificationLine.0

3. Get defaultJustificationPage.0 Pass / Fail

4. Record the Response Value for defaultJustificationPage.0

5. Get defaultPageOnTime.0 Pass / Fail

6. Record the Response Value for defaultPageOnTime.0

7. Get defaultPageOffTime.0 Pass / Fail

8. Record the Response Value for defaultPageOffTime.0 Pass / Fail

9 Get defaultFlashOn.0 Pass / Fail

10. Record the Response Value for defaultFlashOn.0

11. Get defaultFlashOff.0 Pass / Fail

12. Record the Response Value for defaultFlashOff.0

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

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

15. Set defaultPageOnTime.0 to 20 (2 seconds). Pass / Fail

16. Set defaultPageOffTime.0 to 0 (0 seconds). Pass / Fail



19. Use the procedure from Test Case TC002 to download and display the followingto Changeable Message 1.

a. Message: TEST[np]MESSAGEb. Runtime Priority: 100c. Activate Priority: 255d. Beacons 0e. Pixel Service

Pass / Fail

20. Verify that the message is displayed centered on the middle line. Pass / Fail

21. Verify that each page is on for 2 seconds with 2 flashes on and 2 flashes off perpage.

Pass / Fail

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

23. Set defaultJustificationPage.0 to 2 (top). Pass / Fail



of 71 10/31/2007

24. Set defaultPageOnTime.0 to 10 (1 second). Pass / Fail

25. Set defaultPageOffTime.0 to 10 (1 second). Pass / Fail



28. Get dmsActivateMessage.0. Set the value received back to dmsActivateMessage.0to re-activate the message.

Pass / Fail

29. Verify that the message is displayed on the top line of the sign, left justified. Pass / Fail

30. Verify that each page of the message is on for one second, and off for one second,with rapid flashing of .2 seconds on and .2 seconds off.

Pass / Fail

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

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

33. Set defaultPageOnTime.0 to 16 (1.6 seconds). Pass / Fail

34. Set defaultPageOffTime.0 to 5 (.5 second). Pass / Fail



37. Get dmsActivateMessage.0. Pass / Fail

38. Set the Response Value received back to dmsActivateMessage.0 to re-activate themessage.

Pass / Fail

39. Verify that the message is displayed on the bottom line of the sign, right justified. Pass / Fail

40. Verify that each page of the message is on for one and a half seconds, and off forone half second.

Pass / Fail

Test CaseResult:

Pass / Fail

Test CaseNotes:

2.10 TC010 –Default Messages

Test Case:

TC0010

Title: Default Messages



of 71 10/31/2007

Description: The purpose of this test is to verify that the sign will correctly perform the followingoperations: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 forlonger than the Comm Loss Timer.

Pass/FailCriteria:



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

Changeable Message 2: END[nl]DURATION[nl]MESSAGEChangeable Message 3: SHORT[nl]POWER[nl]LOSSChangeable Message 4: LONG[nl]POWER[nl]LOSSChangeable Message 5: COMM[nl]LOSS[nl]MESSAGEBeacon 0 (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“TEST[nl]MESSAGE” 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 DURATION MESSAGE” 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

“TEST[nl]MESSAGE” using a duration of 10 (minutes).

Pass / Fail




of 71 10/31/2007

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

16. Verifythat after power up the message “SHORT POWER LOSS” is displayed. Pass / Fail

17. Using Test Case TC002 download and display the message“TEST[nl]MESSAGE” 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 “LONG POWER LOSS” 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“TEST[nl]MESSAGE” 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 “COMM LOSS MESSAGE” 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 CaseResult:

Pass / Fail

Test CaseNotes:

2.11 TC011 –Time

Title: Time

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

Test Case:

TC011

Pass/FailCriteria:




of 71 10/31/2007


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. Verify that the Response Value for globalTime.0 is twenty more than the valuerecorded 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

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 inUS 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 Pass / Fail



of 71 10/31/2007

corresponds to 03/09/2008 3:00:15 AM. (May be off by a second or two)

29. Set globalTime.0 to 1225504740. (This will set the clock in the sign to a time inUS 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 whichcorresponds 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 whichcorresponds to 1/1/2006 12:00:15 AM. (May be off by a second or two)

Pass / Fail


(Leap year change test)

Pass / Fail



Pass / Fail


(Century change test)

Pass / Fail



Pass / Fail

Test CaseResult:

Test CaseNotes:



of 71 10/31/2007

2.12 TC012 –Scheduling

Title: Scheduling

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

Test Case:

TC012

Pass/FailCriteria:



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

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



of 71 10/31/2007

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 changeablemessages as follows:

34. Changeable 1: CHANGE[nl]MSG 1 Pass / Fail

35. Changeable 3: TEST[nl]MSG 1 Pass / Fail

36. Changeable 4: TEST[nl]MSG 2 Pass / Fail

37. Beacon 0 (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 “TEST MSG 2” is displayed. Pass / Fail


Pass / Fail


Pass / Fail



of 71 10/31/2007

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




Pass / Fail


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 “CHANGE MSG 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.



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




Pass / Fail


Pass / Fail

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 “CHANGE MSG 1” is displayed. Pass / Fail

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

Pass / Fail


Pass / Fail



of 71 10/31/2007

Test CaseResult:

Pass / Fail

Test CaseNotes:

2.13 TC013 –Security

Title: Security

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

Test Case:

TC013

Pass/FailCriteria:



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 orthe valid administrator community name.

Pass / Fail

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

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



of 71 10/31/2007

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 thetime that elapsed between step 17 and step 21, and that the Set attempt from step19 was ignored.

Pass / Fail

23. Change the community name in the test application to administrator, or the validthe 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


31. Verify that the Response Value for globalTime.0 is valid, incremented by thetime 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 validthe administrator community name.

Pass / Fail

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



of 71 10/31/2007

44. Without changing the community name in the test application, SetcommunityNameAdmin.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

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

Pass / Fail

Test CaseNotes:

2.14 TC014 –Pixel Failures

Title: Pixel Failures

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

Test Case:TC014

Pass/FailCriteria:



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



of 71 10/31/2007

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 pixelTestActivation.0 is 2 (no test). Pass / Fail

9. Get pixelFailureTableNumRow.0 Pass / Fail

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 modulecolumns (example 35 for a 5 X 7 module).






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



of 71 10/31/2007

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

34. Verify that the Response Value for pixelFailureXLocation.2.X equals the columnnumber 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 rownumber 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.






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

Test CaseResult:

Pass / Fail

Test CaseNotes:

2.15 TC015 –Power Supply Error Status

Title: Power Supply Error Status

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

Test Case:

TC015

Pass/FailCriteria:



1. Get lineVolts.0 Pass / Fail

2. Verify that the Response Value for lineVolts.0 is 110 (or the value of the AC linevoltage on the sign)

Pass / Fail

3. Get powerSource.0 Pass / Fail



of 71 10/31/2007

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

5. Get shortErrorStatus.0 Pass / Fail

6. Verify that the Response Value for short ErrorStatus.0 is 0 (no errors). 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) or7 (battery).

Pass / Fail


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

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.



Pass / Fail


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



22. Disconnect a power supply in the sign.



25. Reconnect the power supply.



Pass / Fail





Test CaseResult:

Pass / Fail



of 71 10/31/2007

Test CaseNotes:

2.16 TC016 –Temperature and Status

Title: Temperature and Status

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

Test Case:

TC016

Pass/FailCriteria:



1. Get the following objects:

tempMinSignHousing.0tempMaxSignHousing.0

Pass / Fail

2. Verify that the Response Values for tempMinSignHousing.0 andtempMaxSignHousing.0 reflect the temperature range within the sign housing.

Pass / Fail

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



Pass / Fail

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

Pass / Fail

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



Pass / Fail

8. Verify that the Response Values for tempMinSignHousing.0 andtempMaxSignHousing.0 reflect the temperature range within the sign housing,reflecting the decrease in temperature due to the removal of the heat source.

Pass / Fail

Test CaseResult:

Pass / Fail



of 71 10/31/2007

Test CaseNotes:

2.17 TC017 –Field Display

Title: Field Display

Description: The purpose of this test is to verify that the sign correctly displays fieldinformation.

Test Case:

TC017

Pass/FailCriteria:



1. Set the following objects:

1. globalTime.0 to 1103539320 (12/20/2004 10:42:00 AM)2. controllerStandardTimeZone.0 to 03. Set controllerDSTStatus.0 to 1 (disable DST)

Pass / Fail

2. Using the procedure from Test Case TC002, download and display the followingMULTI message:[fo1]TIME: [f1][nl]DATE: [f9]\[f8]\[f10][nl]DAY:[f7][np]LONG YEAR: [f11][nl]TEMP: [f3] DEG C[nl]TEMP: [f4] DEG F

Pass / Fail

3. Verify that the sign displays a two page message as follows:

Page 1: TIME: 10:42DATE: 12\20\04DAY: MON

Page 2: LONG YEAR: 2004TEMP: 20 DEG CTEMP: 68 DEG F

NOTE: the temperature displayed will correspond to the actual ambient (outside)temperature at the time of the test.

Pass / Fail

4. Get statMultiFieldRows.0 Pass / Fail

5. Verify that the Response Value for statMultiFieldRows.0 is 8. Pass / Fail

6. Get statMultiFieldCode.1 Pass / Fail

7. Verify that the Response Value for statMultiFieldCode.1 is 1. Pass / Fail

8. Get statMultiCurrentFieldValue.1 Pass / Fail

9. Verify that the Response Value for statMultiCurrentFieldValue.1 is “10:42”. Pass / Fail






of 71 10/31/2007

13. Verify that the Response Value for statMultiCurrentFieldValue.2 is “12”. Pass / Fail












25. Verify that the Response Value for statMultiCurrentFieldValue.5 is “MON”. Pass / Fail








33. Verify that the Response Value for statMultiCurrentFieldValue.7 is the ambienttemperature in degrees Celsius.

Pass / Fail




37. Verify that the Response Value for statMultiCurrentFieldValue.8 is the ambienttemperature in degree Fahrenheit.

Pass / Fail

Test CaseResult:

Pass / Fail

Test CaseNotes:



of 71 10/31/2007

2.18 TC018 –Reports

Title: Reports

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

Test Case:TC018

Pass/FailCriteria:



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.3. Record when the AC voltage drops below or rises above a threshold.Also record the UPS voltage when the power goes off and goes on.

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

3. Set controllerStandardTimeZone.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 than or equal to16.

Pass / Fail

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

Pass / Fail

10. Get maxEventLogConfigs.0 Pass / Fail

11. Verify that the Response Value for maxEventLogConfigs.0 is greater than or equalto 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 0Set eventClassClearTime.N to 4294967295Get eventClassNumRowsInLog.NVerify 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



of 71 10/31/2007

15. Set eventClassLimit.1 to 20 Pass / Fail

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


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 messagemulti string).

Pass / Fail

24. Set eventConfigLogOID.1 to 1.3.6.1.4.1206.4.2.3.5.8.1.3.5.1 (current messagemulti 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



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



of 71 10/31/2007



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



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 ChangeableMessage 1 “TEST 1”.

Pass / Fail


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

Pass / Fail


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

Pass / Fail


60. Get eventClassNumRowsInLog.1 Pass / Fail

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


eventLogID.1.1eventLogID.1.2eventLogID.1.3

Pass / Fail

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

Pass / Fail


eventLogTime.1.1eventLogTime.1.2eventLogTime.1.3

Pass / Fail

65. Verify that the Response Value for eventLogTime.1.1 is 109871600 plus theelapsed 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 theResponse Value for eventLogTime.1.1.

Pass / Fail

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

Pass / Fail

68. Get eventLogValue.1.1 Pass / Fail



of 71 10/31/2007

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

Pass / Fail


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

Pass / Fail


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

Test CaseResult:

Pass / Fail

Test CaseNotes:

2.19 TC019 –Brightness Control

Title: Brightness Control

Description: The purpose of this test is to verify that the signcorrectly utilizes brightness control.

Test Case:

TC019

Pass/Fail Criteria: The DUT shall pass every step described in thistest 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 orexceeds 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 isbright, or by shining a light on it if the ambient light is low.

Pass / Fail



of 71 10/31/2007

13. Verify that the following objects change to reflect the new value of light enteringthe photocell:

dmsIllumPhotocellLevelStatus.0dmsIllumBrightLevelStatus.0dmsIllumLightOutputStatus.0

Pass / Fail

14. Verify that the actual brightness of the sign has changed in accordance with thenew 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



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

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

Pass / Fail

Test CaseNotes:

item 683.4503 11m arterial full matrix, led based ... · mark iv ids mississauga (mark iv...

Documents