MKS DLC32 device

Need help selecting correct device for MKS DCL32 card. GRBL causes M4 gcode error. GRBL pre 1.11f does not have continuous laser power checkbox.

“GRBL” is most like the correct device type.

What is the specific error?

Can you run this in Console and return output:

$I

$I

[VER:1.1.2022051001:]

[OPT:PHSW]

[MSG:Using machine:MKS DLC32]

[MSG:Mode=AP:SSDI=MKS_DLC:IP=192.168.4.1:MAC=B8-D6-1A-2E-56-31]

ok

Your firmware is not compiled with variable spindle. I’d suggest finding a more recent firmware with laser/variable spindle compiled in.

I found the latest firmware on github and flashed. Here is console from flash:

C:\MKS DCL32\MKS-DLC32-main\MKS-DLC32-main\firmware\TS35\Laser\Normal\Board_V2.0\V2.0.8_H35_20220105_N.bin
Command: esptool.py --port COM4 --baud 921600 --after no_reset write_flash --flash_size 4MB --flash_mode dout 0x00 C:\MKS DCL32\MKS-DLC32-main\MKS-DLC32-main\firmware\TS35\Laser\Normal\Board_V2.0\V2.0.8_H35_20220105_N.bin --erase-all

esptool.py v3.3-dev
Serial port COM4
Connecting.........
Detecting chip type... Unsupported detection protocol, switching and trying again...
Connecting.........
Detecting chip type... ESP32
Chip is ESP32-D0WD (revision 1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
Panel-0 MAC: b8:d6:1a:2e:56:30
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 921600
Changed.
Configuring flash size...

 Panel-0 Erasing flash (this may take a while)...


 Panel-0 Chip erase completed successfully in 4.5s
Compressed 4194304 bytes to 1099450...

Panel-0 Writing at 0x00000000... (1 %)
Panel-0 Writing at 0x00012438... (2 %)
Panel-0 Writing at 0x00021d54... (4 %)
Panel-0 Writing at 0x0004cbc1... (5 %)
Panel-0 Writing at 0x00098928... (7 %)
Panel-0 Writing at 0x000c10de... (8 %)
Panel-0 Writing at 0x000e03c2... (10 %)
Panel-0 Writing at 0x000ea6fa... (11 %)
Panel-0 Writing at 0x000f5278... (13 %)
Panel-0 Writing at 0x000ff3e0... (14 %)
Panel-0 Writing at 0x001100d6... (16 %)
Panel-0 Writing at 0x0011ce99... (17 %)
Panel-0 Writing at 0x001362e7... (19 %)
Panel-0 Writing at 0x0013c271... (20 %)
Panel-0 Writing at 0x001424d3... (22 %)
Panel-0 Writing at 0x00147e2b... (23 %)
Panel-0 Writing at 0x0014df27... (25 %)
Panel-0 Writing at 0x00154100... (26 %)
Panel-0 Writing at 0x0015abad... (27 %)
Panel-0 Writing at 0x00160800... (29 %)
Panel-0 Writing at 0x00166714... (30 %)
Panel-0 Writing at 0x0016bcf3... (32 %)
Panel-0 Writing at 0x0017137c... (33 %)
Panel-0 Writing at 0x00176784... (35 %)
Panel-0 Writing at 0x0017c5c2... (36 %)
Panel-0 Writing at 0x0018240f... (38 %)
Panel-0 Writing at 0x00187700... (39 %)
Panel-0 Writing at 0x0018c8e3... (41 %)
Panel-0 Writing at 0x00191e14... (42 %)
Panel-0 Writing at 0x001973ee... (44 %)
Panel-0 Writing at 0x0019c7d0... (45 %)
Panel-0 Writing at 0x001a3a9d... (47 %)
Panel-0 Writing at 0x001abde2... (48 %)
Panel-0 Writing at 0x001b1628... (50 %)
Panel-0 Writing at 0x001b6e61... (51 %)
Panel-0 Writing at 0x001bc7e2... (52 %)
Panel-0 Writing at 0x001c26e2... (54 %)
Panel-0 Writing at 0x001c7fb0... (55 %)
Panel-0 Writing at 0x001cda31... (57 %)
Panel-0 Writing at 0x001d3347... (58 %)
Panel-0 Writing at 0x001d906d... (60 %)
Panel-0 Writing at 0x001dec14... (61 %)
Panel-0 Writing at 0x001e5810... (63 %)
Panel-0 Writing at 0x001eb2ff... (64 %)
Panel-0 Writing at 0x001f1158... (66 %)
Panel-0 Writing at 0x001f6ebc... (67 %)
Panel-0 Writing at 0x001fca36... (69 %)
Panel-0 Writing at 0x0020281a... (70 %)
Panel-0 Writing at 0x00208626... (72 %)
Panel-0 Writing at 0x0020e173... (73 %)
Panel-0 Writing at 0x00214158... (75 %)
Panel-0 Writing at 0x0021a964... (76 %)
Panel-0 Writing at 0x00220d89... (77 %)
Panel-0 Writing at 0x00226efa... (79 %)
Panel-0 Writing at 0x0022d6b2... (80 %)
Panel-0 Writing at 0x002332f0... (82 %)
Panel-0 Writing at 0x003104d0... (83 %)
Panel-0 Writing at 0x00318326... (85 %)
Panel-0 Writing at 0x00320622... (86 %)
Panel-0 Writing at 0x003289b7... (88 %)
Panel-0 Writing at 0x00330e4d... (89 %)
Panel-0 Writing at 0x003391d0... (91 %)
Panel-0 Writing at 0x00341676... (92 %)
Panel-0 Writing at 0x00349b03... (94 %)
Panel-0 Writing at 0x00351eda... (95 %)
Panel-0 Writing at 0x0035a453... (97 %)
Panel-0 Writing at 0x0036282b... (98 %)
Panel-0 Writing at 0x0036a9b3... (100 %)
Wrote 4194304 bytes (1099450 compressed) at 0x00000000 in 21.4 seconds (effective 1570.3 kbit/s)...
Hash of data verified.

Leaving...
Staying in bootloader.

Firmware successfully flashed. Unplug/replug or reset device 
to switch back to normal boot mode.

After connecting to lightburn here are console output on connection:

Waiting for connection...

ets Jun 8 2016 00:22:57

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)

configsip: 0, SPIWP:0xee

clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00

mode:DOUT, clock div:1

load:0x3fff0018,len:4

load:0x3fff001c,len:1044

load:0x40078000,len:10124

load:0x40080400,len:5856

entry 0x400806a8

[MSG:Using machine:MKS DLC32]

[MSG:X Axis limit switch on pin GPIO(36)]

[MSG:Y Axis limit switch on pin GPIO(35)]

[MSG:Z Axis limit switch on pin GPIO(34)]

Grbl 1.1 ['$' for help]

Your Grbl may not support Variable Power mode (M4)

If your laser does not turn off between cuts,

switch to the GRBL-M3 device

[Info]no exit update file

[MSG:Local access point MKS_DLC started, 192.168.4.1]

[MSG:Captive Portal Started]

[MSG:HTTP Started]

[MSG:TELNET Started 23]

[MSG:'$H'|'$X' to unlock]

Grbl 1.1 ['$' for help]

[MSG:'$H'|'$X' to unlock]

[MSG:Caution: Unlocked]

ok

ok

ok

[VER:1.1.2022010501:]

[OPT:MPHSW]

[MSG:Using machine:MKS DLC32]

[MSG:Mode=STA:SSID=:Status=Not connected:IP=0.0.0.0:MAC=B8-D6-1A-2E-56-30]

[MSG:Mode=AP:SSDI=MKS_DLC:IP=192.168.4.1:MAC=B8-D6-1A-2E-56-31]

ok

My test pattern is a simple 1 inch square.
Frameing appears to work fine without laser enabled.
When framing with laser enabled this is the resulting console msg:

<Idle|MPos:0.000,0.000,0.000|FS:0,0|Pn:P|WCO:0.000,0.000,0.000>

ok

Starting stream

Stream completed in 0:01

ets Jun 8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x3 (DOWNLOAD_BOOT(UART0/UART1/SDIO_REI_REO_V2))

waiting for download

Observation: laser starts moves 1 in in x+ direction and starts to move in y+ direction but stops.

When running the produced Gcode here is the console results:

Starting stream

Layer C00 Pass 1 of 2

Layer C00 Pass 2 of 2

Stream completed in 0:00

��0x00,cs0_drv:0x00,hd_drv:0x00,

[MSG:Using machine:MKS DLC32]

[MSG:X Axis limit switch on pin GPIO(36)]

[MSG:Y Axis limit switch on pin GPIO(35)]

[MSG:Z Axis limit switch on pin GPIO(34)]

Grbl 1.1 ['$' for help]

Your Grbl may not support Variable Power mode (M4)

If your laser does not turn off between cuts,

switch to the GRBL-M3 device

[Info]no exit update file

[MSG:Local access point MKS_DLC started, 192.168.4.1]

[MSG:Captive Portal Started]

[MSG:HTTP Started]

[MSG:TELNET Started 23]

[MSG:'$H'|'$X' to unlock]

Grbl 1.1 ['$' for help]

[MSG:'$H'|'$X' to unlock]

[MSG:Caution: Unlocked]

ok

ok

[VER:1.1.2022010501:]

[OPT:MPHSW]

[MSG:Using machine:MKS DLC32]

[MSG:Mode=STA:SSID=:Status=Not connected:IP=0.0.0.0:MAC=B8-D6-1A-2E-56-30]

[MSG:Mode=AP:SSDI=MKS_DLC:IP=192.168.4.1:MAC=B8-D6-1A-2E-56-31]

ok

Observation: similar to frame observation.

GRBL Settings:

ok

$$

$0=10

$1=25

$2=0

$3=5

$4=0

$5=1

$6=0

$10=1

$11=0.010

$12=0.002

$13=0

$20=0

$21=1

$22=1

$23=5

$24=300.000

$25=1000.000

$26=250.000

$27=1.000

$28=1000.000

$30=1000.000

$31=0.000

$32=1

$38=1

$40=1

$100=80.000

$101=80.000

$102=520.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

ok

This actually looks like an older firmware from Jan 2022 vs May 2022. In any case, this also seems like it doesn’t support variable spindle. You would expect to see a ‘V’ in the list of OPT codes listed.

Thanks, I’ll dig into that. Appreciate the"V" tip also.

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