Dave Perry writes:
> Actually, there is a small moving map. The SL60 is also a comm radio.
> I have the manual in pdf form so I could send that to you. I can get
> the close-up photo also.
Thanks. I've got a pdf manual off the web (1.3Meg), but I can't find any reference to a moving map. There is a rudimentary CDI scale shown with a little airplane as the to/from indicator. Perhaps you could send your's anyway in case it's a later revision.
> I have not used the gps in fgfs.
Check out the KLN89B with:
$ fgfs --aircraft=c172p-2dpanel --geometry=1024x768
This is a panel-click only instrument - like the KAP140 it's not connected to the menu dialog.
>Is our database up to doing this well?
Well, it really depends on what you call 'well'. I think we can do any of the earlyish generation of aviation GPS units to an acceptable standard - stuff like the KLN89/90, the Apollo GX50/55/60/65, probably others (IIMorrow ?). We don't have all the data, but fundamentally we have worldwide airports, VOR, NDB, INT, SUA and comm frequencies available, although some of the coverage is patchy outside of the US. Missing is town, state and country information (state and country might be doable en-mass) but that isn't really *that* important. The other thing I've never found is a computer-parsable database of non-precision approaches - all the charts are readily available in the US but I've not found anything compiled as a file. I guess a tutorial to the user on how to enter their favourite approach from a chart into FlightGear's database would have to suffice.
Currently some of the access into FG's data needs sorting - search by range functions are not currently available for most of the data-types, which is why the KLN89 moving map currently only displays the active flightplan and not surrounding airports and navaids. Another problem with the world-wide data is that we get too many dupes compared to a typical americas-database, particularly with NDB and VOR identifiers.
However, the later generation of GPS units do go beyond the data we currently have available in the sim, since the moving maps display a large amount of geodata in addition to the aerodata. This is the main thing that puts me off trying one of the more impressive units such as the KLN94, or the Garmin 400 or 500 series units - I just can't conceive the geodata part of it being anything other then an extremely tedious slog to get working well. The data is certainly available - we use it as input to TerraGear in the scenery generation stage, but since I mainly just wanted to be able to fly GPS IFR approaches it just didn't seem like a clever plan.
Syd has used a very clever trick for his KLN90 on the b1900d, which is that he's made up a 2D panel containing only the gps, which is then made visible with the normal 2d panel (shift P ?) shortcut-key. That makes input and reading of such a complex text-based instrument a lot easier than on the 3D panel. I'm hoping to get something like that working with a fully approach-capable gps on one of the 3D models at some point.
Cheers - Dave