Setting up your 6030/Compeo

First a bit of Myth Busting. The Brauniger and Flytec instruments are the same. They are a collaborative project. They are the same hardware and the same software.
for updates the same files are available at Flytec and brauniger

The 6030 and 6020 (Compeo and Competino) share many features, but the 6020 has fewer display fields available and doesn't have the pitot static ASI that is so good for hang gliders. Windmill ASIs do not work well enough for total energy to work correctly and misread more the faster you go.

Pressing the in flight buttons.
I recommend a small slit on the inside bend of the thumb on the glove. This enables you to get your thumb out and press the buttons, but when you grip the bar the slit closes and doesn't let the cold air in.
Getting the right arrow buttons in the middle of the touch pad can be the most difficult with thick gloves. I have seen people add lumps of hot melt glue to the middle of the pads!
White symbols are accessed with a short press, yellow ones with a long press. most of the ones useful in flight are short presses.
buttons[1].jpg

 

Often the audio down seems to vanish, so remember the short press bottom left to get it back.
Having been asked by angry pilots to switch off your sound at the briefing, you will then fly with no sound, 4 presses bottom right to get the sound back to maximum. You can set sound to get louder with speed, but its all too quiet, we need it maximum for our flying speeds. Its worth experimenting with foam round your helmet ears to cut down wind noise if you want to hear your audio speed to fly. Choose your helmet carefully, they are all designed for slow paragliding flight!

Airspace
A big advance in airspace capability came with software 3.34 and 3.35. now the instrument can store infinite amounts of airspace on the SD card, and you can pick a file for the area you are flying. That file can contain any number of airspace zones and it will read the nearest ones and display them on your map screen. It will give an audio alarm when you get near them, and flash information on the screen. This works in both horizontal and vertical directions.
In short, now we have what we always wanted for airspace, the whole uk map on screen as you fly and quick access to the altitude limits where you are, listing the nearest three airspace zones to you!
To set up you need a suitable airspace.faf file on your SD card with a path sd:\CTR\aispacefilename.faf
The is usually an updated openair file to use each month, see later for how to deal with that.

Go to the main menu, scroll to the bottom and one more, or scroll up to find the SD card menu ON A NEW PAGE
Use select CTR file to choose your airspace file. You can have airspace files stored for many different places, or choose a modified file with some special airspace on it for the day.

Set the airspace alarms on. Go to settings and CTR Alarm. Set them all to yes, unless you know a good reason to switch only some of the types on :)

Now on the flight map page (press middle bottom), you can see the airspace. Note instrument must acquire for 10 mins or more before the airspace will appear for the first time.

map with airspace.jpg
 

This screen will stay on until you press <page/ESC> again, but you have some basic vario/alti info along the bottom edge, and the vario keeps sounding.

To find out info about the airspace press the <i> button middle right. This will show info about the three nearest airspace's. This screen will revert to the flight screen after a few seconds. When the alarm goes off you will see this screen automatically for a few seconds. Unfortunately you don't then see your altimeter for a few seconds - so beware if you get an alarm climbing fast toward an airspace ceiling!

airspace info.jpg

 

At home I am under Davetry CTA, and I am quite close to Harpur Hill, and there is a 5500ft limit nearby too. When it calculates the altitudes it converts into and out of meters so there are some small errors, so you get 4498 rather than 4500 etc. These numbers will be right if you change your alti units to meters - you don't need to change the airspace.faf file to use alternative units.

It is also possible to set one of the data field to "altitude allowed" - note that this will not show the 10,000ft transponder limit in England and Wales or whatever the scots are allowing at the moment, not unless we make an extra national airspace zone base 10,000 msl…

Setting up a competition route.

You can save many routes, but you can only have one competition route.
You can convert any route into a competition route, but I prefer to edit the competition route directly.

As an example this is a task launching at my house (run down the drive and push out, mind the telephone exchange cables though!). The start is an 8km entry circle round Lose Hill (east of Mam Tor), then going to Lose Hill as a turnpoint, then to Stanage Launch, and a finish at the Anchor Pub at Tideswell road ends.

routefinish[1].jpgroute%20start[1].jpg

 

Insert each waypoint in the route in turn. by default they are set to 400m entry cylinders. Because we will have an entry start circle and then we will go to the turnpoint in the middle, the first turnpoint is entered twice. You can please yourself if you enter the launch or not. Its wont say S for the first one yet. Here I am setting the finish as a line. We will usually use a circle not a line.

Now we go back to the start. To make it into a start you press and hold the WP button. Yellow text means long press, white text a short press. Press enter to get to the settings and set the start radius to 8km (8000) and the time of the first start, the start increment time (20 mins) and how many starts there are (as set these would be 20.45, 21.05 and 21,25. Now write that somewhere where you can see it in case you get confused later and don't take the first start!

screen1[1].jpg

This is my "starting" flight screen. Pressing the right arrow will move between screens.
In the info strip at the bottom of the screen it should display the next place you are going (the start circle centre is LOSE). Lose is alternating with the time to the start. This number shows times greater than one hour.
On this screen I have:
CylArrival = time I will get to the start cylinder edge at current progress (its varying becuase I'm stopped). White on black means I am going to be late!
Start Race = How long it is until the next start, blank unless it is less than an hour (annoyingly). After the start time it will change to white on black. You will get a bleep when the start time happens, and another bleep when you cross the circle.
Dist Cyl = Some fields are annoyingly blank until you are flying…
Dist St Cyl = how far away the start is.
Pressing the up and down arrows will progress the route to the next waypoint. If you want to take a later start press the forward arrow once, and the backward arrow twice, then the time to start should go back to black on white and show countdown to the next start. It doesn't tell you when you run out of starts, it just wont switch to another one!

screen2[1].jpg
 

This is my on course screen. Here we have:
Dist Cyl = this will fill in with the distance to the waypoint cylinder. Its blank because I'm not flying. This could alternatively be Dist Wypt, and it would then fill in on the ground I think. I prefer the distance to the cylinder, so I will turn when it says zero. you have remember if you set this field for 400m, or zero! you will get a bleep when you enter the circle and the numbers will change.
FL = flight level altitude Got to have it somewhere!
Dist Goal** = the distance round all the turnpoints to goal.
Wind Speed and Ground speed.
XT error = perpendicular distance from the course line, -ve for left, +ve for right. This and dist to cyl I will use to report my position.
The arrow - there are two arrows, a black and a grey one, The Black one points to the current turnpoint, the grey one points to the next one. There will also be a little wind sock indicating the calculated wind direction.

Note how the little arrows are no longer in the info screen, now it wont jog up and down the route manually. To get the little arrows back press and hold the WP button to make then reappear, then you can manually change through the route. But after you started you shouldn't have to do it - if it didn't switch you didn't log the turnpoint! (unless you made a programming error).
screen3[1].jpg

 

This is my final glide screen.
Dist CTR = is just there for info. We'll come back to that under airspace.
Wind Spd = I want that for reference.
A BG Goal = Altitude above best glide to goal - this is what it reckons you will arrive at goal at if you get your speed exactly right. Useful as a guide to how much you need to climb before you glide. Factor in a healthy margin. Its not very reliable if you have another turnpoint to do before you get there.
L/D Goal = L/D to goal via all the turnpoints. Not optimised for the cylinder radius unless you use optimised route. ie if you have a turnpointt you will gain on this by the turnpoint radius, because it is thinking you have to glide to the middle of the cylinder.
L/D Ground = As long as this reads flatter than L/D goal you are making it, and A BG goal should be positive.

Optimized competition Route.
If you use this as an option it will correct the distances and calculate the arrow pointers based on the shortest route to the edges of the cylinders. This sounds great, as when there is a turnpoint near goal the cylinder radius distance is significant. However when you are close to the turnpont you must think in the expected flight path and aim appropriately. If you follow the arrow exactly as it points to the edge of the cylinder it jumps about when you are near, and makes it very easy to miss. Then you have to turn back and the same thing happens all over again. Leave this feature until you are sure what you are doing!

optimised%20route[1].jpg

 

If you simply follow the arrow using optimised route you are in effect aiming at a tiny point, should you miss it on the wrong side (the right in this diagram) the arrow seems to suddenly turn 180 degrees and you miss the turnpoint (path A). Unless you understand what's happening you can end up hunting about for the turnpoint! In this case you must aim a little left of the arrow (path B), and then you will get the turnpoint - but this is the opposite of what you would normally do with the std route operating. So there is a big danger using optimised route for the first time, until you understand how it works. Note how it is also essential with optimised route to know the plan of the route before hand, which way you are going to turn to follow the course line. With the normal route you can just blindly follow the arrow. Of course this might all seem simple to understand, until you are low and circling near the turnpoint and not necessarily travelling in the expected direction!
A way round this confusion is to set the screen to switch to map automatically when you are near the turnpoint and then navigate using the map. I have yet to try this.

Preparing the airspace files
The file format is openair.txt but by running it through openair2faf.exe it is checked for units and errors, and an alarm distance is set. See later for how to produce and update these files yourself - for now use this one - alarm distance is set to 100m (horizontal and vertical is the same)
The source airspace files are found the same place as the garmin ones http://soaringweb.org/Airspace/UK/
At the moment there is an error in openair2faf and it considers ALT altitudes to be meters. ALT needs to be replaced with MSL before you run the txt file through openair2faf.

I have prepared the spring 2014 openair files into a faf file that is corrected with ALT replaced by MSL. The difference to us is minimal, alt is the locally set altitude but we tend not to fly through massive pressure changes..
Flytec/Brauniger misinterpreted ALT to mean units were meters!

Gordon Rigg

AttachmentSize
Plain text icon uk060314.txt449.52 KB