mts-op-jcr 1.0 pocket guide

DRAFT FBCB2-JCR 1.0 OPERATORS POCKET GUIDE-MTS

SAFETY STEPS TO FOLLOW IF SOMEONE IS THE VICTIM OF ELECTRICAL SHOCK

1. DO NOT TRY TO PULL OR GRAB THE INDIVIDUAL

2. IF POSSIBLE, TURN OFF THE ELECTRICAL POWER

3. IF YOU CANNOT TURN OFF THE ELECTRICAL POWER, PULL, PUSH OR LIFT THE PERSON TOSAFETY USING A DRY WOODEN POLE, A DRY ROPE OR SOME OTHER INSULATING MATERIAL

4. SEND FOR HELP AS SOON AS POSSIBLE

5. AFTER THE INJURED PERSON IS FREE OF CONTACT WITH THE SOURCE OF ELECTRICALSHOCK, MOVE THE PERSON A SHORT DISTANCE AWAY AND IMMEDIATELY START ARTIFICIALRESUSCITATION, SEE FM 4-25.11

GENERAL SAFETY PRECAUTIONS

For safety precautions during the maintenance of electrical/electronic equipment, see TB 385-4 (Army).

For care and handling of electronics equipment, see TM 43-0158 (Army).

FIRST AID

For further information on first aid, see FM 4-25.11.

WARNING

Do not disconnect or connect any cables without properly powering down the system andturning off all power. When disassembling disconnect the ground cable last and when assem-bling connect the ground cable first. Failure to comply could cause injury to personnel and/ordamage to equipment.

WARNING

Nickel Metal Hydride (NiMH) internal back-up batteries may rupture and causeirritation if leaked electrolytes adhere to eyes and skin. Lithium CarbonMonofluoride Complementary Metal-Oxide Semiconductor (CMOS) button-cellinternal back-up battery may rupture and cause irritation if leaked electrolytesadhere to eyes and skin. Eyes or skin should be immediately washed withwater to remove electrolytes. If Processing Unit (PU) batteries leak, removebatteries and clean out the battery compartment with a clean water dampenedcloth, then dry thoroughly. Dispose of batteries IAW your local servicingDefense Reutilization and Marketing Office (DRMO).

WARNING SUMMARY

a

WARNING

HIGH VOLTAGE - Ensure all power to the FBCB2 system is off (includingpower from the vehicle) before conducting maintenance involving the removalor replacement of system components. Failure to comply could cause injury topersonnel and/or damage to equipment.

WARNING

Inspect cables to ensure they are properly dressed and stowed to prevent tripand snag hazards. Failure to comply could cause injury to personnel and/ordamage to equipment.

WARNING

Avoid contact with skin, eyes, and clothes, and do not breathe vapors ifbacklights in the display unit break and leak Mercury and/or Lead.Immediately contact the proper authorities for proper removal of the spillage,and if necessary administer appropriate medical aid. Dispose of Mercury andLead IAW your local servicing Defense Reutilization and Marketing Office(DRMO). Failure to comply could cause injury to personnel.

CAUTION

Do not shut down the computer power without following software shutdown procedures toavoid loss of data. Failure to comply could cause damage to equipment.

WARNING SUMMARY - Continued

b

TABLE OF CONTENTS

Section No.Page No.

WARNING SUMMARY a

Chapter 1 - MOVEMENT TRACKING SYSTEM (MTS-ES)MTS-ES PLATFORM CABLE DIAGRAM AND COMPONENT DESCRIPTION ANDINDICATORS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.1

MTS-ES Platform System Components . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1-1

MTS-ES PLATFORM STARTUP PROCEDURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2

MTS-ES Platform Startup Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2-1

MTS-ES PLATFORM SHUTDOWN PROCEDURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3

MTS-ES Platform Shutdown Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . 1.3-1

MTS-ES PLATFORM CONFIGURATION PROCEDURES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4

MTS-ES Platform Configuration Procedures. . . . . . . . . . . . . . . . . . . . . 1.4-1

Load UTO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4-5

Bind the Satellite Transceiver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4-6

Unbind the Satellite Transceiver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4-7

Touch Screen Calibration.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4-7

GENERATE LOCAL TAG COLLECTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.5

Generate Local Tag Collection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.5-1

ZEROIZE PROCEDURES FOR SATELLITE TRANSCEIVER (MT-2012). . . . . . . . . . . . . . . . 1.6

Zeroize Satellite Transceiver (MT-2012). . . . . . . . . . . . . . . . . . . . . . . . . . 1.6-1

Zeroize GPS in Satellite Transceiver (MT-2012). . . . . . . . . . . . . . . . . 1.6-1

Chapter 2 - MISSION DATA LOADING (MDL) PROCEDURESCONNECT MISSION DATA LOADER (MDL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1

Connecting MDL to AN/UYK-90(V)2 Display Unit . . . . . . . . . . . . . . . . 2.1-3

CREATE A MESSAGE MISSION DATA SET. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2

Create a Message Mission Data Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2-1

i

TABLE OF CONTENTS - Continued

Section No.Page No.

Export Mission Data Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2-1

CREATE/EDIT MISSION DATA SET. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3

Create Mission Data Set.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3-1

Edit Mission Data Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3-3

Copy Data Set Folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3-4

Remove Data Files from Mission Data Set. . . . . . . . . . . . . . . . . . . . . . . 2.3-5

Refresh Mission Data Files List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3-6

View Mission Data Files Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3-6

Delete Mission Data File.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3-7

Delete Mission Data Set Folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3-7

Rename Mission Data Set Folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3-8

INSTALL FROM MDL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4

Install from an MDL Device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4-1

SCREEN CAPTURES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6

Capture a Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6-1

Capture a Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6-2

Chapter 3 - OPERATOR SECURITY PROCEDURESSECURITY PROCEDURES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1

Destroy the Satellite Transceiver using Transceiver ManagerTools.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1-1

Activate the Screen Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1-2

De-Activate the Screen Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1-3

Chapter 4 - ACRONYMS AND DEFINITIONSACRONYMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1

ii

MTS-ES PLATFORM CABLE DIAGRAM AND COMPONENT DESCRIPTION AND INDICATORS

Cable and Component Diagram

The key communications features of the Movement Tracking System are: its ability to use a variety of in-orbitcommercial satellites, its near real-time communications speed, its security features, and its radio frequencyidentification and military global positioning system capabilities.

MTS-ES PLATFORM SYSTEM COMPONENTS

The MTS-ES Platform consists of the following:

• MT 2012RS transceiver.

• Ruggedized computer.

• Ruggedized keyboard.

• Camouflage cover.

• MTS Plus EUM.

• Transit case.

Figure 1 is a cabling diagram of the MTS-ES Platform system showing the connection of the major components.This diagram is intended to show the interfaces of various MTS-ES Platform equipment and peripherals and doesnot necessarily reflect an actual vehicle configuration.

1.1-1

Figure 1. MTS-ES Platform Cabling Diagram

1.1-2

Controls and Indicators for MTS-ES.

MTS-ES Platform Display Unit.

Figure 2. MTS-ES Platform Display Unit.

Display Unit Controls and Indicators Panel.

The DU has the following front panel functions:

1.1-3

• ON/OFF: Controls DC power to both the PU and DU.

• Panel Window Indicator: TBD

• 911:Selecting 9-1-1 displays the MAYDAY message template, enabling the user to quickly send a MAYDAYmessage without destroying MTS-ES Ptatform.

• SCREEN + BRIGHT and OFF/ON:Increases brightness of the display /LEDs.

• Speaker:Allows for audio to be heard, such as beeps, when required.

1.1-4

MTS-ES Platform Keyboard Unit (KU).

Figure 3. MTS-ES Platform Keyboard Unit.

Keyboard Unit Controls and Indicators.

The following are the KU controls:

• KU Basic Keys:Each KU has a full set of number, letter, and punctuation keys that are arranged in the samepattern as a standard commercial keyboard.

1.1-5

• KU Function Keys: The function keys F1 through F8 are operational when the OPS Main Screen isdisplayed. Function keys F9 through F12 are not used. The function keys on the KU correspond to the FBCB2software buttons on the OPS Function Bar. Selecting the KU's left Alt key and function key simultaneouslycorresponds to the DU 8-Button Bezel Keypad software functions.

• Mouse Controls:There are two mouse control buttons. The left button selects the object or executes a func-tion. The right key opens Help in the Messages dialog box or pop-up menus with options.

• Backlighting:The KU keys are backlit to make their labels visible at night. Press the BACK-LIGHT button toturn backlighting on and off.

• Pointing Device: The KU pointing device duplicates the functions of a mouse device. It consists of a movablepointer. The pointing device moves the cursor on the DU screen.

1.1-6

GUMBALL STATUS INDICATORS

Gumball Status Indicators: The gumball status indicators (total of 4) show the current state of allexternally-connected devices. Status is displayed using a communications antenna gumball for signal strengthand three separate device gumballs using letters and color for device condition.

Joint Capabilities Release (JCR) Gateway Status Indicator: The JCR Gateway gumball status indicator is thefirst status gumball located at the far left of the OPS screen marquee. It provides system status for JCR Gatewayconnections and is depicted by a communications antenna.

• JCR Gateway Status: The JCR vehicle software has a JCR Gateway Server application that allows VDX datato be exchanged with other users. The JCR Gateway Server application provides the capability for the JCRvehicle to serve as a gateway to other users and as a client to another gateway. To register with anothergateway server, the user will enter and send login information to that gateway.

• JCR Gateway:Represented by the signal strength gumball and automatically detects BIT stream rate betweenthe transceiver and the satellite. Full signal strength of 4 bars is shown if transceiver is in a bound state.

Figure 4. Joint Capabilities Release (JCR) Gateway Status Gumball

1.1-7

The Local Comm gumball for your system is located at the top of the Ops screen on the left of the marquee to theleft of the GPS status indicator as shown in Figure 4. The button color is either Red (No Go), Amber (Degraded),Green (Go), or White (Not Tested). Selecting the Local Comm gumball opens the status window, which helps theoperator determine the Satellite Communication (SATCOM) status.

The SATCOM status for your system is indicated on the marquee at the top of the Ops screen.

• Local Comm: GO (GREEN indication). Under normal operations, the green status indicator indicates satellitecommunications has been established.

• Local Comm: DEGRADED (AMBER indication). A amber status indicator indicates satellite communicationshave been lost with the satellite - transceiver not in lock. The operator must move the platform.

• Local Comm: NO GO (RED indication): After second and third attempts to find hardware, a red status indicatormay appear, indicating it is unable to establish communication with the satellite. The operator should checkpower, check cables, and restart to BCOPS.

The GPS status for your system is located at the top of the Ops screen on the left of the marquee to the right ofthe COMMS status indicator as shown in Figure 4.

• GPS: GO (GREEN indication). The green status indicator indicates communication is established with GPSsatellites.

• GPS: DEGRADED (AMBER indication). A amber status indicator indicates status check (TIME, HEADING,and POSITION). It also means lost communications with GPS, and that operator should check GPS settingsand verify satellite and the Line Of Site (LOS) when the MT2012 Transceiver is unobstructed.

• GPS: NO GO (RED indication). After second and third attempt to find hardware, a red status indicator mayappear, indicating it is unable to establish communication with GPS. The operator should check power, checkcables, and restart to BCOPS.

When your platform is configured as one the MTS-ES products, and an MT2012 Transceiver device is externallyconnected to the system, the third status gumball allows you to display the MT-2012 RFID Interrogator devicestatus, as shown in Figure 4.

• Detection: GO (GREEN indication). The green status indicator indicates a MT-2012 device has been detected.

• Detection: NO GO (RED indication). The red status indicator indicates a MT-2012 device has not beendetected/not responded for 2 minutes.

• On/Off: GO (GREEN indication). The green status indicator indicates RFID Enabled.

• On/Off: NO GO (RED indication). The red status indicator indicates RFID Disabled.

• Read: GO (GREEN indication). The green status indicator indicates results successfully received / readcommand not issued.

• Read: NO GO (RED indication). The red status indicator indicates no results received within the time-outperiod.

1.1-8

TRANSCEIVER LED INDICATORS

Figure 5. Satellite Transceiver MT-2012 LEDs

Three status LEDs are located on the outside of the transceiver as shown in Figure 5 and indicate the operatingcondition of the Satellite Transceiver. The following is a description of the LED indicators and their meaning:

1. Red LED illuminates briefly at power up. The only other time the Red LED illuminates is during data trans-mission. If the Red LED stays illuminated, contact field maintenance. If the Red and Amber LEDs areblinking alternately or off, contact Field Signal Maintenance.

2. Green LED illuminates and then begins blinking. Constant blinking means the receiver is not in lock. Whenthe Green LED is on steady, the receiver is in lock.

3. Amber LED on indicates the Satellite Transceiver has a good data connection with the FBCB2 system. It willblink intermittently when data is being transmitted. If it remains off, the Satellite Transceiver is not commu-nicating with the BFT network. If the amber and red LEDs are flashing alternately, a failure has occurred inthe Satellite Transceiver.

1.1-9

MTS-ES PLATFORM STARTUP PROCEDURES

MTS-ES Platform Startup Procedure.

STEP OPERATOR ACTION INDICATION or CONDITION

1. Set the Power Supply toggle switch on the V2 ControlBox to ON.

The Green PWR LED on the V2 ControlBox illuminates. The Satellite TransceiverLEDs will also illuminate.

2. Select ON/OFF on the Display Unit (DU). Startup continues automatically until theDU displays the Session Manager screenwith the Task bar on the bottom, and theLogin dialog box opens.

3.

NOTE

The password is case sensitive. Asterisks aredisplayed as the password is typed followed by ablinking cursor in the Password text box.

NOTE

If an incorrect password is entered, the Bad Pass-word dialog box opens. Select OK and re-enter thepassword. After three unsuccessful login attempts,the system displays a warning notice that themaximum login attempts has been exceeded. Ifthe system aborts the login process, contact theSecurity Officer/S6.

Enter password.

1.2-1

MTS-ES Platform Startup Procedure. - Continued

4.

NOTE

Configure Role is now accessible.

Configure Role, if required IAW CONFIGURATIONPROCEDURES FOR FBCB2-BFT.

• If Role is correct, continue with step 5.

• If correct Role or no Role(s) is(are) notavailable, load UTO IAW Load UTO.Continue with Step 4 after UTO loadcomplete.

5. Select OK. Login dialog box closes.

6. If the Password Expiration Message dialog box isdisplayed, select OK to continue logging in.

Password Expiration Message dialog boxcloses.

7. If the Virus Scan dialog box is displayed, select NO tocontinue logging in.

Session Manager screen displays.

8. Select OPS to start the Ops screen. The Ops Screen opens.

9. Verify the status of the GPS, RFID and the LocalCOMM gumballs.

The GPS, RFID and Local COMM systemstatus gumballs are all green.

10. Verify that the platform's unit icon is displayed on themap or image, and that icons of other units in thearea are also displayed.

This step may take up to 5 minutes. Ifother unit icons are displayed, the V2Mobile Unit is receiving and processingposition data via the satellite.

11. Prepare a Free Text message and send it to a localunit, requesting a reply.

If a reply to the message is received, thenC2 communications are functioningcorrectly.

1.2-2

MTS-ES PLATFORM SHUTDOWN PROCEDURES

MTS-ES Platform Shutdown Procedure.


1. Select START/SHUT DOWN/SHUT DOWN. Shutdown confirmation dialog box opens.

2. Select YES. System closes all applications and shutsdown.

3. Set the Power Supply toggle switch on the V2 ControlBox to OFF.

The Green PWR LED is off. The satellitetransceiver LEDs also off.

1.3-1

MTS-ES PLATFORM CONFIGURATION PROCEDURES

MTS-ES Platform Configuration Procedures.


1.

NOTE

Load UTO if required IAW Load UTO.

Ensure the 10 character password has been enteredin to the Login dialog box.

2. Select Current Role drop-down arrow The Warning: Changing role! dialog boxopens with the message: You are about tochange roles. Would you like to proceed?

3. Select YES. The Warning Changing role! dialog boxcloses, and the Select Role dialog boxopens.

1.4-1

MTS-ES Platform Configuration Procedures. - Continued

4.

Make the appropriate selections using the drop-down arrows:

• Select Corps.

• Select Division.

• Select Brigade.

• Select Battalion.

• Select Company.

• Select Platoon.

• Select a match found within the Matches area.

NOTE

If the correct match is not displayed, use thesearch feature.

1. Select Lookup.

2. Select the keyboard icon.

3. Select all or part of the platform/unit identifier.

4. Select OK.

5. Select Search.

5. Select OK. The Select Role dialog box closes

6. Select OK in the main Login screen. The Product Configuration dialog boxopens.

7. Select MTS-ES Platform.

8. Select OK. Product Configuration dialog box closesand Configure Platform Settings dialogbox opens.

9. Select a platform from Select Platform Type menu.

1.4-2


10. Select Apply.

11. Select Hardware. Configure Hardware settings dialog boxopens.

12.

NOTE

MTS installation is limited to certain approvedvehicles. If another vehicle is selected outsidethe limited MTS vehicles, contact FSR or S6personnel to set Com A: to L-Band. Thevehicles include:

• M900 series.

• HMMWV.

• HET.

• PLS.

• HEMTT.

• FMTV.

Verify L-Band is selected.

.

13. Select Apply.

14. SelectOK. Configure Platform Settings dialog boxcloses. The Restart Required dialog boxopens.

15. Select Reboot. System reboots and returns to Logindialog box.

16. Type Password. No Bumper Number Entered dialog boxopens with the message: Bumper Numberneeds to be entered before continuing.Please enter Bumper Number.

17. Select OK. No Bumper Number Entered dialog boxcloses and Login Screen opens withBumper Number drop-down box.

1.4-3


18. Type Bumper Number (BN) into BN text box or selectfrom drop-down arrow.

19. Select OK. .

20. If the Password Expiration Message dialog box isdisplayed, select OK to continue logging in.

Password Expiration Message dialog boxcloses and the Login dialog box closesand the Transceiver binding warningdialog box displays the message: "Thetransceiver is not in the Bound state.Please use the Transceiver Manger toolto check the transceiver."

21. Select OK. The Transceiver binding warning dialogbox closes.

22. If the Virus Scan dialog box is displayed, select NO tocontinue logging in.

Session Manager screen displays.

23. Select Start/Transceiver Manager. Initialize dialog box opens and closes.The Transceiver Manager Tools dialogbox opens.

24. Select Bind. The Transceiver Bind dialog box opens.When the binding is successful, thefollowing message appears in the first lineof text: "The transceiver xxxxx has beenbound to the current FBCB2-BFT harddrive."

25. Select Close. Transceiver Manager Tools dialog boxcloses and the Local COMM gumballstatus indicator will turn green once theMT-2012 transceiver connection is made.

1.4-4

Load UTO.


1. Verify MDL connected IAW CONNECT MISSIONDATA LOADER (MDL).

2. Select START/FBCB2/MISSION DATA LOAD/MISSION DATA LOADER.

The Mission Data Loader dialog boxopens.

3. Select Copy From. The Mission Data Loader Copy Fromdialog box opens.

4. Select MdlDevice from the Copy From Source drop-down arrow.

The UTO filename appears in the Namewindow.

5. Select UTO file folder. The folder highlights in blue and theactions for extracting are now active.

6. Select Extract. The Importing: Do Not Disconnect Devicemessage appears. Once extraction iscomplete, the Action Complete dialog boxopens.

7. Select OK. The Action Complete dialog box closesand the extraction message disappears.

8. Verify the UTO file was extracted to the Mission DataSets, Name area.

9. Select Install. Mission Data Loader Install dialog boxopens.

10. Select the UTO file folder. The folder highlights in blue and theactions for installation are now active.

11. Select Install Mission. The Installing: Do Not Disconnect Devicemessage appears. Once installation iscomplete, the Action Complete dialog boxopens.

12. Select OK. The Action Complete dialog box closesand the installation message disappears.

13. Select Close. The Mission Data Loader dialog boxcloses.

1.4-5

Bind the Satellite Transceiver.


1.

NOTE

The transceiver must be in the UNBOUND statebefore it can be bound to the system RHDDC.

Select START/TRANSCEIVER MANAGER TOOLS .

The Transceiver Manager dialog boxopens. The transceiver serial number andcurrent security state are displayed in thethird line of text in the dialog box.

2. Record the transceiver serial number as displayed inthe Transceiver Manager dialog box.

3. Select BIND. The Transceiver Bind dialog box opens.When the binding is successful, thefollowing message appears in the first lineof text: "The transceiver xxxxx has beenbound to the current FBCB2-JCR harddrive."

4. Select CLOSE to exit the Transceiver Managerdialog box.

Transceiver Manager dialog box closes.

1.4-6

Unbind the Satellite Transceiver.


1.

NOTE

The transceiver must be in the BOUND statebefore it can be unbound to the system RHDDC.

Select START/TRANSCEIVER MANAGER TOOLS .

The Transceiver Manager dialog boxopens. The transceiver serial number andcurrent security state are displayed in thethird line of text in the dialog box.

2. Record the transceiver serial number as displayed inthe Transceiver Manager dialog box.

3. Select UNBIND. The Transceiver Unbind dialog boxopens. When the unbinding is successful,the following message appears in the firstline of text: "The transceiver xxxxx hasbeen unbound to the current FBCB2-JCRhard drive."

4. Select CLOSE to exit the Transceiver Managerdialog box.

Transceiver Manager dialog box closes.

Touch Screen Calibration.


1. Select Start/Settings/TouchScreen Calibration. TouchScreen Calibration opens anddialog box displays the message: "Thetouch screen has already been calibrated:Do you wish to run the calibration utilityagain [y/n]?".

2. Type y (Yes).

1.4-7

Touch Screen Calibration. - Continued

3. Select Enter. System shuts down and then restarts anddisplays the calibration screen.

4.

NOTE

Be sure to position the stylus or mouse control asclose to the center of the icon as possible whendisplayed. When all selections have been madethe JBCSAD_MTS_calibrate.bash dialog boxopens.

Touch the center edge of the screen using thestylus or keyboard mouse in the following order:

• Upper edge selection: Left top, Center top, Righttop.

• Center edge selection: Left center, Right center.

• Lower edge selection: Left bottom, Center bottom,Right bottom.

• Slight lower mid selection.

The JBCSAD_MTS_calibrate.bash dialogbox opens. Tthe message displays: "Wasthe calibration performed successfully(y:n)?"

1.4-8

Touch Screen Calibration. - Continued

5.

NOTE

If the calibration was unsuccessful, select "n".Select "y" to be taken back to the beginning of thecalibration process.

Select y (Yes).

6. Select Enter. The JBCSAD_MTS_calibrate.bash dialogbox closes, and the Session Managerscreen opens.

1.4-9

GENERATE LOCAL TAG COLLECTION

Generate Local Tag Collection.


1. Select START/MTS-ES/Local Tag Collection. Local Tag Collection window opens.

COLLECT RFID TAGS WITHIN INTERROGATION RANGE:

2. Select Collect Tag. All RFID tag IDs will be collected withininterrogation range.

IDENTIFY CURRENTLY CARRIED CARGO:

3. Select an ID tag row. Row is highlighted.

4. Select Mark as Cargo. Mark As Cargo marks selected(highlighted) RFID tag as Yes under theCargo? column to indicate as currentlycarried cargo. Marked cargo will notdisappear from the database even if thetag is outside of interrogation range.

IDENTIFY NON-CARRIED CARGO:


6. Select Unmark As Cargo. Unmark As Cargo unmarks selected(highlighted) RFID tags as No under theCargo? column. This feature is usedwhen cargo is delivered to consignee orsimply to denote a particular RFID tag asnon-carried cargo.

1.5-1

Generate Local Tag Collection. - Continued


ENABLE RFID TAG AUDIBLE BEACON ALERT:

7.

NOTE

This feature can only be applied against a singleRFID tag at a time. The tag will continue to soundthe beacon alert until the Beep Off button isselected, or a period of five minutes is exceeded.

Select an ID tag row.

Row is highlighted.

8. Select Beep On. Beep On causes the RFID tags to soundthe beacon alert.

DISABLE RFID TAG AUDIBLE BEACON ALERT:


10. Select Beep Off. Beep Off disables the ability for a RFIDtag to sound the beacon alert.

DELETE A NON-CARGO RFID TAG:

11. Select a non-cargo ID tag row. Row is highlighted.

1.5-2



12.

NOTE

This function works for manually entered RFIDtags as well as interrogated tag data. A deleteattempt on a Marked Cargo item will be rejectedby software, you will be prompted to Unmark AsCargo prior to RFID tag removal.

Select Delete.

Delete removes the selected(highlighted) RFID tags from the LocalTag Collection section.

DELETE ALL NON-CARGO RFID TAGS:

13. Select Delete All Unmarked. Delete removes all RFID tags that arenot marked as cargo. This allows you toeasily remove all RFID tags that does notbelong to your current shipment load.

DISABLE RFID INTERROGATOR HARDWARE:

14.

NOTE

Interrogator Off is the default selection for theMT2011 transceiver.

Select Interrogator Off.

Interrogator Off option disables the RFIDInterrogator hardware on the MT2012transceiver. It disables RFID tag interrog-ation.

15. Select Apply.

ENABLE RFID INTERROGATOR HARDWARE:

1.5-3



16. Select Interrogator On. Interrogator ON option enables the RFIDInterrogator hardware on the MT2012transceiver. It allows RFID tag interroga-tion.

17. Select Apply.

SET LOCAL RFID TAG COLLECTION INTERVAL:

18.

NOTE

This section is applicable only if there is a MT2012transceiver connected to your platform.

Select Scan Interval arrow.

19.

NOTE

This feature allows you to set the local RFID tagcollection interval. The default time interval is setto interrogate RFID tag data every 15 minutes.

Select a time interval.

20. Select the Apply.

SET INTERROGATOR'S POWER RANGE:

1.5-4



21.

NOTE

This feature is disabled if your platform isconnected to a MT2011 transceiver.

Select Power Setting arrow.

22.

NOTE

The RFID tags transmit at a constant powerrelated to their battery strength. Increasing/decreasing interrogator power setting expands/shortens the range to interrogate RFID tags.

Select a power range.


MANUALLY ENTER RFID TAGS:

24. Select the Manual Tag Entry ID text field, or keyboardicon.

25. Enter a RFID tag number.

26. Select the Add .

DISABLE AUTOMATIC SERVER UPDATE:

27. Select Auto Update Server Off.


1.5-5



ENABLE AUTOMATIC SERVER UPDATE:

29. Select Auto Update Server On.


RFID DATA TO UPDATE TO SERVER:

31.

NOTE

Marked Cargo Onlyallows you to report "markedcargo" items only to the RFID server.

Select Marked Cargo Only.

1.5-6




33.

NOTE

All Tagsallows you to report all collected RFID tagdata to the RFID server.

Select All Tags.


SET SERVER AUTO UPDATE INTERVAL:

35.

NOTE

Update Intervalallows you to set the serverupdate time interval.

Select Update Interval.

36. Select a time interval.


MANUALLY UPDATE SERVER:

1.5-7



38.

NOTE

Update Server collects all marked cargo RFIDdata and sends the data to the RFID Server.

Select Update Server.

COLLECT HEADER DATA FOR A SINGLE RFID TAG:

39. Select one ID tag row.

40.

NOTE

The Read Header Data button triggers manual tagheader collection for the selected (highlighted) tag.Multiple header data tag collection is not allowed.

Select the Read Header Data.

EXIT LOCAL TAG COLLECTION FUNCTIONALITY:

41. Select CLOSE. Local Tag Collection window closes.

1.5-8

ZEROIZE PROCEDURES FOR SATELLITE TRANSCEIVER (MT-2012)

Zeroize Satellite Transceiver (MT-2012).


1. Select START/TRANSCEIVER MANAGER. Transceiver Manager Tools dialog boxopens.

2. Select Advance. Transceiver Manager Advance Toolsdialog box opens.

3. Select Zeroize Transceiver Keys. Confirm Zeroize Keys dialog box opens.

4. Select Continue. Time Remaining dialog box opens.

5.

WARNING

Destroying Satellite Transceiver is not recoverable.

Select Now, or wait 15 seconds to destroy theTransmission Keys.

A message displays the TransmissionKeys have been destroyed.

Zeroize GPS in Satellite Transceiver (MT-2012).


1. Select START/TRANSCEIVER MANAGER. Transceiver Manager Tools dialog boxopens.

2. Select Advance. Transceiver Manager Advance Toolsdialog box opens.

3 Select Zeroize GPS. Confirm GPS Zeroize dialog box opens.

1.6-1

Zeroize GPS in Satellite Transceiver (MT-2012). - Continued


4. Select Continue. Time Remaining dialog box opens.

5. Select Now, or wait 15 seconds to zeroize the GPS. A message displays the GPS has beenzeroized.

1.6-2

CONNECT MISSION DATA LOADER (MDL)

Connect MDL

CAUTION

Any changes or modification of the MDL not expressly approved by the party responsible forcompliance could result in failure of the MDL device.

NOTE

To assure continued compliance with FCC requirements, use only USB cables specificallyapproved for each system when connecting a peripheral to an MTS-ES Platform.

The MDL is preassembled for immediate use. A special data interface cable is connected from the Left USBconnector on the AN/UYK-90(V)2 Display Unit (DU) to the MDL. Figure 1 shows the Y-cable used to connect theMDL to the MTS-ES Platform. The MDL has a protective dust cap, which is removed before connecting theinterface cable.

2.1-1

Figure 1. MTS-ES Platform USB Interface Cable

2.1-2

NOTE

The MT-ES Platform must be started up prior to the MDL being connected to prevent thepossibility of a system failure during the startup process.

Connecting MDL to AN/UYK-90(V)2 Display Unit.


1. Remove dust cap from MDL.

2. Connect cable assembly (889495-1) to J1connector of MDL.

3. Connect USB end of cable assembly to leftUSB connector of AN/UYK-90(V)2 DU IAWFigure 2.

2.1-3

Figure 2. Connection Between MDL and AN/UYK-90(V)2 Display Unit

2.1-4

CREATE A MESSAGE MISSION DATA SET

Create a Message Mission Data Set.


1. Select START/FBCB2/MISSION DATA LOAD/MESSAGE MANAGER.

The Message Manager dialog boxdisplays.

2. Select NEW GROUP. The Name dialog box opens.

3. Type a name for the new message group and selectOK.

The new group appears in the right pane.

4.

NOTE

Files must be selected and added one at a time.

Open the desired message folder in the left pane andselect the first file to be added to the new group.

5. Select Make Exportable , from Message Managerdialog box.

The file appears under the new groupfolder in the right pane.

6. Repeat the above steps until all desired files areadded to the new group folder.

7. Select CLOSE.

Export Mission Data Set.


1. Select right-facing arrow to open up appropriatefolder in Saved Messages pane to make messageavailable for MDL export.

2.2-1

Export Mission Data Set. - Continued

2. Select message file (not a folder).

3.

NOTE

The Make Exportable creates an exportablemessages package containing the selected savedmessages. The system uses the group's foldername for the exportable package and made avail-able to the MDL functionality.

Select Make Exportable , from Message Managerdialog box.

2.2-2

CREATE/EDIT MISSION DATA SET

NOTE

Mission Data Sets (MDSs) to include overlays, map sets, and any other files to be included inthe MDL load should be created prior to performing this procedure. MDSs can include pass-words, messages, and other types of files that are bundled into sets prior to being included ina mission data load.

Create Mission Data Set.


1. Connect MDL IAW Figure 1.

2.3-1

Create Mission Data Set. - Continued

Figure 1. Connection Between MDL and AN/UYK-90(V)2 Display Unit

2. Select START/FBCB2/MISSION DATA LOAD/MISSION DATA LOAD.

Mission Data Loader dialog box displays.

3. Select NEW MISSION. Mission Data Load Details dialog boxdisplays.

4. Enter a name for the new mission, a point of contact(POC), and description of files in the appropriatefields provided.

2.3-2

Create Mission Data Set. - Continued

5.

NOTE

This option is defaulted to Unclassified when youruser access level is Sensitive But Unclassified(SBU); the field is also shown disabled to preventyou from making an invalid selection.

NOTE

This option is shown enabled If your user accesslevel is classified (SECRET).

Select Classification drop-down for classified(SECRET) and select appropriate option.

6. Select SAVE.

7. Select CLOSE. Data Load Details dialog box closes andthe created mission folder appears in theright pane of the Mission Data Loaderdialog box.

8. Select CLOSE. Mission Data Loader session ends.

Edit Mission Data Set.




2. Select plus sign (+) to open up appropriate folder inthe Available Mission Data Files pane.

2.3-3

Edit Mission Data Set. - Continued

3.

NOTE

The selected folder is indicated in the left pane andthe individual file names within the MDS appearunder the folder name.

Select data file.

4. Select folder from the Mission Data Sets pane.

5.

NOTE

This step is to Add files to the Mission Data Set.

Select Add File.

The selected files will be copied to theMission Data Sets folder selected in theright pane.

6.

NOTE

This step is to Remove files from the Mission DataSet.

Select Remove File.

The selected files will be deleted from theMission Data Sets folder selected in theright pane.

7. Select CLOSE. Mission Data Loader screen closes.

Copy Data Set Folder.




2.3-4

Copy Data Set Folder. - Continued

2. Select appropriate mission folder in Mission DataSets pane.

3. Select Copy Mission. Data Load Details dialog box opens withthe selected folder name entered in theMission Name field, the POC and descrip-tion, if previously entered, and the LastModified date and time automaticallyentered.

4. Select Mission Name. Mission Name text box opens.

5. Enter a new name to copy the MDS.

6. Select Save.

7. Select Close. Data Load Details dialog box closes andthe copied mission folder appears in theMission Data Sets pane.

8. Select Close. Mission Data Loader session ends.

Remove Data Files from Mission Data Set.




2. Select the plus sign (+) to open up appropriate folderin Mission Data Sets pane.

3. Select data file.

4.

NOTE

Remove File deletes a Mission Data Set group file.

Select Remove File.

Mission Data Set File deleted.

2.3-5

Remove Data Files from Mission Data Set. - Continued


Refresh Mission Data Files List.




2. Select Refresh List. Refresh List button updates the displayedlist with any changes that have occurredsince the current dialog box was opened.The button's label turns red when newupdates are available.


View Mission Data Files Details.




2. Select appropriate file from Available Mission DataFiles pane.

3. Select File Details. Element Details dialog box opens

4. Enter a new description

5. Select Save.

6. Select Close. Element Details dialog box closes.

2.3-6

View Mission Data Files Details. - Continued


Delete Mission Data File.




2. Select plus sign (+) to open appropriate folder inAvailable Mission Data Files pane.

3. Select data file.

4. Select Delete File. Selected file deleted from the AvailableMission Data pane.


Delete Mission Data Set Folder.




2. Select appropriate folder in Mission Data Sets pane.

3. Select Delete Mission. Delete Mission dialog box opens.

2.3-7

Delete Mission Data Set Folder. - Continued

4.

NOTE

Delete Mission button removes an existing MissionData Set folder.

Select Yes.

Delete Mission dialog box closes.


Rename Mission Data Set Folder.




2. Select appropriate folder in Mission Data Sets pane.

3. Select Rename Mission. Data Load Details dialog box opens.

4. Select Mission Name text box.

5. Enter new name.

6. Select Save.

7. Select Close. Data Load Details dialog box closes.


2.3-8

INSTALL FROM MDL

Install from an MDL Device.


1. Connect the J1 cable quick-disconnect plug to theinput connector on the MDL device. Connect the J1Cable to the USB Y-connector.

Select START/FBCB2/Mission Data Load/MissionData Loader.

Mission Data Loader Install dialog boxopens.

2.

NOTE

Mission Data Sets Name column is populated.

Select Install.

3. Select a Mission Data Set folder or file.

4. Select Install Mission.

5. Select OK.

VIEW MISSION DETAILS:

6. Select a Mission Data Set folder or file.

7. SelectView Details. Data Load Details opens.

8. Select Close. Data Load Details closes.

DELETE A MISSION DATA SET:

2.4-1

Install from an MDL Device. - Continued

9. Select a Mission Data Set folder.

10. Select Delete Mission. Delete Mission dialog box opens.

11. Select Yes. Selected Mission Data Set folder deleted.

EXIT INSTALL MDL:

12. Select Close. Mission Data Loader dialog box closes.

2.4-2

SCREEN CAPTURES

Capture a Screen.


1.

NOTE

This procedure captures the entire displayincluding any open screens, windows, anddialog boxes. If you only want to capture asingle window or dialog box, refer to theprocedure in Capture a Window.

Open the desired screen for capture.

2. Select START/FBCB2/SCREEN IMAGEUTILITY/CAPTURE SCREEN.

Two (2) beeps will be heard and the screencapture will be saved to a .tmp file in the"Others" folder.

3. Perform the procedure in Create a MessageMission Data Set to copy the mission with thescreen capture file to an MDL.

2.6-1

Capture a Window.


1. Open the desired window for capture.

2. Select START/FBCB2/SCREEN IMAGEUTILITY/CAPTURE WINDOW.

3. Use the POINTING DEVICE on KU to steerthe cursor over the selected window.

4. Select the LEFT KEY pointing device on KUto select the window.

One beep will be heard and the capturedwindow will be saved to a .tmp file in the"Others" folder.

5. Perform the procedure in Create a MessageMission Data Set to load the mission to anMDL device.

2.6-2

SECURITY PROCEDURES

DESTROY THE SATELLITE TRANSCEIVER USING THE TRANSCEIVER MANAGER TOOLS DESTROYTRANSCEIVER COMMAND

The following procedure is to be used if the MTS-ES System is in IMMINENT danger of being captured by theenemy, the system is offline, and there is not time to go back online.

Destroy the Satellite Transceiver using Transceiver Manager Tools.


1. At the Session Manager screen, select START/TRANSCEIVER MANAGER.

Transceiver Manager Tools dialog boxopens.

2. Select Advanced. Transceiver Manager Advanced dialogbox opens.

2. Select DESTROY TRANSCEIVER. A Confirm Destroy dialog box opens withthe message: "WARNING!!! You mustconfirm that you want to destroy the trans-ceiver. This action is not recoverable! Doyou want to continue?"

3. Select CONTINUE. A Time Remaining dialog box opensshowing a countdown clock starting from15 seconds.

4. Allow the countdown to complete or select NOW todestroy the transceiver immediately.

A message is displayed indicating that thetransceiver has been destroyed.

3.1-1

ACTIVATE/DE-ACTIVATE THE SCREEN LOCK FUNCTION

NOTE

The screen lock should be activated any time the Field Test Operator needs to leave theimmediate area and will be out of sight of the DU. It can be activated from any screen.

Activate the Screen Lock.


1. Select START/SCREEN LOCK The screen lock login window appears andcovers the entire display.

NOTE

If three unsuccessful login attempts are made, a warning screen will appear with the followingmessage: "Number of login attempts exceeded. Please contact your security officer. Loginaborted." Should this happen, you will not be locked out and will be able to continue makinglogin attempts. Contact the Security Officer.

3.1-2

De-Activate the Screen Lock.


1. Enter the login password.

2. Select Authenticate. The Screen Lock window closes and expiredpassword warning dialog box opens.

3. Select OK. Expired password dialog box closes andoriginal screen restored.

3.1-3

ACRONYMS

LIST OF ABBREVIATIONS/ACRONYMS

Term Definition

AC Alternating Current

E E

BCOPS Battle Command Operations

BFT Blue Force Tracking

E E

DC Direct Current

DU Display Unit

E E

FBCB2 Force XXI Battle Command Brigade and Below

FMTV Family of Medium Tactical Vehicles

E E

GPS Global Positioning System

E E

HEMTT Heavy Expanded Mobility Tactical Truck

HMMWV High Mobility Multi-Purpose Wheeled Vehicle

E E

IAW In Accordance With

E E

JCR Joint Capabilities Release

4.1-1

LIST OF ABBREVIATIONS/ACRONYMS - Continued

Term Definition

E E

KU Keyboard Unit

E E

PLS Palletized Loading System

E E

SA Situational Awareness

E E

TB Technical Bulletin

TDR Transportation Discrepancy Report

TFOM Time Figure of Merit

TM Technical Manual

E E

USB Universal Serial Bus

E E

VAC Volts Alternating Current

VDC Volts Direct Current

VRC Vehicular Radio Communications

4.1-2

mts-op-jcr 1.0 pocket guide

Documents