Diesel View / Vessel View Upgrade

[ttmott]

Note the Smartcraft section on the far left. The Port GPH and Starboard GPH is the only page/section that seems to be pulling from the port engine. The section on the middle shows different data for the Port and Starbord GPH which is more realistic.
Mercury said that section averages the two together. Not sure I buy it. See their response see below also…

“Richard here is the response I got back from my Smartcraft guy. “The simple answer is it’s a matter of averaging data. The graph on the right is Navico/Simrads and the graph on the left is mercury’s. We ave differently then they do”
Darryn Laitinen
Diesel Product Support Specialist


View attachment 143955

Interesting - the total in the left area equals the sum of the two in the right but not the sum of the two in the left.
Is the Stbd in the left area really the Stbd? Could be something in the setup that needs adjustment.

 

[rlynch03]

Interesting - the total in the left area equals the sum of the two in the right but not the sum of the two in the left.
Is the Stbd in the left area really the Stbd? Could be something in the setup that needs adjustment.

I keep thinking it is a set up issue but have not found it yet…

 

[Shaps]

We have 44 sedan bridge. I have updated to VesselView 7.03 . Does it show engine load like the smartcraft sc5000.
Our boat is a 2006 QSC 500’s

Load is available in the list.

 

[RBB]

My guy made this screen for me

 

[HarrisonAlt]

Here is the treasure map... You need the VV703 dual engine kit and then order the harnesses highlighted in this map. You will remove the old medusa harness and install this as well as a Nema2K network if you don't currently have on.
View attachment 97016

If I want to run 1 VV per sc5000 (2) do I still need a dual engine model? Or will 2 singles be fine?

 

[HarrisonAlt]

And did anyone happen to archive any of the 100 attachments that are now defunct? I'm about to tackle this project and I feel like I'm going in blind with no photos or diagrams

 

[rlynch03]

If I want to run 1 VV per sc5000 (2) do I still need a dual engine model? Or will 2 singles be fine?

Are you planning to keep the SC5000 and add a new Vessel View?

 

[Shaps]

Mercury sent these to me.
Mercury customer support was very helpful. I would call them to confirm what you require for the correct rigging.

 

[alnav]

Attaching a Sea Ray Smartcraft drawing. Also a Cummins drawing for the QSB install which should also be mostly applicable to any diesel Smartcraft setup; gets down to the pinout level should that be needed.

 

[HarrisonAlt]

Are you planning to keep the SC5000 and add a new Vessel View?

View attachment 155378

I wanted to get rid of the SC5000s and throw a pair of Axiom 7+ in their place and use vesselview through then

 

[ttmott]

I wanted to get rid of the SC5000s and throw a pair of Axiom 7+ in their place and use vesselview through then

A couple of things -
VesselView is a device to view data not data nor a data network. Smartcraft is a data system which entails a data hardware system/network, viewing devices, engine and vessel interfaces, and the data language/translators. Smartcraft is actually three CAN data networks. A SC5000, Diesel View, or VesselView are devices to view data on the Smartcraft network.

Assuming your engines are Mercury Smartcraft enabled and are later than 2003 then the helm gauges are probably Mercury System Link. Your SC5000 provides the data link to the gauges. What that means is the helm gauges will not operate without a SC5000, Diesel View, or Vessel View.

To view Smartcraft data on an Axiom or other MFD it must be converted to NMEA 2000. Much of the engine data on the Smartcraft network is not "translatable" onto a NMEA 2000 network that a MFD/Chartplotter interfaces. Most importantly engine faults will not be on the NMEA 2000 network.

Hope this helps...

 

[ocgrant]

They have come a long way with the new Axiom and Vessel View app on the Axiom. I don't know how deep it goes but here is a sample

Mercury Vessel View at MIBS | Raymarine

Check out a Freeman boat equipped with Mercury Marine Vessel View at the 2022 Miami International Boat Show.

www.raymarine.com

 

[alnav]

A couple of things -
VesselView is a device to view data not data nor a data network. Smartcraft is a data system which entails a data hardware system/network, viewing devices, engine and vessel interfaces, and the data language/translators. Smartcraft is actually three CAN data networks. A SC5000, Diesel View, or VesselView are devices to view data on the Smartcraft network.

Assuming your engines are Mercury Smartcraft enabled and are later than 2003 then the helm gauges are probably Mercury System Link. Your SC5000 provides the data link to the gauges. What that means is the helm gauges will not operate without a SC5000, Diesel View, or Vessel View.

To view Smartcraft data on an Axiom or other MFD it must be converted to NMEA 2000. Much of the engine data on the Smartcraft network is not "translatable" onto a NMEA 2000 network that a MFD/Chartplotter interfaces. Most importantly engine faults will not be on the NMEA 2000 network.

Hope this helps...

Tom, the newer Smartcraft Connect device does convert engine fault data and transmit those data to the network. I believe it's in proprietary PGNs so not exactly NMEA 2000, but both Garmin and Raymarine MFDs are able to read the data and display it. There may be some data elements missing but I don't know of any.

 

[ttmott]

I wanted to get rid of the SC5000s and throw a pair of Axiom 7+ in their place and use vesselview through then

A couple of things -
VesselView is a device to view data not data nor a data network. Smartcraft is a data system which entails a data hardware system/network, viewing devices, engine and vessel interfaces, and the data language/translators. Smartcraft is actually three CAN data networks. A SC5000, Diesel View, or VesselView are devices to view data on the Smartcraft network.

Assuming your engines are Mercury Smartcraft enabled and are later than 2003 then the helm gauges are probably Mercury System Link. Your SC5000 provides the data link to the gauges. What that means is the helm gauges will not operate without a SC5000, Diesel View, or Vessel View.

To view Smartcraft data on an Axiom or other MFD it must be converted to NMEA 2000. Much of the engine data on the Smartcraft network is not "translatable" onto a NMEA 2000 network that a MFD/Chartplotter interfaces. Most importantly engine faults will not be on the NMEA 2000 network.

Hope this helps...

Tom, the newer Smartcraft Connect device does convert engine fault data and transmit those data to the network. I believe it's in proprietary PGNs so not exactly NMEA 2000, but both Garmin and Raymarine MFDs are able to read the data and display it. There may be some data elements missing but I don't know of any.

Interesting - I can't get any of that data on my Garmin displays. There must be a Mercury/Garmin or Raymarine S/W data agreement on how to display right? The connect device must be newer than I have; is it the Link converter?
But then again I've never had an engine fault other than a low battery voltage when cranking.

 

[ocgrant]

Here is some more info for Raymarine

Mercury VesselView | Marine Engine Integrations | Raymarine

Mercury Vesselview for Raymarine provides captains with access to detailed information about the status and operation of their Mercury SmartCraft compatible marine engines. Find out more here.

www.raymarine.com

8M0222354.pdf

mercurymarine.widen.net

 

[alnav]

Interesting - I can't get any of that data on my Garmin displays. There must be a Mercury/Garmin or Raymarine S/W data agreement on how to display right? The connect device must be newer than I have; is it the Link converter?
But then again I've never had an engine fault other than a low battery voltage when cranking.

Smartcraft Connect is the name. It came out about 3 years ago. Mercury, Garmin and Raymarine did a joint rollout announcement. I believe it was meant to obviate the need for a Vessel View or other Smartcraft displays on newer, glass panel sans gauges. Garmin (and I think Raymarine) mimics the VV display with Mercury marks on the MFD screen (which is only available when the Connect is detected). I got one when they first came out. It took several months to install because only a dealer could access the app which completes the install (that has since been changed). But, I found that the Connect would misbehave when a Vessel View was also connected. I needed to use both to preserve my Link gauges to one of your earlier points. So, mine is sitting behind my dash disconnected. I'm hoping this has been fixed and I mean to test mine again when I can.

 

[alnav]

Here is some more info for Raymarine

View attachment 155570

Mercury VesselView | Marine Engine Integrations | Raymarine

Mercury Vesselview for Raymarine provides captains with access to detailed information about the status and operation of their Mercury SmartCraft compatible marine engines. Find out more here.

www.raymarine.com

8M0222354.pdf

mercurymarine.widen.net

Here's a similar page from Garmin: https://support.garmin.com/en-US/?faq=8JFTtJielR8Yny4BXb83z9. Garmin will throw an alarm along with the name of the fault code so seems to be a bit further along than Raymarine in that regard.

 

[ttmott]

Smartcraft Connect is the name. It came out about 3 years ago. Mercury, Garmin and Raymarine did a joint rollout announcement. I believe it was meant to obviate the need for a Vessel View or other Smartcraft displays on newer, glass panel sans gauges. Garmin (and I think Raymarine) mimics the VV display with Mercury marks on the MFD screen (which is only available when the Connect is detected). I got one when they first came out. It took several months to install because only a dealer could access the app which completes the install (that has since been changed). But, I found that the Connect would misbehave when a Vessel View was also connected. I needed to use both to preserve my Link gauges to one of your earlier points. So, mine is sitting behind my dash disconnected. I'm hoping this has been fixed and I mean to test mine again when I can.

Now that's an interesting quandary. A Vessel View puts no data back on the networks other than the data feed to the gauges (separate wires/network); I would doubt that Connect puts data on the networks either. Does Connect interface with all three CAN networks? If you are still using CAN 3 and it is interconnected with the displays and you have the Maretron J2K100 generator setup (I think you did this mod) then the Maretron pings the generator over that network. Just a thought....

However, now that I think about it - Every device tags the network with an ID; Smartcraft is no difference other than devices connected to the System Integration Module and Engine ECM.
Does Connect and Vessel View possibly use the same ID data stream on the networks?

 

[alnav]

Now that's an interesting quandary. A Vessel View puts no data back on the networks other than the data feed to the gauges (separate wires/network); I would doubt that Connect puts data on the networks either. Does Connect interface with all three CAN networks? If you are still using CAN 3 and it is interconnected with the displays and you have the Maretron J2K100 generator setup (I think you did this mod) then the Maretron pings the generator over that network. Just a thought....

However, now that I think about it - Every device tags the network with an ID; Smartcraft is no difference other than devices connected to the System Integration Module and Engine ECM.
Does Connect and Vessel View possibly use the same ID data stream on the networks?

I believe the vision is for the Connect/MFD to eventually take over all the legacy VV functions across all CANs. Stuff like trim and troll as well as Zeus controls that you and I don't use must involve signals from the VV, so that may be it. Good idea to check on the ID data stream. I wonder if that can be changed somewhere deep in the VV configuration menus; maybe I can mod the VV ID which might de-conflict the two units. I see in the latest Garmin SW update that there is a way to ID separate helm stations, making one look like a lower helm and the other a fly bridge might do the trick as well.