PathPilot2 ADMIN TOUCHSCREEN not possible + solution

[dreamax]

My 15" ELO Touchscreen was not working properly with PathPilot 2. The y-axis of the touchscreen was flipped and when I touched on the top the pointer was on the bottom...

After a long search I found the solution:

I bootet to the desktop. The touchpanel showed up with these two commands:

lsusb
xinput --list

All I had to do was to install xinput_calibrator with

sudo apt-get install xinput-calibrator

After calibrating with

xinput_calibrator

everything worked fine again!

I hope this can help someone else in the future!

Manfred

PS.: ADMIN TOUCHSCREEN is still not running but I can start it manually with xinput_calibrator on the console

Similar Threads:

• Need Help!- PathPilot2+Touchscreen HP Compaq L5009tm
• PP 2.12 ADMIN TOUCHSCREEN
• Need Help!- PathPilot2.0.4 Conversational
• Will trade $1200 planar touchscreen for perfect touchscreen front end

[asterix]

I had problems with ADMIN TOUCHSCREEN not running

I found the solution that modifies the file: touchscreen_env
In the directory: operator / v2.1.4 / scripts

I modified this way

#-----------------------------------------------------------------------
# coding=utf-8
#
# Copyright © 2014-2018 Tormach® Inc. All rights reserved.
# License: GPL Version 2
#-----------------------------------------------------------------------

#
# sourced by touchscreen calibration scripts
#
TMC_DIR="$HOME/tmc"
GCODE_DIR="$HOME/gcode"

TSCAL_BINARY="$TMC_DIR/bin/xinput_calibrator"

# this file path must match in calibration script called from PathPilot UI
TSCALFILE="$GCODE_DIR/pointercal.xinput"

TSLOGFILE="$GCODE_DIR/logfiles/xinput_calibrator.pointercal.log"

echo "list of xinput devices:"
xinput --list

#TS_DEVICE=`detect_touchscreen.sh`
#if [ $? != 0 ]; then
#    echo "could not find any touchscreen device"
#    exit 1
#fi

echo "Touchscreen device = \"$TS_DEVICE\""

Now he executes ADMIN TOUCHSCREEN but I have to do it again every time I start Pathpilot

I hope you may be interested
Excuse my language but use google translator.

Roberto.

[dreamax]

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:

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...

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

[jwatte]

I wish there was a hook for local edits that the path pilot would run on start-up...
Perhaps with the option to not run it if shift is held down or something (for troubleshooting.)