Closed tomgale closed 3 months ago
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 name: TinyBee corexy meta: (17.01.2024) by Skorpi
kinematics: corexy:
stepping: engine: I2S_STREAM idle_ms: 250 pulse_us: 4 dir_delay_us: 1 disable_delay_us: 0
axes: x:
steps_per_mm: 80.000
max_rate_mm_per_min: 12000.000
acceleration_mm_per_sec2: 6000.000
max_travel_mm: 350.000
soft_limits: true
homing:
cycle: 2
allow_single_axis: true
positive_direction: false
mpos_mm: -3.000
feed_mm_per_min: 200.000
seek_mm_per_min: 4000.000
settle_ms: 250
seek_scaler: 1000.100
feed_scaler: 3.100
motor0:
limit_pos_pin: gpio.33:low
hard_limits: true
pulloff_mm: 3.000
stepstick:
step_pin: I2SO.1
direction_pin: I2SO.2
disable_pin: I2SO.0
y:
steps_per_mm: 80.000
max_rate_mm_per_min: 12000.000
acceleration_mm_per_sec2: 6000.000
max_travel_mm: 350.000
soft_limits: true
homing:
cycle: 3
allow_single_axis: true
positive_direction: false
mpos_mm: 0.000
feed_mm_per_min: 200.000
seek_mm_per_min: 4000.000
settle_ms: 500
seek_scaler: 1000.100
feed_scaler: 3.100
motor0:
limit_pos_pin: gpio.32:low
hard_limits: true
pulloff_mm: 3.000
stepstick:
step_pin: I2SO.4
direction_pin: I2SO.5
disable_pin: I2SO.3
z:
steps_per_mm: 930.000
max_rate_mm_per_min: 1200.000
acceleration_mm_per_sec2: 300.000
max_travel_mm: 260.000
soft_limits: false
homing:
cycle: 0
positive_direction: true
motor0:
hard_limits: false
stepstick:
step_pin: I2SO.7
direction_pin: I2SO.8
disable_pin: I2SO.6
i2so: bck_pin: gpio.25 data_pin: gpio.27 ws_pin: gpio.26
spi: miso_pin: gpio.19 mosi_pin: gpio.23 sck_pin: gpio.18
sdcard: cs_pin: gpio.5 frequency_hz: 1000000
coolant:
flood_pin: gpio.17
mist_pin: I2SO.20
delay_ms: 0
Laser: pwm_hz: 5000 output_pin: gpio.13
disable_with_s0: false s0_with_disable: true speed_map: 0=0.000% 1000=100.000% off_on_alarm: true
start: must_home: false `
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