New development; I created the same job in Vectric Cut2D, and it worked like a charm. I don't think it's got anything to do with my machine, PSU or heat. The G-code created by CamBam does something that makes the motors skip a step. Until I find out what, I'm going to have to get a new CAM software.
I've been traveling so it's been hard to reproduce this, but I noticed some rough movement in the file(s) you gave me. I've been diagnosing the problem as I have time. I suspect it has to do with some of the very short arcs being output by Cambam. You might also try disabling arc output from CamBam, which I think it can do.
I'd like to find a way to run these files even if the Cambam arc output causes problems., It's probably some corner case that hasn't been dealt with. So I'm going to keep diagnosing this.
Arcs converted into lines, made the machine stutter a lot as it accelerates/decelerates through tiny line segments. Stepper motors skipped steps here aswell, just in different places than it used to.
I'm going to check the EMC2 post processor directives in CamBam, and put in very conservative values.
Either should do. It's easier to use the hex but being able to compile your own definitely has its advantages. Please heed caveats on the use of the dev branch. It's EXPERIMENTAL. I hope to push these changes to edge in the next week or so.
This topic is from the original forum (October 2013). Your reply starts a new discussion linked to it.