[alnav]

Here's how I understand (or guess) are the differences:
- The gateway provides just engine info for a NMEA 2000 network. No fault codes or ability to configure stuff like fuel tanks.
- VesselView Link converts all data including fault codes and converts it to NMEA 2000. Same data available to chart plotters as the gateway. But, only a VesselView (or Simrad) unit can show additional data such as fault codes and configure.
- Smartcraft Connect, although details are murky, provides the above, but, with software upgrades by either RayMarine or Garmin, the plotter will be able to display all info including faults and be able to configure. So, no more need for dedicated VesselView units. I am guessing here but the projected cost and the fact that the MFD providers are announcing software support leads me to believe this is how it's going to work out.

 

[alnav]

My understanding (misunderstanding?) Is that there aren't N2K PGNs for every SmartCraft fault code, so an MFD won't have them available to it if the source of data is purely N2K.

Have a look at this manual for the gateway from the Mercury website: https://samerwebapp01apncus01.azure...7/92/b792d09c-af9d-4e5e-b2fc-737dab9e098d/smartcraft_connect_gateway_manual.pdf.

This is what is indicated regarding alarm data:
"NMEA 2000 alarm data is limited and will only display "Check Engine" when an alarm is activated. Refer to the Mercury SmartCraft Gauges for descriptive fault text."

I am guessing the VV Link provides the full set of N2K data and adds proprietary SmartCraft data that MFDs that support the VV Link (Simrad, I assume) can display.

I don't know any of this for sure, however, there are other on here that do, I believe.

Baj, not sure how they do it, but, looking at the architecture of the VesselView Link, the inputs come from the Smartcraft harness but the only output is NMEA 2000. I suspect they have either crafted proprietary PGN's, or as Tom may be suggesting, sending J1939. NMEA 2000 is something of a descendant of J1939 anyway and the message structure is pretty much the same.
So, the current VesselViews (and Simrads) must have software that is able to use the data coming over NMEA 2000. Now, I think Raymarine and Garmin are going to update their software to do the same. It could also be that the new Smartcraft Connect will be doing further conversions that are being done in VesselViews now.
The net result would be (if I'm correct) that nothing would be needed to configure, operate and monitor Smartcraft engines other than the Connect and a capable chart plotter. I think I would go for that and recoup the dash real estate used by VesselView today.

 

[alnav]

Here's what the new Garmin display is going to look like:

 

[alnav]

This helps a little. Not sure why the vv link doesn’t work with garmin

I'm sure VV Link "works" with Garmin today, but only to the extent that it transmits standard NMEA 2000 PGN's. I think what Mercury is referring to is the fuller integration with Smartcraft that the new SC Connect provides in conjunction with the software changes Garmin (and RayMarine) are going to provide.

 

[alnav]

That I'm not completely sure about. When the boat gets back in the water I can easily short the exhaust temp sensor and see exactly where it alarms; I know for sure it displays a message on the VV7 but don't know about the Garmin MFD's or Maretron devices.... The Garmin and Maretron displays show all engine parameters as well as the CAN H parameters (fuel levels, etc)

That will be a good test. One of the fields on the standard engine screens is an alarm. I think it's the equivalent of a "check engine light" and would come on if there is a fault (I think there is a binary NMEA PGN for fault). I assumed that would be it and the exact fault would need to be found on VV.
I was looking for a picture of the alarm in the 84XX/8600 series manual. Couldn't find it but there is a section on the Yamaha gauges that Garmin has recently integrated; looks like full functionality and probably where Mercury integration will end up.

 

[alnav]

I happened on the installation manual for the Connect: https://samerwebapp01apncus01.azure...-4dae-466f-9c37-6c4adcb2ddfc/smartcraft_connect_gateway_installation_manual.pdf

My highlights:
- Single connections to Smartcraft J-Box (or engine harness) and NMEA 2000
- Wifi is only for connecting to an app (also already on App store) for configuration and firmware update. Bluetooth not mentioned but I assume it's an alternate way to connect to the app.
- CAN H is only for steer-by-wire systems (Zeus, etc.). DTS will operate over CAN P.
- WRT alarms, states: "NMEA 2000 alarm data is limited and will only display "Check Engine" when an alarm is activated. Refer to the Mercury SmartCraft Gauges for descriptive fault text." Not sure if this means no other manufacturers' connected product will be able to display faults or not.
- No substantial mention of integration with other NMEA 2000 devices other than a PGN list.

 

[alnav]

Do you agree with the CAN H description? I don't or something has changed over the last couple of years; I know for sure that (on the Cummins powered boats) the DTS is through the engine's ECM and out via J1939 which is CAN P......

Oops. Typo on my part. It should have said "DTS will operate over CAN P." I've edited the original post to correct. So, for purposes of the Connect, CAN P is the primary path for everything except Zeus and other joystick applications.