I threatened to do this some time ago as transferring pics from the camera via a USB cable has become annoying.
Based on the article below, I settled on a Toshiba FlashAir 64GB card which I picked up from Lazada.
We spend a lot of time reviewing the latest technology. It’s what we do. But every once in a while, something comes along that surprises even us. Flash memory was one of those advances. Now that flash memory has been around for years, it seems like something we take for granted.
Have no interest in using the phone app, just want the ability to quickly move photos from the camera to the PC.
After a quick search, I came across this great post from Matt’s Hub which helped me get the card up and running.
A few weeks ago I purchased this SD card on eBay. It’s a Toshiba Flashair card that allows you to connect to it over wifi and transfer files without having to insert it in the device that you’re transferring from.
This is my ‘go-to’ article on getting the card running in STA mode. Great work Matt! Also, check out the comments section as you might find a fix to your problem there.
More Windoze pain, as expected
In order to edit the CONFIG file as directed, I needed a working card reader, and the only ones I have are those attached to my laptops. I tried accessing the card on Linux first but no joy as the exfat filesystem was not recognized.
If you want to go down that path, check this out.
Fired up my VirtualBox and guest OS (Win 10) wasn’t recognizing the card reader. Here we go..
Luckily the fix was pretty straight-forward, as I found the info I needed in this article.
Also after restarting the VM I had to re-insert the card into the reader and then was GTG.
After editing the file with the recommended settings, I popped it into my camera and it worked. Well kinda, sorta if you get my drift.
I’m guessing maybe the issue is that I didn’t update the firmware. Thought I’d skip that step.
Downloaded FlashAirFWUpdateToolV4_v40004_K.exe via archive payload and tried to run. No dice, .NET Framework not loaded on my Win10 VM. Let’s fix that.
Downloaded and installed .NET Framework 4.8 from MS site. Rebooted VM and still no good with the installer stating “Microsoft .NET Framework 3.5 Full package or greater needs to be installed for setup to continue.”
I decide to abandon the firmware update and press on, seeing if I can tailor the CONFIG file on the card to play nicely.
I took a copy of what was on the original CONFIG file and blend it with some new settings as per Matt’s article. Even though I have specified the APPSSID and APPNETWORKKEY params, when I access the card via the browser (FF) it recognizes my AP but asks for the password.
Found more good info in this post here about different CONFIG directives. Worth a look.
I decide it’s best to assign the card a static IP address rather than letting DHCP do the job.
Then using map I can confirm the card is using the correct IP address sudo nmap -sn 192.168.2.0/24
Then it’s just a matter of entering the IP address in the browser and bookmarking the page for easier future access. All seems to be working well now, just as nature intended 🙂