Versions Compared

Old Version 27

changes.mady.by.user Paulo Tsuchiya

Saved on

compared with

New Version Current

changes.mady.by.user admin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


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

Image Added

Easily perform data mining and monitoring from various data sources like:

  • MQTT Brokers
  • OPC-UA
  • PLCs
  • SQL Databases

Image Added

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
maxLevel3
minLevel2
stylenone


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..

and Terms

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:

  1. Local

Project

  1. :

this

  1. This option connects automatically to some data

connection

  1. connections defined in the

Project configuration ExternalTags: this

  1. solution configuration.

  2. TagProvider: This option connects with

a ExternalTags

  1. TagProvider, which are dynamic data sources created in the

Project

  1. solution configuration.

 

  2. Remote:

this

  1. This option allows you to connect with a remote source, not necessarily used by the

Project

  1. 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

Project

Solution

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. 

Understanding the

Data Explorer

DataExplorer Tools

Overview

The Data Explorer DataExplorer tools are typically used in the following phases of the Project project development:

  1. Data Discovery:
 if
  1. Whether using MQTT, OPC-UA, ControlLogix PLCs, or SQL
Database
  1. Databases, the
data explorer
  1. DataExplorer tools
are
  1. provide a user-friendly and easy
to use
  1. way to verify the consistency
with
  1. of the data you intend to work with.
Templates
  1. DataTemplates and Tags
definition
  1. Definition:
Data Templates, Local Tags
  1. DataTemplates, local Tag, and
Tag Providers,
  1. TagProviders can be easily
be
  1. created
into
  1. in the
Project Configuration
  1. project configuration using the data displayed in the
data browser
  1. Data Browser window.
  2. Testing and Validation:
 
  1. When used in conjunction with connections already defined in the
Project
  1. project configuration,
it
  1. these tools can be used to validate and monitor the results of
the
  1. data acquisition.
 

Typical Workflow

  1. Start Servers or Simulators:
 when
  1. When using MQTT or OPC, you have the option to use the built-in OPC-UA server,
or
  1. the local MQTT
Broker
  1. broker,
as well
  1. or run data simulators.
  2. Select the
option
  1. Option for Connection Target:
 
  1. Select the connection, either from the
Project
  1. project or
Remote
  1. remote sources. For ControlLogix
PLC's
  1. PLCs, you can also search for devices in the network automatically.
  2. Browse the
data structure and data values: look
  1. Data Structure and Values: View the values in the TreeView explorer (for OPC, MQTT,
PLC's
  1. and PLCs)
,
  1. or in the DataGrid (for SQL
Queries
  1. queries).
  2. Add Connections,
Data Templates or Points,
  1. DataTemplates, or DevicesPoints to the Unified Namespace:
export
  1. Export server connections, data structures,
os
  1. or 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

DataExplorer Tools

Data Acquisition Execution

Each Data Source Each data source has its own procedure to execute the data acquisition.

Getting data from the

MQTT

Broker

Tools

With MQTT, the Data Browser will will act as a client application to the Brokerbroker, subscribing to the data visible on the User Interfaceuser interface.

Getting data from the OPC -UA Server

Follow the link MQTT Tools for further information.

OPC Tools

With OPC-UA, the Data Browser will will act as a client application to the OPC Serverserver, 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.  

Getting data from SQL Databases

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 data explorer interfaceDataExplorer interface, the default update cycle from update is one second, but that doesn't . However, this does not reflect the performance you will have experience at runtime, which can be much higher according depending on your configuration. 

For all Field Protocols field protocols (MQTT, OPC:A-UA, PLC native protocols), you can defined define parallel requests, subscribing subscribe instead of polling poll (if the protocols protocol allows), and use the AccessType concept , to group your data according to its priority, usage in the application, or process requirements.  There the The volume of data and performance the Project project can manage in Runtime at runtime is way significantly higher than the ones at the data explroer tools.

Troubleshooting and Best Practices

Table of Contents
maxLevel4
minLevel3
include#

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

that of the DataExplorer tools.

In this section:

Page Tree
root@parent@self
spaces93DRAFV10