Thread Closed 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Interfacing a NMEA 0183 talker to an a/c/e/eS/gS-Series MFD
01-04-17, 09:53 AM (This post was last modified: 01-10-17 11:17 AM by Chuck - Raymarine - Moderator.)
Post: #1
Interfacing a NMEA 0183 talker to an a/c/e/eS/gS-Series MFD
Interfacing a NMEA 0183 talker to an a/c/e/eS/gS-Series MFD

Raymarine's a9x/a12/c/e/eS/gS-Series MFDs feature a NMEA 0183 communications interface to support transmission system data to a NMEA 0183 listener, as well support reception of data from a NMEA 0183 talker. However, Raymarine's a6x and a7x MFDs do not feature a NMEA 0183 communications interface. Please click here to view a FAQ addressing how those seeking to simply supply a DSC VHF radio with basic GPS data from an a6x MFD or a7x MFD may do so. For those seeking to bridge other data from NMEA 0183 to SeaTalkng / NMEA 2000, a microprocessor based data bridging the device (ex. Actisense NGW-1-STNG, etc.) would be required for MFDs not featuring a NMEA 0183 communications interface. In systems featuring SeaTalkng / NMEA 2000 devices, other than the a/c/e/eS/gS-Series MFD, which may also use / display data produced by a NMEA 0183 talker, some installers may opt to forego the MFD's NMEA 0183 interface and instead install one of the aforementioned NMEA 0183 to SeaTalkng / NMEA 2000 data bridging devices. The latter would typically occur in use cases where the SeaTalkng / NMEA 2000 device (not the MFD) will be monitored during periods when the MFD may be switched OFF. The NMEA 0183 to SeaTalkng / NMEA 2000 data bridging device will need to be interfaced as a spur to a powered and properly terminated SeaTalkng backbone to which the MFD has also been interfaced as a spur.

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