I have downloaded and installed the 0.82 firmware, the index file and the maslow.yaml file. I am attempting initial calibration on a floor-mounted setup. I got the belts to retract, mounted them to the anchors, and in spite of putting what should be the right machine dimensions corresponding to 12’x8’, the machine pulled itself toward the bottom right corner right off my 8’x4’ platform that’s centered between the anchor points. I proceeded to extend all belts so it could be placed back in the middle of the platform and two belts wouldn’t extend with the dedicated button, but only using “Release Tension” over and over again. Once all were fully out I was getting an error that suggested calibration cannot happen without all belts being fully extended even when they were. I can see the spools (to confirm they’re all the way out) besides the long belts sitting on the ground.
The other - and potentially related - issue that had been intermittent, but is now constant in spite of attempts to restart FluidNC and to power cycle the machine is the one in my title line. I get an error that reads [MSG:ERR: sdmmc_card_init failed code 0x0x102].
The machine isn’t going to work unless it goes through the normal Retract All → Extend all process on start up. That is the place that I think we should start looking.
If you try to do Retract All and then Extend All what happens?
Ok after reloading the Maslow.yaml file, power cycling, and restarting fluidNC each several times, I got it to respond and not give that error. Then during the calibration it tried to pull itself way off the bottom right again. I stopped it before it left my 4x8 foot platform this time.
Now on the third try of doing all that (belts in, belts out, attach to frame, etc) it seemed to be trying to calibrate but stopped with a message unable to move safely. Nothing in the way and it was centered on the 4x8 and had tensioned all belts and then made two of them loose at the point when it threw the error.
Now I’m seeing the sdmmc_card_init error again:(
Machine width (mm) is 3660
Machine height(mm) is 2440
orientation horizontal
The Maslow is on the ground with anchors 2’ beyond the 4’x8’ sheet on each side, and the 4x8 is mounted the wide way - so 8’ left to right. I am referencing left and right based on the two power cords coming out the “bottom”.
What is the meaning of the sdmmc_card_init failed error code? Since we aren’t discussing it, is it to be considered harmless, or can it be at the root of my issues?
I have seen this error many times, and for me it has always resolved after a power cycle or two of the m4. It comes from the firmware not being able to initialize the configured sd card (really not a “card” in this case, as its hard-wired on the board).
Thanks Ron. It has been intermittent for me as well, but with my last 5-6 power cycles it didn’t resolve - and with my added calibration issues I didn’t have the desire to keep trying. The top concern at the moment is to figure out what’s going on with the calibration process. Did you also have initial calibration issues or no?
I did, but that was mostly on the older firmware, before it went in rings. Recent calibrations I started with numbers I got from @dlang’s tool here: http://lang.hm/maslow/maslow4_manual_calibration_simple.html by measuring as well as I could (Bar does not like recommending manual measurements, but this worked really really well for me). Also, calibration will only improve on the numbers, in theory.
The normal reason that this happens is that the maslow.yaml file tells the machine which pins to use to connect to the SD card. If the machine powers up and doesn’t read the maslow.yaml file correctly it won’t find the SD card and you will see that error message.
The quickest thing to try is just to delete the maslow.yaml file and replace it. If that doesn’t fix the issue we can send you a new controller board so we can be sure that the issue isn’t hardware related.
Hi Bar,
Sorry for the slow response. Work has kept me very busy. It is still happening. I have deleted and attempted to replace the yaml file several times. Once or twice when I had first powered up the unit after completing the build it connected but now it won’t regardless of what I do. I hope it turns out to be a simple hardware fix since it’s frustrating behavior.
