Giters

OpenCPN / OpenCPN

A concise ChartPlotter/Navigator. A cross-platform ship-borne GUI application supporting * GPS/GPDS Postition Input * BSB Raster Chart Display * S57 Vector ENChart Display * AIS Input Decoding * Waypoint Autopilot Navigation

Home Page:https://opencpn.org/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Two Signal K connections: No prioritization.

Hakansv opened this issue · comments

commented

Describe the bug
If two Signal K connections, to different servers, are active there's no prioritization between the two. Pict 1
If both contain GNSS positions the ship is "jumping".
Also can the self ship from one source create a target symbol beneath own ship from the other source. See pict 2

To Reproduce
Steps to reproduce the behavior:

  1. Connect a Signal k source including GNSS from one SK-server
  2. Connect a second Signal K source, including position, from another SK-server.
  3. Both are active as ships position. Alternating.

Expected behavior
Handle each SK-source as an individual source.
I think this scenario is not anticipated but may be a further user case. A forum post may indicate the same.
We may discuss this is a bad user case. The two different GNSS sources may be solved by SK-filtering on one of the server?
Not an easy task.

Screenshots
Pict 1 with connections and priority list. Only one source detected.
Pict 2 with a "ghost" ship symbol. Actually self MMSI.
Desktop (please complete the following information if applicable):

  • OS: Win
  • Version 5.9 current master.

bild

bild