Map Descriptor Example 1: - Simple Consumer Map Descriptor - FieldServer FS-8704-12 Driver Manual

FS-8704-12 GE-EGD Driver Manual
5.3.3 Map Descriptor Example 1: - S imple Consumer Map Descriptor
In this example the basics required for each consumer Map Descriptor are explained.
The first element
of data will be
stored in the Data
Data processed by
Array in the 6th
this Map
position (Array
Descriptor will be
elements are
stored in this
indexed from
array.
zero.).
Map_Descriptor_Name , Data_Array_Name
A1 , DA_AI3
This is the dot format ID of the producer,
not the IP address of the producer's
Ethernet node.
This value identifies the producing
processor.
This and the exchangeID uniquely identify
a produced data packet.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
The node name
ties the Map
Descriptor to a
Map Descriptors
node which in
defined to turn ties the Map
consume EGD
Descriptor to an
data must be
adapter and a
passive.
protocol.
, Data_Array_Offset , Function
, 0 , Passive
This is a numeric value assigned
by the PLC programmer to
identify a specific data exchange
to be received by the
consuming device (the
FieldServer in this case). It must
match the ID specified in the
producer.
Page 9 of 23
This is the number of
data elements that
will be consumed
from the message be
processed using this
Map Descriptor.
, Node_Name , Length , Ge_ProducerID
, Node_A , 20 , 0.0.0.1
The data in the data packet will be treated as 16 bit
(two byte) signed integers. As the length=20 a total
of 40 bytes will be processed.
The type of the Data Array should be capable of
storing signed integers in this example.
If you do not use this keyword then the driver will
process the data as bytes.
Refer to Appendix A.1
, Ge_ExchangeID , Ge_Data_Type
, 1 , Int