Home

FieldServer Configuration Manual

Contents

1. 53 Figure 12 FieldServer Timing Diagram sss nnne nennen 61 Figure 13 Timing Diagram Line Drive On Off Tx and Rx Squelch Poll Delay Turnaround Delay 63 Table of Contents IG FieldServer Configuration Manual 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 1 ports as well as various Fieldbus ports The internal poll block 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 r
2. monitor FieldServer Configuration Manual Section Title Map Descriptors Column Title Function Legal Values Setting the No Stats option on a Map Descriptor will disable the display of MD Option statistics for that Map Descriptor in FS GUI No Stats and will cause zero values to be reflected for all statistics relating to that Map Descriptor in RUIdebug logs Refer to Appendix A 4 The Node ID used by this Map Descriptor Node ID when the driver builds read or write messages Allows a Map Descriptor to address remote Address device data at a specific start memory Protocol dependant location Allows a Map Descriptor address a number Length of remote device data locations from the 1 Protocol dependent start address Scan Interval When using continuous Map Descriptor functions such as RDBC this is the time a Map Descriptor will wait before polling for data again 5 Used to specify engineering units to Units interpret data if used Will display a dash if Protocol Dependent not used Network eee DY AVENS SAF A NEWA Check manual for values number Sector Used by some drivers as a sector number Check manual Tor valies for rack addressing x Used by some drivers as a panel number for Panel rack addressing Card Used by some drivers as a card number for rack addressing Page 82 of 92 monitor
3. 50 6 3 1 Node Offline ACIIOD 1 rete ERE 50 6 3 2 Node Inactivity 51 7 Dynamic Parameters erede NARARANASAN 52 71 1 Dynamic allocation of Node ID or Station number sess 52 7 1 1 1 Diagram 1 Static Server Side Node ID 52 7 1 1 2 Remote Client finds a Node with Node ID dependent on the data read from the remote Server device 53 7 1 2 Descriptor Parameters specific to Dynamic Parameters 54 LAGS M 54 7 1 3 1 Example 1 Dynamic Allocation of Node 54 7 1 3 2 Example 2 Dynamic Allocation of System 0 55 7 1 3 3 Example 3 Dynamic allocation of the BACnet MAC 55 7 1 3 4 Example 4 Dynamic Allocation of the connection Baud Rate 55 IA Eror Messagos Ec 57 8 Port Expander Mode PEX 58 8 1 How Port Expansion 58 8 2 Advantages of Port Expander 58 8 3 Limitations of Port Expander 58 8 4 Port Expander Write
4. Data Arrays The value 257 will be stored Data Array Name Data Format Data DA 1 FLOAT 2 DA 2 BYTE 20 Only numbers in the range 0 255 inclusive 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 Data Value Preload Data Format Preload Data Index DA 1 257 FLOAT 0 DA 2 257 FLOAT 0 Page 43 of 92 sierra IG FieldServer Configuration Manual 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 Array Length DA 1 FLOAT 20 Preloads Data Array Name Preload Data Value 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
5. When using RS 485 specifies delay after RTS is asserted Time in seconds Specifies inter character timeout period within a message Timeout in seconds once it starts 15 ms Delay in seconds 5 ms for serial drivers 0 seconds for all adapter amp ethernet drivers May be protocol This is the time the Server takes to initiate a response after having received a poll 11 Not all ports shown are necessarily supported by the hardware Consult the appropriate Instruction manual for details of the ports available on specific hardware Page 75 of 92 IG FieldServer Configuration Manual dependent for some drivers 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 SCADA Tier of the other Client Only FieldServer that tier will start acting as a Server Setting this parameter to Client Only will prevent this happening This parameter allows the user to configure a time after Node Retire Delay which a Node is no longer polled until the FieldServer is Time s 0 restarted See Section 6 1 4 Write Queue Mode Mode for dealing with potential accumulation of successive Overwrite Blocking writes to the same point can be configured 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 If size 0 every successive wri
6. eesseeseeseeeseeeeeeeeeeen eene nn nnne nnn nn anna nnmnnn nnna 10 3 1 Configuration File OVOrVIOW tiere teet eerte rented eet ri etate psa na aud 10 3 2 Configuration File Structure ssssssssssssssess ener 10 3 3 Editing Configuration Files ssssssssssseseseeeneeeneennnenennnenen nennen nnns nennen 14 3 4 Testing Configuration Files with MB8SIM EXE sssssssssssseseeeereneneen nennen nennen 14 3 41 Additional worthwhile MB8SIM checks sss sienten einn rennen 16 4 Descriptor Functions 17 Active vs Passive fUncllons ecco aceto tree tu rette ea bee eterno euh uo a rn ut eu eg 17 4 2 Passive Map Descriptor nnns 17 4 2 1 TEAS SIV tuetur n LLL E E EL RT ED LU LE 17 422 Passive Client Passive Client sessi eene enne 17 4 2 2 1 Working with Passive Client Passive Server Applications 18 4 3 Active Map Descriptor nennen 19 4 3 1 Read Block Continuous RODC sisse einen tne nnne nnns 19 4 8 2 Active Read Continuous with Sequencing Arcs essen 19 4 3 3 Write Block on Change Wrbx esses sienne enne nnne nnne 19 4 3 4 Write Bl
7. Array Function Comm Bits Bit 900 Alias Node Status Nodes Node Name ID Alias Node ID Protocol Port Retry Interval Recovery Interval N1 1 Modbus RTU P1 0 15 0 15 N3 val 300 Modbus P2 0 1s 0 15 Alias Node Status differs from Node Status as follows e f a 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 Page 48 of 92 sierra IG FieldServer Configuration Manual 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 Column Tite Funtion LegalValues 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 1102 Data Length subsequent nodes after the Node ID Data Array Function Special function for Data Array a If configured the Node address of the specified Node will be at offset 0 The length parameter will be used to Node ID determine the number of Node addresses starting from 1 to 256 the Node ID If not declared or specified as Node ID 0 will be at offset 0 This allows the subnet of
8. 1 LonWorks is a trademark of Echelon Corporation registered in the United States and other countries Nodes may have the same Node ID value so long as they are connected to different ports Page 7 of 92 sierra monitor 1 3 2 Clients and Servers FieldServer Configuration Manual 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 below illustrates this MASTER Client Node ZA Server Side FieldServer Client Side Server Node Figure 1 Client Server Page 8 of 92 of IC FieldServer Configuration Manual 2 OVERALL OPERATION PHILOSOPHY The FieldServer functions as a bridge between two or more different Nodes see Figure 2 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
9. 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 the data for longer than the time configured under Cache Time To Live Refer to Appendix C 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 e Allen Bradley PCCC e Metasys amp 8 4 Port Expander Write Options Three possible scenarios exist for Writes in Port Expansion Mode e
10. 77 Appendix C 4 6 Map Descriptors einen 81 Appendix C 5 Valid Characters for Common Fields in Configuration Files eese 83 Appendix C 6 Kernel Error Messages and 83 Appendix C 7 Networking Glossary 24 00 nennen 90 Sven ge m 8 Figure 2 FieldServer Operation Theory 0 0 0 9 Figure 3 MB8SIM Interface Screen sss enne en rentes sn trenes 15 Figure 4 MB8SIM Error Screen with Driver Versions 15 Figure 5 Typical Network architecture 18 6 Grouping Data 24 Figure 7 Seperating Responsible Map Descriptors 25 Figure 8 Creating a LonWorks SNVT Switch from 2 Modbus 25 Figure 9 Packed Bits Activated sioe entre ce EE D Du at Oca deni 30 Figure 10 Static Server Side Node D nennen nnne nennen tnn intres 52 Figure 11 Remote Client finds a Node with Node ID dependent on the data read from the remote Server GI
11. Appendix C 7 Networking Glossary of Terms Term Description 10Base2 10Base2 is the implementation of the IEEE 802 3 Ethernet standard on thin coaxial cable Thin Ethernet or thinnet as it is commonly called runs at 10Mbps Stations are daisy chained and the maximum segment length is 200 meters 10Base5 10Base5 is the implementation of the IEEE 802 3 Ethernet standard on thick coaxial cable 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 10BaseT is the implementation of the IEEE 802 3 Ethernet standard on unshielded 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 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 transmitted over a chann
12. Node Array 160 Data Array Offset Save Yes Low Limit 0 High Limit 255 Page 54 of 92 sierra S IG FieldServer Configuration Manual 27 1 Example 2 Dynamic Allocation of System Node ID FieldServer watches DA NODE ID NEW offset 0 When the data is updated the FieldServer looks for a Node named NODE_1 If a valid one is found then the NODE of that Node will be changed 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 20 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 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 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 D
13. nodes on AS tes womens 9 E Disabled for RS 232 that are not configured Remote Port Determined by specific driver or protocol used See Driver Manual Page 76 of 92 sierra monitor Info Frames Info Frames FieldServer Configuration Manual Connection Type Application Section Title Adapter Column Title Function Legal Values Adapter Adaptor name Piin DH Modbus PROFIBUS MAC Address Specify Network MAC Net_number address Appendix C 4 5 Nodes Device_Name file Section Title Nodes Column Title Function Legal Values Node_Name The node name specified in the CSV Up to 32 Alpha Numeric Characters Node The station number or address of the node The actual meaning is dependent on the driver and protocol refer to the Driver Manual 1 255 Protocol The protocol being used to update the data for that node Refer to the Driver Manual Modbus TCP etc IP_Address IP address of the Server Device Valid IP address Host_Name Specifies the host name of the remote device Any valid host name Retries Specifies how many sequential 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 response will retry polling the device the number of times specifi
14. 4 SPR4052 37 20 at 80 4 SPR4052 00 00 00 00 8 90 4 SPR4052 PATTERN DID NOT 111 100 ul MATCH 5 2 6 1 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 0 thru 8 or 111 depending upon the combinations existing in the Tokens Data Array Page 33 of 92 sierra monitor FieldServer Configuration Manual Table String Composition Source Data Array Source Data Array Build Pattern Description Values Format 55 15 0 255 Byte 37 0F 00 FF Two Hex Characters 555 15 0 2550 INT UINT16 UINT32 555 15 0 2550 Just as decimal values 55 12 15 123 0 255 FLOAT 55 12 15 12 0 00 Requires period and two decimal 255 00 places 1101 Bit 1 1 0 1 Binary pattern 5 2 10Conditional 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 destin
15. 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 at any time The FieldServer thus acts as a Client and a Server simultaneously Location Client Side Figure 2 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 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 PLC If
16. P 8 The Server Node is attached to this connection The Node ID of the Server A name allocated to the node for reference by the Map Descriptors Page 11 of 92 IG FieldServer Configuration Manual 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 Client Side Map Descriptors Descriptors Descriptor Name Data Array Name Data Array Offset Function Node Name Address Length 5 Interval CMD AI 01 DA AI 01 0 Rdbc PLC 1 30001 20 1 000s AO 01 AO 01 0 Rdbc PLC 1 40001 20 1 000s Map Descriptors Map Descriptor Name Data Array Name Data Array Offset Function Node Name Address Length 5 Interval CMD DI 01 DA DI 01 0 Rdbc PLC 1 10001 20 1 000s CMD 01 DA DO 01 0 Rdbc PLC 00001 20 1 000s Node being accessed Number of points in package Name assigned to the Map Descriptor In some protocols the name becomes the variable name Data Array to be used for storage of data being passed between protocols Determines how data is First point to be fetched written address Timing The FieldServer is either being parameters Offset in relevant Data Array to start data reading being read or accesse
17. length parameter and transfer that data to the Data Array specified Reads are performed continuously at an interval specified by the Scan Interval parameter 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 2 4 3 3 Write Block 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 on Change of Value WRBCOV T
18. 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 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 1 The string Revision 123aA is stored starting in the 2nd element index 1 of the Data Array named DA 1 Page 44 of 92 IG FieldServer Configuration Manual 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 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 Fo
19. DA if applicable Offset DA 1 Moves Function Source Data Array Source Offset Target Data Array Target Offset Length Move Only Source DA 0 DA 40 5 Target Offset example Five Floating point values are moved from the first offset of Source DA to Offset 40 of Target DA Moves Function Source Data Array Move Only Source DA 0 Source Offset Target DA Target Data Array larget Offset Offset DA 0 Length o The Target Offset Value will be obtained from the Offset DA at offset 0 Page 23 of 92 FieldServer Configuration Manual 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 Figure 6 Grouping Data 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 th
20. Data Array to change the Baud Rate Dynamically e g Values of 110 300 600 115200 if supported stored in the Data Array will cause the Baud Rate to be changed Dynamic Parameters Function Descriptor Name Data Array Name Data Array offset Baud Rate R1 DA BAUD 0 Page 56 of 92 monitor FieldServer Configuration Manual 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 i i i luati D i k DynParam 2 Err This message is printed when evaluating a Dynamic parameters tas where the function Change Node ID The maximum length of the descriptor is 32 characters 8 DynParam 3 Err Node 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 8 4 Err Node ID Validation failed Lo ld Hi ld Rad 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 8 d DA off Id d changed to dynamically You may ignore this message if
21. FieldServer Configuration Manual Appendix C 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 36 85 0 38 amp 39 86 V 40 87 41 88 X 42 89 43 90 7 45 91 46 92 47 9 48 0 94 49 1 95 underscore 50 2 96 51 3 97 a 52 4 98 b 53 5 99 54 6 100 55 7 101 56 8 102 f 57 9 103 g 58 104 59 2 105 60 lt 106 j 61 107 k 62 108 63 109 64 110 65 111 66 112 67 113 q 68 D 114 r 69 E 115 s 70 F 116 t 71 G 117 u 72 H 118 73 119 w 74 J 120 75 K 121 y 76 L 122 2 77 123 78 124 79 125 80 126 81 Q Appendix C 6 Kernel Error Messages and Descriptions Error Description Action Page 83 of 92 sierra monitor FieldServer Configuration Manual Error Description Action 10003 2 Data Array exceeds the heck Map D iptor Offset length A write to a Byte FloatData Array exceeds Cheeks Map Descriptor Lisel feng 10004 the available space A range of data exceeds the length of a 10005 BYTE Data Array Check Map Descriptor Offset length count 10009 Pro
22. 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 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 Array Function DA Comm OK Bit 256 Node Status Target DA Bit 200 E 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 DA 40 Status 1 Page 31 of 92 FieldServer Configuration Manual 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 table of patterns strings of tokens separated by each linked to 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
23. 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 Page 65 of 92 sierra IG FieldServer Configuration Manual Appendix A 3 Disabling the Client side of a configuration Setupthe Modbus Server side Data Arrays Data Array Name Data Format Data Array Length DA DO 01 Bit I Connections Port Baud Parity Data Bits Stop Bits Protocol P1 9600 None 8 mal Modbus RTU Nodes Node Name ID Protocol Srv 11 11 Modbus Descriptors Map Descriptor Name Data Array Data Array Offset Function Node Address Length SMD_DO1 DA_DO_01 0 Passive RTU Srv 11 00001 1 ignore Setupthe Modbus Client side Connections Port P2 Nodes Node Name ID Protocol Port DEV11 11 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 1 1 process Appendix A 3 1 Disabling a Node Nodes Node Name ID Protocol Port DEV11 11 Modbus RTU P2 ignore DEV12 12 Modbus RTU P2 process Page 66 of 92 IG FieldServer Configuration Manual Appendix A 4 Disabling Statistics D
24. Map Descriptor by name Up to 32 Alpha Numeric Characters Data Array Name DA Name The name of the Data Array where information will be stored to and retrieved from by the Map Descriptor One of the Data Array names as defined in Appendix C 4 2 Data Array Offset The offset into the Data Array where data should be stored on reads or retrieved from on writes to Data Array Length 1 as defined in Appendix C 4 2 Rdbc Read data buffer continuously Wrbc Write data buffer continuously Rdb Read data buffer Function Function of Client Map Descriptor once Wrb Write data buffer once Wrbx Write data buffer on change One of the Node names Node_Name Name of Node to fetch Data from specifies in 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 floating point value 0 Data Array High Scale Buffer High Scale Scaling max in Data Array Any signed 32 bit floating point value 100 Node Low Scale Scaling zero in Connected Node Any signed 32 bit floating point value 0 Node High Scale Scaling max in Connected Node Any signed 32 bit floating point value 100 Page 81 of 92
25. 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 FieldServer Configuration Manual Figure 7 Seperating Responsible Map Descriptors Special Application Creating a LonWorks SNVT Switch from 2 Modbus registers LonWorks Server Map Descriptor Figure 8 Creating a LonWorks SNVT Switch from 2 Modbus registers Page 25 of 92 IG FieldServer Configuration Manual 5 2 Function Moves Type Casting 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 moves described below perform these kinds of operations 5 2 1 Functions Available For Type Casting e Join Float Split Float e Join Int16 Split Int16 e Join Int32 Split Int32 Swapped versions of the above Big Endian vs Little Endian e Extract Bit Pack Bit Move The following legacy functions have been replaced by the functions listed above They are simply presented in the
26. as only one operation can be performed per move SQ Square n outputs are produced for n length values stored in sequence SQRT Square root starting at the Target Offset PER oL 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 Offset Length ADD DA SDA1 0 DA TDA 0 10 SUB DA SDA1 0 DA TDA 10 10 MULT DA SDA1 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 DA SDA1 0 DA TDA 10 E LTE DA SDA1 0 DA TDA 11 1 GT DA SDA1 0 DA TDA 12 A LT DA_SDA1 0 DA TDA 13 4 1l PER DA SDA1 0 DA TDA 14 v EQ DA SDA1 0 DA TDA 15 el NE DA SDA1 0 DA TDA 16 1 Page 36 of 92 SMEG monitor FieldServer Configuration Manual 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 SQRT 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 operatio
27. associated with more than 10216 one Client Node H H h E h An IP Fragmented packet was received PUE ine b add 10302 api stat screen If this occurs frequently enable while IP Defragmentation was disabled IP Defragmentation 10401 The I Net Server ignored a write to an Input 10402 The Baud Rate on a Connections Port has A default value will be used not 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 overwritten This could be caused by using Solve by increasing the Write Queue Size or 10404 i moves to do multiple write thru s on slowing write thru s RDBC Map Descriptor 10999 Up to and including 11001 Lutron driver Data Array length for Area names too small 11002 envers Dala ATAY engin taf cele Increase Data_Array_Length in CSV file names too small Lutron driver Data Array length for Zone 11003 names too small Envirotronics SystemsPlus driver The name entered the SysPlus Cmd This field must be filed in with a valid 11004 t mapdesc field is not recognized or was not SysPlus Cmd entered at all Envirotronics SystemsPlus driver name entered in the SysPlus Data Type This field must be filed in with valid 11005 sa mapdesc field is not recognized or was not SysPlus Data Type entered at all Envirotronics SystemsPlus driver The 11006 name
28. 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 Complete 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 Client Ack Complete Ack Immediate Ack Verified Page 78 of 92 monitor Section Title Nodes FieldServer Configuration Manual Column Title Function Legal Val
29. nennen 26 5 2 1 Functions Available For Type Casting isses einen enne enne 26 5 22 Converting two Integers to a amp nnne ennt nnn 27 5 2 83 Using Moves to pack and unpack bits to or from a 27 1 1 1 Example 1 Simple Bit Extraction sss sienten enne nnns 28 Table of Contents FieldServer Configuration Manual 11 2 Example 2 Simple Bit 28 1 1 3 Example Extracting bit 29 524 Extraction Application Example sss eene 29 5 2 4 1 Bit Extraction Example Configuration sse 30 5 2 5 TASK MOVES S 31 5 2 5 1 Special Application Node Status 31 5 26 E 32 5 2 6 1 Table of Patterns Configuration 33 5 2 0 1 Moves DofMHon e EET 33 5 2 6 2 Table String Composition sssssssssssssseeeeneen nennen nnns 34 5 2 7 Conditional 5 34 5 2 7 1 Conditional Moves 1 35 5 2 7 2 Conditional 2 35 5 9 Mathematical functions cioe ii ete la
30. not directly related to any of the connections Common Information Bridge Title DCCO030 CC0019 This title appears on the top line of the FS GUI 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 01 Ulnt16 200 DA AO 01 Ulnt16 200 DA DI 01 Bit 200 DA DO 01 Bit 200 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 C 3 Page 10 of 92 IG FieldServer Configuration Manual esses eee esse esse Sees sees eee Il Client Side Connections This section contains the parameters that describe the nature of Connections Port Baud Parity Data Bits Stop Bits Protocol Poll Delay P8 9600 None 8 1 Modbus 0 1005 Timing parameters on the connection allow for fine tuning of communications The port to be connected to defined in The protocol for the network connected to this nort Client Side Nodes This section defines the logical connection parameters for the Server Nodes communicating with the FieldServer Nodes Node Name ID Protocol Port PLC 1 Modbus RTU
31. 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 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 the 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 Tokens Status Data Arrays Data Array Name Data Format Array Length Byte 4 Int sil 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 43 20 Faul
32. only Network Network Protocol A Protocol B FieldServer Figure 5 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 for 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 Page 18 of 92 sierra IG FieldServer Configuration Manual 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
33. other FieldServer that forms the hot standby pair Default E value Pex Specify if Pex Mode should be enabled or blanko disabled Refer to Section 8 Enabled Disabled Appendix 4 2 Data Arrays Section Title Data_Arrays Column Title Function Legal Values Data_Array_Name DA_Name Provides name for Data Array Up to 15 Alpha Numeric Characters Data_Format Provides Data Format INT16 INT32 or BYTE Specifies size of source value when scaling FLOAT specifies floating point format for preloaded data in buffer 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 C 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 Default value blank Page 73 of 92 monitor FieldServer Configuration Man
34. table below for reverse compatibility Old Keyword New Keyword Function Performed Int32 Join 2116 1 132 Join Int32 Swapped source bytes ab cd target bytes 2 116 1 132 5 Join Int32 source bytes ab cd target bytes cdab 2 116 1 i32 m10k Join M10K Modulo 10 format Int32 Split 1132 2116 Split Int32 Swapped source bytes abcd target bytes ab cd 1 132 2 116 5 Split Int32 source bytes abcd target bytes cd ab Float Join 2 116 1 float Join _Float_Swapped source bytes ab cd target bytes abcd 2 116 1 float sw Join Float source bytes ab cd target bytes cdab Float Split 1 float 2 116 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 i16 2 i8 Split IntG Swapped source bytes ab target bytes a b 1 116 2 18 5 Split Int16 source bytes ab target bytes b a Page 26 of 92 FieldServer Configuration Manual 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 Offset Target Data Array Targe
35. 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 Page 9 of 92 IG FieldServer Configuration Manual GETTING STARTED BASIC CONFIGURATION 3 1 Configuration File Overview The default driver configuration file CONFIG CSV for any driver combination ordered is loaded into the FieldServer and can be retrieved using the Graphical User Interface Utility see the FieldServer GUI 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 SMC Customer XYZ Corp Ultimate Destination Main Office Note Comments should be at the start of lines If comments made after a line of parameters must not follow a SMC Sales Order 00103400 comma directly Driver Configuration Modbus RTU Configured By GFM Date 23 Mar 00 Relevant Project information Copyright c 2000 FieldServer Technologies 1991 Court Milpitas CA 95035 408 262 6611 Fax 408 262 9042 support fieldServer com This section allows for the determination of parameters
36. values for specific drivers Page 71 of 92 monitor FieldServer Configuration Manual Note Titles in brackets indicate aliases Appendix C 4 1 Common Information Section Title FieldServer Column Title Function Lega Values Title Allows user to add title to main menu if desired Title Text Title text may not contain spaces When block caching is used data previously polled and stored in an internal data Time in Cache Age A Cache Age Timeout buffer is returned to the Server providing the seconds iiim data is not too old This parameter specifies the 300s length of time cached data is valid 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 Time in Cache Time To Live is configured If this data is not accessed for seconds longer that the time specified by this parameter 300s the cache will be cleared FieldServers have the ability to run as multiple FieldServers on one platform To differentiate Tier between the different running applications each 2 of the applications is referred to as a Tier with a specific name i Default A name by which a FieldServer is identified FieldServer Name need not be unique blank Cache Age Limit Maximum age of data in a cache Map onin fes Descriptor for immediate response to po
37. 0 at startup and will be changed to one of the following Baud Rates if supported whenever the Map Descriptor stores a value in the Data Array Page 55 of 92 IG FieldServer Configuration Manual NN Baud Rate 0 Default 1 110 2 300 3 600 4 1200 5 2400 6 4800 7 9600 8 19200 9 20833 10 28800 11 38400 12 57600 13 76800 14 115200 Specify the Data Format as Baud This forces the use of the Values Baud Rate table above Data Arrays Data Array Name Data Format Data Array Length DA BAUD BAUD i The Connection Node and Map Descriptor examples below apply to both methods Connections Port Baud Parity Data Bits Stop Bits Protocol R1 9600 None 8 1 Modbus RTU 000 Node Name Node ID Protocol Port MB RTU 11 Modbus Map_ Descriptors Map Descriptor Name Scan Interval Data Array Name Data Array Offset Function Node Name Address Length 1 1 05 BAUD 0 RDBC MB RTU 40001 1 Method 2 Using actual Baud Rate Values Specify the Data Format as a conventional value data type e g Byte Uint16 Uint32 Data Arrays Data Array Name Data Format Data Array Length DA BAUD UINT32 2 Only for this method specify a dynamic parameter of Function Baud Rate to allow the use of actual Baud Rate values in the
38. 24 as its weighting in the integer value is 2 to the power 10 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 Page 29 of 92 IG FieldServer Configuration Manual Figure 9 Packed Bits Activated 527 1 Bit Extraction Example Configuration Hu 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_Descrptor Name Data Array Name Data_Array_Offset Node Name Function Address Length PI 01 01 Source DA 0 UPS 01 Rdbc 40289 1 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 0 to 9 now contain the first 10 bits of Register 40289 These can now be served as bits to the Protocol of choice Page 30 of 92 FieldServer Configuration Manual 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
39. 3 times a minute using the DA Function After Store Parameter startup the value will be loaded 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 FieldServer Configuration Manual 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 Data Array Length UINT32 Function After Store Non Volatile Page 46 of 92 IG FieldServer Configuration Manual 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 equivalent to the station address of the Node Refer also to Section 9 Appendix C 2 and Appendix 4 5 Example If seven Nodes are connected to
40. 44 1100 nennen enne nennen 67 Appendix A 5 DHCP Client 2222 eene 68 Appendix B 69 Appendix B 1 Moves performance 69 PNMipeeaiiclcnme 70 Appendix 1 Working with the Driver 70 Table of Contents IG FieldServer Configuration Manual Appendix C 1 1 Introduction i i EF o Ee 70 Appendix C 1 2 Driver Manuals as Part of the Documentation Set sees 70 Appendix C 2 Default settings for parameters sssssssssssssssseeeeeenenneen nennen nennen 70 Appendix Available Data Types for Data 71 Appendix C 4 Permissible Values for Configuration File Variables 71 Appendix C 4 1 Common Information esses siis sienne 72 Appendix C 4 2 Data Arrays t ate adi a Poe Ire dnx Sua Ra Haa ee bah 73 Appendix C 4 3 Data Array enne innen tnn 74 Appendix C 4 4 Connections Adapters 75 Appendix C 4 5 Nodes Fe a aea aE
41. ATemporary Read Map Descriptor already exists for the point being written ATemporary Write Map Descriptor already exists for the point being written e No Temporary 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 The Node parameter Write Ack Option needs to be configured Refer to Appendix C 4 Metasys is a registered trademark of Johnson Controls Inc Page 58 of 92 sierra monitor FieldServer Configuration Manual 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 l
42. DOI2 DAIS DOIS 4 0014 FN1 FN2 FN3 FN4 DAO DOO Task_105 21 1 0 DAZ SX TIDAN 52 DA 4 3 OR AND 5 21 This definition will result in the following operation DA 5 21 DA 1 0 amp DA 2 1 DA 3 2 amp 4 3 Page 39 of 92 sierra IG FieldServer Configuration Manual 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 n the Client Side Map Descriptor section by adding scaling parameters e In the Server Side Map Descriptor section by adding scaling parameters e n the 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 Data Array Low Scale Scaling zero in Data Array Any signed 32 bit floating point val
43. 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 assigned a Driver Configuration Code DCC The DCC covers the combination of drivers listed on the cover 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 C 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 sup
44. Node ID dependent on the data read from the remote Server device Remote Client Browse for nodes devices and then browse for points Finds Node ID as updated with data from the remote Server device Server Side Node initially Server Side takes Node ID from Server Side configuration file Client Side Client Side Polls for Data Response data contains Server Side Node ID Polls for Data Response unpacked and stored in Data Array A specially configured task uses the data to change the Node D of the server node in the FleldServer Remote Server Remote Server Device Device Figure 11 Remote Client finds a Node with Node ID dependent on the data read from the remote Page 53 of 92 monitor FieldServer Configuration Manual 7 1 2 Map Descriptor Parameters specific to Dynamic Parameters Section Title Map Descriptors Column Title Function Legal Values Change Node ID Function Function Qr Map Change System Node ID Descriptor Change System 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 C 4 5 or the Bridge Title of the FieldServer specified as described in Appendix C 2 Refer to examples below for more information Data_Array_Name Name of Data Array from whi
45. OHRPCHSH from the value in a data array 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 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 Figure 10 Static Server Side Node ID 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 Page 52 of 92 S IG FieldServer Configuration Manual 7 1 1 2 Remote Client finds a Node with
46. Options rece aa ee ee Ean 58 8 5 Handling of Successive Writes to the Same 59 8 6 Expansion nennen nennen ns 59 9 Timing 60 9 1 Line Drive Parameters i ee ELE ku POUR 62 9 2 Suppressing Squelch on Half Duplex 62 9 2 1 Setting Parameter Values sss 64 222222 rdiet e MER SU TL 64 9 3 Enable om RS 282 Port etes ster rr a Rede gra Er 64 Appendix A Useful Features 1 o1 c ccc olere crc eere rL eren nnmnnn nnmnnn nannan nnmnnn nnna naa 65 Appendix A 1 Using 65 Appendix A 2 Using conditional process 65 Appendix Disabling the Client side of a configuration sssseeeeneeen 66 Appendix 1 1 Disabling a 66 Appendix A 4 Disabling Statistics 2
47. Source Data Array Any signed 32 bit floating point value 100 Target Low Scale Scaling zero in Destination Data Array Any signed 32 bit floating point value 0 Target High Scale Scaling max in Destination Data Array Any signed 32 bit floating point value 100 5521 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 0 to 10 in the Source is being represented as a value from 0 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 Scale DA Unscaled Function Source Data Array Source Offset Target Data Array Target Offset Length 5 Low Scale 5 High Scale Target Low Scale High Scale 00 DA Scaled 00 5 00 10 00 100 Page 41 of 92 monitor 5 6 Preloading Data Arrays with Initial Values FieldServer Configuration Manual 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 s
48. 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 monitor 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
49. Type 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 10077 Unable to add parameters from this line the CSV file 10079 Map Descriptor length greater than Data Array length 10082 Failed attempt to do a Modbus read from 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 10085 PLE Goum set to 1 but Hot standby Set FieldServer parameter hs mode to mode2 not configured for Mode2 Protocol specified in config file but no such 10087 8 driver is loaded 10089 Illegal Modbus Node ID Must be in range 1 to 255 Typicall N h N ifi An attempt to generate a write cache block d ede e Server Name spectiod and a write to this Node occurred before the 10102 failed because the Node did not have a Server Name mechanism discovered a valid connection 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 Hot Standby Mode1 10105 PLC anly Supported in Set FieldServer parameter hs mode to mode2 hot standby mode2 An i
50. ad a Value Effect of Target Data Array 43 5 606 Example S8 Load Value Negative Numbers 44 5 6 7 Example 4 Load a Value Floating Point Numbers 44 5 6 8 Example 5 Load a Value Strings 1 sse 44 56 97 Example 6 Load a Value Strings 2 sisse 45 5 6 10 Example 7 Load a value Casting ssssssssssse esee enne enne 45 5 6 11 Example 8 Load an Object name sisse eene enne 45 5 7 Loading Data Array Values from the FieldServer s Non Volatile Memory 46 6 Manageme n 47 6 1 Data Array Funcions E 47 6 1 1 Node Status Function esci deerit 47 6 1 2 Alias Node ID ios diete idet fos 48 Table of Contents IG FieldServer Configuration Manual 6 1 8 Alias Node ID Example ide ada Er e EE e ERR ER e ERE El e BER EX Ra Eisai 48 6 1 4 Node Online Bits E dE XX 49 6 2 Connection Paratmetelrs conet oce re c 50 6 2 1 Node Hetire 20 50 b 3 Node Parameters deed traen
51. ailable 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 5 IZ P2 rtu Nodes Node Name ID Protocol Port Timeout Write Option Dev1 s 1 mb ru P2 12 Ack Immediate 10 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 Page 59 of 92 IG FieldServer Configuration Manual 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 spe
52. an Interval DA GV 01 192 Gas Snapshot 00 31 DA_GL_PW_01 192 a1 DA GV 01 192 Gas Snapshot 01 5 1l DA GL PA 01 192 5 19 21 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 Page 35 of 92 monitor 5 3 Mathematical functions FieldServer Configuration Manual 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 MULT n length of input values DIV GTE gt Each move works as follows value_of_ DA_SDA1 offsetO MathOperator value of DA SDA1 LTE on offset1 Result is stored in DA_TDA offset GT gt e g for GTE value1 DA SDA1 0 value2 DA SDA1 1 if value1 GTE value2 1 will be stored at DA TDA 10 else 0 will be EQ stored NE The length parameter is always 1
53. and is larger than the length of the Data Array 10047 Could not find Source Data Array for Move 10048 Could not find Target Data Array for Move 10049 Could not find Client Data Array for Move 10050 Could not find Server Data Array for Move 7 exists Could not find Feedback Data Array for 10051 Move 10052 Could not find Mode Data Array for Move 10053 Data Array already has a responsible move 10054 Setpoint Moves are only allowed to be 1 item in length A move was defined and a write occurred to the target Data Array but cannot transfer 10055 to the Source Data Array because no Responsible Active Descriptor is defined A move was defined and a write occurred to the target Data Array but cannot transfer 10056 to the Source Data Array because the Node associated with the Responsible Active Map Descriptor is offline 8051bp03 or CB8MENU found 10058 SMCTCP INI and FS TCP INI files so it will delete F8 TCP INI and use SMCTCP INI in future 10058 Cidversion GERDIBOOTIEXE being used 021 THIS Of Use Manual of setting IP address see Utilities manual 10070 Illegal Node ID 10071 Map Descriptor length of 0 is not allowed Page 85 of 92 sierra monitor FieldServer Configuration Manual Error Description Action 10072 Map Descriptor length too large 10073 Illegal Data
54. ast value that was received from the Client is written to the Server Intervening writes may be lost Blocking if it is important to preserve the sequence of write values to the same point e g switching sequence of on 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 parameters and values using the following Connection Column Title Function Legal Values Write Queue Mode Mode for dealing with potential accumulation of successive writes to the same point can be configured Overwrite Blocking Write Queue Size 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 If size 0 every successive write is blocked message will be displayed when blocking occurs except if the Queue 0 Non negative integer 0 Connections P1 9600 None Port Baud Parity Data Bits Stop Bits Protocol 8 zl Modbus None 0 1005 Blocking n5 Handshaking Poll Delay Write Queue Mode Write Queue Size Timeout 8s 8 6 Port Expansion Configuration The example configuration file for this mode is av
55. ated Reporting will stop after all the devices have been reported or when the Data Array is full Chan Overview Stat Same except 0 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 device 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 System LED Status Provides the states of the system s hardware LEDs with a 1 indicating an LED is on and a 0 indicating an LED is off The target data array for this function should be of type BIT and needs to have a minimum length of 5 The system LEDs correspond to the following bit offsets Bit 0 Run LED Toggles every second while the FieldServer is runni
56. ation 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 The offset within the Data Array to which data is to be copied The offset can be either a hardcoded value or can be obtained from another data array See Moves example 5 1 1 1 for more information Length The number of consecutive source Data Array values to be moved to consecutive target locations starting at the respective offsets Conditional Data Array The name of a Data Array to be used for conditional moves See Section 5 1 1 3 for more information Conditional Offset The offset into the Conditional Data Array where the conditional bits for the move 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 Task Name If a task name is specified the move operation becomes a continuous task on the FieldServer that is executed at the scan interval specified S
57. can Interval The time interval at which the task will be repeated A task name must be specified if a scan interval is specified You could insert in place of any token if the value for that token is unimportant 5 2550 is negative two negative signs one is considered as delimiter Page 34 of 92 FieldServer Configuration Manual 2 10 1 Conditional Moves Example 1 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 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 1 Status 1 1 Source 2 0 Target 01 5 1l Status 2 b au 2 10 2 Conditional MovesExample 2 In this example the data from DA GV 01 will be moved to Gas Snapshot only when DA PW 01 or DA GL PA 01 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 Target Offset Length Conditional Data Array Conditional Offset Task Name Sc
58. ch the parameter value is taken One of the Data_Array_Names specified as described under Appendix C 4 2 Data_Array_Offset Offset into the Data Array from which the parameter value is taken 0 to Data_Array_Length 1 as defined in Appendix C 4 2 Low_Limit These parameters can be used High_Limit to define a range of offsets that are affected by this command Positive integer 0 Save The save value enables or disables making the change permanent f yes the value will be stored and used next time 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 Yes No Load csv with par ameter 7 1 3 Examples 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 0 to 255 inclusive If it is it will look for the Node called 1 If found the Node ID will be changed to the new value Dynamic Parameters Function Change Node ID Descriptor Name PII Data Array Name
59. ch source offset and packs the bits into the Bit Pack Data Array 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 The function extracts a subset of bits out of a source Register offset and transfers these to Bit_Move a destination Register offset in packed form Length specifies the number of bits to be extracted Keywords Function Values The parameter specifies the bit offset within a word to start at when performing Default Bit Offset a bit move For Bit Extract operations the source bit offset in the word pointed 0 to by the Source Offset parameter is implied For Bit Pack operations the bit offset within the word pointed to by Target Offset is implied Length The length parameter specifies the number of bits to be extracted packed n 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 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 n5 Target DA 0 48 5 2 5 Exa
60. cified 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 re established the FieldServer will wait for a period called Probation Delay before marking the Node as online Note 1 The 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 C 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 Timeout 0 5 seconds Map Descriptor Node Connection Node lInactivity Timeout 0 seconds Node see Section 6 3 2 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 Connectio
61. d assist with writing data This can be continuous or on change access storage pacing of data Page 12 of 92 IG FieldServer Configuration Manual Settings for how the FieldServer communicates with Client Nodes Connections Adapter Protocol The protocol for the network N1 Modbus TCP connected to this port Adapter definition applies to defining network and FieldServer e g PROFIBUS Server Side Connections Server Side Nodes Nodes Node Node ID Protocol 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 Descriptors Map Descriptor Name Data_Array Name Data Array Offset Function Node Address_ Length SMD DI 01 DA DI 01 0 Passive Srv 11 10001 200 SMD DO 01 DA DO 01 0 Passive Srv 11 00001 200 Page 13 of 92 sierra monitor S FieldServer Configuration Manual 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 I
62. d 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 0 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 drive off P8 9600 None 8 1 Modbus RTU 0 1005 0 0015 0 0015 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 transmission burst causing spurious data to be received at either end The FieldServer kernel implements a user configurable timing sequence
63. 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 Page 62 of 92 monitor Si FieldServer Configuration Manual 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 appropriate moment 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 valid received message as determined by the protocol driver Note that the Squelch Timer Rx is onl
64. device e g for some Fire Panel drivers and the device could possibly only generate messages at event occurrence that may not happen for weeks or months In such cases the parameter can be omitted or set to zero Nodes Node Name ID Protocol Port Inactivity_Timeout PLC 12 2 ES 1 0 13 IIS Node will be Function Disabled marked offline if Node will stay no messages received for 15 Page 51 of 92 S IG FieldServer Configuration Manual 7 DYNAMIC PARAMETERS Most FieldServer parameters are specified in a configuration file and are fixed 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 Parameter Section Title Notes Node ID Nodes This parameter typically describes the Server device address of a communications session Many drivers use this parameter and the meaning of the System Node 10 FieldServer parameter is dependent on its context e g BACnet Used as the MAC address DNP3 Used as the local station ID Similar to changing the System Node ID but specifically BACnet MAC Address FieldServer designed for use on ProtoCessors because it also writes the new ID down to the PIC where BACnet is implemented The Baud rate on a connection can be changed dynamically B aun C
65. e FieldServer Server side as follows Configuration 1 Descriptor 1 serves up 40001 Length 25 Map Descriptor 2 serves up 40026 Length 25 If the two poll blocks fall within these two address spans the poll will be successful however if all 50 registers are polled in a single poll it will fail Configuration 2 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 Configuration 3 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 Page 24 of 92 sierra monitor 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
66. e did not have a connection 2 kon pi 18 Correct the protocol in the configuration file 10034 configuration file but the required driver is Obtain the correct DCC not loaded in the firmware CB8MENU I DG respond ane Increase Cache Age setting in the configuration 10038 Data Array Age time exceeding the Cache 9 9 9 Age time limit file Page 84 of 92 sierra monitor FieldServer Configuration Manual Error Description Action There was a message overrun on Modbus TCP slave driver The Client is polling too often for the FieldServer to respond and 10039 vier ds unte Man Message E Increase the timeout on the Client device buffer There should be overrun statistics on the Server Connection in question Same as 10039 except the overrun is more 10040 than two messages 10041 Tad n Fix the configuration error configuration file or move not defined 10042 High and Low Scaling values are equal Move overruns Data Array This usually 10045 means mal elise das TS eng er Actions Check Data Array Length the Move command is larger than the length of the Data Array Eus MOVE SERINGA Target Offset Source Offset Client Offset Move Offset lies outside the Data Array Server_Offset Feedback_Offset Mode_Offset 10046 This usually means that the offset of the Length Move comm
67. eatures in this section will probably not be useful 5 1 Moves The Moves function permits data to be moved from one Data 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 The offset within the Data Array to which data is to be copied The offset can Target Offset be either a hardcoded value or can be obtained from another data array See Moves example 5 1 1 1 for more information The following elements are optional The number of consecutive sou
68. ed by the retries parameter The FieldServer will attempt to recover the connection once the recovery interval has elapsed Count Default 3 Retry_Interval The amount of time in seconds that the driver should wait before retrying a poll Interval in Seconds 12 a If a Host name is used instead of an IP address the FieldServer will try to resolve it to an IP_address before starting to poll the remote device If using an IP Address a Host Name the FieldServer will try to resolve the host name to get the latest IP Address to use otherwise the configured Address will be used The FieldServer will try to re resolve the host name before starting node recovery to get the latest IP Address Ifa host name cannot be resolved the last known Address will remain in use Page 77 of 92 monitor Section Title Nodes FieldServer Configuration Manual Column Title Function Legal Values after a timeout has occurred 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 lgnore Clients causes the Server to behave
69. eee EU Cu ERE CLE ac ene 36 5 8 1 Math Function as a Moves Function 36 5 8 Standalone Math 24 0000000000000000000000 37 8 33 Math Usage Example R 37 5 3 4 Optional re RE ERRAT 38 5 3 4 1 Truncate Result Example cie ete etre t tt ena edat e duds 38 D Em 39 5 4 1 Logic as a Moves 39 5 4 2 Slandalone LOglc ooi e Dd e eddies eee waka 39 5 4 2 1 Logic Usage Example ireren endure ebd eder eere aden et 39 PME eoo RR M 40 5 5 1 Map Descriptor Scaling ni o ERR Eb nee 40 5 5 1 1 Scaling function example Converting Celsius to 40 5 5 2 5 USING MOVES 41 5 5 2 1 Moves Scaling function example Multiplying values by 10 41 5 6 Preloading Data Arrays with Initial Values sese een 42 5 6 1 EXEC 42 5 6 2 Parameters used to define Preloads sss enne nnne nnns 42 5 6 8 Limitations and Operational Considerations esses seen 43 5 60 Example T Load a Value ennt 43 5 605 Example 2 Lo
70. el 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 GUI FS GUI Graphical User Interface Hub A concentrator is a hub repeater or concentrator that brings together the connections from multiple networ
71. entered in the Store Data Array Name mapdesc field is not valid or was not entered at all Envirotronics SystemsPlus driver The 11007 name entered in the This field must be filled in with a valid Data Array Par Data Array Name mapdesc field is not name valid or was not entered at all Envirotronics SystemsPlus driver 11008 name entered in the SysPlus Alarm Name mapdesc field is not valid or was not entered at all Page 88 of 92 sierra monitor FieldServer Configuration Manual Error Description Action Envirotronics SystemsPlus driver The requested number of events or auxs to set Reduce number of events or auxs or increase 11009 is more than set up in the parameter Data parameter Data Array length Array Siemens Cerberus driver The counts Data 11010 Array has less than 14 data elements per Increase the number of data elements in the panel and event countds could not be counts Data Array to 14 elements per panel stored Use the events 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 0 15 256 4 3844 since there are always 256 Siemens Cerberus driver The Client driver devices Dor module Tor Calpers Tne field block number represents the Cerberus could not find a suitable Map Descrip
72. equired See Enote0002 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 1 3 Terminology 1 3 1 Nodes The devices communicating with the FieldServer may be referred to as Stations Nodes RTU s DCS s Workstations SCADA Systems 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
73. er 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 2 10 and DA 2 0 20 then this means Da 1 0 is 50 of Da 2 0 so DA 5 0 will contain 50 5 3 4 Optional Parameters m Legal Parameter Description 9 Values Specifies the number of consecutive source Data Array values from all An 2 defined source Data Arrays egg DAI1 DAI4 to be operated on and to y Length positive store a result at consecutive target locations starting at the respective inteder offsets g Task If a task name is specified the move operation becomes a repetitive task Any strin on the FieldServer and the data will be updated on a regular basis y 9 Specifies the time interval at which the task will be repeated A task Scan Interval dede gt 0 15 25 name must be specified if a scan interval is specified Truncate This function causes all intermediate and final results to be stored after Ves Result truncating Refer to the example in Section 5 3 4 1 5 3 4 1 Truncate Result Example Math DAM DAI2 FN1 FN2 DOM DOI2 DOI3 Length Truncate Results DA X DA 17 DA 17 DIV MULT DAZ 0 0 0 0 zl Yes lf DA 17 0 17 and DA X 0 100 x DA 2 0 17 17 will be 85 NOT 100 Page 38 of 92 IG FieldServer Configurati
74. er enables the user to configure the timing of a read after a write The Readback operation will apply to all drivers that support Active Reads 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 Readback On Write Readback Asynchronously Readback Immediately On Write Page 79 of 92 monitor Section Title Nodes FieldServer Configuration Manual Column Title Function Legal Values 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 MAC Address Requered for protocols that use it not needed for other Specified by remote Mac Address of the device Required for protocols that use it No Response The type of response the Server side of Old Data Node Offline response the driver sends when it finds the Zero Data Server node to be offline FFFF Data Not valid for all protocols Timeout The timeout specified for the node 2 seconds The time in seconds after a node goes Recovery Interval off line before the driver tries to poll the 30 seconds device again The length of time communica
75. 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 0 None of these messages are errors 01a RUI SIO Config and system errors will have a banner saying System Error or Configuration Error Figure 4 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 Page 15 of 92 S IG FieldServer Configuration Manual 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 Data 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 Page 16 of 92 IG FieldServer Configuration Manual 4 DESCRIPTOR FUNCTIONS Descriptor functions determine how data is mapped between Data Arrays and the corresponding driver data points
76. escriptor Name Data Array Name Data Array Offset Low Limit High Limit Save Change System Addr Bridget DA NODE ID NEW 0 0 255 Yes In the example above 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 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 7 1 9 4 Example 4 Dynamic Allocation of the connection Baud Rate The Baud Rate on a connection can be dynamically changed from a Data Array Value by one of the following methods Method 1 Using pre mapped Data Array values to Baud Rates By defining the Data Array format as Baud a responsible Map Descriptor can be used to dynamically change the Baud Rate on the associated connection In the Example the below the Baud Rate on the R1 connection will be set to 960
77. essage 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 1 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 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 Delay Line drive On _ Line drive Off P1 9600 8 21 rtu 0 1 0 001 0 001 Page 64 of 92 IG FieldServer Configuration Manual 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
78. 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 Lut List DA Lut List Offset Length Set tck Lut triggers 219 Awt LUT GRF6 0 Set Set tclk 0 zl Page 20 of 92 sierra IG FieldServer Configuration Manual 4 3 7 Read Block RDB This function does a single read at startup only 4 3 8 Active Read Continuous with Offset ARCO This function does a read of length 1 for a range of addresses 4 3 9 Active Read at Startup ARS This function does an active single read on startup or every time the associated node goes online 4 3 10Active Write at Startup AWS This function does an active single write on startup or node coming online 4 3 11 Write block WRB This function does a single write at startup Page 21 of 92 IG FieldServer Configuration Manual 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 f
79. he Wrbcov function operates much the same as a Wrbx but will only write on a value change The write is triggered by a change in value in the associated Data Array If the associated Data Array is updated with the same value a write will not occur The Scan Interval parameter is not required for this function as writes are event driven and not continuous 4 3 5 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 Interval parameter Page 19 of 92 sierra IG FieldServer Configuration Manual 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 element 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 0 and forms a message to write this data to the field device Only certain drivers support require the use use of this
80. ified caused the packet buffer to be exceeded As a result the packet buffer was truncated 10126 0 This is not reported in the current release of the ie B BACNet driver objects An UDP socket buffer overflowed and UDP 10127 data was lost 10128 has pean usad in the Only use KW_N1 and KW_N2 10129 4 USR TAS pe TEPANI fila 10130 UDP broadcast panics has been disabled until a hardwired send is added Tie ane resona queue nas vaen PRISE Check IP addresses in particular the 10133 This is typically the result of a mis configuration on the FieldServer Gateway andriss 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 10210 Info the inet Server received a write to input command that is not supported Page 87 of 92 sierra monitor FieldServer Configuration Manual Error Description Action 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
81. isplay 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 order to conserve memory it is possible to disable the collection 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 FS GUI and will cause zero values to be reflected for all statistics relating to that Map Descriptor in FieldServer Diagnostics 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 02 Map Descriptors Map Descriptor Name Data Array Name Data Array Offset Function Node Name Object Type Instance Option SMD 11 AI 01 DA AI 01 0 Passive Virtual Dev 11 01 Stats SMD 11 MI 02 DA AI 01 I Passive Virtual Dev 11 02 67 92 IG FieldServer Configuration Manual Appendix A 5 DHCP Client Options The FieldServer DHCP Dynamic Host Configuration Protocol Client can be enabled to obtain an IP address lease from a networked DHCP
82. it confirms your S d DA off expectations This message is printed when evaluating a Dynamic parameters task DynParam 6 Err where the function Change System Node ID or DescName s too long Change System MAC Add The maximum length of the descriptor is 32 characters 8 DynParam 7 Err The value extracted from the DA to be used as a dynamic parameter is System Node 1 Validtn out of range based on the low and high values specified Review the failed Lo ld Hi ld validation range in the configuration file and also review your mapping Rqd d Node s Perhaps the DA offset does not contain the new ID 22 ar This is confirmation of a change of a symnica parameter where the function is Change System Node or Change System MAC changed to 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 8 if the platform is not a ProtoCessor It can be ignored 8 Edit the configuration download the modified configuration and reset the FieldServer for the changes to take effect Page 57 of 92 of IC FieldServer Configuration Manual 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
83. k over which data files and messages can be transmitted Networks may be local or wide area Open Systems open systems no single 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 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 PFE Protocol Front End A protocol is a standardized set of rules that specify how a conversation is to take Protocol i M 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 Router protocol such as RIP to move packets efficiently to their destination over an internetwork A router provides greater control 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
84. k Nodes Hubs have moved past their 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 Page 90 of 92 monitor FieldServer Configuration Manual Term Description 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 A network is a system of computers hardware and software that is connected Networ
85. led 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 ID Protocol Port Retry Interval Recovery Interval Dev1 i Modbus RTU P1 0 0 Dev2 2 Modbus P2 0 0 Dev3 S 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 ID Protocol Port Address Type Offline Action PEGSI 12 Modbus P1 ADU Clear data Array PLC 13 i9 Modbus RTU P1 PDU No Action Page 50 of 92 sierra S IG FieldServer Configuration Manual 6 3 2 Node Inactivity Timeout This parameter can be used with Passive Client drivers to let the FieldServer mark the node offline should no messages be received in the set time period Normal node recovery will take place and the node will go online once messages are received again Sometimes it might be required to keep the node always online if for example the FieldServer is connected to a printer port of the
86. ll System Node ID Use is driver dependent Generally used to System station address or identify the FieldServer as a Node when it is 1 System station configured as a Server Displayed where a protocol requires the Network number FieldServer to be assigned a network number 5 e g BACnet Where specified this parameter defines the behavior of the standby FieldServer in Hot Default Standby mode In Mode 1 the FieldServer is Hot Standby Mode dim value completely passive in Mode 2 the standby blank FieldServer polls the connected devices through alternate communication paths Defaul Indicates whether the port expander mode PM Port Expander Mode X value function is enabled or not blank is displ hen this i Cache Map Descriptor Scan Interval TU valle 93920 I olsplayeg b jos 2 seconds error and it indicates that there is no setting Hot Standby Designation Primary or Secondary On boot the primary Primary Page 72 of 92 monitor FieldServer Configuration Manual tries to become the active and the secondary tries to become the standby FieldServer This behavior may be different if the so called secondary FieldServer gets re booted first A name by which a pair of FieldServers configured as a Hot Standby pair is known Default When one of a pair boots it broadcasts Hot Standby Pair Name dee message with its pair name in order to try and blank locate the
87. mple 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 Data Array Name Source DA Target DA Data Format Bit Byte Data Array Length 200 200 Page 28 of 92 FieldServer Configuration Manual Moves Function Source Data Array Source Offset Target Data Array Target Offset Length Bit Pack Source DA 10 DA 2 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 Offset Length Bit Move 5 DA 0 8 Target DA 0 T3 5 2 7 Bit Extraction Application Example Assume a Liebert device has been set up as follows Bits 0 10 are each used to specify a unique event and each has a corresponding integer value determined by the binary contribution it makes to the integer value For example bit 10 has an integer value of 10
88. n along with the next defined operand Note Output of LTE GT LT EQ NE AND OR and NOT is binary either 1 or 0 AND OR and NOT work the same way as Logic The following fields are specific to the Math amp Logic definition DAI DAI4 input Data Arrays 1 through 4 input Data Array offsets 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 i setting 5 3 3 Math Usage Example Math Task 105 51 Task Name 5 Interval DAM DOM DAI2 DOI2 DAIS DAIA DOI4 FN1 2 FN3 4 DAO DOO 0 DA2 1 2 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 4 3 Math Task Name 5 Interval DAI1 DAI2 DOI2 DAI3 DOIS DAl4 0014 FN1 FN2 FN3 FN4 DAO DOO Task 105 il DA_1 0 DA_2 1 DA_3 2 DA_4 3 Div Sub Mult Sq DA_5 21 This definition will result in the following operation DA_5 21 DA 1 0 DA 2 1 DA 3 2 DA 4 3 Page 37 of 92 IG FieldServer Configuration Manual Math Task Name Scan Interval DAI1 DAI2 DOI2 FN1 DAO DOO Task 105 1 1 0 2 0 P
89. n 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 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 Page 60 of 92 IG FieldServer Configuration Manual FieldServer Server Device Status Node Online Retries Status Node Offline Probation Delay Status Node Online Figure 12 FieldServer Timing Diagram Page 61 of 92 sierra IG FieldServer Configuration Manual 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 asserting 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 specifie
90. ng Page 74 of 92 monitor FieldServer Configuration Manual Keyword Description Bit 1 HSB Active LED Bit 2 Node Offline LED Bit 3 Configuration Error LED Bit 4 2 System Error LED Get System Time This parameter is used to access the system clock by using a Data Array The suggested Data Array format is UINT32 with a minimum length of 9 The Data Array will contain the current system time in the following format Offset Description 0 Seconds since 1 Jan 1970 00 00 00 1 Milliseconds past the second 2 Year e g 2014 3 Month 1 12 4 Day 5 Hour 6 Minute 7 Seconds 8 Milliseconds Appendix C 4 4 Connections Adapters Section Title Connections Column Title Port Connection rotocol aud arity Data Bits top Bits Line Drive Off Line Drive On Ic Timeout Turnaround Delay Turnaround Time Function Legal Values Specifies the port through which the device is connected to the FieldServer Adapter is used for Ethernet andhardware P1 P8 R1 R2 connections and port is used for serial The name of the protocol used by this connection Specifies Baud Rate 300 9600 38400 Specifies serial data byte parity Even Odd None ets number of data bits for serial port 7 S Sets the stop bits for communications 1 2 When using RS 485 specifies delay from end of message Time in seconds 1 fo wren tne RTS ine
91. ntain 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 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 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 11 0 The Data Array named SDA1 must have been 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 previously defined in the configuration file or else there will be a configuration error 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 0 5 6 5 Example 2 Load a Value Effect of Target Data Array Format
92. nvalid hot standby mode has been 10106 specified as of the FieldServer check hsb_p s ini files parameters Could not create cache block possibly 10107 because the maximum number of Contact FST data points 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 10111 Hot Standby partner discover found an API Version mismatch 10112 Hot Standby partner discover found a DCC version mismatch Page 86 of 92 sierra monitor FieldServer Configuration Manual Error Description Action Hot Standby partner discover found a 10113 TM config file mismatch 10114 A Node ID 255 was used in the Hot Standby commbit configuration The Gateway Address for adapter N1 has 10117 not been specified This FieldServer will only be accessible on the local TCP IP subnet The NETMASK for adapter N1 or N2 has 10118 not 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 10119 has not 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 Check that the Ruinet and Kernel versions received match In the BACNet driver the OPTION LIST 10125 spec
93. ock on Change of Value 19 4 3 5 Write Block Continuous WIDC esses nnns nnns 19 4 36 Active Write on Trigger AWT esee nennen nnne nnne ener 20 4 8 7 Head Block 21 4 89 8 Active Read Continuous with Offset 21 4 8 9 Active Read at Startup ARS sss eene en rennen nna 21 4 3 10 Active Write at Startup 5 2 2 0000000000000000000000 enne 21 4 3 11 Write block WHRB siiis ssiss sienne ntn nnns nnne et rh 21 5 Data Manipulation 22 ME MOV GS M M 22 SLI Simple MOV6S ses ed det ee tee 23 5 1 1 1 Simple Move 23 5 1 1 2 Special Application Grouping 22 24 5 1 1 3 Special Application Separating Responsible Map Descriptors 25 5 1 1 4 Special Application Creating LonWorks SNVT Switch from 2 Modbus registers 25 5 2 Function Moves Type Casting ssssssssssssssssseee enne
94. on Manual 5 4 Logic Logic functions implement Boolean functions True False statements 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 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 0011 DAI2
95. part e g 0 1 1 01 1 123 456 A Stringf One of the following Preload Data Format Data Array Format Data Format This parameter tells the kernel how to interpret and apply the value specified using the Preload Data Value parameter not to be confused 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 characters unknown 6 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 7 Must be specified as String if Preload Value is String Page 42 of 92 IG FieldServer Configuration Manual 5 6 3 Limitations and Operational Considerations e Each Data Array location to be preloaded requires its own preload line in the configuration file value specified must be compatible with the format of the Data Array e g Integer arrays cannot be preloaded with numbers that co
96. peration 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 0 Page 27 of 92 SMG monitor FieldServer Configuration Manual Parameter Function The function extracts bits out of the source Data_Array Registers at the Data Array offset Bit Extract specified The 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 straight move is performed The function extracts the binary version of ea
97. plements for configuration information on the drivers Appendix C 2 Default settings for parameters Parameter Default Setting Default response timeouts 2000 ms 2 sec 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 Page 70 of 92 monitor FieldServer Configuration Manual Appendix C 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 Format used to store Floating Point Analog values e g temperature volts 16 bit Integer Pleat Each point 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 16 Signed 16 Range 32768 to 32767 discrete Each point in the array represents one bit Integer integer Uinti6 Unsigned Range 0 to 65 535 discrete Each point in the array represen
98. rce Data Array values to be moved to consecutive target locations starting at the respective offsets If a task name is specified the move operation becomes a continuous task on the 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 is specified Defines move functionality e g byte order manipulation Functions are summarized in Error Reference source not found The name of a Data Array to be used for conditional moves See Section 5 1 1 3 for more information The offset into the Conditional Data Array where the conditional bits for the Conditional Offset move 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 Length Task Name Scan Interval Function Conditional Data Array Page 22 of 92 monitor FieldServer Configuration Manual 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 Simple Move Example Data Arrays Move is reversible Data Array Name Data Format Data Array Length meaning data can move Source DA Float 200 from Target DA to Target DA Float 200 Source
99. rmat Array Length Both Data Arrays are DA 1 FLOAT formatted as FLOAT and are DA 2 FLOAT therefore capable of storing the value 257 Preloads Data Array Name Preload Data Value Data 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 20 Preloads Data Array Name Preload Data Value Preload Data Format Preload Data Index DA 1 ABCDEFGHIJKLMNOPQRSTUV String 0 45 92 monitor 5 7 Loading Data Array Values from the FieldServer s Non Volatile Memory 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
100. server Currently the DHCP hostname option can be enabled to report the FieldServer s network hostname to a DHCP Server This is done by creating a text file named hostname ini containing a single line of text e g Boiler Bridge A This file must be sent to the FieldServer and restarted to take effect This hostname will be visible in the DHCP Server s list of IP leases and could be optionally manually added to a DNS server a Static lease IP Address should be reserved in the DHCP Server in order to address the FieldServer by its hostname For more information on enabling the FieldServer DHCP Client refer to the FieldServer GUI Manual Page 68 of 92 IG FieldServer Configuration Manual Appendix Troubleshooting Appendix B 1 Moves performance Suppose we need to read 1000 points from a PLC and transfer it to another data array there are several ways to do it using moves The table below shows the impact on the time it takes to complete the moves using different configuration methods Map Leno Operations Memory locations Performance degrade Descriptor transfer because of Moves 1 1000 1 1000 1 1000 None 1000 1 1000 1 1000 1000 None 1 1000 1000 1 1000 1000 Some what 1000 1 1 1000 1000 1000000 Too Much Page 69 of 92 IG FieldServer Configuration Manual Appendix C Reference Appendix C 1 Working with the Driver Manuals Appendix C 1 1
101. sierra monitor FieldServer Configuration Manual This manual provides instructions for the following FieldServer products Description FS X30 Series FieldServer QuickServer FieldServer APPLICABILITY amp EFFECTIVITY Effective for all systems manufactured after March 2015 Kernel Version 6 17 Document Revision 1 S IG FieldServer Configuration Manual Contact Information Thank you for purchasing the FieldServer Please call us for Technical support of the FieldServer product Contact Information Sierra Monitor Corporation 1991 Tarob Court Milpitas CA 95035 Contact number 1 408 262 6611 1 800 727 4377 Email info sierramonitor com Website www sierramonitor com Contact Information S IG FieldServer Configuration Manual TABLE CONTENTS 1 Fi ldServ r 2 2 50 Seeedenaetesenestedeessaitezcuceseaae euattssceeteauesesttenscueexeceees 7 1 1 Maires Teile i PEE EE A E ended nl Sind E T 7 1 22 A S 7 1 3 Terminology 7 1 3 1 NODOS ees lisse partie ieee 7 7 22 CGlentsand Servers tse dd Fe ta 8 2 Overall Operation 9 3 Getting Started Basic Configuration
102. t aeration indicated 3 45 20 Spacing indicator 4 i 43 20 Zeromatc channel fault 5 42 20 Empty Pipe 6 li 37 20 hi lo flowrate 7 00 00 00 00 comm Error 8 None of the above 111 Page 32 of 92 monitor FieldServer Configuration Manual 5 2 9 1 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 the Table string Table Index Value 1 16 pattern matches The pattern is the delimiter which separates tokens Table String in a pattern and should not be considered 1 10 000 as part of pattern means ignore this token The number of Data Array items to be Number of tokens in table string Length used to build the pattern to compare with should be the same as length under Moves 1 Table user value defined by the applicable driver protocol eg for Bacnet Table User Value 0 normal 0 65 535 1 alarm 2 fault Offset_Table Offset Table Name Table String Table Index Value Iable User Value Length SPR4052 37 46 46 20 0 10 4 SPR4052 36 20 a 20 4 SPR4052 45 20 12 30 4 SPR4052 43 20 29 40 4 SPR4052 45 20 4 50 4 SPR4052 43 20 5 60 4 SPR4052 42 20 6 70
103. t Offset Length Join Float Source DA 0 Target DA 40 T5 Ten 16 Bit Integers are taken from Source DA Length refers to the data type referenced in the Function eg If n is the value shown in Length then and combined in two s to make up 5 floating point 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 number of bits to be moved in the move o
104. t is recommended that the CONFIG CSV file be backed up before editing Once edited the file can saved and uploaded in the Graphic User Interface see FieldServer GUI Manual for details Refer to Appendix C 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 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 with 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 in
105. tarts 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 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 Data Array Offset Preload Data Index Location Data Array Location Data Array Index Buffer Offset The location in the Data Array to be preloaded Data Array Name configuration file and its definition must precede vp dd 5 characters the preload that references it If not System Error Message 10117 will be printed One of the following 0 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 be specified with a fractional
106. te is blocked A message willlinteger 0 be displayed when blocking occurs except if the Queue 0 Only 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 has the benefit of making Enabled Yes the signals cleaner in a noisy environment but may reduce Disabled No the maximum number of devices possible in a multidrop configuration The minimum amount of time that must pass between one Client Map Descriptor completing its task and the next i 05 seconds Client Map Descriptor being serviced Refer to Driver Manuals Low Pri Poll Delay The poll delay used for lower priority Map Descriptors Protocol dependent When an upstream device polls the FieldServer and the data is unavailable or too old the driver generates a poll to Server Hold Timeout the downstream device for fresh data port expansion The Server Hold Timeout defines the time available for this transaction to complete before an error is returned PF 2seconds Bias Mode An IP address for the connection if applicable A remote IP address for the connection if applicable The timeout defined for the connection The time after a node goes off line before the driver tries to 30 seconds poll the device again The length of time communication needs to be re established for before an offline Client node is marked on line again 1 _
107. 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 Column Title Function Legal Values Provide name for Data Array Data Arrays Data Array Name Data_Format Data Array Length Data_Array_Function DA Comm OK Bit 256 Node Status Page 47 of 92 sierra IG FieldServer Configuration Manual 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 Column Tie Funetion Tegal Values Up to 15 alphanumeric characters Data Format Provides data format BIT Data Array Length Number of Data Objects Minimum of 256 bits Data Array Function Special function for the Data Array Alias Node Status None 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 based on the Node s status Data Arrays Data Array Name Data Format Array Length
108. the Node to be declared If subnets are not used this parameter can be excluded SURGE If specified as the subnet is ignored and all Nodes will d 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 1 Node on Net1 Bit 30 Node Online Bits 41 Node on Net2 Bit 30 Node Online Bits 10 22 Node on Net3 Bit 30 Node Online Bits 10 9 Node on Net4 Bit 30 Node Online Bits 5 10 4 Node on Net5 Bit 30 Node Online Bits 10 25 Page 49 of 92 sierra IG FieldServer Configuration Manual 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 seconds 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 instal
109. 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 device 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 3 Note that not all functions are supported by all drivers Refer to the specific Driver Manual for information on functions supported by individual drivers Page 17 of 92 FieldServer Configuration Manual 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
110. tion Probation Delay needs to be re established for before 1 minute an offline Client node is marked on line again Server An alternate to specifying the IP address Typically used when the user wants two nodes to talk to each other When specified the FieldServer sends out a broadcast with the server name and uses the reply to fill in the IP address for the node Until the reply has been received all polling for the node is disabled The server name given should correspond to the pair name specified in the remote FieldServer s bridge settings Only applies to the SMT protocol Alias Node ID This is used to distinguish between different nodes connected to the FieldServer when a PLC does not support the allocation of different None ID s Each node is given a different alias Upstream devices poll the Alias Node ID and the FieldServer routes the poll to the correct PLC which is polled using the Node ID Any enteture Ports For hot standby operation This field is used to control which port on a PLC to look in hot standby section Page 80 of 92 monitor FieldServer Configuration Manual Section Title Nodes Column Title Function Legal Values poll Appendix C 4 6 Map Descriptors Section Title Map Descriptors Column Title Function Legal Values Map Descriptor Name Used to identify a
111. to network users A Server Server typically 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 is the protocol suite developed by the Advanced Research Projects TCP IP Agency ARPA and is almost exclusively used on the Internet It is also widely Transmission Control Protocol Internet Protocol 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 Page 91 of 92 monitor FieldServer Configuration Manual Term Description 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 Page 92 of 92
112. to the FieldServer and tested in much the same way Open an MS DOS prompt and navigate to the directory containing the configuration file Type mb8sim exe c 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 To ignore a block use the ignore keyword at the start and the process keyword at the end of the block To ignore individual lines use 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 Page 14 of 92 FieldServer Configuration Manual c Command Prompt mb8sim cconfig csv Main Menu 2 config csv Fieldserver Information ew Down oad figuration to Fieldser Upload Configuration from Fieldser Change IP Addre ange UI Dis Mods Restart Field er 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 4 Take note of System Errors or Configuration Errors These indicate configuration problems in the configuration file Note a number of System Overrun
113. tocol not detected Check Node Name in csv file Confirm that Active Map Descriptors are not 10010 No connection defined for an existing added to a Server Node Physical 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 10014 BYTE Data Array Check Map Descriptor Offset length count 10016 Could not find or create Node check Mona Mama Noga IE and Protea CSV file 10019 Check CSV file spelling 10023 Protocol or Node Name for Map Descriptor Check CSV file not detected 10025 Dore Increase the timeout on the Modbus TCP Client receiving a response to a poll 10026 There is no connection to one side of a Ensure that a Client and a Server is configured virtual wire for each virtual wire 10027 Connection mode of Hot Standby Data only supported in Hot Standby Mode1 10028 Could not find nor create a Node Refer to 10010 10081 The data points limit on the FieldServer Contact FST has been reached A Server Node has been assigned to a 10032 Client Map Descriptor OR a Client Node Check CSV file does not have a connection Server Name Invalid length specified for TEM 10033 Cable Status Bits See specification in Enote0002 An attempt to generate a write cache block 10034 failed because the Nod
114. tor to module number A Cerberus mapdesc maps to 11011 store the incoming event The error f addresses from module 256 0 to module 256 message reported the events panel anid device n mbers length 1 e g the following addresses are defined for mapdesc of module 15 and length 4 15 256 0 15 256 1 15256 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 SystemsPlus panel replied with Not Refer to the SystemsPlus user manual to set up Monitored when the driver tried to edit read the alarm for monitoring in the panel This 11012 i i scan alarm or tried to read alarm status message can only be solved in the panel and is The driver message screen records the not a driver problem specific alarm s name ALBAGOBEEBIel packet was aceea on If BACnet comms fail check the configuration 11013 a network adapter that is not configured in and network connection the CSV file Message will be ignored 802 3 Hot Standby packet was 11014 received on an incorrectly configured network adapter Packet will be discarded 11015 GE SRTP SD016 message indicates NAK error Page 89 of 92 SMG FieldServer Configuration Manual
115. ts one integer SInt32 Signed 32 Range 2147483648 to 2147483647 discrete Each point in the array bit Integer represents one integer Uint32 Unsigned Range 0 to 4294967295 discrete Each point in the array represents one 32 bit Integer integer Baud Format used to dynamically change the Baud rate on a connection refer to Section 7 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 0 and 1 despite the type conversions This can be overcome using Moves refer to Section 5 2 Appendix C 4 Permissible Values for Configuration File Variables Default and acceptable values for the different variables defined in the configuration file Optional Values ate indicated with an asterix 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
116. ual Appendix C 4 3 Data Array Function The Data Array Function Keyword is used in the configuration file to get system specific error conditions and statistics The available keywords are listed below Keyword Description Node Online Bits Node Error Bits Bit 0 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 Status Bits See Enote0002 Hot Standby Status Bits See Enote0002 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 0 Device handle 1 Node port 2 connection 3 old station 4 station Chan Detail Stat Connection information f 0 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 0 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 repe
117. ue 0 Data Array High Scale Scaling max in Data Array Any signed 32 bit floating point value 100 Node Low Scale Scaling zero in Connected Node Any signed 32 bit floating point value 0 Node High Scale Scaling max in Connected Node Any signed 32 bit floating point value 100 i 5 5 1 41 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 Page 40 of 92 sierra monitor FieldServer Configuration Manual 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 possible 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 floating point value 0 Source High Scale Scaling max in
118. ues 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 number 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 Remote Address The remote IP address used by this node Required for protocols that use it Specified in the configuration file as the Node PLC Type Consult the driver manual Required for protocols that use it for additional information Port Port number for a serial connection Readback Option This Client Side paramet
119. y relevant to Servers as Clients will in any event disregard any spurious data received after a response Legend Line_drive_on 2 Line drive off G Squelch timer TX Squelch timer RX olen Turnaround_delay delay Squelch received by master after poll Deleted by Squelch_timer_TX Squelch received by master after Deleted by Kernel before next poll 1 Squelch received by slave after poll Deleted Squelch timer RX CResponse D Squelch received by slave after response Deleted by Squelch_timer_TX Figure 13 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 Page 63 of 92 FieldServer Configuration Manual 9 2 1 Setting Parameter Values It is important to prevent 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 m

Download Pdf Manuals

Related Search

Related Contents

T'nB DCTRIPPERBK  IBM THINK PAD THINKPAD 390 User's Manual  Bedienungsanleitung  AirLive CoreNVR 9/16 CMS Manual  Samsung 19 colių juodas LED monitorius Vartotojo vadovas  

Copyright © All rights reserved. Failed to retrieve file