OpenCPN Version 5.7.1 Beta Test #2

[Hakan]

Originally Posted by bdbcat

Hi there...
Several users have reported crashes when exiting the app on Rpi/64 using canBus native adapters.
If this is happening to you, we need more information, please. What adapter? What OS? CANbus adapter plugged into live N2K bus, or hanging free?
Any other information would be useful.
Thanks
Dave

Although no shut problem it may be a valid info as well.
Now tested wo trouble on:
Linux RPi400 5.15.84-v8+ #1613 SMP PREEMPT Thu Jan 5 12:03:08 GMT 2023 aarch64 GNU/Linux
Using GeDaD MCS board with MCP 2562E

[Alfange]

Originally Posted by ZUZA

Hi everyone

Please, the Ship Position on the Status Bar is not appearing, usually this position appears before the SOG and COG.

Can anyone help?

Thank you

Hi Dave

It would be interesting and important to have the option of showing the own ship coordinates in the standard Status bar, based only on the coordinates of the position in which the boat is on the nautical chart, even without the connection with the GPS; and not only if the GPS is connected or just after disconnected, because it seems that it is what currently occurs.

Considering that all the desired data, are already an option in the respective Dasboard and StatusBar plugin, but the basic option described above at this time, it is not yet possible for this position of the boat to continue to be shown in the standard status bar, if the GPS is disconnected.

Thanks

[hoolie]

My W11 laptop has no GPS input and the boat position on the status bar is shown correctly.
I think your lack of lat/long display is specific to your system. I have had problems before with a corrupted opencpn.ini configuration file. You could try re-naming your opencpn.ini file (without openCPN running) so that it will be re-created the next time you run openCPN.

[verkerkbr]

Tested here on my AMD64 Linux Mint. Works but not in the Flatpak version.

Tested on my RPI4 with Debian Bullseye Works but not in the flatpak version

Tested on my RPI4 with Ubuntu Kinetic 64 Works but not in the flatpak version

Tested on my RPI4 with Fedora Rawhide (has only the flatpak version) does not work.

What is the problem with the Flatpak version can0 does not appear in the setup screen.

I'am using the candlelicht firmware on several Canable boards.

With this firmware I have to activate can0 with:

sudo ip link set can0 up type can bitrate 250000. Then the led starts flashing and is can0 available.


See image with the Sats data.



Bram

[Alfange]

Originally Posted by hoolie

My W11 laptop has no GPS input and the boat position on the status bar is shown correctly.
I think your lack of lat/long display is specific to your system. I have had problems before with a corrupted opencpn.ini configuration file. You could try re-naming your opencpn.ini file (without openCPN running) so that it will be re-created the next time you run openCPN.

Hi hoolie

It didn't work and still created a problem, because I have thousands of nautical charts and the system had to recreate all related charts, already saved, recreating the entire list and groups, and this will take a few hours.
I do not recommend such action to anyone ...

[Hakan]

Originally Posted by AedanC

When a SAR AIS target goes undetected for a period the black line is not drawn perpendicular to the course as it is with others, but horizontally.

Aedan..
Yes, true. Looking in the code the line is always horizontal for these targets.
My thoughts: I think it could be as it is. It could also be intentional since a line aligned to the wings or a helicopter rotor may be less visible. On your picture it's really obvious something extra is added, i.e. the lost target line?

[verkerkbr]

Originally Posted by verkerkbr

Tested here on my AMD64 Linux Mint. Works but not in the Flatpak version.

Tested on my RPI4 with Debian Bullseye Works but not in the flatpak version

Tested on my RPI4 with Ubuntu Kinetic 64 Works but not in the flatpak version

Tested on my RPI4 with Fedora Rawhide (has only the flatpak version) does not work.

What is the problem with the Flatpak version can0 does not appear in the setup screen.

I'am using the candlelicht firmware on several Canable boards.

With this firmware I have to activate can0 with:

sudo ip link set can0 up type can bitrate 250000. Then the led starts flashing and is can0 available.


See image with the Sats data.



Bram

O is running here with direct NMEA2000 GPS input for many hours. No problems with the shutdown. But as always you have to look to the NMEA2000 net with the right configuration. Some applications do have a terminal fixed and other uou have to use a terminator at the end of de back-bone.


Not yet tested the Actisense NGT-1 with the direct input in O.


Bram

[hoolie]

Originally Posted by ZUZA

Hi hoolie

It didn't work and still created a problem, because I have thousands of nautical charts and the system had to recreate all related charts, already saved, recreating the entire list and groups, and this will take a few hours.
I do not recommend such action to anyone ...

You could have deleted the new .ini file and restored the original file by changing its name back again.

[verkerkbr]

Originally Posted by verkerkbr

O is running here with direct NMEA2000 GPS input for many hours. No problems with the shutdown. But as always you have to look to the NMEA2000 net with the right configuration. Some applications do have a terminal fixed and other uou have to use a terminator at the end of de back-bone.


Not yet tested the Actisense NGT-1 with the direct input in O.

Bram

At first you can activate the Can0 with the former instruction in the terminal.

Now i have set the rule with the program file in etc/rc.local and then the Canable starts
up at the boot. If there is no etc/rc.local. Make one.

#!/bin/bash
sudo ip link set can0 up type can bitrate 250000
exit 0


This works on Linux Mint AMD64 en RPI4 with RaspianBullseye and Ubuntu Kinetic.


There are now a lot of "canable" work-like small boards available at around $20,-.

Bram

[Alfange]

Originally Posted by hoolie

You could have deleted the new .ini file and restored the original file by changing its name back again.

Hi again hoolie and everyone

In part it was what I did indirectly, deleting the new file .ini created, but to restore everything as before, I enabled the navobj.xml file, which was in the immediate sequence to which it was damaged, and everything was restoring to the previous moment, except the database of the addresses of the charts that had to be re-listed, as I mentioned.

I have not lost anything, just time, however it became clear that this is not an option to solve such a problem of the position of the boat in the standard status bar, which considers only the position based on GPS and not the position in which it is considering the coordinates of the nautical chart in use at that time.

OK, this question remains, so I once again ask the attention of users, who eventually know something about the already described, and who can give some help in trying to clarify the matter, which I assume still occurs in this Beta version, since I saw the same situation on some printscreens.

In advance I appreciate everyone's goodwill.
Fair winds, smooth seas and blue horizons.

[bdbcat]

Tony...
re:
"Just trying to start testing this on MacOS Ventura Intel and get crash when attempting to launch."



Sorry, this is a known problem. If you would like to advance test the Beta#3 candidate, try this:
https://dl.cloudsmith.io/public/davi...nCPN_5.7.1.pkg
Thanks
Dave

[AedanC]

Originally Posted by Hakan

Aedan..
Yes, true. Looking in the code the line is always horizontal for these targets.
My thoughts: I think it could be as it is. It could also be intentional since a line aligned to the wings or a helicopter rotor may be less visible. On your picture it's really obvious something extra is added, i.e. the lost target line?

Hi Hakan,
I'm not quite sure what you mean about the "lost target line", are you referring to the blurred depth contour line in my photo?
Aedan

[Hakan]

Aedan..
The line over the AIS target on you shot is the mark saying the target is lost. No position updates since, "Mark targets as lost after (min).." default 8 minutes.

Using default minutes the target is then deleted after 2 minutes.

[Hakan]

About RPi and modprob can0 crash at shut down

Originally Posted by Hakan

Although no shut problem it may be a valid info as well.
Now tested wo trouble on:
Linux RPi400 5.15.84-v8+ #1613 SMP PREEMPT Thu Jan 5 12:03:08 GMT 2023 aarch64 GNU/Linux
Using GeDaD MCS board with MCP 2562E

I though experienced if I start OCPN without modprobe installed he will crash on shut down.
So we better make sure the modprobe is installed in a way it reloads after reboot.

[bcn]

Dave...


with today's +b90dad9 on the macMini (M1, 13.1, Ventura) the Compass and GPS Indicators on the split screen are ok (already since some former commit two days ago).
With OpenGL ON line width and anti-aliasing has improved and is usable now for me.


Tarifa/Gibraltar is still not 100% - a challenging benchmark. See screenshots.



SuperSCAMIN ("additional reduction of detail") should not apply to TSS and Recommended Tracks. Actually it is much too aggressive and TSS get visible only when zoomed in heavily.


Hubert