Data Explorer (Reference):
DataExplorer provides unified data discovery and monitoring across multiple protocols
Children Display | ||||||
---|---|---|---|---|---|---|
|
:
Parent Page:Designer (Reference)
Table of Contents maxLevel 2 minLevel 2 indent 10px exclude Steps style none
The connection target configuration sets up the location of the data source to be used. Typically, you can select 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.
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.
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.
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.
The DataExplorer tools are typically used in the following phases of project development:
Each data source has its own procedure to execute data acquisition.
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.
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.
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.
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:
Type | Description | Use Case |
---|---|---|
Local | Solution-defined connections | Testing existing configuration |
TagProvider | Dynamic data sources | Connected tag providers |
Remote | External sources | Discovery and exploration |
Protocol | Display Type | Update Method |
---|---|---|
MQTT | Hierarchical tree | Subscribe (real-time) |
OPC-UA | Hierarchical tree | Poll (1 second) |
PLCs | Hierarchical tree | Poll (1 second) |
SQL | DataGrid table | On query execution |
Verify data consistency across:
Create from discovered data:
Monitor and test:
Feature | Description |
---|---|
Mode | Client subscriber |
Updates | Real-time via subscription |
Export | Topics to tags |
See MQTT Tools (Reference) for details.
Feature | Description |
---|---|
Mode | OPC-UA client |
Updates | 1-second polling |
Export | Nodes to tags |
See OPC Tools (Reference) for details.
Feature | Description |
---|---|
Discovery | Network scan |
Updates | 1-second polling |
Export | Controller tags |
See PLC Finder (Reference) for details.
Feature | Description |
---|---|
Mode | Query executor |
Updates | Manual execution |
Export | Column configurations |
See SQL Queries (Reference) for details.
Source | Export Target | Result |
---|---|---|
MQTT | TagProvider | Dynamic connection |
OPC | Device Channel | Communication setup |
PLC | Device Points | Mapped addresses |
SQL | Dataset | Query definitions |
Aspect | Explorer | Runtime |
---|---|---|
Update Rate | 1 second fixed | Configurable |
Parallel Requests | Single | Multiple |
Method | Polling only | Poll/Subscribe |
Volume | Limited display | Unlimited |
Task | Tool | Action |
---|---|---|
Find PLCs | PLC Finder | Network scan |
Browse OPC | OPC Tools | Connect and explore |
Monitor MQTT | MQTT Tools | Subscribe to topics |
Test queries | SQL Queries | Execute and review |
Create tags | Any tool | Right-click export |
Build templates | Any tool | Structure export |
Problem | Cause | Solution |
---|---|---|
Can't connect | Wrong address | Verify endpoint |
No data shown | Security | Check credentials |
Slow updates | Network | Test connectivity |
Missing nodes | Permissions | Check server config |
Issue | Check | Action |
---|---|---|
Tags not created | Name conflicts | Use unique names |
Template incomplete | Selection | Select all levels |
Connection fails | Settings | Verify parameters |
Page Tree | ||||
---|---|---|---|---|
|
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.