Re: [Flightgear-devel] Autopilot broken, Eric maybe?
> I already took a look into several times, but if I would able to use the > Bravo-flightdirector as an example I wouldn't have said this. Syd's > flightdirector seems to dependant on other things ( not always other > simlated systems) so I wasn't able yet to use this. > > I guess a short explanation of the flight director nasal code is this: It is more or less an autopilot controller , to manage modes like armed , then capture points, and handle pilot button presses... The autopilot in passive mode IS acting as a flight director , since it goes through the motions , but doesn't output the results to the control surfaces .Those outputs can be used to animate V-bars. That nasal code probably could use a serious cleaning up , its been a learn as i go project ... Its also adapted from Curt's original flight director code , which I probably trashed trying to be helpful :) Cheers and Merry Christmas -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Autopilot broken, Eric maybe?
Hi, > Okay, that's a useful data point, I'll take a look at that > in the next few days (in between eating too much...). I > assume all interactions with the system are occurring > through the radios and autopilot *dialogs* (F12 and F11), > not the cockpit panel? The cockpitpanel isn't working fully right now, as not yet completed, but the dialogs and the autopilot.xml are untouched by me. > Do other autopilot modes work? Do the VNAV modes work, > aside from NAV1-GS hold? VNAV seems to work. Only ILS-Approaches aren't possible right now. > > > Take a look at Syd's scripts? The core flightdirector.nas > scripts are pretty clear, though as always I wish less > copying of files into each aircraft went on. I already took a look into several times, but if I would able to use the Bravo-flightdirector as an example I wouldn't have said this. Syd's flightdirector seems to dependant on other things ( not always other simlated systems) so I wasn't able yet to use this. >If you want help understanding what the scripts do, and how they are > structured, I'm happy to (try to) help. (Actually I think > the scripts could be simplified quite a bit, but Syd may > disagree - he knows better than me!) That's another big point of it - still don't understand quite right waht's the script is doing, how it is structured. > > The flight-drector issue is complicated because the generic > autopilot doesn't provide anything in this area. I have > briefly wondered about writing a C++ generic flight > director, but I don't think it's a good idea - people who > want an accurate flight-drector for a real aircraft will > find it much easier to write a specific one in Nasal (to go > with a custom autopilot) than try to work with a generic C++ > one, I think. But a generic flightdirector with comments written in nasal could help much more. Like the generic systems, autopilot.xml etc... > I'd also be happy to start collecting an 'autopilot > internals' wiki page, to collect information about this kind > of thing in a proper place, and to go alongside my existing > route-manager and GPS/FMS internals documents. > That is a good idea! Merry Christmas HHS __ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Autopilot broken, Eric maybe?
On 23 Dec 2009, at 11:42, Heiko Schulz wrote: > 737-300 (Using the autopilot.panel via F11)- in 19.1 the 737-300 was the > airliner with the best autopilot behavior recommended for ILS-approaches done > by ap. with my last built from 11/27/2009 the aircraft didn't responded > anymore on NAV1-Hold and GS. Okay, that's a useful data point, I'll take a look at that in the next few days (in between eating too much...). I assume all interactions with the system are occurring through the radios and autopilot *dialogs* (F12 and F11), not the cockpit panel? These are the kind of things that people don't mention, but make a big difference in testing. Do other autopilot modes work? Do the VNAV modes work, aside from NAV1-GS hold? > P.S.:I'm beware of that the actually 737-300 needs a own written > flightdirector like the Citation Bravo and other aircrafts from Syd has to be > real - but how to write one? Take a look at Syd's scripts? The core flightdirector.nas scripts are pretty clear, though as always I wish less copying of files into each aircraft went on. If you want help understanding what the scripts do, and how they are structured, I'm happy to (try to) help. (Actually I think the scripts could be simplified quite a bit, but Syd may disagree - he knows better than me!) The flight-drector issue is complicated because the generic autopilot doesn't provide anything in this area. I have briefly wondered about writing a C++ generic flight director, but I don't think it's a good idea - people who want an accurate flight-drector for a real aircraft will find it much easier to write a specific one in Nasal (to go with a custom autopilot) than try to work with a generic C++ one, I think. I'd also be happy to start collecting an 'autopilot internals' wiki page, to collect information about this kind of thing in a proper place, and to go alongside my existing route-manager and GPS/FMS internals documents. Regards, James -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Autopilot broken, Eric maybe?
Hi, > > With the aircraft I test with, that's what I see - the > C172, the Seneca, the B1900 and, to a lesser degree, the > 777-200 (though it has some other problems). I guess the > problem may be, that all of those aircraft have quite well > developed, non-generic autopilots. Unfortunately they are only few ones > > Aside from the GPS setting true-heading-hold when it > shouldn't, what problems are people seeing with heading-hold > and nav1-hold? > > Please let me know the specific aircraft, steps to > reproduce, expected behaviour and actual behaviour. I will > assume people are testing with latest data/ and FG/SG > sources. > > Regards, > James I can't use the latest data and sources, but just as compare and help: 737-300 (Using the autopilot.panel via F11)- in 19.1 the 737-300 was the airliner with the best autopilot behavior recommended for ILS-approaches done by ap. with my last built from 11/27/2009 the aircraft didn't responded anymore on NAV1-Hold and GS. Cheers HHS P.S.:I'm beware of that the actually 737-300 needs a own written flightdirector like the Citation Bravo and other aircrafts from Syd has to be real - but how to write one? __ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Autopilot broken,
James Turner wrote: > Okay, so that's where the bug has come from, I need to fix the logic to only > drive this property when GPS 'leg' mode is active. > > Yes, and it works now. Thank you very much! Stewart -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Autopilot broken
Stuart Buchanan wrote: > The wing leveler and heading autopilot that are part of the KAP140 work > well for the c172p. However, using the generic autopilot instead is not > something that I would expect to work, so they should be disabled > for the c172p. Agreed. And the help keys removed from the help window. And [F11] disabled? > Effectively, you're using the wrong autopilot. Ah, that makes sense now. Thanks, Stewart -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Autopilot broken
S Andreason wrote: > >> configured autopilots like the senecaII, c172p, PA24-250. > >> > > Well yes, but I expected the default aircraft to work. > Since the manual and help windows give instructions on using Ctrl-A, > Ctrl-W, > Ctrl-H, etc, and F11 does open the autopilot settings, I would expect these > to work. >From the sounds of things, you're attempting to use the Generic Autopilot, GPS and Route Manager on the c172p. That won't work because the c172p has a KAP140 A/P, and no GPS has been integrated. So, I wouldn't expect the Route Manager or GPS to work at all. Just as the Autopilot->Autopilot Settings menu item is disabled for the c172p, so I think these keys should be disabled (and possibly any other aircraft that disable that menu item), or re-assigned to the equivalent KAP140 functions. I'll investigate how to do that, and also ensure that our documentation makes clear that aircraft may not implement the entire suite of Route-Manager/GPS/AP. Of course, once we have a C172 with a G1000 panel, then we'll have support for these goodies ;) > Should the old autopilot dialog be ripped out of the c172p? and have all > references to using the autopilot removed? > I don't think so. The wing leveler and simple heading autopilot had value. The wing leveler and heading autopilot that are part of the KAP140 work well for the c172p. However, using the generic autopilot instead is not something that I would expect to work, so they should be disabled for the c172p. Effectively, you're using the wrong autopilot. > Actually, flying the c172p (in yesterday's CVS) around in circles for > 10-15 minutes trying to get the heading to go on autopilot, even setting > the GPS destination, did not work for me. > If it isn't really broken, it sure looks like it. AFAIK the c172p does not contain any GPS, and certainly not one that's integrated with the KAP140 AP. > And if I can't figure it out, I doubt any first-time flyers will. The tutorials section of the manual describes how to use the KAP140 autopilot in some detail. http://www.flightgear.org/Docs/getstart/getstartch9.html#x15-1650009.3.1 -Stuart -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Autopilot broken, Eric maybe?
Heiko Schulz wrote: > Hi, > >> Hey, >> >> could we all agree it's not my fault? :) >> > Only if you will correct the airport name: > http://wiki.flightgear.org/index.php/File:Tu154Innsbruck.png - pretty flat > for LOWI ! :-P > Admittedly I already wondered about it :) But i never thought it would be Schiphol. Anyhow, the filename isn't changed but the corresponding text is. Erik -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Autopilot broken
I'll have to add also that I'm a bit confused by the recent changes (I'm sure I'll eventually figure it out) , but how is this new route manager dialog supposed to work ? I try the normal k...@35000 , and hit activate , and then I get my departure airport suddenly added to the list , which causes the aircraft to go back home again before contuing on to the destination Ive also had cases where takeoff is suddenly taken over by the autopilot , usually disasterous , but I haven't looked very closely at that one yet ...could be something Im doing wrong now... Any light shed on the new code behavior , changes , what we should and shouldn't be doing , would be really helpful. I dont like surprises , when they affect my work ;). Thanks -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Autopilot broken, Eric maybe?
Hi, > > Hey, > > could we all agree it's not my fault? :) > > Erik > Only if you will correct the airport name: http://wiki.flightgear.org/index.php/File:Tu154Innsbruck.png - pretty flat for LOWI ! :-P Cheers HHS __ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Autopilot broken, Eric maybe?
Erik Hofman wrote: > Hey, > > could we all agree it's not my fault? :) > > Sorry Erik, You are only guilty of submitting the most number of files in that 36 hour period. :) I guessed wrong. Stewart -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Autopilot broken, Eric maybe?
Hey, could we all agree it's not my fault? :) Erik -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Autopilot broken, Eric maybe?
James, this is what I've found too. Perhaps I don't understand the proper setup method, but I tend to clean it up as well. Sometimes I get a FL value, others times the point adds with a zero altitude. (or two dep. airport waypoints, one with each altitude) It may be a result of most times the route manager loads with the departure airport already listed. For the time being configure it to not load a depature airport on opening? Peter On Dec 21, 2009, at 1:51 PM, Curtis Olson wrote: > On Mon, Dec 21, 2009 at 12:43 PM, James Turner wrote: > It is not my intention, or expectation, that many aircraft should need to be > changed at all. Aircraft that used the old gps or route-manager directly will > need changes (eg, the 787, and Concorde INS code, but that's non-functional > anyway) but my *intention* was always that most aircraft, whether using the > generic autopilot, or a customised XML autopilot, would work exactly as > before. > > With the aircraft I test with, that's what I see - the C172, the Seneca, the > B1900 and, to a lesser degree, the 777-200 (though it has some other > problems). I guess the problem may be, that all of those aircraft have quite > well developed, non-generic autopilots. > > Aside from the GPS setting true-heading-hold when it shouldn't, what problems > are people seeing with heading-hold and nav1-hold? > > Please let me know the specific aircraft, steps to reproduce, expected > behaviour and actual behaviour. I will assume people are testing with latest > data/ and FG/SG sources. > > Hi James, > > The one aircraft I enjoy flying is the Alphajet ... that uses the generic > autopilot/route manager system. My one comment with the new route manager is > that I've had some variability in the results of building a route. Maybe I'm > not understanding the interface correctly, but sometimes my starting airport > gets added, even when I'm in the air. Sometimes it gets in there twice. > After creating a route, I always need to go in and manually clean up > extraneous stuff before I get what I hoped for. (Sorry for using the word > always, maybe I should say "I feel like" I always have to go fix the route > manually.) :-P > > Curt. > -- > Curtis Olson: http://baron.flightgear.org/~curt/ > -- > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Autopilot broken, Eric maybe?
On Mon, Dec 21, 2009 at 12:48 PM, James Turner wrote: > I thought I'd fixed that back at the start of October, soon after the > initial commit - Curt complained that h couldn't start a route 'in-air' so I > removed the need for departure/destination airports. > > Ah, I get it - you're specifying a departure airport, but then not > activating the route until airborne. > > Hmm. > > I'm not sure that's actually a bug. Activating a route starts a leg to the > first waypoint ... regardless of wether that's 'behind' you in the route or > anything. In real-life I'd activate the route, then select the enroute > waypoint I wanted to 'start' from, and 'DTO' on it, to head straight there - > that's exactly how I fly departures where ATC vector me, then clear me to a > SID waypoint. > > What do you think would be a sensible course of action, in the situation > you describe? Even if I choose not to add the departure airport for in-air > route activation, there's no guarantee that the first route waypoint is > where you actually want to be going. Conceptually, including the starting point in the route seems like it could always be problematic.The "airport location" is some random point on the airport grounds (probably the average of the center points of the runways.) Even if you haven't taken off yet, it would be possible in some circumstances to not fly close to the center of the airport on take off. Then you would get routed back to the starting point before you could continue on to the next way point. I think we are just getting "lucky" when we fly close enough to the center of the airport in most situations for most runways to satisfy the route manager and it clicks on to the next waypoint. The KSFO airport layout is very friendly in this regards, but other airports like DFW and DEN are more sprawling. Regards, Curt. -- Curtis Olson: http://baron.flightgear.org/~curt/ -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Autopilot broken
Hi James, >> There were major changes on the GPS and Route-Manager since August (3 Months >> ago already!) >> I had not noticed because I have not tried using the autopilot for many months. >> written flightdirector like Syds Aircrafts (Citation Bravo works perfect) or >> with own yes, Citation Bravo works for me too. >> configured autopilots like the senecaII, c172p, PA24-250. >> Well yes, but I expected the default aircraft to work. Since the manual and help windows give instructions on using Ctrl-A, Ctrl-W, Ctrl-H, etc, and F11 does open the autopilot settings, I would expect these to work. >> True-Heading can be used with the DTO-Mode in the GPS-menu in the Menubar. >> Ok, I figured out how to give a destination. > The issue / feature here is that the route-manager code has 'always' (for > years, at least) directly set /autopilot/settings/true-heading-deg based on > its internal route-following logic. Personally I don't think it's a great > feature, but people do use it (the route manager) in conjunction with the > generic autopilot dialog to quickly navigate between waypoints. When I broke > the feature by accident, it was noticed, and people asked for the feature > back. > > As far as I know, the old route-manager code behaved much the same as my code > does now - but it sounds as if you disagree? > I guess I do. In the past this property stayed nil until set by somebody wanting autopilot to navigate on a specific heading. Or yes, if route-manager gets Activated, then it did and does set true-heading-deg as you said. As long as route-manager was deactivated or had no waypoints set, it looked like the right place to tie in my buttons on the panel. > For the record, my perception is that entering a value in the generic > autopilot dialog for 'true heading' has never worked, because the value would > **always** be over-written by the route manager. > No, it is not overwritten when route-manager is disabled. And if it never worked, then how did the Ctrl-W, Ctrl-H ever work?? I still think something in this part is broken. > What *has* changed is that the value now actually comes from the GPS code, > not the route-manager. Both are equally 'generic' (just like the autopilot > itself), it was just simpler from a code design perspective to handle the > autopilot interaction in the GPS code, and keep the route-manager separated. > > Does this fit with what you're seeing? > > Yes. Without a destination, the gps code sets wild headings into true-heading-deg, and makes the old autopilot controls act broken and confusing. With a destination set, the GPS code works. Should the old autopilot dialog be ripped out of the c172p? and have all references to using the autopilot removed? I don't think so. The wing leveler and simple heading autopilot had value. Is there a way to set a steady heading without writing my own code, which I thought was discouraged "reinventing the wheel" :) Maybe I am supposed to study and borrow the flight director code or some part of it that makes smooth turns to a set heading? Actually, flying the c172p (in yesterday's CVS) around in circles for 10-15 minutes trying to get the heading to go on autopilot, even setting the GPS destination, did not work for me. If it isn't really broken, it sure looks like it. And if I can't figure it out, I doubt any first-time flyers will. Maybe the fix for half of this, is to Deactivate the New gps code when it has no destination set. Stewart -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Autopilot broken, Eric maybe?
On Mon, Dec 21, 2009 at 12:43 PM, James Turner wrote: > It is not my intention, or expectation, that many aircraft should need to > be changed at all. Aircraft that used the old gps or route-manager directly > will need changes (eg, the 787, and Concorde INS code, but that's > non-functional anyway) but my *intention* was always that most aircraft, > whether using the generic autopilot, or a customised XML autopilot, would > work exactly as before. > > With the aircraft I test with, that's what I see - the C172, the Seneca, > the B1900 and, to a lesser degree, the 777-200 (though it has some other > problems). I guess the problem may be, that all of those aircraft have quite > well developed, non-generic autopilots. > > Aside from the GPS setting true-heading-hold when it shouldn't, what > problems are people seeing with heading-hold and nav1-hold? > > Please let me know the specific aircraft, steps to reproduce, expected > behaviour and actual behaviour. I will assume people are testing with latest > data/ and FG/SG sources. > Hi James, The one aircraft I enjoy flying is the Alphajet ... that uses the generic autopilot/route manager system. My one comment with the new route manager is that I've had some variability in the results of building a route. Maybe I'm not understanding the interface correctly, but sometimes my starting airport gets added, even when I'm in the air. Sometimes it gets in there twice. After creating a route, I always need to go in and manually clean up extraneous stuff before I get what I hoped for. (Sorry for using the word always, maybe I should say "I feel like" I always have to go fix the route manually.) :-P Curt. -- Curtis Olson: http://baron.flightgear.org/~curt/ -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Autopilot broken, Eric maybe?
On 21 Dec 2009, at 18:10, Peter Brown wrote: > One note on using route manager - in a 12/13 CVS - if includes the departure > airport as a waypoint automatically. If you "activate" it on the ground it > will move past it on the takeoff roll and proceed to the next waypoint. If > you don't activate it until in the air it will circle back to the departure > airport as the first waypoint. I thought I'd fixed that back at the start of October, soon after the initial commit - Curt complained that h couldn't start a route 'in-air' so I removed the need for departure/destination airports. Ah, I get it - you're specifying a departure airport, but then not activating the route until airborne. Hmm. I'm not sure that's actually a bug. Activating a route starts a leg to the first waypoint ... regardless of wether that's 'behind' you in the route or anything. In real-life I'd activate the route, then select the enroute waypoint I wanted to 'start' from, and 'DTO' on it, to head straight there - that's exactly how I fly departures where ATC vector me, then clear me to a SID waypoint. What do you think would be a sensible course of action, in the situation you describe? Even if I choose not to add the departure airport for in-air route activation, there's no guarantee that the first route waypoint is where you actually want to be going. Regards, James -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Autopilot broken, Eric maybe?
On 21 Dec 2009, at 17:59, Heiko Schulz wrote: > It worked as long we didn't use the Route-manager. Like Curt already said, > with pending waypoints the values are overwritten, but only then. > That hasn't changed. Okay, so that's where the bug has come from, I need to fix the logic to only drive this property when GPS 'leg' mode is active. > Yep, but though a lot of aircrafts has to be fixed before release, or > otherwise we will really have a "debacle"! It is not my intention, or expectation, that many aircraft should need to be changed at all. Aircraft that used the old gps or route-manager directly will need changes (eg, the 787, and Concorde INS code, but that's non-functional anyway) but my *intention* was always that most aircraft, whether using the generic autopilot, or a customised XML autopilot, would work exactly as before. With the aircraft I test with, that's what I see - the C172, the Seneca, the B1900 and, to a lesser degree, the 777-200 (though it has some other problems). I guess the problem may be, that all of those aircraft have quite well developed, non-generic autopilots. Aside from the GPS setting true-heading-hold when it shouldn't, what problems are people seeing with heading-hold and nav1-hold? Please let me know the specific aircraft, steps to reproduce, expected behaviour and actual behaviour. I will assume people are testing with latest data/ and FG/SG sources. Regards, James -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Autopilot broken, Eric maybe?
One note on using route manager - in a 12/13 CVS - if includes the departure airport as a waypoint automatically. If you "activate" it on the ground it will move past it on the takeoff roll and proceed to the next waypoint. If you don't activate it until in the air it will circle back to the departure airport as the first waypoint. Peter On Dec 21, 2009, at 12:17 PM, James Turner wrote: > > On 21 Dec 2009, at 16:33, Heiko Schulz wrote: > >> There were major changes on the GPS and Route-Manager since August (3 Months >> ago already!) >> >> So this has affected the the use of the autopilot as well. >> All aircrafts using the generic Autopilot-panel are affected, but not those >> with an own written flightdirector like Syds Aircrafts (Citation Bravo works >> perfect) or with own configured autopilots like the senecaII, c172p, >> PA24-250. > >> True-Heading can be used with the DTO-Mode in the GPS-menu in the Menubar. >> >> I think James can tell more! > > The issue / feature here is that the route-manager code has 'always' (for > years, at least) directly set /autopilot/settings/true-heading-deg based on > its internal route-following logic. Personally I don't think it's a great > feature, but people do use it (the route manager) in conjunction with the > generic autopilot dialog to quickly navigate between waypoints. When I broke > the feature by accident, it was noticed, and people asked for the feature > back. > > As far as I know, the old route-manager code behaved much the same as my code > does now - but it sounds as if you disagree? > > For the record, my perception is that entering a value in the generic > autopilot dialog for 'true heading' has never worked, because the value would > **always** be over-written by the route manager. > > What *has* changed is that the value now actually comes from the GPS code, > not the route-manager. Both are equally 'generic' (just like the autopilot > itself), it was just simpler from a code design perspective to handle the > autopilot interaction in the GPS code, and keep the route-manager separated. > > Does this fit with what you're seeing? > > Regards, > James > > -- > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Autopilot broken, Eric maybe?
Hi, > Heiko Schulz wrote: > > Hi, > > > > There were major changes on the GPS and Route-Manager > since August (3 Months ago already!) > > > > So this has affected the the use of the autopilot as > well. > > All aircrafts using the generic Autopilot-panel are > affected, but not those with an own written flightdirector > like Syds Aircrafts (Citation Bravo works perfect) or with > own configured autopilots like the senecaII, c172p, > PA24-250. > > > Citation Bravo does not work :-( > > True Heading goes in circles > > pete > Really with current CVS? It is the only aircraft I can use for realistic approaches, SIDs and STARs, Route-flying ... CVS 11/27/2009 Cheers HHS __ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Autopilot broken, Eric maybe?
Hi James, > > As far as I know, the old route-manager code behaved much > the same as my code does now - but it sounds as if you > disagree? Yep, and Torsten already decribed it well: >>The GPS code sets the property /autopilot/settings/true-heading-deg if >>/instrumentation/gps/config/drive-autopilot is true (which is true by >>default). >>I don't know much about the details of the new gps code from James >>Turner, >>maybe he could chime in for some explanation... On the 737 and other aircraft (except those I mentioned in my previous posting) I have to use the DTO-Mode. Otherwise it won't fly to the next waypoint. So several Aircrafts needs fixing. The other thing, but I already mentioned it in the IRC-Chat, is that NAV1-Heading-hold and NAV1-GS-Hold isn't working anymore. Only the one with nasal-scripted Autopilots. We haven't got much of them > For the record, my perception is that entering a value in > the generic autopilot dialog for 'true heading' has never > worked, because the value would **always** be over-written > by the route manager. It worked as long we didn't use the Route-manager. Like Curt already said, with pending waypoints the values are overwritten, but only then. That hasn't changed. > > What *has* changed is that the value now actually comes > from the GPS code, not the route-manager. Both are equally > 'generic' (just like the autopilot itself), it was just > simpler from a code design perspective to handle the > autopilot interaction in the GPS code, and keep the > route-manager separated. > > Does this fit with what you're seeing? Yep, but though a lot of aircrafts has to be fixed before release, or otherwise we will really have a "debacle"! Cheers HHS > -- > This SF.Net email is sponsored by the Verizon Developer > Community > Take advantage of Verizon's best-in-class app development > support > A streamlined, 14 day to market process makes app > distribution fast and easy > Join now and get one step closer to millions of Verizon > customers > http://p.sf.net/sfu/verizon-dev2dev > ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > __ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Autopilot broken, Eric maybe?
Heiko Schulz wrote: > Hi, > > There were major changes on the GPS and Route-Manager since August (3 Months > ago already!) > > So this has affected the the use of the autopilot as well. > All aircrafts using the generic Autopilot-panel are affected, but not those > with an own written flightdirector like Syds Aircrafts (Citation Bravo works > perfect) or with own configured autopilots like the senecaII, c172p, PA24-250. > Citation Bravo does not work :-( True Heading goes in circles pete -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Autopilot broken, Eric maybe?
> Hi, > Why is the autopilot broken? > > Specifically on my models like bluebird (or ufo if you prefer), I > started to implement a requested feature, but found it does not work > like it used to. > > The property: > /autopilot/settings/true-heading-deg > > acts like it is being set by something else that shouldn't. The GPS code sets the property /autopilot/settings/true-heading-deg if /instrumentation/gps/config/drive-autopilot is true (which is true by default). I don't know much about the details of the new gps code from James Turner, maybe he could chime in for some explanation... Greetings, Torsten -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Autopilot broken, Eric maybe?
On Mon, Dec 21, 2009 at 11:17 AM, James Turner wrote: > For the record, my perception is that entering a value in the generic > autopilot dialog for 'true heading' has never worked, because the value > would **always** be over-written by the route manager. > This would only have been the case if there were any pending waypoints in the route manager. If all waypoints had been reached, or no waypoints have been entered, then the 'old' route manager should not have touched the true-heading-target value. Regards, Curt. -- Curtis Olson: http://baron.flightgear.org/~curt/ -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Autopilot broken, Eric maybe?
On 21 Dec 2009, at 16:33, Heiko Schulz wrote: > There were major changes on the GPS and Route-Manager since August (3 Months > ago already!) > > So this has affected the the use of the autopilot as well. > All aircrafts using the generic Autopilot-panel are affected, but not those > with an own written flightdirector like Syds Aircrafts (Citation Bravo works > perfect) or with own configured autopilots like the senecaII, c172p, PA24-250. > True-Heading can be used with the DTO-Mode in the GPS-menu in the Menubar. > > I think James can tell more! The issue / feature here is that the route-manager code has 'always' (for years, at least) directly set /autopilot/settings/true-heading-deg based on its internal route-following logic. Personally I don't think it's a great feature, but people do use it (the route manager) in conjunction with the generic autopilot dialog to quickly navigate between waypoints. When I broke the feature by accident, it was noticed, and people asked for the feature back. As far as I know, the old route-manager code behaved much the same as my code does now - but it sounds as if you disagree? For the record, my perception is that entering a value in the generic autopilot dialog for 'true heading' has never worked, because the value would **always** be over-written by the route manager. What *has* changed is that the value now actually comes from the GPS code, not the route-manager. Both are equally 'generic' (just like the autopilot itself), it was just simpler from a code design perspective to handle the autopilot interaction in the GPS code, and keep the route-manager separated. Does this fit with what you're seeing? Regards, James -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Autopilot broken, Eric maybe?
S Andreason wrote: > Hi, > Why is the autopilot broken? > > Specifically on my models like bluebird (or ufo if you prefer), I > started to implement a requested feature, but found it does not work > like it used to. > > The property: > /autopilot/settings/true-heading-deg > > acts like it is being set by something else that shouldn't. > > P source/src/FDM/JSBSim/ 105 files updated by ehofman (Is that you > Eric?) > It is me indeed, but I just synchronize JSBSim CVS and FlightGear at that point. If JSBSim is the cause (which I find hard to believe at this point) then there' s something severely wrong since JSBSim has no business updating anything under /autopilot. Erik -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Autopilot broken, Eric maybe?
Hi, There were major changes on the GPS and Route-Manager since August (3 Months ago already!) So this has affected the the use of the autopilot as well. All aircrafts using the generic Autopilot-panel are affected, but not those with an own written flightdirector like Syds Aircrafts (Citation Bravo works perfect) or with own configured autopilots like the senecaII, c172p, PA24-250. True-Heading can be used with the DTO-Mode in the GPS-menu in the Menubar. I think James can tell more! Cheers HHS > Hi, > Why is the autopilot broken? > > Specifically on my models like bluebird (or ufo if you > prefer), I > started to implement a requested feature, but found it does > not work > like it used to. > > The property: > /autopilot/settings/true-heading-deg > > acts like it is being set by something else that > shouldn't. > When pressing the Heading Hold button on the panel, my > aircraft flies in > circles, because this property is constantly changing. Or > with c172p > press [F11] to load autopilot settings, click True Heading, > and attempt > to give it a heading to follow! I am surprised the c172p is > broken as > well, so it is not just my models. > Is there a reason the Autopilot on the top menubar is > greyed out? > > I narrowed down the time frame when this changed. > It works correctly Aug.11 and early Aug.12 (stays nil until > set, and > stays as set), > and is broken Aug.13 > > Changes include: > P source/src/Airports/simple.hxx > P source/src/Autopilot/route_mgr.cxx > P source/src/Cockpit/hud.cxx > P source/src/Environment/environment_ctrl.cxx > P source/src/FDM/JSBSim/ 105 files updated by > ehofman (Is that you > Eric?) > P source/src/Instrumentation/** 5 files > > If you press [/] right after the scenery starts loading, > then quickly > click down 2 directory levels, you can watch when this > property starts > getting set. Throttle up and the autopilot heading starts > changing > faster and faster, slows down at 180 from current heading, > then speeds > up as fast as 10 degrees per second. Quite wild. > > I also searched the last few months of messages, but can't > find anything > relevant to this. > > Stewart > > > -- > This SF.Net email is sponsored by the Verizon Developer > Community > Take advantage of Verizon's best-in-class app development > support > A streamlined, 14 day to market process makes app > distribution fast and easy > Join now and get one step closer to millions of Verizon > customers > http://p.sf.net/sfu/verizon-dev2dev > ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > __ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Autopilot broken, Eric maybe?
Hi, Why is the autopilot broken? Specifically on my models like bluebird (or ufo if you prefer), I started to implement a requested feature, but found it does not work like it used to. The property: /autopilot/settings/true-heading-deg acts like it is being set by something else that shouldn't. When pressing the Heading Hold button on the panel, my aircraft flies in circles, because this property is constantly changing. Or with c172p press [F11] to load autopilot settings, click True Heading, and attempt to give it a heading to follow! I am surprised the c172p is broken as well, so it is not just my models. Is there a reason the Autopilot on the top menubar is greyed out? I narrowed down the time frame when this changed. It works correctly Aug.11 and early Aug.12 (stays nil until set, and stays as set), and is broken Aug.13 Changes include: P source/src/Airports/simple.hxx P source/src/Autopilot/route_mgr.cxx P source/src/Cockpit/hud.cxx P source/src/Environment/environment_ctrl.cxx P source/src/FDM/JSBSim/ 105 files updated by ehofman (Is that you Eric?) P source/src/Instrumentation/** 5 files If you press [/] right after the scenery starts loading, then quickly click down 2 directory levels, you can watch when this property starts getting set. Throttle up and the autopilot heading starts changing faster and faster, slows down at 180 from current heading, then speeds up as fast as 10 degrees per second. Quite wild. I also searched the last few months of messages, but can't find anything relevant to this. Stewart -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] autopilot broken by recent osg branc h fgfsupdate
On Wed 24 January 2007 07:14, Dave Perry wrote: > On Tue, 2007-01-23 at 18:48 +0100, Roy Vegard Ovesen wrote: > > Just updated from CVS (HEAD (OSG)), and it seems to me that the > > autopilots are > > working. I tried the KAP140, and the generic in the pa28-161. Both > > worked > > fine in heading mode, and the followed the bug on the HSI. > > I just did a cvs update -dP for both simgear and the fgfs source (osg > branch) and the "new version" kap140 works with the one quirk; to get > the heading bug to work requires going to the debug gui and reloading > the autopilot config. Oh yes that is right , if we reload the autopilot config with menu/debug We get the autopilot working heading and altitude and the WP function is right Regards -- Gérard - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] autopilot broken by recent osg branch fgfsupdate
On Tue, 2007-01-23 at 18:48 +0100, Roy Vegard Ovesen wrote:
> Just updated from CVS (HEAD (OSG)), and it seems to me that the
> autopilots are
> working. I tried the KAP140, and the generic in the pa28-161. Both
> worked
> fine in heading mode, and the followed the bug on the HSI.
>
I just did a cvs update -dP for both simgear and the fgfs source (osg
branch) and the "new version" kap140 works with the one quirk; to get
the heading bug to work requires going to the debug gui and reloading
the autopilot config.
Here is the version with the differential approximation for altFt. I
think this is exactly what you asked for in
> What I'm asking for is an equation to convert from pressure altitude
> to ASL
> altitude. Something like
> ASL_alt = f(pressure_alt, ref_pressure)
>
1) Add the partial derivative function before altAlert:
hPartial = func {
p0 = arg[1];# Units of p0 must match units of delta p
p = arg[0]; # Units of p must match units of delta p
t0 = 288.15;# [K]
LR = -0.0065;# [K/m]
g = -9.80665;# [m/s²]
Rd = 287.05307; # [J/kg K]
gamma = (Rd*LR)/g;
z = -(t0/LR)*gamma*pow((p/p0),gamma)/p0;
return z;
}
2) Replace the computation of altFt in altAlert with
pressureAltitude = getprop(encoder, "pressure-alt-ft");
hPartBaro = hPartial(baroSettingInhg, 29.92) / 0.3048006;
# print("hPartBaro = ",hPartBaro);
altFt = pressureAltitude + hPartBaro * (baroSettingInhg - 29.92);
Notice:
1) altFt = f(pressure_alt, baro_setting)
2) requires only one call of pow (i.e. exp and ln)
I will send you the working kap140.nas with these changes off-list. It
is working well here.
Regards,
--
Dave Perry
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] autopilot broken by recent osg branch fgfsupdate
On Tue 23 January 2007 18:48, Roy Vegard Ovesen wrote:
> On Tuesday 23 January 2007 16:00, gh.robin wrote:
> > On Tue 23 January 2007 03:27, Dave Perry wrote:
> > > I updated both SimGear, fgfs source, and data for the osg branch
> > > yesterday. After the compiles and installs with no errors, none of the
> > > autopilots are working. This includes the default autopilot from the
> > > gui as well as the kap140 (I am testing the new version from Roy Vegard
> > > Oveson). All were working before the cvs update. The kap140 files are
> > > from before the update.
> > >
> > > I tried the pa28-161 with the default autopilot and the symptoms were
> > > the same as with the kap140.
> > >
> > > With the PRE_OSG_Plib branch fgfs and the /data from the osg branch
> > > test, everything still works as expected.
> > >
> > > The altitude capture still works but the HDG, APR, and NAV do nothing
> > > except wing level. Turning the HI heading bug has no affect. The
> > > locks are updating in the property list.
> > >
> > > Are others seeing this behavior?
> > >
> > > Regards,
>
> Just updated from CVS (HEAD (OSG)), and it seems to me that the autopilots
> are working. I tried the KAP140, and the generic in the pa28-161. Both
> worked fine in heading mode, and the followed the bug on the HSI.
>
> Gérard, are you still heaving trouble with the autopilot? If you are could
> you please tell us excactly what isn't working. Are the controllers not
> activated at all? Are they using non-existent input properties? Have you
> tried to activate the debugging of the controllers (writes debugging info
> to the console)?
Hello Roy,
I just updated from that CVS (HEAD (OSG)), and i confirm getting the same
trouble than Dave , (which is a positive progress to mebecause i have
again the autopilot Altitude working).
I had a talk before with with Dave regarding --->kap140 bug+fix<--- topics
where i explained
---> When the hdg bug is moved the AC seems to obey to that order but the AC
is not auto corrected for the right heading and start to turn permanently
<---
The properties are set with the right values on the /autopilot . Heading and
lock are right
the heading-bug-error-deg is updated in real time
But the auto correction is not done.
The most representative test for that bug is when i try to use the WP
function i get the right value on the properties, but the aircraft never goes
toward the right heading.
I don't know how to activate debugging of the controllers, and
Debugging Options: --log-level={bulk,debug,info,warn,alert
are useless
Regards
--
Gérard
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] autopilot broken by recent osg branch fgfsupdate
On Tuesday 23 January 2007 16:00, gh.robin wrote: > On Tue 23 January 2007 03:27, Dave Perry wrote: > > I updated both SimGear, fgfs source, and data for the osg branch > > yesterday. After the compiles and installs with no errors, none of the > > autopilots are working. This includes the default autopilot from the > > gui as well as the kap140 (I am testing the new version from Roy Vegard > > Oveson). All were working before the cvs update. The kap140 files are > > from before the update. > > > > I tried the pa28-161 with the default autopilot and the symptoms were > > the same as with the kap140. > > > > With the PRE_OSG_Plib branch fgfs and the /data from the osg branch > > test, everything still works as expected. > > > > The altitude capture still works but the HDG, APR, and NAV do nothing > > except wing level. Turning the HI heading bug has no affect. The locks > > are updating in the property list. > > > > Are others seeing this behavior? > > > > Regards, > > Hello, Dave > > Yes i did noticed it , and said that bug on that mailing-list, but could > not explain it > > http://sourceforge.net/mailarchive/message.php?msg_id=37840820 > follow the thread > Regards Just updated from CVS (HEAD (OSG)), and it seems to me that the autopilots are working. I tried the KAP140, and the generic in the pa28-161. Both worked fine in heading mode, and the followed the bug on the HSI. Gérard, are you still heaving trouble with the autopilot? If you are could you please tell us excactly what isn't working. Are the controllers not activated at all? Are they using non-existent input properties? Have you tried to activate the debugging of the controllers (writes debugging info to the console)? -- Roy Vegard Ovesen - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] autopilot broken by recent osg branch fgfs update
On Tue 23 January 2007 03:27, Dave Perry wrote: > I updated both SimGear, fgfs source, and data for the osg branch > yesterday. After the compiles and installs with no errors, none of the > autopilots are working. This includes the default autopilot from the > gui as well as the kap140 (I am testing the new version from Roy Vegard > Oveson). All were working before the cvs update. The kap140 files are > from before the update. > > I tried the pa28-161 with the default autopilot and the symptoms were > the same as with the kap140. > > With the PRE_OSG_Plib branch fgfs and the /data from the osg branch > test, everything still works as expected. > > The altitude capture still works but the HDG, APR, and NAV do nothing > except wing level. Turning the HI heading bug has no affect. The locks > are updating in the property list. > > Are others seeing this behavior? > > Regards, Hello, Dave Yes i did noticed it , and said that bug on that mailing-list, but could not explain it http://sourceforge.net/mailarchive/message.php?msg_id=37840820 follow the thread Regards -- Gérard - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] autopilot broken by recent osg branch fgfs update
I updated both SimGear, fgfs source, and data for the osg branch yesterday. After the compiles and installs with no errors, none of the autopilots are working. This includes the default autopilot from the gui as well as the kap140 (I am testing the new version from Roy Vegard Oveson). All were working before the cvs update. The kap140 files are from before the update. I tried the pa28-161 with the default autopilot and the symptoms were the same as with the kap140. With the PRE_OSG_Plib branch fgfs and the /data from the osg branch test, everything still works as expected. The altitude capture still works but the HDG, APR, and NAV do nothing except wing level. Turning the HI heading bug has no affect. The locks are updating in the property list. Are others seeing this behavior? Regards, -- Dave Perry <[EMAIL PROTECTED]> - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
