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.


Messages - The Westmorland Flyer

Pages: 1 ... 6 7 [8]
106
General Discussion / Re: Transmit power and range
« on: October 12, 2015, 11:22:13 am »
One of the things that will make a vast difference to range, both for ADS-B and for PAW, but especially for the latter, is antenna location. For those of us flying all metal aircraft this has to be an important consideration. For example, the obvious place, on the instrument coaming will mean that signals will be profoundly attenuated below and behind the aircraft. This is not so much a problem for ADS-B, where we are only receiving but for PAW that means that a following aircraft won't see our transmissions and nor will we see his.

This got me thinking about where to put the antennas. From an engineering perspective it is quite easy to have the antennas wherever you want them, either on coaxial cable extension leads or by remoting the dongle with a USB extension cable. If we are flying a PtF aircraft then in principle we can put antennas wherever we like. More difficult for C of A aircraft unfortunately.

For ADS-B reception it is probably fair to say that most stuff will be above us, at least for the time being. As more GA aircraft get ADS-B capability this will change. ADS-B transmissions from the aircraft transponder are at considerably higher power, in the order of 200W peak power typically, so we can afford some losses. An antenna on the fuselage roof should be sufficient for good all round coverage and it might even be that one on the coaming will be adequate. As an aside, transponder antennas are always mounted on the aircraft underbelly because they are transmitting to and receiving from the ground-based radar. We, of course, are listening to the aircraft's interrogation replies rather than the ground radar.

For PAW transmission/reception things are more tricky. The transmit power is quite low so we cannot afford much attenuation. An antenna on the roof and another on the underbelly coupled to the ARF via a coaxial power splitter cable would do the trick but is awkward to engineer and probably somewhat OTT. It's definitely something we need to think about to gain maximum benefit from PAW.

Finally, I'd like to open up the Pandora's box of RF interoperability. We have an ADS-B receiver operating on 1090MHz and a PAW transmitting on 868MHz. It's a fair bet that the front end of the ADS-B dongle isn't the most selective of receivers and a nearby transmitter, albeit 200MHz away, might well swamp the ADS-B dongle's front end. The general rule of thumb here is to keep the antennas out of each other's near field, usually considered to be 2-3 wavelengths. At 1000MHz the wavelength is 30cm, so ideally the ADS-B and PAW antennas should be at least a metre apart to be on the safe side. It would be fairly easy to do some tests to see whether this is a real problem or not.

All this is a bit theoretical but it's based on decades of RF engineering work as well. As we gain real life experience we'll get a better handle on the performance issues and how to fix them. It would be interesting to hear other pilots' thoughts and experiences.

107
General Discussion / Re: USB Dongles fit and Overheating
« on: October 11, 2015, 05:57:25 pm »
I have the LogiLink WiFi dongle and that runs cool but the ADS-B dongle certainly does get uncomfortably hot. I found it was taking 400mA, so that's 2W of dissipated heat in a very small area. I am running the ADS-B dongle on a short USB extension lead and will probably continue to do that when the gear ends up in G-JONL.

108
General Discussion / Re: USB-GPS Working in PilotAware
« on: October 11, 2015, 05:52:14 pm »
Yes the app is to get the GPS info from the tablet/phone over to PAW which then uses it and passes info back to the tablet for SkyDemon etc.
Thanks Ian. Makes perfect sense now and explains your earlier point about going for the easy life. It makes attaching the GPS to the RPi by far the best solution. That's what I'll do!

109
General Discussion / Re: USB-GPS Working in PilotAware
« on: October 11, 2015, 09:05:10 am »
Collisionaware just takes the GPS location and passes it to the RPi (as far as I can tell)
Yes, that seems to make sense now that I've drawn a couple of system diagrams. The name confused me, implying that it did rather more. On that basis it's pretty clear that the best solution is to have the GPS plugged directly into the RPi and then engineer a high level of power integrity for the RPi in the cockpit. Fewer interfaces to set up/go wrong. Many thanks.

110
General Discussion / Re: USB-GPS Working in PilotAware
« on: October 10, 2015, 08:48:13 pm »
Hi Ian,

That's certainly one option to explore although I would want to engineer high reliability of the power supply to the RPi before trusting a key navigation facility to it.

In that configuration, how do the GPS position data get to the iPad/SD? Obviously over the WiFi connection but does it go via CollisionAware or does it have its own application protocol stack? I'm guessing I still need to run CollisionAware to get the traffic into SD? In short, I don't really understand what CollisionAware does!

111
General Discussion / Re: USB-GPS Working in PilotAware
« on: October 10, 2015, 06:38:25 pm »
I'm managing to confuse myself over what bits perform what function. In my config I have XGPS150 bluetooth GPS which in normal operation talks to the iPad running SD. The iPad is the type that does not have built in GPS. All that works fine and has done for years.

In this case, do the GPS data get sent from the iPad to PAW via the CollisionAware interface? What about the traffic data? I set a FLARM key 6000 so does that mean some other session is being established across the WiFi link? I'm trying to understand what data go where and how all these interfaces interact. Is there some sort of system diagram that shows all this stuff?

I'm also wondering whether to get a WAAS GPS to fit onto PAW and use that instead of (as well as?) the XGPS150. My concern is that it seems to be a bit of a palava getting all these interfaces running and my pre-flight checks are complicated enough already! If I understood how it all hangs together then I'd feel a lot more competent getting and keeping the system running in flight.

Thanks for any insight!

112
General Discussion / DVB dongle running very hot
« on: October 10, 2015, 12:42:30 am »
I got the recommended DVB dongle today and it is seeing the occasional ADS-B aircraft, although they don't show for long on the SD display, which is perplexing. The antenna is indoors though, so perhaps signal strength is too low.

My real concern right now is just how hot the dongle runs. After 30 minutes or so the dongle's USB socket on the RPi is very hot and if I unplug the dongle its USB plug is almost too hot to touch! That seems wrong - it must be taking a lot of current to get that hot. Perhaps I have a duff dongle?

Edit: With more traffic today I'm seeing plenty of ADS-B stuff at Flight Level nose bleed, so the dongle is working fine. But it's still getting very hot. Is that normal?

Edit 2: I measured the current draw and it's around 400mA, so the dongle is sinking 2W. No wonder it's getting a bit warm! Some Googling reveals that this is a common problem with this chip set. Not sure how well it will stand up to sitting in the sun on my instrument coaming.

113
General Discussion / Re: Hex / Reg for renters
« on: October 08, 2015, 11:11:41 pm »
ICAO code to callsign conversion for 3PI data  is a very good idea, analogous the the code/callsign conversion system used at control centres to convert mode-A squawk codes to callsigns. 0X406178 means nothing to anyone, but G-JONL does, to the cognoscenti.

Provided there is space on the SD card and a way of getting the data into the RPi then I think a crowd-sourcing approach to building the database would work. At my airport there are perhaps 50 aircraft that might be interested in PAW over time. A few of those would also be ADS-B equipped but not many. It would be an hour or so's work to manually interrogate G-INFO and make a CSV or whatever of ICAO codes and callsigns. I'd do Carlisle and if everyone else did the same for their airports we'd be most of the way there I reckon.

I'm a bit new to all this and still building my first kit, so I don't know how the ICAO code is used/displayed in PAW 3PI ATM. If I'm taking rubbish I hope someone will put me right!

John.

Pages: 1 ... 6 7 [8]