OpenCPN Version 4.8.2 Released

[nohal]

Dave and Pavel, Dave wrote that it is a big job to recompile all the plugins (I think the context was linux), but I wonder if you are considering moving wxWidgets and MSVC++ forward too, or will that be later?
Thanks.

Yes. Sooner. No, do not want any discussion about it now, it is enough of a headache doing it.

Originally Posted by rgleason

PS: Also I saw some discussion about continuing support for Win XP, and wonder if users should be preparing to move on to Win10 to be ready for the next version of O?

Not because of OpenCPN. But XP is several years past dead, be ready that more and more stuff already did, and more will, stop working on it.

In other words, do you think the next version will support or not support XP? It would be good to give users some advance warning. I suppose they have the option of not updating O for awhile too.

The next version will work on XP. The next next version? I don't know. Giving users any warnings about anything is not necessary at this moment.

Pavel

[rgleason]

Thanks Pavel for the quick response. Therefore going forward, should we be using

• plugin api 1.15 all plugins or
• use opencpn.lib from Opencpn v4.2 if the plugin will allow it

XP points are reasonable. [No discussion.]

[bdbcat]

Petter5...

About the large AIS targets.

Is your display size recognized correctly in Options->Display->Advanced->Physical Screen Width?

Thanks
Dave

[nohal]

Originally Posted by rgleason

Thanks Pavel for the quick response. Therefore going forward, should we be using

• plugin api 1.15 all plugins or
• use opencpn.lib from Opencpn v4.2 if the plugin will allow it

Use the oldest opencpn.lib that supports the API the plugin needs. There is no change in that.

And there won't be any change in that until the next release, where the API compatibility will get broken by design and new baseline will be set. Simply ignore the fact you know that we work on something, it will be announced and explained when appropriate. Now please let us just do what we need to do.

[verkerkbr]

Originally Posted by verkerkbr

Or rename the latest Linux version to 4.8.20000

Still running 4.8.10204 and this version works very well.

Thanks for all the efforts.

Bram

Problem solved. Removed in Synaptic Opencpn 10205 and installed latest version 4.8.2

OeSENC charts still working.

Distroying the oeSENC settings was my fear.

Regards,


Bram

[rgleason]

Originally Posted by nohal

Use the oldest opencpn.lib that supports the API the plugin needs. There is no change in that.

And there won't be any change in that until the next release, where the API compatibility will get broken by design and new baseline will be set. Simply ignore the fact you know that we work on something, it will be announced and explained when appropriate. Now please let us just do what we need to do.

So sorry to be an antagonist. Thanks for the clarification.

[Gilletarom]

Hello All,

Originally Posted by verkerkbr

Problem solved. Removed in Synaptic Opencpn 10205 and installed latest version 4.8.2
OeSENC charts still working. Distroying the oeSENC settings was my fear.
...Bram

I confirm. No problem by this way.

[verkerkbr]

Originally Posted by Gilletarom

Hello All,


I confirm. No problem by this way.

More improvements for the Raspberry Pi with OpenCPN 4.8.2 are underway.

Just is a new kernel series started with 4.14.18-V7+ (sudo rpi-update)

With quicker screen movements. (VC4 driver on OpenGL in O off).

Works very well in combination with 4.8.2 and now also signalK instrumenten set is working with real time data.

OpenCPN working on signalK in the future ?

Regards,


Bram

[Gilletarom]

Hello All,

Originally Posted by houlejm

...
Just a little problem for linux users which have installed both PPA's “ppapencpn/opencpn” and “ppa:bdbcat/opencpn”.

    sudo apt install ppa-purge        # If not already installed
    sudo ppa-purge ppa:bdbcat/opencpn

Tested on Ubuntu 16.04 and 17.10, Does not work on Raspberry pi. (ppa-purge not available) Use alternate method below.
...
Jean-Marie

With my raspberry, I use :

- sudo autoremove opencpn
- I update my sources.list file after I place a "#" before the entry with bdbcat/opencpn ppa
- sudo apt install opencpn

And all was Ok. (About oeSENC, I do not know because no oeSENC before.)

[Gilletarom]

Hello All,

Originally Posted by verkerkbr

More improvements for the Raspberry Pi with OpenCPN 4.8.2 are underway.
Just is a new kernel series started with 4.14.18-V7+ (sudo rpi-update)
...
Bram

With rasp, under rasbian without openplotter.
I use "sudo rpi-update".
And all is Ok.
Thank Verkerbr.

[cagney]

While manually selecting a new grib area with the cursor, the CM93 charts all grayed out. After the selection the concerned charts stayed grayed out until I restarted O. I did not try with rescanning the chart database.

In the log there were lines like

11:30:58 EST: Loading CM93 cell /home/thomas/Sailing/Charts/CM93/CM93 30.07.12//03900840/B/03900840.B
11:30:58 EST: Loading CM93 cell /home/thomas/Sailing/Charts/CM93/CM93 30.07.12//03900840/B/03900870.B
11:30:59 EST: Loading CM93 cell /home/thomas/Sailing/Charts/CM93/CM93 30.07.12//03900840/A/03900840.A
11:30:59 EST: VBO Error A: 1283
11:30:59 EST: VBO Error C: 1283
11:30:59 EST: VBO Error C: 1283
11:30:59 EST: VBO Error C: 1283
11:30:59 EST: VBO Error C: 1283
11:30:59 EST: VBO Error C: 1283
11:30:59 EST: VBO Error A: 1283
11:30:59 EST: VBO Error C: 1283
11:31:00 EST: VBO Error C: 1283
11:31:00 EST: VBO Error C: 1283
11:31:00 EST: VBO Error C: 1283
11:31:00 EST: VBO Error C: 1283
11:31:00 EST: VBO Error A: 1283
11:31:00 EST: VBO Error C: 1283
11:31:00 EST: VBO Error C: 1283
11:31:00 EST: VBO Error C: 1283
11:31:00 EST: VBO Error C: 1283
11:31:00 EST: VBO Error C: 1283
11:31:00 EST: VBO Error C: 1283
11:31:00 EST: VBO Error C: 1283
11:31:00 EST: VBO Error C: 1283
11:31:00 EST: VBO Error C: 1283
11:31:00 EST: VBO Error C: 1283
11:31:00 EST: VBO Error C: 1283
11:31:00 EST: VBO Error C: 1283
11:31:00 EST: VBO Error C: 1283
11:31:00 EST: VBO Error A: 1283
11:31:00 EST: VBO Error C: 1283
11:31:00 EST: VBO Error C: 1283
11:31:00 EST: VBO Error C: 1283
11:31:00 EST: VBO Error C: 1283
11:31:00 EST: VBO Error C: 1283
11:31:00 EST: VBO Error C: 1283
11:31:00 EST: VBO Error C: 1283
11:31:00 EST: VBO Error C: 1283
11:31:00 EST: VBO Error C: 1283
11:31:00 EST: VBO Error C: 1283
11:31:00 EST: VBO Error C: 1283
11:31:00 EST: VBO Error C: 1283
11:31:00 EST: VBO Error C: 1283
11:31:00 EST: VBO Error C: 1283
11:31:00 EST: VBO Error C: 1283
11:31:00 EST: VBO Error C: 1283
11:31:00 EST: VBO Error C: 1283
11:31:00 EST: VBO Error A: 1283
11:31:01 EST: VBO Error C: 1283
11:31:01 EST: VBO Error C: 1283
11:31:01 EST: VBO Error C: 1283
11:31:01 EST: VBO Error C: 1283
11:31:01 EST: VBO Error C: 1283
11:31:01 EST: VBO Error A: 1283
11:31:01 EST: VBO Error C: 1283
11:31:01 EST: VBO Error A: 1283
11:31:01 EST: VBO Error C: 1283
11:31:01 EST: VBO Error C: 1283
11:31:04 EST: VBO Error C: 1283
11:31:04 EST: VBO Error C: 1283
11:31:04 EST: VBO Error C: 1283
11:31:04 EST: VBO Error C: 1283
11:31:04 EST: VBO Error C: 1283
11:31:04 EST: VBO Error C: 1283
11:31:04 EST: VBO Error C: 1283
11:31:04 EST: VBO Error C: 1283
11:31:04 EST: VBO Error C: 1283
11:31:05 EST: VBO Error C: 1283
11:31:05 EST: VBO Error C: 1283
11:31:05 EST: VBO Error C: 1283
11:31:05 EST: VBO Error C: 1283
11:31:05 EST: VBO Error C: 1283
11:31:05 EST: VBO Error C: 1283
11:31:05 EST: VBO Error C: 1283
11:31:05 EST: VBO Error C: 1283
11:31:05 EST: VBO Error C: 1283
11:31:05 EST: VBO Error C: 1283
11:31:05 EST: VBO Error C: 1283
11:31:05 EST: VBO Error C: 1283
11:31:05 EST: VBO Error C: 1283
11:31:05 EST: VBO Error C: 1283
11:31:05 EST: VBO Error C: 1283
11:31:05 EST: VBO Error C: 1283
11:31:05 EST: VBO Error C: 1283
11:31:05 EST: VBO Error C: 1283
11:31:05 EST: VBO Error C: 1283
11:31:05 EST: VBO Error C: 1283
11:31:05 EST: VBO Error C: 1283
11:31:05 EST: VBO Error C: 1283
11:31:05 EST: VBO Error C: 1283
11:31:05 EST: VBO Error C: 1283
11:31:05 EST: VBO Error C: 1283
11:31:05 EST: VBO Error C: 1283
11:31:05 EST: VBO Error C: 1283
11:31:05 EST: VBO Error C: 1283
11:31:05 EST: VBO Error C: 1283
11:31:05 EST: VBO Error C: 1283
11:31:05 EST: VBO Error C: 1283
11:31:05 EST: VBO Error C: 1283
11:31:05 EST: VBO Error C: 1283
11:31:05 EST: VBO Error C: 1283
11:31:05 EST: VBO Error C: 1283
11:31:05 EST: VBO Error C: 1283
11:31:06 EST: VBO Error C: 1283
11:31:06 EST: VBO Error C: 1283
11:31:06 EST: VBO Error C: 1283
11:31:06 EST: VBO Error C: 1283
11:31:06 EST: VBO Error C: 1283
11:31:06 EST: VBO Error C: 1283
11:31:06 EST: VBO Error C: 1283
11:31:06 EST: VBO Error C: 1283
11:31:06 EST: VBO Error C: 1283
11:31:06 EST: VBO Error C: 1283
11:31:06 EST: VBO Error A: 1283
11:31:06 EST: VBO Error C: 1283
11:31:06 EST: VBO Error C: 1283
11:31:06 EST: VBO Error C: 1283
11:31:06 EST: VBO Error C: 1283
11:31:06 EST: VBO Error C: 1283
11:31:06 EST: VBO Error C: 1283
11:31:06 EST: VBO Error C: 1283
11:31:06 EST: VBO Error C: 1283
11:31:06 EST: VBO Error C: 1283
11:31:06 EST: VBO Error C: 1283
11:31:06 EST: VBO Error C: 1283
11:31:06 EST: VBO Error C: 1283
11:31:06 EST: VBO Error C: 1283
11:31:06 EST: VBO Error C: 1283
11:31:06 EST: VBO Error C: 1283
11:31:06 EST: VBO Error C: 1283
11:31:06 EST: VBO Error C: 1283
11:31:06 EST: VBO Error C: 1283
11:31:07 EST: VBO Error A: 1283
11:31:08 EST: VBO Error C: 1283
11:31:08 EST: Loading CM93 cell /home/thomas/Sailing/Charts/CM93/CM93 30.07.12//03300840/D/03480849.D
11:31:08 EST: VBO Error C: 1283
11:31:08 EST: VBO Error A: 1283
11:31:08 EST: VBO Error C: 1283
11:31:08 EST: VBO Error C: 1283
11:31:08 EST: VBO Error C: 1283
11:31:08 EST: VBO Error C: 1283
11:31:09 EST: VBO Error C: 1283
11:31:09 EST: VBO Error C: 1283
11:31:09 EST: VBO Error C: 1283
11:31:09 EST: VBO Error C: 1283
11:31:09 EST: VBO Error C: 1283
11:31:09 EST: VBO Error C: 1283
11:31:09 EST: VBO Error C: 1283
11:31:09 EST: VBO Error A: 1283
11:31:09 EST: VBO Error C: 1283
11:31:09 EST: VBO Error C: 1283
11:31:09 EST: VBO Error C: 1283
11:31:09 EST: VBO Error C: 1283
11:31:09 EST: VBO Error C: 1283
11:31:09 EST: VBO Error C: 1283
11:31:09 EST: VBO Error C: 1283
11:31:09 EST: VBO Error C: 1283
11:31:09 EST: VBO Error C: 1283
11:31:09 EST: VBO Error C: 1283
11:31:09 EST: VBO Error C: 1283
11:31:09 EST: VBO Error C: 1283
11:31:09 EST: VBO Error C: 1283
11:31:10 EST: VBO Error C: 1283
11:31:10 EST: VBO Error C: 1283
11:31:10 EST: VBO Error C: 1283
11:31:10 EST: VBO Error C: 1283
11:31:10 EST: VBO Error C: 1283
11:31:10 EST: VBO Error C: 1283
11:31:10 EST: VBO Error C: 1283
11:31:10 EST: VBO Error C: 1283
11:31:10 EST: VBO Error C: 1283
11:31:10 EST: VBO Error C: 1283
11:31:10 EST: VBO Error C: 1283
11:31:11 EST: VBO Error C: 1283
11:31:11 EST: VBO Error C: 1283
11:31:11 EST: VBO Error C: 1283
11:31:11 EST: VBO Error C: 1283
11:31:11 EST: VBO Error C: 1283
11:31:11 EST: VBO Error A: 1283
11:31:11 EST: VBO Error C: 1283
11:31:11 EST: VBO Error C: 1283
11:31:11 EST: VBO Error C: 1283
11:31:11 EST: VBO Error C: 1283
11:31:11 EST: VBO Error A: 1283
11:31:11 EST: VBO Error C: 1283
11:31:11 EST: VBO Error C: 1283
11:31:11 EST: VBO Error C: 1283
11:31:11 EST: VBO Error C: 1283
11:31:11 EST: VBO Error A: 1283

I never tried to to this while beta testing.

Using 4.8.2 0 on Kubuntu 16.04/64

Thomas

[rgleason]

Thomas tried the same with CM93 charts and selected a grib area, it all seems to be ok with Win10. Can this be repeated reliably?

[cagney]

Originally Posted by rgleason

Thomas tried the same with CM93 charts and selected a grib area, it all seems to be ok with Win10. Can this be repeated reliably?

Yes, I just repeated it, exactly the same.
I already have a selected area, that I normally uses. In this case I un-ticked "Always use this area" and to selected a new, different area.

[Moo]

GRIB request error due to bad format of email. Request and response shown below.

The problem is that OCPN is putting in an = for a split line but there appears to be no CR LF in the string sent to the email app; in this case Mailbird.

Edit: Actually I think the problem is the location of the | character before the = or the resulting spaces from the dropped CR LF

send GFS:37S,47S,161E,175W|0.25,0.25|0,6,12..120|= WIND,PRESS,APCP

Error: Incorrect syntax in the following grib request:
GFS:37S,47S,161E,175W|0.25,0.25|0,6,12..120|=
which parsed as follows:
Field 0: 37S,47S,161E,175W
Field 1: 0.25,0.25
Field 2: 0,6,12..120
Field 3: =
Error: "=" is not a valid parameter code for this request (your email program may be splitting long lines- use "=" as a line-split character, see "gribinfo" (email to: gribinfo@saildocs.com or www.saildocs.com/gribinfo)
For more info on request formats, see www.saildocs.com/gribinfo or send a (blank) email to: gribinfo@saildocs.com

[Moo]

A clean install of OCPN and Weather Routing provides no default configuration.

At least on Windows 10

At least there is nothing in ProgramData/OpenCPN

There are boat files in

C:\Program Files (x86)\OpenCPN\plugins\weather_routing_pi\data\boats

But these can't be opened because of, I think, the default Windows permissions.

I thought that the data files were going to be moved to ProgramData from some time ago?