Esteemed BMS Community,
I have been delighted to work with the Dev team (particular thanks to Micro & Tiago) to try and dig a little deeper into how LINK 16 currently works within BMS. As a result of this engagement pilots will find some additional clarification within the updated BMS documentation.

This post builds upon what was put into the BMS documentation to (hopefully) help pilots understand what LINK 16 is, how it is implemented in BMS and what LINK 16 is or is not showing the pilot (and why).

Of course, LINK 16 is new to BMS as of 4.37u4 and there is still a lot of development going on to add even more capability to this fantastic addition to our sim. So I will keep this post updated as any substantive changes are made.

The first part of this post is a set of notes regarding LINK 16 and how it is implemented in BMS, as well as clarifying some key terminology. After this, I have created three pictorial ‘scenarios’ which are designed to articulate what a pilot should expect to see from LINK 16 under certain ‘situations’.

Scenario 1: Shows what to expect when both PPLI and SURV air track data is available.
Scenario 2: Shows what to expect when there is no SURV air track data available, but PPLI air track information is available.
Scenario 3: Shows the impact of the unlikely situation where the pilot has access to SURV air track data but no PPLI air track information.

Each scenario is deliberately identical, portraying 14 different situations (labelled A-N), with a description explaining what the pilot (‘ownship’) would expect to see (or not see) in that situation, and why.

I hope this post will help clarify how LINK 16 works in BMS 4.37u4. In the future, I hope to produce a video that talks through these scenarios and situations as I appreciate some people may prefer that type of content instead of ‘RTFM’ (Read the Flight Manual / Read The Forum Material).

Feedback is very much welcome, if you have any questions, please post below and I will attempt to answer (or if I don’t know, I am sure the Dev team can comment).

1) What Is LINK 16?
• At is most basic level, LINK 16 is a means for various LINK 16 enabled NATO platforms to share or view positional and contact data to enhance situational awareness under the right conditions.

2) A brief, incomplete and oversimplified history of LINK 16.
• TADIL-J (Tactical Digital Information Link J), refers to the system of standardized J-series messages known by NATO as LINK 16.
• LINK 16 is the NATO standardization of the JTIDS system.
• JTIDS (Joint Tactical Information Distribution System) is an L band Distributed Time Division Multiple Access (DTDMA) network radio system used by the United States Department of Defence and their allies to support data communications needs, principally in the air and missile defence community.
• MIDS (Multifunctional Information Distribution System) is the successor to JTIDS.
• MIDS ‘communicates’ with other nodes using ‘J format’ ‘messages’ (originating from TADIL J).
• TADIL is no longer an official US Department of Defence term. Instead, it has been replaced by the generic term Tactical Data LINK (TDL). Despite this, “TADIL” is a legacy holdover and still used in the vernacular.

3) Key Terminology:
• Improved Data Modem (IDM): IDM was designed in the late 70’s before JTIDS or LINK 16 was available. The F-16’s IDM enhances communication capabilities for both Command and Control purposes and data transfer between up to eight aircraft. The IDM facilitates transmission of various types of data, including sensor data, positional updates between aircraft and sharing certain tactical data such as mark points or air to air contacts. Even if limited in features compared to JTIDS/MIDS systems, it still has a valuable role to play in BMS 4.37u4, especially while LINK 16 is not fully implemented.
• Joint Data Net (JDN): An interconnected network of JTIDS/MIDS based systems which links air and missile defence Command and Control and weapons systems across L16 capable forces.
• Net Participation Group (NPG): FC and MC channels are part of dedicated NPG’s. Each channel and its number define what data can be exchanged on that channel. If you create a package for example, all LINK 16 capable aircraft of this package will have the same FC and MC (because one AWACS controller will be responsible for this package).
• Channel: A channel can have different NPGs. For example a channel number (e.g. 56) could have a Mission and Fighter-to-Fighter NPGs. So, in the MIDS/JTIDS, we can set the MC as ‘56’ and the FC also as ‘56’.
• Mission Channel (MC): Mission Channel (MC): (Automatically set by BMS), can be manually set between 0 and 127. Responsible for exchanging information with AWACS or other Command and Control platform.
• Fighter Channel (FC): (Automatically set by BMS), can be manually set between 0 and 126. Responsible for exchanging information between fighter aircraft (tracking and lock information not implemented yet)…
• Special Channel (SC) : Establishes the subnet for the SEAD NPG and identification information. [Not Currently Implemented]
• Flight STNS: Source Track Number. Contains all members of your own flight by default, can be manually changed between 00000 and 77776 (excluding 00077, 00167, 00177 and 07777).
• Team STNS: Source Track Number. Contains next four aircraft in your package by default, can be manually changed between 00000 and 77776 (excluding 00077, 00167, 00177 and 07777).
• Donor: [Partially Implemented]. For situational awareness during a mission, pilots may want to monitor aircraft or targets reported by aircraft that aren’t part of their flight or team. These aircraft, known as donors, can be designated during mission planning (via the Data Cartridge), or selection or deselection can be managed in the cockpit through the LINK 16 DNR page on the DED. Note: The ability to assign Donor’s from 2d and 3d has been implemented in BMS. But the effect is currently limited to seeing that Donor’s positional data.
• PPLI: Air Precise Participant Location Identification is a message transmission from LINK 16 air participants, furnishing network participation status, identification details, positional data and navigation information. It encompasses the voice call sign, position coordinates (latitude/longitude), altitude, course, IFF codes, air platform type (e.g. fighter, bomber, attack) and air platform activity (such as engaging, investigating etc.). PPLI air tracks are shared between aircraft sharing the same NPG.
• SURV: This message serves to share air track data, predominantly disseminated by a Command and Control agency. It comprises details regarding exercise/non-exercise tracks including; track number, strength, position, speed, course, identity (such as pending, unknown, assumed friend, friend, neutral, suspect, hostile), air platform type (generic categories like fighter, bomber, attack etc.) and specific air platform type (e.g. F15, F16 Mig29 etc.).

4) Crucial Range Information
• Currently in BMS the AWACS radar has a maximum detection range of ~135nm. This does not mean everything within 135nm will always be detected, many things impact probability of detection.
• Currently the AWACS has a maximum transmission range of SURV air track L16 data of ~400nm (currently a fairly academic point as the AWACS can only detect contacts out to ~135nm).
• PPLI air tracks are shown in the HSD/FCR/HUD/HMCS to a range of ~150nm from the pilots aircraft.
• SURV air tracks are shown in the HSD/FCR/HUD/HMCS to a range of ~100nm from the pilots aircraft.

5) Detection & Classification Sequence & Limitations of L16
• Currently in BMS only Command and Control aircraft (E3 Sentry and E2 Hawkeye) can provide SURV air track information.
• Flight lock lines, secondary fighter air target tracks and AMRAAM shot lines are not currently implemented.
• The detection of aircraft is conditional on the AWACS being able to sense the contact. This is not only a function of the AWACS notational detection range (up to ~135nm). An AWACS ability to sense a contact can also be impacted by the radar cross section of the contact, whether it is jamming, if it is terrain masking, lost in radar ground clutter (not currently modelled in BMS) or even certain atmospheric conditions (not currently modelled in BMS). The LINK 16 picture should never be considered to be showing all air contacts at all times.
• The classification of contacts is solely managed by Command and Control agencies.
• New contacts will typically follow this sequence when being classified:
• Classified as ‘Detected, Unknown/Assumed Friend/Pending’.
• Classified as ‘Suspect/Assumed Hostile /Pending’.
• Classified as either ‘Friendly’, ‘Neutral’ or ‘Hostile’.

SCENARIO 1

A) Flight members, set as ‘Flight STNS’ in DTC and sharing ownship’s Net Participation Group, within 150nm PPLI display range: Shown on HSD/FCR/HUD/HMCS (PPLI air track).

B) Flight member, set as ‘Flight STNS’ in DTC and sharing ownship’s Net Participation Group, within 150nm PPLI display range: Shown on HSD/FCR/HUD/HMCS (PPLI air track).

C) Package Member, set as ‘Team STNS’ in DTC and sharing ownship’s Net Participation Group, within 150nm PPLI display range: Shown on HSD/FCR/HUD/HMCS (PPLI air track).

D) Friendly, and sharing ownship’s Net Participation Group, within 150nm PPLI display range: Shown on HSD/FCR/HUD/HMCS (PPLI air track).

E) Friendly, detected by AWACS, not sharing ownship’s Net Participation Group or not L16 capable and not within 100nm SURV display range: Not shown on HSD/FCR.

F) Hostile, detected by AWACS and classified ‘Hostile’, not within 100nm SURV display range: Not shown on HSD/FCR.

G) Hostile, not detected by AWACS (out of AWACS 135nm detection range): No SURV air track generated.

H) Hostile, within AWACS detection range and within 100nm SURV air track display range, but not detected by AWACS (bandit could be jamming, stealth or terrain masking): No SURV air track generated.

I) Hostile, detected by AWACS and classified ‘Hostile’, within 100nm SURV display range: Shown on HSD/FCR (SURV air track).

J) Friendly, not detected by AWACS (out of AWACS 135nm detection range) and not sharing ownship’s Net Participation Group or not L16 capable: No SURV air track generated.

K) Friendly, detected by AWACS, either not sharing ownship’s Net Participation Group or not L16 capable, within 100nm SURV display range: Shown on HSD/FCR (SURV air track).

L) Hostile, not detected by AWACS (out of AWACS 135nm detection range): No SURV air track generated.

M) Hostile aircraft, detected by AWACS, but currently classified as ‘Suspect/Assumed Hostile/Pending’, within 100nm SURV display range: Shown on HSD/FCR (SURV air track).

N) Hostile aircraft, detected by AWACS, but currently classified as ‘Unknown/Assumed Friend/Pending’, within 100nm SURV display range: Shown on HSD/FCR (SURV air track).

SCENARIO 2

A) Flight members, set as ‘Flight STNS’ in DTC and sharing ownship’s Net Participation Group, within 150nm PPLI display range: Shown on HSD/FCR/HUD/HMCS (PPLI air track).

B) Flight member, set as ‘Flight STNS’ in DTC and sharing ownship’s Net Participation Group, within 150nm PPLI display range: Shown on HSD/FCR/HUD/HMCS (PPLI air track).

C) Package Member, set as ‘Team STNS’ in DTC and sharing ownship’s Net Participation Group, within 150nm PPLI display range: Shown on HSD/FCR/HUD/HMCS (PPLI air track).

D) Friendly, and sharing ownship’s Net Participation Group, within 150nm PPLI display range: Shown on HSD/FCR/HUD/HMCS (PPLI air track).

E) Friendly, no AWACS so not detected and either not on ownship’s Net Participation Group or not L16 capable: No PPLI or SURV air track generated.

F) Hostile, no AWACS so not detected: No SURV air track generated.

G) Hostile, no AWACS so not detected: No SURV air track generated.

H) Hostile, no AWACS so not detected: No SURV air track generated.

I) Hostile, no AWACS so not detected: No SURV air track generated.

J) Friendly, no AWACS so not detected and either not on ownship’s Net Participation Group or not L16 capable: No PPLI or SURV air track generated.

K) Friendly, no AWACS so not detected and either not on ownship’s Net Participation Group or not L16 capable: No PPLI or SURV air track generated.

L) Hostile, no AWACS so not detected: No SURV air track generated.

M) Hostile, no AWACS so not detected: No SURV air track generated.

N) Hostile, no AWACS so not detected: No SURV air track generated.

SCENARIO 3

A) Flight members, no PPLI available, detected by AWACS, within 100nm SURV display range: Shown on HSD/FCR (SURV air track).

B) Flight member, no PPLI available, not detected by AWACS (out of AWACS 135nm detection range): No SURV air track generated.

C) Package Member, no PPLI available, detected by AWACS, within 100nm SURV display range: Shown on HSD/FCR (SURV air track).

D) Friendly, no PPLI available, detected by AWACS, within 100nm SURV display range: Shown on HSD/FCR (SURV air track).

E) Friendly, detected by AWACS, not within 100nm SURV display range: Not shown on ownship HSD/FCR.

F) Hostile, detected by AWACS, not within 100nm SURV display range: Not shown on HSD/FCR.

G) Hostile, not detected by AWACS (out of AWACS 135nm detection range): No SURV air track generated.

H) Hostile, within AWACS detection range and within 100nm SURV air track display range, but not detected by AWACS (bandit could be jamming, stealth or terrain masking): No SURV air track generated.

I) Hostile, detected by AWACS and classified ‘Hostile’, within 100nm SURV display range: Shown on HSD/FCR (SURV air track).

J) Friendly, not detected by AWACS (out of AWACS 135nm detection range) and no PPLI available : No SURV air track generated.

K) Friendly, detected by AWACS, no PPLI available, within 100nm SURV display range: Shown on HSD/FCR (SURV air track).

L) Hostile, not detected by AWACS (out of AWACS 135nm detection range): No SURV air track generated.

M) Hostile aircraft, detected by AWACS, but currently classified as ‘Suspect/Assumed Hostile/Pending’, within 100nm SURV display range: Shown on HSD/FCR (SURV air track).

N) Hostile aircraft, detected by AWACS, but currently classified as ‘Unknown/Assumed Friend/Pending’, within 100nm SURV display range: Shown on HSD/FCR (SURV air track)

Re: Helping To Understand LINK 16

Time Stamp: 09:00(UK), 06.07/24.

All,
For those that read the original post over the last 12 hours or so, I have made a couple of slight editorial changes.

Change log:
Nothing substantive, a few additions for clarity, addressing some typos and re-ordering the examples, but if you read the original before the time of this post you might want to quickly look through the material before the examples (examples remain unchanged, except the ordering).

I hope this will be the last time I mess around with the original post, except in the event of needing to clarify something, address any errors spotted or update the pack to address changes within BMS.

I will continue to post messages such as these in this thread with any relevant change log to help pilots understand when things change, what has changed and why.

UPDATED
Hi everyone,
I have recently purchased a stream deck and I have now finished my profile (there may be incremental updates in the future). Feel free to use if its helpful for you.

NB: This is for the 8x4 (32 button device).

Please ensure you read the ‘read me’ file in the zip, especially with reference to Key files.

Known issues:

• You must use one of the key files provide (or update your key file using the key presses indicated in the Sream Deck profile, or fully map your own profile using the images in the ICP folder).
• F1 and F2 push buttons for IVC in 2d do not seem to work, but I dont know why. [Still trying to fix].
• Discord mute button only works when discord screen is ‘live’ and only when in PPT mode. [Still trying to fix].
• The panel does not automatically ‘switch’ the switches back to their default (cold start) positions. YOU MUST DO THIS MANUALLY before your fly (or when you shut down). [Not possible to fix ATM as far as I know - looks longingly at over worked dev team…]
• The R-AUX panel is blank. I would love to have images/pull outs that come from the game into the appropriate windows to show things like fuel gauge, FTIT, RPM, Standby compass heading etc etc, but I do not think this is currently possible in BMS (I know it is for DCS, but they use LUA to do all kinds of magic). Who knows, some time soon perhaps (longinglook at dev team intensifies…)

Happy flying.

DropBox Download Link:
https://www.dropbox.com/s/0fm6pp7vv5wrx7n/BMS.zip?dl=0

Images From ‘Map’ Of Profile

Hi eveyone- I just saw this on 320 Sim Pilots channel (if you fly Airbus on MSFS then you probably know him).

I am sad to report that it does not appear to be compatible with BMS (yet?).

My question(s) are:

• Is it possible for it to work with BMS? My assumption is that in principle it should work as TIR works in BMS/MSFS/DCS so why wouldn’t this work in BMS?

• Is compatibility something the BMS dev team need to ‘enable’ or is it the hardware designers at Tobii? Or does someone from the BMS dev team need to reach out to Tobii to ‘remind them that BMS is a thing’ and get them to add the support?

• Ultimately, could we see this supported in BMS any time soon?

As someone who has no interest in VR I have been on the lookout for ‘what comes next’ after TIR5 - and I suspect this is it. Eye tracking, sure it seems useful, but for me I am more interested in loosing the cables and pro clip ‘baggage’ that is needed for TIR5 to work. It seems this thing is just a sensor you attach on your monitor and off you go. This seems so much more efficient and I (could) finally get rid of my wired headset as well (I have always gone wired as whats the point in wireless headsets when you have TIR5 strapped to it…).

If you use TIR and are not bothered about VR, would you want to see this supported in BMS?

Happy flying everyone

-S

@tiag said in Helping To Understand LINK 16:

Hi Tiag,
Thanks for this, I will address what I can over the weekend.

However, be aware the following lines are taken from the BMS documentation, so if wrong please could you provide the exact wording needed (you may also wish to update the documents)?

“SURV: …(such as pending, unknown, assumed friend, friend, neutral, suspect, hostile), IFF codes, air platform type (generic categories like fighter, bomber, attack etc.) a…”

• This is from the 31-1-1, P254 and the training manual p.281

“Mission Channel (automatically set by BMS), can be manually set between 0 and 127-> is responsible for exchanging information with AWACS or other C2 platforms (SURV air track data).”

• This is from the 31-1-1, P254 and the training manual p.281

Thanks @jayb

Have read the thread - looks like it is my issue, but might as well be written in Klingon - no idea what is being said ‍️

nice

@MaxWaldorf

Many thanks eveyone.

Solution was to recognise that the height of fog was causing this effect.

To solve, put fog height to the level you want ‘thick’ IFR conditions (I use 5000’) and have cloud layers above that level.

Thanks to all who helped

My Sqn is starting to see this issue, was just about to post a bug report.

As OP says, there is no crash and no bug report - but this is becoming deeply frustrating.

For my part I would love to see a trainer aircraft mod in BMS.

I appreciate its not for operational flying (but the clue for what it is used for is in the title). I think a turbo-prop like the Super Tucano, PC-21 or T6c Texan II would be an amazing addition to BMS, even something like a Grob 120tp would be useful. I know I / 72 Sqn would make immediate use of such an option if it had the right avionics options etc.

Such aircraft would add a lot of flavour and options for Sqns/Wings that want to augment training or dont immediately want to use a 4th Gen aircraft. This would be especially helpful for pilots that are new to flight sims, combat flight sims or multiplayer flying in general.

I think such a mod would need to have modern avionics/HUD etc to be truly worthwhile as a ‘modern’ trainer. I for one would not want to spend my training time squinting down at a barely readable steam gauge in a world of MFDS, HUDs and glass cockpits.

Not being a programmer/developer I know little about how these things are done, but it seems to me the aircraft mod options in BMS are fairly low at the moment vice DCS. I guess that’s the result of BMS only recently opening up the option of having distinct modules and, perhaps, a smaller community than that of DCS from which to draw programmers/developers that would be keen to take on such a project.

As has been mentioned above, there seems to be a plethora of options in MSFS, but anything in MSFS is likely to be cost prohibitive for many given the limited use of the option beyond training. DCS has great options; Super Tucano and Hawk are free mods which while not perfect, are surprisingly good for a community MoD and entirely suitable for lead in training for something like an F16.

The things I would give for such trainer aircraft in BMS. I guess, with no financial incentive for coding such mods, we are at the mercy of those kind souls with the skills and time available to do such a mod in BMS (like the ones in DCS).

One can hope/dream.
-S

For my part I would love to see a trainer aircraft mod in BMS.

I appreciate its not for operational flying (but the clue for what it is used for is in the title). I think a turbo-prop like the Super Tucano, PC-21 or T6c Texan II would be an amazing addition to BMS, even something like a Grob 120tp would be useful. I know I / 72 Sqn would make immediate use of such an option if it had the right avionics options etc.

Such aircraft would add a lot of flavour and options for Sqns/Wings that want to augment training or dont immediately want to use a 4th Gen aircraft. This would be especially helpful for pilots that are new to flight sims, combat flight sims or multiplayer flying in general.

I think such a mod would need to have modern avionics/HUD etc to be truly worthwhile as a ‘modern’ trainer. I for one would not want to spend my training time squinting down at a barely readable steam gauge in a world of MFDS, HUDs and glass cockpits.

Not being a programmer/developer I know little about how these things are done, but it seems to me the aircraft mod options in BMS are fairly low at the moment vice DCS. I guess that’s the result of BMS only recently opening up the option of having distinct modules and, perhaps, a smaller community than that of DCS from which to draw programmers/developers that would be keen to take on such a project.

As has been mentioned above, there seems to be a plethora of options in MSFS, but anything in MSFS is likely to be cost prohibitive for many given the limited use of the option beyond training. DCS has great options; Super Tucano and Hawk are free mods which while not perfect, are surprisingly good for a community MoD and entirely suitable for lead in training for something like an F16.

The things I would give for such trainer aircraft in BMS. I guess, with no financial incentive for coding such mods, we are at the mercy of those kind souls with the skills and time available to do such a mod in BMS (like the ones in DCS).

One can hope/dream.
-S

@tiag said in Helping To Understand LINK 16:

Hi Tiag,
Thanks for this, I will address what I can over the weekend.

However, be aware the following lines are taken from the BMS documentation, so if wrong please could you provide the exact wording needed (you may also wish to update the documents)?

“SURV: …(such as pending, unknown, assumed friend, friend, neutral, suspect, hostile), IFF codes, air platform type (generic categories like fighter, bomber, attack etc.) a…”

• This is from the 31-1-1, P254 and the training manual p.281

“Mission Channel (automatically set by BMS), can be manually set between 0 and 127-> is responsible for exchanging information with AWACS or other C2 platforms (SURV air track data).”

• This is from the 31-1-1, P254 and the training manual p.281

Re: Helping To Understand LINK 16

Time Stamp: 09:00(UK), 06.07/24.

All,
For those that read the original post over the last 12 hours or so, I have made a couple of slight editorial changes.

Change log:
Nothing substantive, a few additions for clarity, addressing some typos and re-ordering the examples, but if you read the original before the time of this post you might want to quickly look through the material before the examples (examples remain unchanged, except the ordering).

I hope this will be the last time I mess around with the original post, except in the event of needing to clarify something, address any errors spotted or update the pack to address changes within BMS.

I will continue to post messages such as these in this thread with any relevant change log to help pilots understand when things change, what has changed and why.

Esteemed BMS Community,
I have been delighted to work with the Dev team (particular thanks to Micro & Tiago) to try and dig a little deeper into how LINK 16 currently works within BMS. As a result of this engagement pilots will find some additional clarification within the updated BMS documentation.

This post builds upon what was put into the BMS documentation to (hopefully) help pilots understand what LINK 16 is, how it is implemented in BMS and what LINK 16 is or is not showing the pilot (and why).

Of course, LINK 16 is new to BMS as of 4.37u4 and there is still a lot of development going on to add even more capability to this fantastic addition to our sim. So I will keep this post updated as any substantive changes are made.

The first part of this post is a set of notes regarding LINK 16 and how it is implemented in BMS, as well as clarifying some key terminology. After this, I have created three pictorial ‘scenarios’ which are designed to articulate what a pilot should expect to see from LINK 16 under certain ‘situations’.

Scenario 1: Shows what to expect when both PPLI and SURV air track data is available.
Scenario 2: Shows what to expect when there is no SURV air track data available, but PPLI air track information is available.
Scenario 3: Shows the impact of the unlikely situation where the pilot has access to SURV air track data but no PPLI air track information.

Each scenario is deliberately identical, portraying 14 different situations (labelled A-N), with a description explaining what the pilot (‘ownship’) would expect to see (or not see) in that situation, and why.

I hope this post will help clarify how LINK 16 works in BMS 4.37u4. In the future, I hope to produce a video that talks through these scenarios and situations as I appreciate some people may prefer that type of content instead of ‘RTFM’ (Read the Flight Manual / Read The Forum Material).

Feedback is very much welcome, if you have any questions, please post below and I will attempt to answer (or if I don’t know, I am sure the Dev team can comment).

1) What Is LINK 16?
• At is most basic level, LINK 16 is a means for various LINK 16 enabled NATO platforms to share or view positional and contact data to enhance situational awareness under the right conditions.

2) A brief, incomplete and oversimplified history of LINK 16.
• TADIL-J (Tactical Digital Information Link J), refers to the system of standardized J-series messages known by NATO as LINK 16.
• LINK 16 is the NATO standardization of the JTIDS system.
• JTIDS (Joint Tactical Information Distribution System) is an L band Distributed Time Division Multiple Access (DTDMA) network radio system used by the United States Department of Defence and their allies to support data communications needs, principally in the air and missile defence community.
• MIDS (Multifunctional Information Distribution System) is the successor to JTIDS.
• MIDS ‘communicates’ with other nodes using ‘J format’ ‘messages’ (originating from TADIL J).
• TADIL is no longer an official US Department of Defence term. Instead, it has been replaced by the generic term Tactical Data LINK (TDL). Despite this, “TADIL” is a legacy holdover and still used in the vernacular.

3) Key Terminology:
• Improved Data Modem (IDM): IDM was designed in the late 70’s before JTIDS or LINK 16 was available. The F-16’s IDM enhances communication capabilities for both Command and Control purposes and data transfer between up to eight aircraft. The IDM facilitates transmission of various types of data, including sensor data, positional updates between aircraft and sharing certain tactical data such as mark points or air to air contacts. Even if limited in features compared to JTIDS/MIDS systems, it still has a valuable role to play in BMS 4.37u4, especially while LINK 16 is not fully implemented.
• Joint Data Net (JDN): An interconnected network of JTIDS/MIDS based systems which links air and missile defence Command and Control and weapons systems across L16 capable forces.
• Net Participation Group (NPG): FC and MC channels are part of dedicated NPG’s. Each channel and its number define what data can be exchanged on that channel. If you create a package for example, all LINK 16 capable aircraft of this package will have the same FC and MC (because one AWACS controller will be responsible for this package).
• Channel: A channel can have different NPGs. For example a channel number (e.g. 56) could have a Mission and Fighter-to-Fighter NPGs. So, in the MIDS/JTIDS, we can set the MC as ‘56’ and the FC also as ‘56’.
• Mission Channel (MC): Mission Channel (MC): (Automatically set by BMS), can be manually set between 0 and 127. Responsible for exchanging information with AWACS or other Command and Control platform.
• Fighter Channel (FC): (Automatically set by BMS), can be manually set between 0 and 126. Responsible for exchanging information between fighter aircraft (tracking and lock information not implemented yet)…
• Special Channel (SC) : Establishes the subnet for the SEAD NPG and identification information. [Not Currently Implemented]
• Flight STNS: Source Track Number. Contains all members of your own flight by default, can be manually changed between 00000 and 77776 (excluding 00077, 00167, 00177 and 07777).
• Team STNS: Source Track Number. Contains next four aircraft in your package by default, can be manually changed between 00000 and 77776 (excluding 00077, 00167, 00177 and 07777).
• Donor: [Partially Implemented]. For situational awareness during a mission, pilots may want to monitor aircraft or targets reported by aircraft that aren’t part of their flight or team. These aircraft, known as donors, can be designated during mission planning (via the Data Cartridge), or selection or deselection can be managed in the cockpit through the LINK 16 DNR page on the DED. Note: The ability to assign Donor’s from 2d and 3d has been implemented in BMS. But the effect is currently limited to seeing that Donor’s positional data.
• PPLI: Air Precise Participant Location Identification is a message transmission from LINK 16 air participants, furnishing network participation status, identification details, positional data and navigation information. It encompasses the voice call sign, position coordinates (latitude/longitude), altitude, course, IFF codes, air platform type (e.g. fighter, bomber, attack) and air platform activity (such as engaging, investigating etc.). PPLI air tracks are shared between aircraft sharing the same NPG.
• SURV: This message serves to share air track data, predominantly disseminated by a Command and Control agency. It comprises details regarding exercise/non-exercise tracks including; track number, strength, position, speed, course, identity (such as pending, unknown, assumed friend, friend, neutral, suspect, hostile), air platform type (generic categories like fighter, bomber, attack etc.) and specific air platform type (e.g. F15, F16 Mig29 etc.).

4) Crucial Range Information
• Currently in BMS the AWACS radar has a maximum detection range of ~135nm. This does not mean everything within 135nm will always be detected, many things impact probability of detection.
• Currently the AWACS has a maximum transmission range of SURV air track L16 data of ~400nm (currently a fairly academic point as the AWACS can only detect contacts out to ~135nm).
• PPLI air tracks are shown in the HSD/FCR/HUD/HMCS to a range of ~150nm from the pilots aircraft.
• SURV air tracks are shown in the HSD/FCR/HUD/HMCS to a range of ~100nm from the pilots aircraft.

5) Detection & Classification Sequence & Limitations of L16
• Currently in BMS only Command and Control aircraft (E3 Sentry and E2 Hawkeye) can provide SURV air track information.
• Flight lock lines, secondary fighter air target tracks and AMRAAM shot lines are not currently implemented.
• The detection of aircraft is conditional on the AWACS being able to sense the contact. This is not only a function of the AWACS notational detection range (up to ~135nm). An AWACS ability to sense a contact can also be impacted by the radar cross section of the contact, whether it is jamming, if it is terrain masking, lost in radar ground clutter (not currently modelled in BMS) or even certain atmospheric conditions (not currently modelled in BMS). The LINK 16 picture should never be considered to be showing all air contacts at all times.
• The classification of contacts is solely managed by Command and Control agencies.
• New contacts will typically follow this sequence when being classified:
• Classified as ‘Detected, Unknown/Assumed Friend/Pending’.
• Classified as ‘Suspect/Assumed Hostile /Pending’.
• Classified as either ‘Friendly’, ‘Neutral’ or ‘Hostile’.

SCENARIO 1

A) Flight members, set as ‘Flight STNS’ in DTC and sharing ownship’s Net Participation Group, within 150nm PPLI display range: Shown on HSD/FCR/HUD/HMCS (PPLI air track).

B) Flight member, set as ‘Flight STNS’ in DTC and sharing ownship’s Net Participation Group, within 150nm PPLI display range: Shown on HSD/FCR/HUD/HMCS (PPLI air track).

C) Package Member, set as ‘Team STNS’ in DTC and sharing ownship’s Net Participation Group, within 150nm PPLI display range: Shown on HSD/FCR/HUD/HMCS (PPLI air track).

D) Friendly, and sharing ownship’s Net Participation Group, within 150nm PPLI display range: Shown on HSD/FCR/HUD/HMCS (PPLI air track).

E) Friendly, detected by AWACS, not sharing ownship’s Net Participation Group or not L16 capable and not within 100nm SURV display range: Not shown on HSD/FCR.

F) Hostile, detected by AWACS and classified ‘Hostile’, not within 100nm SURV display range: Not shown on HSD/FCR.

G) Hostile, not detected by AWACS (out of AWACS 135nm detection range): No SURV air track generated.

H) Hostile, within AWACS detection range and within 100nm SURV air track display range, but not detected by AWACS (bandit could be jamming, stealth or terrain masking): No SURV air track generated.

I) Hostile, detected by AWACS and classified ‘Hostile’, within 100nm SURV display range: Shown on HSD/FCR (SURV air track).

J) Friendly, not detected by AWACS (out of AWACS 135nm detection range) and not sharing ownship’s Net Participation Group or not L16 capable: No SURV air track generated.

K) Friendly, detected by AWACS, either not sharing ownship’s Net Participation Group or not L16 capable, within 100nm SURV display range: Shown on HSD/FCR (SURV air track).

L) Hostile, not detected by AWACS (out of AWACS 135nm detection range): No SURV air track generated.

M) Hostile aircraft, detected by AWACS, but currently classified as ‘Suspect/Assumed Hostile/Pending’, within 100nm SURV display range: Shown on HSD/FCR (SURV air track).

N) Hostile aircraft, detected by AWACS, but currently classified as ‘Unknown/Assumed Friend/Pending’, within 100nm SURV display range: Shown on HSD/FCR (SURV air track).

SCENARIO 2

A) Flight members, set as ‘Flight STNS’ in DTC and sharing ownship’s Net Participation Group, within 150nm PPLI display range: Shown on HSD/FCR/HUD/HMCS (PPLI air track).

B) Flight member, set as ‘Flight STNS’ in DTC and sharing ownship’s Net Participation Group, within 150nm PPLI display range: Shown on HSD/FCR/HUD/HMCS (PPLI air track).

C) Package Member, set as ‘Team STNS’ in DTC and sharing ownship’s Net Participation Group, within 150nm PPLI display range: Shown on HSD/FCR/HUD/HMCS (PPLI air track).

D) Friendly, and sharing ownship’s Net Participation Group, within 150nm PPLI display range: Shown on HSD/FCR/HUD/HMCS (PPLI air track).

E) Friendly, no AWACS so not detected and either not on ownship’s Net Participation Group or not L16 capable: No PPLI or SURV air track generated.

F) Hostile, no AWACS so not detected: No SURV air track generated.

G) Hostile, no AWACS so not detected: No SURV air track generated.

H) Hostile, no AWACS so not detected: No SURV air track generated.

I) Hostile, no AWACS so not detected: No SURV air track generated.

J) Friendly, no AWACS so not detected and either not on ownship’s Net Participation Group or not L16 capable: No PPLI or SURV air track generated.

K) Friendly, no AWACS so not detected and either not on ownship’s Net Participation Group or not L16 capable: No PPLI or SURV air track generated.

L) Hostile, no AWACS so not detected: No SURV air track generated.

M) Hostile, no AWACS so not detected: No SURV air track generated.

N) Hostile, no AWACS so not detected: No SURV air track generated.

SCENARIO 3

A) Flight members, no PPLI available, detected by AWACS, within 100nm SURV display range: Shown on HSD/FCR (SURV air track).

B) Flight member, no PPLI available, not detected by AWACS (out of AWACS 135nm detection range): No SURV air track generated.

C) Package Member, no PPLI available, detected by AWACS, within 100nm SURV display range: Shown on HSD/FCR (SURV air track).

D) Friendly, no PPLI available, detected by AWACS, within 100nm SURV display range: Shown on HSD/FCR (SURV air track).

E) Friendly, detected by AWACS, not within 100nm SURV display range: Not shown on ownship HSD/FCR.

F) Hostile, detected by AWACS, not within 100nm SURV display range: Not shown on HSD/FCR.

G) Hostile, not detected by AWACS (out of AWACS 135nm detection range): No SURV air track generated.

H) Hostile, within AWACS detection range and within 100nm SURV air track display range, but not detected by AWACS (bandit could be jamming, stealth or terrain masking): No SURV air track generated.

I) Hostile, detected by AWACS and classified ‘Hostile’, within 100nm SURV display range: Shown on HSD/FCR (SURV air track).

J) Friendly, not detected by AWACS (out of AWACS 135nm detection range) and no PPLI available : No SURV air track generated.

K) Friendly, detected by AWACS, no PPLI available, within 100nm SURV display range: Shown on HSD/FCR (SURV air track).

L) Hostile, not detected by AWACS (out of AWACS 135nm detection range): No SURV air track generated.

M) Hostile aircraft, detected by AWACS, but currently classified as ‘Suspect/Assumed Hostile/Pending’, within 100nm SURV display range: Shown on HSD/FCR (SURV air track).

N) Hostile aircraft, detected by AWACS, but currently classified as ‘Unknown/Assumed Friend/Pending’, within 100nm SURV display range: Shown on HSD/FCR (SURV air track)

Yes indeed- many thanks

nice

Hi Everyone,
Does anyone know if this will work in BMS as a rotary encoder for various axis?

https://www.elgato.com/us/en/p/stream-deck-plus-black

-Sharpe

@Micro_440th

Thanks so much for your help Micro

My Sqn is starting to see this issue, was just about to post a bug report.

As OP says, there is no crash and no bug report - but this is becoming deeply frustrating.

@Rouge1512

Straight up fix!

Many thanks - solved, just press ‘L’

A thousand thanks!