Ygthkb

Is it possible to map from a parameter to a trajectory?

How can guns be countered by melee combat without raw-ability or exceptional explanations?

Would water spill from a bowl in a Bag of Holding?

"I showed the monkey himself in the mirror". Why is this sentence grammatical?

Does Plato's "Ring of Gyges" have a corrupting influence on its wearer?

What's the reason that we have a different number of days each month?

In a post-apocalypse world, with no power and few survivors, would Satnav still work?

Why is Shelob considered evil?

Does copper wire need to say it's copper?

Lubuntu 18.10 File Manager: How to view directory tree structure?

Modern Algebraic Geometry and Analytic Number Theory

How can I deduce the power of a capacitor from its datasheet?

How to get a 2D Plot from a 3D Listplot?

How to know if I am a 'Real Developer'

Why don't you get burned by the wood benches in a sauna?

How unreachable are Jupiter's moons from Mars with the technology developed for going to Mars?

I am a giant among ants

Coworker asking me to not bring cakes due to self control issue. What should I do?

Why did Ylvis use "go" instead of "say" in phrases like "Dog goes 'woof'"?

Promise.all returning empty objects

Protagonist constantly has to have long words explained to her. Will this get tedious?

A sequence of orthogonal projection in Hilbert space

Isn't a semicolon (';') needed after a function declaration in C++?

GPSD issues on 16.4

GPSD issues on 16.4

How do I allow non-root access to /ttyUSB0 on 12.04?Issues with alternate Windows software and WineMinidlna Directory IssuesDpkg keep saying that need to --configure -a while trying for network issues on Inspiron 1545lm-sensors issues with sensorsIssues with disabling iPv6 on Ubuntu 14.0.4How to fix configuration issues of an old kernel in order to make upgrade possible in Ubuntu?Ubuntu 18 user interface issues

1

I am completely stuck and tearing my hair out, trying to figure out, what is preventing gpsd from automatically connecting to an external GPS BU 353 dongle via USB and receiving data. I have the identical issue on both of my laptops, which are totally different hardware, so this is purely a software configuration issue.

I have managed to get gpsd working manually, using the following steps, but every time my machine is powered off, I must go through these steps again.

1. sudo killall gpsd



2. 
   

   Remove any sockets gpsd might have left behind, e.g.:

   
   
   

   sudo rm /var/run/gpsd.sock

   
   

3.Check the device path; dmesg - which shows PLU353

4. Ensure no other programs are using the device. none are listed

lsof -n | grep /dev/ttyUSB0 - There are none listed

5. 
   

   Manually launch gpsd

   
   
   

   sudo gpsd /dev/ttyUSB0 -F /var/run/gpsd.sock

   
   



6. xgps sees GPS output - so this Works

My best guesses are that gpsd needs to join a group or be given additional permissions, or alternatively, that it is an issue with udev configuration. But I am blundering about in the dark, just going round and round in circles making wild guesses.

If I could beg your assistance, could you provide simple steps and terminal commands, to get me out of this mess, I would be very very grateful.

I am on a boat and dependent on the solution for my navigation, so this is a serious issue for me, as I need instant access without having to mess around manually getting it to work, not good in a panic situation.....

I hope this is a simple issue, for someone who knows what they are doing, but I appear to be too stupid to figure it out myself.....

Thanking you very much in advance for any support that you can provide.

GEOFFREY

configuration

share|improve this question

edited 30 mins ago

waltinator

22.5k74169

asked 57 mins ago

Geoffrey-cGeoffrey-c

61

New contributor

Geoffrey-c is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Rather than lsof -n | grep /dev/ttyUSB0, I'd use sudo lsof /dev/ttyUSB0 - no need to grep
  
  – waltinator
  33 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Possible duplicate of How do I allow non-root access to /ttyUSB0 on 12.04?
  
  – N0rbert
  19 mins ago
  

  
  
  
  

add a comment | 

1

I am completely stuck and tearing my hair out, trying to figure out, what is preventing gpsd from automatically connecting to an external GPS BU 353 dongle via USB and receiving data. I have the identical issue on both of my laptops, which are totally different hardware, so this is purely a software configuration issue.

I have managed to get gpsd working manually, using the following steps, but every time my machine is powered off, I must go through these steps again.

1. sudo killall gpsd



2. 
   

   Remove any sockets gpsd might have left behind, e.g.:

   
   
   

   sudo rm /var/run/gpsd.sock

   
   

3.Check the device path; dmesg - which shows PLU353

4. Ensure no other programs are using the device. none are listed

lsof -n | grep /dev/ttyUSB0 - There are none listed

5. 
   

   Manually launch gpsd

   
   
   

   sudo gpsd /dev/ttyUSB0 -F /var/run/gpsd.sock

   
   



6. xgps sees GPS output - so this Works

My best guesses are that gpsd needs to join a group or be given additional permissions, or alternatively, that it is an issue with udev configuration. But I am blundering about in the dark, just going round and round in circles making wild guesses.

If I could beg your assistance, could you provide simple steps and terminal commands, to get me out of this mess, I would be very very grateful.

I am on a boat and dependent on the solution for my navigation, so this is a serious issue for me, as I need instant access without having to mess around manually getting it to work, not good in a panic situation.....

I hope this is a simple issue, for someone who knows what they are doing, but I appear to be too stupid to figure it out myself.....

Thanking you very much in advance for any support that you can provide.

GEOFFREY

configuration

share|improve this question

edited 30 mins ago

waltinator

22.5k74169

asked 57 mins ago

Geoffrey-cGeoffrey-c

61

New contributor

Geoffrey-c is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Rather than lsof -n | grep /dev/ttyUSB0, I'd use sudo lsof /dev/ttyUSB0 - no need to grep
  
  – waltinator
  33 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Possible duplicate of How do I allow non-root access to /ttyUSB0 on 12.04?
  
  – N0rbert
  19 mins ago
  

  
  
  
  

add a comment | 

I am completely stuck and tearing my hair out, trying to figure out, what is preventing gpsd from automatically connecting to an external GPS BU 353 dongle via USB and receiving data. I have the identical issue on both of my laptops, which are totally different hardware, so this is purely a software configuration issue.

I have managed to get gpsd working manually, using the following steps, but every time my machine is powered off, I must go through these steps again.

1. sudo killall gpsd



2. 
   

   Remove any sockets gpsd might have left behind, e.g.:

   
   
   

   sudo rm /var/run/gpsd.sock

   
   

3.Check the device path; dmesg - which shows PLU353

4. Ensure no other programs are using the device. none are listed

lsof -n | grep /dev/ttyUSB0 - There are none listed

5. 
   

   Manually launch gpsd

   
   
   

   sudo gpsd /dev/ttyUSB0 -F /var/run/gpsd.sock

   
   



6. xgps sees GPS output - so this Works

My best guesses are that gpsd needs to join a group or be given additional permissions, or alternatively, that it is an issue with udev configuration. But I am blundering about in the dark, just going round and round in circles making wild guesses.

If I could beg your assistance, could you provide simple steps and terminal commands, to get me out of this mess, I would be very very grateful.

I am on a boat and dependent on the solution for my navigation, so this is a serious issue for me, as I need instant access without having to mess around manually getting it to work, not good in a panic situation.....

I hope this is a simple issue, for someone who knows what they are doing, but I appear to be too stupid to figure it out myself.....

Thanking you very much in advance for any support that you can provide.

GEOFFREY

configuration

share|improve this question

edited 30 mins ago

waltinator

22.5k74169

asked 57 mins ago

Geoffrey-cGeoffrey-c

61

New contributor

Geoffrey-c is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share|improve this question

edited 30 mins ago

waltinator

22.5k74169

asked 57 mins ago

Geoffrey-cGeoffrey-c

61

New contributor

Geoffrey-c is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share|improve this question

edited 30 mins ago

waltinator

22.5k74169

asked 57 mins ago

Geoffrey-cGeoffrey-c

61

New contributor

Geoffrey-c is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

edited 30 mins ago

waltinator

22.5k74169

edited 30 mins ago

waltinator

22.5k74169

asked 57 mins ago

Geoffrey-cGeoffrey-c

61

New contributor

Geoffrey-c is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked 57 mins ago

Geoffrey-cGeoffrey-c

61

2 Answers
2

active

oldest

votes

3

You're correct - it is a group membership problem. First, see who owns the device:

ls -l /dev/ttyUSB0

On MY system, I don't have /dev/ttyUSB0, so I'll use /dev/ttyS0 instead

walt@bat:~(0)$ ls -l /dev/ttyS0

crw-rw---- 1 root dialout 4, 64 Feb 23 08:19 /dev/ttyS0

walt@bat:~(0)$ 

The output of the ls command shows that it's owned by root:dialout, and allows group access to the device.

Add your user to the dialout (or whatever is right for your system) group with:

sudo adduser $USER dialout

Then to make this group membership take effect, logout/login, OR newgrp dialout to start a shell with that group membership.

Check your group membership with /usr/bin/id.

share|improve this answer

answered 47 mins ago

waltinatorwaltinator

22.5k74169

add a comment | 

0

• open TCP port 2947 in your firewall


• in terminal, edit /etc/default/gpsd
  
  
  
  
  • sudo -H gedit /etc/default/gpsd
  
  
  • change DEVICES="" to DEVICES="/dev/ttyACM0"
    
  
  
  • save and quit gedit
  
  
  • sudo systemctl restart gpsd
  
  
  
  

gpsmon, cgps, and xgps will now work properly.

share|improve this answer

answered 18 mins ago

heynnemaheynnema

19.5k22158

add a comment | 

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',
autoActivateHeartbeat: false,
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
});


}
});

Geoffrey-c is a new contributor. Be nice, and check out our Code of Conduct.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1120881%2fgpsd-issues-on-16-4%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

3

You're correct - it is a group membership problem. First, see who owns the device:

ls -l /dev/ttyUSB0

On MY system, I don't have /dev/ttyUSB0, so I'll use /dev/ttyS0 instead

walt@bat:~(0)$ ls -l /dev/ttyS0

crw-rw---- 1 root dialout 4, 64 Feb 23 08:19 /dev/ttyS0

walt@bat:~(0)$ 

The output of the ls command shows that it's owned by root:dialout, and allows group access to the device.

Add your user to the dialout (or whatever is right for your system) group with:

sudo adduser $USER dialout

Then to make this group membership take effect, logout/login, OR newgrp dialout to start a shell with that group membership.

Check your group membership with /usr/bin/id.

share|improve this answer

answered 47 mins ago

waltinatorwaltinator

22.5k74169

add a comment | 

3

You're correct - it is a group membership problem. First, see who owns the device:

ls -l /dev/ttyUSB0

On MY system, I don't have /dev/ttyUSB0, so I'll use /dev/ttyS0 instead

walt@bat:~(0)$ ls -l /dev/ttyS0

crw-rw---- 1 root dialout 4, 64 Feb 23 08:19 /dev/ttyS0

walt@bat:~(0)$ 

The output of the ls command shows that it's owned by root:dialout, and allows group access to the device.

Add your user to the dialout (or whatever is right for your system) group with:

sudo adduser $USER dialout

Then to make this group membership take effect, logout/login, OR newgrp dialout to start a shell with that group membership.

Check your group membership with /usr/bin/id.

share|improve this answer

answered 47 mins ago

waltinatorwaltinator

22.5k74169

add a comment | 

You're correct - it is a group membership problem. First, see who owns the device:

ls -l /dev/ttyUSB0

On MY system, I don't have /dev/ttyUSB0, so I'll use /dev/ttyS0 instead

walt@bat:~(0)$ ls -l /dev/ttyS0

crw-rw---- 1 root dialout 4, 64 Feb 23 08:19 /dev/ttyS0

walt@bat:~(0)$ 

The output of the ls command shows that it's owned by root:dialout, and allows group access to the device.

Add your user to the dialout (or whatever is right for your system) group with:

sudo adduser $USER dialout

Then to make this group membership take effect, logout/login, OR newgrp dialout to start a shell with that group membership.

Check your group membership with /usr/bin/id.

share|improve this answer

answered 47 mins ago

waltinatorwaltinator

22.5k74169

ls -l /dev/ttyUSB0

walt@bat:~(0)$ ls -l /dev/ttyS0

crw-rw---- 1 root dialout 4, 64 Feb 23 08:19 /dev/ttyS0

walt@bat:~(0)$ 

sudo adduser $USER dialout

share|improve this answer

answered 47 mins ago

waltinatorwaltinator

22.5k74169

answered 47 mins ago

waltinatorwaltinator

22.5k74169

answered 47 mins ago

waltinatorwaltinator

22.5k74169

0

• open TCP port 2947 in your firewall


• in terminal, edit /etc/default/gpsd
  
  
  
  
  • sudo -H gedit /etc/default/gpsd
  
  
  • change DEVICES="" to DEVICES="/dev/ttyACM0"
    
  
  
  • save and quit gedit
  
  
  • sudo systemctl restart gpsd
  
  
  
  

gpsmon, cgps, and xgps will now work properly.

share|improve this answer

answered 18 mins ago

heynnemaheynnema

19.5k22158

add a comment | 

0

• open TCP port 2947 in your firewall


• in terminal, edit /etc/default/gpsd
  
  
  
  
  • sudo -H gedit /etc/default/gpsd
  
  
  • change DEVICES="" to DEVICES="/dev/ttyACM0"
    
  
  
  • save and quit gedit
  
  
  • sudo systemctl restart gpsd
  
  
  
  

gpsmon, cgps, and xgps will now work properly.

share|improve this answer

answered 18 mins ago

heynnemaheynnema

19.5k22158

add a comment | 

• open TCP port 2947 in your firewall


• in terminal, edit /etc/default/gpsd
  
  
  
  
  • sudo -H gedit /etc/default/gpsd
  
  
  • change DEVICES="" to DEVICES="/dev/ttyACM0"
    
  
  
  • save and quit gedit
  
  
  • sudo systemctl restart gpsd
  
  
  
  

gpsmon, cgps, and xgps will now work properly.

share|improve this answer

answered 18 mins ago

heynnemaheynnema

19.5k22158

share|improve this answer

answered 18 mins ago

heynnemaheynnema

19.5k22158

answered 18 mins ago

heynnemaheynnema

19.5k22158

answered 18 mins ago

heynnemaheynnema

19.5k22158