mifr/subsurface
1
0
Fork 0
mirror of https://github.com/subsurface/subsurface.git synced 2025-01-19 14:25:27 +00:00
Code Issues Projects Releases Packages Wiki Activity

Documentation: fixed some typos in bluettoth part of user manual

Browse source 
[Dirk Hohndel: some fixes of the fixes...]

Signed-off-by: Jan Schubert <Jan.Schubert@GMX.li>
Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
This commit is contained in:
Jan Schubert 2013-02-26 21:55:01 +01:00 • committed by Dirk Hohndel
parent fd9a927ded
commit 16d9f3007f
1 changed files with 7 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
Documentation/user-manual.txt
View file

@ -274,8 +274,8 @@ Weikamp Frog or the Shearwater Predator and Petrel there is a
different procedure to get the devices name to communicate with different procedure to get the devices name to communicate with
subsurface. In general it consists of these steps: subsurface. In general it consists of these steps:
.Enable bluetooth on your computer * enable bluetooth on your computer
.Pairing the device * pairing the device
Please do not forget to set your divecomputer in Bluetooth or upload mode before Please do not forget to set your divecomputer in Bluetooth or upload mode before
Paring and Downloading logs. If you use a Shearwater Predator/Petrel just select Paring and Downloading logs. If you use a Shearwater Predator/Petrel just select
@ -283,11 +283,11 @@ Paring and Downloading logs. If you use a Shearwater Predator/Petrel just select
.On Windows: .On Windows:
Bluetooth is most likely already enabled. For Pairing the device choose Bluetooth is most likely already enabled. For pairing the device choose
Control Panel->Bluetooth Devices->Add Wireless Device Control Panel->Bluetooth Devices->Add Wireless Device
This should bring up a dialog showing your dive computer (in Bluetooth mode) and This should bring up a dialog showing your dive computer (in Bluetooth mode) and
allowing to pair it. Choose "0000" as PIN set in your dive computer should work allowing to pair it. Choose "0000" as PIN set in your dive computer should work
in most cases, if not refere to the manufacturer of your dive computer. The dive in most cases, if not, refer to the manufacturer of your dive computer. The dive
computer should then show up in the list of Bluetooth devices and you may then computer should then show up in the list of Bluetooth devices and you may then
right click on it and choose Properties->COM Ports to get known of the ports right click on it and choose Properties->COM Ports to get known of the ports
used for your dive computer. If there are several ports listet use the one used for your dive computer. If there are several ports listet use the one
@ -299,7 +299,7 @@ Downloading in Subsurface, the drop down list should contain this COM
port already, if not enter it manually. port already, if not enter it manually.
Note: If you have issues downloading from your dive computer in other software Note: If you have issues downloading from your dive computer in other software
afterwards try to remove the pairing to get it to work again (proven to work for afterwards try to remove the pairing to get it working again (proven to work for
Shearwater Desktop). Shearwater Desktop).
.On MacOS: .On MacOS:
@ -353,12 +353,12 @@ Using Bluetooth for downloading from dive computers on Linux seems to be tricky
some times. If you have issues please have a look to the following notes. Using some times. If you have issues please have a look to the following notes. Using
a Shearwater Predator you may be able to pair but then encounter issues when a Shearwater Predator you may be able to pair but then encounter issues when
downloading, showing errors like "Slip RX: unexp. SLIP END" on the Predator. downloading, showing errors like "Slip RX: unexp. SLIP END" on the Predator.
This might be also seen, when using other dive log software and operating This might also be seen, when using other dive log software and operating
systems than Linux. We have no detailed idea about the source and how to fix systems than Linux. We have no detailed idea about the source and how to fix
this, but it is reported to be solved sometimes by one of these steps: this, but it is reported to be solved sometimes by one of these steps:
* use the bluetooth dongle which came with the Shearwater Predator instead of * use the bluetooth dongle which came with the Shearwater Predator instead of
* the inbuilt one of your computer the built-in one of your computer
* switch to different bluetooth drivers for your hardware * switch to different bluetooth drivers for your hardware
* switch of WiFi while using Bluetooth * switch of WiFi while using Bluetooth