tag:blogger.com,1999:blog-40786764724818446532024-03-21T17:33:20.212-07:00Blue Fly Vario developmentA chronicle of the development of the BlueFlyVario.
<a href="http://blueflyvario.com/">Visit the website to order and for support.</a> Flying Alhttp://www.blogger.com/profile/04770253154348277404noreply@blogger.comBlogger121125tag:blogger.com,1999:blog-4078676472481844653.post-14598314930288373222024-02-03T00:25:00.000-08:002024-03-02T12:55:25.901-08:00Minor firmware update M72 and M73<p><b>M72 and M73 Firmware Update (v22 and v23 models)</b></p><p><br /><i><b>Update 2 Mar 2024</b>: The M72 firmware update for Bluetooth GPS_IGC models had a bug which sometimes made the vairo hang when the bluetooth connection was lost. Please use the most recent M73 firmware update for these models:</i></p><ul><li>v23 Models:</li><ul><li>Bluetooth_GPS_IGC - <a href="https://blueflyvario.com/files/v22/BTH_GPS_IGC_23.1.573.hex">BTH_GPS_IGC_23.1.573.hex</a></li></ul><li>v22 Models:</li><ul><li>Bluetooth_GPS_IGC - <a href="https://blueflyvario.com/files/v22/BTH_GPS_IGC_22.2.573.hex">BTH_GPS_IGC_22.2.573.hex</a></li></ul></ul><p></p><p>This minor firmware update improves the reliability of vario shutdown and reduces the instance of the Bluefly becoming unresponsive. </p><p>The firmware files are here:</p><div><ul><li>v23 Models:</li><ul><li>Bluetooth - <a href="https://blueflyvario.com/files/v22/BTH_USB_23.1.472.hex">BTH_USB_23.1.472.hex</a></li><li><strike>Bluetooth_GPS_IGC - <a href="https://blueflyvario.com/files/v22/BTH_GPS_IGC_23.1.572.hex">BTH_GPS_IGC_23.1.572.hex</a></strike></li></ul><li>v22 Models:</li><ul><li>Bluetooth - <a href="https://blueflyvario.com/files/v22/BTH_USB_22.2.472.hex">BTH_USB_22.2.472.hex</a></li><li><strike>Bluetooth_GPS_IGC - <a href="https://blueflyvario.com/files/v22/BTH_GPS_IGC_22.2.572.hex">BTH_GPS_IGC_22.2.572.hex</a></strike></li><li>TTL_GPS - <a href="https://blueflyvario.com/files/v22/TTL_GPS_22.2.272.hex">TTL_GPS_22.2.272.hex</a></li><li>USB_TTL_GPS_IGC - <a href="https://blueflyvario.com/files/v22/USB_TTL_GPS_IGC_22.2.672.hex">USB_TTL_GPS_IGC_22.2.672.hex</a></li></ul></ul></div><p></p>Follow the firmware update procedures described in <a href="http://blueflyvario.blogspot.com/2022/07/firmware-updates-for-v22-models.html">this earlier blog post</a>. I recommend resetting default settings and formatting IGC memory after you have done a firmware update. Flying Alhttp://www.blogger.com/profile/04770253154348277404noreply@blogger.comtag:blogger.com,1999:blog-4078676472481844653.post-13370709596955325892023-12-28T23:58:00.000-08:002023-12-29T18:10:49.615-08:00IGC Validation and New Firmware<p>It has been while since my last update. A few things have been happening behind the scenes. This post announces IGC validation for the Bluefly and describes the latest firmware and software. </p><table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto;"><tbody><tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgwRsNiFp7WOu9NQxrOlkG0HG6ijIM-F_S_h47_i5s115LmlHm-by5jMWZG3QpqBtAnXXpQe-l8NVT_A1pIPN-JxVNupuqDqeJbpnCuDsowy8xRirLOLS6mrBmsVoQ_Jx4IMt5PnSDBhODtcuqgZZXRvEl-CHjyPMW-V7Atn8rvVW2b1PlfE52XygxNd3H0/s2040/Bluefly_v23%20flying.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" data-original-height="1536" data-original-width="2040" height="482" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgwRsNiFp7WOu9NQxrOlkG0HG6ijIM-F_S_h47_i5s115LmlHm-by5jMWZG3QpqBtAnXXpQe-l8NVT_A1pIPN-JxVNupuqDqeJbpnCuDsowy8xRirLOLS6mrBmsVoQ_Jx4IMt5PnSDBhODtcuqgZZXRvEl-CHjyPMW-V7Atn8rvVW2b1PlfE52XygxNd3H0/w640-h482/Bluefly_v23%20flying.jpg" width="640" /></a></td></tr><tr><td class="tr-caption" style="text-align: center;"></td></tr></tbody></table><p><b>IGC Validation</b></p><p>I am happy to announce that validation of Bluefly XBF signed files is now officially supported by the <a href="http://vali.fai-civl.org/">FAI-CIVL open validation server</a>. Validation for IGC files is required for some competitions, and importantly for many of us is used by XCContest. </p><p>A few years ago some models of the Bluefly got IGC tracklog recording. But until October this year the only way to validate to the file was to download it via GPS Dump as described in this <a href="https://blueflyvario.blogspot.com/2021/07/bluefly-igc-validation.html">post</a>. </p><p>For the technically minded, the IGC signing process is handled in the hardware. The IGC file data is stored in onboard NOR Flash memory using a proprietary file format as the $GPGGA and $GNGGA sentences are read from the onboad GPS and processed into B records. The IGC file is signed on the Bluefly using the XBF protocol when recording has stopped (when the Bluefly is shut down).</p>The Bluefly IGC file can be downloaded using the BFVDesktop application available from <a href="https://www.blueflyvario.com/software/">https://www.blueflyvario.com/software/</a> using the procedure describe in <a href="https://blueflyvario.blogspot.com/2021/06/blueflyvariobluetoothgpsigcv123-released.html">this post</a>. Users can connect the Bluefly to a PC and it appears as a serial port. The BFVDesktop application communicates with the Bluefly using commands over the serial port, including commands to list files and download them individually. Users can also format the NOR Flash memory.<br /><p>The following models include IGC recording. These are all based on the same codebase and use the same IGC format and memory protocol, with the relevant updates to the IGC header to reflect hardware and firmware versions.<br /></p><ul style="text-align: left;"><li>BlueFlyVario_Bluetooth_GPS_IGC_v23 (current model released May 2023)</li><li>BlueFlyVario_USB_TTL_GPS_IGC_v22 (current model released May 2022)</li><li>BlueFlyVario_Bluetooth_GPS_IGC_v22 (previous model released May 2022)</li><li>BlueFlyVario_Bluetooth_GPS_IGC_v12.3 (previous model released June 2021)</li></ul>If you want to do validation separately from the open validation server you can download <a href="https://blueflyvario.com/files/vali-xbf.exe">vali-xbf.exe</a>.<br /><br /><b>M70 Firmware Update (v22 and v23 models)</b><p></p><p>I have also recently completed testing new firmware for the v22 and v23 models. I only recommend updating firmware if there is a new feature you want to try or if you are not happy with the performance of your vario. </p><p>The key changes are:</p><ul style="text-align: left;"><li>Updated the $XCTOD sentence used to send voltage and temperature data from the Bluefly to XCTrack</li><ul><li>Adds a checksum to make it more robust (<a href="https://blueflyvario.blogspot.com/2022/10/more-firmware-updates-x66.html">see here</a> for more explanation). </li><li>Fixes a battery voltage error from some firmware versions. </li></ul><li>Added a new <i>beepDutyCycle </i>hardware setting. You might want to use this to change the nature of the Bluefly beeps, or perhaps to prolong the battery life. </li><ul><li>By default when the Bluefly beeps in lift the ratio of beep to silence is 1:1. </li><li>It beeps faster when you go up, but still the length of the beep and silence is the same. </li><li>By adjusting the beep duty cycle you can shorten the beep to silence ratio. </li><li>Start by experimenting with the setting at 0.5 or 0.25.</li></ul><li>Rebuilt the IGC Flash memory writing code. </li><ul><li>For some combination of device and Bluefly there were intermittent errors associated with the periodic writing of track data to the onboard flash memory. </li><li>Flash writing tasks now run in the background. </li></ul></ul><div>The firmware files are here:</div><div><ul style="text-align: left;"><li>v23 Models:</li><ul><li>Bluetooth - <a href="https://blueflyvario.com/files/v22/BTH_USB_23.1.470.hex">BTH_USB_23.1.470.hex</a></li><li>Bluetooth_GPS_IGC - <a href="https://blueflyvario.com/files/v22/BTH_GPS_IGC_23.1.570.hex">BTH_GPS_IGC_23.1.570.hex</a></li></ul><li>v22 Models:</li><ul><li>Bluetooth - <a href="https://blueflyvario.com/files/v22/BTH_USB_22.2.470.hex">BTH_USB_22.2.470.hex</a></li><li>Bluetooth_GPS_IGC - <a href="https://blueflyvario.com/files/v22/BTH_GPS_IGC_22.2.570.hex">BTH_GPS_IGC_22.2.570.hex</a></li><li>TTL_GPS - <a href="https://blueflyvario.com/files/v22/TTL_GPS_22.2.270.hex">TTL_GPS_22.2.270.hex</a></li><li>USB_TTL_GPS_IGC - <a href="https://blueflyvario.com/files/v22/USB_TTL_GPS_IGC_22.2.670.hex">USB_TTL_GPS_IGC_22.2.670.hex</a></li></ul></ul></div><p></p>Follow the firmware update procedures described in <a href="http://blueflyvario.blogspot.com/2022/07/firmware-updates-for-v22-models.html">this earlier blog post</a>. I recommend resetting default settings and formatting IGC memory after you have done a firmware update. <div><br /></div><div><b>BFVDesktop application updated</b></div><div><br /></div><div>You can also get the latest BFVDesktop application here: <a href="https://blueflyvario.com/files/BFVDesktop0.87.zip">https://blueflyvario.com/files/BFVDesktop0.87.zip</a>. This includes:</div><div><ul style="text-align: left;"><li>The new <i>beepDutyCycle </i>setting.</li><li>An included run.sh script for running the application on Mac OS. You should read <a href="https://www.blueflyvario.com/knowledgebase/using-the-bfvdesktop-application-on-macos/">this knowledge base article</a> for more information. </li></ul></div>Flying Alhttp://www.blogger.com/profile/04770253154348277404noreply@blogger.comtag:blogger.com,1999:blog-4078676472481844653.post-2092306603332221352023-05-27T20:37:00.007-07:002023-05-27T20:52:01.458-07:00BlueFlyVario v23 models released<p>Today we announce the release of two new Bluefly v23 models. These have actually been shipping for a few weeks now. The BlueFlyVario_Bluetooth_v23 is the latest version of the classic Bluefly. The BlueFlyVario_Bluetooth_GPS_IGC_v23 includes an onboard GPS and IGC tracklog recording. </p><table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto;"><tbody><tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi5WteY_H3SgpbJ1hfUlB7HcDjDoJehjCFs-7LynpAokJ8edwjprq4cn5RabtXBYc0YKyDeIVNXEItvSzEpzrrMiiBSJzSAZZCfBb-XbGBxtonYb3xIifmdFAKlQfC8pCv6wx4BrLyBGS6l99V3g_QOJ4O_Ek0xgpbWCzGJHhrv2za7alDiXcnYqYw2Sw/s4080/PXL_20230528_030516124%5B1%5D.jpg" style="margin-left: auto; margin-right: auto; text-align: center;"><img border="0" data-original-height="3072" data-original-width="4080" height="482" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi5WteY_H3SgpbJ1hfUlB7HcDjDoJehjCFs-7LynpAokJ8edwjprq4cn5RabtXBYc0YKyDeIVNXEItvSzEpzrrMiiBSJzSAZZCfBb-XbGBxtonYb3xIifmdFAKlQfC8pCv6wx4BrLyBGS6l99V3g_QOJ4O_Ek0xgpbWCzGJHhrv2za7alDiXcnYqYw2Sw/w640-h482/PXL_20230528_030516124%5B1%5D.jpg" width="640" /></a></td></tr><tr><td class="tr-caption" style="text-align: center;">The new Bluefly v23 models look the same.</td></tr></tbody></table><p><b>What is new?</b></p><p>These models are an evolution of the v22 models. The main processor is the same and the firmware is almost exactly the same as the v22. Firmware updates will continue to be made for both v22 and v23. </p><p>The main changes are:</p><p></p><ul style="text-align: left;"><li>USB-C charging and serial port interface. The shift from micro-USB to USB-C reflects the standard most devices are adopting, and the physical port is more robust. </li><li>The GPS version now uses the L96 GPS module instead of the XA1110. The latter is no longer available and the L96 has better performance, in my experience. </li><ul><li>The good news is that the GPS is now entirely inside the case - no more protruding antenna.</li><li>The downside to this GPS module is that the chip antenna is very sensitive to placement of other components. This was overcome in the v23 model by putting the GPS module on a small board and raising it just a few mm further away from the battery. The end result is a much cleaner layout, albeit that the manufacturing time per device is a bit longer. </li></ul></ul><table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto;"><tbody><tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhbv-AtxBCpCO9mHQM1zA2KNT4odVNgs75h8_G3nX76duL9LpcGoU5vkz7v2CZKt7_s0xC6fsm7NebgLEfXznqdoWFRXFQ71PKAc3-4e6PDZolzUcws9RkDd_yTn5WppmTjS1wVcmhcTwFYLfKSju-UbW1MYAwiDjLHPAxr_Q2vudDF3wJMEnZtsNtCMA/s4080/BlueFlyVario_Bluetooth_GPS_IGC_v23_shield.jpg" style="margin-left: auto; margin-right: auto;"><img border="0" data-original-height="3072" data-original-width="4080" height="482" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhbv-AtxBCpCO9mHQM1zA2KNT4odVNgs75h8_G3nX76duL9LpcGoU5vkz7v2CZKt7_s0xC6fsm7NebgLEfXznqdoWFRXFQ71PKAc3-4e6PDZolzUcws9RkDd_yTn5WppmTjS1wVcmhcTwFYLfKSju-UbW1MYAwiDjLHPAxr_Q2vudDF3wJMEnZtsNtCMA/w640-h482/BlueFlyVario_Bluetooth_GPS_IGC_v23_shield.jpg" width="640" /></a></td></tr><tr><td class="tr-caption"><div style="text-align: center;">BlueFlyVario_Bleutooth_GPS_IGC_v23 internals, showing GPS module antenna slightly above the base board.</div></td></tr></tbody></table><b>What is in the box?</b><br /><br />Both models are shipped fully assembled and ready to use. Simply remove the tape and cover protecting the clear button, press the button and your vario should come to life. Some tips:<br /><ul><li>See here for an explanation of the beeps and lights: <a href="https://www.blueflyvario.com/knowledgebase/explain-the-button-lights-and-beeps/">https://www.blueflyvario.com/knowledgebase/explain-the-button-lights-and-beeps/</a></li><li>Plug in USB-C cable to a charger or a computer. The red light indicates charging. </li><li>Connect it to your Android (<a href="https://www.blueflyvario.com/knowledgebase/trouble-connecting-bluetooth/">https://www.blueflyvario.com/knowledgebase/trouble-connecting-bluetooth/</a>) or iOS device (<a href="https://www.blueflyvario.com/knowledgebase/connecting-ios-bluetooth/">https://www.blueflyvario.com/knowledgebase/connecting-ios-bluetooth/</a>).</li><li>For the GPS model, you should leave it on and sitting outside with a clear view of the sky until you get a GPS fix and the orange light flashes. That might take 5 to 10 minutes in a new part of the world or if you have not used it for a long time.</li><li>Consider connecting to the BFVDesktop application to adjust the settings. I do not think this is necessary for most pilots - I have chosen settings which I think work best.</li><li>You might want to add some velcro to secure it to your flight deck or a lanyard (<a href="https://www.blueflyvario.com/knowledgebase/adding-a-lanyard/">https://www.blueflyvario.com/knowledgebase/adding-a-lanyard/</a>)</li></ul> <p></p>Flying Alhttp://www.blogger.com/profile/04770253154348277404noreply@blogger.comtag:blogger.com,1999:blog-4078676472481844653.post-79917840813763563592023-02-06T11:58:00.007-08:002023-02-06T11:58:58.152-08:00Firmware Update x68<p>The latest firmware for all v22 models has been <a href="https://www.blueflyvario.com/files/v22/">uploaded</a>. </p><p>Changes include:</p><p></p><ul><li>Fixed a bug with button performance. The button was not as responsive to a press as it should be during lift or sink. </li><li>Fixed a bug for GPS models that very occasionally interleaved the PRS and B Record sentence, which might have caused issues for XCTrack users who configured to use external GPS. </li></ul><p></p><p>Follow the firmware update procedures described in <a href="http://blueflyvario.blogspot.com/2022/07/firmware-updates-for-v22-models.html">this earlier blog post</a>. </p>Flying Alhttp://www.blogger.com/profile/04770253154348277404noreply@blogger.comtag:blogger.com,1999:blog-4078676472481844653.post-23140590762421030202022-10-08T00:30:00.003-07:002022-10-08T14:50:21.275-07:00More firmware updates x66<p>The latest firmware for all v22 models has been <a href="https://www.blueflyvario.com/files/v22/">uploaded</a>. </p><p>Changes include:</p><p></p><ul style="text-align: left;"><li>Fixed a significant bug with IGC file recording which was inadvertently introduced in x63 firmware for the models which include IGC memory. If you update to this new x66 firmware make sure to clear your IGC memory by formatting it through the BFVDesktop application.</li><li>The <span style="color: #2b00fe;">$XCTOD,Battery%,TempDegC*</span> sentence was added some time ago to improve integration with XCTrack, but I think this is the first time I have documented it. </li><ul><li>The sentence is sent from the BlueFly once every ten seconds. </li><li>This allows you to add widges in XCTrack for Bluefly battery percent and Bluefly Temperature in Degrees C (as measured by the pressure sensor).</li><li><a href="https://xctrack.org/XCTrackOpenData.html">See here</a> for how to use this.</li></ul><li>Minor bug fixes with output text processing. </li><li>Little tweaks to improve shutdown performance. </li></ul><p></p><p>Follow the firmware update procedures described in <a href="http://blueflyvario.blogspot.com/2022/07/firmware-updates-for-v22-models.html">this earlier blog post</a>. </p>Flying Alhttp://www.blogger.com/profile/04770253154348277404noreply@blogger.comtag:blogger.com,1999:blog-4078676472481844653.post-59539957972255105812022-08-20T01:25:00.100-07:002022-08-20T15:02:04.221-07:00Kobo Nia Install<p>This post outlines how to install the <a href="http://blueflyvario.blogspot.com/2022/05/blueflyvariousbttlgpsigcv22-and.html">BlueFlyVario_USB_TTL_GPS_IGC_v22</a> on the Kobo Nia. This combination of the best TTL_GPS Bluefly and the cheapest current model Kobo will give you a fully featured xcsoar based flight instrument. </p><p>Make sure you read to the end of the post before you begin. The Nia makes a good flight instrument, but there are some limitations.</p><p>There are many other models of Kobo and many ways to install a Bluefly. See <a href="http://blueflyvario.blogspot.com.au/2016/07/kobo-glo-hd-install.html">BlueFlyVario_TTL_GPS_v11 Assembly with the Kobo Glo</a> for an example and links to many other blog posts for other models. Also, see Nev’s page for much more information: <a href="http://gethighstayhigh.co.uk/kobo-self-build/">http://gethighstayhigh.co.uk/kobo-self-build/</a>.</p><p><b>Preparation</b></p><p style="text-align: left;">Order your Bluefly from the <a href="https://www.blueflyvario.com/product-category/variometers/">shop</a>. This assembly shows the USB_TTL_GPS_IGC model, but you could also use the cheaper TTL_GPS model. The main advantage of the more expensive model is onboard IGC recording and easier Bluefly firmware upgrades. </p><p style="text-align: left;">Get a Kobo Nia from your local retailer or the internet. </p><p style="text-align: left;">Download a few things:</p><p style="text-align: left;"></p><ul style="text-align: left;"><li><a href="https://download.xcsoar.org/releases/">xcsoar</a>. The latest releases are not compatible with the Nia and at the time of writing this post you need to use a 6.8 version. I used <a href="https://download.xcsoar.org/releases/6.8.17/KOBO/">6.8.17</a>. </li><li>The <a href="https://www.thingiverse.com/thing:5461612">3d printable files </a>for the new v22 TTL_GPS case, lid and button. </li><ul><li>This is optional, but does make the install a bit neater. </li><li>I printed these items in PLA on an old 3d printer and there was a little clean up with a knife required to make them fit, especially around the button. </li></ul><li>Get this Bluefly.<a href="https://www.blueflyvario.com/files/Bluefly22.xci">xci file for the xcsoar menu</a>. </li></ul><div>Make sure you have the latest firmware update for the Bluefly. See <a href="http://blueflyvario.blogspot.com/2022/08/v22-ttlgps-firmware-updates.html">here</a>. </div><p></p><p><b>Prepare the Nia</b></p><p>Before anything, make sure you Nia is working normally as an ebook. Create a Kobo account, do the suggested firmware updates, then shut it down.</p><p>Take the back cover off the Nia. You should be able to pry it loose around the edge. It will look like this:</p><p></p><div style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/a/AVvXsEhLJqKHy_EdCGBr6FeGztNS9qkSgcmFswG3s0tCo42JFNRGJ5BctiKSnd74t51AuksQMY9uRM1QF4_qLfLKmpY_1NIrTu63HMx5b5YRp1nbe_jCljU9fk1OkK4SZF1vf3t-sXWUBPOBr2o8PfyYzlnT08g6baJUqPcn4FxntmCSzQUmzqVdT8PaLOFBiw"><img alt="" data-original-height="4000" data-original-width="2250" height="640" src="https://blogger.googleusercontent.com/img/a/AVvXsEhLJqKHy_EdCGBr6FeGztNS9qkSgcmFswG3s0tCo42JFNRGJ5BctiKSnd74t51AuksQMY9uRM1QF4_qLfLKmpY_1NIrTu63HMx5b5YRp1nbe_jCljU9fk1OkK4SZF1vf3t-sXWUBPOBr2o8PfyYzlnT08g6baJUqPcn4FxntmCSzQUmzqVdT8PaLOFBiw=w360-h640" width="360" /></a></div><br />Backup the sdcard by creating a full disk image with of it with win32diskimager. See step 3 <a href="http://gethighstayhigh.co.uk/kobo-self-build/">here</a>.<div><br /></div><div>Install xcsoar: replace the sdcard, start the kobo, connect a USB cable, in the kobo app press connect to show the drive on your computer, then copy KoboRoot.tgz as described in the <a href="https://www.xcsoar.org/download/">Kobo xcsoar installation instructions</a>. </div><div><br /></div><div><b>Install the Bluefly </b><br /><br /><div>I like to remove the couple of screws near the edge of the boar and pry up the PCB to keep it clear of the underlying metal when soldering. </div><div><p></p><p></p><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/a/AVvXsEg7TUhLKHxM2xOtjlG44Osl34eccp1cxJXkCZLf7UhwIdS4lZAv13jeY0neNg0ce6Jc1fmHVMcB6vpFgDH0lpAH_vl_1sFhSHxnj25VPxxU-dPaujTY6OBrWhRw9O12W7ISP70Wl0anS1i_wGr9-Usv3L2tnNwgjygLY6sfM2LOqIdhCduLJ-LWrK4r4w" style="margin-left: 1em; margin-right: 1em;"><img alt="" data-original-height="2250" data-original-width="4000" height="360" src="https://blogger.googleusercontent.com/img/a/AVvXsEg7TUhLKHxM2xOtjlG44Osl34eccp1cxJXkCZLf7UhwIdS4lZAv13jeY0neNg0ce6Jc1fmHVMcB6vpFgDH0lpAH_vl_1sFhSHxnj25VPxxU-dPaujTY6OBrWhRw9O12W7ISP70Wl0anS1i_wGr9-Usv3L2tnNwgjygLY6sfM2LOqIdhCduLJ-LWrK4r4w=w640-h360" width="640" /></a></div><br />Wires are soldered onto the TTL port. In this example I have used solid core 30AWG winding wire. Use a hot soldering iron but work quickly so you don't damage the PCB. Check carefully for jumped solder tracks. Note the small 3mm hole drilled through the bezel of the kobo that all of the wires go through. I could have made this smaller. <p></p><p></p><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/a/AVvXsEgi9stDawM6lgUsLRmIA_IjhNK8PJ97YrVEwL68JjielPQumlTpUCtb7RrHYl0U6P1RGSh477ppLTjfOXF3ozVP_3549sGMlHlt8MCrqUrJJMjYPgMeoARGR53y29YobnFNMmCbM6pbYLQMmxiodwmSGEvBsZDLbpNkYB0I8r4U8t-Bskg5E4LfczndTQ" style="margin-left: 1em; margin-right: 1em;"><img alt="" data-original-height="2250" data-original-width="4000" height="360" src="https://blogger.googleusercontent.com/img/a/AVvXsEgi9stDawM6lgUsLRmIA_IjhNK8PJ97YrVEwL68JjielPQumlTpUCtb7RrHYl0U6P1RGSh477ppLTjfOXF3ozVP_3549sGMlHlt8MCrqUrJJMjYPgMeoARGR53y29YobnFNMmCbM6pbYLQMmxiodwmSGEvBsZDLbpNkYB0I8r4U8t-Bskg5E4LfczndTQ=w640-h360" width="640" /></a></div><br />Solder each of the wires to the Bluefly. Make sure that the connections are:</div><div><ul style="text-align: left;"><li>Kobo GND - Bluefly GND</li><li>Kobo RX - Bluefly Tx</li><li>Kobo TX - Bluefly Rx</li><li>Kobo V - Bluefly V</li></ul><div>Put the neoprene on the pressure sensor of the Bluefly (black squishy side on the sensor - do not remove the sticky part or you will block the holes). Use the heatshrink to hold it in place (shrink with a hairdryer or hot air gun). </div><p></p><p></p><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/a/AVvXsEixxlcoZnJNJGeZzAhn7589Vpb0BaA9arjXfEv-tuB5SeRDJUL_h-wAvLUI1vdo0kXubq1lEQEZsY310Xe99_1aP7o3Z4fk25VLawoDoxnzb4FhRxnLzyMybxrD54JVC4_a9R56gbHgGp5D6UE4RzhQkslzISQmp-Ce73P97hjjfqFB8v_9l-82TksVBw" style="margin-left: 1em; margin-right: 1em;"><img alt="" data-original-height="2250" data-original-width="4000" height="360" src="https://blogger.googleusercontent.com/img/a/AVvXsEixxlcoZnJNJGeZzAhn7589Vpb0BaA9arjXfEv-tuB5SeRDJUL_h-wAvLUI1vdo0kXubq1lEQEZsY310Xe99_1aP7o3Z4fk25VLawoDoxnzb4FhRxnLzyMybxrD54JVC4_a9R56gbHgGp5D6UE4RzhQkslzISQmp-Ce73P97hjjfqFB8v_9l-82TksVBw=w640-h360" width="640" /></a></div><br /><div style="text-align: left;">The case is placed so it hangs over the edge of the kobo bezel (so the GPS antenna works). In this install I used quality black double sided tape to secure the case to the bezel. The final result is shown below. </div><div class="separator" style="clear: both; text-align: left;"><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiaISqFueMlM925UV6puCFY-6eRTWGxgzdc8eZz_5Usw-t3M7-XxZz_4nBtWKVaHwPMS3rb76lVFWr_ClZDbzvC8CkzszWi3fJwJsOimoFucdTxbW-TDENSBNgkx87zAJ0BH4gLvR9meUuosVALfYk0EtcoDRqXov-zz-bc-674V-N9c2UPgPTKMIKpCA/s3000/IMG_20220821_075045.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="3000" data-original-width="3000" height="640" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiaISqFueMlM925UV6puCFY-6eRTWGxgzdc8eZz_5Usw-t3M7-XxZz_4nBtWKVaHwPMS3rb76lVFWr_ClZDbzvC8CkzszWi3fJwJsOimoFucdTxbW-TDENSBNgkx87zAJ0BH4gLvR9meUuosVALfYk0EtcoDRqXov-zz-bc-674V-N9c2UPgPTKMIKpCA/w640-h640/IMG_20220821_075045.jpg" width="640" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><b>Configure XCSoar</b></div></div><div><b><br /></b></div><div style="text-align: left;">In the devices menu of xcsoar (Menu|Config|Devices) edit device A with the following settings:</div><div style="text-align: left;"><ul style="text-align: left;"><li>Port: ttymxc0</li><li>Baud rate: 115200</li><li>Driver: Bluefly</li></ul><div>Click Monitor to see the data flowing in from the Bluefly. It will take a few minutes of the vario sitting outside with a clear view of the sky and no interference to get a GPS fix. </div><div><br /></div><div>Quit xcsoar and at the boot menu press Nickel to boot to the Kobo erReader mode. Connect your the kobo to a computer and upload the Bluefly.xci file you downloaded earlier to the xcsoar directory. Disconnect the cable and reboot back to xcsoar. </div><div><br /></div><div>Back in xcsoar add the xci file to create the Bluefly menu (Menu|Config|System|Look|Language,Input|Events) (you will need to be using Expert mode). You will need to quit and restart xcsoar for it to take effect. </div><div><ul style="text-align: left;"><li>The xci file adds a bunch of menu options which send commands and settings to the Bluefly. </li><li>It also adds a special gce event which restarts the Bluefly when the xcsoar detects a landing. This forces the IGC file on the Bluefly to be saved. </li></ul><div>Now, Menu|Bluefly|Simulate Button to check it is working. This is the same as short pressing on the button of the Bluefly to toggle the sound on and off. </div></div><div><br /></div><div>Next, Menu|Bluefly|Bluefly Config then set outputMode to LX at 5Hz. </div><div><br /></div><div>Finally, Menu|Bluefly|Devices|Edit and change the driver to LXNAV. </div><div><br /></div><div>The reason for the last two steps is to send $LXWP0 messages from the Bluefly for alt and vario information (instead of the default Bluefly PRS output mode). It reduces the loads on the processor (I think). Also these sentences have a checksum so if the there is a transmission error you will not get funky altitude/vario information. </div><div><br /></div><div><b>Limitations of the Nia</b></div><div><b><br /></b></div><div>I really like the screen on the Nia. If you do the installation as described in this post then it will work for you, but there are some technical limitations that you should be aware of if you decide to do things a little differently:</div><div><ul style="text-align: left;"><li>There is not a specific version of xcsoar that has been built for the Nia. xcsoar kobo versions try to work out what model of kobo it is running on during startup then selects particular linux drivers and a bunch of other kobo linux things. The 6.8 versions work, and I expect that a future 7.x version will work, but at the moment suggested fixes have not been included in a release. </li><li>The underlying kobo linux operating system uses the ttl serial port we connect the Bluefly to during the device boot process. If it reads characters from the Bluefly at a critical point in the first few seconds then the boot will hang (this is why there is is nothing sent from the Bluefly until after startDelayMS). Additionally, there are around 2500 characters sent from the kobo to the Bluefly in the first 10 seconds. The most recent firmware on the Bluefly addresses both of these issues. </li><li>The kobo linux serial processing driver only has so much capacity and it is possible that from time to time there will be buffer overflows on the kobo side. Practically, this results in characters not being received by xcsoar. By using sentences with a checksum bad sentences are just ignored and we can recover gracefully. </li></ul></div><div><b>Further Steps</b></div><div><b><br /></b></div><div>While the Kobo is on, connect the Bluefly to the BFVDesktop application via USB-C cable. You should be able to see the data and configure many more settings on the Bluefly than are able to be set up from the xci file. The default startDelayMS is 2000, but for most users I recommend increasing this to 10000 to more fully avoid the start up process. You can also download igc files from the Bluefly using the BFVDesktop application or GPSDump. </div><div><br /></div><div>In addition, you should be able to download xcsoar's igc files from the Kobo eReader application when the kobo is connected to a computer.</div><div><b><br /></b></div><div>There is a lot more information on configuring XCSoar on the web, and Nev's page has <a href="http://gethighstayhigh.co.uk/xcsoar-tips/">great tips</a>. </div></div>Flying Alhttp://www.blogger.com/profile/04770253154348277404noreply@blogger.comtag:blogger.com,1999:blog-4078676472481844653.post-40513270380700820422022-08-12T18:59:00.005-07:002022-08-13T22:49:27.772-07:00v22 TTL_GPS firmware updates<p>This is just a quick post to announce new firmware has been release for the v22 TTL_GPS models:</p><p></p><ul style="text-align: left;"><li><a href="https://www.blueflyvario.com/files/v22/TTL_GPS_22.2.263.hex">https://www.blueflyvario.com/files/v22/TTL_GPS_22.2.263.hex</a></li><li><a href="https://www.blueflyvario.com/files/v22/USB_TTL_GPS_IGC_22.2.663.hex">https://www.blueflyvario.com/files/v22/USB_TTL_GPS_IGC_22.2.663.hex</a></li></ul><div>The update involves a pretty comprehensive rewrite of the serial data processing code to improve performance and remove some bugs. This was needed to ensure compatibility with the Kobo Nia and restore some functions on other Kobo models. The updates include:</div><div><ul style="text-align: left;"><li>The Bluefly was overwhelmed with data from the Kobo during startup, which switched off further command processing capacity. This has been fixed and the Bluefly should be responsive. </li><li>The Kobo startup code on some models was interfered with by the Bluefly. The startup procedure no sends not data from the Bluefly at all until after the startDelayMS time (default of 2 seconds after power on). </li><li>Other minor bug fixes including LX mode output, outputFrequency restoration and shutdown reliability. </li></ul><div>See <a href="https://blueflyvario.blogspot.com/2022/07/firmware-updates-for-v22-models.html">here </a>for firmware update procedures. </div></div><p></p>Flying Alhttp://www.blogger.com/profile/04770253154348277404noreply@blogger.comtag:blogger.com,1999:blog-4078676472481844653.post-61306701492720196132022-07-23T23:22:00.002-07:002022-08-12T18:33:54.387-07:00Firmware updates for v22 models<p>During the first six months of this year I released four new version 22 Bluefly models to complete the transition to a new processor. Read the earlier blog posts from 2022 to see what the changes are and for a more in depth description of each model. In this post I will describe the firmware update procedure for each model. There are some similarities with the v12 and earlier versions firmware update procedures, but from v22 onwards there is a custom version of ds30loader built just for the Bluefly. </p><p><b>Updated firmware<span> </span></b></p><p><span>From time to time I need to fix bugs or want to add new features to the Bluefly main application. There are some subtle differences between the firmware for each of the v22 models. </span></p><p><span>The software on the Bluefly processor includes a small ds30 bootloader and the main Bluefly application. When the processor reboots it first runs the bootloader program which checks to see if the ds30StudioPro program is trying to communicate with it. If the bootloader does not get the message, then it branches to the main application and the Bluefly will do it's thing. </span></p><p><span>At the time of this blog post the most recent versions of the firmware include bug fixes and minor updates. I recommend updating the firmware if you are having troubles, but for many pilots if you are happy with your Bluefly the way it is then updating the firmware is probably not needed. Fixes include:</span></p><p></p><ul style="text-align: left;"><li>Fixed a bug where the processor hangs unexpectedly. </li><li>Fixed a bug where the IGC memory is turned off too early during shutdown and IGC files were not being signed correctly. </li><li>Minor updates to default settings. </li><li>Other minor fixes. </li></ul><div>It is important you get the firmware built for your model. The most recent version of the v22 firmware will be uploaded here: <a href="https://www.blueflyvario.com/files/v22/">https://www.blueflyvario.com/files/v22/</a>. </div><div><br /></div><div>Note the numbering format: {MODEL_NAME}_{Hardware Version}.{Hardware Revision}.{Single Digit Model Code}{Two Digit Firmware Build Number}</div><div><b><br /></b></div><div><b>Tools to download</b></div><p></p><div>You will also need the ds30StudioPro program and the latest BFVDesktop application. Get them here:</div><div><ul><li style="margin-left: 15px;"><a href="https://www.blueflyvario.com/files/v22/ds30StudioPro.exe">https://www.blueflyvario.com/files/v22/ds30StudioPro.exe</a></li><li style="margin-left: 15px;"><a data-saferedirecturl="https://www.google.com/url?q=https://www.blueflyvario.com/files/BFVDesktop0.82.zip&source=gmail&ust=1658724960131000&usg=AOvVaw2DABc75yBk5rpCTFooX8P6" href="https://www.blueflyvario.com/files/BFVDesktop0.82.zip" style="color: #1155cc;" target="_blank">https://www.<wbr></wbr>blueflyvario.com/files/<wbr></wbr>BFVDesktop0.82.zip</a></li></ul><div>You will need a computer which can run windows applications, a USB cable (and only for the TTL_GPS model - a USB to Serial converter and some soldering skills) </div><div><b><br /></b></div><div><b>Firmware update procedure</b></div></div><p><span>The update procedure is similar for each model </span></p><b>Step 1: Make sure you have your power and connections right. </b><br /><ul style="text-align: left;"><li>BTH_USB and BTH_GPS_IGC models:</li><ul><li>Both of these models have the ds30 bootloader communicating through UART1, which is the micro USB port of the Bluefly. </li><li>Plug the Bluefly into your computer with a USB cable and make sure to note which COM port is listed. </li><li>You might want to connect to the BFVDesktop application just to make sure you know which COM port the Bluefly is installed as. Ensure that you shutdown the BFVDesktop application before trying to update the firmware - only one application can connect to the Bluefly at a time. </li><li>Shutdown the Bluefly by long pressing the button. </li><li><span style="color: #666666;">For bricked varios that are unresponsive to button presses there are additional instructions below. </span></li></ul><li>USB_TTL_GPS_IGC model:</li><ul><li>This model has the ds30 bootloader communicating through UART3, which is connected to the USB-C port of the Bluefly. </li><li>Plug the Bluefly into your computer with a USB cable and make sure to note which COM port is listed. </li><li>You will need to power this model, either by starting up the Kobo if it is connected to the TTL port of the Bluefly, or by temporarily closing the USB PWR lines (<span style="color: #ea9999;">note that if you are connected to a Kobo and you do this you will damage something - see the warning in the release blog post</span>). </li><li>Shutdown the Bluefly by long pressing the button. </li></ul><li>TTL_GPS model:</li><ul><li>This is quite a bit more involved. </li><li>You will need to solder a USB-Serial convertor to the UART 3 connection on the back. You really only need GND, Rx and Tx connected if you are already powering it from elsewhere (like the main TTL connection connected to a Kobo).</li><li>Shutdown the Bluefly by long pressing the button. </li></ul></ul><b>Step 2: Loading the firmware</b><div><ul style="text-align: left;"><li>Note that this will overwrite any hardware settings and they will be reset to defaults. </li><li>Open ds30StudioPro.</li><ul><li>On the Project tab: Select the Input HEX file*.hex file for the model you are updating.</li><li>On the Communication tab: Set the port to the one which you know from step 1 communicates with the Bluefly, and the baud rate is set at 115200.</li><li>On the Bootloader tab: Make sure the Write Destination is just the main flash and not the boot flash. </li></ul></ul><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiI3ADinU6ZGIGKhbCR_s3-8TxF8SNpzcdhbfk9nKfF7K-1fn30kXBTP25ZCmgWAXNxEbwJGhpY9QTweXg-F2i9faZJGxTkOFDUDO7HL8U4aIXgFDtyQLEQM3XK9J-ZOvKHp5NT69shJAfx2qfE_-7B1yVBYBlTiP6LyJUentzVRTFEEcO5Ckz9Lk70rQ/s863/ds30StudioPro.png" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="600" data-original-width="863" height="445" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiI3ADinU6ZGIGKhbCR_s3-8TxF8SNpzcdhbfk9nKfF7K-1fn30kXBTP25ZCmgWAXNxEbwJGhpY9QTweXg-F2i9faZJGxTkOFDUDO7HL8U4aIXgFDtyQLEQM3XK9J-ZOvKHp5NT69shJAfx2qfE_-7B1yVBYBlTiP6LyJUentzVRTFEEcO5Ckz9Lk70rQ/w640-h445/ds30StudioPro.png" width="640" /></a></div><ul style="text-align: left;"><li>Press the Write button</li><ul><li>This will start the ds30StudioPro looking for the bootloader on the vario. If the Bluefly main application is still running then you will get an error - the Bluefly needs to be shut down before you press the Write button. </li><li>Within a few seconds, press the button on the Bluefly to start it up. If everything works then the ds30bootloader on the Bluefly will communicate with the ds30StudioPro application, the firmware will start writing, and you will have new firmware in the vario in under a minute. </li><li>When the writing is finished the Bluefly should restart within about 10 seconds. </li><li>You might get a communications error because there are some buffers that need flushing in the UART communication pipeline - if so, then shut down the vario and try again. </li><li><span style="color: #666666;">For bricked varios: There is a special procedure for varios that are bricked (they are unresponsive to button presses to start up / shut down). For bricked varios you need to momentarily short MCLR and GND programming tabs to force a vario restart after pressing the Write button. </span></li></ul></ul><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjVAQo8u81RFUC11Lu_DTL9QHv62e37nCHXrhFeB2Jd78UMdRceXFiwtMHIbfGAlIqXTkmMjLCda3RLT1Wb_UmuePJo3DW7ARvgqt-ByP65L6Ytkg1ZYfegJXqVjJyp7wc2ZdQ-y3kRDHWduZA2rsdIY-8aHPJgdVB15mx_y7wdhSGr6Jr7iA0CVEenfg/s1280/v22mclr.png" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="720" data-original-width="1280" height="360" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjVAQo8u81RFUC11Lu_DTL9QHv62e37nCHXrhFeB2Jd78UMdRceXFiwtMHIbfGAlIqXTkmMjLCda3RLT1Wb_UmuePJo3DW7ARvgqt-ByP65L6Ytkg1ZYfegJXqVjJyp7wc2ZdQ-y3kRDHWduZA2rsdIY-8aHPJgdVB15mx_y7wdhSGr6Jr7iA0CVEenfg/w640-h360/v22mclr.png" width="640" /></a></div><br /><div><b>Step3: Testing and Settings</b></div></div><div><ul style="text-align: left;"><li>Before you disconnect everything, open up the BFVDesktop application and connect to the Bluefly again. </li><li>Look at the firmware version by restarting the Bluefly and seeing the strings in the opening lines. </li><li>Test two way communications by sending some commands or adjusting some settings. </li><li>For IGC models, you might want to press the IGC button and Format the IGC memory. The default settings would have started to overwrite the IGC files at the first sector of the memory. </li></ul><p><span><br /></span></p><p><br /></p><p><br /></p></div>Flying Alhttp://www.blogger.com/profile/04770253154348277404noreply@blogger.comtag:blogger.com,1999:blog-4078676472481844653.post-50322752356501950242022-05-29T23:04:00.000-07:002022-05-29T23:04:05.820-07:00BlueFlyVario_USB_TTL_GPS_IGC_v22 and BlueFlyVario_TTL_GPS_v22 released <p>The TTL_GPS model of the Bluefly is designed to add a vario and GPS to a Kobo running xcsoar by soldering it to an internal UART serial port. For technically savvy pilots this has been a popular way to build a powerful and reliable flight instrument. The previous TTL_GPS model was released in late 2021, but the chip crisis has meant that the main processor is no longer available. The new v22 TTL_GPS models use the same PIC32MM processor as the earlier v22 bluetooth models and share most of the same codebase. </p><p>Today I release two v22 TTL_GPS models: a base model BlueFlyVario_TTL_GPS_v22 to replace the v12.2 version released last year, and a new enhanced model BlueFlyVario_USB_TTL_GPS_IGC_v22 which adds a USB interface and onboard IGC memory recording. </p><p><b>Base Model BlueFlyVario_TTL_GPS_v22 Hardware Design</b></p><p>Most people installing the Bluefly on a Kobo will want this base model. It is cheaper and offers the same functionality as earlier versions. </p><p>The base model TTL_GPS_v22 is functionally very similar to the last v12.2 model. It has the same L96 GPS, shares the same form factor, and primary TTL_GPS pinouts. Most users will connect it to the Kobo via the UART 1 TTL port. Other noteworthy elements of the hardware design are:</p><p></p><ul style="text-align: left;"><li>It uses the new PIC32MM microcontroller as the other v22 models. </li><li>There is a new all metal button that is more robust, but still needs to be used carefully. Most users will not use the button as the vario powers on as soon as the TTL port has power from the Kobo. </li><li>On the back the RST and GND pads can be shorted while the vario is powered on to reset all settings to default. Make sure to deliberately power it off using the button to save the new settings. </li><li>There are a few ways to use V_Backup if you really think you need it, but I do not recommend connecting it or closing the solder jumper unless you have read the L96 datasheet and know what you are doing. </li><li>The programming pads are also connected to UART 2, which caries the serial communication from the microcontroller to the GPS. </li><li>The UART 3 pads on the back provide another TTL input/output like UART1. If I release firmware updates you will need to interface with these to update the firmware.</li><li>There are quite a few components not populated as the USB_TTL_GPS_IGC uses the same board. </li></ul><p></p><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh9v8oGUE5iJhDWPX7aPwV8He-mWpwPVa8QjZBHmKwot9rVuo8tmf4gl02Wr1Sj50i4Hrb8Kw1-SI-8enEzHRrFwKbpyyKIRWc-ZAEqxW7iqQadVBDjsycWifMfEmQmSTSeQJPNDC_6fTj-YKNxyHNuQHlccvv_EKFrf39uBk8iwusSEROBcUwsl5WWiQ/s960/Slide2.PNG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="720" data-original-width="960" height="480" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh9v8oGUE5iJhDWPX7aPwV8He-mWpwPVa8QjZBHmKwot9rVuo8tmf4gl02Wr1Sj50i4Hrb8Kw1-SI-8enEzHRrFwKbpyyKIRWc-ZAEqxW7iqQadVBDjsycWifMfEmQmSTSeQJPNDC_6fTj-YKNxyHNuQHlccvv_EKFrf39uBk8iwusSEROBcUwsl5WWiQ/w640-h480/Slide2.PNG" width="640" /></a></div><br /><p><b>Enhanced Model BlueFlyVario_USB_TTL_GPS_IGC_v22 Hardware Design</b></p><p>There are a few reasons why you might want the enhanced model:</p><p></p><ul style="text-align: left;"><li>The addition of onboard IGC recording means that you can record a signed IGC file while the vario is connected to your Kobo. You might use this for a backup, or even as your primary file. This is able to be downloaded via the USB port using the BFVDesktop application or GPSDump. Read earlier blog posts about the Bluetooth models to understand how IGC recording works on the Bluefly.</li><li>Some pilots might want to connect the Bluefly via the USB port to a windows or android device running xcsoar or xctrack. You can close the USB PWR header to enable the vario to be powered from the USB port. </li><ul><li>However, warning: <b><span style="color: red;">If you close this header and power the Bluefly from the USB-C interface while the Bluefly is connected to the Kobo, but the Kobo is powered down, then you will fry either the Kobo or the Bluefly.</span> </b>I recommend only closing this header if you do not intend to connect the Bluefly to a Kobo. </li><li>It is ok to have your Bluefly connected to and powered from the Kobo via UART 1, and then plug in a USB cable to the USB-C interface on the Bluefly (but with USB PWR not closed) This will allow you to transfer data from the Bluefly via the USB-C interface (adjusting the settings, downloading IGC files, updating firmware). </li></ul><li>Some pilots might want to use this model connected via a USB cable to an external battery to use as a stand alone vario without a display. You could solder a switch across USB_PWR. </li></ul><p></p><p>Like the base model, most users will connect it to a Kobo via the UART 1 TTL port. Other noteworthy elements of the hardware design are:</p><div><p></p><p></p><p></p><p></p><ul><li>The USB-C interface connected to UART 3 mirrors UART 1. </li><li>The USB power connection to V-Backup is only for advanced users that know how the L96 V_Backup works. </li></ul></div><p></p><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj2-0dZlhJa7GF4ciERyKdmq7tgH14y5_VzGs7S_oyrJ6dPypxBJ30LXYZ262qQdSWPe1wPLI8nxwM32LG28N0iRlN63b-516K22mhwua_Gc74-9yfNJSESqW2N4jHJhHvSKT78skb_9IXYHICiFlsEq6xCxLGpQc4j4QZWJw-H6MhOTJS6ahzFD0P4qQ/s960/Slide1.PNG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="720" data-original-width="960" height="480" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj2-0dZlhJa7GF4ciERyKdmq7tgH14y5_VzGs7S_oyrJ6dPypxBJ30LXYZ262qQdSWPe1wPLI8nxwM32LG28N0iRlN63b-516K22mhwua_Gc74-9yfNJSESqW2N4jHJhHvSKT78skb_9IXYHICiFlsEq6xCxLGpQc4j4QZWJw-H6MhOTJS6ahzFD0P4qQ/w640-h480/Slide1.PNG" width="640" /></a></div><br /><div><b>Firmware changes</b></div><p></p><p>The firmware builds on the earlier v22 models. It is functionally very similar to earlier versions. </p><p><b>What is in the bag</b></p><p>The bag for both models contains only vario module, a small piece of neoprene, and some heatshrink to hold the neoprene in place. </p><p>You will need to add your own wires and enclosure (if you want one).</p><p></p><p><b>Assembly</b></p><p>See the assembly instructions for the <a href="https://blueflyvario.blogspot.com/2021/11/blueflyvariottlgpsv122-released.html">previous version</a>. </p>Flying Alhttp://www.blogger.com/profile/04770253154348277404noreply@blogger.comtag:blogger.com,1999:blog-4078676472481844653.post-21592761649514201292022-05-04T18:42:00.003-07:002022-05-04T18:42:55.642-07:00BlueFlyVario_Bluetooth_GPS_IGC_v22 released<p>This short post releases the BlueFlyVario_Bluetooth_GPS_IGC_v22. A few weeks ago I released the <a href="https://blueflyvario.blogspot.com/2022/03/blueflyvariobluetooothusbv22-released.html">Bluetooth_USB_v22</a> model and indicated that the version with GPS_IGC was coming. It has been ready to go for a few weeks and I have already begun shipping it to replace the previous <a href="https://blueflyvario.blogspot.com/2021/06/blueflyvariobluetoothgpsigcv123-released.html">GPS_IGC_v12.3</a> model. </p><p>This new BlueFlyVario_Bluetooth_GPS_IGC_v22 model provides a bluetooth connection to work with an app on your device, and also includes an onboard GPS for onboard IGC recording. For most pilots that will be XCTrack on Android, or Flyskyhy on iOS. The USB connector is used for charging or to provide a USB serial port connection to adjust hardware settings or download IGC files. The addition of an onboard GPS allows XCTrack to be used on Android devices which do not have their own GPS, such as some Android eReaders. </p><p><b>Hardware changes</b><br /><br />The circuit board is the same as the <a href="https://blueflyvario.blogspot.com/2022/03/blueflyvariobluetooothusbv22-released.html">Bluetooth_USB_v22</a> model. When I released that model I indicated that there were some pads which are not populated with components. This new Bluetooth_GPS_IGC_v22 model populates the GPS and flash memory components, and incorporates new firmware. On the outside it looks exactly the same as the previous GPS_IGC model. </p><p>The changes since the earlier <a href="https://blueflyvario.blogspot.com/2021/06/blueflyvariobluetoothgpsigcv123-released.html">GPS_IGC_v12.3</a> model are similar to what was described for the <a href="https://blueflyvario.blogspot.com/2022/03/blueflyvariobluetooothusbv22-released.html">Bluetooth_USB_v22</a> model, such as a better processor and different power scheme. The GPS and memory chip are the same as the previous GPS_IGC. </p><p><b>Firmware changes</b></p><p>The firmware builds on the Bluetooth_USB model, and adds the functions required to record the GPS data and store it in memory. It is functionally very similar to the previous GPS_IGC model. </p><p><b>What is in the box</b></p><p>The box contains only the assembled vario, with some packaging to keep everything in place and to avoid the button being turned on. This model is shipped fully assembled by default.</p><p></p><p><b>Unboxing and first use</b></p><p>When your vario arrives, do this:</p><p></p><ol><li>Remove it from the packaging. </li><li>Remove the packaging and tape protecting the button from being turned on in transit. The low profile clear button is difficult to turn on accidently in normal use. </li><li>Short press the button. You should hear the vario turn on. See here for an explanation of the beeps and lights: <a href="https://www.blueflyvario.com/knowledgebase/explain-the-button-lights-and-beeps/">https://www.blueflyvario.com/knowledgebase/explain-the-button-lights-and-beeps/</a></li><li>Plug in microUSB cable to a charger or a computer. The red light indicates charging. </li><li>Connect it to your Android (<a href="https://www.blueflyvario.com/knowledgebase/trouble-connecting-bluetooth/">https://www.blueflyvario.com/knowledgebase/trouble-connecting-bluetooth/</a>) or iOS device (<a href="https://www.blueflyvario.com/knowledgebase/connecting-ios-bluetooth/">https://www.blueflyvario.com/knowledgebase/connecting-ios-bluetooth/</a>). The blue light indicates the bluetooth connection (double flash every 1 second or so).</li><li>After some time the orange light will flash every second, indicating you have a GPS fix (provided you are somewhere where the antenna can pick up signals). </li><li>Connect to the BFVDesktop application via USB to adjust the settings or download IGC files. </li><li>You might instead want to connect to GPSDump to download IGC files, if you need them to be signed. </li><li>You might want to add some velcro to secure it to your flight deck or a lanyard (<a href="https://www.blueflyvario.com/knowledgebase/adding-a-lanyard/">https://www.blueflyvario.com/knowledgebase/adding-a-lanyard/</a>) </li></ol>Flying Alhttp://www.blogger.com/profile/04770253154348277404noreply@blogger.comtag:blogger.com,1999:blog-4078676472481844653.post-45126861670528403392022-03-14T22:13:00.003-07:002022-03-14T22:14:47.845-07:00BlueFlyVario_Bluetoooth_USB_v22 released<p>I really enjoy releasing new vario designs. I think this is the best base model Bluefly yet, even though this latest release has come about because of the crazy chip crisis. The v22 is the first model released in 2022. </p><p>This Bluefly model provides a bluetooth connection to work with an app on your device. For most pilots that will be XCTrack on Android, or Flyskyhy on iOS. The USB connector is used for charging or to provide a USB serial port connection to adjust hardware settings. </p><p>It looks the same as the last version, but there are important changes inside. </p><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/a/AVvXsEi2HLyUMaTuHqX_oZZXJdMXwGFqZg6vn74rLe-eF7eKC0ZbrssjngGwdBXeDcFsN5I4La5022fUUUUgN6CUj_pFpLraJneingiqCAsalCvZemj8vbOpqR-cO6eg2AVcXvEFnV1cPFSpE4Y2MSEaP2GsjObPj4Cd8zvgRNFLiRWfMPeFpu-b62wCIh5rxw=s4000" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="3000" data-original-width="4000" height="480" src="https://blogger.googleusercontent.com/img/a/AVvXsEi2HLyUMaTuHqX_oZZXJdMXwGFqZg6vn74rLe-eF7eKC0ZbrssjngGwdBXeDcFsN5I4La5022fUUUUgN6CUj_pFpLraJneingiqCAsalCvZemj8vbOpqR-cO6eg2AVcXvEFnV1cPFSpE4Y2MSEaP2GsjObPj4Cd8zvgRNFLiRWfMPeFpu-b62wCIh5rxw=w640-h480" width="640" /></a></div><p><b>Hardware changes</b></p><p>The biggest change in this model is that I have moved to a new processor, the PIC32MM0064GPM028. For most of the Bluefly history I have been using a 16 bit PIC24F processor. However, the chip crisis meant that these became impossible to purchase and I have run out. Over the last year I have been experimenting with other processors, but in the end the choice was made for me when I had to select what was available in the quantities needed. I am very lucky that my workflow allows me the agility to make changes quickly. </p><p>The new processor has three UART instead of two, and its low power properties has allowed me to implement a new power scheme. This has resulted in a lower overall part count which results in less production mistakes to test and fix (the cost of little components is negligible compared to the effort in production for each component). </p><p>In most other respects the hardware design of the vario is the same as the previous BlueFlyVario_Bluetooth_USB_v12.3; same case, same button, same pressure sensor, same bluetooth chip, and the same USB chip. </p><p>This is the first vario where I have not exposed spare pins for experimenting. I have found that this is something that most pilots do not use or need. In the future I might produce an experimenter's version of this model. </p><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/a/AVvXsEjDAsFTvaAUtCijKmWkJcMSQzIW-1a2XCs3VNKukIL_LjdcgEiX9r8LH5J7_WiwTRYtQLlBZ1lp5BafmIzFn7IecFCOYzo1MvLriHLTlW6oxzUY9hK_MoRTHzQu9-XuCTqQWtfLpwfYrqR0hnVw0UydixRSRhZo3IJKbXP_sQQufDyeqfX5rnCvoWng3A=s4000" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="3000" data-original-width="4000" height="480" src="https://blogger.googleusercontent.com/img/a/AVvXsEjDAsFTvaAUtCijKmWkJcMSQzIW-1a2XCs3VNKukIL_LjdcgEiX9r8LH5J7_WiwTRYtQLlBZ1lp5BafmIzFn7IecFCOYzo1MvLriHLTlW6oxzUY9hK_MoRTHzQu9-XuCTqQWtfLpwfYrqR0hnVw0UydixRSRhZo3IJKbXP_sQQufDyeqfX5rnCvoWng3A=w640-h480" width="640" /></a></div><p></p><p>You might notice there are some pads which are not populated with components. I plan to use the same board for a new Bluetooth_GPS_IGC_v22 model. It will be a while longer until I have that new firmware tested and that model ready for release. </p><p><b>Firmware changes</b></p><p>Changing to a new processor has required a rewrite of about half of the code. The use functionality is pretty much the same, with a few new hardware settings and some optimisation of parts of the code. In addition, the new processor is well supported by a Microchip library and in the MPLAB X IDE. This should make future tweaks to the firmware easier to roll out. </p><p>There is new code to support the new power on/off arrangements. For the user it will feel the same as before, but now when you power down the vario it turns off one of the voltage regulators (which powers off everything other than the processor) and puts the processor into a very deep sleep mode. In this mode the processor consumes about 0.06 mA, but it still responds to a button press to reboot the vario and start it up again. A fully charged battery will last over two years in deep sleep mode, but if you do not plan to use the vario for more than a year I recommend disconnecting the battery. </p><p>Under the code there is also a new version of the ds30 bootlaoder. It is the commercial version and is designed for this device. If I release firmware updates expect a new post describing how to use it. </p><p><b>What is in the box</b></p><p>The box contains only the assembled vario, with some packaging to keep everything in place and to avoid the button being turned on. </p><p></p><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/a/AVvXsEgU40p7NVdlQS6kr7gdOf8JpNZ3Wr1SKMcFtMujXkF9hD6FGUZ6r2m3axecZgMf2gaba4kBatcf0tT9EndloboRCVBxYUhQlWt_Dja5t-diAnVa41z_6YCGF71ecU-ZyL9lKE64bOFdUXC6hz93PClAErq34CWAYC5fNk7cyLUz8p8Hhd1gryT4F0ZQhg=s4000" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="3000" data-original-width="4000" height="480" src="https://blogger.googleusercontent.com/img/a/AVvXsEgU40p7NVdlQS6kr7gdOf8JpNZ3Wr1SKMcFtMujXkF9hD6FGUZ6r2m3axecZgMf2gaba4kBatcf0tT9EndloboRCVBxYUhQlWt_Dja5t-diAnVa41z_6YCGF71ecU-ZyL9lKE64bOFdUXC6hz93PClAErq34CWAYC5fNk7cyLUz8p8Hhd1gryT4F0ZQhg=w640-h480" width="640" /></a></div><br />This model is shipped fully assembled by default.<br /><p></p><p><b>Unboxing and first use</b></p><p>When your vario arrives, do this:</p><p></p><ol style="text-align: left;"><li>Remove it from the packaging. </li><li>Remove the packaging and tape protecting the button from being turned on in transit. The low profile clear button is difficult to turn on accidently in normal use. </li><li>Short press the button. You should hear the vario turn on. See here for an explanation of the beeps and lights: <a href="https://www.blueflyvario.com/knowledgebase/explain-the-button-lights-and-beeps/">https://www.blueflyvario.com/knowledgebase/explain-the-button-lights-and-beeps/</a></li><li>Plug in microUSB cable to a charger or a computer. The red light indicates charging. </li><li>Connect it to your Android (<a href="https://www.blueflyvario.com/knowledgebase/trouble-connecting-bluetooth/">https://www.blueflyvario.com/knowledgebase/trouble-connecting-bluetooth/</a>) or iOS device (<a href="https://www.blueflyvario.com/knowledgebase/connecting-ios-bluetooth/">https://www.blueflyvario.com/knowledgebase/connecting-ios-bluetooth/</a>).</li><li>Consider connecting to the BFVDesktop application to adjust the settings. I do not think this is necessary for most pilots - I have chosen settings which I think work best. </li><li>You might want to add some velcro to secure it to your flight deck or a lanyard (<a href="https://www.blueflyvario.com/knowledgebase/adding-a-lanyard/">https://www.blueflyvario.com/knowledgebase/adding-a-lanyard/</a>) </li></ol><p></p>Flying Alhttp://www.blogger.com/profile/04770253154348277404noreply@blogger.comtag:blogger.com,1999:blog-4078676472481844653.post-82160339157177787352021-11-05T23:48:00.003-07:002021-11-06T00:01:38.206-07:00BlueFlyVario_TTL_GPS_V12.2 released<p>The <a href="https://www.blueflyvario.com/product/blueflyvario_ttl_gps_v12-2/">BlueFlyVario_Bluetooth_TTL_GPS_v12.2 is ready for release</a>. This model has been developed because the lead time on the XA1110 GPS module is crazy, and all of my stock of that module is reserved for the GPS_IGC model. Nonetheless, from crisis come innovation, and this model has some major benefits over the TTL_GPS_v12 released over three years ago. The number of pilots installing a BlueFly on a Kobo has reduced, but it is still very popular and I am pleased that I have found a way to continue to support it during the chip shortage. </p><p><b>What is going on with chips? </b></p><p>The global <a href="https://en.wikipedia.org/wiki/2020%E2%80%932021_global_chip_shortage">electronics chip shortage</a> is madness. For a little electronics design and manufacturing company like Bluefly it is particularly bad. I am a one-man part-time business and the chip shortage has affected availability, price, and development. </p><p></p><ul style="text-align: left;"><li>I can get one or two of almost any component, or if I was a big manufacturer am sure I could get half a million of critical components, but trying to find 500 to 5000 of anything made of silicon is hard. That is exactly the quantities that a company like the Bluefly is operating in. </li><li>The price of all components are up 20% to 50%. </li><li>All of this makes development harder. Over the last year I have been designing sub-components of a future vario project, using a different pressure sensor and new microcontroller family, but just as I was ready to build a full prototype, lead times for the components I included in the design extended to over a year. This has not been wasted time, but it will postpone my plans. </li></ul><div><b>The new GPS</b></div><div><br /></div><div>There are a few GPS modules that are suitable for these little Blueflys. I am looking for GPS modules that include an antenna for reduced part count, are surface mount for easily assembly, are small enough to fit in the design. Most importantly, the module must be available in the quantities needed. There are basically two types; those with a ceramic antenna (like the XA1110 of the previous model), and those with a small chip antenna. </div><div><br /></div><div>I have experimented with chip antenna in the past, but I could never get the performance to work as well as a ceramic antenna. However, with the TTL_GPS there are some criteria that made me think I could get it to work. I could make the circuit board large enough for a good ground plane, and there was no need for a battery with copper foil directly underneath the antenna. After a bit of research I found the <a href="https://www.quectel.com/product/gnss-l96">Quectel L96</a> and decided to experiment with it. This has some advantages of having the same internal MTK chipset I am familiar with and the price is comparable. </div><div><br /></div><div>After my first prototype it was pretty clear that this was going to work. In fact, the performance of the ceramic chip antenna for this GPS with a larger ground plane is better than the previous ceramic antenna model (reduced time-to-first-fix). The image below shows the difference in size between the v12.2 (top) at 20mm x 60mm compared to v12 (bottom) at 17mm x 50mm. It is difficult to see, but without the height of the ceramic antenna the new vario has a much lower profile. </div><div><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgulg9RiZukyOVUUlhVGhdP-ci3TEWzSEN2dGTkHsVEfXv9yG6tbgFmxuGpG9EltbykkDiO9JdKAU2BViA3JJ0TstWeU_zV_-V9KDA9LE3tqIj5ObtWx6BCRR0oJmn6AQQrREUjyF3C6ens/s2048/BlueFlyVario_TTL_GPS_V12.2Compare.jpg" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="1536" data-original-width="2048" height="480" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgulg9RiZukyOVUUlhVGhdP-ci3TEWzSEN2dGTkHsVEfXv9yG6tbgFmxuGpG9EltbykkDiO9JdKAU2BViA3JJ0TstWeU_zV_-V9KDA9LE3tqIj5ObtWx6BCRR0oJmn6AQQrREUjyF3C6ens/w640-h480/BlueFlyVario_TTL_GPS_V12.2Compare.jpg" width="640" /></a></div><br /><div><b>New hardware features</b></div><p></p><p>The BlueFlyVario_Bluetooth_TTL_GPS_v12.2 has some differences from the earlier designs:</p><p></p><ul style="text-align: left;"><li>It is larger, as described above.</li><li>The component layout is different (switch and speaker on the opposite side, sparser components). This is all about designing the board to maximise the performance of the chip antenna. </li><li>The headers/pins for the TTL serial connection have solder tabs to offer alternate ways to connect the wires. </li><li>I have included a V_Backup tab. For most users I do not suggest that you use this (and do not suggest that you close the solder jumper to connect it to V+). If you feel that V_Backup is for you make sure you read the datasheet for the L96 to understand how it works. </li><li>The ON solder jumper next to the voltage regulator is closed by default. This means that as soon as power is connected between GND and V+ that the vario will power on. If you want the same behaviour as the v12 then you can cut the connecting wire on the tab. </li><li>The GPS LED is orange. When the GPS has a 3D fix it will flash. </li><li>Pads for GND, RST and BOOT are exposed on the top of the board. </li><ul><li>Short GND and RST when powering on to reset the default hardware settings. </li><li>Short GND and BOOT when powering on to enter the bootloader for updating firmware via TTL_Serial (if I release an update). </li></ul><li>Note that there are a couple of components near the GPS that are not populated. This is not a mistake. </li></ul>The image below shows the layout on the front and back of the board. <div><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi00jm50eZfHMQtsjitZsb4jQsjL85qJD54vpPYm0QFY438qGr0ht1BXqacIBQDZ3cSUEh0rIboTGKJ8u2KCxVMi-mh1kCPzrPR7K1ClyGhoOB7yoBxUkuxLPVEu88MOwe354u8JU9SFsjx/s960/BlueFlyVario_TTL_GPS_v12.2_Layout.png" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="720" data-original-width="960" height="480" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi00jm50eZfHMQtsjitZsb4jQsjL85qJD54vpPYm0QFY438qGr0ht1BXqacIBQDZ3cSUEh0rIboTGKJ8u2KCxVMi-mh1kCPzrPR7K1ClyGhoOB7yoBxUkuxLPVEu88MOwe354u8JU9SFsjx/w640-h480/BlueFlyVario_TTL_GPS_v12.2_Layout.png" width="640" /></a></div><br /><div><div><b>New firmware</b></div><div><br /></div><div>Some updates to the firmware for this model include:</div><div><ul style="text-align: left;"><li>Some changed default settings to match the different GPS (internal baud rate).</li><li><b>startDelayMS </b>is set at 2000 by default. This adds a 2s delay between the vario powering on (indicated with a very brief chip), and data being sent out. It is used because the ON solder jumper is closed by default. The behaviour is that when your Kobo is started, and power flows from the Kobo serial port, the vario starts right away. </li><li>There is a higher performing vario/GPS sentence multiplexing algorithm. </li></ul></div><div><div><b>What is in the bag?</b></div><div><br /></div><div>The BlueFlyVario_TTL_GPS_v12.2 includes:</div><div><ul style="text-align: left;"><li>The vario module.</li><li>A small piece of neoprene. It is very important that this is placed over the pressure sensor to protect it from the light, but still allow air to come through. Make sure to leave the white tape on, and place the black squishy side of the neoprene on the sensor. </li><li>Some blue PVC heatshrink to hold the neoprene in place and help protect the components. You will only put this on at the final assembly stage. </li><li>Some telephone cable. Strip this for the individual wires. </li></ul></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEghYdVIqMkP74yg93CBIBMZiA-fajUmjNz0ElnpIW1KmKYzrJd211o-agq0lbztmwrD3xwNIiLf7MSgf5J51YFzfaTWJGDIXuhFHEEAZLVSzBmP3Y1EFEGBe_YyiItQ6Za7vi_BXa1tEbWd/s2048/BlueFlyVario_TTL_GPS_v12.2_Bag.jpg" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="1536" data-original-width="2048" height="480" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEghYdVIqMkP74yg93CBIBMZiA-fajUmjNz0ElnpIW1KmKYzrJd211o-agq0lbztmwrD3xwNIiLf7MSgf5J51YFzfaTWJGDIXuhFHEEAZLVSzBmP3Y1EFEGBe_YyiItQ6Za7vi_BXa1tEbWd/w640-h480/BlueFlyVario_TTL_GPS_v12.2_Bag.jpg" width="640" /></a></div><div><div class="separator" style="clear: both; text-align: center;"><br /></div></div><div><b>Simple Assembly</b></div><div><br /></div><div>There are many ways to assemble the module on the Kobo. I suggest you read old blog posts on here and check out Nev's page at <a href="http://gethighstayhigh.co.uk/kobo-self-build/">http://gethighstayhigh.co.uk/kobo-self-build/</a> for more ideas. Some pilots design 3D cases. I prefer a simple install method these days. </div><div><br /></div><div>Some important tips for all installs:</div><div><ul style="text-align: left;"><li>Keep the wires as short as possible. The location of the Bluefly will depend on which kobo you have. Note that xcsoar can be configured in any of the four orientations and you should select a layout to match. </li><li>Put the neoprene on correctly. Make sure the black squishy side is on top of the pressure sensor to protect it from light, but still let air in. </li><li>Keep your solder joints clean. Use a hot soldering iron with flux for the minimum time needed to get good solder joints. Clean the flux off with isopropyl alcohol. </li><li>Make sure the antenna is hanging over the edge of the bezel, with nothing behind the keep out area on the back of the Bluefly board. </li><li>In xcsoar, set the Bluefly as Device A, Port: ttymxc0 (or something like that, only one will work), Baud rate: 115200, Driver: BlueFly Vario.</li></ul><div>The image below shows mid way through an install on an old Kobo Glo. Notice the neoprene in the right spot. At about this point I always make sure that I check the Monitor in the Devices menu of xcsoar to see the data streaming in. <div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjbWD_HgPY6Tnu9KQWaXfQH62dAUDe_PyHCZ-Ix0gyGjoMXyB9qwTwzEZHJlVq13lU0Mz8aFr0xcKBtVeEw16G4m632fCm0mZjxOZuMJTnl5MJGnsYrMV1xEAff8GdfnIFQ9iPTucGwtoFQ/s2048/IMG_20211106_162105.jpg" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="1536" data-original-width="2048" height="480" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjbWD_HgPY6Tnu9KQWaXfQH62dAUDe_PyHCZ-Ix0gyGjoMXyB9qwTwzEZHJlVq13lU0Mz8aFr0xcKBtVeEw16G4m632fCm0mZjxOZuMJTnl5MJGnsYrMV1xEAff8GdfnIFQ9iPTucGwtoFQ/w640-h480/IMG_20211106_162105.jpg" width="640" /></a></div><br /></div></div><div>In my simple installs I generally just attached the vario using double sided tape (after heatshrink). Hot melt glue helps protect the wires.</div><div><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgPvt0zGuOecXvGFV0bUmhviyQU5MHkEYbhdbKTElYcdFVXeDk_Dc5CBn1HlIrGcjLsLdS3tYsj1GMIP4fGIcnN6xjvMx0MEpFfnh_HHgn4dJAM6710Mg3I3bzanqrodxNaUjTpVz6gudiL/s2048/IMG_20211106_172734.jpg" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="1536" data-original-width="2048" height="480" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgPvt0zGuOecXvGFV0bUmhviyQU5MHkEYbhdbKTElYcdFVXeDk_Dc5CBn1HlIrGcjLsLdS3tYsj1GMIP4fGIcnN6xjvMx0MEpFfnh_HHgn4dJAM6710Mg3I3bzanqrodxNaUjTpVz6gudiL/w640-h480/IMG_20211106_172734.jpg" width="640" /></a></div></div></div>Flying Alhttp://www.blogger.com/profile/04770253154348277404noreply@blogger.comtag:blogger.com,1999:blog-4078676472481844653.post-51884342395253757842021-07-25T01:31:00.005-07:002023-05-05T15:14:37.447-07:00Bluefly IGC Validation<p><i>This article has been updated for clarity in May 2023.</i></p><p>Six weeks ago I released a <a href="https://blueflyvario.blogspot.com/2021/06/blueflyvariobluetoothgpsigcv123-released.html">new model of the Bluefly with onboard GPS and IGC recording</a>. The BlueFlyVario_Bluetooth_GPS_IGC_v12.3 has been more popular than I first thought. Today I am pleased to announce the BlueFly IGC files can be validated with <a href="http://www.gpsdump.no/">GpsDump</a> (Version 5.40), so you can use it as a backup for competitions that require validated IGC files. </p><p><b>What is IGC File Signing?</b></p><p>It would be possible for a pilot to create a fake IGC file for competitions or records. Signing the file with a G-Record is designed to prevent this. The G-Record is a few lines of text at the end of the file that can be used to check if the rest of the file was generated by the device creating the IGC file. Nothing is 100% secure, but the signing mechansim prevents casual tampering except by really determined highly technical hackers. Of course, faking an IGC file would be silly, but some people worry about it. </p><p>The original IGC spec by the FAI requires a pretty sophisticated mechanism for signing IGC files, based on individual device serial number and public key encryption. Some high end devices implement this spec, but they are pretty much limited to use on sailplanes. </p><p>A more relaxed version of the specification is <a href="https://www.fai.org/sites/default/files/civl/documents/sporting_code_s7_h_-_civl_flight_recorder_specification_2021_v0.9.0.pdf">produced by FAI CIVL for Hang Gliding and Paragliding use</a>. This is what has now been implemented on the Bluefly and this new model has been submitted for approval by CIVL. In addition, the developer of GPSDump has implemented Bluefly IGC download and resigning and that can be used right now for uploading your IGC files to online competitions.</p><p>You can read a lot more about IGC files and CIVL <a href="http://vali.fai-civl.org/index.html">here</a>. </p><p><b>What is IGC File Validation?</b></p><p>In simple terms this is the opposite of IGC File Signing. A program checks that the IGC file contents match the signature at the end of the file, and that the signature was generated by the device manufacturer. </p><p><b>GpsDump and the Bluefly (XGD)</b></p><p>GpsDump is one of the most widely used programs for downloading IGC files from flight instruments. Stein has been very kind to implement the Bluefly IGC download protocol and validate the Bluefly G-Record. Once the validated track data is in GpsDump it can then be saved as a GpsDump signed IGC file, which is widely supported by competitions and online validators. After you have your Bluefly successfully installed as a COM port, the first step is to read the list of files from the Bluefly. </p><p></p><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhPVHlsskCZ6wv8EFdznBaDebVyCxHYr3W2rjnIIuMaybtXJgSJw6AmRSDayOQiQMDk72EnrDvDsmMqgG7L8pbT9AGtcZtMW7YdjaPx-4MY66NMeqVe1s65F8-lRvNH1L3oPFvZD3sDJ3hJ/" style="margin-left: 1em; margin-right: 1em;"><img alt="" data-original-height="794" data-original-width="523" height="640" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhPVHlsskCZ6wv8EFdznBaDebVyCxHYr3W2rjnIIuMaybtXJgSJw6AmRSDayOQiQMDk72EnrDvDsmMqgG7L8pbT9AGtcZtMW7YdjaPx-4MY66NMeqVe1s65F8-lRvNH1L3oPFvZD3sDJ3hJ/w421-h640/GPSDump_Bluefly.png" width="421" /></a></div><p>The list of IGC files on the Bluefly is then like this. Note that the duration is approximate only. </p><p></p><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjMxO3mbnmwgVF1rb3GN6vXlTmfwIPj52-GIPyT-ym_1wHo_q4-SPr0Rhy-nvC-kurlgeEWAdhnuMjUeWvU7QdwE8_0W2bRywH1FaqiyTCf8abmdabiXC-P9tgTDmSWmuWaByraa463mUIV/" style="margin-left: 1em; margin-right: 1em;"><img alt="" data-original-height="297" data-original-width="235" height="320" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjMxO3mbnmwgVF1rb3GN6vXlTmfwIPj52-GIPyT-ym_1wHo_q4-SPr0Rhy-nvC-kurlgeEWAdhnuMjUeWvU7QdwE8_0W2bRywH1FaqiyTCf8abmdabiXC-P9tgTDmSWmuWaByraa463mUIV/w254-h320/GPSDump_Bluefly2.png" width="254" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: left;">Once the file is downloaded you can then 'Save IGC file made by GpsDump' and add a few details if you like. The GpsDump saved file is re-signed and can then be used by any competition that uses GpsDump files, which I think is almost all of them. </div><div class="separator" style="clear: both; text-align: left;"><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjU1Ccb-EJ3gh_jSjG4UaLL5nCnwifMP-5YSGIUryzQ_-EcL2oO6pJwLgLrs4C07cp-8KtVGsj54ekpI9HNbG5D848Nh5Uxp0e9iE3uUqNjPc4o2OWjgVPwJ4Khy-vexTNl-6TNFUdOTeId/" style="margin-left: 1em; margin-right: 1em;"><img alt="" data-original-height="657" data-original-width="530" height="640" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjU1Ccb-EJ3gh_jSjG4UaLL5nCnwifMP-5YSGIUryzQ_-EcL2oO6pJwLgLrs4C07cp-8KtVGsj54ekpI9HNbG5D848Nh5Uxp0e9iE3uUqNjPc4o2OWjgVPwJ4Khy-vexTNl-6TNFUdOTeId/w517-h640/GPSDump_Bluefly3.png" width="517" /></a></div><br /><b>Bluefly Validation (VBF)</b></div><div class="separator" style="clear: both; text-align: left;"><br /></div><div class="separator" style="clear: both; text-align: left;">The G-Record signing in the Bluefly can also be used to directly validate the files you have downloaded using the BFVDesktop application. See the release blog post for information on how to download the files directly. The IGC files on the Bluefly use the three letter code VBF in anticipation of this code being compliant with the specification (this may change to XBF in the future). </div><div class="separator" style="clear: both; text-align: left;"><br /></div><div class="separator" style="clear: both; text-align: left;">To validate files from the Bluefly that you have downloaded directly using the BFVDesktop application you will need the validation program <a href="https://www.blueflyvario.com/files/vali-vbf.exe">vali-vbf.exe</a>. Use it from the command line like:</div><div class="separator" style="clear: both; text-align: left;"><br /></div><div class="separator" style="clear: both; text-align: left;"><span style="color: #666666;">>vali-vbf.exe <i>filename.igc</i></span></div><div class="separator" style="clear: both; text-align: left;"><i><br /></i></div><div class="separator" style="clear: both; text-align: left;">Please note that you will need firmware version 12.529 or later on your BlueFlyVario_Bluetooth_GPS_IGC for the Bluefly IGC validation to work. There were only a few copies of this new model sent out with an earlier version of the firmware. If you do not have 12.529 or later please contact me and I will help you update it. </div><div class="separator" style="clear: both; text-align: left;"><br /></div><div class="separator" style="clear: both; text-align: left;"><br /></div><div class="separator" style="clear: both; text-align: left;"><br /></div><div class="separator" style="clear: both; text-align: left;"><br /></div><div class="separator" style="clear: both; text-align: left;"><br /></div><div class="separator" style="clear: both; text-align: left;"><br /></div><div class="separator" style="clear: both; text-align: left;"><br /></div><div class="separator" style="clear: both; text-align: left;"><br /></div><div class="separator" style="clear: both; text-align: left;"><br /></div><div class="separator" style="clear: both; text-align: left;"><br /></div><div class="separator" style="clear: both; text-align: left;"><br /></div><div class="separator" style="clear: both; text-align: left;"><br /></div><div class="separator" style="clear: both; text-align: left;"><br /></div><div class="separator" style="clear: both; text-align: left;"><br /></div><div class="separator" style="clear: both; text-align: left;"><br /></div><div class="separator" style="clear: both; text-align: left;"><br /></div><div class="separator" style="clear: both; text-align: left;"><br /></div><div class="separator" style="clear: both; text-align: left;"><br /></div><div class="separator" style="clear: both; text-align: left;"><br /></div><div class="separator" style="clear: both; text-align: left;"><br /></div><div class="separator" style="clear: both; text-align: left;"><br /></div><p></p><p></p><p></p><p><br /></p><ul style="background-color: white; color: #222222; font-family: Arial, Helvetica, sans-serif; font-size: small;"></ul><p><br /></p>Flying Alhttp://www.blogger.com/profile/04770253154348277404noreply@blogger.comtag:blogger.com,1999:blog-4078676472481844653.post-45195602008889519562021-06-11T17:33:00.002-07:002021-06-11T17:44:47.625-07:00BlueFlyVario_Bluetooth_GPS_IGC_v12.3 released<p>The BlueFlyVario_Bluetooth_GPS_IGC_v12.3 is ready for release. This model was developed following requests from many pilots who wanted to add a GPS and IGC tracklog recording to the Bluetooth_USB model. </p><p>The motivation was to integrate the GPS on to the main board instead of using an add-on. The <a href="http://blueflyvario.blogspot.com/2019/06/blueflygpsaddonv12-released.html">GPS add-on</a> released a few years ago worked well, but it was a lot of messing around for those pilots that just wanted a vario with GPS. I took advantage of the opportunity to add a memory chip to add IGC tracklog recording. The new model utilizes many of the same components and code from the other v12 models, with a redesigned the PCB layout to fit in the translucent blue case. This was harder than expected and the design process has taken well over a year through many prototype iterations. The new vario is <a href="https://www.blueflyvario.com/product/blueflyvario_bluetooth_gps_igc_v12-3/">available now</a> and is shipped fully assembled and ready for pilots to enjoy. <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjxBVHuTZZCkAC3Euu4T_pNRxw54VWnvY2uCiU6CaqMJBSRa4DbDG14-d-wJF3K2zkSxB6tfQBfaHfT_Y2KP1VPquW4ioCwJp6wKDM4eDodqx-SKuUWh-r7qR4j60kUy9Z8WUfOq1rAopCP/s2048/BlueFlyVario_Bluetooth_GPS_IGC_v12.3.jpg" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="1536" data-original-width="2048" height="480" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjxBVHuTZZCkAC3Euu4T_pNRxw54VWnvY2uCiU6CaqMJBSRa4DbDG14-d-wJF3K2zkSxB6tfQBfaHfT_Y2KP1VPquW4ioCwJp6wKDM4eDodqx-SKuUWh-r7qR4j60kUy9Z8WUfOq1rAopCP/w640-h480/BlueFlyVario_Bluetooth_GPS_IGC_v12.3.jpg" width="640" /></a>I am pleased that the GPS antenna is flush with the top of the case. By using the same acrylic button recently released on the Bluetooth_USB_v12.3 model I was able to keep the profile pretty clean. </p><p><b>Features</b></p><p>The BlueFlyVario_Bluetooth_GPS_IGC_v12.3 has a combination of features that complement the other Bluefly models, including:</p><p></p><ul style="text-align: left;"><li>Reliable vario sensitivity and audio performance of the other v12 models - it beeps when you go up in the way that pilots love. </li><li>The same Bluetooth and USB interface as the Bluetooth_USB model for data output and adjusting settings. You can adjust all of the same settings, plus a few new ones. </li><li>The XA1110 GPS from the TTL_GPS model: </li><ul><li>Better time-to-first-fix than other models through improved PCB layout. </li><li>Uses battery backup for super fast subsequent fixes on the same day in a similar location. </li><li>Operates at 1 second intervals, although with some tinkering can be set to operate at higher intervals. </li></ul><li>Reliable serial flash memory for storing about 60 hours of flight time at 1 second intervals. </li><ul><li>If the vario is on and the GPS has a 3D fix then IGC recording will start. </li><li>Recording continues until the vario is shut down.</li></ul><li>LED's for indicating status: </li><ul><li>Orange: 1 second flashing = 3D fix</li><li>Blue: Single flash = bluetooth scanning; Double flash = connection. </li><li>Red: Charging.</li><li>Green: Button press, Lift and other indications as described in the manual. </li></ul><li>Battery life of about eight hours.</li></ul><div><b>What is in the box?</b></div><div><br /></div><div>The BlueFlyVario_Bluetooth_GPS_IGC_v12.3 is shipped fully assembled and ready to use. A sticky velcro patch is included to allow mounting it to your flight deck. </div><div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhoSE9Cw4aXHtsbouSoZBpiExxKPYHBHbQBd2WBXEcP9g6nWO9lKI2cYlCIkXePk3QkV1VYYgFbIfh3KJ4m_84Jfk851sEzQxVxeXATbtyw6qvq6kpM8-JJs2OOgt41kaUTPHGVwZkPjwEl/" style="margin-left: 1em; margin-right: 1em;"><img alt="" data-original-height="1536" data-original-width="2048" height="300" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhoSE9Cw4aXHtsbouSoZBpiExxKPYHBHbQBd2WBXEcP9g6nWO9lKI2cYlCIkXePk3QkV1VYYgFbIfh3KJ4m_84Jfk851sEzQxVxeXATbtyw6qvq6kpM8-JJs2OOgt41kaUTPHGVwZkPjwEl/w400-h300/1623453305313.jpg" width="400" /></a></div><br /><b>Typical Use</b></div><div><br /></div><div>This model is designed for stand alone use, or for connecting to a smartphone. Follow these quickstart steps to begin:</div><div><br /></div><div><b>Step 1 - Charging</b>. To begin, find a MicroUSB cable and charge the vario. Any phone charger that provides 5V can be used, or even a computer USB port. The red LED should come on, then turn off when the vario is fully charged. A full charge will take about two or three hours. </div><div><br /></div><div><b>Step 2 - Turn it on</b>. A short single press will turn on the vario. The button, beeps and lights are described in more detail <a href="https://www.blueflyvario.com/knowledgebase/explain-the-button-lights-and-beeps/">here</a>. Move the vario from your feet to above your head to simulate lift and hear the beeping as it rises.</div><div><br /></div><div><b>Step 3 - Connect to a PC (optional)</b>. Download the BFVDesktop application from the <a href="https://www.blueflyvario.com/software/">software page</a> of the website. Using a USB cable connect the vario to your PC and see the settings. Read the <a href="https://www.blueflyvario.com/support/">hardware settings manual</a> for a more detailed description of this settings (although note that the manual is not yet updated with the IGC settings described below). </div><div><br /></div><div><b>Step 4 - Connect to an app</b>. We will use <a href="https://xctrack.org/">XCTrack</a>. This is a popular app among paraglider pilots and works well with the Bluefly. Do the following:</div><div><ul style="text-align: left;"><li>Install XCTrack on your android device by searching for it in Google play. </li><li>Restart the vario (long press to shut it down, then short press to start it up). This ensures that the bluetooth module is ready to go. </li><li>In your android device settings pair the Bluefly as a bluetooth device. The name will be 'Bluefly-ABCD'. </li><li>Open XCTrack and drag down to see the menu. Click Preferences|'Connection & Sensors'|'External sensor' then select the Bluefly you paired with in the previous step. If you select the wrong one select "None", then try again. </li><li>If you want, choose 'Use external GPS' to allow XCTrack to use the GPS information from the Bluefly instead of using the internal android GPS. This is useful on old devices with unreliable GPS, or on android e-readers that do not have a GPS. </li><li>At the bottom of this menu click 'Calibrate' to see pressure data streaming in from the Bluefly. There is no need to adjust the default XCTrack calibration settings here. </li><li>Go back to the main display and you should see the GPS and Bluetooth icon indicating a connection. To test, shut the Bluefly down, and see the disconnected message, then start it up again and see the reconnection messages. </li></ul></div><div><b>IGC Tracklogs</b></div><p></p><p>This is the first Bluefly model which incorporates a memory for recording IGC tracklogs from GPS fixes, and there are some new settings which control how it happens. When the vario is on and the GPS has a valid GPS fix then tracklog recording will start. This means you will always get a backup record without having to rely on your flight software trying to interpret when a flight started or stopped. </p><p><b>IGC Format.</b> The IGC files produced work well with online logging programs and visualization software, but at this stage the firmware does not add a signed G-record required in some high level competitions. In other respects, the IGC file structure follows the <a href="https://www.fai.org/sites/default/files/civl/documents/sporting_code_s7_h_-_civl_flight_recorder_specification_2021_v0.9.0.pdf">recommendations in the FAI sporting code for HPG instruments</a>. </p><p><b>Memory Structure.</b> IGC files are stored on a NOR Flash memory chip soldered to the Bluefly circuit board with a SPI interface to the processor. This is a low profile component and provides 64Mbit of raw memory storage. I had initially envisaged that a standard file system structure would be used, with a mass storage device interface. However, this is not possible with the current Bluefly processer and is something to think about for future Bluefly models. So, for this model, the Bluefly firmware uses a custom memory structure for recording file information. A simplified description of the memory structure is:</p><p></p><ul style="text-align: left;"><li>The NOR Flash Memory chip is structured in 2048 sectors which are 4096 bytes in size. </li><li>Each file starts in a fresh sector. When recording starts a file data header consisting of the file name, the start sector, and the file number is written to the first few bytes of the sector. The file name is based on the date and time received from the GPS (note that this is the UTC time). </li><li>Next, the IGC header information is written (A record and H records). </li><li>Next, B records are written as GPS information is recorded. </li><li>When the end of the sector is reached, the same file data header is written to the following sector, then recording continues. This means that every sector with IGC data also has a file data header.</li><li>When the Bluefly is shut down the file is closed, and the location of the next sector is stored in the Bluefly memory. </li><li>The next file is written in the same way. When all of the sectors are full (after about 60 hours of recording at 1 second intervals), the memory wraps around and the sector pointer sets to 0. In this way there is a continuous record of the last 60 hours of flight time, although the oldest file will be incomplete if the memory is full. </li></ul><div><b>User Interface</b>. The BFVDesktop application (version 0.8) has been updated with the new settings and functionality to download IGC files. The screenshot below shows the new settings:</div><div><ul style="text-align: left;"><li><i>gpsLogInterval </i>has been changed in this model to control how often track points are recorded. The GPS outputs $GNRMC messages once a second (by default), and if gpsLogInterval is set to 1 then each of these messages is formatted to a B record and saved to the IGC memory. If it is set to 2, then every second point is recorded, and so on. </li><li><i>igcSectorNumber </i>is the next memory sector that will be used. There is no need to change this for anything other than developmental reasons. </li><li><i>igcFileNumber </i>is the number stored in the data file header. Again, there is no need to change this. </li><li><i>pilotName </i>is the name stored in the IGC file H record. I am not sure who really cares about this, but it might be important if there is a G record in the future. <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgQoTEd3GTrMbdufZoQPXH3tPtbKRx2WybryAmQWnRC9kuGOHUQ90BAVxwPAji18XE9Qt1oNnVWb14TBo-akHNYmGvEFKLGKICMPcGI_5GQh87w3bQAzNBAdyhfrUCYcm8zV1nTZHcubPDh/s981/BFVDesktop_IGCSettings.png" style="margin-left: 1em; margin-right: 1em; text-align: center;"><img border="0" data-original-height="981" data-original-width="841" height="640" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgQoTEd3GTrMbdufZoQPXH3tPtbKRx2WybryAmQWnRC9kuGOHUQ90BAVxwPAji18XE9Qt1oNnVWb14TBo-akHNYmGvEFKLGKICMPcGI_5GQh87w3bQAzNBAdyhfrUCYcm8zV1nTZHcubPDh/w549-h640/BFVDesktop_IGCSettings.png" width="549" /></a></li></ul></div><div>When the vario is connected if you press on the IGC button in the Hardware Commands section of the interface it will pop up the BFV IGC File Downloader window shown below:</div><div><ul style="text-align: left;"><li>When the window opens a command is sent to the Bluefly to poll each sector for a file data headers the list of files is build. Press Refresh to poll the memory again. </li><li>The file name incorporates the data and time that recording of that file commenced. The file number can be ignored for most purposes. The start sector is where the files starts in memory. And the number of sectors gives you an indication of the size of the file (each sector stores about 110 records at 1 second intervals). In the example below, 11 sectors is about 20 minutes of recording. </li><li>Highlight the file you want and press Download to save it. You can change the save location by using Select Save Directory. </li><li>You can Format the entire IGC memory, deleting everything, and setting the start sector back to 0. </li></ul><div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgeBI6fvSWV7yzcviGgpVGMzDqB5c3kCq-p8x4edA8K4Lt5rzs_aenA0-XV18RWuHi57LluVtTsctvAwserGFNe1InMnBgXRKSZbG3rR8yCMoGz-oyX9EFqFLNqZj3TZ2OLCEoLcmzumswi/" style="margin-left: 1em; margin-right: 1em;"><img alt="" data-original-height="258" data-original-width="802" height="206" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgeBI6fvSWV7yzcviGgpVGMzDqB5c3kCq-p8x4edA8K4Lt5rzs_aenA0-XV18RWuHi57LluVtTsctvAwserGFNe1InMnBgXRKSZbG3rR8yCMoGz-oyX9EFqFLNqZj3TZ2OLCEoLcmzumswi/w640-h206/image.png" width="640" /></a></div></div><div><p><b>Future Development</b></p><p>I am always tinkering. It may be time to change to a new processor, add new features, try to drive down the price, and so on... However, time is always hard to find. Let me know your thoughts. </p><p><br /></p><p><br /></p></div></div>Flying Alhttp://www.blogger.com/profile/04770253154348277404noreply@blogger.comtag:blogger.com,1999:blog-4078676472481844653.post-80066235024320109452021-04-05T03:04:00.001-07:002021-04-05T04:09:05.306-07:00BlueFlyVario_Bluetooth_USB_v12.3 released<p>The <a href="https://www.blueflyvario.com/product/blueflyvario_bluetooth_usb_v12-3/">BlueFlyVario_Bluetooth_USB_v12.3</a> is another minor update to the previous version released a few years ago - the Bluefly has a new button! </p><p>Please read this post in conjunction with the <a href="https://blueflyvario.blogspot.com/2017/01/blueflyvariobluetoothusbv12-released.html">release post for the BlueFlyVario_Bluetooth_USB_v12</a> and the <a href="https://blueflyvario.blogspot.com/2019/06/blueflyvariobluetoothusbv122-released.html">release post for the BlueFlyVario_Bluetooth_USB_v12.2</a> to understand the changes.</p><b>The new button</b><br /><br />One of the most frustrating part of electronic design is getting the physical user interface right - the case, usb connector, lights, and button. I have experimented with a few different buttons in the Bluefly project. The trick is to find the right balance between usability (including with gloves), avoiding accidental presses, cost, reliability of component supply and appearance. The button on previous versions met most of these requirements, however some pilots found that it was pressed accidently too often. <div><br /></div><div>The new button is a lower profile 4x4x1.5mm smd tact switch that is actuated with a machined acrylic part. The button hole in the translucent blue case is machined to 6mm diameter to fit. It costs a bit more, and I need to machine the acrylic myself, but I have found it to be much more pleasant to use. It was tested with competition pilots earlier this year and I am now happy to release it as the default Bluefly button. </div><div><br /></div><div>For those pilots that have followed the Bluefly journey since the beginning, the clear acrylic button might make you think fondly of the first sandwich case <a href="https://blueflyvario.blogspot.com/2013/02/prototype-version-05b.html">released with version 0.5b</a>. <div><br /></div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiJHnfWJNjtuE_7bb9C-hW38yzF34W57_Ev9JRclwW7rCAw5EDf8VcgPT59o3pqZ5siNFC2jYttHRUCIL-ca7VocQbmmpHckWZ0lPvMnKMC_TDQNy27B55X2Pa4vxElahL9KJLSuQCvfgGR/s2048/IMG_4928+%25282%2529.JPG" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="1365" data-original-width="2048" height="426" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiJHnfWJNjtuE_7bb9C-hW38yzF34W57_Ev9JRclwW7rCAw5EDf8VcgPT59o3pqZ5siNFC2jYttHRUCIL-ca7VocQbmmpHckWZ0lPvMnKMC_TDQNy27B55X2Pa4vxElahL9KJLSuQCvfgGR/w640-h426/IMG_4928+%25282%2529.JPG" width="640" /></a></div><div><br /><div><div class="separator" style="clear: both; text-align: center;"><br /></div><b>What is in the bag?</b><br /><br />For self assembly, the v12.3 model of the BlueFly is supplied with the following components:<br /><ul><li>The BlueFlyVario_Bluetooth_USB_v12 mainboard. There is a small piece of neoprene covering the pressure sensor; glued at one end to hold it in place (do not remove it)</li><li>The translucent blue case with four small screws (P1 screwdriver needed) and the machined acrylic button.</li><li>A 750 mAh single cell Lithium Polymer battery.</li></ul><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgfJqfyer2g5eMRjVo-qOsS_7QfEIgDW31pU6iVgqjUcwzC4Xgkw9ILz7piF7CGRdkeINZ3bWrdKv_cqoeyASW3EbUd2QM6BDeM7xAmRYOlF1Zf7yOvdU3KnJLvYw2Qk9LRrvq_Ht6Pr3Hs/s2048/IMG_4915.JPG" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="1365" data-original-width="2048" height="426" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgfJqfyer2g5eMRjVo-qOsS_7QfEIgDW31pU6iVgqjUcwzC4Xgkw9ILz7piF7CGRdkeINZ3bWrdKv_cqoeyASW3EbUd2QM6BDeM7xAmRYOlF1Zf7yOvdU3KnJLvYw2Qk9LRrvq_Ht6Pr3Hs/w640-h426/IMG_4915.JPG" width="640" /></a></div><br /><div class="separator" style="clear: both; text-align: center;"><br /></div><div><b>Assembly</b></div><br />Assembly is pretty simple and will take most people less than 5 minutes. However, if you would prefer not to touch a screwdriver, you can order the vario fully assembled.<br /><div><br /></div><div><b>Step 1 - Initial Test</b></div><div><br /></div><div>Before you put the board in the case, plug in the battery, press the button, and make sure you can hear the vario beep. Also, plug in a microUSB charging cable and make sure the red LED comes on.</div><div><br /></div><div><b>Step 2 - Fit the button into the case</b></div><div><b><br /></b></div><div>The button should fit neatly into the case as shown in the image below. The machining looks a bit rough under the magnifying glass, but is neat at the surface that matters. You might feel the need to scrape of machine fragments of the case or button with your finger nail. Make sure the button can move easily in the hole. </div><div><b><br /></b></div><div><div class="separator" style="clear: both; text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiNVkhoSnvtvPdQeoCtOlz6gY0g8m9qG0SwOrQXuWC9t5byJRbrAcl8e0QBg3j6YAoxvZmrPcJ-4x7HNXMwTnaRbP3Bbic7ogFQrosD0cg8IH0TFXm5I2RIDIjy7Rv3EdBM_-1jgw-vDMEc/s2048/IMG_4918.JPG" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="1365" data-original-width="2048" height="426" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiNVkhoSnvtvPdQeoCtOlz6gY0g8m9qG0SwOrQXuWC9t5byJRbrAcl8e0QBg3j6YAoxvZmrPcJ-4x7HNXMwTnaRbP3Bbic7ogFQrosD0cg8IH0TFXm5I2RIDIjy7Rv3EdBM_-1jgw-vDMEc/w640-h426/IMG_4918.JPG" width="640" /></a></div><br /></div><div><b>Step 3 - Screw the board into the case </b></div><div><b><br /></b></div><div>Place the board in the case ensuring that the USB connector is in the hole at the end. The USB edge of the PCB should be flush with the inside edge of the case. </div><div><b><br /></b></div><div>The small self tapping M2.5x5mm P1 screws secure the board into the case. You really only need two screws on a diagonal, but there is no harm if your use all four. Don't drive the screws home to tightly or you will strip the stand-offs in the case. Just use enough pressure to ensure that the board is secure. <br /><br /><b>Step 4 - Battery and close</b><br /><br />Plug in the battery and place it on the back of the PCB centrally between all four screws, making sure not to place it on the end of the screws. Then close the case. </div><div><div><b><br /></b></div><div><b>Step 5 - Check charging works</b></div><div><b><br /></b></div><div>Plug in a microUSB cable to charge the vario. The red light should come on. Cables with longer tongues work better. </div></div><div><br /></div><div><div><b>Step 6 - Velcro and/or lanyard (optional)</b></div><div><b><br /></b></div><div>Many pilots will put a small piece of velcro on the back of the vario to attach it to their flight deck (this is what I do). Others will drill some small holes in the case and attach a lanyard (I do not do this anymore). </div></div><div><br /></div><div><b>Next Steps</b></div><div><br /></div><div>After install you probably want to connect to the BFVDesktop application to adjust settings, or connect to and Android or iOS device to experiment with different apps. See the <a href="https://www.blueflyvario.com/software/">software page</a> for more information. </div></div></div></div>Flying Alhttp://www.blogger.com/profile/04770253154348277404noreply@blogger.comtag:blogger.com,1999:blog-4078676472481844653.post-10107852857744699082019-08-04T02:24:00.001-07:002019-08-17T15:14:12.269-07:00GPS Logging on the Bluefly with the XA1110<div dir="ltr" style="text-align: left;" trbidi="on">
This post is about using onboard logging capability of the XA1110 GPS on the Bluefly. It gets technical, and then I finish by suggesting for most pilots that you probably do not need it.<br />
<br />
For many years the Bluefly varios have had the ability to stream a GPS signal to an app like xcsoar or XCTrack on Android (for the Bluetooth model), or to xcsoar on the Kobo (for the TTL_GPS model). Most pilots will use the logging capabilities of those apps to keep a record of their flights or to submit them for competition flying. However, the XA1110 has a small onboard memory and can record its own log. This post tells you how to use it if you feel like experimenting.<br />
<br />
<b>What models does this post relate to?</b><br />
<br />
Any model of the bluefly which is connected to the XA1110 GPS. This includes:<br />
<br />
<ul style="text-align: left;">
<li>BlueFlyVario_Bluetooth_USB_v12 with the <a href="http://blueflyvario.blogspot.com/2019/06/blueflygpsaddonv12-released.html">Bluely_GPS_Addon_v12</a> (this configuration was the real reason for this post)</li>
<li><a href="http://blueflyvario.blogspot.com/2018/07/blueflyvariottlgpsv12-released.html">BlueFlyVario_TTL_GPS_v12</a></li>
</ul>
<br />
The XA1110 GPS uses the MediaTek MT3333 chipset which has the 'Locus' function that the logging is based on. If you have another GPS using this chipset, or perhaps even some other MediaTek chipset, then you might find you can interact with its Locus memory in a similar way.<br />
<br />
<b>Why would you want to do this?</b><br />
<br />
Upfront, I would say that in many cases you probably do not want to do mess with the logging capabilities of the XA1110. For most of our flying adventures keeping a GPS track log is nice to have but is not essential. If you keep your android or iphone battery charged then it is probably better to record a log on whatever app you are using.<br />
<br />
However, if you want a backup to your backup, then switching on the Locus of your XA1110 might be for you. One day, if the competition director is pleasant, it might be your last resort to prove that you made goal. Although, it is important to note that the IGC that you might produce from GPS Babel is unsigned.<br />
<br />
<b>How the XA1110 Locus GPS Log works</b><br />
<br />
The Locus log is pretty simple:<br />
<ul style="text-align: left;">
<li>If the GPS has a fix, and logging is 'started', then logging will begin.</li>
<li>The logging interval can be changed from 1 second to 12 hours (in theory).</li>
<li>Each log point stores time, latitude, longitude, and GPS altitude (each point uses 16 bytes).</li>
<li>The memory size is 128k, which means it can store 8192 points. At 1s track intervals that is only 2.27 hours, but at 10s intervals it provides almost 24 hours of logging. I think that is reasonable for the kind of use case I am considering in this blog post (a backup to the backup).</li>
<li>Once the log reaches the end, the GPS just begins to overwrite points from the start of the log. </li>
</ul>
The main drawback of the log is that it is painful to access. You need to send specific commands to the XA1110 to configure, start and restart logging (see the <a href="https://source.sierrawireless.com/resources/airprime/software/airprime_gmm_g3_xa11xx_and_xm11xx_software_user_guide/">XA1110 Software User Guide</a> for more information). I had hoped that if we start logging that it would continue it after the GPS had rebooted, but I found this only works if VBACKUP is connected and the GPS hot starts. The log needs to be manually started on each cold start.<br />
<br />
<b>Firmware update </b><br />
<br />
In order to simplify the commands, a few days ago I uploaded new <a href="https://www.blueflyvario.com/firmware/">firmware</a> (BlueFlyVario_12.M25). This firmware includes one new hardware setting <b>gpsLogInterval</b> (<i>code BGL</i>).<br />
<br />
Updating the firmware on the TTL_GPS model is a pain as you will need to remove your Bluefly from the Kobo, connect it to a USB_Serial converter, then updated it using the ds30loader application from a Windows PC. It is much easier for the Bluetooth_USB model. In either case, if you manage to update your firmware then it works like this:<br />
<ul style="text-align: left;">
<li>If gpsLogInterval is set to 0, then it turns off the log. </li>
<li>In all other cases, the Bluefly sends the following commands to the XA1110 on startup (or when gpsLogInterval is changed):</li>
<ul>
<li>A test command (PMTK000)</li>
<li>The command to set the log interval (PMTK187,1,{<i>BGL Value}</i>)</li>
<li>The command to start logging (PMTK185,0)</li>
<li>The command to query the locus (PMTK183)</li>
</ul>
<li>This results in an output from the Bluefly like:</li>
</ul>
<span style="color: #666666; font-size: x-small;">$PMTK001,0,3*30</span><br />
<div>
<div>
<span style="color: #666666; font-size: x-small;">$PMTK001,187,3*3E</span></div>
<div>
<span style="color: #666666; font-size: x-small;">$PMTK001,185,3*3C</span></div>
<div>
<span style="color: #666666; font-size: x-small;">$PMTKLOG,16,0,a,31,10,0,0,0,3837,48*20</span></div>
<div>
<span style="color: #666666; font-size: x-small;">$PMTK001,183,3*3A</span></div>
</div>
<br />
<div>
You can decipher this using the XA1110 Software User Guide if you feel you must, but the bottom line is that it shows that logging is happening at 10s intervals. </div>
<div>
<br /></div>
<div>
<b>BFVDesktop application update</b></div>
<div>
<br /></div>
<div>
I have also updated the <a href="https://www.blueflyvario.com/software/">BFVDesktop application</a>. Version 0.61 includes the gpsLogInterval hardware setting. In addition, there are a few PMTK commands in the Hardware Commands drop-down to query the locus (PMTK185,0), erase the log (PMTK184,1), and download the log (Query Locus Data - PMTK622,0). To download a log use these steps:</div>
<div>
<ul style="text-align: left;">
<li>Make sure you can see GPS sentences. You might need to set uart1BRG to 16 to make sure that data rate of U1 (which the XA1110 is connected to) is set to 115200.</li>
<li>Note your outputMode setting, then adjust it to 4 (to disable the bluefly output). You should still see GPS sentences. </li>
<li>Send PMTK622,0 to begin downloading the log. You should see sentences like:</li>
</ul>
</div>
<span style="color: #666666; font-size: x-small;">$PMTKLOX,0,1366*6B</span><br />
<div>
<div>
<div>
<span style="color: #666666; font-size: x-small;">1563683257,2019-07-202T04:27:37Z,2,-35.39281,149.20744,681</span></div>
<div>
<span style="color: #666666; font-size: x-small;">1563683258,2019-07-202T04:27:38Z,2,-35.392807,149.20744,681</span></div>
<div>
<span style="color: #666666; font-size: x-small;">$PMTKLOX,1,0,0100000A,1F000000,01000000,00001F0A,00000000,00000000,00000000,00000000,00000000,00000000,00000000,0000001F,FFFFFFFF,FFFFFFFF,FFFFFFFF,000C8C14,B9E9335D,023D920D,C21B3515,43A9028F,BAE9335D,023C920D,C21B3515,43A9028D*5F</span></div>
<div>
<span style="color: #666666; font-size: x-small;">1563683259,2019-07-202T04:27:39Z,2,-35.39281,149.20744,681</span></div>
<div>
<span style="color: #666666; font-size: x-small;">1563683260,2019-07-202T04:27:40Z,2,-35.39281,149.20744,681</span></div>
<div>
<span style="color: #666666; font-size: x-small;">1563683261,2019-07-202T04:27:41Z,2,-35.39281,149.20744,681</span></div>
<div>
<span style="color: #666666; font-size: x-small;">1563683262,2019-07-202T04:27:42Z,2,-35.392803,149.20744,681</span></div>
<div>
<span style="color: #666666; font-size: x-small;">1563683263,2019-07-202T04:27:43Z,2,-35.392803,149.20746,681</span></div>
<div>
<span style="color: #666666; font-size: x-small;">1563683264,2019-07-202T04:27:44Z,2,-35.392803,149.20746,681</span></div>
<div>
<span style="color: #666666; font-size: x-small;">$PMTKLOX,1,1,BBE9335D,023D920D,C21B3515,43A9028D,BCE9335D,023D920D,C21B3515,43A9028A,BDE9335D,023D920D,C21B3515,43A9028B,BEE9335D,023B920D,C21B3515,43A9028E,BFE9335D,023B920D,C21C3515,43A90288,C0E9335D,023B920D,C21C3515,43A902F7*5B</span></div>
<div>
<span style="color: #666666; font-size: x-small;">1563683265,2019-07-202T04:27:45Z,2,-35.392807,149.20746,681</span></div>
<div>
<span style="color: #666666; font-size: x-small;">1563683266,2019-07-202T04:27:46Z,2,-35.39281,149.20746,681</span></div>
<div>
<span style="color: #666666; font-size: x-small;">1563683267,2019-07-202T04:27:47Z,2,-35.39281,149.20746,681</span></div>
<div>
<span style="color: #666666; font-size: x-small;">1563683277,2019-07-202T04:27:57Z,2,-35.39282,149.20746,681</span></div>
</div>
<ul style="text-align: left;">
<li>Note the PMTKLOX sentences are from the XA1110 GPS in the funky 6 x 16 byte format. The other sentences are CSV separated interpretations from the BFV Desktop application.</li>
<li>It takes about 1 minute to download the log over a 115200 connection. </li>
<li>You will find two files in your BFVDesktop folder. </li>
<ul>
<li>locus_record.csv is all valid track points that were decoded from the locus log. You might use this to view the points in excel</li>
<li>locus_record.mtk are the complete log PMTKLOX sentences. Use <a href="https://www.gpsbabel.org/">GPSBabel</a> to convert that '<a href="https://www.gpsbabel.org/htmldoc-development/fmt_mtk_locus.html">MediaTek Locus</a>' file to any tracklog format you want (like FAI/IGC...). </li>
<li>Note that the points are not ordered by date. You will probably need to do some manual editing to create a log that makes sense. </li>
<li>Also note that the points are not split into flights. Again, some manual editing will be required to work out when your flight started and finished (remember, this is the backup to the backup...)</li>
</ul>
<li>When you are done, set your outputMode back to whatever you started with. </li>
</ul>
<div>
<b>Notes for a Kobo</b></div>
<div>
<br /></div>
<div>
I have not tested this on a Kobo yet. However, if you have a TTL_GPS setup on a Kobo (with the updated firmware), and you want to get your locus record, then I would experiment with the following procedure:</div>
<div>
<ul style="text-align: left;">
<li>Create a <a href="http://gethighstayhigh.co.uk/xcsoar-tips/">custom xci file</a> to create some menu options send the appropriate commands to the Bluefly. </li>
<li>Turn on NMEA logging to record the raw output from the Bluefly. </li>
<li>Send the PMTK622,0 command to begin downloading the PMTKLOX. </li>
<li>Copy the NMEA log, and edit it excel to copy all of the PMTKLOX sentences to a new file. </li>
<li>Convert that file using GPS Babel. </li>
</ul>
<div>
If updating the firmware is beyond you, then you might be able to create some other mechanism to send the appropriate commands to commence logging when xcsoar events occur. </div>
</div>
<div>
<br /></div>
<div>
<b>The bottom line</b></div>
</div>
<br />
<div>
If you have read this far, then you probably have worked out that the XA1110 Locus thing with the Bluefly is probably to much hard work for not much benefit. I really just did this to prove to myself that I could. If you really want to do it then I suggest you experiment before relying on it as a backup. </div>
</div>
Flying Alhttp://www.blogger.com/profile/04770253154348277404noreply@blogger.comtag:blogger.com,1999:blog-4078676472481844653.post-551512539217079332019-06-29T21:31:00.000-07:002019-07-10T14:35:50.741-07:00BlueFlyVario_Bluetooth_USB_v12.2 released<div dir="ltr" style="text-align: left;" trbidi="on">
The <a href="http://blueflyvario_bluetooth_usb_v12.2/">BlueFlyVario_Bluetooth_USB_v12.2</a> is a minor update to the previous version released a few years ago. The classic model of the Bluefly has a fancy new translucent blue case and is easier to assemble. Please read this post in conjunction with the <a href="https://blueflyvario.blogspot.com/2017/01/blueflyvariobluetoothusbv12-released.html">release post for the BlueFlyVario_Bluetooth_USB_v12</a> to understand the changes.<br />
<br />
<b>Translucent Blue Case</b><br />
<br />
The new translucent blue case is an upgrade on the sky blue case that has been used for the last few years. The new case includes the following improvements:<br />
<br />
<ul style="text-align: left;">
<li>It incorporates stand-offs in the design, which makes the connection between the mainboard and the case more secure. </li>
<li>Cutouts are very slightly larger. </li>
<li>The lid is secured with different clips, which are much more secure than the older case. </li>
</ul>
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjp3ABiEBFlpwZ4eHfJVsILpULXHwM4tinRs1kw9BuvkPuvgy8TMvRDvtn_TIfSaE3djWjr2_k2AYZ-FVnN9q1wa7pdlFg09DOILtHwQw0j9wbWAJpyT53Z6cdCRQJg4Hq7SSu-nJu5Tobp/s1600/IMG_3028.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="1067" data-original-width="1600" height="426" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjp3ABiEBFlpwZ4eHfJVsILpULXHwM4tinRs1kw9BuvkPuvgy8TMvRDvtn_TIfSaE3djWjr2_k2AYZ-FVnN9q1wa7pdlFg09DOILtHwQw0j9wbWAJpyT53Z6cdCRQJg4Hq7SSu-nJu5Tobp/s640/IMG_3028.JPG" width="640" /></a></div>
<br />
<b>What is in the bag?</b><br />
<br />
The v12 model of the BlueFly is supplied with the following components:<br />
<ul style="text-align: left;">
<li>The BlueFlyVario_Bluetooth_USB_v12 mainboard. There is a small piece of neoprene covering the pressure sensor; glued at one end to hold it in place (do not remove it!)</li>
<li>The translucent blue case with four small screws (P1 screwdriver needed).</li>
<li>A 750 mAh singe cell Lithium Polymer battery. </li>
</ul>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhpqe0bmiLbmcefWoWGAibwiR0tupDk-8gCoB7qQuVd9-RH8KT6_Ir0hS9tja0w3grDGdrzZZ_-3c2v6IxqLiMNIwXM4g1gR11O6nf4CiriL7SCx_YxPAb0KhVd7605iEgK12G077gnPZ-v/s1600/IMG_3067.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="1067" data-original-width="1600" height="426" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhpqe0bmiLbmcefWoWGAibwiR0tupDk-8gCoB7qQuVd9-RH8KT6_Ir0hS9tja0w3grDGdrzZZ_-3c2v6IxqLiMNIwXM4g1gR11O6nf4CiriL7SCx_YxPAb0KhVd7605iEgK12G077gnPZ-v/s640/IMG_3067.JPG" width="640" /></a></div>
<div>
<br /></div>
<b>Assembly</b><br />
<br />
Assembly is pretty simple and will take most people less than 5 minutes. However, if you would prefer not to touch a screwdriver, or you want your vario configured to your custom settings, you can order the <a href="https://www.blueflyvario.com/product-category/services/">simple assembly service</a>.<br />
<div>
<br /></div>
<div>
The simpler assembly method refines the steps outlined in the initial release:</div>
<div>
<br /></div>
<div>
<b>Step 1 - Initial Test</b></div>
<div>
<br /></div>
<div>
Before you put the board in the case, plug in the battery, press the button, and make sure you can hear the vario beep. Also, plug in a microUSB charging cable and make sure the red LED comes on.</div>
<div>
<br /></div>
<div>
<b>Step 2 - Screw the board into the case </b></div>
<div>
<b><br /></b></div>
<div>
The small self tapping M2.5x5mm P1 screws secure the board into the case as shown below. You really only need two screws on a diagonal, but there is no harm if your use all four. Don't drive the screws home to tightly or you will strip the stand-offs in the case. Just use enough pressure to ensure that the board is secure. </div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjcO0lsBvSMr1hJcrlQOaxUtemKjPBjCpXrYKHQJjbvqQKKNNFUliViPD0NLE9NbrNp6tFXoB2JWuNecQpglOL5412bEh4toym6OfWpFxO5Ip7w7fKaV6raWEMm2PmsJ9Df8zlH-rkYv2xu/s1600/IMG_3071.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="1067" data-original-width="1600" height="426" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjcO0lsBvSMr1hJcrlQOaxUtemKjPBjCpXrYKHQJjbvqQKKNNFUliViPD0NLE9NbrNp6tFXoB2JWuNecQpglOL5412bEh4toym6OfWpFxO5Ip7w7fKaV6raWEMm2PmsJ9Df8zlH-rkYv2xu/s640/IMG_3071.JPG" width="640" /></a></div>
<div>
<br />
<div>
<b>Step 3 - Ensure the button is aligned </b></div>
<div>
<b><br /></b></div>
<div>
The button should be aligned with the center of the cutout hole. If it is off center and touching the edge of the hole then the case will interfere with the proper operation of the button. If you need to adjust it unscrew the screws by one turn or so, just enough so you can move the board around, then tighten them again. </div>
<div>
<br /></div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh59deyrywcwePfAmG1QPYcEgt2amx-Rjln8YsAuO0moVCB6saxvCOe-4ugu6vsqE0mXS08Y7nZJ8MxOWIj5k9JSGJ9gagf2D32JTtA6pnNvf4v2olB_iNyNeXLbLOMC-r08l1cTk_FK9pH/s1600/IMG_3073.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="1067" data-original-width="1600" height="426" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh59deyrywcwePfAmG1QPYcEgt2amx-Rjln8YsAuO0moVCB6saxvCOe-4ugu6vsqE0mXS08Y7nZJ8MxOWIj5k9JSGJ9gagf2D32JTtA6pnNvf4v2olB_iNyNeXLbLOMC-r08l1cTk_FK9pH/s640/IMG_3073.JPG" width="640" /></a></div>
<div>
<br /></div>
<div>
<b>Step 4 - Battery and close</b></div>
<div>
<b><br /></b></div>
<div>
Plug in the battery. Place it in the case, making sure not to place it on the end of the screws. Then close the case. There is no longer any need to use tape to keep the case closed (the new lid clips are much more secure), nor any need to secure the battery (it fits snugly). </div>
<div>
<b><br /></b></div>
<div>
<b>Step 5 - Check charging works</b></div>
<div>
<b><br /></b></div>
<div>
Plug in a microUSB cable to charge the vario. The red light should come on. Cables with longer tongues work better. </div>
</div>
<div>
<br /></div>
<div>
<div>
<b>Step 6 - Velcro and/or lanyard (optional)</b></div>
<div>
<b><br /></b></div>
<div>
Many pilots will put a small piece of velcro on the back of the vario to attach it to their flight deck (this is what I do). Others will drill some small holes in the case and attach a lanyard (I do not do this anymore). </div>
</div>
<div>
<br /></div>
<div>
<b>Next Steps</b></div>
<div>
<br /></div>
<div>
After install you probably want to connect to the BFVDesktop application to adjust settings, or connect to and Android or iOS device to experiment with different apps. See the <a href="https://www.blueflyvario.com/software/">software page</a> for more information. </div>
</div>
Flying Alhttp://www.blogger.com/profile/04770253154348277404noreply@blogger.comtag:blogger.com,1999:blog-4078676472481844653.post-14731595346717129682019-06-29T18:36:00.001-07:002019-09-13T15:00:36.037-07:00Bluefly_GPS_AddOn_v12 Released<div dir="ltr" style="text-align: left;" trbidi="on">
I am pleased to be able to release the <a href="https://www.blueflyvario.com/product/gps_addon/">Bluefly_GPS_AddOn_v12</a> board today. Adding a GPS to the Bluefly has been possible for many years (see this post for an example <a href="http://blueflyvario.blogspot.com/2017/08/blueflyvariousbv12-released.html">http://blueflyvario.blogspot.com/2017/08/blueflyvariousbv12-released.html</a>). This new board is designed especially for the Bluefly and uses the XA1110 module which offers a range of premium features.<br />
<br />
Before reading on, why would you want to add a GPS to the Bluetooth model of the Bluefly? For many pilots the answer is you probably do not. If you are using the Bluefly in stand alone mode (just using it's audio), or if you are connecting to almost any Android or iOS device, then that device probably already has a GPS. However, there are a few Android devices that do not have GPS such as Android based eReaders that some pilots are now using with XCSoar. The Bluetooth model of the Bluefly with this new GPS board can provide the location input you need for XCSoar or other apps.<br />
<br />
<b>Features</b><br />
<b><br /></b>
The image below shows the layout of the board.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhbM8rn-qbEK9qPwQLtans6IWr0xQUO6RGmmtzAqiVZWtim5Fij8ecgrW5-zj3_Yy7tHxzA3-dUyXOS_QrZcAszRBarOfEOAAaD39ktaIDN7rcERroANXvqWWW-o_tKourP0Ii2KrvUdnj8/s1600/Bluely_GPS_AddOn_v12_Layout.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="720" data-original-width="960" height="480" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhbM8rn-qbEK9qPwQLtans6IWr0xQUO6RGmmtzAqiVZWtim5Fij8ecgrW5-zj3_Yy7tHxzA3-dUyXOS_QrZcAszRBarOfEOAAaD39ktaIDN7rcERroANXvqWWW-o_tKourP0Ii2KrvUdnj8/s640/Bluely_GPS_AddOn_v12_Layout.png" width="640" /></a></div>
<br />
Features of the board are:<br />
<br />
<ul style="text-align: left;">
<li>The <a href="https://www.sierrawireless.com/products-and-solutions/embedded-solutions/products/xa1110/">XA1110 Mulit-GNSS module from Sierra Wireless</a>. </li>
<li>It's own 3.0v Voltage Regulator and conditioning components for optimal performance. </li>
<li>The blue LED flashes once per second when the GPS has a fix. </li>
<li>The main connectors are:</li>
<ul>
<li>The U1 connections to the Bluefly for Ground, Tx, Rx and 3.3v input. </li>
<li>RA7 enables the voltage regulator (you need the most recent version of the firmware for the Bluetooth model of the Bluefly for this to work). </li>
<li>VBAT connects to the GPS VBACKUP for fast time-to-first-fix (about 5 seconds) and maintains other configuration settings on the GPS. You need to close the solder jumper for this to work. </li>
</ul>
<li>There are pads for a U.Fl connector for those that want to experiment with an external antenna. </li>
</ul>
<br />
<b>Assembly</b><br />
<br />
Assembly is pretty easy if you have basic soldering skills. Before you begin read through all of these steps. If you are really uncomfortable doing this yourself then I am also able to offer an <a href="https://www.blueflyvario.com/product/complex-assembly/">assembly service</a> (but note that this makes the size of the package greater than can be shipped with free shipping).<br />
<br />
<b>Step 1 - Checking your Bluefly </b><br />
<b><br /></b>
To complete your the assembly process your Bluefly will need to be removed from the case. Do this carefully by first removing the battery and any packing holding the vario in position. Next use a small flat screwdriver and gently twist between the end of the PCB and the end of the case with the USB hole. The aim is to release the end tabs of the USB connector from the hole, then press on the button to push the PCB free from the case. If you are gentle the PCB should come out easily, and you will not damage the button or the USB connector.<br />
<br />
Next, plug the battery back in and connect to the <a href="https://www.blueflyvario.com/software/">BFVDesktop application</a> on a windows PC. Send the 'BTN' command a few times just to make sure you have a good connection to the vario. You need <a href="http://blueflyvario.blogspot.com/2019/06/firmware-manual-and-bfvdesktop-updates.html">firmware version 12.423</a> or later for this to work.<br />
<br />
<b>Step 2 - Attaching the GPS_AddOn</b><br />
<br />
Begin by soldering headers to U1, RA7 and VBAT as shown below (I will include a strip of 6 or more headers in the package with the AddOn board). Note that I have used right angled headers in this image, but you can also use straight headers. <u>I strongly suggest that you trim the pin of the headers flush with the board before you solder it (not shown in this image). This will help prevent the LiPo battery from damage.</u> Also note that the secret of all good soldering is lots of flux, a clean hot soldering iron with quality solder, and good cleaning with isopropyl alcohol after soldering.<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgv508sUtsPje7o77cO0bTJXIpWRFe8LxcZjNuv8jkT4u98Ke9wFM1rHWEJCiscJ7XhUopIn7NUQQdGfSXXPDjIp6Xuy83nMtnpkbXP22GQSeFFbVUNPWkaxU7y15fJdvDGtArWWebGF-OB/s1600/IMG_3007.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="1067" data-original-width="1600" height="266" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgv508sUtsPje7o77cO0bTJXIpWRFe8LxcZjNuv8jkT4u98Ke9wFM1rHWEJCiscJ7XhUopIn7NUQQdGfSXXPDjIp6Xuy83nMtnpkbXP22GQSeFFbVUNPWkaxU7y15fJdvDGtArWWebGF-OB/s400/IMG_3007.JPG" width="400" /></a></div>
<br />
<div class="separator" style="clear: both; text-align: left;">
Next, attach the AddOn board. Note that it sits flush on top of the bluetooth module shield, and slightly squishes the neoprene. Again, trim the headers before soldering. </div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhk5H5Wl8hsK35Zehz-03EZN5Zv3FduV6C0NaaoLmkeMoLQV5ND5_Snbt_1m4_Ck016LSHCgyOljwYslmg-Sf6vUxxHSb3gfGi5wdcYiNZV1ycBW8mKtBrz7ievi5hVCWiAnBkHpuf18fxk/s1600/IMG_3009.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="1067" data-original-width="1600" height="266" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhk5H5Wl8hsK35Zehz-03EZN5Zv3FduV6C0NaaoLmkeMoLQV5ND5_Snbt_1m4_Ck016LSHCgyOljwYslmg-Sf6vUxxHSb3gfGi5wdcYiNZV1ycBW8mKtBrz7ievi5hVCWiAnBkHpuf18fxk/s400/IMG_3009.JPG" width="400" /></a></div>
<br />
This final image shows the required pins soldered. <u>Also, note that the VBAT solder jumper has been closed.</u><br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi1Pm9BR3RDoWmr5DZsBn3xweospR1YMjGWB19rT5_k_aYNkmNqqyvJNDPIkVkNlATDYnZVLX7FJD64QKwJPmOmOWLwPyYlAdR1GBxWXF1rqxI9gry5pHYP84E-tiDr2HPaXHH-4PaMcAuY/s1600/IMG_3012.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="1067" data-original-width="1600" height="266" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi1Pm9BR3RDoWmr5DZsBn3xweospR1YMjGWB19rT5_k_aYNkmNqqyvJNDPIkVkNlATDYnZVLX7FJD64QKwJPmOmOWLwPyYlAdR1GBxWXF1rqxI9gry5pHYP84E-tiDr2HPaXHH-4PaMcAuY/s400/IMG_3012.JPG" width="400" /></a></div>
<br />
<b>Step 3 - Configuration</b><br />
<br />
At this point, before putting it in the case, it is a good idea to test to make sure it is working. Follow these steps:<br />
<br />
<ul style="text-align: left;">
<li>Connect the vario to the BFVDesktop application and start it up. You should see the vario data streaming in. </li>
<li>Adjust <b>uart1BRG</b> from the default of 207 to 16. That changes the U1 baud rate (the rate between the vario microcontroller and the GPS module) from 9600 to 115200. </li>
<li>You should now see data from the GPS streaming in. Change the <b>outputMode</b> to 4 to disable the Bluefly sentences and you will be left with just the GPS information. </li>
<li>Shut down and restart the Bluefly. After a few minutes, if the antenna is pointing to the sky, you should get your first fix (and the blue light on the under side of the GPS board will start to blink). </li>
<li>Shut down and restart the Bluefly again. If you have VBAT connected correctly and the solder jumper has been closed then the time-to-first-fix should be no more than 5 to 10 seconds. </li>
<li>Make sure to set the <b>outputMode </b>and <b>outputFrequency </b>back to whatever you want for connecting to your app.</li>
</ul>
<br />
<b>Step 4 - Prepare the case</b><br />
<b><br /></b>
The Bluefly with GPS_AddOn fits in the Sky Blue or new Translucent Blue case provided you cut out a hole for the GPS.<br />
<br />
Begin by downloading the <a href="https://www.blueflyvario.com/files/BlueFlyVario_Bluetooth_v12_GPSShield_markup.pdf">pdf template</a> to use to cut the hole in the right spot. The only really tricky part is to make sure you print the template at the right scale. The images below show the template and final cutout.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjkidQ8iuSNaSuEfvGsuOfjm8P3RPDvY1G5r6hQ4X2oMDANKnOehBGwhyphenhyphen4RvKSxzKlN4UkPSzvA0OnIJvP1llXFx3RRo8PTv6qSAn6arDrfKMMDAGph7IofBDZKD1CyUo4zLXGKtnTGJpa3/s1600/IMG_2992.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="1067" data-original-width="1600" height="266" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjkidQ8iuSNaSuEfvGsuOfjm8P3RPDvY1G5r6hQ4X2oMDANKnOehBGwhyphenhyphen4RvKSxzKlN4UkPSzvA0OnIJvP1llXFx3RRo8PTv6qSAn6arDrfKMMDAGph7IofBDZKD1CyUo4zLXGKtnTGJpa3/s400/IMG_2992.JPG" width="400" /></a></div>
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEis3Cogglcl7D7Ri7kngn_2eLMmc-R1KpZLDs4L2HuR33yco71YteKzDiBRB26Jm8-7IqRmwSpC-Wy1WEyrubppFJxfmwVthThjWIbKeAq4wXVxdO4_iUvsVNini13I33Ep28FKoJzJzpCP/s1600/IMG_3005.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="1067" data-original-width="1600" height="266" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEis3Cogglcl7D7Ri7kngn_2eLMmc-R1KpZLDs4L2HuR33yco71YteKzDiBRB26Jm8-7IqRmwSpC-Wy1WEyrubppFJxfmwVthThjWIbKeAq4wXVxdO4_iUvsVNini13I33Ep28FKoJzJzpCP/s400/IMG_3005.JPG" width="400" /></a></div>
<br />
This final image shows the vario assembled into the older Sky Blue case.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj33_6rPc8vf0A2Cfvlu8WN-7hOThPf1y38H5-WsOX2Wl0YhwIJe2D-iYaj10WQhQ7eNP5Sy5AQ1hBmp-j0FDDMlJhy18lZeTza2_2C0tcUex_YAHdIxiNZZzSzs4bjFKvcDhxO8U5HKidw/s1600/IMG_2995.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="1067" data-original-width="1600" height="266" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj33_6rPc8vf0A2Cfvlu8WN-7hOThPf1y38H5-WsOX2Wl0YhwIJe2D-iYaj10WQhQ7eNP5Sy5AQ1hBmp-j0FDDMlJhy18lZeTza2_2C0tcUex_YAHdIxiNZZzSzs4bjFKvcDhxO8U5HKidw/s400/IMG_2995.JPG" width="400" /></a></div>
<br />
<b>Next Steps</b><br />
<b><br /></b>
Now you have a vario with working XA1110 you may want to experiment with the capabilities of that GPS module. There are many configuration options which you might find useful.<br />
<br />
At some stage I will be blogging about configuring and using the onboard memory of the XA1110 GPS module. With a little effort the GPS can be made to continuously record the last 8186 track points (including height) in its 128k memory. This can provide a backup GPS track for the last 11 hours of GPS on time at 5 second intervals. It is not super awesome, and takes some effort to configure and download the memory, but as a backup track could make the difference for many pilots. </div>
Flying Alhttp://www.blogger.com/profile/04770253154348277404noreply@blogger.comtag:blogger.com,1999:blog-4078676472481844653.post-39979302142028166622019-06-08T16:00:00.000-07:002019-06-08T17:20:03.924-07:00Firmware, Manual, and BFVDesktop updates<div dir="ltr" style="text-align: left;" trbidi="on">
Over the last few days I have found a little time to update and rationalize the firmware for all Bluefly models, update the Hardware Settings Manual, and update the BFVDesktop app used for adjusting the settings. I do not find so much time these days to blog about little updates and improvements, but they are always happening in the background.<br />
<br />
<b>Firmware Updates</b><br />
<br />
The latest firmware is <b>12.M23</b>. I have only provided a few firmware updates since releasing each of the v12 models, and only then on a model by model basis. This firmware update consolidates bug fixes and adds a few new features.<br />
<ul style="text-align: left;">
<li>There is a a new hardware setting <b>quietStart</b>. When set to true then the startup and shutdown beeps do not sound. </li>
<li>The setting <b>startDelayMS</b> described in <a href="http://blueflyvario.blogspot.com/2018/07/blueflyvariottlgpsv12-released.html">this post</a> has now been included in all models. </li>
<li>I have added an experimental <b>outputMode</b> (outputMode=7) to simulate the <a href="https://www.openvario.org/doku.php?id=projects:series_00:software:nmea">OpenVario protocol</a>. </li>
<li>A little bug with the temperature output in outputMode=6 has been fixed. </li>
<li>RA7 for GPS reset on the Bluetooth model has been restored. </li>
<li>Some default settings have been changed. </li>
<li>The settings range has been expanded for many settings. </li>
</ul>
<div>
Bluefly models shipping from mid June 2019 will include this latest firmware. </div>
<div>
<br /></div>
<div>
I do not recommend updating the firmware unless you need a feature or really need to fix a bug. However, if you feel you want to then see the <a href="https://www.blueflyvario.com/firmware/">firmware page on the website</a> and read the Hardware Settings Manual for instructions. After the firmware update don't forget to do the hardware reset procedure by shorting GND and SCL on startup. If you do not do that then you will find that your vario will not start. </div>
<div>
<br /></div>
<div>
<b>Hardware Settings Manual</b></div>
<div>
<br /></div>
<div>
The manual has also been updated to include this, and many other changes I did not get around to documenting. Find it <a href="https://www.blueflyvario.com/support/">here</a>. </div>
<div>
<br /></div>
<div>
<b>BFVDesktop application</b></div>
<div>
<br /></div>
<div>
The BFVDesktop application is used to adjust settings. It has been updated to include the settings described above. Find it <a href="https://www.blueflyvario.com/software/">here</a>. </div>
</div>
Flying Alhttp://www.blogger.com/profile/04770253154348277404noreply@blogger.comtag:blogger.com,1999:blog-4078676472481844653.post-8893011152304891072018-12-12T01:51:00.000-08:002018-12-12T01:51:55.126-08:00The Supair Delight 3<div dir="ltr" style="text-align: left;" trbidi="on">
The <a href="http://www.supair.com/en/produit/delight-3/">Supair Delight 3</a> is a delightful harness - it really lives up to its name!<br />
<br />
This post is loosely related to the Bluefly (in the video below you can see some Blueflys on the Delight 3 flight deck), but is more of a general review of paragliding gear and how it can complement each other.<br />
<br />
During over 20 years of paragliding I have only ever purchased three harnesses for solo flying - the harness I got with my first wing, then about eight or ten years ago a Kortel Karmasutra II (I added a pod about six years ago), and now the Delight 3. In this post I hope to describe why I choose the Delight 3, and after flying it for a bit, what I think about it.<br />
<br />
In a previous blog post I described <a href="https://blueflyvario.blogspot.com/2017/10/flying-nova-mentor-5-in-canberra.html">flying my Nova Mentor 5</a>. In that post you can read about what kind of pilot I am (classic weekend pilot, and more recently with the occasional comp), and what it is like flying around Canberra (technical, mix of mini xc and ridge soaring).<br />
<br />
I purchased the Delight 3 from Mark at <a href="https://www.cloudbaseparagliding.com.au/">Cloudbase Paragliding</a>. It is in his shop <a href="https://www.cloudbaseparagliding.com.au/product/supair-delight3-harness">here</a>. He was great to deal with and shipped it to me very quickly.<br />
<br />
<b>Why the Delight 3?</b><br />
<br />
The decision to move away from my older Kortel Karmasutura II was motivated by its weight and bulk. It is a very comfortable harness in the air, but it is really too heavy to carry up a hill too many times. It is also pretty big, and only fits in my glider bag with a lot of squeezing during pack up. It is lovely in the air, but on launch I was annoyed that it got in the way of my helmet when looking up at the wing, and the pod knocked me in the back of the knees during take-off. I have been looking for the right harness to come along for a while.<br />
<br />
There were a few features I was after in new harness - lightweight, pod, integrated flight deck, and good back protection. The Delight 3 had all of these. I trusted the excellent reviews by <a href="https://flybubble.com/blog/supair-delight-3-harness-review">Flybubble </a>and <a href="http://ziadbassil.blogspot.com/2018/08/supair-delight-3.html">Ziad</a> and decided to order one. Read those reviews as well as this to consider if this harness is for you.<br />
<br />
<b>First Impressions</b><br />
<br />
I have the Delight 3 size M. When I first put my 180cm - 77 kg frame into it I thought I might be right near the top of the size - it was not too small, but it was a bit tight around the hips. However, I was doing the adjustments under a hang point on the ground, and the risers were not wide enough apart to simulate being under a wing. On the ground, I initially let most of the adjustments fully out.<br />
<br />
Since then I have flown it a few times in very rough thermic conditions and very gentle smooth ridge soaring. Every flight I have adjusted everything a bit tighter and now feel that the size M is perfect for me. All of the adjustments have ended up at about the halfway point. Adjusting a harness to match your flying style can be a bit finicky, and this is especially the case for lightweight gear. Now I have tuned the adjustments, the Delight 3 is exceeding my expectations.<br />
<br />
The video below shows the harness in the air during a very early morning ridge soar at Lake George. Please forgive my sloppy camera work and editing.<br />
<div style="text-align: center;">
<br /></div>
<div style="text-align: center;">
<iframe allowfullscreen="" frameborder="0" height="344" src="https://www.youtube.com/embed/_lDJMhWrQ0M" width="459"></iframe>
</div>
<div class="separator" style="clear: both; text-align: center;">
<br /></div>
<div style="text-align: center;">
<br /></div>
<b>Comfort On The Ground</b><br />
<br />
The harness fits nicely into the Nova glider bag with my wing, and I still have room for helmet and lots of other things. I have been really surprised the difference 4 kg makes. Sure, it is much better for hiking up a hill, but I also notice how different it is just putting the glider bag in the car and putting it away when I get home.<br />
<br />
When strapping in ready for launch it feels much more comfortable than my old harness, although the attachment arrangements are very familiar. The integrated flight deck sits a little awkwardly prior to launch at first, but it really only took me one launch to get used to ground handling with it. Overall I can ground handle much easier, actually tilt my head to look at the wing, and the launch process feels a lot tighter.<br />
<br />
<b>Pleasant Flying</b><br />
<b><br /></b>
After launch I found it easy to get into the pod and into sitting position. I still need to adjust my pod straps a bit more to make them tighter, and this will help pull the flight deck closed a little more. The small seat board allows some weight shift control, and when I managed to work out the adjustments any tightness was gone. I like flying a little more upright than many pilots, and the semi rigid back supports that really well.<br />
<br />
I like the extra feeling this harness provides compared to my old one. The Mentor 5 is a high end B wing, and the extra feedback through this harness allows me to squeeze a little more performance from a broken thermal. In the rougher conditions I was thrown about a little, but not too much and it actually gave me more confidence that I could fly the wing more actively.<br />
<br />
The flight deck position is good, and as you can see in the video above is perfect for the Bluefly :)<br />
<br />
<b>Quality Features</b><br />
<b><br /></b>
This is a top quality harness with some great features.<br />
<ul style="text-align: left;">
<li><b>Flight deck</b>. The integrated flight deck is large enough for two main instruments, and one or two little ones. For comps I will end up flying with a Bluetooth model of the Bluefly that I will use for audio, an Android phone running xcosar, the Kobo Mini + TTL_GPS Bluefly, and a Spot. There is enough room behind the flight deck for a backup battery, radio, lunch, and other random things. I like the added extras such as the little loops and clips for attaching instruments, and the hole for a charging cable from the backup battery to the phone. </li>
<li><b>Reserve</b>. The reserve configuration appears smart and accessible. I am flying with a full size reserve, and was able to pack it so that it fits, but can still be test thrown without too much force. </li>
<li><b>Pod</b>. Nice things about the pod include the magnetic closure clips - they just seem to work. The way the speed bar is attached makes it easy to access - but is it still kept out of the way.</li>
<li><b>Internal pockets</b>. The internal pockets on each side under the risers are really handy. One side has the tree attachment carabiner and cable (the one I used for the camera in my test flight), and the other is the same configuration internally but without the cable. I put my camera on a selfie stick in that side. </li>
<li><b>Passive safety</b>. I am familiar with the benefits of passive foam back and under seat protection. I am probably alive because of this kind of protection after a bad accident a few years ago. </li>
</ul>
<div>
<b>Overall Impressions</b></div>
<div>
<b><br /></b></div>
<div>
I am super happy with this purchase - it really is what I was after. The harness is a great match for my high end B wing, works well with my instruments, is comfortable on the ground and in the air, and has a bunch of features that I wanted. I am not sure that I could suggest any improvements to the Supair designers.<br />
<br /></div>
<br />
<br />
<br />
<br /></div>
Flying Alhttp://www.blogger.com/profile/04770253154348277404noreply@blogger.comtag:blogger.com,1999:blog-4078676472481844653.post-59468237476247430962018-12-07T13:22:00.001-08:002018-12-07T13:27:09.426-08:00BlueFlyVario_TTL_GPS_v12 firmware update<div dir="ltr" style="text-align: left;" trbidi="on">
<div class="separator" style="clear: both; text-align: center;">
</div>
<div class="separator" style="clear: both; text-align: center;">
</div>
Today I have released a firmware update for the BlueFlyVario_TTL_GPS_v12 (<a href="https://www.blueflyvario.com/firmware/">firmware version 12.219</a>). This update changes the way data from the on board XA1110 GPS is cached by Bluefly processor and multiplexed with the normal Bluefly output. Updating the firmware on a Bluefly attached to a Kobo requires that it be removed, so this post also describes how you can use an xci file to adjust the GPS without having to update the firmware.<br />
<br />
When the TTL_GPS_v12 model of the Bluefly was <a href="http://blueflyvario.blogspot.com/2018/07/blueflyvariottlgpsv12-released.html">released</a> the GPS module was upgraded. The new XA1110 GPS module communicates with the Bluefly processor over UART at 115200 baud. A few months ago some issues were found when using the Bluefly with LK8000 that we thought that were being caused by occasional errors in the communication. This knowledgeable article describes how to <a href="https://www.blueflyvario.com/knowledgebase/change-the-blueflyvario_ttl_gps_v12-gps-data-rate/">c<span id="goog_2134825175"></span>hange the baud rate</a> as a workaround.<br />
<br />
However, additional testing discovered that in some circumstances (such as when tracking a lot of satellites), too much UART data was being sent from the XA1110 in a short time and the Bluefly could not keep up. This was causing errors in some re-transmitted GPS sentences, and some sentences were even being dropped. Location sentences are being transmitted successfully, which is why initial testing did not pick up the bug. <br />
<br />
The firmware update described in this blog post allows the Bluefly processor to cache the GPS data in a more robust way. Many hours of testing suggests that all GPS sentences will now be transmitted without error. <br />
<br />
Thanks to those Bluefly users who helped us workout the bug.<br />
<br />
<b>What models are affected?</b><br />
<br />
The bug affects BlueFlyVario_TTL_GPS_v12 (with the XA1110 GPS/GLONASS module) shipped between initial release on 7 Jul 2018 to and 27 Nov 2018. Varios shipped from 28 Nov 2018 date have the updated firmware. <br />
<br />
This firmware update does not apply to the Bluetooth_USB or USB models of the Bluefly. <br />
<br />
If your vario is installed on a Kobo and you are running xcsoar you can see what version of the firmware you are running by starting (or restarting) the vario while you are looking at the Device monitor (Menu|Config|Devices|Monitor). See the image below which shows the firmware loaded on this device is version 12.218.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg6NCclEHZeshqeKzCf6lyaXatItxnfo2C7CBs4YIix2gIVqWfcHfGQkL7gaCGWO7llOaONOHaczw-THbLxNtV2emnvCLA3Piez4BRffFsJ2W0EaZdChv8N3JJ1quRnTavtL1sx9ntIOjYS/s1600/IMG_2985_LI.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="1067" data-original-width="1600" height="426" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg6NCclEHZeshqeKzCf6lyaXatItxnfo2C7CBs4YIix2gIVqWfcHfGQkL7gaCGWO7llOaONOHaczw-THbLxNtV2emnvCLA3Piez4BRffFsJ2W0EaZdChv8N3JJ1quRnTavtL1sx9ntIOjYS/s640/IMG_2985_LI.jpg" width="640" /></a></div>
<div style="text-align: center;">
<br /></div>
<b>What should I do?</b><br />
<br />
If you have firmware 12.2.18 there are a few options:<br />
<div>
<b><br /></b></div>
<div>
<b>Option 1 - Do nothing</b>. If you are happy with the performance of you vario, and it is installed on a Kobo on which you are running xcsoar, then you may wish to do nothing. This will be ok for some pilots, but if you are using your GPS tracks for competitions or want increased confidence in the performance of the GPS then I recommend option 2 or 3.<br />
<br />
<b>Option 2 - Change the baud rate</b>. Changing the baud rate between the Bluefly processor and the onboad XA1110 is a workaround which provides a reliable fix. If your Bluefly is soldered to your Kobo, and you are running xcsoar, then this is probably the easiest thing to do. You can change the baud rate in two ways:<br />
<ul style="text-align: left;">
<li>Use the baud rate update procedure described in the <a href="https://www.blueflyvario.com/knowledgebase/change-the-blueflyvario_ttl_gps_v12-gps-data-rate/">knowledgebase article</a>.</li>
<li>Use <a href="https://www.blueflyvario.com/files/BlueFlyDebug_28Nov18.xci">the BlueFlyDebug_28Nov18.xci file</a> to send the same commands to the Bluefly to change the baud rate, but without having to disconnect it from the kobo. See Nev's extensive information on xci files <a href="http://gethighstayhigh.co.uk/xcsoar-tips/">here</a> for more information on how they work. To to this:</li>
<ol>
<li>First download the xci file to your pc, then get it onto the Kobo in the xcsoardata directory. </li>
<li>Load this xci file to create the BlueFly menu using Menu|Config|System|Language,Input|Events</li>
<li>Restart to apply changes. </li>
<li>Look at the monitor (Menu|Config|Devices|Monitor) to make sure the BlueFly is running by seeing the data is streaming in. The GPS sentences are the ones starting with $G</li>
<li>Check that your new BlueFly menu is working and that you have two way communications with the Bluefly. (Menu|BlueFly|SimulateButton). You should hear a beep as if you were pressing the button on the Bluefly. If you don't hear anything from the Bluefly then there is probably a problem with physical connection and you will need to fix that before continuing. </li>
<li>Go into the GPS Adjustments menu (Menu|BlueFly|GPS Adjustments). </li>
<li>Press Menu|BlueFly|GPS Adjustments|GPS Command Mode. That sends the command PGCMD,380,7 which puts the XA1110 GPS into command mode. Note that xcsoar adds the appropriate checksum and end of line information to the command. </li>
<li>Press Menu|BlueFly|GPS Adjustments|XA1110 9600 Baud. That sends the command PGCMD,231,1 which adjusts the XA1110. </li>
<li>Fully shutdown and restart the Kobo. This ensures that the Bluefly, and its attached XA1110 GPS, are fully powered down and restarted. The baud rate changes to the GPS do not take effect until you have done this restart. </li>
<li>Have a look at the device monitor again. Now you should not see any GPS sentences. We have adjusted the data rate from the XA1110, but now we need to adjust the rate of UART 1 on the Bluefly process so it picks up those sentences. If you do actually see GPS sentences before you have adjusted U1 then you might not have successfully done step 6, 7 and 8. </li>
<li>Change the Bluefly U1 baud rate by pressing Menu|BlueFly|GPS Adjustments|U1 Baud 9600. </li>
<li>Look at the monitor for the last time and you should now see GPS sentences again. The GPS Tx baud rate is 9600, the Bluefly U1 Rx baud rate is 9600, and if you have the defaults the Bluefly U2 Tx baud rate is 115200, which allows it to keep up with the GPS information. </li>
<li>Note that I have also included buttons for adjusting U1 back to 115200, and also for adjusting the XA1110 baud back to 115200.</li>
</ol>
</ul>
Once you have done that, you are still running the older firmware, but the U1 baud rate means that the Bluefly processor with that older firmware can keep up with the GPS data sending rate without errors. </div>
<div>
<br />
<b>Option 3 - Actually update the firmware</b>. To update the firmware you will need a USB serial adapter, the Bluefly must be removed from the Kobo, and you will need the ds30 loader from the firmware page. Removing a Bluefly from a Kobo can be tricky, and if you are not very practiced with good soldering techniques then it is likely you will damage the Bluefly, the Kobo, or both.</div>
<div>
<br /></div>
<div>
The firmware update procedure is the same as for the v11 as described here: <a href="http://blueflyvario.blogspot.com/2016/08/firmware-update-for-v11-models.html">http://blueflyvario.blogspot.com/2016/08/firmware-update-for-v11-models.html</a>.</div>
<div>
</div>
<div>
Alternately, you can ship the TTL_GPS back to me and I will update the firmware for you. If you want to do that please contact me and I will send you the address and instructions. </div>
</div>
Flying Alhttp://www.blogger.com/profile/04770253154348277404noreply@blogger.comtag:blogger.com,1999:blog-4078676472481844653.post-62286135802109812122018-07-07T19:20:00.001-07:002018-07-08T03:28:55.299-07:00BlueFlyVario_TTL_GPS_v12 released<div dir="ltr" style="text-align: left;" trbidi="on">
In April 2016 the <a href="http://blueflyvario.blogspot.com/2016/04/blueflyvariottlgpsv11-released.html">v11 model of the BlueFly TTL_GPS was released</a>. That model is now in use by many thousands of pilots around the world. Most pilots install the TTL_GPS model in a Kobo and run xcsoar. Today I am pleased to release a major update, the BlueFlyVario_TTL_GPS_v12.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
</div>
<b>Why a new model?</b><br />
<br />
This update was driven by the reduced availability of the PA6H GPS used on the v11 (and all earlier BlueFly TTL_GPS models). Just over a year ago <a href="https://www.sierrawireless.com/company/newsroom/pressreleases/2017/04/04-03-2017-sierra_wireless_acquires_gnss_embedded_module_assets_of_globaltop_technology/">Sierra Wireless purchased GlobalTop</a>, the manufacturer of the PA6H. For some time the PA6H module was available, but over the last few months all of my suppliers have run out of stock; I had to choose a new GPS.<br />
<br />
I have selected the <a href="https://www.sierrawireless.com/products-and-solutions/embedded-solutions/products/xa1110/">SierraWireless XA1110</a>. From their website:<br />
<br />
<i>'AirPrime® XA1110 Multi-GNSS Module with Patch Antenna<br /><br />Compact, high-precision, ultrafast TTFF Multi-GNSS positioning with integrated antenna. The XA1110 supports tracking of GPS+Glonass or GPS+Glonass+Galileo satellite system combinations to deliver superior positioning accuracy of <2.5m (with SBAS). Based on MediaTek's latest MT3333 engine, it’s the smallest integrated antenna multi-GNSS module on the market with an ultra-compact form factor of 12.5 x 12.5 x 6.8 mm.'</i><br />
<div>
<br />
<div>
In practice, I feel that there is a significant performance improvement over the PA6H, and some better features:<br />
<ul style="text-align: left;">
<li>GPS + Glonass means quicker fixes and better tracking in many parts of the world. </li>
<li>The smaller size fits better on the board, and allows for a better ground plane layout on the PCB. However, note that the patch antenna is about 1.5mm higher than the PA6H. </li>
<li>For advanced users, there is good documentation on the Sierra Wireless website on sending commands to GPS module to customize its performance (in our case via the BlueFly). </li>
<li>The XA1110 default baud rate is 115200 (this has resulted in some changes outlined below). </li>
</ul>
<b>What is in the bag?</b><br />
<br />
The v12 is supplied with the same parts as the v11:<br />
<ul style="text-align: left;">
<li>The main module. The PCB size is 50mm x 17 mm which is the same as the v11. The speaker, GPS, button and header locations are in the same spot as the v11. </li>
<li>A small piece of neoprene. This is really important. It must be placed over the pressure sensor if the sensor is exposed to any light (even light through a translucent case). The neoprene allows the air pressure through, but stops the light. Light makes the pressure sensor go crazy. It is really important to place it on the pressure sensor with the black foam side down - do not stick it to the pressure sensor - you will block the hole and it will not work!</li>
<li>Some blue PVC heat shrink cut to size. </li>
<ul>
<li>Put the neoprene on the pressure sensor, and the heatshrink evenly over the module.</li>
<li>Use a heat gun, or a hairdryer on hot setting to carefully shrink the plastic around the module.</li>
</ul>
</ul>
<div class="separator" style="clear: both; text-align: center;">
</div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhTSJOOF2ZoQbrqin-PyENdEFePSRigRIt5BpiD1v3t4MkybUuRVR8vruR7QtqOqfKW8ZujIFt6NNe1o5b_lBsIe5-vPRmeNQuwTGEZ-elei3IP6aW6phiCnXdre75L99p-ZDEe_6v_xW-2/s1600/BlueFlyVario_TTL_GPS_v12.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="683" data-original-width="1024" height="426" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhTSJOOF2ZoQbrqin-PyENdEFePSRigRIt5BpiD1v3t4MkybUuRVR8vruR7QtqOqfKW8ZujIFt6NNe1o5b_lBsIe5-vPRmeNQuwTGEZ-elei3IP6aW6phiCnXdre75L99p-ZDEe_6v_xW-2/s640/BlueFlyVario_TTL_GPS_v12.jpg" width="640" /></a></div>
<br />
<b>Hardware changes</b><br />
<br />
There have been a few hardware changes from the v11.</div>
<div>
<ul style="text-align: left;">
<li>Much of the layout is identical, but the components around the GPS have been moved around for better positioning. </li>
<li>The behavior of the blue LED which provides a GPS indication is now different. It is not lit to start with, and then flashes at one pulse per second when the GPS get a fix.</li>
<li>There are a few pads on the back side of the board for users who want to experiment, but I recommend leaving them alone as unless you really know what you are doing:</li>
<ul>
<li>SJ1 is still used to bypass the button function for turning on the module as soon as power is supplied to Vin. I still do not recommend closing this for most installs. If you are considering using it then also consider using the new <b>startDelayMS</b> hardware setting. </li>
<li>There are pads to connect a super small backup battery to the GPS VBACKUP. I feel that this is not needed for most installs, and it actually causes more problems than it solves. The pads are designed for a XH414H-IV01E battery which is currently widely available from ebay and aliexpress. </li>
<li>There are pads for an external antenna header for the XA1110. Before you consider using this you should read the XA1110 documentation in detail so you know what kind of antenna to use. The pads are designed for a U.FL-R-SMT IPEX connector. I have not yet experimented with it very much. </li>
</ul>
</ul>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjx2QVj0CzEUKtpvJQC7ueAhJprKxBi-tXo1nY9zt9_t-Jui-1_YBTr0nxh_NxrzwM758vRIz1QP69w6FKxOdoZqBfjzs26aF52Im33hwnUdRJd3F3TzlRqAmQTTGOrGlha3RQFM4Wi9vSJ/s1600/BlueFlyVario_TTL_GPS_v12b.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="683" data-original-width="1024" height="426" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjx2QVj0CzEUKtpvJQC7ueAhJprKxBi-tXo1nY9zt9_t-Jui-1_YBTr0nxh_NxrzwM758vRIz1QP69w6FKxOdoZqBfjzs26aF52Im33hwnUdRJd3F3TzlRqAmQTTGOrGlha3RQFM4Wi9vSJ/s640/BlueFlyVario_TTL_GPS_v12b.jpg" width="640" /></a></div>
<div>
<br /></div>
</div>
</div>
<div>
<br /></div>
<b>Firmware Changes</b><br />
<br />
New features of the v12 firmware include:<br />
<div>
<ul style="text-align: left;">
<li>There is a new hardware setting called <b>startDelayMS</b>. </li>
<ul>
<li>This adds a startup delay before data is sent to the Kobo. Some models of Kobo do not react well if data is received during the Kobo boot process. If you have closed SJ1, then you might need to adjust this setting to achieve a stable startup. </li>
<li>You can adjust the duration of the delay by sending the command <span style="color: #274e13;"><b>$BDM DELAY*</b></span>, where DELAY is the delay in milliseconds.</li>
<li>If <b>startDelayMS </b>is set to anything other than zero then you will hear two very short high pitched beeps as soon as the vario is started, then the delay happens, then the normal vario start up procedure kicks in and data starts flowing from the BlueFly. </li>
<li>The default setting is 0. </li>
</ul>
<li>Some default values for hardware settings have changed:</li>
<ul>
<li><b>uart2BRG </b>(BR2) = 16. The default baud rate between the BlueFly and the Kobo is now 115200, which is now the same for all of the Kobo models. </li>
<li><b>uart1BRG</b> (BRG) = 16. This sets the baud rate between the BlueFly processor and the onboad GPS to 115200. </li>
<li><b>heightSeconds</b> (BHT) = 3600. This changes the default auto power off from 600 seconds (10 minutes) to 3600 seconds (1 hour).</li>
<li><b>toggleThreshold</b> (BTT) = 2000. This changes the auto toggle back on feature to react to 20 m/s lift or sink, instead of 1 m/s lift of sink. Most pilots prefer to just use the button to turn the sound on and off. </li>
</ul>
<li>The maximum value for all hardware settings is now 65534 (0xFFFE), although I am yet to update the BFV Desktop app. </li>
<li>Some pitot related code has been updated for those advanced tinkerers who are experimenting with an airspeed sensor. </li>
</ul>
<b>Installation</b><br />
<br />
See this <a href="http://blueflyvario.blogspot.com/2016/07/kobo-glo-hd-install.html">previous post for an example of how to install the vario on the Kobo Glo HD</a>. There are many links on that post that describe a few different ways to install the vario.<br />
<br />
Also, see <a href="http://gethighstayhigh.co.uk/kobo-self-build/">Nev's page for many examples</a> of which serial port to use on different models, and for a great explanation of how to create a custom xci file.<br />
<br />
I still feel the simple install is best. The image below shows a simple installation on the Kobo Glo HD. I normally just attach the vario to the bevel which is closest to the internal serial port. I use double sided tape to hold it in place, then encase the wires and secure around the edges with hotmelt glue. In this install the xcsoar settings have been changed to landscape orientation.<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh23R31c_G4DGlwkBVwckH2n2HYgG5W9liZBm1ZEmwqqlxRnZR3ksEmdDdxhdY3XyVQNg6wAAKbFV8l5uSrPOw6PS9BNQF06qRRiNK2VMTJy1ePnavaNYlddKxZyonOE0D_UV7brUeNRgyj/s1600/BlueFlyVario_TTL_GPS_v12c.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="683" data-original-width="1024" height="426" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh23R31c_G4DGlwkBVwckH2n2HYgG5W9liZBm1ZEmwqqlxRnZR3ksEmdDdxhdY3XyVQNg6wAAKbFV8l5uSrPOw6PS9BNQF06qRRiNK2VMTJy1ePnavaNYlddKxZyonOE0D_UV7brUeNRgyj/s640/BlueFlyVario_TTL_GPS_v12c.jpg" width="640" /></a></div>
<br />
Some tips which are applicable to all installs:<br />
<br />
<ul style="text-align: left;">
<li>Use the neoprene, but do not use the sticky side which would block the holes in the pressure sensor.</li>
<li>Make sure you connect the BlueFly-Tx to the Kobo-Rx, and the Kobo-Tx to the BlueFly-Rx. </li>
<li>Set the baud rate in xcsoar to 115200. </li>
<li>Read an earlier blog post about using xci files. That is currently the easiest way to send commands to the vario (you also need to read the hardware settings manual on the <a href="http://www.blueflyvario.com/index.php/support">support page of the website</a>).</li>
<li>Check your wires to ensure the solder quality is good, and that the wires are not routed next to other components on the Kobo circuit board which might pick up stray power. I like to keep the wire length less than 5cm.</li>
<li>If you get 'Waiting for GPS fix' shown in xcsoar, and after 10 minutes of the vario being on, outside, and with the antenna having a clear view of the sky, the do the following debugging:</li>
<ul>
<li>Check in the Devices Monitor for incoming data from the vario.</li>
<li>Record a NMEA log and look for messages from the GPS to assess what is going on with the satellites.</li>
</ul>
</ul>
</div>
</div>
Flying Alhttp://www.blogger.com/profile/04770253154348277404noreply@blogger.comtag:blogger.com,1999:blog-4078676472481844653.post-63484881891357993562017-11-02T03:10:00.000-07:002018-06-11T03:01:37.455-07:00Airspeed Sensor Updates<div dir="ltr" style="text-align: left;" trbidi="on">
Almost two years ago I <a href="http://blueflyvario.blogspot.com.au/2015/12/gps-and-airspeed-shields.html">blogged about an airspeed sensor</a> shield for the BlueFly. This blog post is about a new approach to integrating an airspeed sensor with the BlueFly. It is still far from perfect, and still requires experimentation, but is a bit more accessible for those who want to tinker.<br />
<div>
<br /></div>
<div>
<b>The Sensor</b></div>
<div>
<br /></div>
<div>
Instead of producing a dedicated sensor I am relying on the widely available MS4525DO based sensor which is used by the R/C community. This uses the same differential pressure sensor as the dedicated airspeed sensor I used to produce for the BlueFly. However, because of the volume of manufacturing they can be produced at a cheaper price. Search ebay, aliexpress, banggood, hobbyking, or your favorite supplier of electronics from China for '<i>px4 airspeed</i>'. You should get many results. Make sure to select one of the sensors based on the digital MS4525DO (white) instead of the older analog sensor (black). You can read more about this sensor on the <a href="https://pixhawk.org/peripherals/sensors/px4airspeed">pixhawk website</a>. </div>
<div>
<br /></div>
<div>
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEimbfJHWv8BvP84Lf7wGmJEa3GsudM4BUiReXPEu8Oh9imM0fWHUE5e4tIBxGFQiz6vh8-ogVhrq4y_faTOXmftvkWarL6UtgaHnYQGryMpZXANKQ-UDNtcX01XdDshxkNT9F7-46eRIFjB/s1600/PX4_Airspeed_Sensor.jpg" imageanchor="1"><img border="0" height="426" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEimbfJHWv8BvP84Lf7wGmJEa3GsudM4BUiReXPEu8Oh9imM0fWHUE5e4tIBxGFQiz6vh8-ogVhrq4y_faTOXmftvkWarL6UtgaHnYQGryMpZXANKQ-UDNtcX01XdDshxkNT9F7-46eRIFjB/s640/PX4_Airspeed_Sensor.jpg" width="640" /></a></div>
<div>
<b><br /></b></div>
<div>
<b>The Enclosure</b></div>
<div>
<br /></div>
<div>
A 3d printable enclosure is designed to hold the sensor and BlueFlyVario_Bluetooth_USB_v12 (or the USB only version). It is far from a perfect design, but even on a rough 3D printer (like mine) is useful enough. You can <a href="https://www.thingiverse.com/thing:2621157">grab the design from thingverse</a>. Note that the lid and main part of the case are designed to be glued or held together with tape. Below is a photo of the BlueFly with airspeed sensor installed in the 3D printed case. </div>
<div>
<br /></div>
<div>
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiIG7Xx279KneEVUEL_yNrhLmSx0rOznO_xGIPJI_hD50TtwJ6Ep89gIpff30c1Pto62FRMbYIRJPUwoJHzB-3jFJrrXHwes5NY2P2No7P4X0VTONrLTEHYqtsBjbWeh4YjCNfJ4T3byLV4/s1600/BlueFly_Airspeed.jpg" imageanchor="1"><img border="0" height="426" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiIG7Xx279KneEVUEL_yNrhLmSx0rOznO_xGIPJI_hD50TtwJ6Ep89gIpff30c1Pto62FRMbYIRJPUwoJHzB-3jFJrrXHwes5NY2P2No7P4X0VTONrLTEHYqtsBjbWeh4YjCNfJ4T3byLV4/s640/BlueFly_Airspeed.jpg" width="640" /></a></div>
<div>
<br /></div>
<div>
<b>Firmware Update</b></div>
<div>
<br /></div>
<div>
Before going on please update your <a href="http://www.blueflyvario.com/firmware/">firmware to the BlueFlyVario_12.M16 version</a>. The firmware changes include:</div>
<div>
<ul>
<li>Fixed a bug with MS5611 temperature sensor output (that is only relevant for tinkering)</li>
<li>Changed outputMode 6 (BFV Extended Sentence) to include the MS4525DO sensor temperature. The sentence is now in the following format: <span style="color: #6aa84f;"><b>$BFX,pressure(Pa),vario(cm/s), MS5611temp(deg C in 2 decimal places), battery(%),pitotDiffPressure(pa), volts(V), pitotTemp(deg C in 1 decimal place)*checksum\r\n</b></span> </li>
<li>Ensured that if you send the command $BUP 1* that it always triggers an differential pressure sensor calibration sequence (which takes about 10 seconds). </li>
</ul>
<div>
<b>Assembly</b></div>
</div>
<div>
<b><br /></b></div>
<div>
The first step is working out what to connect to what. The sensor is connected to the I2C port of the BlueFly. You will need to ensure:</div>
<div>
<ul style="text-align: left;">
<li>BlueFly-Gnd is connected to PX4Airspeed-Gnd</li>
<li>BlueFly-SDA is connected to PX4Airspeed-SDA</li>
<li>BlueFly-SCL is connected to PX4Airspeed-SCL</li>
<li>BlueFly-V+ is connected to PX4Airspeed-+5V. Note that the the BlueFly actually only provides 3.3V, but my experiments suggest that there is no degradation in performance of the MS4525DO sensor at this voltage. </li>
</ul>
</div>
<div>
<br /></div>
<div>
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhn5y4QVOidAIBwZ0rbwYtAuPddFrvfTmRjvPKnGISNiHjkhizjWQwgzN7D-hezrfFajEQXYuSXcJAnkRrweTNtmdvjvK5UMGvtT0HenBQYO-s8XTH3_1ufEMjmG1KzGl2pIFWLhepSp6V2/s1600/Connections.jpg" imageanchor="1"><img border="0" height="426" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhn5y4QVOidAIBwZ0rbwYtAuPddFrvfTmRjvPKnGISNiHjkhizjWQwgzN7D-hezrfFajEQXYuSXcJAnkRrweTNtmdvjvK5UMGvtT0HenBQYO-s8XTH3_1ufEMjmG1KzGl2pIFWLhepSp6V2/s640/Connections.jpg" width="640" /></a></div>
<div>
<br /></div>
<div>
After soldering, the connections are shown below. You will need to cut and solder the wires to the length required for your enclosure. </div>
<div>
<br /></div>
<div>
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjOSguSWD3qPr5UAPtt1hs92CuSQoy7kEQV5g7RHjkw63VgHaR_yHsMrevZW8DYhVjsdyVVIrQ26gdcDTFnQqs3nysJSy6VcnwQLAiezRqPNoJx5sN4li5MNgZ21khUijLSC6hn2frU9ZxL/s1600/Connections2.jpg" imageanchor="1"><img border="0" height="426" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjOSguSWD3qPr5UAPtt1hs92CuSQoy7kEQV5g7RHjkw63VgHaR_yHsMrevZW8DYhVjsdyVVIrQ26gdcDTFnQqs3nysJSy6VcnwQLAiezRqPNoJx5sN4li5MNgZ21khUijLSC6hn2frU9ZxL/s640/Connections2.jpg" width="640" /></a></div>
<div>
<br /></div>
<div>
The image below shows the connected sensor and pitot tube mounted in the 3d printed enclosure. Note:</div>
<div>
<ul style="text-align: left;">
<li>The BlueFly mainboard mounts in a similar way as in the standard sky blue case. </li>
<li>The upper nozzle on the differential pressure sensor connects to the pitot part of the pitot tube, the lower nozzle on the static port. </li>
<li>You should use a few dabs of hot melt glue to keep the pitot tube and px4 airpeed sensor firmly in place. </li>
</ul>
</div>
<div>
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjb4735j-1C5gdCYV6Llq2Wx7l5Db8PMqG7UsosL5dU2hckzVJ_iMDyH0fq0jLfK2Vk7qQxCBFR7Fd-3jby0NzrKBBWBaUuFdHMtG9Xa_It-TgYMPloqXO68llMOpdNJRaGy5SgxUDCvY4W/s1600/Enclosure.jpg" imageanchor="1"><img border="0" height="426" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjb4735j-1C5gdCYV6Llq2Wx7l5Db8PMqG7UsosL5dU2hckzVJ_iMDyH0fq0jLfK2Vk7qQxCBFR7Fd-3jby0NzrKBBWBaUuFdHMtG9Xa_It-TgYMPloqXO68llMOpdNJRaGy5SgxUDCvY4W/s640/Enclosure.jpg" width="640" /></a></div>
<div>
<br /></div>
<div>
<b>Configuration</b></div>
<div>
<br /></div>
<div>
At the time of writing this blog post the only app which I am aware can read the indicated airspeed is xcsoar, and only when using the BlueFly in outputMode=2 (LX mode) and xcsoar configured to use the LXNAV driver. Key points:</div>
<div>
<ul style="text-align: left;">
<li>You first configure the BlueFly to outputMode=2 and usePitot = true using the BFVDesktop app or by using direct serial commands. See the <a href="http://www.blueflyvario.com/support/">hardware settings manual</a> for information about how to adjust the settings.</li>
<li>In xcsoar, set the driver to LXNAV and connect to the appropriate port (Bluetooth or over IP as appropriate for your model of BlueFly). </li>
<li>In xcsoar, you should now see the Airspeed IAS info box provide the <a href="https://en.wikipedia.org/wiki/Indicated_airspeed">indicated airspeed</a> reading. Note that this is different from the true airspeed. At low speeds (less than about 10km/hr) it will jump around quite a bit. At our paragliding and hanggliding airspeeds it should be accurate to about 1km/hr or less. </li>
<li>Note that you can send the command $BUP 1* (this is the same as usePitot=true) to trigger a zero calibration of the differential airspeed sensor. A zero calibration will always be triggered on startup, and should be re-triggered only when the actual airspeed of the pitot is zero. </li>
</ul>
<div>
If you really want to tinker and develop a custom app which uses the full features of the airpeed sensor then you will probably want to read the sentence from outputMode=6 (<span style="color: #6aa84f;"><b>$BFX,pressure(Pa),vario(cm/s), MS5611temp(deg C in 2 decimal places), battery(%),pitotDiffPressure(pa), volts(V), pitotTemp(deg C in 1 decimal place)*checksum\r\n</b></span> ) This provides the MS5611 pressure and temp, and the MS4525DO pitot differential pressure and temp. With some smart coding you should be able to calculate the true airspeed, and even develop a total energy calculation. </div>
</div>
<div>
<br /></div>
<div>
On the hardware side, you might want to add a push button for zero calibration. The firmware polls RB10. An internal pull up keeps it high, but if you use a push button to ground then zero calibration will be triggered. </div>
<div>
<br /></div>
<div>
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhgwY1_fmOXC3zQDyQZbT_ilphob6sdEK8xNjDpeVqi051A-OfLhwsa4Fcd4IdvFUsBX7itsrcFtcqcMU8mKK8DKdBPSdhbjw8xJ-wNWsLJ9PgVFd-q3youXmSdnmvhuKOSbRqBN9aHQW-O/s1600/Assembled.jpg" imageanchor="1"><img border="0" height="426" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhgwY1_fmOXC3zQDyQZbT_ilphob6sdEK8xNjDpeVqi051A-OfLhwsa4Fcd4IdvFUsBX7itsrcFtcqcMU8mKK8DKdBPSdhbjw8xJ-wNWsLJ9PgVFd-q3youXmSdnmvhuKOSbRqBN9aHQW-O/s640/Assembled.jpg" width="640" /></a></div>
<div>
<br /></div>
<div>
<b>Todo</b></div>
<div>
<br /></div>
<div>
As always, there is more to do; manual updates, testing, more software, better physical layout for mounting in a paraglider or hangglider, etc. </div>
</div>
Flying Alhttp://www.blogger.com/profile/04770253154348277404noreply@blogger.comtag:blogger.com,1999:blog-4078676472481844653.post-83307583629655464102017-10-15T13:03:00.000-07:002017-10-15T14:25:07.872-07:00Flying the Nova Mentor 5 in Canberra<div dir="ltr" style="text-align: left;" trbidi="on">
A few months ago I starting flying a new Nova Mentor 5. It is so lovely that I decided to write a few words about it. Read on to hear about it's precision, stability, and performance.<br />
<div>
<br /></div>
<div>
This blog post is only loosely related to the BlueFly. One of the common queries I get from BlueFly users around the world is what wing I fly, and sometimes what the flying is like around Canberra. I will answer both of those questions in this post. </div>
<div>
<b><br /></b></div>
<div>
<b>What kind of pilot am I?</b> In between a full time job, making and shipping well over 100 BlueFly's each month, and doing family stuff, I get time to fly. I have been flying paragliders since 1995 and am probably best characterized as a classic weekend pilot. Most of the time I stay pretty close to launch; dancing with light thermals below airspace, or making optimum use of a little ridge lift. I also fly tandem with family and friends (not commercially). </div>
<div>
<br /></div>
<div>
<b>What is Canberra flying like? </b>Our sites around Canberra are not suited to big XC. The flying here is very technical if we want to make use of limited lift to do some little XC. We have a great club, and you can read more about flying Canberra at <a href="http://www.acthpa.org/">www.acthpa.org</a>. </div>
<div>
<br /></div>
<div class="separator" style="clear: both; text-align: center;">
<iframe allowfullscreen="" class="YOUTUBE-iframe-video" data-thumbnail-src="https://i.ytimg.com/vi/6uDz7GFuEZU/0.jpg" frameborder="0" height="270" src="https://www.youtube.com/embed/6uDz7GFuEZU?feature=player_embedded" width="480"></iframe></div>
<div class="separator" style="clear: both; text-align: center;">
<span style="font-size: 12.8px;">Launching at Collector near Canberra - I actually ended up catching a few thermals after a sinking launch. </span></div>
<div>
<br /></div>
<div>
<b>Why an EN B wing?</b> With over 20 years flying paragliders I have flown all kinds of wings. If you have been reading this blog since the beginning you may recall that I had a bad accident when flying an EN C wing. In fact, it was recovering from that accident which gave me the time to mature the BlueFly from a few prototypes to begin shipping them around the world. After that accident, I got a Nova Mentor 3 (M) and have enjoyed every flight on it.</div>
<div>
<br /></div>
<div>
I don't get enough spare time to travel to many far away places, or any time to fly during the week. Around Canberra we are often low to the ground and the air can be quite rowdy. A comfortable EN B wing strikes the balance between performance and stability for someone like me who might go a month without flying, and then not get many consecutive days. </div>
<div>
<br /></div>
<div>
<b>Why the Nova Mentor 5</b>? I loved my Mentor 3 (M), but after loosing a few kg I was near the bottom of the weight range and decided to get a smaller wing. The Mentor 5 (S) had just been released so I made a quick decision to get one. I have always appreciated Nova's premium quality and support (Nova are not contributing to this by the way; I am just a happy customer). </div>
<div>
<br /></div>
<div>
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhm0Po3ocq5d3jzlv2WZqW4fQgVzHxPDKoNnE1gCDKgKz4mYVVUm7Y7VpNz2o2HAaqvgz8n652O2mylsGIET0g-eiut3rrP9G6DTHDFQ1hqC55F1fPUMedoKAYcxQDQK-iH2vp9BxHZB8EU/s1600/22522488_10213243564259662_55079145_o.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" height="360" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhm0Po3ocq5d3jzlv2WZqW4fQgVzHxPDKoNnE1gCDKgKz4mYVVUm7Y7VpNz2o2HAaqvgz8n652O2mylsGIET0g-eiut3rrP9G6DTHDFQ1hqC55F1fPUMedoKAYcxQDQK-iH2vp9BxHZB8EU/s640/22522488_10213243564259662_55079145_o.jpg" width="640" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;">Shaun (in front), and me (at the back) kiting in a very light breeze</td></tr>
</tbody></table>
I have now flown the wing in a lot of winter thermals, and as Spring has begun in Canberra, in a few sharper thermals that throw me around. I have nothing bad to say about the Mentor 5, and love the precision, stability, and performance. </div>
<div>
<br /></div>
<div>
<b>Precision</b>: This surprised me. Part of the reason the Mentor 5 (S) does exactly what I ask of it is because my wing loading is greater (top third of the weight range), but it is much more than that. I can hold a tighter turn and keep the wing just where I want it. When encountering turbulence I do not get thrown out of lift. I feel like the precision is at least as good as my EN C wing of four years ago.</div>
<div>
<br /></div>
<div>
<b>Stability</b>: The wing seems to stay solidly above my head, with only minor inputs required to keep it there. Even in some rough air I have only had a few little tip tucks, and they have popped out very quickly. The wing easily enters and exits big ears, and the longish brake travel seems like an inadvertent stall is very unlikely. I have not done SIV on this wing yet, but already I have more confidence than my Mentor 3. I am using speed bar much more!</div>
<div>
<br /></div>
<div>
<b>Performance</b>. Near the top of the weight range the sink rate is less than many other wings (when comparing using my 'am I at the top' test with a bunch of other pilots on a ridge). The wing is fast; at trim other pilots comment on the sound of the lines whistling though the air. On speed bar I have found I can already reach a few spots much more easily that my older wings. </div>
<div>
<br /></div>
<div>
In summary, for a weekend pilot like me, the Nova Mentor 5 is a great choice. </div>
<div>
<br /></div>
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj1eyKHePMK0W5tUM6kBEefey7ZwshqZ-1Il-NItKFjA6ZSjzTduvlauQL0KZRcp2RPhdzzeHkLjWImU78ONXXHzv3Urf29RxPaOhW6a9F39fXYjK_Z4iyK9sp2TaGvn9TlEnFZbH1mWfzK/s1600/2017-10-15+15.27.06.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" data-original-height="1200" data-original-width="1600" height="480" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj1eyKHePMK0W5tUM6kBEefey7ZwshqZ-1Il-NItKFjA6ZSjzTduvlauQL0KZRcp2RPhdzzeHkLjWImU78ONXXHzv3Urf29RxPaOhW6a9F39fXYjK_Z4iyK9sp2TaGvn9TlEnFZbH1mWfzK/s640/2017-10-15+15.27.06.jpg" width="640" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;">Well done Nova - another very pleasant wing. </td></tr>
</tbody></table>
<div>
<br /></div>
<div>
<br /></div>
<div>
<br /></div>
</div>
Flying Alhttp://www.blogger.com/profile/04770253154348277404noreply@blogger.comtag:blogger.com,1999:blog-4078676472481844653.post-10968797751602089152017-08-27T03:17:00.001-07:002017-08-27T03:37:19.722-07:00BlueFlyVario_USB_V12 released<div dir="ltr" style="text-align: left;" trbidi="on">
A busy work and family life means that I have only so much time for this hobby, and that time is almost entirely consumed by keeping up with orders for BlueFly varios; there has not been much time for development. However, today I can announce the release of the <a href="http://www.blueflyvario.com/product/blueflyvario_usb_v12/">BlueFlyVario_USB_v12</a>. This replaces the <a href="http://blueflyvario.blogspot.com.au/2016/08/new-bluefly-usb-models-released.html">BlueFlyVario_USB_v11 and the BlueFlyVario_USB_GPS_v11</a>.<br />
<br />
The USB only model of the Bluefly is much less popular than the Bluetooth_USB model, (which is what you probably want if you are going to use it with a phone), or the TTL_GPS model (which is probably what you want if you are going to use it with a Kobo). Nonetheless, there are some reasons why the USB only model might be right for you:<br />
<ul style="text-align: left;">
<li>If all you want are the great sounds of the BlueFly; then you can use it as a stand alone vario that beeps. </li>
<li>If you are sure that you want to connect via USB to a PC, or to Android phone via USB OTG; then you can use it with xcsoar or another app. </li>
</ul>
<div>
<b>What is in the bag?</b></div>
<div>
<br /></div>
<div>
The BlueFlyVario_USB_v12 is essentially the same as the most recent revision of the <a href="http://blueflyvario.blogspot.com.au/2017/01/blueflyvariobluetoothusbv12-released.html">BlueFlyVario_Bluetooth_USB_v12</a>, but without the RN4678 Bluetooth module and some associated components. It has a slightly different firmware as the analog switch is no longer required to switch between the Bluetooth and USB output. See the image below for what is included:<br />
<ul style="text-align: left;">
<li>The BlueFlyVario_USB_v12 mainboard. There is a small piece of neoprene covering the pressure sensor; glued at one end to hold it in place. </li>
<li>The sky blue enclosed case. </li>
<li>A 750 mAh singe cell Lithium Polymer battery. </li>
<li>4 x 5 mm M3 black nylon hex standoffs and 4 x 5 mm M3 black nylon screws.</li>
</ul>
<div>
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjKX0jZsBPNQ4sRT_zUcWW6DbElXFKQAFViv_vH-KJ_IixYPLZAUXepT2g3ezGiLisQLz6u8awc-2e7ctUJsqQeHhkup3brw-k-JiE7F4Zyj36DZ6UtLGZlWtwHG3bA4LG0-ZsHNN94viff/s1600/IMG_1391.JPG" imageanchor="1"><img border="0" height="426" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjKX0jZsBPNQ4sRT_zUcWW6DbElXFKQAFViv_vH-KJ_IixYPLZAUXepT2g3ezGiLisQLz6u8awc-2e7ctUJsqQeHhkup3brw-k-JiE7F4Zyj36DZ6UtLGZlWtwHG3bA4LG0-ZsHNN94viff/s640/IMG_1391.JPG" width="640" /></a></div>
</div>
<div>
<br /></div>
<b>Assembly</b><br />
<br />
Follow the assembly instructions for the <a href="http://blueflyvario.blogspot.com.au/2017/01/blueflyvariobluetoothusbv12-released.html">BlueFlyVario_Bluetooth_USB_v12</a>.<br />
<br />
<b>Configuration</b><br />
<br />
The BlueFly varios have many hardware settings to adjust the audio and lift/sink thresholds for beeping. See the <a href="http://www.blueflyvario.com/support/">hardware settings manual</a> for a full description of all of the settings. Most people will just use the default settings. However, read on if you want to mess with them.<br />
<br />
For most users the easiest way to connect will be to use the BFVDesktop application from a PC (<a href="http://www.blueflyvario.com/software/">available on the support page of the website</a>). The v12 models of the BlueFly include a FTDI USB to serial computer. When you plug it in to your PC a virtual serial port will be installed. In the BFVDesktop application select the installed port, <span style="color: red;"><b>make sure the baud rate is 115200</b></span>, then press connect. Test connection with the BlueFly by sending the $BTN* command, which simulates a button press on the actual BlueFly.<br />
<br />
You could also configure the BlueFly from a suitable terminal application on the PC or Android by using the raw commands as described in the hardware settings manual.<br />
<br />
<b>Adding a GPS</b><br />
<br />
I have discontinued the USB_GPS model at this stage. However, with a little basic soldering you can still add a GPS to the U1 headers. This can be done on the Bluetooth_USB model as well, but the GPS used in this example will not fit in the sky blue case with the bluetooth module and you would need to work out a way to suitably attach it to the outside.<br />
<br />
The first step is to select a GPS which runs on 3.3v, has an included antenna, and has a TTL serial output. By default the U1 port on the BlueFly is configured to receive NMEA sentences at 9600 baud multiplex them with the normal BlueFly output, delivering the resultant data stream via the USB_Serial port at 115200. Any sentence arriving to the BlueFly at U1 which less than 82 characters long, beginning with $ and ending with *, will be gobbled up by the BlueFly and sent through. <br />
<br />
A suitable GPS, and the one used in this example, is a widely available model used for RC flying. Search for "naze32 mini gps" on ebay, aliexpress, banggood, or where ever you get your electronic components. It is based on the ublox7 module, and I have found it to get a lock quickly and reliably. Also, it is just the right size to fit neatly in the sky blue case. Like most GPS', it defaults to a TTL output at 9600 baud which means it will work with the BlueFly without further configuration.<br />
<br />
First, take the GPS out of its case and strip the wires. In the image below Red is 3.3v in, Black is GND, Orange is GPS-Tx (which will be connected to BlueFly-Rx), and Blue is GPS-Rx (which will be connected to BlueFly-Tx). Note that the wire colors might be different for you. <br />
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgWqiOzbfMU7b4ug94BArWhSoMqNuKl3jPVKFSlNsk5BBS2dsYdqV7F79Ml4jE9vcCgi0BJJVxNyKLBlSfjac6VYni4EbyHTLkYtY5kff7LdMPWiBuG2BytAXngmtqLSqDGLHz4w-XHySdD/s1600/IMG_1382.JPG" imageanchor="1"><img border="0" height="425" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgWqiOzbfMU7b4ug94BArWhSoMqNuKl3jPVKFSlNsk5BBS2dsYdqV7F79Ml4jE9vcCgi0BJJVxNyKLBlSfjac6VYni4EbyHTLkYtY5kff7LdMPWiBuG2BytAXngmtqLSqDGLHz4w-XHySdD/s640/IMG_1382.JPG" width="640" /></a><br />
<br />
Next connect it to your BlueFly. Make sure your solder joints are clean and well made. Put a piece of tape on the BlueFly where the bluetooth module would have been to ensure there are no shorts between the underside of the GPS and the BlueFly board.<br />
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj8ChnZzJgPwHGjYXXvu4ZXjf8GgIR0JUgzVZfDYTjBINDgnwNeG3FIGbk8rbTKwToIsMUuXK6P1thQmHxD-qvAf2PiF99o61wdwOj7uFWtwfDiWillDnrdDEIt-59DahkJIB3L6hZrUSBx/s1600/IMG_1392.JPG" imageanchor="1"><img border="0" height="426" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj8ChnZzJgPwHGjYXXvu4ZXjf8GgIR0JUgzVZfDYTjBINDgnwNeG3FIGbk8rbTKwToIsMUuXK6P1thQmHxD-qvAf2PiF99o61wdwOj7uFWtwfDiWillDnrdDEIt-59DahkJIB3L6hZrUSBx/s640/IMG_1392.JPG" width="640" /></a><br />
<br />
Finally, stick it to the top of the tape with more double sided tape and fold the wires away neatly. As the GPS module is just the right height you will not need the 5mm black stand offs at the GPS end of the board. It will fit neatly in the sky blue case, but make sure to be careful not to damage the button or USB connector as you put it in - do not force anything.<br />
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiahBvqPdjL-rodsUbyxmRkaA0mNYDTta9Y5pdI9T3Hp85IY5Z-jkqKa7_sqSHol3HuAWCueVTsrnywKqQHjK0T2cxqnbD6eDdkkKUlsQISbdX95qW-0BTIOb_jl2vOART2pkNUYEWrVvqV/s1600/IMG_1394.JPG" imageanchor="1"><img border="0" height="426" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiahBvqPdjL-rodsUbyxmRkaA0mNYDTta9Y5pdI9T3Hp85IY5Z-jkqKa7_sqSHol3HuAWCueVTsrnywKqQHjK0T2cxqnbD6eDdkkKUlsQISbdX95qW-0BTIOb_jl2vOART2pkNUYEWrVvqV/s640/IMG_1394.JPG" width="640" /></a><br />
<br />
If you connect to the BFVDesktop app you should now see GPS sentences streaming in among the standard output from the BlueFly.<br />
<br />
Note that it is possible for advanced users to further configure the GPS. The uBlox software to control a GPS is u-centre. It is possible to disconnect from the BFVDesktop app, and connect to u-centre. You will actually be connecting to the BlueFly at 115200 baud, even though the GPS is at 9600 baud. Some settings are available as the BlueFly sends any nmea sentence it receives from USB-Serial to the GPS as well. However, for any GPS setting feature which relies on binary communication, such as GPS firmware upgrades, then the multiplex magic of the BlueFly will not work.<br />
<br />
<b>Connecting to Android</b><br />
<b><br /></b>
Some users will want to connect the USB model of the BlueFly to their Android phone for use with xcsoar. If you have installed a GPS this might be what you could do with an Android device that does not have Bluetooth or a GPS. <i>However, a disclaimer - I feel that that USB connectors are not designed for movement, and over time will be fragile if used on a paragliding flight deck, so I always recommend using the Bluetooth version if you have a choice. </i><br />
<br />
You will need a USB-OTG cable. The connection method is shown in the image below.<br />
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgBsgJAPXIo4n3_DWZRqt_vpvw-NxRmG_WeHatnkKTZumHu_KPPeeoizgk5mnqBIwR1fs7iV6QGnSLppGimt-n5tGJ862PKwJFUhVN12yedtvNBYX9jWf69J-V4P4bh1DipZzBqza17poDn/s1600/IMG_1395.JPG" imageanchor="1"><img border="0" height="426" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgBsgJAPXIo4n3_DWZRqt_vpvw-NxRmG_WeHatnkKTZumHu_KPPeeoizgk5mnqBIwR1fs7iV6QGnSLppGimt-n5tGJ862PKwJFUhVN12yedtvNBYX9jWf69J-V4P4bh1DipZzBqza17poDn/s640/IMG_1395.JPG" width="640" /></a><br />
<br />
In the above image the BlueFly is connected to the UartBridge app. You can get it on Google Play here: <a href="https://play.google.com/store/apps/details?id=com.manichord.uartbridge">https://play.google.com/store/apps/details?id=com.manichord.uartbridge</a>. This app was designed to be used with the FTDI converter used on the BlueFly. It is open source and you can find it on <a href="https://github.com/maks/UartBridge">GitHub</a>. Thanks to Maks for the great work.<br />
<br />
The UartBridge app will take the data coming in via USB-Serial at 115200 baud, and create TCP server on the local host to send it out on port 4353. In xcsoar you configure a device as shown below:<br />
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiftdY9qv6-Ot6r22mQy0ypRHnawgZwlcdhhghscuywVNdbfrBFhNRf5WHV9Mok3AsicnTfInmk2wbVRo8qkZ2qu1Gu9KfoW7yydm2dfPdBDtaqLzmEZbA6qLWiHdGv6ZDMbXjHlWX_UuXa/s1600/2017-08-27+18.35.26.png" imageanchor="1"><img border="0" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiftdY9qv6-Ot6r22mQy0ypRHnawgZwlcdhhghscuywVNdbfrBFhNRf5WHV9Mok3AsicnTfInmk2wbVRo8qkZ2qu1Gu9KfoW7yydm2dfPdBDtaqLzmEZbA6qLWiHdGv6ZDMbXjHlWX_UuXa/s400/2017-08-27+18.35.26.png" width="225" /></a> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg9C1BlgogLsQCrAodzDAClnomiK_Wg_kxbeI4h880gskMpVv-O48n0fAJSEH9YcYHRzVwoCRZIMfEyx6yPmSKfPVydPvLn3XsW8Jiu0ecVgx7PUSwqSS_qzzeGW3UPmsNw8iI9Rew0IpCY/s1600/2017-08-27+18.35.15.png" imageanchor="1"><img border="0" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg9C1BlgogLsQCrAodzDAClnomiK_Wg_kxbeI4h880gskMpVv-O48n0fAJSEH9YcYHRzVwoCRZIMfEyx6yPmSKfPVydPvLn3XsW8Jiu0ecVgx7PUSwqSS_qzzeGW3UPmsNw8iI9Rew0IpCY/s400/2017-08-27+18.35.15.png" width="225" /></a><br />
<br />
The BlueFly data (and multiplexed GPS data) will stream into xcsoar. <br />
<br />
<b>What about the TTL_GPS model?</b><br />
<br />
At this stage I am not planning on a TTL_GPS_v12 model. The v12 Bluetooth_USB and USB models were motivated by wanting to fit in the larger 750 mAh battery, and incorporating the FTDI USB converter, neither of which applies to the TTL_GPS model. I am sure there will be mode development in the future, but I do not have anything in planning to replace the TTL_GPS at this stage.<br />
<br /></div>
Flying Alhttp://www.blogger.com/profile/04770253154348277404noreply@blogger.com