background image

FS-8704-13 GE-SRTP  

 

Driver Manual 

 

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 (408) 262-2299 fax: (408) 262-9042 

Visit our website: www.fieldserver.com          E-mail:  support@fieldserver.com 

 

Page 15 

6.  Driver Notes 

6.1  Driver Stats  

 

The statistics recorded by the GE-SNPX Serial Driver are slightly different from the way that 
Fieldserver driver normally record statistics. This difference arises from the fact that this driver is 
not a simple poll response driver. Bare in mind that a single poll can generate a large number of 
response fragments. 
 
Fragment Ack/nack messages are NOT counted as message but the bytes sent/rcvd are counted. 
Connection messages are counted as messages and the bytes sent/rcvd are counted. 
 
This driver can expose these and additional statistics by writing data to a data array.  
 
A special map descriptor is required. The driver recognizes the map descriptor by its name which 
must be "

SRTP-stats

" . 

 
The following example shows how this special map descriptor can be configured. 
 

Nodes 
Node_name, Protocol

 

null_node, SRTP 
 

Data_Arrays 
Data_Array_Name, Data_Format, Data_Array_Length

 

SRTP_STATS       , UINT32        ,  600 
 
Map_blocks 
Map_block_Name, Data_Array_Name, Node_name, Length 
srtp-stats                , SRTP _STATS      , null_node   , 600 
 
 
When the driver sees this map descriptor it uses the data array SRTP _STATS (in this example) 
to store driver specific statistics. Only one of these map descriptors may be specified (per tier) per 
FieldServer. 
 
The driver stores the following stats for each port.. The offset into the data array can be found by 
multiplying the port number by 50 

 

Stat # 

Stat Code 

1 GE_STAT_BAD_SEND                
2 GE_STAT_POLL_MSGS_SENT          
3 GE_STAT_POLL_BYTES_SENT         
4 GE_STAT_SESS_CONNECT            
5 GE_STAT_DEV_CONNECT             
6 GE_STAT_BAD_PDU                 
7 GE_STAT_BAD_PROTOCOL            
8 GE_STAT_TIMEOUT                 
9 GE_STAT_MBOX_NAK_MAJOR          

Summary of Contents for FS-8704-13

Page 1: ...l systems manufactured after January 1 1999 Instruction Manual Part Number FS 8704 13 Version 1 00 Revision 1 a 9 26 2002 Driver Manual Supplement to the FieldServer Instruction Manual FS 8704 13 GE SRTP Ethernet Driver A Sierra Monitor Company ...

Page 2: ... 4 4 Client Side Map Descriptors 5 4 4 1 FieldServer Specific Map Descriptor Parameters 5 4 4 2 Driver Specific Map Descriptor Parameters 6 4 4 3 Timing Parameters 6 4 4 4 Map Descriptor Example 1 Simple Read 7 4 4 5 Map Descriptor Example 2 Simple Write 8 4 4 6 Map Descriptor Example 3 Handling Bits 9 5 Configuring the FieldServer as a GE SRTP Driver Server 10 5 1 Data Arrays 10 5 2 Server Side C...

Page 3: ... allows the FieldServer to transfer data to and from devices over Ethernet using GE SRTP Driver protocol There are two Ethernet ports standard on the FieldServer The FieldServer can emulate either a Server or Client The GE SRTP driver is capable of read writing the data tables of a GE series 90 PLC which is equipped with an Ethernet port The driver is capable of exposing its communication statisti...

Page 4: ...www fieldserver com E mail support fieldserver com Page 2 2 Driver Scope of Supply 2 1 Supplied by FieldServer Technologies for this driver UTP cable 7 foot for Ethernet connection UTP cable 7 foot for RS232 use RJ45 to DB9F connector adapter RJ45 to DB25M connection adapter RS485 connection adapter Driver Manual 2 2 Provided by user GE SRTP System ...

Page 5: ...ed to a hub DATE 12 7 01 BY MN 408 262 2299 BASE NAME FILE NAME FS T28704 13 VSD GE SRTP CONNECTION DIAGRAM P4 P1 Rx P2 P3 T x R x Tx Tx Rx Rx P7 P5 P6 Tx Rx Tx T x Rx Rx P8 R1 T x R x Tx R x Tx R2 Net 1 T x Rx R x Tx Con Net 2 Sys Co m Tx Rx Con Act Ru n Pwr RS485 RS232 10 Base T ETHERNET P1 P7 R1 P2 R2 P3 P4 P5 P6 P8 N1 N2 CPU 364 1 2 ETHERNET CPU P4 P1 R x P2 P3 Tx Rx T x Tx Rx Rx P7 P5 P6 Tx R...

Page 6: ... SRTP Driver 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 optional para...

Page 7: ...al server node PLC 1 255 IP_Address IP address of physical server node PLC Must be on the same subnet as the server or gateway Protocol Specify protocol used GE_SRTP SRTP Adapter Specify on which port the device is connected to the FieldServer N1 Example Client Side Nodes Nodes Node_Name Protocol IP_Address Adapter Node_A SRTP 192 168 1 174 N1 4 4 Client Side Map Descriptors 4 4 1 FieldServer Spec...

Page 8: ...Discrete SB Discrete SC Discrete S Discrete S Length Length of Map Descriptor Ensure that the length does not exceed the table length 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 rea...

Page 9: ...iver will store the data The name must correspond to a data array defined in the data array section of the CSV file Read will be performed every 2 0 Seconds RDBC Read Block Continuous The driver will read data from the PLC continuously Map descriptor names may be used in driver error messages It is not essential but it is useful to use unique names Location in the data array at which the first ele...

Page 10: ...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 Scan_Interval node_name Address Length Data_Type Write_AO DA_AO 0 wrbc 5 0s Node1 20 10 AQ Write continuously Write to the AQ Analog Output tabl...

Page 11: ...bits can cross byte boundaries Here we read 2 bits from table T starting at bit 8 This is most useful when writing to the PLC in cases where you want to turn one particular bit on or off Map_Descriptor_Name Data_Array_Name Data_Array_Offset Function Scan_Interval node_name Address Length Data_Type Format Read_DI DA_T 100 rdbc 2 0s PLC 1 8 2 T Bit The format parameter tells the driver to override t...

Page 12: ...SRTP Driver communications the driver independent FieldServer buffers need to be declared 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 pa...

Page 13: ...ur website www fieldserver com E mail support fieldserver com Page 11 5 2 Server Side Connections Section Title Adapter Column Title Function Legal Values Adapter Specify which port the device is connected to the FieldServer N1 Protocol Specify protocol used GE_SRTP SRTP Example Server Side Connections Connections Adapter Protocol N1 SRTP ...

Page 14: ...ocol Specify protocol used SRTP Example Server Side Nodes Nodes Node_Name Node_ID Protocol GE_Srv_11 11 SRTP 5 4 Server Side Map Descriptors 5 4 1 FieldServer Specific Map Descriptor Parameters Column Title Function Legal Values Map_Descriptor_Name Name of this Map Descriptor Up to 32 alphanumeric characters Data_Array_Name Name of Data Array where data is to be stored in the FieldServer One of th...

Page 15: ...te SC Discrete S Discrete S Length Length of Map Descriptor Ensure that the length does not exceed the table length 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 Has no meaning on the server as the driver responds based on the nature of the request The map descriptors sh...

Page 16: ...ssive PLC1 1 1000 R If the client is reading then response data will be obtained from this table If the client array writing then incoming data will be stored in this array Address 1 corresponds to offset zero 1st 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 descri...

Page 17: ...y writing data to a data array A special map descriptor is required The driver recognizes the map descriptor by its name which must be SRTP stats The following example shows how this special map descriptor can be configured Nodes Node_name Protocol null_node SRTP Data_Arrays Data_Array_Name Data_Format Data_Array_Length SRTP_STATS UINT32 600 Map_blocks Map_block_Name Data_Array_Name Node_name Leng...

Page 18: ... RUIdebug utility program Messages marked with a are only printed once and then suppressed to prevent the error log being filled with repetitive messages SRTP 1 FYI The MapDesc called s is too short You have define a map descriptor to expose driver statistics but the length parameter must be at least 500 long Ensure the Data array is this long too Edit the CSV correct he problem and reset the Fiel...

Page 19: ...te an occasional corrupt message There is no corrective action you can take to eliminate this error SRTP 13 Err Cant Process ServiceRQst x h The driver cannot process this service request It can only read write table memory There is no corrective action you can take when this message is printed If you wish take a log file using RUIdebug and contact Fieldserver support The message is followed by a ...

Reviews: