I had incorrectly assumed the default RFCOMM channel was 0.  It's 1 as
pointed out by Anton.  This patch corrects it in the FAQ and user
manual.

Regards,

Rick
From 06857f4fc768b7f912c8d364c0b66a6fb98c6f33 Mon Sep 17 00:00:00 2001
From: Rick Walsh <[email protected]>
Date: Mon, 25 May 2015 21:26:58 +1000
Subject: [PATCH] Correct default RFCOMM channel in documentation

The default RFCOMM channel is 1, not 0 as previously stated in FAQ and user manual.  This patch corrects it.

Signed-off-by: Rick Walsh <[email protected]>
---
 Documentation/FAQ.wordpress   | 8 ++++----
 Documentation/user-manual.txt | 8 ++++----
 2 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/Documentation/FAQ.wordpress b/Documentation/FAQ.wordpress
index da918bb..1d64d3f 100644
--- a/Documentation/FAQ.wordpress
+++ b/Documentation/FAQ.wordpress
@@ -189,11 +189,11 @@ The command to establish an RFCOMM connection is:
 &lt;controller&gt; is the Bluetooth controller, hci0
 &lt;dev&gt; is the RFCOMM device file, rfcomm0
 &lt;bdaddr&gt; is the dive computer's MAC address, 00:11:22:33:44:55
-[channel] is the dive computer's Bluetooth channel we need to connect to.  If you omit it, channel 0 will be assumed.  Based on a limited number of user reports, the channel for different dive computers is probably:
+[channel] is the dive computer's Bluetooth channel we need to connect to.  If you omit it, channel 1 will be assumed.  Based on a limited number of user reports, the channel for different dive computers is probably:
 <ul>
 <li>Shearwater Petrel 2: channel 5
-<li>Shearwater Petrel 1: channel 0
-<li>OSTC Sport: Channel 0
+<li>Shearwater Petrel 1: channel 1
+<li>OSTC Sport: Channel 1
 </ul>
 E.g. to connect a Shearwater Petrel 2, set the dive computer to upload mode and enter:
 <pre><code style="font-size: 8pt;">sudo rfcomm -i hci0 connect rfcomm0 00:11:22:33:44:55 5
@@ -203,7 +203,7 @@ Press CTRL-C for hangup</code></pre>
 To connect a Shearwater Petrel 1 or OSTC Sport, set the dive computer to upload mode and enter:
 <pre><code style="font-size: 8pt;">sudo rfcomm -i hci0 connect rfcomm0 00:11:22:33:44:55
 (enter password when prompted)
-Connected /dev/rfcomm0 to 00:11:22:33:44:55 on channel 0
+Connected /dev/rfcomm0 to 00:11:22:33:44:55 on channel 1
 Press CTRL-C for hangup</code></pre>
 If you don't know what channel your dive computer uses, or the channel in the list above doesn't work, the command 'sdptool records' should help determine the appropriate channel.  The output below is from a Shearwater Petrel 2.
 <pre><code style="font-size: 8pt;">sdptool -i hci0 records 00:11:22:33:44:55
diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
index 349b19a..f1a5879 100644
--- a/Documentation/user-manual.txt
+++ b/Documentation/user-manual.txt
@@ -3610,12 +3610,12 @@ The command to establish an RFCOMM connection is:
 - <bdaddr> is the dive computer's MAC address, +00:11:22:33:44:55+
 - [channel] is the dive computer's Bluetooth channel we need to connect to.
 
-If one omits it, channel 0 is assumed.  Based on a limited number of user reports,
+If one omits it, channel 1 is assumed.  Based on a limited number of user reports,
 the appropriate channel for the dive computer is probably:
 
 - _Shearwater Petrel 2_: channel 5
-- _Shearwater Petrel 1_: channel 0
-- _Heinrichs-Weikamp OSTC Sport_: channel 0
+- _Shearwater Petrel 1_: channel 1
+- _Heinrichs-Weikamp OSTC Sport_: channel 1
 
 E.g. to connect a _Shearwater Petrel 2_, set the dive computer to upload mode and enter:
 
@@ -3629,7 +3629,7 @@ This gives the response:
 To connect a _Shearwater Petrel 1+ or + HW OSTC Sport+, set the dive computer to upload mode and enter:
 
 	sudo rfcomm -i hci0 connect rfcomm0 00:11:22:33:44:55   (enter a password, probably 0000, when prompted)
-	Connected /dev/rfcomm0 to 00:11:22:33:44:55 on channel 0
+	Connected /dev/rfcomm0 to 00:11:22:33:44:55 on channel 1
 	Press CTRL-C for hangup
 
 If the specific channel the dive computer needs is not known, or the channel in the list above doesn't
-- 
2.4.1

_______________________________________________
subsurface mailing list
[email protected]
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Reply via email to