Setting Up Modbus Network (Scenarios)

When setting up a network, various settings are necessary in order to connect devices to each other and exchange data. The steps necessary for configuration depend on the application, and, thus on the devices used and their roles as master or slave.

Note

Note the naming conventions for distinguishing different programmable devices:

Controller
In what follows, devices that can be programmed under CODESYS V3 or e!COCKPIT (such as most PFCs) are referred to simply as “controllers.”
The scenarios described for “controller (master)” devices also apply to Touch Panels 600 if they act as control panels, i.e. if they have a corresponding license (provided by the vendor or added subsequently).

Controller (CODESYS V2)
The term “controller (CODESYS V2)” is used for those controllers that are programmed with CODESYS V2 outside of e!COCKPIT (for example, 750-881 Controllers).

The following applications will be considered:

The procedure described below for the individual applications represent the general process for performing the configuration.
The order may vary. Depending on the communicating device selected, individual steps may be largely or entirely omitted.

  1. Select Devices
    For devices in e!COCKPIT to be used, they must be known devices in e!COCKPIT, i.e. be available in the product catalog. Once e!COCKPIT is installed, WAGO devices are automatically available in the product catalog. Third-party devices that function as a master or slave are represented in e!COCKPIT by generic devices. These are also available in the product catalog.
  2. Place Devices in the Communication View
    Devices are scanned or dragged from the product catalog into the communication view.
  3. Configure the I/O Modules Used in the Device Detail View
    If the device has I/O modules, they can be added automatically through a scan and displayed in the Device Detail view. Alternatively, I/O modules can also be placed in the Device Detail view directly from the product catalog even without an online connection.
    Note: Third-party devices cannot be scanned.
  4. Connect Devices
    Devices are connected on the communication layer through connectors. If unique assignment of the “master” and “slave” roles is possible based on the device, this is performed automatically. The arrow on the connection line points from the master to the slave.
    Note:If a connection is established between devices that can play both roles, the direction of communication cannot be determined automatically. In this case, the connection order is used (starting point = master → endpoint = slave). However, the direction of communication can be changed subsequently at any time.
  5. Set the Protocol for the Connection
    Select TCP or UDP from the context menu of the connector/connection.
  6. Make the Device Settings on the “Settings” Panel
    The device settings on the “Settings” panel are displayed in a context-sensitive way for the specific selected device and its communication interfaces and can be modified as needed.
  7. Program Application
    In the Device Detail view, the I/O map is created between the local bus and application variables, and the applications are programmed
    Note: This step is only relevant for controllers.
  8. Configure Slave
    Slave data points can be created and configured in the data point configurator. These are published and thus available to the master (see also Slave Settings in the Data Point Configurator).
    Note: This step is omitted if the controller (CODESYS V2) or fieldbus coupler is used as a slave, since in this case, the data points do not result automatically from the programming, but are instead created automatically from the hardware configuration. For these devices, and for third-party devices, only additional data points, so-called “generic data points,” can be created. These are not made available by default. They allow access to large data structures, for example. However, this requires detailed configurations (data types, size etc.). Variables of the third-party device can also be created/modified in batches through a CSV file (menu ribbon, “DEVICE” tab > [Export]/[Import]).
  9. Configure Connection between Master and Slave
    In the fieldbus configurator, you can set the communication relation on the data point level. This determines what slave data points should be available to the master in what form and what transmission quality should be used for communication, e.g. update rate, access time type (see also Master and Connection Settings in the Fieldbus Configurator).
    Note: This step is omitted for third-party devices used as the master.
  10. Access Data Points
    Slave data points that have been created can be accessed from the master’s application.