Seatalk converter ST60+not on ng backbone

[Chuck - Raymarine - Moderator]

Alvin,

Please note that Raymarine MFDs are not designed to supply power to a SeaTalkng / NMEA 2000 backbone. Within the system which you have described, the ACU-200's SeaTalkng Power dip switch should be configure to OFF and the SeaTalkng Power Cable supplied with the SeaTalk to SeaTalkng Converter should be connected to a spur socket located at the approximate mid-point of the backbone's LEN load. The ST60 Depth Instrument would then be connected to the yellow SeaTalk socket of the ST-STng Converter. Within this installation, the ST60's Depth Instrument's second SeaTalk port should not have any cable connected to it.

Communications with the ST60 Depth instrument would then be verified by first ensuring that the ST60 Depth Instrument is reporting depth. If so, then the MFD's Data Sources feature should then be configured to Manual and the ST60 Depth Instrument should be selected from the list of Depth data sources. After doing so, an application page other than the MFD's Fishfinder page should be opened and configured to display Databox 1 or 2 which in turn has been configured to be populated with the Depth data item. Should the Databox be dashed and the ST60 Depth Instrument report a value for depth, then it would appear that the ST60 Depth Instrument may have suffered a failure of it's SeaTalk communications circuitry. The ST60 Depth Instrument may be tested by disconnecting it from the system and then interfacing it to a powered SeaTalk bus to which another device having a SeaTalk communications interface and capable of displaying Depth data has been interfaced.