Technical Support Center

Ethernet Data Packet Structure


Ethernet Data Packet Framing#

The following figure shows the basic structure of an Ethernet data packet. In order to keep the overhead of the data transmission as low as possible, the "User Datagram Protocol" (UDP) is used.

ADMA Data Format#

Use of the UDP Data Area#

For the data output of one format, the entire UDP data area is available. The data area itself does not receive any predefined header information for all formats, in order not to restrict the flexibility of formats to be created in the future.

General Structure of an ADMA data format#

An ADMA data format generally consists of 3 segments:
1] a static-header
2] a dynamic-header and
3] the actual user data.
However, customer-specific data formats are also possible. They completely dispense with header information or use their own header definitions e.g. DELTA data or Robot data.

ADMA Data Structure#

ADMA-Header#

With the header information, it is possible to identify the sent format version and connected ADMA device. In addition, the complete configuration of the ADMA will be transmitted.
The ADMA Header consists of 2 segments:
1] a static header
2] a dynamic header.

Static-Header#

The static header will not be changed in its definition. It will always be first in the data packet, so that it can be clearly distinguished how the subsequent dynamic header and the data can be interpreted.

NAMEDESCRIPTION
GeneSys IDUsed to uniquely identify the beginning of a data packet
"GBIN" = GeneSys Binary (public)
Header VersionUsed to uniquely identify the beginning of a data packet
Format IDContains the format ID of the following data
Format VersionContains the version of the following data
Serial NumberADMA serial number
AliasADMA Alias

Dynamic-Header#

The configuration of the ADMA is sent in the dynamic header. A part of the configuration is sent in each data packet. Each piece includes a maximum of 4 bytes. If all of these parts have been received, they are getting saved in a file with the ending *.gscb.

NAMEDESCRIPTION
Config IDContains the config ID, which is sent in the dynamic header
Config FormatContains the config format, which is sent in the dynamic header
Config VersionContains the config version, which is sent in the dynamic header
Config SizeContains the total file size of the configuration in bytes
Byte OffsetContains the position of the "Slice Data" within the configuration file
Slice Size in ByteIncludes the size of "SliceData"
Slice DataValues for the configuration file

The following graphic illustrates the storage of the configuration.

Applikationsingenieur | bei GeneSys seit 2014

Notify me about Updates