Jump to content

CDU Divert frequencies and F10 map ATC showing 4.250. How to interpret this?


coolts

Recommended Posts

It's actually 4.25MHz. Those old radios used those frequencies.

 

You have to think like a programmer to see how this can happen. Batumi airfield has lots of ATC frequencies almost certainly stored as an array. Say the original array back when the system was programmed was freqTable = [111MHz, 222Mhz, 33MHz] for the VHF, UHF, and FM frequencies. So the A-10 divert page was programmed to pull a specific element out of that array to display on the page text. So how do you link to the frequency you want if you want to show VHF AM? You display.Batumi.freqTable select 0. This picks out the 0th element of the Batumi.freqTable array which is the first one. That's how the A-10 worked and it pulled the correct frequency for years.

 

But what happens if someone changes the freqTable array, say to [4.25, 111, 222, 33]? The A-10 is now pulling the 0th element of the array just like it was programmed but the 0th element is the wrong piece of data. The same programming written years ago that used to pull the right data is pulling the wrong data because the reference data changed.

  • Like 1
Link to comment
Share on other sites

It's actually 4.25MHz. Those old radios used those frequencies.

 

You have to think like a programmer to see how this can happen. Batumi airfield has lots of ATC frequencies almost certainly stored as an array. Say the original array back when the system was programmed was freqTable = [111MHz, 222Mhz, 33MHz] for the VHF, UHF, and FM frequencies. So the A-10 divert page was programmed to pull a specific element out of that array to display on the page text. So how do you link to the frequency you want if you want to show VHF AM? You display.Batumi.freqTable select 0. This picks out the 0th element of the Batumi.freqTable array which is the first one. That's how the A-10 worked and it pulled the correct frequency for years.

 

But what happens if someone changes the freqTable array, say to [4.25, 111, 222, 33]? The A-10 is now pulling the 0th element of the array just like it was programmed but the 0th element is the wrong piece of data. The same programming written years ago that used to pull the right data is pulling the wrong data because the reference data changed.

 

So its just needs someone to adjust the array order? That's like 1/2 an hours work. Surely.

[sIGPIC][/sIGPIC]

i7 9700k | 32gb DDR4 | Geforce 2080ti | TrackIR 5 | Rift S | HOTAS WARTHOG | CH PRO Pedals

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...