Home

FieldServer Configuration Manual

1. FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 12 of 90 JS 5 5 55 5 S S 59 s 5 55 8s 5 52s9 Es Ss8 2 S if i TM EG SIS Oa TCT Settings for how the FieldServer communicates with Client Nodes de Connections The protocol for the network connected to this port Adapter Protocol N1 Modbus TCP Adapter definition applies to defining network and FieldServer e g Profibus connections 11 Server Side Nodes Nodes Node Name Node_ID _ Protocol MBP Srv 11 11 Modbus TCP Since the FieldServer is a Server here this is the ID of the FieldServer virtual Node The FieldServer can represent multiple Virtual Node ID s in most protocols A Node name for reference by the Map Descriptors Server Side Map Descriptors Map_Descriptors Map Descriptor Name _ Data_Array_Name_ Data Array Offset Function Node Name Address_ Length SMD DI 01 DA DI 01 0 Passive MBP_Srv_11 10001 200 SMD_DO_01 DA DO 01 0 Passive MBP_Srv_11 00001 200 FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Config
2. Inter character timeout 500 ms SCADA hold 2000 ms 2 sec Data cache age limit for acceptable data 20000 ms 20 sec Cache 80 Retry Interval 10000 ms 10 sec Recovery Interval 30000 ms 30 sec Probation Delay 60000 ms 1 min Scan Interval 1 second Poll Delay 50 ms Retries 3 Activity Timer 120000 ms 2 hour Parity None Baud 9600 Data Bits 8 Stop Bits 1 Handshake Timeout 2000 ms 2 sec FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 74 of 90 Appendix B 3 Available Data Types for Data Arrays To facilitate the choice of data type each of the data types available are described below Data Format Description Float Format used to store Floating Point Analog values e g temperature volts Each point oa in the array represents one 32 bit Floating Point value Bit Format for storing Binary Data Each point in the array represents one bit Byte Format for storing Bytes of data Each point in the Array represents one Byte SInt16 Signed 16 bit mu irit Range 32768 to 32767 discrete Each point in the array represents one integer nteger Uint16 Unsigned 16 EE a Range 0 to 65 535 discrete Each poin
3. Data_Array_Length Buffer_Length Number of Data Objects 0 10000 Data_Array_Function Special function for the Data Array Refer to table in Appendix B 4 3 None DA_Function_After_Store If this parameter is specified when a value different to the current value is written to the Data Array it will be stored in the FieldServer s Non Volatile Memory On start up this value is loaded from the Non Volatile Memory into the Data Array This value is only stored 3 times a minute so if more writes than that are done the values will be stored in the Data Array but not to the Non Volatile Memory Storing this value has performance impacts so care must be taken to store this value only if needed Refer to Section 0 Non Volatile FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 76 of 90 Appendix B 4 3 Data Array Function The Data Array Function Keyword is used in the configuration file to get Data Array specific error conditions and statistics The available keywords are listed below Keyword Description Node Online Bits Node Error Bits Bit O is unused Every bit corresponds to the Node with that number up to 255 E g Bit 3 corresponds to Node 3 etc Refer to Section 6 1 4 Cable Sta
4. The Rdbc function also has the ability to perform what is known as write throughs If the driver allows writing to the point related to the Map Descriptor where Rdbc is specified then the Rdbc function will write the data in the Data Array back to the point when an update in the associated Data Array is detected This makes Rdbc the ideal function for read write points 4 3 2 Active Read Continuous with Sequencing Arcs This function will perform the same operation as an Rdbc Arc function but will sequence through the range of addresses starting at Address and wrapping at Address Length A length of 1 will be used for every one of the Addresses that gets polled The following drivers currently support the ARCS function e Modbus RTU e Lutron Machine e BACnet MS TP BACnet Arcnet BACnet e Metasys N2 4 3 3 Write Block on Change Wrbx The Wrbx function will write data from the Data Array to the remote device The write is triggered by a change in the associated Data Array If the associated Data Array is updated a write will occur even if the value s within the Data Array have not changed The Scan_Interval parameter is not required for this function as writes are event driven and not continuous 4 3 4 Write Block Continuous Wrbc This is similar to the Wrbx function except that the writes occur at a regular interval rather than on an event driven basis The frequency of the writes is determined by the Scan_I
5. 0 001 0 001 FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 60 of 90 10 HOT STANDBY 10 1 Terminology Term Description Active FieldServer The FieldServer actively polling the field Nodes Standby FieldServer A FieldServer which is running but is not polling field Nodes nor responding to Client polls It will assume active status if the Active FieldServer fails to issue a heartbeat in the designated time frame Failover Timeout The time interval between the Active FieldServer failing and the Standby FieldServer preparing to become the Active FieldServer Transfer Interval The total time interval between the Active FieldServer failing and the Standby FieldServer actually resuming communications as the Active FieldServer Status Data Array Primar 7 The FieldServer designated to be the Active FieldServer on system startup FieldServer Secondary The FieldServer designated to be the Standby FieldServer on system startup FieldServer Commbit Data Bit Data Array that shows all the online Nodes one bit per Node address Practical limit is Array 255 Nodes the offset corresponds to the Node ID bad Int Data Array that shows all the status of all Nodes one integer per No
6. Data Array Offset Function Node Name Address Length Scan Interval Keepalive CO1 DA Keepalive 0 Rdbc TA 01 40001 zd 60s Keepalive CO2 DA Keepalive it Rdbc TB_02 40001 pdb 60s Keepalive C03 DA Keepalive ve Rdbc 1C_03 40001 5 di 60s Keepalive CO6 DA Keepalive 5 Rdbc TEG_S_ 06 40001 5 di 60s FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 67 of 90 10 3 6 Server Name NOTE The Client Node Descriptors used to have to have CONFIG CSV file entries that describe the adapter and IP address of the AC2PA connection and backup connection this is no longer required the Client Node Descriptor now only needs to be given the Server Name of the source of the data The Server names are configured in the HSB P INI and HSB S INI files for each physical FieldServer 10 3 7 Application example using Hot Standby Mode 2 Consider the application in Figure XV where the highest redundancy level possible is required The application has a mixture of Single and Dual port Servers and Dual Redundant Clients Physical Physical FieldServer 1 FieldServer 2 primary primary A tussi mms EE E Mar EE lt u Virtual Bridge on Tier 2 Ig PEX Tier e PEX Tier NR EH FER 0 NL EE L ee TTTT TTT TTTTTTTTTTTTTTTTTTTT
7. Source DA Uint16 200 Target DA Bit 200 Moves Function Source Data Array Source Offset Target Data Array Target Offset Length Bit Extract Source DA pes Target_DA 0 48 5 2 5 Example 2 Simple Bit Packing In this example 12 bits are packed into the 3rd and 4th register of the target byte array starting at the eleventh bit in the source array Note that the second target register will only be half populated leaving the last 4 bits empty Data Arrays Source DA Target DA Data Array Name Data Format Data Array Length Bit 200 Byte 200 FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 26 of 90 Moves Function Source Data Array Source Offset Target Data Array Target Offset Length Bit Pack Source_DA 10 Target DA 12 12 5 2 6 Example 3 Extracting bit groups The following example extracts 3 bits from the second byte of a 32 bit register and places them into a byte register on their own The Bit Offset keyword is used here to achieve this Data Arrays Data Array Name Data Format Data Array Length Source DA Uint32 200 Target DA Byte 200 Moves Function Source Data Array Source Offset Bit Offset Target Data Array Target
8. Target_Offset Length Move Only Source DA 0 larget DA 40 75 Five Floating point values are moved from the first offset of Source DA to Offset 40 of Target DA 5 1 1 2 Special Application Grouping Data The location of data in Data Arrays on the FieldServer is determined by corresponding Map Descriptors Should a Client poll the FieldServer for data spanning more than one Map Descriptor the FieldServer will not know which Map Descriptor to use This can be circumvented by moving data from multiple Client Side Source Data Arrays to a single Server Side Target Data Array This Data Array should be larger of greater length than the maximum poll length of the Client One Server Data Array means One Server Map Descriptor is possible Example Consider a Modbus Client needing registers 40001 through 40050 from the FieldServer The poll lengths used to obtain this data are unknown This could be configured in the FieldServer Server side as follows Configuration 1 Map Descriptor 1 serves up 40001 Length 25 Map Descriptor 2 serves up 40026 Length 25 FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 22 of 90 Configuration 2 Configuration 3 If the two poll blocks fall within these two address spans the
9. Figure Client Server FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 8 of 90 2 OVERALL OPERATION PHILOSOPHY The FieldServer functions as a bridge between two or more different Nodes see Figure II The information is gathered by the Client side of the FieldServer from the Server Nodes via a Serial Port Ethernet port or plug in card Nodes may use different protocols and even different communication busses The Client Node Descriptors contain information about each Node including connection ports and protocol Each Node is given a Node_Name and a Node_ID The data from a Server Node is stored on the FieldServer in a Data Array The exact location as well as the format of the information is determined by the Map Descriptors The FieldServer can contain any number of Data Arrays but each Data Array can only store data in one format The Client Map Descriptors describe where the information is to be stored on the FieldServer and the Server Map Descriptors describe how this information is able to be accessed by a Client Node On the Server side of the FieldServer virtual Nodes are created to convert the information stored in the Data Arrays to the format required by the Client Node These Nodes can be accessed by any of the available ports on the FieldServer a
10. Grouping Data cccccnonocoonnoncnonononannnnnnnnnonononnnnncnnonnnnonnnnnnncnnnnnonnnnnnnccnnnnnnnnnos 21 5 1 1 3 Special Application Separating Responsible Map Descriptors ooooccccconcooononccnncnonnonnnncnnccnonannnonos 22 5 1 1 4 Special Application Creating a LonWorks SNVT Switch from 2 Modbus registers 22 5 2 Function Moves Type Casting ccccececececececececececeeeeececeeeeeeeeeceeeeeeeeeeeeeeeeeee cece cece eene ener ener eere ener eren een 23 5 2 1 Functions Available For Type Casting esses eese eene nnne nh nnne nnns enata asa ss sse s asa ada n sss sana aa 23 5 2 2 Converting two Integers to a Float 5 2 3 Using Moves to pack and unpack bits to or from a Register 5 2 4 Example 1 Simple BI EXACT Mii e hA SE obs Ea e ELE XR CERTA ERR PR ATIS aa LIRA RR 5 2 5 Example 2 Simple Bit Packing ita neret era gene etn t eaae Ra ea ehe hekin eee peek e deg ae edu 5 2 6 Example 3 Extracting bit groups 5 2 7 Bit Extraction Application Example 5 2 7 1 Bit Extraction Example Configuration esperese e earn aaee e aaeeei ae eba Eara pA errana 27 5 2 8 Task MOVES ii EEA A a e E AA 5 2 8 1 Special Application Node Status 5 2 9 Match pattern essen FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer
11. Protocol RTU Srv 11 11 Modbus RTU Map Descriptors Map Descriptor Name Data Array Name Data Array Offset Function Node Name Address Length SMD DO1 DA DO 01 0 Passive RTU Srv 11 00001 1 ignore FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 71 of 90 Set up the Modbus Client side Connections Port P2 Nodes Node Name Node_ID Protocol Port DEV11 ni Modbus RTU P2 Map Descriptors Map Descriptor Name Data Array Name Data Array Offset Function Node Name Address Length SMB BO1 DA DO 01 0 Rdbc DEV11 AT fll process Appendix A 2 2 Disabling a Node Nodes Node Name Node_ID Protocol Port DEV11 y ddl Modbus RTU P2 ignore DEV12 puo Modbus RTU P2 process FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 72 of 90 Appendix A 3 Disabling Statistics Display For large configurations with many Map Descriptors there is a possibility that the FieldServer will run out out memory before the entire configuration file is loaded In order to conserve memory it is possible to disable the collection
12. Up to and including FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 87 of 90 Error Description Action 11001 Lutron driver Data Array length for Area names too small 11002 Lutron driver Data Array length for Scene names too small 11003 Lutron driver Data Array length for Zone names too small Increase Data Array Length in CSV file 11004 Envirotronics SystemsPlus driver The name entered in the SysPlus Cmd mapdesc field is not recognized or was not entered at all This field must be filled in with a valid SysPlus Cmd 11005 Envirotronics SystemsPlus driver The name entered in the SysPlus Data Type mapdesc field is not recognized or was not entered at all This SysPlus Data Type field must be filled in with a valid 11006 Envirotronics SystemsPlus driver The name the mapdesc field is not valid or was not entered entered in Store Data Array Name at all 11007 Envirotronics SystemsPlus driver The name the mapdesc field is not valid or was not entered entered in Par Data Array Name at all 11008 Envirotronics SystemsPlus driver The name entered in the SysPlus Alarm Name mapdesc field is not valid or was not entered at all This field mu
13. the SCADA virtual FieldServer will automatically get the data from the FieldServer 2 PEX virtual FieldServer 9 The thick lines represent all possible logical connections from FieldServer 1 PEX Tier virtual FieldServer to the other FieldServers that it can communicate with The solid lines are the default connections and the dotted lines are the backup connections that are only used if there is a failure 10 If the Data Array name contains the string nocop then its data will not be copied to the standby FieldServer 10 3 8 Configuring the FieldServer for Hot Standby Mode 2 10 3 8 1 Hot Standby Status Function Hot Standby Status Function provides the status of the FieldServers The offset number and the value in the Data Array are as follows Data Array Offset Value Description 0 1 Primary OK 1 1 Secondary OK 2 1 Primary is active 3 1 Secondary is active 4 1 Hot standby system failure 5 X Number of times primary has become active 6 X Number of times secondary has become active 23 1 Hot standby hubs not on independent networks 24 1 Somewhere a backup connection used Example Data Arrays Data Array Name Data Format Data Array Length Data Array Function DA HS Status UINT16 32 Hot Standby Status Array FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888
14. will store two characters from the string in each Data Array element Data Arrays Data Array Name Data Format Data Array Length DA 1 FLOAT 20 Preloads Data Array Name Preload Data Value Preload Data Format Preload Data Index DA 1 Revision 123aA STRING 74 The string Revision 123aA is stored starting in the 2nd element index 1 of the Data Array named DA 1 FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 42 of 90 5 6 9 Example 6 Load a Value Strings 2 Data Arrays Data Array Name Data Format Data Array Length DA 1 Uint32 20 Preloads Data Array Name Preload Data Value Preload Data Format Preload Data Index DA 1 ABCD String 0 The value found in the 1st element of the Data Array will be 0x4241 Ascii value of A and the value found in the 2nd element will be 0x4443 Ascii value of B A UINT32 Data Array can store 2 characters per element 5 6 10 Example 7 Load a value Casting Data Arrays Data Array Name Data Format Data Array Length Both Data Arrays are DA 1 FLOAT 20 formatted as FLOAT and are DA 2 FLOAT therefore capable of storing the value 257 Preloads Data Array Name Preload Data Value Preload_Da
15. 509 1970 email support fieldserver com FieldServer Configuration Manual Page 69 of 90 10 3 8 2 Cable Status Function Cable Status Function provides the cable status between the FieldServer and the Nodes If the cable is good it is indicated by a 1 in the Cable Status Data Array The offset number in the Data Array is as follows Data Array Offset Description Data Array Offset Description 0 P1 on Primary Serial 16 P1 on Secondary Serial 1 P2 on Primary Serial 17 P2 on Secondary Serial 2 P3 on Primary Serial 18 P3 on Secondary Serial 3 P4 on Primary Serial 19 P4 on Secondary Serial 4 P5 on Primary Serial 20 P5 on Secondary Serial 5 P6 on Primary Serial 21 P6 on Secondary Serial 6 P7 on Primary Serial 22 P7 on Secondary Serial 7 P8 on Primary Serial 23 P8 on Secondary Serial 8 R1 on Primary RS485 24 R1 on Primary RS485 9 R2 on Primary RS485 25 R2 on Primary RS485 12 N1 on Primary Ethernet 28 N1 on Primary Ethernet 13 N2 on Primary Ethernet 29 N2 on Primary Ethernet Example Data Arrays Data Array Name Data Format Data Array Length Data Array Function DA Cable Status Bit 32 Cable Status Bits The Cable Status bits take 60s for the change in status to be asserted as the system retries a few times when testing the connection This 60 second delay is a h
16. Array to another The function parameter within moves allows data manipulation to occur while moving the data e g Logic operation Integer to floating point conversion etc Scaling Logic and Math are also possible while moving data With the exception of Conditional Moves see 5 2 9 each Data Array location may only act as the target location of one Responsible Move This ensures that the data source can be uniquely determined in order to establish source data validity and so that a write through the target data location is directed to the appropriate location Moves will execute whenever the source data changes or the scan interval if specified expires If a task name but no scan interval is defined a default scan interval of 1s is assumed A Move operation must specify the following elements Source Data Array The name of the Data Array from which data is to be copied Source Offset The offset within the Data Array from which data is to be copied Target Data Array The name of the Data Array to which data is to be copied Target Offset The offset within the Data Array to which data is to be copied The following elements are optional eae The number of consecutive source Data Array values to be moved to consecutive en E target locations starting at the respective offsets TIN If a task name is specified the move operation becomes a continuous task on the ask_Name FieldServer that is executed at the scan int
17. Configuration Manual Table of Contents 5 2 9 1 Table of Patterns Configuration example cccccccccsesssecececeesessscececececsesesseseeececsesesaeseeeesseesseaees 5 2 9 2 Moves DeflnitiOn sioe e oe HE RUE beri l deiude e RUE bed vn hd YE ede XR tS 5 2 9 3 Table String Composition 5 2 10 Conditional Moves xiu se rid ed era Cod outa ea id beo baud de o Pe a Lad adi ii ended 5 2 10 1 Conditional Moves Example T erinrar onran pAn A EEEO IRR ERE SNIPA AENEIS 5 2 10 2 Conditional MovesExample Zi eara a r E E a aE aai EE EE ERES 5 3 Mathematical f rictions OT 5 3 1 Math Function as a Moves Function esee eines entnns estan sten tans s etas naar rr sn assets 5 3 2 Standalone Maths svete aun dina ud ni ie a I HIR 5 3 3 MiGth Usage Example acea editae ded datei ede EA a id di 5 3 4 Optional Parameteks eei e m t rete eene do ees eere bes o tee duo 33 eh aae P eda o apt baee tel Tee a PURA URS 5 3 4 1 Truncate Result Example 5 4 LOB IGS Sues cies cote Gute Vets cota Hed bete dots ca tues aede a Gu Oo bende deus ees sues deae Sue NA aede ouo du ea aee de dex tetas 5 4 1 Logicas d Moves Function ics daa tens dina HAYA TRE ERE Ta Ted 5 4 2 StGNGQIONC LA M A 5 6 Preloading Data Arrays with Initial Values 5 6 1 INTFOGUCTION sS 5 6 2 Parameters used to define Preloads cccsessssscecccessessesscececeseessessceseesseesasecesecsseeeasecesecsseessaseseseesseeses 5 6 3 Limitations and Operational Cons
18. FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 84 of 90 Error Description Action 10049 Could not find Client Data Array for Move 10050 Could not find Server Data Array for Move 10051 Could not find Feedback Data Array for Move 10052 Could not find Mode Data Array for Move 10053 Data Array already has a responsible move Setpoint Moves are only allowed to be 1 item 10054 in length A move was defined and a write occurred to 10055 the target Data Array but cannot transfer to the Source Data Array because no Responsible Active Map Descriptor is defined A move was defined and a write occurred to the target Data Array but cannot transfer to 10056 the Source Data Array because the Node associated with the Responsible Active Map Descriptor is offline 8051bp03 or CB8MENU found SMCTOP INI and 10058 FS_TCP INI files so it will delete FS_TCP INI and use SMCTCP INI in future Obtain latest RUIBOOT or use manual method of 10059 Old version of RUIBOOT EXE being used AN setting IP address see Utilities manual 10070 Illegal Node ID 10071 Map Descriptor length of 0 is not allowed 10072 Map Descriptor length too large 10073 Illegal Data T
19. Node Parameters eenn ee era cas oe ete NA 6 3 1 Node Offline Action a aar a e aa a aa aa a nnn nennen aa kane sees sata asas esses sata dadas sss essa sa dada assa essa aaa 47 7 Dynamic Parameters eco e eite Aree eE ex A RN Te E NR VENERE NE ASERNE ERESSE Se 48 7 1 1 Dynamic allocation of Node ID or Station number sisse eene th anas sse a aa 48 7 1 1 1 Diagram 1 Static Server Side Node ID enne nnne nn nnne esent nnns 48 FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Table of Contents 7 1 1 2 Remote Client finds a Node with Node ID dependent on the data read from the remote Server device 49 7 1 2 Map Descriptor Parameters specific to Dynamic Parameters 7 1 3 Examples etis d eee ea repa dde e de aea du dented Feo ba deus es Ae RET a a EE lave eo ed REA ed TE ED LAUS Ta eed 7 1 3 1 Example 1 Dynamic Allocation of Node ID cccccnonococccnnononononoonnnncnnonnnnnnnonnnncononnnnnonnnnccninnnnnnnos 7 1 3 2 Example 2 Dynamic Allocation of System Node ID esee enne 7 1 3 3 Example 3 Dynamic allocation of the BACnet MAC address sess 51 7 1 4 Error Messages s ct d tae OTE EE I Pao d ge Renan daa eR e e PW Pd Te Ded Fe E Eine 52 8 Port Expander Mod PEX Mode cce e
20. Offset Length Bit Move Source DA 0 8 Target_DA 0 no 5 2 7 Bit Extraction Application Example Assume a Liebert device has been set up as follows A single packed bit integer with a value of 1034 signifies a blown rectifier fuse a hardware shutdown and a battery discharge sum of the values for the corresponding events The value 1034 has no meaning as such but when the integer is unpacked the individual data bits communicate the required information This is depicted in the following diagram FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 27 of 90 15 2 7 1 Bit Extraction Example Configuration Example of Bit Extraction Data Arrays Data Array Name Data Format Data Array Length Source DA Uint16 200 Target_DA Bit 200 Map Descriptors Map Descriptor Name Data Array Name Data Array Offset Node Name Function Address_ Length CMD PI AlarmO1 01 Source DA 0 UPS 01 Rdbc 40289 xl Moves Function Source Data Array Source Offset Target Data Array Target Offset Length Bit Extract Source DA 0 Target_DA 0 10 Target DA offsets O to 9 now contain the first 10 bits of Register 40289 These can now be served as bits to the Protocol o
21. The Node parameter Write Ack Option needs to be configured Refer to Appendix B 4 10 Metasys is a registered trademark of Johnson Controls Inc This setting only affects writes to points not configured existing as read cache Map Descriptors Writes to existing points on the FieldServer are acknowledged immediately FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 54 of 90 8 5 Handling of Successive Writes to the Same Point When multiple successive port expansion writes to the same point occur there is a potential build up of pending write transactions in the FieldServer since the Server side may receive write transactions at a faster speed than they are completed on the Client side depending on the speeds of the respective protocols There are two fundamental ways of dealing with the potential accumulation of successive writes to the same point e Overwrite any pending write values that have not yet been sent to the Server are overwritten with the latest write value This is the default option and it ensures that the last value that was received from the Client is written to the Server Intervening writes may be lost e Blocking if it is important to preserve the sequence of write values to the same point e g a switching sequence of o
22. There will be a line System Hot Standby ETH This FieldServer now ACTIVE Test the Hot Standby Configuration by disconnecting the power from the Primary FieldServer The secondary FieldServer s Activ LED should show solid Yellow and the Error screen should show an ACTIVE message as above Reconnecting the power to the Primary FieldServer and disconnecting the power to the Secondary FieldServer should reinstate the original behavior of the FieldServer Refer to the Utilities manual for information on file downloading FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual 10 3 Hot Standby Mode 2 Dual Redundant Mode In this mode both the Primary and the Secondary system are continuously active and the Data Arrays of both systems are continually updated Each system keeps an image of what is happening in its complementary system Figure XII shows how the dual image allows for multiple data paths which in turn provide a high level of data redundancy Hot Standby Mode 2 is intended for more complex applications where requirements are more stringent Consequently configuration is more complex Physical Hot Standby FieldServer 1 with two Virtual FieldServers Information Client J RS 232 Data Transfers Internal Data Transfe
23. Write data buffer once Wrbx Write data buffer on change One of the Node names specifies in Node Name Name of Node to fetch Data from Client Node Descriptor above Data Type Type Data Type in PLC File Type File Type in PLC Block Number DB File Number Block Number in PLC See Driver Manual for validity and applicability Data Array Low Scale Buffer Low Scale Scaling zero in Data Array Any signed 32 bit integer in the range 2 147 483 647 to 2 147 483 647 0 Data Array High Scale Buffer High Scale Scaling max in Data Array Any signed 32 bit integer in the range 2 147 483 647 to 2 147 483 647 100 Node Low Scale Scaling zero in Connected Node Any signed 32 bit integer in the range 2 147 483 647 to 2 147 483 647 0 Node High Scale Scaling max in Connected Node Any signed 32 bit integer in the range 2 147 483 647 to 2 147 483 647 100 FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Section Title Map Descriptors Page 81 of 90 Column Title Function Legal Values Readback Option This Client Side parameter enables the user to configure the timing of a read after a write The Readback operation will apply to all drivers that s
24. any token if the value for that token is unimportant 2550 is negative two negative signs one is considered as delimiter FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 31 of 90 5 2 10 Conditional Moves A move can be defined so that it is executed conditionally based on the status of a bit in a predefined Data Array location conditional Data Array A useful feature of the conditional move is that data is able to be moved to the same target offset as defined by another conditional move The user is thus able to move data from different sources into the same target based on the status of a bit in a Data Array The conditional bit can be placed in any Data Array and can also be in the source or destination Data Array It simply needs to be declared in the Move instruction parameters A conditional move needs to be scheduled by the kernel for processing and therefore requires a task name and scan interval The Parameters for a Conditional move are as follows Conditional Move Parameters Source Data Array The name of the Data Array from which data is to be copied Source Offset The offset within the Data Array from which data is to be copied Target Data Array The name of the Data Array to which data is to be copied Target Offset
25. caching capability insures that data from Server devices is immediately available to the Client devices when needed Data can be cached from slower devices or remote units for immediate access by the Client device See Section 8 for details The Hot Standby option for the FieldServer is available when dual redundancy is required See section 10 for details 1 2 Application Today s plants are integrated intelligent facilities requiring multiple mechanical and electrical systems to be controlled from a central processor Many of these devices are not part of the central automation system but that system still needs data input from these devices Through its powerful protocol conversion capability the FieldServer allows system designers and managers to connect unique instrumentation and sensor devices onto common protocol systems and into the plant Ethernet backbone Due to its internal poll block caching multiple protocol capability and high port count the FieldServer improves data and machine update time compared to conventional HMI packages using multiple drivers and port expanders The FieldServer is designed to enable devices within a facility to communicate with each other or to a central control station via Serial Arcnet Ethernet or other communication busses Two way communication is easily available between the various process and control systems 13 Terminology 1 3 1 Nodes The devices communicating with the FieldServer may
26. enis einn an nr nano nr nrnnnn non senses tanen enn 62 10 2 2 Configuring the FieldServer for Hot Standby Mode 1 esses eise nennen estne 62 10 3 Hot Standby Mode 2 Dual Redundant Mode enne nennen nennen enne enne nennen 63 TOBE cSingle Port SerVGEs s I T exte iade ee deo ate de era P POR Ad Ed e Uds adve de ERR da due 64 10 3 2 Duadl POrt SetVer ues t RR RR RE DE ERT UR HAT REET CERT e NU EU 64 10 3 3 Tiers SCADA A AAA E ardeat ed don ead deed oth qua haie sed ead o gua aguda 10 3 4 RUINET functions for Hot Standby Mode 2 10 3 5 Keepalive Map Descriptors asocia 10 3 6 Server Name sepe A ti 10 3 7 Application example using Hot Standby Mode 2 sisse esses nnne eniin annee tira dans 10 3 8 Configuring the FieldServer for Hot Standby Mode 2 10 3 8 1 HotStandby Stat s F nctiOh nii eo EXP es eR RHET eee ee ye deest 10 3 8 2 Cable Status F nctiOn ioo iere erede E ne Re RR eee de aee da ERA RENNES Ra Fede E ves Rue bare te Appendix A Useful Features p orse 70 Appendix A 1 Using COMMENTS 3 c re ere eren d xk Or eB teo n E eU SH kd Pe ee EXER ES 70 Appendix A 2 Using conditional process statements ccccconocooncnnononononannnnnonnnnnnnnononnnncnnnnnnnnnnnncnnnnnnnnnnnnncnnnnnennnnos 70 Appendix A 2 1 Disabling the Client side of a configuration AppendbcA 2 2 Disabling d N Od ions tette ee d dr e a e e eno RE NR ERE ee e eR Re
27. file CONFIG CSV for any driver combination ordered is loaded into the FieldServer and can be retrieved using the Remote User Interface Utility see the FieldServer Utilities Manual for more details Use this file as a template when editing configuration files to ensure that the edited file takes the correct form A detailed explanation of the configuration file follows 3 2 Configuration File Structure Lines beginning are comments and do not affect the configuration Delivery csv Note Comments should be at the start of SMC Customer RONDE lines If comments made after a line of Ultimate Destination Main Office parameters must not follow a comma SMC Sales Order 00103400 directly Driver Configuration Modbus RTU Configured By GFM Date 23 Mar 00 Relevant Project information Copyright c 2000 FieldServer Technologies 1991 Tarob Court Milpitas CA 95035 408 262 6611 Fax 408 262 9042 support fieldServer com This section allows for the determination of parameters not directly related to any of the connections Common Information Bridge Title This title appears on the top line of the RUI screen It may be used to indicate the configuration version loaded and the relevant customer project Data_Arrays Data Array Name Data Format Data_Array_Length DA Al 01 UInt16 200 DA AO 01 UInt16 200 DA DI 01 Bit 200 DA
28. gen dae Appendix A 3 Disabling Statistics Display Appendix B Reference cid ia Hee SE E YR EER E HANE E Ne ROTE ee UHR EN ERES Aa 73 Appendix B 1 Working with the Driver Manuals c cccccccccsesssececccecsessscesececeeseceeaeseeececseseeaeseesceseeeaeseeeesseeeaaes 73 Appendix B 1 1 Introduction FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Table of Contents Appendix B 1 2 Driver Manuals as Part of the Documentation Set 73 Appendix B 2 Default settings for parameters ccceccccccccecssssscececececseseeesececeeseeeaesececesseseaaeseeseeseeseeaeseeseseseeaaeas Appendix B 3 Available Data Types for Data Arrays Appendix B 4 Permissible Values for Configuration File Variables Appendix B A 1 COMMON Information iunii t ee EET RARE ERES SSH AAA A TRE EFE ARN ERR LAE EAR o 75 Appendix B 4 2 DATA ATV Sitio lid idas BER OPERE ER ACD TREND EE locas AER E ENIRO dees ROTG coda Appendix B 4 3 Data Array FUNCtIONL ccccsessssesececeesensesssecscessessaassessceseessasseeseceseessasesesecsseessaseseseeseneseasaassesss Appendix B 4 4 Connections Adapters ccccccsssceessesnssceessecssceessecssscesseesssscessecssscesnsecsascessecssseeessecssssenseeenas AppendbcB 4 5 Nodes iue outta io A I ea oad dae ERE PE weet AA b
29. poll will be successful however if all 50 registers are polled in a single poll it will fail Map Descriptor 1 serves up 40001 Length 50 For this to work all 50 points must be contiguous in the same Data Array so that one Map Descriptor can be created If all 50 registers are polled in a single poll it will be successful If the Client polling algorithm keeps a fixed length of 50 and then decides to poll address 40050 length 50 the poll will fail because addresses 40051 through 40099 are not declared in the FieldServer Map Descriptor 1 serves up 40001 Length 200 For this to work points must be contiguous in the Data Array and the Data Array length must be at least 200 Since Modbus can poll a maximum length of 125 a Client cannot poll the required registers and encounter an address that is not configured This is therefore the most robust solution and only costs a few points SA13 Special Application Separating Responsible Map Descriptors Responsible Map Descriptors are active Map Descriptors that control the Communications see section 4 Two Responsible Map Descriptors cannot share the same Data Array Offset due to monitoring functions present in the kernel Refer to Section 4 3 for more information If two Responsible Map Descriptors require access to the same data the data can be made accessible to the second Responsible Map Descriptor by moving it to a second Data Array Server 1 Move u i gt 5 1 1 4 Special Ap
30. relevant to Protonode and X25 If this parameter is set to Yes or Enabled it loads the RS 485 line by placing additional resistance on it This Enabled Yas Bias_Mode has the benefit of making the signals cleaner in a noisy environment but Disabled No may reduce the maximum number of devices possible in a multidrop configuration Section Title Adapter Column Title Function Legal Values Adapter Adaptor name Arcnet DH Modbus Profibus etc MAC_Address Net_number Specify Network MAC address 16 Not all ports shown are necessarily supported by the hardware Consult the appropriate Instruction manual for details of the ports available on specific hardware FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 78 of 90 Appendix B 4 5 Nodes Device Name Provides name for Node Section Title Nodes Column Title Function Legal Values Node Name Up to 32 Alpha Numeric Characters specified by the retries parameter The FieldServer will attempt to recover the connection once the recovery interval has elapsed Node ID Specifies Node ID Information 1 255 Protocol Specifies Protocol used Modbus TCP etc IP Address IP address of Client PLC Valid IP address Specifies how many se
31. tee saeua dee eae vate conca accion 4 1 Active ws Passive TUhlctlons eco ois A A A gusce pee a 4 2 Passive Map Descriptor Functions 4 2 1 PASIVO E 4 2 2 Passive Client Passive Client c ccccccscccccessccessssceceessssecsessececssseceesseseceessessessssecsesssseesssaecsessseeesesssseeeaes 4 2 2 1 Working with Passive Client Passive Server Applications 4 3 Active Map Descriptor RUlctions iio Er an 4 3 1 Read Block Continuous Rdbc c ccccsscccceesscceesssceceesssseceessecsesssceceessssecussessesusseceessssecsssseceesuseeesesssseeeaaes 4 3 2 Active Read Continuous with Sequencing Arcs sessi iiie sees seen nnnn nennen nhan enhn ss sanant 4 3 3 Write Block on Change WrDbX i eee dent tete eene aet etl eo Koi oro nte dari eoe ge sint anei arabada k eua 4 3 4 Write Block Continuous Wrbc 4 3 5 Active Read on Trigger ART s cccccssccccsessessesssceceessesecssssesecssssecsessssecusseceesssseceessesecsuseeceessseeesesseseeeaaeees 4 3 6 Active Write on Trigger AWT o a ERROR Data Manipulation Features ec ccccccccccescesecececevecevaceveceeseevecseecevececeecvecevecedecereee eceedeevecereee ecsverevedesseevederseevers 20 5 1 MOVES UL IER 20 5 1 1 Simple MOVES ete trm RIS D Le hau Fea oed LT aee e ER beet ba 5 DAN Fe SE PUENTE Oba bo TOTEM nane RN Ea Udo 21 Sal sd Simple Move Exam ple iia ER E RR E E UR cess RR Ea rv et E sena 21 5 1 1 2 Special Application
32. the data for longer than the time configured under Cache_Time_To_Live Refer to Appendix B 4 then the FieldServer will stop reading the data and remove the Map Descriptor cache 8 2 Advantages of Port Expander Mode Configuration is simpler the FieldServer automatically creates and deletes Map Descriptors as required If mapping changes are made to a Client the FieldServer usually does not need to be reconfigured 8 3 Limitations of Port Expander Mode Port Expander Mode does not work with all combinations of drivers If the FieldServer is used as a Pure Port Expander Single Protocol there is no restriction at all e g Modbus RTU Port Expander The following families of drivers support Port Expansion within the family e Modbus RTU e Allen Bradley PCCC e Metasys 8 4 Port Expander Write Options Three possible scenarios exist for Writes in Port Expansion Mode e ATemporary Read Map Descriptor already exists for the point being written e A Temporary Write Map Descriptor already exists for the point being written e NoTemporary Map Descriptor exists for the point being written In the first two cases data is simply witten through the FieldServer to the Server using the existing Temporary Data Arrays lin the third case temporary Map Descriptors are created It is possible to configure the FieldServer to send an immediate acknowledgement of a write instead of waiting for acknowledgement of successful receipt from the Client
33. the delimiter which separates tokens in a Table String pattern and should not be considered as part of 1 10 000 pattern means ignore this token The number of Data Array items to be used to Length build the pattern to compare with the Table Number oFsens ndeniesiingshauie be the same as length under Moves 1 string Offset Table Offset Table Name Table String Table Index Value Length SPR4052 37 46 46 20 0 4 SPR4052 36 20 i 4 SPR4052 45 20 22 a SPR4052 43 20 3 4 SPR4052 45 20 m 4 SPR4052 43 20 75 4 SPR4052 42 20 6 4 SPR4052 37 20 2 7 m SPR4052 00 00 00 00 8 4 SPR4052 PATTERN DID NOT MATCH 111 n 5 2 9 2 Moves Definition Moves Source_Data_Array Source_Offset Target_Data_Array Target_Offset Length Function Offset_Table_Name Tokens 0 Status 0 4 Match pattern SPR4052 The Status Data Array will contain only the numbers O thru 8 or 111 depending upon the combinations existing in the Tokens Data Array 5 2 9 3 Table String Composition Source Data Array Source Data Array I Build Pattern Description Values Format 55150255 Byte 37 OF 00 FF Two Hex Characters 555 15 0 2550 INT UINT16 UINT32 555 15 0 2550 Just as decimal values 55 12 15 12 0 00 Requires period and two decimal 55 12 15 123 0255 FLOAT 255 00 places 1101 Bit 1 1 0 1 Binary pattern xn You could insert in place of
34. 0 DA_TDA 20 4 DIV DA_SDA1 10 DA_TDA 30 3 SQ DA_SDA1 0 DA TDA 100 4 SQRT DA_SDA1 10 DA_TDA 140 2 GTE DA_SDA1 0 DA_TDA 10 pl LTE DA_SDA1 0 DA_TDA 11 74 GT DA SDA1 0 DA TDA 12 pl LT DA_SDA1 0 DA_TDA p il 1 PER DA_SDA1 0 DA_TDA 14 pdb EQ DA_SDA1 0 DA_TDA 15 ye NE DA_SDA1 0 DA_TDA 16 1 FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 34 of 90 5 3 2 Standalone Math The Math definition allows up to four source data locations up to four Math operations and one output data location Operands are kept on a stack and are operated on in the sequence in which they have been defined Math functions consume 1 or 2 stack variables as inputs 2 for ADD SUB MULT DIV GTE LTE GT LT NE EQ and 1 for SORT SQ and leave the output on the stack ready to be used by the next defined Math operation The output of each operation becomes an input to the next operation along with the next defined operand Note Output of GTE LTE GT LT EQ NE AND OR and NOT is binary either 1 or O AND OR and NOT work the same way as Logic The following fields are specific to the Math amp Logic definition DAI1 DAI4 input Data Arrays 1 through 4 DOI1 DOI4 input Data Array of
35. 147 483 648 to 2 147 483 647 Default O Any signed 32 bit integer in the range 2 147 483 648 to 2 147 483 647 Default 100 Any signed 32 bit integer in the range 2 147 483 648 to 2 147 483 647 Default O Any signed 32 bit integer in the range 2 147 483 648 to 2 147 483 647 Default 100 Data Array Low Scale Scaling zero in Data Array Data Array High Scale Scaling max in Data Array Node Low Scale Scaling zero in Connected Node Node High Scale Scaling max in Connected Node 5 5 1 1 Scaling function example Converting Celsius to Fahrenheit The following portion of a Map Descriptor example shows the settings required for a Client Map Descriptor to take a Fahrenheit temperature reading and store it into the Data Array as a Celsius value Note that these parameters do NOT define the data range thus a temperature of 500 F will still be properly converted Data Array Low Scale Data Array High Scale Node Low Scale Node High Scale 0 100 32 212 FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 38 of 90 5 5 2 Scaling using Moves It is also possible to scale values while moving data between Data Arrays Doing the scaling this way often provides more visibility as it is then possibl
36. 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 62 of 90 10 2 1 Limitations of Hot Standby Mode 1 There is a time latency involved in the switchover process It takes about 2 seconds to achieve switchover from passive to active mode and the time taken for data polling and Data Array update needs to be added to this The Passive FieldServer will not respond to polling Data Arrays on the passive FieldServer are not updated until switchover polling and a successful response from the host has been achieved 10 2 2 Configuring the FieldServer for Hot Standby Mode 1 The required files are HSB P ini and HSB S ini there is no config csv file change required HSB P ini FieldServer HS Pair Name Hot Standby Mode HS Designation FieldServer1 Model Primary HSB S ini FieldServer HS Pair Name Hot Standby Mode _ HS Designation FieldServer1 Model Secondary Connections N1 N2 Connection Adapter Channel Mode Hot Standby Hot Standby Download the HSB P ini file to the FieldServer designated as Primary and the HSB S ini to the FieldServer designated as Secondary Please note that on the Download screen the Local and Remote file names need to match Restart the FieldServers The Activ LED on the FieldServer designated as Primary should be solid yellow Verify the operation by checking the error screen in Ruinet
37. 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 82 of 90 ASCII Code Char Comment ASCII Code Char Comment 55 7 101 e 56 8 102 f 57 9 103 g 58 104 h 59 105 i 60 106 j 61 107 k 62 gt 108 63 109 m 64 110 n 65 A 111 o 66 B 112 p 67 C 113 q 68 D 114 r 69 E 115 S 70 F 116 t 71 G 117 u 72 H 118 V 73 119 w 74 J 120 X 75 K 121 y 76 L 122 Z 77 M 123 78 N 124 79 O 125 80 P 126 A 81 Q Appendix B 6 Kernel Error Messages and Descriptions Error Description Action A write to a Data Array exceeds the available 10003 space Check Map Descriptor Offset length A write to a Byte FloatData Array exceeds the 10004 available space A range of data exceeds the length of a BYTE 10005 Check Map Descriptor Offset length count Data Array 10009 Protocol not detected Check Node Name in csv file Confirm that Active Map Descriptors are not added to No connection defined for an existing Physical a Server Node TM Node Descriptor Define the Client Node Descriptor connection in the CSV file Unable to create a Client Node Descriptor 10011 since no valid channel adapter or port has Specify a valid channel adapter or port been specified Attempting to read a range past the end of a 10014 Check Map Descriptor Offset length count BY
38. A e To switch the display to the PEX virtual tier from the main menu type T for Tier B for PEX e TheServer Name and the Adapter IP address connections that the FieldServer automatically discovers to the named Server Nodes are displayed on the Node Descriptor screen of the SCADA tier FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 66 of 90 10 3 5 Keepalive Map Descriptors Keepalive Map Descriptors read data from all the Nodes every 60 seconds and act as a Keepalive signal This is required for ascertaining cable status Example Consider two FieldServers connected in Hot Standby Mode 2 each with a SCADA Tier and a PEX Tier polling a two port PLC The SCADA Tier of the FieldServer receives data from the PEX Tier of the same FieldServer If the SCADA Tier of the second FieldServer is not polling the PEX side on its own FieldServer then there is no way that the second FieldServer can know when the cable connected to the PLC goes bad and reflect the change in the corresponding Data Array Hence Keepalive Map Descriptors are required which check the cable status and eliminate this condition Data Arrays Data Array Name Data Format Data Array Length DA Keepalive UINT16 6 Map Descriptors Map Descriptor Name Data Array Name
39. A_2 1 DAB 2 DA4 3 AND OR AND NOT DA 5 21 This definition will result in the following operation DA 5 21 DA 1 0 amp DA 2 1 DA 3 2 8 DA 4 3 FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 37 of 90 5 5 Scaling When writing a configuration file for the FieldServer it may be required for the FieldServer to scale data before passing it on to the receiving devices This can be accomplished in three different places in the FieldServer configuration e Inthe Client Side Map Descriptor section by adding scaling parameters e Inthe Server Side Map Descriptor section by adding scaling parameters e Inthe Moves section by adding Scaling Parameters In all cases four keywords are added to the section that needs to be populated with the necessary scaling parameters The FieldServer makes use of the four scaling parameters to calculate a slope and offset for scaling all incoming values It is possible therefore to do any linear value conversion that may be required 5 5 1 Map Descriptor Scaling For the first two cases where keywords are added to the map descriptors the four keywords to be used along with their valid ranges are as follows Column Title Function Legal Values Any signed 32 bit integer in the range 2
40. DO 01 Bit 200 I Data Arrays are protocol neutral data buffers for storage of data to be passed between protocols It is necessary to declare the data format of each of the Data Arrays to facilitate correct storage of the relevant data More information is available in Appendix B 3 FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 10 of 90 if Client Side Connections This section contains the parameters that describe the nature of the physical connection to the Server Nodes Connections Port Baud Parity Data Bits Stop Bits Protocol Poll Delay P8 9600 None 8 nat Modbus RTU 0 10Qs Timing parameters on the connection allow for fine tuning of communications The port to be connected to The protocol for the defined in terms of connection network connected to speed and properties this port This section defines the logical connection parameters for the Server Nodes communicating with the FieldServer Client Side Nodes Nodes Node Name Node_ID Protocol Port PLC nl Modbus RTU P8 The Server Node is attached to this connection A name allocated to the node for reference by the Map Descriptors The Node ID of the Server FieldServer Technologies 1991 Ta
41. FieldServer Technologies FieldServer Configuration Manual APPLICABILITY amp EFFECTIVITY This manual provides instructions for the following FieldServer products Description FS X20 Series FieldServer FS X30 Series FieldServer FS X40 Series FieldServer Effective for all systems manufactured after February 2012 Kernel Version 6 04 Document Revision 2 FieldServer Configuration Manual Table of Contents TABLE OF CONTENTS 1 1 2 1 3 FieldServVer Concepts nissene E E EE EEEE EE S EE E S EE EE EE 6 1 1 INtrOdUCtOM as ioci tc aii 6 1 3 1 1 3 2 Overall Operation Philosophy 3 o Eie a aaa aa ao a a asia seisena aseetita 8 Getting Started Basic Configuration sessssssesecosssssssscccssssssseccesssessseceosssssseecessssssssecesssessseceosssssseeseessssse 9 3 1 Configuration File Ova Wii even E oque sen o aee e eR ee Ve Hee PENNE eer eu era ea gea Aide 9 3 2 Configuration Elle STRUCTURE EE RET RET RR AAA Ao ais 9 3 3 Editing Configuration Files NR EO rI AA AN szannacech se ssnsnes sagusnaenanaaneasaanveasts 13 3 4 Testing Configuration Files with MB8SIM EXE ccccsssccccccessesssceseeececseseeaeseeececseeaaeeeseescseeaaeaeeeesceeeea 13 3 4 1 Additional worthwhile MB8SIM checks eese isses sees eene sintesi tnis a tesis s saisir tassi sienne 15 Map Descriptof EUFICLIOTIS 03d ee oe eoi Eee oe areae ate ao deoa eaae ade gea ewe aee euet a deae er
42. Format tells the kernel how to interpret the number specified by the Preload Data Value parameter Example If Preload Data Format is set to Byte then the preload value is cast to a byte before being stored in the Data Array 5 6 4 Example 1 Load a Value Preloads Data Array Name Preload Data Value Preload Data Format Preload Data Index DA SDA1 nid n 0 The Data Array named DA SDA1 must have been previously defined in the configuration file or else there will be a configuration error Format specified with a dash therefore the value 11 will be type cast to an unsigned 32 bit integer Omitting the value altogether would have the same effect Note If the format of the Target Data Array is Bit then the value 11 will not be stored as Bit arrays can only store 1 and O 5 6 5 Example 2 Load a Value Effect of Target Data Array Format Data Arrays The value 257 will be stored Data Array Name Data Format Data Array DA 1 FLOAT 20 i Only numbers in the range 0 255 inclusive DA 2 BYTE 20 can be stored in a BYTE array The kernel chops off the part of the number that exceeds the byte Therefore the value stored will be 1 The value 257 is cast to a floating point number Preloads Data Array Name Preload Data V Preload Data Format Preload Data Index DA 1 257 FLOAT 0 DA 2 257 FLOAT 0 FieldServer Tec
43. SA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 75 of 90 Note Titles in brackets indicate aliases Appendix B 4 1 Common Information Cache Age Timeout internal data buffer is returned to the Server providing the data is not too old This parameter specifies the length of time cached data is valid Section Title FieldServer Column Title Function Legal Values Allows user to add title to main menu if desired Title text may not Title Title Text contain spaces When poll block caching is used data previously polled and stored in an Cache Age Time in seconds 300s Cache Time To Live longer that the time specified by this parameter the cache will be cleared Cache Size Specify size of Cache 0 1000 80 Used for Port Expansion A cache is created for data from a Node for which no Map Descriptor is configured If this data is not accessed for Time in seconds 300s Appendix B 4 2 Section Title Data Arrays Data Arrays Data Format Provides Data Format Column Title Function Legal Values Data Array Name Up to 15 Alpha Provides name for Data Array DA Name Numeric Characters INT16 INT32 or BYTE Specifies size of source value when scaling FLOAT floating point format specifies for preloaded data in buffer
44. ST for assistance FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 61 of 90 ETHERNET Passive FieldServer ES mititica AE boh dn Jh GL n n Ld Pa P5 P4 P3 PB P Power Net 2 Net1 9 09 Pa us LETEO LTE 10 100 Base T ne RI RS a85 EST Opto Isolated Ribbon cables FS 8915 16 transfer hardwired ports to EH BS Serial connection to PLC gt standby FieldServer 2 A RARA Net Nec 1 g g PB P7 PB P5 P4 pe Pi Ethernet AS 232 10 100 Base T Re m1 AS 485 Opto Isolated Active FieldServer Figure X Hot Standby Mode 1 Option 1 Passive FieldServer Opto Isolated Ribbon cab FS 8915 16 transfer hardwired ports to standby FieldServer Serial connection to PLC Net2 Net 1 ig ip PB P7 Pe P5 P4 P3 PB Pi Power us 22532 emma 2838 10 100 Base T Re m PRES hs 285 Opto Isolated Active FieldServer Figure XI Hot Standby Mode 1 Option 2 1 There is no way of connecting a PC to the Ethernet ports or monitoring FieldServers by Utilities when using this option FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax
45. Server Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 65 of 90 ETHERNET Passive FieldServer Ribbon cables Serial Port FS 8915 16 transfer hardwired ports to standby FieldServer Active FieldServer Figure XIV Dual Port Server 10 3 3 Tiers SCADA and PEX To maintain an image of the complementary system in a FieldServer FieldServers have the ability run as multiple FieldServers on one platform To differentiate between the different running applications each of the applications is referred to as a Tier with a specific name Hot Standby Mode 2 makes use of the SCADA tier and the PEX tier for achieving its functionality The configuration file CONFIG CSV is now split into two sections one section for PEX tier and one section for SCADA tier Each section is identified by the keywords PEX TIER or SCADA TIER Note the PEX tier must be defined FIRST 10 3 4 RUINET functions for Hot Standby Mode 2 To view the various tiers on the FieldServer using RUINET e Connect in the normal fashion e g RUINET 1192 168 1 13 This connection will directly connect to the PEX Virtual Tier e To switch the display to the SCADA virtual tier from the main menu type T for Tier A for SCAD
46. T PLCS PLC10 aBRZ EREEP c S28 E 2 g rS 33 VIS s Physical Physical ERRELLEL ER 222 information Server s 5 FieldServer 3 FieldServer 3 FieldServer 4 Information Server ili E FieldServer 4 auxiliary auxiliary Figure XV Hot Standby Mode 2 Application Primary and auxillary FS X40 FieldServers are used to allows RS 232 connection to more than 8 PLC s e The dark blue boxes represent the physical FieldServers e The light gray boxes represent the information Servers e The thin lines represent the RS 232 RS 485 serial connections e The physical Ethernet connections are NOT represented e The thick solid and dotted lines represent the logical Ethernet connections possible from FieldServer 1 to all possible sources of data Connections from FieldServer 2 are not shown but do exist Redundancy is Achieved as Follows e When FieldServer 1 fails FieldServer 2 takes over and remains Active until FieldServer 2 fails at which point FieldServer 1 takes over e If the PEX tier of FieldServer1 fails the SCADA Tier of FieldServer 1 will get the data from the PEX Tier of FieldServer 2 FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email suppor
47. TE Data Array 10016 Could not find or create Node Check Node Name Node ID and protocol in CSV file FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 83 of 90 Error Description Action 10019 Check CSV file spelling Protocol or Node Name for Map Descriptor 10023 Check CSV file not detected Modbus TCP Client goes offline before 10025 u Increase the timeout on the Modbus TCP Client receiving a response to a poll 10006 There is no connection to one side of a virtual Ensure that a Client and a Server is configured for each wire virtual wire 40027 Connection mode of Hot Standby Data only supported in Hot Standby Mode1 10028 Could not find nor create a Node Refer to 10010 The data points limit on the FieldServer has 10031 Contact FST been reached A Server Node has been assigned to a Client 10032 Map Descriptor OR a Client Node does not Check CSV file have a connection Server Name 10033 Invalid length specified for Cable Status Bits See specification inSection 10 3 8 2 An attempt to generate a write cache block 10034 failed because the Node did not have a connection A protocol was specified in the configuration i i Correct the pr
48. The kernel checks the condition of the bits every second for a change in status Moves Source Data Array Source_Offset Target_Data_Array Target_Offset Length Conditional Data Array Conditional Offset Task_ Name Scan Interval Source 1 0 Target 00 21 Status T a ell Source_2 0 larget 01 A Status pail b mel 15 2 10 2 Conditional MovesExample 2 In this example the data from DA GV 01 will be moved to Gas Snapshot only when DA GP PW 01 or DA GL PA O1 is updated on offset 192 In this example all of the Data Arrays are bits but analog data types will work as well Moves Source Data Array Source Offset Target Data Array Target Offset Length Conditional Data Array Conditional Offset Task Name Scan Interval DA GV O1 192 Gas Snapshot 00 E DA GL PW 01 192 a pel DA_GV_01 192 Gas Snapshot 01 E DA GL PA 01 192 b 1 The Conditional Move that executed last becomes the Responsible Move by which data validity is determined and through which write operations are routed If none of the Conditional Moves targeting a specific location have executed the Conditional Move defined last acts as the Responsible Move FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 33 of 90 5 3 Mathematica
49. The offset within the Data Array to which data is to be copied The number of consecutive source Data Array values to be moved to consecutive Length target locations starting at the respective offsets The name of a Data Array to be used for conditional moves See Section 5 1 1 3 for Conditional Data Array more information The offset into the Conditional Data Array where the conditional bits for the move Conditional Offset are defined The value found at this specified location must be non zero for the move to be executed If the value is zero the move is inhibited TKN If a task name is specified the move operation becomes a continuous task on the ask_Name FieldServer that is executed at the scan interval specified The time interval at which the task will be repeated A task name must be specified if a Scan Interval u scan interval is specified FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 32 of 90 5 2 10 1 Conditional Moves Example 1 l In this example the user needs to move the data from one of two source locations based on the status of bit 1 or 2 of the conditional Data Array If bit 1 is high then the data from Source_1 will be moved If bit 2 is high the Data from Source_2 will be moved
50. USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 48 of 90 7 DYNAMIC PARAMETERS Most FieldServer parameters are specified in a configuration file and are fixed A growing number however may be changed dynamically using values found in Data Arrays We call these Dynamic Parameters The following parameters can be dynamically configured Section Parameter 5 Notes Title This parameter typically describes the Server device address of a Node ID Nodes nau communications session Many drivers use this parameter and the meaning of the parameter is dependent on its context System Node ID FieldServer e g BACnet Used as the MAC address DNP3 Used as the local station ID Similar to changing the System Node ID but specifically designed for use BACnet MAC Address FieldServer on ProtoCessors because it also writes the new ID down to the PIC where BACnet is implemented 7 1 1 Dynamic allocation of Node ID or Station number Almost all FieldServer configurations consist of a Server and Client side The Client side of the FieldServer reads data from the Server device The Server side of the FieldServer then serves this data to remote Client Nodes using a different protocol The configuration of the Server Side of the FieldServer is done in a configuration file and as such is fixed This is
51. age 10117 will be printed One of the following O to maximum where maximum is the length of the Data Array being referenced less 1 e g If the Data Array length is 200 the maximum value of this parameter is 199 Length Not used A length of 1 is always applied One of the following Preload Data Value Preload Value Specify the value to be used to initialize the Data Array Location If the Data Array specified is a Data Array of Complex Data Objects CDO then the kernel stores the value to the objects Present Value field The value is assumed to be a floating point value and the format specified by the parameter below is ignored Any number may be specified with a fractional part e g 0 1 1 01 1 123 456 A String One of the following Preload_Data_Format Data_Array_Format Data_Format This parameter tells the kernel how to interpret and apply the the Preload_Data_Value parameter not to be confused value specified using with the format of the Data Array Float Bit Byte Uint16 Uint32 Int16 Int32 String Preload Obj Name If this parameter is specified then the kernel takes the value specified by the parameter and uses it to assign a Name to the Data Array object if the Data Array is an array of Complex Data Objects CDO A maximum of 39 characters Leading trailing spaces and tabs are ignored Commas not supported support for other special ch
52. al Page 51 of 90 7 1 3 2 Example 2 Dynamic Allocation of System Node ID The FieldServer watches DA NODE ID NEW offset O When the data is updated the FieldServer looks for a Node named NODE_1 If a valid one is found then the NODE ID of that Node will be changed and the FieldServer will print a message reporting the change Dynamic Parameters Function Descriptor Name Data Array Name Data Array Offset Low Limit High Limit Save Change System Node ID NODE 1 DA NODE ID NEW 0 0 255 Yes The Low Limit and High Limit parameters may be omitted in which case the Node ID is not validated against them The save value enables or disables making the change permanent If yes the value will be stored and used next time on start up as the Node ID If no the change will only remain until the next power cycle at which time the value in the configuration file will be used 7 1 3 3 Example 3 Dynamic allocation of the BACnet MAC address Configuration and operation is the same as changing the System Node ID except that this command not only changes the value of the System Node ID parameter it also causes the firmware to write to the underlying PIC on the FieldServer to have it start using the new ID Dynamic Parameters Function Descriptor Name Data Array Name Data Array Offset Low Limit High Limit Save Change System MAC Addr Bridge1 DA NODE ID NEW 0 0 255 Yes In the example above
53. alent to the station address of the Node Refer also to Section 9 Appendix B 2 and Appendix B 4 5 Example If seven Nodes are connected to the FieldServer when the Node with ID 5 is online the sixth bit of the Data Array configured for the function Node Status will be set to 1 zero bit is unused Typical Data Array Parameters are Section Title Data_Arrays Data Arrays Data Array Name Data_Format Data Array Length Data Array Function DA Comm OK Bit 256 Node Status FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 45 of 90 6 1 2 Alias Node ID If you have two Nodes with the same Node ID or your Node ID s are longer than 255 the Node Status Function as described above will not work correctly In such cases each Node can be assigned an Alias Node ID which can be used to provide Node Status Typical Data Array Parameters are Section Title Data Arrays Data Array Function Special function for the Data Array 6 1 3 Alias Node ID Example A Data Array has been defined to report the status of the Nodes in the configuration using the Alias Node ID Each Node that has been allocated an Alias Node ID will have the corresponding bit in the Data Array set unset ba
54. aracters unknown 7 Strings This has been tested with strings up to 320 characters long Leading and trailing spaces and tabs are ignored commas cannot be used and support for other special characters is unknown Format must be specified as STRING The case of the characters is preserved 8 Must be specified as String if Preload Value is String FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 40 of 90 5 6 3 Limitations and Operational Considerations e Each Data Array location to be preloaded requires its own preload line in the configuration file e The value specified must be compatible with the format of the Data Array e g Integer arrays cannot be preloaded with numbers that contain fractions e Preloads cause Data Array updates The FieldServer kernel does not differentiate between an update on a Data Array performed as a preload or as the result of a store after processing a protocol message If the Data Array point is associated with a Map Descriptor using the Write on update Wrbx function or an Rdbx function set to Write through the preload will trigger the write Refer to Section 4 3 3 for more information e The Preload Data Format must not be confused with the format of the Data Array being preloaded The Preload Data
55. arget Offset Length Source Low Scale Source High Scale Target Low Scale Target High Scale Scale DA Unscaled 00 DA_Scaled 00 AS 00 10 00 100 FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 39 of 90 5 6 Preloading Data Arrays with Initial Values 5 6 1 Introduction Preloads provide a technique which allows parts of one or more Data Arrays to be initialized to specified values The Preloads are defined in a configuration file and loaded once when the configuration file is loaded as the FieldServer starts It is also possible to use the FieldServer scripting language to have the FieldServer load a configuration file and then poke values into the Data Arrays For more information on this technique call FST Tech Support 5 6 2 Parameters used to define Preloads Data Array Offset Preload Data Index Location Data Array Location Data Array Index Buffer Offset The location in the Data Array to be preloaded Section Title Preloads Column Title Function Legal Values Name of the Data Array to be preloaded The Data Array must exist or be defined in the configuration file AA Up to 15 alphanumeric Data Array Name and its definition must precede the preload that MES references it If not System Error Mess
56. arob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 29 of 90 5 2 9 Match pattern The match pattern move is used at run time to move a customized single value based on combinations of values in a Data Array as compared with preloaded customized criteria The user builds a table of patterns strings of tokens separated by each linked to a particular location in a target Data Array A PATTERN DID NOT MATCH string may also be defined and linked to a Data Array location A pattern is built based on the values in the Data Array at run time by the move function The pattern built at run time is compared with the preloaded table of patterns The tokens in each pattern must match exactly If the preloaded pattern contains a wildcard that token would not be compared If the pattern matches a pattern in the table its value will be stored in the target Data Array at the specified location If the pattern does not match any of the preloaded patterns in the table a check is done for a PATTERN DID NOT MATCH string in table If found the corresponding value will be stored in the target Data Array If a PATTERN DID NOT MATCH string is not defined a default value of 1 will be stored and an SDO will be generated prompting the user to add a PATTERN DID NOT MATCH record to t
57. be referred to as Stations Nodes RTU s DCS s Workstations SCADA Systems MMI s Field Devices etc To prevent confusion these devices are always referred to as Nodes in this manual Similarly Device Address Station Address Station ID is always referred to as Node ID in this manual 1 LonWorKS is a trademark of Echelon Corporation registered in the United States and other countries Except for FS X20 3 Nodes may have the same Node ID value so long as they are connected to different ports FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 7 of 90 1 3 2 Clients and Servers A Client Node can request data from and write data to a Server In Process Control and Building Automation applications it is accurate to describe a Client as a device that receives status and alarm data from a Server and writes setpoints and control points to the Server In a FieldServer application there is a Client Server relationship on each network coupled to the FieldServer It is therefore typical that the FieldServer acts as a Client and a Server at the same time Figure I below illustrates this MASTER Client Node Server Side EI 5 5 Client Side Server Node
58. been specified This FieldServer will not be accessible on the TCP IP network through one or both of these adapters The IP ADDRESS for adapter N1 or N2 has not 40119 been specified This FieldServer will not be accessible on the TCP IP network through one or both of these adapters 10120 An unrecognized rui command was received Check that the Ruinet and Kernel versions match In the BACNet driver the OPTION LIST specified caused the packet buffer to be 10125 FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 86 of 90 Error Description Action Te The BACNet driver received a request for a This is not reported in the current release of the read property multiple with multiple objects BACNet driver An UDP socket buffer overflowed and UDP 10127 data was lost The keyword MY IP has been used in the 10128 Only use KW_N1 and KW N2 FS TCP INI file The keyword N1 IP has been used in the 10129 Use the FS TCP INI file SMCTCP INI file UDP broadcast panics has been disabled until 10130 i a hardwired send is added The ARP resolve queue has been overrun This i i Check all IP_addresses in particular the gateway 10133 is typically the result of a mis configuration on a
59. ce i e if the device station is configured to be 10 position 10 in the Data Array will show the number of errors per hour Errors for the past 60 minutes are stored Dev Msg Rates Same as above except counting messages not errors Dev Error Percentage Percentage of messages generating errors over the past hour Node Status Provides the communication status between the FieldServer and the actively mapped Nodes Refer to Section 6 1 1 Alias Node Status Where 2 nodes have the same Node ID or Node ID s are longer than 255 each Node can be assigned an Alias Node ID which can be used to provide Node Status Refer to Section 6 1 2 FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 77 of 90 Appendix B 4 4 Connections Adapters Section Title Connections Column Title Function Legal Values Specifies the port through which the device is connected to the Port P1 P8 R1 R2 FieldServer 3 9600 Baud Specifies Baud Rate 38400 Stop Bits Sets the stop bits for communications H3 7 When using RS 485 specifies delay from end of message to when the RTS Time Line Drive O EET E E line is deasserted seconds Ic Timeout urnaround_ ff n T Delay This is the time the Server takes to initiat
60. d a Driver Configuration Code DCC The DCC covers the combination of drivers listed on the cover In addition to the specific configuration instructions for each driver these manuals provide drawings and default configuration files for the combination of drivers The Driver Manual contains a section for both the Client and Server side software drivers Each section of this supplement is split into two parts The first describes the hardware and software included with the FieldServer as well as providing additional information relating to getting the FieldServer set up and connected The next part discusses the configuration file in detail and provides all the information needed to configure the driver related parameters Appendix B 1 2 Driver Manuals as Part of the Documentation Set In order to install and configure the FieldServer proceed through the instructions in the Start up Guide Refer to the Driver Manual for connection information If the default file is all that is needed then nothing further is required it is already loaded onto the FieldServer If it is necessary to modify the Configuration Files to suit specific needs please refer to Section 2 of this manual for a general overview of the configuration file and then refer to the specific driver supplements for configuration information on the drivers Appendix B 2 Default settings for parameters Parameter Default Setting Default response timeouts 2000 ms 2 sec
61. d to the single RS 232 port of the PLC These splitter devices are robust and manufactured using just a few passive electronic devices diodes to minimize the chances of failure In this arrangement the two FieldServers have to poll the Server alternately to prevent serial message collisions A token passing method is used to achieve this The FieldServer with the token is allowed to poll the Server on its serial port When the response is received the token is transferred over the Ethernet to the other FieldServer which then takes its turn Timeouts lost or duplicate tokens or failed FieldServers are also managed in an elegant fashion Clearly data would be lost if the Single Port Server were to fail in any way 10 3 2 Dual Port Server Server devices that make two ports available for redundant communications are referred to as Dual Port Servers Each port can be connected to a separate FieldServer allowing each FieldServer to poll for data at will This arrangement is depicted in Figure XIV Should one of the ports fail then the data is routed to the Client through the PEX Tier of the other FieldServer and then through the SCADA tier to the Client Refer to Figure XIV and Section 10 3 2 If both FieldServers were to fail obviously the data cannot get to the Client at all This means that there ARE situations where two points of failure can occur and cause the system as a whole to fail With dual redundant systems this is unavoidable Field
62. ddress the FieldServer The Client side plc channel has not yet been 10134 A cache block was not created discovered or an attempt to write to an Analog Input Data Type A temporary write block has been removed 10136 because an identical one existed Write data might have been lost Warning the Server is responding with data 10209 from an explicit Map Descriptor that is not reading continuously Info the inet Server received a write to input 10210 command that is not supported Warning A Server side driver tried to read from a Data Object that has a WRBX as a 10214 responsible Map Descriptor The data being read from the Server side might not be the same as on the Client side A Server node is associated with more than 10216 one Client Node Display RX IP fragments stat in the Ethernet api stat An IP Fragmented packet was received while 10302 screen f this occurs frequently enable IP IP Defragmentation was disabled Defragmentation 10401 The I Net Server ignored a write to an Input The Baud Rate on a Connections Port has not 10402 A default value will be used been defined The MSTP driver must run at a cycle time 10403 shorter that 10ms or proper operation cannot be guaranteed The Write Queue is full and data has been 35254 overwritten This could be caused by using Solve by increasing the Write Queue Size or slowing moves to do multiple write thru s on a RDBC write thru s Map Descriptor 10999
63. ddress of the specified Node will be at offset O The length parameter will be used to determine the Node ID 1 to 256 number of Node addresses starting from the Node ID If not declared or specified as Node ID O will be at offset O This allows the subnet of the Node to be declared If subnets Subnet ID are not used this parameter can be excluded If specified as 0 to 256 the subnet is ignored and all Nodes will be found Data Arrays Data Array Name Data Format Data Array Length Data Array Function Node ID Subnet ID Node on Net Bit 30 Node Online Bits mel ae Node_on_Net1 Bit 30 Node_Online_Bits T4 1 Node_on_Net2 Bit 30 Node_Online_Bits 10 22 Node on Net3 Bit 30 Node Online Bits 10 23 Node on Net4 Bit 30 Node Online Bits 10 4 Node on Net5 Bit 30 Node Online Bits 10 25 FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 47 of 90 6 2 Connection Parameters 6 2 1 Node Retire Delay When a FieldServer is started up it polls all Nodes Nodes that respond within the specified timeout period seconds will be marked online Nodes failing to respond within the timeout period will be repeatedly polled for the length of time specified in the Node Retire Delay parameter second
64. de address Practical odeSta ata A limit is 255 Nodes the offset corresponds to the Node ID The value of the integer rra T corresponds to the current Node status A Data Array showing the status of all Hot Standby FieldServers in a pair e g which Hot Standby FieldServer is active is it the primary or secondary is the standby FieldServer active why did the switchover occur 10 2 Hot Standby Mode 1 True Hot Standby Two FieldServers are used in this configuration one designated as Active and the other as Passive The Active FieldServer transmits and receives information from the remote Nodes and transmits a constant heartbeat signal to the Passive unit On failure of the Active FieldServer the heartbeat stops and control switches to the Passive FieldServer which consequently becomes the Active FieldServer This FieldServer now polls the host for data and updates its Data Arrays and from this point maintains communication with the host The heartbeat can be transferred via 2 Ethernet ports using either 2 hubs Figure X or 2 crossover cables Figure XI Two are used in order to preserve the redundant capability of the entire system Hot Standby Mode 1 is ideal for straightforward applications where the objective is simply to prevent a FieldServer hardware failure from interrupting communications Only Modbus RTU is supported for Hot Standby at present Most other drivers could use this function but should refer to F
65. ded from the Non Volatile Memory into the Data Array This value will only be stored 3 times a minute so if more writes than that are done the values will be stored in the Data Array but not to the Non Volatile Memory Storing this value has performance impacts so care must be taken to store this value only if needed Loading Data Array Values from the FieldServer s Non Volatile Memory There is a limit to the number of values that can be stored from a single data array UINT32 9 FLOAT 9 SINT32 9 UINT16 19 SINT16 19 BYTE 39 Example Data Arrays Data Array Name DA NV UINT32 Data Format UINT32 Data Array Length nit DA Function After Store Non Volatile FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com Page 43 of 90 FieldServer Configuration Manual Page 44 of 90 6 NODE MANAGEMENT 6 1 Data Array Functions 6 1 1 Node Status Function The Node Status Function is a Data Array function which provides the communication status between the FieldServer and the actively mapped Nodes The online status of a particular Node is indicated in the Node Status Data Array If the communication status is good then the Node Status is set to 1 The communication status goes bad if it does not receive a response to a poll The offset number in the Data Array is equiv
66. e ID or Change_System_MAC_Add You may ignore this message if it confirms your expectations DynParam 9 FYI Cant write MAC ADDR to PIC with this firmware This message will be printed immediately after 48 if the platform is not a ProtoCessor It can be ignored 9 Edit the configuration download the modified configuration and reset the FieldServer for the changes to take effect FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 53 of 90 8 PORT EXPANDER MODE PEX MODE Under certain conditions the FieldServer can be configured in a Port Expander Mode where statically configured Map Descriptors are not required to retrieve data from a Server Node 8 1 How Port Expansion Works When the FieldServer receives a poll from the Client Node it scans its internal tables looking for a Map Descriptor that matches the poll If such a Map Descriptor is found the FieldServer responds with data from the appropriate Data Array If no Map Descriptor is found the FieldServer scans the list of configured Nodes and creates a Map Descriptor cache to fetch the data from that Node and returns this data to the Client The FieldServer will continue to retrieve data from the Node for future polls from the Client Node If the Client Node does not access
67. e a response after having Delay Turnaround_Time received a poll seconds Where two FieldServers are connected in Hot Standby mode each with a PEX and a SCADA Tier if the SCADA Tier of one FieldServer polls the Client Server Mode i C 7 SCADA Tier of the other FieldServer that tier will start acting as a Server n nt cki 3 16 0 Ev Odd Parity Specifies serial data byte parity N one 1 in in in in ly 0 e Data Bits Sets number of data bits for serial port 2 lie o Setting this parameter to Client Only will prevent this happening This parameter allows the user to configure a time after which a Node is Node Retire Delay i i Time s O no longer polled until the FieldServer is restarted See Section 6 1 4 Mode for dealing with potential accumulation of successive writes to the Overwrite Write Queue Mode same point can be configured Bl n The length of the queue can be configured if blocking mode is set When using RS 485 specifies delay after RTS is asserted until message is Time transmitted seconds sale a m Timeout Specifies inter character timeout period within a message once it starts d seconds On g Write Q Size Blocking will occur when there is no more space on the Write Queue Non negative rite Queue Size Hu If size 0 every successive write is blocked A message will be displayed integer 0 when blocking occurs except if the Queue SizezO Only
68. e and responds with data accordingly The Passive function will also accept writes and update the associated Data Array 4 2 2 Passive Client Passive Client The Passive Client function is intended for use where the associated Map Descriptor performs a Client function and is connected to an active Server The Passive Client function will consume all unsolicited messages for the related point s and store them in the associated Data Array 4 Note that not all functions are supported by all drivers Refer to the specific Driver Manual for information on functions supported by individual drivers FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 17 of 90 4 2 2 1 Working with Passive Client Passive Server Applications Data Server Client Typical Properties Map Descriptor function used for both protocols A and B is passive FieldServer is non intrusive into both networks and responds to queries and commands only Network Protocol A Network Protocol B FieldServer Figure V Typical Network architecture Some applications require the data Server to actively write data to and from the FieldServer To do this it is necessary to change the Client side of the configuration to be passive Individual drivers have specific requirements f
69. e bits are placed into the destination array in sequence Only one bit is allocated per offset If the source array is of Bit Data Array type a straight move is performed The function extracts the binary version of each source offset and packs the bits into the Data Array Sie Pack offset specified The number of bits packed depends on the target Data type e g Bytes will get 8 bits Floats will get 32 etc The length will specify the number of bits to pack If the destination Array is a Bit data type a straight move is performed ai Woe The function extracts a subset of bits out of a source Register offset and transfers these to a Y destination Register offset in packed form Length specifies the number of bits to be extracted Keywords Function i Values The parameter specifies the bit offset within a word to start at when performing a bit Default Bit Die move For Bit Extract operations the source bit offset in the word pointed to by the O i Source Offset parameter is implied For Bit Pack operations the bit offset within the word pointed to by Target Offset is implied p Default Length The length parameter specifies the number of bits to be extracted packed 1 5 2 4 Example 1 Simple Bit Extraction The following example extracts 3 16 bit registers worth of data from the 6th register of the source array into the equivalent target of 48 bits Data Arrays Data Array Name Data Format Data Array Length
70. e bytes ab cd target bytes cdab 2 116 1 132 m10k Join M10K Modulo 10 format Int32 Split 1 132 2 116 Split_Int32_Swapped source bytes abcd target bytes ab cd 1 i32 2 i16 sw Split Int32 source bytes abcd target bytes cd ab Float Join 2 116 1 float Join Float Swapped source bytes ab cd target bytes cdab 2 116 1 float sw Join _Float source bytes abcd target bytes ab cd Float Split 1 float 2 i16 Split Float Swapped source bytes abcd target bytes ab cd 1 float 2 116 sw Split Float source bytes abcd target bytes cd ab Integer Join 2 18 1 116 Join_Int16_Swapped source bytes a b target bytes ab 2 18 1 16 s Join_Int16 source bytes a b target bytes ba Integer Split 1 116 2 i8 Split_Int16_Swapped source bytes ab target bytes a b 1 116 2 i8 s Split_Int16 source bytes ab target bytes b a Figure VI Legacy Functions for Type Casting Moves FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 24 of 90 5 2 2 Converting two Integers to a Float Data_Arrays Data Array Name Data Format Data Array Length Source DA Uint16 200 Target DA Float 200 Moves Function Source Data Array Source Of
71. e to view both scaled and unscaled data in the Data Arrays The keywords for scaling in the moves section are different from the Map Descriptor keywords in order to avoid confusion but function in much the same way The keywords are Column Title Function Legal Values Source Low Scale Scaling zero in Source Data Array Any signed 32 bit integer in the range 2 147 483 648 to 2 147 483 647 Default O Source High Scale Scaling max in Source Data Array Any signed 32 bit integer in the range 2 147 483 648 to 2 147 483 647 Default 100 Target Low Scale Scaling zero in Destination Data Array Any signed 32 bit integer in the range 2 147 483 648 to 2 147 483 647 Default 0 Target High Scale Scaling max in Destination Data Array Any signed 32 bit integer in the range 2 147 483 648 to 2 147 483 647 Default 100 i 5 5 2 1 Moves Scaling function example Multiplying values by 10 The following move example shows 5 values being moved from one Data Array to another DA Unscaled DA Scaled During the move the values are multiplied by 10 because the scaling parameters state that A value from O to 10 in the Source is being represented as a value from O to 100 in the Target Again these do not represent limits and so a value of 500 would also be scaled properly and end up as 5000 in the Target Data Array Offset Moves Function Source Data Array Source Offset Target Data Array T
72. ecause the Node did not have a write to this Node occurred before the Server Name connection mechanism discovered a valid connection The maximum number of concurrent cache 10103 blocks has been exceeded A write cache block poll did not occur 10104 Connection mode of Hot Standby Data is only supported in Hot Standby Mode1 PLC Port Count 1 only supported in 10105 Set FieldServer parameter hs mode to mode2 hot standby mode2 An invalid hot standby mode has been 10106 specified as part of the FieldServer check hsb_p s ini files parameters Could not create cache block possibly 10107 because the maximum number of data_points Contact FST has been exceeded 10108 A BACNet alarm event was generated but the required Alarm Limits has not been set 10110 Hot Standby partner discover found a PRIMARY SECONDARY mismatch Hot Standby partner discover found an API 10111 Version mismatch Hot Standby partner discover found a DCC 10112 f version mismatch Hot_Standby partner_discover found a 10113 ANM config file mismatch A Node ID 255 was used in the Hot Standby 10114 q commbit configuration A port other than P1 R1 was specified on an 10116 X20 The port handle has been changed to point to the only UART on X20 The Gateway Address for adapter N1 has not 10117 been specified This FieldServer will only be accessible on the local TCP IP subnet The NETMASK for adapter N1 or N2 has not 10118
73. eeeeee cete eese eee eene e neones naoso aneas oeoo osoa ener eene eene 53 8 1 How Port Expansion Works ccccsssessccececsssssneeesececsensseceeseceescsesuneesececscsesaeaeseceesssesaaeeseceeessesnsanseseeeseeeas 53 8 2 Advantages of Port Expander Mode 8 3 Limitations of Port Expander MOde ccccccccccsssssssecccecsessaeeeeccecseseseeseeecscsesesaeseeeeeceeseeaeseseesesesesaeaeseeseeeee 8 4 Port Expander Write Options miserorum eee tr REPRE he te Ree oce ee RE Ee eee een Ea oreet oe Vo Pea Ee pelo 8 5 Handling of Successive Writes to the Same Point cccccccccessessssececececeeseaeeeeeesceesesaseeseesceeseeasaeseceseeees 54 8 6 Port Expansion Configuration niteni eeaeee n e a a e aa a eki a 54 A AS AT 55 9 1 A e eese tcn vete etu ve to texte Rente EE e ER RERO T 57 9 2 Suppressing Squelch on Half Duplex Communications ccccococooconncnonononannnnncnnnnnonannnnnoncnnnnnonnnnnnncnnnnnnnnnnos 57 9 2 1 Setting Parameter Val es 31 455 id RO A E a ex dig oleae a dena de ende doge 58 9 2 2 EOS ES uero eer ee EU RUNE ues ERE esee rate ut rada ita A tals eese aros 58 9 3 Enable onRS 232 NO 59 10 lA EA 60 10 1 TerrminoloBy soris E te eere re S Pee CR RERNTUR BEST tre EXER CEPR AEN exi Ee EE ee e OE NO SRM 60 10 2 Hot Standby Mode 1 True Hot Standby cccccssscccsssseceessscecsessececessseceesseseceesaeeecsesseeeesseeeceesaeeeessaaess 60 10 2 1 Limitations of Hot Standby Mode 1 isses seien
74. eir origins as wire concentrator centers and often house FieldServers routers and network management devices Internet The Internet is a collection of over 2 000 packet switched networks located all over the world all linked using the TCP IP protocol It links many university government and research sites Internet Protocol IP IP is part of the TCP IP suite It is a session layer protocol that governs packet forwarding Interoperability Interoperability is the ability of one manufacturer s computer equipment to operate alongside communicate with and exchange information with another vendor s dissimilar computer equipment Leased line A leased line is a transmission line reserved by a communications carrier for the private use of a customer Examples of leased line services are 56 Kbps or T 1 lines Local Area Network LAN A LAN is a group of computers each equipped with the appropriate network adapter card and software and connected by a cable that share applications data and peripherals All connections are made by cable or wireless media but a LAN does not use telephone services It typically spans a single building or campus LUI Local User Interface Network A network is a system of computers hardware and software that is connected over which data files and messages can be transmitted Networks may be local or wide area Open Systems In open systems no sin
75. emain until the next power cycle at which time the value in the configuration file will be used Low Limit These parameters can be used to define a i Nm range of offsets that are affected by this Positive integer O High Limit command The save value enables or disables making the change permanent f yes the value will be stored and used next Save time on start up as the Node ID If no Yes No 7 1 3 Examples 7 1 3 1 Example 1 Dynamic Allocation of Node ID The parameter value is taken from the specified Data Array and Data Array Offset and is used to modify the parameter specified under Function of the object e g Node specified under Descriptor_Name subject to the limits set by Low_Limit and High_Limit In this example when the value of Node_Array offset 160 is updated presumably by a driver then the FieldServer will check the value is in the range O to 255 inclusive If it is it will look for the Node called PLC_1 If found the Node ID will be changed to the new value Dynamic Parameters Function Change Node ID Descriptor Name BIC Data_Array_Name Node_Array Data_Array_Offset 160 Save Yes Low Limit High_Limit 0 2255 FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manu
76. erval specified The time interval at which the task will be repeated A task name must be specified if Scan Interval i p a scan interval is specified T Defines move functionality e g byte order manipulation Functions are summarized unction in Figure VI The name of a Data Array to be used for conditional moves See Section 5 1 1 3 for Conditional Data Array more information The offset into the Conditional Data Array where the conditional bits for the move Conditional Offset are defined The value found at this specified location must be non zero for the move to be executed If the value is zero the move is inhibited FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 21 of 90 5 1 1 Simple Moves The simplest move involves the transfer of data without any format or protocol changes Whenever the Source Data Array is updated not necessarily changed the Target Data Array will be updated 5 1 1 1 Simple Move Example Data Arrays Move is reversible meaning Data Array Name Data Format Data Array Length data can move from Source DA Float 200 Target_DA to pone if es applicable writeable points Target DA Float 200 Moves Function Source Data Array Source_Offset Target_Data_Array
77. f Da 2 0 so DA 5 0 will contain 50 5 3 4 Optional Parameters TET Legal Parameter Description Values Specifies the number of consecutive source Data Array values from all defined Any Length source Data Arrays egg DAI1 DAI4 to be operated on and to store a result at positive consecutive target locations starting at the respective offsets integer If a task name is specified the move operation becomes a repetitive task on the y Task_Name i Any string FieldServer and the data will be updated on a regular basis Specifies the time interval at which the task will be repeated A task name must Scan Interval qn i m gt 0 1s 2s be specified if a scan interval is specified Truncate This function causes all intermediate and final results to be stored after Y es Result truncating Refer to the example in Section 5 3 4 1 j5 3 4 1 Truncate Result Example Math DAIL DAI2 DAI3 FN1 FN2 DAO DOI1 DOI2 DOI3 DOO Length Truncate Results DA_X DA_17 DA_17 DIV MULT DAZ 0 0 0 0 d Yes If DA 17 0 17 and DA X 0 100 x DA_Z 0 x 17 17 will be 85 NOT 100 FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 36 of 90 5 4 Logic Logic functions implement Boolean functions True False stateme
78. f choice FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 28 of 90 5 2 8 Task Moves If a Task Name is defined the move will become a repetitive task and the data will be updated on a regular basis The time between updates can be set using the Scan Interval parameter If the Scan Interval parameter is set the Task Name parameter must be set If a Task Name is declared but no Scan Interval is defined a default scan interval of 1s is assumed 15 2 8 1 Special Application Node Status The following data array can be configured to capture the status of a Node Refer also to Section 6 1 1 Data Arrays Data Array Name Data Format Data Array Length Data Array Function DA Comm OK Bit 256 Node Status Target DA Bit 200 y Node status bits are only evaluated by the FieldServer when the data is accessed Since the data is only accessed on update the data will be neither accessed nor updated and a move would never occur This can be circumvented by giving the move a Task Name and specifying a Scan Interval Moves Function Source Data Array Source Offset Target Data Array Target Offset Task Name Scan Interval Move Only DA Comm OK 0 Target_DA 40 PLC1 Status 1 FieldServer Technologies 1991 T
79. fset Target Data Array Target Offset Length Join Float Source DA 0 larget DA 40 nb Ten 16 Bit Integers are taken from Source DA and combined in two s to make up 5 floating point values Length refers to the data type referenced in the Function eg If n isthe value shown in Length then Join Float creates n Floats Split Float disassembles n Floats Join Int16 Creates n Integers Bit Extract extracts n Bits etc 5 2 3 Using Moves to pack and unpack bits to or from a Register A register provided by a device often consists of a set of binary values packed together for efficient data transfer These registers are normally 16 bits in size but may also be 8 or 32 bits long Since a register is read as an analog value by most protocols these binary values need to be extracted out of the register into a bit data array before they can be read as useful data The Bit Extract Move function has been created for this purpose The Bit Pack function can be used to pack bits into a register The Bit Move function allows the user the ability to extract a group of bits in one register and place them singly into another register The Bit Offset keyword can be used to start moving a group of bits from a specified offset within the register This keyword may also be used in conjunction with the Bit Extract and Bit Pack functions to specify the first register Offset to Extract or Pack The Length keyword will always specify the nu
80. fsets 1 through 4 DAO output Data Array DOO output Data Array offset FN1 FN4 logic functions 1 4 permitted values ADD SUB MULT DIV GTE LTE GT LT EQ NE SQRT SQ AND OR NOT no setting 5 3 3 Math Usage Example Math Task Name Scan_Interval DAI1 DOI1 DAI2 DOI2 DAI3 DOI3 DAI4 DOI4 FN1 FN2 FN3 FN4 DAO DOO Task 105 1 ADAE EO X03 28 DA3 2 DA4 3 ADD SUB MULT SQRT DA5 21 This definition will result in the following operation DA_5 21 Sqrt DA 1 0 DA 2 1 DA_3 2 DA 4 3 Math Task Name Scan Interval DAI1 DOI1 DAI2 DOI2 DAI3 DOI3 DAI4 DOI4 FN1 FN2 FN3 FN4 DAO DOO Task 105 1 DA 1 0 DA2 1 DA3 2 DA 4 3 Div Sub Mult Sq DAS 21 This definition will result in the following operation DA 5 21 DA_1 0 DA 2 1 DA 3 2 DA 4 3 FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 35 of 90 Math Task Name Scan Interval DAI1 DOI1 DAI2 DOI2 FN1 DAO DOO Task_105 1 DA1 O0 DA2 O0 Per DA5 0 This definition will result in the following operation DA 5 0 DA 1 0 Per DA 2 0 Or DA 5 0 DA 1 0 DA 2 0 100 i e if DA 1 0 10 and DA 2 0 20 then this means Da 1 0 is 5096 o
81. g the numbers following addresses are defined for a mapdesc of module 15 and length 4 15 256 0 15 256 1 15 256 2 15 256 3 Our example event will cause this error message since the greatest address is 15 256 3 3843 and we need an address of 3844 A mapdesc with module 15 and length 5 will store the event ok since 15 256 5 1 15 256 4 3844 Envirotronics SystemsPlus driver The SystemsPlus panel replied with Not i Refer to the SystemsPlus user manual to set up the Monitored when the driver tried to edit read es 11012 alarm for monitoring in the panel This message can scan alarm or tried to read alarm status The i only be solved in the panel and is not a driver problem driver message screen records the specific alarm s name A BACnet Ethernet packet was received on a If BACnet comms fail check the configuration and 11013 network adapter that is not configured in the network connection CSV file Message will be ignored An 802 3 Hot Standby packet was received 11014 on an incorrectly configured network adapter Packet will be discarded 11015 GE SRTP SD016 message indicates NAK error Appendix B 7 Networking Glossary of Terms Term Description 10Base2 is the implementation of the IEEE 802 3 Ethernet standard on thin coaxial cable 10Base2 Thin Ethernet or thinnet as it is commonly called runs at 10Mbps Stations are da
82. gle manufacturer controls specifications for the architecture The specifications are in the public domain and developers can legally write to them Open systems are crucial for interoperability FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 90 of 90 Term Description Packet A packet is a collection of bits comprising data and control information which is sent from one Node to another Packet Switching In packet switching data is segmented into packets and sent across a circuit shared by multiple subscribers As the packet travels over the network switches read the address and route the packet to its proper destination X 25 and frame relay are types of packet switching services Transmission Control Protocol Internet Protocol PFE Protocol Front End Braten A protocol is a standardized set of rules that specify how a conversation is to take place including the format timing sequencing and or error checking A router is a network layer device that connects networks using the same Network Layer protocol for example TCP IP or IPX A router uses a standardized protocol such as RIP to Router move packets efficiently to their destination over an internetwork A router provides greater control
83. h MB8SIM EXE MB8SIM EXE is a program that simulates the FieldServer on the PC and can be used for testing edited configuration files before transferring them back to the FieldServer This file can be obtained by calling Tech Support It is not necessary to use mb8sim The configuration can be loaded into the FieldServer and tested in much the same way e Open an MS DOS prompt and navigate to the directory containing the configuration file e Type mb8sim exe c lt configuration file gt where configuration file gt is the name of the file to be tested For example to test the CONFIG CSV file type mb8sim cconfig csv To test specific sections of a configuration file it is possible to ignore certain sections e To ignore a block use the ignore keyword at the start and the process keyword at the end of the block e To ignore individual lines use e The end keyword will stop processing the file and anything after this keyword will be ignored The following is an example of the interface when using MB8SIM EXE It looks very similar to the interface when using RUINET FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 14 of 90 c Command Prompt mb8sim cconfig csv q Main Menu Download Configuration to Fiel Upload Configuration fro
84. he table In the example below a combination of 4 values in a Tokens Data Array shows the status The FieldServer can perform match pattern arithmetic and store the status as a single number 0 thru 8 Data Arrays Data Array Name Data Format Data Array Length Tokens Status Byte 4 Int pal Consider the following combinations of 4 values here is a wildcard The token starting with the wildcard will not be compared Data Array Values Status Description Status Value for Device 37 46 46 20 Good 0 36 20 Channel disabled 1 45 20 Fault indicated2 2 T 43 20 Fault aeration indicated 3 i i 45 20 Spacing indicator 4 d 43 20 Zeromatc channel fault 5 aj 42 20 Empty Pipe 6 E ie 37 20 hi lo flowrate 7 00 00 00 00 comm Error 8 None of the above 111 FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 30 of 90 152 91 Table of Patterns Configuration example Section Title Offset Table Column Title Function Legal Values Offset Table Name Provide name for Offset Table Up to 32 alphanumeric characters A unique value that will be stored if the pattern Table Index Value 1 16 matches The pattern is
85. hnologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 41 of 90 5 6 6 Example 3 Load a Value Negative Numbers Only SINT16 SINT32 and FLOAT formatted Data Arrays can store negative numbers The Preload Data Format must also be specified with one of those formats Preload Data Format must be cast so that the sign is preserved and then stored in a Data Array whose format can support negative numbers Data Arrays Data Array Name Data Format Data Array Length DA 1 FLOAT 20 Preloads Data Array Name Preload Data Value Preload Data Format Preload Data Index DA 1 1 FLOAT 0 5 6 7 Example 4 Load a Value Floating Point Numbers Only FLOAT formatted Data Arrays can store floating point numbers The Preload Data Format must also be specified with FLOAT In this example the value 123 456 is stored to the 11th element index 10 of the Data Array called DA 1 Data Arrays Data Array Name Data Format Data Array Length DA 1 FLOAT 20 Preloads Data Array Name Preload Data Value Preload Data Format Preload Data Index DA 1 123 456 FLOAT 10 5 6 8 Example 5 Load a Value Strings 1 Strings can be stored in Data Arrays of any format If the Data Array format is UINT32 or SINT32 then the kernel
86. iderations 5 6 4 Example 1 Lood d Value aid eii re oe etude coe n adeat ve nter oo dona dent 5 6 5 Example 2 Load a Value Effect of Target Data Array Format sess essen 5 6 6 Example 3 Load a Value Negative Numbers sscccccccceseessssseeseceseessaascesecsseessaaecesecssseseaaseeseesseenes 5 6 7 Example 4 Load a Value Floating Point Numbers esses nhan noncnnnnnnns 5 6 8 Example 5 Load a Value Strings 1 ccccccccsssccceesssceceesceceesececeessssecsesseceessssecsesseseceessessesseecsesssseensaes 5 6 9 Example 6 Load a Value Strings 2 ccccccccsssscceessssecessceceesssseceesseseceesseseessssecsessssecessessesseeesesseseensaes 5 6 10 Example 7 Load a value Casting sessi essen esee enn tn nennen enn th asas assess saa a asas sess sa conos 5 6 11 X Example 8 Load an Object name esses sensn nnne enn rh anas sse n sa rh daas ss sse sa sa daas ss sse sa dada 5 7 Loading Data Array Values from the FieldServer s Non Volatile Memory 6 Node Management iere erret e etas eee esses pues ees veee E E NER E 6 1 Data Array FUNCTIONS iion d Ee xe EE ERE ERU Y eR ER ERR ERE REQUE Ye Pe Aa anales andara 6 1 1 Node Status Function 6 1 2 Alias Node ID o tede ere ree e eere ee ee ES ee ee eee aae o aae a eu eo Eee a vo eee d 6 1 3 Alias Node ID Example 6 1 4 Node Online BS tt Pd ehe Ee evades 6 2 Connection Parameters 6 2 1 Node Retire Delay 6 3
87. illustrated in the diagram below Remote Client Browse for nodes devices and then browse for points Finds node device as configured in config csv static Server Side Client Side Polls for Data Remote Server Device It is possible to control the Node ID of the Server Node by including a special task in the Configuration file that watches the value of a single element of a Data Array When the value is updated then this task takes the value and replaces the Node ID of a designated Node so that its new Node ID is the value found in the Data Array This is illustrated in the following diagram This new Node ID can be saved to the Non Volatile Memory so that it isn t lost on a power cycle When the device starts up again the stored value will be used FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 49 of 90 7 1 1 2 Remote Client finds a Node with Node ID dependent on the data read from the remote Server device Server Side Client Side Remote Server Device Server Side Node initially takes Node ID from configuration file Polls for Data Response data contains Server Side Node ID Response unpacked and stored in Data Array A specially configured task use
88. in the sense that the driver does nothing while the timeout timer is counting up to its setpoint Once there is a timeout on one Node the driver will not retry any Map Descriptors on that Node until the Retry Interval has expired Thus during the Retry Interval the other Node will get 10096 of the service FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual FieldServer Timeout HE NN Retry interval Probation Delay Server Device Status Node Online Retries P is et ees Se Status Node Offline X lS Sa Status Node Online Figure VIII FieldServer Timing Diagram Page 56 of 90 FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 57 of 90 9 1 Line Drive Parameters The RS 485 communications connection requires that line drive is asserted before sending a message When the message is sent the line drive must be turned off to allow other devices on the network to assert their line drives Because the assertion and de assertion of the line drive is not instantaneous some time needs to be allowed between as
89. isy chained and the maximum segment length is 200 meters 10Base5 is the implementation of the IEEE 802 3 Ethernet standard on thick coaxial cable 10Base5 Thick or standard Ethernet as it is commonly called runs at 10Mbps It uses bus topology and the maximum segment length is 500 meters 10BaseT is the implementation of the IEEE 802 3 Ethernet standard on unshielded 10BaseT twisted pair wiring It uses star topology with stations directly connected to a multi port hub It runs at 10Mbps and has a maximum segment length of 100 meters FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 89 of 90 Term Description 802 3 This IEEE standard governs the Carrier Sense Multiple Access Collision Detection CSMA CD networks which are more commonly called Ethernet 802 3 networks operate at varying speeds and over different cable types See 10Base2 10Base5 and 10BaseT Arcnet Datapoint designed this 2 5 Mbps token passing star wired network in the 1970s Its low cost and high reliability can make it useful to companies on a tight network budget although not endorsed by any IEEE committee ArcnetPlus is a proprietary product of Datapoint that runs at 20 Mbps Bandwidth Bandwidth is the amount of data that can be transm
90. itted over a channel measured in bits per second For example Ethernet has a 10Mbps bandwidth and FDDI has a 100 Mbps bandwidth Actual throughput may be different than the theoretical bandwidth FieldServer A FieldServer connects two networks of the same access method for example Ethernet to Ethernet or Token Ring to Token Ring A FieldServer works at the OSI s Media Access Layer and is transparent to upper layer devices and protocols FieldServers operate by filtering packets according to their destination addresses Most FieldServers automatically learn where these addresses are located and thus are called learning FieldServers Ethernet Ethernet is a 10Mbps CSMA CD network that runs over thick coax thin coax twisted pair and fiber optic cable A thick coax Ethernet uses a bus topology A thin coax Ethernet uses a daisy chain topology A fiber Ethernet is point to point DIX or Blue Book Ethernet is the name of the Digital Equipment Corp Intel and Xerox specification 8802 3 is the ISO s specification Gateway In OSI terminology a gateway is a hardware and software device that connects two dissimilar systems such as a LAN and a mainframe It operates at the fourth through seventh layers of the OSI model In Internet terminology a gateway is another name for a router Hub A concentrator is a hub repeater or concentrator that brings together the connections from multiple network Nodes Hubs have moved past th
91. l functions Mathematical functions implement subset of math functions of Data Array values Some single operator functions can be incorporated into Moves but Multi operator operand functions must be defined in the Math block The length of the move defines the number of input operands The following table shows the Mathematics functions and their text representation Operator csv Mathematics Notes text Operator ADD SUB All operands are combined and a single output is produced for n length MULT of input values DIV GTE gt Each move works as follows ITE value of DA SDA1 offsetO MathOperator value of DA SDA1 offset1 Result is stored in DA TDA offset GT gt e g for GTE LT lt valuel DA SDA1 0 value2 DA SDA1 1 EQ E if value1 GTE value2 1 will be stored at DA TDA 10 else O will be stored The length parameter is always 1 as only one operation can be performed NE l per move SQ Square n outputs are produced for n length values stored in sequence starting SQRT Square root at the Target Offset PER For 2 values A and B result of A PER B will be A B 100 which will be stored in the target Data Array 5 3 1 Math Function as a Moves Function Example Moves Function Source Data Array Source Offset Target_Data_Array Target Offset Length ADD DA_SDA1 0 DA_TDA 0 10 SUB DA_SDA1 0 DA_TDA 10 10 MULT DA_SDA1
92. m Field Ces Figure III MB8SIM Interface Screen Check all screens to see if the file is working correctly paying particular attention to the Error screen From the main menu press E to enter the error display screen and examine the errors listed refer to Figure IV Take note of System Errors or Configuration Errors These indicate configuration problems in the configuration file Note a number of System Overrun errors may occur in this screen They are caused as a result of the simulation and will not cause any problems on the FieldServer Command Prompt mb8sim cconfig csv System Errors tup at Tue Dec 17 04 48 2003 A HAuwpwn Pp None of these messages are errors Config and system errors will have a banner saying System Error or Configuration Error b p rFEPBFEE EFBFBF Mo Figure IV MB8SIM Error Screen with Driver Versions When the file is free from errors with the exception of System Overrun Errors download it using the D command from the main menu of the Remote User Interface FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 15 of 90 3 4 1 Additional worthwhile MB8SIM checks e Check the Connections defined to ensure that they are as expected e Do the same for Nodes e Check the Da
93. mber of bits to be moved in the move operation when using these three functions If the length keyword is not used then only one bit will be moved Note The Data Array Type being used in source and target Data Arrays can produce varying results and care should be taken to use the correct type For example when using the Bit Extract function it makes sense to use Byte Ulnt16 or Uint32 source Data Array Types to extract 8 16 or 32 bits per register respectively It also makes sense to use the Bit Data Type for target Data Array Type However the FieldServer will allow other types to be used and follow a routine choice of conversion that may not be considered predictable to all users For example if the Float Data Type is used as a source type in Bit Extract 32 bits per register will be extracted according to the rounded Integer number being represented in the Float Register If the Float Data Type was used as a target type in Bit Extract then each float register would store one binary value and would only ever represent 1 or O FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 25 of 90 Parameter Function The function extracts bits out of the source Data Array Registers at the Data Array offset specified Bit Extract Th
94. ment and for their duration prevent reception of data Squelch Timer Tx starts at the end of a transmission as defined by RTS becoming inactive and Squelch Timer Rx starts at the end of a valid received message as determined by the protocol driver Note that the Squelch Timer Rx is only relevant to Servers as Clients will in any event disregard any spurious data received after a response SaL RTS l l Master GY 77 TX J I I l E Legend Line drive on We O Une dive 2 Line drive off S Squelch timer TX 5299 3 Squelch_timer_RX 255 Turnaround delay Poll delay l l l l RX I I t t T l l l I l I 8 l l l I l I O Squelch received by master after poll l Lo Deleted by Squelch_timer_TX i i i l Squelch received by master after I I hid id response l 4 ll Deleted by Kernel before next poll i Squelch received by slave after poll I Deleted by Squelch_timer_RX RTS l l Squelch received by slave after l I l Fog response l Deleted by Squelch timer TX TX l EE Slave t i i 1 T l l I I l l l b I i RX y T i I Q9 y I l l Figure IX Timing Diagram Line Drive On Off Tx and Rx Squelch Poll Delay Turnaround Delay Note Squelch_Timer_Tx and Squelch_Timer_Rx are not supported in the FS X30 Series 9 2 1 Setting Parameter Values It is important to pre
95. n off transitions then the Server can be configured to handle writes in a blocking mode Here successive writes to the same point are queued to a configurable maximum length Writes are accepted from the Client until the queue is full at which point further writes will be rejected This option must be configured on the Server using the following Connection parameters and values Column Title Function Legal Values Mode for dealing with potential accumulation of successive writes to Overwrite Write Queue Mode the same point can be configured Blocking The length of the queue can be configured if blocking mode is set Blocking will occur when there is no more space on the Write Queue Non negative Write Queue Size M If size 0 every successive write is blocked A message will be displayed integer 0 when blocking occurs except if the Queue Size 0 Connections Port Baud Parity Data Bits Stop Bits Protocol Handshaking Poll Delay Write Queue Mode Write Queue Size Timeout P1 9600 None 8 Xd Modbus RTU None 0 100s Blocking n5 8s 8 6 Port Expansion Configuration The example configuration file for this mode is available from FieldServer Technical Support if needed Although Map Descriptor configuration is not required Connections and Nodes do need to be configured Connection Port Protocol Server Hold Timeout P1 mb rtu 12 P2 mb r
96. nterval parameter FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 19 of 90 4 3 5 Active Read on Trigger ART This function is used to effect a single data read per trigger An example from the Envirotronics Driver is presented below Client Side Map Descriptors Map Descriptor Map Descriptor Name Data_Array_Name Data Array Offset Function Node Name SysPlus_Cmd Store Data Array Name Store Data Array Offset Length Ed Rd Program Rd Triggers 0 Art SYSPLUS O1 Ed Rd Program Ed Rd Program 0 nl This command is triggered by writing any value to Data Array Name at Data Array Offset The retrieved data is stored as follows Offset from Store Data Array Offset Description 0 Program number 4 3 6 Active Write on Trigger AWT This function is used to effect a single data write per trigger As with the Wrbx function the write only occurs when the Data Array is updated In this case the updated data is not used to form the write but updating the Data Array triggers a read of a Secondary Data Array which contains the data to be served in the write In the example below from the Lutron eLumen Driver the driver watches the Data Array called Lut triggers offset 13 If that Data Array elemen
97. nts of bit Data Array values Single operator logic can be incorporated into Moves but Multi operator operand logic must be defined in the Logic block 5 4 1 Logic as a Moves Function The length of the Move defines the number of input operands For binary operators AND OR all operands are combined and a single output is produced For the unary operator NOT an output is produced for every input and is stored in sequence starting at the output location 5 4 2 Standalone Logic The logic definition allows up to four source data locations up to four logic operations and one output data location Operands are kept on a stack and are operated on in the sequence in which they have been defined Logic functions consume 1 or 2 stack variables as inputs 2 for AND OR and 1 for NOT and leave the output on the stack ready to be used by the next defined logic operation The output of each operation becomes an input to the next operation along with the next defined operand Fields Specific to the Logic Definition DAI1 DAI4 input Data Arrays 1 through 4 DOI1 DOI4 input Data Array offsets 1 through 4 DAO output Data Array DOO output Data Array offset FN1 FN4 logic functions 1 4 permitted values And Or Not no setting 5 4 2 1 Logic Usage Example Logic Task Name Scan_Interval DAI1 DOI1 DAI2 DOI2 DAI3 DOI3 DAI4 DOI4 FN1 FN2 FN3 FN4 DAO DOO Task_105 pal UA1 0 D
98. ode Appendix B 4 6 Map DescFIDtOrs iu d e eie a debe de A en end eo pe ede Aida wee de dees Appendix B 5 Valid Characters for Common Fields in Configuration Files Appendix B 6 Kernel Error Messages and Descriptions Appendix B 7 Networking Glossary of Terms cccssssccccecessessscecececseseeseesececeeseseeaeseeecesseseaaeseesceceeseaaeseesesceeeaaeas FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 6 of 90 1 FIELDSERVER CONCEPTS 1 1 Introduction The FieldServer functions as a gateway enabling different devices utilizing different protocols to interface with each other The FieldServer solves communication and protocol conversion problems and improves response times in distributed data acquisition and control systems The extensive driver library available from FieldServer Technologies provides a wide range of interoperability solutions For a current list of available drivers visit our website at www fieldserver com The FieldServer also acts as an Ethernet gateway enabling new and legacy PLCs RTUs and SCADA devices to link to Ethernet for plant wide communications Depending on the model the FieldServer is equipped with combinations of Serial Ethernet and LonWorks ports as well as various Fieldbus ports The internal poll block
99. ode ID Set from DA Node s not found While trying to change the Node ID the FieldServer could not find a Node whose name matches the task s Descriptor Name parameter 9 DynParam 4 Err Node ID Validation failed Lo ld Hi ld Rqd d Node s The Node ID was not changed because the dynamic value extracted from a DA did not satisfy the validation Check that the devices have been correctly configured Possibly mapping of DA and offset need adjustment DynParam 5 FYI Node s This message is printed each time the Node ID is successfully updated failed Lo ld Hi ld Rqd 9 6d Node s Id d changed to 96d dynamically You may ignore this message if it confirms your expectations s d DA off This message is printed when evaluating a Dynamic parameters task where the DynParam 6 Err function Change System Node ID or Change System MAC Add The DescName s too long maximum length of the descriptor is 32 characters 9 DynParam 7 Err The value extracted from the DA to be used as a dynamic parameter is out of System Node Id Validtn range based on the low and high values specified Review the validation range in the configuration file and also review your mapping Perhaps the DA offset does not contain the new ID DynParam 8 FYI Bridge s d Id d changed to d s d DA off This is confirmation of a change of a symnica parameter where the function is Change System Nod
100. of per Map Descriptor statistics This is done by adding the MD Option parameter to the Map Descriptor section and setting the value to No Stats for each Map Descriptor If a specific Map Descriptor is to be monitored then this setting can be omitted for that Map Descriptor Setting the No Stats option on a Map Descriptor will disable the display of statistics for that Map Descriptor in RUInet and will cause zero values to be reflected for all statistics relating to that Map Descriptor in RUldebug logs Statistics on the Node and Connection are not affected Example This example will disable statistics on SMD 11 AI 01 but not on SMD 11 MI O2 Map Descriptors Map Descriptor Name Data Array Name Data Array Offset Function Node Name Object Type Object Instance MD Option SMD 11 AI 01 UDA AI 01 0 Passive Virtual Dev 11 Al 01 No Stats SMD 11 MI 02 DA AI 01 yd Passive Virtual_Dev_11 MI 02 n FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 73 of 90 Appendix B Reference Appendix B 1 Working with the Driver Manuals Appendix B 1 1 Introduction The purpose of the Driver Manual is to provide driver specific configuration information When drivers are installed in the FieldServer the specific combination is assigne
101. on burst causing spurious data to be received at either end The FieldServer kernel implements a user configurable timing sequence designed to suppress the reception of this spurious data When the transmission ceases and releases the channel noise can be generated at both the transmitting and receiving end In a master slave situation using poll and response messages this leads to four possible instances of squelch generation e Squelch received by the master at the end of a master to slave poll transmission e Squelch received by the slave at the end of a slave to master response transmission e Squelch received by the slave at the end of a master to slave poll transmission e Squelch received by the master at the end of a slave to master response transmission The first two are examples of what is termed TX squelch received by the transmitting port at the end of a message the last two are examples of RX squelch received by the receiving port at the end of a message The timing diagram illustrates the four instances of squelch and identifies time intervals controlled by two connection parameters i e Squelch Timer Tx and Squelch Timer Rx These timers are activated at the FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 58 of 90 appropriate mo
102. onitor the health of the communications path for that point if the associated protocol allows for this Specifying a passive function will mean that the FieldServer expects the communications for that point to be controlled and monitored by another device on the associated network Note By design it is necessary that all active Map Descriptors communicate to a point that has a passive mapping on the remote device and that passive Map Descriptors are controlled by an active mapping on the remote device There is a loose relationship between Active Passive and Client Server Clients usually use active mappings and Servers usually use passive mappings however Active Servers and Passive Clients do exist Points that send an update to a network on change e g Alarm panels are a good example of Active Servers Another set of terminology used in this area is solicited vs unsolicited messages A Client receives a solicited message from a Server when it asks for it i e the point is polled A Client receives an unsolicited message from a Server when the Server sends the point without the Client asking for it Clients that send solicited messages are Active Clients communicating with Passive Servers Clients that receive unsolicited messages are Passive Clients communicating with Active Servers 4 2 Passive Map Descriptor Functions 4 2 1 Passive The Passive function will not initiate any communications but waits to be solicited by a remote devic
103. or managing passive communications but the following steps are typically required to change the Active Client side of a configuration file to make it a Passive Client e Remove Adapter Port to Client side Node e Change Function from Rdbc to Passive e Remove Scan_Interval e Change Node ID to remote device s target Device ID If the Server side remains passive then every Map Descriptor should have Passive as its function Consequently the Server device will write data to the FieldServer s Data Arrays and the Client device will read that data from the same Data Arrays making the operation of the FieldServer much like that of a normal data Server on an office network FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 18 of 90 4 3 Active Map Descriptor Functions A Responsible Map Descriptor is a Map Descriptor that inherently monitors the quality of the data that it is mapping and can be recognized by the Function parameter field The following are all Responsible Map Descriptors 4 3 1 Read Block Continuous Rdbc The Rdbc function will read a block of data of length specified by the length parameter and transfer that data to the Data Array specified Reads are performed continuously at an interval specified by the Scan Interval parameter
104. otocol in the configuration file Obtain 10034 file but the required driver is not loaded in the correct DCC the firmware CB8MENU The FieldServer did not respond due to a Data 10038 Array Age time exceeding the Cache Age time Increase Cache Age setting in the configuration file limit There was a message overrun on Modbus TCP slave driver The Client is polling too often for 10039 the FieldServer to respond and there is more than one message in the in buffer There m Increase the timeout on the Client device should be overrun statistics on the Server Connection in question Same as 10039 except the overrun is more 10040 than two messages Invalid move function specified in 10041 Fix the configuration error configuration file or move not defined 10042 High and Low Scaling values are equal Move overruns Data Array This usually means 10045 that the offset PLUS the length of the Move command is larger than the length of the Data Actions Check Data Array Length Array Check Move settings Move Offset lies outside the Data Array This Target Offset Source Offset Client Offset 10046 usually means that the offset of the Move Server Offset Feedback Offset Mode Offset Length command is larger than the length of the Data Array 10047 Could not find Source Data Array for Move Make sure that the specified Data Array exists before 10048 Could not find Target Data Array for Move specifying move
105. ousekeeping function and will not affect any process control operation FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 70 of 90 Appendix A Useful Features Appendix A 1 Using comments Configuration file comments are lines starting with Use this format to comment on the line Nodes Node Name Node ID Protocol Main building Node Test A 1 Modbus RTU Never place comments in the middle or at the end of lines e g this is NOT allowed Nodes Node Name Node ID Protocol Test A 1 Modbus RTU Main building Node Appendix A 2 Using conditional process statements The Client or Server sides of a configuration can be disabled using the following keywords Keyword Function Ignore all lines will be ignored after this statement until a process statement is encountered Process causes lines after this statement to be processed again End configuration stops here ignoring all further lines Appendix A 2 1 Disabling the Client side of a configuration Set up the Modbus Server side Data_Arrays Data Array Name Data Format Data Array Length DA DO 01 Bit 1 Connections Port Baud Parity Data Bits Stop Bits Protocol P1 9600 None 8 1 Modbus_RTU Nodes Node Name Node_ID
106. over paths and greater security than a FieldServer however it is more difficult to set up and maintain RUI Remote User Interface A Server is a computer that provides shared resources to network users A Server typically Server has greater CPU power number of CPUs memory cache disk storage and power supplies than a computer that is used as a single user workstation SUI System User Interface TCP IP TCP IP is the protocol suite developed by the Advanced Research Projects Agency ARPA and is almost exclusively used on the Internet It is also widely used in corporate internetworks because of its superior design for WANs TCP governs how packets are sequenced for transmission IP provides a connectionless datagram service TCP IP is often used to generically refer to the entire suite of related protocols Wide Area Network WAN A WAN consists of multiple LANs that are tied together via telephone services and or fiber optic cabling WANs may span a city state a country or even the world Wireless LAN A wireless LAN does not use cable but rather radio or infrared to transmit packets through the air Radio frequency RF and infrared are the most common types of wireless transmission FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com
107. plication Creating a LonWorks SNVT_Switch from 2 Modbus registers LonWorks Server Map Descriptor FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual 5 2 It is often necessary to manipulate incoming data to create the necessary outgoing data by either joining smaller data types to create a larger data type or splitting larger data types to deliver smaller data types An example of this is Modbus where two 16 bit registers are used to transfer a 32 bit floating point value Upon receipt of these two registers the FieldServer needs to join the integers to extract the floating point value The Type Casting Function Moves Type Casting moves described below perform these kinds of operations 5 2 1 Functions Available For Type Casting Join Float Split Float Join Int16 Split Int16 Join Int32 Split Int32 e Swapped versions of the above Big Endian vs Little Endian e Bit Extract Bit Pack Bit Move The following legacy functions have been replaced by the functions listed above They are simply presented in the table below for reverse compatibility Old Keyword New Keyword Function Performed Int32 Join 2 116 1 132 Join_Int32_Swapped source bytes ab cd target bytes abcd 2 116 1 132 sw Join Int32 sourc
108. quential errors must occur before marking a data buffer and poll block bad and marking a device offline The FieldServer will poll the device and if it receives no Count Retries response will retry polling the device the number of times Default 3 Retry Interval Interval between retries Interval in Seconds Srv Offline Method A Server Node could send contradictory information if its data comes from multiple Client Nodes some of which are offline and others online causing it to respond differently depending on what data is polled This confuses some systems This setting allows the user to select whether the Server Node should appear online or offline if there is a mix of Client Node Statuses Ignore Clients causes the Server to behave explicitly not to depend on the status of the Client Node but on the data validity only i e non expired data will be served whether or not the responsible Client Nodes are online Any Offline suppress a data response if ANY of the responsible Client Nodes for the data range concerned are offline All Offline only suppress a data response if ALL of the responsible Client Nodes for the data range concerned are offline Always Respond overrides the data validity as well i e it forces the Server Node to regard data as valid even if the Client Node is offline or the data has expired Ignore Clients Any Offline All Offline Always Respond Write Ack Option Ack Comple
109. r and timing of the write retries is then governed by the Retries and Retry Interval parameters Warning ensure that repeated writes are safe for your application since a Write may be retried because of a transmission error in the Write acknowledgement in which case the remote device will see two similar write requests Yes No Node Offline Action If this parameter is defined when a Client Node goes offline all Data Array values of Map Descriptors defined on this Node will be set to zero Clear Data Array No Action FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 80 of 90 Appendix B 4 6 Map Descriptors Section Title Map Descriptors Column Title Function Legal Values Map Descriptor Name Name of the Map Descriptor Up to 32 Alpha Numeric Characters Data Array Name DA Name Name of Data Array where data is to be stored in the FieldServer One of the Data Array names as defined in Appendix B 4 2 Data Array Offset Starting Location of Data Array O to Data Array Length 1 as defined in Appendix B 4 2 Rdbc Read data buffer continuously Wrbc Write data buffer Function Function of Client Map Descriptor continuously Rdb Read data buffer once Wrb
110. r over virtual Ethernet connection External Data Transfer over physical Ethernet connection X Bad Data X Bad Connection Physical Hot Standby FieldServer 2 with two Virtual FieldServers Figure XII Diagram Showing Data Integrity achieved using Virtual FieldServer Concept even with cable failures and bad data Mode 2 Hot Standby introduces the following new concepts to FieldServer configuration Single Port Server Dual Port Server Tiers SCADA and PEX Keepalive Map Descriptors Server Name FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com Page 63 of 90 FieldServer Configuration Manual Page 64 of 90 10 3 1 Single Port Server Most devices information Servers that wait to be polled for data are only capable of communicating with one Master device through one port at any time The method employed by FieldServer to achieve redundancy with these devices is depicted in Figure XIII ETHERNET Passive FieldServer ETE Ribbon cables FS 8915 16 transfer hardwired ports to standby FieldServer Serial Port 1 E g P P Pb PS PA PD o Active FieldServer Figure XIII Single Port Server The RS 232 ports of the two FieldServers are routed via an RS 232 splitter device allowing them to be connecte
111. re established the FieldServer will wait for a period called Probation Delay before marking the Node as online Note 1 The Ic Timeout parameter monitors the time between characters in a response If the time exceeds the Ic Timeout the response is discarded and is considered a Timeout Note 2 All parameters in bold above are configurable See table below for where they are configured and what the defaults will be if they are not configured Refer also to Appendix B 2 Parameter Default Value Where Used Scan Interval 2 seconds Map Descriptor Node Connection Poll Delay 0 05 seconds Connection Timeout 2 seconds Map Descriptor Node Connection Retry Interval 10 seconds Node Retries 3 times Node Recovery Interval 30 seconds Node Probation Delay 1 minute Node Ic Timeout 0 5 seconds Map Descriptor Node Connection Note 4 In the case of parameters that may be declared at the Connection Node or Map Descriptor level when the parameter is declared at more than one level the Map Descriptor declaration takes highest priority followed by the Node declaration and then the Connection declaration Note 5 A non response from the remote Server device causes a Timeout The driver does nothing until a response is received or the timeout period has expired Thus if a connection has two Nodes and one Node is producing Timeouts this will have the effect of slowing down communication for the other Node
112. rob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 11 of 90 The Map Descriptor parameters describe the address details required to move data between the FieldServer and an external device and the nature of the data transfer Client Side Map Descriptors Map_Descriptors Data Array Name Data_Array_Offset Function Node Name Address Length Scan Interval CMD AI 01 DA AI 01 0 Rdbc PLC1 30001 20 1 000s CMD AO 01 DA AO 01 0 Rdbc PLC 1 40001 20 1 000s Map Descriptor Name Map Descriptors Data Array Name Data Array Offset Function Node Name X Address Length Scan Interval CMD DI 01 DA DI 01 0 Rdbc PLC1 10001 20 1 000s CMD DO 01 DA DO 01 Rdbc PLE 00001 Map_Descriptor_Name Node being accessed Name assigned to the Map Descriptor In some protocols the name becomes the variable Data Array to be used for storage of data being passed Determines how data is to name between protocols First point be fetched written The address being Timing FieldServer is either accessed parameters reading being read or A assist with Offset in relevant Data Array to start data writing data This can be access storage i pacing of data continuous or on change
113. s Once this period has expired there will be one further poll and if the Node does not respond within the specified timeout period it will be retired The FieldServer must be restarted for retired or new Nodes to be identified This is an optional parameter If not set the FiledServer will continue retrying indefinitely This would be useful in a situation where there are plans for expansion and some Nodes have not yet been installed and so would never respond Example Connections Port Timeout Node Retire Delay P1 0 2 10 P2 0 2 10 P3 0 2 10 Nodes Node Name Node ID _ Protocol Port Retry Interval Recovery Interval Dev1 EHE Modbus RTU P1 0 0 Dev2 22 Modbus RTU P2 0 0 Dev3 3 Modbus RTU P3 0 0 6 3 Node Parameters 6 3 1 Node Offline Action This function allows the user to clear the values from a Data Array if the associated active connection to a Passive Node is lost By default the last values obtained from the Passive Node will remain in the Data Arrays if the connection is lost This functionality has been implemented for the following protocols BACnet IP BACnet MSTP Lonworks and Metasys N2 A configuration example follows Nodes Node Name Node ID Protocol Port Address Type Node Offline Action PLC 12 7119 Modbus RTU P1 ADU Clear data Array PLC 13 13 Modbus RTU P1 PDU No Action FieldServer Technologies 1991 Tarob Court Milpitas California 95035
114. s the data to change the Node ID of the server node in the FleldServer Remote Client Server Side Client Side Remote Server Device Browse for nodes devices and then browse for points Finds Node ID as updated with data from the remote Server device Polls for Data FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 50 of 90 7 1 2 Map Descriptor Parameters specific to Dynamic Parameters Section Title Map Descriptors Column Title Function Legal Values Change Node ID Function Function of Client Map Descriptor Change System Node ID Change System MAC Addr Descriptor Name Name of the Object that will be affected by the Dynamic Parameter function One of the Node names specified as described in Appendix B 4 5 or the Bridge Title of the FieldServer specified as described in Appendix B 4 1 information Refer to examples below for more Data Array Name Name of Data Array from which the parameter value is taken One of the Data Array Names specified as described under Appendix B 4 2 Data Array Offset Offset into the Data Array from which the parameter value is taken O to Data Array Length 1 as defined in Appendix B 4 2 the change will only r
115. sed on the Node s status Data Arrays Data Array Name Data Format Data Array Length Data Array Function Comm Bits Bit 900 Alias Node Status Nodes Node Name Node ID Alias Node ID Protocol Port Retry Interval Recovery Interval N1 pal pe Modbus RTU P1 0 1s 0 1s N3 pal 300 Modbus RTU P2 0 1s 0 1s Alias Node Status differs from Node Status as follows e fa Node does not have an Alias Node ID defined then that Node s status will not be reflected in the Data Array e The Alias Node ID s can be any positive whole number including zero up to the limit of the maximum Data Array size FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 46 of 90 6 1 4 Node Online Bits This Data Array function allows the user to specify Nodes and Subnets for which communication status is required Example Typical Data Array Parameters are Section Title Data Arrays Up to Data Array Name Provide name for Data Array alphanumeric characters Data Format Provides Data format If specified this allows the user to configure the number Data Array Length 1 to 256 subsequent nodes after the Node_ID Node Online Bits Data Array Function Special function for Data Array None If configured the Node a
116. serting the line drive and sending the message as well as between the end of the message and de asserting the line drive This time is specified by the Line Drive On and Line Drive Off parameters If R1 or R2 are declared as ports in the configuration file then Line Drive On and Line Drive Off are set to 1ms by default and need not be declared in the connection parameters unless the application requires that the line drive times are adjusted If Line Drive times are set incorrectly truncated messages and noise occur If the time set is too long it could truncate a message from another device If the time set is too short the FieldServer s message will be truncated For P1 P8 RS 232 the Line Drive parameters default to O Line Drive is implemented on FieldServers using the RTS Request to send line on the RS 232 connection Example Client Side Connections Connections Port Baud Parity Data Bits Stop Bits Protocol Poll Delay Line drive on Line drive off P8 9600 None 8 pal Modbus RTU 0 100s 0 001s 0 001s Note 1 Line Drive On and Line Drive Off are not supported in the FS X30 Series Note 2 Handshaking is not supported The RTS line can be enabled by specifying Line Drive On and Line Drive Off as non zero values 9 2 Suppressing Squelch on Half Duplex Communications Many half duplex serial communication channels generate noise when the channel switches direction typically at the end of a transmissi
117. st be filled in with a valid Data Array name 11009 The requested number of events or auxs to set is Envirotronics SystemsPlus driver more than set up in the parameter Data Array Reduce number of events or auxs or increase parameter Data Array length 11010 Siemens Cerberus driver The counts Data Array has less than 14 data elements per panel and event countds could not be stored Increase the number of data elements in the counts Data Array to 14 elements per panel FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 88 of 90 Error Description Action Use the event s panel module and device numbers to define a Map Descriptor with Node Name panel e g For message DRIVER CER No mapdesc for panel 2 module 15 device 4 Create a mapdesc that will map to an address of15 256 4 3844 since there are always 256 Siemens Cerberus driver The Client driver devices per module for Cerberus The mapdesc field could not find a suitable Map Descriptor to block number represents the Cerberus module 11011 store the incoming event The error message number A Cerberus mapdesc maps to addresses from reported the event s panel module and device module 256 0 to module 256 length 1 e
118. t any time The FieldServer thus acts as a Client and a Server simultaneously Client Node i Data Hghway Aus Virtual Server Nodes Server Server Map Descriptors Side SS AAA st Data Arrays j f z Location Client Map Descriptors Client Side Client Node Descriptors Server Node Modbus Figure II FieldServer Operation Theory Example Consider a Modbus PLC with a set of 10 high alarms in address 00001 to 00010 A Map Descriptor is allocated to fetch Data Objects from Modbus address 00001 length 10 and save this data to a Data Array named PLC1 offset 20 The high alarm for sensor number 5 on PLC1 is thus stored in Data Array PLC1 offset 24 the fifth location starting at offset 20 A DCS using Allen Bradley DH protocol can be configured to access the FieldServer and read the Data Array The FieldServer will appear to the DCS as another DH PLC If the Virtual Node PLC1 is configured to contain the data on sensor 5 PLC1 as a DH address B3 57 then the data needed for address B3 57 will be retrieved from Data Array PLC1 offset 24 FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 9 of 90 3 GETTING STARTED BASIC CONFIGURATION 3 1 Configuration File Overview The default driver configuration
119. t fieldserver com FieldServer Configuration Manual Page 68 of 90 Notes 1 ThePrimary fieldServers 1 amp 2 each have 2 virtual FieldServers within them referred to as e Virtual FieldServer on Tier 1 or SCADA Tier virtual FieldServer e Virtual FieldServer on Tier 2 or PEX Tier Virtual FieldServer 2 The PEX Tier virtual FieldServers are connected to the Main PLCs via P1 to P6 3 The Information Clients receive ALL the data via the R1 connection ports on the SCADA Tier virtual FieldServers 4 The SCADA Tier virtual FieldServers are not connected directly to any PLCs These virtual FieldServers get all their data from either the PEX Tier virtual FieldServers or from the physical FieldServers 3 amp 4 5 The SCADA Tier virtual FieldServer 1 normally gets its data from PEX Tier virtual FieldServer 1 via virtual network connection VN AND from physical FieldServer 3 6 If either physical FieldServer 1 fails the information Client will get data from FieldServer 2 7 If either physical FieldServer 3 or 4 fails then the FieldServer 1 or 2 SCADA virtual tier will get data from the other auxilary physical FieldServer 8 If the FieldServer1 SCADA Tier virtual FieldServer cannot get data from FieldServer 1 PEX Tier virtual FieldServer via virtual network connection VN it will get the data from FieldServer 2 PEX Tier virtual FieldServer via physical network connections N1 or N2 Thus if a serial cable on FieldServer 1 is disconnected
120. t in the array represents one integer bit Integer SInt32 Signed 32 bit Range 2147483648 to 2147483647 discrete Each point in the array represents one Integer integer Uint32 Unsigned 32 o bre int Range 0 to 4294967295 discrete Each point in the array represents one integer it Integer In transferring data points from one protocol to another via the Data Arrays in the FieldServer the integrity of the data format is retained E g if a point representing a bit data type is transferred into a Data Array of type Float the value will be a 32 bit floating point value that will only take on the values of 0 and 1 If this is transferred to an integer point in another protocol the value will still only ever take on the values of O and 1 despite the type conversions This can be overcome using Moves refer to Section 5 2 Appendix B 4 Permissible Values for Configuration File Variables Default and acceptable values for the different variables defined in the configuration file Default values are indicated in bold Timing parameters are listed in seconds 0 003 would represent three milliseconds While this list contains acceptable variables for the FieldServer some are not suitable for all configurations depending on the drivers used Please see the Driver Manual for complete information regarding acceptable variable values for specific drivers FieldServer Technologies 1991 Tarob Court Milpitas California 95035 U
121. t is updated even if the value remains unchanged the the write is triggered The driver extracts the data from the Secondary Data Array called Set tlck offset O and forms a message to write this data to the field device Only certain drivers support require the use use of this function For other drivers awt is a synonym for wrbx since there is no secondary Data Array to extract information from Note The driver may extract more data from the array than specified by the length parameter The only way to know how much data is to read that specific driver s manual Map Descriptors Map Descriptor Name Data Array Name Data Array Offset Function Node Name GRAFIK command DA Lut List DA Lut List Offset Length Set tck Lut triggers 13 Awt LUT GRF6 O Set tclk Set tclk 0 5 dl FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 20 of 90 5 DATA MANIPULATION FEATURES The features described in this section may or may not be needed depending on the application where the FieldServer is implemented If the application calls for straight passing of data without modification through the FieldServer then the features in this section will probably not be useful 5 1 Moves The Moves function permits data to be moved from one Data
122. ta Arrays to ensure that all Data Arrays defined are there If too many Data Arrays exist this usually signifies that a spelling error exists in the configuration and that incorrect Data Arrays were specified in the Map Descriptors Note that the first few lines of the error screen are merely informative and relevant information used for fault finding and do not represent errors Errors are shown as System Error or Configuration Error in the error screen FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 16 of 90 4 MAP DESCRIPTOR FUNCTIONS Map Descriptor functions determine how data is mapped between Data Arrays and the corresponding driver data points The choice of function used is critical in ensuring that the right relationship is established with the device being communicated with The most important decision to make when choosing a function is whether the function needs to be active or passive Once this is determined the trigger for initiating communications determines which active or passive function is used 4 1 Active vs Passive functions Active functions control the communications activity for the associated points in the network Specifying an active function for a point will enable the FieldServer to decide when a point is updated and m
123. ta_Format Preload Data Index DA 1 257 FLOAT 0 DA 2 257 BYTE 0 The value 257 will be cast to a byte before it is stored Only numbers in the range 0 255 inclusive can be stored in a BYTE The kernel chops off the part of the number that exceeds the byte and then stores this truncated value in the FLOAT array Thus the value 257 will be stored in the 1st element of DA 1 and the value 1 in the 1st element of DA 2 5 6 11 Example 8 Load an Object name In the example below a Complex Data Object for Analog Outputs is created with 20 objects The preload sets the name of the 1st object index 0 to the string ABCDEFGHIJKLMNOPQRSTUV as well as setting the value of the Present Value field in the object to zero Data Arrays Data Array Name Data Format Data Array Length DA 1 AO 20 Preloads Data Array Name Preload Data Value Preload Data Format Preload Data Index DA 1 ABCDEFGHIJKLMNOPQRSTUV String 0 FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual 5 7 If the value in the Data Array changes the FieldServer can be configured to save this changed value to its Non Volatile Memory up to 3 times a minute using the DA Function After Store Parameter On startup the value will be loa
124. te default the Server waits for the Client Side write transaction to complete before acknowledging the Write request This makes for good reliability but has a cost in terms of throughput Ack Immediate fast but less reliable The Server immediately acknowledges a Write request before queuing the Client Side Write The acknowledgement is thus not affected by the success or failure of the Client Side Write Only recommended if the same points are updated regularly Ack Verified most reliable and slowest The Server waits for a Ack Complete Ack Immediate Ack Verified FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Section Title Nodes Page 79 of 90 Column Title Function Legal Values Client Side Write and Readback to be completed and only updates the data value if a data comparison between the Client Side Write and Read values passes If the transaction fails for any reason or if the data comparison fails the Server responds with a negative acknowledgement Enable Write Retries The default write behavior is for a write operation WRB or WRBX to be attempted once only If a timeout occurs the write operation is aborted If set to yes this parameter enables failed write requests to be retried The numbe
125. the FieldServer watches offset zero of the Data Array called DA NODE ID NEW If it changes and the new number is valid in range then the Bridge section of the configuration file is scanned until a bridge whose Title matches the descriptor name is found Once found the value of the System Node ID is updated and the driver writes the new ID down to the PIC on which the BACnet driver has been implemented The Low Limit and High Limit parameters may be omitted in which case the Node ID is not validated against them The save value enables or disables making the change permanent If Yes the value will be stored and used next time on start up as the System MAC Addr If No the change will only remain until the next power cycle at which time the value in the configuration file will be used FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 52 of 90 7 1 4 Error Messages DescName s too long Message Description DynParam 1 Err Validation impossible Lo f Hi f The low validation value is greater than the high value Desc s This message is printed when evaluating a Dynamic parameters task where the DynParam 2 Err function Change Node ID The maximum length of the descriptor is 32 characters 9 DynParam 3 Err N
126. tu Nodes Node Name Node ID Protocol Port Timeout Write Ack Option Dev1 zd mb rtu P2 12 Ack Immediate FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 55 of 90 9 TIMING PARAMETERS Under normal operation the FieldServer will send a poll request to a Server device and that device will reply with a response The amount of time between successive poll requests is called the Scan Interval The time between receiving a response from a Server device and the next poll request is called the Poll Delay If the FieldServer sends a poll request and the Server device does not send a response it is considered a timeout The time the FieldServer waits before declaring a timeout can be adjusted by the Timeout parameter If a timeout occurs then the FieldServer will retry the poll request number of times retried is specified by the retries parameter The interval between Retries is specified by the Retry Interval The FieldServer will send poll requests at the end of each Retry Interval Once the specified numbers of Retries have been sent the FieldServer will mark the Node offline Once a Node has been marked offline it will wait for a period specified by Recovery Interval before sending another poll request Once the communications have been
127. tus Bits See Section 10 3 8 2 Hot Standby Status Bits See Section 10 3 8 1 Node Detail Stat Dev Detail Stat A Data Array is created to reflect Node details Handle can be set Values are reflected in the following order O Device handle 1 Node port 2 connection 3 old station 4 station Chan Detail Stat Connection information f O First value handle 1 port 2 old port 5 error count Values in Data Array will reflect these values Node Overview Stat Gives overview of all devices configured on the FieldServer Cycles through all the devices on the FieldServer in the order that they are configured Note that the Data Array needs to be long enough to store all device information O Handle 1 station 2 port 3 adapter 4 status 6 old station 10 Historical message count 11 minutes 12 hour 13 day 14 month 15 Historical error count 16 minutes 17 hour 18 day 19 month The next device starts at position 20 and the same structure is repeated Reporting will stop after all the devices have been reported or when the Data Array is full Chan_Overview_Stat Same except O handle 1 port 2 adapter 3 status 8 old port 9 old adapter Thereafter follow Historical message and Error blocks in the same format as above Dev_Error_Rates Reports the number of errors per hour for each Node Location in the Data Array is the station of the devi
128. upport Active Reads and Write Through operations Readback Asynchronously When a write occurs the read will occur when scheduled Readback On Write When a write occurs set the timer to 0 so the Responsible Map Descriptor will get queued in the next cycle Readback Immediately On Write Prioritize both write and read to happen in a higher priority queue than normal reads The Readback operation will apply to all drivers that support Active Reads and Write Through operation Readback Asynchronously Readback On Write Readback Immediately On Write MD Option Setting the No Stats option on a Map Descriptor will disable the display of statistics for that Map Descriptor in RUInet and will cause zero values to be reflected for all statistics relating to that Map Descriptor in RUIdebug logs Refer to Appendix A 3 No Stats Appendix B 5 Valid Characters for Common Fields in Configuration Files ASCII Code Char Comment ASCII Code Char Comment 32 space 82 R 33 83 S 35 84 T 36 85 U 38 amp 39 86 V 40 87 Ww 41 88 X 42 89 Y 43 90 Z 45 z 91 46 92 47 93 48 0 94 A 49 1 95 underscore 50 2 96 51 3 97 a 52 4 98 b 53 5 99 C 54 6 100 d FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free
129. uration Manual Page 13 of 90 3 3 Editing Configuration Files The configuration file is in comma delimited format where entries within a line are separated by commas and the end of a line is indicated by an entry without a comma This file can be edited using spreadsheet programs or any text editor It is recommended that the CONFIG CSV file be backed up before editing Once edited the file can be sent back to the FieldServer using the D command in the Remote User Interface Refer to Appendix B 4 for the parameters that are usually filled out in the configuration file Only the specified values may be used other values may affect FieldServer performance or functioning Not all parameters are compulsory for every driver See the related driver manual for details The bold legal value is the value that will be used if the parameter is not specified Not all variables need be defined for every configuration Depending on the protocol and configuration some variables might not be necessary More detailed information is located in the relevant Driver Manual including settings specific to the drivers being used for a particular application Most FieldServer parameters are specified in a configuration file and are fixed A growing number however may be changed dynamically using values found in Data Arrays We call these Dynamic Parameters Refer to Section 6 3 for more information on Dynamic Parameters 3 4 Testing Configuration Files wit
130. vent the squelch suppression times from overlapping with valid data and interfering with proper communication The following connection parameters can be configured for the FieldServer Turnaround delay This is the time the Server takes to initiate a response after having received a poll The Client connection must have a Squelch Timer Tx value less than the turnaround delay Poll Delay This is the shortest time the Client will wait between receiving a response message and initiating the next poll The Server connection must have a Squelch Timer Tx value less than the poll delay Example Connections Port Squelch Timer Tx Squelch Timer Rx Turnaround Delay Line drive On Line drive Off P1 0 06 0 01 0 050 0 001 0 001 9 2 2 Statistics Each connection keeps track of the number of bytes suppressed as a result of TX and Rx squelch timers These may be viewed in the connection statistics screen FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 59 of 90 9 3 Enable on RS 232 Port To force the RTS line high on the RS 232 Connection specify Line Drive Off and Line Drive On as non zero values Connections Port Baud Parity Data Bits Stop Bits Protocol Poll Delay Line drive On Line drive Off P1 9600 None 8 pal mb rtu 0 1
131. ype for J Bus Legal values Al AR DI DR An attempt to generate a write cache block 10074 failed because the Node did not have a connection 10075 Illegal Map Descriptor address This section of Data Array already has a 10076 responsible Map Descriptor IN Ensure Map Descriptor headings are included in the 10077 Unable to add parameters from this line i CSV file Map Descriptor length greater than Data Arra 10079 p p gth g y length Failed attempt to do a Modbus read from 10082 Only writes can be broadcast Node ID O 10083 Illegal Modbus Map Descriptor length 10084 Illegal Modbus Map Descriptor address 10085 Check backup station number settings PLC Port Count set to 1 but Hot Standby not 10085 Set FieldServer parameter hs mode to mode2 configured for Mode2 Protocol specified in config file but no such 10087 20 driver is loaded 10089 Illegal Modbus Node ID Must be in range 1 to 255 10102 An attempt to generate a write cache block Typically a Node has a Server Name specified and a FieldServer Technologies 1991 Tarob Court Milpitas California 95035 USA Web www fieldserver com Tel 408 262 2299 Fax 408 262 2269 Toll Free 888 509 1970 email support fieldserver com FieldServer Configuration Manual Page 85 of 90 exceeded As a result the packet buffer was truncated Error Description Action failed b

FieldServer Configuration Manual

Contents

Download Pdf Manuals

Related Search

Related Contents