[slyfox]

Hello!



I am new to X-Plane and really enjoying it so I decided to buy the CH Products Yoke and Pedals. I also bought the X-Plane 8.40 DVD. On my Linux setup the yoke and pedals does not work. I used linux jstest from joydev utilities and the it recognizes both the pedals and yoke. The problem is when I move the yoke left,, right, forward, or backward neither jstest or X-plane displays that it is moving. The joydev module is also loaded. Below is the lsusb comand result


[root@neilhome hotplug]# lsusb
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 003: ID 068e:00ff CH Products, Inc. Flight Sim Yoke
Bus 002 Device 002: ID 068e:00f2 CH Products, Inc. Flight Sim Pedals
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 003: ID 0781:5150 SanDisk Corp. SDCZ2 Cruzer Mini Flash Drive (thin)
Bus 001 Device 001: ID 0000:0000
[root@neilhome hotplug]#

here is the the jstest output

[neil@neilhome ~]$ jstest /dev/js0
Joystick (CH PRODUCTS CH PRO PEDALS USB ) has 3 axes and 0 buttons. Driver version is 2.1.0.
Testing ... (interrupt to exit)
Axes: 0:-32767 1:-32767 2: 0

[neil@neilhome ~]$ jstest /dev/js1
Joystick (CH PRODUCTS CH FLIGHT SIM YOKE USB ) has 7 axes and 12 buttons. Driver version is 2.1.0.
Testing ... (interrupt to exit)
Axes: 0: 0 1:-12162 2: 32767 3: 32767 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:off 10:off 11:off

here is my kernel version (using CentOS 4.4 , a RedHat 4.4 EL clone)
[neil@neilhome ~]$ su -c 'uname -a'
Password:
Linux neilhome 2.6.9-42.EL #1 Sat Aug 12 09:17:58 CDT 2006 i686 athlon i386 GNU/Linux
[neil@neilhome ~]$

and attached are my dmesg and lsmod ouputs

Thanks in advance for any help.


Neil aka slyfox

Attached File(s)

•  dmesg.js.txt (17.08K)
  Number of downloads: 22
•  lsmod.dump.txt (2.51K)
  Number of downloads: 18

[Ahab]

Try an updated kernel (2.6.18 or 2.6.19 are current depending on who you ask), and make sure it has both USB(HID) and Joystick support built in. Looks like you have USB support already but not sure about Joystick. Any distro's present 'default' kernel should have those things set if you aren't comfortable compiling your own.

I'm not really familiar with jstest so this could be the same thing, but try:

cat /dev/js0

and move your pedals around. Do you get anything in the terminal? If not, then your pedals aren't being recognized as input devices for whatever reason.

I hope you get them working. If so, please post about it. I was thinking of purchasing the CH Pro Pedals myself and was hoping they worked fairly effortlessly with Linux. I have their Combatstick 568 and it works great

EDIT: Nevermind, I see this exact advice was already given in another thread you started. Why ask the same question twice by the way?

This post has been edited by Ahab: 09 January 2007 - 05:25 PM

[raato]

BTW, just read from Linux-usb-users mailing list that "Seems like every CH USB device suffers from this under later linux 2.6 kernels" - and "this" means the effect you're seeing: device seems connected but just doesn't work. The cure to this according to the mailing list is unplugging and replugging the yoke and pedals.

[dinman2022]

BTW, just read from Linux-usb-users mailing list that "Seems like every CH USB device suffers from this under later linux 2.6 kernels" - and "this" means the effect you're seeing: device seems connected but just doesn't work. The cure to this according to the mailing list is unplugging and replugging the yoke and pedals.

I found this this to be mostly true under Ubuntu Gutsy with Kernel version 2.6.22-14.
This is a stock installation of Ubuntu - not something I compiled.
I run a CH 568 Combat Stick and CH Pro pedals.

However, unplugging and plugging back-in the joystick and pedals often does NOT resolve
my problem. What's more annoying is that when it does work, all the buttons and axes
are sensed through different ports requiring a re-configuration of X-Plane each time I run. Whether
X-Plane sees the joystick and pedals or not, the system DOES see them. New entries
appear in 'dmesg' as they are plugged in and they appear listed when running 'lsusb'.

I'm pretty disappointed given that these were recommended as good for X-Plane.

Dave

[ramius345]

I have found a fix for this problem. I had the same problem with my fighterstick and pro throttle but not my pro pedals. If you do jstest and a CH joystick is not responding to input, you need to do something similar to this page

http://patchwork.ker...rg/patch/54824/

This requires downloading the kernel source from

http://www.kernel.org

and applying the patch manually.

I have a Fighterstick and a Pro throttle, the patch looked like this for me (items I have added are in bold). I found the device ID's for my stick and throttle by performing a lsusb, my output looks like this (relevant parts highlighted in bold):

[ramius@pinapple usbhid]$ lsusb
Bus 002 Device 004: ID 068e:00f3 CH Products, Inc. Fighterstick
Bus 002 Device 003: ID 068e:00f2 CH Products, Inc. Flight Sim Pedals
Bus 002 Device 005: ID 068e:00f1 CH Products, Inc. Pro Throttle
Bus 002 Device 002: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 006: ID 0fca:8007 Research In Motion, Ltd.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[ramius@pinapple usbhid]$


in /usr/src/linux/drivers/hid/hid-ids.h around line 117:


#define USB_VENDOR_ID_CH 0x068e
#define USB_DEVICE_ID_CH_PRO_THROTTLE 0x00f1
#define USB_DEVICE_ID_CH_PRO_PEDALS 0x00f2
#define USB_DEVICE_ID_CH_FIGHTERSTICK 0x00f3
#define USB_DEVICE_ID_CH_COMBATSTICK 0x00f4
#define USB_DEVICE_ID_CH_FLIGHT_SIM_YOKE 0x00ff


and then in /usr/src/linux/drivers/hid/usbhid/hid-quirks.c around line 53:


{ USB_VENDOR_ID_ATEN, USB_DEVICE_ID_ATEN_UC100KM, HID_QUIRK_NOGET },
{ USB_VENDOR_ID_ATEN, USB_DEVICE_ID_ATEN_CS124U, HID_QUIRK_NOGET },
{ USB_VENDOR_ID_ATEN, USB_DEVICE_ID_ATEN_2PORTKVM, HID_QUIRK_NOGET },
{ USB_VENDOR_ID_ATEN, USB_DEVICE_ID_ATEN_4PORTKVM, HID_QUIRK_NOGET },
{ USB_VENDOR_ID_ATEN, USB_DEVICE_ID_ATEN_4PORTKVMC, HID_QUIRK_NOGET },
{ USB_VENDOR_ID_CH, USB_DEVICE_ID_CH_FIGHTERSTICK, HID_QUIRK_NOGET },
{ USB_VENDOR_ID_CH, USB_DEVICE_ID_CH_COMBATSTICK, HID_QUIRK_NOGET },
{ USB_VENDOR_ID_CH, USB_DEVICE_ID_CH_FLIGHT_SIM_YOKE, HID_QUIRK_NOGET },
{ USB_VENDOR_ID_CH, USB_DEVICE_ID_CH_PRO_THROTTLE, HID_QUIRK_NOGET },
{ USB_VENDOR_ID_CH, USB_DEVICE_ID_CH_PRO_PEDALS, HID_QUIRK_NOGET },


Once I recompiled the kernel, the device started responding in jstest.

This post has been edited by ramius345: 29 December 2009 - 03:29 PM

[The World War 1 Flying Ace]

ramius345, on 29 December 2009 - 02:27 PM, said:

I have found a fix for this problem.

Any chance of you sending this to the USB HID kernel maintainers so the fix makes it into the official kernel?

[The World War 1 Flying Ace]

The World War 1 Flying Ace, on 17 May 2010 - 10:35 AM, said:

Any chance of you sending this to the USB HID kernel maintainers so the fix makes it into the official kernel?

Actually, I can do this if you have no objections.

[The World War 1 Flying Ace]

After some judicious Googling, I discovered a way to make the joysticks work without having to patch the kernel. The secret is to pass the quirks information to the usbhid driver - either on the kernel command line (if the usbhid driver is built into the kernel) or on the modprobe command line (if the driver is a module.)

I used the latter - on Kubuntu (should work on plain Ubuntu as well) I created a file /etc/modprobe.d/usbhid.conf with the following content:

options usbhid quirks=0x068e:0x00f1:0x08,0x068e:0x00f3:0x08

If your distribution uses a plain modprobe.conf file, just add that line to the file.

On that line, the quirks= lists any quirks for devices, in the form <manufacturer ID>:<device ID>:<quirk> - in this case 0x068e is the manufacturer ID for CH Products, 0x00f1 is the device ID for the Pro Throttle, and 0x00f3 is the device ID for the FighterStick, and 0x08 is the HID_QUIRK_NOGET quirk.