fbpx

 

  • Re: BUDS dongle ECU download error code messages reference

    by » 6 years ago


    I get similar gobbely goop on another 912iS engine that I downloaded via dongle that is running like a top. Yes both engines have had all the required stater updates.

    The simple point is that if we had a tool to understand/decode all the specific Rotax messages they designed into the ECU to pop up, then we could make an informed decision as to what is going on.

    Knowing what the messages are would explain allot.
    Which ones would cause a solid Lane light, which ones would cause flashing Lane lights. Which are typically startup or run up faults, such as doing a run up and switching the Lanes off and back on.

    The maintenance/service procedures for the dongle need to be in the Rotax engine maintience/service documents.

  • Re: BUDS dongle ECU download error code messages reference

    by » 6 years ago


    The tool needed is the software titled BUDS log viewer software, On the Rotax site under ECU software is a list of which version is available for 3 types of operating systems. The listing states that training is required to obtain the appropriate software.

  • Re: BUDS dongle ECU download error code messages reference

    by » 6 years ago


    Since all other maintenance/service procedures for rotax engine are in the Rotax engine maintenance/service documents to maintain the engine properly to ROTAX standards, why are the 912iS doggle maintience/service documents not provided? Why the secret? I do not understand. Rotax needs to change improve this policy it does not make sense. Every single procedure/process for installing/servicing and maintaining is in the rotax documents, why hold back needed information? Who at ROTAX can fix this? It is a much needed improvement in customer service.

  • Re: BUDS dongle ECU download error code messages reference

    by » 6 years ago


    Paul,
    I can't enlarge the report you posted to the point I can read it, but it appears that it is a list of all the faults recorded during the last downloaded operational time period.
    I think the system may record faults detected during the start up and shut down phase so it could be that many are really not germane to your in flight engine warnings.
    The analysis of the time the fault is recorded should be correlated to an actual in-flight warning light and give you more insight into the problem.
    Again, since I can't read the posted document, I am only offering it as a suggestion. You may have already distilled the faults during the in-flight time period.

  • Re: BUDS dongle ECU download error code messages reference

    by » 6 years ago


    James,

    It is hard to read and low resolution.
    The Yellow highlights indicate that the second print is 44 hours after the first.
    The circled entries are the only ones that have changed.

    There were 10 New Generator select faults of two varieties.
    There were 6 New eTPU (enhanced Time Processing Unit) Faults. (Crank Position Sensor???)
    There were 11 New Cylinder #3 EGT Sensor Faults.

    For a total of 27 Logged Faults in 44 hours.

    I would work on that list from the bottom up.
    The EGT faults are the most likely and easiest to resolve.
    Swap the #3 EGT Probe with another cylinder and see if the problem moves (Intermittent Probe) or is resolved (intermittent connection).

    Paul,
    If you have a level 2 Dongle, you should be able to clear the faults so you do not have to keep looking at the faults that happened a hundred hours ago.

    Bill Hertzel
    Rotax 912is
    North Ridgeville, OH, USA
    Clicking the "Thank You" is Always Appreciated by Everyone.


You do not have permissions to reply to this topic.