Switching on UHF radio implemented incorrectly
-
Only receive on Guard for both, you will not transmit
-
The off-squelch-guard switch would be used to quickly change to transmit over guard.
-
MAIN
UHF 6… - receive/transmitBOTH
UHF 6… - receive/transmit
GRD ch. - receive**/transmit => Nope!** -
The off-squelch-guard switch would be used to quickly change to transmit over guard.
Neat trick ! … suppose it effects UFC also
-
Not entirely related to the original topic, but it’s linked to the start-up, so I hope it’s okay I put this here:
The manual says this:
The channel knob selects one of the 19 presets available. In BMS those presets are automatically set with the Falcon BMS.cfg config line: set g_bInitBUPfromDTC 1.
By default the panel selects channel 6, but this is also configurable in the [your callsign].ini file COMMS section.The last sentence caught my attention, as the question whether or not we could change that default BUP UHF came up within the squadron yesterday, so I went into Callsign.ini and found this:
[COMMS]
Comm1=1
Comm2=15
TACAN Channel=75
ILS Frequency=11030
ILS CRS=356
TACAN Band=0
TACAN Domain=0
Comm1_Comment=(open)
Comm2_Comment=(open)No mention of BUP Comms, no option in WDP, and I’m unable to find a config entry in any of the manuals, so I’m guessing / hoping the actual config line didn’t make it into the ini or manuals, but is known by the devs?
-
interesting question
I can’t remember honestlyout of the blue did you try BUP_UHF_1=254300 for instance?
I have no idea if this would work. I remember it was discussed but It seem I forgot to correct it from the manual or complete the information with an how to.
And I checked the tech manual structure of the callsign ini chapter and it’s not there either -
Yeah, let’s don’t get too technical… just wanna know is it transmit/receive case in BOTH on both frequencies?
Look at the photo, there is a Transmitter, a Main Receiver, and a Guard Receiver
-
@Red:
interesting question
I can’t remember honestlyout of the blue did you try BUP_UHF_1=254300 for instance?
I have no idea if this would work. I remember it was discussed but It seem I forgot to correct it from the manual or complete the information with an how to.
And I checked the tech manual structure of the callsign ini chapter and it’s not there eitherYears ago.
-
Yeah, but that’s 8 years old, back in 4.32. We had 4.33 and 4.34, both may have changed it
Knowing me I never state stuff in manuals without backing, it always is a consequence from either testing on my own or statement from devs, or both.
But as I said in this case I really can’t remember from where that bit originated. Might also be a misunderstanding on my part as well -
Absolutely, that’s the meaning of “years ago”, there was no irony meant :).