1
Technical Support / Re: Track files upload
« on: September 27, 2025, 10:32:25 am »
Worked for me yesterday (26th) and today on my PC.
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.
2
Technical Support / Change of Pi
« on: May 01, 2025, 06:09:56 pm »
I have had to change the Pi on my Classic PAW because of a dodgy power socket. As the new Pi has a new MAC there is a mismatch with my current software key. I have looked on the PAW website for the procedure, but can not find anything relevant. Am I overlooking something? I have sent a request to support@pilotaware.com - is that the appropriate route?
3
Technical Support / Re: Track file discrepancies
« on: March 22, 2025, 12:59:07 pm »
Again thanks!
4
Technical Support / Re: Track file discrepancies
« on: March 21, 2025, 06:55:55 pm »
Thank you Steveu. I flew yesterday, was tracked fine by ground stations but the track file showed a sudden excursion after lift-off near B to the middle of the North Sea! I'll try a new card; please remind me - do I just plug it in or do I have to register it in some way?
5
Technical Support / Re: Track file discrepancies
« on: March 11, 2025, 09:32:10 am »
Than you Peter. G-DENS, 40263C. Is a fixed amount of card space allocated to track files and would overwriting when full cause a temporary dropout?
6
Technical Support / Re: Track file discrepancies
« on: March 10, 2025, 10:31:53 am »
Just to note: ground station replay doesn't show any discrepancy for the first two time periods mentioned, so what is happening appears to be confined to the recording process. For the third time period there is loss of contact with ground stations, but that may be because I was not in range of working stations in that part of Wales.
7
Technical Support / Track file discrepancies
« on: March 07, 2025, 11:01:41 am »
I give below the link for a track file on Playback from a flight this week from our strip near Bath to Haverfordwest. Viewed on Playback it shows more than a dozen irregularities lasting about a minute each (including an interesting excursion to The Netherlands!). The data in the track file shows a somewhat different story - breaks of around 5 minutes (eg 112658 to 113553, 113609 to 114054, 120619 to 121054). Any ideas on what is causing these dropouts? Unit is PAW Classic with latest update.
Trevor
https://playback.pilotaware.com/playback/?track=ccc38309
Trevor
https://playback.pilotaware.com/playback/?track=ccc38309
8
Technical Support / Re: Identification of type
« on: March 01, 2025, 10:18:21 am »
Thank you Peter, fully understood. I was alerted to this because I use EasyVFR rather than SkyDemon and it displays 'parachutes' as parachutes and I was surprised by the occasional 85kt parachute! Playback then confirmed the misidentity.
9
Technical Support / Re: Identification of type
« on: February 22, 2025, 10:28:22 am »
So back to my original query; is it a mis-setting on the target aircraft PAW (or other EC device) or is it something within the PAW system that provides the attribution. It not just on this one flight that I have noticed the problem.
10
Technical Support / Re: Identification of type
« on: February 21, 2025, 10:01:16 pm »
Thank you steveu, link is below, aircraft BNRP and BOJW as noted on earlier post at around 13:00.
https://playback.pilotaware.com/playback/?track=fb9f0bd7
https://playback.pilotaware.com/playback/?track=fb9f0bd7
11
Technical Support / Re: Identification of type
« on: February 04, 2025, 05:35:43 pm »
When you ask for a link to the track file, what do you mean by a link in this context? I show below an extract of the track file when two aircraft (BNRP and BOJW, both PA28s) are displaying on Playback as parachutes. They also displayed as such on my tablet running EasyVFR fed from my PAW Classic.
$PALOG,20241122,130032,RF,402AEE,PAW,UPL,51.26121,-1.47124,297,3333,51.22350,-1.56620,151,0
$GPGGA,130032,5115.672,N,00128.275,W,1,10,0.9,1016.1,M,47.2,M,,*65
$GPGSA,A,3,22,13,14,12,23,10,19,24,15,17,00,00,1.84,0.85,1.64*09
$GPRMC,130032,A,5115.672,N,00128.275,W,71.000,297,221124,,,A*4B
$PFLAA,0,4306,6474,-327,1,402A1D!G-BNRP,201,3.0,99,0.0,4E*6A
$PFLAA,0,-4188,-6612,-937,1,402AEE!G-BOJW,151,0.0,52,0.0,4E*0E
$PFLAA,0,-326,8623,-449,1,4080C8!-,47,0.0,101,-1.5,4E*66
$PFLAA,0,9344,1977,22,1,406552!GFELC,43,4.0,79,-1.5,8*03
$PALOG,20241122,130032,RF,402AEE,PAW,UPL,51.26121,-1.47124,297,3333,51.22350,-1.56620,151,0
$GPGGA,130032,5115.672,N,00128.275,W,1,10,0.9,1016.1,M,47.2,M,,*65
$GPGSA,A,3,22,13,14,12,23,10,19,24,15,17,00,00,1.84,0.85,1.64*09
$GPRMC,130032,A,5115.672,N,00128.275,W,71.000,297,221124,,,A*4B
$PFLAA,0,4306,6474,-327,1,402A1D!G-BNRP,201,3.0,99,0.0,4E*6A
$PFLAA,0,-4188,-6612,-937,1,402AEE!G-BOJW,151,0.0,52,0.0,4E*0E
$PFLAA,0,-326,8623,-449,1,4080C8!-,47,0.0,101,-1.5,4E*66
$PFLAA,0,9344,1977,22,1,406552!GFELC,43,4.0,79,-1.5,8*03
12
Technical Support / Identification of type
« on: February 01, 2025, 11:13:18 am »
I have noticed recently that on Playback quite a few traffic detected show Parachute as type, whereas the registration clearly shows this to be incorrect (eg an Ikarus and Pietenpol on my most recent flight). Is this a mis-setting on the aircraft concerned or is there another reason?
13
General Discussion / Re: Parachutes!
« on: November 29, 2024, 03:05:49 pm »
And for me, Classic and I still have to load the latest October software.
14
General Discussion / Re: Rosetta -> FX Upgrade
« on: November 28, 2024, 06:50:29 pm »
But note, I believe, that FX doesn't have a voice output compared with Rosetta/Classic.
15
General Discussion / Re: Parachutes!
« on: November 28, 2024, 06:48:09 pm »
Re my original post, it's not an EasyVFR matter, it's just that EVFR displays parachutes differently so I noticed it. PAW playback also shows the same identification as parachute for G-SARM (a C42) and G-BNRP and G-BOJW (PA28s). So my original question, more specifically: why are they being shown as parachutes on PAW?