Tactics Plugin

[rgleason]

Lepinard, I have only encouraged, tested and suggested things to Thomas, the plugin and the documentation is all written by him. He's done a great job, and I think he'll respond to your ideas.

He has given us an alternative if we do not have a heel sensor, so I expect he'll listen to your suggestion.

Suggest you put this suggestion in Tracker.

[tom_BigSpeedy]

Originally Posted by LEPINARD

However by having an option available such as "force True Heading to SOG" we could continue to have great functionalities using the approximation that the surface current is backyard or frontyard (but not lateral).

Lepinard, all you will see is the speed difference between SOG and STW.
That means the "current" display will always be directly from bow or stern,
in other words the component of the current along the centerline of the boat, assuming your STW(speed through water) is calibrated correctly.
And all of the polar based functions rely on compass heading and STW.
So I don't really think it makes sense, as the informations will lack reliability (it is already error prone due to possible calibration issue).

I can put it on my list of todo's but it'll take a while. I have only limited time, and I'm still struggling to get the laylines-to-waypoint going and to lift the whole plugin on github.
And when that's done, we should get it going under linux, etc...

But you can simply give it a try and use the NMEAConverter plugin to create a HDG (compass) sentence from your COG.
That's the easiest and quickest way for now to get you going.


Thomas

[rgleason]

Good idea NMEA Converter | Official OpenCPN Homepage

But you can simply give it a try and use the NMEAConverter plugin to create a HDG (compass) sentence from your COG. That's the easiest and quickest way for now to get you going.

Did not realize that would force current to the vector component normal to the keel, so I think that's probably of more limited interest as we can see that component from the current arrow. By the way, does the arrow get longer with more current? I suppose that could be one for later.

It sounds to me like the first thing to do is to calibrate instruments and then re calibrate until you are sure they are good!

[LEPINARD]

Hi Thomas and Rick
First sorry for two mistakes.

- Thank you Thomas for this great job.
- and the second one the option that will be nice is Force HDT to COG (and not HDG to SOG as I wrote)

I beleive that with such option we could have without Heading sensor (expensive) alredy nice info such as the part of the surface current in the axis of the boat, and the lay lines, vmg ratio cmg ratio despite the approximation. that is already not bad.

I anderstand however you have other priorities.

I have tried with NMEA converter and manage to have HDG firt and HDT infos but did not succeed to have Pi-Tackticks correct. I still have a compass heading at 999° and a true Heading at 1003°

I attach the vdr tfile that I Use for test (from this last summer) (I had a .xls terminaison to upload) and a screen copy of the NMEA stream and what I get with Tacktics.
May be it will help o debug.

All my best and once again that is a great job!
Cumulus

[tom_BigSpeedy]

Lepinard,

do you see heading (HDG/HDT) correctly in the original dashboard ?

It should be identical for dashboard_pi and tactics_pi.

Thomas

[LEPINARD]

Thomas
If you look at the sceen copy you will see stranges things
In tacktics
Thrue Heading 1003
Cap compas 999

in dash bord
True heading empty
Cap compas there is two One is correct the other one is empty.
I am bloddy lost
Thanks for your help
Cumulus

[tom_BigSpeedy]

Lepinard,

here you go ...

You had a wrong setting in nmeaconverter_pi ...


You missed the second field from VTG ...
This one should work, see also screenshot.

$XXHDT,$IIVTG1,$IIVTG2

And you will need manual heel input like this to see some "current" :


But remember that setting HDT to COG will give you no drift angle at all (except maybe a small portion via the manual heel input), so you will not see any real current display.
The only thing that remains is the speed difference between STW and SOG, which means that you will get only the vector of current along the keel line of your boat.

I suggest to set a fixed heel angle to 0 (see screenshot above), to avoid side effects with manual heel input at very low speeds and small speed differences between SOG and STW

Happy sailing in Greece.

Thomas

[LEPINARD]

HI Thomas

THis is great !!! It works well !
look at the screen shot .

Thank tou very much for help . soon I will test it on the sea.

Just a little problem on the display of SOG and STW (see screen shot)

All my best and good job!
Cumulus

[tom_BigSpeedy]

Originally Posted by LEPINARD

Just a little problem on the display of SOG and STW (see screen shot)

Strange ...
Standard dashboard functionality I thought ...

What does it read in the background ? Something like "Vitesse" ?
I can't read it, resolution is too bad ...

Does it also happen when you change the language of O to English ?

Thomas

[LEPINARD]

Thomas
Hard to read also for me : seems to be "vitesse". I have switch O to "english" and you are right, It is OK.
I have notice also that the translation in french of the dashbord is not so good.

Cumulus

[tom_BigSpeedy]

Maybe there's a CR/LF in the French translation of the headline (instrument description) of the SOG / STW instruments ...

Actually I didn't do any specific translations yet for tactics_pi, so O must use some standard translation files ...

Thomas

[LEPINARD]

I was trying to understand why I have no current speed and direction on opencpn (in french)...
And when I switch O to english as you proposed, It worked correctly.

Conclusion
In french
SOG and STW display is poluted by something
No Current speed nor direction.
No current arrow

In english
All is ok .

Thanks for all Thomas.

Cumulus

[LEPINARD]

In fact the current is not computed and displayed some time

To restore the computation we have to set manual heel input ok (the current appears) and then back to fixe max leeway

Cumulus

[tom_BigSpeedy]

I just uploaded a new version, with stabilized layline-to-waypoint calculation
Doc updated to Rev1.4 as well

VirusTotal
SHA256: 49f55ca3e6da7979ec88d2f1f9dde1f851bd0d31a0c9c0f760 91e32e29f38ca4
Dateiname: tactics_pi.dll
Erkennungsrate: 0 / 56
Analyse-Datum: 2016-06-11 08:35:38 UTC ( vor 0 Minuten )
0
0

Analyse
File detail
Zusätzliche Informationen
Kommentare
Bewertungen

File identification
MD5 3a0119da9862dce3e1ff7a70afb57172
SHA1 06a4ede3c97eb8eae6c44af2349103c2c3003fc5
SHA256 49f55ca3e6da7979ec88d2f1f9dde1f851bd0d31a0c9c0f760 91e32e29f38ca4
ssdeep
6144:xgRDsFh6tSOVvEkloRuNTDUBIvf3i7LuK7HRa4cSigfx9 oJLvSfageQz63zIFxOw:eCh6tZVt6RuNXyLu5eeZGTsEY2

authentihash 0495e0a84dd30024a08a524a3af8239749e8aa216e693c8214 b91df83a04fd1d
imphash ac9fd7a0388b7cb6199c19443c502f54
File size 637.0 KB ( 652288 bytes )

Thomas

[rgleason]

Thanks Thomas!,

Lepinard,

I was trying to understand why I have no current speed and direction on opencpn (in french)...
And when I switch O to english as you proposed, It worked correctly.

Thomas has been working on the plugin itself, and no language system or po files have been setup. That will come later. Perhaps you will volunteer to provide the french translations in growd source when the time comes?
Gilletarom often does this for French, he's sailing in Norway now.