Technical data

SINAUT TD7 software package for the CPU
2.5 Data point typicals
Software
System Manual, 07/2009, C79000-G8976-C222-07
227
• Sending process typicals
(Bin04B_S, Ana04W_S, Cnt01D_S/Cnt04D_S, Dat12D_S)
Setting the parameter to 0 is useful, if PartnerNo = 0 was set. If the
PartnerObjectNo is missing, there must be a list on the partner PLC from
which the missing object number can be recognized (see FC
ListGenerator).
If the subscriber specified by PartnerNo is an ST7cc control center, the
PartnerObjectNo does not need to be specified in the FB because there
are no DBs as destination objects in ST7cc as there are in a CPU. ST7cc
decodes its messages solely based on the source address in the
message.
• Receiving process typicals
(Cmd01B_R, Set01W_R, Par12D_R)
The parameter setting PartnerObjectNo = 0 is necessary in the following
situations:
– The partner is not an S7-CPU; in other words, there is no object = DB
number. This is, for example, the case when the partner is an ST7cc
control center.
– There is more than one partner (PartnerNo = 0) that wants to send
data to this typical. The corresponding objects of these partners will
then generally have different numbers; in other words, no unique
number can be specified here.
If the PLC receives a message for the object set here, and
PartnerObjectNo is greater than 0, the system checks whether the source
object number in the message is identical to the PartnerObjectNo set
here. If they are different, the received information is discarded. An error
message to this effect is entered in the diagnostic buffer (event ID B131).
This check is not made if PartnerObjectNo = 0. Regardless of the sender
object, each message addressed to the object is also passed on to the
object.