Skip to main content

Object: Data Sources Manager

Symbol: _visu_icon_data_sources.png

The object is used as a node for Data Sources below it. At least one data source has to exist. An application with the data source manager communicates with remote devices.

For more information, see: Data Link with Data Sources

Command: Add Object > Data Source

Function: The command opens the Add Data Source dialog.

. Call

  • Project Menu

  • Context menu in the Devices view in the CODESYS perspective

  • Context menu in the Data Sources view in the HMI perspective

Requirement: The Data Sources Manager object is selected that should have an additional data source.

Dialog: Add Data Source

Name

Example: Data_Source_A

Select data source type

Data source type that matches the controller configuration in order to establish communication

  • Symbolic:

    Requirement: The local device is a CODESYS HMI.

    The data is transmitted by means of symbolic monitoring. This requires that symbols are configured in the symbol configuration of the remote PLC application.

    Note: As long as the symbol configuration is not impacted by an application change, you have the advantage that the application in the local device does not have to be updated.

    Hint: Use this communication connection unless there are no resources available in the remote PLC for a symbol configuration.

  • CODESYS ApplicationV3:

    The data is transmitted via the CODESYS address protocol. This requires that the address information between the remote PLC and the local device match. Otherwise a connection cannot be established.

    Advantage: A symbol configuration is not required in the remote application.

    Note: For changes to the remote application, the local application has to be updated (for example, the HMI application).

    Hint: Use this communication for embedded or mini PLCs when there are no available resources for the symbol configuration.

  • OPC UA Server:

    Data is transferred from an OPC UA Server to the local controller via a TCP connection.

Add

Opens the Initialize Data Source – Provider Settings dialog

The contents of the dialog depend on the selected data source type.

Important

The remote PLC should be running and the remote PLC application loaded and started.

Dialog: Initialize Data Source Wizard – Provider settings (for CODESYS Symbolic)

Tip

The settings of this dialog are described here: Tab: Communication, via CODESYS Symbolic

The dialog is used to configure the connection initially when you have selected CODESYS Symbolic as the data source type. The communication is done by means of symbolic monitoring. The configuration can be modified later in the editor of the data source on the Communication Settings tab.

Dialog: Initialize Data Source Wizard – Provider settings (for CODESYS ApplicationV3)

Tip

The settings of this dialog are described here: Tab: Communication, via CODESYS ApplicationV3

The dialog is used to configure the connection initially when you have selected CODESYS ApplicationV3 as the data source type. The communication is done by means of address monitoring.

Dialog: Initialize Data Source Wizard – Provider settings (for OPC UA Server)

Tip

The settings of this dialog are described here: Tab: Communication, via OPC UA Server

The dialog is used to configure the connection initially when you have selected OPC UA Server as the data source type. The communication is established via a TCP connection.

Dialog: Initialize Data Source Wizard – Browse data items

Tip

The settings of this dialog are described here: Tab: Variables

Function: You can select the variables for data transmission from the variables of the remote PLC. By clicking Finish, the data source is initialized and the data types and variables (data interface) are declared below the folder DataSources_Objects. You can modify the settings in the editor of the data source object.

Call: Automatic

: