Topics

1

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

2

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...

3

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

4

Technical Support / Loss of position information in flight

« on: July 25, 2016, 11:08:49 pm »

Any idea what's happening here? Took my PilotAware on a flight from Netherthorpe to Duxford today and lost position shortly after take off. However SkyDemon was still reporting 11 satellites, as was the webpage when I logged onto the PilotAware homepage.

Tried disconnecting and reconnecting the wifi and restarting SkyDemon multiple times with no effect. The only thing I did not do was reboot the PilotAware box (which I wish I'd thought to try whilst airborne!)

When I changed from Flarm to internal navigation SkyDemon performed normally for the remainder of the flight.

Interestingly on the return trip the PilotAware / SkyDemon setup performed flawlessly, no changes to its position in the aircraft, power supply or handset.

Any thoughts?

Thanks Gareth

5

General Discussion / NOOK Simple Touch and PilotAware

« on: July 03, 2016, 08:13:45 pm »

I've been experimenting with a old 6 inch ebook reader, the Barnes & Noble NOOK Simple Touch. It's been rooted so it's possible to sideload APKs onto it. Anyhow XCSoar installs seems to run ok on it, it connects to the PilotAware and displays traffic and airspace. Don't think it'll replace skyDemon for me but it might be of interest to folk looking for a daylight readable screen as an alternative to the Kobo Mini, mine was very cheap when they were being sold off as end of line. Hopefully I'll get chance to take it flying this week and see how it performs in the air.

6

General Discussion / ARF transmission with 20151219

« on: December 21, 2015, 02:28:14 pm »

I'm not getting any indication that the PilotAware is broadcasting on my airband scanner with the latest version, swap back to an SD card with an old version (20151107) and I get a nice strong blip  every 2 seconds as usual. PilotAware and scanner in bay window for testing as always, home page reports TRX (RXTX) Enabled TX=339 RX=0 CRCFAIL=0 as normal, if I adjust the squelch on the scanner to hear the static I can just about pick out a blip but it is very weak, certainly not enough for the scanner's squelch to distinguish from background.

I know there will be a new ARF board along shortly, could this anything to do with using the original one?

7

General Discussion / Pi Zero and PilotAware

« on: November 26, 2015, 07:14:14 pm »

Probably off topic for most people but I thought I'd post this in case it is of interest to some. I picked up one of the new Pi Zero's today, it's basically a stripped down version of the original Pi1, 512MB RAM, 1GHz Broadcom BCM2835 processor, 40 pin GPIO Header, micro USB for power and data etc.

Anyhow I thought I'd give it a try with PilotAware, got enough leads to get it hooked up to everything except a monitor (which isn't usually needed). Initially took the MicroSD card out of one of my working PilotAware units (the second one I put together, based on my original 256MB Pi1, no ARF. Wifi, GPS Dongle and DVB all on a powered USB hub). Unfortunately on applying power there was no sign of the PilotAware hotspot appearing, the only sign of life was the flashing power LED (7 short flashes, then 1 long, then repeats).

Next I tried a clean install with a freshly partitioned and formatted card, installation files copied on to it as usual, put it in the Pi Zero, applied power and left it to do its thing, partition the card, and install the operating system. After 90 minutes there's still no sign of the PilotAware hotspot appearing (usually takes 15 mins or so with the cards I'm using), still getting the same flashing power LED (7 short 1 long, then repeats). When I power down and remove the MicroSD card it still shows 1 big FAT32 partition in GParted, rather than the numerous partitions of a successful PilotAware installation.

A bit of googling seems to indicate that folk using Raspbian have similar issues using old installations, the official Pi Raspbian NOOBS was updated a couple of days ago (to support the new hardware?) so I'm guessing this must be a similar situation. Until my Mini HDMI adapter arrives it's difficult to progress any further, I know the Pi Zero is not on the list of supported hardware, but given its very small form factor, low price, Pi1 architecture and low power consumption (160mA quoted) I'd be interested in anyones suggestions on anything else to try to get it working.