| Page 11 of 26 |
4.4.5.Map Descriptor Example. 3 - Multiple Consumer Map Descriptor
In this example we assume that one produced data packet (produced by 0.0.0.1 and identified as exchange 1) contains different types of data elements making up the single exchange. This is configured when configuring EGD for the producer. The arrangement of data must correspond exactly with the configuration of the Map Descriptors used to consume the data. The following two Map Descriptors imply that the exchange contains at least 180 bytes of data and that the first 40 bytes contain 20 word values and that bytes 100 to 179 contain bit values. We cannot deduce what bytes
Map_Descriptor_Name, | Data_Array_Name, | Data_Array_Offset, | Function, | node_name, | Length, | ge_producerID, | ge_exchangeID, | ge_Data_Type, | ge_offset |
A1, | DA_AI3, | 0, | Passive, | Node_A, | 20 , | 0.0.0.1 , | 1, | Int, | 0 |
A2, | DA_DI1, | 0, | Passive, | Node_A, | 80 , | 0.0.0.1, | 1, | Bit, | 100 |
The producerID and
exchangeID for both these Map Descriptors are identical.
Therefore they will both be applied to the same incoming data packet.
The data types are different. The one Map Descriptor will be used to interpret incoming data as integers and the other will interpret data as bits. These data types must correspond to the way the producer is configured.
The 2nd Map Descriptor will process data bytes starting at byte 100. As the first byte is identified as byte zero, byte 100 is actually the 101st byte in the data part of the message.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com Tel: (408)