Hi Roberto, thank you for your input!
I have installed v2.1.5 and there they have introduced ~operator/v2.1.5/scripts/detect_touchscreen.py
In v2.1.4 they used detect_touchscreen.sh
Now I took the output of input --list into the list of known devices in detect_touchscreen.py as follows:
Code:
operator@tormachpcnc:~$ xinput --list
? Virtual core pointer id=2 [master pointer (3)]
? ? Virtual core XTEST pointer id=4 [slave pointer (2)]
? ? Elo TouchSystems, Inc. Elo TouchSystems 2700 IntelliTouch(r) USB Touchmonitor Interface id=9 [slave pointer (2)]
? ? PixArt USB Optical Mouse id=10 [slave pointer (2)]
? Virtual core keyboard id=3 [master keyboard (2)]
? Virtual core XTEST keyboard id=5 [slave keyboard (3)]
? Power Button id=6 [slave keyboard (3)]
? Video Bus id=7 [slave keyboard (3)]
? Power Button id=8 [slave keyboard (3)]
? AT Translated Set 2 keyboard id=11 [slave keyboard (3)]
Added (in my case) 'Elo TouchSystems, Inc. Elo TouchSystems 2700 IntelliTouch(r) USB Touchmonitor Interface' to the list...
Code:
operator@tormachpcnc:~$ gedit ~operator/v2.1.5/scripts/detect_touchscreen.py
LIST_OF_KNOWN_DEVICES = ['eGalax Inc. USB TouchController',
'D-WAV Scientific Co., Ltd eGalax TouchScreen',
'eGalax Inc. USB TouchControlle?', # trailing 3 byte sequence " 0xe1 0x81 0xb2"
'EloTouchSystems,Inc Elo TouchSystems 2216 AccuTouch® USB Touchmonitor Interface',
'FUJITSU COMPONENT LIMITED USB Touch Panel',
'Elo TouchSystems, Inc. Elo TouchSystems 2700 IntelliTouch(r) USB Touchmonitor Interface'
]
Now the ADMIN TOUCHSCREEN command is working on the MDI input!
But this change will be gone with the next update... or TORMACH is so kind and adds this line for me in the next version :-))
This should make the steps in my first post obsolete but it was the step in the right direction...
all the best
Manfred