PC/SeaTalk/NMEA interface box E85001, need cable advice

I am all new to Raymarine's seatalk ng network.  I have purchased the EV-200 autopilot system and now I am trying to connect to my laptop with the PC/SeaTalk/NMEA interface box E85001, problem is it neither comes with cable nor does it list the required cables.  I have searched Raymarine and the entire web but I cannot find cables to go from the SeaTalk ng network to the interface box and I am guessing that to go from the box to my pc I need cable part number E86001.

Views: 1041

Reply to This

Replies to This Discussion

Welcome to the Raymarine Technical Forum Kurtis,

The Evolution autopilot is designed to exclusively support SeaTalkng/NMEA 2000 communications protocol.  The end result of any adaptation performed is to end up with SeaTalkng/NMEA 2000 communications protocol for use by the autopilot using the fewest number of conversions possible.  As such, answer to your question concerning how to interface the Evolution autopilot to the PC is in part dependent upon the navigational software application which will be run on the PC and the communications protocol which is supported by that application.

SeaTalk: the only application that I am aware of featuring support for SeaTalk communications is RayTech RNS 6.1/6.2 software.  RayTech RNS 6.1/6.2 software would also be the only navigational softare application that we would typically recommend use of the E85001 PC/SeaTalk/NMEA 0183 Interface module as part of the kit to interface the PC to the Evolution autopilot.  See the attached chart addressing how a DB-9 PC Serial Data Cable would be interfaced to the E85001.  The serial data cable color codes within this chart are applicable only to the E86001 PC/Serial Data Cable.  If using a third party serial data cable, then the pin numbers specified within the same attached chart should be used.  Should the PC not feature a DB9 Serial Port, then it is strongly recommended that the SeaLevel Serial to USB Adapter referenced with the attached chart be obtained to adapt the serial data cable for use with a USB port.

Either of the PC/SeaTalk/NMEA 0183 Interface Module's SeaTalk ports will be interfaced to the the yellow SeaTalk port of a SeaTalk to SeaTalkng Converter (updated with v1.21 SeaTalk to SeaTalkng Converter software) of an E22158 SeaTalk to SeaTalkng Converter Kit using the supplied A22164 SeaTalk to SeaTalkng Converter Cable (cut off the cable's black 3-Pin SeaTalk plug to access the cable's red, yellow, and black leads).  One of the two blue SeaTalkng Terminations Plugs included with the SeaTalk to SeaTalkng Converter Kit should be installed within either of the the two blue backbone ports of the SeaTalk to SeaTalkng Converter.  The SeaTalkng Power Cable supplied with the SeaTalk to SeaTalkng Converter Kit should be interfaced to the one of the white SeaTalkng spur ports of the SeaTalk to SeaTalkng Converter Kit and to a 12VDC power circuit.  Should an ACU200 or ACU300 be installed onboard, then the ACU should be configured to NOT power the SeaTalkng backbone.

The EV-1, ACU, and p70/p70R will each be interfaced to the white SeaTalkng spur ports of an A06064 SeaTalkng 5-Way Connector.  The remaining blue SeaTalkng Terminations Plug included with the SeaTalk to SeaTalkng Converter Kit should be installed within either of the two blue backbone ports of the SeaTalkng 5-Way Connector.  Finally, the remaining blue SeaTalkng backbone port of the SeaTalk to SeaTalkng Converter and remaining blue SeaTalkng backbone port of the SeaTalkng 5-Way Connector will be joined with an appropriate length of SeaTalkng Backbone Cable (400mm (A06033), 1m (A06034), 3m (A06035), 5m (A06036), 9m (A06068), or 20m (A06037))

NMEA 0183: This is the most commonly supported marine electronics communications protocol for third party navigational PC applications.  RayTech RNS 6.1/6.2 software additionally features support for NMEA 0183 communications with marine electronics.  Actisense and other third party marine electronics communications adapter manufacturers offer NMEA 0183 to NMEA 2000 adapters and some featuring a USB interface (ex. Actisense NGW-1-USB, etc.).  The NGW-1-USB will be interfaced to the PC's USB port and to an A06045 SeaTalkng to DeviceNet Female Adapter Cable.  The white SeaTalkng Spur plug of the SeaTalkng to DeviceNet Female Adapter Cable will be connected to the white SeaTalkng spur port of an A06064 SeaTalkng 5-Way Connector.  An A6031 Termination Plug will be inserted into either blue blackbone port of the SeaTalkng 5-Way Connector.

The EV-1, ACU, and p70/p70R will each be interfaced to the white SeaTalkng spur ports of an A06064 SeaTalkng 5-Way Connector.  A SeaTalkng Terminations Plug should be installed within either of the two blue backbone ports of the SeaTalkng 5-Way Connector.  Finally, the remaining blue SeaTalkng backbone ports of the two SeaTalkng 5-Way Connectors will be joined with an appropriate length of SeaTalkng Backbone Cable (400mm (A06033), 1m (A06034), 3m (A06035), 5m (A06036), 9m (A06068), or 20m (A06037)). 

SeaTalkng/NMEA 2000Actisense and other third party marine electronics communications adapter manufacturers offer NMEA 2000 to USB adapters (ex. Actisense NGT-1, etc.).  The NGT-1 will be interfaced to the PC's USB port and to an A06045 SeaTalkng to DeviceNet Female Adapter Cable.  The white SeaTalkng Spur plug of the SeaTalkng to DeviceNet Female Adapter Cable will be connected to the white SeaTalkng spur port of an A06064 SeaTalkng 5-Way Connector.  An A6031 Termination Plug will be inserted into either blue blackbone port of the SeaTalkng 5-Way Connector.

The EV-1, ACU, and p70/p70R will each be interfaced to the white SeaTalkng spur ports of an A06064 SeaTalkng 5-Way Connector.  A SeaTalkng Terminations Plug should be installed within either of the two blue backbone ports of the SeaTalkng 5-Way Connector.  Finally, the remaining blue SeaTalkng backbone ports of the two SeaTalkng 5-Way Connectors will be joined with an appropriate length of SeaTalkng Backbone Cable (400mm (A06033), 1m (A06034), 3m (A06035), 5m (A06036), 9m (A06068), or 20m (A06037)). 

Attachments:

Thank you for your help but this does not answer my question.  I am using the RayTech RNS 6.1/6.2 software. I have then E86001 cable to connect my pc to the C/SeaTalk/NMEA 0183 Interface Module and the seatalk to seatalk ng kit but what I need to know is what cable to use for connecting from the  C/SeaTalk/NMEA 0183 Interface Module to the seatalk network.  I am already using the yellow connection for the s100's pod to connect.  Does this mean I have to buy another seatalk to seatalk ng kit? 

Kurtis,

Thanks for clarifying the interface problem that you are seeking assistance with.  In the future, listing all of the products that are to be interfaced onboard will aid in providing a more targeted response.  

If you review the SeaTalk portion of the prior response, you will find that it did indeed specify that the PC/SeaTalk/NMEA 0183 Interface Module was to be interfaced to the the yellow SeaTalk port of a SeaTalk to SeaTalkng Converter (updated with v1.21 SeaTalk to SeaTalkng Converter software) of an E22158 SeaTalk to SeaTalkng Converter Kit using the supplied A22164 SeaTalk to SeaTalkng Converter Cable (cut off the cable's black 3-Pin SeaTalk plug to access the cable's red, yellow, and black leads).

It is not necessary to purchase another SeaTalk to SeaTalkng Adapter Kit to add the PC/SeaTalk/NMEA 0183 Interface Module to your system given the marine electronics items which you have specified onboard thus far.  The following two methods may be used to interface the PC/SeaTalk/NMEA 0183 Interface Module to your system:

  • the SeaTalk to SeaTalkng Converter Cable which is presently connected to the SeaTalk to SeaTalkng Converter's SeaTalk port may be connected to a D244 SeaTalk 3-Way Junction Block.  The D244 will then be interfaced to the one of the PC/SeaTalk/NMEA 0183 Interface Module's SeaTalk ports and the S100's base station will each be interfaced to the D244 using appropriate lengths of SeaTalk Cable which have hand the plug removed from one end. 
  • the SeaTalk to SeaTalkng Converter Cable may be connected to one of the SeaTalk ports of the PC/SeaTalk/NMEA 0183 Interface Module after cutting off the cable's black 3-Pin SeaTalk plug to access the cable's red, yellow, and black leads.  The S100's base station would then be connected to the second SeaTalk port of the PC/SeaTalk/NMEA 0183 Interface Module using and appropriate length of SeaTalk Cable which has had the 3-Pin SeaTalk plugs removed each end.

Reply to Discussion

RSS

Events

Videos

  • Add Videos
  • View All

Photos

Loading…
  • Add Photos
  • View All

Latest Activity

Timothy Dube posted a discussion

ST50 instruments with new MFD c97

I have a '98 Island Packet with a complete suite of instruments - ST50+ wind, speed, depth, R10XX radar, SPX30 Smartpilot with 6002 controller - all connected with SeaTalk, but without a chartpotter.  I would like to add a c97 MFD to the system. Can I use the SeaTalk Converter to connect everything and get the old system to work with the new MFD?See More
16 minutes ago
Moderator - Raymarine, US replied to Larry Witty's discussion E125 Pilot Controls not working after Lighthouse Update to v15
"Welcome to the Raymarine Technical Forum Larry, The ST6002 is an autopilot control head which was compatible with a number of autopilot course computers introduced before and after the ST6002.  What model of autopilot course computer is…"
17 minutes ago
Underway - Raymarine, US replied to Randy Drummond's discussion adding S2 Course computer to new STng network
"It would be best to connect the p70 to the S2 course computer via Seatalk interface, then connect both to the Seatalk NG backbone through the Seatalk to Seatalk NG converter.  This way if you needed to calibrate the S2 course computer the p70…"
23 minutes ago
Randy Drummond posted a discussion

adding S2 Course computer to new STng network

I am installing a new STng network with an es75 MFD, I70 instruments and a P70 control head. I would like to use my existing S2 course computer. Should I connect the P70 to the STng network via  spur cable and connect the S2 to the network using a ST1 to STng converter or would it be best to connect the p70 directly to the S2 and then connect the S2 to the network by way of the converter.Thanks,RandySee More
25 minutes ago
Eric Heatzig replied to Eric Heatzig's discussion SeatalkNG data selection
"Perhaps i have the wrong installations manual, but I do not see any Appendices in the installation manual I retrieved form your site. https://raymarine.app.box.com/s/8o1sxspkhvf8ev7smk40/1/1327412824/30603262973/1 ENGLISHDocumentnumber:87247-2 Date:…"
28 minutes ago
Underway - Raymarine, US replied to Wayne Romberg's discussion ST60+ wind instrument still not reliable
"With how you have explained operation, this points toward connectivity.  You explained you have changed the connectors at the back of the display, are there any other splice connections in the cable going from the display to the masthead?…"
30 minutes ago
Wayne Romberg posted a discussion

ST60+ wind instrument still not reliable

The saga continues as my ST60+ wind instrument is still not reliable. It works for weeks on end and then after a few hours of a rough passage, it goes erratic for a while and then just quits  (wind arrow straight up & wind speed 0.0)  I turn if off for an hour or so and it still doesn't work. I turn it on after we get to smooth water and it works as it should and continues to work for weeks.  I sent the unit to the NH service center and they could not find anything wrong with it. I replaced…See More
31 minutes ago
Larry Witty posted discussions
37 minutes ago
Moderator - Raymarine, US replied to Eric Heatzig's discussion SeatalkNG data selection
"Eric, The list of NMEA 2000 PGNS supported for transmission and reception is specified within the Appendix D of the a/c/e-Series MFD Installation Manual."
41 minutes ago
Moderator - Raymarine, US replied to Otto Schulz's discussion Assistance installing AIS
"Otto, You're getting closer.  Your last diagram incorrectly shows the SeaTalkng 5-Way Connector at the top of the diagram being interfaced to the spur socket of a SeaTalkng T-piece ... this is incorrect.  Your diagram should be…"
44 minutes ago
Eric Heatzig replied to Eric Heatzig's discussion SeatalkNG data selection
"thank you for your response. What PGNs does it transmit?"
50 minutes ago
Moderator - Raymarine, US replied to Eric Heatzig's discussion SeatalkNG data selection
"Welcome to the Raymarine Technical Forum Eric, Raymarine's a/c/e/eS/gS-Series MFDs are not configurable with respect to designating specific PGNs to be transmitted."
54 minutes ago
Eric Heatzig posted a discussion

SeatalkNG data selection

Hi,is there a way to know or control what PGN data the a98 is able to output?thanksEricSee More
55 minutes ago
Moderator - Raymarine, US replied to Walt Bilofsky's discussion Another Older Autopilot Problem
"Welcome to the Raymarine Technical Forum Walt, Raymarine's autopilots are exclusively designed to support 4800 BAUD NMEA 0183 communications.  Should your third party MFD only output 38400 BAUD NMEA 0183, then it will be necessary to…"
1 hour ago
Walt Bilofsky posted a discussion

Another Older Autopilot Problem

I'm putting in a non-Raymarine MFD and would like to connect it to my Autohelm 100 autopilot for navigation.  The MFD is going on my flybridge, so I should be able to put its NEMA 0183 output into the ST-7000 control head up there which will get all the sentences into the SeaTalk system.  (Right?)The problem is that I want to set the MFD's NEMA 0183 baud rate to 38,400 so I can feed it AIS data.  I assume 38,400 baud won't work with the ST-7000 of the NEMA 0183 input of the Autohelm 100,…See More
1 hour ago
Moderator - Raymarine, US replied to David Alton's discussion E125 Track "Jumping" Around the World
"Welcome to the Raymarine Technical Forum David, Please note that this problem has not been previously reported.  The MFD's Tracks feature simply plots position coordinates received from the system's GPS sensor (internal or external).…"
1 hour ago

© 2016   Created by Moderator - Raymarine, US.   Powered by

Badges  |  Report an Issue  |  Terms of Service