Thread Closed 
 
Thread Rating:
  • 1 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
"No Navigation Data" reported when engaging Track mode - Garmin chartplotter
05-02-17, 10:41 AM (This post was last modified: 02-20-19 04:29 PM by Chuck - Raymarine - Moderator.)
Post: #1
"No Navigation Data" reported when engaging Track mode - Garmin chartplotter
"No Navigation Data" reported when engaging Track mode with Evolution autopilot

Raymarine's engineering team has completed investigating a problem in which the latest Evolution autopilot software (EV-1/EV-2: v2.17; ACU: v2.23; p70/p70S/p70R/p70RS: v3.07) would not support track mode with either of the following two types of systems:
- Garmin chartplotting products which have been interfaced as a spur to a SeaTalkng / NMEA 2000 backbone to the which the Evolution autopilot components have been interfaced, or
- Raymarine C-Series Classic MFDs which have been interfaced via a SeaTalk to SeaTalkng converter to a SeaTalkng / NMEA 2000 backbone to the which the Evolution autopilot components.

The subject problem has not been reported in conjunction with Evolution autopilots which have been interfaced to other brands of third party chartplotting products. We have received reports from some Garmin chartplotting product owners stating that the subject problem was corrected by upgrading the Evolution autopilot components with the latest available Evolution autopilot software update (at the time of this response: EV-1/2 CCU software was v3.02; ACU software was v2.23; p70/p70S & p70R/p70RS software was v3.08). However, we have also some confirmed reports that the latest available Evolution autopilot software may not address this issue with some Garmin chartplotting products and legacy Raymarine chartplotting products (see above).

It is considered to be a best installation practice that Raymarine products be maintained with the latest product software updates to no only ensure that the product will support the latest features, but will also feature the latest feature enhancements and feature corrections. Should one's Evolution autopilot have been updated with the latest available software updates and encounter the subject problem when interfaced to a Garmin chartplotting product which has been interfaced as spur to SeaTalkng / NMEA 2000 backbone, then it would be recommended that:
- the Garmin chartplotting product be disconnected from the SeaTalkng / NMEA 2000 backbone which is interfacing the Evolution autopilot components to one another, and
- that the Garmin chartplotting product's NMEA 0183 interface be connected to a NMEA 0183 to NMEA 2000 data bridging device (ex. Actisense NGW-1-ISO-STNG, etc.) which in turn has been interfaced as a spur to the SeaTalkng / NMEA 2000 backbone to which the Evolution autopilot components have been interfaced.


RAYFAQ#
Visit this user's website Find all posts by this user
Thread Closed 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)

Contact Us