About nickH

Hello Norm, Yes, there are different alternatives for installation and setup of your Linux development environment for the SDK. For the start, I would always recommend to setup a Development Environment using QEMU. This is the recommended way and it's also the easiest and quickest. Because a default user (boschrexroth/boschrexroth) and many necessary tools are automatically installed on the first boot. In addition, the QEMU is very lightweight and provides an emulator for both architectures arm64 and amd64.   But if you are a Linux expert and don't need Windows for your daily work, a native Linux can be your development environment of choice. Also because of performance reasons manly with the arm version of the QEMU.   Best regards Nick ... View more

Hello Because the partition layout of Ubuntu Core 20 has changed, the version update to V1.12 has to be conducted using the image update mechanism of the ctrlX CORE via micro SD card. In the Collaboration Room (path: ctrlX_CORE_APPS/All-Apps-In-One-File/RM21.11 - V 1.12) you can find the SystemImage and a Guideline on how to perform the update in the Release Notes. Be aware that with V1.12 Licensing comes into play. Therefore see Quick Start Guide Licensing Center.  Best regards Nick ... View more

Hello,  for the SDK-V1.12 you need to install the new ctrlx-datalayer package. You can find the package as a Debian package in the folder "/deb" of the SDK.    If you have already installed a old version of the package, you can remove this version first: sudo dpkg -r ctrlx-datalayer   Now you can install the datalayer package: sudo dpkg -i deb/ctrlx-datalayer*.deb     These commands can also be found in the readme of a cpp-sample.   Best regards Nick   ... View more

Hi Adam, I got an update on your issue.  The notification (apparmor="DENIED" operation="open" profile="snap.rexroth-deviceadmin.web" name="/snap/" pid=1495 comm="wasp" requested_mask="r" denied_mask="r" fsuid=0 ouid=0) in the Logbook appears because the DeviceAdmin-App has a bug. The App tries to access data outside of its own snap, which gets blocked by apparmor because of security violations.  Other than notifications in the logbook this bug doesn't have any negative effect and can be ignored. Further this bug will get fixed with the next patch of the DeviceAdmin.    Best regards Nick ... View more