Features

"Divider" NumericUpDown control

A different polling rate (divider) can be set for each slave device. Divider 1 means that the slave device is polled in each cycle. Divider 2 means that the slave device is polled every second cycle. Divider 3 means that the slave device is polled every third cycle, and so on.

"Modulo" NumericUpDown control

The modulo value can be used to distribute slave devices with a divider greater than one to different cycles, in order to shorten the maximum cycle time. A divider value of two and a modulo value of zero mean that the slave device is polled in each even cycle. A divider value of two and a modulo value of one mean that the slave device is polled in each odd cycle.

Additional Data_Exchange Samples

It is possible to specify that several DP cycles are passed though within a task cycle. Optionally, each slave device can be supplied with different output data for each DP cycle. Optionally, the input data of each DP cycle can be transferred to the controller. If data is to be exchanged in each DP cycle, then there is a separate set of variables for each DP cycle.

"Multiplier" NumericUpDown control

"Modulo" NumericUpDown control

"Parallel services" NumericUpDown control

The number of parallel ADS services for one box can be set here.

NoAnswer-Reaction

For each slave device the user can specify whether it should remain in Data Exchange state, even if it does not respond or respond incorrectly.

"Leave Data-Exch" option

The slave device should leave the Data Exchange state if it does not respond or if it responds incorrectly.

"Stay in Data-Exch (for WD-Time)" option

If the option "Stay in Data-Exch" is selected and the watchdog is enabled, the data exchange is only exited if the slave device has never responded correctly within the response monitoring time. If the option "Stay in Data-Exch" is selected and the watchdog is not enabled, data exchange is only terminated if the slave device has not responded correctly 65,535 times.

Restart Behavior of the Slave

For each slave device the user can specify whether the device should automatically start up again after leaving the Data Exchange state or whether it should remain in the Wait-Prm state.

"Automatic Restart" option

The slave device should automatically start up again after leaving the Data Exchange state.

"Manual Restart" option

The slave device should remain in the Wait-Prm state after leaving the Data Exchange state. A restart must be carried out manually.

"No Reaction" option

The PROFIBUS cycle is not stopped after the slave device has left the Data Exchange state.

"Stop All Slaves" option

For each slave device the user can specify whether the PROFIBUS cycle should be stopped after it has left the Data Exchange state. FC310x: All slave devices leave the data exchange and enter the Wait-Prm state. For a restart, an IO reset or a restart of the TwinCAT system must be carried out. EL6731: The terminal enters the PREOP state. A restart is triggered by switching to OP state.

Changes of the Input Data

For each slave device the user can specify whether the input data of the slave device should be set to zero or remain unchanged when the device leaves the Data Exchange state. On leaving the Data Exchange state, the DpState is not equal to zero.

"Inputs will be set to 0" option

When the slave device leaves the Data Exchange state, the input data of the slave device is set to zero.

"No Changes" option

When the slave device leaves the Data Exchange state, the input data of the slave device remain unchanged.