 |
|||
|
|
|||
|
Page Title:
Figure 4-5. EXAMPLE OF COMPANY LOADSET |
|
||
| ||||||||||
|
|  TM 11-5820-890-10-8
CO/TEAM COMMAND NET
NET ID: 275
CHANNEL 1
FIRE SUPPORT NET
NET ID: 678
CHANNEL 2
NET ID: 280
RIGHT FLANK CO/TEAM
CHANNEL 3
NET ID: 250
BN/TF COMMAND NET
CHANNEL 4
ATCHD ENGINEER PLT
NET ID: 733
CHANNEL 5
NET ID: 255
BN/TF ADMIN/LOG NET (OR KEK)*
CHANNEL 6
Figure 4-5. EXAMPLE OF COMPANY LOADSET
NET ID: 276
1 ST PLT
CHANNEL 1
2ND PLT
NET ID: 277
CHANNEL 2
NET ID: 278
3RD PLT
CHANNEL 3
CHANNEL 4
NET ID: 275
CO/TEAM COMMAND NET
CHANNEL 5
NET ID: 678
FIRE SUPPORT NET
NET ID: 733
ATCHD ENGR PLT (OR KEK)*
CHANNEL 6
Figure 4-6. EXAMPLE OF PLATOON LOADSET
*
If a KEK is loaded in Channel 6 in preparation for use of OTAR procedures, Channel 6 may
normally an infrequent requirement, and Channel 6 requires FH data be loaded in order to send
an OTAR message. One solution is to load a TEK in Channel 6, use it for normal communications
until an OTAR requirement comes up, and then load a KEK from the ANCD into Channel 6.
4-14
|
|
Privacy Statement - Press Release - Copyright Information. - Contact Us |
Click
here for thousands of PDF manuals