Summary of the content on the page No. 1
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.02
Document Revision: 1
Summary of the content on the page No. 2
FS-8704-12_GE-EGD Manual Table of Contents TABLE OF CONTENTS 1. GE-EGD (ETHERNET GLOBAL DATA) DESCRIPTION...................................................3 2. DRIVER SCOPE OF SUPPLY............................................................................................4 2.1. Supplied by FieldServer Technologies for this driver ...................................................4 rd 2.2. Provided by the Supplier of 3 Party Equipment...............................................
Summary of the content on the page No. 3
FS-8704-12_GE-EGD Manual Page 3 of 26 1. 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
Summary of the content on the page No. 4
FS-8704-12_GE-EGD Manual Page 4 of 26 2. Driver Scope of Supply 2.1. Supplied by FieldServer Technologies for this driver FieldServer Technologies Description PART # FS-8915-10 UTP cable (7 foot) for Ethernet connection FS-8704-12 Driver Manual. rd 2.2. Provided by the Supplier of 3 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.
Summary of the content on the page No. 5
FS-8704-12_GE-EGD Manual Page 5 of 26 3. 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: DATE: 2/4/04 FILE NAME: BY: MF FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com Tel: (408) 262-2299 Fax:
Summary of the content on the page No. 6
FS-8704-12_GE-EGD Manual Page 6 of 26 4. 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
Summary of the content on the page No. 7
FS-8704-12_GE-EGD Manual Page 7 of 26 Example // Data Arrays Data_Arrays Data_Array_Name, Data_Format, Data_Array_Length DA_AI_01, UInt16, 200 DA_AO_01, UInt16, 200 DA_DI_01, Bit, 200 DA_DO_01, Bit, 200 4.2. Client Side Connection Descriptors Section Title Adapter Column Title Function Legal Values Adapter Adapter Name N1,N2 Protocol Specify protocol used GE_EGD Example // Client Side Connections Adapters Adapter, Protocol N1, GE_Egd 4.3. Clie
Summary of the content on the page No. 8
FS-8704-12_GE-EGD Manual Page 8 of 26 4.4. Client Side Map Descriptors 4.4.1. FieldServer Specific Map Descriptor Parameters Column Title Function Legal Values Up to 32 alphanumeric characters. The Map Descriptor name can be any name that has meaning to you and need not be unique. Name of this Map Map_Descriptor_Name Descriptor This driver recognizes a special Map Descriptor name; "EGD-ii". It stands for EGD Internal Indications. Its use is more fully explained in Appen
Summary of the content on the page No. 9
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 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 typic
Summary of the content on the page No. 10
FS-8704-12_GE-EGD Manual Page 10 of 26 4.4.3. Map Descriptor Example. 1 - Map Descriptor Basics In this example the basics required for each consumer Map Descriptor are explained. Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function, node_name, Length, ge_producerID, ge_exchangeID A1, DA_AI3, 5, Passive, Node_A, 1, 0.0.0.1, 1 When you Data processed The first element The node name This is the number define Map These by this Map of data will be ties
Summary of the content on the page No. 11
FS-8704-12_GE-EGD Manual Page 11 of 26 4.4.5. 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. The following two
Summary of the content on the page No. 12
FS-8704-12_GE-EGD Manual Page 12 of 26 5. Configuring the FieldServer as a GE-EGD Server 5.1. Server Side Connection Descriptors Section Title Connections Column Title Function Legal Values Adapter Adapter Name N1,N2 Protocol Specify protocol used GE_EGD Example Adapters Adapter, Protocol N1, GE_Egd 5.2. Server Side Node Descriptors Section Title Nodes Column Title Function Legal Values Up to 32 alphanumeric Node_Name Provide name for node characters Node_ID Thi
Summary of the content on the page No. 13
FS-8704-12_GE-EGD Manual Page 13 of 26 5.3. Server Side Map Descriptors 5.3.1. FieldServer Specific Map Descriptor Parameters Column Title Function 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 Name of this Map error. Map_Descriptor_Name Descriptor This driver recognizes a special Map Descriptor name; "EGD-ii". It stands for EGD Internal Indications. Its use is
Summary of the content on the page No. 14
FS-8704-12_GE-EGD Manual Page 14 of 26 Column Title Function Legal Values 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 Where nnn are in the the IP address of
Summary of the content on the page No. 15
FS-8704-12_GE-EGD Manual Page 15 of 26 5.3.4. Map Descriptor Example. Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function, node_name, Length, Scan_Interval, ge_producerID, ge_exchangeID, ge_data_type A1, DA_AI3, 0, Wrbc, Node_A, 100 5.0s , 0.0.0.1, 1, %R The consumer must be Defines how data is configured to have packed into the data part the same of the message. Consider this as Only a wrbc can be producerID and the producer used to produce data. exc
Summary of the content on the page No. 16
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 Versapro to configure/look at the EGD configuration. 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). Since the EGD data packet is not structured, the FieldServer cannot decode the
Summary of the content on the page No. 17
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. • Store the Hardware settings to the PLC • Put the processo
Summary of the content on the page No. 18
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.com
Summary of the content on the page No. 19
FS-8704-12_GE-EGD Manual Page 19 of 26 Adapters Adapter, protocol N1, ge_egd Nodes Node_name, IP_Address, Adapter, Protocol PLC90-30, 216.232.242.3, N1, ge_egd This is the IP address of the producing port. You can obtain this by using the Versapro HWC program and Nodes double clicking on the Module with the adapter shown in Node_name, Protocol the EGD configuration. (Fred, in this example) Now look null_node, ge_egd for the Ethernet port a
Summary of the content on the page No. 20
FS-8704-12_GE-EGD Manual Page 20 of 26 Map_Descriptors Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function, node_name, Length, ge_producerId, ge_exchangeId, ge_data_type, ge_offset Q1, DATA_Q, 0 Passive, PLC90-30, 1, 1.2.3.4, 1, %q, 0 R1, DATA_R, 0 Passive, PLC90-30, 1, 1.2.3.4, 1, %r, 1 I1, DATA_R, 0 Passive, PLC90-30, 2, 1.2.3.4, 1, %u, 3 R2, DATA_R, 1
