Introduction to Devices module
The Devices module implements real-item data communication with a wide variety of field devices and industrial protocols, supporting standard interfaces like OPC-UA, OPC-DA and MQTT and Hart.
The connectivity also includes IT protocols, like SNMP and Ping, and connection with Historian tools, such as OSIsoft PI, GE Historian, InfluxDB and Canary.
Currently over 50 drivers are included in the platform, and our development team has experience with more than 200 communication protocols.
On this page:
Table of Contents maxLevel 3 style none
Devices Functionality
The Device Module collects data from the field and feeds that data into the solution's tags.
Feature Highlights
Simplify the solution architecture by removing the needing for additional communication products.
Easily setup a communications hub to support comms and logic between practically any device, any database, any historian, anywhere.
The Devices modules covers On-Premise, Edge or enterprise level, and to/from the cloud.
MQTT Broker and OPC Server are both built-in in the Device module.
MQTT SparkPlug B and OPC-UA simulators expedite demos and prototyping.
Driver Toolkit allows our team, or any third-party, to easily add new interfaces.
Implementing Communication Protocols
The software supports numerous communication protocols for Human Machine Interface (HMI) and industrial device interaction. The platform also supports open communication standards, like OPC, but there are various benefits in having the native protocol implementation. When using the platform, you don't need to understand the details of the protocol implementation because you can easily map the devices and the information you want to read or write from the device. However, if you want to have a deeper understanding of what a communication protocol is and how they are implemented in the system, 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
In a SCADA system, handling read and write events is crucial for the efficient exchange of data between the HMI, PLCs, and other devices. Our software 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 ExternalTags External Tags Distinctions
While both Devices module and ExternalTags External Tags manage data points and their communication, the Devices module focuses on field device communication, whereas ExternalTags External Tags focuses on the overall management of tags within the platform environment.
Devices represent the physical equipment in the system, while ExternalTags 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, our the software promotes modularity, simplifies configuration, and enables users to build scalable and maintainable solutions.
You can see External TagProvidersTag Providers for more information.
Purpose and Key Concepts
The Devices module facilitates seamless communication and data exchange with various field devices and industrial protocols, simplifying system architecture and enhancing connectivity. The configuration of the Devices module is performed on the sectionsin five levels:
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. The configuration of Channels is on the Solution Explorer, at Devices → Channels.
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. The configuration of Nodes is on the Solution Explorer, at Devices → Nodes.
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 solution configuration.
AccessType
Each Point is associated with an AccessTypeAccess Type, which defines the rules for reading and/or writing values for that Point, such as the . The polling rate value, whether a read is performed on startup, and whether you write values to that Pointa specific Point are exemples of rules you can specify. The AccessType Access Type allows users to configure how clients can access data points in the system.
Configuring the Devices module
Add sequence and link to Configuring page.
More on the Devices Module
Use the Historian Module as base and do the same.
In this section:
| Page Tree | ||||
|---|---|---|---|---|
|
...