This article provides a standardized, phased procedure for diagnosing, troubleshooting, and resolving EETI projected capacitive (PCAP) touch controller issues on applicable Elo touchscreens and integrated devices.
Symptoms of touch performance anomalies may include:
- Unresponsive touch areas or dead zones
- Inaccurate touch tracking or calibration drift
- Intermittent touch operation
- Unintended, self-triggering ("ghost" or "phantom") touches
⚠️ Critical Pre-Check — Do Not Update Firmware Immediately:
When first investigating a touch issue, do not immediately update the controller firmware or run sensor tests. First, reproduce the issue and capture the current controller state, firmware version, and active error codes. This diagnostic baseline is essential for root-cause analysis if escalating the issue to Technical Support.
Prerequisites & Utility Package
These procedures apply to applicable EETI-based touch controllers and require a Windows host system connected directly to the touch controller. Before starting, verify the following setup requirements:
- Environment Requirements: Ensure the touch display is powered on and connected via the specified interface (USB, UART, or I2C).
- Device Manager Verification: Verify that Windows recognizes the controller in Device Manager under Human Interface Devices (HID).
Depending on your troubleshooting status, Elo Technical Support may provide an approved diagnostic utility package and officially validated firmware. The utility package typically contains:
| Utility / File | Purpose |
|---|---|
eGalaxUpdate2.exe | Controller information viewer and firmware flashing utility. Used to view controller model, version, and checksum. |
eGalaxTuner_80HXXX.exe | Real-time controller operating status and diagnostic error code viewer. |
eGalaxSensorTester4.exe | Comprehensive hardware sensor integrity and trace testing tool. Checks for open/short circuits. |
| Approved Firmware File | Controller firmware update image (e.g., [Firmware_Image].H84), applied only when specifically authorized. |
📌 Note: Utility names and available functions may vary by controller package. Use only utilities and firmware directly supplied or approved by Elo/Zebra for your specific product model.
Step-by-Step Troubleshooting Workflow
Step 1: Document the Touch Issue
- Reproduce the issue: Replicate the touch anomaly before changing any controller settings, hardware connections, or firmware.
- Record symptoms: Note the exact physical location of unresponsive areas or ghost touches, and document if the behavior is constant or intermittent.
- Document environmental conditions: Record installation details, power supply characteristics, nearby electromagnetic noise sources, and the grounding configuration.
Step 2: Record Current Firmware Information
- Close any active touch-intensive third-party applications.
- Launch
eGalaxUpdate2.exe. - In the Current Controller section (left side of the window), record the following values:
- Model: Note the controller model identifier (e.g.,
[Controller_Model]). - Version: Confirm the current firmware version (e.g.,
[FW_Version]). - CRC: Record the controller checksum (e.g.,
[Checksum]).
- Model: Note the controller model identifier (e.g.,
- Verify that the bottom status bar displays: "Touch controller connected."
- Capture and save a clear screenshot of the entire window for your service records.
Step 3: Check Controller Status & Error Codes
- Launch
eGalaxTuner_80HXXX.exe. - In the bottom-left INFO SETTING panel, check the Touch checkbox to activate live tracking and monitoring.
- Observe the Error Code field (top left) and status messages:
- Normal Operation: No active warning codes; normal tracking behavior is reported.
- Abnormal State: Active errors will appear in Red text, indicating a hexadecimal code and diagnostic message (e.g.,
Err: [Hex_Code], ERR_UTABLE_CRC_FAIL).
- If any abnormal status or error code is displayed, capture a full screenshot of the application window immediately.
📌 Note: Save the displayed error code and description exactly as shown. Do not attempt to clear errors or reset the controller before documenting this baseline.
Step 4: Update Firmware (Only When Instructed)
Only proceed with a touch controller firmware update if explicitly instructed by Elo Technical Support, or when applying an officially validated update packaged specifically for your exact device model.
🛑 WARNING — Avoid Controller Damage:
Applying a firmware image intended for another device or model can permanently damage or disable the touch controller.
DO NOT touch the screen, lean on the glass, place any objects on the surface, or disconnect cables/power while the update is in progress. Doing so may interrupt the flash cycle and corrupt the calibration baseline.
- Launch
eGalaxUpdate2.exe. - Click the Load Image button.
- Browse to and select the approved generic firmware file (format:
.H84, e.g.,[Firmware_File].H84). - Inspect the Load Image panel on the right side of the window to verify that the target Type, Model, Version, and CRC match your hardware requirement. The status bar will read "Load Image OK".
- Click Go! to initiate the update process. The tool will automatically erase the controller memory and download the new firmware image.
- Wait for the utility process to conclude without any interruption. Once completed, the progress bar will turn green and display: "Firmware update Success."
Step 5: Run the Sensor Diagnostic Test
Run the hardware sensor test when requested by Elo Technical Support, after performing an authorized firmware update, or once firmware health is confirmed and sensor evaluation is required.
🛑 SAFETY WARNING — Keep Screen Completely Clear:
During the sensor diagnostic test, keep all hands, tools, cables, and conductive objects entirely clear of the display surface. The tool performs highly precise capacitance baseline measurements that will fail if touched or if an object is within close proximity.
- Launch
eGalaxSensorTester4.exe. - Verify that the utility recognizes the controller information (Model Name, Type Name) and that the status panel displays "LINK".
- Ensure the screen surface is clean and clear of any touch interaction.
- Click the Start Test !! button.
- The status banner will turn yellow and display "Testing... Don't Touch". Do not touch or hover near the screen during this time.
- The utility will automatically perform the following integrity checks:
- HW Signal: Controller hardware signal verification
- Open Test: Sensor line continuity (checking for micro-cracks or broken copper traces)
- Short Test: Line-to-line isolation (checking for bridge shorts or physical damage)
- Mutual Cap Test: Matrix capacitance baseline verification
- Raw Data Test: Signal-to-noise ratio and baseline stability checks
- Evaluate the test outcome:
- PASS: The screen displays a green pass status. The hardware sensor array is fully functional. Perform touch calibration and validation as directed for your product.
- FAIL: The screen displays a red "Fail !!" box, indicating a specific failed item under Test Item. Immediately capture a screenshot of the failure details.
Step 6: Collect Diagnostic Logs for Technical Support
If touch anomalies persist, diagnostic errors remain, or the sensor test fails, assemble the following information package for escalation:
- Description of Symptoms: A brief description of the touch issue, including exact location of any ghost touches or unresponsive areas.
- Device Details: The Elo/Zebra device model, part number, and serial number.
- Baseline Screenshots:
eGalaxUpdate2.exeshowing Model, Version, and CRC checksum.eGalaxTuner_80HXXX.exeshowing any red error codes and descriptions.eGalaxSensorTester4.exedisplaying the diagnostic test results and failure details.
- Diagnostic Log Folder: Locate the log directory automatically generated within the sensor tester tool folder. This folder is named
Log_[Model_Number](for example,Log_2703). Compress (.zip) this entire folder to preserve all raw test summaries and CSV/log files. - Installation Environment: Details regarding cable types, power distribution, mounting hardware, and earth grounding configurations.
Submit this compiled diagnostic package directly to Elo Technical Support through your active support case, or contact Support for engineering team evaluation and RMA assessment.
Please report any broken links by emailing elo.support@zebra.com and include a link to the knowledge article