{"id":17213,"date":"2026-04-22T12:23:26","date_gmt":"2026-04-22T12:23:26","guid":{"rendered":"https:\/\/manuals.seakeeper.com\/ride\/troubleshooting-checklist-codes-554-555\/troubleshooting-checklist-codes-553-554-555\/"},"modified":"2026-04-28T17:46:13","modified_gmt":"2026-04-28T17:46:13","slug":"troubleshooting-checklist-codes-553-554-555","status":"publish","type":"page","link":"https:\/\/manuals.seakeeper.com\/ride\/troubleshooting-checklist-codes-553-554-555\/troubleshooting-checklist-codes-553-554-555\/","title":{"rendered":"Troubleshooting Checklist &#8211; Codes 553, 554, &#038; 555"},"content":{"rendered":"\n<h1 class=\"wp-block-heading\">1.&nbsp; Notes Before Beginning:<\/h1>\n\n\n\n<p><strong>Background \u2013 <\/strong>Fault Codes 553, 554 and 555 are related to the GPS signal Ride is receiving from the boat. Each is specific to help understand precisely what problem must be overcome for proper Ride operation.<\/p>\n\n\n\n<p><strong>Separate NMEA 2000 and <span translate=\"no\">Seakeeper<\/span> Ride CAN Networks \u2013<\/strong><\/p>\n\n\n\n<div class=\"wp-block-columns is-layout-flex wp-container-core-columns-is-layout-9d6595d7 wp-block-columns-is-layout-flex\">\n<div class=\"wp-block-column is-layout-flow wp-block-column-is-layout-flow\" style=\"flex-basis:20%\">\n<figure class=\"wp-block-image size-full is-resized\"><img loading=\"lazy\" decoding=\"async\" width=\"231\" height=\"158\" src=\"https:\/\/manuals.seakeeper.com\/ride\/wp-content\/uploads\/image-63.png\" alt=\"\" class=\"wp-image-10754\" style=\"aspect-ratio:1.4683544303797469;width:146px;height:auto\"\/><\/figure>\n<\/div>\n\n\n\n<div class=\"wp-block-column is-layout-flow wp-block-column-is-layout-flow\" style=\"flex-basis:66.66%\">\n<p><strong><u><span translate=\"no\"><span translate=\"no\"><span translate=\"no\">Seakeeper<\/span><\/span><\/span> Ride CAN is not to be connected to NMEA 2000 Cables. The two networks must be built separately.<\/u><\/strong> <span translate=\"no\"><span translate=\"no\"><span translate=\"no\">Seakeeper<\/span><\/span><\/span> Ride Software Module receives one (1) drop from the NMEA 2000 CAN network on a dedicated port. In no other location shall the networks be connected to each other. No other CAN networks shall be connected to <span translate=\"no\"><span translate=\"no\"><span translate=\"no\">Seakeeper<\/span><\/span><\/span> Ride.<\/p>\n<\/div>\n<\/div>\n\n\n\n<p><strong>Clearing Fault Codes \u2013 <\/strong>For some Faults within the Ride system, to clear the fault and proceed with normal automatic operation, the operator must acknowledge the fault by selecting the center button on the keypad or MFD. For Codes 553, 554 and 555 this is not the case, these will clear automatically once proper conditions are met. &nbsp;<\/p>\n\n\n\n<p><strong>Software Updates \u2013<\/strong> Ride always recommends updating to the newest software version in order for the troubleshooting guide below to be most relevant up to date and helpful. You can find software update instructions here \u2013 <a href=\"https:\/\/ride.seakeeper.com\/support\/software-updates\/\">Vessel Attitude Control System | Motion Control Software Updates<\/a><\/p>\n\n\n\n<p><strong>GPS signal influence on Ride motion detection \u2013<\/strong> Ride uses GPS signals for operation. As a result, Ride will indicate to the operator if there are problems with the GPS signal it is receiving. Furthermore, sometimes GPS antennas report inaccurate speeds and locations as they power up and receive their correct location fix. These inaccuracies can trigger motion related faults such as 508 Trim Angle Out of Range, 509 List Angle Out of Range on the Ride system. When this occurs, those motion related faults (508, 509) can be cleared once the GPS signal is corrected. Therefore, if you see multiple fault codes and 553, 554, or 555 are indicated among them, troubleshoot the GPS related 553, 554 or 555 first.<\/p>\n\n\n\n<p><strong>Ride GPS source selection \u2013<\/strong> <span translate=\"no\">Seakeeper<\/span> Ride will automatically select a GPS source which demonstrates it has the most accuracy of those antennas on the NMEA 2000 network. Once the boat is underway and <span translate=\"no\">Seakeeper<\/span> Ride is operational, if that GPS source degrades or disconnects, it might throw any of the 553, 554, or 555 faults. Slowing the boat down to a stop allows for the automatic feature to adjust and find an alternative source. Additionally, it is possible to manually override the automatic selection and choose a source.<\/p>\n\n\n\n<p><strong>Faults and Meanings \u2013<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>553 \u2013 EPE Fault<\/strong>\n<ul class=\"wp-block-list\">\n<li>This fault indicates that the NMEA 2000 network hardware is found but the GPS signal is of poor quality which may result in notably poor Ride performance. This can be a result of the location of the GPS antenna being obstructed by metal or carbon fiber, the geographical location of the boat, or hardware related to the GPS antenna.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>554 \u2013 NMEA 2000 Fault<\/strong>\n<ul class=\"wp-block-list\">\n<li>This fault indicates that the Ride Software Module does not see the hardware for a proper NMEA 2000 network. Note that a properly constructed NMEA 2000 network requires power, terminator resistors and drops to interconnect devices.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>555 \u2013 GPS Fix Loss Fault<\/strong>\n<ul class=\"wp-block-list\">\n<li>This fault indicates that the NMEA 2000 network hardware is found, but there is no qualified GPS antenna writing to the network. The GPS source must identify itself on the network as well as have a \u2018fix\u2019 or established satellite connection.\n<ul class=\"wp-block-list\">\n<li class=\"has-small-font-size\">If needed, contact <span translate=\"no\"><span translate=\"no\"><span translate=\"no\"><span translate=\"no\"><span translate=\"no\"><span translate=\"no\">Seakeeper<\/span><\/span><\/span><\/span><\/span><\/span> Ride for full details on what PGNs are required for Ride function.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<h1 class=\"wp-block-heading\">2.&nbsp; Fault 553 &#8211; EPE<\/h1>\n\n\n\n<h4 class=\"wp-block-heading\">A. <strong>GPS Signal Quality Check<\/strong><\/h4>\n\n\n\n<p>\u2610 Check Ride GPS source: Menu \u2192 Ride Info \u2192 GPS<\/p>\n\n\n\n<p>On this page you can see the signal quality of the GPS. <span translate=\"no\">Seakeeper<\/span> Ride looks for an EPE less than 5.0 for proper signal quality. If this value is consistently over 5.0, the 553 fault will trigger.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">B. <strong>Is there only one Antenna displayed?<\/strong><\/h4>\n\n\n\n<p>\u2610 YES \u2192 Continue<\/p>\n\n\n\n<p>\u2610 NO \u2192 Multiple Antennas Available \u2192 Manually select a different Antenna. Operate the boat at speed and determine if this selection has a better signal quality when underway. Repeat as necessary to determine best antenna for underway signal quality.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">C. <strong>Review antenna hardware quality<\/strong><\/h4>\n\n\n\n<p>\u2610 Check for obstructions to Anteanna including t-tops, biminis, large carbon fiber structures, etc.<\/p>\n\n\n\n<p>\u2610 If possible, relocate antenna to have clear, unobstructed view of horizon.<\/p>\n\n\n\n<p>\u2610 Check antenna hardware for bad or loose connections.<\/p>\n\n\n\n<p>\u2610 Check NMEA 2000 network for bad or loose connections.<\/p>\n\n\n\n<p>\u2610 If problem persists, consider replacing or adding a new GPS antenna to the NMEA 2000 network.<\/p>\n\n\n\n<h1 class=\"wp-block-heading\">A. Fault 554 \u2013 NMEA 2000<\/h1>\n\n\n\n<h4 class=\"wp-block-heading\">A. <strong>Does the fault appear at <span translate=\"no\">Seakeeper<\/span> Ride equipment startup?<\/strong><\/h4>\n\n\n\n<p>\u2610 YES \u2192 Continue<\/p>\n\n\n\n<p>\u2610 NO \u2192 Fault occurs intermittently \u2192 Go to Intermittent 554 Section.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">B. <strong>Software Module to NMEA 2000 Connection Check:<\/strong><\/h4>\n\n\n\n<p>\u2610 NMEA plug fully seated in Software Module.<\/p>\n\n\n\n<p>\u2610 NMEA drop is connected to the correct port on Software Module.<\/p>\n\n\n\n<p>\u2610 NMEA cable is connected to NMEA 2000 drop location on NMEA 2000 network.<\/p>\n\n\n\n<p>\u2610 No bent pins\/corrosion.<\/p>\n\n\n\n<p>\u2610 Cable not damaged.<\/p>\n\n\n\n<p>\u2610 Verify NMEA 2000 network is not cross connected to <span translate=\"no\">Seakeeper<\/span> Ride network (CAN Stats page).<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">C. <strong>NMEA 2000 network powered and terminated correctly?<\/strong><\/h4>\n\n\n\n<p>\u2610 Verify power to NMEA 2000 Network (check for blown fuse or breaker).<\/p>\n\n\n\n<p>\u2610 Terminator resistors are on NMEA 2000 Network.<\/p>\n\n\n\n<p>\u2610 Is Ride Software Module present on NMEA network? \u2192 Go to MFD manufacturer manual to review network devices shown on network.<\/p>\n\n\n\n<p>\u2610 No damage\/corrosion.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">D. <strong>If the fault persists:<\/strong><\/h4>\n\n\n\n<p>Follow the Warranty &amp; Replacement Procedure section. A Ride Support specialist will determine whether replacement components are required.<\/p>\n\n\n\n<h1 class=\"wp-block-heading\">B. Intermittent 554 Fault<\/h1>\n\n\n\n<h4 class=\"wp-block-heading\">A. <strong>Do other GPS dependent items on the boat fail intermittently?<\/strong><\/h4>\n\n\n\n<p class=\"has-text-align-center\"><strong>Troubleshoot your NMEA 2000 Network hardware.<\/strong><strong><\/strong><\/p>\n\n\n\n<p>\u2610 NMEA Power Tee correctly powered.<\/p>\n\n\n\n<p>\u2610 NMEA network is built with proper terminator resistors.<\/p>\n\n\n\n<p>\u2610 NMEA drops and backbones conform to correct sizing as specified by NMEA 2000.<\/p>\n\n\n\n<p>\u2610 No bent pins\/corrosion.<\/p>\n\n\n\n<p>\u2610 Cable not damaged<\/p>\n\n\n\n<p>\u2610 Verify NMEA 2000 network is not cross connected to <span translate=\"no\">Seakeeper<\/span> Ride network.<\/p>\n\n\n\n<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; \u2610 Check physical connectors.<\/p>\n\n\n\n<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; \u2610 No errors shown on CAN Statistics page (go to <span translate=\"no\">Seakeeper<\/span> Ride app on MFD \u2192 Settings \u2192 Info \u2192 CAN Statistics).<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">B. <strong>Backbone Power<\/strong><\/h4>\n\n\n\n<p>\u2610 Voltage confirmed with multimeter.<\/p>\n\n\n\n<p>\u2610 Reset power if unstable.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">C. <strong>Terminators<\/strong><\/h4>\n\n\n\n<p>\u2610 Terminators installed at both ends<\/p>\n\n\n\n<p>\u2610 Replace if missing\/damaged<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">D. <strong>If the fault persists:<\/strong><\/h4>\n\n\n\n<p>Follow the Warranty &amp; Replacement Procedure section. A Ride Support specialist will determine whether replacement components are required.<\/p>\n\n\n\n<h1 class=\"wp-block-heading\">C.Fault 555 \u2013 Loss GPS Fix<\/h1>\n\n\n\n<h4 class=\"wp-block-heading\">A. <strong>Allow time for all equipment to start up.<\/strong><\/h4>\n\n\n\n<p>\u2610 Power on the boat and allow to sit for 5 minutes with clear visibility to the sky.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\u2192 If <span translate=\"no\"><span translate=\"no\">Seakeeper<\/span><\/span> Ride receives power before the GPS both receives power and obtains a reliable fix, a 555 fault will occur. Make sure to allow enough time for all boat systems to power up and establish communication before attempting to troubleshoot. The 555 fault should automatically clear once GPS connection is established.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">B. <strong>Does the Fault Appear at Ride Equipment Startup?<\/strong><\/h4>\n\n\n\n<p>YES, but it will clear after a few minutes \u2192 See the above section Allow time for all equipment to start up.<\/p>\n\n\n\n<p>YES, and it will never clear \u2192 Continue to GPS Obstruction Check<\/p>\n\n\n\n<p>NO, faults occur intermittently while underway \u2192 Continue to the next section.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">C. <strong>GPS Obstruction Check<\/strong><\/h4>\n\n\n\n<p>\u2610 Verify boat is outdoors with clear sky view, no obstructions from buildings, canopies, covers, etc. Move boat to clear location if possible. Clear overhead obstructions from antenna, especially metal or carbon fiber if possible.<\/p>\n\n\n\n<p>\u2610 Once Obstruction Check is complete move onto MFD Check<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">D. <strong>MFD Check<\/strong><\/h4>\n\n\n\n<p>Is GPS fix demonstrated on MFD?<\/p>\n\n\n\n<p>YES \u2192 \u2610 Follow MFD Manufacturer guidance to have GPS fix output to NMEA 2000 bus (some MFDs have this as an option which can be selected on or off). Continue to other GPS Dependent Items.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\u2610 Verify the MFD which is demonstrating GPS fix is connected on the same NMEA 2000 network as <span translate=\"no\"><span translate=\"no\">Seakeeper<\/span><\/span> Ride.<\/li>\n<\/ul>\n\n\n\n<p>NO \u2192 \u2610 Troubleshoot NMEA 2000 Network antenna to provide valid GPS signal for all devices.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">E. <strong>Do other GPS dependent items on the boat fail intermittently?<\/strong><\/h4>\n\n\n\n<p>YES \u2192 Review hardware from GPS antenna to the NMEA 2000 backbone for loose connections, terminators or similar hardware. Consider replacing hardware if possible.<\/p>\n\n\n\n<p>\u2610 Plugs properly seated.<\/p>\n\n\n\n<p>\u2610 No bent pins\/corrosion.<\/p>\n\n\n\n<p>\u2610 Cables not damaged.<\/p>\n\n\n\n<p>\u2610 Tees not damaged.<\/p>\n\n\n\n<p>Note: if hardware failure is between NMEA 2000 backbone and Software Module it will display as 554.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">F. <strong>If the fault persists:<\/strong><\/h4>\n\n\n\n<p>Follow the Warranty &amp; Replacement Procedure section. A Ride Support specialist will determine whether replacement components are required.<\/p>\n\n\n\n<h1 class=\"wp-block-heading\">5. Warranty \/ Replacement Procedure (If Needed)<\/h1>\n\n\n\n<p>Gather the following:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\u2610 Software Module serial number.<\/li>\n\n\n\n<li>\u2610 Photos of wiring layout\/routing (when applicable).<\/li>\n\n\n\n<li>\u2610 List of electrical devices active when the fault occurs (when applicable).<\/li>\n\n\n\n<li>\u2610 Notes on any intermittent communication behavior.<\/li>\n<\/ul>\n\n\n\n<p>\u2610 Open a Ride Support case documenting all findings.<br>\u2610 Ensure troubleshooting details are included in the case.<br>\u2610 If a component is confirmed defective, a replacement will be issued per <span translate=\"no\">Seakeeper<\/span> warranty policy.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>1.&nbsp; Notes Before Beginning: Background \u2013 Fault Codes 553, 554 and 555 are related to the GPS signal Ride is receiving from the boat. Each is specific to help understand precisely what problem must be overcome for proper Ride operation. Separate NMEA 2000 and Seakeeper Ride CAN Networks \u2013 Seakeeper Ride CAN is not to [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":17211,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"footnotes":""},"manual":[377],"model":[],"document_type":[],"hidden":[],"class_list":["post-17213","page","type-page","status-publish","hentry","manual-troubleshooting-checklist-codes-553-554-555"],"acf":[],"_links":{"self":[{"href":"https:\/\/manuals.seakeeper.com\/ride\/wp-json\/wp\/v2\/pages\/17213","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/manuals.seakeeper.com\/ride\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/manuals.seakeeper.com\/ride\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/manuals.seakeeper.com\/ride\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/manuals.seakeeper.com\/ride\/wp-json\/wp\/v2\/comments?post=17213"}],"version-history":[{"count":4,"href":"https:\/\/manuals.seakeeper.com\/ride\/wp-json\/wp\/v2\/pages\/17213\/revisions"}],"predecessor-version":[{"id":17279,"href":"https:\/\/manuals.seakeeper.com\/ride\/wp-json\/wp\/v2\/pages\/17213\/revisions\/17279"}],"up":[{"embeddable":true,"href":"https:\/\/manuals.seakeeper.com\/ride\/wp-json\/wp\/v2\/pages\/17211"}],"wp:attachment":[{"href":"https:\/\/manuals.seakeeper.com\/ride\/wp-json\/wp\/v2\/media?parent=17213"}],"wp:term":[{"taxonomy":"manual","embeddable":true,"href":"https:\/\/manuals.seakeeper.com\/ride\/wp-json\/wp\/v2\/manual?post=17213"},{"taxonomy":"model","embeddable":true,"href":"https:\/\/manuals.seakeeper.com\/ride\/wp-json\/wp\/v2\/model?post=17213"},{"taxonomy":"document_type","embeddable":true,"href":"https:\/\/manuals.seakeeper.com\/ride\/wp-json\/wp\/v2\/document_type?post=17213"},{"taxonomy":"hidden","embeddable":true,"href":"https:\/\/manuals.seakeeper.com\/ride\/wp-json\/wp\/v2\/hidden?post=17213"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}