Just updated - watchdog STILL not receiving depth data

[GreenHeaven]

2yrs and counting... how is this possible?

Is it too much to ask for this vital plug in to be able to see the depth data clearly displayed in opencpn...


Windows PC - Network wifi connection GPSD 0183 data flowing nicely

[Corsair63]

Originally Posted by GreenHeaven

2yrs and counting... how is this possible?

Is it too much to ask for this vital plug in to be able to see the depth data clearly displayed in opencpn...


Windows PC - Network wifi connection GPSD 0183 data flowing nicely

Check the Depth input in OCPN, in the NMEA data display of the program filter the sentences DPT, and compare them with below info.

also follow this thread, https://www.cruisersforum.com/forums...150313-38.html in the last messages.

it could happens to you same as me, your echo-sounder maybe is transmitting in NMEA 3.0 with some data in the scale parameter and it won't show the depth.

$SDDPT,3.3,0.0,9999.9*6C - doesn't work (ver 3.0)

$SDDPT,3.25,0.00,*7F - works (ver 3.0)

$SDDPT,3.1,0.0*55 - works (ver 2.0)

FTB if NMEA library of plugin is not updated try to exchange the Echo-sounder NMEA output to ver 2.0 and you'll have depth display in OCPN and in Watchdog plugin.

[GreenHeaven]

Thank you so much for that response!!!

I have depth mssages that look like this


<GREEN>21:43:55 (GPSD:192.168.1.100:2000) $IIDBT,42.0,f,12.8,M,7.0,F*1B<0x0D><0x0A>

These 0183 messages are transcoded from old raymarine sensor putting out seatalk by a multiplexer.

I guess I dont understand how OpenCPN can read it without out a problem, yet Watchdog cant.

If this is a simple parsing task, then pls send me the relevant dll code and ill write a parser. Better yet, Ill compile a very lightwieght ASM 32bit dll you can load at run time. and call a parsing function in that.

A parser is a trivial task to implement once you understand the structure of this software and plug in.

Depth has to be the single most important piece of data in a boat esp at anchor!
How has this gone unaddressed for so long?

[wholybee]

Greenheaven:
Note that the sentence you provided is "Depth Below Transducer"(DBT) not "Depth"(DPT) as the example Corsair63 has given. That is probably why the Watchdog plugin doesn't understand it.

You could translate that with the NMEAConverter plugin. No need to write your own code.

[Corsair63]

AFAIK Warren says the watchdog plugin only understand sentence DPT, what he says about translating with NMEAconverter plugin could resolve the problem.

but really strange that your devices doesn't provide with DPT sentence.

[bdbcat]

"How has this gone unaddressed for so long?"
Probably because no-one else is using "$xxDBT" sentence with watchdog.
Somebody had to be first, and you are it.


Dave

[GreenHeaven]

Originally Posted by bdbcat

"How has this gone unaddressed for so long?"
Probably because no-one else is using "$xxDBT" sentence with watchdog.
Somebody had to be first, and you are it.


Dave

first to raise the issue I believe you meant to say WINK

[GreenHeaven]

Originally Posted by Corsair63

AFAIK Warren says the watchdog plugin only understand sentence DPT, what he says about translating with NMEAconverter plugin could resolve the problem.

but really strange that your devices doesn't provide with DPT sentence.

I just buy the standard pieces and plug em together and this is what comes out

The transplexer is Quark device and they are fully OpenCPN aware so I presume they take the raymarine fagtalk and convert it properly. what do I know

I will add that if you are going to add depth, probably should go through the list and find all the permutations and include em. at least thats what I was taught



Thx for the suggestion of the /pi file NMEA Converter ))))
https://opencpn.org/OpenCPN/plugins/nmeaconvert.html

Lets take a look at the manual to see how to use it

https://opencpn-manuals.github.io/ma...0.1/index.html

Hmm I guess not (((((

[GreenHeaven]

Added:


Got NMEAconverter to convert

<GREEN>20:15:05 (GPSD:192.168.1.100:2000) $IIDBT,42.1,f,12.8,M,7.0,F*1A<0x0D><0x0A>

<GREEN>20:15:05 (virtual) $SDDPT ,12.8,0.0*4C<0x0D><0x0A>


and the other formats that were supposed to work.
Watchdog is still not seeing the depth

[wholybee]

Can you remove the extra space? I have not idea if that is the problem, but normally it wouldn't be there.

Not sure where you got the broken link, but clicking NMEA converter on the table of contents takes you here:
https://opencpn-manuals.github.io/ma...ter/index.html

[GreenHeaven]

Originally Posted by wholybee

Can you remove the extra space? I have not idea if that is the problem, but normally it wouldn't be there.

Not sure where you got the broken link, but clicking NMEA converter on the table of contents takes you here:
https://opencpn-manuals.github.io/ma...ter/index.html

Thanks for that link

Removing all spaces makes no diffrence, It shouldnt as these fields are comma delimited not space or tab delimited.

I need to see the parsing code to understand what in the heck is going on with watchdog. I can find no info on this

The structure of the messages kindly suggested by Corsair do not work. Puzzling

[sanner]

Old thread but I'm seeing this same problem w/ Watchdog and Dashboard Tactics (and original Tactics).


However depth is displaying just fine w/ std Dashboard plugin.


Sample NMEA data coming from signalk/10110

$IIDPT,2.30,1.000*70

or
$IIDPT,2.3,1.0*40


Both fail - I've tried several other values (w/ neg offset) and other depth sentences, no luck.



I'm running Rpi5/Bookworm with latest build from git version of OpenCPN. I've also tried with current flatpak 5.7.1-1 release and same issue - only original Dashboard shows depth data (DPT works fine for it).


I believe this was working a few months back. Anyone else seeing this lately?

[nohal]

OpenCPN has nothing to do with how Watchdog or Dashboard Tactics plugins process the NMEA messages, so you need to look for the problem in those plugins, not the core application (= building OpenCPN from git has no chance to fix this)

I use or develop neither, but a brief look at the Watchdog code suggests that it might simply need to update the opencpn-libs submodule to the current version to process the DPT sentences.
I am a bit lost in what is the current codebase for the other plugin, but the problem will likely be the same in case it is the mnt151-frontend2 branch which is the last one that has some changes.

[rgleason]

I am presently busy updating these with some final changes from Jon, and dave has updated the opencpn-libs and added macos universal builds. Hopefully this will fix the problem.

[sanner]

Good call, that sounds about right - thx.



Looks like watchdog is using 1.16 API so that could be the issue. I'm having trouble compiling / finding wxWidgets on my lastest Bookworm/Pi5 install so no luck rebuilding so far today.


(wx3.2-headers, libwxgtk3.2 & cmake 3.25)


I wasn't certain about Dashboard Tactics either but the mnt151-frontend2 branch seems to be active - not sure which version as 1.16 & 1.17 seem to be referenced in the coded.