Watchdog Plugin

[Hakan]

Watchdog, with the code from https://github.com/rgleason/watchdog_pi, does use the dpt.cpp understanding only NMEA 2.0, without the third "Maximum range field".
To get Watchdog_pi to understand also NMEA 3.0 the dpt.cpp from OCPN Dashboard_pi may be copied and used instead?

[stevead]

To get Watchdog_pi to understand also NMEA 3.0 the dpt.cpp from OCPN Dashboard_pi may be copied and used instead?

A quick perusal of dasboard_pi (in OpenCPN core), dashboard_tactics_pi and tactics_pi shows that ALL use an outdated dpt.cpp parser that does NOT parse NMEA 183 version 3.0 DPT sentences of the form:

           1   2   3   4
           |   |   |   |
    $--DPT,x.x,x.x,x.x*hh<CR><LF>
   
    Field Number:
     1) Depth, meters
     2) Offset from transducer,
        positive means distance from tansducer to water line
        negative means distance from transducer to keel
     3) Maximum Range
     4) Checksum

Strange that no-one has reported this behaviour ? More strange is how many tactics plugins we have??

I did a quick & dirty fix to dpt.cpp in the TwoCan plugin eons ago, so perhaps that could be used to update the dpt.cpp (and dpt.h) source files.

And to bring the watchdog up to speed, it should add support for NMEA2000 by listening for and parsing PGN 128267.

[Corsair63]

Originally Posted by stevead

Strange that no-one has reported this behaviour ? More strange is how many tactics plugins we have??

Maybe could be because most of transducers are transmitting the third field as null and the coding could understand it.

otherwise I really could not understand that same sentence, one with three fields and blank range works but the one with some numerical data in this field doesn't work.

$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)

[stevead]

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

I don't know what depth sensor or multiplexer is transmitting this sentences.

If the maximum range is indeed 999.9 metres then that is valid, however if the maximum range is unavailable or not defined, then it should be a null field.

If this sentence is being generated by the conversion of a NMEA 2000 PGN 128267 message and the maximum range is "unavailable", then that would be a bug with the multiplexer as it should be generating a NMEA 183 sentence with a null field instead of 999.9 for maximum range.

[Hakan]

Steve...
Dashboard_pi: dpt.cpp is prepared for N0183 >=v3.0, i.e. if 4 fields are present, if you check. Although is the "Maximum range" value not used.

[Corsair63]

Originally Posted by stevead

I don't know what depth sensor or multiplexer is transmitting this sentences.

If the maximum range is indeed 999.9 metres then that is valid, however if the maximum range is unavailable or not defined, then it should be a null field.

If this sentence is being generated by the conversion of a NMEA 2000 PGN 128267 message and the maximum range is "unavailable", then that would be a bug with the multiplexer as it should be generating a NMEA 183 sentence with a null field instead of 999.9 for maximum range.

Negative, this is a straight away NMEA 0183 from Furuno Echo Sounder, with no intervention either conversion in Multiplexer, pure NMEA 0183 sentence. and selected in the ES as version 3.0 when exchanged to ver 2.0, it omits the max. range field and them is shown by the plugin.

the one with null third field is the one generated via multiplexer from a N2K Furuno Echo Sounder. and is the one displayed in the plugin.

have to say that any of the combination above and already reported in this thread from my side are properly displayed in OCPN data.

[stevead]

Originally Posted by Hakan

Steve...
Dashboard_pi: dpt.cpp is prepared for N0183 >=v3.0, i.e. if 4 fields are present, if you check. Although is the "Maximum range" value not used.

You're correct. My quick perusal, was perhaps, too quick!

As you mentioned, using dpt.cpp from the dashboard_pi for the watchdog plugin would indeed solve the problem.

[Corsair63]

Hi all,

new version of plugin and still persists the reading error of version 3.0 with some data in last field of the sentence for the depth.

e.g. $SDDPT,3.3,0.0,9999.9*6C

exchanges echo-sounder to version 3.0 and immediately triggered the depth alarm and 0.0 reading, come back to version 2.0 and correct display of the depth in the alarm.

[rgleason]

We have been using a certain nmea library for watchdog that has wroked, will substituting one lib file be acceptable and compile and work?

Also if we update one of the files shouldnt we update all of them? Furthermore I have tried changing nmea libs and found that in certain instances it does not work. There is additional programming required.

Right now my priorities with watchdog is to add some missing alarms, but this change could be added if it is a simple problem with some clear abswers.

[Jorand]

Hello, I have been using OpenCPN for 3 years without any problem (windows10 PC). Following the installation of WATCHDOG, it is now blocked. Trying this plug-in as an anchor alarm, I removed the mark without deleting the associated anchor alarm. Since then, it has been impossible to delete this alarm which completely blocks the movement of my sailboat on the map. Does anyone have an easier solution than completely reinstalling OpenCPN?

[GreenHeaven]

Originally Posted by rgleason

We have been using a certain nmea library for watchdog that has wroked, will substituting one lib file be acceptable and compile and work?

Also if we update one of the files shouldnt we update all of them? Furthermore I have tried changing nmea libs and found that in certain instances it does not work. There is additional programming required.

Right now my priorities with watchdog is to add some missing alarms, but this change could be added if it is a simple problem with some clear abswers.

perhaps you could define what data fields watchdog is expecting in order to display depth.

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

<GREEN>20:06:54 (virtual) $SDDPT 12.8,0.0*60<0x0D><0x0A>



These not working


windows 10, latest ver of everything

[Corsair63]

Originally Posted by GreenHeaven

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

supposed that both of them are not conforming the standard NMEA DPT sentence
the first one has an extra space: $SDDPT ,12.8,0.0*4C should be: $SDDPT,12.8,0.0*4C
the second one has no coma separator: $SDDPT 12.8,0.0*60 should be: $SDDPT,12.8,0.0*60

[rgleason]

Sorry guys if watchdog is screwed up in some alarms, we had a bad divergence (ans I dont think it is my fault) and I have tried to fix that with this new veesion.

But there are two problems, only cursory testing was done, and I think we have pypilot alarm back but have lost the rudder alarm.

Depth was working as far as I know.

It would help if some of you programmers would lend a shoulder and if users could provide good testing and reports.

See this https://github.com/rgleason/watchdog_pi/issues/44

I do what I can.

[GreenHeaven]

Originally Posted by rgleason

Sorry guys if watchdog is screwed up in some alarms, we had a bad divergence (ans I dont think it is my fault) and I have tried to fix that with this new veesion.

But there are two problems, only cursory testing was done, and I think we have pypilot alarm back but have lost the rudder alarm.

Depth was working as far as I know.

It would help if some of you programmers would lend a shoulder and if users could provide good testing and reports.

See this https://github.com/rgleason/watchdog_pi/issues/44

I do what I can.

Can you point me to the source code and the file with the parser in it please
Ill fix it

[Corsair63]

Hi Developers,

just installed the new version of plugin.

happy to say that now works with version 3.0 and max range in the last field of the NMEA sentence.

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

on arrival the new version, I exchanged the Furuno Echo-sounder in trouble from version 2.0 to 3.0, I had to restart OCPN and the plugin displayed properly the depth now with this device.