TazerReloaded

I wrote this config: ``` [output_pin intensity] pin: P2.0 pwm: true cycle_time: 0.001 scale: 255 value: 0 shutdown_value: 0 [gcode_macro M3] default_parameter_S: 255 gcode: SET_PIN PIN=intensity VALUE={S} [gcode_macro M5] gcode:...

Also noticed an issue while trying to print today: Whenever I enable a heater, Klipper shuts down with a "Timer too close" error after a few seconds. Same config on...

The relay for laser power is attached to the Pi and controlled via Moonraker power commands, so I don't think that affects Klipper in any way. I also control the...

I tested the output frequency today, and on my hardware (SKR 1.4), I get a nice clean 10.8kHz square wave with the following settings: ``` hardware_pwm: true cycle_time: 0.0001 ```...

Unfortunately, the time of re-flashing is coming back sooner or later. The master branch has already altered the communication protocol, and introduced a few fixes for my setup. I flashed...

Klipper already supports modular config, you can just do: ``` [include laser.cfg] #[include extruder.cfg] ``` Then define the heater and extruder stuff in extruder.cfg, and the laser pins in laser.cfg....

That's a creative solution, but stepper pulses are frequency modulated and most lasers expect pulse width modulation for power control. How do you convert the signal? And with a raster...

Cool, I'll wait for the implementation of PWM scheduling then! I already wrote my own little "slicer" for images, so syntax adjustments are not an issue (still working on minimizing...

I tested https://github.com/KevinOConnor/klipper/pull/4128 today, works quite well with my setup. Hardware: - Raspberry Pi 3B, default clock - BTT SKR 1.4 100MHz - Some generic 1.3W diode laser with PWM...

The controller could use PID for driving the stepper back in the event of missed steps, but standard operation should be normal stepping according to the MCUs commands (like open...