So its either in the Linux input driver or the joystick itself. A lot
of USB HIDs abuse the standard, so it is likely a case of that (yes,
even tho Microsoft was a major author of USB HID). I am curious which
button it shows up as? It might be a "feature", a kind of limit
button.
.hc
On Jan 28, 2006, at 4:29 PM, David Merrill wrote:
Hello Hans, et al -
I've got another puzzling joystick bug that's showing up today as i
play around with the [hid] object in linux (Ubuntu Hoary, kernel
2.6.10-5-686).I am using a Microsoft "Sidewinder Dual Strike" USB joystick, and
after changing the permissions on /dev/input/event* I can successfully peek at the output with evtest, and I can open the
device for reading with the [hid] object.The strange behavior is that when I push the continuous
input-degree-of-freedom near one edge or another, a *button-press*
registers, but I have not pressed any button (I see this buttonpress
in both evtest, and hans' [hid] external). The continuous DOF of this
joystick has a springy region near the edges where there is some
resistance - and I get the spurious buttonpress when I cross into this
region.I tried the same joystick in windows, and I don't get the spurious
buttonpresses. (I tested it with both the windows control panel "game
controllers" interface, and jsarlo's joystick external).Has anyone see this kind of behavior? Any ideas why it doesn't show up
in Windows, but does in Linux? I'd be really interested to find out
how to fix something like this..thanks, -David Merrill
Hans-Christoph Steiner wrote:
On Apr 8, 2005, at 12:11 PM, august wrote:
hmm. I have the 'evdev' module loaded, but there is nothing at /dev/input/event*
You need:
mknod /dev/input/event0 c 13 64 mknod /dev/input/event1 c 13 65 mknod /dev/input/event2 c 13 66 mknod /dev/input/event3 c 13 67 mknod /dev/input/event4 c 13 68 mknod /dev/input/event5 c 13 69 ...
thanks....I had the devices listed alright....but the permissions
weren't set. maybe someone else is having the same problem.doing "chmod +r /dev/input/event*" should do the trick.
now, HID works as expected.....but I only get a resolution from
0-255 on the joystick axis. Is that how it is supposed to be? I thought the resolution was much higher.best -august.
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list"Supposed to" might be the key word there. That value, AFAIK,
depends on the hardware. I have two joysticks: a Logitech Wingman,
which outputs 0-127, and a Saitek Force 3D, which outputs 0-4091.
This is also why I wrote the [autoscale] object which is used in the
[joystick], [tablet], and [mouse] objects. These objects always
output between 0 and 1, converting the output range of the device,
to resolution between 0 and 1. Then when you write a patch for one
joystick, it'll stick work with other joysticks..hc
"The arc of history bends towards justice." Dr.Martin Luther King, Jr.
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
There is no way to peace, peace is the way.
-A.J. Muste