Documente Academic
Documente Profesional
Documente Cultură
Introduction
EGD is a communication protocol based on Ethernet data packages that are sent
perodically by one device (the producer) and received by one or more other devices (the
consumers). These data packages are referred to as exchanges.
EGD is based on Internet Protocol and is connection less. That is, unlike other typical
communication protocols, reception of data exchanges is not acknowledged.
The advantage of this concept is reduced overhead-, and network bandwith utilization.
EGD is an efficient way to exchange memory between devices on a network. It is not
intended for event notification or communications, where loss of a data sample could
have significant consequences.
A producer can determine physical health of the network, but cannot assume arrival of
transmitted data at the consumer(s).
A consumer knows the time interval to receive data and can therefore qualify health of
the communication.
A simple EGD communication between two or more devices (targets) requires at least a
produced exchange to send data from one device, and one or more corresponding
consumed exchanges to receive this same data on other devices.
Each device can however produce and consume multiple exchanges (to-, or from multiple
other devices) at the same time.
EGD Configuration
EGD is configured in Machine Edition by adding an EGD component to a target and
setting up produced and consumed exchanges as required by the application.
Communication takes place automatically without any application program intervention.
Configuration of EGD exchanges (produced, as well consumed) specifies two sets of
information:
On a produced exchange definition, this list specifies all memory locations (i.e.
reference memory or symbolic variables) that are to be sent with this exchange.
1)
It must be a unique number across the network of EGD devices to identify the
producing device. The Local Producer ID is given in IP address format and is
submitted with each produced exchange from the device.
It does not necessarily need to be the IP address of a local Ethernet interface. (In a
PAC System or 90-70, there may also be more than one ETM sending / receiving
EGD.)
The Producer ID also appears in each consumed exchange configuration and must match
the Local Producer ID of the exchange that is to be received.
Exchange ID
1)
It must be a unique number for each exchange from one and the same producing
device. Exchanges from different producing devices may however use the same
Exchange ID.
Producer ID and Exchange ID together provide a unique identification for each EGD
exchange on a particular network.
Produced exchanges are either multicast, or directed to a target IP address. However, the
decision to consume an exchange is NOT taken on the IP address of the producer, but on the
Local Producer ID and Exchange ID submitted with the exchange.
Adapter Name
Designates the Ethernet interface that is to produce / consume an exchange. This setting
is of special interest in systems with more than one Ethernet interface.
For a unicast exchange, this parameter specifies the IP address of the Ethernet
interface that is to receice the exchange.
For a multicast exchange, the parameter specifies the Group ID of the devices that
2)
the exchange is sent to. Group IDs may range from 1 to 32
Group ID (Consumer only)
The Group ID is only needed when a multicast exchange is to be received. Otherwise, it
is ignored.
The number must match the Group ID configured in the destination parameter of
2)
the multicast exchange that is to be received.
A device can receive multicast exchanges that are directed to different groups. I.e. A
device can virtually belong to several groups.
2)
When sending I/O data from a controller to intelligent devices like a 90-30 ENIU or an RX3i
ENIU, the controller can send data for a whole group of devices within one exchange in
Multicast mode. The individual ENIUs are configured to receive the complete exchange and only
use their relevant data portion.
Usually, one large exchange in Multicast mode should be preferred and adds less load to the
network than many small exchanges in Unicast mode.
3)
Description
Data has been received within the update timeout period
Update timeout expired and no data has been received
Data has been received, but not within the update timeout period
Producer Status
Since there is no acknowledgement for data reception, a produced exchange status can at
most indicate proper production, but there is no indication that the exchange is received
at the consumer.
Status Description
1
Data has been sent correctly within the production period
References
Machine Edition Help Files: Ethernet Global Data: an Overview
GFK-1541
GFK-2382
GFK-1246
GFK-2224