Help / FAQ

[VanisleBC]

I hate to be that guy, be she went the one time. since i havent been able to get it running despite quite a number of attempts.

Code reads:

20:44:20 PDT: NMEA input device open failed: /dev/cu.usbserial4
20:51:12 PDT: Closing NMEA Datastream Serial:/dev/cu.usbserial4
20:51:12 PDT: Opening NMEA Datastream Serial:/dev/cu.usbserial4
20:51:12 PDT: Metrics: m_display_size_mm: 285 wxDisplaySize: 1280:800
20:51:12 PDT: NMEA input device open failed: /dev/cu.usbserial4
20:51:13 PDT: Metrics: m_display_size_mm: 285 wxDisplaySize: 1280:800
20:53:54 PDT: Closing NMEA Datastream Serial:/dev/cu.usbserial4
20:53:54 PDT: Opening NMEA Datastream Serial:/dev/cu.usbserial4
20:53:54 PDT: Metrics: m_display_size_mm: 285 wxDisplaySize: 1280:800
20:53:54 PDT: NMEA input device open failed: /dev/cu.usbserial4
20:53:55 PDT: Metrics: m_display_size_mm: 285 wxDisplaySize: 1280:800

Any ideas?

Thanks so much.

[nohal]

Originally Posted by VanisleBC

I hate to be that guy, be she went the one time. since i havent been able to get it running despite quite a number of attempts.

Code reads:

20:44:20 PDT: NMEA input device open failed: /dev/cu.usbserial4
20:51:12 PDT: Closing NMEA Datastream Serial:/dev/cu.usbserial4
20:51:12 PDT: Opening NMEA Datastream Serial:/dev/cu.usbserial4
20:51:12 PDT: Metrics: m_display_size_mm: 285 wxDisplaySize: 1280:800
20:51:12 PDT: NMEA input device open failed: /dev/cu.usbserial4
20:51:13 PDT: Metrics: m_display_size_mm: 285 wxDisplaySize: 1280:800
20:53:54 PDT: Closing NMEA Datastream Serial:/dev/cu.usbserial4
20:53:54 PDT: Opening NMEA Datastream Serial:/dev/cu.usbserial4
20:53:54 PDT: Metrics: m_display_size_mm: 285 wxDisplaySize: 1280:800
20:53:54 PDT: NMEA input device open failed: /dev/cu.usbserial4
20:53:55 PDT: Metrics: m_display_size_mm: 285 wxDisplaySize: 1280:800

Any ideas?

Thanks so much.

The device can't be opened, this may in my book be caused by 2 things:
1) It does not exist. Open the Terminal application and run

ls -la /dev/cu.usbserial4

It should return something like this:

crw-rw-rw-  1 root  wheel   20,   7 Sep 28 08:06 /dev/cu.usbserial4

2) Something else is already using it. Open the Terminal application and run

lsof | grep "/dev/cu.usbserial4"

It should not return anything. If OpenCPN is not running and using the port.

Pavel

[RalphG]

Hello everybody,

I'm new to this forum, so if there is a better place for this question or a thread already answering it please let me know ... I could not find any.

I'd like to use OpenCPN on RHEL/CentOS/ScientificLinux 7.3; the package opencpn-4.8.0-1 on je.onfray.fr/repo/epel/7 works smoothly, but for the (quite oldish) plugin-s63 I get a message 'plugin not compatible', and there is no plugin for oeSENC at all. If I understood the mechanism behind these plugins correctly there is a piece of binary-only code involved, so getting me the source and compiling these plugins myself is not an option if the binary is not compatible with my system.

So: is anybody using these plugins on RHEL7? If so, how did you manage? If not, is there a chance to generate RPMs for them?

Thank you very much!

Best regards, Ralph

[CarCode]

Ralph,

I don't know about CentOS but I think the best way might be to try to use the oesenc plugin instead of s63. There seems to be several cheap charts for use with oesenc.
As far as I can see there are the needed binary "oeserverd" for linux, linux64 and linuxarm beside the binary for Windows and macOS in the sources of oesenc-pi plugin. You might give it a try to compile it yourself for your OS.

Gerhard

[RalphG]

Thank you, Gerhard; yes, I would love to use the oeSENC charts, I was just afraid to run into the same problems as I did with the S63 plugin, but I downloaded the oeserverd binary from github and ran ldd on it, and it reported no problems - encouraging! So I'll try to build the plugin ...

I still wonder why this important plugin is not in the je.onfray.fr repository - am I the only one who's using RHEL7?

Regards, Ralph

[CarCode]

Ralph,

as I said I know nothing about CentOS, Fedora etc.
Perhaps you try to consult SethDart (Jean-Eudes). It seems he know better.
http://www.cruisersforum.com/forums/...ml#post2065406

Gerhard

[SethDart]

Originally Posted by RalphG

I'd like to use OpenCPN on RHEL/CentOS/ScientificLinux 7.3; the package opencpn-4.8.0-1 on je.onfray.fr/repo/epel/7 works smoothly, but for the (quite oldish) plugin-s63 I get a message 'plugin not compatible', and there is no plugin for oeSENC at all. If I understood the mechanism behind these plugins correctly there is a piece of binary-only code involved, so getting me the source and compiling these plugins myself is not an option if the binary is not compatible with my system.

Hi Ralph,

I've build latest S63 plugin for EPEL. Can you give it a try and report?

BTW, the oesenc plugin is also available for EPEL, you can install opencpn-plugin-oesenc.

If you need any other plugin, please ask and I'll do my best to build it for EPEL.

Thanks,
Jean-Eudes

[penduick33]

Hi All,
Twice install of V4.8.0 and at each time, the plug-in windows is empty (see picture hereunder) and I can't install it (those which are normaly included with).
My computer is an ASUS-R752L with win10 and works well.
Is there anyone who can help me to solved this(my) problem, please?

[Hakan]

penduick..
Thanks for the report. I've earlier reported a similar experience: http://www.cruisersforum.com/forums/...ml#post2482952
Would you mind publish your config- and log-files here, so the developers may find out what's happening?

The config is called opencpn.ini and the log file opencpn.log. Both are probably found in your C:\ProgramData\opencpn\ but to be sure click the "About OpenCPN" icon in the Opencpn tool bar (The question(?) mark) Tab: "About"

Since you seems rather new on this forum: (BTW: Very welcome!)
To be able to attache the files to this forum you've to either Quote this post or "Go Advanced" and then "Manage attachments". Make a copy of each file and rename them to get the extension .doc. Example: Rename opencpn.ini to opencpn.ini.doc (some file types are very size limited but .doc not that much)


Håkan

[penduick33]

Originally Posted by Hakan

penduick..
Thanks for the report. I've earlier reported a similar experience: http://www.cruisersforum.com/forums/...ml#post2482952
Would you mind publish your config- and log-files here, so the developers may find out what's happening?

The config is called opencpn.ini and the log file opencpn.log. Both are probably found in your C:\ProgramData\opencpn\ but to be sure click the "About OpenCPN" icon in the Opencpn tool bar (The question(?) mark) Tab: "About"

Since you seems rather new on this forum: (BTW: Very welcome!)
To be able to attache the files to this forum you've to either Quote this post or "Go Advanced" and then "Manage attachments". Make a copy of each file and rename them to get the extension .doc. Example: Rename opencpn.ini to opencpn.ini.doc (some file types are very size limited but .doc not that much)


Håkan

Hi Hakan!
Thank you for your answer and your help.
See files requested attached and picture of the plugins files in program(x86), please.
Hope to read you soon and have a solution...

[penduick33]

Originally Posted by Hakan

penduick..
Thanks for the report. I've earlier reported a similar experience: http://www.cruisersforum.com/forums/...ml#post2482952
Would you mind publish your config- and log-files here, so the developers may find out what's happening?

The config is called opencpn.ini and the log file opencpn.log. Both are probably found in your C:\ProgramData\opencpn\ but to be sure click the "About OpenCPN" icon in the Opencpn tool bar (The question(?) mark) Tab: "About"

Since you seems rather new on this forum: (BTW: Very welcome!)
To be able to attache the files to this forum you've to either Quote this post or "Go Advanced" and then "Manage attachments". Make a copy of each file and rename them to get the extension .doc. Example: Rename opencpn.ini to opencpn.ini.doc (some file types are very size limited but .doc not that much)


Håkan

Hi Hakan!
Thank you for your answer and your help.
See files requested attached, please.
Hope to read you soon in order to find a solution...

[Hakan]

pend...
Well, I wasn't able to find a possible cause for this issue but still hopes for Dave, T-Dan or other more experienced programmers.

Thanks
Håkan

And BTW -- For next time, to rename a log or ini file I meant to just rename in the file explorer using F2 - not to open it in a word processor and make a Word .doc file with all that headers.

[penduick33]

Originally Posted by Hakan

pend...
Well, I wasn't able to find a possible cause for this issue but still hopes for Dave, T-Dan or other more experienced programmers.

Thanks
Håkan

And BTW -- For next time, to rename a log or ini file I meant to just rename in the file explorer using F2 - not to open it in a word processor and make a Word .doc file with all that headers.

Hakan,
OK (for all)!
I'll trie to found an issue by myself and I'm waiting returns from programmers...Hope this will be done soon!

[transmitterdan]

Penduick,

You have lots of plugins loaded into the plugins folder that are not the standard 4 plugins.

I suggest you uninstall OpenCPN. Then delete the OpenCPN plugins folder and all sub folders. Then install OpenCPN and see what happens.

If you want to make a backup copy of the plugins folder that would be a good idea. But if you find the above idea works you will have to install other plugins one at a time. Don't just copy all of them into plugins folder in one go.

[Hakan]

T-dan..
That would probably solve the issue for penduick.. but this is the second time we've got report like this. Two users report >?> 20 users experience the same without telling but quit O and think - worthless??
If there's a plugin causing this O would give at least a hint to the user what plugin and preferably what's the problem?
How should we act to find out the problem? Suggestions? What can I do?

Håkan