AXIOM MFD Instead of a95
|
02-16-17, 05:52 PM
(This post was last modified: 02-17-17 10:38 AM by Chuck - Raymarine - Moderator.)
Post: #2
|
|||
|
|||
RE: AXIOM MFD Instead of a95
Welcome to the Raymarine Forum Tamrow,
Please click here to view a FAQ addressing how your VHF radio / AIS receiver will need to be interfaced to the system. The GA150 shown within your diagram will need to be replaced with a Raystar 150 GPS Sensor. Finally, the SeaTalkng backbone (presently created by and limited to the SeaTalk to SeaTalkng Converter) will be expanded to include at least two additional spur sockets ... one to accommodate the NMEA 0183 to SeaTalkng/NMEA 2000 data bridging devices, and the second to accommodate the Raystar 150 GPS Sensor. Please click here to view a FAQ addressing how to add additional spur sockets to a SeaTalkng backbone. As the Axiom MFDs feature a DeviceNet Micro-C (M) plug for interfacing the Data Master MFD to a SeaTalkng / NMEA 2000 backbone, the Axiom MFD will need to be interfaced as a spur to the SeaTalkng backbone via an A06045 15.7in (0.4m) DeviceNet (F) to SeaTalkng Spur Adapter or an A06075 39.4in (1.0m) DeviceNet (F) to SeaTalkng Adapter. While no changes to the diagram would be directly associated with replacing the RMK-9 with a RMK-10, it will be necessary to instead interface each MFD and the RMK-10 to a HS5 RayNet Network Switch. Please click here to view a FAQ addressing this subject. Transducers cannot be mated to an i70/i70S MFID. The transducers used with your ST60 Tridata would need to be interfaced to a iTC-5 Analog Instrument Converter which would be installed a component of the backbone (i.e. not as a spur). The i70/i70S would then be interfaced to a spur socket within the backbone. |
|||
« Next Oldest | Next Newest »
|
Messages In This Thread |
AXIOM MFD Instead of a95 - Tamrow - 02-16-17, 04:51 PM
RE: AXIOM MFD Instead of a95 - Chuck - Raymarine - Moderator - 02-16-17 05:52 PM
|
User(s) browsing this thread: 1 Guest(s)