PilotAware
British Forum => Technical Support => Topic started by: MrSums on September 02, 2017, 12:05:05 pm
-
Hi guys,
I have been trying for the best part of 9 months; now to make my unit work robustly and consistently. Understand the power requirements and just purchased an Anker PowerCore 13000 which is supposed to supply 3amps. I purchased the built unit from you last year and have updated the firmware consistently - on current verison as of now.
The issue is that the wifi signal drops out after a random amount of time - on the Anker this morning it was running fine for a couple of hours and dropped, so I rebooted and it dropped after only a few minutes. Could this be a wofo dongle issue?
Here is this morning's log file, following the first reboot:
(10:53:37) NAV-UDP : /var/lib/misc/udhcpd.leases Lease file updated
(10:53:23) ADSB-USB : Connected
(10:53:22) NAV-UDP : /var/lib/misc/udhcpd.leases Lease file updated
(10:53:07) NAV-UDP : /var/lib/misc/udhcpd.leases Lease file updated
(10:52:52) NAV-UDP : /var/lib/misc/udhcpd.leases Lease file updated
(10:52:37) NAV-UDP : /var/lib/misc/udhcpd.leases Lease file updated
Use of uninitialized value $eth0_ip in concatenation (.) or string at htdocs/index.cgi line 152.
(10:52:22) NAV-UDP : /var/lib/misc/udhcpd.leases Lease file updated
Use of uninitialized value $eth0_ip in concatenation (.) or string at htdocs/network.cgi line 218.
(10:52:07) NAV-UDP : /var/lib/misc/udhcpd.leases Lease file updated
Use of uninitialized value $eth0_ip in concatenation (.) or string at htdocs/index.cgi line 152.
(10:51:52) NAV-UDP : /var/lib/misc/udhcpd.leases Lease file updated
(10:51:37) NAV-UDP : /var/lib/misc/udhcpd.leases Lease file updated
(10:51:22) NAV-UDP : /var/lib/misc/udhcpd.leases Lease file updated
(10:51:07) NAV-UDP : /var/lib/misc/udhcpd.leases Lease file updated
(10:50:52) NAV-UDP : /var/lib/misc/udhcpd.leases Lease file updated
(10:50:38) NAV-UDP : /var/lib/misc/udhcpd.leases Lease file updated
Use of uninitialized value $eth0_ip in concatenation (.) or string at htdocs/network.cgi line 218.
(10:50:23) NAV-UDP : /var/lib/misc/udhcpd.leases Lease file updated
(10:50:08) NAV-UDP : /var/lib/misc/udhcpd.leases Lease file updated
(10:49:53) NAV-UDP : /var/lib/misc/udhcpd.leases Lease file updated
(10:49:38) NAV-UDP : /var/lib/misc/udhcpd.leases Lease file updated
Use of uninitialized value $eth0_ip in concatenation (.) or string at htdocs/index.cgi line 152.
(10:49:23) NAV-UDP : /var/lib/misc/udhcpd.leases Lease file updated
(10:49:08) NAV-UDP : /var/lib/misc/udhcpd.leases Lease file updated
(10:49:07) NAV-UDP : /var/lib/misc/udhcpd.leases Lease file update
'
(10:49:05) NAV-TCP : NAV_LOGGING Message='
(10:49:05) NAV-TCP : Device Table End
(10:49:05) NAV-TCP : Device 10 = NAV_LOGGING
(10:49:05) NAV-TCP : Device Table Start
(10:49:05) NAV-TCP : Device Add 10 NAV_LOGGING
(10:49:01) TFC-USB : Startup
(10:49:01) MAIN : Radio OK
(10:49:01) MAIN : Await Radio Startup
(10:49:00) MAIN : Await Radio Startup
(10:48:59) MAIN : Await Radio Startup
(10:48:58) BMP-I2C : HW_OK
(10:48:58) MAIN : Await Radio Startup
(10:48:57) MAIN : Await Radio Startup
(10:48:56) MAIN : Await Radio Startup
(10:48:56) FILESYS : Mount RO
(10:48:56) FILESYS : Mount RW
(08:30:23) COMMON : Set Date/Time 2017/9/2 10:48:56 DST=0
(08:30:23) BMP : MPL3115A2 inreset=0
(08:30:23) TRX-SER : Configuration Complete
(08:30:23) MAIN : Await Radio Startup
(08:30:22) TRX-SER : Settings Reconfigured Successfully
(08:30:22) BMP : MPL3115A2 inreset=1
(08:30:22) MAIN : Await Radio Startup
(08:30:22) GPS-USB : Connected to /dev/usbp3
(08:30:21) MAIN : Await Radio Startup
(08:30:21) ADSB-USB : Connected
(08:30:20) MAIN : Await Radio Startup
(08:30:19) MAIN : Await Radio Startup
(08:30:18) MAIN : Await Radio Startup
(08:30:17) TRX-SER : Serial Device = /dev/ttyAMA0
(08:30:17) TRX-SER : Serial Device = /dev/ttyAMA0
(08:30:17) FLM-USB : Startup
(08:30:17) GDL-USB : Startup
(08:30:17) MAV-USB : Startup
(08:30:17) TRP-USB : Startup
(08:30:17) FEEDOUT : Listening for Connection
(08:30:17) GPS-USB : Startup
(08:30:17) TRX-SER : Configuration Begin
(08:30:17) MONITOR : DNS UnResolved
(08:30:17) MONITOR : NetMonitor start
(08:30:17) ADSB-USB : Attempting connection
(08:30:17) MONITOR : SysMonitor start
(08:30:17) MAIN : Q[2] 0 messages
(08:30:17) MAIN : Q[1] 0 messages
(08:30:17) MAIN : Q[0] 0 messages
(08:30:17) INTERNAL : today=20170902 sysdata.license.date=20171118
(08:30:15) COMMON : config_wifi_power=3
(08:30:15) COMMON : config_wifi_power=3
(08:30:15) COMMON : config_wifi_channel=9
(08:30:15) COMMON : config_wifi_channel=9
(08:30:15) COMMON : config_wifi_mode=1
(08:30:15) COMMON : config_wifi_mode=1
(08:30:15) COMMON : SSID changed to PilotAware-B827EB907205
(08:30:15) COMMON : SSID changed to PilotAware-B827EB907205
(08:30:15) MAIN : Feature Set = 00000003
(08:30:15) MAIN : revision: a01041
(08:30:15) MAIN : pcb revision: 1
(08:30:15) MAIN : manufacturer: Sony
(08:30:15) MAIN : model: Model B Pi 2
(08:30:15) MAIN : processor: Broadcom BCM2836
(08:30:15) MAIN : memory: 1024 MB
(08:30:15) MAIN : version #858 SMP Tue Mar 15 15:56:00 GMT 2016
(08:30:15) MAIN : sysname Linux
(08:30:15) MAIN : release 4.1.19-v7+
(08:30:15) MAIN : nodename pilot3i-rpi
(08:30:15) MAIN : machine armv7l
PilotAware.exe Version 20170721
(08:30:15) SERVER : Starting PilotAware 1 ...
-
Come on guys, give me a clue ...
I have spent countless £££ on power supplies and bricks. I have just spent more money on a replacement wifi dongle. I read this http://forum.pilotaware.com/index.php/topic,986.0.html (http://forum.pilotaware.com/index.php/topic,986.0.html) post and bought a usb extension as the ADS-B dongle certainly seemed to get hot.
All to no avail - I have a PAW system that will fire up and last about as far as taxiing to the end of the runway and then becomes just added weight to the airplane as I furiously reconfigure my GPS to use a reliable source.
What do you need by way of logs that will help us through this?
-
It could be there is an intermittent fault here, I think we need to arrange a return.
Do You think this is the best option ?
Thx
Lee
-
Hi Lee,
It doesn't look like anyone else is having the same problems I have, so I suspect you may be right. Happy to swap the unit out.
Best
Robert
-
Hi Lee,
It doesn't look like anyone else is having the same problems I have, so I suspect you may be right. Happy to swap the unit out.
Best
Robert
Hi Robert,
I will send a PM
Thx
Lee
-
Well this is a turn-up.
I removed the SD card in order to return the unit and as I did so, it dropped back through the slot into the body of the unit - what a clutz I am.
So I took the screws out and found the card. Looked at the unit and thought the bridge was not fully plugged in to the m/b; took them apart and fitted them together again. Put the unit together and thought I may as well try it out before returning.
Lo and behold (and any other expletives you find appropriate) it is as solid as a rock. The battery pack ran out last night without dropping the signal and after recharging, it has been up for nearly 6 hours this morning.
Happy days. Thanks again to Lee for putting up with my grumbles.
Robert
-
This sort of thing has happened before. Maybe the PAW guys could put a bit of adhesive foam in the case so that it presses down on the connector.
-
Well .....
I am not totally convinced, I would not expect the WiFi to be affected by the bridge.
Could you 'soak test' for longer so we can be convinced ?
Thx
Lee
-
Could be be causing the unit to crash?
-
Sure Lee - I am going to keep it up for a couple of days, recharging the battery each time. I'll update in a while
Robert
Well .....
I am not totally convinced, I would not expect the WiFi to be affected by the bridge.
Could you 'soak test' for longer so we can be convinced ?
Thx
Lee