Time to revisit coolant mapping of M-codes in Linuxcnc

I haven't looked but I am fairly sure the the software supports mcode with decimal places ? M7.0 or m7.1  etc and so on. 

the current coolant/cutting fluid controls are way to limited and require to much special handling. It would make sense to update the current scheme with mcode that could be numbers 

M7.1 air blast
M7.2 mist
M7.3 flood
M7.4 through tool 

etc and so forth. I can modify the existing post processor but where exactly would this change have to be made in the core of the linuxcnc software base ? Also the existing mcodes for coolant can be left standing. I am just trying to avoid creating custom mcodes for controlling the various cooling systems I am adding to my machines, but many NEWER cnc machines also have many varying types of coolant schemes. 

Minor suggestion - leave the mist as M7, and flood as M8 and save the 'derivative' M-codes as M7.n or M8.n

M8 - main flood
M8.1 - supplemental
M8.2 - TSC
M8.3 - washdown

M7 - main mist
M7.1 - supplemental

Etc.

haven't looked but I am fairly sure the the software supports mcode with decimal places ? M7.0 or m7.1 etc and so on.

As far as I'm aware Mcode numbers must be integers (Gcodes can have decimals)
You could create a single custom mcode with a P word though.

Ok, so configure coolant m codes as follows

M7 p1 mist
M7 p2 derivative 

M8 p1 flood
M8 p2 through tool
M8 P3  high pressure through tool

M9  p01 mist off
M9 p100 all off 



As kind of a loose structure?

Thanks for the reply. If anyone knows where in the code base to look for this stuff it'd be nice to save me the time of having to dig through tons of folders and files

Thanks

I was actually picturing a remapped (ie currently unused Mcode). This would be a rather simple gcode remap where you could then use 'motion.digital-out' pins for the appropriate coolant flow.

Actually adding this to the source code will likely involve
a) a number of files in '/src/emc/rs274ngc'
b) pose the additional challenge of there not being a suitable NML command for all the different coolant variants you have in mind.

Aciera wrote:

I was actually picturing a remapped (ie currently unused Mcode). This would be a rather simple gcode remap where you could then use 'motion.digital-out' pins for the appropriate coolant flow.

Actually adding this to the source code will likely involve
a) a number of files in '/src/emc/rs274ngc'
b) pose the additional challenge of there not being a suitable NML command for all the different coolant variants you have in mind.
 

This is what I did for my non-standard cooling stuff.  Just cooked up some Mnn.ngc files to take care of stuff like spindle taper air blast, washdown, and multi-mist nozzles on my gang lathe.

spumco wrote:

Aciera wrote:

I was actually picturing a remapped (ie currently unused Mcode). This would be a rather simple gcode remap where you could then use 'motion.digital-out' pins for the appropriate coolant flow.

Actually adding this to the source code will likely involve
a) a number of files in '/src/emc/rs274ngc'
b) pose the additional challenge of there not being a suitable NML command for all the different coolant variants you have in mind.
 
This is what I did for my non-standard cooling stuff.  Just cooked up some Mnn.ngc files to take care of stuff like spindle taper air blast, washdown, and multi-mist nozzles on my gang lathe.

are you at liberty to share those mappings ? 

Aciera wrote:

I was actually picturing a remapped (ie currently unused Mcode). This would be a rather simple gcode remap where you could then use 'motion.digital-out' pins for the appropriate coolant flow.

Actually adding this to the source code will likely involve
a) a number of files in '/src/emc/rs274ngc'
b) pose the additional challenge of there not being a suitable NML command for all the different coolant variants you have in mind.

The issue at hand, the lack of NML commands is a problem that requires a lot of extra effort for every retrofit that could be solve once and be done with.