Lexicon-GBE dictionary

Lexicon, as its name implies, is a 'dictionary '. Therefore, many user-defined work can be performed in this module. This module is not only an important module but also a very commonly used module. However, to use this module smoothly, the following two conditions are indispensable:

A) log on to the module as a free user. Normal general users cannot access this module.

B) There must be a DB of dict type to store custom data, and the DB must be in the selected MDB.

1. Custom type

The Lexicon module provides a variety of customizable data types, such as dbvwwl, dstwld, dsxwld, revcwl, stawld, udetwld, and uwlrd. Some of them are used to define data tables, some are used to define attributes and types. Due to my limited level and incomplete knowledge, I can only talk about the following two types.

 

2. uwlrd

Uwlrd is generally referred to as UDA, short for user-defined attribute. User-defined attributes are an important supplement to basic and hidden properties of PVDF. Because the system attributes of all component types can be enumerated, Udas can be used to customize attributes when we find that the system attributes are not suitable for our use.

2.1 data layers

UDA has three levels of data:

Uwrl-uda world

Ugro-uda group is optional at this level, but it is strongly recommended. This level can be used to effectively manage UDA

UDA-uda actual component layer

2.2 establish management

You can use the menu bar to create a management layer or a command line to create a management layer.

2.2.1 create uwrl on the Interface

 

2.2.2 create uwrl through command line

New uwrl

In the earlier version, there may be no interface to create, and you can only create it using command lines.

2.2.3 create ugro

The ugro creation method is the same as that of uwrl.

2.3 create UDA

The method for creating a UDA is the same as that for creating its management layer. Here we create a UDA for storing the device type.

2.4 UDA attributes

After creating a UDA, you will find that UDA has a large number of attributes that need to be filled in. The list is as follows:

2.5 attribute description

2.5.1. Description

This attribute is not actually visible in the non-lexicon module, but it is easy for the Administrator to maintain it later. Here we enter the 'device type '.

2.5.2. UDA type

This attribute specifies the data type. Click the drop-down menu on the right to view multiple options. For example, integer, string type, boolean type, date type, and the direction type and position type that are unique to MCM. Here we select 'text', that is, string type.

2.5.3. UDA Length

This attribute specifies the length of the data type. Here we set it to 10

2.5.4. Element Types

This attribute is used to define the types of elements that UDA assigns to the child. You can directly enter or click it and select it on the page.

A uda can be assigned to multiple types of elements. Here we only assign this UDA to equi-type elements, it is also acceptable if we continue to assign this attribute to the zone type element.

2.5.5. UDA default

Specify the default value of UDA. Here we set it to pump.

2.5.6. User-Defined name

UDA name. This attribute is very important and is the name of the UDA displayed in other modules. The name is equiptype.

2.5.7. Valid values

Specifies the valid value range of UDA, which can be used to constrain the value of UDA.

The writing method here is required. If it is a real number, it should be written as 0-10, indicating that it is between 0 and 10. If it is a string, its value must be enclosed in single quotation marks or | the value should be enclosed, for example, | pump |. If there are multiple parallel values, the values are separated by commas. Here we write it as | pump |, | tank |.

2.6 UDA Verification

In this case, open the design module, select an equi, enter the q att query attribute, and you will find that the following line is added after the system attribute,

: Equiptype Pump

Note: We did not add ':' In the name just now. Here is the identifier automatically added by PVDF, which is used to distinguish UDA from the built-in attributes of the system.

We changed the value of this attribute to tank. The modification was successful. If we changed it to xxxx, an error will be prompted, and the value is not within the valid value range.

2.7 UDA conclusion

The system attributes of UDA are the same as those of PVDF, and the query and modification operations are the same. At the same time, it is equivalent to system attributes when we use PML programming.

 

3. udet

Compared with UDA, udet is not common. Udet is short for user-defined element types, that is, user-defined component type. You can define udet to implement some special requirements.

3.1 data layers

Like UDA, udet also has three levels of data:

Udetwl-udet world

Udetgr-udet Group

Udet-udet

Careful readers may find that the data layers of udet are exactly the same as those of UDA. In fact, they not only have the same data layers, but also have the same creation method. Both interfaces and command lines are available. You can refer to the UDA data level creation method to create a udet data level. However, udet and UDA have completely different attributes.

3.2 udet attributes

3.2.1. Description

This attribute is also a descriptive property. Here we enter 'device '.

3.2.2. User-Defined name

Udet name. This attribute is very important. It is the name of the level type created by udet in other modules. Here we name it tank.

3.2.3. Base type

The basic type. Note that the custom component type must be equivalent to one of the component types known to the PVDF and cannot create a completely nonexistent type in the child model. The author believes that this is an important cause of udet comparison. Click the drop-down list on the right to select a known type of the Child model.

3.2.3. Owner types and member types

These two attributes do not need to be defined by the user. After the base type is selected, the program will automatically obtain them.

3.2.4 hidden attributes

After the base type is selected, the udet automatically inherits all the basic attributes of its equivalent type, but whether it inherits the hidden attributes can be set through the panel. The interface is as follows:

3.3 udet Verification

Open the design module, select a zone, and enter new: tank in the command line. A new component of the type tank will be created at the zone layer:

Note: New: tank must be written here, which cannot be missed; otherwise, a syntax error is prompted.

 

3.4 udet conclusion

The components of udet are of the same type in different aspects. At the same time, you can also use collect statements to collect or evaluate the value of VaR statements when using PML programming.