Versions Compared

Key

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

Data Explorer (Reference): 

DataExplorer provides unified data discovery and monitoring across multiple protocols

Children Display
depth1
styleh3
excerptTyperich content

Introduction to the DataExplorer

Image Removed

Easily perform data mining and monitoring from various data sources like

:

  • MQTT Brokers
  • OPC-UA Servers
  • PLCs (ControlLogix, others)
  • SQL Databases
Image Removed

On this page:

Table of Contents
maxLevel2
minLevel2
indent10px
excludeSteps
stylenone


Key Concepts

and Terms

Connection Target

The connection target configuration sets up the location of the data source to be used. Typically, you can select from three types of locations:

  1. Local: This option connects automatically to some data connections defined in the solution configuration.

  2. TagProvider: This option connects with TagProvider, which are dynamic data sources created in the solution configuration.

  3. Remote: This option allows you to connect with a remote source, not necessarily used by the solution.

Connection Status

To browse data, the first step is to connect with the data source. After the connection is established, the Data Browser tree will regularly update with data from the sources.

Note: For SQL queries, the DataGrid results view will only update after you execute a query, but the connection is established automatically.

Data Browser Window

For field devices (MQTT, OPC-UA, PLCs), after the connection is established, a hierarchical tree with the data structure and values is displayed. For SQL queries, the results are shown in a DataGrid.

Export Settings to the Solution

When connecting with a remote data source not used by the solution, there are 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 DataExplorer Tools

Overview

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

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

  1. 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.
  2. 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.
  3. 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).
  4. 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 (Reference) 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 (Reference) 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 (Reference) 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 (Reference) for further information.

Three connection types available:

TypeDescriptionUse Case
LocalSolution-defined connectionsTesting existing configuration
TagProviderDynamic data sourcesConnected tag providers
RemoteExternal sourcesDiscovery and exploration

Connection Status

  • Automatic connection establishment for field devices
  • Real-time updates in Data Browser tree
  • Manual query execution for SQL sources

Data Browser Window

ProtocolDisplay TypeUpdate Method
MQTTHierarchical treeSubscribe (real-time)
OPC-UAHierarchical treePoll (1 second)
PLCsHierarchical treePoll (1 second)
SQLDataGrid tableOn query execution

Typical Workflow

1. Data Discovery

Verify data consistency across:

  • MQTT topics
  • OPC-UA nodes
  • PLC tags
  • Database tables

2. Configuration

Create from discovered data:

  • DataTemplates
  • Local tags
  • TagProviders
  • Device connections

3. Validation

Monitor and test:

  • Connection stability
  • Data quality
  • Update rates
  • Value accuracy

Tool-Specific Features

MQTT Tools

FeatureDescription
ModeClient subscriber
UpdatesReal-time via subscription
ExportTopics to tags

See MQTT Tools (Reference) for details.

OPC Tools

FeatureDescription
ModeOPC-UA client
Updates1-second polling
ExportNodes to tags

See OPC Tools (Reference) for details.

PLC Finder

FeatureDescription
DiscoveryNetwork scan
Updates1-second polling
ExportController tags

See PLC Finder (Reference) for details.

SQL Queries

FeatureDescription
ModeQuery executor
UpdatesManual execution
ExportColumn configurations

See SQL Queries (Reference) for details.


Export Options

To Solution Configuration

SourceExport TargetResult
MQTTTagProviderDynamic connection
OPCDevice ChannelCommunication setup
PLCDevice PointsMapped addresses
SQLDatasetQuery definitions

Quick Actions

  • Create Tags: Single-click tag creation
  • Build Templates: Structure to DataTemplate
  • Add Connection: Remote to solution
  • Configure Points: Bulk mapping

Performance Considerations

Explorer Limitations

AspectExplorerRuntime
Update Rate1 second fixedConfigurable
Parallel RequestsSingleMultiple
MethodPolling onlyPoll/Subscribe
VolumeLimited displayUnlimited

Runtime Capabilities

  • Parallel request processing
  • Subscribe mode (where supported)
  • AccessType prioritization
  • High-volume data handling

Best Practices

Discovery Phase

  1. Start local servers/simulators
  2. Verify network connectivity
  3. Test with small data sets
  4. Document findings

Configuration Phase

  1. Create templates before tags
  2. Use bulk import for large sets
  3. Organize with categories
  4. Test incrementally

Validation Phase

  1. Compare explorer vs runtime
  2. Monitor communication logs
  3. Verify data types
  4. Check update rates

Common Tasks

TaskToolAction
Find PLCsPLC FinderNetwork scan
Browse OPCOPC ToolsConnect and explore
Monitor MQTTMQTT ToolsSubscribe to topics
Test queriesSQL QueriesExecute and review
Create tagsAny toolRight-click export
Build templatesAny toolStructure export

Troubleshooting

Connection Issues

ProblemCauseSolution
Can't connectWrong addressVerify endpoint
No data shownSecurityCheck credentials
Slow updatesNetworkTest connectivity
Missing nodesPermissionsCheck server config

Export Problems

IssueCheckAction
Tags not createdName conflictsUse unique names
Template incompleteSelectionSelect all levels
Connection failsSettingsVerify parameters

Child Pages


See Also



In this section...

Page Tree
root@parent
spaces93DRAF

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.