OpenCPN Beta Version 3.3.2118 Released

[fgd3]

Trying to update OpenCPN for Ubuntu produced this apparent error:

Errors were encountered while processing:
/var/cache/apt/archives/opencpn-tcdata_3.3.2107-0~trusty1_all.deb
/var/cache/apt/archives/opencpn-gshhs-crude_2.2.4-0~trusty2_all.deb
/var/cache/apt/archives/opencpn-gshhs-low_2.2.4-0~trusty2_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Did the update fail? Any idea why? What's my next step?

Fabbian

[nohal]

Fabbian...
do

sudo apt-get remove "opencpn*"
sudo apt-get update
sudo apt-get install opencpn

There was a conflicting file in one of the first version of the split packages. Don't worry, the remove step won't touch any data files, so you should end up with a running 3.3.2118 with the same configuration as you had before

Pavel

[bdbcat]

Ahoy testers....

I am analyzing crash dumps this morning.

I find one crash from an anonymous user concerning Danish ENCs.

Are the Danish ENCs available for downloading anywhere?
The one cell that is crashing is DK2KATGN.000

Anyone recognise this?

Thanks
Dave

[bdbcat]

Big_tomspeedy...

"Can you reset the oz_factor to 40 please ?"

Done, in github now.

Dave

[bdbcat]

reflectionsv37...

1. The *3D, etc characters in the NMEA sentence are checksum characters. They are calculated by OCPN. They change, depending upon the content of the message.
The Furuno GPS should ignore messages that have an improper checksum.

Show us some messages that seems to fail, and some that pass. We can verify the checksum with an external tool.

2. You should be able to install 3.3.2107 in parallel with any other version, and run it independently. Of course, unless you run in "portable" mode, all versions share the same config files and navobj files. So you cannot run them at the same time.
A simple parallel install of OCPN will not alter your existing route and waypoint information.. But if you are nervous, simply make a backup copy of navobj.xml, which lives in the same folder as your config file. Keep this backup somewhere safe and dry, and restore if necessary. It contains all your routes, tracks, and waypoints.


3. re: "Right clicking on the route and sending to the GPS is also no longer working." Have you tried this with a simple two or three point route in 3.3.2118? May we see the sentences being transmitted, please?

Thanks
Dave

[reflectionsv37]

Dave,

First, let me start this by saying that during neither my testing today, or my testing yesterday was I drinking or otherwise mentally impaired!

The reason I asked about the 3 checksum characters was that I only see them in the Route sentence, not the waypoint sentences and didn't see any reference to them in the Furuno upload specs.

Todays testing:

I started testing the 5 waypoint route I used yesterday that worked with the route manager but didn't work when right clicking on the route. I included a screen capture of the success and failure, but they appear to be identical.

I then tried the 11 waypoint route I used yesterday. Much to surprise, it worked fine today. As did any other route I tried up to a maximum of 24 waypoints. And even more surprising, both of these routes upload fine using the right click on the route. (Yes, I'm also starting to think I'm losing my mind!)

Thinking I must have done something wrong, I went back and tried the 5 waypoint route again. I can send it from route manager, but not right clicking. I created another route with 5 waypoints. I can also send this one via the route manager, but not right clicking. And again with this route, the NMEA screens appear identical.

I added a 6th waypoint to this route and tried uploading again with right click, it failed. I added 5 more waypoints to the same route giving it 11 and tried again. It uploaded with 11 waypoints using the right click. I've included a screen capture showing both the 6 waypoint failure and the 11 waypoint success on the same screen.

I'm completely stumped. I can find no obvious pattern to why one works and another fails. I also included a screen print of the 24 that succeeds. Unless your checksum routine uses a date function or lunar position as part of the algorithm, I don't think it's the checksums. I think it must be a hardware issue on my computer. I don't know what else it could be.

Yesterday, after posting my message, I saved off the opencpn directory, removed all versions and reinstalled 2107 as a completely clean install and the results were the same as I posted yesterday. I powered off and rebooted the computer multiple times during yesterdays tests and it made no difference. Also powered the GPS off and on multiple times to make sure there wasn't something residual sitting around somewhere. No difference. I restored my saved configuration directory, reinstalled 2118 and tried again yesterday with the same results. Today I try it to get you screen captures, and some of it works!

I think I'll go get a cold beer and start looking for a new motherboard.

[reflectionsv37]

One other comment on overzoom. I can overzoom now but not as far in as I could before. I also like to overzoom way in when I'm at anchor so I can see where I've swung and can't do that now. I agree with the other commenter who suggested we be allowed to overzoom even further.

[bdbcat]

reflectionsv37...

When faced with this myself, I would do the following:

Find/borrow another computer. Connect to the OCPN target computer with a NULL modem cable in place of the Furuno GPS receiver.. Run hyperterm, or similar, on the monitor computer. Verify that the NMEA sentences are actually making it out of your OCPN machine clearly, and match expectations.

If that all looks right, consider the cable from OCPN to Furuno. Connectors squeaky clean?

On overzoom, point taken. Extended overzoom in place for next Beta.

NMEA will drive one to drink, and no mistake.

Good Luck
Dave

[fgd3]

Originally Posted by nohal

Fabbian...
do

sudo apt-get remove "opencpn*"
sudo apt-get update
sudo apt-get install opencpn

There was a conflicting file in one of the first version of the split packages. Don't worry, the remove step won't touch any data files, so you should end up with a running 3.3.2118 with the same configuration as you had before

Pavel

Thanks, Pavel. I can always count on you for expert help with my Linux problems.

Fabbian

[tom_BigSpeedy]

Originally Posted by bdbcat

Big_tomspeedy...

"Can you reset the oz_factor to 40 please ?"

Done, in github now.

Dave

Thanks Dave,

much appreciated.

Thomas

[rgleason]

Have uploaded install of most recent version 3.3.2118 for Windows.
Here Opencpn Beta File Thingie rguser rgpass

[Baikal]

and did not correct the work overzoom in OpenCPN with the Russian language FS#1497

[bcn]

Baikal,

somebody would have to translate the term "overzoom" for the Russian version.

Hubert

[Baikal]

Originally Posted by bcn

Baikal,

somebody would have to translate the term "overzoom" for the Russian version.

Hubert

so it was translated!

[nohal]

Baikal...
Isn't there a shorter term, something like "Overzoom"? I'm not exactly sure that "Чрезмерное приближение" fits on the screen...
This is not a rhetoric question, the reason for asking it is https://github.com/OpenCPN/OpenCPN/b...canv.cpp#L9523 - We don't display that text if it is wider than 500 pixels...

Pavel