Here's a design that neatly shows how N2KBuilder can be used with non-Maretron devices. If Jon Kinne entered the right LEN values into the properties of those various Airmar, Simrad, and Actisense boxes, then N2KBuilder's current and voltage calculations should be about right. But that might change if Jon takes my suggestion of dropping the multiport and just using one Devicenet-to-Simnet patch cable in the NavPod, with two short SimNet cables daisy chaining to the other instruments. I'm confidant that such a cabling system will work fine for this network, but note that N2KBuilder does its calculations based on the sort of certified N2K cable that Maretron sells, and non-certified cable doesn't necessarily have the same power and data carrying abilities.
Jon's N2B file is here, and he describes the system thusly:
"Here is the diagram of my new proposed N2K network aboard Indigo. I
will use the terminator built into the PB200, and the multiport will be
in the NavPod at the helm. I only need 60' of the Airmar cable to run
down the mast, and the extra will be used to connect the backbone to
the NavPod (12' max). The NGW-1 will take 0183 sentences coming from my ShipModul multiplexer
and translate them to 2000 for the N2K instruments. The MUX receives
input from a Garmin GPS, DSC information from the VHF and communicates
with Nobeltec Max-Pro VNS via USB."
This is the diagram of the system that is now complete, and about which I posted an hour or so ago in response to Ben's Simrad/N2K lead article today.
Jon Kinne
s/v Indigo
Island Packet 37
Forgot to mention that I did indeed take Ben's suggestion and eliminated the multiport at the NavPod, and used two short SimNet cables to daisy-chain the three instruments together. Works very well!
Jon Kinne
s/v Indigo
Island Packet 37