GPS "Connecting.../dev/ttyUSB0"

General Custom Hardware / Electronics
1

I have RealDash running on a Linux Mint. I recently received this USB GPS module. https://www.adafruit.com/product/4279

I plugged the device into a USB port, and waited for a lock. I then go to Garage, then Dash, then Connections. I add a device, and scroll to the “External GPS Module” Right arrow and select Serial/USB, then right arrow again, make sure /dev/ttyUSB0 is highlighted, click right arrow, select “9600” for baud rate, checkmark, checkmark, X out of Gragae, and then I start to get the “Connecting…/dev/ttyUSB0” message every few seconds, but it never stops popping up, and when choosing the GPS screen on RealDash, it never updates…I still show someplace in Finland I believe.

What am I doing wrong? Is there a linux app that I can use to monitor and see if there is NMEA data coming from the module?

TIA

2

Start RealDash from terminal and see if you get any messages from RD about the connection. Typically USB connections do not have user privileges by default on Linux.

3

Thanks. What is the terminal command to run RealDash.

4

Sorry about that, I guess I only needed to type “realdash” in terminal to start it. Here is the output.

11:33:37.176 renderer_opengles.cpp(328)(tid:0x00000000) : NUTS_INFO - OpenGL ES version : OpenGL ES 3.1 Mesa 21.2.6, Renderer: Mesa DRI Intel(R) HD Graphics 4400 (HSW GT2)
11:33:37.242 os_linux.cpp(114)(tid:0x00000000) : NUTS_ERROR - dbus_connection_send_with_reply_and_block: The name org.xfce.ScreenSaver was not provided by any .service files
11:33:37.248 gpio.cpp(321)(tid:0x00000000) : NUTS_INFO - GPIO is not available
Error org.freedesktop.DBus.Error.ServiceUnknown: The name org.mpris.MediaPlayer2.spotify was not provided by any .service files
Error org.freedesktop.DBus.Error.ServiceUnknown: The name org.mpris.MediaPlayer2.spotify was not provided by any .service files
Error org.freedesktop.DBus.Error.ServiceUnknown: The name org.mpris.MediaPlayer2.spotify was not provided by any .service files
11:33:48.389 SerialComms_linux.cpp(481)(tid:0xdfec419e) : NUTS_ERROR - (Linux) Failed to open com port: /dev/ttyUSB0
11:33:48.389 SerialComms_linux.cpp(482)(tid:0xdfec419e) : NUTS_ERROR - ERROR: 13 opening /dev/ttyUSB0: Permission denied
11:33:48.389 SerialComms_linux.cpp(483)(tid:0xdfec419e) : NUTS_ERROR - In case of permission error, see this: > Serial port terminal > Cannot open /dev/ttyS0: Permission denied - Ask Ubuntu
11:33:50.402 SerialComms_linux.cpp(481)(tid:0x6485af68) : NUTS_ERROR - (Linux) Failed to open com port: /dev/ttyUSB0
11:33:50.402 SerialComms_linux.cpp(482)(tid:0x6485af68) : NUTS_ERROR - ERROR: 13 opening /dev/ttyUSB0: Permission denied
11:33:50.402 SerialComms_linux.cpp(483)(tid:0x6485af68) : NUTS_ERROR - In case of permission error, see this: > Serial port terminal > Cannot open /dev/ttyS0: Permission denied - Ask Ubuntu
11:33:52.418 SerialComms_linux.cpp(481)(tid:0x4b196d7a) : NUTS_ERROR - (Linux) Failed to open com port: /dev/ttyUSB0
11:33:52.418 SerialComms_linux.cpp(482)(tid:0x4b196d7a) : NUTS_ERROR - ERROR: 13 opening /dev/ttyUSB0: Permission denied
11:33:52.418 SerialComms_linux.cpp(483)(tid:0x4b196d7a) : NUTS_ERROR - In case of permission error, see this: > Serial port terminal > Cannot open /dev/ttyS0: Permission denied - Ask Ubuntu
11:33:54.418 SerialComms_linux.cpp(481)(tid:0x6485af68) : NUTS_ERROR - (Linux) Failed to open com port: /dev/ttyUSB0
11:33:54.418 SerialComms_linux.cpp(482)(tid:0x6485af68) : NUTS_ERROR - ERROR: 13 opening /dev/ttyUSB0: Permission denied
11:33:54.419 SerialComms_linux.cpp(483)(tid:0x6485af68) : NUTS_ERROR - In case of permission error, see this: > Serial port terminal > Cannot open /dev/ttyS0: Permission denied - Ask Ubuntu
11:33:56.426 SerialComms_linux.cpp(481)(tid:0x6485af68) : NUTS_ERROR - (Linux) Failed to open com port: /dev/ttyUSB0
11:33:56.426 SerialComms_linux.cpp(482)(tid:0x6485af68) : NUTS_ERROR - ERROR: 13 opening /dev/ttyUSB0: Permission denied
11:33:56.426 SerialComms_linux.cpp(483)(tid:0x6485af68) : NUTS_ERROR - In case of permission error, see this: > Serial port terminal > Cannot open /dev/ttyS0: Permission denied - Ask Ubuntu
11:33:58.441 SerialComms_linux.cpp(481)(tid:0x4b196d7a) : NUTS_ERROR - (Linux) Failed to open com port: /dev/ttyUSB0
11:33:58.442 SerialComms_linux.cpp(482)(tid:0x4b196d7a) : NUTS_ERROR - ERROR: 13 opening /dev/ttyUSB0: Permission denied
11:33:58.442 SerialComms_linux.cpp(483)(tid:0x4b196d7a) : NUTS_ERROR - In case of permission error, see this: > Serial port terminal > Cannot open /dev/ttyS0: Permission denied - Ask Ubuntu
11:34:00.459 SerialComms_linux.cpp(481)(tid:0x4b196d7a) : NUTS_ERROR - (Linux) Failed to open com port: /dev/ttyUSB0
11:34:00.459 SerialComms_linux.cpp(482)(tid:0x4b196d7a) : NUTS_ERROR - ERROR: 13 opening /dev/ttyUSB0: Permission denied
11:34:00.459 SerialComms_linux.cpp(483)(tid:0x4b196d7a) : NUTS_ERROR - In case of permission error, see this: > Serial port terminal > Cannot open /dev/ttyS0: Permission denied - Ask Ubuntu
11:34:02.468 SerialComms_linux.cpp(481)(tid:0x4b196d7a) : NUTS_ERROR - (Linux) Failed to open com port: /dev/ttyUSB0
11:34:02.468 SerialComms_linux.cpp(482)(tid:0x4b196d7a) : NUTS_ERROR - ERROR: 13 opening /dev/ttyUSB0: Permission denied
11:34:02.469 SerialComms_linux.cpp(483)(tid:0x4b196d7a) : NUTS_ERROR - In case of permission error, see this: > Serial port terminal > Cannot open /dev/ttyS0: Permission denied - Ask Ubuntu
11:34:04.468 SerialComms_linux.cpp(481)(tid:0x4b196d7a) : NUTS_ERROR - (Linux) Failed to open com port: /dev/ttyUSB0
11:34:04.468 SerialComms_linux.cpp(482)(tid:0x4b196d7a) : NUTS_ERROR - ERROR: 13 opening /dev/ttyUSB0: Permission denied
11:34:04.468 SerialComms_linux.cpp(483)(tid:0x4b196d7a) : NUTS_ERROR - In case of permission error, see this: > Serial port terminal > Cannot open /dev/ttyS0: Permission denied - Ask Ubuntu
11:34:06.469 SerialComms_linux.cpp(481)(tid:0x4b196d7a) : NUTS_ERROR - (Linux) Failed to open com port: /dev/ttyUSB0
11:34:06.469 SerialComms_linux.cpp(482)(tid:0x4b196d7a) : NUTS_ERROR - ERROR: 13 opening /dev/ttyUSB0: Permission denied
11:34:06.469 SerialComms_linux.cpp(483)(tid:0x4b196d7a) : NUTS_ERROR - In case of permission error, see this: > Serial port terminal > Cannot open /dev/ttyS0: Permission denied - Ask Ubuntu
11:34:08.469 SerialComms_linux.cpp(481)(tid:0x4b196d7a) : NUTS_ERROR - (Linux) Failed to open com port: /dev/ttyUSB0
11:34:08.469 SerialComms_linux.cpp(482)(tid:0x4b196d7a) : NUTS_ERROR - ERROR: 13 opening /dev/ttyUSB0: Permission denied
11:34:08.469 SerialComms_linux.cpp(483)(tid:0x4b196d7a) : NUTS_ERROR - In case of permission error, see this: > Serial port terminal > Cannot open /dev/ttyS0: Permission denied - Ask Ubuntu

5

Another update:

Did some googling, and then ran: sudo addgroup “$username” dialout

After a reboot, it connected! YAY!!

Now the output is

11:42:54.292 renderer_opengles.cpp(328)(tid:0x00000000) : NUTS_INFO - OpenGL ES version : OpenGL ES 3.1 Mesa 21.2.6, Renderer: Mesa DRI Intel(R) HD Graphics 4400 (HSW GT2)
11:42:54.331 os_linux.cpp(114)(tid:0x00000000) : NUTS_ERROR - dbus_connection_send_with_reply_and_block: The name org.xfce.ScreenSaver was not provided by any .service files
11:42:54.334 gpio.cpp(321)(tid:0x00000000) : NUTS_INFO - GPIO is not available
Error org.freedesktop.DBus.Error.ServiceUnknown: The name org.mpris.MediaPlayer2.spotify was not provided by any .service files
Error org.freedesktop.DBus.Error.ServiceUnknown: The name org.mpris.MediaPlayer2.spotify was not provided by any .service files
Error org.freedesktop.DBus.Error.ServiceUnknown: The name org.mpris.MediaPlayer2.spotify was not provided by any .service files

Im not concerned with the spotify error , but I wonder how to correct “NUTS_ERROR - dbus_connection_send_with_reply_and_block: The name org.xfce.ScreenSaver was not provided by any .service files” if I even need to.

TIA
Michael

6

While it appears that the GPS is connecting to RD, my location is not updating on the Navigation screen. Must I purchase a subscription to RD for my location to update?

TIA

7

No subscription necessary to test the connections. Try to disable ‘internal gps’ from Settings->Application.

8

Thanks. I changed the setting, but it did not work. Also, it took out my wifi–it basically disabled the wifi, and there was no way to get it back. I then reverted back the setting, and wifi came back, but of course, the Map did not update to my location.

Any other ideas?

9

Don’t know. We would need to see what your GPS module is sending to analyse if it is a NMEA data that RealDash understands. Try to read the data directly to terminal and paste the lines here.

10

Ran $ sudo cat /dev/ttyUSB0 and got the following

$GLGSV,3,2,10,65,30,266,29,72,17,215,16,66,14,325,76,07,293,2063
$GLGSV,3,3,10,86,06,178,73,04,090,6B
$GNRMC,152917.000,A,3403.0336,N,
11815.9535,W,0.24,171.74,110522,A68
$GNVTG,171.74,T,M,0.24,N,0.44,K,A21
$GNGGA,152918.000,3403.0337,N,11815.9543,W,1,07,1.27,122.4,M,-33.6,M,4F
$GPGSA,A,3,13,07,17,19,1.54,1.27,0.8702
$GLGSA,A,3,72,76,65,1.54,1.27,0.8712
$GNRMC,152918.000,A,3403.0337,N,11815.9543,W,0.75,299.96,110522,A6A
$GNVTG,299.96,T,M,0.75,N,1.40,K,A*29

Tried to run XGPS, but ran into an error "host localhost port 2947, which I have not been able to resolve yet.

TIA

11

I ran cgps, and the GPS appears to be producing NMEA data.

Any ideas on how to get RD to recognize the data/gps?

TIA

12

I see, the data is not from GPS but from GLONASS, which is not supported by RealDash external GPS parser.

I will add support for GLONASS for next release, but unfortunately we just missed 2.0.9 as it went for production a hour ago.

13

Wow, that’s great, thanks.

The specs indicate it has NMEA output. Gonna see if I can activate that and see what happens.

Thanks,
Michael

14

The output from your device is valid NMEA data already, RealDash just don’t parse the GLONASS data from it as this is the first time we encounter it.

15

Just saw a new version with GLONASS support was posted. THANKS!!!

16

Hope it works. I tested it on simulator, but testing actual GLONASS here is not an option.

17

Please add for android External GPS too

now a have proble with autostart - conflict App GPS and RealDash

in Windows GPS device connect ok!

in android - present in the list but not connect
Harware with any platrorm i can send

regards
Faslcon

18

Any changes we made for GLONASS support are on all supported platforms. If you have some other problem, please try to explain in very simple terms for me to understand.

19

I made video for you
please check

20

Send me a debug log