E22158 and ST4000+

[Tenedos]

I am upgrading my electronics and installed a Raymarine Axiom 9 and a new seatalkng network. I bought an E22158 with the intention of connecting my old instruments and my Autohelm ST4000+ via seatalk1.

However, in the manual, I see an explicit restriction on using autopilots with E22158:

Autopilot restrictions

Important: A SeaTalk autopilot or associated controller must not
be connected to the SeaTalk - SeaTalkng converter.

There are restrictions as to how an autopilot is connected in a
system containing a SeaTalk - SeaTalkng converter.

• SeaTalkng autopilot (e.g. SPX course computer with ST70
controller) — This can be connected as part of the SeaTalkng
system in the usual manner. However any SeaTalk cable from the
autopilot must NOT be connected to the converter.

• SeaTalk autopilot (e.g. S1, S2 or S3 course computer with
ST6002 controller) — This cannot be connected to the converter,
nor to any device on the converter’s SeaTalk spur. A SeaTalk
autopilot will usually be connected directly to the multifunction
display."

Reading around a bit, some people say this is old information and this "just works".

Has anyone done something similar? Any idea why the converter would not work in this setup?

[SailFastTri]

I don't see an issue. They're not saying it can't be connected. They're saying HOW it should be connected.

[Tenedos]

Thanks SailFastTri. This diagram seems to contradict what they are saying. I will try!

[SailFastTri]

I have an ACU-200 course computer with P70 control head. It has been operating just fine for several years using SeaTalkNG connected to the E22158 and P70 control head also on NG. The "other side" of the E22158is connected to an S3 remote control, an array of ST60+ speed/wind/depth and an NMEA0183-SeaTalk converter that talks to my AIS500 transceiver and an RS-232 port for a laptop that uses a USB-serial connection to run PC navigation software.

I also have an NNMEA2000 to SeaTalkNG converter that connects NMEA2000 to my B&G Chartplotter, and the CP is directly connected to Lowrance BR24 Broadband radar. The CP can read all the AIS and instrument data from my Raymarine sources, but the B&G human interface to the AP functions is a little wonky and even though it works, I don't like the way it works but it doesn't matter to me because I don't use the AP to follow courses (and don't want to because I keep an active watch) -- instead I set a heading using the P70 control head and make periodic course corrections from there or the handheld remote.


Edit: Also, the B&G CP receives "fast heading" data from the ACU-200 to enable the use of radar overlay on the charts, but for some reason I needed to connect that to the NMEA 0183 interface of the SeaTalk/NMEA0183 converter. It's a real mish-mash but it works reliably now that it's all running, and it just required some Internet research and trial-error.

[fabricator-ken]

[ATTACH]18t18tdt42e/ATTACHipg]

Originally Posted by SailFastTri

I have an ACU-200 course computer with P70 control head. It has been operating just fine for several years using SeaTalkNG connected to the E22158 and P70 control head also on NG. The "other side" of the E22158is connected to an S3 remote control, an array of ST60+ speed/wind/depth and an NMEA0183-SeaTalk converter that talks to my AIS500 transceiver and an RS-232 port for a laptop that uses a USB-serial connection to run PC navigation software.

I also have an NNMEA2000 to SeaTalkNG converter that connects NMEA2000 to my B&G Chartplotter, and the CP is directly connected to Lowrance BR24 Broadband radar. The CP can read all the AIS and instrument data from my Raymarine sources, but the B&G human interface to the AP functions is a little wonky and even though it works, I don't like the way it works but it doesn't matter to me because I don't use the AP to follow courses (and don't want to because I keep an active watch) -- instead I set a heading using the P70 control head and make periodic course corrections from there or the handheld remote.


Edit: Also, the B&G CP receives "fast heading" data from the ACU-200 to enable the use of radar overlay on the charts, but for some reason I needed to connect that to the NMEA 0183 interface of the SeaTalk/NMEA0183 converter. It's a real mish-mash but it works reliably now that it's all running, and it just required some Internet research and trial-error.

[CaptNemoO2]

The manual is outdated:

Autopilot compatibility with SeaTalk to SeaTalkng Converter

Originally Posted by Chuck - Raymarine Moderator

Autopilot compatibility with SeaTalk to SeaTalkng Converter

As of the date of this posting, the SeaTalk to SeaTalkng Converter Kit Owner's Manual had not been updated since the kit was introduced. However, with the introduction of v1.14 SeaTalk to SeaTalkng Converter software, the SeaTalk to SeaTalkng Converter now supports integration with autopilots featuring a SeaTalk and/or SeaTalkng communications interface. Each product's software update web page includes a history of the changes introduced with each software update. Most recently manufactured Raymarine products are designed to be easily updated by their owners using the systems MFD (MFD must feature SeaTalkng and/or Ethernet (SeaTalkhs/RayNet). The latest available Raymarine product software updates and instructions for performing the updates may be downloaded here. It is expected that Raymarine will be updating the online version of Owner’s Manual to reflect this change.

RAYFAQ#

I've done it and it works, using an ST4000 control head with a type 300 course computer.

[svmobert]

I will say it probably depends on your entire combination. I have an S3G course computer on SeaTalk1. I also have the STNG<->ST1 converter to support my Raystar 150 GPS.

When my ST6001 AP control head leaked and shorted, I replaced it with the P70s. I first connected the P70s to the SeatalkNG bus, but that did NOT work. I had to connect the P70s to Seatalk1 directly. In this case I believe the limitation was the P70S itself will not control a Seatalk1 AP from a SeatalkNG network.

Since the P70s supports both ST1 and STNG directly, it wasn't really an issue.