I was typing this in response to the post you made in the other thread, but I'll place it here instead. I think your issue may be due to #1?
I'm experiencing the exact same problem that you are describing. Stalling motors during move commands from 2010 screenset.
I've had 4 users come to me with this issue. It's probably one of two things.
1) If you have a dual core processor, go into the bios and disable either C1E or EIST.
this fixed the issue for 3 people.
2) the 4th user was using an old PC that just wasn't capable of displaying the larger toolpath. Open the task manager and check the CPU usage with g-code loaded. Then turn the toolpath on and off with the toolbar button. The user that had the problem was seeing 90%CPU usage without the machine even running, but only 3% with the toolpath turned off.
If this is the issue you're having, the machine should run smoothly with the toolpath turned off. But you really need a better PC.
Hi again, thank you for your response. As mentioned earlier I'm running on a Athlon XP 2500+ which is a single core processor.
I've done some tests and it seems that something in the 2010 scripts puts a good load on the CPU.
While running a normal job, and when manually jogging at full speed I'm experiencing a CPU load at maximum 60% from mach3. But the load spikes during rapids caused by 2010 macros. The CPU then reaches near 99%, but only when display toolpath is checked, otherwise it's stable at 20-30%.
Could this be some kind of bug in the isMoving() command or is it the While IsMoving() that's eating up this load? If this is the case can't a delay be added to lengten this loop?
As a really ugly solution would it be possible to turn off the toolpath display during these moves?
Somehow I get the feeling that this computer should be enough to power Mach III, could be wrong though;)
Again, thanks for the support //Petter