Just got LW4 up and running, and I got to say,

Just got LW4 up and running, and I got to say, its a nice step above LW3. works great so far. Good work!!

However, i do have a config question.

What are the config file settings to allow air assist control? I will be using P2.5 to activate the SSR that controls my valve. I had it working on an older version of Smoothie, and LW3 , but maybe the config has changed? Or I fat fingered something in the config (cant find anything).

Thanks in advance!!

Sorry. Just realized this is basically a machine set up question.

There is a special section you can that gcode value in settings/machinr

@Ariel_Yahni_UniKpty Yes, but doing it that way, it does not come on during raster engraving , only when the laser fires when doing a cut operation. What am I missing?

@Jorge_Robles ​ is that only intended for cutting?
@Eric_Flynn ​ maybe add it to the start and end gcode?

I think that will work. Just sort of an inelegant solution considering there provision for it otherwise. But yea, if it works it works.

Let’s see @Jorge_Robles ​ answer on the the purpose of the air assist section

yes, i wasn’t sure if it was specific or not

Apparently, as stated, I got that part. I was asking about the switch in the LW4 settings. Nowhere is it apparent that it is for Emblaser machines only.

Would m8 m9 codes work… That’s “coolant flood on” in CNC code

@Eric_Flynn ​, Well, the Air Assist settings are somewhat generic. It tells what gcode will be used to turn ON/OFF, each pass instead doing on job start/end.

Although could be renamed to GCode Pass Start, GCode Pass End.

+Peter van der Walt​ Z limit was dropped from implementation a while ago :wink:

@Jorge_Robles ​ does it work with raster operations or only cut?

Have to check, I think I implemented both :slight_smile:

FYI, Similar discussion here: https://plus.google.com/114422684423642232545/posts/WY3So9LcyYc

Thanks guys. Yes, it works as expected just putting the defined M codes into start/end , which is fine for most stuff. It would be nice if the tick worked as expected, that way you could turn it off if needed with a simple switch. Now, if you add the AA codes, and use the switch, it only turns on with a cut op , it will not turn on with a raster op. However, it also turns off, with the laser in that case, it should just stay on until the job is finished. Start/End obviously fixes that, but without the ability to turn it off if needed without messing around a bit.

@Eric_Flynn thanks!. I’ve found it’s not properly honoring pass ON/OFF on raster. Will fix soon.

About instant on/off . Could it be implemented as an override on gcode run @cprezzi ?

what about using the macro section to make a button to enable/disable as needed?

@Domm434 Macros would not work as they do just add the code to the end of the queue, so they would be executed after the job.

@Jorge_Robles I don’t see the need to manually activate/deactivate air assist/flood/mist during a job.
Instead of that we could add pre- and post-gcodes to each cam operation, so everybody can add whatever they like for each operation.

@cprezzi there’s an slightly difference between air assist and pre/post gcode operation, unless we think a rework.

Air assist can be enabled/disabled at will on each operation, but enabling a pre/post operation gcode on settings could not be the same as will affect all the operations, unless we introduce a new an in-operation toggle (like actual air assist) called “Use Pre/Post Operation” and “Use Pre/Post Pass” for example.

Corner scenario could be to park a tool upon start/end operation and does nothing compared air assist.