How can I get the GPS receiver BU-353 working on Ubuntu?











up vote
7
down vote

favorite
1












I have a GPS receiver BU-353 with USB interface and I'm trying to get it working under Ubuntu.



I ran gpsd -n -N -D 2 /dev/ttyUSB0, and got this output:



gpsd: launching (Version 2.94)
gpsd: listening on port gpsd
gpsd: running with effective group ID 1000
gpsd: running with effective user ID 1000
gpsd: opening GPS data source type 3 at '/dev/ttyUSB0'
gpsd: speed 38400, 8N1
gpsd: Garmin: garmin_gps Linux USB module not active.
gpsd: speed 9600, 8O1
gpsd: speed 38400, 8N1
gpsd: gpsd_activate(): opened GPS (fd 6)
gpsd: speed 4800, 8N1
gpsd: NTPD ntpd_link_activate: 0
gpsd: /dev/ttyUSB0 identified as type SiRF binary (2.687608 sec @ 4800bps)
gpsd: detaching 127.0.0.1 (sub 1, fd 8) in detach_client
gpsd: detaching 127.0.0.1 (sub 1, fd 8) in detach_client


After this I started tangoGPS, which said no GPS and no GPSD found.










share|improve this question




























    up vote
    7
    down vote

    favorite
    1












    I have a GPS receiver BU-353 with USB interface and I'm trying to get it working under Ubuntu.



    I ran gpsd -n -N -D 2 /dev/ttyUSB0, and got this output:



    gpsd: launching (Version 2.94)
    gpsd: listening on port gpsd
    gpsd: running with effective group ID 1000
    gpsd: running with effective user ID 1000
    gpsd: opening GPS data source type 3 at '/dev/ttyUSB0'
    gpsd: speed 38400, 8N1
    gpsd: Garmin: garmin_gps Linux USB module not active.
    gpsd: speed 9600, 8O1
    gpsd: speed 38400, 8N1
    gpsd: gpsd_activate(): opened GPS (fd 6)
    gpsd: speed 4800, 8N1
    gpsd: NTPD ntpd_link_activate: 0
    gpsd: /dev/ttyUSB0 identified as type SiRF binary (2.687608 sec @ 4800bps)
    gpsd: detaching 127.0.0.1 (sub 1, fd 8) in detach_client
    gpsd: detaching 127.0.0.1 (sub 1, fd 8) in detach_client


    After this I started tangoGPS, which said no GPS and no GPSD found.










    share|improve this question


























      up vote
      7
      down vote

      favorite
      1









      up vote
      7
      down vote

      favorite
      1






      1





      I have a GPS receiver BU-353 with USB interface and I'm trying to get it working under Ubuntu.



      I ran gpsd -n -N -D 2 /dev/ttyUSB0, and got this output:



      gpsd: launching (Version 2.94)
      gpsd: listening on port gpsd
      gpsd: running with effective group ID 1000
      gpsd: running with effective user ID 1000
      gpsd: opening GPS data source type 3 at '/dev/ttyUSB0'
      gpsd: speed 38400, 8N1
      gpsd: Garmin: garmin_gps Linux USB module not active.
      gpsd: speed 9600, 8O1
      gpsd: speed 38400, 8N1
      gpsd: gpsd_activate(): opened GPS (fd 6)
      gpsd: speed 4800, 8N1
      gpsd: NTPD ntpd_link_activate: 0
      gpsd: /dev/ttyUSB0 identified as type SiRF binary (2.687608 sec @ 4800bps)
      gpsd: detaching 127.0.0.1 (sub 1, fd 8) in detach_client
      gpsd: detaching 127.0.0.1 (sub 1, fd 8) in detach_client


      After this I started tangoGPS, which said no GPS and no GPSD found.










      share|improve this question















      I have a GPS receiver BU-353 with USB interface and I'm trying to get it working under Ubuntu.



      I ran gpsd -n -N -D 2 /dev/ttyUSB0, and got this output:



      gpsd: launching (Version 2.94)
      gpsd: listening on port gpsd
      gpsd: running with effective group ID 1000
      gpsd: running with effective user ID 1000
      gpsd: opening GPS data source type 3 at '/dev/ttyUSB0'
      gpsd: speed 38400, 8N1
      gpsd: Garmin: garmin_gps Linux USB module not active.
      gpsd: speed 9600, 8O1
      gpsd: speed 38400, 8N1
      gpsd: gpsd_activate(): opened GPS (fd 6)
      gpsd: speed 4800, 8N1
      gpsd: NTPD ntpd_link_activate: 0
      gpsd: /dev/ttyUSB0 identified as type SiRF binary (2.687608 sec @ 4800bps)
      gpsd: detaching 127.0.0.1 (sub 1, fd 8) in detach_client
      gpsd: detaching 127.0.0.1 (sub 1, fd 8) in detach_client


      After this I started tangoGPS, which said no GPS and no GPSD found.







      usb gps






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Dec 12 at 9:23









      Zanna

      49.4k13128236




      49.4k13128236










      asked Mar 16 '11 at 5:56









      Parimal N

      1682410




      1682410






















          2 Answers
          2






          active

          oldest

          votes

















          up vote
          6
          down vote













          BU-353 is known to work with gpsd.




          1. Try the -b flag (for example, gpsd -b /dev/ttyUSB0)



          2. Open a separate terminal window and run gpsmon (included in the 'gpsd-clients' package) to check gpsd output. Restart gpsmon each time you restart gpsd.



            Could tango be starting too soon? The dongle requires a few seconds to sort out the signals, identify satellites, and calculate a fix; udev requires a few seconds to start gpsd, which in turn requires a few seconds to probe the dongle (which may not be ready yet) and begin broadcasting useful information when the data stream finally begins. gpsmon can help diagnose that problem, too.




          3. If there's no gpsd output, then do a more detailed check. Do the following steps in order to test the dongle, the kernel module, the mount, the device node, and gpsd:




            • Unplug the USB dongle and kill gpsd (sudo pkill gpsd). Wait 10 seconds for /dev/ttyUSB0 to be freed.

            • Plug the USB dongle back in and wait 10 seconds.

            • Check dmesg | tail -n 5 to verify the dongle was really mounted to /dev/ttyUSB0. If it doesn't mount, then you're missing a kernel module (from your description, that's unlikely). Sometimes it gets mounted to /dev/ttyUSB1 if 0 isn't free!

            • See if udev recognized the dongle and started gpsd (ps -e | grep gpsd). If not, then you have a udev rules issue, and you must start gpsd manually with gpsd /dev/ttyUSB0


            • Once gpsd is running, check for dongle output (dongle output = gpsd input). Try cat /dev/ttyUSB0 (stop it with CTRL+c). If that fails, then try resetting the baud rate to 4800:



              pkill gpsd
              stty 4800 > /dev/ttyUSB0
              gpsd -b /dev/ttyUSB0
              cat /dev/ttyUSB0 # CTRL+c to stop


            • If you have have good dongle output (=gpsd input), open a second terminal window and try either gpsmon or cgps to test gpsd output.

            • Finally, now that you have good dongle output and good gpsd output, try tangoGPS.








          share|improve this answer






























            up vote
            1
            down vote













            I was having a similar problem. I did everything here and still couldn't get it to work in openCPN. I stumbled on to another forum that said to try changing the default settings for gpsd at /etc/default/gpsd to this.



            # Default settings for the gpsd init script and the hotplug wrapper.

            # Start the gpsd daemon automatically at boot time
            START_DAEMON="false"

            # Use USB hotplugging to add new USB devices automatically to the daemon
            USBAUTO="true"

            # Devices gpsd should collect to at boot time.
            # They need to be read/writeable, either by user gpsd or the group dialout.
            DEVICES="/dev/ttyUSB0"

            # Other options you want to pass to gpsd
            GPSD_OPTIONS="-n -G -b"
            GPSD_SOCKET="/var/run/gpsd.sock"
            #end of file gpsd


            to my surprise it worked.






            share|improve this answer























              Your Answer








              StackExchange.ready(function() {
              var channelOptions = {
              tags: "".split(" "),
              id: "89"
              };
              initTagRenderer("".split(" "), "".split(" "), channelOptions);

              StackExchange.using("externalEditor", function() {
              // Have to fire editor after snippets, if snippets enabled
              if (StackExchange.settings.snippets.snippetsEnabled) {
              StackExchange.using("snippets", function() {
              createEditor();
              });
              }
              else {
              createEditor();
              }
              });

              function createEditor() {
              StackExchange.prepareEditor({
              heartbeatType: 'answer',
              convertImagesToLinks: true,
              noModals: true,
              showLowRepImageUploadWarning: true,
              reputationToPostImages: 10,
              bindNavPrevention: true,
              postfix: "",
              imageUploader: {
              brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
              contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
              allowUrls: true
              },
              onDemand: true,
              discardSelector: ".discard-answer"
              ,immediatelyShowMarkdownHelp:true
              });


              }
              });














              draft saved

              draft discarded


















              StackExchange.ready(
              function () {
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f30569%2fhow-can-i-get-the-gps-receiver-bu-353-working-on-ubuntu%23new-answer', 'question_page');
              }
              );

              Post as a guest















              Required, but never shown

























              2 Answers
              2






              active

              oldest

              votes








              2 Answers
              2






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes








              up vote
              6
              down vote













              BU-353 is known to work with gpsd.




              1. Try the -b flag (for example, gpsd -b /dev/ttyUSB0)



              2. Open a separate terminal window and run gpsmon (included in the 'gpsd-clients' package) to check gpsd output. Restart gpsmon each time you restart gpsd.



                Could tango be starting too soon? The dongle requires a few seconds to sort out the signals, identify satellites, and calculate a fix; udev requires a few seconds to start gpsd, which in turn requires a few seconds to probe the dongle (which may not be ready yet) and begin broadcasting useful information when the data stream finally begins. gpsmon can help diagnose that problem, too.




              3. If there's no gpsd output, then do a more detailed check. Do the following steps in order to test the dongle, the kernel module, the mount, the device node, and gpsd:




                • Unplug the USB dongle and kill gpsd (sudo pkill gpsd). Wait 10 seconds for /dev/ttyUSB0 to be freed.

                • Plug the USB dongle back in and wait 10 seconds.

                • Check dmesg | tail -n 5 to verify the dongle was really mounted to /dev/ttyUSB0. If it doesn't mount, then you're missing a kernel module (from your description, that's unlikely). Sometimes it gets mounted to /dev/ttyUSB1 if 0 isn't free!

                • See if udev recognized the dongle and started gpsd (ps -e | grep gpsd). If not, then you have a udev rules issue, and you must start gpsd manually with gpsd /dev/ttyUSB0


                • Once gpsd is running, check for dongle output (dongle output = gpsd input). Try cat /dev/ttyUSB0 (stop it with CTRL+c). If that fails, then try resetting the baud rate to 4800:



                  pkill gpsd
                  stty 4800 > /dev/ttyUSB0
                  gpsd -b /dev/ttyUSB0
                  cat /dev/ttyUSB0 # CTRL+c to stop


                • If you have have good dongle output (=gpsd input), open a second terminal window and try either gpsmon or cgps to test gpsd output.

                • Finally, now that you have good dongle output and good gpsd output, try tangoGPS.








              share|improve this answer



























                up vote
                6
                down vote













                BU-353 is known to work with gpsd.




                1. Try the -b flag (for example, gpsd -b /dev/ttyUSB0)



                2. Open a separate terminal window and run gpsmon (included in the 'gpsd-clients' package) to check gpsd output. Restart gpsmon each time you restart gpsd.



                  Could tango be starting too soon? The dongle requires a few seconds to sort out the signals, identify satellites, and calculate a fix; udev requires a few seconds to start gpsd, which in turn requires a few seconds to probe the dongle (which may not be ready yet) and begin broadcasting useful information when the data stream finally begins. gpsmon can help diagnose that problem, too.




                3. If there's no gpsd output, then do a more detailed check. Do the following steps in order to test the dongle, the kernel module, the mount, the device node, and gpsd:




                  • Unplug the USB dongle and kill gpsd (sudo pkill gpsd). Wait 10 seconds for /dev/ttyUSB0 to be freed.

                  • Plug the USB dongle back in and wait 10 seconds.

                  • Check dmesg | tail -n 5 to verify the dongle was really mounted to /dev/ttyUSB0. If it doesn't mount, then you're missing a kernel module (from your description, that's unlikely). Sometimes it gets mounted to /dev/ttyUSB1 if 0 isn't free!

                  • See if udev recognized the dongle and started gpsd (ps -e | grep gpsd). If not, then you have a udev rules issue, and you must start gpsd manually with gpsd /dev/ttyUSB0


                  • Once gpsd is running, check for dongle output (dongle output = gpsd input). Try cat /dev/ttyUSB0 (stop it with CTRL+c). If that fails, then try resetting the baud rate to 4800:



                    pkill gpsd
                    stty 4800 > /dev/ttyUSB0
                    gpsd -b /dev/ttyUSB0
                    cat /dev/ttyUSB0 # CTRL+c to stop


                  • If you have have good dongle output (=gpsd input), open a second terminal window and try either gpsmon or cgps to test gpsd output.

                  • Finally, now that you have good dongle output and good gpsd output, try tangoGPS.








                share|improve this answer

























                  up vote
                  6
                  down vote










                  up vote
                  6
                  down vote









                  BU-353 is known to work with gpsd.




                  1. Try the -b flag (for example, gpsd -b /dev/ttyUSB0)



                  2. Open a separate terminal window and run gpsmon (included in the 'gpsd-clients' package) to check gpsd output. Restart gpsmon each time you restart gpsd.



                    Could tango be starting too soon? The dongle requires a few seconds to sort out the signals, identify satellites, and calculate a fix; udev requires a few seconds to start gpsd, which in turn requires a few seconds to probe the dongle (which may not be ready yet) and begin broadcasting useful information when the data stream finally begins. gpsmon can help diagnose that problem, too.




                  3. If there's no gpsd output, then do a more detailed check. Do the following steps in order to test the dongle, the kernel module, the mount, the device node, and gpsd:




                    • Unplug the USB dongle and kill gpsd (sudo pkill gpsd). Wait 10 seconds for /dev/ttyUSB0 to be freed.

                    • Plug the USB dongle back in and wait 10 seconds.

                    • Check dmesg | tail -n 5 to verify the dongle was really mounted to /dev/ttyUSB0. If it doesn't mount, then you're missing a kernel module (from your description, that's unlikely). Sometimes it gets mounted to /dev/ttyUSB1 if 0 isn't free!

                    • See if udev recognized the dongle and started gpsd (ps -e | grep gpsd). If not, then you have a udev rules issue, and you must start gpsd manually with gpsd /dev/ttyUSB0


                    • Once gpsd is running, check for dongle output (dongle output = gpsd input). Try cat /dev/ttyUSB0 (stop it with CTRL+c). If that fails, then try resetting the baud rate to 4800:



                      pkill gpsd
                      stty 4800 > /dev/ttyUSB0
                      gpsd -b /dev/ttyUSB0
                      cat /dev/ttyUSB0 # CTRL+c to stop


                    • If you have have good dongle output (=gpsd input), open a second terminal window and try either gpsmon or cgps to test gpsd output.

                    • Finally, now that you have good dongle output and good gpsd output, try tangoGPS.








                  share|improve this answer














                  BU-353 is known to work with gpsd.




                  1. Try the -b flag (for example, gpsd -b /dev/ttyUSB0)



                  2. Open a separate terminal window and run gpsmon (included in the 'gpsd-clients' package) to check gpsd output. Restart gpsmon each time you restart gpsd.



                    Could tango be starting too soon? The dongle requires a few seconds to sort out the signals, identify satellites, and calculate a fix; udev requires a few seconds to start gpsd, which in turn requires a few seconds to probe the dongle (which may not be ready yet) and begin broadcasting useful information when the data stream finally begins. gpsmon can help diagnose that problem, too.




                  3. If there's no gpsd output, then do a more detailed check. Do the following steps in order to test the dongle, the kernel module, the mount, the device node, and gpsd:




                    • Unplug the USB dongle and kill gpsd (sudo pkill gpsd). Wait 10 seconds for /dev/ttyUSB0 to be freed.

                    • Plug the USB dongle back in and wait 10 seconds.

                    • Check dmesg | tail -n 5 to verify the dongle was really mounted to /dev/ttyUSB0. If it doesn't mount, then you're missing a kernel module (from your description, that's unlikely). Sometimes it gets mounted to /dev/ttyUSB1 if 0 isn't free!

                    • See if udev recognized the dongle and started gpsd (ps -e | grep gpsd). If not, then you have a udev rules issue, and you must start gpsd manually with gpsd /dev/ttyUSB0


                    • Once gpsd is running, check for dongle output (dongle output = gpsd input). Try cat /dev/ttyUSB0 (stop it with CTRL+c). If that fails, then try resetting the baud rate to 4800:



                      pkill gpsd
                      stty 4800 > /dev/ttyUSB0
                      gpsd -b /dev/ttyUSB0
                      cat /dev/ttyUSB0 # CTRL+c to stop


                    • If you have have good dongle output (=gpsd input), open a second terminal window and try either gpsmon or cgps to test gpsd output.

                    • Finally, now that you have good dongle output and good gpsd output, try tangoGPS.









                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited Dec 12 at 9:25









                  Zanna

                  49.4k13128236




                  49.4k13128236










                  answered Dec 6 '11 at 5:46









                  user535733

                  7,53222941




                  7,53222941
























                      up vote
                      1
                      down vote













                      I was having a similar problem. I did everything here and still couldn't get it to work in openCPN. I stumbled on to another forum that said to try changing the default settings for gpsd at /etc/default/gpsd to this.



                      # Default settings for the gpsd init script and the hotplug wrapper.

                      # Start the gpsd daemon automatically at boot time
                      START_DAEMON="false"

                      # Use USB hotplugging to add new USB devices automatically to the daemon
                      USBAUTO="true"

                      # Devices gpsd should collect to at boot time.
                      # They need to be read/writeable, either by user gpsd or the group dialout.
                      DEVICES="/dev/ttyUSB0"

                      # Other options you want to pass to gpsd
                      GPSD_OPTIONS="-n -G -b"
                      GPSD_SOCKET="/var/run/gpsd.sock"
                      #end of file gpsd


                      to my surprise it worked.






                      share|improve this answer



























                        up vote
                        1
                        down vote













                        I was having a similar problem. I did everything here and still couldn't get it to work in openCPN. I stumbled on to another forum that said to try changing the default settings for gpsd at /etc/default/gpsd to this.



                        # Default settings for the gpsd init script and the hotplug wrapper.

                        # Start the gpsd daemon automatically at boot time
                        START_DAEMON="false"

                        # Use USB hotplugging to add new USB devices automatically to the daemon
                        USBAUTO="true"

                        # Devices gpsd should collect to at boot time.
                        # They need to be read/writeable, either by user gpsd or the group dialout.
                        DEVICES="/dev/ttyUSB0"

                        # Other options you want to pass to gpsd
                        GPSD_OPTIONS="-n -G -b"
                        GPSD_SOCKET="/var/run/gpsd.sock"
                        #end of file gpsd


                        to my surprise it worked.






                        share|improve this answer

























                          up vote
                          1
                          down vote










                          up vote
                          1
                          down vote









                          I was having a similar problem. I did everything here and still couldn't get it to work in openCPN. I stumbled on to another forum that said to try changing the default settings for gpsd at /etc/default/gpsd to this.



                          # Default settings for the gpsd init script and the hotplug wrapper.

                          # Start the gpsd daemon automatically at boot time
                          START_DAEMON="false"

                          # Use USB hotplugging to add new USB devices automatically to the daemon
                          USBAUTO="true"

                          # Devices gpsd should collect to at boot time.
                          # They need to be read/writeable, either by user gpsd or the group dialout.
                          DEVICES="/dev/ttyUSB0"

                          # Other options you want to pass to gpsd
                          GPSD_OPTIONS="-n -G -b"
                          GPSD_SOCKET="/var/run/gpsd.sock"
                          #end of file gpsd


                          to my surprise it worked.






                          share|improve this answer














                          I was having a similar problem. I did everything here and still couldn't get it to work in openCPN. I stumbled on to another forum that said to try changing the default settings for gpsd at /etc/default/gpsd to this.



                          # Default settings for the gpsd init script and the hotplug wrapper.

                          # Start the gpsd daemon automatically at boot time
                          START_DAEMON="false"

                          # Use USB hotplugging to add new USB devices automatically to the daemon
                          USBAUTO="true"

                          # Devices gpsd should collect to at boot time.
                          # They need to be read/writeable, either by user gpsd or the group dialout.
                          DEVICES="/dev/ttyUSB0"

                          # Other options you want to pass to gpsd
                          GPSD_OPTIONS="-n -G -b"
                          GPSD_SOCKET="/var/run/gpsd.sock"
                          #end of file gpsd


                          to my surprise it worked.







                          share|improve this answer














                          share|improve this answer



                          share|improve this answer








                          edited Dec 12 at 9:25









                          Zanna

                          49.4k13128236




                          49.4k13128236










                          answered Sep 2 '17 at 18:28









                          user273913

                          101116




                          101116






























                              draft saved

                              draft discarded




















































                              Thanks for contributing an answer to Ask Ubuntu!


                              • Please be sure to answer the question. Provide details and share your research!

                              But avoid



                              • Asking for help, clarification, or responding to other answers.

                              • Making statements based on opinion; back them up with references or personal experience.


                              To learn more, see our tips on writing great answers.





                              Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                              Please pay close attention to the following guidance:


                              • Please be sure to answer the question. Provide details and share your research!

                              But avoid



                              • Asking for help, clarification, or responding to other answers.

                              • Making statements based on opinion; back them up with references or personal experience.


                              To learn more, see our tips on writing great answers.




                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function () {
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f30569%2fhow-can-i-get-the-gps-receiver-bu-353-working-on-ubuntu%23new-answer', 'question_page');
                              }
                              );

                              Post as a guest















                              Required, but never shown





















































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown

































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown







                              Popular posts from this blog

                              數位音樂下載

                              When can things happen in Etherscan, such as the picture below?

                              格利澤436b