Messages

1

OGN-R PilotAware / Converting OGN station to Atom

« on: April 25, 2023, 07:39:49 pm »

Hi I have been involved in converting UKLLE to PWUKLLE . We are having difficulty with Flarm Reception or possibly seeing Flarm reception on OGN . I note that OGN Range calls the station PWUKLEE . Is this likley to be causing a miss match between servers ?
Any help please !
Doug

2

Technical Support / Re: Disconnection from Sky Demon

« on: June 13, 2019, 09:03:43 pm »

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

3

Technical Support / Re: Disconnection from Sky Demon

« on: June 13, 2019, 08:44:54 pm »

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

4

Technical Support / Re: Disconnection from Sky Demon

« on: June 13, 2019, 04:14:28 pm »

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

5

Technical Support / Disconnection from Sky Demon

« on: June 13, 2019, 01:06:05 pm »

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

6

Technical Support / PAW output to Google Maps

« on: September 26, 2016, 10:33:40 pm »

Is there a way to link PAW to a free PC based mapping system ?  Google Maps ?  This would give an output to a ground station without the need for a dedicated Navigation system. Might be usefull for small ATC units.

7

Technical Support / Re: Audio Testing

« on: July 15, 2016, 01:33:01 pm »

Hi all, I have installed the little amp that Lee pointed out on e bay. I can get good volume.  Testing in the hangar I am getting an annoying amount of interference. All other electronics, stropbes etc are  OFF except intercom.  There is a distinct click click  plus some white noise.  If you turn the PAW on and off you can hear it go thro a start up sequence. Depower the PAW or disconnect the audio lead and it disapears.  I have also tried moving the PAW away from the little amp board with no success.

 I need to ask pretty please that the PAW volume reset on power off bug is de bugged.  If I turn the PAW up I get enough signal for the s/n to be ok.

I am convinced that the audio is the best feature of PAW. 

Doug

8

General Discussion / Re: Enhancement Requests

« on: June 28, 2016, 03:51:39 pm »

Audio volume.  Will there be an update soon to make the audio volume stay at the required level after a re set ?  Only asking to prevent me installing the little £3 audio board from e bay if I do not need it.

9

Technical Support / Re: Audio Testing

« on: June 23, 2016, 08:14:33 pm »

I have ordered a little amp board just in case.  I am hoping to use an audio input that was once used for an ADF.  This will be neat as I can switch the paw audio off if need.   I also noticed the clicking interference but it was not really significant.
I will have a fiddle with a head set at home and next time at the plane reset the vol at power up plus have a co pilot. Last night I was engine warming in a 15 - 20 kts wind so really needed to have my eyes outside.

10

Technical Support / Re: Audio Testing

« on: June 23, 2016, 10:51:10 am »

Probably not.  There would have been several power down / ups before getting airborne and bright sunlight slightly bumpy and being solo conditions meant I did not do much fiddling in the air.  I will pause or take note
 until the bug is sorted.  Maybe the web page could indicate the level set.  That would be useful.
I did have fun with the other a/c that had my old PAW with new bridge in it and we re set up on the ground and did an air to ground demo to a few of the Mona Flying Club members.

11

Technical Support / Re: Contact lost intermittently with other paw unit

« on: June 23, 2016, 10:40:35 am »

It would be good to have some info on PUK antenna as they look like a good external option.  I am trying to find a good antenna position in the rear not blocked by that well known blob of water, my head. If one of the RF experts could comment I will buy one and give it a go.

12

Technical Support / Re: Audio Testing

« on: June 23, 2016, 10:27:30 am »

I tested audio airborne last night.  OK on the ground but ( on max I think but is there any way of proving it ?) not loud enough in the Jodel. I was using a redundant audio in feed from an old adf.

What is the Pi output levels ?  Next plan is to try a mic input with the Pi any comments ? I am working thro a 4 place intercom.

Doug

13

Technical Support / Re: Newbuild not working.

« on: June 20, 2016, 12:40:14 pm »

I assume you have done it by buying bits not a kit.  I would be very suspicious of your power supply.  Can you connect something else to the micro usb plug, maybe a phone , to prove you have power . 
Do you have all the other bits plugged in GPS, wifi dongle and adsb/tv dongle ?

Doug

14

Technical Support / Audio Testing

« on: June 20, 2016, 12:35:31 pm »

I have found it useful for audio testing that when you change the volume via the configure panel a nice young lady says " Pilotaware "  If this is not in the instructions then it would be a useful inclusion. As described in the instructions the test setting of Mode S also provides audio warnings that are a usefull test.

Doug

15

General Discussion / Re: Results and setups

« on: June 18, 2016, 08:54:03 pm »

Buying the commercial lead and chopping it up to work out the connections is a great idea. Trying to solder up the 4 ring jacks is horrible.