DBS00328-31A - Operators Manual DM200-DM500 PDF
DBS00328-31A - Operators Manual DM200-DM500 PDF
DBS00328-31A - Operators Manual DM200-DM500 PDF
Revision record
Version Date Description
1.0 September 2006 Original issue of document
1.2 March 2007 Minor errors corrected
2.0 July 2008 Information related to DM200 S-VDR and DM400 VDR
included in this manual.
3.0 June 2011 Updated system overview and list of error codes to reflect
changes to V3.1 of the S-VDR/VDR program code.
Description of the VDR Verifier utility
3.1 August 2012 The list of spare parts is updated
Contents
3 OPERATION.............................................................................................................8
3.1 Bridge alarm Unit ......................................................................................................8
3.1.1 Alarm display .....................................................................................................8
3.1.2 Means for initiating a backup on the VDR data disc...........................................8
6 OPERATION OF SIU..............................................................................................17
6.1 LEDs on Module Rack ............................................................................................17
6.1.1 AC LED............................................................................................................17
6.1.2 Link indications ................................................................................................17
6.1.3 AC breaker.......................................................................................................17
6.1.4 LEDs in the Ethernet connector .......................................................................18
6.1.5 Allocation of system labels for digital interfaces...............................................18
6.1.6 MR address......................................................................................................18
7 OPERATION OF RVI..............................................................................................19
7.1.1 RVI address .....................................................................................................19
7.1.2 Ethernet ports ..................................................................................................19
7.1.3 ST LED ............................................................................................................19
1.1 References
9200238 Installation Manual for DM200/DM300 S-VDR and DM400/DM500 VDR
9200327 Installation Manual for DM400/DM500 VDR Sensor Interface Unit
9200331 Installation Manual for Remote Video Interface for DM200, DM300, DM400, DM500
9200343 Inspectors and Authorities Manual for DM200/DM300 S-VDR and DM400/DM500
VDR
2 System overview
2.1 System overview for S-VDR
Firewire
RS-422 S-DAU STP CAT5 Capsule
BAU Power
4 x Audio or
Half slot in dpu 4 x Serial
BMU
BMU
BMU Gray print denotes that
BMU optional equipment is
BMU needed.
BMU
4 x Audio or
Half slot in dpu
4 x Serial or
8 x Analog or
BMU 8 x Digital
BMU
BMU
BMU
BMU
BMU Ethernet STP CAT5
6 x BMU
3 Operation
3.1 Bridge alarm Unit
The BAU is the primary user interface for an installed operational VDR. It serves two purposes:
• Alarm display
• Interface for initiating backup an the VDR data disc
3.1.1.2 Warnings
Warnings look like alarms but with a “W” after the error code. See section 8.3
3.1.1.3 Dimming
The button with the light bulb symbol may be used to alter the luminance of the keyboard, error
LEDs and the LCD display simultaneously.
The backup procedure is started when the two “Save” buttons are pressed simultaneously. The VDR
is capable of making the backup within seconds.
The system is capable of storing three incidents. The “Save” LED indicates when there is multiple,
one or no save opportunity left (disk full). A backup will be protected for 30 days after which the
space on the disc will be released automatically.
This VDR data disc must be replaced if it becomes full (which is unlikely under normal
circumstances). Alternatively, data from the disc must be transferred to another media and space on
the disc can be manually released. This requires proper authorization and cannot be done from the
BAU.
The VDR data disc, which is easily removed from the DAU, must be retrieved if the vessel is
abandoned after a serious incident.
Service
console
I/F for
BAU Radar
interface
VGA
interface
Keyboard
Cables for
interface
batteries
4.1 DPU
The DPU is the main computer in the system. It is basically a PC, but it has been designed from
scratch in a completely different manner to withstand environmental stress that far exceeds what an
ordinary industrial PC can sustain.
AC LED (blue)
Steady light AC power OK OK
Off AC power failed Error
OK LED (blue)
Steady light Power to DPU present OK
Off No power to the DPU Error (note 1)
4.1.3 AC inlet
The main power source for the VDR is ships AC (110V-240V).
ERR LED
AUX DC output LED
Battery, DC and AC breaker
DC for DPU LED
Optional DC outlet Battery, DC and AC LED
DC for DPU AC inlet
PSU outlet
DC inlet
Serial
interface VDR data
module disc
Radar
interface
Capsule
Audio interface
interface
module Program
memory
AC LED (blue)
Steady light AC power OK OK
Off AC power failed Error
DC LED (blue)
Steady light DC power OK OK
Off DC power failed Error
5.1.2 AC inlet
The main power source for the VDR is ships AC (110V-240V).
5.1.3 DC inlet
The VDR must be connected to the ships emergency power source (24VDC) if the emergency
power system is based on DC.
5.1.4 DC to DPU
The PSU and the DPU is connected with a cable. DC is supplied to the DPU through this cable.
This cable also carries bi-directional communication between the PSU and the DPU.
Warning: The cable between the DPU and PSU must NOT be connected or disconnected
while the PSU is on i.e. all power sources must be switched off and the blue “DC for DPU”
LED must be off.
5.2 DPU
The DPU is the main computer in the system. It is basically a PC, but it has been designed from
scratch in a completely different manner to withstand environmental stress which far exceeds what
an ordinary industrial PC can sustain.
6 Operation of SIU
Module Rack
6.1.3 AC breaker
The AC breaker is a combination of a fuse and a manually operated switch, i.e. it can be used to
manually switch off the power source but it will also pop out automatically if too much current is
drawn from the power source.
6.1.6 MR address
Must be set to “0” or “1” for an additional second SIU.
7 Operation of RVI
7.1.3 ST LED
The Status LED (Yellow) will flash (1Hz) after power on and then become steady if a
communication link is established to the DAU. The LED will always be switched off after one
minute.
8 Error codes
Error codes and messages will be displayed by the BAU and VDR status display when errors are
detected. An “R” after the error code denotes a repetitive alarm, see section 3.1.1.1. A “W” after the
error code denotes a warning, see section 8.3
replaced.
106 SERIAL module 1 The Serial Interface module in the DPU is using too much power.
Power failure The module is probably faulty and must be replaced.
108 VIDEO module 1 The Video Interface module in the DPU did not start. Wait three
Not started minutes; maybe the VDR is able to recover by restarting the
interface else try to reboot the system. If the error persists the
module is faulty (or wrong type) and must be replaced.
110 AUDIO module 1 The Audio Interface module in the DPU did not start. Try to reboot
Not started system if the error persists the module is faulty (or wrong type) and
must be replaced.
112 SERIAL module 1 The Serial Interface module in the DPU did not start. Try to reboot
Not started system. If the error persists the module is faulty (or wrong type)
and must be replaced.
118 PSU battery The power supply is unable to detect the battery pack. Check that
Not present the fuse/breaker on the PSU named “BAT” is pushed; see section
5.1.1. If the error persists for 5 minutes then call for assistance.
120 PSU battery The PSU was unable to fully charge the battery within a specified
Could not be charged time. Release the fuse/breaker on the PSU named ”BAT” for 15
seconds, then push it in again see section 5.1.1. If the error returns
(this may take 18hours) call for assistance i.e. the battery pack is
defective and needs replacement.
122 PSU battery A temperature sensor for the battery pack is disconnected or
Temp. sensor missing broken. Call for assistance, the PSU needs repair.
123 (Never displayed on Alarm system under initialization. Displayed shortly after system
BAU) startup.
124 PSU The output voltage from the PSU has dropped below 19V.
Low output voltage This message will appear shortly before the battery is discharged
when operating from the internal battery only. This message will
not appear if the battery is new and was fully charged since the
VDR will power down automatically after two hours when
operating from the batteries (well before the voltage drops below
19V).
If AC power or DC power is present (and the AC and DC
fuse/breaker are pushed) while this error is displayed call for
assistance, the PSU needs to be repaired.
126 PSU Call for assistance, the PSU needs to be repaired.
Error
128 AUDIO module 2 This will only happen if audio channel 5 is enabled in the
Missing (AUD5) configuration. The optional Audio Interface module 2 (half slot) is
defective or internally disconnected (check cable) inside DPU.
130 xxxxxx xxxxxx = SERIAL, VIDEO, AUDIO
132 Module duplicate Two modules with identical system locations have been detected.
134 Restart the system. If the error persists call for assistance.
144
146 AUDIO module 2 The optional Audio Interface module 2 (half slot) did not start. If it
Not started is not installed, audio channel 5 in the configuration must be
disabled or else check the cable from the baseboard in the DPU to
the module.
Restart the system; if the error persists replace the module.
148 SERIAL The serial module must be located in slot 1 in the DPU. Check the
Module in wrong slot position of the module or that the internal cables in the DPU are not
crossed.
150 AUDIO The Audio Interface module must be located in DPU slot 2
Module in wrong slot (DM300) and the optional Audio Interface module 2 (half slot), if
present, in DPU slot 3. Check the position of the modules or that
the cables for the modules inside the DPU are not crossed.
152 VIDEO The video module must be located in slot 4 (the horizontal slot).
Module in wrong slot Check that the cables for the modules inside the DPU are
connected straight.
160 EXTERNAL BACKUP The system is unable to record data to the extended external backup
Not recording disc (NAS). If no other relevant errors e.g. #162 is displayed call
for assistance.
162 EXTERNAL BACKUP The communication to the extended external backup disc (NAS) is
Can not find interrupted. Check that the extended external backup disc is
installed correctly (e.g. is the LAN cable connected to DPU).
Reboot system. If the error persists call for assistance. The most
probable cause is a defective/misconfigured extended external
backup disc.
300- SERIAL A mandatory serial signal has disappeared. Check that the source is
307 Timeout on SIxx on. Check the signal from the source (serial monitor in VDR
explorer, WEB status or VGA status display). If no signal is
present check the cable or that the configuration is correct.
400- Error codes related See Section 8.2
549 to a VDR only
550 STORAGE One or more types of data are not recorded. If the error persists
Dataset incomplete then restart the VDR and report this error if it still persists.
560 BACKUP INCIDENTS The capacity of the VDR data disc is too small for the configured
Backupdisk too small incident record size.
Change the VDR data disc or reduce the incident record size.
561 BACKUP INCIDENTS The configured incident record size on the VDR data disc is too
Incident too small small for storing the capsule data.
Change the incident type to large incident or replace the capsule
with one with lower capacity.
562 INTERNAL BACKUP The capacity of the VDR data disc is too small for internal
Backupdisk too small extended backup.
Change the VDR data disc or disable this feature.
608 STORAGE (Warning) The VDR has detected that the capsule or VDR data disc has been
Device reset disconnected and/or connected during the first 24h hours after
system restart, see section 8.3
609 STORAGE The VDR has detected that the capsule and /or VDR data disc has
Device resets been disconnected and/or connected too many times within a given
interval
611 CAPSULE The VDR is unable to record data to the capsule. Another error
Not recording explaining why (e.g. #612 CAPSULE Can not find) is normally
displayed in advance. Try to fix the preceding error else reboot
system. If the error persists call for assistance.
612 CAPSULE The VDR is unable to detect a capsule. Check that the capsule is
Can not find connected correctly. If the error persists call for assistance.
613 CAPSULE The VDR has detected a capsule but is unable to get access. The
Can not access most likely cause is that the capsule is not initialized (formatted)
correctly. A trained service technical can fix this.
614 CAPSULE Too many write-errors (writing to the capsule) have occurred
WR errors level 1 within a given interval. Retrying to write data fixed the problem.
The most likely cause is communication problems. The capsule is
not taken out of service and data is still recorded.
615 CAPSULE Too many write-errors (writing to the capsule) have occurred
WR errors level 2 within a given interval. More sophisticated measures than just
retrying to write data were needed in order to fix the problem. The
most likely cause is serious communication problems or a defective
capsule. The capsule is not taken out of service and data is still
recorded.
616 CAPSULE Too many write-errors (writing to the capsule) have occurred
WR errors level 3 within a given interval. The VDR was unable to write data despite
several attempts. The most likely cause is serious communication
problems or a defective capsule. The capsule is taken out of service
and data is temporarily not recorded. The VDR will attempt to
recover from this problem.
617 CAPSULE The VDR is unable to write log messages to the capsule
Can not write log
618 CAPSULE The amount of data received by the VDR exceeds the capacity of
Record-data too big the capsule. The most probable cause is that the VDR is unable to
compress the radar images due to noise or other errors, or that the
VDR is configured to record images from multiple high resolution
radars.
619 CAPSULE (Warning) A write-error (writing to the capsule) has occurred during the first
WR error level 1 24 hours of operation. Retrying to write data fixed the problem.
The most likely cause is communication problems.
See section 8.3
620 CAPSULE (Warning) A write-error (writing to the capsule) has occurred during the first
WR error level 2 24 hours of operation. More sophisticated measures than just
retrying to write data were needed in order to fix the problem. The
most likely cause is a temporarily disruption of communication
from the VDR to capsule or a defective capsule.
See section 8.3
621 CAPSULE (Warning) A write-error (writing to the capsule) has occurred during the first
WR error level 3 24 hours of operation. More sophisticated measures than just
retrying to write data did not fix the problem. The most likely cause
is a temporarily disruption of communication from the VDR to
capsule or a defective capsule.
WR error level 2 the first 24 hours of operation. More sophisticated measures than
just retrying to write data were needed in order to fix the problem.
The most likely cause is a temporarily disruption of communication
from the VDR to VDR data disc or a defective VDR data disc.
See section 8.3
641 BACKUP (Warning) A write-error (writing to the VDR data disc) has occurred during
WR error level 3 the first 24 hours of operation. More sophisticated measures than
just retrying to write data did not fix the problem. The most likely
cause is a temporarily disruption of communication from the VDR
to VDR data disc or a defective VDR data disc.
See section 8.3
651 INTERNAL BACKUP The VDR is unable utilize VDR data disc for extended back.
Not recording Another error explaining why (e.g. #652 INTERNAL BACKUP
Can not find) is normally displayed in advance. Try to fix the
preceding error else reboot system. If the error persists call for
assistance.
652 INTERNAL BACKUP The VDR is unable to detect a VDR data disc or utilize the VDR
Can not find data disc for extended backup. Check that the VDR data disc is
connected correctly. If the error persists call for assistance.
653 INTERNAL BACKUP The VDR has detected a VDR data disc but is unable to get access.
Can not access The most likely cause is that the VDR data disc is not initialized
(formatted) correctly. A trained service technical can fix this.
654 INTERNAL BACKUP Too many write-errors (writing to the VDR data disc) have
WR errors level 1 occurred within a given interval. Retrying to write data fixed the
problem. The most likely cause is communication problems. The
VDR data disc is not taken out of service and data is still recorded.
655 INTERNAL BACKUP Too many write-errors (writing to the VDR data disc) have
WR errors level 2 occurred within a given interval. More sophisticated measures than
just retrying to write data were needed in order to fix the problem.
The most likely cause is serious communication problems or a
defective VDR data disc. The VDR data disc is not taken out of
service and data is still recorded.
656 INTERNAL BACKUP Too many write-errors (writing to the VDR data disc) have
WR errors level 3 occurred within a given interval. The VDR was unable to write data
despite several attempts. The most likely cause is serious
communication problems or a defective VDR data disc. The VDR
data disc is taken out of service and data is temporarily not
recorded. The VDR will attempt to recover from this problem.
659 INTERNAL BACKUP A write-error (writing to the VDR data disc) has occurred during
(Warning) the first 24 hours of operation. Retrying to write data fixed the
WR error level 1
problem. The most likely cause is communication problems.
See section 8.3
660 INTERNAL BACKUP A write-error (writing to the VDR data disc) has occurred during
(Warning) the first 24 hours of operation. More sophisticated measures than
WR error level 2
just retrying to write data were needed in order to fix the problem.
The most likely cause is a temporarily disruption of communication
from the VDR to VDR data disc or a defective VDR data disc.
See section 8.3
661 INTERNAL BACKUP A write-error (writing to the VDR data disc) has occurred during
(Warning) the first 24 hours of operation. More sophisticated measures than
WR error level 3
just retrying to write data did not fix the problem. The most likely
cause is a temporarily disruption of communication from the VDR
to VDR data disc or a defective VDR data disc.
See section 8.3
901- SYSTEM FAILURE The software is not working properly. Restart the VDR and report
923 ERROR 901-923 this error if it is repeated.
980 BAU and DPU not The software in BAU is incompatible with the software in the
compatible DPU.
981 No communication The BAU has never been able to communicate with the DPU. The
to DPU most probable cause is a defective cable or that the VDR did not
boot correctly.
982 No communication Initial communication was ok but the communication has failed
to DPU later. The most probable cause is that the VDR encountered a fatal
error and completely stopped. Restart the system, if the error
persists then call for assistance.
999 (Never displayed on The system is booting the VDR application from the boot flash.
the BAU)
--- Time, VDR No errors detected
A system which is installed and operating correctly will in general be able to operate for 24 hours
without having to recover from errors however there is always a chance that a problem is detected
within the first 24 hours of operation even if the error rate is very low e.g. one per year. The
simplest test if a warning is issued is to restart the VDR and check that is does not happen again
alternatively let the VDR operate for e.g. 24 hours and then analyze the log.
Please notice that all activity related to system recovery will be logged and the log must be analyzed
as part of the APT in order to check the integrity of the VDR.
The default IP address of the VDR is 10.0.0.100 (255.0.0.0). The PC must use an IP address within
the same range.
The following description covers how to change the IP address for Windows XP. The scheme for
Windows 2000P is almost identical.
Note: The operator may have changed the IP address for the VDR. This must be documented in the
“Inspectors and Authorities Manual for DM200/DM300 S-VDR and DM400/DM500 VDR”.
Click on “Properties”.
Type in the IP address of the VDR in the browser address field. The IP address of the VDR is
10.0.0.100 (default).
If needed change the IP address, the default IP address is set to the default at program start. Pressing
“Test” will verify that a connection can be made to VDR.
Select the duration of the recording to be verified. Duration can be set from 15min to 720min.
Please notice that duration is limited to the time since last restart of the VDR and that only the radar
images recorded to capsule will be checked. The best result is obtained if the data to be verified
were recorded during a voyage.
Warning: The input was steady – the current value is printed and must be checked.
Passed: The input changed during the verification – the current value is printed and must be
checked.
The last 60 seconds of audio from each track* is stored and must be checked before a conclusion is
made. A graphical representation of data from each track is shown as additional information.
* Data for tracks with no active microphones which is not configured to record VHF radio communication is omitted.
Error: The received data did not contain the NMEA formatters defined in the VDR configuration
or list of defined NMEA formatters was empty. Other kind of errors may be displayed e.g. detection
of CRC errors.
Passed: The received data contained the NMEA formatters defined in the VDR configuration
The last four images from each active input are saved and must be checked before a conclusion is
made.
Boxes in DAU
DM300 DPU 1000610
DM300 PSU 1000611
DM200 DPU 1300687
Modules in DPU
Serial 08-001 2000621
Audio 08-001 2000627
Video 02-004 2301955
Video 02-004D 2301902
RBD 80GB-003 2301873
USB Backup Drive for DM200 2302123
COMM 03-001 (DM300) 2000649
COMM 03-004 (DM200) 3300608
FW 01-001 (DM300 older versions, w. RJ45) 2000650
FW 01-002 2301064
Miscellaneous parts
Beacon replacement kit 3000671
Clamps and cover for beacon 2301127
Cradle for capsule MK2 2000673
Cradle for capsule MK3 2300562
Cable from PSU to DPU - DM300 3000674
DM300 Spare DPU with no modules 2000680
(baseboard and all cables included)
Battery pack for DM300 PSU p/n 1000611 2000685
Battery pack for DM200 (DAU) 2301377
Spare ETX base board with ETX module 2300605
mounted for DM300 DPU 04-00x
Spare ETX base board with ETX module 2300961
mounted for DM200 DPU 200-01
Serial, Audio, Power (SAP) board for DM200 2300384
DPU 200-01
Internal cable set for DM300 DPU (spare 2000687
parts)
Fan (80x80x25) for DPU right side 2000688
Fan for DM300 PSU 2000689
Fan (92x92x25) for DM200 DPU top 2300962
New lock for DAU and SIU 2000690