OpenMarine

Full Version: OpenPlotter 3 roadmap
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
I see, it seems that Raspberry OS for 32 bits is still using the old "Raspbian" name for definition:

32-bit:

PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
NAME="Raspbian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

64-bit:

PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

I will fix this on next version. Thanks for reporting. You can try the Raspberry OS 64-bit.
(2022-06-07, 06:24 PM)Sailoog Wrote: [ -> ]I see, it seems that Raspberry OS for 32 bits is still using the old "Raspbian" name for definition:

32-bit:

PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
NAME="Raspbian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

64-bit:

PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

I will fix this on next version. Thanks for reporting. You can try the Raspberry OS 64-bit.

Ok many thanks Sailoog
So, just out of curiosity this morning, I ran dpkg-buildpackage, on openplotter-gpio to see if it would compile on my 64 bit home test system. I compiled fine (after adding a few missing packages), and shows up in openplotter-settings version 3 (as 2.3.2-beta). It seems to run.

Before I got to a lot of trouble simulating a test on this, is there something I'm missing? Will this work with V3?

Answered my own question: when I set up a test SeaTalk GPIO, I get an error in SignalK. Oh well...
Most of the openplotter v2.x.x apps will compile for bullseye in v3.x.x but you will find unexpected issues. openplotter-gpio will have big changes in v3.x.x because GPIO inputs will generate notifications and GPIO outputs will be added as actions in openplotter-notifications app.
when do you think I2C and gpio for v3 beta will be coming?

I just had issues with signal k from what i can tell is server.js stopped working some how. So it wasn't passing data internally in signal k!
I Just started again with new openplotter image as i couldn't resolve it.
Doc for Dashboards is done: https://openplotter.readthedocs.io/en/3....s_app.html

Everything you need to start creating Grafana and InfluxDB dashboards and how to combine them.
(2022-06-10, 04:14 PM)turnipisum Wrote: [ -> ]when do you think I2C and gpio for v3 beta will be coming?

I just had issues with signal k from what i can tell is server.js stopped working some how. So it wasn't passing data internally in signal k!
I Just started again with new openplotter image as i couldn't resolve it.

I can not give a date, I can only report on progress.

At the end of this week we will start publishing the stable versions of the currents apps and docs.

pypilot, I2C, GPIO and SDR are next.
You probably have realized that a new version of openplotter-opencpn-installer has been released where PPA sources have been replaced by Debian/Ubuntu Backports. This is the result of a long discussion with the OpenCPN team and here is a short summary and background.

For some years we have used the Ubuntu PPA source to install OpenCPN in Debian and derivatives because this was the recommended way. This has been working right for years but according to some Debian purists this is an abomination and it is true that this has been the source of the problems with plugins availability for some architectures like arm64.

Plugin management has become uncontrollable because this scenario has forced to build plugins for each system/version/architecture and in some cases, like Raspberry, build special plugins. To solve this we have to make big changes in the OpenCPN core so there is a roadmap to finally build just native Debian plugins that will be installed in all derivatives. With this movement in openplotter-opencpn-installer we take the first step in this roadmap.

To have plugins for Debian the first thing you need is to install OpenCPN from a Debian repository, so we replaced the Ubuntu PPA source by the official Debian Backports repository. As you probably has noticed there is an old opencpn version in the official Debian repositories but this versions will rarely be up to date because OpenCPN development is always faster than the very restrictive rules to aprove new versions in the official Debian repositories. Backports repository is also official and is not as restrictive as the stable one so there is where opencpn will live. OpenPlotter will be in charge of adding the backports sources and everything to make this work.

Installing the last version of openplotter-opencpn-installer app old sources will be removed, new ones will be added and you just have to reinstall opencpn. You will find the main plugins, like o-charts, available for arm64. Now you should use the Flatpak way only in some non-LTS Ubuntu systems or some special cases.
Hi Sailoog,
I see there has been a steady stream of openplotter3 point releases, it is good to see many transition from beta to stable. Rapid progress - thanks.
Yes, we are late for this sailing season, but we are going as fast as we can.
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35