MK3 do not see FlashAir card?
Hi,
I have Prusa MK3 and a 16 Gb Toshiba's FlashAir W-04 WiFi card formatted in FAT-32.
1. The MK3 is working fine with the stock 8 Gb card.
2. The FlashAir card works fine if inserted into PC or Canon camera.
3. However, if I insert FlashAir card into MK3 - then MK3 says "No SD card".
I checked that I insert the card the proper way (contacts are up, logo down). I have tried to reboot MK3 while card is inserted. I have tried to select card type = FlashAir in MK3's settings. I have tried to reboot after settings change while card is inserted. Nothing helps.
However, MK3 is able to tell when card is inserted and removed. E.g. if I turn it on without card, and then insert the card - MK3 will tell me that the card was inserted, but still fails to recognize it saying that there is no SD card.
BTW, if I select "No SD card" in the menu - MK3 will show empty directory tree.
MK3's firmware is the latest one.
What am I missing here?
Re: MK3 do not see FlashAir card?
Fully insert the card, then pull it out about 1mm. Mine will recognize the card when I do this.
Re: MK3 do not see FlashAir card?
+1 for bobstro's suggestion. I had the exact same issue, and pulling it out just that much made it work again. I leave mine in and it has worked flawlessly since.
RE: MK3 do not see FlashAir card?
I came across this post when I was trying to get a 64GB FlashAir W-04 up and running with my MK3S. bobstro's suggestion is appreciated but unfortunately did not help me either. I had initialized the card using the FlashAir software but had not formatted it as FAT32. I had issues with the Toshiba FlashAir software on both Windows and Mac, something about the card not being detected by the software. Despite those errors, I was able to get it working.
I ended up going through the following steps to get my setup working:
- Format the card as FAT32 using Disk Utility application on MacOS
- Initialize the SD card using the Toshiba FlashAir application on MacOS - note that this didn't seem to complete successfully, but when I checked, the directory tree and config file had been generated (which is what you need to modify)
- Update the config file to support the following:
- WebDav = 2 (read/write)
- Static IP address (no DHCP, IP, subnet mask, default gateway) - make sure the address you choose isn't in your router's DHCP range
- AppMode = 5 (WiFi client, automatically connect)
APPNAME and UPDIR can be whatever you want as far as I know. I believe APPNAME needs to be unique if you have multiple FlashAir cards on the network. Make sure you don't change your CID and FW version. You can use any text editor (I used Vim) to modify the config file. My full config file is below:
[Vendor]
CIPATH=/DCIM/100__TSB/FA000001.JPG
VERSION=<your card's VERSION>
CID=<your card's CID>
PRODUCT=FlashAir
VENDOR=TOSHIBA
APPNAME=<whatever you want>
APPMODE=5
APPSSID=<your WiFi SSID>
APPNETWORKKEY=<your WiFi Key>
DHCP_Enabled=No
IP_Address=192.168.0.xxx
Subnet_Mask=255.255.255.0
Default_Gateway=192.168.0.x
UPDIR=/<some dir>
WEBDAV=2
After applying this config, my MK3S recognized the card and I was able to mount it on my Windows machine and export g-code directly from Prusa Slic3r. 👌
Hope it helps you as well!
RE: MK3 do not see FlashAir card?
I had a similar issue with a 64Gb Toshiba FlashAir card (reformatted to Fat32). I decided to join GitHub and set up Visual Studio Code to do some debugging using the 3.7.2 Firmware branch. I eventually got my Mk 2.5 to properly recognize my card by altering the firmware slightly. I realize this may not be of much help to you immediately, but I'll see if I can notify the devs about what I did. I'll post the details below in case someone else can make use of it.
[boring details FWIW]
I found that in Sd2Card.cpp::init, after CMD0 is sent to the card and gets the proper response, the CMD8 that is sent next is receiving back R1_ILLEGAL_COMMAND instead of the R7 response. After much googling, I added code after the CMD0 is sent and before sending CMD8 to repeatedly send 0xFF until the card sends back 0xFF (or it times out). This is apparently sometimes needed to give extra clock cycles to the card to allow it to do work to get ready for the next command. Apparently some (but not all) cards require this to function correctly.
According to google, it's suggested to send 0xFF before every command, but at least for my card it was necessary only between CMD0 and CMD8.
Rob H.