Error 20 after installing homing switches

[JohnJohn (John Johnson)]

ok… I’m looking at this right now.
Hang tight…

edit:
Did you press the Start button next to the green Synch indicator?

It doesn’t appear to be pushing data.

I can’t tell if it flashed the controller or if it’s waiting to start the flash.

Did it scroll a pile of data before all the black screen filled with white dots?

It looks like it’s connected.
The Start button should work and you should see lots go by.
I would have thought from the directions on github that it would have disconnected automatically after the flash operation was done.

I’ve downloaded the tool and I’m looking for an ESP32 based device to connect to.

[inspectorbill3 (Bill Fuller)]

still syncing since 3:30 eastern

[JohnJohn (John Johnson)]

When you installed the downloader tool there is an instruction manual.
Flash_Download_Tool__en.pdf
I’m reviewing this right now.

[inspectorbill3 (Bill Fuller)]

Yes I pushed start
did not scroll data before scrolling white dots
what do we need to do to verify that it is in the download mode?

[JohnJohn (John Johnson)]

I’m not certain. I did push the reset button in my exploration of this.

I did push start and stop.

Close any engraving software that may be open then test another COM port to see if anything is monopolizing the conversation.

When I selected the correct COM port the Flash Download Tool came to life.

I’ll have to get an ESP32 device and attempt to flash it.
The 8266 I had on my desk flashed just fine.
No programming mode change or programmer tool.

I just hooked it to the computer with the USB cable and flashed the first compatible binary file I could find.

[JohnJohn (John Johnson)]

I flashed it a second time for good measure and it went into the Synching mode for less than 2 seconds. The on board LED blinked a few times and it was done in less than 10 seconds.

I’m hoping that some other software grabbed your controller and the flash tool has been staring at your mouse for an hour…

[inspectorbill3 (Bill Fuller)]

3_8_error.txt (1.6 KB)
SPI mode DIO

[JohnJohn (John Johnson)]

You’re super-close.

The 8266 chip is one that I had on my desk. My apologies if that derailed you.

When the Downloader tool starts you should select the chip you have (and Develop under WorkMode of course).

According to the Schematic the chip is an ESP32S, but It could be an S2 or an S3

The number you need for this selection is on the shielded chip and probably immediately under (or beside) the word ESPRESSIF

Can’t quite tell from the pic… but again… close!

I’ll probably order one of these controllers so I can have one on hand for next time.

The error file you posted was really interesting.

The .py files are source code written in Python. If you’d like to use them we’ll likely have to generate a binary to flash to the microcontroller. I’m not sure if these can run MicroPython code as an option. I’ll double check this because I’m not fully certain.

The binary file seemed to work as expected, that’s the file that you need to download into the MKS-DLC32 controller.

[inspectorbill3 (Bill Fuller)]

I pulled the board for now and hooked up my old board.

[JohnJohn (John Johnson)]

This is great. I can’t guarantee that the answer is ESP32 with no S but I would test with that first and if it doesn’t take, test the ESP32-S3 because it’s supposed to be backward compatible to the S1.

The Datasheet says that it uses the ESP32-D0WDQ6 chip… So I’d assume it’s not a D2WD - but after an hour of pouring over the literature I’m going in circles trying to confirm.

If the .bin file works and you get a finished message, stop there, close the Downloader Tool and start LightBurn. Please, attempt to connect to the controller in LightBurn. It should connect outside the engraver. It may need power other than the USB cable - it can depend on the cable. If you download to it, it should connect to LightBurn with the Download tool closed.

When LightBurn connects, as part of the start-up or welcome message in the Console window, the controller should appear as the engraver would. The build option OPT:V… for the variable spindle (laser) should be shown when LightBurn Connects.

When the controller is not connected to the rest of the engraver, Homing Errors can be expected because the limit switch state doesn’t change within the allotted number of steps counted out by the controller.

Once it’s connected and after the homing error (if it happens) please request the Machine Settings report $$ from the Console window in LightBurn.

Please copy and paste the Welcome Message and the Machine Settings report into a reply here.

We can compare these settings to what you shared previously and set them back if need be. The variable spindle option is Key to getting the laser working and I get the sense that you’re really close.

[inspectorbill3 (Bill Fuller)]

Thanks I’ll give it a try tomorrow

[inspectorbill3 (Bill Fuller)]

Well I tried every ESP UART and even USB( when available) also hooked up to another computer setup same results, white dots and more white dots.

[JohnJohn (John Johnson)]

The only other thing that I would test is 80 kHz instead of 40 kHz. I did find mention of 80 kHz in the data sheet but it directly conflicted with the manufacturers instructions at GitHub. Plus, it appeared to me that you flashed a binary for an ESP 8266 into your makerbase controller.

When connected with just the USB cable, do the power and receive-data lights come on.

I’m going to get one of these on order so I can test this.

[inspectorbill3 (Bill Fuller)]

I will try 80 instead of 40. I tried flashing binary on every option. I wonder do I need to erase feature?
Yes usb power and receive-data lights.

[inspectorbill3 (Bill Fuller)]

80khz same results marching dots

[JohnJohn (John Johnson)]

@inspectorbill3

I wonder do I need to erase feature?

I wouldn’t think so, but it may be worth an attempt.

[inspectorbill3 (Bill Fuller)]

I was wrong with just usb and no 12volts there are no lights on or flashing. Erase gives same results marching ants.