Quote:
Originally Posted by lr172
Being a software guy, I'll take a guess at what is happening. If there is a setting that starts and stops logbook flight capture based upon ground speed, like the demo recording, setting that to 1 or 2 should fix it. As I mentioned, I will bet that the Garmin's are sending the waypoint or lat/lon coordinates as part of their power on test routine. If you have the GS threshold set >0 and you're not moving during the power on, it shouldn't capture the leg. This seems to be be confirmed by the other poster. I would guess that a setting of 1 or 2 still should keep you from ending legs at the top of the loop.
If you tell me where the log settings are, I will change mine and confirm this. I would further speculate that the previous version ignored the POST data (possibly unintentionally) and while addressing a different problem, they introduced this new behavior. It happens all the time in the s/w business.
Larry
|
Thanks Larry. I heard back from Jeff and GRT and he's still looking into this. He did tell me that he put a 20 second delay in the logging programming to stop the problem with the loop problem back an update or two ago. In this latest release they added the new ground speed setting for the ADSB ground switching. I changed mine from AUTO to 30. I'm going to try it back in AUTO just to see if that makes a difference. I'll have to dig around and find where the GS settings are for the log/flight timers.
__________________
Jerry "Widget" Morris
RV 8, N8JL, 3,000+ hours on my 8.
VAF #818
Saint Simons Island, GA. KSSI
PIF 2008, 2009, 2010, 2011,2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020
 I just wish I could afford to live the way I do
|