What is a diagnostic?
How to Run Diagnostics for UPDD Issues
What is the UPDD diagnostics procedure?
The diagnostics procedure is used to gather information that will help Touch-Base diagnose issues you may be having with the UPDD driver.
How do I start the diagnostics?
There are three ways to invoke it:
- UPDD Console
- Command line
- UPDD Test program
For Linux users, invocation of the diagnostics routine is clarified in https://support.touch-base.com/Documentation/50376/Running-UPDD-tools-from-a-terminal?Keywords=Running+UPDD+tools+from+a+terminal .
What does the diagnostics procedure collect?
The diagnostic procedure tries to gather as much information as possible on a failing system. The "Analysing" process gathers system information, HID Report descriptor details, and various driver logs. The data capture process will then attempt to read and store raw data that will indicate if any data is coming from the controller.
What do I need to do during the data capture?
You will need a keyboard or mouse to proceed through the various steps. You can cancel out of the application procedure at any time using standard cancel keystrokes relative to the OS, such as Esc on Windows.
For standard (fixed) data capture: you are requested to draw a single-touch pattern on all connected touch screens, then draw with two fingers on all connected touch screens (ignore this step if you have a single-touch monitor).
Where are the log files saved?
Unless stated otherwise, log files will be created on the desktop. In some cases, on Linux, a user desktop may not exist so look in /opt/updd/data/updd/log
What do I do with the diagnostics file?
Upload the resultant diagnostics file on a support request at https://portal.touch-base.com/contact for analysis.