Beta Test / Technical

[Temptress]

OK all think I have it sorted.

Tried all the plugins in order and combinations always seems to crash when I introduce

libwmm_pi18_v07a_amd64_pi.so

Could this be the fact that I using x86 based processor?

When this is in /usr/lib/opencpn opening th eoptions button causes the app to crash. I will see if i can re-create the AIL Target list issue but this was random so may be difficult to reproduce

[nohal]

The version you have should be ok, but I don't have a 64 bit version of Ubuntu handy and can't reproduce on i386. Try downloading the current 0.8 release instead (it comes as a deb package, so install it, not just copy to the plug-in dir)

Pavel

[Temptress]

Pavel

I will try that in a few days and get back to you all here. I need to do something else just now....

[rgleason]

Have reestablished Celestial Nav Plugin docs..and augmented. It is not showing up in NON-Edit mode. Why? Do I have this set up correctly? Thanks
Celestial Navigation PlugIn | Official OpenCPN Homepage

[jongough]

Hi,
I have been trying out the new S63 charts in 3.3.1931. The charts now seem to be working fine, however, I have had to stop using this beta as it keeps on loosing connection to my autopilot and wind instruments. Both of these are serial devices and I use Belkin USB to Serial converters. The PC is running Win 8.1 64 bit and is currently fully up to date. When I use 3.2.2 it is all OK, so it appears that the beta version does not handle windows serial ports well.

I have looked through this forum and found similar error messages that I get when I try and restart the serial port,

11:06:08 AM: Closing NMEA Datastream Serial:COM4
11:06:08 AM: Stopping Secondary Thread
11:06:18 AM: Not Stopped after 10 sec.
11:06:18 AM: Opening NMEA Datastream Serial:COM4
11:06:18 AM: Error, comm port open failure, INVALID_HANDLE_VALUE, Datastream skipped.

But this seems to be (?) related to bluetooth which I am not using. There is nothing in the log when the com port stops responding.

Sometimes after about 20mins of not working the beta version crashes (two crash reports have been sent today).

I have attached the current log file which mainly contains the information from running the beta, but it also contains log info from 3.2.2

Is there any advice as to how to make the beta work better with the serial ports?

Thanks
Regards
Jon

[bcn]

Jon,

do you run an AIS as well? From the AIVDO sentence in the log...

There is a known issue with AIS in 3.3.1931 (and older versions) that crashes OpenCPN after some time.
Mentioned in the 3.3.1931 thread.

Hubert

[jongough]

Hubert,
Yes I do have AIS. I did not know of this issue as I did not look for it as I thought it may have been a symptom of the COM Port issue.

I have just anchored up for the night and have been using 3.2.2 for the last few hours with no COM Port issues. With 3.3.1931 I would loose at least one COM Port within about 1-15mins.

Is this the correct forum to report this issue and do you know if anyone else is experiencing it?

Thanks
Regards
Jon

[bcn]

Jon,

perhaps the 3.3.1931 thread would have been more appropriate, but as you sent a crash report in, your issue should have been registered.
What you might add is a screenshot of your COM settings (perhaps with the drop-down list of available COM ports).

Hubert

[jongough]

Hubert,
Here is a PDF of the COM ports I am using in OpenCPN.
COM6: AIS
COM3: Auto Pilot output and heading input from Auto Pilot
COM4: TackTick (now Raymarine) wireless wind instruments
NET: Output of AIS to send information to internet.

At the time of the errors "NET" was defined but not in use.

Garmin-USB: This is for a GPS that was not in use.

Is there anything else that would help?

Regards
Jon

[PjotrC]

In the thread about Beta 3.3.2107 I mentioned a problem with displaying GRIBs near the IDL. (cf. http://www.cruisersforum.com/forums/...ml#post1629106 ).

Indeed, this issue goes back to 2.5.0. I checked the backlog of GRIBS from this month, and I have now about 12 such files that cause the winbarbs to disappear, when the chart centre is moved between, say, 170W and 170E.

The GRIB area needs not cross the IDL for the problem to appear.
Some GRIBs reloaded at a later time for the same area behave OK, while others consistently (for now) lose the windbarbs.

A sample such GRIB is attached.

[nohal]

Pjotr...
Just to make sure what we are looking for - With this file you never see the wind bards?
I'm asking because while I can make it not show them while zoomed out enough and panning to move it to a specific area of the screen (right half), it works normally for me in all the other cases.

Pavel

[PjotrC]

Originally Posted by nohal

...move it to a specific area of the screen (right half), it works normally for me in all the other cases.

Yes, the windbarbs disappear when the area is moved enough to the right (for any zoom level, I think). Moving it to the left makes them reappear.

Version 1.3.6 handles this file correctly... :-)

[nohal]

What is 1.3.6?
OK, the fix should be easy enough when there's no unreproducible magic involved.

Pavel

[PjotrC]

Originally Posted by nohal

What is 1.3.6?

.....

[nohal]

Pjotr...
Should be fixed in master now.

Pavel