Commissioning Procedure

Commissioning Procedure of the DiagnosticCoverage_2 Function Block

1.Instantiate the FB in a program called in a main cyclic task and enable it.

2.Create a global variable, connect it to the input/output pin iq_wExeCntActl and increment it by one in each called POU. Then connect a value corresponding to the number of increments to the input i_wExeCntCfg.

3.Create 4 retained variables and connect them to the inputs i_dwAppliSignature1 to i_dwAppliSignature4. The values must be in variables since it is not possible to hard-code them in the application.

4.Connect variables or hard-coded values with the firmware version to the inputs i_bFirmVers0 to i_bFirmVers3.

5.Connect a variable or a hard-coded value corresponding to actual setting of task cycle to the input i_wTaskTime and the allowed value of maximum allowed jitter to i_wTaskJittLim.

6.Verify that the watchdog of cyclic task is enabled in the controller configuration.

7.If cross-checking of 2 controllers is required

oset i_ComTestEn to TRUE,

oset i_xComTestMstr to TRUE on the master controller, and FALSE on the slave controller (in the case of using a library-compatible controller)

oassign i_wComTestValue and i_wComDigitSum to communication inputs.

oassign q_wComTestValue and q_wComDigitSum to communication outputs.

Then do the same on the other controller and connect them both input to output.

8.If variable speed drives are used, then interlock (logical AND) the output q_xAppOk with free wheel or Quick stop inputs of device functions of variable speed drives or direction commands.

9.Download the application, read the application signature from PLC_R structure and write the values of 4 DWORD variables to the retained variables in your application.

10.Power-cycle the controller or use the i_xRst input.

11.The q_xAppOk output should be TRUE at this point. If it is not, than verify the q_wStat output to find out why it is not TRUE.

12.During commissioning you can set the input i_xTest to TRUE to bypass checking of application signature, firmware version information, execution count, cycle time test and mutual cross checking of 2 controllers. TRUE on this input will suppress the checking for 5 hours.