Maulkin Posted January 5, 2017 Posted January 5, 2017 I set the ILS to a known ILS beacon and confirm that the morse code is heard. The "Needle 2 Flag" is cleared, but that thin needle never points anywhere? How do I get that to work? --Maulkin Windows 10 64-bit - AMD Ryzen 9 5900X @ 3.7 GHz - 32 GB DDR4 3600MHz RAM - EVGA FTW3 RTX 3080 - Asus Crosshair VIII Hero motherboard - Samsung EVO Pro 1 TB SSD - TrackIR 4 Pro - Thrustmaster Warthog - Saitek rudder pedals - Lilliput UM-80/C with TM Cougars
Steph-JJ Posted January 5, 2017 Posted January 5, 2017 Look at this Thread, maybe helpful https://forums.eagle.ru/showthread.php?t=175390 "You want me to fly in the back of a tiny little jet with a crazy fighter pilot who thinks he´s invincible, home in on a SAM site in North Vietnam and shoot it before it shoots me? You´ve gotta be shittin´me!" Captain Jack Donovan
Maulkin Posted January 5, 2017 Author Posted January 5, 2017 Thanks Steph but as far as I could see it was mostly referring to TACAN which is the wide needle. Keep in mind I have read the information in the latest flight manual and I have gone through both the navigation and ILS landing tutorials a few times each. I set the ILS and i can hear the tone but the needle is stuck at the 135 degrees position. Am I missing a mode setting somewhere? --Maulkin Windows 10 64-bit - AMD Ryzen 9 5900X @ 3.7 GHz - 32 GB DDR4 3600MHz RAM - EVGA FTW3 RTX 3080 - Asus Crosshair VIII Hero motherboard - Samsung EVO Pro 1 TB SSD - TrackIR 4 Pro - Thrustmaster Warthog - Saitek rudder pedals - Lilliput UM-80/C with TM Cougars
Zeus67 Posted January 5, 2017 Posted January 5, 2017 Thanks Steph but as far as I could see it was mostly referring to TACAN which is the wide needle. Keep in mind I have read the information in the latest flight manual and I have gone through both the navigation and ILS landing tutorials a few times each. I set the ILS and i can hear the tone but the needle is stuck at the 135 degrees position. Am I missing a mode setting somewhere? Check the HSI mode knob. "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." "The three most dangerous things in the world are a programmer with a soldering iron, a hardware type with a program patch and a user with an idea."
Pikey Posted January 5, 2017 Posted January 5, 2017 Isn't the thin needle just for VOR navigation which is shared from the same transceiver? I've never expected it to move for ILS, ILS is something I only observe through the HUD. If im tuned to a VOR station then the needle moves as expected. ___________________________________________________________________________ SIMPLE SCENERY SAVING * SIMPLE GROUP SAVING * SIMPLE STATIC SAVING *
Maulkin Posted January 5, 2017 Author Posted January 5, 2017 Thanks Pikey I was just starting to suspect that and test it out. I'll give that a shot. --Maulkin Windows 10 64-bit - AMD Ryzen 9 5900X @ 3.7 GHz - 32 GB DDR4 3600MHz RAM - EVGA FTW3 RTX 3080 - Asus Crosshair VIII Hero motherboard - Samsung EVO Pro 1 TB SSD - TrackIR 4 Pro - Thrustmaster Warthog - Saitek rudder pedals - Lilliput UM-80/C with TM Cougars
Frederf Posted January 6, 2017 Posted January 6, 2017 It's just for VOR and I think the ground controlled intercept which isn't modeled. The thin needle has nothing to do with ILS.
firmek Posted January 7, 2017 Posted January 7, 2017 It's just for VOR and I think the ground controlled intercept which isn't modeled. The thin needle has nothing to do with ILS. Correct, it works with VOR - which if I'm correct there are as much as 4 VOR stations on Caucasus map. Easy way to test it is with Kutaisi 113.60. As for confusion regarding ILS, I think it's fully justified. First, the freq. is set using ILS know - ok, this is a minor thing. Setting a correct ILS frequency while in range of the ILS transmitter clears the warning flag from HSI. What's most important however is that manual states that HSI NAV mode works with both, VOR and ILS. Page 104: "NAV (main INS/VOR navigation mode): In this mode, the HSI connects with the INS and displays waypoint navigation information along with bearing to selected VOR/ILS station." F/A-18, F-16, F-14, M-2000C, A-10C, AV-8B, AJS-37 Viggen, F-5E-3, F-86F, MiG-21bis, MiG-15bis, L-39 Albatros, C-101 Aviojet, P-51D, Spitfire LF Mk. IX, Bf 109 4-K, UH-1H, Mi-8, Ka-50, NTTR, Normandy, Persian Gulf... and not enough time to fully enjoy it all
Maulkin Posted January 7, 2017 Author Posted January 7, 2017 Thanks Firmek! Now that I know what to look for I found the other three: Mineralnye Vody : 117.1 Krasnodar : 115.8 Tbilisi : 113.7 It's gratifying to finally verify that I can get the thin needle to work. :) --Maulkin Windows 10 64-bit - AMD Ryzen 9 5900X @ 3.7 GHz - 32 GB DDR4 3600MHz RAM - EVGA FTW3 RTX 3080 - Asus Crosshair VIII Hero motherboard - Samsung EVO Pro 1 TB SSD - TrackIR 4 Pro - Thrustmaster Warthog - Saitek rudder pedals - Lilliput UM-80/C with TM Cougars
firmek Posted January 7, 2017 Posted January 7, 2017 I'm glat to hear that I could help just a bit. However, the question about ILS remains open. If yes, then there should be a bug report, if not manual should be updated. F/A-18, F-16, F-14, M-2000C, A-10C, AV-8B, AJS-37 Viggen, F-5E-3, F-86F, MiG-21bis, MiG-15bis, L-39 Albatros, C-101 Aviojet, P-51D, Spitfire LF Mk. IX, Bf 109 4-K, UH-1H, Mi-8, Ka-50, NTTR, Normandy, Persian Gulf... and not enough time to fully enjoy it all
Frederf Posted January 7, 2017 Posted January 7, 2017 Every single NTTR TACAN is a VORTAC (VOR-TACAN) so you can test Mirage VOR on something like 23 different stations. On Caucasus there are other types of station. Hexagon = VOR Hexagon with box = VOR-DME Hexagon with hollow ears = TACAN Hexagon with filled ears = VORTAC With VORTAC if you know the channel there is a table to look up the VOR frequency. All VORTACs have DME. When you input an ILS frequency into the VOR-ILS panel the HSI thin needle should not point to anything. If there is any bug it is the HSI needle 2 orange flag changing to valid since there is non valid needle 2 indication. In normal airplanes ILS and VOR are two separate radio panels and one might dial in a VOR and an ILS on their respective panels and use both signals simultaneously. The Mirage is a queer beast in that it uses a single panel for both systems and intelligently switches behavior based on the frequency entered (ILS and VOR frequency ranges don't overlap). And so one must choose to use VOR or ILS but never at the same time. ILS consists of localizer, glideslope, and marker signals. There is no "beacon" to point to. The entirety of the ILS indications show up on the ADI with the LOC and GS needles as well as the flashing marker light in the corner. The HSI is not involved.
Maulkin Posted January 15, 2017 Author Posted January 15, 2017 ILS consists of localizer, glideslope, and marker signals. There is no "beacon" to point to. The entirety of the ILS indications show up on the ADI with the LOC and GS needles as well as the flashing marker light in the corner. The HSI is not involved. I dont see any flashing light? Corner of what? --Maulkin Windows 10 64-bit - AMD Ryzen 9 5900X @ 3.7 GHz - 32 GB DDR4 3600MHz RAM - EVGA FTW3 RTX 3080 - Asus Crosshair VIII Hero motherboard - Samsung EVO Pro 1 TB SSD - TrackIR 4 Pro - Thrustmaster Warthog - Saitek rudder pedals - Lilliput UM-80/C with TM Cougars
Maulkin Posted January 15, 2017 Author Posted January 15, 2017 Every single NTTR TACAN is a VORTAC (VOR-TACAN) so you can test Mirage VOR on something like 23 different stations. On Caucasus there are other types of station. Hexagon = VOR Hexagon with box = VOR-DME Hexagon with hollow ears = TACAN Hexagon with filled ears = VORTAC With VORTAC if you know the channel there is a table to look up the VOR frequency. All VORTACs have DME. Can you give some examples? I am only seeing the 4 VOR (hexagon) beacons, but the only other symbols I am seeing on the map is the TACAN (which VOR/ILS will not work with..but that is why I have TACAN so that is covered separately), a rectangle symbol (for example the one near Krasnodar-Center 840.0MHz MB Chan 40) and the fuzzy symbols which I think are NDB's. I dont see any"hex with a box" or "hex with filled ears". That being said the VOR/ILS on the Mirage is very limited when it comes to the range of frequency values so, for example, I cannot set it to the frequency of that rectangles or the fuzzy symbols I referred to because they are much too high. --Maulkin Windows 10 64-bit - AMD Ryzen 9 5900X @ 3.7 GHz - 32 GB DDR4 3600MHz RAM - EVGA FTW3 RTX 3080 - Asus Crosshair VIII Hero motherboard - Samsung EVO Pro 1 TB SSD - TrackIR 4 Pro - Thrustmaster Warthog - Saitek rudder pedals - Lilliput UM-80/C with TM Cougars
Frederf Posted January 16, 2017 Posted January 16, 2017 (edited) Page 63 of manual, ADI, item #4 "Marker light" St. George VOR is a VOR-DME station. Note the hexagon enclosed within the square. Nellis TACAN is a TACAN station only. Notice the symbol carefully that the 3 squares are hollow and not filled in black. Boulder City VORTAC is both a VOR station and a TACAN together. Notice the symbol has black filled-in boxes. For example McCarraan VORTAC operates TACAN services on 116X (1140 MHz, 1203 MHz) but also VOR services on 116.9 MHz. And sure enough if you tune the ILS-VOR panel to 116.9 the needle points to the station. The VOR range is 108.0 to 118.95 Mhz. ILS localizers are 108.1 through 111.95 (odd 100 kHz values, 50 kHz increment). The rectangles are RSBN stations which are specialized (Soviet ~900 Mhz). The fuzzy stations are lower frequency NDBs being in the range 190-1750 kHz (0.19 to 1.750 MHz). Both of these systems are not Mirage-compatible. One bug that this uncovers is that the DME component of TACAN should provide range to the St. George station when you set the set to 23X (and of course the instrument mode to TACAN). Also it is also probably a bug that when in Cv mode (true compass) that the VOR needle is not being corrected to show the true bearing (both relative and absolute) to station. Edited January 16, 2017 by Frederf
Maulkin Posted January 16, 2017 Author Posted January 16, 2017 Ah ok I think I misunderstood you. I was looking for a light that remained lit when a valid ILS station was selected. The light you are referring to only lights up when you fly over an inner/outer marker (along with an 'M' on the HUD) --Maulkin Windows 10 64-bit - AMD Ryzen 9 5900X @ 3.7 GHz - 32 GB DDR4 3600MHz RAM - EVGA FTW3 RTX 3080 - Asus Crosshair VIII Hero motherboard - Samsung EVO Pro 1 TB SSD - TrackIR 4 Pro - Thrustmaster Warthog - Saitek rudder pedals - Lilliput UM-80/C with TM Cougars
Recommended Posts