TM 11-7025-221-10
2-28. Generate Local Mux Configuration Routine (V3/V4 Models).
Perform this routine to enter local mux configuration data in memory 1 or memory 2. Before performing
the routine, ensure that you have the configuration data required to complete the entries in the routine
as described in a below. The step-by-step procedures for the routine are in b below.
a. Data Required. To assist you in listing and determining if you have all the data you will need,
the following chart shows you what data are required and where the data are used in the routine.
NOTES
"Step No." Column. Step number for each procedure performed
q
by an operator that requires configuration data is listed in this
column. Steps performed by an operator that do not require a
configuration data input are not listed.
"Message heading/data required" Column. The message heading
q
that is displayed for each step requiring configuration data is shown
in this column. Below each message heading is one or more lines
for listing the required data that is supplied by the authority that
originated the configuration.
"Definitions" Column. This column defines the type of data that
q
is supplied and entered on the lines in the "Message heading/data
required" column. Some steps listed below are not used in all
configurations. Notes are added in the column to describe the
exceptions.
Local Mux Configuration Data Requirements (V3/V4 Models)
Message heading/
Step
Definitions
data required
No.
Enter "1" for memory 1 or "2" for mem-
4
MEMORY SELECTION
ory 2.
Entry:
At each port, enter port rate in kb/s or "0"
PORT RATES IN KBS
6
if port is inactive.
Port 5
Port 1
NOTE
Port 2 _
Port 6
Port 7 --
Port 3 --
Ports 5 thru 8 not used in V4 model.
Port 8 _
Port 4 --
Enter one of following for each active port.
PORT INTERFACE
7
"1" for balanced
Port 1 _
Port 4 --
"2" for conditioned diphase
Port 2 _
Port 5
Port 3 --
Ports 5 thru 8 not used in V4 model.
q
Ports 6, 7, and 8 are automatically entered as
q
balanced ("1") when active.
2-68