SmartCraft to NMEA 2000

[Keithc101]

Hello. I have a Mercruiser MAG 350 MPI TOW SPORTS model year 2003 inboard that is SmartCraft ready but currently has analog gauges. I have installed a NMEA 2000 network and a SmartCraft to NMEA gateway (from Mercury). I have found a 10-pin connector at the engine (with a purple weather cap) that fits the gateway plug. I have Livorsi Vantage View gauges ordered but not yet arrived. What's confusing me is whether or not I need a SmartCraft junction between the 10-pin engine connection and the gateway or if I need something else for this conversion. So far, using an Actisense PC gateway and/or a Lowrance LMF-400, I can see no engine data streaming on the network. I see all other sensors on the network including fuel flow and GPS. Any help is appreciated!

[Keithc101]

In case it's needed my Mercruiser serial number is 0M318164 - hopefully will confirm this is SmartCraft ready/compatible.

[EuropeanAM]

Keith:

This is a Smartcraft Compatible engine.

You CANNOT, however, directly plug any Smartcraft Device (including the GATEWAY STICK) directly into the engine.

You MUST have a Smartcraft Network installed. A Smartcraft Network consists of a Can-network Data Cable, and terminating resistors at each end of the network.

If you're only installing ONE Smartcraft Device (the Gateway Stick), a simplified data cable and junction adapter can be used. If MORE THAN ONE device will be installed (such as other System Gauges or Smartcraft Instruments), you will require a JUNCTION BOX at the dash end.

I would strongly suggest contacting a dealer that is knowledgeable in Smartcraft Rigging, to assist you in determining what the appropriate means of rigging up your components would be.

Sherm @ Sherm's Marine (or we) would be happy to assist you with purchase of components.... Email or Phone are the BEST means of contacting the Parts Departments.

[Keithc101]

Don,

Thanks for your response - very helpful. I sent an email to the parts dept as suggested. For others that may find this helpful, I will repeat the info here:

All devices/sensors on the boat (including the Livorsi Vantage View gauges) are NMEA 2000. The only device I will be plugging into the (needed) Smartcraft network is the gateway stick. I'm hoping this conversion will allow me to see as much engine data as possible on the N2k network but, as a minimum, I need rpm, voltage, oil pressure and temperature.


I have, separate from the engine, already plugged into the N2k network, and functioning:


- Lowrance LMF-400
- Lowrance GPS puck
- Airmar depth and temperature sensor
- Offshore systems fuel tank level/volume sensor
- Navlink wifi
- Actisense PC gateway


Currently (evidently incorrectly) plugged into the engine 10-pin junction and NOT functioning - Mercury Smartcraft/NMEA 2000 Gateway stick.


I've ordered Livorsi Vantage View (NMEA 2000 version) gauges including tach, gps speedometer, and combination oil pressure/voltage/temperature/fuel. So, I intend to simply plug the master tach into the N2k network and, hopefully, get the data from the Smartcraft gateway stick.


I'm assuming that installing the data cable/junction adapter is straight forward?

Thanks!

Keith

[Keithc101]

I've ordered the Smartcraft CAN data cable with two termination resistors and a junction connection. Should get everything installed this weekend and will post the results here. Fingers crossed.

[EuropeanAM]

Should be pretty straightforward for you (once you receive the components).

Make sure the data cable is installed as marked (engine end AT engine).

[Keithc101]

All worked great - getting all the engine data now. Except - for the fuel gauge (using Livorsi Vantage View gauges). My network system includes an Offshore Systems NMEA 2000 Fuel tank level sensor.


The problem is that the fuel gauge bounces between full and empty. The engine gateway (even though there is no tank sensor connected to the SmartCraft engine) includes a tank level PGN that broadcasts a 0% - empty level (I can see this on my connected computer using an Activision gateway/reader). The offshore systems fuel tank sensor transmits (correctly) a 100%-full level. The Livorsi gauge seems to be alternately reading both the engine gateway and tank sensor levels and therefore bounces between empty and full. When I disconnect the SmartCraft gateway stick, the fuel gauge correctly reads full - no bouncing. I've tried to change the Tank 1 / Tank 2 settings options on the Livorsi tach menu but no luck in getting the bouncing fuel gauge to stop. Any ideas on how I can correct this? Obviously, leaving the gateway unplugged is not an option since that transmits all the other engine data displayed on the gauges. I've tried changing the fuel sender "instance" settings switch on the Offshore Systems sending unit from 0 to 4- no luck. I have it set to transmit fuel tank level %.


Any ideas on how I get the Livorsi gauge to show only the sending unit level and ignore the state way stick tank level broadcast? The tank sending unit is a NMEA 2000 certified device.

[Wildcat Dude]

I would contact Livorsi - prior to that - check the sender's ground wire. Livorsi Marine- Contacts

[Keithc101]

There is no (separate) ground wire on the sending unit - since it is a NMEA standard screwed connection. I have sent an email to the Livorsi sales tech support shown on their website. Given that Don is very familiar with the Mercury gateway and that Livorsi is a common gauge used with Mercury systems, I am hoping he has the magic bullet...

[lfb6]

Well, if I picked the right manuals, you could try to change the "instance" of your fuel sensor to another value (#4 in the manual), maybe then you'll be able to set up the right sensor in "Setting Fuel Tank Data Source" in the Livorsi Speedo (page 47), it seems both senders have the same identification?

Manuals used
http://www.osukl.com/senders/UM/3271-UM.pdf
http://www.livorsi.com/pdf/vantage/l...structions.pdf

Just an idea....

[EuropeanAM]

You would need to set up the sources (and ignore the ENGINE fuel tank data) within your GPS system.

This is one of the drawbacks of a Gateway Stick- it simply transmits ALL available data (you have no means of configuring, calibrating, or turning data "on" or "off"). Those are functions found in the Smartcraft Instruments, such as the Level-1 or higher MercMonitor... Vessel View-4, or Vessel View-7.

[Keithc101]

Don - one idea I have heard is that I need to install resistors on the engine fluid level 1/2 wires. I had just cut and capped the previous analog fuel level sending unit wires when I replaced the unit with the NMEA 2000 version. Think that might do it? If so, where would I get the resistors? I'd hate to have to replace the $$ NMEA fuel sender with an analog version.

[lfb6]

Again: Have you configured the instance of your fuel sensor?

[Keithc101]

Yes. The sender allows up to 10 tanks (0 to 9 instance setting switch on unit). I tried 0 through 4 before giving up.

[Keithc101]

I'm wondering if just cutting/sealing the old WEMA sending unit wires was incorrect? Should I just ground the black wire or should I put a 120 ohm resistor between the black and purple wires?

[EuropeanAM]

Don - one idea I have heard is that I need to install resistors on the engine fluid level 1/2 wires. I had just cut and capped the previous analog fuel level sending unit wires when I replaced the unit with the NMEA 2000 version. Think that might do it? If so, where would I get the resistors? I'd hate to have to replace the $$ NMEA fuel sender with an analog version.

Installing resistors on these wires would only "fool" the PCM into sending a tank level signal relative to the resistance on the circuit.

You would still have an erroneous reading being transmitted (and will likely still see the cycling you're experiencing currently).

There should be a means of turning off specific NMEA-2000 data inputs.... Livorsi should be able to assist you with that.

[Keithc101]

That's what I thought. Working with Livorsi now. Yay for kicks I'll hook up a test rheostat to the wires and see what happens...
the resistor idea was Luvorsi's.

[EuropeanAM]

Be sure to report back on your findings.... this is an unusual installation (and it's always good to learn from such situations).

[Keithc101]

Won't be able to get to it until this weekend - but will report findings

[lfb6]

Yes. The sender allows up to 10 tanks (0 to 9 instance setting switch on unit). I tried 0 through 4 before giving up.

I'm sorry to have asked you again, you already wrote that in an earlier posts- did oversee it. Not sure if the first 4 were enough to stop trying. If you search Mercury for information on the gateway software you can find that the gateway is capable of transmitting:

- Level information for Fuel1, Fuel 2, oil, water, waste (5 sensors) and as the Smartcraft gateway is capable of multi (<4) engine setups it might be even more.

Personally I would try a higher instance number like 8 or 10 on the fuel sensor and see what happens.


If that doesn't work: You mentioned the Actisense PC gateway and that you're able to decode the traffic on the bus:

The engine gateway (even though there is no tank sensor connected to the SmartCraft engine) includes a tank level PGN that broadcasts a 0% - empty level

Can't you check your system for the instances used by the Smartcraft gateway and the instance used by your Offshore-sys fuel gauge?

Your situation now is that values of different sensors are alternately displayed on one single gauge- either two sensors with same instance on the bus or the Livorsi device not properly differentiating between them. Possible causes:

- The Offshore systems fuel gauge doens't change the instance as expected, sending still PGNs with the same instance as the Smartcraft gateway

- The Smartcraft gateway is blindly sending PGNs with instance information for more sensors that expected (actually all it is capable of, might be 5 or more)

- The Livorsi system does not correctly distinguish between sensors with different instances

It's essential to know what happens on the bus and which instances send PGNs with level information. That's the only way to find out who's to blame for this mess.