Old topic - same problem - error 24

I’ve had my Ortur Master 2 Pro for a year now and one of my most produced projects, I’ve never had an issue with until today when I’m on a time crunch. I run on an Imac 27. Same program, just text change as always, same computer, same cables. It frames perfectly, profiles perfectly, just doesn’t burn after about 2-3 seconds where it produces the ERROR 24 and stops.
It’s a 5 hour burn and I’ve now spent 3 1/2 hrs of brain time trying to figure out/fix the issue.
ANYTHING new with this? I just upgraded Firmware today to 1.3.01
I also tryed saving file as .lbrn after trying .lbrn2


Can you save gcode with .txt extension and then upload here for review?

The text file is to big it says

To where did you send it? Can you simplify the file to make it smaller or provide a link to a share drive?

Here is the beginning of the gcode - it errors out pretty fast so it should be in this first part I guess.

; LightBurn 1.3.01
; GRBL device profile, absolute coords
; Bounds: X67.99 Y12.42 to X313.86 Y387.47
G00 G17 G40 G20 G54
; Scan @ 66.8001 in/min, 97.5% power
G0 X10.4002Y0.4903
; Layer C00
G1 X0.0172F66.8S243.8
G1 X0.0096Y0.0039S0
G1 X-0.0359S243.8
G1 X-0.0055Y0.0039S0

I don’t see an issue in the g-code at least for what you posted. Can you try running that portion and check to see if the error is triggered with that snippet? Be prepared to shutdown the laser as it will likely continue to fire when done.

One thing I do see that’s odd but shouldn’t be causing your issue is that your S values for power look odd. Have you had problems with power modulation?

I suspect you have S Value Max set to 255 in Device Settings. This is universally 1000 as far as I know for Ortur machines.

Well!!! After rebooting, changing cords around and hours of no production - I did go back and change the S Value MAX back to 1000 at your suggestion, hit start and the sucker is working. Not sure what the solution was - but thanks for your help .))

Glad you’re back up and running. If the g-code was fine I was leaning toward it being a potential communication issue in which case the cord swap may have been the actual fix.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.