Tag name of the tag. Naming restriction applied. Please refer to Name Restriction.

Additional description.

The type of data stored in this tag. IntegraXor supports the following data types:

Note

Some devices only support a subset of the data type listed. Please check and ensure the data type selected matches the data type of the tag you intended to link to on the device.

Length for string data type.

Numerical tag address. For example Modbus node. Not used for modern protocol which uses extended address like OPC.

String tag address. For example, OPC and GE Fanuc SNP. Not used for conventional protocol which uses numeric address like Modbus.

Batch numbering indicates if a chunk of data for one device shall be read or write together if they are contiguous in data address arrangement. It can be any number that can link them into one chunk or one batch, for instance, entering 100 for several contiguous tags will make them poll or update at one go. This shall speed up the communication a lot especially for serial communication.

Enter -1 to let I/O manager automatically handle grouping based on protocol selected.

Enter 0 to force it to be read separately.

Enter any positive integer to group tags.

Modbus user can ignore this column but need to enter dummy tag to ensure the addresses are in one range, otherwise they will be polled separately.

Note

Dummy tags will still be considered into license I/O count, so engineer must arrange the addresses in contiguous form. If changing data address is not possible, engineer needs to optimize the license count by combining several chunks of addresses.

The default initial value. The tag will be initialized with this value when the project starts.

Enter expression to perform data scaling, value conversion, and any engineering unit conversion to manipulate the raw data before it is set to tag.

Enter expression to perform data scaling, value conversion, and any engineering unit conversion to manipulate the tag data before it is sent to device.

This column determines the tag's security level for reading. If the user login with user level lower than the value here, server will ignore the user's request to return the data. The highest security level is 1000 and it is set to 0 by default. It must not left blank.

This column determines the tag's security level for writing. If the user login with user level lower than the value here, server will ignore the user's request to set the data. The highest security level is 1000, it is set to 0 by default. It must not left blank.

Database name defined in Database Task. Server will log the tag value to this database based on log frequency or mechamism specified. This is the only thing need to do at back-end configuration if trending for a tag is required.

An additional attribute that defines the log frequency or mechanism for the tag.

Database name defined in Database Task. Server will save the tag value to this database upon changes. This retentive feature comes handy when a tag needs to start up with previously set, used or received data. System will store the last good value so that this last good value will be used upon next system start up, or upon communication error. Retentive value will always overwrite Default value when presents.

Displays a list of role defined for selection. Check or tick the roles to grant read access to users with the role selected. If no role is selected, all users are allowed to read this tag.

An additional attribute that defines whether the tag is write only tag. Set to true to mark this tag as write only. No user is allowed to read this tag even though he is given read Role.

Displays a list of role defined for selection. Check or tick the roles to grant write access to users with the role selected. If no role is selected, all users are allowed to write to this tag.

An additional attribute that defines whether the tag is read only input tag. Input tag can only be changed via I/O input read.

Set to true to mark this tag as read only. No user is allowed to write to this tag even though he is given Write Role.

Tip

For Modbus, 1x coil & 3x register need to have this attribute turn ON. This mean, to get Input Coil, you need to create a Boolean tag with this attribute ON; to get Input Register, you need to create a Integer/Float tag with this attribute ON. Otherwise, this attribute shall remain OFF.