Quantcast
Viewing all 8621 articles
Browse latest View live

Troubleshooting hsb2 communications

Raymarine's hsb2 Pathfinder Series Radar, Chartplotter, and Fishfinder The following troubleshooting steps should be undertaken when troubleshooting hsb2 communications.

- Verify that all Pathfinder Series Displays are equipped with hsb2 communications circuitry

- Verify that the hsb² network is properly terminated (i.e. 2 hsb2 inline termination plugs only and that these hsb2 inline termination plugs have been installed within the two displays forming the end of the hsb2 daisy chain (See diagram below). If a DSM30 or DSM300 fishfinder sounder module has been installed, then the DSM should be installed at one end of the hsb2 daisy chain. The DSM250 requires a hsb2 Inline Termination Plug, while the DSM30 and DSM300 are internally terminated. If the display's hsb2 port is gray, then no hsb2 inline termination plug has been installed in the display's port. If the display's hsb2 port is black, then you are looking are the male end of a hsb2 inline termination plug.

Image may be NSFW.
Clik here to view.
[Image: attachment.php?aid=87]


- Verify that the hsb2 inline termination plug has been removed from any display into which a hsb2 Y-Cable has been inserted (see diagram above)

- Verify that all hsb cables are securely seated and have proper strain relief

- Verify that there are no damaged hsb cables by visually inspecting and performing continuity tests

- Verify that the hsb cable(s) have not been subjected to excessively small radius bends (<6 inch diameter). Subjecting these cables to excessively tight bends can permanently damage the cables. Excess cable should be loosely coiled and secured to a bulkhead

- If the system contains more than 2 hsb² nodes, attempt fault isolation to identify the faulty component (i.e. connect 2 nodes at time to verify communications between the two nodes)

- Verify that no more than 2 C-Map SW+ regions are being served on the hsb² network.

- Perform resistance tests and continuity tests of the hsb² components:
-- Terminators (uninstalled from hsb² port): 120 +/- 2 ohms across the HSVB_POS & HSVB_NEG pins (see diagram above)
--Pathfinders (power off): 2200 +/- 50 ohms across the HSVB_POS & HSVB_NEG pins
--Terminators (installed): values should drop by approximately 5 ohms from the value measured prior to installation
--For multiple display systems, with the system's hsb² displays reconnected to the hsb² network and the Pathfinder PC disconnected from the hsb² network, measure the resistance of the network through the hsb² cable:

Displays.......... Resistance

1____________114

2____________108

3____________103

4____________99

5____________94

6____________90

7____________87

8____________84

- For maximum system performance, verify that all Pathfinder Series Displays have v4.11 software installed within them ... please note that Raymarine's Product Repair Center can no longer update the software within these hsb2 Pathfinder Series Displays

Unfortunately, should one or more of the displays have failed hsb2 communications circuitry, then it must be replaced, as Raymarine's Product Repair Center can no longer service these displays.

CRAFAQ#

Image may be NSFW.
Clik here to view.
.jpg
  Clipboard02.jpg (Size: 159.28 KB / Downloads: 4)

Replacing hsb/hsb2/SL Pathfinder Series Display(s) with an a/c/e/eS/gS-Series MFD(s)

If replacing a hsb/hsb2 Pathifnder Series Display, then all hsb/hsb2 Pathfinder Series Displays within the system must be replaced to permit the displays to share radar imagery, fishfinder imagery, cartography, satellite weather, IP camera video, etc..

POWER: The currently installed Power/NMEA 0183 Input Cable will need to be replaced with the cable supplied with the a/c/e/eS/gS-Series MFD.

ETHERNET: Should more than one Raymarine product featuring an Ethernet network (RayNet/SeaTalkHS) interface (a/c/e/eS/gS-Series MFDS, CPxxx Sounder Modules, Quantum/Digital/HD Digital/SuperHD Digital Radomes and Open Array Radar Scanners, Thermal Cameras, CAM200IP, PC w/Voyage Planner software, etc.) be installed onboard, then these devices must be interfaced to a common Ethernet network to fully communicate with one another. Failure to do so will prevent the sharing radar, cartography, fishinder, weather, IP camera video, waypoints, routes, tracks, etc. between the system's MFDs. To view Raymarine Ethernet networking products, click here.

Raymarine's 6" and 7" a/e/eS-Series MFDs feature a single Ethernet network socket permitting them to be interfaced to one other Raymarine product featuring an Ethernet network interface. Raymarine's 9", 12", and 16" a/c/e/eS-Series MFDs feature two Ethernet network sockets permitting them to be interfaced to one other Raymarine product featuring an Ethernet network interface. Raymarine's 9", 12", and 16" gS-Series MFDs feature three Ethernet network (Gigabit and POE) sockets permitting them to be interfaced to one other Raymarine product featuring an Ethernet network interface. Should the MFD(s) not feature sufficient Ethernet network sockets to interface all of the Raymarine products featuring an Ethernet network interface, then it will be necessary to install a HS5 RayNet Network Switch(es) to support interfacing the additional Ethernet devices. As the Ethernet network circuitry of a/c/e/eS-Series MFDs is not operational when these MFDs are switched OFF, many customers opt to connect all of the Raymarine products featuring an Ethernet network interface to a HS5 RayNet Network Switch(es). The latter installation method offers a degree of redundancy to the system as well a some flexibility in choosing which MFD will function as the system's Data Master.

RADAR: Radar scanners featuring analog video interfaces which are compatible with hsb/hsb2/SL Pathfinder Series Radar Displays (ex. RD218, RD424, 2D, and 4D radomes; 5S, 7S, 9S, and 11S open array pedestals) are not compatible with the new a/c/e/eS/gS-Series MFDs. Analog radar scanners are most easily identified by their white radar cables. However, these radar scanners are highly regarded in the recreational marine electronics industry and have value for those seeking to replace or add radar to a system featuring a hsb/hsb2/SL Pathfinder Series Radar Display, C-Series Classic MFD, or E-Series Classic MFD. As such, it is generally recommended the currently installed radar be sold privately (ex. ebay, Craigs List, etc.) where you may well find that it may be sold for a fair portion of their original retail price due to the fact that these radar scanners are no longer manufactured.

In order to use an a/c/e/eS/gS-Series MFD's radar features, the MFD must be interfaced to a Quantum, Digital, or HD Digital Radome or HD/SuperHD Open Array Radar Scanner. The bolt patterns of the Digital or HD Digital Radomes are identical to those of the analog radomes which had been designed for use with the C-Series Classic MFDs. Likewise, bolt patterns of the HD/Super HD Open Array Radar Scanners are identical to those of the analog open array radar scanners which had been designed for use with the C-Series Classic MFDs.

The Digital/HD Digital Radome or HD/SuperHD Open Array Pedestal will be interfaced to the system via Digital Radar Cable. Digital Radar Cable should not be cut. In sailing vessels, it is recommended that a Digital Radar Extension Cable should be chased from the radar scanner’s power / communications interface port to the base of the mast, pole mount or backstay. This will permit the Digital Radar Extension Cable to be quickly and cleanly disconnected from the vessel's wiring should the mast or be removed. The Digital Radar Extension Cable will be connected to an appropriate length of Digital Radar Cable w/RayNet (F) plug. A Digital Radar Extension Cable would not typically be used on a power boat unless mounted on an arch or tower would was intended to be removed. In most power boat installations, the Digital Radar Cable will be plugged directly into the Digital Radome's power / communications interface port.

The Digital Radar Cable will in turn be interfaced to power and to the RayNet port of the a/c/e/eS/gS-Series MFD. Alternatively, the Digital Radar Cable may be interfaced to an A80007 HS5 RayNet Network Switch which will in turn be interfaced to the RayNet port of the a/c/e/eS/gS-Series MFD via an appropriate length of RayNet RayNet (F) to RayNet (F) Cable. The latter method would typically be employed if the MFD lacks sufficient RayNet Network sockets to alone support interfacing all other devices featuring a RayNet/SeaTalkhs/Ethernet interface (ex. other a/c/e/eS/gS-Series MFDs, RMK-9, CP100/CP200/CP300/450C Sounder Module, Digital/HD Digital/SuperHD radar scanners, IP Cameras, thermal camera, Fusion Marine stereos, etc.) and/or when seeking a central hub to interface products.

Should the a/c/e/eS/gS-Series MFD be installed within a binnacle mounted pod, then it is recommended that the Digital Radar Cable terminate below decks where it will be interfaced to power. Terminating the Digital Radar Cable below decks will eliminate the need to run power leads up the binnacle tube(s). Should a network switch be installed onboard, then the Digital Radar Cable will be joined to the network switch. Should a network switch not be installed onboard, then the Digital Radar Cable may then be interfaced to the MFD via a an assembly constructed from an A80160 RayNet (M) to RayNet (M) Cable Joiner and an appropriate length of RayNet RayNet (F) to RayNet (F) Cable. Terminating the Digital Radar Cable below decks will eliminate the need to run power leads up the binnacle tube(s) and has the benefit of offering better environmental protection to cable/wire splices.

Tech Tip: when installing marine electronics in pods mounted to binnacle tubing, it is recommended that cables featuring plugs be chased before chasing cables featuring bare leads. Cables featuring the larger plugs should be chased before chasing cables featuring the smaller plugs. Cables featuring bare leads should be chased last. When chasing a cable featuring bare leads on one end and a plug on the other end, then end of the cable featuring the bare leads should be chased rather than the plug end of the cable. You may also want to consider removing all cables from binnacle tubing before installing new equipment to better facilitate chasing cable.

SEATALK: SeaTalk instruments, autopilot components, GPS sensors, and chartplotters featuring a 1st generation SeaTalk interface which do not additionally feature a SeaTalkng interface (ex. ST40/60 Instrument Displays, ST6001, S2G, Wireless AP Controller, C80 MFD, Raystar 125 GPS Sensor, etc.) should be interfaced to one another, in any order, using standard SeaTalk Cables. SeaTalk Cables can be joined using D244 SeaTalk Junction Blocks, splices, marine grade terminal strips, or R55006 SeaTalk Auxiliary Junction Boxes. SeaTalk Cable is available in 15", 1m, 3m, 5m, and 9m lengths. This method of interfacing is referred to as a SeaTalk bus.

Each SeaTalk to SeaTalkng Converter will support a SeaTalk bus of up to five SeaTalk devices. Should your present SeaTalk bus consist of more than five SeaTalk devices, then it will need to be divided into smaller busses including no more than five SeaTalk devices. Each bus will in turn be connected to the yellow SeaTalk port of a SeaTalk to SeaTalkng Converter. The SeaTalk to SeaTalkng Converters may be interfaced to one another via appropriate length of SeaTalkng Backbone Cable. The SeaTalk bus will need to be branched or extended and connected to the yellow (SeaTalk) port of an E22158 SeaTalk to SeaTalkng Converter Kit which has been upgraded with v1.21 or later SeaTalk to SeaTalkng Converter software.

The Data Master a/c/e/eS/gS-Series MFD will in turn be interfaced to one of the white SeaTalkng spur ports of the SeaTalk to SeaTalkng Converter using an appropriate length of SeaTalkng Spur Cable.

The SeaTalk bus will be to be disconnected from its present power source ... this may well be the red terminal of an autopilot course computer's SeaTalk port. The SeaTalk bus will instead be powered via the SeaTalk to SeaTalkng Converter. The SeaTalkng power cable supplied with the SeaTalk to SeaTalkng Converter Kit will be connected to a 12VDC power circuit and will be interfaced to the other white SeaTalkng spur ports of a SeaTalk to SeaTalkng Converter at the approximate midpoint of the LEN load of the SeaTalkng/NMEA 2000 backbone which is being created.

Finally, the supplied SeaTalkng Termination Plugs will need to be installed in the two blue SeaTalkng backbone ports of the SeaTalk to SeaTalkng Converter(s).

EXTERNAL ALARM: The a/c/e/eS/gS-Series MFDs do not feature alarm switching leads to support sounding an external piezoelectric alarms. Those seeking to monitor alarms in a remote location onboard the vessel (ex. stateroom, etc.) will typically install an a65 MFD at the remote location(s). The advantage of installing a small MFD at that location is that not only will the alarm be sounded at that location, but information will be available at that location regarding the nature of the alarm being sounded.

NMEA 0183: The NMEA 0183 leads of any NMEA 0183 devices which are presently interfaced to the leads of the Pathfinder Series Display's Power/NMEA 0183 Input Cable and NMEA 0183 Output Cable will need to be disconnected from these cable and will instead be spliced to the corresponding leads of the a9x/a12x/c/e/eS/gS-Series MFD's Power/NMEA 0183/Video Input Cable. As the a6x and a7x MFDs do not feature a NMEA 0183 port, should the system not feature a larger a-Series MFD or a c/e/eS/gS-Series MFD, then it will be necessary to instead interface the NMEA 0183 device(s) to a powered and properly terminated SeaTalkng/NMEA 2000 backbone to which the a6x or a7x MFD has been interfaced as a spur. NMEA 0183 to SeaTalkng/NMEA 2000 data bridging devices (ex. Actisense NGW-1-STNG, Actisense NGW-1-AIS, etc.) are available from third parties to support interfacing NMEA 0183 devices to systems featuring a/c/e/eS/gS-Series MFDs.

SEATALKNG/NMEA 2000: Should the hsb/hsb2/SL Pathfinder Series Display be interfaced any SeaTalkng/NMEA 2000 devices, then the Data Master a/c/e/eS/gS-Series MFD may be interfaced to the backbone to which such devices have been interfaced via an appropriate length of SeaTalkng Spur Cable. Should the SeaTalkng/NMEA 2000 backbone be constructed from third party NMEA 2000 networking components, then please note that Raymarine offers SeaTalkng to DeviceNet Male (A06046) and SeaTalkng to DeviceNet Female adapter cables (A06045) as well as Stripped End Spur cables (A06044) to support interfacing Raymarine products to third party NMEA 2000 networking components.

Analog Video Input: Raymarine’s c-Series MFDs, e7/e7D MFDs, and eS-Series MFDs support video input from one analog NTSC/PAL video source. Raymarine’s other e-Series MFDs and gS-Series MFDs support video input from up to two analog NTSC/PAL video sources (second via optional R70003 e-Series Accessory Video Cable). Should a compatible Raymarine or FLIR branded thermal camera need to be interfaced to the system, then it will need to be interfaced to the video input socket of the a/c/e/eS/gS-Series MFD’s Power/NMEA 0183/Video Input Cable. Other analog NTSC/PAL video input devices may be either interfaced to the video input socket of the a/c/e/eS/gS-Series MFD’s Power/NMEA 0183/Video Input Cable or to the video input socket of the R70003 e-Series Accessory Video Cable.

Video Output: The R70003 e-Series Accessory Video Cable may be used to interface a 9” and larger e-Series MFDs to a monitor or TV supporting 720P @ 60Hz. The gS-Series MFDs as well as the 9” and larger eS-Series MFDs feature a HDMI port to permit the MFD to be interfaced to a monitor or TV to repeat the MFD's screen image.

FISHFINDING FEATURES: Should the hsb/hsb2/SL Pathfinder Series Display(s) feature internal fishfinder circuitry or currently be interfaced to a DSM250, then its transducer may be adapted (w/E66066 Transducer Adapter) to be mated to the fishfinder Transducer socket of an ax7/cx7/e7D/ex7/eSx7 MFD to support operation as a 600W fishinder. The DSM250 is not compatible with the a/c/e/eS/gS-Series MFDs. Should the hsb2 Pathfinder Series Display(s) currently be interfaced to a DSM250 w/1kW transducer, then the DSM250 may be replaced with a CP370 to support continued operation as a 1kW fishinder. The a/c/e/eS/gS-Series MFDs may also be mated to the CP100, CP200, and CP470/570 fishinder modules & compatible transducer(s) to support CHIRP/DownVision, SideVision, and high power CHIRP sounding.

SIRIUSXM SATELLITE WEATHER/RADIO FEATURES: It is recommended that a SR150 SiriusXM Satellite Weather / Radio Receiver be used to support the SiriusXM Satellite Weather and SiriusXM Satellite Radio features of an a/c/e/eS/gS-Series MFD. While it is possible to interface a SR50 Sirius Satellite Weather/Radio Receiver to an a/c/e/eS/gS-Series MFD, Sirius Satellite Radio will not be supported with this Satellite Radio Receiver and some satellite weather graphics layers will not be supported.

PROFESSIONAL INSTALLATION: While the replacement of this equipment is well within the capabilities of those familiar with marine electronics equipment installation, there will be some cable splicing and cable chasing required. Should this not be within your comfort zone or skills, then click here to locate a Certified Raymarine Installer in your area.

CRAFAQ#

Using the latest Navionics chart cards with an A/C/E-Series Classic MFD

When using currently available Navionics cartography, it it is strongly recommended that that the MFD be updated with the latest available Raymarine product software updates. A/C/E-Series Classic MFDs were designed and tested for use with Navionics Gold, Platinum (not Platinum Plus), and HotMaps chart cards. These retired MFDs were not tested with Navionics chart cards containing more than 2GB of nautical charts (not to be confused with 3D chart, sonar charts, aerial overlay charts, etc.). While the A/C/E-Series Classic MFDs may support reading cartography from Navionics Gold, NAV+, and Platinum Plus chart cards having memory capacities as large as 16GB, it is our experience that chart cards containing more than 2GB of nautical charts stored on the chart card may increase screen redraw times, and/or cause the MFD to reboot, and/or not be able to be viewed by the MFD. Prior to purchasing a new chart chard for an A/C/E-Series Classic MFD, it is recommended that Navionics be contacted to verify that the specific chart card being considered has been tested with your model of A/C/E-Series Classic MFD. As the NAV+ chart cards are pre-populated by Navionics with more than 2GB of charts, it is recommended that the NAV+ chart card's Nautical Charts be deleted and replaced with less than 2GB of nautical charts using the Navionics Chart Installer application.

CRAFAQ#

Adding a C/E-Series Widescreen MFD(s) to a network featuring E-Series Clasic MFDs

Unfortunately, C/E-Series Widescreen MFDs may not be interfaced to an Ethernet (SeaTalkhs/RayNet) network which also features E-Series Classic MFDs. While it is possible to interface an E-Series Classic MFD to a common SeaTalkng backbone to which a C/E-Series Widescreen MFD also been interfaced, communications would be limited to alphanumeric, GPS, instrument, navigational, and system status data between these systems. Correspondingly, it is not possible for E-Series Widescreen MFDs to share graphical data (ex. radar imagery, fishfinder imagery, cartography, or Sirius Marine Weather) with an E-Series Classic MFD.

Should full functionality dual station or multi-station capability be desired, then it would be necessary that all MFDs be E-Series Classic MFDs, all MFDs be C-Series Widescreen MFDs (only two MFDs permitted), or all MFDs be E-Series Widescreen MFDs.

CRAFAQ#

Interfacing a Raystar 130 GPS Sensor to a a/c/e/eS/gS-Series MFD

It is recommended that the new a/c/e/eS/gS-Series MFD be upgraded with latest available Raymarine product software updates.

Any Raymarine products featuring a 1st generation SeaTalk interface which do not additionally feature a SeaTalkng interface (ex. ST40/60+ Instrument Displays, ST6002, S3G, etc.) should be interfaced to one another, in any order, using standard SeaTalk cable. SeaTalk cables can be joined using D244 SeaTalk Junction Blocks, splices, marine grade terminal strips, or R55006 SeaTalk Auxiliary Junction Boxes. SeaTalk cable is available in 15", 1m, 3m, 5m, and 9m lengths (D230, D284, D285, D286, and D287 respectively). This method of interfacing is referred to as a SeaTalk bus.

The SeaTalk bus will need to be branched or extended and connected to a D244 SeaTalk Junction Block. The SeaTalk Junction Block will in turn be connected to the yellow (SeaTalk) port of a SeaTalk to E22158 SeaTalkng Converter Kit (w/v1.21 software) using the cable supplied with the SeaTalk to SeaTalkng Converter Kit. The Raystar 130 GPS Sensor will in turn be interfaced to one of the white SeaTalkng spur ports using the cable supplied with the GPS sensor. The SeaTalkng power cable supplied with the SeaTalk to SeaTalkng Converter Kit will be interfaced to the other white SeaTalkng spur ports of the SeaTalk to SeaTalkng Converter. One of the two SeaTalkng Termination Plugs supplied with the SeaTalkng Converter Kit will need to be installed in either of the two blue SeaTalkng backbone ports of the SeaTalk to SeaTalkng Converter. The new a/c/e/eS/gS-Series MFD will be interfaced to an A06028 SeaTalkng T-Piece or an A06064 SeaTalkng 5-Way Connector using an appropriate length of SeaTalkng Spur Cable ((400mm (A06038), 1m (A06039), 3m (A06040), 5m (A06041)). The remaining SeaTalkng Termination Plug supplied with the SeaTalkng Converter Kit will need to be installed in either of the two blue SeaTalkng backbone ports of the SeaTalkng T-Piece or an SeaTalkng 5-Way Connector. Finally, a SeaTalkng Backbone Cable of appropriate length (400mm (A06033), 1m (A06034), 3m (A06035), 5m (A06036), 9m (A06068), 20m (A06037)) will be used to connect the remaining blue SeaTalkng backbone port of the SeaTalkng T-Piece or a SeaTalkng 5-Way Connector to the remaining blue SeaTalkng backbone port of the SeaTalk to SeaTalkng Converter.

Image may be NSFW.
Clik here to view.
[Image: attachment.php?aid=91]


------------------

For systems featuring no additional SeaTalk or SeaTalkng devices:

The new a/c/e/eS/gS-Series MFD will be interfaced to one of the white SeaTalkng spur ports of an A06064 SeaTalkng 5-Way Connector using an appropriate length of SeaTalkng Spur Cable. The Raystar 130 GPS Sensor will be interfaced to one of the white SeaTalkng spur ports of the SeaTalkng 5-Way Connector using the cable supplied with the GPS sensor. An A06049 SeaTalkng Power Cable will be interfaced to the remaining white SeaTalkng spur ports of the SeaTalk to SeaTalkng Converter and to a 12VDC power source. Finally, an A06031 SeaTalkng Termination Plug will need to be installed in each of the two blue SeaTalkng backbone ports of the SeaTalkng 5-Way Connector. See diagram below.

Image may be NSFW.
Clik here to view.
[Image: attachment.php?aid=90]


----------------

As the a/c/e/eS-Series MFDs feature an internal GPS sensor, when interfacing an external source of GPS data (ex. Raystar 130, Airmar Weather Station, etc.) or when installing more than one of these MFDs within a system, it is necessary that the Data Master MFD's Data Sources feature (HOME->SET-UP->SYSTEM SETTINGS->DATA SOURCES) be used to specify the single source of GPS data which will be used by the Raymarine system.

CRAFAQ#

Image may be NSFW.
Clik here to view.
.jpg
  Clipboard02.jpg (Size: 110.37 KB / Downloads: 2)

Image may be NSFW.
Clik here to view.
.jpg
  Clipboard04.jpg (Size: 137.01 KB / Downloads: 2)

Will the new CPT100 DVS work on A98 MFD

I have an A98 and am using the CPT100. The break away bracket is broken. I saw that there is a new CPT100 DVS transducer; with what appears to be a better bracket. Will the new transducer work on the A98 MFD, is it better then the old CPT100 or can I just purchase the new style bracket and use it with the original CPT100. Thank You Dave

Dragonfly 4 Pro w/ update 12.09 not working properly

I have had my Dragonfly 4 Pro since November of last year. No issues at all with it. I did the update to v. 12.09 and then my problems started.

Depth only works around 10mph and below, if I go above that, the screen goes blue and shows 1200'. Sonar does the same thing, works till about 10mph and then goes white.

GPS seems to take alot longer to get my position now.

I did a reset on the unit when the issues first started to see if it would fix it, and it has not.

Thanks,

Stephen Phillips

Testing ST60

So, I have nothing showing on my ST60 (new to me, so I have no idea what I am doing)
The center of the screen, looks kinda brown.
I removed from the boat to bench test with my 12v power supply.
I connected +12vdc to the red terminal of the sea talk connection point, and the negative to the gray. The display (back) lights up for a second and the DEPTH and other items come on. Still has that (large) brown spot on the center of the display. Am I testing it right? Any suggestions, before I send it to the factory?

Thanks

ES9 Interface with ST6001+

I have a ST6001+ autopilot with a linear drive. Will this unit interface with the ES9, via ST to STng converter and allow of AP from the ES9?

Thanks in advance!

repave st60+ with i60

I currently have the ST60+ on my sailboat. I would like to replace it with the i60 wind. The question I have can I plug the old wind machine at the top of the mast directly into the new i60 wind display? Will I be loosing and functionality in using the old wind transducer?

Thanks

auto pilot replacement

I have a 43 sailboat that has a Raymarine Smart Pilot S2G AST driving a linear ram. I would like to replace this with the EV-1 system. I looked at your price list and I believe the T70161 will do the job. ACU-400, p70, and EV-1 core. Will the ACu-400 be over kill? Shouold I drop down to the ACU-300? You do not have a system pack with the ACU-300, just the ACU-400.

Fusion RA 205 Connection to SeaTalk ng

What cable (s) are required to connect a Fusion RA205's NMEA 2000 port to the SeaTalk ng backbone so I can control the Fusion audio with an e125 running LH 15?

Adding EV 200 Autopilot

I'm adding an EV 200 hyd package with a Teleflex Smartstick Rudder reference to my 2008 Pursuit 315OS.

This is the equipment that is currently installed on my boat:
Raymarine E120
Raymarine Gyroplus SHS
Raymarine SR 100
Raymarine SeaTalk HS
Raymarine DSM 300
Raymarine Radar
Sea Star Outboard Hydraulic steering for twin 250 Yamaha with power steering

I had a couple of questions:

1. Is there a diagram that shows the shows the exact hook up for this setup?
2. Do I still need the fluxgate compass? Is there anything that I can remove?
3. Do I need some type of bridge between the two systems to make them compatible?

Thank in Advance.

Why did I get a standard SD card with my new A98?

I just bought a new A98 MFD with preloaded lighthouse vector charts, packaged inside the box is a Lighthouse charts SD card, why? The MFD only accepts micro -SD, what am i supposed to do with the standard SD card?

Interfacing a Fusion stereo head unit to an a/c/e/eS/gS-Series MFD

Fusion True Marine stereo head units are manufactured with Ethernet and/or NMEA 2000 communications interfaces. For maximum performance, it is recommended that Fusion stereos featuring an Ethernet interface (ex. 750 Series, 700i/700 Series, etc.) be interfaced to Raymarine's a/c/e/eS-Series MFDs via an Ethernet network rather than via a NMEA 2000 network. In a simple system, the Fusion True Marine stereo head unit's Ethernet socket may be interfaced to the MFD's Ethernet network socket (RayNet (M)) via an appropriate length of RayNet (F) to RJ45 (M) Cable. In a larger system, the Fusion True Marine stereo head unit's Ethernet socket may be interfaced to the Ethernet network socket (RayNet (M)) of a HS5 RayNet Network Switch using an appropriate length of RayNet (F) to RJ45 (M) Cable.

Fusion True Marine stereo head units which only feature a NMEA 2000 communications interface (ex. 650 Series, 70 Series, 205 Series, etc.) may be interfaced to a Raymarine system featuring a/c/e/eS/gS-Series MFDs, via a powered and properly terminated SeaTalkng backbone. A simple SeaTalkng backbone may be constructed from the following components:

- A06064 SeaTalkng 5-Way Connector
- A06031 SeaTalkng Termination Plugs x 2
- A06049 SeaTalkng Power Cable ... connected to 12VDC power circuit protected with a 5A fuse
- Fusion accessory CAB000863 unpowered NMEA 2000 Connection Cable ... features a DeviceNet (M) plug
- A06045 0.4m SeaTalkng to DeviceNet (F) Adapter or A06075 1m SeaTalkng to DeviceNet (F) Adapter ... to be connected between the above listed Fusion CAB000863 cable and a spur port of the SeaTalkng 5-Way Connector
- an appropriate length of SeaTalkng Spur Cable to interface the MFD to a spur port of the SeaTalkng 5-Way Connector.

CRAFAQ#

connecting Uniden 380 VHF to A98 MFD

How do I connect my new A98 to my Uniden 380 VHF? Which wires go where?

E7 MFD without cartography

I recently purchase a new boat which has an e7 MFD without cartography (model E62354). I am a bit confused about "without cartography" . Does this mean that the unit simply does not have the chip installed for cartography, or does it mean that the unit will not accept a cartography chip?

Interfacing a DSC VHF radio via NMEA 0183 to an a/c/e/eS/gS-Series MFD

NOTE: As the colors of the NMEA 0183 leads of DSC VHF radios differ from manufacturer to manufacturer and often from model to model, it will be necessary to consult your DSC VHF radio's installation/operation guide to determine the colors of its leads supporting the following:
- NMEA 0183 IN+ (required)
- NMEA 0183 IN- (required)
- NMEA 0183 OUT+ (optional ... permits MFD to automatically plot DSC position reports)
- NMEA 0183 OUT- (optional ... permits MFD to automatically plot DSC position reports)

----------------------

On the a/c/e/eS/gS-Series MFD to which the NMEA 0183 DSC VHF will be interfaced, configure the MFD's Port 1 for 4800 BAUD NMEA 0183 communications (HOME->SET-UP->SYSTEM SETTINGS->NMEA SET-UP->NMEA INPUT PORT 1:->NMEA 4800). The NMEA 0183 Port 1 leads of the a/c/e/eS/gS-Series MFD's Power/NMEA 0183 Video Input Cable will be interfaced to the NMEA 0183 leads of the DSC VHF radio as follows:

- MFD NMEA 0183 Port 1 OUT+ (yellow) lead to DSC VHF 4800 BAUD NMEA 0183 IN+ lead
- MFD NMEA 0183 Port 1 OUT+ (brown) lead to DSC VHF 4800 BAUD NMEA 0183 IN- lead
- MFD NMEA 0183 Port 1 IN+ (white) lead to DSC VHF 4800 BAUD NMEA 0183 OUT+ (blue) lead
- MFD NMEA 0183 Port 1 IN- (green) lead to DSC VHF 4800 BAUD NMEA 0183 OUT- (brown) lead

CRAFAQ#

Bundled cartography options for a/c/e/eS/gS-Series MFDs

The memory of Raymarine's a/c/e/eS/gS-Series MFDs is not and can not be pre-loaded with cartography. The Chart application of these MFDs is dependent upon the presence of a compatible LightHouse, Navionics, or C-Map chart card within the MFD's memory card reader when using the MFD. Raymarine a/c/e/eS/gS-Series MFDs may be purchased with a pre-populated LightHouse Charts card, Navionics NAV+ Chart Card, or C-Map 4D Essentials Chart Card. Alternatively, these MFDs may be purchased without a chart card. The latter option may be chosen for a system which
- features more than one a/c/e/eS/gS-Series MFD (cartography is shared between networked a/c/e/eS/gS-Series MFDs) or
- the a/c/e/eS/gS-Series MFD bundled chart card options are not consistent with the cartography requirements of the user (ex. user desires 3D, aerial overlay cartography, and pilot book data found in Navionics Platinum Plus cartography)

CRAFAQ#

Updates

Just want to be clear on updating. When I download the new ver 16 for my
e7 does that also update the other peripherals on the system? Evolution autopilot, AIS 650, HD Radar. If not can I download those updates to the same cf card as the e7 update or do I need to do them separately?
Viewing all 8621 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>