Joystick Saitec ST30 detected as Wasp

Bug #121343 reported by Daniel Tschernatsch
2
Affects Status Importance Assigned to Milestone
libjsw (Ubuntu)
Expired
Low
Unassigned

Bug Description

Binary package hint: jscalibrator

In jscalibrator the ST30 USB-Joystick from Saitek is detected as a "...Wasp..."

See http://www.saitek.de/prod/st30.htm

Steering with x and y and Buttons work fine. But the hat and throttle don't work as expected.

The Throttle affects two axes:
When I move throttle upwards from the middle position one axis goes up from 0 to 127
When I move throttle down from the middle position another axis goes down from 0 to -128

The Hat does not move the hat in jscalibrator frontend. depending on the position, the hat is moved to, some multiple axes are set some values...

I can add some screenshots tomorrow.

I would like to help getting this bug resolved. What further information could be useful Output of lsusb?

Revision history for this message
Emmet Hikory (persia) wrote :

In order to actually fix this, the most useful information would be the section of /proc/bus/usb/devices for your joystick, the output of evtest for the affected device (this program is confusingly duplicated in dvb-utils and lineakd and poorly documented: I recommend installing dvb-utils for Ubuntu or Xubuntu and lineakd for Kubuntu), and a screenshot showing the issue.

On the other hand, unless you are playing Search & Rescue, you probably want to use the jscal program to calibrate your joystick, as jscalibrator only affects this single game. Also, please try to confirm your strange axis behaviour with js_demo from the flightgear package (note that there is a bug that requires you to unplug and reattach the joystick after using js_demo and before playing any games). If you can replicate it separately, it might be a problem with the input system, rather than specific to jscalibrator.

Changed in libjsw:
assignee: nobody → persia
status: Unconfirmed → Needs Info
Revision history for this message
Daniel Tschernatsch (daniel311) wrote :
Download full text (27.3 KiB)

Thank you for your fast reply. Since jscalibrator is only for one game, my "Binary package hint" was wrong. But I realized that I don't need calibration, because X Y and Z are precisly calibrated with this joystick.

So I don't want jscalibrator, but it has a nice GUI.

/proc/bus/usb/devices:
T: Bus=02 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=07b5 ProdID=0316 Rev= 1.01
S: Manufacturer=Mega World
S: Product=USB Game Controllers
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=350mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=00 Driver=usbhid
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=10ms

root@desktop:~# evtest /dev/input/event7
Input driver version is 1.0.0
Input device ID: bus 0x3 vendor 0x7b5 product 0x316 version 0x110
Input device name: "Mega World USB Game Controllers"
Supported events:
  Event type 0 (Reset)
    Event code 0 (Reset)
    Event code 1 (Key)
    Event code 3 (Absolute)
  Event type 1 (Key)
    Event code 288 (Trigger)
    Event code 289 (ThumbBtn)
    Event code 290 (ThumbBtn2)
    Event code 291 (TopBtn)
  Event type 3 (Absolute)
    Event code 0 (X)
      Value 0
      Min -128
      Max 127
      Flat 15
    Event code 1 (Y)
      Value 0
      Min -128
      Max 127
      Flat 15
    Event code 2 (Z)
      Value 127
      Min -128
      Max 127
      Flat 15
    Event code 16 (Hat0X)
      Value 0
      Min -1
      Max 1
    Event code 17 (Hat0Y)
      Value 0
      Min -1
      Max 1
    Event code 40 (?)
      Value 127
      Min -128
      Max 127
      Flat 15
Testing ... (interrupt to exit)

Hat seems to work as expected (up -> down -> left -> right):
Event: time 1182542380.757994, type 3 (Absolute), code 17 (Hat0Y), value -1
Event: time 1182542380.757998, type 0 (Reset), code 0 (Reset), value 0
Event: time 1182542380.925940, type 3 (Absolute), code 17 (Hat0Y), value 0
Event: time 1182542380.925944, type 0 (Reset), code 0 (Reset), value 0
Event: time 1182542381.525737, type 3 (Absolute), code 17 (Hat0Y), value 1
Event: time 1182542381.525742, type 0 (Reset), code 0 (Reset), value 0
Event: time 1182542381.685687, type 3 (Absolute), code 17 (Hat0Y), value 0
Event: time 1182542381.685691, type 0 (Reset), code 0 (Reset), value 0
Event: time 1182542383.061230, type 3 (Absolute), code 16 (Hat0X), value -1
Event: time 1182542383.061235, type 0 (Reset), code 0 (Reset), value 0
Event: time 1182542383.221176, type 3 (Absolute), code 16 (Hat0X), value 0
Event: time 1182542383.221180, type 0 (Reset), code 0 (Reset), value 0
Event: time 1182542383.812980, type 3 (Absolute), code 16 (Hat0X), value 1
Event: time 1182542383.812984, type 0 (Reset), code 0 (Reset), value 0
Event: time 1182542383.964930, type 3 (Absolute), code 16 (Hat0X), value 0
Event: time 1182542383.964934, type 0 (Reset), code 0 (Reset), value 0

Buttons too (Trigger -> leftmost btn -> middle button -> right button):
Event: time 1182542433.628417, type 1 (Key), code 288 (Trigger), value 1
Event: time 1182542433.628420, type 0 (Reset), code 0 (Reset), value 0
Event: time 11825...

Emmet Hikory (persia)
Changed in libjsw:
assignee: persia → nobody
importance: Undecided → Low
status: Incomplete → Confirmed
Revision history for this message
Thomas Hotz (thotz-deactivatedaccount) wrote :

Long time no update so we are wondering if you still have this bug? Can you give us an answer please if it is working or not in a supported Ubuntu version? Thank you!

Changed in libjsw (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for libjsw (Ubuntu) because there has been no activity for 60 days.]

Changed in libjsw (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.