434 THROTTLE AXIS MISMATCH CAUSES HOT ENGINE AT RAMP START
-
Goodevening gents,
As I see some of us have problems with FTITT at ramp start caused probably by a windows and BMS 434 Throttle axis mismatch leading to Hot Starts.
Thats not the case with 433 cause with the same calibration exiting 434 and entering 433 engine starts without problems (idle and burner positions not altered). In 434 when in pit the throttle handle is not at full aft position when TQS is fully retracted, but when in 433 the handle is full aft and matches the TQS position.
Please if others have the same problems please report it here including your throttle type.
If anyone have solution or any suggestions to this specific problem report it here.
My throttle is TQS with vipergear hall and tusba r1.
Thanks -
Have you tried re-calibrating your TQS as part of your setting up of your 4.34 controls?
How does your throttle report under BMS 4.34>Contollers>Setup does the blue bar movement correspond with the TQS physical movement? if not, Iād suggest re-calibrating.
Have you contacted Realsimulator for their advice, I have always found them to be very helpful when troubleshooting their products.
-
Ddoc blue bar moves correctly at both main and advanced pages. But how do you explain that it only occurs with 434?
-
4.33 and 4.34 do not have the same install configuration. Not altering your idle and AB setup just means you havent set it yet in 4.34.
If you use the Idle Cutoff setting in the config, Id suggest resetting the idle position in setup (position throttle slightly above the end of its travel, slightly below where you want idle to be, then RIGHT click the Set AB button).
Positioning the throttle ahead of this position puts the throttle at IDLE or above. Positioning the throttle aft of this position puts the throttle in OFF.
-
Blue,
The axismapping.dat and joystick.cal files are perfectly compatible from 4.33 to 4.34.
I doubt the Op problem is a calibration issue; If it works in 4.33 there is no reason it doesnāt work in 4.34
the trick is to adapt to the new FTIT code:
1. move your throttle all the way up and down before strating your engine. You need to wake up the throttle position. This wasnāt necessary when starting from Ramp in 4.33, it is now in 4.34
2. in 4.33, we strated the engine by advancing the throttle (or clicking idle detent) when JFS brought the engine to (above) 20%, which is correct. In 4.34 you have to wait till min 25%. That slight deviation created quite a lot of hotsartsIMHO itās a bit too restrictive, but honestly, itās great to HAVE to check that FTIT and see it increasing too quick.
After a while you can detect the Hotstarts even when the FTIT is not at 400Ā° yet because of its rate of increase.
And itās easy to fix it as well.Early this week I had a throttle disconnect while ramping and sure enough it turned into a hotstart as well. I could reconnect my throttle but by the way I did, the hotstart was past salvageable. I had to cancel my flight.
Well it wasānt because of the hotstart but rather that stupid disconnect.Throttle position and calibration became sure enough more critical with 4.34. Maybe a bit too much I agree but once you have identified the reason why you have many hotstarts, itās easy to overcome them.
-
@Red:
Blue,
The axismapping.dat and joystick.cal files are perfectly compatible from 4.33 to 4.34.
They are not compatible.
4.34 added three new axes and also changed joystick.cal format.
I had to change those .dat/.cal file generating logic to update my Alternative Launcher to support 4.34.
When BMS detect axismapping.dat/joystick.cal has fewer axes information or unmatched format, it will reformat them. -
@Red:
Blue,
The axismapping.dat and joystick.cal files are perfectly compatible from 4.33 to 4.34.
I doubt the Op problem is a calibration issue; If it works in 4.33 there is no reason it doesnāt work in 4.34
the trick is to adapt to the new FTIT code:
1. move your throttle all the way up and down before strating your engine. You need to wake up the throttle position. This wasnāt necessary when starting from Ramp in 4.33, it is now in 4.34
2. in 4.33, we strated the engine by advancing the throttle (or clicking idle detent) when JFS brought the engine to (above) 20%, which is correct. In 4.34 you have to wait till min 25%. That slight deviation created quite a lot of hotsartsIMHO itās a bit too restrictive, but honestly, itās great to HAVE to check that FTIT and see it increasing too quick.
After a while you can detect the Hotstarts even when the FTIT is not at 400Ā° yet because of its rate of increase.
And itās easy to fix it as well.Early this week I had a throttle disconnect while ramping and sure enough it turned into a hotstart as well. I could reconnect my throttle but by the way I did, the hotstart was past salvageable. I had to cancel my flight.
Well it wasānt because of the hotstart but rather that stupid disconnect.Throttle position and calibration became sure enough more critical with 4.34. Maybe a bit too much I agree but once you have identified the reason why you have many hotstarts, itās easy to overcome them.
25% you sayā¦ this explains why I always get a hotstart following the IRL checklist procedure - which is to introduce fuel above 20%, or max motoring RPM if that is less than 20% RPM (not a factor in BMS as pressure altitude in BMS doesnt seem to affect JFS motoring RPM).
The advice given in the forum back in 4.32 and 4.33 was to wake the throttle by moving it up and down before starting the engine. Realistically, even starting at 19.8% RPM should not have much chance of a hot startā¦ but in BMS this is guaranteed.
The axismapping files perhaps are compatible; I havent checked. The OP didnt say he copied those from his original install anyway, so I assumed he was not aware that 4.34 is a standalone install.
-
25% you sayā¦ this explains why I always get a hotstart following the IRL checklist procedure - which is to introduce fuel above 20%, or max motoring RPM if that is less than 20% RPM (not a factor in BMS as pressure altitude in BMS doesnt seem to affect JFS motoring RPM).
The advice given in the forum back in 4.32 and 4.33 was to wake the throttle by moving it up and down before starting the engine. Realistically, even starting at 19.8% RPM should not have much chance of a hot startā¦ but in BMS this is guaranteed.
The axismapping files perhaps are compatible; I havent checked. The OP didnt say he copied those from his original install anyway, so I assumed he was not aware that 4.34 is a standalone install.
no itās not garanteed
below 15% , this is garantee
below 20 % this is a 70% chance
else this is a 2% chanceso startup between 20 and 25 (and even 25) is 2% chance.
-
Then Im just having a very unusual series of rolls on that percentage table, I guess. I havent done hundreds of flights yet, though. So its possible, I guess.
-
Then Im just having a very unusual series of rolls on that percentage table, I guess. I havent done hundreds of flights yet, though. So its possible, I guess.
are you using Analog detent or Keyboard detent ?
-
Then Im just having a very unusual series of rolls on that percentage table, I guess. I havent done hundreds of flights yet, though. So its possible, I guess.
I suppose itās not the problem, but still, on which block? Some, like the -52 and their engine, seem to hotstart when they actually donāt.
-
Analog, Idle Cutoff, block 40
-
Analog, Idle Cutoff, block 40
Do you systematically put full throttle and back prior to JFS start ?
-
Well FTIT rise quickly after15% rpm and when at 20% engine is already on fire. Mayby its a calibration issue. Tonight I 'll try to reset to default and connect TQS via cougar Stick and calibrate it through CCP and then to follow the āwake up the throttleā procedure. Analog idle cutoff all blocks.
-
Well FTIT rise quickly after15% rpm and when at 20% engine is already on fire. Mayby its a calibration issue. Tonight I 'll try to reset to default and connect TQS via cougar Stick and calibrate it through CCP and then to follow the āwake up the throttleā procedure. Analog idle cutoff all blocks.
Do you systematically put full throttle and back prior to JFS start ?
-
Do you systematically put full throttle and back prior to JFS start ?
No not that often! I didnāt have such issues with 433. I 'll try some starts with wake up procedures tonight.
Ī£ĻĪ¬Ī»ĪøĪ·ĪŗĪµ Ī±ĻĻ ĻĪæ SM-A510F Ī¼ĪæĻ ĻĻĪ·ĻĪ¹Ī¼ĪæĻĪæĪ¹ĻĪ½ĻĪ±Ļ Tapatalk
-
No not that often! I didnāt have such issues with 433. I 'll try some starts with wake up procedures tonight.
Ī£ĻĪ¬Ī»ĪøĪ·ĪŗĪµ Ī±ĻĻ ĻĪæ SM-A510F Ī¼ĪæĻ ĻĻĪ·ĻĪ¹Ī¼ĪæĻĪæĪ¹ĻĪ½ĻĪ±Ļ Tapatalk
this is absolutly mandatory in 4.34 for those who use analog idle cut off
you must synchronize your throttle position before JFS start, therefore move full range up and down your throttle
you have of course a physical Detent ? (not the one in the cougar )
-
Do you systematically put full throttle and back prior to JFS start ?
I systematically move the throttle before engine start. Im unsure whether to the stops - I move it until I see it move in the pit, then retract it fully. Part of the VERIFY check; Throttle - OFF.
-
I systematically move the throttle before engine start. Im unsure whether to the stops - I move it until I see it move in the pit, then retract it fully. Part of the VERIFY check; Throttle - OFF.
So you should be safe
No spiking of your throttle ?
-
Pretty sure not. Iāll do some more starts when I get a chance tonight and make sure itās not just bad luckā¦ Iām a bit busy atm