Dashboard-Tactics (Dash T)

[rgleason]

Canne, how can we bring dashboard-tactics (your advanced version) into the Plugin Managere (PIM) constellation? What would be necessary?
I know you advised re this before and it required a new version of OpenCPN.

Also as you point out, I should update the line

tmplPath += _T("plugins") + s + _T("dashboard_tactics_pi") + s + _T("data") + s + _T("streamin_sk_template.json"); wxString tmplPath = *GetpSharedDataLocation();

but where should it land?

Is there user configuration data that needs to be written, so we should be using getpPrivateApplicationLocation?


We've had to make this change for flatpak installations and the old version of dash-t is due for that update too.

[Canne]

Thank you, Rick,

For your support to DashT!

@tronco, if your wish is just to get SignalK data in OpenCPN, please note that OpenCPN v5.2.4 you are using supports it now natively. You do need DashT for that anymore.

Originally Posted by rgleason

Canne, how can we bring dashboard-tactics (your advanced version) into the Plugin Managere (PIM) constellation? What would be necessary?
I know you advised re this before and it required a new version of OpenCPN.

No, it does not require a new version of OpenCPN, I am running v2.0 of DashT on OpenCPN 5.2.4 every day. But as it goes for now, the Plug-In Manager and OpenCPN itself follows the paradigm that OpenCPN and consequently, all its plug-ins shall work on all supported platforms, and there are many of them, some of them quite historical. A decision which I fully understand and respect since certainly a key factor to the success of OpenCPN.

But it is too limiting to my needs and in DashT v2.0 onwards I support only Windows 10 Professional and Ubuntu 20.04 LTS (and its derivates) with GTK3.

Unless the OpenCPN paradigm changes and the with it the Plug-In Manager becomes environment aware, proposing only plug-ins for the platforms where they have been effectively tested working (Test plan + test report), it would be totally useless to make a version of a DashT v2.0, say for a 32-bit Raspberry, which is GTK2 based. Some of the functions would work, some of the functions would not for the eventual, unhappy users of this niche-market plug-in.

I would just remove DashT from the Plug-In Manager until then since Dashboard and Tactics exist as separate plug-ins already in it.

Originally Posted by rgleason

Also as you point out, I should update the line

but where should it land?

If you insist... the problem for the above is likely in this line and in this line: in OpenCPN API *GetpSharedDataLocation() function. Instead of modifying the code, one needs to make sure that on the platform you are running, one can find, from the path returned by the above API function, appended with (see the next line in the code)

/plugins/dashboard_tactics_pi/datastreamout_template.json


This to allow that the user who edits the JSON-configuration file from the default values to roll back to the default simply by deleting the modified JSON-file.

Originally Posted by rgleason

Is there user configuration data that needs to be written, so we should be using getpPrivateApplicationLocation?

In the standalone installer I have never had a problem with this function, so I reckon it is related to the different data file location used in Plug-In Manager, which, on the other hard, the OpenCPN *GetpSharedDataLocation() API-function does not take into account. Maybe you are right, by switching to getpPrivateApplicationLocation() it may work. Probably not seeing the nature of the template function need to be copied to the private application folder.

I would like to add that Signal K node server has evolved a lot since 2019 from which this code base dates from: it requires now a mandatory subscription to the delta channel variables one wants to read. Also, InfluxDB v2.0 is now official and not beta: they do not allow GET-method inquiry anymore but only OPTIONS inquiry. So, what good it will make to fix this old code base since it will work only with an old SignalK and an old InfluxDB? My suggestion remains: just drop it.

Originally Posted by rgleason

We've had to make this change for flatpak installations and the old version of dash-t is due for that update too.

See above, while the Plug-In Manager's paradigm is that once it compiles and links it will work I have difficult to believe how flatpak would make that miracle to happen. But I have not tried, of course.

[bdbcat]

Canne...


re:
"But it is too limiting to my needs and in DashT v2.0 onwards I support only Windows 10 Professional and Ubuntu 20.04 LTS (and its derivates) with GTK3."


Just for edification, what types of functions in Dash-T have specific dependencies on W10P and gtk3? That is, what functions are required that are NOT basic wxWidgets functions?


Thanks
Dave

[Canne]

Dear Dave,

JavaScript/TypeScript based instruments/extensions need wxWebView which has been removed from GTK2 based distributions because webkit2gtk is not supported since long time now. I have explained what it takes to make one's own port on, say on Rasberry Buster. The method is not recommended, of course for a professional distribution.

Another problem outside of the OpenCPN ecosystem after that will be that the wxWebView based scripted objects will need to access local servers and services. A CORS-enabled proxy needs to be provided to enable this, otherwise security settings on the system's browser back-end will prevent the access. With older systems I do not know how this would work, due to the first problem with wxWebView.

Hence I am limiting my interest to the systems on which I can test in real life that everything works.

Best regards,

Petri

[bdbcat]

Petri...
OK, clear enough.
As the plugin developer, the decision of which $archs to support and maintain is of course yours, and yours alone.
Of course, it would be nice to have a few builds of Dash-T in the PIM catalog, especially for the most popular platforms. (e.g. Win1, Ubuntu focal, MacOS, etc.)


To help us along, will you list the exact runtime $archs that should be implemented (by Rick) in the OCPN PIM catalog? By this, I mean the $archs that you determine are compatible and functionally complete.


Thanks
Dave

[tronco]

It is possible to export to signal k VMG data. Thanks

[chfeld]

Hi guys,
first, thanks for all your great work!


I posted a feature request a few days ago in ocpn-pi-dashboard, but I think it would perfectly fit here as well:


Universal, user-configurable display for XDR

XDR is used whenever no classical sentence is applicable, and it's becoming increasingly common. The format is quite universal, takes care of different data types and units. So there could be a new module that can handle all cases. The user has to specify the transducer ID and optionally a display name. The module should find the other parameters (type, unit) as soon as it sees a sentence. That should be all that's necessary, at least for a digital display.






Actually, with that configurable display, some others would become maybe obsolete, like barometer, heel or pitch.

[hasse_A]

Hello,

I cant seem to get the true wind speed/angle displayed.
OpenCPN 5.2.0
Dashboard-Tactics 1.6
O/S = Win10

I think I have all the input data needed for DashT to calculate True wind.
It even says so in the log-file. See red line below.
What can be the reason True wind is not shown in "True Wind Angle & Speed" ?
It only gives me 0 degrees and 0 knots.

/Hans

20:36:40.235 MESSAGE chart1.cpp:8814 Changing NMEA Datasource for IIVLW to (Priority: 0)
20:36:40.287 MESSAGE socketutil.cpp:220 radar_pi: multicast reception for 239.254.2.0 port 50100 on interface 192.168.43.243
20:36:40.287 MESSAGE tactics_pi.cpp:1916 dashboard_tactics_pi: Tactics true wind calculations: a valid AWS received, now (4.700000).
20:36:40.287 MESSAGE tactics_pi.cpp:1930 dashboard_tactics_pi: Tactics true wind calculations: Forced calculation requested, no TWD, but has TWA/TWS.
20:36:40.287 MESSAGE tactics_pi.cpp:1976 dashboard_tactics_pi: Tactics true wind calculations: Tactics has now an internal AWA value, (162.100000).
20:36:40.287 MESSAGE tactics_pi.cpp:1992 dashboard_tactics_pi: Tactics true wind calculations: Tactics has no valid intenal AWS value.
20:36:40.287 MESSAGE chart1.cpp:8814 Changing NMEA Datasource for WIVWR to (Priority: 0)
20:36:40.318 MESSAGE chart1.cpp:8814 Changing NMEA Datasource for IIMDA to (Priority: 0)
20:36:40.434 MESSAGE tactics_pi.cpp:2001 dashboard_tactics_pi: Tactics true wind calculations: Tactics has a valid internal AWS value (4.700000).
20:36:40.434 MESSAGE tactics_pi.cpp:2017 dashboard_tactics_pi: Tactics true wind calculations: Tactics has no valid internal true heading value.
20:36:40.434 MESSAGE chart1.cpp:8814 Changing NMEA Datasource for WIMWV to (Priority: 0)
20:36:40.503 MESSAGE chart1.cpp:8814 Changing NMEA Datasource for IIXDR to (Priority: 0)
20:36:40.572 MESSAGE chart1.cpp:8814 Changing NMEA Datasource for HCHDG to (Priority: 0)
20:36:40.619 MESSAGE chart1.cpp:8814 Changing NMEA Datasource for IIMTW to (Priority: 0)
20:36:40.819 MESSAGE chart1.cpp:8814 Changing NMEA Datasource for TIROT to (Priority: 0)
20:36:41.136 MESSAGE chart1.cpp:8814 Changing NMEA Datasource for AIVDO to (Priority: 0)
20:36:41.389 MESSAGE socketutil.cpp:220 radar_pi: multicast reception for 239.254.2.0 port 50100 on interface 192.168.43.243
20:36:41.451 MESSAGE chart1.cpp:8814 Changing NMEA Datasource for PNKEP to (Priority: 0)
20:36:41.637 MESSAGE tactics_pi.cpp:2026 dashboard_tactics_pi: Tactics true wind calculations: Tactics has an internal true heading value, now (145.125479).
20:36:41.637 MESSAGE tactics_pi.cpp:2033 dashboard_tactics_pi: Tactics true wind calculations: AWA unit is availabe, now (°rl).
20:36:41.637 MESSAGE tactics_pi.cpp:2112 dashboard_tactics_pi: Tactics true wind calculations: checks OK, execution of algorithm will be launched.
20:36:42.660 MESSAGE chart1.cpp:8814 Changing NMEA Datasource for GPRMC to (Priority: 0)
20:36:42.723 MESSAGE chart1.cpp:8814 Changing NMEA Datasource for IIVHW to (Priority: 0)

[rgleason]

Is the speed 0 ?
Sorry I am working on other pi right now. Will get to this later.

[hasse_A]

Originally Posted by rgleason

Is the speed 0 ?
Sorry I am working on other pi right now. Will get to this later.

Yes, the STW=0. The true wind speed and direction should be equal.
Now True wind speed =0 and True Wind angle = 0 degrees.
It's ok Rick. I am trying to set up debug environment for DashT to see whats going on. Will see if I get there before any one else figures it out.

[rgleason]

I am kind of surprized because petri did a lot of testing and improved things greatly. Perhaps i changed something when compiling.

Thanks!

[hasse_A]

Rick,

I have recorded stimuli for the scenario. Attaching the file. You can try it out and see if you get the same result.

/Hans

[hasse_A]

The link to the Source code in the Downloads->Dashboard-Tactics plugin page is broken 404.
/Hans

[rgleason]

Hans



One more PI to go then dashboard_tactics
https://github.com/jongough/testplugin_pi/issues/177

The repository is here https://github.com/rgleason/dashboard_tactics_pi
Petri's repos is here https://github.com/canne/dashboard_tactics_pi
both are fine.

[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