Please consider whether the snotty supercilious response you have just
given is conducive to encouraging others to help.
This project is only going to grow and will need all the help it can get
at a variety of levels.
Your attitude will do nothing to assist there.
I humbly apologise for not pickin
On 11 Sep 2009, at 06:15, Ron Jensen wrote:
> ICAO Annex 10 Volume 1 gives a great amount of information on the nav
> radio system in general. Chapter 3 would be a good read for anyone
> working on the nav radio code. There is an online version here:
>
> http://www.scribd.com/doc/5509183/Annex1
On Thu, 2009-09-10 at 16:03 -0700, John Denker wrote:
> 2) There is no doubt that there is frequency pairing for
>collocated VOR/DME. The pairing scheme for DME/VOR,
>DME/MLS, and DME/ILS/MLS are documented starting on
>page 3-100 of ICAO Annex 10 Volume 1 "Aeronautical
>Communica
Sorry , I was not reading closely enough ...
On Thu, Sep 10, 2009 at 1:27 PM, Martin Spott wrote:
> syd adams wrote:
>
> > I know , it's wikipedia , but it gives a short explanation of the VOR
> -DME
> > pairing ...
>
> I think the pairing of a DME with a VOR is unchallenged. People
> (including
OK, so I guess that was entirely my fault on not tuning the DME to the
DME on the NDB-DME station. Blame Atlas for that! :D
Sorry for starting such an OT discussion :P
> On 09/10/09 14:11, willie wrote:
>
>>> I think the pairing of a DME with a VOR is unchallenged. People
>>> (including me) are
On 09/10/09 14:11, willie wrote:
>> I think the pairing of a DME with a VOR is unchallenged. People
>> (including me) are doubtful about the pairing of a DME with an NDB,
> Here's a real-world discussion showing that they really do exist.
> http://www.pprune.org/archive/index.php/t-77933.html
It
Martin Spott wrote:
> syd adams wrote:
>
>> I know , it's wikipedia , but it gives a short explanation of the VOR -DME
>> pairing ...
>
> I think the pairing of a DME with a VOR is unchallenged. People
> (including me) are doubtful about the pairing of a DME with an NDB,
>
> Martin.
Here's
syd adams wrote:
> I know , it's wikipedia , but it gives a short explanation of the VOR -DME
> pairing ...
I think the pairing of a DME with a VOR is unchallenged. People
(including me) are doubtful about the pairing of a DME with an NDB,
Martin.
--
Unix _IS_ user friendly - it's just
On 9 Sep 2009, at 21:28, Atadjanov Daniyar wrote:
> Just tested NDB freqs "problem" - everything work good. Sorry for
> panic.
That's good news indeed! I was worried I'd broken the spatial searches.
Thanks for checking, and please let me know if you see other strange
behaviour.
James
---
08.09.09, 21:47, "James Turner" :
> BTW, for NDBs, FlightGear *should* be picking the closest NDB with the
> matching frequency - exactly as MSFS. If that's not what you're
> seeing, that's a bug, and likely my fault. Please let me know a
> suitable test location and NDB frequencies / idents
http://en.wikipedia.org/wiki/Distance_measuring_equipment
I know , it's wikipedia , but it gives a short explanation of the VOR -DME
pairing ...
On Tue, Sep 8, 2009 at 1:01 PM, James Turner wrote:
>
> On 8 Sep 2009, at 20:01, Torsten Dreyer wrote:
>
> >> There ara a lot NDB-DME in /data/Nava
Do I have to do so with NAV1/2? I don't seem to find any way to tune
the KI226 DME without using the radio dialog/using the NAV radios.
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial.
On 8 Sep 2009, at 20:01, Torsten Dreyer wrote:
>> There ara a lot NDB-DME in /data/Navaids/nav.dat
>> ...
>> 2 -42.72933900 170.95621900146 310 1000.0 HK HOKITIKA
>> NDB-DME
>> ...
>>
>> http://wikimapia.org/9701833/Hokitika-NDB-DME
> No doubt about this. But I don't know of any
On Tue, 8 Sep 2009, James Turner wrote:
> This:
>
>> Just want to ask developers: is it possible to make ILS/LOC
>> establishing radius more realistic?
>>
>> What we have now in FG? You can establish ILS/LOC anywere you are if
>> you are in n-kilometers over airport. In real life ATC asks pilots:
> 2009/9/8 Torsten Dreyer :
> > NDB-DME
>
> There ara a lot NDB-DME in /data/Navaids/nav.dat
> ...
> 2 -42.72933900 170.95621900146 310 1000.0 HK HOKITIKA NDB-DME
> ...
>
> http://wikimapia.org/9701833/Hokitika-NDB-DME
No doubt about this. But I don't know of any NDB receiver (which
2009/9/8 Torsten Dreyer :
> NDB-DME
There ara a lot NDB-DME in /data/Navaids/nav.dat
...
2 -42.72933900 170.95621900146 310 1000.0 HK HOKITIKA NDB-DME
...
http://wikimapia.org/9701833/Hokitika-NDB-DME
--
---
WBR, Vadym.
---
Then it's my fault :D I don't know how to get DME frequencies, Atlas
doesn't tell me that...
Thanks for the information!
>> One thing I would like, if it's not already avaliable: Being able to
>> tune a DME to a NDB-DME. I can't do that in FG, although Atlas
>> reports
>> some NDBs as having D
> One thing I would like, if it's not already avaliable: Being able to
> tune a DME to a NDB-DME. I can't do that in FG, although Atlas reports
> some NDBs as having DME capability.
Huh? As far as I know there are only DME paired to VOR but not NDB. There are
places where DME and NDB might be at t
This:
> Just want to ask developers: is it possible to make ILS/LOC
> establishing radius more realistic?
>
> What we have now in FG? You can establish ILS/LOC anywere you are if
> you are in n-kilometers over airport. In real life ATC asks pilots:
> "Report localizer established" because in
One thing I would like, if it's not already avaliable: Being able to
tune a DME to a NDB-DME. I can't do that in FG, although Atlas reports
some NDBs as having DME capability.
--
Let Crystal Reports handle the reportin
Hi!
Is it possible to fix another bug in navradio (?) system? If runway or the
region has two (or more) NDBs with same frequency, then FG shows only one of
them _everytime_. In real life (as far as i know) NDBs of working runway are
turned on and other NDBs with same freqs are turned off. In MS
James Turner wrote:
>- runways (and taxiways) are initialised with the airport elevation
> instead of a zero elevation in the apt_loader. This is still a poor
> substitute for correct values, but in the absence of source for the
> actual runway elevation profile, it's much better tha
On 7 Sep 2009, at 14:36, dave perry wrote:
> I was wrong about the height being correct. Thought it might be a
> scope
> problem for nav_elev so I tried moving the declaration back to
> navradio.hxx and moving the assignment of a value back into the
> search.
> The search is never called???
On 7 Sep 2009, at 13:00, Curtis Olson wrote:
> You could be seeing the results of nav1 & nav2 interleaved. You
> might try tuning them both in to valid stations and seeing what
> happens.
D'oh, good observation Curt :)
Unfortunately having CVS-uped, my SG and FG won't start - crashes with
James Turner wrote:
> On 6 Sep 2009, at 22:50, dave perry wrote:
>
>
>> The height is correct. It looks like every other call of
>> FGNavRadio::updateWithPower gets the wrong value for nav_elev. Hope
>> this helps find the bug.
>>
>
>
I was wrong about the height being correct. Though
On Mon, Sep 7, 2009 at 3:37 AM, James Turner wrote:
> Thanks Dave, this is almost certainly my fault - and indeed all the
> airports I tested at are very close to sea level elevation.
>
> Very odd that it's alternating from a valid value to zero, I'll dig
> into the code today.
>
>
Dave,
You coul
On 6 Sep 2009, at 22:50, dave perry wrote:
> The height is correct. It looks like every other call of
> FGNavRadio::updateWithPower gets the wrong value for nav_elev. Hope
> this helps find the bug.
Thanks Dave, this is almost certainly my fault - and indeed all the
airports I tested at are
After many tries , deleting navradio , doing make clean , make distclean,I
finally had to delete the FG and SG source and do a new checkout . Now
everything compiles fine .
Another reason I'd love to see CVS gone :)
--
Let
On 6 Sep 2009, at 05:23, syd adams wrote:
> Hello.
>Unless Im doing something wrong , I'm now getting these errors
> trying to compile FG...
>
> navradio.cxx: In member function ‘virtual void
> FGNavRadio::update(double)’:
> navradio.cxx:362: error: ‘struct SGVec3d’ has no member named ‘s
29 matches
Mail list logo
