OpenCPN v5.9.1 Beta test starts

[Corsair63]

Originally Posted by Ivanm

Hi all
Arpa targets excessive big on screen and radar targets and Ais targets are far from each other on radar plugin

Ivanm

It's supposed that AIS targets are displayed as per ground stabilized (GNSS source) and shown in true bearing and calculated distance own position-broadcasted target AIS position, GNSS based both.

RADAR targets are displayed as it receives them.

Two things could happen:
1 - that you the RADAR stabilized with the compass and there is a compass misalignment plus the difference in both calculated GNSS positions and Calculated RADAR distance.
2 - the RADAR is head-up and for any reason there is a misalignment in the headline of for such reason this difference in bearing.

what could be done in both cases:
1 - calibrate (adjust) the compass. Most of the electronic ones, they have a procedure to carry it out.
2 - check the initial parameters of the RADAR and just in case and very carefully correct such difference in the headline.

could be other factors but the #1 is the most common.

[Ivanm]

Originally Posted by Hakan

Ivanm.
I'm on W10 at home using the radar Emulator and there they match. Both overlay and the PPA window. I'm using radar_pi's ARPA function.

I don't recognize the green checked circle symbol (Halo...) on you picture. What's that?
I have a 3G and no Halo..

But I'll test onboard with the live radar. But could take a day or two.
What's your system?

Thanks I am on Win10 and the Halo is my arpa targets on Simrad

[Hakan]

As corsair mentioned. Start with the basics if not done.
Secure your compass heading is correct regarding length axis accordance and deviation.
If still offset it's also possible to adjust in radar plugins' preferences.
Also any range offset is possible to adjust in the radar plugin.
The Halo ARPA function is unknown for me and we can't control it. If the heading is correct adjusted you may try the radar plugin's ARPA function? Works independent of the radar scanner type.

[Ivanm]

Originally Posted by Corsair63

It's supposed that AIS targets are displayed as per ground stabilized (GNSS source) and shown in true bearing and calculated distance own position-broadcasted target AIS position, GNSS based both.

RADAR targets are displayed as it receives them.

Two things could happen:
1 - that you the RADAR stabilized with the compass and there is a compass misalignment plus the difference in both calculated GNSS positions and Calculated RADAR distance.
2 - the RADAR is head-up and for any reason there is a misalignment in the headline of for such reason this difference in bearing.

what could be done in both cases:
1 - calibrate (adjust) the compass. Most of the electronic ones, they have a procedure to carry it out.
2 - check the initial parameters of the RADAR and just in case and very carefully correct such difference in the headline.

could be other factors but the #1 is the most common.

Thanks all, I have found the issue, if I move the radar ppi the Ais targets doesn't move with the ppi and is displaced but can be moved back into correct place again ...don't think it was like that previously

[Hakan]

That one I can't reproduce.
I'm using OCPN present Beta 5.9.1 and radar plugin from Plugin manager master catalog version 5.5.0.
However I move the PPI window all AIS targets are nicely following on there correct positions. Also shifting between head and course up is no problem.

[Ivanm]

Originally Posted by Hakan

That one I can't reproduce.
I'm using OCPN present Beta 5.9.1 and radar plugin from Plugin manager master catalog version 5.5.0.
However I move the PPI window all AIS targets are nicely following on there correct positions. Also shifting between head and course up is no problem.

I think I am using the beta radar plugin not near PC now, will downgrade to 5.5.0 and test again
I must say I don't move the whole Ppi window , only the range rings inside I like to zoom out and mpve downwarts

[Hakan]

I's using a radar beta plugin before 5.5.0 but changed to also test this. But yes, do test.

[wholybee]

Shortly after the connection screen was reworked, there was a thread about UDP connections and having both receive and output checked. Apparently there are cases this works and some users use it. I made a pull request, but it didn't get noticed or merged.

https://github.com/OpenCPN/OpenCPN/pull/3867

[wholybee]

The AutotrackRaymarine plugin is causing OCPN 5.9.1 to crash every 5-10 minutes when using NMEA2000 over Ethernet.

OCPN becomes unresponsive until Windows offers to close it.

[Hakan]

Originally Posted by Ivanm

I must say I don't move the whole Ppi window , only the range rings inside I like to zoom out and mpve downwarts

Ahaa. That I didn't understood. Sorry. And you're correct! This bug is present in both master and beta catalog versions.
But corrected in Github radar plugin master branch.

We need to get alpha version released.
Meanwhile since you are on Windows(?) you may try a tarball for import.
A link here.
If you are not familiar how to import pls revert.
Thanks for testing.
Håkan

[bdbcat]

Attention all translators...


New and important additions have been make to crowdin translation strings. The additions support the new-user startup wizard, recently added to OCPN 5.9


Thanks in advance for your translation help.
Dave

[bbalan]

Extremely Minor Issue: "r" shortcut key to turn Own Ship's Range Rings on and off.


This works (thanks!). But one must move the chart for it to take effect. Obviously not a problem if GPS signal present and boat moves a bit. But with no GPS or chart movement, nothing happens until you drag the chart a little.



Windows 11.

[Douwe Fokkema]

Originally Posted by wholybee

The AutotrackRaymarine plugin is causing OCPN 5.9.1 to crash every 5-10 minutes when using NMEA2000 over Ethernet.

OCPN becomes unresponsive until Windows offers to close it.

I have tested the AutoTrackRaymarine plugin with O 5.9.1 using the NGT-1 interface. Working fine.

I would like to see a opencpn.log of the crash.

[bcn]

How to test the new initial configuration wizard on a system where OCPN is already configured?

[nohal]

Originally Posted by bcn

How to test the new initial configuration wizard on a system where OCPN is already configured?

Either by removing the config file (That is 100% simulating the actual use case when it is invoked)

Or by starting opencpn with -W parameter from command line (In that case it is shown even with preexisting configuration file).