top - download
⟦9c2159f93⟧ Wang Wps File
Length: 18131 (0x46d3)
Types: Wang Wps File
Notes: NORWEGIAN HAWK AMC
Names: »5248A «
Derivation
└─⟦b3c9a9699⟧ Bits:30006142 8" Wang WCS floppy, CR 0015A
└─ ⟦this⟧ »5248A «
WangText
…02……00……00……00……0a……00……0b……00……00……00……0c……00……86…1 …02… …02… …02… …02…
NORWEGIAN HAWK AMC SYS/84-08-20
Part II
TECHNICAL PROPOSAL Page
#
LUFTSFORSVARETS FORSYNINGSKOMMANDO
PROPOSAL FOR
NOWEGIAN HAWK AMC
PART II
NORWEGIAN HAWK AMC SYS/84-08-20
Part II
TECHNICAL PROPOSAL Page
iv
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
1 FUNCTIONAL DESCRIPTION ...........................
5
2 AMC HARDWARE CONFIGURATION .......................
5
3 AMC SOFTWARE SYSTEM ..............................
6
4 ATDL ENCRYPTION ..................................
14
5 ATDL/MBDL/LINK 1 CONVERTER .......................
15
6 ITDL/MBDL CONVERTER ..............................
18
7 PHYSICAL PARAMETERS ..............................
18
8 DISPLAY SYSTEM ...................................
19
9 TRAINING .........................................
29
R̲e̲f̲e̲r̲e̲n̲c̲e̲d̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲s̲
1. Advanced Defence Information Systems
Published by Christian Rovsing A/S, 1984
1 F̲U̲N̲C̲T̲I̲O̲N̲A̲L̲ ̲D̲E̲S̲C̲R̲I̲P̲T̲I̲O̲N̲
A brief description of the AMC functions during normal
operation is included in ref. 1 chapter III D, section
1, 2 and 3. Further information is included in section
3 in the present document.
2 A̲M̲C̲ ̲H̲A̲R̲D̲W̲A̲R̲E̲ ̲C̲O̲N̲F̲I̲G̲U̲R̲A̲T̲I̲O̲N̲
The standard AMC included hardware for communication
on 8 ATDL and 8 MBDL lines. The hardware configuration
consists of standard CR80 modules and H/W modules specially
developed for the AMC. A block diagram for the H/W
configuration is shown in figure 3 (page 111 in ref.
1).
A Testbox is associated to the AMC system.
This Testbox contains test programs to be loaded into
the AMC for off-line testing of H/W modules.
The line panels for connection to HAWK batteries and
MBDL equipment is hidden behind the front cover plate
above the main swithces (see photo in ref. 1 page 116).
At the rear of the AMC is installed cables between
the two crates with possibilities for connection to
crypto devices.
3 A̲M̲C̲ ̲S̲O̲F̲T̲W̲A̲R̲E̲ ̲S̲Y̲S̲T̲E̲M̲
To give an overview of the processing performed by
the AMC, the data flow involved in the processing of
some typical message types are described below. Thereafter
follows a short description of each of the software
modules developed for the AMC. The S/W block diagram
is shown in ref. 1 figure 4 (page 113). Only the S/W
modules, that controls the data flow through the AMC
are included in this block diagram while all modules
included in the AMC are mentioned in the present description.
3.1 A̲T̲D̲L̲/̲M̲B̲D̲L̲ ̲M̲E̲S̲S̲A̲G̲E̲ ̲P̲R̲O̲C̲E̲S̲S̲I̲N̲G̲
M̲B̲D̲L̲ ̲m̲e̲s̲s̲a̲g̲e̲s̲
Reference tracks
Commands
Rebroadcast information
Management information
A̲T̲D̲L̲ ̲m̲e̲s̲s̲a̲g̲e̲s̲
Reference tracks
Status reports
Link monitoring
M̲B̲D̲L̲ ̲R̲e̲f̲e̲r̲e̲n̲c̲e̲ ̲t̲r̲a̲c̲k̲s̲
MILI reads the information and sends it to MITRAM.
MITRAM updates the trackfile and thereby causes AMES
to generate track reports which are sent to the batteries
via ALI.
M̲B̲D̲L̲ ̲C̲o̲m̲m̲a̲n̲d̲s̲
MILI reads the information and sends it to MITRAM.
Dependent of the contained track information, MITRAM
may update the trackfile as for reference tracks. The
command information is sent to COSTA who converts it
to ATDL commands which is sent to the batteries via
ALI.
M̲B̲D̲L̲ ̲R̲e̲b̲r̲o̲a̲d̲c̲a̲s̲t̲ ̲I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲
MILI reads the information and uses it for either statistical
calculation of error rate on MBDL lines or for updating
of adjacent battalion information.
M̲B̲D̲L̲ ̲M̲a̲n̲a̲g̲e̲m̲e̲n̲t̲ ̲I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲
MILI reads the information and sends it to MITRAM.
Management information concerning ID conflicts may
be sent to EDIM while Pointer information may be sent
to a battery via ALI to a battery.
A̲T̲D̲L̲ ̲R̲e̲f̲e̲r̲e̲n̲c̲e̲ ̲T̲r̲a̲c̲k̲s̲
ALI reads the information and sends it via ASUM to
ATRAM. ATRAM updates the trackfile and thereby causes
AMES to forward the tracks via ALI to other batteries.
A̲T̲D̲L̲ ̲S̲t̲a̲t̲u̲s̲ ̲R̲e̲p̲o̲r̲t̲s̲
ALI reads the information and sends it via ASUM and
ATRAM to COSTA. COSTA converts the status reports to
MBDL representation and sends it via MILI to the TSQ-38.
A̲T̲D̲L̲ ̲L̲i̲n̲k̲ ̲M̲o̲n̲i̲t̲o̲r̲i̲n̲g̲
ALI reads testmessages and sends them to ASUM who checks
the testmessages and reports errors to EDIM. ASUM generates
testmessages which are sent to the batteries via ALI.
3.2 D̲E̲S̲C̲R̲I̲P̲T̲I̲O̲N̲ ̲O̲F̲ ̲S̲/̲W̲ ̲M̲O̲D̲U̲L̲E̲S̲
1 A̲L̲I̲:̲ ̲ ̲A̲T̲D̲L̲ ̲L̲I̲N̲E̲ ̲H̲A̲N̲D̲L̲E̲R̲
ALI represents the software interface to the ATDL Line
Terminating Units. All received ATDL messages will
be handed over to ASUM. ATDL messages to be transmitted
are received from AMES, ASUM, ATRAM and COSTA via 32
buffer queues, one queue for each transmission line
for each module.
2 A̲S̲U̲M̲:̲ ̲ ̲A̲T̲D̲L̲ ̲L̲I̲N̲E̲ ̲S̲U̲R̲V̲E̲I̲L̲L̲A̲N̲C̲E̲ ̲M̲O̲D̲U̲L̲E̲
ASUM surveys the ATDL transmission lines by means of
ATDL test messages which both are originated from and
are received by this module. Messages that do not participate
in the link monitoring procedure are handed over to
ATRAM.
3 A̲T̲R̲A̲M̲:̲ ̲ ̲A̲T̲D̲L̲ ̲T̲R̲A̲C̲K̲F̲I̲L̲E̲ ̲M̲A̲N̲A̲G̲E̲R̲
ATRAM is responsible for the Trackfile updates, the
conflict detection and reporting and the immediate
forwarding of some ATDL messages. Command and status
messages are handed over to COSTA.
4 A̲M̲E̲S̲:̲ ̲A̲T̲D̲L̲ ̲M̲E̲S̲S̲A̲G̲E̲ ̲S̲E̲Q̲U̲E̲N̲C̲E̲R̲
AMES is responsible for the forwarding of track reports.
All relevant data are extracted from the Trackfile
and combined to form reports in accordance with the
last updates made by ATRAM.
5 M̲I̲L̲I̲:̲ ̲M̲B̲D̲L̲ ̲L̲I̲N̲E̲ ̲H̲A̲N̲D̲L̲E̲R̲
MILI represents the software interface to the MBDL
Line Terminating Units. Most received MBDL messages
are handed over to MITRAM. Only re-broadcast messages
are processed by MILI itself. Messages to be transmitted
are received from COSTA. A queue effect is incorporated
in these message exchanges.
6 M̲I̲T̲R̲A̲M̲ ̲M̲B̲D̲L̲ ̲T̲R̲A̲C̲K̲F̲I̲L̲E̲ ̲M̲A̲N̲A̲G̲E̲R̲
MITRAM performs the analysis of the MBDL messages received
from MILI. If a mesage is of reference type, MITRAM
is responsible for the full Trackfile update and conflict
detection. Messages informing ATRAM about new alert
or conflict situations are sent when needed. If a message
contains an ENGAGE ̲A command, the basic processing
concerning the affected track is performed and thereafter
relevant data are handed to COSTA for the final processing.
The ENGAGE ̲B management message is used as Down Link
Pointer. This pointer may be sent to a battery via
ALI and stored in the Common Area for DSI usage. The
ENGAGE ̲C message is used to clear ID conflicts. When
an ID conflict is cleared this is reported to EDIM.
7 C̲O̲S̲T̲A̲:̲ ̲C̲O̲M̲M̲A̲N̲D̲ ̲A̲N̲D̲ ̲S̲T̲A̲T̲U̲S̲ ̲H̲A̲N̲D̲L̲E̲R̲
COSTA is responsible for the command/status exchange
between the BOC and the batteries. The module handles
the synchronization between status messages from the
ATDL side of the AMC and operator commands from the
MBDL side. At the ATDL side ATDL messages are received
from ATRAM and ATDL messages are sent to ALI. Correspondingly
MBDL messages at the MBDL side are received from MITRAM
and MBDL messages are sent to MILI. Information from
battery status messages and the status reported uplinks
via MILI are stored in a special file in the Common
Area.
8 C̲O̲M̲M̲O̲N̲:̲ ̲C̲O̲M̲M̲O̲N̲ ̲A̲R̲E̲A̲ ̲M̲O̲D̲U̲L̲E̲
COMMON contains the Common Data Area in its local data
area. Included in this area is the Trackfile. At system
startup COMMON is responsible for the initialization
of the Common Area and for the startup sequence of
all modules in the AMC software system.
9 E̲D̲I̲M̲:̲ ̲E̲R̲R̲O̲R̲ ̲D̲I̲S̲P̲L̲A̲Y̲ ̲M̲O̲D̲U̲L̲E̲
EDIM represents the software interface to the Operators
Panel. EDIM receives data originated by the operator
about link start/stop and positional information and
sends the data to the relevant Modules. EDIM informs
the operator about link states and about ID conflicts.
EDIM receives this information from ASUM, ATRAM, MITRAM,
ALI and MILI.
10 C̲O̲R̲I̲N̲A̲:̲ ̲ ̲C̲O̲O̲R̲D̲I̲N̲A̲T̲E̲ ̲I̲N̲P̲U̲T̲ ̲H̲A̲N̲D̲L̲E̲R̲
CORINA receives messages from EDIM containing positional
information. The processed data are stored in the Common
Area.
11 T̲I̲M̲O̲:̲ ̲ ̲T̲I̲M̲E̲R̲ ̲M̲O̲D̲U̲L̲E̲
TIMO implements an internal clock to the AMC by which
the modules can request an event after a specified
time elapse. The content of the requested event is
specified by the requesting module itself.
12 A̲P̲U̲:̲ ̲ ̲A̲T̲D̲L̲ ̲P̲A̲C̲K̲/̲U̲N̲P̲A̲C̲K̲ ̲M̲O̲D̲U̲L̲E̲
APU is a set of procedures used to convert the ATDL
message formats to an internal representation (unpack)
or to convert it in the opposite direction (pack).
13 C̲O̲R̲M̲:̲ ̲ ̲C̲O̲R̲R̲E̲L̲A̲T̲I̲O̲N̲ ̲M̲O̲D̲U̲L̲E̲
CORM is a set of procedures that are called by the
trackfile managers. The procedures perform correlation
check between specified coordinates and the tracks
kept in the Trackfile.
14 R̲E̲C̲P̲R̲O̲-̲R̲E̲C̲O̲R̲D̲ ̲A̲N̲D̲ ̲S̲Y̲S̲T̲E̲M̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲S̲
RECPRO contains procedures for creation and removal
of records in the Trackfile, reservation and release
of the Trackfile and a local action procedure common
for most of the software modules.
15 M̲C̲O̲N̲V̲E̲R̲T̲ ̲-̲ ̲M̲B̲D̲L̲/̲A̲T̲D̲L̲ ̲C̲O̲N̲V̲E̲R̲S̲I̲O̲N̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲S̲
MCONVERT contains procedures for conversion of coordinates
between MBDL and ATDL representation.
16 A̲C̲O̲N̲V̲E̲R̲T̲ ̲-̲ ̲A̲T̲D̲L̲/̲M̲B̲D̲L̲ ̲C̲O̲N̲V̲E̲R̲S̲I̲O̲N̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲S̲
ACONVERT contains procedures for conversion of geographical
battery position data and battery relative track positions
to AMC relative coordinates.
17 A̲M̲C̲N̲A̲M̲E̲S̲ ̲-̲ ̲A̲M̲C̲ ̲N̲A̲M̲E̲S̲ ̲D̲E̲F̲I̲N̲I̲T̲I̲O̲N̲ ̲M̲O̲D̲U̲L̲E̲
AMCNAMES defines the symbolic names for all data areas
in the Common Area and for various constants. These
names are used by all software modules when they access
data in the Common Area or for interprocess communication.
18 A̲M̲C̲G̲E̲N̲1̲
AMCGEN1 includes the standard header generation file
X2GEN1 and extends it with special save locations to
be used by the various procedures in the AMC system.
AMCGEN1 also includes the names defined by AMCNAMES.
AMCGEN 1 must be included in all modules that want
access to the Common Area.
19 T̲E̲S̲T̲A̲:̲ ̲ ̲T̲E̲S̲T̲B̲O̲X̲ ̲H̲A̲N̲D̲L̲E̲R̲
TESTA is the module that executes immediately after
masterclear. It determines whether a testrun or normal
operation shall be entered. During normal operation
of the AMC, this module is inactive. When a testrun
is wanted, a testbox is connected to the system and
TESTA is then responsible for loading the test modules
from the testbox. During a testrun, the ordinary functions
of the AMC are aborted and a hardware checkout is made
instead.
20 X̲T̲O̲M̲O̲:̲ ̲ ̲S̲P̲E̲C̲I̲A̲L̲ ̲T̲E̲S̲T̲O̲U̲T̲P̲U̲T̲ ̲M̲O̲D̲U̲L̲E̲
XTOMO replaces TOMO in the operational AMC system.
XTOMO implements only a procedure that responds correctly
to a call of the testoutput generation procedure but
without generating any test data.
21 R̲T̲C̲:̲ ̲ ̲R̲E̲A̲L̲ ̲T̲I̲M̲E̲ ̲C̲L̲O̲C̲K̲
RTC implements a 10ms timing and rescheduling base
in the AMC system. RTC includes monitor procedures
for access of the time information in the Common Area.
22 B̲I̲M̲:̲ ̲ ̲B̲U̲F̲F̲E̲R̲ ̲I̲N̲T̲E̲R̲C̲H̲A̲N̲G̲E̲ ̲M̲A̲N̲A̲G̲E̲R̲
BIM implements procedures for exchange of fixed length
buffers between modules by means of queues referenced
by queue numbers.
23 F̲L̲O̲A̲T̲:̲ ̲ ̲F̲L̲O̲A̲T̲I̲N̲G̲ ̲P̲O̲I̲N̲T̲ ̲M̲O̲D̲U̲L̲E̲
FLOAT implements procedures for floating point calculations
(ADD, SUB, MUL, DIV, COS, SIN, SQRT).
24 I̲N̲I̲T̲L̲I̲S̲T̲
INITLIST contains information for kernel initialization
and addresses of software modules in the PROM area.
25 A̲M̲C̲K̲E̲R̲N̲E̲L̲
AMCKERNEL is a special version of the CR80 AMOS KERNEL.
26 R̲O̲O̲T̲
ROOT performs initialization of all modules after kernel
initialization.
27 I̲D̲L̲E̲
IDLE process is executing when no other modules want
execution time.
28 X̲2̲G̲E̲N̲1̲,̲ ̲X̲2̲G̲E̲N̲2̲
Program and Data header generation modules.
29 S̲2̲S̲Y̲S̲S̲
Standard AMOS names definition module.
30 R̲O̲M̲C̲H̲K̲
ROMCHK surveys the checksum of the PROM area. An illegal
checksum causes a system error.
4 A̲T̲D̲L̲ ̲E̲N̲C̲R̲Y̲P̲T̲I̲O̲N̲
To the standard AMC can be delivered a crypto rack
for mounting on top of the AMC. This rack is designed
to contain 8 KG84 crypto devices. These crypto devices
cannot be delivered by CRA, but signal and power cables
can be delivered. The encryption is performed on the
digital ATDL signal between ATDL LTU…08…s and ATDL modems.
5 A̲T̲D̲L̲/̲M̲B̲D̲L̲/̲L̲I̲N̲K̲ ̲1̲ ̲C̲O̲N̲V̲E̲R̲T̲E̲R̲
The following description is based on a short review
of the LINK 1 specification STANAG No. 5501 dated 25.
september 1973.
In the ATDL/MBDL Converter only little capability exists
for the exchange of reference tracks/track data between
the NADGE system and the IHAWK batteries. Therefore,
it is recommended to extend the ATDL/MBDL Converter
with a LINK 1 communication line for connection to
the NADGE system. Thereby track data may be transferred
to the batteries via the Converter while commands still
must be transmitted via the MBDL data links.
Below is shown a principle diagram for the HAWK - AMC
- TSQ - NADGE system with LINK 1 connection between
AMC and NADGE.
Incorporation of the LINK 1 communication with NADGE
in the standard AMC S/W system will introduce several
new S/W modules and extension of some of the existing
modules.
The new modules necessary to implement the LINK 1 communication
are:
o LINK 1 Line Handler
o LINK 1 Message Sequencer
o LINK 1 Line Surveillance Module
o LINK 1 Track File Manager
o ATDL/LINK 1 Data Flow Control Module
The modules to be extended are:
o Correlation Module
o ATDL Track File Manager
o MBDL Track file Manager
Further the trackfile layout of the AMC must be changed.
In the table below is made a comparison between ATDL,
MBDL and LINK 1 formats, to see the correspondance
between messages in the three formats.
ATDL MBDL LINK 1
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Test Message…0e…1)…0f… No equivalent Test Message…0e…1)…0f…
Air Track Pos. Msg. Partial equivalent…0e…2)…0f… Basic Track Info.Msg.
Air Pos.Ampl. Msg. Ampl.Track Info. Msg.
ECM Intercept Data No equivalent Strobe Message
IFF/SIF Message No equivalent SIF Information
Management Msg. (Info)…0e…3)…0f… No equivalent Management Msg.…0e…3)…0f…
Mngmt. Msg. (Pointer) No equivalent No equivalent
Special Point Pos. Msg. Partial equiv.…0e…4)…0f… Not applicable
Data Ref. Pos. Msg. No equivalent…0e…5)…0f… Not applicable…0e…5)…0f…
Weapon/Engagement Status Partial equivalent…0e…2)…0f… No equivalent
Command Message Partial equivalent…0e…2)…0f… No equivalent
N̲O̲T̲E̲S̲:
1) The ATDL and LINK 1 Test Messages are not equivalent;
they are used by the converter to monitor the status
of the data link.
2) Only minor part of the information contained in
the ATDL Message is available in the MBDL Messages.
3) Not totally equivalent but used for management
in the converter.
4) Position of batteries reported in MBDL when status
is stand-by.
5) All MBDL reporting is relative to the same coordinate
center. LInK 1 uses fixed, programmed locations
of sites.
6 I̲T̲D̲L̲/̲M̲B̲D̲L̲ ̲C̲O̲N̲V̲E̲R̲T̲E̲R̲
Instead of using the confidential ATDL format the communication
with the batteries the converter may be modified to
use IDL. We do not have any specification for ITDL.
However, we have a specification for a message format
denoted IDL (International Data Link) dated 7th November,
1976. A cursory inspection of this document shows that
ATDL and IDL uses the same message types and (sometimes
with different denotation) and specifies the same operational
usage of messages, but the fields within each type
of message are allocated at different bit position.
We expect to be able to use the existing ATDL LTU and
ATDL Modem unchanged, but further investigations are
necessary to determine the exact deviations.
We do not have any knowledge of whether the HAWK batteries
are able to communicate in IDL.
7 P̲H̲Y̲S̲I̲C̲A̲L̲ ̲P̲A̲R̲A̲M̲E̲T̲E̲R̲S̲
A standard AMC has the following physical characteristics:
Weight: 140 kg.
Dimensions: Depth: 564mm,
Height: 1160mm,
Width: 580mm
Power Consumption:350 W, 220V/110V +̲5%, 50 or 60 Hz
Environment: 18 - 43…0e…o…0f…C (operational)
The AMC has beeen designed and tested to meet the requirements
of NGTS-40, MPD 7005, MIL STD 805 with some deviations.
8 D̲I̲S̲P̲L̲A̲Y̲ ̲S̲Y̲S̲T̲E̲M̲
CRA has completed the development of a Display System
Interface (DSI), which extracts track data and status
information from the AMC and communicates the information
to a Display System. The Display System and a total
renewing of the old TSQ-38 system is currently under
development at AEG-TELEFUNKEN. The operator of the
upgraded TSQ will then have an overview of the total
air situation for own battallion and some status information
from remote battallions.
The DSI is mounted on top of the AMC as shown in the
figure on the next page.
9 T̲R̲A̲I̲N̲I̲N̲G̲
In connection to the development of the AMC system,
CRA has developed training courses for BOC operators
and maintenance personnel.
FRONT VIEW OF AMC-DSI RACK ASSEMBLY
