Raymarine Live Short Cuts: SeaTalk NG Networking 

Thank you for watching!

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

Glad it was helpful!

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

Glad it helped!

Thank you for watching!

Glad it was helpful! Thank you for watching.

Thank you for watching.

Glad it was helpful! Thank you for watching.

Glad it was helpful!

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

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.

Thank you for watching! More content coming soon.

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.

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.

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.

Hello Glenn. We have another long-form episode that also talks about networking: ru-vid.comPOzVB2rpQMo?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. james.mcgowan@raymarine.com

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.

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.

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

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.

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.

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.

@RaymarineInc amazing explanation! Thank you very very much!

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/

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.

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.

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.

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.

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.

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.

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.

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

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.

@@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 ?

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

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

Thank you. I will take a look for it.

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.

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.

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

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.

@@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?

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.