March 4, 2007 18:39
Thank you for the clarification on how GPS repeat works.
Here is the configuration that I am using:
GPS NMEA source ----->> AIS receiver ----->> Keyspan (1)----->> MAC
(RM SC520)
Instrument NEMA ------------------------------->> Keyspan (2)----->> MAC (RM Seatalk --> NMEA box)
The sentences on Keyspan(1) contain both GPS and AIS information. I assume "GPS repeat" filters out the AIS sentences and either re-transmits the GPS sentences received (when there is no Waypoint set in MacENC) or transmit MacENC generated sentences when a waypoint is set in MacENC. IMHO, GPS repeat mode should have a preference to filter out any non-GPS sentences recieved in the GPS panel.
The sentences on Keyspan (2) contains instruments + anything else that is flying around the Seatalk bus - GPS data, waypoint data, autopilot data, rubber angle etc. This is the reason filtering is need in the TCP/IP consolidation - to remove the non-instrument data.
Here is the configuration that I am using:
GPS NMEA source ----->> AIS receiver ----->> Keyspan (1)----->> MAC
(RM SC520)
Instrument NEMA ------------------------------->> Keyspan (2)----->> MAC (RM Seatalk --> NMEA box)
The sentences on Keyspan(1) contain both GPS and AIS information. I assume "GPS repeat" filters out the AIS sentences and either re-transmits the GPS sentences received (when there is no Waypoint set in MacENC) or transmit MacENC generated sentences when a waypoint is set in MacENC. IMHO, GPS repeat mode should have a preference to filter out any non-GPS sentences recieved in the GPS panel.
The sentences on Keyspan (2) contains instruments + anything else that is flying around the Seatalk bus - GPS data, waypoint data, autopilot data, rubber angle etc. This is the reason filtering is need in the TCP/IP consolidation - to remove the non-instrument data.