Unfortunately, there's nothing a plugin can do for this. The plugin inject NMEA data (including AIS) as any input port would do. So this behavior would be the same with aisReplay or any other tool injecting NMEA. There's no "clear" or "reset" switch and I guess there'll never be. IMHO, it's a corner case.
Gilletarom, re: clock ; it's not related to the VDR plugin. The clock instrument currently available in the dashboard plugin is a local PC clock, not related to NMEA input. That's why, when replaying a previously saved stream, the clock doesn't match. A NMEA clock could be added, but would probably be UTC (IIRC, NMEA time input is UTC. I don't remember if date is available as well) Feel free to open a request in flyspray for this (if there's none yet) in the dashboard plugin
I had VDR working well in the old version 2.** but when I switched to 3.0 it won't load.
I got this error message that makes me think it wants a 32bit processor I am running a 64 bit
See attached screen shots.
You just have to copy the dll to the plugins subfolder of your OpenCPN installation. From your screenshots it appears that you are for some reason running OpenCPN with a commandline parameter containing the path to the dll in your temporary location - Could it be, that you selected "Open with..." or something like that while trying to download the plugin?
Sorry again for being such a poor reader. Works perfectly. I am integrating a new radar, chart plotter display and ais with this. Your help is so much better than what I get from the manufacturer of my radar.
I have something strange going on with my heading information. It's solid on my plotter and autopilot but in open cpn it jumps around, I want to see what the sentencing is saying.
Try to play with the COG & SOG filtering setting and try to set the filtering period to something like 5 seconds. The correct value for this depends on how "smart" your GPS actually is, so some experimenting might bring better behavior.
Your heading in the other devices is probably a compass heading (HDM, HDG or HDT).
COG will jump around whenever your vessel has a SOG close to zero.
This is due to the way GPS and COG calculation works.
I haven't come across a way to get compass heading in open cpn yet, so maybe this is a feature to be requested.
Well, I get it now. It isn't getting heading from compass data?
That seems like it would cause problems with the AIS display as well.
Here is what I get with both displays head up, radar and cpn.
The boat seems to be oriented properly. I thought it was looking at compass data for that. But the jumping around when I am sitting at the dock gives a very unstable COG of course.
If we get an overlay project going I think radar's work off compass heading data, the charting program should also. Thinking about it, AIS doesn't require a compass heading but it should. Relative bearing relates to the direction the boat is pointed not the direction of travel.
Well, i'm not (yet) an expert on open cpn, so i could have missed something.
But up untill now, i haven't seen antything in the toolbox relating to compass processing.
I agree with your opinion that compass should be used, and in SOLAS setups compass is mandatory.
Radar doesn't necessarily require compass, but most yachts do use it in order to be able to have north up display.
Having compass data makes radar overlay much easier, but it is possible without it.
You would need a very high quality radar signal and processing for this to work without compass data.
In inland installations, radar overlay combined with AIS requires compass data.