OpenCPN on Raspberry Pi2

[mattkab]

Originally Posted by nohal

Matt...
There is no point for a non-developer user to build the master branch, actually the exact opposite. We package beta releases from it when it makes sense.

Pavel

That's a completely viable approach.

My personal opinion is that OpenCPN on low powered devices such as the Raspberry Pi are pushing the boundaries of the hardware and the software and need the newest versions to test. I agree 100% on using the releases on more stable and performant environments.

But you've correctly pointed out a flaw in my thinking and I'm going to try the packages in PPA right now...

[bcn]

Matt,

nevertheless a script for those which want to jump into the cold water and to report back would be an interesting complement.

And guys: document your stuff in the Wiki if you feel that this make steps easier for others or that details don't get lost.

Hubert

[CarCode]

Hubert,
you should read a little bit about the "Truck Factor": Truck-Factor by mtov

OpenCPN is a typical example.

Gerhard

[bcn]

Gerhard,

I see that you are well aware about the news at ct/heise.de ...
Read those as well and thought about OCPN.

Perhaps you lead me with one decade talking about natural detrition :-)
Nobody is eternal. Getting under the truck might short things..

And yes, everybody would like to see more developers here. As in any other project.
More: I don't see anybody here trying to keep somebody out.
It's Free software, so are the developers. To come or to go.

And generally I like to hear your findings - but there is no positive touch to get philosophical about the habitat.
You like that software and you know about programming. Do - and a correct critic or even a polemic approach to get things cleared up is positive. Great. Critics ad personam are just acid and does not add.

You are welcome

Hubert

[Swokey]

I'm new to the Pi2 and OpenCPN and I hope someone can help me. I have installed OpenCPN on the Pi2 and I have an USB GPS mouse. It took me a while but the GPS mouse is working. I checked that with the command 'cgps -s', see screenshot below.




So I'm ready for the next step, getting the GPS data in OpenCPN. I have setup a data connection in OpenCPN:



I think /dev/ttyUSB0 is the right port, because I see that when I execute 'ls '/dev/tty*'



I the NMEA debug screen I don't see anything happening.

Is there someone that can help me what I'm doing wrong?

[mattkab]

A couple things off the top of my head to look at:

1) Check the data settings. On my GPS puck, it's 9600 baud. (9600/8/N/1 is a very common serial protocol)

2) Try gpsd instead of cgps.

3) Make sure your user is in the dialout group

4) Use screen to verify the data stream first:
sudo apt-get install screen
screen /dev/ttyUSB0

... AND Welcome!


Sent from my SM-N900T using Cruisers Sailing Forum mobile app

[Swokey]

Thanks for you quick support, I will answer it point by point

1) The GPS puck has 4800 bps 8 data bits, 1 stop bit and none parity.

It's right that I can only do something with the 4800 bps?

2) I executed first 'gpsd -n -D 2 /dev/ttyUSB' and the 'gpsctl -V' then nothing happens and have to stop it



3) I'm in the dailout group



4) I had allready installed screen but when I executed 'screen /dev/ttyUSB0' then screen is terminated directly



Hopefully you can give this newby some more help.

[verkerkbr]

Here with BananaPi and a GPS mouse with an USB connector (has a serial-usb convertor build in).

Simply, take serial setting, baud rate 4800 and port /dev/ttyUSB0.

Actived NMEA debug and you see the output from the mouse passing by.

The only problem I had with the GPS mouse, is that is uses to much current from the USB port of the Banana. It works, but sometimes the lights go out on the board and switches off.

Bram

[Swokey]

It's really frustrating me that it isn't working.

When I check the GPS with commands xgps, cgps -s or gpsmon I get a good fix. But still with opencpn I don't get anything.

In OpenCPN I have set serial setting, baud rate 4800 and port /dev/ttyUSB0.



I have set the NMEA debug window on, then I see the following:



Any ideas what I can do?

[petter5]

I suggest to try using GPSD

 sudo apt-get update
 sudo apt-get install gpsd gpsd-clients python-gps

Go to Options-> Connections-> Add Conection and select "Network" plus the GPSD radio button. Address should be "localhost" and DataPorts should be set to 2947

Press apply.

What is your NMEA debug window showing now ?

[petter5]

Also, this webpage has a lot of info regarding setting up a USB GPS on the RaspberryPI
https://learn.adafruit.com/adafruit-...-everything-up

[verkerkbr]

Have you add yourself (as user) to the dialout setting ?

sudo usermod -a -G dialout user. (your user name)

I also did this for tty on the same way.

Otherwise it does not work.

And why is priority setting 2 ?

Bram

[bcn]

I've seen this kind of data in the debug with wrong baud settings.

Try one by one. 4800, 9600, 19200 ...

[Swokey]

Originally Posted by petter5

I suggest to try using GPSD

 sudo apt-get update
 sudo apt-get install gpsd gpsd-clients python-gps

Go to Options-> Connections-> Add Conection and select "Network" plus the GPSD radio button. Address should be "localhost" and DataPorts should be set to 2947

Press apply.

What is your NMEA debug window showing now ?

Thanks a lot, this is the solution for my problem. I see now good NMEA data in the debug window.

[akopac]

Did you make sure you part of the dial out group and I installed goad and goad client.


Sent from my iPhone using Cruisers Sailing Forum