This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[SOLVED] usb nmea connection unstable
#1
Sad 
hello
I'm using open plotter 8.0  with a usb gps device (Ublox/FTDI usb to serial)
Unfortunately the multiplexer drops this connectio and i have to restart
any ideas what is causing this
Reply
#2
Open OpenPlotter in debug mode and restart the NMEA 0183 multiplexer to see if kplex is reporting errors.
Reply
#3
Is your module 3.3v or 5V?
How much amp are you demanding from Raspberry pins?
Reply
#4
(2016-04-11, 06:48 PM)Sailoog Wrote: Is your module 3.3v or 5V?
How much amp are you demanding from Raspberry pins?

hello

the usb unit is 5 v en does not use a lot of power
I have tried to put openplotter in debug mode but the terminal command does not work

[email=pi@openplotter]pi@openplotter[/email]:~ $ python/home/pi/config/openplotter/openplotter.py

bash: python/home/pi/config/openplotter/openplotter.py: No such file or directory

open plotter works but the gps data stops after a few minutes
Do you know if there is a problem with the ftdi drivers
Reply
#5
There is a space after python.

Enviat des del meu fnac 5 usant Tapatalk
Reply
#6
You are able to use the same serial port for different programs.
You can also give a serial port two or more names.
Configuration problems
Or you have hardware problems
Or OP issues.

Configuration problems
Please check that in SignalK-Tab NMEA2000 port is set to none (if you don't have an can-usb adapter).
Check also Opencpn that there is no serial port in the configuration.
Have you used USB manager?
Yes
have you used Remember port?
Are you sure you didn't change any serial from one port to an other?

How to check serial configuration of the USB manager: type
$ ls /dev/tty*
look for the devices behind tty9.
now pull of your usb-serial gps and type again
$ ls /dev/tty*
there should be one yellow ttyUSB missing and your blue ttyOP...
Otherwise (if two blue ttyOP... are gone) you have changed ports.
Reconfig USB manager
Delete all USBs from the list
Look if the file is empty
$ cat /etc/udev/rules.d/10-openplotter.rules
pull out all serial usb adapter
push in the first. give it a name...

Hardware problem
To be sure that your PI and gps are OK, it is best to shutdown anything from openplotter.

Open a terminal on your desktop
$ killall node
$ killall kplex
$ killall python
pull of all usb-serial adapter
push in the usb-serial adapter from the gps
$ ls /dev/tty*
there should be only one ttyUSB0
there should be in maximum only one yellow ttyOP...
$ sudo apt-get install cutecom
$ cutecom
select device /dev/ttyUSB0
select baud rate
open device
now look if it works for an hour.

OP issues
Debug Openplotter as already mentioned by Sailoog
Reply
#7
Thx for the explanation
I will try the options and report back
For now I have the program running and i use an action to automatically reconnnect if the usb connection to the GPS is lost
(If nmea gps time message not updated for 10 sec, reset multiplexer, reset K server)[Image: sad.png]

I will also try to connect the gps direct to the serial port of the PI
Any suggestions for this ? ( ublox gps, should be save with the 3,3 V GPIO)[Image: huh.png]
Reply
#8
So you have a gps-ublox-shield (neo 7M or neo 8M ?) and this connected to an USB serial ttl converter?
What type of USB serial ttl converter do you use? What does "lsusb" say? Hopefully not Prolific.
neo 7M or neo 8M are specified to work from 1.65-3.6 V most of them from 2.7-3.6 V. So connecting the ttl serial to GPIO
shouldn't be a problem. But using a 5V USB serial ttl could be a problem.
Many ublox 6 7 8 are programmable. Use the Windows Software of ublox. https://www.u-blox.com/de/product/u-center-windows.
Reply
#9
(2016-04-12, 10:33 AM)e-sailing Wrote: So you have a gps-ublox-shield (neo 7M or neo 8M ?) and this connected to an USB serial ttl converter?
What type of USB serial ttl converter do you use? What does "lsusb" say? Hopefully not Prolific.
neo 7M or neo 8M are specified to work from 1.65-3.6 V most of them from 2.7-3.6 V. So connecting the ttl serial to GPIO
shouldn't be a problem. But using a 5V USB serial ttl could be a problem.
Many ublox 6 7 8 are programmable. Use the Windows Software of ublox. https://www.u-blox.com/de/product/u-center-windows.

Hi

i will check  The u blox is a neo 6, the converter an FTDI
The TTL output of the ublox should be save, but I will check with an osciloscope
Can you advice on settings in openplotter / raspian
Reply
#10
(2016-04-12, 01:13 AM)e-sailing Wrote: You are able to use the same serial port for different programs.
You can also give a serial port two or more names.
Configuration problems
Or you have hardware problems
Or OP issues.

Configuration problems
Please check that in SignalK-Tab NMEA2000 port is set to none (if you don't have an can-usb adapter). No
Check also Opencpn that there is no serial port in the configuration. No
Have you used USB manager?
Yes
have you used Remember port? No i used remember device changing to remember port increased stability
Are you sure you didn't change any serial from one port to an other? sud

How to check serial configuration of the USB manager: type
$ ls /dev/tty*
look for the devices behind tty9.
now pull of your usb-serial gps and type again
$ ls /dev/tty*
there should be one yellow ttyUSB missing and your blue ttyOP...
Otherwise (if two blue ttyOP... are gone) you have changed ports.
Reconfig USB manager
Delete all USBs from the list
Look if the file is empty
$ cat /etc/udev/rules.d/10-openplotter.rules
pull out all serial usb adapter
push in the first. give it a name...

Hardware problem
To be sure that your PI and gps are OK, it is best to shutdown anything from openplotter.

Open a terminal on your desktop
$ killall node
$ killall kplex
$ killall python
pull of all usb-serial adapter
push in the usb-serial adapter from the gps
$ ls /dev/tty*
there should be only one ttyUSB0
there should be in maximum only one yellow ttyOP...  OK
$ sudo apt-get install cutecom
$ cutecom
select device /dev/ttyUSB0
select baud rate
open device
now look if it works for an hour.  This is the problem cutecom loses connection after a couple of minutes

OP issues
Debug Openplotter as already mentioned by Sailoog
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)