Tag Structure
WideQuick Modular Framework utilizes a flexible tag structure to simplify configuration and reduce time to market for WideQuick applications. This tag structure makes it possible to connect a large number of tags to an object without having to manually connect each tag to said object.
This ease of use also makes it easy to import large number of tags and automatically connect them to objects. This means that it is easy to make modifications and additions to existing projects.
For a tag to conform to the tag structure in WideQuick Modular Framework it needs to consist of the following five parts
-
Connection
-
Device
-
System
-
Object name
-
Suffix
Tip
If you are uncertain if your variable name is correct, try using the text input below to confirm. It will turn green when the name is correct.
✅ Variable name is valid!
See the image below
Connection
Connection represents the connection. This could be the type of connection such as Modbus, OPC or the model/make of the PLC such as Siemens or SAIA.
Device
The device represents an electrical enclosure such as AS01 or similar.
System
The system represents which system the tag belongs to. For instance LB01, Intake, or Outlet.
Object name
The object name represents the name of the object itself, this might be a temperature sensor GT11, a motor M01 or a pump P23.
Suffix
Suffix represents what type of signal the tag represents, for instance a measurement value, a setpoint or a status indicator.
Naming tags
These are just examples, the tags can be named whatever you wish as long as they follow the structure Connection.Device.Sys_Component_Suffix
Example tags
Skane.Kallby.AS01_pump07_IO
Kentima.Staffanstrop.Skap03_GT11_MV
Modbus.AS01.Kallby_Motor01_LG
Configuring tags in OPC DA & OPC UA
Configuring OPC tags to follow the standard is very straight forward. The tags just have to be named according to the structure.
Configuring tags in Modbus Serial & Modbus TCP/IP
Modbus tags should also follow the same tag structure. However both the connection and the device are retrieved from from the connection name and the device name as seen in the image below. This means that the tag in the tag editor only needs to contain sys_component_suffix.
Connecting object to tags
Before you can connect tags to an object you first need an object. Please review create object here
Once an object is created the DynTouch needs to be connected to the tags. This is done by entering the tag information on the properties of the DynTouch. This means just entering the tag information as seen in the image below. This will allow WideQuick to automatically find all tags connected to this object.
In order to speed up the process of connecting several objects to their tags it is not necessary to enter the same connection, device and sys information on every object in the view. Instead these properties can be set on the workview properties. If a DynTouch is left empty it will instead try to retrieve the information from the view.
Object name
It is possible to ignore entering the object name on the DynTouch by instead naming the object to the object name.
Special properties on tags
It is possible to define tag specific properties and description for a tag which will override the rules set for tag that in for instance the popups. Please see Create popup
This is done by entering specific values in the description of the tag in the tag editor.
Possible values to override are:
-
The description of the tag - This is set by entering the description of the tag in the Description field in the tag editor until the first semi-colon (;)
-
The number of decimals that will be displayed on the tag - This is set by writing DECIMAL=X; Where x represents the number of decimals.
-
The privilege required to write a value to the tag (write privilege) - This is set by writing PRIV=privilege; Where privilege represents a privilege in the user system.
The example below sets the description to: "Börvärde" with 2 decimals and requires the privilege "Config" to edit.
Warning
The tag must contain a description for the override to work. I.e. it's not possible to just write DECIMAL=3;