OpenCPN NMEA input thru USB100 woes

[StoneCrab]

How about the port?

Are you sure which com port is assigned to the NMEA input on the PC? The GPS dongle gets assigned a COM port when the USB driver is loaded. Your NMEA communicaton should get a separate COM port. Since Windows 7 and 10 use virtual COM ports assignments are straightforward but you can see them in the Device Manager and a few of the other communication utilities.

I'd look at the active COM ports, read their descriptions and then try assigning OpenCPN to the COM ports one at a time until you hit some communications regardless of baud rate.

[AboardAdventurer]

I gave up on getting the USB100 to communicate with V5 via Serial. There is something funny going on, as it communicates perfectly with V4. I ended up utilizing GPSGate and establishing a TCP connection which performs flawlessly so far. Further, GPSGate allows me to use the bluetooth on my mini-pc to provide the same data to an android device with OpenCPN running on it at the same time. Double Bonus!


AA

[AboardAdventurer]

Following up with the Maretron USB100 impressions as they relate to OpenCPN integration, most of the issues previously identified in this thread have been resolved thru the use of TCP network protocol input, GPSGate and the NMEA Converter Plugin. For the relatively basic stuff, it is working fine and seems to be a very stable solution for bringing NMEA2k data into OC. Unfortunately, the USB100 has surprisingly limited functionality with the amount of PGN's it can translate to NMEA0183. I was attempting to get AIS to work this weekend and the USB100 doesn't support any AIS functions AT ALL!!



From the Maretron USB100 Manual:

Received NMEA 2000 PGN

Transmitted NMEA 0183 Sentence

126992 System Time

127245 Rudder Angle

127250 Vessel Heading

127251 Rate of Turn

127257 Attitude

127488 Engine Parameters, Rapid Update

127489 Engine Parameters, Dynamic

127505 Fluid Level

127508 Battery Status

128259 Speed

128267 Water Depth

128275 Distance Log

129025 Position, Rapid Update

129026 COG & SOG, Rapid Update

129029 GNSS Position Data

129029 GNSS Position Data

129033 Time & Date

129539 GNSS DOPs

129540 GNSS Sats in View

129540 GNSS Sats in View

130306 Wind Data

130310 Environmental Parameters

130311 Environmental Parameters

130576 Small Craft Status

As you can see, the list is actually quite limited. If you're running other Maretron hardware (as I am) and need access to setup information thru the USB100 interface, than you'll need this device regardless. If on the other hand you do not run any additional Maretron hardware, I would avoid using the USB100 as your NMEA2k to PC interface. I have ordered a Yacht Devices WiFi Gateway to supplement the USB100 functionality while also adding the ability to pick up the NMEA2k data remotely on a tablet. The YD hardware has a far more extensive list of supported PGN's so I'm excited to see how it all ties together. As an added bonus, YD has a browser-based configurable dashboard to supplement the information available directly thru OC.

I'll report on any issues getting the Yacht Devices YDWG-02 gateway implemented in this growing system I've got here...


AA

[EngNate]

Look at the NEMO Gateway from Rose Point - Check the translation list, it does AIS one way but not the other. Handy though because it gives an ethernet connection option too.

[teppokurki]

Shameless plug:

Signal K Node Server can also use YDGW input and translate from and to N2K and NMEA0183. It can provide further options like web dashboards and database based graphs.

Native support for Signal K input in OpenCpn is also in the works.

[s/v Jedi]

So, apart from AIS, what data are you missing? The problem with AIS is that at some point the 0183 stream can’t handle traffic load anymore. I have an Actisense converter that supports AIS but then restricts other sentences to make it work.

The Yacht Devices converters obviously don’t have this problem because they either don’t use a UART chip or one that is much faster, like 256kbps or more

Originally Posted by AboardAdventurer

Following up with the Maretron USB100 impressions as they relate to OpenCPN integration, most of the issues previously identified in this thread have been resolved thru the use of TCP network protocol input, GPSGate and the NMEA Converter Plugin. For the relatively basic stuff, it is working fine and seems to be a very stable solution for bringing NMEA2k data into OC. Unfortunately, the USB100 has surprisingly limited functionality with the amount of PGN's it can translate to NMEA0183. I was attempting to get AIS to work this weekend and the USB100 doesn't support any AIS functions AT ALL!!



From the Maretron USB100 Manual:

Received NMEA 2000 PGN

Transmitted NMEA 0183 Sentence


126992 System Time

127245 Rudder Angle

127250 Vessel Heading

127251 Rate of Turn

127257 Attitude

127488 Engine Parameters, Rapid Update

127489 Engine Parameters, Dynamic

127505 Fluid Level

127508 Battery Status

128259 Speed

128267 Water Depth

128275 Distance Log

129025 Position, Rapid Update

129026 COG & SOG, Rapid Update

129029 GNSS Position Data

129029 GNSS Position Data

129033 Time & Date

129539 GNSS DOPs

129540 GNSS Sats in View

129540 GNSS Sats in View

130306 Wind Data

130310 Environmental Parameters

130311 Environmental Parameters

130576 Small Craft Status

As you can see, the list is actually quite limited. If you're running other Maretron hardware (as I am) and need access to setup information thru the USB100 interface, than you'll need this device regardless. If on the other hand you do not run any additional Maretron hardware, I would avoid using the USB100 as your NMEA2k to PC interface. I have ordered a Yacht Devices WiFi Gateway to supplement the USB100 functionality while also adding the ability to pick up the NMEA2k data remotely on a tablet. The YD hardware has a far more extensive list of supported PGN's so I'm excited to see how it all ties together. As an added bonus, YD has a browser-based configurable dashboard to supplement the information available directly thru OC.

I'll report on any issues getting the Yacht Devices YDWG-02 gateway implemented in this growing system I've got here...


AA

[AboardAdventurer]

Originally Posted by EngNate

Look at the NEMO Gateway from Rose Point - Check the translation list, it does AIS one way but not the other. Handy though because it gives an ethernet connection option too.

Neat! Extremely expensive bit of kit, but it seems to be fairly loaded with useful features. I'm pretty committed to my current solution but others following this thread may look into Nemo further. Thanks for sharing.

Originally Posted by teppokurki

Shameless plug:

Signal K Node Server can also use YDGW input and translate from and to N2K and NMEA0183. It can provide further options like web dashboards and database based graphs.

Native support for Signal K input in OpenCpn is also in the works.

I would LOVE to play with signal K, but I'm not a programmer and with the small investment of additional hardware it isn't really on my radar, so to speak.

Originally Posted by s/v Jedi

So, apart from AIS, what data are you missing?

At the moment, nothing. If the USB100 had AIS I wouldn't need to make a change. I want as much of my data flowing over NMEA2k as possible instead of peacemealing 0183 and 2000 into a confusing system. The YD unit will likely be only responsible for AIS and possibly engine instrumentation integration via an Albacombi Analog-> NMEA2k box. The YD will also make all of the network data available over WiFi with presumably little fuss, so that opens up some additional possibilities once I get the base system ironed out.



AA

[StoneCrab]

I keep running across threads here where we are trying to connect proprietary equipment together to produce a comprehensive network. Sometimes the cabling is the issue. To that end, I am providing a link to a company that will build custom cables for you.

Check out this link: https://www.showmecables.com/cablebuilder

I am not affiliated with them. I just know that by the time you buy the right die for the crimpers, the right wire and connector, this is more time and cost efficient.