>>3. I'd be looking at why your CAM produces so many lines of code. It seems excessive to me. Are you for example converting arcs to lines unnecessarily? Also take another look at the pic I posted, why have the lines suddenly changed from around 3 hundredths to 7 thousandths for no apparant reason?
This was the root of your trouble. CV was the cure in this case, but M3 ( and all controllers) have a problem with very small
segmented motion at times. Its a question of predictability. Even if in CV mode, a trajectory planner has to computer various
equations on accel, velocity and time on each segment as part of the process. Tell ArtCam (or what your using) to put out in
lower resolution and it gets much smoother.
CV of course must be used in this type of file, but it works best with larger segments, it always has. Ignore the microstepping
stuff ( my advice), I use as high a micro-step as I can, balanced with speed, if I need more speed Ill lower the micro-stepping,
but in general , and in almost all cases, the higher the micro-stepping, the smoother the motion..
Higher micro-stepping also allows using higher frequencies to control with , and the higher the kernal base frequency,
the smoother the motion as well. For steppers, micro-stepping is pretty much unavoidable for performance..
Nice to hear you've smoothed out.
Art
Art