Grace’s updated network for 2017

I originally posted a fairly lengthy article outlining Grace’s integrated network about a year ago, but it is a work in progress and constantly changing. There have been some updates that I wanted to cover which will help the network continue to grow and expand, as well as fixes for problems I found.

Grace's electroniGrace's electronics as of June 2017

Grace’s electronics as of June 2017 – click for a larger version

I’ve updated the network diagram to include the changes as well as more detail on the Internet Alcove and the new Radar Arch.


There were several problems with the 2016 design which caused reliability and accessibility challenges.

Accessibility – the majority of the NMEA 2000 network was behind the navigation station panel where all the instruments are mounted, which required removing it every time I had to work on the network. This caused lots of extra work to be able to unscrew and carefully remove the panel without tripping breakers, pushing buttons, or damaging anything. I am currently in the process of designing a new panel using Front Panel Express which will condense all of the devices, swap out the factory electrical panels with more compact BlueSea solutions, and hinge the whole thing for ease of access. This isn’t 100% done yet, but it is one of the top things I am changing.

Squished –  I used standard NMEA 2000 taps off the backbone in this area, and by the time I made it through the 2016 season, there were too many back-to-back to fit in the space!

Power problems – the dual power setup I discussed in Grace’s integrated network was causing headaches and major reliability issues, with parts of the bus unable to see the other devices at random times depending on what was powered up when.


Removal of dual power sources – instead of powering things for the “always on” part of the network from the Maretron tap, and the rest of the devices from the Raymarine tap at the helm, I now have one power source – the Maretron tap. This means that everything goes on all at once, but it has solved the weird power fluctuations and device disappearing problems.

I liked having a section of devices that I could leave on all the time and access remotely, but the weird interactions caused outages during navigation which were dangerous. To achieve this same result, I can manually power down individual instruments and leave others on, with the exception of things like tank sensors and depth transducers.

4 port NMEA 2000 connector block

4 port connector block – I purchased three of these to add to key parts of the network – two for behind the navigation panel. I considered a version from ActiSense, but they are hard to find and expensive. I also considered the ActiSense QNB product I used on Jammy, but it had too few ports and was a bit bulkier than I’d like. I may still do this later this year and move some taps around as I like having a single device for the drops and the power, all integrated and sealed.

iKommunicate – this was added last year shortly after the network was updated and I did a review of the product. It has become one of the primary ways I get data off the network on a smart phone or tablet.

Depth/speed/temp – the old Raymarine ST60 speed sensor started failing late in 2016. I replaced the depth sensor (the speed sensor is a funky non-standard size) with a Maretron DST110 smart tri-ducer which includes depth, speed, and temperature. This is a no brainer for anyone with a NMEA 2000 network needing to update/replace any of those three sensors. Pretty much plug and play as long as you have a NMEA 2000 tap nearby.

Raymarine i70s instruments

Raymarine i70s / p70s instruments – as part of the depth sensor change out, the old ST60 instrument at the helm stopped working since it was reliant on dedicated wires providing the data to the unit from that sensor. Thankfully, even after 15+ years, the holes for the ST60 are identical to the new Raymarine i70s, so replacing them was pretty easy. I chose to hide the ST60 wind instrument under the helm, as it is still gathering data from the mast mounted instrument and transmitting it onto the NMEA 2000 network via the Seatalk1 converter. Eventually I want to replace the masthead device with a NMEA 2000 or wireless solution.

The i70s are a leap forward compared to the old ST60’s of course, and it is nice to be able to display all sorts of different info depending on the “mode” that the boat is in – navigating, docking, anchored, etc. – instead of static displays. I have configured lots of different data panels depending on these modes, and love the visibility they provide.

I also replaced the autopilot head with the p70s to make all three instruments consistent in look and software. The autopilot head has some minor updates from the original but otherwise is pretty close.

SmartThings – this was added to help manage temperature and security and I covered it in SmartThings keeps the boat warm during winter. It required a connection via ethernet to the internet.

Arlo Security Cameras – this was just recently added, and I’ll write more about it soon. Like the SmartThings hub, the Arlo hub requires an ethernet connection to the internet. I really wish manufacturers would go away from this, but I understand that for security and such you would want reliability.

Grace radar arch

Grace radar arch

Radar & Radar Pole / Arch – this was a big project which I still plan to write about very soon. I added a Raymarine Quantum radar on top of a Garhauer radar pole and arch. It sounds so simple when said that way, but the planning and execution for the pole installation was quite intense. There were a lot of cables from other devices mounted on the arch, and things that had to shift around to make everything work. The radar itself is a fantastic addition to have for visibility, and has come in handy on several trips already.

Vesper AIS move – prior to heading up to the San Juans in this year’s first longer trip, I had to move the Vesper AIS. This was partly because I was having problems with my VHF radio and removed the splitter I had put in place last year as a temporary solution. I also wanted a dedicated VHF antenna like I had on Jammy, and was able to do this with the new radar arch. I have seen significant improvements in the quality of my AIS antenna signal as a result of a dedicated, properly terminated antenna.


The next big change is the installation of a Raymarine Axiom chart plotter, and a B&G Vulcan 5 chart plotter (more of an instrument given the size) at the helm. This requires a new NavPod shell, and moving some things around including the H50 wireless radio.

There are a few other small projects I have planned for the rest of the year such as adding a display in the main stateroom so I can see random data when awoken at night, a new tank sensor for the waste tank and maybe fuel tank.

You Might Also Like...

3 thoughts on “Grace’s updated network for 2017”

  1. Steve – I’m enjoying your experiences (just signed up today 7/7) as I am performing many of the same feats that you have either completed or are contemplating. I went with a Garmin 1042xsv chartplotter and the Vesper AIS XB-8000 for my first purchases and have started eliminating the former ’98 Raymarine stuff, including the radar. The autopilot can’t seem to get power yet either but it’s old too. This is all on our “new-to-us” (NTU) 1998 Bayliner Avanti 3685 that we just purchased. Price was right, size was right, now to get all the stuff to work. . . . . Oops, should’ve mentioned – maiden voyage issues: installer apparently used one too many connections on the negative buss (per mechanic) so the Garmin wouldn’t power up because the engine room blower was on . . ? .really? Went back to dock and they “fixed” it . . then found out the Vesper wasn’t getting full power but we were way too far away to fix it at the time . . . and then, you guessed it . . lost oil pressure on one of the 454’s (380HP) which proceeded to blow oil all over my cleaned engine bay . . . they can down and trucked it back to the yard to fix it . . . . can you say “I’m loosing the season here!” . . . grrrr. Oh well, keep writing, I’m enjoying it (since I can’t boat).

  2. From the looks of your diagram you’ve attached a Maretron backbone cable (which I believe uses a DeviceNet connector) and hooked it up to a spur port (could well be a backbone port, but on your diagram it appears to be going into the centre of the hub) on the SeatalkNG 5 way hub. How’ve you managed that? Did you end up hacking the cable and attaching a SeatalkNG end connector to a standard Maretron cable?


Leave a Comment