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

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

Bajabum posted a discussion

Waypoint Transfer from E120 to e127

Hi-I'm having some difficulty transferring waypoints to an e127 that were backed up from an E120. I have tried uploading the archive.fsh file directly after transferring the file to a micro sd card. The e127 shows the file name on the import/export screen but doesn't transfer it when I select it. I have also converted the archive.fsh file to a .gpx file using a third party software tool with the same result. The same .gpx file seems to work fine with other mapping software that I have.Any…See More
1 hour ago
John Young posted a discussion

St4000 Smoked today!

Hi Tech suport community,Today I was installing the STng converter and somehow managed to smoke the control head on my st4000 autopilot, Not sure how but it still turns on and powers the helm but will only drive to port.  First off does Raymarine still repair these?  Also can I replace the st4000 with a newer control head and still use the compass and wheel drive?Thanks for the help!JohnSee More
2 hours ago
TJ replied to Robert Bunch's discussion Smart Pilot S1000 Autopilot
"The max reception on the s100 remote is three bars, not 5."
2 hours ago
nir replied to nir's discussion AIS alert - Antenna VSWR Fault
"Hi, I removed the original VHF antenna line, connected the emergency VHF antenna, took screen shot and log. then I did the same with no antenna connected then I reconnected the original VHF antenna and re-took everything. I can't say resaults…"
2 hours ago
paul shard replied to paul shard's discussion e95 - Unable to save Databar changes - reset after powering on
"Super Info. Thats fixed it thanks! Paul"
4 hours ago
Darrell Brand posted blog posts
4 hours ago
Jan-Erik replied to Jan-Erik's discussion Temperature from Airmar to NMEA2000?
"Temperature to NMEA0183 would also be ok."
9 hours ago
Jan-Erik posted a discussion

Temperature from Airmar to NMEA2000?

I have the ST30 Bidata with airmar depth in one transducer and speed/temperature in the other. The exact model for speed/temp is ST300-P371 Shorty. ST30 Bidata is only capable of showing depth and speed.My question is: is there any component that I could connect to the two unused temperature leads without loosing the ST30 because that would affect the astethics of the dashboard.I'm thinking: I know I could use the ITC-5 for everything but is it possible to connect only the two temperature…See More
10 hours ago
Jack Elliott posted a discussion

Ray tech planner

How do I turn off the disclaimer pop up when I start up Ray tech plannerSee More
12 hours ago
mike posted a discussion

Sport Pilot - EV200 installation help

Im in the process of installing the wheel sport pilot on my boat for the EV200 system.  The direction say to turn to starboard until you cant anymore.  The problem is that you have to line up the key which on my would require almost a 320 degree turn back to port to get it to line up.  Does it even matter about the position of the shaft when you install the unit?See More
13 hours ago
Hugh updated their profile
15 hours ago
Hugh posted a discussion

Intermittent display of COG and SOG on E80 with RS125

Hi All,First our setup:- Two E80 Classic MFDs wired up together via the Seatalk HS interface.- An RS125 talking to the Master via Seatalk.  - A Raymarine Smart Pilot connected to the slave E80 via NMEA 0183.- A Raymarine Radome connected to the slave.There is also some extra wiring in the boat that I can't identify (due to very difficult cable runs) including a breaker labelled "Seatalk 12V" that has no effect that on that I can identify so far.The problem is that when the Slave unit is turned…See More
15 hours ago
Karl Coplam replied to Karl Coplam's discussion c95 networked with e7 won't display NMEA AIS targets when both displays active, and other troubles
"Sorry for the typos. . . IPad and autocorrect drive me crazy. And one more thing -- the manual says that networked displays can share SD card cartography, but the e7 on th cockpit does not display any cartography from the c95 belowdecks. Am I…"
16 hours ago
Karl Coplam posted a discussion

c95 networked with e7 won't display NMEA AIS targets when both displays active, and other troubles

Just installed a new c95 belowdecks, along with a new dicitfqrk raymarine radar scanner, and the Rainer network cables between the c95 and the e7. I have a third party (ACR) AIS transponder connected via the NMEA input port 1 on both MFDs. The AIS targets display just fine when either MFD is running by itself, but as sinks as you turn on the second unit (and select the c95 as the master unit) the. AIS targets disappear on both units. What is wrong?Also, the c95 (connected to ther radar via a…See More
16 hours ago
Bob Oriol replied to Kevin tisdall's discussion i70 readout of COG from Garmin 740 gps
"Kevin, Thank that is the problem, and setting the variation manually is the work around.  I found this on another thread that confirms there is a bug in the…"
17 hours ago
Bob Oriol replied to John R Walkey's discussion i70 incorrect COG display
"There is a bug in the i70.  I found this on another thread.  I did implement the workaround and it performs as expected.  The i70 firmware hasn't been updated in two years.  Hopefully Raymarine will fix it before someone…"
17 hours ago

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

Badges  |  Report an Issue  |  Terms of Service