mirror of
https://github.com/subsurface/subsurface.git
synced 2025-02-19 22:16:15 +00:00
Documentation: update french translation of manuals
This commit is contained in:
parent
9c67016769
commit
6d679931d0
8 changed files with 3006 additions and 2698 deletions
File diff suppressed because it is too large
Load diff
File diff suppressed because it is too large
Load diff
File diff suppressed because it is too large
Load diff
File diff suppressed because it is too large
Load diff
|
@ -409,12 +409,12 @@ asciidoc.install(3);
|
|||
</div>
|
||||
<div class="paragraph"><p><span class="big">MANUEL UTILISATEUR de Subsurface-mobile</span></p></div>
|
||||
<div class="paragraph"><p><strong>Auteurs du manuel</strong> : Willem Ferguson, Dirk Hohndel</p></div>
|
||||
<div class="paragraph"><p><span class="blue"><em>Version 2, octobre 2017</em></span></p></div>
|
||||
<div class="paragraph"><p><span class="blue"><em>Version 2, décembre 2017</em></span></p></div>
|
||||
<div class="paragraph"><p>Welcome as a user of <em>Subsurface</em> and <em>Subsurface-mobile</em>, advanced dive
|
||||
logging software with extensive infrastructure to describe, organize, and
|
||||
interpret scuba and free dives. <em>Subsurface</em> offers many advantages over
|
||||
other similar software solutions, including compatibility with Windows,
|
||||
Mac-OS/X, Linux (many distributions), Android and iOS. In addition,
|
||||
macOS, Linux (many distributions), Android and iOS. In addition,
|
||||
<em>Subsurface</em> is open-source software that allows downloading dive
|
||||
information from many dive computers.</p></div>
|
||||
<div class="sect1">
|
||||
|
@ -427,10 +427,8 @@ sites de plongées où un ordinateur n’est pas utile. Alors que la version
|
|||
<em>Subsurface</em> pour ordinateur affiche bien plus d’informations détaillées
|
||||
pour chaque plongée, la version mobile permet un accès facilité lors sur un
|
||||
voyage de plongées, utile pour prouver une experience de plongées aux clubs
|
||||
ou pour revoir les plongées précédentes. <em>Subsurface-mobile</em> pour Android
|
||||
permet également de collecter des positions GPS où sont effectuées les
|
||||
plongées. (Subsurface-mobile pour iOS ne supporte pas toutes les fonctions
|
||||
pour le moment).</p></div>
|
||||
ou pour revoir les plongées précédentes. <em>Subsurface-mobile</em> permet
|
||||
également de collecter des positions GPS où sont effectuées les plongées.</p></div>
|
||||
<div class="paragraph"><p>Les utilisateurs de <em>Subsurface-mobile</em> utilisent habituellement
|
||||
l’application mobile en tant que compagnon de la version de <em>Subsurface</em>
|
||||
pour ordinateur, partageant les informations de plongées entre les versions
|
||||
|
@ -470,8 +468,7 @@ Modifier de nombreux champs des données de plongées, comme le moniteur, le
|
|||
</li>
|
||||
<li>
|
||||
<p>
|
||||
Enregistrer, stocker et appliquer des positions GPS des plongées (Uniquement
|
||||
sous Android).
|
||||
Enregistrer, stocker et appliquer des positions GPS des plongées.
|
||||
</p>
|
||||
</li>
|
||||
<li>
|
||||
|
@ -482,10 +479,13 @@ Visualiser les positions des points GPS enregistrés et des plongées sur une
|
|||
</li>
|
||||
</ul></div>
|
||||
<div class="paragraph"><p>Ces points sont détaillés dans la suite du manuel. <em>Subsurface-mobile</em> ne
|
||||
supporte pas encore le téléchargement des données de plongées depuis tous
|
||||
les ordinateurs de plongées que supporte la version de bureau. Seule une
|
||||
partie des ordinateurs de plongées utilisant une interface USB FTDI ou une
|
||||
interface Bluetooth/BTLE sont accessibles depuis <em>Subsurface-mobile</em>.</p></div>
|
||||
supporte pas le téléchargement des données de plongées depuis tous les
|
||||
ordinateurs de plongées que supporte la version de bureau. Cette limitation
|
||||
est due principalement à la capacité d’accéder à plusieurs types de
|
||||
périphériques sur deux plateformes mobiles. Une partie des ordinateurs de
|
||||
plongées utilisant une interface USB FTDI ou une interface Bluetooth /
|
||||
Bluetooth LE sont accessibles depuis <em>Subsurface-mobile</em>. Sous iOS, seul
|
||||
les ordinateurs de plongées basés sur le Bluetooth LE sont supportés.</p></div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="sect1">
|
||||
|
@ -516,18 +516,19 @@ ci-dessous, à gauche).</p></div>
|
|||
<div class="paragraph"><p>Tap the "No cloud mode" button. The app will not access the <em>Subsurface</em>
|
||||
cloud storage server to obtain dive log information. This means that dive
|
||||
log information is stored on the mobile device only. If no dives have been
|
||||
entered into the dive log yet (the usual case), then a an empty dive log is
|
||||
entered into the dive log yet (the usual case), an empty dive log is
|
||||
created.</p></div>
|
||||
</div>
|
||||
<div class="sect2">
|
||||
<h3 id="_using_cloud_storage">3.2. Using Cloud Storage</h3>
|
||||
<div class="paragraph"><p>A free Internet cloud storage account can be used for storing dive log
|
||||
information. This cloud storage account can be created either from
|
||||
<em>Subsurface</em> on the desktop or <em>Subsurface-mobile</em> using a mobile device; in
|
||||
fact, you can do full maintenance of a dive log from <em>Subsurface-mobile</em>
|
||||
alone. On the other hand, if you share credentials between
|
||||
<em>Subsurface-mobile</em> and <em>Subsurface</em> for desktop, through the <em>Subsurface</em>
|
||||
cloud storage your dive log can be shared by both devices.</p></div>
|
||||
<div class="paragraph"><p>The <em>Subsurface</em> developers provide a custom free Internet cloud storage
|
||||
account that can be used for storing dive log information. This cloud
|
||||
storage account can be created either from <em>Subsurface</em> on the desktop or
|
||||
<em>Subsurface-mobile</em> using a mobile device; you can do full maintenance of a
|
||||
dive log from <em>Subsurface-mobile</em> alone. By using the same credentials wirh
|
||||
<em>Subsurface-mobile</em> and <em>Subsurface</em> for desktop, the <em>Subsurface</em> cloud
|
||||
storage allows you to share your dive log between both (or even more than
|
||||
two) devices.</p></div>
|
||||
<div class="paragraph"><p>The dive data are cached both on the mobile device as well as on the desktop
|
||||
- it is easy to create backups of the data (for example in XML format) on
|
||||
the desktop, and both mobile device and desktop keep a local copy of the
|
||||
|
@ -618,8 +619,7 @@ Drag the action button visible on most screens to the right
|
|||
system. On the left is the main menu, activated as described above. On the
|
||||
right of the image are the items of all the submenus accessible.</p></div>
|
||||
<div class="paragraph"><p>All screenshots in this user manual are currently from the Android
|
||||
version. As indicated earlier, the iOS version currently doesn’t support
|
||||
<em>GPS</em> features.</p></div>
|
||||
version. The iOS screens look fairly similar.</p></div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="sect1">
|
||||
|
@ -629,11 +629,12 @@ version. As indicated earlier, the iOS version currently doesn’t support
|
|||
dive list. While the dive list is loading from the cloud, a message appears
|
||||
at the bottom of the screen, indicating that the cloud is being accessed,
|
||||
after which the dive list is shown. Once the list is loaded you can scroll
|
||||
up and down. To upload dives from a dive computer, tap the blue action
|
||||
button. If you wish to add a dive manually, tap the + button in the action
|
||||
bar (described below). Tapping an existing dive on the list brings up a
|
||||
display of <em>Details View</em> for that dive (see image on right below). This
|
||||
includes the dive profile as well as additional information and notes.</p></div>
|
||||
up and down through your dive history. To upload dives from a dive
|
||||
computer, tap the blue action button. If you wish to add a dive manually,
|
||||
tap the + button in the action bar (described below). Tapping an existing
|
||||
dive on the list brings up a display of <em>Details View</em> for that dive (see
|
||||
image on right below). This includes the dive profile as well as additional
|
||||
information and notes.</p></div>
|
||||
<div class="imageblock" style="text-align:center;">
|
||||
<div class="content">
|
||||
<img src="mobile-images/Divelist2.jpg" alt="FIGURE: Dive list screen" />
|
||||
|
@ -657,7 +658,8 @@ of the information (see image below). It may be necessary to scroll the
|
|||
window to access all the information. At the bottom of the edit screen is a
|
||||
<em>Save</em> action button. Tap this to save the new information, after which the
|
||||
dive list screen is updated and shown. To cancel any edits, tap the Android
|
||||
<em>Back</em> Button.</p></div>
|
||||
<em>Back</em> Button or the application back button at the top left of the screen
|
||||
on iOS.</p></div>
|
||||
<div class="paragraph"><p>When the virtual keyboard is shown, to avoid screen clutter, the action
|
||||
button is hidden. Once you close the keyboard it is drawn again.</p></div>
|
||||
<div class="imageblock" style="text-align:center;">
|
||||
|
@ -716,9 +718,21 @@ the dive.</p></div>
|
|||
<div class="sect1">
|
||||
<h2 id="S_Download">9. Download dives from a dive computer</h2>
|
||||
<div class="sectionbody">
|
||||
<div class="paragraph"><p>Download of dives is possible from dive computers with a FTDI USB interface,
|
||||
or with a Bluetooth/BTLE interface.</p></div>
|
||||
<div class="paragraph"><p>First, establish a link between the dive computer and the mobile device.</p></div>
|
||||
<div class="paragraph"><p>The download deature supports only a limited number of dive computers. On
|
||||
Android devices these are typically dive computers using an FTDI interface
|
||||
using a USB OTG cable (but this is blocked on some Android devices by OS
|
||||
settings). Android devices also support all Bluetooth dive computers that
|
||||
are supported in Subsurface. And both Android and iOS devices allow direct
|
||||
download of dive data from a hand full of Bluetooth LE enabled dive
|
||||
computers.</p></div>
|
||||
<div class="paragraph"><p>The process for download is slightly different between the two OSs. In our
|
||||
testing we got the best results on iOS when the dive computer was in
|
||||
Bluetooth mode before <em>Subsurface-mobile</em> is started. On most dive computers
|
||||
this is done through a menu entry, others (like the Suunto models) always
|
||||
respond to BLE requests.</p></div>
|
||||
<div class="paragraph"><p>On Android devices, you should first establish a link between the Bluetooth
|
||||
or Bluetooth LE dive computer and the mobile device using Android
|
||||
utilities. See below for more details.</p></div>
|
||||
<div class="paragraph"><p>For USB dive computers, USB cables "normally" used for uploading dives to a
|
||||
desktop/laptop computer do NOT work: these cables usually have a full-sized
|
||||
("Type A") male USB plug on one end which plugs into the USB port of a
|
||||
|
@ -738,15 +752,15 @@ still in some cases cannot access a dive computer through a serial port.</p></di
|
|||
<img src="mobile-images/USB-OTG.jpg" alt="FIGURE: USB-OTG cable" />
|
||||
</div>
|
||||
</div>
|
||||
<div class="paragraph"><p>For Bluetooth-equipped dive computers, establish a Bluetooth connection
|
||||
between the dive computer and the mobile device. Use the tools on the mobile
|
||||
device to achieve pairing between the Bluetooth dice computer and the mobile
|
||||
device. For of Android devices, the Settings → Bluetooth tool is probably
|
||||
appropriate. Ensure pairing of the dive computer and mobile device.
|
||||
<em>Subsurface-mobile</em> performs communication using both Bluetooth and
|
||||
Bluetooth-low-energy (BTLE). The appropriate choice of Bluetooth
|
||||
communication is made by the software and the user need not be concerned
|
||||
with this.</p></div>
|
||||
<div class="paragraph"><p>For Bluetooth-equipped dive computers and Android devices, establish a
|
||||
Bluetooth connection between the dive computer and the mobile device. Use
|
||||
the tools on the mobile device to achieve pairing between the Bluetooth dice
|
||||
computer and the mobile device. For of Android devices, the Settings →
|
||||
Bluetooth tool is probably appropriate. Ensure pairing of the dive computer
|
||||
and mobile device. <em>Subsurface-mobile</em> performs communication using both
|
||||
Bluetooth and Bluetooth-low-energy (BTLE). The appropriate choice of
|
||||
Bluetooth communication is made by the software and the user need not be
|
||||
concerned with this.</p></div>
|
||||
<div class="paragraph"><p>With pairing between dive computer and <em>Subsurface-mobile</em> having been set
|
||||
up, dive download is simple. From the main menu, tap <em>Manage dives →
|
||||
Download from DC</em>. A screen is shown requiring that the user specify the
|
||||
|
@ -779,11 +793,11 @@ the section above <a href="#S_Edit_Dive">Edit a dive</a>.</p></div>
|
|||
<div class="sectionbody">
|
||||
<div class="paragraph"><p>In the <em>Details View</em>, the Action Bar at the bottom has a GPS pin on the
|
||||
left hand side. Tap that pin and the dive site is shown in Google
|
||||
Maps. Close Google Maps by using the Android <em>Back</em> button.</p></div>
|
||||
Maps. Close Google Maps by using the Android <em>Back</em> button or tapping on the
|
||||
<em>Subsurface-mobile</em> link in the top left corner on iOS.</p></div>
|
||||
<div class="paragraph"><p>Alternatively, the <em>Details View</em> has a button at the top right hand marked
|
||||
<em>Map it</em>. Tap this button to open Google Maps showing the dive site (image
|
||||
below). Afterwards, use the Android <em>Back</em> button to return to
|
||||
<em>Subsurface-mobile</em>.</p></div>
|
||||
below).</p></div>
|
||||
<div class="imageblock" style="text-align:center;">
|
||||
<div class="content">
|
||||
<img src="mobile-images/Map.jpg" alt="FIGURE: Map of dive site" />
|
||||
|
@ -839,21 +853,21 @@ activated or to be switched off.</p></div>
|
|||
</div>
|
||||
</div>
|
||||
<div class="sect1">
|
||||
<h2 id="_recording_dive_locations_using_gps_android_only">12. Recording dive locations using GPS (Android only).</h2>
|
||||
<h2 id="_recording_dive_locations_using_gps">12. Recording dive locations using GPS</h2>
|
||||
<div class="sectionbody">
|
||||
<div class="paragraph"><p>The fact that most smartphones have GPS facilities allows
|
||||
<em>Subsurface-mobile</em> on Android to record the locations of dives. If the
|
||||
smartphone is taken on the dive boat during a dive, locations will be
|
||||
automatically recorded at regular intervals. These locations can then be
|
||||
applied to dives in the dive list. Here is how it’s done:</p></div>
|
||||
<em>Subsurface-mobile</em> to record the locations of dives. If the smartphone is
|
||||
taken on the dive boat during a dive, locations will be automatically
|
||||
recorded at regular intervals. These locations can then be applied to dives
|
||||
in the dive list. Here is how it’s done:</p></div>
|
||||
<div class="sect2">
|
||||
<h3 id="S_ConfigureGPS">12.1. Configuring the GPS service</h3>
|
||||
<div class="paragraph"><p>From the Main menu, select <em>Settings</em>. The Settings screen has a section for
|
||||
configuring the GPS service (image below). GPS location data are collected
|
||||
at regular intervals, e.g. every 5 minutes, or at regular distances,
|
||||
e.g. after the boat has moved more than 200m, or a combination of both of
|
||||
these approaches. Provide the appropriate information and tap the Android
|
||||
<em>Back</em> button. The program is now ready to collect GPS positions.</p></div>
|
||||
these approaches. Provide the appropriate information and tap the <em>Back</em>
|
||||
button. The program is now ready to collect GPS positions.</p></div>
|
||||
<div class="imageblock" style="text-align:center;">
|
||||
<div class="content">
|
||||
<img src="mobile-images/GPS-config.jpg" alt="FIGURE: GPS configure" />
|
||||
|
@ -862,7 +876,8 @@ these approaches. Provide the appropriate information and tap the Android
|
|||
</div>
|
||||
<div class="sect2">
|
||||
<h3 id="_collecting_gps_positions">12.2. Collecting GPS positions</h3>
|
||||
<div class="paragraph"><p>Ensure that the GPS on the Android device has been activated. Open the Main
|
||||
<div class="paragraph"><p>Ensure that the GPS on the mobile device has been activated and that you
|
||||
have given the app permission to access your location data. Open the Main
|
||||
Menu and select <em>GPS → Run location service</em>. This activates the recording
|
||||
of GPS locations.</p></div>
|
||||
<div class="imageblock" style="text-align:center;">
|
||||
|
@ -1004,7 +1019,7 @@ characteristics of the mobile device and the font characteristics used by
|
|||
<div id="footer">
|
||||
<div id="footer-text">
|
||||
Last updated
|
||||
2017-10-20 22:56:41 CEST
|
||||
2018-02-07 17:48:32 CET
|
||||
</div>
|
||||
</div>
|
||||
</body>
|
||||
|
|
|
@ -11,13 +11,13 @@ image::mobile-images/Banner.jpg["Banner", align="center"]
|
|||
*Auteurs du manuel* : Willem Ferguson, Dirk Hohndel
|
||||
|
||||
|
||||
[blue]#_Version 2, octobre 2017_#
|
||||
[blue]#_Version 2, décembre 2017_#
|
||||
|
||||
Welcome as a user of _Subsurface_ and _Subsurface-mobile_, advanced dive
|
||||
logging software with extensive infrastructure to describe, organize, and
|
||||
interpret scuba and free dives. _Subsurface_ offers many advantages over
|
||||
other similar software solutions, including compatibility with Windows,
|
||||
Mac-OS/X, Linux (many distributions), Android and iOS. In addition,
|
||||
macOS, Linux (many distributions), Android and iOS. In addition,
|
||||
_Subsurface_ is open-source software that allows downloading dive
|
||||
information from many dive computers.
|
||||
|
||||
|
@ -31,10 +31,8 @@ sites de plongées où un ordinateur n'est pas utile. Alors que la version de
|
|||
_Subsurface_ pour ordinateur affiche bien plus d'informations détaillées
|
||||
pour chaque plongée, la version mobile permet un accès facilité lors sur un
|
||||
voyage de plongées, utile pour prouver une experience de plongées aux clubs
|
||||
ou pour revoir les plongées précédentes. _Subsurface-mobile_ pour Android
|
||||
permet également de collecter des positions GPS où sont effectuées les
|
||||
plongées. (Subsurface-mobile pour iOS ne supporte pas toutes les fonctions
|
||||
pour le moment).
|
||||
ou pour revoir les plongées précédentes. _Subsurface-mobile_ permet
|
||||
également de collecter des positions GPS où sont effectuées les plongées.
|
||||
|
||||
Les utilisateurs de _Subsurface-mobile_ utilisent habituellement
|
||||
l'application mobile en tant que compagnon de la version de _Subsurface_
|
||||
|
@ -54,16 +52,18 @@ _Subsurface-mobile_ permet de :
|
|||
de plongées.
|
||||
- Modifier de nombreux champs des données de plongées, comme le moniteur, le
|
||||
binôme, l'équipement ou les notes relatives à la plongée.
|
||||
- Enregistrer, stocker et appliquer des positions GPS des plongées (Uniquement
|
||||
sous Android).
|
||||
- Enregistrer, stocker et appliquer des positions GPS des plongées.
|
||||
- Visualiser les positions des points GPS enregistrés et des plongées sur une
|
||||
carte.
|
||||
|
||||
Ces points sont détaillés dans la suite du manuel. _Subsurface-mobile_ ne
|
||||
supporte pas encore le téléchargement des données de plongées depuis tous
|
||||
les ordinateurs de plongées que supporte la version de bureau. Seule une
|
||||
partie des ordinateurs de plongées utilisant une interface USB FTDI ou une
|
||||
interface Bluetooth/BTLE sont accessibles depuis _Subsurface-mobile_.
|
||||
supporte pas le téléchargement des données de plongées depuis tous les
|
||||
ordinateurs de plongées que supporte la version de bureau. Cette limitation
|
||||
est due principalement à la capacité d'accéder à plusieurs types de
|
||||
périphériques sur deux plateformes mobiles. Une partie des ordinateurs de
|
||||
plongées utilisant une interface USB FTDI ou une interface Bluetooth /
|
||||
Bluetooth LE sont accessibles depuis _Subsurface-mobile_. Sous iOS, seul
|
||||
les ordinateurs de plongées basés sur le Bluetooth LE sont supportés.
|
||||
|
||||
== Installer _Subsurface-mobile_ sur votre périphérique nomade
|
||||
|
||||
|
@ -87,17 +87,18 @@ image::mobile-images/Credentials.jpg["FIGURE: Mobile credentials screen", align=
|
|||
Tap the "No cloud mode" button. The app will not access the _Subsurface_
|
||||
cloud storage server to obtain dive log information. This means that dive
|
||||
log information is stored on the mobile device only. If no dives have been
|
||||
entered into the dive log yet (the usual case), then a an empty dive log is
|
||||
entered into the dive log yet (the usual case), an empty dive log is
|
||||
created.
|
||||
|
||||
=== Using Cloud Storage
|
||||
A free Internet cloud storage account can be used for storing dive log
|
||||
information. This cloud storage account can be created either from
|
||||
_Subsurface_ on the desktop or _Subsurface-mobile_ using a mobile device; in
|
||||
fact, you can do full maintenance of a dive log from _Subsurface-mobile_
|
||||
alone. On the other hand, if you share credentials between
|
||||
_Subsurface-mobile_ and _Subsurface_ for desktop, through the _Subsurface_
|
||||
cloud storage your dive log can be shared by both devices.
|
||||
The _Subsurface_ developers provide a custom free Internet cloud storage
|
||||
account that can be used for storing dive log information. This cloud
|
||||
storage account can be created either from _Subsurface_ on the desktop or
|
||||
_Subsurface-mobile_ using a mobile device; you can do full maintenance of a
|
||||
dive log from _Subsurface-mobile_ alone. By using the same credentials wirh
|
||||
_Subsurface-mobile_ and _Subsurface_ for desktop, the _Subsurface_ cloud
|
||||
storage allows you to share your dive log between both (or even more than
|
||||
two) devices.
|
||||
|
||||
The dive data are cached both on the mobile device as well as on the desktop
|
||||
- it is easy to create backups of the data (for example in XML format) on
|
||||
|
@ -174,8 +175,7 @@ system. On the left is the main menu, activated as described above. On the
|
|||
right of the image are the items of all the submenus accessible.
|
||||
|
||||
All screenshots in this user manual are currently from the Android
|
||||
version. As indicated earlier, the iOS version currently doesn't support
|
||||
_GPS_ features.
|
||||
version. The iOS screens look fairly similar.
|
||||
|
||||
== The Dive List
|
||||
|
||||
|
@ -183,11 +183,12 @@ Most of the actions of _Subsurface-mobile_ center around the dives on the
|
|||
dive list. While the dive list is loading from the cloud, a message appears
|
||||
at the bottom of the screen, indicating that the cloud is being accessed,
|
||||
after which the dive list is shown. Once the list is loaded you can scroll
|
||||
up and down. To upload dives from a dive computer, tap the blue action
|
||||
button. If you wish to add a dive manually, tap the + button in the action
|
||||
bar (described below). Tapping an existing dive on the list brings up a
|
||||
display of _Details View_ for that dive (see image on right below). This
|
||||
includes the dive profile as well as additional information and notes.
|
||||
up and down through your dive history. To upload dives from a dive
|
||||
computer, tap the blue action button. If you wish to add a dive manually,
|
||||
tap the + button in the action bar (described below). Tapping an existing
|
||||
dive on the list brings up a display of _Details View_ for that dive (see
|
||||
image on right below). This includes the dive profile as well as additional
|
||||
information and notes.
|
||||
|
||||
image::mobile-images/Divelist2.jpg["FIGURE: Dive list screen", align="center"]
|
||||
|
||||
|
@ -208,7 +209,8 @@ of the information (see image below). It may be necessary to scroll the
|
|||
window to access all the information. At the bottom of the edit screen is a
|
||||
_Save_ action button. Tap this to save the new information, after which the
|
||||
dive list screen is updated and shown. To cancel any edits, tap the Android
|
||||
_Back_ Button.
|
||||
_Back_ Button or the application back button at the top left of the screen
|
||||
on iOS.
|
||||
|
||||
When the virtual keyboard is shown, to avoid screen clutter, the action
|
||||
button is hidden. Once you close the keyboard it is drawn again.
|
||||
|
@ -253,10 +255,23 @@ image::mobile-images/RedDustbin.jpg["FIGURE: delete dive from list", align="cent
|
|||
[[S_Download]]
|
||||
== Download dives from a dive computer
|
||||
|
||||
Download of dives is possible from dive computers with a FTDI USB interface,
|
||||
or with a Bluetooth/BTLE interface.
|
||||
The download deature supports only a limited number of dive computers. On
|
||||
Android devices these are typically dive computers using an FTDI interface
|
||||
using a USB OTG cable (but this is blocked on some Android devices by OS
|
||||
settings). Android devices also support all Bluetooth dive computers that
|
||||
are supported in Subsurface. And both Android and iOS devices allow direct
|
||||
download of dive data from a hand full of Bluetooth LE enabled dive
|
||||
computers.
|
||||
|
||||
First, establish a link between the dive computer and the mobile device.
|
||||
The process for download is slightly different between the two OSs. In our
|
||||
testing we got the best results on iOS when the dive computer was in
|
||||
Bluetooth mode before _Subsurface-mobile_ is started. On most dive computers
|
||||
this is done through a menu entry, others (like the Suunto models) always
|
||||
respond to BLE requests.
|
||||
|
||||
On Android devices, you should first establish a link between the Bluetooth
|
||||
or Bluetooth LE dive computer and the mobile device using Android
|
||||
utilities. See below for more details.
|
||||
|
||||
For USB dive computers, USB cables "normally" used for uploading dives to a
|
||||
desktop/laptop computer do NOT work: these cables usually have a full-sized
|
||||
|
@ -276,15 +291,15 @@ still in some cases cannot access a dive computer through a serial port.
|
|||
|
||||
image::mobile-images/USB-OTG.jpg["FIGURE: USB-OTG cable", align="center"]
|
||||
|
||||
For Bluetooth-equipped dive computers, establish a Bluetooth connection
|
||||
between the dive computer and the mobile device. Use the tools on the mobile
|
||||
device to achieve pairing between the Bluetooth dice computer and the mobile
|
||||
device. For of Android devices, the Settings -> Bluetooth tool is probably
|
||||
appropriate. Ensure pairing of the dive computer and mobile device.
|
||||
_Subsurface-mobile_ performs communication using both Bluetooth and
|
||||
Bluetooth-low-energy (BTLE). The appropriate choice of Bluetooth
|
||||
communication is made by the software and the user need not be concerned
|
||||
with this.
|
||||
For Bluetooth-equipped dive computers and Android devices, establish a
|
||||
Bluetooth connection between the dive computer and the mobile device. Use
|
||||
the tools on the mobile device to achieve pairing between the Bluetooth dice
|
||||
computer and the mobile device. For of Android devices, the Settings ->
|
||||
Bluetooth tool is probably appropriate. Ensure pairing of the dive computer
|
||||
and mobile device. _Subsurface-mobile_ performs communication using both
|
||||
Bluetooth and Bluetooth-low-energy (BTLE). The appropriate choice of
|
||||
Bluetooth communication is made by the software and the user need not be
|
||||
concerned with this.
|
||||
|
||||
With pairing between dive computer and _Subsurface-mobile_ having been set
|
||||
up, dive download is simple. From the main menu, tap _Manage dives ->
|
||||
|
@ -315,12 +330,12 @@ image::mobile-images/DC-Download.jpg["FIGURE: DC download screen", align="center
|
|||
|
||||
In the _Details View_, the Action Bar at the bottom has a GPS pin on the
|
||||
left hand side. Tap that pin and the dive site is shown in Google
|
||||
Maps. Close Google Maps by using the Android _Back_ button.
|
||||
Maps. Close Google Maps by using the Android _Back_ button or tapping on the
|
||||
_Subsurface-mobile_ link in the top left corner on iOS.
|
||||
|
||||
Alternatively, the _Details View_ has a button at the top right hand marked
|
||||
_Map it_. Tap this button to open Google Maps showing the dive site (image
|
||||
below). Afterwards, use the Android _Back_ button to return to
|
||||
_Subsurface-mobile_.
|
||||
below).
|
||||
|
||||
image::mobile-images/Map.jpg["FIGURE: Map of dive site", align="center"]
|
||||
|
||||
|
@ -369,13 +384,13 @@ synchronized with the copy in the cloud every time that _Subsurface-mobile_
|
|||
is closed. This option is a switch that allows auto sync to be either
|
||||
activated or to be switched off.
|
||||
|
||||
== Recording dive locations using GPS (Android only).
|
||||
== Recording dive locations using GPS
|
||||
|
||||
The fact that most smartphones have GPS facilities allows
|
||||
_Subsurface-mobile_ on Android to record the locations of dives. If the
|
||||
smartphone is taken on the dive boat during a dive, locations will be
|
||||
automatically recorded at regular intervals. These locations can then be
|
||||
applied to dives in the dive list. Here is how it's done:
|
||||
_Subsurface-mobile_ to record the locations of dives. If the smartphone is
|
||||
taken on the dive boat during a dive, locations will be automatically
|
||||
recorded at regular intervals. These locations can then be applied to dives
|
||||
in the dive list. Here is how it's done:
|
||||
|
||||
[[S_ConfigureGPS]]
|
||||
=== Configuring the GPS service
|
||||
|
@ -384,14 +399,15 @@ From the Main menu, select _Settings_. The Settings screen has a section for
|
|||
configuring the GPS service (image below). GPS location data are collected
|
||||
at regular intervals, e.g. every 5 minutes, or at regular distances,
|
||||
e.g. after the boat has moved more than 200m, or a combination of both of
|
||||
these approaches. Provide the appropriate information and tap the Android
|
||||
_Back_ button. The program is now ready to collect GPS positions.
|
||||
these approaches. Provide the appropriate information and tap the _Back_
|
||||
button. The program is now ready to collect GPS positions.
|
||||
|
||||
image::mobile-images/GPS-config.jpg["FIGURE: GPS configure", align="center"]
|
||||
|
||||
=== Collecting GPS positions
|
||||
|
||||
Ensure that the GPS on the Android device has been activated. Open the Main
|
||||
Ensure that the GPS on the mobile device has been activated and that you
|
||||
have given the app permission to access your location data. Open the Main
|
||||
Menu and select _GPS -> Run location service_. This activates the recording
|
||||
of GPS locations.
|
||||
|
||||
|
|
|
@ -2829,12 +2829,13 @@ tab of the <em>Notes</em> panel. Photos taken in rapid succession during a dive
|
|||
(therefore sometimes with large overlap on the dive profile) can easily be
|
||||
accessed in the <em>Photos</em> tab. This tab serves as a tool for individually
|
||||
accessing the photos of a dive, while the stubs on the dive profile show
|
||||
when during a dive a photo was taken. Single-click a thumbnail in the
|
||||
<em>Photos</em> panel to select a photo. Double-click a thumbnail to view the
|
||||
full-sized image, overlaying the <em>Subsurface</em> window. Deleted a photo from
|
||||
the <em>Photos</em> panel by selecting it (single-click) and then by pressing the
|
||||
<em>Del</em> key on the keyboard. This removes the photo BOTH from the <em>Photos</em> tab
|
||||
as well as the dive profile.</p></div>
|
||||
when during a dive a photo was taken. The size of the thumbnails in the
|
||||
<em>Photos</em> tab can be changed using the <em>Zoom level</em> slider at the bottom of
|
||||
the panel. Single-click a thumbnail in the <em>Photos</em> panel to select a
|
||||
photo. Double-click a thumbnail to view the full-sized image, overlaying the
|
||||
<em>Subsurface</em> window. Delete a photo from the <em>Photos</em> panel by selecting it
|
||||
(single-click) and then by pressing the <em>Del</em> key on the keyboard. This
|
||||
removes the photo BOTH from the <em>Photos</em> tab as well as the dive profile.</p></div>
|
||||
</div>
|
||||
<div class="sect3">
|
||||
<h4 id="_photos_stockées_sur_un_disque_dur_externe">5.5.4. Photos stockées sur un disque dur externe</h4>
|
||||
|
@ -2859,7 +2860,7 @@ which dives have associated photos and which not: activate the <em>Photos</em>
|
|||
checkbox in the dropdown list obtained by right-clicking on the header bar
|
||||
of the <strong>Divelist</strong>. In the <strong>Divelist</strong>, all dives with associated photographs
|
||||
have an icon indicating whether the photographs were taken during the dive,
|
||||
just before/after the dive or both during and before/after the dive. More
|
||||
just before/after the dive or both during and before/after the dive. More
|
||||
information is provided in the section dealing with <a href="#S_Divelist_columns">photo icons on the <strong>Divelist</strong></a>.</p></div>
|
||||
</div>
|
||||
<div class="sect3">
|
||||
|
@ -2964,8 +2965,8 @@ only two types of information that need to be provided:</p></div>
|
|||
in time on the <strong>Dive Profile</strong> panel and indicating the cylinder to which the change was made. After
|
||||
right-clicking, follow the context menu to "Add gas change" and select the appropriate cylinder from
|
||||
those defined during the first step, above (see image below). If the
|
||||
<strong>tank bar</strong> button in the toolbar has been activated, the cylinder switches are also indicated in the
|
||||
tank bar (image below).
|
||||
<strong>gas bar</strong> button in the toolbar has been activated, the cylinder switches are also indicated in the
|
||||
gas bar (image below).
|
||||
</p>
|
||||
</li>
|
||||
</ul></div>
|
||||
|
@ -3034,8 +3035,8 @@ three steps, exactly as with multi-cylinder dives above:</p></div>
|
|||
selecting <em>Add gas change</em>. A list of the appropriate cylinders is shown with the
|
||||
currently used cylinder greyed out. In the image below Tank 1 is greyed out, leaving only Tank 2
|
||||
to be selected. Select the appropriate cylinder. The cylinder change is then shown on the dive
|
||||
profile with a cylinder symbol. If the <strong>Tank Bar</strong> is activated using the toolbar to the left of the
|
||||
profile, then the cylinder change is also shown on the Tank Bar (see image below). After all
|
||||
profile with a cylinder symbol. If the <strong>gas bar</strong> is activated using the toolbar to the left of the
|
||||
profile, then the cylinder change is also shown on the gas bar (see image below). After all
|
||||
the cylinder change events have been recorded on the dive profile, the correct cylinder pressures
|
||||
for both cylinders are shown on the dive profile, as in the image below.
|
||||
</p>
|
||||
|
@ -5442,21 +5443,35 @@ The most efficient way to create a dive profile is to enter the appropriate
|
|||
</ul></div>
|
||||
<div class="sect3">
|
||||
<h4 id="_plongées_loisir">14.2.1. Plongées loisir</h4>
|
||||
<div class="paragraph"><p>Recreational mode is what comes closest to planning a dive based on the non-decompression limit (NDL).
|
||||
It computes the maximum time a diver can stay at the current depth without needing mandatory decompression
|
||||
stops and without using more than the existing gas (minus a reserve). The planner automatically takes
|
||||
into account the nitrogen load incurred in previous dives. But conventional dive tables are also used in a
|
||||
way that can take into account previous dives. Why use a dive planner for recreational dives? Using
|
||||
recreational dive tables, the maximum depth of a dive is taken into account. But few dives are
|
||||
done at a constant depth corresponding to the maximum depth (i.e. a "square" dive profile). This means
|
||||
dive tables overestimate the nitrogen load incurred during previous dives. The <em>Subsurface</em>
|
||||
dive planner calculates nitrogen load according to the real dive profiles of all uploaded previous dives,
|
||||
in a similar way as dive computers calculate nitrogen load during a dive. This means that the diver gets <em>credit,</em>
|
||||
in terms of nitrogen load, for not remaining at maximum depth during
|
||||
previous dives, so a longer subsequent dive can be planned.
|
||||
For the planner to work it’s crucial to upload all previous dives
|
||||
onto <em>Subsurface</em> before doing dive planning.
|
||||
To plan a dive, the appropriate settings need to be defined.</p></div>
|
||||
<div class="paragraph"><p>Recreational mode is intended for what most divers would call
|
||||
"recreational", "sports"or "nontechnical" dives, remaining within no-deco
|
||||
limits (NDL). It computes the maximum time a diver can stay at the current
|
||||
depth without needing mandatory decompression stops and without using more
|
||||
than the existing gas (minus a reserve). The planner automatically takes
|
||||
into account the nitrogen load incurred in previous dives. But conventional
|
||||
dive tables are also used in a way that can take into account previous
|
||||
dives. Why use a dive planner for recreational dives? The subsurface dive
|
||||
planner provides two significant advantages over the use of recreational
|
||||
dive tables for dive planning.</p></div>
|
||||
<div class="paragraph"><p>Firstly, using recreational dive tables, the maximum depth of each previous
|
||||
dive is taken into account. But few dives are done at a constant depth
|
||||
corresponding to the maximum depth (i.e. a "square" dive profile). This
|
||||
means dive tables overestimate the nitrogen load incurred during previous
|
||||
dives. The <em>Subsurface</em> dive planner calculates nitrogen load according to
|
||||
the real dive profiles of all uploaded previous dives, in a similar way as
|
||||
dive computers calculate nitrogen load during a dive. This means that the
|
||||
diver gets <em>credit,</em> in terms of nitrogen load, for not remaining at maximum
|
||||
depth during previous dives, so a longer subsequent dive can be planned.
|
||||
For the planner to work it’s therefore crucial to log previous dives in
|
||||
<em>Subsurface</em> before doing dive planning.</p></div>
|
||||
<div class="paragraph"><p>Secondly, recreational dive tables are not designed to build additional
|
||||
safety features into a dive. NDL times derived from dive tables often take
|
||||
divers close to the limit where decompression sickness (DCS) can arise. The
|
||||
Subsurface dive planner allows a diver to build more safety features into a
|
||||
dive plan, preventing recreational divers from getting close to the limits
|
||||
of getting a DCS hit. This is performed by specifying appropriate gradient
|
||||
factors for a dive plan, as explained below.</p></div>
|
||||
<div class="paragraph"><p>To plan a dive, the appropriate settings need to be defined.</p></div>
|
||||
<div class="paragraph"><p>Ensure the date and time is set to that of the intended dive. This allows
|
||||
calculation of the nitrogen load incurred during previous dives.</p></div>
|
||||
<div class="ulist"><ul>
|
||||
|
@ -5492,10 +5507,7 @@ Define the amount of gas the cylinder must have at the end of the bottom
|
|||
most agencies assume a fixed amount of gas, or actually of pressure e.g. 40
|
||||
or 50 bar or 25% or 33% (rule of thirds). But <em>Subsurface</em> can do better
|
||||
because it knows about the ascent and that is why we add the amount of gas
|
||||
during the ascent (i.e. the "deco gas“). Subsurface still uses a fixed
|
||||
pressure "reserve" but that’s supposed to be for the additional gas used
|
||||
when there’s a problem and your pulse rate goes up when you start to buddy
|
||||
breathe. This reserve amount is user configurable.
|
||||
during the ascent.
|
||||
</p>
|
||||
</li>
|
||||
<li>
|
||||
|
@ -5517,24 +5529,49 @@ La vitesse de remontée peut être modifiée. Les vitesses de remontée par
|
|||
loisir.
|
||||
</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>
|
||||
To build additional safety into the dive plan (over and above those of
|
||||
recreational dive tables), specify gradient factors less than 100% (<em>GFHigh</em>
|
||||
and <em>GFLow</em> under the <em>Planning</em> heading in the planner). On the other hand,
|
||||
to approximate the values in recreational dive tables, set the gradient
|
||||
factors to 100. By reducing the values of GFHigh and GFLow to values below
|
||||
100, one can build more safety into a dive. Decreasing the values of the
|
||||
gradient factors below 100 will shorten the duration of the dive. This is
|
||||
the price of a larger safety margin. Reasons for using gradient factors less
|
||||
than 100 may be the age of the diver, the health of a diver, or unusual
|
||||
conditions such as cold water or strong currents. Realistic conservative
|
||||
values for the gradient factors are GFLow=40% and GFHigh=80%. This allows
|
||||
you to create a cusom dive plan, suited to yourself as well as the dive
|
||||
conditions.
|
||||
</p>
|
||||
</li>
|
||||
</ul></div>
|
||||
<div class="paragraph"><p>Below is an image of a dive plan for a recreational dive at 30 meters with
|
||||
gradient factors of 100. Because the no-deco limit (NDL) is 22 minutes,
|
||||
there remains a significant amount of air in the cylinder at the end of the
|
||||
dive.</p></div>
|
||||
<div class="imageblock" style="text-align:center;">
|
||||
<div class="content">
|
||||
<img src="images/Planner_OC_rec1.jpg" alt="FIGURE: A recreational dive plan: setup" />
|
||||
</div>
|
||||
</div>
|
||||
<div class="paragraph"><p>The dive profile in the planner shows the maximum dive time within no-deco
|
||||
limits using the Bühlmann ZH-L16 algorithm and the gas and depth settings
|
||||
specified as described above. The <em>Subsurface</em> planner allows rapid
|
||||
assessment of dive duration as a function of dive depth, given the nitrogen
|
||||
load incurred during previous dives. The dive plan includes estimates of the
|
||||
amount of air/gas used, depending on the cylinder settings specified under
|
||||
<em>Available gases</em>. If the initial cylinder pressure is set to 0, the dive
|
||||
<em>Available gases</em>. If the start cylinder pressure is left blank, the dive
|
||||
duration shown is the true no-deco limit (NDL) without taking into account
|
||||
gas used during the dive. If the surface above the dive profile is RED it
|
||||
means that recreational dive limits are exceeded and either the dive
|
||||
duration or the dive depth needs to be reduced.</p></div>
|
||||
<div class="paragraph"><p>Below is an image of a dive plan for a recreational dive at 30
|
||||
meters. Although the no-deco limit (NDL) is 23 minutes, the duration of the
|
||||
dive is limited by the amount of air in the cylinder.</p></div>
|
||||
<div class="paragraph"><p>Below is the same dive plan as above, but with a safety stop and reduced
|
||||
gradient factors for a larger safety margin.</p></div>
|
||||
<div class="imageblock" style="text-align:center;">
|
||||
<div class="content">
|
||||
<img src="images/Planner_OC_rec.jpg" alt="FIGURE: A recreational dive plan: setup" />
|
||||
<img src="images/Planner_OC_rec2.jpg" alt="FIGURE: A recreational dive plan: gradient factors setup" />
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
@ -5551,8 +5588,14 @@ panel of <em>Subsurface</em> is used. If these are changed within the planner (s
|
|||
the planner), the new values are
|
||||
used without changing the original values in the <em>Preferences</em>.
|
||||
Gradient Factor settings strongly affect the calculated ceilings and their depths.
|
||||
A very low GFLow value brings on decompression stops early during the dive.
|
||||
** For more information about Gradient factors, see the section on <a href="#S_GradientFactors">Gradient Factor Preference settings</a>.</p></div>
|
||||
A very low GFLow value brings on decompression stops early during the dive.</p></div>
|
||||
<div class="ulist"><ul>
|
||||
<li>
|
||||
<p>
|
||||
For more information about Gradient factors, see the section on <a href="#S_GradientFactors">Gradient Factor Preference settings</a>.
|
||||
</p>
|
||||
</li>
|
||||
</ul></div>
|
||||
<div class="paragraph"><p>If the VPM-B model is selected, the Conservatism_level needs to be specified
|
||||
on a scale of 0 (least conservative) to 4 (most conservative). This model
|
||||
tends to give deco stops at deeper levels than the Bühlmann model and often
|
||||
|
@ -5702,82 +5745,61 @@ utilisant du EAN50 et utilisant les réglages décrits ci-dessous.</p></div>
|
|||
towards the top middle of the planner. The saved dive plan will appear in
|
||||
the <strong>Dive List</strong> panel of <em>Subsurface</em>.</p></div>
|
||||
<div class="paragraph"><p><strong>Les détails du plan de plongée</strong></p></div>
|
||||
<div class="paragraph"><p>On the bottom right of the dive planner, under <em>Dive Plan Details</em>, the
|
||||
details of the dive plan are provided. These may be modified by checking any
|
||||
of the options under the <em>Notes</em> section of the dive planner, immediately to
|
||||
the left of the <em>Dive Plan Details</em>. If a <em>Verbatim dive plan</em> is requested,
|
||||
a detailed sentence-level explanation of the dive plan is given. If any of
|
||||
the management specifications have been exceeded during the planning, a
|
||||
warning message is printed underneath the dive plan information.</p></div>
|
||||
<div class="paragraph"><p>On the bottom right panel of the dive planner, under <em>Dive Plan Details</em>,
|
||||
the details of the dive plan are provided. These may be modified by checking
|
||||
any of the options under the <em>Notes</em> section of the dive planner,
|
||||
immediately to the left of the <em>Dive Plan Details</em>. If a <em>Verbatim dive
|
||||
plan</em> is requested, a detailed sentence-level explanation of the dive plan
|
||||
is given. If any of the management specifications have been exceeded during
|
||||
the planning, a warning message is printed underneath the dive plan
|
||||
information.</p></div>
|
||||
<div class="paragraph"><p>If the option <em>Display segment duration</em> is checked, then the duration of
|
||||
each depth level is indicated in the <em>Dive Plan Details</em>. This duration
|
||||
INCLUDES the transition time to get to that level. However, if the <em>Display
|
||||
transition in deco</em> option is checked, the transitions are shown separately
|
||||
from the segment durations at a particular level.</p></div>
|
||||
<div class="paragraph"><p>The planner has a check box <em>Display plan variations</em>. By checking this box,
|
||||
the planner provides information about a dive that is a little deeper or
|
||||
slightly longer than the planned dive. This is found near the top of the
|
||||
<em>Dive plan details</em> where the dive duration is indicated. The information is
|
||||
intended to be used if it is necessary to modify the ascent "on the fly" in
|
||||
the case of unexpected deviations from the dive plan during the dive.
|
||||
Checking this option creates a lot of additional computation, to such a
|
||||
degree that the planner is slower than otherwise. The information is
|
||||
typically given as:</p></div>
|
||||
<div class="literalblock">
|
||||
<div class="content">
|
||||
<pre><code>Runtime: 53min + 0:52/m + 4:21/min</code></pre>
|
||||
</div></div>
|
||||
<div class="paragraph"><p>This indicates:</p></div>
|
||||
<div class="paragraph"><p><strong>Dive plan variations</strong>: The planner has a check box <em>Display plan variations</em>. By checking this box, the planner
|
||||
provides information about a dive that is a little deeper or slightly
|
||||
longer than the planned dive. This is found near the top of the <em>Dive plan details</em>
|
||||
where the dive duration is indicated. The information is intended to be used if it is necessary to
|
||||
modify the ascent "on the fly" in the case of unexpected deviations from the dive plan during the dive.
|
||||
For example, if it says "Runtime: 123min, Stop times + 2:49 /m + 1:30 /min" this means: if you dive deeper
|
||||
than planned, you should add almost 3 minutes per meter you go deeper to your decompression (and
|
||||
you can substract 3 minutes per meter that you stay shallower). If you overstay your bottom
|
||||
time, you need to add one and a half minutes to the stops for each minutes you overstay
|
||||
and similarly, you can shorten your deco time by one and a half minute for each minute
|
||||
you stay shorter. These variations of depth and time are based on the last manually entered segment of the
|
||||
dive (not necessarily the deepest). The additional minutes should be distributed
|
||||
over the differnent stops in a way proportional to the stop length, i.e. add more of the
|
||||
additional minutes to the longer, shallower stops. The given times refer to the
|
||||
duration of the decompression phase and do not include the extended bottom time!
|
||||
This way of altering dive plans becomes inaccurate for large deviations from the original
|
||||
plan. So it should not be trusted for more than a few minutes or meters of
|
||||
deviations from the planned bottom time. Checking this option creates a lot of additional computation,
|
||||
to such a degree that the planner is slower than otherwise.</p></div>
|
||||
<div class="paragraph"><p><strong>Minimum gas requirements</strong>: The planner also estimates the <em>minimum gas</em> pressure
|
||||
required for safe ascent after an event that causes the dive to be aborted. The
|
||||
calculation assumes that in worst case an out of gas (OoG)
|
||||
situation occurs at the end of the planned bottom time at maximum depth, requiring
|
||||
additional time at maximum depth to solve the problem and forcing
|
||||
the buddy pair the share the gas of one diver. In addition the combined SAC of both
|
||||
divers is increased by an estimated factor compared to the SAC of a single diver under normal conditions.
|
||||
The result of the minimum gas calculation for the bottom gas is printed to the planner output. There
|
||||
are two selector boxes on the left of the <em>Dive plan details</em>:</p></div>
|
||||
<div class="ulist"><ul>
|
||||
<li>
|
||||
<p>
|
||||
Calculated dive duration is 53 min.
|
||||
<em>SAC factor</em>. This is an estimate of the degree to which your SAC increases
|
||||
if a critical problem arises underwater, e.g. gas sharing or
|
||||
entanglement. Realistic values range from 3 to 5, reflecting the gas use of
|
||||
two divers sharing a single gas cylinder after an OoG situation.
|
||||
</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>
|
||||
For each extra meter in depth during the bottom phase of the dive, the
|
||||
ascent duration increases by 52 seconds.
|
||||
</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>
|
||||
For each extra minute of bottom time, the duration increases by 4 min 21
|
||||
sec. Thus, if the bottom time is two minutes longer than planned, ascent
|
||||
duration duration will be (2 * 4min 21 sec) = 8 minutes 42 sec longer and
|
||||
would probably require that each deco stop is 8:42/53:00 = around 16% longer
|
||||
than planned. These calculations are only applicable for small deviations
|
||||
from the dive plan, not for larger deviations.
|
||||
</p>
|
||||
</li>
|
||||
</ul></div>
|
||||
<div class="paragraph"><p><strong>Minimum gas requirements</strong></p></div>
|
||||
<div class="paragraph"><p>The planner also estimates the <strong>minimum gas</strong> pressure required for safe
|
||||
ascent after an event that causes the dive to be aborted. The calculation
|
||||
assumes that in worst case an out of gas (OoG) situation occurs at the end
|
||||
of the planned bottom time at maximum depth. This OoG event forces the buddy
|
||||
team the share the gas of one diver and that they require an additional
|
||||
period of time at maximum depth to solve the problem at hand. In addition
|
||||
the combined SAC of both divers is increased by an estimated factor compared
|
||||
to the SAC factor of a single diver under normal conditions. The result of
|
||||
the minimum gas calculation for the bottom gas is printed to the planner
|
||||
output. No automatic checks are performed based on this result. The feature
|
||||
only gives valid results for simple, rectangular shaped single level dive
|
||||
profiles. For multi level dives one would need to check every leg of the
|
||||
profile independently.</p></div>
|
||||
<div class="paragraph"><p>There are two selector boxes on the left of the <em>Dive plan details</em>:</p></div>
|
||||
<div class="ulist"><ul>
|
||||
<li>
|
||||
<p>
|
||||
<strong>SAC factor</strong>. This is an estimate of the degree to which your SAC increases if a critical problem arises underwater,
|
||||
e.g. gas sharing or entanglement. Realistic values range from 2 to 5, reflecting the gas use of two divers sharing
|
||||
a single gas cylinder after an OoG situation.
|
||||
</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>
|
||||
<strong>Problem solving time</strong>. This is an estimate of how long you would take to solve the problem before starting the ascent
|
||||
to terminate the dive. The default value is 2 minutes.
|
||||
<em>Problem solving time</em>. This is an estimate of how long you would take to
|
||||
solve the problem before starting the ascent to terminate the dive. The
|
||||
default value is 2 minutes.
|
||||
</p>
|
||||
</li>
|
||||
</ul></div>
|
||||
|
@ -5794,7 +5816,7 @@ plan. the minimum gas is typically given as:</p></div>
|
|||
<div class="ulist"><ul>
|
||||
<li>
|
||||
<p>
|
||||
Within parentheses, the <strong>SAC factor</strong> and <strong>Problem solving time</strong> specified.
|
||||
Within parentheses, the <em>SAC factor</em> and <em>Problem solving time</em> specified.
|
||||
</p>
|
||||
</li>
|
||||
<li>
|
||||
|
@ -5818,6 +5840,23 @@ The delta-value: number of bars of back gas available at the end of the
|
|||
</p>
|
||||
</li>
|
||||
</ul></div>
|
||||
<div class="paragraph"><p>No automatic checks are performed based on this result. The feature only
|
||||
gives valid results for simple, rectangular shaped single level dive
|
||||
profiles. For multi level dives one would need to check every leg of the
|
||||
profile independently.</p></div>
|
||||
<div class="paragraph"><p><strong>Isobaric counterdiffusion information</strong>: For gas switches during the ascent in hypoxic open-circuit trimix dives information
|
||||
about isobaric counterdiffusion (icd) is given near the bottom of the <em>Dive plan details</em>, based on the
|
||||
rule-of-fifths (i.e. during a gas change, the increase in nitrogen partial pressure should not exceed
|
||||
one fifth of the corresponding decrease in partial pressure of helium). For each gas change, two lines
|
||||
are printed, indicating the changes in gas fractions (%) and the equivalent changes in partial pressures. If the
|
||||
rule-of-fifths is not met, the relevant information is highlighted in red and a warning message appears
|
||||
at the bottom of that table. The gas change events on the dive profile also provide information on icd,
|
||||
visible at the bottom of the <em>Information box</em> when the mouse hovers on the respective gas change icon. This information
|
||||
is only shown for gas changes relevant with respect to icd. If the rule-of-fifths is not met,
|
||||
a red warning exclamation mark is shown over the gas change icon. When relevant, the <em>Information box</em> contains
|
||||
information such as: ICD ΔHe:-13% ΔN₂+3%>2.6%. This means: for this gas change, the helium
|
||||
decreased with 13% while the nitrogen increased with 3% which
|
||||
is more than the 2.6% maximum increase in nitrogen suggested by the rule-of-fifths.</p></div>
|
||||
<div class="sidebarblock">
|
||||
<div class="content">
|
||||
<div class="admonitionblock">
|
||||
|
@ -5827,9 +5866,10 @@ The delta-value: number of bars of back gas available at the end of the
|
|||
</td>
|
||||
<td class="content">The <strong>plan variations</strong> and <strong>minimum gas</strong> estimates are only guidelines for a
|
||||
diver performing dive planning, intended to enhance the safety of executing
|
||||
a particular dive plan. They are NOT precise and should NOT be relied upon
|
||||
as the only safety features in dive planning. Interpret these estimates
|
||||
within the framework of your formal training to perform dive planning.</td>
|
||||
a particular dive plan and do not replace formal contingency planning for a
|
||||
specific dive. They are NOT precise and should NOT be relied upon as the
|
||||
only safety features in dive planning. Interpret these estimates within the
|
||||
framework of your formal training to perform dive planning.</td>
|
||||
</tr></table>
|
||||
</div>
|
||||
</div></div>
|
||||
|
@ -5841,11 +5881,14 @@ within the framework of your formal training to perform dive planning.</td>
|
|||
<em>Open circuit</em> in the dropdown list.
|
||||
The parameters of the pSCR dive can be set by selecting <em>File → Preferences → Profile</em>
|
||||
from the main menu, where the gas consumption calculation takes into account the pSCR dump
|
||||
ratio (default 1:10) as well as the metabolic rate. The calculation also takes the oxygen drop
|
||||
ratio (default 1:8) as well as the metabolic rate. Specify the bottom and deco SAC rates.
|
||||
Here the SAC in the planner is the volume of gas per minute
|
||||
that is exhaled into the loop on the surface, <strong>not</strong> the amount of gas that escapes into the water.
|
||||
The calculation takes the oxygen drop
|
||||
across the mouthpiece of the rebreather into account. If the
|
||||
pO<sub>2</sub> drops below what is considered safe, a warning appears in the <em>Dive plan
|
||||
details</em>. A typical pSCR cylinder setup is very similar to an open circuit dive;
|
||||
one or more drive cylinders, possibly with different bottom and decompression
|
||||
one or more dive cylinders, possibly with different bottom and decompression
|
||||
gases, including gas switches during the dive like in open circuit diving.
|
||||
Therefore, the setup of the <em>Available gases</em> and the <em>Dive planner points</em> tables
|
||||
are very similar to that of a open circuit dive plan, described above. However, no oxygen setpoints
|
||||
|
@ -7920,7 +7963,7 @@ salvaged after being overwritten by new dives.</p></div>
|
|||
<div id="footer">
|
||||
<div id="footer-text">
|
||||
Last updated
|
||||
2017-11-28 08:54:18 CET
|
||||
2018-02-07 17:48:32 CET
|
||||
</div>
|
||||
</div>
|
||||
</body>
|
||||
|
|
|
@ -1995,12 +1995,13 @@ tab of the _Notes_ panel. Photos taken in rapid succession during a dive
|
|||
(therefore sometimes with large overlap on the dive profile) can easily be
|
||||
accessed in the _Photos_ tab. This tab serves as a tool for individually
|
||||
accessing the photos of a dive, while the stubs on the dive profile show
|
||||
when during a dive a photo was taken. Single-click a thumbnail in the
|
||||
_Photos_ panel to select a photo. Double-click a thumbnail to view the
|
||||
full-sized image, overlaying the _Subsurface_ window. Deleted a photo from
|
||||
the _Photos_ panel by selecting it (single-click) and then by pressing the
|
||||
_Del_ key on the keyboard. This removes the photo BOTH from the _Photos_ tab
|
||||
as well as the dive profile.
|
||||
when during a dive a photo was taken. The size of the thumbnails in the
|
||||
_Photos_ tab can be changed using the _Zoom level_ slider at the bottom of
|
||||
the panel. Single-click a thumbnail in the _Photos_ panel to select a
|
||||
photo. Double-click a thumbnail to view the full-sized image, overlaying the
|
||||
_Subsurface_ window. Delete a photo from the _Photos_ panel by selecting it
|
||||
(single-click) and then by pressing the _Del_ key on the keyboard. This
|
||||
removes the photo BOTH from the _Photos_ tab as well as the dive profile.
|
||||
|
||||
==== Photos stockées sur un disque dur externe
|
||||
Most underwater photographers store photos on an external drive. If such a
|
||||
|
@ -2023,7 +2024,7 @@ which dives have associated photos and which not: activate the _Photos_
|
|||
checkbox in the dropdown list obtained by right-clicking on the header bar
|
||||
of the *Divelist*. In the *Divelist*, all dives with associated photographs
|
||||
have an icon indicating whether the photographs were taken during the dive,
|
||||
just before/after the dive or both during and before/after the dive. More
|
||||
just before/after the dive or both during and before/after the dive. More
|
||||
information is provided in the section dealing with <<S_Divelist_columns,
|
||||
photo icons on the *Divelist*>>.
|
||||
|
||||
|
@ -2110,8 +2111,8 @@ only two types of information that need to be provided:
|
|||
in time on the *Dive Profile* panel and indicating the cylinder to which the change was made. After
|
||||
right-clicking, follow the context menu to "Add gas change" and select the appropriate cylinder from
|
||||
those defined during the first step, above (see image below). If the
|
||||
*tank bar* button in the toolbar has been activated, the cylinder switches are also indicated in the
|
||||
tank bar (image below).
|
||||
*gas bar* button in the toolbar has been activated, the cylinder switches are also indicated in the
|
||||
gas bar (image below).
|
||||
|
||||
When this is complete, _Subsurface_ indicates the appropriate use of
|
||||
cylinders in the dive profile. Below is a two-cylinder dive, starting off
|
||||
|
@ -2166,8 +2167,8 @@ three steps, exactly as with multi-cylinder dives above:
|
|||
selecting _Add gas change_. A list of the appropriate cylinders is shown with the
|
||||
currently used cylinder greyed out. In the image below Tank 1 is greyed out, leaving only Tank 2
|
||||
to be selected. Select the appropriate cylinder. The cylinder change is then shown on the dive
|
||||
profile with a cylinder symbol. If the *Tank Bar* is activated using the toolbar to the left of the
|
||||
profile, then the cylinder change is also shown on the Tank Bar (see image below). After all
|
||||
profile with a cylinder symbol. If the *gas bar* is activated using the toolbar to the left of the
|
||||
profile, then the cylinder change is also shown on the gas bar (see image below). After all
|
||||
the cylinder change events have been recorded on the dive profile, the correct cylinder pressures
|
||||
for both cylinders are shown on the dive profile, as in the image below.
|
||||
|
||||
|
@ -3885,20 +3886,37 @@ image::images/PlannerWindow1.jpg["FIGURE: Dive planner startup window", align="c
|
|||
|
||||
==== Plongées loisir
|
||||
|
||||
Recreational mode is what comes closest to planning a dive based on the non-decompression limit (NDL).
|
||||
It computes the maximum time a diver can stay at the current depth without needing mandatory decompression
|
||||
stops and without using more than the existing gas (minus a reserve). The planner automatically takes
|
||||
into account the nitrogen load incurred in previous dives. But conventional dive tables are also used in a
|
||||
way that can take into account previous dives. Why use a dive planner for recreational dives? Using
|
||||
recreational dive tables, the maximum depth of a dive is taken into account. But few dives are
|
||||
done at a constant depth corresponding to the maximum depth (i.e. a "square" dive profile). This means
|
||||
dive tables overestimate the nitrogen load incurred during previous dives. The _Subsurface_
|
||||
dive planner calculates nitrogen load according to the real dive profiles of all uploaded previous dives,
|
||||
in a similar way as dive computers calculate nitrogen load during a dive. This means that the diver gets 'credit,'
|
||||
in terms of nitrogen load, for not remaining at maximum depth during
|
||||
previous dives, so a longer subsequent dive can be planned.
|
||||
For the planner to work it's crucial to upload all previous dives
|
||||
onto _Subsurface_ before doing dive planning.
|
||||
Recreational mode is intended for what most divers would call
|
||||
"recreational", "sports"or "nontechnical" dives, remaining within no-deco
|
||||
limits (NDL). It computes the maximum time a diver can stay at the current
|
||||
depth without needing mandatory decompression stops and without using more
|
||||
than the existing gas (minus a reserve). The planner automatically takes
|
||||
into account the nitrogen load incurred in previous dives. But conventional
|
||||
dive tables are also used in a way that can take into account previous
|
||||
dives. Why use a dive planner for recreational dives? The subsurface dive
|
||||
planner provides two significant advantages over the use of recreational
|
||||
dive tables for dive planning.
|
||||
|
||||
Firstly, using recreational dive tables, the maximum depth of each previous
|
||||
dive is taken into account. But few dives are done at a constant depth
|
||||
corresponding to the maximum depth (i.e. a "square" dive profile). This
|
||||
means dive tables overestimate the nitrogen load incurred during previous
|
||||
dives. The _Subsurface_ dive planner calculates nitrogen load according to
|
||||
the real dive profiles of all uploaded previous dives, in a similar way as
|
||||
dive computers calculate nitrogen load during a dive. This means that the
|
||||
diver gets 'credit,' in terms of nitrogen load, for not remaining at maximum
|
||||
depth during previous dives, so a longer subsequent dive can be planned.
|
||||
For the planner to work it's therefore crucial to log previous dives in
|
||||
_Subsurface_ before doing dive planning.
|
||||
|
||||
Secondly, recreational dive tables are not designed to build additional
|
||||
safety features into a dive. NDL times derived from dive tables often take
|
||||
divers close to the limit where decompression sickness (DCS) can arise. The
|
||||
Subsurface dive planner allows a diver to build more safety features into a
|
||||
dive plan, preventing recreational divers from getting close to the limits
|
||||
of getting a DCS hit. This is performed by specifying appropriate gradient
|
||||
factors for a dive plan, as explained below.
|
||||
|
||||
To plan a dive, the appropriate settings need to be defined.
|
||||
|
||||
Ensure the date and time is set to that of the intended dive. This allows
|
||||
|
@ -3925,10 +3943,7 @@ calculation of the nitrogen load incurred during previous dives.
|
|||
most agencies assume a fixed amount of gas, or actually of pressure e.g. 40
|
||||
or 50 bar or 25% or 33% (rule of thirds). But _Subsurface_ can do better
|
||||
because it knows about the ascent and that is why we add the amount of gas
|
||||
during the ascent (i.e. the "deco gas“). Subsurface still uses a fixed
|
||||
pressure "reserve" but that's supposed to be for the additional gas used
|
||||
when there's a problem and your pulse rate goes up when you start to buddy
|
||||
breathe. This reserve amount is user configurable.
|
||||
during the ascent.
|
||||
|
||||
- Define the depth of the dive by dragging the waypoints (white dots) on the
|
||||
dive profile or (even better) defining the appropriate depths using the
|
||||
|
@ -3943,23 +3958,43 @@ calculation of the nitrogen load incurred during previous dives.
|
|||
défaut sont celles qui sont considérées comme sûres pour les plongées
|
||||
loisir.
|
||||
|
||||
- To build additional safety into the dive plan (over and above those of
|
||||
recreational dive tables), specify gradient factors less than 100% (_GFHigh_
|
||||
and _GFLow_ under the _Planning_ heading in the planner). On the other hand,
|
||||
to approximate the values in recreational dive tables, set the gradient
|
||||
factors to 100. By reducing the values of GFHigh and GFLow to values below
|
||||
100, one can build more safety into a dive. Decreasing the values of the
|
||||
gradient factors below 100 will shorten the duration of the dive. This is
|
||||
the price of a larger safety margin. Reasons for using gradient factors less
|
||||
than 100 may be the age of the diver, the health of a diver, or unusual
|
||||
conditions such as cold water or strong currents. Realistic conservative
|
||||
values for the gradient factors are GFLow=40% and GFHigh=80%. This allows
|
||||
you to create a cusom dive plan, suited to yourself as well as the dive
|
||||
conditions.
|
||||
|
||||
Below is an image of a dive plan for a recreational dive at 30 meters with
|
||||
gradient factors of 100. Because the no-deco limit (NDL) is 22 minutes,
|
||||
there remains a significant amount of air in the cylinder at the end of the
|
||||
dive.
|
||||
|
||||
image::images/Planner_OC_rec1.jpg["FIGURE: A recreational dive plan: setup", align="center"]
|
||||
|
||||
The dive profile in the planner shows the maximum dive time within no-deco
|
||||
limits using the Bühlmann ZH-L16 algorithm and the gas and depth settings
|
||||
specified as described above. The _Subsurface_ planner allows rapid
|
||||
assessment of dive duration as a function of dive depth, given the nitrogen
|
||||
load incurred during previous dives. The dive plan includes estimates of the
|
||||
amount of air/gas used, depending on the cylinder settings specified under
|
||||
_Available gases_. If the initial cylinder pressure is set to 0, the dive
|
||||
_Available gases_. If the start cylinder pressure is left blank, the dive
|
||||
duration shown is the true no-deco limit (NDL) without taking into account
|
||||
gas used during the dive. If the surface above the dive profile is RED it
|
||||
means that recreational dive limits are exceeded and either the dive
|
||||
duration or the dive depth needs to be reduced.
|
||||
|
||||
Below is an image of a dive plan for a recreational dive at 30
|
||||
meters. Although the no-deco limit (NDL) is 23 minutes, the duration of the
|
||||
dive is limited by the amount of air in the cylinder.
|
||||
Below is the same dive plan as above, but with a safety stop and reduced
|
||||
gradient factors for a larger safety margin.
|
||||
|
||||
image::images/Planner_OC_rec.jpg["FIGURE: A recreational dive plan: setup", align="center"]
|
||||
image::images/Planner_OC_rec2.jpg["FIGURE: A recreational dive plan: gradient factors setup", align="center"]
|
||||
|
||||
==== Plongées en circuit ouvert non loisir, incluant une décompression
|
||||
|
||||
|
@ -3976,6 +4011,7 @@ the planner), the new values are
|
|||
used without changing the original values in the _Preferences_.
|
||||
Gradient Factor settings strongly affect the calculated ceilings and their depths.
|
||||
A very low GFLow value brings on decompression stops early during the dive.
|
||||
|
||||
** For more information about Gradient factors, see the section on xref:S_GradientFactors[Gradient Factor Preference settings].
|
||||
|
||||
If the VPM-B model is selected, the Conservatism_level needs to be specified
|
||||
|
@ -4126,13 +4162,14 @@ the *Dive List* panel of _Subsurface_.
|
|||
|
||||
*Les détails du plan de plongée*
|
||||
|
||||
On the bottom right of the dive planner, under _Dive Plan Details_, the
|
||||
details of the dive plan are provided. These may be modified by checking any
|
||||
of the options under the _Notes_ section of the dive planner, immediately to
|
||||
the left of the _Dive Plan Details_. If a _Verbatim dive plan_ is requested,
|
||||
a detailed sentence-level explanation of the dive plan is given. If any of
|
||||
the management specifications have been exceeded during the planning, a
|
||||
warning message is printed underneath the dive plan information.
|
||||
On the bottom right panel of the dive planner, under _Dive Plan Details_,
|
||||
the details of the dive plan are provided. These may be modified by checking
|
||||
any of the options under the _Notes_ section of the dive planner,
|
||||
immediately to the left of the _Dive Plan Details_. If a _Verbatim dive
|
||||
plan_ is requested, a detailed sentence-level explanation of the dive plan
|
||||
is given. If any of the management specifications have been exceeded during
|
||||
the planning, a warning message is printed underneath the dive plan
|
||||
information.
|
||||
|
||||
If the option _Display segment duration_ is checked, then the duration of
|
||||
each depth level is indicated in the _Dive Plan Details_. This duration
|
||||
|
@ -4140,53 +4177,43 @@ INCLUDES the transition time to get to that level. However, if the _Display
|
|||
transition in deco_ option is checked, the transitions are shown separately
|
||||
from the segment durations at a particular level.
|
||||
|
||||
The planner has a check box _Display plan variations_. By checking this box,
|
||||
the planner provides information about a dive that is a little deeper or
|
||||
slightly longer than the planned dive. This is found near the top of the
|
||||
_Dive plan details_ where the dive duration is indicated. The information is
|
||||
intended to be used if it is necessary to modify the ascent "on the fly" in
|
||||
the case of unexpected deviations from the dive plan during the dive.
|
||||
Checking this option creates a lot of additional computation, to such a
|
||||
degree that the planner is slower than otherwise. The information is
|
||||
typically given as:
|
||||
*Dive plan variations*: The planner has a check box _Display plan variations_. By checking this box, the planner
|
||||
provides information about a dive that is a little deeper or slightly
|
||||
longer than the planned dive. This is found near the top of the _Dive plan details_
|
||||
where the dive duration is indicated. The information is intended to be used if it is necessary to
|
||||
modify the ascent "on the fly" in the case of unexpected deviations from the dive plan during the dive.
|
||||
For example, if it says "Runtime: 123min, Stop times + 2:49 /m + 1:30 /min" this means: if you dive deeper
|
||||
than planned, you should add almost 3 minutes per meter you go deeper to your decompression (and
|
||||
you can substract 3 minutes per meter that you stay shallower). If you overstay your bottom
|
||||
time, you need to add one and a half minutes to the stops for each minutes you overstay
|
||||
and similarly, you can shorten your deco time by one and a half minute for each minute
|
||||
you stay shorter. These variations of depth and time are based on the last manually entered segment of the
|
||||
dive (not necessarily the deepest). The additional minutes should be distributed
|
||||
over the differnent stops in a way proportional to the stop length, i.e. add more of the
|
||||
additional minutes to the longer, shallower stops. The given times refer to the
|
||||
duration of the decompression phase and do not include the extended bottom time!
|
||||
This way of altering dive plans becomes inaccurate for large deviations from the original
|
||||
plan. So it should not be trusted for more than a few minutes or meters of
|
||||
deviations from the planned bottom time. Checking this option creates a lot of additional computation,
|
||||
to such a degree that the planner is slower than otherwise.
|
||||
|
||||
Runtime: 53min + 0:52/m + 4:21/min
|
||||
*Minimum gas requirements*: The planner also estimates the _minimum gas_ pressure
|
||||
required for safe ascent after an event that causes the dive to be aborted. The
|
||||
calculation assumes that in worst case an out of gas (OoG)
|
||||
situation occurs at the end of the planned bottom time at maximum depth, requiring
|
||||
additional time at maximum depth to solve the problem and forcing
|
||||
the buddy pair the share the gas of one diver. In addition the combined SAC of both
|
||||
divers is increased by an estimated factor compared to the SAC of a single diver under normal conditions.
|
||||
The result of the minimum gas calculation for the bottom gas is printed to the planner output. There
|
||||
are two selector boxes on the left of the _Dive plan details_:
|
||||
|
||||
This indicates:
|
||||
|
||||
* Calculated dive duration is 53 min.
|
||||
* For each extra meter in depth during the bottom phase of the dive, the
|
||||
ascent duration increases by 52 seconds.
|
||||
* For each extra minute of bottom time, the duration increases by 4 min 21
|
||||
sec. Thus, if the bottom time is two minutes longer than planned, ascent
|
||||
duration duration will be (2 * 4min 21 sec) = 8 minutes 42 sec longer and
|
||||
would probably require that each deco stop is 8:42/53:00 = around 16% longer
|
||||
than planned. These calculations are only applicable for small deviations
|
||||
from the dive plan, not for larger deviations.
|
||||
|
||||
*Minimum gas requirements*
|
||||
|
||||
The planner also estimates the *minimum gas* pressure required for safe
|
||||
ascent after an event that causes the dive to be aborted. The calculation
|
||||
assumes that in worst case an out of gas (OoG) situation occurs at the end
|
||||
of the planned bottom time at maximum depth. This OoG event forces the buddy
|
||||
team the share the gas of one diver and that they require an additional
|
||||
period of time at maximum depth to solve the problem at hand. In addition
|
||||
the combined SAC of both divers is increased by an estimated factor compared
|
||||
to the SAC factor of a single diver under normal conditions. The result of
|
||||
the minimum gas calculation for the bottom gas is printed to the planner
|
||||
output. No automatic checks are performed based on this result. The feature
|
||||
only gives valid results for simple, rectangular shaped single level dive
|
||||
profiles. For multi level dives one would need to check every leg of the
|
||||
profile independently.
|
||||
|
||||
There are two selector boxes on the left of the _Dive plan details_:
|
||||
|
||||
* *SAC factor*. This is an estimate of the degree to which your SAC increases if a critical problem arises underwater,
|
||||
e.g. gas sharing or entanglement. Realistic values range from 2 to 5, reflecting the gas use of two divers sharing
|
||||
a single gas cylinder after an OoG situation.
|
||||
* *Problem solving time*. This is an estimate of how long you would take to solve the problem before starting the ascent
|
||||
to terminate the dive. The default value is 2 minutes.
|
||||
* _SAC factor_. This is an estimate of the degree to which your SAC increases
|
||||
if a critical problem arises underwater, e.g. gas sharing or
|
||||
entanglement. Realistic values range from 3 to 5, reflecting the gas use of
|
||||
two divers sharing a single gas cylinder after an OoG situation.
|
||||
* _Problem solving time_. This is an estimate of how long you would take to
|
||||
solve the problem before starting the ascent to terminate the dive. The
|
||||
default value is 2 minutes.
|
||||
|
||||
Using the above information, the planner then estimates what the minimum
|
||||
bottom gas cylinder pressure needs to be for a safe ascent. This information
|
||||
|
@ -4198,7 +4225,7 @@ plan. the minimum gas is typically given as:
|
|||
|
||||
This indicates:
|
||||
|
||||
* Within parentheses, the *SAC factor* and *Problem solving time* specified.
|
||||
* Within parentheses, the _SAC factor_ and _Problem solving time_ specified.
|
||||
* The number of liters of back gas required for a safe ascent (2130 litres in
|
||||
the example above)
|
||||
* The number of bars of back gas required for a safe ascent (90 bars in the
|
||||
|
@ -4208,14 +4235,34 @@ This indicates:
|
|||
bars in the above example). A positive delta reflects a safe plan; a
|
||||
negative delta indicates insufficient gas for a safe ascent.
|
||||
|
||||
No automatic checks are performed based on this result. The feature only
|
||||
gives valid results for simple, rectangular shaped single level dive
|
||||
profiles. For multi level dives one would need to check every leg of the
|
||||
profile independently.
|
||||
|
||||
*Isobaric counterdiffusion information*: For gas switches during the ascent in hypoxic open-circuit trimix dives information
|
||||
about isobaric counterdiffusion (icd) is given near the bottom of the _Dive plan details_, based on the
|
||||
rule-of-fifths (i.e. during a gas change, the increase in nitrogen partial pressure should not exceed
|
||||
one fifth of the corresponding decrease in partial pressure of helium). For each gas change, two lines
|
||||
are printed, indicating the changes in gas fractions (%) and the equivalent changes in partial pressures. If the
|
||||
rule-of-fifths is not met, the relevant information is highlighted in red and a warning message appears
|
||||
at the bottom of that table. The gas change events on the dive profile also provide information on icd,
|
||||
visible at the bottom of the _Information box_ when the mouse hovers on the respective gas change icon. This information
|
||||
is only shown for gas changes relevant with respect to icd. If the rule-of-fifths is not met,
|
||||
a red warning exclamation mark is shown over the gas change icon. When relevant, the _Information box_ contains
|
||||
information such as: ICD ΔHe:-13% ΔN₂+3%>2.6%. This means: for this gas change, the helium
|
||||
decreased with 13% while the nitrogen increased with 3% which
|
||||
is more than the 2.6% maximum increase in nitrogen suggested by the rule-of-fifths.
|
||||
|
||||
****
|
||||
[icon="images/icons/warning2.png"]
|
||||
[WARNING]
|
||||
The *plan variations* and *minimum gas* estimates are only guidelines for a
|
||||
diver performing dive planning, intended to enhance the safety of executing
|
||||
a particular dive plan. They are NOT precise and should NOT be relied upon
|
||||
as the only safety features in dive planning. Interpret these estimates
|
||||
within the framework of your formal training to perform dive planning.
|
||||
a particular dive plan and do not replace formal contingency planning for a
|
||||
specific dive. They are NOT precise and should NOT be relied upon as the
|
||||
only safety features in dive planning. Interpret these estimates within the
|
||||
framework of your formal training to perform dive planning.
|
||||
****
|
||||
|
||||
=== Planning pSCR dives
|
||||
|
@ -4224,11 +4271,14 @@ To plan a dive using a passive semi-closed rebreather (pSCR), select _pSCR_ rath
|
|||
_Open circuit_ in the dropdown list.
|
||||
The parameters of the pSCR dive can be set by selecting _File -> Preferences -> Profile_
|
||||
from the main menu, where the gas consumption calculation takes into account the pSCR dump
|
||||
ratio (default 1:10) as well as the metabolic rate. The calculation also takes the oxygen drop
|
||||
ratio (default 1:8) as well as the metabolic rate. Specify the bottom and deco SAC rates.
|
||||
Here the SAC in the planner is the volume of gas per minute
|
||||
that is exhaled into the loop on the surface, *not* the amount of gas that escapes into the water.
|
||||
The calculation takes the oxygen drop
|
||||
across the mouthpiece of the rebreather into account. If the
|
||||
pO~2~ drops below what is considered safe, a warning appears in the _Dive plan
|
||||
details_. A typical pSCR cylinder setup is very similar to an open circuit dive;
|
||||
one or more drive cylinders, possibly with different bottom and decompression
|
||||
one or more dive cylinders, possibly with different bottom and decompression
|
||||
gases, including gas switches during the dive like in open circuit diving.
|
||||
Therefore, the setup of the _Available gases_ and the _Dive planner points_ tables
|
||||
are very similar to that of a open circuit dive plan, described above. However, no oxygen setpoints
|
||||
|
|
Loading…
Add table
Reference in a new issue