Map Descriptor Example. 1 - Map Descriptor Basics; Map Descriptor Example. 2 - A Simple Consumer Map Descriptor - FieldServer FS-8704-12 GE-EGD Manual

FS-8704-12_GE-EGD Manual
4.4.3.

Map Descriptor Example. 1 - Map Descriptor Basics

In this example the basics required for each consumer Map Descriptor are explained.
Map_Descriptor_Name, Data_Array_Name,
A1, DA_AI3,
Data processed The first element
by this Map of data will be
Descriptor will stored in the
be stored in this Data Array in
array. the 6th position
(Array elements
are indexed
from zero.).
4.4.4.

Map Descriptor Example. 2 - A Simple Consumer Map Descriptor

Map_Descriptor_Name, Data_Array_Name,
A1, DA_AI3,
This is the dot format ID of the
producer. It is 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-9042 Toll_Free: 888-509-1970 email: support@fieldserver.com
Data_Array_Offset, Function,
5, Passive,
When you
The node name
define Map
ties the Map
Descriptors to
Descriptor to a
consume EGD
node which in
data they must
turn ties the Map
be passive.
Descriptor to an
adapter a
protocol.
Data_Array_Offset, Function, node_name,
0, Passive, Node_A,
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 10 of 26
node_name, Length, ge_producerID,
Node_A, 1,
This is the number
of data elements
that will be
consumed from the
message be
processed using this
nd a Map Descriptor.
Length, ge_producerID,
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.
The data type is more completely explained in
section Appendix A.1
ge_exchangeID
0.0.0.1, 1
These
parameters are
required but will
be explained in
the next
example.
ge_exchangeID, ge_Data_Type
1, Int