Test Executive — TestStand(r)

Posted on November 11, 2008 by LV_TS_Test_Engineer_3000_VI
TestStand(TS) is a Test Management Executive()
 
It uses your LabVIEW Test(s) code to connect to TestStand which will then preform limit,reporting,sequence of executing your LabVIEW code.
It has a Built-in LabVIEW adapter(TestStand will pick up on LabVIEW’s input and output) which allow connect to TestStand Variables as needed.
Buitl in Test Type ( Measure Pass Fail, Boolean Pass Fail)
Makes Report(look at the ReportGen_xxx.seq if modification are needed)
Stores data to Database( modify your UUT data Type if you need to provide more then just the serial number ex part number.)
Flow Controls(If-Else ,ForLoops..)
TestStand store UUT infomation,Step Information in variables accessible to programmer and LV code(via TS reference).
Most to the development is done in a TestStand’s sequence Development Editor
TestStand also come with a LabVIEW(r) Operator Interface.
The Operator Interface prevents access to the Development Editor (This is done via the TestStand API). (Note the Operator Interface supplied is a starting point)
The Operator Interface can be used or modifed to fit your needs. (ex. Removing or adding controls and indicator which get updated as TestStand run it sequence)
Most common us for communiction of OI and TS is via UIMessage CallBack Vi in OI and matching PostUIMessage in the TS Sequence.
A matching UIMessage number is used to create actions between the OI with the TS.
 
DO: Have a meeting with the TestStand and LabVIEW developer so both effort can be running in parallel. 
TestStand Developer will Set DMM, Close DMM Route UUToutput,Run Power Supply regulation test ,what to do if it pass or fail.
LabVIEW Developer will create the DMM Driver and DMM(DC,10VRange) type function, Math functions to support  the Power Supply regulation test
 
TestStand also support adapters other then LabVIEW (Please go to the National Instruments site www.ni.com ) for addition information.
LabVIEW and TestStand are products of National Instruments
Posted in Test Sector | Leave a comment

LabVIEW and TestStand Discussion

Posted on November 10, 2008 by LV_TS_Test_Engineer_3000_VI
Ring Type or Enum Type?
Use Enum Type when working with LabVIEW(r) Module to be used in TestStand.
This will allow TestStand to display the Enum "String" in the input/output section.
 
TestStand(r) variables
Local, File, Station
Local Varible   Local.index123
Used when the variable will not be used outside the sequence
 
File Variable    FileGlobal. SelectedOption.
Used when other sequences will be using  this variable
 
Station Global     StationGlobal.UUTtype
When TestStand need to know the variable define for the the particular Station.
 
(Dont forget to copy the  StationGlobal File when copying the sequences to another machine and modify only what need to change)
 
LabVIEW and TestStand are National Instruments’s Products
Posted in Test Sector | Leave a comment

Types of High Level Meeting

Posted on November 10, 2008 by LV_TS_Test_Engineer_3000_VI
The following are typical Top level meeting a Test Engineer will attend.
 
 
  • Kick off Meeting – General Information about Project
  • Preliminary Design Review – (Initial Design Presentation)
  • Critical Design Review  – (Last Review of Design)
  • ATP  –    Acceptance Test Procedure (Validation  of system)
  • Customer Site Setup and Final ATP run( Sign off).
(along the way their will be status, project review,implementation review, and  how-are-you doing, type meetings)
Posted in Test Sector | Leave a comment

Company Organization

Posted on November 10, 2008 by LV_TS_Test_Engineer_3000_VI
Typical Structure in Company Organization.
 
  • Boss— Company Head
  • Manager- works for Boss at a specific Department(ex.Test Equipment Dept).
  • Supervisor- work on specific task assigned by Manager(ex.Project level)
  • Engineer – Works on parts of the specific task of Project and reports to Supervisor(ex.Engineers)

Know your company structure.

If you are an Engineer, you should discuss issues and status with your Supervisor first.

  

Posted in Test Sector | Leave a comment

Information Collected During Automated Testing

Posted on November 10, 2008 by LV_TS_Test_Engineer_3000_VI
The following parameter are typical in Test Report.
 

UUT Part Number(PN)
UUT Serial Number(SN)
TestStation (PartNumber,SerialNumber)
Software (PartNumber,Serial Number, Revision)
Software Serial Number
Operator Name/Number
Description of Test
Test Start Time
Test End Time
Testing Data(for each Test)
    Test Index
    Test Name
    Test Limits
    Test Data/Measurement/Calculated
    Test Unit
    Test Step Results
Overall Test Result
Instrument used (Id String-nomally contains PN SN Firmware,etc)
Test File Name and Location 
Customer Name, Charge Number,Location of Testing etc.

Posted in Test Sector | Leave a comment

Power Supply – Remote Sensing

Posted on November 10, 2008 by LV_TS_Test_Engineer_3000_VI
When I put my power supply to 5V i get 4.7V at the Unit Under Test?
 
This my be an Issue of Wire LOSS Voltage drop.
Power Supplies typically have a Hi and Lo Sense terminal.
The Supply my be locally sense(vendor typically have jumpers at the  power supply connecting the HI Out to HI Sense and Low Out to Low Sense.)
Remove the jumper and with the HI Sense to where the UUT’s Hi Power is connected and the Lo Sense to the where the UUT’s Lo Power is connect.  This will insure that When the supply is set to 5V the UUT see 5V.
Remember that across the Power Supplies Hi and Lo Terminal the voltage will typically be Higher then the Set Voltage as the Power Supply compensates for the wire loss which cause the 0.3v drop in this example.
ALSO CHECK YOUR Wire Gauge of the HI and LO output terminals.
Are you using the correct Gauge wire for your currents?
(READ YOUR POWER SUPPLY Manual for correct remote sensing)
Posted in Test Sector | Leave a comment

PC Controller Configuration

Posted on November 10, 2008 by LV_TS_Test_Engineer_3000_VI
There are many configuration possible using a PC as a controller for Testing.
 
  • PC rack which can hold many PCI card (for a few card a standard Full size PC may be sufficant.)
  • Standard PC which connects to USB Data Aquistion module(Uses just the USB port which is standard on many PC).
  • Standard PC which connects to a PXI Chassis ( Chassis Provides for syncing PXI Card)
  • Standard PC which connects to a Real Time Controller via Ethernet Cable.
Figure below illustration of some configuration above:
 
 
 
 
Posted in Test Sector | Leave a comment

Software Documents

Posted on November 10, 2008 by LV_TS_Test_Engineer_3000_VI
The following is a list of Software Document.
  • Engineering Change Notice (ECN)
  • Software Part Number
  • Software Configuration Document
  • Software Requirement Specification
  • Software Validation Document
  • Software Description Document.
  • Software Operating Instruction
Engineering Change Notice (ECN)
This document provides different departments in the company and also the customer what document are created, reason for changes(or first time release).
Software Part Number
Provides the part number for your software with revision history
Software Configuration Document
Provides a tie-in to the companies configuration Management System(With software it relates to your check-in/checkout product)
Software Requirement Specification
Provides the software requirements for a requested application.(What the program must do?)
Software Validation Document
This document provides a way to validate the software requirements and even system validation in some cases.
Software Description Document
Provides a functional description of the software(main loops , section, description Test result, software architecture,etc)
Software/Station Operating Instruction
Instruction on the use of the application.
The name of the documents used in your company may be different.
Posted in Test Sector | Leave a comment

Test Station Cabinet Layouts

Posted on November 9, 2008 by LV_TS_Test_Engineer_3000_VI
Most popular Test Station cabinets are 19inches wide to accept 19 standard equipment.
 
The high depends on the number of equipment to be included.
 
When the high is limited one can setup a two bay station.
 
Many manufacture provide different depth to accept long equipment or wiring service loop(space for wiring).
 
Companies my have a standard color to be used on all their equipment(check).
 
Below are some sample layout of Single and Two bay Test stations.
 
 
 
 
Posted in Test Sector | Leave a comment

Introduction to ATE space

Posted on November 9, 2008 by LV_TS_Test_Engineer_3000_VI
 
This space was created to provide information on Automated Test Equipment, Test Engineering, and Testing.
I need a place to add items related to my experiences in the Testing Sector to provide other with ideas to research on their own.
 
Some categories will be:
  • Station Layouts
  • Typical Test Data format
  • Test Report Content
  • Discussion on PC Host Setup
  • Discussion on PC Host and RealTime Target
  • Discussion on PC Host and FPGA Target
  • Test Adapter (interconnect)
  • LabVIEW(r) (National Instrument’s product)
  • TestStand(r) (National Instrument’s product)
  • Software Documents
    • Requirements
    • Operation
    • Function Description
    • Configuration Management SW documents
    • Check in/out products
  • Software Architecture Types
    • Event Loop
    • Quene Loop
    • Combo
    • Parallel Loop
  • Typical Company chain of command
  • Equipment Discussion
  • Discrete Componet companies

All information should be researched to meet you own satisfaction.

Posted in Test Sector | 2 Comments