-
-
Notifications
You must be signed in to change notification settings - Fork 369
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem: Disconnection error from SD Card #810
Comments
Quick update. I tried with another 1GB sd card, formatted with SD Card Formatter, and it was not detected at all from the web gui. I then decided to upload the original firmware (following link) from the MKS with their own uploading tool From their web gui and with all the 3 sd card (32, 1 and 1 GB) sd card previously used, I was able to send the same gcode several times with no errors. This result suggests me that it is probably a configuration problem of the yaml file...I guess... |
One possibility is that we switched from the Arduino SDCard driver to the one in the Espressif ESP-IDF framework. It will be difficult to debug this remotely, and without access to a card that fails. If you can send me a card that doesn't work I can investigate further. |
In what release did you switch from Arduino to Espressif sd driver? I can try to flash that firmware and check if that is the problem. No problem to send you a sd card that fails, you can send me your address via email to flavioprattico@gmail.com Otherwise we can use Anydesk so you can control my computer. I also have FluidTerm and the Espressif IDF on my computer. |
The switch occurred after 3.4.4. Remote control might work, but having the card in hand would be faster for me. Considering the severe time shortage I am up against, that is an important consideration. |
I flashed the 3.4.4 but now no one of the three is recognized, it always appears "No SD Card". Can you suggest me a compatible SD that I can buy in the meanwhile? |
I am starting to think that you might have a hardware problem on the DLC32 board. There have been numerous reports of different strange DLC32 behavior that could be explained by hardware quality problems - hardly surprising for something as inexpensive as DLC32. I have two DLC32 v1.1 boards. I just spent two hours trying to get the first one of them to connect to serial. I thought that it was a problem with the CH340 driver caused by my recent upgrade to Windows 11, but that was wrong. When I tried an MKS Tinybee (also CH340) that worked. Then I dug out my other DLC32 board and it worked too. I tested several old microSD cards - from Kingston, Adata, and SanDisk - with the working DLC32 v1.1. They all worked just fine. I used release firmware v3.6.7. |
It would be really strange a hardware problem because, as I said before, the three SD cards work perfectly with the original firmware from MKS. Anyway, before shipping you one of the SD card, I am going to buy a new MKS DLC32 V2.1 board and test it to check if really is a hardware issue. I will let you know! |
Finally I found the solution! Checking on a MKS repository on GitHub I found a fork of FluidNC. Inside I checked the yaml files and tested this one with the last release of FluidNC (namely 3.6.7) https://github.com/makerbase-mks/FluidNC/blob/main/example_configs/MKS_DLC32_BASE.yaml I did not check inside the differences with the official one in this repository, but it worked several times with all SD cards I had. |
@MitchBradley what do you suggest, I have to open a pull request in order to add this yaml file? |
I am hesitant to assume that this is solved until we know exactly which change in the config file fixed it. I do not see any differences that should matter. Perhaps you could try smaller changes to discover the exact difference between working and failing. |
Ok, I will do it! |
Hi, I put these settings (from link above by flavioprattic) into a config for MKS CNC32 board and the SD card works on that board as well now. None of the settings I had found elsewhere, or from MKS directly worked. sdcard: The IO diagram for the board from MKS says CS is on IO25, but actually is is IO15. |
I think the FNC wiki page has it right. |
Yes, but there is no entry for CNC32 and the detect pin quoted for DLC32 does not seem to work on CNC32 |
What is MKS CNC32? Do you have a link? |
Hi, yes https://www.aliexpress.com/item/1005005084530034.html |
Can we close this issue now? Sounds like this is an MKS problem. We waste a lot of time supporting their stuff for them. |
Macrobase CNC32 is not the same as Makerbase DLC32. Note "macro" vs "maker". Not only did they ripoff most of the design, they also ripped off the name. What a nuisance. This stuff is so inexpensive because they rip off everybody including us developers |
I guess the issue can be closed. Thanks for the support! |
I bought both units from Macrobase Aliexpress store just to add to confusion. The DLC32 packed up after less than one hour of use, they are sending a replacement. The CNC32 still working. |
If you have not already done so, please consider donating to the FluidNC project to help defray some of our costs in supporting this cheap Chinese stuff. |
Controller Board
MKS DLC32 V2.1
Machine Description
Just the MKS board with a stepper motor attached to the x axis
Input Circuits
No response
Configuration file
https://github.com/bdring/FluidNC/blob/main/example_configs/MKS_DLC32_21_XYZ.yaml
Startup Messages
User Interface Software
msftconnecttest.com
What happened?
Hello everyone!
I am trying to run a gcode file from the sd card plugged into the MKS DLC32 V2.1 board. I tried two different sd cards (1 GB and 32 GB), both formatted with SD Card Formatter, as suggested for windows users. I am able to upload the gcode file from the web gui, I can start it and, for random seconds, it works. Then it stops and if I click on the Refresh button it appears "No SD card". Then I have to reboot the board, connect to the FluidNC wifi and I can see, once again, the SD card content in the web gui.
I also tried to change the frequency to 10MHz us suggested here
#742
but I had same results.
I tested the same procedure also with previous releases of the FluidNC firmware (namely 3.5.1 and 3.6.1), but it does not change the results.
No problems sending longer or different gcode files over the serial with GCode sender or similar.
Other Information
Last FluidNC reales (3.6.7) flashed on the MKS board
The text was updated successfully, but these errors were encountered: