USB key dongle for oeSENC

[Ben S]

Hi Hubert,

I updated my Windows 10 version 1703 to the latest 1909
Only charts connected to the dongle work
All other oesenc charts do not work anymore

I send you a mail

[bcn]

Then your PC is one of the single digit percent of W10 installs that change their "personality" when updated.
Got somehow better with the latest W10 updates, but yours has been a big jump between versions.

This W10 behavior is btw. one reason why we added the dongle option.


Please create a system identifier file from Options|plug-ins|oeSENC --> Preferences and send it to o-charts.
We will have a look.


Hubert

[hreuver]

Originally Posted by bcn

We got feedback from SG. Asking for the target systems for ARM64.

Any news on the USB dongle / SG lock library for ARM64?
I would like to compare some systems, but that will be easier (and more affordable) with a USB dongle.

[bcn]

No updates from SG these days.


We proposed Arm64 for Debian 10, Ubuntu 18.04 and 20.04 (both LTS).


Will give them a shout again.

[verkerkbr]

Originally Posted by bcn

No updates from SG these days.


We proposed Arm64 for Debian 10, Ubuntu 18.04 and 20.04 (both LTS).


Will give them a shout again.

Hi Hubert,

ask the same for the armhf 64 bits. De Rpi 4 is running perfect and fast on the 64 bits V8 kernel. Now also on the 5.4.40 kernel version.

However still an error message with the activation of the dongle.

Regards,

Bram

[hreuver]

@bram.


Since the USB dongle does not work for ARM64 currently, it is off-topic here.
However it should be a valid comment for the current opencpn-5.1.11 (beta) topic.


You can use a system fingerprint for oesenc on arm64 with the 4.2.1 or newer versions of the plugin. However I don't know a legit source for a recent precompiled plugin except github. I hope Dave will add it to the beta repo.

[bdbcat]

hreuver...


"I hope Dave will add it to the beta repo. "



oesenc_pi, v4.0.10, available in the OpenCPN Release PPA repo, is functionally identical to the managed version 4.2.1.


Dave

[verkerkbr]

Originally Posted by hreuver

@bram.


Since the USB dongle does not work for ARM64 currently, it is off-topic here.
However it should be a valid comment for the current opencpn-5.1.11 (beta) topic.


You can use a system fingerprint for oesenc on arm64 with the 4.2.1 or newer versions of the plugin. However I don't know a legit source for a recent precompiled plugin except github. I hope Dave will add it to the beta repo.

I'am running here Linux Mint Tricia 19.3 64 bits with the Oesenc dongle.

The same with my I386 system and the dongle

However still an error with the initalisation of the dongle on my RPI 4 with 64 kernel version 5.3.

Using the latest OpenCPN beta versions 5.1.428 with use of SignalK input.

[BlackSea]

Originally Posted by verkerkbr

I'am running here Linux Mint Tricia 19.3 64 bits with the Oesenc dongle.

The same with my I386 system and the dongle

However still an error with the initalisation of the dongle on my RPI 4 with 64 kernel version 5.3.

it does not yet exist libsglock for ARM64 ( no userspace ) Nice that kernel supports this but you also need a library

[hreuver]

Originally Posted by bdbcat

oesenc_pi, v4.0.10, available in the OpenCPN Release PPA repo, is functionally identical to the managed version 4.2.1.

@dave
I tested the oesenc-pi v4.0.10 and oesenc_pi v4.2.8

Functionality is different, if I use v4.0.10 OpenCPN freezes. If I use a simple bash-script as wrapper to return "0" when "oeserverd -s" is called I can work with v4.0.10.
No need to change.


However my request:
Could you remove the opencpn:armhf dependency from the opencpn-sglock-arm32 package?


If I can use a wrapper it is also moderately easy to switch oeserverd with the armhf-version of oeserverd. Currently the depency on opencpn:armhf in opencpn-sglock-armhf breaks the upgrade system in Ubuntu 20.04/ARM64. But I can use the USB Dongle with oeSENC + OpenCPN-beta on ARM64. When I tested today it worked.

Rebuilding the sglock-arm32 package is a tremendous lot of work on an arm64 system (just to remove one label on a largely binary package).

[bcn]

Originally Posted by hreuver

If I can use a wrapper it is also moderately easy to switch oeserverd with the armhf-version of oeserverd. Currently the depency on opencpn:armhf in opencpn-sglock-armhf breaks the upgrade system in Ubuntu 20.04/ARM64. But I can use the USB Dongle with oeSENC + OpenCPN-beta on ARM64. When I tested today it worked.

Do I get the idea right that you are using a 32bit package in the ARM64 environment?

[hreuver]

Originally Posted by bcn

Do I get the idea right that you are using a 32bit package in the ARM64 environment?

Yup.

OpenCPN ARM64
Plugin oesenc-pi ARM64, with oeserverd ARMHF
opencpn-sglock-arm32, off course ARMHF


The hardware I use has no ARMHF installation candidate, standard it is shipped with Ubuntu 20.04/ARM64.


I was planning to test it with an RPI4 and then post the procedure somewhere on this forum.
It requires some copying by hand and a specific installation order.
Not a standard Ubuntu installation procedure.

[bcn]

This is quite helpful as it takes the pressure away from SG for ARM64 - what we know is right now a "niche". Some very interested users but far away from being mainstream.

[bdbcat]

bcn...
Let us not remove the pressure on SGLock folks.
hreuver's technique to run oeserverd/armhf on arm64 environment is creative, and instructive. But certainly not fit for casual users, yet, IMHO.


Dave

[hreuver]

Originally Posted by bdbcat

bcn...
Let us not remove the pressure on SGLock folks.
hreuver's technique to run oeserverd/armhf on arm64 environment is creative, and instructive. But certainly not fit for casual users, yet, IMHO.

I would add to it, it is usefull for beta testing, but not fit for proper use.
Mixing environments is not the way to go to get a stable system.


There are parts where I think "how could this possible work, I think I left some steps".