Summary of the content on the page No. 1
-
A Sierra Monitor Company
Driver Manual
(Supplement to the FieldServer Instruction Manual)
FS-8700-66 GE SNP
APPLICABILITY & EFFECTIVITY
Effective for all systems manufactured after May 1, 2001
Driver Version: 1.02
Document Revision: 9
Summary of the content on the page No. 2
FS-8700-66_GE-SNP Manual Table of Contents TABLE OF CONTENTS 1. GE_SNP Description ...................................................................................................... 3 2. Driver Scope of Supply.................................................................................................. 4 2.1. Supplied by FieldServer Technologies for this driver.................................................. 4 3. Hardware Connections ......................................
Summary of the content on the page No. 3
Page 3 of 29FS-8700-66_GE-SNP Manual Page 3 of 29 1. GE_SNP Description The GE-SNP Serial driver allows the FieldServer to transfer data to and from devices over either RS-232 or RS-485 using GE-SNP Serial protocol. The FieldServer can emulate either a Server or Client. The FieldServer provides functions to read and write PLC memory and change the privilege level. Standard SNP mailbox messages are used. The driver does not support Datagram messages and cannot parse them. These
Summary of the content on the page No. 4
Page 4 of 29FS-8700-66_GE-SNP Manual Page 4 of 29 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 RS-232 use FS-8917-03 RJ45 to DB9M connector adapter FS-8700-66 Driver Manual. FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.com Tel: (408) 262-2299 Fax: (408) 262-2296 Toll_Free: 888-509-1970 email: support@fieldServe
Summary of the content on the page No. 5
Cable 4 Page 5 of 29FS-8700-66_GE-SNP Manual Page 5 of 29 3. Hardware Connections The FieldServer is connected to the GE PLC in one of two ways. Almost every GE PLC has a RS-232 and RS-485 port. Possible cable configurations are illustrated below. A converter is required to connect between RS-232 and RS-485. An example of connection configurations for the Model480TLED connector is depicted overleaf. Any equivalent connector can be used. Cable 1 RS-485 port RS-485 port 15 p
Summary of the content on the page No. 6
RS-232 RS-232 Page 6 of 29FS-8700-66_GE-SNP Manual Page 6 of 29 Remote Serial Device– 4 wire TDA(-) TDB (+) RDB(+) RDA(-) RS- 232 TO RS-422/485 GND O OPTICALLY ISOLATED N 2 2 CONVERTER 1 2 3 4 5 6 7 8 3 3 Recceive TB1 4 TDA(-) TDB(+) 5 Transmit RDA(-) RDB(+) 7 7 electronics B&B 422/ 485 GND MODEL4 85OTLED TB2 +12V J2 R-232 GND Remote Serial DB25F Device– 2 wire 21787 91035 + (B) - (A) From FieldServer GND Converter for Cable 3: From RS-232 on FieldServer to RS-485 on
Summary of the content on the page No. 7
black yellow blue white gre n e black 6 yellow 7 blue 2 white 3 green 5 Page 7 of 29FS-8700-66_GE-SNP Manual Page 7 of 29 RJ45 Ethernet cable segment RJ45 5 3 2 7 6 9 pin 9 pin Horner 9 pin 5 3 2 232 to 9 pin 422 15 pin CPU or 2ndary port 25 pin PLC null modem Pri or 2ndary port GE LOGICMASTER PC Software to PLC 15 pin Horner 232 to 9 pin 422 9 pin Com1 9 pin PC RJ45 Typical FieldServer Cable (408)-262-2299 RJ45 P1-P8 GE SNP CONNECTION DIAGRAM BASE NAME: DATE: 2/2/04 FILE NAME: BY:
Summary of the content on the page No. 8
Page 8 of 29FS-8700-66_GE-SNP Manual Page 8 of 29 4. Configuring the FieldServer as a GE_SNP Client For a detailed discussion on FieldServer configuration, please refer to the FieldServer Configuration Manual. The information that follows describes how to expand upon the factory defaults provided in the configuration files included with the FieldServer (See “.csv” sample files provided with the FieldServer). This section documents and describes the parameters necessary for configuri
Summary of the content on the page No. 9
Page 9 of 29FS-8700-66_GE-SNP Manual Page 9 of 29 4.2. Client Side Connection Descriptors Section Title Connections Column Title Function Legal Values Specify which port the device is 1 Port P1-P8, R1-R2 connected to the FieldServer Protocol Specify protocol used SNP 110 – 19200, standard baud rates Baud* Specify baud rate only (Vendor limitation), 19200 Parity* Specify parity Even, Odd, None, Mark, Space Data_Bits* Specify data bits 7, 8 Stop_Bits* Specify stop bits 1 Hands
Summary of the content on the page No. 10
Page 10 of 29FS-8700-66_GE-SNP Manual Page 10 of 29 4.3. Client Side Node Descriptors Section Title Nodes Column Title Function Legal Values Provide name for Node. The driver uses the Node name to establish a connection with the Server if the Node_ID is non-zero. If the Node_ID is zero then the driver Up to 32 alphanumeric Node_Name ignores the Node name when logging characters onto the PLC and logs on using a Null name. Thus by setting the Node_ID to zero you can allow th
Summary of the content on the page No. 11
Page 11 of 29FS-8700-66_GE-SNP Manual Page 11 of 29 4.4.2. Driver Related Map Descriptor Parameters Column Function Legal Values Title One of the Node names specified in Node_Name Name of Node to fetch data from “Client Node Descriptor” above Discrete Inputs (%I) Discrete Outputs (%Q) Discrete Temporaries (%T) Discrete Internals (%M) Genius Global Data (%G) Data_Type Data type Analog Inputs (%AI) Analog Outputs (%AQ) Registers (%R) %SA Discrete %SB Discrete %SC Dis
Summary of the content on the page No. 12
Page 12 of 29FS-8700-66_GE-SNP Manual Page 12 of 29 4.4.4. Map Descriptor Example 1 – Simple Read This example provides a Map Descriptor to read 10 bytes of Discrete Input states, starting at the very first Discrete Input. The data is st stored in a Data Array called DA_DI and the first input is stored at location 100 in the array (101 element). The PLC is polled every 2 seconds Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function, Node_Name Address Length Scan_Interval
Summary of the content on the page No. 13
Page 13 of 29FS-8700-66_GE-SNP Manual Page 13 of 29 4.4.6. Map Descriptor Example 3 – Handling Bits This example writes data from the FieldServer Data Array called DA_AO to the PLC identified as NODE1. The write is repeated every 5 seconds. Ten word values are written to the PLC’s %AQ Data Table starting at location 20. Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function, Node_Name, Address, Length, Scan_Interval, Data_Type, Format Read_DI,, DA_T, 100, RDBC, PLC-1, 8,
Summary of the content on the page No. 14
Page 14 of 29FS-8700-66_GE-SNP Manual Page 14 of 29 5. Configuring the FieldServer as a GE_SNP Server For a detailed discussion on FieldServer configuration, please refer to the FieldServer Configuration Manual. The information that follows describes how to expand upon the factory defaults provided in the configuration files included with the FieldServer (See “.csv” files provided with the FieldServer). This section documents and describes the parameters necessary for configuring th
Summary of the content on the page No. 15
Page 15 of 29FS-8700-66_GE-SNP Manual Page 15 of 29 5.2. Server Side Node Descriptors Section Title Nodes Column Title Function Legal Values The Node name is used differently in a Server Node Provide name for Node. The driver uses the Node name to establish a connection with the Up to 32 alphanumeric Node_Name Server if the Node_ID is non- characters zero. See Section 6.3 for additional information. The parameter is used to control how the driver logs onto Node_ID 0,1 t
Summary of the content on the page No. 16
Page 16 of 29FS-8700-66_GE-SNP Manual Page 16 of 29 5.3. Server Side Map Descriptors 5.3.1. FieldServer Specific Map Descriptor Parameters Column Title Function Legal Values Up to 32 alphanumeric Map_Descriptor_Name Name of this Map Descriptor characters Name of Data Array where data One of the Data Array names Data_Array_Name is to be stored in the FieldServer from “Data Array” section above 0 to maximum specified in “Data Data_Array_Offset Starting location in Data Array Arra
Summary of the content on the page No. 17
Page 17 of 29FS-8700-66_GE-SNP Manual Page 17 of 29 5.3.3. Timing Parameters Column Title Function Legal Values Specifies time Server side waits before responding to Scada_Hold_Timeout >1.0s Client that Node is offline on FieldServer Client side. FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.com Tel: (408) 262-2299 Fax: (408) 262-2296 Toll_Free: 888-509-1970 email: support@fieldServer.com
Summary of the content on the page No. 18
Page 18 of 29FS-8700-66_GE-SNP Manual Page 18 of 29 5.3.4. Map Descriptor Example. Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function, Node_Name, Address, Length, Data_Type Server-R-Data, TABLE_R, 0, Passive, PLC-1, 1, 1000, %R If the Client is reading Address1 corresponds This is a Server. It This Map Descriptor can be then response data will st to offset 0 (1 location) responds to polls but used to respond to a poll be obtained from this in the array. If Cli
Summary of the content on the page No. 19
Page 19 of 29FS-8700-66_GE-SNP Manual Page 19 of 29 Appendix A. Troubleshooting Tips nd • Every 2 message Times Out A possible cause is that the poll frequency is so low that the time between polls is greater than the Max Link Idle Time (of the PLC). If the time is exceeded the connection is closed. Thus when the next poll is received by the PLC it ignores it and hence it times out in the FieldServer. After timing out, the driver re-establishes the connection for the next poll. • V
Summary of the content on the page No. 20
Page 20 of 29FS-8700-66_GE-SNP Manual Page 20 of 29 Appendix B. Error Messages Message Explanation SNP:#1 FYI. The MapDesc called The length of the Map Descriptor defined to expose driver 5 <%s> is too short. statistics must be at least 660. SNP:#2 FYI. You could have You may safely ignore this message. Read Appendix B.1 used a MapDesc called <%s> to for information on how to expose the driver’s expose diagnostic info. communication statistics using a Data Array. The driver is req
