The System Monitor communication driver gets information about the local system, such as the processor, memory, hard disk, and network information. When running a distributed application, the metrics will refer to the server computer. Using the Channel remote execution, you can get information from other computers running the application.

Summary Information

Communication Driver Name: System Monitor

Current Version: 1.0.0.0

Implementation DLL: T.ProtocolDriver.SystemMonitor.dll

Max number of nodes: Only one node can be defined to each channel

Supported Operands:


OperandRead WriteData TypeAddress Size
ProcessorYes
Real8 bytes
MemoryAvailableYes
Real8 bytes
MemoryInUseYes
Real8 bytes
MemoryTotalYes
Real8 bytes
MemoryPhysicalAvailableYes
Real8 bytes
MemoryPhysicalInUseYes
Real8 bytes
MemoryPhysicalTotalYes
Real8 bytes
HDWriteBytesPerSecondYes
Real8 bytes
HDReadBytesPerSecondYes
Real8 bytes
NetDataReceivedBytesPerSecondYes
Real8 bytes
NetDataSentBytesPerSecondYes
Real8 bytes



Point Configuration

The syntax for the Ping address points is: <Property>  

Where:

You can map each property to a Tag in the application, or you can define only one line under Edit > Device > Points, mapping the entire data structure to a Template Tag

In order to use template tags: 



Troubleshoot

The most common error is related to the Windows cache of the performance counter. To recover the system, execute the following commands in the Command prompt while running the prompt with Administrator privileges: C:\windows\system32>lodctr/r


If you still have this error: Error: Unable to rebuild performance counter setting from system backup store, error code is 2

Then, you should run:

The expected message is: 


The status of the driver's execution can be observed through the diagnostic tools, which are:

• Trace window
• Property Watch
• Module Information