| Page 9 of 26 |
| ||
|
|
|
|
|
| Column Title | Function | Legal Values |
|
| The following keywords apply only to the |
|
| |
|
| This identifies the GE device producing the |
|
|
|
| EGD data. Although in decimal dot format, it |
|
|
|
| is not an IP address and does not necessarily |
|
|
|
| correspond to the IP address of the GE- |
|
|
|
| Ethernet port producing the message. It |
|
|
|
| corresponds to the producer ID configured for |
|
|
|
| the CPU producing the data. | Nnn.nnn.nnn.nnn |
|
|
|
|
| |
| ge_producerId | The default value is typically the same as the | Where nnn are in the |
|
|
| IP address of the producer but the value can | range |
|
|
| be changed and it is possible for one device |
|
|
|
| to have multiple Ethernet interfaces and |
|
|
|
| hence multiple IP addresses. |
|
|
|
| Any change to the producerID must be |
|
|
|
| matched by a similar change in the |
|
|
|
| consumer's configuration. |
|
|
|
| Used with the the producerID, to uniquely |
|
|
| ge_exchangeId | identify a packet of EGD data. Thus, this | Integer values >= 1 |
|
| driver uses these two parameters to match a |
| ||
|
| produced data packet with one or more |
|
|
|
| passive Map Descriptors. |
|
|
|
| Each produced data packet contains raw | Byte, Bit, Word, |
|
|
| packed data. Nothing in the message |
| |
|
| Dword, Int , Long |
| |
|
| identifies the structure or type of the incoming |
| |
|
| Float (4 byte IEEE real |
| |
| ge_data_type | data. The Driver therefore cannot |
| |
| number) or Double (8 |
| ||
|
| differentiate between byte, integer, real ... |
| |
|
| byte IEEE real |
| |
|
| numbers and requires the specification of this |
| |
|
| number). |
| |
|
| keyword to unpack the data buffer. |
| |
|
|
|
| |
|
| If the producer has been configured to |
|
|
|
| produce data of multiple types in one data |
|
|
|
| packet then you will need multiple Map |
|
|
|
| Descriptors to decode them. The ge_offset is | Zero, Any positive |
|
| ge_offset | used to point to the first byte in the data |
| |
| integer |
| ||
|
| packet to be processed by the Map |
| |
|
|
|
| |
|
| Descriptor. Typically the Map Descriptor for |
|
|
|
| the 2nd, 3rd ... Map Descriptors associated |
|
|
|
| with one data packet will be |
|
|
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com Tel: (408)
