diff options
| author |  Tim Wootton <timw00.tw@googlemail.com> | 2013-12-10 21:27:53 +0000 |
|---|---|---|
| committer |  Dirk Hohndel <dirk@hohndel.org> | 2013-12-10 22:39:41 +0100 |
| commit | edfa3ba810f500c293eade993829e11f37145922 (patch) | |
| tree | dc8e5afa30bca441c659925ebb2c0aa25007e308 /Documentation | |
| parent | aa34ca814d89468c3d2908e900dea5a19097ab72 (diff) | |
| download | subsurface-edfa3ba810f500c293eade993829e11f37145922.tar.gz | |
User manual: use charge rather than load when referring to battery
Signed-off-by: Tim Wootton <tim@tee-jay.demon.co.uk>
Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/user-manual.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt index 1d4f5b81c..f4436cf7c 100644 --- a/Documentation/user-manual.txt +++ b/Documentation/user-manual.txt @@ -237,7 +237,7 @@ Often, dive computers retain all their dives even though these dives have been i [IMPORTANT] In the case of *communication failure* then check the following: 1) Is the dive computer still in PC-communication or Upload mode? -2) Is the battery of the dive computer fully loaded? If not then load or replace the battery. +2) Is the battery of the dive computer fully charged? If not then charge or replace the battery. 3) Is the cable faulty? Does the cable work perfectly using other software? Has it worked before, or is this the first time you are using the cable? 4) Consult *Appendix A* and make sure you specified the correct Mount Point (see above). If your _Subsurface_ computer does not recognise the USB adaptor by showing an appropriate device name next to the Mount Point, then there is a possibility that the cable or USB adaptor is faulty. A faulty cable is the most common cause of communcation failure between dive computer and _Subsurface_ computer. |