Switching on UHF radio implemented incorrectly
-
Meantime, I spent 40min yesterday looking at “your issue” trying to reproduce instead of taking this time to continue going forward on my work on DB. …. 40 min wasted. Period.
-
my bad on the enter, 273.525, I entered 520. but the 3rd character doesn’t show anyway?
training manual, mission 1: page 15:
Push COM1 on the ICP and the DED displays the UFC COM1 page.
[…] To enter the manual frequency, enter “27352” in the scratchpad, followed by ENTR.
Note that the last 5 cannot be entered, it does not matter. Remember the Scratchpad is the area between asterisks.It wasn’t volume. the volume knob when pressed doesn’t do anything. is it supposed to?
You need to be more precise, do you mean to ask of there’s a push feature on the volume knob implemented or that when you click the volume knob (left or right?) , it doesn’t move
There is no push feature on the volume knobs, you must be confusing the squelsh button, which has a pushbutton implemented and as Always in that case, it’s said in the dash one if implemented in BMS or not
Dash1, 1.2.1.12, Comms panel, page 25The push function is not implemented in BMS.
As well, on the subject of bkup/UHF. The manual states set to bkup, didnt see where it follows on and says set to UHF, COM1 doesn’t work when in bkup.
Training manual, mission 1: page 14
For the moment simply put the IFF MASTER knob in STBY and rotate the CNI switch from BACKUP to UFC so you can start using the primary onboard systems.
With that done the Up Front Controller comes online and it is suggested that you load up the data cartridge into the system before you set up the radios through the UFC. The DTC contains all the information that was set in mission planning. In real life the pilots carry it with them and load into the DTC receptacle on the right console. In BMS we load the DTC by selecting the DTE page on the MFD and selecting the LOAD button (OSB 3). The sequence of highlights of the OSB has changed so do not worry if it takes longer than before.
The reason we load the DTC before setting the UFC radios is that since the DTC has a comms section, the presets might be different than the ones pre-briefed. If you load the DTC after setting the UFC radios you might not be on the correct frequency anymore. For more information about the data cartridge refer to the DTC section in the BMS-Manual.obviously that should point out where you missed the information in the manual
Maybe You really need to look at your way of reading the manual and get a bit more attention doing it.
everything is in there, repeated and proven. -
Appreciate all the help
-
Now, I’ll steal this thread for some 5mins ,
What about UHF MAIN/BOTH switch (ufc & backup) , how’s that suppose to operate IRL? … Well IMHO that’s not really implemented? *Its not that I miss it , use it, so much (at all ) , just asking beacause I necer figured it out … I cant check that in singelplay,
For what I’ve ‘reckon’ so far , MAIN = only selected freq should be on rec/trans , BOTH = SELected freq & GRD freq muxed ? Correct?
-
Both = Main + listening Guard
Same behavior IRL and In-Game
-
Yes MUX’d.
-
Thanks.
That’s what is confusing. , so on BOTH , you receive both freqs in same time… But when transmit , do you transmit on eg UHF6 an GRD in the same time , whats the logic here?
eg…
MAIN
UHF 6… - receive/transmitBOTH
UHF 6… - receive/transmit
GRD ch. - receive/transmitIs that correct? Or is GRD listen only, on separate circuit. That would mean you receive and transmit on 2 separate freqs in the same time with one UHF radio… I’m not quite sure how radio could do that,…
…on the other hand it could do it with some time div multiplex (similar to frequency hop) , so switching between 2 freqs with some very fast relay many time per second/minute , … in theoryYeah, let’s don’t get too technical… just wanna know is it transmit/receive case in BOTH on both frequencies?
Thanks
–damn AMRAAM ,… you said it before I could ask, you read my mind ,… and to be honest I failed to see Dee-Jay’s “LISTENING ONLY” bah…;)
-
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 :).