just looking at your xml, it has 2000 steps per unit, what hardware do you have as that seems rather low for being set up in imperial units.

Is it steppers? Do your drives have micro stepping? what gearing? whats the ballscrew pitch or TPI?

Hood

Oh O...  I'm not sure I posted the correct xml file.  I'm using the SyilSX3.xml configuration file that Syil created.  Is that the xml file I need to post and not the mach3 file.

Just in case, here's the Syil xml mach3 config file.

yes thats correct, if you are using the syil then thats the profile you will want, will go load that and see

Hood

Sorry took so long but I had to modify your xml to reflect my pin asignment.
OK first thing I noticed is you have the kernel set to 35KHz and your motors are tuned faster than that so try setting to 45KHz and see if that helps. Also you have ES set in the General Config page, you want to change that to CV. For this file it shouldnt really matter as you have a G64 in it but just for future.
 Also might be good to set Persistent DROs on the General config page and maybe even persistant tools but that will depend on how you do the tool changes etc.

I tried your file and your xml and it runs fine for me, certainly none of the jerky movements you are seeing, think maybe the Kernel speed change may help you out.
Hood

Oh another thing you might want to change is the Auto Limits OverRide on the settings page but you would have to enable your limits and that depends how your switches are set up. Usually if your switches are activated at either end of the axis travel you can use them as both Home and Limit switches.

Hood

Sorry took so long but I had to modify your xml to reflect my pin asignment.
OK first thing I noticed is you have the kernel set to 35KHz and your motors are tuned faster than that so try setting to 45KHz and see if that helps. Also you have ES set in the General Config page, you want to change that to CV. For this file it shouldnt really matter as you have a G64 in it but just for future.
 Also might be good to set Persistent DROs on the General config page and maybe even persistant tools but that will depend on how you do the tool changes etc.

I tried your file and your xml and it runs fine for me, certainly none of the jerky movements you are seeing, think maybe the Kernel speed change may help you out.
Hood

Maybe, it's the laptop I'm using is not fast enough.  The interrupt value seems to hover around 10 ish.  I saw a Mach video tutorial or doc somewhere that described typical numbers.  I don't recall what was good numbers or not.  I seem to recall values around 2-3 being good.  Maybe, the laptop is not up to the task.

Well, that could just push me over the edge to get a real PC and not use the laptop.  I have a MPG that I can't hook up to the laptop since I can't seem to get a 2nd parallel port adaptor to work on the laptop.  USB to parallel doesn't work and I haven't tried a PCMCIA adaptor to parallel yet.

On the debug screen there is a blend box.  When I run the code I see values changing in this box.  Maybe, this is a value relating to CV when it's combining one line to the next possibly the blend value shows the amount of stitching is being performed.

I modified the feed rate to 1.9 on the G1 and G2 commands in the sample test file and it still comes to a complete stop between each command.  It's almost like there is a delay value execution number that is appied between each Gcode line.

Are there other tests that I can perform to isolate this more?

I've learned quite a few things from this.  I have a better handle on G61, G64 commands and how to create G2 commands in two formats.

I am only guessing that the non smooth threadmilling is the cause for rough threads.  Since I can't make it run continuously smooth I can't verify if that is indeed the culprit or it's just the way it is.

The other thing I learned is that when pressing the stop on Mach you can lose a few steps.  Now I know when I crash my tool into my part I should go back and verify my X and Y zeros.

I have checked persistant DROs.  Doesn't seem to work.  I exit the program and restart it and find the DROs have new numbers.  Bummer!

Thanks for the help.  Going to bed now.  It's 3am in the morning.

Wayne

Ahhhhhhhh laptop, now thats a bad word LOL
 ok do the drive test and see what that looks like, also try the optimisation steps and look to see if there are any power saving options set up in device manager.
 Did you try with the Kernel set to 45KHz?

One thing you might want to look at is the SmoothStepper, its still Beta but works well and the few things that are still to be implemented should be done shortly.
 Hood

Another thing to check is make sure your xml is not read only (can be if you copy from a CD) Also when you make a setting change you could try using the save Config option, think its under the config menu.
Hood

I don't want to compromise anything on this machine.  The laptop came configured when I bought the machine.  Since I can't hook up the MPG to the laptop it's time to dump it and get a real PC.

I've ordered a PC to be configured with two parallel ports so I can run the machine and have the MPG hooked up.  I'll get the PC on Tues and will report back if it has resolved the CV problem.  Hopefully, the answer will be yes.

No matter...  Hopefully, I'll be able to use the MPG I have.

Thanks everyone for all the help.  I'll let you know what happens with the new PC when it arrives.

Wayne

Just a follow up and a FYI for someone else that may have this sympton.

After getting the new PC hooked up and configured I was totally bummed as the new PC did exactly the same thing.

What I discovered was that if I raised the kernel from 25K to 45K on the laptop it would time out.  The laptop can't run that fast.  I finally found the setting in the ports/pins configuration.  Not sure why it's there an not in the general configuration section.   

When I upped the kernel rate on the PC there was no issues.  Still the program paused or ramped down and up at each line.

I finally found that disabling the backlash solved this.  Enabling backlash again confirms the start/stop and disabling backlashed it runs continuous from line to line.

So, the PC was not all in vain.  One issue down...  Now to go play with the MPG.   

Wayne