Search the Community

Fellow Malibu crew, I have a 2014 23LV that I get a "Loss of CAN Signal" upon power on and it will not allow me to crank engine. Initially when using bypass key it will blow the 10amp fuse connected to the Power button. I did some individual disconnect of most of the CAN connected components and was able to get the 10 amp fuse to stop popping and actually crank with the key to give me an engine error code. The code that I get is a SPN:66014 FMI:4. I just paid the dealer to fix prior to list of troubleshooting below and they said they cleaned many of the connections and replaced fuses. It cranked 1 time and ran for about 400 yards and I shut it off and when I tried to start it again I got the same Loss of CAN Signal. Since receiving it back I had a friend who is an airplane mechanic and works on CANbus daily help me, but without having the wiring diagrams for the boat we could only do so much. Here is what we tested: 16 pin Delphi connector at the engine bay gave a 120ohm reading back to the connector under the dash. Disconnected each of the following components individually to test to see if removing them from the CAN network did away with the Loss of CAN signal warning - GPS, Depth Gauge, Paddlewheel, Surf Gate, ECM, Viper control module - Loss of CAN signal continued to show up even after disconnecting each individually and trying to restart Checked all ground connections - I believe the Dealer checked these as well Disconnected and reconnected Starter Checked readings at battery and starter and all were good Cranked with key and pulled emergency shutoff lanyard Tested relay (either PTR or Start) with a 9v battery to ensure relay was good One thing that is interesting is that if I turn the bypass key 1 click the Loss of CAN signal error goes away. Prior to doing this the engine shows 0 hours and no engine info. once I move key to that position the 380 hours comes up along with engine temp, etc. Another thing to note is that depth gauge a few minutes before the 1st Loss of CAN error appeared to be reading erradically bouncing from 2 feet to 4 feet to 6 feet, etc for a few minutes. When I received back from the dealer the depth finder didn't work at all giving a 0 ft reading. I read a few comments from other posts from @csleaver and @oldjeep which were very helpful in troubleshooting. If the ECM was toast altogether, I would assume disconnecting it from the CAN altogether would have proved that but I still got the error . So in short - without the key I get a Loss of Can error and in using the bypass key I can get the SPN: 66014 FMI:4 Sorry for the long post, just looking for any other insight on troubleshooting. Thanks in advance for any direction you can provide. -Ryan

Hi all, I'm a frequent visitor but have never posted. Sorry if this is not in the right place. I've been doing research on diagnostic scanners for my 2007 rlxi. I have an MEFI -5 ECM. There seems to be a lot of info here and on other forums for MEFI 1-4 but for newer ECMs everything seems to point to Rinda https://www.rinda.com . Their products look awesome but are too pricey for me and don't provide an open interface layer. I'm a DIY'er, non-professional, looking to do some basic diagnostics and maybe build some home brew digital gauges. I'm hoping to get a thread going to collaborate on and save info related to MEFI 5,6 and eControls. I have no commercial interest in this project but I would like to recognize a few companies & websites who have a ton of great, open information and products: OBD Diagnostics https://obd2allinone.com/mefi5scan.asp , Copperhill Technologies https://copperhilltech.com/ Elm electronics https://www.elmelectronics.com/ , Bakes https://www.bakesonline.com/bakes-resource-library Here's a start. I'm happy to share more if there is interest in this project. MEFI-5 an newer (including Econtrols) use a CAN bus, 6-pin diagnostic connector, J-1939 29-bit / 250kbps CAN protocol Connector parts and adapter cables can be purchased from OBD diagnostics Most inexpensive OBD II scanners for cars use the ELM 327 chipset (or some derivative or knock off). These scanners can be reconfigured to use the J1939 protocol to read messages on the bus. Inexpensive Arduino boards with a CAN interface from Copperhill can be quickly configured to read J1939 messages using their free code examples The bad news: the magic decoder to translate raw CAN messages to meaningful human readable information is contained in a proprietary SAE standard The good news: Boats are pretty simple and a lot of the important information is out there in manuals and other examples. First I built a wifi black box "flight recorder". So far I've got an arduino due with CAN transceivers from copperhill streaming CAN messages to a raspberry pi zero. I can read things like throttle position, RPM, Coolant Temp, Oil pressure, engine hours etc. I can also pull any stored / pending DTCs (DM2 messages). The same thing can be done with an ELM 327 based scanner (https://www.scantool.net/obdlink-sx/) but instead of using their software for cars just connect to it with putty (any serial terminal emulator will work) on windows or linux.