LB 1.4.05 currently. Nothing compelling is keeping me from 1.5, but I’m also in no rush to introduce potential bugs since 1.4 is working fine for me.
Just setting up a new AlgoLaser DIY 5W with their new air assist and finding a quirk I’d like advice about, to see if I can tweak its behavior some.
I feel like this is a mix of Algo firmware quirks and LB quirks. Not sure if/how I can change either.
M16 powers on pump at 100% speed.
M16Sxxxx powers on and/or adjusts speed, where S100=10%, S1000=100%
M17 powers off pump
M7 generates “unsupported g-code” error
M8 does nothing.
M9 powers pump @ 30%
The pump powers on at 30% at connection and remains on unless issued an m17.
I figured I could work around all that with start/end gcode and macros, issuing m16s500 at start and m17 at end. And a macro for turning it off if I connect and don’t immediately run a job. So, that’s what I did. I only intend this machine for engraving, so a low/moderate flow of air during any/every job is adequate. A single start GCode can manage that.
I also created macros for M16S250, M16S500, M16S1000, & M17. These work as expected.
This is where it gets a bit funky…
With LB air toggle OFF (+start/end gcodes):
Upon start, the pump powers on at expected 50% then almost immediately switches to 30% (like an M9 was issued), runs job, shuts off air, moves to finish position, and turns on air again to 30% (M9 again?)
With LB air toggle ON (+start/end gcodes):
Upon start, the pump powers on at expected 50%, runs job, shuts off air, moves to finish position, and turns on air again to 30% (M9 again?) It then remains on until I issue an m17 manually.
So…enabling air toggle partially works. Disabling air toggle fails miserably.
Any thoughts on how I can make this pump behave?
TIA!