SOLVED! - Pi 2 Wifi problems with a Nexus 7

[Vic]

Lee, I am running v 20160511


Vic

[Admin]

I am posting this on behalf of user Brian, I do not have access to a nexus 7, so difficult for me to advise, is this the same Mode G issue others are seeing ?

Hi All, Today i have tried for some time to complete step 5 of the PilotAware quick start guide.
When i connect my navigation device, nexus 7, to PilotAware all appears well (i am connected , no internet ) but if i open a browser and type 192.168.1.1 it will NOT take me to the PilotAware Homepage.
I have a SIM card in my nexus 7 and thought this may be giving me problems so i removed it and started all over again. Same result.
Any suggestions?

[Admin]

Hi Brian

Do you have access to another device to connect to PilotAware, this should rule out if PilotAware is working correctly ?
Any other device with wifi access is suitable. Even a PC

PilotAware should have alternating red/green LED's until the license is enterd do you see that ?

Thx
Lee

[exfirepro]

Hi Brian/Lee,

I remember at one stage way back in my early days on PAW having problems logging onto 192.168.1.1 because the tablet insisted on automatically adding a  'www' in front of the 'web' address. I can't remember if this was my Nexus 7 or iPad, though I'm pretty sure it was the Nexus, but the answer was to type http://192.168.1.1 which prevented the device trying to go to 'the internet'. Worked for me.

Might not be the answer but certainly worth a try.

Peter

[JCurtis]

I ordered a PAW this week and have access to a selection of devices, with an early N7 in the office, so happy to do some testing when it all arrives.

[Paul_Sengupta]

Yes, sometimes it does connect, but the actual IP traffic is very sporadic and sketchy.

One thing to ask people having problems is to try moving the tablet about 2 metres from the PAW and see if that helps at all.

[Vic]

Interesting you should suggest that Paul, I flew with my now Pi 2 PAW (Bridge not arrived yet) and my N7 on Wednesday.

On the outbound flight I was P1. The PAW was on top of the coaming on the other side of the cockpit, no more than a metre away from the N7. The connection was rock solid for the whole hours flight (although we did receive some odd mute lifting RFI on Lakenheath Radar's VHF frequency 128.9 while crossing their overhead ..perhaps it was the multiple F16's doing circuits beneath us!  )

On the return, I was passenger, with PAW and N7 some 200mm apart and the connection to Skydemon simply refused to stay up for more than 30 seconds in most instances. Looks like we possibly have some internal emissions problems in our 70's cockpit. Next time I'll try switching off the Bendix King DME which is most likely not WIFI compliant!

[Paul_Sengupta]

Upgrade to 20160530 and all will be well. 

[Vic]

Forgot to mention, I was already running 20160530 which I had previously tested as fully stable at home.

[Paul_Sengupta]

Ok, not quite solved.

I tried it in the car this evening to/from Popham. When I had the units about 30cm apart the connection kept dropping out, and I had to keep going back to Go Flying --> Use FLARM to reconnect. Moving the units about 40cm apart made the connection stable.

So going to "b" has helped, but it hasn't completely fixed it.