Re: [Flightgear-devel] GPS/FMS/route-manager changes
On Monday 08 December 2008 21:59:53 I wrote: Can't tell whether this is related, but I just noticed a problem with the b1900d's ILS localizer. I tried a little circuit: starting off at EHAM park position B01, taxied to runway 36L, made a 90 deg right, for about a minute, then a 180 right, until I hit the northsea coast, and then made a left to heading 220, approx, following the coast. Over airport Valkenburg (EHVB), I should have intercepted the ILS localizer for EHAM runway 06 (110.55, tuned on radio 1). But this didn't happen. Glideslope was okay. Oh, never mind. I think I figured out what I did wrong. I think I left the VOR1 being slaved to the GPS instead of the NAV1 radio. I retried this pattern again, and everything worked. Cheers, Durk -- SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] GPS/FMS/route-manager changes
I'm planning various enhancements to the GPS and route manager code in the next few weeks and months, and would appreciate any feedback or criticism people might have, especially from people using the code in ways I might not have expected. In summary, I'm planning to make the route-manager more 'abstract', i.e remove the GPS-like functions it currently has (time to next waypoint), etc. At the same time I'll make the GPS a mandatory instrument, and change the GPS code to use the route manager waypoints. This should make the route-manager and GPS code usable in far more aircraft to drive a CDI/HSI gauge. I'm going to update the route-manger to have a 'current waypoint', and no longer pop waypoints once they are reached - instead the current waypoint will be incremented. This will enable the route-manager to drive the leg/flight-plan mode of the GPS more easily, and also permit me to show the active route on my work-in-progress NAV display. Once these basics are done I will extend the GPS with a Nasal interface and various standard things it's currently lacking - closest VOR tracking, and proper 'direct to' and 'nearest' modes. Once the above is done I plan to deprecate all of the existing DCLGPS code, and re-create the KLN89b as a generic 3D instrument using Nasal. I'm happy to work with anyone to create other GPS units - hopefully they will all be doable with a Nasal layer on top of the generic GPS code, and the Nasal interface can be extended as necessary to make this work. Assuming all the above is done, the next step will be adding even more functions to enable a real FMS to be created, again in Nasal with support functions in C++. I would appreciate help on the instrument side - I know Syd has created parts of the KLN90 for the B1900, and I'll keep that working and hopefully enhance it in parallel with the KLN89B work. The two seem to share an awful lot of functionality, so some Nasal reuse is probably possible as well. I've created a wiki page to track the things I'm currently working on: http://wiki.flightgear.org/index.php/Plan-zakalawe Regards, James -- SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] GPS/FMS/route-manager changes
Hi James, On Monday 08 December 2008 11:54:15 James Turner wrote: I would appreciate help on the instrument side - I know Syd has created parts of the KLN90 for the B1900, and I'll keep that working and hopefully enhance it in parallel with the KLN89B work. The two seem to share an awful lot of functionality, so some Nasal reuse is probably possible as well. I've created a wiki page to track the things I'm currently working on: Can't tell whether this is related, but I just noticed a problem with the b1900d's ILS localizer. I tried a little circuit: starting off at EHAM park position B01, taxied to runway 36L, made a 90 deg right, for about a minute, then a 180 right, until I hit the northsea coast, and then made a left to heading 220, approx, following the coast. Over airport Valkenburg (EHVB), I should have intercepted the ILS localizer for EHAM runway 06 (110.55, tuned on radio 1). But this didn't happen. Glideslope was okay. Cheers, Durk -- SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
