Logbook App FAQ

The app suddenly stops recording!

Up to version 2.50 it was possible to use the iCloud Sync in the background. This led to data loss for some users (including myself) starting in summer 2021. You can find more details on the iCloud Sync detail page. There is an alternative way to synchronize your logbook across multiple devices, please use the Logbook Synchronization feature!

Can I use the App on multiple devices?

Yes starting with version 2.52 there is an alternative to iCloud to synchronize your logbook across multiple devices, please use the Logbook Synchronization feature!

How to show more than 3 pictures per day in the PDF export?

In the PDF there can be 3 images per page with comments/free texts. If you want to export another 3 images, you have to write so much text (or just line breaks) in an entry that a second page is created. Then again there are up to 3 pictures on that new page. And so on...

How work maintenance records?

Check out this page for details on all 4 redcord types (maintenance, POI, manual, auto).

The covered distance is different to another app I use!

The Logbook App calculates in statistics or PDF exports the covered distance based on the records in your logbook. It calculates always the airline between two records. So if you travel a almost straight line e.g. across the Atlatic Ocean, it is sufficient to create a record each hour. But if your trip goes tack and jibe every few moments across the thousands island of Croatia, it is of value to have many records. So if you are in doubt I suggest you to create more than too less records. Especially as you will be able to exclude these automatic created records from your PDF export, and you can also filter them away in your log overview. But for the calculated covered distance they will count in! And if you decide to add a record retrospectively it is much easier to adjust an existin real record (correct position and time), which will become manual by changing it and show up again in your export.

How to export a part of my logbooks?

It is planned to include a filter option for the start and end date when exporting. Until then there is a workaround you could do. Move all entries that you want to export into a separate logbook, and then move them back again.
Example of records: If you only want to export day 2, create a logbook with a name like TEMP in the settings, then go to your logbook to be exported, open the bottom entry 1), scroll down to the menu item database and move all entries in TEMP. Then switch to TEMP and scroll to the first entry that you want to export. In the example above 3) and from here move everything back into the logbook to be exported. Now switch back to the logbook to be exported and move the part on top that should not be exported back to TEMP, so from 5). Then export your logbook. When you are done, move all entries from TEMP back into the actual logbook and delete TEMP.

I have trouble to receive NMEA data

In order to be able to establish a connection, a connection must exist and you must know the protocol (TCP or UPD), the port and, in case of TCP, also the IP address.
1. Connection
Your iOS device (iPhone or iPad) must be in the same network (WiFi) as the device* that the NMEA data provides, how you can establish this connection (WiFi SSID and possibly password) is to find in the instructions for the device* you are using.
2. Protocol
Here, too, please take a look at the instructions for your device* that supplies NMEA data. Generally there is UDP or TCP. With TCP, your NMEA device* is a server (receiver) and waits for someone (i.e. your iPhone / iPad) to come and ask what NMEA data is currently available. With UDP it is the other way around, the iPhone / iPad opens a server (receiver) and waits for someone (your NMEA device*) to come by and deliver NMEA data. That's why you don't need an IP address with UDP, because the sender needs to know it and not the recipient. Usually the NMEA devices* send a broadcast in the UDP case, i.e. the message is sent to all IP addresses in the same network. Please also note with UDP that only one process (i.e. only one app) can listen on a port for incoming connections. This means that only one app can listen to the port on a device. As a result, you will not be able to supply two apps on the same device with your NMEA data with UDP.
3. IP Address
As I said, you only need it with TCP. And that is the IP address of your NMEA device*. With many devices you can also surf to this IP address via a browser (such as Safari) for the configuration. The IP can also be changed for many manufacturers, so you have to get the IP address from the instructions if you do not know it. I have listed a few standard IP addresses / ports on this NMEA page, but as I said, these do not have to be correct because you can change them.
4. Port
The port is required for UDP and TCP, this can usually be changed and you would have to get the port from the instructions. I have listed a few standard IP addresses / ports on this NMEA page, but as I said, these don't have to be correct because they can be changed.
5. Mandatory sentences
For a permanently functioning connection, the logbook app requires either RMC or MWV data records. If you don't have either of them in your NMEA network, no connection will be recognized. Here you can find details about RMC/MWV.
6. Specials for TCP
Some NMEA devices* only allow an incoming TCP connection. For example, if you are already using another app and it already has a working connection, it is possible that no one else can establish a connection. There are different limits to the simultaneous use, some can only one, some two, some several.
7. It is still not working?
If you are not sure about the correct protocol, IP and port, then this is probably the problem. Ask your NMEA device* supplier/manufacturer for help. If you are sure you know the protocol, port and IP and it still does not work, then try to establish a connection via an app such as 'Terminus' or 'UDP Terminal' (both free in the App Store). If that doesn't work either, the protocol, port or IP is wrong. If that works, it's probably due to the data itself, so show me an excerpt of your data and drop me a message.

[*] The device that receives the NMEA data in your WiFi.

Parts of my track are shown as a dashed line on the map, why?

For performance reasons, the entire track is not shown in detail by default, as otherwise loading the track can take a long time. If you switch to the map settings (the small wrench at the top right of the map), you can configure how many entries should be displayed in detail. Only the detailed part can also be tapped, e.g. to move or open an entry. You can also set an offset, so for example out of 500 entries you want 250 to be displayed in detail and only from entry 200 (i.e. all between 200 and 450 in this case). The remainder (1 - 199 before and 451 - 500 after) is only shown as dashed line. The colored lines depend on the speed. You can also configure that in the map settings, from when the line should remain red and until when it should turn green.

Does the lack of internet connectivity affect the app in any way?

The following features may require internet: If you are off shore without internet connectivity, I highly recommend to configure the following in logbook settings, to ensure the app is completely independent to any network related services.
Geocoding
Disable geocoding entirely, if you like you can geoencode your logbook afterwards.
Location Sharing
Disable it, as it won't work anyhow without internet connectivity.
Weather services
Change it to 'off' and go to 'Select data sources' and ensure no value relies on internet. I recommend to set all values to either NMEA if you can, or to 'previous record'. As the name 'Previous record' says, it will always prefill the value from the previous record, so you just need to keep the latest record up to date with the real weather situation.

After opening the app all my records are gone!

There are more possible reasons.
There is just a temporary problem!
In very rare cases the user interface does not connect to the database. In this case just kill the app (by swiping it up in app switcher) and restart it.
Wrong logbook selected!
First it could be you just selected the wrong Logbook in settings. To check this, just go into the apps settings, scroll to Logbooks, and select the right one.
Local database vs. iCloud database!
You can either use the local database or the database in iCloud, so the records you are after could be in the other database. More details are described in the iCloud Sync page.
Data recorded while iCloud sync was active!
Up to version 2.50 it was possible to use the iCloud Sync in the background. This led to data loss for some users (including myself) starting in summer 2021. You can find more details on the iCloud Sync detail page.
Your database did not finish migration succesfully!
If you are affected by this issue, you still see all your logbooks but none of them has records in it. In this case connect your iPhone or iPad to your computer to access the local apps data folder with Finder (macOS) or iTunes (Windows).
  1. Disable iCloud Sync. If it isn't already, this is probably not your problem, as the problem must have already occurred in the local database.
  2. Connect your iPhone/iPad to your Mac or PC
  3. Open Finder or iTunes
  4. Click on the left side on the name of your iPhone/iPad
  5. Click on top on Apps or Files
  6. Select the Logbook App
  7. Copy all files from the App to your computer as backup before your continue
  8. Verify there are three files starting with storev7.* and three files strating with storev8.*. If this is not the case, this solution is not for your problem.
  9. Kill the Logbook app (by swiping it up in app switcher)
  10. Delete all three files starting with storev8.* from your device
  11. Open the Logbook app and wait until the database migration is finished successfully, now all should be as you expected it

I am on water 24/7 for several days and noticed the app quits somehow each 24 hours?

It is really the case (I noticed this the first time with iOS12), that iOS seems to end (not kill, as there is no crashlog) all apps using location services each 24 hours. (e.g each day at 09:00). I can't avoid this behavior, but in app rlease version 2.34 I implemented the option to receive a local notification that will ring as soon as this happen, so you just have to reopen the app after this alarm sound and everything continues as expected. Details to increase reliability here.

I had a trip in a different time zone, back home all times are wrong.

Without changing individual settings all new records are created in the time zone of you iOS device. So, if you create records in a different time zone the records will be shown based on your actual time zone. To avoid this, you can either set the real time zone in advance to your trip in the logbook individual settings (where you also can change logbook name, crew etc.). As this will create all new records in the selected time zone. Afterwards you have the possibility to scroll down to the very first record in your list and adjust the time zone for it. This will change the time zone also for all other record after this one. Keep in mind new records will still be created in the time zone you selected in the logbook settings. It is highly recommended you do a backup of your database before trying to fix wrong time zones in a valuable logbook.

What will happen to logbook records when I cross time zones?

Each record has its own timezone specified, so when you pknow you will pass timezones, do the following to define the timezone for all new record. Go to settings - logbook - (i) - change the timezone to your current timezone. Now all new records will be created in this timezone. This will not affect existing records, just new ones. Once you cross to another timezone, go again to the logbook settings and adjust it to the next timezone, and so on...
It is also easy to adjust timezones afterwards, go from the bottom to the top, as changing the timezone of a specific record will always adjust the timezone of all records after it as well.

How to backup, restore or copy the Logbook App database to another device?

If you are not interested in a backup but only in synchronizing the data on another device, you can synchronize this via iCloud. However, there are a few important things to consider in this case in order to avoid data loss! The details are described on the iCloud Sync page. The other option is to create a backup of the database (which is generally recommended after every major voyage!) And then import it into another device. This is also a possibility to share a logbook among several people if the storage space is accessible to everyone.
Backup
If you would like to backup your Logbook database , just go to Tools, Export and send the SQLite file via Email to yourself, save it to iCloud, or something similar. The database inlcudes all your logbooks, records, maneuver-, packing-, safety-lists.
Restore your backup
Just open the file (e.g. from your email) and store it in Files app (iCloud Drive or local). Afterwards open it in Files app and share it (square button with arrow upwards) with Logbook app. If you do not see Logbook app in the share dialog, scroll to the right and tap on 'More' to find Logbook app. Afterward Logbook app opens and you will be asked if you really would like to replace the existing database. Be careful you will lose all data in the target app, and this cannot made undone. Note 1: You have to select the correct logbook in the apps settings afterwards! Note 2: If all available logbooks are named (null), kill the app and open it again
Copy database from iPhone to iPad or vice versa
First do the export as described above, then copy the database directly via AirDrop to the other device, open it there with Logbook App. Alternatively to AirDrop it works also with Mail, Dropbox, Owncloud or Files. However it necessary for import to copy the file to Files app as described above.

What is the difference between Vmax Log and Vmax Track?

Difference between VMax Log and Track
In each record the SOG is saved, it represents the current speed at that time when the record was created. From all those values, the line Vmax Log is drawn.
In return Vmax Track is the speed calculated between two records, based on the distance divided by the time difference of those two records.

How are engine operating hours calculated?

It is described in the explanation for engines and bullet point 13 in statistics.

I would like to post my Logbook to Facebook, is this possible?

Yes, you can post your Logbook from your iPhone or iPad directly. Please see the HOWTO post a Logbook to Facebook.

I can not open open the CSV export in Excel?

The reason is oviously the UTF-8 encoding which is not supported by all Excel versions. Here is a detailled description how to open your Sailing Logbook in Excel.