Summary of the content on the page No. 1
A Sierra Monitor Company
Utility User Manual
Ruinet
APPLICABILITY & EFF ECTIVITY
Effective for all systems manufactured after Ma y 1, 2001
Version: 1.10
Rev. 10
Summary of the content on the page No. 2
Ruinet Utility User Manual Table of Contents TABLE OF CONTENTS 1. GENERAL OVERVIEW .....................................................................................................4 1.1. PC Requirements ...........................................................................................................4 1.1.1. Hardware.................................................................................................................4 1.1.2. Software .....................
Summary of the content on the page No. 3
Ruinet Utility User Manual Table of Contents Appendix B.2. Connecting to a FieldServer using Name -y..................................................37 Appendix B.3. Broadcast Mode -ib .......................................................................................37 Appendix B.4. The Most Recently Connected FieldServer -p ..............................................37 Appendix B.5. Disable Auto Connect Mode –m0...........................................................
Summary of the content on the page No. 4
Ruinet Utility User Manual Page 4 of 46 1. General Overview The Ruinet Utility is used to: • Transfer files (configuration, firmware, etc ) to and from a FieldServer • Monitor a working FieldServer’s internal data and parameters • Change or update a FieldServer’s internal data and parameters • Delete files on a FieldServer • Restart a FieldServer 1.1. PC Requirements 1.1.1. Hardware Ruinet works over an Ethernet network so a TCP/IP enabled PC with a network card is req
Summary of the content on the page No. 5
Ruinet Utility User Manual Page 5 of 46 2. Remote User Interface (RuiNet) The notes in this section explain how to navigate the menu system provided by RuiNet and provide information on the contents of the various screens. 2.1. A – Connecting to a FieldServer Since RuiNet can only work with one FieldServer at a time, it is necessary to target the FieldServer of interest. (Note that it is possible to run multiple instances of RuiNet at the same time). If RuiNet is run with
Summary of the content on the page No. 6
Ruinet Utility User Manual Page 6 of 46 FieldServer Name. (Specified in ‘FieldServer, Title’ section of the CSV file). Press one of these keys to select the option. List of other action keys. Some of these keys only work in Expert Mode. Read the Advanced Notes on Tiers. Figure 2.2 2.2. B - FieldServer Information FieldServers were previously known as bridges, hence the use of the B key to access the screen displaying general information about a FieldServer. The B Scre
Summary of the content on the page No. 7
Ruinet Utility User Manual Page 7 of 46 2.2.1. FieldServer Information – Settings Aspect Parameter Description FieldServers have the ability to run as “multiple” FieldServers on one platform. To differentiate between the different running Tier applications, each of the applications is referred to as a Tier with a specific name. FieldServer_Name A name by which a FieldServer is identified - need not be unique. N1 IP Address The IP address of the N1 Ethernet Adapter. N1 Net
Summary of the content on the page No. 8
Ruinet Utility User Manual Page 8 of 46 2.2.2. FieldServer Information – Status Aspect Parameter Description FieldServers have the ability to run as “multiple” FieldServers on one Tier platform. To differentiate between the different running applications, each of the applications is referred to as a Tier with a specific name. The part of the FieldServer firmware that contains the drivers ordered. Driver Configuration Each combination of drivers is known as a DCC. A DCC ver
Summary of the content on the page No. 9
Ruinet Utility User Manual Page 9 of 46 Parameter Description shipped without the time or date set and hence the value shown here is meaningless until the FieldServer time is synchronized with the computer’s. 2.3. O - Connection Overview This is one of the most important information screens provided by RuiNet. It supplies information on communication between the FieldServer and remote devices. A number of aspect screens are available, and some of the aspect screens have more
Summary of the content on the page No. 10
Ruinet Utility User Manual Page 10 of 46 This is the aspect name “Settings”. An aspect is a collection of related information. To view next connection, use the arrow keys. See a filtered list of nodes which displays only those nodes which are using the connection currently displayed on the screen. Figure 2.5 – Connection Overview – Settings aspect – Page 1 FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com Tel: (40
Summary of the content on the page No. 11
Ruinet Utility User Manual Page 11 of 46 2.3.1. Connection Overview – Settings Aspect. Parameter Description Connection The current connection out of the total number of connections. Adapter An adapter ID is displayed if the driver is an adapter driver. The minimum amount of time that must pass between one Client Map Poll_Delay Descriptor completing its task and the next Client Map Descriptor being serviced. Refer to Driver Manuals. Low_Pri_Poll_Delay The poll delay used f
Summary of the content on the page No. 12
Ruinet Utility User Manual Page 12 of 46 Parameter Description Application 2.3.2. Connection Overview - Status Aspect Parameter Description Connection The current connection being displayed out of the total number. The use of this variable to determine timeouts is driver dependent and has no consistent meaning. In passive drivers this variable may not have been used Timer at all. In simple poll response drivers this variable should decrease from its maximum (equal tim
Summary of the content on the page No. 13
Ruinet Utility User Manual Page 13 of 46 2.3.3. Connection Overview - Statistics Aspect Connection statistics are a roll-up of all the statistics maintained by the Nodes and Map Descriptors using the connection. For example: If three Map Descriptors use a single connection then each time a message is sent for each Map Descriptor, the Map Descriptor, Node and connection statistics are all updated. Thus response time statistics are more meaningful when viewing individual nodes
Summary of the content on the page No. 14
Ruinet Utility User Manual Page 14 of 46 Parameter Description The number of times a cache Map Descriptor containing outdated Cache - Created data has been polled resulting in the creation of a new cache Map Descriptor. See Error! Reference source not found. The number of expired cache blocks. See Error! Reference Cache - Bumped source not found. Writes are never cached - the external device is put on hold while the FieldServer resends the message to the PLC and waits f
Summary of the content on the page No. 15
Ruinet Utility User Manual Page 15 of 46 Parameter Description Avg Passthru Response Time TCP Conn Lost Number of times a TCP connection was lost or interrupted. TCP Send Failed Number of times a message sent on TCP connections failed. FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com Tel: (408) 262-2299 Fax: (408) 262-9042 Toll_Free: 888-509-1970 email: support@fieldserver.com
Summary of the content on the page No. 16
Ruinet Utility User Manual Page 16 of 46 2.3.4. Connection Overview - Error Statistics Aspect Parameter Description Connection The current connection being displayed out of the total number. Pex mode tried to create a cache block and failed - normally a PEX No slave failed write-through. See Driver Manual for further information A message arrived from the upstream device while the server port Server Overruns was on hold. Increase the timeout setting in the external devic
Summary of the content on the page No. 17
Ruinet Utility User Manual Page 17 of 46 Parameter Description external device trying to access it. Messages received but unable to be processed - normally Msg Ignored because the driver has not implemented functionality for that message. The number of times that Data Arrays were cleared after a Sys Cleared system-normal type message was received from a device (e.g. fire alarm panel) The number of bytes received during the squelch timing period 2 Squelch TX started when RTS
Summary of the content on the page No. 18
Ruinet Utility User Manual Page 18 of 46 Parameter Description Connection The current connection being displayed out of the total number TX bytes Number of bytes sent. TX packets Number of packets sent. Number of packets not sent for reasons that include the transmit buffers TX dropped being full. TX errors Errors during transmission such as hardware errors. RX IP fragments The number of IP fragmented packets received. Collisions Number of collisions - the network is to
Summary of the content on the page No. 19
Ruinet Utility User Manual Page 19 of 46 Parameter Description RX IP not for us The number of received IP packets not meant for the FieldServer. Max RX buffers used The maximum number of receive buffers used since restart. Rx buffers in use The number of receive buffers currently in use. 2.4. N - Node Overview Node number - type number to go to Every attempt is made to standardize the way detail for that node, e.g. type 02 to in which drivers report stats but in some dr
Summary of the content on the page No. 20
Ruinet Utility User Manual Page 20 of 46 2.4.1. Node Overview - Settings Aspect Parameter Description Node The current node being displayed out of the total. Adapter The adapter name where a node is connected to an adapter. Node_Name The node name specified in the CSV file. The station number or address of the node. The actual meaning is Node_ID dependent on the driver and protocol – refer to the Driver Manual. The protocol being used to update the data for that node.
