| Page 23 of 26 |
Appendix B.1. EGD-ii (EGD Internal Indications)
This driver can expose data from the most recently consumed message and some additional diagnostic information.
A special Map Descriptor is required. The driver recognizes the Map Descriptor by its name which must be
The following example shows how this special Map Descriptor can be configured.
Nodes |
|
|
Node_name, | Protocol |
|
null_node, | ge_egd |
|
Data_Arrays |
|
|
Data_Array_Name, | Data_Format, | Data_Array_Length |
EGD_DIAG, | UINT32, | 100 |
Map_Descriptors |
|
|
Map_Descriptor_Name, | Data_Array_Name, | Node_name |
EGD_DIAG, | null_node |
When the driver sees this Map Descriptor it uses the Data Array EGD_DIAG to store driver specific data. Only one of these Map Descriptors may be specified per FieldServer.
The driver stores the following data.
Array |
| Contents |
|
Element |
|
| |
|
|
| |
| The first 32 bytes of the most recently received UDP packet received on | ||
| port 0x4746 (The GE EGD port). | ||
|
| ||
32 | PDUTypeVersion | ||
33 | RequestID | ||
34 | ProducerID2 | ||
35 |
| ExchangeID | |
36 | TimeStampSec | ||
37 | TimeStampNanoSec | ||
38 | Status3 | ||
39 | ConfigSignature | ||
40 | Reserved | ||
41 | Source IP Address1 | ||
2As a UINT32. Not in dot format
3Read section 4.4 of
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com Tel: (408)