Machsupport Forum
Mach Discussion => General Mach Discussion => Topic started by: striplar on October 19, 2014, 10:42:57 AM
-
I'm using Mach3 with an ESS and the Aqua Screen set. I'm finding there are serious issues with resuming after pausing.
I've seen this on several occasions now and it's quite alarming. After pausing and turning off the spindle using the screen button, I find that the feedrate resumes at a very much faster rate than when it stopped. Whether this is an issue resulting from me pausing when the feedrate is overridden or not I'm yet to discover. Needless to say, it's not very safe when you're already cutting with as high feeds and speeds as the machine can cope with.
I'm currently looking at the screen having resumed a cut, and the program window isn't updating to the current line, but that's a separate issue.
My guess is that the system uses the programmed feedrate on resuming, without taking into account any override.
Can anyone else verify this for me?
-
My guess is that this would be an issue with the ESS plugin.
-
My guess is that this would be an issue with the ESS plugin.
Ok, I'll play 'pass the parcel' and see if they say it's probably Mach3...
-
Surprise surprise, Warp9 say that the ESS doesn't plan any moves except when jogging or homing. They suggest it may be an issue with the Aqua screen saver.
This is what I dislike about these systems where there are two parties that don't appear to talk to each other. Nobody wants to investigate it and see if the problem is in their back yard. It's much easier to say it's someone else's problem.
So, back to square one.... does anyone know where the problem lies?
-
Screensets have absolutely zero effect on Mach3 functionality. This should be easy to confirm by using the default 1024 Screenset.
There is one possibility where the screenset may cause issues, which is if the graphics use too many system resources which slow down Mach3. But the screenset itself just tells Mach3 which buttons your pressing, nothing more.
Gerry
-
That's how I thought it worked, but this is the comment a moderator put on the Warp9 forum...
"I am always very suspicious of screen sets as most of them I have seen try to do very clever things that wind up causing problems."
The machine is tied up for some time so I can't try it out.
The key question is what decides what feedrate is used when the Run is pressed after Pause? Why would the feedrate change? I would have thought the queue would just be frozen and resumed so neither part of the system would need to change it.
-
A screenset can't really do anything that effects Mach3. Some may include macros, but if the macros run on the parallel port, then they should run on a Smoothstepper. Imo, at least.
I can guess who that moderator is, lol.
-
Fwiw, the Aqua screenset is very basic, and does nothing.
My 2010 screenset includes some macros to automatically zero tools during tool changes. There are well over 1000 people using it, many with smoothsteppers, with no issues.
There really are no "clever things" that you can do that would cause problems. Screensets are just different graphics and controls in different locations. They have no control over mach3 functionality.
-
Fwiw, the Aqua screenset is very basic, and does nothing.
My 2010 screenset includes some macros to automatically zero tools during tool changes. There are well over 1000 people using it, many with smoothsteppers, with no issues.
There really are no "clever things" that you can do that would cause problems. Screensets are just different graphics and controls in different locations. They have no control over mach3 functionality.
I think many people have issues but they just accept them or don't notice them. I'm sure my bug is a common one, but because it's not a show stopper, people don't bother reporting it. I suppose it's down to me as usual to prove to either Mach3 or Warp9 that it's their problem. I really shouldn't need to do this for bugs in basic functions that ought to have been resolved years ago. It's supposed to be a mature product.
-
If you're issue doesn't happen with the parallel port, than it's a Smoothstepper issue.
If it's a mach3 issue, then I doubt it'll get fixed. There's hasn't been a new release in years, and the latest versions have their own bugs.
Hopefully, someday Mach4 will eliminate all these issues with motion controllers. Then I'll finally buy one.
-
I have no way of knowing whether the problem exists with the parallel port version. I'll just have to experiment when I get time and see if I can discover where the problem is.
Ah yes, Mach4.... a 'virtual' product that is born of legend. I don't know why they can't just prune it down to something really basic and at least release something. The way they're going, it will never see the light of day. All I need is for it to execute G1 F# S# and M03, that's all I use. How hard can it be to make a system like that?
There's a big gap in the market for someone to produce a nice simple Windows based system without all the junk and clutter of the Mach3 bloatware.
-
There's a big gap in the market for someone to produce a nice simple Windows based system without all the junk and clutter of the Mach3 bloatware.
Planet CNC and Eding CNC
-
There's a big gap in the market for someone to produce a nice simple Windows based system without all the junk and clutter of the Mach3 bloatware.
Planet CNC and Eding CNC
Thanks for that, I'll take a look
-
There's a big gap in the market for someone to produce a nice simple Windows based system without all the junk and clutter of the Mach3 bloatware.
Planet CNC and Eding CNC
grbl arduino
-
Has anyone actually got a machine working with Mach4? The Warp9 forum seem to think that they just need an ESS plugin and they will have it working. We've been waiting for so long that most of us have given up hope.
-
An Arduino and grbl is not in the same league as Mach3 and the others I mentioned. Not even close.
As for Mach4, afaik, there are no motion controller plugins available, except for the parallel port plugin. There are a few using the parallel port plugin, but I can't tell you if they're using Mach4 exclusively yet.
-
An Arduino and grbl is not in the same league as Mach3 and the others I mentioned. Not even close.
As for Mach4, afaik, there are no motion controller plugins available, except for the parallel port plugin. There are a few using the parallel port plugin, but I can't tell you if they're using Mach4 exclusively yet.
Thanks for that.
-
An Arduino and grbl is not in the same league as Mach3 and the others I mentioned. Not even close.
Gerry you are a 100% right, but
striplar was only asking: "All I need is for it to execute G1 F# S# and M03, that's all I use"
that was the trigger for grbl and Arduino.
Thomas
-
An Arduino and grbl is not in the same league as Mach3 and the others I mentioned. Not even close.
Gerry you are a 100% rught, but
striplar was only asking: "All I need is for it to execute G1 F# S# and M03, that's all I use"
that was the trigger for grbl and Arduino.
Thomas
Quite so Thomas, I never use any of the canned cycles, it's all done on the CAD/CAM system that runs on the same computer as Mach3.