Hello,
by operating with WD you avoid the topic. Means the WDs - even with expanded setups - will provide more access of the ctrlX.
Running the system without WD into a endless-loop will cause high load on the core the PLC-Task is calculated and all task with lower-Prio will be suppressed. Communication of the web-sites is effected etc. Trying to get in contact with the ctrlX-PLC Eng will run in Timeout-topic. Goal would be natural to bring the PLC in Stop. Remember the Endless-loop is not a bug in terms of system-behaviour. If a) the PLC-website can not be loaded, b) the PLCEng is not connectable the Rest-Api be supported. If not - the deactivation of the PLC-App will be possible, even several trials may be needed to trigger the switching to 'Service' - mode. Activating the PLCApp again will bring the PLC in Stop-mode. Low load will the result - connecting with PLCEng is possible again. Flashing the image can be avoided by that!
If the above is not feasible:
Sending the control for service can be avoided just by re-flashing the ctrlx-runtime - image again (system-apps). Placing a microSD with the Image makes the ctrlX to 'boot' with external memory content.
The topic is described within the release notes or https://docs.automation.boschrexroth.com/doc/3417946415/hardware-reset-of-the-ctrlx-core-and-the-ctrlx-drive-plus-with-integrated-ctrlx-core/1-06/en/
Bye
... View more
