summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoseph Herlant <aerostitch@users.noreply.github.com>2019-06-05 11:31:56 -0700
committerGitHub <noreply@github.com>2019-06-05 11:31:56 -0700
commit93ab5a0b2c41dd703ecd121afc5e61f14f5cf7b6 (patch)
treeafaa2536790e9dded1b0cddab583d01a13175349
parented11c5f8de5095da29e14068f9c8670fd0398022 (diff)
downloadnavit-93ab5a0b2c41dd703ecd121afc5e61f14f5cf7b6.tar.gz
Probably don't need "please" here.
-rw-r--r--docs/basic_configuration.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/basic_configuration.rst b/docs/basic_configuration.rst
index 732e50caf..74c54a0cd 100644
--- a/docs/basic_configuration.rst
+++ b/docs/basic_configuration.rst
@@ -18,7 +18,7 @@ On some systems Navit comes with integrated espeak support, so you don't need to
Connect GPS
-----------
-Now please connect your GPS. The exact procedure for this varies depending on the type of GPS device you are using and how you connect it to your computer. On Linux / Unix systems, your GPS should typically show up as a character device, i.e., you will find an entry in the /dev folder corresponding to your GPS device. Again, the file name depends on the type and connection method of your GPS receiver. See [[Connecting a GPS receiver]] for details.
+Now connect your GPS. The exact procedure for this varies depending on the type of GPS device you are using and how you connect it to your computer. On Linux / Unix systems, your GPS should typically show up as a character device, i.e., you will find an entry in the /dev folder corresponding to your GPS device. Again, the file name depends on the type and connection method of your GPS receiver. See [[Connecting a GPS receiver]] for details.
Most GPS receiver will output the position in [[NMEA]] format, which can be used directly in Navit or using a GPS daemon program such as **gpsd**. A simple way to test whether your GPS receiver works and outputs NMEA data is to dump its output to a console. For example, if your GPS receiver can be found at /dev/rfcomm0, you can dump its output using