Up-to-date vector charts for OpenCPN - oeSENC

[bcn]

Originally Posted by skipperearly

Help please!
Have just bought oeSENC for Croatia and generated within ocpn/oeSENC plugin the fingerprint file. File name is 16chr long ext .fpr , filesize 0 (empty)

When I now try to generate system identifyer in o-charts portal I always get error "BAD FILE SIZE"

my setup: Win10, opcn 4.6.0

What should I do now?

Skipperearly,

we have seen somthing similar with a system with a tad agressive virus scanner. Do you run one beside of the integrated Windows Defender? If yes, can you please stop it and try again?

Hubert

[skipperearly]

Originally Posted by bcn

Skipperearly,

we have seen somthing similar with a system with a tad agressive virus scanner. Do you run one beside of the integrated Windows Defender? If yes, can you please stop it and try again?

Hubert

Hubert - thanks for helping BUT

took pc off the i/net,
switched off virus checker (Avira)
tried again to generate fpr file but is again empty.

I also noticed that the file name in the plugin dialog is different to the files on the desktop or prog data/opencpn/ directories.

Have then deleted all fpr files, edited the ini file to delete last fpr entry and tried again - unsuccessful.

Anything else I can try ? e.g. on-line service from o-charts?

[.Paul.]

@Skipperearly, @bcn,

In addition to the possibility of a virus scanner grabbing a file while it is being created, it is possible for a file backup system to grab a new file before the originating process is finished working with it.

I have had WD SmartWare on my Win 10 system grab onto files while they are still in use by the originating process. I have to disable backups while downloading charts. After the new charts have been processed, I enable backups in SmartWare.

Paul

[Liburnian]

This line in log file seems suspicious:
16:25:35 CET: oeSENC_pi failed to initialize OpenGL
Could here be a problem?
The name of directory is something like myname33-HR-2017-1
All ASCII characters..

Thanks for advices

[bdbcat]

SkipperEarly...

Two things:
1. I also noticed that the file name in the plugin dialog is different to the files on the desktop or prog data/opencpn/ directories.

More info on this, please?

2. Can you give us the full path name of the empty FPR on the Desktop? Should be something like:

"C:\Users\{yourname}\Desktop\OC????.FPR"

Thanks
Dave

[bdbcat]

Liburnian...

For test purposes, could you try to load oesenc_pi charts with main program (OpenCPN) disabled OpenGL?

Thanks
Dave

[skipperearly]

Originally Posted by bdbcat

SkipperEarly...

Two things:
1. I also noticed that the file name in the plugin dialog is different to the files on the desktop or prog data/opencpn/ directories.

More info on this, please?

2. Can you give us the full path name of the empty FPR on the Desktop? Should be something like:

"C:\Users\{yourname}\Desktop\OC????.FPR"

Thanks
Dave

,
Thanks Dave for helping! - would have hoped for a support link on the o-charts web site to get me further - at least they took my money!
... anyhow

did some more testing, switched off AVIRA and also windows defender settings and put oeserverd.exe on the exception list and ... - still no success.
File names vary always in the last 5 digits
eg on desktop oc01W_1490166989.fpr but
in program data/opencpn/ oc01W_1490166949.fpr gets created, both empty
in the opencpn.ini the lastfilename is always the name of the programm data/ocpn fpr file.

on another test [dialog] [desktop] [prog data/opencpn]
xx4035 changed to xx4037 , xx4035
xx74163 to xx74165 , xx74163
restarted opcn
empty, xx7433, xx7435
etc, so it appears that filename on desktop is always 2 higher than in progdata.

Also dialog does not read ini file to display last created fpn


ref your 2) full path name:

C:\Users\Freddie\Desktop\oc01W_1490174795.fpr

What shall I try next?

[bcn]

Skipperearly..

o-charts is simply the "outlet" for the charts.
Licensing from chart providers, production and distribution, well separated from the OCPN core.

We prefer to have the issues here at the forum to get an overview about those.
At least the ones in English..

And Dave is in this case the right address as he has written the plug-in.

Can you please attach the complete log, after disabling OpenGL and running the SystemIdentifier routine once again?

Hubert

[Liburnian]

The mac's ball is still spinning
OpenGL was't the issue. The program freezes when I confirm pop-up with info of the run-out date of charts or when I go with cursor over green rectangles at he bottom. Old CM93 charts work well when the program is responsive.

Last lines of log:
16:05:48 CET: validate_SENC_server
16:05:48 CET: Available TRUE
16:06:08 CET: PlugInManager: Deactivating PlugIn: /Applications/OpenCPN.app/Contents/PlugIns/libchartdldr_pi.dylib
16:06:08 CET: chartdldr_pi: DeInit
16:06:08 CET: PlugInManager: Deactivating PlugIn: /Applications/OpenCPN.app/Contents/PlugIns/libwmm_pi.dylib
16:06:08 CET: PlugInManager: Deactivating PlugIn: /Applications/OpenCPN.app/Contents/PlugIns/oesenc_pi/liboesenc_pi.dylib
16:06:08 CET: opencpn::MyFrame exiting cleanly.
16:06:08 CET: Chart cache PlugIn purge
16:06:08 CET: PlugInManager: Deactivating PlugIn: /Applications/OpenCPN.app/Contents/PlugIns/libchartdldr_pi.dylib
16:06:08 CET: PlugInManager: Deactivating PlugIn: /Applications/OpenCPN.app/Contents/PlugIns/libwmm_pi.dylib
16:06:08 CET: PlugInManager: Deactivating PlugIn: /Applications/OpenCPN.app/Contents/PlugIns/oesenc_pi/liboesenc_pi.dylib

[bcn]

Liburnian...

also here: can you please attach the complete log?

Hubert

[skipperearly]

Originally Posted by bcn

Skipperearly..

o-charts is simply the "outlet" for the charts.
Licensing from chart providers, production and distribution, well separated from the OCPN core.

We prefer to have the issues here at the forum to get an overview about those.
At least the ones in English..

And Dave is in this case the right address as he has written the plug-in.

Can you please attach the complete log, after disabling OpenGL and running the SystemIdentifier routine once again?

Hubert

Thanks for clarification - Hubert.

attached log file with OpenGL switched off (could this realy have an impact for the SystemIdentifier generation?)
BTW the desktop file is now oc01W_1490199931.fpr
and is not shown in the log!

Hope I can now get helped.

[bdbcat]

Skipper Early...

OK, as normal for diagnosing complex system, the first thing to do is simplify the environment, making it as simple as possible while still exhibiting the problem.

So, please, first remove or disable all plugins except for oesenc_pi. And try to build the FPR again.

Focus on the .fpr file generated in the ProgramData folder. This is the master file. The one copied to the desktop is just a convenience, helping new users to find the file easily.

Also, are you comfortable with working in DOS box (cmd)? If so, I can guide you through some lower level debugging steps....

Thanks
Dave

[Liburnian]

Here's the attachment of log file..

[skipperearly]

Originally Posted by bdbcat

Skipper Early...

OK, as normal for diagnosing complex system, the first thing to do is simplify the environment, making it as simple as possible while still exhibiting the problem.

So, please, first remove or disable all plugins except for oesenc_pi. And try to build the FPR again.

Focus on the .fpr file generated in the ProgramData folder. This is the master file. The one copied to the desktop is just a convenience, helping new users to find the file easily.

Also, are you comfortable with working in DOS box (cmd)? If so, I can guide you through some lower level debugging steps....

Thanks
Dave

Dave,
switched off all plugins except oesend_pi
no change - fpr file has size zero

no problem to use cmd promt
pls advise steps

[bdbcat]

SkipperEarly...

OK, open CMD prompt.

cd "C:\Program Files (x86)\OpenCPN\plugins\oesenc_pi"

oeserverd -f C:\ProgramData\opencpn\

Then look in c:\ProgramData to see if the fpr is built, and the size.

If no luck, try the other way:

cd C:\ProgramData\opencpn

 "C:\Program Files (x86)\OpenCPN\plugins\oesenc_pi\oeserverd" -f .\

If still this does not work, then try running the same set of commands as administrator command prompt.

Dave