Watchdog Plugin

[rgleason]

Thank you. Have made a report under Opencpn Issues.
https://github.com/OpenCPN/OpenCPN/issues/2763


Dave may have some questions for you, but as I said he is very busy and this may be a distraction right now. Sorry. This will be addressed at some point.

[leamas]

I have a more or less identical setup: Raspbian based on Debian 11.4, flatpak installed version 5.6.2-0+b75be76. With this setup I cannot reproduce the plugin loading problem. Furhermore, there are plenty of Flatpak users out there which does not report this, so it is something with your installation (that is not to say there isn't any bug involved).


The first step would be to clear your local data using:

$ rm -r $HOME/.var/app/org.opencpn.OpenCPN

Then, reinstall the flatpak package using

$  flatpak --user install --reinstall org.opencpn.OpenCPN

... and report back if problem persists. Reporting back, please submit output from

flatpak list

and

cat /etc/debian_version

[leamas]

NOTE! removing $HOME/.var/app/org.opencpn.OpenCPN means all your local setup will go away, starting from a clean state.

[ALROCHARARI]

Originally Posted by leamas

NOTE! removing $HOME/.var/app/org.opencpn.OpenCPN means all your local setup will go away, starting from a clean state.

I made the configuration of the backports version I have on the same RPI 4. The results are identical.

I will try your "restage" solution on the flatpak version and report the results.

[ALROCHARARI]

Originally Posted by leamas

I have a more or less identical setup: Raspbian based on Debian 11.4, flatpak installed version 5.6.2-0+b75be76. With this setup I cannot reproduce the plugin loading problem. Furhermore, there are plenty of Flatpak users out there which does not report this, so it is something with your installation (that is not to say there isn't any bug involved).


The first step would be to clear your local data using:

$ rm -r $HOME/.var/app/org.opencpn.OpenCPN

Then, reinstall the flatpak package using

$  flatpak --user install --reinstall org.opencpn.OpenCPN

... and report back if problem persists. Reporting back, please submit output from

flatpak list

and

cat /etc/debian_version

There are the results after clean reinstallation:
- "ERROR ... Could not open file "opencpn" for reading with errno = 2" immediately present.
- "MESSAGE ... ERROR Loading translation catalog for : opencpn-chartdldr_pi immediately present.
- "MESSAGE ... ERROR Loading translation catalog for : opencpn-wmm_pi immediately present.
- During installation, had the warning that org.freedesktop.Platform//20.08 is end-of-life
- Flatpak list gave:
-- org.freedesktop.Platform version 20.08.21 branch 20.08
-- org.freedesktop.Platform.GL.default version 21.1.8 branch 20.8
-- org.opencpn.OpenCPN version 5.6.2)0+b75be76 branch stable
- debian_version is 11.5

When removing all the plugins, no more errors.
The only explanation I see is that my PI is configured as french (belgian) with belgian keyboard.

[rgleason]

When removing all the plugins, no more errors.
The only explanation I see is that my PI is configured as french (belgian) with belgian keyboard.

Including the internal plugins?
This might be the cause. Can you load them one at a time and test?
Perhaps first with Belgian keyboard, then change to US?


Sorry about all the trouble, but this might help isolate the problem.

[ALROCHARARI]

Originally Posted by rgleason

Including the internal plugins?
This might be the cause. Can you load them one at a time and test?
Perhaps first with Belgian keyboard, then change to US?


Sorry about all the trouble, but this might help isolate the problem.

OK this is the next run of tests:
1. Changed to en_US.UTF8 (Not straight through process. Had to manually modify /etc/default/locale file.)
2. Removed all plugins from OpenCPN FP settings
3. Closed OpenCPN FP, removed opencpn.log, restarted OpenCPN FP
4. -- NO MORE ERRORS IN opencpn.log --
5. Reactivated WMM plugin only
6. Closed OpenCPN FP, removed opencpn.log, restarted OpenCPN FP
7. - "ERROR ... Could not open file "opencpn" for reading with errno = 2" REAPPEARED in opencpn.log
- "MESSAGE ... ERROR Loading translation catalog for : opencpn-wmm_pi DID NOT REAPPEARED.

Same logic if I test with another standard plugin.

Seem confirming that there is 2 separate issues.
Not sure they are 100% separate.
I'm not 100% sure that the "locale" reconfiguration is correct even if when I execute locale command, the list seem clean with only en_US.UTF8 visible.

Ready for next test...

If it can help, I'm ready to send a USB key RPI4 bootable with my configuration for debugging purpose.

[Gilletarom]

Originally Posted by ALROCHARARI

There are the results after clean reinstallation:
- "ERROR ... Could not open file "opencpn" for reading with errno = 2" immediately present.
- "MESSAGE ... ERROR Loading translation catalog for : opencpn-chartdldr_pi immediately present.
- "MESSAGE ... ERROR Loading translation catalog for : opencpn-wmm_pi immediately present.
- During installation, had the warning that org.freedesktop.Platform//20.08 is end-of-life
- Flatpak list gave:
-- org.freedesktop.Platform version 20.08.21 branch 20.08
-- org.freedesktop.Platform.GL.default version 21.1.8 branch 20.8
-- org.opencpn.OpenCPN version 5.6.2)0+b75be76 branch stable
- debian_version is 11.5

When removing all the plugins, no more errors.
The only explanation I see is that my PI is configured as french (belgian) with belgian keyboard.

Hum ... there is only one version of the language file in French. The notion of "Belgian" language does not exist in French. Even Quebecers whose French is quite different from the French of France use the same version of the language file. And so far, apart from two or three small adaptations, no one cares.


Concretely, it is probably preferable to position everything in French of "france" in your settings.

[ALROCHARARI]

Originally Posted by Gilletarom

Hum ... there is only one version of the language file in French. The notion of "Belgian" language does not exist in French. Even Quebecers whose French is quite different from the French of France use the same version of the language file. And so far, apart from two or three small adaptations, no one cares.


Concretely, it is probably preferable to position everything in French of "france" in your settings.

Good for me even if not ideal. I can live with this as my belgian keyboard is still supported.

Remaining error still present:
"ERROR ... Could not open file "opencpn" for reading with errno = 2"

[leamas]

I also have that error message. The short story is that it could be disregarded, it's does not reflect an actual problem.


Expanding on this the error message comes from pluginmanager.cpp, in the CheckPluginCompatibility() function. In the log, you can see that the message immediately after the ERROR message is Plugin is compatible by elf library scan: true. This reflects that the ERROR message is dealt with successfully.


It could be argued the ERROR message actually should be a MESSAGE or perhaps WARNING. However, this is basically all there is to this.



I

[BILLY_BUDD]

Help! Watch Dog AIS Guard Zone

I cannot seem to get Watch Dog to alarm an AIS Guard Zone. I am located where there are plenty of AIS targets (near a ferry route). I have been able to confirm WatchDog alarm/alarm reset capability via an Anchor Watch. However, I have not been able to demonstrate an Guard Zone Alarm function with an ODraw Exclusion Boundary-GUID and WatchDog when AIS targets engage the boundary.

I have carefully followed the instructions in the manual and I am fairly certain I have been able to exercise this capability while cruising in the ICW prior to the pandemic. I am not perfect, far from it, so anything can happen.

Chuck (aka Billy Budd)

[GreenHeaven]

thank you for this essential plug in.
How do I set a depth alarm please??

[GreenHeaven]

Thank you for this great plug in, but how to get depth working ?????

How do I get help with Depth Alarm please????


https://www.cruisersforum.com/forums/tags/depth.html
None here

https://paste.pics/bc23e80887144710f9430a76a59c1105

Yet Open CPN is displaying the depth OK from the NMEA 0183 wireless feed

[johnwilde]

Hi,

Just wondering if someone can assist with this plugin. I'm running v2.4.45.0 on a Windows based OCPN v5.6.2.

I'm trying to set up an anchor watch alarm running a command for email notification. I have a *.bat file set up which works fine and does the e-mailing (when I run it manually). However, when I set this as the command and try test (along with Message Box'), whilst I get the message box, no e-mail is sent as the command does not seem to action.

I've tried setting the parameters to force and alarm activation - same response - the bat file doesn't seem to run.

Would love to get this working, so any help would be much appreciated.

Thanks in advance.



John

[Hakan]

John..
I've tried it on my Win I can't do more than agree on your experience.
The "Command" function as such is working. Try for example the command: calc
This opens the windows calculator when alarming.
To run a .bat file I didn't succeed. I tested like: cmd /c test.bat and nothing happens nor a failure reply.

My guess: Since Watchdog use the wxProcess::Open() function I think the called wxExecute i waiting for the PID from the called program. An .exe file, like calc.exe, is reporting this but the cmd test.bat don't in the same way. I also tried a .py file but that created an (watchdog) error.
So, it seems on Windows we need an .exe file to get it to work?

Or please --- anyone Win guru to sort this out?