Raymarine Live Short Cuts: SeaTalk NG Networking

[@jimwiddowson9879]

Very good instruction - I am upgrading from Seatalk instruments to Seatalk NG and you have taken all the anxiety out of the upgrade - I now feel confident to proceed with upgrades. Thank you

[@RaymarineInc]

Thank you for watching!

[@caspian007007]

Jim, Thanks for the great video. It was a great introduction explaining the structure of the NG Canbus system. It really answered a lot of questions and helped me sort out a wiring strategy for my boat. Much appreciated!

[@RaymarineInc]

Glad it was helpful! Thank you for watching.

[@Matt-lu3pw]

Another great very informative video. I think your videos are one of the main reasons I have decided to upgrade to new Raymarine equipment for my boat. Having now watched many of your videos I feel almost familiar with the lighthouse user interface which clinched my decision to upgrade to the new axiom MFDs and cyclone radar rather then choosing another brand. I’m not aware that any of your competitors produce this sort of detailed content that you do. I look forward to tuning in and learning. Thank you. 👍

[@RaymarineInc]

Thank you for the very kind words, for watching the show, and for sticking with Raymarine for your boat.

[@redtide941]

Great video. I just got a salvage boat with a mix of nmea, seatalk and seatalk NG instruments and this really helped me figure out what's going on

[@RaymarineInc]

Glad it helped!

[@robhowen]

I recently acquired a boat with Raymarine which is new to me. This video helped provide cabling basics. Thank you!

[@RaymarineInc]

Thank you for watching, and welcome to the Raymarine family.

[@AndanteCruises]

Excellent Jim, thank you.

[@RaymarineInc]

Thank you for watching!

[@espr55]

Exactly the info that I needed. I'm combining New Raymarine products with B&G and other N2K devices. Thanks!

[@RaymarineInc]

Glad it was helpful! Thank you for watching.

[@tangoechobravo5817]

I really appreciate this video! Thank you.

[@RaymarineInc]

Glad it was helpful!

[@chucka8345]

Outstanding job Jim!

[@RaymarineInc]

Thank you for watching.

[@paulhodson5894]

Hello Jim, great session, I thought you should have also mentioned the balancing of the network and trying to have equal devices either side of the power source where possible.

[@RaymarineInc]

That is a great tip Paul, and important for large SeaTalk NG or NMEA 2000 networks. We offer a SeaTalk NG Reference Manual which goes into all the details. It is available for anyone interested on Raymarine.com here: raymarine.app.box.com/s/rvhycb6x1brzo64921k5tsqwv2ica3j6/folder/1787214721

[@richardhenrypfs]

Jim, this was VERY informative. I'm hoping you can help me with connecting a basic system... I'm adding an i50 depthsounder at my lower helm (with a power cable) and want to connect it to my existing c125 chartplotter at my upper helm. The two instruments are within 10 feet, can I just run a spur cable between the two or do I need a 5 way connector with two backbone terminators? Thanks!

[@RaymarineInc]

Thank you for watching. You will need to create a basic SeaTalk NG backbone to link the c125 and i50 depth sounder. The way the networking functions, you can't go directly from one to the other with a spur cable alone. The backbone system is important because it provides a level of redundance and error-checking of the data being sent, plus the backbone provides a power feed to small networked devices like the i50 depth sounder. Our SeaTalk NG starter set might be a good solution, part number T70134. It includes the 5-way connector, the network power cable, 2 terminators, and a 3-meter (9.8-foot) spur cable. Your i50 instrument has a short spur cable in the box you can use to tie it in to the 5-way connector. If you add more gear in the future, expanding the STNG network is as simple as removing one of the terminators, adding a backbone cable in its place, and then joining it to whatever combination of 5-way or t-connectors you need to add the new components with spur cables. The terminator then plugs back into the new endpoint.

[@vitoproplumber]

Awesome Vid as usual! 👍👍 Can you do a "short cut" on the newest LH updates added. Using the sonar zoom, sonar frequency adjustment, & what was added to the latest & greatest update. Nice learning little tricks. Also, Will the Medium Frequency eventually get a Fish Alarm with or without a CPBOX? Medium getting very popular with tuna fishing. Thanks as usual 🤙🤙

[@RaymarineInc]

Hi Vito! I'll get those topic on my short list. Also, I just fired a message to the product team asking about the fish detection alarm and what improvements we might see. I'll update you when I hear back.

[@onfilandtime]

Thanks for this video, it was a good help identifying the colour coding of the wiring in our boat. One subject I couldn't find on your Training videos and page, but is what lead me to this video: I am trying to integrate our Raymarine NMEA/Navigation network with CZone, because I am aware that there is a way to have CZone integration with an Axiom chartplotter. I am trying to determine how to integrate these to increase this potential functionality to control circuits and do monitoring from our MFDs. On this vessel we have a robust CZone network with its own backbone, and we have the Raymarine Seatalk NG backbone with 3 Axiom MFDs, among other systems. I think on the CZone side I can add a T-connector to the CZone backbone, and then run a spur to a Bridge Interface. Now, my question is on the Raymarine side. Can I similarly run a spur cable to the Bridge Interface, or would it be a backbone cable? And do you know much about these specific Bridge Interfaces....are they set for Raymarine SeaTalk NG or is a Micro C adapter required?

[@RaymarineInc]

In addition to making the physical network connection to CZone hardware, there is typically a configuration file for the CZone system that must be configured to allow the connection of a Raymarine MFD. For this I do recommend opening a ticket with our support team. We have a couple of people well versed in the CZone integration who can guide you through exactly what you will need to do on your system. Please click through here to get a support ticket started: teledyneflir.my.site.com/s/ Click on the "Support" icon.

[@Aboardsecondwind]

Very helpful. Thank you

[@RaymarineInc]

Glad it was helpful! Thank you for watching.

[@bootsperformance]

enjoying you videos. I have an Axiom 7+rv, an st2000 and an I-70 wind. How do I connect the ST2000to the system?

[@RaymarineInc]

Your Axiom and your i70 instrument are lined together using SeaTalk NG cabling. They communicate with each other using NMEA 2000 sentences (PGNs.) The ST2000 autopilot communicates using our earlier SeaTalk 1 format. You can add the ST2000 to the SeaTalk NG network using a SeaTalk 1 to SeaTalk NG converter kit, part number E22158. This adapter has 5 ports on it. 2 of them (blue) are where the SeaTalk NG backbone passes through. You'll uses a SeaTalk NG backbone cable, included in the kit, to extend your current backbone and add the converter. Remove a network terminator cap (blue) from your existing network. Plug in the backbone cable. Plug the other end of the backbone cable into one of the blue ports on the converter. Plug the terminator you removed into the other blue port on the converter. The Yellow port on the converter is where your ST2000 will plug in. We supply an adapter cable in the kit that has a standard 3-pin SeaTalk 1 connector on the end. Depending on what your ST2000 was previously connected to, you might also need to purchase a D244 SeaTalk 3-way connector and a length of SeaTalk 1 cable long enough to reach from the ST2000's main power/data plugin point back to the STNG converter. Use the 3-way block to plug in the adapter from the converter, and the SeaTalk 1 cable going to the pilot connector. The 3rd socket on it will be empty, and a weather cap is included to seal it off. The converter will also have 2 empty spur ports (white.) These probably won't be used unless you add additional SeaTalk NG devices in the future. If the converter is mounted out of the weather you can leave them empty. We do offer weather caps for empty SeaTalk spur connections under part number A06032. The converter kit will include a SeaTalk NG power cable, but you should not need to use it as your existing SeaTalk NG backbone is already powered to make the i70 work. The converter will get power from the network.

[@simonsmith3060]

Really nice video. Can a 2000's vintage C-Series plotter be integrated into the network?

[@RaymarineInc]

Yes, to some degree. C-Series classic models (C80 and C120) have a 5-pin port on the back for SeaTalk 2. SeaTalk 2 was the predecessor to what today is SeaTalk NG and NMEA 2000. The communication protocol is identical. Using that port along with adapter cable A06048 you can connect a C-Series to the SeaTalk NG backbone. It can share information with depth, speed and wind instruments, GPS, autopilot, AIS, VHF and other similar SeaTalk NG and NMEA 2000 compatible devices. Keep in mind that this connection won't allow a C-Series to connect to a radar, share charts, display the output of a fishfinder, or any other high-bandwidth connections. Its for lower-speed instrument and navigation data.

[@simonsmith3060]

@@RaymarineInc Thanks, It's a C70, purchased in 2010, it has NMEA 2000 and Seatalk/ST2 connections. It also runs fine with my 2Kw radar purchased at the same time. I'm upgrading my sail, depth and speed i50 instruments and adding a i50 tri-data for the nav station. Thanks again for your help.

[@RooftopSafetyUSA]

Is there a connector to extend the length of spur cables? I am connecting a non-Raymarine AIS into my network and all of the female devicenet adaptor cables are too short. Only thing I can figure is to connect the short devicenet adaptor into a backbone tee and connect with backbone cable. Is there any other option? A spur cable to spur cable connector would solve the problem but I don't see one listed anywhere.

[@RaymarineInc]

Unfortunately there are not Spur cable extenders. There are limits to how long spurs can be in order to maintain network integrity. If the spur isn't long enough to reach the backbone, you must extend the backbone to reach the spur. For all practical purposes, there isn't a limit to how long the backbone can be.

[@glenntaylor5638]

Is there another session after this "Short cuts"? Is there any order required in spurs joining the backbone, or can all devices, on their individual spur lines, be joined in any order? BTW, I found this session very helpful.

[@RaymarineInc]

Hello Glenn. We have another long-form episode that also talks about networking: kzbin.infoPOzVB2rpQMo?si=vJMGrt9ZCpkf4nhs There is no particular order required of the devices that are plugged in as spurs. GPS, instruments, autopilots, etc. can be plugged in where they have most convenient access to the network backbone. There is 1 thing to remember though. Most of your smaller spur devices draw their power from network. This includes devices like a GPS sensor, compass sensor, i50, i60 and i70 instrument displays, the AR200 sensor, and a few others. One of the key cables that feeds the backbone is a network power connection. Ideally this power should be plugged in at a central location with a balanced load of devices both upstream and downstream of the power connection. This helps to ensure that device at the far ends of the network do not starve for power. Every device plugging into the backbone carries a rating for how much power it consumes, called a Load Equivalency Number (LEN.) If you think of your entire network being stretched out in a straight line, with all of your spurs plugged in along the the length of the backbone, the LEN value of all of the devices plugged in upstream of the power feed, should be about the same as the value of all the LENs of devices downstream of the power feed. Mostly this comes into play on larger vessels with a very long backbone and lots of spur connections. If you only have a small number of devices, and they are all in the same basic area of the boat, this may be less of a factor. You might find this SeaTalk NG Reference Manual helpful: raymarine.app.box.com/s/rvhycb6x1brzo64921k5tsqwv2ica3j6/file/23388950831 Feel free to email me with any questions. [e-mail]

[@regellis1335]

I was sold a STNG conversion kit to connect my element 7s to my raymarine S-2000 (purchased in 2023). Is this the correct sea talk backbone for me or do I need a standard 5 pack with 3 white and the two blue ends?

[@RaymarineInc]

I believe you have the Element 7S and the ST2000 Tiller Pilot. If that is correct, then yes, the SeaTalk to SeaTalk NG converter kit is the right item for you. The yellow connection on the converter will connect to the SeaTalk connection on the ST2000 autopilot. The Element 7S will plug into one of the white SeaTalk NG connections on the converter, using a NMEA 2000 to STNG spur cable, which was included in the box with your Element display. The network power cable (red) which is included with the converter kit will plug into the other white SeaTalk NG connection on the converter. Finally, the 2 blue terminators included in the converter kit will plug into each of the blue ports on the converter.

[@kristinpercy]

About the sea talk ng to seatalk adapter. Blue each end (terminators) and three white ports centre one for the adapter cable. Do you leave the blue terminators in? Or should the backbone be connected in to each end of the adapter? You’ve said only two terminators in the whole system. So presumably you should not have them on this adapter. ? Please could you clarify…

[@RaymarineInc]

If you have your SeaTalk NG adapter installed in a larger SeaTalk NG network, treat the blue ports as backbone connections. If the adapter lives in the middle of the network, backbone cables will plug in at both ends carrying network traffic through the converter. There will always be 2 and only 2 network terminators in the SeaTalk NG network at its extreme ends.

[@rayzar6720]

Excellent info.

[@RaymarineInc]

Glad it was helpful!

[@RuneLanghoffGgsig]

Like the format, Please make one with Axiom. Ankering and race saling startline.

[@RaymarineInc]

Thank you for watching! More content coming soon.

[@Lordlindef]

I do need all this for a good price whit newer charts too for my older c120w Great machine but cant get it to talk whit anything of autopiloten nett radar ore any. Hope ur have an anser and some good ideas. Love ur videos

[@RaymarineInc]

The C120W uses a Navionics+ map on a CompactFlash (CF) memory card. You'll need to contact Navionics directly to see about getting one, as they officially ended normal production of charts on Compact Flash media a few years ago. You can reach Navionics through their web site at www.navionics.com.

[@M-yc3er]

18:56 So the Seatalk 1 has 12V power on it, if you use the Seatalk 1 to Seatalk ng adapter you're saying the Seatalk 1 can then power the Seatalk ng Backbone? can the Seatalk ng power both systems? depending on amount of devices if you needed two power supplies is it better to have one power the old and one power the new? or try and centralize power input by the LEN Numbers? The power supply issue is confusing to me when linking these two systems. I am in the process of adding two Axioms 9"Pro & 12"+ (removing the old Raychart RC420) but wanting to keep the old (and still working) ST40 Instruments- 2x Tri Data & 2x Wind plus Auto Pilot. Also as a bonus question- i intend on linking the 2 Axioms Via Raynet, but i was also connecting them both on the Seatalk ng backbone, i understand that Raynet can do the job of passing all info to the Axiom without Seatalk ng cable but my concern is that would only work if both MFD's are turned ON? i.e. the MDF not on the backbone won't get this data unless i also turn the other MDF ON which is on the backbone, yes?

[@RaymarineInc]

Since your network is mostly SeaTalk 1 devices, let its power connection do the work to power everything. When you plug the SeaTalk 1 to SeaTalk NG adapter into the SeaTalk 1 network, it will receive power and switch on automatically. Your Axiom displays don't really draw any power from the SeaTalk NG backbone. Their connection exchanges data, but doesn't draw a significant feed from the backbone. It is not necessary to run SeaTalk NG to both Axiom displays. When linked with RayNet, the SeaTalk NG data stream is bridged onto the RayNet high speed network and shared with other Axioms connected to the network. When your Axioms are installed and connected to RayNet for the first time, an alarm will pop up asking you to designate one of then at the network data master. This designation makes that display the storage location for system settings, waypoints/routes/tracks database, and that unit becomes the communication bridge between RayNet and SeaTalk NG. The data master Axiom should be the one with the SeaTalk NG connection made. You can make the connection to your other Axioms, but they will ignore it unless they are switched to be the master. Since you have concerns about having 1 Axiom on, version both of them, make your data master the unit that will always be on. The secondary units can be switched on and off at will. The master unit should be on at all time. If you switch the master off, while the secondaries are still on, you'll get an alarm on the secondaries alerting you that the data master is offline. You won't be able to do anything until you either turn the master back on, or re-designate another unit to be the master. I don't recommend switching the master without some consideration though. Remember, the master unit stores the system configuration, navigation database, and acts as the communication bridge. If you switch masters, the new unit coming online as the master will not have access to that saved information, and you'll be missing your navigation data and settings. Pick a master and stick with it. Plan that it will always be on. Regularly backup the masters settings and navigation database too so you have a backup if needed for recovery purposes.

[@M-yc3er]

@@RaymarineInc Excellent response thank you, I will do as you suggest, i assume also there's no need to have Map Cards on the slave Axiom either? unless its good for back up if i lose the Master Axiom? FYI I plan on having the 9"Pro as Master at the Nav Station, that will be the communications hub all cables will lead there, the 12"+ will be at the helm and without worrying about a Seatalk ng cable i only need to run 1xPower and 1xRanynet cable so simplifies its installation. NB the 12+ is the chartplotter only model so it doesn't have the Transducer socket (its blanked off)so it must get sounder input from the raynet cable via the Pro9S Master. I had another thought, if i did just want to turn on the Salve 12+ at the Helm i guess i can always unplug the Raynet cable and it will run off its own map as a stand alone mfd, in that case running the Seatalk ng to it wont be a total waste as it will get used in that instance. I realize that anything i do on that 12+ at the helm wont be saved to the Master at the nav station it will be history stored on that slave mdf only.

[@mikedee7261]

EV-100 wheel pilot. Regarding power cable , red positive, black negative. What is bare wire for and does it get connected to vessel power panel? If so, where? Thanks.

[@RaymarineInc]

The bare wire is an RF drain. If your boat is fitted with a grounding plate or dedicated RF ground, connect it there. Otherwise it can connect to the negative battery terminal.

[@brewster56]

Should you only have 1 12 volt power source for a network?

[@RaymarineInc]

Yes. The SeaTalk NG or NMEA 2000 backbone must be powered from a single point. Ideally, it will be near the center of the network to balance the load both upstream and downstream of the power connection.

[@ivoherzog3116]

Hi. I have several generations Raymarine equipment in my boat. I am having a lot of trouble to make the old wind/speed/depth SeaTalk to connect to my SeaTalk Ng autopilot (this works) and then, integrate all of these to my Axion plotter (NMEA 2000). I do have ALL the adaptors you showed in this video. Nevertheless, the SeaTalk (wind/speed/depth) are talking to the auto pilot, but this network is not communicating with the NMEA 2000 (Axion/AIS/VHF) network. Can you please advise?

[@RaymarineInc]

It sounds like you need a SeaTalk to SeaTalk NG converter kit (E22158) in your network. This device sits in-between the SeaTalk 1 network (depth, speed, wind) and your newer devices running SeaTalk NG. The Depth, Wind and Speed instrument's SeaTalk 1 network cable will be connected to the center, yellow port on the converter. The converter will then be plugged into the SeaTalk NG Backbone through one of its blue connectors, joining into the backbone connecting your Axiom and autopilot components. There should be only 2 blue terminators in your network overall, at the ends of the backbone. I suspect one of these things might be happening: 1. You have an extra blue terminator in the network somewhere. Make sure there are only 2 of them overall, at the ends of the overall backbone. You could also be missing a terminator. There must be 2 of them all the time plugged in, and never more than 2 of them. 2. You have the SeaTalk to SeaTalk NG converter plugged into the backbone using a white spur cable, rather than joining it to the backbone. 3. You actually have 2 seperate SeaTalk NG networks running. One has the converter with SeaTalk 1 instruments, and the new autopilot. The other has your Axiom, AIS and VHF on it. You need to join them together so there is one continuous backbone linking all of them.

[@StevenPfromm]

If yojr connecting to a NEMa2000 that already powered by 12 volts do you need to power the ng network? Or is 1 power source cover both. If nema2000 is connected as a spear does the nema2000 12 volt power need to be disconnected.

[@RaymarineInc]

If you are joining the NMEA 2000 and SeaTalk NG backbones together, there should only be 1 power source. SeaTalk NG is simply NMEA 2000 data running on a Raymarine-specific cabling system, so all the normal rules for NMEA 2000 networking apply. 1 power source in the middle, and 1 terminator at each end of the network. This means most likely you will be removing 1 SeaTalk NG terminator and 1 NMEA 2000 at the point where you are bringing the backbones together. That will leave you with 2 terminators at the extreme ends of the network. When you reduce to 1 power source, it should be centrally located so the power load is balanced upstream and downstream of where it is introduced. Every device on a NMEA 2000 or SeaTalk NG network has a LEN (Load Equivalency Number) rating. Add up all the LEN values upstream of the power feed, add up all the LEN values downstream, and they should be roughly the same. If there is more load on one side or the other, it is recommended to move the power feed up or downstream to get it to a more central point. For joining a SeaTalk NG backbone to a NMEA 2000 backbone, we offer 2 accessory cables that make this very easy. A06074 is a SeaTalk NG backbone to DeviceNet Male (NMEA 2000) connector A06075 is a SeaTalk NG backbone to DeviceNet Female (NMEA 2000) connector On the SeaTalk NG cabling system all cables are female at both ends, and all ports are male. In the DeviceNet NMEA 2000 system cables are all male on one end, female on the other, so you'll need to inspect where you are planning to join the backbones to see which version of the adapter you will need.

[@bborjd]

Jim, have my new system up and running but my Airmar triducer shows 3 dashes for speed. Is there something I'm missing in setup or calibration?

[@RaymarineInc]

You might need to go into the data source selection menu and choose your speed source. You didn't mention if this is on Axiom or an instrument. On Axiom go to Home...Settings...Network...Data Sources...and select the Speed tab. Axiom will scan and show all sources for speed-through-water information. Select the device that your Triducer is connected to and it should begin populating all instances of Speed in the system. Our i70s instruments have a similar data source selection menu. Go to Menu...Setup...System Setup...Data Sources...Speed.

[@solentbuoy7660]

Hey Jim, can you help 🙏 I want to add axiom 9+ to my boat but I have st5000 autopilot and st60 tri data, I understand what I need to connect to the system but can I do away with the control heads and just use the axiom ??

[@RaymarineInc]

Your ST60 Tridata could be replaced by an iTC-5 instrument transducer converter. The depth and speed transducers currently plugged into the tridata would be connected to this module, and you could eliminate the Tridata display if you want to. Axiom will be able to see, control and calibrate those transducers. The ST5000 autopilot head cannot be eliminated without doing some upgrades. The ST5000-series autopilots were a bit unique in our lineup in that the control head is also the course computer and power supply for the autopilot. If you look at the back of the ST5000 you'll see that the autopilot compass, drive unit, and rudder sensor are all connected directly to it. Because of that, the ST5000 controller is an integral part of that system and can't be eliminated. If you wanted to upgrade and eliminate the ST5000 from your helm, you could use an Evolution EV-150 system with your existing drive unit. ST5000 and its compass are removed. EV-1 sensor core replaces the compass. ACU-150 actuator controller connects to your autopilot drive. Your current rudder feedback sensor connects to the ACU-150, or can be eliminated as its not required anymore for the autopilot, though you may want to keep it just to know the rudder angle. That Evolution system can be configured, calibrated and controlled by Axiom.

[@solentbuoy7660]

@@RaymarineInc thanks for that detailed reply, that’s a massive help 😎 if I just keep the st5000 but hide it under the helm, can I add a p70rs to the new STNG network and still control autopilot from the p70 unit ?

[@yoeman3416]

I recently replaced my dsm300 with a cp370 and used the adapter and it works with my e120w but now want to use a MFD e70011 as my primary display Can I feed both from the cp370 or do I need another adapter I do have the new stng kit I'm told my radar and auto helm st 6002 won't work with the newer MFD

[@RaymarineInc]

Unfortunately the E120W display and the c95 display (E70011) are from different product generations and can't be networked together in a way that would allow them to share the CP370 sonar. You'll need to pick one or the other to be your fishfinder and connect the CP370 to that one alone. It's not SeaTalk NG, but the faster RayNet High Speed Ethernet (aka SeaTalk HS) that allows the sonar picture to be shared. You can connect SeaTalk NG to both displays. The digital depth (number) will be shared in the data stream. Any depth data box on the non-sonar display will populate with a number. You won't see the bottom scroll, fish targets, etc. though. Your ST6002 autopilot will keep working with the newer system if you use our SeaTalk 1 to SeaTalk NG converter kit, E22158. This device bridges the older SeaTalk 1 network traffic onto the new SeaTalk NG network, and vice-versa.

[@mariekfishing]

Chuck can I connect an AR200 directly to Axiom MFD and its gets it power from the MFD instead of having to connect to the backbone? I have a flybridge Axiom connected with Raynet but no backbone at Flybridge. If i create a second backbone on flybridge and have the Raynet connected axiom on that 2nd backbone will it share the seatalkng devices across all?

[@RaymarineInc]

The AR200 sensor must be connected to a powered backbone. It gets it power from the backbone. Axiom can't supply power to, or communicate with the AR200 directly. Your Axiom also gets connected to the backbone through its NMEA 2000 port. Axioms share NMEA 2000 data with each other over their RayNet connection, but you can't really create 2 seperate SeaTalk NG backbones and bridge them to each other with RayNet. Unfortunately it doesn't work that way. The AR200 needs to be connected to the main backbone.

[@aiu1465]

hello. I have Raymarine element 9 and compass RS 150 element 9 has an output - a plug for connecting NMEA 2000, compass pc 150, cable with plug - SeaTalkng®. please tell me how to connect and configure the compass rs150 to element 9?

[@RaymarineInc]

You will need to build a SeaTalk NG backbone, then connect your Element 9 and Raystar 150 to it. Our SeaTalk NG starter kit has most of what you will need. The part number is T70134. You'll also need Raymarine cable A06075, which is a NMEA 2000 to SeaTalk NG adapter cable. The 5-way connector serves as the backbone. Plug the 2 included terminators into the blue ports to terminate the network. Power the backbone using the supplied STNG power cable. That will leave you with 2 empty spur ports (white.) Plug the Raystar 150 into one of them. Then use the A06075 NMEA 2000 to STNG adapter cable to make the final connection between the Element's NMEA 2000 port and the last empty white spur connection. Since Element has an internal GPS of its own, and you are adding another one with the external Raystar 150, you'll need to tell Element to make the Raystar 150 the preferred source for GPS. Once everything is installed and powered up, on Element to Home...Settings...This Display...Data Sources. Select the GPS tab and you'll see listings for both the Element's Internal GPS receiver and your Raystar 150. Highlight the Raystar 150 and press the OK button to make it the preferred GPS source. A green check-mark will appear on the left indicating it is the preferred source.

[@doddi1952]

One question . Can I use 24 V to power the ctalk NG into one of the white spur connectors (on the backbone) with the black cable with the red stripe. Or do I have to use 12 V ??

[@RaymarineInc]

SeaTalk NG must be powered with 12-Volts DC only. Do not power it with 24-volts.

[@ejdd3442]

i have a EV100 autopilot on seatalkng and a separate network switch HS5 that connects my Radar, AIS and Axiom. I want to connect by EV100 to the HS5 so I can see my autopilot on the Axiom. Is this possible. I spent endless hours searching Seatalkng to Raynet to no avail. Any Ideas?

[@RaymarineInc]

Your Axiom screen should be plugged into both the RayNet high speed network as well as the SeaTalk NG network. Run a cable between Axiom's Network port and one of the empty ports on your HS5 network switch. You'll also connect your radar to the HS5 network switch. There are 2 legs on the Axiom's power cable. One leg provides power to the unit. The other has a 5-pin, threaded DeviceNet NMEA 2000 data connector. In the kit with your Axiom was a DeviceNet to SeaTalk NG adapter cable with a white connector on the end. Attach this adapter and plug it into any empty white port on the SeaTalk NG network. This will allow Axiom to see and control your autopilot, get data from your AIS, and share information with other network instruments. The RayNet network is Ethernet-based and carries high-speed, high-bandwidth information like radar, sonar and camera feeds. This network also allows multiple Axioms to share a single map card. The SeaTalk NG or NMEA 2000 network carries low-bandwidth navigation and status information like GPS position, course, speed, depth, wind, heading, AIS, engine parameters and similar.

[@pacmanchristian]

Hi, it is sometime no easy to turn the ring 1/4 turn to fix the Spur cable properly. Especially if the 5-way connector is fixed on the boat wall with his sockets opened to the bottom I can only turn it a little bit. It is very narrow between the other Spur connectors. Is there any tool you can provide?

[@RaymarineInc]

Agreed, the locking collars on the SeaTalk NG sockets, blue and white, can be tight to lock and unlock. Fortunately, it should not be necessary to open and close them much once installed. If you get one that seems to be stuck, you can carefully try to get a better grip on it with some slip-joint pliers, but proceed with extreme caution as you don't want to break the collar.

[@ejdd3442]

I have to connect my Raymarine quantum 2 radar to my Axiom 9+ do I need to use HS5 if so would it make sense to use the highspeed ethernet for the entire network and not consider seatalk ng? I am a bit confused.

[@RaymarineInc]

The Quantum 2 radar can be connected to Axiom either using a RayNet network cable, or via Wi-Fi. If you make a wired connection that radar can be plugged directly into Axiom's network port. If you have additional RayNet high speed accessories (cameras, external sonar module, FLIR) then you might need to add a network switch to make more connections. The Axiom+ only have a single RayNet port. Quantum does not tie into SeaTalk NG. SeaTalk NG is a slower-speed network that carries data like depth, speed, wind, engine data, GPS, etc.

[@ejdd3442]

@@RaymarineInc Thank You! I am almost there, I have AIS, and Autopilot therefore I definately would need the HS5 which would be used for those devices as well?

[@RaymarineInc]

AIS and autopilot are low-bandwidth SeaTalk NG devices. The HS-5 switch is for high bandwidth accessories like additional Axiom displays, radar, external sonar modules, FLIR camera, and video cameras.

[@themooringscottage8872]

If my backbone is in cable trunking is it ok if it near to 240 ac cables ( insulated) , will it cause interference ? Regards Mark Raynes

[@RaymarineInc]

The SeaTalk NG cabling is shielded so the presence of the AC cabling should not present an issue for it.

[@intensivecare180]

If I have an existing spur cable that is fished through T-Top tubing, and I now want to expand the network , is there an adapter to use the spur cable and "switch" it to a backbone with some sort of adaptor without pulling out the spur cable just to add a backbone cable in its place? My plan is to add a 5-way and add an i70 up in the E-box next to the Ray73 VHF.

[@RaymarineInc]

Unfortunately we don't offer a spur-to-backbone adapter. The wiring and the physical connector is a bit different in each of those cables. Your best bet, though painful, would be to use the existing spur to pull up a backbone cable, then add your 5-way block and terminator at the top. There is another possible solution to consider too. If the only SeaTalk NG items up there are your Ray73 VHF and the to-be-added i70 instrument, you might look for an older generation i70, rather than the current i70s instrument. The slightly older i70 instruments have 2 spur ports on them that allow them to daisy-chain devices together. That 2nd spur port is no longer present on i70s instruments to make them compliant with the latest NMEA 2000 networking standards.) If you can locate an older generation i70, you can connect it to the the existing spur cable, then connect the Ray73 to the empty spur on the i70. Just as an example of what I am talking about, this listing is an older-generation i70 instrument with the double-spur ports: maxmarineelectronics.com/product/raymarine-i70-color-multifunction-instrument-w-sun-cover-tested-90-day-warranty/ If you prefer the older generation instrument to have the more modern, squared-off corners and black surround, we do also offer a bezel kit for it, part number A80355. There is a suncover that goes with it, part number R70663. This makes the older i70 instument cosmetically look like the current i70s instrument. The software the instrument runs is the same across i70 and i70s, so old instruments can be updated to the latest release easily from any connected Raymarine Axiom display.

[@intensivecare180]

@RaymarineInc amazing explanation! Thank you very very much!

[@spatus75]

Hello. I have a raymarine e120 and I would like to connect it to my raymarine axiom 7 within my network. I have not been able to get the axiom to view the radar info. Please help

[@RaymarineInc]

Axiom cannot share radar information with the e120. Due to the age differences between them they communicate quite differently and cannot share a common radar scanner. You would need to replace the E120 with another Axiom display of any size of configuration. Also, for your radar scanner to work with Axiom it would need to be a digital radar scanner. The E80 and E120 displays were the last in our lineup that could work with analog radar scanners, and also digital radar scanners. The Analog radar scanners would connect directly to the large radar connector port on the back of the screen, where a digital radar scanner could connect either directly to the SeaTalk High Speed port, or to a remote SeaTalk High Speed network switch. If you have an analog radar scanner, directly connected to the radar port of your E120 with a thick, white interconnect cable, it will not work with an Axiom display.

[@davidressler4292]

Why doesn't Axiom support the Raymarine network natively?

[@RaymarineInc]

The SeaTalk NG network is a bit of a hybrid system designed to accommodate both legacy and newer products. When it was introduced there was an abundance of SeaTalk 1 devices still fresh in the market, and not as many new NMEA 2000 CANbus devices yet. The SeaTalk NG system actually carries NMEA 2000 information on cables that support both NMEA 2000 and SeaTalk 1 for legacy devices. Over time the number of SeaTalk 1 devices has dropped significantly, so the need for the legacy cabling support is also declining. When Axiom was conceived, the decision was made to go all-in on NMEA 2000 networking going forward so they were designed with industry-standard DeviceNet connectors, rather than SeaTalk NG connectors. As time goes on you'll continue to see more Raymarine devices with NMEA 2000 Device Net connectors on them as the transition progresses. Fortunately, it is easy to switch the cabling systems from one to another as needed with simple adapter cables. We offer both spur/drop connector adapters for attaching items to the backbone, as well as backbone adapter cables which enable the navigation network backbone to transition from NMEA 2000 to SeaTalk NG cabling, and vice-versa.

[@doneckhoff6609]

My wind bubble went away on i70 and is innacurate. The wind vane in the mast appears to be turning. The MFD lighthouse 3 shows that the iTC5 is connected. The version is 1.12. Is this the most recent software update? Also, the network is the old network when we bought the boat 2 years ago. Is this a problem. Not sure what the password is. When I tried to update it only gave me the option of the SD card and No network?? We have Starlink. Is there a way for me to connect to that instead of an internal one? Or how do I get the internal one to work. Thanks!

[@RaymarineInc]

Sorry you are having trouble with your wind instrument. Version 1.12 is the latest for the ITC-5, so you're up-to-date. Your MFD sounds like it is behind on its software. LightHouse 4.4 is the latest as of today. To get your wind information back, first lets make sure the iTC-5 is still selected as the preferred wind source. On Axiom touch Home...Settings...Network...Data Source Selection. When that loads touch the Wind tab. Your iTC-5 should be listed as a source for wind information, and there should be a checkmark to its left indicating it is selected. If not, please touch it. Its listing should also indicate the current speed and direction its sending to the network. If that does not solve the issue it might be worth testing the masthead transducer to be sure the sensors in it are working and sending signals down to the iTC-5. We have a simple test you can perform with a multimeter to check both the vane and cups. You can access it here: raymarine.custhelp.com/app/answers/detail/a_id/3324/~/masthead-wind-transducer-test Related to getting Axiom connected to your Starlink system for internet, you can connect Axiom's Wi-Fi to the Starlink hotspot. On Axiom go to Home...Menu...Settings...Getting Started....Software Update...Check Online. On the next menu that appears touch Wi-Fi Settings. Enter the SSID (network name) for your Starlink Wi-Fi, and enter its password. Axiom will connect to it for internet access. From there you can have Axiom check for software updates. Follow the on-screen prompts to update it to the latest version.

[@doneckhoff6609]

My iTc-5 is listed as the source. I have not gone up the mast yet to see the tranducer setting as I am unsure that I can reach the top from the Bosun chair since i am short, anyway. I checked the connections on the iTC-5 with a multimeter and all the voltage was within specs except unsure when testing the wind speed I got multiple readings quickly from 0 to 7 but never held on a reading, there was not much wind. The vane was pointing in the correct wind direction and the cups were spinning normally -I believe I have the trapazoid shape. but no wind reading at all on my instruments. All other Voltages were reading correctly but now my depth is not reading either- only dashes. If the readiing are ok does that mean I still have a transducer problem? Regarding my MFD. When I do the steps to update software- when I click on that the only options that pops up is "check Sd card". I do not have the option of "check online" like it shows on tutorials I have watched. How do I get that option to come back on? Also, I have an outdated Navionics SD card in one of the slots on the front and purchased a new Navionics card that is updated and placed that in the 2nd SD card slot, but it is not reading that card??? only one is showing when I press check updates for SD card... and it says last update was 8/11/21 which is prior to us purchasing the boat. @@RaymarineInc

[@Steve-nw6ir]

Hello, I have a problem with my Axiom 9 on the sonar-depth reading. the software is the 4.4 ver. what is happening is the bottom reading is changing to what my cannon balls are running at. seems to happing if the boat moves side to side . the bottom reading comes back to true bottom reading if I run the cannon balls up to about 10 ft from surface. fishing in 40-100 ft with the cannon balls at 20-30 ft. thinking it's a gain setting . been on auto for all setting. thanks

[@RaymarineInc]

Hello Steve. It sounds like your outrigger balls are passing through the sonar beam, and presenting a brighter target than the actual bottom. You might try lowering the gain just a bit. Bring it down 5% at a time until it re-acquires the actual bottom.

[@Lordlindef]

Hei boss. Do you have any future plans and ideas of raymarine c120/w ??? Ais and newer maps

[@RaymarineInc]

The C120 and C120W models were both discontinued quite a while ago, and no longer receive software updates. The final versions of software for each of them can be downloaded from Raymarine.com though. Both of those models do support AIS, as long as you have the latest software in them. The C120 interfaces to AIS using its NMEA 0183 port. The C120W could integrate with AIS using NMEA 0183 or SeaTalk NG. Both of those models use Navionics charts on Compact Flash (CF) cards. You would need to contact Navionics about chart updates in that format.

[@Lordlindef]

But thats allsow only 4gb. Have photos of it all

[@oliverschlotz-pissarek1755]

I would like to integrate an vhf lowrance lvr-250 in a seatalk ng Network, so the vhf is able to geht the gps Position. Is that possible? If yes, what parts do I need? Thanks in advance! Oliver

[@RaymarineInc]

Your LVR-250 VHF is an older unit that only supports the NMEA 0183 data interface. You will need a SeaTalk NG to VHF interface kit, part number E70196, to complete the installation. The plug-in converter will read the feed from the SeaTalk NG network and provide the basic GPS position data to the radio needed for its Digital Selective Calling (DSC) features to work.

[@rogerroellwhatbrandofnetto6076]

I would like to know if I can use a wheel drive on my StarCraft power boat it has a mercurer I/O unit with rack & pinion steering it 19.5 ft

[@RaymarineInc]

A popular wheel drive option is the Octopus Drive. It is a replacement cable-steering helm with an integrated electric autopilot drive. It works with our Evolution EV-200 autopilot system (T70156.) You can see the details on it here: octopusdrives.com/products/type-s-t-dashboard-drives/

[@phansenri]

I have a fusion radio. some times it appears and is controllable on my axiom mfd and some times it does not appear. is there an order to start up for it to appear on the MFD?

[@RaymarineInc]

Axiom can control Fusion systems connected either through NMEA 2000 or via Ethernet. There is no particular startup order needed for them to see each other. Typically once both are online they will connect within 10 to 15 seconds. If you happen to have one of the Fusion systems that supports both NMEA 2000 and Ethernet connectivity, I would connect only one or the other, but not both. The Ethernet connection has higher bandwidth so supports sharing album art with Axiom, where NMEA 2000 does not. Otherwise, the operation is the same. If it keeps giving you trouble, please make a call to our support team, preferably from the boat, as they can help to narrow down the cause of the issue.

[@sheilamrum8132]

Hey i have lovrence plotter with nmea 2000 in my cokpit. I have nov boght a raymarine axiom 9 to put with my chart tabel can i just connect to nmea 2000 and will it work. I have Lowrence radar can i see it on raymarine via nmea

[@RaymarineInc]

Your Axiom 9 and the Lowrance plotter can share basic navigation data across NMEA 2000. Things like waypoint information, position, course, speed, ETA, etc. can be shared. The radar picture from your Lowrance radar is not available to Axiom over NMEA 2000. NMEA 2000 is a low-bandwidth data bus and can't carry high-bandwidth information like radar, sonar or chart data.

[@davidobyrne3586]

My Element 14 stops and then shuts down, then within a minute it starts up again, I also noticed the screen is hot… is this a power problem or is it from the sun..

[@RaymarineInc]

Hello David. Sorry your Element is giving you trouble. Element should be able to keep operating normally in hot conditions and in direct, tropical sun. It's also common for our screens to feel hot if they are in the direct sun. We design them to be able to accommodate the extra solar heat. It is hard to say exactly what the cause is here, but here are some things to check. First, double-check the power feed going to it just to verify that it is at an acceptable range. Element wants to see at least 8.0 volts DC and no more than 16 Volts DC. Ideally 12 to 13 volts is the target. If you are on the lower end of the scale, and really anywhere below 10 volts, the unit may be starving for power. Your boat's batteries would be very low at that point. Are there any other devices or electical loads on the boat cycling on an off as this happens? A temporary drop in voltage could cause Element to drop offline and then restart. Also, how does Element behave when it is not in hot conditions? If you are out early morning or evening does it remain online? If the power feed checks out, and this seems to be heat related, it might be worthwhile to send it up to our repair center so we can have a look at it.

[@Lordlindef]

How to connect it all whit my radar and autopilot ??? Internett ? And ais antenna for c120 w. Is it just to buy antenna and plug in ??? No one videos of any of this machine's

[@RaymarineInc]

The C120W is an older platform that we have not made for a bit over 10 years. There are not many videos for it due to its age. The C120W can network to a Raymarine digital radar scanner using SeaTalk High Speed Ethernet cabling and a network switch. From our current radar lineup you could connect C120W to the HD Color RD418HD or RD424HD radars, or a Magnum open-array radar. There are other older radar models it will work with too. They do need to have a digital connection, rather than an analog connection. The C120W supports SeaTalk NG networking for connecting to Raymarine instruments and autopilot. If you want to connect an AIS transceiver to it, you'll need one that supports NMEA 0183 output. Our current AIS700 model still supports that connection standard.

[@Lordlindef]

Can get network from my router to ny c120w ????

[@RaymarineInc]

The C120W can connect to a Raymarine network switch to get access to a connected radar scanner, sonar module or another C-Series Widescreen display for networking. I'm not sure what kind of a router you have there, but the C120W does not have any internet capability, if that is what you are looking to do.

[@wjhann4836]

"Non Raymarine Devices" - Axiom Plotters? They are delivered with NMEA 2000 micro connectors.

[@RaymarineInc]

Yes...we are in the process of changing over some products from SeaTalk NG connectors to NMEA 2000 connectors. In most cases we supply an adapter cable in the product box to make that conversion, if needed.

[@bitsurfr46]

I am still waiting for coverage of your wireless products.😢

[@RaymarineInc]

Thanks for watching, and leaving a comment. I'll try to get wireless instruments up soon.

[@steliospissourios8058]

Hello James ! I wait for your answer ! I send you on your mail !

[@RaymarineInc]

Thank you. I will take a look for it.

[@screaminbones4808]

Will any airmar transducer work with the i50 or would it need to be one with a Raymarine part # ?

[@RaymarineInc]

There are other Airmar instrument transducers that will work with i50 (and other) Raymarine instruments that we don't carry in our lineup. Airmar's parts and accessories branch, Gemeco Marine, is a great resource for these specialty transducer options. Longer stems, shorter stems, retractable options, etc. They do make a wide range of transducers for instrument systems that are compatible.