[CA] [CA11] Heading Info on E120 Classic
|
07-26-19, 10:14 AM
(This post was last modified: 07-31-19 11:41 AM by Chuck - Raymarine - Moderator.)
Post: #1
|
|||
|
|||
[CA11] Heading Info on E120 Classic
The heading data from my fluxgate compass runs to Raypilot650 via cable from the S3. It's the only connection to the 650, and I'm wondering if I could connect the second SeaTalk outlet on the 650 to my E120 Classic, since the Heading box on the Databar is blank. The 650 does show a Heading reading.
|
|||
07-31-19, 11:42 AM
Post: #2
|
|||
|
|||
RE: [CA11] Heading Info on E120 Classic
Welcome to the Raymarine Forum seeray96,
What model of Raymarine autopilot course computer has your RayPilot 650 Autopilot Control Head been interfaced to? |
|||
08-08-19, 11:14 AM
(This post was last modified: 08-08-19 12:27 PM by Chuck - Raymarine - Moderator.)
Post: #3
|
|||
|
|||
RE: [CA11] Heading Info on E120 Classic
Model S3, (E15014R, s/n E15014, mfd 8/06).
|
|||
08-08-19, 12:31 PM
(This post was last modified: 08-08-19 12:32 PM by Chuck - Raymarine - Moderator.)
Post: #4
|
|||
|
|||
RE: [CA11] Heading Info on E120 Classic
seeray96,
Q. I'm wondering if I could connect the second SeaTalk outlet on the 650 to my E120 Classic A. As long as the MFD's NMEA 0183 port has not been interfaced to the autopilot, then the MFD's SeaTalk port may indeed be interfaced to the S3 autopilot course computer's second SeaTalk port. Doing so would have the added advantage of not only displaying heading data, but also permitting use of the autopilot's Track mode after navigation has been commanded by the MFD (i.e. Go To Waypoint/Cursor or Follow Route). |
|||
08-24-19, 02:08 PM
(This post was last modified: 08-26-19 08:10 AM by Chuck - Raymarine - Moderator.)
Post: #5
|
|||
|
|||
RE: [CA11] Heading Info on E120 Classic
Q. Both SeaTalk outputs on the S3 are already used. That's why I thought the 650 to E120 Classic would be easy.
|
|||
08-26-19, 08:17 AM
Post: #6
|
|||
|
|||
RE: [CA11] Heading Info on E120 Classic
seeray96,
Unless interfaced to the vessel's engine system to permit monitoring of engine data, it would seem odd that both the MFD's SeaTalk socket and SeaTalk2/NMEA 2000 socket would currently be in use. In order to properly advise you regarding how the equipment should be interfaced, it would be necessary to learn the complete list of devices within your system and how they had been interfaced to one another. Please attach a system diagram (hand drawn will suffice) of your system for analysis. The system diagram should list all devices with the vessel's marine electronics system and how they have been interfaced to one another. |
|||
08-26-19, 12:24 PM
(This post was last modified: 08-27-19 09:26 AM by Chuck - Raymarine - Moderator.)
Post: #7
|
|||
|
|||
RE: [CA11] Heading Info on E120 Classic
Thanks, Chuck. I'll forward the info as soon as I get it all traced. For what it's worth, there's no connection to the SeaTalk/Alarm port on the E120 Classic.
|
|||
08-27-19, 09:38 AM
Post: #8
|
|||
|
|||
RE: [CA11] Heading Info on E120 Classic
seeray96,
As indicated within my earlier response, it would seem odd that both the MFD's SeaTalk socket and SeaTalk2/NMEA 2000 socket. However, as you have indicated that there is presently nothing interfaced to the MFD's SeaTalk/Alarm port, then this port may indeed be used to interface the MFD to the Raypilot 650's remaining SeaTalk port (or to the S3 autopilot's second SeaTalk port not only supply the MFD with 1Hz heading data, but also to support the autopilot's Track mode feature. The latter two options would require that the system not feature a SeaTalk to SeaTalkng Converter (may or may not be part of a more extensive SeaTalkng / NMEA 2000 backbone) to which both the MFD and S3 autopilot course computer have been interfaced. |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)