Log-on to the System Controller and Guru
- First, let us explore the Guru bar and learn how to access Apps and Short Cuts. Next we can examine the OS/2 command line interface (similar to DOS) for manipulating and compressing files.
- 1) Log on to the system by clicking Logon
2) Click on the Apps button to open the Select Application window.
3) Click on Guru Browser button to start exploring objects in Guru.
4) Click on the Value drop down list (secont line below the ObjClass selection in Key 1) to explore the various objects available. Here are some of the most common object classes:
For tester definition, you need to look at the following object classes in Guru:
For Device definition, you need to look at RiDeviceDef object class.
For DIB definition, you need to look at RiDibDef and RiDevicePinsDef object class.
For DIB Cal, you need to look at RiDibCal object class.
For Fixture definition, you need to look at RiFixtureDef object class.
For Fixture Cal, you need to look at RiFixtureCal object class.
Look for the following object classes:
- RiTesterDef ( Tester Calibration and Configuration ) What's the system name?
RiTestPlan ( Device Test Plans ) Name some...............?
RiDeviceDef ( Device Under Test ) Name one ...............?
RiDibDef ( Device Interface Board ) Are there any available..................?
RiFixtureDef ( Fixture ) Is there a Cal Fixture................?
- The OS/2 command line interface is very similar to the DOS command line interface and uses the same command syntax. Open a command line interface window from the menu bar.
1) Practice exploring the directories by first changing the drive to D: with the command "D:" enter. Now change the directory with the command "CD RiApps" Enter. Browse the directories with the "DIR" Command and finding the file "student.usr" in the User directory. The syntax for the zip utilities are command then resultant zip file name then the file name you wish to compress.
2) Now lets copy the zip file to the root directory D by typing the command "copy student.zip D:\ " This will copy the named file to the drive and directory path called out.
3) Next create a new sub-directory file folder by changing to the root directory: "cd .." (moves back one directory in a tree) and then typing "MD ..\Junk". This will create a subdirectory under drive D:\ called Junk.
4) Now close the OS/2 Command window by typing "EXIT"
NOTE: Any time you send a file by email or move it by a removable media, first zip it to maintain all the file's extended attributes, like long file names and properties.
- Locate the desktop icon named Assistance Center and double click to open it. Then select the Tasks folder inside and again double click to show the available tasks. Select the OS/2 Warp Desktop Guide to explore the features of the OS/2 operating system.
Opening the RI System Software Application
- The Cassini application is run from Guru.
- 1) Click Login at the top of the Guru Bar.
2) Open Cassini by clicking on Apps or Short Cuts (if available)
3) The System Controller displays the main Cassini window.
- The Cassini window provides three basic functions. It provides the Log-on user interface, it offers the user access to the top level RI application windows and displays messages sent by the other RI application windows to the user. The title bar of the message window says "Cassini <SERIAL NUMBER> <VERISON>". The <SERIAL NUMBER> is 8 digits and the <VERSION> is described as a 3 digit number.
The Test System offers the user several levels of accessibility to the System Software depending on the type of user (system administrator, system programmer, test plan developer, test operator, etc.) To obtain the appropriate level of access the user must first log-on to Guru with their user name and password or use one of the standard access names and passwords. If you do not log-on, the System Software will restrict your access level. You will not be able to access any program management, program generation, program execution or system administration functions. Since we are going to be creating new tests in this lab, we will need the access required by a test engineer.
The RI System Software provides custom Test Executives for testing parts. The Test Executive loads and runs Test Plans and Test Limits. The procedure for starting-up the Test System and running a Test Executive is described below.
1) Click on the System button. Click on the Package Execs button.
2) The System Computer will open the Package Test Execs Container Window.
3) Open the Test Executive object "Demo" by clicking on the Demo button.
4) The Cassini application loads the test plans, the limit files and the custom Test Executive that was created by the Instructor.
The Test Executive Editor Window provides three entry fields for entering the Lot name or number, the Sub Lot name or number, and the part number for the Next Part you want to test. (The next part number default to 1 if you do not enter a value. The Lot and Sub Lot names will remain blank.) Practice selecting and entering names in the Lot and Sub Lot entry fields and selecting and entering a number for the next part to be tested.
The Test Executive provides number of data display for testing parts. To open the Data Viewer Window, place the mouse pointer on the Test Executive Editor window's menu bar and click on the View then selected the desired viewer from the menu.
You have finished all of the hard parts. Now you can run the test plans and limit files you selected with your custom test executive.
- 1) To start testing select the green Start button on the custom Test Executive you have created. If you have not activated a handler the software will instruct you to select a handler. Follow the procedure displayed by the system computer and activate the Simulated Handler.
2) Each time a new part is tested, the Test Executive will update the test summary data and the summary plots in the Data Viewers you opened.
3) To stop testing select the red Stop button or the red Pause button.
4) To start testing again select the green Start button again or select the green Resume button to resume testing.
5) Select the red Stop button when you are finished testing.
6) Close the Data Viewers you have opened by placing the mouse pointer on the down arrow in the upper left corner of each Data Viewer Window and double clicking mouse button 1. Repeat this process for the other Data Viewer Windows.
7) Close the Test Executive Editor Window by placing the mouse pointer on the down arrow in the upper left corner of the Test Executive Editor Window and double clicking mouse button 1.
8) Continue experimenting with the Test Exec, try out the features and different data viewing options. Can you find a way to easily display the underlying test program?