VesselView 7 cuts out

Shaps

Well-Known Member
GOLD Sponsor
Nov 4, 2019
2,455
Long Island,NY
Boat Info
2010 Sundancer 500
2015 Brig Falcon 330T
Engines
Twin Cummins QSC550 w Zeus Pods
This started happening a couple of weeks ago.

Randomly, my VesselView 7 will cut out. It essentially does a quick reboot, not a full power on/reset. Has only happened at the dock once or twice. I spoke to mercury who said the only way that happens is power is being interrupted and to check the power leads.
Well those wires go into a big plug and all seemed fine.
Also, at the same time, my smartcraft gauges all shut down and then come back to life.
The whole process is usually over between 5-10 seconds but it is majorly disconcerting.

I've dug in under the helm, and cannot seem to find any loose connections whatsoever.
Spoke to my mechanic who suggested the j-block (i am assuming he means the smartcraft junction block) may be going bad. Has anyone heard of this happening? Is there a way to test a junction block?

Thanks!
Shaps
 
Hmmm 2010 - there were quite a few changes between my Smatrcraft and yours. However, the gauges are driven by the VesselView 7 so if the VesselView blinks the gauges will blink. Power for the Smartcraft system including the VV7 comes from the engines in two forms. One is SmartCraft power that is on all of the time (uninterrupted) and one is the ignition switch wakeup signal. Each engine provides the uninterrupted power and the wakeup signal is provided by both ignitions but combined into a single input into the VV7. So, if power was truly interrupted the VV7 should completely reboot and you should see the initial Mercury splash screen and that long bootup sequence ending with the safety "Accept" screen. If this is not happening then I suspect there is a software glitch happening. You can go into the menu and do a complete system reset; however, it will be necessary to set up all of the engines and parameters in the system.
 
Thanks Tom. I am getting the splash message, but NOT the full on accept message.
I am a bit paranoid about doing a full reset on the vesselview.
Isn't there a 'personality file' i need that only the cummins guys have access to?
 
Thanks Tom. I am getting the splash message, but NOT the full on accept message.
I am a bit paranoid about doing a full reset on the vesselview.
Isn't there a 'personality file' i need that only the cummins guys have access to?
Good question - Mine shows "Troll" all of the time and has the Troll RPM sweeps that neither I nor Cummins can get rid of that they believe is a Cummins artifact.... So, there may be something of a personality file but it must be well hidden or this comes from the engines. With that said they installed a new VV7 in my boat after the lightning strike and still that Troll mode shows.
I think that no matter how the system is programmed as to it's function it shouldn't reboot. I would suggest that the first test would be to simply activate it with one ignition switch and watch it without the engine running then do the same with the other. If for example the reboot happens only on one engine then probably the wake circuit; If on the other hand it happens with either ignitions on or both on then either a Smartcraft power problem or there is truly an issue with the VV7 unit.
 
I agree with Tom, if it is not doing a full reboot you have a software issue. You might want to insure you have the latest software also.

https://www.mercurymarine.com/en/us/gauges-and-controls/gauges-displays/vesselview/software/

I had a MFD that was shutting down and found it was getting too hot as there is no air moving back there. So to extend the life of my eletronics I drilled a 2" hole in the AC distribution box to pump some cold air in that area as there is no circulation currently. Made a big difference
 
Will try that Tom. Thanks

I still think I can get rid of that troll mode for you. In my experimenting with the menu I have seen it.
I will look again this week and post it.
Dumb question from me... Any harm in leaving the ignition key on for any length of time without the engines running?

Interesting Grant.. I was pretty sure it was the latest and greatest software but i'll triple check. Thank you!
 
Also agree with Tom and OC. With your Zeus and DTS I think you have a lot more configuration data than those of us with just engine data. Does your VV have either a USB port or an SD card slot? I think from either of those you can make a copy of the configuration which would be the equivalent of a "personality file". You may want to try to do that soonest in case your symptoms get worse.
 
@alnav
Pretty sure I have a microSD slot. Good call on the backup. Thank you!
 
There should be no issues with leaving the Ign on and the engine not running. I don't believe we have an electric fuel boost pump (my QSM11 doesn't) and the heat in the ECM (cooled by fuel) is mostly generated by operating the injector solenoids and that shouldn't be an issue. An hour to two for sure won't hurt. I can't answer for your DTS and drive requirements however.
 
Thanks Tom. Appreciated

Any opinion on the smartcraft jbox being the issue? or pretty sold on software

Will try and report back.
 
Thanks Tom. Appreciated

Any opinion on the smartcraft jbox being the issue? or pretty sold on software

Will try and report back.
Dave,
Just to rule out a "weak" connection remove all connections on the jbox, inspect for corrosion and plug them all back in and test it. I have found some pins on connectors get corrosion and cause issues. You would be amazed how corrosion can travel through wires. I have seen some stuff in cars that amazes me so for sure boats have issues. I had an old Ghost alarm on my boat from the PO, didn't work found the GPS antenna on the roof cracked, chased the wire all the way back to find the alarm brain and when I unplugged it found the water corrosion into the antenna had gotten all the way down the wire and corroded the main board some 20+ feet from the antenna. You should see what a bad coolant sensor does in a car when it is compromised and electricity is applied to glycol.
 
Thanks Grant.
I'll do that. Crazy stuff!
 
When I first got my boat, the dealer told me to always start the starboard engine before the port because doing the opposite caused Smartcraft problems in their experience. I've always followed that advice. Since your problem has only occurred at the dock, I'm wondering if there's a chance your problem might be related to start sequence?
 
@alnav
apologies if i didnt explain it well.
It rarely happens at the dock, but happens when underway. It is inconsistent, whether we are in calm seas or not.

Edit:
Good safety tip on the stbd side first... I'll try anything.
 
When I first got my boat, the dealer told me to always start the starboard engine before the port because doing the opposite caused Smartcraft problems in their experience. I've always followed that advice. Since your problem has only occurred at the dock, I'm wondering if there's a chance your problem might be related to start sequence?
That's interesting. I'd like to know the root of that.... Regardless from a wiring perspective it shouldn't make a difference. Typically, the extras on the boat are on the Starboard engine's wire harness; things like steering angle, depth, paddlewheel, etc if your boat does use these features via Smartcraft. The port wire harness also has plugs for these features. I do know that the SIM modules on the engines cannot be exchanged between engines. But, the Port engine is incidence 0 in all things data; go figure....
 
Checked the connections as best i could, no corrosion i could find. No loose connections either. Tried gently moving any of the connectors and could not reproduce the shutdown. On the advice of my cummins guy, i did a full fullpower shutdown, waited 5 minutes and restarted.
Then, i tried to download the personality file. Bought a brand new microSD card, formatted it, inserted it and... The VesselView would not see the card. Not sure why. Is there some setting that either locks out the card reader or enables it? Mercury was closed when I got to this point.

I am starting to think the vv7 may be on the way out... ugh
 
I found this last night and thinking I recall seeing the camera box checked. I'm guessing the PO had something at some point as I don't have a camera installed. Going back tonight to (un)check it and will report back to just close this out. HOPING!

Still doesn't answer why I can't see the microSD card.

vv7_camera.PNG
 
@Shaps The new SD card you purchased.....is it the proper "Class" for the VV? When I was setting up my Garmin MFD, I wanted the biggest, baddest, fastest SD card I could buy. I bought an uber fast card. Sadly, it wasn't compatible with the MFD. Had to drop down a class in speed, but that fixed the issue.

Jaybeaux
 
@Shaps The new SD card you purchased.....is it the proper "Class" for the VV? When I was setting up my Garmin MFD, I wanted the biggest, baddest, fastest SD card I could buy. I bought an uber fast card. Sadly, it wasn't compatible with the MFD. Had to drop down a class in speed, but that fixed the issue.

Jaybeaux

The manual didn't specify a speed or size, so i bought something middle of the road.
I am hoping you're right. I'm going to call mercury and ask them what specs are for the microSD card. Would be great if it was that simple!
Tks @Jaybeaux
 
I found this last night and thinking I recall seeing the camera box checked. I'm guessing the PO had something at some point as I don't have a camera installed. Going back tonight to (un)check it and will report back to just close this out. HOPING!

Still doesn't answer why I can't see the microSD card.

View attachment 107645

Sometimes they are just not compatible :( I had this with my Axioms - 2 SD cards both same size & specs - the Axiom liked one brand but would not even see the other.

-Kevin
 

Forum statistics

Threads
112,944
Messages
1,422,715
Members
60,927
Latest member
Jaguar65
Back
Top