Raspberry PI - Installing OpenCPN Version 5

[Dsanduril]

As noted above in my previous posts, we too have a Pi onboard running the nav systems. It does not need rebooting any more than the Raymarine instruments, whose network fails about once every 2-6 weeks in some form or another (and it's not even a complicated setup, we only have basic instruments and AP).

For some of the technical stuff we don't use OpenGL and have no issues with panning and zooming. CPU sits at 5-6% when just running, and moves up to 10-15% when actively panning/zooming/creating routes, etc.

The one thing I have found that seems to be consistent is leaving the grib plugin loaded with a grib file displayed. That usually leads to a non-responsive OpenCPN within about a day. I can usually SSH into the Pi in that case, but have not investigated too much yet (other boat projects). Presuming some kind of memory issue since CPU doesn't seem to be the problem, but not sure.

[Reefmagnet]

Originally Posted by Kerryf

Guys, i love raspberry pi and that sounds like a fantastic project to occupy hours of time setting it up but in my opinion raspberry pi belongs on the workshop bench or running (badly) a home entertainment system. It definitely does not belong as a primary navigation system on a boat. Not suitable!

If configured incorrectly, this would be the case and I'm the first to admit that plug and play they ain't vis setting up as a chartplotter. All things considered, they don't even work out a great deal cheaper than a basic mfd. And they have no water resistance.

BUT...

Does your mfd can consume as little as 200mA in operation?
Is it both practical and affordable to carry a complete set of hardware spares aboard for your mfd?
Can you add new features to your mfd at will?
Can you store all charts, documentation, manuals, notes etc with automatic syncing to cloud storage on your mfd?
..and the list goes on.

So pro's and cons.

PS I've never had any joy setting one up as a dnla media server either, but then again, that applies to my mfd as well.

[Reefmagnet]

Heads up for pi users that may not know; there are phone apps available that allow you to shut down and restart your pi without the need to connect via vnc or SSH. Other handy apps for a phone are network mappers which help find your dhcp address allocated pi (and other devices) on the network.

[NahanniV]

Originally Posted by verkerkbr

I also have a touchscreen with Egalax driver. But the driver has to be added manualy.

Hi Bram,

Can you elaborate on what driver is needed and exactly how to install it ?

With the driver installed, will the touch screen work after the monitor is turned off then on again ?

Much appreciated,
JM.

[NahanniV]

Originally Posted by verkerkbr

I also have a touchscreen with Egalax driver. But the driver has to be added manualy.

Hi Bram,

Can you elaborate on what driver is needed and exactly how to install it ?

With the driver installed, will the touch screen work after the monitor is turned off then on again ?

Much appreciated,
JM

[verkerkbr]

Originally Posted by NahanniV

Hi Bram,

Can you elaborate on what driver is needed and exactly how to install it ?

With the driver installed, will the touch screen work after the monitor is turned off then on again ?

Much appreciated,
JM

Hi JM,


yes the driver keeps working when installed.

I will make detailed instructions how the get the Egalax touch working.

At the moment I'am not at my desk for looking at the settings. I will make an howto for you later.

Regards,

Bram

[verkerkbr]

Originally Posted by NahanniV

Hi Bram,

Can you elaborate on what driver is needed and exactly how to install it ?

With the driver installed, will the touch screen work after the monitor is turned off then on again ?

Much appreciated,
JM

Hi JM,

first get the driver from the EET website. I used 2.5.5814L-ma. But perhaps there are newer drivers.

Unzip driver and go to the new directory. With the screen connected run setup.sh. Click on the settings.

Then adjust the driver: usr/share/X11/xorg.conf.d/52-egalax-virtual.conf

driver is evdev

then install:

sudo apt install xserver-xorg-input-evdev

in de kernel is installed the usb driver. You have to blacklist this one.

in etc/modprobe.d blacklist.conf blacklist usbtouchscreen

So is it working here.

There are other options available to correct the the touch points.

But this was not needed for my Faytech 10" screen.

Regards,

Bram

[Jubilee39]

I got openplotter working on PI looks very interesting. It seems to me that since the Moitessier hat is incorporated that sensors that come on the hat cannot be incorportated by other means. I am very rusty programming having last done it in basic. I want to set up monitor for various current sources and to that end I got a MCP3008 and a 5 channel hall effect ADC model HXA-ACDC. Openplotter sees the MCP3008 and signalk will show the channels but I do not get input. I have scoured the internet but I cnnot seem to install any recipe that will work. The terminal window opens with openplotter as the first command line and I cannot get to the raspian terminal. I also would like to use team viewer as a remote desktop as I already use it as a remote monitor but cannot get it to install instead of the packaged vnc.
Any help would be appreciated as for now my nav input is via BT from onboard instruments and I want to build my own using other chips instead of the hat and don't want to waste my time if I cannot.

[NahanniV]

Originally Posted by verkerkbr

Hi JM,

first get the driver from the EET website. I used 2.5.5814L-ma. But perhaps there are newer drivers.

Unzip driver and go to the new directory. With the screen connected run setup.sh. Click on the settings.

Then adjust the driver: usr/share/X11/xorg.conf.d/52-egalax-virtual.conf

driver is evdev

then install:

sudo apt install xserver-xorg-input-evdev

in de kernel is installed the usb driver. You have to blacklist this one.

in etc/modprobe.d blacklist.conf blacklist usbtouchscreen

So is it working here.

There are other options available to correct the the touch points.

But this was not needed for my Faytech 10" screen.

Regards,

Bram

Thanks Bram,

Sorry, I did not get to this until just now as we have been sailing in areas without good internet connection.

It did not work for me, I am sure I have done something wrong.

I downloaded the driver from: DanoTech Co., Ltd.

Unzipped it.

$sudo sh setup.sh Picked all correct choices (defaults in most cases)
$sudo Reboot

Not sure what you mean by this:
"
Then adjust the driver: usr/share/X11/xorg.conf.d/52-egalax-virtual.conf
"
The file is there, do I need to edit it ?

$sudo apt install xserver-xorg-input-evdev
completes OK.

"
in etc/modprobe.d blacklist.conf blacklist usbtouchscreen
"
That was already done by the setup.sh I guess.

$sudo reboot

The touchscreen works in exactly the same way it did before this installation.

if I turn off the screen it is not working when it is turned back on.

when I try the Calibration utility it says the Daemon is not running ?
$ eCalib

eCalib Utility version: [v2.4.3715]
-h Show help message
Daemon is not running

Any Idea where I went wrong ?

[verkerkbr]

Originally Posted by NahanniV

Thanks Bram,

Sorry, I did not get to this until just now as we have been sailing in areas without good internet connection.

It did not work for me, I am sure I have done something wrong.

I downloaded the driver from: DanoTech Co., Ltd.

Unzipped it.

$sudo sh setup.sh Picked all correct choices (defaults in most cases)
$sudo Reboot

Not sure what you mean by this:
"
Then adjust the driver: usr/share/X11/xorg.conf.d/52-egalax-virtual.conf
"
The file is there, do I need to edit it ?

$sudo apt install xserver-xorg-input-evdev
completes OK.

"
in etc/modprobe.d blacklist.conf blacklist usbtouchscreen
"
That was already done by the setup.sh I guess.

$sudo reboot

The touchscreen works in exactly the same way it did before this installation.

if I turn off the screen it is not working when it is turned back on.

when I try the Calibration utility it says the Daemon is not running ?
$ eCalib

eCalib Utility version: [v2.4.3715]
-h Show help message
Daemon is not running

Any Idea where I went wrong ?

Hi JM,


i got my driver from the EET website.


EETI eGalaxTouch Drivers for Linux Look for the right kernel version.



Did you give the setup the right instructions ? With USB cable connected ?


Yes the config: usr/share/X11/xorg.conf.d/52-egalax-virtual.conf must be changed to the evdev driver. Except for the Joystick of course.



So it must work.


Regards,


Bram

[NahanniV]

It is working now.

I downloaded the latest driver from EETI eGalaxTouch Drivers for Linux

and everything works !

Originally Posted by NahanniV

Thanks Bram,

Sorry, I did not get to this until just now as we have been sailing in areas without good internet connection.

It did not work for me, I am sure I have done something wrong.

I downloaded the driver from: DanoTech Co., Ltd.

Unzipped it.

$sudo sh setup.sh Picked all correct choices (defaults in most cases)
$sudo Reboot

Not sure what you mean by this:
"
Then adjust the driver: usr/share/X11/xorg.conf.d/52-egalax-virtual.conf
"
The file is there, do I need to edit it ?

$sudo apt install xserver-xorg-input-evdev
completes OK.

"
in etc/modprobe.d blacklist.conf blacklist usbtouchscreen
"
That was already done by the setup.sh I guess.

$sudo reboot

The touchscreen works in exactly the same way it did before this installation.

if I turn off the screen it is not working when it is turned back on.

when I try the Calibration utility it says the Daemon is not running ?
$ eCalib

eCalib Utility version: [v2.4.3715]
-h Show help message
Daemon is not running

Any Idea where I went wrong ?

[NahanniV]

Originally Posted by verkerkbr

Hi JM,


i got my driver from the EET website.


EETI eGalaxTouch Drivers for Linux Look for the right kernel version.



Did you give the setup the right instructions ? With USB cable connected ?


Yes the config: usr/share/X11/xorg.conf.d/52-egalax-virtual.conf must be changed to the evdev driver. Except for the Joystick of course.



So it must work.


Regards,


Bram

I did not have to edit the .conf file with the latest driver package.
Will adding the evdev add functionality ?

[verkerkbr]

Originally Posted by NahanniV

I did not have to edit the .conf file with the latest driver package.
Will adding the evdev add functionality ?

Hi Jim,

good to hear that it works now.

My setup was from more then a year ago. Then the config did not show any driver. so I had to add the Evdev.

Latest driver setup version does this perhaps.

Regards from the Netherlands,


Bram

[NahanniV]

Originally Posted by verkerkbr

Hi Jim,

good to hear that it works now.

My setup was from more then a year ago. Then the config did not show any driver. so I had to add the Evdev.

Latest driver setup version does this perhaps.

Regards from the Netherlands,


Bram

How do you get right clicks ?

Regards from the Bahamas,

[Moo]

Originally Posted by Kerryf

Guys, i love raspberry pi and that sounds like a fantastic project to occupy hours of time setting it up but in my opinion raspberry pi belongs on the workshop bench or running (badly) a home entertainment system. It definitely does not belong as a primary navigation system on a boat. Not suitable!

I built a plotter based on a RPi, as others on this forum know, it replicates all the functions of a commercial plotter and more, is ip67, has some dedicated buttons for MOB etc. Has inputs from N2k network and N0183 plus a set of weather station sensors. Total cost $380 NZ mostly for the ip67 components.

It has run reliably for many voyages now and at sea is the only instrument running these days.

P. S. When running a pass into an atoll I do not look at any instruments.. As you said you are just a beginner.