m1 behavior

Is it possible to have M1 stop the spindle of a lathe? Currently my axis motion stops but the spindle remains on. I would like to be able to measure features before running the next tool....

This may be similar to the question about modifying an m3 code that was just posted, but I figured this would be a very commonly desired option.

Thanks all.

Have you looked at Manual tool changer and M6?

linuxcnc.org/docs/html/gui_axis.html#sec:Manual-Tool-Change

Rick G

Yes, using the block skip function and subroutine would get me where I want....

That said, I do think that it should be an option. The spindle stopping and coolant turning off is pretty standard on most controls when a M1 or M0 command is issued. Would anyone else be interested in such a thing? If so maybe a feature request could be started.

Justin

there've been several requests to modify the behaviour of the m1,m2,m30 etc group codes

those arent currently in the set of remappable codes, but is doable

any strong reason not to define a new M code and be done?

-Michael

I guess I am used to fanuc controls, and that is essentailly the industry standard. I believe that with fanuc there is most likely a group of parameters that control the behavior of m0, m1 so that integrators can make their machines run however they need to. I believe m0, m1 and maybe some others would greatly benefit from a similar setup, similar to the homeing sequences that Linuxcnc has now. You define the behavior in the .ini file and it acts accordingly. What would it take to add something like this?

Making a custom mcode to do this is just fine, but I do not know how you could turn it on and off like you can with both m1 and m0 other than use block delete, which would prevent you from using block delete for anything else.

BigJohnT wrote:

Simply switch to master and you can define a M code to suit your particular needs. None of my commercial CNC controllers do anything more than stop motion with M1 or program pause. Of course you would also have to handle what to turn back on somehow...

John

here's an example how it can be done with remapping (requires master), this is John's example
repackaged as new code:

git.mah.priv.at/gitweb/emc2-dev.git/shor...s/extend-m1-by-remap

Current restrictions:
- M1 cant be remapped directly like M6/M61/T/S/F, so a new code is needed for now
- the M10 is modal group 5, not group 4 like M1, since group 4 cant currently be remapped

Lifting the 'current restrictions' requires some coding on my side. Think what you wish for..

- Michael

I've added the capability to redefine or extend the m0,m1,m60 codes

see the configs/sim/remap/extend-builtins demo

git.mah.priv.at/gitweb/emc2-dev.git/shor...ads/remap-mgroup4-rc

This needs exercise, so I'd be grateful for feedback

- Michael

Thanks Michael!

I just tested the extended m1 and m0 posted, it works great and is exactly what I needed. Would it be possible to record if it was in m3 or m4 before the m1/ m0 and then start the spindle the same direction after the program is started again. I imagine this would be much like how it checks the coolant....


; record whether mist/flood were on
#<mist> = #<_mist>
#<flood> = #<_flood>

/M5 M9 ; stop spindle, mist+flood off

/m1 (refer to builtin m1)

; restore mist, flood setting
/o100 if [#<mist>]
/ m7
/o100 endif

/o200 if [#<flood>]
/ m8
/o200 endif


Only <mist> and <flood> would be m3 and m4?