Dashboard-Tactics (Dash T)

[rgleason]

Yes, I believe it is possible to extend the number of instruments, as Petri had made changes to lift the limit essentially doubling it.
Isofar as this instrument goes, yes it should be completely feasible, the problem is I am not a totally competent programmer, I take the challenge but but may need some help from others.

Originally Posted by Baikal

Is it possible to add a simple GPS distance odometer with a reset button in the settings to the tactical dashboard?
The GPS Odometr plugin is not suitable. clogs up the toolbar and works in a separate window. This functionality should be in the dashboard

[rgleason]

@Baikal

Upon reflection, I think you should address some of these issues with Lennart, (he is quite responsive) so that the format of the GPSodometer improves and you using that new tool too. After those improvements are done, we can see about integrating it, but it is best not to loose focus, and in the end, having the tool separate may prove to be easier.

If you were to post to the GPSodometer thread, describing the improvements you would like, with some screenshots as an example. I am sure he will respond. Keep in mind he just did an update, so it will be the next time he releases perhaps.

[Baikal]

rgleason
I spoke with Lennart about this
he cannot implement it on his own, he needs support
https://github.com/LennartG-Sve/GPS-...ment-948278925
I propose to discuss this in the topic GPS Odometer

[rgleason]

Baikal, good plan. I'll listen. and help where I can.


Hans, after a good deal of struggle (and some help from Dave) we have a new version of dashboard_tactics_pi 1.6.7.0. Dave will be adding the commit to the PIManager catalog shortly.



This is an interim version to replace the older version disappeared from cloudsmith a week or so ago due to retainage settings. I would like to now focus on the issue you've identified. I will download and run your example next. Also give the new version a try please. Thanks.

[rgleason]

Hans, Yes apparent and true do not track, however what data does this file have in it?


Is is letting Dashboard_tactics compute the true wind data from apparent? Or are there sentences with true wind. Lets see.

With your file in a text editor, doing searches, with our NMEA0183 Sentences available

Exist and of interest

1. VWR relative wind speed & angle, exists, regular
2. MWV wind speed and angle, exists, regular
3. HDG Heading magnetic, exists, regular
4. GPRMC Recommended min nav info, has speed over ground
5. GPGLL none
6. VDO PNKEP or ROT I don't know what these are do you?
7. What other sentences are in this file?

Not of interest

1. VLW Log, Distance traveled through water
2. AIVDM AIS many of these, ignore
3. XDR for barometer and roll, exists, regular
4. VLW distance traveled through the water, exists, regular
5. MDA meteorological composite (obsolete) use XDR instead - remove this.
6. MTW mean temp of water, exists, regular
7. VWT true wind speed & angle (old), does not exist.
8. MWD wind direction and speed, does not exist.

Filter out the MDA from the data stream for sure, has wind in it.
Generally, try to filter the unneeded sentences out keeping just the basic data needed. This will stabilize your Dashboard too.


Lets keep learning about this case.

[rgleason]

I see that PNKEP is Niki performance.
Do you have any dampening set for COG or SOG? ...not that it would make a difference.
Do you have Force true wind calculation checked? That does not change things much.

Looking at the file as below, it appears that as the wind changes direction and varies, there is some discontinuity in true and apparent wind, but generally they follow each other.

What are the source of these files? Did you doctor them at all?
I have to think about this some more....


Maybe you should try filtering out MWV or VWR.
MWV https://gpsd.gitlab.io/gpsd/NMEA.htm...peed_and_angle
VWR https://gpsd.gitlab.io/gpsd/NMEA.htm...peed_and_angle


I would suggest starting with MWV first. Also get rid of MDA.


For this plugin, I need to get the B&W icons working and somehow get the spacing and formating for text entry fixed in some of the screens.

[hasse_A]

Originally Posted by rgleason

Rick,

Is is letting Dashboard_tactics compute the true wind data from apparent? Or are there sentences with true wind. Lets see.

It is letting Dash_T calculate True wind direction. See attachment.

Originally Posted by rgleason

Filter out the MDA from the data stream for sure, has wind in it.
Generally, try to filter the unneeded sentences out keeping just the basic data needed. This will stabilize your Dashboard too.

Done

/Hans

[hasse_A]

Originally Posted by rgleason

Maybe you should try filtering out MWV or VWR.

I would suggest starting with MWV first. Also get rid of MDA.

Done. Se attachment.

I am running with VDR-file as input and I am a bit surprised that the MWV and VWR are not marked as filtered and dropped. (Violet colored)

/Hans

[hasse_A]

If I click in "Use SOG instead of STW for True wind Calc." I get sporadic True wind angle but in this case the boat is not moving. Shouldn't STW and True Heading calculated from Magnetic Heading and the use of WMM be enough ?

If we take it to the extreme. Lets say STW=0. Current is setting you sideways at 10 knots. I have a hard time understanding how Dash_T would be able to calculate the correct Wind Angle if it is using SOG.

Anyhow the display goes blank often. Probably a timeout. I instrumented the code and increased the timehout to 20 from 10 but it did not change the beauvoir.

/Hans

[rgleason]

Hans,

You haven't explained how you obtained the file you attached, some details about the equipment used etc. Petri did extensive testing on this plugin. Have you tried filtering out the sentences that I suggested? - Ah forgive me I see your post below now. Let me give this a try. I meant filter one or the other, preferably MWV. We may have to talk with Petri if he is available.

Please read https://github.com/canne/dashboard_tactics_pi
We are using version mnt151 which is not the development version and all the solutions were akso included with the Thomas' standalone Tactics_pi plugin

and this
https://github.com/canne/dashboard_t...tone%3Av1.5.11

[hasse_A]

The wind, water speed and magnetic heading are sent from Raymarine instruments and translated from the NMEA 2000 bus to NMEA 0183 by an Actisence . This information is feed to a multiplexer where ROLL and Baeameter is added to the data stream.
The multiplexer communicates to the Win 10 PC with, either USB or WiFi.
In this case the data is received on WiFi. I have recorded this data with VDR.

Note I get no Checksum errors, and how could it matter how the data is gathered ? You have the VDR-file and it's data is not working.

I can make a new recording, excluding AIS, ROLL and Barometer data if you feel this would be easier to have an overview of.

I can't do this right now as I am in the middle of a flue and need to do this on my buddies boat and I don't want to expose him. On the boat I am on right now there is no NMEA 0183 interface for the wind instruments.

Is it not possible to just filter out the messages not wanted ?
I can do it if you want. Will need to write some program though.

/Hans

[hasse_A]

Originally Posted by rgleason

https://github.com/canne/dashboard_t...tone%3Av1.5.11

I get the impression the problem should already have been solved ?
Am I downloading the wrong code ?

/Hans

[rgleason]

Hans, I have a question about this on opencpn github, but VDR plays files and the nmea0183 shows up in the NMEA0183 debug window without needing any "Connections". The VDR data stream is just being piped directly to Opencpn so there is no way of filtering sentences.

The filter at the bottom of the Nmea0183 window is just a "View filter" which shows a specific sentence, the other sentences are still running.

So, the best way to filter out these sentences is to use your text editor and the search and replace function. Do that, save the file with an appropriate name and run it, and post it up here too.

The sentences to try first are MWD, MWV, AIVDO, AIVDM (filter them all out please)

Petri and others have tested this extensively. The problem is more about the variation in the data being received I believe. Also I note that your boat is moving slightly even though it is not shown in the data.


So what code are you downloading exactly! Why not use the PIM plugin? The nmea0183 VDR file may be the problem.

[rgleason]

Hans, read this


https://github.com/canne/dashboard_tactics_pi/issues/47


and this


https://github.com/canne/dashboard_tactics_pi/issues/84


and this


https://www.cruisersforum.com/forums...ml#post2991179

[rgleason]

There is your answer. Slow Seatalk Data causes the jitter. Data speed maters. Timestamps are essential.
1. Change your instruments to Nmea2000 and use signalK.

Which gives 0.85 seconds before the AWA instruments catches up with its neighbor. That's very visible, indeed.

The AWA sentence delivered by my (dead slow) ST60 arrives in average 1.8 second interval, worst case well over 2 seconds as provided by OpenCPN to the plugin and then further distributed to the instruments (see below for detailed statistics).

The data is provided at that moment to the instrument object through its SetData() method. If the this happens after the Draw() method is called, it is too late, since the arrow, for example is redrawn each time in this method and if the correct data is not there, it is not there.

What might be the update interval of your AWA/AWS data containing sentences?

While an excellent tool for debugging, the NMEA recorder does its playback in a monotonic rate since it does not record / use timestamps in the data file. Therefore it is perhaps too fast to detect this type of issues.

The obvious remedy is to increase the frequency of the incoming data from the ridiculous 0.5 Hz (in my case). But since this is not possible without changing the instrument, I attempted to reduce the quite important jitter caused by the NMEA event-driven distribution system of OpenCPN.

How? I bypassed entirely the OpenCPN (previously it was reading directly the USB) and got all my wind data from Signal K server's "delta" TCP port 8375: that's a thread against a thread, a socket against a socket, fast and furious! I managed to reduce the jitter considerably and the SetData() gets called more accurately. I got a video with much more better synchronized needles to a human eye and with a worst case like this