Raystar 125 wrong year

From what I have seen on a 3 day trip, tides and route calculations are affected.
The only way to check tides now is to open the tide data from the tidal diamond (or animation) and then change the date which works only until you revert the display back to normal.
Knock on effects are if the gps data feeds a navtex receiver such as the ICS one.
 
From what I have seen on a 3 day trip, tides and route calculations are affected.
The only way to check tides now is to open the tide data from the tidal diamond (or animation) and then change the date which works only until you revert the display back to normal.
Knock on effects are if the gps data feeds a navtex receiver such as the ICS one.
Ooops, thanks very much for that. I didn't realise it did tideso_O(y)
I think the answer for my system is replace the 125 with a Raystar 150 and connected via a Seatalk1 to SeatalkNG converter??
 
Hi.
I have a Camino 108 transponder which as well as its own gps sensor also takes the fast heading data from my S2 course computer. This fast heading is multiplexed with the ais data. The is also an option to add the gps (currently disabled) to this data stream. All this goes to the single nmea input on the C80 at 34800. So far so good. I have a raymarine seatalk/nmea convertor which currently takes the seatalk data (including the RS125) and outputs this to nmea which gives position data to my disc radio and also feeds an ICS Navtex receiver which also acts as a repeater and log. This is the area where I am trying to find out how to get the nmea data stream to the ICS unit to include the nav data as well as the gos from the Camino as without correct date/time the trip log as well as navtext messages do not work.
I do have a second nmea output on the Camino unit which can be programmed to 4800 baud, so I guess the issue is combining the raymarine seatalk/nmea data to also include the new gps source.
It would have been so easy if the C80 rebroadcast the nmea input across seatalk!

I also have a Quark A031 which currently is used to multiplex seatalk and the ais output from the Camino and transmit the data via its wifi. It might be possible to program the output of the nmea on the quark to 4800. Not sure if the ais data stream will swamp this though....
 
Last edited:
Hi.
I have a Camino 108 transponder which as well as its own gps sensor also takes the fast heading data from my S2 course computer. This fast heading is multiplexed with the ais data. The is also an option to add the gps (currently disabled) to this data stream. All this goes to the single nmea input on the C80 at 34800. So far so good. I have a raymarine seatalk/nmea convertor which currently takes the seatalk data (including the RS125) and outputs this to nmea which gives position data to my disc radio and also feeds an ICS Navtex receiver which also acts as a repeater and log. This is the area where I am trying to find out how to get the nmea data stream to the ICS unit to include the nav data as well as the gos from the Camino as without correct date/time the trip log as well as navtext messages do not work.
I do have a second nmea output on the Camino unit which can be programmed to 4800 baud, so I guess the issue is combining the raymarine seatalk/nmea data to also include the new gps source.
It would have been so easy if the C80 rebroadcast the nmea input across seatalk!
See if the NMEA input gets sent out over Seatalk, i might be wrong.

The 4800 port on the Camino should send GPS data to the VHF and the ICS

Do you have any ST60 displays with NMEA connections ?
 
See if the NMEA input gets sent out over Seatalk, i might be wrong.

The 4800 port on the Camino should send GPS data to the VHF and the ICS

Do you have any ST60 displays with NMEA connections ?
Hi Paul.
I think I have quite a list of things to try now.
1. See if the nmea multiplexed data does get retransmitted on the seatalk bus. I vaguely remember some article that indicated it would do this with caveats that not all data would be rebroadcast and also that there was a restricted number after the decimal point which reduced accuracy.
2. Try the unused nmea output on my camino muktiplexor ( I added this to my previous post).
3. See if I can connect the gps sensor to my ST60+ graphic display which has nmea and claims to support position data.
4. I have an S2 course computer with nmea inputs - maybe try connecting an nmea gps to this if it is retransmitted to the seatalk bus?
 
Last edited:
Expensive solution!

How about a NMEA 0183 GPS, connected to port 3 of the plotter ?
Many thanks Paul.
My plotter is at the aft end of the cockpit table in a twin wheel cockpit and I have honestly no idea how to get wires into that but it would involve a lot of destruction and swearing.
I have a dedicated Raymarine NMEA GPS antenna feeding into the Raymarine 650 AIS transceiver but the manual for the 650 continually says just use it for that and don't connect it into the Seatalk system so I assume (a) I cannot do that and (b) I cannot also connect a (new) different GPS NMEA antenna elsewhere in the Seatalk system? [I realise the question might be a nonsense question to somebody that knows what they are talking about !]
 
I have now had some feedback from Raymarine which may assist anyone else facing similar issues.

1. First options and limitations
You can connect a current NMEA1083 GPS (i.e. Digital Yacht do one) to either the input port of the S2G or the autopilot control head (if it has the NMEA0183 connections on - not all control head models had this). From here, providing the S2G is connected, you can pass lat/long/time (GGA/GLL). However, date is not passed and therefore you wont get ant more benefits that leaving the RS125 connected (i.e. tide and currents needs date).

2. Second option 'should' work
The ST60 Multi can take in GLL and GGA and output RMC (which should include date on SeaTalk 1

ST60 NMEA.jpg

ST60 NMEA.jpg

However, as I don't have an ST60 multi here I cannot test this out

3. Using the AIS data stream at 38400 to include its GPS feed from its dedicated GPS receiver.
Strictly speaking, AIS units should not be set to output their GPS (various reasons, the main one being network latency and data loops). However, in theory, the answer is yes

Hope this may clarify things a bit.
 
Last edited:
I have now had some feedback from Raymarine which may assist anyone else facing similar issues.

1. First options and limitations
You can connect a current NMEA1083 GPS (i.e. Digital Yacht do one) to either the input port of the S2G or the autopilot control head (if it has the NMEA0183 connections on - not all control head models had this). From here, providing the S2G is connected, you can pass lat/long/time (GGA/GLL). However, date is not passed and therefore you wont get ant more benefits that leaving the RS125 connected (i.e. tide and currents needs date).

2. Second option 'should' work
The ST60 Multi can take in GLL and GGA and output RMC (which should include date on SeaTalk 1

69a2b4c3f3fd4bb4b01399c3c7204f2a


However, as I don't have an ST60 multi here I cannot test this out

3. Using the AIS data stream at 38400 to include its GPS feed from its dedicated GPS receiver.
Strictly speaking, AIS units should not be set to output their GPS (various reasons, the main one being network latency and data loops). However, in theory, the answer is yes

Hope this may clarify things a bit.
Brilliant bit of work - many thanks.
I believe I have a ST60 Graphic and the manual suggests that does the same thing as the Multi ie takes in NMEA (and puts it out as well)
 
Sorted.
The C90W has an internal GPS. I turned this 'ON'. It promptly lost the signal from the R125 and then it found a fix from the internal GPS which provided the correct date and time and provided a differential GPS position.
 
Top