User:Jrkenti/Sandbox

Hi Sean, This is an example of a WIKI work instruction i had made back in January.

Jrkenti (talk) 17:27, 14 March 2022 (UTC) Jrkenti (talk) 17:27, 14 March 2022 (UTC) Jrkenti (talk) 02:08, 17 March 2022 (UTC) Jrkenti (talk) 22:08, 16 March 2022 (UTC)

Scope

This test equipment is used to test all Klaran devices. The use of the software is consistent across many other work instructions.

Purpose

This WI is designed just to teach the user to operate the software on the Klaran test stations

References

NOTE for January 30, 2019.  This section will be completely unnecessary.  
Where ever the documents are mentioned, they can be linked.
SAF-POL-012: Personal Protective Equipment Policy
TST-WI-042: Klaran Daily Verification

Definitions

NOTE for January 30, 2019.  This section will be completely unnecessary.  
Whenever words need definitions they can have be a link to their own page.
Digital Traveler – a csv file, a list of serial numbers used to track the data from each test.  Most Digital Travelers get used once and only once (except when groups of devices are tested more then once: golden devices and parts that get pre-tested and post-tested).

Safety

• NOTE for Jan 30 2019. This section should be replaced by an 'info box' in the upper right corner of the page.

Responsibilities

Lead Engineer ensures the procedure is operable, and addresses irregularities that arise during its use. The lead engineer ensures the station is operating as per these instructions. Technician or operator must follow this work instruction. The technician must record any process deviations and note any failures. The technician must notify lead Engineer of any process deviations or failures.

Process

Turn on the Computer and Start the Software

1. If not already on, turn on the computer and log in. User name and password are listed near each machine's monitor.
   1. If the computer was off, several networking issues may arise. Ask an engineer to make sure that the system is working properly.
   2. Getting the software to recognize mapped drive shortcuts requires “mapping” the mapped drive from within the software: this can be done from the popup window that appears when the “Import List” button is clicked from the Operation page.
2. If not already open, load software by double clicking on CA-13739-LLA – Shortcut on desktop. Select ‘Run’ or ‘Yes’ at the ‘administrator’ prompt.
   1. If any errors occur while loading the software, contact an engineer.
   2. Proceed to the verification of settings

Verify all the Settings and Links

1. Select the Operation button in the Main window.
2. Verify Calibration on the sticker on the LabSphere matches the calibration file. (near the lower left of the operation page of the software)
   1. The date on the sticker should be 1 year ahead of the date in the calibration name.
   2. If it does not match, consult with an engineer.
3. Verify the Test Program XML is the correct XML for the testing the selected parts. (near the upper left of the operation page of the software)
   1. Use “K2Production.xml” to test K2 parts
   2. Use “DetroitProduction.xml” to test Detroit parts
   3. Use “OPT235.xml” to test Optan235 parts
   4. Use a “…TDR.xml” to test parts according to any open TRD
   5. Use a “…CRB.xml” to test parts according to any open CRB
   6. If the selected XML does not match the XML required for testing the selected parts, consult with an engineer.
4. Verify that the station you are about to use has had its daily verification performed.
   1. A csv file, generated today, will exist in that station’s “To Load” folder with the word “golden” in the file name.
   2. If no such file exists, perform the daily verification before any other testing (TST-WI-042).
5. All other computer files necessary for using these systems can be found in the shortcut on the desktop.
6. Select a test level (golden is for daily verification, swr is for special work requests, pre and post are for production testing (before and after burn in), exp is for experimentation and system testing).
7. Select an operator designator (if your initials are on the list, choose your initials, otherwise choose a generic operator and tell an engineer to add you to the list).
8. Click on ‘Import List’ to select a digital traveler. (Every group of devices has a unique traveler. Travelers are specific to each group of devices from each build lot. Golden devices have special travelers. TDR & SWR parts also have special travelers.)

Test Devices

1. Using the vacuum tweezers, and following all safety procedures, remove the first part from tray and load it into the testing fixture, being sure to orient it correctly. See Figure 1.

   

   Figure 1: On the left, a Detroit device, and on the right, a K2 device correctly oriented in their respective test fixtures. This is obviously the wrong image.

2. Using the vacuum tweezers, and following all safety procedures, remove the first part from tray and load it into the testing fixture, being sure to orient it correctly. See Figure 2.

   

   Figure 2: On the left, a Detroit device, and on the right, a K2 device correctly oriented in their respective test fixtures. This is obviously the wrong image.

   1. For Detroit devices, the Zener Diode (the small structure within the device) should be sitting roughly 90 degrees counter-clockwise from the positive terminal, and roughly 90 degrees clockwise from the negative terminal.
   2. For K2 devices, the Zener Diode should be sitting roughly 90 degrees clockwise from the positive terminal and roughly 90 degrees counterclockwise from the negative terminal.
   3. Be certain the device is seated properly and will not get pinched when the lid is closed.
3. Press Run Single button in software – wait a moment until it completes.
4. If the test is a success proceed to the next step, otherwise continue with this step.
   1. Devices that test successfully will produce a popup window with a bin ID that matches a bin for that type of device. This id should also be on a label on the light up board (and it should be the one lit up).
   2. Devices that test “no bins match” are “Non Conforming”. Proceed to the next step.
   3. Devices that test “Electrically Good” or “Electrically Bad” should be handled as indicated by an engineer.
   4. Devices that test “SHORT” or “OPEN” need to be retested: Dismiss the popup window and reseat the device in the testing fixture (remove it and put it back, or just wiggle it a little bit). Also, clear any debris from the test holder that may be interfering with the proper testing of the device. Return to the previous step by “retesting” the device when presented with that option by the software. Devices that test this way several times are “Non Conforming”. CAUTION: if several devices test this way in a row, consult with an engineer.
5. Unload the device from the fixture.
   1. For post testing, place the device in the bin indicated by the popup window and light-up board. NOTE: THIS SHOULD BE REMOVED: (‘Go ahead’ parts will probably later be returned to the original ‘Go Ahead’ waffle pack, organized by bin, with little bin labels.)
   2. For pre testing, place the device back into the waffle pack so it can be ready to be burned-in. Certain types of nonconforming devices will need to be excluded from BurnIn, consult with an area lead.
   3. For golden testing, place the device back in the golden device box, in the same spot it came from.
   4. For swr testing, consult the swr instructions to determine what to do with the tested parts.
6. Dismiss the popup window and “Continue” to the next device when presented with that option by the software.
7. Repeat steps, starting with loading the next device, for all parts to be tested.
   1. There is no need to adjust the operator field, the traveler field, or the test level field between each device.

Clean Up

1. When you have finished a given traveler, and are not ready to start another, close the software by clicking ‘Log Out’ and then clicking on the “X” in the upper right of the window.
2. Cover all open waffle packs with labeled lids.
3. Move closed waffle packs to their appropriate locations.
4. Alert an engineer if you observed any anomalous behavior by the software.