Glaudrung

Thanks Pete, for everybody intrested in this interimversion of fsuipc, mail me at glaudrung@skynet.be I wil send it as soon as possible (because now I want to FLY first) Luc

Pete, I have just tried the new interim version you sent me of your fsuipc and it's working like a charm. I tried, while I was at it, if it still worked while connected to AS2004. And that worked also. So I am a happy pilot again. Thanks again. I will post the solution to the PSS forum too. Would you mind it if I mailed this interim version to those pilots that have the same problem? Just until a new official version becomes available. my sincere regards Luc

Pete, Your last tip/question was right on the mark. When I unticked the option to suppress interference, the airbus flew like a dream again. Don't ask me why or what I think could be the reason but I am glad we got around this problem. I would like to express my gratitude to you and the other posters here for all the effort and time that was put into this 'rather' simple problem. my best regards Luc

Pete, quote What of the option on the main (front page) screen of PFC options -- does the "suppress interference" on or off change anything? the suppress interference is always on with me brcause the default throttle has to be connected for the flightyoke to work correctly. I'm going to try a flight after dinner a let you know my findings. Luc

Bob, Glad to hear from you. First a question. About which bus are you talking? The later series of A330/340 or the very first one with the A319/320/320. I have both and the A330 flies like a charm with whatever version of fsuipc. The small busses however are something else. They act normally when I use the fsuipc version 3.20 (installed together with the bus) but when I upgrade to version 3.3 or above, I get a very decent impression of a (very) heavy divebomber. Something to use by some 9/11 terrorist I guess but not something to transport passengers. But I will try your suggestion. I have tried so many possible solutions in the last 48 hours I lost count but one more or less won't hurt either. Luc

Pete, engaging the AT is a two-step proces. First thing you do is arming the AT. This you do by programming the fmc. The next step is indeed advancing the throttle levers through their pre-set detentes. With other words, you don't move the levers on the throttle quadrant but you press the 'Keypad +' key to advance the levers. First press moves them to CL-mode, second one to Flex-THr and the third press brings them to the TOGA-mode and this activates the AT. When handflying the bus, you can use a button to activate the AT but even then, you have to set throttle levers by using the 'keypad +' and the 'keypad -' keys The actual throttllevers are in my case only used to taxi the bus to the runway. After that, they are indeed parked at the bottom and are never used again until after touchdown and rollout. Then they are used again to taxi to the gate. Luc 'Glaudrung' Brusselmans

Well, When I tried the checkbox to disable trimming-inputs, I have tried both checked & unchecked but both settings give me the same result. AT is enabled by the the throttle itself. When the fmc has been programmed, the V-speeds are stored in the AT and when you put the throttle-control (not with the usual F1-F4) with the Kpd+ AT is automatically selected. Autopilot itself (VNAV & LNAV) are selected with a mouseclick. I know for sure that PSS disables all joystick inputs by default when activating the AP and I assume that it's the gameport-inputs they are shutting down. PFC-driver works through the serialport however and maybe that is the reason why the checkbox doesn't respond as it should. It's looking for gameport instructions and is, as such, not responding on the instructions that pass through by the serial port. just my two cents worth of technical insight. (not a lot as far as I know) thanks anyway for your time and effort you're putting into this. Luc "Glaudrung" Brusselmans

Thanks Pete, (Do you sleep next to this forum...?) Well, we know now that it has something to do with the difference between fsuipc v3.2 and its connection with the pfc-driver and the fsuipc v3.2+ and that connection with the pfs-driver. I have changed back to an older version of the pfcdriver but that also doesn't solve the problem. Using the checkbox in the latest version of fsuipc, as you indeed mentionned earlier on, doesn't do the trick either. But I guess you are not very far from the truth peter because when I postpone the activation of the autopilot until I reach a 'safe' altitude, I can get the bus back under control by trimming. I think we can thus safely assume that it is now to the people of pss to take things further. I will contact them. Thanks for the assistance Pete Luc ' Glaudrung' Brusselmans

Chris, Was I glad to read your post. Seems that my problem is not mine alone. And, just to let you know, you have given me the clue to the answer (not the solution I'm afraid. When you wrote that you are using PFC components, I got an idea. I deleted my pfc driver and, believe it or not my A320 was airworthy again. So that makes sense in the way that PSS disables all flightyokes and their input BUT... if you're using the throttle quadrant... that is connected serial isn't it...? Would that be disconnected too? And it makes also sense that only a few are experiencing this. You have to use pfc-components AND the A320 AND AS2004 (for use with latest versions at least you have to install fsuipv 3.3 or higher). Now for Pete... What is the connection between the pfc-driver and fsuipc? And how does it interfere with the PSS airbus? I know, I know Always more questions I'm afraid. Luc "Glaudrung" Brusselmans

Well Pete, I am not that technical so I sure don't know what is or isn't 'odd' in the logfile. The problem was posted at the pss forum but it seems that I am the only one with it. The funny thing is that, altough the small busses (319-320-321) are affected, the large ones (330,340) are not. I can switch between fsuipc versions at will, the large planes keep on working while the small ones only work properly when using the 3.22 (or lower) version. And you are correct, I would have thought it was a problem that I was not alone with. However, nobody seems to have it. I will keep looking and keep you informed Pete. Maybe, just maybe, we can come up with the right solution Luc 'Glaudrung' Brusselmans Belgium

Hello Pete, I'm using Windows XP prof. (fully updated including SP 2). After reading your post, I've tried adding those lines in the ini-file but with no succes. The strange thing is that it all has started with AS2004 and the 'customised versions of fsuipc. The last 'working' version was 3.22. After that, the busses became uncontrolable using the AP. I have tried several flights, with version 3.22 and with later versions, but always with the same result. With version 3.22 I could use the AP without problems With later versions, engaging AP caused the plane to dive to mother earth. always the same weather, the same weight, balance and fuel, the same flightplan with the same V-speeds in the FMC. I have tried changing the versions and removed the ini-file everytime to ensure a clean break for every version I sure hope you can come up with a few ideas. Thanks Luc 'Glaudrung' Brusselmans

Pete, I've got something weird on my hands and I hope you can give me some hint of a solution. What happens here is that the busses from PSS start diving towards earth as soon as I activate the autopilot. This happes with all versions of fsuipc higher that 3.20. (3.30 and the 'custom' versions for as2004). When I replace a version with the 3.20, the problem goes away. When I put the original one back (let's say 3.317 or 3.3) the whole thing starts again. Activating autopilot and hups, a oneway ticket to the solid ground... Do you have any ideas what could be causing this...? All suggestions are welcome Luc 'Glaudrung' Brusselmans Belgium