Halaman utama Jelajahi Bantuan
Masuk
ademant
/
gpsd
Liatin 1
Bintangi 0
Fork 0
Berkas Masalah 0 Tarik Permintaan 0 Wiki
Cabang: pylib-fixes
Ranting Tag
gpsd
/
www
/
bt.html

bt.html 7.6 KB
Permalink Riwayat Mentahan

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231 
  1. <!DOCTYPE HTML>
    2. 

  2. <html lang="en">
    3. 

  3. <head lang="en">
    4. 

  4.    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
    5. 

  5.    <meta name="Author" content="Eric S. Raymond">
    6. 

  6.    <meta name="Description" content="Blutooth setup instructions for GPSD">
    7. 

  7.    <meta name="Keywords" content="GPS, gpsd, bluetooth">
    8. 

  8.    <meta name="Revised" content="24 June 2020">
    9. 

  9.    <meta name="robots" content="index,follow">
    10. 

  10.    <link rel="stylesheet" href="main.css" type="text/css">
    11. 

  11.    <title>Bluetooth and GPSD</title>
    12. 

  12. </head>
    13. 

  13. 

  14. <body>
    15. 

  15. 

  16. <div id="Header">Bluetooth and <code>gpsd</code></div>
    17. 

  17. 

  18. <div id="Menu">
    19. 

  19.     <img src="gpsd-logo-small.png" alt="Small gpsd Logo" height="126"
    20. 

  20.     width="105"><br>
    21. 

  21.     <a href="index.html">Home</a><br>
    22. 

  22.     <a href="index.html#news">News</a><br>
    23. 

  23.     <a href="index.html#downloads">Downloads</a><br>
    24. 

  24.     <a href="index.html#mailing-lists">Mailing lists</a><br>
    25. 

  25.     <a href="index.html#documentation">Documentation</a><br>
    26. 

  26.     <a href="faq.html">FAQ</a><br>
    27. 

  27.     <a href="xgps-sample.html">Screenshots</a><br>
    28. 

  28.     <a href="index.html#recipes">Recipes</a><br>
    29. 

  29.     <a href="index.html#others">Other GPSDs</a><br>
    30. 

  30.     <a href="hardware.html">Hardware</a><br>
    31. 

  31.     <a href="for-vendors.html">For GPS Vendors</a><br>
    32. 

  32.     <a href="wishlist.html">Wish List</a><br>
    33. 

  33.     <a href="hall-of-shame.html">Hall of Shame</a><br>
    34. 

  34.     <a href="troubleshooting.html">Troubleshooting Guide</a><br>
    35. 

  35.     <a href="hacking.html">Hacker's Guide</a><br>
    36. 

  36.     <a href="protocol-transition.html">Application Compatibility</a>
    37. 

  37.     <a href="references.html">References</a><br>
    38. 

  38.     <a href="history.html">History</a><br>
    39. 

  39.     <a href="future.html">Future</a><br>
    40. 

  40. 

  41.     <a href='http://www.catb.org/hacker-emblem/'><img
    42. 

  42.     src='glider.png' alt='hacker emblem' height="55" width="55"></a><br>
    43. 

  43. 

  44.     <script src="https://www.openhub.net/p/3944/widgets/project_thin_badge.js"></script>
    45. 

  45. 

  46.     <a href="https://validator.w3.org/check/referer"><img
    47. 

  47.           src="https://www.w3.org/Icons/valid-html401"
    48. 

  48.           alt="Valid HTML 4.01!" height="31" width="88"></a>
    49. 

  49. </div>
    50. 

  50. 

  51. <div id="Content">
    52. 

  52. 

  53. <p>Bluetooth connections work with <code>gpsd</code> by leveraging the
    54. 

  54. rfcomm serial port emulation.  Rfcomm provides a serial port interface
    55. 

  55. to a BT device and has been designed to allow for automated
    56. 

  56. connect/disconnect operations over Bluetooth.  The steps below will
    57. 

  57. allow you to use your BT GPS device automatically whenever it is
    58. 

  58. powered on and gpsd is running.</p>
    59. 

  59. 

  60. <p>Note that you must be logged in as root for most of these steps.</p>
    61. 

  61. 

  62. <h2>Installation</h2>
    63. 

  63. 

  64. <p>If your system comes with Bluetooth tools preinstalled (look for
    65. 

  65. <img src="bt.png" alt="Bluetooth icon"> on your status bar) you can
    66. 

  66. probably skip these steps.</p>
    67. 

  67. 

  68. <ol>
    69. 

  69. <li><p>First, the Bluez protocol stack must be installed.  All the
    70. 

  70. documentation can be found on <a
    71. 

  71. href='http://bluez.sourceforge.net/'>http://bluez.sourceforge.net/</a>.</p></li>
    72. 

  72. <li><p>Install bluetooth for your device with the "rfcomm" module to
    73. 

  73. allow for serial port emulation.</p>
    74. 

  74. 

  75. <p>This procedure has been verified against Blues version 5.54, but
    76. 

  76. should work with any recent version.</p></li>
    77. 

  77. 

  78. <li><p>Next, load the following modules:</p>
    79. 

  79. <pre>
    80. 

  80.         # modprobe hci_xxx (xxx depend on your type of device)
    81. 

  81.         # modprobe bluez
    82. 

  82.         # modprobe l2cap
    83. 

  83.         # modprobe rfcomm
    84. 

  84. </pre>
    85. 

  85. </li>
    86. 

  86. 

  87. <li><p>If the modules have loaded successfully, type "hciconfig" and you
    88. 

  88. should see your BT interface listed under the "hci0" name.  "hciconfig" is
    89. 

  89. part of the Bluez stack.  Not all distributions install it by default.
    90. 

  90. Gentoo requires USE="deprecated" with bluez to install hciconfig.</p></li>
    91. 

  91. </ol>
    92. 

  92. 

  93. <h2>Configuration</h2>
    94. 

  94. 

  95. <ol>
    96. 

  96. <li><p>Turn on your BT GPS device and scan for remote BT devices:</p>
    97. 

  97. <pre>
    98. 

  98.     # hciconfig hci0 up
    99. 

  99.     # hcitool scan
    100. 

  100. </pre>
    101. 

  101. </li>
    102. 

  102. 

  103. <li><p>Write down the address of your BT GPS receiver (xx:xx:xx:xx:xx:xx).
    104. 

  104. At this point, it is quite likely that passing the address to gpsd will work.</p></li>
    105. 

  105. 

  106. <li><p>If you're using a smartphone app to send your GPS data via
    107. 

  107. Bluetooth Start the GPS app on your phone, altering any settings needed
    108. 

  108. to make it send NMEA strings over Bluetooth.</p></li>
    109. 

  109. 

  110. <li><p>Check the protocol and channel that your device supports.</P>
    111. 

  111. 

  112. <pre>
    113. 

  113.     # sdptool browse xx:xx:xx:xx:xx:xx
    114. 

  114. </pre>
    115. 

  115. 

  116. <p>A smartphone app will look something like this in the output.  Note
    117. 

  117. the channel number is 2:</p>
    118. 

  118. 

  119. <pre>
    120. 

  120.   Service Name: GPS2BT
    121. 

  121.   Service RecHandle: 0x1000b
    122. 

  122.   Service Class ID List:
    123. 

  123.     UUID 128: 00001101-0000-1000-8000-00805f9b34fb
    124. 

  124.   Protocol Descriptor List:
    125. 

  125.     "L2CAP" (0x0100)
    126. 

  126.     "RFCOMM" (0x0003)
    127. 

  127.       Channel: 2
    128. 

  128. </pre>
    129. 

  129. 

  130. <p>A standalone Bluetooth GPS may look like this.  Note the channel
    131. 

  131. number is 1:</p>
    132. 

  132. 

  133. <pre>
    134. 

  134.   Service Name: SPP slave
    135. 

  135.   Service RecHandle: 0x10000
    136. 

  136.   Service Class ID List:
    137. 

  137.     "Serial Port" (0x1101)
    138. 

  138.   Protocol Descriptor List:
    139. 

  139.     "L2CAP" (0x0100)
    140. 

  140.     "RFCOMM" (0x0003)
    141. 

  141.       Channel: 1
    142. 

  142.   Language Base Attr List:
    143. 

  143.     code_ISO639: 0x656e
    144. 

  144.     encoding:    0x6a
    145. 

  145.     base_offset: 0x100
    146. 

  146. </pre>
    147. 

  147. 

  148. <p>The Service name will vary based on the app or device.  Write down the
    149. 

  149. channel number and use it in the next step instead of channel 1. The channel
    150. 

  150. number will likely vary each time the app is started, so you will probably
    151. 

  151. need some scripting or other additional configuration to fix that. If gpsd or
    152. 

  152. gpsctl is reporting "connection refused" it is likely that you have the
    153. 

  153. wrong channel number.</p>
    154. 

  154. 

  155. <p>If you're using a smartphone app you will probably need to specify a
    156. 

  156. channel other than 1.</p>
    157. 

  157. </li>
    158. 

  158. 

  159. <li><p>The /etc/bluetooth/rfcomm.conf file is no longer used by rfcomm.
    160. 

  160. Previous versions of this procedure used that file.<p>
    161. 

  161. </li>
    162. 

  162. 

  163. <li><p>Bind rfcomm0 to the serial data channel, in this case 1, of the BT
    164. 

  164. GPS.  Then verify it worked:</p>
    165. 

  165. <pre>
    166. 

  166.     # rfcomm bind rfcomm0 xx:xx:xx:xx:xx:xx 1
    167. 

  167.     # rfcomm -a
    168. 

  168.     rfcomm0: xx:xx:xx:xx:xx:xx channel 1 clean 
    169. 

  169.     # ls /dev/rfcomm0
    170. 

  170.     /dev/rfcomm0
    171. 

  171. </pre>
    172. 

  172. <p>You will now have a new device file, /dev/rfcomm0, that you will
    173. 

  173. use for gpsd to connect to the BT GPS.
    174. 

  174. </li>
    175. 

  175. 

  176. <li>
    177. 

  177. <p>Under most Linux distros, GPSD is by default configured to start gpsd on
    178. 

  178. a hotplug event announcing a USB GPS. You need to reconfigure the GPSD
    179. 

  179. installation so the daemon will be started at boot time listening to
    180. 

  180. /dev/rfcomm0 (it will still work with hotplugged USB GPSes after you
    181. 

  181. do this).</p>
    182. 

  182. 

  183. <p>Under Debian and Ubuntu Linux, <code>"dpkg-reconfigure gpsd"</code>
    184. 

  184. will start a dialog that will reconfigure the device for you. You
    185. 

  185. will need to reboot for this change to take effect.</p>
    186. 

  186. </li>
    187. 

  187. 

  188. <li><p>You may find it easier just to start gpsd manually.</p>
    189. 

  189. <pre>
    190. 

  190.     # gpsd -n /dev/rfcomm0
    191. 

  191. </pre>
    192. 

  192. </ol>
    193. 

  193. 

  194. <p>At this point, your system should be configured to use gpsd with
    195. 

  195. your BT GPS device. You should test operation in the normal way
    196. 

  196. described in the <a href="troubleshooting.html">Troubleshooting Guide</a>.</p>
    197. 

  197. 

  198. <h2>Known Issues:</h2>
    199. 

  199. <ul>
    200. 

  200. <li><p>Apparmor may silently prevent gpsd from using rfcomm.  Check
    201. 

  201. your "dmesg" output for signs of Apparmor interference.</p></li>
    202. 

  202. 

  203. <li><p>Creating rfcomm to bind on startup, and then starting gpsd, is
    204. 

  204. very init system dependent and is not covered here.</p>
    205. 

  205. </li>
    206. 

  206. 

  207. <li>
    208. 

  208. <p>In February 2009 it was reported that there are some issues with
    209. 

  209. the Bluetooth stack in Ubuntu Intrepid. <a
    210. 

  210. href="http://cris.bytesnblades.net/2009/02/20/starting-gpsd-automatically-with-a-bluetooth-gps/">This
    211. 

  211. report advocates using a different Bluetooth device manager and describes some
    212. 

  212. additional udev rules.</a></p>
    213. 

  213. </li>
    214. 

  214. </ul>
    215. 

  215. 

  216. <h2>Contributors:</h2>
    217. 

  217. <ul>
    218. 

  218. <li><p>Jean-Michel Bouffard</p></li>
    219. 

  219. <li><p>Joshua Layne</p></li>
    220. 

  220. <li><p>Lukasz Stelmach</p></li>
    221. 

  221. <li><p>Bertolt Loprets</p></li>
    222. 

  222. <li><p>Rob Shinn</p></li>
    223. 

  223. <li><p>Tomáš Ebenlendr</p></li>
    224. 

  224. </ul>
    225. 

  225. 

  226. <hr>
    227. 

  227. <script src="datestamp.js"></script>
    228. 

  228. </div>
    229. 

  229. </body>
    230. 

  230. </html>
    231. 

  231.