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

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

elvira replied to David Poeltl's discussion p70 installation problem
"I have a similar problem.  I have a smartpilot x30 and control head  I have the nmea 0183 connected to my garmin 7000 chartplotter  I receive the fluxgate compass data in my chartplotter, but not the data from my chartplotter in the…"
Saturday
ALAN IZZARD updated their profile
Jul 12
Luis replied to John Pecora's discussion DSM300 Made in Mexico
"Hello, I have DSM30 bought in 2010. The bar code shows E63074 and on the bottom line */AE63074 1200513* It is connected to a CW90 chart plotter though a hub switch that also connects the radar to the chartplotter. Since the beginning it has an…"
Jul 11
Don Bruce replied to Ray Pantlik's discussion File conversion from .fsh to gpx and gpx to fsh
"Voyage planner is the worst software I have ever had the misfortune to need. I am still looking for a way to convert GPX to FSH files that would preclude me from having to use Voyage planner. GPSutility is good but they want $60 to get the full…"
Jul 10
John Wagner-Stafford updated their profile
Jul 6
Bob Collins replied to ROBERT RING III's discussion REPLACE RAY215 MICROPHONE
"Is the Ray215 cord still available?  The cover on my cord is disintegrating."
Jul 5
Frank Thalhauser replied to P's discussion No rudder reference displayed
"Kyle, I seem to recall that when I first tried changing the pilot type, I did not press and hold (for 2 seconds) the standby button as required to exit and save the change. Fortunately, the guy I had on the phone caught my error, and the second time…"
Jun 28
Kyle replied to P's discussion No rudder reference displayed
"Thanks for the feedback Frank.  I finally contacted Tech support Friday while at the helm.  First person was not able to help and basically told me system is out of date and probably not repairable but didn't have one in front of them…"
Jun 27
Russell Herbert replied to Dave's discussion C80 and WiFi
"I have a C90W I am replacing it with a c127. Wiring is easy except the NMEA is a little confusing. The C90W has 10 or more wires and the c127 only 6. Assuming they wire to the VHF and maybe another. I see 4 white wires going into a 2"x3"…"
Jun 27
Stephen L Jones updated their profile
Jun 24
Joel Hjelseth replied to Joel Hjelseth's discussion Raymarine Dragonfly 7 malfunction
"Sounds even worse than mine. Suggest you do as they suggest and take it to an approved Raymarine dealer."
Jun 14
Doug Stevens replied to Joel Hjelseth's discussion Raymarine Dragonfly 7 malfunction
"Thanks for your reply. Mine kicks off at 6 mph. I have moved it to three different places and same results."
Jun 14
Joel Hjelseth replied to Joel Hjelseth's discussion Raymarine Dragonfly 7 malfunction
"No. Still broke. Have not sent it to be checked by RayMarine. The only other possibility is that I have the transducer mounted on the left side of the propeller rather than the right side as recommended."
Jun 14
Doug Stevens replied to Joel Hjelseth's discussion Raymarine Dragonfly 7 malfunction
"Mine is doing the same thing.  Did you get this fixed? If so, what did you do? Thank you for your help."
Jun 14
Andy Barbasch updated their profile
Jun 13
Tom Aydelotte replied to John Pecora's discussion DSM300 Made in Mexico
"Just learned of this replacement program. Several years ago I spent multiple hours trying to figure out my DSM300 inconsistencies... is there any program still available to solve this issue?"
Jun 11

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

Badges  |  Report an Issue  |  Terms of Service