Folgende Warnungen sind aufgetreten:
Warning [2] Undefined variable $unreadreports - Line: 34 - File: global.php(961) : eval()'d code PHP 8.2.24 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/global.php(961) : eval()'d code 34 errorHandler->error_callback
/global.php 961 eval
/showthread.php 28 require_once
Warning [2] Undefined property: MyLanguage::$thread_modes - Line: 43 - File: showthread.php(1621) : eval()'d code PHP 8.2.24 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/showthread.php(1621) : eval()'d code 43 errorHandler->error_callback
/showthread.php 1621 eval




Themabewertung:
  • 0 Bewertung(en) - 0 im Durchschnitt
  • 1
  • 2
  • 3
  • 4
  • 5
Pollin 7T - Anschluss Touch-Controller
#14
Hi Jack,
danke für Deine Antwort, aber was bringt Dich auf die Idee, die Ursache bei NOOBS zu suchen, habe ich da irgend was übersehen?
  • Das Problem zeigt sich übrigens bei jeder Rasbian Installation sobald ein aktueller Kernel installiert ist.
  • Nutze ich einen älteren Kernel (4.4.34) und vermeide "apt-get upgrade" dann funktioniert das Panel.
  • In dem Installationsscript von Christian (hier) wird allerdings "apt-get upgrade" aufgerufen und damit auch der Kernel und Umgebung aktualisiert.
  • Ein Kernel downgrade via (sudo rpi-update dea25fa62132365c11087e51e416df656db28bf3) hat zwar den Kernel zurückgesetzt war aber ohne Auswirkung auf die Panel-Kunktion
  • Eine erneute Installation von Rasbian und der anschließende Start des modifizierten Installationsscripts von CarPc, also ohne den script-Befehl "sudo apt-get upgrade ..." war leider auch ohne Wirkung. Der Kernel ist zwar auf der Version 4.4.34 geblieben, das Panel wird aber ignoriert.
Über die SSH Konsole zeigt sich fogendes Bild:

Code:
pi@rpi099:~ $ uname -a

Linux rpi099 4.4.34-v7+ #930 SMP Wed Nov 23 15:20:41 GMT 2016 armv7l GNU/Linux
pi@rpi099:~ $ evtest
No device specified, trying to scan all of /dev/input/event*
Not running as root, no devices may be available.
Available devices:
/dev/input/event0:    eGalax Inc. Touch
/dev/input/event1:    eGalax Inc. Touch
/dev/input/event2:    RAPOO Rapoo 2.4G Wireless Device
/dev/input/event3:    RAPOO Rapoo 2.4G Wireless Device
/dev/input/event4:    RAPOO Rapoo 2.4G Wireless Device
Select the device event number [0-4]: 1
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0xeef product 0x1 version 0x112
Input device name: "eGalax Inc. Touch"
Supported events:
 Event type 0 (EV_SYN)
 Event type 1 (EV_KEY)
   Event code 320 (BTN_TOOL_PEN)
   Event code 330 (BTN_TOUCH)
 Event type 3 (EV_ABS)
   Event code 0 (ABS_X)
     Value    743
     Min        0
     Max     2047
   Event code 1 (ABS_Y)
     Value   1911
     Min        0
     Max     2047
 Event type 4 (EV_MSC)
   Event code 4 (MSC_SCAN)
Properties:
Testing ... (interrupt to exit)
***********************************************
 This device is grabbed by another process.
 No events are available to evtest while the
 other grab is active.
 In most cases, this is caused by an X driver,
 try VT-switching and re-run evtest again.
 Run the following command to see processes with
 an open fd on this device
"fuser -v /dev/input/event1"
***********************************************
^C
pi@rpi099:~ $ fuser -v /dev/input/event1
                     BEN.        PID ZUGR.  BEFEHL
/dev/input/event1:   pi          760 F.... kodi.bin
                     pi          905 F.... startx
                     pi          924 F.... xinit
                     pi          957 F.... lxsession
                     pi         1013 F.... dbus-launch
                     pi         1014 F.... dbus-daemon
                     pi         1021 F.... gvfsd
                     pi         1120 F.... gvfs-udisks2-vo
                     pi         1149 F.... gvfs-afc-volume
                     pi         1159 F.... gvfs-goa-volume
                     pi         1164 F.... gvfs-mtp-volume
                     pi         1168 F.... gvfs-gphoto2-vo


Da es mir (noch) nicht gelungen ist die CarPc Anwendung zu stoppen, ohne auch den Pi herunter zu fahren, kann ich nicht sagen ob die Events von dem Panel überhaupt ankommen.

Nutze ich die gleiche Hardware und tausche nur die SD-Karte, sieht das Ganze so aus:

Code:
pi@rpi004:~ $ uname -a
Linux rpi004 4.4.34-v7+ #930 SMP Wed Nov 23 15:20:41 GMT 2016 armv7l GNU/Linux
pi@rpi004:~ $ evtest
No device specified, trying to scan all of /dev/input/event*
Not running as root, no devices may be available.
Available devices:
/dev/input/event0: eGalax Inc. Touch
/dev/input/event1: eGalax Inc. Touch
/dev/input/event2: RAPOO Rapoo 2.4G Wireless Device
/dev/input/event3: RAPOO Rapoo 2.4G Wireless Device
/dev/input/event4: RAPOO Rapoo 2.4G Wireless Device
Select the device event number [0-4]: 1
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0xeef product 0x1 version 0x112
Input device name: "eGalax Inc. Touch"
Supported events:
 Event type 0 (EV_SYN)
 Event type 1 (EV_KEY)
   Event code 320 (BTN_TOOL_PEN)
   Event code 330 (BTN_TOUCH)
 Event type 3 (EV_ABS)
   Event code 0 (ABS_X)
     Value      0
     Min        0
     Max     2047
   Event code 1 (ABS_Y)
     Value      0
     Min        0
     Max     2047
 Event type 4 (EV_MSC)
   Event code 4 (MSC_SCAN)
Properties:
Testing ... (interrupt to exit)
Event: time 1498764571.037081, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1498764571.037081, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1498764571.037081, type 1 (EV_KEY), code 320 (BTN_TOOL_PEN), value 1
Event: time 1498764571.037081, type 3 (EV_ABS), code 0 (ABS_X), value 686
Event: time 1498764571.037081, type 3 (EV_ABS), code 1 (ABS_Y), value 1238
Event: time 1498764571.037081, -------------- EV_SYN ------------
Event: time 1498764571.077069, type 3 (EV_ABS), code 1 (ABS_Y), value 1241
Event: time 1498764571.077069, -------------- EV_SYN ------------
Event: time 1498764571.101082, type 3 (EV_ABS), code 0 (ABS_X), value 685
Event: time 1498764571.101082, type 3 (EV_ABS), code 1 (ABS_Y), value 1245
Event: time 1498764571.101082, -------------- EV_SYN ------------
Event: time 1498764571.117086, type 3 (EV_ABS), code 0 (ABS_X), value 684
Event: time 1498764571.117086, type 3 (EV_ABS), code 1 (ABS_Y), value 1249
Event: time 1498764571.117086, -------------- EV_SYN ------------
Event: time 1498764571.141098, type 3 (EV_ABS), code 0 (ABS_X), value 683
Event: time 1498764571.141098, type 3 (EV_ABS), code 1 (ABS_Y), value 1254
Event: time 1498764571.141098, -------------- EV_SYN ------------
Event: time 1498764571.165093, type 3 (EV_ABS), code 0 (ABS_X), value 682
Event: time 1498764571.165093, type 3 (EV_ABS), code 1 (ABS_Y), value 1256
Event: time 1498764571.165093, -------------- EV_SYN ------------
Event: time 1498764571.181100, type 3 (EV_ABS), code 1 (ABS_Y), value 1258
Event: time 1498764571.181100, -------------- EV_SYN ------------
Event: time 1498764571.205107, type 3 (EV_ABS), code 1 (ABS_Y), value 1259
Event: time 1498764571.205107, -------------- EV_SYN ------------
Event: time 1498764571.213109, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1498764571.213109, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1498764571.213109, -------------- EV_SYN ------------
Event: time 1498764640.325926, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1498764640.325926, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1498764640.325926, type 3 (EV_ABS), code 0 (ABS_X), value 110
Event: time 1498764640.325926, type 3 (EV_ABS), code 1 (ABS_Y), value 198
Event: time 1498764640.325926, -------------- EV_SYN ------------
Event: time 1498764640.389952, type 3 (EV_ABS), code 0 (ABS_X), value 109
Event: time 1498764640.389952, -------------- EV_SYN ------------
Event: time 1498764640.413927, type 3 (EV_ABS), code 0 (ABS_X), value 108
Event: time 1498764640.413927, -------------- EV_SYN ------------
Event: time 1498764640.429922, type 3 (EV_ABS), code 0 (ABS_X), value 107
Event: time 1498764640.429922, type 3 (EV_ABS), code 1 (ABS_Y), value 200
Event: time 1498764640.429922, -------------- EV_SYN ------------
Event: time 1498764640.453922, type 3 (EV_ABS), code 0 (ABS_X), value 105
Event: time 1498764640.453922, type 3 (EV_ABS), code 1 (ABS_Y), value 201
Event: time 1498764640.453922, -------------- EV_SYN ------------
Event: time 1498764640.477929, type 3 (EV_ABS), code 0 (ABS_X), value 104
Event: time 1498764640.477929, type 3 (EV_ABS), code 1 (ABS_Y), value 203
Event: time 1498764640.477929, -------------- EV_SYN ------------
Event: time 1498764640.501934, type 3 (EV_ABS), code 0 (ABS_X), value 103
Event: time 1498764640.501934, type 3 (EV_ABS), code 1 (ABS_Y), value 204
Event: time 1498764640.501934, -------------- EV_SYN ------------
Event: time 1498764640.525933, type 3 (EV_ABS), code 0 (ABS_X), value 102
Event: time 1498764640.525933, -------------- EV_SYN ------------
Event: time 1498764640.549933, type 3 (EV_ABS), code 0 (ABS_X), value 100
Event: time 1498764640.549933, -------------- EV_SYN ------------
Event: time 1498764640.565938, type 3 (EV_ABS), code 0 (ABS_X), value 99
Event: time 1498764640.565938, type 3 (EV_ABS), code 1 (ABS_Y), value 202
Event: time 1498764640.565938, -------------- EV_SYN ------------
Event: time 1498764640.589943, type 3 (EV_ABS), code 0 (ABS_X), value 98
Event: time 1498764640.589943, type 3 (EV_ABS), code 1 (ABS_Y), value 200
Event: time 1498764640.589943, -------------- EV_SYN ------------
Event: time 1498764640.613945, type 3 (EV_ABS), code 1 (ABS_Y), value 198
Event: time 1498764640.613945, -------------- EV_SYN ------------
Event: time 1498764640.637946, type 3 (EV_ABS), code 1 (ABS_Y), value 197
Event: time 1498764640.637946, -------------- EV_SYN ------------
Event: time 1498764640.661949, type 3 (EV_ABS), code 1 (ABS_Y), value 196
Event: time 1498764640.661949, -------------- EV_SYN ------------
Event: time 1498764640.685943, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1498764640.685943, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1498764640.685943, -------------- EV_SYN ------------
Event: time 1498764647.294818, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1498764647.294818, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1498764647.294818, type 3 (EV_ABS), code 0 (ABS_X), value 190
Event: time 1498764647.294818, type 3 (EV_ABS), code 1 (ABS_Y), value 1156
Event: time 1498764647.294818, -------------- EV_SYN ------------
Event: time 1498764647.342831, type 3 (EV_ABS), code 0 (ABS_X), value 189
Event: time 1498764647.342831, -------------- EV_SYN ------------
Event: time 1498764647.358831, type 3 (EV_ABS), code 0 (ABS_X), value 190
Event: time 1498764647.358831, -------------- EV_SYN ------------
Event: time 1498764647.366830, type 3 (EV_ABS), code 0 (ABS_X), value 199
Event: time 1498764647.366830, -------------- EV_SYN ------------
Event: time 1498764647.374828, type 3 (EV_ABS), code 0 (ABS_X), value 209
Event: time 1498764647.374828, type 3 (EV_ABS), code 1 (ABS_Y), value 1157

Deshalb glaube ich derzeit nicht an eine Hardware-Ursache oder an eine fehlerhafte Installation.

Kann mir irgend jemand ein funktionierendes Image für eine 8 oder 16GByte SD Karte für einen Pi3 mit Pollin 7" zur Verfügung stellen. Derzeit habe ich weder GPS noch FM Hardware im Einsatz, da ich soweit ja noch ger nicht gekommen bin. Ein Test des Touchpanels mit einen funktionierenden Image sollte aber auch ohne diese Hardware möglich sein.

Gunter
Read the manual first!
Zitieren


Nachrichten in diesem Thema
RE: Pollin 7T - Anschluss Touch-Controller - von gupi - 30.06.2017, 09:17

Gehe zu:


Benutzer, die gerade dieses Thema anschauen: 9 Gast/Gäste
RasPiCarProjekt