About nickH

nickH · ‎05-10-2022

Hello, like I recommended, I compared the mouse-data example with the Python samples in the SDK (see ctrlx-automation-sdk/smaples-python/datalayer.provider). I saw that the python wheel datalayer got updated to ctrlxdatalayer (see ctrlx-datalayer on PyPI). So I changed the import to the new python wheel. Then you also have to add the datalayerdeb to the parts in your snapcraft.yaml. Now the provider of the app is working and I can see the nodes in the Data Layer (sdk-py-mouse-data). I tested it with a ctrlX CORE (V1.14.0). But I could not test the input form a mouse, cause I did not have a USB-C adapter at hand. Please have a look into the attached edited sample and try it out. Best regards, Nick

nickH · ‎05-05-2022

Hi, could you look at the diagnostics->logbook, enable system messages in the settings (click on the gear symbol) and filter for "snap.sdk-py-mouse-data.provider.service"? Maybe this could give you some information on what goes wrong. Additionaly I would recommend you to look at the python samples inside the SDK (V1.14) and compare them to the sdk-py-mouse-data sample. Maybe some dependencies got updated in the meanwhile. Best regards, Nick

nickH · ‎05-04-2022

Good morning, Please always download the SDK from releases (for example with: wget https://github.com/boschrexroth/ctrlx-automation-sdk/releases/download/1.14.0/ctrlx-automation-sdk-1.14.3.zip). Then unpack the zip archive (unzip ctrlx-automation-sdk-*.zip). Install the Data Layer debian package (sudo dpkg -i ctrlx-automation-sdk/deb/ctrlx-datalayer-*.deb). And change the mode for the flatc compilers in the SDK (chmod a+x ctrlx-automation-sdk/bin/oss.flatbuffers*/ubuntu20-gcc-*/release/flatc). If you setup your App Build Environment with version 1.14 you don't need to do this steps manually. You can just run the script (./install-sdk.sh) and it automatically downloads the newest release and does the steps I mentioned. install-sdk.sh: #!/usr/bin/env bash sudo snap install snapcraft --classic sudo apt-get install jq -y rm ctrlx-automation-sdk-*.zip* rm ctrlx-datalayer-*.deb* LATEST=$(curl -s https://api.github.com/repos/boschrexroth/ctrlx-automation-sdk/releases/latest) for i in {0..1} do FILTER=.assets[$i].browser_download_url DOWNLOAD_URL=$(echo $LATEST | jq -r $FILTER) wget $DOWNLOAD_URL done unzip -XK $(ls ctrlx-automation-sdk-*.zip) chmod a+x ctrlx-automation-sdk/bin/oss.flatbuffers*/ubuntu20-gcc-*/release/flatc chmod a+x ctrlx-automation-sdk/bin/framework/ubuntu20-gcc-*/rexroth-automation-frame find ctrlx-automation-sdk/ -name '*.sh' -exec chmod +x {} \; sudo dpkg -r ctrlx-datalayer sudo dpkg -i ctrlx-datalayer-*.deb

nickH · ‎05-04-2022

Hi, thank you for reporting this issue. There seems to be a bug in the documentation it has to be "text", not "textEnglish" and "number" (not "diagnosisNumber"). We are going to change that in the documentation. Some more information regarding this topic. The format of this JSON file got changed from V1.12 to V1.14. But the format of V1.12 should still work with a ctrlX CORE V1.14. See the two sample files (one V1.12 and one V1.14) in the SDK. I also changed the sample form the documentation to V1.14. You could use that as well (if the System apps on your ctrlX CORE are V1.14): { "mainDiagnostics": { "0E0A0666":{ "text": "Example diagnostic message", "version": "1" }, "0E0F2666":{ "text": "Example diagnostic error with priority 2", "version": "2", "detailedDiagnostics":{ "00000001":{ "text": "Example detailed diagnostic 1" }, "00000002":{ "text": "Example detailed diagnostic 2" } } } } }

nickH · ‎05-03-2022

Hi, the error you got from the ctrlX CORE, shows that you tried to install an app you build for base: core18 at a ctrlX CORE (V1.12 or newer) with core20 as its system app. So you have to build your app for base: core20 (e.g. snapcraft.yaml of a sample in the SDK). To do that you need a App Build Environment which is a Ubuntu 20.04 Linux operating system with a special set of software packages and certain settings. There are different ways to setup such a development environment. See this documentation on the different possibilities and how to setup one. Recommended is to setup the build in App Build Environment of ctrlX WORKS (V1.14). But you could also set up an App Build Environment manually using qemu (see this Video). WSL2 is not one of the possibilities, because it isn't an ideal environment for working with Snapcraft. See more here. Best regards, Nick

About nickH

Re: SDK USB Mouse Data Layer

Re: SDK USB Mouse Data Layer

Re: Issues buildin cpp sample from sdk

Re: How to use diagnosis/registration/register-file

Re: No connection to snap store