Hi,
I have set up a machining project for 3D printing using the recommended Slic3r software. When I am using relative E-values for the extruder instead of absolute values, RoboDK loses a lot of Extruder calls. Maybe that's due to rounding errors. Anyway I do not think RoboDK is supposed to behave this way.
The error of one single skipped Extruder call is of course neglectable but it accumulates throughout the program.
I attached the RoboDK files for relative and absolute E-values and additionally the first part of the equivalent g-code (also prepared with Slic3r) as text file (the g-code file is not allowed as attachment and the complete txt-file would be too large).
Please have a look into that, especially the programs and tell me how you think about it.
I have set up a machining project for 3D printing using the recommended Slic3r software. When I am using relative E-values for the extruder instead of absolute values, RoboDK loses a lot of Extruder calls. Maybe that's due to rounding errors. Anyway I do not think RoboDK is supposed to behave this way.
The error of one single skipped Extruder call is of course neglectable but it accumulates throughout the program.
I attached the RoboDK files for relative and absolute E-values and additionally the first part of the equivalent g-code (also prepared with Slic3r) as text file (the g-code file is not allowed as attachment and the complete txt-file would be too large).
Please have a look into that, especially the programs and tell me how you think about it.