RT-samples in com.boschrexroth.sdk.control.rt-2.6.0 causes the automationcore process to restart

I downloaded com.boschrexroth.sdk.control.rt-2.6.0.zip and compiled the scheduler and dl-shm-owner examples from samples-cpp for testing. Both examples cause the entire rexroth-automation-frame process to restart during the first startup loading process. They only work correctly on the second load.

The first run shows "Stopping Service for snap application rexroth-automationcore.control" after registering the component sdk_rt::ShmOwner.

After the rexroth-automationcore.control service restarts, the second load is successful.

The issue has been occured on both the Virtual 2.6.4 system in CtrlX Works and the 2.6 system on the CtrlX-X7.

Attached is the complete log information I obtained from "snap logs -f rexroth-automationcore."

Hi Maron

I got news for you regarding this issue. Its actually not a bug but designed as it is. The restart of the automation-core will happen if an app, which is not signed is installed and provides a bundle with the slot "automation-bundle-v3". So this happens for all SDK-samples and for your own project (as long as the app is not signed).

Background: The app rexroth-automationcore restart is initiated by snapd or systemd because the SDK samples snaps are not signed. The restart of rexroth-automationcore occurs on first install of any unsigned RT-SDK snap in order to connect the content interface "automation-bundle-v3". So that the rexroth-automationcore is able to access the bundle provided by the unsigned snap. There is no restart on update/reinstall of the snap. There will be no restart when installing an app for productive use since these apps should be signed.

Learn more on how to get your app validated and signed: Customer App Support Services

Best regards,

Nick