Bill Kearney wrote:
what annoys me the most about NMEA is that the organization says it was
formed to arrive at some sort of standardization, and so NMEA 0183, and
now 2000. However, the bozos at Raymarine have decided to make
SeaTalk, just to muddy the waters. Want to connect a Garmin? Sure,
that's where the NMEA standard is supposed to work, but instead, we
have to buy a multiplexer so that these gadgets can network. So, based
on NMEAs own mission statement, they are a failure.

Oh please, that's ridiculous. Technology has significantly changed since
NMEA-0183 was started. What it sought to accomplish at the time was quite
ambitious. Likewise for the NMEA-2000 spec. That 0183 didn't do what
Raymarine NEEDED meant they had to implement something else, but also
supported the 0183 spec. Likewise for the 2000 spec. The hassle with the
2000 spec has been the delay in standardizing the hardware connection (now
done). But it's trivial to splice from a SeaTalk2, LowranceNet and Micro-C
connector and have it all "just work". I know, I've done it.

So if all your looking to do is whinge, well, keep at it.


Concur. Progress of what's possible makes even keeping everything
interoperable within a single manufacturer hard.

Raymarine had just Seatalk (v1) for a long while, with NMEA on some
hardware to exchange data with other brands, but now we have Seatalk2
(=NMEA2000= 1Mb CANbus) and SeatalkHS (=100 Mb Ethernet). So far so
good. However, their old implementation of ST2 (ST-290 range of
instruments) is apparently not compatible with ST2 as implemented in the
newer E-series displays: the documentation examples and notes tell you
NOT to link ST-290 to the E-series through ST2 but thru ST1!