Hmmm... Okay, I'd have thought you could make the DRO show whatever you want it to via a macro. (Don't know enough to talk any more about it.)

Here's a reference sheet I made for the buttons. Others may find it useful until they get used to their setup.

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

There are no macros running when you're jogging or running g-code. The CPU load is entirely due to the larger toolpath display. Unfortunately, Mach3's toolpath display is very resource intensive, and it sounds like your PC just isn't good enough to do the job.
I believe the other user with a similar problem was also running a single core Athlon. He tried a better video card, but it didn't help. He changed to a P4 and saw 10% or lower CPU loads.

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!

There's an open source pendant that works with Mach3 on Kickstarter right now.
If anyone using the 2010 Screenset is interested in it, I'll have modified versions of the 2010 screens available when it's finished.
http://www.kickstarter.com/projects/1651082654/jog-it-open-source-controller-pendant-for-emc2-and

Hello ger21 and all happy users,

I just bought your great screenset 2010 some days ago, and it looks great...

Unfortunately, I got some serious problems with:


I'm totally unable to start my VFD spindle with it.

I'm using the famous Huanyang VFD plugin. I can hear a relay "clicking" once but the spindle never starts.

When I enter a speed into the box and press enter, the speed goes to zero immediatly.


With default screen, spindle runs OK.

Of course, screenset is totally unusable for me.


Do you have any solution for me ?


Thank you !

Use the MDI to change the spindle speed. Just hit Enter, and type S10000 (or whatever rpm you want), and hit enter again.

The box displays the currently set speed, but doesn't allow you to change it. It sounds like your rpm is set to 0, so the spindle isn't spinning.

Mach3 defaults the spindle speed to 0 rpm. As a workaround, I add S10000 to my Initialization string in General Config, so that when I click Reset, it sets the spindle speed to 10,000 rpm, so it's never at 0. When I'm cutting, my g-code sets the spindle speed.

 Yeppeee ! Works !

 Thank you !



 I'm also looking for some informations about how the use a Webcam with Mach3/ScreenSet2010 to ease my life.

 (Off topic, I know ;-)

 
 Do you have any links ?

 Thank you again !

 

You should be able to set up the laser zeroing button to work with your webcam. I've never used one, but if you enter the offset distance from your spindle into the laser macro, then jog the machine until the webcam is at 0,0, then pressing the laser button should zero the spindle to the webcam location. See the manual for info on editing the laser macro.

I am very new to this so if my question sound lame bare with me. i have a licenced version of Mach 3. i made a plate that is .0641 thick, i want to use it to zero the top of my work piece. I have connected to an empty pin and tested the connection it makes (which works) . i have seen videos of machines touching off on a work piece then raise up a little and then come back down super slow and touch off again thus finding the work piece top, then the machine goes over to a permanent plate touches off and then it is ready to go. my question is how do I get my machine to automatically touch off on these plates and does the permanent plate connect to the same pin as the moveable one? i am assuming that this procedure is in the Mach 3 software. But I am unable to find out how. I have heard that you can write your own C++ program code to do this, but since I am clueless as to how to do that. is there some add on i can get, purchase, or a simple procedure to do this? Am I making sense?  thanks in advance guys