Tweaks

Most of the defaults settings are enough to get started with DashT plug-in and many of the key parameters can be changed using the Preferences dialog. However, under the hood there are many more parameters which one could not possibly put in the Preferences dialog without making it totally confusing and overstuffed. Maybe one day there will be an effort made to create a way to set these “advanced parameters” with some Graphical User Interface (GUI) solution.

But until that day comes, you can get many things shaped to behave to your liking if you are able to use a text editor: When OpenCPN is not running, open its ini/conf-file and follow the instructions in this chapter to make your modifications.

The OpenCPN configuration file is located in:

Windows \ProgramData\opencpn\opencpn.ini

Linux ~/.opencpnp/opencpn.conf

Since we do not want to attempt to replace OpenCPN documentation, please open the OpenCPN user’s guide on your computer platform if you cannot find the configuration file from above locations.

NOTE: It goes without saying - make a backup copy of the file before start tweaking with it!

TIP: In the same directory you have the OpenCPN log file. If something goes wrong, it is good to take a look at the end of that file where the most recent start-up logs are located. You can search lines having string “dashboard_tactics_pi” which is used by DashT for its log messages (there are usually only few, but if you do not see any, it means quite likely that DashT never gets loaded by OpenCPN).

In below sections we explain by owner and by key the meaning and eventual usage of each key.

OpenCPN

PlugIns

[PlugIns]
PluginOrder=ChartDownloader;GRIB;VDR;DashT
LatestCatalogDownloaded=Master

If you do not see here DashT in the list there can be an issue with the OpenCPN plug-in manager.

Windows:

[PlugIns/dashboard_tactics_pi.dll]
bEnabled=1

Linux:

[PlugIns/libdashboard_tactics_pi.so]
bEnabled=1

dashboard_tactis_pi is the name of DashT in the OpenCPN plug-in catalog. If bEnabled=0 then DashT remains disabled: use OpenCPN plug-in manager instead of attempting to tweak this setting yourself.

AUI

[AUI]
AUIPerspective=layout2|name=ChartCanvas;caption=;state=768;dir=5;layer=0;row=0;
pos=0;prop=100000;bestw=5;besth=5;minw=298;minh=915;maxw=-1;maxh=-1;floatx=-1;
floaty=-1;floatw=-1;floath=-1|name=DASHT-57881c38-fd95-4000-83bf-3804e5d7179;
caption=AvgWind;state=2098121;dir=4;layer=0;row=0;pos=0;prop=100000;bestw=325;
besth=425;minw=325;minh=425;maxw=-1;maxh=-1;floatx=8;floaty=614;floatw=313;
floath=431|....

If you are wondering where OpenCPN’s wxWidgets stores the DashT many window positions (in this example, window pane named AvgWind), this is the place. There is nothing you can do by editing but if you have issues, you can delete all the entries before the restart and all windows (not only those of DashT) will be piled up above each other so that you can rearrange them. If the instrument cluster window pane’s ID changes for some reason (by your tweak?), its position will be lost and it will be reopened in the default position.

DashT

Dashboard

Version=2
SpeedometerMax=12
COGDamp=0
SpeedUnit=0
SOGDamp=0
DepthUnit=3
DepthOffset=0
DistanceUnit=0
WindSpeedUnit=0
TemperatureUnit=0
UTCOffset=0

It is recommended to use Configuration Dialog which provides full wxWidgets platform specific interface to set these values.

Key / Parameter	Description
Version	Leave it as 2 - this is the compatibility flag with the OpenCPN Dashboard sometimes used in the code, you do not want version 1 features (backward compatibility has not been tested)
SpeedometerMax	Speedometer maximum numerical value
COGDamp	0 = turns damping off. Value 1 gives 1/2 = 0.5 damping factor = no damping, >0.5 = damping - see below note
SpeedUnit	-1 = use OpenCPN setting, 0 = [kts], 1 = [mph], 2 = [km/h], 3 = [m/s]
SOGDamp	0 = turns damping off. Value 1 gives 1/2 = 0.5 damping factor = no damping, >0.5 = damping - see below note
DepthUnit	3 = [m], 4 = [feet], 5 = [Fathoms], 6 = [Inches], 7 = [Centimeters]
DepthOffset	0 = no offset, otherwise offset in meters (albeit the dialog asks it in centimeters), can be negative or positive floating point value like 0.5; multiplied internally to match the corresponding DepthUnit selection
DistanceUnit	-1 = use OpenCPN setting, 0 = [NMi], 1 = [statute miles], 2 = [km], 3 = [m]
WindSpeedUnit	0 = [kts], 1 = [mph], 2 = [km/h], 3 = [m/s]
TemperatureUnit	0 = Celsius, 1 = Fahrenheit
UTCoffset	Divided in 48 steps, from -24 to 24, presenting half an hour offsets from -12:00 to 12:00. Eg. -2 is equivalent of -01:00

NOTE: About COG/SOG filter value: With all the respect, the built-in Dashboard documentation must be mistaken telling that “1” is presenting no filtering; it is activating the filtering code but the filtering is, presumably not altering the signal: dashboard_pi.cpp:    mSOGFilter.setFC(g_iDashSOGDamp ? 1.0 / (2.0*g_iDashSOGDamp) : 0.0);. If you look at the code of iirfilter.cpp the value 0.0 turns the filtering completely off. Here is an excerpt of the description of the iirfilter: The parameter is a setting to a single order inifinite-impulse-response filter: The value defines filter’s cutoff frequency. A value of 0.5 is basically no filtering and smaller values decrease the cutoff frequency. If you think of the filter as being “fast” or “slow” then 0.5 is fastest and smaller values are “slower”. The OpenCPN Dashboard built-in documentation tells us “A typical filter value of 10 seems to work pretty well.”. That ends up as \(1/(2*10)=0.05\) for the iirfilter. If we mark the requested iirfilter cut-of value with \(v\), and the ini/conf file setting with \(a\), then \(a=1/(2v)\).

Fonts

Fonts are quite difficult to tweak but you can try. They get their default values by wxWidgets library’s adaptation to the operating system platform on which it is running:

Windows:

FontTitle=1;10;-20;0;0;0;400;1;0;0;1;0;0;2;32;Arial
FontData=1;14;-28;0;0;0;400;0;0;0;1;0;0;2;32;Arial
FontLabel=1;8;-16;0;0;0;400;0;0;0;1;0;0;2;32;Arial
FontSmall=1;8;-16;0;0;0;400;0;0;0;1;0;0;2;32;Arial

Linux:

FontTitle=Sans Italic 10
FontData=Monospace Bold 14
FontLabel=Monospace 8
FontSmall=Monospace 8

However, there is perhaps no need to modify anything here, since the Configuration Dialog provides full wxWidgets platform specific interface to set these highly platform specific values.

Instrument fonts

There is one tweak possibility provided by DashT compared to the OpenCPN Dashboard plug-in or its forks: we can set the default values and fonts in advance before these are set, in more generic terms. This allows to experiment with what values wxWidgets sets for this operating system. Set the values below to your liking, remove the above fields and start OpenCPN with DashT plug-in enabled:

[PlugIns/DashT/Fonts]
TitleFontSize=10
TitleFontFamily=SWISS
TitleFontStyle=ITALIC
TitleFontWeight=wxNORMAL
DataFontSize=14
DataFontFamily=TELETYPE
DataFontStyle=NORMAL
DataFontWeight=BOLD
LabelFontSize=8
LabelFontFamily=TELETYPE
LabelFontStyle=NORMAL
LabelFontWeight=NORMAL
SmallFontSize=8
SmallFontFamily=TELETYPE
SmallFontStyle=NORMAL
SmallFontWeight=NORMAL

Please see for the available values in wxFont documentation which is not going to be repeated here (yes, we use the short names, they will not go away).

NOTE: the above settings are actually designed to be able to pass the user choice from the Dashboard preferences dialog to the JavaScript-based instruments stylesheets - the instrument styles are CSS/SASS controlled. However, nothing has been implemented yet, so if you change something here, the JavaScript instrument’s font will not change, sorry, remains in to-do list.

TIP: Meanwhile, please remember that the JavaScript instruments are executed on a kind of a browser window. Depending of the operating system on which you are running you can try to zoom in / zoom out. Typically this is Ctrl-(plus-key) and Ctrl-(minus-key), and Ctrl-(zero-key) to get back to 100% zoom.

Colors

This tweak allows you to change and experiment with the look of the instruments - other than the baro-, wind- and performance history displays which remains on the white background due to their “hair-line” printing by making one pixel-size dots around the canvas (it is not impossible, but really challenging color world…).

[PlugIns/DashT/Colors]
BackgroundColor=DASHB
ForegroundColor=DASHF
LabelColor=DASHL
RedColor=DASHR
GreenColor=DASHG
IllustrationsColor1=DASH1
IllustrationsColor2=DASH2
NeedleColor=DASHN
SecondNeedleColor=BLUE3
CentralCircleColor=UBLCK
CompassBackgroundColor=COMP1
EmbossedNeedle=1
EmbosNeedleContourColor=UBLCK
ShowRedGreenFace=1
LowDegRedGreenFace=20
HighDegRedGreenFace=50
ForeroundColor=DASHF

You guessed it right - the colors are coming from OpenCPN and the idea of OpenCPN is to provide - not perhaps the most elegant way - color themes which allows to circulate around the “day”, “dusk” and “night” themes. You can find the currently (OpenCPN v5.2) available colors here.

It is better to stick to OpenCPN defined names for colors so that you respect (at least to some extent) the the “day”, “dusk” and “night” themes. An example of such usage is available here.

Extra dial tweaks

Key / Parameter	Description
EmbossedNeedle	When 1 creates an illusion of an embossed needle, set to 0 if you want the classical, flat one
ShowRedGreenFace	Red and green circles, present in some dials can be turned off by setting 0 here
LowDegRedGreenFace	If the above remains in 1, then one can set the angle in which the informative red / green circle segments ends

Dashboard index

DashboardCount=5 - one thing you need to understand with the OpenCPN and wxWidgets dashboard management using the ini/conf-file is that it does not delete the old dashboard block from the ini/conf-file, it just decreases the counters if you delete a dashboard (a window pane collecting instruments) or an instrument in it. At startup we loop on this counter and search for the following block structures - let’s check the anatomy of one of those:

[PlugIns/DashT/Dashboard3]
Name=DASHT-57881c38-fd95-4000-83bf-43804e5d7179
Caption=AvgWind
Orientation=V
Persistence=1
InstrumentCount=1
Instrument1=73
InstrumentID1=
Instrument2=91
InstrumentID2=71ced54e-9110-4dd7-a778-ec133c11496f
Instrument3=27
InstrumentID3=

Key / Parameter	Description
Name	DASHT-[UID] to make difference from Dashboard instrument panes, prefix is different and UID algorithm more advanced
Caption	You can see this in the window pane title and in the Preferences
Orientation	V = vertical; H = horizontal
Persistence	Badly chosen name since it is more like ‘visible by default’; make sure that you have at least one dashboard (window pane) visible, otherwise you need to go to plug-in manager to get hold of the Preferences dialog
InstrumentCount	As mentioned this is used to control the actual instruments, not the entries below which can be more numerous than the instrument count - they are never deleted by wxWidgets - maybe there is a way to do it but OpenCPN Dashboard has not considered it necessary (and it certainly is not the end of the world)
Instrument1	The number is the index on which the OpenCPN Dashboard will loop to create instruments on a window pane called “dashboard” - the type is an internal code for instrument type, in this case a Tactics Average Wind instrument
InstrumentID1	This instrument is of an old OpenCPN Dashboard type and it does not need a unique identifier
Instrument2	The instrument in this position was a DashT Race Start but it is gone now
InstrumentID2	DashT adds an unique ID for all instruments. This is used to store the parameters of a web based instrument, for example by the system’s web browser library. TIP: to make such an instrument to ‘forget’ it setting, just change any number in the string to something else!

There can be even more of ‘forgotten’ instruments. If you are really bugged by these, or even ‘forgotten’ instrument panes you can very well remove them, there is no harm.

DashT/Tactics

NOTE DashT attempts to keep full compatibility with Tactics instruments and algorithms; there is no way to guarantee that all parameters are available in both plug-ins. Therefore, if using DashT use this documentation and if you are using Tactics plug-in, use its own documentation.

CurrentDampingFactor=0.003
LaylineDampingFactor=0.2
LaylineLenghtonChart=5
MinLaylineWidth=2
MaxLaylineWidth=30
LaylineWidthDampingFactor=0.2
ShowLaylinesOnChart=1
ShowCurrentOnChart=1
CMGSynonym=CMG
VMGSynonym=VMG
DataExportSeparator=;
DataExportUTC-ISO8601=0
DataExportClockticks=0
TacticsImportChecked=0

Key / Parameter	Description
CurrentDampingFactor	The layline damping factor determines how fast the laylines react on your course changes, i.e. your COG changes. Low values mean high damping. DashT Tactics recommends values from 0.002 to 0.008 to start your experimenting with.
LaylineLenghtonChart	The width of the boat laylines is based on the yawing of the boat (vertical axis), i.e. your COG changes. The idea is to display the COG range where you’re sailing to.
LaylineLenghtonChart	Length of the boat laylines in [nm]
ShowLaylinesOnChart	Toggles laylines visibility as an overlay on the chart canvas. 0 turns them off and 1 back on.
ShowCurrentOnChart	Toggles current arrow visibility as an overlay on the chart canvas. 0 turns it off and 1 back on.
CMGSynonym	This setting allows you to whatever abbreviation you want for the self-explanatory vector Tactics algorithms is calculating. Finishing the endless discussions in the forums about the meaning of life, too bad!
VMGSynonym	Same reason for the existence of this abbreviation settin. I guess that the author of the mentioned, albeit simple vector chart just got enough of it = do what you want!
DataExportSeparator	This is used by all CSV-export functions - such as baro-, wind- and performance history - as separator. Space as separator (not recommended) requires “ “ quotes around it. TAB as separator presents as “\t". All printable characters do not require quotes around them. Maybe you want to stick to semicolon (default) and comma (as file name implies), after all.
DataExportUTC-ISO860	You want to set this to 1 if you plan to import the CSV-file later on some application like a time series database, or perhaps some Python script. The dull second as time accuracy is not enough for them. But for your eyes and for your wristwatch only, you do not need this
DataExportClockticks	Same, the aforementioned application types like timestamps. This is the best of it all, milliseconds since EPOCH! (a trivia question: were you born before or after the Unix Epoch?)
TacticsImportChecked	This is used only if you have both the excellent and light-weight Tactics plug-in installed together with DashT - you are suggested to import Tactics settings into DashT and you can continue to use Tactics as before, the two will not get mixed

Performance

PolarFile=C:\\Program Files (x86)\\OpenCPN\\plugins\\
weather_routing_pi\\data\\polars\\yourboat100.pol
BoatLeewayFactor=10
fixedLeeway=30
UseHeelSensor=0
UseFixedLeeway=0
UseManHeelInput=1
CorrectSTWwithLeeway=0
CorrectAWwithHeel=0
ForceTrueWindCalculation=0
UseSOGforTWCalc=0
ShowWindbarbOnChart=1
ShowPolarOnChart=1
PersistentChartPolarAnimation=1
Heel_5kn_45Degree=5
Heel_5kn_90Degree=8
Heel_5kn_135Degree=5
Heel_10kn_45Degree=8
Heel_10kn_90Degree=10
Heel_10kn_135Degree=11
Heel_15kn_45Degree=25
Heel_15kn_90Degree=20
Heel_15kn_135Degree=13
Heel_20kn_45Degree=20
Heel_20kn_90Degree=16
Heel_20kn_135Degree=15
Heel_25kn_45Degree=25
Heel_25kn_90Degree=20
Heel_25kn_135Degree=20
ExpPolarSpeed=0
ExpCourseOtherTack=0
ExpTargetVMG=0
ExpVMG_CMG_Diff_Gain=0
ExpCurrent=0
NKE_TrueWindTableBug=0
TwaMarkUseShortAvgWind=1

Key / Parameter	Description
PolarFile	(a single line, BTW) Your boat’s polar, or a polar close to your boat - you get plenty of those with the weather_routing_pi plug-in! See Tactics Polar file discussion - it is not a bad idea to prepare several of those for your boat, say 90%, 95%, 100% and 105%(!).
PolarLookupTableOutputFile	Same as the above but use a .csv extension for a comma separated value output file which is built from the above PolarFile according the algorithm explained in Tactics Polar section. Once you haver recovered your file and inspected it, you may want to remove this line from your configuration file - there is no need to create at every start!
BoatLeewayFactor	Leeway is the ‘drift’ of the boat due to heel/wind influence. Low values mean high performance of hull. If we mark Leeway as \(L\), BoatLeewayFactor as \(c\), Heel angle as \(a\) and Speed Through Water STW as \(v\) then \(L(v) = c * a / v^{2}\) - one word, keep you paddlewheel clean!
fixedLeeway	This parameter has dual purpose to limit the Leeway in calculations, depending of the UseFixedLeeway : if 0 (use a heel sensor or manual “heel polar”) then this value limits Leeway to this maximum value; if 1 (do not use manual heel ‘polar’ nor the heel sensor): Leeway gets this value.
UseHeelSensor	Use the internal heel sensor if available. Important for the correct calculation of the surface current.
UseFixedLeeway	Select the behavior of fixedLeeway parameter
UseManHeelInput	If no heel sensor is available, you can create a manual “heel polar” below. Just read/enter the data from a mechanical heel sensor (e.g. available on compass). Use True Wind Speed & Angle only ! Take care: motoring w/o sails and a heel will show wrong current data!
CorrectSTWwithLeeway	Correct STW with Leeway: apply a correction to your log speed throughout the plug-in based on the calculated Leeway and Current. Does make only sense with a real heel sensor. Make sure your instruments do not already apply this correction!
CorrectAWwithHeel	Correct AWS/AWA with Heel: Use with care, this is normally done by the instruments themselves as soon as you have an integrated, original equipment heel sensor. But if it your own heel sensor, this can make a use of it!
ForceTrueWindCalculation	Force True Wind Calculation: Internally calculates True Wind data (TWS,TWA,TWD) and uses it within the whole plug-in even if there is True Wind data available via NMEA or Signal K.
UseSOGforTWCalc	Use SOG instead of STW for True Wind Calculations: Recommended (as the True Wind blows over the earth surface, we should calculate it with Speed Over Ground. This eliminates the influence of currents). > > > However, some sailors say that are interested in how the wind blows over the water, so you can make your choice here! > > > BTW, some other, innovative sailors are even using the great pair of software DashT or Tactics only for this feature while their paddlewheel has got stuck - well, it is like going to plough a potato field with a Ferrari! Better not think too much about this usage for not to lose motivation…
ShowWindbarbOnChart	Toggles wind barb visibility as an overlay on the chart canvas. 0 turns it off and 1 back on.
ShowPolarOnChart	Toggles the polar visibility as an overlay on the chart canvas. 0 turns it off and 1 back on.
PersistentChartPolarAnimation	Toggles the persistent Tactics overlays visibility as an overlay on the chart canvas. Persistent means here that even if you minimize all the DashT instruments by toggling the DashT button on the OpenCPN toolbar - perhaps to clean out the chart area, the real-time calculations and the corresponding Tactics overlays keep on being animated around the boat, perhaps helping you in your sailing. 0 turns this feature off and 1 turns it back on.
Heel_5kn_45Degree	This is the first in the series of the manual ‘heel polar’, give the value in degrees. Remember, here TWS = 5 knots and TWA = 45 degrees. Do not use AWS/AWA!
n/a	NKE format ($PNKEP) : Currently only set up for NKE instruments. Exports a predefined set of up to five NMEA records which are “known” by NKE instruments and can be displayed there. Please read the manual how to set up the interface connection and read more details about the contents of the NKE sentences. You got it right, there is no switch other than to select which PNKEP-format sentence will be sent out.
ExpPolarSpeed	Target Polar Speed (PNKEP01)
ExpCourseOtherTack	COG on other Tack (PNKEP02)
ExpTargetVMG	Target VMG angle and performance percentage (PNKENP03)
ExpVMG_CMG_Diff_Gain	Angles to optimize Target VMG and Target CMG and corresponding gain (PNKENP04)
ExpCurrent	Current direction and speed (PNKENP05)
NKE_TrueWindTableBug	In case this is 1 this is used for internal debugging and replacement of its MWD sentence provided TWS. Provided that you are using DashT from the original distribution, nothing will happen with your MWD sentence: the experimental threshold m_VWR_AWA has been set to 10.0 but it needs to be lesser than 8.0 before this variable takes whatsoever action. If you are a happy NKE owner and want to experiment with this, it is necessary that you make your own fork and you set the m_VWR_AWA lesser than 8.0 to experiment with this. In this case, if the condition hits, you will see a debug message in the OpenCPN log file. For the rest of us, the sheer mortals this parameter has no effect. But better explain it, since you see it…
TwaMarkUseShortAvgWind	This is controlling the instrument TWA to Waypoint in a way how it is using the integrated wind data provided by the Average Wind instrument (which is, actually a background process) providing short and long integration time. If the wind is very stable, you can as well use the long integration time. Or for some other reason you may prefer it - in this case set this value to 0

AverageWind

[PlugIns/DashT/Tactics/AverageWind]
ShortAvgTimePercentage=25
AvgTime=240

Key / Parameter	Description
ShortAvgTimePercentage	Ratio in percentage of the AvgTime minimum percentage is 10, default is 25, maximum is 50
AvgTime	This is the normal “long” integration time, minimum and default is 240 seconds = 4 minutes, while the maximum is 1800 seconds = 30 minutes

BaroHistory

[PlugIns/DashT/Tactics/BaroHistory]
Exportrate=60
BaroHistoryExportfile=C:\\Users\\JoeDoe\\Downloads\\barotest.csv

Export rate is in seconds.

PolarPerformance

[PlugIns/DashT/Tactics/PolarPerformance]
Exportrate=5
BaroHistoryExportfile=C:\\Users\\JoeDoe\\Downloads\\perftest.csv

Export rate is in seconds.

Windhistory

[PlugIns/DashT/Tactics/Windhistory]
Exportrate=5
BaroHistoryExportfile=C:\\Users\\JoeDoe\\Downloads\\windtest.csv

Export rate is in seconds.

Odograph

[PlugIns/DashT/Tactics/Odograph]
GrandTotal=0
DataPointInterval=30
OdographExportfile=C:\\Users\\JoeDoe\\Downloads\\odograph.csv
ShowBoatLog=1

Key / Parameter	Description
GrandTotal	The persistent storage for the total trip counter
DataPointInterval	Time in seconds between the two GNSS points and the distance calculations between them. It is also the time period of the storage in the CSV file. Default value is 30 seconds, equivalent of 77 meters at 5 knots. Minimum value is 10 seconds (51m @10kn). Possible values are 10, 20, 30, etc. seconds, i.e. 15 seconds would become 10 seconds
OdographExportfile	A helper so that one does not type the file name if it remains the same
ShowBoatLog	Put here 0 if you do not want to show the boat’s navigation system’s log-based trip data - for example, if it is also making the log data calculation based on GNSS data

Streamout

[PlugIns/DashT/Tactics/Streamout]
ConfigFile=streamout.json

The quite rich (in features) database schema is set in a separate JSON-file. The default configuration file streams into a file which can be imported into a InfluxDB v2 database. However, it is possible to stream directly into a live database using HTTP protocol. In this case you would modify an existing HTTP-configuration file template and put its name here. See Configuration file management regarding the settings in the JSON-file.

StreaminSk

[PlugIns/DashT/Tactics/SteaminSk]
ConfigFile=streamin-sk.json

In a similar manner like with the output streaming, the Signal K input streaming is configured with a separate JSON file. The default one being good for the local Signal K server node connection you may to make your own copy, if your server is located, for example on another computer.

DashT/WebView

[PlugIns/DashT/WebView]
[PlugIns/DashT/WebView/EngineDJG]
instrujsURL=http://127.0.0.1:8080/enginedjg/
[PlugIns/DashT/WebView/RaceStart]
instrujsURL=http://127.0.0.1:8088/racedashstart/
[PlugIns/DashT/WebView/RaceMark]
instrujsURL=http://127.0.0.1:8088/racedashmark/
[PlugIns/DashT/WebView/TimesTUI]
instrujsURL=http://127.0.0.1:8088/timestui/

This is to explain with a URL the DashT from which network port it can expect to find and fetch the corresponding JavaScript instrument code to be integrated with the DashT dashboard.

The default values correspond to the helper script set services explained in this document.

Nothing prevents to change these values to point to an external server or internally to different ports if you so like, there is no limitation from where the code is coming from, as long as it is from the same DashT version.

NOTE: you may be tempted to use file:// protocol. Be aware that on all operating systems supported by DashT the code fetched with this protocol will not be allowed to save any of its parameters due to obvious security measures the manufacturers have undertaken in recent years. Therefore this protocol support has been definitely dropped from DashT as well.

DEBUG: One can use about:blank in URLs to debug issues on wxWidgets WebView implementation on a particular platform, to eliminate all HTML5 and JavaScript code and their dynamic interactions.

Cache: At every restart or at the orientation change DashT is making a Reload() request on wxWidgets WebView instance to fetch the latest versions of the drivers. But if you change, say EngineDJG paths by modifying the common.js file and expecting your changes being visible in the instrument it may happen that your changes are not getting loaded. This is certainly depending of the wxWidgets WebView implementation on you platform but also of the web server you are using. The tweak in this case is simply to change the name common.js to something else both on the folder and in the index.html file and the restart the OpenCPN application, or to change the orientation of the window pane on which the instruments are located.

Race

[PlugIns/DashT/Race]
[PlugIns/DashT/Race/RaceStart]
LaylineWidth=3
GridSize=1
GridStep=0.026998
GridLineWidth=1
GridBoldInterval=2
ZeroBurnSeconds=60
[PlugIns/DashT/Race/RaceMark]
LaylineWidth=2
RungStep=0.053996
RungLineWidth=2
AvgWindLineWidth=3
ShortAvgWindRungLineWidth=1

Key / Parameter	Description
LaylineWidth	Pen width on the canvas in pixels
GridSize	In [NMi] - a square behind the start line
GridStep	In [NMi] - 50 meters is 0.026998 NMi, minimum is 0.00486 NMi which corresponds to about 9 meters (otherwise you can start playing ‘Painted Black’…)
GridLineWidth	Pen width on the canvas in pixels (for non-bold line)
GridBoldInterval	1=all lines are bold, 2 every 2nd is bold, etc.
ZeroBurnSeconds	Continuously calculate from the polar where the inviting Zero Burn mark should be kept on the COG line and at which point it should disappear if the boat has passed it - or has passed its chance
RungStep	In [NMi] = 100 meters is about 0.053996 NMi
RungLineWidth	Pen width on the canvas in pixels
AvgWindLineWidth	Pen width on the canvas in pixels
ShortAvgWindRungLineWidth	Pen width on the canvas in pixels