Buy Suzuki Outboard Parts

Announcement

Collapse
No announcement yet.

NMEA 2000 Network Issue

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • NMEA 2000 Network Issue

    Hello friends,
    I just installed a N2K net on my 2004 Pro-Line with 2016 DF175. The engine had analog gauges which were replaced with SMIS gauges during installation. I switched the engine connectors as instructed in Suzuki Bulletin 004 of August 15, 2007. The net has these nodes:

    Suzuki Engine Monitor – software version 3.5.0-MZ1620C-B.1.0
    Suzuki SMIS 4” Gauge – software version 2.6.0 MZ1454
    Suzuki SMIS 4” Gauge – software version 2.7.3 MZ1583
    Garmin 742xs GPSmap - software version 8.60

    I have 2 issues:
    No engine data is being displayed on either the gauges or the Garmin, although all nodes report the engine monitor is on the network. Data from the Garmin is being displayed on both gauges.
    The gauges don’t list 2016 as a model year selection, so I selected 2015 DF175 on both.

    I’m not sure how to resolve the missing engine data, although I suspect a software versioning issue. I’d sure appreciate some direction. Thanks.

  • #2
    Did you have a Chance to read the "Sticky" thread on the list above (fifth one down on the list)?

    Moonlighter posted this sometime backp

    Comment


    • #3
      Yes, I followed his directions. One difference, however, is that Suzuki bulletin 004 referenced above uses the existing engine-to-dash analog cable by switching connections at the engine.

      Comment


      • #4
        Note: The engine interface cable (990C0-88149-350) has 3 connections: a NMEA 2000 that connects to a N2K T, a 4-pin male that connects to the digital (previously analog) cable from the engine, and a 4-pin female that is apparently unused as I could find no matching connection behind the dash.
        Last edited by thissenw; 05-20-2017, 11:56 AM.

        Comment


        • #5
          Moonlighter is expert to the wiring problems if he doesn't see your question on a day of so send him PM

          Comment


          • #6
            I was looking at the interface cable descripton and is says (Adapter Cable also needed for DF150G/175G/250AP/300AP applications.) It did not list a part number. Did you have to get an adapter cable?
            Henry

            Comment


            • #7
              The only cable I bought is the engine interface cable (P/N 990C0-88149-350). I believe the adapter cable is only needed when analog gauges are used. I replaced them with SMIS digital gauges.

              Comment


              • #8
                I was curious, because of the extra 4 pin plug. I thought possibly the adapter may connect the SMIS to the female connector on the interface cable instead of the male one. Idk though.

                If you have access to a SDS, you should be able to connect it to your harness at the console and get motor functions. This would verify that the wiring, connector, and the digital signal is good to that point.

                Moonlighter has alot of knowledge with N2k networks, Installation, setup, software versions needed and what will and won't work. Hopefully he will chime in, or PM him as art stated.
                Last edited by Nayna32; 05-21-2017, 01:30 PM.
                Henry

                Comment


                • #9
                  Should work as youve got it set up as stated, if physical connections are all good.

                  Since you can see the engine interface on the SMIS gauges Bus device list and Garmin device lists, it would seem that connections are OK, this one has me baffled.

                  Btw you dont need to set engine hp on the SMIS displays - it is automatically detected. Even if you did select it, you would only need to do it on one SmIS because its a network setting and doing it on one gause sets it across all. And, it will revert to what was there anyway.

                  The only thing I can suggest is that the different sw versions on the 2 SMIS displays may be an issue. But you cant change sw versions unless you have a Lowrance/Simrad display on your network. I suppose the other thing is that the SMIS displays are pretty well past their "use by" date and they are becoming increasingly problematic with the new motors.

                  Try taking the SMIS displays off the network (just unplg them), and see if you get any engine data in the Garmin. Remember engine key mist be turned on.

                  Comment


                  • #10
                    Turns out the switched 12v connector I selected to power the net drops to 10.1v after a short time. I connected it to a steady 12v supply, and engine hours are now displayed on both gauges and the Garmin. I can’t run the engine without water, but it looks encouraging. I noticed that engine trim isn’t updated on the Garmin as I tilt the engine. It’s not even a selectable option on the gauges. I think I read someplace that the unused 4-pin female connector on the engine interface cable is used for a trim interface. How can I activate this parameter? Thanks so much for your help.

                    Comment


                    • #11
                      Good work on finding the problem - I will remember that low voltage to the network causes data dramas, good to know!

                      The trim data on 2016 motors comes thru the main harness, not via the extra 2 pin connector on the interface.

                      Does trim position show on the SMIS gauges? It should.

                      If so, it must be an issue with the Garmin, perhaps data sources? Or setup?

                      Comment


                      • #12
                        Did a test run today, and found the issues listed below. There’s apparently a conflict between the V2.73 SMIS software and the V3.50 engine interface software for my 2016 DF175. My question is should I back-level the 2.73 gauge to V2.60, or upgrade to a later version? If later, what version should I download, and where might I find it? Is there a fix for the bouncing trim value? Thanks for your help.

                        Fuel flow displays on the V2.60 gauge and the Garmin. Not on the V2.73 gauge.

                        Fuel economy displays on the V2.60 gauge and the Garmin. Not on the V2.73 gauge.

                        Fuel range displays on the V2.60 gauge and the Garmin. Not on the V2.73 gauge.

                        Engine volts displays on the V2.60 gauge and the Garmin. Not on the V2.73 gauge.

                        Engine temp displays on the V2.60 gauge and the Garmin. Not on the V2.73 gauge.

                        Engine hours displays on the V2.60 gauge and the Garmin. Not on the V2.73 gauge.

                        After engine trim calibration, the value displays on all devices, but it bounces wildly, so as to be unusable.

                        Comment


                        • #13
                          Change 2.7 gauge to 2.6.0.

                          re the trim, not sure, hopefully someone else will chime in.

                          Comment


                          • #14
                            Hi Moonlighter,
                            Took my boat to the dealer and asked that they flash both gauges to V2.70 as specified in this doc: Suzuki | LOWRANCE | Marine Electronics. Long story short, they said they had computer issues and couldn't do it for a few days. Got me wondering, if I installed a C10 gauge, could it be used to flash the 4" SMIS gauges? Thanks.

                            Comment


                            • #15
                              Yes. C-10 has a USB port so you can attach a card reader and upload software changes to the network.

                              Be careful when updating SMIS software. If they are all connected to the network at the time the software is uploaded, it will attempt to update all SMIS gauges on the netwoek simultaneously - and will crash/fail. So you should disconnect all except one SmIS gauges and do that one, then dsconnect it, connect the next one, and do that. Etc.

                              Comment

                              Working...
                              X