T O P I C R E V I E W |
bambuko |
Posted - 10/08/2018 : 12:20:07 Is anybody else using this latest Bluefly vario with LK8000? I have connected it to two different kobos and in both cases kobo suddenly shuts down in flight.
One of these kobos worked fine with v11 version of Bluefly vario for a long time, so I am suspecting it might be something to do with v12 and LK8000?
v12 apparently works fine with Xcsoar, but has not been tested before with LK8000
Have you fitted BlueFlyVario_TTL_GPS_v12 and is it working OK?
Alistair, is very kindly trying to help me to debug the issue from the other side of the world, but it's not an easy job.
It is also possible, I am doing something wrong?
so... if you had succes with v12 and LK8000 on kobo please let us know |
15 L A T E S T R E P L I E S (Newest First) |
bambuko |
Posted - 01/10/2018 : 21:27:21 Well... I have been flying many hours now, since adjusting data rate, and never had any problems. I still have no clue what causes the original problem - but at least we have solution that works.
|
villamany |
Posted - 01/10/2018 : 20:15:38 I just downloaded a IGC file from a friend Kobo with BFv12 and XCsoar without the 9600bps GPS speed change and has several glitchs going from 2000m to 22m altitude in some points, i think this may be the issue for LK hangs. I flew next my friend with the BFv11 (updated with the v12 firmware) and the log is fine without any issue.
https://drive.google.com/file/d/1wwZKOzbX8s1gZ5wTrQT6POpFw3h5_VtY/view?usp=sharing
|
villamany |
Posted - 24/09/2018 : 20:41:51 Hi guys, same issue here on the latest Aura 2ed+BlueFly v12 installs, now seems to works fine at 9600 baud in UART1, however in some early v11 installs i get a pair of kobo hangs at 115200 baud in UART2 so i decided to go down again to 57600 baud on that.
So my preferred setting for both v11 and v12 (and never get a hang since some flying months) is 9600 for GPS/UART1 and 57600 for kobo/UART2 also is a good idea to enable the new startDelayMS parameter for prevent some hangs when you turn on the Kobo and bluefly at the same time. I use a startDelayMS of 5000ms and works perfect.
Thanks for your help. |
bambuko |
Posted - 28/08/2018 : 09:46:57 We have concentrated so far on looking at NMEA logs to see if there was a problem...
I looked at runtime log to try to understand the mystery of two NMEA logs and 2080 date.
quote:
[000014138] . Device A is <BlueFlyVario> Port=/dev/ttymxc0 [000014139] . ComPort 1 Initialize </dev/ttymxc0> speed=115200 bit=8 [000014141] . ComPort 1 Init </dev/ttymxc0> end OK [000014144] . Device B is DISABLED. [000014145] . Device C is DISABLED. [000014145] . Device D is DISABLED. [000014146] . Device E is DISABLED. [000014146] . Device F is DISABLED. [000014148] . ComPort 1 ReadThread : started [000014701] . LK Battery Manager V1 started, current charge=84% [000015119] . GCE_STARTUP_REAL [000015120] . ProgramStarted=NormalOp h8:11:07 (NO FIX) [000015122] . Free ram=420076 K storage=2935872 K [000015619] . LoadTask : </mnt/onboard/LK8000/_Tasks/Default.lkt> [000024119] ... GPS baro source back available h8:11:07 (NO FIX) [000024605] . First GPS DATE: 2080-1-5 h8:11:07 (NO FIX) [000036938] . Change GPS DATE: 2080-1-7 h23:59:55 (NO FIX) [000058954] . Change GPS DATE: 2018-8-6 h19:14:59 (NO FIX) [000059917] . First GPS DATE: 2018-8-6 h19:14:59 (NO FIX) [000060902] . First GPS DATE: 2018-8-6 h19:14:59 (NO FIX) [000130882] . AutoQNH: setting QNH to HOME waypoint <Talgarth> altitude=296 m [000309834] . Entering shutdown h19:19:09 (UTC 19:19) [000310996] . Save history to </mnt/onboard/LK8000/_Configuration/History.txt> [000310997] . SaveRecentList: saved 1 recent waypoints [000311280] . SaveTask : saving </mnt/onboard/LK8000/_Tasks/Default.lkt> [000311438] . Stop COM devices [000311439] . ComPort 1 ReadThread : terminated [000311554] . Settings for 917 airspaces saved to file </mnt/onboard/LK8000/_Airspaces/AspConfig.LK> [000311566] . CloseLKAirspace [000311567] . ComPort 0: status=1 Rx=597727 Tx=6 ErrRx=0 ErrTx=0 [000311567] . ComPort 1: status=1 Rx=0 Tx=0 ErrRx=0 ErrTx=0 [000311568] . ComPort 2: status=1 Rx=0 Tx=0 ErrRx=0 ErrTx=0 [000311568] . ComPort 3: status=1 Rx=0 Tx=0 ErrRx=0 ErrTx=0 [000311569] . ComPort 4: status=1 Rx=0 Tx=0 ErrRx=0 ErrTx=0 [000311569] . ComPort 5: status=1 Rx=0 Tx=0 ErrRx=0 ErrTx=0 [000311570] . Finished shutdown h19:19:12 (UTC 19:19) [000311571] . WndMain::OnDestroy [000005896] ...Loading default Sound Table :
Perhaps there are some clues? |
FlyingAl |
Posted - 26/08/2018 : 23:31:50 I have posted a new knowledge base article about how to change the data rate between the GPS and the Bluefly here:
https://www.blueflyvario.com/knowledgebase/change-the-blueflyvario_ttl_gps_v12-gps-data-rate/ |
bambuko |
Posted - 26/08/2018 : 10:20:27 Yes, I did have GPS fix.
I can experiment with a GPS module and kobo. I have VK2828U7G5LF (GPS/GLONASS) which afaik is similar to the one used on BlueFly vario V12. Let's see whether I get similar logs and date problems? |
AlphaLima |
Posted - 25/08/2018 : 23:40:16 I'm not saying you did something wrong. All I can say the the logfile has a timestamp of a far future. This was probably caused by a wrong/corrupt NMEA stream. Yes the date is set by the GPS. Did you have a GPS fix?
|
bambuko |
Posted - 22/08/2018 : 20:03:47 No, I didn't create the log in May. The only testing I have done was in August. These two log files were created in one run on the August 13th (i.e. LK creates two logs, one with correct date and another with the weird 2080 date).
I still don't understand why? Unless it is something to do with it being GPS/Glonass, rather than (as previously) only GPS??? Don't know?
quote: ...Looks like your date setting was wrong...
are you saying that I did something wrong? or are you saying that something else is wrong? date is set by gps? |
AlphaLima |
Posted - 22/08/2018 : 19:17:12 So you created a log on 1st of May ??? Looks like your date setting was wrong. |
bambuko |
Posted - 22/08/2018 : 16:58:31 quote: Originally posted by AlphaLima
You wrote you sent the wrong file...
Sounds like we misunderstood each other... After sending you the log,I have noticed, that LK actually produces two logs one dated 2080 and another dated 2018. For example (from the latest test I have run): NMEA_2018-08-13-19-02-55.txt and NMEA_2080-01-05-23-59-52.txt
I don't know or understand the significance of having two logs? rather than just one (perhaps you can explain?)
I only have one log (i.e. 2080) and that is the one I have sent to you. I didn't say this was the wrong one, just that it was one of the two.
The best way to do this job would be to have spare BlueFly vario to experiment with, but the one I have, is soldered to the kobo and in the glider and now works fine (with different internal baud rate), so clearly not keen to take it all apart again.
I have spare kobo to play with, but no spare Bluefly vario, so I guess, unless you find anything interesting in the log I have sent you, or until we have the hardware to play with, the question will remain un-resolved.... |
AlphaLima |
Posted - 22/08/2018 : 12:19:37 You wrote you sent the wrong file, but did not send the correct one, so far! |
bambuko |
Posted - 21/08/2018 : 18:38:36 It is as far as I am concerned - has been working OK, since the changes described here. Didn't get any comments from AlphaLima yet, so don't know if there is anything obvious in LK8000 NMEA log? I will be using it (as soon as the weather gets better) and obviously will report if there are any problems... |
Aleksandar |
Posted - 21/08/2018 : 16:18:01 Any new information, is it V12 work stabile? |
bambuko |
Posted - 13/08/2018 : 20:42:32 Posted |
AlphaLima |
Posted - 13/08/2018 : 20:30:53 Please send the NMEA Log to AlphaLima (at) lk8000 (dot) it |