Skip to content

111: No sleep before waitForMoving()

Torsten Bögershausen requested to merge torsten/111-no-sleep-before-wait into master

There was a dynamic sleep before calling waitForMoving(), to "jump over" the acceleration phase. However, this leads to problems on "fast axes": (especially testing agains a simulator) The sleep was too long, the axis had already moved to it's new destination, and axis.waitForMoving() could not detect any movement, because that was already done. Solution: Remove the sleep() and add the old sleep time into the timout when calling waitForMoving()

Merge request reports