+- Raymarine forum (http://forum.raymarine.com)
+-- Forum: Raymarine Forums (/forumdisplay.php?fid=1)
+--- Forum: Networking / System Integration (/forumdisplay.php?fid=21)
+--- Thread: Troubleshooting a SeaTalkng communications failure (/showthread.php?tid=2260)
Troubleshooting a SeaTalkng communications failure - Chuck - Raymarine - Moderator - 12-19-16 11:37 AM
Troubleshooting a SeaTalkng communications failure
Conflicts between data sources may present symptoms of a SeaTalkng communications failure. When the system features more than one source for any type of data, it is necessary to ensure that the Data Sources feature has been utilized to specify which resources will be used by the system for each type of data (GPS, Wind, Depth, etc.) for which two or more sources are present within the system. As such, prior to proceeding with troubleshooting apparent SeaTalkng communications failure (NO AIS, NO FIX, etc.), it is recommended that one first verify that the Data Sources feature has been properly used. Additionally, should the system feature an AIS350, AIS650, or AIS500, it is recommended that one verify that the AIS350, AIS650, or AIS500 has been interfaced by one communications protocol only (i.e. either SeaTalkng (preferred) or NMEA 0183, but not both).
Should the the Data Sources and AIS receiver/transceiver points raised above have been satisfied, and a SeaTalkng communications failure persist, then it is recommended that the vessel's batteries be fully charged, and that after charging and while connected to shore power that the problem be duplicated. Should the problem not be able to duplicated under these conditions, then the problem may have resulted from insufficient power and it would correspondingly be recommended that the power issue be addressed by one or more of the following:
- the vessel's batteries be load tested and replaced depending upon the results of the load tests,
- additional house battery storage be added to the vessel,
- the vessel's charging system be operated more frequently,
- the vessel's charging system capacity be increased.
Should one be able to duplicate the problem while connected to shore power, then it is recommended that the following be verified:
- the backbone be inspected for
----- proper termination,
----- the SeaTalkng backbone's power insertion spur has been located at the approximate midpoint of the SeaTalkng backbone's LEN load
----- if a SeaTalkng backbone power insertion spur has been installed and a Raymarine Evolution ACU200/400 or SPX10/30 autopilot course computer has been installed, that the ACU or course computer's SeaTalkng POWER switch has been configured to the OFF position. Note: it is considered a best practice that the SeaTalkng backbone be powered via a power insertion spur (ex. T-Piece, 5-Way Connector spur socket).
----- maximum total spur length (6m) not exceeded,
----- no more than 3 devices daisy chained within a spur,
----- proper splices,
----- signs of cable damage (cuts, kinks, crush, etc).
- check the resistance of the backbone's two termination plugs ... the measured resistance across its CAN_H and CAN_L pins should be 120 ohms.
- with the backbone powered OFF and one of its two termination plugs removed, check the resistance of the backbone across the CAN_H and CAN_L pins of the backbone socket which had its termination plug removed to verify that it is 120 ohms ... if not, then devices should be removed one by one until it is determined which device is causing the resistance to not be as expected ... should any such device be identified, then it should be sent to Raymarine’s Product Repair Center to be bench checked / serviced.
- with the backbone powered OFF, the aforementioned termination plug should be reinserted into its backbone socket and then the other termination plug should be removed. The resistance of the backbone across the CAN_H and CAN_L pins of the backbone socket which had its termination plug removed should then be checked to verify that it is 120 ohms ... if not, then devices should be removed one by one until it is determined which device is causing the resistance to not be as expected ... should any such device be identified, then it should be sent to Raymarine’s Product Repair Center to be bench checked / serviced.
RAYFAQ#