Devices Functionality

The Devices module facilitates seamless communication and data exchange with various field devices and industrial protocols, simplifying system architecture and enhancing connectivity, collecting data from the field, and feeding that data into the solution's tags.

Feature Highlights

• Simplify the solution architecture by removing the need for additional communication products.
• Easily set up a communications hub to support communications and logic between practically any device, database, historian, or anywhere.
• The Devices Module covers On-Premise, Edge or enterprise level, and to/from the cloud.
• MQTT Broker and OPC Server are both built-in to the Device module.
• MQTT SparkPlug B and OPC-UA simulators expedite demos and prototyping.
• Driver Toolkit allows our team, or any third party, to add new interfaces easily.

Implementing Communication Protocols

The software supports numerous communication protocols for Human Machine Interface (HMI) and industrial device interaction. The platform also promotes open communication standards, like OPC, but there are various benefits to having the native protocol implementation. When using the platform, you don't need to understand the protocol implementation details because you can easily map the devices and the information you want to read or write from the device. However, you want to understand a communication protocol and how it is implemented in the system. In that case, you can refer to the page Protocols.

When using the Devices module, you can use multiple protocols simultaneously. The selection of the protocols is explained in Device Channels.

Handling Read And Write Events

Handling read and write events in a SCADA system is crucial for efficiently exchanging data between the HMI, PLCs, and other devices. The platform facilitates these events by allowing users to configure access types, which define the specific methods for reading and writing the values of each data point. The access types can be configured to determine the polling rate, specify whether a read is performed on startup, and decide whether unsolicited input is accepted.

The page Access Types Configuration has a detailed explanation of the concepts of development and execution of communication drivers.

Devices Module And External Tags Distinctions

While the Devices module and External Tags manage data points and their communication, the Devices module focuses on field device communication. In contrast, External Tags concentrate on the overall management of tags within the platform environment.

Devices represent the physical equipment in the system. At the same time, External Tags are the logical entities that store and manage tag information. Understanding the distinction between these two components is essential for effective system configuration and management. By clearly separating the responsibilities of these components, the software promotes modularity, simplifies setup, and enables users to build scalable and maintainable solutions.

You can see External Tag Providers for more information.

Main Components

To configure the Devices module, you need to understand five main components:

• Protocols
• Channels
• Nodes
• Points
• Access Type

You can find a brief description of each feature below.

Protocols

Protocols are the rules governing the communication between devices. Our software supports a variety of communication protocols.

Channels

Channels are created and configured to handle specific communication protocols and drivers. Each channel is defined by a specific protocol driver and connection type, such as RS-232 or TCP/IP. Channels allow the module to access multiple devices, such as PLCs, using the defined protocol and interface.

Nodes

Each device connected to the system through channels is called a Node. Nodes can be individual devices or groups of devices. Each node contains one or more Points.

Points

Points are individual items that can be read or written from/to nodes. They can be registers, I/O values, or variables residing in field devices (nodes). Each Point is bound to a specific Tag in the solution configuration.

AccessType

Each Point is associated with an Access Type, which defines the rules for reading and writing values for that Point. The polling rate value, whether a read is performed on startup, and whether you write values to a specific Point are examples of rules you can specify. The Access Type allows users to configure how clients can access data points in the system.

Configuring the Devices Module

The basic process to configure the Device module follows the sequence below:

1. First, create channels to handle the protocols and drivers used when accessing the devices. Learn more at Device Channels.
2. Create Nodes according to the devices you will be transmitting to and receiving data from. Access the Device Nodes page to learn more about it.
3. Once your Nodes are ready, you can set Device Points bound to a specific Tag to read or write data on the Nodes. Learn more at Device Points.
4. Then, create Access Types bound to Points to set the rules for writing or reading the data. Vists the Access Types page to read more details.
5. Use the Device Monitor to supervise your Devices on Runtime. Check the Devices Monitor page for more information.

The above steps are a simplified explanation of the configuration process. For additional information on configuring the Historian module, access Configuring The Devices Module.

More on the Devices Module

To learn more about the Devices module, you can use the additional documentation pages that are available.

• Learn how to use the Devices module and others by accessing the Working with the Devices Module page.

The Advanced Devices Topics page presents complementary information about the following:

• Importing PLC Addresses
• Devices Runtime attributes

Use the Devices Best Practices and Common Issues pages to access best practices tips and troubleshooting guides.

In this section: