Electrical - When batteries are OFF (or 00.0V) a few objects are still operable

alepouna commented 1 year ago

Aircraft Version

Experimental

Build info

{
    "built": "2023-01-08T23:19:25+00:00",
    "ref": "refs/heads/experimental",
    "sha": "7865832062508907453d0f04b1b2c774158dbcb2",
    "actor": "frankkopp",
    "event_name": "manual",
    "pretty_release_name": "experimental:78658320",
    "version": "v0.10.0-exp.7865832"
}

Describe the bug

If you turn OFF both batteries, APU/GPU then a few objects (explained below each) are still operable.

Preconditions:

Battery switches both OFF or 00 volts (from draining)
APU/GPU off/disconnected.

(In the screenshot I drained the batteries AND have the OFF switches off. I powered the airplane for a little bit to charge the batteries and its still replicable - also replicable after just loading in the sim)

ANN LT on TEST

When putting the panel lights on TEST mode the ADIRS indicator lights up

The batteries also indicators also show up as in TEST mode, and the AVAIL light of GPU but this could be normal behaviour? But without any power maybe not. Dunno!

No Smoking switch activates audio queue

If you interact with the No Smoking switch, you can hear the audio alert (and I want to assume the entire function operates as well) https://user-images.githubusercontent.com/98479040/211363285-ef8010b6-ccf6-4ba1-92af-7780eb584381.mp4 (Might need to turn the audio up, sorry!)

Evac horn plays the sound

https://user-images.githubusercontent.com/98479040/211363792-fc944808-4dda-4219-9746-e4d1a4571186.mp4 (Might need to turn the audio up, sorry!)

Discord Username (optional)

Alepouna🌙#9824

alepouna commented 1 year ago

To add a quick note, it has come to my attention that NAV lights behaviour is normal due to the airplane having a GPU avail. I am doing some other tests currently on the airplane, will confirm shortly by editing both OG post and posting a comment here :)

alepouna commented 1 year ago

Yup, seems to be as such. When GPU isn't AVAIL the NAV lights do not turn on either. Removed from post. Everything else is replicable.

alepouna commented 1 year ago

Also I'd like to add, as someone mentioned on Discord (sorry whoever it was i can't find your message D:) that the backlight on the battery indications, could be off when there is no battery. More information would be very welcome about this as well.

MicahBCode commented 1 year ago

Something to add: Dome light is also working with both battery switches in OFF position and no EXT PWR conntected or APU running. Not sure if thats simulated correctly.

tracernz commented 1 year ago

Something to add: Dome light is also working with both battery switches in OFF position and no EXT PWR conntected or APU running. Not sure if thats simulated correctly.

Can't replicate this on master. Perhaps you are using some kind of bindings rather than the buttons on the overhead?

Captain's dome light is powered from ground service bus, so it is on whenever external power is connected (doesn't need to be on), and FO's dome light is off one of the batt busses, I forget which, but it's the only light you have in emergency config (used to be SOP to have it on during takeoff). This is all correctly implemented.

MicahBCode commented 1 year ago

@tracernz Yeah with "no EXT PWR connected" i meant it is available ("AVAIL" is shown in the overhead) but not switched on. But as you stated this is in that case correctly implemented then.

komp1821 commented 1 year ago

So these two annunciator lights have driven me crazy... Let's start with the Ext Power AVAIL light: There are three scenarios we need to look at:

Scenario a) AC ESS BUS supplied, external power connected or not AC ESS SHED BUS supplies power to the AVAIL light. In addition, AC ESS BUS must be powered as well. There are relays involved.

Scenario b) AC ESS not supplied, external power is NOT connected Obviously the simplest. There is no power supply to the AVAIL light. It must not come on during light test.

Scenario c) AC ESS not supplied, external power is connected In this case the Ground Power Control Unit (GAPCU) is supplied by the External Power; it bypasses the External Power Contactor. The AVAIL light is supplied (and controlled) by the GAPCU directly. In reality the GAPCU has protection circuits that inhibit activation of external power when the delivered power is outside of the specifications (voltage or frequency fluctuations, incorrect phase sequence). In this case the AVAIL light will stay off and it must not come on if you flick the light test switch. If the specifications are met, AVAIL is on. The light must not turn off during light test then. Since I assume we cannot simulate a malfunctioning ground power, the light would always be on in this case.

Now to the ON BAT light for the ADIRUs. They receive their power supply directly from each ADIRU. In the TEST position, they receive power supply from DC BUS 2 additionally. This is not an either-or scenario. It's literally both. ADIRU power supply is a very complex topic and I didn't bother wrapping my head around it right now. This is something to be done during the ADIRU implementation. I suggest we defer this part of the issue (I can create a new one if you wish) until a proper ADIRU simulation exists. It doesn't have any impact on function, it's just not 100% correct for now.

joeherwig commented 1 year ago

Just a remark regarding the annunciators without batteries off. I notived the the Simvars for instance for `FUELSYSTEM PUMP ACTIVE:1 etc. can still be changed even though there is no electricity connected at all.

If i want to rely within my homecockpit for the korry-annunciators on those simvars, they are still at the "on" value, even though all power is off and disconnected and within the VC the annunciators are off.

Probably it makes sense to provide the annunciator lights on LVars to make the values visible in the VC available externally. Based on Simvars (A-Vars) that doesn't work right at the moment.

flybywiresim / aircraft