|T O P I C R E V I E W
||Posted - 13/07/2021 : 17:37:00
i am sending Cambridge 302 format data to LK8000, there is field <5> (true altitude in meters +1000), e.g. 1190, and field <6> the QHN information e.g. 1013.
The device sending this (XCVario), shows an altitude of 190 m, and in the CAI 302 protocol field <5> i see the the value "1190" what fits for me according to the description.
LK8000 then display's 190 m for barometric, except if i connect my FLARM that comes as a second device with another baro sensor.
Once this is connected, there is some offset in the barometric altitude LK8000 displays. I see then a difference of several meters, usually 7-8 meters. Independent of the QNH i enter, the altitude changes of course, but the offset remains constant.
The same works flawless using XCSoar, there the altitude displayed is exactly as delivered in the protocol.
Geoid-Altitude feature i have disabled in LK8000, and i have tried also to twist devices means configure first XCVario/CAI302 in device B, and then on device C FLARM.
My expectation was that in case of presence of an altitude from device B (first in alphabet is take first), device C got ignored. According to my observation apparently this is not the case.
So my questions here:
Is this expectation device B comes before D right?
What could be the cause of this observation?
How can we further debug this?
Thanks in advance, Eckhard
|2 L A T E S T R E P L I E S (Newest First)
||Posted - 13/07/2021 : 22:39:31
Okay, then this is the problem. I thought there is some way to use a dedicated baro source, e.g. by the order of devices, afaik XCSoar does like this.
Any option to address as a future feature for LK8000?
Actually we end up with two slightly different altitudes in one cockpit, as future feature this could make sense. What do you mean?
||Posted - 13/07/2021 : 17:52:03
if baro altitude comming from flarm device is available it is used first...