FieldServer FS-8700-67 Russelectric Model 2000

FieldServerFS-8700-67 Russelectric Model 2000Driver Manual(Supplement to the FieldServer Instruction Manual)APPLICABILITY & EFFECTIVITYEffective for all systems manufactured after November 2015Kernel Version:Document Revision:1.041

FS-8700-67 Russelectric Model 2000 ManualContact Information:Thank you for purchasing the FieldServer.Please call us for Technical support of the FieldServer product.Contact Information:Sierra Monitor Corporation1991 Tarob CourtMilpitas, CA 95035Contact number: 1 408 262-6611 1 800 727-4377Email: info@sierramonitor.comWebsite: www.sierramonitor.comContact Information

FS-8700-67 Russelectric Model 2000 ManualTABLE OF CONTENTS1Russelectric model 2000 Description . 42Driver Scope of Supply . 52.1Supplied by Sierra Monitor Corporation for this driver . 5rd2.2Provided by the Supplier of 3 Party Equipment. 52.2.1rdRequired 3 Party Hardware . 53Hardware Connections . 64configuring the fieldserver as a russelectric model 2000 client . 74.1Data Arrays/Descriptors . 74.2Client Side Connection Parameters . 84.3Client Side Node Parameters . 84.4Client Side Map Descriptor Parameters . 94.4.1FieldServer Specific Map Descriptor Parameters . 94.4.2Driver Related Map Descriptor Parameters . 94.4.3Timing Parameters . 94.5Map Descriptor Example. . 105Configuring the FieldServer as a russelectric Model 2000 Server . 115.1Server Side Connection Descriptors . 115.2Server Side Node Descriptors . 125.3Server Side Map Descriptors . 125.3.15.3.25.3.3FieldServer Specific Map Descriptor Parameters . 12Driver Specific Map Descriptor Parameters . 12Map Descriptor Example. . 13LIST OF FIGURESFigure 1 - Generic Connection Diagram .6Table of Contents

FS-8700-67 Russelectric Model 2000 Manual1RUSSELECTRIC MODEL 2000 DESCRIPTIONThe Serial Russelectric Model 2000 driver allows the FieldServer to transfer data to and from devicesover either RS-232 or RS-485 using RTU protocol. The Russelectric Model 2000 drivers implement aModel 2000 Client and a Model 2000 Server. The Client driver can read data from a remote Server andsend write data commands. The Server driver emulates a Model 2000 device and responds to data readand write poll commands.MessagesThe client driver implements the following RTU message or command types: Read Output Table – Used to read the bit values of the discrete outputs on the Model 2000.Read Registers – Used to read the integer values of the Model 2000’s internal registers.Force Single Output – Used to set or clear the bit value of a single discrete output on the Model2000.Preset Single Register – Used to load an integer value into a specific single register of the Model2000.AddressingEvery Model 2000 has a unique address assigned to it. The client driver can send messages to a specificModel 2000 by using the unique address in the message or by using a special broadcast address of value0. Only the following messages can be sent in broadcast by the client (other messages are read datatypes and would cause a communications collision when all Model 2000 devices respond): Force Single OutputPreset Single RegisterAll Model 2000 devices have to receive and process a broadcast message. No device may send aresponse message in reply. Subsequent data read commands by the client driver will update the datathat was changed or loaded by a broadcast messagePage 4 of 13

FS-8700-67 Russelectric Model 2000 Manual22.1DRIVER SCOPE OF SUPPLYSupplied by Sierra Monitor Corporation for this driverSierra Monitor Corporation PART #FS-8917-02FS-8700-672.2DescriptionRJ45 to DB9F connector adapterDriver ManualProvided by the Supplier of 3 rd Party Equipment2.2.1 Required 3 rd Party HardwareThe user has to provide a suitable cable with appropriate connectors that will connect the Model 2000either directly to the FieldServer or to the RS-232 to RS-485 converter. When connecting to a converter,consult the converter’s documentation for pinouts.Page 5 of 13

FS-8700-67 Russelectric Model 2000 Manual3HARDWARE CONNECTIONSThe FieldServer is connected to the Model 2000 as shown below.Configure the Model 2000 according to manufacturer’s instructions.Direct RS-485 Connection WiringR1 or R2TXATXB3 RXA4 RXB5 GND -Note: A B -TX2RXRX3TXGND5GNDRefer to converterspec for pinnumbers onconverters.RusselectricModel 2000232 - 485ConnectorNOTE: Only connect RS-232 OR RS-385. Bothshown for illustration purposes only.ORRS-232TX12 -RS-485RXFS RS-232 to converter wiringJ7 connector(408)-262-2299FIELDSERVERRusselectric Model 2000CONNECTION DIAGRAMBASE NAME:FILE NAME:Figure 1 - Generic Connection DiagramPage 6 of 13DATE: 12/01/03BY:MF

FS-8700-67 Russelectric Model 2000 Manual4CONFIGURING THE FIELDSERVER AS A RUSSELECTRIC MODEL 2000CLIENTFor a detailed discussion on FieldServer configuration, please refer to the FieldServer ConfigurationManual. The information that follows describes how to expand upon the factory defaults provided in theconfiguration files included with the FieldServer (See “.csv” sample files provided with the FieldServer).This section documents and describes the parameters necessary for configuring the FieldServer tocommunicate with a Russelectric Model 2000 Server.4.1Data Arrays/DescriptorsSection TitleData ArraysColumn TitleFunctionData Array NameProvide name for Data ArrayData Array FormatProvide data format. Each Data Array can onlytake on one format.Data Array LengthNumber of Data Objects. Must be larger thanthe data storage area required by the MapDescriptors for the data being placed in thisarray.Example//Data ArryasData ArraysData Array NameRTU RegistersRTU Digital Out, Data Format, Uint16, Bit, Data Array Length, 79, 34Page 7 of 13Legal ValuesUpto15alphanumericcharactersFloat, Bit, Uint16, Sint16,Backed Bit,Byte,Packed byte, Swapped Byte1-10, 000

FS-8700-67 Russelectric Model 2000 Manual4.2Client Side Connection ParametersSection TitleConnectionsColumn TitleProtocolFunctionSpecify which port the deviceis connected to the FieldServerSpecify protocol usedBaud*Specify baud rateParity*Data Bits*Stop Bits*Poll Delay*Specify paritySpecify data bitsSpecify stop bitsTime between internal pollsPortLegal Values1P1-P8, R1-R2Rus, RussElectric, Model 2000110-115200 Standard baud rates only (set to same value asused on Model 2000)Even, Odd, None, Mark, Space (Refer to Model 2000 set up)810.5 secondsExample//Client Side ConnectionsConnectionsPort , ProtocolP1, Rus4.3, Baud, 9600, Parity, None, Poll Delay, 1.0 sClient Side Node ParametersSection TitleNodesColumn TitleNode NameFunctionProvide name for NodeNode IDModel 2000 station addressProtocolSpecify Protocol usedSpecify through which port the device is connectedto the FieldServerPortLegal ValuesUp to 32 alphanumeric characters0-247 (Node 0 used exclusivelybroadcast)Rusto2P1-P8, R1-R2Example//Client Side NodesNodesNode NameNode 1, Node ID,,1, Protocol, Rus, Port, P11 Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction manual for details of the portsavailable on specific hardware.2 Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction manual for details of the portsavailable on specific hardware.Page 8 of 13

FS-8700-67 Russelectric Model 2000 Manual4.4Client Side Map Descriptor Parameters4.4.1 FieldServer Specific Map Descriptor ParametersColumn TitleMap Descriptor NameData Array NameFunctionName of this Map DescriptorName of Data Array where data is tobe stored in the FieldServerData Array OffsetStarting location in Data ArrayFunctionFunction of Client Map DescriptorLegal ValuesUp to 32 alphanumeric charactersOne of the Data Array names fromData Array section above.0 to maximum as specified in DataArray sectionRdbc, Wrbc, Wrbx4.4.2 Driver Related Map Descriptor ParametersColumn TitleFunctionNode NameName of Node to fetch data fromData TypeUsed to indicate access to the Model2000 Registers or Points (flags)LengthThe number of registers or pointsAddressThe starting register or point numberLegal ValuesOne of the node names specified in ClientNode Descriptor above. Node 0 can beused to broadcast a command. Only writefunctions can be used with Node 0RegisterFlagFor write functions, length defaults to 1.Length must be less than or equal to themaximum number of points or registersavailable. See your hardware manual fordetails1-10,0001-10,0004.4.3 Timing ParametersColumn TitleScan IntervalFunctionRate at which data is polledLegal Values 0.5 sPage 9 of 13

FS-8700-67 Russelectric Model 2000 Manual4.5Map Descriptor Example.Map Descriptor NameRUS MBA1This can be any namebut each name mustbe unique. Name willappear in FieldServerMap Descriptor statusinformation screens., Scan Interval, 3.0s, Data Array Name, RTU Digital Out, Data Array Offset,0, Node Name, Node 1The function may be read forread commands and write forwrite type commands.Continuous operations areallowed.This value specifies theoffset into the data array(RTU Digital Out) wherethe data fetched must bestored.Scan interval must be adapted for multipleMap Descriptor scans to prevent a situationwhere not all Map Descriptors can beexecuted in a certain time. Take remotedevice response time into consideration here., Function, RdbcThe data array name must be one found underData Arrays. Data from the scan will be storedinto the array at Data Array Offset.Page 10 of 13, Data Type, Flag, Address,1, Length, 34Use Register to accessModel 2000 registers orFlag to access the outputtableNode name must be one foundunder Nodes, Node name. Datawill be fetched from this node andport during a scan. Use Node 0with id of 0 to execute a broadcastcommand.

FS-8700-67 Russelectric Model 2000 Manual5CONFIGURING THE FIELDSERVER AS A RUSSELECTRIC MODEL 2000SERVERFor a detailed discussion on FieldServer configuration, please refer to the FieldServer ConfigurationManual. The information that follows describes how to expand upon the factory defaults provided in theconfiguration files included with the FieldServer (See “.csv” sample files provided with the FieldServer).This section documents and describes the parameters necessary for configuring the FieldServer tocommunicate with a Russelectric Model 2000 ClientThe configuration file tells the FieldServer about its interfaces, and the routing of data required. In order toenable the FieldServer for Russelectric Model 2000 communications, the driver independent FieldServerbuffers need to be declared in the “Data Arrays” section, the FieldServer virtual node(s) needs to bedeclared in the “Server Side Nodes” section, and the data to be provided to the clients needs to bemapped 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.1Server Side Connection DescriptorsSection TitleConnectionsColumn TitlePortProtocolBaud*Parity*FunctionSpecify which port the device isconnected to the FieldServerSpecify protocol usedSpecify baud rateSpecify parityData Bits*Stop Bits*Handshaking*Specify data bitsSpecify stop bitsSpecify hardware handshakingLegal ValuesP1-P8, R1-R23Rus110 – 115200, standard baudEven,Odd, (setNone,rates onlyto Mark,same Spacevalue(referto onModel2000setup)as usedModel2000)81NoneExample//Server Side ConnectionsConnectionsPort, Baud, Parity, ProtocolP1, 9600, None, Rus3Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction manual for details of the portsavailable on specific hardware.Page 11 of 13