|
Status |
||||||||
|
Device diagnostics and status information
|
||||||||
|
Shows
device status and allows for driver and controller re-initialization along
with test functions. |
||||||||
|
Function |
Description |
|||||||
|
|
Shows
the actual controller type in use. |
|||||||
|
|
Indicates,
as best as possible, if the device is connected. For serial controllers this
may be difficult to determine. |
|||||||
|
|
A
device may need the driver to send firmware commands to the device to be
initialized and ready for use. The macro is shown, and can be edited, in the
UPDD Advance Console. The status of the macro processing is shown as
follows: |
|||||||
|
|
|
No
macro is defined. |
||||||
|
|
|
Indicates
the macro was sent to the device but the driver is not expecting a response
so cannot indicate the success of the controller initialisation. |
||||||
|
|
|
The init macro contains an ACK statement but a valid acknowledgement
was not seen from the device within the specified time. |
||||||
|
|
|
A red
cross indicates that the driver is not loaded or an error was encountered
during controller initialization. If the driver is loaded but the device is
not functioning the most likely cause is that the specified port resource(s)
are already in use by another process or the port is not available. |
||||||
|
|
Sync
errors indicate that the driver is experiencing some form of error with the
hardware port or received data packets. This value should be zero or very
low. Any high counts will imply an error is occurring that may affect
performance of the pointer device. This could indicate the controller is
running at a different baud rate to that defined in UPDD settings or the
controller is transmitting some data packets not recognized by the driver. |
|||||||
|
|
This
function reinitializes the controller. The macro, if defined, is sent to the controller. |
|||||||
|
|
This
option resets the sync error count. Only enabled if error count > 0 |
|||||||
|
|
This
function reloads the driver. This could take a number of seconds to perform. |
|||||||
|
|
Invoke
the test screen. |
|||||||
|
|
Invoke
the test grid. |
|||||||
|
|
Dump driver settings to a file. The file is useful for support purposes but can also be used in subsequent installs to define the initial settings. |
|||||||
|
|
||||||||