Baumer GK473 User Manual
Page 18
Manual_GK473_S7_Profibus_EN.doc 18/32
Baumer IVO GmbH & Co. KG
04.05.11
Villingen-Schwenningen,
Germany
BEA
//
End
current
block
KOMM: NOP
0
CALL "DPNRM_DG"
// symbol SFC13
REQ :=TRUE
LADDR :=W#16#3FE
// Diagnostic address 1022=3FEh,
// see Hardware Config Slave
RET_VAL:=MW20
// any free memory word available
RECORD :=P#DB20.DBX 0.0 BYTE 11 // Target is data block DB20,
// Start byte 0, length 6+5=11 byte
BUSY :=M1.0
// any memory bit used as Busy token;
// Repeat as long as Busy
U
M
1.0
// Call memory bit M1.0 ; set VKE correspondingly
SPB
KOMM
//
Repeat
SFC13
// As long as VKE=1 (linked result)
3.8 Organization block OB86
OB86 "Loss Of Rack Fault” is effected once (incoming and outgoing) upon DP slave alarm (with
existing external and static diagnostic data).
These events occur with station breakdown and rebooting after power loss of the DP-Slave, bus
interruption or slave alarm messages.
Incoming and outgoing events can be evaluated separately.
Organization block OB86 not inserted in the project will make the PLC stop upon occurrence of such
event.
To prevent a PLC stop it is sufficient inserting OB86 without program code.
The program in OB86 described in the following is first tracing the logic basic address of the DP-slave
the warning comes from and stores the information in memory word 5.
Further the fault ID (possible values hex. C1 to C7) is checked and stored in memory word 7.
After having checked whether it is an incoming or outgoing event the program is branching down into
several subprograms. In the following example however the same applies to both cases. The
diagnostic data (10 byte) are being consistently copied into data block DB20. There is a repetition loop
since this procedure may take several cycles and SFC13 is repeated until the operation has been
finalized (BUSY).
L
#OB86_MDL_ADDR
// Logic basic address of DP-Slaves
T MW
5
L #OB86_FLT_ID
//
Fault
ID
T MB
7