•The FMS will not pop up pages for the MFD if it is on a STATUS page. (Login screen, some
manual entries on messages…)
•
•If the MFDs are powered off and back on and find the IDM already in an OPERATIONAL
state the MFD will skip the initialization and just reconnect to the IDM.
•
•PN NET is not functional and should always show STOPPED or CONFIG REQUIRED or
EMCON.
•
•Messages should always use NET: TI NET as the PN net is not currently functional and the
SEND will fail if it is selected.
•
•Selecting LOAD on the FMS DTS page has no effect on the MFD JVMF. The FMS and
MFD load separate sets of files.
•
•The IDM Takes 1 ½ min to boot up from the time power is applied.
Changing the selection of UTO on the SETUP page may result in a brief delay while the IDM processes the selected UTO. The selected UTO should always be set in the AMPS and not changed unless a new UTO is loaded.
• If you have logged into the TI and need to load a different Mission card or you want to start over loading the JVMF from the start, put the card in, verify that it is ready by using the FMS, and follow the File Load slide.
• Always include the UTO files in an AMPS mission load even when you do not need to reload the UTO into the IDM as this will make it easier to select the correct UTO to use in the AMPS screen. Otherwise you will need to remember the database name which may not be the same as the filename.
Elevation data (RDTED files) will not work in the moving map unless it is in the DTS before the TAC page is accessed. This effects Elevation Banding, Height Above Terrain, Threat Inter-Visibility, and certain values prefilled into some VMF messages.
• The process will go smoother if you avoid loading files at the same time as other activities that use the DTS heavily. (FMS DTS Load, Accessing the TAC page…)