ADF and NDB tuning problems

[bkthunder]

Hello. I can't for the life of me tune in to the correct NDB on the F-86. I'm checking against Lino Germany's latest beacon map and also the F10 view.

e.g. I was trying to tune in 740Khz (which is a clear mark on the freq. tape, so not much room for error) and I got a spinning needle and the wrong morse code all the way till I was right on top of it and across.

 

Other stations gave the same result.

 

Any ideas?

 

P.S. I was in MP if that makes any difference...

 

 

EDIT: see post # 7 http://forums.eagle.ru/showpost.php?p=2756173&postcount=7

Edited April 25, 2016 by bkthunder

[Art-J]

In SP the system seems to be working OK, as I've flown tutorial mission without issues. No idea about MP though. Open the kneeboard to double check what frequency You've actually set.

[bkthunder]

I cross checked all the frequencies in all available documents and F10 view.. I'm even thinking the radio is receiving 2 frequencies at the same time, 'cause the morse code is way too long and never matching any chart.

[Art-J]

Where is this 740kHz NDB located?

[bkthunder]

44° 58' 13'' N 41° 06' 56'' E

 

I have tried with others with the same confusing results...

I still have to try in SP, but in MP surely something is off.

[Art-J]

Quite possibly. Will check in SP too, but if other stumbled upon it, sounds like there's some MP related issue here indeed. Can NDB freqs be adjusted in MP anyway??

[bkthunder]

Ok, so I did some testing in SP and it seems to be a bug with the F-86.

 

Testing with Armavir NDB station 740 Khz:

 

UH-1 - correct morse code (VM / ∙∙∙- --) and ADF needle points to the station

L-39C - correct morse code (VM / ∙∙∙- --) and ADF needle points to the station

F-86 - tuned to 740 Khz, received WRONG morse code (AS / ∙- ∙∙∙) and adf needle keeps spinning.

 

I tired to find on the map if there is a beacon with the AS morse code, but couldn't find it from the F10 view. Also checked Lino Germany's beacon list and beacon map to no avail.

 

So, out of 3 aircraft, the F-86 is the only one failing the test in both MP and SP.

I think this is a bug.

[enigma6584]

Ok, so I did some testing in SP and it seems to be a bug with the F-86.

 

Testing with Armavir NDB station 740 Khz:

 

UH-1 - correct morse code (VM / ∙∙∙- --) and ADF needle points to the station

L-39C - correct morse code (VM / ∙∙∙- --) and ADF needle points to the station

F-86 - tuned to 740 Khz, received WRONG morse code (AS / ∙- ∙∙∙) and adf needle keeps spinning.

 

I tired to find on the map if there is a beacon with the AS morse code, but couldn't find it from the F10 view. Also checked Lino Germany's beacon list and beacon map to no avail.

 

So, out of 3 aircraft, the F-86 is the only one failing the test in both MP and SP.

I think this is a bug.

 

Make sure you put this in the "bug reports" thread. :thumbup:

[Art-J]

On the other hand....

 

... I've just put the Sabre on Maykop ramp (quick mission in SP), tuned to 740kHz and the ADF pointed correctly, with correct (VM) morse code clearly audible. That is in the latest stable version of 1.5.3, haven't tested OB one, is that the version You guys have been using on Your server?

[bkthunder]

On the other hand....

 

... I've just put the Sabre on Maykop ramp (quick mission in SP), tuned to 740kHz and the ADF pointed correctly, with correct (VM) morse code clearly audible. That is in the latest stable version of 1.5.3, haven't tested OB one, is that the version You guys have been using on Your server?

 

I'm referring to the latest stable release.

Never tried from the ramp, for sure I couldn't tune it from the air, flying close to it.

Also, it was not a tuning error, because I tried all other frequencies around 740 and they all gave spinning needle and wrong morse code. Besides, 740 is clearly marked on the tape, so unless it's a texture error, I was definitely on 740..

[Art-J]

So I tried an SP air start and indeed, the symptoms You've described appeared right away. I don't know enough about mission editor, though, to tell why 740 NDB works OK in cold start, while doesn't work in air start missions.

[71st_AH Rob]

I'm referring to the latest stable release.

Never tried from the ramp, for sure I couldn't tune it from the air, flying close to it.

Also, it was not a tuning error, because I tried all other frequencies around 740 and they all gave spinning needle and wrong morse code. Besides, 740 is clearly marked on the tape, so unless it's a texture error, I was definitely on 740..

 

Out of curiosity I tried 740, never had occasion to tune it before, from ramp at Kutaisi MP, stable release and it works as expected. Will try in the Mig-15 maybe this evening.

[bkthunder]

So I tried an SP air start and indeed, the symptoms You've described appeared right away. I don't know enough about mission editor, though, to tell why 740 NDB works OK in cold start, while doesn't work in air start missions.

 

740 was just an example I took because it's clearly marked on the freq. tape.

Other NDBs give exactly the same result: wrong morse and no tracking.

[Art-J]

That would mean the Sabre's ADF generally doesn't wok in air started missions (haven't checked hot-on-runway ones), both in SP and MP.

[bkthunder]

Well, i gave it another go in MP from ramp start, same as before, wrong morse from the ground or the air. What's more is I am almost certain the morse code is overlapping and changing every time, because each time I hear it changes and it gets more confusing...

Anyway lsnfrom my side, it's definitely a problem that only the f-86 has.

I would mark it as a bug and hopefully bst will have a look..

[justinm11]

Try the Batumi NDB. I know that one works properly in both air and and ramp starts, SP and MP. Unless something has changed in the latest patch, I've used that NDB in all the above situations. I have noticed some of the above issues though. I was trying to test out different NDBs to create NDB approach plates for some of the bigger airports and I struggled to get alot of them to work. Sometimes I could tune an ndb, track to it, visually fly over where the beacon should have been and the beacon would still be tracking straight ahead, while a different ndb would track without issue. I put it down to my chart being out of date, since all the morse identifiers seemed off. I found a few NDBs that worked properly, but I wasn't looking for this type of error. I do know that Batumi works without issue in the sabre though its hard to tune. Listen for the ident and all will be well. Maybe that could be used as a benchmark for proper functioning? If you want to test it, search down the forums and try my approach that I put out. That will confirm proper functioning of the beacon.

[71st_AH Rob]

I have tried to replicate your error but can't, all NDB that I try are correct.

 

I know it was asked before but I think your answer was ambiguous, but have you verified that you are tuned to the correct frequency using page one of the kneeboard, it displays the current setting of the AN/ANR-6 radio compass which can be hard to determine in the cockpit and if you are too close to another freq you could be getting a miss-reading.

 

Also, the canopy must be closed for it to function correctly, I assume that it was?

Edited May 1, 2016 by 71st_AH Rob

[Art-J]

Testing in SP, continued. Previously, I cold not get ADF to work in airstart missions, with bugged behaviour exactly as described by Bkthunder. Cold start worked OK. Today I checked a couple of NDBs around MinVody airbase (including infamous 740kHz one) and with exception of 907, which has different code than marked on Lino Germany's map, all were detected correctly in cold-, ramp- and airstart missions. The problem seems to have dealt with itself (?).

 

The only thing that changed in my game a few days ago was reassigning some controls for the F-86 (even though none of them were radio or nav related). Bkthunder, it might be good idea to do a controls cleanup for You Sabre and check if it helped.