Closed zxvcv closed 3 years ago
Similar bug exist in U12 command
after "on board test" few things showed up:
Bug was caused by wrong start point of the calculations (it should be end point from previous calculation step but taken was current position (wich is almost same value but with position error)
missclick
CounterClockwise circle move (U13) and brobably G3 is not working properly. It throws an error while comand is invoked. in this example start value U13 should be same (or very close to) end value