03-12-2024, 01:55 PM
Dear community
I met some issues when I created a 3D printing project by importing .gcode file.
Firstly, when I added a file, RoboDK prompted me that some commands (G92) were not supported, as shown in the picture below.
Secondly, I have more than two printers working simultaneously, and the material deposition rates need to be constantly changed. So I added different characters, like U and V, to transfer the extrusion volume of each material, like "G1 X10 Y10 Z10 U10 F600". However, I can't find a method to obtain the U/V_value.
Thirdly, I realized from the examples that RoboDK provided more parameters, like %TOOL% and %ROBOT%, to meet cases where the command parameters are diverse. However, you know the general .gcode file for 3D Printing doesn't have these parameters, so if I want to add similar information to my .gcode file, what should I do?
As a result, I want to know if users can modify the rules for RoboDK to parse nc files. In addition, is there any relevant documentation that explains the existing parsing rules in detail?
Thanks for any advice!
Regards best!
Guoquan Zhang
I met some issues when I created a 3D printing project by importing .gcode file.
Firstly, when I added a file, RoboDK prompted me that some commands (G92) were not supported, as shown in the picture below.
Secondly, I have more than two printers working simultaneously, and the material deposition rates need to be constantly changed. So I added different characters, like U and V, to transfer the extrusion volume of each material, like "G1 X10 Y10 Z10 U10 F600". However, I can't find a method to obtain the U/V_value.
Thirdly, I realized from the examples that RoboDK provided more parameters, like %TOOL% and %ROBOT%, to meet cases where the command parameters are diverse. However, you know the general .gcode file for 3D Printing doesn't have these parameters, so if I want to add similar information to my .gcode file, what should I do?
As a result, I want to know if users can modify the rules for RoboDK to parse nc files. In addition, is there any relevant documentation that explains the existing parsing rules in detail?
Thanks for any advice!
Regards best!
Guoquan Zhang