Wireless access of M3s with SD cardToshiba FlashAir  

RE: Wireless access of M3s with SD cardToshiba FlashAir

That's because the max size SD card that can be read by the printer is 32gb.  You could potentially format the card at a lower capacity which may allow it to be read. 

RE: Wireless access of M3s with SD cardToshiba FlashAir

Ha!

never crossed my mind 64GB would be an issue in these days 🙂

I will try to format it to 32GB, see what happens.

Thank you very much for your insight.

RE: Wireless access of M3s with SD cardToshiba FlashAir

Hm... seems like I ended up with wrong capacity SD. Tried to format it as 32GB but this piece of software from Toshiba called "FlashAirFWUpdateToolV4" refuses to initialize the card.

When I format it to full 64GB capacity, with some considerable hassle I am able to put it back into workable condition again but anything else is simply no go.

RE: Wireless access of M3s with SD cardToshiba FlashAir

 I have the same card and I discovered that there’s a timing issue with some cards being recognized by the firmware during the card initialization phase. I have a simple software fix that I’m going to request be pulled into the official firmware.  For what it’s worth, the firmware  seems to recognize my 64 Gb card just fine, although I did have to reformat it to Fat32 first.

See https://forum.prusa3d.com/forum/original-prusa-i3-mk3s-mk3-hardware-firmware-and-software-help/mk3-do-not-see-flashair-card/#post-103876

RE: Wireless access of M3s with SD cardToshiba FlashAir

Yeah, there's been a github issue on that for a while ( https://github.com/prusa3d/Prusa-Firmware/issues/1685 ) but no movement. Same with the IP address no longer being shown.

RE: Wireless access of M3s with SD cardToshiba FlashAir

Thank you for your posts!

Very useful. I need to read through the threads, had no clue this was actually such an issue.

At the moment, I am struggling to re-format the FlashAir card back to it's original state. In one instance I succeeded to format it but since then, when I tried to shrink down to 32GB, the FlasAir software from Toshiba never finishes the formatting process any more. I have to get back to this when I have time.

 rob-h2: if I understand you well - you can use full 64GB capacity in FAT32 mode and the printer recognizes the card? Just asking because my attempts to make it 32GB failed so far.

RE: Wireless access of M3s with SD cardToshiba FlashAir

Do you know if the lack of delay in initialization was also what was causing the IP to not be displayed on the printer?

RE: Wireless access of M3s with SD cardToshiba FlashAir

Posted by: Makak007

 rob-h2: if I understand you well - you can use full 64GB capacity in FAT32 mode and the printer recognizes the card? Just asking because my attempts to make it 32GB failed so far.

What I can confirm is that my card is formatted as a 64GB Fat32 card, and with my software tweak the printer is able to browse up and down through the various folders and files I put on the card to test it. There are only a few folder and files, so I have no idea if the printer could still access all files if the card was full. Still, that's and edge case and probably not worth worrying about. 

RE: Wireless access of M3s with SD cardToshiba FlashAir

Posted by: vintagepc

Do you know if the lack of delay in initialization was also what was causing the IP to not be displayed on the printer?

No idea - before it was recognizing the card, I don't remember checking to see if I could see the card on my network when it was plugged into my printer. What I did do was spent a lot of time messing about with the contents of the Config file on the card to get it to work in station mode when plugged into my PC. Once that was working and the printer was recognizing the card, I was able to see the card from my PC via WiFi. So I'd suggest get it working with your PC first.

Here's my Config:

[Vendor]

CIPATH=/DCIM/100__TSB/FA000001.JPG
APPMODE=5
APPNETWORKKEY=************
VERSION=F15DBW3BW4.00.02
CID=02544d535736344755f458987a012401
PRODUCT=FlashAir
VENDOR=TOSHIBA
COMMAND=fat cp /SD_WLAN/BCONFIG 1:/BCONFIG
COMMAND=fat cp /DCIM/100__TSB/FA000001.JPG 1:/FA000001.JPG
FILEIO=0
MASTERCODE=EC21E52DBC9E
APPSSID=ELWIN-G
LOCK=1
DNSMODE=1
APPAUTOTIME=1800000
UPDIR=/
WEBDAV=2

RE: Wireless access of M3s with SD cardToshiba FlashAir

Thank you.

RE: Wireless access of M3s with SD cardToshiba FlashAir

Spared a moment to experiment a little bit. I succeeded, here is what I did:

1 - I have 64GB FlashAir TOSHIBA SD card W-04

2 - I removed the old partition and added a new one: FAT32, set as ACTIVE, formatted in notebook SD card reader (no formatting in camera, etc.)

3 - I used older version of FlashAirFWUpdateToolV4_v40002 and successfully formatted the SD card (latest version FlashAirFWUpdateToolV4_v40004 only kept checking software version in closed loop with no successful formatting at all)

4- Inserted the FlashAir SD into Prusa3D i3 MK3S and voila, it sees the G-Code folder, I mapped the network location (set fixed IP first). I can read and write, though connection is terribly slow (might be my Wifi signal is too bad???) but it works. As long as this state lasts, I will be happy and 99% satisfied.

Code I used (followed the example given at prusa web):

[Vendor]
APPSSID=mynetssid
APPNETWORKKEY=mypassword
CID=025cidofmyflashaircard012201
VERSION=F15DBW3BW4.00.02
APPMODE=5
APPNAME=3D_printer
LOCK=1
PRODUCT=FlashAir
STA_RETRY_CT=0
UPDIR=/G-Code
UPLOAD=1
VENDOR=TOSHIBA
WEBDAV=2

When I delete a gcode file via my computer, in printer menu I need to jump one level up and then back to G-Code folder in order to refresh the list of gcodes, otherwise list is confusing and incorrect.

That's it so far, will test it for a couple of days to see if any issues surface.

RE: Wireless access of M3s with SD cardToshiba FlashAir

My config for my i3 is ;-

[WLANSD]
ID=PrusaSD
DHCP_Enabled=NO
IP_Address=192.168.1.201 <- replace with whatever fixed IP address you want to use for your network 
Subnet_Mask=255.255.255.0
Default_Gateway=192.168.1.253 <- replace with your networks default gateway
Preferred_DNS_server=192.168.1.253 <- replace with your networks default DNS server
Alternate_DNS_Server=192.168.1.253
Proxy_Server_Enabled=NO
Proxy_Server_Name=192.168.1.253
Port_Number=8080

[Vendor]
CIPATH=/DCIM/100__TSB/FA000001.JPG
APPMODE=5
APPNETWORKKEY=************ <- replace with your networks access password
VERSION=F15DBW3BW4.00.02 <- this should be the firmware version of your card which may be different
CID=02544d535731364754d33b687a012101
PRODUCT=FlashAir
VENDOR=TOSHIBA
APPSSID=Higgins Home <-replace with your networks id
LOCK=1
DNSMODE=1
APPAUTOTIME=1800000
MASTERCODE=ec21e51b21c3
UPLOAD=1
UPDIR=/ <- with this you can access the root of the card rather than a subfolder.  Not important for a prusa but something like a cr10 can only read from card root
WEBDAV=2
TIMEZONE=0
NOISE_CANCEL=0
appname=PrusaSD

RE: Wireless access of M3s with SD cardToshiba FlashAir

So I'm running a FlashAir 32 GB W-04 on my mk3S using firmware 3.7.2, and it works as expected as long as the printer stays powered on. But when I turn the printer off, then back on, it doesn't know there is an SD card in the slot. I have to remove it, and reinsert it multiple times before it recognizes there is a card in the slot. I got the card to reduce the wear and tear on the printer card reader, but this defeats that purpose. Anyone else have this issue? Anyone know of any fixes for this?

RE: Wireless access of M3s with SD cardToshiba FlashAir

Possibly stupid question but do you have the printer settings option set for a flashair card enabled ?  Not near printer at the moment but there's a setting you can change to tell the printer it has a flashair installed.  I think it changes some initialisation stuff at power on.

RE: Wireless access of M3s with SD cardToshiba FlashAir

This is a known issue that's been reported to the github. Some cards take longer to initialize and as a result the printer can't see it when it tries.

RE: Wireless access of M3s with SD cardToshiba FlashAir

Well, here's an interesting additional observation: When I went to Settings>>Sort and selected "none", the FlashAir was recognized as being loaded on printer power-up. I tried this with Settings>>SD Card set to both "flshAir" and "normal" with the same result. So vintagepc, your hint

Some cards take longer to initialize and as a result the printer can't see it when it tries.

made me try this experiment, so thanks. And neophyl, your question

...do you have the printer settings option set for a flashair card enabled ? 

prompted me to run testing with Settings>>SD Card set to both "flshAir" and "normal", and they both operated identically, as far as I can tell. So I don't know what this setting really does. Note that I have a W04 card, so I get no IP address reported on the printer anyway.

So for now, I'll operate with sort turned off, and see how I like it. I generally keep the FlashAir mostly empty, so the lack of a sorted file listing is not a big deal for me. Thanks for replying guys...Jack

RE: Wireless access of M3s with SD cardToshiba FlashAir

By the way, what about your gcode file sorting?
On my regular card (came with the printer) I am sorting by creation time - youngest files first, oldest at the bottom. But that is not the case with my FlashAir. Any idea if something can be done about thid or is it a bug?

RE: Wireless access of M3s with SD cardToshiba FlashAir

I just loaded the new 3.8.0 firmware, and the problem is solved. The printer recognizes the FlashAir as an installed card, and my PC can see the mapped drive and download to it. Same for PrusaSlicer. I've tried using both the FlashAir and the "normal" settings for the SD card, and they seem to both work, identically as far as I've detected. So, problem solved.

RE: Wireless access of M3s with SD cardToshiba FlashAir

@jack That’s great that it’s working for you now. 🙂  The new version has changed the timing on your printer enough that the card will properly initialize.  For others, using 3.8.0 has not fixed their FlashAir init problem, so it’s still hit and miss.  There is no fix in 3.8.* that specifically addresses the FlashAir issue, but a few people have had success with it. FWIW to those reading this, the pull request for a fix for this issue is now labelled with 3.9.*  so it might be included in the next minor release.