Thread Closed 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Interfacing a non-Data Master MFD to the SeaTalkng backbone or SeaTalk bus
03-09-17, 12:05 PM (This post was last modified: 03-09-17 12:06 PM by Chuck - Raymarine - Moderator.)
Post: #1
Interfacing a non-Data Master MFD to the SeaTalkng backbone or SeaTalk bus
Interfacing a non-Data Master MFD to the SeaTalkng backbone or SeaTalk bus

In systems featuring more than one MFD which is designed to be interfaced with other compatible MFDs via an Ethernet network, only the MFD which has been configured as the system's Data Master MFD will have an active SeaTalkng and/or SeaTalk port(s). Accordingly, the MFD which has been configured as the system's Data Master MFD must be interfaced to the system's SeaTalkng backbone or SeaTalk bus. The Data Master MFD will then serve as the bridge between the other MFDs and the SeaTalkng backbone or SeaTalk bus.

Should there be
- a desire to add a level of redundancy within the system or
- should the concept of operation for the vessel's system include periodically configuring one of the system's other compatible MFDs as the system's Data Master MFD,
then more than one of the system's MFDs may be interfaced to the SeaTalkng backbone or SeaTalk bus. In this way, should
- the system's primary Master MFD suffer a failure, or
- should it be desired to be switch the system's primary Master MFD off to reduce the number of MFDs being powered within the system,
then the other MFD which has been interfaced to the SeaTalkng backbone or SeaTalk bus may be configured as the system's Data Master MFD to support communications with the SeaTalkng backbone and/or SeaTalk bus.


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