[Flightgear-devel] CH pedals
I got it working now, I made a mistake in patching the module joydev.o Now I have to adjust the xml files to get the 14 axes working. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] CH pedals
Hi, i've recently discovered this url: http://sourceforge.net/mailarchive/message.php?msg_id=1389791 in which is explaned what the problem is with the CH product pro pedals. Now I've compiled the pedals in joydev.c and hid-core.c and can see the hid-core.c: hid_init_reports usb_set_idle()=-911 in dmesg, but still the joystick isn't recognised with js_demo. I've copied the entire dmesg output, since I can't really tell what is relevant and what isn't. First lsmod, I need to load every module you see here. it doesn't work if i don't [EMAIL PROTECTED] operat]# lsmod Module Size Used by ehci-hcd 25732 0 (unused) joydev 6060 0 hid22404 0 (unused) input 5312 0 (autoclean) [joydev hid] nvidia 3859036 6 rtnet 53768 0 rtai_rtdm 12900 0 [rtnet] rtai_shm7368 0 rtai_fifos 17672 0 rtai_sched_up 48241 0 [rtnet rtai_rtdm] rtai 39616 2 [rtnet rtai_rtdm rtai_shm rtai_fifos rtai_sched_up] 3c59x 29552 1 usb-uhci 26668 0 (unused) usbcore83616 1 [ehci-hcd hid usb-uhci] you can see it still doesn't work.what am i doing wrong? I'm already trying everything for 2 weeks greetings Luuk van Hal [EMAIL PROTECTED] operat]# js_demo Joystick test program. ~~ Joystick 0: CH PRODUCTS CH THROTTLE QUADRANT Joystick 1: CH PRODUCTS CH FLIGHT SIM YOKE USB Joystick 2 not detected Joystick 3 not detected Joystick 4 not detected Joystick 5 not detected Joystick 6 not detected Joystick 7 not detected +JS.0--+JS.1--+ | Btns Ax:0 Ax:1 Ax:2 Ax:3 Ax:4 Ax:5 | Btns Ax:0 Ax:1 Ax:2 Ax:3 Ax:4 Ax:5 Ax:6 | +--+--+ | -1.0 -1.0 -1.0 -1.0 -1.0 -1.0 .. | -0.1 -0.2 +1.0 +1.0 +1.0 +0.0 +0.0 . | [EMAIL PROTECTED] operat]# dmesg A PERIODIC TIMER * *** LINUX TICK AT 100 (HZ) *** *** CALIBRATED CPU FREQUENCY 3192095000 (HZ) *** *** CALIBRATED TIMER-INTERRUPT-TO-SCHEDULER LATENCY 2688 (ns) *** *** CALIBRATED ONE SHOT SETUP TIME 2010 (ns) *** RTDM Version 0.5.0 *** RTnet 0.7.0 - built on Jul 28 2004 15:05:34 *** RTnet: initialising real-time networking RTnet: stack-mgr started RTDM: registered protocol device 2:2 RTDM: registered protocol device 17:2 8139too-rt Fast Ethernet driver 0.9.24-rt0.2 PCI: Found IRQ 11 for device 01:00.0 PCI: Sharing IRQ 11 with 00:1d.0 PCI: Sharing IRQ 11 with 00:1d.3 NVRM: loading NVIDIA Linux x86 NVIDIA Kernel Module 1.0-7174 Tue Mar 22 06:44:39 PST 2005 meminit hack PCI: Found IRQ 5 for device 02:03.0 PCI: Sharing IRQ 5 with 00:1d.1 spurious 8259A interrupt: IRQ7. usb.c: registered new driver hiddev usb.c: registered new driver hid hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik [EMAIL PROTECTED] hid-core.c: USB HID support drivers PCI: Found IRQ 9 for device 00:1d.7 PCI: Setting latency timer of device 00:1d.7 to 64 ehci_hcd 00:1d.7: Intel Corp. 82801EB USB2 ehci_hcd 00:1d.7: irq 9, pci mem e1e15000 usb.c: new USB bus registered, assigned bus number 5 ehci_hcd 00:1d.7: ehci_start hcs_params 0x104208 dbg=1 cc=4 pcc=2 ordered !ppc ports=8 ehci_hcd 00:1d.7: ehci_start hcc_params 6871 thresh 7 uframes 1024 64 bit addr ehci_hcd 00:1d.7: capability 10001 at 68 ehci_hcd 00:1d.7: BIOS handoff succeeded ehci_hcd 00:1d.7: reset command 080012 (park)=0 ithresh=8 Periodic period=1024 Reset HALT ehci_hcd 00:1d.7: enabled 64bit PCI DMA PCI: cache line size of 128 is not supported by device 00:1d.7 ehci_hcd 00:1d.7: init command 010001 (park)=0 ithresh=1 period=1024 RUN ehci_hcd 00:1d.7: USB 2.0 enabled, EHCI 1.00, driver 2003-Jun-19/2.4 hcd.c: 00:1d.7 root hub device address 1 hub.c: port 1, portstatus 100, change 1, 12 Mb/s hub.c: port 1 connection change hub.c: port 1, portstatus 100, change 1, 12 Mb/s hub.c: port 2, portstatus 100, change 0, 12 Mb/s usb.c: kmalloc IF cfd9af00, numif 1 usb.c: new device strings: Mfr=3, Product=2, SerialNumber=1 usb.c: USB device number 1 default language ID 0x0 Manufacturer: Linux 2.4.24-rthal5 ehci_hcd Product: Intel Corp. 82801EB USB2 SerialNumber: 00:1d.7 hub.c: USB hub found hub.c: 8 ports detected hub.c: standalone hub hub.c: ganged power switching hub.c: individual port over-current protection hub.c: Single TT hub.c: TT requires at most 8 FS bit times hub.c: Port indicators are not supported hub.c: power on to power good time: 0ms hub.c: hub controller current requirement: 0mA hub.c: port removable status: hub.c: local power source is good hub.c: no over-current condition exists hub.c: enabling power on all ports usb.c: hub driver claimed interface cfd9af00 usb.c: kusbd: /sbin/hotplug add 1 ehci_hcd 00:1d.7: GetStatus port 1 status 001803 POWER sig=j CSC CONNECT
[Flightgear-devel] 3 USB Joysticks CH
I'm still using Red Hat 8.0 on kernel 2.4.24 with 3 joysticks from CH products on a Sweex usb 2.0 hub. /usr/src/make xconfig support for usb (usbcore.o) -- Y Preliminary USB device filesystem -- Y EHCI HCD -- Y UHCI alternate driver (JE) -- Y USB full HID support -- Y HID Input layer support -- Y Input core support -- Y Joystick support -- Y lsmod: Module Size Used by rtnet 53768 0 rtai_rtdm 12900 0 [rtnet] rtai_shm 7368 0 (unused) rtai_fifos 17672 0 (unused) rtai_sched_up 48241 0 [rtnet rtai_rtdm] rtai 39616 2 [rtnet rtai_rtdm rtai_shm rtai_fifos rtai_sched_up] 3c59x 29552 1 mousedev 5492 1 dmesg | grep usb: usb.c: registered new driver usbdevfs usb.c: registered new driver hub usb.c: new USB bus registered, assigned bus number 1 usb.c: new USB bus registered, assigned bus number 2 usb.c: new USB bus registered, assigned bus number 3 usb.c: new USB bus registered, assigned bus number 4 usb.c: new USB bus registered, assigned bus number 5 usb.c: registered new driver hid input: USB HID v1.00 Joystick [CH PRODUCTS CH PRO PEDALS USB ] on usb1:3.0 input: USB HID v1.00 Joystick [CH PRODUCTS CH THROTTLE QUADRANT] on usb1:4.0 input: USB HID v1.00 Joystick [CH PRODUCTS CH FLIGHT SIM YOKE USB ] on usb1:5.0 So far so good, I would say ...BUT ...this is the output of js_demo: Joystick test program. ~~ Joystick 0 not detected Joystick 1 not detected Joystick 2 not detected Joystick 3 not detected Joystick 4 not detected Joystick 5 not detected Joystick 6 not detected Joystick 7 not detected I've tried every possible combination of modules concerning usb and joysticks but I can't get any of the USB joysticks to work. Can someone tell me why these joysticks don't work while they are installed correctly. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] RE: Unknown IO option
I'm still working on the unknow IO option but now I have some doubts about my way of compiling because it seems that none of my changes help. Every time I adjust my code, I save the file and I do: ./configure , make , make install .does it work this way? Regards Luuk ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] SG_LOG output?
Where can I find the output of SG_LOG? Because I don't get any output on the command line. Or can I use printf / cout? (these commands don't seem to work either) Regards Luuk ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] RE: Unknown IO option
First of all thanks for the quick answers. I've added all the changes I made
to the files concerning rh_flight, to the bottom of this mail. I've checked
all the things you mentioned, but I couldn't find any problems.
Is: ./configure, make, make install the same as what you call compiling?
Because I'm not using any building programs although I have Code Warrior
installed for programming other codes I'm working on.
Where can I find the output of sg_log, printf and cout?
Regards.
Luuk
Options.cxx:
{rh_flight, true, OPTION_CHANNEL, , false, , 0 }, //line
1308
FlightGear.dsp:
SOURCE=.\src\Network\rh_flight.cxx
//line 10035
!IF $(CFG) == FlightGear - Win32 Release
# PROP Intermediate_Dir Release\Lib_Network
!ELSEIF $(CFG) == FlightGear - Win32 Debug
# PROP Intermediate_Dir Debug\Lib_Network
!ENDIF
# End Source File
# Begin Source File
SOURCE=.\src\Network\rh_flight.hxx
//line 10050
!IF $(CFG) == FlightGear - Win32 Release
# PROP Intermediate_Dir Release\Lib_Network
!ELSEIF $(CFG) == FlightGear - Win32 Debug
# PROP Intermediate_Dir Debug\Lib_Network
!ENDIF
# End Source File
# Begin Source File
fgfs.1.in:
.TP
.BI --rh_flight= medium , direction , hz , options , ...
//line 385
Open an IO connection using the Rexroth-Hydraudyne Motion protocol.
fg_io.cxx:
#include Network/rh_flight.hxx
//line 62
else if ( protocol == rh_flight )
//line 182
{
RH_Flight *rh_flight = new RH_Flight;
io = rh_flight;
}
Makefile.in
am__libNetwork_a_SOURCES_DIST = rh_flight.cxx rh_flight.hxx // line 53
am_libNetwork_a_OBJECTS = rh_flight.$(OBJEXT) // line 67
DEP_FILES = ./$(DEPDIR)/rh_flight.Po// line 79 91
libNetwork_a_SOURCES = rh_flight.cxx rh_flight.hxx // line 229
252
include ./$(DEPDIR)/rh_flight.Po// line 325
Makefile.am
libNetwork_a_SOURCES = rh_flight.cxx rh_flight.hxx // line 41
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Unknown IO option
I'm trying to add an IO option to FlightGear v.0.9.8 for communication through ethernet-udp with another program, like --native=params. It's called rh_flight with --rh_flight=socket,out,60,127.0.0.1,udp as parameters but when I start FG with fgfs --rh_flight=socket, it says Unknown option --rh_flight= I've added rh_flight.cxx and rh_flight.hxx and I modified; fg_io.cxx options.cxx Makefile.am (/src/Network), Makefile.in (/src/Network) fgfs.1.in strings-default.xml and options.xml from the base package. The changes i made are simular to the code written for native. We're running RedHat 8.0 on a P4. We've installed the following libraries from flightgear.org: base package v0.9.8 FreeGlut OpenAL plib-1.8.4 metakit2.4.9.3 SimGear-0.3.8 / zlib1.1.4 When I type fgfs --help --verbose I can see the option in the IO-option list but it doesn't work. Can someone tell me what I forgot to change/include in order to get this working? Regards L v Hal ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
