This page will help you build a FLARM enabled version of AirWhere, we are adding a new radio board that sends a message out on the FLARM frequency so FLARM enabled traffic can see us, we can not see the FLARM traffic, they can just see us. If you wish to see FLARM traffic or learn more about FLARM please visit the www.flarm.com website and purchase one of their devices. This setup will still send and receive on the airwhere frequency so you will still see airwhere enabled devices and they will see you.
The install and setup procedure just requires basic computer knowledge, how to download files, install software and to be competent at soldering. Some fault finding and knowledge of serial communications is always useful but not necessary. If you have any issues building this device please pop on the AirWhere facebook group and ask, alternatively contact us.
Firstly before you start you will need to register an ID for your unit.
|1.1 ||Proceed to the registration page and type in your email and choose a password and press sign up.|
You will then receive an email asking you to confirm your email address, if you dont receive one, check spam to see if its there or any other issues - contact us.
|1.2|| Once you have verified your email proceed to log in and then press add aircraft and add your details|
Examine your FLARM board you purchase in the next step and there will be a code on top. Enter the first 2 digits into the manufacturer field and then next 4 into the ID field.
This will now be your flying number.
First we will describe the initial flarm setup which can be used via USB to a kobo and wifi/ble - we recommend this setup is built and configured first, perhaps on a breadboard to confirm all the hardware is ok and it is much easier to diagnose any issues. Once the flarm/airwhere system is seen to be working then proceed to install into your finished case/setup.
To purchase the hardware you will be using please order the following items :-
All these items and a kit are availble on our shop site
, please contact us if you cant find what your looking for. ( 1/3/2018 - items will be added to the shop site shortly )
into a kobo the following items are required to build as per the later instructions, however if you are going to spec your own build, purchase whats necessary.
There are also various parts to fit the various different kobos - we do a full kit of parts to make your own, if this is too much for you we also supply a complete ready to go version.
Once the purchased hardware arrives
you will need to install the windows / mac drivers to be able to ‘see’ the board and then install the AirWhere software onto it.
||Load this page and then download the relevant driver for windows and install.
||Extract the zip file to a folder and then run the correct executable in the file.|
If your on 32 bit windows, run the exe with 86 in it and if your on a 64 bit windows run the 64 version. Your version can be found in windows device manager.
||Now you should be able to get a micro usb cable and plug your AirWhere board in..|
Windows should say its found the hardware and that is now working.
||Open windows device manager (control panel – device manager). Find ‘Ports’ you should see a new port there, perhaps com3 or com4 which is your new board.Take a note of this number you will need this in the next step.|
||Create a new folder on your PC.
Name the folder but DO NOT allow any spaces between letters.
||You will need to download into this folder 4 files:|
- ESPFlasherGUI.exe from =https://github.com/neoxharsh/ESP32-GUI-Flasher/tree/master/dist
This is the flasher program you will be using (Windows only, for the Mac see this page)
The next three files are available either on the AirWhere down loads page http://www.airwhere.co.uk/airware-downloads.php
or you may find them under files on the Airwhere-ESP32_Pilots Only page on facebook.
- Bootloader called bootloader.bin
- Partition called default.bin
- Application currently called AirWhereESP32.bin
This may change so check facebook for the live version or for the latest unstable version AirwhereESP32Dev.bin
Please make sure there are NO spaces in any of the file names and the directory it is in, this will create an issue.
||Plug the ESP32 into a microUSB and into a USB port on your computer.|
The OLED may say Heltic and then start counting packets it is transmitting. Ignore this and carry on.
||Double click on the ESPFlasherGUI.exe file and link the Bootloader, Partition and Application files.
||Select and check the COM port (you checked device manager for this number before)|
For example COM11 (even though the correct port may appear in the box you MUST click on the drop down and reselect it or the download will fail).
|| Select the memory size 4MB.
|| Finally press FLASH and immediately after press the PRG on the board once. |
The card will start to write the data, takes about 9s. You may find the programme terminates with a message that says it is rebooting and a flashing light on the ESP32 board. Ok this has probably worked. ( We have seen the buttons on the ESP32 board marked up incorrectly, so if you try one button and it fails with "cant find packet head" or similar, just try the other button, some need it held until the flashing process starts and then let go. )
||Now check to see if you can see the AirWhere ESP32 board on your wifi settings.
So now you have a working ESP32 board with the AirWhere program.
||Search for the new device in your wifi settings and connect to it..
You will be asked for default password 12345678. ( this password could have been changed when the unit was built so check with the builder.)
||Now type 192.168.4.1 in your web browser.
If you are using an android phone please switch your data oﬀ, android will try look for airwhere on the internet and the connection will take a long time.
You will now see a page titled AirWhere ESP32. This is the configuration page.
||Then use the Configure Pilot Info button to enter your details, the ID field will be disabled and will be filled in by the FLARM board later when its connected.
When you press ‘Submit’ the device will try to return to the home page but when the FLARM board is attached it will create a new access point with your new number, therefore will require to be searched for and connected to.
||Reconnect this wifi device then refresh 192.168.4.1.
||Click ‘Pilot Info’, input your pilot details, your Wifi SSID and Password..
This will allow you to upgrade the software via your Wifi connection.
||When you’ve completed the settings press submit.
The unit will restart so go back to the home page again once its started.
||Press ‘Configure Hardware’ and under ‘Radio board’ select ‘FLARM board’.
the other choices depend on what you are building and have attached.
||Select in flight software select what software you will be using and which platform.
(as we want to connect to an android phone in this version).
||Select which baud rate your gps uses, if its a standard gps they are mainly 9600 such as the PA6C shown on the circuit diagram later.
however the bluefly vario uses 57600 as standard, this will be your kobo connection speed aswell so make a not of this number.
||In connection mode choose OTG/Serial Mode ( GPS attached to ESP32, this will be main mode that the flarm setup will be used, apart from wifi mode. Again press submit and reconnect to home page..
Sometimes this take a couple of mins, if it hangs, refresh your browser 192.168.4.1. You should now be back on the home page for your device. If the page times out, just refresh and it will appear again.
This step is optional but we recommend it as it will help diagnose any issues and will confirm the setup and hardware is operational before proceeding to install into a case.
||Download putty https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html - this is an application that will let you see the output from airwhere and will help see if everything is working ok.
||Install this and then run the application, on the first screen press the serial radio button and then add your com port as you found earlier and then type in a (baud rate ) speed, which you defined earlier in AirWhere ( 9600 or 57600 probably ).
||Plug the ESP into a spare usb port on the computer.
if you stick with the same port everytime it will hopefully stay on the same com port, but check device manager anyway to make sure.
||The next screen will probably come up blank - press reset on the esp8266 board and then text will start scrolling out in this screen showing you something similar to the following lines.
We would recommend checking this as you install the components and check the system.
||Follow the wiring diagram to setup the AirWhere FLARM board.
a breadboard can be used to temporarily check the system works ok, however soldering gives a better joint.
|ESP32||FLARM board||Aerial||Power LED||GPS Lock LED||GPS||Kobo|
|IO17 ( TX2 )||RXD|
|IO16 ( RX2 )||TXD|
|3V||VCC||+ve||+VE/VCC||+ve (TP2 - optional)|
||After the diagram has been followed, connect the board to usb and run putty as in the previous step, the flarm board should now be found and gps data appear on the application.
||As the GPS gets its first lock, it can take a while from cold.
the text AIRWHERE TRANSMITTING LOCATION should appear on the screen amongst the gps statements, this shows your build is now working.
||If your wifi and wifi password have been added to the config, the device should be seen on the AirWhere tracking page.
||Update your FLARM board.
all boards require a freely available yearly update from FLARM, this is done automatically and navigating to "configure hardware" on the AirWhere configuration page will facilitate this. If your FLARM board is installed correctly the expiry date will be shown on this screen , please press update FLARM board and then update. Your board will reboot after this has finished, reconnect again to see the new expiry date. If the date is the same, try again, there may have been network issues. ( If it has failed the board will say not connected, dont worry this is normal, please try updating again )
At this point the unit can be connected to USB or switched to wifi mode and connected to a working kobo or android.
Information can be found on Step Seven of this page
on how to complete this. The only difference being speed ( baud rate ) you have configured before.
Notes : If your gps takes a 3-5V input then sometimes ( or if its not working ) attach the positive on the GPS to the 5V on the ESP32 board. This sometimes can help give it a bit more power for a better lock.
If your using a bluefly vario then the pps is in a different place than the above diagram, please check the data sheet
WiFi mode allows the board to be used in a simple set-up or for testing purposes.
Currently it works with XCSoar and LK8000 but its in development with XCtrack as well (beta). XCTrack will be fully integrated with AirWhere shortly.
For your information
If you are using an Android device such as a phone or tablet and it has a GPS installed then there is no additional wiring for the ESP32 to work as AirWhere with your device and show other AirWhere users. The set-up entirely depends on what flight software you are going to use. If its XCSoar / LK8000 or XCTrack (beta). AirWhere doesn’t have a built in GPS on the board so you will need to get the Android device to send its internal GPS data to the AirWhere. There are a number of ways of doing that but the easiest way I’ve found is to use the free application called ‘Share GPS’. This can be found on Androids Play Store.
||Go to Androids Play Store and download ‘Share GPS’, once it is installed run the application.
||Click on ‘Connections’ and ‘Add’.
||Click on ‘Activity’ and select the first option - ‘Share my gps with a laptop or tablet’.
||Choose the option ‘Use TCP/IP to send NMEA GPS to PC’.
||Tick ‘Connect on App Start’. (if you have the premium version) then name it, e.g. ‘airwhere’.
||Set up as ‘use UDP instead of TCP’.
||Input ‘Host’ as 192.168.4.1 and ‘Port’ as 10111 .|
When complete it will be set to ‘idle’. To start the server, first make sure your android device is connected to the AirWhere wifi access point and then click on ‘Idle’ which will switch to ‘Connected’. When your phone gets a GPS fix the T:0 on the heltec board will be increasing in value, this is your data being sent out. If you have added your wifi details as your device gets a fix you will be shown on live tracking page.
Choose LK8000 or XCSoar
||Connect to the AirWhere home page by connecting to its wifi and going to 192.168.4.1.
||Click Configure Hardware..
Then under ‘Flight Software’ choose ‘LK8000 - Android’ and under Connection mode choose ‘Wifi Mode’ and click ‘Submit’. The board will restart.
||Check that the ShareGPS software is now showing connected.
(if you have setup the app correctly).
Now you need to let LK8000 know where to get the AirWhere data from.
||Press the menu button bottom right, then ‘config’, ‘config’, ‘LK8000 Setup’, ‘Device Setup’.
||Device A should be ‘Internal’ .
||.Device B should be ‘Generic’, ‘UDP Server’, ‘Port 10110’.
||Press close.and then a line saying restarting comm ports will come on screen, then detected FLARM, this shows your system is working.
||Press the middle of the bottom info bar and the flarm screens will come up, check the airwhere video sections for usage.
Hint - to see traffic on the main map, go to ‘config’ and on page 13 at the bottom ‘enable traffic’.
That’s it, Airwhere is now configured!
||Connect to the AirWhere home page by connecting to its wifi and going to 192.168.4.1..
||Click Configure Hardware. Then under ‘Flight Software’ choose ‘XCSoar - Android’ and under ‘Connection mode’ choose ‘Wifi Mode’ and click ‘Submit’. The board will restart..
||Check that the ShareGPS software is now showing connected .
(if you have setup the app up correctly).
||Double click on the plane icon at the bottom and bring up the menu. Click ‘Config’ and click.
||Device A should be set to ‘Built-in GPS & sensors’ and
||Device B should be set to UDP Port, TCP port 10110 and Driver FLARM.
If the AirWhere is on and the ShareGPS is in a ‘Connected’ status then XCsoar will show that its receiving FLARM data (that’s just AirWhere data).
When AirWhere sees another user it will be shown as FLARM traffic in the XCsoar application.
Step Nine (Optional).
Firstly you will need to purchase a piezo buzzer and then attach ground of the buzzer to ground on the esp32, the positive of the buzzer to pin 32.
||First purchase a GY-86 board, these shouldnt be too expensive, we have them on the shop site if your finding it difficult to find - also make sure you have a speaker attached - we need sounds for the vario ;)
||Add a small piece of black tape or neoprene to the top of the tiny pressure sensor on top of the gy86 but be careful not to cover the sensor holes, the pressure sensor is effected by light so we need to keep it in the dark so its stable.
||Follow the wiring diagram to setup the vario board.
a breadboard can be used to temporarily check the system works ok, however soldering gives a better joint.
||To configure LK8000 or XCSoar to use data from this sensor, please change the device driver to be BlueFly Vario we will have our own driver soon but for now please use this, using this driver gives you barometric height and therefore a correct climb visual climbrate, also outside air temperature, this can be setup up in config
The board now needs housing in a case and a way of securing to your flight deck, we do have cases available, so please contact
Please if you do build an AirWhere in this way, as it is so cheap and easy to do please do donate a contribution to the project, the project has taken 2 years and thousands of hours of work to get to here and we have to pay for server fees - many thanks. Our paypal is email@example.com for any donations to keep this project alive :)
That’s it, Airwhere is now configured!
If there are any problems during the install please check the following.
||Double check config settings - ie OTG Mode / GPS etc.
||FLARM board is updated.
||If there are some issues that stop the board working properly, please try updating to the development version before emailing in. Your issue may have been fixed already but not tested and released live.
Have fun with the project!