BMS 4.34 Documents correction report
-
To introduce a little pint of humor here, it’s very fortunate that the tabs names were changed…
Otherwise, the first minute of this video would have been a premonition of 4.34 in 4.33
-
Hmm…. Do all these errors mean I shoulda held off on ordering the manuals from Lulu :scared:
I just blew almost £180 !
-
Hmm…. Do all these errors mean I shoulda held off on ordering the manuals from Lulu :scared:
I just blew almost £180 !
Never. They’re collector now.
-
mm…. Do all these errors mean I shoulda held off on ordering the manuals from Lulu
Should the manual be 2 pages, maybe
buth here so far we have about 5-6 errors in more than 1500 pages, and I’d say quite not so important errors.
So you’re fine. The manuals won’t be corrected for a while anyway -
Emergency Checklist Page 06:
MFDS RFWD FAIL = Left MFD inoperative
MFDS LFWD FAIL = Right MFD inoperativeThese two need to be swapped:)
Edit RD [Fixed]
-
Emergency Checklist Index
Ground Emergencies
Main Generator Failure ( ground ) ……20
Its not on Page 20, its Page 9
Edit RD [Fixed]
-
checklists
The page numbering of the checklists appears to no longer start at 0. This change makes it hard to print just the changed pages, although with how much has changed it’s not really a problem. Hopefully page counts can remain 1 indexed in future updates, especially if the changes are only to a few pages, to ease reprinting
The table of contents doesn’t match up with the page numbers, for example, “Checklists Main Volume” contents has “Verify Checks” on page 2, they’re now on page 3. Also, it no longer shows page as 1/16, 2/16 etc just 1, 2…
Edit RD [Fixed]
–----------------KTO_AIP_434 on page 49 states BMS 4.33 rather than 4.44
Edit RD [Fixed]
-
Good Day, All!
It’s amazing to have IFF in BMS 4.34, Dev team, Thank you for everything you done for it! we like it.
But we found something inconsistency with the manual describing about LIT and AUD feedback of M4 interrogation.
According to 4.34’s TO-BMS1F-16CM-1.pdf : “LIT only provides a visual cue when interrogated, no matter the answer. AUD sounds the aural cue only when the jet is unable to answer the Mode 4 interrogation correctly. Setting it to AUD is therefore recommended, as you want to be warned when this happens.”
“OUT: no feedback at all (the default option).
• LIT: visual feedback when interrogated with the 4 symbol highlighted on the UFC CNI page whenever your jet is interrogated in Mode 4.
• AUD: an audio tone will be played in addition to the visual signal (LIT) if your jet is interrogated in Mode 4
and the interrogation key does not match your key.”But yesterday in fact we found LIT M4 symbol highlighted only when interrogated by M4 and interrogation matched my key. if it didn’t match, it was not highlighted.
So that’s a situation we think is not like the manual said “no matter the answer”Second question is about the IFF emergency:
I switched IFF MASTER Knob to EMERG , the Emergency code for mode 1 is “70” so I let my human wingman change the M1 scan code to 70 for interrogating me. But he said no answer. So i am wondering if the IFF emergency is just an eyecandy or we had some mistakes?
Thanks!
-
Good Day, All!
It’s amazing to have IFF in BMS 4.34, Dev team, Thank you for everything you done for it! we like it.
But we found something inconsistency with the manual describing about LIT and AUD feedback of M4 interrogation.
According to 4.34’s TO-BMS1F-16CM-1.pdf : “LIT only provides a visual cue when interrogated, no matter the answer. AUD sounds the aural cue only when the jet is unable to answer the Mode 4 interrogation correctly. Setting it to AUD is therefore recommended, as you want to be warned when this happens.”
“OUT: no feedback at all (the default option).
• LIT: visual feedback when interrogated with the 4 symbol highlighted on the UFC CNI page whenever your jet is interrogated in Mode 4.
• AUD: an audio tone will be played in addition to the visual signal (LIT) if your jet is interrogated in Mode 4
and the interrogation key does not match your key.”But yesterday in fact we found LIT M4 symbol highlighted only when interrogated by M4 and interrogation matched my key. if it didn’t match, i was not highlighted.
So that’s a situation we think is not like the manual said “no matter the answer”Second question is about the IFF emergency:
I switched IFF MASTER Knob to EMERG , the Emergency code for mode 1 is “70” so I let my human wingman change the M1 scan code to 70 for interrogating me. But he said no answer. So i am wondering if the IFF emergency is just an eyecandy or we had some mistakes?
Thanks!
BMS has the correct function for LIT and AUDIO.
The document will be corrected.
As for the emergency transponders, all works fine. M1 70 and M3 7700 interrogations work as expected for transponders set to EMERG.
Could you guys make a video ? ( Be sure to have the SCAN page visible) -
BMS has the correct function for LIT and AUDIO.
The document will be corrected.
As for the emergency transponders, all works fine. M1 70 and M3 7700 interrogations work as expected for transponders set to EMERG.
Could you guys make a video ? ( Be sure to have the SCAN page visible)Thanks for explanation! We tried EMERG again this morning, that worked!! Maybe we had wrong setup last night. Thank you Dev team!
-
Good to hear!!!
-
KTO AIP, Pohang airbase. ATIS freq is 127.4 (as on airport diagram); but is listed as 108.7 on the TCN+ILS approach charts.
Edit RD [Fixed] -
Only a small one:;)
TO-BMS1F-16CM-34-1-1
Markpoint Description Big X and small x on Page 87 different than in Picture (Fig 51) on Page 94
-
In -1 page 151
text reads: With the C&I switch in C&I all IFF settings are changed through the UFC (Up Front Controller) pages.
should that not be: With the C&I switch in UFC all IFF settings are changed through the UFC (Up Front Controller) pages.
?
hope it helps
greetings Snowman
Edit RD [Fixed]
-
On the Carrier Case 1 recovery training mission, the Enterprise approach freq. is 265.100 as indicated in the mission doc., but when the mission begins, 269.5 is already tuned at the UHF radio, and curiously it works OK with a correct reply from approach control.- When I tuned the apropiate freq 265.100 I had no response, and worse, when I returned to 269.5 couldnt contact anymore with the carrier
-
How do you the frequency when you enter the mission?
The frequency is not readily visible in the pit when you enter the mission, and since training scripts indeed sets the frequency 265.1, and since I just tested I am happy to report that the TE sets 256.1 in Com1 and all works fine
Here’s the proof
Once int eh TE, hit DCS return, ICP COm 1 and the pit will show this:
The only reason why the frequency wouldn’t be right is that the training script didn’t run correctly
-
Training manual - page 11. First sentence duplicated. See pic.
Edit RD [Fixed]
-
@Red:
How do you the frequency when you enter the mission?
The frequency is not readily visible in the pit when you enter the mission, and since training scripts indeed sets the frequency 265.1, and since I just tested I am happy to report that the TE sets 256.1 in Com1 and all works fine
Here’s the proof
Once int eh TE, hit DCS return, ICP COm 1 and the pit will show this:
http://www.ravico.com/ST/BMS_434/picture/hornet_case1.pngThe only reason why the frequency wouldn’t be right is that the training script didn’t run correctly
OK, The confusion was that when the mission begins, for some reason, 265.1 is already tuned at the scratch pad, but the active freq is 256.1
-
Still don’t get it Soldano. 256.1 is not active. As showed in the picture, the correct and set frequency is 265.1. the simple fact that the carrier approach controller responds is ample proof
-
Dash -34
1.4.4.2.1 Enhanced Search Display (ESD) pg.57When a target is tail/low aspect (including near beam targets at 80” right/left) the indication will be pointing up from the search target.
Should it be 80° (as in the preceding sentence)?