Somebody needs to run this on their machine to believe me. If you can't duplicate this I will make a video and post it to prove this. I understand how CV works.  I have two of my units and one other of my friend's units doing this and they use completely different hardware.

Basically if you try and 3d contour with exact stop the machine is going to sound jerky like a machine gun stopping at every little point along the way. In CV mode it runs smooth through the points cause it calculates the trajectory accel and decel based on the lookahead. Then we can control how continuous through a target radius. I get it. I've been using it and watched it get better since mach2. Then on one of my upgrades, I'm not sure which one its backwards. It's working backwards so when its off its on, when its on its off.

Maybe I have a bad install or there is some other cause of this, corrupt xml or something but I don't believe so. CV Feedrate is off, CV limit angle is on and set to 179, CV dist tolerance is on and set to anywhere between 1mm and 0.05mm depending on the scale and geometry of my part.

We'll see what Hood has to say in the morning. Thanks for your attention on this issue.

Brian

I have just run your code on my mill, changed to G21 (also a return after the M30) but other than no change to the code. Didnt have any CV setting and ran it smoothly , entered CV settings and ran again and no difference. G61 and ran again and as expected it was jerky, changed CV settings to off again while using ES and again exactly the same as before so afraid I am not finding what you are getting.
 I tried the above with Version 3.042.007, 3.042.008 and 3.041 and also tried with SmoothStepper and Parallel Port.

What are your CV settings? and I will try with exactly your settings.
Hood

Here is a video of my problem.

http://www.jbdstudio.com/cv_vid.wmv

Here is my xml

http://www.jbdstudio.com/xml.zip

The problem is CV dist tolerance. Wha I have learned is something has changed in your trajectory code where targeting a small radius the accel decel planning is not nearly as fast as it used to be. I used to always run with the dist tol on set to a small number and get really nice crisp parts. I ran parts last night with it off and they seem to fine and its running smooth. I bumped my radius up to .5mm. I Used to get the same accel decel at .1 that I now only get at >.5.

So the real issue is something changed with CV dist tol, but I seem to be doing ok without it now. Now I'm not sure if there is a bug or maybe now CV distance tolerance is working properly and maybe before it never did.

Brian

Brian, I am back home now so cant test it out with your settings, will be at the workshop tomorrow and see but looks like you are happy withthe way it works now, I think?
Hood

Basically there have been some changes made to CV and my settings no longer ran my machine like they used to.

I used to be able to use really small CV dist tolerance values and the machine ran fast. My values now have to be much larger
to keep the speed up.

Is it as good as before with the increased settings?
Hood

So far I cut 3 jobs and it seems to be performing without putting any large radius on my parts sharp corners that I'm contouring on and my feeds are
in the same 400mm/min-1000mm/min range. So at a quick glance yes, I really appreciate your responsiveness on this matter. I will let you know if I have any more troubles.
 

So previously you were at 0.05 and now? will try it out tomorrow and see.
Hood

So with further testing and thinking I had this licked I am seeing the real problem.

When raster cutting along XZ-axis while indexing the part with a rotary table A-axis I am having CV issues. The issue is that the velocity is not continuous as if you set it into exact stop mode or turned on CV dist tol and made the tolerance really really small.

If I open up a new session of mach and load the code and run it it works great. If I make changes to CV dist tol value, turn CV dist tol on/off, feedhold, stop, start, restart or some combination of those commands is when it starts having issues. It will act as if its in exact stop mode making it take forever to machine my contours.

The trouble is I don't know what the combination of commands is to repeat the bug. I just know that it does happen enough to cause me headaches in ver 3.41 and 3.42.015. I will be trying to figure out exactly how to reproduce the error repeatedly. Does anyone have any inclination to what the issue may be or have they seen this before. Attached is code that it happens on.

Brian