- Posts: 2419
- Thank you received: 2349
Trajectory Planner using Ruckig Lib
- Grotius
- Offline
- Platinum Member
-
Less
More
2 years 3 months ago #306640
by Grotius
Replied by Grotius on topic Trajectory Planner using Ruckig Lib
Hi Arciera,
I can write gcode file output tomorrow, but clothoids & splines must then be converted to a G1 linestrip.
Then the overall output is G1,G2 or G3.
Is this ok for you?
I can write gcode file output tomorrow, but clothoids & splines must then be converted to a G1 linestrip.
Then the overall output is G1,G2 or G3.
Is this ok for you?
The following user(s) said Thank You: akb1212, Lcvette, Aciera
Please Log in or Create an account to join the conversation.
- Aciera
- Offline
- Administrator
-
Less
More
- Posts: 4819
- Thank you received: 2177
2 years 3 months ago #306643
by Aciera
Replied by Aciera on topic Trajectory Planner using Ruckig Lib
Don't worry about it, it's really not important.
The following user(s) said Thank You: Grotius
Please Log in or Create an account to join the conversation.
- Grotius
- Offline
- Platinum Member
-
Less
More
- Posts: 2419
- Thank you received: 2349
2 years 3 months ago - 2 years 3 months ago #306645
by Grotius
Replied by Grotius on topic Trajectory Planner using Ruckig Lib
Hi Arciera,
Ok, I will not worry about it.
I tried a free gcode file, a griffins logo. File about 14000 lines.
www.cnccookbook.com/g-code-examples-file...for_Milling_Machines
In the file no G64 P.. Q.. was given. Raw output :
Then i added G64 P0.1 Q0.1
The output :
Then without the velocity display :
The purple are all clothoids. Cyan is spline, White is line.
File specs :
items G64 P.. Q.. before:14151 after:28292 diff:-14141
So the gcode file is increased by 14141 segments.
Maybe test some more files?
Ok, I will not worry about it.
I tried a free gcode file, a griffins logo. File about 14000 lines.
www.cnccookbook.com/g-code-examples-file...for_Milling_Machines
In the file no G64 P.. Q.. was given. Raw output :
Then i added G64 P0.1 Q0.1
The output :
Then without the velocity display :
The purple are all clothoids. Cyan is spline, White is line.
File specs :
items G64 P.. Q.. before:14151 after:28292 diff:-14141
So the gcode file is increased by 14141 segments.
Maybe test some more files?
Last edit: 2 years 3 months ago by Grotius.
The following user(s) said Thank You: akb1212, tommylight, Clive S, Lcvette, Aciera, Darium
Please Log in or Create an account to join the conversation.
- Aciera
- Offline
- Administrator
-
Less
More
- Posts: 4819
- Thank you received: 2177
2 years 3 months ago #306651
by Aciera
Replied by Aciera on topic Trajectory Planner using Ruckig Lib
The following user(s) said Thank You: akb1212, tommylight, Grotius
Please Log in or Create an account to join the conversation.
- Grotius
- Offline
- Platinum Member
-
Less
More
- Posts: 2419
- Thank you received: 2349
2 years 3 months ago #306657
by Grotius
Replied by Grotius on topic Trajectory Planner using Ruckig Lib
The following user(s) said Thank You: akb1212, tommylight, Lcvette, Aciera
Please Log in or Create an account to join the conversation.
- Aciera
- Offline
- Administrator
-
Less
More
- Posts: 4819
- Thank you received: 2177
2 years 2 months ago #306662
by Aciera
Replied by Aciera on topic Trajectory Planner using Ruckig Lib
I understand that lowering the value will create smaller deviations. What I'm concerned about is the predictability of the maximum deviation a certain G64 Pn Qn command is going to produce as knowing this is crucial for CNC application.
I know we've had this discussion before but if 'G64 P0.1 Q0.1' means a maximum path deviation of 0.1 mm then those white GCode lines would have to be 0.1mm apart which seems a bit hard to believe (but of course I do not know for sure).
I know we've had this discussion before but if 'G64 P0.1 Q0.1' means a maximum path deviation of 0.1 mm then those white GCode lines would have to be 0.1mm apart which seems a bit hard to believe (but of course I do not know for sure).
The following user(s) said Thank You: akb1212, Grotius
Please Log in or Create an account to join the conversation.
Time to create page: 0.331 seconds