We have an Elo Touchscreen monitor (Elo Touch ET1502L) connected to a Verdin iMX8MP module running Torizon OS (6.4.0). We’re running Chromium & Weston containers to render a web application. The touchscreen monitor works perfectly, however a mouse cursor is displayed on the screen.
Executing lsusb returns this (alongside other devices):
Bus 001 Device 025: ID 04e7:2903 Elo TouchSystems ET1502L
However executing cat /proc/bus/input/devices returns multiple entries for this device:
I suspect if there’s a way to disable "Elo Touch ET1502L Mouse" then the cursor will disappear, but allow the touchscreen to continue to function. Can this be achieved with a udev rule?
Connecting a mouse did not allow the cursor to be moved, I’m guessing the OS doesn’t like having 2 devices as mice. Connecting a different brand of touchscreen instead (old 3M MicroTouch) did not show a cursor, and allowed a separate mouse to be connected successfully.
Thanks for the suggestion. We’d like to be able to connect a mouse and use it without any other configuration changes, so this approach wouldn’t be ideal.
Some of our customers may keep a mouse for specific tasks, but leave it unplugged most of the time and rely only on the touchscreen. The issues here are two-fold, as the ELO touchscreen is showing a mouse cursor and also preventing other mice from working.
Thanks - I will give that a go, but I suspect it will stop the touchscreen from working also, as you can see above, the ID 0003:04E7:2903.0006 is the same for input15 & input17. Somehow I need only one of the 2 inputs to be disabled for this device.
I took a look at the ELO Touch website and it was not much help. Their drivers and such are here. Interestingly they seem to have a daemon that they install on some systems. I’m not sure what that would do exactly.
There seem to be many discussions about how to disable something like this under Xorg but nothing I have found for disabling the input device under Wayland/Weston.
It may be worth reaching out to ELO support to see if they have any suggestions.
I’m not sure if it’s entirely helpful, but have you tried a udev rule to make libinput ignore that specific mouse device?
We encountered something similar where we wanted/needed to to the opposite (have Wayland ignore the touch device) because we had a Qt application and needed touch2pointer for certain widgets to accept input properly.