EM120 Multibeam Echo Sounder Maintenance Manual Rev A

Maintenance manual
EM120 Multibeam echo sounder

Base version
EM 120 Multibeam echo sounder

Maintenance manual -- Base version
852-164111 / AA000 / 2-24
Note Kongsberg Simrad AS makes every effort to ensure that the information contained within this document is correct. However, our equipment is continuously being improved and updated, so we cannot assume liability for any errors which may occur. The information contained within this document remains the sole property of Kongsberg Simrad. No part of this document may be copied or reproduced in any form or by any means, and the information contained within is not to be communicated to a third party, without the prior written consent of Kongsberg Simrad AS. Warning The equipment to which this manual applies must only be used for the purpose for which it was designed. Improper use or maintenance may cause damage to the equipment or injury to personnel. The user must be familiar with the contents of the appropriate manuals before attempting to operate or work on the equipment. Kongsberg Simrad AS disclaims any responsibility for damage or injury caused by improper installation, use or maintenance of the equipment.
Kongsberg Simrad AS, P.O.Box 111, N-3191 Horten, Norway Telephone: +47 32 86 50 00, Telefax: +47 32 73 58 85
Maintenance manual
Sections
This book is the Maintenance manual for the EM 120 multibeam echo sounder. It describes how to perform intermediate maintenance on the system.
Introduction
This section presents a general introduction to the echo sounder system, and defines the maintenance philosophy. Refer to page 1.
2 3
Technical specifications
This chapter presents the main technical specifications. Refer to page 5.
Cable layout and interconnections

This chapter describes the cabling, and details the necessary cable specifications. Refer to page 9.
Transceiver Unit
This chapter describes the design and operation of the Transceiver Unit. Each circuit board is explained, as well as overall block diagrams and the theory of operation. Refer to page 35.
Preamplifier Unit
This chapter describes the design and operation of the Preamplifier Unit. Each circuit board is explained, as well as overall block diagrams and the theory of operation. Refer to page 96.
Tx Junction Box
This chapter describes the design and operation of the TX Junction Box. Refer to page 112.
Troubleshooting
This chapter provides basic procedures for automatic and traditional troubleshooting. Refer to page 113.
Replacement procedures
This chapter explains how to perform replacement of the line replaceable units (LRU). Refer to page 155.
Datagram formats
The formats for data input and output to and from the EM Series multibeam echo sounders are described here. Refer to page 166.
10
System administration
This chapter provides basic reference information useful for the EM 120 system supervisor. Refer to page 209.
852--164111 / A
Kongsberg Simrad EM 120 Multibeam echo sounder
Base version
11
Spare parts
This chapter provides a listing of the line replaceable units with illustrations and order numbers. Refer to page 242.
12
Drawing file
II
852--164111 / A
Maintenance manual
Remarks
References
Further information about the EM 120 system may be found in the following manuals: EM 120 Operator manual EM 120 Installation manual
The reader
This maintenance manual is intended to be used by a trained maintenance technician or engineer, with experience of electronic and digital circuitry, computers and electromechanical design. The level of information is based on Kongsberg Simrads maintenance philosophy: The onboard technical personnel shall, with the help of the documentation and the systems built- in test functions, be able to identify malfunctions, locate the fault, and replace major parts, modules and components on the Line Replaceable Unit (LRU) level. He/she will however not attempt to repair the LRUs.
852--164111 / A
III
Base version
Table of Contents
1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 1.2 1.3 1.4 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maintenance philosophy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Note about changing AC supply voltage . . . . . . . . . . . . . . . . . . . . . . . . List of units and main subunits . . . . . . . . . . . . . . . . . . . . . . . . . . Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Physical properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restrictions for use -- limitations . . . . . . . . . . . . . . . . . . . . . . . . . Surface finish . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operating and storage temperature . . . . . . . . . . . . . . . . . . . . . . System performance data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1
1 1 2 4
TECHNICAL SPECIFICATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5
5 5 6 7 8 8 8 8
CABLE LAYOUT AND INTERCONNECTIONS . . . . . . . . . . . . . . . . . . .

3.1 3.2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cable layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Shipyard and system cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cable specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Serial lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transducer cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cable terminations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . W102 -- Serial line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . W103 -- RS--232 Serial line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . W105 -- Coax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . W301 W202 W400 W502 ----AC power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote synchronization and On/Off . . . . . . . . . . . . . . Ethernet RJ45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9
9 10 10 10 13 13 13 14 15 15 16 17 18 19 20 21 22 23 24 25 26 26
3.3
3.4
W503 -- Keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . W504 -- Mouse or Pointing device . . . . . . . . . . . . . . . . . . . . . . . . W505 -- Centronics printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transducer cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5
IV
852--164111 / A
Maintenance manual
Transmit array cable markings . . . . . . . . . . . . . . . . . . . . . . . . . . Receive array cable markings . . . . . . . . . . . . . . . . . . . . . . . . . . . Cables between Tx Junction Box(es) and Transceiver Unit . Cables between Preamplifier Unit and Transceiver Unit . . .
26 29 31 32
TRANSCEIVER UNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1 Description and main functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Processing Rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Receiver Rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Transmitter Rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The rear panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Theory of operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Simplified block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Control functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Processing rack details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Circuit boards and modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Receiver rack details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Circuit boards and modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transmitter rack details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Circuit boards and modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Circuit board descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4--Ports Serial Line Board (C114P) . . . . . . . . . . . . . . . . . . . . . . . Beamformer & Signal Processor (BSP) . . . . . . . . . . . . . . . . . . . Ethernet Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ROM board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Control Processor Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Processing Unit Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . Motherboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transmitter/Receiver Board (TRB) . . . . . . . . . . . . . . . . . . . . . . . Low Voltage Power Unit (LVPU) . . . . . . . . . . . . . . . . . . . . . . . . . High Voltage Power Supply (HV2PS2) . . . . . . . . . . . . . . . . . . . Signal Processor Board (SPB31) . . . . . . . . . . . . . . . . . . . . . . . . . Receiver Backplane (RXBP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64--Channel Transmitter (TX64) . . . . . . . . . . . . . . . . . . . . . . . . .
35
35 35 38 40 41 41 42 42 42 43 45 45 45 46 46 46 47 47 47 48 48 49 54 57 59 60 65 67 68 71 75 77 83 87
4.2
4.3
4.4
4.5
4.6
852--164111 / A
Base version
Transmitter Backplane (TXBP) . . . . . . . . . . . . . . . . . . . . . . . . . .
91
PREAMPLIFIER UNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1 5.2 Description and main functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Theory of operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Simplified block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Control functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preamplifier Unit details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Circuit boards and modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Circuit board descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Simplified block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preamplifier (DP16) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preamplifier Unit Power Supply (PAPS) . . . . . . . . . . . . . . . . . . Preamplifier Backplane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setup messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setup messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Launchpad messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Launchpad messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ESO messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ESO messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sound Speed Profile Editor messages . . . . . . . . . . . . . . . . . . . . . . . . . . . Sound Speed Profile Editor messages . . . . . . . . . . . . . . . . . . . . Ping Display messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ping Display messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CPU CMOS SETUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setup for SSC--486H . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setup for SSC--5x86H . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
96
96 96 99 99 99 99 99 100 100 101 101 101 102 107 108
5.3 5.4
6 7
TX JUNCTION BOX(ES) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1 7.1 7.2 7.3 7.4 7.5 7.6
112
112
TROUBLESHOOTING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
113
113 113 115 115 122 122 142 142 145 145 147 147 148 150 150 152 155 155
7.7
REPLACEMENT PROCEDURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

8.1
VI
852--164111 / A
Maintenance manual
8.2
Tools required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transceiver Unit procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Circuit boards and modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fan drawers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Heater element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . High Voltage Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AC mains circuit breaker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AC mains filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fuse replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TX64 Fuse replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fan drawers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Presentation format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Input datagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Attitude data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sound Speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Depth input from single beam echo sounder . . . . . . . . . . . . . . Remote control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Depth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Raw range and beam angle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Seabed image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Central beams echogram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Height . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Attitude . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Heading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mechanical transducer tilt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Surface sound speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sound speed profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Kongsberg Simrad SSP output . . . . . . . . . . . . . . . . . . . . . . . . . .
156 157 157 157 159 159 160 160 161 161 162 163 165 166 166 167 167 167 174 178 178 182 183 186 187 190 190 192 193 194 195 195 196 197 197 198 199 200
DATAGRAM FORMATS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

9.1 9.2 9.3
852--164111 / A
VII
Base version
Single beam echo sounder depth . . . . . . . . . . . . . . . . . . . . . . . . . Runtime parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
200 201 204 209 210 210 211 211 211 211 212 212 212 213 214 214 215 215 216 216 216 216 231 231 231 231 232 232 232 232 234 235 235 235 235 235 236 241
10
SYSTEM ADMINISTRATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

10.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.2 Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EM 120 Installation setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.3 EM 120 File system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Survey files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sound speed profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Absorption coefficient file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workstation I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Echo sounder parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BIST files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logfiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operator configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Survey jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TOC files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.4 File formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Survey format and I/O library . . . . . . . . . . . . . . . . . . . . . . . . . . . The survey format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.5 Survey Predefined Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . File locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Survey Predefined Files . . . . . . . . . . . . . . . . . . . . . . . 10.6 Projection data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scope and purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Projection overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Projection protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.7 Dynamic Projection Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dynamic projection library definitions . . . . . . . . . . . . . . . . . . . . Dynamic projection library protocol . . . . . . . . . . . . . . . . . . . . . . Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
VIII
852--164111 / A
Maintenance manual
11
SPARE PARTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

11.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2 Spares data presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Spares table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parts list codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.3 Transceiver Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Processing Rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Receiver Rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 242 242 243 244 244 245 247 249 249
12
DRAWING FILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

12.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2 Drawing list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
852--164111 / A
IX
Base version
Document logistics
Rev A B C D E F G
(The original signatures are recorded in the companys logistic database.)
Date 04.01.01
Written EGj
Checked BHL
Approved EHa
Rev A B C D Original issue.
Comments
To assist us in making improvements to the product and to this manual, we would welcome comments and constructive criticism. Please send all such - in writing or by e- mail - to: Kongsberg Simrad AS Documentation Department P.O.Box 111 N- 3191 Horten Norway or e- mail: [email protected]
852--164111 / A
Maintenance manual
High voltage safety warning

The voltages used to power this equipment are potentially lethal. Even 110 volts can kill.
Whenever possible, the following precautionary measures should be taken before any work is carried out inside the equipment: Switch off all high- voltage power supplies. Check the operation of any door interlocks and any other safety devices. Completely discharge all high- voltage capacitors.
2 Open his mouth and check for and remove any false teeth, chewing gum etc.
Check if the victim is breathing. If not, check if his heart is beating. The pulse is normally easily found in the main arteries of the neck, either side of the throat, up under the chin. If his heart is beating but he is not breathing, commence ARTIFICIAL RESPIRATION. If the victims heart is not beating, commence EXTERNAL CARDIAC MASSAGE (ECM). Continue to shout for assistance till someone arrives.
It should be noted that interlocks and safety devices are normally located only at regular access points, and high voltages may be exposed during dismantling.
EXTERNAL CARDIAC MASSAGE 1 Kneel beside the victim. Place the heel of one hand in the centre of his chest, at a position half way between the notch between the collar- bones at the top of his chest, and the dip in the breast- bone at the base of his rib cage. Place the other hand on top of the first. 2 Keeping the arms straight and using your entire weight, press down rapidly so that the breast bone is depressed four- five cm, then release the pressure. Repeat rhythmically at a rate of one cycle per second. This will be hard work, but keep going. His life depends on YOU. Do not worry about breaking his ribs - these will heal if he survives.
NEVER WORK ALONE ON HIGH-VOLTAGE EQUIPMENT!
FIRST AID IN THE EVENT OF ELECTRIC SHOCK

Normally, even a high voltage electric shock will not kill instantly. The victim can still be revived even when his breathing and heart- beat have ceased. Could YOU save someones life? In the event of electric shock, the correct actions, performed quickly may well save the victims life. Make sure you know what to do!
Immediate action
While shouting for help, remove the source of power from the victim. Switch off the supply if possible, or using a dry, non- conductive material (rubber gloves, broom handle etc.) to insulate yourself, separate the victim from the source. If the voltage exceeds 1000 volts, switch off the supply and be ready to catch the victim. Take care- do not become a victim yourself. Commence first aid on the spot. Continue to shout for assistance till someone arrives.
1 Lay the victim flat on his back and loosen any tight clothing (collar, tie, belt etc.).
852--164111 / A
XI
Base version
ARTIFICIAL RESPIRATION
1 Kneel besides the victims head. Place one hand under his neck and lift, allowing his head to fall back. This will lift his tongue and open the air passage in his throat. 2 Place the palm of the hand on his forehead to maintain the chin- up position. 3 Using the index finger and thumb of the same hand, pinch the victims nostrils closed. Open his mouth. 4 Take a deep breath and cover his mouth with yours. Blow steadily into his lungs to expand his chest. Remove your mouth from his to allow the air to escape from his chest. You should be able to see his chest deflate. 5 Repeat the inflation- deflation cycle at a rate of about 12 cycles per minute till the victim begins to breath normally again.
If started quickly and performed correctly, the resuscitation methods described will keep a sufficient volume of oxygenated blood flowing trough the victims body to allow full recovery. Proficiency in the resuscitation methods can only be achieved trough training. All personnel concerned should attend courses on a regular basis. Remember, someones life could depend on you.
DO YOU KNOW WHAT TO DO?
COMBINING EMC AND ARTIFICIAL RESPIRATION

If you are alone, perform ONE cycle of artificial respiration for every FIVE cycles of EMC. This will be hard work, but keep going. His life depends on YOU! If there are other people available to help, one should perform the EMC while one performs the artificial respiration for every five cycles of EMC. It will be much more efficient with two people. Once the victims heart is beating and he is breathing, roll him onto his side and support him in that position. As consciousness returns he may vomit, and this will allow any liquid to drain out of his mouth. Remove the victim to a hospital as soon as possible, but do not interrupt the artificial respiration and EMC cycles till his heart beat and breathing returns.
XII
852--164111 / A
Introduction
1
1.1
INTRODUCTION
Overview
This is the maintenance manual for the Kongsberg Simrad EM 120 multibeam echo sounder system. The manual contains detailed descriptions of each of the units in the system. Each circuit board and mechanical assembly is described. The manual also describes the troubleshooting process based on the Built- In Self test (BIST) software, and it includes procedures for disassembly and reassembly of the replaceable items. This manual does not describe the maintenance of the Operator Station and the peripheral devices (printers, plotters and sensors). For information about these items, refer to the applicable manufacturers documentation.
1.2
Maintenance philosophy
Kongsberg Simrad AS defines three levels for maintenance manuals: Organizational - You will only perform limited preventive and corrective maintenance on the system. There is no need for technical education or training, and no need for any instruments. Typical tasks are exterior cleaning, or changing fuses. Intermediate - You will perform overall preventive and corrective maintenance on the system. It is recommended that you are an educated engineer with experience from computerized design and mechanical systems. It is further expected that you can use standard electronic instruments, such as an oscilloscope. You should be trained by Kongsberg Simrad to perform maintenance on the system. Typical tasks may include troubleshooting, testing and circuit board replacement. Depot - You will perform detailed maintenance on the system and on the circuit boards and modules. You must be an educated engineer with experience of computerized design and mechanical systems. It is further expected that you can use standard electronic instruments, such as an oscilloscope. You should be trained by Kongsberg Simrad to perform maintenance on the system. Typical tasks are circuit board repair.
Note !
This maintenance manual is prepared for the intermediate level.
852--164111 / A
Base version
1.3
System overview
The EM 120 is designed to do mapping to full ocean depth with an hitherto unsurpassed resolution, coverage and accuracy. The receive transducer is wideband and in conjunction with a separate low frequency transmit transducer, the EM 120 may optionally be able to deliver sub- bottom profiling capabilities with a very narrow beamwidth. The nominal sonar frequency is 12 kHz with an angular coverage sector of up to 150 and 191 beams per ping as narrow as 1. The angular coverage sector and beam pointing angles may be set to vary automatically with depth according to achievable coverage. This maximizes the number of usable beams. The beam spacing is normally equidistant with equiangle available. The transmit fan is split in several individual sectors with independent active steering according to vessel roll, pitch and yaw. This place all soundings on a best fit to a line perpendicular to the survey line, thus ensuring a uniform sampling of the bottom and 100% coverage. The sectors are frequency coded (11.25 to 12.60 kHz), and they are all transmitted sequentially at each ping. The steering is fully taken into account when the position and depth of each sounding is calculated, as is the refraction due to the sound speed profile, vessel attitude and installation angles. Pulse length and range sampling rate are variable with depth for best resolution, and in shallow waters due care is taken to the near field effects. The ping rate is only limited by the round trip travel time in the water up to a ping rate of 5 Hz. The EM 120 transducers are linear arrays in a Mills cross configuration with separate units for transmit and receive. The arrays are divided into modules, these may be replaced by a diver. The number of modules used (and hence the beamwidth) may be adjusted according to particular installation requirements. For both arrays 1 and 2 beamwidths are standard options, and 4 beamwidth is available for the receive array. The resulting array lengths are between 2 and 8 m. The Kongsberg Simrad EM 120 is a complete system. All necessary sensor interfaces, data displays for quality control and sensor calibration, seabed visualization, and data logging are a standard part of the system, as is integrated seabed acoustical imaging capability (sidescan). A combination of phase and amplitude detection is used, resulting in a measurement accuracy practically independent of beam pointing angle. Postprocessing software is available from both Kongsberg Simrad and third- party suppliers. A world- wide marketing and service organization having many years of multibeam experience is in place for supporting the EM 120.
852--164111 / A
Introduction
System diagram
Operator Station
Interfaces: Sound Speed Sensor Tide Center depth output Ethernet and serial lines (data i/o)
Optional
Sub Bottom Profiler Transceiver Unit (Option)
Transceiver Unit
Remote Control
Preamplifier Unit
TX Junction Box no.1
8 --- 24 -- 12 -- 12
-- 16
24 -- -- 24
Receive transducer array Transmit transducer array
Figure 1 - System diagram
852--164111 / A
(CD3387e/GIF/WMF)
Internal Ethernet
Interfaces: Positioning systems Attitude (roll, pitch and heave) Heading Clock Trigger input/output Clock synchronization
Base version
1.4
Note about changing AC supply voltage

The EM 120 is wired for 230 Vac when it comes from the factory. If it is desireable to change to 115 Vac, do the following: The PU power must be rewired. The switch on the LVPU must be rewired. The preamplifier must be rewired. The 220 Vac fans must be changed to 115 Vac type.
Refer to page 165.
852--164111 / A
Technical specification
TECHNICAL SPECIFICATIONS
Kongsberg Simrad is engaged in continuous developments of its products and reserves the right to alter specifications without prior notice.
Note !
List of units and main subunits

Operator station - The Operator Station may contain a number of subunits and peripherals (for example storage units, printers and plotters). The configuration of these will be defined by the user. Transceiver Unit Preamplifier Unit TX Junction Box(es) Transmit Transducer Array Receive Transducer Array Junction Box - Normally, a single Junction Box is used for on/off and remote control. Additional junction boxes may need to be added if required to splice cables or add special functions.
Interfaces
Serial lines with operator adjustable baud rate, parity, data length and stop bit length for: - Motion sensor (roll, pitch, heave and optionally heading) in format supported by sensors from Applied Analytics, Seatex and TSS - Gyrocompass in either NMEA 0183 HDT or SKR82/LR60 format - Positions in either Simrad 90, NMEA 0183 GGA or GGK format - External clock in NMEA 0183 ZDA format - Sound speed profile - Sound speed at transducer - Sea level height (tide) - Output of depth straight down in NMEA 0183 DPT format Interface for 1 PPS (pulse per second) clock synchronisation signal SCSI interface for tape drive (DAT or Exabyte), additional disk drives and optional greyscale recorder for seabed image Parallel interface for Postscript colour graphics printer/plotter
852--164111 / A
Base version
Ethernet interface for input of sound speed profile data and output of all data normally logged to disk and/or tape
Physical properties
Transmit transducer Module length Width Height Module weight Frame length Receive transducer Module length Width Height Module weight Frame length Transceiver Unit Physical dimensions Height Width Depth Weight Power Preamplifier Unit Physical dimensions Height Width Depth Weight Power TX Junction Box Physical dimensions Also see drawing 834- 213111 Also see drawing 834- 213112 920 mm 600 mm 630 mm Approx 96 kg 100 to 240 Vac, < 300 Vac, 47 to 63 Hz Also see drawing 830- 211291 1760 mm 600 mm 630 mm 197 kg 100 to 240 Vac, < 1800 Vac, 47 to 63 Hz 447 mm 342 mm (400 mm with frame) 120 mm (170 mm with frame) 24 kg 1808 (4_), 3600 (2_) or 7200 (1_) mm 179 / 132 mm 760 mm (900 mm with frame) 220 mm (280 mm with frame) 58 kg 4020 (2_) or 7770 (1_) mm
852--164111 / A
Technical specification
Height Width Depth Weight Operator Station
440 mm 500 mm 303 mm 15.5 kg
Dimensions and weight will depend upon choice of workstation model, thus the following figures serve as a guideline only. Chassis height Chassis width Chassis depth Chassis weight Monitor height Monitor width Monitor depth Monitor weight External storage unit height External storage unit width External storage unit depth External storage unit weight 103 mm 418 mm 443 mm 10 kg 487 mm 475 mm 506 mm 31 kg 68 mm 190 mm 310 mm 3 kg
Power requirements
Operational voltage and frequency The single phase supply must be protected with 16A slowblow fuses. Transceiver Unit Operator Station Preamplifier Unit TX Junction Box Acceptable transients Short time (max 2 sec) Spikes (max 50ms) 25%, 42 - 69 Hz < 1000 V 100 to 240 Vac, <1100 W, 47 to 63 Hz 100 to 240 Vac, < 300 W, 47 to 63 Hz 100 to 240 Vac, <300 W, 47 to 63 Hz Not applicable
852--164111 / A
Base version
Power interrupts Menu settings, all parameters and the sound speed profile are stored on the Operator Stations harddisk during operation, so operation can continue after power interruption. However, the file system may be damaged, so the use of an uninterruptable power supply (UPS) is higly recommended.
Restrictions for use - limitations No specific restrictions apply.
Surface finish
All cabinets are painted. System units exposed to salt water must be treated accordingly.
Operating and storage temperature

Preamplifier, Transceiver Operator station Storage 0 - 45 _C 0 - 40 _C - 30 to + 70 _C
System performance data

Frequency Maxiumum ping rate Number of beams per ping Beamwidth Beam spacing Coverage sector Transmit beam steering Receive beam steering Depth resolution Pulse length Range sampling rate 12 kHz 5 Hz 191 1x1, 1x2, 2x2 or 2x4_ Equidistant and equiangle Up to 150_ Stabilized for roll, pitch and yaw Stabilized for roll 10, 20, 40 cm 2, 5 and 15 ms 2 kHz (37 cm)
Depth range from transducers 20 to 11000 m
Frequencies in the range of 11.25 to 12.60 kHz are employed to code the different transmit sectors. Other beamwidths are possible in accordance with the number of transducer modules installed.
852--164111 / A
3
3.1
CABLE LAYOUT AND INTERCONNECTIONS

Introduction
The standard cables used between the EM 120 system units and between the units and their external devices are shown here. For larger installations where the EM 120 is a subsystem, the cables will also be shown in the cable layout plan and interconnection diagram specific for the vessel into which the system is installed.
Note !
All cable connections may have to be made in accordance with the guidelines laid down by the vessels classification society. If no such guidelines exist, Kongsberg Simrad AS recommends that Det norske Veritas (DnV) Report No. 80- P008 Guidelines for Installation and Proposal for Test of Equipment be used as a guide.
852--164111 / A
Base version
3.2
System cabling
Cable layout
The interconnection cables are identified on the cable layout drawings. Each cable is then listed in the corresponding list, which contains the required cable specifications. On the following pages, each cable is identified with the appropriate terminations.
Shipyard and system cables

General
Each individual cable is identified on the cable plan. The cables fall into two categories: Cables provided by the installation shipyard or owner System cables supplied with the delivery
Shipyard cables
Note that the cable specifications given are the minimum specifications. For each cable, the following information is provided: Connection to be made on each end of the cable (including system unit, terminal board identification and plug/socket to be used) Number of cores Recommended cable type Minimum cable specifications The necessary considerations must be taken to meet special requirements. Kongsberg Simrad accepts no responsibility for damage to the system or reduced operational performance if this is caused by improper cabling.
System cables
Several cables are supplied with the system. Such cables normally comprise power cables for peripheral equipment, and interconnection cables for computers and/or workstations.
10
852--164111 / A
C10 (W301) AC power
External tape storage
Operator Station
C5 (W501) SCSI cable
C11 (W301) AC power C8 (W301) AC power C1 (W502) Display C9 (W301) AC power
External harddisk
C4 (W501) SCSI cable
C14 (W400) Ship's ethernet C16 (W103) Depth/Tide (Serial B) C15 (W102) Sound speed sensor (Serial A) C12 (W301) AC power C2 (W503) Keyboard
Keyboard
C3 (W504) Mouse
C6 (W505) Plotter
(CD4967A / GIF)
Mouse or other pointing device
Plotter (option)
C18 (W105) Coax to Transceiver Unit C17 (W400) Ethernet to Transceiver Unit
C7 (W505) Printer
C13 (W301) AC power
Postscript laser printer (option)

Figure 2 - EM 120 Cable plan - Operator Station
852--164111 / A
11
Base version
C22 (W103)
Auxiliary interface 1 (serial 3)
C20 (W103)
Positioning system (serial 1)
C21 (W103)
Motion sensor (serial 2)
C17 (W400)
Ethernet to Operator Station
C18 (W105) (optional)

Coax to Operator Station
EM120 Transceiver Unit
C25 (W105)
1 PPS from Navigation system
Note: The number of' transducer cables shown are those for a maximum beamwidth system.
C24 (W202)
Remote control and synchronization -- 8 R01-R08
C19 (W301)
AC power
Preamplifier Unit
C26 (W301)
AC power
T01-T12 -- 12
-- 12 T13-T24
(CD4967B / GIF)

-- 24

-- 24 -- 16
TX1-TX24 To TX Transducer array
TX25-TX48
RX1-RX16 From RX Transducer array
Figure 3 - EM 120 Cable plan - Transceiver Unit
12
852--164111 / A
3.3
Cable specifications
Introduction
The cables identified in the cable plan are listed here. Each cable is identfied with a cable identificator (Cxx) and a type (Wxxx). References are made to dedicated specification sheets with cable details and connections. MFS = Manufacturer supply
System cables
OPERATOR UNIT CABLES ID C1---EM120 C2---EM120 C3---EM120 C4---EM120 C5---EM120 C6---EM120 C7---EM120 C8---EM120 C9---EM120 C10---EM120 C11---EM120 C12---EM120 C13---EM120 C14---EM120 C15---EM120 C16---EM120 C17---EM120 C18---EM120 Type W502 W503 W504 W501 W501 W505 W505 W301 W301 W301 W301 W301 W301 W400 W102 W103 W400 W105 Specifications Page 22 / Note 1 Page 23 / Note 1 Page 24 / Note 1 SCSI / Note 1 SCSI / Note 1 Page 25 / Note 2 Page 25 / Note 2 Page 19 Page 19 Page 19 Page 19 Page 19 Page 19 Page 21 Page 16 Page 17 Page 21 / Note 3 Page 18 / Note 3 Terminations Operator Station ---Display unit Operator Station --- Keyboard Keyboard --- Mouse Operator Station --- External hard disk External hard disk --- External tape storage Operator Station --- Plotter (Centronics) Operator Station --- Laser printer (Centronics) Display --- AC power Operator Station --- AC power External disk storage --- AC power External tape storage --- AC power Plotter --- AC power Laser printer --- AC power Operator Station --- Ships network (Ethernet) Operator Station Port A --- Sound Speed sensor Operator Station Port B --- Depth/Tide sensor Transceiver Unit --- Operator Station Transceiver Unit --- Operator Station Yes Yes Yes Yes MFS Yes Yes Yes Yes Yes
TRANSCEIVER UNIT CABLES ID C17---EM120 C18---EM120 C19---EM120 C20---EM120 C21---EM120 Type W400 W105 W301 W103 W103 Specifications Page 21 / Note 2 Page 18 / Note 3 Page 19 Page 17 Page 17 Terminations Transceiver Unit --- Operator Station Transceiver Unit --- Operator Station Transceiver Unit --- AC power Transceiver Unit --- Positioning system (Serial 1) Transceiver Unit --- Motion sensor (Serial 2) MFS
852--164111 / A
13
Base version
ID C22---EM120 C23---EM120 C24---EM120 C25---EM120 C26---EM120
Type W103 W103 W202 W105 W301
Specifications Page 17 Page 17 Page 20 --- Note 4 Page 18 Page 19
Terminations Transceiver Unit --- Auxiliary 1 (Serial 3) Transceiver Unit --- Auxiliary 2 (Serial 4) Transceiver Unit --- Remote on/off Transceiver Unit --- 1 PPS clock (coax) Preamplifier --- AC power
MFS
Yes
TRANSDUCER CABLES ID R01---R08 RX1---RX16 T01---T24 TX1---TX48 Type N/A N/A N/A N/A Specifications Page 26 --- Note 6 Page 26 --- Note 6 Page 26 --- Note 5 Page 26 --- Note 6 Terminations Signal cables Transceiver --- Preamplifier Signal cables Preamplifier --- Transducer Signal cables Transceiver --- TX Junction Box Signal cables TX Junction Box --- Transducer MFS Yes Yes Yes Yes
Note 1 - This is a standard computer cable provided with the Operator Station. Note 2 - The workstation only provides one parallel interface to plotter or printer. In most cases, plotters and printers will be connected directly to the ships ethernet network. Note 3 - Either C17 or C18 is used to connect the Transceiver Unit to the Operator Station. Note 4 - A syncronization system may be used when more than one echo sounder or sonar systems are used simultanously. This system is connected to the Remote connector on the Transceiver Unit. This is described on W202. If a Simrad Synchronization Unit is used, further cabling is described on W722. Note 5 - One or two TX Junction Boxes may be used depending on the array specifications. Note 6 - The number of cables depends on the chosen system specifications.
Serial lines
The EM 120 uses several serial lines to interface with sensors and peripherals. Although the normal implementation is described in this document, the setup of these interfaces may easily be altered in the echo sounder. Operator Station serial lines Serial Port A - This serial port is a 25- pin female D- connector. This port is normally used to interface with the sound velocity sensor. Serial Port B - This serial port is a 9- pin male D- connector. This port is normally used for a sound speed profiler, or a depth/tide sensor.
14
852--164111 / A
Transceiver Unit serial lines The Transceiver Unit is equipped with four serial lines. All connectors are 9- pin male D- connectors. The serial lines are normally set up as follows: Serial Port 1 - Positioning systems Serial Port 2 - Motion sensor Serial Port 3 - Auxiliary 1 Serial Port 4 - Auxiliary 2
Transducer cables
The transducer cables are described on page 26.
3.4
Cable terminations
The termination of all the cables into plugs or terminal blocks are shown on the referenced pages. The transducer cables are supplied terminated.
852--164111 / A
15
Base version
W102 - Serial line This cable is a multi- purpose serial line with 25- pin D- connectors in one or both ends. It provides interface with any peripheral unit.
1
Female 25-pin D-pin connector
13
Male 25-pin D-pin connector
13
14
25
25
14
A
1 2 3 4 5 6 7 8 9 10
TXD RXD RTS CTS DSR Ground CDC DTR HI SGND
Revision: A
Serial line cable
W102
Conductors Screen Voltage Max.diameter
12 x 2 x 0.5 mm2 Overall braided 60V Set by the plugs
16
852--164111 / A
W103 - RS-232 Serial line

This cable is a multi- purpose serial line. It provides interface with any peripheral unit. One end of the cable connects to the local unit with a 9- pin D connector, while the other connects to the peripheral as described in the peripheral units documentation. Note that this cable does not support all the signals in the standard RS- 232 specification.
9-pin D connector Other unit to be connected as described in applicable documentation

5 Female 9-pin D-pin connector 9 1 Male 9-pin D-pin connector 6 9 6 5 1 Screen
Rx Tx Ground
2 3 5
To plug housing
View
Revision: E
Standard RS-232 serial line
W103
852--164111 / A
17
Base version
W105 - Coax This cable is used for connections to peripheral units or networks. In the EM 1002, EM 120 and EM 300 systems, this cable connects the 1 PPS timing signal to the Transceiver Unit. It is also possible to use a coax connection between the Transceiver Unit and the Operator Station.
Local Coax connector Peripheral unit to be connected as described in applicable documentation W105
Live Ground
Live Gnd
Screen/Ground Live Revision: B
Coax connection to peripheral unit or network
W105
18
852--164111 / A
W301 - AC power This cable is a standard 2- phase power cable. It is commercially available in standard lengths, or may be produced locally to suit the specific installation needs. The instrument end is terminated in a standard IEC female socket, while the other end is terminated in a plug suitable for the local standard.
IEC plug
Use the applicable plug to suit local standard. British standard plug used as example only.
Live (normally Blue) Ground (always Yellow or Yellow/Green) Neutral (normally Brown)
Revision: A
Standard power cable for 115/230 Vac 2-phase Conductors Screen Voltage Max. diameter 2 x 1.5 mm2 + GND None 750 V Set by the plugs
W301
852--164111 / A
19
Base version
W202 - Remote synchronization and On/Off This cable connects the Transceiver Unit to a remote On/Off switch located in a Junction Box (type EM1- 212595). The same connection allows trigger output and remote control (synchronization) with a serial line.
Junction box EM1-212595 Terminal block

1 2 3 4 5 6 7 8 9
Trigger out Trigger GND Standby + Standby On RTS CTS GND (Not connected)
Transceiver Unit 9-pin D connector Remote

1 2 3 4 5 6 7 8 9
Junction box EM1-212595

Trigger out Trigger GND
RTS
Trigger out to external system (synchronization)
CTS GND
1 2 3 4 5 6 7 8 9
System On/Off
Serial line to/from external system (synchronization)

Revision: B
Transceiver Unit - Junction Box
W202
20
852--164111 / A
W400 - Ethernet RJ45 This cable contains the Ethernet connection. RJ45 plugs are used to terminate the cable. Note that these plugs must be screened to comply to EC rules.
Pin 1 Pin 8
Pin 8
View
RJ45 plug
1 2 3 4 5 6 7 8
TX Data + (White/Orange) Tx Data - (Orange) Recv Data + (White/Green) (Blue) (White/Blue) Recv Data - (Green) (White/Brown) (Brown)
Pin 1
RJ45 plug
1 2 3 4 5 6 7 8
Ethernet 10Base-T Straight Through RJ45 plug

1 2 3 4 5 6 7 8
(1) TX Data + to (3) Recv Data + (2) Tx Data - to (6) Recv Data (3) Recv Data + to (1) Tx Data +
RJ45 plug
1 2 3 4 5 6 7 8
(6) Recv Data - to (2) Tx Data -
(Used to cascade HUBs, or for connecting two ethernet stations or computers back-to-back without a HUB)
Ethernet 10Base-T Crossover
Revision: C
Ethernet 10Base-T with RJ45 plugs
W400
852--164111 / A
21
Base version
W502 - Display This is a standard display cable used to connect the video signals. Depending on the computer type, the cable may be terminated in: Standard VGA plug (typical on most commercial computers) Multiconnector for Unix work stations Seperate RGB connectors (used on high- quality monitors) The cable is normally physically fastened to the display unit, and it is provided with the plug(s) readily attached.
15-pin D connector (VGA type)
Multi-connector for Unix work stations
Seperate R, G and B connectors (used with monitors)
Revision: A
Display Unit
W502
22
852--164111 / A
W503 - Keyboard This is a standard keyboard cable. In most cases, the cable is physically connected to the keyboard. It is terminated in a plug suited to fit the computer. Several keyboard types are available for different languages and hardware platforms. Both the keyboard and the attached cable are commercial items.
Plug suited for the computer
In most cases, the keyboard cable is physically connected to the keyboard
Keyboard
(Different keyboard types are supplied)
Revision: A
Keyboard
W503
852--164111 / A
23
Base version
W504 - Mouse or Pointing device This is a standard mouse cable. It is physically connected to the mouse. It is terminated in a plug suited to fit the computer or the keyboard (Unix workstations). Several mouse and pointing device types are available with two or three buttons, and with or without a scroll wheel. Both the mouse and the attached cable are commercial items.
Various mouse types support two or three buttons, and may also provide a scroll wheel.
Plug suited for the computer
The cable is physically connected to the mouse
Note that certain mouse types for Unix workstations are connected to the keyboard. Revision: A
(Different mouse types and other pointing devices are supplied)
Mouse
Mouse / Pointing device
W504
24
852--164111 / A
W505 - Centronics printer This is a standard Centronics printer cable.

The socket on the rear side of the computer is normally a 25-pin female D-connector.
13
25-pin D-connector
1 2 3 4 5 6 7 8 9 10 11 15 1824
Strobe Data 0 Data 1 Data 2 Data 3 Data 4 Data 5 Data 6 Data 7 Acknowledge Busy Error Ground
25
14
Printer plug
Revision: B
Centronics printer cable
W505
852--164111 / A
25
Base version
3.5
Transducer cables
Introduction
The transducer cables between the TX Junction Box(es), Preamplifier Unit, Transceiver Unit and transducer arrays are all supplied by Kongsberg Simrad with the EM 120 system. The physical number of cables depends on the chosen system beamwidth as shown the following tables.
TX Cables System Number of transducer modules = Number of cables beamwidth from Tx transducer array to Tx Junction Box(es) 1 degree 48 Two Tx Junction Boxes are used. Each of these are connected to the EM 120 Transceiver Unit with 12 cables, making a total of 24 cables. 2 degrees 24 One Tx Junction Box is used. This is connected to the EM 120 Transceiver Unit with 12 cables. RX Cables System Number of transducer modules = Number of cables beamwidth from Rx transducer array to Preamplifier Unit 1 degree 16 The Preamplifier Unit is connected to the Transceiver Unit with 8 cables. 2 degrees 8 The Preamplifier Unit is connected to the Transceiver Unit with 4 cables. 4 degrees 4 The Preamplifier Unit is connected to the Transceiver Unit with 2 cables.
The following cable information is available both in the EM 120 installation and maintenance manuals. The cable markings are normally recorded in the installation manual first, and it is recommended to copy these records to the maintenance manual later.
Transmit array cable markings

Each transducer module and its cable is identified with a serial number as follows: TX<nnn> where <nnn> is a numerical value.
26
852--164111 / A
The cables between the Tx Junction Box(es) and the Transceiver Unit are identified as follows: T<n>/<x> where <n> is a number between 1 and 12 and <x> is a number between 13 and 24. In a 1- degree Tx system, 12 cables are connected from each Tx Junction Box to the Transceiver Unit. Two identical sets of cables are then provided, the first set (T 1/13 to T12/24) are used from Tx Junction Box no.1 to sockets T1 through T12 on the Transceiver Unit. The second set is used from Tx Junction Box no.2 to sockets T13 through T24 on the Transceiver Unit. Each transducer module is also identified by its physical location in the array (frame). This location number must be recorded during the installation of the transducer modules, and written down in the tables provided in this chapter. Note ! In order to ensure proper operation by the EM 120 system, it is of vital importance that the physical location of the transducer modules fits the designated module number in the transmit and receive circuitry. The Tx transducer array is physically positioned in the fore- and- aft direction under the hull. Transducer module number 1 is always the most forward module. Module number 2 is the second forward, and so on.
Refer to figure 4 on page 30.
During installation, you can select any Tx module you wish and place them in random order in the frame. However, you MUST write down the serial number on each module in the order they have been positioned in the frame, so that you later can identify the modules in positions 1, 2, 3 and so on. The connections to the Tx Junction Box(es) are made with 25- pin D connectors. Note ! Note ! Note ! During the installation of the transmit array, you must fill in the table below. In a 2 degree system, you will only need the first 24 modules. The cable from module 1 must point to port. Location of Tx modules
Physical postion (Module) 1 (forward) 2 3 Module serial number Socket identification Tx 1/25 Tx 2/26 Tx 3/27
852--164111 / A
27
Base version
Physical postion (Module) 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
Module serial number
Socket identification Tx 4/28 Tx 5/29 Tx 6/30 Tx 7/31 Tx 8/32 Tx 9/33 Tx 10/34 Tx 11/35 Tx 12/36 Tx 13/37 Tx 14/38 Tx 15/39 Tx 16/40 Tx 17/41 Tx 18/42 Tx 19/43 Tx 20/44 Tx 21/45 Tx 22/46 Tx 23/47 Tx 24/48 Tx 1/25 Tx 2/26 Tx 3/27 Tx 4/28 Tx 5/29 Tx 6/30 Tx 7/31 Tx 8/32 Tx 9/33 Tx 10/34 Tx 11/35
Tx Junction Box no.2 (1 degree system only):
28
852--164111 / A
Physical postion (Module) 36 37 38 39 40 41 42 43 44 45 46 47 48
Module serial number
Socket identification Tx 12/36 Tx 13/37 Tx 14/38 Tx 15/39 Tx 16/40 Tx 17/41 Tx 18/42 Tx 19/43 Tx 20/44 Tx 21/45 Tx 22/46 Tx 23/47 Tx 24/48
Receive array cable markings

Each transducer module and its cable is identified with a serial number as follows: RX<nnn> where <nnn> is a numerical value. Each transducer module is also identified by its physical location in the array (frame). This location number must be recorded during the installation of the transducer modules, and written down in the tables provided in this chapter. Note ! In order to ensure proper operation by the EM 120 system, it is of vital importance that the physical location of the transducer modules fits the designated module number in the transmit and receive circuitry. The cables between the Preamplifier Unit and the Transceiver Unit are identified as follows: R<n> where <n> is a number between 1 and 8. The Rx transducer array is physically positioned in athwartship direction under the hull. Transducer module number 1 is always the first on the port side. Module number 2 is the second on the port side, and so on.
Refer to figure 4.
852--164111 / A
29
Base version
Module no.1
Port
Number of modules depends on system beamwidth
Forward
Starboard
Note: Top view! TX transducer array

Module no.1
Number of modules depends on system beamwidth
(CD4971)
RX transducer array
Figure 4 - Location of the first module in each array (example)
During installation, you can select any Rx module you wish and place them in random order in the frame. However, you MUST write down the serial number on each module in the order they have been positioned in the frame, so that you later can identify the modules in positions 1, 2, 3 and so on. Note ! During the installation of the receive array, you must fill in the table below. In a 1 degree receive system, you will need all the modules listed in the table. With a 2- degree system, you need only the first 8, while the 4- degree system only requires the first 4 modules. A dummy module shall be installed at each end of the Tx transducer array.
Note !
Note !
30
852--164111 / A
Location of Rx modules
Physical postion (Module) 1 (port) 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Module serial number Socket identification Rx 1 Rx 2 Rx 3 Rx 4 Rx 5 Rx 6 Rx 7 Rx 8 Rx 9 Rx 10 Rx 11 Rx 12 Rx 13 Rx 14 Rx 15 Rx 16
Cables between Tx Junction Box(es) and Transceiver Unit

The signal cabling between the Tx Junction Box(es) and the Transceiver Unit is made with 24 or 12 individual cables. The number of cables depends on the chosen Tx system beamwidth.
See the table on page 26 for Tx system beamwidth versus cable numbers.
For every two transducer cables connected to the Tx Junction Box, one cable is passed on to the Transceiver Unit. The connections on both units are made with 50- pin D connectors. The cables and corresponding sockets are identified as listed in the table.
See the Transceiver Unit input socket identifications in figure 5 on page 33. See the Tx Junction Box input and output socket identifications in figure 6 on page 33.
Tx Junction Box to Transceiver Unit cabling

Modules Input socket ID on Tx Junction Box (Info only) Tx 1/25, 2/26 Tx Junction Box output socket and cable ID T1/13 Socket on Transceiver Unit T1
1/2
852--164111 / A
31
Base version
Modules
Input socket ID on Tx Junction Box (Info only) Tx 3/27, 4/28 Tx 5/29.. Tx 7/31.. Tx 9/33.. Tx 11/35.. Tx 13/37.. Tx 15/39.. Tx 17/41.. Tx 19/43.. Tx 21/45.. Tx 23/47, 24/48 Tx 1/25, 2/26 Tx 3/27.. Tx 5/29.. Tx 7/31.. Tx 9/33.. Tx 11/35.. Tx 13/37.. Tx 15/39.. Tx 17/41.. Tx 19/43.. Tx 21/45.. Tx 23/47, 24/48
Tx Junction Box output socket and cable ID T2/14 T3/15 T4/16 T5/17 T6/18 T7/19 T8/20 T9/21 T10/22 T11/23 T12/24 T1/13 T2/14 T3/15 T4/16 T5/17 T6/18 T7/19 T8/20 T9/21 T10/22 T11/23 T12/24
Socket on Transceiver Unit T2 T3 T4 T5 T6 T7 T8 T9 T10 T11 T12 T13 T14 T15 T16 T17 T18 T19 T20 T21 T22 T23 T24
3/4 5/6 7/8 9/10 11/12 13/14 15/16 17/18 19/20 21/22 23/24 25/26 27/28 29/30 31/32 33/34 35/36 37/38 39/40 41/42 43/44 45/46 47/48
Tx Junction Box no.2 (1--degree system only):
Cables between Preamplifier Unit and Transceiver Unit

The signal cabling between the Preamplifier Unit and the Transceiver Unit is made with 8, 4 or 2 individual cables. The number of cables depends on the chosen Rx system beamwidth.
See the table on page 26 for Rx system beamwidth versus cable numbers.
32
852--164111 / A
REAR
T 17
T 18
T 19
T 20
T 21
T 22
T 23
T 24
T9 T1 R8
T 10 T2 R7
T 11 T3 R6
115/230VAC 50/60Hz 800W
T 12 T4 R5
T 13 T5 R4
T 14 T6 R3
T 15 T7 R2
Serial port 3 Serial port 4 Test Remote
T 16 T8 R1
Serial port 1 Serial port 2
EXTERNAL SENSORS
1.PPS
ETHERNET
(CD5133/873--213180A)
Figure 5 - Transceiver Unit sockets
REAR
T 1/13
TX 1/25
TX 2/26
TX 3/27
TX 4/28
T 2/14
T 3/15
TX 5/29
TX 6/30
TX 7/31
TX 8/32
T 4/16
T 5/17
TX 9/33
TX 10/34
TX 11/35
TX 12/36
T 6/18
T 7/19
TX 13/37
TX 14/38
TX 15/39
TX 16/40
T 8/20
T 9/21
TX 17/41
TX 18/42
TX 19/43
TX 20/44
T 10/22
T 11/23
TX 21/45
TX 22/46
TX 23/47
TX 24/48
T 12/24
(CD5127/873-213180A)
Figure 6 - TX Junction Box input and output sockets For every two transducer cables connected to the Preamplifier Unit, one cable is passed on to the Transceiver Unit. The connections on both units are made with 50- pin D connectors. The cables and corresponding sockets are identified as listed in the table.
852--164111 / A
33
Base version
See the Transceiver Unit input socket identifications in figure 5 on page 33. See the Tx Junction Box input and output socket identifications in figure 6 on page 33.
Preamplifier Unit to Transceiver Unit cabling

Module Input socket ID on Preamplifier Unit (Info only) Rx 1/2 Rx 3/4 Rx 5/6 Rx 7/8 Rx 9/10 Rx 11/12 Rx 13/14 Rx 15/16 Preamplifier Unit output socket and cable ID R1 R2 R3 R4 R5 R6 R7 R8 Socket on Transceiver Unit R1 R2 R3 R4 R5 R6 R7 R8
1/2 3/4 5/6 7/8 9/10 11/12 13/14 1516
In a 1- degree Rx system, all modules 1 through 16 are used. In a 2 degree system, the first 8 modules are used, while the 4 degree system uses the first 4.
REAR RX 16 RX 15 RX 14 RX 13 RX 12 RX 11 RX 10 RX 9
RX 8
RX 7
RX 6
RX 5
RX 4
RX 3
RX 2
RX 1
115/230VAC 50/60Hz 200W
R4
R3
R2
R1
R8
R7
R6
R5
SBP 4
SBP 3
SBP 2
SBP 1
SBP 8
SBP 7
SBP 6
SBP 5
(CD5129/213278B)
Figure 7 - Preamplifier Unit input and output sockets
34
852--164111 / A
Maintenance manual
4
4.1
TRANSCEIVER UNIT
Description and main functions
Overview
The EM 120 Transceiver Unit performs the reception, data acquisition, received signal processing and transmission for the multibeam echo sounder system. The cabinet holds three wired racks containing the system circuit boards. The top Processing Rack holds the complete Processing Unit with its own power supply. This unit provides data acquisition, signal processing and function control. The middle Receiver Rack holds the receiver boards, a controller, two power supplies and a large capacitor bank. The bottom Transmitter Rack holds the transmitter circuitry and a dedicated controller. Extra Capacitor Unit on the rear panel. This chapter provides the following information:
Description and main functions, page 35. Transceiver Unit outline, page 36. Transceiver Unit racks, page 37. Theory of operation, page 42. Processing rack, details, page 45 Receiver rack, details, page 46. Transmitter rack, details, page 47 Circuit board descriptions, page 48.
852--164111 / A
35
Base version
630 mm
600 mm
1834 mm
1600 mm Min 303 mm
(CD3694)
Figure 8 - EM 120 Transceiver Unit - Outline dimensions
36
1995 mm
852--164111 / A
Maintenance manual
Circuit breaker Processing rack
Processing Unit
SIMRAD
POWER SUPPLY 290-112750
7.5V REF 7.5V 5VA 5VA 5V 12V 12V 24V GND SWITCHED POWER SUPPLY ANALOG POWER SUPPLY L204
VCC
F203
-10db
L203
HALT OVER-VOLTAGE VCC2
SERVICE OFF NORMAL S202
KONGSBERG SIMRAD
HV-POWER UNIT 290 - 213160
HIGH MIDDLE
16 A
16 A
ON/OFF RELAY
LOW VREF
Receiver rack
24V REF
24V STAND BY
CHG.
SLOW BLOW
L202
50 100
150
F201 8A SLOW BLOW
F202 8A
V
-20db
BLEED
VBB
L201
CAUTION
DO NOT PULL OUT THIS UNIT BEFORE THE METER SHOWS ZERO (0) VOLTAGE FOR CONTINUED PROTECTION AGAINST THE RISK OF FIRE REPLACE ONLY WITH SAME TYPE AND RATING OF FUSE
MAINS INPUT 115/230V AC
S201 230V AC
P201
Cooling fans
Transmitter rack
(CD5535/860-213008/B)
Figure 9 - EM 120 Transceiver Unit wired racks
852--164111 / A
37
Base version
The Processing Rack

The Processing Rack is located at the top of the Transceiver Unit. It holds a chassis with several circuit boards, a fan and a power supply. A ground strap and a circuit breaker for the power supply is also available, but these are mounted on the main rack, and not on the shelf.
The Processing Rack is shown in figure 10. The power supplies are not shown on this drawing.
ROM Card Processor Board BSP1 Circuit breaker
Slot 10 Slot 9 Slot 8 Slot 7 Slot 6 Slot 5 Slot 4 Slot 3 Slot 2 Slot 1 P5 P1 P7 P5 P1 P7
(CD5344D / 860-213008/B)
Serial card Ethernet adapter
BSP2
Figure 10 - Processing Rack circuit board locations The Processing Rack holds the following circuit boards and modules: 4- Ports Serial Line Board Beamformer & Signal Processor 1 / 2 (BSP1 and BSP2) Ethernet Adapter ROM board Control Processing Unit Board Power supply Fan Motherboard
A more detailed description of all the circuit boards and modules is found on page 45.
38
852--164111 / A
Maintenance manual
Vorsicht! Spannung Attention Danger
(CD5403B / 861-212871/A)
Power supply HN5-9/OVP-A
Power supply OLD-12/15BB
Figure 11 - Power supplies on the rear panel
852--164111 / A
39
Base version
The Receiver Rack

The Receiver Rack is located at the middle of the Transceiver Unit. It holds several circuit boards, power supplies and a capacitor bank. All the units are accessed from the front of the rack.
Transmitter/Receiver Boards High voltage power supply Capacitor bank
SIMRAD
7.5V REF 7.5V 5VA 5VA 5V 12V 12V 24V GND ANALOG POWER SUPPLY
L204
VCC
F203
-10db
SWITCHED POWER SUPPLY
L203
HALT OVER- VOLTAGE VCC2
SERVICE OFF NORMAL ON/OFF RELAY S202
KONGSBERG SIMRAD
HIGH MIDDLE LOW VREF
HV-POWER UNIT 290 -213160

16 A 16 A
24V REF
24V STAND BY
CHG.
SLOW BLOW
L202
50
100
15 0
F201 8A SLOW BLOW
F202 8A
V
-20db
BLEED
VBB
L201 MAINS INPUT 115/230V AC
CAUTION
DO NOT PULL OUT THIS UNIT BEFORE THE METER SHOWS ZERO ( 0 ) VOLTAGE FOR CONTINUED PROTECTION AGAINST RISK OF FIRE REPLACE ONLY WITH SAME TYPE AND RATING OF FUSE.
S 201 230V AC
P201
(CD5391C / 860-213008/A)
Low voltage power supply
Signal Processor Board (SPBRX)
Fan drawer
Figure 12 - The Receiver Rack The Receiver Rack holds the following circuit boards and modules (from left): TRB 32/Receiver board (x 4) Low Voltage Power Supply High Voltage Power Supply Signal Processor Board RX (SPRX) Capacitor bank
A more detailed description is found on page 46.
40
852--164111 / A
Maintenance manual
The Transmitter Rack

The Transmitter Rack is located at the bottom of the the Transceiver Unit. It holds one processor board and a number of transmitters.
64-Channel Transmitter Boards (Tx64)
(CD4472D/210132A)
Signal Processor Board TX (SPBTX)
Figure 13 - The Transmitter Rack The Transmitter Rack holds the following circuit boards and modules (from left): 64- Channel Transmitter Board (TX64) Signal Processor Board TX (SPTX)
A more detailed description is found on page 47
The rear panel

On EM 120 a large capacitor unit is mounted on the back panel. It holds large capacitors used to store energy for the transmit pulses. It is connected to the transmitter backplane.
852--164111 / A
41
Base version
4.2
Theory of operation
Overview
This chapter presents a functional description of the Transceiver Unit.
Serial lines to/from the sensors
(CD4551b)
Ethernet to/from the Operator Station
Control Processor
Command and control (serial line)
Beamformer and Signal Processor (BSP) x 2

Processing Rack 16-bit sampled data
Signal Processor Tx (SPTX)
Command and control
Signal Processor Rx (SPRX)
64-Channel Transmitter (TX 64) x 14

Transmitter Rack Receiver Rack
Receiver Board (TRB) x 4
Filter Transmit array
Preamplifier Unit Receive array
Figure 14 - Transceiver Unit, simplified block diagram
Simplified block diagram

The simplified block diagram for the Transceiver Unit presents the following main functions: Transmission Reception Processing
Refer to figure 14.
42
852--164111 / A
Maintenance manual
The various parameter settings made on the Operator Station are sent to the Control Processor in the Processing Unit. The information is interpreted, and passed on to the Signal Processor TX, which is the master processor in the TX/RX system. After the transmission, the Signal Processor RX is instructed to receive the echoes, and pass these to the two Signal Processors in the Processing Unit.
Control functions
The control functions in the Transceiver Unit are mainly handled by the three processor boards, but additional peripheral boards are also used. The majority of the control boards are contained in the Processing Unit.
Ethernet to/from the Operator Station
Processing Rack
Serial lines to/from the sensors
Ethernet adapter
Bus system
Serial lines
PROM bank
Control processor
BSP x 2
(CD4554)
Command and control (serial line)
Signal Processor Tx (SPTX)
Command and control
Signal Processor Rx (SPRX)
Transmit circuitry
Receive circuitry
Figure 15 - The control functions The Control Processor in the Processing Unit is not equipped with interface capabilities, and thus requires external boards to handle ethernet and serial lines interface. It also relies on an external memory board for the software contained in ROM device. All the peripheral boards used here are commercial. One serial line is used to interface the command and control signals to and from the TX/RX controllers. The Signal Processor TX is the master.
852--164111 / A
43
Base version
External synchronisation
The serial line RTS and CTS signals are used for external synchronisation. In addition a trig out signal is issued by the TRU. Levels: RTS, CTS: H=high= +3 to +15 V L=low= - 3 to - 15 V Trig out: TTL Level Outputs from TRU: Trig out=1 TX is off(High TTL level) Trig out=0 TX is active(Low TTL level) RTS=H RTS=L TRU is ready for a new ping TRU is not ready
RTS is pin 7 on the CPU card D connector. (Pin 6 on EM120 and EM300 remote plug). Inputs to TRU: CTS=H Ping command CTS=L Wait CTS is pin 8 on the CPU card D connector. (Pin 7 on the EM120 and EM300 remote plug). The CTS pulse length must be minimum 30 milliseconds. Gnd is pin 5 on the CPU card D connector. (Pin 8 on EM120 and EM300 remote plug). Typical sequence:
CTS _____________- - - - - - - ________________- - - - - - - - - - _________ TX Command - - - - - - - - - - - - - - _______________- - - - - - - ________________- - (TRU ready) (TRU busy) (TRU busy) - - - - - - - - - - - - - - __- - - - - - - - - - - - - - - - - - - - __- - - - - - - - - - - - - - - - TX Pulse
RTS Trig out
When the TRU is ready for a new ping, RTS is set to H. When the external device is ready for a new ping, CTS shall be changed to H. The TRU will then start a ping, change RTS to L (busy), and the Trig out will be low during the transmit pulse. After the Trig out is received, the external device should turn CTS to L. (Or at least keep it high for 35 milliseconds). When the received period is finished and the TRU is ready for a new ping, the RTS will be changed to H, and the TRU will wait for new trigger (a high level on CTS). If CTS is H all the time, or if external sync in the installation menu is switched off, the TRU will ping at its maximum rate.
44
852--164111 / A
Maintenance manual
4.3
Processing rack details

Location
The Processing Rack is located at the top of the the Transceiver Unit. It holds a chassis with several circuit boards, a fan and a power supply. A ground strap and a circuit breaker for the power supply is also available, but these are mounted on the main rack, and not on the shelf.
Circuit boards and modules

4- ports Serial Line Board
This is a commercial circuit board. It provides the Transceiver Unit with four serial lines.
The interface board is explained on page 49
Beamformer & Signal Processor 1/2 (BSP1 and BSP2)

These are the main processing boards in the Transceiver Unit.
The circuit board is explained on page 54.
Ethernet Adapter
This is a commercial circuit board. It provides the Transceiver Unit with the ethernet communication to the Operator Station.
The circuit board is explained on page 57
ROM board
This is a commercial ROM board.
Control Processor Board (SSC)

This processor board acts as a function controller.
Power supply
The Processing Rack contains two analogue power supplies located behind the circuit board.
The power supplies are explained on page 65.
Motherboard
This is a commercial circuit board.
Fan
The fan is located on the right side of the Processing Unit, when seen from the front.
852--164111 / A
45
Base version
4.4
Receiver rack details

Location
The Receiver Rack is located at the middle of the the Transceiver Unit. It holds several circuit boards, power supplies and a capacitor bank.
Refer to the illustration on page 40.

Transmitter/Receiver board
These four boards hold the amplifiers for all the individual receive channels. (The boards may also provide power amplification of the transmitted signal, but as this function is not used in the EM 120, these components have been omitted).
The circuit board is explained on page 68.
Low Voltage Power Supply

This is a commercial linear power supply mounted on a chassis for easy replacement. It also contains linear supplies for the TRBs.
The Low Voltage Power Supply is explained on page 71.
High Voltage Power Supply

This is a switching power supply. It provides the high output voltage for the transmitters, and uses the Capacitor bank to store the energy between the pings.
The High Voltage Power Supply (HV2PS2) is explained on page 75.
Signal Processor Board RX (SPRX)

The processor board is used as a function controller. This is a common circuit board whose name is SPB31, and it is both used in the Transmitter Rack and the Receiver Rack.
The Signal Processor Board is explained on page 77.
Backplane (RXBP)
The Receiver Rack uses a passive backplane. All connections to the circuit boards (except transmission signals) are made on this backplane.
The RX Backplane is explained on page 83
Capacitor bank
This unit stores transmission energy temporarily.
46
852--164111 / A
Maintenance manual
4.5
Transmitter rack details

Location
The Transmitter Rack is located at the bottom of the Transceiver Unit. It holds one processor board and a number of transmitter boards.
Refer to the illustration on page 41
The physical number of transmitter boards is defined by the specified system accuracy: A 1 degree system has 14 transmitter boards

64- Channel Transmitter Board (TX64)
Each of these circuit boards holds 64 individual power amplifiers, each controlled by the function controller.
Signal Processor Board TX (SPTX)

The processor board is used as a function controller.
Backplane (TXBP)
The Transmitter Rack uses a passive backplane.
The TX Backplane is explained on page 91
852--164111 / A
47
Base version
4.6
Circuit board descriptions

Overview
This chapter describes all the circuit boards and modules in the EM 120 Transceiver Unit. A functional description with a block diagram is provided, as well as the facilities provided for maintenance.
48
852--164111 / A
Maintenance manual
4-Ports Serial Line Board (C114P)

Purpose and description
This is a commercial circuit board designed and produced by Moxa Technologies. This is identified as C114P, and is located in the Processing Rack.
Refer to figure 10.
How it works
Each of the 4 ports can be configured to RS- 232, RS- 422, or RS- 485 interface individually. It is designed for the system manufacturers, integrators, or VARs that want to provide all high performance reliability, and quality multiple ports data communication system. For high speed data communication, the C114P provides four 16C550 UARTs which offer 16- byte FIFO buffers. By buffering the data into FIFO before putting it into the bus, it can drastically reduce the CPU load. Two operation modes are supported in the C114P: Normal mode All four ports can be configured as any base address and interrupt IRQ level. The standard PC serial communication ports (COM1, COM2, COM3, COM4) with normal default base address and IRQ can be achieved in this mode. Enhanched mode. All four ports share the same IRQ. This mode is most suitable for the high speed applications in multitasking environment, such as SCO- UNIX. The C114P Ports RS- 232/422/485 Card provides the following advanced features: 4 independent RS- 232, RS- 422 or RS- 485 serial ports Each port can be configured with jumpers individually. Speed up to 115.2 Kbps. Four 16C550 UARTs for C114P, with 16 bytes FIFO. Interrupt jumpers selectable, IRQ 2, 3, 4, 5, 7, 10, 11, 12, or 15. On- board Interrupt vector for greater throughput. RS- 232, RS- 422 or RS- 485 protocol jumper selectable. Compatible with PC- standard ports: COM1 - COM4. Supports 2- wire or 4- wire RS- 422/RS- 485 operations.
852--164111 / A
49
Base version
JP2
JP4
JP6
JP8
COM4
JP1
JP3
JP5
JP7
COM3
P1
COM2 JP10 JP11 JP12
JP9
COM1
(CD5561)
Figure 16 - The C114P layout
Facilities
LEDs None. Links The default settings of C114P for use in the multibeam are listed below: 1 Mode setting: Enhanced Mode
Enhanced Mode ON SW5
1 2 3 4 5 6 7 Mode
(CD5822)
50
852--164111 / A
Maintenance manual
Interrupt Vector Address: 2C0H

Interrupt Vector Address ON
SW5
1 SA 4 2 5 3 6 4 7 5 8 6 7
(CD5822B)
9 Mode
Port Base Address: Port 1 = 280H; Port 2 = 288H; Port 3 = 290H; Port 4 = 298H
Base Addr = 280H ON Base Addr = 288H ON SW2
1 SA 3 2 4 3 5 4 6 5 7 6 8 7 9 SA 1 3 2 4 3 5 4 6 5 7 6 8 7 9
SW1
Base Addr 290H ON SW3

1 SA 3 2 4 3 5 4 6 5 7 6 8 7 9 SA
Base Addr = 298H ON SW4

1 3 2 4 3 5 4 6 5 7 6 8 7 9
(CD5822C)
Port Interrupt IRQ: Port 1 = IRQ5; Port 2 = IRQ5; Port 3 = IRQ5; Port 4 = IRQ5
Jp9 (IRQ) 2 3 4 5 7 10 11 12 15
Jp10 (IRQ) 2 3 4 5 7 10 11 12 15
Jp11 (IRQ) 2 3 4 5 7 10 11 12 15
Jp12 (IRQ) 2 3 4 5 7 10 11 12 15
852--164111 / A
51
(CD 5704)
Base version
Port Protocol: Port 1 = RS- 232; Port 2 = RS- 232; Port 3 = RS- 232; Port 4 = RS- 232
JP1
RS232/422/485
JP1
RS232/422/485
(CD5822D)
RS-232
RS-422
RS- 485 Sent/Receive Checking Setting Port 1 = RTS; Port 2 = RTS; Port 3 = RTS; Port 4 = RTS
JP2
RTS REG
JP4
RTS REG
JP6
RTS REG
JP8
RTS REG (CD5822E)
52
852--164111 / A
Maintenance manual
Communication Protocol Setting, option RS--422 configuration The C114P can offer three protocols for each port: RS- 232, RS- 422 and RS- 485. The communication protocol of each port is set by JP1, JP 3, JP5 and JP7. For example: Port 1 is set by JP1 and its different protocol settings are shown below.
JP1
RS232/422/485
JP1
RS232/422/485
CD5808
RS-232 Default Setting
RS-422
Connections The C114P contains one DB- 37 female connector on the rear side of the circuit board. It comes with a cable; one terminal is a 37- pin male D- type and the other terminal is a four 9- pin male D- type connectors. This is not used. In addition, four 10- pin pin- head connectors corresponds to the DB- 37 connector on the board of C114P. These four connectors are called COM1, COM2, COM3 and COM4, and are connected directly to the TRU bottom plate.
Refer to figure 17 for pin assignment.
NC RI CTS RTS DSR
10 9 8 7 6
(CD5573)
5 4 3 2 1
GND DTR TXD RXD DCD
Figure 17 - 10- pin header connector pin assignment
852--164111 / A
53
Base version
Beamformer & Signal Processor (BSP)

The Beamforming & Signal Processing (BSP) board is a multi digital signal processor (DSP) board. It is designed to perform the beamforming and signal processing in sonars and multibeam echo sounders. It is controlled from a host processor. The processing power in the Beamforming & Signal Processing (BSP) board is based on eight Texas TMS320C50 fixed point digital signal processors working in parallel while beamforming the data. Next, there are four Texas TMS320C44 floating point digital signal processors interconnected to use both parallel and sequential processing of the beamformed data from the fixed point processors. The Beamforming & Signal Processing (BSP) board is a single slot full length standard ISA format circuit board made to fit into a personal computer.
How it works
The Beamforming & Signal Processing (BSP) board contains four main sections; Sonar Input Data Beamforming Signal Processing Host Interface The Sonar Input Data interfaces an 18- bit wide and 1k deep Input FIFO (First- In- First- Out) register. This input FIFO holds the data received from the transducer array through the receiver processing circuitry. A dedicated digital signal processor reads the input FIFO. There are two identical Beamforming digital signal processing branches. Each consists of four digital signal processors and a 16- bit wide and 8k deep dual port memory (DPRAM). The two branches are exchanging data by means of this DPRAM. The Signal Processing section comprises three digital signal processors dedicated to do further processing of the beamformed data. The Host Interface function is maintained by the master processor on the Beamforming & Signal Processing (BSP) board. It exchanges data with the host processor via a 16- bit wide and 8k deep dual port memory (DPRAM) on the ISA bus.
Facilities
LEDs D1 (LED) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C44 D
54
852--164111 / A
Maintenance manual
Test points There is one test point for each C50 digital signal processor (eight total). These testpoints are all connected to the XF/ signal which is active while that particular C50 access the shared DPRAM. There is also one test point for each C44 digital signal processor (four total). These test points are connected to the IIOF2/ signal, which is a general purpose I/O port bit that can be controlled by the software. The C44- D testpoint is also connected to a light emitting diode (D1) for visual observation. The LED will be activated during each ping.
TP1 TP2 TP3 TP4 TP5 TP6 TP7 TP8 TP11 TP12 TP13 TP14 (& D1) C50 E0 C50 E1 C50 E2 C50 E3 C50 F0 C50 F1 C50 F2 C50 F3 C44 A C44 B C44 C C44 D
The testpoints will be active when the corresponding processor is working. Links A number of links are implemented on the board to allow for several different applications. Links LK1, LK2 and LK3 are used to identify the board as one out of maximum eight boards in one system.
LK3 0 0 0 0 1 1 1 1 LK2 0 0 1 1 0 0 1 1 LK1 0 1 0 1 0 1 0 1 BSP ID BSP 0 BSP 1 BSP 2 BSP 3 BSP 4 BSP 5 BSP 6 BSP 7
Link applications The following links are ON (closed) in this application:
852--164111 / A
55
Base version
BSP0 is the master processor (no links). BSP1 is the slave processor (link LK1).
Switches There are no switches on the board. Connections The Beamforming & Signal Processing (BSP) holds the following plugs and sockets:
P1 P2 P3 P4 P5 P6 P7 Sonar input data ISA bus component Emulator Direct memory access External communication port Test access port External communication port
The P1, sonar input data, is connected to SPRX via a flat cable plug connected to the Reciever Backplane, plug P11.
56
852--164111 / A
Maintenance manual
Ethernet Adapter
This is a 16- bit ISA adapter designed and produced by 3Com, identified as 3C509B- COMBO. The purpose of the adapter is to connect the transceiver unit to the operator unit. The circuit board is located in the Processing Rack.
Refer to figure 10
How it works
The cable types and connector specifications in the Ethernet Adapter are: 10BASE5 thick Ethernet coaxial, 10BASE2, fibre etc. with an AUI connector. 10BASE2 thin Ethernet coaxial with a BNC connector. 10BASE- T, twisted- pair cable with a RJ- 45 connector.
The 3C509B- COMBO edge connectors is shown in figure 18.
The 3C509B- COMBO has a LED for the link beat. This LED confirms that there is an active connection between the adapter and the hub. The thin ethernet segment is terminated at both ends with a 50 W terminator. The maximum bus speed supported by the Ethernet Adapter is 10 MHz.
852--164111 / A
57
Base version
LED RJ-45 connector
AUI connector
(CD4612)
BNC connector
Figure 18 - The 3C509B- COMBO backplate with its connectors
Facilities
LEDs Confirms that there is an active connection between the adapter and the hub. If the LED is on, the link beat is working. (The connection is correct). If the LED is off, the link beat has not been established or there is a problem with the connection between the adapter and the hub. If the LED is blinking, the cable polarity is reversed.
See figure 18
Connections The internal wiring gives access to the BNC and RJ45 connections at the bottom plate of the Transceiver Unit.
Setup of the board

If the type of ethernet cable is known at delivery time, the board is set up accordingly. If not, the board is set up for 10BASE- T (RS- 45). It is difficult to reconfigure the board on site. (A PC with ISA- bus and special software is needed).
58
852--164111 / A
Maintenance manual
ROM board
The ROM board is an ISA bus card that adds an EPROM socket to a PC motherboard. This is a commercial circuit board designed and produced by Blunk Microsystems. The ROM board is located in the processing rack.
Refer to figure 10
It provides a means of auto- starting embedded applications. If a properly formatted EPROM is installed, the BIOS will recognize the EPROM during its ROM scan and pass control to it after completing the power- up tests. The ROM board uses one 27010, 27020 or 27040, booting applications as large as 128K, 256K or 512K, respectively.
Facilities
LEDs None Test points None Links Jumper 1- 8 2- 7 3- 6 4- 5 Base Address CE000 CE800 CF000 CF800
When used in EM 120, the default settings for the ROM board are jumpers 2- 7, and base address CE800.
852--164111 / A
59
Base version
Control Processor Board

This circuit board is an ISA Half- sized Single Board Computer delivered by ICP. It is equipped with a 486 CPU and advanced high performance multi- mode I/O. There are two variants of the circuit board that might be placed in the system. These are identified as: SSC- 486H or SSC- 5x86H Both of them are explained in this chapter. The Control Processor Board is located in the Processing rack.
Refer to figure 10
Specifications
The Half- sized Single Board Computers SSC- 486H and SSC- 5x86H provides the following specifications:
SSC-486H CPU Bus DMA channels Interrupt levels Chipset Real-time clock/calendar 486SX/DX/DX2 or DX4 PC/104 bus 7 15 DS--12887 chip and quartz oscillator, 128B CMOS memory, powered by lithium battery for over 10 years of data retension. 1MB to 64MB SSC-5x86H 486SX/DX/DX2/DX4 or Cyrix/AMD 5x86 ISA bus and PC/104 bus 7 15 DS--12887 chip and quartz oscillator, 128B CMOS memory, powered by lithium battery for over 10 years of data retension. 1MB to 64MB, EDO and standard DRAM supported. Up to two PCI Enhance IDE hard drives. Two 2.88MB, 1.44MB, 1.2MB, 720KB or 360KB floppy disk drives. Two NS16C550 compatible UARTs Yes
UM8498F and UM8496 M1489 and M1487
RAM memory
IDE hard disk drive interface Floppy disk drive interface
Up to two IDE hard drives. Two 2.88MB, 1.44MB, 1.2MB, 720KB or 360KB floppy disk drives. Two NS16C550 compatible UARTs Yes
High speed serial ports Bi-directional Parallel Port
60
852--164111 / A
Maintenance manual
SSC-486H Watch-dog timer Can be set by 1, 2, 10, 20, 110 or 220 seconds period. Reset or NMI was generated when CPU did not periodically trigger the timer. Your program use hex 043 and 443 to control the watch--dog and generate a system reset. Yes Yes PS/2 Mouse Port on-board +5V @ 2.5A (486DX2--66, 4MB RAM) +/-- 12V @ 20mA (for RS--232 only) 0 ~ 60C (CPU needs cooler)
SSC-5x86H Can be set by 1, 2, 10, 20, 110 or 220 seconds period. Reset or NMI was generated when CPU did not periodically trigger the timer. Your program use hex 043 and 443 to control the watch--dog and generate a system reset. Yes Yes PS/2 Mouse Port on-board +5V @ 1.75A (5x86--133, 4MB RAM)
External power connector Keyboard connector Mouse Power Consumption
Operating temperature
0 ~ 60C (CPU needs cooler)
The setup procedures for SSC- 486H and SSC- 5x86H are described on page 150
Facilities
Jumpers All the SSC- 5x86H- and SSC- 486H circuit boards jumpers are preset at the factory. The default settings are listed in the tables.
Refer to figure 19 for different jumper settings.
852--164111 / A
61
Base version
Closed
Open
3
(CD5549)
1-2
2-3
1-2
2-3
2-4
Figure 19 - Different applicable jumper settings The SSC- 486H circuit board:
Jumpers SSC-486H CPU JP1 JP2 JP3 JP4 JP5 JP6 JP7 CPU Clock Generator Speed (33 MHz) CPU Voltage (+3.3 V) Upgrade the External Cache (128KB, 32K x 8) Watch-Dog Timer, Active Type JP8 Settings 2 -- 3 1 -- 2 3 -- 4 Open Open 1 -- 2 Open Open 1 3 5 7 ----2 4 6 8 Closed Closed Open Open Description ---------
JP12 JP24 JP13 JP14 JP18
2 -- 3 Open 2 -- 3 1-- 2 3 -- 4 1 -- 2 1 3 5 7 ----2 4 6 8 Open Closed Open Open
----Open when WDT time--out --
WDT Time-out period JP17 (10 sec.)
62
852--164111 / A
Maintenance manual
Jumpers Parallel Port Interface, Parallel Port Interrupt Setting (IRQ7) Parallel Port Data Request Setting (DRQ3) Parallel Data Acknowledge (DACK3) Serial Port Interface, COM1 Serial Port Interrupt Setting (IRQ4) COM2 Serial Port Interrupt Setting (IRQ3) IDE Host Adapter Interface FDC47C665 Multi-I/O Chipset PS/2 Mouse IRQ Selection (IRQ12) JP22
Settings 1 -- 2
Description --
JP20
2 -- 3
--
JP19
2 -- 3
--
JP21
1 -- 2
--
JP23
1 -- 2
--
JP11 JP16 JP15
Open Open Closed
IDE IOCHDRY Non--Connected Enable FDC37C665 --
The SSC- 5x86H circuit board:

Jumpers SSC-5x86H CPU JP1 JP2 JP3 JP4 JP5 JP6 JP7 JP8 JP9 JP10 CPU Clock (33MHz) JP11 JP12 JP14 CPU Voltage (+3.3V) Watch-Dog Timer, Active Type JP13 JP15 Settings 2 -- 3 2 -- 3 3 -- 4 3 -- 4 3 -- 4 5 -- 6 2 -- 3 2 -- 3 Closed Open 1 -- 2 3 -- 4 Open 1 -- 2 2 -- 3 1 -- 2 Closed Closed Description --------------Open when WDT time--out
852--164111 / A
63
Base version
Jumpers WDT Time-out period JP16 (10 sec.)
Settings 1 3 5 7 ----2 4 6 8 Open Closed Open Open
Description --
DiskOnChip Memory Address PS/2 Mouse
JP17 JP18
5 -- 6 Closed
Address E000 Enable PS/2 Mouse, IRQ12
Connections COM1 is used for external sync (RTS, CTS). COM1, pin RX/TX, is also connected to the test connector at the TRU bottom plate, for debug purposes and factory production testing.
Refer to description page 44.
1PPS signal is connected from the parallel port (signal on pin 10, GND on pin 23) to the bottom plate in the Transceiver Unit.
64
852--164111 / A
Maintenance manual
Processing Unit Power Supply

The Processing Rack contains two analogue power supplies (HN5- 9/OVP- A and OLD- 12/15BB). The purpose of those is to feed power to the circuit boards in the Processing Rack, respectively 5 Vdc and 12 Vdc. The power supplies are located on the rear side of the Processing Rack, hidden behind a cover plate.
How it works
This is two analogue power supplies that feed respectively 5 Vdc and 12 Vdc to the Processing Rack. Both have connections to the same 16- pin socket.
Refer to the block diagram in figure 20, with 230 Vac, and figure 21, with 110 Vac.
16
15
14 13
12
11
10
+12V
+12V
GND
GND
GND
GND
GND
AC1
-12V
AC1
AC2 0.75 Bn
0.75 Wh
+Out +S -S -Out
(CD5520/212871A)
+5V com
+Out -S -S Com +S -S -Out
+12V
-12V
HN5-9/ OVP-A
4 2 3 1 5
OLD-12/ 15BB
4 2 3 1 5
0.75 Bn
AC1 AC2
0.75 Wh
0.75 Bl 0.75 Gn
0.75 Gn
0.75 Bn
0.75 Bn
0.75 Bk
0.75 Bk
2.5 Bk
2.5 Bk
2.5 Bk
2.5 R
2.5 R
2.5 R
AC2 AC1 AC2
+5V
+5V
Figure 20 - Power supplies - internal block diagram 230 Vac.
+5V
852--164111 / A
65
Base version
-Out
+S -S -Out HN5-9/ OVP-A

4 2 3 1 5
-12V
(CD5520E)
4 2 3 1 5
OLD-12/ 15BB
AC1 AC2
AC1 AC2
Figure 21 - Power supplies - internal block diagram (110 Vac). From this socket the connections goes further to the PU backplane, to the fans in the Processing Rack and to the main circuit breaker. It is also connected to the TX backplane with a 12 Vdc- and a ground signal.
Facilities
Connections Pins 2, 4, 5 and 9 are not in use.
Pin 1 3 6 7 8 10 10 11 11 12 13 13 14 14 15 16 Signal AC2 AC1 +5 Vdc +5 Vdc +5 Vdc GND GND GND GND GND GND GND +12 Vdc +12 Vdc +12 Vdc --12 Vdc Connection Circuit breaker Circuit breaker PU backplane--P9 pin 4 PU backplane--P9 pin 5 PU backplane--P9 pin 6 PU backplane--P8 pin 5 TX backplane--P1 pin 1 PU backplane--P8 pin 6 TX backplane--P1 pin 2 PU backplane--P9 pin 1 PU backplane--P9 pin 2 PU backplane--P9 pin 2 Fans in PU TX backplane--P1 pin 3 Fans in PU PU Backplane--P8 pin 4
66
852--164111 / A
Maintenance manual
Motherboard
How it works
This is a passive backplane with standard ISA- bus.
Facilities
LEDs The board has four LEDs: + 5V - 5V + 12V - 12V - 5V is not used and is not lit. The three others should be lit at all times. Test points None Links None Connections + 5V, + 12V and - 12V.C
852--164111 / A
67
Base version
Transmitter/Receiver Board (TRB)

The purpose of the Transmitter/Receiver Board (TRB) is to provide amplification of the signals received from the Preamplifier Unit. The board has 32 individual channels. The board is designed to provide transmission as well, but these components are not mounted on the circuit boards used in the EM 120 Transceiver Unit The TRB is fastened to a combined strengthening plate and heat sink which covers the entire component side of the board and also forms a front panel to the board. The board is located in tracks within the Transceiver Unit to ensure correct location, and is held in position by four screws. The TRB has two 34- pin connectors on its front edge which carry the signals from the Preamplifier Unit.
How it works
Transmission The TRB contains a control interface that controls the 32 transmitters on the board. The transmitters can be controlled individually to enable beamforming of the transmitted pulse. This function is not used in the EM 120. Reception The TRB receives signals from 32 transducer elements. The signals are individually amplified, time- varied- gain regulated, demodulated, and analogue- to- digital converted. The converted signals are then output from the board and sent to the BSPs for further processing. Technical details Dimensions (Width x Heigh x Depth) Analogue input/output Connectors 220 x 233.35 x 0.32 mm 32 channels, 60W, + T/R switch Two 96- pin euro on back edge of board Two 34- pin flat cables on front edge 12- bits resolution I/Q simultaneously converted to 32- bit latched bus + 5 Vdc, 8 Vdc, + 24 Vdc
Analogue to digital
Power requirements
68
852--164111 / A
Maintenance manual
Address bus from SPRX Not mounted in the EM 120

(Cd3428B)
32 Tx Channels
Tx control Rx control
RX and Tx control circuitry Data aquisition control Data aquisition
32 Rx Channels
2 x 16-bit data buses
From the preamplifier (EM 120)
Data out to the SPRX
Figure 22 - Transmitter/Receiver (TRB) block diagram
Facilities
Test points The test points listed below are available to assist the maintenance engineer. They are located on the front edge of the board between the two connectors, in front of the corresponding LED. AVCC analogue voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . + 5 V AVDD analogue voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NA VCC digital voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . + 5 V AVEE analogue voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . - 5 V HV1 high voltage transmitter . . . . . . . . . . . . . . . . + 13 - + 135 V HV2 high voltage transmitter . . . . . . . . . . . . . . . . . . . . . . . . . NA HV3 high voltage transmitter . . . . . . . . . . . . . . . . . . . . . . . . . NA HV4 high voltage transmitter . . . . . . . . . . . . . . . . . . . . . . . . . NA TX transmitter indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NA The testpoints marked with NA are not used on EM 120. Links The TRB holds no links that can be set by the maintenance engineer. Switches The TRB holds no switches that can be adjusted by the maintenance engineer. LEDs The TRB holds ten red LEDs on its front edge, mounted in a vertical line between the connectors. When these LEDs are lit, they indicate the presence of the corresponding voltage levels.
852--164111 / A
69
Base version
Connectors The TRB carries four connectors, two located at each end of the board. P1 is a 96- pin, male right- angled euro- connector, located on the rear edge of the board, carrying power. P2 is a 96- pin, male, right- angled euro- connector, also located on the rear edge of the board, carrying power and digital control signals. P3 and P4 are 34- pin, male, right- angled connectors with ejector/latch, located on the front edge of the board. Each connector carries 16 input/outputs to the transducer/preamplifier.
70
852--164111 / A
Maintenance manual
Low Voltage Power Unit (LVPU)

The purpose of the Low Voltage Power Unit (LVPU) is to supply power to all the modules in the Transceiver Unit, except the high voltage power for the transmission, power to PU and +/12Vdc. The Low Voltage Power Unit is located between the Transmitter/Receiver Boards and the High Voltage Power Supply in the Receiver Rack. The power supply is a plug- in module. It has two front mounted fuses, one service switch, and one switch to select 115 or 230 Vac mains input.
Switched power supply Mains transformer Ulveco N14034-TD Used in analogue power supply MAP55-4001
TB1
P1
1 3
P2
(CD5488A)
On/off relay
Power supply MAP55-1024M Stand-by power
Figure 23 - The Low Voltage Power Supply
How it works
The power unit contains two separate power supplies; one switched power supply (MAP55- 4001) and one for standby power (MAP55- 1024M). The output of the standby power supply is 24 Vdc.
852--164111 / A
Line filter
71
5 21
A1
Base version
The power unit has a service switch. When this is set to normal, the power supply is controlled by the on/off relay. This relay is remote controlled from a switch in the operator room. When you disengage the relay, you can control the power supply manually from the Transceiver Rack using the service switch. It is then possible to activate parts of the system (service mode). The transformers and rectifiers function is to provide 8 Vdc output for the receivers either we have 115 Vac or 230 Vac input.
Refer to the block diagram in figure 24 and the circuit diagram on page 250.
24 Vdc stand-by power
Stand-by power S202
Service Off
On/off from remote 24 Vdc to heater 24 Vdc to fans
Normal
115/230 Vac in
115/230 Vac to HVPS +12 Vdc Switch mode power -12 Vdc +24 Vdc GND +5 Vdc
(Cd5497)
230 V
+ 8 Vdc + 8 Vdc -
115 V
S201
Figure 24 - The Low Voltage Power Unit simplified block diagram
Facilities
LEDs L201: Indicator for mains input L202: Indicator for 24 Vdc stand by mode
72
852--164111 / A
Maintenance manual
L203: Lit to indicate AC supply to switched and analogue L204: Lit to indicate AC supply to analogue power.
SIMRAD
POWER SUPPLY 290-112750 +7,5V Analog REF Power -7,5V Supply +5VA -5VA +5V +12V Switched -12V Power +24V Supply GND Service OFF Normal On/off Relay
F203
F203 L203
S202
On/off relay
+24V REF
24V Stand-by
L202
(CD5488B)
F201 8A
Slow Blow
F202 8A
L201
Mains input 115/230Vac
S201
S 201 230Vac
Figure 25 - The front panel Test points None Links None Switches S201: Switch for mains input 115/230 Vac
852--164111 / A
73
Base version
S202: Service/Off/Normal switch Connections P1 P2 Fuses F201: Primary fuse F202: Primary fuse F203: Thermostat fuse inside the torodial transformer
74
852--164111 / A
Maintenance manual
High Voltage Power Supply (HV2PS2)

The high voltage power supply (HV2PS2) is used for transforming from 115/230 Vac to a controlled dc voltage. The high voltage power supply consist of one rectifier module and five dc- dc converter modules mounted on a large heatsink.
How it works
The input module consist of a rectifier with automatic voltage selector. The rectified voltage from the input module is divided and put into five dc- dc converter modules. The output voltage is varied from minimum to maximum in three steps: - 20 dB: - 10 dB: a 14 V module a 14 V module and a 29 V module
Maximum: a 14 V module and four 29 V modules The bleeder is used for reducing the output voltage. The trip voltage of the bleeder can be changed by adjusting potentiometers. The potetiometers is behind the front of the power supply.
Refer to block diagram in figure 26.
29 Vout
29 12V AC1 29 5V -10dB -20dB B L E E D E R 5V -10dB -20dB
AC2 29
14 DC-DC Converter Modules
GND
(CD5721/GIF)
Figure 26 - HV2PS2 block diagram.
852--164111 / A
75
Base version
Facilities
LEDs Test points TP01: TP02: TP03: TP04: TP05: TP06: The negative (ground) output voltage (AGND1). The positive output voltage (VP_POS). Varistor connected to ground (AGND1). Connection for external bleeder. Connects to plug P2. Connection for external bleeder. Connects to plug P2. The positive output voltage (VP_POS).
Control signals - 20 dB, low: Output voltage at - 20 dB of maximum output voltage. - 10 dB, medium: Output voltage at - 10 dB of maximum output voltage. Auxilary supply voltages VCC: The 5V supply voltage at the secondary side (VCC). VBB: The 12V supply voltage at the secondary side (VBB). Input voltage AC1: Main input 115/230 Vac (N). AC2: Main input 115/230 Vac (L). Output voltage AGND1: VP_POS: Adjustments - 20 dB: - 10 dB: Maximum: Adjustment of the bleeder voltage at low voltage operation (- 20 dB). Adjustment of the bleeder voltage at medium voltage operation (- 10 dB). Adjustment of the bleeder voltage at normal voltage operation (0 dB). The negative (ground) output voltage (AGND1). The positive output voltage (VP_POS).
76
852--164111 / A
Maintenance manual
Signal Processor Board (SPB31)

The Signal Processor Board (SPB31) is designed for high speed beamforming and sonar signal processing. The board design is based on the TMS 320C31 floating point DSP (Digital Signal Processor) from Texas Instruments. The Signal Processor Board is designed as a double Europe standard sized printed circuit board. It is equipped with a number of front mounted LEDs, test points, potentiometers and coax connectors. The board is used two places in the EM 120 Transceiver Unit; to control the transmission (SPTX) and the reception (SPRX).
How it works
The main components of the Signal Processor Board are: 1 TMS 320C31 Digital Signal Processor Clock frequency 33.33 or 40 MHz 32- bit data bus 24- bit address bus 40/32- bit floating point unit 1 internal serial line 2 pc 32- bit timers 4 interrupt inputs DMA controller Programmable in C and assembly Emulator and symbolic de- bugger available 2 3 4 5 6 7 8 9 256k x 32 bit PROM. 512 x 32 bit SRAM 25 ns Complex multiplier. 4 serial lines RS422/RS232. Programmable counter for TX clock, 64 CHTX. Dual port interface to P1 bus (Multibus I type). Bus interface to P2 bus. Control bus for control outputs compatible with SPB29.
The Signal Processor Board works very similar to other microprocessor boards. The TMS 320C31 Digital Signal Processor operates with standard peripheral circuitry such as RAM, PROM (with software) and the interface controllers. Devices for disk drive control are omitted, but Dual Port RAM and a complex multiplier is implemented instead. Refer to the block diagram.
852--164111 / A
77
Base version
16-bit databus and 24-bit address bus P1 16-bit databus 24-bit address bus
Bus interface Serial line Signal processor TMS320C31 Emulator
Dual port RAM (DPRAM)
Data bus Address bus
Serial lines
Serial line interface (4 ea)
256k x 32 PROM 512k x 32 RAM
Program counter
Dual port RAM (DPRAM)
Bus interface
Multipliers
(CD1401)
P2 16-bit databus and 24-bit address bus
Figure 27 - Signal Processor Board SPB31 simplified block diagram An emulator for the TMS 320C31 processor is developed. It consists of a controller board in a PC and an active pod which is connected to the target board by a 12 pin plug.
Facilities
Unmounted devices Note that several sockets on the Signal Processor Board may be empty. On EM 120 the Mulitpliers with corresponding DPRAM are not mounted.
78
852--164111 / A
Maintenance manual
Links A large number of links are implemented on the processor board to allow for several different applications. The links are used as follows: LK 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2BI422 to RXDB on U15 LK 2 . . . . . . . . . . . . . . . . . . . . . . . . RXDB2 input to RXDB on U15 LK 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2AI422 to RXDA on U15 LK 4 . . . . . . . . . . . . . . . . . . . . . . . RXDA2 input to RXDA on U15 LK 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CLKIN to U64 LK 6 . . . . FSRO and DRO to set frame sync for sercom on U32 LK 7 . . . RDRO to DRO when sercom in U32 is used on RS232 LK 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clock to U36 LK 9 . . . . . . . . . . . . . . . . . . . . . . . . RXDA input to RXDA on U63 LK 10 . . . . . . . . . . . . . . . . . . . . . . . . RXDB input to RXDB on U63 LK 11 . . . . . . . . . . . . . . . . . . . . . . . . BI422 input to RXDB on U63 LK 12 . . . . . . . . . . . . . . . . . . . . . . . AI422 input to RXDA on U63 LK 13 . . . . . . . . . . . . CLQ to P2A25, U60 must not be mounted LK 14 . . . . . . . . . . TXCLK to P2B24, U60 must not be mounted LK 15 . . . . . . . . . . . . . CLI to P2A24, U60 must not be mounted LK 16 . . . . . . . . . . TSTSIG to P2C23, U60 must not be mounted LK 17 . . . . . . . . . . . TXEN~ to P2A22, U60 must no be mounted LK 18 . . . . . . . . . . . . . . . . . . MEM3 to P2C3, LK30 must be OFF LK 19A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XF0~ as output LK 19B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XF0 as input LK 20A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XF0 as output LK 20B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XF0~ as input LK 23A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XF1~ as output LK 23B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XF1 as input LK 24A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XF1 as output LK 24B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XF1~ as input LK 25A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCLK0~ as output LK 25B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCLK0 as input LK 26A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCLK0 as output LK 26B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCLK0~ as input LK 27A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCLK1~ as output LK 27B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCLK1 as input
852--164111 / A
79
Base version
LK 28A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCKL1 as output LK 28B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCLK1~ as input LK 29 . . . . . . . . . . . . . . . . . . . . . External reset, INIT1, when ON LK 30 . . . . . . . . . . . . . . . . . . IACK~ to P2C3, LK18 must be OFF LK 31 . . . . . . . . . . . . . . . . . . . . . . . . . . U40 to CLKIN on DSP U32 Note that this list is for reference only. Link applications When using the Signal Processor Board in the EM 120 Transceiver Unit, the following links must be ON (closed): SPRX: LK 5 LK 8 LK 9 LK10 LK 31 SPTX: LK 4 LK 5 LK 8 LK 9 LK 10 LK 19 (see below) LK 20 (see below) LK 23 (see below) LK 24 (see below) LK 31
Figure 28 - Signal Processor Board SPB31, default settings
80
(Cd5684)
852--164111 / A
Maintenance manual
LEDs LEDs used for SPTX: D1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . program initialized OK D2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ready for new command D3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . transmit active D4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BIST active D5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . not used D6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . test purpose D7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . test purpose D8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . test purpose LEDs used for SPRX: D1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . program initialized OK D2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BIST active D3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . aquisition of reciever data D4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . aquisition of reciever data D5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . simulator active D6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . not used D8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . not used
Test points TP 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GND TP 2 . . . . . . . . . . . . . . . . . . . . . . General purpose test output no.1 TP 3 . . . . . . . . . . . . . . . . . . . . . . General purpose test output no.2 TP 4 . . . . . . . . . . . . . . . . . . . . . . General purpose test output no.3 TP 5 . . . . . . . . . . . . . . . . . . . . . . General purpose test output no.4 TP 6 . . . . . . . . . . . . . . . . . . . . . . General purpose test output no.5 TP 7 . . . . . . . . . . . . . . . . . . . . . . General purpose test output no.6 TP 8 . . . . . . . . . . . . . . . . . . . . . . General purpose test output no.7 TP 9 . . . . . . . . . . . . . . . . . . . . . . General purpose test output no.8 TP 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . +5 Vdc TP 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clock pulse, CP, monitor TP 12 . . . . . . . . . . . . . . . . . . . . . . . WE~ for testing RAM loading TP 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GND TP 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GND TP 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GND
852--164111 / A
81
Base version
Ground
TP 1 TP 2 D1 D2 D3 D4 D5 D6 D7 D8 TP 6 TP 7 TP 8 TP 9 TP 10 TP 3 TP 4 TP 5
Same as LED D1 Same as LED D2 Same as LED D3 Same as LED D4 Same as LED D5 Same as LED D6 Same as LED D7 Same as LED D8 +5 Vdc
Software controlled LEDs +5 Vdc
D9
Test signal output Reset
P3 S1
TP 11 TP 12
Clock pulse WE/ to test RAM
J2 Serial lines
Emulator
P9
J1
(CD4340)
Serial lines
Ground
TP 15
Figure 29 - Signal Processor Board SPB31, front mounted devices Connections The following connections are made to the Signal Processor Board: P 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multibus P 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . Signal processor external bus P 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test signal output J1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Serial lines J2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Serial lines The trig out puls is active during transmit, and generated by SPRX. This is a TTL level pulse and is active when low.
The connections are explained in the figure on page 44 . The Receiver Backplane connections(PXB- P3) are explained on page 84.
82
852--164111 / A
Maintenance manual
Receiver Backplane (RXBP)

The purpose of the Receiver Backplane is to enable communication between the circuit boards plugged into it, and between these circuit boards and the external circuitry in the cabinet. The RXBP is located behind the middle wired rack in the Transceiver Unit, and holds the following circuit boards: Transmitter/Receiver Board 1 Transmitter/Receiver Board 2 Transmitter/Receiver Board 3 Transmitter/Receiver Board 4 Low Voltage Power Supply High Voltage Power Supply Signal Processor Board RX Capacitor Bank
How it works
There are no active components on this backplane.
Facilities
LEDs None
P5 LK9 P2 LK6 P3 TP9
TP1
P11
P14
TP10
P12 P6 TP12 TP11 LK7 P7 TP14 P8 LK8 P10 P9 P13 TP13 TP8 TP7 TP6 P4 TP5 TP3 TP4 TP2
(CD5466B / 382-134122D)
Figure 30 - Receiver Backplane, rear side
852--164111 / A
83
Base version
Test points All the test points listed below are only used during development and debugging: TP 1: GND TP 2: Read pulse to the TRB TP 3: Filter clk. to PDHs on the TRB TP 4: Write pulse to the TRB TP 5: Sample and hold to PDHs on the TRB TP 6: Four times demodulater frequency to PDHs on the TRB TP 7: TX enable to the TRB TP 8: GND TP 9: GND TP 10: Write pulse to fifo on the BSP TP 11: Read pulse to 2 port RAM on the SPTX TP 12: Write pulse to 2 port RAM on the SPTX TP 13: Test signal input to PDHs on the TRB Only links LK7 and LK8 are applicable for system setup. These are closed as shown in the illustration.
HVCLK HVCKR
(Cd5482)
HVCK
DBT0 DA0
LK7 LK8
DB0
Figure 31 - Applicable links Connections The sockets on the rear side of the backplane and their connections in the EM 120 Transceiver Unit are described in the tables below.
(Cd5481)
Pin 1 Pin 2 Pin 3 Pin 4
Figure 32 - Pin configuration
84
852--164111 / A
Maintenance manual
RXB-P2 1 2 3 4 RXB-P3 1 1 2 2 3 4 RXB-P5 1 2 3 4 RXB-P6 1 2 3 4 RXB-P7 1 2 3 4 RXB-P8 1 2 3 4
Signal STBY+ STBY-ON
Connection Bottom plate--Remote pin 3 Bottom plate--Remote pin 4 Bottom plate--Remote pin 5
Signal HEAT HEAT STBY-STBY-TRIG DGND Signal +12VH HGND HGND +5VH Signal HGND HGND HV HV Signal HGND HGND HV HV Signal HGND HGND HV HV
Connection Wall sect.--Resistor pin 1 Heater--Terminal pin 2 Wall sect.--Resistor pin 2 Heater--Terminal pin 1 Bottom plate--Remote pin 1 Bottom plate--Remote pin 2 Connection TXB--P3 pin 4 TXB--P3 pin 2 TXB--P3 pin 3 TXB--P3 pin 1 Connection TXB--P15 pin 1 TXB--P15 pin 2 TXB--P15 pin 3 TXB--P15 pin 4 Connection TXB--P17 pin 1 TXB--P17 pin 2 TXB--P17 pin 3 TXB--P17 pin 4 Connection TXB--P19 pin 1 TXB--P19 pin 2 TXB--P19 pin 3 TXB--P19 pin 4
852--164111 / A
85
Base version
RXB-P9 1 2 3 4 RXB-P13 1 2 3 4 RXB-P14 1 2 3 4
Signal POW1 POW2 POW1 POW2 Signal +5 Vdc +5Vdc DGND DGND Signal +5 Vdc +5Vdc DGND DGND
Connection TX/RX Fan pin 1 TX/RX Fan pin 3 PU Fuse pin 3 PU Fuse pin 4 Connection TXB--P2 pin 1 TBX--P2 pin 2 TBX--P2 pin 3 TBX--P2 pin 4 Connection TXB--P2 pin 1 TBX--P2 pin 2 TBX--P2 pin 3 TBX--P2 pin 4
(CD5461A / 861-213155/A)
P5 P2
TP1
P3
TP10 TP9
P14
TP12
TP4 TP11
TP2
P6 P7
LK7 TP13
P4 P10 P9
TP5 TP3
TP6
P8
LK8
P13
Figure 33 - The Receiver Backplane
86
852--164111 / A
Maintenance manual
64-Channel Transmitter (TX64)

Once the transmission parameters have been calculated by the Signal Processor Tx (SPTX), each of the transmitter boards is addressed. The databus from the SPTX is connected to all the boards, and data for the individual transmitters is loaded into the onboard RAMs as they are addressed from the SPTX. The output from the TX64 RAM bank is connected to the output stages, which are implemented using Kongsberg Simrad- designed amplifier hybrids. The physical number of TX64 boards fitted to the EM 120 transceiver depends on the chosen system specifications. Thus, up to 14 64- Channel Transmitter (TX64) boards are used.
How it works
Overview The TX64 boards are controlled by the Signal Processor TX (SPTX), and the output signals are made available on the front mounted sockets. Flat ribbon cables connect these output pulses to the filters. The TX64 board is equipped with two large front mounted connectors. Two LED indicators and one test point are located between these connectors. The test point is a ground (GND) connection, while the LEDs monitor the +5 Vdc and +12 Vdc supply voltages. The TX64 board is equipped with eight onboard fuses. These fuses are located on the High Voltage (HV) supply line, and each fuse protects a group of eight transmitters. Fuse rating is 4 A, physical size is 5 x 20 mm. The functions of the transmitter may be divided into three parts: The power unit (Power & Fuses) The digital control unit The analogue transmitter driver unit (TX Hybrid) Power unit The power unit includes the three separate supply voltages used and the components around them. The voltages are +12 Vdc, +5 Vdc and High Voltage (HV). The value of the HV depends on the desired output power. Typical range is +13 to +135 Vdc. Digital control unit The main function of the digital control unit is to supply the analogue transmitter unit with the correct driving signals.
852--164111 / A
87
Base version
(CD1405C)
Data and address buses to/from the Signal Processor Tx (SPTX)
Data, address and control buffers
Address latch and sequential counter
Fault detection buffer
Random Access Memory
On-board errors
Latch 1-15
Latch 16
To the remaining 60 output hybrids
Output hybrid
Output hybrid
Output hybrid
Output hybrid
To the filters
Figure 34 - 64- Channel Transmitter (TX64) block diagram
The shape of the driving signals are temporarily stored in RAMs on the board. The RAMs are filled by the host processor. The drive signals for the output pulses are derived from the pattern. The signals are clocked and latched before they are supplied to the transmitter hybrids. The transmitted pulse is controlled by the address latches and the controller. The transmitted frequency is increased by 64 times, and is then supplied to the CLK input. The TX Enable (TXEN/) input enables the transmitters and controls the transmit pulse length. Status information such as fuse blown can be read from the fault detect buffer on the data bus. To lower the sidelobe level, IC U89 is omitted and a piggy back board is inserted. This piggy back board contains a PLD with doubled resolution for transmit beampattern.
88
852--164111 / A
Maintenance manual
Analogue transmitter unit There are 64 transmitters on the board. Each of these is a thick film hybrid designed by Kongsberg Simrad. There are no frequency dependent components on the board. The transmitters are electrically designed into in groups of eight, each group being protected by a 4 A fuse. The transmitter outputs are brought to the front edge connectors P3 and P4.
Facilities
LEDs D 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . +5 Vdc D 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . +12 Vdc
Outputs P3
+12 Vdc +5 Vdc
D9 D10
P4
Figure 35 - 64- Channel Transmitter (TX64) front mounted devices Test points TP 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GND Links A number of links are implemented on the board to allow for several different applications. The links are used as follows: LK1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Selects PROM (when ON) LK2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Selects RAM (when ON) Link applications The following links are ON (closed) in this application: LK2 Switches None Connections The TX64 is equipped with the following connectors:
(CD4417)
852--164111 / A
89
Base version
P 1 . . . . . . . . . . . . . . . Connections to the external power supply P 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . Interface to control processor P 3 . . . . . . . . . . . . Outputs from channels 01- 32. Front mounted P 4 . . . . . . . . . . . . Outputs from channels 33- 64. Front mounted Fuses F 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . TX group 1, Channels 01- 08 F 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . TX group 2, Channels 09- 16 F 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . TX group 3, Channels 17- 24 F 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . TX group 4, Channels 25- 32 F 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . TX group 5, Channels 33- 40 F 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . TX group 6, Channels 41- 48 F 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . TX group 7, Channels 49- 56 F 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . TX group 8, Channels 57- 64 Fuse rating is 4 A. Physical fuse size is 4 x 20 mm. Oscilloscope check points The Clock (CLK) is input on pin P2 B24, and connected to buffer U90, pin 4. The clock frequency varies with the transmission frequency, and will be 64 times this. Frequency alterations during one transmission are achieved by changing the clock frequency. The TX Enable (TXEN/) is input on pin P2 A22, and connected to buffer U90, pin 2. The TXEN/ pulse is the transmit trigger, and the length of the TXEN is also the length of the transmitted pulse. For EM 120 the TX frequency is from 11.25 to 12.60 kHz.
90
852--164111 / A
Maintenance manual
Transmitter Backplane (TXBP)

The purpose of the transmitter Backplane is to enable communication between the circuit boards plugged into it, and between these circuit boards and the external circuitry in the cabinet. The TXBP is located behind the bottom wired rack in the Transceiver Unit, and holds the following circuit boards: 64- channel Transmitter Board (TX64) Signal Processor Board TX (SPB31)
(CD5461B / 213155/A)
P19
P18
P17
P16
P15
P14
P13
P12
P8
P7 P9 P3
Vorsicht Spannung Attention Danger
P1
P2
Fan TX/RX 1 2 3
Figure 36 - The Transmitter Backplane

P8 P19 P18 P17 P16 P15 P14 P6 P13 P5 P12 P4 P11 P10
C23
C21
C19
C19
C17
C13
C11
C9
C7
C5
P10
C3
P11
P6
P5
P4
C1
TP1 C24 C22 C20 C18 C16 C14 C12 C10 C8 C6 C4 C2
P7 P9
P3
TP4 TP3
P1
P2
TP6
TP5
(Cd5524 / 213169/A)
Figure 37 - Transmitter Backplane, rear side
852--164111 / A
91
Base version
How it works
Facilities
LEDs None Test points The following testpoints are only used during development and debugging. TP 1: DGND TP 2: DGND TP 3: SMEM/ Active low when data is read from TX64 TP 4: DMEM/ Active low when data is written to TX64 TP 5: DGND TP 6: TXE/ Active low when transmit is ongoing. Links None. Connections The sockets on the rear side of the backplane and their connections in the EM 120 Transceiver Unit are described in the tables below.
(Cd5481)
Pin 1 Pin 2 Pin 3 Pin 4
92
852--164111 / A
Maintenance manual
Bb Aa Cc
Dd Ee
Ff Gg
Hh
(CD5461C)
Figure 39 - Capacitor numbers
TXB-P1 1 2 3 4
Signal GND GND +12 Vdc +12 Vdc
Connection PU power supply PU power supply PU power supply PU power supply
TXB-P2 1 2 3 4
Signal +5 Vdc +5 Vdc DGND DGND
Connection RXB--P13 pin 1 RXB--P13 pin 2 RXB--P13 pin 3 RXB--P13 pin 4
TXB-P3 1 2 3 4
Signal +5 VH HGND HGND +12 VH
Connection RXB--P5 pin 4 RXB--P5 pin 2 RXB--P5 pin 3 RXB--P5 pin 1
TXB-P4 1 2 3 4
Signal HVGND HVGND HV HV
Connection Capacitor c--base sect. Capacitor c--base sect.
TXB-P5 1 2 3 4
Connection Capacitor e--base sect. Capacitor e--base sect.
852--164111 / A
93
Base version
TXB-P6 1 2 3 4
Connection Capacitor g--base sect. Capacitor g--base sect.
TXB-P10 1 2 3 4
Connection Capacitor a--base sect. Capacitor a--base sect.
TXB-P11 1 2 3 4
Connection Capacitor b--base sect. Capacitor b--base sect.
TXB-P12 1 2 3 4
Connection Capacitor d--base sect. Capacitor d--base sect.
TXB-P13 1 2 3 4
Connection Capacitor f--base sect. Capacitor f--base sect.
TXB-P14 1 2 3 4
Connection Capacitor h--base sect. Capacitor h--base sect. Bleeder A
94
852--164111 / A
Maintenance manual
TXB-P15 1 2 3 4 TXB-P17 1 2 3 4 TXB-P19 1 2 3 4
Signal HVGND HVGND HV HV Signal
Connection RXB--P6 pin 1 RXB--P6 pin 2 RXB--P6 pin 3 RXB--P6 pin 4 Connection RXB--P7 pin 1 RXB--P7 pin 2
HV HV Signal HVGND HVGND HV HV
RXB--P7 pin 3 RXB--P7 pin 4 Connection RXB--P8 pin 1 RXB--P8 pin 2 RXB--P8 pin 3 RXB--P8 pin 4
The bleeder is mounted on the Processing Unit power supply cover.
852--164111 / A
95
Base version
5
5.1
PREAMPLIFIER UNIT
Description and main functions
Overview
The EM 120 Preamplifier Unit preamlifies the signals from the hydrophones. The EM 120 Preamplifier Unit contains the preamplifiers for the receive signals. The unit also provides the frequency splitting circuitry to feed low frequency signals to the optional Sub Bottom Profiler. This chapter provides the following information:
Description and main functions, page 96. Preamplifier Unit outline, page 97. Preamplifier Unit wired cabinet, page 98. Theory of operation, page 99. Preamplifier Unit details, page 100. Circuit board descriptions, page 101.
96
852--164111 / A
Maintenance manual
630 mm 600 mm
680 mm
(CD5584 / 834-213112AB)
Figure 40 - EM 120 Preamplifier Unit - Outline dimensions
300 mm
920 mm
852--164111 / A
97
Base version
Power supply
Circuit breaker
KONGSBERG SIMRAD
12 V POWER SUPPLY 290 - 213103
(CD5583 / 860-213423/A)
Cooling fans
Preamplifier (x8)
Input cable (x16)
Figure 41 - EM 120 Preamplifier Unit - wired cabinet
98
852--164111 / A
Maintenance manual
5.2
Theory of operation
Overview
This chapter presents a functional description of the Preamplifier Unit.

The simplified block diagram for the preamplifier Unit present the following main functions:
Hydrophone 2-8 kHz Optional Sub Bottom Profiler
(CD5707b / GIF)
Differential Amplifier with 40 dB gain
Band Pass Filters
11-13 kHz
Transceiver Unit
Figure 42 - Block diagram of one of the channels.
Control functions
The preamplifier has no external control interface, and the power is on all the time. (No remote control).
Cooling
The fans usually operate with 230 Vac, and must therefore be changed if 110 Vac is used.
For external cabling, please refer to the chapter concerning transducer cables, page 26.
852--164111 / A
99
Base version
5.3
Preamplifier Unit details

Preamplifier
2, 4 or 8 DP16 preamplifier boards are mounted in this unit.
Power Supply
This is a linear commercial power supply, that feeds power to thw preamplifier unit.
The power supply is explained on page 107
Backplane
The Preamplifier Unit uses a passive backplane
The backplane is explained on page 108
100
852--164111 / A
Maintenance manual
5.4
Circuit board descriptions

Overview
This chapter describes all the circuit boards and modules in the EM 120 Preamplifier Unit. A functional description with a block diagram is provided, as well as the facilities provided for maintenance.

The block diagram shows one of the 8 channels:
Differential input
2-8 kHz Band Pass Filters 11-13 kHz
P1
P3, P4
(CD5707c / GIF)
P2
Figure 43 - Block diagram of one of the 16 channels.
852--164111 / A
101
Base version
Preamplifier (DP16)
The purpose of the Preamplifier is to amplify and filter the signals from the hydrophones.
How it works
2, 4 or 8 preamplifier circuit boards (DP16) are mounted in this unit. The DP16 is a 16- channel, dual preamplifier for the EM 120 multibeam echo sounder. Each channel consists of a differential input preamplifier, followed by two parallel filters, one bandpass filter for a 2 - 8 kHz passband, one for a 11 - 13 kHz passband. The nominal gain for both channels is 40.0 dB.
Differential input HF Filter Optional Sub Bottom Profiler
(CD5707 / GIF)
LF Filter
Transceiver Unit
Figure 44 - Block diagram of one of the channels. This HF filter is a passive LCR filter with adjustable inductors. The LF filter is a standard active filter with no adjustable components.
Facilities
LEDs None Test points The table below shows the available test points on the circuit board: Testpoints LK1 TP17 TP18 TP1 TP2 TP3 TP4 TP5 TP6 Description Probe ground point (scopelink) + 8 V regulated supply voltage - 8 V regulated supply voltage Channel 16 preamplifier output Channel 15 preamplifier output Channel 14 preamplifier output Channel 13 preamplifier output Channel 12 preamplifier output Channel 11 preamplifier output
102
852--164111 / A
Maintenance manual
TP7 TP8 TP9 TP10 TP11 TP12 TP13 TP14 TP15 TP16
Channel 10 preamplifier output Channel 9 preamplifier output Channel 8 preamplifier output Channel 7 preamplifier output Channel 6 preamplifier output Channel 5 preamplifier output Channel 4 preamplifier output Channel 3 preamplifier output Channel 2 preamplifier output Channel 1 preamplifier output
Connections Input signals from the hydrophones are connected on the front of the pcb (P3, P4). Output signals to Transceiver Unit and to optional Sub Bottom Profiler is connected to the backplane (P2 for TRU, P1 for Sub Bottom Profiler). Connector P1 and P2 are 96 pin euro edge connectors. Connector P3 and P4 are 25 pin D- sub connectors. The table below shows the connections for P1. A a-1 a-2 a-3 a-4 a-5 a-6 a-7 a-8 a-9 a - 10 a - 11 a - 12 a - 13 a - 14 a - 15 a - 16 a - 17 a - 18 a - 19 Signal VCC VCC VCC VCC VCC GND GND GND GND GND GND GND GND GND GND GND GND GND GND B b- 1 b- 2 b- 3 b- 4 b- 5 b- 6 b- 7 b- 8 b- 9 b - 10 b - 11 b - 12 b - 13 b - 14 b - 15 b - 16 b - 17 b - 18 b - 19 Signal VCC VCC VCC VCC VCC GND GND GND GND GND GND GND GND GND GND GND GND GND GND C c- 1 c- 2 c- 3 c- 4 c- 5 c- 6 c- 7 c- 8 c- 9 c - 10 c - 11 c - 12 c - 13 c - 14 c - 15 c - 16 c - 17 c - 18 c - 19 Signal VCC VCC VCC VCC VCC GND GND GND LF_16 LF_15 LF_14 LF_13 LF_12 LF_11 LF_10 LF_9 LF_8 LF_7 LF_6
852--164111 / A
103
Base version
a - 20 a - 21 a - 22 a - 23 a - 24 a - 25 a - 26 a - 27 a - 28 a - 29 a - 30 a - 31 a - 32 A a-1 a-2 a-3 a-4 a-5 a-6 a-7 a-8 a-9 a - 10 a - 11 a - 12 a - 13 a - 14 a - 15 a - 16 a - 17 a - 18 a - 19 a - 20 a - 21 a - 22
GND GND GND GND GND GND GND GND VEE VEE VEE VEE VEE Signal VCC VCC VCC VCC VCC GND GND GND GND GND GND GND GND GND GND GND GND GND GND GND GND GND
b - 20 b - 21 b - 22 b - 23 b - 24 b - 25 b - 26 b - 27 b - 28 b - 29 b - 30 b - 31 b - 32 B b- 1 b- 2 b- 3 b- 4 b- 5 b- 6 b- 7 b- 8 b- 9 b - 10 b - 11 b - 12 b - 13 b - 14 b - 15 b - 16 b - 17 b - 18 b - 19 b - 20 b - 21 b - 22
GND GND GND GND GND GND GND GND VEE VEE VEE VEE VEE Signal VCC VCC VCC VCC VCC GND GND GND GND GND GND GND GND GND GND GND GND GND GND GND GND GND
c - 20 c - 21 c - 22 c - 23 c - 24 c - 25 c - 26 c - 27 c - 28 c - 29 c - 30 c - 31 c - 32 C c- 1 c- 2 c- 3 c- 4 c- 5 c- 6 c- 7 c- 8 c- 9 c - 10 c - 11 c - 12 c - 13 c - 14 c - 15 c - 16 c - 17 c - 18 c - 19 c - 20 c - 21 c - 22
LF_5 LF_4 LF_3 LF_2 LF_1 GND GND GND VEE VEE VEE VEE VEE Signal VCC VCC VCC VCC VCC GND GND GND HF_16 HF_15 HF_14 HF_13 HF_12 HF_11 HF_10 HF_9 HF_8 HF_7 HF_6 HF_5 HF_4 HF_3
The table below shows the connections for P2.
104
852--164111 / A
Maintenance manual
a - 23 a - 24 a - 25 a - 26 a - 27 a - 28 a - 29 a - 30 a - 31 a - 32
GND GND GND GND GND VEE VEE VEE VEE VEE
b - 23 b - 24 b - 25 b - 26 b - 27 b - 28 b - 29 b - 30 b - 31 b - 32
GND GND GND GND GND VEE VEE VEE VEE VEE
c - 23 c - 24 c - 25 c - 26 c - 27 c - 28 c - 29 c - 30 c - 31 c - 32
HF_2 HF_1 GND GND GND VEE VEE VEE VEE VEE
The table below shows the connections for P3. Pin 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 IN_LO_1 IN_LO_2 IN_LO_3 IN_LO_4 IN_LO_5 IN_LO_6 IN_LO_7 IN_LO_8 Channel 1 input low side Channel 2 input low side Channel 3 input low side Channel 4 input low side Channel 5 input low side Channel 6 input low side Channel 7 input low side Channel 8 input low side IN_HI_1 IN_HI_2 IN_HI_3 IN_HI_4 IN_HI_5 IN_HI_6 IN_HI_7 IN_HI_8 Channel 1 input high side Channel 2 input high side Channel 3 input high side Channel 4 input high side Channel 5 input high side Channel 6 input high side Channel 7 input high side Channel 8 input high side Signal Description
852--164111 / A
105
Base version
24 25 The table below shows the connections for P4. Pin 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 IN_LO_9 IN_LO_10 IN_LO_11 IN_LO_12 IN_LO_13 IN_LO_14 IN_LO_15 IN_LO_16 Channel 9 input low side Channel 10 input low side Channel 11 input low side Channel 12 input low side Channel 13 input low side Channel 14 input low side Channel 15 input low side Channel 16 input low side IN_HI_9 IN_HI_10 IN_HI_11 IN_HI_12 IN_HI_13 IN_HI_14 IN_HI_15 IN_HI_16 Channel 9 input high side Channel 10 input high side Channel 11 input high side Channel 12 input high side Channel 13 input high side Channel 14 input high side Channel 15 input high side Channel 16 input high side Signal Description
106
852--164111 / A
Maintenance manual
Preamplifier Unit Power Supply (PAPS)

The power supply feeds power to the preamplifier unit.
How it works
Commercial Linear supply mounted in a plug in unit.
5 1 3 2 4 Input Voltage Connection -12V out -S +S Ccom -S +S +12V out

(CD5607 / 860-213104/B)
P1
P2
Figure 45 - Preamplifier Power Supply
Facilities
LEDs None Test points None Links None (AC main selection is done on the backplane).
852--164111 / A
107
Base version
Preamplifier Backplane
The purpose of the Preamplifier Backplane is to enable communication between the circuit boards plugged into it, and between these circuit boards and the external circuitry in the cabinet. The Preamplifier Backplane holds the following circuit boards / modules: Preamplifier (x8) Power Supply.
TP1
BACKPL - J33 BACKPL - J31 BACKPL - J29 BACKPL - J27 BACKPL - J25 BACKPL - J23 BACKPL - J21 BACKPL - J19 BACKPL - J20
TP3
TP2
BACKPL - J34
BACKPL - J32
BACKPL - J30
BACKPL - J28
BACKPL - J26
BACKPL - J24
(CD5603 / 861-213284BA)
Figure 46 - The Preamplifier Backplane
How it works
Facilities
LEDs None Test points TP1: +12V TP2: - 12V TP3: GND TP4: GND TP5: GND
108
BACKPL - J22
RXB-P1
852--164111 / A
Maintenance manual
Links
Pin 1 Pin 2 Pin 3 Pin 4 Pin 5 Pin 6 Pin 7 Pin 8
(CD5609)
Pin 9 Pin 10

AC Input for use at: Jumper Apply AC 100 V AC 2/4 1/5 120 V AC 1/3 2/4 4/1 220 V AC 1/3 2/3 1/5 230/240 V AC 2/3 4/1
Connections If 230 Vac:

RXB-P1 1 1 4 4 Signal AC mains AC mains AC mains AC mains Connection Fuse Fan Fuse Fan
852--164111 / A
109
Base version
Backpl--J19 Backpl--J20 Backpl--J21 Backpl--J22 Backpl--J23 Backpl--J24 Backpl--J25 Backpl--J26 Backpl--J27 Backpl--J28 Backpl--J29 Backpl--J30 Backpl--J31 Backpl--J32 Backpl--J33 Backpl--J34
BP--SBP1 (Sub Bottom Profiler) BP--R1 (TRU) BP--SBP2 BP--R2 BP--SBP3 BP--R3 BP--SBP4 BP--R4 BP--SBP5 BP--R5 BP--SBP6 BP--R6 BP--SBP7 BP--R7 BP--SBP8 BP--R8
110
852--164111 / A
Maintenance manual
J1
J3
J5
J7
J9
J11
J13
J15
J17
J2
J4
J6
J8
J10
J12
J14
J16
J18
Figure 48 - Preamplifier Backplane, front side.
TP1
J33
J31
J29
J27
J25
J23
J21
J19
TP3
TP2
TP5
TP4
J34
J32
J30
J28
J26
J24
J22
J20
P1
(CD5606 / 865-213164/A)
Figure 49 - Preamplifier Backplane, rear side.
852--164111 / A
111
Base version
6
6.1
TX JUNCTION BOX(ES)
Description
This box is only made for routing of transmit signals. There are no components inside the box, but a PCB with several D connectors mounted. Each of the 48 TX modules has a cable with a 25- pin D connector in the end. The transmit section output from the TRU have 24 pcs of 50- pin D connectors. The function of the TX- junction box is to route signals from 2 pcs of 25- pin D connectors to one 50- pin D connector. There are 6 boards in one TX junction box. Each board is then routing 4 psc of 25- pin D connectors to 2psc of 50- pin D connectors.
For cabling, please refer to the chapter concerning transducer cables, page 26.
112
852--164111 / A
Troubleshooting
7
7.1
TROUBLESHOOTING
Messages
Introduction
The EM 120 provides numerous messages to inform you of major and minor hardware and software errors. The messages, if they occur, will be displayed in the Status Display in the Message field. The different utilities operating on the EM 120 Operator Station each issue several messages. These messages can be sorted in four categories: display warnings display errors warnings errors The messages presented as display warnings and warnings merely point out small inaccuracies, and must be regarded as guidelines to the normal operation of the system. The display errors and operational errors reflect major and minor hardware and software errors, some of which must be acted upon to ensure the normal operational capability. The following chapters present all the possible messages, and briefly explain the proper action to be taken. The information is provided as follows:
<Nxxx>: -- <Message text>
Necessary action with applicable references. <Nxxx> is the message identifier. The number will allow you to find the message easier in this document, and it tells you which utility issued it. N - module/utility identifier. xxx - message identifier In the list below you will find one letter representing each module. Each module is described in its own chapter. The number xxx is only an identifier. S: setup messages W: ESO/workstation messages L: launchpad messages E: sound speed profile editor messages P: Ping Display messages
852--164111 / A
113
Base version
The Hardware and CPU CMOS setup messages are presented with the exact same layout. The Hardware messages also start with a message identifier <Nxxx>, and have a following message text. The message text contains an error code which has to be decoded to get the exact error condition.
Refer to Hardware messages on page 148 for details.
Most display errors are equipped with a help- textfunction, giving additional help on the errors. This text will, in most cases, be identical to the action text found in this manual.
114
852--164111 / A
Troubleshooting
7.2
Setup messages
Setup messages
The following messages are presented by the Setup utility.
Display Warnings
S10: -- Remember to set correct Gain parameters when using Manual bottom detection! Normal mode should be Range And Gain, which uses Automatic bottom detection!
This mode should only be used when automatic bottom detection doesnt work. Make sure that the Depth To Normal Incidence depth indicator has a sensible value it should have a value fairly close to the expected depth.
S21: -- The profile is not deep enough, and should be extended. When you select the OK button, the profile will be sent to the profile editor for automatic extension.
All profiles used by the system require a maximum depth of 12000 meters. Profiles less deep will be extended by the system, starting from the original maximum depth. The extension is based on standard table values, with two points interpolated between last value pair in profile and first table value pair.
S32: -- The sound velocity profile <name> contains too few samples.
The profile header says that the profile contains less than two entries. At least two entries are required, and for any real life sounding that is really too few entries.
S33: -- The sound velocity profile <name> contains more than 1000 samples!
The system is not designed to handle profiles exceeding 1000/100 depth/speed pairs. You should use the profile, or download again, using 100 depth/speed pairs as a maximum.
S69: -- Profiles in Simrad Survey Format cannot be downloaded...
The system cannot use this format for sound speed profiles. These profiles are produced when logging data, based on a Simrad ASCII format profile selected by the user. If this ASCII profile is no longer available, and you would like to use it again, you could use the Profile Editor to convert the profile into the Simrad ASCII profile format.
S93: -- Both Heads are currently deactivated! Pinging is disabled...
When configuring a dual head system, at least one of the heads must be set up with one of the available frequencies. Of course, an actual dual head requires both heads being assigned frequencies. A dual head system can also be configured as a single head system, assigning frequencies to only one of the heads.
852--164111 / A
115
Base version
S94: -- You cannot use the same frequency on both sonar heads!
Because of interference problems, running both sonar heads with the same frequency is disabled.
S150: -- The file <filename> was empty, and factory defaults was read. Please verify all settings and save all settings using the File-->Save menu option.
The specified file containing setup parameters (runtime or installation) was empty. When this happens, the system automatically installs the default version of the file. The file may have been corrupted during a program crash.
S237: -- No profile downloaded...
The system has not received any download profiles. When downloading takes place, the setup program is notified of the profile name. So far, it seems that nothing has arrived.
S238: -- Profile not located in profile directory!
When downloading takes place, the setup program is notified of the profile name. The system has received a download profile, but it could not be located in the directory used for sound speed profiles.
Display Errors
S15: -- Unable to write BIST output buffer to printfile <filename>.
An attempt was made to open the printfile in the system defaults directory for writing, but the operation failed. You should have full read and write access to the directory and all files in the directory.
S17: -- Unable to write BIST output buffer to file <filename>.
An attempt was made to open the savefile in the system defaults directory for writing, but the operation failed. You should have full read and write access to the directory and all files in the directory.
S18: -- No reply to the current BIST test!
Each of the Built In Self Test (BIST) commands is required to give a response within a fixed period of time. The length of this period varies with the type of test. The Processing Units has subunits that may not respond in time, but this should be reported back to the operator as part of the reply to the current BIST test. If the Processing Unit does not respond within the allocated time period, you should try one of the other tests to see if this is a general problem. If this is the case, or if the problem persists, you should try rebooting the Processing Unit.
S37: -- Sound Velocity Profile <name> was not found!
116
852--164111 / A
Troubleshooting
The specified profile was not located in the directory containing the sound speed profiles ($SHAREDHOME). You could have misspelt the profile name, or the profile has been removed from this directory after it was selected. Try selecting the profile from the pull- down menu. This menu is updated every time it is opened, and should give you the exact list of available profiles.
S50: -- The file <filename> is not found in the $HOME/<directory>, or in the $NEPTUNEHOME/defaults directory. S64: -- Profile <name> has an error in line 1. The line should contain a space after the opening parenthesis and one space before the closing parenthesis. Correct the profile before reselecting...
According to the Simrad ASCII profile format, this space is required. You can fix the problem using a text editor. If you have downloaded the profile from an external source, please verify that your profile source or download programs adheres to the file syntax.
S65: -- Profile <name> has an error in line 1. It seems that the header does not contain the correct no. of elements. Create the profile before retrying...
The profile header should start with ( and close with ). One or both of these elements could not be located in the header line. You can fix the problem using a text editor. If you have downloaded the profiles from an external source, please verify that your profile source or download programs adheres to the file syntax.
S66: -- Sound Velocity Profile directory <name> not found!
The missing directory ($SHAREDHOME) is created during installation, and should always be present. If not, it means that someone has modified the file system. You should reinstall the system to recreate the proper operating environment.
S70: -- The BIST for SW version returned an empty string!
Each of the Built In Self Test commands will return with the result being displayed in the BIST output area. This message informs you that a reply arrived, but that the reply contained no text to be displayed. This is clearly an error. Please repeat BIST command to check if the problem is repeatable. Errors like this should not occur, and if the problem persists, you are advised to reboot the Processing Unit and restart the operation station software.
852--164111 / A
117
Base version
S73: -- Format error in BIST return for SW version request!
Each of the Built In Self Test commands will return with the result being displayed in the BIST output area. This message informs you that a reply arrived, but that the reply did not match the expected format. This is clearly an error. Please repeat BIST command to check if the problem is repeatable. Errors like this should not occur, and if the problem persists, you are advised to reboot the Processing Unit and restart the operation station software.
S74: -- BSP Test failed -- do you want to reboot the BSP unit?
The BSP sub- unit may occasionally lock up, with no pings being produced from the echo sounder. When that happens, the BSP BIST command will fail with this message. It is, however, possible to restart the BSP without rebooting the Processing Unit. This will happen when you confirm that a reboot is wanted. When the boot is completed, you should run the BSP BIST command again to verify that the unit responds correctly.
S96: -- Environment MODULE_ADDRESSES undefined!
The program cannot operate without the specified environment. Please verify that the correct startup procedure is used.
S97: -- Network Configuration File not found! File: <filename>
The program cannot operate without the specified file. Please verify that the file specified by the environment MODULE_ADDRESSES with hostname as extension is present in your home directory, and that you at least have Read permission.
S147: -- Error sending datagrams to Ping Display!
Communication with the Ping Display uses IP socket communication, where the Ping Display has opened a specific port for data input. This error occurs when the setup program tries to send to that port. The most likely explanation is that the port no. specified for the Ping Display is in use by another program.
S148: -- No profile name entered!
You have not specified a profile name - the input field is empty. Enter a profile name to proceed...
S151: -- The file <filename> is not found in the $HOME directory, or in the $NEPTUNEHOME/defaults directory. After verifying the settings, you may create the file by using the File-->Save menu option. The program terminates when you select the OK button.
118
852--164111 / A
Troubleshooting
The specified file containing setup parameters (runtime or installation) is missing from the system directory, and was not located in any of the predefined locations for the file. The error indicates that the system somehow has been corrupted, possible due to manual operations in the file system. It is advisable to reinstall the system to re- establish system integrity.
S152: -- Not able to copy the file <filename> to $HOME/<filename>. The program terminates when you select the OK button.
The specified file containing setup parameters (runtime or installation) was missing from the system directory, and could not be copied to this directory. Due to problems with the directory access. The error indicates that the system somehow has been corrupted, possible due to manual operations in the file system. It is advisable to reinstall the system to re- establish system integrity.
S206: -- Min. Depth must be less than Max. Depth!
It should be fairly easy to fix - just enter a minimum value less than the maximum value...
S207: -- Max. Depth must be greater than Min. Depth!
It should be fairly easy to fix - just enter a maximum value greater than the minimum value...
S208: -- Legal interval: [<value>, <value>]
The input value is outside the specified interval re- enter value to proceed...
S209: -- Max. Port Angle -- Max. Starboard Angle must be > 40!
The Max. Port Angle and Max. Starboard Angle are restricted with respect to the angle of each other in order to avoid too wide swath. Re- enter value, keeping the input value within restrictions indicated by the message.
S211: -- Couldnt locate Workspace of Main Program!
If this error occurs, it means that certain workspace functions will be disabled, but that the overall functionality will be present. It has been observed that restarting the Operator Station software may remove the problem.
S212: -- Couldnt connect to SMS Server!
Occurs when the program is started independent of the rest of the system, or when the operating environment is insufficiently defined. It means that none of the functionality based on running an integrated system will be present, thereby rendering the system inoperable. If restarting the system does not remove the problem, it is likely, that the easiest way to fix it is to reinstall the software.
852--164111 / A
119
Base version
S213: -- Illegal Window Configuration Command received: <command>
An unknown workspace or window command was received. Should not affect the main functionality of the program.
S214: -- Couldnt send status to SMS Server!
This is a serious error, which should not occur. It reflects internal corruption in the communication link with the rest of the system. It means that none of the functionality based on running an integrated system will be present, thereby rendering the system inoperable. If restarting the system does not remove the problem, it is likely, that the easiest way to fix it is to reinstall the software.
S215: -- Server Connection Broken!
This is a serious error, which should not occur. It reflects internal corruption in the communication link with the rest of the system. It means that none of the functionality based on running an integrated system will be present, thereby rendering the system inoperable. If restarting the system does not remove the problem, it is likely, that the easiest way to fix it is to reinstall the software.
S239: -- Sensor Offset + current sound speed exceeds maximum speed of 1700.0 m/s.
The system does not recognise sound speeds in water exceeding 1700 m/s. To correct, enter an offset value, which keeps the sum of sound speed and offset value below or equal to 1700 m/s.
Errors
S25: -- The Profile contains errors and will not be used. Errors detected:
The same message is used for several types of warnings: 1. Out- of- bounds depth values. Legal interval is 0 - 12000m. 2. Out- of- bounds sound speed values. Legal interval is 1400 - 1700 m/s. 3. Fewer actual samples than stated in profile header, using actual no. of samples in profile. 4. Gradient anolomies checking two neighbouring value pairs. Even though you are given the choice to use the profile, it is recommended that you use the profile editor to verify and correct it. Otherwise, the echo sounder soundings may suffer quality degradation.
S28: -- Too step gradients...
If one or more of the samples are spike values, they should be removed from the profile.
120
852--164111 / A
Troubleshooting
S61: -- The following entries in the set--up--file are missing or contain an error in value specification:
All setup parameters are checked when a setup file is opened. Any parameters that are not within legal range or missing from the file will be listed in this message. By following the instructions, it is possible to get around the problem and recreate the setup file. You may instead check if you have a backup version of the installation file in the system directory by selecting the File- >Read... option. You will probably find some older version of the file, because any modification of the installation parameters followed by a File- Savecreates a backup version of the file to be modified.
S70: -- The BIST for SW version returned an empty string!
Each of the Built In Self Test commands will return with the result being displayed in the BIST output area. This message informs you that a reply arrived, but that the reply contained no text to be displayed. This is clearly an error. Please repeat BIST command to check if the problem is repeatable. Errors like this should not occur, and if the problem persists, you are advised to reboot the Processing Unit and restart the operation station software.
S71: -- The Set--up--file is empty. Do you want to reinstall the default Simrad file?
The file containing installation parameter setup values was empty. When this happens, the system can automatically install the default version of the file. The file may have been corrupted during a program crash. Confirming installation of default file allows you to continue. Otherwise, the system cannot be operated...
S98: -- Error in connecting to input socket for program <program name>.
The setup program tries to open an input socket, but the operation failed. The most likely explanation, is that the port no. specified for the setup program already is in use. Check if any of the programs started from a previous session of the system are still running. If so, terminate these programs. If you do not know how to do this, it will in most cases be sufficient to log out and then back in. This will terminate any running programs and free up resources. Then restart the operator station software...
852--164111 / A
121
Base version
7.3
Launchpad messages
Launchpad messages
The following messages are presented by the Launchpad utility.
Display Warnings
L16: -- No reply from PU on Time Request. Logging NOT started!
When activating logging of data, the system timestamps some of the datagrams used in the process. The time to use was requested from the Processing Unit, but the reply did not arrive within a fixed period of time. This may be due to a Processing Unit running at full capacity, or - if the situation continues, while having a normal load on the system - that you may have network problems.
L39: -- The <program name> program has not yet registered. Do you still want to wait for the program to come up?
When starting one of the programs used by the system, it will try to hook up to enable the necessary communication and supervision. If a program does not succeed with this initial registration or hook up, it may have problems in the initial phase of starting up. Please refer to the Status Display, Messages Section for possible error messages that may help sorting out the problems.
L111: -- Tape Operation Aborted! Reason:
The reason for an aborted tape operation may vary. With the exception of a user- triggered abort, the reason stated in the message body originates from the operating system, but should be fairly easy to understand. Examples of this could be a message stating that the tape drive is offline or that no data cartridge is loaded.
L112: -- You cannot delete the current survey!
The current survey could be active, meaning that the associated directories and files are in use for data storage and processing. Removal of the current survey is therefore prohibited.
122
852--164111 / A
Troubleshooting
L113: -- The Log--file is quite large: size X Mb -- reset recommended!
The messages in the logfile may be viewed using the File- >Print / View command. If the file contains too many messages, it may be prove too crowded for practical purposes. It is recommended that you pay heed to the suggestions of reset offered by the system. Use the File- >Reset Log- file option. If you are afraid of loosing useful information, please note that any errors reported while logging data, is logged in a separate logfile along with the survey data. Also remember, that you are offered the option of backing up your logfile before resetting.
L114: -- You cannot alter logging set--up while logging is Active!
Due to the programmed functionality of the system, some parameters (logging setup & installation parameters) may not be modified, because that would disrupt proper functionality and data integrity.
L117: -- The root partition of this system now has less than 2Mb space left...
If the disk space on the root partition falls to zero, you may experience various types of problems while operating the system. It is advisable to increase this space to a minimum of 10 - 20 Mb.
L230: -- Operator <name> has no Config--file...
Use the Update Operators Config- file popup menu option on the All Programs icon in the Programs section of the Launchpad. This will generate a default file for the current operator.
L321: --This is the systems broadcast IP address, and cannot be deleted. If you were thinking of defining a new broadcast address, this one will be automatically adjusted whenever the systems IP address is modified.
When removing an IP address, all programs having the selected address will be modified. Since the selected address is of vital importance for the system, deletion or modification is not allowed. The address is used to establish and maintain the connection with the echo sounder.
L325: -- You cannot change the datagram set--up of the systems reserved programs!
Currently, only user- defined datagram subscriptions may be modified. Allowing the user to modify the flow of datagrams needed for proper operation of the system could result in operational problems.
852--164111 / A
123
Base version
L326: -- You cannot modify the IP address of the systems reserved programs!
Currently, only user- defined datagram subscription setup may be modified. Allowing the user to modify the networking setup, needed for proper operation of the system, could result in operational problems.
L327: -- The specified IP Port no. is outside bounds! Legal interval: [2000, 6000]
The interval is limited to avoid interfering with the internal port no. usage of the system. Using port no.s already in use will give operational problems, both for the system programs and for user programs.
L328: -- IP Port no. <port no.> is already in use by the <subscriber name> subscriber! Legal IP Port interval: [2000, 6000]
Opening and using the same port no. for reading is not allowed. You may send datagrams to the same port no. from several programs, but since you are defining datagram distribution, you cannot use the same port as another program.
L333: -- Logging cannot be started when Edit Mode is enabled in the Set--up menu!
The reason for this restriction is that when logging to a line is started, all current values of the installation parameters are logged with the data. And since only one such representation is possible per line, editing of these parameters is prohibited when already logging.
L335: -- Initial Power--Up Test was interrupted! Echo Sounder Not Ready!
The initial power- up test was interrupted by the user. And since it is an absolute requirement that this test is successfully completed, this test should be performed (with no errors reported).
L336: -- No Sound Speed Probe values received!
The system is supposed to receive Sound Speed Probe values, bot does not receive any. Verify probe connections, setup and power.
L357: -- Datagram subscriber remoteLogging not defined! Use Options-->DatagramSubscriptions...to enter remoteLogging as a subscriber. Remember to supply IP address and port.no. to receive datagrams on!
The system has received a Remote Control datagram, but vital information is missing from the datagram distribution setup. Without this, none of the remote control functionality will be available. The rest of the sounder will operate as normal.
124
852--164111 / A
Troubleshooting
L358: -- No datagrams are selected for the remoteLogging subscriber! Use Options-->DatagramSubscriptions... and select datagrams for subscription for the remoteLogging subscriber.
When using the Remote Control functionality, you must define a selection of datagrams that you want distributed to the remoteLogging subscriber. Otherwise, nothing will flow to this subscriber, even though it is properly defined with an IP address and port number.
L372: -- Could not verify incoming profile!
The Profile Editor is already running, and profile verification is currently suspended. Terminating the current editor session will automatically bring up the received profile for verification.
Display Errors
L12: -- The following Program(s) should always run, but is still NOT running:
The Operator Station software is an integrated system, and is based on having a predefined set of programs running. If not, the echo sounder cannot be operated. You may look for any messages related to the offending program in the Messages area of the Status Display, or use the File- >Print / View menu item to bring up the Message Viewer. Select the icon for the offending program(s) to check for any messages that could help you locate and fix the problem.
L13: -- Echo Sounder Not Ready! The Initial Power Up Built In Self Test (BIST) has failed. Details may be found in the ESO Set--up BIST Self Test (Show-->Testing) menu.
The Echo Sounder has a range of Built In Self Test (BIST) commands, testing various parts of the Sounder. Every time the Operator Station software is started, a link to the Processing Unit is established and the Initial Power- Up- Test is performed. If this fails, the Echo Sounder is inoperable, and the operator should examine the error messages in the BIST test window in the Set- up- program. Additional status information may be obtained using the other BIST tests available.
852--164111 / A
125
Base version
L15: -- Error in Runtime or Installation set--up values! Must be corrected before activating!
All parameters go through verification checks. First while reading from the Set- up- file, and second while entering parameters manually. The reported error is detected while reading from a Set- up- file, and will block Echo Sounder operation until corrected. Set the correct value for the offending parameter(s) in the setup program, and use the File menu Read command to read the setup back in. This will automatically verify the new setup.
L40: -- The following Program(s) has not yet registered:
All programs started and supervised by the Launchpad establishes a communication link with the system when they are launched. The listed program(s) did not succeed in establishing this link. It could be that the program (s) crashed before the linkup was attempted. If so, the program(s) has no possibility to communicate with the rest of the system. You may try a manual start of the system in a window, to see if you can find any useful messages written in the window.
L47: -- The Initial Power Up Self Test failed. Do you want to repeat the test?
Please refer to the test menus in the Echo Sounder Set- up program for details.
L59: -- Echo Sounder Not Ready! Error in Sound Speed Profile!
There are no samples in the current Sound Speed Profile! Verify & correct current profile, or select a new one! After doing this, you should run the Power Up Built In Self Test (BIST) to enable the system.
L60: -- Echo Sounder Not Ready! Error in echo sounder set--up parameters!
All parameters go through verification checks. First while reading from setup- file and second when entering parameters manually. The reported error is detected while reading from the setup- file, and must be corrected before continuing! After doing this, you should run the Power Up Built In Self Test (BIST) to enable the system.
L62: -- No Processing Unit has been detected while scanning the Network. Do you want to terminate the Launchpad?
126
852--164111 / A
Troubleshooting
The Operator Station is not receiving broadcast datagrams from the Processing Unit. The continuing flow of broadcast datagrams tells the rest of the system that the PU is still alive. To prevent gaps in the line and possible data corruption, logging was stopped. Possible reasons for loss of contact: . Processing Unit is not Powered On . Network Cable Problems . Configuration Errors . Processing Unit Hardware / Software malfunction
L67: -- Format Error in Processing Unit Broadcast!
The Processing Units broadcast their presence on the Network. Such a broadcast message was received, but did not meet the format specification.
L76: -- No reply to the Initial Power--Up BIST. Do you want to Retry?
The network connection is OK, but the Processing Unit is not responding. Cancel the current attempt. Power the Processing Unit Off and then On again. Then try restarting the operating software.
L83: -- Could not create Config--file!
An attempt was made to store the current layout configuration onto the system defaults directory, but the operation failed. You should have full read & write access to this directory.
L84: -- Error in retrieving All Workspaces info!
This is an internal error in the Launchpad, and should never happen. If it does occur, it will be during saving of the layout configuration to file. You should then restart the Operator Station software, and try the same command once again. This error may indicate internal problems for the Launchpad program, and should be reported.
L85: -- Program <name> contains an error in the configuration--file start--string!
This is a serious error. An attempt was made to update the main configuration file from data in memory. The attempt failed because the internal information did not adhere to the syntax for this type of information. You should exit and restart the system to avoid loss of operational control.
L89: -- Could not create Log--file Backup!
An attempt was made to open the logfile in the system defaults directory, but the operation failed. You should have full read & write access to this directory.
L99: -- Not able to change to Raw Data Directory <name> when generating Survey Parameters file.
852--164111 / A
127
Base version
An attempt was made to change the internal working directory to the one used for raw data ($RAWDATAHOME), but the operation failed. Please verify that you have full read, write & execute access to this directory.
L120: -- The main configuration file <filename> was not found. Since this is a vital file for the system, the Launchpad will terminate when you select the OK button...
This file contains the overall configuration of the operator station software. The system cant operate without this file. The file was copied to the system directory during installation, and may have been accidentally removed.
L121: -- Error(s) found in the Launchpad Configuration File! When you select the OK button, the file will be deleted and this program will terminate. When restarting the system, the Factory Default Configuration File will be installed.
The Launchpad program uses a text- file to define which programs are included in the system. Quite a few bits of information are stored here, using a fixed syntax. This error occurs because the line for this program does not adhere to the syntax. An erroneous modification may have been done using a text editor. A new default version of the file will automatically be installed when restarting the system.
L137: -- A survey name must be provided before this program can start!
Fill in or select a survey name to continue!

L140: -- Illegal character(s) in the Survey Name!
The characters (> or <) are illegal as part of all file- names, survey- names and operator names. Space ( ) will be substituted with _.
L141: -- Illegal character(s) in the Operator Name!
The characters (> or <) are illegal as part of all file- names, survey- names and operator names. Space ( ) will be substituted with _.
L144: -- Program <name> (possibly specified by the environment symbol <symbol name> in the start--up script) was not found in the Network Configuration File. File: DPC.addresses.<hostname> The system cannot work until the problem is fixed, and will terminate when you select the OK button.
The specified file contains network addresses and port no.s for all programs attached to the system. The error occurs when the program listed in the error message does not have an appropriate entry in the file.
128
852--164111 / A
Troubleshooting
L145: -- Error opening Network Configuration File! File: DPC.addresses.<hostname> The system cannot work until the problem is fixed, and will terminate when you select the OK button.
The specified file contains network addresses and port no.s for all programs attached to the system. The error occurs when your program tries to access this file, but is denied access. Several possible reasons: 1. The file does not exist. Removed? Wrong Name? 2. You have no file system access.
L146: -- Error in connecting to socket given by <entry name> in the file: DPC.addresses.<hostname>. The system cannot work until the problem is fixed, and will terminate when you select the OK button.
All programs in this system have an entry in the specified file. The most likely reason for this problem is that this entry is in use by a process (program) running on the system now. If you cannot find and terminate such a process, then try logging out and logging on before restarting the system.
L147: -- The following environment variables are undefined: <variable list>
Part of the system uses external definition of various elements used within the programs. One such type of external definition is Environment Variables. One or more of these are undefined, leaving the system without all information needed to function properly. The environment variables should be defined as part of the installation process, and these error points to either an error in the installation, or manual interference in the files defining these variables.
L149: -- Active Pos. Sys.: No Input...
The system does not receive any input from the positioning system defined as Active. This could be due to the wrong system being selected as Active. You should also check input port parameters in the setup program, and finally, check that the cabling is OK and that the positioning system unit generates the correct datagrams.
L150: -- Heading Sensor: No Input...
852--164111 / A
129
Base version
The system does not receive any input from the system generating the Heading. This could be due to the wrong system being selected for Active Heading. You should also check input port parameters in the setup program, and finally, check that the cabling is OK and that the unit from which heading is used, generates the correct datagrams.
L151: -- Attitude Sensor: No Input...
The system does not receive any input from the attitude sensor. You should check input port parameters in the setup program, and that the cabling is OK. Also check that the attitude sensor generates the correct datagrams.
L163: -- Quit Signal Received! System will shut down when you select the OK button!
The system uses built- in mechanisms to handle signals (interrupts) originating both internally and externally. The type of signal is described in the message. All, except the external Terminate Signal, is caused by errors in the program.
L164: -- Floating Point Exeption! System will shut down when you select the OK button!
L165: -- Bus Error! System will shut down when you select the OK button!
L166: -- Segmentation Violation! System will shut down when you select the OK button!
L167: -- Terminate Signal Received! System will shut down when you select the OK button!
The system uses built- in mechanisms to handle signals (interrupts) originating both internally and externally. The type of signal is described in the message. All except the external Terminate Signal, is caused by errors in the program.
130
852--164111 / A
Troubleshooting
L168: -- Illegal Instruction Signal Received! System will shut down when you select the OK button!
The system uses built- in mechanisms to handle signals (interrupts) originating both internally and externally. The type of signal is described in the message. All, except the external Terminate Signal is caused by errors in the program.
L169: -- SIGNAL <signal no.> received! System will shut down when you select the OK button!
L172: -- The following Programs are still running, and must be terminated before continuing:
The operating software uses several programs in an integrated system. Each running program is represented internally as a process. It has been observed, mostly after a crash, that these processes may continue to be active when they should not have been. The system detects these processes when it is restarted, and will, on users confirmation, issue termination commands before the system continues initialisation. But on rare occasions, the termination signal sent to these processes fails, and manual intervention is required as instructed in the error message.
L173: -- The following Programs could not be terminated:
The operating software uses several programs in an integrated system. Each running program is represented internally as a process. It has been observed, mostly after a crash, that these processes continue to be active when they should not have been. The system detects these processes when it is restarted, and will, on user confirmation, issue termination commands before the system continues initialisation. But on rare occasions, the termination signal sent to these processes fails, and manual intervention is required as instructed in the error message.
L176: -- The following Program(s) should always run, but is still NOT running:
852--164111 / A
131
Base version
All programs started and supervised by the Launchpad establishes a communication link with the system when they are launched. The listed program(s) did not succeed in establishing this link. It could be that the program (s) crashed before the linkup was attempted. In that case, the program(s) has no possibility to communicate with the rest of the system. You may try to start the system manually in a window, to see if you can find any useful messages written in the window. These programs are so called system programs, and it will be impossible to run the system when they are not running as intended.
L177: -- Could not read Raw Data directory for survey <name>.
You do not have the correct access to the specified directory. Correct ownership of directories and files are defined when the system is installed, so this problem could be the result of a manual operation in the file system. Please verify that you have read, write & execute access to the storage directories for raw data ($RAWDATAHOME).
L178: -- Not able to change to Survey Directory <name> when fetching Line Statistics file!
The system could not perform an internal change of directory to the specified directory due to error in directory access. You should have read, write & execute access to all directories and files in the data storage locations. Please verify and correct.
L179: -- Not able to change to Home Directory when fetching Line Statistics file!
The system could not perform an internal change of directory back to your login directory due to error in directory access. You should have read, write & execute access to all directories and files in the data storage locations. Please verify and correct.
L181: -- Not able to copy the file <filename> to $HOME/<filename>. Program terminates when you select the OK button!
This is the file setting up the configuration of the status filed in the Launchpad. An attempt was made to copy this file from the system defaults directory, but failed. You should have read & write access to all files in the system directory and to the directory itself. Please verify and correct.
L182: -- Could not open Operators File!
Open a terminal window, and go to the $HOME/.eso_system directory. Verify that you have both Read and Write access to the file esoSetup.operators.
L183: -- Not able to copy the Status Config file to <directory name>. Using default values...
132
852--164111 / A
Troubleshooting
This is the file setting up the configuration of the status fields in the Launchpad. An attempt was made to copy the file from the system defaults directory, but failed. You should have read & write access to all files in the system directory and to the directory itself. Please verify and correct.
L184: -- Status Config file not found. Using default values...
This is the file setting up the configuration of the status fields in the Launchpad. It was not located in any of the predefined locations. This is an error by itself - but the system uses a default setup, and will be operable. If you define a new status setup, remember to save the setup for later use.
L186: -- Could not init log--file!
It was not possible to create the file due to error in permissions. You should have read & write access to all files in the system directory and to the directory itself. Please verify and correct.
L187: -- Could not open log--file for append!
It was not possible to open the file for append due to error in file access. You should have read & write access to all files in the system directory. Please verify and correct.
L189: -- Line Statistics File could not be opened! Survey: <survey name> File: <line name>.linestat
The line statistics file for the specified line exists, but it could not be opened due to error in file access. You should have read, write & execute access to all files in the data storage directories. Please verify and correct.
L190: -- Statistics File for Survey <survey name>, line <line name> is empty!
The line statistics file for the specified line exists, but it was empty. It is difficult to state the reason for this, because all lines, no matter how small, should have something in this type of file. The file should be removed.
L193: -- Raw Data Parameters File for Survey <survey name> could not be opened!
The line parameters file for the specified line exists, but it could not be opened due to error in file access. You should have read, write and execute access to all data storage files and directories. Please verify and correct.
852--164111 / A
133
Base version
L194: -- Survey Parameters File for Survey <survey name>, line <line name> is empty!
The line parameters file for the specified line exists, but it was empty. It is difficult to state the reason for this, because all lines, no matter how small, should have something in this type of file. The file should be removed.
L198: -- Not able to change to Survey Directory <directory name> when fetching Line Statistics file!
There can be several reasons for this error, the most probable is that you dont have the correct access to the specified survey directory. Please verify that you have read, write & execute access to all directories in the $PROCHOME location. $PROCHOME is an environment variable defining the top location of your storage area for processed data (not raw data).
L209: -- You do not have WRITE access to file <name>.
You do not have the correct access to the specified file. Correct ownership of directories and files are defined when the system is installed, so this problem could be the result of a manual operation in the file system. Please verify that you have read, write & execute access to the shared system directory ($SHAREDHOME) and all files and subdirectories.
L212: -- Operation cancelled! Echo Sounder not ready!
The system was interrupted while performing a Power Up test. One of the main criteria for initiating the system is that the Power Up test is completed without error. When this test is cancelled, the system is defined to be inoperable. It will remain so until the test is completed successfully.
L222: -- Line Statistics File not found. Survey: <survey name> File: <line name>.linestat
The specified Line Statistics File does not exist. When terminating logging to a line, such a file is produced automatically. This error indicates that the file system has been manually modified.
L228: -- The file <filename> is not found on $HOME/<name> directory, or on $NEPTUNEHOME/defaults directory. Since this is a vital file for the system, the Launchpad will terminate when you select the OK button...
134
852--164111 / A
Troubleshooting
The main configuration file is not located in any of the predefined locations. The system cannot be operated without this file. You should check if you have any backups of the system directory - one is made during every upgrade / reinstall of the system. If that fails, reinstall the system.
L229: -- The file <filename> is not found on $HOME/<name> directory, or on $NEPTUNEHOME/defaults directory. Using default set--up...
The main configuration file is not located in any of the predefined locations. The system cannot be operated without this file. You should check if you have any backups of the system directory - one is made during every upgrade / reinstall of the system. If that fails, reinstall the system.
L231: -- The file <filename> is not found on $HOME/<name> directory, or on $NEPTUNEHOME/defaults directory.
The specified file is not located in any of the predefined locations. The system cannot be operated without this file. You should check if you have any backups of the system directory - there is made one during every upgrade / reinstall of the system. If that fails, reinstall the system.
L232: -- Not able to remove the file <file name>. Check access and owner of the file. Program terminates when you select the OK button.
You do not have the correct access to the specified file. Correct ownership of directories and files are defined when the system is installed, so this problem could be the result of a manual operation in the file system. Please verify that you have read, write & execute access to the system directory and all files in this directory ($HOME/.eso_system).
L233: -- Unable to open Table Of Contents!
You do not have the correct access to the selected file. Correct ownership of directories and files are defined when the system is installed, so this problem could be the result of a manual operation in the file system. Please verify that you have read, write & execute access to the system directory and all files in this directory ($HOME/.eso_system).
L234: -- Unable to open temporary copy of the log--file!
It was not possible to open the file, due to an error in file access. You should have read & write access to all files in the system directory ($HOME/.eso_system). Please verify and correct.
L235: -- Cannot allocate enough memory for viewing the log--file. You should reset the file using the File-->Reset Log--file option.
852--164111 / A
135
Base version
The logfile was too big for the available memory resources. If it is important to view the logfile, you could try terminating as many of the programs as possible before retrying. If the problem persists, you should reset the logfile. When resetting, it is possible to take a backup copy of the logfile.
L297: -- Raw Data Parameters File for Survey <survey name> Line <line name> could not be opened!
The parameter file for the specified survey exists, but it could not be opened due to error in file access. You should have read, write and execute access to all data storage files and directories. Please verify and correct. Due to the sequence of events producing this file, this error is not likely to occur.
L298: -- Survey Parameters File for Survey <name> does not exist!
The survey parameter file is based on the parameters for each line, and presents information regarding changes in line parameter setup. For some reason, this file could not be produced. It may be, that there are no lines in the survey, or that the logged lines are corrupted.
L299: -- Raw Data Parameters File for Survey <survey name> Line <line name> does not exist!
The file contains the parameter setup being used when logging the line. For some reason, this file could not be produced. It may be that the logged line is corrupted.
L300: -- Environment variable for Network Configuration File not defined!
Some of the information required to have the system running properly, is set outside of the actual programs, using environment variables. The specified variable is not defined, and probably means an installation error, or manual modification in the definition of variables.
L301: -- Could not open Network Configuration File! File: <filename>
It was not possible to open the file due to error in file access. You should have read & write access to all files in the system directory. Please verify and correct.
L302: -- Unable to open Serial Datagram Set--up--file
It was not possible to open the file due to error in file access. You should have read & write access to all files in the system directory. Please verify and correct.
L303: -- Unable to open Datagram Set--up--file! File: <filename>
136
852--164111 / A
Troubleshooting
This file contains the datagrams available for subscription. It will not be possible to use the subscription facility without this file. You should have read & write access to all files in the system directory. Please verify and correct.
L304: -- Format error on input from Datagram Set--up--file! File: <filename>
Datagrams available for user- defined distribution are defined using a fixed format. One or more of the entries in this file does not fit this format. The safest way to fix the problem is to remove the file, and restart the system. The file will then be copied to the system directory, using the default version supplied with the installation.
L318: -- Illegal format on IP address! Format: ddd.ddd.ddd.ddd, where d is a digit. Leading zeros may be omitted.
The networking addresses used by the system must follow the specified syntax. Normally, if you have subscribers running on the same computer as the operating software, you should use the IP address of this computer.
L334: -- PPS not received!
The system does not receive any input from the system generating the 1PPS. This could be due to the wrong system being selected for 1PPS. You should also check input port parameters in the setup program, and finally, check that the cabling is OK and that the unit from which heading is used, generates the correct datagrams.
L337: -- Depth/Height Sensor: No Input...
The system is supposed to receive sensor input, but does not receive any. Verify sensor connections, setup and power.
L364: -- The system is currently configured NOT to launch the Survey Display automatically. Changing this mode requires changing the configuration file...
Some installations have their own Survey Control software. The message indicates that the current configuration of the system has disabled this particular feature. Please refer to the documentation for information on how to enable this software.
L400: -- Could not open print tmp--file.
852--164111 / A
137
Base version
You do not have the correct access to a work- file in your own home directory. Correct ownership of directories and files are defined when the system is installed, so this problem could be the result of a manual operation in the file system. Please verify that you have read, write & execute access to your login directory and the files in this directory.
L401: -- Error in Launchpad Message Server Initialize!
Some system resources could not be allocated, because some other program is holding these resources. Check if any of the programs started from a previous session of the system are still running. If so, terminate these programs. If you do not know how to do this, it will in most cases be sufficient to log out and then back in. This will terminate any running programs and free up resources. Then restart the operator station software...
Warnings
L45: -- Error reading input datagram...
Reading from the communication input socket failed. This is a low- level error, and should not occur if the system managed to start properly. If the error persist, try terminating the system and restart the software again.
L52: -- Sound Speed At Transducer deviates more than X m/s from the corresponding value defined by the current Sound Speed Profile!
The sound speed at transducer depth received from the probe exceeded the selected alarm offset 5 times in a row. You should verify that you are using the correct sound speed profile, and also verify the size of the alarm offset.
L54: -- Current Center Depth exceeds original maximum depth from the current Sound Speed Profile! Center Beam Depth = <depth> Profile Max. Depth = <depth>.
The original profile had a maximum depth before the automatic profile extension extended the profile down to 12000 m. The depth you now are registering exceeds this depth. This could mean that your original profile isnt deep enough for this area.
L355: -- Unknown NMEA Telegram received...
The datagram received were not uniquely recognised. It seems to be a NMEA datagram, but one not supported by the system. The datagram may also contain format errors. Please refer to separate documentation on datagram definitions.
Errors
L64: -- Connection timeout -- Logging switched Off!
138
852--164111 / A
Troubleshooting
The Operator Station stopped receiving broadcast datagrams from the Processing Unit. The continuing flow of broadcasts datagrams tells the rest of the system that the PU is still alive. To prevent gaps in the line and possible data corruption, logging was stopped. Possible reasons for loss of contact: .Processing Unit is not Powered On .Network Cable Problems .Configuration Errors .Processing Unit Hardware / Software malfunction
L65: -- Connection timeout -- Pinging switched Off!
The Operator Station stopped receiving broadcast datagrams from the Processing Unit. The continuing flow of broadcast datagrams tells the rest of the system that the PU is still alive. The system status was set to No Pinging. Possible reasons for loss of contact: .Processing Unit is not Powered On .Network Cable Problems .Configuration Errors .Processing Unit Hardware / Software malfunction
L66: -- Timeout in Processing Unit <--> Launchpad Connection!
The Operator Station stopped receiving broadcasts from the Processing Unit. The continuing flow of broadcasts tells the rest of the system that the PU is still alive. Possible reasons for loss of contact: .Processing Unit is not Powered On .Network Cable Problems .Configuration Errors .Processing Unit Hardware / Software malfunction
L122: -- There are too many entries in setup--file! Max = 18.
The configuration file contains all programs included in the integrated system, but may also contain programs added by the user. These programs may be started from the Launchpad, but are not supervised as the other programs. The total number of entries has exceeded the maximum limit, probably due to manual modifications of this configuration file. To restore the default file supplied by the system, remove the $HOME/.eso_system/esoEmX_config file, and restart the system.
L123: -- Not able to obtain the icon for <this utility>!
852--164111 / A
139
Base version
Each of the programs integrated into the system has a button in the rightmost part of the Launchpad, and each of these buttons should have a symbol / icon for identification purposes. The symbol name specified in the external configuration file was not found, indicating an error in the file, or a mismatch between the configuration file and the file containing the icon descriptions. If this error occurs, a capital X is drawn instead of the proper icon.
L124: -- Not able to obtain default icon!
Each of the programs integrated into the system has a button in the rightmost part of the Launchpad, and each of these buttons should have a symbol / icon for identification purposes. The symbol name specified in the external configuration file was not found, indicating an error in the file, or a mismatch between the configuration file and the file containing the icon descriptions. If this error occurs, a capital X is drawn instead of the proper icon. This message indicates that the X icon was not found.
L142: -- Environment MODULES_ICON_FILE not found, or empty! Fix and restart!
The file containing the icon descriptions used by the system cannot be located, because the environment variable, giving the name of this file, was undefined. All environment variables used by the system are defined when installing the system, so this message indicates a system installation error.
L143: -- Unable to open module icon description file <name> specified in environment MODULES_ICON_FILE. Fix and restart!
The file containing the icon descriptions could not be opened. The file may be missing, or you do not have the proper file access.
L152: -- Clock: No Input...
The system does not receive any clock input from the positioning system. You should check input port parameters in the setup program, and that the cabling is OK. Also check that the positioning system generates the correct datagram.
L154: -- Logging of Survey Data to Disk was switched Off due to an error in the <name> program!
Refer to messages in the Status Display for further details.

L155: -- Logging of Raw Data to Disk was switched Off due to an error in the <name> program!
140
852--164111 / A
Troubleshooting
Refer to messages in the Status Display for further details.

L170: -- Unable to create Process List!
An attempt was made to open the process id logfile in the system directory for writing, but the operation failed. You should have full read & write access to the specified file and directory.
L171: -- Unable to open Process List!
An attempt was made to open the process id logfile in the system directory for reading, but the operation failed. You should have full read & write access to the specified file and directory.
L356: -- Format Error in Remote Control Telegram!
The datagram received was recognised as a Remote Control datagram, but the content does not adhere to the datagram syntax. Please refer to separate documentation on datagram definitions.
852--164111 / A
141
Base version
7.4
ESO messages
ESO messages
The following messages are presented by the ESO utility.
Display warnings
W22: -- No probe samples logged!
The sampling of probe values was terminated, but no values were actually received. Check probe connections and serial port setup.
W26: -- The file <name> was empty. Factory Defaults was used instead. Please verify settings and use the File --> Save command to make settings permanent.
This means that the setup- file somehow has been corrupted. (E.g. system crash, text editor). A workaround is to set all parameters in the menus as required, and recreate the setup- file using the File- >Save command. If this is followed by the File- >Read command, full functionality should be restored. Alternatively, you could exit the program remove the empty file - and then restart the program. This will enable you to install the default setup- file delivered with the system.
Display errors
W5: -- Serial Set--up--file <filename> missing. Install Default file?
The specified file is either removed or renamed. However, the default file provided will enable all functions on a system not extended with a serial port expansion card.
W9: -- No Serial input device is open! Select the Smart Probe Profile Inputs as the current serial I/O function in the Workstation I/O Interfaces menu.
The serial port specified for this function could not be opened as expected probably due to error in read/write permission, or that a non- existing device is specified in the setup- file.
W12: -- Unable to open temporary file <filename>!
The error occurs because of inaccurate read/write permissions to the system directory. This is either an installation error, or an error introduced after installation.
W17: -- Input Error. To enable new input, you must reselect the current input function.
The input format was not recognised. Reading from the serial port was disabled to avoid further input, and must be reactivated by reselecting the input function.
142
852--164111 / A
Troubleshooting
W27: -- The file <filename> is not found in the $HOME directory, or on $NEPTUNEHOME/defaults directory.
The setup- file should be present in both the indicated locations. If you at any point have done a system upgrade, you should check for backup copies in any of the system directory backups in the login directory. Backup file syntax: .eso_system<date_time>/ .esoSetup.serial. If no such files are found, search for the file on the CD- ROM containing the installation.
W28: -- Not able to copy the file <filename> to $HOME/.eso_system. Program terminates when you select the OK button.
W29: --Not able to remove the file <filename>. Check access and owner of the file. Program terminates when you select the OK button.
W30: -- Unable to open device <device--name>! You may have a permission problem.
The error occurs because of inaccurate read/write permissions to the specified serial port device. This is either an installation error, or an error introduced after installation.
W40: -- The set--up file is incomplete. Verify all parameters. Then save your configuration using the File-->Save Set--up menu option. Then read the set--up using the File-->Read Set--up to reinitiate the system!
The file could be corrupted (system crash), or modified outside the program (text editor), accidentally removing parts of the file.
W41: -- Incomplete SVP CALC profile received on the network...
When receiving from the network, AML CALC files are supposed to be received in one go, i.e. complete with both profile identifier and termination sequence. In this case, no termination sequence was found in input.
Warnings
W43: -- The device associated with this function is in active use by the following function: <function>. To use the selected function: 1. Switch OFF the other function or 2. Change device associated with one of the two functions.
852--164111 / A
143
Base version
W44: -- You must terminate any active functions before reading set--up file! W45: -- Could not open tide output file: <filename>. You may have a permission problem...
An attempt was made to open the tide file in the current survey directory, but the operation failed. You should have full read & write access to the directory and all files in the directory. Correct the directory & file access and activate the tide input function again.
W46: -- The <name> function cannot share device with the <name> function. Per definition, only the following functions may share device: <list of functions> These functions may all be active at the same time. W53: -- Serial Port input not recognised! To enable new input, you must reselect the last selected input function
The input received was not recognized. This could be due to errors in the format used for transmitted data, or, if a serial line is used, errors in setting up serial line characteristics.
W54: -- Input buffer overrun -- function disabled! To enable new input, you must reselect the currently disabled input function.
Errors
W60: -- The last command sequence to the probe failed. Repeat your latest action to retransmit sequence. If this message was issued when bringing up this window, select the Apply Settings button in the Sampling Parameters section to repeat sequence.
The probe did not recognize the last command issued. This could be caused by garbled serial line transfer. Verify your serial line settings and retry the command once again.
W61: -- No reply to last SV Plus command! Probe may be disconnected or without power... W62: Format Error in SV Plus Input!
The input from the probe was not recognized.This could be caused by garbled serial line transfer. Verify your serial line settings and retry the command once again.
144
852--164111 / A
Troubleshooting
7.5
Sound Speed Profile Editor messages

Sound Speed Profile Editor messages
The following messages are presented by the SSP Editor utility.
Warnings
E10: -- Profile contains fewer points than specified in Profile Header. Using number of points read from file!
The profile may have been edited manually, creating a mismatch between header no. of entries and actual no. of entries. The profile was automatically corrected.
E11: -- Profile contains more points than specified in Profile Header. Using number of points read from file!
The profile may have been edited manually, creating a mismatch between header no. of entries and actual no. of entries. The profile was automatically corrected.
E13: -- You have no WRITE access to profile directory <directory name>.
The profile directory is created with full Read and Write access when installing the system. This problem may be caused by manual modifications of the file system. Set the correct directory access before retransmitting.
E33: -- The file <filename> containing the selected Sound Profile was not found.
Someone has deleted the selected Sound Velocity Profile from the disk after the list was created! The list was produced using only actual and existing profiles. If you have no idea how this could have happened, get in touch with the System Administrator.
E38: -- You have no WRITE access to the selected Sound Velocity Profile directory!
The File Selection Box enables traversal of the file system directory structure, which means that you may select any directory as a storage area for the SV Profile - even those you do not have WRITE access to. If you are denied access to a directory that you would like to have access to, check the System Manager to see if this is permissible.
E42: -- You have no DELETE access to the selected Sound Velocity Profile!
The profile directory is created with full Read and Write access when installing the system. This problem may be caused by manual modification of the file system. Set the correct directory & file access before retrying.
E54: -- Please use the Save As... command to give the profile a name.
852--164111 / A
145
Base version
E56: -- No points in Profile...
The editable buffer is empty. Create a profile using the New Profile command in the File menu. You may also use the Copy SV Profile or the Combine SV Profiles in the Edit menu.
E60: -- Illegal Survey Format File Name: <filename>
The survey format profile name does not match the syntax, which is as follows: <line_no_yyyymmdd_hhmmss_sensor_version>.sfsvp The only way to correct this is to do a manual profile rename. Since the survey profiles are named autmatically, this is an error that should not have occurered.
E61: -- Empty file: <filename>
The file does not contain any samples, and cannot be used. It is not possible to state any reasons for this. The file should be removed from the profiles directory.
E62: -- Currently no editable profiles in work area to save!
Errors
E46: -Environment SVP_EDITOR_MODULE_NO not defined or empty! Environment SVP_EDITOR_MODULE_NAME not defined or empty! These errors results in a program that does not work properly. Fix and restart!
Most of the variable elements of the system configuration can be configured outside the programs. This is done by quite a few environment variables, which is set to an initial value when installing the system, and then fetched by the programs when needed. The environment variables listed in the error message must be set to match the initial values.
146
852--164111 / A
Troubleshooting
7.6
Ping Display messages

Ping Display messages
The following messages are presented by the Ping Display utility.
P32: -- No information received from the ESO! Ignore this message if used in stand--alone mode.
When starting up, the program tries to get some information from the ESO system. But when running in a standalone mode, it does not receive any answer. The requested information is not important in the standalone mode. If you get this message when running as part of the complete system, try restarting the operator software.
852--164111 / A
147
Base version
Hardware messages
The following messages are reported by the software monitoring the hardware circuitry in the Transceiver Unit. 400: 402: Illegal parameter value in command from PU to SPTX High voltage power supply too low. This is a failure reported by the SPRX. Action: Run the BIST program for more details. 403: High Voltage power supply too high. This is a failure reported by the SPRX. Action: Run the BIST program for more details. 404: Low Voltage power supply failure. This is a failure reported by the SPRX. Action: Run the BIST program for more details. 406: DC offset problem on a number of receiver channels. This is a warning reported by the SPRX. Action: Run the RX_CHANNELS BIST program for more details. 420: Illegal parameter value in command from PU. This is a warning reported by the BSP. Action: Run BSP BIST. If this does not help, restart the echo sounder. 421: Communication problem between SPRX and BSP. This is a warning reported by the BSP. Action: Run SPRX and link SPRX- BSP BIST. 422: Internal synchronisation problem on BSP. This is a warning reported by the BSP. Action: Run BSP BIST. 460: No valid heading input. This is a failure reported by the PU. Action: Check heading input from sensor and installation parameters on the Operator Station. 461: No valid attitude input. This is a warning reported by the PU. Action: Check heading input from sensor and installation parameters on the Operator Station. 462: No valid position input. This is a failure reported by the PU.
148
852--164111 / A
Troubleshooting
Action: Check heading input from sensor and installation parameters on the Operator Station. 463: No valid 1 PPS input. This is a failure reported by the PU. Action: Check heading input from sensor and installation parameters on the Operator Station. 464: Error in communication with TRU. This is a failure reported by the PU. Action: Check SPRX, LV power BIST. Check power in TRU RX. 465: Error in communication with BSP. This is a failure reported by the PU. Action: 466: Illegal parameter value in command from OS to PU. This is a warning reported by the PU. Action: 467: No external trigger received. This is a warning reported by the PU. Action: Check heading input from sensor and installation parameters on the Operator Station.
852--164111 / A
149
Base version
7.7
CPU CMOS SETUP

Setup for SSC-486H
To change the setup you must mount a standard VGA card and connect a VGA monitor and a keyboard. This setup is based on BIOS:KU26C- 03B. Hit DEL key after power on and confirm/change to following settings in CMOS:
Advanced setup
Typematic rate (char/sec) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 System keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Absent Primary display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Absent Mouse support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disable Above 1MB memory test . . . . . . . . . . . . . . . . . . . . . . . . . . Enable Memory test tick sound . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enable Parity error check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enable Hit DEL message display . . . . . . . . . . . . . . . . . . . . . . . . Enable Extended Bios RAM area . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0:300 Wait for F1 if any error . . . . . . . . . . . . . . . . . . . . . . . . . . Enable System boot up numlock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . On Numeric processor test . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enable Wietek processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Absent Floppy drive seek at boot . . . . . . . . . . . . . . . . . . . . . . . . . . Disable System boot up sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:,C: System boot up CPU speed . . . . . . . . . . . . . . . . . . . . . . . . . . High External cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enable Internal cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enable Internal cache WB or WT . . . . . . . . . . . . . . . . . . . . . . . . WR- thru Turbo switch function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enable Password checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setup Video shadow, C000, 16k . . . . . . . . . . . . . . . . . . . . . . . . . . Enable Video shadow, C400, 16k . . . . . . . . . . . . . . . . . . . . . . . . . . Enable Shadow, C800, 16k . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disable Shadow, CC00, 16k . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disable Shadow, D000, 16k . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disable Shadow, D400, 16k . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disable Shadow, D800, 16k . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disable
150
852--164111 / A
Troubleshooting
Shadow, DC00, 16k . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disable Shadow, E000, 64k . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disable IDE multi- sector transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . Auto Primary IDE 32- bit transfer . . . . . . . . . . . . . . . . . . . . . . . . Disable Primary IDE block mode . . . . . . . . . . . . . . . . . . . . . . . . . . Master Primary IDE LBA mode . . . . . . . . . . . . . . . . . . . . . . . . . . Mas/Sla Secondary IDE present . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . None Secondary IDE 32 bit transfer . . . . . . . . . . . . . . . . . . . . . . . Disable Secondary IDE Block mode . . . . . . . . . . . . . . . . . . . . . . . . Disable Secondary IDE LBA mode . . . . . . . . . . . . . . . . . . . . . . . . Mas/sla
Peripheral setup
Onboard FDC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enable Onboard IDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enb- pri Serial port 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3F8h Serial port 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2F8h Parallel port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378h Parallel port mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Normal Parallel extended mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ECP
Chipset setup
Auto config function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enable Cache read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3- 2- 2- 2 Cache write . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 ws DRAM wait . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 ws DRAM page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fast Keyboard clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.5 MHz AT clock select . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCLK/4 Local ready . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Delay 1T CPU ADS# delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . No delay Alt bit in tag SRAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7+1 bit Signal LDEV# sample time . . . . . . . . . . . . . . . . . . . . . . . . . . in T3 HW DRAM parity check . . . . . . . . . . . . . . . . . . . . . . . . . . . Disable ISA bus refresh disable bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fast DRAM refresh method . . . . . . . . . . . . . . . . . . . . . . . . . . . Ras only Devider for refresh . . . . . . . . . . . . . . . . . . . . . . . . . Reserved (1/1) Video ROM cache C000, 16k . . . . . . . . . . . . . . . . . . . . . . . . Disable
852--164111 / A
151
Base version
Video ROM cache C400, 16k . . . . . . . . . . . . . . . . . . . . . . . . Disable Adapter ROM cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disable System memory remap or not . . . . . . . . . . . . . . . . . . . . . . Enable LOWA20# select . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chipset RC reset select . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chipset IO recovery time select . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 BCLK Hold CPU percentage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disable Software flush 80486 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disable Enable force read miss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disable
Setup for SSC-5x86H

This setup is based on Award Bios v4.51G. ICP version KU35- LSV3.2. Hit DEL key after poweron and confirm/change to following settings in CMOS:
Standard setup
Primary Master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . None Primary Slave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . None Drive A: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . None Drive B: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . None Video . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EGA/VGA Halt on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . All, but keyboard
BIOS features setup

Virus Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabled CPU internal cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabled External cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabled Quick power on self test . . . . . . . . . . . . . . . . . . . . . . . . . . Disabled Boot sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A,C Swap floppy drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabled Boot up floppy seek . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabled Boot up Numlock status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . On Boot up system speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . High Gate A20 option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fast Memory parity check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabled Typematic rate setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabled Typematic rate (chars/sec) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Typematic delay (msec) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
152
852--164111 / A
Troubleshooting
Security option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setup PS/2 mouse functional ctrl . . . . . . . . . . . . . . . . . . . . . . . . Disabled PCI/VGA Palette snoop . . . . . . . . . . . . . . . . . . . . . . . . . . Disabled OS selector for DRAM>64Mb . . . . . . . . . . . . . . . . . . . . . . Non OS2 Video bios shadow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabled C8000- CFFFF Shadow . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabled D0000- D7FFF Shadow . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabled D8000- DFFF Shadow . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabled
Chipset features
Auto configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabled AT- BUS CLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CLK/4 DRAM read timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Normal DRAM write timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Normal SRAM read timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3- 1- 1- 1 SRAM write timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0 Wait Hidden refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabled Memory hole (15M- 16M) . . . . . . . . . . . . . . . . . . . . . . . . . Disabled ISA I/O recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabled Fast back to back . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabled
Power managment setup

Power Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disable PM control by APM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Yes Video Off Option . . . . . . . . . . . . . . . . . . . . . . . Susp/stby - > OFF Video Off Method . . . . . . . . . . . . . . . . . . . . . . . V/H Sync+Blank MODEM use IRQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 PM TIMERS HDD power down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabled Doze mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabled Standby mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabled Suspend mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabled PM EVENTS VGA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Off FDD HDD (3FxH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . On (1FXH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . On LPT & COM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LPT/COM
852--164111 / A
153
Base version
NMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OFF IRQ3 IRQ4 IRQ5 IRQ6 IRQ7 IRQ8 IRQ9 (COM2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . On (COM1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . On (LPT2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . On Floppy disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . On LPT1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . On RTC Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Off IRQ2 redir . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . On
IRQ10 Reserved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Off IRQ11 Reserved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Off IRQ12 PS/2 Mouse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . On IRQ13 Coprocessor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Off IRQ14 Hard disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . On IRQ15 Reserved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Off
Integrated peripherals
On- chip Local Bus IDE . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabled Onboard FDC control . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabled Onboard UART1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3F8/IRQ4 Onboard UART2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2F8/IRQ3 Onboard paralell port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378 Parallel port mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Normal
154
852--164111 / A
8
8.1
REPLACEMENT PROCEDURES
Introduction
Overview
This chapter presents the basic procedures for disassembly and reassembly of the replaceable parts in the EM 120 sonar system.
852--164111 / A
155
Base version
Tools required
A standard tool set is required to perform the removal and replacement of the modules. This tool set should contain the following tools: Cabinet key Standard screwdrivers in different widths and lengths Allen keys in metric sizes Philips screwdrivers in different sizes Pozidrive screwdrivers in different sizes Flat nosed pliers Lap jointed pliers Wire cutters Soldering iron Open ended and ring spanners in metric sizes Adjustable spanners Socket set The following expendables are recommended: Solder Wire straps in different sizes
156
852--164111 / A
8.2
Transceiver Unit procedures

Overview
The Line Replaceable Units (LRUs) in the EM 120 Transceiver Unit are: Processing rack: - 4- Ports Serial Line Board - Beamformer & Signal Processor 1/2 (BSP1 and BSP2) - Ethernet Adapter - ROM bank - Control Processor Board (486) - Power supply X2 (HN5- 9/OVP- A and OLD- 12/15BB) - Fan - Motherboard Receiver rack: - Transmitter/Receiver board (x4) (TRB) - Low Voltage Power Unit (LVPU) - High Voltage Power Supply (HV2PS2) - Signal Processor Board RX (SPRX) - Capacitor bank Transmitter rack: - 64- Channel Transmitter Board (TX64) - Signal Processor Board TX (SPTX) Other devices: - AC mains fuse and filters - Fuses - Fan drawers The replacement procedures for these parts are described in the following disassembly & reassembly procedures.

Introduction
The Transceiver Unit holds three wired racks. All the wired racks hold plug- in circuit boards and modules. The replacement of these modules is described in this procedure. The system must be switched off prior to disassembly. Access is gained to the wired racks by opening the front door of the Transceiver Unit. To open the front door, use the special tool for the cabinet doors. Before removing any modules, be sure that voltmeter on front of the High Voltage Supply shows zero (0) voltage.
852--164111 / A
157
Base version
Processing rack The following modules are accessible in the Processing rack: 4- Ports Serial Line Board Beamformer & Signal Processor 1/2 (BSP1 and BSP2) Ethernet Adapter ROM bank Control Processor Board (486) Power supply X2 (HN5- 9/OVP- A and OLD- 12/15BB) Fan Motherboard
The circuit boards and modules in the Processing rack are shown on page 38.
Receiver rack The following modules are accessible in the Receiver rack: Transmitter/Receiver board (x4) (TRB) Low Voltage Power Unit (LVPU) High Voltage Power Supply (HV2PS2) Signal Processor Board RX (SPRX) Capacitor bank
The circuit boards and modules in the Receiver rack are shown on page 40.
Transmitter rack The following modules are accessible in the Transmitter rack: 64- Channel Transmitter Board (TX64) Signal Processor Board TX (SPTX) Note ! All the above listed units are plug- in modules.
The circuit boards and modules in the Transmitter rack are shown on page 41.
Disassembly procedure
1 2 3 Remove the front mounted cables from the applicable circuit boards. Release the thumbscrews if required. Pull the board/unit carefully out.
Refer to page 163.
Software replacement
Replacement of all the circuit boards

In some cases, i might be necessary to replace all the circuit boards in the Transceiver Unit. The following procedure is then suggested:
158
852--164111 / A
1 2
Open the front door of the Transceiver Unit as previously described. Switch off the circuit breaker on the right side of the Processor rack, and pull out the contact on the Low Voltage Power Unit. Wait until voltmeter on the High Voltage Supply shows zero volts. Unplug the front mounted flat ribbon cable connectors on the Transmitter/Receiver boards and 64- Channel Transmitter (TX64) circuit boards. Use care; do not pull by the cables ! Remove the circuit boards and modules carefully. Insert new circuit boards and modules in reverse order. Mount the front mounted flat ribbon cable connectors and the front covers. Check that the circuit boards and modules have been installed in their correct locations! Refer to the applicable pictures and drawings.
4 5
Fan drawers
Refer to page 165.
Heater element
Introduction
A heater element is mounted on the right wall in the bottom wired rack. The heater is included to ensure the temperature inside the cabinet remains stable when the system is switched off, thus preventing condensation forming inside the cabinet. The heater is a commercial item.
1 2 3 Caution ! Open the front door of the Transceiver Unit. Switch off the front mounted circuit breaker located on the right side of the Processor rack Open up the middle section of the cabinet
Do not open the middle cabinet while in rough sea. The cabinet is heavy, and sudden movements may cause damage or injury to personnel. 4 5 6 Note down the location of the wires prior to removal ! Locate the heater. Follow the heater cables to the terminal block, and disconnect the wires. Loosen the rail support holding the heater in place, and allow the heater to slide out (forward).
852--164111 / A
159
Base version
Reassembly procedure
The new heater is replaced reversing the above procedure.

Introduction
The power supply is located in the Receiver Rack, between the Low Voltage Power Supply and the Capacitor bank.
1 2 Open the front door of the Transceiver Unit. Switch off the circuit breaker on the right side of the Processor rack, and pull out the contact on the Low Voltage Power Unit.
Caution !
Do not pull out the unit before the voltmeter shows zero (0) voltage. 3 Unbolt the unit. It is mounted with four captive- bolts so they cannot fall out. The nuts and spring washers are accessible.
The new power supply is replaced by reversing the above procedure.
AC mains circuit breaker

Introduction
The circuit breaker is located on the right side of the Processor rack.
1 2 Switch off the AC input to the cabinet. Open the front door of the Transceiver Unit. Open up the middle part of the cabinet and swing the middle section towards the left.
Caution !
Do not open the middle cabinet while in rough sea. The cabinet is heavy, and sudden movements may cause damage or injury to personnel. Make sure that the input AC voltage is switched off prior to commencing the disassembly. 3 Unbolt the 4 screws on each side of the Processor rack to loosen the entire rack. Push the rack carefully backwards until the screws that hold the circuit breaker are available with a screwdriver. It might be necessary to loosen some straps that holds the cables.
Caution !
160
852--164111 / A
4 5 6 7
Note down the location of the wires prior to removal ! Disconnect the wires on the faulty circuit breaker. Unbolt the screws that holds the circuit breaker Remove the circuit breaker carefully.
Replace by reversing the above procedure.
AC mains filter
Introduction
The mains AC filter is located on the bottom plate of the Transceiver Unit.
1 2 Switch off the AC input to the cabinet. Open the front door of the Transceiver Unit. Open up the middle part of the cabinet and swing the middle section towards the left.
Caution !
Do not open the middle cabinet while in rough sea. The cabinet is heavy, and sudden movements may cause damage or injury to personnel. Make sure that the input AC voltage is switched off prior to commencing the disassembly. 3 4 5 Note down the location of the wires prior to removal ! Disconnect the wires on the faulty AC filter. Unbolt the 2 screws that holds the AC filter from the undeside of the bottom plate and remove the filter.
Caution !
Replace by reversing the above procedure.
Fuse replacement
Introduction
The Transceiver Unit holds several power supplies. Two of these are equipped with primary fuses. Low Voltage Power Unit High Voltage Power Supply
The fuses on these power supplies are front mounted. No disassembly is required.
852--164111 / A
161
Base version
Replace with the same type of fuse.
TX64 Fuse replacement

Introduction
The 64- Channel Transmitter Board (TX64) is equipped with eight fuses. These are located side by side on the circuit board. Each fuse protects a group of eight output channels. - Physical dimensions - Rating 5 x 20 mm 4A
If any of the fuses blow, the appropriate group of transmitters will fail.
1 2 3 4 Open the front door of the Transceiver Unit. Remove the flat ribbon cables on the TX64 boards. Pull out the board. Replace the fuse(s).
Reverse the above procedure.
162
852--164111 / A
Software replacement
Overview
Normally the spare boards are fully equiped with software. If this is not the case, follow the instructions below. Several of the circuit boards in the wired racks hold software on onboard PROMs and PALs. These devices must be moved from a faulty circuit board to a new spare. This is a delicate job, and the circuit board and the memory devices must be handled with great care. The following precautions must be taken: The software replacement operation must be performed on a stable workbench or table. The table must be covered with an antistatic mat connected to the ships ground The maintenance technician or engineer must wear a grounding bracelet, firmly connected to the ships ground. All circuit boards must be stored in antistatic bags while not in use. Each software device is identified with a white label. This label holds the following information: Circuit board Device number Software version Date Checksum (in hexadecimal) E.g. SPB E.g. U15 E.g. V1.1 E.g. 90.09.15 E.g. 05A3
Disassembly
1 2 Identify the device to be removed and write down the location of pin 1. Use a small screwdriver or a special extraction tool and remove the device carefully from its socket on the source circuit board. Enure that the device is lifted as vertically as possible to prevent damage to the pins.
3 Caution !
Once the device has been removed, handle it with care !
Insertion
1 Identify the socket where the device is to be located, place the device carefully into the socket, and ensure that it is orientated correctly. Press the device gently but firmly into the socket using even pressure over the whole surface area.
852--164111 / A
163
Base version
After insertion, check that all the pins are properly inserted into the socket, and that no pins are bent.
Resassembly procedure
Note ! Several circuit boards contain software mounted in PROMs, or other hardware devices. In the event of board replacement, ensure that the correct firmware devices are mounted and that correct links are fitted. 1 2 3 Locate the new module in the rack ensuring that module is correctly positioned in the guide rails. Slide the board gently into the rack ensuring that the rear connectors mate correctly. Secure the thumbscrews. Reconnect the flat ribbon cables (if any) onto the front of the board. Ensure that no pins are bent or broken, and that the plugs connect properly. Clip the locks onto the connectors to ensure the board is held securely in position. Close the cabinet door.
164
852--164111 / A
Fan drawers
Introduction
There are several fan drawers in the sonar system. There are two fans in the bottom of each rack. All are identical. There are also two more fans located in the Processing Rack beneath the circuit breaker. The disassembly- and reassembly procedure of those two fans are more complicated, therefore it is explained separately from the other six fan drawers. The sonar system must be switched off. Access is gained to the wired racks by opening the front door of the Transceiver Unit.
The fan drawers located underneath the wired racks: 1 2 Gain access to the wired rack. Twist the right thumb- screw on the fan drawer anti- clockwise a few turns, and the left thumb- screw clockwise a few turns. Pull out the fan drawer. Gain access to the Processing Rack, both front and rear, by opening the front door, and the midsection. Unscrew the chassis, and pull it out from behind. The fan is attached to the chassis with screws. Unscrew the fan, and take it off.
3 1 2 3
The two fan drawers located in the Processing Rack:
The fan drawers located underneath the wired racks: 1 2 3 1 2 3 Push the drawer in. Make sure that the unit connects properly to the rear socket. Secure the unit with the thumbscrews. Close the cabinet door. Replace the fan back on the chassis. Put the chassis back into the rack. Close the midsection and front door.
The two fan drawers located in the Processing Rack:
852--164111 / A
165
Base version
9
9.1
DATAGRAM FORMATS
Introduction
The information herein is common for the EM 3000, EM 2000, EM 1002, EM 300 and EM 120 multibeam echo sounders. Some of the information may not be relevant for your specific system. Please disregard this. The formats for data input and output to and from the EM Series multibeam echo sounders are described here. The information given here is valid for the Kongsberg Simrad multibeam echo sounders introduced after 1995.
Note !
Note ! Note !
The information in this document is not valid for the EM 12, EM 100, EM 950 and EM 1000 multibeam echo sounders. In order to meet special customer requirements, Kongsberg Simrad may have to change the datagram formats described here. The formats presented in this document may therefore be altered without prior notice, although backward compatibility will be maintained as far as possible. Before software is written in accordance with this document, it is strongly recommended to contact Kongsberg Simrad to ensure that the latest version is used, and that any planned changes are taken into account.
9.2
Presentation format
The format description is according to the NMEA 0183 standard for ASCII fields, with the ASCII character(s) given as follows: x.x defines a variable length numerical field, with optionally included decimal point and sign. c- - c defines a variable length field of printable characters. x- - x defines a variable length field of numeric characters. a_ _ defines a fixed length field of alphabetical characters (for example aa= two character long field. x_ _ defines a fixed length field of numeric characters. For binary fields, the length is given in number of bytes plus U for unsigned and S for signed data.
166
852--164111 / A
Datagram formats
9.3
Input datagrams
Introduction
Only a limited number of input formats from external sensors are accepted. These are primarily in accordance with the NMEA 0183 specification, or based upon the principles of that specification.
Note !
The majority of these formats have not been defined by Kongsberg Simrad. Thus, these formats are not controlled by Kongsberg Simrad. Almost all input formats are ASCII. Serial line input on the multibeam echo sounders Processing Unit is most common, but some datagrams - which are not time critical - are interfaced on serial line(s) or Ethernet to the Operator Station.
Position
Overview
The EM Series accepts position data in the following formats: NMEA 0183 GGA GGK SIMRAD 90 With the GGA and GGK datagrams, information contained in NMEA 0183 VGST and VTG datagrams will also be accepted and used. A datagram format for Sonar Head depth is provided for the EM 3000 and the EM 2000. Note that the format is the same as that used by the Paroscientific Digiquartz pressure sensor. This format may also be used for input of for example varying datum heights or other special height information on all models. A datagram format for input of tidal height is provided. The GGA format is given below according to the NMEA 0183 version 2.30 description. Additional data at the end of the datagram is accepted to cater for users who need to log additional information than what is provided in the standard format. This is also supported with the GGK format. The total datagram length must be limited to less than 128 bytes if additional data is included. Note ! While such additional data will be logged, it is up to the user to extract the data to whatever use is required in postprocessing. Anyone using this possibility must also be aware that any future changes to the GGA or GGK format may require modifications in the datagrams and hence data decoding. The GGK format was originally defined by the US Army Corps of Engineers for their tests with kinematic GPS. Trimbles proprietary version of the format is supported. If any changes to the format are made if it becomes part of the NMEA standard, this will be implemented.
852--164111 / A
167
Base version
To preserve the inherent accuracy of the kinematic GPS data it is necessary to correct the data for vessel motion. This requires accurate timing synchronisation between the motion sensor and the GPS receiver. It is therefore imperative that: the position datagram has a constant and known time delay or the time stamp in the datagram is actually the time of the position fix, that synchronisation to the 1 PPS signal of the GPS receiver is enabled, and that the system clock has been set correctly As neither of these conditions may not be possible to achieve with a sufficient accuracy, the application of motion correction is operator selectable. Motion compensation may be applied to any position input, not only kinematic GPS. In addition to position data from the GGA or GGK datagrams, speed and course over ground from NMEA VTG datagrams may also be copied into the position output datagram. These values may be useful in filtering of the positioning during postprocessing. If a VTG datagram does not follow the GGA or GGK datagram the course and speed fields of the output datagrams will be set to their invalid values. The Standard deviation of semi- major axis of error ellipse field in a NMEA GST datagram may also be copied to the position output datagram as its Measure of position fix quality. It will then replace the use of the HDOP or DOP field in the GGA or GGK datagram respectively to derive this field. This must be enabled by the operator however, and then if the GST datagram does not follow the GGA or GGK the quality measure field of the output datagram will be set to its invalid value. As an alternative to GGA, the SIMRAD 90 format position datagram may be used. The SIMRAD 90 format is intended to be the format of choice when the positioning system is not a standalone GPS receiver supplying GGA or GGK format datagrams. The SIMRAD 90 format can in addition to global longitude latitude coordinates also be used for Northing Easting type projection coordinates (e.g. UTM). To cater for applications where the EM 2000 or EM 3000 Sonar Head is mounted on a subsea vehicle, the original SIMRAD 90 format has been expanded to allow inclusion of the depth of the vehicle in addition to its horizontal position in longitude latitude or Northing Easting coordinates. Also for EM 2000 and EM 3000 applications with separate surface and underwater positioning systems, the SIMRAD 90 format will allow the underwater position to be provided relative to the vessel, with the vessel surface position given in a separate GGA, GGK or SIMRAD 90 datagram.
168
852--164111 / A
Datagram formats
GGA Datagram
Data Description Start identifier = $ Talker identifier Sentence formatter UTC of position Latitude in degrees and minutes, plus optional decimal minutes Latitude --- N/S Longitude in degrees and minutes, plus optional decimal minutes Longitude --- E/W GPS quality indicator Number of satellites in use HDOP Antenna altitude re mean sea level (geoid) Units of antenna altitude Geoidal separation (sea level re WGS---84) Units of geoidal separation Age of differential GPS data Differential reference station id Possible extension of datagram with user defined data (addition to NMEA format) Checksum End of sentence delimiter = CRLF Format Always 24h aa Always GGA, hhmmss.ss, llll.ll, a, yyyyy.yy, a, x, xx, x.x, x.x, M, x.x, M, x.x, xxxx, c--- ---c *hh Always 0Dh 0Ah Valid range --Capital letters --000000 to 235959.9... 0000 to 9000.0... N or S 00000 to 18000.0... E or W 0 to 8 00 to 12 0 to ----------0000 to 1023 ------Note ----------------1 --1 2 --2 ------3 -----
Note 1 The HDOP (Horizontal Dilution Of Precision) value will be scaled and copied to the Measure of position fix quality field in the position output datagram. The scale factor depends upon the GPS quality indicators value: 1 - (SPS or standard GPS) => 1000 2 - (differential GPS) => 100 3 - (PPS or precise GPS) => 200, but 10 if GGA is treated as RTK. (See Note 2) 4 - (kinematic GPS with fixed integers) => 10 5 - (kinematic GPS with floating integers) => 50 6 - (estimated or dead reckoning mode) => 1000 7 - (manual input mode) => 1000 8 - (test mode) => 1000, but 10 if GGA is treated as RTK. (See Note 2) The Measure of position fix quality field will be set to 65534 (largest valid number) if the indicator is zero (non- valid position).
852--164111 / A
169
Base version
Note 2 This scaling is used to give at least a relatively correct position fix quality change (in the order of cm) if there are dropouts in differential, precise or kinematic measurements, although HDOP is not a meter value. Note 3 When the quality factor is 4 or 5 a height output datagram is automatically generated, and also if the quality factor is 3 or 8 and the operator has set the GGA position to be an RTK position. The height is the sum of these two fields which are assumed positive upwards (antenna above geoid). The maximum length of this field should is restricted so that the total datagram length is not more than 127 bytes.
GGK Datagram
Data Description Start identifier = $ Talker identifier Sentence formatter UTC time of position UTC date of position Latitude in degrees and minutes, plus optional decimal minutes Latitude --- N/S Longitude in degrees and minutes, plus optional decimal minutes Longitude E/W GPS quality indicator Number of satellites in use DOP Antenna ellipsoidal height Units of antenna ellipsoidal height Possible extension of datagram with user defined data Checksum End of sentence delimiter = CRLF Format Always 24h aa Always GGK, hhmmss.ss, MMDDYY, llll.llllll, a, yyyyy.yyyyyy, a, x, xx, x.x, x.x, M, c--- ---c *hh Always 0Dh 0Ah Valid range --Capital letters --000000 to 235959.99... 010100 to 123199 0000 to 9000.0... N or S 00000 to 18000.0... E or W 0 to 3 00 to 12 0 ------------Note ------------------1 --1 ----2 -----
Note 1 The DOP (Dilution Of Precision) value will be scaled and copied to the Measure of position fix quality field in the position output datagram. The scale factor depends upon the GPS quality indicators value: 1 (SPS or standard GPS) => 1000 2 (differential GPS) => 100 3 (kinematic GPS) => 10
170
852--164111 / A
Datagram formats
The Measure of position fix quality field will be set to 65534 (largest valid number) if the indicator is zero (non- valid position). This scaling is used to give at least a relatively correct position fix quality change (in cm) if there are dropouts in differential, precise or kinematic measurements, although DOP is not a meter value. Note 2 The maximum length of this field should is restricted so that the total datagram length is not more than 127 bytes.
GST Datagram
Data Description Start identifier = $ Talker identifier Sentence formatter UTC time of the GGA or GGK associated with this sentence RMS value of the standard deviation of the range inputs to the navigation process Standard deviation of semi---major axis of error ellipse in meters Standard deviation of semi---minor axis of error ellipse in meters Orientation of semi---major axis of error ellipse in degrees from true North Standard deviation of latitude error in meters Standard deviation of longitude error in meters Standard deviation of altitude error in meters Checksum End of sentence delimiter = CRLF Format Always 24h aa Always GST, hhmmss.ss, x.x, x.x, x.x, x.x, x.x, x.x, x.x, *hh Always 0Dh 0Ah Valid range --Capital letters --000000 to 235959.9... 0 --0 --0 --0 --0 --0 --0 ------Note ----------1 ---------------
Note 1 The term standard deviation of error in the format description implies that the GST datagram was originally intended to contain statistics. Such a use may invalidate the intended use here, namely to derive a better quality measure than the HDOP in the GGA or DOP in the GGK datagram. Thus, the GST datagram should only be used if one is certain that this field contains the semi- major axis of the error ellipse for the latest fix, and not a statistical measure calculated over a number of fixes.
852--164111 / A
171
Base version
VTG Datagram
Data Description Start identifier = $ Talker identifier Sentence formatter Course over ground, degrees true Course over ground, degrees magnetic Speed over ground, knots Speed over ground, km/h Mode indicator Checksum End of sentence delimiter = CRLF Format Always 24h aa Always VTG, x.x,T, x.x,M, x.x,N, x.x,K, a *hh Always 0Dh 0Ah Valid range --Capital letters --0 to 359.9... 0 to 359.9.. 0 --0 --A,D,E,M,S or N ----Note ------1 1 1 1 -------
Note 1 Only true course and the first valid speed field will be used.
Simrad 90 Datagram
Data Description Start identifier = $ Talker identifier Sentence formatter Date of position UTC of position as hour, minute, second, hundredth of second Latitude in degrees, minutes and decimal minutes Hemisphere identifier Longitude in degrees, minutes and decimal minutes, or depth in meters Hemisphere or depth identifier Northing or range in meters Easting or depth in meters UTM zone number User defined central meridian longitude or bearing Hemisphere or bearing identifier System descriptor Position fix quality indicator Speed over ground in m/s Format Always 24h aa Always S90, DDMMYY, hhmmssss, Length Valid range 1 2 4 7 9 --Capital letters --010100 to 311299 00000000 to 23595999 0000.0000 to 9999.9999 N or S 00000.0000 to 18000.0000 E, W or D 000000000.0 to 999999999.9 0000000.0 to 9999999.9 01 to 60 00000.0000 to 35999.9999 E, W, or B 0 to 7 0 to 9 and A to F 00.0 to 99.9 Note -----------
xxxx.xxxx a, xxxxx.xxxx
9 2 10
A A A
a, xxxxxxxxx.x, xxxxxxx.x, xx, xxxxx.xxxx a, x, x, xx.x,
2 12 10 3 10 2 2 2 5
A B B --C C 1 2 3
172
852--164111 / A
Datagram formats
Data Description Course over ground in degrees End of sentence delimiter = ,CRLF
Format xxx.x Always 2Ch 0Dh 0Ah
Length Valid range 5 3 000.0 to 359.9 ---
Note 3 ---
Note 1 Value of system descriptor defines content of datagram as follows. (Note that the Kongsberg Simrad EM 12, the EM 950 and the EM 1000 multibeam echo sounders will only accept values less than 3): 1 2 The position is longitude latitude in global coordinates given in the fields noted A. The position is Northing Easting on the Northern hemisphere given in the fields noted B. If the projection is defined to be UTM the UTM zone number or a user definable central meridian longitude may be given in the field noted C. As for system descriptor equal to 1, but the position is on the Southern Hemisphere. As for system descriptor equal to 0, but in addition the depth is given in the Easting field noted B. As for system descriptor equal to 1, but in addition the depth is given in the longitude field noted A. As for system descriptor equal to 2, but in addition the depth is given in the longitude field noted A. The position is given relative to the vessel in a polar coordinate system with horizontal range and depth provided in the fields noted B and bearing re true North in the field noted C. As for system descriptor 6, but the bearing is re the vessel centerline.
3 4 5 6 7
Note 2 The position fix quality given in the position output datagram will be derived from the quality indicator (this differs from the original definition of the format) as follows (in m):
F 0.01 E 0.02 D 0.05 C 0.1 B 0.2 A 0.5 9 1 8 2 7 5 6 10 5 20 4 50 3 100 2 200 1 500 0 1000
Note 3 If these fields have valid values they will be copied to equivalent fields in the position output datagram. They may be used in filtering of the positioning during postprocessing. (The original definition of the format had line heading in the course field and its use was to orient real- time displays).
852--164111 / A
173
Base version
Tide input
Data Description Start identifier = $ Talker identifier Sentence formatter Date and time of prediction / measurement Tide offset in meters and decimal meters Optional checksum End of sentence delimiter = CRLF Format Always 24h a Always TIDE, YYYYMMDDhhmm, x.x *hh Always 0Dh 0Ah Valid range --Capital letter --199601010000 to 999912312359 327.66 ----Note --------1 -----
Note 1 A negative number will be assumed to indicate an increase in sea level.
Depth or height input

Data Description Start identifier = * Sentence identifier Talker identifier Depth or height in meters and decimal meters End of sentence delimiter = CRLF Format Always 2Ah ii ii x.x Always 0Dh 0Ah Valid range --00 to 09 00 to 99 ----Note --1 --2 ---
Note 1 A sentence identifier equal to 00 is used for underwater vehicle depth, all other identifiers are customer specific (usually a datum height). Note 2 If input is depth, it will be used in the depth output datagram to offset the transmit transducer depth. If input is height, which will usually imply a time or position variable datum height, its use will depend on the sentence identifier and will be implemented as required by a specific customer. Depth is positive downwards. Depths may be scaled and offset by operator settable constants: output_depth [m] = scale_factor * (input_depth - offset)
Attitude data
Overview
Attitude data is generally accepted on one or more serial input port(s) as: roll, pitch, heave and heading on one port, or roll, pitch and heave on one port and heading separately on another port.
174
852--164111 / A
Datagram formats
The data update rate should be commensurate with the expected dynamics of the vessel (typically up to 100 Hz). The acceptable format for roll, pitch, heave and optionally also heading is a 10 byte long message originally defined in the EM 1000 for use with digital motion sensors. It is supported by the following sensors: Applied Analytics POS/MV Photokinetics Octans Seatex MRU Seatex SeaPath TSS DMS- 05 Heading will be accepted in the NMEA 0183 HDT format or in the format used by the Simrad Robertson SKR80(82) gyrocompass. A current loop to RS- 232 converter may then be required. The Lemkuhl LR40(60) Scan Repeater format is also accepted, as it is the same as that of the SKR80 with the exception of an extra status byte. Note that if the attitude sensor is capable of reading the gyrocompass and transfer the heading to the attitude sensor datagram (if it does not measure heading itself), this is preferable to interfacing the gyrocompass directly to the system. Roll, pitch and heading in the Sperry Marine MK- 39 MOD2 Attitude and Heading Reference System format is also accepted. A second motion sensor must then be used to supply heave. Attitude data may be supplied from more than one sensor. All data may be logged, but only one set as chosen by the operator will be used in real time.
EM Attitude input format

The EM attitude format is a 10- bytes long message defined as follows: Byte 1: Sync byte 1 = 00h, or Sensor status = 90h- AFh Byte 2: Sync byte 2 = 90h Byte 3: Roll LSB Byte 4: Roll MSB Byte 5: Pitch LSB Byte 6: Pitch MSB Byte 7: Heave LSB Byte 8: Heave MSB Byte 9: Heading LSB Byte 10: Heading MSB where LSB = least significant byte, MSB = most significant byte.
852--164111 / A
175
Base version
All data are in 2s complement binary, with 0.01_ resolution for roll, pitch and heading, and 1 cm resolution for heave. Roll is positive with port side up with 179.99_ valid range Pitch is positive with bow up with 179.99_ valid range Heave is positive up with 9.99 m valid range Heading is positive clockwise with 0to 359.99_ valid range. Non- valid data are assumed when a value is outside the valid range. How roll is assumed to be measured is operator selectable, either with respect to the horizontal plane (the Hippy 120 or TSS convention) or to the plane tilted by the given pitch angle (i.e. as a rotation angle around the pitch tilted forward pointing x- axis). The latter convention (called Tate- Bryant in the POS/MV documentation) is used inside the system in all data displays and in logged data (a transformation is applied if the roll is given with respect to the horizontal). Note that heave is displayed and logged as positive downwards (the sign is changed) including roll and pitch induced lever arm translation to the systems transmit transducer. This format has previously been used with the EM 950 and the EM 1000 with the first synchronisation byte always assumed to be zero. The sensor manufacturers have been requested to include sensor status in the format using the first synchronisation byte for this purpose. It is thus assumed that: 90h in the first byte indicates a valid measurements with full accuracy any value from 91h to 99h indicates valid data with reduced accuracy (decreasing accuracy with increasing number) any value from 9Ah to 9Fh indicates non- valid data but normal operation (for example configuration or calibration mode) and any value from A0h to AFh indicates a sensor error status
Sperry Mk.39 Attitude input format

The format is 18 bytes long, and it is organised as 9 words. The most significant byte of a word is transmitted first. Word 1 AA55h Word 2 Status and time Word 3 Heading Word 4 Roll Word 5 Pitch Word 6 Heading rate
176
852--164111 / A
Datagram formats
Word 7 Roll rate Word 8 Pitch rate Word 9 Checksum (MSB) and 1s complement of checksum (LSB) All data are in 2s complement binary. Heading is given within 180_, roll and pitch within 90_. (Note however that the values +180_ and +90_ are not permitted, as these are one bit too high.) Heading is measured with reference to true North, and positive when the bow points eastwards. Roll is per definition a rotation angle (Tate- Bryant) and positive when the starboard side goes up. Pitch is positive when the bow goes down.
HDT format
Data Description Start identifier = $ Talker identifier Sentence formatter Heading, degrees true Checksum End of sentence delimiter = CRLF Format Always 24h aa Always HDT, x.x,T *hh Always 0Dh 0Ah Valid range --Capital letters --0 to 359.9... ----Note -------------
SKR80 format
The SKR80 sends out a stream of data with four bytes for each measurement. There is one byte for each digit: The first byte for the decimal degree (Example: xxx.X) The second for the degree (Example: xxX.x) The third for the 10s degree (Example: xXx.x) The fourth for the 100s degree (Example: Xxx.x) The two uppermost bits of a byte are always zero, the next two bits give the digit, 00 for the decimal, 01 for the degree, 10 for the 10s degree, and 11 for the 100s degree. The lowest four bits give the digit value in 4- bit BCD format. As an example a heading of 234.5_ will give the four bytes 05h 14h 23h 32h. The LR40 adds a fifth byte at the end for status with the two upper bits of the status byte set to 11 (11000000 for OK, 11001010 for alarm). This status byte is ignored.
852--164111 / A
177
Base version
Clock
The system clock is used to time stamp all data output. The clock may be set upon start of new survey or power- up on the Processing Unit (recommended source is a NMEA ZDA format datagram). The clock will drift, typically some seconds per day, unless it is synchronised to a 1 PPS (pulse per second) input signal (the clock millisecond counter will be set to zero whenever a pulse is received). A fully correct clock is only necessary if the output data are later to be combined with other time critical data logged or created by other systems, for example an accuracy of up to one minute would be necessary to apply tidal changes. If the timestamp supplied in the position input datagrams is to be used, it is imperative that the system clock is correctly set and that 1 PPS synchronisation is used.
ZDA format
Data Description Start identifier = $ Talker identifier Sentence formatter UTC Day Month Year Local zone hours Local zone minutes Optional checksum End of sentence delimiter = CRLF Format Always 24h aa Always ZDA, hhmmss.ss, xx, xx, xxxx, xx, xx *hh Always 0Dh 0Ah Valid range --Capital letters --000000 to 235959.9... 01 to +31 01 to +12 0000 to 9999 ---13 to +13 00 to +59 ----Note --------------1 1 -----
Note 1 Local zone time is not used. An offset time may be entered by the operator to get the system clock to show a different time than UTC.
Sound Speed
Overview
A sound speed profile may be loaded into the Operator Station either on a serial line or on Ethernet. Formats previously used with existing Kongsberg Simrad echo sounders (Kongsberg Simrad ASCII and Binary Sound Velocity Profile input datagrams) will be accepted, but since their resolution in depth is limited to 1 m and the number of entries to 100, a new format given below without these limitations is recommended. This format is also accepted by the Kongsberg Simrad HIPAP and HPR underwater positioning systems (but not necessarily vice- versa). Note that a complete profile may be pieced together from several datagrams and edited with the Operator Stations Sound Speed Editor.
178
852--164111 / A
Datagram formats
The new format is completely in ASCII and allows 9998 entries without limitations in resolution. In addition to depth and sound speed, it allows input of absorption coefficient, pressure, temperature and salinity or conductivity. The latter parameters may be used to calculate depth, sound speed and absorption coefficient. Use of a depth dependent absorption coefficient allows a more accurate determination of bottom backscatter strength. Note that this datagram may also be logged as output, retaining information not included in the standard sound speed profile output datagram, such as where and when the profile has been taken.
Kongsberg Simrad SSP format

Data Description Start identifier = $ Talker identifier Datagram identifier Data set identifier Number of measurements = N UTC time of data acquisition Day of data acquisition Month of data acquisition Year of data acquisition --- Depth in m from water level or Pressure in MPa --- Sound velocity in m/s --- Temperature in _C --- Salinity in parts per thousand or Conductivity in S/m Data set delimiter End of repeat cycle Latitude in degrees and minutes, plus optional decimal minutes Latitude --- N/S Longitude in degrees and minutes, plus optional decimal minutes Longitude --- E/W Atmospheric pressure in MPa User given comments llll.ll, Variable 5--0000 to 9000.0... 5 Format Always 24h aa Always Sxx, xxxxx, xxxx, hhmmss, xx, xx, xxxx, x.x, x.x, x.x, x.x, Length 1 2 4 6 5 7 3 3 5 2 --1 --1 --1 --Valid range --Capital letters S00to S53 00000 to 65535 0001 to 9999 000000 to 235959 00 to 31 00 to 12 0000 to 9999 0 to 12000.00 0 to 1.0000 1400 to 1700.00 ---5 to 45.00 0 to 45.00 0 to 7.000 0 to 200.00 0Dh 0Ah Note ----1,2 ----3 3 3 3 ---------
N entries of the next 5 fiields --- See note 4
Absorption coefficient in dB/km x.x CRLF
0 --2
-----
a, yyyyy.yy,
2 Variable 6---
N or S 00000 to 18000.0...
5 5
a, x.x, c--- ---c
2 1 --Variable
E or W 0 to 1.0000 ---
5 5 5
852--164111 / A
179
Base version
Data Description Optional checksum End of datagram delimiter = \CRLF
Format *hh 5Ch 0Dh 0Ah
Length --3
Valid range -----
Note 6 ---
Note 1 The datagram identifier identifies what type of data is included. This is shown in the following table where D is depth, P is pressure, S is salinity, C is conductivity, c is sound speed, a is absorption coefficients, and L is latitude. The notation c(T,S) indicates for example that the sound speed is to be calculated from the temperature and salinity input data. When pressure is used, the atmospheric pressure must be given if the pressure is absolute, otherwise the pressure must be given re the sea level and the atmospheric pressure must be zero.
Identifier S00 S10 S11 S12 S20 S21 S22 S30 S31 S32 S40 S41 S42 S50 S51 S52 Input data D, c D, c D, c, a D, c, T, S D, T, S D, T, S, a D, T, S D, T, C D, T, C, a D, T, C P T, S , P T, S, a , P T, S , P T, C , P T, C, a , P T, C , Data to be used D, c D, c D, c, a D, c, a(D,T,S,L) D, c(D,T,S,L) D, c(D,T,S,L), a D, c(D,T,S,L), a(D,T,S,L) D, c(D,T,C,L) D, c(D,T,C,L), a D, c(D,T,C,L), a(D,T,C,L) D(P ,T,S,L), c(P ,T,S,L) D(P ,T,S,L), c(P ,T,S,L), a D(P ,T,S,L), c(P ,T,S,L), a(P ,T,S,L) D(P ,T,C,L), c(P ,T,C,L) D(P ,T,C,L), c(P ,T,C,L), a D(P ,T,C,L), c(P ,T,C,L) , a(P ,T,C,L)
Note 2 S00 is a special case because then the sound speed profile will be taken into use immediately without further operator intervention. The checksum is then mandatory and must be correct. Furthermore entries for zero depth and a deeper depth than expected during the survey must be included. Note 3 Note that these fields have fixed length and leading zeros must be used. Note 4
180
852--164111 / A
Datagram formats
The depth or pressure field is always required while the other fields are optional except for those required by the datagram identifier. The field- delimiting commas must always be included even if the fields are empty. Note 5 The positions, atmospheric pressure and comment fields are optional. Note that the option field must not include a \. It is recommended to include sensor type in the comment field. Note 6 The checksum field is calculated between the $ and the * delimiters by exclusive ORing of all bytes. The checksum is required for datagram S00, but is optional for the others.
AML CALC format

Sound speed profile data input in the CALC format is used by the Applied Microsystems Ltd. (AML) Total System Software package to support AMLs complete range of sensors is also accepted. This format is an ASCII format with a five line header plus a variable number of lines with data as follows: Line 1: CALC, sn, date, depthincrement, depthdisplay sn is the sensor serial number date is current date taken from computer depthincrement is logging depth increment depthdisplay is depth units (meters or decibars) Line 2: AML SOUND VELOCITY PROFILER S/N: xxxxx Line 3: DATE:xxxxx TIME:xxxxx This line gives the Julian date and time at start of sensor logging Line 4: DEPTH OFFSET(M): xxxx.x This line gives the pressure offset at sea level. Each line of data contains three numbers: depth (in meters) sound velocity (in m/s) temperature (in degrees Celcius) Line 5: DEPTH(M) VELOCITY (M/S) TEMPERATURE (_C) The numbers are separated by a space, and each line is terminated with a linefeed (LF). The numbers shall all include a decimal point (xxx.x xxxx.x xx.xLF). The data are terminated by a line with three zeros with two spaces between the zeros (0 0 0).
AML Smart Sensor format

The AML Smart SV&P sensor and later the SVPlus sensor may be used directly for sound speed profile input on serial line to the Operator Station. Both these sensors may also be used to measure the sound speed at the transducer depth continuously during the surveying.
852--164111 / A
181
Base version
A measurement is requested from a smart sensor by issuing the word scan as four ASCII characters terminated by CR. The reply from the SV sensor is a string of ASCII characters: SCRLF xxxx.x CRLF> where xxxx.x is the measured sound speed in m/s (in bytes 5- 11). From the SV&P sensor the received string is: SCRLF xxx.xx xxxx.x CRLF> where the first number is the pressure in decibars relative to the surface and the second sound speed in m/s (in bytes 13- 19). Smart sensors with autonomous output may also be used, both P&SV (sound speed with pressure) and T&SP (sound speed with temperature). The P&SV format is: xxx.xx xxxx.x CRLF The T&SP format is: xx.xxx xxxx.x CRLF The last field in both of these formats give the sound speed and the first field either pressure in decibars or temperature in degrees Celcius.
Depth input from single beam echo sounder

Overview
Depth datagrams from a single beam echo sounder are accepted for display and logging on the system. The following formats are supported: NMEA 0183 DBS NMEA 0183 DPT binary datagrams from the Kongsberg Simrad EA 500 echo sounder series.
DBS format
Data Description Start identifier = $ Talker identifier Sentence formatter Depth in feet Depth in meters Depth in fathoms Checksum End of sentence delimiter = CRLF Format Always 24h aa Always DBS, x.x,f, x.x,M, x.x,F *hh Always 0Dh 0Ah Valid range --Capital letters --0.1 --0.1 --0.1 ------Note ------1 1 1 -----
182
852--164111 / A
Datagram formats
Note 1 The decoding priority will be meter field, feet field and fathom field with the depth value extracted from the first field with valid data.
DPT format
Data Description Start identifier = $ Talker identifier Sentence formatter Depth in meters from the transducer Offset of transducer from waterline in meters Maximum range scale in use Checksum End of sentence delimiter = CRLF Format Always 24h aa Always DPT, x.x, x.x, x.x *hh Always 0Dh 0Ah Valid range --Capital letters --0.1 --0 --------Note --------1 -------
Note 1 A negative value implying that the offset is from the keel should not be used.
EA 500 format
Data Description Start identifier = D Channel identifier Time as HHMMSShh Depth in meters from the transducer Bottom backscattering strength in dB Transducer number Athwartship slope in degrees Format Always 34h x, xxxxxxxx, 32 bit IEEE 754 floating point 32 bit IEEE 754 floating point 32 bit integer 32 bit IEEE 754 floating point Valid range --1 to 3 00000000 to 23595999 0.1 --------Note --1 1 1 -------
Note 1 Only the channel identifier, depth and time will be decoded by the system. The least significant byte is transmitted first (the Intel convention). Note ! The datagram must be sent on Ethernet to UDP port number 2200 on the Operator Station.
Remote control
Overview
A Remote Control datagram has been implemented to allow:
852--164111 / A
183
Base version
the multibeam echo sounder to start logging on remote command. the multibeam echo sounder to send out parameter and sound speed profile datagrams as a response to the remote command. the survey line numbers to be remotely settable. Note that the parameter and sound speed profile datagrams are always sent out when logging is started or any changes are made to the parameters or sound speed. They may also be sent out regularly at operator specified intervals. The datagram currently only allows survey related parameters to be transferred to the system. It will later be expanded to allow remote setting of all installation parameters, and then basically as a copy of the standard start/stop datagram with identical conventions with regard to order (which is not important), but requiring only the parameters actually to be set.
Data Description Start identifier = $ Talker identifier Datagram identifier EM model number Responsible operator Survey identifier Survey line number Survey line identifier (planned line no) Comment Optional checksum End of datagram delimiter = \CRLF Format Always 24h aa Rxx, EMX=dddd, ROP=a--- ---a, SID=a--- ---a, PLN=d..d, PLL=d--- ---d, COM=a--- ---a *hh 5Ch 0Dh 0Ah Valid range --Capital letters R00 to R20 ----------------Note ----1 2 ---------------
Note 1 Rxx defines what action the system is to take with respect to pinging and logging of data in addition to changes in the parameters. Note that logging of survey data on local storage is not affected, this is determined by operator control from the menu only. R00 - System to stop pinging (and logging if on) R10 - System to stop all logging (but continue or start pinging). R11 - System to start logging on new line to both local and remote R12 - System to star logging on new line but only to local storage R13 - System to start logging on new line but only to remote R20 - System to send installation parameter datagram and sound speed profile datagrams to remote
184
852--164111 / A
Datagram formats
Note 2 The EM model number will be required when parameter changes are made with respect to transducer location or system gain settings.
852--164111 / A
185
Base version
Overview
Output datagrams are usually logged to disk or tape on the EM Series Operator Station. The output datagrams may also be exported to user provided programs on the Operator Station or on an external Ethernet network using UDP protocol (remote logging). An NMEA DPT depth datagram may be exported on a serial line. The output datagrams are mostly in binary format using signed or unsigned integer numbers with lengths of 1, 2 or 4 bytes. All binary data will presently be big endian. Note ! As this is subject to modifications, we recommend that software written to decode EM Series data includes a check for the byte ordering with a provision for byte swapping. Suitable data fields to check on are the length field at the start of the datagram, the EM Series model number field and possibly the date and time fields. The basic output datagram structure established with the EM 100 echo sounder is retained. All datagrams (except the NMEA DPT datagram) start with STX, datagram type and time tag, and end with ETX and checksum (sum of bytes between STX and ETX). In addition the total length of the datagram (not including the length field) will precede the STX byte, given as a four byte binary number. The length field is only included when logging to tape and/or disk, but not for datagrams logged to a remote location. The length can then be derived from the network software. Systems logging data remotely should add this length at the start of each datagram. This length is required if the data are to be used with Kongsberg Simrad postprocessing systems. The time stamp resolution has been increased to 1 millisecond and now includes the century, but as a consequence the time stamp is now binary and not ASCII as implemented previously. The date is given as 10000*year(4 digits) + 100*month + day, for example 19950226 for February 26, 1995. All date fields in the output datagrams use this format. A time is usually given (in milliseconds) from midnight. The datagrams identify the multibeam echo sounder model and its serial number. The system model number is 120 for the EM 120, 300 for the EM 300, etc. For the EM 3000D (the dual head system) the model number was originally given as 3002 and the serial number is that of Sonar Head number 1. However in the depth datagram model numbers 3003- 3008 are now used to also identify the actual transmit and sampling frequencies of the two heads. If only one head is activate on the EM 3000D, it is coded as a single head system.
186
852--164111 / A
Datagram formats
Due care has been taken to include all parameters needed in postprocessing in the relevant datagrams, with a minimum of data duplication. Where resolution of a data field is variable, a resolution descriptor is included. Invalid data are always identified by the highest positive number allowed in a field unless otherwise noted. A real- time parameter datagram has been added to enable logging of parameters not used in postprocessing, but which may be important in checking the quality of the logged data, or to allow tracing of reasons for possible malfunctions. Attitude data as time continuous records and raw ranges and beam pointing angles are logged to allow eventual postprocessing corrections. The logged attitudes are valid at the transmit transducer, and are corrected for any sensor offsets.
Depth
Data Description Number of bytes in datagram Start identifier = STX (Always 02h) Type of datagram = D(epth data) (Always 44h) EM model number (Example: EM 3000 = 3000) Date = year*10000 + month*100 + day (Example: Feb 26, 1995 = 19950226) Time since midnight in milliseconds (Example: 08:12:51.234 = 29570234) Ping counter (sequential counter) System serial number Heading of vessel in 0.01 Sound speed at transducer in dm/s Transmit transducer depth re water level at time of ping in cm Maximum number of beams possible Number of valid beams = N z resolution in cm x and y resolution in cm Sampling rate (f) in Hz or Depth difference between sonar heads in the EM 3000D Repeat cycle --- N entries of : --- Depth (z) from transmit transducer (unsigned for EM 120 and EM 300) Format 4U 1U 1U 2U 4U 4U 2U 2U 2U 2U 2U 1U 1U 1U 1U 2U 2S 16*N 2S or 2U Valid range ----------0 to 86399999 0 to 65535 100 --0 to 35999 14000 to 16000 0 to 65536 48 --1 to 254 1 to 254 1 to 254 300 to 30000 ---32768 to 32766 -----32768 to +32766 or 1 to 65534 Note ------4 ------------1 --------3 4 --2
852--164111 / A
187
Base version
Data Description --- Acrosstrack distance (y) --- Alongtrack distance (x) --- Beam depression angle in 0.01 --- Beam azimuth angle in 0.01 --- Range (one---way travel time) --- Quality factor --- Length of detection window (samples) (Example: ---20 dB = 216) --- Reflectivity (BS) in 0.5 dB resolution/4) --- Beam number End of repeat cycle Transducer depth offset multiplier End identifier = ETX (Always 03h) Check sum of data between STX and ETX
Format 2S 2S 2S 2U 2U 1U 1U 1S 1U 1S 1U 2U
Valid range ---32768 to 32766 ---32768 to 32766 ---11000 to 11000 0 to 56999 0 to 65534 0 to 254 1 to 254 ---128 to +126 1 to 254 ---1 to +17 -----
Note 2 2 3 3 3 5 ----6 1 -----
Note 1 The transmit transducer depth plus the depth offset multiplier times 65536 cm should be added to the beam depths to derive the depths re the water line. The depth offset multiplier will usually be zero, except when the EM 2000/3000 Sonar Head is on an underwater vehicle at a depth larger than 655.36 m. Note that the offset multiplier will be negative (- 1) if the actual heave is large enough to bring the transmit transducer above the water line. This may represent a valid situation, but may also be due to an erroneously set installation depth of either the transducer or the water line. Note 2 The beam data are given re the transmit transducer or sonar head depth and the horizontal location of the active positioning systems antenna. Heave, roll, pitch, sound speed at the transducer depth and ray bending through the water column have been applied. On the EM 1002/2000/3000 the beam depths must be regarded as signed values to take into account beams which may be going upwards. On the EM 120/300 the beam depths are always positive and the values are therefore unsigned. Note 3 The range, beam depression angle (positive downwards and 90_ for a vertical beam) and beam azimuth angle (re vessel centerline) are given relative to the transducer (sonar head) at the ping transmit time. Heave, roll, pitch and sound speed at the transducer depth have been applied, but not ray bending. These values may thus be directly used for a new ray bending calculation with a revised sound speed profile to generate new sounding depths and positions without any need for using attitude data. The range resolution in time is the inverse of the
188
852--164111 / A
Datagram formats
range sampling rate (i.e. nominally equivalent to about 70 ms for the EM 3000). Note that if the data need to be reprocessed with a new sound speed at the transducer depth or new roll, pitch or heave values, full reprocessing starting with the raw range and beam angle data is required. Attitude data is also required in this reprocessing, and both these data types will in the future be logged as standard. If the beam azimuth angle has a value larger than 35999, the beam pointing angle has replaced the beam depression angle, and the raw two- way travel time has replaced the one- way heave and beam angle corrected travel time. The transmit tilt angle plus 54000 is given in the beam azimuth angle field. The use of this data definition is available on remote output to a port named as RawDepth... for use by other systems which do their own attitude and sound speed processing. Note 4 In an EM 3000D the transmit transducer depth is that of Sonar Head number 1, taking into account the depth offset multiplier as described in note 1. The range multiplier is replaced by the difference in depth between Sonar Head number 1 and 2, i.e. head 2 depth is equal to head 1 depth (possibly modified with depth offset multiplier) plus the depth difference. The range sampling rates in Hz of the two heads is given through the EM model number according to the following table:
EM model number Sonar Head 1 Sonar Head 2 3003 13956 14621 3004 14293 14621 3005 13956 14293 3006 14621 14293 3007 14293 13956 3008 14621 13956
Previously the model number of the EM 3000D was given as 3002 with head sample rates of 13956 and 14621 Hz respectively. The head depths in this case should be assumed to be equal, and although the mathematical derivation of final beam depths would elsewise be the same as described above, the transmit transducer depth was not actually exactly that of the sonar heads. Note 5 The quality numbers upper bit signifies whether amplitude (0) or phase (1) detection has been used. If amplitude the 7 lowest bits give the number of samples used in the centre of gravity calculation. If phase the second highest bit signifies whether a second (0) or first (1) order curve fit has been applied to determine the zero phase range, and the 6 lowest bits indicates the quality of the fit (actually the normalized variance of the fit re the maximum allowed, i.e. with a lower number the better the fit). Note 6 Beam 128 is the first beam on the second sonar head in an EM 3000D dual head system.
852--164111 / A
189
Base version
Raw range and beam angle

Data Description Number of bytes in datagram Start identifier = STX (Always 02h) Type of datagram = F (Always 46h) EM model number (Example: EM 3000 = 3000) Date = year*10000 + month*100 + day (Example: Feb 26, 1995 = 19950226) Time since midnight in milliseconds (Example: 08:12:51.234 = 29570234) Ping counter (sequential counter) System serial number Maximum number of beams possible Number of valid beams = N Sound speed at transducer in dm/s Repeat cycle --- N entries of : --- Beam pointing angle in 0.01 --- Transmit tilt angle in 0.01 --- Range (two---way travel time) --- Reflectivity (BS) in 0.5 dB resolution --- Beam number End of repeat cycle Spare (Always 0) End identifier = ETX (Always 03h) Check sum of data between STX and ETX 1U 1U 2U ------------Format 4U 1U 1U 2U 4U 4U 2U 2U 1U 1U 2U 8*N 2S 2U 2U 1S 1U Valid range ----------0 to 86399999 0 to 65535 100 --48 --1 to 254 14000 to 16000 -----11000 to 11000 ---2999 to 2999 0 to 65534 ---128 to 126 1 to 254 1 1 1 ----Note -----------------------
Note 1 The beam pointing angle is positive to port and the transmit tilt angle is positive forwards for a normally mounted system looking downwards. The range resolution in time is the inverse of the range sampling rate given in the depth datagrams.
Seabed image
Data Description Number of bytes in datagram Start identifier = STX (Always 02h) Type of datagram = S(eabed image data) (Always 53h) EM model number (Example: EM 3000 = 3000) Date = year*10000 + month*100 + day (Example: Feb 26, 1995 = 19950226) Time since midnight in milliseconds (Example: 08:12:51.234 = 29570234 Format 4U 1U 1U 2U 4U 4U Valid range ----------0 to 86399999 Note -------------
190
852--164111 / A
Datagram formats
Data Description Ping counter (sequential counter) System serial number Mean absorption coefficient in 0.01 dB/km Pulse length in ms Range to normal incidence used to correct sample amplitudes in no. of samples Start range sample of TVG ramp if not enough dynamic range (0 else) Stop range sample of TVG ramp if not enough dynamic range (0 else) Normal incidence BS in dB (BSN) (Example: ---20 dB = 236) Oblique BS in dB (BSO) (Example: ---1 dB = 255) Tx beamwidth in 0.1 TVG law crossover angle in 0.1_ Number of valid beams (N) Repeat cycle --- N entries of : --- beam index number --- sorting direction --- number of samples per beam = Ns --- centre sample number End of repeat cycle Repeat cycle --- SNs entries of: --- Sample amplitudes in 0.5 dB (Example: ---30 dB = 196) End of repeat cycle Spare byte if required to get even length (Always 0 if used) End identifier = ETX (Always 03h) Check sum of data between STX and ETX
Format 2U 2U 2U 2U 2U 2U 2U 1S 1S 2U 1U 1U 6*N 1U 1S 2U 2U SNs 1S
Valid range 0 to 65535 100 --1 to 20000 50 --1 to 16384 0 to 16384 0 to 16384 ---50 to 10 ---60 to 0 1 to 300 20 to 300 1 to 254 --0 to 253 ---1 or 1 1 --1 -------128 to 126
Note ----1 1 ----------------2 3 --4
---
0---1U 1U 2U
-------
-------
Note 1 These fields have earlier had other definitions. Note 2 The beam index number is the beam number - 1. Note 3 The first sample in a beam has lowest range if 1, highest if - 1. Note that the range sampling rate is defined by the sampling rate in the depth output datagram and that the ranges in the seabed image datagram are all two- way from time of transmit to time of receive Note 4 The centre sample number is the detection point of a beam.
852--164111 / A
191
Base version
Central beams echogram

Data Description Number of bytes in datagram Start identifier = STX (Always 02h) Type of datagram = K (Always 4Bh) EM model number (Example: EM 3000 = 3000) Date = year*10000 + month*100 + day (Example: Feb 26, 1995 = 19950226) Time since midnight in milliseconds (Example: 08:12:51.234 = 29570234) Ping counter (sequential counter) System serial number Mean absorption coefficient in 0.01 dB/km Pulse length in ms Range to normal incidence used in TVG Start range sample of TVG ramp if not enough dynamic range (0 else) Stop range sample of TVG ramp if not enough dynamic range (0 else) Normal incidence BS in dB (BSN) (Example: ---20 dB = 236) Oblique BS in dB (BSO) (Example: ---1 dB = 255) Tx beamwidth in 0.1 TVG law crossover angle in 0.1_ Number of included beams (N) Repeat cycle --- N entries of : --- beam index number Format 4U 1U 1U 2U 4U 4U 2U 2U 2U 2U 2U 2U 2U 1S 1S 2U 1U 1U 6*N Valid range ----------0 to 86399999 0 to 65535 100 --1 to 20000 50 --1 to 16384 0 to 116384 0 to 16384 ---50 to +10 ---60 to 0 1 to 300 20 to 300 1 ----0 to 253 --2 ----3 Note ----------------1 1 1 ----1 1 1 1 ---
- spare byte to get even length (Always 0) - number of samples per beam = Ns - start range in samples
End of repeat cycle Repeat cycle --- SNs entries of: --- Sample amplitudes in 0.5 dB (Example: ---30 dB = 196) End of repeat cycle Spare byte if required to get even length (Always 0 if used) End identifier = ETX (Always 03h) Check sum of data between STX and ETX
1U 1U 2U 2U
SNs 1S
11-----128 to +126 -------
---
0---1U 1U 2U
-------
192
852--164111 / A
Datagram formats
Note 1 The sample amplitudes are not corrected in accordance with the detection parameters derived for the ping, as is done for the seabed image data. Note 2 The beam index number is the beam number - 1. Note 3 The range for which the first sample amplitude is valid for this beam given as a two- way range. The detection range is given in the raw range and beam angle datagram. Note that data are provided regardless of whether a beam has a valid detection or not.
Position
Data Description Number of bytes in datagram Start identifier = STX (Always 02h) Type of datagram = P(osition data) (Always 050h) EM model number (Example: EM 3000 = 3000) Date = year*10000 + month*100 + day (Example: Feb 26, 1995 = 19950226) Time since midnight in milliseconds (Example: 08:12:51.234 = 29570234) Position counter (sequential counter) System / serial number Latitude in decimal degrees*20000000 (negative if southern hemisphere) (Example: 3234 S = ---651333333) Longitude in decimal degrees*10000000 (negative if western hemisphere) (Example: 110.25 E = 1102500000 ) Measure of position fix quality in cm Speed of vessel over ground in cm/s Course of vessel over ground in 0.01 Heading of vessel in 0.01 Position system descriptor Number of bytes in input datagram Position input datagram as received Spare byte if required to get even length (Always 0 if used) End identifier = ETX (Always 03h) Check sum of data between STX and ETX Format 4U 1U 1U 2U 4U 4U 2U 2U 4S Valid range ----------0 to 86399999 0 to 65535 100 ----Note -------------------
4S
---
---
2U 2U 2U 2U 1U 1U Variable 0---1U 1U 2U
--0 --0 to 35999 0 to 35999 1 to 254 --- 254 ---------
1 1 1 --2 --3 -------
Note 1 These data will be valid only if available as input.
852--164111 / A
193
Base version
Note 2 The position system descriptor shows which source this data is from and its real- time use by bit coding: xxxx xx01 - position system no 1 xxxx xx10 position system no 2 xxxx xx11 position system no 3 10xx xxxx the position system is active, system time has been used 11xx xxxx - the position system is active, input datagram time has been used xxxx 1xxx the position may have to be derived from the input datagram which is then in SIMRAD 90 format. Note 3 Complete input datagram except header and tail (such as NMEA 0183 $ and CRLF).
Height
Data Description Number of bytes in datagram Start identifier = STX (Always 02h) Type of datagram = h(eight data) (Always 068h) EM model number (Example: EM 3000 = 3000) Date = year*10000 + month*100 + day (Example: Feb 26, 1995 = 19950226) Time since midnight in milliseconds (EXample: 08:12:51.234 = 29570234) Height counter (sequential counter) System serial number Height in cm Heigth type End identifier = ETX (Always 03h) Check sum of data between STX and ETX Format 4U 1U 1U 2U 4U 4U 2U 2U 4S 1U 1U 2U Valid range ----------0 to 86399999 0 to 65535 100 -----4294967296 to 4294967295 0 to 99 ----Note ------------------1 -----
Note 1 The height type is as given in the height input datagram unless it is zero. Then the height is derived from the GGK or GGA datagram and is the height of the water level re the vertical datum (possibly motion corrected).
194
852--164111 / A
Datagram formats
Tide
Data Description Number of bytes in datagram Start identifier = STX (Always 02h) Type of datagram = T(ide data) (Always 054h) EM model number (Example: EM 3000 = 3000) Date = year*10000 + month*100 + day (Example: Feb 26, 1995 = 19950226) Time since midnight in milliseconds (Example: 08:12:51.234 = 29570234) Tide counter (sequential counter) System serial number Date = year*10000 + month*100 + day (from input datagram) (Example: Feb 26, 1995 = 19950226) Time since midnight in milliseconds (from input datagram) (Example: 08:12:51.234 = 29570234) Tidal offset in cm Spare (Always 0) End identifier = ETX (Always 03h) Check sum of data between STX and ETX Format 4U 1U 1U 2U 4U 4U 2U 2U 4U Valid range ----------0 to 86399999 0 to 65535 100 ------------------Note -----
4U 2S 1U 1U 2U
0 to 86399999 ---32768 to 32766 -------
-----------
Attitude
Data Description Number of bytes in datagram Start identifier = STX (Always 02h) Type of datagram = A(ttitude data) (Always 041h) EM model number (Example: EM 3000 = 3000) Date = year*10000 + month*100 + day (at start of data record) (Example: Feb 26, 1995 = 19950226) Time since midnight in milliseconds (at start of data record) (Example: 08:12:51.234 = 29570234) Attitude counter (sequential counter) System serial number Number of entries = N Repeat cycle --- N entries of: --- Time in milliseconds since record start --- Sensor status --- Roll in 0.01 Format 4U 1U 1U 2U 4U Valid range ----------Note -----------
4U
0 to 86399999 0 to 65535 100 --1 ----0 to 65534 -----18000 to 18000
---
2U 2U 2U 12*N 2U 2U 2S
--------1 ---
852--164111 / A
195
Base version
Data Description --- Pitch in 0.01 --- Heave in cm --- Heading in 0.01 End of repeat cycle Sensor system descriptor End identifier = ETX (Always 03h) Check sum of data between STX and ETX
Format 2S 2S 2U 1U 1U 2U
Valid range ---18000 to 18000 ---1000 to 10000 0 to 35999 -------
Note ------2 -----
Note 1 The sensor status will be copied from the input datagrams two sync bytes if the sensor uses the EM format, and from the sensors status word if it is a Sperry Mk39. See the input format description for further details. Note 2 The sensor system descriptor will show which sensor the data is derived from, and which of the sensors data have been used in real time by bit coding: xx01 xxxx motion sensor number 1 xx10 xxxx motion sensor number 2 xxxx xxx1 heading from the sensor is active xxxx xx0x roll from the sensor is active xxxx x0xx pitch from the sensor is active xxxx 0xxx heave from the sensor is active
Heading
Data Description Number of bytes in datagram Start identifier = STX (Always 02h) Type of datagram = H(eading data) (Always 048h) EM model number (Example: EM 3000 = 3000) Date = year*10000 + month*100 + day (at start of data record) (Example: Feb 26, 1995 = 19950226) Time since midnight in milliseconds (at start of data record) (System: 08:12:51.234 = 29570234) Heading counter (sequential counter) System serial number Number of entries = N Format 4U 1U 1U 2U 4U Valid range ----------Note -----------
4U
0 to 86399999 0 to 65535 100 --1 ---
---
2U 2U 2U
-------
196
852--164111 / A
Datagram formats
Data Description Repeat cycle --- N entries of: --- Time in milliseconds since record start --- Heading in 0.01 End of repeat cycle Heading indicator (active or not) (0 = inactive) End identifier = ETX (Always 03h) Check sum of data between STX and ETX
Format 4*N 2U 2U 1U 1U 2U
Valid range --0 to 65534 0 to 35999 -------
Note -------------
Mechanical transducer tilt

Data Description Number of bytes in datagram Start identifier = STX (Always 02h) Type of datagram = J (Always 4Ah) EM model number (Example: EM 1002 = 1002) Date = year*10000 + month*100 + day (at start of data record) (Example: Feb 26, 1995 = 19950226) Time since midnight in milliseconds (at start of data record) (Example: 08:12:51.234 = 29570234) Tilt counter (sequential counter) System serial number Number of entries = N Repeat cycle --- N entries of: --- Time in milliseconds since record start --- Tilt in 0.01 degrees End of repeat cycle Spare (Always zero) End identifier = ETX (Always 03h) Check sum of data between STX and ETX 1U 1U 2U ------------Format 4U 1U 1U 2U 4U Valid range ------------Note
4U
0 to 86399999 0 to 65535 100 --1 ----0 to 65534 ---1499 to +1499
---
2U 2U 2U 4*N 2U 2S
--------1
Note 1 This tilt angle is the measured mechanical tilt of a hull unit such as that often supplied with the EM 1002. It is positive when the transducer is tilted forewards.
Clock
Data Description Number of bytes in datagram Start identifier = STX (Always 02h) Format 4U 1U Valid range ----Note -----
852--164111 / A
197
Base version
Data Description Type of datagram = C(lock data) (Always 043h) EM model number (Example: EM 3000 = 3000) Date = year*10000 + month*100 + day (of EM clock) (Example: Feb 26, 1995 = 19950226) Time since midnight in milliseconds (of EM clock) (Example: 08:12:51.234 = 29570234) Clock counter (sequential counter) System serial number Date = year*10000 + month*100 + day (from external clock input) (Example: Feb 26, 1995 = 19950226) Time since midnight in milliseconds (from external clock datagram) (Example: 08:12:51.234 = 29570234) 1 PPS use (active or not) (0 = inactive) End identifier = ETX (Always 03h) Check sum of data between STX and ETX
Format 1U 2U 4U 4U 2U 2U 4U
Valid range ------0 to 86399999 0 to 65535 100 -----
Note ---------------
4U
0 to 86399999 -------
---
1U 1U 2U
1 -----
Note 1 Shows if the system clock is synchronised to an external 1 PPS signal or not.
Surface sound speed

Data Description Number of bytes in datagram Start identifier = STX (Always 02h) Type of datagram = G (Always 047h) EM model number (Example: EM 3000 = 3000) Date = year*10000 + month*100 + day (at start of data record) (Example: Feb 26, 1995 = 19950226) Time since midnight in milliseconds (at start of data record) (Example: 08:12:51.234 = 29570234) Sound speed counter (sequential counter) System serial number Number of entries = N Repeat cycle --- N entries of: --- Time in seconds since record start --- Sound speed in dm/s (including offset) End of repeat cycle Format 4U 1U 1U 2U 4U Valid range ----------Note -----------
4U
0 to 86399999 0 to 65535 100 --1 ----0 to 65534 14000 to 15999
---
2U 2U 2U 4*N 2U 2U
-----------
198
852--164111 / A
Datagram formats
Data Description Spare (Always 0) End identifier = ETX (Always 03h) Check sum of data between STX and ETX
Format 1U 1U 2U
Valid range -------
Note -------
Sound speed profile

This datagram will contain the profile actually used in the real time raybending calculations to convert range and angle to xyz data. It will usually be issued together with the installation parameter datagram. Note ! The format as given below has been changed from previous editions of this manual. The former format is identified by its type which was V (056h). The previous format had 2 byte long fields for depth and sound speed, this is now 4 bytes.
Format 4U 1U 1U 2U 4U 4U Valid range ----------0 to 86399999 0 to 65535 100 ----Note -------------
Data Description Number of bytes in datagram Start identifier = STX (Always 02h) Type of datagram = U (Always 055h) EM model number (Example: EM 3000 = 3000) Date = year*10000 + month*100 + day (at start of use) (Example: Feb 26, 1995 = 19950226) Time since midnight in milliseconds (at start of use) (Example: 08:12:51.234 = 29570234) Profile counter (sequential counter) System serial number Date = year*10000 + month*100 + day (when profile was made) (Example: Feb 26, 1995 = 19950226) Time since midnight in milliseconds (when profile was made) (Example: 08:12:51.234 = 29570234) Number of entries = N Depth resolution in cm Repeat cycle --- N entries of:
2U 2U 4U
-------
4U
0 to 86399999 1 --1 to 254 --14000 to 17000 -------
---
2U 2U 8*N 4U 4U
---------
- Depth
--- Sound speed in dm/s End of repeat cycle Spare byte to get even length (Always 0) End identifier = ETX (Always 03h) Check sum of data between STX and ETX
0 to 1200000 ---
1U 1U 2U
-------
852--164111 / A
199
Base version
Kongsberg Simrad SSP output

This datagram will contain the profile as received as input, and is logged as is to enable use of its data in postprocessing. The real time use of its data is decided by the operator, the sound speed profile actually being used is given by the sound speed profile output datagram (see above).
Data Description Number of bytes in datagram Start identifier = STX (Always 02h) Type of datagram = W (Always 057h) EM model number (Example: EM 3000 = 3000) Date = year*10000 + month*100 + day (Example: Feb 26, 1995 = 19950226) Time since midnight in milliseconds (Example: 08:12:51.234 = 29570234) SSP counter (sequential counter) System serial number Format 4U 1U 1U 2U 4U 4U 2U 2U Valid range ----------0 to 86399999 0 to 65535 100 ----------Note -------------------------
Input datagram starting with Sentence formatter and ending Variable with Comment Spare byte if required to get even length (Always 0 if used ) 0 --- 1U End identifier = ETX (Always 03h) Check sum of data between STX and ETX 1U 2U
Single beam echo sounder depth

Data Description Number of bytes in datagram Start identifier = STX (Always 02h) Type of datagram = E(cho sounder data) (Always 045h) EM model number (Example: EM 3000 = 3000) Date = year*10000 + month*100 + day (of EM clock) (Example: Feb 26, 1995 = 19950226) Time since midnight in milliseconds (of EM clock) (Example: 08:12:51.234 = 29570234) Echo sounder counter (sequential counter) System serial number Date = year*10000 + month*100 + day (from input datagram if available) (Example: Feb 26, 1995 = 19950226) Format 4U 1U 1U 2U 4U 4U 2U 2U 4U Valid range ----------0 to 86399999 0 to 65535 100 ----Note -------------------
Time since midnight in milliseconds (from input datagram if 4U available) (Example: 08:12:51.234 = 29570234)
0 to 86399999
---
200
852--164111 / A
Datagram formats
Data Description Echo sounder depth from waterline in cm Source identifier (S, T, 1, 2 or 3) End identifier = ETX (Always 03h) Check sum of data between STX and ETX
Format 4U ASCII 1U 2U
Valid range 0 to 1200000 -------
Note --1 -----
Note 1 Identifies the source datagram type, i.e. NMEA DBS, NMEA DPT or EA 500 series channel 1- 3 respectively.
Runtime parameter
Data Description Number of bytes in datagram Start identifier = STX (Always 02h) Type of datagram = R(untime parameter) (Always 052h) EM model number /Example: EM 3000 = 3000) Date = year*10000 + month*100 + day (Example: Feb 26, 1995 = 19950226) Time since midnight in milliseconds (Example: 08:12:51.234 = 29570234) Ping counter System serial number Operator Station status Processing Unit status BSP status Sonar Head or Transceiver status Mode Filter identifier Minimum depth in m Maximum depth in m Absorption coefficient in 0.01 dB/km Transmit pulse length in ms Transmit beamwidth in 0.1 degrees Transmit power re maximum in dB Receive beamwidth in 0.1 degrees Receive bandwidth in 50 Hz resolution Receiver fixed gain setting in dB TVG law crossover angle in degrees Source of sound speed at transducer Maximum port swath width in m Beam spacing Maximum port coverage in degrees Format 4U 1U 1U 2U 4U 4U 2U 2U 1U 1U 1U 1U 1U 1U 2U 2U 2U 2U 2U 1S 1U 1U 1U 1U 1U 2U 1U 1U Valid range ----------0 to 86399999 0 to 65535 100 ----------1 --0 to 254 0 to 10000 1 to 12000 1 to 20000 1 to 50000 1 to 300 0 to ---50 5 to 80 1 to 254 0 to 50 2 to 30 0 to 3 10 to 20000 0 to 2 10 to 110 Note ----------------1 1 1 1 2 3 ----4 --------------5 8 6 8
852--164111 / A
201
Base version
Data Description Yaw and pitch stabilization mode Maximum starboard coverage in degrees Maximum starboard swath width in m Spare (Always 0) HiLo freqency absorption coefficient ratio End identifier = ETX (Always 03h) Check sum of data between STX and ETX
Format 1U 1U 2U 2U 1U 1U 2U
Valid range --10 to 110 10 to 20000 --00 to 120 -----
Note 7 -------------
Note 1 The system status will by set bits indicate system faults by bit coding (a fault may not necessarily be detrimental to system performance). The Operator Station status byte is used as follows: 1xxx xxxx - No reply from the Processing Unit. The Processing Unit status byte is used as follows: xxxx xxx1 - Communication error with BSP xxxx xx1x - Communication error with Transceiver or Sonar Head xxxx x1xx - Attitude not valid for this ping xxxx 1xxx - Heading not valid for this ping xxx1 xxxx - System clock has not been set since power on xx1x xxxx - External trigger signal not detected x1xx xxxx - Hull unit not responding A set bit in the BSP status byte indicates an internal communication problem. On the EM 2000 and EM 3000 problems with the high speed data uplink are specifically indicated as follows: xxxx xxx1 - EM 2000, EM 3000 and Sonar Head no 1 on the EM 3000D xxx1 xxxx - Sonar Head no 2 on the EM 3000D The BSP status byte is used as follows by the EM 3000: xxxx xxx1 - Ping rejected due to errors in received data on BSP1 xxxx xx1x - Too much seabed image data on BSP1 xxxx x1xx - Invalid command received by BSP1 xxx1 xxxx - Ping rejected due to errors in received data on BSP2 xx1x xxxx - Too much seabed image data on BSP2 x1xx xxxx - Invalid command received by BSP2 The Sonar Head status byte is used as follows by the EM 2000 and EM 3000:
202
852--164111 / A
Datagram formats
xxxx xxx1 - Temperature too high on Sonar Head 1 xxxx xx1x - Data link failure on Sonar Head 1 xxxx x1xx - Voltages out of range on Sonar Head 1 xxx1 xxxx - Temperature too high on Sonar Head 2 of EM 3000D xx1x xxxx - Data link failure on Sonar Head 2 of EM 3000D x1xx xxxx - Voltages out of range on Sonar Head 2 of EM 3000D The Transceiver status byte is used as follows by the EM 120, EM 300 and EM 1002: xxxx xxx1 - Transmit (HV) voltage out of range xxxx xx1x - PSU voltage out of range xxxx x1xx - Internal communication error xxxx 1xxx - Receive channel DC offset(s) out of range xxx1 xxxx - Internal communication error x1xx xxxx - Internal communication error 1xxx xxxx - Defective fuse(s) in transmitter Note 2 The mode identifier byte is used as follows: 0000 0000 - Nearfield (EM 3000) or Very Shallow 0000 0001 - Normal (EM 3000) or Shallow (default for EM 2000) 0000 0010 - Target detect (EM 3000) or Medium 0000 0011 - Deep 0000 0100 - Very deep Note 3 The filter identifier byte is used as follows: xxxx xx00 - Spike filter set to Off xxxx xx01 - Spike filter is set to Weak xxxx xx10 - Spike filter is set to Medium xxxx xx11 - Spike filter is set to Strong xxxx x1xx - Slope filter is on xxxx 1xxx - Sector tracking or Robust Bottom Detection (EM 3000) is on 0xx0 xxxx - Range gates have Normal size 0xx1 xxxx - Range gates are Large 1xx0 xxxx - Range gates are Small xx1x xxxx - Aeration filter is on x1xx xxxx - Interference filter is on
852--164111 / A
203
Base version
Note 4 The used absorption coefficient should be derived from the seabed image or central beams echogram datagram if it is automatically updated with changing depth. Note 5 The sound speed (at the transducer depth) source identifier is used as follows : 0000 0000 - From real time sensor 0000 0001 - Manually entered by operator 0000 0010 - Interpolated from currently used sound speed profile Note 6 The beamspacing identifier is used as follows: 0000 0000 - Determined by beamwidth (FFT beamformer of EM 3000) 0000 0001 - Equidistant 0000 0010 - Equiangle 0000 0011 - Equiangle around nadir, equidistant further out Note 7 The yaw and pitch stabilization identifier is set as follows: xxxx xx00 - No yaw stabilization xxxx xx01 - Yaw stabilization to survey line heading xxxx xx10 - Yaw stabilization to mean vessel heading xxxx xx11 - Yaw stabilization to manually entered heading 1xxx xxxx - Pitch stabilization is on. Note 8 Port swath width and coverage was in earlier versions the sum of port and starboard
Installation parameters
This datagram is an ASCII datagram except for the header which is formed as in all other output datagrams. The datagram is issued as a start datagram when logging is switched on and as a stop datagram when logging is turned off, i.e. at the start and end of a survey line. It may also be sent to a remote port as an information datagram. It is usually followed by a sound speed profile datagram. In the datagram all ASCII fields start with a unique three character identifier followed by =. This should be used when searching for a specific field as the position of a field within the datagram is not guaranteed. The number or character part following is in a variable format with a minus sign and decimal point if needed, and with , as the field delimiter. The format may at any time later be expanded with the addition of new fields at any place in the datagram.
204
852--164111 / A
Datagram formats
For the EM 3000 the transducer 1 data are for the Sonar Head and the transducer 2 data are for the second Sonar Head of an EM 3000D. For other new EM systems with separate transmit and receive transducers, transducer 1 refers to the transmit transducer, and transducer 2 refers to the receive transducer.
Data Description Number of bytes in datagram Start identifier = STX Type of datagram = I or i(nstallation parameters) or r(emote information) Example --Always 02h Start = 049h Stop = 069h Remote info = 70h EM 3000 = 3000 Feb 26, 1995 = 19950226 08:12:51.234 = 29570234 ------WLZ=x.x, SMH=x.x, HUN=x HUT=x.x S1Z=x.x, S1X=x.x, S1Y=x.x, S1H=x.x, S1R=x.x, S1P=x.x, S1N=x--- ---x, S2Z=x.x, S2X=x.x, S2Y=x.x, S2H=x.x, S2R=x.x, S2P=x.x, S2N=x--- ---x, GO1=x.x, GO2=x.x, OBO=x.x FGD=x.x Format 4U 1U 1U Valid range ------Note 1 -----
EM model number Date = year*10000 + month*100 + day Time since midnight in milliseconds Survey line number System serial number Serial number of second sonar head Water line vertical location in m System main head serial number Hull Unit Hull Unit tilt offset Transducer 1 vertical location in m Transducer 1 along location in m Transducer 1 athwart location in m Transducer 1 heading in degrees Transducer 1 roll in degrees re horizontal Transducer 1 pitch in degrees Transducer 1 no of modules Transducer 2 vertical location in m Transducer 2 along location in m Transducer 2 athwart location in m Transducer 2 heading in degrees Transducer 2 roll in degrees re horizontal Transducer 2 pitch in degrees Transducer 2 no of modules System (sonar head 1) gain offset Sonar head 2 gain offset Outer beam offset High/Low Frequency Gain Difference
2U 4U 4U 2U 2U 2U ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII
----0 to 86399999 0 to 65534 100 --100 ----100 --0 or 1 ---------------------------------------
--------------1 -----------------------------------------
852--164111 / A
205
Base version
Data Description Transmitter (sonar head no1) software version Receiver (sonar head 2) software version BSP software version Processing unit software version Operator station software version Datagram format version Depth sensor time delay in millisec Depth sensor offset Depth sensor scale factor Depth sensor heave Active position system number Position system 1 motion compensation Position system 1 time stamp used Position system 1 vertical location in m Position system 1 along location in m Position system 1 athwart location in m Position system 1 time delay in seconds Position system 1 geodetic datum Position system 2 motion compensation Position system 2 time stamp use Position system 2 vertical location in m Position system 2 along location in m Position system 2 athwart location in m Position system 2 time delay in seconds Position system 2 geodetic datum Position system 3 motion compensation Position system 3 time stamp use Position system 3 vertical location in m Position system 3 along location in m Position system 3 athwart location in m Position system 3 time delay in seconds Position system 3 geodetic datum Position system 3 on serial line or Ethernet Motion sensor 1 vertical location in m Motion sensor 1 along location in m Motion sensor 1 athwart location in m Motion sensor 1 roll reference plane Motion sensor 1 time delay in milliseconds Motion sensor 1 roll offset in degrees
Example TSV=c--- ---c, RSV=c--- ---c, BSV=c--- ---c, PSV=c--- ---c, OSV=c--- ---c, DSV=c--- ---c, DSD=x--- ---x, DSO=x.x, DSF=x.x, DSH=aa, APS=x, P1M=x, P1T=x, P1Z=x.x, P1X=x.x, P1Y=x.x, P1D=x.x, P1G=c--- ---c, P2M=x, P2T=x, P2Z=x.x, P2X=x.x, P2Y=x.x, P2D=x.x, P2G=c--- ---c, P3M=x, P3T=x, P3Z=x.x, P3X=x.x, P3Y=x.x, P3D=x.x, P3G=c--- ---c, P3S= x, MSZ=x.x, MSX=x.x, MSY=x.x, MRP=aa, MSD=x--- ---x, MSR=x.x,
Format ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII
Valid range ------------------IN or NI 0 to 2 0 or 1 0 or 1 ----------0 or 1 0 or 1 ----------0 or 1 0 or 1 ----------0 for Ethernet ------HO or RP -----
Note 2 2 2 2 2 2 ------3 7 4 5 ----------4 5 ----------4 5 -------------------------
206
852--164111 / A
Datagram formats
Data Description Motion sensor 1 pitch offset in degrees Motion sensor 1 heading offset in degrees Motion sensor 2 vertical location in m Motion sensor 2 along location in m Motion sensor 2 athwart location in m Motion sensor 2 roll reference plane Motion sensor 2 time delay in milliseconds Motion sensor 2 roll offset in degrees Motion sensor 2 pitch offset in degrees Motion sensor 2 heading offset in degrees Gyrocompass heading offset in degrees Roll scaling factor Transducer depth sound speed source Active heading sensor Active roll sensor Active pitch sensor port no Active heave sensor port no Cartographic projection Responsible operator Survey identifier Survey line identifier (planned line no) Comment Spare byte if required to get even length End identifier = ETX Check sum of data between STX and ETX
Example MSP=x.x, MSG=x.x, NSZ=x.x, NSX=x.x, NSY=x.x, NRP=aa, NSD=x--- ---x, NSR=x.x, NSP=x.x, NSG=x.x, GCG=x.x, MAS=x.x, SHC=x AHS=x, ARO=x, API=x, AHE=x, CPR=aaa, ROP=c--- ---c, SID=c--- ---c, PLL=x--- ---x, COM=c--- ---c, Always 0 if used Always 03h
Format ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII 0---1U 1U 2U
Valid range ----------HO or RP ------------0 or 1 1 to 4 1 to 4 1 to 4 1 to 4 -----------------
Note ----6 6 6 6 6 6 6 6 ----8 -------------------------
Note 1 Serial number of head no 2 if that head is the only one in use with the EM 3000D, otherwise the serial number of head no 1 in the EM 3000D or the only head in the EM 3000. Note 2 A version number is given as 3 alphanumerical fields separated by decimal points, plus date as yymmdd (for example 3.02.11 991124). Note 3 IN = the heave of an underwater vehicle is presumed to be measured by the vehicles depth sensor and the heave sensor input is not used by system. Note 4 1 = the positions are motion compensated 0 = the positions are not motion compensated
852--164111 / A
207
Base version
Note 5 0 = the system has used its own time stamp for the valid time of the positions 1 = the system has used the time stamp of the position input datagram (external time). Note 6 If entries for a second motion sensor are not included although two sensors are being used, they are presumed to have the same parameters. Note 7 Position system number - 1. Note 8 0 = sound speed is taken from manual entry. 1 = sound speed is taken from current profile.
208
852--164111 / A
10 SYSTEM ADMINISTRATION
10.1 Introduction
This chapter provides basic reference information useful for the EM 120 system supvervisor. In order to make the most of the information provided, you may need some basic knowledge of the Unix operating system.
852--164111 / A
209
Base version
10.2 Passwords
EM 120 Installation setup
In order to change the installation parameters on the EM 120 system, you need to enter a password. This password is common for all the operators of the EM 120 system. You will automatically be prompted to enter the password once you select Edit enable in the Edit menu. If a password has not been identified, the first attempt to modify the installation parameters will prompt you to enter a new password. If the password is lost, the current password can be deleted by deleting the following file: $HOME/.eso_system/.esoEM 120_protection No special privileges are required to delete this file. Once it is gone, the system will prompt you for a new password next time you choose Edit enable.
210
852--164111 / A
10.3 EM 120 File system

Introduction
The EM 120 requires a large number of individual files. Some are used for data storage, others for system setup, while some are used to store operator and system configurations. This chapter lists the various file types and provides brief explanations. The notation $<name> is an environment variable, usually specifying a filsystem directory.
The EM 120 supports a dedicated tool for file management. This is described on page NO TAG.
Survey files
During a survey, the EM 120 system will record and store the following file types: Raw data Survey data The information is stored on the Operator Station harddisk on dedicated data formats defined by Kongsberg Simrad..
Survey data
These are the data files generated by the system. Note that files will only be stored if the Survey Format To Disk option is checked in the window opened by Options - > Logging. These files are used by the Kongsberg Simrad postprocessing software, and by the Survey Display program.
Refer to page NO TAG for further information on the Logging parameters.
Note !
Unless this data is stored, the Survey Display application will not work.
Raw data
These are the files containing the raw data retrieved during the survey. These files are the most important files collected during a survey. If you accidentally loose your survey data format files (required by the Kongsberg Simrad postprocessing software), you can recreate these files based on the raw data files. Care should be taken to backup raw data files on a regular basis, using the backup facilities supplied as an integral part of the system.
Sound speed profiles

All the sound speed profiles are stored as separate files in directory specified by the environment variable.
852--164111 / A
211
Base version
$SHAREDHOME The files have extension *.asvp
Absorption coefficient file

The absorption coefficient file contains number pairs of absorption coefficients and corresponding depths. The coefficients are integrated during loading to the echo sounder and the integrated value is used. The file is named absorption.coef and is stored in directory: $SHAREDHOME
Workstation I/O
When you define the use of the Operator Stations serial lines, the setup information is stored in the following file: $HOME/.eso_system/esoSetup.serial
Echo sounder parameters

These are the files determining how the current echo sounder system is set up. The system uses separate files for runtime and installation parameters. Installation setup The installation setup information is saved in the following file: $HOME/.eso_system/esoEM120Setup.installation Every time you save this file, a backup file is generated automatically. This file is named: esoEM120Setup.installation.yyyy_mmdd_hhmm where: yyyy=year mm=month dd=day hh=hour mm=minute.
The installation file can be viewed or printed using the Launchpads Print/View function described on page NO TAG.
You can also save the setup files with other names you choose yourself. You can then pick any name, but you must keep the extension as .installation. The extension is added automatically if you only specify the file name. Runtime setup The runtime setup information is saved in the following file: esoEMEM120Setup.runtime
212
852--164111 / A
Every time you save this file, a backup file is generated automatically. This file is named: $HOME/.eso_system/esoEM120Setup.runtime.yyyy_mmdd_ hhmm where: yyyy=year mm=month dd=day hh=hour mm=minute.
The installation file can be viewed or printed using the Launchpads Print/View function described on page NO TAG.
You can also save the runtime files with other names you choose yourself. You can then pick any name, but you must keep the extension as .runtime. The extension is added automatically if you only specify the file name. Echo sounder status The information in the Status Field in the Launchpad is stored in the following file: $HOME/.eso_system/esoSetup.status IP addresses, ports and datagrams The IP addresses for the various items in the system, the ports used for the various applications, and the datagram distribution are collected in the following file: $HOME/DPC.addresses.<host> where <host> is the name of the Operator Station. You may modify the contents of this file by using the Options - > Datagram subscriptions choices on the Launchpad. The datagrams available are listed in the following file: $HOME/.eso_system/esoSetup.datagrams This is a static file, and will only be used by the system. NMEA 0183 The information for the NMEA 0183 depth serial line is stored in the following file: $HOME/.eso_system/esoSetup.serial
BIST files
When you run the built- in test applications, the results displayed in the output area in the BIST window may be saved to disk. The file is created with the following location and file name:
852--164111 / A
213
Base version
$HOME/.eso_system/BISToutput Every time you save the information, the old file will be replaced. The information is stored in ASCII format.
The BIST function and the corresponding window is explained on page NO TAG.
Logfiles
Each application in the EM 120 system issues report and error messages when required. These messages are collected in logfiles. The size of the current logfile is monitored by the system. If it exceeds 8Mb, a warning dialogue pops up recommending a reset of the file. The actual reset is done using the File- >Reset Logfile option, as instructed in the popup dialogue.
The logfile can be viewed or printed using the Print/View function on the Launchpad described on page NO TAG.
When you reset the logfile using the File - > Reset logfile command on the Launchpad, you may create a backup copy of the logfile. The backup is named: $HOME/.eso_system/esoLogfile.yyyy_mmdd_hhmm where: yyyy=year mm=month dd=day hh=hour mm=minute. In most cases you do not need to create backup copies of the logfile, since errors and warnings are logged to the survey logfiles during active surveying. In addition to this logfile, the errors and warnings issued during a survey are saved on a separate file for the active survey. This file is only created while logging takes place. The file is: $PROCHOM/<survey>/esoLogfile where <survey> is the chosen name for the active survey.
Operator configuration files

These are the individual files containing the operator specified window layouts and desktop workspaces for the programs supervised by the EM 120 Launchpad. Default window layout Each operator can define a preferred window and workspace layout, and then use the Window Layout - > Save Operators Layout command on the launchpads main menu to save this information. The name of the file will be:
214
852--164111 / A
$HOME/.eso_system/esoEmX_config.<operator> where <operator> is the current operator of the system, as defined in the Launchpads Survey field (below the program icons). The default window layout is: $HOME/.eso_system/esoEmX_config List of known operators The list of the operators known to the system is stored in the following file: $HOME/.eso_system/esoSetup.operators User preferences All the preferences you define during the survey are stored in a separate file. $HOME/.eso_system/esoSetup.launchpad This file is created using the Options - > User preferences command on the Launchpads main menu.
Survey jobs
These are the files generated by the Survey Displays Planning module. All these plans are located in the following directory: $SHAREDHOME/<job name>.asciiplan
TOC files
The TOC (Table of Contents) files are created automatically when you select the Generate Tape TOC operation in the File Admin window.
Refer to page NO TAG for a description of the Launchpads File Admin window.
Each TOC file contains a list of oll the files on the tape. This is normally all the files used for a specific survey, but in general it can be any file types recognized by the File Admin utility. The TOC files can be named manually, or they can be assigned a name automatically. This name is then defined based on the curernt date and time with extension *.TOC. The files are stored in the following directory: $HOME/.eso_system/
852--164111 / A
215
Base version
10.4 File formats

Introduction
The main files are described in this chapter, but the header files that follow the system are only referred to and must be inspected by listing the header file of current interest or by checking the computer display.
Survey format and I/O library

The Survey Format (SF) files are the key files of the Kongsberg Simrad workstation systems. The files are located in the $PROCHOME directory. An I/O library from Kongsberg Simrad is supplied to the users who wish to access the data themselves. You can then install the I/O library whereever it fits for your development. Header files and libraries are available. The SF is a Kongsberg Simrad defined format that fits for all Simrad multibeam echo sounder data, and for the Kongsberg Simrad EA 500 and EK 500 single beam echo sounders. The data is converted directly to this format if a Kongsberg Simrad logging system is used. As the lines are run, the raw data is fed into the handleMessage or handleEmX filter and stored correctly on the $PROCHOME/<SurveyName> directory, while the survey.lines file on the same directory is updated with information about the same line.
The survey format

Introduction
This is the Kongsberg Simrad workstation processing format that applies to all multibeam echo sounders and also to some single beam echo sounders. The format is used in other workstation products in addition to Neptune, such as Merlin, Poseidon and Triton. The format is based on indexed files. For each line there is an index file which holds some common index data for each ping. The files handled by the index file are: 1 2 3 Depth file Sonar Image file Classification file
The following files have been defined as system administration files: 4 5 Parameter file sound speed file
216
852--164111 / A
These files contain parameter settings and information about the sound speed that has been used during the data collection. The information about the used sound speed is vital for reprocessing old data with new sound speed profiles. The position files (there might be several due to more than one positioning system) are treated separately. After position processing, a new valid position file is generated and will be used for further processing (Sensor 00), version 02. A representation of the file structure is described by the following: Index file Depth file Position file FileHeadrec FileHeadRec FileHeadrec PingHeadRed DepthFileRec 1 PosHeadRec IndexFileRec 1 DepthFileRec 2 PositionFileRec 1 IndexFileRec 2 ........ PositionFileRec 2 .......... ......... ......... .......... DepthFileRec i ......... IndexFileRec i ......... PositionFileRec i ......... DepthFileRec n ......... IndexFileRec n ......... PositionFileRec n Raw sidescan file FileHeadRec SideHeadRec SideRawFileRec 1 SideRawFileRec 2 ......... ......... SideRawFileRec i ......... SideRawFileRec n Parameter file FileHeadRec ParameterRec 1 ParameterRec 2 ......... ......... ParameterRec i ......... ParameterRec n sound speed file FileheadRec SndVelFileRec 1 SndVelFileRec 2 ......... ......... SndVelFileRec i ......... SndVelFileRec n
Survey format I/O library

The I/O sub- routine library can be used by a company or institution who have bought a license for a Kongsberg Simrad workstation product. It can also be distributed by the Kongsberg Simrad customer to others after agreement between Kongsberg Simrad and the institution or company. Maintenance and help with the library and files are given to those who have maintenance contract with Kongsberg Simrad.
The Survey format coordinate system

The coordinate system of the vessel has an x- axis along the ships keel pointing forwards from the origin of the ship. The y- axis points to starboard, and the z- axis points straight down giving the depths as positive values increasing with depth.
852--164111 / A
217
Base version
This generates the right- hand coordinate system on board the ship. Positive rotation around the axis is defined by the right- hand rule, giving a positive rotation of angles in the horizontal plane in the same way as the gyro rotates positively (Clockwise as seen from above the ship). The data that is logged on files is in latitude/longitude coordinates. The data is represented by a 4- byte integer that has the following resolutions: Latitude: 2*10E7 decimal degrees per number unit (+90 to - 90 degrees). Longitude: 1*10E7 decimal degrees per number unit (+180 to - 180 degrees). Depths are treated with centimetre resolution in the EM 120 system, and represented in this resolution on the XYZ files.
Use of the Kongsberg Simrad I/O library

Introduction The Kongsberg Simrad I/O library consists of two different parts. One part is intended to be used by those who want to fit their own data into Kongsberg Simrads Survey Format (SF) file format. The modules supported for this use are msgSim and handleMessage. The handleMessage takes its input data from the logging program (Mermaid/Merlin) or from msgSim. The other part is intended to be used by those who want to use Survey Format data. This part of the library is called RWlib (Read and Write library). All routines in the library return an integer as return parameter. This parameter is negative if something went wrong or the data returned are not valid. Message simulator The message simulator (msgSim) simulates messages from the logging system by reading one or more raw data files, putting the message length in front of each message and writing it to stdout. If the messages are separated on different data files, the files containing the depth data message must end with .dpt, position data with .pos, sidescan data with .rss and start/stop/parameter data with .inf. The module also handles the situation when all messages are collected in one file. All of these data files must only contain valid, complete messages and nothing else. Message handling Messages from Mermaid/Merlin or msgSim may be piped into handleMessage. This module reads the messages from stdin, decodes them into survey format and writes them to file. The files written are: position files (.pos)
218
852--164111 / A
depth files (.depth) sidescan files (.sidescan) parameter files (.para) sound speed files (.svel) index files (.ind). The name of the new file starts with the line number, an underscore, the date of the start telegram, an underscore, the time, an underscore, sensor number, an underscore, version number and the extension. Example: 0183_19921031_155630_00_01.depth The module starts decoding and writing when a start telegram arrives and stops when a stop telegram arrives. If sidescan data is to be handled, depth data must be present, and if the data is to be used with near real time visualization (i.e. Merlin), position data must also be present. For information on how to run handleMessage, see the section Command references.
Library calls
Introduction The library is written in the ANSI C programming language. The definition and prototyping is done in the *.h files: readWriteFile.h SurveyLines.h newFormat.h The return structures that you need to know about are found in the newFormat.h file. This file is documented internally in the file, while the other *.h files not are intended to be read, just included to supply you with the structures required for some of the calls. These calls are described here, and the prototyping is found in the above listed header files. Writing new files For writing new files in SF the library libRW is supported. With this library you can open, write and close new files in SF. Before a file (of any type) can be written, it must be opened by the appropriate open routine for this file type. The input parameters for these routines are: file directory, generic file name, sensor number (set to 0- >zero) type specific header,
852--164111 / A
219
Base version
a comment and a description of the process which created the file. In addition file handler newFilePnt must be supported for each file (except for opening the index file) and one common write handler. E.g. this write handler is used for writing indices to files. To write new records to file, a set of writing routines are supported. All those writing routines have their specific record format, their file handler (except for writing pings) and the common write handler as parameters. When depth data or sidescan data is written, it must be specified which sounder (port or starboard for dual system or single for single system) the data comes from. To close the file (except the index file which is closed with a specific routine) the routine closeNewFile is called with the file handler as input. All data are written to file in the native format (little or big Endian) in which the program is running. The index file (with ping data) is written every time the ping number changes. This is done automatically in writeDepth or writePing, which means that these routines must be called in order to let the index and ping records be written (ping number must be supplied and properly changed if not present in the raw datagram). Date and time must also be supplied for each record (ping and position) so that it will be possible to index a ping from position through data and time. When the index file is written, all indices are written including those for sidescan and position. As sidescan data only are accessible through the index file, all calls to either writeDepth or writePing must be made. Position data, on the other hand, may either be accessed via index (for near real time) or via time. But in order to make indices for the position data correct, all data must be written in time sequence. The positions are also filtered for coarse jumps (i.e. more than one degree) and flagged accordingly before they are written. Available routines are described in the following paragraphs. Open files
newIndexFile: Open and init index file
(IN: writeHandler, directory, pingHeader, comment, process)

newPosFile: Open and init position file
fileName,
sensor,
(IN: fileHandler, writeHandler, directory, sensor, posHeader, comment, process)

newDepthFile: Open and init depth file
fileName,
(IN: fileHandler, writeHandler, sensor, comment, process)

newSideFile: Open and init sidescan file
directory,
fileName,
(IN: fileHandler, writeHandler, directory, sensor, sideHeader, comment, process)
fileName,
220
852--164111 / A
newSvelFile: Open sound speed file
(IN: fileHandler, writeHandler, sensor, comment, process) (IN: fileHandler, writeHandler, sensor, comment, process) Write files
writePos:-- Write position data to file
directory,
fileName,
newParaFile: Open parameter (start/stop/parameter) file
directory,
fileName,
(IN: fileHandler, writeHandler, positionRecord)

writeDepth: Write depth data to file (and possible also index and ping)
(IN: fileHandler, writeHandler, sounder, depthRecord)

writeSidescan: Write sidescan data to file
(IN: fileHandler, writeHandler, sounder, sidescanRecord)

writePing: Set current ping data, write ping and index data to file
(IN: writeHandler, sounder, pingRecord)

writeSvel: Write sound speed data to file
(IN: fileHandler, writeHandler, soundVelRecord)

writePara: Write parameter data to file
(IN: fileHandler, writeHandler, parameterRecord) Close files

closeNewFile: Close a file
(IN: fileHandler)
closeIndexFile: Write last index/ping to file (if necessary), close index file
(IN: writeHandler)
Reading and updating survey data

For those who only want to read or update data on SF, the library libRW is supplied. With this library you can open, read, copy, update and close the files containing SF data. Before anything can be done with a file, it must be opened by the appropriate opening routine. These routines have the parameters: 1 file mode (r or r+) 2 directory 3 file name 4 sensor number (set to 0) 5 file version number as input In addition a file handler must be supported for each file. For the index file an index handler must also be supported. It is through this index handler that depth, sidescan and (for near real time) position data are accessible. The different opening routines then return some type specific data (e.g. a file header and number of record). To open a file for reading, set file mode to r and for updating set file mode to r+.
852--164111 / A
221
Base version
If the data is written on a machine with little Endian and read on a machine with big Endian format (or vice versa), it is automatically swapped when read, or updated. If the file is copied, then it is always copied to the native format of the machine the program is running on. Note ! Compressed data can not be transferred between little Endian and big Endian machines. Compressed data can not be transferred between little Endian and big Endian machines. The data can be accessed in several different ways. Ping data, position data, sound speed data and parameter data are accessed via an index number which starts at 0 (zero) and goes up to the number of records (minus one) for each file. Depth data and sidescan data are accessed via the file index. This index is set with the setFileIndexno routine. If the depth and sidescan data were produced by a dual echo sounder system, the port and starboard can be accessed via the port and stb parameters; for single echo sounder system, the sing parameter is used. To get an interpolated position for a ping, one must first call the routine initPosInter. This routine incudes an index to the first position and number of positions as input parameters. This is because all indexing on a file within a region is based on the indices from the position file. The routine uses a handler posSearchPnt and returns the first valid ping index and number of indices within the positions. These parameters should then be used in the loop to access the ping, depth and sidescan data. To get a ping with its position the routine getPingPos is used. This uses the parameter indexHandler set by setFileIndexno. You may also specify the maximum legal difference in time and in distance from the ping to the two nearest positions. If you only want ping data at a specific delta distance, this may also be set. If the routine returns with a negative number, no valid position exists for this ping. When finished, freePosInter is called. To update a file, the file must be opened with file mode = r+. Then all the update routines can be used. Access through the index handler to depth and sidescan files must still be used. When the updating is finished, updateHeader must be called to set the right time and process for file updated. If you want to change other data in the files than flags, the file should be copied (with copyFile) before it is updated. The routine copyFile has as input parameter the file handler and the new directory, and it returns the new file version number. To make a new position file from several position files (combine), the general file header must be copied with copyHeader. Then the copied file (header) must be opened with openPosFileAppend and position can be written (in sequence) with updatePostion.
222
852--164111 / A
There are also some convenience routines to update flags for position, ping and depth data. These routines read the data, check if some flags are changed and if so, write the changed data back. Modules that keep original survey data structures in memory, should use the ordinary update routines instead. It is however strongly recommended that you keep track of what flags (e.g. one variable that tells whether some of the depth flags for a ping are changed) that are changed, in order to minimize input/output. When depth flags are updated only those flags which are not equal NaN (Not a Number) are updated. The module does also (for the time being) contain some routines to transform across- and along- data for each beam to either latitude and longitude or to UTM and to calculate the distance between two positions. Supplied routines are described in the following paragraphs. Open files openIndexFile Open index file directory, IN: fileHandler, indexHandler, fileMode, fileName, sensor, versionNumber, OUT: pingHeader, sounderSystem, numbOfPing openPosFile Open position file IN: fileHandler, fileMode, directory, fileName, sensor, versionNumber, OUT: posHeader, numbOfPos openDepthFile Open depth file IN: fileHandler, fileMode, directory, fileName, sensor, versionNumber openSideFile Open sidescan file IN: fileHandler, fileMode, directory, fileName, sensor, versionNumber, OUT: sideHeader openSvelFile Open sound speed file IN: fileHandler, fileMode, directory, fileName, sensor, versionNumber, OUT: numbOfSvel openParaFile Open parameter file IN: fileHandler, fileMode, directory, fileName, sensor, versionNumber, OUT: numbOfPara openPosFileAppend Open position file for append IN: fileHandler, directory, versionNumber, posHeader) fileName, sensor,
852--164111 / A
223
Base version
Reading data setFileIndexno Set index and get ping data IN: fileHandler, indexHandler, pingIndex, OUT: pingRecord getDepth Get depth data stbDepthRecord, IN: fileHandler, indexHandler, OUT: singDepthRecord, portDepthRecord getSidescan Get sidescan data IN: fileHandler, indexHandler, OUT: singSidescanRecord, stbSidescanRecord, portSidescanRecord getPosition Get position data IN: fileHandler, posIndex, OUT: positionRecord getManyPos Convenience positions routine to get many
IN: fileHandler, fromPosIndex, numbOfPos, OUT: positionRecords getSvel Get sound speed data IN: fileHandler, svelIndex, OUT: soundVelRecord getPara Get parameter data IN: fileHandler, paraIndex, OUT: parameterRecord getPosIndDateTime Get position indexes from date and time IN: fileHandler, totNumbOfPos, fromDate, fromTime, toDate, toTime OUT: fromPosIndex, numbOfPos initPosInter Initiate for accessing positions for ping interpolated
IN: positionFileHandler, indexFileHandler, posSearchPnt, posHeader, fromPosIndex, numbOfPos, totalNumbofPing, OUT: fromPingIndex, numbOfPing getPingPos Get ping with interpolated position IN: indexFileHandler, indexHandler, posSearchPnt, pingIndex, deltaDistance, maximumDistance, maximum TimeDifference,
224
852--164111 / A
OUT: pingRecord, positionRecord freePosInter IN: posSearchPnt getManyIndexOUT: indexes getNoPingOUT: getInterPos noPing Interpolate position from time and date Get number of ping in file IN: indexFileHandler, Get noPing pings from fromPing IN: indexFileHandler, fromPing, noPing, Free data for position interpolation
IN: positionFileHandler, indexFileHandler, posHead, maxDist, maxTimeDiff, OUT: newPos getPosList Get position data into position list posHead, fromPos, noPos, IN: positionFileHandler, deltaDist, maxDist, OUT: pingPosList getPingList Get position data into ping list IN: pingHead, posSearch, fromPing, noPing, deltaDist, maxDist, maxTimeDiff, OUT: pingPosList getFromNoOfPing Get fromping and no of pings for pings that are between two valid positions indexFileHandler, fromPos,
IN: positionFileHandler, noPos, totPing, OUT: fromPing, noPing flagPosJump
Mark all position with pos_jump_flag which are outside a given range from the median of the surrounding positions
IN: posHead, noPos, pos, medianFilterType, maxDist Copy file copyFile Copy file
IN: fileHandler, directory, OUT: versionNumber copyHeader Copy general file header IN: fileHandler, directory, OUT: versionNumber Update file updatePing Update ping data and set index
IN: fileHandler, indexhandler, pingIndex, pingRecord
852--164111 / A
225
Base version
updateDepth
Update depth data singDepthRecord,
IN: fileHandler, indexHandler, stbDepthRecord, portDepthRecord updateSidescan Update sidescan data
IN: fileHandler, indexHandler, singSidescanRecord, stbSi descanRecord, portSidescanRecord updatePosition updateHeader Update flags updatePosFlag updatePingFlag updateDepthFlag Update position flag Update ping flag and set index Update depth flag for current index IN: fileHandler, posIndex, positionFlag IN: fileHandler, indexHandler, pingIndex, pingFlag IN: fileHandler, indexHandler, singDepthFlagList, stbDepthFlagList, portDepthFlagList Close file closeFile IN: fileHandler Close a file Update position Update file header after updating file IN: fileHandler, posIndex, positionRecord IN: fileHandler, process, comment
Convenience routines
Some routines has been developed to make life easier for the programmers. These functions are listed below. Transform toLL Transform each beam to latitude and longitude IN: positionRecord, depthRecord, OUT: latLongPositions toUTM Transform each beam to UTM IN: utmSone, positionRecord, posHeader, gyroHeading, depthRecord, OUT: utmPositions getDiffDist Calculate distance between to positions (in centimetres) posHeader, gyroHeading,
IN: fromPositionRecord, toPositionRecord, posHeader
226
852--164111 / A
OUT: distance calcDirection Calculate the direction from one position to another (in milli- degrees)
IN: fromPositionRecord, toPositionRecord, posHeader OUT: direction
Header files
For each file there is a description on what it contains. The documentation is on the header file itself, and the user should consult this file. It is found in the IO library distribution. For each file there is a description on what it contains. The documentation is on the header file itself, and the user should consult this file. It is found in the IO library distribution. readWriteFile.h newFormat.h process.h datum.h cdefine.h general.h Handlers and readWriteFile.c prototypes for
Definition of survey format. Process id. description List of datums Definitions of some C programming definitions used in the programs. Definition of some general structures that are used several places in the code.
SurveyLines library
This file is important for all the processing. It includes all the lines of the survey, and identifies which versions are the most recent. The file is binary and is located on the $PROCHOME/<SurveyName> directory. The file survey.lines is an index of all existing SF data files on current directory. The file current.line identifies the line currently being processed. These two files must be updated by the modules writing or updating SF files. All modules reading SF files get a list of existing survey format files by reading the survey.lines file. The sensors that exists for the different lines are also listed on a specific file. This is the line.sensors file. In addition a file called adm.data contains the sensors of the survey with their name and their id numbers. Writing and updating The following routines are supplied:
int SlAdd ( s110FileType ioFileType /* IN: SL_SURVEY_L or SL_CURRENT_L */
852--164111 / A
227
Base version
char *dir, char *prefix, SlsurveyFileType survFileType int version, ProDescType lastProc )
/* IN: Directory name */ /* IN: File name prefix */ /* IN: SL_POS, SL_INDEX, SL_DEPTH,or SL_SIDESCAN */ /* IN: File version */ /* IN: Process identification */
This function adds a new record to the survey.lines file. If a record for the directory/file name prefix combination of current interest already exists, this record is updated and no new record is added. For current.line SlAdd has the same functionality as for survey.lines, except that when a new record is added, the previous record is deleted.
int SlUpdate ( SlIoFileType ioFileType, char *dir, char *prefix, SlSurveyFileType survFileType int version, ProDescType lastProc ) /* IN: SL_SURVEY_L or SL_CURRENT_L */ /* IN: Directory name */ /* IN: File name prefix */ /* IN: SL_POS, SL_INDEX, SL_DEPTH,or SL_SIDESCAN */ /* IN: File version */ /* IN: Process identification */
This function is equal to the SlAdd function, except that the current directory/file name prefix combination must exist. If the new version number is lower than the version number on the survey.lines file, then the datafiles (.pos, .ind, .depth, or .sidescan) with version number higher than the new version number will be deleted.
int SlDelete( SlIoFileType ioFileType, char *dir, char *prefix, /* IN: SL_SURVEY_L or SL_CURRENT_L */ /* IN: Directory name */ /* IN: File name prefix */
SlSurveyFileType survFileType, /* IN: SL_POS,SL_INDEX,SL_DEPTH, or SL_SIDESCAN */ ProDescType lastPro ) /* IN: Process identification */
228
852--164111 / A
Delete a survey format file by setting the version equal to 0. The record is deleted in the survey.lines file. The datafile (.pos, .ind, .depth, or .sidescan) will be deleted.
int SlDeleteLine( SlIoFileType ioFileType, char *dir, char *prefix, ProDescType lastPro ) /* IN: SL_SURVEY_L or SL_CURRENT_L */ /* IN: Directory name */ /* IN: File name prefix */ /* IN: Process identification */
Deletes all survey format files for a line by setting the versions equal to 0. The datafiles (.pos, .ind, .depth, and .sidescan) will be deleted and the file [<dir>/]<prefix>_00_01.para will be deleted Reading The following functions return information in a SlList structure (See the SurveyLines.h file for information about the structure). The following routines are supplied:
SlList *SlCreateList ( SlIoFileType ioFileType, ) /* IN: SL_SURVEY_L or SL_CURRENT_L */
Function for reading survey.lines and current.line. SlCreateList returns a SlList structure.
int SlUpdateList ( SlIoFileType ioFileType, SlList *ioList ) /* IN: SL_SURVEY_L or SL_CURRENT_L */ /* IN: Pointer to structure from the SlCreateList function */
SlUpdateList updates an existing SlList structure. Use SlCreateList once to create the list. Then call SlUpdateList repeatedly to get information on changes made to the survey.lines or current.line. Header files This is where the programmers can find the definitions of the structures of this library. The actual header files are:
852--164111 / A
229
Base version
SurveyLines.h lineSensors.h
Survey line and current line structures. Structures and line.sensors file. routines for the
Administration file I/O

File format The adm.data file contains the names of the different sensors. The file is an ASCII file named where for each sensor the following data are written: sensor <sensorType1> <N1> <name1> sensor <sensorType2> <N2> <name2> sensor <sensorType1> <N3> <name3> where Nx is the sensor number on the Survey Format files, and namex is the name of the sensor. The sensorTypex is position or depth. This is when more than the usual EM sensor exists. The Merlin logging system will build this file and the survey.lines file automatically, and the default EM sensor is given by: sensor position 0 undefined Reading To read the file, the following routine is called: AdReadAdm ( EvHandler *evHand ) And to fetch the sensors read: AdGetSensors ( int *noSensors, SensorPnt *snrPnt ) Structures and files The structures are defined in the adm.h file.
230
852--164111 / A
10.5 Survey Predefined Files

Introduction
When you define and run a survey, you will always need information describing basic data or setup, such as: projection data user defined colours user defined show/hide settings coastline contours course deviation The Survey Predefined Files function allows you to build a set of templates to hold this kind of information.
File locations
The Survey Predefined Files are located in the $SHAREDHOME directory. In this directory, you can create subdirectories defining specific survey types, where the type can be defined by your own choice. You can for example create sets of files to match specific bottom conditions or geographical locations. The result may be (for example): $SHAREDHOME/Oslofjord/*.* $SHAREDHOME/Mercator_30_degrees/*.* In order to create the file structure, and to copy in the files you wish to use, you need to open a terminal window on your Operator Station and use the standard Unix commands.
Refer to the applicable instruction manual(s) for a description of the terminal window and the Unix commands.
Using the Survey Predefined Files

When you define a new survey using the options on the EM 120 launchpad, you are asked which of the Survey Predefined Files you will use. When you select any of the templates on the list, the files in that directory are copied over to the survey directory on $PROCHOME.
Refer to page NO TAG for a description of the EM 120 launchpad and the functions used to create a new survey.
852--164111 / A
231
Base version
10.6 Projection data

Scope and purpose
This document defines the interfaces and use of the component Projection. The purpose with the document is to describe how the component interfaces with other components, and how the component is to be used.
Projection overview
Each and every survey should have a well defined projection. The Kongsberg Simrad Software will use the defined projection in all geographic displays and in many other programs where a projection is needed. There are three major different ways to define a projection in the Kongsberg Simrad Software: 1 2 You have full access to the library PROJ.4 from USGS. You can give Kongsberg Simrad the source code (in C) to his preferred projection, and make that projection a permanent part of all Kongsberg Simrad Software. You can program your own projections into the shared library (libsharedProj.so) which is used in all Kongsberg Simrad Software. A template of the source code is supplied by Kongsberg Simrad.
It should be noted that Kongsberg Simrad knows nothing about what goes on inside your projection routines. Some of these routines may contain datum transformations which should be known to the system operator.
Projection protocol
You should for each and every survey define your preferred projection. The projection used in a survey is defined in the file $PROCHOME/<survey>/projection.data The first word in the first line defines which projection to use. The file may look like this: 1 2 If the first word is RijksDriehoksnet, the preferred projection for the Netherlands is used. If the first word is utm, a UTM- projection is used. Setting the UTM zone is however a little tricky: utm 0 3 0 3 If the file looks like the above, UTM zone 31 is selected. The number 3 is the longitude.
232
852--164111 / A
3 4
If the first word is sharedlib, the projection from the shared library libsharedProj.so is used If the first word is user_defined, a user defined projection from the USGS PROJ.4 library is used. The file $PROCHOME/<survey>/projection.data may then look like this: user_defined defaultProjections:proj1 This means that the user defined projection using PROJ.4 is found in the file $PROJ_LIB/defaultsProjections and that the setup for the projection is taken from <proj1>. The file $PROJ_LIB/defaultsProjections may look like this: (which is standard PROJ.4, ref. [1], [2] and [3]): <proj1> proj=stere x_0=155000 y_0=463000 k=0.9996 lat_0=52.156160556 lon_o=5.387638889 <proj2> proj=utm zone=31
If the first word is GK_AUSTRIA, the preferred projection for Austria is selected. There are 16 parameters which controls this projection and they are all kept in the same file. These 16 parameters must be in the specified order in the file, the rest of the file is comments. As we can see this projection performs a datum transformation from WGS 84 to Bessel (Europe) prior to the projection. The projection itself is a Gauss- Krger. $PROCHOME/<survey>/projection.data may look like this: GK_AUSTRIA -563.9 -82.3 -463.4 4.47 4.85 1.88 4.46 6377397.155 299.15281285 16.333333333333 6378137.0 298.257223563 0
852--164111 / A
233
Base version
-5000000 500 ! Line1: GK_AUSTRIA tells Simrad Software ! to use Gauss-Kruger for Austria. ! Transformationsparameter ! fr die Umwandlung von WGS84-Koordinaten ! nach Gauss-Krger-Koordinaten bezogen ! auf das Datum MGI ! Zeile 1: Translation in x [m] ! Zeile 2: Translation in y [m] ! Zeile 3: Translation in z [m] ! Zeile 4: Mastab ! Zeile 5: Rotation in x [] ! Zeile 6: Rotation in y [] ! Zeile 7: Rotation in z [] ! Zeile 8: groe Halbachse [m] ! Nutzersystem (z.B. Bessel) ! Zeile 9: Abplattung Nutzersystem ! (z.B. Bessel) ! Zeile 10: Zentralmeridian Nutzersystem ! (z.B. Bessel) ! Zeile 11: groe Halbachse [m] WGS84 ! Zeile 12: Abplattung WGS84 ! Zeile 13: Zuschlag Rechtswert ! Zeile 14: Zuschlag Hochwert ! Last line: Fixed height used in ! projections.
Notes
The setup of the projection is quite important to do right which means that this should be done by qualified persons only. In the Neptune/Survey Display system it is possible to set up default surveys that you can use as templates for new surveys. These default surveys can then be set up with the correct projections and given names which makes it easy for the operator to choose a default survey of the correct type. There is already a file $PROJ_LIB/defaultsProjections which is in use if some of the standard default surveys are used.
234
852--164111 / A
10.7 Dynamic Projection Library

Introduction
The purpose is to describe how the component interfaces with other components and how the component is to be used.
Overview
There need to be defined a shared library where the customer can implement his own projection routines to use with Kongsberg Simrads Graphic System. This shared library will then be a permanent part of all graphic windows.
Dynamic projection library definitions

In the graphic system today you can set projection and some projection parameters in the file $PROCHOME/<survey>/projection.data. This file will also be used when you specify that projections shall be taken from the shared library libsharedProj.so. The shared library for customer defined projections, libsharedProj.so, must be put somewhere where the loader will find it at startup, /usr/lib/libsharedProj.so.
Dynamic projection library protocol

When you wish to use a projection defined in the shared library, the first line in the file $PROCHOME/<survey>/projection.data must look like this: sharedlib 5 The number (here: 5) is defined by you. When the program (i.e. Survey, Merlin, GridDisplay) starts, it will look for the file $PROCHOME/<survey>/projection.data. When it finds the word sharedlib as the first word in the file, the next word is read as an integer which identifies which projection will be used. The initUserProjection routine is then called with this number as a parameter. This enables you to do additional initialisation to the projection. Since only the first line in $PROCHOME/ <survey>/projection.data is used by the system, you can freely use the rest of this file for additional parameters to be read at startup time. Each and every projection should be associated with a name. This name will appear when you wish to plot something on a plotter. For Kongsberg Simrads Graphic System to get this name, you must supply a routine getUserProjectionName which also has the number as an input parameter and returns a string with the name to be used for the projection.
852--164111 / A
235
Base version
When Kongsberg Simrads Graphic System is set up to use projection routines from the shared library libsharedProj.so, it will do so by calling two routines. The routine used for projection is userProjectionLatLongToNorthEast, and the routine used for the reverse projection is userProjectionNorthEastToLatLong.
Example
This is an example of how the codes for initUserProjection getUserProjectionName userProjectionLatLongToNorthEast userProjectionNorthEastToLatLong should look like: /* **FILEHEADER** ** $Id: dummyRoutines.c,v 1.1.1.1 ** 1997/01/23 08:45:44 tp Exp $ ** ** Filename: dummyRoutines.c ** Date of creation: 23 Jan 1997 ** Creator: Terje Pedersen ** Purpose: Dummy-routines for the shared ** library libsharedProj.so ** which can be changed by the customer. ** Copyright: Kongsberg Simrad AS ** **_FILEHEADER */ #include <stdlib.h> /*calloc-function*/ #include <string.h> /*memcpy-function*/ /* **S*************************************** * Routine: * initUserProjection * Purpose: * Initialize the users preferred * projection. The programmer has access to * the file projection.data in current * directory which the user controls. * Parameters: * int userProjectionNumber (input) * This is the number found in * projection.data * where the first line looks like this:
236
852--164111 / A
* sharedlib 4 * In this case userProjectionNumber will be * 4. * Return values: * 0 on success, -1 on error. * References: * The Component Interface * Doucument: Neptune/UserProjections. * Changes: * **_S** **********************************/ int initUserProjection(int userProjectionNumber) { switch (userProjectionNumber){ case 1: break; default: return -1; }/*switch*/ return 0; }/*initUserProjection*/ /* **S**************************************** * Routine: * getUserProjectionName * Purpose: * Get the name to display in the * menus for this user projection. * Parameters: * int userProjectionNumber (input): * This is the number found in * projection.data * where the first line looks like this: * sharedlib 4 * In this case userProjectionNumber will * be 4. * Return values: * A dynamically allocated character array * containing the name of the projection to * use. On error NULL is returned. * References: * The Component Interface Doucument: * Neptune/UserProjections.
852--164111 / A
237
Base version
* Changes: * **_S** ************************************/ char *getUserProjectionName(int userProjectionNumber) { char *p; if ((p = calloc(20,sizeof(char)))==NULL) return NULL; switch (userProjectionNumber){ case 1: memcpy(p,User Projection 1,18); break; default: free(p); return NULL; }/*switch*/ return p; }/*getUserProjectionName*/ /* **S** ************************************* * Routine: * userProjectionLatLongToNorthEast * Purpose: * This routine is called to get the * projection coordinates from the * geographic coordinates. * Parameters: * int userProjectionNumber (input): * See initUserProjection. * double latitude, double longitude (input): * latitude and longitude in decimal * degrees. * double *north, double *east (input/output): * pointers to doubles where to store the * projection coordinates north and east * (in meters). * Return values: * 0 on success, -1 on error. * References: * The Component Interface Doucument: * Neptune/UserProjections. * Changes: * **_S** ************************************/
238
852--164111 / A
int userProjectionLatLongToNorthEast(int userProjectionNumber, double latitude, double longitude, double *north, double *east) { if (north == NULL || east == NULL) return -1; switch (userProjectionNumber){ case 1: break; default: return -1; }/*switch*/ return 0; }/*userProjectionLatLongToNorthEast*/ /* **S** ************************************* * Routine: * userProjectionNorthEastToLatLong * Purpose: * This routine is called to get the * geographic coordinates from the * projection coordinates. * Parameters: * int userProjectionNumber (input): * See initUserProjection. * double north, double east (input): * Projection coordinates (meters) * double *latitude, double *longitude * (input/output): * Pointers to doubles where to store the * geographic coordinates latitude and * longitude (desimal degrees). * Return values: * 0 on success, -1 on error. * References: * The Component Interface Doucument: * Neptune/UserProjections. * Changes: * **_S** ************************************/ int userProjectionNorthEastToLatLong(int userProjectionNumber, double north, double east,
852--164111 / A
239
Base version
double *latitude, double *longitude) { if (latitude == NULL || longitude == NULL) return -1; switch (userProjectionNumber){ case 1: break; default: return -1; }/*switch*/ return 0; }/*userProjectionNorthEastToLatLong*/ The makefile on a DEC OSF1 UNIX workstation looks like this: # $Id: Makefile,v 1.1 1997/01/23 11:12:07 tp Exp $ # Makefile to create libsharedProj.so. # # 23 Jan 1997, Terje Pedersen # # Copyright: Kongsberg Simrad AS # # .PHONY:install lib clean CC=cc LD=ld LDFLAGS=-shared -no_archive INSTALL=/usr/local/lib dummyRoutines.o: dummyRoutines.c @$(CC) -c $< lib: dummyRoutines.o @$(LD) $(LDFLAGS) -o libsharedProj.so dummyRoutines.o -lc install: lib @cp libsharedProj.so $(INSTALL)/libsharedProj.so @cp dummyRoutines.h $(NEPTUNEHOME)/include/simrad/. @ls -l $(INSTALL)/libsharedProj.so
240
852--164111 / A
@ls -l $(NEPTUNEHOME)/include/simrad/dummyRoutines.h clean: @rm dummyRoutines.o libsharedProj.so The makefile is probably very similar on other platforms.
Notes
There are some restrictions on shared libraries on every platform. You should be aware of this. When upgrading Kongsberg Simrad Software the customers shared library should be reinstalled to make sure it is the one being used. You are encouraged to use the initialisation routine to test that the projection is working. Heights are not used in Kongsberg Simrads Graphic system. It is not necessary in the projections since the height varies very little within one survey that a fixed height will suffice. This can be a parameter in $PROCHOME/<survey>/projection.data that you can read at startup time and use in the projections internally.
852--164111 / A
241
Base version
11 SPARE PARTS
11.1 Overview
This chapter contains an illustrated presentation of the spare parts available for the EM 120 multibeam echo sounder. All the parts are not listed her, only those defined as line replaceable units (LRU) to be changed by the onboard maintenance personnel.
11.2 Spares data presentation

Spares table
The parts are presented in a table format (5008) specified by the Royal Norwegian Navy. An example is shown below.
10 SNo 11 Drawing ref 12 Other ref. 24 Date 1 Fig.1 -05.03.97 Fig.1 05.03.97 13 Prod.p.no 14 TM part.no 17 NATO No 290--085827 --299--049179 --Powec Power Supply PMP 4M.02 Fan Drawer Assembly 15 Article name 16 Technical data 18 Price 19 TM code 23 Status ------21 Unit 26 Userspares 20 Comp EA 0 C EA 0 C 22 Quantity 27 Base spares 25 Ser.no. 1 0 N/A 3 0 N/A
The parts information in this table also conforms to the civilian standard NS 5820 specified by the Norwegian Standardisation Society (Norges Standardiserings Forbund).
242
852--164111 / A
Spare parts
Parts list codes

These are the code descriptions for the information in the table.
Key codes to the parts list

No 10 11 12 13 14 Caption Serial no. Drawing no. & item no. Other references Producers part no. True manufacturers part no. Article name Technical data NATO catalogue no. Currency/unit price True manufacturers code Component Row number in list. The number of the drawing, and the position on that drawing, of the part. Any other applicable references are included here. The part number to be used when ordering spares from Kongsberg Simrad AS. Part number designated by manufacturer of part. Will be same as (13) if part is manufactured or assembled by Kongsberg Simrad AS. The name of the unit or part. Any additional technical information which may be relevant. The NATO stock number will be added where appropriate. Price of the part, and the applicable currency This is a code number to identify the suppliers of the parts to enableyou to order directly from the suppliers in an emergency. Component definition. C = a component which cannot be broken down into smaller units. P = a part which may contain separately replaceable components. S = a set of parts. The SI units applicable to the component. E.G. m = metric units for bolts etc. The total number of that particular part included in the system. Code for use by the Navy. Will be completed by the Navy This is the date the row was last updated. The component serial number where applicable. The suggested number of spares to be held by the user. The suggested number of spares to be held at the users home base. Description
15 16 17 18 19
20
21 22 23 24 25 26 27
Unit Quantity Status Date Serial number User spares Spares at base
852--164111 / A
243
Base version
11.3 Transceiver Unit

Overview
The line replaceable units in the EM 120 Transceiver Unit are: Circuit boards Capacitor battery Power supplies Fan drawers
244
852--164111 / A
Spare parts
Processing Rack
The spare parts in The Processing Rack are those circuit boards used in the chassis.
ROM Card (382-213300) Processor Board (719-087001) BSP1 (382-112392) Circuit breaker
Slot 10 Slot 9 Slot 8 Slot 7 Slot 6 Slot 5 Slot 4 Slot 3 Slot 2 Slot 1 P5 P1 P7 P5 P1 P7
(CD5344D / 860-213008/B)
Serial card (719-097239)
Ethernet adapter (719-087003)
BSP2 (382-112392)
Fan (129-096870)
Figure 50 - Processing Rack spares

SNo Drawing ref Other ref. Date 1 Fig.50 -24.02.00 Fig.50 24.02.00 3 Fig.50 24.02.00 4 Fig.50 24.02.00 5 Fig.50 24.02.00 6 Fig.50 24.02.00 Prod.p.no TM part.no NATO No 382--213300 --719--087001 --382--112392 --719--087002* 719--097239 -719--087003 --129--096870 --Article name Technical data Other information ROM Card Price TM code Status ------------------Unit Userspares Comp EA 1 C EA 0 C EA 0 C EA 0 C EA 0 C EA 0 C Quantity Base spares Ser.no. 1 0 N/A 1 0 N/A 2 1 N/A 1 1 N/A 1 1 N/A 2 1 N/A
Processor Board Commercial item Beamformer & Signal Processor
Serial card Commercial item Ethernet Adapter Commercial item Fan, axial, 12 Vdc Commercial item
Note !
SNo 4: Part.no 719- 087002 is being replaced with part.no 719- 097239.
852--164111 / A
245
Base version
Vorsicht! Spannung Attention Danger
(CD5403C / 861-212871/A)
Power supply HN5-9/OVP-A (290-086216)
Power supply OLD-12/15BB (290-087850)
Figure 51 - Processing Rack spares - power supplies

10 SNo 11 Drawing ref 12 Other ref. 24 Date 1 Fig.51 -24.02.00 Fig.51 24.02.00 13 Prod.p.no 14 TM part.no 17 NATO No 290--086216 --290--087850 --Power supply HN5--9/OVP--A Commercial item Power supply OLD--12/15BB Commercial item 15 Article name 16 Technical data 18 Price 19 TM code 23 Status ------21 Unit 26 Userspares 20 Comp EA 0 C EA 0 C 22 Quantity 27 Base spares 25 Ser.no. 1 1 N/A 1 1 N/A
246
852--164111 / A
Spare parts
Receiver Rack
The following spare parts are those circuit boards and power 52supplies used in the Receiver Rack.
Transmitter/Receiver Boards (382-213019)
High voltage power supply (290-213160)
Capacitor bank (299-113105)
SIMRAD
7.5V ANALOG REF POWER 7.5V SUPPLY 5VA 5VA 5V 12V SWITCHED 12V POWER 24V SUPPLY GND
L204
VCC
F203
-10db
L203
HALT OVER- VOLTAGE VCC2
SERVICE OFF NORMAL ON/OFF RELAY S202
KONGSBERG SIMRAD
HIGH MIDDLE LOW VREF
HV-POWER UNIT 290 -213160

16 A 16 A
24V REF
24V STAND BY
CHG.
SLOW BLOW
L202
50
100
150
F201 8A SLOW BLOW
F202 8A
V
-20db
BLEED
VBB
L201 MAINS INPUT 115/230V AC
CAUTION
DO NOT PULL OUT THIS UNIT BEFORE THE METER SHOWS ZERO ( 0 ) VOLTAGE FOR CONTINUED PROTECTION AGAINST RISK OF FIRE REPLACE ONLY WITH SAME TYPE AND RATING OF FUSE.
S 201 230V AC
P201
(CD5391D / 860-213008/A)
Low voltage power supply (290-112750)
Signal Processor Board (SPBRX) (382-213144)
Figure 53 - Receiver Rack spares
SNo
Drawing ref Other ref. Date
Prod.p.no TM part.no NATO No 382--213019 --290--112750 --290--213160 --382--213144 --299--113105 ---
Article name Technical data Other information Transmitter / Receiver Board
Price TM code Status ----------------
Unit Userspares Comp EA 0 C EA 0 C EA 0 C EA 0 C EA 0 C
Quantity Base spares Ser.no. 4 1 N/A 1 1 N/A 1 1 N/A 1 1 N/A 1 1 N/A
Fig.52 -16.06.00 Fig.52 -16.06.00 Fig.52 -16.06.00 Fig.52 -16.06.00 Fig.52 -16.06.00
Low Voltage Power Supply
Signal Processor Board RX
Capacitor Bank
852--164111 / A
247
Base version
SNo
Drawing ref Other ref. Date
Prod.p.no TM part.no NATO No
Article name Technical data Other information
Price TM code Status
Unit Userspares Comp
Quantity Base spares Ser.no.
64-Channel Transmitter Boards (64CHTX) (382-134512)
(CD4472H/210132A)
Signal Processor Board TX (SPBTX) (382-213289)
Figure 54 - Transmitter Rack spares

SNo Drawing ref Other ref. Date 1 Fig.54 -16.06.00 Fig.54 -16.06.00 Prod.p.no TM part.no NATO No 382--213289 --382--134512 --Article name Technical data Other information Signal Processor Board TX Price TM code Status ------Unit Userspares Comp EA 0 C EA 0 C Quantity Base spares Ser.no. 1 1 N/A 1 1 N/A
64--Channel Transmitter Board
248
852--164111 / A
Drawing file
12 DRAWING FILE
12.1 Introduction
This chapter holds the drawings referenced to in the other sections of the manual. Note that these drawings are not available in the electronic copy of this manual. The original drawings are available in electronic format (AutoCAD) upon request.
12.2 Drawing list

The following drawings are included: 824- 113216 (Rev. A) Power supply 290- 112750 (page 250) 830- 211291 (Rev. A) Transceiver Unit, outline dimesions (page 251) 211292 (Rev. A) Transceiver Unit, outline dimesions (page 253) 830- 213111(Rev. A) TX Junction Box, outline dimesions (page 254) 860- 213297 (Rev. A) Preamplifier - Transceiver connection cables (page 255)
852--164111 / A
249
Base version
MAP 55-1024M Stand by Power + + 24Vdc 115/230Vac N L GND GR GR BK BK A+ 21 LP201 LP202 P201 5 WH 3 1 BK F202 8A F201 8A GR P1 d22+ BK K201 A22 6 4 2 Map 55-4001 GN GN BK WH YE Note: Fuse F203 is a thermostat fuse inside the transformer T201 YE F203 YE Mains filter BL BN T201 1F YE BK 230V GN BN R BL WH O GR P2 z24 GND P2 z32 Ships ground P2 z28 Ships ground NTC 22 L 115/230Vac N GND BL BL GR GR BK BK R R P2 z4 P2 d6 LP203 S202 Service Off Normal 24Vdc P1 d26- Stand by
VIO BL GN WH BK
On/off from remote P1 z32 Heater P1 z28 P1 d30 Fans P2 d26 115/230 Vac to high voltage P2 d30 power
N 115/230Vac L Ships ground
WH
BK YE
+12V
P2 z8 P2 d10 -12V P2 z12 P2 d14 +24V P2 z16 P2 d18 GND P2 z20 P2 d22 +5V
AC + R AC WH
P1 z4 + P1 d6 -
8V for Receiver
S201 115V LP204
AC + BK AC BL
P1 d10 + P1 z8 -
8V for Receiver
Page 1 of 1 (Cd5483)
Power supply 290-112750
824-113216
Rev.A
250
852--164111 / A
Drawing file
Page 1 of 2 (CD5646)
Transceiver Unit, outline dimensions
830-211291
Rev.A
852--164111 / A
251
Base version
Transceiver Unit, outline dimensions
830-211291
Rev.A
252
852--164111 / A
Drawing file
(CD5647)
Page 1 of 1 (CD5647B)
Transceiver Unit, EM300
830-211292
Rev.A
852--164111 / A
253
Base version
Weight: Approx 15.5 kg All measurements in mm.

TX Junction Box, outline dimensions
830-213111
Rev.B
254
852--164111 / A
Drawing file
370-087569 D-Sub connector, 50-pin 379-087571 Cover for D-sub connector A-A pin 1 50P-MALE A 5010
110
RX 3 8 0 - 2 1 3 2 9 6
649-021724 Heat-shrinkable tubing 642-087565 Signal cable 16x2x0.5mm2
Total cutting length, cable : 5100 10
5010
110
RX 3 8 0 - 2 1 3 2 9 6
Check : Wire identification, check pin no. vs pin no.
Apply a label to the cable marked with module type (TX), and the cable registration number (both ends). Use Brother P-Touch 8000 marking machine, black text / yellow background, 12mm.
Page 1 of 2 (CD5342A)
Preamplifier - Transceiver connection cables
860-213297
Rev.A
852--164111 / A
255
Base version
Cutting length 32-39 mm, see table 1.
~15
Attach the screen leader with adhesive copper tape. Cut the aluminium screen similar to the outer insulation.
629-087129 Shielding foil tape 3M 1183 19 mm 379-087570 Crimping connector 2.5

Pin Pin Pin Pin Pin Pin Pin Pin Pin Pin Pin Pin Pin Pin Pin Pin Pin Pin Pin Pin Pin Pin Pin Pin Pin Pin Pin Pin Pin Pin Pin Pin 2 35 3 36 4 37 5 38 6 39 7 40 8 41 9 42 10 43 11 44 12 45 13 46 14 47 15 48 16 49 17 50
Pair 16 Pair 15 Pair 14 Pair 13 Pair 12 Pair 11 Pair 10 Pair 9 Pair 8 Pair 7 Pair 6 Pair 5 Pair 4 Pair 3 Pair 2 Pair 1
Wh Bk Wh Bk Wh Bk Wh Bk Wh Bk Wh Bk Wh Bk Wh Bk Wh Bk Wh Bk Wh Bk Wh Bk Wh Bk Wh Bk Wh Bk Wh Bk
Pair No. 1,2,15,16 3,14 4,5,12,13 6,7,10,11 8,9
Extractor: Amp no. 0-0091285-1 Pliers: Amp no. 169424-1
: Not in use
Connect the cable 1:1

1 18 2 19 3 20 4 21 5 22 6 23 7 24 8 25 9 26 10 27 11 28 12 29 13 30 14 31 15 32 16 33 17 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34
The cable side of the plug. (The same mounting for both plugs.)
Table 1. Pin number 2,3,16,17,35,36,49,50 4,15,37,48, 5,6,13,14,38,39,46,47 7,8,11,12,40,41,44,45 9,10,42,43 Length 39 37.5 36 34 32
Page 2 of 2 (CD5342B)
Preamplifier - Transceiver connection cables
860-213297
Rev.A
256
852--164111 / A
Maintenance manual
Blank page
852--164111 / A
257
Kongsberg Simrad EM 120 Maintenance manual / Base version

EM120 Multibeam Echo Sounder Maintenance Manual Rev A

Uploaded by

Copyright:

Available Formats

EM120 Multibeam Echo Sounder Maintenance Manual Rev A

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

EM120 Multibeam Echo Sounder Maintenance Manual Rev A

Uploaded by

Copyright:

Available Formats

Maintenance manual

EM120 Multibeam echo sounder

EM 120 Multibeam echo sounder

852-164111 / AA000 / 2-24

Cable layout and interconnections

Kongsberg Simrad EM 120 Multibeam echo sounder

Kongsberg Simrad EM 120 Multibeam echo sounder

CABLE LAYOUT AND INTERCONNECTIONS . . . . . . . . . . . . . . . . . . .

Kongsberg Simrad EM 120 Multibeam echo sounder

Transmitter Backplane (TXBP) . . . . . . . . . . . . . . . . . . . . . . . . . .

REPLACEMENT PROCEDURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

DATAGRAM FORMATS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Kongsberg Simrad EM 120 Multibeam echo sounder

Single beam echo sounder depth . . . . . . . . . . . . . . . . . . . . . . . . . Runtime parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SYSTEM ADMINISTRATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

SPARE PARTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

DRAWING FILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Kongsberg Simrad EM 120 Multibeam echo sounder

Rev A B C D Original issue.

High voltage safety warning

NEVER WORK ALONE ON HIGH-VOLTAGE EQUIPMENT!

FIRST AID IN THE EVENT OF ELECTRIC SHOCK

Kongsberg Simrad EM 120 Multibeam echo sounder

DO YOU KNOW WHAT TO DO?

COMBINING EMC AND ARTIFICIAL RESPIRATION

This maintenance manual is prepared for the intermediate level.

Kongsberg Simrad EM 120 Multibeam echo sounder

Sub Bottom Profiler Transceiver Unit (Option)

TX Junction Box no.1

TX Junction Box no.2

Receive transducer array Transmit transducer array

Figure 1 - System diagram

Kongsberg Simrad EM 120 Multibeam echo sounder

Note about changing AC supply voltage

List of units and main subunits

Kongsberg Simrad EM 120 Multibeam echo sounder

Height Width Depth Weight Operator Station

440 mm 500 mm 303 mm 15.5 kg

Kongsberg Simrad EM 120 Multibeam echo sounder

Restrictions for use - limitations No specific restrictions apply.

Operating and storage temperature

System performance data

Depth range from transducers 20 to 11000 m

Cable layout and interconnections

CABLE LAYOUT AND INTERCONNECTIONS

Kongsberg Simrad EM 120 Multibeam echo sounder

Shipyard and system cables

Cable layout and interconnections

C10 (W301) AC power

External tape storage

C11 (W301) AC power C8 (W301) AC power C1 (W502) Display C9 (W301) AC power

C4 (W501) SCSI cable

Mouse or other pointing device

C13 (W301) AC power

Postscript laser printer (option)

Kongsberg Simrad EM 120 Multibeam echo sounder

C18 (W105) (optional)

EM120 Transceiver Unit

TX Junction Box no.1

TX Junction Box no.2