Show Posts

You can view here all posts made by this member. Note that you can only see posts made in areas to which you currently have access.


Messages - Mat

Pages: [1] 2
1
Technical Support / Re: WiFi repeatedly connecting/disconnecting
« on: May 31, 2023, 01:30:50 am »
Time I gave up and went to bed, but toggling the network routing functionality seems to change the behaviour.
  • Routing off - stays connected
  • Routing on - disconnections as above
I wonder what's changing on the Raspberry Pi as a result of this setting?

2
Technical Support / Re: WiFi repeatedly connecting/disconnecting
« on: May 31, 2023, 12:17:03 am »
I've had a good fiddle with the PilotAware on the bench tonight.

This is the repeated disconnection behaviour I'm getting with my Pixel 4a, and presumably similar with my mate's Pixel 2. It's immediate disconnection rather than some time later.



I've tried a few things, to no avail:
  • Disabled Battery > Adaptive preferences > Adaptive charging and Adaptive battery
  • Disabled Network & Internet > Adaptive connectivity
  • Disabled Mobile data (not really a fix, but worth trying)
  • Set a static IP

I had some success by manually setting an IP and DNS to 0.0.0.0 rather than using DHCP. This keeps the connection active, but doesn't seem to actually allow access to anything on 192.168.1.1  So close, yet so far. :'(

3
Technical Support / WiFi repeatedly connecting/disconnecting
« on: May 18, 2023, 09:57:02 pm »
A mate is having problems connecting to a PilotAware Classic unit running 20230316 from his phone (Android 11). It works fine with an Android tablet, but on his phone the WiFi connection repeatedly connects and disconnects (about 5 seconds later). I can replicate this behaviour with my own Android 13 phone.

It looks to me like it's Android not playing ball with an Internet-less WiFi access point. Slightly odd as it's worked fine from his phone in the past. I'm assuming something's changed in Android recently, or possibly something different in PilotAware 20230316 that Android doesn't like (I'm somewhat dubious, but with the same problem afflicting Android 11 and 13 I wonder if a change has triggered something).

As far as I can tell Android just doesn't like that there's no Internet available on the AP and I need to find a way persuade it that it's fine. There's lots of suggestions online for fixing this in various versions of Android over the last few years, so I've a series of things to try next time I can get near the device, but wondered if anyone else has experienced this problem and fixed it? I note the troubleshooting page references turning off the Android power saving facility, but it's not clear what setting that is in contemporary Android.

4
Technical Support / Incessant beep
« on: July 19, 2020, 12:22:25 pm »
Now I'm back flying again I've noticed that I'm getting an incessant regular beep through my headset every few seconds whenever I plug the Pi's audio output into the plane. It disappears when I unplug. Is this PilotAware? Is it trying to tell me something!?

I think the flight before last I ended up rebooting to 'fix' the problem. Thinking about yesterday's flight, I think I only got traffic alerts through SkyDemon. It was relatively quiet though. Maybe the two are related. is the beeping telling me something's stuffed?

It's a PilotAware classic running 20190621 into a TY91 then through to my Bose A20.  I think I've ruled out everything else as it only occurs when I plug in the PilotAware audio output into the Trig TY91 audio in, but I could do a bit more digging trying a second headset, etc.

5
Technical Support / Which Raspberry Pi
« on: September 16, 2019, 10:10:07 pm »
Am about to order an upgrade to my Raspberry Pi 2 to isolate the WiFi dongle from some drop-out issues I've been having on my PilotAware Classic. Although I suspect it's partly power supply issues. (Can't reallly justify a wholesale Rosetta upgrade).

However, I need to decide between Raspberry Pi 3B or 3B+ now that both work with the PilotAware software. I've found a supplier, but the latter seem to be in short supply with RS offering back-orders for Feb 2020!

Raspberry Pi 3B and 3B+ in comparison suggests power consumption is somewhat less on the 3B, with a few features missing/reduced. Much advantage of the older model for PilotAware?

6
Sorry Peter I didn't know it was yourself at Sywell last night!

We were all pretty knackered after five hours flying diagnosing tracking issues.  ;D

7
Yeah, my Sky Ranger Classic sometimes struggles to keep up with a CTSW, so he can be some way away.

G-XLAM and G-CJAK both run Trig transponders, I think G-SLNT has a Funke. That being said, we did have the amusement of another Funke transponder (sans PilotAware) flying sideways/backwards to France due ADS-B lacking correct heading info.

Further, G-XLAM's transponder is fed from a separate GPS mouse, not PilotAware. Not sure about the other two, but I'll direct them here.

8
This is clearly an issue with G-SLNT as both yourself and G-CJAK were seeing each other reliably throughout the trip.

What I failed to mention was that Alan in G-CJAK could see G-SLNT certainly on the first trip and I think on the second trip. So that adds a bit of more confusion.Not sure if he's got any relevant screenshots/tracklog.

In diagnosing this Alan also spotted another aircraft with a different ICAO between PilotAware and transponder. He's going to let him know (looks like a typo between 0 and 9). Surprisingly it didn't seem to cause any problems to us, although I suppose both were overlaid on the display.

[...] unlike G-CJAK and G-XLAM which were both rock solid, G-SLNT was jumping about all over the place like a mad thing - often racing ahead and off to the side of track at supersonic speed, then suddenly jumping back to the ‘group’ - so his position signal is at best ‘intermittent’ and that’s me being ‘polite’ about it.

That's just Kev's flying :) I had a bit of jumping about between me and G-CJAK earlier in the trip - noticed because I was jumping behind and ahead of him on screen but only close behind in reality. Didn't have spare brain capacity at the time to figure out whether it was him or me jumping about, but it was probably a somewhat smaller jump.

It’s almost certainly not the case here as you were seeing the others in your group, but remember that appearing on PAW RADAR but not on SkyDemon can simply be to do with your filter settings as your PAW Radar Screen is fed with RAW received data, whereas the data used to drive SkyDemon is subject to any filtering set in PilotAware AND any additional filtering set in SkyDemon. In this case however, you must have had ‘Mode CS’ selected in PilotAware (hopefully ‘+ Filter as you are transponder equipped) as the others are all showing as CSA. Out of interest - what Mode CS ‘Range’ and Vertical Display Range were you running? Same question for SkyDemon - Did you have ‘Show Bearingless Targets’ turned ‘On’ in SD - It’s now ‘Off’ by default and might have defaulted to this on your last SD update so worth checking. What did you have ‘Show Within Vertically’ in SD set to? As I say, almost certainly nothing to do with why G-SLNT wasn’t showing though.

I did wonder whether there was any filtering going on, but I'm not aware of any other than the vertical and horizontal extents. I thought I'd read there was a way to filter traffic (i.e. those you're flying all the way with) on the SkyDemon radar view, but I've never been able to get it to do anything other than show the corner bigger. Interesting that the radar display is RAW but the feed is further filtered in PilotAware before going to SkyDemon.

All settings you mention seem fine:



I assume automatic decluttering doesn't affect aircraft targets?

I was getting some bearingless targets, but presume these were other unsighted aircraft rather than a corruption of G-SLNT (e.g. one had what appeared to be a valid French registration).

You should be able to replay your track files using James Rose’s excellent replay tool at https://aircrew.co.uk/playback/ though I can’t remember if it differentiates between source systems.

I have a few tracklogs due to PilotAware drop-outs that I separately need to resolve, but I've put a large 20MB one on there (https://aircrew.co.uk/playback/2de11d) and a smaller 642KB one (https://aircrew.co.uk/playback/afc2f1). This seems to confirm G-SLNT is only received as PilotAware and no transponder, but doesn't explain why the PilotAware position was not shown on my SkyDemon (yet was on the radar).

the strange thing is not being visible in SD but it is in PAW-RADAR
If I can get a track file for this, it may give some clues.

2019-09-01_09-34.trk (20MB)
2019-09-01_12-09.trk (642KB)

What 3rd party connection method is used in SkyDemon ?

PilotAware.

9
Rather odd behaviour with PilotAware today. Flew to Blois with G-CJAK and C-SLNT this weekend (and others, but those were in our return formation today). All three aircraft including mine (G-XLAM) are ADS-B transponder equipped and have PilotAware devices connected to SKyDemon.

I have not been able to see G-SLNT all weekend in SkyDemon. Initially put this down to reception problems due to him being directly behind me and my device being sat on the dash. No problem with others. No difference with him in front. Something's up.

I had time to do a bit of digging during our hours of flying today:
* G-CJAK visible in SkyDemon and verbally in PilotAware audio output.
* G-SLNT not visible in SkyDemon (maybe I saw him once but not long enough to screenshot and shown as a hex [ICAO?] code which I assume was his due to location), very occasionally verbalised by PilotAware audio output.

Traffic display appears to show lack of CSA in mode column for G-SLNT (presume those are Mode-C, Mode-S and ADS-B?)



Radar display appears to show G-SLNT ahead of me (and G-CJAK) behind. Why does it appear here yet not in SkyDemon? I've never managed to get SkyDemon to filter traffic even though I know it's supposed to be able to. With hindsight should have checked with my phone too.



Logs appear to show CRC errors. Is this normal, or related?



Have pulled device from the plane, so can extract logs if I know what I'm looking for.

10
Sorry, I meant Android not Google. But yeah, it's an Android tablet which will preferentially connect to home or the club WiFi. I think the behaviour is the same when it's in the middle of nowhere.

I'll have to try AlanG's faff method and set a password. If that doesn't work, I'll look at a WiFi prioritisation app.

Cheers.

11
This has been bugging me for a while, but I thought to note it down for further research after flying today.

My PilotAware works fine, but I have to go through the process of connecting to the WiFi hotspot on every aircraft start. This is because Android reports "No internet access detected, won't automatically connect" (and asks whether I want to stay connected, although the answer generally doesn't matter). Invariably, I forget until after I've asked SkyDemon to 'Go flying' and have to backtrack.

I guess - as the error message suggests - Google is figuring out the PilotAware doesn't offer Internet access and refusing to remember it for future reconnection. I'd much prefer if my tablet would jump straight on the WiFi hotspot as soon as it appears.

Has anyone worked around this one?

I can see potential solutions but (settings, additional app, etc.) each needs trying against the PilotAware unit which is in the aircraft so if someone's solved it already knowing how could be handy.

12
Technical Support / Re: Raspberry Pi 2 Model B 1.2
« on: March 06, 2017, 07:09:46 pm »
Sorry, I wasn't 100% clear. I've gone through the process of Ciseco ARF, a beta bridge board, then final bridge board which has been in the plane for a while but I never got round to upgrading the Pi when the time came. I'll get one ordered and ask Lee for a license transfer once it arrives.

I know a mate had trouble with a Pi 1.2 initially but I've now clarified it was purely a software issue before the new version came out. Might as well get the slightly newer one now I know it is supported.

Cheers.

13
Technical Support / Raspberry Pi 2 Model B 1.2
« on: March 05, 2017, 09:55:30 pm »
Just thinking of upgrading my Raspberry Pi to a 2B to get the audio output and bearing-less targets.

Are there any major PilotAware-specific differences between the 2B and 2B version 1.2?


14
Turns out Raspberry Pis are out of stock at present.... but once I've solved that problem will be in touch.

15
I'd like to shift one of my PilotAware units from the original Raspberry Pi to a newer Rapsberry Pi 2B to take advantage of the extra features. I recall the license is tied to the MAC address of the Pi Ethernet now instead of the WiFi dongle as originally. Is this easy to do? (I presume it's not automated!)

Pages: [1] 2