navigps
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
navigps [2008/02/10 22:59] – 80.229.30.161 | navigps [2009/09/10 15:53] – AqcjRbVp 220.181.53.233 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== NaviGPS with Linux ====== | + | NaIe0F |
- | + | ||
- | {{ http:// | + | |
- | //WORK IN PROGRESS// | + | |
- | + | ||
- | The device is known as "Scytex Navi BT GPS" or " | + | |
- | + | ||
- | + | ||
- | * [[http://www.locosystech.com/support.php? | + | |
- | * [[http:// | + | |
- | * [[http:// | + | |
- | * [[http:// | + | |
- | + | ||
- | + | ||
- | ===== USB Connection ===== | + | |
- | + | ||
- | The Navi GPS uses a builtin Prolific Serial to USB converter, supported by the Linux Kernel. | + | |
- | + | ||
- | Device Drivers | + | |
- | USB support | + | |
- | USB Serial Converter support | + | |
- | | + | |
- | + | ||
- | This is displayed in [[man> | + | |
- | + | ||
- | <code> | + | |
- | usb 5-5.1: new full speed USB device using ehci_hcd and address 5 | + | |
- | usbcore: registered new driver usbserial | + | |
- | drivers/ | + | |
- | usbcore: registered new driver usbserial_generic | + | |
- | drivers/ | + | |
- | drivers/ | + | |
- | pl2303 5-5.1:1.0: pl2303 converter detected | + | |
- | usb 5-5.1: pl2303 converter now attached to ttyUSB0 | + | |
- | usbcore: registered new driver pl2303 | + | |
- | drivers/ | + | |
- | </ | + | |
- | + | ||
- | ===== Live GPS data processing ===== | + | |
- | + | ||
- | The best way to directly use live data provided by the gps is to use the [[man> | + | |
- | + | ||
- | $> sudo aptitude install gpsd gpsd-clients | + | |
- | + | ||
- | Because I just wanted to test it, not really use it on my desktop PC I didn't set the connector port and denied the start on boot question. | + | |
- | + | ||
- | Now connect the device and start the daemon: | + | |
- | + | ||
- | $> gpsd -p / | + | |
- | + | ||
- | To visualize the data made available by the daemon use the [[man> | + | |
- | + | ||
- | If you have trouble getting the NaviGPS to talk to gpsd using the NMEA protocol, then switch to the Binary protocol, which gpsd also understands. | + | |
- | + | ||
- | + | ||
- | ===== Downloading Data ===== | + | |
- | + | ||
- | The Navi GPS comes with a Windows tool to download routes, waypoints and track data. To download the data you need to switch the device into " | + | |
- | + | ||
- | Locosys made specifications for the [[Navilink]] protocol available and a first [[http://www.splitbrain.org/blog/ | + | |
- | + | ||
- | ===== DataLogging to SD-Card ===== | + | |
- | + | ||
- | The NaviGPS handles SD-Cards up to 2GB. When the card is formatted in the device 4 primary partitions are created but only the first one is used and formatted with FAT16. All data is stored inside a '' | + | |
- | + | ||
- | > v1.4 firmware formats the card without a partition table. If you try to display the partition table with fdisk on Linux it will show you four invalid partitions, although the first is close to being usable. --- //[[johnc+navigps@kirriwa.net|johnc]] 2007-05-18 13:04 UTC+10// | + | |
- | + | ||
- | You can log the following [[http:// | + | |
- | + | ||
- | ^short^ Description | + | |
- | | GGA | Global Positioning System Fix Data | 1 sec | | + | |
- | | GLL | Geographic position, latitude / longitude | + | |
- | | GSA | GPS DOP and active satellites | + | |
- | | GSV | GPS Satellites in view | 5 sec | | + | |
- | | RMC | Recommended minimum specific GPS/Transit data | 1 sec | | + | |
- | | VTG | Track made good and ground speed | off | | + | |
- | | ZDA | Date & Time | off | | + | |
- | + | ||
- | As you can see it does not log Date and Time by default. | + | |
- | > I was able to enable the logging of these options on my device in the settings. | + | |
- | + | ||
- | However this info can be reconstructed from the filename. Simply add a [[http://aprs.gids.nl/nmea/# | + | |
- | + | ||
- | $--ZDA, | + | |
- | + | ||
- | You then can process the data with [[man> | + | |
- | + | ||
- | $> gpsbabel -t -i nmea -f 20060816_081520.TXT -o gpx -F 20060816_081520.gpx | + | |
- | + | ||
- | This will produce an XML file in the popular [[http:// | + | |
- | + | ||
- | ===== Bluetooth ===== | + | |
- | + | ||
- | Make sure you have Bluetooth support compiled into your Kernel. Now activate Bluetooth in the Settingsmenu and install the following packages: | + | |
- | + | ||
- | * bluez-pin | + | |
- | * bluez-util | + | |
- | * gpsd | + | |
- | + | ||
- | (these are Debian-Packagenames) | + | |
- | + | ||
- | Now edit your / | + | |
- | < | + | |
- | # | + | |
- | # HCI daemon configuration file. | + | |
- | # | + | |
- | + | ||
- | # HCId options | + | |
- | options { | + | |
- | # Automatically initialize new devices | + | |
- | autoinit yes; | + | |
- | + | ||
- | # Security Manager mode | + | |
- | # none - Security manager disabled | + | |
- | # auto - Use local PIN for incoming connections | + | |
- | # user - Always ask user for a PIN | + | |
- | # | + | |
- | security user; | + | |
- | + | ||
- | # Pairing mode | + | |
- | # | + | |
- | # multi - Allow pairing with already paired devices | + | |
- | # | + | |
- | pairing multi; | + | |
- | + | ||
- | # PIN helper | + | |
- | pin_helper / | + | |
- | + | ||
- | # D-Bus PIN helper | + | |
- | # | + | |
- | } | + | |
- | + | ||
- | # Default settings for HCI devices | + | |
- | device { | + | |
- | # Local device name | + | |
- | # %d - device id | + | |
- | # %h - host name | + | |
- | name "Your Device Name"; | + | |
- | + | ||
- | # Local device class | + | |
- | class 0x3e0100; | + | |
- | + | ||
- | # Default packet type | + | |
- | #pkt_type DH1, | + | |
- | + | ||
- | # Inquiry and Page scan | + | |
- | iscan enable; pscan enable; | + | |
- | + | ||
- | # Default link mode | + | |
- | # | + | |
- | # | + | |
- | # | + | |
- | # deny role switch on outgoing connections | + | |
- | lm accept; | + | |
- | + | ||
- | # Default link policy | + | |
- | # | + | |
- | # | + | |
- | # | + | |
- | # | + | |
- | # | + | |
- | lp rswitch, | + | |
- | + | ||
- | # Authentication and Encryption (Security Mode 3) | + | |
- | auth enable; | + | |
- | #encrypt enable; | + | |
- | } | + | |
- | + | ||
- | </ | + | |
- | + | ||
- | Now restart your bluetooth-services ("/ | + | |
- | <code bash> | + | |
- | ~$ hcitool scan | + | |
- | + | ||
- | Scanning ... | + | |
- | xx: | + | |
- | + | ||
- | </ | + | |
- | + | ||
- | Now we got the MAC-Address of the device. For a connection we do also need the channel, but " | + | |
- | i figured out that my naviGPS communicates on channel 1. | + | |
- | + | ||
- | + | ||
- | ... to be continued | + |
navigps.txt · Last modified: 2009/09/10 18:31 by andi