Occasionally, on startup, engine gauges only partially turn on or sometimes not at all
-
Good man. It must be a software issue then.
-
I must set right my earlier post about encountering this issue. In an attempt to better define the exact circumstances in which this issue occurs, I discovered that powering up the aircraft by switching on batteries 1 and 2 makes the EGT and N1 indicators light up initially.
When after that either the APU generator or external power comes online, all other indicators on the PED's come alive. I guess this must be normal behaviour. I searched for this in the manual, but couldn't find a confirmation for it.
I didn't have any of the above issues so far.I apologize for any confusion that I may have caused.
-
Same here in v1.2 and powering up loading TURNAROUND state. Resolved only after restarting flight, then loading TURNAROUND state twice.
-
Hi all,
Just to clarify a few points as I suspect there may be some confusion in this thread where the expected aircraft behaviour is being mistaken for a bug.
When loading into the aircraft cold and dark, it is expected behaviour that only the N2 and EGT displays are illuminated on the PED (see attached screenshot). In that state, the aircraft is at the 'Essential Power Level' and electrical power is being supplied only by the aircraft's batteries. In order to preserve the battery's charge, only the most important systems are powered in this state. The rest of the PED displays will power on once the APU or GPU is connected and powering the aircraft.
However, we have been made aware of an issue which is causing only the N1 displays on some engines to appear after switching on the batteries. This isn't intended behaviour and is something we are actively investigating. We suspect this may be battery voltage related, and waiting for an extended period on the ground without the APU or GPU connected is causing the battery to drain, causing this issue.
If you switch on the batteries with only the N1 displays illuminated, we would recommend ensuring that "State Saving" is disabled on the EFB and then restarting the flight. That will ensure the battery voltage is at its maximum value when loading into the next flight and as long as the batteries are powered on within a reasonable time frame (approx 5 minutes) then the PED should display the correct format. A more permanent solution is being worked on for the next update.
Mark - Just Flight
Just Flight Development Assistant
-
Hi all,
Just to clarify a few points as I suspect there may be some confusion in this thread where the expected aircraft behaviour is being mistaken for a bug.
When loading into the aircraft cold and dark, it is expected behaviour that only the N2 and EGT displays are illuminated on the PED (see attached screenshot). In that state, the aircraft is at the 'Essential Power Level' and electrical power is being supplied only by the aircraft's batteries. In order to preserve the battery's charge, only the most important systems are powered in this state. The rest of the PED displays will power on once the APU or GPU is connected and powering the aircraft.
However, we have been made aware of an issue which is causing only the N1 displays on some engines to appear after switching on the batteries. This isn't intended behaviour and is something we are actively investigating. We suspect this may be battery voltage related, and waiting for an extended period on the ground without the APU or GPU connected is causing the battery to drain, causing this issue.
If you switch on the batteries with only the N1 displays illuminated, we would recommend ensuring that "State Saving" is disabled on the EFB and then restarting the flight. That will ensure the battery voltage is at its maximum value when loading into the next flight and as long as the batteries are powered on within a reasonable time frame (approx 5 minutes) then the PED should display the correct format. A more permanent solution is being worked on for the next update.
Mark - Just Flight
@Mark said in Occasionally, on startup, engine gauges only partially turn on or sometimes not at all:
We suspect this may be battery voltage related, and waiting for an extended period on the ground without the APU
I concur with the thought above.
Usually when I get into the aircraft I start the electrical system up (batteries and APU) immediately. This time I got into the aircraft and was distracted for 10-15 minutes before I attempted start up. This was when I experienced only the N1 dials being lit.
-
M Martyn referenced this topic on
-
So I noticed that I get no engine guages when I am preparing for my stream... the aircraft is sat on the apron, in a Cold and Dark state for about 30 minutes... When I start switching stuff on, the guages don't illuminate at all, then I have to restart... happened to me three times (streamed the aircraft 3 times)... off stream when I enter the aircraft immediatley and start switching stuff on, no issues...
-
So I noticed that I get no engine guages when I am preparing for my stream... the aircraft is sat on the apron, in a Cold and Dark state for about 30 minutes... When I start switching stuff on, the guages don't illuminate at all, then I have to restart... happened to me three times (streamed the aircraft 3 times)... off stream when I enter the aircraft immediatley and start switching stuff on, no issues...
@GADGETFPV I think I've seen the same thing. Guessing "cold and dark" is still using up battery. So best to make sure we fire up APU or connect Ground power quickly after starting up a session.
-
mine is different - loading on ramp cold & dark or on runway - ALL instruments turn off within seconds, a partially visible PILOT's microphone sneaks up like a snake, the EFB is gone completely. Can post a video if you like. Creepy but makes this master piece unusable. Was working perfectly fine yesterday and earlier today - I have not changed any settings, updated Navigraph to the latest cycle etc. What is going on?
Edit: here is a short video https://www.youtube.com/watch?v=H_1C2dXGSB0
-
Please don't blame the users for this problem. I have carefully followed the checklist from cold and dark through to engine startup and confirm what everyone is saying here. Hoped V1.2 would fix this but it hasn't. Restarting is not the solution. Please fix this bug. Thank you.
-
Please don't blame the users for this problem. I have carefully followed the checklist from cold and dark through to engine startup and confirm what everyone is saying here. Hoped V1.2 would fix this but it hasn't. Restarting is not the solution. Please fix this bug. Thank you.
@Goochie Users haven't been blamed and we've confirmed above that this is a bug that we are investigating. Until a fix is found, please make sure to establish electrical power ASAP after starting a flight, ideally the APU or EXT AC.
Martyn - Development Manager
-
@Goochie Users haven't been blamed and we've confirmed above that this is a bug that we are investigating. Until a fix is found, please make sure to establish electrical power ASAP after starting a flight, ideally the APU or EXT AC.
-
I was just about to post a reply to this “don’t blame the users”. What an utterly ridiculous notion to suggest that JF are blaming us. They’re absolutely not!
@BPFonteyn Take it easy. If you read the posts you will see that early on the responses from JF were to look at different things we were doing. Fortunately there were plenty of others contributing their experiences, enough to show this was not a user problem. Quite often, the first thought can be the user is doing something wrong. We have got past that point.
