Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[CA11] Feedback request on proposed SeaTalkNg on Regal 3560
12-20-19, 11:15 AM
Post: #2
RE: [CA11] Feedback request on proposed SeaTalkNg on Regal 3560
Welcome to the Raymarine Forum John,

Q1. Attached is my proposed network layout. If anyone can validate or point out issues, I would be very grateful!
A1. Nice job on the diagram. From the standpoint of a properly powered and terminated NMEA 2000 backbone constructed from SeaTalkng networking components, the diagram is correct. The Yacht Devices Engine Gateway YDEG-04 appears to have been terminated with a DeviceNet (M) socket (just like your MFD). Accordingly, an A06045 SeaTalkng to DeviceNet (F) Adapter will be required for each Yacht Devices Engine Gateway installed. Unfortunately, I can't weigh in on whether the Yacht Devices engine interfacing components selected are correct and would recommend that the compatibility of these components be verified with Yacht Devices.

The YDWG-02R model of Yacht Devices NMEA 2000 to WiFi Gateway features a SeaTalkng spur plug. Alternatively, the YDWG-02N model of Yacht Devices NMEA 2000 to WiFi Gateway may be adapted to be connected to a spur socket within the backbone.

Q2. Will the SeaTalk 1 devices pull power from the SeaTalkNg backbone or will they need seperate 12v power
A2. SeaTalk1 devices will be powered by the SeaTalkng / NMEA 2000 backbone via a system's SeaTalk to SeaTalkng Converter(s).

Q3. Will this setup allow my SeaTalkNg/Nema2k network to see and use the data from the two SeaTalk 1 devices (Depth and Rudder sensor).
A3. Yes.
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
RE: [CA11] Feedback request on proposed SeaTalkNg on Regal 3560 - Chuck - Raymarine - Moderator - 12-20-19 11:15 AM

Forum Jump:


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