Hello Guest it is March 29, 2024, 03:56:30 AM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - petterman

Pages: 1
1
Finished Screens / Re: Mach3 2010 Screenset - Now available
« on: July 22, 2012, 06:03:07 PM »
Just upgraded to a new computer now, P4 3.0GHz, 9700pro, 1GB ram and with this setup all my earlier mentioned problems are gone, thanks for your input!


2
Finished Screens / Re: Mach3 2010 Screenset - Now available
« on: July 20, 2012, 12:21:25 PM »
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?

Quote
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

3
Finished Screens / Re: Mach3 2010 Screenset - Now available
« on: July 15, 2012, 08:54:52 AM »
Hi, I've having some problem using this screenset along with Mach3 R3.043.062. Sometimes during toolchanges my steppers stall out entirely. This never happens during normal rapids, just rapids caused by 2010 screenset. The problem goes away if I turn of toolpath display or unload my g-code file. Is there any workaround for this? My computer (XP 2500+, 1gb ram) should be sufficient to drive this config?

I'm using Gecko G540 as stepper driver, if that has something to do with it.
Other than the problem above I'm much pleased with the looks and feel of this screenset.

Thanks
Petter

4
Did this help with the stalling problem as well? I'm experiencing the exact same problem that you are describing. Stalling motors during move commands from 2010 screenset.

Pages: 1