E80 Classic and Evolution Autopilot

[dschedgick]

I have an E80 Classic that is hooked directly to my DSM300 through the Seatalkhs port. I also have an S1000 autopilot that I'd like to upgrade to an Evolution autopilot. I believe the Evolution autopilot could use the Seatalkhs port that the DSM300 is currently using, but I want to keep the sonar unit as well. What extra hardware/wiring do I need to purchase to get the Evolution autopilot to interface with my E80 Classic so GPS data can be shared and to keep my DSM300 active (part numbers would be nice)? Or maybe this can't really be done with my E80 classic. If I can't connect through Seatalkhs, what do you suggest to get GPS data to the Evolution autopilot? I'm assuming I need GPS data for the Evolution autopilot to go to run trolling patterns.

Thank you.

[Chuck - Raymarine - Moderator]

Welcome to the Raymarine Forum

Q. I have an E80 Classic that is hooked directly to my DSM300 through the Seatalkhs port. I also have an S1000 autopilot that I'd like to upgrade to an Evolution autopilot. I believe the Evolution autopilot could use the Seatalkhs port that the DSM300 is currently using,
A. It is not possible to interface an Evolution autopilot to an Ethernet (SeaTalkhs) network. The E-Series Classic MFD and Evolution autopilot components will each be interfaced as individual spurs to a powered and properly terminated SeaTalkng backbone. Raymarine offers the A06061 / 4.92in (1.5m) E-Series Classic MFD to SeaTalkng Spur cable to permit the MFD's SeaTalk2/NMEA 2000 socket to be interfaced as a spur to a SeaTalkng backbone. The E-Series Classic MFD will additionally need to be updated with E-Series Classic MFD v5.69 software.