[CA] [CA11] Networking
|
01-30-19, 03:29 PM
(This post was last modified: 01-30-19 03:29 PM by Chuck - Raymarine - Moderator.)
Post: #2
|
|||
|
|||
RE: [CA11] Networking
Welcome to the Raymarine Forum MB,
Using the key word "diagram" in conjunction with Forum's Search feature to search the Forum's Networking will provide a list of system diagrams which have been previously posted to this Forum. While we don't have a single diagram which includes each of the devices which you have listed, you should be able to see that the MFDs, fishfinder sounder module, and radar transducer will be interfaced to one another via an Ethernet communications network. In its simplest form, this Ethernet network may be constructed by connecting the MFDs to one another via an appropriate length of RayNet (F) to RayNet (F) Cable. The fishfinder sounder module would then be connected to either of the MFDs via an appropriate length of RayNet (F) to RayNet (F) Cable. A Digital Radar Cable (combines power and Ethernet communications within a single cable) would then be used to connect the HD radar to the remaining Ethernet Network socket of one of the MFDs. Alternatively, a HS5 RayNet Network Switch may be installed. In the case of latter, each MFD and the CP370 would instead be interfaced to the HS5 RayNet Network Switch via an appropriate length of RayNet (F) to RayNet (F) Cable. Similarly, the Digital Radar Cable would be interfaced to the HS5 RayNet Network Switch. With regard to the remaining devices which you have listed, a powered and properly terminated SeaTalkng / NMEA 2000 backbone will be need to be constructed onboard. This backbone will need to have a sufficient number of spur sockets to accommodate interfacing a SeaTalkng Power Cable, the Data Master MFD, EV-1 CCU, ACU-300, and p70S/p70RS autopilot control head each as individual spurs to the backbone. The Data Master a/c/e/eS/gS-Series MFD will interface to a spur socket within the backbone via an appropriate length of SeaTalkng spur cable. As the SeaTalkng / NMEA 2000 communications interface of the Axiom / Axiom Pro / Axiom XL MFDs is terminated with a male DeviceNet Micro-C plug/socket, a SeaTalkng to DeviceNet (F) Adapter Cable will be used to mate the Data Master Axiom / Axiom Pro / Axiom XL MFD to a spur socket within the backbone. I recommend that you look at the gS165(4), RMK-9, i70, DT800, CP470C, B175 Pair,Dual RS130 GPS,12KW SHD Open, EV- 300 diagram to view how the Data Master MFD and EV300 would be interfaced to one another via a SeaTalkng backbone which has been constructed from SeaTalkng networking components. I recommend that you look at the eS128(2), CPT-100, RD424HD 4KW Radome, CP-200, Fusion diagram to view how the MFDs, HD radar, and CP370 (interfaces identically to the CP100) would be interfaced to one another via an Ethernet communications network. |
|||
« Next Oldest | Next Newest »
|
Messages In This Thread |
[CA11] Networking - Plowin - 01-28-19, 10:11 PM
RE: [CA11] Networking - Chuck - Raymarine - Moderator - 01-30-19 03:29 PM
RE: [CA11] Networking - Papa Ralph - 03-23-19, 02:41 PM
RE: [CA11] Networking - Chuck - Raymarine - Moderator - 03-25-19, 09:20 AM
RE: [CA11] Networking (Axiom to S1 AutoPilot) - Papa Ralph - 07-12-19, 07:20 PM
RE: [CA11] Networking - Chuck - Raymarine - Moderator - 07-16-19, 02:42 PM
|
User(s) browsing this thread: 5 Guest(s)