If its any help , the error message pops up the instant the gps dialog is
opened.The dialog seems to work regardless , so Im not sure what the
problem is.
Syd
On Wed, Oct 9, 2013 at 1:20 PM, syd adams wrote:
> No , Im not sure what caused the segfault... but the error message appears
> every ti
No , Im not sure what caused the segfault... but the error message appears
every time i try to use gps navigation ( with the b1900d).Another change in
behavior is the heading needle deflection is extremely sensitive now when
using nav1 slaved to gps. I could be wrong , i dont have the docs in front
Am Mittwoch, 9. Oktober 2013, 01:37:27 schrieb syd adams:
> Not sure what went wrong but i get this error consistently now:
>
> Nasal runtime error: props.setValue() with non-number
> at /media/FG/fgdata/Nasal/props.nas, line 29
> called from: __dlg:gps, line 20
> called from: __dlg:gps, lin
I will search for that. allways a segfault ? fg crash ?
2013/10/9 syd adams
> Not sure what went wrong but i get this error consistently now:
>
> Nasal runtime error: props.setValue() with non-number
> at /media/FG/fgdata/Nasal/props.nas, line 29
> called from: __dlg:gps, line 20
> calle
Not sure what went wrong but i get this error consistently now:
Nasal runtime error: props.setValue() with non-number
at /media/FG/fgdata/Nasal/props.nas, line 29
called from: __dlg:gps, line 20
called from: __dlg:gps, line 134
Segmentation fault (core dumped)
On Fri, Oct 4, 2013 at 1:48
Am Donnerstag, 3. Oktober 2013, 21:38:52 schrieb James Turner:
> On 3 Oct 2013, at 17:35, Dirk Dittmann wrote:
> > The improved-issue1164 is ready.
>
> > https://gitorious.org/fg/dirks-flightgear/source/778cc8c6a0abb88a1238850376ea2374358fd887:
> Thanks, looks good and pushed.
thx
>
> Unfortunat
http://wiki.flightgear.org/Talk:Nasal_Style_Guide
On Thu, Oct 3, 2013 at 9:38 PM, James Turner wrote:
>
> On 3 Oct 2013, at 17:35, Dirk Dittmann
> wrote:
>
> The improved-issue1164 is ready.
>
> https://gitorious.org/fg/dirks-flightgear/source/778cc8c6a0abb88a1238850376ea2374358fd887:
>
>
> Th
On 3 Oct 2013, at 17:35, Dirk Dittmann wrote:
> The improved-issue1164 is ready.
> https://gitorious.org/fg/dirks-flightgear/source/778cc8c6a0abb88a1238850376ea2374358fd887:
Thanks, looks good and pushed.
Unfortunately I now need to fix the route-path code to subdivide long legs
along the gre
Hi James,
The improved-issue1164 is ready.
https://gitorious.org/fg/dirks-flightgear/source/778cc8c6a0abb88a1238850376ea2374358fd887:
Dirk
Am Dienstag, 1. Oktober 2013, 21:37:58 schrieb James Turner:
> - please make a helper function for the great-circle XTK error function,
> with some sane na
On 1 Oct 2013, at 23:07, James Turner wrote:
> No, there's rules, since the codebase contains quite a mixture.
Whoops, typo. Meant to say,
'No, there's NO rules, since...'
James ;)--
October Webinars: Code for Perfo
On 1 Oct 2013, at 22:34, Dirk Dittmann wrote:
> I understand and will make the improvements. Thx for the hind ! I squash the
> commit and improve readability. Is there any code convention documentation ?
> Which I could read?
No, there's rules, since the codebase contains quite a mixture. We
Am Dienstag, 1. Oktober 2013, 21:37:58 schrieb James Turner:
> On 30 Sep 2013, at 08:47, Dirk Dittmann wrote:
> > branche fix-issue1164 @ my clone
>
> > https://gitorious.org/fg/dirks-flightgear/source/85592ec45db2866a15197c051d97cb4014537b4b:
> Hi Dirk, this is looking pretty good, just some sma
On 30 Sep 2013, at 08:47, Dirk Dittmann wrote:
> branche fix-issue1164 @ my clone
> https://gitorious.org/fg/dirks-flightgear/source/85592ec45db2866a15197c051d97cb4014537b4b:
Hi Dirk, this is looking pretty good, just some small nitpicks:
- please make a helper function for the great-circle XT
Am Montag, 30. September 2013, 12:52:08 schrieb James Turner:
> On 30 Sep 2013, at 12:29, Eric van den Berg
wrote:
> > The other stuff I asked Dirk to add as it makes our extra500 (GPSS) AP
> > design a lot easier.
> Incidentally if you (Dirk) are looking at this code, the really great thing
> wo
on, 30 Sep 2013 12:52:08 +0100
To: flightgear-devel@lists.sourceforge.net
Subject: Re: [Flightgear-devel] GPS - merge request
On 30 Sep 2013, at 12:29, Eric van den Berg
wrote:The other stuff I asked Dirk to add as it makes our extra500 (GPSS) AP
design a lot easier.
Incidentally if you
On 30 Sep 2013, at 12:29, Eric van den Berg wrote:
> The other stuff I asked Dirk to add as it makes our extra500 (GPSS) AP design
> a lot easier.
Incidentally if you (Dirk) are looking at this code, the really great thing
would be to get the turn-anticipation code enabled. All the pieces are
On 30 Sep 2013, at 12:29, Eric van den Berg wrote:
> It actually does solve issue 1164 (which I started).
> When one switches to the next waypoint, the active leg course and
> x-track-error relate to the leg between the previous and active waypoint of
> the flightplan (as it should in LEG mode
@lists.sourceforge.net
Subject: Re: [Flightgear-devel] GPS - merge request
On 30 Sep 2013, at 08:47, Dirk Dittmann
wrote:Improved the Cross track error according to the great circle.
http://williams.best.vwh.net/avform.htm#XTE.
Great,.
And make the overflight sequence configurable for the aircraft. The
Am Montag, 30. September 2013, 09:00:19 schrieb James Turner:
> On 30 Sep 2013, at 08:47, Dirk Dittmann wrote:
> > Improved the Cross track error according to the great circle.
> > http://williams.best.vwh.net/avform.htm#XTE.
>
> Great,.
>
> > And make the overflight sequence configurable for th
On 30 Sep 2013, at 08:47, Dirk Dittmann wrote:
> Improved the Cross track error according to the great circle.
> http://williams.best.vwh.net/avform.htm#XTE.
Great,.
>
> And make the overflight sequence configurable for the aircraft. The default
> is
> the same.
>
> /instrumentation/gps/c
Hello,
Improved the Cross track error according to the great circle.
http://williams.best.vwh.net/avform.htm#XTE.
And make the overflight sequence configurable for the aircraft. The default is
the same.
/instrumentation/gps/config/over-flight-arm-angle-deg 90
/instrumentation/gps/con
Hi,
Hate to be a nuisance, but is there any reason for this limit:
if (_last_speed_kts < 60) {
// need valid leg course and sensible ground speed to compute the turn
return;
}
in Instrumentation/gps.cxx line 770?
If I have a vehicle with a ground speed of less than 60, the route
Hi all,
I would like to give my support to Olivier about the merge request :
https://gitorious.org/fg/fgdata/merge_requests/139
This merge request contains the Garmin GPS196. I use it in real life with my
aircraft and I'd take pleased to see it in fgdata.
I invite anybody with commit's right to
Hi all,
Quite a lot of people within the FG world has been asking to include some of
the PAF projects into the official FG git
repository. The team is now ready to do so, and is ready to issue the
corresponding merge
requests:
- one concerning a new joystick configuration file ;
- one concern
On 11-07-14 04:16 AM, Stuart Buchanan wrote:
> Martin Muc wrote:
>> Just trying Flight Gear for the first time today. What a ridiculously
>> top-notch open source project. Just awesome. Congrats and thank you to
>> everyone who's made it so.
> Glad you like it. It's only as good as the people
Thank you pointing this, I haven't seen it. Here is the patch to correct
the mistake.
Thanks in advance to commit it.
best regards
seb
Victhor Foster wrote :
Well, since this was a GPS-related thread, I decided to post this here instead
of creating another thread :-)
The zkv500's "Turnpoint"
Well, since this was a GPS-related thread, I decided to post this here instead
of creating another thread :-)
The zkv500's "Turnpoint" screen works properly now. However, the navigation
display won't show the distance to the waypoint.
--
On 10 Dec 2009, at 21:41, Scott Hamilton wrote:
> I can't seem to find it in airportinfo(), this is what debug.dump shows;
>
> { id: 'YMML', elevation: 131.97839, lat: -37.66986124, name:
> 'Melbourne Intl', has_metar: 1, lon: 144.842831907, runways: {
> 16: { id: 16, stopway:
On Wed, 2009-12-09 at 13:54 +, James Turner wrote:
> > Off-topic is there anyway in Nasal to find the ILS frequencies and
> > optionally the name, for a particular airport and runway?
>
> Yes, the airportinfo function returns you a Nasal hash with all this and more.
I can't seem to f
Hi James,
thank you very much for your changes, here is the very first step of a
vor-to-vor flightplan builder. Let me improve it for more functions and
capacities.
best regards,
seb
James Turner a ecrit :
On 9 Dec 2009, at 13:47, Scott Hamilton wrote:
Something I was playing around wi
On 9 Dec 2009, at 13:47, Scott Hamilton wrote:
>Something I was playing around with a few months back I thought, if only I
> could find the nearest VOR/NDB/FIX/APT to
>some point that I am not at but will be in the near future, unfortunately
> I've forgotten what it was I was trying to
On Wed, 2009-12-09 at 08:27 +, James Turner wrote:
I second this.
Something I was playing around with a few months back I thought, if
only I could find the nearest VOR/NDB/FIX/APT to
some point that I am not at but will be in the near future,
unfortunately I've forgotten what it was
Ok I'll look into it further ... need to learn how to use it before i
update the KLN90B...
Altitude is set from a separate instrument , not linked to the GPS in any way.
As for the EFIS-84 settings , I haven't come across any good refences
for the controller, so it can only be set from the dialog f
On 16 Nov 2009, at 11:35, Stuart Buchanan wrote:
> One minor bug was that selecting a NAV ID in the GPS reset the set
> altitude to the NAV
> ID height, but didn't update that altitude select on the panel. I
> think this might be seen as
> a bug in the GPS code rather than the panel, as that'
syd adams wrote:
> Hello James ,
> Just tried the b1900d after a long while , and I have no idea how to
> use my own KLN90B anymore ... any pointers on how I can fix this ?
> In particular , I cant set the destination waypoint , though it
> appears with a search.
> Thanks.
I had a fairly success
On 16 Nov 2009, at 07:43, syd adams wrote:
> Just tried the b1900d after a long while , and I have no idea how to
> use my own KLN90B anymore ... any pointers on how I can fix this ?
> In particular , I cant set the destination waypoint , though it
> appears with a search.
I assume when you tal
On 16 Nov 2009, at 08:53, Victhor Foster wrote:
> You need to use the Route Manager dialog. The route will only
> activate once the aircraft is airborne.
Uh, I hope not :) That's not the intended behaviour, and it's not what
I see. Indeed, I normally activate the route before I taxi out to t
You need to use the Route Manager dialog. The route will only activate once the
aircraft is airborne.
Look at the GPS dialog. If you see that the destination airport on the current
leg is your departure airport, go back to the route manager, search for your
destination's ICAO code, then press "D
Hello James ,
Just tried the b1900d after a long while , and I have no idea how to
use my own KLN90B anymore ... any pointers on how I can fix this ?
In particular , I cant set the destination waypoint , though it
appears with a search.
Thanks.
Hi,
>
> Also, if we have two consistent time_t, why not simply subtract one from
> the other, ABS it, and voila you have the time difference ? Or am I
> missing something regarding usage of difftime ?
yes. there is no _standard_ mapping of the data type time_t to any
standard C/C++ data type.
Hey all, I also added on my side, in an #ifdef, since it's somehow
already included nix side :)
That said, why not simply assign 0 to the two time_t rather than a function
call ?
Then, it's only a matter of dealing with difftime.
Don't we already have time (and timing ?) abstracted facilities tho
On 7 Oct 2009, at 10:32, Alan Teeder wrote:
James
The “this” fault is fixed. Thanks.
To cure the time and difftime under Windows all that is needed is to
include
That's what I'd hoped, thanks for confirming. I would still prefer to
use something more robust than the C-library functions,
uot;file://d:\fg\source\projects\VC90\FlightGear\Win32\Release\BuildLog.htm"
Alan
_
From: Nicolas Quijano [mailto:nquij...@gmail.com]
Sent: 06 October 2009 17:22
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] GPS / route-manager landing
Hi all, this doesn&
\..\src\Autopilot\route_mgr.cxx(234) : error C3861: 'difftime':
identifier not found
Build log was saved at "file://d:\fg\source\projects\VC90\FlightGear\Win32\Release\BuildLog.htm
"
Alan
From: Nicolas Quijano [mailto:nquij...@gmail.com]
Sent: 06 October 2009 17:22
To: FlightGea
lease\BuildLog.htm"
Alan
_
From: Nicolas Quijano [mailto:nquij...@gmail.com]
Sent: 06 October 2009 17:22
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] GPS / route-manager landing
Hi all, this doesn't build on windows, it can't find the
Hi all, this doesn't build on windows, it can't find the time symbol
referenced at line 229 and 233 in route_mgr.cxx.
Missing header ?
Also, there is a reference to std::strncasecmp in positioned.cxx around line
820, which is also not available in windows (at least, not here).
Since it's dealing w
On 5 Oct 2009, at 08:33, Dave wrote:
> That all sounds like good stuff. I'll try and migrate the KLN89
> towards
> using it and depreciating the dclgps stuff - that should give it some
> testing.
Sounds good to me. I've been going through the KLN89 manual, and
there's definitely some more s
James Turner wrote:
> Just a notification / warning - I'm planning to land my GPS / FMS /
> route-manager re-write tomorrow (Monday). It's not perfect (yet) but
> already much more usable than the previous code. I'm sure I'll regress
> a few things initially, but of course I'll work through a
Just a notification / warning - I'm planning to land my GPS / FMS /
route-manager re-write tomorrow (Monday). It's not perfect (yet) but
already much more usable than the previous code. I'm sure I'll regress
a few things initially, but of course I'll work through any issues
that people repo
Thanks guys :)
--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with
Now that you've explained what ecrit means and I'm sure everyone is pleased
to find out it's nothing painful, :-) I don't think you necessarily need to
worry about changing your email client.
Regards,
Curt.
On Tue, Feb 17, 2009 at 2:47 PM, Sébastien MARQUE wrote:
> sorry guys for that, I forgo
sorry guys for that, I forgot to withdraw the accent, btw I haven't
found yet where I can change this permanently in my thunderbird config.
seb
Csaba Halász a ecrit (wrote):
> On Tue, Feb 17, 2009 at 9:14 PM, syd adams wrote:
>> I have a silly , non FG question
>> what does "syd adams a éc
On Tue, Feb 17, 2009 at 9:14 PM, syd adams wrote:
> I have a silly , non FG question
> what does "syd adams a écrit :" mean
> Googling didn't help , and I don't speak french
Well, look at the header for the quote above, and try to compare with
the "ecrit" thing :)
--
Csaba/Jester who
Lol...
>I have a silly , non FG question
>what does "syd adams a écrit :" mean
>Googling didn't help , and I don't speak french
>Cheers :)
It means: "Syd Adams wrote..."
:-)
--
Open Source Business
I have a silly , non FG question
what does "syd adams a écrit :" mean
Googling didn't help , and I don't speak french
Cheers :)
On Tue, Feb 17, 2009 at 9:34 AM, Sébastien MARQUE wrote:
> Hi,
>
> There is a "gps" in CVS: $FGROOT/Aircraft/Instruments-3d/zkv500, I mean
> an instrument whi
Hi,
There is a "gps" in CVS: $FGROOT/Aircraft/Instruments-3d/zkv500, I mean
an instrument which looks like a gps for a non-pilot, not-advised user
:). This instrument manages routes, looks for airports, saves waypoints
(bookmarks), creates routes, give several infos about wind, etc.
It uses th
I had planned to switch the B1900D over to use that , since my nasal KLN90B
is nothing more than a display of the current gps properties but
waiting to see whats happening with the KLN89.
Cheers
--
Open Source Busines
James Turner wrote:
> On 17 Feb 2009, at 00:49, Curtis Olson wrote:
>
>
>> At one point I think I recall that we had a variant of the C172 with
>> a working GPS installed in the instrument panel. I don't see that
>> any more now. Does anyone recall if we had such a thing and know
>> wher
On 17 Feb 2009, at 00:49, Curtis Olson wrote:
> At one point I think I recall that we had a variant of the C172 with
> a working GPS installed in the instrument panel. I don't see that
> any more now. Does anyone recall if we had such a thing and know
> where it can be found?
I presume y
At one point I think I recall that we had a variant of the C172 with a
working GPS installed in the instrument panel. I don't see that any more
now. Does anyone recall if we had such a thing and know where it can be
found?
Thanks,
Curt.
--
Curtis Olson: http://baron.flightgear.org/~curt/
-
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, u
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 l
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
Here's a patch which refactors the 'plain' GPS code into a slightly
more manageable structure - i.e breaks the large update() method into
various sub-functions. I've tested the patch with B1900d, and things
seem to work as expected, but if anyone experiences GPS weirdness
after this is comm
>
> * LeeE -- Monday 14 April 2008:
> > I'm running a nasal loop at 1/(frame-rate/2), which typically works
> > out to between 10-20 Hz, but because the gps update rate is much
> > slower (0.45 sec if I'm interpreting the code correctly) the
> > results aren't very smooth - the effect is that
So summarising the current state of play - research seem to show
that gps units can have update rates of 50Hz+ but cost a lot of
money.
In view of that it seems reasonable to make the FG gps update rate
configurable - that was the main purpose of researching it - I
didn't want to make it confi
On Monday 14 April 2008 18:55, Melchior FRANZ wrote:
> * Curtis Olson -- Monday 14 April 2008:
> > Let's say I want to do a simple moving average ... so the new
> > value is (let's say) 9 parts the previous filtered value + 1
> > part of the latest sensor reading. Doing that as a simple
> > averag
On Mon, Apr 14, 2008 at 2:01 PM, Mike Schuh <[EMAIL PROTECTED]> wrote:
> On Mon, 14 Apr 2008, Melchior FRANZ wrote:
>
> >* Curtis Olson -- Monday 14 April 2008:
> >> Let's say I want to do a simple moving average ...
> >
>
> >FlightGear has an aircraft.angular_lowpass() in $FG_ROOT/Nasal/aircraf
On Mon, 14 Apr 2008, Melchior FRANZ wrote:
>* Curtis Olson -- Monday 14 April 2008:
>> Let's say I want to do a simple moving average ...
>
>FlightGear has an aircraft.angular_lowpass() in $FG_ROOT/Nasal/aircraft.nas.
>It filters sin() and cos() separately, and builds the angle from that again.
T
* LeeE -- Monday 14 April 2008:
> I'm running a nasal loop at 1/(frame-rate/2), which typically works
> out to between 10-20 Hz, but because the gps update rate is much
> slower (0.45 sec if I'm interpreting the code correctly) the
> results aren't very smooth - the effect is that the results fo
On Mon, Apr 14, 2008 at 12:55 PM, Melchior FRANZ wrote:
> * Curtis Olson -- Monday 14 April 2008:
> > Let's say I want to do a simple moving average ... so the new value is
> > (let's say) 9 parts the previous filtered value + 1 part of the latest
> > sensor reading. Doing that as a simple averag
* Curtis Olson -- Monday 14 April 2008:
> Let's say I want to do a simple moving average ... so the new value is
> (let's say) 9 parts the previous filtered value + 1 part of the latest
> sensor reading. Doing that as a simple average though will glitch if your
> values are coming in around 0/360.
On Mon, Apr 14, 2008 at 11:29 AM, LeeE wrote:
> Oops - meant an exponential filter - seems to work ok, except for
> the inevitable glitch between 360/0 deg (I'm using
> indicated-track-true-deg) but then it resolves in 0.45 sec, which
> isn't too bad. The lag affected a couple of controllers but
On Monday 14 April 2008 15:47, LeeE wrote:
> On Monday 14 April 2008 15:09, Curtis Olson wrote:
> > On Mon, Apr 14, 2008 at 8:38 AM, LeeE wrote:
> > > I've been doing some experimentation using the gps instrument
> > > for navigation functions but I've hit a minor problem due to
> > > the gps instr
http://www.k300performance.co.uk/driftbox.htm
may be of interest and is a little more affordable, possibly around 1000 of
your US dollahs
Best Regards
Willie Fleming
-
This SF.net email is sponsored by the 2008 JavaOne(SM
On Monday 14 April 2008 15:09, Curtis Olson wrote:
> On Mon, Apr 14, 2008 at 8:38 AM, LeeE wrote:
> > I've been doing some experimentation using the gps instrument
> > for navigation functions but I've hit a minor problem due to
> > the gps instrument update rate.
> >
> > I'm running a nasal loop a
On Mon, Apr 14, 2008 at 8:38 AM, LeeE wrote:
> I've been doing some experimentation using the gps instrument for
> navigation functions but I've hit a minor problem due to the gps
> instrument update rate.
>
> I'm running a nasal loop at 1/(frame-rate/2), which typically works
> out to between 10-
Hi all,
I've been doing some experimentation using the gps instrument for
navigation functions but I've hit a minor problem due to the gps
instrument update rate.
I'm running a nasal loop at 1/(frame-rate/2), which typically works
out to between 10-20 Hz, but because the gps update rate is muc
Hello,
Some time ago, when i clicked on the
Menu/Equipment/GPS Setting/ Get nearest airport
I could get the Airport.
Now It does not work, does anybody else noticed that change ?
Is it a bug ?
Regards
--
Gérard
-
T
79 matches
Mail list logo
