Increase "Own Vessel" render update time

[imp-cruiser]

I was wondering if it were possible to increase (or decrease) the render update time for the "own vessel" when using GPS NMEA stream as input connection.

Currently, I think the update time is 1 second. (Chances are I might have missed something very obvious in the settings, in that case, my apologies.)


Thanks!

[nohal]

Originally Posted by imp-cruiser

I was wondering if it were possible to increase (or decrease) the render update time for the "own vessel" when using GPS NMEA stream as input connection.

Currently, I think the update time is 1 second. (Chances are I might have missed something very obvious in the settings, in that case, my apologies.)


Thanks!

The frequency of updates from most of "normal" GPS units is 1Hz, which means once per second.
Unless of course you explicitly bought one that supports higher update frequency, in which case you have to use the configuration software for that GPS unit to switch it to the mode where it produces the data more frequently.

[Moo]

Originally Posted by imp-cruiser

I was wondering if it were possible to increase (or decrease) the render update time for the "own vessel" when using GPS NMEA stream as input connection.

Currently, I think the update time is 1 second. (Chances are I might have missed something very obvious in the settings, in that case, my apologies.)


Thanks!

What are you trying to achieve?



But anyway try this:

[imp-cruiser]

Originally Posted by nohal

The frequency of updates from most of "normal" GPS units is 1Hz, which means once per second.
Unless of course you explicitly bought one that supports higher update frequency, in which case you have to use the configuration software for that GPS unit to switch it to the mode where it produces the data more frequently.

For testing purposes I streamed NMEA data ($GPRMC) over the network (TCP). I can play with the update frequency (and my original NMEA file already updates every 0.1 second); however, the vessel's position in the viewer only changes every second? Am I missing something?

I tried checking the source (and changed some parameters), but did not find a specific parameter or function related to this so far (I realize the code is quite extensive and I might have looked into the wrong files :-)).

[imp-cruiser]

Originally Posted by Moo

What are you trying to achieve?

But anyway try this:

For now, I was just streaming NMEA data over the network (TCP) for simulation purposes. I do plan on sailing using realtime iGNSS as input, but so far I was looking into the possibilities of the viewer. Consequently, faster update times of the vessel location could be useful (I'm testing some custom waypoint following methods, among other things, using OpenCPN as visual feedback).

[Moo]

Originally Posted by imp-cruiser

For now, I was just streaming NMEA data over the network (TCP) for simulation purposes. I do plan on sailing using realtime iGNSS as input, but so far I was looking into the possibilities of the viewer. Consequently, faster update times of the vessel location could be useful (I'm testing some custom waypoint following methods, among other things, using OpenCPN as visual feedback).

Have you tried changing the update time that I highlight? Do you really need updates more frequently than 1 second?


Are you trying to use course up?


Is the ownship icon you need to update faster, or the highway in the route popup window?



Chris

[nohal]

Originally Posted by imp-cruiser

For testing purposes I streamed NMEA data ($GPRMC) over the network (TCP). I can play with the update frequency (and my original NMEA file already updates every 0.1 second); however, the vessel's position in the viewer only changes every second? Am I missing something?

I tried checking the source (and changed some parameters), but did not find a specific parameter or function related to this so far (I realize the code is quite extensive and I might have looked into the wrong files :-)).

If you do not enable the data filter mentioned by Moo, the ownship is updated as fast as the data is available and technically possible. It is much faster than once per second on all systems I have ever seen.

[seandepagnier]

I have hacked in support to update AIS targets in realtime since they often get updates only 20 seconds and less if you miss a message.

This draws a different color boat in the "extrapolated position" in addition to the normal boat which is at the last message location. I didn't submit this yet, it adds another checkbox to the ais options unfortunately. It doesn't utilize turn rate in the calculation. I'm not sure it should.

I sometimes wonder if AIS could transmit intended future course, like the route the autopilot is following which could improve this even more if there are turns ahead and it would be interesting to plot these, but I don't think AIS standard supports this.


I also draw the planes in a similar way showing realtime positions from the adbs rendering in the rtlsdr plugin.

[imp-cruiser]

Originally Posted by Moo

Have you tried changing the update time that I highlight?

Yes, nothing changes (both for increase and decrease).

Originally Posted by Moo

Do you really need updates more frequently than 1 second?

Well, not really; however, the real vessel is rather small, and for testing (simulating), for instance, a collision avoidance program (outside OpenCPN), using OpenCPN merely as a visual feedback tool, it would be useful. Ultimately, AIS as well as ENC chart objects from OpenCPN could be used as complementary data, as it already provides interpretation for this.

Originally Posted by Moo

Are you trying to use course up?

I tried both ways (north up and course up).

Originally Posted by Moo

Is the ownship icon you need to update faster, or the highway in the route popup window?

The ownship icon (for now)

[imp-cruiser]

Originally Posted by nohal

If you do not enable the data filter mentioned by Moo, the ownship is updated as fast as the data is available and technically possible. It is much faster than once per second on all systems I have ever seen.

For example, my .nmea looks like this (for less than two seconds):

$GPRMC,104242.90,A,5108.05362, ...
$GPRMC,104242.92,A,5108.05362, ...
$GPRMC,104242.94,A,5108.05362, ...
$GPRMC,104242.96,A,5108.05362, ...
$GPRMC,104242.98,A,5108.05362, ...
$GPRMC,104243.00,A,5108.05361, ...
$GPRMC,104243.02,A,5108.05361, ...
$GPRMC,104243.04,A,5108.05361, ...
$GPRMC,104243.06,A,5108.05361, ...
$GPRMC,104243.08,A,5108.05361, ...
$GPRMC,104243.10,A,5108.05361, ...
$GPRMC,104243.12,A,5108.05361, ...
$GPRMC,104243.14,A,5108.05361, ...
$GPRMC,104243.16,A,5108.05361, ...
$GPRMC,104243.18,A,5108.05361, ...
...

Maybe updates only occur when the last character (second) of the timestamp changes (e.g. from 2 to 3)?

[Hakan]

For this NMEA sequence OCPN does what it get. Even though the RMC message are sent more often the latitude is not changed more than once. So here OCPN does what it should. It may be the GPS sends often but not change the position more than once per second?

[imp-cruiser]

Originally Posted by Hakan

For this NMEA sequence OCPN does what it get. Even though the RMC message are sent more often the latitude is not changed more than once. So here OCPN does what it should. It may be the GPS sends often but not change the position more than once per second?

Hm. Position (longitude and latitude) also changes over one second (~0.1 s).

[nohal]

Originally Posted by imp-cruiser

Hm. Position (longitude and latitude) also changes over one second (~0.1 s).

Would you mind posting the actual data? And exact instructions on how to replay them at the speed you are replaying them?

[imp-cruiser]

Originally Posted by nohal

Would you mind posting the actual data? And exact instructions on how to replay them at the speed you are replaying them?

Sure. Temporary link: https://nextcloud.svbaelen.org:444/i...PSMfcLgk5zXmAz

More info on the replay method in file header (stream.py).

[imp-cruiser]

Originally Posted by boat_alexandra

I have hacked in support to update AIS targets in realtime since they often get updates only 20 seconds and less if you miss a message.

Do you mean to decrease the update time interval? I guess AIS has a similar minimum of 1 second in the viewport. On the other hand, current AIS systems only allow updates every 2 seconds (tops, up to x minutes, depending on the "Class"). In this case it does not really matter. (Although next generation systems will increase bandwidth, among other improvements, significantly, so this might change in the next few years?)

Originally Posted by boat_alexandra

This draws a different color boat in the "extrapolated position" in addition to the normal boat which is at the last message location.

That's interesting! I am planning on doing something similar (drawing "additional object") based on different sources (onboard sensors, AIS, ...)