When using lightburn with the Jackpot/ESP32/micro USB when the cut for any form of a circle or curve is initiated the x/y goes to the start position, moves a slight bit and then stops.
An error code is also indicated in the lightburn console screen
error:20
Unsuported or invalid G-code command found in block
On or near line 2:
Job halted
What could be causing the error ?
Can you post your gocde and what software you used to make it?
The shape is generated within the lightburn program.
The error is generated when trying to output the shape via the Jackpot’s grbl laser device
The strange item is that Lightburn will output a straight line shape such as a square, triangle, octagon, etc. perfectly.
I am trying to find out how to extract the g-code command that the error is referencing
I powered down all items and powered them up in the correct process
Homed the X and Y using end stops in light burn, that worked as it should
Drew a square (in lightburn) and selected start and the output to the steppers was correct and they moved correctly to generate the square shape.
I then drew a circle (in lightburn) and selected to frame it and that worked correctly as the steppers output the correct movement to frame the circle.
I then selected start and the steppers moved the gantry to the correct starting position, moved a slight bit and stopped.
The following error code was indicated wihtin the lightburn display:
Starting stream
Layer C02
error:20
Unsupported or invalid g-code command found in block.
On or near line 2:
Job halted
Stream completed in 0:00
ok
ok
ok
ok
ok
Below is this is the g code generated
; LightBurn 1.4.01
; GRBL device profile, absolute coords
; Bounds: X10.82 Y13.41 to X44.68 Y45.6
G00 G17 G40 G21 G54
G90
M4
; Cut @ 1000.002 mm/min, 50% power
M8
G0 X18.971Y15.741
; Layer C02
G1 X18.284Y16.159S500F1000
G1 X17.62Y16.608
G1 X16.981Y17.086
G1 X16.366Y17.592
G1 X15.779Y18.125
G1 X15.218Y18.684
G1 X14.686Y19.268
G1 X14.183Y19.876
G1 X13.711Y20.507
G1 X13.271Y21.16
G1 X12.863Y21.834
G1 X12.489Y22.528
G1 X12.15Y23.242
G1 X11.847Y23.972
G1 X11.581Y24.72
G1 X11.353Y25.484
G1 X11.164Y26.263
G1 X11.015Y27.056
G1 X10.907Y27.861
G1 X10.842Y28.679
G1 X10.82Y29.507
G1 X10.842Y30.335
G1 X10.907Y31.153
G1 X11.015Y31.958
G1 X11.164Y32.751
G1 X11.353Y33.53
G1 X11.581Y34.294
G1 X11.847Y35.042
G1 X12.15Y35.773
G1 X12.489Y36.486
G1 X12.863Y37.18
G1 X13.271Y37.854
G1 X13.711Y38.507
G1 X14.183Y39.138
G1 X14.686Y39.746
G1 X15.218Y40.33
G1 X15.779Y40.889
G1 X16.366Y41.422
G1 X16.981Y41.928
G1 X17.62Y42.406
G1 X18.284Y42.855
G1 X18.971Y43.274
G1 X19.68Y43.661
G1 X20.41Y44.017
G1 X21.16Y44.339
G1 X21.929Y44.627
G1 X22.715Y44.88
G1 X23.518Y45.097
G1 X24.338Y45.277
G1 X25.171Y45.418
G1 X26.018Y45.521
G1 X26.878Y45.583
G1 X27.749Y45.604
G1 X28.621Y45.583
G1 X29.48Y45.521
G1 X30.328Y45.418
G1 X31.161Y45.277
G1 X31.98Y45.097
G1 X32.784Y44.88
G1 X33.57Y44.627
G1 X34.339Y44.339
G1 X35.089Y44.017
G1 X35.819Y43.661
G1 X36.528Y43.274
G1 X37.215Y42.855
G1 X37.879Y42.406
G1 X38.518Y41.928
G1 X39.132Y41.422
G1 X39.72Y40.889
G1 X40.281Y40.33
G1 X40.813Y39.746
G1 X41.316Y39.138
G1 X41.788Y38.507
G1 X42.228Y37.854
G1 X42.636Y37.18
G1 X43.009Y36.486
G1 X43.348Y35.773
G1 X43.652Y35.042
G1 X43.918Y34.294
G1 X44.146Y33.53
G1 X44.335Y32.751
G1 X44.484Y31.958
G1 X44.591Y31.153
G1 X44.657Y30.335
G1 X44.679Y29.507
G1 X44.657Y28.679
G1 X44.591Y27.861
G1 X44.484Y27.056
G1 X44.335Y26.263
G1 X44.146Y25.484
G1 X43.918Y24.72
G1 X43.652Y23.972
G1 X43.348Y23.242
G1 X43.009Y22.528
G1 X42.636Y21.834
G1 X42.228Y21.16
G1 X41.788Y20.507
G1 X41.316Y19.876
G1 X40.813Y19.268
G1 X40.281Y18.684
G1 X39.72Y18.125
G1 X39.132Y17.592
G1 X38.518Y17.086
G1 X37.879Y16.608
G1 X37.215Y16.159
G1 X36.528Y15.741
G1 X35.819Y15.353
G1 X35.089Y14.998
G1 X34.339Y14.675
G1 X33.57Y14.387
G1 X32.784Y14.134
G1 X31.98Y13.917
G1 X31.161Y13.737
G1 X30.328Y13.596
G1 X29.48Y13.493
G1 X28.621Y13.431
G1 X27.749Y13.41
G1 X26.878Y13.431
G1 X26.018Y13.493
G1 X25.171Y13.596
G1 X24.338Y13.737
G1 X23.518Y13.917
G1 X22.715Y14.134
G1 X21.929Y14.387
G1 X21.16Y14.675
G1 X20.41Y14.998
G1 X19.68Y15.353
G1 X18.971Y15.741
M9
G1 S0
M5
G90
; return to user-defined finish pos
G0 X0 Y0
M2
`||All of these are straight G1 commands that should not pose a problem, so it is probably here.
If I had to guess, it would be the S500. It appears that lightburn is sending power on a scale from 0 to 1000, which is ok… unless the controller is expecting the scale to be from 0 to 255.
You can test by selecing a lower power. If it comes on near full power when 25% is selected, then that’s it. Or you can tell Lightburn that laser power scales from 0 to 255. This is likely the better option.
K will do
I saw that line that did not look similar to the other G1 lines
I am going to look at the Gcode that is generated when an object is created that has all straight lines and see if the s500 and the f1000 is also in that g code
I think it is a bot, odd there are no arc commands in there. Those are all straight lines, small straight lines.
What is a bot ?
ok this is the g code for a hexagon that is generated by lightburn and when output to the Jackpot runs the g code and the steppers move correctly and completes the hexagon
; LightBurn 1.4.01
; GRBL device profile, absolute coords
; Bounds: X11.38 Y62.63 to X55.22 Y98.52
G00 G17 G40 G21 G54
G90
M4
; Cut @ 1000.002 mm/min, 50% power
M8
G0 X22.338Y62.627
; Layer C02
G1 X11.375Y80.573S500F1000
G1 X22.338Y98.519
G1 X44.263
G1 X55.225Y80.573
G1 X44.263Y62.627
G1 X22.338
M9
G1 S0
M5
G90
; return to user-defined finish pos
G0 X0 Y0
M2
That gcode is all straight lines.
G1 code means to move in a straight line to the X and/or Y and/or Z coordinate specified.
G2 (or G02) is to move in a clockwise arc and G3 (G03) will move in a counter-clockwise arc. The code that you posted up there doesn’t use any of these.
In the G1 command: (nnn denotes any number)
G1 X100 would retain the same Y, Z, F and S parameters that were used before.Sorry…
I think it is a BIT odd there are no arc commands in there. Those are all straight lines, small straight lines.
I looked into the short lines as curves in lightburn and this is how lightburn works with curves, the software uses short lines to make the curves. I tried lowering the tolerance for the curve detail but that did nothing to help the issue.
I also tried lowering the laser power setting and that did not help either.
Is it possible that the Jackpot does not like the use of small lines for curves because of the controller having to make many very small movements quickly ?
Copy of the text from the lightburn website regarding curves:
¶This controls the precision LightBurn uses in displaying curves on the screen. All curves are displayed as a series of short lines, but the higher this value is, the shorter those lines will be. You can see the difference below.
If you’re working with files containing thousands of curves and your computer is lagging you may want to try reducing this value. If you need your curves to be very precise, you may want to increase it.
Ok I have tried about everything I can think of to try to get it to draw anything with a curved portion.
I’ve tried;
A totally different computer
Tried lighburn over WiFi
Tried lightburn on USB
Changed the baud rate for the com port
Tried a different USB cable
The Jackpot will not make a curved motion for an item that is to be cut.
It will frame it as a circle if you select the rubberband frame option but when the g code is run it will start, stop and generate the error code 20
I have tried installing all new files using the web installer via the usb connection in hopes of restoring the controller back to the way it came to me from V1.
There is another person on this forum that has it working with lightburn but I can not get it to function as I need it to.
I am out of ideas
Error code 20 is an invalid command, so something is going wrong.
The gcode that you showed earlier looks OK, though it was a bit weird that it doesn’t use arcs.
Is it OK with straight lines?
You said it will rubberband frame… is that at a lower power? Have you tried running it at low power?
Can you post your config.yaml?
(Note, whennposting code lime that using 3 back ticks (`) before and after a code block makes.it easier to read on the forum, but shouldn’t really be needed here. It just makes sure that funny things with asterisks don’t put things in italics or bold font)
One item that I did not mention is that the laser is not hooked up as I am just wanting to proof out the X, Y and Z movements prior to powering up the laser.
With the laser disconnected it shouldn’t matter, I say this because :
I think it could be something due to the length of the short lines making up the curved item and how fast the g code is read and then output is sent to the steppers.
I do know there is another guy on the V1 forum that has his MPCNC working with the jackpot and he is not having any troubles.
I did reload all the firmware (3.7.8) and associated files in hopes that it would be put back to what it was when it was shipped to me.
I did have firmware 3.7.9 loaded but removed it by uploading the 3.7.8.
Is it possible that there could be some code residing in the ESP32 that could be causing the issue
I would like to try and get it back to the way it was when I received it to see if that would make a difference.
Did you uncomment the laser section in the config?
I might be able to try this later today. I did plenty of vector testing in lightburn with the jackpot and did not have any issues. I tested my logo a lot and it is full of curves, and I was pushing the speeds up pretty high.
Please post your yaml so we can see your laser section.
You have some M8 and M9 in your code, What are you trying to do with those? That is Coolant, do you have a coolant pin defined? Supported Gcodes | Wiki.js
Is that used by lightburn for air assist? I have a 24v solenoid hooked up to mine to control the air to the air assist (kept forgetting to turn it on at the start of the job and didn’t want to mess up the lens) and i didn’t have to change anything in the config for it to work. I saw the light coming on before I ever had it hooked up so I just used that spot lol. I have been exclusively using the first jackpot I got for laser on my Primo and other than some connection over usb errors in the very beginning that were just me not knowing what I was doing it has been completely flawless for me.
Ya, I did uncomment the laser data
I will be posting over the yaml file in a bit, been a busy Monday so far
Ok
Success finally !
I did another fresh install of all files, updated the laser information as per V1’s information and now it is drawing shapes as it should
now to move on to getting the laser to fire up
Sorry for the aggravation
I went thru the previous yaml file used and compared it to the one that I just downloaded and updated
I still don’t see what could have been causing it
I must have had something incorrect in the previous yaml file as that was the only file that I had to modify
thank you again and sorry for the aggravation