Version 20190418 and GS-OGN PAW Flag Missing

[Winged_Jaguar]

Hi Peter,
I feed Flightradar24 (EGUB13) and the upload stats to that reveal there was about a 15 minute internet break on Friday night at around 1am (presumably BTInternet doing some maintenance/update) that being the only break during the entire week. I'll continue to check whether any subsequent internet drop-outs (which are rare) correlate to the OGN-R/PAW disconnects.
Best regards
Chris

[zack_ster]

Hi Lee,

I seem to be having the same issues as Chris. The symptoms are as follows:

1) Neither my PA Classic or a friend's PA Rosetta show the GS-OGN flag in the PA radar screen when powered up in the garden next to my PWSHIREN ground station. The flag is not present when flying round the house either. Very occasionally, the flag will pop up for a few minutes and then disappears. While it is up, upload of FLARM traffic does occur and can be seen in Skydemon. The instances of the flag being present are tiny and seemingly random.

2) When the PA is powered up in the garden, the home screen of the ground station ALWAYS shows the unit as connected (see 401FF5) in the image below) despite the PA traffic screen showing no G\STN in the traffic screen and no GS-OGN flag.

3) I have changed every single component in the system part by part, but the problem is still present. Every unit is running the latest software.

Any help you can give would be much appreciated!

Rgds,

Zak

[Admin]

Hi Zack

OK, something strange is going on here, and I am not sure what the correct behavior should be.

It appears you have Flarm & PilotAware with the ID 401FF5, as can be seen here, this is the remote logging I capture

PWSHIREN,1557589623,2927,POS,401FF5,7850,N,-2864,E,594,V,0x0040,T,FLM,ET
PWSHIREN,1557589623,2928,POS,401FF5,7730,N,-2631,E,601,V,0x0050,T,PAW,ET
PWSHIREN,1557589625,2930,POS,401FF5,7694,N,-2562,E,601,V,0x0050,T,PAW,ET
PWSHIREN,1557589626,2931,POS,401FF5,7785,N,-2731,E,598,V,0x0040,T,FLM,ET

So the intention is to upload FLARM (and MLAT) to PilotAware, whereas in this case 401FF5 is identified as already being FLARM, in which case - do not upload.

maybe this needs a rethink so that having FLARM does not exclude FLARM uplink
this does not explain what happens when at home - if you are ONLY running PilotAware with 401FF5

Finally the OGN-R should still be visible, can you send me a track file from your PilotAware to analyse for what it is receiving ?
lee.moore@pilotaware.com

Thx
Lee

[zack_ster]

Hi Lee,

Sorry for the delay in replying, I have been away for work.

You are right (of course!), the aircraft is fitted with a FLARM unit as I fly from a gliding club field. At home, when running PilotAware in the garden no FLARM was connected.

I don't have a recent in-flight track log to send as I re-installed my PilotAware software recently. I'll take the aircraft out this weekend, fly it over my ground station and forward you the log. In the meantime, I'll send you a log from the garden test where we have no OGN-R flag.

Thanks very much for looking at this,



Zak

[Winged_Jaguar]

Hi Lee

The recent builds of OGN-R have been 100% stable with the connection to the PAW ground station being unbroken and the MLAT data being continuously received. The OGN-R is running with two SDR's and a 2.5A Raspi power supply and no throttling has been observed that I can see. The service always reconnects after the periodic background upgrades. Looking very good.

Many thanks
Chris