Develop
Ticket #1218 (closed defect: fixed)
MC setting with Vega
| Reported by: | dgjansen@… | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Other | Version: | 6.2.3 |
| Keywords: | altair,vega | Cc: |
Description
Unable to change MC using switch on Vega, only available directly on Altair
Attachments
Change History
comment:2 Changed 2 years ago by Turbo
- Milestone XCSoar 6.0.x deleted
Milestone XCSoar 6.0.x deleted
comment:4 Changed 2 years ago by max
- Status changed from new to closed
- Resolution set to fixed
Supposedly fixed. Reopen if still occurs.
comment:5 Changed 18 months ago by ubx
- Keywords altair,vega added
- Status changed from closed to reopened
- Version changed from 6.0 to 6.2.3
- Resolution fixed deleted
- Milestone changed from XCSoar 6.0.x to XCSoar 6.x @ Altair
This problem still exists in XCSoar 6.2.3 on Altair. See attached trace.
comment:6 follow-up: ↓ 7 Changed 18 months ago by ubx
After some more debugging/trancing:
Setting MC either on XCsoar or with the Vega switch:
XCSoar always sends a MC 0 back to Vega (nmea sentence: $PDVMC,0,0,0,0,10133*50).
Change MC on Vega, it sends a correct nmea sentence ($PDSWC,4,806000,101,124*6E)
and XCSoar receives it (verified in debug-mode). But for some reason XCSoar
does not like it.
comment:7 in reply to: ↑ 6 Changed 18 months ago by baderr
Replying to ubx:
After some more debugging/trancing:
Setting MC either on XCsoar or with the Vega switch:
XCSoar always sends a MC 0 back to Vega (nmea sentence: $PDVMC,0,0,0,0,10133*50).
Change MC on Vega, it sends a correct nmea sentence ($PDSWC,4,806000,101,124*6E)
and XCSoar receives it (verified in debug-mode). But for some reason XCSoar
does not like it.
Hi
I have a dual Altair/Pro? installation and after propper configuration of the com port everithing with MC setting seems to work fine with me (DeviceA AltairRU 57600 Com3, DeviceB Vega 38400 Com1, DeviceC NmeaOut? 38400 Com2)
I have no knowlege how to debug nmea stream but the calculations in XCSoar seems to change and the MC changes in the display.
Ralph
comment:8 follow-up: ↓ 9 Changed 18 months ago by ubx
Hi Ralph,
yes, it works all fine with the XCSoar version 5.2.1 (original installed on Altair), that you most likely have installed. My test concerns version 6.2.3.
Can you confirm that?
Andreas
comment:9 in reply to: ↑ 8 Changed 18 months ago by baderr
Replying to ubx:
Hi Ralph,
yes, it works all fine with the XCSoar version 5.2.1 (original installed on Altair), that you most likely have installed. My test concerns version 6.2.3.
Can you confirm that?
Andreas
I've run 6.2.3 from USB stick.
Only tested on ground (Glieder not ready to fly)
Confirmed that the setting arrived in Vega by starting 5.2.1 afterwords.
I can document it by video on saturday
Ralph
comment:10 Changed 18 months ago by baderr
Result of Test (6.2.3 from USB, system like described erlier):
- Moving the Switch on Vega changes MC Display and V OPT on Altair
- After GPS connection, It takes a while (one or two minutes) until switching is recognized (like some connecting in the background has to be established fist)
- After Restart, MC Setting is 0 again (5.2 remebers setting)
- The Sensors like wheel and Breaks are working fine
Maybe this can help, Ralph
comment:12 Changed 16 months ago by ubx
After some more testing:
MC setting via the Vega MC-Switch is only possible if XCSoar receives
valid GPS fixes (GPRMC sentence).
comment:13 Changed 16 months ago by Turbo
that might just be the infoboxes that don't update properly... please try to switch to fullscreen and back and see if the MC really hasn't changed
comment:14 Changed 16 months ago by ubx
055b23692885beb033c6add9f12a817109772b71
No, the infobox is updated properly, but without GPS fix, the MC value
goes back to an initial value (to 0.0 after XCSoar startup) after a few seconds.
see the demo: http://youtu.be/i4vb3NeK6l0
There is another problem within this context:
In the state of "GPS waiting for fix", switch to full screen and back, the vario gauge looses values as you can see here: http://youtu.be/aERE-3SW0wg
comment:15 Changed 5 months ago by max
- Status changed from reopened to closed
- Resolution set to fixed
f9272ddad1522ba3f88fad722ae93ca65b125122

XCSoar 6.1.0 has been released yesterday. PLease check with it if the issue is still present