Driver Manual - Chipkin Automation Systems
A Sierra Monitor CompanyDriver Manual(Supplement to the FieldServer Instruction Manual)FS-8704-12 GE-EGDAPPLICABILITY & EFFECTIVITYEffective for all systems manufactured after April 2010Driver Version:Document Revision:1.023
FS-8704-12 GE-EGD Driver ManualTable of ContentsTABLE OF CONTENTS1GE-EGD (Ethernet Global Data) Description . 32Driver Scope of Supply . 32.1Supplied by FieldServer Technologies for this driver . 3rd2.2Provided by the Supplier of 3 Party Equipment . 33Hardware Connections . 44Data Array Parameters . 55Configuring the FieldServer as a GE-EGD Client . 65.1Client Side Connection Parameters . 65.2Client Side Node Parameters . 75.3Client Side Map Descriptor Parameters . 75.3.1FieldServer Specific Map Descriptor Parameters . 75.3.2Driver Specific Map Descriptor Parameters. 85.3.3Map Descriptor Example 1: - Simple Consumer Map Descriptor . 95.3.4Map Descriptor Example 2: - Multiple Consumer Map Descriptor . 106Configuring the FieldServer as a GE-EGD Server . 116.1Server Side Connection Parameters . 116.2Server Side Node Parameters . 116.3Server Side Map Descriptors. 126.3.1FieldServer Specific Map Descriptor Parameters . 126.3.2Driver Specific Map Descriptor Parameters. 126.3.3Timing Parameters . 126.3.4Map Descriptor Example. 13Appendix A. Vendor Information . 14Appendix A.1. Enable the FieldServer to read data from a 90-xx PLC. 14Appendix A.1.1. Use Versapro to configure/look at the EGD configuration. . 14Appendix A.1.2. Create a CSV file that will consume the produced data. . 16Appendix B. Troubleshooting. 19Appendix B.1. ProducerID with FieldServer device as Producer . 19Appendix B.2. Produced Time Stamp . 19Appendix B.3. Status Values . 19Appendix B.4. Error Messages . 19Appendix B.5. EGD-ii (EGD Internal Indications) . 20Appendix B.6. Driver Stats . 21Appendix C. Reference . 23Appendix C.1. Data Types . 23FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.comTel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
FS-8704-12 GE-EGD Driver Manual1Page 3 of 23GE-EGD (ETHERNET GLOBAL DATA) DESCRIPTIONThe GE-EGD (Ethernet Global Data) driver allows the FieldServer to transfer data to and from devices over Ethernetusing GE-EGD (Ethernet Global Data) protocol. 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 andcomputer data in 1998. EGD uses UDP or datagram messages for fast transfer of up to 1400 bytes of data from aproducer to one or more consumers. UDP messages have much less overhead than the streaming TCP connectionused for programming or CommReq’s over SRTP Ethernet. Like Genius broadcast input or directed controlmessages, UDP messages are not acknowledged. They can be sent at short intervals. Chances of one or moremessages being dropped are small on a local area network.As a Client the FieldServer acts as an EGD consumer. As a Server the FieldServer acts as an EGD producer.The IC697CMM742 Ethernet module supports both GE SRTP and GE EGD.2DRIVER SCOPE OF SUPPLY2.1Supplied by FieldServer Technologies for this driverFieldServer Technologies PART #FS-8915-102.2DescriptionUTP cable (7 foot) for Ethernet connectionProvided by the Supplier of 3 r d Party EquipmentEGD capable GE communication/processor module.The IC697CMM742 modules configured with Control and IC693CPU364 and IC200CPUE05 configured withVersaPro can send and receive EGD.FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.comTel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
FS-8704-12 GE-EGD Driver Manual3Page 4 of 23HARDWARE CONNECTIONSThe 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.GE-EGD DeviceN7Hub/RouterFieldServer Part #8915-10UTP cableConnect to an Ethernet Porton the FieldServer81FieldServerN1FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.comTel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
FS-8704-12 GE-EGD Driver Manual4Page 5 of 23DATA ARRAY PARAMETERSData Arrays are “protocol neutral” data buffers for storage of data to be passed between protocols. It is necessaryto declare the data format of each of the Data Arrays to facilitate correct storage of the relevant data.Section TitleData ArraysColumn TitleFunctionData Array NameProvide name for Data ArrayData Array FormatData Array LengthProvide data format. Each Data Array can only take on oneformat.Number of Data Objects. Must be larger than the data storagearea required by the Map Descriptors for the data being placed inthis array.Legal ValuesUpto15alphanumericcharactersFloat, Bit, UInt16,SInt161-10, 000Example// Data ArraysData ArraysData Array NameDA AI 01DA AO 01DA DI 01DA DO 01, Data Array Format, UInt16, UInt16, Bit, Bit, Data Array Length, 200, 200, 200, 200FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.comTel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
FS-8704-12 GE-EGD Driver Manual5Page 6 of 23CONFIGURING THE FIEL DSERVER AS A GE-EGD CLIENTHistorically, one uses the client-server model to describe the operation of most protocols. Recently producerconsumer model protocols have started to become more numerous. The GE-EGD (Ethernet Global Data) is aproducer-consumer model protocol. In equating the two models it is important to regard the consumer as apassive (FieldServer) client. Other clients typically are active and poll for new data. The consumer is a passiveclient in that waits to digest new data generated by a producer.For a detailed discussion on FieldServer configuration, please refer to the instruction manual for the FieldServer.The information that follows describes how to expand upon the factory defaults provided in the configuration filesincluded with the FieldServer (See “.csv” files provided with the FieldServer).This section documents and describes the parameters necessary for configuring the FieldServer to communicatewith a GE-EGD Producer.The configuration file tells the FieldServer about its interfaces, and the routing of data required. In order to enablethe FieldServer for GE-EGD communications, the driver independent FieldServer buffers need to be declared in the“Data Arrays” section, the destination device addresses need to be declared in the “Client Side Nodes” section, andthe data required from the servers needs to be mapped in the “Client Side Map Descriptors” section. Details onhow to do this can be found below.Note that in the tables, * indicates an optional parameter, with the bold legal value being the default.5.1Client S ide Connection ParametersSection TitleAdapterColumn TitleAdapterProtocolFunctionAdapter NameSpecify protocol usedLegal Values1N1,N2ge egdExample// Client Side ConnectionsAdaptersAdapterN1, Protocol, ge egd1Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction manual for details of the ports availableon specific hardware.FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.comTel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
FS-8704-12 GE-EGD Driver Manual5.2Page 7 of 23Client S ide Node P arametersSection TitleNodesColumn TitleFunctionNode NameProvide name for NodeIP AddressThe IP address in dot format of the EGD-Device.ProtocolSpecify protocol usedSpecify which adapter connects to the network the EGDdevice is connected to.AdapterLegal here nnn is in the range 0-255.ge egd2N1, N2Example// Consumer (Passive Client) Side NodesNodesNode NameNode A5.3, IP Address, 192.168.1.102, Adapter, N1, Protocol, ge egdClient Side Map Descriptor P arameters5.3.1FieldServer Specific Map Descriptor ParametersColumn TitleMap Descriptor NameData Array NameFunctionName of this Map DescriptorName of Data Array where data is to bestored in the FieldServerData Array LocationStarting location in Data ArrayFunctionFunction of Client Map DescriptorLegal ValuesUp to 32 alphanumeric characters.One of the Data Array names fromSection 40 to (Data Array Length-1) as specifiedin Section 4Passive2Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction manual for details of the ports availableon specific hardware.FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.comTel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
FS-8704-12 GE-EGD Driver Manual5.3.2Page 8 of 23Driver Specific Map Descriptor P arametersColumn TitleFunctionNode NameName of Node to fetch data fromLengthGe ProducerIdGe ExchangeIdGe Data Type*Ge Offset*Number of points being consumed. For Bit values thisrepresents the number of bytes (i.e. number of points dividedby 8)This identifies the GE device producing the EGD data.Although in decimal dot format, it is not an IP address anddoes not necessarily correspond to the IP address of the GEEthernet port producing the message. It corresponds to theproducer ID configured for the CPU producing the data.The default value is typically the same as the IP address of theproducer but the value can be changed and it is possible forone device to have multiple Ethernet interfaces and hencemultiple IP addresses.Any change to the producerID must be matched by a similarchange in the consumer's configuration.Used with the ProducerID, to uniquely identify a packet of EGDdata. The driver uses these two parameters to match aproduced data packet with one or more passive MapDescriptors.Each produced data packet contains raw packed data. Nothingin the message identifies the structure or type of the incomingdata. The Driver therefore cannot differentiate between byte,integer, real . numbers and requires the specification of thiskeyword to unpack the data buffer.If the producer has been configured to produce data ofmultiple types in one data packet then multiple MapDescriptors are required to decode them. The Ge Offset isused to point to the first byte in the data packet to beprocessed by the Map Descriptor.Typically the MapDescriptor for the 2nd, 3rd . Map Descriptors associated withone data packet will be non-zero.Legal ValuesOne of the node namesspecified in Section 5.21 - 1000Nnn.nnn.nnn.nnnWhere nnn are in the range0-255.Integer values 1Byte, Bit, Word, Dword, Int ,Long, Float (4 byte IEEE realnumber) or Double (8 byteIEEE real number).0, Any positive integerFieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.comTel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
FS-8704-12 GE-EGD Driver Manual5.3.3Page 9 of 23Map Descriptor Example 1: - S imple Consumer Map DescriptorIn this example the basics required for each consumer Map Descriptor are explained.Data processed bythis MapDescriptor will bestored in thisarray.Map Descriptor NameA1The first elementof data will bestored in the DataArray in the 6thposition (Arrayelements areindexed fromzero.)., Data Array Name, DA AI3Map Descriptorsdefined toconsume EGDdata must bepassive., Data Array Offset,0This is the dot format ID of the producer,not the IP address of the producer'sEthernet node.This value identifies the producingprocessor.This and the exchangeID uniquely identifya produced data packet., Function, PassiveThe node nameties the MapDescriptor to anode which inturn ties the MapDescriptor to anadapter and aprotocol., Node Name, Node AThis is a numeric value assignedby the PLC programmer toidentify a specific data exchangeto be received by theconsuming device (theFieldServer in this case). It mustmatch the ID specified in theproducer.This is the number ofdata elements thatwill be consumedfrom the message beprocessed using thisMap Descriptor., Length, 20, Ge ProducerID, 0.0.0.1, Ge ExchangeID,1, Ge Data Type, IntThe data in the data packet will be treated as 16 bit(two byte) signed integers. As the length 20 a totalof 40 bytes will be processed.The type of the Data Array should be capable ofstoring signed integers in this example.If you do not use this keyword then the driver willprocess the data as bytes.Refer to Appendix A.1FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.comTel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
FS-8704-12 GE-EGD Driver Manual5.3.4Page 10 of 23Map Descriptor Example 2: - Mult iple Consumer Map DescriptorIn 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 makingup the single exchange. This is configured when configuring EGD for the producer. The arrangement of data must correspond exactly with the configuration ofthe Map Descriptors used to consume the data. The following two Map Descriptors imply that the exchange contains at least 180 bytes of data and that thefirst 40 bytes contain 20 word values and that bytes 100 to 179 contain bit values. We cannot deduce what bytes 40-99 contain.Map Descriptor NameA1A2, Data Array Name, DA AI3, DA DI1, Data Array Offset,0,0The producerID andexchangeID for boththese MapDescriptors areidentical. Thereforethey will both beapplied to the sameincoming datapacket., Function, Passive, PassiveNode NameNode ANode ALength2080Ge ProducerID0.0.0.10.0.0.1Ge ExchangeID11The data types are different.The first Map Descriptor will beused to interpret incomingdata as integers and thesecond will interpret data asbits. These data types mustcorrespond to the way theproducer is configured.Ge Data TypeIntBitge offset0100The 2nd MapDescriptor willprocess data bytesstarting at byte 100.As the first byte isidentified as bytezero, byte 100 isactually the 101stbyte in the data partof the message.FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.comTel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
FS-8704-12 GE-EGD Driver Manual6Page 11 of 23CONFIGURING THE FIEL DSERVER AS A GE-EGD SERVER6.1Server Side Connection ParametersSection TitleConnectionsColumn TitleAdapterProtocolFunctionAdapter NameSpecify protocol usedLegal ValuesN1,N2ge egdExampleAdaptersAdapterN16.2, Protocol, ge egdServer Side Node ParametersSection TitleNodesColumn TitleFunctionNode NameProvide name for NodeIP AddressThe IP address in dot format of the EGD-Device.ProtocolSpecify protocol usedSpecify which adapter connects to the network the EGDdevice is connected to.AdapterLegal here nnn is in the range 0-255.ge egd3N1, N2Example// Producer(Active Server) Side NodesNodesNode Namenode A, IP Address,, 192.168.1.102,, Adapter, N1, Protocol, ge egd3Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction manual for details of the ports availableon specific hardware.FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.comTel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
FS-8704-12 GE-EGD Driver Manual6.3Page 12 of 23Server Side Map DescriptorsOnly one Map Descriptor may be configured for each ExchangeID. Each produced exchange is thus limited to onedata type and to data from one Data Array. This is different from the configuration of consumer Map Descriptors.6.3.1FieldServer Specific Map Descriptor ParametersColumn TitleMap Descriptor NameData Array NameFunctionName of this Map DescriptorName of Data Array where data is to bestored in the FieldServerData Array LocationStarting location in Data ArrayFunctionFunction of Client Map Descriptor6.3.2Legal ValuesUp to 32 alphanumeric characters.One of the Data Array names fromSection 40 to (Data Array Length-1) as specifiedin Section 4WrbcDriver Specific Map Descriptor P arametersColumn TitleFunctionNode NameName of Node to fetch data fromLengthLength of Map DescriptorThis identifies the GE device producing the EGD data. Although indecimal dot format, it is not an IP address and does not necessarilycorrespond to the IP address of the GE-Ethernet port producing themessage. It corresponds to the producer ID configured for the CPUproducing the data.The default value is typically the same as the IP address of theproducer but the value can be changed and it is possible for onedevice to have multiple Ethernet interfaces and hence multiple IPaddresses. Any change to the producerID must be matched by asimilar change in the consumer's configuration.This and the producerID uniquely identify a packet of EGD data. Thus,the consumer uses these two parameters to update. Any change tothe exchangeID must be matched by a similar change in theconsumer's configuration.Each produced data packet contains raw packed data. This keyword isused to tell the driver how to pack the data into the message. Thusdata can be read from a BIT array in the FieldServer and sent as wordsfor storage in %R (register memory) in the GE-PLC. Any change to thedata type must be matched by a similar change in the consumer'sconfiguration.Ge ProducerIdGe exchangeIdGe data type6.3.3Legal ValuesOne of the Nodenames specified inSection 6.2.1 - 1000Nnn.nnn.nnn.nnnWhere nnn are in therange 0-255.Integer values 1Refer to Appendix C.1.Timing ParametersColumn TitleScan IntervalFunctionRate at which data is produced. This is the equivalent of the producer interval.Legal Values 0.1sFieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.comTel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
FS-8704-12 GE-EGD Driver Manual6.3.4Page 13 of 23Map Descriptor Example.Map Descriptor Name , Data Array Name , Data Array Offset , Function , Node Name , Length , Scan Interval ,Ge producerID , ge exchangeID , Ge data typeA1, DA AI3,0, Wrbc, Node A, 100, 5.0s, 0.0.0.1,1, %ROnly a Wrbc can be usedto produce data. Theother write functions arenot periodic.Consider this as theproducer interval.The consumer mustbe configured tohave the sameproducerID andexchangeID. Thesetwo fields are theonly way it has ofdifferentiating oneset of produceddata from another.Defines how data is packedinto the data part of themessage.In this example data will bepacked words (unsigned 16bit integers) suitable forstorage in register memoryin the GE PLC's.Appendix C.1 contains a fulllist.FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.comTel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
FS-8704-12 GE-EGD Driver ManualPage 14 of 23Appendix A. Vendor InformationAppendix A.1. Enable the FieldServer to read data from a 90-xx PLC.Appendix A.1.1.Use Versapr o to configur e/look at the EGD configur ation.Produced data must be produced for a specific consumer (Specific IP address). Thus a new exchange must becreated in the PLC that will produce data for the FieldServer.Since the EGD data packet is not structured, the FieldServer cannot decode the data ranges without the MapDescriptors. It is therefore important that the data ranges in the produced exchange correspond to the MapDescriptors in the CSV file. Go online. View Menu, Hardware Configuration. (Launches HWC program). HWC. Edit. Rack Operations. EGD Configuration. Add an exchange. Set the CONS ADDRESS equal to the IP address of the FieldServer.FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.comTel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
FS-8704-12 GE-EGD Driver ManualPage 15 of 23This is the producerID.It may be the same as the IP address of theadapter 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 processor back in run mode (must be running to produce.)A second screen image shows that this exchange actually has an additional range at offset 8.FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.comTel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
FS-8704-12 GE-EGD Driver ManualPage 16 of 23You will need thisadapter’s IP address. Itwill be used as the NodeIP address in the CSVfile.Appendix A.1.2.Create a C SV 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.comTel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
FS-8704-12 GE-EGD Driver ManualAdaptersAdapterN1Page 17 of 23, Protocol, ge egdNodesNode NamePLC90-30NodesNode namenull node, IP Address, 216.232.242.3, Adapter, N1, Protocol, ge egdThis is the IP address of the producing port. You can obtain this byusing the Versapro HWC program and double clicking on the Modulewith the adapter shown in the EGD configuration. (Fred, in thisexample) Now look for the Ethernet port address., Protocol, ge egdData ArraysData Array NameDA AO 01DA AI 00DA AI 01DA AI 02DA AI 03DA AI 04DA AI 05DA AI 06DA AI 07EGD DIAGEGD STATS, Data Format, Float, BYTE, BIT, UINT16, UINT32, SINT16, SINT32, FLOAT, FLOAT, UINT32, UINT32Map DescriptorsMap Descriptor Name,egd-ii,egd-stats,, Data Array Length, 200, 100, 100, 100, 100, 100, 100, 100, 100, 100, 100Data Array Name,EGD DIAG,EGD STATS,Node NameNull NodeNull NodeFieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.comTel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
FS-8704-12 GE-EGD Driver ManualMap DescriptorsMap Descriptor NameQ1R1I1R2I2Q2, Data Array Name, DATA Q, DATA R, DATA R, DATA R, DATA R, DATA RPage 18 of 23, Data Array Offset,0,0,0,1,2,1, Function, Passive, Passive, Passive, Passive, Passive, PassiveMust correspond to the‘Local Producer’ in theEGD configuration. Notnecessarily the IPaddress of the producerport., 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.4Ge exchangeId,1,1,1,1,1,1Refer to Appendix C.1 to see how manyitems are being transmitted. Note thatthe %Q, %I references are actually bytereferences and not bit references asthey are always produced in multiplesof 8 and are always byte aligned., Ge data type, %q, %r, %u, %r, %i, %q, Ge offset,0,1,3,5,7,8These offsetsmust correspondto the offsets inthe EGDconfiguration.These data types mustcorrespond to thereferences in the EGDrange configuration.FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.comTel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
FS-8704-12 GE-EGD Driver ManualPage 19 of 23Appendix B. TroubleshootingAppendix B.1. ProducerID with FieldServer device as ProducerDuring testing it has been observed that a 90-30 PLC required that the ge ProducerID parameter was set to thesame value as the IP Address of the FieldServer.Appendix B.2. Produced Time StampThe GE-EGD (Ethernet Global Data) driver always sets the timestamp of produced data to the time of the FieldServer Device. The nanoseconds portion of the time stamp is always set to zero.Appendix B.3. Status ValuesThe status of the EGD Exchange may be monitored in the GE PLC. The status value is well documented in GFK1541 Chapter 4.4. During testing, using the Field Server device as a producer and the GE Device as a consumer thefollowing status values were observed.0 - The exchange had never been consumed1 - Normal4 - Length of produced and consumed exchange not equal - Different messages with the same exchange ID.6. - Timeout.Appendix B.4. Error MessagesMultiple protocol drivers may exist on a FieldServer. Each driver may produce its own error messages and theFieldServer itself may produce error messages.MessageEGD:#1 Error. Can’t init UDP.EGD:#2 Error. Can’t get a socket.EGD:#3 Error. Protocol does notsupport active polling. Changefunction for mapDesc %s EGD:#4 Error. Producer IDrequired for mapDesc %s EGD:#5 Error. Exchange IDrequired for mapDesc %s EGD:#6 FYI. No data typespecified. Defaulted to Byte EGD:#7 FYI. Data type notrecognized. Defaulted to Byte for mapDesc %s 4ActionThis is a fatal error. The FieldServer needs to be re-initialized or you needtechnical support from FieldServer Technologies.The rdbc/rdb/rdbx functions are not supported by this protocol. The deviceyou wish to poll must be configured to 'produce' its data and this driver will4'consume' the data using passive Map Descriptors.Each Map Descriptor requires a producerID.4Each Map Descriptor requires an exchangeID.4This is a warning only. You can eliminate the warning by editing the CSV file.Edit the CSV file, download to the FieldServer and restart the FieldServer for the changes to take effect.FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.comTel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com4
FS-8704-12 GE-EGD Driver ManualMessageEGD:#8 Error. Don't know GEDataType(%d)formapDesc %s EGD:#9 Error. Incoming datafrom ip %s producerID %s exchangeID (%d)isbeingabandoned.EGD:#10 Error. Don't know GEDataType(%d)formapDesc %s EGD:#11 FYI. You could haveused a mapDesc called egd-ii to expose diagnostic info.EGD:#12 Invalid IP. Too manycharacters.EGD:#13 Invalid IP %s EGD:#14 Error. The mapDesccalled egd-stats is too shortEGD:#15 FYI. You could haveused a m
FS-8704-12 GE-EGD Driver Manual Page 3 of 23 FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com 1 GE-EGD (ETHERNET GLOBAL DATA) DESCRIPTION The GE-EGD (Ethernet Global Data) driver allo
CAS 2700-15 Danfoss AK-SC-255 XML Page 6 of 28 2016 Chipkin Automation Systems, 3381 Cambie St- Box 211, Vancouver, BC, Canada, V5Z 4R3 Tel: (866) 383-1657, Fax: (416) 915-4024 Email: dfs@chipkin.com Website: www.chipkin.com 2.2 Wiring and Connections This section contains wiring diagrams for the various connections that are possible for this Gateway.
FS-8705-33 ACC99 Irrigation Controller Ethernet Driver Page 5 of 54 2021 CHIPKIN AUTOMATION
programmable logic controller, is important for industrial engineer. Factory automation mainly covers; Machine level automation, Production line or work cell automation, Shop floor automation, and Plant level automation. The present manual focus on the 1st level of factory automation e.g. machine automation level. It provides an introduction .
GE Mark IV Speedtronic Driver Manual 4 1 Description The GE mark IV Speedtronic driver allows the FieldServer to receive status data from Speedtronic devices over either RS-232 or RS-485 using GE Mark IV Speedtronic protocol. The Driver acts as a Passive Client and receives status data from Speedtronic devices.
May 03, 2016 · A separate Hawaii Driver’s Manual is sold at stores to help you become a well-informed, safe driver and to help you qualify for a regular Hawaii driver’s license. A separate Driver’s Manual for Commercial Motor Vehicle Driver Licensing is available at driver licensing offices and the Motor Vehicle Safety Office to prepare drivers to pass the
BACnet/IP Driver Manual 5 1 Description The BACnet/IP driver allows the FieldServer to transfer data to and from devices over Ethernet using BACnet/IP protocol. The FieldServer can emulate either a Server or Client. All information in a BACnet system is represented in terms of objects. The Object_Identifier is a 32-bit code
Modbus/TCP Server, e.g. Quantum PLC 2 Modbus/TCP Host Node [such as: Intellution Fix, Wondereware Intouch, GE Cimplicity, Quantum PLC (Master)]3 1 This cable is necessary for connection to the driver. It is shipped with the FieldServer and not separately with the driver. 2 If FieldServer is used as a Modbus/TCP Client. 3 If FieldServer is used .
Sharma, O.P. (1986). Text book of Algae- TATA McGraw-Hill New Delhi. Mycology 1. Alexopolous CJ and Mims CW (1979) Introductory Mycology. Wiley Eastern Ltd, New Delhi. 2. Bessey EA (1971) Morphology and Taxonomy of Fungi. Vikas Publishing House Pvt Ltd, New Delhi. 3. Bold H.C. & others (1980) – Morphology of Plants & Fungi – Harper & Row Public, New York. 4. Burnet JH (1971) Fundamentals .
