Disconnection from Sky Demon

[dougblair]

I have recently resurected my PAW Classic
Key is up to date
Power lead is good 20 swg
Power supply ( mains at home ) is good
Using a noo elec sdr ( bought for my eventual paw ogn base station )
I am connecting to SD by Flarm code 6000
At home I can see adsb traffic and GPS
In the air at the weekend I had a couple of disconnects

At home where I am not watching all the time the log suggests I am getting disconnects.

Log as below for those cleverer than me.  Suggestions please.





(11:41:38) BFLY-TCP  : Device Table End
(11:41:38) BFLY-TCP  :     Device 11 = NAV_LOGGING
(11:41:38) BFLY-TCP  : Device Table Start
(11:41:38) BFLY-TCP  : Device Del 39 NAV_SKYDEMON
(11:41:38) BFLY-TCP  : Device Connection Lost fd=39 count=-1 : Broken pipe
(11:41:38) INTERNAL  : PilotAware received SIGPIPE Continuing
(11:39:36) BFLY-TCP  : Device Table End
(11:39:36) BFLY-TCP  :     Device 39 = NAV_SKYDEMON
(11:39:36) BFLY-TCP  :     Device 11 = NAV_LOGGING
(11:39:36) BFLY-TCP  : Device Table Start
(11:39:36) BFLY-TCP  : Device Add 39 NAV_SKYDEMON
(11:31:41) BFLY-TCP  : Device Table End
(11:31:41) BFLY-TCP  :     Device 11 = NAV_LOGGING
(11:31:41) BFLY-TCP  : Device Table Start
(11:31:41) BFLY-TCP  : Device Del 36 NAV_SKYDEMON
(11:31:41) BFLY-TCP  : Device Connection Lost fd=36 count=-1 : Broken pipe
(11:31:41) INTERNAL  : PilotAware received SIGPIPE Continuing
(10:07:52) BFLY-TCP  : Device Table End
(10:07:52) BFLY-TCP  :     Device 36 = NAV_SKYDEMON
(10:07:52) BFLY-TCP  :     Device 11 = NAV_LOGGING
(10:07:52) BFLY-TCP  : Device Table Start
(10:07:52) BFLY-TCP  : Device Del 41 NAV_SKYDEMON
(10:07:52) BFLY-TCP  : Device Connection Lost fd=41 count=-1 : Broken pipe
(10:07:52) INTERNAL  : PilotAware received SIGPIPE Continuing
(10:07:49) BFLY-TCP  : Device Table End
(10:07:49) BFLY-TCP  :     Device 41 = NAV_SKYDEMON
(10:07:49) BFLY-TCP  :     Device 36 = NAV_SKYDEMON
(10:07:49) BFLY-TCP  :     Device 11 = NAV_LOGGING
(10:07:49) BFLY-TCP  : Device Table Start
(10:07:49) BFLY-TCP  : Device Add 36 NAV_SKYDEMON
(09:57:54) BFLY-TCP  : Device Table End
(09:57:54) BFLY-TCP  :     Device 41 = NAV_SKYDEMON
(09:57:54) BFLY-TCP  :     Device 11 = NAV_LOGGING
(09:57:54) BFLY-TCP  : Device Table Start
(09:57:54) BFLY-TCP  : Device Del 40 NAV_SKYDEMON
(09:57:54) BFLY-TCP  : Device Connection Lost fd=40 count=-1 : Broken pipe
(09:57:54) INTERNAL  : PilotAware received SIGPIPE Continuing
(09:57:47) BFLY-TCP  : Device Table End
(09:57:47) BFLY-TCP  :     Device 41 = NAV_SKYDEMON
(09:57:47) BFLY-TCP  :     Device 40 = NAV_SKYDEMON
(09:57:47) BFLY-TCP  :     Device 11 = NAV_LOGGING
(09:57:47) BFLY-TCP  : Device Table Start
(09:57:47) BFLY-TCP  : Device Add 41 NAV_SKYDEMON
(09:43:22) BFLY-TCP  : Device Table End
(09:43:22) BFLY-TCP  :     Device 40 = NAV_SKYDEMON
(09:43:22) BFLY-TCP  :     Device 11 = NAV_LOGGING
(09:43:22) BFLY-TCP  : Device Table Start
(09:43:22) BFLY-TCP  : Device Del 39 NAV_SKYDEMON
(09:43:22) BFLY-TCP  : Device Connection Lost fd=39 count=-1 : Broken pipe
(09:43:22) INTERNAL  : PilotAware received SIGPIPE Continuing
(09:43:18) BFLY-TCP  : Device Table End
(09:43:18) BFLY-TCP  :     Device 40 = NAV_SKYDEMON
(09:43:18) BFLY-TCP  :     Device 39 = NAV_SKYDEMON
(09:43:18) BFLY-TCP  :     Device 11 = NAV_LOGGING
(09:43:18) BFLY-TCP  : Device Table Start
(09:43:18) BFLY-TCP  : Device Add 40 NAV_SKYDEMON
(09:28:32) GPS-USB   : Corrupt Sentence count=4 line='6' errno='Success'
(09:26:50) BFLY-TCP  : Device Table End
(09:26:50) BFLY-TCP  :     Device 39 = NAV_SKYDEMON
(09:26:50) BFLY-TCP  :     Device 11 = NAV_LOGGING
(09:26:50) BFLY-TCP  : Device Table Start
(09:26:50) BFLY-TCP  : Device Del 36 NAV_SKYDEMON
(09:26:50) BFLY-TCP  : Device Connection Lost fd=36 count=-1 : Broken pipe
(09:26:50) INTERNAL  : PilotAware received SIGPIPE Continuing
(09:26:47) BFLY-TCP  : Device Table End
(09:26:47) BFLY-TCP  :     Device 39 = NAV_SKYDEMON
(09:26:47) BFLY-TCP  :     Device 36 = NAV_SKYDEMON
(09:26:47) BFLY-TCP  :     Device 11 = NAV_LOGGING
(09:26:47) BFLY-TCP  : Device Table Start
(09:26:47) BFLY-TCP  : Device Add 39 NAV_SKYDEMON
(08:52:37) BFLY-TCP  : Device Table End
(08:52:37) BFLY-TCP  :     Device 36 = NAV_SKYDEMON
(08:52:37) BFLY-TCP  :     Device 11 = NAV_LOGGING
(08:52:37) BFLY-TCP  : Device Table Start
(08:52:37) BFLY-TCP  : Device Add 36 NAV_SKYDEMON
(08:52:03) TFC-USB   : Startup
(08:52:03) MAIN      : Radio OK
(08:52:03) MAIN      : Await Radio Start
(08:52:01) MAIN      : Await Radio Start
(08:52:01) BMP-I2C   : HW_OK GNSS=574, PALT=759
'
(08:52:00) BFLY-TCP  : NAV_LOGGING Message='
(08:52:00) BFLY-TCP  : Device Table End
(08:52:00) BFLY-TCP  :     Device 11 = NAV_LOGGING
(08:52:00) BFLY-TCP  : Device Table Start
(08:52:00) BFLY-TCP  : Device Add 11 NAV_LOGGING
(08:52:00) BFLY-UDP  : Notice: Interval 366ms exceeds 250ms +2%
(08:52:00) FILESYS   : Mount RO
(08:52:00) FILESYS   : Mount RW
(08:47:07) COMMON    : Set Date/Time 2019/6/13 08:52:00 DST=0
(08:47:06) MAIN      : Await Radio Start
(08:47:04) MAIN      : Await Radio Start
(08:47:02) MAIN      : Await Radio Start
(08:47:00) MAIN      : Await Radio Start
(08:46:58) TRX-SER   : Configuration Complete
(08:46:58) MAIN      : Await Radio Start
Notice: Interval 1351ms exceeds 250ms +2%
(08:46:58) GDL90-UDP : (08:46:58) BFLY-UDP  : Notice: Interval 1351ms exceeds 1000ms + %
(08:46:58) TRX-SER   : Settings Reconfigured Successfully
(08:46:57) GPS-USB   : Connected to /dev/usbp3

[exfirepro]

Hi Doug,

What version of PilotAware Software are you running? and on what device? The ‘current’ version of PilotAware is 20180520, but Lee has done a considerable amount of work since last May - in part to address disconnects, particularly (though not exclusively) with SkyDemon on Android devices.

The new software is due for release shortly, so it might be worth your while waiting for the release unless you are running an older version than 20180520, but if you could answer the above questions that will help.

Regards

Peter

[dougblair]

Hi I am on version 20180520 and it is a Galaxy Tab s2

[SimonM]

I know you have said you are using a good cable and mains power supply but it really is worth checking the PAW unit Home page  192.168.1.1 to make sure your supply isn't throttled.

It should read Throttled 0x0 and not 0x50005 or 0x50000. The latter two suggest there is or has been a power issue.

Apologies if you've already done this.

[Admin]

Hi Doug
Just noticed you are using a nooelec sdr
Just wondering why not the one supplied with Pilotaware?
If I recall correctly, these draw upto a whopping 300ma

Also I fixed a number of issues related to android and udp
I would like to give you early access if you are ok to reformat an sd card for full install?
Thx
Lee

[dougblair]

Hi Lee,

I am happy to do a card format you can send me a beta version to try.

I will check out what current the noo elec SDR uses and still have several of the original SDRs. Noo Elec was really for my PAW OGN link. I have a higher gain antenna that fits it but why I want to see airliners 70 + miles away I do not know !!!!

Best Regards

Doug

[dougblair]

Throttled 0x0  which looks good.  The Noo Elec does use 300ma.  Does anyone know what the original sdr uses ?  I will dig out my old one.

Doug