Victron GX now sends NMEA 2000

Victron has had a lot of impressive connectivity products, but one area they have had challenges with is in getting all of that data onto NMEA 2000. In their recent v2.40 release, that has changed for the better.

Victron GX now sends NMEA 2000

It’s no secret that I love Victron’s control ecosystem. On my last three boats, I’ve had Victron bits that have helped provide visibility into the power system. Earlier this year, I finished the conversion on Rendezvous to a mostly-Victron system which I wrote about in Victron + Wakespeed + Battle Born power system.

One of the glaring holes in Victron’s communication has been with NMEA 2000. In particular, their GX-series of devices has had very limited capabilities – in fact, they have only been able to receive information from the NMEA 2000 network, and only tank information. It was nice to be able to see tank levels on their devices, like the Color Control GX, but most people with NMEA 2000 tank level stuff already have ways of displaying that.

There were various other NMEA 2000 interfaces you could get from Victron, but those were specifically for controlling devices, and as a side effect, you got some info from those devices on NMEA 2000. I had the VE.Direct to NMEA 2000 interface, commonly used between a battery meter or solar charge controller, and I also had the VE.Bus to NMEA 2000 interface, used between an inverter/charger and other devices. However, using these had drawbacks – some features weren’t available unless you used native Victron busses.

Enabling NMEA 2000

Victron VE.Can to NMEA 2000 cable

You’ll need to be running v2.40 or later of Victron’s GX software – they released v2.41 recently that addressed some initial bugs in the NMEA 2000 support. I’m using a Color Control GX for these examples, but it also works for other GX products like the Venus, etc.  You will also need a VE.Can to NMEA 2000 cable, available through Victron resellers for about $95 US. I purchase my Victron stuff from PKYS.

When you install the VE.Can cable, you’ll need to make sure your VE.Can network has a terminator (should have been provided with the GX product you have) and if you have an existing, powered NMEA 2000 network, remove the fuse from the cable so you don’t create a short circuit.

Once you have the cable connected, in the Settings -> Services menu you will find an option for CAN-bus.

Once inside the CAN-bus menu, using the default profile, and turning the “Send data to VE.Can” on should get traffic flowing to your NMEA 2000 network.

Examining the NMEA 2000 traffic

Maretron N2Kanalyzer showing Victron devices

I have the following Victron devices:

I also have several MPPT solar controllers but they aren’t installed yet. These devices provide all of their wealth of data to the Color Control GX, and it now is sending out data to my NMEA 2000 network.  You can see four devices listed above – the MultiPlus is listed twice.

The Color Control GX shows up as a device but doesn’t send any electrical PGNs as it is just the device facilitating the communication for the other devices.

Battery Data

The BMV-712 is sending two useful PGNs – 127506 and 127508.

PGN 127506 – DC Detailed Status includes the state of charge (SOC) and time remaining. The other values do not appear to change or have data in them.

I have two batteries being monitored by my BMV-712 – my house bank is connected to the shunt and is considered battery instance 0 above, and the generator battery is connected to the second monitoring point only for voltage and shows up as instance 1.

I now have battery voltage, battery current, state of charge and time remaining for my house bank, battery voltage for my generator battery all on the NMEA 2000 network. This was the primary info I wanted so that when I was elsewhere on the boat I could see the state of the house bank at a glance.

Inverter / Shore Power Data

The data being sent out for the MultiPlus is a bit different. There are two NMEA 2000 devices.

Actisense device display

The Actisense NMEA Reader displays what the two MultiPlus devices are and shows that one is utility/shore, and the other is the output.

MultiPlus inverter on shore power

Here’s what they look like when I am on shore power. You can see both devices have data from AC power sources, but the right one shows a much higher value. I assume this is my water heater or other devices that aren’t on the inverter side of the circuit – just the AC pass through.

MultiPlus inverter on battery power

Here’s what they look like when I am on battery power with the inverter running AC loads. The right device is showing zero values, indicating that shore power is gone/off.

MultiPlus inverter charger, inverter, and battery status

The above shows the left hand device, or 000502, which is the inverter side of things, but the PGNs for charger status, battery status, and inverter status.  The charger and inverter status are useful, and pass along to other devices on the network to show the general state.

The battery PGN is good to have too, if you don’t have a BMV or other device monitoring your battery state. Unfortunately, there’s no way I’ve found to configure instance IDs, so this battery status PGN conflicts with the one being sent by the BMV.

The right hand device also has a bunch of proprietary PGNs which I assume would be used to exchange more detailed info that Victron needs to track, or perhaps control devices via NMEA 2000 that are Victron specific.

Data is good

Finally having battery and inverter data on the NMEA 2000 network is wonderful. Being able to see the state of my electrical system on the various Maretron DSM displays around the boat, and especially on the MFDs while underway is very convenient. It gives me clear visibility into what is going on with the system, and I can use the various alarms and alerts to help augment what Victron has. I also like having this data being logged constantly to my Yacht Devices Voyage Recorder so that I can analyze performance and any issues later on.

It took a while for Victron to add this support, but I’m glad it’s finally here.


Archived Comments

These are read only comments from the old system. Scroll down to participate in SeaBits Discussions, our new interactive forum attached to each article.

Greg Davydov
January 4, 2020 at 12:48 pm
Hi Steve,
Do you know how Victron N2K data interfacing with SignalK?

  • Steve Mitchell
    January 4, 2020 at 10:25 am
    I think you’re asking how you can interface Victron N2K data within SignalK? By default, any N2K data will show up in SignalK if you have it configured with an N2K interface. You’ll see all of the various messages there that are on the NMEA 2000 network.
    However, if you do not have the NMEA 2000 cable for the GX product, you can use a plugin by Scott Bender to pull the information over the Ethernet/WiFi network directly from the GX product: https://github.com/sbender9/signalk-venus-plugin
    I used this plugin for several years before the NMEA 2000 support came out. It pulls a ton more data from the GX product than NMEA 2000 does, but it is only visible in SignalK unless you use another plugin to send it out to other networks, which can get more complicated.

Jurjen Hoekstra
January 7, 2020 at 1:45 pm
Hello Steve, what is the advantage of the Venus GX compared to a setup with a VE-Direct to NMEA2000 converter and a VE-Bus to NMEA2000 converter? Is there now more data available on the NMEA2000 which one can display? I have a set-up with a VE-Direct and VE-Bus converter on my motoryacht Xanthiona and am considering the Venus GX, but do not see yet how it would benefit. I use SeaSmart ethernet module to publish the NMEA2000 data for the purpose of remote monitoring to the HelmSmart cloud service. One thing the service does not distinguish between is the shore power and the output power. See also: http://www.xanthiona.com

  • Steve Mitchell
    January 7, 2020 at 1:36 pm
    You likely see the same (or more) data on your NMEA 2000 network that you would with a Venus GX. So you probably wouldn’t see any more data on your NMEA 2000 network, although it sounds like you don’t see both sides of the AC stuff which you would with the new firmware. The few advantages I can think of are as follows:
    First, Victron has said they are deprecating the interfaces you’re using, so there could be new PGNs or firmware updates to products that those interfaces no longer support.
    Second, as you cover in your post on your site, is the integration with Victron’s VRM portal that the Venus GX has. This would allow you to control and monitor the electrical system via their portal/apps instead of SeaSmart. I’ve demoed SeaSmart before, and I think you would have more control in general over your Victron components with the VRM than SeaSmart.
    Third would be the additional AC data.

Discussion

Thoughts and comments on this article: