Even better solution: I hooked up the power wires for my laser to the bed heater output and made that a GPIO that I then turn on and off via gCode.

@krohm-koala said in [3.3.0-rc2] M3-M5 gcode action:

hen you want to adjust your focus, it's a bit difficult duri

Does your laser have a Z-axis to adjust height? I'm planning for mine too - so eventually I'll do a test g-code that fine adjusts the laser height over multiple passes, and to than workout the offset from the top of the material being engraved/cut.

@Royassas said in DWC - dashboard move buttons: using G1-movements for XYZ-moves?:

Might this be because of the sticky S setting in laser mode definition?

Yes. If you set the sticky feature then the S parameter is remembered across G0 moves. This is IMO a dangerous thing to do, but unfortunately it's what the programs that generate GCodes for laser cutters and engravers expect. I'd much rather those programs generated the S parameter on every G1 move that needs the laser on, which would be the safe thing to do.

You can use command G1 S0 at the end of your GCode file (or in your stop.g file, if your program ends with a M0 command) to reset the laser power to zero.

It's occurred to me that the firmware could remember the laser power setting separately for each input channel, so I may implement this in a future firmware version. I'll also change it to reset the remembered laser power to zero automatically at the end of a job, if it doesn't already.

I will add move.currentMove.laserPower (with range 0..1) to the object model in RRF 3.01-RC4, then DWC will have it available for display.

@dc42 said in Laser Filament Monitor 'SW' PCB Pads - Unsolved:

@snowcrash said in Laser Filament Monitor 'SW' PCB Pads - Unsolved:

Ok, so... was my original understanding correct? that is, the voltage reading between the 2 pads (High/Low) serves as an indicator for filament present/not-present?

Our intention is that if you want to add a filament presence switch, you add a switch that shorts those 2 pads together when filament is present.

To make it easier for us (or anyone else) to prototype new functionality.

In what why exactly? could you please give an example?

No, because we haven't used them yet.

Ok, thanks

The latest firmware (2.02RC2) doesn't yet adjust laser power during acceleration and deceleration, but if a move gets executed at less than the requested feed rate, it adjusts laser power to compensate for that.