[CA] [CA11] Upgrades to my 2006 Four Winns

[Chuck - Raymarine - Moderator]

morowsky,

Q1. There are no NMEA 0183 connections to the existing S1 or anything on its SeaTalk backbone, so I do not believe that a loop will be an issue.
A1. While possible, it would be quite atypical that a system featuring an autopilot and a chartplotting product would not have been installed in a manner whereby these products were interfaced to one another. The S1 only supported two types of communications ... NMEA 0183 and SeaTalk. Typically, the S1 would have been interfaced to the C-Series Classic MFD via SeaTalk bus as is shown within your Original Wiring diagram.

Q2. Is this a workable design?
A2. I would recommend one change with respect to how the autopilot has been interfaced the new equipment. The S1 has a pair of SeaTalk ports. It is recommended that one of these ports be used to interface the S1 to the ST6001 alone. The second port of the S1 should then be interfaced to the SeaTalk (yellow) socket of the SeaTalk to SeaTalkng Converter. The red lead of the SeaTalk cable connecting the S1 to the SeaTalk to SeaTalkng Converter should not be connected to the red SeaTalk terminal of the S1. This method is recommended to 1) avoid creating a ground loop and 2) to provide a level degraded system capability onboard in the event of a failure within the SeaTalkng backbone whereby the autopilot may be operated with all other power circuits / devices switched OFF.

Q3. If I want to get better heading information for AIS and Radar, etc., could I add an EV-1 Sensor core (Conneccted to the SeaTalkng), and remove the Fluxgate Compass from the S1?
Q3a. Negative. The design of the S1/S1G/S2/S2G/S3/S3G are dependent upon having the autopilot course computer interfaced to the M81190 fluxgate compass or the a NMEA 0183 source of 10Hz stabilized heading data. While it would not do anything to improve the performance of the autopilot, you may want to consider including an AR200 Augmented Reality Sensor / GPS in place of the GA150 shown within your diagram. While it wouldn't improve autopilot performance, the stabilized attitude and heading data would support heading dependent calculations by the MFDs as well as providing a GPS data source to the system which would be independent of the power state of the MFDs. For the benefit of others viewing this FAQ whose systems feature i70/i70S Multifunction Instrument Display (MFID), ST70 MFID, p70/p70S/p70R/p70RS Autopilot Control Head, or ST70 Autopilot Control Head, please click here to view a FAQ addressing which device Data Sources should be configured via.

Q3b. Will the appropriate heading data needed by the S1 pass through the SeaTalk to SeaTalkng Conversion?
A3b. Negative. See the response to Q3a.

Q4. The Axiom Pro 9 is a RVX model. Will I be able to view RealVision 3D on the other MFD, a Axiom 9 without SONAR?
A4. As long as the Axiom Pro RVX MFD is powered ON and has been interfaced to a ReaVision 3D transducer, then it will indeed be possible to view RealVision 3D sonar imaging on the Axiom MFD.

Q5. Will or could there be issues with all the data (Heading, GPS, depth, AIS, etc.) on the SeaTalkng network getting onto the SeaTalk network?
A5. See the FAQ referenced above addressing the Data Sources feature. This feature is used to configure which data sources will be used by the system.