[CA] [CA11] Connecting Ev150 to garmin5208 - Printable Version +- Raymarine forum (http://forum.raymarine.com) +-- Forum: Raymarine Forums (/forumdisplay.php?fid=1) +--- Forum: Autopilots (/forumdisplay.php?fid=23) +--- Thread: [CA] [CA11] Connecting Ev150 to garmin5208 (/showthread.php?tid=5767) |
[CA11] Connecting Ev150 to garmin5208 - Makoman23 - 06-12-18 06:54 PM Hello, which cable would i need to hook up an ev150 system to a garmin 5208 in order to get a speed data source. As of rite now the ev150 control shows "detecting magnets" and can not complete a compass linerization. Thank you RE: [CA11] Connecting Ev150 to garmin5208 - Chuck - Raymarine - Moderator - 06-14-18 10:08 AM Welcome to the Raymarine Forum Makoman23, Please be aware that third party GPS/Chartplotting product which you have identified is capable of determining SOG, not Speed (through water (STW)). For those who will be operating the autopilot in a standalone configuration, the Speed Input (MENU->SET-UP->AUTOPILOT CALIBRATION->VESSEL SETTINGS->SPEED INPUT) configuration setting may be configured to Cruise Speed rather than Speed or SOG. For systems which are interfaced to a source of GPS data, but are not interfaced to a source of STW data, then the Speed Input setting should be configured to SOG. Doing so will permit the autopilot to complete Detecting Magnetics. Should the third party GPS/Chartplotting product support NMEA 2000 communications is specified within it's product web page then it may be interfaced as a spur to the powered and properly terminated SeaTalkng / NMEA 2000 backbone to which the Raymarine Evolution autopilot components have been interfaced. Please click here to view a FAQ addressing how third party products featuring a NMEA 2000 communications interface may be interfaced to a spur socket within a backbone which has been constructed from SeaTalkng networking component. Should an additional backbone socket need to be added to the backbone to accommodate the interfacing the third party GPS/Chartplotter to the system, then please click here to view a FAQ addressing this subject. |