|
|
Post by Wathose on Jun 18, 2020 11:49:20 GMT
Hello,
since the 2006 update I have an issue with the DMN and DMS DME at Munich Airport. When I enter the coverage range (approximately 20 NM) the reading on my ND is a value around 2000 NM. Frequency is correctly set to 115 respectively 116. Is that an error in the database or can I fix it on my own?
Thank you
|
|
|
|
Post by niksan29 on Jun 18, 2020 12:44:49 GMT
Hello! Which sim do you use? And your plane? Primarily, try using any of the default aircraft  P/S I checked all three containers NVX06010.BGL(for FSX\P3D1-4\P3D5) which contain Munich (DMS), range and frequency are equal 25nm\115.00 MHz, probably a problem with only your aircraft.. The only thing you need to additionally check: the range(but it’s not because of this, your problem), since in another source of navigation information a different range is indicated 40nm, I hope Herve knows the right option  |
|
|
|
Post by Wathose on Jun 18, 2020 13:30:15 GMT
I am using P3D v4.5 and the FSLABS A320. I also checked it with a default plane. When I am at the runway in EDDM (approximately 1 NM vfrom DMN) I get a reading of 2938 NM in the default plane..
I really have no plan..
|
|
|
|
Post by Wathose on Jun 18, 2020 13:44:29 GMT
Also had a try with the Navaid Package unistalled. DMN and DMS show the right indications. But of course thousand of other Navaids are missing/wrong without this correction files.
And thanks for your help!
|
|
|
|
Post by niksan29 on Jun 18, 2020 13:57:02 GMT
I also checked DMN 116.00 MHz(from Navaid Package) for P3D 4.5 , no problem, max range 25nm... But in sim range really 2938 NM  I will look at it further, thanks P/S P3DV5\Aerosoft A318:  --- but if set it in the right nav radio package it works fine: 
|
|
|
|
Post by Wathose on Jun 18, 2020 14:12:35 GMT
Oh, okay. So im glad being not the only one having that strange behaviour. I would really appreciate if you keep me up to date below this post and let me now if a fix is available. Thank you very much!
|
|
|
|
Post by Wathose on Jun 18, 2020 16:12:15 GMT
News: Tuning in DMS 115.0 results in recieving CAM VOR (listenning to the morse code was the key to find that out). Maybe CAM contains an error concerning the range
|
|
|
|
Post by niksan29 on Jun 18, 2020 17:17:13 GMT
anyway the problem is in the NVX06010.BGL container from navaid package, but upon examination I do not see a problem, range are equal 25nm... when returning the default container, the problem disappears, it looks like something is wrong in the structure  need help from Herve, I'm sure he will answer soon |
|
|
|
Post by Herve Sors on Jun 18, 2020 23:37:20 GMT
There's no problem with CAM TACAN range (defined in P3DV4/5 as a TACAN + a DME on 115.00) that is set to 130 nm and whose coordinates are OK. DMS dme range is set to 25 nm. I don't know exactly what is this "coverage range" setting you're talking about. Is it something that is part of the FMC display? In such a case there could be a calculation problem here. The fact the problem disappear with default NVX06010 is probably due to the fact DMS is on another frequency in P3DV4 (108.60). It has been corrected in P3DV5
Note that CAM and DMS are 210 nm from each other (less than 130+25 as defined in updated database). Standard VOR receiver shouldn't receive CAM while at EDDM but may be your integrated FMC works differently
I do not receive CAM in FSX while at EDDM (but, in FSX, there's no TACAN part for CAM record, only a DME). I do not have P3DV4 but I will test it on P3DV5 ASAP when back home with a standard aircraft
Also note there has been no change in DMS and CAM ranges and coordinates in 2006 so it is a bit curious, you just had the problem on last cycle. Any other change in your aircraft software? I really don't know what this 2398 means! Problem may be linked to the way the aircraft FMC interprets BGL data, at least if it uses them (there's 2 records for TACANs one is a DME record and the other is a TACAN record that normally is only used by military aircrafts that have a TACAN gauge). I will check a possible misreading due to some kind of interference with the TACAN record but I don't think it can explain the problem in a non-military aircraft)..
More later on when I will have check a few other points
|
|
|
|
Post by Herve Sors on Jun 19, 2020 0:39:38 GMT
Later on. Just for a test. Could you replace the NVX06010.bgl file with this one www.aero.sors.fr/beta/NVX06010.bgland let me know if it changes something I just change the range of the TACAN part of the CAM tacan, nothing else |
|
|
|
Post by niksan29 on Jun 19, 2020 4:08:28 GMT
Just for a test. I just change the range of the TACAN part of the CAM tacan, nothing else Sorry Herve, a problem with other navigation aids: DMN 116.00 MHz and DMS 115.00 MHz(I also replaced the file from you and there are no changes), the problem is definitely not in the aircraft, this problem also arises in the aircraft stock:
 I really have no ideas, I compared the stock files and from the navaid package and they are absolutely identical except for the range: stock 60\navaid package 25. P\S Perhaps some kind of dme with a similar frequency at a distance of about 2900 miles from us has an incorrect range? i will check others only dme. + oops ... i checked a few only dme all over the world, this happens everywhere(in this example region: EF other values)   Herve, we will wait for you to have more time for analysis, thx! |
|
|
|
Post by Herve Sors on Jun 19, 2020 7:25:12 GMT
Ok fine analysis that will permit me to check DME only compilation process although it has not changed since a long and nobody mentioned a problem here!
What I see on your pictures (2939 and 3720 nm are measured distances to tuned navaid facility, here on NAV1)? Correct?
Curiously doesn't happen in FSX
Will have a look
Hervé
|
|
|
|
Post by Herve Sors on Jun 19, 2020 8:09:42 GMT
Ok. I confirm problem with these DMEs only occur in P3DV4 (and may be V5..to be tested). Coding of DME only navaids flags is strictly identical to that of stock navaids. The only difference in P3DV4 and V5 is that TACAN records are included for TACANs and VORTACs (these records do not exist in FSX and P3Dv1, only since P3Dv2). I found 9 TACAN and VORTAC navaids with a frequency of 113.70 (ANT in Finland). One is at 3726 NM (OTT). A definitive answer could be obtained with a DME without any tacan worldwide on the same frequency
Could you test LRD (Lahr in Germany) on 108.05. There's no tacan on this frequency anywhere
I cannot release 2007 (normally it should have been today..until this problem is solved)
Hervé
|
|
|
|
Post by niksan29 on Jun 19, 2020 8:42:15 GMT
Yes! Could you test LRD (Lahr in Germany) on 108.05. There's no tacan on this frequency anywhere unfortunately the problem is there:  |
|
|
|
Post by Herve Sors on Jun 19, 2020 9:05:59 GMT
Ok..this will be a difficult one then :-(
What is the result if you just replace the NVX06010.bgl file with the stock P3DV5 one ? Keep all other ones and only test LRD
Any chance also to test it on P3DV4?
|
|
I will look at it further, thanks 
