Dashboard-Tactics (Dash T)

[rgleason]

This thread is intended for questions and discussion about Dashboard-Tactics.


Manual: Dashboard-Tactics Manual (Currently located under Logs, may move.)
Repository: Github Repository
Download: First Release Dash-T Current Release on Top
Quote from Github Readme:

"If you are using both the built-in Dashboard and the Tactics plug-ins in OpenCPN v5 or greater, you may want to have but one plug-in instead of two to have all available instruments available in one place. Even if you are not interested in Tactics functions, it has also improved a few aspects of the plain Dashboard, like export/import functions and streaming. This version comes with more resources allowing it to be expandandable, to host even more (!) instruments talking NMEA-2000, such as engine monitoring, mast rotation, etc.
Tactics functions provide information to help you sail better - ranging from true wind data to advanced functions which allows a selection of the best head sail for the next tack. Please read further about it and other advanced features here:

• Tactics and performance functions
• Influx DB 2.0 ouput streaming and export
• Signal K data input streaming
• all docs - (HTML/PDF formats)

Petri also has recently made it be known that:
"If the pull request [dashboard_pi: Accept malformed Navico DPT NMEA0183 messages] gets accepted before the 30th of November, I will integrate it to keep v1.5.11 compatible with Dashboard_pi as I have announced. Not that I am particularly happy that one manufacturer's error is silently fixed down in the core NMEA-parser (+20 years old) without informing the user. But that is the project's choice, not mine.'

"I am glad to see that Dashboard_pi is not dead. I wish it long life, in fact! After 30th November I will not support Dashboard_pi compatibility anymore in DashT next versions - most of the code has not been updated in ages and is a limiting factor to the new features I am planning. That's why I will drop dashboard_pi OpenCPN version from my code base - I am grateful for the excellent starting point both the dashboard_pi and tactics_pi code have provided, of course! Time to move forward."


I will likely be using Dashboard-Tactics instead of Dashboard.

[SCarns]

Just noticed the Rudder Angel is inverted. I checked it against "Dashboard", which is correct.

[rgleason]

Thanks SCarns, I got a couple of screenshots while checking, during a big turn to starboard.

[jean_pfoumf]

Hello,
issue (W7/PC and Raspbian/RPI).
When you use the 2 screens canvas and move the Tactics dashboard it becomes horizontal.
If you click "Undock" it comes back to vertical but horizontal again if you move it.
Same with previous tactics plug-in but not with the standard Dashboard.


Jean

[Schnapsy]

There is a problem with the translation (file *.po / *.mo ...).

In Dash-T, the French translation of the device names does not appear above the dials, it is the name in English that appears.

And if I modify the file .po /.mo (opencpn-dashboard_tactics_pi.mo), no change is taken into account...

[SCarns]

Hi guys,

I installed a new Raymarine autopilot. The EV-1 sensor is suppose to transmit heel and yaw (or pitch & roll, whatever). Heel seems as if it would be important in tactics. But I get nothing? So I don't know if this information is coming through in 0183 or if O5 just doesn't see it. Can someone point me in the right direct and tell me what I should be looking for?

[hoolie]

O5 does show pitch and heel on the standard dashboard from our Airmar sensor. Check your NMEA debug window for the XDR sentence from the EV-1.

I don't know whether dashboard-tactics shows these values

[rgleason]

Here are many closed Issues for Dashboard-Tactics

Some examples:

O-DT-TA-1-010 : Provide correction to apparent wind angle and speed data based on the heel angle [R26] #23

O-DT-DA-2-001 : Dashboard instrument support for Unicode direction symbols [R30] #35
https://unicode.org/charts/nameslist/n_2190.html

O-DT-TA-1-017 : Calculate the surface current [R27] #47


See the Long Term Maintenance (two branches)
https://github.com/canne/dashboard_t...pers/README.md

[SCarns]

Hi Rick!

I logged the NMEA stream on O5 and the XDR sentence isn’t coming through. I can trigger it with the correct sentence from NMEA converter, so either the sensor isn’t sending the info or the Yacht Devices nmea 2000 interface iant translating it. Or both.

[rgleason]

Originally Posted by SCarns

Hi Rick!

I logged the NMEA stream on O5 and the XDR sentence isn’t coming through. I can trigger it with the correct sentence from NMEA converter, so either the sensor isn’t sending the info or the Yacht Devices nmea 2000 interface iant translating it. Or both.

I think it is Yacht Devices. Do you have software that will access their stream? I think tactics_pi would be the same result because O is not getting the XDR sentence, but you could try that.

[rgleason]

Originally Posted by hoolie

O5 does show pitch and heel on the standard dashboard from our Airmar sensor. Check your NMEA debug window for the XDR sentence from the EV-1.

I don't know whether dashboard-tactics shows these values

lease see this post by Petri
https://github.com/canne/dashboard_t...ment-511156952
Petri has tested for leeway and heel. Also refer to

"Section 4.2 Heel Angle Corrections.
Sailboat-Performance-Testing-Techniques.pdf "
See figure 20 and the earlier formulas.

At the bottom Petri states:


"we shall use the following approximation for easier implementation in OpenCPN event driven (no DB) which would require to create intermediate buffers about the preceding (or following!) AWA correction. The below formula is safe estimation of paper's observation about issues a cup-anemometer has with heel: which you call cosine response. It is noteworthy to mention that this approximation is probably not valid with ultrasonic instruments.

aws_corrected_for_heel = aws_measured / cos(heel) "

[rgleason]

By the way, I believe all of Petri's fixes were back ported to Thomas and Tactics_pi.


Also Dashboard-Tactics has a cmake switch which will compile only the corrected Dashboard Instruments, without the set of Tactics Instruments.

[rgleason]

Several screenshots of Dashboard-Tactics



With VDR_pi Reading the Sample2.txt file from Tactics_pi


Then when VDR_pi reading is shut off, within a short period of time almost all fields show --- or "no data" I noticed that perhaps because I set heel to manual, that heel field doesn't go blank.


Then there are two different shots of Preferences, the last one shows that Heel is set to manual, in my case.

[rgleason]

Now turned on Heel sensor in Preferences and it works.

[rgleason]

Schnapsy, Petri has provided a very detailed answer for all of us here.
https://github.com/canne/dashboard_t...ment-575918522


The short answer is that we need to create a new language file that includes both the tactics and the dashboard words and add that to the internationalization cloud site so that authors can edit and upload, then that file can be included in the compilation. Petri does have a link to the internationalization website. I think if someone were to provide him with a PR for the language files he would merge.

Originally Posted by Schnapsy

There is a problem with the translation (file *.po / *.mo ...).

In Dash-T, the French translation of the device names does not appear above the dials, it is the name in English that appears.

And if I modify the file .po /.mo (opencpn-dashboard_tactics_pi.mo), no change is taken into account...