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. | ||
Driver Configuration | The part of the FieldServer firmware that contains the drivers ordered. | ||
| Each combination of drivers is known as a DCC. | ||
| A DCC version number is allocated to each DCC. This version increases | ||
DCC Version | with changes/updates to drivers. Tech support are able to track a DCC | ||
version to determine what features of each driver are available and what | |||
| |||
| bugs may have been present in a particular version. | ||
Kernel Version | The version number of the kernel. The kernel is that part of the firmware | ||
that provides support and resources to the individual drivers. Tech support | |||
| may require this number. |
| |
BIOS Version | The version number of the FieldServer’s BIOS. This seldom changes. | ||
| Each FieldServer has a combination of drivers and a maximum number of | ||
| data points that may be managed. A data point is an element of a Data | ||
Data Points Used | Array with a responsible Map Descriptor. | Responsible Map Descriptors | |
are client side, active and almost always read Map Descriptors. | |||
| |||
| Example: A CSV file configured with a RDBC Map Descriptor with a length | ||
| of 100 may use 100 data points. If the number of points used exceeds the | ||
| maximum then the FieldServer will continue to operate for 24 hours and | ||
| |||
| then shutdown. See Enote024 for details on point count. | ||
| The file slots.ini controls the maximum number of data points. Only use | ||
Data Points Max | slots.ini supplied with the FieldServer or by tech support. The user cannot | ||
edit or generate this file. The default for an X40 is 1000 points. The | |||
| |||
| default for an X20 is 500 points. The FieldServer bridge ID must be | ||
| provided to tech support for them to generate a new slots.ini file. | ||
|
| ||
Cycles Now | Number of times the FieldServer executes all its software per second. This | ||
number will change continuously. |
| ||
|
| ||
Cycles Max | The maximum value since the FieldServer started. | ||
Cycles Min | The minimum value since the FieldServer started. | ||
Avg Cycle Time | The average time in milliseconds the software took to complete since last | ||
restart. Cycle timers are only started after the CSV files have been loaded. | |||
| |||
Min Cycle Time | The minimum/maximum time in milliseconds the software took to complete. | ||
Max Cycle Time | Use the R key to reset this value. |
| |
Cache Age Ave1 | The average data age of the cache blocks currently in existence. | ||
Cache Age Max1 | The maximum data age of the cache blocks currently in existence | ||
Cache Age Max | The maximum data age of cache blocks that existed on the FieldServer | ||
Ever1 | since startup, i.e. the oldest that cache data ever got. | ||
Cache usage (RDB)1 | The number of active cache blocks reading data at the current time. | ||
Cache usage (WRB)1 | The number of active cache blocks writing data at the current time. | ||
Memory Blocks | The number of memory blocks reserved | by drivers and other system | |
functions. |
| ||
|
| ||
Last Time Rebooted | The time that the FieldServer was last restarted. New FieldServers are | ||
1Cache blocks are temporary Map Descriptors created by the FieldServer to achieve certain objectives such as a write through or port expansion. Because they are temporary this number rise and fall is not visible. The read cache blocks persist until they expire after the cache_age_to_live time has expired.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com Tel: (408)