The interface used for monitoring events, such as interrupts.
Namespace:
Quanser.HardwareAssembly: Quanser.Hardware.Hil (in Quanser.Hardware.Hil.dll)
Syntax
| Visual Basic (Declaration) |
|---|
Public Interface Monitor |
| C# |
|---|
public interface Monitor |
| Visual C++ |
|---|
public interface class Monitor |
| JavaScript |
|---|
Quanser.Hardware.Monitor = function(); Quanser.Hardware.Monitor.createInterface('Quanser.Hardware.Monitor'); |
Remarks
The monitor functions are similar to the task functions. Monitors track events asynchronously as a separate "task". Monitors may be regarded as separate "threads" that run asynchronously in the background. Unlike tasks they are not periodic, but respond to events, such as interrupts. The implementation depends on the underlying driver and data acquisition card. The user can create a monitor, start and stop the monitor, and read the states of events from the monitor. Monitors are created using the MonitorCreateInterruptReader method listed in the Hil remarks.
The monitor functions are:
| Method Name | Description |
|---|---|
| Start()()() | Starts a monitor. |
| ReadInterrupt(array<SByte>[]()[]) | Reads the state of the interupts being monitored. This function blocks until an interrupt occurs or Stop()()() is called from another thread. |
| Stop()()() | Stops a monitor. |
| IsValid()()() | Checks whether a monitor is valid. |
See Also
