Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Hardware: simple utility for send hex commands to usb device
10-20-2008, 01:10 PM
Post: #31
 
Your problem could be that your kernel is not configured to give you force feedback support

can you run run those commands and tell us what the result is ?

lsmod |grep usbhid (this one will tell us if USB Human Interface is loaded )

lsmod |grep ff_memless ( this one will tell us if force feedback is loaded )

ls /lib/modules/`uname -r`/kernel/drivers/input
Find all posts by this user
Quote this message in a reply
10-21-2008, 03:22 PM
Post: #32
 
root@richie-desktop:/dev/system# lsmod |grep usbhid
usbhid 35968 0
hid 50688 1 usbhid
usbcore 149616 5 btusb,usbhid,ehci_hcd,uhci_hcd
root@richie-desktop:/dev/system# lsmod |grep ff_memless
root@richie-desktop:/dev/system# ls /lib/modules/`uname -r`/kernel/drivers/input
evbug.ko ff-memless.ko input-polldev.ko joystick misc serio touchscreen
evdev.ko gameport joydev.ko keyboard mouse tablet
root@richie-desktop:/dev/system#

Ahh! Il try loading ff_memless?
Find all posts by this user
Quote this message in a reply
10-21-2008, 03:53 PM
Post: #33
 
still no luck.

I found this in linux-input mailing list
Code:
Not sure this will fix your issues, but ...

ff-utils original code has 2 flaws :
- it is NOT 64-bit compatible
- it was coded for 2.4.x kernels, and when you compile it, it does not use
the includes of your specific kernel, but those shipped with the sources
(see sub-folder "linux")

So I recommend you apply the patch that fixes this issues :
look on SourceForge libff patches page ...

https://sourceforge.net/tracker/?func=detail&atid=440671&aid=2098907&group_id=44724

Then, be sure to test FF with "ffcfstress" (only for Constant Force),
not only with "fftest" ;
the first one works very well with my Logitech G25,
whereas I not sure the second one does ... (the rendered Constant Force effect is so week, that it's not that clear ...).

Finally, you can try the FFConsoleDemo of the OIS library (get 1.2.0 sources,
and apply the recent "Linux FF 64bit port + Windows FF fixes + DemoFFTest" patch
https://sourceforge.net/tracker/?func=detail&atid=775955&aid=2087429&group_id=149835) ; it tests constant and periodic FF (Constant Force test is OK for my G25, not periodic).

im working on trying the above.

Code:
Works fine for me here on 64-bit, and uses standard headers. Maybe you
are using an old version?

The latest version is in linuxconsole SVN:
http://linuxconsole.svn.sourceforge.net/viewvc/linuxconsole/trunk/utils/
Downloadable with SVN command (on one line):
svn co
https://linuxconsole.svn.sourceforge.net/svnroot/linuxconsole/trunk/utils
input-utils
I tried that and I got the results below.
That is a newer version of the force feedback tools.

Code:
richie@richie-desktop:/root/utils$ sudo ./ffcfstress -d /dev/input/event3
ERROR: device (or driver) has no force feedback support [ffcfstress.c:165]

Code:
sudo modprobe ff_memless
root@richie-desktop:~/utils# lsmod |grep ff_memless
ff_memless             13320  0
root@richie-desktop:~/utils#


Code:
root@richie-desktop:~/utils# ./evtest /dev/input/event3
Input driver version is 1.0.0
Input device ID: bus 0x3 vendor 0x46d product 0xc299 version 0x111
Input device name: "G25 Racing Wheel"
Supported events:
  Event type 0 (Sync)
  Event type 1 (Key)
    Event code 288 (Trigger)
    Event code 289 (ThumbBtn)
    Event code 290 (ThumbBtn2)
    Event code 291 (TopBtn)
    Event code 292 (TopBtn2)
    Event code 293 (PinkieBtn)
    Event code 294 (BaseBtn)
    Event code 295 (BaseBtn2)
    Event code 296 (BaseBtn3)
    Event code 297 (BaseBtn4)
    Event code 298 (BaseBtn5)
    Event code 299 (BaseBtn6)
    Event code 300 (?)
    Event code 301 (?)
    Event code 302 (?)
    Event code 303 (BtnDead)
    Event code 304 (BtnA)
    Event code 305 (BtnB)
    Event code 306 (BtnC)
  Event type 3 (Absolute)
    Event code 0 (X)
      Value   8181
      Min        0
      Max    16383
      Fuzz      63
      Flat    1023
    Event code 1 (Y)
      Value    255
      Min        0
      Max      255
      Flat      15
    Event code 2 (Z)
      Value      0
      Min        0
      Max      255
      Flat      15
    Event code 5 (Rz)
      Value    255
      Min        0
      Max      255
      Flat      15
    Event code 16 (Hat0X)
      Value      0
      Min       -1
      Max        1
    Event code 17 (Hat0Y)
      Value      0
      Min       -1
      Max        1
  Event type 4 (Misc)
    Event code 4 (ScanCode)
Testing ... (interrupt to exit)
Event: time 1224618348.182780, type 3 (Absolute), code 0 (X), value 8171
Event: time 1224618348.182784, -------------- Report Sync ------------
Event: time 1224618348.190782, type 3 (Absolute), code 0 (X), value 8162
Event: time 1224618348.190785, -------------- Report Sync ------------
Event: time 1224618348.198784, type 3 (Absolute), code 0 (X), value 8154
Event: time 1224618348.198788, -------------- Report Sync ------------
Event: time 1224618348.206782, type 3 (Absolute), code 0 (X), value 8146
Event: time 1224618348.206786, -------------- Report Sync ------------
Event: time 1224618348.222788, type 3 (Absolute), code 0 (X), value 8137
Event: time 1224618348.222793, -------------- Report Sync ------------
Event: time 1224618348.230782, type 3 (Absolute), code 0 (X), value 8128
Event: time 1224618348.230786, -------------- Report Sync ------------
Event: time 1224618348.240782, type 3 (Absolute), code 0 (X), value 8120
Event: time 1224618348.240785, -------------- Report Sync ------------
Event: time 1224618348.248783, type 3 (Absolute), code 0 (X), value 8112
Event: time 1224618348.248788, -------------- Report Sync ------------
Event: time 1224618348.264785, type 3 (Absolute), code 0 (X), value 8102
Event: time 1224618348.264789, -------------- Report Sync ------------
Event: time 1224618348.270782, type 3 (Absolute), code 0 (X), value 8093
Event: time 1224618348.270786, -------------- Report Sync ------------
Event: time 1224618348.278784, type 3 (Absolute), code 0 (X), value 8085
Event: time 1224618348.278788, -------------- Report Sync ------------
Event: time 1224618348.290784, type 3 (Absolute), code 0 (X), value 8075
Event: time 1224618348.290788, -------------- Report Sync ------------
Event: time 1224618348.298780, type 3 (Absolute), code 0 (X), value 8066
Event: time 1224618348.298784, -------------- Report Sync ------------
Event: time 1224618348.304782, type 3 (Absolute), code 0 (X), value 8058
Event: time 1224618348.304786, -------------- Report Sync ------------
Event: time 1224618348.322786, type 3 (Absolute), code 0 (X), value 8048
Event: time 1224618348.322791, -------------- Report Sync ------------
Find all posts by this user
Quote this message in a reply
10-22-2008, 02:10 AM
Post: #34
 
ff_memless should be automatically loaded and usbhid should be using it.

Can you give the result of : grep HID /usr/src/linux/.config

CONFIG_HID_FF should probably be set to Y
Find all posts by this user
Quote this message in a reply
10-25-2008, 08:58 PM
Post: #35
 
richie@richie-desktop:~/linux-source-2.6.27$ grep HID .config
CONFIG_BT_HIDP=m
CONFIG_HID_SUPPORT=y
CONFIG_HID=m
# CONFIG_HID_DEBUG is not set
CONFIG_HIDRAW=y
CONFIG_USB_HID=m
CONFIG_USB_HIDINPUT_POWERBOOK=y
# CONFIG_HID_FF is not set
CONFIG_USB_HIDDEV=y
# USB HID Boot Protocol drivers
CONFIG_USB_PHIDGET=m
CONFIG_USB_PHIDGETKIT=m
CONFIG_USB_PHIDGETMOTORCONTROL=m
CONFIG_USB_PHIDGETSERVO=m
richie@richie-desktop:~/linux-source-2.6.27$

eek? I think thats bad.
Find all posts by this user
Quote this message in a reply
10-26-2008, 01:16 PM
Post: #36
 
CONFIG_HID_FF must be set to y

When configuring your kernel, go to Device Drivers, then HID Devices and then enable Force feedback support.

Hope this helps !
Find all posts by this user
Quote this message in a reply
10-27-2008, 10:43 PM
Post: #37
 
I added a G25 wheel linux tool to SVN that tof8pool e-mailed to me. If you update the vdrift trunk you'll see it in the tools folder. You can also see it here:
In order to view links, you must have to reply to this thread.
Find all posts by this user
Quote this message in a reply
10-28-2008, 09:03 AM
Post: #38
 
Thanks for this great source of information at first!
Since this is the only active place I could find for information about how to activate my G25 fully I'd really like to ask for some help here.

I've followed all the steps mentioned in this topic but I still can't get the wheel in 900 mode.
I'm getting errors I can't eplain:
Code:
exss@exss-ws01:~/Files/usbtool-0.1$ sudo python2.5 ./usbtool g25-set-range-wheel-900
autoselect first known device G25 (normal mode) at 46d:c294:0
Command alias detected: g25-set-range-wheel-900
Send command f881 84 03 000000
opening device
alt setting 0
Traceback (most recent call last):
  File "./usbtool", line 159, in <module>
    dev.write(buf)
  File "/home/exss/Files/usbtool-0.1/usb.py", line 273, in write
    res=usb.usb_bulk_write(self.iface.device.handle, self.addrout, data[:min(len(data), self.outsize)], timeout)
TypeError: usb_bulk_write() takes exactly 5 arguments (4 given)

And when I specify the USB ID I get the following output:
Code:
exss@exss-ws01:~/Files/usbtool-0.1$ sudo python2.5 ./usbtool -d 046d:c294:0 -v f810
Send command f810
opening device
alt setting 0
Traceback (most recent call last):
  File "./usbtool", line 159, in <module>
    dev.write(buf)
  File "/home/exss/Files/usbtool-0.1/usb.py", line 273, in write
    res=usb.usb_bulk_write(self.iface.device.handle, self.addrout, data[:min(len(data), self.outsize)], timeout)
TypeError: usb_bulk_write() takes exactly 5 arguments (4 given)

As you can see, both methods give me this error. I'm not sure if I've missed something but I could really use some help Smile

I'm running Debian "Lenny". I've installed all the updates up to the ones of today.
The backages swig, python2.5, python2.5-dev, python-usb, libusb-dev have been installed in an attempt to make it all work. I have not modified my kernel as it has been explained in this topic simply because I wasn't able to find the files stated there.
My hardware specs are (in case you need them):
Core2Duo 2,0@2,66
Gigabyte EP45-DS3P
2*1GB 800Mhz DDR2 Ram
nVidia GeForce 8600 GT 256MB
500 Watt Tagan PSU
Logitech G25 wheel

The wheel is connected directly to the motherboards USB port, not via an extra hub.

I've tried to rebuild the libusb-wrapper a few times already as stated in one of the earlier posts. It tells me the following:
Code:
./build.sh
/usr/include/usb.h:330: Warning(302): Identifier 'usb_device' redefined (ignored),
/usr/include/usb.h:242: Warning(302): previous definition of 'usb_device'.

Thanks in advance Smile
Find all posts by this user
Quote this message in a reply
11-02-2008, 06:09 AM
Post: #39
 
could you try to use the G25manage tool ?

In order to view links, you must have to reply to this thread.

There are only 2 little files to downloads : the source code and a makefile.

Once the source is compiled, you just have to try:
./G25manage --nativemode
and
./G25manage --range 900
Find all posts by this user
Quote this message in a reply
12-22-2008, 05:40 PM
Post: #40
 
Hello,
I have a Logitech Formula EX (not a G25), and I want to have a separate brake and accelerator (now it is combined).

I tried a lot of command, but I can't reload the usbhid module after using usbtool.

I'm under Linux Fedora 10 (umane -r is 2.6.27.7-134.fc10.x86_64).

Help me please ;-)

Code:
# cat /proc/bus/usb/devices
...
T:  Bus=06 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  3 Spd=1.5 MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=046d ProdID=c294 Rev=21.00
S:  Manufacturer=Logitech
S:  Product=Logitech Formula Force RX
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr= 80mA
I:* If#= 0 Alt= 0 #EPs= 2 Cls=03(HID  ) Sub=00 Prot=00 Driver=usbhid
E:  Ad=81(I) Atr=03(Int.) MxPS=   8 Ivl=10ms
E:  Ad=01(O) Atr=03(Int.) MxPS=   8 Ivl=10ms
...

# python usbtool -d 046d:c294:0 -v f810
Send command f810
opening device
alt setting 0

# rmmod joydev
# rmmod usbhid
ERROR: Module usbhid does not exist in /proc/modules
# modprobe usbhid
FATAL: Module usbhid not found.

# cat /proc/bus/usb/devices
...
T:  Bus=06 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  3 Spd=1.5 MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=046d ProdID=c294 Rev=21.00
S:  Manufacturer=Logitech
S:  Product=Logitech Formula Force RX
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr= 80mA
I:* If#= 0 Alt= 0 #EPs= 2 Cls=03(HID  ) Sub=00 Prot=00 Driver=(none)
E:  Ad=81(I) Atr=03(Int.) MxPS=   8 Ivl=10ms
E:  Ad=01(O) Atr=03(Int.) MxPS=   8 Ivl=10ms
...

# lsmod |grep usbhid
# lsmod |grep ff_memless
# ls /lib/modules/`uname -r`/kernel/drivers/input
gameport  input-polldev.ko  joydev.ko  joystick  lirc  misc  mouse  serio  tablet  touchscreen
Find all posts by this user
Quote this message in a reply
03-11-2009, 06:50 AM
Post: #41
 
Hey, a DFP owner here, resurrecting this thread.
First, I want to express my gratitude to all who have contributed, there has been some awesome work achieved.

To start with, I had the same problem as eXSs. USBtool was a no go.
G25manage on the other hand would run fine, except it didn't actually do anything (Because I have a DFP?).

After a bit of hacking of USBtool, and looking at how G25manage does it, I changed this line (line 273) of code in usb.py
From:
Code:
res=usb.usb_bulk_write(self.iface.device.handle, self.addrout, data[:min(len(data), self.outsize)], timeout)
to:
Code:
res=usb.usb_bulk_write(self.iface.device.handle, self.addrout, data, min(len(data), self.outsize), timeout)
This allowed the program to run, and with the aid of running
Code:
sudo rmmod joydev && sudo rmmod usbhid && sudo modprobe usbhid
USBtool told me I had successfully changed my wheel to pro mode.

Here's where I get stuck. USBtool will allow me to change the left and right suck/push values for the feedback, as per the in-built commands, so I assume the program is working now. However, attempting to change the wheel to 900 degree mode results in absolutely nothing happening, those little stops just won't get out of the way.

Does anyone who actually knows what they're doing, unlike me, have any comments about what I might be doing right or wrong?

Edit: The tweak I made to USBtool is of absolutely no use unless you are experiencing the problem outlined in eSXs's post, if you don't have this specific problem, don't bother.
Find all posts by this user
Quote this message in a reply
05-01-2009, 04:55 AM
Post: #42
shameless first post bump DFP 900 DEGREES PLZ!
How can I get FF/900 degrees with my DFP again?



I tried usbtool, G25Manage, removal and loading of modules... nothing

dmesg reports

Code:
#dmesg
Force feedback for Logitech force feedback devices by Johann Deneux <johann>
input,hidraw0: USB HID v1.00 Joystick [Logitech Logitech Driving Force] on usb-0000:00:02.0-1

usbtool also states:
Code:
#./usbtool -l
List devices:
046d:c294:0 Device G25 (normal mode) found!

Code:
# ./usbtool -v -d 046d:c294:0 -v g25-set-range-wheel-900
Command alias detected: g25-set-range-wheel-900
Send command f881 84 03 000000
opening device
alt setting 0

after setting set-range-wheel-900, the js0 device file disappears, removal of joydev, usbhid and reloading do nothing. Stuck in 400 degrees I believe; just one led on.

I also changed the line in usb.py Simey spoke of but no, luck either... AHH!

900 degrees is the most priority to me.

Please help. Thank you.
Find all posts by this user
Quote this message in a reply
05-01-2009, 07:59 PM
Post: #43
 
Have you read these?

In order to view links, you must have to reply to this thread.
In order to view links, you must have to reply to this thread.
In order to view links, you must have to reply to this thread.
Find all posts by this user
Quote this message in a reply
05-01-2009, 08:21 PM
Post: #44
 
The DFP takes slightly different commands than the G25. I was trying to find the big bunch of info I wrote about it a while ago, I thought I posted it here, but it must have been on the linux-input mailing list.

edit: No, I did post it here, in fact in [the beginning of] this very thread: In order to view links, you must have to reply to this thread.

Either way, I think that the G25 tool(s) don't really support the DFP. It needs its own tool or a different mode in the G25 tool to support its commands.
Visit this user's website Find all posts by this user
Quote this message in a reply
11-05-2009, 02:41 PM
Post: #45
 
Hi,
The link to download "usbtool" is no longer available.

Where can I get this tools ? Thank you.
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)