PilotAware
British Forum => General Discussion => Topic started by: the_top_pilot on August 24, 2016, 05:03:08 pm
-
Today our testing started for real.
So far loving the results. We would like to see more PAW's out there so get buying and building.
The Mode C and S are important to us and are the main subject of our testing. I have enclosed an image of my PAW placed on to our mission rack in a PA31 reg BPYR.
You may note that I to have gone for one of the recommended Maplin Hammond Cases. I have removed the end panel and have replaced it with a 3mm hole mesh to let air circulate. You can now see the lights on the Pi2 and the Bridge unit through the mesh.(http://)
With the Yellow antenna I made using a piece of wire and a right angle SMA was indicating in the traffic window that we were picking up in excess of 170 sources at a range of up to 165kms.
The one PAW we did see had a hex code of 405091 at a range of 16.1km
Steve
-
Hi Steve
Very interested to know how you are getting on with the new Mode-C functionality ?
Especially how the filtering is managing to ignore your own transponder.
Thx
Lee
-
Lee,
I am continuing with the testing. Interestingly in either of the 2 mode C set ups I was not seeing our aircraft but were being warned of other mode C traffic that we were visual with or had information by the traffic service we were receiving. Today we have a 5 hour plus flight where Pilotaware will be running again.
I will keep you updated.
Steve
-
Hi Steve,
I know its always busy inflight, but the check would be to go to the web traffic page and see if there is a reference to SELF.
This would indicate that your own transponder is detected and ignored.
This is what I have spent quite a lot of time trying to perfect, to stop false reporting.
Thx
Lee
-
Lee,
I took screen shots of the traffic page yesterday, looking back I do not see the word SELF. I will look again today.
We are full ADSB equipped and I had put in the hex code to Pilotaware.
Steve
-
I'm hopefully flying today so I'll see what happens.
-
My flight is delayed till Saturday
-
Lee,
I took screen shots of the traffic page yesterday, looking back I do not see the word SELF. I will look again today.
We are full ADSB equipped and I had put in the hex code to Pilotaware.
Steve
Steve,
As you are ADSB out equipped (presumably via a Mode S Transponder) you should ideally be running Mode-C/S Select on the 'Mode-CS(Beta)' setting as you do not need the Mode-C filter. In this setting your Mode-S and ADSB are both filtered by your Hex ID. This means the 'SELF' label will not display in the traffic table, but your aircraft should appear at or near the top of the table in the 'ADSB' logs.
Regards
Peter
Mode S Development Tester
-
Hi Peter
Is that true, if you have a mode s transponder, it does not respond to a mode a or c interrogation ?
My understanding was that these responses are independent of each other
Could you confirm with your trig contacts ?
Thx
Lee
-
Hi Lee,
That's certainly how it has worked with me using the engineering software, though I might be wrong. I will speak to trig in the morning.
Regards
Peter
Postscript Having spoken to Trig, the answer to Lee's question is that my TT21 does 'respond' to Mode 'A' or 'C' interrogations as well as Mode 'S' ones, but the response is controlled by the pulses within the specific interrogations. In any case I do not get 'SELF' appearing in the traffic table (though I am as I say still flying with the 'Engineering' Test software not the latest Beta release).
-
Some observations from my flight yesterday.
With the PAW set with the aircrafts hex code and mode C/S filter.
In an area where there were no other aircraft in the valleys of Scotland if we decended of climbed with gusto a mode C warning was given?
Self was only displayed in traffic window a very few times during a 6.5 hour flight.
Otherwise all seemed to work perfectly.
I will report more soon.
-
In an area where there were no other aircraft in the valleys of Scotland if we decended of climbed with gusto a mode C warning was given?
Thats interesting 🤔
Part of the filtering is comparing the mode c alt, to the paw baro sensor.
As you say rapid ascent/descent could indeed fool the filter to display your own transponder due to possible latencies
Did you note the relative altitude reported, or the audio warning ?
Thx
Lee
-
Thankfully my aircraft doesn't know the meaning of gusto :-[
-
I don't know Ian, mine was getting bounced up and down quickly enough yesterday on our trip back through the weather front from Sherburn to East Fortune. Didn't see Steve though - mind you I didn't see much at all apart from rain and clouds ??? Roll on Summer 8)
Peter
-
Lee,
Sadly I only made occasional looks at the SkyDemon screen because I had to work..... I did not have audio connected on this flight
I did note at the end of the flight I had received 15 PAW contacts over the period between 09:30 local and 18:00 local.
I will conduct further tests this coming week.
Steve
-
WX Permitting another 7.5Hr trip to Scotland on Wednesday the 7th. Routing SAPCO, TRENT, POLEHILL, TALLA Then off into the highlands ending up in Oban for fuel and Lunch.
If anyone has there PAW switched on I will review the track list when I get back and report on what I have seen.
Steve
-
I have a base station running close to Poulton VRP (Blackpool)
May just be to far to the west of you track after Pol. On
your way north.
-
WX Poor at target area. will retry 08/09/2016
-
4hr 45min flight on the 8th. Great ADSB results. I will mention that when we climb or decend we get a mode 'C' target warning red ring and audio alert. This does cause a bit of a worry as we have a lookout, start our action then the warning sounds. Is there some clever trick were we can suppress this alert? We started our decent out of the airway at flt level 10.
Steve
-
what is the rate of ascent/descent.
I am guessing we are seeing either the on board baro, or the transponder altitude encoder
slower to stabilise
-
Hi Steve
I have been thinking on this and I think I have a solution.
The issue is that ModeC samples are retained for 10 seconds, which is fine
BUT, if we have a filtered match, that sample should NOT be retained.
What you are seeing is your own ModeC from a higher/lower alttude.
So I think we can handle this.
Steve will you be able to take an engineering release to try - this is much easier now It can be loaded from a memory stick
Thx
Lee
-
Steve,
Just a thought to add to the mix.... is your aircraft pressurised? This would presumably have an effect on the reaction time of the PAW Baro sensor. Just a thought.
Nice meeting up with you on Monday, sorry I had to rush off. Might have been better staying until the Tuesday as I ran out of daylight (and almost out of fuel) so had to spend the night at Eshott anyway.
Regards
Peter
-
Great to meet up to. I did follow you on flightradar 24 and saw you stop in the evening.
Ref our aircraft, its non pressurised and full of holes.
Steve