You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 254 Next »

Devices
(Field Communication)


Introduction to the Devices Module

The Devices module facilitates seamless real-time communication and data exchange with various field devices and industrial protocols, supporting standard interfaces like OPC-UA, OPC-DA, MQTT, and HART. 

Included in Devices

  • IT Protocols (SNMP and Ping)
  • Connections with Historian Tools (OSIsoft PI, GE Historian, InfluxDB, and Canary) 
  • 70+ Drivers 
  • 200 Communication Protocols





Key Concepts and Terms

Concept / Term

Definition

Protocols

some text - didn't hit enter

Channels

And some more

Nodes

And oh look, I hit enter, the text got bigger, then I hit backspace and removed the unneeded blank line that helped the text get bigger. Wow!

Points


AccessType

Concept / Term doesn't wrap in edit mode at this width, but in the actual page it does - so odd! How to fix this???!!!

Apparently once the left column is big, hitting enter to make a new row keeps this column with large text now - SO WEIRD! It was all small before!!!

Ugh.







Protocols

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

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 in the Solution Explorer, at Devices → Nodes.

AccessType

Each Point is associated with an AccessType, which defines the rules for reading and/or writing values for that Point. Some rules that can be set are Polling rate, whether a read is performed on startup, and whether you write values to that Point. The AccessType allows users to configure the way in which clients can access data points in the system.




Understanding the Devices Module

The Device Module collects data from the field and feeds that data into the solution's tags. 

Module Highlights

  • Simplify your 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.
  • On-Premise, Edge or enterprise level, and to/from the cloud – we have you covered!
  • MQTT Broker and OPC Server are both built-in!
  • 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

Our software supports numerous communication protocols for 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. 

→ Read more about  communication Protocols.

When using the Devices module, you can use multiple protocols simultaneously. 

→ Read more about Devices Channels.


Devices Module And ExternalTags Distinctions

While both Devices module and ExternalTags manage data points and their communication, the Devices module focuses on field device communication, whereas ExternalTags focuses on the overall management of tags within the platform environment.

Devices represent the physical equipment in the system, while ExternalTags 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 software promotes modularity, simplifies configuration, and enables users to build scalable and maintainable solutions.

→ Read more about External TagProviders



 

Configuring the Devices Module

The Device Module collects data from the field and feeds that into the solution tags.

Configuring a Device

All initial configurations for devices in the solutions on the software platform encompass the following workflow:

  1. Defining a Channel using a target communication Protocol. It will create the base instance for linking a Node Learn more at Devices - Channels.

  2. Defining the Node linked to the created Channel. Learn more at Devices Nodes.

  3. Defining the Point that you would like to monitor. Learn more at Device Points.

Protocols define communication rules between the platform and devices. Channels define global parameters for the usage of a communication protocol. Nodes represent the physical field devices (like a PLC) with a unique field address (PrimaryStation). Points represent tags within a device. Additionally, AccessType defines how the device interacts with the platform (Read and/or Write). Learn more at AccessType.

Tutorials

The Device Configuration Tutorial provides a detailed guide to configuring the Modbus interface, along with the essential concepts that apply to all communication drivers. This tutorial demonstrates how to define multiple protocol interfaces using the abstraction layers, such as Channels and Nodes, provided by the platform. You will learn the differences in syntax for the STATION and ADDRESS fields when using various protocols, as well as the configuration and testing procedures that remain consistent across all communication interfaces.

The tutorial includes an overview of device configuration features, which enable users to configure and manage industrial automation devices such as PLCs, HMIs, sensors, actuators, and others. It offers a user-friendly graphical interface for adding, removing, and configuring these devices in an automation solution. You will also explore how to configure communication parameters and tags for each device, ensuring reliable and accurate communication between devices and the automation control system.

Go to Device Configuration Tutorial →  Modbus Tutorial.




Working with the Devices Module

Runtime Execution

You can control the Devices Module execution while running your solution. You can Run, Pause, or Stop the Historian module directly from the platform. Access Runtime → Runtime Diagnostics to find the three buttons that you can use to control the module.


Intra-Module Interaction

Here are some examples of how to use this module in conjunction with other modules within the software environment:

Using Data Quality on Displays

Monitors can display and use the data quality on communication tags to ensure accurate and reliable information is being presented to operators.

Tooltip option

Data quality is a critical aspect of any HMI/SCADA system, our platform allows users to incorporate data quality on displays to provide a visual representation of data reliability, enabling operators to make well-informed decisions. This allows operators to identify potential issues and take appropriate action to maintain system performance and safety.

Simulator Drivers

The TSimulator driver is a communication protocol that allows users to generate random values in a variety of data types for testing and validation purposes. It is designed to be used with the Devices module and provides a set of flexible options that allow users to create accurate and customized simulations for their systems. TSimulator supports multiple data types, including BOOL, INTEGER, FLOAT, STRING, RAMP, and SINE. For each data type, the user can configure the minimum and maximum value that the simulation value can reach, as well as other options such as string length for the STRING type or ramp step for the RAMP type.

The TSimulator is an internal driver developed by Tatsoft, designed to work seamlessly with our software. In addition to the TSimulator, there are three external simulators available for integration with the platform. 

Simulators

  1. TSimulator (internal Tatsoft driver)
  2. OPC UA Simulator (external simulator)
  3. MQTTspB Simulator (external simulator)
  4. Modbus Protocol Simulator (external simulator)

→ Read more about TSimulator Auto Generated Values.

Unified Namespace Module

The Devices Module collects data from the field and feeds it into the solution, effectively mapping tag values to field equipment like PLC registers.

External Systems Interaction

The Devices Module is an essential component that enables seamless communication between the HMI and various devices in the industrial automation system, such as PLCs and other equipment. Each external device used with the software platform has its own communication rules defined by the manufacturer or protocol creator. The module supports multiple communication protocols and has 70+ drivers available for integration.

→ See a list of available Communication Drivers.



 

Advanced Devices Topics 

Importing PLC Addresses 

Simplify the creation of communication Nodes and Point Addresses with various methods for automatic data configuration import. Users can copy and paste tables from Excel, import data from CSV files, and employ various Import Wizards for diverse data sources. 

→ Read more about Importing PLC Addresses.

Devices Runtime Attributes

The Devices Namespace exposes properties and methods from the .NET objects used by the Device Module execution. You can use these methods to configure security attributes to protect critical data and ensure system integrity. 

→ Read more about Devices Runtime Attributes.



 

Best Practices and Troubleshooting

See the below to find our best practice recommendations for using the Devices module the most effectively. And in case you should happen to encounter any issues you will also find some troubleshooting tips below as well.

Built-in Diagnostics tools

There are three built-in tools for diagnostics of the software solution and runtime: PropertyWatch, TraceWindow and ModuleInformation.


Read information specific to Devices Diagnostics in Devices - Monitor.


Common Issues and Solutions

ControlLogix PLC Type

ControlLogix Micro850

Troubleshooting and Best Practices

Built-in Diagnostics tools

Built-In

There are three built-in Tools for diagnostics on software framework: PropertyWatch, TraceWindow and ModuleInformation.

→ Read information specific to Devices Diagnostics in Devices - Monitor.

Co

Common Issues and Solutions

ControlLogix PLC Type

ControlLogix Micro850

Importing L5K from ControlLogix

Performance

Best Practices and Recommendations

System Design

Documentation

Training

Regular Maintenance and Updates



 

What's Next?



  • No labels