Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[CA11] Upgrading to Axioms from C80
04-21-19, 09:52 PM (This post was last modified: 04-24-19 12:44 PM by Chuck - Raymarine - Moderator.)
Post: #1
[CA11] Upgrading to Axioms from C80
Chuck,

I'm upgrading to an Axiom 9RV, RD424HD and Axiom 7DV. I plan to keep my existing Auto Pilot and would like to interface everything together. I don't know the model number of the existing GPS antenna, but it is NMEA 183 and presently is tied in through the Smart Pilot. Please take a look at this network diagram and tell me if I need to make any changes.

Thanks for your help!

Mark


Attached File(s)
.pdf  NMEA 200 network.pdf (Size: 228 KB / Downloads: 14)
Find all posts by this user
Quote this message in a reply
04-24-19, 01:56 PM (This post was last modified: 04-24-19 02:03 PM by Chuck - Raymarine - Moderator.)
Post: #2
RE: [CA11] Upgrading to Axioms from C80
Welcome to the Raymarine Forum Mark,

Your system diagram incorrectly indicates how the system's autopilot components are to be interfaced to the SeaTalk to SeaTalkng Converter. Please click here to view a FAQ addressing this subject. In a nutshell, the autopilot control head should be interfaced to one of the autopilot course computer's SeaTalk ports. The other SeaTalk port of the autopilot course computer will be interfaced to the SeaTalk to SeaTalkng Converter's SeaTalk (yellow) socket.

Your system diagram incorrectly indicates that the SeaTalk to SeaTalkng Converter and a portion of what you have labeled as "NMEA 2000" (i.e. the engine side backbone) may be interfaced to the system's HS5 RayNet Network Switch. Please click here to view a FAQ addressing adapting devices having a NMEA 0183, SeaTalk, or SeaTalkng / NMEA 2000 to a Raymarine Ethernet (SeaTalkhs / RayNet) network. As indicated within the referenced FAQ, it is the function of the Data Master MFD to bridge data from the marine electronics SeaTalkng / NMEA 2000 network to the systems Ethernet network for use by the system's MFDs. Accordingly, the connections to the HS5 RayNet from the SeaTalk to SeaTalkng Converter and from the engine side NMEA 2000 backbone should be removed. In this case, only the Axiom MFD and the Digital Radar Cable should be connected to the HS5 RayNet Network Switch.

Essentially, the system will consist of two powered and properly terminated NMEA 2000 backbones ... one will be for the marine electronics (to include the VHF radio and stereo) and the other will be for the engine equipment. The marine electronics backbone will be constructed from SeaTalkng Networking components. These backbones will communicate with one another via a NMEA 2000 engine gateway. Please click here to view a FAQ addressing how engine systems may be interfaced to Axiom MFDs. As such, system diagram incorrectly shows that the VHF radio and stereo should be interfaced to your engine side NMEA 2000 backbone. The VHF radio and stereo, along with the system's Data Master MFD, should instead be interfaced to spur sockets within the marine electronics backbone. Please click here to view a FAQ addressing how additional spur sockets may be added to a marine electronics backbone which has been constructed from SeaTalkng Networking components. Finally, please click here to view a FAQ addressing how devices having NMEA 2000 ports which have been terminated with a DeviceNet plug/socket (ex. Data Master Axiom MFD, stereo, DSC VHF radio) may be adapted to be mated to a SeaTalkng spur socket.
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


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

Contact Us