Irtouchsystems Mice & Touchpads Driver



  1. Irtouchsystems Mice Vs
  2. Irtouchsystems Mice Meaning
  • Here is a step by step manual guide for IRTOUCHSYSTEMS InfraRed USB TouchScreen software installation process on Windows 7 / 8 / 8.1 / 10 / Vista / XP. 1 Download Setup.exe file for Windows 7 / 8 / 8.1 / 10 / Vista / XP, save and unpack it if needed. 2 Switch on your new mouse hardware.
  • Mice are known to be able to chew through almost anything, especially if they think food is on the other side. But there is one thing they can’t chew through Steel Wool! A good mouse prevention technique is to fill any holes in your home with steel wool. This can be anywhere from air vents to hole in your kitchen cupboards.
  • I'm announcing the release of the 3.16.61 kernel. All users of the 3.16 kernel series should upgrade. The updated 3.16.y git tree can be found at.
  • Check our new training course. And Creative Commons CC-BY-SA. Lecture and lab materials.
Irtouchsystems Mice & Touchpads Driver

I have two identical HP notebooks that went through the Windows 8.1 'update' to Windows 10 though, at a month apart. Oh, how I wish I still had 8.1.

Hi,
I'm currently trying to get a Beijing IRTOUCHSYSTEMS Optical Touchscreen to work with the usbtouchscreen kernel module (currently testing with 3.0.6).
I see that the existing module recognises a different screen from the same vendor (Vendor 6615) so I quickly patched the module in an attempt to use the same routines for this screen. The device was then detected by the module and an input device created accordingly. Unfortunately it doesn't appear to get any events from the screen
I'm looking for any advice that can help me get further, whether it's things to try, info to read or people to talk to.
This is what the device appears like in /proc/bus/input/devices:
Code:

I: Bus=0003 Vendor=6615 Product=0c20 Version=0646
N: Name='Beijing IRTOUCHSYSTEMS Co.,LtD Optical TouchScreen'
P: Phys=usb-0000:00:1d.1-1/input0
S: Sysfs=/devices/pci0000:00/0000:00:1d.1/usb6/6-1/6-1:1.0/input/input20
U: Uniq=
H: Handlers=mouse2 event9
B: PROP=0
B: EV=b
B: KEY=400 0 0 0 0 0
B: ABS=3

Irtouchsystems Mice Vs


The xorg log looks like this:
Code:

[200790.465] (II) config/udev: Adding input device Beijing IRTOUCHSYSTEMS Co.,LtD Optical TouchScreen (/dev/input/mouse2)
[200790.465] (II) No input driver/identifier specified (ignoring)
[200790.466] (II) config/udev: Adding input device Beijing IRTOUCHSYSTEMS Co.,LtD Optical TouchScreen (/dev/input/event9)
[200790.466] (**) Beijing IRTOUCHSYSTEMS Co.,LtD Optical TouchScreen: Applying InputClass 'evdev touchscreen catchall'
[200790.466] (II) Using input driver 'evdev' for 'Beijing IRTOUCHSYSTEMS Co.,LtD Optical TouchScreen'
[200790.466] (II) Loading /usr/lib64/xorg/modules/input/evdev_drv.so
[200790.466] (**) Beijing IRTOUCHSYSTEMS Co.,LtD Optical TouchScreen: always reports core events
[200790.466] (**) Beijing IRTOUCHSYSTEMS Co.,LtD Optical TouchScreen: Device: '/dev/input/event9'
[200790.466] (--) Beijing IRTOUCHSYSTEMS Co.,LtD Optical TouchScreen: Found absolute axes
[200790.466] (--) Beijing IRTOUCHSYSTEMS Co.,LtD Optical TouchScreen: Found x and y absolute axes
[200790.466] (--) Beijing IRTOUCHSYSTEMS Co.,LtD Optical TouchScreen: Found absolute touchscreen
[200790.466] (II) Beijing IRTOUCHSYSTEMS Co.,LtD Optical TouchScreen: Configuring as touchscreen
[200790.466] (**) Beijing IRTOUCHSYSTEMS Co.,LtD Optical TouchScreen: YAxisMapping: buttons 4 and 5
[200790.466] (**) Beijing IRTOUCHSYSTEMS Co.,LtD Optical TouchScreen: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[200790.466] (**) Option 'config_info' 'udev:/sys/devices/pci0000:00/0000:00:1d.1/usb6/6-1/6-1:1.0/input/input20/event9'
[200790.466] (II) XINPUT: Adding extended input device 'Beijing IRTOUCHSYSTEMS Co.,LtD Optical TouchScreen' (type: TOUCHSCREEN)
[200790.466] (II) Beijing IRTOUCHSYSTEMS Co.,LtD Optical TouchScreen: initialized for absolute axes.
[200790.466] (**) Beijing IRTOUCHSYSTEMS Co.,LtD Optical TouchScreen: (accel) keeping acceleration scheme 1
[200790.466] (**) Beijing IRTOUCHSYSTEMS Co.,LtD Optical TouchScreen: (accel) acceleration profile 0
[200790.466] (**) Beijing IRTOUCHSYSTEMS Co.,LtD Optical TouchScreen: (accel) acceleration factor: 2.000
[200790.466] (**) Beijing IRTOUCHSYSTEMS Co.,LtD Optical TouchScreen: (accel) acceleration threshold: 4

xinput --list shows:
Code:

⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Broadcom Corp id=11 [slave pointer (2)]
⎜ ↳ PS/2 Mouse id=13 [slave pointer (2)]
⎜ ↳ AlpsPS/2 ALPS GlidePoint id=14 [slave pointer (2)]
⎜ ↳ Beijing IRTOUCHSYSTEMS Co.,LtD Optical TouchScreen id=9 [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)]
↳ Sleep Button id=7 [slave keyboard (3)]
↳ Broadcom Corp id=10 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=12 [slave keyboard (3)]
↳ Laptop Integrated Webcam id=8 [slave keyboard (3)]

and the details for the device is (xinput --list 9):
Irtouchsystems
Code:

Beijing IRTOUCHSYSTEMS Co.,LtD Optical TouchScreen id=9 [slave pointer (2)]
Reporting 3 classes:
Class originated from: 9
Buttons supported: 5
Button labels: Button Unknown Button Unknown Button Unknown Button Wheel Up Button Wheel Down
Button state:
Class originated from: 9
Detail for Valuator 0:
Label: Abs X
Range: 0.000000 - 4095.000000
Resolution: 10000 units/m
Mode: absolute
Current value: 256.000000
Class originated from: 9
Detail for Valuator 1:
Label: Abs Y
Range: 0.000000 - 4095.000000
Resolution: 10000 units/m
Mode: absolute
Current value: 257.000000

Irtouchsystems Mice Meaning


Incidentally xinput --test 9 gives no output when the screen is touched, and there is no output when cat'ing the input device files
Again, any advice that can help me get further, whether it's things to try, info to read or people to talk to would be much appreciated,
Gus.
_________________
--with-${relevantQuote}




Comments are closed.