v0.1.3 AP Problems
-
@martyn I did another flight (by the way I am using the 100 version), but this time it worked perfectly. I will post screenshots the next time the problem occurs.
However, one thing I would like to note is that the instant I set a new altitude (6300ft) and armed it (current altitude was 16000ft), there was a long beep like when the altitude reaches within 1000ft of the target. Every time I had the AP problem, this beep has been there. But this time, AP descent worked perfectly. -
I too seem to have encountered an issue with the AP when descending with version 1.4. Pressing ALT ARM triggers the horn to sound and the plane starts its descent immediately from ALT HOLD and quite violently too. In order to descend properly I have to hold the plane in altitude hold, start the descent with vertical speed mode then adjust selected altitude and press ALT ARM.
Cheers :)
-
@laurens Can you also post the screenshots requested above? This is proving difficult to reproduce so that information would be greatly appreciated
@martyn
I made a couple of test flights. The first flight went well, no problems did show up. But the sound of the horn was there as soon as “ALT ARM” was selected.The second flight I tested if the horn also was heard as I selected a higher altitude.
In levelflight I selected a higher altitude and as soon Alt ARM was selected the sound was there. So I deselected Alt ARM, and then the plane went up while “ALT” is stil selected.
-
@laurens Can you also post the screenshots requested above? This is proving difficult to reproduce so that information would be greatly appreciated
-
@martyn I did another flight (by the way I am using the 100 version), but this time it worked perfectly. I will post screenshots the next time the problem occurs.
However, one thing I would like to note is that the instant I set a new altitude (6300ft) and armed it (current altitude was 16000ft), there was a long beep like when the altitude reaches within 1000ft of the target. Every time I had the AP problem, this beep has been there. But this time, AP descent worked perfectly. -
Can you all try using this WASM gauge? Download here
The file needs to be moved into this location, overwriting the existing file: \Packages\Community\justflight-aircraft-146\SimObjects\Airplanes\JF_146_100\panel
I just tested the new gauge, could not find any of the problems we had. The horn works as it should when setting a new altitude and arm it. No sound, only when in range of the target altitude.
I made several descents in my test flight, and all went well.
Thanks for solving this problem so quickly.
-
Can you all try using this WASM gauge? Download here
The file needs to be moved into this location, overwriting the existing file: \Packages\Community\justflight-aircraft-146\SimObjects\Airplanes\JF_146_100\panel
@martyn managed to record what has been happening with me the last couple flights. Apologies if it is hard to see, don't usually record things.
First video when on ascent out of the airport the plane refuses to hold 2000 fpm, and instead kept pitching up despite me trying to set it multiple times. This was recorded after I first attempted to correct it. I tried setting VS both by manually clicking it on the FCU and on my Bravo hardware (tried toggling between IAS and VS as well on the hardware).
https://www.youtube.com/watch?v=FzFmPo2RmUMIn this clip I was attempting to slow the plane down, any attempt at using the speed brakes just resulted in the plane pitching downwards to maintain the ~250 knots IAS.
https://www.youtube.com/watch?v=R4yeW3OkFE8The only thing different in my settings between 1.2 and 1.3/4 is that I rebound SYNC from Afterburner to ELT. I have noticed that the button light for IAS is lit on my Bravo, and not on the FCU when loading in to the plane. I don't think it was doing that prior to 1.3. It kind of feels like IAS is forcing itself on in the background, perhaps. Which wasn't an issue in 1.1/2.
Unless I am doing something fundamentally wrong that wasn't causing an issue previously that I am just missing?
Shall DL that gauge to try too, since I did have the above mentioned altitude bug as well.
-
So far I haven't encountered the exact problems as described in this thread with the WASM you supplied, but unfortunately I'm encountering the early level off first encountered in 0.1.2 again. Just took off, selected an altitude of 9000ft, ALT ARM => No altitude horn this time, white ALT annunciator turned on.
Set IAS, used Sync (using the ELT binding if that has any impact) to set the desired airspeed. At about 8000ft the horn sounded, as intended, but at 8600ft the green ALT annunciator came on, the green IAS annunciator turned off, and the plane levelled off at about 8500ft, even descending a little to get back to that altitude. -
Downloaded the 0.1.4 update and applied the WASM patch and it’s much better. Still seems to arm the ALT mode too soon in ascent though, meaning I had to adjust up a couple of hundred feet, but all the weird descent issues I was having seem to be fixed (only one flight though), and altitude capture seemed to work fine in descent. Will try a couple of additional flights in coming days
-
@martyn managed to record what has been happening with me the last couple flights. Apologies if it is hard to see, don't usually record things.
First video when on ascent out of the airport the plane refuses to hold 2000 fpm, and instead kept pitching up despite me trying to set it multiple times. This was recorded after I first attempted to correct it. I tried setting VS both by manually clicking it on the FCU and on my Bravo hardware (tried toggling between IAS and VS as well on the hardware).
https://www.youtube.com/watch?v=FzFmPo2RmUMIn this clip I was attempting to slow the plane down, any attempt at using the speed brakes just resulted in the plane pitching downwards to maintain the ~250 knots IAS.
https://www.youtube.com/watch?v=R4yeW3OkFE8The only thing different in my settings between 1.2 and 1.3/4 is that I rebound SYNC from Afterburner to ELT. I have noticed that the button light for IAS is lit on my Bravo, and not on the FCU when loading in to the plane. I don't think it was doing that prior to 1.3. It kind of feels like IAS is forcing itself on in the background, perhaps. Which wasn't an issue in 1.1/2.
Unless I am doing something fundamentally wrong that wasn't causing an issue previously that I am just missing?
Shall DL that gauge to try too, since I did have the above mentioned altitude bug as well.
@melon said in v0.1.3 AP Problems:
I was attempting to slow the plane down, any attempt at using the speed brakes just resulted in the plane pitching downwards to maintain the ~250 knots IAS
That is exactly what it will happen and is intended. You have selected the vertical mode of IAS thus telling the autopilot that you want to maintain the speed when you pressed the button.
By deploying the airbrake and inducing drag, the autopilot is unquestioningly obedient and will do its very best to maintain the speed you commanded earlier - and it can only do that by lowering the nose.
What you get is no reduction in airspeed but an increased rate of descent.
There are situations (all too common) where you need to go down and slow down and it's a fine art in manipulating the automatics to achieve this. In the 146, descent in icing conditions with anti-ice on, particularly in the terminal environment, was, shall we say, a challenge at times.
If you want to slow down, set the aircraft off at a modest rate of descent circa 1000fpm and the VS mode will maintain that - you can then deploy the airbrake to slow down (rapidly) or bring the thrust back. -
@melon said in v0.1.3 AP Problems:
I was attempting to slow the plane down, any attempt at using the speed brakes just resulted in the plane pitching downwards to maintain the ~250 knots IAS
That is exactly what it will happen and is intended. You have selected the vertical mode of IAS thus telling the autopilot that you want to maintain the speed when you pressed the button.
By deploying the airbrake and inducing drag, the autopilot is unquestioningly obedient and will do its very best to maintain the speed you commanded earlier - and it can only do that by lowering the nose.
What you get is no reduction in airspeed but an increased rate of descent.
There are situations (all too common) where you need to go down and slow down and it's a fine art in manipulating the automatics to achieve this. In the 146, descent in icing conditions with anti-ice on, particularly in the terminal environment, was, shall we say, a challenge at times.
If you want to slow down, set the aircraft off at a modest rate of descent circa 1000fpm and the VS mode will maintain that - you can then deploy the airbrake to slow down (rapidly) or bring the thrust back.@toozin Please watch the video. I know what it should do, but it was not doing that because if you watch the video you'll see that I was in VS mode not IAS. I was using IAS as the term not as the mode in the sentence you quoted. To reiterate, I was in VS mode yet it was acting like it was in IAS mode when it was not.
I previously had been using VS to maintain 2000fpm while slowing from like 280 to 250 or whatever. That is not working now.
-
@toozin Please watch the video. I know what it should do, but it was not doing that because if you watch the video you'll see that I was in VS mode not IAS. I was using IAS as the term not as the mode in the sentence you quoted. To reiterate, I was in VS mode yet it was acting like it was in IAS mode when it was not.
I previously had been using VS to maintain 2000fpm while slowing from like 280 to 250 or whatever. That is not working now.
@Martyn Wanting to check something after poking around Ver 1.4 I loaded up Ver 1.2 and a few circuits up to 10000 feet. I was able to get my issue to happen there as well, but it happened far less frequently, where as in 1.4 it was happening to me constantly. I noticed that when switching between IAS and VS mode the Bravo would sometimes not change modes, or the change would be quite delayed (a good 5 seconds or so). I had to activate VS mode twice to get it to switch off IAS to VS, as displayed on the Bravo (the in game FCU was displaying as you'd expect it too, except when pressing the Bravo's IAS button). I was able to get this behaviour to occur when pressing either the in game buttons or the physical buttons on the Bravo. As a side issue the IAS button on the FCU wouldn't light up when pressing it on the Bravo, despite the mode definitely being on.
-
@toozin Please watch the video. I know what it should do, but it was not doing that because if you watch the video you'll see that I was in VS mode not IAS. I was using IAS as the term not as the mode in the sentence you quoted. To reiterate, I was in VS mode yet it was acting like it was in IAS mode when it was not.
I previously had been using VS to maintain 2000fpm while slowing from like 280 to 250 or whatever. That is not working now.
@melon said in v0.1.3 AP Problems:
I previously had been using VS to maintain 2000fpm while slowing from like 280 to 250 or whatever
In my expereince (3500 hrs 146/RJ) a VS of 2000fpm was at the very maximum limit to achieve a speed decrease without deploying 'the handle of shame'. Try 1500 fpm and things become far more manageable.
-
@Martyn Wanting to check something after poking around Ver 1.4 I loaded up Ver 1.2 and a few circuits up to 10000 feet. I was able to get my issue to happen there as well, but it happened far less frequently, where as in 1.4 it was happening to me constantly. I noticed that when switching between IAS and VS mode the Bravo would sometimes not change modes, or the change would be quite delayed (a good 5 seconds or so). I had to activate VS mode twice to get it to switch off IAS to VS, as displayed on the Bravo (the in game FCU was displaying as you'd expect it too, except when pressing the Bravo's IAS button). I was able to get this behaviour to occur when pressing either the in game buttons or the physical buttons on the Bravo. As a side issue the IAS button on the FCU wouldn't light up when pressing it on the Bravo, despite the mode definitely being on.
-
Can you all try using this WASM gauge? Download here
The file needs to be moved into this location, overwriting the existing file: \Packages\Community\justflight-aircraft-146\SimObjects\Airplanes\JF_146_100\panel
@martyn said in v0.1.3 AP Problems:
Can you all try using this WASM gauge? Download here
The file needs to be moved into this location, overwriting the existing file: \Packages\Community\justflight-aircraft-146\SimObjects\Airplanes\JF_146_100\panel
Martyn, is this gauge only for the -100 series aircraft? Is there a replacement for the other variants?
-
@martyn said in v0.1.3 AP Problems:
Can you all try using this WASM gauge? Download here
The file needs to be moved into this location, overwriting the existing file: \Packages\Community\justflight-aircraft-146\SimObjects\Airplanes\JF_146_100\panel
Martyn, is this gauge only for the -100 series aircraft? Is there a replacement for the other variants?
-
@jmarkows The same gauge is used by all the variants but the file is located only in the -100 panel folder
-
@martyn Using the replacement gauge, did few flights using just the FCU, the Bravo and/or a combination of the two. It appears to be working for the most part, was able to descend/ascend in VS or IAS and switch between the two with nothing crazy happening.
But there is something odd with using the Bravo's IAS mode. It doesn't seem to want to hold the speed properly some times, one time it just gradually kept pitching up until it lost near all speed, the next it worked fine. It also doesn't change the indicators from VS to IAS on the FCU using the button on the Bravo, and can't switch to IAS without VS being on first. Its bound to Toggle Autopilot Flight Level Change.As an aside, when you use the SYNC mode, to set like a vertical speed, will the plane pull itself towards the original vertical speed before settling back down to the new speed? It's something I've noticed during climb mostly, when pushing the nose down to build some speed before climbing again.
Sorry if this is rambling a bit, wrote it at like 2:30am,
Edit: Okay I think I worked out what was happening, on my keyboard IAS mode was set to Alt, and only Alt... I have no idea how that happened.
