fbpx

 

  • Re: FADEC interface

    by » 4 months ago


    Thanks Jeff.

     

    I redo all the wiring for HIC connectors to GEA 24, and the problem persists. Also I checked all X connectors, and are as per manual.

    Symptoms:

     

    Both Lanes ON:

    Garmin Engine FADEC Interface Info:

    • Lane A Status - Caution
    • Lane B Status - Caution
    • Ambient Pressure -          Sensor Fault
    • Boost Pressure -          Sensor Fault
    • Crankshaft Position -          Sensor Fault
    • Manifold Air Pressure - Sensor Fault
    • Manifold Air Temp -          Sensor Fault
    • Oil Pressure - Sensor Fault
    • Oil Temperature - Sensor Fault
    • Overboost PCV Valve - Fault

    Engine Indications:

    • No RPM
    • No Oil Press
    • No Oil Temp

    Lane A ON:

    Garmin Engine FADEC Interface Info:

    • Lane A Status - No Data
    • Lane B Status - Caution
    • Lane A/B Communication - Fault
    • Ambient Pressure -          Sensor Fault
    • Boost Pressure -          Sensor Fault
    • Crankshaft Position -          Sensor Fault
    • Manifold Air Pressure - Sensor Fault
    • Manifold Air Temp -          Sensor Fault
    • Oil Pressure - Sensor Fault
    • Oil Temperature - Sensor Fault

    Engine Indications:

    • No MAN Press
    • No RPM
    • No Oil Press
    • No Oil Temp
    • No CLNT
    • NO EGT

    Lane B ON:

    Garmin Engine FADEC Interface Info:

    • Lane A Status - Caution
    • Lane B Status - No Data
    • Lane A/B Communication - Fault
    • Crankshaft Position -          Sensor Fault
    • Overboost PCV Valve - Fault

    Engine Indications:

    • No RPM
    • No Oil Press
    • No Oil Temp

    Garmin Engine FADEC Interface Info always reads Engine Type, Serial Number, Hours, Throttle Position, ECU Type, ECU Serial Number and ECU Software Number.

    RS-232 Port configured as Garmin Instrument Data.

     

     

    No clue yet. I´m trying to get a B.U.D.S. to scan the ECU.

     


  • Re: FADEC interface

    by » 4 months ago


    Ricardo,

    You say the RS232 port is configured as “garmin instrument data”.  That is correct, but the RS-232 path is only a backup. The information from the GEA-24 to the GDU is primarily (normally) over the Garmin CAN.  In the event the Garmin CAN fails and the RS-232 path is used, it will only display engine data on the GDU that it’s connected too, it won’t propagate to a second EFIS. 

    I know you have connected the Rotax CAN to the GEA-24 Pins 17 & 33 on the J244 connector, but have you also connected the Garmin CAN to pins 1 & 2 on the GEA-24 J241 connector? Looking at the original photo you posted the Garmin CAN does not appear to be connecting to the GEA-24.  

     


  • Re: FADEC interface

    by » 4 months ago


    Jeff, yes Garmin CAN bus is connected to GEA 24. It has a status light on the back of the unit, and it’s blinking indicating good connection. It has to be something else. 
    I appreciate your help and time. 


  • Re: FADEC interface

    by » 4 months ago


    I assume you found the problem with no power on HIC A/B pin 1?


You do not have permissions to reply to this topic.