-
-
Notifications
You must be signed in to change notification settings - Fork 369
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem: Laser firing on G0 moves #1285
Comments
I think enable stays on until M5. The output should be off during G0 |
ah ok, might be my misunderstanding then, so the enable pin stays on, but the PWM output should drop to zero? I'll double check tomorrow, but I think the tube is staying powered, (or at least I can see the plasma in it). Is this the use case for DisableWithS0? I can try that too. Thanks! |
Have you tried disable_with_s0: true ? |
here are my settings on the same board and everything works fine for me `board: MKS TinyBee V1 #$config/filename=TinyBee.yaml $ESP115 =ON kinematics: stepping: axes:
y:
z:
i2so: spi: sdcard: coolant: Laser: start: |
disable_with_s0: true is the fix! thanks all. On the off chance that it helps someone else, the tube staying energised was because the little control panel which comes with the laser PSU overrides the PWM signal, which is a bit annoying. |
Wiki Search Terms
Laser Mode, Laser, Spindle, G0
Controller Board
MKS Tinybee V1.0
Machine Description
CoreXY CO2 laser with DM542 motor drivers, Cloudray M100 Laser PSU.
Input Circuits
No response
Configuration file
Startup Messages
User Interface Software
LightBurn
What happened?
Hi, I tried a test cut of two rectangles in Lightburn, the machine moved as expected, through both rectangles. The issue is the laser Enable pin switched on with the M4 command, and stayed on during the G0 moves, both to the first rectangle and between the two rectangles. Fluid NC is recognising the Laser spindle, and test firing the laser through both WebUI and Lightburn works as expected. I think Fluid NC is in laser mode, because as I understand it a 'GcodeUnsupportedCommand' error should be thrown if the M4 command is sent to an unsupported spindle. Lightburn's terminal shows no errors while or after the GCode is running. Could the issue be with the GCode being sent from Lightburn? Any help would be massively appreciated, thanks!
GCode File
; LightBurn 1.6.03
; GRBL device profile, absolute coords
; Bounds: X14 Y21 to X127 Y103
G00 G17 G40 G21 G54
G90
M4
; Cut @ 100 mm/sec, 20% power
M8
G0 X61Y22
; Layer C00
G1 X14S200F6000
G1 Y57
G1 X61
G1 Y22
G0 X127Y21
G1 X82
G1 Y103
G1 X127
G1 Y21
M9
G1 S0
M5
G90
; return to user-defined finish pos
G0 X0Y0
M2
Other Information
No response
The text was updated successfully, but these errors were encountered: