Hi guys - I'm new to all this - my 1st post, 1st mill, 1st project.....

I'm evaluating a Mach3 trial with a view to purchase.  Installation and configuration went well, and all operates  as it apparently should.
 -
When I start a gcode run, the spindle (pwm control) starts as expected when the M3 is encountered, and stops on M5 as expected.   During a gcode run if I click Stop, gcode execution pauses and the spindle stops, when I click  CycleStart gcode execution resumes as expected.
 
But I don't understand this:  when I click CycleStart to resume gcode  execution, why does the spindle not restart too?  There has been no M5 to stop it, so technically, to me, the gcode is broken by the CycleStart function not having performed a full 'resume'.
 
Perhaps this by design, but I have now broken two tooltips.  And what else is not restored on a restart?  Is there is a preference/configuration setting to toggle this that I've missed?
 
Otherwise, great program!  As a software engineer myself, I can see the years of work that have gone into this.  Alternatively for my spindle issue, is there an "ExecutingGcode" output from Mach3 that simply tells hardware that gcode is executing?
 
Cheers and thanks
PS: The capcha box on your ContactUs screen fails every time.

You should not use stop if you want continue cutting just pressing cycle start. You should use pause. Although pause do not work in midle of circle and I think it can not be used very well in subroutines. You could loose position when use stop as axis do not declerate at all. Some servo systems can handfle that, ut steppers do not. To stop whitout loosing position is use pause and after machine do not move press stop.

Correct way to continue after stop is use "run from here" but I think it is not functinal in demo, needs to have license

Many thanks for your help Mstcnc.  Some good info there I didn't know. 

But pause?  I don't seem to have a 'Pause' button, or anything like it.  The reasons I need to pause are to change tooltips, tweak Z zero, and check part dimensions.  Is there an accepted way to do this without restarting the spindle manually?  A document reference would also be good.

I gather there are alternative Mach3 screens - has anyone made one with more of a video player control metaphor, do you know?  Or is such a thing even possible?

And again, does Mech3 have an output signal that just says gcode is running, anyone?

<Correct way to continue after stop is use "run from here" but I think it is not functinal in demo, needs to have license>

Run from here is correct way to do restart after tool tip change and more likely only way to start correct coordinates and offsets if you make modification those.
It is explaned in mach manuals, which you will find in http://www.machsupport.com/help-learning/product-manuals/

Which version you are using and are you using standard screen set?

I don´t know for sure or more specific how to make output active when code is running, but that do not mean that it is not possible.... maybe in brains it could be possible?

-M

Thanks again Mstcnc

Sorry about the delay in responding - I've been out of town on a family matter for a couple of days.  
I'm just using the latest trial version - 3.043.066 - with a view to purchase.
I'm guessing you are calling the FeedHold button "pause" - OK.  As far as I can tell, RunFromHere recalcs the last valid position from the start of the Gcode up to the stopped line number, then waits for CycleStart.  RunFromHere allows a CycleStart from any gcode line as expected.
 
That's all much clearer now, thanks to you, but I'm still looking for a way to stop Gcode from running unless the spindle is running first.  Mach3 handles it if X or Y is moved by preceeding further gcode execution with the "PreparatoryMove" dialog, there's no such protection if only Z moves as often is the case for a toolchange.

Which is how I broke another tooltip today.  Any further ideas? Anyone else?  Pretty *please*....

Run from her has an option to start the spindle I think.
Also, there might be an option to not stop the spindle on Stop? Don't have Mach3 on this PC, so I can't check.

If all you are wanting to do is check the spindle is running before code can be executed then that would be relatively simple but would depend on your spindle setup as to how its done.

BTW RFH will not work in demo mode.

Hood

The reasons I need to pause are to change tooltips, tweak Z zero, and check part dimensions.  Is there an accepted way to do this without restarting the spindle manually?

I might be missing something here but if by "change tooltips" you mean "change tool" then surely you don't need to feedhold and run from here - you just have the correct toolchange sequence in gcode (M6 T.../M3 etc.) and tick "stop spindle - wait for cycle start in toolchange on the config screen.

Ian

Greetings Gerry, Hood, and Ian - thanks for your comments.

As I said above I'm very new at this, and haven't attempted a toolchange under gcode control yet.   I've glimpsed some postprocessor gcode for toolchanges, but I know nothing about the accepted process.

I've simply been trying different tools (3mm shaft) with ad-hoc toolchanges to assess suitable feedrates, cutdepths, and spindle speeds in MDF.  I'm evaluating MeshCam at the same time.

If RFH doesn't work in the demo, as Mstcnc also mentioned, it explains a lot.  But you're correct Hood, a safeguard that either starts the spindle before the gcode, or a check that the spindle is running before the gcode is, is exactly what I'd like.

My spindle is simply PWM controlled by Mach3 as per the setup manual, with a simple manual isolator and estop override.  Hood, can you suggest where I look to find how to implement such a safeguard?  I'm hoping there's a way to hold the gcode until the spindle has ramped up.

I'm mighty grateful for all your help.  

There are severla ways to accomplish the code not running unless the spindle is on, however if Mach is controlling the spindle on/off then the only real way would be to use a macropump, for that you will need an index pulse to Mach so it knows the RPM.


Regarding ramp up/down, there are settings on General config for that, it will delay the code continueing for the time you have set there.
Hood