AIS Connection Lost | C90W | IC-M506 | NMEA-2000

[Mike Parker]

There is a software update available for the Icom M506 which resolved some NMEA2000 communication issues. I don't know if it corrects this particular issue, but it is worth a try.
Update can only be performed by Icom or an authorized Icom Repair Facility.
At the time I set an M506 in it came back with version 1.002. I think recently shipped M506 radios have later software versions.

[Greggegner@gmail.com]

I have the follow on Raymarine NMEA 2000 cabling ( no Seatalk ng to NMEA converter). I have read the thread, checked the FAQs and cannot find an issue.
My MNEA 2000 network:
-C90W – not able to receive from the Icom – firmware is latest patch V 2.35
-Icom M506 – receiving long/lat and speed without issue
-Actisense 0183 to NMEA converter -nothing is attached to it
Raymarine NMEA power connection
All connections are Ts
In addition I have ST60 wind, depth, and speed gauges I want to get into NMEA 2000 via cable A06047.

Q1: how should C90W be configured to receive NMEA 2000?
Q2: do I need to add a Seatalk ng to NMEA 2000 converter for either the ST60 and/or C90W?

[Chuck - Raymarine - Moderator]

Gregg,

Q1: how should C90W be configured to receive NMEA 2000?
A1: Other than ensuring that the NMEA 2000 network has been been interfaced to the Data Master MFD, there are no configuration settings which need to or can be made to cause the MFD to receive data via its SeaTalkng/NMEA 2000 port. If the MFD is receiving data from a compatible device then one need only configure the AIS Objects layer to ON within the Chart application page/pane being viewed. Like any other device supporting SeaTalkng / NMEA 2000 communications, each NMEA 2000 device to be networked must be interface as a spur to a powered and properly terminated SeaTalkng / NMEA 2000 backbone.

Q2: do I need to add a Seatalk ng to NMEA 2000 converter for either the ST60 and/or C90W?
A2. As the SeaTalk to SeaTalkng Converter's software is more advanced with respect to NMEA 2000 processing, it is recommended that when interfacing the MFD to a SeaTalkng / NMEA 2000 backbone that a SeaTalk to SeaTalkng Converter rather than the MFD be used as the system's SeaTalk to SeaTalkng / NMEA 2000 data bridging device. Accordingly, it would be recommended that a SeaTalk to SeaTalkng Converter which has been updated with the latest available Raymarine product software updates be installed so support integration of the ST60 instruments with the system.

[Greggegner@gmail.com]

I am planning on buying E22158 SeaTalk one to SeaTalkng converter and hooking the NMEA 2000 spur cable from the Icom to the a blue connection. The ST60 will be on the yellow connection using the Seatalk1 to NMEA conversion cable. The C90W will be connected on the white connector with a terminator on the other blue. I will load the converter software on the C90W. Does this sound correct?

[Chuck - Raymarine - Moderator]

Gregg,

Q: I am planning on buying E22158 SeaTalk one to SeaTalkng converter and hooking the NMEA 2000 spur cable from the Icom to the a blue connection. The ST60 will be on the yellow connection using the Seatalk1 to NMEA conversion cable. The C90W will be connected on the white connector with a terminator on the other blue. I will load the converter software on the C90W. Does this sound correct?
A: Negative. The NMEA 2000 VHF radio will not be interfaced to the SeaTalk to SeaTalkng Converter's backbone socket. Instead, an additional spur socket to accommodate the NMEA 2000 VHF radio must be added to the SeaTalkng / NMEA 200 backbone created with the SeaTalk to SeaTalkng Converter. Please click here to view a FAQ addressing how to add spur sockets to a SeaTalkng / NMEA 2000 backbone.