OpenCPN Version 5.7.1 Beta Test #1

[Hakan]

Originally Posted by LeaseOnLife

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

• GNSS status shows no satellites

• GNSS status use PGN 129540 for satellites status and satellite system from 129029. Is 129540 received?

  wind history gets cleared every so often and starts from scratch with empty graph

  If the wind history graph is emptied it may be due to seldom received data relative north? We use now a 6 seconds watchdog That was good for a Raymarine sensor. Maybe we could lengthen that watchdog?

  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.

  Wind data is from PGN 130306. That PGN has five modes or wind references:
  1) magnetic or 2) true direction relative north,
  3) apparent wind relative center line,
  4) true wind angle relative center line and speed relative ground,
  5) true wind angle relative center line and speed relative water.
  So rather complicated. What wind sensor do you use producing the PGN? or if you produced them in another system is the wind reference flag used correct?
  We have had one Raymarine N2k sensor to test on.
  Also bear in mind to see wind data over ground, 4), you have to select that option in Dashboard Preferences Appearance.
  

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

  No user editable priority is planned. Dashboard's inbound priority is basically 0) Nav-data from OCPN core, 1) N2k, 2) SK, and then different N0183 messages dependent on type of data. Due to the sometimes very complex collection of sources a priority dialog would not be very feasible. What a user can do is to select what data to feed into OCPN and for N0183 use the Connection's filter function.

Both for this issue and the AIS ship names we really would like have some example to test if possible. Do you have the opportunity to capture - (candump -L) your N2k data and share? Will be possible if you've a Linux system.

[LeaseOnLife]

Originally Posted by 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.

Hakan, scratch that, I was wrong... I was too impatient to wait for ships at anchor to send out PGN with name... after waiting a bit longer all targets turned green. Thanks!

[LeaseOnLife]

Originally Posted by Hakan

• GNSS status use PGN 129540 for satellites status and satellite system from 129029. Is 129540 received?

on the sat status:
I have 2 GPSs connected to N2K: Sitex MDA-5 AIS receiver (native N2K) and a N183 gps feeding B&G 2000 wind/depth system which feeds a Simrad AT10 N183-N2K translator.


looking at the N2K with signalk I can see both GPSs on the bus, see screenshot. I have source #43 selected in the priority catalog, but O-dashboard decides to us the old GPS (#73) with 7 satellites in view, while the newer GPS built into the AIS sees 21..


PGN129540 does not seem to exist on my N2K bus, not received from either GPS


Having multiple GPS on N2K is very common, many of the MFDs now have a built-in GPS, plus the usual AIS-transceiver GPS, plus an external GPS that also does pitch/roll for the autopilot. ==> there has to be a selection method

[Hakan]

Originally Posted by LeaseOnLife

[/LIST] on the sat status:
I have 2 GPSs connected to N2K: Sitex MDA-5 AIS receiver (native N2K) and a N183 gps feeding B&G 2000 wind/depth system which feeds a Simrad AT10 N183-N2K translator.

Do you know which PGN the AT10 supports? It really has some limitations. A Acticens or a YD may have done a more reliable job nowadays? (I know, they cost!)

looking at the N2K with signalk I can see both GPSs on the bus, see screenshot. I have source #43 selected in the priority catalog, but O-dashboard decides to us the old GPS (#73) with 7 satellites in view, while the newer GPS built into the AIS sees 21..

Yes, we know... working on that. The goal is to inform Dashboard about present SAT-source and let GNSS Status instrument all time use data from the same.

PGN129540 does not seem to exist on my N2K bus, not received from either GPS

That's essential for GNSS Status! Compare N0183: xxGSV. Is the AT10 involved here as well?


Thanks.
Håkan

[bdbcat]

LeaseOnLife....
Thanks for the report on AIS target name cache. There was a problem there, corrected now for next Beta. Works fine with a logfile you sent me earlier.
Good Luck
Dave

[LeaseOnLife]

on to the wind...

Originally Posted by Hakan

• If the wind history graph is emptied it may be due to seldom received data relative north? We use now a 6 seconds watchdog That was good for a Raymarine sensor. Maybe we could lengthen that watchdog? Wind data is from PGN 130306. That PGN has five modes or wind references:
  1) magnetic or 2) true direction relative north,
  3) apparent wind relative center line,
  4) true wind angle relative center line and speed relative ground,
  5) true wind angle relative center line and speed relative water.
  So rather complicated. What wind sensor do you use producing the PGN? or if you produced them in another system is the wind reference flag used correct?
  We have had one Raymarine N2k sensor to test on.
  Also bear in mind to see wind data over ground, 4), you have to select that option in Dashboard Preferences Appearance.

For these tests I do not send any calculated wind values from signalk/node-red to the N2K bus. signalk only sees apparent wind speed and wind angle data from source #2 see screenshot.

There is more than one heading source on my system... the B&G compass (via the AT10 N183=>N2k) as well as a Maretron N2K compass for faster heading data for radar overlay on a chart. That may cause some weird effects, including the reset of the strip chart.



I certainly can do a candump -L, the file will be big. PM me with a email address to send that to.

[Hakan]

LeasOnLife..
Heading:
In the new OCPN priority you can set which one to use in OCPN.
And if OCPN use a HDT that one will also be used in Dashboard so basically the two HDT sources shouldn't cause a problem.
But could you test the priority function to see if you can set one prio from two equal PGN. A PGN example: [nmea2000 COM3:127:129029] If your ...:127:... is different for the two HDT it would theoretically work?
Wind:
If you only send apparent wind Dashboard will try to calculate true wind using HDT and SOG if present. Then a "jumping" HDT can cause trouble and not less if you're anchored and SOG is not stable. I'll check the code. We wouldn't calculate true wind if SOG is to close to zero?
I'll check and come back if the candump is needed.
Thanks
Håkan

[zigzag930]

On MacBook Pro, running Montery 12.6.2, the chart bar is very small. Unable to select charts as the "Arrow" for scrolling covers the chart bar selection

[LeaseOnLife]

Originally Posted by Hakan

LeasOnLife..
Heading:
In the new OCPN priority you can set which one to use in OCPN.
And if OCPN use a HDT that one will also be used in Dashboard so basically the two HDT sources shouldn't cause a problem.
But could you test the priority function to see if you can set one prio from two equal PGN. A PGN example: [nmea2000 COM3:127:129029] If your ...:127:... is different for the two HDT it would theoretically work?
Wind:
If you only send apparent wind Dashboard will try to calculate true wind using HDT and SOG if present. Then a "jumping" HDT can cause trouble and not less if you're anchored and SOG is not stable. I'll check the code. We wouldn't calculate true wind if SOG is to close to zero?
I'll check and come back if the candump is needed.
Thanks
Håkan

I moved a N2K heading source up all the way, wind history still gets cleared every 10-20 minutes..
I found that , at least for the last ~10 minutes, dashboard TWA is always to port, never to starboard., see screenshots whiles swinging at anchor. AWA seems to be correct:

[LeaseOnLife]

Originally Posted by Hakan

LeasOnLife..
But could you test the priority function to see if you can set one prio from two equal PGN. A PGN example: [nmea2000 COM3:127:129029] If your ...:127:... is different for the two HDT it would theoretically work?

It certainly lets me select / move the priorities even with equal PGNs. If that doesn't answer your question, please re-ask

[mgrouch]

On which platforms does it use wxWidgets 3.2? I see on arm64 focal it is still linked with wxWidgets 3.0

Thanks

[bdbcat]

mgrouch...
Hmmm That is clearly a bug. I will investigate.


Thanks
Dave

[bdbcat]

ZigZag...


"On MacBook Pro, running Montery 12.6.2, the chart bar is very small. Unable to select charts as the "Arrow" for scrolling covers the chart bar selection"


Could we see a screenshot, please?
Thanks
Dave

[bdbcat]

mgrouch...


"On which platforms does it use wxWidgets 3.2? I see on arm64 focal it is still linked with wxWidgets 3.0"


I spoke too soon earlier. Not a bug.
wxWidegets 3.2 is available on ubuntu Jammy (22.04) and later.


Dave

[Hakan]

Originally Posted by LeaseOnLife

I moved a N2K heading source up all the way, wind history still gets cleared every 10-20 minutes..
I found that , at least for the last ~10 minutes, dashboard TWA is always to port, never to starboard., see screenshots whiles swinging at anchor. AWA seems to be correct:

Lease...
I found some small fixes for N2k wind angels. It may be they explain your reported issues.
The wind history graph issue may also be corrected dependent on the cause on your system.
On its way to Git master.

Thanks for testing and reporting.