Messages

31

Technical Support / ADS-B status line

« on: May 15, 2021, 03:50:38 pm »

This may have been answered before. I was tracking a friend's aircraft today with my PAW Classic. The traffic page showed only CS, and nothing in the ADS-B status line, but PAW Playback Grid and PAW Vector both show that he is transmitting ADS-B well. What am I missing?

32

Technical Support / Re: Vector shows PAW but not ADS-B signals

« on: April 02, 2021, 11:17:57 pm »

Thanks Peter. I'll see how the picture fills up with a few more varied flights.

33

Technical Support / Re: Vector shows PAW but not ADS-B signals

« on: April 02, 2021, 09:40:36 am »

On the SE 2 web page, this is the claim:

With 20W transmit power, your 1090MHz ADS-B signal can be received up to 40NM away.

So, the limit seems to be 40NM, or 74km.

You're getting some pings up to 40km,and the occasional towards 50km, looking at your diagram?

You don't say if your PAW is using the integral, internal or external aerials, or what sort of aircraft it is, metal, wood or rag & tube?

Low wing, wood and fabric. Classic PAW, internal aerials, central on the coaming. SE2 in 3 positions: coaming RHS, central behind me near canopy, canopy RHS low. (to keep it vertical). On PAW playback grid, not a lot of difference between the SE2 playback for the 3 positions, but some breaks compared with PAW. On FR24 the addition of SE2 shows tracking to a much lower height on take-off/landing compared with previous Mode S only. Of the 8 PAW stations which tracked me (for at least some of the time), 5 were within 22nm the whole time, the other 3 never more than 43nm. Hence my question about whether some ATOM stations are not receiving ADS-B In. Does any one else have PAW/SE2 comparison for their flights? And I recognise that this is air-to-ground, not air-to-air.

34

Technical Support / Re: Vector shows PAW but not ADS-B signals

« on: April 01, 2021, 10:41:24 pm »

Flew yesterday with my new Sky Echo 2 as well as PAW; 3 flights Garston Fm-Devizes-Lyneham-GF, up to 4000',  to compare different positions of the SE2. Vector plots of the 3 flights combined given below for PAW and SE2. Very impressed by PAW coverage (though there's room for improvement in some sectors): 8 stations in total (Wadswick, Shirenewton, Calne, Clench, Kemble, Oxford, EGVL, Enstone, with at least 4 most of the time. SE2 results significantly thinner. Referring back to earlier messages on the thread, is this because quite a few of these ATOM stations don't have ADS-B In capability (is this listed anywhere?), or should I be wondering about the performance of my SE2?

35

Technical Support / Re: Aircrew Playback symbology

« on: March 08, 2021, 10:23:31 am »

Thank you Lee, very thankful for ATOM/Grid! Keep up the good work.

That explains PU from gliders, but not the 'static' or C-GKOA's ACS position - unless U or M are not always shown?

M shouldn't be overload, it can always be ignored - the important thing is to have as much visibility of traffic as possible. I was just trying to explain PAW and Aircrew Playback to someone else and realised that there were things I didn't understand.

Trevor

36

Technical Support / Re: Aircrew Playback symbology

« on: March 08, 2021, 09:24:40 am »

Thank you James, I hadn't noticed that hovering worked! As the PAW traffic page uses A for ADS-B I'd assumed that Aircrew did the same, and therefore couldn't work out what B was.

On 'static', I attach a track file. At 12:41:22 over Newport Pagnell PA28 G-COVA is shown as ACSPUM and 'static' - though clearly it isn't as there is a track.  The aircraft NNE and NW of G-COVA are also labelled 'static' as are several other aircraft.

A couple more queries:

There are several gliders visible at 12:41:22 (including two to the south of my aircraft) shown as PU. I assume that, as FLARM is widely carried by gliders, but probably not many have PAW, these are FLARM outputs provided to me by Upload - correct? The use of P rather conceals the source; is every U accompanied by a P, ie does P just indicate an 869.5MHz transmission rather than specifically a PAW output? I also note NW of Banbury a glider with just P - I assume that this is a glider with a PAW unit.

At 12:46:15 C-GKOA (which I imagine is a Brize Skyvan paradropper) is manoeuvring around Weston-on-the-Green and shown as ACS - but no M or U. I would therefore have thought that it should be a bearingless target, but it is shown with a position.

So many questions! Apologies, but this display is fascinating!

Trevor

37

Technical Support / Aircrew Playback symbology

« on: March 07, 2021, 07:10:06 pm »

Could someone please remind me what the ACSPUMB identifiers on Aircraft Playback are? Also what is the implication of "Type: static"?
Is there anywhere which explains all this?

38

Technical Support / Re: Vector shows PAW but not ADS-B signals

« on: December 29, 2020, 05:13:04 pm »

Simples! Thank you.

39

Technical Support / Re: Vector shows PAW but not ADS-B signals

« on: December 29, 2020, 12:53:08 pm »

This answers a question I was about to ask, but to wander slightly off thread, how does VECTOR differentiate between ADS-B and CAP1391; aren't they both ADS-B outputs?

40

Technical Support / Re: PAW with uAvionix Skyecho 2

« on: November 13, 2020, 08:40:13 am »

As I understand it, SE2 is permanently on for 1090MHz ADS-B receive. If you have PAW (as I have) then just stay with PAW for input to your nav display. However if PAW for some reason stops working then transfer the WiFi connection to SE2 and carry on! SE2 just arrived so when next possible I'll find out whether this is correct.

41

Technical Support / Re: Loss of connection - PAW Classic

« on: August 02, 2020, 06:41:51 pm »

Flew again today (before I could act on either suggestion); same behaviour. Fine outbound. Unable to connect to WiFi for the return (IPhone wouldn't connect either). Tried again after landing - the same. Tried again 30 min later - fine!

I'll load WiFi Analytics and try removing the 1090Rx SDR - probably not for a few days. Thanks for the suggestions - keep to get back to normal working as it's been perfect for ages.

42

Technical Support / Re: Loss of connection - PAW Classic

« on: August 02, 2020, 07:42:02 am »

New WiFi dongle received from PilotAware Support, but I have the same problem. On outbound flight everything worked normally. At destination PAW was powered off, Nexus 7 tablet left running. For return flight, I could not establish a connection to the WiFi hotspot, though audio traffic messages were being received normally, and the Nexus was detecting other ground-based WiFis, even when airborne. Back at base, after both had been shut down, I tried again after about 30 min - connection established!

So doesn't appear to be anything to do with Device Connect Setting. Is there some connection within the PAW that I should be looking at? I did have it apart before this flight to make sure that the board was pressed fully home.

43

Technical Support / Re: Loss of connection - PAW Classic

« on: July 21, 2020, 12:13:45 pm »

Flew yesterday; while WiFi connected to the PAW before departure, with web pages visible, within 3 min of flight couldn't see PAW WiFi. Audio functioned perfectly, so PAW clearly running. New WiFi dongle should be with me shortly.

44

Technical Support / Re: Loss of connection - PAW Classic

« on: July 19, 2020, 11:26:52 am »

Further observations:

It's been running for 90 min now, still connected. And the time stamp is now correct. I have moved the WiFi dongle from below the GPS dongle - perhaps that has helped.

On Thursday's second flight, I wasn't able to see the PAW WiFi, let alone connect to it. At 1200' over Beaulieu, though, I was seeing half a dozen ground WiFis.

45

Technical Support / Re: Loss of connection - PAW Classic

« on: July 19, 2020, 09:33:24 am »

Thanks to both of you for comments. Lee - I thought I knew the answer to your questions, but now I'm not sure; I think I'm getting inconsistent behaviour. It's been running for about 20 minutes this morning, and twice the web pages have frozen (same result on IPhone and Nexus), but by the time I look at the WiFi connection (still showing connected) and turn back to the web pages it's running again.

Oh, now I've got "PAW connected" on both, and frozen web pages - but lights seem to be behaving normally. I have changed the port for the WiFi dongle - no difference. I suspect the dongle and ordered a new one on Friday - will let you know what happens with that. One query: though it was running for 20 min just now, the time code is still showing yesterday afternoon - the previous time I tested it.

And now the web pages are visible again!