About nickH

I'm happy that this solved your issue.  Like I tried to explain in this post: To use the Data Layer in your snap you need the ctrlx-datlayer.deb. This debian package gets published with the SDK on GitHub. And gets downloaded to your Build Envrionment when you download the complete SDK form GitHub (like when you execute the install-sdk.sh). Now you need to include it to your snap with the snapcraft.yaml. And there are two ways to do this. The way you showed and the way we have currently in the SDK. There the snapcraft.yaml files of all sample projects got simplified.  But therefore, the storage folder (ctrlx-automation-sdk/deb) of the ctrlx-datalayer debian package in the SDK needs to be registered in the sources list (/etc/apt/sources.list.d/ctrlx-automation.list) so the debian package can be found by snapcraft. But this is already done in the App Build Environment of ctrlX WORKS V1.18.  Best regards,  Nick ... View more

Hi Archer,  great that you got the connection to the physical device running.  Some hint regarding the connection to the ctrlX CORE virtual : There are two ways to run your control.  Network adapter: ip: 192.168.1.1 -> connection settings for Data Layer Client like with the physical ctrlX CORE Port forwarding: ip: 127.0.0.1:8443 -> ip: 10.0.2.2 and sslPort: 8443     Best regards,  Nick   ... View more

I would recommend to switch to the newest release. Since the version 1.18 of ctrlX WORKS, we provide a workaround for this problem. See the new error-message: The workaround is to download the SDK form the link @CodeShepherd already shared. Please download the full repository (marked red in my screenshot). Then copy it to the home directory of your build environment and restart the script.   Best regards,  Nick   ... View more

Thanks for your quick answer! Maybe another option could be creating a Ruby binding to the C-library using FFI. Is this a pure C-API or is it C++? ... View more

A USB device could be connected and detected within the VirtualBox Ubuntu20 VM. The problem persists in the QEMU VM. The use of the QEMU VM is still the target. ... View more