A Sierra Monitor Company Driver Manual (Supplement to the FieldServer Instruction Manual) FS-8704-12 GE-EGD (Ethernet Global Data) APPLICABILITY & EFFECTIVITY Effective for all systems manufactured after May 1, 2001 Driver Version: 1.
FS-8704-12_GE-EGD Manual Table of Contents TABLE OF CONTENTS 1. GE-EGD (ETHERNET GLOBAL DATA) DESCRIPTION...................................................3 2. 2.1. 2.2. DRIVER SCOPE OF SUPPLY............................................................................................4 Supplied by FieldServer Technologies for this driver ...................................................4 Provided by the Supplier of 3rd Party Equipment ..........................................................4 3.
FS-8704-12_GE-EGD Manual 1. Page 3 of 26 GE-EGD (Ethernet Global Data) Description The GE-EGD (Ethernet Global Data) driver allows the FieldServer to transfer data to and from devices over Ethernet using GE-EGD (Ethernet Global Data) protocol. There are two Ethernet ports standard on the FieldServer. The FieldServer can emulate either a Server or Client. GE Fanuc Automation and GE Drive Systems developed an Ethernet Global Data, or EGD, exchange for PLC and computer data in 1998.
FS-8704-12_GE-EGD Manual 2. Page 4 of 26 Driver Scope of Supply 2.1. Supplied by FieldServer Technologies for this driver FieldServer Technologies PART # FS-8915-10 FS-8704-12 2.2. Description UTP cable (7 foot) for Ethernet connection Driver Manual. Provided by the Supplier of 3rd Party Equipment EGD capable GE communication/processor module. The IC697CMM742 modules configured with Control and IC693CPU364 and IC200CPUE05 configured with VersaPro can send and receive EGD.
FS-8704-12_GE-EGD Manual 3. Page 5 of 26 Hardware Connections The FieldServer is connected to the Site Ethernet as shown below. Configure and connect the "GE TCP/IP Ethernet Interface Type 2" according to manufacturer’s instructions. N7 Site Ethernet (408)-262-2299 FIELDSERVER GE-EGD CONNECTION DIAGRAM BASE NAME: FILE NAME: DATE: 2/4/04 BY: MF FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.
FS-8704-12_GE-EGD Manual 4. Page 6 of 26 Configuring the FieldServer as a GE-EGD Client Historically, one uses the client-server model to describe the operation of most protocols. Recently producer-consumer model protocols have started to become more numerous. The GE-EGD (Ethernet Global Data) is a producer-consumer model protocol. In equating the two models it is important to regard the consumer as a passive (FieldServer) client. Other clients typically are active and poll for new data.
FS-8704-12_GE-EGD Manual Page 7 of 26 Example // Data Arrays Data_Arrays Data_Array_Name, DA_AI_01, DA_AO_01, DA_DI_01, DA_DO_01, 4.2. Data_Format, UInt16, UInt16, Bit, Bit, Data_Array_Length 200 200 200 200 Client Side Connection Descriptors Section Title Adapter Column Title Adapter Protocol Function Adapter Name Specify protocol used Legal Values N1,N2 GE_EGD Example // Client Side Connections Adapters Adapter, N1, 4.3.
FS-8704-12_GE-EGD Manual 4.4. Page 8 of 26 Client Side Map Descriptors 4.4.1. FieldServer Specific Map Descriptor Parameters Column Title Function Map_Descriptor_Name Data_Array_Name Data_Array_Location Function 4.4.2. Name of this Map Descriptor Name of Data Array where data is to be stored in the FieldServer Starting location in Data Array Function of Client Map Descriptor Legal Values Up to 32 alphanumeric characters.
FS-8704-12_GE-EGD Manual Page 9 of 26 Column Title Function Legal Values The following keywords apply only to the GE-EGD protocol. 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 GEEthernet port producing the message. It corresponds to the producer ID configured for the CPU producing the data. Nnn.nnn.nnn.
FS-8704-12_GE-EGD Manual 4.4.3. Page 10 of 26 Map Descriptor Example. 1 - Map Descriptor Basics In this example the basics required for each consumer Map Descriptor are explained. Map_Descriptor_Name, A1, Data processed by this Map Descriptor will be stored in this array. Data_Array_Name, DA_AI3, The first element of data will be stored in the Data Array in the 6th position (Array elements are indexed from zero.). 4.4.4.
FS-8704-12_GE-EGD Manual 4.4.5. Page 11 of 26 Map Descriptor Example. 3 - Multiple Consumer Map Descriptor In this example we assume that one produced data packet (produced by 0.0.0.1 and identified as exchange 1) contains different types of data elements making up the single exchange. This is configured when configuring EGD for the producer. The arrangement of data must correspond exactly with the configuration of the Map Descriptors used to consume the data.
FS-8704-12_GE-EGD Manual 5. Page 12 of 26 Configuring the FieldServer as a GE-EGD Server 5.1. Server Side Connection Descriptors Section Title Connections Column Title Adapter Protocol Function Adapter Name Specify protocol used Legal Values N1,N2 GE_EGD Example Adapters Adapter, N1, 5.2. Protocol GE_Egd Server Side Node Descriptors Section Title Nodes Column Title Function Node_Name Provide name for node Node_ID This keyword is not required.
FS-8704-12_GE-EGD Manual 5.3. Page 13 of 26 Server Side Map Descriptors 5.3.1. FieldServer Specific Map Descriptor Parameters Column Title Function Map_Descriptor_Name Name of this Map Descriptor Legal Values Up to 32 alphanumeric characters. The Map Descriptor name can be any name that has meaning to you and in fact duplicate name will not produce an error. This driver recognizes a special Map Descriptor name; "EGD-ii". It stands for EGD Internal Indications.
FS-8704-12_GE-EGD Manual Column Title ge_producerId ge_exchangeId ge_data_type ge_offset 5.3.3. Column Title Scan_Interval Page 14 of 26 Function 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. Legal Values Nnn.nnn.nnn.
FS-8704-12_GE-EGD Manual 5.3.4. Map_Descriptor_Name, A1, Page 15 of 26 Map Descriptor Example. Data_Array_Name, DA_AI3, Data_Array_Offset, 0, Only a wrbc can be used to produce data. The other write functions are not periodic. Function, Wrbc, node_name, Node_A, Consider this as the producer interval. Length, 100 Scan_Interval, 5.0s , The consumer must be configured to have the same producerID and exchangeID.
FS-8704-12_GE-EGD Manual Page 16 of 26 Appendix A. Advanced Topics Appendix A.1. Enable the FieldServer to read data from a 90-xx PLC. Appendix A.1.1. Use configuration. Versapro to configure/look at the EGD Produced data must be produced for a specific consumer. Thus you must create a new exchange in the PLC that will produce data for the FieldServer. (Specific consumer means specific IP address).
FS-8704-12_GE-EGD Manual Page 17 of 26 This is the producerID. It may be the same as the IP address of the adapter but this is not always the case. • • • • • • • Note the Local Producer address. Typically it will be the same as the IP of the closest GE Ethernet port. You can override this. Add Ranges. Record the offset and reference for each data range in the exchange. Save your work. Close HWC. Stop the processor.
FS-8704-12_GE-EGD Manual Page 18 of 26 You will need this adapter’s IP address. It will be used as the node IP address in the CSV file. 5.3.5. Create a CSV file that will consume the produced data. An example is shown on the following page. 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.
FS-8704-12_GE-EGD Manual Page 19 of 26 Adapters Adapter, N1, protocol ge_egd Nodes Node_name, PLC90-30, IP_Address, 216.232.242.3, Adapter, N1, Protocol ge_egd This is the IP address of the producing port. You can obtain this by using the Versapro HWC program and double clicking on the Module with the adapter shown in the EGD configuration. (Fred, in this example) Now look for the Ethernet port address.
FS-8704-12_GE-EGD Manual Map_Descriptors Map_Descriptor_Name, Q1, R1, I1, R2, I2, Q2, Data_Array_Name, DATA_Q, DATA_R, DATA_R, DATA_R, DATA_R, DATA_R, Page 20 of 26 Data_Array_Offset, 0 0 0 1 2 1 Function, Passive, Passive, Passive, Passive, Passive, Passive, node_name, PLC90-30, PLC90-30, PLC90-30, PLC90-30, PLC90-30, PLC90-30, Length, 1, 1, 2, 1, 1, 1, ge_producerId, 1.2.3.4, 1.2.3.4, 1.2.3.4, 1.2.3.4, 1.2.3.4, 1.2.3.4, Read the section on data types to see how many items are being transmitted.
FS-8704-12_GE-EGD Manual Page 21 of 26 Appendix A.2. Data Types Each produced data packet contains up to 1400 bytes of unstructured data. The specification of the ge_data_type in the Map Descriptor tells the driver how to interpret these raw data bytes. The minimum data unit processed is a byte. This is the case even when the data type is specified as bit. This is because EGD producers cannot produce a single bit.
FS-8704-12_GE-EGD Manual Page 22 of 26 Appendix B. Error Messages Multiple protocol drivers may exist on a FieldServer. Each driver may produce its own error messages and the FieldServer itself may produce error messages. Message EGD:#1 Error. Can’t init UDP. EGD:#2 Error. Can’t get a socket. EGD:#3 Error. Protocol does not support active polling. Change function for mapDesc=<%s> EGD:#4 Error. Producer ID required for mapDesc=<%s> EGD:#5 Error. Exchange ID required for mapDesc=<%s> EGD:#6 FYI.
FS-8704-12_GE-EGD Manual 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 "EGD-ii" which stands for EGD Internal Indications. The following example shows how this special Map Descriptor can be configured.
FS-8704-12_GE-EGD Manual Page 24 of 26 Appendix B.2. Driver Stats EGD producers produce data messages for slave devices to consume. frequency of the messages depends on the producer configuration. The type and The driver counts all incoming messages of interest as the PLC_READ_MSG_RECD statistic. Other legal messages which do not contain the data this driver is interested in are discarded and are counted as the MSG_IGNORED statistic.
FS-8704-12_GE-EGD Manual Page 25 of 26 Appendix C. Troubleshooting Tips Appendix C.1. ProducerID with FieldServer device as Producer During testing it has been observed that a 90-30 PLC required that the ge_ProducerID parameter was set to the same value as the IP Address of the FieldServer. Appendix C.2. Produced Time Stamp The GE-EGD (Ethernet Global Data) driver always set the timestamp of produced data to the time of the Field Server Device.
FS-8704-12_GE-EGD Manual Page 26 of 26 THIS PAGE INTENTIONALLY LEFT BLANK 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.
