OrgDaten Module Configuration
- Aktualisiert2023-12-28
- 7 Minute(n) Lesezeit
OrgDaten Module Configuration
Orgdaten_Config
The group of type Initialization of variables contains the common configuration values for the variables.
OrgDaten_user.WTB
The WTB tabs that are used in the userbox of the OrgDaten module displayed in the following figures. Each line corresponds to a tab. Currently the entry is limited to a maximum of ten tabs (and therefore ten lines).
Tab Page Content WTBs
The content to be displayed on tab pages in the userbox of the OrgDaten module must be configured in tables either of type OrgDaten_Daten or of type OrgDaten_Data_Ex.
In OrgDaten_v.3.0.3 and later, it is possible to configure the userbox input boxes for integer and float variables. Table type OrgDaten_Data_EX is required for this. The hot change function is currently not possible for text variables.
Use of a Selection List for Input Fields
To be able to adjust an entry using the selection list, the selection list must be entered in column Selectlist [WTB].
Choose the 2-column table type Combobox for the selection list.
Data Transfer
Available transfer variants:
- testXplorer
- testXplorer + ASAM ODS
For the testXplorer integration the state machine OrgDaten_TXCtl.G is used. It is located in the config part of the OrgDaten module. Even if the testXplorer is not used, the state machine has to be part of the test. The mapping tables (OrgDaten_Mapping.OUT.WTB) must be filled out as follows:
| Source | Destination |
|---|---|
| OrgDaten_testXplorer.ACT | TXCtl_TXPL.ACT |
| OrgDaten_testXplorer.CTL | TXCtl_TXPL.CTL |
Data Storage
- Mapping—In the interface containing the incoming variables, map them as
follows:
Source Destination OrgDaten_testXplorer.STS TXCtl_TXPL.STS - If testXplorer is used—The state machine OrgDaten_TXCtl.G has to be edited (macros of TXPL module) in order to control testXplorer actions.
- If testXplorer is not used—If no testXplorer actions are used only the mapping (see above) has to be prepared.
- Data storage unit generator—Data storage units can be formed automatically In PAbasic OrgDaten_TNG.G. The data storage unit must be written to norm name OrgDaten_TNG.TXT.
- Deleting data storage units—When a data storage unit is deleted, all measurement data and the corresponding saved files are move to the sav0 directory in a recycle bin. The parameters of the recycle bin path can be adjusted in the base module Data2Delete (D2D). The recycle bin can be deleted manually or automatically. Automated deletion can be adjusted with the PCU Configuration tool.
- Data storage unit (display name)—The term Container in the
Userbox can be adapted to the customer (alternatives e.g.,: test number, order number,
etc.). To do this the variable OrgDaten_Container_MULTIL.TXT must
be initialized with the appropriate value in a variable initialization. Variable
initialization is in the Module configuration.
Figure 93. Variable initialization in PAconfigurator 
The variable is initialized with Container by default. If Order number is entered instead, the display in the userbox changes
Figure 94. 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 meta data. In each case you must enter your data in the (value) table Orgdaten_Datenablage.WTB.
The columns of this (value) table must be filled out 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 a three-column table type is used and the third column is left empty then the default name for the property group is Header-Data.
Default Values
From OrgDaten module version 3.9.0, it is possible to define default data. If a container is closed then all values that have been changed by the user will be reset to their default values.
The default values are stored in a 2-column table located in the Module configuration. The columns have to be filled as listed 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. |
Integration into the STMC Module
A detailed explanation of how modules can be integrated into the STMC module can be found in the STMC module description. Here you find the norm names and values that are intended to be used for this integration.
| Feature | Norm Name | Value |
|---|---|---|
| STMC Module ID | CV_STMC_Orgdaten.ID | 10101 |
| Automatic Registration of (Value) Table | Orgdaten_STMC.WTB |
The OrgDaten module can be in the STMC module, if you create a selection list, e.g., named Container. The way how selection lists are added to the Action selection list of the STMC module is explained in the documentation of the STMC module.
The number for the entry in the column Value is the value of the variable CV_STMC_OrgDaten.ID. In the column Selection enter a name for the selection.
The properties of this selection list are described in the following section.
Selection List Container
The selection list Container must be defined as a simple selection list and may contain the following two rows, where the text in column Selection will be shown 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 shows different options how the opening or closing of containers can be handled in different situations.
All data belonging to the same test order are stored in one container. The container is opened at the start of the test order and is closed at the end. The following figure depicts the default container behavior.
The container will be opened automatically by loading a test. If the test is unloaded and continued later, the files are stored in the same container. This container is closed when the test order is completed. The following figure depicts the behavior when a test is unloaded and continued.
The container will be opened automatically by loading a test if it is existing. In case no container was created or the container was not opened when activating manual or automatic mode, then you can select whether there will be:
- A warning
- Inhibit to proceed
- No hint
The parameterization of the selected behavior in this case has to be done in the test case of your application.
The container may be opened or closed by an action command in the sequence table.
It is possible to unload a test and the container is closed. If this test order is interrupted and another test is loaded the data are written to the container of this test. When the interrupt test is continued later the data can be written to the original container of this test.
