EFWD Build

[efwd]

yep, however as I understand it, having the certification will gain you access to the codes via the dongle and the computer program. Quite honestly, I was never provided any valuable information by the mechanic who has done my two 100hr services. He has used the computer and it has told him accurately what it was that is turning on my lane lights. That is all that mattered to me at the time so I didn't really care. Now that I am trying to wean myself from the need to have anybody else involved, I am reallizing things. Just to be able to manage the codes I will need the Program to download to my computer which requires that I purchase the Dongle for $1300. Then you have to have spent $500 and a weekend for the rights to codes. Now, every other year, take another day and spend $315 to maintain the rights. Just acknowledging the facts, not complaining. I think I may just have the FBO download them or interpret what I pull off from the G3X. Then again, I sure would appreciate a better understanding of this engine though, so I may take the recert class in a few weeks.

[efwd]

Well I got another opportunity to figure out the data that the G3X can see from the Rotax912is. Im hoping that this is just intake air temperature being too high. I flew to San Diego today and I found 105 degree air back at Chino when I came home. I was able to get the reboot of the G3X to occur without having to shut down the lane. I guess I am on the right track on the cause or it is simply a failing sensor. I need to figure out how to address such a code now. Is it a sensor or am I going to need another NACA duct to get cooler air into the intake if I hope to fly in excessive heat. Anybody else ever get this code?

[Shadowrider]

Can you look at your data log to see what your intake temps hit? Looks like the sensor has failed? Out of curiosity does the data log, log all the data from 912is that it’s can see through the can bus? If I remember you recently turned on datalog in the G3x?

[efwd]

Hi Dustin. I had in fact had the Data Log programmed the entire time since I have been flying. I believe during that time of programming I just had no idea or I had forgot that data can be captured. In addition to that I had not always had an SD card in the slot. Having said that, here is what the card revealed at the time that this failure developed.

2020-09-05,18:59:22,01:59:22,-07:00,+33.8786072,-117.7495259,1683,3DDiff,7162.1,78.3,307,-32,24,-1.38,293.6,2.1,10,1735,1608,-170,86.0,92,0.25,0.09,-0.031,1.054,+0.070,-0.289,250,4500,29.78,GPS,KCNO,,8.1,44,15,3.988,+1. 00,7595,1.25nm,,,,,,,,,,,,,,,,-11.8,38.6,4768,13.1,297,040007FF N N 1,040007FF 1,1200,ALT,212,40.2,61,4980,19.4,14.0,0.2,3.1,1400 ,1420,1505,1485,,ENGINE ECU,


There are paragraphs of these recorded over the one hour flight. I only had the light for the last 5-7 min of the flight so Im not sure what it is logging the whole time. This is the first paragraph that came up with "ENGINE ECU" logged at the end. The time was 18:59. Im not able to decipher any of it with certainty. No temperatures that I can see.
Im going to fly this morning before it gets hot. If my light comes on then I suspect you are correct about the sensor being bad.

[Shadowrider]

Interesting. Looks like date/time zulu correction/Lat long/some sort of navigation reference KCNO?/transponder/ and then what appears to be a bunch of engine parameters?
CHT/fuel pressure/oil pressure/rpms/manifold presssure/amp??/egt1/egt 2/egt3/egt4? These are just a guess. Looks like you found out how to get into the faults in the G3X.
212,40.2,61,4980,19.4,14.0,0.2,3.1,1400 ,1420,1505,1485,,ENGINE ECU.

Sounds like you don't really need the dongle but you can read the faults in the G3x. Once they are corrected and you cycle the ecu they should clear. From what I am seeing, most are having problems with the connectors. I would check your manifold temp sensor connector. Unplug it, clean it with some air or possible contact cleaner in a spray can and then reconnect. If the error appears I would probably try swapping it out.

[efwd]

I seemed to have fixed it. I attempted to fly in cool air without doing anything so that I could rule out OAT being the culprit. I got the light while on the ground run up when I went WOT. Returned to the hangar, removed and reinserted the sensor after manipulating the probe inside a bit. I found the tip to be resting against the guard that Surrounds it. I had just disconnected and reconnected it without improvement. It was only after manipulating it that it turned the light out. I flew it for 1.2 hours without a repeat light. I am going to order a spare in the event I have only temporized the repair.

[michaega]

Eddie it was nice to talking to you at Corona this morning and yes a bit hazy today with the California fires blocking out the sun. I’ll let you know when Richard is back working on his 915 install on his Kitfox 7 and maybe find out about the property he purchased with landing area in Flagstaff AZ.
George

[efwd]

Yeah George that was really nice to reconnect with you again. It has been awhile. I had ash all over the windscreen and leading edges when I got back to Chino.

[Shadowrider]

Good find Eddie! Maybe the probe has been close to the side of the sensor and intermittently grounding out and has been that way from day one? Is this what caused your fault when you where over Vegas?

[efwd]

The light on the way to Vegas was due to the lack of the securement devices that hold the pressure sensors to the air-box tightly. The latest light before this was the coil that went south. The beauty is that Carl has been enlightening me about the G3X and the capabilities. We spoke tonight and we believe Garmin is falling short only with the education about how to use it. There are limited youtube videos about using the G3X. He showed me how this thing is basically a “black box”. I have downloaded my file from my SD CARD into flygarmin.com and I can watch my entire flight and my engine operations as well as the map and most everything on the EFIS. Airspeed, HSI, etc etc. Amazing technology these days.
P.S. I just found on Flygarmin.com a two day course for $495. Many of the other avionics have Ecourses that are far less expensive. And, lets not forget we could read lots of pages in the install manual and the operators manual. Boring, and I can't remember how to do all this stuff once I am in the air. It has been slow going on learning it but the qty. of information available to me in flight is crazy.