Logbook Konni for OpenCPN

[ptulp]

I have a new release for OSX and Linux here: https://github.com/ptulp/LogbookKonn...es/tag/V1.3004


As I don't have a windows environment I could not create a windows version.
If somebody else would be so kind



Thanks,
Peter

[ptulp]

Originally Posted by skipperearly

In case you will implement the XDR could you pls allow settings in the ini/conf file to define match of which XDR parameter goes into which logbook field.
This would be much nicer than another hardcoded solution.

As the XDR data for fuel needs some calculation and the structure of the program, which does not allow dynamic changes at this moment, it is only possible to hardcode it.


Peter

[Schnapsy]

Originally Posted by ptulp

I have a new release for OSX and Linux here: https://github.com/ptulp/LogbookKonn...es/tag/V1.3004

As I don't have a windows environment I could not create a windows version.
If somebody else would be so kind

Thanks,
Peter

Hello Peter,

Thank you a lot for this update, I found in addition that the request "Save data DURING sailing" was taken into account. Bravo !

I am unable for the moment to create a windows version (but I try, despite the lack of relevant information).

Regarding the sentence XDR for fuel, can you confirm that the structure of this sentence is of this style:

$ IIXDR, F, 00.0, L (or G), FUEL, * checksum

Thanks,
Alain

[ptulp]

Originally Posted by Schnapsy

Hello Peter,

Thank you a lot for this update, I found in addition that the request "Save data DURING sailing" was taken into account. Bravo !

I am unable for the moment to create a windows version (but I try, despite the lack of relevant information).

Regarding the sentence XDR for fuel, can you confirm that the structure of this sentence is of this style:

$ IIXDR, F, 00.0, L (or G), FUEL, * checksum

Thanks,
Alain

I found out that the "F" is already defined for Frequency.
The type for flowrate gives a different data type than you want I guess.
So I would suggest "V" for volume. Although the original measurement is in M (Cubic meter), we can adapt that to "L" for liter or "G" for gallon.
So the command would be:
$ IIXDR, V, 00.0, L (or G), FUEL, * checksum


Peter

[ptulp]

Also a windows version is now available here:



https://github.com/ptulp/LogbookKonn...es/tag/V1.3004

[rgleason]

Schnapsy any interest in being made an editor so you can update

Logbook documentation for others?


https://opencpn.org/wiki/dokuwiki/do...s:logs:logbook

I don't believe I will be doing this.
I can make you an editor/manager for the OpenCPN wiki, just PM me with your request and your email which is used for your pw.

[Schnapsy]

Originally Posted by ptulp

Also a windows version is now available here:

https://github.com/ptulp/LogbookKonn...es/tag/V1.3004

Thank you Peter,

But, after verification, the fuel consumption data are not taken into account and the balance remains the same, the initial data do not change in the logbook....

On the other hand, resizing the layout window works perfectly.

[Schnapsy]

Originally Posted by rgleason

Schnapsy any interest in being made an editor so you can update Logbook documentation for others?

https://opencpn.org/wiki/dokuwiki/do...s:logs:logbook

I don't believe I will be doing this.
I can make you an editor/manager for the OpenCPN wiki, just PM me with your request and your email which is used for your pw.

Rick,

No problem to help to complete the instructions.
I propose that we exchange by MP to define exactly what is needed.
I have a meeting this evening, I'll write you tomorrow.

[ptulp]

Originally Posted by Schnapsy

Thank you Peter,

But, after verification, the fuel consumption data are not taken into account and the balance remains the same, the initial data do not change in the logbook....

On the other hand, resizing the layout window works perfectly.

This version 1.3004 does not have the XDR fix yet. I still have to add that functionality.


Regards,
Peter

[skipperearly]

When testing the new logbook version on shore with weak GPS signal I noticed an unexpected behavior of the auto-entry in the konni logbook-pi.

See attached screenshot for details.


Would it be possible to ignore NIL GPS sentences to avoid this?
In fact it would even be better to have an option to set the minimum distance from last GPS reading to get ignored for SOG calculations.

Shall I raise this in tracker or are others (with more reliable GPS units ) not interested?

[ptulp]

Originally Posted by skipperearly

When testing the new logbook version on shore with weak GPS signal I noticed an unexpected behavior of the auto-entry in the konni logbook-pi.

Would it be possible to ignore NIL GPS sentences to avoid this?
In fact it would even be better to have an option to set the minimum distance from last GPS reading to get ignored for SOG calculations.

Shall I raise this in tracker or are others (with more reliable GPS units ) not interested?

Could you check via the NMEA debug window that when the position is zero in the NMEA message, the IsDataValid field set to A or V?.
This should be for the messages GLL, RMB and RMC
Message GGA has the GPSQuality field (0-2)


Thanks,
Peter

[skipperearly]

Sorry Peter, but I will be offshore for the next 2 weeks - will check on return. Thanks for following up.

[ptulp]

Originally Posted by Schnapsy

Thank you Peter,

But, after verification, the fuel consumption data are not taken into account and the balance remains the same, the initial data do not change in the logbook....

On the other hand, resizing the layout window works perfectly.

There is a new version 1.3005 with the XDR message handling.
Again the windows version is not there as I don't have a windows environment.
The plugin for OSX and linux can be found here:
https://github.com/ptulp/LogbookKonn...es/tag/v1.3005.


Peter

[rgleason]

Windows version has been added by Ptulp

[Schnapsy]

Originally Posted by ptulp

There is a new version 1.3005 with the XDR message handling.

Peter

Hello Peter,

I installed the new version 1.3005 and I am testing it at the office.
For now, it does not work.

If I understand the principle correctly, the number transmitted by the NMEA sentence is fitting in the "FUEL column" and is therefore subtracted from the "FUELTOTAL column" ...

I tried with and without the comma behind the name of the transducer (FUEL), ie $IIXDR,V,xx.xx,L,FUEL,* and $IIXDR,V,xx.xx,L,FUEL* but nothing fits in the column FUEL (and therefore FUELTOTAL).

Am I wrong somewhere ?