svat user guide

PRODUCTIONSVAT

(SYSTEM VERIFICATION AUTOMATION TEST)

GENERAL USER GUIDE

By: Son Vo

Date: January 13, 2015

Table of ContentsI. Running Test........................................................................................................................................3

II. Keywords, syntaxes and their explanations.......................................................................................19

III. LabVIEW Installation & EXE File Creation......................................................................................20

IV. Important files...............................................................................................................................23

V. Test Report and Failure/Fix Data Collection......................................................................................28

VI. New Firmware and Daughter Board Release.................................................................................28

VII. Update text files in TextFolder\SetupFolder folder on host computer..........................................29

VIII. General Test Rack Setup, Parts and Troubleshooting....................................................................30

IX. Test record and backup.................................................................................................................35

Revision History

Rev Description of Change Process Owner Reviewers Date

A Initial draft for release Son Vo Richard Aronson 8/12/2014

B Updated release review Son Vo Richard Aronson 1/13/2015

C Merged updates and format changes Son Vo Richard Aronson 1/14/2015

January 13, 2015 document.docx

I. Running Test.The images and explanations below are meant to help the user have some general

understandings of how to execute this System Verification Automation Test (SVAT) application. The actual images the operators will see may be slightly different. Please make sure that Excel and other applications that use serial communication are closed before running SVAT. This user guide is applied to all products that the test racks support. Operator must follow all instructions present on screen to have the tests run correctly. WCP test is very critical with the size and location of the browser thus operator must size the browser the exact size when ask to.

After the SVAT has been launched but there is no activity happening after any button on the Main Window has been pressed, this means that SVAT is hung up or it is still inside in some sub loop. The operator will not be able to get out of this mode therefore SVAT must be exited.

Click the “STOP”, red polygon button at the top left of the Main Window to exit LabVIEW.

Below are the steps of how to execute the RGB Production SVAT

1. Launch SVAT.

Double click this icon (picture below) on the test rack computer’s desktop to launch the application. SVAT will automatically load the latest version and the main window will open up in full screen mode.

This image is the shortcut to Executable.

2. Running SVAT

If SVAT is not running, the operator would see this sign at the top left corner of the SVAT Main Window. Click the white arrow button to run SVAT. If SVAT is

running, the operator would see this sign instead. If SVAT prompts that the executable version is not current, please close SVAT and re-run Launch SVAT step above.


3. Functions of important buttons on SVAT Main Window

While SVAT is running, but no test is running yet, there are several visible buttons on the Main Window where the operator can click to execute its pre-programmed function(s). The two images below show the important buttons that will be visible once SVAT is launched and running.

- FTP-Host-to DUT button: If this button is clicked, a sub window will pop up to ask the operator to select the path of the file that will be FTP to the DUT. Once the path is selected, SVAT will FTP the chosen file to the DUT. Warning: SVAT will not know if FTP was successfully transferred or not.

- Select device to talk to: Click the dropdown box arrow to view the devices on the test rack. Once a device is selected, a blinking PAUSE button will be visible. This indicates that the operator is able to communicate with the selected device manually. To talk to a different device, the operator just needs to re-select a different device. Type the command in the communication window to talk to the selected device. To get out of the manual communication mode, click the pause blinking button.

- Stop button: If SVAT is running but no test is running, this button will have no function. This stop button is also visible during test. Click it to stop the test. It is the appropriate method to terminate the test. This button will work immediately if SVAT is not in any sub-loop otherwise SVAT will have to complete the sub-loop and then execute this button.


VIEW DUT FILES button: An imbedded sub window will appear on the Main Window if this button is clicked. See figure below.

Click CURRENT TEST to view the test result of the last tested DUT. Enter S/N and click “OPEN TEST HISTORY BY S/N” will open test result of the entered S/N. Click “EXIT” button of the said window to close this window.

- EXIT button: Click this button to exit LabVIEW. - RUN button: Click this button to run test.- LINX MAC button (not shown): Click this button to run the Mac Address installation

process for the CPU card of the Linx products.

4. Run Test

The test will start if this button is pressed. One of the setup steps that SVAT does is to check the Serial Number (SN) of the DUT. If the SN matches one of the SNs in the NotCorrectSerialNumber.txt file or the operator selects to change the SN, SVAT will ask the operator to enter a new SN and SVAT will change it. SVAT uses the same method of installing new SN for installing new Mac Address, but Mac Address installation is part of the test grid instead. The test process for all models will be the same from step “a” to step “d” below.

a. Establishing Communication

After the “RUN” button is clicked, SVAT will try to communicate with all devices of the test rack. Once all communications are established, SVAT will talk to the DUT to inquire some information. If one of the devices of the test rack is unable to communicate, test will be terminated. SVAT will list what device it is for easy troubleshooting. If DUT is unable to communicate, SVAT will ask the operator to exit test or select a model that doesn’t have serial communication.


b. Selecting Model

A sub window (see image below) will pop up to ask the operator to select a model. (Note: if SVAT detects that the DUT has only ONE (1) available model, SVAT will bypass this step.)

Click the dropdown arrow of the SelectedElement box to select a model. Click the “OK” button to continue after a model has been selected. There are two types of models, Label Model (Common Model) and ID Model. Label Model is the model that appears on the label. This is the model that the operator will select. The other model is the ID Model. It is the imbedded model of the system. This ID Model is shown in the ID or Sysinfo command. These two models are sometime different therefore SVAT has to check to make sure that the DUT has the correct Label Model and the correct ID Model. Change model process will occur if the DUT’s ID model is not match with the ID model of the selected model in the reference setup file.

c. Test Selection Configuration Window.

This window allows the operator to select what test cases to run. The selection process of this window is designed to be executed in a particular order. The next selection box or dropdown box will appear following the completion of the previous selection. Please see images of this section below.

- Selecting Test Mode (Type): 1st Step

There are two test modes, Write, Create References and Test modes where Write mode is to create reference files and Test mode is to test, and if required, reference files will be called up to compare. See image below.


Dropdown arrow

Click the dropdown arrow of the Select Test Type box to make the selection.

- Test Grid Selection: 2nd Step

There are two ways to select a test grid for a DUT, Automatic and Manual Select. See image below.

Click the dropdown arrow of the Test Grid Selection and then select either Automatic or Manual Select.

Automation: SVAT will select a test grid based on the selected model. This must be the only test grid selection method after all test girds and setup files are created and completed.

Manual Select: A file selection window will pop up with the default path of where all test grids are stored. See image below.


Dropdown arrow

To select a test grid, select a test grid then click OK button or double click on a test grid.

- Test Sheet Selection: 3rd Step

A test grid (Excel Workbook) might have more than one sheet. The operator must select a sheet to run. See image below.

Click the dropdown arrow of the Test Sheet Selection to select a test sheet to test.

- Test Case Selection: 4th Step

The list of the test cases will show up. Image below shows the test cases for the QVHDxV model. Click “SELECT ALL” button to select all test cases or click ON/OFF LED in front of the test case to select or deselect each test case individually. Click “UNSELECT ALL” button to unselect all test cases. “SELECT ALL” and “UNSELECT ALL” buttons share a same button. SVAT will execute this button depending on what mode is it in. Two images below show all test cases that are not selected and all test cases that are selected, respectively. Warning: The default values of the LEDs are NULL, not solid green, see the last LED of the image below.


- DONE button: 5th

Click this button after all selections are made. Once this button is clicked, the operator can’t go back therefore the operator must double check all of his/her selections.


d. Test Case Execution.

At this stage, SVAT will start running each selected test case sequentially. SVAT will skip any test cases that are not selected. Below is the information of the Main Window and the pop ups that the operator will see during test.

- Main Window

The Main Window displays some important information so that when someone looks at the Main Window they will know the status of the DUT. However there are some displays only show up after the test has been completed or terminated. The image below shows the information of the DUT and status of the test during test.


Model,SN,FW

Test case, where at

Current Device Keyword

Below are the descriptions of the displays of the Main Window (image above.)

Model: ID Model. Serial #: Serial Number of DUT. Firmware: DUT’s firmware. Customer Name and CO#: Name of customer and Sale order

number. This info is obtained during test. Test Grid Path: The path of the selected test grid. Test Sheet: Selected test sheet of the test grid. Current Test Case: Shows what test case it is testing. TEST/WRITE button: Shows what mode it is. Command Line of Current Test: Shows total number of lines

(elements) and the line where SVAT is at. Current Device: Shows current device that SVAT is

communicating. Keyword: Shows what keyword it is. PQA Method: Shows what PQA (Picture Quality Analysis)

method it is. Test Case Loop ON/OFF: Shows if current test case is loop enable

of disable and number of cycles. Test Cases and LEDs: Shows all test cases of a test sheet and

their status selected or not selected. Test case status LEDs (LEDs right in front of the test case). It is

corresponding LED will light up RED if that test case fails. Slider: Points to current test case. Test Completed button (not shown): Shows if test has been

completed. Print Front Panel button (not shown): Prints the main window. Print Current Report button (not shown): Prints the last tested

DUT’s report. Terminated button (not shown): Indicates if test has been

terminated. This button only appears if the operator terminates test.

Run Last Test button (not shown): This button only appears after the test has been completed. Operator can click this button to run the exact test for the next same DUT. This is to bypass all the test selections.

Status Information Box (not shown): This box shows what SVAT is doing to the DUT. This box only appears for long execution such as booting up. This is to help the operator aware that DUT is booting or the operator might mistakenly think that SVAT is hung up.


- Pop-up Windows

The order of the pop ups present here is not meant to show the same order as of during test. The operator might see the same pop up multiple times during test because it is used throughout the test. The center box of each window is usually the descriptions, questions and/or instructions that the operator has to perform. Most of the pop ups will not be shown once the test rack is capable of doing PQA (Picture Quality Analysis) automation; SVAT will analyze the image instead of the operator. Below are the description and the image of each pop-up. Some pop-ups are too big to show the entire image therefore they are shown in multiple images.

- Firmware Check Window.

Keyword “FirmwareCheck” must be used to activate this window (image below). This window only pops up when the firmware check has failed, that is when the DUT’s firmware did not match with the reference or there was no reference file. The detail box lists the information of what passed, what failed and versions of different firmware for the DUT and Reference. If no reference file, the “REF: (blank)” will show and SVAT will open a recorded text file to ask the operator to verify and save it as reference file. The image below shows the firmware version fails because there is no reference file, you can see REF is “blank”. However, the FW, Boot, FPGA of the daughter cards (DB) are OK.


If the above window pops up, it means the Firmware Verification step has failed. There are several options that the operator has to make to continue the test. Please choose option or options (one at a time) that are appropriate to the test. Below are the descriptions of what each option does.

1. Run Firmware Update

If this option is select, SVAT will simply run the remainder of the selected test case, normal operation. The test case is written to include upgrade firmware step (but not all models), but it is only be executed if Firmware Verification step has failed and the operator has chosen to run firmware upgrade.

2. Update Sysinfo Ref File

SVAT will update the reference file with the current recorded file. The operator must run step 4 below following this selection.

3. Update Excel Ref File for DB Cards

Reference Excel file of DB cards will open. The operator has to manually modify the file and save it. The operator must run step 4 below following this selection.

4. Re-Run Firmware Check.

Select this option to rerun the Firmware Check if reference files have been updated.

5. Skip This Test Case

SVAT will move on to the next selected test case and an error will be recorded in the test history report of this DUT.

6. EXIT

SVAT will exit LabVIEW and an error will be recorded.


- Order Verification Window

Keyword “OrderVerification” must be used to activate the Oder Verification window (image below). The Order Verification window has been broken down to several images for easier demonstration. The images are shown below with their descriptions.

1. Customer Name and Sale Order Number and Input Output Sections.

The operator has to manually enter the customer name and the sale order number in the customer name and sale order fields.

If applied, the 625 level of input, output and wpm cards and the quantity of each type will show in the designated field.

The above image is where the operator has to make a selection for Input Output Section. If “Incorrect” is selected, test will be terminated. Select “N/A” if this section is not applicable to the DUT. Select “Correct” if all cards and quantities are correct.


2. Options Section

The image below shows the Standard Options and the Purchase Options (available options for purchase) of the DUT. To enable a purchase option, the operator needs to turn on its LED. Standard options and selected purchased options will be loaded to the DUT when using keywords “OptionOnTest” and/or “OnptionOnFinal”. There are also some Test-Required options where they are must be enabled during testing and disabled after testing therefore two different keywords above are used to separate when it is testing and when it is final. Test-Required” options are also can be purchase options too.

The image above is for the Options Section. If all selections are made, then select “Selection Made”. If it is not applicable, then select “N/A”

3. Done button.

Click “DONE” button when all selections of customer name, sale order number, and input output card and option sections are made. SVAT will prompt operator if any field is unfilled.


- Physical Verification.

This is the overall physical verification such as screws, plates, paint… of the DUT for the operator to enter. Please use keyword “PhysicalVerification” to activate this window. The operator must fill out all Tech and Q.C. fields, Originator’s name and QC Tech name. To quick fill Tech and QC fields, click “QUICK FILL” button to fill them all. The SVAT will alert the operator if any required field is not filled out. Please make sure to enable “YES” for the RMA button if the DUT is a RMA. Please refer to 4 images below for this section.


- Simple Pass/Fail Window.

Use “PhysicalCheck” keyword to activate this window (image below). Use this keyword for something about PASS/FAIL selection and PQA visualization (PQA that cannot be automated, image that will always be different for each run. This image would be a running clock image.) Example for when using this keyword: This can be used to ask the operator to verify if the fan is running or not. The choices for this window are spelled out in the buttons, please see picture below. If “PASS” and “TALK 2 DEVICE” are selected, SVAT will not record any errors in the test report. SVAT will record an error for all other choices and will ask the operator to describe the failure and select a failure code in a different window. The operator can also choose not to enter the failure code by clicking “Ignore Failure” button of the said window.


If “TALK 2 DEVICE” is selected, another window will open up where the operator has to select a device to talk to (see image below). The operator can select a device at any time by clicking “SELECT DEVICE” button. Click “EXIT” to close the “TALK 2 DEVICE” window. There is another portion (not shown) of the “TALK 2 DEVICE” window where the operator types in commands to communicate with the current selected device.

- PQA Automation Window

Note: The test rack is not capable of doing any PQA Automation yet therefore a PQA Pass/Fail selection window, window below, will pop up for the operator to select Good or Not Good after the operator has visually analyzed the signals (images). Use keywords FS-PQA-Verification, Initial-PQA-Verification and Route-PQA-Verification to activate this window. If PQA Automation is available, SVAT will execute the PQA automatically without popping up this window. SVAT will only pop up this window when PQA Automation fails. It is then to ask the operator to double check the quality of the signal and then make a selection. For now, Without PQA Automation, this window will pop up for the operator to make a selection after the operator has visualized the signal.


There are basically three options for this window. Good, Not Good, and Re-Run Current Test Case. To Rerun current test case, click the dropdown box and select “Re-Run”, SVAT will then rerun the entire test case. Click “GOOD” if the operator sees a good signal, clear and good quality image. Click “Not Good” if the operator does not see a good image. If “Not Good” is selected, the failure collection process will be executed as describe in the Simple Pass/Fail section above. “Rerun” and “Not Good” will report an error in the test report.

This paragraph describes how SVAT displays the DUT’s outputs and inputs. SVAT displays the DUT’s outputs and inputs in three different ways, 1: Make all inputs visible and make them into strips (rectangles) that cover all output columns, but not every output. This is called Initial Display therefore Initial-PQA-Verification keyword should be used. 2: Display one input at a time and stretch the selected input to cover all output(s). This is called Full Screen display therefore FS-PQA-Verification should be used. 3: The third display is primary for Linx products. It is when routing an input signal to all outputs. It is called Route Display therefore Route-PQA-Verification should be used. Base on the keyword, SVAT will use the appropriate calculation to perform the correct PQA if current test rack is capable of performing PQA automation.

The display of the DUT will be different for different models, but they are all followed the same display methods mentioned above. For Initial Display, SVAT uses the DUT’s current OPTM and maximum number of inputs and outputs that the DUT can support to calculate the sizes and locations for each input. For example: MW4500 is the DUT with 10 inputs and 8 (2X4) outputs, but MW4500 can support up to 30 inputs and 12 (3X4) outputs. SVAT will use the maximum input (30) and maximum output (12) for calculation. Since this DUT only has 10 inputs, it will only cover 10/30 or (1/3) of the total output. To make a reference for this initial test, 1/30 of the total output is used because they are all redundant. SVAT does not have to make references for same model with different configuration.

II. Keywords, syntaxes and their explanationsPlease see Keywordwords.xlsx in LabVIEW-ControlFilesFolder\ExcelFolder\GeneralExcelFolder for details.


III. LabVIEW Installation & EXE File Creation

A. Modules that need to be downloaded from NI website.

These three modules below must be downloaded from NI.com website. They will come in as zipped files. Please make sure that you download the latest version of each one. User name is “[email protected]” and password is “rgb”. Go to ni.com and then download section to download the files below. You will have to type in the exact name in the search box to pull up the correct and latest module.

1. NI Device Driver: This is for communication.

2. LabVIEW Run-Time Engine: This is for running executable LabVIEW files.

3. Vision Development Module: This is for vision such as screen shot….

Unzip the files and install them on the host computer. Please ask RGB test engineer for a valid serial number when installing Vision Development Module. The whole process will take a few hours.

B. Folders Creation

1. Copy and paste the entire SVAT-RGB folder from one computer onto the host computer C drive. Some modifications are needed. Please see Edit Files step below.

2. Creating central folder on the network.

Only do this if the central folder on the network has not been created yet. This folder should have been created. This folder contains all files that can be shared between hosts.

a. Create a folder on the network, give it an appropriate name.b. Copy and paste the entire LabVIEW-ControlFilesFolder to this folder.c. Copy and paste the entire TestResultFolder folder to this folder or

create the “TestResultFolder” folder if the “TestResultFolder” folder is not existed yet. Make sure “ReferenceFolder” and “DeviceUnderTestFolder” folders are present in TestResultFolder folder.


mailto:[email protected]

C. Create Shortcut to launch LabVIEW EXE

1. Open the SVAT-RGB folder on the host computer C drive

2. Open LabVIEW-VI-Folder

3. Create a short cut for Launch-SVAT-EXE application. Put this shortcut in the host computer desktop.

D. Edit Files

1. From the SVAT-RGB folder, open TextFolder then SetupFolder

2. Open file: “SystemPortAssignment” and edit the settings to reflect the serial communication configuration of the current test rack.

3. Open file: “AutomationSetupPath” and change the path to where the LabVIEW-ControlFilesFolder folder is located.

3. Open file: “PathOfTestResultFolder” and change the path to where the TestResultFolder folder is located.

4. Open file: “IPAddressIPGateWay-Set” and change the settings of the reserved IP address and IP gateway for the current test rack. The IP address must be different for each test rack. This is to avoid the conflict when multiple test racks are running at the same time.

5. Open file: “WallDisplaySetup” and change the display configuration to reflect the current test rack’s display configuration. Test rack must have two SuperView 4Ks for displaying. Default setting is that four (4) inputs of the first SuperView (FirstWall) and all of the eight (8) inputs of the second SuperView (SecondWall) are used. Output of the SecondWall will be connected to the input #5 of the FirstWall. Output number one (1) of the FirstWall is for displaying.

6. Open file: “EXEVersion” and change it to the version of the LabVIEW EXE files.

7. Open the C:\SVAT-RGB\TextFolder\ReferenceFolder and delete all folders in this folder if the host computer doesn’t have the same specifications of the computer where you copy the SVAT-RGB folder from. If you copy from the master USB stick, you don’t have to do this.

E. Creating LabVIEW EXE (This can only be done on development computer and it is assumed that no changes made to the project)

1. Open the C:\SVAT-RGB\LabVIEW-VI-Folder


2. Double click on “SVAT-RGB-Production.lvproj”. The SVAT-RGB-Production project window will open up. See image below.

3. Click “Build Specifications” and then “My Application”

4. Select “Destination Folder” and then enter the path where the EXE files will be stored. Please make sure that this folder is existed and it is empty. See image below.

5. Click “Version Information” and enter the version that you want. To control what version can be executed, you have to edit a file named “EXEVersion”. Please refer to “Edit Files” section above.

6. Click “BUILD” to build the EXE


7. Copy the entire contains in the folder of step 4 above and paste it to LabVIEW-ControlFilesFolder\EXEFolder of the central folder (folder in step 2 section B above)

IV. Important files.There are several very important Excel and text files that support the System Automation

Verification Test (SVAT). You have to make sure that these files are up to date. Important text files are stored in root\TextFile\SetupFolder folder where root is the path that the SVAT is located at. Important Excel files are in LabVIEW-ControlFilesFolder\ExcelFile\GeneralExcelFile folder. The test grid Excel files are stored in LabVIEW-ControlFilesFolder\ExcelFile\ExcelTestGridFile folder. The TestFailureLog.xlsx file is stored in TestResultFolder\TestFailure folder. Below is the list of the files and their purposes.

A. Text Files.

There are a lot of setup files for the program to run smoothly. But, a few files will be explained below because you might have to edit these files to get the wanted results.

1. AutomationSetupPath.txt

This file contains the path of the setup folder. The setup folder is the folder that contains most of the needed materials to setup LabVIEW.

2. DisplayUseTiming.txt

This file contains the timing that SVAT uses to display maximum inputs of DUT on monitor. (This has been disabled. Different method has been used.)

3. FirstWallRGBOutputNumber.txt

This file contains the input number of the First Wall that will intake RGB when test rack switches to RGB testing mode. Since SuperView 4k is capable of taking RGB and DVI signal with the same connector therefore it is convenient to use input #1. Letter “1” should be entered for this file.

4. InvalidMacAddress.txt

This file lists the invalid Mac Addresses. SVAT inquires the Mac Address of the DUT and then compares it with the Mac addresses of this file. If it matches, SVAT will run the Mac Address installation process.

5. IPAddressIPGateWay-Set.txt

This file contains the reserved IP Address and IP Gateway that the particular test station will use to communicate with DUT via Telnet. SVAT loads these IP address and IP gateway to the DUT for TCP communication. Different test racks


must have this IP Address differently or conflict will occur if two test racks communicate with same IP Address at the same time.

3. MacAddressFile.txt

This file stores the used Mac Addresses. Every time SVAT runs the Mac address installation process, SVAT will ask the operator to enter the reserved Mac address of the DUT. After the completion of Mac address installation, SVAT will add the word “USED”, DUT’s serial number and the date to the end of the Mac address and store it in this file for reference. SVAT will alert the operator if the DUT’s serial and/or Mac address match with this file.

5. NotCorrectSerialNumber.txt

This file lists the incorrect serial numbers. SVAT inquires the serial number of the DUT and then compares it with the serial numbers of this file. If it matches, SVAT will run the serial number installation process.

6. PathOfTestResultFolders.txt

This file contains the path of the folder that stores all test data for all test racks.

7. Trigger-Edid-Check.txt

This file contains the information (phrase) that is used for EDID testing for Tigger products.

8. SystemPortAssignment.txt

This file lists the devices names and their serial communication ports and baud rates of the test station. The format must be as is in the file. If changed, it might not work correctly. To comment out a line, you just need to enter 3 X’s in front of the line.

9. WallDisplay.txt

This file lists the configuration of the two SuperView 4K’s of each test rack. The first line is the main output that is used to connect to monitor or capture card. The next four lines are the input numbers of the First SuperView 4K that are used and these inputs will be connected directly to the outputs of the DUT. The next line is the input number that is used for connecting the output of the Second SuperView (SecondWall) to it. The rest (8 lines) are the inputs of the Second SuperView. These inputs will be connected directly to the outputs of the DUT. The test rack is setup to support twelve outputs by using two SuperView 4Ks. The FirstWall will intake 4 outputs and the SecondWall will intake 8 outputs. One output of the SecondWall will feed to the FirstWall.

10. WhenItIsSameAsPrompt.txt


This file contains characters or phrases that serve as PROMPT (>), end of a command, for some particular models. Not all models end with “>” at the end of a command therefore this file is used and please updates this file accordingly.

B. Excel Files.

There is one important setup Excel, Model-InputOutput.xlsx, file that must be maintained carefully. Three worksheets, InputOutput, OptionCode and CardVersionDetails of this file are being used. Below are the explanations of each important column of each sheet. The TestFailureLog.xlsx is for failures collection.

TestFailureLog.xlsx File

1. TestFailureLogSheet Sheet

This sheet lists the format of how failure data are connected. You must not change this format.

2. FailureCodes Sheet

First column lists the failure codes. You can edit this column to add, remove or rename the failure codes.

3. FixCodes Sheet

Same as FailureCodes sheet, but it is for fix.

Model-InputOutput.xlsx File

1. InputOutput Sheet

- ModelDescription

This column lists the Label Models or Common Models. This column is used to determine the different in firmware, options and configurations.

- ID Model

This column lists the ID imbedded models of the systems. This column is used when switching model is required.

- Model Code

This column is not important because the design has been changed, but it still needs a number for each product.

- # of Inputs


This column lists the number of inputs. If configurable, the word “congif” should be entered here. If it is fixed, the number of inputs should be entered here.

- # of Outputs

Same as “# of Inputs”

- VideoInType

Not used

- VideoOutType

Not used

- Password

This column lists the password of each model. This is used for commands that require password.

- TestGrid

This column lists the test grid name of each model. All test grids must be in the central location.

- ProductFamily

This column lists the product family of each model. This is used for data storage.

- HowToChangeModel

This column lists the special method of how to change model from one to another of the same product. If blank, it uses the regular method.

- OutputDisplay

This column lists the display configuration of each model so that the output display during test can be configured accordingly to display the outputs correctly.

- MaxInput

This column lists the maximum input number that each model can support. This is used for display purpose.

- MaxOutput


Same as MaxInput

- SameFW-Family

Models that use same firmware must have same name in this field. This is for data storage.

- SameVideo-Family

Models that output same configurations and same video type should have same name in this field. This is use for video storage.

- BootCode

List the current boot code version of each model.

2. OptionCode Sheet

- Start

This column lists all option names.

- Next Columns

These columns list the option keys and their status for each common model or label model. These option keys are obtained from option code generator with serial 99999. The statuses are Purchase (P), Test Require (T) and Standard (S). Test-Require options are also available for purchase.

3. CardVersionDetials Sheet Duplicated has been created for GA

- 625 Level

This column lists the 625 level of each daughter card. This information will be used to display for the operator to verify number of cards installed in the DUT

- Card Description

This column lists a key phrase that describes each different card type when “sysinfo” or “ver” command is entered. This is used to detect what types of cards are installed in the DUT.

- FW, HW, FPGA versions and Boot


These columns list the latest versions for each type of card. If applicable, update these columns when new firmware or new daughter is released.

- Input/Output

This column lists if card is input or output card. Some input cards and output cards have same descriptions in “sysinfo” command therefore this is required to separate them.

- Signal Type

This column lists the types of signal each card type supports. This is used for inputting correct signal and ask operator to connect correct signal (cable) to the card.

V. Test Report and Failure/Fix Data Collection.A. Test Report

SVAT creates the folder for each DUT. Folder name has the serial number included. This is to differentiate the DUTs’ folders. This folder contains several import files including the test report. The DUTs are categorized by their product name. All the DUTs’ folders are located at root\TestResultFolder\DeviceUnderTestFolder where root is the path where the TestResultFolder is. SVAT appends test information to the overall test report file for each test cycle. SVAT also creates the current test report for easy viewing and printing.

B. Failure/Fix Data Collection

As mentioned in the Running Test section under Pass/Fail and PQA Automation windows, SVAT collect failure/fix data for analysis. This Excel file is located in TestResultFolder under TestFailures folder. SVAT will append the data to this file each time the DUT fails a test. SVAT also ask to operator to enter a fix code and a fix description after the completion of the test if SVAT finds there is an open failure entry for the DUT.

VI. New Firmware and Daughter Board ReleaseThis section explains what has to be done to SVAT when new firmware and/or new daughter board (DB) is released. Please always to update the file that is on the network. After you’ve made the changes to files if required, you must run the test to see if SVAT works as expected. You should run a test with old firmware to see if SVAT catches the incorrect firmware of the DUT. You should also run a test with the correct firmware to verify that the firmware is correct.

A. New Firmware Release.


Only Linx firmware release requires some changes in the CardVersionDetials and/or GA-CardVersionDetials sheet of the Model-InputOutput Excel file. The versions of each card type must be updated to the latest versions if applicable. No other changes are required. SVAT will ask the operator to update the firmware file of DUT’s model during test.

B. New DB Release.

1. CardVersionDetials/GA-CardVersionDetials sheet of Model-InputOutput Excel file.

Add the information of the new DB to this sheet. Please make sure the Card Description field is in alphabetical order if descriptions are similar with other boards. For example: One card has card description of “DVI/RGB” and the other has “DVI/RGB dual”. The “DVI/RGB” must be in front of the “DVI/RGB dual”.

2. WallDB-Description.txt file

If DB card is NOT for Linx products, add card description to this file.

VII. Update text files in TextFolder\SetupFolder folder on host computer.

SVAT is designed to automatically update some of the files from the network to the host computer every time SVAT runs. Below are the steps to update certain text files from the network to host root\TextFolder\SetupFolder

1. Edit the files that need to be updated and save them with the exact same names and store them in LabVIEW-ControlFilesFolder\TextFolder\RoutineUpdateFiles folder on the network.

2. Clear AAA-TransferLogFile.txt in the folder of step 1 above.

How this works:

- SVAT reads host computer’s name and compares it with the names in AAA-TransferLogFile file. Ignore if it matches, otherwise SVAT will transfer all files in the folder mentioned above to host computer root/SVAT-RGB/TextFolder/SetupFolder.

- SVAT writes host computer’s name to AAA-TransferLogFile.txt to indicate that files have been transferred to this computer so that SVAT will not transfer again next time SVAT runs. This is to save time.

VIII. General Test Rack Setup, Parts and Troubleshooting1. Equipment: The list below is what needed to build a test rack.


Control:- One (1) computer with Windows 7- Wireless mouse and keyboard- One (1) monitor that can display 1080p- Two (2) 4-port or 8-port USB to serial - One (1) 16-port Dell 2816 Ethernet switcherDisplay:- Two (2) MediaWall 4K*- One (1) display monitor Dell U310 or better- One (1) QVHDxV*- One (1) set of speaker with RCA connection

Signal

- One (1) 802R Quantum (Note: RACK1 uses 882 and 804)- One (1) Linx 34 (at least 16x32) *

Output: All DVI/RGB cardInput: 1 Fiber, 1 Cat5

- Two (2) StarTech 16-port VGA splitter- One (1) DSx 300 *- One (1) Fiber Tx *- One (1) TPD Tx *- One (1) Tektronix TSG 130A- One (1) ALTINEX 6-port Svideo/Composite DA- One (1) WD Live TW Media Player

Note: SD-HDI generator is available but not connected to system.* is RGB product.

Rack (From StarTech.com)

- One (1) 42U Rack Part#: 4POSTRACKBK- One (1) Caster Kit 4POSTCASTER- One (1) 4U drawer 4UDRAWER- One (1) 50Pkg M5 cage nuts CABCAGENUTS- One (1) 50Pkg M5 screws CABSCEWS- Three (3) cabinet shelf CABSHELF- One (1) sliding cabinet shelf SLIDESHELFD- Three (3) cable management panel CABLMANAGER2- Two (2) 24 outlets 120V/15 strip RKPW247015

Cables: All cables should be 10ft-15ft long and without ferrite bead (if possible) for easy connection.


2. Test Rack Connections. (Please see image below.)

The connection of the test rack is very simple. It is divided into three groups: Control Lines, Inputs and Outputs.


a. Control Lines: These are serial and TCP communications between host computer and test rack devices including DUT.

b. Inputs: The output each generator type feeds to the input of each DA type to get multiple signals. These are the signals that will feed to DUT’s inputs.

c. Outputs (Display): These are the output signals of the DUT that will feed to the test rack display, two MediaWall 4K. Please refer to WallDisplay.txt file.


Figure: TestRackDiagram


3. Test Rack Troubleshooting

a. No Communication

Serial Communication: (Please see TestRackDiagram figure)

This can be the DUT itself. If not DUT, check the communication lines and make sure that the SystemPortAssignment.txt file matches with the computer serial configuration.

Confirm DUT is powered up and completed the boot up process. Confirm serial communication cable is plugged in. Check SystemPortAssignment.txt file in TextFolder/SetupFolder

to make sure that the ports are assigned correctly because if the computer has been power cycled or the USB to serial box has been re-plugged, the port assignment may change.

Confirm that no other application the uses serial communication is open.

Network Communication: (Please see TestRackDiagram figure)

Confirm there are no duplicate IP Addresses on the network. Confirm Ethernet cable is plugged in. Confirm the Ethernet switcher is on and working. For devices that have no serial communication especially for

DSx, you have to know what IP address it is so that you can enter it correctly. Default IP address is 192.168.1.200, but it will be changed during test. If you stop the test before it is changed back to default, the DSx now has a different IP Address (for now it is 192.168.1.221 or 192.168.1.220).

DUT might need more time to complete the boot up process Delete all cookies and history of the browser (explorer) DUT’s IP address might not be on the same subnet of the

system

b. No Outputs

This can be the DUT itself.

If not DUT:

Check all cables. Check if source is present.

Connect source directly to monitor Check FirstWall and SecondWall window enable command

(winen) to make sure that certain windows must be enabled.


Check FirstWall and SecondWall “winsrc” command to make sure that the intake are corresponding to what the DUT is taking in.

Make sure that monitor is turn to the correct input source. Might need to power cycle the RackLinxDA of the test rack. Make sure that the RackLinxDA routes correctly

1 or 2 route to allIf current output is Fiber, 5 routes to 32If current output is HDMI, 10 routes to 32If current output is HDBT, 3 routes to 32If current output is Composite, 11 routes to 32

IX. Test record and backupThe test records are saved in one central location for all test racks. All test racks are able to

access to it. As of this time, there is no backup system in place yet. The backup plan is to automatically save the same test records at a second location, a drive or a USB.

The RGB-SVAT folder on the development computer is the folder that should be used for duplication of other test rack. The up to date copy of this folder is always saved on a separate USB in case if this computer crashes.

X. MediaWall V and Its Test RackEven though the Media Wall V has its own test rack, but this model uses the same test

mechanism as of other model, so all the above topics are also applied to the MediaWall V. Since there will be no particular TPI for this model therefore instructions, illustration and reference pictures, and general troubleshooting guides will be available to guide the test operator throughout the test process. There is a Board ID Enter Process which the test operator must follow all the instructions step by step precisely. Once the IE browser is open, the test operator must not touch or move the mouse and do not press any key on the keyboard. The MediaWall V test rack also has the ability to detect if required cables are connected to the DUT or not. If not, system will alert the test operator the port type and port number(s) that don’t have correct cable(s) connected. Test will not continue unless all required port(s) are satisfied.

1. Power-Up MediaWall V At MediaWall V Test RackThe MediaWall test rack has two power cables, Power Cable A and Power Cable B. They

are controlled by a device called Data Probe. The operator has to use Power Cable A and Power Cable B for power supply A and power supply B of the MediaWall V respectively. If the DUT has only ONE power supply inserted, the test operator must use Power Cable A to power up the DUT. If the test operator doesn’t use Power Cable A for power supply A, the Two Power Supply test case will not work correctly and/or MediaWall V might not boot up at all.


Just like testing any other model, the test operator has to power up the MediaWall V unit and wait until it completes the boot up process and a provided serial communication cable must be connected to the serial communication connector before running test. The MediaWall V takes around 15 seconds to power down. Please DO NOT remove the power cable(s) from the unit right away after the power switched has turned to the OFF position. You have to wait until the front panel LCD shuts down, black color, before removing the power cable(s). The MediaWall V might be crashed if power cabl(s) is removed too early before it completes its shutdown process.

2. Instructions, Illustration, Reference Pictures and General Troubleshooting Guidesa. Instructions:

There are two types of instructions, popup instructions and picture-attached instructions. The popup instructions will be popping up to ask the test operator to perform a task or tasks. The pop up window will be closed by itself or the test operator has to click the “OK” or “Close” button to close the window. The picture-attached instructions or explanations will only be displayed when the operator view the illustration or reference pictures. Each picture has its own instructions which will be displayed in the Instruction Box to the very top of the Illustration Window. There are might be some additional instructions on the picture itself. The test operator must follow all instructions step by step and please DO NOT bypass any steps.

b. Illustration and Reference Pictures:In addition to instructions, illustration pictures will help the operator to understand and follow the tasks easier. There are test results that test rack cannot check automatically therefore test rack will ask operator to verify the results. The reference pictures are the guidance for the operator to compare the test results to.

c. Viewing illustration and Reference PicturesIf there are illustration and/or reference pictures available, a Pictures button will be visible on the active screen. The Illustration Window will pop up once the Pictures button is clicked. The first picture and its instructions will be presented. The screenshot below shows how the Illustration Window looks like.The, Next, Back, Last, First buttons will navigate to the next, previous, last and first pictures in the series of the current set of illustration pictures, respectively. Click the “Close” or “Done” button to close the Illustration Window.

d. View General Troubleshooting GuidesJust like the Illustration Pictures, if General Troubleshooting Guides are available, the “HELP” button will be visible on the current active window. A text box will be visible once the “HELP” button is clicked. Remember, the guides are only meant for some quick check or verification before the test operator decides to fail the DUT. There is NO down to component level troubleshooting guide.


3. Board ID Enter ProcessFor this process to work correctly, the test operator must enter (scan) the S/Ns

into each highlighted text box. The picture below shows all the boards and their S/Ns which already had been entered. The scanning order is from Left to Right and Top to Bottom. The first (highlighted) text box will be highlighted. System will automatically jump to the next box (to the right) after a serial number has been scanned in the previous box. Click “RE-SCAN” (has been changed to Clear All) button to start over. The test operator can also start any where by double click at the wanted text box. Click “DONE” after all S/Ns have been scanned in. Click “EXIT” button to skip this process. Remember, the number of the text boxes might be different than this picture because of different configuration. A tool (folder called mfg_setup) is required for this to work. This special tool is provided by the Engineering Dept. This folder must be loaded to location <root>\SVAT-RGB folder.


There is also a second window just like the above, but it is for board revision. Each field will take two revisions (Engineer revision and Board revision) and they are separated by a comma. If no comma, system will take it as Board revision only.

4. Thumb Nail TestThumbnail is a quick way to show the stage: configuration, wall layout and the image of the signal of the MediaWall V. This is part of the View Controller application. The application software of the View Controller must be installed. A physical setup must be done for this to work. For easy testing, wall layout of 1by3 and ONE window is the setup.

Three shortcuts (above pictures, names must be same as in pictures) must be on Desktop. Below is the automatic Thumb Nail test sequence.a. Launch Configure Tomcat

- This process will take around 10 seconds. The START button will always be clicked regardless of it Tomcat application has been started or not.

b. Launch ThumNail Setup

- This process will take around 3 seconds. The IP Address of 127.0.0.1 will be entered automatically.

c. Launch VIEW for MediaWall V

- This process will take around 20 seconds. The user name and password will be entered automatically. The monitor should be displaying the image below if the VIEW for MediaWall V is launched correctly.


d. Testing

- System will automatically take the screen shot of the display (the image above) and compare it to a reference image. If matches, system will change the image, take screen shot and compare to another reference image. The image below is the second image.

In the event of a failure (current image and reference not match) is detected, system will display the current and the reference image to see the differences. A Pass/Fail/Retest window will also pop for the test operator to select. If fail, always try to select “Re-Run Test Case” for a second time because the View Controller application freezes sometimes.

5. Media Wall V Test Racka. Equipment

Hardware:- Rack- MediaWall V 18-Input, 6-Output-

b. Diagram

XI. Voltage Measurement StationThe Voltage Measurement Station is designed for measuring the voltages of individual boards

and for some cases; the station might also be used for programming.

1. Voltage Measurementa. Document Setup


There are three important files/folders to make this station works. 1: VoltageRecordFile.xlsx; 2: Voltage_Check_Illustration_Folder; 3: DB-VoltageLocation worksheet in the Model-InputOutput.xlsx file.

VoltageRecordFile:


svat user guide

Documents