,QIRUPDWLRQDERXWXSJUDGLQJWRD&38[&RU&38[
S7-300 Automation System CPU Specifications: CPU 31xC and CPU 31x
A5E00105475-03
8-3
7LS:
,I\RXDUHXVLQJD&38[&[ZHUHFRPPHQGWKDW\RXXVH6)%
UDWKHUWKDQ6)&'3150B'*
6)&%/.029
In the past, this SFC could be used with CPUs 312 IFM to 318-2 DP to copy data
from a non runtime-related DB.
SFC 20 no longer has this functionality with CPUs 31xC/31x. SFC83 "READ_DBL"
is now used instead.
6)&5'B'3$50
This SFC is no longer available on CPUs 31xC/31x. Instead you should use
SFC 102 "RD_DPARA", which works asynchronously.
6)&VWKDWPD\UHWXUQRWKHUUHVXOWV
You can ignore the following points if you only use logical addressing in your user
program.
If you use address conversion in your user program (SFC 5 "GADR_LGC",
SFC 49 "LGC_GADR"), you must check the assignment of the slot and logical start
address for your DP slaves.
• In the past, the diagnostic address of a DP slave was assigned to the slave's
virtual slot 2. Since DPV1 was standardized, this diagnostic address has been
assigned to virtual slot 0 (station proxy) for CPUs 31xC/31x.
• If the slave has modeled a separate slot for the interface module (e.g. CPU31x-
2 DP as an intelligent slave or IM 153), then its address is assigned to slot 2.
$FWLYDWLQJGHDFWLYDWLQJ'3VODYHVYLD6)&
With CPUs 31xC/31x, slaves that were deactivated via SFC 12 are no longer
automatically activated at the RUN to STOP transition. Now they are not activated
until they are restarted (STOP to RUN transition).
Comments to this Manuals