Please read the following notes carefully
(i) On boot-up the Nodemcu board will attempt to connect to the Internet. If for any reason it can't then the web connection will stay down. Similarly, if at any point the link to the Internet is disconnected then
this will not be regained until the board is rebooted. This
is a limitation of the current hardware, hopefully when the new ESP32 comes out
we will be able to solve this.
(x)If you build your airwhere and the moment it gets a gps fix the transmit light comes on and doesnt blink there is a couple of problems this might be.
(ii) Currently, with LK8000/Kobo, if the network disconnects then the Nodemcu may just wait. The ErrTx will increase when viewed in Terminal in the Devices and board is unable to re-connect without re-booting.
This happens very rarely, but the LK guys know about it and hopefully a later release of LK will solve this problem.
We can manually restart the comms if it goes down , if you look at the third config page and press "Reset Comms" this should restart the connection between LK and Airware and be back running again :)
If that doesnt work then config , press wifi Off and then wifi On and this will cycle the wifi. We will have a solution to this problem vi LK and a script to upload to keep the wifi connection alive.
(iii) Currently, when running TCP Server with XCSoar and Bluefly, XCsoar has been seen to drop the GPS connection from time to time. Not sure if its just mine
or on all versions - reported to XCSOAR developers for attention, but as yet no one seems to be replying. Please let us know if you get the same :-
(iv) If the device doesnt receive a gps signal or wifi signal it will reboot itself after 2-3 mins and keep doing this until it receives a signal, this is be design to clear any problems up that might occur and make a reconnect.
(v) Currently tested successfully on LK8000(kobo,winCE),XCSoar(kobo,Android), LK8000 ( HD2 HDA - windows )
(vi)The set-up webpage will give the true indication of the Flight Software status when you first open it. For efficiency the Flight software is then briefly disconnected to concentrate resources on the on-board web processing. The Flight software reconnects 20 seconds after you have stopped using the web. So opening and immediately refreshing the set-up web page will indicate the Flight Software has been disconnected, this is intentional.
(vii)If you're running on Android, make sure you have all other Wifi networks set to Forget to prevent unintended reconnection to the wrong Access Point. Just have the one AirWare SSID on your list of connects and close all webpages in background.
(viii)The Node boards are extremely cheap. To date we have found one dodgy one out of about 10 purchased, so if you find the board repeatedly disconnecting from the USB or crashing it may be cured with a new one! Good job they are only cheap ;)
(ix)If your using a HTC HD2 the phone is a bit strange how it connects to wifi, searching the internet, the phone has lots of problems with some routers, we have found it can take several attempts to connect to wifi on the node board, if you add the password and then just wait it will finally connect after 1-3 minutes, no fixed time, just random, so just make sure you have the one access point in the wifi connection list and then let it start to connect, load LK8000 and it will connect in time.
1. You have accidently clicked connect nrf905 on the webpage - this will try and connect to a different RF board - this should remain unattached for most purposes
2. You have got the antenna wire shorted out, please put a resistance meter over the sma connection or over the signal and ground ( pins one and two on the RF Lora board ). This should be open.
If you succesfully install AirWhere on any other hardware please write a How To and some pics and send it in, thanks