Configure the OrgDaten module user box, including WTB tabs, tab page variables, and selection lists for input fields. Define mapping, data storage containers, metadata, default values, and STMC module integration settings.

Orgdaten_Config

The group of type Initialization of variables contains the common configuration values for the variables.

OrgDaten_user.WTB

The WTB tabs in the OrgDaten module user box are listed in rows. Each line corresponds to one tab. You can currently add up to 10 tabs (and therefore 10 lines).

Tab Page Content WTBs

The content displayed on the tab pages in the user box of the OrgDaten module must be configured in tables of type OrgDaten_Daten or OrgDaten_Data_Ex.

Figure 49. Configuration of Variables in the OrgDaten_Daten Table


In OrgDaten, you can configure the user box input fields for integer and float variables. To do this, you need the table type OrgDaten_Data_EX. The hot change function isn’t currently available for text variables.

Figure 50. Configuration of Variables in the OrgDaten_Daten_Ex Table


Use of a Selection List for Input Fields

To adjust an entry using the selection list, you must enter the selection list in the Selectlist [WTB] column.

Figure 51. Inserting a Selection List for an Input Field


Choose the 2-column table type Combobox for the selection list.

Figure 52. Example of the Combobox Table Type as Selection List
Figure 53. Resulting Tab in the Userbox


Mapping

The state machine must be part of the test. Fill out the mapping tables (OrgDaten_Mapping.OUT.WTB) as follows:

Source Destination
OrgDaten_testXplorer.ACT TXCtl_TXPL.ACT
OrgDaten_testXplorer.CTL TXCtl_TXPL.CTL

In the interface that contains the input variables, map them as follows:

Source Destination
TXCtl_TXPL.STS OrgDaten_testXplorer.STS

Data Storage

  • Data storage unit generator—Create data storage units automatically in PAbasic OrgDaten_TNG.G. You must write the data storage unit to the norm name OrgDaten_TNG.TXT.
  • Deleting data storage units—When you delete a data storage unit, all measurement data and the corresponding saved files are moved to the recycle bin in a sav0 directory. You can adjust the parameters of the recycle bin path in the base module Data2Delete (D2D). You can delete the recycle bin manually or automatically. You can configure automatic deletion in the PCU Configuration tool.
  • Data storage unit (display name)—The term Container in the Userbox can be customized for your application. To do this, initialize the variable OrgDaten_Container_MULTIL.TXT with the appropriate value in a variable initialization. You can find variable initialization in the Module configuration.

    The variable is initialized with Container by default. If you enter Order number instead, the display in the userbox changes

    Figure 54. Initialization Value Container and Order Number

Defining Meta Data for Data Storage

Depending on the data storage, you can use a two-column or a three-column value table to define metadata. In each case you must enter your data in the value table Orgdaten_Datenablage.WTB.

Fill out the columns of this value table as follows:

No. Value Description
1 Constant text or norm name Mandatory: label of the data (e.g.,: "User name", TLN_DUT_ level.TXT.CA, ...)
2 Constant text or norm name Mandatory: value (e.g., "Smith", CUST_DeviceName.TXT, ...)
3 Constant text or norm name Optional: property group (e.g., "Device data", CUST_Property1.TXT,...)

If the system supports property groups and you use a three-column table type, the system assigns the default property group name Header-Data if you leave the third column empty.

Default Values

You can define default data. When you close a container, the system resets any values the user changed back to their default values.

The default values are stored in a two-column table in Module configuration. Fill in the columns as shown in the following table.

Column Value Description
1 INT / FLOAT /TXT Default value to which the variable will be reset.
2 Norm name Norm name of the variable that will be reset.
Figure 55. Example of a Table with Default Values


Integration into the STMC Module

This section lists the standard names and values to use for the integration.

Table 31. Registration of the Module OrgDaten
Feature Norm Name Value
STMC Module ID CV_STMC_Orgdaten.ID 10101
Automatic Registration of (Value) Table Orgdaten_STMC.WTB

You can use the OrgDaten module in the STMC module if you create a selection list (for example, Container).

The number in the Value column is the value of the CV_STMC_OrgDaten.ID variable. In the Selection column, enter a name for the selection.

Figure 56. Example for the Integration of the OrgDaten Module in the STMC Module


The next section describes the properties of this selection list.

Selection List Container

Define the selection list Container as a simple selection list. The list can include the following two rows. The text in the Selection column appears in the sequence table:

Value Selection Description
1 Create container Creates and opens a container
2 Close container Closes a container.

Scenarios for Handling the Container

This section describes the different options for handling the opening and closing of containers in various situations.

All data for the same test order is stored in a single container. The container opens when the test order starts and closes when the test order ends. The following figure shows the default container behavior.

Figure 57. Default Behavior

The container opens automatically when you load a test. If you unload the test and resume it later, the system stores the files in the same container. The container closes when the test order is complete. The following figure shows what happens when you unload and then resume a test.

Figure 58. Behavior When a Test is Unloaded and Continued

The container opens automatically when you load an existing test. If no container exists, or if the container didn’t open when you activated manual or automatic mode, you can select whether there will be:

  • A warning
  • Inhibit to proceed
  • No hint

In this case, you must parameterize the selected behavior in your application’s test case.

Figure 59. Behavior when a Container is Closed


You can use an action command in the sequence table to open or close the container.

Figure 60. Container Handling in Automatic Mode


You can unload a test, and the container closes. If you interrupt this test order and load another test, the system writes the data to the container for the newly loaded test. When you later continue the interrupted test, the system can write the data to the original container for that test.

Figure 61. Interrupted and Later Continued Test