von Posted November 6, 2008 Report Posted November 6, 2008 I am attempting to assign and calibrate two GoFlight TQ6 throttles for the PMDG737-800. What I need is just one power range from minimum (idle power) to maximum power, calibrated without a zone for reverse thrust. TQ6 has levers (buttons) for reverse thrust which I can assign to keyboard keys F2 and F1. My options to SET are Reverse, Idle and MAX. But, I always end up with a calibrated reverse thrust zone. Is there a way to eliminate the reverse thrust zone from each calibrated throttle? My throttles are currently assigned axis as detected by FSUIPC: Throttle 1 is assigned = Z axis Throttle 2 is assigned = V axis Is V ok to use?
Pete Dowson Posted November 6, 2008 Report Posted November 6, 2008 What I need is just one power range from minimum (idle power) to maximum power, calibrated without a zone for reverse thrust. The default single generic throttle does that, as do the individual throttles in FS itself. My options to SET are Reverse, Idle and MAX. I assume you must mean in FSUIPC? You do not mention FSUIPC anywhere. The reverse option applies to the 4 individual throttles. I assume you are using those? But, I always end up with a calibrated reverse thrust zone. Is there a way to eliminate the reverse thrust zone from each calibrated throttle? Yes, of course. Simply make the reverse zone zero size. Calibrate the Reverse (minimum) and one value of the Idle zone to be the same, or as near as possible the same, then make the idle zone big enough to always reach by making sure the upper idle value leaves a reasonable area on the axis. You always need a proper idle zone in any case, to be sure you can actually always get to idle. My throttles are currently assigned axis as detectedby FSUIPC: Throttle 1 is assigned = Z axis Throttle 2 is assigned = V axis Is V ok to use? The letter assignment is based on the Windows joystick driver. it doesn't matter what it is. Pete
von Posted November 6, 2008 Author Report Posted November 6, 2008 Pete, Yes it is FSUIPC Ver 3.80 Thanks for the quick reply. I will give it another try.
Pete Dowson Posted November 6, 2008 Report Posted November 6, 2008 Yes it is FSUIPC Ver 3.80 3.80 is very much out of date and isn't supported. Current is 3.82, and there's a 3.849 available in the Announcements above. Pete
von Posted November 7, 2008 Author Report Posted November 7, 2008 Pete, Thanks for the info. I updated today to Ver 3.82. It showed as ver 3.817 in the FSUIPC registration box when selected from FS9 menu. Lastly I updated to Ver 8.849 which reports the correct version number. Now back to FSUIPC throttle assignments and calibrationlearning, for me today!
Pete Dowson Posted November 7, 2008 Report Posted November 7, 2008 I updated today to Ver 3.82. It showed as ver 3.817 in the FSUIPC registration box when selected from FS9 menu. Yes, that was a minor error, fixed immediately by 3.821. In fact 3.817 was identical to 3.82, it was the "release candidate". Lastly I updated to Ver 8.849 which reports the correct version number. Hopefully 3.849, though, not 8.849? ;-) Regards Pete
von Posted November 7, 2008 Author Report Posted November 7, 2008 Yep, You are correct, my typo there. It Is ver 3.849. I better not do that when I go to edit the FSUIPC ini file!
von Posted November 10, 2008 Author Report Posted November 10, 2008 Pete, Finally! I got my GF-TQ6 Throttles calibrated to the PMDG737-800. With reverse! WOW! I thought my eyes would start bleeding from reading so much! It took many tries to learn assign/calibrate basics. I read your tutor. Still learning. Does this portion of my ini file look right? The last two throttle lines are ending with /8? Could you tell me what the throttle line says in english? Because my throttles have no idle detent I had to make the idle range a little large. Can you see that in the numbers? Ideally, should the data in throttle line 1 exactly match the data in throttle line 2? ** Is this first calibration data section supposed to be here? I do not remember seeing it before, but it has been many moons since I had to peek inside. [JoystickCalibration] SepRevsJetsOnly=No ApplyHeloTrim=No FlapsSetControl=0 FlapDetents=No ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=0 RudderTrimControl=0 CowlFlaps1Control=0 CowlFlaps2Control=0 CowlFlaps3Control=0 CowlFlaps4Control=0 MaxSteerSpeed=60 ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes [buttons] 1=P2,4,C66079,0 ; Gear Down 2=P2,5,C66080,0 ; Gear Up 4=P2,8,K122,8 ; Track IR Center (F11) 6=H2,0,K120,8 ; Talk Squawkbox (F9) 7=P2,9,K121,8 ; Track IR Pause (F10) [buttons.Level D Simulations B767-300ER] 0=P2,6,K68,11 ; A/P Disconnect (ctrl+shft+D) 1=P2,7,K87,11 ; A/T Disconnect (ctrl+shft+W) 2=P2,1,K80,10 ; Vertical Speed Select (F/Min) [buttons.American Airlines B767-300ER TCP LDS] 0=P2,6,K68,11 ; A/P Disconnect (ctrl+shft+D) 1=P2,7,K87,11 ; A/T Disconnect (ctrl+shft+W) 2=P2,1,K80,10 ; Vertical Speed Select (F/Min) [buttons.DreamFleet Beech Baron 58] 0=P2,6,C65759,0 ;Flaps Dec 1=P2,7,C65758,0 ;Flaps Inc [MacroFiles] 1=737 OHD 2=767 3=APchart [buttons.B737-800 American Airlines] 0=P2,7,C65758,0 1=P2,6,C65759,0 2=P2,1,K80,10 [Axes.B737-800 American Airlines] 0=0Z,256,D,9,0,0,0 1=0V,256,D,10,0,0,0 [JoystickCalibration.B737-800 American Airlines] <<< New <<< ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No FlapsSetControl=0 FlapDetents=No ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=0 RudderTrimControl=0 CowlFlaps1Control=0 CowlFlaps2Control=0 CowlFlaps3Control=0 CowlFlaps4Control=0 MaxSteerSpeed=60 Throttle1=-12288,-11641,-10132,16171/8 Throttle2=-15983,-13386,-9390,14585/8
Pete Dowson Posted November 10, 2008 Report Posted November 10, 2008 Does this portion of my ini file look right? No idea. Everyone has different needs. The last two throttle lines are ending with /8?Could you tell me what the throttle line says in english? Throttle1=-12288,-11641,-10132,16171/8 Min -12288 (below that is max reverse only Idle zone -11641 to -10132 Max 16171 (above that is all max thrust) Can't remember what the option values (/n) are -- it'll probably be filter (F) or Rev, whatever you see ticked. I don't tend to edit these in the raw form and don't expect others to. Because my throttles have no idle detent I had to make theidle range a little large. Can you see that in the numbers? doesn't look very large, but the numbers depend so much on the individual device, and how it is calibrated or mapped in the windows drivers for it, that it is impossible to tell. Ideally, should the data in throttle line 1 exactly matchthe data in throttle line 2? That would only happen if both of the axes are identical in every way and are both treated and calibrated identically in the windows drivers. It can happen -- with digital devices usually (or perhaps those using optical readers rather than pots), but it's not all that likely likely. Anyway, the separate throttle levers in a real aircraft are never identically positioned for the same thrust 9unless digital as in the Airbus). ** Is this first calibration data section supposed to be here? There's normally always going to be a default set of parameters. Else how does FSUIPC know what to do for an aircraft you've not set specific stuff for? It contains no actual set calibrations in any case, only the default options. Generally there's no point anyway in having aircraft-specific calibrations unless you either have different controls for each aircraft (and so different assignments as well), or simply want them to behave differently for each (e.g. no reverse zone for a Cessna, but one for a 737). [buttons.Level D Simulations B767-300ER] [buttons.American Airlines B767-300ER TCP LDS] If you changed the parameter "ShortAircraftNameOk=..." to "substring", you could have the one section for all B767's by changing the heading in one to [buttons.B767] and deleting the other section altogether. See the Appendix about all this in the recent advanced user's guide. Regards Pete
von Posted November 10, 2008 Author Report Posted November 10, 2008 Pete, Thanks for the reply and additional information. Much appreciated. Have a great day.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now