TestIT:Guide Step Type

9.5.1 Step type

The step type is found in the first section named step. When a step is created, press Save – or Cancel and the step will not be saved.

9.5.1.1 Standard

This is the standard guide step with header, text, image, buttons, and all configuration options.

An example/Instruction:

1. Write the step number
2. Select the standard step type
3. Select an image
4. Write the value of the OK button text (e.g. OK), and the NOK button text (e.g. Cancel)
5. Press Save

9.5.1.2 Scan

This is the standard functionality and a scan section. If the step type is scan, the OK button is set to go to next.

Configuration:

1. Scanned value – select a symbol name from the list
2. Go to next on scan – select Yes or No

9.5.1.3 Unique ID

This is a step which runs in the background. It will use a unique ID device to set a string symbol. It will also have the option to set the value as object ID in the running guide. If object ID is selected, then max 50 characters.

Configuration:

1. Write the unique ID
2. Select the symbol
3. Mark ‘set as object ID’, if it is wanted

9.5.1.4 Scan Object ID

This is the standard functionality and a scan section. The scanned value will be set as object ID in the running guide, so max 50 characters

Configuration:

1. Scanned value – select a symbol name from the list
2. Go to next on scan – select Yes or No

9.5.1.5 Action

This is a step which runs in the background. It will execute commands from the top down. If the order should be changed, just drag the command up or down. Add action steps on the green plus or delete them on the red cross.

Commands:

Commands
Set	Value A will be set
Reset	Value A will be reset
Move	Value C will be moved to Value A (only numbers)
StringMove	Value C will be moved to Value A (only strings)

9.5.1.6 Print

This is a step which runs in the background and will use a printer device. Just select a printer.

9.5.1.7 Stored procedure

This is a step which runs in the background and will use a MSSQL device. Just select a stored procedure.

9.5.1.8 Multi edit

The multi edit step uses a text file to generate several buttons or text areas.

Configuration:

1. Select:
   1. Number of columns
   2. File device (folder device)
   3. Element type (see element type)
   4. File name
   5. Input front size
   6. Input max width
   7. If textbox is only for reading – Yes or No
   8. Element height
   9. Press load text file
   10. Now it is possible to add, edit, and remove elements (see element configuration below)

Element type:

Single Select	Hide textbox, but show button on/off (only number symbols). It will go to next when button is selected.
Multi Select	Hide textbox, but show button on/off (only number symbols).
Multi Edit	Show the textbox, with options to enter text.
Button add	Show the textbox, with option to add (only number symbols).
Button minus	Show the textbox, with option to subtract (only number symbols).
Button add/minus	Show the textbox, with option to add or subtract (only number symbols).

Element configuration:

1. Enter
   1. A value to use in the element
   2. A text to use in the element
   3. A tooltip to use in the element
2. Select a symbol to (NB! If a symbol is selected, it will override the element)
   1. The value
   2. The text
   3. The tooltip

9.5.1.9 Leak device

It is a specialized step to run a leak test device. Currently supported is Nolek S9 and Nolek S10.
It will use a leak test device and execute a defined recipe, and will show the entire measurement on the screen.

Configuration:

1. Setup section
   1. Select the leak testing device to use
   2. Select a symbol with recipe name – a sting symbol which will contain the recipe name
2. Run section
   1. Select the start action
      1. If automatic, the leak device will start as soon as the step is loaded
      2. If not, wait for a button to be selected in TestIT
   2. Select timeout – An INT symbol containing the number of seconds to set as timeout for the measurement
   3. Select activate control leak, which means it will show if it will be possible to show a mistake
3. Done section
   1. Select yes or no if it should continue when it is done
      1. If yes, the guide will continue to the next step when the measurement is done
      2. If no, the step will wait for an OK action

9.5.1.10 Standard with symbols

The same as the standard setup, but with this step type it is possible to select a symbol which makes it possible to change the text while the production is running.

9.5.1.11 Password scan

This is the same as the step type scan, but this is with a password. The text written in the space is not shown while it is written.

9.5.1.12 Guide Executer

Is used to run other guides dynamically, according to a configuration that can be changed during runtime. The guides that are called by the guide executer, are referred to as substeps.

Configuration - symbols:

Configuration symbol	The string symbol that contains the sequence of substeps to execute
Substep Status symbol	The status of the latest called substep (1 = OK, 2 = NOK)
Substep Info ID symbol	Symbol to receive the ID of the latest called substep
Substep Info text symbol	Symbol to receive the info text from the latest substep.

Configuration string:

• The configuration string can contain up to 9 sequence steps (1000, 2000,… 9000),
• Each sequence step can have any number of substeps inside.
• The sequence step to continue to after each substep, can be specified depending on whether the guides went ok or not.
• If the next sequence step doesn’t exist, the sequence will end
• If there are multiple guides in the same sequence, they will be run in the order they are written (from left to right). Unless a guide returns an error, then it will jump directly to the NOK sequence step.

The configuration string is built up as following, with “|” separating each step: StepNumber;GuideName;OKStepNumber;NOKStepNumber|StepNumber2;GuideName2;OKStepNumber2…

Example configuration:

1000;TestGuideA;2000;7000|1000;TestGuideB;2000;7000|2000;TestGuideC;3000;7000|7000;ErrorGuide;9999;9999;

The example configuration generates the following diagram:

When TestGuideA is run successfully, it will continue to the next substep in same sequence (1000 TestGuideB). If TestGuideA returns an error, it will continue to NOK step (7000 ErrorGuide). Since step 3000 and step 9999 does not exist, the sequence will just end when called.

Note: To receive an error from a substep, which will go to the NOK step; there needs to be a Guide Result at the end of the substep that specifies that it was an error.

Alternatively, if the guide does not exist, it will also count as error and go to NOK.

9.5.1.13 Guide Result

Can be used for two purposes.

1. Reporting an error back to a guide executer, signaling that it should go to the NOK step.
2. Adding a result line to the production window

Configuration – General:

1. Tick the Status box If the result is OK, or leave it empty for NOK. Alternatively, tick the Use symbol box, and select a bool symbol.
2. (Optional) Enter an ID number for this result. Alternatively use a symbol with the ID number.
3. Write the Text/Description for this result. Alternatively use a symbol with the text.

Configuration – Add result specific:

1. Use the general configuration
2. Tick Add result
3. Write the result name
4. Type the result unit type. Alternatively use the value of a symbol.
5. Write the minimum of the result. Alternatively use the value of a symbol.
6. Write the maximum of the result. Alternatively use the value of a symbol.
7. Select the result icon that will be displayed.
8. Select if the result should be logged to the database.

9.5.1.14 DataRow Selecter

This is used to display a list of values. It can also be used to select a value from the list during runtime. Alternatively, it can be used as a check list.

Configuration:

1. Tick the Use Device box if you want to receive the data from a device (currently supports MSSQL)
2. Select the stored procedure or the Data symbol that will hold the data.
3. Select the symbol to receive the selected value (can be left empty if using multi select)
4. Tick the Scan box to allow the operator to select value(s) by scanning or typing their name.
5. Tick the Continue on selection box to automatically continue when the operator selects a value. This disables the Multi selection option.
6. (Optional) Select a symbol to hold the default selected value. If the name of any value in the data rows matches this, it will be highlighted/selected by default.
7. Tick the Multi Selection box if multiple rows can be selected at the same time. Multiple selected values will not be saved or stored in the selected row symbol.
8. Tick the Select all required, if the operator must select all rows before being able to continue.

Requirements:

1. When using stored procedure: The procedure must select 2 values per data. Example:

Select Val1,Val2 from table.

1. When using a symbol instead of a stored procedure, the string must be as following: Value1A¨Value1B|Value2A¨Value2B|Value3A¨Value3B

Where Value1A is the name, and Value1B is the description for the first row. The “|” Separates each row. The Description can be empty, but “ ¨ ” must be used after the name.