[CA] Navionics Platinum+ maps shared between Axiom displays?

[Chuck - Raymarine - Moderator]

DRFASailboater,

General comments regarding the system diagram:
- It should be noted that the backbone's power insertion spur socket is not located at the approximate mid-point of the backbone's LEN load ... in fact, it appears to be located at the extreme end of one side of the backbone. Our recommended best installation practice calls for powering the backbone via a dedicated 12VDC switched circuit having an insertion point at the approximate mid-point of the backbone's LEN load.
- Within the center of the diagram, a SmartController Wireless Autopilot Controller and its wireless base station is shown. The diagram incorrectly shows the SmartController's wireless base station being interfaced as a spur to the backbone. SmartController's wireless base station must be interfaced to the SeaTalk socket of a SeaTalk to SeaTalkng Converter which has been updated with the latest available product software.

Comments regarding the Diagnostics...json file (Devices list):
- The software within the following components has not been updated with latest available Raymarine product software update and should be updated accordingly:
----- one of the SeaTalk to SeaTalkng Converters (S/N 1240884)
----- EV-1 autopilot course computer ... please click here to view a FAQ addressing actions to be taken after updating Evolution autopilot software.

- Only devices which have been interfaced as spurs to the backbone and/or have been interfaced to the system via an Ethernet network will be listed. As RayMics are not designed to be interfaced directly to the backbone (the interface to the Ray260), they will not be listed via this diagnostics feature.

- Logs may be created as a result of software errors/crashes. If the Save Logs option specifies (0), then no logs have been generated and this diagnostic feature may be skipped.

After addressing the items listed above, should the problem with the MicroTalk persist (although off topic ... thread was started to address Navionics chart sharing), then please respond accordingly.