| HTML |
|---|
<style>
.text-span-6 {
background-image: linear-gradient(99deg, rgba(170, 163, 239, .5), rgba(125, 203, 207, .5));
border-radius: 50px;
padding-left: 15px;
padding-right: 15px;
}
#title-text {
display: none;
}
.panelgradient {
background-image: linear-gradient(180deg, #d5def0, whitesmoke);
border-radius: 8px;
flex-direction: column;
justify-content: center;
align-items: center;
padding: 4rem;
display: flex;
position: relative;
}
</style>
<div class ="panelgradient">
<h1 style="text-align: center;">DataExplorer Tools<br> (OPC, MQTT, PLCs, SQL)</h1>
</div> |
Introduction to the DataExplorer
Easily perform data mining and monitoring from various data sources like:
- MQTT Brokers
- OPC-UA
- PLCs
- SQL Databases
Introduction
The DataExplore tools allows you to easily perform data mining and monitoring from various data sources, including MQTT Brokers, OPC-UA, PLCs and SQL databases.
Each Data Source has specific features suitable that connection, but all tools share common look and fell, and similar workflows. This section will present those common workflows, and the specific features for each connection type, which include:
MQTT: Run Built-in Broker or the publisher simulator. Browse data from any broker.
OPC-UA: Run Built-in Server or simulator. Browse data from local or remote servers.
ControlLogix PLCs: Discover ControlLogix PLC in your network, connect to browse its data structure.
SQL Queries: Explore SQL database and build new queries visually.
On this page:
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
Key Concepts and Terms
Purpose and Key Concepts
The purpose of the DataExplorer tools is the allow engineers to very the data sources they intend to user the project, as well test and verify the data of the connection in use..Connection Target
The connection target configuration is sets up the setup of the location of the data source that will to be useused. Typically, you can select among 3 from three types of locations:
Local
:
This option connects automatically to some data
connections defined in the
solution configuration.
TagProvider:
This option connects with
TagProvider, which are dynamic data sources created in the
solution configuration.
Remote:
This option allows you to connect with a remote source, not necessarily used by the
solution.
Connection Status
In order to be able to To browse data, the first step is to Connect connect with the data source. After the connection is established, the DataBrowser Data Browser tree will regularly update with data from the sources.
The Note: For SQL queries is an exception, the DataGrid results view , will only will update after you command execute a query, but the connection is executed established automatically.
Data Browser Window
For Field Devices field devices (MQTT, OPC-UA, PLC'sPLCs), after the connection is established, am Hierarchical a hierarchical tree with the data structure and values of the value is displayed. For SQL queries, the results are shown in a DataGrid.
Export Settings to the
ProjectSolution
When connecting with a remote Data Source, data source not used by the Projectsolution, there are option so with one click, you incorporate that Data Source to your application. For options to incorporate that data source into your application with one click. For SQL queries, you can export your customization of DataGrid columns , to be used in operator displays.
MQTT Broker
OPC Server
TagProvider
Understanding the Data Browsing tools
Run Simulators or Local Servers, as needed
Content
Select the option for Data Served Connection
Content
Browse the Data Structure and Values of the ServerContent
Add Connections, or Data Points, to the Unified NamespaceContent
Configuring Data Explorer tools
Configuration Workflow
Content
Configuring the MQTT Explorer
Content
Configuring the OPC Explorer
Content
Working with the Data Explorer Tools
Runtime Execution
Content
Navigating the Data Models
Content
Troubleshooting and Best Practices
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
Troubleshooting and Common #Issues
The Historian module may encounter some issues in its operation. Here are some common issues and their troubleshooting:
#Issue
Solution
Best Practices and #Recommendations
To ensure the smooth operation of the Historian module, follow these best practices:
#Best practice
Recommendations
In this section...
| Page Tree | ||||
|---|---|---|---|---|
|
Understanding the DataExplorer Tools
Overview
The DataExplorer tools are typically used in the following phases of project development:
- Data Discovery: Whether using MQTT, OPC-UA, ControlLogix PLCs, or SQL Databases, the DataExplorer tools provide a user-friendly and easy way to verify the consistency of the data you intend to work with.
- DataTemplates and Tags Definition: DataTemplates, local Tag, and TagProviders can be easily created in the project configuration using the data displayed in the Data Browser window.
- Testing and Validation: When used in conjunction with connections already defined in the project configuration, these tools can be used to validate and monitor the results of data acquisition.
Typical Workflow
- Start Servers or Simulators: When using MQTT or OPC, you have the option to use the built-in OPC-UA server, the local MQTT broker, or run data simulators.
- Select the Option for Connection Target: Select the connection, either from the project or remote sources. For ControlLogix PLCs, you can also search for devices in the network automatically.
- Browse the Data Structure and Values: View the values in the TreeView explorer (for OPC, MQTT, and PLCs) or in the DataGrid (for SQL queries).
- Add Connections, DataTemplates, or DevicesPoints to the Unified Namespace: Export server connections, data structures, or specific topics to be used by the application.
Working with the DataExplorer Tools
Each data source has its own procedure to execute data acquisition.
MQTT Tools
With MQTT, the Data Browser will act as a client application to the broker, subscribing to the data visible on the user interface.
Follow the link MQTT Tools for further information.
OPC Tools
With OPC-UA, the Data Browser will act as a client application to the OPC server, reading the data visible on the user interface by polling every second.
Follow the link OPC Tools for further information.
PLC Finder
With PLCs, the Data Browser will send protocol request to the PLC, reading the data visible on the user interface by polling every second.
Follow the link PLC Finder for further information.
SQL Queries
With SQL Databases, the DataGrid is only updated when the Execute Query command is executed.
Follow the link SQL Queries for further information.
Performance Considerations
As this is only a DataExplorer interface, the default update cycle is one second. However, this does not reflect the performance you will experience at runtime, which can be much higher depending on your configuration.
For all field protocols (MQTT, OPC-UA, PLC native protocols), you can define parallel requests, subscribe instead of poll (if the protocol allows), and use the AccessType concept to group your data according to its priority, usage in the application, or process requirements. The volume of data and performance the project can manage at runtime is significantly higher than that of the DataExplorer tools.
In this section:
| Page Tree | ||||
|---|---|---|---|---|
|
NEW ORGANIZATION
About the Data Explorer Tools
Content
Key Concepts and Terminology
Connection Target
* MQTT Broker
* OPC Server
* TagProvider
How the Data Browsing Tools Work
Run Simulators or Local Servers, as needed
Select the option for Data Served Connection
Browse the Data Structure and Values of the Server
Add Connections, or Data Points, to the Unified Namespace
Configuring the MQTT Explorer
Configuring the OPC Explorer
Working with the Data Explorer Tools
* Runtime Execution
* Navigating the Data Models
Troubleshooting and Best Practices
* Common Issues and Solutions
* Best Practices and Recommendations