Raymarine ST60 to e7 MFD via X-5 course computer

[Ningaloo]

I am assisting an owner with some legacy Raymarine instruments on a (new to him) Beneteau 34.7.

The boat has ST60+ wind, depth and speed all working as expected.
It also has a X-5 course computer with a ST6002 controller.
Finally there is an e7 MFD at the saloon chart table.

The ST60+ instruments have a SeaTalk connection to the X-5 which has a separate Seatalk connection to the ST6002.
I have now connected the X-5 to the MFD using in/out NMEA0183, hoping to get the data from the instruments onto the MFD and the GPS data from the MFD to the pilot.

Sadly this does not seem to be happening. I can't see any wind or depth data on the MFD.

Can anyone suggest anything?

Both the e7 MFD and X-5 course computer support N2K/SeaTalk(ng) but I'm reluctant to implement an N2K network unless I can be certain that the legacy SeaTalk1 data will be available on it.

Our objective is to set a route on the MFD which will be an offshore race course which may involve using the same waypoint multiple times. I would like the MFD to "follow" the route, i.e. automatically select the next waypoint as the"goto" waypoint once we get within the arrival radius. I would also like to display the BTW and DTW on deck somehow. I am wondering if the ST6002 will display this data even though the autopilot will not be engaged.

All suggestions welcome.

 

[KompetentKrew]

The E7 has a SeatalkNG connector, so I would guess the officially supported way would be to use the SeaTalk1 to SeaTalkng converter kit. I don't know for sure whether that would work, but someone like Hudson Marine would know.

Converting NMEA 0183 to NMEA 2000 is an active translation - it's not simply a matter of converting the voltage levels, or using a simple electronic circuit. The NMEA 0183 string has to be read into a CPU (a low-powered one is fine) which looks up the appropriate matching NMEA 2000 sentence which it then translates to.

Seatalk1 is not NMEA 0183, but they're both just serial data so I imagine they work the same.

I wouldn't expect a device to do the translation between SeaTalk 1 / NMEA 0183 / NMEA 2000 just because it has both sockets. Well, I actually did make the mistake of expecting it with an Em-Trak 900-series AIS, but fortunately Em-Trak are adding that feature (NMEA 0183 to NMEA 2000) and releasing it as an update soon.

Digital Yacht make a SeaTalk to NMEA 0183 converter.

I'm treating SeaTalk1 and NMEA 0183 as a dead end and getting rid of it, so sorry I can't be more help.

 

[robmcg]

I am pretty sure that the course computer does not 'bridge' the seatalk data. In order to get the MFD to understand the seatalk data from the st60's then a seatalk to seatalk ng converter will be necessary.

 

[Ningaloo]

I am pretty sure that the course computer does not 'bridge' the seatalk data. In order to get the MFD to understand the seatalk data from the st60's then a seatalk to seatalk ng converter will be necessary.

is is what the manual says:
"The SPX-5 system acts as a bridge between SeaTalk and NMEA, allowing NMEA and SeaTalk devices to share information"

Sadly is does not clarify if it means SeaTalk1 or SeaTalkng however the latter is normally used with the "ng" suffix.

I have now discovered that the MFD will allow me to log NMEA data to an SD card so I'll try that and see what I get.

@KompetentKrew: I'm well versed in the distinctions between NMEA0183, SeaTalk1, NMEA2000 and SeaTalkng, however, given the statement in the manual, I still think that what I have done should work! Like you I regard all this as legacy and my own boat ix exclusively B&G N2K, but I'm trying to help out a friend here without blowing the budget. Mandatory AIS transponder and PLB for all crew members (for offshore racing) is going to do that on its own!

 

[Boathook]

I've got the st60 wind and st50 speed depth instruments and they get that data from the iTC-5 module that all the transducer data goes to to start with. The instruments are connected by the seatalk ng cables. The seatalk ng also supplies data to my eS9 mfd and a single i70s display that can show all the transducer output. Also connected in is a raymarine ais. I have also connected my sport pilot autohlem, but being fairly early design the mfd only has limited functionality over controlling this.

 

[KompetentKrew]

I apologise, Stewart. I write trying to be clear and I gather it sometimes comes across as pedantic or worse.

I see the manual does indeed say that, but looking for more information I find Raymarine support denying it and another thread in which the same Raymarine tech is quoted saying "Raymarine's X-Series autopilots are not designed to function as complete SeaTalk to SeaTalkng data bridging devices". The threads quoted by Genesis V are here and here.

 

[Ningaloo]

I apologise, Stewart. I write trying to be clear and I gather it sometimes comes across as pedantic or worse.
I see the manual does indeed say that, but looking for more information I find Raymarine support denying it and another thread in which the same Raymarine tech is quoted saying "Raymarine's X-Series autopilots are not designed to function as complete SeaTalk to SeaTalkng data bridging devices". The threads quoted by Genesis V are here and here.

Thanks for this - and no apology necessary - I was just intending to clarify my knowledge level. But I'm more confused than ever!

The Raymarine response you linked to is below:
"SeaTalkng / NMEA 2000 devices are each designed to be interfaced as spurs to a powered and properly terminated SeaTalkng backbone rather than as you have indicated. Additionally, Raymarine's X-Series autopilots are not designed to function as complete SeaTalk to SeaTalkng data bridging devices. Accordingly, it is recommended that the SeaTalk bus be disconnected from the X5 and that it instead be interfaced to a SeaTalk to SeaTalkng Converter(s) which will be installed as a backbone component within the backbone which will be installed. Please click here to view a FAQ addressing how to interface products having a SeaTalk interface to a SeaTalkng backbone, to which the Data Master MFD and SPX5 will also be interfaced. Following installation, it is recommended that the SPX5 and SeaTalk to SeaTalkng Converter each be updated with the latest available Raymarine product software updates. "

The diagram from the initial post that you reference shows what I understand to be a "powered and properly terminated SeaTalkng backbone" with the MFD and X-5 course computer on spurs.
I take the point that a SeaTalk1 to SeaTalkng converter may be required to see the other ST60+ instrument data but how can you "disconnect the SeaTalk bus from the X-5" given that the ST6002 pilot control only has SeaTalk connections?

Looks like the minimum I need is the SeaTalk1 to SeaTalkng converter kit which gives me a backbone, one spur for power and one spur to the X-5, then I'll need a backbone cable (which I assume goes into the blue socket at one end of the SeaTalk converter), a T-piece and a spur cable to connect to the MFD. That lot is AU$320 before carriage to WA!