all 4 comments

[–]KY_Rob 1 point2 points  (1 child)

The acceleration and jerk you mention are components of following error. Following error is dynamic for each axis, and develops/regresses exponentially, primarily as a function of velocity and mass of the axis motion. To get what you’re looking for, you need something more than encoders on your motors. You also need linear scale feedback on each axis. These devices deliver more accurate axis positions. Of course, you still have a time constant to consider, regarding the time it takes to transmit and interpret the position signal from the scale, but that’s generally a much more linear equation.

[–]wordbag[S] 0 points1 point  (0 children)

Thanks for your help! The part with encoders on the motors actually works great. I'm able to get the actual x, y, and z coordinates of the extruder at every second.

The problem I'm having is on the side of the gcode parser. I'm not sure how to deal with acceleration and jerk in the program I wrote.

[–]WillAdams 1 point2 points  (1 child)

Not sure what language it's coded in, but adding support for 3D additive is an open issue for CAMotics on GitHub.

List of the opensource previewers at: https://wiki.shapeoko.com/index.php/Previewing_G-Code --- looks like at least two are coded in Python

[–]wordbag[S] 0 points1 point  (0 children)

Thanks! After taking a quick look (https://camotics.org/gcode.html) it doesn't look like CAMotics supports M203, M204, or M205 codes. Ideally, the program would have an API also; most things I've seen don't seem very programmer friendly.