PilotAware
British Forum => Technical Support => Topic started by: Ian Melville on August 23, 2016, 08:56:35 pm
-
Just given myself a headache and trashed two PAW, and it was all going so well.
Last night I downloaded the latest version and did a full install as per the script on a formatted SD card. Installed it in my PiB+ and once it booted, connected to he Wifi and input my license number. Bingo worked as advertised.
Tonight I stupidly reformatted the same SD card for the Pi2B, connected and entered my license key. all good so far. However on reboot it kept rebooting the Pi, and I spotted it was only when I tried to connect with a browser (in this case my iPad).
OK, download a new copy, extract. Format SD card and copy files to it. This time I the PiB+. Insert key info and again when I reconnect with the iPad browser it reboots the Pi.
Could it be the iPad? so switched to iPhone with a complete new installation and bingo, I back in. Until I set the license key and reboot, then I am in the same situation as with the iPhone.
I am also unable to connect via the LAN, with the WiFi dongle in or out
Before anyone says it the power, I have tried two Anker Batteries and a Mains Pi PSU. As these were two good working units, I doubt it's a hardware issue. I am either doing something wrong, of the image is failing.
Time to have food :)
-
Hi Ian,
Shouldn't think you have trashed anything. Sounds as though it could be a licensing issue.
Do you have two licences and are you inputting the correct licence details appropriate to each device?
-
that's a possibility, however after saving the license key, each showed a valid license and expiry date. All the modules also turned green.
Now I cannot get into the config page, I can not check what I did put in.
-
Do they both have Bridges?
-
Yup
-
I would plug in a tv to monitor the boot-up. Should give a clue. Software corruption?
-
Hi Ian
I saw a similar issue using a 1amp wall supply, with the HDMI and LAN connected.
Do you have these connected ?
If so, please try removing LAN and HDMI.
I did not fully investigate, but wonder if it is related to the 1.2amp USB peripheral
Supply setup
Thx
Lee
-
Hi Ian
One other thought I have had, could your web browser have cached the web page that performs a reboot ?
To be absolutely sure that you are going to the PilotAware landing page, it should be
http://192.168.1.1/index.html
Or
http://192.168.1.1/index.cgi
I have this saved as a hotlink on my desktop on my ipad
Thx
Lee
-
Hi Ian
I saw a similar issue using a 1amp wall supply, with the HDMI and LAN connected.
Do you have these connected ?
If so, please try removing LAN and HDM
Neither connected when I initially had the issue, I did connect both later to try and see what was happening.
All Power supplies are 2Aor greater
-
Hi Ian
One other thought I have had, could your web browser have cached the web page that performs a reboot ?
To be absolutely sure that you are going to the PilotAware landing page, it should be
http://192.168.1.1/index.html
Or
http://192.168.1.1/index.cgi
I have this saved as a hotlink on my desktop on my ipad
Thx
Lee
Now that is a possibility as I did the reboots from the browser page. Will have to wait until I get home to investigate further.
Cheers
-
Hi Ian
One other thought I have had, could your web browser have cached the web page that performs a reboot ?
To be absolutely sure that you are going to the PilotAware landing page, it should be
http://192.168.1.1/index.html
Or
http://192.168.1.1/index.cgi
I have this saved as a hotlink on my desktop on my ipad
Thx
Lee
Now that is a possibility as I did the reboots from the browser page. Will have to wait until I get home to investigate further.
Cheers
Aha, I think that will be it.
I have been working on the reboot strategy as part of the reboot and update flows
Its quite complicated, but there needs to be a background task that performs the reboots, rather than the foreground http server, otherwise there is his potential for the browser to cache the last page.
Basically the http server needs to redirect the browser to another page BEFORE performing the reboot.
Lookng forward to see if this is the issue
Thx
Lee
-
I've done that... Once! Now I tend to press the back button on the browser before it reconnects.
-
The good news lee is that was the issue. Both units running as advertised :)
-
The good news lee is that was the issue. Both units running as advertised :)
Phew!
Ok, seems like we need to implement a way f not getting the reboot page in the cache
Thx
Lee
-
I have had the same issues....
Check PAWS function and check access to Config Page on web browser. Download new software either using LAN or through the old way with SD card.
Fire up, connect to PAWS wifi, go to config page and...... wham nothing happens wifi drops out.
So it would seem that the latest software needs a different web page http://192 etc etc string than the previous software - how come??
I am going to try again with this
"To be absolutely sure that you are going to the PilotAware landing page, it should be
http://192.168.1.1/index.html
Or
http://192.168.1.1/index.cgi
Cheers
Bryan
-
Hi Bryan
The question is how are you getting to the config page ?
Are you typing the entire address, or is it one previously cached by the browser ?
After installation did you perform a reboot from the web interface ?
Thx
Lee
-
Ok so, before doing the software update I fired up the PAWS, went to the config page through my web browser (did not type new full address as it comes up when I start to type 192 etc). Never previously had to re-type full address on previous installs.
Switched off - connected to LAN, powered up, waited long time, powered down, disconnected LAN, powered up - waited long time, connected to wifi, went to web browser previous link was still there, refresh page, nothing happens, wifi drops out, try numerous times same results....
So take second unit do the same - get same result - scratch head and bit of arse tooo !! think ok perhaps try old software install process - so out with laptop, SD card etc. = same result - hmmmm resort to Forum and BINGO not first to have this issue and sure not going to be the last - follow the above thread and hey ho gets to config page - however need to now type in license key etc etc - first unit wont accept license key and says its expired.... oh crap now what - try second unit and that accepts its license key, will retry first unit again later... clearly a difference when doing the software upgrade when plugging into the LAN than doing it with the SD card method ??
Lee - I don't follow the "After installation did you perform a reboot from the web interface " if I cannot get to the web interface in the first place??
-
Hope this will help.
I updated to 20160820 by connecting to router via RJ45 patch lead.
Plugged in lead, switched on PA and left for about 15mins.
Unplugged and rebooted by cycling power, logged onto home screen with tablet by clicking on stored "pilot aware" favorite (not cashed address)
but still on previous version of sw, confirmed / shown on home screen.
Clicked the updates tab and this shown available update, clicked the install button.
I think the PA rebooted automatically and after all was working as per previous configuration without needing to do any further entry of licence number etc.
-
I am also having uissues since upgrading to 20160820. Using the supplied power cable, and the same wall supply that worked with teh previous version, I now find the WiFi is very, very flakey. Often cannot get into 192.168.1.1 at all, and keep finding that the phone or tablet has reverted to my home wifi and PAW wifi is not even showing on the available wifi list. Then it reappears and you get it to connect but it soon disappears again. I have gone form a robust system to one that is 100% unusable. Might it be that 20160820 demands jsut a bit more power and the prevously-adequate power supply is no longer enough? But I never had any power problems before, either on this wall charger or on a battery PSU
-
Hi Stu
Did you perform an upgrade, or full install from zip file ?
Also are you pi2 or pib+ ?
Thx
Lee
-
Bryan, same question, are you pi2 or pib+ ?
-
I have a Pi2B and I jsut did an auto-upgrade from teh July version. Since posting above, I have (a) reset it to "Powered" (aircraft) - Initially as soon as I had 20160820 I had set it to be Base Station RX as I am testing at home and thought I ought not really be transmitting as an aircraft; and also I changed it to show modes S (as it had previously been, though teh upgrade had reset it to "none") plus teh new Mode C, and set range to max. Since then it seems to have worked much better; initially it wa still a bit flakey but it has now managed to run fro over half an hour without loosing wifi.
-
It has now run continuously for 7 hrs without loosing teh wifi. So problem appears to be fixed or to have gone away. I really don't think I changed anything, but at least I now once more have something I can continue to est and prepare fro my aircraft installation.
-
Hi Stu
Could be the 'basestation RX' mode ?
Did you have a LAN/RJ45 connection when in the above mode ?
Thx
Lee
-
Sorry to be a bit late coming back on this but the problem is solved, I think it must have been that the system was continuously going to the cached address and not to the correct starting link, as discussed above.