| T O P I C R E V I E W |
| turlings |
Posted - 19/06/2021 : 16:26:56
I have problems using my LK8000 kobo combined with a bluefly vario in my paraglider. The log files are not correct in some sort, since during the flight the flight time freezes (sometimes after 1minute, sometimes after 17, so not cosistent). I continued flying so there was no top landing or such.
However, the logger parameter which normally on auto, states it is still on. The odometer also still adds up, it shows me thermalling and everything I need, except for the correct "flight time" and the logger in te igc. Strange thing is that I could still use "force landing" at the end, without it saying "not flying", so somehow it was not registered as landed.
It is realy annoying since I lost my first XC flight which I would have loved to review in 3D.
Anyone who can help or knows the issue?
Regards,
Toine |
| 15 L A T E S T R E P L I E S (Newest First) |
| turlings |
Posted - 25/06/2021 : 09:31:27
nice! updated again...
that was easy 
Thanks so much! |
| brunotl |
Posted - 24/06/2021 : 16:06:07
on kobo version release and beta share the same settings files, and settings settings files are not included in distribution archives so nothing is overwrited..
a best practices is to do a complete backup of your LK8000 directory before upgrade... |
| turlings |
Posted - 24/06/2021 : 15:32:33
When installing a newer version, what is the quickes way to keep your settings? I don't know it the saved set-up files are overwritten.
Is there already an estimation on the release date as a stable version? |
| brunotl |
Posted - 24/06/2021 : 12:24:24
only fixed in beta (7.3.7) |
| turlings |
Posted - 24/06/2021 : 11:40:41
I updated to 7.2, should that fix the problem as well? thanks for the help... I understand the software much better by checking the log files now! |
| brunotl |
Posted - 23/06/2021 : 10:15:15
you can try last beta available here : https://github.com/LK8000/LK8000/releases/tag/7.3.7
by modifying how Flight time is calculated to ignore invalid GPS data, problem should be fixed... |
| brunotl |
Posted - 22/06/2021 : 20:54:14
by making a workaround to deal with invalid input ...
|
| turlings |
Posted - 22/06/2021 : 20:26:19
I do not realy understand. If it is not related how can updating fix my issue? |
| brunotl |
Posted - 22/06/2021 : 17:39:48
problem is not related to LK8000 version...
next version should fix your issue... |
| turlings |
Posted - 22/06/2021 : 16:26:12
Maybe it's wise to first update to version 7.2? Or best first try to find this issue... |
| turlings |
Posted - 21/06/2021 : 17:09:42
Just wondering if that might combine with the fact that the IGC files seem to be created in 2012... which was wrong in Nickel. I don't know if this is used somewhere besides for the system time.
I was playing around with NMEA last week, so I have a file, but not yet at a failing moment. Don't know if it helps.
https://we.tl/t-P5ofJqRb4J
I will try to reproduce the error riding around with it. It does not happen all the time and not at the same time of flight. |
| brunotl |
Posted - 21/06/2021 : 16:39:41
as we can see in your Rruntime.log file, your gps chip send invalid date/time time to time,
i need a NMEA log from your GPS to check what data is really send by your gps when that happen... |
| turlings |
Posted - 21/06/2021 : 14:02:43
So actually it is only flight time and the log-file which is accessible on the kobo which are incorrect. The IGC files are all there, but show an inconsistency with the logbook. |
| turlings |
Posted - 20/06/2021 : 13:43:44
I uploaded the available files over Wetranfer:
https://we.tl/t-fdYl22Y3jm
Do not have an NMEA yet |
| brunotl |
Posted - 20/06/2021 : 12:31:35
wayting for nmea, ca you send the track log, the logbbok files and runtime.log ? |
