VDR DANELEC Operator Manual
VDR DANELEC Operator Manual
Revision record
Version Date Description
1.0 April 2014 Original issue of document
1.1 May 2014 Minor revision
1.2 June 2014 Minor revision
1.3 May 2016 Update of error text for error 054 and 184
1.4 September 2018 Description of Remote Audio Interface included.
Description new features and changes related to software
release 1.60.
2.0 June 2019 Information related to DM100 S-VDR G2, included
Contents
3 OPERATION.............................................................................................................10
3.1 Bridge Control Panel.................................................................................................10
3.1.1 Alert display........................................................................................................10
3.1.2 Self-test – Operational Performance Test ..........................................................10
3.1.3 Setting the display brilliance level to default.......................................................10
3.1.4 Download of VDR data to USB stick ..................................................................11
3.2 Operation of the DM100 DAU ...................................................................................12
3.3 Data Processing Unit (DPU) .....................................................................................13
3.3.1 Power LEDs .......................................................................................................13
3.3.2 AC breaker .........................................................................................................13
3.3.3 AC inlet...............................................................................................................13
3.3.4 Battery switch .....................................................................................................13
3.3.5 VDR status LED .................................................................................................14
3.3.6 Main CPU LED ...................................................................................................14
3.3.7 LEDs in the Ethernet connectors........................................................................14
1.1 References
DBS10704 Installation Manual for DM100/DM400 VDR compact Sensor Interface Unit
DBS10956 Installation Manual for DM100 VDR and DM100 S-VDR G2
DBS11010 Inspector's and Authorities' Manual for DM100 VDR and S-VDR G2
DBS10919 Installation Manual for Remote Video Interface with PoE RVI 02-004, RVI 02-004D
DBS00327 Installation Manual for DM100/DM400 modular Sensor Interface Unit
1.3 Nomenclature
The term “VDR” will be used a generic term which covers both the DM100 VDR and DM100 S-
VDR G2. When required, the full product names “DM100 VDR” and “DM100 S-VDR G2” will be
used to distinguish between the products.
Float-free
Ethernet PoE capsule
Ethernet PoE DAU STP CAT5
STP CAT5
BCP
Ethernet STP
CAT5/CAT6 Images from
BMU RADAR and ECDIS
BMU Ethernet PoE
BMU STP CAT5
BMU Optional
BMU Remote
BMU Video I/F
Ethernet
6 x BMU STP CAT5
Video inputs (2)
VHF Serial inputs (12) Analog or DVI from
e.g. GPS e.g. RADAR
SIU
Float-free
Ethernet PoE capsule
STP CAT5 Fixed
Capsule OR
* For configuration of the VDR, acquiring network data and acquiring image data.
** VDR core inputs on SIUs. There is not limit for number of digital and analog input on RDIs
3 Operation
3.1 Bridge Control Panel
The BCP is the primary user interface for an installed operational VDR. It serves two purposes:
VDR status
Termination Interfaces Ethernet Audio
LED Battery
resistors for for serial data ports interfaces
switch
SI00 - SI03 Main CPU Power status
Service mode
switch status LED LEDs
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)
3.3.2 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 AC power sources, but it will also pop out automatically if too much
current is being drawn from the power source or if overvoltage is detected.
3.3.3 AC inlet
The main power source for the VDR is the ship’s AC (110V-230V).
switch to its “OFF” position. Move the battery switch back to its “ON” position after the VDR has
been turned off.
4.1.2 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
being drawn from the power source.
4.1.4 UR address
Must be set to “0” for the first SIU, and “1” for an additional second SIU.
Module Rack
5.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
being drawn from the power source.
5.1.6 MR address
Must be set to “0” for the first SIU, and “1” for an additional second SIU.
RVI 02-004
RVI 02-004D
Ethernet link and speed Ethernet link and activity Ethernet port with PoE
(Yellow) (Green)
RAI 08-001
RAI address: Ethernet link and speed Ethernet link and activity
Ethernet port with PoE
Must be set to “0” (Yellow) (Green)
8 Error codes
Error codes and messages will be displayed by the BCP.
defective/misconfigured NAS.
170 AUDIO
Recording muted Recording of audio has been stopped due to manual intervention
172 NETWORK Data Too much network data is being transmitted to the VDR. Network
Accumulated Excess
data in this context does not include image data. Try to determine
what is wrong using the VDR Explorer i.e. check what has been
received on NI200 – NI215
180 SYSTEM The VDR is in service mode. It is possible to make changes to the
In Service Mode
VDR configuration. When this is done, the mode switch on the
DPU front must be set to position “Normal operation”.
182 BCP The DPU is unable to communicate with the Bridge Control
Communication error
Panel. Check the cable from the DPU to the BCP. Reboot the
system. If the error persists, the most probable cause is a faulty
cable or BCP.
184 BAM The communication to the Bridge Alert Management system has
BAM comm. timeout
been interrupted.
190 DPU The primary fan in the DPU has failed. The secondary fan in DPU
CPU fan failed
will serve as a backup until the problem is rectified. The VDR will
be able to operate normally unless the secondary fan also fails
(error 191). This problem must be rectified latest at the next APT.
191 DPU The secondary fan in the right side of the DPU has failed. This is
Backup fan failed
only a major problem if the primary fan has also failed (error 190).
300- SERIAL Mandatory serial data is not being received. Check that the source
Timeout on SIxx
307 is 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 and make sure that the configuration is
correct.
320- NETWORK Channel Mandatory network data is not being received on channel NI2xx.
Timeout on NI2xx
335 Check that the source is switched on and active, check the cable
and that the VDR configuration is correct.
360- NETWORK Channel Too much network data is currently being received on channel
Excess Data on NI2xx
375 NI2xx. Check that the source is operating correctly. The VDR
Explorer may be used to monitor the data.
400- SERIAL Mandatory serial data is not being received. Check that the source
Timeout on SIxx
431 is 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 and make sure that the configuration is
correct.
441 SERIAL module 2 For a DM100, the second serial module is integrated on the SAP
Missing (SI08-12)
board in the DPU. The most probable cause is that the SAP board
in the DPU is defective.
484 RVI VIDEO An AC powered RVI with incorrect RVI address has been detected.
Wrong RVI address
The RVI address must be 0 or 1. All RVIs connected to the VDR
must be set up in the VDR configuration.
486 RVI VIDEO VIDEO module 3 cannot be detected. The most probable cause is
Module 3 missing
that that the cable to the RVI from the DPU is disconnected or the
RVI is defective. In addition, for an AC powered RVI: Power to the
RVI is switched off, the internal Ethernet cable in the RVI is
disconnected or the video interface module is defective.
488 RVI VIDEO VIDEO module 4 cannot be detected. The most probable cause is
Module 4 missing
that that the cable to the RVI from the DPU is disconnected or the
RVI is defective. In addition, for an AC powered RVI: Power to the
RVI is switched off, the internal Ethernet cable in the RVI is
disconnected or the video interface module is defective.
591- IMAGE The image recorded on channel VDxx exceeds the allocated space
VDxx image too large
598 in the capsule. Check the video image for noise. Check the
calibration of the video channel. Check that “Image Format” in the
VDR configuration is set to PNG. Reduce the number "color mask
bits" if necessary.
701 CAPSULE The VDR is unable to record data to the fixed capsule. Another
Not recording
error explaining why (e.g. #702 CAPSULE Cannot find) is
normally displayed in advance. Try to fix the preceding error.
Otherwise reboot the system.
702 CAPSULE The VDR is unable to detect a fixed capsule. Check that the fixed
Cannot find
capsule is connected correctly. If the error persists, the fixed
capsule is probably defective.
703 CAPSULE The VDR has detected a fixed capsule but is unable to get access to
Cannot access
the memory. If the error persists, the fixed capsule is probably
defective.
704 CAPSULE, too many Too many write-errors (writing to the fixed capsule) have been
write errors
detected by the DPU over a period of time. The most likely cause is
communication problems. Check the cable from the DPU to the
fixed capsule.
705 CAPSULE, too many Too many write-errors (writing to the FRM memory) have been
write errors
detected by the fixed capsule over a period of time. The most likely
cause is serious communication problems or a defective fixed
capsule.
706 CAPSULE, too many Too many read-errors (reading back data from the fixed capsule)
read errors
have been detected by the DAU over a period of time. The VDR
was unable to write and verify data despite several attempts. The
most likely cause is serious communication problems or a defective
fixed capsule.
707 CAPSULE, too many Too many read-errors (reading back data from the fixed capsule)
read errors
have been detected by the fixed capsule over a period of time. The
VDR was unable to write data despite several attempts. The most
likely cause is serious communication problems or a defective
fixed capsule.
708 CAPSULE The VDR found too many data errors within a given interval when
Verification failed
verifying the data written to the fixed capsule. The fixed capsule is
probably defective.
709 CAPSULE The amount of data collected for a 15-second period exceeds the
Record too big
maximum allowed size for the fixed capsule. This is typically
caused by receipt of too much image data. Use the “Analysis of
recorded data” utility on the BCP or in the configurator tool to
determine the cause. If the problem relates to image data, carry out
an OPT and check the recorded images.
710 CAPSULE The amount of data received by the VDR exceeds the capacity of
Record-data too big
the fixed capsule. This is typically caused by receipt of too much
image data. Use the “Analysis of recorded data” utility on the BCP
or in the configurator tool to determine the cause. If the problem
relates to image data, carry out an OPT and check the recorded
images.
711 Capsule The DPU has detected a too high data loss rate (saving to the fixed
Data loss rate too
high
capsule) over a period of time. The most likely cause is
communication problems. Check the cable from the DPU to the
fixed capsule.
721 FLOAT-FREE The VDR is unable to record data to the float-free capsule. Another
Not recording
error explaining why (e.g. #722 FLOAT-FREE Cannot find) is
normally displayed in advance. Try to fix the preceding error,
otherwise reboot the system.
722 FLOAT-FREE The VDR is unable to detect the float-free capsule. Check that the
Cannot find
float-free capsule is connected correctly. If the error persists, the
float-free capsule is probably defective.
723 FLOAT-FREE The VDR has detected a float-free capsule but is unable to get
Cannot access
access to the memory. If the error persists, the float-free capsule is
probably defective.
724 FLOAT-FREE, too many Too many write-errors (writing to the float-free capsule) have been
write errors
detected by the DPU over a period of time. The most likely cause is
communication problems. Check the cable from the DPU to the
float-free capsule.
725 FLOAT-FREE, too many Too many write-errors (writing to the FRM memory) have been
write errors
detected by the float-free capsule over a period of time. The most
likely cause is serious communication problems or a defective
float-free capsule.
726 FLOAT-FREE, too many Too many read-errors (reading back data from the float-free
read errors
capsule) have been detected by the DPU over a period of time. The
VDR was unable to write and verify data despite several attempts.
The most likely cause is serious communication problems or a
defective float-free capsule.
727 FLOAT-FREE, too many Too many read-errors (reading back from the memory) have been
read errors
detected by the float-free capsule over a period of time. The VDR
was unable to read back data despite several attempts. The most
likely cause is serious communication problems or a defective
float-free capsule.
728 FLOAT-FREE The VDR found too many data errors within a given interval when
Verification failed
verifying the data written to the float-free capsule.
729 FLOAT-FREE The amount of data collected for a 15-second period exceeds the
Record too big
maximum allowed size for the float-free capsule. This is typically
caused by receipt of too much image data. Use the “Analysis of
recorded data” utility on the BCP or in the configurator tool to
determine the cause. If the problem relates to image data, carry out
an OPT and check the recorded images.
730 FLOAT-FREE The amount of data received by the VDR has exceeded the capacity
Record-data too big
of the float-free capsule. This is typically caused by receipt of too
much image data. Use the “Analysis of recorded data” utility on the
BCP or in the configurator tool to determine the cause. If the
problem relates to image data, carry out an OPT and check the
recorded images.
731 FLOAT-FREE The DPU has detected a too high data loss rate (saving to the float-
Data loss rate too
high
free capsule) over a period of time. The most likely cause is
communication problems. Check the cable from the DPU to the
float-free capsule.
741 LONG-TERM The VDR is unable to utilize the VDR data disk for the long term
Not recording
recording. Another error explaining why (e.g. #742 LONG-TERM
Cannot find) is normally displayed in advance. Try to reboot the
system. If the error persists, the DPU is probably defective.
742 LONG-TERM The VDR is unable to detect the VDR data disk or utilize the disk
Cannot find
for long term recording. Try to reboot the system. If the error
persists, the DPU is probably defective
743 LONG-TERM The VDR has detected the VDR data disk but is unable utilize the
Cannot access
disk. If the error persists, the disk is probably defective.
744 LONG-TERM, too many Too many write-errors (writing to the VDR data disk) have been
write errors
detected by the DPU over a period of time. The most likely cause is
an internal problem in the DPU. If the error persists, the DPU must
be repaired.
745 LONG-TERM, too many Too many write-errors (writing to the VDR data disk) have been
write errors
detected by the DPU over a period of time. The most likely cause is
a defective VDR data disk (i.e. the SDD inside the DPU). If the
error persists, the DPU must be repaired.
746 LONG-TERM, too many Too many read-errors (reading back data from the VDR data disk)
read errors
have been detected by the over a period of time. The VDR was
unable to read back data despite several attempts. The most likely
cause is an internal problem in the DPU. If the error persists, the
DPU must be repaired.
747 LONG-TERM, too many Too many read-errors (reading back data from the VDR data disk)
read errors
have been detected by the long-term disk over a period of time. The
VDR was unable to read back data despite several attempts. The
most likely cause is a defective VDR data disk (i.e. the SDD inside
the DPU). If the error persists, the DPU must be repaired.
748 LONG-TERM The VDR found too many data errors within a given interval when
Verification failed
verifying the data written to the VDR data disk.
749 LONG-TERM The amount of data collected for a 15-second period has exceeded
Record too big
the maximum allowed size for the VDR data disk. This is typically
caused by the receipt of too much image data. Use the “Analysis of
recorded data” utility on the BCP or in the configurator tool to
determine the cause. If the problem relates to image data, carry out
an OPT and check the recorded images.
750 LONG-TERM The amount of data received by the VDR exceeds the capacity of
Record-data too big
the VDR data disk. This is typically caused by receipt of too much
image data. Use the “Analysis of recorded data” utility on the BCP
or in the configurator tool to determine the cause. If the problem
relates to image data, carry out an OPT and check the recorded
images.
751 LONG-TERM The DPU has detected a too high data loss rate (saving to the long
Data loss rate too
high
term storage) over a period of time. The most likely cause is an
internal problem in the DPU. If the error persists, the DPU must be
repaired.
901- SYSTEM FAILURE The software is not working properly. Restart the VDR and report
ERROR 901-933
933 this error if it is repeated.
970 SELF-TEST The amount of RAM is insufficient to start the VDR. Restart the
RAM size xxx MB,
Should be >= yyy MB
system. If the error persists, then call for assistance.
971 SELF-TEST Required networking interfaces are not available to start the VDR.
xx network
interfaces found, 4
Restart the system. If the error persists, then call for assistance.
required
972 SELF-TEST Required Video (VGA) circuitry could not be initialized. Restart
Failed to initialize
VGA
the system. If the error persists, then call for assistance
983 No communication The BCP 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 up correctly.
984 No communication The initial communication was functional but the communication
to DPU
has failed at some point. The most probable cause is that the VDR
has encountered a system error and completely stopped. Restart the
VDR. If the error persists, the DPU is probably defective.