Did you follow the instructions in this post for setting up your device or are you still using the old profile?
1 Like
Funny thing. I followed these instructions originally.. Operate xTool S1 with LightBurn - xTool Support Center (already posted).
But I figured maybe there is some overlooked setting in the .lbdev file, so I followed the directions in your link. Now the all the macros in the “console” tab are gone, including “DETECT”. No big deal, I just reload the device profile that was created with the .lbdev file and copy the macro info and create it for the manually created profile.
Unfortunately this has not produced desirable results. Now when I load ANY of the profiles, “DETECT” only moves in X and Y. The machine never raises and lowers the head to use the depth finding pin. M368 was the M-code for the “DETECT” macro from the .lbdev file.
If I can’t regain the auto depth functionality I will have to set the depth manually, which will be notably slower since continuous jog does not function in LB.
So far I have tried importing the .lbdev file (per the previous xtool link) and that has not worked. I’ve also tried building a new profile by the same method with identical results.
To be fair I should manually set the depth and at least see if my squares are squares instead of triangles. 
Ok. It looks like the depth pin was bumped. Hoping that’s all.
At this point the auto depth finding is working again, and the squares are squares!
Thanks for posting those directions.
Not sure what the real difference between the manual setup profile and loading the .lbdev really is, but it seems to work properly now.
Points of interest:
.lbdev - includes rotary macros and a Z height “DETECT” macro
.lbdev - does not include the z focus option in the “Move” tab
.lbdev - homing covers X Y Z axis
Manually built profile (per your post) has none of the customized macros
Manually built profile has the z focus option in the “Move” tab
Manually built homing does not include Z axis - Must add macro
Thanks again for the help. I have added the rotary macros to the manually built profile and I believe it will be my goto from now on.
1 Like
Well I’m not sure if I need another thread, but it is still part of the same issue I believe.
Today I ran some squares created it lightburn. The good news is that they where square, but the bad news is that they only cut the first pass.
Here is an example of the problem end of the square cut code, and the beginning of the 2nd pass:
G1 X-0.001Y-0.012
; LAYER C01 PASS 2 OF 8
M4
G1 X-0.004Y-0.013
ETC…
And the adjustment to the code that “fixes” it:
G1 X-0.001Y-0.012
M5
; LAYER C01 PASS 2 OF 8
M4
G1 X-0.004Y-0.013
etc…
Speaking of M5, is there a way to modify the post processor? If I use a “custom g code” device will I be able to modify the post processor?
Is there a list of G and M codes somewhere?
There are two examples earlier in this thread of how to setup the machine profile. One reference to xtool’s website, and one reference that walks through a manual setup. The .lbdev file from xtool’s site gives me triangles instead of squares ON THE 1ST pass (proper squares on subsequent passes), and the manually created one fixes the squares except subsequent passes have the laser shut off.
When comparing the xtool and manual .lbdev files side-by-side, I cannot find anything that looks like the culprit for this behavior.
Which tree should I be barking up?
Please read Joe’s post again. I believe it’s all there. With our instructions, it uses our custom Xtool device type, which bypasses their GRBL compatibility layer. (You can see this by the Xtool icon)
You can import the .LBDEV file at the end of his post:
That’s expected. Using the new device type, you don’t need the macro anymore. Use the “Focus-Z” button in the “Move” window instead.
I mistakenly thought the .lbdev file would be the same as the walk through setup. Happy to say I was wrong.
It looks like things are working fine after importing the one you reference.
Thank you Lightburn for making great software and supporting it!
1 Like
Remove the .TXT because it is a PDF file.
GRBL Supported GCodes.pdf.TXT (325.4 KB)
NOTE: This is a generic list and not specific to the xTool.
Mike
What can be done with these codes, or how do we make use of them.
I wanted to have a look at the file but left my phone/laptop cable at the workshop.
That requires an education. GCode is a programming language, so some homework is required.
Unless you need to solve a specific program problem, knowing is not all that useful.
Thank you sir.
Well I am still experiencing odd behavior with multiple passes.
Working gcode
G1 X0.018Y-0.358
; Layer C02 Pass 2 of 4
G1 X-0.018Y-0.358
Non working gcode that includes z step for the pass ( generated by LB)
G1 X0.018Y-0.358
; Layer C02 Pass 2 of 4
G0 Z0.5
M4
Previously adding M5 after
G1 X0.018Y-0.358
fixed it, and I expect that is still the case. It would just be nice to not have to manually setup the gcode for the multipass jobs. As workarounds go, I have to say it’s at least an easy one even if I don’t like it.
As indicated earlier I am using the .lbdev file that Aaron.F made reference to in his response.
Come to think of it, I have no programming issues to solve right now tG, the machines singing like a bird.
Got my first pieces going to market tomorrow with a buddy of mine so we’ll see what happens.
Was just curious/puzzled by what further programming could do, that lightburn hasn’t already thought of.
1 Like
You are not the first xTool owner to say this. 