I have a complete NN3D system that was installed in 2010. Components are an MFD8, DRS4D, GP-330B, DFF1 and HUB-101. Also have a SCS200 compass on the N2K network. All are installed on a 2008 Parker 2530 that is trailered and stored indoors. The boat power is Yamaha F150s with the command link square gauges. I also have the Yamaha N2K gateway to provide engine data to the MFD8. I'm also using the NMEA 0183 output on the MFD8 to provide speed, temp and time information to command link through the Speed gauge (blue and white wires).
This system has worked flawlessly since installation. A month ago while fishing I noticed that the NMEA 0183 data to command link was intermittent. Speed would flash 199 mph then go back to normal. It did this several times until there was no GPS speed data (or time or temp) received by command link. I removed, checked and reconnected all NMEA 0183 and NMEA 2000 connections, ethernet connections, misc. connections behind the dash and checked all the fuses. I'm using Port 1 on the MDD8 to provide NMEA0183 data to CL.
Took the boat again and everything worked except for no speed, temp and time data was being received by command link. All NavNet components worked. The following day after cleanup and putting the boat away I started up the MFD8 to clean up some waypoints and the MFD8 stated up with no connection to any devices except the compass which is on the N2K network. All ethernet devices were X'ed out (GPS, DRS and DFF). I ran the wizard and it did not see any devices. I can understand why the GPS was X'ed out because I was in the garage.
I backed up my data, did a master reset and installed software 2.13 (I had 2.07 previously). Restarted the system and still no communication among the ethernet devices. I played around with the connections at the HUB by swapping ports, etc. and eventually started up the MDF8 where it recognized everything. Just to make sure the GPS was working I borrowed a cable from a friend and hooked it up directly to Port 1 on the MFD8 and put it outside and it worked fine. Note that getting the system to recognize everything took several restarts and running the wizard. But in the garage it appeared everything was communicating.
Took the boat out again for some testing and once again on MDF8 startup there was no connection among the devices. Ran the wizard and nothing, no DFF1, no radar, no Yamaha gateway, no compass, no GPS. Shut down and restarted and ran the wizard again, and again. After the third time it finally started up and recognized everything. With a new problem being that there was no normal fish finder display. DFF1 was blinking every two seconds, MFD8 showed OK for the sounder, but no viable info on the display. Putted around for three hours trying different things but could not get anything to happen with the fish finder.
So now back home in the garage I borrow a friends FCV600L and a P66 transducer he just had on the shelf. Put the transducer in a barrel of water and with the FCV600L I get a good signal. Hook up the DFF1 to the P66 in the barrel and zip, the same screen I had on the water. Hook up the FCV600L to the B117 thru-hull in the boat and I get a good signal. So I send the DFF1 off to Furuno for diagnosis.
To deal with the NMEA0183 to CL problem I'm assuming that maybe Port1 on the MFD8 has failed somehow. So I've switched over to Port3 for my NMEA0183 to CL data but have not had the boat back in the water to test it yet. A question I have is if the CL system receives and displays NMEA0183 data if the engines are not running (w/ key on)?
Meanwhile all this quircky, glitchy stuff with the system is still bothering me. Note I had not made any changes to anything related to the NN3D, N2K or NMEA0183 networks prior to the problem. And although it seems like I've got everything talking, it's not very reassuring since I did not find anything wrong (except the DFF1). Having everything working, shutting down, and then on the next restart seeing things X'ed out is not very confidence inspiring. My Furuno love at this point is being majorly tested.
Any advice, suggestions, information, etc. would be greatly appreciated.
This system has worked flawlessly since installation. A month ago while fishing I noticed that the NMEA 0183 data to command link was intermittent. Speed would flash 199 mph then go back to normal. It did this several times until there was no GPS speed data (or time or temp) received by command link. I removed, checked and reconnected all NMEA 0183 and NMEA 2000 connections, ethernet connections, misc. connections behind the dash and checked all the fuses. I'm using Port 1 on the MDD8 to provide NMEA0183 data to CL.
Took the boat again and everything worked except for no speed, temp and time data was being received by command link. All NavNet components worked. The following day after cleanup and putting the boat away I started up the MFD8 to clean up some waypoints and the MFD8 stated up with no connection to any devices except the compass which is on the N2K network. All ethernet devices were X'ed out (GPS, DRS and DFF). I ran the wizard and it did not see any devices. I can understand why the GPS was X'ed out because I was in the garage.
I backed up my data, did a master reset and installed software 2.13 (I had 2.07 previously). Restarted the system and still no communication among the ethernet devices. I played around with the connections at the HUB by swapping ports, etc. and eventually started up the MDF8 where it recognized everything. Just to make sure the GPS was working I borrowed a cable from a friend and hooked it up directly to Port 1 on the MFD8 and put it outside and it worked fine. Note that getting the system to recognize everything took several restarts and running the wizard. But in the garage it appeared everything was communicating.
Took the boat out again for some testing and once again on MDF8 startup there was no connection among the devices. Ran the wizard and nothing, no DFF1, no radar, no Yamaha gateway, no compass, no GPS. Shut down and restarted and ran the wizard again, and again. After the third time it finally started up and recognized everything. With a new problem being that there was no normal fish finder display. DFF1 was blinking every two seconds, MFD8 showed OK for the sounder, but no viable info on the display. Putted around for three hours trying different things but could not get anything to happen with the fish finder.
So now back home in the garage I borrow a friends FCV600L and a P66 transducer he just had on the shelf. Put the transducer in a barrel of water and with the FCV600L I get a good signal. Hook up the DFF1 to the P66 in the barrel and zip, the same screen I had on the water. Hook up the FCV600L to the B117 thru-hull in the boat and I get a good signal. So I send the DFF1 off to Furuno for diagnosis.
To deal with the NMEA0183 to CL problem I'm assuming that maybe Port1 on the MFD8 has failed somehow. So I've switched over to Port3 for my NMEA0183 to CL data but have not had the boat back in the water to test it yet. A question I have is if the CL system receives and displays NMEA0183 data if the engines are not running (w/ key on)?
Meanwhile all this quircky, glitchy stuff with the system is still bothering me. Note I had not made any changes to anything related to the NN3D, N2K or NMEA0183 networks prior to the problem. And although it seems like I've got everything talking, it's not very reassuring since I did not find anything wrong (except the DFF1). Having everything working, shutting down, and then on the next restart seeing things X'ed out is not very confidence inspiring. My Furuno love at this point is being majorly tested.
Any advice, suggestions, information, etc. would be greatly appreciated.