Service client – Questions et réponses sur Logbook Suite

In Logbook, the Auto NMEA func­tion records the cur­rent posi­tion every 2 minu­tes and also cal­cu­la­tes the distance tra­ve­led since the last saved posi­tion.
If the option Distance (Log) from log instru­ment is deac­ti­va­ted in the dialog Defaults, GPS/NMEA or if no log value is con­tai­ned in the NMEA data, Logbook deter­mi­nes the value for the Log field from these par­tial distances.
This value is usually much more accu­rate than the value from the ship’s log.

Incor­rect set­tings in dialog Default, GPS/NMEA can cause that no data trans­fer is pos­si­ble or that it takes a long time until the data are ente­red in Logbook.

The­r­e­fore in the dialog Default, GPS/NMEA only the opti­ons for the data that really can be recei­ved should be enab­led. Other­wise Logbook will wait for unavailable data until the timeout.

This applies par­ti­cul­lary to the option iPad Pres­sure, which should be acti­va­ted only if the iPad has an inte­gra­ted baro­me­ter. In the app LogbookNMEA con­nect, which is used for the data retrie­val, you also need to setup and acti­va­ted the source iPad baro­me­ter in addi­tion to the source for recei­ving the navi­ga­tion data.
We recom­mend to use the option Use time from iPad only if the NMEA data source of the ship net­work does not pro­vide a relia­ble UTC value.

With USB con­nec­tions, in most cases it is not pos­si­ble to acti­vate devices that are alre­ady used by a navi­ga­tion pro­gram also for Logbook, because the navi­ga­tion pro­grams occupy the port of the device per­ma­nently and do not release it for other programs.

If the Auto NMEA func­tion has not recei­ved any usable data during a data retrie­val, a red mes­sage inclu­ding an error number is dis­played.
The cause of the error is usually the GPS signal or the GPS source itself.
This means the type number of the error:

T1 = no data
T2 = Posi­tion error — devia­tion too large (the posi­tion is too far away from the pre­vious one)
T3 = no com­plete posi­tion (e.g. only LAT and no LON)

Lors de l’ou­ver­ture de Logbook, le sys­tème véri­fie si le fon­c­tion­ne­ment du moteur est défini sur « ter­miné » pour chaque jour clô­turé. Si ce n’est pas le cas, un mes­sage d’err­eur s’af­fi­che.
Pour une éva­lua­tion cor­recte, tu dev­rais véri­fier et cor­ri­ger les entrées des jours listés.

Pro­cède comme suit pour com­plé­ter l’en­trée manquante :

1. Passe à la pre­mière date men­ti­onnée dans le mes­sage d’erreur.
2. Active la carte Navi­ga­tion.
3. Ouvre la boîte de dia­lo­gue Saisie des don­nées et passe à la der­nière entrée du jour.
4. Véri­fie si le bouton moteur du moteur con­cerné est affi­ché en bleu ou en gris.

Si le bouton du moteur est affi­ché en bleu :

1. Clique sur le bouton du moteur affi­ché en bleu pour arrê­ter le fon­c­tion­ne­ment du moteur.
2. Pro­cé­dez ainsi pour tous les jours men­ti­onnés dans le mes­sage d’erreur.

Si le bouton du moteur est affi­ché en gris :

1. Note l’heure.
2. Ferme la boîte de dialogue.
3. Active main­ten­ant la carte Moteur, Moteur(s).
4. Pour le moteur en ques­tion, va dans le champ Cou­pure sous Moteur — comp­teur horaire.
5. Efface l’heure inscrite et saisis l’heure notée.
6. Le moteur ne dev­rait plus être listé à droite sous Moteur(s) allumé(s).
7. Pro­cé­dez ainsi pour tous les jours men­ti­onnés dans le mes­sage d’erreur.

Seve­ral media out­lets have recently repor­ted mas­sive GPS dis­rup­ti­ons, par­ti­cu­larly in the Baltic Sea and the eas­tern Medi­ter­ra­nean. This is pre­su­ma­bly caused by tar­ge­ted inter­fe­rence (GPS jamming) in con­nec­tion with the war in Ukraine.
If you are tra­ve­ling in this area and fre­quently receive the red error mes­sage while using the Auto NMEA, this GPS jamming may be the reason. This is because Logbook com­pa­res the posi­ti­ons with each data recor­ding and reports an Auto NMEA error if they are too far apart. Incor­rect posi­ti­ons are no longer used. <br>
If the GPS error is only tem­po­rary (as we have mostly seen with the errors repor­ted by our cus­to­mers in the past year), this also has no influence on your logbook ent­ries.
See also (unfort­u­na­tely only in German):

https://www.ndr.de/nachrichten/mecklenburg-vorpommern/Ostsee-Raetselhafte-GPS-Stoerungen-behindern-Schiffs-und-Flugverkehr,balticjammer100.html

https://skipper.adac.de/gps-stoerungen-im-ostseeraum-und-mittelmeer/

What often helps with pro­blems with the iPad is a deep restart of the device. Unfort­u­na­tely, unlike the PC, the iPad is not com­ple­tely restar­ted even when a system update is per­for­med, which means that data and set­tings accu­mu­late and can lead to problems.

1. First close all files in Logbook Suite.
2. Then close all apps by swit­ching them out of the App Switcher.
3. Restart the iPad. To do this, you have to hold down the keys men­tio­ned below until the apple appears. This can take up to 10 seconds. The pro­ce­dure is dif­fe­rent for the various models:

• iPad (newer modells): Press the Volume Up button once briefly, then press the Volume Down button once briefly, and then press and hold the Standby button.
• iPad with home button: Press and hold the home button and the standby button at the same time.
• iPad Pro (old): Hold down the side button (standby button) and the quiet button at the same time.

If you don’t know how to cate­go­rize your iPad here: just try it out, not­hing can happen. You can tell that it is working because the apple will appear at some point. Do not select the slider that may appear in between.