Configuring Hardware and Communication Connections STEP 7.pdf

Configuring the Distributed I/O (DP)
New SFBs and SFCs for Accessing DPV1 Slaves
In order to make the topic more comprehensive, the table below shows - wherever
possible - the new interfaces and their functions compared with previous interfaces.
You can find detailed information in the descriptions of the SFBs/SFCs and new
OBs. A conversion of existing configurations to the new SFBs/SFCs is not
necessarily required. However, you should use the new SFCs/SFBs when you
create new projects with a DPV1 configuration to be able to use all DPV1 functions.
Function Previous Interface New Interface (DPV1) Comments
Read Data Record SFC 59 RD_REC SFB 52 RDREC -
Write Data Record SFC 58 WR_REC SFB 53 WRREC -
Receive interrupt from - SFB 54 RALRM The SFB must be called in the OB
a DP Slave
that is triggered by the interrupt.
Hinweis
Wenn ein DPV1-Slave über GSD-Datei projektiert ist (GSD ab Rev. 3) und die
DP-Schnittstelle des DP-Masters ist auf "S7-kompatibel" eingestellt, dürfen im
Anwenderprogramm keine Datensätze mit SFC 58/59 bzw. SFB 53/52 von den
E/A-Baugruppen gelesen bzw. beschrieben werden. Der DP-Master adressiert in
diesem Fall den falschen Steckplatz (projektierter Steckplatz+3).
Abhilfe: Schnittstelle des DP-Masters auf "DPV1" umstellen.
Checklist for Testing Existing User Programs
The following sections of your existing user program must be checked if you have
edited the configuration with STEP 7 V5.1, Service Pack 2 and if you have
switched to "DPV1":
Function What is to be checked?
Address
conversion
Reading
Diagnostics with
SFC 13
Reading/Writing
Data Records
For DP Slaves configured via GSD files you must check the assignments Slot
Logic Start Address, if you have used address conversion in the user program
(SFC 5, SFC 49, SFC 50). Slot 0 has an additional address.
• DP Slave implemented via GSD File:
Previously the first I/O module of the DP Slave was assigned to slot 4. However,
the first I/O module is now assigned to slot (as you can see in the hardware
configuration).
• DP Slave integrated in STEP 7 (for example, ET 200M):
the interface module (slot 2) has its own address.
The originally assigned diagnostic address still functions. STEP 7 assigns this
address internally to slot 0.
However, the diagnostic data record of DPV1 Slaves has a different structure (refer to
the description of DP Slaves. With ET 200M, for example, also refer to the keyword
"Extended Diagnostics").
If you transfer data records to a DPV1 slave with SFC58 "WR_REC" or if you fetch
data records from a DPV1 slave with SFC59 "RD_REC" and if this DPV1 slave
operates in DPV1 mode, the DP Master evaluates the error information it received
from the Slave as follows: If the error information lies within the range from
W#16#8000 to W#16#80FF or W#16#F000 to W#16#FFFF the DP master passes
the error information to the SFC. If it lies out of this range, the CPU passes the value
W#16#80A2 to the SFC and suspends the slave. For a description of the error
information received from DPV1-Slaves, see Receiving an Interrupt from a DP-Slave
with SFB 54 "RALRM" STATUS[3].
See also: Jumps to Language Descriptions and Help on Blocks, System Attributes
Configuring Hardware and Communication Connections with STEP 7
3-62 A5E00706939-01