Openplotter reliability?

maby

Well-Known Member
Joined
12 Jun 2009
Messages
12,783
Visit site
Hi all, I didn't want to hijack the current Openplotter related thread, so here's my new one...

Following suggestions in my request for ideas to share out a connection-limited marina wifi service, I've spent a few days playing with Openplotter. I've been running it on a Pi 3B using the standard image downloaded from the Openplotter web site. After a couple of days of serious experimentation, I've come to the conclusion that it has interesting possibilities, but it does seem rather fragile. I'm just wondering if this is something unique to me - implying that I'm doing something wrong - or is it more general?

I installed (actually, installed four times) from the basic image - not the Noobs image - and booted it up on a known good RPi. In each case, it booted fine and got to the home screen. I then needed to install the drivers for an additional USB WiFi adaptor - I know that the theory is that Openplotter on a Pi 3B should be able to run the onboard wireless simultaneously as an AP and a client to another AP, but it has never actually agreed to do that for me. The process of getting the USB WiFi adaptor configured requires a few reboots and, in every one of my attempts, the Pi has got into the state which I've seen described on some of the forums where it hangs on the boot step where it is checking the 800x480 video sub-system. Once it starts doing that, it seems impossible to get it to boot cleanly again.

The Openplotter 1.0 image reports that there is an upgrade to 1.2 available and the release notes indicate that one of the additions is the ability to configure out the check of 800x480 - so I decided to try doing things the other way round - boot 1.0 and immediately upgrade to 1.2 before trying any of the other configuration tasks. I hooked the Pi up to the network via an ethernet cable to eliminate the need to do any wifi configuration, booted from a fresh card and selected the update option from the menu. It spent a long time downloading, unpacking and installing, then flashed some sort of error message up on the terminal window, paused for a couple of seconds, then blanked the screen - ignoring keyboard and mouse. I let it stand for quite a long time, then forced a reboot - it comes back up still believing that it is running 1.0, but the upgrade option is now broken and many of the other functions don't work either.

So, am I unusual, or is this all still a bit fragile? Thus far, I have put in more than a day trying various options - I really can't justify any longer unless there is a realistic prospect of success. I have a lot of experience of Raspberry Pi - I've built some non-trivial products around them. The hardware I'm using is proven - pulled from our stores where it has been used for commercial applications. All I'm really looking for is a natting wireless extender - possibly with Open VPN built in. I have found some pretty good instructions for setting that up and it will probably be my next attempt. Open plotter does seem to offer some intresting additional functions, but on my current experience I can't justify pouring more time into it.
 
For your specific problems it's probably better to ask the horses mouth >>
http://forum.openmarine.net/

Upgrade should be fairly seamless if lenghty, ISTR a couple of " Y/n" confirms needed along the way .I reinstalled a few weeks ago, didn't take long at all apart from left alone for the download/upgrade time .


Otherwise I've only broken mine when fiddling - it stays on without a reboot for weeks at a time 24/7 running openplotter & signalk writing data to a influxdb database, with a hifiberry amp & Clementine it is the onboard music/podcast/streaming music centre acessable anywhere from a tablet/laptop. Some node-red in the background.

Rock solid once going, well almost - chromium (open source chrome) can be quite resource hungry & maybe a coupe of times it has crashed when listening to BBC radio through chromium all afternoon.
 
Last edited:
Thanks for that - I will give it another try - but probably not until next week!

Gave it a go last night, far from seamless but none of the fatal issues you were having.

So on a Raspberry Pi 3b & freshly formated 10x 17Gb SD card.

The Pi is attached to monitor.keyboard & screen though I did the whole process with all control done over VNC using a tablet to see if it could be done, it could.

pi@openplotter:~ $ cat /sys/firmware/devicetree/base/model
Raspberry Pi 3 Model B Rev 1.2

pi@openplotter:~ $ cat /proc/cpuinfo
processor : 0
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 38.40
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4


processor : 1
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 38.40
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4


processor : 2
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 38.40
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4


processor : 3
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 38.40
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4


Hardware : BCM2835
Revision : a02082

Image downoaded from here >>
http://www.sailoog.com/blog-categories/openplotter-rpi


Roughly using instructions from here, but using the openplotter image, not NOOBs >>
https://docs.sailoog.com/openplotter-v1-x-x/getting-started


Copied image onto 16Gb SD card using win32 disc imager >>
https://sourceforge.net/projects/win32diskimager/


Put card into Pi & powered up. Minute or so a wifi network called Openplotter appears, log on from tablet using android VNC viewer.


Click on anchor icon to open openplotter - click on network tab.


Select RPi3: AP/client and click set, click apply then reboot from shutdown menu.


Click on wifi icon top right of screen - no interfaces found, reboot again....

Couldn't get internal wifi adapter to work so tried an Alfa AWUS051NH V2 , set network mode to RPi3: AP + client.
Rebooted and the Alfa was there. Logged onto the wifi network which is run from a mobile phone.

From the updates menu ran 'update openplotter"

Took HOURS! But successful first time, at one point the openplotter access point disappeared but came back again , just as well as there were a couple of "y/N" prompts which needed keyboard input to answer on the terminal.

Finally...... update process finished cleanly & rebooted.

Another problem - after the reboot the Openplotter network wasn't there, so could be important to make a note of the IP address of the second wifi adapter, then you can use that in VNC to log on to the Pi again. I reset and OKed the network mode to the same settings and rebooted. All good, up and running and seems plenty stable.

Since I've tried setting network mode back to RPi3: AP/client and unplugging the Alfa, internal adapter working again as both openplotter network and logged onto the mobile network sharing net access. Seems the RPi3: AP/client won't work with another usb/wifi dongle plugged in.

So looks like the RPi3: AP/client doesn't work before the upgrade, bit of a pity as means you need either ethernet or an external wifi dongle working with net access to do the upgrade.

But actual time on the keyboard wasn't that long, upgrade took a good while though. At no point did it crash or hang.
 
Concerning reliability;
I've found that it is pretty critical to use a quality SD card for the Pi, I manage (at work) 15+ Pi systems that run 24/7, 365 (not Openplotter but similar application with video and so on) and they do crash occasionally, requiring a new SD-card and a full rebuild.
The SD cards we've been using so far has been Kingston SDCG/64Gb, they typically last at least a year for us.
Another factor is to have a reliable, stable power supply that can deliver 2.5A continuous _at least_.
 
Concerning reliability;
I've found that it is pretty critical to use a quality SD card for the Pi, I manage (at work) 15+ Pi systems that run 24/7, 365 (not Openplotter but similar application with video and so on) and they do crash occasionally, requiring a new SD-card and a full rebuild.
The SD cards we've been using so far has been Kingston SDCG/64Gb, they typically last at least a year for us.
Another factor is to have a reliable, stable power supply that can deliver 2.5A continuous _at least_.

:encouragement:

Yet to trash an SD card but low power supply must be near the top of RPi issues. Openplotter has a card backup option in the accessories menu so easy to back up the entire system.
 
I've been monitoring the effect of having extra's like influxdb and a lamp stack (minus MySql) running and on a B+ PI it's been remarkably stable.

I have the PI encased within the official 7" screen case, with the touchscreen. This is going to be placed next to the nav station and the plan is not so much to have the chart plotter available - but an easy to follow (and most importantly) a standardised way of getting at all the data - which I am achieving with html/bootstrap/php/javascript coupled to the web socket from SignlalK server.

So with the above in mind - do I think its fragile?

I have done one install, messed with the LAMP addition and added Influx DB, then inserted a full website - and it's not even blinked, absolutely no crashes, hang ups or anything, for which I am most impressed. If it's this stable on the boat - I will be delighted.
 
As the SD card is the most likely part to fail, simply having an identical card with a clone of the setup on it seems like a proper safeguard.
I'd go for that if I had a Pi onboard.
 
No real reason for it not be stable, but the PI is dead slow, so best used as your server, and gateway, and use something much faster for actually working with OpenCPN (if you use that).

As other have said the SD card is (not the actual card itself though) is the weak point. The data is easily backed up, but there is another way. You can actually boot and run the system via USB. The SD card slot has limited bandwidth available, it is actually faster and safer to use a USB 3 SSD or similar.
 
No real reason for it not be stable, but the PI is dead slow, so best used as your server, and gateway, and use something much faster for actually working with OpenCPN (if you use that).

As other have said the SD card is (not the actual card itself though) is the weak point. The data is easily backed up, but there is another way. You can actually boot and run the system via USB. The SD card slot has limited bandwidth available, it is actually faster and safer to use a USB 3 SSD or similar.

We were marketing a product based on the Pi3 (or Pi Zero W) with a hard disk attached - then we migrated it into the AWS cloud - so we have several RPis and several hard disks in stores. We did initially try using an SD card in the Pi, but we were running a local database and the frequency or write cycles was so high that we destroyed the SD card within three months.

The Pi is a lovely little machine provided you use it appropriately. One of our first generation machines is still up and running - two years without a blink. It's just the Openplotter distribution that seems fragile to me - I'm pleased to see that GHA also hit a couple of problems above!
 
It's just the Openplotter distribution that seems fragile to me - I'm pleased to see that GHA also hit a couple of problems above!

Once installed it's rock solid though, and the install is not that bad really, your problems don't seem typical from feedback on the openplotter forums. Plenty power going in?
 
Once installed it's rock solid though, and the install is not that bad really, your problems don't seem typical from feedback on the openplotter forums. Plenty power going in?

I did have power problems when I started, but I switched to a well specified PSU and everything seemed fine in hardware terms after that. The primary problem hitting me was the hang during startup on "checking 800x480" - which, I gather, is a common problem. I tried to update to V1.2 in order to overcome that and that failed seriously after running for ages and soaking up a lot of internet bandwidth.

In practice, I really don't need most of the functionality of Openplotter - I was just looking for a natting WiFi extender and I have found other Raspberry Pi packages that will deliver that. I will have another go at Openplotter next week just to see it in operation.
 
I did have power problems when I started, but I switched to a well specified PSU and everything seemed fine in hardware terms after that. The primary problem hitting me was the hang during startup on "checking 800x480" - which, I gather, is a common problem.
Very little on the openplotter forums - sounds like a raspbian issue, same as the USB/wifi drivers.


I tried to update to V1.2 in order to overcome that and that failed seriously after running for ages and soaking up a lot of internet bandwidth.
Sounds very much like something wrong your end, I had a couple of hiccoughs updating but neither fatal, any update for any computer eats a load of data, no way round that.


In practice, I really don't need most of the functionality of Openplotter - I was just looking for a natting WiFi extender and I have found other Raspberry Pi packages that will deliver that. I will have another go at Openplotter next week just to see it in operation.

I'll have another hit at it as well just to check for consistency & do a better report back to the developers of anything which they can improve, the support is very good but sometimes might take a day or so to get the replies.

Well worth a good look, one of the big pluses is having signalk built in, what NMEA might be like given a good few more decades of development and being made free and opensource ;)
 
Top