{"id":74,"date":"2009-02-20T12:09:32","date_gmt":"2009-02-20T11:09:32","guid":{"rendered":"http:\/\/cris.netsons.org\/?p=74"},"modified":"2009-03-24T07:50:54","modified_gmt":"2009-03-24T06:50:54","slug":"starting-gpsd-automatically-with-a-bluetooth-gps","status":"publish","type":"post","link":"https:\/\/cris.bytesnblades.net\/it\/2009\/02\/20\/starting-gpsd-automatically-with-a-bluetooth-gps\/","title":{"rendered":"(English) Starting gpsd automatically with a bluetooth GPS"},"content":{"rendered":"

Purtroppo questo articolo \u00e8 disponibile soltanto in English<\/a>.<\/p>

I’ve lost a bit time trying to have gpsd starting automatically upon connection of my bluetooth GPS receiver (Holux M-1000) and finally I’ve found a solution that is probably not the best but is enough good for me.
\n<\/p>\n

At first I had to struggle against the quite completely broken bluetooth support of ubuntu intrepid.
\nProvidentially<\/em> the Blueman project<\/a> is keeping a PPA repository<\/a> with the last version of their fantastic Bluetooth Manager<\/em> and up to date bluez packages.<\/p>\n

Installing the Blueman manager<\/em> and their bluez packages solved the most of my problems: thank you guys!<\/p>\n

The gpsd distribution comes already with a set of udev rules (see \/etc\/udev\/rules.d\/50-gpsd.rules<\/em>) that match some devices by vendor and product id and a set of hotplug scripts that are invoked upon detection of devices to start and stop the gpsd daemon. Sadly this seems to work only with serial or usb devices as the sysfs subsystem does not seem to keep any of such information for my blootooth device.<\/p>\n

But let’s see what happens when the device is attached to a serial port …
\nRunning udevadm monitor –udev<\/em> reveals the following events:<\/p>\n

add  \/devices\/pci0000:00\/0000:00:02.1\/usb2\/2-1\/2-1.4\/2-1.4:1.0\/bluetooth\/hci0\/hci0:43 (bluetooth)\r\nadd  \/devices\/virtual\/tty\/rfcomm0 (tty)\r\nmove \/devices\/pci0000:00\/0000:00:02.1\/usb2\/2-1\/2-1.4\/2-1.4:1.0\/bluetooth\/hci0\/hci0:43\/rfcomm0 (tty)<\/code><\/pre>\n
so the device is recognized and a virtual serial port is created and relocated under the bluetooth device sub-tree.<\/p>\n
Checking the information of the relocated rfcomm device with udevadm info -a -p \/devices\/…<\/em> reveals that it inherits the address of the gps device as attribute:<\/p>\n
looking at device '\/devices\/pci0000:00\/0000:00:02.1\/...\/bluetooth\/hci0\/hci0:43\/rfcomm0':\r\n   KERNEL==\"rfcomm0\"\r\n   SUBSYSTEM==\"tty\"\r\n   DRIVER==\"\"\r\n   ATTR{address}==\"00:A6:01:39:D0:A0\"\r\n   ATTR{channel}==\"1\"<\/code><\/pre>\n
Good! The device address can be used to write a rule for udev!<\/p>\n
At this point I’ve got fresh versions of the GPSd’s<\/a> hotplug scripts as the ones that come with ubuntu are a bit outdated and broken.
\nThese scripts are available on the GPSd’s project subversion<\/a>: I’ve got gpsd.hotplug<\/em> and gpsd.hotplug.wrapper<\/em> from the trunk and copied them to \/lib\/udev<\/em>.<\/p>\n
So I’ve added the following two rules to \/etc\/udev\/rules.d\/50-gpsd.rules<\/em><\/p>\n
ACTION==\"add\", SUBSYSTEM==\"tty\", ATTR{address}==\"00:A6:01:39:D0:A0\", SYMLINK=\"gps%n\", \\\r\n                    ENV{HOLUX_M1000}=\"present\", RUN+=\"\/lib\/udev\/gpsd.hotplug.wrapper\"\r\nACTION==\"remove\", SUBSYSTEM==\"tty\", ENV{HOLUX_M1000}==\"present\", RUN+=\"\/lib\/udev\/gpsd.hotplug.wrapper\"<\/code><\/pre>\n
Note how the ADD<\/em> rule sets an environment variable ENV{HOLUX_M1000}<\/em> that is used for matching the REMOVE<\/em> event.<\/p>\n
I’ve reloaded the udev rules with udevadm control reload_rules<\/em> … et voil\u00e0 … gpsd starts automatically when connecting my gps device.<\/p>","protected":false},"excerpt":{"rendered":"
Purtroppo questo articolo \u00e8 disponibile soltanto in English.I’ve lost a bit time trying to have gpsd starting automatically upon connection of my bluetooth GPS receiver (Holux M-1000) and finally I’ve found a solution that is probably not the best but … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[49,4],"tags":[35,4,34,36],"class_list":["post-74","post","type-post","status-publish","format-standard","hentry","category-experiments","category-tips","tag-bluetooth","tag-tips","tag-ubuntu","tag-udev"],"_links":{"self":[{"href":"https:\/\/cris.bytesnblades.net\/it\/wp-json\/wp\/v2\/posts\/74","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cris.bytesnblades.net\/it\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cris.bytesnblades.net\/it\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cris.bytesnblades.net\/it\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/cris.bytesnblades.net\/it\/wp-json\/wp\/v2\/comments?post=74"}],"version-history":[{"count":55,"href":"https:\/\/cris.bytesnblades.net\/it\/wp-json\/wp\/v2\/posts\/74\/revisions"}],"predecessor-version":[{"id":668,"href":"https:\/\/cris.bytesnblades.net\/it\/wp-json\/wp\/v2\/posts\/74\/revisions\/668"}],"wp:attachment":[{"href":"https:\/\/cris.bytesnblades.net\/it\/wp-json\/wp\/v2\/media?parent=74"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cris.bytesnblades.net\/it\/wp-json\/wp\/v2\/categories?post=74"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cris.bytesnblades.net\/it\/wp-json\/wp\/v2\/tags?post=74"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}