| Author |
 Topic  |
|
|
phil_atkin
Pulcino
United Kingdom
31 Posts |
 Posted - 29/08/2026 : 12:19:25
|
v7.5.6 on Oudie N, S100 and ATR833, with SeeYou Navigator forced to stop.
About 100km into my task with everything running perfectly, I noticed that the map had stopped updating correctly. I restarted the com ports several times - the map updated just once each time. Switching between pages, zooming in/out etc. caused the map to update just once.
When I got to a turnpoint, LK8000 didn't advance to the next TP.
After about another 30 minutes of this behaviour, everything suddenly started working again (without any input from me), announced 'Next TP' (and sent the target to the S100) and it was perfect until the end of the flight. |
|
|
davesalmon
Pterodattilo
United Kingdom
1655 Posts |
Posted - 29/08/2026 : 15:18:39
|
| Found a notice that there was apparently some gps jamming near the East coast area until 27 August. |
 |
|
|
phil_atkin
Pulcino
United Kingdom
31 Posts |
Posted - 29/08/2026 : 18:19:10
|
| I believe that’s right, but I wasn’t near the East coast. In any case, are the symptoms what you’d expect if the GPS was being jammed? I was able to force the map etc. to update whenever I interacted with the system - it just wouldn’t do so continuously. |
|
|
|
brunotl
Pterodattilo
France
1231 Posts |
Posted - 29/08/2026 : 23:40:08
|
Could you check the IGC track and see whether there is a corresponding ~30-minute gap in the recorded track during the period when LK8000 was not updating correctly?
|
|
|
|
phil_atkin
Pulcino
United Kingdom
31 Posts |
Posted - 30/08/2026 : 15:51:22
|
quote:
Originally posted by brunotl
Could you check the IGC track and see whether there is a corresponding ~30-minute gap in the recorded track during the period when LK8000 was not updating correctly?
Hi Bruno,
Yes, there was a gap. It spanned the turning point (the gap began before the TP, ended after the TP). What is interesting to me is that, when the system went back to normal (normal screen updates, normal track recording), it recognised that I had gone round the TP. It’s possible, however, that this was a consequence of my attempts at the TP to advance manually to the next TP.
I can, of course, send you the trace and the runtime.log if that would help.
BTW - further evidence re. GPS jamming - the S100 continued to update bearing, distance etc correctly and continuously.
Phil
|
|
|
|
brunotl
Pterodattilo
France
1231 Posts |
Posted - 30/08/2026 : 18:16:22
|
The gap in the IGC track is particularly significant. It suggests that LK8000 was not just failing to update the display, but was also temporarily not recording/processing the incoming GPS data.
A few months ago, we had a similar issue involving the S100. During the investigation, we found that the S100 could send GPRMC and GPGGA sentences with slightly different timestamps, by a few tens of milliseconds. This could cause a problem in LK8000's GPS processing.
That issue was fixed in v7.5.3, so it should already be fixed in the v7.5.6 version you were using. Nevertheless, the logs may help determine whether something similar is happening here, or whether this is a different issue.
The fact that the S100 continued to update bearing, distance, etc. is also useful information. It makes a general GPS reception/jamming problem less likely and points more towards an issue in LK8000's handling of the NMEA data.
please send me the IGC trace and the runtime.log, but for this particular issue, a raw NMEA log from the S100 would be especially useful. |
|
|
|
phil_atkin
Pulcino
United Kingdom
31 Posts |
Posted - 30/08/2026 : 18:27:17
|
OK - how do I send you files?
And what do you mean by a raw NMEA log from the S100? I do have the IGC from the S100, which is continuous. |
|
|
|
phil_atkin
Pulcino
United Kingdom
31 Posts |
Posted - 30/08/2026 : 18:56:04
|
| (I've sent you the files by email) |
|
|
|
brunotl
Pterodattilo
France
1231 Posts |
Posted - 31/08/2026 : 12:54:17
|
quote:
Originally posted by phil_atkin
what do you mean by a raw NMEA log from the S100?
When the issues occur, activate nmea log in lk8000 ( menu -> config 2/3 -> nmea log)
After exit from lk8000 you will have Nmea_xxx.txt file in _logger folder |
|
|
| |
Topic |
|
Frozen map in v7.5.6