| Driver Manual |
6.5Driver Stats
In addition to the standard FieldServer communication statistics described in the FieldServer User’s Manual the Optomux Driver can also expose some driver statistics by writing data to a data array. A special map descriptor is required. The driver recognizes the map descriptor by its name which must be
The following example shows how this special map descriptor can be configured.
Nodes
Node_name, Node_ID, Protocol
null_node, 0 | , Optomux |
Data_Arrays
Data_Array_Name, Data_Format, Data_Array_Length
OPTO22_STATS , UINT32 , 300
Map_Descriptors
Map_descriptor_Name, Data_Array_Name, Node_name, length
, OPTO22_STATS , null_node , 300 |
When the driver sees this map descriptor it uses the data array SK_STATS (in this example) to store driver specific statistics. Only one of these map descriptors may be specified per FieldServer.
The driver stores the following data.
Array Element | Contents |
|
0 | OPTO_STAT_BAD_FUNCTION | The Opto22_Function has a |
|
| bad value. |
1 | OPTO_STAT_DYNAMIC_MASK | Mask cannot be specified in a |
|
| CSV file with a zero value. |
2 | OPTO_STAT_TIMEOUT |
|
3 | OPTO_STAT_STREAMING |
|
4 | OPTO_STAT_NAK |
|
5 | OPTO_STAT_PROTOCOL |
|
6 | OPTO_STAT_IC_TIMEOUT |
|
7 | OPTO_STAT_DEVICE_MSG_RECD |
|
8 | OPTO_STAT_DEVICE_BYTES_RECD |
|
9 | OPTO_STAT_DEVICE_FUNCTION |
|
10 | OPTO_STAT_NO_START |
|
11 | OPTO_STAT_MSG_IGNORED |
|
12 | OPTO_STAT_POLL_MSG_SENT |
|
12 | OPTO_STAT_POLL_BYTES_SENT |
|
FieldServer Technologies 1991 Tarob Court, Milpitas, California 95035 (408)
Visit our website: www.fieldserver.com
Page 25