This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Display depth sounder scan data in OpenCPN / SignalK app
#2
NMEA0183 is not up to the task of decoding fishfinder information. That's not it's intent. With a fishfinder or other sounder device, there is usually a sonar module involved. I'm not familiar with your fishfinder, but when there is a sonar module involved (yours may be inside your unit, so I'll guess your transducer connects directly to the GPSMap?), there is usually some high bandwidth ethernet connection or video-type connection directly to or in the display. NMEA0183 is an ASCII text-based language that will never be able to decode that info. It's real purpose is to send the GPS & similar data it receives out to a VHF radio, laptop, or even SignalK. It operates at a very slow 4800 baud (0183HS is 38400 baud for AIS data).

Even DeviceNet (NMEA2000 at 250,000 baud) isn't up to the task of handling that big of data load. Fishfinders, like radars, require high-speed (ethernet or directly connected) interfaces with a device that understands how to decode that info.
Reply


Messages In This Thread
RE: Display depth sounder scan data in OpenCPN / SignalK app - by SCarns - 2021-07-18, 04:58 PM

Forum Jump:


Users browsing this thread: 1 Guest(s)