Thread Closed 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
MFD(s) no longer communicating with devices after SW update or reset
04-26-18, 09:43 AM
Post: #1
MFD(s) no longer communicating with devices after SW update or reset
MFD(s) no longer communicating with SeaTalkng, SeaTalk, or NMEA 0183 devices after software update and/or Factory Reset

Executing a Factory Reset / System Settings Reset by a MFD will cause the settings of the system's MFD's settings to revert back to their default settings. Similarly, updating the software within a MFD(s) may cause cause the MFD's settings to revert to their default values. With respect to communications, incorrect configuration of the following MFD settings may adversely effect communications:

- NMEA (0183) Output Setup: recommend that all listed sentences be sentences be selected for transmission by the MFD unless you desire to block transmission of specific NMEA 0183 sentence.

- NMEA (0183) Port Setting: if a MFD has been interfaced to a NMEA 0183 talker or listener, then the NMEA 0183 port setting must be configured to match the baud rate of the NMEA 0183 talker/listener which has been interfaced to the MFD's NMEA 0183 port. Example: MFD interfaced to an AIS receiver/transceiver. In this case, the MFD's NMEA Port Setting would need to be configured to AIS 38400.

- Data Master: In systems featuring more than one MFD, care must be taken to ensure that the MFD which has been directly interfaced to the SeaTalkng / NMEA 2000 backbone or to the SeaTalk bus has been configured as the Data Master MFD. Only the MFD which has been configured as the system's Data Master will support communications via its SeaTalk and SeaTalkng / NMEA 2000 communications ports.

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

Forum Jump:

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