TABLE OF FIGURES... II A - DISCUSSION...1 B - CONFIGURATION...5. B.1 - Setup Dialog... 5 B.2 - Description... 6 B.3 - Controls...

Transcription

1 Radiant Technologies, Inc. 2835D Pan American Freeway NE Albuquerque, NM Tel: Fax: Table of Contents TABLE OF FIGURES... II A - DISCUSSION...1 B - CONFIGURATION...5 B.1 - Setup Dialog... 5 B.2 - Description... 6 B.3 - Controls... 6 C - EXECUTION, ARCHIVE RECALL AND EXPORTING...8 C - EXECUTION, ARCHIVE RECALL AND EXPORTING...8 C.1 - Execution... 8 C.2 - Archive Recall... 8 C.3 Admin Info C.4 Test Definition Graph C.5 Exporting C.6 - Controls C.7 - Discussion D USER VARIABLES...20 E - CHANGE AND VERSION RECORD...21 I

2 Table of Figures Figure A.1 - Branching on Multiple Logic Conditions Figure A.2 - Example Using the Automatic Branch Abort Figure B.1 - Automatic Branch Abort Task Configuration Dialog Figure C Recall the Task from the Archive Figure C Automatic Branch Abort Task Configuration Recalled from the DataSet Archive Figure C Automatic Branch Abort Task Execution Results Figure C Admin Info Subdialog Figure C Automatic Branch Abort Task Test Definition Graph Text Output Figure C Export Dialog Figure C Standard Windows File Browser Dialog Figure C Export Configuration Dialog - Printer Option Figure C Standard Windows Printer Configuration Dialog Figure C Sample Automatic Branch Abort Task Text Export File Figure C Sample Automatic Branch Abort Task Excel Export Output Figure C Sample Automatic Branch Abort Task Word Export Output II

3 Radiant Technologies, Inc. 2835D Pan American Freeway NE Albuquerque, NM Tel: Fax: VII Tasks A. Program Control 1. Branch Tasks ii. Auto Branch Abort Task A - Discussion The Automatic Branch Abort Task is very similar to the Automatic Exit Task. There are two primary differences. The first is that the Automatic Branch Abort must be programmed into a Branch Loop. (The Task may be programmed outside a Branch Loop but will not serve any useful purpose.) The second difference is that the Task does not terminate the Test Definition, but may terminate the continued looping of the Branch Loop. When the Task executes, it performs a comparison between a User Variable and the Task's Branch Logic Condition in an inverse fashion to the Branch Task itself. (Inverse because the Branch Task uses a successful comparison to Branch and the Branch Abort uses the successful comparison to stop Branching.) If the proper condition is met, a flag is set to tell the Branch Task not to branch regardless of its Branch Logic Condition/User Variable comparison. Figure A.1 shows the cooperative operation of the Branch Abort Task and the Branch Task. 1

4 Figure A.1 - Branching on Multiple Logic Conditions. 1

5 It is important to note that multiple Auto Branch Abort Tasks may be programmed usefully into a single Branch Loop. If the abort condition is met, the Branch Abort flag will be set by any of the Tasks. However, if the abort condition is not met, the Task will not clear the abort flag. Thus any Auto Branch Abort Task can pass an abort signal through other Tasks to the Branch Task. This make the Auto Branch Abort Task a very useful tool since it allows the Branching to be dependent on any number of variables. Consider the following example: Figure A.2 - Example Using the Automatic Branch Abort. This example modifies the standard Fatigue example shown in the Tutorials. Task 1 - "Start Prompt" - This is a Pause Task that prompts the user to start the experiment. Task 2 - "Baseline PUND" - This is a PUND that executes once. It provides a baseline, pre-stress measurement of the sample. Task 3 - "Fatigue Stress" - This is a Waveform Task set to stress the sample and adjust its duration as the Test Definition loops. This is the Branch Target. Task 4 - "Fatigue Measurement PUND" - A PUND Task that repeatedly measures the progress of Fatigue after each stress period. Task 5 - "Fatigue Progress" - This is a Pass-Through Filter Task that records and displays P* and other PUND parameters during the Fatigue execution. It is set to Single-Point mode. Task 6 - "Check Overtemp" - The experimenter is concerned that the ambient laboratory temperature may exceed 35 ºC, which would taint the results. The 2

6 experiment itself does not introduce any heat but other equipment in the vicinity may do so. A thermal detection device has its detector placed in proximity to the sample and is connected to the Precision Tester through the GPIB interface. The device is set to 35 C. Below that temperature it will report the text "Normal" when queried. Over that temperature it will report "Overtemp". A Generic GPIB Task is placed in the Test Definition to query the thermal detector. Task 7 - "Overtemp Abort" - An Automatic Branch Abort Task is added that compares the User Variable "GPIB Response String" to the text string "Overtemp". If the strings are equal it sets the abort flag. Task 8 - P* < 20.0" - The sample normal shows P* of ~50.0 µc/cm 2 for the test voltage. A value that falls below 20.0 µc/cm 2 will be considered sufficient to characterize the Fatigue properties of the sample. A second Automatic Branch Abort Task is used to look for this condition and stop the experiment. Task 9 - "Fatigue Loop" - The Branch Task. This Task is set to terminate after 50 iterations if it does not see a Branch Abort flag. If P* remains above 20.0 µc/cm2 for that period, the sample can be presumed to be Fatigue free. Table A.1 shows a variety of conditions that are tested and the resulting response by the Branch Task. Note that Branch Looping continues only in the first entry of the table. Each of the subsequent entries represents one or more conditions that cause branching to terminate. Any of these entries may follow sequentially from the first entry, but they are independent of each other. The table does not represent a sequence of activity since any of the terminating conditions would cause execution to leave the table. The last four entries in the table represent normal Branch Loop termination at Loop Counter = 51, regardless of the state of the loop abort flag. Normal loop conditions are indicated in green. Loop terminating conditions are indicated in red. The presence of any loop terminating condition will cause the loop to terminate. In other words, conditions that do not cause the abort flag to be set will not reset the abort flag if it is set. Temperature C P* (µc/cm 2 ) Loop Condition Branches Count Temperature: Normal - Abort Not Set Yes P*: Normal - Abort Not Set Loop Count: Continue Temperature: Out of Range - Abort Set No P*: Normal - Abort Not Set Loop Count: Continue Temperature: Normal - Abort Not Set No P*: Out of Range - Abort Set Loop Count: Continue Temperature: Out of Range - Abort Set No 3

7 P*: Out of Range - Abort Set Loop Count: Continue Temperature: Normal - Abort Not Set P*: Normal - Abort Not Set Loop Count: Terminate Temperature: Out of Range - Abort Set P*: Normal - Abort Not Set Loop Count: Terminate Temperature: Normal - Abort Not Set P*: Out of Range - Abort Set Loop Count: Terminate Temperature: Out of Range - Abort Set P*: Out of Range - Abort Set Loop Count: Terminate No No No No Changes for Version 4.1.x: Table A.1 - Branch Control Conditions. Comments field extended to 511 characters. Office/Word/Excel 2000 and later export was added. (Office '97 export was elminated.) Moved to Library->Program Control->Branching. 4

8 B - Configuration Task Name: Auto Branch Abort Version: Last Update: 26 February 2009 In QuikLook Menu: No Folder: Program Control Subfolder: Branching Subsubfolder: None Window Name: Automatic Branch Abort Setup Change and Version Record Known Bugs: None User Variables Added: User Variables B.1 - Setup Dialog Figure B.1 - Automatic Branch Abort Task Configuration Dialog. 5

9 B.2 - Description The setup of the Automatic Branch Abort Task is identical to the setup of the Branch Task itself. It must be remembered that the logic assigned to the Branch Abort is used to cause the Branch Task to stop Branching, while the Branch Task configuration set the logic to continue Branching. Here a User Variable is selected, a comparison type assigned and a limit value specified. A disabled text control shows the logic as it is assigned. Changes for Version 4.1.x: Comments field extended to 511 characters. B.3 - Controls Name Type Default Description Task Name Text BA2:# This serves as a root identifier for this instance of the Automatic Branch Abort Task. The Task will be identified with this value in the Editor and the Current Test Definition (CTD). Executed Tasks will be displayed and stored with this name with a. and an execution number appended to it. Each new instance of the Task within the Editor should have a unique Task Name assigned. 30-character limit Abort on True/False Parameter to Compare Comparison Radio Button List Box List Box Abort on True Toggling logic buttons. One and only one of these choices may be selected. Under normal and default conditions Abort on True is selected telling the Task to set the Abort flag if the specified condition is met. The logic may be inverted by selecting Abort on False so that the Abort flag will be set if the condition is NOT met. Adjusting this selection will be reflected in the logic text of the disabled text control. Variable This box lists all available User Variables. The list is variable showing only User Variables that have been added by Tasks that have been accessed at some time since the program has been started. One variable must be selected. Each User Variable has a type. Depending on the type of the selected variable. One of Integer, Text, Real or Boolean will be enabled while the others are disabled. Adjusting this selection will be reflected in the logic text of the disabled text control. "=" Selects one of several comparison types to be made between the selected User Variable and the assigned parameter limit. Adjusting this selection will be reflected in the logic text of the disabled text control. Integer Integer 0 If the User Variable selected in Parameter to Compare is an integer, this control is enabled. Otherwise it is disabled. Enter a limit to which the selected User Variable is compared. Adjusting this selection will be reflected in the logic text of the disabled text control. Text Text "" If the User Variable selected in Parameter to Compare is a text string, this control is enabled. Otherwise it is disabled. Enter a limit to which the selected User Variable is compared. Adjusting this selection will be reflected in the logic text of the disabled text control. Real Real 0.0 If the User Variable selected in Parameter to Compare is a real value, this control is enabled. Otherwise it is disabled. Enter a limit to which the selected User Variable is compared. Adjusting this selection will be reflected in the logic text of the disabled text control. 6

10 Boolean List Box true If the User Variable selected in Parameter to Compare is a Boolean value, this control is enabled. Otherwise it is disabled. Enter a state to which the selected User Variable is compared. Normally the value in Comparison should be set to "=" or "NOT =" when the User Variable is a Boolean (unlabeled) Text Variable Read-Only. This control gives a plain-english description of the condition that will cause the Task to set the Branch Abort flag. The text is adjusted by changes to the Abort on True/False, Parameter to Compare, Comparison, Integer, Text, Real and Boolean controls. Comments Text A string of up to 511 characters to be written at the user s discretion. Intended to allow a detailed description of the design decision to include the Automatic Branch Abort Task. Export Help OK Cancel Button Unpressed Disabled during normal configuration. Enabled only on Archive Recall. This button is used to configure and enable the exporting of Task information. Button Unpressed Read this Help page. Button Unpressed Close the configuration dialog. Accept the configured Task values and add the Task to the Test Definition Button Unpressed Close the configuration dialog. Do not add the Task to the list in the Editor. 7

11 C - Execution, Archive Recall and Exporting C.1 - Execution The execution of this Task is visible to the user only as a text message in the status bar (at the lower left of the Vision main window) indicating if the Task aborted or not. This indication will normally be quickly overwritten by the next Task. C.2 - Archive Recall As with all Tasks, the Automatic Branch Abort Task can be recalled from the DataSet Archive to review the Task configuration and the outcome of its execution. To recall, open the desired DataSet and its Archive. Open the appropriate Executed Test Definition (ETD) and its "Data Folder". Finally, double-click on the desired copy of the Automatic Branch Abort Task. 8

12 Figure C Recall the Task from the Archive. First the original configuration dialog appears. The controls show the values as they were configured for the Task execution. Most controls are disabled. The Export control is active and may be used as described below. Help is also available. Admin Info opens a subdialog that provides Vision version and compilation date and Task compilation and execution date information. Cancel will close the dialog. 9

13 Figure C Automatic Branch Abort Task Configuration Recalled from the DataSet Archive. Once the configuration dialog is closed a message box will appear to indicate if the Task allowed Branching to continue or if it was aborted. 10

14 Figure C Automatic Branch Abort Task Execution Results. C.3 Admin Info The Admin Info button shown in Figure C.2.2 has been added to all Tasks as of Version 4.2.x. The button opens one of two subdialogs. Program Tasks, such as the Automatic Branch Abort Task present the dialog of Figure C.3.1. Here, the Vision Version and compilation date along with the Task configuration and execution date and time are presented. This information is of minor value to the user. However, Measurement Tasks also present Tester Type, Tester Serial Number and Driver Version. This information can be useful to RTI in helping the customer troubleshoot problems with Vision and/or the tester. Note that the exporting of this information has also been added to the export target applications as described below. Figure C Admin Info Subdialog. 11

15 C.4 Test Definition Graph Figure C.4.1 shows an example of the Automatic Branch Abort Task text output to a Test Definition Graph in "Standard" text mode. Test Definition Graphing is available by right-clicking in the Editor or DataSet Tab window. Information about the configuration of the Tasks that make up the Test Definition is presented graphically. See the discussion in the main Vision help pages under Tutorial IX or the Main Manual Section XIII. Figure C Automatic Branch Abort Task Test Definition Graph Text Output. C.5 Exporting In order to allow data to be exported from the Task when the Task is recalled from the DataSet Archive, an Export button appears on the recalled configuration dialog. This button is normally disabled, but it is enabled in Archive Regraph as in Figure C.2.2, above. Clicking the button produces the new dialog that appears below. Figure C.5.1 shows the Export configuration dialog in which the "Export Text" option is selected and the browser button enable. Figure C.5.2 shows the browser dialog that opens when the Browse for File Name button is clicked. 12

16 Figure C Export Dialog. Figure C Standard Windows File Browser Dialog. 13

17 C.6 - Controls Name Type Default Description Select List "Print" Select between the "Print", "Export Text", "Export Word" and "Export Option Box Excel" options. This control enables the Browse for File Name button for Line Spacing Left Margin Tab Spacing Browse for File Name File Name all selections except the "Print" option. Integer 100 This control appears when Select Option is set to "Print". Otherwise it is hidden. Increasing or decreasing this value will increase or decrease the vertical spacing of lines on the printed page. Experimentation will fix the value for any given printer. Integer 100 This control appears when Select Option is set to "Print". Otherwise it is hidden. Increasing or decreasing this value will increase or decrease the left start point of text on the printed page. Experimentation will fix the value for any given printer. Integer 200 This control appears when Select Option is set to "Print". Otherwise it is hidden. Increasing or decreasing this value will increase or decrease the horizontal spacing of tabbed sections of text on the printed page. Experimentation will fix the value for any given printer. Button Unpressed This control is enabled for all export options except "Print". For the remaining options, this control must be selected. The browser dialog will appear where a path and file name must be specified for the export output. Text This control is always disabled and cannot be used to specify the file name or path for Text, Word or Excel export. Once the browser is used to select a path and file name, those will be displayed in this control for review. Note that a path and file name MUST be specified for the "Text" and "Vision" export options and may be specified for "Excel" or "Word". Help Button Unpressed Open this help document for review. OK Button Unpressed Accept the configured export and close the dialog. Exporting will occur when the main data regraph dialog is closed. Cancel Button Unpressed Close the export dialog. Do not export. C.7 - Discussion Data can be exported to one of four targets: Printer - Pre-formatted text is sent to the printer when the configuration dialog is closed. Before printing a printer setup dialog will appear (Figure C.7.2), allowing printer options to be adjusted. (The appearance of the dialog will vary from user to user.) With the release of Version 4.1.x, printer text can be formatted from within Vision by adjusting the Line Spacing, Left Margin and Tab Spacing integer values (Figure C.7.1). Experimentation will show the proper settings for all exporting to the attached printer. These controls are hidden unless the printer is specified as the target. 14

18 Figure C Export Configuration Dialog - Printer Option. 15

19 Figure C Standard Windows Printer Configuration Dialog. Text File - Selecting this option enables the Browse for File Name button. Clicking this button will open a standard browser dialog in which a file name and path must be selected. If the file already exists, the output will be appended to existing text. An output file name must be specified for this export. Figure C.7.3 shows a sample of the Automatic Branch Abort Task text export. The information shown in the Admin Info subdialog of Figure C.3.1 has been added to the Text Export output. 16

20 Figure C Sample Automatic Branch Abort Task Text Export File. Excel - Selecting this option enables the Browse for File Name button. Clicking this button will open a standard browser dialog in which a file name and path may be selected. Specifying a file name is optional. However, if specified, a unique file name/file path must be created or an overwrite situation will occur. Data are not appended to existing files. When the recalled configuration dialog is closed, the Excel program will be started and a spread sheet created. When Excel is closed, the data will be written to the specified file name, or the user will be prompted to save if the file is not specified. Office/Excel 2000 or later must be loaded for this option. Office/Excel is not provided with the tester or Vision software. Figure C.7.4 shows a sample of the Automatic Branch Abort Task Excel export. The information shown in the Admin Info subdialog of Figure C.3.1 has been added to the Excel Export output. 17

21 Figure C Sample Automatic Branch Abort Task Excel Export Output. Word - Selecting this option enables the Browse for File Name button. Clicking this button will open a standard browser dialog in which a file name and path may be selected. Specifying a file name is optional. The Word program will be opened and written when the recalled configuration dialog is closed. If a new file name is specified, the document will be saved immediately. If no file name is specified, the user will be prompted to save the documents when closed. Office/Word 2000 or later must be loaded for this option. Office/Word is not provided with the tester or Vision software. The information shown in the Admin Info subdialog 18

22 of Figure C.3.1 has been added to the Text Export output. Figure C Sample Automatic Branch Abort Task Word Export Output. 19

23 Auto B.A.: Branch Aborted Boolean D User Variables True if the Branch Abort Logic Condition was met, otherwise set to False. 20

24 E - Change and Version Record This page specifically lists changes that are visible to the user. Often the software is changed in ways that are not directly apparent to the user. These changes may adjust the version number, in which case they are listed simply as "Internal Changes". Such changes may be indirectly evident in speed and performance improvements or the change of the Task file size. Version November 2001 Corrected an error that caused the Task to fail when it used a real User Variable type for comparison. Version December 2001 Moved the Branch Abort flag from the User Variable list to a system list to reduce clutter. Version March Set to Version for release - 14 March Installed initial Word file export - 26 March SPC. Version October Removed "Eye" icon from all dialogs - 4 October SPC. 2. Added Tool Tips - 11 November SPC. 3. Office 2000 Exporting - 2 February SPC. 4. User Variable Update - 8 April SPC. 5. Added print export characters position control variables for vertical line position, left margin and tab length. 31 July SPC. 6. Caused the Word program to shut down after Office '97 exporting from the Print/Export Task. This allows the file to be moved or renamed. 5 November 2004 Version May Set to Version for release. 21 May Moved to the "Branching" subfolder. 2 July Added Branch and Filter Target Task icons that show the association with the Branch Task by including a blue dot at the icon lower-left corner, or a Filter Task by including a brown rectangle at the lower-right corner. 2 May Internal Changes. 25 November

25 Version January Set to Version for release. 16 January Removed all references to Office/Word/Excel ' January Eliminated "Excel 2000" and "Word 2000" text from export output. 13 August Version December Set to Version to reflect changes. 9 December Added debug logging calls to facilitate troubleshooting. 9 December Version February Set to Version to match Vision framework version update. 26 February Added Admin Info button and subdialog. 20 July Write Vision Version and compile date to all export targets. 20 July Version November Set to Version to match Vision framework. 5 November Version January Set to Version to match Vision framework. 11 January Version June Set to Version to match Vision framework. 8 June