Multi Function Gauge NMEA 2000 output issue

[ChrisLong1985]

I have a DF175 with the Multi Function gauge (model number 34200-96L00) and I am having issues receiving engine data on the NMEA 2000 network.

Does this particular gauge model output all engine data to the NMEA 2000 network?

Currently I am only receiving engine RPM on the network to my Garmin 7412xsv unit.

The other issue is in the device list of the Garmin, the Suzuki shows up as "unknown" and drops in out of the list every few seconds.

Thanks

[Harper]

The multi-function gauge does not output any information, so your Garmin unit does not receive info from your multi-function gauge. It receives the info from the same place that your multi-function gauge receives it, namely the DF175 itself via the engine interface. So both units are receiving the same information from the same source. In other words, you should be able to receive all information from the engine on your Garmin, even if you don't have a multi-function gauge in your network. The mf gauge is used to configure and calibrate the engine interface, because you are not able to do this with your Garmin.

Set your mf gauge, using the instructions in your operators manual, to receive what data you want to see on the mf gauge and/or the Garmin. That same info will show up on your Garmin. If it doesn't show up on the Garmin, but does on the gauge, then you have a bad connection to the Garmin unit, or the Garmin unit is not properly set up. If what info you are trying to receive also does not show up on the mf gauge, then it's possible that you have a failed engine interface or bad NMEA 2000 backbone or connection, assuming you have configured everything properly with the mf gauge. Before assuming any bad interface, you should double check all connections on the NMEA network, including the power connection. Once you get everything working, then you can read what info you want to on your Garmin and on your gauge, or read some information on the garmin and different info on the gauge. They do not have be kept both reading the same info.

You don't indicate what year your DF175 is, but what data it should output without any additional add-on sensors are: RPM, engine temp, engine hours, engine voltage, engine trim, and fuel flow.

[ChrisLong1985]

The multi-function gauge does not output any information, so your Garmin unit does not receive info from your multi-function gauge. It receives the info from the same place that your multi-function gauge receives it, namely the DF175 itself via the engine interface. So both units are receiving the same information from the same source. In other words, you should be able to receive all information from the engine on your Garmin, even if you don't have a multi-function gauge in your network. The mf gauge is used to configure and calibrate the engine interface, because you are not able to do this with your Garmin.

Set your mf gauge, using the instructions in your operators manual, to receive what data you want to see on the mf gauge and/or the Garmin. That same info will show up on your Garmin. If it doesn't show up on the Garmin, but does on the gauge, then you have a bad connection to the Garmin unit, or the Garmin unit is not properly set up. If what info you are trying to receive also does not show up on the mf gauge, then it's possible that you have a failed engine interface or bad NMEA 2000 backbone or connection, assuming you have configured everything properly with the mf gauge. Before assuming any bad interface, you should double check all connections on the NMEA network, including the power connection. Once you get everything working, then you can read what info you want to on your Garmin and on your gauge, or read some information on the garmin and different info on the gauge. They do not have be kept both reading the same info.

You don't indicate what year your DF175 is, but what data it should output without any additional add-on sensors are: RPM, engine temp, engine hours, engine voltage, engine trim, and fuel flow.

Thanks for your response. I have a better understanding now.

All engine data on the Suzuki multi-gauge are working correctly. Even when the NMEA plug is disconnected from the back of the gauge, all engine data on the gauge is still recognised and functioning correctly. That's why I thought the gauge outputs engine data to the NMEA network.

Other devices plugged into the NMEA network backbone (GPS) are recognised on the Garmin unit without issues. For some reason the Suzuki isn't recognised correctly and drops in and out off the device list on the Garmin.

The engine is a 2015 model.

[ChrisLong1985]

The multi-function gauge does not output any information, so your Garmin unit does not receive info from your multi-function gauge. It receives the info from the same place that your multi-function gauge receives it, namely the DF175 itself via the engine interface. So both units are receiving the same information from the same source. In other words, you should be able to receive all information from the engine on your Garmin, even if you don't have a multi-function gauge in your network. The mf gauge is used to configure and calibrate the engine interface, because you are not able to do this with your Garmin.

Set your mf gauge, using the instructions in your operators manual, to receive what data you want to see on the mf gauge and/or the Garmin. That same info will show up on your Garmin. If it doesn't show up on the Garmin, but does on the gauge, then you have a bad connection to the Garmin unit, or the Garmin unit is not properly set up. If what info you are trying to receive also does not show up on the mf gauge, then it's possible that you have a failed engine interface or bad NMEA 2000 backbone or connection, assuming you have configured everything properly with the mf gauge. Before assuming any bad interface, you should double check all connections on the NMEA network, including the power connection. Once you get everything working, then you can read what info you want to on your Garmin and on your gauge, or read some information on the garmin and different info on the gauge. They do not have be kept both reading the same info.

You don't indicate what year your DF175 is, but what data it should output without any additional add-on sensors are: RPM, engine temp, engine hours, engine voltage, engine trim, and fuel flow.

I also forgot to mention I am from Australia, because a different gauge is issued here compared to the US, is that correct?

[Harper]

I also forgot to mention I am from Australia, because a different gauge is issued here compared to the US, is that correct?

Yes that's correct. But I think it is pretty obvious now that your problem is with the Garmin unit only, either with the network connection to it, or in your setup, or with the instrument itself.

That being the case, I doubt that there's much more that we can help you with here. You're going to have to check your connection and work with Garmin.

[ChrisLong1985]

Yes that's correct. But I think it is pretty obvious now that your problem is with the Garmin unit only, either with the network connection to it, or in your setup, or with the instrument itself.

That being the case, I doubt that there's much more that we can help you with here. You're going to have to check your connection and work with Garmin.

No worries, thanks for your help Mike

[pfirmin]

Based on this thread, post number #38, you have the wrong gauge.

http://www.suzukioutboardforum.com/s...mea2000-4.html

He mentions that 34200-96L00 i for installations not requiring networking. While 34200-96L10 is for Nmea2k networks. I can check later and see exactly which gauges were installed on my boat. I have twin 2016 DF250AP and am located in Bahrain. Mine was literally plug and play. My garmin 7410xsv recognized both engines the second I turned the key on. The gauges also pick up the gps signal from the garmin to show speed and my coordinates and compute mileage.

[Moonlighter]

Correct, that was pointed out to the OP on another forum....

I have updated the "sticky" thread at the top of this forum with a note to that effect.