A32N FBW Apu problem

Hi guys, since yesterday I’ve noticed that APU on stable version is not acting correctly. Starting the airplane from cold and dark, batteries on, GPU on etc, then APU Master ON and APU start till the “APU AVAIL” on ECAM. When I switch off the GPU though, all screens go black, as if the power from APU won’t “kick in”.

Same procedure with dev version, will not show this behaviour and will correctly switch instantly the power from GPU to APU, without loss of instrumentation.

Community folder and liveries already emptied, only FBW folder is in there.

Any thoughts?

Maybe you should check to ensure your APU gen is on also. It is located on the ELEC panel next to Gen 1

Thanks, it is. I’m wondering if I’m having issues because of some conflicts in between different versions. To uninstall I’ve exited FS, uninstalled the FBW installer, deleted the fbw folder from community and restarted to reinstall FBW installer… No luck.
Can you confirm the custom tablet in the stable version has horizontal menu entries, and dev version has it vertical?

I have the latest experimental version installed and can confirm it is working as it should there. What does your ECAM ELEC page show you before you select EXT PWR off? Can you see that external is supplying power, and that the APU GEN values are green but not supplying the bus? If the APU is not showing green values like in the image below, that will indicate an issue.

When you select APU for the Lower ECAM is it even running? Does it show as Available? Once APU gen is available what happens when you put ground power in the off position? One thing that stands out that you’re not mentioning is anything regarding Fuel. Might consider crosschecking the fuel pumps if it’s not starting. Have never seen this issue with any versions I have ever used of the FBW mod.

I’ve found a workaround: turning on and off any of the fuel pumps, just once, will result in a proper switch between external and internal power. Which brings me to another question:

  1. Can you confirm that to start APU, fuel pumps are normally set to off? From the fuel diagram in the ECAM page, it looks like the APU is feeding from the 1/left system, and keeping them off always left me wondering what the APU is feeding from, if fuel pumps are all set to off?

  2. Unrelated question: since I’ve been watching all existing video-tutorials about the starting-up procedure of the A32N from FBW, some of them have the flyPAD menu horizontal, some of them vertical. In my experience it’s always been horizontal (using the stable version) and I see it vertical only in the dev version. Can you guys confirm this?

If the main fuel pumps are off, the APU fuel pump operates as soon as the APU master switch is in the ON position.

1 Like

I have the same issue with the APU.
I tried both versions and I can confirm that the flyPAD menu is horizontal in the stable version and vertical in the dev one.

1 Like

So, one could assume the mod simulates the backup pump or secondary pump? I’ve not noticed a low pressure reading on the APU page with LH supply off.

Hi, yesterday I finally managed to understand what was happening with my fbw installation and resolve all the issues. For a while light switches and the efb had stopped working or acted in a weird way, reinstalling and cleaning community was not helping. Found out in fbw website a cleanup procedure to delete a folder from %appdata%, but there were 2 in this location, one was a leftover from the Fs marketplace installation done a while ago. When that was deleted, I opened the sim and removed once again the marketplace fbw from the content manager, at this point everything was clean, and the community version started working perfectly. I was stuck in some old flight model and many outdated configurations, the plane now flies better than it ever did, I wonder how many other people have this since this cleanup and possibly of having conflicts outside of the community folder was not something I read about before. Hope it helps

2 Likes

Yes FBW even publishes a cleanup .bat file on their discord Server to avoid the issues you described.

1 Like

I’ll try this AND I’ll look for the cleanup .bat file in a few days and hopefully mark this thread as closed. Thanks a lot guys!

Looking for the cleanup bat on their discord but can’t find it anywhere. Can you please tell me in which page it is or share a direct link? Thanks!

At their discord in the #support section and then under files.

It’s a bit difficult to find. Just go their and ask the support staff about your problem and where to find the .bat. They are very very quick and helpful.

Nothing worked.
Used the bat, also manually checked that those folders were removed, restarted, reinstalled the installer on empty community folder… Even deleted manual and rolling cache in the simulator. Still have those weird problems (including the APU bug). Also, to add to the weirdness, I’ve noticed that the APU will start, will hear the sound of if from external camera, BUT it won’t show any exhaust effect as it used to. I guess my only option now is to reinstall the whole simulator…

I just scanned through the thread, and it seems to me most (if not all) of these issues have been fixed in the dev version.

Can you confirm if you have/ ever had a version downloaded from the marketplace? There shouldn’t be any A32NX entries in the content manager (0.6.x)

It would be nice if you could hop onto our Discord server where support is usually pretty quick (leave a message in our #support channel)

Never had it from the marketplace.
The APU bug is indeed absent in the dev version, but I have several other problems with that one, including autobrakes not being disabled by touching the brakes, no “decel” nor other advices on the PFD, no v-speeds recalled by right mouse click on MCDU and so on… I just did another quick flight test with the dev version and surprise surprise, my simbrief username popped up in the fly-pad, without any input from me after the “clean” install.

I’ll write in the support channel on discord then and let you guys know, thanks!

Sounds good! As you might have guessed already, a clean install can sometimes do wonders. Also, having a clean community folder to start with, helps rule out conflicts with other mods/liveries. Feel free to stop by the Discord and one of our Community Support folks will be happy to assist