Fluer de Mer - your problems sound hauntingly familiar. I had some form of each one you mention, although the freezing/rebooting not so often. I'm happy to say that the software
upgrade shipped at the end of 2013, which I didn't install until the spring of 2014, eliminated all the issues. I had a completely trouble free system throughout last season. What a relief and pleasure to have it all working properly after 2 full years of nonsense.
I should point out that all my gear
was first generation Zeus and brand-new-to-market Tritons. I wasn't surprised there were some bugs but it was a bit out of hand. I did a ton of troubleshooting, network re-configuring, and a few unit swaps which seemed to have minor positive affects. But at the same time various software upgrades came out to the Triton, Pilot controller, Zeus, remote
control, and more. So it's impossible to say what was really causing the improvement. At least until the fall 2013 update which did it all.
Once I got proper attention at Navico
they put in a lot of time trying to help me (I went all the way to the president of North America). Most of that was troubleshooting ideas. I felt like I became the most important member
of their QA department. They really tried to pin the problem on my network configuration although it completely fit within NMEA
specs. I use Maretron cables
and connectors, including their multiport junction box, which Navico
was very suspicious of. I got Maretron involved and of course they thought this was hogwash. They also helped in a way Navico never suggested which was to run their N2KAnalyzer on my network. This was fascinating and showed how extremely chatty each B&G device is on the network, especially each of my 8 Tritons, and the potential for many conflicts. Navico never acknowledged this as a problem nor gave me any feedback on the data analysis - but their next upgrade made my problems go away...
I strongly suggest you get a hold of, and a tight grip on, a support tech at Navico over the phone
. Be prepared to send them a full schematic of your system including cable lengths, power sources, etc. You may have fundamental configuration issues that need addressing regardless of what your dealer thinks is right. You have to nail that first. Then it might be a process of elimination finding a potentially bad piece of gear that is polluting your network with enough noise
to cause all your failures.
I'd also recommend running the Maretron analyzer. Your dealer should be able to do it, or to do it yourself unfortunately you need Maretron's expensive N2k to USB converter on your network, then connected to a PC. I had this anyway to give nav data to PC software so I just ran the analyzer and got a complete view of the network traffic. Then a call to Maretron support really enlightened me to what I was looking at.
I'll add one disclaimer to say that all my analysis might be wrong and it wasn't a network noise
problem, but some other bug that was fixed. I could never get acknowledgement of the truth. But my professional experience where I had to deal with small and huge high-throughput networks makes my suspicions very worthy.
Good luck. You'll love this gear when the problems go away.