OpenCPN Release Candidate 4.8.10204

[bdbcat]

Ahoy testers...

Here is OpenCPN Release Candidate 4.8.10204

This is a Release Candidate.
This RC was not expected, but became necessary in order to confirm the Changelog item (47).

Once again, absent any truly significant bugs, we will release this version as 4.8.2.


Source is available now on github at:
https://github.com/OpenCPN/OpenCPN
Branch: master
Tag: Beta_v4.8.10204

Windows:
http://opencpn.navnux.org/beta/openc...0204_setup.exe

Mac:
http://opencpn.navnux.org/beta/OpenCPN_4.8.10204.dmg

linux Beta PPA:
In build queue now.



Changelog:
47. Implement configurable Null header acceptance on UPD receiver, (FURUNO)


Thanks for your help, and...
Good Luck
Dave

[Baikal]

And have not corrected a problem with display ENC in OpenGL at selection of area of request Grib
Exactly the same problem as with the highlight of the track was

[Hakan]

Dave..
For info I've run with an active "configurable Null header acceptance on UPD receive" for a lot of scenarios the last days and haven't seen any obstacles.
It may be we can put to the future work list to scrap the option and make the Furuno adaptation permanent? Such a hidden config flag is easily forgotten so next Furuno user may have the same problem. Especially after a year or so.
Håkan

[Gilletarom]

Hello Dave, Hello Hakkan,

1° : Dave, China chart : Ok.

2° About this : "47. Implement configurable Null header acceptance on UPD receiver, (FURUNO)"
Can you explain what it is?
Thank in advance.

[bcn]

2° About this : "47. Implement configurable Null header acceptance on UPD receiver, (FURUNO)"

Furuno places a header before the NMEA sentences send over Ethernet.
These headers contain data symbols that are called "Null"bytes and OpenCPN did stumble over these data when parsing the messages.

[brucechun]

Hi Dave,

I posted a report about missing fairway boundary lines in cell C25C507W with 4.8.10203 before I found the .10204. The missing feature also apply to 4.8.10204.




The missing fairway boundary lines actually show on nearby cell C25C508W.


Safewater mark under night mode fixed.

Best regards,

Bruce

[Gilletarom]

Hello Bruce :

Originally Posted by brucechun

Hi Dave,
I posted a report about missing fairway boundary lines in cell C25C507W with 4.8.10203 before I found the .10204. The missing feature also apply to 4.8.10204.
....
The missing fairway boundary lines actually show on nearby cell C25C508W.
...
Bruce

See this : http://www.cruisersforum.com/forums/...ml#post2569804

[Gilletarom]

Hello BCN,

Originally Posted by bcn

2° About this : "47. Implement configurable Null header acceptance on UPD receiver, (FURUNO)"

Furuno places a header before the NMEA sentences send over Ethernet.
These headers contain data symbols that are called "Null"bytes and OpenCPN did stumble over these data when parsing the messages.

You said "NMEA sentences send over Ethernet.". Please, only with Ethernet or also by WIFI (If a FURUNO tool has WIFI)?

[bcn]

Ethernet is here used generically: either copper cable or radio-electric spectrum

The stumble stone was how Furuno formed the packets their system sends around.

[Gilletarom]

Hello BCN,

Originally Posted by bcn

Ethernet is here used generically: either copper cable or radio-electric spectrum
The stumble stone was how Furuno formed the packets their system sends around.

So I think that it is that I know as "Tag block". The tag block is inside each sentences, more exactly, before the standard content of the sentences.

[bcn]

This is not exactly the same.
But TAG blocks can be considered as a header as well. And are not limited to an Ethernet communication scenario.

We were discussing here TAG blocks from the NMEA0183 V4 standard some weeks ago.
A small look how this works:
https://rietman.wordpress.com/2016/0...183-tag-block/
or a more complete vision:
https://www.nmea.org/Assets/may%2009...00183_v400.pdf

[bdbcat]

Bruce...

Please find and delete the SENC file for 507W, and allow to be rebuilt next time you view it. This should correct the FAIRWY outline drawing.

Thanks
Dave

[bdbcat]

Baikal...

re:
And have not corrected a problem with display ENC in OpenGL at selection of area of request Grib
Exactly the same problem as with the highlight of the track was

Sorry we missed this one.
Can you provide a screenshot?

Thanks
Dave

[brucechun]

Hi Dave,

Yes, it works.

Thanks, regards,

Bruce

[Gilletarom]

Hello BCN,

Originally Posted by bcn

This is not exactly the same.
But TAG blocks can be considered as a header as well. And are not limited to an Ethernet communication scenario.
We were discussing here TAG blocks from the NMEA0183 V4 standard some weeks ago.
A small look how this works:
https://rietman.wordpress.com/2016/0...183-tag-block/
or a more complete vision:
https://www.nmea.org/Assets/may%2009...00183_v400.pdf

In one of the links above, I read this:
"
UdPbC?\s:VE0001*07\$VWVHW,135.0,T,155.0,M,18.0,N,3 3.3,K*58
UdPbC?\s:SO0001*08\$SDDBT,32.8,f,10.0,M,05.5,F*3E
UdPbC?\s:GP0001*03\$GPZDA,112250.80,17,09,2016,2,0 *63
UdPbC?\s:AI0009*14\!AIVDM,1,1,,A,494q>JQv2HcFkOrLo pM30u10050l,0*04
(Note: the question mark after the UdPbC string represents the null terminator.)
"
Is the text "UdPbC" a "header" in the sense that you speak about it in the previous posts?

What are the rules of writing headers? What is their role, in other words, what are they for?