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 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, line 134
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
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 adams@gmail.com wrote:
No , Im not sure what caused the segfault... but the error message
Am Donnerstag, 3. Oktober 2013, 21:38:52 schrieb James Turner:
On 3 Oct 2013, at 17:35, Dirk Dittmann dirk.dittmann@gmail.com wrote:
The improved-issue1164 is ready.
https://gitorious.org/fg/dirks-flightgear/source/778cc8c6a0abb88a1238850376ea2374358fd887:
Thanks, looks good and
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
On 3 Oct 2013, at 17:35, Dirk Dittmann dirk.dittmann@gmail.com 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
http://wiki.flightgear.org/Talk:Nasal_Style_Guide
On Thu, Oct 3, 2013 at 9:38 PM, James Turner zakal...@mac.com wrote:
On 3 Oct 2013, at 17:35, Dirk Dittmann dirk.dittmann@gmail.com
wrote:
The improved-issue1164 is ready.
On 30 Sep 2013, at 08:47, Dirk Dittmann dirk.dittmann@gmail.com 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
Am Dienstag, 1. Oktober 2013, 21:37:58 schrieb James Turner:
On 30 Sep 2013, at 08:47, Dirk Dittmann dirk.dittmann@gmail.com wrote:
branche fix-issue1164 @ my clone
https://gitorious.org/fg/dirks-flightgear/source/85592ec45db2866a15197c051d97cb4014537b4b:
Hi Dirk, this is looking
On 1 Oct 2013, at 22:34, Dirk Dittmann dirk.dittmann@gmail.com 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
On 30 Sep 2013, at 08:47, Dirk Dittmann dirk.dittmann@gmail.com 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.
Am Montag, 30. September 2013, 09:00:19 schrieb James Turner:
On 30 Sep 2013, at 08:47, Dirk Dittmann dirk.dittmann@gmail.com 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
@lists.sourceforge.net
Subject: Re: [Flightgear-devel] GPS - merge request
On 30 Sep 2013, at 08:47, Dirk Dittmann dirk.dittmann@gmail.com
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
On 30 Sep 2013, at 12:29, Eric van den Berg evan_den_b...@hotmail.com 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
On 30 Sep 2013, at 12:29, Eric van den Berg evan_den_b...@hotmail.com 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
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 evan_den_b...@hotmail.com
wrote:The other stuff I asked Dirk to add as it makes our extra500 (GPSS) AP
design a lot easier.
Incidentally
Am Montag, 30. September 2013, 12:52:08 schrieb James Turner:
On 30 Sep 2013, at 12:29, Eric van den Berg evan_den_b...@hotmail.com
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
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.
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
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:
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
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 find
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
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 do,
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
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
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 talk
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 successful
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's
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
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.
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 time symbol
referenced at line 229 and 233
Hey all, I also added time.h 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
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
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 time symbol
referenced at line 229 and 233 in route_mgr.cxx.
Missing header
) : 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: FlightGear developers discussions
Subject: Re: [Flightgear-devel
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 any
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
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
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
where it can
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
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 the
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 seb.mar...@free.frwrote:
Hi,
There is a gps in CVS: $FGROOT/Aircraft/Instruments-3d/zkv500, I mean
an
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
On Tue, Feb 17, 2009 at 9:14 PM, syd adams adams@gmail.com 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 :)
--
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 adams@gmail.com wrote:
I have a silly , non FG question
what does
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
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
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,
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
* 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
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
average though
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
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-20
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 at
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
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 instrument
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
* 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.
* 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
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.
This
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/aircraft.nas.
It
63 matches
Mail list logo
