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: 1285

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

Richard H Wheeler liked jeff hesse's discussion S1000 autopilot
Dec 3
Paul Poswiatowski replied to Paul Poswiatowski's discussion I have a ST5000 auto pilot. It won't track more than 30 seconds.
"Back again.  The unit tracks ok for a couple minutes.  At high speed a little better, sometimes I can get 15 minutes out of it.  It will still do a crazy Ivan at times.  I believe I just have a defective unit.  I am scouring…"
Nov 30
Steven Osolin replied to Ed Y's discussion CP300 sonar not listed on Raymarine site?
"I'm in the same "boat" you are. I've been working on a project 1987 Pro-line 23 WA for a couple of years. Finally got it out last weekend. I've got a brand new C140W, CP300 and a B164 1kw transducer. The MFD does…"
Nov 23
Peter replied to John F Wong's discussion No data for 4" Open Array Super HD
"Hi, can't we just buy the IF PCB? I have the same problem. VCM100 going to sleep mode. network is working good."
Nov 22
Josh Pekar replied to Kevin Linder's discussion Cameras for e125
"I am also able to access other non-raymarine hardware through the MFD's WiFi by also assigning them within the same static IP range i.e. I can access my NVR.   Now you have a WiFi access point whenever your MFD is running.  Neat!"
Nov 17
Josh Pekar replied to Kevin Linder's discussion Cameras for e125
"Update on how to get 3rd party IP cameras to work with Raymarine settings that worked for me. 1. Must set static IP for camera in the range of 10.0.1.X** 2. Set Subnet of camera as 255.0.0.0, Gateway and DNS as 10.0.1.1 3. Disable ONVIF…"
Nov 16
Steve Battel updated their profile
Nov 16
John updated their profile
Nov 9
John replied to Al's discussion Wiring Install of Raymarine Fluxgate Compass Module
"Can I install the fluxgate and connect to a Seatalk/ng or Seatalk/1 network that I have already in place? Thank you"
Nov 9
Dave Hope replied to Dave Hope's discussion P/C backup for E80
"As you can see not been in touch for a while as all fixed and working well However now having some troubles getting laptop to connect to sea talk now Think it was after laptop was upgraded to windows 10 Do you know of any issues? Thanks Dave"
Nov 5
skipbern updated their profile
Nov 3
No Name updated their profile
Oct 27
Joe Shabbott liked Moderator - Raymarine, US's discussion Interfacing a Raystar 130 GPS Sensor to an E-Series Widescreen MFD (E90W, E120W, E140W)
Oct 23
Michael replied to Moderator - Raymarine, US's discussion SeaTalkng Communications Protocol
"Hi, these are good docs on the phys network, but there doesn't appear to be any protocol info in these docs. is there any doc on the sentences? Or is STNG the same sentences as NMEA2000 sentences?  thx"
Oct 22
Richard Anderson updated their profile
Oct 3
Mark noe updated their profile
Sep 12

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

Badges  |  Report an Issue  |  Terms of Service