Board index FlightGear Support Flying

Engine Failure

Controlling your aircraft, using the autopilot etc.

Re: Engine Failure

Postby ORZMUD » Tue Apr 23, 2019 11:42 pm

I think that was associated with idle approach VS full throttle takeoff and cruise throttle.


Now that you mentioned, it makes sense.

No, we model low oil from repeated use. I think we add some random water also.

We don't record all the properties associated with these two systems (oil and carb ice) but we do record coughing, and it was definitely an event associated with coughing. It got severe right as the engine shut off. I looked at the property tree and didn't notice enough of a change in oil pressure or EGT to think it was oil related. But it appears that we don't record the icing numbers only the engine status.


I'll appreciate any heading/direction as to where to start looking to add those values in the log

That's why that carb heat is there and is to be used on approach if there is any doubt about conditions. Really, always use it on a long approach is a good rule of thumb I think.


I'll add this to my pre-flight checklist. Thanks!

Regards,
ORZMUD
 
Posts: 36
Joined: Tue Mar 19, 2019 9:59 am
Location: Carlsbad, CA
Callsign: ORZMUD
Version: 2019.2.0
OS: Linux

Re: Engine Failure

Postby ORZMUD » Tue Apr 23, 2019 11:44 pm

wkitty42 wrote in Tue Apr 23, 2019 6:20 pm:looks like it would be a good idea to add additional numbers to the recordings so these types of things can be replayed and analyzed thoroughly...


Totally agree, it will make it easier from the troubleshoot/support pov.

Regards,
ORZMUD
 
Posts: 36
Joined: Tue Mar 19, 2019 9:59 am
Location: Carlsbad, CA
Callsign: ORZMUD
Version: 2019.2.0
OS: Linux

Re: Engine Failure

Postby wlbragg » Wed Apr 24, 2019 1:01 am

You can add the following two signals to Aircraft/c172p/Systems/flight-recorder/components/engine.xml

Code: Select all
    <signal>
        <type>float</type>
        <property type="string">/engines/active-engine/carb_ice</property>
    </signal>

    <signal>
        <type>float</type>
        <property type="string">/engines/active-engine/carb_icing_rate</property>
    </signal>


So Aircraft/c172p/Systems/flight-recorder/components/engine.xml will look like this...

Code: Select all
    <!-- ============================================================== -->
    <!-- State                                                          -->
    <!-- ============================================================== -->

    <signal>
        <type>int</type>
        <property type="string">/controls/engines/active-engine</property>
    </signal>

    <signal>
        <type>bool</type>
        <property type="string">/engines/active-engine/exhaust</property>
    </signal>

    <signal>
        <type>bool</type>
        <property type="string">/engines/active-engine/cranking</property>
    </signal>

    <signal>
        <type>bool</type>
        <property type="string">/engines/active-engine/running</property>
    </signal>

    <signal>
        <type>bool</type>
        <property type="string">/engines/active-engine/crash-engine</property>
    </signal>
    <signal>
        <type>bool</type>
        <property type="string">/engines/active-engine/kill-engine</property>
    </signal>
    <signal>
        <type>bool</type>
        <property type="string">/engines/active-engine/killed</property>
    </signal>

    <signal>
        <type>bool</type>
        <property type="string">/engines/active-engine/crashed</property>
    </signal>

    <signal>
        <type>bool</type>
        <property type="string">/engines/active-engine/coughing</property>
    </signal>

    <signal>
        <type>float</type>
        <property type="string">/engines/active-engine/carb_ice</property>
    </signal>

    <signal>
        <type>float</type>
        <property type="string">/engines/active-engine/carb_icing_rate</property>
    </signal>

    <!-- ============================================================== -->
    <!-- Controls                                                       -->
    <!-- ============================================================== -->


That should give you the icing numbers needed in the future.

That's a quick lesson as to how to add information you want recorded. Beware they must be valid properties and not just a nasal variable to work correctly. You must make sure they are of the correct tpye, ir: int, float, bool, etc.
Kansas(2-27-15)/Ohio/Midwest scenery development.
KEQA (2-27-15), 3AU, KRCP Airport Layout
Intel i5 3570K AMDRX480
User avatar
wlbragg
 
Posts: 5778
Joined: Sat Aug 25, 2012 11:31 pm
Location: Kansas (Tornado Alley), USA
Callsign: WC2020
Version: next
OS: Win10/Linux/AMDRX480

Re: Engine Failure

Postby ORZMUD » Wed Apr 24, 2019 1:36 am

Thanks!
Will add it on my setup.
ORZMUD
 
Posts: 36
Joined: Tue Mar 19, 2019 9:59 am
Location: Carlsbad, CA
Callsign: ORZMUD
Version: 2019.2.0
OS: Linux

Re: Engine Failure

Postby ORZMUD » Wed Apr 24, 2019 4:34 am

I started a new session and right after starting the engine it started to sputter again.
Saved the fgtape to this location:

http://www.saaib.net/file/c172p-20190423-201213.fgtape

I let the engine run in this state for a couple of minutes, then I disabled the "Complex engine procedures and failures" which immediately had the engine back to normal operation.

While playback of the fgtape I opened the Debug/Browse Internal Properties/engines/active-engine during the sputtering phase and after it recovers and couldn't see any much difference, other than the oil-pressure-psi constantly and slowly dropping, max RPM achieves below 1500.

The values of carb_ice and carb_icing_rate barely change.

Regards,
ORZMUD
 
Posts: 36
Joined: Tue Mar 19, 2019 9:59 am
Location: Carlsbad, CA
Callsign: ORZMUD
Version: 2019.2.0
OS: Linux

Previous

Return to Flying

Who is online

Users browsing this forum: No registered users and 2 guests