E120/SeaRay Navigator Upgrade ?

[rvaupel23]

Thanks Chuck. You've been great here. So I've begun the work and everything is going in as planned.

Q) Flipping the last question around, can I leverage a single MFD's NMEA 0183 outputs to feed multiple listeners? ie, the VHF and my VesselView that's looking for GPS data. Or, should I use the NMEA 0183 outputs of the "slave" MFD to feed that device? I wasn't sure if the slave broadcasts NMEA data or only the data master. Which is ok/better?

Thanks again.

[Chuck - Raymarine - Moderator]

Ryan,

Q) Flipping the last question around, can I leverage a single MFD's NMEA 0183 outputs to feed multiple listeners? ie, the VHF and my VesselView that's looking for GPS data. Or, should I use the NMEA 0183 outputs of the "slave" MFD to feed that device? I wasn't sure if the slave broadcasts NMEA data or only the data master. Which is ok/better?
A) Please click here to view a FAQ addressing this subject. Unlike the SeaTalkng/NMEA and SeaTalk communications interfaces of Raymarine MFD, the NMEA 0183 interfaces MFDs will be operational irrespective of whether the MFD has or has not been configured as the system's Data Master MFD. However, in this case, I would simply recommend following the recommendations of the FAQ unless the physical locations of the MFDs and NMEA 0183 listeners make it more convenient to use the NMEA 0183 ports of each MFD to supply data to the NMEA 0183 listeners.

[rvaupel23]

I've realized there was a second transducer in my original setup. I beleive its:

Sea Ray part# 1757382
NAVIGATOR, SRNII TRANSDUCR DEPTH/TEMP W/PT NY

That seems to equate to:

Part manufacturer: Maptech
Part number: 105-0401-S
Connections: (1) 5-pin male
Airmar #: 44-088-1-01, 170kHz

Q: Can I interface this transducer into my new system, perhaps with an ITC5?

[Chuck - Raymarine - Moderator]

Ryan,

Q: Can I interface this transducer (Part manufacturer: Maptech Part number: 105-0401-S, Connections: (1) 5-pin male; Airmar #: 44-088-1-01, 170kHz) into my new system, perhaps with an ITC5?

A: I believe that the transducer is an Airmar smart transducer, cable of functioning as a NMEA 0183 or NMEA 2000 smart depth sensor ... recommend verifying with Airmar, Inc.. Accordingly, the transducer may not be used with the iTC-5. Should the specification for the transducer have indicated that it was designed to operate at 200kHz, then there may have been a possibility were it not a smart transducer. Should Airmar confirm that the transducer is a smart transducer supporting NMEA 2000 communications protocol, then it would be recommended that it be interfaced as a spur to the SeaTalkng backbone formed by the SeaTalk to SeaTalkng Converter. Should an additional spur socket need to be added to the system to support interfacing the NMEA 2000 transducer, then please click here to view a FAQ addressing this subject. Please click here to view a FAQ addressing how to interface third party devices having a NMEA 2000 communications interface to a SeaTalkng backbone.

[rvaupel23]

When connecting my CAM220 to the HS5 through the PoE Injector, can/should I use this connectivity method:

1. HS5 SeaTalkhs Network Switch (A80007) - Under the helm
2. RayNet to RJ45 Port Male Cable, 1M (A62360) - From the HS5 to the PoE injector
3. PoE Injector (R32141) - Under the helm where my HS5 and fuse block is located
4. G-Series Highspeed Patch Cable, 10M (E06056) - From the injector routed up/back to the camera's location
5. Supplied Waterproof RJ45 ethernet coupler (R32142) - To connect the camera's ethernet cable to the patch cable

I wasn't sure between these cables, the injector, and/or the coupler if anything was acting as a "cross-over" that might prevent connectivity. The CAM220 installation documentation doesn't describe this exact example. Thanks.

[Chuck - Raymarine - Moderator]

Ryan,

The method which you have described to interface the CAM220IP to the HS5 RayNet Network Switch is correct. However, of Raymarine's RJ45 to RJ45 Cables, only the R32140 RJ45 to RJ45 Cable features POE leads.

[rvaupel23]

I made all the connections today. The PoE injector has a red light on, assuming that means it's getting suitable power. I don't however get anything lit on the corresponding HS5 port nor does my MFD recognize a camera source. It says "No video source available" when I navigate to the camera applet. Is there something else I need to do to configure / activate the cam? The installation manual didn't specifically suggest so. Thanks.

[Chuck - Raymarine - Moderator]

Ryan,

Please click here to view a FAQ addressing this subject.

[rvaupel23]

Quick update. I connected the cam's Ethernet feed directly to the injector and it immediately started working. So, is the g series patch cable as described above not PoE compatible or is the cam's included coupler indeed doing a crossover?

[Chuck - Raymarine - Moderator]

Ryan,

Of Raymarine's RJ45 to RJ45 Cables, only the R32140 25' RJ45 to RJ45 Cable features POE leads. The E66054, E66055, E66056,E66057, and A62136 RJ45 to RJ45 Cables do not feature POE leads and as such should not be used to interface a POE device to a POE injector. FLIR/Raymarine also offers the following RJ45 to RJ45 Ethernet Cables featuring POE leads should longer lengths be required (the following are FLIR part numbers):
- 25' 308-0163-25
- 50' 308-0163-50
- 75' 308-0163-75
- 100' 308-0163-100

Please click here to view a FAQ addressing where one may purchase Raymarine/FLIR parts.