OpenCPN Version 5.7.1 Beta Test #1

[Hakan]

Originally Posted by Gilletarom

The picture from Windows.

Question : "Center-info-close" ? what about ?

Select a target and try!
It will - Center the target at about 1:5000 chart scale. - Open Target Info - Close Target list

[bcn]

I see quilting of vector with raster charts. Is that intentionally? In this case a bad solution as there are vector charts with larger scale (and coverage) in the vector set for the same place. Tarifa and Ceuta at Strait of Gibraltar.

[Hakan]

Originally Posted by Gilletarom

Hello Dave,

About Grib plugin :

Would it be possible that there is, in the preferences of Thunderbird, an option to check so that Thunderbird is not closed unnecessarily for the users who wish it?

Gille..
Thunderbird is good but I think you have to convince it yourself. OCPN can and should not adjust preferences for another app.
Although not related to this thread about OCPN Beta. For the purpose you mentioned I use the "FiltaQuilla" add-on/plugin. Create a filter that for a mail from saildocs having an attached file - save the file to ...../gribs/ - then move the mail to scrap bin.

[bcn]

"Additional reduction of details at Small Scale"

Where shall we see this?

[bdbcat]

bcn..


"Additional reduction of details at Small Scale"

"Where shall we see this?"

Not implemented yet for o-charts plugin.
You should see some effect for standard S57 ENCs that are not sensibly encoded.
In your case, the original S57 material for Finland might be inspected/compared.


Dave

[bdbcat]

bcn...
"I see quilting of vector with raster charts. Is that intentionally?"


No, this is a bug.


Dave

[LeaseOnLife]

Socketcan interface should allow interface selection can1 (2,3,4,5,)

My PI4 has a CAN hat with 2 CAN interfaces. can0 was used for signalk and I want opencpn to use can1. That can not be selected... My choices are can0, slcan0 and vcan0. For further testing I have signalk use can1, with O using can0.

[LeaseOnLife]

N2K sources for wind, depth, speed thru water are not yet implemented ?
At least they don't show in the new "Adjust Comm priority" dialog.


I can not find OpenCPN as a device on other N2K instruments / devices. I believe it claims address 77, but can not be found or interrogated for capabilities

[LeaseOnLife]

Using N2K only: basic navigation works (Position, HDG, SOG), plus radar overlay works too.

AIS: ships show too, but:

PGN129040 has a placeholder in the code, but is not used any further. PGN129040 was sent by my AIS when we encountered a Chinese fishing fleet, they marked their humongous net with small AIS transmitters.

Using an iKommunicate N2K=>N183 translation device, these small transmitters showed like in the pics below. I'd expect O to do the same thing when PGN129040 is received.

There is more info on a github issue for a signalk plugin:

https://github.com/sbender9/signalk-...a0183/issues/8

[Hakan]

Originally Posted by LeaseOnLife

N2K sources for wind, depth, speed thru water are not yet implemented ?
At least they don't show in the new "Adjust Comm priority" dialog.

Adjust Comm priority is for navigational data for OCPN core only. See the labels in the list.

Plugin Dashboard though would use the sources you mentioned. Please test.

[bdbcat]

LOL...
N2K sources for wind, depth, speed thru water are not yet implemented ?
At least they don't show in the new "Adjust Comm priority" dialog.



As Hakan says. The new Adjust Comm Priority dialog manages the core OCPN nav functions only.

I can not find OpenCPN as a device on other N2K instruments / devices. I believe it claims address 77, but can not be found or interrogated for capabilities


SocketCAN transmit capabilities are a work in process. You have stumbled open the initial bare and largely unimplemented functions. I do not expect that we will implement full network citizenship for socketCAN, at least initially. SocketCAN bus writing will be present, however, for basic support of plugins that might want to use N2K to control, for example, an Autopilot.


And yes, 77 is the address hardcoded into this Beta for native socketCAN support. Not n2k-negotiated, just there for testing basic functionality.
Thanks
Dave

[LeaseOnLife]

AIS targets stay yellow..


Above I stated that AIS ships show when N2K is the only source. The ships showed a brighter than normal green, so the names have been stored before in mmsitoname.csv.


After deleting mmsitoname.csv and then starting O, the ships stay yellow.

[LeaseOnLife]

Originally Posted by Hakan

Adjust Comm priority is for navigational data for OCPN core only. See the labels in the list.

Plugin Dashboard though would use the sources you mentioned. Please test.

I typically use tactis_pi (without N2K), but here I tried dashboard with N2K source only:

• GNSS status shows no satellites
• wind history gets cleared every so often and starts from scratch with empty graph
• in the combined AW/TW gauge, sometimes one of the pointers shows wind from the other side, see screenshot. that can last for a minute and then both pointers are on top of each other for while again, as it should be, I am at anchor.

With that, I see that values for wind are getting to the dashboard. But which ones? I can fudge wind data in signalk and send them to N2K. Ie: use SOG instead of STW for TW calcs, or do heel correction via node-red and send those out to N2K.


Will there be a separate priority dialog for a core plugin like dashboard? make so much sense

[Hakan]

Originally Posted by LeaseOnLife

AIS targets stay yellow..
After deleting mmsitoname.csv and then starting O, the ships stay yellow.

A AIS target stays yellow until OCPN has received the ship's name and the color change to dark green.
Once seen the target's name is saved and on next program start a position report is enough to identify the ship and if present in the mmsitoname file the color is light green until the ship's name is again received.

Studying the code the AIS ship name is for N2k reported by these PGNs:
Class A PGN 129794
Class B PGN 129809

So if the ship stays yellow OCPN may not have received actual PGN(s) but only the position reports?

[LeaseOnLife]

Originally Posted by Hakan

A AIS target stays yellow until OCPN has received the ship's name and the color change to dark green.
Once seen the target's name is saved and on next program start a position report is enough to identify the ship and if present in the mmsitoname file the color is light green until the ship's name is again received.

Studying the code the AIS ship name is for N2k reported by these PGNs:
Class A PGN 129794
Class B PGN 129809

So if the ship stays yellow OCPN may not have received actual PGN(s) but only the position reports?

I don't think so. I waited long enough and O with N2K as only source does not show a name for any of the AIS targets.


In contrast:

• my Zeus chartplotter only has a N2K connection, and shows the name of the ships after some time.
• Using the TwoCan plugin as only source will show names after some time

looks to me the problem is in O