awacs does not answer
-
Dear colleagues, I have problems with the AWACS, I tune in to UHF channel 6. I can ask you but you don’t answer me even though there is an AWACS nearby. It happens to me in this field, in Korea or in the Balkans I do not have this problem, if there is AWACS they answer me. Greetings and thank you
-
@jack333 ,
Mideast 128 is a BIIIIIGGG Theater…and there are restrictions on range in communications with AWACS. I think max range to AWACS from you of over 200 (or is it 250, I can’t quite recall) NM will result in AWACS not hearing you. You’ll get an answer if you are within range and on the right frequency.
From the BMS Technical Manual pg 46:"4.33 introduced a couple of new features to the 4.32 radios. One big addition is that, as with real life radios, we are now limited in range. Radio range (including IVC) is now Line of Sight dependant. As you get further away from the other radio the quality and volume of the transmission will degrade until you can not understand, then no longer hear the other person’s transmission. The other change is the possibility of using sidetone (if your hardware supports it), for an even more authentic audio experience."
So, get a bit closer to the Eyeball, and you’ll be able to chat with the nice lady/man in the airplane with the rotating dome.
Regards,
Tomcattwo
(VoiceClone) -
@jack333 said in awacs does not answer:
even though there is an AWACS nearby
-
Check that the frequency on UHF channel 6 is correct. The briefing will have a comm ladder with the awacs tactical frequency. The comm frequencies need to be loaded into the dtc for channel 6 to work, otherwise it will need to be entered manually.
-
@TeeSquare said in awacs does not answer:
Check that the frequency on UHF channel 6 is correct. The briefing will have a comm ladder with the awacs tactical frequency. The comm frequencies need to be loaded into the dtc for channel 6 to work, otherwise it will need to be entered manually.
UHF 6 is not the awacs frequency, it is your package tactical frequency, which is the first flight of the package default UHF 6 for all the flights. This is where the AWACS is if there is one. Default comm plan sets that without error.
-
the briefing should tell if there is an allocated AWACS to support of UHF6…
You should also check the AWACS sunrise, sundown and potential distance to your area of operation.
-
Thanks for the answers
-
Out of curiosity, does anyone know what the max distance to AWACS is to get a response? Assuming both AWACS and ownship is at, say, 20.000 ft.
The docs have no mention of it …
-
@jayb said in awacs does not answer:
Out of curiosity, does anyone know what the max distance to AWACS is to get a response? Assuming both AWACS and ownship is at, say, 20.000 ft.
The docs have no mention of it …
Does someone know the approx distance to AWACS in which AWACS will be able to respond and of course monitor the airspace I am in ?
-
Since this question arises quite often, I did a little test an went into TE Builder:
I set an E-3 AWACS over Kuwait and me in a Viper in the west, first finding out were I approximately could hear AWACs and were not. Then I flew the remaining route, trying “Request picture” every few seconds. When I found the exact point, I repeated a few times, “End mission”, save the TE, went into “Edit” and measured the distance by shifting waypoints over my and the AWACS’ position (you see the distance between them in UI).
And the answer is: almost exactly 300nm at angels 20 on a sunny day.
Remember, I did the test with E-3, not knowing values from other aircraft.Someone could complain that @jayb could have done this by himself, but using the TE editor feels too much like running DCS
Though, BMS has a much more comfortable UI. -
@Atze-0 You are quite right, the question comes up often but is very rarely answered. I did run a few tests in ME128 (not as thorough as yours though!) and found that I lost AWACS around 280-300 nm distance.
I was hoping for a developer response since there must be some underlying formula/calculation which determines the distance. I don’t know if you have ever seen any response from the BMS team on this, there is certainly no mention in the current documentation. But I suppose that our findings are close enough that we can conclude that ~300nm is the maximum distance
Thanks for doing the tests and for publishing your results !
-JayB