Sign in to follow this  
Guest Arne

Some more nose-diving issues with A319-320-321 & FSUIPC

Recommended Posts

Hello all,After using the PSS A320 for years now without any problem, suddenly the 'nose-diving-problem-on-autopilot-connect' appeared.Since my last flight, I installed the Feelthere 737PIC and Activesky 6.None of the suggestions on any of the forums appeared to resolve the problem.However, I noticed that (probably some of the above software packages) had updated FSUIPC to version 3.5. Re-installment of the previous version 3.4 made the Airbus behave normally again.So does anyone know whether these problems could be due to the version of FSUIPC, or that there is still a critical setting in the later version that I might have left checked/unchecked?Happy flying,Arne

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

I have to say that 3.536 seems to introduce odd problems for me that I hadn't noticed with 3.4 but I've not got anything conclusive to back that up. Just a few curiojs things have happened. But make sure in the Miscellaneous page (the technical page on previous versions) that the "Discon elev trim axis for a/p" is NOT checked/ticked.Rob Elliott, EGPE InvernessPSS Airbus Support andAirbus Fleet Training Captain, British Airways Virtual airbus@speedbirdonline.co.ukhttp://www.speedbirdonline.co.uk/airbus.htmlhttp://www.bavirtual.co.uk

Share this post


Link to post
Share on other sites

Rob,just found your answer after I experienced the same problems yesterday. The "discon elev trim axis" entry in FSUIPC really might be the solution, because for the Feelthere 737 PIC you have to check/tick this option. Will have a try this evening and post the results...Alex

Share this post


Link to post
Share on other sites

Rob, guys,I am having a quick test right now and must say, it seems you are right: Unchecking the "discon elev trim axis" option makes everything working nice again - thank you for the hint...Alex

Share this post


Link to post
Share on other sites

I've experienced the same problem, albeit a little worse. At times, the MCP speed intervention doesn't work nor does manual heading select. I have also downloaded the software three times; I'm going to see if I can locate the FSUIPC version prior to the last release and see if that makes a differences as well as loading up the Cessna (default), then changing to the PSS aircraft.Will report what I learn...also if anyone can direct me to where I can find the FSUIPC release prior to the last one, I'd appreciate it.Many thanks,baw7162404.png

Share this post


Link to post
Share on other sites

>But make sure in the Miscellaneous page (the>technical page on previous versions) that the "Discon elev>trim axis for a/p" is NOT checked/ticked.Sorry for the silly question, but how do I go about getting a registration key for FSUIPC? I don't see the options you listed, so I assume I need a registered version?Thanks :).

Share this post


Link to post
Share on other sites

DigitalDAve, you can get the full registered version of FSUIPC at http://secure.simmarket.com/product_info.php?products_id=538BAW716, please email me at the address below and I'll send you the previous version of FSUIPC.Rob Elliott, EGPE InvernessPSS Airbus Support andAirbus Fleet Training Captain, British Airways Virtual airbus@speedbirdonline.co.ukhttp://www.speedbirdonline.co.uk/airbus.htmlhttp://www.bavirtual.co.uk

Share this post


Link to post
Share on other sites

Rob,Thanks for the link. I've been doing some checking around, and found a thread that implied that if I had the unregistered version, I should be OK, as the issue with the checked/unchecked tickbox isn't an issue on the unregistered version, only the registered one... Any idea if this is true? Sorry, I didn't make a note of the thread :(.

Share this post


Link to post
Share on other sites

Hi all,I have tested the A320 with three versions of FSUIPC: the current 3.5 version, the beta 3.538, and the FSUIPC that comes with the download 3.401 (I think). In any case, in each case, when the autopilot is engaged, the nose dives dramatically and if you engage the a/p anywhere close to the ground (less than 3000 feet), chances are high that you will have uncommanded contact with terrain. In addition, there is a problem with the autothrottle; it continues to accelerate even if you execute speed intervention through the MCP.After testing these versions, I am reasonably comfortable in concluding that FSUIPC is NOT the problem. What I have yet to do is merge the PSS panel with an iFDG aircraft to see if the problem is in the .air file or in the panel file. That is next.BTW, a similar problem exists with the A330/A340 download.To Norman and PSS: Has someone changed your download, or heaven forbid, have you been hacked into and someone sabotaged your download program? You may want to check, because I find it really odd that the aircraft performed flawlessly until recently and now, the thing will not fly on a/p. It also makes me wonder about the 777; why some people report certain faults and others report different ones. Also, I am now having problems with my 777 that I did not encounter before; basically the FMS is now useless, where before, only certain aspects were bad (and previously reported).Something to consider...and offered in the framework of "there may be something rotten in your server".Dave baw7162404.png

Share this post


Link to post
Share on other sites

As discussed above, I did a merge test with the iFDG aircraft (for which there is a published merge for the two products...although it comes from the iFDG side). The same exact nose dive existed when engaging the autopilot. I don't know what else to do except pull FS9 completely off my computer, reload it and see, once downloaded, if that fixes the problem. I have not ruled out something possibly downloaded somewhere else that has corrupted a .dll file which may cause the exact fault.To Norman and PSS: Any thoughts on this subject, or any other suggestions for testing that we can do to isolate the problem? I find it very hard to believe that something that has been working fine before (in FS9.1) would suddenly go haywire after a fresh download. Will advise upon completion of the reload of FS9 and the aircraft.baw7162404.png

Share this post


Link to post
Share on other sites

>Hi all,>To Norman and PSS: Has someone changed your download, or>heaven forbid, have you been hacked into and someone sabotaged>your download program? Dave,I've had a draft to your very long email for a few days but to clarify, the files on the servers remain identical. I hope to finish the email to you later when I get home.

Share this post


Link to post
Share on other sites

>Hello all,>>>After using the PSS A320 for years now without any problem,>suddenly the 'nose-diving-problem-on-autopilot-connect'>appeared.>>Since my last flight, I installed the Feelthere 737PIC and>Activesky 6.>>None of the suggestions on any of the forums appeared to>resolve the problem.>>However, I noticed that (probably some of the above software>packages) had updated FSUIPC to version 3.5. Re-installment of>the previous version 3.4 made the Airbus behave normally>again.>>>So does anyone know whether these problems could be due to the>version of FSUIPC, or that there is still a critical setting>in the later version that I might have left>checked/unchecked?>>>Happy flying,>>Arne>Arne, Ive had the same problems, before but now I got my a319 320 321 to all work fine. First make sure your fs9 joystick settings are set to defaults, second before takeoff trim elevator to -1.8UP, and third always start flight from default flt w/cessna 172 at KSEA. Hope that helps.

Share this post


Link to post
Share on other sites

You don't have to be at KSEA (I always start at Malaga LEMG) and you don't have to start the FS session with the default Cessna, the default Boeing 737 is just as good for this purpose - make sure avionics are ON whichever one you choose. Apart from that I agree with your recommendations.Rob Elliott, EGPE InvernessPSS Airbus Support andAirbus Fleet Training Captain, British Airways Virtual airbus@speedbirdonline.co.ukhttp://www.speedbirdonline.co.uk/airbus.htmlhttp://www.bavirtual.co.uk

Share this post


Link to post
Share on other sites

As I stated earlier, I planned to off load FS9 completely, run spyware check, registry cleaner, then defrag...after that reload FS9 then the AirbusPro. This has been accomplished.After reloading FS9 with the 3.401 version of FSUIPC that came with the Airbus, and following the instructions noted my esteemed colleague at BAV Rob Elliott, I was successful in operating the Airbus A320, programmed FLEX takeoff, autopilot normal operation and full autoland. Therefore, the problem with the Airbus Pro is NOT with PSS or any of its downloads for the base product. The thing is rock solid. Before going to the draconian steps I have taken to solve the problem, I would suggest following my next few posts, as I will be reloading programs and continuing to test as I go to see if I can isolate the particular program that caused the Airbus to go haywire in the first place.As an aside, I will also reload the 777 before doing this, to see if this also resolves some of the 777 problems as well, or if the loading of this program affected the Airbus. I will report when completed, probably later today.Kind regards,Dave LambCaptain A320/B767 (baw716)British Airways Virtual

Share this post


Link to post
Share on other sites

I believe I found the problem...I downloaded the 777 and flew it on a loop around KSEA; takeoff 34R, climb to 5000, ANVIL, WNSLO, FOURT, MILLT, then setup for ILS34L. The FMS accepted the input, although I could not close the discon at FOURT. Checked the manual...just would not accept it. I flew it anyway.The same FMS problems occured; wrong updated times, but it actually flew the route quite nicely, up to 5000, engaged at 1000 feet, LNAV, a/p at 3000 feet, VNAV and everything went pretty well. It made very wide turns and overshot WNSLO, which from ANVIL at 250kts is an easy turn...it should not have done that. At FOURT, I went to HDG sel, then flew it back toward the ILS. It captured the LOC, but not the APPR. However, a funny thing happened: I could not disengage the autopilot. I tried every which way from Sunday; it would not disengage. The aircraft began to sink with elevator trim; I had no manual control at all. The aircraft actually crashed; but not by much...When I reloaded the A320, loaded up the same route, everything was fine until I turned to final and slowed down. The engines suddenly quit. At 3000 feet at 160 kts, with no APU started, it was impossible to recover and I crashed.I believe the problem lies in the download of the 777. One of the gauge files on the 777 may be corrupting the other PSS aircraft. Unfortunately, the only way to know this is to uninstall the aircraft and see if this theory is correct. If I can get the gauge files out, then get the A320 to fly again properly, then we will know for sure.Stay tuned...Dave Lamb(baw716)

Share this post


Link to post
Share on other sites

OK...test number three:I offloaded the 777, setup the A320 and flew it on the same loop. This time, no autopilot failures; however, there was a problem with the VNAV setup. I had inserted 250 for climb, 250 for cruise and 190 for descent (from 5000 feet cruise alt). The a/t did not pick up these changes and accelerated to 298kts (standard setting).I need to do one more complete round of tests; e.g. reload the 777, refly the 777 and the A320 and see if I can repeat the error. If this happens, then we can define this as more fact than theory (which at this state it still is: a theory which fits the facts). What I don't know is if there is a file in the download that affects the A320 autopilot. I need to rule this out before fully concluding that the 777 download is the culprit.I will report later tonight or tomorrow the results of my testing as well as communicate with PSS to get their thoughts on this. For now, please don't take any action based on my comments until I have confirmed the issue and can provide a suggestion regarding the solution.ThanksDave Lambbaw716

Share this post


Link to post
Share on other sites

On the speed, were you in managed speed? If so you need to make sure that the speed constraint 250/FL100 is set up in the MCDU or it will go to 298 as you found. So click on the LSK to the right of a fix/waypoint below FL100 to take you into the Vert REv page and enter that constraint at LSK2L CLB SPD LIM.Rob Elliott, EGPE InvernessPSS Airbus Support andAirbus Fleet Training Captain, British Airways Virtual airbus@speedbirdonline.co.ukhttp://www.speedbirdonline.co.uk/airbus.htmlhttp://www.bavirtual.co.uk

Share this post


Link to post
Share on other sites

Rob,I had set up the MCDU for 250 climb, 250 crz, 250 descent and 250/10000 speed restriction. I didn't set it up on the legs page, since the flight altitude was set in the INIT page. Its my understanding that if the crz alt is set up in the INIT page, and the climb/crz/des speeds are set up with the proper constraints, it isn't necessary to set up the speed on the legs page (unless, of course, there is a crossing altitude restriction).In any case, I have isolated the problem for the A320 series aircraft and have a fix that does work (at least on my machine).1) This fix works only for cases in which the new 777 has been downloaded and installed on FS.2) It is my belief that there a file that is in the download for the 777 affects the autopilots of other PSS aircraft. This is validated in my tests both with the A320 and A330/A340 aircraft in which FS was offloaded, the Airbuses reinstalled, flown without problems. Then the 777 was loaded and neither aircraft's autopilot/autothrottle worked properly.Therefore, for this fix to work, it is important to do the following:a) offload FS, run a registry cleaner and defrag your machine before you reload FS.:( reload FS, followed by the PSS AirbusPro, followed by the Airbus A330/A340.c) do not load the 777. If you do, it will corrupt the autopilots of the Airbuses.For those of you who have problems with the Airbuses and have the 777, go ahead and attempt this fix; however, save all your executables for your addon files, since you will need to reload them one by one after you have removed FS and restored the Airbuses.I would also recommend testing the Airbuses before you load any other software to assure they are working correctly.To PSS: Question: In the 777 download, are there gauge files that are common to all PSS aircraft that are modified when the 777 is installed to FS? If there are, I would suggest having a look at those files to see what changes occur to other PSS aircraft. After almost 24 hours of testing, I have been able to determine that a) after removing FS and reinstalling it, the current FSUIPC and the Airbus, the Airbus worked flawlessly. :( I then installed the 777; immediately afterward, there were serious problems with the stability of the autopilot (nose diving) and no speed intervention control. c) When the 777 was removed, the problem was not eliminated. Only by uninstalling the 777, then uninstalling and reinstaling FS and FSUIPC did the Airbuses fly correctly. Therefore, by process of elimination, the cause of the Airbus flight problem seems to lie in the download of the 777. It is important to note that I have not proved to an absolute certainty that the 777 is the cause of the Airbus problems. With that said, the degree of testing that I have done and documented certainly leaves me with the conclusion, after all else has been eliminated, that it is more likely than not that a bug in the 777 install exists that affects the other aircraft.I now currently have all the PSS Airbuses loaded on to my FS and they work excellent; no anomolies at all, with the current version of FSUIPC up and running (v3.53). I have elected to not reload the 777 files until it is possible to isolate the problem. It is hopeful that the patch that is developed for that aircraft will solve the problems of the 777; however, some attention should be paid to the files which are modified that affect the other PSS aircraft when the 777 is installed to FS..and if those files are modified as a result of the patch, then that would be great news. IMPORTANT NOTE: To other pilots who have problems with the A320 autoflight system: Do you have the 777 also installed on your computer? If you do not, please report this immediately, as this would then possibly lead us away from the conclusion drawn above. It is important here that we be fair to PSS.In the interim, I will continue to load my other add-ons and keep testing the Airbuses to make certain they are still flying correctly, so that other programs can be eliminated (or included) as possible causes for the autoflight failures. If I have anything new to report, I will do so.Thanks to Rob Elliott, as always, for your diligent work and continued support.My machine:AMD2.2ghz (64mb), nvidia motherboard (GeForce), 3gb DDR 3200 RAM (dual channel), HD1: 250gb-90%free space HD2: 150gb-92% free space. Graphics: 256mb nvidia FX5200. On LAN with three other computers (two wireless)..this machine hardwired into router; high speed broadband internet connection.Kind regards,Dave Lamb2404.png

Share this post


Link to post
Share on other sites

Dave, this is interesting. I have never installed the PSS777 and haven't had the sort of problems you have described. Maybe you have hit on the cause of some things going wrong. Being a mere Airbus support drone in the basement of PSS Towers we have reached limit of what I can tell you here. Sadly the executives on the top floor don't give me access to the guts of the gauge files or any knowledge of what regression testing was carried out on any 777/Airbus shared gauge files. Norman will have to step in here.Rob Elliott, EGPE InvernessPSS Airbus Support andAirbus Fleet Training Captain, British Airways Virtual airbus@speedbirdonline.co.ukhttp://www.speedbirdonline.co.uk/airbus.htmlhttp://www.bavirtual.co.uk

Share this post


Link to post
Share on other sites

Rob,I'd appreciate anything you can do to push this ahead. If there are gauge files common to the Airbus and the 777 (which I believe there are based on the testing), it is possible that the reverse problem is happening: If a PSS Airbus is loaded on the same computer as the 777, the problems with the 777 are made worse. Please pass this onto Norman; I'd be happy to walk him through what I did to fix the A320; if they can isolate the common gauge files, it might be part of the 777 problem and a key component to a fix for that aircraft as well.Many thanks again for your kind assistance, Kind regards,Dave Lamb (BAW716)Captain A320/B767British Airways Virtual

Share this post


Link to post
Share on other sites

Tried my Airbus for the first time since the 777 came out and

Share this post


Link to post
Share on other sites

we should have a updated patch of the a320 and its panel! but wait! the b777 patch hasnt come out yet. i guess there no hope for the a320 a330 and a340. PSS developers! give us the patch! be fair with us! pls! we paid for it! make a patch or new version!!!

Share this post


Link to post
Share on other sites

If you do a search you will see that we have said many times that there will not be an update or a patch for the A320 family. We have to hope that a brand new Airbus is released but I have no indication yet of what is planned for future releases after the 757.We are very fair with everyone who posts problems on these forums. And never forget that you might have one problem but someone else doesn't (I have had very few of the problems posted on this forum for example. Just lucky I guess). What I have learnt over the years is that even if we issued a patch it might only help some people and not others and might not solve your particular problem. With the range of individual PC setups, other aircraft loaded on your PC - these can cause conflicts, the way you load flights and the complexity and lack of open code of FS itself we can never gurantee that what works for one will always work the same way for someone else.Rob Elliott, EGPE InvernessPSS Airbus Support andAirbus Fleet Training Captain, British Airways Virtual airbus@speedbirdonline.co.ukhttp://www.speedbirdonline.co.uk/airbus.htmlhttp://www.bavirtual.co.uk

Share this post


Link to post
Share on other sites

Following my previous post, I have installed the 777 in 8 separate stages - copying the files from a separate storage folder from the original download. At each stage, I re-checked the Airbus A320 series AP performance on take off.At each stage, the Airbus performed as advertised and I now have a fully operational PSS Airbus and PSS 777 on this particular installation - I have just flown EGLL-EGNX in the 777 using a full FMC route into auto-ILS and autoland with no issues other than those we know about. After that I loaded an Airbus A319, took off and engaged the AP with no problem!Also, the 777 file structure is simpler than I thought - the odd file I found in the FS9.cfg folder is nothing to do with PSS.Now need to look at my main installation which has many other add-ons to see what else might be causing the Airbus problem! For others who have this problem - how about a list of add-ons to compare with each other - might be a quick way to identify the culprit.John Rooum

Share this post


Link to post
Share on other sites

Now carefully checked my main installation - including manually deleting and re-installing all Airbus files - and the systems now work as advertised. I can force a pitch down after take off - but only by using the AP on a manual take off without resetting the FD. Otherwise it now seems to work perfectly in all normal modes - both A320 and A330/340!Perhaps there is some add-on or an installation tool itself common to those of us seeing this issue which corrupts the Airbus gau file.

Share this post


Link to post
Share on other sites
Sign in to follow this