Adds a device.

Adds a station to a serial device.

Deletes the selected device or station.

Saves the selected device’s content in the clipboard. This includes stations for serial devices.

Shows all dropdown content within the I/O Device Editor window.

Hides all dropdown content within the I/O Device Editor window.

Collapses the selected tree from Ethernet Device or Serial Device.

Expands the selected tree from Ethernet Device or Serial Device.

Lists all created ethernet devices under a dropdown.

Lists all created serial devices and their stations under a dropdown.

Opens the Certificates Editor to manage Key Pairs and Trust Stores.

Closes the I/O Device Editor window.

Select between Ethernet or Serial to determine the type of link between the HMI project and an external device.

Assigns a name to the user’s device.

Assigns a protocol to communicate over for the I/O device.

Assigns a name to the user’s device.

Assigns 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.

Sets the maximum time to wait without any response before listing a communication failure.

Number of retries to reconnect for when a communication failure occurs.

Swaps the upper and lower bytes of integer data.

Swaps the upper and lower bytes of a string word data.

Swaps the upper and lower bytes of float32 data.

Swaps the upper and lower bytes of float64 data.

The specific address of identifier of the PLC to communicate within a network.

Assign 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.

When an invalid character is encountered, the gateway will do one of the following:

Will replace any invalid characters within the string with “?”.

Will skip the invalid character and continue with the next one.

Will stop reading the string and truncate any remaining characters.

If toggled, it will perform a write request and immediately perform a read without needing to wait for a scan.

Select the type of PLC that will be connected. Is only available in specific protocols.

Assigns a specific type of transmission type between devices.

Message is for point to point communication between devices.

Used for real-time I/O data exchange, it does not require explicit designation of the target device.

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.

Toggling this will allow the capability of the devices to handle multuple concurrent service reuqests or operations from different devices.

The IPv4 address of the target I/O Device.

Assign the Ethernet protocol to use to connect to the device.

Choose the port number for the target I/O device.

The slot number of the device. Valid numbers are from 0 - 255.

Assigns a frame type. Canvas only supports 4E currently.

Assigns a unit ID of the device. Valid numbers are from 0 - 255.

Assigns the Uniform Resource Identifier to locate the asset on the network.

Checking this will enable encryption and allow some more features to be changed.

Will automatically generate a key pair on the device. Unchecking this box will allow the user to assign a specific key pair instead.

Selects 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.

Select an encryption method for communication with the server. Current encryptions methods are “Basic128Rsa15”, “Basic256”, “Basic256Sha256”, “Aes128_Sha256_RsaOaep” or “None”.

Selects if the data should be signed, encrypted, signed and encrypted, or neither.

Assign a name to the server.

Select the Authentication Method for the encryption. Options include “Anonymous” or “Username”

Enters the username for the client.

Enter the password for the specified client.

Assign a Source Node ID. Valid numbers are 0-254 for TCP and 1-254 for UDP.

Assign a Source Network ID. Valid numbers are 0-65535.

Assign a Destination Network ID. Valid numbers include 0-65535.

Assign a Destination Node ID. Valid numbers include 0-65535.

Assign a Destination Unit. Valid numbers include 0-65535.

Assign a Rack Number of the target device. Valid numbers include 0-255.

Assigns a name to the user’s I/O serial device.

Assigns 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.

Sets the maximum time to wait without any response before listing a communication failure.

Number of retries to reconnect for when a communication failure occurs.

Specifies 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.

When an invalid character is encountered, the gateway will do one of the following:

Will replace any invalid characters within the string with “?”.

Will skip the invalid character and continue with the next one.

Will stop reading the string and truncate any remaining characters.

If toggled, it will perform a write request and immediately perform a read without needing to wait for a scan.

Select the type of PLC that will be connected. Is only available in specific protocols.

Assigns 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.

Assigns 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.

Controls the rate at which information is transferred between devices. The options are 300, 600, 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200, and 230400.

Used to determine if the device correctly received the character. Both devices need to have the same parity.

Assigns the number of data bits there are in each packet between 7 and 8.

Assigns the number of stop bits there are between each frame between 1 and 2.

Limits how much data is being sent into the device. This can be either On, Off, or Control.

Used to confirm that data sent was correctly transmitted / received. Only applies to Mitsubishi MELSEC Serial, and only 3C is supported in Canvas.

Adds a key pair or trust store.

Deletes the selected key pair or trust store.

Edits the selected key pair or trust store.

Closes the Certificates Editor window.

Displays all of the current key pair names in order of creation.

Displays all of the current certificates for created key pairs.

Displays all of the current private keys for created key pairs.

Displays all of the current descriptions of created key pairs.

Assigns a name to the user’s key pair.

Assigns the selected file to be the certificate of the key pair.

Assigns the selected file to be the private key of the key pair.

Assigns a description to the key pair.

Controls whether or not the key pair will have a Private Key Password or not.

Assigns a private key password to the key pair.

Displays all of the current trust store names in order of creation.

Displays all of the current descriptions of created trust stores.

Displays all of the currently added certificates in created trust stores.

Assigns a name to the user’s trust store.

Assigns the selected files using the Add Certificate icon to be certificates in the trust store.

Assigns a description to the trust store.

Adds a device.

Deletes the selected device.

Saves the selected device’s content in the clipboard.

Pastes 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.

Shows all dropdown content within the Data Server Editor window.

Hides all dropdown content within the Data Server Editor window.

Collapses the selected tree from Ethernet Device or Serial Device.

Expands the selected tree from Ethernet Device or Serial Device.

Opens the Device Settings tab.

Opens the Device Tag tab.

Opens the Certificates Editor to manage Key Pairs and Trust Stores.

Opens the Payload Editor to manage Payload settings and properties.

Closes the Data Server Editor window.

Select between Ethernet or Serial to determine the type of link between the HMI project and an external device.

Assigns a name to the user’s device.

Assigns a protocol to communicate over for the data server device.

Assigns a name to the user’s device.

Assigns a protocol to use to communicate with the serial device. The options are MQTT JSON Publisher, Modbus TCP and OPC UA Server.

Toggle that allows the users to host all tags in the project on the data server.

Assign a name to the server.

Assigns the Uniform Resource Identifier to locate the asset on the network.

Sets the name of the Application.

Choose the port number for the target Data Server.

Assigns a value to be the slave/server ID for Modbus TCP communication.

Specifies 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.

When an invalid character is encountered, the gateway will do one of the following:

Will replace any invalid characters within the string with “?”.

Will skip the invalid character and continue with the next one.

Will stop reading the string and truncate any remaining characters.

IPv4 address or hostname for the MQTT broker.

hoose the port number for the target MQTT broker.

Assigns a client ID for publishing and subscribing.

Enables connecting to the MQTT broker using a non persistent connection.

Notes the keepalive time used by the MQTT client. This will be displayed in seconds.

Enables the use of SSL encryption with the broker.

Select a key pair to use for SSL encryption. These key pairs can be edited in the Certificates Editor window.

Select a trust store to use for SSL encryption. These trust stores can be edited in the Certificates Editor window.

If toggled, a username and password will be used for connecting to the MQTT

Assign a username for connecting to the MQTT broker.

Assign a password for connecting to the MQTT broker.

Toggle that will tell if the client should use a message queue, and will store messages when the client is disconnected.

Assigns the number of messages to be held in the message queue. Acceptable values are 20 to 10000.

Minimum time between publishes, with 0 being as soon as possible. Maximum value is 10000.

Toggle that will impose an age limit on queued messages.

The maximum age of a message in seconds that will be published.

Sets the criteria for when to publish a payload.

Will publish a message every time a tag value updates. This is the default.

Will publish after every scan, but only generates message for changed tag values.

Will publish all tag values after every scan. Will publish even if there are no changes.

Determins the rate for polling tag changes. This will only be available in “On Scan Delta” or “On Scan All”

Can select one of the following built-in payload formats for publishing:

Each payload contains data from a single tag.

Each payload contains data from multiple tags.

The payload root object is the tag object, and all tag properties are direct children of the root object. Only available for “Single” payloads.

Uses the tag ID as a property name for the value object. Available for both Single and Multi Payloads.

Stores an array of tag objects named “Tags”. The tag ID property is included in the tag object.

Includes the following properties: Value and Value Time.

Includes the following properties: Value, Value Time, Type, Read Time, Device, and Quality.

Controls 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 require more handshakes and bandwidth consumption.

The message will be sent at most once.

The message will be sent at least once but may be sent multiple times.

The message will be sent exactly once.

If 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.

Sets a prefix string to include in all publish topics.

Sets a suffix string to include in all public topics.

Assigns 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.

Can select one of the following built-in payload formats for subscribing:

Each payload contains data from a single tag.

Each payload contains data from multiple tags.

The payload root object is the tag object, and all tag properties are direct children of the root object. Only available for “Single” payloads.

Uses the tag ID as a property name for the value object. Available for both Single and Multi Payloads.

Stores an array of tag objects named “Tags”. The tag ID property is included in the tag object.

Includes the following properties: Value and Value Time.

Includes the following properties: Value, Value Time, Type, Read Time, Device, and Quality.

Controls 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 require more handshakes and bandwidth consumption.

The message will be sent at most once.

The message will be sent at least once but may be sent multiple times.

The message will be sent exactly once.

Sets the subscriber tag identifier type.

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.

Identifies tags using an identifier within the payload.

Sets the clamp method of provided values to the tag’s data type.

Values outside of the data type range will be rejected.

Values outside of the data type range will be clamped to the data type range.

Values outside of the data type range will overflow.

Sets a prefix string to include in all subscribed topics.

Sets a suffix string to include in all subscribe topics.

Controls whether or not encryption is used for the server.

Controls 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.

Controls whether or not all incoming certificates will be trusted. When this field is disabled, only the certificates in the trust store will be trusted.

Controls whether messages can be sent with no encryption method. The option None allows for messages to be sent without an encryption method. The option disabled forces messages to be sent with an encryption method.

Controls the use of the method of encryption. Sign allows the method to be used for signing messages, 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 allows but not required.

Controls the use of the method of encryption. Sign allows for the method to be used for signing messages, but not for 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 allows but not required.

Controls the use of the method of encryption. Sign allows for the method to be used for signing messages, but not for 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 allows but not required.

Controls the use of the method of encryption. Sign allows for the method to be used for signing messages, but not for 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 allows but not required.

Controls whether or not anonymous clients can connect to the server.

Controls whether or not anonymous clients can browse topics on the server.

Controls whether or not anonymous clients can read tag values from the server.

Controls whether or not anonymous clients can write tag values to the server.

Controls whether or not clients can be authenticated by providing a matching username and password.

Creates a new user to allow for authentication. Users can be deleted by clicking the trash icon to the right of the user number.

Assigns a username for the user.

Assigns a password for the user.

Controls whether or not the user can browse topics on the server.

Controls whether or not the user can read tag values from the server.

Controls whether or not the user can write tag values to the server.

Controls whether or not clients can use certificates for authentication.

Controls whether or not clients authenticated using a certificate can browse topics on the server.

Controls whether or not clients authenticated using a certificate can read tag values from the server.

Controls whether or not clients authenticated using a certificate can write tag values to the server.

Controls whether or not authentication tokens will be encrypted using the same security policy as the endpoint they are attached to.

Controls whether or not clients are able to authenticate without encryption. This option is only available when enabled by the Match Endpoint Security Policy field.

Sets 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.

Determines the prefix structure for OPC UA tag topics:

Tag topics will be direct children of the “Tags” topic. Ex: Tags.browseName.

Tag topics will be children of topics which are named after their I/O devices.

Ex: Tags.deviceName.browseName.

Controls 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.

Controls 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.

Assigns a name to the user’s Data Server serial device.

Assigns a protocol to use to communicate with the serial device. The only option is Modbus RTU.

Assigns 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.

Assigns 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.

Controls the rate at which information is transferred between devices. The options are 300, 600, 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200, and 230400.

Assigns a parity bit to be used for error checking. The options are Even, Odd, and None.

Assigns the number of data bits there are in each packet between 7 and 8.

Assigns the number of stop bits there are between each frame between 1 and 2.

Limits 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.

Assigns a value to be the slave/server ID for Modbus RTU communication.

Specifies 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.

When an invalid character is encountered, the gateway will do one of the following:

Will replace any invalid characters within the string with “?”.

Will skip the invalid character and continue with the next one.

Will stop reading the string and truncate any remaining characters.

Adds a tag.

Edits the selected tag.

Deletes the selected tag.

Shows all dropdown content within the Device Tag tab.

Hides all dropdown content within the Device Tag tab.

Displays all current tag names in order of addition.

Organizes added tags into a folder that allows BOOL Read/Write access for Modbus TCP.

Organizes added tags into a folder that allows BOOL Read Only access for Modbus TCP.

Organizes added tags into a folder that allows Analog Read Only access for Modbus TCP.

Organizes added tags into a folder that allows Analog Read/Write access for Modbus TCP.

Displays all access added tags possess between Publish/Subscribe and Publish Only.

Displays all assigned names to added tags for an OPC UA Server.

Assigns the folder that the tag will be added into. The options are 0: Coil, 1: Discrete Input, 3: Input, and 4: Holding.

Allows the user to select an already created tag to be added.

Assigns a number 1-65536 to be the Modbus TCP communication address.

Displays the Modbus TCP address after being formatted to with the tag type number and filling zeros.

Assigns access to the tag between Publish/Subscribe and Publish Only.

Assigns an identifier that is used when publishing tag data. This defaults to the assigned tag’s path.

Assigns the MQTT topic to publish tag messages to. This defaults to the assigned tag’s path.

Assigns an identifier that is used when subscribing to incoming messages. This defaults to the assigned tag’s path.

Assigns 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.

Assigns a name that will be used as part of the OPC topic used by client devices. This defaults to the assigned tag’s path.

Controls 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.

Controls 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.

Closes the New Tag window and adds a tag with the entered information.

Closes the New Tag window and discards the entered information.

Adds a tag.

Edits the selected tag.

Deletes the selected tag.

Shows all dropdown content within the Device Tag tab.

Hides all dropdown content within the Device Tag tab.

Organizes added tags into a folder that allows BOOL Read/Write access for Modbus RTU.

Organizes added tags into a folder that allows BOOL Read Only access for Modbus RTU.

Organizes added tags into a folder that allows Analog Read Only access for Modbus RTU.

Organizes added tags into a folder that allows Analog Read/Write access for Modbus RTU.

Displays all current tag names in order of addition.

Assigns the folder that the tag will be added into. The options are 0: Coil, 1: Discrete Input, 3: Input, and 4: Holding.

Allows the user to select an already created tag to be added.

Assigns a number 1-65536 to be the Modbus TCP communication address.

Displays the Modbus TCP address after being formatted to with the tag type number and filling zeros.

Closes the New Tag window and adds a tag with the entered information.

Closes the New Tag window and discards the entered information.

Adds a new payload format.

Deletes the selected payload format.

Saves the selected payload format’s content in the clipboard.

Pastes the device’s content in a Payload Editor window. This can be done through different projects.

Opens the Payload Settings tab when selecting a payload format.

Opens the Properties tab when selecting a payload format.

Shows all dropdown content within the Payload Settings tab.

Shows all dropdown content within the Payload Settings tab.

Assigns a name to the user’s payload format.

Assigns a number of tags in each payload between Multiple or Single.

Assigns a wrapping method between Identifier and Array

Assigns a name to the user’s wrap.

Drops down with a menu to add a new property or property group.

Moves a property or property group up one position.

Moves a property or property group down one position.

Deletes the selected property or property group.

Shows all dropdown content within the Properties tab.

Hides all dropdown content within the Properties tab.

Assigns and displays a name for the property or property group.

Assigns 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.

Assigns and displays a format for properties.