What Is the EloLogAnalyzer Utility and How Do I Use It?
This article explains the purpose and operation of the EloLogAnalyzer utility. EloLogAnalyzer is a diagnostic tool that reads and analyzes touch events recorded by the Elo Multi-Touch USB driver from the Windows Event Log. It helps identify abnormal touch behavior, unmatched touch events, and other issues that may assist in troubleshooting touch performance.
EloLogAnalyzer retrieves touch event information from the Windows Event Log and displays the events in an easy-to-read table. The utility automatically analyzes the data and highlights potential issues, such as unmatched touch events or unusually long touch durations.
When Should I Use EloLogAnalyzer?
EloLogAnalyzer is intended for troubleshooting and engineering analysis of Elo touch devices. Consider using the utility when you experience any of the following issues:
- Intermittent or inconsistent touch response.
- Unexpected touch releases or missing touch events.
- Touch events that appear to remain active ("stuck touches").
- Multi-touch performance or gesture issues.
- Driver validation after installing or updating an Elo Multi-Touch driver.
- Collecting diagnostic information for Elo Technical Support or Engineering.
EloLogAnalyzer analyzes touch events generated by the Elo USB Multi-Touch driver. It is intended as a diagnostic tool and does not modify the driver, firmware, or touch controller configuration.
Download EloLogAnalyzer
📦 Download EloLogAnalyzer v1.0.6
Supported Driver Version
Kernel-level touch logging is supported beginning with Elo Multi-Touch Driver 6.9.17. For best results, use EloLogAnalyzer on systems with a single Elo touch monitor. When multiple Elo touch monitors are connected, Windows Event Log entries from different devices may become intermixed, making analysis unreliable.
How EloLogAnalyzer Works
The utility reads Elo USB driver events from the Windows System Event Log and displays each touch event in a searchable table.
During analysis, EloLogAnalyzer:
- Matches every Touch Down event with its corresponding Touch Up event.
- Highlights unmatched or incomplete touch events in red.
- Displays matching touch pairs in green when an event is selected.
- Counts touches that remain active for more than one second.
- Provides an overall summary of detected events.
Event Table Columns
| Column | Description |
|---|---|
| Index | Sequential index of the event within the table. |
| Down / Up | Indicates whether the event is a Touch Down or Touch Up event. |
| Touch ID | Unique identifier assigned to the touch event. |
| Pair Index | Unique identifier linking each Touch Down event with its matching Touch Up event. |
| Raw Point | Touch coordinates reported directly by the touch controller before calibration. |
| Calibrated Point | Coordinates after driver calibration has been applied. |
| Touch Count | Number of simultaneous touch contacts during the event. |
| Timestamp | Time the touch event occurred (milliseconds). |
| Holding Time | Duration of the touch. The first event after the driver reloads is identified as Driver Reloaded. |
Available Commands
| Button | Description |
|---|---|
| Read from Current OS System Log | Reads Elo touch events directly from the current Windows System Event Log and performs automatic analysis. |
| Read from Saved Event Log (.evtx) | Loads a previously saved Windows Event Log (.evtx) for offline analysis. |
| Help | Displays the EloLogAnalyzer user instructions. |
Saving a Windows Event Log
To analyze an Event Log collected from another computer:
- Open Windows Event Viewer.
- Expand Windows Logs.
- Select System.
- Right-click System and select Save All Events As....
- Save the file using the .evtx format.
- Open the saved file using the Read from Saved Event Log (.evtx) option in EloLogAnalyzer.
Summary Panel
The Summary panel provides a quick overview of the captured touch events.
| Field | Description |
|---|---|
| Event Count | Total number of Elo touch events retrieved. |
| Touch Downs | Total Touch Down events. |
| Touch Ups | Total Touch Up events. |
| Suspicious Entries | Events that could not be matched with a corresponding Touch Down or Touch Up event. |
| Down More Than One Second | Touch events that remained active for longer than one second. |
Example
The following image shows the EloLogAnalyzer interface, including the event table and Summary panel.
When troubleshooting intermittent touch issues, ask the customer to save the Windows System Event Log as an .evtx file and analyze it with EloLogAnalyzer. Reviewing the log can quickly identify unmatched touch events, prolonged touches, or other driver-level behavior that may not be apparent during normal operation. Including the .evtx file when opening an Elo Technical Support case can also help reduce troubleshooting time.
Please report any broken links by emailing support@elotouch.com and include a link to the knowledge article