Author |
Topic |
|
AlphaLima
Moderator
Germany
1978 Posts |
|
brunotl
Pterodattilo
France
1096 Posts |
|
davesalmon
Pterodattilo
United Kingdom
1620 Posts |
Posted - 23/01/2020 : 16:37:32
|
I have just updated the old Android phone I use with Condor, to 7.1h. As soon as the data stream starts a message pops up on the screen every few seconds, "Master Time Reset". As soon as the data stream is stopped by either pausing Condor or starting the Exit process, the message stops. Didn't occur previously, though can't be certain whether it was version f or g. |
|
|
brunotl
Pterodattilo
France
1096 Posts |
Posted - 23/01/2020 : 23:13:32
|
quote: Originally posted by davesalmon
I have just updated the old Android phone I use with Condor, to 7.1h. As soon as the data stream starts a message pops up on the screen every few seconds, "Master Time Reset". As soon as the data stream is stopped by either pausing Condor or starting the Exit process, the message stops. Didn't occur previously, though can't be certain whether it was version f or g.
can you do a NMEA Log and send it to me ? |
Edited by - brunotl on 23/01/2020 23:13:55 |
|
|
davesalmon
Pterodattilo
United Kingdom
1620 Posts |
Posted - 23/01/2020 : 23:26:05
|
Will do. Dave |
|
|
Robert Haugen
Pulcino
Norway
37 Posts |
Posted - 25/01/2020 : 16:14:26
|
quote: Originally posted by davesalmon
I have just updated the old Android phone I use with Condor, to 7.1h. As soon as the data stream starts a message pops up on the screen every few seconds, "Master Time Reset". As soon as the data stream is stopped by either pausing Condor or starting the Exit process, the message stops. Didn't occur previously, though can't be certain whether it was version f or g.
I have the same issue. |
Robert Haugen |
|
|
brunotl
Pterodattilo
France
1096 Posts |
Posted - 25/01/2020 : 16:22:57
|
we have found the problem and publish a new version a 7.1i on GPlay. |
Edited by - brunotl on 25/01/2020 16:23:30 |
|
|
Robert Haugen
Pulcino
Norway
37 Posts |
Posted - 25/01/2020 : 16:55:59
|
quote: Originally posted by brunotl
we have found the problem and publish a new version a 7.1i on GPlay.
Sorry, forgot to say. I use the PC version, which have the same issue. |
Robert Haugen |
|
|
brunotl
Pterodattilo
France
1096 Posts |
|
danielvelez
Falchetto
Colombia
145 Posts |
Posted - 27/01/2020 : 03:33:33
|
Hello.
I have a bug on versions g and h, during this weekend flying. Bug seems to be that "head wind" field goes crazy showing big numbers, even getting over the other data fields, and thus the speed to fly speed shows 0, so mccready speed to fly is unusable.
I´m using a hisense a2 pro, and connected to a bluetooth airspeed and vario (altair).
|
|
|
AlphaLima
Moderator
Germany
1978 Posts |
Posted - 27/01/2020 : 07:50:10
|
OK, thanks for reporting, I'm afraid we need a NMEA logs of one of your flights to reproduce that.
|
Edited by - AlphaLima on 27/01/2020 09:54:40 |
|
|
brunotl
Pterodattilo
France
1096 Posts |
Posted - 27/01/2020 : 14:31:34
|
quote: Originally posted by danielvelez
Hello.
I have a bug on versions g and h, during this weekend flying. Bug seems to be that "head wind" field goes crazy showing big numbers, even getting over the other data fields, and thus the speed to fly speed shows 0, so mccready speed to fly is unusable.
I´m using a hisense a2 pro, and connected to a bluetooth airspeed and vario (altair).
As AlphaLima says, we need the NMEA log...
But if you have external Airspeed, HeadWind is simply "TrueAirSpeed - GroundSpeed"
So problem can come from : - Bug in External device sending wrong airspeed - BUG in device GPS reporting a wrong ground speed - BUG in LK8000 Drivers you use to get data from external device. - BUG in LK8000 GPS Driver used to get GroundSpeed
for two first we can't do anything, for the two last we need to know witch driver you use and NMEA Log to check what data is really sent by device...
|
|
|
danielvelez
Falchetto
Colombia
145 Posts |
Posted - 27/01/2020 : 20:19:57
|
quote: Originally posted by brunotl
quote: Originally posted by danielvelez
Hello.
I have a bug on versions g and h, during this weekend flying. Bug seems to be that "head wind" field goes crazy showing big numbers, even getting over the other data fields, and thus the speed to fly speed shows 0, so mccready speed to fly is unusable.
I´m using a hisense a2 pro, and connected to a bluetooth airspeed and vario (altair).
As AlphaLima says, we need the NMEA log...
But if you have external Airspeed, HeadWind is simply "TrueAirSpeed - GroundSpeed"
So problem can come from : - Bug in External device sending wrong airspeed - BUG in device GPS reporting a wrong ground speed - BUG in LK8000 Drivers you use to get data from external device. - BUG in LK8000 GPS Driver used to get GroundSpeed
for two first we can't do anything, for the two last we need to know witch driver you use and NMEA Log to check what data is really sent by device...
Ok. Prior to versions h, and i, the phone worked good. (With the gps workaround at first and then with your special version). I have not updated any firmware on the airspeed sensor or vario sensor, and the phone hasn´t updated any "firmware" at all.
If i "replay" the igc, there is no issues with the info and everything works great, but during flight the info was wrong...
Here you can see at the end of this short video, the screen on the instrument, showing looooonng string on the HdWind field and the "Speed to Fly" showing 0.
https://youtu.be/kJkl_hDapUE
I have configured, lower left to Indicated Airspeed as received from the bluetooth feed, and on the lower right, speed to fly.
How can I "make" a nmea log for you guys? Any suggested app for trying it out on the next adventure?
|
|
|
brunotl
Pterodattilo
France
1096 Posts |
Posted - 27/01/2020 : 21:49:57
|
you video is private, we can't watch it.
in replay, headwinf is calulated using wind estimation in circling, same as if you only use only GPS data.
to make nmea log just go in menu "Config 2/3" -> "NMEA Logger", for each configured device a file is created in "_Logger" folder.
|
|
|
danielvelez
Falchetto
Colombia
145 Posts |
Posted - 28/01/2020 : 18:57:48
|
Ok. Video should be public now... I missed a few steps loading it to youtube.
I´m gonna try to log the nmea as you suggest and send the feedback then.
|
|
|
|
Topic |
|