[KUKA] Remove unnecessary & annoying tasks throwing errors at timeout when proper message from the component is present#1167
Merged
Conversation
Record the KRC5-only fix (AxoKrc5 tasks no longer ThrowWhen on ErrorTime/TaskTimeout) across library and central changelogs. - AxoKrc5.md: 4th KRC5-only divergence + Configuration note - TROUBLES.md: TaskTimeout watchdog bullet flagged KRC4-only - library CHANGELOG + GitVersion: bump to 0.61.1 - central CHANGELOG: [FIX] AxoKrc5 spurious task-timeout entry Refs #1167
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
AxoKrc5no longer throws spurious task-timeout errors when the component has already reported the proper condition.ThrowWhenwatchdog calls (_errorTimer.outputandDuration >= Config.TaskTimeout) from all eightAxoKrc5tasks.AxoKrc4is intentionally unchanged and keeps both watchdogs.0.61.1.Changes from CHANGELOG
[FIX]
AxoKrc5no longer throws spurious task-timeout errorsNote: PLC bug fix in
src/components.kuka.robotics/ctrl/src/AxoKrc5/v_5_x_x/AxoKrc5.st. KRC5-only —AxoKrc4is unchanged. No public-API change. Branch:1165-bug-kuka-issue-with-robot-reset.ThrowWhenwatchdog calls (_errorTimer.outputandDuration >= Config.TaskTimeout) from everyAxoKrc5task —StartAtMain,StartMotors,StartProgram,StartMotorsAndProgram,StartMotorsProgramAndMovements,StartMovements,StopMotors, andStopMovementsAndProgram. A stalled task now surfaces through the component's own status message instead of an additional, redundant task-timeout error that fired even when the component had already reported the proper condition.src/components.kuka.robotics/docs/AxoKrc5.mdandTROUBLES.mdrecord the divergence (a 4th KRC5-only difference;ErrorTime/TaskTimeoutno longer abort KRC5 tasks; theTaskTimeoutwatchdog troubleshooting bullet is now flagged KRC4-only). Library CHANGELOG bumped to0.61.1.Impact: Operating a KRC5 robot no longer produces nuisance task-timeout errors on top of the component's genuine status message.
AxoKrc4retains both watchdogs.Risks/Review: KRC5 tasks no longer self-abort on duration; long-running or stuck tasks rely on the component status message and operator intervention rather than the
TaskTimeoutwatchdog.Commits
docs
Other
Diff stat
Test plan
apax build; affected KRC5 sequences exercised in PLCSIM Advanced (verify no spurious task-timeout errors during long/stalled tasks)Generated by
/pr-description-update. Last regenerated: 2026-06-01.