Messages

2326

General Discussion / Re: G-CEAR

« on: July 24, 2016, 10:12:15 am »

Ian,

If PAW is configured with no 'Reg' in the 'Flight ID' box, it will just transmit the auto generated (or manually entered) HEX instead. I take it that is what has happened here and that you looked up the Reg on G-Info from the displayed HEX?

Having dealt with a few posts of this nature recently, I'm starting to get a bit concerned that some users are very lax about correctly programming transmitting equipment in their aircraft. (See Brinzlee's recent posts in the Ground Station thread). OK, we are using a 'licence free' frequency, but we still need to 'play by the rules' if we don't want to attract the potentially unwelcome attention of Offcom and the CAA. Maybe the 'Quick Start' sheet needs to stress a bit stronger the importance of correct equipment programming before use and not transmitting false information (though in this case of course the information may not be 'false' - just 'missing').

Regards

Peter

2327

General Discussion / Re: Ground Station

« on: July 23, 2016, 11:08:35 pm »

Hi Brinz,

4A276F isn't the right Hex code for G-NULA either.... and if as per G-INFO the aircraft is a CT2K microlight, I don't think the CAA would be amused at it squittering ADSB with the wrong ICAO code and a SDA level of 3. If you know the guy, perhaps a discrete word about his transponder / ADSB and PAW settings might be appreciated. Unless of course there is something else very strange going on.

Regards

Peter

2328

General Discussion / Re: Pilot Aware returned

« on: July 22, 2016, 11:06:21 pm »

Hi Bobby,

I'm really sorry to hear that you have given up on your PAW and decided to return it for a refund. I have also had personal experience of the frustration of systems which don't seem to work as expected, so can appreciate your position. Having been personally involved in your support in the early days, I still feel that this has been more an issue of lack of suitably equipped 'target aircraft' than any fault with PilotAware. Having used it extensively over the past 9 months or so, I have had sufficient close call alerts from GA Mode S and ADSB aircraft to be in no doubt whatsoever as to PilotAware's effectiveness as an electronic conspicuity aid. Add to that the benefit in being able to track CAT ADSB in close proximity on approach to Edinburgh or during Zone transits, and also colleagues during flyouts and its effectiveness IMHO is beyond doubt.

I however accept your decision that at this stage it is not for you. Perhaps you may elect to rejoin us at a later stage when more aircraft come to recognise the benefits of electronic conspicuity and fit any of the systems which PilotAware can now 'see and display'. Believe me, there is currently still nothing better available at 5 times the price! I have tried most.

Regards

Peter

2329

General Discussion / Re: PAW at Top Farm Cambridgeshire.

« on: July 20, 2016, 09:55:07 am »

Hi Brian,

Looks like the owner must have changed 'Group-ID' away from PAWGRP, which would make the hash marks disappear as he/she was now no longer using the same group ID as yourself. My guess is that they have mistakenly put their 'aircraft ID' (Reg) in the 'Group ID' slot or just not entered their reg at all. With no entry in the Flight ID slot, PAW will transmit its 'Hex' instead - which is what you were seeing later.

Regards

Peter

2330

Technical Support / Re: EasyVFR connection.

« on: July 18, 2016, 11:28:21 pm »

According to Chris (Moffrestorer) - see this thread: -

http://forum.pilotaware.com/index.php/topic,550.msg6945.html#msg6945

....the correct pin for EasyVFR is now 6002. I'm not an EasyVFR user, but have just checked the Changelog in 20160708 which seems to bear this out and says 6001 is the pin for Runway HD.

Regards

Peter

2331

Technical Support / Re: await radio startup

« on: July 18, 2016, 02:10:40 pm »

Hopefully it will sort the problem. If not, try to take a screen grab, initially of the home screen, and add it to your post so we can see what is going on. Take screen grabs of the Configure and Logging screens while you're at it. They might also prove useful if it still refuses to fire up properly.

Regards

Peter

2332

Technical Support / Re: await radio startup

« on: July 18, 2016, 12:17:58 am »

Take it you are using a standard kit with the correct power cable and a power supply capable of supplying 2 Amps?

The other most likely issue is not having a good GPS fix. This is critical and doesn't happen at first boot-up unless your GPS is out in the clear with a good view of the sky to the south, so it can work out where it is. Until it gets a good 'fix' the Bridge won't start transmitting as it doesn't have the positional data it needs to do so.

If you haven't done so, give it another try outside and be patient - it can take 20 to 30 minutes for everything to get going the first time out.

Regards

Peter

2333

General Discussion / Re: PilotAware Get Together

« on: July 18, 2016, 12:12:18 am »

Sounds like a plan to me Keith

Regards

Peter

2334

Technical Support / Re: First ground tests - OK except all voce messages say traffic is at my level !!!!

« on: July 18, 2016, 12:10:16 am »

Stu,

In the case of the ADSB reports, the aircraft are described as 'Level', 'Above' or 'Below', simply to direct your visual scan to help locate the inbound aircraft. In this context an aircraft described as level will be at an altitude which brings it within +/- 10 degrees of your own level in the vertical plane, which to the human eye will appear to be at roughly the same level as yourself. Of course, the further away it is from you, the greater the vertical separation which will still report as 'level'. Remember, the whole purpose of the system is to bring to your attention the presence of other aircraft so you can see and avoid them.

Mode S altitude is derived from the other aircraft's transmission and is compared to your current altitude as stored within your PAW. The audio alert is limited to a warning based on the degree of risk presented based on the signal strength of the transmission from the approaching aircraft. The relative altitude is clearly displayed on screen to assist with visual lookout for the inbound contact, either 'level', above or below your present altitude. We have considered adding relative altitude to the mode S audio alert, but this has not yet been incorporated.

Hope this helps

Regards

Peter
Mode S Development Tester

2335

General Discussion / Re: PilotAware Get Together

« on: July 15, 2016, 09:35:57 pm »

How about Sherburn Aero Club? Food Drinks, great atmosphere very much center of the UK too.

And I can make it on a single tank of fuel. Not sure what to do about this 'orrible weather though! Mind you I have done a fair bit of flying in the rain recently. 

Regards

Peter

2336

General Discussion / Re: Ground Station

« on: July 13, 2016, 11:17:53 pm »

Thanks Jeremy, just wondered.

Regards

Peter

2337

General Discussion / Re: Over Farm Fly-in

« on: July 13, 2016, 11:15:25 pm »

And so.... ...PAW proves its worth yet again, though not necessarily in a way we might have expected!

Nice to hear more of them are starting to turn up in the air.

Regards

Peter

2338

General Discussion / Re: Latest Update 20160708

« on: July 13, 2016, 11:10:05 pm »

ADSB usage. From the table I guess that only three aircraft
are ADSB equipped.

Am I correct?   

Eric,

At first sight, Keith is correct - the rest of your traffic screen entries 'appear' to be Mode S. The significant factor is normally the fact that containing no positional information PAW cannot display any DISTance from the contact aircraft to your PAW.

Whilst I have experienced lots of 'non-ADSB' CAT aircraft, including Dash-8s and other FlyBe aircraft in particular, I am very suspicious that so many 'CAT' aircraft - including Boeing 737s, 747s and 787s  at such high altitudes would not be fitted with ADSB out equipment.

If they were on the ground, knowing your proximity to Blackpool Airport, I would suspect that some of these - for example the bottom two - were Ground Transmissions from otherwise ADSB equipped aircraft (which appear on PAW in the same manner as if they were Mode S), but most of these are, as I say at high altitude.

I wonder if there is something else going on here. Perhaps Lee might be able to shed some light on this.

Regards

Peter

2339

General Discussion / Re: Ground Station

« on: July 13, 2016, 01:41:07 pm »

Hi JC,

Just saw a report of this on news. Just out of interest was it Mode S or ADSB?

Peter

2340

General Discussion / Re: Latest Update 20160708

« on: July 13, 2016, 11:00:59 am »

Hi Doc/ Tony / Ian,

If it was easy, we would have done it, believe me.

Yes, as Ian says, with an aircraft fitted with ADSB and Mode S, we get two sets of data, but Lee then filters out the Mode S using the 'hex' address, as the ADSB gives us exact positional data which are then presented to your nav system.

The problem arises with straight Mode S, which is used by a significant proportion of GA, as well as by a significant proportion of CAT instead of ADSB. Having no positional information (except altitude) we have to assess and present risk information based solely on the strength of the received signal. The problem is that signal is generated from a transponder the output of which can vary from about 70watts minimum at the antenna (e.g. Trig TT21 or similar) up to 500watts at the antenna for CAT. That's before we take into account significant variation between the fit of even the same transponder in individual aircraft, which can be considerable. The only reliable filter to differentiate between a close GA signal or a further out CAT one is the human eyeball I'm afraid.

Regards

Peter R
Mode S Development Tester