07-14-19, 09:14 AM
All,
Looking for confirmation that this combination actually works. I have a Raymarine MFD e120W with a Raystar 125 GPS and a Raymarine 240 VHF radio. I've followed every thread known to mankind on this combination. But yet... "no gps".
Here's what the cabling looks like:
GPS RS125 --> NMEA Cabling to the Seatalk/STNG Converter (white connector)
e120W/MFD --> NMEA Cabling to the same SeaTalk/STNG Converter (white Connector)
240 VFF --> 3 Pin SeaTalk cable spliced to remove the red wire (power) and connected the yellow to yellow, screen to screen --> connected to th SeaTalk/STNG Converter (Yellow connector).
The only variable i can see in my combination preventing this from working is that the Software Code on the VHF is 2.20. I noticed in the release notes that the v2.23 (Dec 2010) has a note that says "SeaTalk1 communications issue resolved during power up".
Anyone have the same setup that could confirm/deny ??? when we purchased this boat many years ago -- we thought it was just a glitch, but the more and more i look into this - it appears to be a bug.
Looking for confirmation that this combination actually works. I have a Raymarine MFD e120W with a Raystar 125 GPS and a Raymarine 240 VHF radio. I've followed every thread known to mankind on this combination. But yet... "no gps".
Here's what the cabling looks like:
GPS RS125 --> NMEA Cabling to the Seatalk/STNG Converter (white connector)
e120W/MFD --> NMEA Cabling to the same SeaTalk/STNG Converter (white Connector)
240 VFF --> 3 Pin SeaTalk cable spliced to remove the red wire (power) and connected the yellow to yellow, screen to screen --> connected to th SeaTalk/STNG Converter (Yellow connector).
The only variable i can see in my combination preventing this from working is that the Software Code on the VHF is 2.20. I noticed in the release notes that the v2.23 (Dec 2010) has a note that says "SeaTalk1 communications issue resolved during power up".
Anyone have the same setup that could confirm/deny ??? when we purchased this boat many years ago -- we thought it was just a glitch, but the more and more i look into this - it appears to be a bug.