Feature Requests

[sloppy]

Originally Posted by transmitterdan

Have you tried to zoom in on the missing waypoint. Does it appear when you zoom in?

Yes and it does not show, even when I go back to where I jotted it down it does not appear

[sloppy]

Ok found the problem, I needed the Microsoft runtime C ++ now everything works fine, thanks again for responding.

[rgleason]

How did it occur to you that you needed the MS Runtime C++?

Was there a message? If so, When did that message appear?
We'd like to know for the FAQ

Originally Posted by sloppy

Ok found the problem, I needed the Microsoft runtime C ++ now everything works fine, thanks again for responding.

[nohal]

Originally Posted by rgleason

How did it occur to you that you needed the MS Runtime C++?

Was there a message? If so, When did that message appear?
We'd like to know for the FAQ

Rick...

It can not occur, ever, if the plugin is correctly built. Forget about this "incident".

Pavel

[sloppy]

Well I read the install instructions in the open cpn web and when I tried it everything worked

[blubaju]

Originally Posted by Hakan

In my opinion it's in no way dead. Some rather new more or less luxury pleasure boats use a NMEA2000 alike bus.

But so many older pleasure boats will for sure use NMEA0183 for another ten or twenty years. My own is from 1974 and no serious degeneration is seen.
And the majority of all commercial ships still use NMEA 0183 and I think a N2k bus is far away from being common on that market?

Maybe a temporary help: email jan 2015

I (Meindert Sprang) am almost finished with the new MiniPlex-3Wi-N2K which has 4 NMEA 0183 inputs, 2 NMEA 0183 outputs, SeaTalk in and out(!) and NMEA 2000 (both ways). And USB of course. I hope we can start selling these beginning of February 2014

The MiniPlex-3 series with NMEA 2000 will convert NMEA 2000 into NMEA 0183 and vice versa. It will also have an option to convert raw NMEA 2000 frames into a $MXPGN sentence to allow reading PGN's that cannot be converted into NMEA 0183 like switch and lamp info. This sentence can also be used to generate any arbitrary PGN on NMEA 2000. I have attached a PDF describing this sentence. Maybe you can present this to the OpenCPN community...
The NMEA organisation is currently looking into this sentence too.
Meindert Sprang
ShipModul Marine Electronics (this new model under development is not listed yet)

Regards,
Heinrich
Attached Files
File Type: pdf MXPGN sentence.pdf (17.9 KB, 125 views)
Reply With Quote Quick reply to this message

#2
11-01-2015, 12:33
bdbcat's Avatar
bdbcat

Join Date: Mar 2008
Posts: 5,358
Re: nmea2000, nmea0183, ST and WIFI for openCPN?
Heinrich...

Thanks for the info.

I see no reason why this device could not be directly supported by OpenCPN. Of course, the new $MXPGN sentence will not be recognised by the OCPN base, nor any existing PlugIns. But a PlugIn could be built to intercept these sentences and do whatever might be wanted. That PlugIn may also interface by the USB port for direct control of the device as well.

The conversion of more "normal" PGNs into NMEA0183 messages would be transparent to OCPN, and would work automatically.

So, a good product idea here, and I hope to see it shipping soonMXPGN sentence.pdf

[transmitterdan]

Originally Posted by rgleason

How did it occur to you that you needed the MS Runtime C++?

Was there a message? If so, When did that message appear?
We'd like to know for the FAQ

Rick,

A FAQ should try to limit itself to frequently asked questions. It becomes not so useful when long and full of one time only incidents not applicable to the majority of users.

This incident is not frequently occurring. Likely never again.

Likewise, copying posts from CF to the FAQ or documentation isn’t a great idea in my opinion. Without context several of the FAQ and doc sections have become confusing to the reader. In the FAQ one could point the reader to the CF OpenCPN forum where they may find infrequently encountered problems discussed. It would be nice to explain how they can use the detailed search engine. Then they could see the entire context of the discussion

[rgleason]

Agreed, Good points.

• Frequent
• Can you identify which ones are confusing so I can fix them?
• Yes, I do use CF links when appropriate and it can shorten the FAQ
• An explanation of how to search should be at the top? Good Idea.
• I was thinking they should be given some structure by topic.

Thanks.

Originally Posted by transmitterdan

Rick,

A FAQ should try to limit itself to frequently asked questions. It becomes not so useful when long and full of one time only incidents not applicable to the majority of users.

This incident is not frequently occurring. Likely never again.

Likewise, copying posts from CF to the FAQ or documentation isn’t a great idea in my opinion. Without context several of the FAQ and doc sections have become confusing to the reader. In the FAQ one could point the reader to the CF OpenCPN forum where they may find infrequently encountered problems discussed. It would be nice to explain how they can use the detailed search engine. Then they could see the entire context of the discussion

[nohal]

Originally Posted by rgleason

Agreed, Good points.

• Frequent
• Can you identify which ones are confusing so I can fix them?
• Yes, I do use CF links when appropriate and it can shorten the FAQ
• An explanation of how to search should be at the top? Good Idea.
• I was thinking they should be given some structure by topic.

Thanks.

Rick...

Not CF links. One link to this forum and an explanation on how to use the search function of the forum. That is one of the FAQs, titled "How do I find answers to questions not present in this FAQ and not covered in the manual which I have already studied?"

Pavel

[rgleason]

Pavel

I had to separate it to two questions. Still somewhat convoluted, so any suggestions are welcome.
https://opencpn.org/wiki/dokuwiki/do...ser_manual:faq

Originally Posted by nohal

Rick...

Not CF links. One link to this forum and an explanation on how to use the search function of the forum. That is one of the FAQs, titled "How do I find answers to questions not present in this FAQ and not covered in the manual which I have already studied?"

Pavel

[BlackSea]

Hi,


is it also possible to implement "Zoom/Scale Weighting" for mbtiles?


For example: zoom=zoom+1 -> tilesize=128x128

[bdbcat]

BlackSea...


It is technically possible. But not for OCPN 5.0. We are at feature-freeze point, and very near closeout.


Add to Flyspray tracker as a Feature Request, and it will be considered for the next Release.


Thanks
Dave

[BlackSea]

I have tried to create Future Request @ Flyspray but it doesn't work

Notice: Undefined variable: conf in /home/szlhykiz/public_html/flyspray/includes/class.backend.php on line 1081 Completely unexpected exception: Connection to tcp://mail.bigdumboat.com:587 Timed Out
This should never happend, please inform Flyspray Developers

Update: is done

[jheyland]

Not sure if this was asked before, search seems broken.


I recently purchased a ONWA chartplotter. ONWA provides worldwide charts for their plotters at no charge (BIG YEAH!). I was wondering if there was any plan to support their K-chart format.

[nohal]

Originally Posted by jheyland

Not sure if this was asked before, search seems broken.


I recently purchased a ONWA chartplotter. ONWA provides worldwide charts for their plotters at no charge (BIG YEAH!). I was wondering if there was any plan to support their K-chart format.

No. And as far as I know there is no documentation available for that format.