OpenCPN Beta Version 3.1.1224 Released

[bdbcat]

Ahoy, OpenCPN'ers...

OpenCPN Version 3.1 Beta Build 1224 will soon be available for download from opencpn.org.

Monitor the opencpn.org Downloads page to find and download the latest Beta version binaries.....

Source is available now on github at:
https://github.com/OpenCPN/OpenCPN
Branch: beta31_stable

Changelog:
115. Correct to allow linux /dev/ttyUSB0 access.
116. Correct auto-upgrade of "AIS Port (Shared)" to 3.2 Connections architecture
117. Correct GPS upload port persistence to include manually entered ports.
118. Correct Windows serial port write performance bottleneck.
119. Correct AIS extended name field update. (FS#886)
120. Implement portaudio sound library support for linux.
121. Correct Dashboard datastream interface.
122. Improve AIS Icons and console background for Journeyman styles.
123. Correct for non-conformance of Xport to Windows API.
124. Correct UDP output port to be ephemeral (FS#908)
125. Add WindHistory instrument to Dashboard. Thanks to Thomas Rauch.
126. Implement AIVDO processing for Dashboard.
127. Update language files
128. Implement focused context menus for immutable layer objects (FS#576)

Release Beta 3.1.1224

Notes:

Have a very Happy Christmas, and good luck testing.

Dave

[cagney]

Windows, Mac and Ubuntu versions now available.
Thomas

[AISEAG]

Thanks Dave for this christmas parcel.

[cagney]

120. Implement portaudio sound library support for linux.

This is, hopefully, the end of the Linux Sound problem.
By using the portaudio libraries, sound should just work.
A new dependency is added, Ubuntu calls it "libportaudio2", other distros may have other names. This package should be fetched automatically. For compiling "portaudio19-dev" has to be present as well.
If you are using the wxgtk packages compiled with support for SDL, now is the time to un-peg these in Synaptic (or similar), update and the standard wx packages should be installed.

28. Implement focused context menus for immutable layer objects (FS#576)

The chance to confuse layers with standard features, is almost nil, wit the new context menu.
Right clicking on, for example a route belonging to a layer, brings up a small dialog saying "Layer Route" and just contains one option "Properties". Also, when hovering with the cursor over a route belonging to a layer, the yellow semi transparent text bubble, starts with "Layer Route........"
If you really need to use a route in a layer for navigation, import the layers gpx file in normal fashion, through the "Route Manager"

Thomas

[cagney]

Dave/Thomas

Some text problem with "Wind History" headlines, at least on my Linux.


Thomas

[Gilletarom]

Hello,

Thank Dave.

Trying with VDR. It seem that Cagney said right. Problem with apparent wind and apparent angle. But ???? not shure. The apparent wind is block on the same value ?

Gilletarom

[jpiebrig]

Hi dave,

117. Correct GPS upload port persistence to include manually entered ports.

Still not working for me. May be I have missed something but after I have uploaded once with "Serial:/dev/garmin" , then it comes back to "Serial:/dev/ttyS0"


120. Implement portaudio sound library support for linux.

Works very well after following instructions from Cagney.

[P_Dub]

Many, Many thanks for this update. One small correction for the current arrows of S57 charts. You must have forgotten to include the correct file:- chartsymbols.xml. The one that you did send me in may. If you don't remember send me an email I will reply because I can not send it within this program, it refuse to take it.
Have a good day.
P_Dub

[cagney]

Dave

The option "Send to GPS" does not appear in the focused menu, for a wpt in a route (and track?), any more. I think it was still in 12.20.

Thomas

[tom_BigSpeedy]

Cagney,
the "wind history" instrument is meant to be run as a standalone (vertical) instrument.
Just define a separate dashboard and add it as the only instrument.
See screenshot wind_history_setup.gif please.

You can / should (!) resize it with the mouse, see windhistory.gif
In real conditions, it monitors around 40 min of wind direction (red), as well as wind speed (blue), showing a vertical timeline every 5 mins (the example screenshot is a full-speed VDR replay).

The text on the top shows the current values, as it is displayed in the standard instruments (blue = wind speed data, TWS=True Wind Speed, red = direction, TWD = True Wind Direction).

Here is an explanation of the text line, left side (see screenshot):
TWS 7.5 : true Wind Speed currently 7.5 kts
Max 22.3 kts since 18:50 : this is the max Windspeed in the visible (!) curve, i.e. the last ~40 mins
Overall 22.3 : the max windspeed since O was started.

right side :
TWD 357° : True wind direction currently 357°

The thin red/blue curves are the real direction/speed values, the thicker curves are smoothed values. Makes it easier to see trends.

There is some logic included :
The instruments re-zoomes automatically as much as possible, always trying to show the whole visible curve;
Windspeed curve:
if your max (visible) windspeed is 10 kts, then your scale is from 0...11 kts (rounded upwards to the next full knot).
In the screenshot we had a mx of 22.3kts --> scale is 0...23 kts.
Wind direction :
The instrument scale shows +/- 90° of the currently visible data values, but is limited to a total of 360°.
If the wind is shifting through North (from 350, 355, 359, 002, 010, ...) we're shifting the curve as well, meaning that there is NO vertical jump in the data from 360° --> 0°, and we do NOT loose all the continuity in the smoothed curves !

If you should happen to have more than a full 360° cycle of wind direction in the recorded data (if you sail through a couple of dust devils ), I limited the max scale to 360°, meaning that the curve will run out of the visible area on bottom or on top of the instrument.

Please note :
you don't have to have the instrument "open" all the time.
Once activated as initially described, you can close it, and simply reopen it on demand. You don't loose the curves, the instrument continues to collect the data.
Simply rightclick on the standard-dashboard, and set click the wind history instrument (wind_history_re-activation.gif)
Well to be honest this is an dashboard-automatism and was not my programming :-)

Thomas

[bdbcat]

jpiebrig...

If you upload once, and then shut down, does the config file show the correct entry for /dev/garmin?

ex:
MostRecentGPSUploadConnection=Serial:/dev/garmin

Thanks
Dave

[bdbcat]

P_Dub...

Please send me the file by direct email.

Thanks
Dave

[jpiebrig]

Dave,

That is the line in my opencpn.conf you request for:

MostRecentGPSUploadConnection=Serial:/dev/garmin

It seems to be OK, but doesn't work. I have tried it again.

[bdbcat]

Thomas....

As programmed, the "Send to GPS" option only appears if the GPS is connected and giving valid position data.

This is Jesper's original logic, which I had not considered until this very minute.

I suppose it could be always available, say for the case when you are planning a trip with portable GPS from inside a cave with no signal??

Thoughts?

Dave

[bdbcat]

jpiebrig...

Does the port persistence fail for context menu (right-click), or for RouteManagerDialog? Both?

Dave