About nickH

Hi Jordi unfortunately there is not much to find in the manual at the moment.  The schedBackground task is always available in the default configuration of the scheduler, without any additional app installed. It runs at a low priority and is used for background tasks, like persisting the nvram.  The task motionHighPrep gets created with the installation of the ctrlX Motion App. The callable inside this task will prepare a motion command for the execution, which is send unbuffered to the motion app. For that it needs to prepare the command very quick in a very high prior task.  Best regards Nick ... View more

Hi @Josaphat_Aviles,  There is not an easy answer to your question, which would fully answer it. I would recommend you to learn more about C++ in general. There is good literature and also videos you can find online. This would be something you learn in a course about C++ in university for example. But I attached a little example for you. In this example I edited the hello.world example from the ctrlX Automation SDK and instead for printing out directly something to the logbook I used my self-created shared library (libSharedLibrary.so). Some things you need to do, so it will work: link the library in the CMakeLists include the header (interface description of the library) in your main.cpp include the library in your snap (so it is available at runtime) possibly change the environment variable LD_LIBRARY_PATH (see also this post in the community) Best regards,  Nick   ... View more

Just one more comment:  As far as I know, daemons ALWAYS have root access within their area of confinement.  (See, for example, comments by ogra here.)  If you have configured your app to run as a daemon - the typcial use-case for ctrlX CORE - then access generally is a question of broadening the area of confinement via the plugs mechanism (i.e. setting up the plugs correctly) and never one of "sudo". ... View more

Hi Chriss,  you could implement a logic, after you get the result "ALREADY_EXISTS", that does a Data Layer Read to "datalayer/security/scopes/<your_scopename>" and checks if the content matches what you are expecting. Or you can also keep it simpler and just send a write to "datalayer/security/scopes/<your_scopename>" and overwrite the value at the scope.  Best regards,  Nick ... View more