Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
a75 not detecting NMEA2000
08-12-16, 01:42 PM (This post was last modified: 08-12-16 01:45 PM by Chuck - Raymarine - Moderator.)
Post: #4
RE: a75 not detecting NMEA2000
Mark,

As you have suggested, Raymarine does not support interfacing engine systems to the marine electronics backbone without an engine gateway. I strongly suspect that should you connect the a75 it in place of your e97, you will find that the a75 will perform in the same manner. The Engine Setup feature of the a/c/e/eS/gS-Series MFDs is exclusively designed to function with Raymarine's ECI-100 Engine Gateway and as such, should not be expected to function within your system.

Raymarine's a/c/e/eS/gS-Series MFDs follow the NMEA 2000 convention that that should a single instance of a device be present within a system, that its instance number will be 0. For items such as engines and tanks where more than one may be installed, Raymarine's a/c/e/eS/gS-Series MFDs follow the NMEA 2000 convention that instance 0 will be assigned to the instance farthest to port, with instance numbers increasing from port to starboard. As such, should a vessel feature three engines, the port engine would need to be assigned instance 0, the center engine would need to be assigned instance 1, and the starboard engine would need to be assigned instance 2. One of the features engines interfaced via an ECI-100, is that the a/c/e/eS/gS-Series MFDs would then support engine identification to address engines having instance numbers deviating from this convention. In the absence of an ECI-100, it would be necessary to re-assign instance numbers to the engines using instructions from the engine manufacturer.
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
a75 not detecting NMEA2000 - mark426 - 08-11-16, 06:05 PM
RE: a75 not detecting NMEA2000 - Chuck - Raymarine - Moderator - 08-12-16 01:42 PM

Forum Jump:


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