Simrad argus Installation And Service Manual

Page 1
ENGLISH
ARGUS RADAR SYSTEM
Installation & Service Manual
navico-commercial.com
Page 2
Page 3
RECORD OF CHANGES
Part number/Rev.
Date
Purpose of change
Requested by
988-10187-001 September 2011 First issue
988-10187-002 December 2013 Software release 3.2 M. Carmagnini
988-10187-003 October 2014 Software release 3.2.5 M. Carmagnini
988-10187-004 October 2016 Software release 3.3.2 M. Carmagnini
MANUAL TABLE OF CONTENTS
Warnings Chapter 1 INSTALLATION AND SETTINGS Chapter 2 SERIAL INTERFACE SPECIFICATIONS Chapter 3 RADAR CONFIGURATION Chapter 4 DEBUG AND SIMULATION FACILITIES Chapter 5 TROUBLESHOOTING Chapter 6 Annex A Chapter 7 Annex B Chapter 8 Annex c
Page 4
TABLE OF CONTENTS
CHAPTER 1 Installation and settingS ..................................................................... 1.1
1.1 GUIDELINES FOR THE INSTALLATION OF SHIPBORNE RADAR EQUIPMENT .................... 1.1
1.2 INTERFERENCE ...................................................................................................................... 1.1
1.2.1 Location relative to masts, funnels and other constructions ........................... 1.1
1.2.2 Blind sectors and range ........................................................................................... 1.2
1.2.3 Interaction with sea and false echoes ...................................................................... 1.3
1.2.4 Cables and grounding ............................................................................................. 1.3
1.2.5 Radar controls and display ...................................................................................... 1.4
1.3 SYSTEM SPECIFICATIONS ..................................................................................................... 1.5
1.3.1 Dimension and Weight ............................................................................................. 1.5
1.3.2 Power ....................................................................................................................... 1.5
1.3.3 Environmental Data ................................................................................................ 1.5
1.4 INPUT/OUTPUT REQUIREMENTS .......................................................................................... 1.6
1.5 ANALOGUE GYRO COMPASS (SYNCHRO OR STEPPER) .................................................... 1.7
1.6 SERIAL GYRO ....................................................................................................................... 1.10
1.7 SPEED LOG ........................................................................................................................... 1.10
1.8 EPFS ...................................................................................................................................... 1.11
1.9 AIS ......................................................................................................................................... 1.11
1.10 BAM ...................................................................................................................................... 1.11
1.11 VDR CONNECTION .............................................................................................................. 1.12
1.12 RADAR CONSOLE FAILURE OUTPUT ................................................................................. 1.13
1.13 CONFIGURATION LINKS TABLE ......................................................................................... 1.13
1.13.1 Antares PCB Links: ............................................................................................... 1.13
1.13.2 Alpha PCB Links: .................................................................................................. 1.13
1.13.3 Alpha Expansion PCB Links: ................................................................................ 1.15
CHAPTER 2 SERIAL INTERFACE SPECIFICATIONS ............................................. 2.1
2.1 SERIAL LINE 1, HEADING ...................................................................................................... 2.1
2.2 SERIAL LINE 2, AIS ................................................................................................................ 2.3
2.3 SERIAL LINE 3, EPFS - GPS ................................................................................................. 2.10
2.4 SERIAL LINE 4 ...................................................................................................................... 2.28
2.5 SERIAL LINE 5 ...................................................................................................................... 2.30
2.6 SERIAL LINE 6 ...................................................................................................................... 2.31
2.7 SERIAL LINE 7 ...................................................................................................................... 2.32
2.8 SERIAL LINE 8 ...................................................................................................................... 2.33
CHAPTER 3 RADAR CONFIGURATION .................................................................. 3.1
3.1 HOW TO ACCESS THE RADAR CONFIGURATION ................................................................. 3.1
3.1.1 Radar Configuration................................................................................................ 3.1
3.2 GYROCOMPASS CONFIGURATION ........................................................................................ 3.3
3.3 SPEED LOG CONFIGURATION .............................................................................................. 3.5
3.4 OWN SHIP DIM. AND WEIGHT .............................................................................................. 3.6
3.5 CONNING AND EPFS POS. CONFIGURATION MENU ........................................................... 3.7
3.6 UNCONVENTIONAL SENSOR CFG. ........................................................................................ 3.8
3.7 ANTENNA SETTINGS .............................................................................................................. 3.9
3.7.1 Adjustment of Azimuth Type (PPR Selection) ........................................................ 3.10
3.7.2 Adjustment of the heading line .............................................................................. 3.11
3.8 TXRX SETTINGS .................................................................................................................. 3.12
3.8.1 Transceiver Communication Type ......................................................................... 3.13
3.8.2 Transceiver Communication Type ......................................................................... 3.13
3.8.3 Performance Monitor Adjustment ......................................................................... 3.14
3.8.4 Tuning Adjustment ................................................................................................. 3.15
3.8.5 Magnetron timer reset ........................................................................................... 3.15
3.8.6 Digital potentiometers reset................................................................................... 3.15
3.9 VIDEO TRIGGER ADJUSTMENTS ......................................................................................... 3.16
3.9.1 Video Adjust Mode................................................................................................. 3.17
3.9.2 Adopted communication configurations ................................................................ 3.17
Page 5
3.9.3 Trigger Delay ........................................................................................................ 3.18
3.9.4 QV (Quantized Video) Threshold .......................................................................... 3.19
3.10 SECTOR BLANKING ............................................................................................................. 3.19
3.11 SYSTEM CONFIGURATION .................................................................................................. 3.21
3.11.1 Display settings (Fig 3.11.1 -A) ............................................................................ 3.21
3.11.2 IP Address (Fig 3.11.1 -B) .................................................................................... 3.24
3.11.3 MAC Address (Fig 3.11.1 -C) ............................................................................... 3.25
3.11.4 TXRX Associated by Default (Fig 3.11.1 – D) ....................................................... 3.25
3.11.5 General info (Fig 3.11.1 – E) ................................................................................ 3.25
3.11.6 Additional Functions (Fig 3.11.1 – F) ................................................................... 3.26
3.12 RESTART BUTTON ................................................................................................................ 3.27
3.13 USB MENU (FIG 3.1.2-N) ..................................................................................................... 3.28
3.13.1 Save Screenshots.................................................................................................... 3.30
3.13.2 Saving and reloading maps ................................................................................... 3.30
3.13.3 File configuration .................................................................................................. 3.31
3.13.4 System log files ...................................................................................................... 3.31
3.14 STORED PARAMETERS ........................................................................................................ 3.32
3.15 SOFTWARE UPGRADE .......................................................................................................... 3.33
CHAPTER 4 DEBUG AND SIMULATION FACILITIES ............................................. 4.1
4.1 GENERAL INFORMATION ...................................................................................................... 4.1
CHAPTER 5 TROUBLESHOOTING .......................................................................... 5.1
5.1 INTRODUCTION ...................................................................................................................... 5.1
5.1.1 Safety Precautions ................................................................................................... 5.1
5.1.2 Personnel ................................................................................................................. 5.1
5.2 REQUIRED TOOLS AND INSTRUMENTS ............................................................................... 5.1
5.3 CORRECTIVE MAINTENANCE PROCEDURES ....................................................................... 5.2
5.4 CORRECTIVE MAINTENANCE PROCEDURES ON DISPLAY CORE UNIT .......................... 5.3
5.4.1 DISPLAY CORE UNIT Cover Removing and Installation .............................. 5.3
5.4.2 Alpha Expansion Board Replacement ..................................................................... 5.3
5.4.3 ANTARES Assy Replacement ................................................................................... 5.4
5.4.4 Alpha Board Replacement ....................................................................................... 5.4
5.4.5 Line Filter Replacement .......................................................................................... 5.5
5.4.6 P.S. Assy Replacement ............................................................................................. 5.5
5.4.7 Fans Assy Replacement ........................................................................................... 5.6
5.5 CORRECTIVE MAINTENANCE PROCEDURES ON THE DISPLAY UNIT ............................. 5.12
5.6 CORRECTIVE MAINTENANCE PROCEDURES ON THE KEYBOARD UNIT ........................ 5.12
5.7 INTRODUCTION .................................................................................................................... 5.13
5.7.1 Parts List................................................................................................................ 5.13
5.7.2 Parts Location Illustration .................................................................................... 5.13
5.7.3 Parts List Tables .................................................................................................... 5.14
5.8 SYSTEM LIFETIME ................................................................................................................ 5.16
CHAPTER 6 Annex A ................................................................................................ 6.1
CHAPTER 7 Annex B ................................................................................................ 7.1
CHAPTER 8 Annex C ................................................................................................ 8.1
List of Tables
TABLE 1.4.1 - SUMMARY OF THE INPUT/OUTPUT REQUIREMENTS .......................................................... 1.6
TABLE 1.10.1 VDR CONNECTION ......................................................................................................... 1.12
TABLE 1.10.2 MONITOR TIMINGS ......................................................................................................... 1.12
TABLE 5.1 LIST OF CORRECTIVE MAINTENANCE PROCEDURES .......................................................... 5.2
Page 6
988-10187-004 4
SHIPPING AND UNPACKING
The unit parts are placed in cardboard boxes covered with a plastic sheet. Each box includes a protecting polyurethane box shaped for the contained parts.
The following general rules apply:
- Inspection for damage during transport.
- When the unit(s) arrive at destination, inspection should be made immediately to register any damage that may have occurred during transport.
- The customer is normally responsible for insurance during transportation. If any damage is found, both the insurance company and the shipping agent must be informed immediately.
- Units must be transferred on board still packed into their boxes.
- When the units are removed from their boxes, they must be left in their protective plastic cover until installation.
It is advisable to keep the packing material for possible future use. The plastic sheet the unit is wrapped in, can be used to protect it during installation and maintenance procedures.
In addition to the various main parts, the package should also include:
- Technical Manual with installation procedures.
- Installation kit (terminals, clamps, connectors etc.)
- Standard spare part kit (fuses, screws etc.)
The installation kit and spare part kit are necessary for the installation and operation of the equipment, and must be kept together to perform the installation work. Contents of the kits should be checked immediately after unpacking, using the supplied material list in the box. The manufacturer will not accept claims for missing items unless presented immediately after unpacking.
STORAGE
After the material contained in the boxes have been inspected in the presence of the customer and have been verified that no damage has occurred, the unit shall be stored in its original packing until the time of installation. The storage premises must be dry and well protected.
If the units must be kept in storage for more than one month, it is advisable to insert hygroscope substances, such as silicon gel salts, in the crates.
The Argus Radar System contains delicate electronic components, please handle accordingly.
Page 7
988-10187-004 5
WARNINGS
HIGH VOLTAGE
Radar equipment includes high voltage that can cause injury or loss of life. Danger exists only when the units are opened for service, exposing internal circuits. The ARGUS Radar has been carefully designed to protect personnel from possible injury from high voltages. Nevertheless, it is recommended that the Main Power Line shall always be OFF as an added protection when inspecting or servicing the equipment. Although every effort has been made to eliminate danger to personnel, no responsibility is accepted for any injury or loss of life suffered in connection with this equipment.
X-RAY RADIATION
The Argus Radar does not generate X-RAY radiation.
RADIO-FREQUENCY RADIATION
Harmful effects (particularly to the eyes) may be caused by exposure of any part of the human body to radio-frequency mean power densities in excess of 100 mW/cm2. This power density is exceeded at a distance of 1 ft. or less from the 12 ft. X-Band aerial (when stationary). The system is designed to disable radiation when the antenna is not rotating. The pedestals have also been prepared for installation of an external safety switch, which can be mounted on, or near the platform. This switch disconnects the power from the Pedestal preventing accidental operation during servicing. Whenever it is necessary to disconnect the waveguide system from a radar transmitter for maintenance purpose, the transmitter output should, when practical, be terminated in a matched load. If this is not possible, care should be taken to avoid standing in front of an open-ended waveguide from which power is being radiated. NEVER look down a waveguide from which power is being radiated.
SAFETY SWITCH
The Radar Unit is provided with a safety switch, which disables the antenna rotating during maintenance and service.
Page 8
988-10187-004 6
SAFETY PRECAUTIONS
Purpose
Safety precautions described in this paragraph are applicable to the Argus X­Band Radar System. Depending upon the type of advice, the following attention signs are used in the technical manual:
WARNING
IF THIS OPERATING PROCEDURE, MAINTENANCE PROCEDURE, PRACTICE, CONDITION OR STATEMENT IS NOT STRICTLY FOLLOWED, IT COULD RESULT IN SEVERE INJURY OR DEATH OF PERSONNEL.
WARNING
IF THIS OPERATING PROCEDURE, MAINTENANCE PROCEDURE, PRACTICE, CONDITION OR STATEMENT IS NOT STRICTLY FOLLOWED, IT COULD RESULT IN DAMAGE, OR DESTRUCTION OF UNIT, OR LOSS OF TRANSMISSION EFFICIENCY.
NOTE
Advice of an essential operating procedure, maintenance procedure, condition or statement, which must be followed.
Whenever a precaution, relating specifically to a part of the technical manual is needed, precaution information is given in the relevant part of the manual. Warning and Caution Signs precede applicable text.
Safety Operations
During normal operation (unit closed), the unit can be quickly disconnected from the main power line, switching OFF the main circuit breaker located on the electric switchboard.
During maintenance (unit opened) it is possible to turn on the unit, by setting the SERVICE MODE to SW2 switch, mounted on the SRT control PCB (see next page). This switch is connected in parallel with the relay, controlled by the POWER ON command, and during normal operation must be set to NORMAL. During maintenance, in order to prevent RTM occasional turning-on it is better to disconnect and insulate, momentarily, PWON terminal from the relevant terminal board.
NOTE
Main power line is always present on terminal board and on fuses
Page 9
988-10187-004 7
SW2 switch (red rotary component)
SRT control PCB
Safety Summary
The following general safety precautions are not related to any specific procedure and therefore do not appear elsewhere in this technical manual. These are recommended precautions that personnel must understand and apply during most phases of operation and maintenance.
KEEP AWAY FROM ANY LIVE CIRCUITS! Operating personnel must at all times observe all safety regulations. Do not replace components or make adjustments inside the unit with the high voltage supply turned ON. Under certain conditions, dangerous potentials may exist when the power breaker is in OFF position, due to charges retained by capacitors. To avoid danger and casualties, always remove power and discharge to ground a high voltage circuit before touching it.
DO NOT SERVICE OR ADJUST YOURSELF! Under no circumstances should any person initiate servicing or adjusting the unit except in the presence of authorized personnel.
RESUSCITATION Personnel working with or near high voltage should be familiar with modern methods of resuscitation. Such information may be obtained from the Bureau of Medicine and Surgery or equivalent.
Page 10
988-10187-004 8
Warning Information
The following warning signs appear in this technical manual. To point out their importance, they are repeated here for emphasis:
WARNING
USE EXTREME CARE WHEN WORKING ON THE UNIT ONCE THE COVER HAS BEEN OPENED. THE MAGNETRON ASSEMBLY OPERATES AT HIGH VOLTAGES THAT MAY CAUSE FATAL INJURIES
WARNING
BE AWARE OF HIGH VOLTAGE CAPACITORS. IT IS NECESSARY TO SHORT-CIRCUIT THEIR LEADS BEFORE PERFORMING ANY MAINTENANCE ACTION ON THEM.
WARNING
ON THE ELECTRIC SWITCHBOARD, SET THE POWER BREAKER DEDICATED TO THE PRESENT EQUIPMENT TO “OFF”, AND ATTACH A SIGN, READING: “WORK IN PROGRESS! DO NOT SWITCH ON!”
WARNING
USE EXTREME CARE WHEN WORKING ON THE EQUIPMENT ONCE THE UNIT HAS BEEN OPENED. THE MAGNETRON ASSEMBLY OPERATES AT HIGH VOLTAGES THAT MAY CAUSE FATAL INJURIES.
WARNING
SET MAIN LINE BREAKER TO OFF BEFORE REPLACING ANY FUSE. FUSES ARE AT VOLTAGE LEVELS, WHICH MAY CAUSE FATAL INJURIES.
Page 11
Argus Radar - INSTALLATION AND SETTINGS
988-10187-004 1.1
CHAPTER 1
INSTALLATION AND SETTINGS
1.1 Guidelines for the installation of
shipborne radar equipment
Information provided by radar is of vital importance for navigators and the safe navigation of ships.
Special care should be taken to ensure correct installation of the radar, in order to ensure the performance of the radar system.
Correct location of the radar antenna is an important factor the performance of the radar system. Interference, either by reflecting constructions or other transmitters, may heavily reduce the radar performance by creating blind sectors, clutter on the radar display or generation of false echoes.
1.2 Interference
Proper care should be taken with regard to the location of radar antennas relative to other antennas which may cause interference to either equipment. The location of the antenna should comply with the following:
The radar antenna should be installed at a safe distance from interfering high­power energy sources and other transmitting and receiving radio antennas.
The lower edge of the radar antenna should be a minimum of 50 cm above any safety rail.
Radar antennas in close proximity should have a minimum vertical elevation separation angle of 20° and a minimum vertical separation of 1 m where possible.
1.2.1 Location relative to masts, funnels and
other constructions
Proper care should be taken with regard to the location of radar antennas relative to masts, funnels and other constructions.
The location of the antenna should comply with the following: The antenna should generally be mounted clear of any structure that may cause signal reflections. Ensure that any support or other obstacles are clear of the rotation of the antenna (see specific antenna outline drawing for rotation radius). Install antenna and turning unit so that the installation complies with the compass safe distance for the equipment.
Page 12
Argus Radar - INSTALLATION AND SETTINGS
988-10187-004 1.2
1.2.2 Blind sectors and range
To ensure full benefit from the radar, it is vitally important for the OOB that horizontal and vertical blind sectors for the radar antennae are minimized. The objective is to see the horizon freely through 360°, or as close to as possible.
For all radar systems and where practical, a line of sight from the radar antenna to the bow of the ship should hit the surface of the sea at no more than 500 m or twice the ship length, depending which value is smaller. This goes for all load and trim conditions.
The radar antenna should be located in an elevated position to permit maximum target visibility.
Ideal Radiation Plane
Blind sectors should be kept at a minimum, and should not occur in an area of the horizon from right ahead to 22.5° abaft the beam to either side.
Note: Any two blind sectors separated by 3° or less should be treated as one blind sector.
Individual blind sectors of more than 5°, or a total of blind sectors of more than 20°, should not occur in the remaining area, excluding the area in the above subparagraph (e).
For radar installations with two radar systems, where possible, the antennas should be placed in such a way as to minimize the blind sectors.
Page 13
Argus Radar - INSTALLATION AND SETTINGS
988-10187-004 1.3
All installations should facilitate protection of equipment from damage, including cabling.
Safe service access should be provided using service platforms where necessary, having a minimum size of 1 m2 at a suitable height and with a safety rail of suitable height.
Consideration should be given to the compass safety distance, as supplied by the manufacturer, when positioning equipment units.
The design of the mounting platform for the antenna and antenna pedestal should take into account the vibration requirements of resolution A.694(17) and furthermore defined by IEC 60945. In addition to vibration, the design of the mounting platform should consider shock and whiplash due to conditions at sea.
1.2.3 Interaction with sea and false echoes
Considerations of interaction with the sea imply that the radar antenna should be only as high as necessary to clear major objects, and as high to be consistent with other requirements regarding acceptable horizon and target detection range. The location of the antenna should minimize sea clutter returns and the number of multi-path nulls.
1.2.4 Cables and grounding
Cables and grounding should comply with the following:
Cable screens, especially coaxial cable screens, should be installed according to manufacturer's documentation.
The cables should be kept as short as possible to minimize interference and attenuation of the signal.
All cables between antenna and radar system units should be routed as directly as possible, consistent with consideration for other equipment, in order to reduce electromagnetic interference effects. Cables should not be installed close to high-power lines, such as radar or radio-transmitter lines.
Crossing of cables should be done at right angles (90°) to minimize magnetic field coupling.
All outdoor installed connectors should be waterproof by design to protect against water penetration into the cables.
Cables and microwave transmission lines should be handled carefully and be without sharp bends.
Cables and microwave transmission lines should be installed with sufficient physical separation, as defined in the manufacturer's documentation.
Page 14
Argus Radar - INSTALLATION AND SETTINGS
988-10187-004 1.4
1.2.5 Radar controls and display
If the control panel is a separate unit, the functionality of the radar controls should be available for the mariner at all workstations where a radar display is available.
The orientation of the display unit should be such that the user is looking ahead. The lookout view should not be obscured and the ambient light should cause minimum degradation on the display screen in accordance with MSC/Circ.982.
WARNING
ONLY ELECTRONIC POSITION FIXING SYSTEMS (EPFS) APPROVED IN ACCORDANCE WITH THE REQUIREMENTS OF THE IMO IN RESOLUTION MSC.112(73) SHALL BE CONNECTED TO THE ARGUS RADAR CONSOLE.
WARNING
ACCORDING THE IMO STANDARD, A GROUND SPEED SENSOR IS REQUIRED TO BE CONNECTED TO THE ARGUS CONSOLE. IT IS ALLOWED TO USE AN ELECTRONIC POSITION FIXING SYSTEM (EPFS) APPROVED IN ACCORDANCE WITH THE REQUIREMENTS OF THE IMO IN RESOLUTION MSC.112(73) OR AN ALTERNATIVE TWO DIMENSIONAL GROUND STABILISING SDME IN COMPLIANCE WITH IMO RESOLUTION MSC.96(72)
WARNING
LONG TRANSMISSION LINES CAN AFFECT THE RADAR PERFORMANCE. THE SYSTEM HAS BEEN TESTED WITH 20 M LENGTH FROM TRANSCEIVER TO ANTENNA PEDESTAL, CONSIDER THAT TRANSMITTED/RECEIVED POWER ARE HALVED FOR EVERY 10 MS ADDED (EX: +20 M = -6DB SIGNAL/NOISE). CLEARLY THIS AFFECTS DETECTION FOR FAR TARGETS AND FOR SMALL/LOW REFLECTIVITY ONES LIKE SAILBOATS. HIGHEST MAST POSITION IS GOOD FOR LONG RANGE DETECTION BUT IT AFFECTS HEAVILY THE DETECTION IN SEA CLUTTER. FOR OPTIMAL DETECTION IN SEA CLUTTER SUGGESTED ANTENNA HEIGHT FROM SEA LEVEL IS APPROX. 20 M. USUALLY THE CONTRADICTORY SPECIFICATIONS ARE SOLVED WITH INSTALLATION OF MORE THAN ONE ANTENNA, FOR EXAMPLE ONE AT 30 M FOR LONG RANGE DETECTION AND ONE AT 20 M FOR OPTIMAL DETECTION OF LOW INTENSITY ECHOES IN SEA CLUTTER.
Page 15
Argus Radar - INSTALLATION AND SETTINGS
988-10187-004 1.5
WARNING
THE RADAR UNIT IS PROVIDED WITH A SAFETY SWITCH, WHICH DISABLES ANTENNA ROTATION DURING MAINTENANCE OPERATIONS AND AVOIDS HIGH VOLTAGE DAMAGE. ALWAYS TURN THE SAFETY SWITCH “OFF”, WHENEVER ADVISED IN THIS MANUAL (FOR INSTANCE, BEFORE PERFORMING ANY MAINTENANCE OR INSTALLATION PROCEDURE). IGNORING SAFETY SWITCH OPERATION MAY PRODUCE HAZARD OF ELECTROCUTION AS WELL AS OTHER SEVERE INJURES
1.3 System Specifications
1.3.1 Dimension and Weight
See outline drawings
1.3.2 Power
Power supply
Single phase 220 or 115 Vac +/- 15% 50/60 Hz
Power consumption (estimated)
Monitor M5027
68 W (+ 5 W power supply)
Monitor M5024
35 W (+ 5 W power supply)
Monitor M5019
30 W (+ 5 W power supply)
Monitor M5016
25 W (+ 5 W power supply)
Monitor 26” Hatteland 16:10
120 W
Monitor 24” Hatteland
110 W
Core + Keyboard
40 W
1.3.3 Environmental Data
Operating temperature
-15°C / +55°C
Storage temperature
-25°C / +70°C
Relative humidity
Up to 95% at +40°
Water resistance, Salt spray, Vibrations etc. as per IEC 60945
Page 16
Argus Radar - INSTALLATION AND SETTINGS
988-10187-004 1.6
1.4 Input/Output Requirements
The parameters with tolerances are included with each of the inputs listed.
Table 1.4.1 - Summary of the Input/Output Requirements
Feature Characteristics
Power (see also
section 1.3.2)
Voltage:
Consumption:
Single phase 110 to 230 Vac ±15%, 50/60 Hz ±6% 50 VA
Environmental Conditions
Operating:
Storage:
Temperature -15°C to +55 °C
Temperature -20°C to +60 °C
Gyrocompass Synchro:
. Voltage value: 50 ÷ 115 Vac ±10%
(reference) . 50/60 Hz or 300/400 Hz . Gear ratio: 1:360, 1:180, 1: 90, 1:36
Stepper:
. Voltage value: 15 to +100 V positive (Vef)
-15 to -100 V negative (Vef)
. Gear ratio: 1:360, 1:180, 1: 90, 1:36
Stepper rectified:
. Voltage value: 100 Vac (Vef) . Frequency: 50/60 Hz or 300/400 Hz ±6% . Gear ratio: 1:360, 1:180, 1: 90, 1:36
Serial:
. RS422 standard FNMEA or RS232 . Load: 7 KΩ, terminated 120 Ω
Speed Log Mechanical input:
. PRR: 100 pulses/NM, 200 pulses/NM, 400
pulses/NM . Input type: diode isolated, pull-up . pulse width: 1 ms (min)
. Load: 2.7 KΩ
. Threshold: +10 V (typ)
Speed For
Electronic input (switch):
. PRR: 120 pulses/m, 20000 pulses/NM . Load: ≥ 1 KΩ . Pulse width: 0.1 µs (min) . Voltage: TTL to 15V (typ)
Speed Serial
Electronic input (serial):
. Input type: RS422 standard NMEA or
RS232 . Load: 3 KΩ, terminated 120 Ω
System Failure (FAIL) TB1 (pin 5-6)
Relay output NC
Closed when the system is in failure or
switched off
- Max 125 V 30 W load
AIS
. RS422 standard FNMEA or RS232
Load: 7 KΩ, terminated 120 Ω
EPFS
RS232
Load: 3 KΩ, terminated 120 Ω
BAM
Input type: RS422 standard NMEA or
RS232
Load: ≥ 3 KΩ, terminated 120 Ω
Danger Target (DGT) TB1 (pin 3-4)
Relay output NC/NO configurable
Active when a Radar Target or AIS is
dangerous
- - Max 125 V 30 W load
Page 17
Argus Radar - INSTALLATION AND SETTINGS
988-10187-004 1.7
Feature Characteristics
Dead Man Alarm Reset (DNA) TB1 (pin 1-2)
Relay output NC/NO configurable
Active when an action is made on the
control panel
- Max 125 V 30 W load
Video and Combined data without ALPHA Expansion or CH3 and CH4 with this card
. Voltage value: 0,8 to 1,5 Vpp adjustable
. Load: ≥ 1 KΩ, terminated 75 Ω
Video and data with Alpha Expansion CH1 and CH2: (Optional) Video:
Polarity:
. Positive or negative
Amplitude: . 1 to 4 Vpp adjustable
Load:
. Load: ≥ 1 KΩ, terminated 75 Ω
Bandwidth:
. 24 MHz (-3 dB)
Trigger:
Polarity:
. Positive or negative
Amplitude:
. TTL to 40 V (peak)
Load:
. Load: ≥ 1 KΩ, terminated 75 Ω
PRF:
. 300 to 4000 Hz
Pulse width:
. 50 ns (min.)
Serial Interface: Signal Standard:
. RS232 or RS422 . Load: ≥ 3 KΩ, terminated 120 Ω
Antenna Rotation Rotation rate: . 15 to 60 RPM
Data
Device type:
- Bearing
. Voltage value: 4 to 50 V . 128 or 132 pulses per antenna revolution . Load: ≥ 2 KΩ
- Encoder
. Voltage value: 4 to 50 V
. 1024 or 4096 pulses per antenna
revolution
. Load: ≥ 2 KΩ
Heading line Voltage value: . 4 to 50 V Load: . Load: ≥ 2 KΩ
Pulse width:
. ≥ 0,1 mS and < 45°
Polarity:
. Positive or negative or bipolar
1.5 Analogue Gyro compass (Synchro or Stepper)
The gyro signals are connected to TB14 on the Alpha PCB. There are several connection possibilities depending on type and reference voltage of the gyro.
Refer to the drawing below for the relevant configuration for Synchro and Stepper.
Page 18
Argus Radar - INSTALLATION AND SETTINGS
988-10187-004 1.8
Fig 1 For Argus (ALPHA PCB) connect to TB14.
Note: Connection with stepper gyro full wave rectified signal (SPERRY MK-37, MK-20)
1. Close the jumpers P10, P13, P15 on the Alpha PCB;
2. make the interconnection to TB4 on the Alpha PCB as follow:
TB14
WIRE
NUMBERS
FROM
GYRO
3. Follow the configuration instructions described in Chapter 3
4. Check the phases status through the LED on the Alpha PCB.
The three phases are given by the gyro with a 3 bit Gray code. The purpose of this code is to detect the increment of the value and its sign; its most important characteristic is that only one of the three bits at the time can change and in this application (normally is not a characteristic of the Gray code), the 3 bits cannot have all the same level. To give a quick look to the Gray code see the four green LED on the Alpha:
1. The first one next to red LED is D33 and it indicates the first phase (S1).
S0
S1
S2
S3
R1H
R1L
R2
#5
#1
#2
#3
#4
Page 19
Argus Radar - INSTALLATION AND SETTINGS
988-10187-004 1.9
2. The second one is D34 and it is the second phase indicator (S2).
3. The third one is D35 and it indicates the third phase (S3).
4. The last one is D36 and it is to indicate the Reference.
Now that the LEDs are individuated, move the gyro or in any way simulate a steering and the three LEDs (S1, S2 and S3) will start to change their state and it will be easy to observe that they will never be “all on” or “all off”; their state will change one at a time.
WARNING
THE GYRO INTERFACE SHOULD BE CONFIGURED CORRECTLY ACCORDING TO TYPE OF SENSOR CONNECTED, OTHERWISE LEVELS AND LED SIGNALS WILL BE INCORRECTLY LIGHTED, ALSO WHEN THE SIGNALS ARE AVAILABLE.
S1
S3
S2
Gyro Phases combinations in Gray code
Page 20
Argus Radar - INSTALLATION AND SETTINGS
988-10187-004 1.10
1.6 Serial Gyro
A Standard or Fast NMEA Gyro can be connected to the Alpha PCB TB9
Connect it according to guidelines defined in Chapter 2 Serial Interfaces.
1.7 Speed LOG
Speed log with analogue signal is connected to TB14 on the Alpha PCB. There are several connections depending on the type of log installed. Most single axis analogue speed logs are shorting-type (relay contact closure), in this case the signal shall be connected between PIT and GND on TB14.
Speed log with NMEA output can be connected to Alpha PCB input TB2. See the serial interface chapter for accepted sentences.
WARNING
THE HEADING SENSOR, A GYRO EQUIPMENT OR EQUIVALENT, SHOULD BE ABLE TO SUSTAIN A RATE OF TURN UP TO 20°/S ACCORDING TO IMO RESOLUTION MSC.192(79) AND MSC.116(73) FOR THD DEVICES. IF THE INTERFACE IS ANALOGUE THE MINIMUM TURN RATE SHOULD BE 12°/S. FOR A DIGITAL INTERFACE THE HEADING REFRESH SHOULD BE MORE THAN 20 HZ, UP TO 50 HZ. IF THE GYRO UPDATE RATE IS UNDER THE PREVIOUS STATED VALUES THE TRACKING PERFORMANCE CAN BE SERIOUSLY DEGRADED WITH INCREASING ERRORS ON TARGET VECTOR DURING THE OWN SHIP CHANGE OF COURSE.
Page 21
Argus Radar - INSTALLATION AND SETTINGS
988-10187-004 1.11
1.8 EPFS
The EPFS (Electronic Position Fixing System) signal is connected to TB3 on the Alpha PCB. When connected to an EPFS, the TB3 output sends relevant data for INS and ECDIS.
NOTE
Supported EPFS equipment must follow the IMO recommendation MSC.114(73)
1.9 AIS
The AIS signal is connected to TB8 on the Alpha PCB. It's possible to receive RS422 or RS232 standard signal only at 38400 bps. The sentences accepted are: AIALR, AIVDM and AIVDO.
NOTE
It is also possible to connect the output from the RADAR to the AIS device, to acknowledge the alarms coming from AIS from the RADAR interface. Normally, the AIS equipment has only one input available, so that only one RADAR can be connected to it and only one will be able to acknowledge the alarms. This output is on the same serial port TB8 with only one sentence generated: AIACK
The same output is the source for tracking data sentences TTD and TLB.
NOTE
Supported AIS equipment must follow the IMO recommendation A.917(22)
1.10 BAM
Using same formatting as per EPFS:
The BAM (Bridge Alarm Monitoring system) signal can be connected to TB10 or TB4 on the Alpha PCB.
NOTE
Supported BAM equipment must follow the IMO recommendation MSC.252(83)
Page 22
Argus Radar - INSTALLATION AND SETTINGS
988-10187-004 1.12
1.11 VDR Connection
To connect a VDR System to the Argus Radar, use the VGA Output on the Core Unit (Alpha Assy). The maximum distance from the Unit to the VDR depends on the level of the Video signal output of the cable in use. See the following table for distances regarding function of cable type.
Cable
Video
1280x1024
Video
1600x1200
Video
1920x1200
(26” wide
screen)
Distance (m)
Distance (m)
Distance (m)
RG75
RG59
M202 M203
RG11
CT100
CT125
10
25 25 35 40 50
60
8
20 20 30 30 40
45
10
25 25 35 40 50
60
Table 1.10.1 – VDR Connection
NOTE
- Supported VDR equipment must follow the IMO recommendation A.861(20)
- The VDR outlet is completely different from the DVI outlet to which the monitor is connected
Monitor synchronism timings according to the resolution
Resolution 1280x1024 1366x768 1600x1200 1920x1080 1920x1200
Dot Clock
110 MHz 72 MHz 110 MHz 144 MHz 130 MHz
Horizontal Period
15.56 uS 21.75 uS 16.36 uS 14.7 uS 16 uS
Horizontal Sync
1.67 uS 469 nS 0.908 uS 236 nS 246 nS
Horizontal Front
Porch
392 nS 916 nS 416 nS 458 nS 336 nS
Horizontal Back Porch
1.86 uS 1.388 uS 496 nS 694 nS 652 nS
Vertical Period
16.41 mS 17.53 mS 19.96 mS 16.48 mS 19.76 mS
Vertical Sync
46.4 uS 87 uS 164 uS 58 uS 96 uS
Vertical Front
Porch
15.6 uS 87 uS 48.8 uS 58.8 uS 48 uS
Vertical Back
Porch
410 uS 652 uS 116 uS 418 uS
Table 1.10.2 – Monitor timings
Page 23
Argus Radar - INSTALLATION AND SETTINGS
988-10187-004 1.13
1.12 Radar Console Failure Output
For installation where a continuous check of the radar console operability is mandatory, a failure output is available. The FAIL output is located on TB1 on the Alpha PCB and it is a NC contact that can supply up to 200 mA of current (see Input/Output specification at this Chapter’s introduction). A special electronic circuit on the Antares PCB acts continuously as a watchdog to detect any operational failure that can cause a processor malfunction. Should a failure occur or the system is powered-off, the contact switches to closed condition.
1.13 Configuration Links Table
1.13.1 Antares PCB Links:
Function
Ref.
Link Name
Description
Factory
Preset
BDM
J8
BDM
Enable B
Normally Open
Open
J11
BDM
Enable A
Normally Open
Open
Restore J7
SW
If closed at startup, the default programs will not start and the upgrade ÷ restore programs will be run.
Open
1.13.2 Alpha PCB Links:
Function Ref. Link Name Description
Factory
Preset
Video
P7
VD1 Termination
Link closed when the Argus is
standalone or the last
equipment on the Video chain
Close
P12
VD2 Termination
Link closed when the Argus is
standalone or the last
equipment on the Video chain
Close
P2
422 Termination
Link closed when the Argus is
standalone on 422 serial communication or the last equipment on 422 serial
communication chain
Open
Page 24
Argus Radar - INSTALLATION AND SETTINGS
988-10187-004 1.14
Function Ref. Link Name Description
Factory
Preset
Serial
P3
FNMEA 1
Termination
Link closed when the Argus is
standalone on 422 serial communication or the last equipment on 422 serial
communication chain
Open
P4
FNMEA 2
Termination
Link closed when the Argus is
standalone on 422 serial communication or the last equipment on 422 serial
communication chain
Open
P5
FNMEA 3
Termination
Link closed when the Argus is
standalone on 422 serial communication or the last equipment on 422 serial
communication chain
Open
P8
232+422 / 1
Termination
Link closed when the Argus is
standalone on 422 serial communication or the last equipment on 422 serial
communication chain
Open
P9
232+422 / 2
Termination
Link closed when the Argus is
standalone on 422 serial communication or the last equipment on 422 serial
communication chain
Open
P11
232 / RX7 Inversion
Set this link to configure serial polarity
1-2
P14
232 / RX8 Inversion
Set this to configure serial polarity
1-2
Gyro
P10 S3 Gyro set
Normally open, close in case of Sperry MK20 or MK37
Open
P13 S2 Gyro set
Normally open, close in case of Sperry MK20 or MK37
Open
P15 S1 Gyro set
Normally open, close in case of Sperry MK20 or MK37
Open
Alarm
P1
Dead Man Alarm
Set 1-2 normally open contact or 2-3 normally close contact
1-2
P6
Danger Target Alarm
Set 1-2 normally open contact or 2-3 normally close contact
1-2
Page 25
Argus Radar - INSTALLATION AND SETTINGS
988-10187-004 1.15
1.13.3 Alpha Expansion PCB Links:
Function Ref. Link Name Description
Factory
Preset
Video
P1
Video 1
Termination
Link closed when the Argus is standalone or the last equipment on the Video chain
Close
P2
Video 2
Termination
Link closed when the Argus is standalone or the last equipment on the Video chain
Close
P6
Video 3
Termination
Link closed when the Argus is standalone or the last equipment on the Video chain
Close
P8
Video 4
Termination
Link closed when the Argus is standalone or the last equipment on the Video chain
Close
P3
VD1 Level
Close in Serial Data Communication, open in Combined Video and with SRT Adapter Box installations
Close
P4
VD2 Level
Close in Serial Data Communication, open in Combined Video and with SRT Adapter Box installations
Close
Trigger
P5
Trigger 1
Termination
Link closed when the Argus is standalone or the last equipment on the Trigger chain
Close
P7
Trigger 2
Termination
Link closed when the Argus is standalone or the last equipment on the Trigger chain
Close
Page 26
988-10187-004 1.16
This page is intentionally left blank
Page 27
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.1
CHAPTER 2
SERIAL INTERFACE SPECIFICATIONS
2.1 Serial Line 1, Heading
It is possible to receive RS422 or RS232 standard signal at 4800 or 38400 bps indifferently on TB9 (FNMEA 1). Note that the circuit is able to receive at 4800 and 38400 bps also with RS232 connection, but this is not a standard connection according to the IEC 61162-2 standard.
SCHEME 4 IN + IN ­SHLD OUT+ OUT­GND
RS 422 Interface Listener Connection
+ IN
"A" Data Input
- IN
"B" Data Input
SHLD
“C” insulated Ground
Input Load
7 K
RS 232 Interface Listener Connection
- IN
RX Data Input
SHLD and + IN
Insulated ground
Input Load
7 K
This serial line is compliance with IEC 61162-1 and IEC 61162-2. Accepted sentences: THS and HDT
Page 28
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.2
THS – True heading and status
NOTE
This sentence replaces the deprecated sentence HDT.
Actual vessel heading in degrees true produced by any device or system producing true heading. This sentence includes a “mode indicator” field providing critical safety related information about the heading data, and replaces the deprecated HDT sentence.
$--THS,x.x,a*hh<CR><LF>
Mode indicator (see Note)
Heading, degrees true
NOTE
Mode indicator. This field should not be null.
A = Autonomous
E = Estimated (dead reckoning)
M = Manual input
S = Simulator mode
V = Data not valid (including standby)
HDT – Heading true
Actual vessel heading in degrees true produced by any device or system producing true heading.
NOTE
This is a deprecated sentence which has been replaced by THS.
$--HDT, x.x, T*hh<CR><LF>
Heading, degrees true
Page 29
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.3
2.2 Serial Line 2, AIS
It is possible to receive RS422 or RS232 standard signal at 4800 and 38400 bps on TB8 (FNMEA 2). Note that the circuit is able to receive at 4800 and 38400 bps also with RS232 connection, but this is not a standard connection according to the IEC 61162-2 standard.
SCHEME 2 IN + IN ­SHLD OUT+ OUT­GND
RS 422 Interface Listener Connection
+ IN
. "A" Data Input
- IN . "B" Data Input
SHLD
. “C” insulated Ground
Input Load
. 7 K
RS 232 Interface Listener Connection
.
- IN . RX Data Input
SHLD and + IN
. Insulated ground
Input Load
- 7 K
RS 422 Output Talker Connection
+ OUT
. "A" Data Output
- OUT . "B" Data Output
GND
. “C” Ground
Output Drive
- 150 mA
-
This serial line complies to IEC 61162-1 and IEC 61162-2. Accepted sentences: VDM, VDO and ALR. Send sentences TLB, TTD and ACK.
VDM – AIS VHF data-link message
Defined in ITU-R M.1371 and as received on the VHF Data Link (VDL), using the “six-bit” field type. The structure provides for the transfer of long binary messages by using multiple sentences.
Data messages should be transmitted in as few sentences as possible. When a data message can be accommodated in a single sentence, then it shall not be split.
Page 30
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.4
VDM – AIS VHF data-link message
Defined in ITU-R M.1371 and as received on the VHF Data Link (VDL), using the “six-bit” field type. The structure provides for the transfer of long binary messages by using multiple sentences.
Data messages should be transmitted in as few sentences as possible. When a data message can be accommodated in a single sentence, then it shall not be split.
!--VDM,x,x,x,a,s—s,x*hh<CR><LF>
Number of fill-bits, 0 to 5 (see Note 5)
Encapsulated ITU-R M.1371 radio message (see Note 4)
AIS channel (see Note 3)
Sequential message identifier, 0 to 9 (see Note 2)
Sentence number, 1 to 9 (see Note 1)
Total number of sentences needed to transfer the message,
1 to 9 (see Note 1)
NOTE 1
The length of an ITU-R M.1371 message may require the transmission of multiple sentences. The first field specifies the total number of sentences used for a message, minimum value 1. The second field identifies the order of this sentence in the message, minimum value 1. These cannot be null fields.
NOTE 2
The sequential message identifier provides a message identification number from 0 to 9 that is sequentially assigned and is incremented for each new multi-sentence message. The count resets to 0 after 9 is used. For a message requiring multiple sentences, each sentence of the message contains the same sequential message identification number. It is used to identify the sentences containing portions of the same message. This allows for the possibility that other sentences might be interleaved with the message sentences that, taken collectively, contain a single message. This should be a null field for messages that fit into one sentence.
NOTE 3
The AIS channel is indicated as either “A” or “B”. This channel indication is relative to the operating conditions of the AIS unit when the packet is received. This should be a null field when the channel identification is not provided. The VHF channel numbers for channels “A” and “B” are obtained by using a “query” (see 7.3.4) of the AIS unit for an ACA sentence.
Page 31
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.5
NOTE 4
This field supports up to 60 valid characters. Under certain conditions, this field may support up to a maximum of 62 valid characters: 1) When the message can be transmitted using a single sentence, the sequential message identifier field is set to null allowing an additional valid character in this encapsulated field. 2) When the AIS channel field is set to null an additional valid character is allowed in this encapsulated field. 3) The maximum number of 62 valid characters is only possible when the conditions allow both the sequential message identifier and AIS channel fields is set to null.
NOTE 5
This cannot be a null field. See “x4” in 7.3.3.
Page 32
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.6
VDO – AIS VHF data-link own-vessel report
This sentence is used to transfer the entire contents of an AIS unit’s broadcast message packet, as defined in ITU-R M.1371 and as sent out by the AIS unit over the VHF data link (VDL) using the “six-bit” field type. The sentence uses the same structure as the VDM sentence formatter.
!--VDM,x,x,x,a,s—s,x*hh<CR><LF>
Number of fill-bits, 0 to 5 (see Note 5)
Encapsulated ITU-R M.1371 radio message (see Note 4)
AIS channel (see Note 3)
Sequential message identifier, 0 to 9 (see Note 2)
Sentence number, 1 to 9 (see Note 1)
Total number of sentences needed to transfer the message,
1 to 9 (see Note 1)
NOTES 1
To 5 See VDM sentence notes.
ALR – Set alarm state
Local alarm condition and status. This sentence is used to report an alarm condition on a device and its current state of acknowledgement.
$--ALR,hhmmss.ss,xxx,A, A,c--c*hh<CR><LF>
Alarm’s description text
Alarm’s acknowledge state, A = acknowledged
V = unacknowledged
Alarm condition (A = threshold exceeded, V = not exceeded)
Unique alarm number (identifier) at alarm source
Time of alarm condition change, UTC
Page 33
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.7
TLB – Target label
Common target labels for tracked targets. This sentence is used to specify labels for tracked targets to a device that provides tracked target data (e.g. via the TTM – Tracked target message). This will allow all devices displaying tracked target data to use a common set of labels (e.g. targets reported by two radars and displayed on an ECDIS).
$--TLB,x.x,c--c,x.x,c--c,...x.x,c--c*hh<CR><LF>
Additional label pairs (see Note 1)
Label assigned to target ‘n’ (see Note 2)
Target number ‘n’ reported by the device.
NOTE 1
This sentence allows several target number/label pairs to be sent in a single message, the maximum sentence length limits the number of labels allowed in a message.
NOTE 2
Null fields indicate that no common label is specified, not that a null label should be used. The intent is to use a null field as a place holder. A device that provides tracked target data should use its ”local” label (usually the target number) unless it has received a TLB sentence specifying a common label.
Page 34
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.8
TTD – Tracked target data
This sentence is used to transmit tracked radar targets in a compressed format. This enables the transfer of many targets with minimum overhead. New target labels are defined by the TLB sentence to reduce bandwidth use. Transmission of up to four targets in the same sentence is possible.
!--TTD,hh,hh,x,s—s,x*hh<CR><LF>
Number of fill-bits, 0 to 5 (see Note 4)
Encapsulated tracked target data (see Note 3)
Sequential message identifier, 0 to 9 (see Note2)
Hex sentence number, 1 to FF (see Note 1)
Total hex number of sentences needed to transfer
the message, 1 to FF (se Note 1)
NOTE 1 The transfer of all tracked targets may require the transmission of multiple sentences. The first field specifies the total number of sentences used for a message, minimum value 1. The second field identifies the order of this sentence in the message, minimum value 1. These cannot be null fields.
NOTE 2
The sequential message identifier provides a message identification number from 0 to 9 that is sequentially assigned and is incremented for each new multi-sentence message. The count resets to 0 after 9 is used. For a message requiring multiple sentences, each sentence of the message contains the same sequential message identification number. It is used to identify the sentences containing portions of the same message. This allows for the possibility that other sentences might be interleaved with the message sentences that, taken collectively, contain a single message. This should be a null field for messages that fit into one sentence.
NOTE 3
The tracked target data structure is described below. One sentence may contain from one up to four structures of 15 characters in the same sentence. This field supports a maximum of 60 valid characters for messages transferred using multiple sentences.
NOTE 4
This cannot be a null field. See “x4” in description of encapsulation sentences in IEC 61162-1.Every target (tracked or AIS) is packed according to the structure below. Data is stored most significant bit first. Every message character is converted into six bits. The structure is encapsulated as 15 characters. The sentence may contain from one to four targets.
Page 35
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.9
Page 36
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.10
2.3 Serial Line 3, EPFS - GPS
It is possible to receive RS422 or RS232 standard signal at 4800 or 38400 bps indifferently on TB3 (FNMEA 3). Note that the circuit is able to receive at 4800 and 38400 bps also with RS232 connection, but this is not a standard connection according to the IEC 61162-2 standard.
SCHEME 3 IN + IN ­SHLD OUT+ OUT­GND
RS 422 Interface Listener Connection
+ IN
"A" Data Input
- IN
"B" Data Input
SHLD
“C” insulated Ground
Input Load
7K
RS 232 Interface Listener Connection
- IN
RX Data Input
SHLD and + IN
Insulated ground
Input Load
7K
RS 422 Output Talker Connection
+ OUT
"A" Data Output
- OUT
"B" Data Output
GND
“C” Ground
Output Drive
150 mA
This serial line complies to IEC 61162-1 and IEC 61162-2. Accepted sentences: ZDA, GLL, GGA, GNS, RMC, DTM and ACK. Send sentences OSD, RSD and TTM.
Page 37
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.11
ZDA – Time and date
UTC, day, month, year and local time zone.
$--ZDA, hhmmss.ss, xx, xx, xxxx, xx, xx*hh<CR><LF>
Local zone minutes (see Note),00 to +59
Local zone hours(see Note), 00 h to ±13 h
Year (UTC)
Month, 01 to 12 (UTC)
Day, 01 to 31 (UTC)
UTC
NOTE
Local time zone is the magnitude of hours plus the magnitude of minutes added, with the sign of local zone hours, to local time to obtain UTC. Local zone is generally negative for East longitudes with local exceptions near the International date line.
Page 38
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.12
GLL – Geographic position – latitude/longitude
Latitude and longitude of vessel position, time of position fix and status.
$--GLL, llll.ll, a, yyyyy.yy, a, hhmmss.ss, A, a *hh<CR><LF>
Mode indicator (see Notes 1 and 2)
Status (see Note 2) A=data valid V=data invalid
UTC of position
Longitude, E/W
Latitude, N/S
NOTE 1
Positioning system mode indicator:
A = Autonomous
D = Differential
E = Estimated (dead reckoning)
M = Manual input
S = Simulator
N = Data not valid
NOTE 2
The mode indicator field supplements the status field (field 6). The status field should be set to V = invalid for all values of operating mode except for A = Autonomous and D = Differential. The positioning system mode indicator and status fields should not be null fields.
Page 39
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.13
GGA – Global positioning system (GPS) fix data
Time, position and fix-related data for a GPS receiver. Differential reference station ID, 0000-1023
Age of differential GPS data (see Note 2)
Units of geoidal separation,m
Geoidal separation (see Note 3)
Units of antenna altitude, m
Antenna altitude above/below
mean sea level (geoid)
Horizontal dilution of precision
$--GGA, hhmmss.ss, llll.ll, a, yyyyy.yy, a, x, xx, x.x, x.x, M, x.x, M, x.x, xxxx*hh<CR><LF>
Number of satellites in use, 00-12, may
be different from the number in view
GPS quality indicator (see Note 1)
Longitude E/W
Latitude N/S
UTC of position
NOTE 1
All GPS quality indicators in headings 1 through 8 are considered “valid”. The heading “0” is the only “invalid” indicator. The GPS quality indicator field should not be a null field.
0 = fix not available or invalid
1 = GPS SPS mode
2 = differential GPS, SPS mode
3 = GPS PPS mode
4 = Real Time Kinematic. Satellite system used in RTK mode with fixed integers
5 = Float RTK. Satellite system used in RTK mode with floating solution
6 = Estimated (dead reckoning) mode
7 = Manual input mode
8 = Simulator mode
Page 40
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.14
NOTE 2
Time in seconds since last SC104 type 1 or 9 update, null field when DGPS is not used.
NOTE 3
Geoidal separation: the difference between the WGS-84 earth ellipsoid surface and mean sea level (geoid) surface, “ – “ = mean sea level surface below the WGS-84 ellipsoid surface.
GNS – GNSS fix data
Fix data for single or combined satellite navigation systems (GNSS). This sentence provides fix data for GPS, GLONASS, possible future satellite systems and systems combining these. This sentence could be used with the talker identification of GP for GPS, GL for GLONASS, GN for GNSS combined systems, as well as future identifiers. Some fields may be null fields for certain applications, as described below.
If a GNSS receiver is capable simultaneously of producing a position using combined satellite systems, as well as a position using only one of the satellite systems, then separate $GPGNS, $GLGNS, etc. sentences may be used to report the data calculated from the individual systems.
If a GNSS receiver is set up to use more than one satellite system, but for some reason one or more of the systems are not available, then it may continue to report the positions using $GNGNS, and use the mode indicator to show which satellite systems are being used.
Differential reference station ID (see Note 2)
Age of differential data (see Note 2)
Geoidal separation, m (see Note 4)
Antenna altitude, m,re:mean-sea-level (geoid)
$-- GNS, hhmmss.ss, llll.ll, a, yyyyy.yy, a, c--c,xx,x.x,x.x,x.x,x.x,x.x *hh<CR><LF>
HDOP (see Note 3)
Total number of satellites in use, 00-99
Mode indicator (see Note 1)
Longitude, E/W
Latitude, N/S
UTC of position
NOTE 1
Mode Indicator. A variable length valid character field type with the first two characters currently defined.
Page 41
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.15
The first character indicates the use of GPS satellites, the second character indicates the use of GLONASS satellites. If another satellite system is added to the standard, the mode indicator will be extended to three characters; new satellite systems shall always be added to the right, so the order of characters in the mode indicator is: GPS, GLONASS, other satellite systems.
The characters should take one of the following values:
N = No fix. Satellite system not used in position fix, or fix not valid.
A = Autonomous. Satellite system used in non-differential mode in position fix.
D = Differential. Satellite system used in differential mode in position fix.
P = Precise. Satellite system used in precision mode. Precision mode is defined as: no deliberate degradation (such as selective availability), and higher resolution code (P-code) is used to compute position fix.
R = Real time kinematic. Satellite system used in RTK mode with fixed integers.
F = Float RTK. Satellite system used in real time kinematic mode with floating solution.
E = Estimated (dead reckoning) mode.
M = Manual input mode.
S = Simulator mode.
The mode indicator should not be a null field.
Page 42
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.16
RMC – Recommended minimum specific GNSS data
Time, date, position, course and speed data provided by a GNSS navigation receiver. This sentence is transmitted at intervals not exceeding 2 s and is always accompanied by RMB when a destination waypoint is active. RMC and RMB are the recommended minimum data to be provided by a GNSS receiver. All data fields should be provided, null fields used only when data is temporarily unavailable.
$--RMC, hhmmss.ss, A, llll.ll,a, yyyyy.yy, a, x.x, x.x, xxxxxx, x.x,a, a*hh<CR><LF>
Mode indicator
(see Notes 2 and 3)
Magnetic variation,
degrees, E/W (see Note 1)
Date: dd/mm/yy
Course over ground, degrees true
Speed over ground, knots
Longitude, E/W
Latitude, N/S
Status (see Note 3) A = data valid V = navigation receiver warning
UTC of position fix
NOTE 1
Easterly variation (E) subtracts from true course. Westerly variation (W) adds to true course.
NOTE 2
Positioning system mode indicator:
A = Autonomous mode
D = Differential mode
E = Estimated (dead reckoning) mode
M = Manual input mode
S = Simulator mode
N = Data not valid
NOTE 3
The positioning system mode indicator field supplements the positioning system status field (field No. 2) which should be set to V = invalid for all values of mode indicator except for A = Autonomous
Page 43
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.17
OSD – Own ship data
Heading, course, speed, set and drift summary. Useful for, but not limited to radar/ARPA applications. OSD gives the movement vector of the ship based on the sensors and parameters in use.
$--OSD, x.x,A,x.x, a,x.x,a,x.x,x.x,a*hh<CR><LF>
Speed units, K = km/h; N = knots;
S = statute miles/h
Vessel drift (speed) Manually
Entered
Vessel set, degrees true
Speed reference,B/M/W/R/P (see Note)
Vessel speed
Course reference, B/M/W/R/P (see Note)
Vessel course, degrees true
Heading status: A = data valid, V = data invalid
Heading, degrees true
NOTE
Reference systems on which the calculation of vessel course and speed is based. The values of course and speed are derived directly from the referenced system and do not additionally include the effects of data in the set and drift fields.
B = bottom tracking log
M = manually entered
W = water referenced
R = radar tracking (of fixed target)
P = positioning system ground reference.
Page 44
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.18
RSD – Radar system data
Radar display setting data.
$--RSD, x.x, x.x,x.x, x.x,x.x, x.x,x.x, x.x,x.x, x.x, x.x, a, a*hh<CR><LF>
Display rotation (see Note 1)
Range units, K = km
N = nautical miles
S = statute miles
Range scale in use
Cursor bearing, degrees clockwise from 0°
Cursor range, from own ship
EBL 2, degrees
VRM 2, range
Origin 2 bearing (see Note 2)
Origin 2 range (see Note 2)
Bearing line 1 (EBL1), degrees from 0°
Variable range marker 1 (VRM1), range
Origin 1 bearing (see Note 2) degrees from 0°
Origin 1 range (see Note 2), from own ship
NOTE 1
Display rotation: C = course-up, course-over-ground up, degrees true H = head-up, ship's heading (centre-line) 0° up N = north-up, true north is 0° up
NOTE 2
Origin 1 and origin 2 are located at the stated range and bearing from own ship and provide for two independent sets of variable range markers (VRM) and electronic bearing lines (EBL) originating away from own ship position.
Page 45
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.19
TTM – Tracked target message
Data associated with a tracked target relative to own ship's position.
$--TTM, xx, x.x, x.x, a, x.x, x.x, a, x.x, x.x, a, c--c, a, a, hhmmss.ss, a *hh<CR><LF>
Type of acquisition
A = Automatic
M = manual
R = reported
Time of data (UTC)
Reference target (see Note 2)= R,
null otherwise
Target status (see Note 1)
Target name
Speed/distance units, K/N/S
Time to CPA, min., "-" increasing
Distance of closest-point-of-approach
Target course, degrees true/relative (T/R)
Target speed
Bearing from own ship, degrees true/relative (T/R)
Target distance from own ship
Target number, 00 to 99
NOTE 1 Target status:
L = Lost, tracked target has been lost
Q = Query, target in the process of acquisition
T = Tracking
NOTE 2 Reference
NOTE
All the position data sent out via TTM and TTD is always relative to the CCRP
Page 46
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.20
DTM - Datum reference
Local geodetic datum and datum offsets from a reference datum. This sentence is used to define the datum to which a position location, and geographic locations in subsequent sentences, are referenced. Latitude, longitude and altitude offsets from the reference datum, and the selection of the reference datum, are also provided.
Cautionary notes: the datum sentence should be transmitted immediately prior to every positional sentence (e.g. GLL, BWC, WPL) which is referenced to a datum other than WGS84, the datum recommended by IMO.
For all datums the DTM sentence should be transmitted prior to any datum change and periodically at intervals of not greater than 30 s.
$--DTM,ccc,a,x.x,a,x.x,a, x.x,ccc*hh<CR><LF>
Reference datum
Altitude offset, m (see Note 3)
Lon offset, min, E/W (see Note 3)
Lat offset, min, N/S (see Note 3)
Local datum subdivision code (see Note 2)
Local datum:
(see Note 1)
NOTE 1 Three character alpha code for local datum. If not one of the listed earth­centred datums, or 999 for user defined datums, use IHO datum code from International Hydrographic Organisation Publication S-60, Appendices B and C. Null field if unknown. This field should be set to 999 when manual offsets are entered and in use by the position fixing device.
NOTE 2 One character subdivision datum code when available or user defined reference character for user defined datums, null field otherwise. Subdivision character from IHO Publication S-60, Appendices B and C.
NOTE 3 Latitude and longitude offsets are positive numbers, the altitude offset may be negative. Offsets change with position: position in the local datum is offset from the position in the reference datum in the directions indicated:
WGS84 = W84
WGS72 = W72 SGS85 = S85 PE90 = P90
WGS84 = W84
WGS72 = W72
SGS85 = S85
PE90 = P90
User defined = 999
IHO datum code (see Note 4)
Page 47
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.21
Plocal datum = Pref datum + offset
When field 1 contains a value of 999, these fields may not be null, and should contain the manually entered or user defined offsets.
NOTE 4 Users should be aware that chart transformations based on IHO S60 parameters may result in significant positional errors when applied to chart data.
WPL – Waypoint location
Latitude and longitude of specified waypoint.
$--WPL, llll.ll, a, yyyyy.yy, a, c--c*hh<CR><LF>
Waypoint identifier
Waypoint longitude, E/W
Waypoint latitude, N/S
NOTE 1
Waypoints with name field are not accepted.
Page 48
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.22
RTE – Routes
Waypoint identifiers, listed in order with starting waypoint first, for the identified route. Two modes of transmission are provided: "c" indicates that the complete list of waypoints in the route is being transmitted; "w" indicates a working route where the first listed waypoint is always the last waypoint that had been reached (FROM), while the second listed waypoint is always the waypoint that the vessel is currently heading for (TO) and the remaining list of waypoints represents the remainder of the route.
$--RTE, x.x, x.x, a, c--c, c--c,...... c--c*hh<CR><LF>
Waypoint "n" identifier (see Note 1)
Additional waypoint identifiers (see Note 1)
Waypoint identifier
Route identifier
Message mode: c = complete route, all waypoints
w = working route, first listed waypoint is "FROM",
second is "TO" and remaining are rest of route
Sentence number (see Note 2)
Total number of sentences being transmitted (see Note 2)
NOTE 1
A variable number of waypoint identifiers, up to "n", may be included within the limits of allowed sentence length. As there is no specified number of waypoints, null fields are not required for waypoint identifier fields.
NOTE 2
A single route may require the transmission of multiple sentences, all containing identical field formats when sending a complex message. The first field specifies the number of sentences, minimum value = 1. The second field identifies the order of this sentence (sentence number), minimum value = 1. For efficiency, it is permitted that null fields be used in the additional sentences when the data is unchanged from the first sentence. (Note that this practice can lead to the incorrect assembly of sentences if there is a high risk of loss of sentence.).
Page 49
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.23
MWD – Wind direction and speed
The direction from which the wind blows across the earth’s surface, with respect to north, and the speed of the wind.
$--MWD, x.x,T,x.x,M,x.x,N,x.x,M*hh<CR><LF>
Wind speed, m/s
Wind speed, knots
Wind direction, 0° to 359° magnetic
Wind direction, 0° to 359° true
MWV – Wind speed and angle
When the reference field is set to R (Relative), data is provided giving the wind angle in relation to the vessel's bow/centreline and the wind speed, both relative to the (moving) vessel. Also called apparent wind, this is the wind speed as felt when standing on the (moving) ship.
When the reference field is set to T (Theoretical/calculated wind), data is provided giving the wind angle in relation to the vessel's bow/centreline and the wind speed as if the vessel was stationary. On a moving ship, these data can be calculated by combining the measured relative wind with the vessel's own speed.
Example 1 If the vessel is heading west at 7 knots and the wind is from the east at 10 knots the relative wind is 3 knots at 180°. In this same example the theoretical wind is 10 knots at 180° (if the boat suddenly stops the wind will be at the full 10 knots and come from the stern of the vessel 180° from the bow).
Example 2 If the vessel is heading west at 5 knots and the wind is from the southeast at 7,07 knots the relative wind is 5 knots at 270°. In this same example the theoretical wind is 7,07 knots at 225° (if the boat suddenly stops the wind will be at the full 7,07 knots and come from the port-quarter of the vessel 225° from the bow).
$--MWV, x.x, a, x.x, a, A *hh<CR><LF>
Status, A = data valid V= data invalid
Wind speed units, K = km/h
M = m/s
N = knots
Wind speed
Reference, R = relative, T = true
Wind angle, 0° to 359°
Page 50
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.24
DPT – Depth
Water depth relative to the transducer and offset of the measuring transducer. Positive offset numbers provide the distance from the transducer to the waterline. Negative offset numbers provide the distance from the transducer to the part of the keel of interest.
$--DPT, x.x, x.x, x.x*hh<CR><LF>
Maximum range scale in use
Offset from transducer, in metres (see Notes 1 and 2)
Water depth relative to the transducer, in metres
NOTE 1
“positive” = distance from transducer to water line; “-“ = distance from transducer to keel.
NOTE 2
For IEC applications, the offset should always be applied so as to provide depth relative to the keel.
DBT – Depth below transducer
Water depth referenced to the transducer.
$--DBT, x.x, f, x.x, M, x.x, F*hh<CR><LF>
Water depth, fathoms
Water depth, m
Water depth, feet
ROR – Rudder order status
Angle ordered for the rudder.
$--ROR,x.x,A,x.x,A,a*hh<CR><LF>
Command source location (as TRC)
Port rudder order (see Notes 1 and 2)
Status A = data valid, V = data invalid
Starboard (or single) rudder order (see Notes 1 and 2)
Status A = valid,V = data invalid
Page 51
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.25
NOTE 1
Relative measurement of rudder order angle without units, "-" = bow turns to port.
NOTE 2
The status field should not be a null field.
RSA – Rudder sensor angle
Relative rudder angle, from rudder angle sensor.
$--RSA, x.x, A, x.x, A*hh<CR><LF>
Port rudder sensor (see Notes 1 and 2)
Status A = data valid,
V = data invalid
Starboard (or single) rudder sensor
(see Notes 1 and 2)
Status A = valid,
V = data invalid
NOTE 1
Relative measurement of rudder angle without units, "-" = bow turns to port. Sensor output is proportional to rudder angle but not necessarily 1:1.
NOTE 2
The status field should not be a null field.
Page 52
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.26
XDR – Transducer measurements
Measurement data from transducers that measure physical quantities such as temperature, force, pressure, frequency, angular or linear displacement, etc. Data from a variable number of transducers measuring the same or different quantities can be mixed in the same sentence.
This sentence is designed for use by integrated systems as well as transducers that may be connected in a "chain" where each transducer receives the sentence as an input and adds on its own data fields before retransmitting the sentence.
$--XDR, a, x.x, a, c--c,................ a, x.x, a, c--c*hh<CR><LF>
Transducer "n" (see Note 1)
Data, variable number of transducers
Transducer No. 1 ID
Units of measure, transducer No. 1
(see Note 2)
Measurement data, transducer No. 1
Transducer type, transducer No. 1 (see
Note 2)
NOTE 1
Sets of the four fields "type-data-units-ID" are allowed for an undefined number of transducers. Up to "n"transducers may be included within the limits of allowed sentence length; null fields are not required except where portions of the "type-data-units-ID" combination are not available.
NOTE 2
Allowed transducer types and their units of measure are as specified in below table – see next page.
Page 53
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.27
Transducer
Type
field
Units Comments
Temperature
C
C = degrees Celsius
Angular
displacement
A D = degrees "-" = anticlockwise
Absolute humidity
B
K = kg/m3
Kilograms per cubic metre
Linear
displacement
D M = metre "-" = compression
Frequency
F
H = Hertz
Salinity
L
S = ppt
ppt = parts per thousand
Force
N
N = newtons
"-" = compression
Pressure
P
P = pascals
"-" = vacuum
Flow rate
R
l = litres/s
Tachometer
T
R = revolutions/min
Humidity
H
P = per cent
Volume
V
M = cubic metres
Voltage
U
V = volts
Current
I
A = amperes
Switch or valve S None (null)
1 = ON, CLOSED;
0 = OFF, OPEN
Generic
G None (null) x.x = variable data
Page 54
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.28
2.4 Serial Line 4
It is possible to receive RS422 or RS232 standard signal at 4800 bps indifferently on TB2 (422). Note that the circuit is able to receive at 4800 bps also with RS232 connection, but this is not a standard connection according to the IEC 61162-2 standard.
RS 422 Interface Listener Connection
+ IN_4
"A" Data Input
- IN_4
"B" Data Input
SHLD_4
“C” insulated Ground
Input Load
≥ 3 K
RS 232 Interface Listener Connection
- IN_4
RX Data Input
SHLD_4 and + IN_4
Insulated ground
Input Load
≥ 3 K
This serial line complies to IEC 61162-1 and IEC 61162-2. Accepted sentences: VBW and VHW.
Page 55
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.29
VBW – Dual ground/water speed
Water-referenced and ground-referenced speed data.
$--VBW, x.x, x.x, A, x.x, x.x, A, x.x, A, x.x, A*hh<CR><LF>
Status (see Note 2): stern ground speed,
A = data valid, V = data invalid
Stern transverse ground speed (see Note 1),
knots
Status (see Note 2): stern water speed,
A = data valid, V = data invalid
Stern transverse water speed (see Note 1), knots
Status (see Note 2), ground speed,
A = data valid, V = data invalid
Transverse ground speed (see Note 1), knots
Longitudinal ground speed (see Note 1), knots
Status (see Note 2): water speed, A = data valid, V = data invalid
Transverse water speed (see Note 1), knots
Longitudinal water speed (see Note 1), knots
NOTE 1
Transverse speed: "-" = port,
Longitudinal speed: "-" = astern.
NOTE 2
The status field should not be a null field.
VHW – Water speed and heading
The compass heading to which the vessel points and the speed of the vessel relative to the water.
$--VHW, x.x, T, x.x, M, x.x, N, x.x, K*hh<CR><LF>
Speed, km/h
Speed, knots
Heading, degrees magnetic
Heading, degrees true
Page 56
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.30
2.5 Serial Line 5
It is possible to receive RS422 or RS232 standard signal at 2400 or 4800 bps indifferently on TB6 (232+422_2).
SCHEME 1 IN + IN ­GND 422+ 422­232
RS422 Interface Listener Connection
+ IN
"A" Data Input
- IN
"B" Data Input
GND
“C” Ground
Input Load
3 K
RS232 Interface Listener Connection
- IN
RX Data Input
GND and + IN
Ground
Input Load
3 K
RS422 Output Talker Connection
+ OUT
"A" Data Output
- OUT
"B" Data Output
GND
“C” Ground
Output Drive
150 mA
RS 232 Output Talker Connection
TX
TX Data Output
GND
GND
Output Drive
10 mA
Page 57
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.31
2.6 Serial Line 6
It is possible to receive RS422 or RS232 standard signal at 2400 or 4800 bps indifferently on TB12 (232+422_1).
RS 422 Interface Listener Connection
+ IN_6
"A" Data Input
- IN_6
"B" Data Input
GND
“C” Ground
Input Load
3 K
RS 232 Interface Listener Connection
- IN_6
RX Data Input
GND and + IN_6
Ground
Input Load
3 K
RS 422 Output Talker Connection
+ OUT_6
"A" Data Output
- OUT_6
"B" Data Output
GND
“C” Ground
Output Drive
150 mA
RS 232 Output Talker Connection
TX_6
TX Data Output
GND
GND
Output Drive
10 mA
Page 58
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.32
2.7 Serial Line 7
It is possible to receive RS422 or RS232 standard signal at 4800 indifferently on TB10 (422). Note that the circuit is able to receive at 4800 bps also with RS232 connection, but this is not a standard connection according to the IEC 61162-2 standard.
RS 422 Interface Listener Connection
+ RX_7
"A" Data Input
- RX_7
"B" Data Input
GND
“C” Ground
Input Load
≥ 3 K
RS 232 Interface Listener Connection
- RX_7
RX Data Input
GND and + RX_7
Ground
Input Load
≥ 3 K
RS 232 Output Talker Connection
TX_7
TX Data Output
GND
GND
Output Drive
10 mA
The output is the source of RAALR sentences.
Page 59
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.33
2.8 Serial Line 8
It is possible to receive RS422 or RS232 standard signal at 4800 indifferently on TB4 (422). Note that the circuit is able to receive at 4800 bps also with RS232 connection, but this is not a standard connection according to the IEC 61162-2 standard. Using unconventional sensors setup is possible to set if the alert management system is a BAM or a Legacy management system (supporting ALR and ACK sentences)
ACN – Alert command
This sentence is used for acknowledge, silence, responsibility transfer and to request repeat of alert details in case the reception process has detected, based on ALC, that ALF has been missed.
Responsibility transferred is used for a special conditional state of an alert. In this state the source of an alert indicates the alert visually as an acknowledged alert (i.e. no flashing indication nor audible signal). In this state the source of an alert re-raises an unacknowledged alert, if the source of the alert is unable to receive heartbeat (HBT) sentences from the sender of the sentence.
This sentence cannot be queried.
$--ACN,hhmmss.ss, aaa, x.x, x.x, c, a*hh <CR><LF>
Sentence status flag (see Note 6)
Alert command, A, Q, O or S (see Note 5)
Alert Instance, 1 to 999999 (see Note 4)
Alert Identifier (see Note 3)
Manufacturer mnemonic code (see Note 2)
Time (see Note 1)
NOTE 1
Release time of the alert command. (e.g. for VDR purposes), optional can be a null field. Sender is allowed to use all alternatives defined in IEC 61162­1:2010, Table 5, Field type summary. The receiver is allowed to ignore the content of this field. If the receiver does not ignore this field it should support all alternatives defined in IEC 61162-1:2010, Table 5, Field type summary.
NOTE 2
Used for proprietary alerts defined by the manufacturer. For standardized alerts this should be a null field.
NOTE 3
The alert identifier is unique within a single alert source. The alert identifier is a variable length integer field of maximum 7-digit integer. It identifies the type of the alert e.g. a “lost target” alert. Number range 10000-9999999 is reserved for proprietary alerts. Alert Identifier examples: “001”, “2456789”, “245”
Page 60
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.34
NOTE 4
The alert instance identifies the current instance of an alert to distinguish alerts of the same type (Alert identifier) and from the same source (e.g. dangerous target). Alert instance is maximum 6-digit integer from 1 to
999999. The number of alert instance can be freely defined by the manufacturer as long as it is unique for one type of alert (alert identifier). It is not permitted to modify the alert instance within a life cycle of a distributed alert (from ‘active-unacknowledged’ state until ‘normal’ state is reached). It can also be a null field, when there is only one alert of that type.
NOTE 5
This should not be null field acknowledge: A request / repeat information: Q responsibility transfer: O, silence: S
NOTE 6
This field should be “C” and should not be null field. This field indicates a command. A sentence without “C” is not a command.
ALC – Cyclic alert list
The purpose of this sentence is to satisfy the needs for a safe and consistent data distribution with a minimum of data traffic. Each change on an alert’s data leads to an incremented Revision counter. So an alert processing device only needs to check the alert entries in the ALC messages to ensure that no ALF message has been lost. In the case where an ALF message has been lost, the missing message can be requested by sending a request alert command (see Clause K.2).
The ALC sentence provides condensed ALF sentence information. It contains the identifying data for each present alert of one certain source/device so that the receiver can understand which ALF has been missed (and retransmission of ALF can be requested by using the ACN sentence). It shall be published cyclically at least every 30 s by each alert generating device.
The cyclic alert list transmission shall never stop. When all alerts are in normal state the cyclic alert list is empty, i.e. the number of alert entries is 0.
The length of this sentence varies with the number of alerts (number of list entries) that are being generated. In cases where the needed number of entries exceeds the permitted sentence length the number of sentences is increased.
Alert entry n (see Note 4)
$--ALC, xx, xx, xx, x.x, aaa, x.x ,x.x ,x.x,……..,aaa, x.x, x.x, x.x*hh <CR><LF>
Additional Alert entries (see Note 4)
Revision counter Alert entry 1
Alert instance (see Note 4)
Alert identifier
Manufacturer mnemonic code
Number of alert entries (see Note 3)
Sequential message identifier, 00 to 99 (see Note 2)
Sentence number, 01 to 99 (see Note 1)
Total number of sentences for this message, 01 to 99 (see Note 1)
Page 61
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.35
NOTE 1
The first field specifies the total number of sentences used for a message, minimum value 1. The second field identifies the order of this sentence in the message, minimum value 1. These cannot be null fields.
NOTE 2
The sequential message identifier relates all sentences that belong to a group of multiple sentences (i.e. message). Multiple sentences (see Note 1) with the same sequential message identifier, make up one message.
NOTE 3
Contains the number of alert entries transported within this sentence.
NOTE 4
Alert entry 0 – n: Each alert entry consists of four fields:
Manufacturer Identifier (see ALF Manufacturer Identifier);
Alert Identifier (see ALF Alert Identifier);
Alert instance (see ALF Alert instance);
Revision Counter (see ALF Revision Counter).
Each entry identifies a certain alert with a certain state. It is not allowed that an alert entry is split between two ALC sentences.
ALF – Alert sentence
This sentence is used to report an alert condition and the alert state of a device. An ALF message shall be published for an alert each time the alert information in this sentence changes and on alert request (see Clause K.2).
To transmit additional alert description text (see Note 12), optionally a second ALF sentence may be transmitted.
$$--ALF, x, x, x, hhmmss.ss, a, a, a, aaa, x.x, x.x, x.x, x, c---c*hh <CR><LF>
Alert text (see Note 12)
Escalation counter, 0 to 9 (see Note 11)
Revision counter, 1 to 99 (see Note 10)
Alert instance, 1 to 999999 (see Note 9)
Alert identifier (see Note 8)
Manufacturer mnemonic code (see Note 7)
Alert state, A, S, N, O, U or V (see Note 6)
Alert priority, E, A, W or C (see Note 5)
Alert category, A, B or C (see Note 4)
Time of last change (see Note 3)
Sequential message identifier, 0 to 9 (see Note 2)
Sentence number, 1 to 2 (see Note 1)
Total number of ALF sentences for this message, 1 to 2 (see Note 1)
Page 62
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.36
NOTE 1
The first field specifies the total number of sentences used for a message, minimum value 1. The second field identifies the order of this sentence in the message, minimum value 1. These cannot be null fields. When the sentence number is 2, the following Alert category, Alert priority and Alert state can be null fields.
NOTE 2
The sequential message identifier relates all sentences that belong to a group of multiple sentences (i.e. message). Multiple sentences (see Note 1) with the same sequential message identifier, make up one message.
NOTE 3
Time should represent the last time the data within the alert message has changed. For example changing the alert text by in-/decrementing a contained counter or count down should cause a revision of alert message and a new time. Time is an optional field. The time-field is additional information about when this happened and not used for decision making. There is no mandatory requirement for time synchronization between the equipment. It should be either a null field (if not used) or UTC (if used). Sender is allowed to use all alternatives defined in IEC 61162-1:2010, Table 5, Field type summary. The receiver is allowed to ignore the content of this field. If the receiver does not ignore this field, it should support all alternatives defined in IEC 61162-1:2010, Table 5, Field type summary.
NOTE 4
The alert category is in compliance with the category definition as described in INS Performance Standard (MSC.252(83)) and Bridge Alert Management Performance Standard (MSC.302(87)): A, Category A: Alerts, where information at the operator unit is directly assigned to the function generating the alert is necessary, as decision support for the evaluation of the alert-related condition, e.g. graphical information of danger of collision or graphical information of danger of grounding. B, Category B: Alerts where no additional information for decision support is necessary besides the information which can be presented using the alert source and the text description of the alert. C, Category C: Alerts that cannot be acknowledged on the bridge but for which information is required about the status and treatment of the alerts, e.g. certain alerts from the engine.
NOTE 5
Alert priority: Emergency Alarm: E, for use with Bridge Alert Management, (see IMO MSC.302(87)) Alarm: A Warning: W Caution: C
Page 63
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.37
NOTE 6
active – unacknowledged: V active – silenced: S active – acknowledged or active: A active – responsibility transferred: O rectified – unacknowledged: U normal: N
NOTE 7
Used for proprietary alerts defined by the manufacturer. For standardized alerts this should be a null field.
NOTE 8
The alert identifier is unique within a single alert source. The alert identifier is a variable length integer field of maximum a 7-digit integer. It identifies the type of the alert, e.g. a “lost target” alert. Number range 10000-9999999 is reserved for proprietary alerts. Alert Identifier examples: “001”, “2456789”, “245”.
NOTE 9
The alert instance identifies the current instance of an alert to distinguish alerts of the same type (Alert identifier) and from the same source (e.g. dangerous target). Alert instance is maximum a 6-digit integer from 1 to
999999. The number of alert instance can be freely defined by the manufacturer as long as it is unique for one type of alert (alert identifier). It is not permitted to modify the alert instance within a life cycle of a distributed alert (from ‘active-unacknowledged’ state until ‘normal’ state is reached). It can be also a null field, when there is only one alert of that type.
NOTE 10
The revision counter is the main method to follow an up-to-date status. The revision counter is also unique for each instance of alert. The revision counter starts with 1 and the step for an increment is 1. The count resets to 1 after 99 is used. The revision counter increments on each change of content of any field of the alert.
NOTE 11
The escalation counter is presenting the number of alert escalations after time expiration during the state active-unacknowledged. The escalation counter starts with 0 and the step for increment is 1. The count resets to 1 after 9 is used. The alert escalation can be the escalation from warning into warning (activation of audible signal only), the escalation from warning to alarm, or the escalation from alarm to alarm with the activation of backup navigator alarm.
Page 64
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.38
NOTE 12
This field is used for the Alert title which is mandatory and for an additional alert description which is optional.
The first ALF sentence transmits the Alert title. An Alert title is maximum
16 characters short form of the alert text.
The optional second ALF sentence transmits the additional alert
description. Additional alert description is the long description of the alert. The additional alert description contains more information for decision making (i.e. alert description text).
The second ALF sentence uses null fields for Time of last change, Alert
category, Alert priority, and Alert state to allow longer text. The actual number of valid characters should be such that the total number of characters in a sentence does not exceed the “82”-character limit.
Some equipment standards specify alert text longer than 16 characters
(for example the AIS standard has defined some alerts to be coded with ALR-sentence and with text longer than 16 characters). In such cases, the first ALF sentence is used for the first 16 characters of the alert text as alert title and the second ALFsentence to carry the full alert text. EXAMPLES: $IIALF,1,1,0,124304.50,A,W,A,,192,1,1,0,LOST TARGET*14<CR><LF> $IIALF,2,1,1,081950.10,B,A,S,XYZ,0512,1,2,0,HEADING LOST*2D<CR><LF> $IIALF,2,2,1,,,,,XYZ,0512,1,2,0,NO SYSTEM HEADING AVAILABLE*0D<CR><LF>
ARC – Alert command refused
This sentence is used for:
Category A or C alerts (see IMO MSC.302(87)), for which it is illegal to accept acknowledge or responsibility transfer, e.g. not enough information for decision support
available or the source of acknowledgement is not acceptable, Note that in a properly working system such attempts should not happen.
Category B (see IMO MSC.302(87)), if the source of acknowledge is not acceptable.
$--ARC, hhmmss.ss, aaa, x.x, x.x, c*hh <CR><LF>
Refused alert command, A, Q, O or S (see Note 5)
Alert instance, 1 to 999999 (see Note 4)
Alert identifier (see Note 3)
Manufacturer mnemonic code (see Note 2)
Time (see Note 1)
NOTE 1
Release time of the Alert Command Refused, e.g. for VDR purposes, optional, can be a null field. The sender is allowed to use all alternatives defined in IEC 61162-1:2010, Table 5, Field type summary. The receiver is allowed to ignore the content of this field. If the receiver does not ignore this field it should support all alternatives defined in IEC 61162-1:2010, Table 5, Field type summary.
Page 65
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.39
NOTE 2
Used for proprietary alerts, defined by the manufacturer. For standardized alerts this should be a null field.
NOTE 3
The alert identifier is unique within a single alert source. The alert identifier is a variable length integer field of maximum a 7-digit integer. It identifies the type of the alert, e.g. a “lost target” alert. Number range 10000-9999999 is reserved for proprietary alerts. Alert Identifier examples: “001”, “2456789”, “245”.
NOTE 4
The alert instance identifies the current instance of an alert to distinguish alerts of the same type (Alert identifier) and from the same source (e.g. dangerous target). Alert instance is maximum a 6-digit integer from 1 to
999999. The number of alert instance can be freely defined by the manufacturer, as long as it is unique for one type of alert (alert identifier). It is not permitted to modify the alert instance within a life cycle of a distributed alert (from ‘active-unacknowledged’ state until ‘normal’ state is reached). It can also be a null field, when there is only one alert of that type.
NOTE 5
Refused Alert Command: Indicates refused “Alert command” of a corresponding ACN sentence. This should not be a null field. acknowledge: A request / repeat information: Q responsibility transfer: O silence: S
EVE – General event message
This sentence is used to transmit events (e.g. actions by the crew on the bridge) with a time stamp.
$--EVE,hhmmss.ss,c--c,c--c*hh<CR><LF>
Event description
Tag code used for identification of source of event (see Note)
Event time (see Note)
NOTE This may be a null field.
Page 66
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.40
HBT – Heartbeat supervision sentence
This sentence is intended to be used to indicate that equipment is operating normally, or for supervision of a connection between two units.
The sentence is transmitted at regular intervals specified in the corresponding equipment standard. The repeat interval may be used by the receiving unit to set the time-out value for the connection supervision.
$--HBT,x.x,A,x*hh<cr><lf>
Sequential sentence identifier (see Note 3)
Equipment status (see Note 2)
Configured repeat interval (see Note 1)
NOTE 1
Configured autonomous repeat interval in seconds. This field should be set to NULL in response to a query if this feature is supported.
NOTE 2
Equipment in normal operation A = yes, V = no This field can be used can be used to indicate the current equipment status. This could be the result of an built-in integrity testing function.
NOTE 3
The sequential sentence identifier provides a message identification number from 0 to 9 that is sequentially assigned and is incremented for each new sentence. The count resets to 0 after 9 is used.
ACK – Acknowledge alarm
Acknowledge device alarm. This sentence is used to acknowledge an alarm condition reported by a device.
$--ACK,xxx*hh<CR><LF>
Unique alarm number (identifier) at alarm source
ALR – Set alarm state
Local alarm condition and status. This sentence is used to report an alarm condition on a device and its current state of acknowledgement.
$--ALR,hhmmss.ss,xxx,A, A,c--c*hh<CR><LF>
Alarm’s description text
Alarm’s acknowledge state, A = acknowledged
V = unacknowledged
Alarm condition (A = threshold exceeded, V = not exceeded)
Unique alarm number (identifier) at alarm source
Time of alarm condition change, UTC
Page 67
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.41
Page 68
Argus Radar - SERIAL INTERFACE SPECIFICATIONS
988-10187-004 2.42
Antares PCB Serial In / Out Port Summary
Processor
Device and
Connector Name
Used For
Input
Type
Output
Type
Input /
Output Baud
Rate
A
ttyS0 Standard Out Console 232 232 57600
ttyS1 Keyboard 232 232 38400
ttyS2 TB10 Wind Sensor /RAALR 422/232 232 4800
ttyS3 TB4 BAM 422/232 232 4800
B
ttyS0 Standard Out Console 232 232 57600
ttyS1 TB9 Gyro 422/232 422 4800 / 38400
ttyS2 TB8
AIS In / AIS ACK and
TTD-TLB Out
422/232 422 38400
ttyS3 TB3 INS / EPFS / ECDIS 422/232 422 4800 / 38400
ttyS4 TB2 Speed Log 422/232 422 4800
ttyS5 TB6 Serial TXRX 1 422/232 422/232 4800
ttyS6 TB12 Serial TXRX 2 422/232 422/232 4800
Page 69
Argus Radar - RADAR CONFIGURATION
988-10187-004 3.1
CHAPTER 3
RADAR CONFIGURATION
3.1 How to access the Radar Configuration
To access the Radar configuration a password is required. It will then be possible to make the necessary adjustments in the System Configuration, plus some Debug and Simulation facilities are available.
After enabling this function, it will be open for adjustment until the system is switched to STAND BY.
3.1.1 Radar Configuration
To obtain access to the Radar Configuration MENU, please follow the procedure below. It will take you into the Super User Mode of the Argus system. Remember to save all settings and exit the mode again as soon as configurations are completed!
1) Press “Radar Configuration” in the Main Menu bar on the display:
2) Enter the password "HIGH" using the alphanumerical keypad:
Page 70
Argus Radar - RADAR CONFIGURATION
988-10187-004 3.2
3) Before entering the setup, a check dialog appear on screen with the following warning:
Fig 3.1.1 Security Check
The console setup is necessary for the commissioning of the system. From the console display, using only the trackball, it's possible to configure and adjust all parts of the system. Several functions of the console setup can normally only be accessed by an authorized service engineer using a password to gain access. Please contat Navico service if you need assistance.
Fig 3.1.2 Radar configuration Menu
C
D
E
G
L
O
Page 71
Argus Radar - RADAR CONFIGURATION
988-10187-004 3.3
3.2 Gyrocompass Configuration
To configure the Argus radar settings for connected gyro:
Press the "A" button in fig. 3.1.2, page 3.2, to open the following window:
Figure 3.2.1 Gyro compass Configuration Menu
The first row, “Gyro Connected As” indicates the type of Gyro. By pressing the associated button will open the following list:
The selection changes the type of interface used, and for NMEA (referring to NMEA 0183) serial, the baud rate.
By pressing the “Negative Phases” associated button, another list will open, showing the possibilities of Gyro ratio.
The list is valid and activated only when the Gyro is not serial.
Use the list to define how many cycles of stepper or synchro are calculated for each 360° Gyro turn.
Page 72
Argus Radar - RADAR CONFIGURATION
988-10187-004 3.4
Examples:
1:360 means that each stepper or synchro cycle corresponds to 1 degree and 1 complete
360° turn correspond to 360 cycles. For this setup the gyro resolution will be 1/6°
1:36 means that each stepper or synchro cycle corresponds to 10 degree, and 1 complete
360° turn correspond to 36 cycles.
Normally, for most Gyro types, the Gyro Ratio is 1:360.
Other settings are available with analogue gyro, one is the “Reference generated Internally” checkbox that is the usual setup for stepper gyro.
When the reference signal to sample phases is external, the checkbox should not be activated.
Another checkbox “Negative Phases” is available in stepper mode, and it should be checked, when the voltage on phase is going from zero to negative.
The S1, S2, S3 symbols can be highlighted and reflect exactly the same gyro phases states described in the analogue gyro section.
The user manual explains the analogue gyro interface operation.
Note that this kind of interface does not permit equal phase levels, or lack of reference signal (synchro mode). Failure warnings due to incorrect settings can only be cleared by correcting the gyro settings.
The gyro preset is necessary also because this kind of interface is not absolute, but receives incremental pulses and therefore needs a preset value taken when the ship’s heading is stable.
Page 73
Argus Radar - RADAR CONFIGURATION
988-10187-004 3.5
3.3 Speed LOG Configuration
In this menu it is possible to configure the connection of a Speed LOG to the radar, by pressing the "B" button on fig. 3.1.2, page 3.2, the following window will be displayed:
Figure 3.3.1 Speed Log Configuration
The first row indicates the type of Speed Log connected. By pressing the asociated button, the following list will open:
If the speed log signal is NMEA (referring to NMEA 0183), it is necessary to select the Input where it is connected, push the B button on fig. 3.1.2, page 3.2, to switch between the possibilities.
Type Function
100 p/NM
PIT dry contact, 100 pulses per NM
200 p/NM
PIT dry contact, 200 pulses per NM
400 p/NM
PIT dry contact, 400 pulses per NM
120 p/mt
FOR signal input, 120 pulses per meter
20000 p/NM
FOR signal input , 20000 pulses per NM
NMEA
RS232/422 NMEA 0183 serial connection
Page 74
Argus Radar - RADAR CONFIGURATION
988-10187-004 3.6
3.4 Own Ship Dim. and Weight
By pressing the “Own Ship Dim. and Weight " button, the following window will appear:
Figure 3.4.1 Own Ship Dim. and Weight
In the window, it is possible to insert the following data:
Weight: by pressing the relevant button will open a list:
The list shows a selection of 8 pre-defined Tonnage / ROT values. The chosen selection related to the tonnage of the ship will be used to define the Rate of Turn for the Trial Manoeuvre computing.
Be sure to select a relevant value, otherwise the Trial Manoeuvre will provide incorrect information;
Length: look to the help line for correct use of the 3 Mouse Operating Push Buttons in
order to decrease, increase the length value or input a new length value in meters.
Width: look to the help line for correct use of the 3 Mouse Operating Push Buttons in order to decrease, increase the width value or input a new width value in meters.
Page 75
Argus Radar - RADAR CONFIGURATION
988-10187-004 3.7
3.5 Conning and EPFS Pos. Configuration Menu
By pressing the “Conning and EPFS Position” button, the following window will appear:
Figure 3.5.1 Conning and EPFS Position
Conning Position: Look to the help line for correct use of the 3 Mouse Operating Push Buttons in order to decrease, increase the X or Y value or input a new X or Y value in meters. A picture of the ship profile and a text on line will be drawn in order to help the operator to insert the correct values. This is the position of the EPFS referred to the graphical shape as indicated in the figure. This value is used to calculate the exact geographical coordinate of the antenna position. Length and width are not used when AIS is connected, instead they are extracted from the VDO static message. The CCRP will be located at the conning position.
EPFS Ant. Position: Look to the help line for correct use of the 3 Mouse Operating Push Buttons in order to decrease, increase the X or Y value or input a new X or Y value in meters. A picture of the ship profile and a text on line will be drawn in order to help the operator to insert the correct values. This is the position of the EPFS referred to the graphical shape as indicated in the figure. This value is used to calculate the exact geographical coordinate of the GPS antenna position.
EPFS Datum Check: Accept the DTM sentence when the checkbox is signed. The datum is used to compensate local geographic coordinates with an offset with reference to WGS-
84.
Page 76
Argus Radar - RADAR CONFIGURATION
988-10187-004 3.8
3.6 Unconventional sensor Cfg.
By pressing the “Unconventional sensor Cfg” button, the following window will appear:
Figure 3.6.1 Unconventional sensor Cfg.
With this function, it is possible to configure specific sensors (A) in addition to the conventional sensors. For example, a GPS backup is useful when connected to ECDIS, a wind sensor for conning wind information, an alarm monitoring system.
The menu above, as well as identifying the selected sensor, has the characteristic of being able to set the serial port speed.
NOTE
This operation is possible only and exclusively if the various sensors are directly connected to the RADAR.
A
Page 77
Argus Radar - RADAR CONFIGURATION
988-10187-004 3.9
3.7 Antenna Settings
By pressing the “Antenna Settings " button, the following window will appear:
Figure 3.7.1 Antenna Settings
Following the Help Line and the suggestion in the window, it should be easy to set the correct values for antenna height and antenna Cartesian coordinates, which will be important to draw the ship profile correctly, visible only at a low range scale.
The PPI will be centred on the cross representing the position of the Radar. The antenna height is one of the parameters used to calculate the Anti Sea Clutter processing. As a consequence of this insertion, a drawing of the ship's profile will appear at a low scale in the centre of the PPI:
To configure a valid radar connection, the checkbox E should be activated and the correct antenna selected from list A . The PPR selection B is available only when communication with the transceiver is in parallel mode (all radar signals connected separately).
A
B
C
D
E
Page 78
Argus Radar - RADAR CONFIGURATION
988-10187-004 3.10
3.7.1 Adjustment of Azimuth Type (PPR Selection)
Pressing the B button of fig. 3.7.1, page 3.9, a list will be open with all the possible azimuth values.
The list below shows all the standard and some special configurations with the relevant PPR:
NOTE
If the communication with the transceiver has already been established, if the Heading Line pulse is being received and if it has been correctly set, it is possible to read the PPR value measured by he system, on the label next to the PPR selection (between parenthesis). This is the easier and faster way to insert the correct PPR setting.
Antenna
Pedestal
Sensor Type
PPR
1XP
Proximity Switch
132
1XP
Encoder Kit
1024 to 4096
SU
Lettore + Antsig
128
SU
Encoder Kit
1024 to 4096
SRT 12/25 UP
Lettore + Antsig
128
Page 79
Argus Radar - RADAR CONFIGURATION
988-10187-004 3.11
3.7.2 Adjustment of the heading line
Pressing the C button of fig. 3.7.1. page 3.9, it is possible to set the Heading Line: The Heading Line skew value can be set in two ways:
Pressing the right or left arrow in order to turn the Radar picture clockwise or counter clockwise with a precision of 1/10 of a degree, with the possibility to turn it from -180° to +180°
Placing the EBL on the angle where it is desired to place the HL and pressing the "SET TO EBL" button, the picture will automatically turn, placing the angle where the EBL was positioned on the Heading Line Marker.
Press the D button to select the correct Heading Line polarity, positive for a signal that is zero with positive voltage as the active state, negative when the signal is bipolar (going from negative to positive voltage) or active with a negative level. Note: This function is only available when Alpha Extension board is installed.
WARNING
BUTTONS B AND D ARE AVAILABLE ONLY FOR THE RADAR VIDEO CHANNEL 1 AND 2.
CAUTION
IF THE CORRECT ANTENNA AND ANTENNA HEIGHT HAS NOT BEEN SELECTED OR IF THE SEA TABLES WERE NOT CREATED, A DEFAULT SETTING WILL BE USED. THE DEFAULT SETTING MAY, HOWEVER, NOT BE THE OPTIMAL ONE FOR TARGET DETECTION IN THE SEA CLUTTER AND TRACKING PERFORMANCE.
Page 80
Argus Radar - RADAR CONFIGURATION
988-10187-004 3.12
3.8 TXRX Settings
Pressing the button TXRX settings (G button of fig. 3.1.2, page 3.2), the window below will appear. The TXRX buttons can be up to four, to which can be connected the 3rd and the 4th TXRXs. In the "TXRX n SETUP MENU" (where n is the number of the TXRX chosen) it is possible to adjust the TXRX parameters such as video, heading line, azimuth type, etc.
Note: Some of these functions are protected by a password i.e. can only be accessed by authorized personnel.
Figure 3.8.1 TXRX Settings Menu
NOTE
In case of connection with a MOSFET transceiver with an "RTM Control P.C.B." on board instead of an "RTM Control B P.C.B." (TXRX software version lower than 54), the buttons in position 12-15-16-17-19 will not be activated. In case of connection with a non Simrad transceiver or with an old transceiver type (non MOSFET), all the buttons above and the button in position 5 will not be activated.
The password protected NMEA Protocol button (E) selects the protocol to use. All SRT and SRT derived transceivers work with NMEA protocol.
The communication mode is working at a baud rate of 4800 bps. More TXRX information is available from the Debug Display window (see Chapter 4), selecting the TXRX communication messages.
B
E
F
D
Page 81
Argus Radar - RADAR CONFIGURATION
988-10187-004 3.13
3.8.1 Transceiver Communication Type
Pressing the A button of fig. 3.8.1, page 3.12, the following list will open:
The list permits the selection of the communication’s type used to control the transceiver.
Other Comm: For any transceiver that cannot be controlled by the console, but is still able to generate the appropriate video, trigger and antenna synchronism signal.
Serial Comm: For the standard connection with RS232 serial line.
SXI n Comm: For video combined connections, all the signals needed are combined with the video on only one coaxial cable; "n" is the console priority for that transceiver.
Higher numbers have higher master priority than lower ones.
CAUTION
PRIORITY NUMBERS ARE IMPORTANT AND SHOULD NOT BE MIXED UP. IF THE SETUP HAS TO BE TRANSFERRED FROM CONSOLE TO CONSOLE VIA A MEMORY STICK, CHECK THAT PRIORITY IS NOT THE SAME IN ANY OF THE CONSOLES CONNECTED TO THE SAME RADAR INPUT. TWO CONSOLES WITH SAME PRIORITY, TRYING TO BE MASTER OF THE SAME TRANSCEIVER WILL SEND CONFLICTING COMMANDS AND MAKE IT JUMP BY DIFFERENT PRFS OR TUNING SETTINGS.
3.8.2 Transceiver Communication Type
Pressing the B button of fig. 3.8.1, page 3.12, (password protected), it is possible to adjust amplitude and slope of the TXRX Pre-STC. The range scale is automatically set to
0.75 NM. Amplitude and slope can be adjusted using the up and down arrow. This adjustment optimises the minimum visible distance and it can affect the auto-tuning performance for TXRX not derived from SRT.
Connecting the probe of the oscilloscope to the pin STC of TB13 of the RTM Control B PCB (the connector of the I.F. Amplifier, normally the blue wire), the PRESTC ramp will be shown on the scope.
The Amplitude shall be adjusted to be about 4 - 4.2V.
The Slope shall be adjusted to be about 2 - 3 µs.
Page 82
Argus Radar - RADAR CONFIGURATION
988-10187-004 3.14
The PRESTC is not a video processing to be used continuously during the normal operating, but it is a fixed STC curve stored in the TXRX to suppress enough main bang and too close echoes that otherwise would be in saturation. This adjustment is normally perfectly performed at the testing in the factory, and shall not be touched again, and only very skilled radar experts shall be allowed to touch these adjustments in case of very special situations.
The digital potentiometer values to measure the above described Amplitude and Slope values are normally:
- Amplitude 58 - 60
- Slope 5 – 9
CAUTION
BAD ADJUSTMENT OF PRESTC WILL COMPROMISE ARPA GOOD WORKING AND / OR AUTO TUNING FACILITY.
3.8.3 Performance Monitor Adjustment
Press the C button of fig. 3.8.1, page 3.12, to control the performance monitor. The range scale is automatically set to 24 NM and the performance monitor activated. Set the transceiver at maximum tuning using the Auto Tuning function or by adjusting the Manual Tune Progress bar to have the best echoes performance on the screen.
The top arrow buttons can be used to adjust the opening of the Performance Monitor Ring (now visible on the screen) and the bottom ones can be used to adjust the distance of the above mentioned ring.
Referring to the above figure "OPEN" and "DISTANCE" labels indicate the actual values of the digital potentiometers.
The Opening shall be adjusted to around 60 to 100 degrees.
The Distance (which correspond to the Power Level) shall be adjusted to a value of around 180 in the label down on the left (P.L.).
NOTE
the performance monitor is a facility used to check the performance of the transceiver, so it is very important that it is made one time at the installation. If, for example, the Power Level is low and the distance is less than 24 NM, it could indicate that the Performance Monitor is not correctly adjusted, but the reason could also be that the performance of the TXRX is low and the magnetron could be old or defective.
Page 83
Argus Radar - RADAR CONFIGURATION
988-10187-004 3.15
3.8.4 Tuning Adjustment
Pressing the D button of fig. 3.8.1. page 3.12, it is possible to adjust the Tuning. The range scale is automatically set to 24 NM, the performance monitor activated, the tuning control set to the middle position. The right placed label with "M.B." written indicates the Main Bang value and the procedure for the adjustment is described in detail in the transceiver technical manual.
There are 2 possibilities to adjust the tuning on Argus displays: Automatic or Manual. Press "Auto Adjust" to run the procedure automatically. The M.B. label content will change indicating the following possible steps of the adjusting:
Init Off Decreases the Tune Offset potentiometer down to 0;
Scan n Increases the potentiometer until it reaches the maximum (99);
Set Off Decreases again the potentiometer to the optimal Tune Offset found
in the previous step;
Adjust n Decreases the tune indication potentiometer down to 0 and increases it until the main bang value (n) reaches 128;
M.B. n Display the actual main band value.
3.8.5 Magnetron timer reset
When the magnetron is replaced and only when it is replaced, the Service Engineer should reset the timers of the transceiver so that at the next service it will be possible to check how many hours the new magnetron has been transmitting, and at which pulse and PRF, and thereby see if it is really still new or needs to be changed.
The magnetron timers can be reset by pressing the "F" button of fig. 3.8.1, page 3.12, and accepting the action, pressing "Yes" to the asked question "Are You Sure?".
The Argus system gives a System Warning if the magnetron is close to the expected lifetime. A "Magnetron EOL" (End Of Life) will be displayed under the TXRX field in the System Status Display Menu.
Everything described in this paragraph is valid only in case of RTM Control B PCB on board of the transceiver (TXRX software version 54 or higher). If this is not the case, when the magnetron is replaced, it is kindly requested to write down the value of the Main TX timer (which is placed on the Transformer assy of the transceiver) on a sticker and attach it on the chassis of the transceiver.
3.8.6 Digital potentiometers reset
This button (password protected) should be used when it is necessary to restore the default presets of the transceiver when the service engineer is no longer able to return it to a working condition.
Page 84
Argus Radar - RADAR CONFIGURATION
988-10187-004 3.16
3.9 Video Trigger Adjustments
Pressing the H button (password protected) of fig. 3.1.2, page 3.2, it is possible to adjust the radar video and trigger delay.
IMPORTANT
TO GAIN ACCESS TO THIS FUNCTION THE SYSTEM MUST BE MASTER (refer to the Argus Radar System user manual 988-10185-004). THIS TYPE OF ADJUSTMENT MUST BE CARRIED OUT IN PORT.
After entering the section “VIDEO AND TRIGGER SETTINGS” the following screen display appears on the left side of the menu.
IMPORTANT
AFTER ENTERING THE SECTION “VIDEO AND TRIGGER SETTINGS” THE SCALE AT 0.25 NM (operation useful only for setting the trigger delay) IS AUTOMATICALLY SET ON THE MAIN PPI DISPLAY.
This menu is divided into the following areas:
Figure 3.9.1 Video and Trigger Setting
B I H E A C D G F
Page 85
Argus Radar - RADAR CONFIGURATION
988-10187-004 3.17
3.9.1 Video Adjust Mode
Pressing the B button (password protected) of fig. 3.9.1, page 3.16, the system goes into “VIDEO ADJUST MODE ON” (under normal conditions this function is set to OFF). When carrying out this operation the TEST video is activated on the main PPI display; in other words, a large ring is created and the following actions are automatically carried out:
A long impulse is emitted.
The gain is forced by 100%.
The video palette is changed in order to highlight the saturated echoes with a red
colour (everything that is not saturated assumes a yellow colour).
To adjust the video the scale must be set at 0.75 NM or 1.5 NM (refer to the Argus user manual 988-10185-004, paragraph “Range scale increase/decrease”). Using the arrows G (Fig. 3.9.1, page 3.16) increase or decrease the value that appears in window F (Fig.
3.9.1, page 3.16).
The purpose of this operation is to eliminate the saturated echoes and therefore make the various red zones disappear from the video screen.
If red zones are seen on the screen, decrease the value in window F (Fig. 3.9.1, page 3.16) to make them completely disappear (some limited red zones are acceptable).
If the screen is completely yellow, increase the value in window F (Fig. 3.9.1, page
3.16) to make the red zones appear and then decrease the value to remove as many red zones as possible.
A datum that assists in understanding that the adjustment is correct is the value in window A (Fig. 3.9.1, page 3.16). This value oscillates during adjustment and it can assume three colourations:
Yellow: when the value drops below 240 indicates that the value should be increased, but more than 220 is anyway acceptable.
Red: when the value exceeds 250 indicates that the value must be decreased.
Green: when the value is between 240 and 250 indicates that the value is correct.
End the adjustment operation by pressing push button B (Fig. 3.9.1, page 3.16) into OFF mode. Push button H (Fig. 3.9.1, page 3.16) permits the automatic adjustment of the video.
IMPORTANT
ALWAYS PRESS THE PUSH BUTTON E “ACCEPT” TO SAVE AND MAKE EFFECTIVE THE MODIFICATIONS CARRIED OUT.
3.9.2 Adopted communication configurations
A text appears in box I (Fig. 3.9.1, page 3.16). This text varies on the basis of the communication hardware configurations adopted between the console and the transmitter. Pay attention to what is shown, otherwise the adjustment operations could become useless and bring about an incorrect visualisation of the radar video.
Page 86
Argus Radar - RADAR CONFIGURATION
988-10187-004 3.18
3.9.3 Trigger Delay
Press the C button (password protected) of fig. 3.9.1, page 3.16 to adjust the Trigger Delay. The Trigger delay is caused by the path length mismatch for the trigger and video signal.
The video path delay is much longer because it's the result of the transmission through the waveguide to the antenna and back.
The delay depends of the length and type of the cable/waveguide used in the installation.
The range scale is automatically set to 0.25 NM. Press the arrow buttons in order to enlarge or squeeze the picture and adjust the delay between video and trigger from 0 meters to a maximum of 384 meters.
The delay adjustment is visible in real time on the PPI around the ship.
The illustration shows two different samples of incorrectly adjusted trigger delay:
1: The dock or pier is bowed towards the center, which means that the figure is too high
2: The dock or pier is bowed away from the center, which means that the figure is too low.
NOTE
For SRT transceivers it is also possible to change the delay to negative numbers. In this case the trigger from the TXRX will be anticipated in time in respect to the video. This negative setting is needed when trigger and video are passing through long coaxial cables with different propagation times, the video cable being the slowest one. This usually happens for all installations with an SRT Adapter Box, as buffer amplifier and cable lengths are more than 150 meters.
NOTE
On channel 1 and 2, two optional buttons C for Trigger and Video polarity will be available.
Page 87
Argus Radar - RADAR CONFIGURATION
988-10187-004 3.19
3.9.4 QV (Quantized Video) Threshold
WARNING
THIS VALUE MUST BE SET AT “AUTO” EXCEPT FOR THE VARIOUS CASES OUTLINED BY THE MANUFACTURER.
Pressing the D button (password protected) of fig. 3.9.1, page 3.16, it is possible to set the QV. The threshold is used by the automatic tracking to identify real radar echoes from receiver noise. This value depends on the receiver noise from the transceiver band and the video cable attenuation. This value can be set manually adjusting the noise level to see some speckles in the 24 NM range scale.
This adjustment is really subjective, and the receiver gain changes with the selected pulse length, with the weather, the humidity and so on, so the preferred solution is to activate the Auto Threshold. With this selection the automatic tracking software measures the PFA (Probability of False Alarm) and calculates the correct threshold for the optimum detection performance.
3.10 Sector Blanking
Pressing the I button of fig. 3.1.2, page 3.2, the following window will appear:
Figure 3.10.1 Sector Blanking Settings
The radar offers two blanking sectors, which can be set individually. Transmission will be off within the set sectors.
The sector blanking is visible on the PPI with a sector delimited by two green lines (which will be red during the setting) and, if the gain value is high enough, the absence of receiver noise will be clearly visible.
Page 88
Argus Radar - RADAR CONFIGURATION
988-10187-004 3.20
To configure sector blanking, use up or down arrows to change the "Start Sector" and the "End Sector" values. The graphic displayed on the PPI will change in real time, but the command to the transceiver will be sent only after pressing the "Apply Sector" button. Use "Discard" to discard temporary modifications to the sector blanking configuration. The “on-off button next to the sector n label 1-2" shall be pressed to cancel the current sector blanking.
NOTE
The settings of the Sector Blanking are stored directly in the TXRX and not in the Argus Core Unit/display.
Page 89
Argus Radar - RADAR CONFIGURATION
988-10187-004 3.21
3.11 System Configuration
Press the L button of fig. 3.1.2, page 3.2, and the following window will appear:
Figure 3.11.1 System Configuration
3.11.1 Display settings (Fig 3.11.1 -A)
The "Display settings" are the currently used settings. If the diagonal, the aspect ratio and the resolution information are shown in green, it means that the settings used are the same as detected directly by the monitor. Otherwise they will appear in red.
To modify the display settings, press the "Display Settings" button to enter the Display Settings menu – see example next page.
A
C
E
D
F
Page 90
Argus Radar - RADAR CONFIGURATION
988-10187-004 3.22
Current settings and detected settings are shown in this menu. You can choose to accept the detected settings by clicking on the "Accept and set Detected Settings" button, or you can manually change the display settings by selecting one of the “monitor selections” available.
The Argus display video output (DVI and VGA) can support 6 different display resolutions:
Display Resolution
1280x1024
1366x768
1600x1200
1920x1080
1920x1200
Page 91
Argus Radar - RADAR CONFIGURATION
988-10187-004 3.23
The table below shows which resolution is required for the different type monitors normally connected to an Argus display:
Unit Type
Description
Aspect Ratio
Display Resolution
M5016 16” Simrad
16:9
1366x768
M5019
19” Simrad
16:9
1366x768
10CM-003
19" TFT Hatteland
5:4
1280x1024
10CM-004
19" TFT ISIC
5:4
1280x1024
10CM-005
23" TFT Hatteland
4:3
1600x1200
10CM-006 23" TFT ISIC
4:3
1600x1200
M5024
24” Simrad
16:9
1920x1080
10CM-008
26" TFT Hatteland
16:10
1920x1200
M5027
27” Simrad
16:9
1920x1080
To force the use of manual settings, click on the relative button “Force the use of Manual Settings”, then confirm by clicking on “Yes” followed by “Accept”.
WARNING Settings which are not automatically recognized are most probably not IMO approved configurations. A warning: "NOT“APPROVED MODE” will appear in the System status window.
Page 92
Argus Radar - RADAR CONFIGURATION
988-10187-004 3.24
3.11.2 IP Address (Fig 3.11.1 -B)
The IP Addresses next to the “This Console” label are for the working console. The “PROC A IP” column is the IP address of Processor A of Antares p.c.b.
The Proc A IP of This Console can be set by clicking on the IP address field.
The Proc B IP will automatically be set.
Figure 3.11.1-B
The following functions can be used only if This Console is connected via LAN with other Argus consoles:
Scan Other Nets
The Argus console searches through 10.x.x.x, 192.168.0.x, 172.1.x.x and 212.4.5.x subnetworks for other Argus units. All the consoles available will be presented in the table.
Set All Sequentially
After a scan identification, the IP of the listed consoles in the table can be set in an incremental order starting from own console IP number. The assigned IP will be incremented +2 for every console found and a dialog window will be shown on each one to accept the IP setting request.
Send Configuration
This function can be used to share the configuration of This Console with the other ones. Please note that Transceiver, Antenna and Video/Trigger settings may have to be re­configured at each console.
Page 93
Argus Radar - RADAR CONFIGURATION
988-10187-004 3.25
3.11.3 MAC Address (Fig 3.11.1 -C)
This is the Ethernet MAC address of the board (not settable). Part of the address is a field assigned only to Simrad. Less significant bytes are different for any Antares PCB manufactured.
3.11.4 TXRX Associated by Default (Fig 3.11.1 – D)
By pressing the relevant button, the following list with all the transceivers connected will be displayed:
This is not the interswitch, this list selects the TXRX to use at the start-up of the system. For example if the Port Argus Console is normally used with TXRX n 2, the selection “TXRX2” shall be chosen in the left list, and if a blackout occurs or the system is restarted or completely powered off and on again, the Console will automatically select the TXRX n 2 at the restart.
WARNING
IF THE SETUP HAS TO BE TRANSFERRED FROM CONSOLE TO CONSOLE VIA A MEMORY STICK, CHECK THAT THE DEFAULT TRANSCEIVER IS NOT THE SAME FOR ANY OF THE CONSOLES.
3.11.5 General info (Fig 3.11.1 – E)
This window shows information regarding the screen resolution, PPI pixel size and the exact software version installed in the system.
Page 94
Argus Radar - RADAR CONFIGURATION
988-10187-004 3.26
3.11.6 Additional Functions (Fig 3.11.1 – F)
Figure 3.11.6
In this configuration, it is possible to enable, disable or expand the ECDIS, Conning Information and Twin Scan functions.
- ECDIS interface ( Figure 3.11.6-A)
Selecting/deselecting this function enables/disables transmitting the Overlay video to a connected ECDIS. Clicking on the ”More” button expands the configuration window, and it is possible to see the console for the radar that is enabled at that moment. For more information, refer to the Technical User Manual.
Figure 3.11.6-A
- Simplified Conning Information Enable (Figure 3.11.6-B)
Selecting this function enables the Conning Tasks on the System Data Area Section (if the wide screen configuration is being used).
Page 95
Argus Radar - RADAR CONFIGURATION
988-10187-004 3.27
- Twin Scan Enable (Figure 3.11.6-C)
Selecting this function enables/disables the Video Combination Mode (if the wide screen configuration is being used) for the video configurations in the TXRX Interswitch menu.
Enabling/disabling the Twin PPI Mode function, which is used to select different radar transceivers for each PPI.
Figure 3.11.6-C
3.12 Restart button
Press this button (Fig 3.1.2 – M, page 3.2), to reboot the Argus system. After pressing the button, another red window will appear asking for a confirmation of the requested action.
Figure 3.12.1
The following actions are applied only after a reboot of the system:
Display Resolution change
System Program Version change
IP Address settings
Moving the Main Menu column from left to right or from right to left
Adding or removing the percentage value from the Video Processing Progress Bars
Page 96
Argus Radar - RADAR CONFIGURATION
988-10187-004 3.28
3.13 USB Menu (Fig 3.1.2-N)
By pressing the button, the system will try to mount any memory stick inserted in the USB port, and the following window will be displayed:
Figure 3.13.1 USB Menu
If no USB memory is connected to the keyboard’s USB socket or in case of incompatibility of the USB memory with Linux OS, the above window will indicate: Fail mounting module!
In this case the USB memory installed cannot be used, due to an incompatibility between it and the system.
Figure 3.13.2 USB Storage
Page 97
Argus Radar - RADAR CONFIGURATION
988-10187-004 3.29
If the USB memory is used with the ARGUS for the first time, the following window will be displayed:
Figure 3.13.3 USB Storage
To enable the Memory Stick, a directory file tree is needed in the USB memory. A directory named “ARGUS” shall be created in the root of the USB memory and it should contain other directories named “logs”, “maps”, “screenshots”, “setup”, and “update”.
If this file tree is not present, a warning will appear, and the only action possible will be “Format Module”. This will not erase any files in USB Module, but just create the required directory tree.
By pressing the “Format Module” button, the window will return to the previous, and it will be possible to access the functions.
The USB flash disk will be mounted in /mnt/usb and the USB STORAGE Menu will appear as shown by the following picture. The figure shows the possibility to store maps, backup setup files, system logs and screenshot pictures on the flash disk and to get maps, backup setup files and to upgrade the Argus software from the flash disk.
This is a list of the sub-directories that can be found under the Argus directory.
Maps : All files *.map.
Setup: Sub-directories named NAME_XXXXX_cfg, where NAME given when it was
stored (usually own ship name) and XXXXX is the serial number of the ANTARES p.c.b.
Update: All console update packages.
Screenshots: Screenshots of the display picture in PNG format. Named usually as
G/V-SERNUM-YEARMONTHDAY-HOURMINUTES.png, where G or V means a
Page 98
Argus Radar - RADAR CONFIGURATION
988-10187-004 3.30
complete screenshot with all the graphic included and the second one with only the PPI video, SERNUM is the serial number of the Antares PCB and YEARMONTHDAY-HOURMINUTES the date and time in UTC format (from EPFS sensor) of the picture.
3.13.1 Save Screenshots
Figure 3.13.4 Save screenshots
The Screen Capture function allows you to save the views of the radar in order to capture the situation at that particular moment.
- Pressing the “Video radar Only” button, it is possible to save only the radar image at that specific moment.
- Pressing the “Entire Screen” button, it is possible to save the whole image on the display at that specific moment.
- Pressing the “Cancel” button will take you back to the main menu.
3.13.2 Saving and reloading maps
In this mode, it is possible to save or transfer maps from the Argus system to USB pen drive and vice versa.
Page 99
Argus Radar - RADAR CONFIGURATION
988-10187-004 3.31
3.13.3 File configuration
In this mode, it is possible to save or transfer system configuration files from Argus to a USB pen drive and vice versa.
3.13.4 System log files
In this mode, it is possible to save or transfer system configuration log files from Argus to a USB pen drive. This is to allow Simrad to have information about the system present on the Argus system. No reverse transfer of data is permitted.
Page 100
Argus Radar - RADAR CONFIGURATION
988-10187-004 3.32
3.14 Stored parameters
All configuration parameters are stored in files that can be stored and retrieved from the memory stick. These parameters are essential for the system, they should be saved in a backup storage or the System Installation Checklist should be filled. These parameters
should be restored when the Antares Assy is replaced.
Parameter
Stored On
Antares PCB
TXRX
Gyro configuration
Log configuration
Own ship dimensions
Ship Tonnage / ROT
Conning position coordinates
EPFS antenna position coordinates
Radar antenna position and type
Sea clutter attenuation shapes
Heading Line Alignment
Trigger/Video delay adjustment
PRESTC Amplitude and Slope
PM Opening and Distance
Tuning Offset and Indication
TXRX communication type and protocol
Startup TXRX selection adjustment
Display Resolution
Function keys configuration
Time configuration (UTC/Local Time
Miscellaneous personal settings
Tasks (Additional PPI, ROT, Depth,
Heading etc…)
Twin scan data(combination Types)
Loading...