A320 FMGS B36

Stefan,

Without more info, I cannot do anything. I did not write the interface with Skalarki hardware, and it's hard for me to tell where the error is because it is very likely inside that module.
At least try to get a log somewhere (hardware connect for instance), and note if a particular action is causing the crash. Also what is disconnected exactly? Is it completely frozen or not?

JL

Quote:

---

Originally Posted by filippoporcari

when the apu is running it feeds its own generator....so the electrical systems of the aircraft are normally operated...
am not sure if apu has its own battery or uses the aircraft batteries...anyway they're used ONLY for apu start...after that apu gen starts working.
your problem was probably something different and not related to apu
regards
fil

---

Hi Fil, I found this thread on pprune -- http://www.pprune.org/engineers-tech...-a320-apu.html
<<will the APU take over the supply of electricity to the aircraft from the GPU? >>
No, external power button will be blue on with the GPU supplying. Once APU is available you will need to press the external power button to txfr over to the APU genny.

I would note I am a pilot not an engineer.

--
I did not press the EXTERNAL POWER button to transfer to APU so that might have been my issue. Will test again. Cheers.

on the SD ELEC page u csn easily monitor which generator is on bus.
btw...the APU itself is "self sustaining" and not battery drain while it is running; if u had ext pwr on and u use apu for engine starting the ext pwr should be supposed to be disconnected...but u can also start engines using ext pwr and no apu at all providing u have ext HP air connected.
anyway this should not be the reason of your issue.
cheers
fil

hi jl,
maybe just a busy period and don't want to rush things too much but...pls could u check the strange behaviour of ILSs at LIRF?
as reported: ils 16L....course is showing -002 instead of 161 (navdata pro installed correctly)
ils 34 L....the ils is correctly tuned, received and identified but the two magenta diamonds just don't move and no way to intercept.
thx a lot and sorry to bump this up.
regards
fil

Quote:

---

Originally Posted by jeehell

Stefan,

Without more info, I cannot do anything. I did not write the interface with Skalarki hardware, and it's hard for me to tell where the error is because it is very likely inside that module.
At least try to get a log somewhere (hardware connect for instance), and note if a particular action is causing the crash. Also what is disconnected exactly? Is it completely frozen or not?

JL

---

Hi JL
checked the log and the strange thing is that it was last modified on 1.10.14. When does the log will be modified, or does it has a set path which may be wrong? Best is to do a clean installation, or do you have a better idea? Or shall I rename the log file and check if its creating a new one, don't want to set up all again....

Regards
Stefan

Hello JH

36.1 works very well for me, system stable, no fault can find.
I must still useable on 36.2.uploaden?

Regards Rigo

Hi Rigo,

you can rename the "updater.exe" to "updater.old" in your main FMGS folder, so the update function is disabled.

But JL does not support older versions.

Regards
Stephan

Hi Stefan Thank you

I've installed the B 36.1, and works very well.
I'll rename the updater. the errors are depatiert here I've not.
Until new functions so long, then I will upload again.

Greetings Rigo

Hi,

I powered up my cockpit yesterday and left it for about half an hour, standing at the gate. When I came back hardware connect had crashed.

So I suppose these crashes does not have anything to do with a specific action within the cockpit. At least I have not done anything in these 30 minutes. I am using all Skalarki hardware. I have kept the hardware connect log file, but it does not really say much.

Thanks
Stefan

another way to have the updater on demand and not on every startup is to add to the starter.ini file the line Updater=no and the autoupdater won't be started at every startup but only on user action running the updater itself.
this was explained by jl long time ago.
cheers
fil