This article provides information on the EloLogAnalyzer utility

Please see the information below regarding the EloLogAnalyzer utility.

(1) Introduction
This utility is used to view/analyze Elo driver’s multi-touch logging information.
Download utility HERE  
 
Starting with Elo muli-touch 6.9.17, the logging of kernel level multi-touch information is supported on system with single Elo touch monitor only; log entries in Windows Event Log will be messed up with touches from multi-monitors.
 
The app retrieves Elo USB driver's logging entries from Windows Event Log (under Windows Logs - System) and display log entries in a table. It also mark entries in red if it considers them as suspicious (entries without unique matching touch-down or touch-up).
 
The utility does basic analyzing of log and show count of suspicious entries (highlighted in red) and touch-down that lasted more than a second. The basic analyzing is done by eliminating all valid pairs of touch-down and touch-ups and whatever left over is considered as "suspicious".
 
Clicking any entry inside the table, will get the corresponding touch event (pairing touch event) highlighted (in green).
 
(2)  Table description
 
Index: This is the index into the whole table.
 
Down/Up: Indicating if this event is a touch-down or touch-up. Touch-down events are highlighted.
 
Touch ID: It’s the touch id corresponding to the current touch event.
 
Pair Inx: Each touch-down and corresponding touch-up a is marked by a unique 2-byte number. This way the user can identify which touch-up belongs to which touch-down. In normal condition, there should be one-to-one relation between a touch-down and it’s matching touch-up.
 
Raw Point: The controller reported touch coordinates before going through kernel driver’s calibration process. For pCap touch monitors installed as digitizer, the coordinate should remain the same after going through driver’s calibration process.
 
Cal. Point: The calibrated coordinates. It is the result of driver’s calibration process. For pCap monitors in digitizer mode, it should be the same as “Raw Point”.
 
Touch Ct: Total number of simultaneously touch contacts at the time of this touch event.
 
Timestamp: This is the timestamp for the touch event to milliseconds.
 
Holding Time: Indicate touch-down time in milliseconds. 1st entry after driver has been reloaded is marked as "Driver reloaded".
 
(3) Button description
 
[Read from Current OS System Log]
 
Retrieve Elo Log entries writing with last logging format from OS’s System Log and provide basic analyzing result. If there is suspicious entries found, it will show count of such entries in red and all suspicious entries will be highlighted in red in the table.
 
[Read from Saved Event Log (.evtx)]
 
Read Elo log entries from a locally saved log with extension “.evtx”. This can be used to analyze a Windows Event Log collected from another Windows system. Steps below must be followed to save a copy of current system log (where Elo touch events logged):
 
    1.  Start Windows Event Viewer
    2.  Right-click "Windows Logs" - "System" and then choose “Save All Events As…”.
    3.  Save the file with .evtx extension for analyzing and debugging.
 
Display this user instruction.
 
(4) The "Summary" panel
 
      Event Count: total number of Elo touch logging retrieved from Windows Event Log.
      Touch-downs: total touch down event count.
      Touch-ups: total touch-up event count.
      Suspicious entries: total count of events that do not belong to any unique touch-down/touch-up pair.
      Down more than a sec: total touch-down that lasted more than a second.