Jump to content
The simFlight Network Forums

737nut

Members
  • Posts

    36
  • Joined

  • Last visited

About 737nut

  • Birthday 01/01/1970

Contact Methods

  • Website URL
    http://www.737nut.com

737nut's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Every time i do a 'clean' install of FSUIPC and or button assignments, the NGX works great. Shut the sim down and re-start and the problems are back. Be interesting to see if you have found something. Rob
  2. I had to use the first example you gave to get it to work, somewhat. The problem I am having now is that virtual joy buttons 1 and 3 bounce back and forth and never stop. I tried changing fasttime and poll rate to no avail. I checked in the game controller properties and the buttons are not showing this on/off cycle so i'm not sure what is causing it. I also checked the inputs via a 3rd party software and monitored the inputs, no bouncing or erroneous inputs shown. So why is FSUIPC seeing a rapidly changing input? ( I labled the input as Polabs and Virtual, per my question above, is this correct?) Thoughts? Thanks, Rob
  3. I have a question. I don't have a Bodnar card but use an interface called a pokeys card. I have copied over the HID name below. What do I put in the Vendor and Product code lines and does it need the quotations? I have 8 encoders hooked up to this card that is seen as a vitual joystick and has 32 button inputs and supports encoders in paired inputs just like the Bodnar card. Thanks, Rob Device at "\\?\hid#vid_1dc3&pid_1001&mi_00#b&323e0194&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=1DC3, Product=1001 (Version 16.0) Manufacturer= PoLabs Product= Virtual Joystick Serial Number= PoKeys Usage Page: 1 Input Report Byte Length: 17 Output Report Byte Length: 0 Feature Report Byte Length: 0 Number of Link Collection Nodes: 2 Number of Input Button Caps: 1 Number of InputValue Caps: 6 Number of InputData Indices: 38 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Buttons range 1 -> 32 at indices 6 -> 37 Value U/RX at index 0, range 0 -> 1023, using 16 bits Value V/RY at index 1, range 0 -> 1023, using 16 bits Value Z at index 2, range 0 -> 1023, using 16 bits Value Y at index 3, range 0 -> 1023, using 16 bits Value X at index 4, range 0 -> 1023, using 16 bits Value Thr at index 5, range 0 -> 1023, using 16 bits ************************************************************************** Device at "\\?\hid#vid_1dc3&pid_1001&mi_01#b&1f0de556&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=1DC3, Product=1001 (Version 16.0) Manufacturer= PoLabs Product= Communication Interface Serial Number= PoKeys Usage Page: FF00 Input Report Byte Length: 65 Output Report Byte Length: 65 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 0 Number of InputValue Caps: 1 Number of InputData Indices: 1 Number of Output Button Caps: 0 Number of Output Value Caps: 1 Number of Output Data Indices: 8 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Value 0x01 at index 0, range 0 -> 255, using 8 bits ************************************************************************** Device at "\\?\hid#vid_1dc3&pid_1001&mi_02#b&bddc918&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=1DC3, Product=1001 (Version 16.0) Manufacturer= PoLabs Product= Virtual keyboard Serial Number= PoKeys Device is a keyboard Usage Page: 1 Input Report Byte Length: 35 Output Report Byte Length: 0 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 2 Number of InputValue Caps: 0 Number of InputData Indices: 110 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 **************************************************************************
  4. I'm having a strange problem that just started yesterday. I downloaded the new PMDG NGX the day it was released and had ZERO problems for almost 2 weeks. Last night, i started FSX and every time i loaded the NGX i would get a CTD (crash to desktop) I thought long and hard what had changed, I did assign some buttons a couple of days ago but it worked after that ok. So i removed the Modules folder from FSX and re-started FSX. Now the PMDG NGX loads and works fine!? If I put the module folder, ie; FSUIPC back in the FSX folder, it causes a crash of FSX to the desktop. The error says it's in the NGX.dll so why does or why is something in FSUIPC causing this that didn't the first 2 weeks I had the NGX using it fine with FSUIPC? I am using FSX SP2 with acceleration FSUIPC vs 4.726 PMDG NGX w/ hotfix 3 I'm at a loss where to even begin troubleshooting this issue. Thanks for ideas Rob
  5. Pete, Sorry if i confused you. Certainly not my intentions but understandable as i pulled this post up from the dead. :) On page one of this thread you stated there were internal feedback tables for the FSUIPC AP functions. You mentioned some timing and coding issues converting to FSX. Then later in the thread you mentioned that 90% N1 (an apparent max limit set in the internal table?) was not enough to climb in the jet and wondered if FSX was underpowering the aircraft. Based on those staements i assumed that there was a parameter with-in FSUIPC that i could change to set the max value that FSUIPC would use to hold my set airspeed. The stock planes and my CS727 will go over 100% no problem but only the FSUIPC speed hold seems limited to the aforementioned 90% N1 max setting. I hope that helps you some? Thanks for your time and this great product! Rob
  6. Pete, I'm not sure where it is but i'll try and find something. I was going off the presumption that where you stated 90% didnt seem high enough and seeing as how when i engage fsuipc speed hold function the max N1 i see is 90%. I was assuming it was internal to fsuipc? sorry
  7. Pete, This is a quote from you a few post back in this thread, You hit the nail on the head about the 90% limit being to low. The 727 i fly needs about 97% to maintain a good climb.
  8. Hi Pete, I just tested the fsuipc speed hold function using FSX and Captain Sim 727, works great but it needs to go a little higher on the N1. Is there an .ini setting that wiould give me more N1/power to hold speed? Sorry for the long delay in testing. Life duties called. Thanks, Rob
  9. It worked very well at holding speed on the DF727. They didn't model the later 727-222's or the converted -100 which is what i am building. I got lucky and got a real 727 TQ with the AT option! I appreciate you adding it back in and i will test and advise how it goes. I may even add the moving thottles as well. Thanks, Rob
  10. I was using it to control the airspeed on my 727 since dreamfleet didn't have it in their plane and the 727sim i am modeling has AutoThrottle. In FSX, i thought i was using it to control the Captain Sim 727 throttle as well but i could be wrong. I do know it worked great in FS9 so it would be great to have it available in FSUIPC4 :wink: I have no autothrottle now in FSX in my 727. Thanks, Rob
  11. I have 4.28 which i downloaded last week and installed. I found the document with all the info located in your SDK files i downloaded. Here is the info found in that file, "FSUIPC Autopilot feedback control facility ========================================== This is preliminary and rudimentary documentation only. Please feel free to ask questions. Offsets 0700 - 0717 = Pitch control by elevator and/or elevator trim Offsets 0718 - 072f = Bank control by aileron Offsets 0730 - 0747 = KIAS/GS control by throttle(s) Offsets 0748 - 075F = Mach control by throttle(s) The latter two are mutually exclusive -- if both are enabled only KIAS operates, the other is switched off. Each of these blocks of 24 bytes are used as follows: 0-7 Double target pitch or bank, in degrees, speed in knots or Mach 8 Switch to enable the control loop. This is 0 for "off", non-zero for "on". FSUIPC reduces this by 1 every 50-55 mSecs, so your program needs to write FF here at intervals not exceeding 14 seconds -- do it every 5 at least, for safety. This mechanism is to prevent the user losing control if your program crashes or terminates without clearing this down. 9 Flags: 2^0 = 1 No trim-out. This is only applicable to pitch control, By default FSUIPC will control the pitch using the elevator, but then, when very close (less divergence than your original minimum), it will trim out the elevator divergence. This is more or less what a pilot would do and seems to be the way the real aircraft work too, as far as we've determined. However, if you do not want this transfer of offset to the trim, set this flag. 2^1 = 1 Trim only: again, this is only applicable to pitch control. Normally FSUIPC will control the pitch by elevator adjustments. If this flag is set it will use the trim only. Note that the flags are independent -- even if the trim is used for control, any user-set or remaining deviation on the elevator can also be trimmed out when the pitch is closely achieved. 2^2 = 1 Speed and Mach control only: use EPR for engine limits instead of N1% (see below). 2^3 = 1 Speed control only: use ground speed, not indicated air speed 10-19 Factors used in the feedback loop calculations. These are 5 16-bit values, as follows: 10-11 value L = unsigned low difference, in degrees/knots/machhundredths * 256 128 == 0.5 degrees default for pitch and bank 51 == 0.2 knots for speed 10 == 0.0004 mach (.04 1/100ths) 12-13 value H = unsigned high difference, in degrees/knots/machhundredths * 256 2560 == 10.0 degrees default for pitch and bank 7680 == 30 knots for speed 1792 == 0.07 mach ( 7 1/100ths) 14-15 value R = signed max rate of change to attempt, in degrees/knots/machhundredths * 256 per sec 307 == 1.2 degrees per sec default for pitch and bank 589 == 2.3 knots per sec default for speed 256 == 0.01 mach per sec (1 1/100th) (The sign allows reversal if needed) 16-17 value Fh = signed high fiddle factor, scalar * 256 25600 = 100 default for pitch and bank 7600 = 29.7 default for speed and mach 17-18 value Fl = signed low fiddle factor, scalar * 256 12800 = 50 default for pitch and bank 3600 = 14.8 default for speed and mach Note that you can change these at any time, but the change does not become effective until you next enable the feedback control after it has been turned off (and seen to be turned off). This is because FSUIPC builds a lookup table from these values, it doesn't use them directly. New values will also be applied after FS has been paused, put into slew mode, or entered menus or modal dialogues. This is because all the feedback operations are suspended during these times (to prevent absurd runaway changes) and this is effectively achieved in the same way as you turning the operations off and on again. 20-21 Parameter 1: 22-23 Parameter 2 The use of these depends on the control: For pitch and bank, Parameter 1 is the maximum change to the FS control in any one "tick". Default is 512 (out of the range of -16383 to +16383 provided by the control). The pitch and bank loops operate at FS's tick rate of 18/sec (approx), so this limits the change to 9216/sec. For pitch only, parameter 2 is the amount of trim to transfer per tick when "trimming out", unless this is prohibited by the option flag 2^0. By default this is 32 -- i.e. 576 per second. This will help applications in achieving realistic trim wheel movements -- I suspect there's a limit to how fast they really spin. Certainly the PFC motorised trim wheel will be regulated (but I don't know its speed yet). For speed and mach control, Parameter 1 gives the maximum engine setting and Parameter 2 gives the minimum. This, by default, is the N1% value, in exactly the same units as provided by FSUIPC (e.g. offset 0898 for Engine 1). For props this will relate to the RPM of course. The defaults are 90% (value 14745) and 20% (3276) respectively. If you want the limits in terms of EPR, set the flag 2^2 and replace these limits by ones in the same units as the FSUIPC supplied EPR (e.g. offset 08BC for engine 1). Note that FS does not provide EPR for props nor for all jets. FSUIPC controls each engine separately within the same limits, but using the same throttle changes for each, calculated in the same way. It only operates throttles for engines which exist and which are flagged as "combusting" (e.g. FSUIPC offset 0894 for Engine 1). Note that changes to the target, the switch, the flags, and Parameters 1 and 2, can be made at any time and are effective immediately, unlike the factors themselves. The feedback loop is roughly 18 times per second for all controls. The actual target rates are calculated from the difference in target value and current value, using rates of change, and using the variables detailed above. The pitch and bank system seems to work quite well. There are frequent little trim changes, but maybe these are realistic (time to watch some cockpit videos I think! ). The speed control needs tuning -- especially the Mach one which is way out at present. The "fiddle factors" are just my "guesses" and need refining. The mach minimum and maximum and the max rate are also my initial guesses. My testing facilities are still in place, so you can play with those. To use them, do this: 1. Edit the FSUIPC.INI file, adding "Debug=Please" into the [General] section. 2. Load up FS, go to the FSUIPC Logging page and enter "32" into the Extras logging edit box. 3. Now go to the Keys or Buttons page. You can assign key presses or buttons to the following extra controls now made available: Fsuipc bank hold off Fsuipc bank hold on Fsuipc bank hold set Fsuipc bank hold toggle Fsuipc mach hold off Fsuipc mach hold on Fsuipc mach hold set Fsuipc mach hold toggle Fsuipc pitch hold off Fsuipc pitch hold on Fsuipc pitch hold set Fsuipc pitch hold toggle Fsuipc speed hold off Fsuipc speed hold on Fsuipc speed hold set Fsuipc speed hold toggle These should be self-explanatory. For the "Set" ones, put the value to be set as the parameter -- only whole numbers, but okay for testing (degrees, knots, or 100 x mach). For the "on" and "toggle" controls the current pitch/bank.speed or mach becomes the target to maintain. When this test option is enabled the timeout (switch decreasing by 1 each tick) does not apply, for obvious reasons. Have fun and let me know how you get on! ========================================= Pete Dowson, February 2005 =========================================
  12. Hello, I reinstalled FSX and the latest FSUIPC4 onto my new PC. I added Debug=Please in the fsuipc.cfg set 32 in the logging extras section, when i go to assign my buttons to Fsuipc speed hold off and Fsuipc speed hold on, those are not shown in my choices. It worked on my last set-up just fine. My new system uses Vista Premium Home 32, FSX thru SP2, and my old set-up was WINXP and FS9/FSX. Thanks, Rob
  13. I just downloaded the latest version of FSUIPC and now all my servo driven real aircraft engine gauges move VERY smooth and fluid like motion, just like the real plane!!! Thank you for fixing what has been an annoying problem with FS data for a long time! Rob
  14. Pete, Whenever you get to with-in 800-1000 foot of your selected AP altitude, you get an aural and visual alert. I have both in my cockpit that i want to activate but have been unsucessful. I'm surprised it hasn't been touched on by others. I posted in several forums asking how others made theirs work but got no response. Thanks, Rob
  15. Every default FS9 Jet/TurboProp, Every add-on jet, Project Magenta, ALL have and altitude alert either by an indicator on the MIP or a sound. Why isn't there an offset for this important function. Thanks, Rob
×
×
  • 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.