Technical data

SINAUT TD7 software package for the CPU
2.6 Blocks for optional expansion
Software
290 System Manual, 07/2009, C79000-G8976-C222-07
Name: NewData
Refer to
Parameters you require often (Page 223).
Explanation
of the
typical-
specific
outputs
Whenever the FB has received new data and has stored it in the data area
defined by DataOutput, the NewData output is set to TRUE for one OB1
cycle.
2.6 Blocks for optional expansion
2.6.1 FC ListGenerator300, FC ListGenerator400
Function
The FC ListGenerator is required in a CPU that receives messages containing either an
incomplete destination address or no destination address at all. The lack of the destination
object number is the most important factor here because this points to the instance DB in
which the received information should be stored. Missing or incomplete destination
addresses can occur when no or incomplete parameters are set for them in the station (this
is permitted for typicals that send binary information, analog values or counted values). If
these typicals send data to more than one destination, no destination address is set for these
typicals. Due to the missing destination information, the send message is automatically
transmitted to all destinations for which a connection is configured. Such messages are
therefore received without a destination address at the various destinations.
Note
Messages without a destination address that are sent to the partner over a TIM have the
destination subscriber number added by the sending TIM, and sometimes several addresses
if there are several destinations along the way. The TIM enters 0 in the address field for the
destination object number, since the TIM does not have the relevant information. The only
destination subscribers it knows are those to which it has a configured connection. At the
receiving end, the message therefore contains the destination subscriber number but the
destination object number is 0.
If the destination object number is not contained in the received message, FC Distribute,
which is responsible for distributing the received messages, references an object reference
list. Using the source address (source subscriber no. + source object no.) contained in every
message, FC Distribute searches through the list for an entry that specifies the missing
destination object number for the given source address; in other words, it searches for the
number of the local instance DB.