Autohelm 100/300 autopilot
|
11-21-16, 10:55 PM
Post: #1
|
|||
|
|||
Autohelm 100/300 autopilot
I understand that the eS127 supports the SG3 autopilot using the Seatalk to SeatalkNG converter.
The existing Autohelm 100/300 and the SG3 autopilots both work perfectly with the ST50+ instruments and control heads using Seatalk. Can the eS127 connected to the Autohelm 100/300 using the Seatalk to SeatalkNG converter control the autopilot? At the FT Lauderdale show, Raymarine tech said that there is no difference in the Seatalk between the Autohelm 100/300 and the SG3. |
|||
11-23-16, 01:19 PM
(This post was last modified: 11-23-16 01:23 PM by Chuck - Raymarine - Moderator.)
Post: #2
|
|||
|
|||
RE: Autohelm 100/300 autopilot
Welcome to the Raymarine Forum Lazybones,
SeaTalk communications protocol changes were introduced with the ST50+ Instruments. Products having communications interfaces which had been programmed to support the earlier SeaTalk communications protocol (ex. ST50 Instruments, Type 100/300 autopilot course computer, etc.) would not be recommended to be interfaced to a SeaTalk to SeaTalkng Converter. Accordingly, while ST50+ Instruments may be interfaced to an a/c/e/eS/gS-Series MFD via a SeaTalk to SeaTalkng Converter, it is recommended that Type 100/300 autopilot course computers be interfaced via NMEA 0183 communications to Raymarine's a/c/e/eS/gS-Series MFDs. |
|||
11-23-16, 04:11 PM
Post: #3
|
|||
|
|||
RE: Autohelm 100/300 autopilot
Thank you.
When interfacing the eS series with the Autohelm 100/300 via NMEA, will the eS series be able to control the 100/300 autopilot? If so, is this also true then for the SG3 autopilot? |
|||
11-23-16, 04:23 PM
Post: #4
|
|||
|
|||
RE: Autohelm 100/300 autopilot
Lazybones,
While it would be possible for an autopilot which had been interfaced via NMEA 0183 communications protocol to receive data from the MFD to support using the autopilot's Track mode feature, the autopilot control head would need to be used to command the autopilot into track mode ... as it would with earlier generations of MFDs. The autopilot course computer designs featuring a SeaTalk communications interface which followed the 100/300 course computer (ex. S1, S1G, S2, S2G, S3, S3G) may be interfaced to a SeaTalkng backbone via a SeaTalk to SeaTalkng Converter (updated w/v1.21 software) to not only support using the autopilot's Track mode feature, but to also use the MFD's Autopilot Controls feature which would support having the MFD itself command the autopilot into Auto, Track, and Standby modes. |
|||
11-23-16, 05:22 PM
Post: #5
|
|||
|
|||
RE: Autohelm 100/300 autopilot
Thank you.
I now understand that the 100/300 must use itsb own control head to enable track mode. Will the es127 MFD using NMEA interface to the SG3 instead of Seatalk/SeatalkNG, be able to utilize the track control from the MFD? or is it required to utilize the Seatlak to SeatalkNG converter to accomplish this? |
|||
11-23-16, 05:30 PM
Post: #6
|
|||
|
|||
RE: Autohelm 100/300 autopilot
Lazybones,
Use of an a/c/e/eS/gS-Series MFD's Autopilot Controls feature requires that a compatible autopilot be interfaced to the MFD via SeaTalkng as a direct spur or via a SeaTalk to SeaTalkng Converter. As such, should one opt to interface a S3G autopilot course computer to an a/c/e/eS/gS-Series MFD via NMEA 0183 communications, then the a/c/e/eS/gS-Series MFD's Autopilot Controls features would not be supported ... instead, it would be necessary to use the autopilot's control head to command it into Auto, Track, or Standby modes. |
|||
11-23-16, 05:33 PM
Post: #7
|
|||
|
|||
RE: Autohelm 100/300 autopilot
Thank you.
|
|||
11-23-16, 06:24 PM
Post: #8
|
|||
|
|||
RE: Autohelm 100/300 autopilot
You're welcome.
|
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 3 Guest(s)