after trying out the sample from the ctrlx-sdk (automation.scheduler)
we get a watchdog error, if we swap from operation mode into service mode.
The actual error:
Is the sample still up to date / supported?
Is there more detailed documentation?
Looking forward to hear from you,
Solved! Go to Solution.
Please beware that the SDK version (1.10) has to fit to your system version (automation core + device admin 1.10) so that the used interface are fitting.
At the moment no problems are known with this example and it is working on my control:
our version was correct, also our SDK.
But we found out that the problem is with the scheduler.
If you make an own task, our program and the sample from github
causes a watchdog Error. If you add the Callable to the ctrlXAutomation-Task
it works fine. Why is the sample not working under a own task?
Is this unknown or undefined behaviour?
Where's the documentation for it? It was fustrating to figure it out.
That is quite easy to explain because of the structure of the system. As a realtime bundle snap you are part of the CELIX framework in which environment also all other real time applications are running. So if you take a part of the code out of the task scheduling of all the others you will break up the timing behaviour of the complete project and cause a watchdog to occur.
I do not get you question. As a bundle you always add an own callable to the system that has to run in your realtime task (for deterministic purposes). If you want to have an independent task simply use a non bundle snap.