Jump to content
The simFlight Network Forums

radioguy

Members
  • Posts

    9
  • Joined

  • Last visited

About radioguy

  • Birthday 01/01/1970

Contact Methods

  • Website URL
    http://

radioguy's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Hi all, I'm going through a re-install of FSX and its associated bits. Part of this involves some upgraded PFC hardware. I formerly had a throttle quadrant that was serial connected and seemed to be causing all sorts of conflict issues with a separate install of FlightLink helo hardware that are USB. I've now changed out the PFC serial quadrant to a USB unit. Also upgraded to PFC USB pedals. In the former PFC setup, the pedals were ported through the throttle quadrant box that was connected to a serial (COM) port on the PC. Now, each device connects directly to USB...BUT..while the PC (and FSX) sees each device for what it is, FSUIPC (Ver. 4.923) does NOT see any of the devices..as such. There is a notice on the FSUIPC screen that clearly states that USB devices require the USB port to act as a COM port via software. I was under the impression that PFCFSX (4.410 in this case) is the required software. But even with that installed, FSUIPC still does not see those devices on the initial startup. Windows sees them, FSX sees them, just not FSUIPC. As well, I have PFCHID ver.1.36 installed, though I'm not sure what that does. Also, I'm getting really wonky feedback from the throttle and pedals. In the Windows calibration routine, all axes and rotations, buttons and switches, are functioning. But in FSX, a rudder input will turn the yoke on the virtual cockpit (acting as an aileron control, not rudder), the throttle on a single engine a/c is reversed (full throttle is back, not forward), and various other strangeness. Suffice to say that nothing is working correctly. So, for starters on this issue, could someone kindly set me straight on which software is required to get a USB port to emulate a COM? Also, I've got all the devices running through a hub into one USB port. Is this OK? Or should each device run through its own dedicated USB port? And if that's the case, how do I get them to play "nicely" with each other? Thanks, Alan Aronoff (CYUL)
  2. Understood Pete. Seems clear now. Just re-did the FlightLink stuff and all is working OK One more thing about the PFC rig. With the GF equipment coming, I'll be removing the throttle unit. The Cirrus pedals connect either through that or into the back of the PC. Would you suggest I change the pedals to USB? I'd need to buy a new unit as PFC informs me the current one is not convertible. Thanks to Paul and you for all the input. Alan
  3. Hmm. I don't know of any way you can get cross-interference from separate devices, and especially separate devices with separate drivers, UNLESS there's some mlutiple assignments going on, possibly ones you aren't aware of. Pretty much all cases like that have been down to such a mix up. That's why Paul suggested we clear out all assignments from the fsx.cfg file and do a "virgin" setup within FSUIPC. Again, that is nothing like you seemed to describe earlier. The device is evidently a bona fide USB joystick type device as far as Windows is concerned. Sorry for any confusion. It would seem, then, that we're not sdealing with "classic" serial inputs but rather GAME inputs. The PFC throttle/pedals are connected directly to the back of the PC through what I would imagine then is a gameport. That's okay, but FSUIPC is reading them via the Windows joystick driver, so they need setting up correctly there first. All FSUIPC would be doing is handling assignments and final calibration instead of letting FSX do that. Are you then suggesting all devices be calibrated first through Windows Control Panel before I mess with FSUIPC? Sorry, now it gets confusing again. Are you saying you CAN set up the FlightLink devices via Windows and you can assign them in FSX, but not in FSUIPC? That makes no sense as FSUIPC is using the exact same Windows functions as FSX -- UNLESS Windows is assigning them a joystick ID or more than 15. FSUIPC can only handle joystick devices 0 to 15. But, since Windows assigns these IDs sequentially according to the number connected, I cannot imagine that number being exceeded. I've never known it happen. Prior to clearing out the fsx.cfg, ALL devices were set up through the FSX internal routine. Everything worked fine. Calibration routines were normal. The only issue I encountered was that phantom spiking I reported on the Avsim forum. I certainly don't have more than 15 joystick devices so I doubt that's the issue. I've just gone back to FSX and opened up FSUIPC. Now we're on to the axes section as the buttons were successfully assigned yesterday. It seems that the collective and pedals are now visible through FSUIPC in that I'm getting values when those units are moved. Might be time for another quick call with Paul on how to actually get them to function in FS. School is fun!! I'll get back with more info on the progress. Thanks, Alan
  4. Pete, Allow me to clarify a bit. I have the PFC drivers installed and those devices were seen in FSUIPC when I used the PFC specific setup routine available through the FSX addons menu option. I also believe that the serial connections might have been causing the phantom spiking that your program detected, and was evidenced by the involuntary inputs to the other devices in FSX, specifically in this case helo rudders moving without any input from the HID.. The Flight Link rig seems to use standard MS drivers as there's nothing specific from them available in that regard. The serial devices (pedal/throttle box in the PFC rig) are conneted directly to a serial port on the PC. The pedals/collective on the Flight Link rig are connected THROUGH the Flight Link G-Stick housing and that housing is connected via USB to the PC. I am NOT using any external serial/USB converter plugs. Tried that a few years back with no joy..they just don't work in this setup. I just received the following today from Flight Link..... Thank you for your question. The pedals and collective are not "serial" but they connect directly to the G-Stick USB controller on the G-Stick itself via the two db15 connectors and cables. I've included a document that describes how to setup the units using Windows Game Controllers and how the small dip switches on the G-Stick should be configured. With the controls you own and fully connected, dip switches 1-5 should be in the "down" position and dip switch 6 should be in the "up" position. The dip switches are very delicate so please be careful when trying to move them. We can sell you usb controllers for the pedals and the collective. They are $50 each. Once installed, you will most likely not experience a better signal in the software than connecting them with the DB15 cables to the G-Stick as they are currently configured. The pedals and collective use similar potentiometers and the signals are the same whether coming through their own controller or through the G-Stick controller. If I use the Windows joystick setup routine, and further the one resident in FSX, I am able to assign functions to the device. But the whole purpose of this exercise is to bypass that and program all devices via FSUIPC. I'm concentrating on the G-Stick III currently and was able to program the stick buttons/hat switch via FSUIPC..no problem there. BUT..I can't seem to get the pedals and collective to be seen by FSUIPC when all settings in the FSX.cfg file were cleared out as per the exercise conducted yesterday with Paul. I am awaiting a GoFlight Ultimate Pilot rig which is why we didn't even attempt to play with the PFC devices yesterday. The PFC throttle/trim/gear unit will disappear to be replaced by the GoFlight. I've downloaded their driver file and will get to it when the equipment arrives and is ready for installation. All this having been said, I'm simply looking for a soultion whereby all devices will be seen and able to be programmed through FSUIPC. Do you believe that converting the db15 connectors to USB on the Flight Link will help? Alan
  5. I've got both PFC fixed wing and Flight Link rotary controllers. These units are fairly old and are still using serial connections in some of their setups. So while the PFC yoke and F/L G-Stick are USB connected, the pedals and throttles are still serial thru connections. In going through a function assignment process in FSUIPC today, I'm experiencing issues with reading of those axes that are using serial connections. Paul Johnson, very knowledgeable and patient guy, spent 2 hours on the phone with me today going through the setup. Prior, I was getting phantom inputs on the F/L rudders and erratic numbers in raw data through FSUIPC. Paul suggested I use this program to do assignments rather than the basic FSX platform, and when we encountered this issue, he further thought I should post about it here. So I guess the basic questions are, is there a software utility that can address the serial connectivity issue within FSUIPC, or should I consider converting those serial devices to USB? Any suggestions or assistance would be appreciated. Thanks, Alan Aronoff CYUL
  6. Pete et. al., OK, this one is wierd. I recently had my Jetliner yoke re-wired to USB. It's working fine in FS9, all buttons, switches, and other functions are normal. Move over to FSX and it's a bit different. The yoke forward/back control (pitch) is acting as such but also as a throttle. It also seems to negate the throttle on my PFC quadrant. So when I pull back on the yoke for takeoff, the throttle decreases to cut point. Moving the yoke forward inreases the throttle. If this were happening in both FS versions on my system, I'd think it might be a wiring issue. Such doesn't seem to be the case. Should I look somewhere in the FSX config file? Any other suggestions? First aid would be appreciated. Thanks, Alan Aronoff (CYUL)
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.