Example program #2: Parameterization of the CycleCounter and watchdog behavior (from firmware 09)

Example program #2: Parameterization of the CycleCounter and watchdog behavior (from firmware 09) 1:

Using the sample programs

This document contains sample applications of our products for certain areas of application. The application notes provided here are based on typical features of our products and only serve as examples. The notes contained in this document explicitly do not refer to specific applications. The customer is therefore responsible for assessing and deciding whether the product is suitable for a particular application. We accept no responsibility for the completeness and correctness of the source code contained in this document. We reserve the right to modify the content of this document at any time and accept no responsibility for errors and missing information.

Example 2: Parameterization of the CycleCounter and watchdog behavior (from firmware 09)

Example program #2: Parameterization of the CycleCounter and watchdog behavior (from firmware 09) 2: Download (sample file)

In this example the behavior of a EL2262 for the CycleCounter and watchdog case is parameterized with a PLC program and a visualization (from firmware 09).

Data:

In the System Manager the SyncManager watchdog time is set to 25 ms.

Example program #2: Parameterization of the CycleCounter and watchdog behavior (from firmware 09) 3:
System Manager watchdog time

After the PLC has been started the visualization can be used to set the CycleCounter and watchdog behavior for each channel. It is loaded at the push of a button via ADS/acyclic data traffic into the registers 0x0F00/0x0F01 and is then active.

Any PDI errors counted in register 0x030D are read.

For resetting in the event of interruption of the communication the EtherCAT cable to the EL2262 can be unplugged, or the cyclic data transfer can be stopped in the visualization via the DisableEcFrameSending software parameter.

Example program #2: Parameterization of the CycleCounter and watchdog behavior (from firmware 09) 4:
PLC visualization of the example program

According to the setting from Fig. PLC visualization of the example program, this behavior of the outputs then results:

Example program #2: Parameterization of the CycleCounter and watchdog behavior (from firmware 09) 5:
Output behavior based on specific setting
Example program #2: Parameterization of the CycleCounter and watchdog behavior (from firmware 09) 6:

Using the ESC registers

If settings are loaded into ESC registers (in this case 0x0F00, for example), they are retained until they are overwritten or until the system is de-energized. If the system was de-energized, the required values have to be re-loaded into the registers.