I have a Yorahome laser that I replaced the controller with with MKSDLC32. I can not get the laser to come on with a program (fire button works and the wireless interface works.
Here are my starter questions:
When creating laser manually, what selection should I use? GRBL, GRBL-LPC, GRBL M3?
I added limit switches and set the home to lower left. The home button works and when I try to create a simple program (circle) I get an out of bounds error and the gcode is showing negatie values. What did I mess up?
In console type $H $$ enter and paste results.
GBRL should be the one to use.
$0=10
$1=25
$2=0
$3=1
$4=0
$5=1
$6=1
$10=1
$11=0.010
$12=0.002
$13=0
$20=1
$21=0
$22=1
$23=3
$24=300.000
$25=1000.000
$26=250.000
$27=1.000
$28=5000.000
$30=10000.000
$31=0.000
$49=10.000
$32=1
$38=1
$40=1
$100=80.000
$101=80.000
$102=80.000
$103=100.000
$104=100.000
$105=100.000
$110=6000.000
$111=6000.000
$112=6000.000
$113=1000.000
$114=1000.000
$115=1000.000
$120=500.000
$121=500.000
$122=500.000
$123=200.000
$124=200.000
$125=200.000
$130=450.000
$131=450.000
$132=50.000
$133=300.000
$134=300.000
$135=300.000
$30 needs to be equal to the S-Value Max value in the Device Settings.
Most commonly you donāt get to set the home to your choosingā¦ May be related to the other issues. However, that sounds like the correct cornerā¦
Did you pull the information on the setup from somewhere?
I have one of these controllers ā¦ sitting on my desk 
Thanks. I think you mean $130 & $131 for the x and y max. I have them set in lightburn but I just updated the controller.
No I could not find any setup info for this and I am sure I have the lightburn config all messed up.
I can fire the laser using the āFIREā button on the move menu but it will not run when trying to cut a simple circle
I think I have the wrong device type selected. I save the gcode and it is using M4 and when I use the wifi web gui for the board and do a test fire it uses M3
1 Like
Your $30 value is 10000, the default S-Value Max is 1000 ā¦ check and make sure they are the same.
Thanks for the suggestions. I found on another post that this is a firmware issue with the DLC32 and downgraded it to make it work right
You too? 
Iāve just arrived, letās see if the issue is solved. If not, Iām also here to support in whatever need.
Excellent choice on the controller. I have an MKS DLC32 as a desk-mule to poke at. Iām going to attempt to install it on a Sainsmart 3040 for some light cnc testing.
MKS-DLC32 has newer variable spindle software (in Python) that replaces the original one in standard Grbl 1.1. This causes the āVā to not appear in the Build option and the Warning to appear in the Console window in LightBurn. I assure you that the variable spindle option is present and controlled by M3 on regular GRBL.
I just tested it with the Fire button on 4% and 8% power with a volt meter.
Regular GRBL. GRBL-M3 is much earlier.
Generally yes, but this controller is quite exceptional. Thereās a config file and another couple of blocks of settings to mess with.
The engraver is likely expecting a workspace-offset like most CNC controllers.
After connecting, confirm the units are set to measure speed in mm per minute. Itās advisable to change this in the Settings window in LightBurn if itās not (mm/min).
Next, open the Move window and set the distance and speed values very low, Iām using 30mm/min and a distance of 5mm.
Next, use the compass arrows around the house on the left side of the Move window to confirm that jogging motions coincide with the compass arrows.
If they do, which corner does the engraver attempt to home toward.
If the arrows donāt correspond to the expected motion, we can adjust.
I have mine on my desk to fool with, but havenāt tried to configure it for any particular machine. Donāt know how easy it will be on the DLC32ā¦ I havenāt seen anything that outlines a basic procedure to get this rightā¦ Sounds like a good job to you
Iāve seen Ruida configured to be used in all four corners ā¦ I think youād be foolish to build a general controller, that you couldnāt configure the home position.
However, Iāve tried to help more than one person to move the machine home or origin. All of them have had to pay someone for phone help to get it squared awayā¦ this was with a Ruida.
So I generally say you donāt get to chose.
I have to find the latest firmware anywayā¦ do you know if itās on the Github site?
1 Like
I learned the hard way that the Screen size is one of the ābuild-timeā options so the screen size mattersā¦ Do you have the H24 or H35 screen?
I used this Firmware:
The parallel one thatās likely to work with the other screen option is here:
I havenāt tested the firmware required for the larger screen.
$S dumps some of the advanced codes:
grbl esp is a good reference:
It looks like a direct āliftā. 
Hereās a fuller answer.
https://forum.lightburnsoftware.com/t/flame-detector-on-mks-dlc32-board/107643/13
Thanks
I have the TS35-R V2.0 screen.
I will check these outā¦
1 Like
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.