FORUM CTRLX AUTOMATION
ctrlX World Partner Apps for ctrlX AUTOMATION
Dear Community User! We have started the migration process.
This community is now in READ ONLY mode.
Read more: Important
information on the platform change.
04-18-2023 08:52 AM
Hi I tried to execute the sample code below but i kept getting stopped out by watchdog feature.
Solved! Go to Solution.
04-18-2023 10:56 AM
Hello !
viewing the code-example makes me convince that the WD is expected correctly... the While loop runs and will consume time .... till the WDTime is reached... if a WD time is setup,
If not I would expect - becasuse of the endless loop - a PLC WD/Exception as well.
Do you disagree - did I get it wrong?
Bye
04-18-2023 11:13 AM
Hi I do acknowledge that the while loop will cause a watchdog error here. But is there an alternative solution to this? i tried disabling the watchdog feature, and my corex became unresponsive straight away. Had to sent back to LOHR for repair.
04-18-2023 12:01 PM - edited 04-20-2023 02:09 PM
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-ctr...
Bye