Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LXNAV S80 Vario: Download of Flight List fails #1248

Open
lordfolken opened this issue Jun 13, 2023 · 11 comments · May be fixed by #1254
Open

LXNAV S80 Vario: Download of Flight List fails #1248

lordfolken opened this issue Jun 13, 2023 · 11 comments · May be fixed by #1254
Labels
more information More information needed

Comments

@lordfolken
Copy link
Contributor

lordfolken commented Jun 13, 2023

XCSoar versions having and not having the problem

Not Working:
current head.
6.8.17
7.10
7.23

Expected behavior

After going to Config->Devices->FlightDownload, be presented with a list of flights to choose from, and to then download.

Actual behavior

There is an error: Failed to Download flight list

Setup:

  • This is a flarm hooked up to the gps port of an S80 Vario running 9.13 firmware.
  • The S80 is connected via the bluetooth stick from LXNAV
  • rfcomm bind to the device to /dev/rfcomm0
  • the flarm doesn't have gps lock as i'm indoors
  • communication from xcsoar running on a linux computer to the vario works (i get environment, flarm, gps(when outside), baro, airspeed and vario
  • Bidirectional communication works: MC/Bal/Bugs go both ways
  • Declaration of tasks works, (not always)
  • There are 50 Flights in the logbook of the device

The configuration in xcsoar:
2023-06-13-211724_480x640_scrot

Logs:
xcsoar.log
2023-06-13_19-20.nmea.txt

DataPort Spec from LXNAV:
LXNAV_DataPort_Specification1.04.pdf

XCSoar 6.8.17:
xcsoar-6.8.17.log
XCSoar 7.10:
xcsoar-7.10.log
XCSoar 7.23:
xcsoar-7.23.log

@MaxKellermann
Copy link
Contributor

Since you did not specify a version that worked, I figure that you never tried this with any other XCSoar version?

@lordfolken
Copy link
Contributor Author

I will try some other versions.

@lordfolken
Copy link
Contributor Author

There is two things that strike me:

  • it seems to stop after the 8th flight
  • the starting date seems wrong, always 00.00.1980. (althought this would be a bug in the firmware)

@lordfolken
Copy link
Contributor Author

So so far i have been able to trace the problem to ParseLogbookContent in ReadLogbookContent.

It doesn't return true and there is no further handling of the case.

@lordfolken
Copy link
Contributor Author

So its failing to parse the Date, because IsPlausible expects a month and day bigger than 0.
For some reason the vario returns. "00.00.1980" as a flight date.

@lordfolken
Copy link
Contributor Author

HFDTE220417 is present in the file i was able to download.
The dates show correctly in the Vario's UI.

So while this is a firmware bug, any incorrect date in any file will prevent XCSoar from displaying the flight log list of all the flights.

@lordfolken lordfolken linked a pull request Jun 20, 2023 that will close this issue
@groundhogxc
Copy link
Contributor

groundhogxc commented Jun 21, 2023

Thanks for the PR. By the way: Did you (re)start the LX instrument (the hardware) very late, like just a minute or so before takeoff? I have seen some funny things happen with "historic" dates in IGC files in this scenario, although did not yet encounter this particular problem.

@lordfolken
Copy link
Contributor Author

I think the main thing with my setup, is that the flarm is powered through the s80. So it only starts when the vario starts.

@kobedegeest
Copy link
Contributor

kobedegeest commented Jun 22, 2023

we had (have) similar issue in our club with the s100 of invallid dates the issue (according to LX) is the setting "logger always on" in the LX device if this setting is enabled and it does not have a gps fix at startup the whole log file is wasted because it gets assigned an invalid date.

@groundhogxc
Copy link
Contributor

Here the FLARM is also powered through the LX. (By the way: Can you control/declare/download the FLARM through the LX via pass-through? That is my dream, but it never worked for me).

I am not sure about the "logger always on" setting; I did have the impression that the problem occurs if the first fix is not recorded a sufficiently long time before takeoff detection or something like that. Because it seemed to be connected with "rebooting" the device very close to takeoff.

@lordfolken
Copy link
Contributor Author

I got a beta Firmware from lxnav. Ill try it out.

@MaxKellermann MaxKellermann added the more information More information needed label Dec 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
more information More information needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants