After I wrote the last post I spoke with a very helpful guy at B&G who explained a bit about the N2k/Fastnet bridge (H5000 Fastnet Interface). It would appear that it should be supplying more data to our N2K network than it is, which suggests our H2000 Performance processor isn’t correctly configured – which isn’t a huge surprise. He explained that the data transmission rates on Fastnet is much lower than N2K and they’d not bridged data to avoid swamping the Fastnet bus. I’m not sure that really makes sense – as a throttled feed of the data that they’ll already let you inject onto Fastnet from an old serial NMEA0183 source (such as a GPS set) would cause no more trouble than the current feed – and be rather simpler on a boat moving towards more modern tech, where a GPS upgrade to an N2K device has probably already happened. Anyway that’s how it is. It leaves me with a job to look at the config of our performance processor.
I did source a rather expensive but fairly pristine pilot remote on eBay, which worked perfectly. That gave me the confidence to take the old one apart. I found that one of the screws that hold the circuit board down had become loose and was lodged under the board. Once it was back in the right place all worked well again, so now I’ve got a spare. Whilst reassembling it I did replace the lanyard attachment point – it had always been broken and having a way of tethering it has always seemed a good idea. I was able to 3d print a replacement, which pleased me.
In order to provide the data feed to the Saillogger platform that provides the tracking I use here I’ve been running SignalK on the Cerbo GX display/processor that manages the Victron battery kit. It’s part of Victron’s supported configuration and the Cerbo is connected to the boat’s N2K network so has access to all the boat’s data. Signalk is really very neat – it’s an open source modern http based data sharing platform, which supports plugins to connect to all sorts of things, and when combined with Node Red workflows can be used to build all sorts of automation and monitoring.
My first step will be connecting the Cerbo to allow monitoring the the bilge pump and an high level bilge alarm. Because the Cerbo is always running and internet connected (ours uses the boat’s network or falls back to a cheap IoT mobile dongle) that means I can get flooding alerts whilst the boat is unattended.
Longer term I’m thinking that the sensible thing to do would be to create a Fastnet SignalK module. The SignalK platform can manage the translation to N2K – or wherever else – and it would allow all the Fastnet devices to be used for as long as they work. I also wonder about an Expedition/SignalK interface – that seems to be a match made in heaven with all the data Expedition makes available.