[jackking123]

Landed, pulled top cowl, checked, checked connections, wiggled things. It reset after start, no fault 1/2 hr flight back to base.
Builder owner in two yrs since new, said it happened once before. He kind of did the same thing. It reset and did not come back.

It had a full scan recently before this happened during condition inspection. All sensor OK. During condition inspection removed service exhaust,
new plugs, oil change, new plugs, inspections... meaning things were wiggled around. Always make you think

HOT humid weather wise. The engine temps are fine, but could this be the dreaded Rotax coil overheat?

I read this is kind of a nuisance, "a Rotax thing", normal, no worries. When shutting down turning off A of first than B, it is clear LANE A was working.
Fault light is not full ECU failure, Kaput, just some spurious sensor or rebel electron set off the software. Correct? if I am wrong tell me. Not worried.

My current solution is do nothing, pray and wave magic crystals over the cowling before each flight. Thoughts?

 

[snowsam]

If the engine was running and you had the fault active, you can go into your MFD and view the fault code.

If you have the G3X, here is the video of how to do it:

 

[mburch]

No need to go to config mode these days, you can see this information on the System Information page that's accessible from the main menu, or from the Engine page there is a menu option to access FADEC information.

 

[rvbuilder2002]

I think the Flight Training Supplement that Van's is required by regulation to provide with every SLSA or ELSA kit contains details on how to access this information in flight.

 

[rcarsey]

Need to look at what the actual error was. I had an intermittent issue that continually got worse.. it was just a ignition wire with corrosion in the boot. I could hear the noise in my radio long before the ECU threw an error.. if it doesnt come back for you soon, borrow someone's dongle and see what it was. It doesnt throw errors just for funsies.