I am proud to present version six of the BTOA and downloader for you to try!

There are some significant changes, least of which is an installer for Windows as well as a .app package for Mac. Unfortunately, the Linux version cannot yet flash the BTOA.

Please let me know how they work for you before I post them in the OP!

Thank you
Adrian

Version 6 works! I'll get the new version of F3K master going in the AM

Connecting to serial port /dev/tty.usbserial-AD020FTF, 115200N2 (please wait) ...
BTOA: V5.0
Build: Wed Jul 16 19:16:00 2014
Data: V1
Settings: V6
Interval: 500
Battery: not setup
Also log: Vario

Flashing altimeter firmware ...

avrdude: AVR device initialized and ready to accept instructions
avrdude: Device signature = 0x1e950f
avrdude: reading input file "firmware/blank_eeprom.hex"
avrdude: writing eeprom (1024 bytes):
avrdude: 1024 bytes of eeprom written
avrdude: verifying eeprom memory against firmware/blank_eeprom.hex:
avrdude: load data eeprom data from input file firmware/blank_eeprom.hex:
avrdude: input file firmware/blank_eeprom.hex contains 1024 bytes
avrdude: reading on-chip eeprom data:
avrdude: verifying ...
avrdude: 1024 bytes of eeprom verified
avrdude: reading input file "firmware/editions/FirmwareV6.hex"
avrdude: writing flash (30592 bytes):
avrdude: 30592 bytes of flash written
avrdude: verifying flash memory against firmware/editions/FirmwareV6.hex:
avrdude: load data flash data from input file firmware/editions/FirmwareV6.hex:
avrdude: input file firmware/editions/FirmwareV6.hex contains 30592 bytes
avrdude: reading on-chip flash data:
avrdude: verifying ...
avrdude: 30592 bytes of flash verified

avrdude done.  Thank you.

Rebooting altimeter ...
Connecting to serial port /dev/tty.usbserial-AD020FTF (please wait) ...
BTOA: V6.0
Build: Sat Dec 13 00:50:02 2014
Data: V1
Settings: V7
Interval: 500
Battery: not setup
Also log: Vario
Remaining: 14.20 hour(s)
Entries: 28780

Reboot finished.
Erasing altimeter (please wait) ...
Done...

Wiping settings memory ...
Firmware upgrade done - reconnecting ...
Connecting to serial port /dev/tty.usbserial-AD020FTF (please wait) ...
BTOA: V6.0
Build: Sat Dec 13 00:50:02 2014
Data: V1
Settings: V7
Interval: 500
Battery: not setup
Also log: Vario
Remaining: 18.20 hour(s)
Entries: 0

Connected.
Loading settings from altimeter ...
Done.
Writing settings to altimeter ...
$$$SY,0000
---
Done...

Connecting to serial port /dev/tty.usbserial-AD020FTF (please wait) ...
BTOA: V6.0
Build: Sat Dec 13 00:50:02 2014
Data: V1
Settings: V7
Interval: 500
Battery: not setup
Also log: Battery 2
Remaining: 18.20 hour(s)
Entries: 0

Reboot finished.
Verifying settings ...
Loading settings from altimeter ...
Done.
Error verifying altimeter settings. Please try saving again.
Erasing altimeter (please wait) ...
Done...

Loading settings from altimeter ...
Done.

Adrian,

Thanks very much for your patience, I braved the rain and wind for few throws today.
For what it's worth, test version of F3K master would not connect, current version did fine.

Very cool app!

Anyone know why the start altitude drifted up during a 30 flying session?

Could just be atmospheric conditions changing.
If you analyze for launches it will remove the variations, re-zeroing each launch.

There was a front passing, the Analyze feature is Money... I'm a fan

I flew a couple hours today with V6 and the test F3K Master today. Had some strangeness going on. It would read out launches in meters but say feet, at least I hope I can throw over 55 feet.... Also was reporting my 1s Lipo at 58 volts.

When I got home I checked the settings and my height unit default had gotten changed as had the battery monitor calibration and logging interval. I may have done it by mistake when looking at the settings screen on the phone but I don't think so and it was for sure not intentional.

Question what's recommended for the "switch positions"? I've got mid as output launch height and on as output over bluetooth. What I'd like to do is just be able to flip the switch and get the launch height and battery volts but it seems I need the output over bluetooth option selected in one of them.

Thanks, Rj

Are you looking for phone readouts or just to listen to the beeps at different switch positions? Have not tried 6 yet, but I have mine set to beep the battery voltage & max launch height. With my poor hearing, I need to hold the nose of the fuse close to my ear to hear the beeps.

BP

Originally Posted by rdjay

I flew a couple hours today with V6 and the test F3K Master today. Had some strangeness going on. It would read out launches in meters but say feet, at least I hope I can throw over 55 feet.... Also was reporting my 1s Lipo at 58 volts.

When I got home I checked the settings and my height unit default had gotten changed as had the battery monitor calibration and logging interval. I may have done it by mistake when looking at the settings screen on the phone but I don't think so and it was for sure not intentional.

Question what's recommended for the "switch positions"? I've got mid as output launch height and on as output over bluetooth. What I'd like to do is just be able to flip the switch and get the launch height and battery volts but it seems I need the output over bluetooth option selected in one of them.

Thanks, Rj

Rick, it sounds like your settings got corrupted at some point. Only thing to do is fix them like you have!

I use the switch positions for output over bluetooth and output battery voltage or sometimes launch height. All output over bluetooth does is repeat the message sent to the android. The others are to beep out the values on the BTOA itself.

PS, your logged data will be unaffected with the exception of the voltage.

Yes, the log looked fine, except the voltage.

Understood, output over bluetooth will repeat message, that's really what I want as it has launch height and voltage and sometimes I miss it when it reads out at landing.

Thanks for the help. Hopefully next weekend the weather will cooperate again like these last two days and I can get more flying in!

Rj

I see a big difference between the log of flight times kept on my mobile from the one generated by the analysis through the BTOA application. I see there's a threshold range that if i change then the length of the flight changes drastically. Has anyone determined how to go along with this landing threshold? TIA for any hint.

Use the threshold that creates the desired results as close as possible to what you believe is correct. It will never be exact since the only way it can judge the end of a flight is by the altitude.

For instance, ground skimming will trigger the end of the flight but the flight actually lasted significantly longer.

In the future, we may be able to look at the g-sensor data to determine the end of flight more accurately.

Has anyone had any problems with the new version?