-
Notifications
You must be signed in to change notification settings - Fork 33
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
XcSoar/XcVario sync problems continued! #144
Comments
Hey Graham, could you please add details to your report? thx |
Helmut I thought I had Eckhard Entering a figure on the flight setup in XCS always results in the same number writing to XCV so this is fine. The problem is the 40l or so that is added on startup or each time the flight setup page is open. With XCS "Sync TO" device ON and Sync FROM device OFF. XCS flight setup updates XSV exactly. Changing the setting in XCV has no effect as you would expect. |
Dear Graham, |
I have checked these parameters and they match. |
If there is no ballast reported from vario, there will be no update from vario, so this fix must stay. It may behave same as if you switch off sync from device, hence it may just cover another issue, but is not the root cause. |
Eckhard
Link to my OneDrive files showing requested photos and a video showing the issue.
Dry Mass of 425 kg on XCS is as per manual to include pilot weight
Did you see my Ps using XCS 6.8.11 and Borgelt protocols. Problem unchanged.
https://1drv.ms/u/s!AnZWH7uXxHdohpMeRmdx5dOY5PMZ6g?e=DumlCy
regards
Graham
|
The things i see here: |
EckhardThanks for your efforts, I think until it is resolved I will disable part of the two comms exchange and loose the functionality I am interested in, MC and QNH and will check updates from time to time so please consider this closed from me for the time being.
I have tried to match the loading but the weight and area steps in the settings on both XCSoar and XcVario don’t allow to get an exact match. Whilst I understand the relationship with ballast and wing loading, I don’t understand why the units don’t simply exchange litres (XCSoar seems to send litres to XCV without problems) and let each sort the wing loading calculations. If you decide to stop exchanging ballast data while the problem exists please let me know.Thanks again for your attention
Graham
|
Yes, i guess disable this at first shall be okay, hence i want to encourage you to write a bugreport in xcsoar when you encounter issues that are already confirmed, such as ballast precision is got cut in 7.21, otherwise a new version will never happen that fixed this problem. |
Eckard
I have raise an issue with XCSoar, I hope I am not digging a big hole for myself!!!
Regards
Graham
From: Eckhard Völlm ***@***.***>
Sent: 01 January 2022 21:56
To: iltis42/XCVario ***@***.***>
Cc: GrahamD2 ***@***.***>; Author ***@***.***>
Subject: Re: [iltis42/XCVario] XcSoar/XcVario sync problems continued! (Issue #144)
Yes, i guess disable this at first shall be okay, hence i want to encourage you to write a bugreport in xcsoar when you encounter issues that are already confirmed, such as ballast precision is got cut in 7.21, otherwise a new version will never happen that fixed this problem.
An exact match for the masses is not needed, but as close as possible or less that 0.2% delta should be okay.
The protocol had been defined by cambridge long time ago and inherited to borgelt and xcvario. Limits in there are well known, and yes i agree there might be benefits from exchanging litres in future, hence its not the root cause of the trouble you see.
This simply comes first from different reference data, and second from rough ballast updates in the older version (solution for that already merged). And once your reference data is different, mostly all other polar calculations won't match, or at least do something that is very hard to explain e.g. different S2F, different netto vario, in both units.
The ballasting things are under work in xcsoar as well, xcvario is a bit advance providing crew weight and empty mass, but this will come this winter i guess.
—
Reply to this email directly, view it on GitHub <#144 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXC4ADMLBEZTXPZG2ILSWELUT5Z7XANCNFSM5LBOMSCA> .
Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub> .
You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AXC4ADOI36ZM7AN633CMMXLUT5Z7XA5CNFSM5LBOMSCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOHPJBM5Q.gif> Message ID: ***@***.*** ***@***.***> >
|
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: