I originally had an iFly 720 which exported NMEA data via the USB-serial cable available from Adventure Pilot to my MGL XTreme EMS's fuel flow computer function. This is a one-way communication, the EMS is receiving GPS data sentences from the iFly. This initially seemed to work well. However, at some point (I honestly don't know if it was in relation to a software update or not), I noticed that the EMS would stop receiving data after ?30-40 minutes of flight. This is indicated by the fuel flow's ground speed and range changing color and defaulting to a pre-set average groundspeed when NMEA data is not available.
I never really got this fully resolved before I upgraded to the iFly 740. Again, initially, it seemed to work fine. However, now after only 7-10 minutes of flight, the EMS's fuel flow indicates it is no longer receiving NMEA data. If I shut the iFly 740 down and re-boot, it immediately starts working again, but the same failure happens about 7-10 minutes later!
I've double-checked that I've outputting the correct GPS data sentences in the "Custom" configuration menu of the iFly. I also re-verified that both the EMS and the iFly have the same baud rate (4800).
I've submitted this to support and hopefully they'll have some ideas or better yet, a fix! I thought, however, that I would see if anyone else has experienced this and knows a possible solution? One thing I wonder about is the communication baud rate - both MGL and iFly say to be sure the rates are the same, but give no specific recommended rate. Would a higher baud rate help any?
It's really frustrating because it works so well for a few minutes and then quits!
John
N750A