It has been a long time since I saw this but.. When I am in decent, I have selected "Level change" and brought the throttles to idle. Auto throttle is engaged. The plane starts to come down as it should but the throttles are "hunting" They go to idle and then for some reason there is a command for like 90% throttle and then they spool back down and then back up. So my speed is a constant 10 to 15 faster then commanded. Any ideas? I am going to do a flight tonight and use Vnav and see what it does.
Just to check : try with only Spd and VS and see how the throttles behave.
You can use LNav too.
I will give this a try when I get home. I am using the PM flight model as well.
Bob, I have tried with FlCh but I do not have your issue.
My motorized TQ is from Cockpitsonic.
Quote from: GSalden on October 20, 2015, 09:53:45 AM
Bob, I have tried with FlCh but I do not have your issue.
My moto
rized TQ is from Cockpitsonic.
I am not using a motorized throttle. Shes the old fashoned kind.... ;D When I am descending I pull the throttle back to idle.
Is the vertical speed constant when its doing this?
What is the throttle mode displayed on the PFD? (top left)
Quote from: KyleH on October 20, 2015, 11:01:51 AM
Is the vertical speed constant when its doing this?
What is the throttle mode displayed on the PFD? (top left)
Going to fire up the sim and will have a few of these answers. More to come.
Ok I just flew the milk run. Takeoff to TC fine. Cruse to TD fine. Before TD I dialed in 220knts on the MCP. At TD select VS dialed in the - altitude to get me to my desired altitude at my waypoint, and down we go an so starts the hunt. Air speed stayed 10 to 20 knots faster then MCP commanded speed all the way to landing. Kyle, upper left "MCP"
Ok. V/S mode does not control airspeed.
The plane will try and maintain the airspeed set in the speed window using throttle, but in V/S mode, the selected vertical speed is the driving restriction.
FLCH/LVL CH mode descends via the speed set in the speed window. It sets the throttles to idle, then pitches for the selected airspeed and gets whatever vertical speed that happens to correlate to.
V/S mode is not meant to be used for long climbs or descents. It is typically only to be used for short periods of time.
For descent from cruise use LVL CH or VNAV.
I need to do a comprehensive write up or video series on this as it keeps coming up. If I was arriving early enough, I'd do a training session at Worldflight.
Well it was a very short decent. 5000 to 2600. I am having the hunt in FLCH LVL change as well and speed running 10-25knts faster then commanded. It does this through approach as well.
There is secret sauce going on with LVL CH as well for short descents.
The formula it uses is: V/S = change in altitude/2.
So: if your descending from 35,000' to 12'000 as would be normal, it would try to give you a 11,500 foot per minute descent. Obviously that would cause an overspeed, so the airspeed is limited to that which is in the MCP speed window.
But, descending from 5000 to 2500', it will give you 1250 foot per minute v/s, and use thrust to maintain the airspeed set in the speed window.
That's how the real thing works, not sure if PM emulates that.
What does it do if you pull the speed brakes? If it throttles up, then it's trying to maintain some speed set somewhere.
The spooling up and down though sound's like a potential software/hardware issue.
Quote from: KyleH on October 20, 2015, 04:30:56 PM
There is secret sauce going on with LVL CH as well for short descents.
The formula it uses is: V/S = change in altitude/2.
So: if your descending from 35,000' to 12'000 as would be normal, it would try to give you a 11,500 foot per minute descent. Obviously that would cause an overspeed, so the airspeed is limited to that which is in the MCP speed window.
But, descending from 5000 to 2500', it will give you 1250 foot per minute v/s, and use thrust to maintain the airspeed set in the speed window.
That's how the real thing works, not sure if PM emulates that.
What does it do if you pull the speed brakes? If it throttles up, then it's trying to maintain some speed set somewhere.
The spooling up and down though sound's like a potential software/hardware issue.
Well there is no hardware involved. I do not have a motorized TQ. If I throw the boards the plane still does not slow down as I think it should so someplace there is another speed I guess.. Time to hunt through the CDU pages I guess. Never had this issue before...
My thought is I am missing a setting while setting up the CDU. Any thoughts on this?
Bob, I am thinking this is an N1 Limit setting in the CDU. I am guessing here. But levelCH I believe uses the N1 Limit setting in the CDU. What is the N1 Limit setting set to?
Trev
If the mode in the PFD is MCP, then it is trying to set the speed from the MCP not the CDU.
The N1 setting in the CDU is used for climb, not descent.
Could you shoot a video of this Bob. Otherwise we are just stabbing at things.
Quote from: Trevor Hale on October 21, 2015, 04:28:58 AM
Bob, I am thinking this is an N1 Limit setting in the CDU. I am guessing here. But levelCH I believe uses the N1 Limit setting in the CDU. What is the N1 Limit setting set to?
Trev
I think you hit the nail on the head! I did a little more looking around inside the CDU last night and found that speed reference. But.. This does not explain the hunting during approach.
Quote from: KyleH on October 21, 2015, 04:44:30 AM
If the mode in the PFD is MCP, then it is trying to set the speed from the MCP not the CDU.
The N1 setting in the CDU is used for climb, not descent.
Could you shoot a video of this Bob. Otherwise we are just stabbing at things.
As a matter of fact I think I can. I am still pretty sure it is the way I am programming the CDU. And I also have to wonder if it has something to do with the Decent speed issues that Gsaldan is having in the other thread. I have used the PM model in the past with out this issue so I do not think it is the model. Maybe I should try it with the default 73 model?
Unless your using VNAV the CDU does not affect descent.
Quote from: KyleH on October 21, 2015, 04:53:17 AM
Unless your using VNAV the CDU does not affect descent.
Ok this is what I thought. But I may still have a setting wrong in the software. I will probably not get another chance to fly it until I get back from WF at this point, but we can talk more about it while we are all there!
Bob,
I am using the FSX default 737 in P3Dv3.
Even without PM the "hunting" like you described it appears a little and the speed stays 15 knots above the dialed mcp speed.
I did modify the flaps and spoilers drag a little to match more like what I was used to with the PMDG 737 NGX and Ifly CBE 737-800.
We can further dicuss it here when you getback.
If one of you guys is interested in trying an improved PM 737-800 flight model ( airfile + aircraft.cfg file ) sent me a PM.
Several years ago I did the same for the Captain Sim757 and it was published on their website.
This model "feels" more real , follows the descent path better and has improved drag, thrust and lift values.
http://www.mycockpit.org/forums/showthread.php?t=10876&highlight=cycle+time (http://www.mycockpit.org/forums/showthread.php?t=10876&highlight=cycle+time)
Keep in mind my problem is not a hardware issue as I do not have throttles that move. This is a software issue of some kind. It may not be PM at fault. When I get home I will do more digging.
Quote from blueskydriver about this issue at MyCockpit :
"It's the aircraft model from PM... I switched to the Prosim737 aircraft model along time ago and PM works great with that model. I still use PM that way now. "
I have asked him what exact model and aircraft.cfg he is using.
If he helps I will share them with you to try.
Update :
Three flightmodels I tested with :
- default FSX 737
- Project Magenta 737 NGX
- custom made flightmodel based on the Ifly
In LNAV and VNAV no issues.
With MCP speed there is throttle hunting which causes the speed to stay +- 15 knots faster than the dialed in speed.
Altitude Hold is also not stable. The aircraft either descents a bit and then climbs back, or climbs a bit and then descents back.
This is with all flight models.
Disabling the PM mcp and using the default mcp solves these issues.
I tried playing around with the cycle time in the MCP menu. Low till 25 ms and all the way up to 100 ms.I uses 30 now.
I tried with Descent/Speed control on/off.
Nothing fixes this.
In the CDU Maintenance / AT page 1: all sensivities set to 120 for spd / spd / thr / lvl/ mach . Page 2 P/D both 120.
At altitudes higher than 11.000ft the speed is accurate with mcp speed. Alkso no issues with pitching up/down.
250 knots = 250 knots
220 knots = 220 knots
210 knots = 210 knots.
In the CDU Maint AT pages there are settings for <11000ft and >11000 ft.
My tests showed that higher than 11000 ft there was no issues...
The approach issues where the aircraft starts to zig-zag or pitch up/down I was able to fix with my custom flight model.
My workaround :
1 Manually : When capturing the localizer I turn off AT and apply thrust manually. In this way I am able to land with VorLoc and App and make a nice landing.
2 Autolanding : When capturing the localizer I set the mcp speed to 15 knots below the speed I need to fly. Then the aircraft flies at the speed it has to.
At 500 ft I set the MCP speed to Vref -5 instead of Vref + 5...
This causes a very nice autolanding with a beautifull flare....
I can conclude that the PM mcp alone or icw the CDU is causing the speed/altitude/throttle hunting issues...
In several replies years ago Jonathan wrote that they never found the cause but it was something in FSX...
With Fs2004 they never had the issue.
Therefore we have to find a better workaround ourselves...
Unfortunately I have sent my flight models to 3 people and no one has given feedback up to now.
Imho we can make things better if we do this together.
So come on guys, lets solve this...
Hi Gerard,
I'm sorry I didn't get a chance too help you. Karen and I have been so caught up in dealing with issues concerning our new shed/hangar that I haven't had the time to turn my simulator on and check things for you. Not sure when I'll get too it...
John
I want to share my experience. My pm-setting as well shows throttle hunting. If I disable all weather injection, the system works perfect and keeps the speeds flawless...
Even if I use weather from the pm-instructorstation speedhunting occures. Usually I use FSGlobalWeather in a network setting.
My next step is a trial series with several airmodels. ProSim model I will give a try as well, but the model has to be adapted and I´m not sure about it.
I will keep you informed about the results. I´m interested if anyone could confirm the weather relation to speed hunting.
At the moment I use a the pm 737 flightmodel with some minor modifications.
Bernhard
Bernard,
If you are interested give me a pm with your email adres and I will sent you a dl link for my flightmodel.
I have made a Topic at the Fsuipc forum and asked for help for a LUA script which slows down the flying speed by 10 knots when under 11000 ft.
Eg : now mcp speed is 135 --> flying speed is 145-150
However Pete is on holidays till next week, so it might take some time.
Also later I want to take a better look at the throttle hunting issue.
I was thinking about a delay feature. Now they go up and within 2 seconds they come down.
If there is a delay of 2 seconds they won't go up that high and act more stable.
Regarding your findings with the throttle hunting :
When using certain high-fidelity aircraft including PMDG 747, MD-11 or other high-sensitivity aircraft, turbulence effects can result in stability problems and potential s-turn autopilot hunting. Both FSUIPC turbulence effects and FSX internal turbulence effects (used by AS and FSX itself) can cause these problems. In order to minimize these harmful effects, it is recommended to minimize/disable turbulence effects in both FSUIPC (if in use) and FSX.
FSUIPC (if installed and FSUIPC wind smoothing/turbulence effects are enabled) - Edit These FSUIPC.ini settings:
TurbulenceRate=0.5,2.5
TurbulenceDivisor=40,40,80,80
FSX - Edit the following FSX.cfg setting (under [Weather]):
TurbulenceScale=0.500000
Thanks for the hints regarding turbulenceRate. I will give them a try. My proposal to sort things out is to start with essential settings, perhaps configure a testbed on a second system. When disturbing factors identified, then they might be eliminated.
thanks & regards
Bernhard
Greetings
I have had this issue for several months. A/T is perfect when weather is turned off, but as soon as weather injection occurs the A/T begins to hunt - especially in turns and descents. I am using ProSim737 flight model with Opus FSI weather. I have attempted a work-around by turning off GRIB data in OpusFSI, as well as other variables in Opus and FSUIPC but the issue still persists.
I spoke with Stephen at Opus about this issue and it appears the problem is (maybe) an underlying fault in FSX.
I have trialed the Salden's suggestion in addition to advice provided on another forum which suggested to alter the max_throttle_rate.
I am using the ProSim V2 flight model and have made a post on their forum: http://www.prosim-ar.com/forum/viewtopic.php?f=23&t=9069&sid=1a6ab1ed018250b3c705f7865c3d4e88&p=66629#p66629 (http://www.prosim-ar.com/forum/viewtopic.php?f=23&t=9069&sid=1a6ab1ed018250b3c705f7865c3d4e88&p=66629#p66629)
Cheers, WilloW
Well after several tests, it is not just weather related, at least no my issue. With live weather (Activsky Next) on it is much more pronounced. 5 flights tonight and never turning on weather, the AT and speed stayed out of whack. Speed stayed several KTS's over commanded. Now with weather off the "S" turns on approach went away. This is Project magenta with PM MCP turned to "off". More tests to follow...
Thanks for the note Bob
The thread over at ProSim has a detailed post on the issue
http://www.prosim-ar.com/forum/viewtopic.php?f=23&t=9069&sid=1a6ab1ed018250b3c705f7865c3d4e88&p=66629#p66629 (http://www.prosim-ar.com/forum/viewtopic.php?f=23&t=9069&sid=1a6ab1ed018250b3c705f7865c3d4e88&p=66629#p66629)
Cheers, WilloW
If the PM mcp is turned off than the default 737 mcp will be used.
Just found this... Go to the [autopilot] section of your aircraft.cfg file and locate max_throttle_rate. if it isn't there add it. This value is always set to 0.10 by default. Start by cutting this value in half to 0.05 or less.
max_throttle_rate
| This value sets the maximum rate at which the autothrottle will move the throttle position. In the example, the maximum rate is set to 10% of the total throttle range
Douglas DC-3( max_throttle_rate=0.100000 )
|
|
This should fix your issue. you will have to find the "Happy medium" Too slow and your throttle will never catch up. Too fast and it will always blow past the setpoint.
Trev
Quote from: Trevor Hale on February 28, 2017, 09:30:48 AM
Just found this... Go to the [autopilot] section of your aircraft.cfg file and locate max_throttle_rate. if it isn't there add it. This value is always set to 0.10 by default. Start by cutting this value in half to 0.05 or less.
max_throttle_rate
| This value sets the maximum rate at which the autothrottle will move the throttle position. In the example, the maximum rate is set to 10% of the total throttle range
Douglas DC-3( max_throttle_rate=0.100000 )
|
|
This should fix your issue. you will have to find the "Happy medium" Too slow and your throttle will never catch up. Too fast and it will always blow past the setpoint.
Trev
This problem actually rectified itself on my system after a few version updates from ProSim-AR. Still the information is good to know should the issue occur again. Cheers, WilloW