Transcript
OPERATOR'S MANUAL
VOYAGE DATA RECORDER SIMPLIFED VOYAGE DATA RECORDER
MODEL
VR-3000 VR-3000S
(Applicable to software version 1.5x)
www.furuno.com
The paper used in this manual is elemental chlorine free.
・FURUNO Authorized Distributor/Dealer 9-52 Ashihara-cho, Nishinomiya, 662-8580, JAPAN
All rights reserved.
Printed in Japan
A : SEP . 2010 C : JAN . 27, 2012
Pub. No. OME-44374-C (REFU )
VR-3000/3000S MOL
*00017441012* *00017441012* * 0 0 0 1 7 4 4 1 0 1 2 *
IMPORTANT NOTICES General • This manual has been authored with simplified grammar, to meet the needs of international users. • The operator of this equipment must read and follow the descriptions in this manual. Wrong operation or maintenance can cancel the warranty or cause injury. • Do not copy any part of this manual without written permission from FURUNO. • If this manual is lost or worn, contact your dealer about replacement. • The contents of this manual and equipment specifications can change without notice. • The example screens (or illustrations) shown in this manual can be different from the screens you see on your display. The screens you see depend on your system configuration and equipment settings. • Save this manual for future reference. • Any modification of the equipment (including software) by persons not authorized by FURUNO will cancel the warranty. • All brand and product names are trademarks, registered trademarks or service marks of their respective holders.
How to discard this product Discard this product according to local regulations for the disposal of industrial waste. For disposal in the USA, see the homepage of the Electronics Industries Alliance (http://www.eiae.org/) for the correct method of disposal.
How to discard a used battery Some FURUNO products have a battery(ies). To see if your product has a battery, see the chapter on Maintenance. Follow the instructions below if a battery is used. Tape the + and terminals of battery before disposal to prevent fire, heat generation caused by short circuit.
In the European Union The crossed-out trash can symbol indicates that all types of batteries must not be discarded in standard trash, or at a trash site. Take the used batteries to a battery collection site according to your national legislation and the Batteries Directive 2006/66/EU.
Cd
In the USA The Mobius loop symbol (three chasing arrows) indicates that Ni-Cd and lead-acid rechargeable batteries must be recycled. Take the used batteries to a battery collection site according to local laws.
Ni-Cd
Pb
In the other countries There are no international standards for the battery recycle symbol. The number of symbols can increase when the other countries make their own recycling symbols in the future.
i
SAFETY INSTRUCTIONS WARNING ELECTRICAL SHOCK HAZARD
WARNING Do not disassemble the battery.
Do not open the equipment. Only qualified personnel should work inside the equipment.
Battery fluid is harmful to the eyes and skin, particularly the eyes. If the fluid contacts skin or eyes, flush area with fresh water and contact a physician immediately.
Do not disassemble or modify the equipment.
Do not dispose of the battery or acoustic beacon in fire.
Fire, electrical shock or serious injury can result.
Those components may burst if disposed of in fire. Further, dispose of the battery in accordance with appropriate regulations.
Immediately turn off the power (BATTERY, DC and AC switches in that order) at the DCU and also turn off off the power at the ship's mains switchboard if water leaks into the equipment or the equipment is emitting smoke or fire. Continued use can cause fatal damage to the equipment. Only authorized personnel shall disassemble the DRU.
Do not touch any electricaly conductive parts. Touching electrically conductive parts can result in electrical shock. Use rubber gloves, etc. when conducting inspection or maintenance work. Do not short battery terminals. Short can lead to bursting or fire.
Pressure may build up inside the unit when it is subjected to fire or is retrieved from a great depth. Do not allow rain or water splash to contact the equipment. Fire or electrical shock can result.
WARNING LABELS Warning labels are attached to the DCU. Do not remove the labels. If the label is missing or damaged, contact a FURUNO agent or dealer about replacement. WARNING To avoid electrical shock, do not remove cover. No user-serviceable parts inside.
WARNING To avoid electrical shock, do not remove cover. No user-serviceable parts inside.
ii
Name: Type: Code No.:
Warning Label 1 86-003-1011-2 100-236-232-10
Name: Type: Code No.:
Warning Label 2 03-129-1001-2 100-236-742-10
CAUTION Do not: - use batteries of different capacities - mix old batteries with new - mix batteries of different makes Batteries themselves may become damaged or damage to electrical parts may result.
POWERING DATA COLLECTING UNIT On the power control panel in the Data Collecting Unit (DCU), confirm that the status display shows “- - -“ and the NORMAL LED is lit after the power has been on for two minutes. If not, see Chapter 3.
Procedure for turning on power 1. Turn the AC breaker switch on. 2. Turn the DC breaker switch on if DC power is connected. 3. Turn the BATTERY BACKUP breaker switch on.
Status Display
NORMAL LED
Breaker switches (from left) Battery Backup, DC, AC
Power control panel/status display inside the DCU
Error indication on Remote Alarm Panel (RAP) If the ERROR LED (red) lights on the RAP, check the error number on its status display and refer to the error code tables in Chapter 3.
ERROR LED
Remote Alarm Panel
iii
IF AN INCIDENT OCCURS Press and hold the SAVE button on the Remote Alarm Panel until the SAVE LED blinks. Bring the HDD with you after an incident occurs, if possible.
SAVE LED (yellow)
SAVE button
• The SAVE LED (yellow) starts flashing and shortly thereafter lights. Then, recording to the backup HDD in the Data Collecting Unit is stopped.
• Recording at the Data Recording Unit continues.
iv
TABLE OF CONTENTS FOREWORD.............................................................................................. vi SYSTEM CONFIGURATION..................................................................... vii 1. OPERATION........................................................................................... 1
1.1 Overview ........................................................................................................................ 1 1.2 Operating Procedure ...................................................................................................... 6 1.2.1 Powering, recording.........................................................................................................6 1.2.2 Stopping recording...........................................................................................................6 1.3 Operation on Remote Alarm Panel ................................................................................. 7 1.4 Removing HDD at an Incident ........................................................................................ 8 1.5 How to Release DRU ..................................................................................................... 8
2. MAINTENANCE ..................................................................................... 9
2.1 Annual Recertification .................................................................................................... 9 2.2 Cleaning ......................................................................................................................... 9 2.3 Software Maintenance.................................................................................................. 10 2.3.1 Software list ...................................................................................................................10 2.3.2 Checking software version of system program ..............................................................10 2.3.3 Checking software version of RAP ................................................................................10 2.4 Replacing Batteries .......................................................................................................11 2.5 Replacing Acoustic Beacon .......................................................................................... 12 2.6 Replacing Backup HDD................................................................................................ 13 2.7 Replacing Fuses........................................................................................................... 14 2.8 Replacing Parts ............................................................................................................ 14 2.9 Verifying Recording Function of the DRU....................................................................... 15 2.10 Confirmation of Peripheral Devices.............................................................................. 16
3. TROUBLESHOOTING.......................................................................... 17
3.1 General Troubleshooting .............................................................................................. 17 3.2 Error Codes.................................................................................................................. 18 3.3 Testing Display of Remote Alarm Panel........................................................................ 20
4. LOCATION OF PARTS......................................................................... 21
4.1 Parts Location .............................................................................................................. 21 4.1.1 Data Collecting Unit (VR-3010) .....................................................................................21 4.1.2 Data Recording Unit (VR-5020-9G or VR-5020-6G).....................................................22 4.1.3 Junction Box (IF-8530) ..................................................................................................23 4.1.4 Remote Alarm Panel (VR-3016)....................................................................................23 4.2 Parts List ...................................................................................................................... 24
5. INTERFACE (IEC 61162-1, IEC 61162-2)............................................. 25
5.1 Data Sentences............................................................................................................ 25 5.2 Interface Circuits .......................................................................................................... 38 5.2.1 IEC 61162-1 ...................................................................................................................38 5.2.2 IEC 61162-2 ...................................................................................................................39
APPENDIX: PLAYING BACK RECORDED DATA ................................... 40 SPECIFICATIONS ..................................................................................................... SP-1
v
FOREWORD A Word to the Owner of the VR-3000, VR-3000S Thank you for purchasing the FURUNO Voyage Data Recorder (VDR) VR-3000, Simplified Voyage Data Recorder (S-VDR) VR-3000S. We are confident you will discover why FURUNO has become synonymous with quality and reliability.
What is a VDR, S-VDR? A VDR records various data and events encountered aboard ship. The purpose of the VDR is to help investigators locate the causes of marine incidents. There is no principle difference between a VDR and an S-VDR. The difference is the amount of information required to be recorded. The VDR is required to record more data than the S-VDR. Note that this manual refers to either the VDR or S-VDR as VDR. The revised SOLAS Chapter V requires the installation of VDRs on passenger ships of 150 GT and above on all voyages and other ships of 3000 GT and above on international voyages and for newly built ships on and after 1 July, 2002. The basic VR-3000/VR-3000S consists of a Data Collecting Unit (DCU), a Data Recording Unit (DRU), a Remote Alarm Panel (RAP) and microphones to record bridge audio. The VR-3000 is also equipped with a Junction Box (JB), which is optional on the VR-3000S. The DCU contains the Data Processor Unit, interface modules and backup batteries. It collects data from sensors as required by the IMO and IEC standards. The DCU processes the incoming data and information in the order of occurrence while old data is overwritten with new data for storage in the DRU for a 12 h period. The batteries supply power to the DCU to record bridge audio for 2 h in case of a main ship’s power failure. The flash memory in the DRU stores the data coming from the DCU. All essential navigation and status data including bridge conversation, VHF communications, and radar images are recorded. The data can be retrieved by using playback software for investigation after an incident. The DRU components are embodied in the protective capsule. The capsule ensures survival and recovery of the recorded data after an incident. An acoustical pinger helps locate the DRU underwater.
Features • • • • • • •
Reliable and fast data exchange between DCU and DRU via a single IEEE1394 cable. Easy commissioning and maintenance by PC downloading/uploading. 12-hour recording of normal sensor loading in standard memory. UTC time tagged for system synchronization and easy data retrieval. Choice of flash memory capacity in the Data Recording Unit. Backup hard disk (HDD) for storage and retrieval of data. Meets IMO A.861 (20), IEC 61996 and other relevant standards.
vi
SYSTEM CONFIGURATION Data Recording Unit (DRU) VR-5020-6G/VR-5020-9G Waterproof MIC VR-3012W Bridge MIC VR-5011
Max. 6 ch VHF I/F IF-5200
Remote Alarm Panel (RAP) VR-3016
Max. 2 ch
VHF Audio Max. 2 ch IEC 61162 serial data
Serial (Max. 8 ch)
Data Collecting Unit (DCU) VR-3010
24 VDC
Serial (1ch)
Junction Box (JB) IF-8530*
Radar I/F RI-3010*
Alarm Monitoring System
Junction Box (JB) IF-8530 (max. 2)
Analog (Max. 16 ch)
Digital (Max. 64 ch)
No. 1 Radar No. 2 Radar
Radar Video SW Interface IF-1000RVC
100-230 VAC
24 VDC
PC Live Player V4 VR-3020
: Standard supply equipment and cable : Optional supply equipment and cable : Local supply equipment and cable * Optional with VR-3000S
GPS Speed log Heading Serial (Max. 8) Echosounder Autopilot Analog Engine telegraph (Max. 16 ch) Steering gear M/E remote system Main air compressor Digital (Max. 64 ch) Bow thruster Shell door system Watertight doors Fire doors Anemometer Fire detection Main alarms Others
Serial (1 ch)
Environmental category DCU DRU RAP Bridge MIC Waterproof MIC VHF I/F unit JB Radar Video SW Interface
Protected from weather Exposed to weather Protected from weather Protected from weather Exposed to weather Protected from weather Protected from weather Protected from weather
For the S-VDR, where it is impossible to obtain radar data, the AIS target data should be recorded as a source of information from other ships. (Ref. IMO Res.MSC.163(78), section 5.4.7.)
vii
This page intentionally left blank.
viii
1. OPERATION 1.1 Overview The VR-3000/VR-3000S consists of Data Collecting Unit (DCU), Data Recording Unit (DRU), Remote Alarm Panel (RAP), Junction Box (JB, optional supply with VR-3000S) and bridge microphone units. The VDR system continuously stores data from the past 12 hours onto the Flash Memory in the capsule, erasing the oldest data stored as new data is recorded. The data to be recorded includes the following: Parameters to be recorded
IEC 61162 formatter
Date and time
ZDA
Ship’s position and datum used
GNS and DTM
Speed (water and/or ground)
VBW
Heading (true)
HDT
Heading (magnetic)
HDG
AIS-VHF data-link message
VDM
AIS-VHF data-link own-vessel message
VDO
Depth (echo sounder)
DPT
Alarms
ALR
Rudder order/response manual
RSA
Rudder order/response automatic
HTC, HTD
Engine order/response
RPM, XDR
Hull openings, watertight doors
XDR
Accelerations and hull stress
XDR, ALR
Wind speed and direction
MWV
VDR alarm output
$VRALR
Notes
No requirement for S-VDR to send alarm messages
Radar data Bridge audio VHF communication audio
Power supply precaution If ship’s mains power source (100-230 VAC) and emergency source fail, the VR-3000/VR-3000S continues to record bridge audio for 2 h from backup batteries. When using the backup batteries, suspend power to the IF-8530 Junction box..
1
Continuity of storing data The VDR should be provided with power to store data for 12 h on a first-in, first-out basis. Recording is terminated only under the following circumstances: a) During essential maintenance while the vessel is in port. b) When the vessel is laid-up. c) In case of emergency, when the backup HDD is removed.
Data Collecting Unit The DCU mainly consists of Data Processor Unit and Power Control Panel. The DCU includes two 12 V backup batteries with a lifetime of approximately four years. The DCU collects the data from various sensors and radar and records them in the DRU and backup HDD. Recording interval of data and audio is as follows: - Radar video signal: every 15 seconds - Bridge and VHF audio: real time - IEC sentences: when received - Analog and digital data: every second LEDs: Light (green) when respective power is applied.
Status Display LEDs (from left) SAVE (yellow): When stopping the data recording, this starts blinking from OFF state, then lights steadily. If the HDD is disconnected, this LED lights also. NORMAL (Green): On at normal operation. ERROR (red): Lights for error. Breaker switches (from left) Battery Backup, DC, AC
2
Data Recording Unit The Data Recording Unit is housed in a highly visible protective capsule which can withstand a fire of 1100°C for 1 hour and deep-sea pressure of 6000 m. The underwater acoustic beacon (pinger) on the capsule automatically transmits 10 ms pulses at 37.5 kHz for at least 30 days when it is submerged in water. The expected life of the beacon is 6 years. The DRU is connected to the Data Collecting Unit (DCU) with a non-halogen FireWire cable (IEEE1394). Underwater Acoustic Beacon
Data Recording Unit
Integrity The recording integrity is ensured by continuous monitoring of power supply, record function, bit error rate, and microphone functionality. Visual alarm is generated for malfunction of any of these. Alarm status is also indicated by relay contacts.
Data items to be recorded Date and time Date and time are obtained from an external GPS navigator referenced to UTC. Time information is recorded at intervals of 1 s. Without date and time data, no data except audio signal is recorded.
Ship’s position and datum used Latitude, longitude and datum are obtained from a GPS navigator, Loran-C receiver or other EPFS or INS available on standard digital interface. The source of data is identifiable on playback.
Speed (water and/or ground) Speed through the water (STW) or speed over the ground (SOG) is recorded at intervals of 1 s. The resolution is 0.1 kt. Transverse speed is also indicated when available on board.
Heading (true, magnetic) Heading is recorded at intervals of 1 s to a resolution of 0.1°. The data is labeled G (gyrocompass), GPS, GLONASS, MAG. If heading information is not available in IEC 61162 format, an appropriate interface may be necessary.
3
AIS-VHF data-link message, AIS-VHF data-link own-vessel message Where there is no commercial off-the-shelf interface available to obtain radar data then AIS target data shall be recorded as a source of information regarding other ships, otherwise AIS information may be recorded additionally as a beneficial secondary source of information on both other and own ship. The VDM message (UAIS VHF Data-link) shall be recorded in such a way that all target data available from the onboard AIS are acquired. If the VDO message (UAIS VHF Data-link Own-vessel report) is recorded, this shall be additional to the recording of individual sensor data.
Depth (echo sounder) Depth under keel up to a resolution of 0.1 m as available on the ship is recorded.
Alarms The status of all IMO mandatory alarms is recorded individually with ID number and time stamp. Audible alarms from the alarm units are stored simultaneously by the bridge audio microphones.
Rudder order/response Rudder order and response angles are recorded up to a resolution of 1° as available on the ship. The rudder information is recorded. If more than one rudder is provided, the circuitry can be duplicated.
Engine order/response The DCU obtains the engine order and response from the engine telegraph or direct engine control. The signal level is normally 0-10 V. The engine parameters with shaft revolution and ahead/astern indicators are recorded to a resolution of 1 rpm. All order and response from bow, stern, thruster, tunnel thrusters and controllable pitch propellers shall be recorded. The S-VDR shall record this data if said serial data is available.
Hull openings, watertight doors Inputs digital or RS-422 serial can be connected individually. The data is received at intervals of 1 s and stored with time stamps. Serial data sentence XDR is received at a data rate of 1,200-9,600 baud.
Accelerations and hull stresses The DCU obtains signals from appropriate hull stress and response monitoring devices. The inputs are recorded individually and stored with time stamps. Serial data sentence XDR is received at a data rate of 1,200-9,600 baud.
Wind speed and direction The DCU obtains the signal from appropriate wind speed and direction sensor. The inputs are recorded individually and stored with time stamps. Serial data sentence XDR is received at a data rate of 1,200-9,600 baud.
VDR alarm output There is no requirement for the S-VDR to send alarm messages. If, as an option, such messages are sent then the appropriate sentence format is ALR.
4
Radar data Radar image including range rings, EBLs, VRMs, plotting symbols, radar maps, parts of SENC, voyage plan, and other essential navigational indications, is recorded in the DRU via the interface in the DCU which is connected to the buffered video output of the radar display unit. One complete picture frame is captured at intervals of 15 s. The radar display complying with IEC 60936-1 should have a buffered output (VESA DMTS compatible) with resolutions between 640 x 480 and 1280 x 1024, and can be directly connected with the VDR. Scanning may be interlaced or non-interlaced.
Bridge audio Up to six microphones are supplied as standard to record conversation at conning station, radar display and chart table. If possible, the microphones should be positioned to capture the audio from the intercom, public address system, and audible alarms on the bridge. The microphones are labeled Mic1, Mic2, etc. Microphone captures conversation in the bridge, audio signals from equipment and sound from machinery. The microphone generates a test beep every 12 hours which is also recorded. The microphone picks up audio signals ranging from 150 to 6000 Hz.
Communications audio A maximum of two VHF communications are recorded for both transmitted and received audio signals. The VHF radio connections are labeled VHF1 and VHF2.
5
1.2 Operating Procedure The VDR comes with a key to lock the DCU to protect against any unauthorized access. The key must be kept securely after installation.
1.2.1 Powering, recording On the power control panel in the DCU, turn on the AC SUPPLY MAINS, DC SUPPLY MAINS and BATTERY BACK-UP switches in this order. Confirm that the NORMAL LED on the power control panel and RAP lights. The VDR records data automatically in the DRU and backup HDD.
NORMAL LED
NORMAL LED
REMOTE ALARM PANEL
Breaker switches (from left) Battery Backup, DC, AC POWER CONTROL PANEL
1.2.2 Stopping recording Recording is terminated only under the following conditions: - During essential maintenance purposes while the vessel is in port. - When the vessel is laid-up. To stop recording, turn off the BATTERY BACKUP, DC SUPPLY MAINS and AC SUPPLY MAINS switches in this order. DO NOT turn off the system by the main breaker while the BATTERY BACKUP switch is on. If this is done, the system operates on the batteries. The system stops after running on batteries after 2 hours.
6
1.3 Operation on Remote Alarm Panel No power switch is provided on the Remote Alarm Panel; it is turned on and off by the power switch on the DCU. When the ERROR LED (red) on the Remote Alarm Panel is on, identify the error by checking code number in the error code tables in Chapter 3. The buttons on the Remote Alarm Panel work as described in the figure below. Buzzer
Status Display LEDs (from left) SAVE (yellow): Starts blinking from OFF state when recording is stopped, then lights steadily. If the HDD is disconnected, this LED lights also. NORMAL (Green): On at normal operation. ERROR (red): Lights for error.
DIMMER: Adjust panel backlighting; display software version no. (pressed together). TEST: Tests LCD.
ACK: Silences buzzer.
SAVE: Stops recording onto the backup HDD. See the NOTICE below.
Remote Alarm Panel Note: The buzzer sounds every time the radar connected to the VDR is turned off. Press the ACK button to silence the alarm.
NOTICE After pressing the SAVE button, data will not be recorded. Replace the HDD with an initialized one, or contact a FURUNO agent for necessary procedure.
SAVE button The SAVE button functions to stop recording to the backup HDD in the DCU. If an incident occurs, press this button to stop recording to the backup HDD, and then see paragraph 1.4 for how to remove the HDD,
7
1.4 Removing HDD at an Incident VDR information is copied automatically into the backup hard disk drive (HDD) for more than 12 hours (max. 13 hours) and is then automatically written over with new data. Bring the HDD with you after an incident if possible. Press the SAVE button only when an incident occurs. To replace the HDD under other circumstances, see section 2.6. To remove the HDD, do the following: 1. Press the SAVE button (long press) on the RAP (Remote Alarm Panel). The yellow LED starts blinking, showing that recording is being terminated. 2. Wait until the SAVE LED lights steadily. Note: Turning off the power is not required at an incident. However, to replace the HDD, turn off the power after the step 2. 3. Pull the knob on the HDD holder to open the holder. 4. Disconnect the IEEE1394 cable. 5. Remove the HDD. Knob
HDD
HD
IEEE1394 Cable
DCU, showing location of HDD
1.5 How to Release DRU To remove the DRU from the bracket (cradle) do the following: 1. Loosen the hand-tightened cap. 2. Pull the DRU cable straight out. (The cable may be cut after an incident.) 3. Remove two snap pins and then two hinge pins. 4. Lift the release levers.
8
4. Release levers.
1. Cap
2. DRU cable 3. Hinge pin
3. Snap pin
2. MAINTENANCE Periodic checks and maintenance are important for proper operation of any electronic systems. This chapter contains maintenance instructions to be followed to obtain optimum performance and the longest possible life of the equipment. Any maintenance must be executed by a suitably qualified technician.
WARNING ELECTRICAL SHOCK HAZARD Do not open the equipment. Only qualified personnel should work inside the equipment. Do not disassemble or modify the equipment. Fire, electrical shock or serious injury can result.
2.1 Annual Recertification The VDR must undergo an annual performance test to recertify suitability. This test is conducted by a test engineer authorized by the manufacturer and certified by a relevant ship classification society, the content and procedure of the test in accordance with the regulations of that society. For further details about the VDR performance test, contact your ship classification society.
2.2 Cleaning Dirt or dust may be removed from units with a soft cloth. Fresh water-moistened cloth may be used to remove stubborn dirt. DO NOT use any commercial cleaning agents to clean any unit. They can remove paint and markings. This is especially important with the Waterproof Microphone VR-3012W. The watertight integrity of the microphone will be compromised if any commercial cleaning agent contacts the ventilation sheet behind the MIC cover.
MIC COVER
Waterproof microphone VR-3012W (bulkhead type)
9
2.3 Software Maintenance 2.3.1 Software list The software and software version of the VR-3000/VR-3000S are as shown in the table below. VR-3000/VR-3000S software list Software name
Software version
Date
VR-3000 System Program
2450031-01
Mar 2006
VR-3000 RAP
2450026-01
Mar 2006
2.3.2 Checking software version of system program Follow the procedure below to check software version of system program. 1. Start up a PC that uses Windows XP or Windows 2000 OS. 2. Change the IP address to 10.0.0.102 and the subnet address to 255.0.0.0. 3. Connect the cross LAN cable (supplied) between the LAN port on the PC and J14 (Data) in the DCU of the VR-3000/VR-3000S. 4. Start up the VDR Maintenance Viewer from the PC. 5. Select Guest and click OK. 6. Open the menu of this program from Tool/Status Monitor. 7. The program version is displayed at the right side of the VDR VERSION.
2.3.3 Checking software version of RAP Push and hold down the RAP’s plus and minus buttons together. A three-digit number appears (for example, “101”) and these digits are the version number.
10
2.4 Replacing Batteries Every four years, the back-up batteries (2 pcs.) in the DCU must be replaced with new ones (Type: OP24-12 Code no.: 004-385-010) by a qualified service engineer. Note that the batteries should be recycled. Contact a FURUNO dealer for further details. Observe the following precautions with the batteries:
CAUTION
WARNING Battery handing precautions - Do not attempt to dismantle the battery. If accidental skin/eye contact is made with the battery fluid, wash the affected area/part immediately with liberal amounts of clean fresh water and seek IMMEDIATE medical attention.
Do not: - use batteries of different capacities - mix old batteries with new - mix batteries of different makes Batteries themselves may become damaged or damage to electrical parts may result.
- DO NOT INCINERATE batteries as they are liable to rupture if placed into a fire. Batteries that have reached the end of their service life must be disposed of in accordance with appropriate regulations. - Do not short battery terminals. Short can lead to bursting or fire.
To replace the batteries, do the following: 1. Open the DCU door with its key. 2. Power off the DCU. 3. Unfasten J3 connector from the PDU Board (24P0083) 4. Unfasten two screws securing the batteries. 5. Disconnect four battery leads, which are covered with the “vinyl boots”. 6. Use the handle to remove batteries from the DCU. 7. Replace batteries. 8. Lock the DCU.
Battery leads (under vinyl boot) Battery Battery Screw
Screw J3
DCU, inside view
11
2.5 Replacing Acoustic Beacon The life of the underwater acoustic beacon is approximately 6 years. It must be replaced (Type: DK-120, Code no. 000-148-648) by a qualified service technician before validity date marked on the beacon.
1. Unfasten two bolts and remove the beacon cover. 2. Use box screwdriver (7 mm) or slotted screwdriver to unfasten four bolts and then remove the beacon. 3. Attach a new beacon.
Bolts Water switch is right side. (The label is upside-down.) Validity date should face in front.
Acoustic beacon
DRU (Beacon cover removed) NOTICE: As the acoustic beacon contains a battery, it must be disposed of in accordance with appropriate regulations.
12
2.6 Replacing Backup HDD On some vessels several backup HDDs (Type: VR-3011-A, Code No.:001-173-390, Option) are carried onboard, replacing one when it is necessary to transport it from the vessel for playback and extract. A backup HDD may only be replaced in the follow situations: 1) When the equipment can be powered off; for example, maintenance while in port, etc. 2) An incident has occurred and the Save button on the RAP (VR-3016) was operated to stop recording. An HDD may not be re-used for recording after the Save button has been operated four times. Contact a FURUNO dealer for further details. A backup HDD records navigation data for more than past 12 hours (48 hours max). For longer recording, use Live Player V4. Change
DCU VR-3010 HDD VR-3011-A
DRU VR-5020
RAP VR-3016
AC Adapter HDD VR-3011-A
IEEE1394 (4Pin – 6Pin)
PC for Playback / Extract
Replacing backup HDD 1. Open the DCU with its key. Turn off the DCU. 2. Pull the knob on the HDD holder to open the holder. 3. Disconnect IEEE1394 cable from the HDD. Remove the HDD. 4. Set new HDD to holder. 5. Connect IEEE1394 cable. 6. Push knob on the HDD holder to close the holder. Turn on the DCU. 7. Confirm that HDD is operating (DCU power is ON, Save LED is OFF) with no error. 8. Close the DCU and lock it with its key. 9. Refer to the operator’s manual of the Live Player V4 for how to playback/extract recorded data from the Backup HDD.
Knob
HDD
HD
IEEE1394 Cable
13
2.7 Replacing Fuses The battery cable in the DCU contains two 10A fuses in fuse holders. If a fuse blows, the BACKUP BATTERY LED may not be lighting. Find the cause before replacing a fuse. Have a serviceman replace any fuse.
Fuses
2.8 Replacing Parts Interval-specific parts The batteries in DCU and the acoustic beacon on the DRU must be replaced every 4 and 6 years respectively to comply with IMO conventions. Record the date of expiration on the card in the card holder on the door of the DCU. Part Battery in DCU Acoustic underwater beacon in DRU
Replacement interval 4 years 6 years
Remarks 2 pcs., replace together
Consumable parts The parts in the table below should be replaced before the estimated lifetime shown. The period of expiration begins from the date of installation. Record the date of replacement on the card in the card holder on the door of the DCU. Consumable part Backup HDD
Life 2 years / 25℃
DC-DC converter
4 years / 25℃*
DCU chassis fan DCU CPU fan
6 years / 25℃* 6 years / 25℃*
CMOS battery on CPU board in DCU
6 years / 25℃
AC power supply
6 years / 25℃
Remarks ・Data cannot be recorded to the backup HDD when it fails. Error 018 is generated when this occurs. The life of VR-3011-A (Code No.: 001-173-390): 10 years / 25℃ If DC power supply fails, RAP indicates 082 and AP in DCU indicates 84. Failure of one or both of these fans prevents the CPU from operating, which may prevent start up of the VDR. Failure of this battery prevents GPS time synchronization. Error 026 is generated when this occurs. If AC power supply fails, RAP indicates 214 with AC power switch ON.
* = Product has a 90% probability of achieving full lifespan
14
2.9 Verifying Recording Function of the DRU Verify the DRU’s recording function at the annual inspection and when repairing or maintaining the VDR or sensors connected to the VDR. The verification requires the Live Player V4. Refer to its Operator's Manual for the operating procedure. Note that data cannot be extracted during recording. 1. Start the Live Player V4 on the PC. 2. Open the Tool menu and select Source Select. Select Live from the pull-down menu. 3.Click the Alarm tab and open Alarm History 4. Set the Playback/CPU switch in the DCU to the Playback position. 5. Wait about 12 minutes and confirm that Alarm 174 occurs on Alarm History of Live Player V4. 6. Connect the PC to the DCU as shown in the Figure below.
DCU
Disconnect cable from HDD.
Set slide SW to Playback. J8 (DRU) PC
DRU
J6 (Playback)
IEEE1394 cable
7. Disconnect the cable attached to the Backup HDD. 8. Open the Tool menu and select Source Select. Select DRU from the pull-down menu. 9. Click the Analyze Track button. 10. Click the Connect button. 11. Select Extract from the Tool menu to show the Extraction dialog box. 12. Select the track to extract. 13. Click the Select button and select the location where to save data. 14. Click the Start button. 15. After the extraction is completed, click OK, Close and Close in that order. Then, do the following. a) Disconnect the cable between the PC and J6 in the DCU. b) Connect the Backup HDD. c) Set the Playback/CPU slide switch in the DCU to the CPU position.
15
2.10 Confirmation of Peripheral Devices Confirm the data from serial signal output devices, analog signal output devices and contact signal output devices. To do this, connect the PC to the DCU and use the Live Player software.
Serial signal output devices The threshold levels of the time-out for serial signal input are preset. If the data is not input to the VDR, an error code appears on the Remote Alarm Panel (see paragraph 3.2). Confirm the accuracy of the input signal, comparing the value of the input sensor and preset value in the VDR.
Analog and contact signal output devices Confirm the signal value and accuracy, comparing the indication of the input device and the input value on the VDR.
16
3. TROUBLESHOOTING This chapter provides information on possible causes of problems you may experience with your VDR. If you still have a problem after referring to the table, contact your local dealer or national distributor for further advice. Always provide the product serial number.
3.1 General Troubleshooting Use the table below to identify the trouble, cause and possible solution. Troubleshooting table Symptom
Possible causes
Possible solution
AC and/or DC LED not lit
No power supply
Check the breaker switches on ship’s mains switchboard.
BATTERY BACKUP LED not lit
No power from the battery
Call for service.
ERROR LED lighting in red
Malfunction of the system
Restart the system. If the problem still remains, call for service. Check integrity of DRU connection.
17
3.2 Error Codes Error codes may appear on the status display on the Power Control Panel to alert to possible trouble. Below is a list of those codes. System soft ware: 2450031-1.5x Error Code
Error Name
---
Description
Action
Normal operation. “---” is shown at startup or when recognizing HDD.
HDD
BACK_UPHDD_MIS
Backup HDD not connected to VDR,
1) SAVE button pressed and backup HDD
SING
or no memory area.
removed: Replace backup HDD. 2) Other situations: Reset VDR. If normal operation not restore, request service
018
Backup HDD No
This indicates that the BACKUP has
Connect BACKUP HDD or investigate LOG
Connection
been disconnected more than 120
and repair/replace.
seconds. 022
026
DRU No Connection
DRU has been discontinued more
Connect DRU again or investigate LOG
than 120 seconds.
and repair or replace.
GPS Large Time
This indicates that the time
Restart VR-3000/S. Try to see if the CMOS
Difference
difference between system time and
clock is set correctly. If not, set it and
time supplied by UTC source is
restart VR-3000/S. If yes, find out why the
more than the specified time.
time source device GPS is delivering “out of bands” time info.
042
082
Radar No
One of the active/enabled video
If radar is turned OFF, press ACK on the
Connection
channels can not grab from the
RAP to silence alarm. Turn on radar. If no
channel. This can be either because
error appears, the system is normal. If error
radar is turned OFF or wrong
occurs again, check cable connections or
configuration.
setting.
RAP is missing. Connection to RAP
When RAP and AP error codes are “082”,
is lost.
check cable connected to RAP and
RAP No Connection
reconnect RAP. When RAP error code is “082” and AP error code is “084”, see error code “082+084”. 084
AP No Connection
No alarm panel connection.
When RAP and AP error codes are “084”, check connection to alarm panel. When RAP error code is “082” and AP error code is “084”, see error code “082+084”.
18
Error Code 082+084
Error Name
Description
Action
Fatal system Failure
Fatal system error. This indicates
Reboot VR-3000/S manually. If VR-3000/S
that VR-3000/S can not be rebooted
does not recover, request service.
automatically.
Note: After switching to battery drive (error
(RAP=082, AP=084)
code 214), this error may occur. The error disappears and the system recovers after AC and/or DC power is reconnected. 088
JB No Connection
Indicates that Junction Box (No.1) is
Check cable and IP-address setting.
missing. 094
098
170
171
173
Backup HDD
Indicates that Backup is inactive-not
Check connection to Backup HDD. If not
Recording Fail
storing data.
still storing, request service.
DRU Recording Fail
Indicates that DRU is inactive-not
Check connection to DRU. If not still
storing data.
restarting recording, request service.
VDR Configuration
Data can not be stored because
Restore VDR setting data. If not, request
Fail
VDR setting data is corrupted.
service.
VDR Recording
Radar video inputs over the capacity
Check or reduce the radar channels or
Buffer Overflow
of the recording buffer memory.
video resolutions.
Fatal System Failure
Fatal system error. VR-3000/S
If VR-3000/S repeat continuously, request
rebooted automatically after an error
service.
occurred. 174
186
214
IEEE1394 Bus
Cannot Recover DRU and Backup
Restart VDR. If VR-3000/S does not
Recover Giveup
HDD
recover, request service.
DRU Memory
It looks that data can not be
Modify radar recording setting. Max.
Shortage
recorded more than 12 hours.
recordable channel: two channels.
Battery Running
Both AC and DC power are down
Reconnect AC and/or DC power.
and switching to battery drive. Audible alarms are generated for max. two. 218
MIC Test Fail
This ALARM is issued when the
Check MIC TEST in the VDR Maintenance
microphone test fails. This test can
Viewer. If this is OK, locate the faulty
be run from Audio tab in the VDR
microphone and check/replace it.
Maintenance Viewer, and is run every 12-hours during normal operation. 226
DRU Flash Device
This indicates that no. of FLASH
Check if no. of FLASH devices and
No match
device found in DRU and defined
configuration setting are same.
in CONFIGURATION is not same. 234
GPS No Connection
System does not receive UTC
Check that a valid UTC source is
information.
connected to the serial port defined as UTC source.
19
Error Code 246
Error Name
Description
Action
PDU No Connection
Cable connection inside DCU is
Check cable between PDU and CPU block
faulty.
in DCU.
254
Self Test Fail
System failed by the self test.
Request service.
3xx
Serial No
Data is not delivered from a serial
Reconnect serial data. Check failed device.
(301-372)
Connection
channel within an assigned time.
401
Battery No
Battery voltage is not coming or it is
Confirm that the battery switch is turned on.
Connection or
low.
If OK, battery is required to replace a new
Battery Voltage Low. 402
Terminal Board No
one. Terminal board is abnormal.
Connection
Confirm cable connection between terminal board and audible interface board.
403
Battery Voltage Low
Battery voltage is lowered.
It is required replacement of battery.
404
DRU Bad Sector
DRU memory device failure.
Restart VDR. If error occurs again, request
Full 405
BaukupHDD Bad
service. BackupHDD memory device failure.
Sector Full
Restart VDR. If error occurs again, request service.
406
DUR Exchanged
This indicates that DRU is replaced.
Restart VR-3000/S.
407
Backup HDD
This indicated that backup HDD is
Restart VR-3000/S.
Exchanged
replaced.
Frame Grabber
Radar interface board is available
Board Fail
but it is not recognized.
Audio Board Fail
Audible interface board is available
411
412
Request service.
Request service.
but it is not recognized. 413
Serial Board Fail
Serial interface board is available
Request service.
but it is not recognized. 42x
JB No Connection
(442-428) 431
Poor connection between JB
Check cable and IP-address setting.
(No.2-8) and DCU. DCU Serial Buffer
Serial data from DCU serial
Restart VDR. If error occurs again, request
overflow
channels (1-8) are not recorded to
service.
DRU and Backup HDD correctly. 432
JB Buffer overflow
Serial, analog and digital data from
Restart VDR. If error occurs again, request
Junction Box are not recorded to
service.
DRU and Backup HDD correctly. 433
DRU Device Config
The recording time may shorten
Failure
because DRU is not formatted
Request service to reformat DRU.
properly. 434
BackupHDD Device
The recording time may shorten
Config Failure
because BackupHDD is not formatted properly.
20
Request service to reformat BackupHDD.
Error Code
Error Name
Description
Action
435
DRU Device
Serial data from DRU are not
Restart VDR. If error occurs again, request
Recording Verify
recorded correctly because the DRU
service to reformat DRU.
Failure
format is out of order.
BackupHDD Device
Serial data from BackupHDD are not
Restart VDR. If error occurs again, request
Recording Verify
recorded correctly because the
service to reformat BackupHDD.
Failure
BackupHDD format is out of order.
Fatal System Failure
Fatal system error. This indicates
Restart VDR manually. If VR-3000/S does
that VR-3000/S can not be rebooted
not recover, request service.
436
437
automatically. 438
VDR System
VDR system information can not be
If error is not recovered automatically,
Information Error
acquired. Usually, this error is
restart VDR. If VR-3000/S does not
recovered automatically.
recover, request service.
3.3 Testing Display of Remote Alarm Panel Press the TEST button on the RAP to check that all LCD segments are displayed properly.
21
4. LOCATION OF PARTS 4.1 Parts Location 4.1.1 Data Collecting Unit (VR-3010) Fuses
From top: 1) RADAR I/F Board (RI-3010) 2) AUDIO Board 3) SERIAL Board 4) Riser Card (24P0068) 5) CPU Board
Battery (OP24-12) (2 pcs.) Backup Hard Disk (HDD) (VR-3011-A)
Compact Flash Card
PDU Board (24P0083)
CONNECTOR PANEL board (24P0081)
AP PANEL Board (24P0076B) AP MAIN Board (24P0075B) (underneath) LED PANEL Board (24P0082)
Power Supply (RTW28-11RN-1) (underneath) DC-DC Converter (ACE-716C-RS) (underneath)
Terminal Board 2 (24P0079)
Terminal Board 1 (24P0078) (w/WAGO connectors)
Data Collecting Unit (VR-3010)
22
4.1.2 Data Recording Unit (VR-5020-9G or VR-5020-6G) CONNECTOR Board (24P0042)
FLASH DISK Board (FW-ATA2501-1)
Underwater Acoustic Beacon (DK-120)
CONNECTION Board (24P0087) 2.5-inch FLASH DISK (SLFLD25-8GM1U1 (for 6G) or DK0090G88TNO (for 9G))
DRU
REPEATER Board (24P0080) (Firewire cable connects to CONNECTOR Board.)
Components inside capsule
Data Recording Unit (VR-5020-9G or VR-5020-6G)
23
4.1.3 Junction Box (IF-8530) MAIN Board (24P0069)
Terminal Board (24P0077) (w/WAGO connectors)
Junction Box (IF-8530)
4.1.4 Remote Alarm Panel (VR-3016)
RAP PANEL Board (24P0076A) (underneath) RAP MAIN Board (24P0075A) (underneath)
Remote Alarm Panel (VR-3016)
24
4.2 Parts List This equipment contains complex modules in which fault diagnosis and repair down to component level are not practical (IMO A.694(17)/8.3.1. Only some discrete components are used. FURUNO Electric Co., Ltd. believes identifying these components is of no value for shipborne maintenance; therefore, they are not listed in this manual. Major modules can be located on the parts location on previous pages. Name
Type
Code No.
Data Collecting Unit (VR-3010) AP MAIN Board
24P0075B
004-385-320
AP PANEL Board
24P0076B
004-385-330
AUDIO Board
PCI-9111-DG
000-148-411
Battery (2 sets)
OP24-12
004-385-010
Compact Flash Card
CFI-128MDG(H02AA)
004-385-140
CONNECTOR PANEL Board
24P0081
004-385-110
CPU Board
PEB3730VL2A
004-383-400
DC-DC Converter
ACE-716C-RS
004-385-450
RADAR I/F Board
RI-3010
004-388-070
LED PANEL Board
24P0082
004-385-340
PDU Board
24P0083
004-384-750
Power Supply
RTW28-11RN-1
004-385-390
Riser Card
24P0068
004-385-070
SERIAL Board
99033-8
000-156-911
Terminal Board 1
24P0078
004-385-350
Terminal Board 2
24P0079
004-385-700
Backup Hard Disk (HDD)
VR-3011-A
001-173-390
Data Recording Unit (VR-5020-9G or VR-5020-6G) CONNECTION Board
24P0087
000-166-816-10
CONNECTOR Board
24P0042
004-381-030
FLASH DISK
SLFLD25-8GM1U1 (for 6G)
000-166-792-10
DK0090G88TNO (for 9G)
000-166-822-10
FLASH DISK Board
FW-ATA-2501-1
000-161-500-11
REPEATER Board
24P0080
000-155-924-01
Underwater Acoustic Beacon
DK-120
000-148-648
MAIN Board
24P0069
004-385-490
Terminal Board
24P0077
004-385-510
Junction Box (IF-8530)
Remote Alarm Panel (VR-3016) RAP MAIN Board
24P0075A
004-385-520
RAP PANEL Board
24P0076A
004-385-560
25
5. INTERFACE (IEC 61162-1, IEC 61162-2) 5.1 Data Sentences ALA - Set detail alarm condition 1
2
3
4
5
6
7
8
$xxALA, hhmmss.ss, aa, aa, xx, xxx, A, A, c—c *hh 1) Event time Event time of alarm condition change includeing acknowledgement state change. If this is not available, this shouled be a null field. 2) System Indicator of original alarm source Indicator characters as system of alarm source. This field is two fixed characters, see AnnexD. 3) Sub system equipment indicator of original alarm source Indicator characters as sub-system of alarm source. This field is two fixed characters, see AnnexD. For group alarms or if no sub-system can be identified, this should be a null field. 4) Instance number of equipment/unit/item Instance number identifying the equipment, unit or item. This field is two fixed numeric characters. 5) Type of alarm Type of alarm. This field is three fixed numeric characters as defined in AnnexD, Table D.1. Codes 900 to 999 are user definable. 6) Alarm condition This field is a single character specified by the following. N = normal state; H = alarm state (threshold exceeded); J = alarm state (extreme threshold exceeded); L = alarm state (low threshold exceeded, i.e. not reached); K = ararm state (extreme low threshold exceeded, i.e. not reached); X = other. 7) Alarm's acknowledged state This field is a single character specified by the following: A = acknowledged; V = not acknowledged; B = broadcast (acknowledged not applicable); H = habour mode; O = override. 8) Alarm's description text Additional and optional descriptive text/alarm detail condition tag. Maximum number of characters will be limited by maximum sentence length and length of other fields.
ALR - Set alarm status Updated the text label of the alarm identification field to be the same as that field in the ACK sentence. $--ALR,hhmmss.ss,xxx,A,A,c--c*hh 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
26
DOR - Door status indication This sentence indicates the status of watertight doors, fire doors and other hull openings / doors. $xxDOR, A, hhmmss.ss, aa, cc, xxx, xxx, a,a, c—c *hh 1
2
3
4
5
6 78 9
1) Message type S: Status for section: the number of faulty and/or open doors reported in the division specified in field 4 and 5. The section may be a whole section (one or both of the division indicator fields are null) or a sub-section. The status S is normally transmitted at regular intervals. Examples of use are given in Annex E. E: Status for single door. (E may be used to indicate an event). F: Fault in system: Division indicator fields defines the section when provided. 2) Event time Time when this status/message was valid. This may be a null field. 3) Type of door monitoring system The field is two fixed characters, see table below. 4) First division indicator First division indicator where door is located. This field is two characters, see table below. 5) Second division indicator Second division indicator where the door is located. This field is three numeric characters, see table below. 6) Door number or door open count This field is three fixed numeric characters. When the message type field is E this field identifies the door. When message type field is S this field contains the numbeer of doors that are open or faulty. When the message type field is F this field is null. 7) Door status When the message type field is S or F this field shold be a null field. When the message type field is E, this field is specified by the following: O = Open C = Close S = Secured F = Free status (for watertight door) X = Fault (door status unknown) 8) Water tight door switch setting This field includes a single character specified by the following: O = Harbour mode (allowed open) C = Sea mode (ordered closed) This may be a null field 9) Message description text Descriptive text/door tag. If a door allocation identifier is string type, it is possible to use this field instead of the above door allocation fields. The maximum number of characters will be limited by the maximum sentence length and the length of other fields.
Type of door monitoring system ID System category WT Watertight door WS Semi-watertight door (splash-tight) FD Fire door
HD
Hull (shell) door
OT
Other
First division indicator
Second division indicator
Number of watertight bulkhead / frame number
Deck number
Number / letter of zone. This can also be identifier for control and monitoring main system
Deck number or control system loop number or other control system division indicator as is appropriate for system Deck number
Door indication number / frame number As above
As above
27
DPT - Depth IMO Resolution A.224 (VII). 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*hh Checksum Offset from transducer, in meters = distance from transducer to water-line Water depth relative to the transducer, in meters
DTM - Datum reference (to be further developed) Local geodetic datum to which a position location is referenced. 1 2 3 4 5 6 7 8 $--DTM, ccc, a,x.x,a,x.x,a,x.x,ccc*hh 1) Local datum WGS84 = W84 WGS72 = W72 SGS72 = S72 PE90 = P90 Under defined = 999 IHO datum code (see Note 1.) Three character alpha code for local datum. If not one of the listed earth-centered datums, or 999 for user difined 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. 2) Local datum subdivision code 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. 3) Lat offset, min, N/S (see Note2.) 4) Lon offset, min E/W (see Note2.) 5) Attitude offset, m (see Note2.) 6) Reference datum WGS84 = W84 WGS72 = W72 SGS85 = S85 PE90 = P90 Note1: Users should be aware that chart transformations based on IHO S60 parameters may result in significant positional errors when applied to chart data. Note2: Lattitude and longitude offsets are positive numbers, the altitude offset may be negative. Off sets change with position: position in the local datum is offset from the position in the reference datum in the directions indicated:
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.
28
ETL - Engine telegraph operation status The ETL sentence indicates engine telegraph position including operating location and sub-telegraph indicator. $xxETL, hhmmss.ss, a, xx, xx, a, x, *hh 0
1
2
3 4 5 6
7
0) Header 1) Event Time 2) Indicator of command O = Order A = Answerback 3) Position indication of engine telepgraph 00 = Stop engine 01 = [AH] Dead Slow 02 = [AH] Slow 03 = [AH] Half 04 = Full 05 = [AH] Nav. Full 11 = [AS] Dead Slow 12 = [AS] Slow 13 = [AS] Half 14 = [AS] Fulll 15 = [AS] Crash Astern 4) Position indication of sub telegraph 20 = S/B (Stand-by engine) 30 = F/A (Full away – Navigation full) 40 = F/E (Finish with engine) 5) Operating location indicator B = Bridge P = Port wing 1 S = Starboard wing 1 C = Engine control room E = Engine side 6) Number of engine or propeller shaft 0 = single or on centre-line Odd = starboard Even = port 7) Checksum
29
FIR - Fire detection 1
2
3
4
5
6
7
8
9
$xxFIR, A, hhmmss.ss, aa, cc, xxx, xxx, a, a, c--c, *hh 1) Message type S: Status for section: the number of faulty and activated condition reported as number in field 6.The section may be a whole section (one or both of the division indicator fields are null) or a sub-section. The status S is normally transmitted at regular intervals. Examples of use are given in Annex E. E: Status for each detecter. (E may be used to indicate an event.) F: Fault in system: Division indicator fields defines the section when provided. D: Disabled: Detector is manually or automatically disabled from giving fire alarms. 2) Event time Time of condition change or acknowledgement. This may be a null field. 3) Type of fire detection system The field is two fixed characters, see table below. 4) First division indicator First division indicator where detector is located. This field is two characters, see table below. 5) Second division indecator Second division indicator where the detector is located. This field is three numeric characters, see table below. 6) Fire ditector number or activation detection count This field is three fixed numeric characters. When the message type field is E, this field identifies the detector. When message type field is S this field contains the number of detectors activated. When the message type field is F or D this field is null. 7) Condition When the message type field is S this field should be a null field. When the message type field is E, F or D this field includes a single character specified by the following: A = Activation V = Non-activation X = Fault (state unknown) 8) Alarm's acknowledgement state When the message field type is E or F this field includes a single character specified by the following: A = acknowledged V = not acknowledged When the message field type is S or D this shold be a null field. 9) Message description text Descriptive text/sensor location tag. If a sensor location identifier is string type, it is possible to use this field instead of above sensor allocation fields. Maximum number of characters will be limited by the maximum sentence length and the length of other fields.
Type of door monitoring system First division indicator Second division indicator ID System category Number / letter of zone. Loop number. This can be FD Generic fire detector, can be This can also be a control also be another control and any of the ones below. and monitoring system monitoring sub-system FH Heat type detector main unit identifier, for identifier, for example FS Smoke type detector example fire central sub-central. FD Smoke and heat detector number / letter. FM Manual call point As above As above GD Any gas detector GO Oxygen gas detector GS Hydrogen sulphide gas detector GH Hydro-carbon gas detector SF Sprinkler flow switch As above As above SV Sprinkler manual valve release CO CO2 manual release As above As above OT Other As above As above Note: For units controlled from the fire system (typically all FD, FH, FS, FD and FM), the normal division indicators should be fire zone and loop number.
30
GEN - Generic status information This sentence provides a means of transmitting multi-sensor generic status information from any source, in a format that can be registered by the VDR. The sentence is designed for efficient use of the bandwidth and must be accompanied with a description of how to interpret the information. Each sentence holds a base address for all status groups. Each group is assigned a 16-bit address. Up to eight contiguous groups with increasing address may be transmitted in a single sentence. Data is blocked in 16-bit groups. Unused bits shall be assigned a fixed value to simplify data compression. A separate configuration with interpretation of bit equal to "1" and "0" for all sentence groups and bit positions that are used, must be provided as this information is not included in the sentence. It is the responsibility of the talker to provide this information. $xxGEN, hhhh, hhmmss.ss, hhhh[,hhhh], *hh 0
1
2
3
4
0) Header 1) Address of first group in sentence Address of first group in GEN sentence. Address is represented in hexadecimal format in range 0x0000 through 0xFFFF. The 16-bit address is formatted as fixed 4-character HEX field. 2) Time stamp Time when status was valid. 3) Packed generic status group The packed generic status group is represented as a 6-bit value. The 16-bit value is formatted as fixed 4-character HEX field. 4) Optional repeat of field 3 Optional repeated packed generic status field. Each repeat increases the status address by one. Up to seven repetitions yielding a total of 128 status bits per sentence is possible. hh = Check sum
31
GNS - GNSS fix data Fix data for single or combined satellite navigation systems (GNSS). 1 3 4 5 6 7 8 9 10 11 3 2 2 $--GNS,hhmmss.ss,llll.lll,a,yyyyy.yyy,a,c--c,xx,x.x,x.x,x.x,x.x,x.x,a*hh
1) UTC of position 2) Latitude, N/S 3) Longitude, E/W 4) Mode indicator Mode indicator. A variable length valid character field type with the first three characters currently defined. The first character indicates the use of GPS satellites, the second character indicates the use of GLONASS satellites and the third indicate the use of Galileo satellites. If another satellite system is added to the standard, the mode indicator will be extended to four characters, new satellite systems should always be added on the right, so the order of characters in the mode indicator is: GPS, GLONASS, Galileo, other satellite systems in the future. The characters should take one of the following values. A = Autonomous. Satellite system used in non-differential mode in position fix. D = Differential. Satellite system used in differential mode in position fix E = Estimated (dead reckoning) mode F = Float RTK. Satellite system used in real time kinematic mode with floating integers M = Manual input mode N = No fix. Satellite system not used in position fix, or fix not valid 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. P is also used for satellite system used in multi-frequency, SBAS or Precise Point Positioning (PPP) mode. R = Real Time Kinematic. Satellite system used in RTK mode with fixed integers S = Simulator mode 5) Total number of satllite in use,00-99 6) HDOP HDOP calculated using all the satellites (GPS, GLONASS, Galileo and any future satellites) used in computing the solution reported in each GNS sentence. 7) Antenna altitude, m, re: mean-sea-level(geoid) 8) Geoidal separation Geodial Separation: the difference between the earth ellipsoid surface and mean-sea-level (geoid) surface defined by the reference datum used in the position solution, "-" = mean-sea-level surface below ellipsoid. The reference datum may be specified in the DTM sentence. 9) Age of differential data (see Note.) 10) Differential reference station ID (see Note.) 11) Navigation status indicator The navigational status indicator is according to IEC 61108 requirements on ‘Navigational (or Failure) warnings and status indications’. This field shoule not be a NULL field and the character should take one of the following values: S = Safe When the estimated positoning accuracy (95 % confidence) is within the selected accuracy level corresponding to the actual navigation mode, and integrity is available and within the requirements for the actual navigation mode, and a new valid position has been calculated within 1 s for a conventional craft and 0.5 s for a high spee craft. C = Caution When integrity is not available U = Unsafe When the estimated positioning accuracy (95 % confidence) is less than the selected accuracy level corresponding to the actual navigation mode, and/or integrity is available but exceeds the requirements for the actual navigation mode, and/or a new valid position has not been calculated within 1 s for a conventional craft and 0.5 s for a high speed craft. V = Navigational status not valid, equipment is not providing navigational status indication.
Note : Age of differential data and Differential Reference Station ID: a) When the talker is GN and more than one of the satellite systems are used in differential mode, then the “Age of differential data” and “Differential reference station ID”
32
fields should be provided in following GNS sentences with talker Ids of GP, GL, etc. These following GNS messages should have the latitude, N-S, longitude, E/W, altitude, geoidal separation, mode, and HDOP fields null. This indicates to the listener that the field is supporting a previous $GNGNS sentences to denote the number of satellites used from that satellite system. Example: A combined GPS/GLONASS receiver using only GPS differential corrections has the following GNS sentence sent. $GNGNS,122310.2,3722.425671,N,12258.856215,W,DA,14,0.9,1005.543,6.5,5.2,23*59
Example: A combined GPS/GLONASS receiver using both GPS differential corrections and GLONASS differential corrections may have the following three GNS sentences sent in a group. $GNGNS,122310.2,3722.425671,N,12258.856215,W,DD,14,0.9,1005.543,6.5,, *74 $GPGNS,122310.2,,,,,,7,,,,5.2,23*4D $GLGNS,122310.2,,,,,,7,,,,3.0,23*55
The Differential Reference station ID may be the same or different for the different for the different satellite systems. b) Age of Differential Data For GPS Differential Data: This value is the average age of the most recent differential corrections in use. When only RTCM SC104 Type1 corrections are use, the age is that of the most recent Type1 corrections. When RTCM SC104 Type9 corrections are used solely, or in combination with Type1 corrections, the age is the average of the most recent corrections for the satellites used. Null field when Differential GPS is not used For GLONASS Differential Data: This value is the average age of the most recent differential corrections in use. When only RTCM Type31 corrections are used, the age is that of the most recent Type31 correction. When RTCM SC104 Type34 corrections are used solely, or in combination with Type31 corrections, the age is the average of the most recent corrections for the satellites used. Null field when differential GLONASS is not used. For Galileo Differential Data: This value is the average age of the most recent differential corrections in use. When only RTCM SC104 Type41 corrections are used, the age is that of the most recent Type41 corrections. When RTCM SC104 Type42 corrections are used solely, or in combination with Type41 corrections, the age is the average of the most recent corrections for the satellite used. Null field when differential Galileo is not used.
33
HDG - Heading Magnetic $--HDG,x.x,x.x,a,x.x,a*hh | | | | | | | | | | | +--------- 4 | | | +--+----------- 3 | +----+----------------- 2 +------------------------ 1 1. Magnetic sensor heading, degrees 2. Magnetic deviation, degrees E/W 3. Magnetic variation, degrees E/W 4. Checksum
HDT - Heading True $--HDT, x.x, T*hh $--HDT,x.x,T*hh | | | | | +--------- 2 +----+----------- 1 1. Heading, degrees true 2. Checksum
HSS - Hull stress surveillance systems 0
1
2
3
4
$xxHSS, c--c, x.x, A, *hh
0: Header 1: Measurement point ID 2: Measurement value 3: Data status, A = data valid, V = data invalid 4: Check-sum Note: This must be verified by Ship Classification. VDR is required to log such data if HSS is fitted on ship.
34
HTC - Heading/Track control command $--HTC,A,x.x,a,a,a,x.x,x.x,x.x,x.x,x.x,x.x,x.x,a*hh | | | | | | | | | | | | | | | | | | | | | | | | | | | +--- 14 | | | | | | | | | | | | +----- 13 | | | | | | | | | | | +-------- 12 | | | | | | | | | | +------------ 11 | | | | | | | | | +---------------- 10 | | | | | | | | +-------------------- 9 | | | | | | | +------------------------ 8 | | | | | | +---------------------------- 7 | | | | | +-------------------------------- 6 | | | | +----------------------------------- 5 | | | +------------------------------------- 4 | | +--------------------------------------- 3 | +------------------------------------------ 2 +--------------------------------------------- 1
1. Override, A = in use, V = not in use 2. Commanded rudder angle, degrees 3. Commanded rudder direction, L/R = port/starboard 4. Selected steering mode 5. Turn mode R = radius controlled T = turn rate controlled N = turn is not controlled 6. Commanded rudder limit, degrees(unsigned) 7. Commanded off-heading limit, degrees(unsigned) 8. Commanded radius of turn for heading changes, n.miles 9. Commanded rate of turn to heading changes, deg/min 10. Commanded heading-to-steer, degrees 11. Commanded off-track limit, n.miles(unsigned) 12. Commanded track, degrees 13. Heading reference in use, T/M 14. Checksum
35
HTD - Heading/Track control data $--HTD,A,x.x,a,a,a,x.x,x.x,x.x,x.x,x.x,x.x,x.x,a,A,A,A,x.x*hh | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +--- 18 | | | | | | | | | | | | | | | | +------ 17 | | | | | | | | | | | | | | | +--------- 16 | | | | | | | | | | | | | | +----------- 15 | | | | | | | | | | | | | +------------- 14 | | | | | | | | | | | | +--------------- 13 | | | | | | | | | | | +------------------ 12 | | | | | | | | | | +---------------------- 11 | | | | | | | | | +-------------------------- 10 | | | | | | | | +------------------------------ 9 | | | | | | | +---------------------------------- 8 | | | | | | +-------------------------------------- 7 | | | | | +------------------------------------------ 6 | | | | +--------------------------------------------- 5 | | | +----------------------------------------------- 4 | | +------------------------------------------------- 3 | +---------------------------------------------------- 2 +------------------------------------------------------- 1
1. Override, A = in use, V = not in use 2. Commanded rudder angle, degrees 3. Commanded rudder direction, L/R = port/starboard 4. Selected steering mode 5. Turn mode R = radius controlled T = turn rate controlled N = turn is not controlled 6. Commanded rudder limit, degrees(unsigned) 7. Commanded off-heading limit, degrees(unsigned) 8. Commanded radius of turn for heading changes, n.miles 9. Commanded rate of turn to heading changes, deg/min 10. Commanded heading-to-steer, degrees 11. Commanded off-track limit, n.miles(unsigned) 12. Commanded track, degrees 13. Heading reference in use, T/M 14. Rudder status A = within limits, V = limit reached or exceeded 15. Off-heading status A = within limits, V = limit reached or exceeded 16. Off-track status A = within limits, V = limit reached or exceeded 17. Vessel heading, degrees 18. Checksum
36
MWV - Wind speed and angle When the reference field is set to relative, data is provided giving the wind angle in relation to the vessel’s heading and wind speed, both relative to the moving vessel. When the reference field is set to true, data is provided giving the wind angle relative to the vessel’s heading and wind speed, both with reference to the moving water. True wind is the vector sum of the relative apparent wind vector and the vessel’s velocity vector along the heading line of the vessel. If represents the wind at the vessel if it were stationary relative to the water and heading in the same direction. $--MWV,x.x,a,x.x,a,A*hh | | | | | | | | | | | +--------- 6 | | | | +----------- 5 | | | +------------- 4 | | +---------------- 3 | +------------------- 2 +---------------------- 1 1. Wind angle, 0 to 359 (degrees) 2. Reference, R=relative, T=true 3. Wind speed 4. Wind speed units, K/M/N 5. Status, A=data valid, V=data invalid 6. Checksum
PRC - Propulsion remote control status This sentence indicates the engine control status (engine order) on a M/E remote control system. This provides the detail data not available from the engine telegraph. $xxPRC, x.x, A, x.x, A, x.x, A, x, *hh 0
1
2 3
4
5 6 7
8
0) Header 1) Lever demand position -100 - 0 - 100% from "full astern" (crash astern) to "full ahead" (navigation full) "stop engine" 2) Data status A = data valid V = data invalid 3) RPM demand 4) Data status R = relative (%): 0-100% from zero to maximum rpm T = true (rpm): "-"Astern V = data invalid 5) Pitch demand 6) Data status R = relative (%): -100 - 0 - 100% from "full astern" (crash astern) to "full ahead" (navigation full) "stop engine" T = true (degree): "-"Astern V = data invalid 7) Number egine or propeller shaft 0 = single or on centre-line Odd = starboard Even = port 8) Checksum
37
RPM - Revolutions Shaft or engine revolution rate and propeller pitch. $--RPM, a, x, x.x, x.x, A*hh Status: A = data valid Propeller pitch, % of maximum, “-” = astern Speed, revolutions/min, “-” = counter-clockwise Engine of shaft number, numbered from center-line Odd = starboard, even = port, 0 = single or no center-line Source, shaft/engine S/E
RSA - Rudder sensor angle $--RSA, x.x, A, x.x, A*hh Port rudder sensor (see note), Status: A = data valid Starboard (or single) rudder sensor (see note), Status: A = data valid
NOTE - Relative measurement of rudder angle without units, “-” = turn to port. Sensor output is proportional to rudder angle but not necessarily 1 : 1. TRC - Thruster control data This sentence provides the control data for thruster devices $xxTRC, x, x.x, A, x.x, A, x.x, *hh 0
1 2 3
4
5 6
7
0) Header 1) Number of thrusters Odd = Bow thruster Even = Stern thruster 2) RPM demand 3) Data status R = relative (%): 0-100% from zero to maximum rpm T = true (deg) V = data invalid 4) Pitch demand value "-" port 5) Data status R = relative (%) T = True (deg) V = Data invalid 6) Azimuth demand Direction of thrust in degrees (0 deg - 360 deg) for thrusters capable of rotating direction of thrust 7) Checksum
38
TRD - Thruster response data This sentence provides the response data for thruster devices. $xxTRD, x, x.x, A, x.x, A, x.x, *hh 0
1 2 3
4
5 6
7
0) Header 1) Number of thrusters Odd = Bow thruster Even = Stern thruster 2) RPM demand 3) Data status R = relative (%): 0-100% from zero to maximum rpm T = true (deg) V = data invalid 4) Pitch response value "-" port 5) Data status R = relative (%) T = True (deg) V = Data invalid 6) Azimuth demand Direction of thrust in degrees (0 deg - 360 deg) for thrusters capable of rotating direction of thrust 7) Checksum
VBW - Dual ground/water speed: This sentence to be expanded as shown below: $--VBW,x.x,x.x,A,x.x,x.x,A,x.x,A,x.x,A*hh | | | | | | | | | | | | | | | | | | | | | +--- 11 | | | | | | | | | +----- 10 | | | | | | | | +-------- 9 | | | | | | | +----------- 8 | | | | | | +-------------- 7 | | | | | +----------------- 6 | | | | +-------------------- 5 | | | +------------------------ 4 | | +--------------------------- 3 | +------------------------------ 2 +---------------------------------- 1 1. Longitudial water speed, knots 2. Transverse water speed, knots 3. Status: water speed, A=data valid V=data invalid 4. Longitudial ground speed, knots 5. Transverse ground speed, knots 6. Status: ground speed, A=data valid V=data invalid 7. Stern transverse water speed, knots 8. Status: stern water speed, A=data valid V=data invalid 9. Stern transverse ground speed, knots 10. Status: stern ground speed, A=data valid V=data invalid 11. Checksum
39
VDM - UAIS VHF Data-link Message (IEC 61162-2, for AIS) !--VDM,x,x,x,x,s--s,x*hh | || | | | | | | | | | | +--- 7 | | | | | +----- 6 | | | | +-------- 5 | | | +------------ 4 | | +-------------- 3 | +---------------- 2 +------------------ 1 1. Total number of sentences needed to transfer the message, 1 to 9 2. Message sentence number, 1 to 9 3. Sequential message identifier, 0 to 9 4. AIS channel Number 5. Encapsulated ITU-R M.1371 radio message 6. Number of fill-bits, 0 to 5 7. Checksum
VDO - UAIS VHF Data-link Own-vessel report (IEC 61162-2, for AIS) !--VDO,x,x,x,x,s--s,x*hh | | || | | | | | | | | | +--- 7 | | | | | +----- 6 | | | | +-------- 5 | | | +------------ 4 | | +-------------- 3 | +---------------- 2 +------------------ 1 1. Total number of sentences needed to transfer the message, 1 to 9 2. Message sentence number, 1 to 9 3. Sequential message identifier, 0 to 9 4. AIS channel Number 5. Encapsulated ITU-R M.1371 radio message 6. Number of fill-bits, 0 to 5 7. Checksum
40
WAT - Water level detection This sentence provides detection status of water leakage and bilge water level, with monitoring location data. Malfunction alarm of the water level detector should be included in the “ALA” sentence. $xxWAT, A, hhmmss.ss, aa, aa, xx, xxx, A, c—c, *hh 0
123456789
0) Header 1) Message type S: Status for section: Number of faulty and activated condition reported as number in field 4. The section may be a whole section (one or both of the division indicators are empty) or a sub-section. (If S is used then it shall be transmitted at regular intervals) E: Status for each water level detector. (E may be used to indicate an event.) F: Fault in system: If limited to one section, indicated by division indicator fields, if not, division indicators [empty]. (F may be used to indicate an event). 2) Time stamp Time when this status/message was valid. 3) System indicator of alarm source Indicator characters showing system detecting water level. The field is two characters. 4) Location (1) Indicator characters showing detection location. The field is two characters. 5) Location (2) Indicator characters showing detection location. The field is two characters. 6) Number of detection point or detection point number Number showing high-water-level detecting point or the number of the water leakage detection point. This field is three fixed numeric characters. 7) Alarm condition This field is a single character specified by the following: N = normal state H = alarm state (threshold exceeded) J = alarm state (extreme threshold exceeded) L = alarm state (Low threshold exceeded i.e. not reached) K = alarm state(extreme low threshold exceeded i.e. not reached) X = Fault (state unknown) When S status indicated in 2nd field, this field is ignored 8) Descriptive text Additional and optional descriptive text/level detector tag. 9) Checksum
41
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 of 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 its own data fields on before retransmitting the sentence. $--XDR, a, x.x, a, c--c, ........ a, x.x, a, c--c*hh 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)
NOTES 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. ZDA - Time and date $--ZDA,hhmmss.ss,xx,xx,xxxx,xx,xx*hh | | | | | | | | | | | | | +--------- 7 | | | | | +----------- 6 | | | | +-------------- 5 | | | +------------------ 4 | | +---------------------- 3 | +------------------------- 2 +--------------------------------- 1 1. UTC 2. Day, 01 to 31(UTC) 3. Month, 01 to 12(UTC) 4. Year(UTC) 5. Local zone hours, 00h to +-13h 6. Local zone minutes, 00 to +59 as local hours 7. Checksum
NOTE - Zone description if the number of whole hours added to local time to obtain GMT. Zone description is negative for east longitudes.
42
5.2 Interface Circuits 5.2.1 IEC 61162-1 Data Collecting Unit
A
B
Junction Box
A A
B
43
5.2.2 IEC 61162-2 Data Collecting Unit
G
B
A
Junction Box
B
A
G
44
APPENDIX: PLAYING BACK RECORDED DATA IMO Circulator SN Circ, 246 recommends that all VDR and S-VDR systems installed on or after 1 July 2006 be supplied with an accessible means for extracting the stored data from the VDR or S-VDR to a laptop computer. Manufacturers are required to provide software for extracting data, instructions for extracting data and cables for connection between recording device and computer. FURUNO provides the following:
• LIVE PLAYER V4 (instructions) • LIVE PLAYER V4 CD (software) • Cables: Firewire and LAN Refer to the Operator’s Manual for the Live Player V4 for how to playback recorded data.
45
FURUNO
VR-3000/VR-3000S
SPECIFICATIONS OF VOYAGE DATA RECORDER VR-3000/ SIMPLIFIED VOYAGE DATA RECORDING VR-3000S The Voyager Data Recorder (VDR) is a recording system required on certain categories of ships from 1st July 2002 by the revised SOLAS Chapter V. The Simplified Voyager Data Recorder (S-VDR) is a recording system required by IMO MSC.163(78). VR-3000 fully complies with the IMO Resolution A. 861 (20) and IEC 61996 testing standard. VR-3000S fully complies with the IMO MSC.163(78) and IEC/PAS 61996 testing standard.
1
GENERAL
1.1
Recording Period
DRU: 12 hours, Backup HDD: approx. 48 hours
1.2
Battery Backup
More than two hours after loss of ship’s mains
2
DATA COLLECTING UNIT (DCU): VR-3010
2.1
CPU
Intel Pentium M 1.6GHz
2.2
Memory
512 Mbyte
2.3
Input Signal Input signal Bridge audio VHF audio Serial data IEC 61162-2 Serial data IEC 61162-1 Radar image
VR-3000 6ch 2ch 4ch 12ch Std. 1ch (+3ch*) Std.16ch, Max. 48ch*
VR-3000S 6ch 2ch 2ch(+2ch*) 6ch(+6ch*) Max. 4ch*
Remarks 775mV AC/600 ohms 775mV AC/600 ohms
Max. 48ch*
Max.192ch*
Remote ACK signal
Std. 64ch, Max. 192ch* 1ch
-10 - +10V, 0 - +10V, 4 - 20mA Contact signal, Voltage signal (10 -32V)
1ch
Output signal Ethernet 100Base-T VDR System Fail signal Local ACK signal IEEE1394a
VR-3000 2ch 1ch 1ch 1ch
VR-3000S 2ch 1ch 1ch 1ch
Analog signal
Digital signal
RGBHV signal
Remarks
For data extraction * : Option
3
DATA RECORDING UNIT (DRU): VR-5020
3.1
Chassis
Protective capsule
3.2
Memory Capacity
6 GB or 9 GB
SP - 1
E4437S01D-M
FURUNO
VR-3000/VR-3000S
3.3
Shock Resistance
50G x 11 ms
3.4
Penetration Resistance
100 m diameter pin w/250 kg weight, dropped from 3 m height
3.5
Fire Resistance
1100°C for 1 hour, 260°C for 10 hours
3.6
Submersible
6000 m (60 Mpa)
3.7
Acoustic Beacon
Replaced every 6 years, max. depth 6000 m, 30 days 37.5 kHz 10 ms pulse transmission
4
MICROPHONE: VR-5011/VR-3012W
4.1
AGC Amplifier Output
775 mV AC/600 ohm
4.2
Frequency Response
Within 6 dB at 150 Hz to 6 kHz
4.3
Audio Coverage
Cylindrical area of approx. 10 m in diameter Distance: approx. 2 m
4.4
On-board Beeper
5
POWER SUPPLY
1s in 12 hours period (built in)
100-230 VAC, 1 phase, 50/60 Hz, 2.0-0.9A 24 VDC, 7.5A Max
6 6.1
6.2 6.3
6.4
7 7.1 7.2 7.3 7.4 7.5
ENVIRONMENTAL CONDITION Ambient Temperature (IEC 60945) Data collecting unit (VR-3010) -15°C to +55°C Data recording unit (VR-5020) -25°C to +55°C Waterproof Microphone (VR-3012W) -25°C to +55°C Others -15°C to +55°C Relative Humidity 95% at 40°C Waterproofing (IEC 60952) Data collecting unit (VR-3010) IP20 Data recording unit (VR-5020) IPX7 Junction box (IF-8530) IP20 Remote alarm panel (VR-3016) IP20 Microphone (VR-5011) IP20 Microphone (VR-3012W) IPX6 Vibration (IEC 60945) 2 - 5 Hz and up to 13.2 Hz with an excursion of ±1 mm ±10% (7 m/s2 maximum acceleration at 13.2 Hz) 13.2 - 100 Hz with a constant maximum acceleration of 7 m/s2 COATING COLOR Data Collecting Unit (VR-3010) Data Recording Unit (VR-5020) Junction Box (IF-8530) Remote Alarm Panel (VR-3016) Microphone (VR-5011/VR-3012W)
2.5GY5/1.5 Fluorescent orange 2.5GY5/1.5 N3.0 2.5GY5/1.5
SP - 2
E4437S01D-M
FURUNO ELECTRIC CO., LTD. 9-52 Ashihara-Cho, Nishinomiya City, 662-8580, Hyogo, Japan Tel: +81 798-65-2111 Fax: +81 798-65-4200
Pub NO. DOC-897
Declaration of conformity We
FURUNO ELECTRIC CO., LTD.
0735
---------------------------------------------------------------------------------------------------------------------(Manufacturer)
9-52 Ashihara-Cho, Nishinomiya City, 662-8580, Hyogo, Japan
---------------------------------------------------------------------------------------------------------------------(Address)
hereby declare under our sole responsibility that the product Voyage Data Recorder (VDR) Type VR-3000
---------------------------------------------------------------------------------------------------------------------(Model names, type numbers)
to which this declaration relates conforms to the following standard(s) or normative document(s) IMO Resolution A.861(20) IMO Resolution A.694(17)
EN 61996: 2001 (IEC 61996 First edition: 2000-07) EN 60945 (IEC 60945: Fourth edition: 2002-08) EN 61162 (IEC 61162-1 Second edition: 2000-07)
---------------------------------------------------------------------------------------------------------------------(title and/or number and date of issue of the standard(s) or other normative document(s))
For assessment, see • EC type examination (Module B) certificate BSH/4612/4290315/06 of 02 June 2006 issued b y Federal Maritime and Hydrographic Agency (BSH), The Federal Republic of Germany • EC quality system¥(Module D) certificate No. BSH/4613/02202/0339/06 of 04 July 2006 and its Annex of 04 July 2006 issued by Federal Maritime and Hydrographic Agency (BSH), The Federal Republic of Germany • Test Report No. BSH/4612/129 0192/05 of 27 April 2006 prepared by Federal Maritime and Hydrographic Agency (BSH), The Federal Republic of Germany • Test report 115482 of 02 May 2003 prepared by Danish Technological Institute, Denmark • Test reports FLI 12-06-001 of 24 February 2006, FLI 12-06-026 of 25 May 2006 and FLI 1206-027 of 31 May 2006 issued by Furuno Labotech International Co., Ltd, Japan This declaration is issued according to the provisions of European Council Directive 96/98/EC on marine equipment modified by Commission Directive 2002/75/EC.
On behalf of Furuno Electric Co., Ltd.
Hiroaki Komatsu Manager, Nishinomiya City, Japan International Rules and Regulations July 11, 2006 ----------------------------------------------------- ---------------------------------------------------------------(Place and date of issue)
(name and signature or equivalent marking of authorized person)
