Semi-automatic digital logbook for Signal K

[bergie]

It's done, but please review it carefully. As I said it's the firt time i put my hands on a React app :S

Had to do some minor adjustments, but it is merged now. Thanks again! Will be in the next logbook release.

[MigGat]

Glad to help!

[bergie]

Glad to help!

I just released 0.5.0 with this patch.

[Relax]

I just tested this app. It seems nice. I sail with various crews. Would it be possible to have different crew sets to choose from? It's a bit tedious task to change the crews.

[bergie]

I just tested this app. It seems nice. I sail with various crews. Would it be possible to have different crew sets to choose from? It's a bit tedious task to change the crews.

Would need some thinking and design. Could you file a feature request in the GitHub repo? And if you have some sketches on how you think the UI could look like, please share!

[bergie]

Thanks everybody for the comments and bug reports! I released 0.6 yesterday incorporating a lot of the feedback received.

[Caribsailor]

First I would like to say thank you to Bergie and collaborators!

The Logbook is my most used WebApp in SK. I am slowly getting data compiled in it.

I do have some questions for guidance on a few things.

I have read the readme. many times and have had success from it. The challenge i'm having is locating the files to backup. I'm not a coder (but the learning curve has started) and I can seem to locate the file from the readme description.

The second one, is getting engine hours and trip logs into the Logbook.

I'm currently cruising in Belize and working on building my ship server with OpenPlotter. Internet is spotty. Not complaining.

Thank you again and thank you in advance for any guidance.

Cheers

[bergie]

For engine hours, you can have Signal K operate a counter: https://www.npmjs.com/package/signalk-hour-meter
You need some way for Signal K to know the engine is running. For example, RPMs. On our boat we use alternator output for this: https://www.npmjs.com/package/@meri-impe...-engine-on

Trip logs require something to output navigation.log. On my boat this is done by the paddle wheel sensor. GPS based method would also be doable, see https://github.com/meri-imperiumi/signal.../issues/62

For backup, you need to locate the .signalk directory. That is by default in the home folder of the system user that Signal K runs as, but may be also different in your setup.

---

BTW, if somebody wants to see how the mostly-automated logs look like, we publish ours as part of our blog posts. See for example yesterday’s sail on the Szczecin lagoon: https://lille-oe.de/2023-04-12/

[Caribsailor]

For engine hours, you can have Signal K operate a counter: https://www.npmjs.com/package/signalk-hour-meter
You need some way for Signal K to know the engine is running. For example, RPMs. On our boat we use alternator output for this: https://www.npmjs.com/package/@meri-impe...-engine-on

Trip logs require something to output navigation.log. On my boat this is done by the paddle wheel sensor. GPS based method would also be doable, see https://github.com/meri-imperiumi/signal.../issues/62

For backup, you need to locate the .signalk directory. That is by default in the home folder of the system user that Signal K runs as, but may be also different in your setup.

---

BTW, if somebody wants to see how the mostly-automated logs look like, we publish ours as part of our blog posts. See for example yesterday’s sail on the Szczecin lagoon: https://lille-oe.de/2023-04-12/

Thank you for your quick reply!

Here the data  from the data browser.
   
The engine status populates to the Logbook, but unsure on why the engine hours does not. (Engine hours is correct)

As for the trip log.  Data from the Data Browser
   
I have it populating to the SK instrument panel webapp, but again, does not populate to the Logbook.

Thanks again.

[bergie]

Logbook uses navigation.log, not trip log. See https://github.com/meri-imperiumi/signal.../issues/32

The engine hours path will need to be propulsion.*.runTime (where * is your engine name. For example, “main”). You can use the signal k path mapper plugin to make those match.