by Vmax549 » Fri Apr 26, 2019 7:35 pm
So just to be clear can we assume that this issue was fixed in UCCNC as per V2103 ?
V2103
- An issue with full circles execution was fixed, that if the software was forced to syncronise with the motion controller after a motion which movement gave the startpoint of the arc and then the full (360°) circle was executed after the code which caused the syncronisation and if the 1/steps per value was not an integer divisor of the endpoint then the circle was in some cases no more understood as a full circle by the motion software, because the syncronisation caused the start coordinates and the end coordinates to become different points, because the steps per value did not allow the programmed coordinate by resolution and so then the circle might not be executed depending on which side the start coordinate offset. The issue was fixed with the controller is now not syncronising the coordinates while in cycle except for certain operations which require the syncronisation.
- Rigid tapping and Thread cutting possibly missed to make the syncronous motion in some case (~1 out of few hundreds usually). This was fixed for the ethernet controllers only in the previous release and now the same was fixed for the USB controllers.
Just to confirm, (;-) TP