Device Communication
Device Communication Description
CIMON’s HMIs can connect with PLCs and other HMIs to display relevant information for the project. HMIs can connect with other devices via ethernet and USB mini as well. With these tools, users can display information from HMIs and other PLCs to help display a project more efficiently and easier to read than from reading from a PLC.
Designer Functionalities
I/O Device Editor
To access I/O Device Editor, go to Tools > I/O Device Editor, or click on the Open I/O Device Editor… on the toolbar to open it. To create a new device, click the + icon to open the Add New I/O Device screen. Users can select the ethernet or serial Connection Type for that specific device. Users can also set the Device Type, which will open a dropdown of specific devices that Canvas supports connecting to. Once selected, the I/O Device will be created with default settings.
Ethernet Device
Ethernet devices are used when the connection to another device is via an Ethernet connection. Users must input the IP of the device they are connecting to, the Ethernet Type, and the Port. Depending on the selected protocol, users can also set the PLC Type. Users can also select the String Encoding and the String Encoding Method. Users can also change settings such as the Timeout time and the Retry Count. Users will also be able to change the name of the Device and the Protocol of the device as well. Users can use a different protocol to suit the use case of a specific project; the available protocols are listed below.
Back to top of Device Communication
Back to top of Device Communication
Back to top of Device Communication
ODVA EtherNet/IP
Canvas supports ODVA EtherNet/IP as a way to connect with other devices that support this protocol. Users using this method can set the Message Type for how the message should function when connected to another device that supports ODVA EtherNe t/IP.
OPC UA Client
Canvas supports OPC UA Client as a way to connect to other devices that support this protocol. Users can Enable Encryption and enhance security for their OPC UA Client. Users can also manage specific Security Policies and change the authentication method.
Back to top of Device Communication
Serial Device
Serial Devices are used when a connection to another device is made via a serial cable. Users will need to input the Serial Port of the device they are connecting to, the Comm Type, and the Baudrate. Users can also select the String Encoding and the String Encoding Method. Users can also change settings such as the Timeout time and the Retry Count. Users will also be able to change the name of the Device and the Protocol of the device as well.
Back to top of Device Communication
Back to top of Device Communication
Back to top of Device Communication
Data Server Editor
To access the Data Server Editor, go to Tools > Data Server Editor or click the Open Data Server Editor… on the toolbar to open it. To create a new device, click the + icon to open the Add New Server Device screen. Users can select the Connection Type of ethernet or serial for that specific device. Users can also select the Device Type, which will open a dropdown of specific devices that Canvas supports connecting to. Once selected, the Data Server will be created with default settings.
Ethernet Device
Ethernet devices are used when the connection to another device is via an Ethernet connection. Users will need to input the Port of the device they are connecting to for it to connect successfully. For Modbus TCP, users will need to enter the Unit ID via Modbus to connect successfully and the String Encoding and String Encoding Method.
MQTT JSON Publisher
The MQTT JSON Publisher can be used to publish to the user and subscribe to read tag data. Users can set Subscribe Topic and Publish Topic to follow the subscribe/publishing method for MQTT JSON Publisher.
Back to top of Device Communication
Modbus TCP/RTU
Modbus TCP and RTU host memories with the following memory areas: 0, 1, 3, and 4. Users must use the MODBUS address of the address they wish to target. If, for example, the user wishes to target Y00, the tag must target 000001. Depending on the tag data type, a different range of addresses will also be allocated.
OPC UA Server
OPC UA Server tags must have a unique Browse Name. Users must set whether the Tag can be Allowed Read and Allowed Write when creating the Device Tag for the OPC UA Server.
Back to top of Device Communication
Serial Device
Serial Devices are used when a connection to another device is made via a serial cable. Users will need to input the Serial Port of the device they are connecting to, the Comm Type, and the Baudrate. Users can also select the PLC Type, the String Encoding, and the String Encoding Method. Users will also be able to change the name of the Device and the Protocol of the device as well. For Modbus TCP, users must enter the Unit ID via Modbus to connect successfully and the String Encoding and String Encoding Method. Modbus RTU is currently the only protocol for Serial Devices on Data Server Editor.
Device Tag
Device tags are used to connect tags with the server. The created server will host any tags listed within the Device Tag tab. Within the tab, addresses and other properties for each tag can be configured. Each protocol will have different settings for the Device Tag screen.
Payload Editor
Payload Editor lets users edit the MQTT message sent to the server. This will allow users to configure how payloads are configured for specific devices to match the required format. Users can configure Multi Tag Wrap Basic and Multi Tag Wrap Full as an example and change how many Tags per Payload and the Wrap Method. These can be configured within the Payload Editor as needed.
Back to top of Device Communication
Certificate Editor
The Certificate Editor is used to create and edit certificate files, which can be used to encrypt and authorize any connection to the project. Users can use this feature to add more security and encryption to their projects so that no unauthorized access can happen. Users can use their own Private Key and Certificate for their project.
Key Pairs
The Key Pairs page is where users can see their current Key Pairs. Clicking the + icon will create a new Key Pair. Users will need to insert a Name, a Certificate, a Private Key, and a Description. Users can also add a Password for the Private Key as an additional layer of security. Users will also be able to Delete and Edit any current Key Pairs they have.
Back to top of Device Communication
Trust Stores
There is also a Trust Stores tab, where users can put all known certificates they use within the project. This is where certificates will be verified by the project to confirm that they are acceptable. Users can click the + icon to create a new Trust Store. This will open the New Trust Store pop-up page. Users will need to add a Name, Certifications, and a Description. Users can Delete and Edit any Trust Stores already created.
Back to top of Device Communication