manualshive.com logo in svg

FieldServer FS-8700-66, Manual

Share
Download
FieldServer FS-8700-66 Manual Download Page 25

Page 25 of 29FS-8700-66_GE-SNP Manual 

 

 

 

 

Page 25 of 29 

 

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

: [email protected] 

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.  
 
If  the  Client  sends  a  Null  Node  name  then  the  FieldServer  will  connect  if  any  SNP  Nodes 
have been defined for the same port as the Client using the Null name.  In such a case the 
Node  must  be  connected  to  a  port  (This  is  not  always  common  with  FieldServer  Server 
configurations). 

 

Example

: Client uses Null name connection. In this case Node must be connected to the 

Client’s port; the Node name is ignored and only one SNP Node per port. 

 

Ports 

 

Port, 

baud 

P1  , 

…. 

 

 

Nodes 

 

Node_Name, 

Port 

Node1, 

P1 

 

If  the  Client  uses  the  Node  name  during  a  connection  attempt  then  the  FieldServer  uses 
the name to find a matching Node.  The name must be an exact match.  If a match is found 
then the connection can be established.  In this case the Node does not have to be tied to 
a particular port and thus one Node could respond to different Clients polling it on different 
ports.  If this method is used and the Node is tied to a port then the Client must poll on the 
same port. 

 

Example:

  Client  uses  a  specific  name  to  connect.  In  this  case  provided  there  is  a  Node 

with a matching name the connection will be made  

 

Ports 

 

Port, 

baud …. 

P1,   

…. 

 

 

Nodes 

 

Node_Name, 

Protocol  

Node1,         

 SNP 

 

Summary of Contents for FS-8700-66

Page 1: ...itor 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 9 ...

Page 2: ...ptor Parameters 10 4 4 2 Driver Related Map Descriptor Parameters 11 4 4 3 Timing Parameters 11 4 4 4 Map Descriptor Example 1 Simple Read 12 4 4 5 Map Descriptor Example 2 Simple Write 12 4 4 6 Map Descriptor Example 3 Handling Bits 13 5 Configuring the FieldServer as a GE_SNP Server 14 5 1 Server Side Connection Descriptors 14 5 2 Server Side Node Descriptors 15 5 3 Server Side Map Descriptors 1...

Page 3: ...ver 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 messages are defined by the SNP protocol to allow multiple data types to be packed into one message They are not commonly used by the HMI and 3rd part...

Page 4: ...eldServer com Tel 408 262 2299 Fax 408 262 2296 Toll_Free 888 509 1970 email support fieldServer com 2 Driver Scope of Supply 2 1 Supplied by FieldServer Technologies for this driver FieldServer Technologies PART Description FS 8915 10 UTP cable 7 foot for RS 232 use FS 8917 03 RJ45 to DB9M connector adapter FS 8700 66 Driver Manual ...

Page 5: ...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 DATE 2 2 04 BY MF BASE NAME FILE NAME GE SNP CONNECTION DIAGRAM FieldServer GE PLC RS 485 port RS 232 port RS 232 port RJ11 RS 485 port 15 pin female Pin...

Page 6: ...CHO 4W 2W 4W 2W TERM JP1 TB1 TB2 R1 or R2 B A GND FieldServer 2 3 4 7 DB25F 91035 7 Rx Tx RTS GND Note Pins 4 5 and pins 6 8 20 are bridged internally to allow for RS 232 devices that need hardware control RS 232 Device 2 3 5 J2 Rx Tx RTS GND RS 232 TO RS 422 485 OPTICALLY ISOLATED CONVERTER Recceive Transmit RS 232 SR 422 485 MODEL485OTLED electronics B B TDA TDB RDA RDB 422 485 GND SD RTS 12V R ...

Page 7: ...F 408 262 2299 BASE NAME FILE NAME GE SNP CONNECTION DIAGRAM P1 P8 RJ45 PLC Pri or 2ndary port CPU or 2ndary port Horner 232 to 422 9 pin 15 pin Horner 232 to 422 9 pin 15 pin RJ45 black yellow blue white green 3 2 5 9 pin Ethernet cable segment 9 pin 25 pin PC Com1 6 7 2 3 5 RJ45 black yellow blue white green 9 pin RJ45 black yellow blue white green 9 pin 9 pin null modem 5 3 2 7 6 5 3 2 Typical ...

Page 8: ...the FieldServer for GE_SNP 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 and the data required from the Servers needs to be mapped in the Client Side Map Descriptors section Details on how to do this can be found below Note that in the tables indicates an...

Page 9: ...is not supported None Poll _Delay Time between internal polls 0 32000 seconds 1 second Timeout The timeout specified for the connection is used as the data link layer timeout It is also used as the timeout for each Map Descriptor if a timeout is not explicitly defined for a Map Descriptor Example Client Side Connections Connections Port Protocol Baud Parity Handshaking Poll_Delay P1 SNP 19200 Odd ...

Page 10: ...ed to control how the driver logs onto the PLC Read the notes above Node_Name 0 1 Protocol Specify protocol used SNP Port Specify which port the device is connected to the FieldServer P1 P8 R1 R22 Example Client Side Nodes Nodes Node_Name Node_ID Protocol Port PLC 1 1 SNP P8 4 4 Client Side Map Descriptors 4 4 1 FieldServer Related Map Descriptor Parameters Column Title Function Legal Values Map_D...

Page 11: ... does not exceed the table in the PLC 1 1000 Address Starting address of read block write block The 1st element of each Data type Table is referred to as address one 1 2 3 Positive whole numbers Format Use to override the default format for obtaining data Bit tables are by default read by reading whole bytes at a time If the Length is 10 then 10 bytes of data are read and placed in 10 Data Array l...

Page 12: ...erval Data_Type Write_AO DA_AO 0 WRBC Node1 20 10 5 0 AQ Use the symbol as you would if you were programming a GE PLC The name of the Data Array in which the driver will store the data The name must correspond to a Data Array defined in the Data Array section of the CSV file Map Descriptor names may be used in driver error messages It is not essential but it is useful to use unique names RDBC read...

Page 13: ...ta 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 2 2 0 T Bit The format parameter tells the driver to override the default data ty...

Page 14: ...eclared in the Data Arrays section the FieldServer virtual Node s needs to be declared in the Server Side Nodes section and the data to be provided to the Clients needs to be mapped in the Server Side Map Descriptors section Details on how 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 1 Server Side Connection Des...

Page 15: ...for additional information Up to 32 alphanumeric characters Node_ID The parameter is used to control how the driver logs onto the PLC Read the notes above Node_Name 0 1 Protocol Specify protocol used SNP Server_Hold_Timeout In a number of FieldServer configurations it is common to omit the port when defining a Server Node this cannot be done with the SNP protocol unless the FieldServer is to be us...

Page 16: ...Descriptor Parameters Column Title Function Legal Values Node_Name Name of Node to fetch data from One of the Node names specified in Client Node Descriptor above Data_Type Data type Use one of the Data Types specified in brackets Discrete Inputs I Discrete Outputs Q Discrete Temporaries T Discrete Internals M Genius Global Data G Analog Inputs AI Analog Outputs AQ Registers R SA Discrete SB Discr...

Page 17: ...a 95035 USA Web www fieldServer com Tel 408 262 2299 Fax 408 262 2296 Toll_Free 888 509 1970 email support fieldServer com 5 3 3 Timing Parameters Column Title Function Legal Values Scada_Hold_Timeout Specifies time Server side waits before responding to Client that Node is offline on FieldServer Client side 1 0s ...

Page 18: ...esponse data will be obtained from this table If the Client is writing incoming data will be stored in this array Address1 corresponds to offset 0 1 st 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 This Map Descriptor can be used to respond to a poll that reads and writes to...

Page 19: ...times out in the FieldServer After timing out the driver re establishes the connection for the next poll Very slow Comms Rate A timer known as the T1 timer is the minimum time that must pass before a response to a message can be sent Both ends of a SNP connection have their own T1 timer hard coded in the driver When a connection is made the timers are exchanged and the larger of the two is used Th...

Page 20: ...ed unsupported aspect of the SNP protocol If the message occurs frequently take a log and report the error to FieldServer SNP 6 FYI T1 timer set to ld mSec This message requires no action It reports the T1 timer value selected by the slave in milliseconds If the value is large then this will slow the communications rate and you may wish to reconfigure the slave SNP 7 FYI T1 timer reset to ld mSec ...

Page 21: ... and contact FieldServer for support SNP 14 Error Attach Response Unexpected The driver has been polled by a Client and it has received an unexpected message If the error occurs repeatedly then make a log record the values reported in this message and contact FieldServer for support There are a few variations of this message but they all indicate the same problem SNP 15 FYI Node Station forcing to...

Page 22: ... SNP stats Example Configuration of this special Map Descriptor Nodes Node_Name Protocol Null_Node SNP Data_Arrays Data_Array_Name Data_Format Data_Array_Length SNP_STATS UINT32 660 Map_Descriptors Map_Descriptor_Name Data_Array_Name Node_Name Length snp stats SNP_STATS Null_Node 660 When the driver sees this Map Descriptor it uses the Data Array SNP_STATS in this example to store driver specific ...

Page 23: ... however the device can not necessarily respond to the request 25 DRV_DLL_CLIENT_SENDS_BYTES Byte count includes ack nak s sent and all fragments and connection 26 DRV_DLL_SERVER_SENDS_MSG 27 DRV_DLL_SERVER_SENDS_ACKNAK 28 DRV_DLL_SERVER_SENDS_BYTES Same as for Client 29 DRV_DLL_CLIENT_RCVS_MSG Counts ack nak s and all message fragments excluding attach responses 30 DRV_DLL_CLIENT_RCVS_BYTES Byte ...

Page 24: ...ECK A message is invalid because the checksum failed 43 GE_STAT_CD_UPD_FUNCTION A message is invalid because the message type is not known 44 GE_STAT_CD_UPD_NO_START A message is invalid because it begins with the wrong codes 45 GE_STAT_CD_UPD_PROTO A message is invalid because it is unexpected in its current context or some other reason 46 GE_STAT_CLIENT_SENDS_FRAG Counts the number of read write...

Page 25: ...nected to a port This is not always common with FieldServer Server configurations Example Client uses Null name connection In this case Node must be connected to the Client s port the Node name is ignored and only one SNP Node per port Ports Port baud P1 Nodes Node_Name Port Node1 P1 If the Client uses the Node name during a connection attempt then the FieldServer uses the name to find a matching ...

Page 26: ...ata The Data age is greater than the CACHE_AGE setting 0x05 0xbc Other Problems Eg No Server MD s defined for requested data Major Error Status Codes Error Status Description 01h Illegal Service Request Either not defined or not supported 02h Insufficient Privilege Minor status field contains the privilege level required for the service request 04h Protocol Sequence Error The CPU has received a me...

Page 27: ... to locate given connection ID 36 0DC Unable to find connection address 37 0DB Invalid segment selector in Datagram 38 0DA Null pointer to data in segment selector 39 0D9 Transfer type invalid for this selector 40 0D8 Point length not allowed 41 0D7 Invalid Datagram type specified 42 0D6 Datagram connection boundary exceeded 43 0D5 Invalid block name specified in Datagram 44 0D4 Mismatch of config...

Page 28: ... in the PLC 74 0B6 Cyclic Redundancy Check CRC checksum comparison in Verify failed 75 0B5 Additive checksum comparison in Verify failed 76 0B4 Attempt to alter interrupt list in MAIN DECL BLOCK during RUN MODE 77 0B3 Length limit exceeded includes read past end of transferred data writes past ofprogram block 78 0B2 Program block already exists and cannot be replaced Minor Error Status Codes Progr...

Page 29: ...ual Page 29 of 29 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 THIS PAGE INTENTIONALLY LEFT BLANK ...

Reviews:

No comments

Brands by name

Popular brands

Load more brands