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 - Robski

Pages: 1 ... 4 5 [6]
76
General Discussion / Re: Spacing of antenna
« on: October 14, 2015, 03:09:05 pm »
See here for more detail than you probably want!

77
General Discussion / Re: Facebook
« on: October 14, 2015, 03:02:35 pm »
Faceache?

Ugh!

And what everybody else said!

78
General Discussion / Re: PilotAware Map
« on: October 13, 2015, 03:22:49 pm »
Put myself on at Sleap.

Awfully lonely over here, by the look of it.

I'll have to start persuading people to start building PAWs over this way, or start a production line for them!

79
General Discussion / Re: USB-GPS Working in PilotAware
« on: September 29, 2015, 05:18:09 pm »
Me again! The dim one!

Read this thread and I think I understand what's ocurring but...

Is an external GPS dongle recommended over collisionAware (for Android)? If so do we have a recommended device?

I ask as I'm ordering up bits to build my PA this afternoon...

80
General Discussion / Re: Altitude Accuracy
« on: September 29, 2015, 12:57:12 pm »
For those of us lucky to have our own Permit to Fly aircraft who can legitimately tinker with the aircraft systems...

Would putting the barometric board in a separate, sealed box that we then attach into the aircraft's static source be the proper solution?
With this in mind is there a maximum length for the lines between the barometer board in its 'sealed' box and the GPIO / Slice of Pi etc.

81
General Discussion / Why a Barometric Pressure Sensor?
« on: September 23, 2015, 03:31:08 pm »
Excuse my latest dimness, but...

There is a development of PilotAware to add a barometric pressure sensor.

I'm just wondering why?

For altitude purposes surely GPS can provide that.

Or is this for a gross error check against GPS?
Or to sense current atmospheric pressure to compare with GPS altitude to calculate a correction to allow transmission of altitude data at 1013Mb / hPa?
Or something I haven't thought of? (The most likely situation!)

Keep up the good work. I'll build one of these little beasties once my engine is installed and the plane flying again.

82
General Discussion / Re: Android
« on: September 22, 2015, 01:45:12 pm »
Does the work Lee is doing with adding a USB GPS to the RPi / PilotAware mean that PA will work 'directly' with SkyDemon on Android and not need CollisionAware?

Just making sure I understand the way things are evolving!

Having multiple connection options has to be a good thing, though.

83
General Discussion / Re: Android
« on: September 22, 2015, 01:35:36 pm »
There may be some issues with Android killing processes that are asleep. I don't have a thorough understanding of this at the moment.
Hi Chris.
You've probably moved beyond this now, but sounds like the CollisionAware needs to run its business end as a service rather than an app. That way the unload/reload aspects of the Android Lifecycle ought to no longer apply.
A very quick google turned up:
http://stackoverflow.com/questions/6177775/android-app-application-vs-android-app-service
but there should be lots more out there!

I came a cropper with the lifecycle when I did a bit of programming for android a couple of years ago, so I can sympathise. Fortunately I just needed to re-code to work within the application lifecycle rather than outside it, which CollisionAware probably needs to.

84
General Discussion / Re: ICAO Code
« on: September 22, 2015, 01:09:40 pm »
Understood!

85
General Discussion / ICAO Code
« on: September 03, 2015, 04:15:32 pm »
Hi Lee,

In a previous posting you suggest setting the the ICAO code as follows (abridged):
If you do not have a transponder, I suggest setting this to the last 6 digits of the WiFi name, I will automate this at some point in the future. So if the WiFi is:-
pilotaware-0123456789AB

set the ICAO to:-
6789AB
I guess this makes sense for people who will be using the PilotAware in a number of aircraft.

If one always flies the same aircraft, or the kit will be permanently located on one aircraft, then wouldn't it be more suitable to use the transponder code allocated to the aircraft?
Regardless of whether a mode S transponder has been fitted all G reg aircraft have a code allocated, including microlights and even scrapped aircraft. It can be found on G-INFO as:
ICAO 24 bit aircraft address:Binary: 0100_00_000_011_11_1111001100
Hex: 403FCC
Octal: 20037714

Presumably the Hex is the one to use!

Or am I missing something here? (A not uncommon occurrence)

Rob

86
General Discussion / Re: Question prompted by LAA Mag article
« on: September 03, 2015, 02:30:45 pm »
I understand now.

Thanks, Lee.

87
General Discussion / Re: Progress
« on: September 03, 2015, 02:27:09 pm »
Roll on the Android version of PilotAware !
Seconded!

Not that I'm complaining, Lee!

88
General Discussion / Question prompted by LAA Mag article
« on: September 03, 2015, 10:59:40 am »
Firstly, thanks for the work you are putting into this, Lee. I'm interested in building a PilotAware as my next project.

I am uncertain as to where PilotAware gets its current position GPS co-ordinates from.
For iThings mention is made of Garmin external GPS receivers, but what if one is using an iThing with internal GPS, or better yet, an Android tablet with internal GPS? (I'm specifically thinking of a Nexus 7 with SkyDemon here).

Sorry if this seems obvious - I may be just being dense!

89
General Discussion / Re: Questions
« on: September 03, 2015, 10:08:02 am »
Don't like connections in aircraft wiring if they can be dispensed with.

Why do people try to make things more difficult than they need to be?

In my experience when wiring, components etc. are soldered in an aircraft environment they become dramatically less reliable.
Proper connectors and/or crimps every time - as far as possible!

Soldering a PA together does rather limit the scope for future upgrades too!

Pages: 1 ... 4 5 [6]