New electronics. Nmea 2000. Multiplexer etc

Only if you're mixing and matching Raymarine and other suppliers NMEA2000​ equipment. You can connect the Shipmodul multiplexer to the SeaTalkng backbone with a Raymarine adapter cable. I'm in a similar position with several Raymarine bits and pieces for historic and bargain purchase reasons.
 
Sorry i meant if i have raymarine ng and also standard nmea2000 i might have 2 backbones?

Still no Rob. NG is basically N2K with oddball Raymarine connectors. You can connect NG kit together using Raymarine cables, connect standard N2K kit together to form a N2K network then join the two backbones together by splicing a N2K cable to a NG cable.
 
You've just said "no - but yes". Unless Rob has other non-Raymarine NNEA2000 kit he only needs a single Seatalkng backbone with an adaptor cable for a Shipmodul multiplexer. This is where some DIY cables could be useful...
 
Sorry i meant if i have raymarine ng and also standard nmea2000 i might have 2 backbones?

I've successfully mixed and matched Seatalk ng and standard DeviceNet (NMEA2000) - including a ShipModul Multiplexer. As others have said, it is only the physical cables that are different.

Edit: Saw there was a bit of a debate going on. I can confirm I've got a ShipModul Multiplexer, Raymarine Autopilot & displays, garmin GND10 & GMI20 and an Actisense NGW-1 all successfully working on a single N2K bus. The backbone cable is Seatalk ng - if doing it again I would probably mix Seatalk ng and standard DeviceNet to form the backbone.

One advantage of the ShipModul Multiplexer is that there are regular updates available with new functionality which are easy to install.
 
Last edited:
I've successfully mixed and matched Seatalk ng and standard DeviceNet (NMEA2000) - including a ShipModul Multiplexer. As others have said, it is only the physical cables that are different.

Edit: Saw there was a bit of a debate going on. I can confirm I've got a ShipModul Multiplexer, Raymarine Autopilot & displays, garmin GND10 & GMI20 and an Actisense NGW-1 all successfully working on a single N2K bus. The backbone cable is Seatalk ng - if doing it again I would probably mix Seatalk ng and standard DeviceNet to form the backbone.

One advantage of the ShipModul Multiplexer is that there are regular updates available with new functionality which are easy to install.

I think i'll be buying a Shipmodul and selling the vYacht, i'd like to set my VHF/AIS to N2K. Curious if i could make calls from OpenCPN and AIS, any idea ?
 
I think i'll be buying a Shipmodul and selling the vYacht, i'd like to set my VHF/AIS to N2K. Curious if i could make calls from OpenCPN and AIS, any idea ?

I've thought about selling the vYacht too (I don't have WiFi on the ShipModul and use a tablet with OpenCPN over USB but I find I rarely make use of the vYacht WiFi).

The ShipModul Multiplexer will now translater AIS sentences. I haven't tried making calls to AIS targets from OpenCPN. In any event it's a doddle with the SH radio and I'll probably be fitting one of the RAM mics over the winter.
 
I've successfully mixed and matched Seatalk ng and standard DeviceNet (NMEA2000) - including a ShipModul Multiplexer. As others have said, it is only the physical cables that are different.

Edit: Saw there was a bit of a debate going on. I can confirm I've got a ShipModul Multiplexer, Raymarine Autopilot & displays, garmin GND10 & GMI20 and an Actisense NGW-1 all successfully working on a single N2K bus. The backbone cable is Seatalk ng - if doing it again I would probably mix Seatalk ng and standard DeviceNet to form the backbone.

One advantage of the ShipModul Multiplexer is that there are regular updates available with new functionality which are easy to install.

So why do you need the actisense? I thought everything could go in to the Shipmodul?
 
You've just said "no - but yes". Unless Rob has other non-Raymarine NNEA2000 kit he only needs a single Seatalkng backbone with an adaptor cable for a Shipmodul multiplexer. This is where some DIY cables could be useful...

It's not two networks, or even two separate backbones. It's a powered N2K network, with a NG cable extending the backbone to allow for the connection of NG equipment without using multiple adapter cables. All NG and N2K equipment will share all of the data.
 
I've thought about selling the vYacht too (I don't have WiFi on the ShipModul and use a tablet with OpenCPN over USB but I find I rarely make use of the vYacht WiFi).

The ShipModul Multiplexer will now translater AIS sentences. I haven't tried making calls to AIS targets from OpenCPN. In any event it's a doddle with the SH radio and I'll probably be fitting one of the RAM mics over the winter.


I'm thinking about getting the wifi version, as i do use the wifi side of the vYacht to send data to a laptop and a tablet.
 
It's not two networks, or even two separate backbones. It's a powered N2K network, with a NG cable extending the backbone to allow for the connection of NG equipment without using multiple adapter cables. All NG and N2K equipment will share all of the data.

Ok got it. Apart from the physical convertor cable it is one nmea2000 network.
 
Ok got it. Apart from the physical convertor cable it is one nmea2000 network.

There are some useful docs on the NMEA website. e.g. https://www.nmea.org/Assets/2012 ibex full nmea installation.pdf

So for example, it is not necessary to have an expensive STNG to DeviceNet convertor cable per box. You can run a normal DeviceNet T-Piece or two to connect several standard N2K items to one convertor cable to connect to the STNG backbone.

Within reason (i.e. you're not running a cable up the mast) the main thing to worry about is voltage drop. Maretron do a simulator to build a network (free download) which is very good, but naturally restricted to Maretron components so a little restrictive. I ended up producing a little spreadsheet which worked out the LEN supported on the wire between each node of the network (i.e. instrument/junction etc.) and so could calculate the voltage drop to every item on my N2K network.

A group purchase would be a good idea. Unfortunately for that, I'm almost complete now.
 
So for example, it is not necessary to have an expensive STNG to DeviceNet convertor cable per box. You can run a normal DeviceNet T-Piece or two to connect several standard N2K items to one convertor cable to connect to the STNG backbone.

My suggestion, which is just one solution, was to build a 0183 network as normal, then at the "last" T connector fit a cable with a devicenet connector at one end and NG connector at the other, from the NG end build what would normally be a NG network, but without the power cable and terminate with a NG terminator. The cable could be made by cutting a NG cable and fitting a devicenet connector to the end or by splicing half a devicenet cable to half a NG cable. Standard N2K or NG equipment could then be added/removed at will.
 
My suggestion, which is just one solution, was to build a 0183 network as normal, then at the "last" T connector fit a cable with a devicenet connector at one end and NG connector at the other, from the NG end build what would normally be a NG network, but without the power cable and terminate with a NG terminator. The cable could be made by cutting a NG cable and fitting a devicenet connector to the end or by splicing half a devicenet cable to half a NG cable. Standard N2K or NG equipment could then be added/removed at will.

Are you thinking of having a part DeviceNet backbone and part STNG backbone? If starting again I would probably do that. I saw a box (Actisense I think) for joining two backbones and having several spurs off it. Of course you don't need to splash out on such a box and could just use terminal blocks as a very short stretch of unshielded cable isn't going to be a killer for N2K. My thinking behind using the box was more a matter of avoiding the installation looking homemade.
 
Are you thinking of having a part DeviceNet backbone and part STNG backbone? If starting again I would probably do that. I saw a box (Actisense I think) for joining two backbones and having several spurs off it. Of course you don't need to splash out on such a box and could just use terminal blocks as a very short stretch of unshielded cable isn't going to be a killer for N2K. My thinking behind using the box was more a matter of avoiding the installation looking homemade.

Actually in my case I was only really asking as i was looking at b&g triton. But tbh I may as well just get all raymarine as the ev100 looks good for me. Then a shipmodul to add in the ais from the radio and broadcast on wifi and i am good to go.
 
Are you thinking of having a part DeviceNet backbone and part STNG backbone? If starting again I would probably do that. I saw a box (Actisense I think) for joining two backbones and having several spurs off it. Of course you don't need to splash out on such a box and could just use terminal blocks as a very short stretch of unshielded cable isn't going to be a killer for N2K. My thinking behind using the box was more a matter of avoiding the installation looking homemade.

I'm not, i suggested it in response to Robs questions. I'm almost all N2K, apart from the autopilot and wind, which are both stand alone. The VHF/AIS is either, currently set to 0183 for the benefit of the vYacht. With a wifi Shipmodul i'd set the VHF/AIS to N2K and possibly add in the autopilot and wind. Everything is then available on the laptop, tablet and three 4" displays in the cockpit.
 
From memory there has been a firmware upgrade a few months ago, so it will do simultaneous TCP and UDP. But in my opinion it is the best multiplexer and NMEA0183/2000 converter around. If it's Wi-Fi doesn't meet your needs, you could get the basic multiplexer from them and have a look at this (which I'm involved with): https://www.kickstarter.com/projects/nmeawifi/nmea0183-wi-fi-device
 
Top