Messages

1

Technical Support / Re: Static IP address after upgrade

« on: June 26, 2019, 10:43:59 am »

Thanks Lee - yes, I can ping it no problem, for the http://paw.local to work I need to turn on the WiFi on the PC, same as using 192.168.1.1

No big issue, I'll just have to get used to using the USB stick method for updates if it's not connected to the internet.

thanks

Gareth

2

Technical Support / Static IP address after upgrade

« on: June 25, 2019, 08:53:30 pm »

Seem to have lost my static IP address for my unit after upgrade despite copying across my config file and profiles from my the old card. When I'm not flying I usually have my PilotAware unit set up as a base station connected by an ethernet cable to allow easy access over my home network to back up tracks, perform updates and see a list of traffic overhead.

The option to modify the IP address is now greyed out so I can't change it, (tried on the phone and on the PC connected via WiFi), it doesn't seem to be recognising the settings in the config file, any suggestions?

Here's the contents of my config file

volatile_replay=0
volatile_tfc=0
volatile_trp=0
volatile_adsb=0
volatile_nmea=0
volatile_nav=0
volatile_trx=0
volatile_bmp=0
keywords=UNDEF_9550F4.cfg
config_ident=9550F4
config_flightid=UNDEF
config_groupid=PAWGRP
config_ac_type=10
config_ac_ann=0
config_modecs_select=2
config_modecs_detect=3
config_modecs_sep=4
config_distwarn_select=0
config_horzdisp_select=0
config_vertdisp_select=0
config_license0=5D9F
config_license1=043C
config_license2=976E
config_license3=50E0
config_volume=10
config_usbp1_type=0
config_usbp1_baud=0
config_usbp2_type=0
config_usbp2_baud=0
config_usbp3_type=0
config_usbp3_baud=0
config_usbp4_type=0
config_usbp4_baud=0
config_wifi_ssid=PilotAware-B827EB9550F4
config_wifi_phrase=
config_wifi_mode=1
config_wifi_channel=1
config_wifi_power=4
config_wired_dhcp=0
config_wired_static_ip=192.168.0.100
config_qnh=1013
config_license=5D9F043C976E50E0
=

thanks

Gareth

3

General Discussion / PilotAware Track file Post Processor

« on: October 02, 2018, 05:14:53 pm »

Just had a look at the Track file Post processor - looks good, tried replying with feedback to the post in the ecosystem category as requested but I've no 'reply' button for any of those threads..

Playback works nicely, however, the date displayed is a month out. August flights display as September, September flights display as October. I've checked the PilotAware date, and the PC's date, both are correct...

4

Technical Support / Re: Strange false positive

« on: September 04, 2018, 09:56:55 am »

Must admit I'd forgotten there's no registration data contained in a mode C transponder signal, thanks for the explanation Paul, I see why it's not a simple matter to screen out my own transponder now. Look forward to trying out the next software build to see if it's improved.

5

Technical Support / Re: Strange false positive

« on: September 02, 2018, 08:22:34 pm »

Thanks David - glad to hear I'm not the only one seeing the issue. I guess I'll have to try turning off mode C detection next time and see what the result is.

6

Technical Support / Re: Strange false positive

« on: September 01, 2018, 10:33:25 am »

I'd be surprised if it is a dodgy connector Paul, everything appears tight. I'd suspect the reason for it showing up when maneuvering is the distance and hight I'm flying from a radar ground station. As I lift the wing in a turn I'm guessing it provides just enough change in the position of the transponder aerial for it to be picked up by a ground station and the transponder to start replying to it.

Why my own transponder signal is not been screened out by the PilotAware filter and why it's showing a spurious ID on the screen, that I can't explain..

7

Technical Support / Re: Strange false positive

« on: August 30, 2018, 01:33:58 pm »

here's the track file Lee

https://www.dropbox.com/s/2uelmdumi7zasxe/2018-08-28_11-14.trk?dl=0

Its usually when I reach a turn point, or obit for some reason. Soon as I bank into a turn, that's when it happens, not really noticed it when climbing or descending.

thanks

Gareth

8

Technical Support / Strange false positive

« on: August 30, 2018, 12:28:19 pm »

Any thoughts on this one, I'm getting this sort of warning on a semi-regular basis, it usually occurs when maneuvering, if I turn the aircraft transponder to standby it disappears, reappears when I switch it back to ACS. I've got the Hex code entered correctly and Mode CS Filter set in PilotAware as far as I can see..

thanks

Gareth

9

Technical Support / Re: Software Update 20180129

« on: February 05, 2018, 08:08:31 pm »

Thanks Lee - the issue turned out to be a poor generic 75cm USB extension cable (how many times have you heard that?!). Swapped to the usual Anker Powercore 20100 battery pack that I use when flying, I get throttled=0x0. For home use I usually plug the PilotAware into an Anker USB Charger 4.8A/24W 2-Port USB Wall Charger. Replaced the generic 75cm USB extension lead needed to reach the bay window with a heavy duty Syncwire cable  (http://amzn.eu/5s9R9oI) and that also gives me throttled=0x0.

I swapped the standard RTLSDR for a NooElec Nano 3 a few weeks ago when I rehoused my PilotAware in a Stratux case to try and tidy things up a bit. I've no information on its power requirements I'm afraid. I wasn't convinced the old RTLSDR was working reliably, left on continuously for days on end as ground station, sometimes it would show no ADSB traffic at all for long periods of time, and would immediately display multiple contacts on rebooting. Now I'm wondering if it was a power supply issue after all...

thanks

Gareth

10

Technical Support / Re: Software Update 20180129

« on: February 04, 2018, 07:41:56 pm »

Thanks all, I'd not appreciated the need to update the operating system, just kept installing the new PilotAware update whenever one was released.

Yes, my device is configured as a base station and sat on the window sill most of the time when it's not in the aeroplane.

Fresh install from scratch on another SD card seems to have done the trick and I've now got a message alternating between throttled=0x5005 and throttled=0x5000 (whatever that might mean!)

thanks again

Gareth

11

Technical Support / Re: Software Update 20180129

« on: February 03, 2018, 08:44:52 pm »

After updating I'm seeing

error=1 error_msg="Command not Registered"

Under UPTIME on the home page which I don't recall seeing before. Tried rebooting but still present, any ideas?

thanks

Gareth

12

General Discussion / Re: Call sign UP-OGN on detected by Pilot Aware

« on: April 22, 2017, 09:23:27 pm »

lots and lots of UP-OGN on the way back from Sywell today...

look forward to hearing about this 

13

General Discussion / Re: Sky Demon and Radar on one screen

« on: December 05, 2016, 08:34:58 pm »

Also on a Motorola Nexus 6 (bit small for using SkyDemon though..)

14

General Discussion / Re: Sky Demon and Radar on one screen

« on: December 05, 2016, 08:32:44 pm »

Only just tried it with the PAW on the ground, but yes, the split screen function appears to work with radar and SkyDemon in Android 7.0 (here on a Nexus 9)

15

General Discussion / Re: LAA Rally

« on: September 11, 2016, 08:07:54 pm »

I didn't fly into Sywell but took my PilotAware along and had it running as a receive only ground station in my bag whilst airside. Picked up a few arrivals on phone as well as the PilotAware/Skydemon Ground station but not as many as I hoped. Saw Paul land in G-DOGG but didn't get any indication on my phone and can find no record in the downloaded log (I can't find any PAWGRP tags in the logs when they're opened in a text editor in fact)

Here's my logs from Sunday
https://www.dropbox.com/s/clniigmc9m4anem/2016-09-04_09-46.trk?dl=0
https://www.dropbox.com/s/vvb9he146e7jm1b/2016-09-04_13-49.trk?dl=0

Is there anything I can do to check it is working as it should be?

thanks

Gareth