Master interface settings
Note
Pay attention to the effects of the autoconfiguration mode!
Autoconfiguration mode is enabled by default and is suitable for most applications. Because many configurations are done automatically, some tabs for the Data Point Configurator are irrelevant or unavailable in this mode. This affects the “FMMU/Sync” tab and the Sync-Manager.
It may happen that you need to disable the autoconfiguration mode, for example, to configure slave-to-slave communication. Note that expert knowledge is required in this case because you must manually make all master and slave configuration settings.
Parameters | Value | Description |
|---|---|---|
Autoconfig master/slaves |
| Most of the master and slave configuration is done automatically based on device description files and implicit calculations. The “FMMU/Sync” tab and Sync-Manager are not available in the Data Point Configurator. Even if this option of the master is activated, the expert mode can be explicitly activated for each individual slave. The expert mode allows manual editing of the automatically generated process data configuration. |
| The configuration settings for master(s) and slave(s) mostly have to be done manually. | |
EtherCAT NIC Settings | ||
Destination address (MAC) | FF-FF-FF-FF-FF-FF | MAC ID of the subscriber in the EtherCAT network that the telegram should receive Recommendation: To remain device-independent, it makes sense not to specify a fixed MAC ID at this point. Use network names instead (see options below). |
Broadcast |
| No target address (MAC) has to be specified. |
| The target address (MAC) is used. | |
Redundancy |
| The bus is redundant (applies if the bus is structured as a ring topology). Note: This function is not currently supported by WAGO devices. Settings in the “Redundancy EtherCAT NIC Settings” area, therefore have no effect. |
| The bus is not supported redundantly. | |
Source address (MAC) | 00-00-00-00-00-00 | MAC ID of the controller (target system) or network name Note: “Select network by name” is enabled by default For this reason, the setting remains “00-00-00-00-00-00”. Recommendation: To remain device-independent, it makes sense not to specify a fixed MAC ID at this point. Use network names instead (see options below). |
[Browse...] |
| The MAC ID or name of available target devices are used to search for the network. |
Network name | br1 | Name or MAC ID of the network depending on which of the following options is enabled. “br1” is preset and identifies the ETHERNET bridge used for EtherCAT. The device port used for EtherCAT must be set to “separated”. Since only port X2 is allowed for EtherCAT, it forms the EtherCAT bridge “br1” that is selected in this case. |
Select network by MAC | The network is specified by the MAC ID. The project cannot be used on another device because every network adapter has a unique MAC ID. This setting is not recommended. | |
Select network by name | The network is identified by the network name (preset by default). | |
Redundancy EtherCAT NIC Settings | ||
This area opens if the “Redundancy” function has been selected. Note: WAGO devices do not currently support redundancy. | ||
Distributed Clocks | ||
Cycle time | 100 … 1000000 μs | Time after which a new data telegram is sent on the bus. If the “Distributed Clocks” functionality is enabled on the slave, the specified master cycle time is applied to the slave clocks. Precise synchronization of the data exchange can be achieved in this way, which is especially important when spatially distributed processes require simultaneous actions. Simultaneous actions are e.g., applications in which multiple axes must execute coordinated movements simultaneously. A very precise, network-wide time base with jitter much less than 1 microsecond can be achieved in this way. |
Sync Offset | -50 … 50 % | Makes it possible to set the time delay of the sync interrupt of the EtherCAT slave against the cycle time of the PLC. Normally, the PLC cycle starts 20 % later than the sync interrupt of the slave. This means that the PLC cycle could be delayed by 80 % of the cycle time without a message being lost. |
Sync window monitoring |
| Synchronization of the slave is monitored. |
| The slave is not synchronized. | |
Sync window | 1 … 32758 μs | Time for Sync Window Monitoring If the synchronization of all slaves is within this time window, the “xSyncInWindow (IoDrvEthercat)” variable is set to TRUE. Otherwise, it is set to FALSE. |
Options | ||
Use LRW instead of LWR/LRD |
| Direct communication from slave to slave is possible via combined read/write commands (LRW). |
| Read (LRD) and write (LWR) commands are used separately. | |
Messages per task |
| Various tasks can be used to control read and write commands, i.e., handling of input/output messages. |
| A task is used to control read and write commands. | |
Automatically restart slaves |
| Master tries to restart the slaves immediately after a communication interruption. |
| There is not automatic restart after a communication interruption. | |
Master Settings | ||
These additional settings are opened when autoconfiguration mode is disabled at the top of the dialog box (“Autoconfig Master/Slaves”). Otherwise, the settings are applied automatically. | ||
Image In Address | 16#1 … 16#1FFFFFFF | First logical address of the first slave for input data |
Image Out Address | 16#1 … 16#1FFFFFFF | First logical address of the first slave for output data |
Diagnostic message | ||
Diagnostic messages are displayed in online mode only. Other diagnostic messages are available in the fieldbus configurator in the “Status” tab. | ||
Diagnostic message | - | The “Diagnostics messages” field displays the status of the master. Possible status include “Init”, “Pre-Operational”, “Save Operational” and “Operational”. |
Bus load | 0 … 100 % | Indication of the bus load in percent |
