Re: [Flightgear-devel] navradio
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/Annex10-ICAO Cheers Ron, that's a good link. Regards, James -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] navradio
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 picking up on the difference between colocation and frequency pairing. It would have been far better to have simply ignored my useless contribution but you took it upon yourself to issue a pointless smackdown. Luckily, I have been lurking here for a while and know that your attitude is not truly representative. Others may not be so fortunate. John Denker wrote: 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 shows no such thing. The topic of this sub-thread is NDB/DME frequency pairing, not NDB/DME collocation. 1) There is no doubt that VOR and DME can be collocated. 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 Communications. 3) There is no doubt that NDB and DME can be collocated. 4) There is considerable doubt that any real-world ground station implements frequency pairing for NDB/DME. No evidence of such pairing has been adduced. 5) There is considerable doubt that any real-world cockpit instrument implements frequency pairing for NDB/DME. No evidence of such pairing has been adduced. If NDB/DME frequency pairing exists, perhaps somebody would be kind enough to tell us what the pairing scheme is, and/or give an example of a real-world instrument that implements such pairing. Otherwise we will continue to assume that the lack of any such pairing within FGFS is entirely realistic. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Best Regards Willie Fleming -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] navradio
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 selective about who its friends are ! -- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] navradio
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 a real-world discussion showing that they really do exist. Probably not too common in US/ W Europe, I'll grant you that. http://www.pprune.org/archive/index.php/t-77933.html BTW this took 30 secs Googlage. -- Best Regards Willie Fleming -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] navradio
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 shows no such thing. The topic of this sub-thread is NDB/DME frequency pairing, not NDB/DME collocation. 1) There is no doubt that VOR and DME can be collocated. 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 Communications. 3) There is no doubt that NDB and DME can be collocated. 4) There is considerable doubt that any real-world ground station implements frequency pairing for NDB/DME. No evidence of such pairing has been adduced. 5) There is considerable doubt that any real-world cockpit instrument implements frequency pairing for NDB/DME. No evidence of such pairing has been adduced. If NDB/DME frequency pairing exists, perhaps somebody would be kind enough to tell us what the pairing scheme is, and/or give an example of a real-world instrument that implements such pairing. Otherwise we will continue to assume that the lack of any such pairing within FGFS is entirely realistic. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] navradio
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 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 shows no such thing. The topic of this sub-thread is NDB/DME frequency pairing, not NDB/DME collocation. 1) There is no doubt that VOR and DME can be collocated. 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 Communications. 3) There is no doubt that NDB and DME can be collocated. 4) There is considerable doubt that any real-world ground station implements frequency pairing for NDB/DME. No evidence of such pairing has been adduced. 5) There is considerable doubt that any real-world cockpit instrument implements frequency pairing for NDB/DME. No evidence of such pairing has been adduced. If NDB/DME frequency pairing exists, perhaps somebody would be kind enough to tell us what the pairing scheme is, and/or give an example of a real-world instrument that implements such pairing. Otherwise we will continue to assume that the lack of any such pairing within FGFS is entirely realistic. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] navradio
Sorry , I was not reading closely enough ... On Thu, Sep 10, 2009 at 1:27 PM, Martin Spott martin.sp...@mgras.netwrote: 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 selective about who its friends are ! -- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] navradio
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 Communications. 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/Annex10-ICAO Thanks, Ron -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] navradio
08.09.09, 21:47, James Turner zakal...@mac.com: 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 to reproduce the problem, and I'll take a look. Hi, James. Just tested NDB freqs problem - everything work good. Sorry for panic. Daniyar -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] navradio
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 -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] navradio
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??? I'll also keep looking at this and let you know if I find the problem. I've just committed at least one fix - the problem actually predates my navradio change, but it also my fault. I broke the elevation data for ILS/LOC navids when I cleaned up the 'align localiser with runway centerline' logic. The problem is that runways don't have an elevation specified (in apt.dat). I've actually fixed this in two ways: - alignLocaliserWithRunway uses the original, specified elevation for the navid - 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 than assuming zero. Regards, James -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] navradio
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 than assuming zero. Does it help to add the actual threshold elevation from our current Scenery and to store that in the respective .threshold.xml file in the same way as we're storing the elevation for each ILS ? Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] navradio
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 MSFS: ADF is showing the direction to the nearest NDB with selected frequency (the easiest way i think). Let's fix this and make FG's radio-subsystem more realistic :) Thanks, Daniyar -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] navradio
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 real life you can establish it only when you are on base/final. and this: On 8 Sep 2009, at 17:55, Atadjanov Daniyar wrote: 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 MSFS: ADF is showing the direction to the nearest NDB with selected frequency (the easiest way i think). Both come under the category of 'problems with the nav radio code'. The second in particular I hope to work on 'soon' - I don't know nearly enough about modelling radio reception to improve the code (or make judgements about its quality) to address the first issue. You may notice I've been careful in my emails to state the areas I'm working on, precisely because there's many overlapping problems. The GS needle indications are wrong in the aircraft - no amount of improvements or advanced modelling in the navradio code will matter, if the panels aren't handling the output deflection sanely. Similarly, I've been cleaning up the code so that changes to the behaviour are hopefully cleaner and easier in the future. 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 to reproduce the problem, and I'll take a look. Regards, James -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] navradio
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 reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] navradio
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 the same place, but I think you have to tune boths frequencies individually. Torsten -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] navradio
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 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 the same place, but I think you have to tune boths frequencies individually. Torsten -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] navradio
2009/9/8 Torsten Dreyer tors...@t3r.de: 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. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] navradio
2009/9/8 Torsten Dreyer tors...@t3r.de: 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 is also known as ADF) that automatically tunes the DME frequency. Most modern receiver for VOR do this, like the KX165, but that is due to a link between the DME-receiver and the NAV-receiver. As far as i know, you have to tune the DME part of your NDB-DME manually and the cited line of nav.dat is unusable for the DME part, because the DME channel is missing. Torsten -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] navradio
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. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] navradio
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: Report localizer established because in real life you can establish it only when you are on base/final. and this: On 8 Sep 2009, at 17:55, Atadjanov Daniyar wrote: 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 MSFS: ADF is showing the direction to the nearest NDB with selected frequency (the easiest way i think). Both come under the category of 'problems with the nav radio code'. The second in particular I hope to work on 'soon' - I don't know nearly enough about modelling radio reception to improve the code (or make judgements about its quality) to address the first issue. James, this patent (and those it references) may be an assistance to you: http://www.freepatentsonline.com/3663734.html Note that the listed patent and those it refers to are now expired and are now in the public domain. g. -- Proud owner of F-15C 80-0007 http://www.f15sim.com - The only one of its kind. ScarletDME - The red hot Data Management Environment A Multi-Value database for the masses, not the classes. http://www.scarletdme.org - Get it _today_! -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] navradio
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 zakal...@mac.com wrote: 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 NDB receiver (which is also known as ADF) that automatically tunes the DME frequency. Most modern receiver for VOR do this, like the KX165, but that is due to a link between the DME-receiver and the NAV-receiver. As far as i know, you have to tune the DME part of your NDB-DME manually and the cited line of nav.dat is unusable for the DME part, because the DME channel is missing. There's also this entry: 13 -42.72933900 170.95621900146 11750 1000.0 HK HOKITIKA NDB-DME which is the DME part of the NDB-DME. As Torsten notes, none of the receivers in FG at present do pairing of NDB-DME frequencies, and I have no idea if any real world equipment can do this - or if there's even a defined pairing scheme. You can happily tune your ADF to 310KHz, and a DME receiver to 117.5MHz, and either/both should work, but there's no link between the two other than their geographical co-location. Again, if anyone with more knowledge of such facilities wants to comment, please do. James -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] navradio
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 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. Thanks again, James -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] navradio
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 could be seeing the results of nav1 nav2 interleaved. You might try tuning them both in to valid stations and seeing what happens. Regards, Curt. -- Curtis Olson: http://baron.flightgear.org/~curt/ -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] navradio
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. 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??? I'll also keep looking at this and let you know if I find the problem. 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. Thanks again, James -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] navradio
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 memory corruption issues as the scenery / ground cache comes up. I didn't think any of the commits recently looked that 'big', but I'll roll back to a few days ago (when I was running fine). James -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] navradio
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 ‘sg’ navradio.cxx:362: error: ‘struct SGVec3d’ has no member named ‘sg’ navradio.cxx:363: error: ‘struct SGVec3d’ has no member named ‘sg’ make[3]: *** [navradio.o] Error 1 Ive tried compiling SG and FG starting from ./autogen.sh onward , but no luck. I'll try deleting the source for both and do a fresh checkout , but thought I'd mention the problem just in case. cheers It looks like something hasn't updated right - Mathias recently did some updates to SGVec3d (in SimGear), and corresponding updates in various client FG files, including navradio. On trunk, those .sg() references should now say .data() I believe. I'd check your navradio.cxx file is updating 'correctly' - sticky revisions, merge conflicts, etc. Assuming you don't have any edits to it, deleting the file and 'cvs up' should work. Regards, James -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] navradio
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 Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
