Tried uploading a g-code file to try out my first test cut and it gave me a SD Card error. See below code from the message log.
MSG:ERR: sdmmc_card_init failed code 0x0x102]
Power everything off and then back on again do you still see the same issue?
how large a file? @bar, how much space is available?
David Lang
I don’t think that it’s a space issue, I’ve gotten that error message a couple times, but I’ve always gotten it to go away with a restart. The SD card protocol is super picky about the initial values of all the pins on startup and I think there are some ways to make it confused…not sure exactly what they are.
I’m seeing this issue after the calibration I ran after updating both yaml and html files as well as firmware for 0.70.
Calibration ran fine, jogs fine, seems fine.
Even with 10 or so successive restarts of the board, including both via the Restart FluidNC button and via power cycling with a short wait for capacitors to drain, I was not able to get a load of the interface where that error wasn’t in the first few lines of the console. I attempted to load a file each time anyway and this also failed, as expected.
This sounds like it could be an issue with the .yaml file. That file tells the machine which pins the SD card is connected to
Reading through the forums a bit more it seems like that error message is more common on 0.7+ for some reason. I will look into it and see what I can figure out.
1 Like
Now that I am past calibration again I have run into this issue again.
Went to upload Gcode file and got this “No SD Card detected” error.
I also noticed I keep getting the “sdmmc_card _init failed” when I power on the M4.
Maybe this is a not enough memory issue? My File System shows I have only 12 KB left while my file 553 KB.
There are two storages on the Maslow. One is the one that you are seeing an SD error about, the other is the one you’re seeing the yaml and html files in.
You should first try a restart and then try replacing your Maslow.yaml file (back your current file up so you can copy across the calibration if you don’t want to have to redo that, too). If replacing that doesn’t work, I would grab the most recent firmware from the interstitial releases thread here on the forum in the software section.
Which version of the firmware are you currently on?
Im on the latest firmware 0.72.1 already.
Did a restart already but will play with that again later today.
Still no luck.
- Powered up the M4, saw the sdmmc_card _init failed error as per usual.
- Uploaded in yaml file
- Retract, Extend, Tensioned. No problem
- Go to upload nc file and still get No SD card detected.
I’m going to see if I can remove the SD card and put it back in. Maybe the connection isn’t great right now.
It’s not a separate SD card. they couldn’t handle the vibration, it’s soldered
in.
you may have a defective board if it’s saying that nothing is there after you
uploaded the yaml file and power cycled the system
David Lang
I am realizing this after taking the cover off to try to find it haha.
@bar any thoughts on if this is a defective board or not? I’m not sure what else to test at this point.
I figured it was soldered, but separate since I could access and update the yaml and html files but couldn’t upload or access uploaded G code.
It not being that way tells me Bar’s idea about the pins being referenced wrong in a busted yaml file might be less likely.
This is almost certainly an issue with the maslow.yaml file being corrupted. The maslow.yaml file contains the pin assignments to control the SD card and the stepper motors so if that file can’t be read properly the machine won’t be able to connect to those bits of external hardware.
The maslow.yaml file itself is stored on the ESP32’s internal memory so no need to connect to the SD card. Unfortunately that internal memory is only a few kb so we can’t upload gocde files there directly…hence the need for external storage
Ok I will try to using a new yaml file and transfer over the calibration values and see if that helps.
1 Like
@bar are there any unused ungrounded floating data pins in the SD card wiring?
2 Likes
Not that I’m aware of!
2 Likes
Just wanted to confirm that using a new a new yaml file has solved this issue for me and I was able to get my first cut in! Thanks everyone to get me to this stage!
Now running into some issues with Z-Axis, especially when switching router bits… trying to test a couple more things before starting a new topic on this.
1 Like
Interesting pocketing path. You might want to try a different program to generate your gcode. The pocket path should follow what it’s pocketing around. That will give you much smoother edges.
1 Like