Skip to content

Device Communication Information

Device Communication Tables

I/O Device Editor

ItemDescription
New DeviceAdds a device.
New StationAdds a station to a serial device.
Delete DeviceDeletes the selected device or station.
Copy DeviceSaves the selected device’s content in the clipboard. This includes stations for serial devices.
Expand AllShows all dropdown content within the I/O Device Editor window.
Collapse AllHides all dropdown content within the I/O Device Editor window.
CollapseCollapses the selected tree from Ethernet Device or Serial Device.
ExpandExpands the selected tree from Ethernet Device or Serial Device.
Ethernet DeviceLists all created ethernet devices under a dropdown.
Serial DeviceLists all created serial devices and their stations under a dropdown.
Certificates EditorOpens the Certificates Editor to manage Key Pairs and Trust Stores.
OKCloses the I/O Device Editor window.

Add New I/O Device

ItemDescription
Connection TypeSelect between Ethernet or Serial to determine the type of link between the HMI project and an external device.
Device NameAssigns a name to the user’s device.
Device TypeAssigns a protocol to communicate over for the I/O device.

I/O Device Editor - Ethernet Device

ItemDescription
Device NameAssigns a name to the user’s device.
Device ProtocolAssigns a protocol to communicate over for the I/O device. The current protocols Canvas supports are CIMON PLC (HMI Protocol), Allen-Bradley EtherNet/IP, Fatek FBS, LSIS FEnet, Mitsubishi MELSEC Ethernet, Modbus TCP, ODVA EtherNet/IP, OPC UA Client, Omron FINS, Proface GPEthernet, and Siemens S7.
Timeout (ms)Sets the maximum time to wait without any response before listing a communication failure.
Retry CountNumber of retries to reconnect for when a communication failure occurs.
String EncodingAssign an encoding method for reading and writing strings stored on a device. This setting can be overwritten for tags in the Edit Tag menu. The current methods supported by Canvas are ASCII, ISO-8859-1, Latin1, Windows-1252, Windows-949, CP949, Shift_JIS, GBK, and UTF-8.
String Encoding MethodWhen an invalid character is encountered, the gateway will do one of the following:
Replace: Will replace any invalid characters within the string with "?".
Skip: Will skip the invaid character and continue with the next one.
Stop: Will stop reading the string and truncate any remaining characters.
Read Immediately After WriteIf toggled, it will perform a write request and immediately perform a read without needing to wait for a scan.
Station NumberThe specific address of identifier of the PLC to communicate within a network.
Swap (Integer)Swaps the upper and lower bytes of integer data.
Swap (String)Swaps the upper and lower bytes of string word data.
Swap (Float32)Swaps the upper and lower bytes of float32 data.
Swap (Float64)Swaps the upper and lower bytes of float64 data.
PLC TypeSelect the type of PLC that will be connected. Is only available in specific protocols.
Message TypeAssigns a specific type of transmission type between devices:
Explicit: Message is for point to point communication between devices.
Implicit: Used for real-time I/O data exchange, it does not require explicit designation of the target device.
UCMM: Unconnected Message Manager allows unconnected and unscheduled messages to be exchanged between devices that do not have an established connection or a fixed exchange schedule.
Use Multiple ServiceToggling this will allow the capability of the devices to handle multiple concurrent service requests or operations from different devices.
HostThe IPv4 address of the target I/O Device.
Ethernet TypeAssign the Ethernet protocol to use to connect to the device.
PortChoose the port number for the target I/O device.
Slot NumberThe slot number of the device. Valid numbers are from 0 - 255.
Frame TypeAssigns a frame type. Canvas only supports 4E currently.
Unit IdentifierAssigns a unit ID of the device. Valid numbers are from 0 - 255.
Application URIAssigns the Uniform Resource Identifier to locate the asset on the network.
Enable EncryptionChecking this will enable encryption and allow some more features to be changed.
Generate Encryption CertificatesWill automatically generate a key pair on the device. Unchecking this box will allow the user to assign a specific key pair instead.
Encryption Key PairSelects a key pair to use for encryption. Users may create a new one or use an existing one. Key pairs may be created and edited within the Certificates Editor.
Security PolicySelect an encryption method for communication with the server. Current encryption methods are “Basic128Rsa15”, “Basic256”, “Basic256Sha256”, “Aes128_Sha256_RsaOaep” or “None”.
Message SecuritySelects if the data should be signed, encrypted, signed and encrypted, or neither.
Server NameAssign a name to the server.
Authentication MethodSelect the Authentication Method for the encryption. Options include “Anonymous” or “Username”.
Authentication UsernameEnters the username for the client.
Authentication PasswordEnter the password for the specified client.
Source Node IDAssign a Source Node ID. Valid numbers are 0-254 for TCP and 1-254 for UDP.
Source Network IDAssign a Source Network ID. Valid numbers are 0-65535.
Destination Network IDAssign a Destination Network ID. Valid numbers include 0-65535.
Destination Node IDAssign a Destination Node ID. Valid numbers include 0-65535.
Destination Unit IDAssign a Destination Unit. Valid numbers include 0-65535.
Rack NumberAssign a Rack Number of the target device. Valid numbers include 0-255.

I/O Device Editor - Serial Device

ItemDescription
Device NameAssigns a name to the user’s I/O serial device.
Device ProtocolAssigns a protocol to use to communicate with the serial device. The options are CIMON PLC (HMI Protocol), LSIS Cnet, Mitsubishi MELSEC Serial, Modbus RTU, Omron HostLink, Panasonic FP7, and Yokogawa FA-M3.
Timeout (ms)Sets the maximum time to wait without any response before listing a communication failure.
Retry CountNumber of retries to reconnect for when a communication failure occurs.
String EncodingSpecifies the encoding method for reading and writing string values stored on the device. The available encoding methods are ASCII, ISO-8859-1, Latin1, Windows-1252, Windows-949, CP949, Shift_JIS, GBK, and UTF-8.
String Encoding MethodWhen an invalid character is encountered, the gateway will do one of the following:
Replace: Will replace any invalid characters within the string with "?".
Skip: Will skip the invaid character and continue with the next one.
Stop: Will stop reading the string and truncate any remaining characters.
Read Immediately After WriteIf toggled, it will perform a write request and immediately perform a read without needing to wait for a scan.
PLC TypeSelect the type of PLC that will be connected. Is only available in specific protocols.
Serial PortAssigns a COM port for the device. COM1 is for RS-422/485, COM2 is for RS-232-C, and COM3 is for RS-232-C for 10, 12, and 15 inch Xpanels only.
Comm TypeAssigns a communication type for the COM port. COM2 and COM3 are forced to be RS-232, but COM1 can be RS-422 or RS-485.
BaudrateControls the rate at which information is transferred between devices. The options are 300, 600, 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200, and 230400.
ParityUsed to determine if the device correctly received the character. Both devices need to have the same parity.
Data BitsAssigns the number of data bits there are in each packet between 7 and 8.
If the data contains any Korean characters, select 8 bits to avoid errors.
Stop BitsAssigns the number of stop bits there are between each frame between 1 and 2.
Flow ControlLimits how much data is being sent into the device. This can be either On, Off, or Control.
Error DetectionSpecifies the error detection method for Allen-Bradley DF1, between BCC and CRC.
Transmission DelaySets the time in milliseconds that the client device will wait before sending a request
Read Block ToleranceSets the allowed amount of unused device addresses per block. Only applies to Modbus RTU.
Frame TypeUsed to confirm that data sent was correctly transmitted / received. Only applies to Mitsubishi MELSEC Serial, and only 3C is supported in Canvas.
Station NameAssigns a name to the user's I/O serial device station.
Destination IDAssigns a destination ID for the station. Valid numbers include 0-255.

Certificates Editor

ItemDescription
Add new Key Pair / Add new Trust StoreAdds a key pair or trust store.
Delete Key Pair / Delete Trust StoreDeletes the selected key pair or trust store.
Edit Key Pair / Edit Trust StoreEdits the selected key pair or trust store.
OKCloses the Certificates Editor window.

Key Pairs

ItemDescription
NameDisplays all of the current key pair names in order of creation.
CertificateDisplays all of the current certificates for created key pairs.
Private KeyDisplays all of the current private keys for created key pairs.
DescriptionDisplays all of the current descriptions of created key pairs.

New Key Pair

ItemDescription
NameAssigns a name to the user’s key pair.
CertificateAssigns the selected file to be the certificate of the key pair.
Private KeyAssigns the selected file to be the private key of the key pair.
DescriptionAssigns a description to the key pair.
Use PasswordControls whether or not the key pair will have a Private Key Password or not.
Private Key PasswordAssigns a private key password to the key pair.

Trust Stores

ItemDescription
Trust StoreDisplays all of the current trust store names in order of creation.
DescriptionDisplays all of the current descriptions of created trust stores.
CertificatesDisplays all of the currently added certificates in created trust stores.

New Trust Store

ItemDescription
NameAssigns a name to the user’s trust store.
CertificatesDisplays all of the current descriptions of created trust stores.
DescriptionAssigns a description to the trust store.

Data Server Editor

ItemDescription
New DeviceAdds a device.
Delete DeviceDeletes the selected device.
Copy DeviceSaves the selected device’s content in the clipboard.
Paste DevicePastes the device’s content in a Data Server Editor window. This can be done through different projects, but ethernet devices will only paste under ethernet and serial devices will only paste under serial.
Expand AllShows all dropdown content within the Data Server Editor window.
Collapse AllHides all dropdown content within the Data Server Editor window.
CollapseCollapses the selected tree from Ethernet Device or Serial Device.
ExpandExpands the selected tree from Ethernet Device or Serial Device.
Device SettingOpens the Device Settings tab.
Device TagOpens the Device Tag tab.
Certificates EditorOpens the Certificates Editor to manage Key Pairs and Trust Stores.
MQTT Payload EditorOpens the MQTT Payload Editor to manage MQTT Payload settings and properties.
OKCloses the Data Server Editor window.

Add New Server Device

ItemDescription
Connection TypeSelect between Ethernet or Serial to determine the type of link between the HMI project and an external device.
Device NameAssigns a name to the user’s device.
Device TypeAssigns a protocol to communicate over for the data server device.

Device Setting - Ethernet Device

ItemDescription
Device NameAssigns a name to the user’s device.
Device ProtocolAssigns a protocol to use to communicate with the serial device. The options are MQTT JSON Publisher, Modbus TCP and OPC UA Server.
Use All TagsToggle that allows the users to host all tags in the project on the data server.
Server NameAssign a name to the server.
Application URIAssigns the Uniform Resource Identifier to locate the asset on the network.
Application NameSets the name of the Application.
PortChoose the port number for the target Data Server. Aside from Modbus TCP Port 502, only numbers above 1023 are supported as Port numbers.
Unit IDAssigns a value to be the slave/server ID for Modbus TCP communication.
String EncodingSpecifies the encoding method for reading and writing string values stored on the device. The available encoding methods are ASCII, ISO-8859-1, Latin1, Windows-1252, Windows-949, CP949, Shift_JIS, GBK, and UTF-8.
String Encoding MethodWhen an invalid character is encountered, the gateway will do one of the following:
Replace: Will replace any invalid characters within the string with "?".
Skip: Will skip the invaid character and continue with the next one.
Stop: Will stop reading the string and truncate any remaining characters.
Broker AddressIPv4 address or hostname for the MQTT broker.
Client IDAssigns a client ID for publishing and subscribing.
Use Clean SessionEnables connecting to the MQTT broker using a non persistent connection.
Keep AliveNotes the keepalive time used by the MQTT client. This will be displayed in seconds.
Use SSLEnables the use of SSL encryption with the broker.
Key PairSelect a key pair to use for SSL encryption. These key pairs can be edited in the Certificates Editor window.
Trust StoreSelect a trust store to use for SSL encryption. These trust stores can be edited in the Certificates Editor window.
Use MQTT PasswordsIf toggled, a username and password will be used for connecting to the MQTT.
MQTT UsernameAssign a username for connecting to the MQTT broker.
MQTT PasswordAssign a password for connecting to the MQTT broker.
Use Message QueueToggle that will tell if the client should use a message queue, and will store messages when the client is disconnected.
Message Queue SizeAssigns the number of messages to be held in the message queue. Acceptable values are 20 to 10000.
Message Queue Publish Rate LimitMinimum time between publishes, with 0 being as soon as possible. Maximum value is 10000.
Use Message Queue Age LimitToggle that will impose an age limit on queued messages.
Message Queue Age Limit (s)The maximum age of a message in seconds that will be published.
Running ModeSets the criteria for when to publish a payload.
On Change any: Will publish a message every time a tag value updates. This is the default.
On Scan Delta: Will publish after every scan, but only generates message for changed tag values.
On Scan All: Will publish all tag values after every scan. Will publish even if there are no changes.
Polling Rate (ms)Determines the rate for polling tag changes. This will only be available in "On Scan Delta" or "On Scan All"
Publish Payload FormatCan select one of the following built-in payload formats for publishing:
The client devices must be configured to listen for payloads with the matching format.
Single: Each payload contains data from a single tag.
Multi: Each payload contains data from multiple tags.
No Wrap: The payload root object is the tag object, and all tag properties are direct children of the root object. Only available for "Single" payloads.
Wrap: Uses the tag ID as a property name for the value object. Available for both Single and Multi Payloads.
Array Wrap: Stores an array of tag objects named "Tags". The tag ID property is included in the tag object.
Basic: Includes the following properties: Value and Value Time.
Full: Includes the following properties: Value, Value Time, Type, Read Time, Device, and Quality.
Publish QOSControls the Quality of Service to use when publishing. This determines how many times each message will be sent in the event there is packet loss. In general, a higher value means communication will be more reliable but requires more handshakes and bandwidth consumption.
Zero: The message will be sent at most once.
1: The message will be sent at least once but may be sent multiple times.
2: The message will be sent exactly once.
Publish Retain MessagesIf enabled, the broker will retain the last known value for each topic. When a new client subscribes to a topic, the value that was retained will be published to the client by the broker. The broker can only retain one value per topic.
Publish Topic PrefixSets a prefix string to include in all publish topics.
This does not add a “/” level separator to a full topic.
Publish Topic SuffixSets a suffix string to include in all public topics.
This does not add a “/” level separator to a full topic.
Access TypeAssigns access to tags between Publish/Subscribe and Publish Only. The MQTT JSON Publisher server always publishes MQTT messages when a hosted tag’s value updates, but users can choose whether or not to subscribe to MQTT messages from clients.
Subscribe Payload FormatCan select one of the following built-in payload formats for subscribing:
The client devices must be configured to listen for payloads with the matching format.
Single: Each payload contains data from a single tag.
Multi: Each payload contains data from multiple tags.
No Wrap: The payload root object is the tag object, and all tag properties are direct children of the root object. Only available for "Single" payloads.
Wrap: Uses the tag ID as a property name for the value object. Available for both Single and Multi Payloads.
Array Wrap: Stores an array of tag objects named "Tags". The tag ID property is included in the tag object.
Basic: Includes the following properties: Value and Value Time.
Full: Includes the following properties: Value, Value Time, Type, Read Time, Device, and Quality.
Subscribe QOSControls the Quality of Service to use when subscribing. This determines how many times each message will be sent in the event there is packet loss. In general, a higher value means communication will be more reliable but requires more handshakes and bandwidth consumption.
Zero: The message will be sent at most once.
1: The message will be sent at least once but may be sent multiple times.
2: The message will be sent exactly once.
Subscribe Tag Identifier TypeSets the subscriber tag identifier type.
Topic: Identifies which tags each message is for based on the message topic. The subscribe topic must match what is defined in the Device Tag tab.
Payload: Identifies tags using an identifier within the payload.
Subscribe Clamp MethodSets the clamp method of provided values to the tag's data type.
Reject: Values outside of the data type range will be rejected.
Clamp: Values outside of the data type range will be clamped to the data type range.
Overflow: Values outside of the data type range will overflow.
Subscribe Topic PrefixSets a prefix string to include in all subscribed topics.
This does not add a “/” level separator to a full topic.
Subscribe Topic SuffixSets a suffix string to include in all subscribed topics.
This does not add a “/” level separator to a full topic.
Enable EncryptionControls whether or not encryption is used for the server.
Authentication will be disabled unless this field is enabled.
Generate CertificateControls whether or not a key pair will be automatically generated on the device once a project is ran. When this field is disabled, a user-specified key pair will be used instead.
Trust All CertificatesControls whether or not all incoming certificates will be trusted. When this field is disabled, only the certificates in the trust store will be trusted.
Require EncryptionControls whether messages must have an encryption method. The box unchecked allows for messages to be sent without an encryption method. The box checked forces messages to be sent with an encryption method.
Basic 128 RSA-15Controls the use of the method of encryption. Sign allows the method to be used for signing messages, but not encryption. Sign and Encrypt allows for the method to be used for signing and encrypting messages, but both must be used. Both allows for the method to be used for either signing or encryption. Encryption is allowed but not required.
Basic 256Controls the use of the method of encryption. Sign allows the method to be used for signing messages, but not encryption. Sign and Encrypt allows for the method to be used for signing and encrypting messages, but both must be used. Both allows for the method to be used for either signing or encryption. Encryption is allowed but not required.
Basic 256 SHA-256Controls the use of the method of encryption. Sign allows the method to be used for signing messages, but not encryption. Sign and Encrypt allows for the method to be used for signing and encrypting messages, but both must be used. Both allows for the method to be used for either signing or encryption. Encryption is allowed but not required.
AES-128 SHA-256 RSA-OAEPControls the use of the method of encryption. Sign allows the method to be used for signing messages, but not encryption. Sign and Encrypt allows for the method to be used for signing and encrypting messages, but both must be used. Both allows for the method to be used for either signing or encryption. Encryption is allowed but not required.
Allow Anonymous AuthenticationControls whether or not anonymous clients can connect to the server.
Allow Anonymous BrowseControls whether or not anonymous clients can browse topics on the server.
Allow Anonymous ReadControls whether or not anonymous clients can read tag values from the server.
Allow Anonymous WriteControls whether or not anonymous clients can write tag values to the server.
Allow Username AuthenticationControls whether or not clients can be authenticated by providing a matching username and password.
Add New UserCreates a new user to allow for authentication. Users can be deleted by clicking the trash icon to the right of the user number.
UsernameAssigns a username for the user.
PasswordAssigns a password for the user.
Allow BrowseControls whether or not the user can browse topics on the server.
Allow ReadControls whether or not the user can read tag values from the server.
Allow WriteControls whether or not the user can write tag values to the server.
Allow Certificate AuthenticationControls whether or not clients can use certificates for authentication.
When the Trust All Certificates field is enabled, any certificate may be used for authentication. When it is disabled, only certificates found in the trust store may be used.
Allow Certificate BrowseControls whether or not clients authenticated using a certificate can browse topics on the server.
Allow Certificate ReadControls whether or not clients authenticated using a certificate can read tag values from the server.
Allow Certificate WriteControls whether or not clients authenticated using a certificate can write tag values to the server.
Match Endpoint Security PolicyControls whether or not authentication tokens will be encrypted using the same security policy as the endpoint they are attached to.
Allow Unencrypted AuthenticationControls whether or not clients are able to authenticate without encryption. This option is only available when enabled by the Match Endpoint Security Policy field.
Authentication Security PolicySets the security policy for authenticating users. The options are None, Basic128Rsa15, Basic256, Basic256Sha256, and Aes128_Sha256_RsaOaep. This option is only available when the Match Endpoint Security field is disabled.
Server LayoutDetermines the prefix structure for OPC UA tag topics:
Basic: Tag topics will be direct children of the "Tags" topic.
Example: Tags.browseName.
Device: Tag topics will be children of topics which are named after their I/O devices.
Example: Tags.deviceName.browseName.
Default Allow ReadControls whether or not clients are able to read the current value of tags or not. Individual tags may overwrite this option by choosing True or False in their Allow Read field.
Default Allow WriteControls whether or not clients are able to write a value to tags or not. Individual tags may overwrite this option by choosing True or False in their Allow Write field.
Use All Tags (Logix)Uses all created tags to be Logix tags when communicating with an EtherNet/IP Client.
Group IDAssigns a Group ID to be used in the topic structure when communicating via Sparkplug Edge Node.
EoN IDAssigns a EoN ID to be used in the topic structure when communicating via Sparkplug Edge Node.
Use Primary Host ApplicationControls whether or not a Primary Host Application can be specified and used.
Primary Host ApplicationReceives a state condition from the specified host.
Use Metric AliasingWhen disabled, the string identifier for the tag is used every time the tag value is updated. When enabled, there's an automated workflow that ties each tag to a numeric identifier that is used by the payload. This field should be matched to the host device's setting.
Use All DevicesControls whether or not I/O devices will be automatically added to the Device Tag list.

Device Setting - Serial Device

ItemDescription
Device NameAssigns a name to the user’s Data Server serial device.
Device ProtocolAssigns a protocol to use to communicate with the serial device. The only option is Modbus RTU.
Serial PortAssigns a COM port for the device to use for Modbus RTU. COM1 is for RS-422/485, COM2 is for RS-232-C, and COM3 is for RS-232-C for 10, 12, and 15 inch Xpanels only.
Comm TypeAssigns a communication type for the COM port to use. COM2 and COM3 are forced to be RS-232, but COM1 can be RS-422 or RS-485.
BaudrateControls the rate at which information is transferred between devices. The options are 300, 600, 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200, and 230400.
ParityAssigns a parity bit to be used for error checking. The options are Even, Odd, and None.
Data BitsAssigns the number of data bits in each packet between 7 and 8.
If the data contains Korean characters, select 8 bits to avoid errors.
Stop BitsAssigns the number of stop bits between each frame between 1 and 2.
Flow ControlLimits the amount of data transferred. When enabled, the Modbus Master will wait for an ackowledgement signal from the target device before sending another command. The options are Off, On, and Control.
Unit IDAssigns a value to be the slave/server ID for Modbus RTU communication.
String EncodingSpecifies the encoding method for reading and writing string values stored on the device. The available encoding methods are ASCII, ISO-8859-1, Latin1, Windows-1252, Windows-949, CP949, Shift_JIS, GBK, and UTF-8.
String Encoding MethodWhen an invalid character is encountered, the gateway will do one of the following:
Replace: Will replace any invalid characters within the string with "?".
Skip: Will skip the invaid character and continue with the next one.
Stop: Will stop reading the string and truncate any remaining characters.

Device Tag - Ethernet Device

ItemDescription
New TagAdds a tag.
Edit TagEdits the selected tag.
Delete TagDeletes the selected tag.
Expand AllShows all dropdown content within the Device Tag tab.
Collapse AllHides all dropdown content within the Device Tag tab.
TagDisplays all current tag names in order of addition.
Address0- Coil Tags: Organizes added tags into a folder that allows BOOL Read/Write access for Modbus TCP.
1- Discrete Input Tags: Organizes added tags into a folder that allows BOOL Read Only access for Modbus TCP.
3- Input Tags: Organizes added tags into a folder that allows Analog Read Only access for Modbus TCP.
4- Holding Tags: Organizes added tags into a folder that allows Analog Read/Write access for Modbus TCP.
Access TypeDisplays all tag's assigned access type chosen between Publish/Subscribe and Publish Only.
Browse NameDisplays all assigned names to added tags for an OPC UA Server.

Device Tag - Ethernet Device New Tag

ItemDescription
Tag TypeAssigns the folder that the tag will be added into. The options are 0: Coil, 1: Discrete Input, 3: Input, and 4: Holding.
TagAllows the user to select an already created tag to be added.
0: Coil and 1: Discrete require a BOOL data type. 3: Input and 4: Holding require an Analog data type.
AddressAssigns a number 1-65536 to be the Modbus TCP communication address.
PreviewDisplays the Modbus TCP address after being formatted to the tag type number and filling zeros.
Access TypeAssigns access to the tag between Publish/Subscribe and Publish Only.
Publish IDAssigns an identifier that is used when publishing tag data. This defaults to the assigned tag’s path.
If the identifier is not included in the publish payload format, Publish ID will be ignored.
Publish TopicAssigns the MQTT topic to publish tag messages to. This defaults to the assigned tag’s path.
Subscribe IDAssigns an identifier that is used when subscribing to incoming messages. This defaults to the assigned tag’s path.
If the identifier is not included in the subscriber payload format, Subscribe ID will be ignored.
Subscribe TopicAssigns the MQTT topic to listen to messages on. The topic can include the MQTT wildcard characters # (multi-level) and + (single level). This defaults to the assigned tag’s path.
Browse NameAssigns a name that will be used as part of the OPC topic used by client devices. This defaults to the assigned tag’s path.
Allow ReadControls whether or not clients are able to read the current value of the tag or not. The three options are Use Server Default, True, and False.
Allow WriteControls whether or not clients are able to write a value to the tag or not. The three options are Use Server Default, True, and False.
OKCloses the New Tag window and adds a tag with the entered information.
CancelCloses the New Tag window and discards the entered information.

Device Tag - Serial Device

ItemDescription
New TagAdds a non-Virtual (Runtime Only) tag.
Edit TagEdits the selected tag.
Delete TagDeletes the selected tag.
Expand AllShows all dropdown content within the Device Tag tab.
Collapse AllHides all dropdown content within the Device Tag tab.
Address0- Coil Tags: Organizes added tags into a folder that allows BOOL Read/Write access for Modbus RTU.
1- Discrete Input Tags: Organizes added tags into a folder that allows BOOL Read Only access for Modbus RTU.
3- Input Tags: Organizes added tags into a folder that allows Analog Read Only access for Modbus RTU.
4- Holding Tags: Organizes added tags into a folder that allows Analog Read/Write access for Modbus RTU.
TagDisplays all current tag names in order of addition.

Device Tag - Serial Device New Tag

ItemDescription
Tag TypeAssigns the folder that the tag will be added into. The options are 0: Coil, 1: Discrete Input, 3: Input, and 4: Holding.
TagAllows the user to select an already created tag to be added.
0: Coil and 1: Discrete require a BOOL data type. 3: Input and 4: Holding require an Analog data type.
AddressAssigns a number 1-65536 to be the Modbus RTU communication address.
PreviewDisplays the Modbus RTU address after being formatted to the tag type number and filling zeros.
OKCloses the New Tag window and adds a tag with the entered information.
CancelCloses the New Tag window and discards the entered information.

MQTT Payload Editor

ItemDescription
New Payload FormatAdds a new payload format.
Delete Payload FormatDeletes the selected payload format.
Copy Payload FormatSaves the selected payload format’s content in the clipboard.
Paste Payload FormatPastes the device’s content in a MQTT Payload Editor window. This can be done through different projects.
Payload SettingsOpens the Payload Settings tab when selecting a payload format.
PropertiesOpens the Properties tab when selecting a payload format.

Payload Settings

ItemDescription
Expand AllShows all dropdown content within the Payload Settings tab.
Collapse AllHides all dropdown content within the Payload Settings tab.
Payload Format NameAssigns a name to the user’s payload format.
Tags per PayloadAssigns a number of tags in each payload between Multiple or Single.
Wrap MethodAssigns a wrapping method between Identifier and Array.
Wrap NameAssigns a name to the user’s wrap.

Properties

ItemDescription
Add PropertyDrops down with a menu to add a new property or property group.
Move UpMoves a property or property group up one position.
Move DownMoves a property or property group down one position.
Delete PropertyDeletes the selected property or property group.
Expand AllShows all dropdown content within the Properties tab.
Collapse AllHides all dropdown content within the Properties tab.
Property NameAssigns and displays a name for the property or property group.
ValueAssigns and displays a value for properties. The options for value include Tag Identifier, Tag Device, Tag Quality, Tag Value, Tag Type, Tag Value Timestamp, Tag Read Timestamp, Tag Quality Timestamp, and Tag Payload Timestamp.
FormatAssigns and displays a format for properties.