Hi JFCh,
I've been juggling with that idea for some time now.
Could being able to split the Gcode into parts would work? I'm not in charge of the development, but I'm trying to see if we could have an easier solution to implement on our end.
Like if you could run the path until a certain location, "split the gcode" and create a new Robot Machining project with the rest of the program, keeping the same settings and all, but allowing you o use a different Z rotation.
We had another client doing robot milling that had the same request as it was physically impossible to run the process in one blow without collisions.
(No promises here, just discussing the potential approaches to solve that kind of situation.)
Jeremy
I've been juggling with that idea for some time now.
Could being able to split the Gcode into parts would work? I'm not in charge of the development, but I'm trying to see if we could have an easier solution to implement on our end.
Like if you could run the path until a certain location, "split the gcode" and create a new Robot Machining project with the rest of the program, keeping the same settings and all, but allowing you o use a different Z rotation.
We had another client doing robot milling that had the same request as it was physically impossible to run the process in one blow without collisions.
(No promises here, just discussing the potential approaches to solve that kind of situation.)
Jeremy
Find useful information about RoboDK and its features by visiting our2022世界杯32强赛程表时间
and by watching tutorials on ourYoutube Channel.