Watchdog Plugin

[Corsair63]

Really strange thing, the sentence that worked before now is not working and the one not working is working now.

version 2.4.57

$SDDPT,2.37,0.00,*7D<0x0D><0x0A>
conforming NMEA standard with blank max. range field, worked before, now not working.

$SDDPT,2.4,0.0,9999.9*6A<0x0D><0x0A>
also conforming NMEA standard with numeric value in the max. range field, before was not working but now works in the plugin.

both sentences are shown in OCPN but now the first one is not displayed in watchdog plugin.

[rgleason]

Corsair I will check WD using your sentences, but I believe the difference is based on the difference between the nmea0183 library used. I can try to make a new version with the opencpn nmea0183 library, but every alarm will have to be tested. Are you willing to do this? I think the pypilot alarms could be tested by Marco Bergman. If you are willing let me know.

[rgleason]

Corsair. Is WD depth showing NA all the time?

[bdbcat]

Rick...
1. Processing of DPT is not implemented in OCPN core. Depth is not required for basic core nav functions. DPT is Implemented by individual plugins as required. So merging core NMEA0183 library gains nothing. The red herring I have mentioned.

2. The DPT message implemented by (12 year old) watchdog plugin handles only the older (2.0?) format, like:

$SDDPT,2.37,0.00,*7D<0x0D><0x0A>

That is a potential RFE to the plugin, but has nothing to do with core NMEA0183 library.

3. If both DPT and DBT messages are present, only DBT will be used.


Hope this helps.
Dave

[Corsair63]

Originally Posted by rgleason

Corsair I will check WD using your sentences, but I believe the difference is based on the difference between the nmea0183 library used. I can try to make a new version with the opencpn nmea0183 library, but every alarm will have to be tested. Are you willing to do this? I think the pypilot alarms could be tested by Marco Bergman. If you are willing let me know.

Watchdog is a huge plugin, I can test what I'll be working with it, step by step.

[Corsair63]

Originally Posted by rgleason

Corsair. Is WD depth showing NA all the time?

when switched on the Echo-Sounder (0183) (ES) now working on 3.0 it shows the correct depth (this one is giving the data straight away to the multiplexer and no intervention of it, so the sentence is as is).

when received before the sentence from N2K and converted to 0183 in multiplexer was displayed correctly (e.g. $SDDPT,2.37,0.00,*7D<0x0D><0x0A>) but now only displayed N/A all the time.

another thing is working with N2K ES displays N/A if I switch it off and switch on the ES 0183 still persists the N/A and I have to re-start OCPN and after that the depth is displayed.

I've done the same procedure, in opposite way, ES 0183 off - ES N2k on - re-start OCPN but still persist the N/A.

in all situations I don't loose the depth display in OCPN, only when are switched off both of then.

[Corsair63]

Originally Posted by bdbcat

2. The DPT message implemented by (12 year old) watchdog plugin handles only the older (2.0?) format, like:

$SDDPT,2.37,0.00,*7D<0x0D><0x0A>

Hi Dave,

that sentence is NMEA 3.0 at least, because it has the third field but empty, the separator is present.

same sentence for version 2.0 should be:

$SDDPT,2.37,0.00*7D

old NMEA from 2000 rev 2001 (ver 2.0)
the sentence was:
$--DPT,x.x,x.x*hh
1 - depth in m
2 - offset
3 - checksum

[bdbcat]

Corsair...
Thanks for the info.
My copy/paste error, I guess. It seems pretty clear to me that DPT parser in watchdog_pi only understands a true 2.0 sentence. Opportunity for improvement.


Dave

[rgleason]

I am finding that Watchdog 14.57.0 is not working with old depth data or new depth data. Please find two depth files attached and 2 screenshots using old depth and new depth files.

[Corsair63]

Hi,

just a remark in my previous finding. tested today.

N2K ES on - sentence converted by multiplexer received in OCPN $SDDPT,2.37,0.00,*7D display NA in WD
(in previous version of WD was properly displayed)

0183 ES on - sentence in $SDDPT,3.3,0.0,9999.9*6C display NA in WD
(in previous version when ES set-up as NMEA 2.0 output was displayed properly by WD)
(just forget about values, is just an example of sentences and situation)

switched off N2K - still display NA
re-started OCPN - WD showing the correct data from 0183 ES

tried another combinations, but no way to display the depth from the N2K converted to proper 0183 sentence.

if started OCPN with 0183 ES on WD displays correctly the data supplied by this ES.

OCPN at any moment looses the depth readings.

[bdbcat]

Corsair...
"OCPN at any moment looses the depth readings."


Do you mean watchdog_pi, or maybe dashboard_pi?
Thanks
Dave

[Corsair63]

Originally Posted by bdbcat

Corsair...
"OCPN at any moment looses the depth readings."


Do you mean watchdog_pi, or maybe dashboard_pi?
Thanks
Dave

WD showing NA
Dashboard showing correct depth readings

[rgleason]

Watchdog 2.4.60.0 in Master Catalog, has been merged by Dave into PIM and is available.
Depth is fixed, Pypilot Alarms and Rudder Alarms are back in the plugin.
Please test every aspect of this plugin and and advise here of which alarms work and which don't (we need to know both confirmations and negatives)!!! ..along with Opencpn version and OS!!



We also need the same testing for Tesplugin 1.0.253.0, In particular which OS it works on and which OS it does not.



Thanks. Also a big thanks to Dave R. for his help getting this working!

[Corsair63]

updated to WD 2.4.60

first test about depth alarm:

several conditions and test performed.
- N2K ES showing correct reading and alarm triggered when condition meets.
- both ES working at the same time, 0183 has priority, working
- 0183 ES working alone, all in order shown depth and alarm triggered when conditions meet.
- switched off one, the reading is still correct with the other one without re-starting OCPN. (same tried with each ES)
- switched off both and alarm triggered (of course)
- started one and showing correct reading.

FYI, ES 0183 is sending ver 3.0 and N2K ES is translated in multiplexer to ver 4.1

all above are situations in WD plugin, OCPN (Dashboard) showing correct reading too as usual.

I'll try another alarms and I'll report findings

[Corsair63]

2nd test about course alarm

selected source as GPS and seems to work.

selected heading sensor and displayed N/A, this signals are received in Multiplexer from Autopilot and flux gate via SeaTalk converted to 0183.

some of them:

<GREEN>13:20:33 (UDP:192.168.1.2:10110) $HCHDG,284.50,,,0.00,E*22<0x0D><0x0A>
<GREEN>13:20:34 (UDP:192.168.1.2:10110) $HEHDT,284.5,T*24<0x0D><0x0A>
<GREEN>13:20:34 (UDP:192.168.1.2:10110) $HCHDG,284.50,,,0.00,E*22<0x0D><0x0A>