OpenCPN Version 5.2.0 Released

[ZagsAtCF]

Ah-ha! If I actually follow "all" of the instructions it works perfectly! Thank you.

[aboon]

Has anyone else reported the effect that I described in my post of 08-08-2020 18:09 re the obstruction and other boundaries?

Andrew

[MaVi]

Hi!

Not sure if it was posted here already (search didn't help me out, here)but:

If I replace the TCP (port 10110) connection with the SignalK localhost connection, I run into a big problem: As my GPS takes some time to get a fix, my position is undefined for a while.
While that happens my GPS location (according to the gps data from the dashboard) cycles through quite a few values. Many are at (or very near) 0.00 , 0.00, but some are very very large(like 147483647 214 , 2147483647 21)
As I have tracking enabled I get some very long and fast trips- possibly to some other solar system (as the position doesn't fit the dash I can't really tell)
This is annoying, but it also causes OpenCPN to slow down to the point of crashing.

For the time being I am sticking with the TCP connection as it serves me well.
Hope this is a simple fix?

[Hakan]

MaVi..
It may this is the same issue as discussed here?
https://www.cruisersforum.com/forums...ml#post3239078
If so there may be a solution for next O release.

[MaVi]

Originally Posted by Hakan

MaVi..
It may this is the same issue as discussed here?
https://www.cruisersforum.com/forums...ml#post3239078
If so there may be a solution for next O release.

Looks very similar, thanks!
So, I'll wait a bit

[MaVi]

While I'm here-

I have a graceful power-off switch on the Pi I run OpenCPN on.
While it may gracefully shut down the Pi, I get a warning when I start OpenCPN again, that OpenCPN had a problem on its last run- if I want to disable all plugins..
(I get the same error id I choose to shut down the Pi from the power menu without first manually closing OpenCPN)

Am I the only one that gets an error? Should I add some script somewhere to first stop OpenCPN?

[rgleason]

No, search on Lennart's wiki article "Graceful shutdown Linux" or something like that. I believe it is under supplimentary.

Originally Posted by MaVi

While I'm here-

I have a graceful power-off switch on the Pi I run OpenCPN on.
While it may gracefully shut down the Pi, I get a warning when I start OpenCPN again, that OpenCPN had a problem on its last run- if I want to disable all plugins..
(I get the same error id I choose to shut down the Pi from the power menu without first manually closing OpenCPN)

Am I the only one that gets an error? Should I add some script somewhere to first stop OpenCPN?

[swolf]

Originally Posted by Waretoot

OK, so I've tried deleting the old installations and installing 5.0.1 followed by 5.2.0, same issue. Deleted OpenCPN.ini from Preferences/opencpn dir, same issue.

5.0.1 works though :-)

Waretoot, did you find a solution for MacOS 10.11?
Is there someone to confirm operation of 5.2 on OSX 10.11?


Cheers
Werner

[rgleason]

Wiki Link: Linux O Graceful shutdown

[chrismiller]

I'm getting a bug with the chart panel options. When maximised to a screen in windows the chart panel options extends across a second monitor. Screen shots attached showing the behaviour.

[MaVi]

Originally Posted by rgleason

Wiki Link: Linux O Graceful shutdown

Thanks for the reply. I've tried this solution, and it works for the button on the Moitessier.

However, I have a Geekworm X710 to power my pi, and it's button still shuts down the Pi. As it also powers itself off it is, for me, the far better solution. But I cannot get it's shutdown script to include killing OCPN first.

I figured I'd simply add the OCPN kill code at the top of the /etc/x710pwr.sh script that gets created, but so far no luck.

I do (apparently ) not know enough about scripting in Linux to get this to work.

Help would be appreciated!

[Max47]

Hello everyone and good and nice work, thanks. I don't know if this is the right position, but I wanted to warn that the "Testplugin" plugin gives an error and you can't update on Pi4-4giga with Moitessier-oSenq, all updated. See: https://i.imgur.com/SDoIj9q.png.
Good wind everyone! :faccia rossa:

[MaVi]

Originally Posted by MaVi

Thanks for the reply. I've tried this solution, and it works for the button on the Moitessier.

However, I have a Geekworm X710 to power my pi, and it's button still shuts down the Pi. As it also powers itself off it is, for me, the far better solution. But I cannot get it's shutdown script to include killing OCPN first.

I figured I'd simply add the OCPN kill code at the top of the /etc/x710pwr.sh script that gets created, but so far no luck.

I do (apparently ) not know enough about scripting in Linux to get this to work.

Help would be appreciated!

Never mind- found the problem and fixed it. Thanks!

[rgleason]

Originally Posted by MaVi

Never mind- found the problem and fixed it. Thanks!

What was it? You should contribute to the forum for others. No matter how dumb it might sound.

[MaVi]

Originally Posted by rgleason

What was it? You should contribute to the forum for others. No matter how dumb it might sound.

Well, first I misread what the line

 sudo sed -e '/shutdown/ s/^#*/#/' -i /etc/rc.local

actually does, which explained why I could not find the trigger for the script. It is triggered at boot time..
So I created a simple script from the graceful shutdown page , basically:

#!/bin/bash
# /etc/acpi/powerbtn.sh
# Initiates a shutdown when power button has been
# pressed
LOGFILE=/home/pi/shutdownlog.log
$USER=pi

echo '$(date) OCPN stop request received' >> $LOGFILE
if /usr/bin/pgrep -u $USER opencpn > /dev/null ; then
  echo '$(date) OCPN found running. Stopping now' >> $LOGFILE
  /usr/bin/pkill -u $USER opencpn
fi
while (pgrep -x opencpn >/dev/null); do
  sleep 1
  echo '$(date) Waiting for OCPN to stop' >> $LOGFILE
done
echo '$(date) OCPN stopped' >> $LOGFILE
sleep 2

as killOCPN.sh (and of course chmod +x'ed)
Next I added the killOPCN command into the /etc/x710pwr.sh script , just before the 'sudo poweroff' and 'sudo reboot' lines.

The one thing I haven't figured out yet is how to use a simple shutdown button press insted of the long press that is now required- I can shorten the rebootpulsemaximum, but then the X710 does not power-off, but that's for the next rainy sunday afternoon...