OpenCPN Beta Version 3.1.1206 Released

[RickyEM]

Originally Posted by RickyEM

I just installed the beta and the nvc plug-in does not work with this beta while the plug-in does work with version 3.02.

I was mistaken, the new plug-in works fine with my nvc bahamas charts. If I knew how to delete this post I would do that or perhaps the board moderator could. Thanks!

[muttnik]

Originally Posted by bdbcat

If you can compile from source, the latest github code has been corrected. Otherwise, a new Beta will be forthcoming very soon.

Done and now working: thanks. Is there a "known issues" page I should have checked before posting? Sorry: I'm new to OpenCPN.

fyi, the UDP address is necessary only for output connections, and may be x.x.x.255

Couple of comments, feel free to disregard :-).
* If you create a UDP output, sentences from other sources that are transmitted out of this interface are then read back in. Seeing the same sentence twice probably does no harm and you may consider the overhead of automatically filtering broadcast packets originating from a local interface as greater than just processing the sentence twice.
* The wiki on data streams says that filtered sentences are not processed by opencpn but are still available for output by other interfaces. I just tried this, filtering out AIVDM sentences from an input tcp stream with opencpn outputting to udp broadcast. The AIVDM sentences stopped appearing in the output UDP stream. In light of the previous point I reckon this is the right thing to happen, but maybe the wiki needs clarifying.
* Is there any mileage in setting 10110 as a default port in network connections and for use in wiki examples? I know manufacturers are using all kinds of random ports, but 10110 is defined for nmea-0183 by the iana. If users are wanting to output broadcast to other devices (a common use case with the proliferation of ipads), giving them a (changeable) default might save non-technical users some stress in deciding what port to use.

cheers
keith

[Gilletarom]

Hello,

Originally Posted by bdbcat

RickyEM...

NVC charts work fine on the latest Beta (3.1.1206). Give it a try.

Dave

I confim that NVC-Chart plugin run fine with OCPN 3.1.1206 on XP SP3 using NVC dongle.

Is is only necessary that the dongle was inserted in the USB port before running OCPN.

Gilletarom.

[Gilletarom]

Hello Dave,

Exceptionally, I place this file here because it does not fit with the language files.


So use possibly with the next version of OpenCPN to come.

B.R.

Gilletarom

[Gilletarom]

Hello Dave,

In the new pot file, there is an item that intrigue me:

Rouge or suspicious vessel

"Rouge" is the correct word it or is there a typo?

Thank by advance.

B.R.

Gilletarom.

[cagney]

Originally Posted by Gilletarom

Hello Dave,

In the new pot file, there is an item that intrigue me:

Rouge or suspicious vessel

"Rouge" is the correct word it or is there a typo?

Thank by advance.

B.R.

Gilletarom.

I think it's a typo for "rogue".

Thomas

[Gilletarom]

Hello ,

For Rouge vessel suspect" I search on web site and I see this :

http://www.navcen.uscg.gov/pdf/AIS/F...2012_09_11.pdf (see page 30 of this pdf)

For "Rogue vessel suspect" I search also on the web and I see this :

AIVDM/AIVDO protocol decoding

I think that "Rogue" is better. And I can translate "Rogue vessel suspect" but I do not undestand "Rouge vessel suspect"

Gilletarom

[Gilletarom]

Hello,

Originally Posted by Gilletarom

Hello Dave,

Exceptionally, I place this file here because it does not fit with the language files.

So use possibly with the next version of OpenCPN to come.

B.R.

Gilletarom

As said in my private message, here a new version of french language file for 3.1.1220.

B.R.

Gilletarom

[Hakan]

Hello,

Referring to post #137 and user manual @ opencpn.org/ocpn/data_connections, use of UDP.’

I’m trying to play with network broadcasting within my wifi network at home. The goal is of course to make a setup for boat use afterwards. I can’t get it working and need some help. Posted here even if it may not be a correct tread though OPN from this beta gives the opportunity for this communications. Please advice me if this task has been explored in another tread. (my search for it where unsuccessful) My lack of knowledge is obviously how to handle the local network communication setup. I’ve tried to find a relevant Google answer but failed.

I’m using XP on sender(1) and Win7 on receiver(2). Both connected to the same local subnet, 192.168.1.x
Data displayed on PC(1) is from the San Fransisco AIS feed coming in on one network TCP-port. Works fine. That data is sent out via another network UDP-port. Also works fine due the the NMEA window.

PC(1) is forwarding nicely due to its NMEA window whatever address or port I use. No problem with OPN
PC(2) sees nothing. (I’ve for a short test connected the San Fransisco AIS feed also here and it works fine)

Please advice what addresses and ports I should use on respectively PC.
Is it maybe the wifi router that’s the problem?

Appreciate whatever knowledge I can get.

[vagspel]

Hi,
I have installed the latest version of OpenCPN 3.1.1206 for Debian/RasperryPi and are having problems with getting the AIS/position in. If I under settings select ttyusb0 I dont get any data. If I run minicom -b 38400 -D /dev/ttyusb0 i get perfect data! Anyone have any idea why this does not work?
Testing CM93 makes the system crasch but I will test on the B version with 512Mb memory because I think that that is the problem, lack of memory. Smaller rastercharts works with no problems.
Will also try to make a smaller databas CM93 and see if that works.
BR
Gunnar

[muttnik]

Originally Posted by Hakan

I’m using XP on sender(1) and Win7 on receiver(2). Both connected to the same local subnet, 192.168.1.x
[...]
Please advice what addresses and ports I should use on respectively PC.

For address, assuming the subnet is a /24 as you suggest above, the address you'd want would be 192.168.1.255 on the sender (ie broadcast address for you ipv4 subnet). This is the address broadcasts are sent *to*: A wildcard appears to be used for receipt so packets will be received on the unicast, subnet broadcast or all-subnets broadcast addresses (ie for the receiver, it doesn't matter).

For port, you just need to try and avoid clashing with any other software you are running on your network and make them the same on sender and receiver. I'm using 10110 which appears to be defined by the IANA for nmea-0183.

Do use the latest git sources. See post #127: there is a problem with UDP in beta 3.1.1206 but the latest git sources work fine.

[Hakan]

muttnik..many thanks for your answer.

I've tried the address you suggested, .255, on both sender and receiver. Port 10110. (I've also tried TCP instead of UDP.) No result. I can't see the port on cmd-netstat but I think something is broadcast from sender because if I instead use/steel another port occupied of OPN it takes a while and OPN switch to another port.

Maybe I should wait for next Beta? (My compiling knowledge is not good enough for the git source.)

[muttnik]

Originally Posted by Hakan

Maybe I should wait for next Beta? (My compiling knowledge is not good enough for the git source.)

Yes. I had the a problem on linux which sounds like it might be what you are experiencing (post #114): see bdbcat's reply in #127.

[Hakan]

Originally Posted by muttnik

Yes. I had the a problem on linux which sounds like it might be what you are experiencing (post #114): see bdbcat's reply in #127.

Eh..right.. I could have noticed? I'll await patiently. Many thanks.