Machsupport Forum
Mach Discussion => General Mach Discussion => Topic started by: rlrhett on August 09, 2009, 11:21:09 PM
-
After I installed the latest version of Mach3 I started getting a wierd start stop motion. It did not do this before.
In motor tuning the motors move smooth as silk. Likewise I can jog smoothly. However, if I run a program I get this wierd start/stop motion. Same if I tell it to go to zero. It will run for about a second, come to a complete stop and then continue after a half second pause. Any ideas? It will haltingly pulse its way through the program otherwise normaly. Rapids seem about the right speed and feed rate seems right --when it is moving. I can't figure out why it is coming to a stop.
All 3 axis stop and start at the same time.
PS: I did a "Restore Settings...." which took me all the way back to raw default settings, and I am still getting this weird motion.
-
Look in your code and see if there is a G61 on the first few lines, if there is replace it with G64. If there was no G61 then put a G64 in on the first line anyway.
See if that helps.
Hood
-
No, unfortunately that did not seem to do anything. I still have the wierd motion.
-
Please attach your xml
Hood
-
Where do I find that? Sorry, big noob.
-
If you are using Mach3Mill then look for a file called Mach3Mill.xml, you will find it in C:\Mach3 folder. If you have any other profile then it will be the name of that profile.xml.
Another quick question, do the DROs show the movement stopping as well and is it 029 version of Mach you are using?
Hood
-
Found the xml. Thank you. I suppose if I had just looked it would have been obvious. Sorry.
As to version: Version R3.042.029. In fact, the problem started when I upgraded to this version.
As to the DRO's, they don't update smoothly even when the motion is smooth. In other words it doesn't scroll where I see, e.g., 3.000 followed by 3.001 followed by 3.002, etc. It is more like 3.000 followed by 3.148 followed by 3.1786 etc. They seem to update in blocks. Again, this happens even though the motors are moving smoothly. I don't know if that is normal.
HOWEVER, when it is running g-code it stops at regular intervals and the DRO's show the stops. For example, if I start from x0y0 and g0 to x10y10 it will travel EXACTLY 2.5328" on both axis, stop, then travel 2.5328" more, stop, etc, until it reaches x10y10. The DRO's will show: 0.0000, then 2.5328, then 5.0656, then 7.9584, etc. It does this to both axis in sync. I can run the g-code back and forth from x0y0 and x10y10 and it will always stop at the same places.
If I move just one axis instead of two at a time, the distance changes (2.5926" at rapids) but will always stop at the same distance. if I do g1 rather than g0, the distance changes depending on the feed rate. However, if the feedrate doesn't change the stops will all be at the same distance.
I hope that tells you something, because I am totally stumped.
Thanks,
-
There seem to be a few that are running into problems with ver 029, try going back to your older version.
Hood
-
Unfortunately, changing versions has NOT helped. I have uninstalled the driver AND the software, deleted the Mach 3 folder and reinstalled R3.02. No change.
This is very strange. Jogging moves flawlessly. I assume when I jog using the virtual pendant I am sending pulses just like if I was running g-code. I can't imagine what the difference is. Likewise, when I move the motors in motor tuning mode the are smooth as silk. However, the moment it tries to run g-code I get these predictable stops.
Is there perhaps someone from Artsoft that may have a suggestion?
-
Attach your code please, I have looked at your xml and it seems fine with the exception you have Output 1 enabled and set to Port 1 but you have it asigned to Pin 0.
Hood
-
I am not sure what you mean by 'attach your code'. What code?
-
I am not sure what you mean by 'attach your code'. What code?
I mean this code
However, the moment it tries to run g-code I get these predictable stops.
Hood
-
All code. Any code. From the Roadrunner to simple one line "g0 x0 y0" or "g1 x10 y10". I am NOT having this problem just with one file. I have this problem on all g-code files.
As I said in post 12, I can go to the MDI screen and enter "g0 x10 y10" and it stops at consistent intervals. It doesn't matter what g-code I use.
It makes me suspect something about the difference between the way Mach3 generates pulses from g-code as opposed to generating pulses for a jog command or in the motor tuning mode. Unfortunately, I don't know enough about how Mach3 does what it does to be able to speculate why it jogs smoothly but executes g-code with these stops.
Does that suggest anything to you?
Thanks,
-
Do the DROs show the stop start motion or do they count smoothly?
Run the driver test and see if that looks good.
Hood
-
The DRO's show the stops exactly. The driver test shows very good results with very little latency.
-
That is weird, I have tried your xml here and it works well. The only thing I see wrong in your xml is you have Output 1 enabled but you dont have a pin asigned to it but that shouldnt cause the problems you see.
As you dont have a great deal set up in ports and pins it might be worth making a custom profile from scratch and trying that.
Hood
-
THat sounds like the old quicktime syndrome. Something is interupting your driver in pulses. While running a file, open the task manager and check for other programs running , also check the performance monitor for spikes in the cpu load that coinside with the stops.
(;-) TP
-
HALELUJA!!!
I have a dedicated computer for this, and I thought I had stripped all non-Mach 3 software. Somehow, I had forgotten to delete iTunes from the system.
No iTunes -- No wierd motion! Thank you sooo much!
-
GOOD JOB dude, (;-) TP