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:
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 the setup of the location of the data source that will be use. Typically, you can select among 3 types of locations:
- Local Project: this option connects automatically to some data connection defined in the Project configuration
- TagProvider: this option connects with a TagProvider, which are dynamic data sources created in the Project configuration.
- Remote: this option allows you to connect with a remote source, not necessarily used by the Project.
Connection Status
In order to be able to browse data, the first step is to Connect with the data source. After the connection is established, the DataBrowser tree will regularly update with data from the sources.
The SQL queries is an exception, the DataGrid results view, only will update after you command a query, but the connection is executed automatically.
Data Browser Window
For Field Devices (MQTT, OPC-UA, PLC's), after the connection is established, am Hierarchical tree with the data structure and values of the value is displayed. For SQL queries the results are in a DataGrid.
Export Settings to the Project
When connecting with a remote Data Source, not used by the Project, there are option so with one click, you incorporate that Data Source to your application. For SQL queries, you can export your customization of DataGrid columns, to be used in operator displays.
Understanding the Data Explorer Tools
Overview
The Data Explorer tools are typically used in following phases of the Project development:
Data Discovery: if using MQTT, OPC-UA, ControlLogix PLCs, or SQL Database, the data explorer tools are a friendly and easy to use way to verify the consistency with data you intend to work with.
Templates and Tags definition: Data Templates, Local Tags, and Tag Providers, can easily be created into 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, it can be used to validate and monitor the results of the 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, or local MQTT Broker, as well run data simulators.
Select the option for Connection Target: Select the connection, either from the Project or Remote. For ControlLogix PLC's you can also search for devices in the network automatically.
Browse the data structure and data values: look the values in the TreeView explorer (OPC, MQTT, PLC's), or DataGrid (SQL Queries).
Add Connections, Data Templates Data Points, to the Unified Namespace: export server connections, data structures, os specific topics to be used by the application.
Configuring Data Explorer Tools
Configuring the MQTT Explorer
Content
Configuring the OPC-UA Explorer
Content
Configuring the Sql Query Builder
Content
Add reference to a Child Page about the Visual Query Editor
Working with the Data Explorer Tools
Data Acquistion Execution
Each Data Source has its procedure to execute the data acquisition .
Getting data from the MQTT Broker
With MQTT, the Data Browser will will act as a client application to the Broker, subscribing the data visible on the User Interface.
Getting data from the OPC -UA Server
With OPC-UA, the Data Browser will will act as a client application to the OPC Server, reading by polling every second the data visible on the User Interface.
Getting data from SQL Databases
With SQL, the DataGrid is only updated when the Execute Query command is executed.
Performance Considerations
As this is only a data explorer interface, the default cycle from update is one second, but that doesn't reflect the performance you will have runtime, which can much higher according your configuration.
For all Field Protocols (MQTT, OPC:A-UA, PLC native protocols), you can defined parallel requests, subscribing instead of polling (if the protocols allows), and use the AccessType concept, to group your data according its priority, usage in the applicaiton or process requirements.
Troubleshooting and Best Practices
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...
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