Technologies Computer Driver Instruction Manual

ManualsBrandsFieldServer ManualsComputer HardwareFS-8700-66

A Sierra Monitor Company

APPLICABILITY & EFFECTIVITY

Effective for all systems manufactured after May 1, 2001

Driver Manual

(Supplement to the FieldServer Instruction Manual)

FS-8700-66 GE SNP

Driver Version:

1.02

Document Revision:

Summary of content (29 pages)

PAGE 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.
PAGE 2
FS-8700-66_GE-SNP Manual Table of Contents TABLE OF CONTENTS 1. GE_SNP Description ...................................................................................................... 3 2. 2.1. Driver Scope of Supply .................................................................................................. 4 Supplied by FieldServer Technologies for this driver.................................................. 4 3. Hardware Connections ........................................................
PAGE 3
Page 3 of 29FS-8700-66_GE-SNP Manual 1. Page 3 of 29 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.
PAGE 4
Page 4 of 29FS-8700-66_GE-SNP Manual 2. Page 4 of 29 Driver Scope of Supply 2.1. Supplied by FieldServer Technologies for this driver FieldServer Technologies PART # FS-8915-10 FS-8917-03 FS-8700-66 Description UTP cable (7 foot) for RS-232 use RJ45 to DB9M connector adapter 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@fieldServer.
PAGE 5
Page 5 of 29FS-8700-66_GE-SNP Manual 3. Page 5 of 29 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. illustrated below. Possible cable configurations are 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.
PAGE 6
Page 6 of 29FS-8700-66_GE-SNP Manual Page 6 of 29 RS- 232 TO RS-422/ 485 OPTICALLY ISOLATED CONVERTER 3 4 5 7 7 Recceive Transmit B& B electronics 1 2 3 4 5 6 7 SD RTS 3 O N SR-422/485 2 RS-232 FS-8917-01 2 8 TB1 TDA(-) TDB(+) RDA(-) RDB(+) 422/ 485 GND MODEL485 OTLED TB2 +12V R-232 GND J2 DB25F 21787 TDA(-) TDB (+) RDB(+) RDA(-) GND JP1 4800 9600 19.2K 38.4K ECHO 4W/2W 4W/2W TERM.
PAGE 7
Page 7 of 29FS-8700-66_GE-SNP Manual Page 7 of 29 RJ45 Ethernet cable segment black yellow blue white green 6 7 2 3 5 Horner 232 to 422 9 pin black yellow blue white green 5 3 2 7 6 RJ45 9 pin 9 pin 5 3 2 9 pin 15 pin CPU or 2ndary port 25 pin PLC null modem Pri or 2ndary port 15 pin 9 pin 9 pin Com1 9 pin PC black yellow blue white green 3 2 5 Horner 232 to 422 GE LOGICMASTER PC Software to PLC RJ45 Typical FieldServer Cable (408)-262-2299 RJ45 P1-P8 GE SNP CONNECTION DIAGRAM BAS
PAGE 8
Page 8 of 29FS-8700-66_GE-SNP Manual 4. Page 8 of 29 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).
PAGE 9
Page 9 of 29FS-8700-66_GE-SNP Manual 4.2.
PAGE 10
Page 10 of 29FS-8700-66_GE-SNP Manual 4.3. Page 10 of 29 Client Side Node Descriptors Section Title Nodes Column Title Node_Name Node_ID Protocol Port 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 ignores the Node name when logging onto the PLC and logs on using a Null name.
PAGE 11
Page 11 of 29FS-8700-66_GE-SNP Manual 4.4.2. Driver Related Map Descriptor Parameters Column Title Function Node_Name Name of Node to fetch data from Data_Type Data type Length Address Format* GE_Func* Page 11 of 29 Length of Map Descriptor. Ensure that the length does not exceed the table in the PLC Starting address of read block / write block. The 1st element of each Data type Table is referred to as address one. Use to override the default format for obtaining data.
PAGE 12
Map Descriptor Example 1 – Simple Read Page 12 of 29 Map Descriptor Example 2 – Simple Write RDBC = read block continuous. The driver will read data from the PLC continuously. Address 1, Length 10, Data_Type %1 Use the % symbol as you would if you were programming a GE PLC. Read will be performed every 2.0s. Scan_Interval, 2.0, The address and length specify the first element and the number of elements that must be read from the PLC’s data tables.
PAGE 13
Map Descriptor Example 3 – Handling Bits Page 13 of 29 Data_Array_Name, DA_T, Function, RDBC, Node_Name, PLC-1, Address, 8, Length, 2, Scan_Interval, 2.0, The format parameter tells the driver to override the default data type and read bits specifically. In this case the bits are stored in the Data Array in two separate elements at DA_T[100] and DA_T[101] Data_Array_Offset, 100, Data_Type, %T, FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.
PAGE 14
Page 14 of 29FS-8700-66_GE-SNP Manual 5. Page 14 of 29 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).
PAGE 15
Page 15 of 29FS-8700-66_GE-SNP Manual 5.2. Page 15 of 29 Server Side Node Descriptors Section Title Nodes Column Title Node_Name Node_ID Protocol Server_Hold_Timeout* 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 Server if the Node_ID is non- characters zero. See Section 6.3 for additional information.
PAGE 16
Page 16 of 29FS-8700-66_GE-SNP Manual 5.3. Page 16 of 29 Server Side Map Descriptors 5.3.1. FieldServer Specific Map Descriptor Parameters Column Title Function Map_Descriptor_Name Name of this Map Descriptor Data_Array_Name Name of Data Array where data is to be stored in the FieldServer Data_Array_Offset Starting location in Data Array Function Function Descriptor 5.3.2.
PAGE 17
Page 17 of 29FS-8700-66_GE-SNP Manual 5.3.3. Page 17 of 29 Timing Parameters Column Title Function Scada_Hold_Timeout Specifies time Server side waits before responding to Client that Node is offline on FieldServer Client side. Legal Values >1.0s 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.
PAGE 18
Address1 corresponds st to offset 0 (1 location) in the array. If Client reads %R15 then driver responds with data from element 14 of the array. This is a Server. It responds to polls but does no active work itself. Node_Name, PLC-1, Address, 1, This Map Descriptor can be used to respond to a poll that reads and writes to addresses 1 to 1000. If a poll attempts to read data at address 1001, then if no other Map Descriptor covers that address space, a “no datas” response will be sent.
PAGE 19
Page 19 of 29FS-8700-66_GE-SNP Manual Page 19 of 29 Appendix A. Troubleshooting Tips • • • Every 2nd 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.
PAGE 20
Page 20 of 29FS-8700-66_GE-SNP Manual Page 20 of 29 Appendix B. Error Messages Message SNP:#1 FYI. The MapDesc called <%s> is too short. SNP:#2 FYI. You could have used a MapDesc called <%s> to expose diagnostic info. SNP:#3 FYI. SNP device requires inter msg timer < timeout. Nid=<%s>. SNP:#4 Error. Node=<%s> Cant SNP:#5 Err. Total expected/rcvd=%d/%d emulate bytes SNP:#6 FYI. T1 timer set to <%ld> mSec. SNP:#7 FYI. T1 timer reset to <%ld> mSec. SNP:8 FYI. Subsequent connect response ignored.
PAGE 21
Page 21 of 29FS-8700-66_GE-SNP Manual Message SNP:11 Err. Max Tbuf Len. FieldServer cant go bigger than %d bytes Possible Offending Poll =<%s> addr=%d length=%d SNP:12 FYI. Max Tbuf Len. FieldServer != Device. Changed FieldServer to %d bytes SNP:13 Err. Wrong type=%d(h) mbox=%x(h) msg SNP:#14 Error. Attach Response. Unexpected ! SNP:#15 FYI. Node Station forcing to 0 SNP:#16 Err. Addresses start at 1. MapDesc=<%s> SNP:#17 Err. MapDesc=<%s> has bad data type. SNP:#18 Err. MapDesc=<%s> has bad data type.
PAGE 22
Page 22 of 29FS-8700-66_GE-SNP Manual Page 22 of 29 Appendix B.1. Driver Stats The statistics recorded by the GE-SNP Serial Driver are slightly different from the way that FieldServer driver normally records statistics. This difference arises from the fact that this driver is not a simple poll response driver. Bear in mind that a single poll can generate a large number of response fragments. Fragment Ack/nack messages are NOT counted as messages but the bytes sent/rcvd are counted.
PAGE 23
Page 23 of 29FS-8700-66_GE-SNP Manual No Message Page 23 of 29 Description 17 GE_STAT_MBOX_PLC_STAT 18 GE_STAT_MBOX_PRIV_LVL 19 GE_STAT_NO_NODES 20 GE_STAT_CONNECT_ATTEMPT 21 GE_STAT_CONNECT_RESPONSE 22 GE_STAT_CONNECT_NO_RESPONSE 23 DRV_DLL_CLIENT_SENDS_MSG 24 DRV_DLL_CLIENT_SENDS_ACKNAK 25 DRV_DLL_CLIENT_SENDS_BYTES 26 DRV_DLL_SERVER_SENDS_MSG 27 DRV_DLL_SERVER_SENDS_ACKNAK 28 DRV_DLL_SERVER_SENDS_BYTES If a poll for a SNP Node is received and there are no Nodes defined or there is no matching Node
PAGE 24
Page 24 of 29FS-8700-66_GE-SNP Manual No Message 38 GE_STAT_DRV_ACT_NO_DATA_R 39 GE_STAT_DRV_ACT_NO_NODE_R 40 GE_STAT_DRV_ACT_NAK_R 41 GE_STAT_DRV_ACT_NORMAL_R 42 GE_STAT_CD_UPD_CHECK 43 GE_STAT_CD_UPD_FUNCTION 44 GE_STAT_CD_UPD_NO_START 45 GE_STAT_CD_UPD_PROTO 46 GE_STAT_CLIENT_SENDS_FRAG 47 GE_STAT_CD_UPD_IC_TIMEOUT 48 GE_STAT_CD_UPD_MSG_IGNORED 49 GE_STAT_CD_UPD_NAK 50 GE_STAT_CD_UPD_STREAMING Page 24 of 29 Description Corresponds to slave driver actions in responding to a poll.
PAGE 25
Page 25 of 29FS-8700-66_GE-SNP Manual Page 25 of 29 Appendix C. Advanced Topics Appendix C.1. SNP Node Names The following notes describe how the Node name is used when the FieldServer is acting as a Server. When a Client attempts to establish a connection it may do so by sending the name of the Node it wishes to connect to or by sending a Null Node name.
PAGE 26
Page 26 of 29FS-8700-66_GE-SNP Manual Page 26 of 29 Appendix C.2. Scaling Scaling was added in version 1.02a and is not supported for earlier versions. Scaling is applied by the driver when bytes and registers are stored. When bit data is transferred in bit format than scaling is not applied. When bit data is transferred using bye format’s then scaling may be applied. Scaling is applied using the FieldServer’s standard Map Descriptor parameters.
PAGE 27
Page 27 of 29FS-8700-66_GE-SNP Manual Decimal -10 -11 -12 -13 -14 -15 -16 -17 -18 -19 -20 -21 -22 -23 -24 -25 -26 -27 -28 -29 -30 -31 -32 -33 -34 -35 -36 -37 -38 -39 -40 -41 -42 -43 -44 -45 -46 -47 -48 49 -50 -51 -52 -53 -54 -55 -56 -57 -58 -59 -60 -61 Hex 0F6 0F5 0F4 0F3 0F2 0F1 0F0 0EF 0EE 0ED 0EC 0EB 0EA 0E9 0E8 0E7 0E6 0E5 0E4 0E3 0E2 0E1 0E0 0DF 0DE 0DD 0DC 0DB 0DA 0D9 0D8 0D7 0D6 0D5 0D4 0D3 0D2 0D1 0D0 0CF 0CE 0CD 0CC 0CB 0CA 0C9 0C8 0C7 0C6 0C5 0C4 0C3 Page 27 of 29 Description Invalid sweep stat
PAGE 28
Page 28 of 29FS-8700-66_GE-SNP Manual Decimal -62 -63 -64 -65 -66 -67 -68 -69 -70 -71 -72 -73 -74 -75 -76 -77 Hex 0C2 0C1 0C0 0BF 0B 0BD 0BC 0B 0B 0B9 0B8 0B7 0B6 0B5 0B4 0B3 -78 0B2 Page 28 of 29 Description The OEM key is NULL (inactive). Invalid block state transition. Bad OMF record checksum in store. Illegal OMF record type/data contents. Bad Block Type given in Load/Store. Block Set (subblock name) not found. Block Type (e.g., data) not found. Maximum length of a partial store exceeded.
PAGE 29
Page 29 of 29FS-8700-66_GE-SNP Manual Page 29 of 29 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-2296 Toll_Free: 888-509-1970 email: support@fieldServer.