About nickH

Hi @Jerry  the App Build Environment (in ctrlX WORKS) runs in prot forwarding mode on your local host (127.0.0.1).  Per default the ssh port is forwarded to port 10022. So you can connect to the App Build Environment via "ssh -p 10022 boschrexroth@127.0.0.1".  If you want to forward another port from the qemu to the localhost of your windows you can add this port in the settings in ctrlX Works.    Best regards,  Nick ... View more

Hi @fl9  @Sgilk is right. The problems occurs because of the mismatch you have between the SDK Version (V2.4.3) you are using and the system apps you have installed on your ctrlX CORE (V1.14). I would recommend to use the same version with both. But at minimum the major version has to be the same.  So a recommendation from my side would be to update either to V1.20 and use the V1.20 SDK (this is the latest LTS version). Or update both the SDK and the ctrlX CORE (and ctrlx works) to the newest pre-release (currently V2.4, but tomorrow V2.6 will release).  Best regards,  Nick  ... View more

Hi @ctrlXW-ChrisB  first thing I would try is: uninstall the InfluxDB App delete the App Data of the InfluxDB App reinstall the InfluxDB App Best regards,  Nick ... View more

Yes you are right. The finalStateMachine() runs in a separate thread and not in the scheduler context. See Callable.cpp line 28-35:  //! Starts the final state machine in a separate thread. void Callable::finalStateMachineStart() { TRACE_INFO("#%d", m_instanceID); m_finalStateMachineState = FinalStateMachineState::IDLE; m_thread = std::thread(&Callable::finalStateMachine, this); } Thats why we can do a std::this_thread::sleep_for(std::chrono::seconds(1)) in line 196. And the watchdog ist not called.  ... View more

Hi @DanielToGo  I just tried to reproduce your error: Setup a new App Build Environment with ctrlX WORKS V2.4.  Ran the scripts "install-cpp-aarch64-libs.sh" and "install-sdk.sh"  And after that I ran "./build-snap-amd64.sh" in ~/ctrlx-automation-sdk/samples-cpp/datalayer.sharedmemory/  But I was able to build the snap and therefore I wasn't able to reproduce your error.  ... View more