Table of Contents
Advertisement
Commissioning Guidelines
5th step: Load and test program
S Load the project to the SIMATIC CPU.
S Connect an SLG of the parameterized MOBY type to each MOBY channel.
S After the new start of the SIMATIC CPU (STOP → RUN), the CPU may not
assume the STOP state. If the CPU does assume STOP, continue with the
analysis of the cause. This is done by evaluating the dignostic messages of the
CPU (function: destination system – module status).
The primary causes are listed below.
– The I/O address of the modules in HW Config does not agree with
ASM_address parameterized in "MOBY FH Param" (UDT 10), or the
ASM_address does not exist for the I/O.
– A slave has failed, and OB 122 is not programmed.
S Since the default parameterization of the FC 56 is set with MDS_IO_control =
B#16#1, the presence check on the SLG must already be active now. This is
indicated by the flickering RxD LED on the ASM. If you now place an MDS in
the transmission window of an SLG, the PRE or ANW LED must go on.
If the RxD LED does not go on, continue with trouble-shooting as described in
the next point.
S Function check with the programmer
Use the "modify variable" function to indicate the state of communication
between FC 56 and ASM, examine errors and start commands. The following
figure shows the required variables. It is included in the sample project under
the name "VAT_channel_1." You can start the applicable command by setting
flag bits 1.0 to 1.7.
Figure 8-5 Variables for function check – VAT1
8-4
FC 56
J31069-D0155-U001-A0-7618
Advertisement
Table of Contents
