Sharkku Posted March 28, 2017 Posted March 28, 2017 (edited) I noticed that the deflection of the VOR course needle is wrong (=reversed). I haven't been able to find any comments on this, has anyone else noticed it? I noticed this being east of Mineralniye Vody flying westbound towards Mineralniye Vody VOR. I dial in 270 on the OBS, and the needle is centered and I get a TO flag, upwards pointing white triangle. But when I deviate to the right, the needle also deflects to the right. It should deflect to the left, indicating that I am to the right of my desired radial. Given that the needle represents the radial, and my position is represented by the small circle in the middle of the CDI. Edited March 28, 2017 by Sharkku
Razor18 Posted March 28, 2017 Posted March 28, 2017 This update supposedly fixed the issue for Huey: https://forums.eagle.ru/showpost.php?p=2994487&postcount=42 Is your update status beyond this?
Sharkku Posted March 28, 2017 Author Posted March 28, 2017 Yeah, I'm always on the latest... 1.5.6.1938 at the moment. Shoot, maybe I somehow managed to skip the needed files? I thought it wasn't possible to have anything but all the updated files using the auto-updater... Or is it a regression? Is it working correctly for you?
ESA Dodo Posted April 10, 2017 Posted April 10, 2017 Yesterday I was trying to complete a radio navigation in Nevada and I notice that erroneous behaviour again. Previously I have noticed it using Tibilisi VOR. On course to the station with the TO flag, I made a deliberate right turn to check it out, and the CDI came also to the right. So it is not fixed. On course to the station. 030º Course selected, TO flag shown and needle centered. Right turn in the vicinity of the VORTAC station. Needle deflects the wrong side. And that is the way it should be:
ESA Dodo Posted April 10, 2017 Posted April 10, 2017 Meanwhile it is fixed, a way to work with it is to select the reverse course. You will have an inverse TO-FROM indication, but at least the needle will show the correct deviation.
Razor18 Posted April 10, 2017 Posted April 10, 2017 If you have to work around, then it is definitely NOT fixed, is it? :music_whistling:
ESA Dodo Posted April 10, 2017 Posted April 10, 2017 Obviously not. At least as far as I can check and unless I have missed something in my updates.
Recommended Posts