roblpm
Well-Known Member
No, NMEA 0183 isn't on a backbone, it's just pairs of data wires connected between devices.
Sorry i meant if i have raymarine ng and also standard nmea2000 i might have 2 backbones?
No, NMEA 0183 isn't on a backbone, it's just pairs of data wires connected between devices.
Sorry i meant if i have raymarine ng and also standard nmea2000 i might have 2 backbones?
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.
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 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.
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...
So why do you need the actisense? I thought everything could go in to the Shipmodul?
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.
I fitted it first. Haven't yet prioritised removing it and putting it on the for sale section.
Ok got it. Apart from the physical convertor cable it is one nmea2000 network.
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.
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.