Hi,
We are trying to set the flight detector to start when RPMs are over 1000 (engine start) and end when RPMs are below 1000 (engine stop) in order to have the exact Flight Time the engine has been running. We have seen that there are 3 modes in Operations Setup Menu (Automatic flight detect, flight detect on digital input and Manual flight detect). Which of these options is correct to our need? I've tried with Automatic and set the Flight detect minimum RPMs to 1000, but we cannot set the minimum ASI to 0, so it detect the flight when both conditions are true (RPMs and ASI).
Is there any option to setup the IEFI to start the flight (flight time counter) when we start the engine?
Thanks in advance.
Automatic Flight Detect
Forum rules
Please keep your posts friendly and on topic. No politics or discussions of a controversial nature not related to our favorite subject of flying and avionics. Offending posts may be removed or moderated.
Please keep your posts friendly and on topic. No politics or discussions of a controversial nature not related to our favorite subject of flying and avionics. Offending posts may be removed or moderated.
Re: Automatic Flight Detect
That's a really good question!
I'm also interesting in this function.
Waiting for the answer
I'm also interesting in this function.
Waiting for the answer
Re: Automatic Flight Detect
You are referring to the engine hobbs - hobbs works that way.
Flight time is different - it really does not have anything to do with the engine as such.
In automatic detect it uses the RPM and ASI as trigger to start a possible flight - both must be above the limit. Once a possible flight is triggered it no longer looks at RPM at all - only ASI. As long as ASI stays above stall for at least one minute the flight recording is now confirmed (if ASI drops out before this the flight recording is canceled and no log entry is done).
The flight remains active until ASI drops below stall for about 30 seconds - then the log is closed. The reason for the somewhat long 30 seconds is to prevent touch and go's from closing the log.
In case of rotor craft automatic flight log is based on rotor speed only.
Note that the hobbs is recorded in the flight folio.
Flight time is different - it really does not have anything to do with the engine as such.
In automatic detect it uses the RPM and ASI as trigger to start a possible flight - both must be above the limit. Once a possible flight is triggered it no longer looks at RPM at all - only ASI. As long as ASI stays above stall for at least one minute the flight recording is now confirmed (if ASI drops out before this the flight recording is canceled and no log entry is done).
The flight remains active until ASI drops below stall for about 30 seconds - then the log is closed. The reason for the somewhat long 30 seconds is to prevent touch and go's from closing the log.
In case of rotor craft automatic flight log is based on rotor speed only.
Note that the hobbs is recorded in the flight folio.
Re: Automatic Flight Detect
You are referring to the engine hobbs - hobbs works that way.
Flight time is different - it really does not have anything to do with the engine as such.
In automatic detect it uses the RPM and ASI as trigger to start a possible flight - both must be above the limit. Once a possible flight is triggered it no longer looks at RPM at all - only ASI. As long as ASI stays above stall for at least one minute the flight recording is now confirmed (if ASI drops out before this the flight recording is canceled and no log entry is done).
The flight remains active until ASI drops below stall for about 30 seconds - then the log is closed. The reason for the somewhat long 30 seconds is to prevent touch and go's from closing the log.
In case of rotor craft automatic flight log is based on rotor speed only.
Note that the hobbs is recorded in the flight folio.
Flight time is different - it really does not have anything to do with the engine as such.
In automatic detect it uses the RPM and ASI as trigger to start a possible flight - both must be above the limit. Once a possible flight is triggered it no longer looks at RPM at all - only ASI. As long as ASI stays above stall for at least one minute the flight recording is now confirmed (if ASI drops out before this the flight recording is canceled and no log entry is done).
The flight remains active until ASI drops below stall for about 30 seconds - then the log is closed. The reason for the somewhat long 30 seconds is to prevent touch and go's from closing the log.
In case of rotor craft automatic flight log is based on rotor speed only.
Note that the hobbs is recorded in the flight folio.
Re: Automatic Flight Detect
Hi Rainer, thanks for your answer.
In that case, is it any option to see the time the engine has been running since the last time it has been started?
I mean, when we finish the flights we are used to see (in the old screen) both, hobbs and the time the engine has been running from the last start, and this value should coincide with the result of the substraction between the last hobbs wrote in the book and the actual hobbs value in the MX1. It's just like a double confirmation, in order to prevent human errors.
Of course, we can do it just substracting these values, but we wanted to know if this could be an option here in MX1.
Thanks again for your time.
BR.
In that case, is it any option to see the time the engine has been running since the last time it has been started?
I mean, when we finish the flights we are used to see (in the old screen) both, hobbs and the time the engine has been running from the last start, and this value should coincide with the result of the substraction between the last hobbs wrote in the book and the actual hobbs value in the MX1. It's just like a double confirmation, in order to prevent human errors.
Of course, we can do it just substracting these values, but we wanted to know if this could be an option here in MX1.
Thanks again for your time.
BR.
Re: Automatic Flight Detect
Hello!! Thanks for your answer. Could you please just explain how is giving us the FT value? Below transponder screen in the upper corner left side I can see UTC, LCL and FT. This value is Flight time? How is calculate it? It should be the automatically calculate between the difference between start Hobbs and finish Hobbs? Or am I wrong? If is not.like that, how is it calculate? Thank you!
Re: Automatic Flight Detect
FT is the flight timer. That is the time between take off and landing and has nothing to do with Hobbs.
Hobbs is related to engine RPM based on your criteria that you setup in the engine monitoring setup menus.
Hobbs is related to engine RPM based on your criteria that you setup in the engine monitoring setup menus.