Accrssing THEC64 Wirelessly With A Sandisk Wireless Connect
May 13, 2020 20:40:44 GMT
jj0 likes this
Post by kolonelpanick on May 13, 2020 20:40:44 GMT
Here’s is all the info you need on using a Sandisk Wireless Connect USB stick with THEC64.
BACKGROUND
The Sandisk Wireless Connect (WC) is advertised as a USB stick that functions as an access point, which can be accessed via the manufacture’s mobile app or through a web interface. Less clear is that the device can join a previously existing network and be accessed by WebDAV, which can make managing files for THEC64 easier.
SETTING UP THE WIRELESS CONNECT
Begin by updating the WC’s firmware (charging it beforehand is probably a good idea). The firmware can be downloaded from Sandisk. In my case, the device refused to join any networks after doing so, which required me to do a hard reset (hold down the power button for 15 seconds to accomplish this).
Once you’re up to date, you’ll need to begin configuring the device. Remove it from your computer (you can leave it connected to a charger if you wish). It will appear as an open wireless network. Some options can be configured through the device’s web interface, but many things are missing (like the option to have it join a preexisting wireless network).
To access all of the options you’ll want to grab the WC’s mobile app. Once you have it, begin by changing the device’s SSID (under “Change Drive Name”) and giving it a password (“Set Password to Drive”). The same password will be used for accessing the device through WebDAV or the web interface later on.
Now, go to “Internet Connection” in the WC app and enter the details for your network. Note that the device cannot connect to 5ghz access points.
Unfortunately, there’s no way to assign an IP address manually — so you’ll need to do that through your router. Go to “About” under settings to find the WC’s MAC address and then assign it an IP address in your router’s configuration page (oftentimes you’ll find this option under DHCP settings).
After a static IP address has been set, reboot the WC. It should then grab the IP address you assigned it in the router. To verify this, go back to “About.”
[Note: If you don’t mind connecting to the WC access point on the device you intend to manage THE64 with it is not necessary to have it join your network. In that case, the WC can be accessed via 172.25.63.1.]
ACCESSING THE WIRELESS CONNECT
There are three ways to manage the WC: through the mobile app, via a web browser, or using WebDAV.
The web interface allows let you add/delete files and create folders, but lacks some of the more sophisticated options you’d find in a file manager (like the ability to open files in an editor and save them on the fly).
To access the WC by its web interface go to the following address:
The username is “owner” and the password is identical to the wireless password. Replace the Xs with the WC’s actual IP address.
To access the WC using WebDAV (preferred) grab Cyberduck, which is available for both macOS and Windows. For some reason, the newest version of Cyberduck does not work properly with the WC. The following versions are confirmed to work:
If you’re adventurous, try and find the newest version that works properly — I didn’t have enough patience. The newest release will connect to the WC, but fail when transferring files.
Likewise, the WebDAV client built into Windows File Explorer doesn’t play nice with the WC. Using “Add a network location” produces an error stating that the entered folder is not valid — even though it most certainly is. On the other hand, using “Map network drive” yields some success — but only temporarily in my experience.
Finder’s built in WebDAV client in macOS can access the WC, but unfortunately only in read-only mode.
I did some rudimentary testing in Linux with Xfce in Debian 10 and had mixed (i.e., unpredictable) results. Perhaps someone can suggest a suitable Linux client or share their outcomes in other desktop environments.
[Edit: I’ve since had successful results in Linux with the cadaver command line app.]
The iOS app FileBrowser connects to the WC without issue.
CONFIGURING CYBERDUCK
The main benefit of Cyberduck over the web interface is that it allows you to edit files on the WC. For example, a .cjm file can be opened in Notepad++ or a .D64 file can be opened in DirMaster — provided that file associations are set up properly in Windows Explorer.
To configure the WC in Cyberduck create a WebDAV bookmark that specifies the server (set to the WC’s IP address) and path (set to /files under “More Options”). In addition, it’s probably a good idea to set “Transfer Files” to “Use browser connection.” That should prevent Cyberduck from opening multiple connections simultaneously, which the WC might not be able to handle.
Like when accessing the web interface, enter the username “owner” and your wireless password. Strangely, I couldn’t find the username in any of Sandisk’s official documents.
USB VS. WIRELESS MODE, POWER, AND THEC64
Wireless remains active on the WC even when it is mounted. However, access to the filesystem over wireless is disabled.
Oddly, THEC64 doesn’t unmount the WC when it’s shut off. For that reason, I bought a USB hub with switches. Flipping the port’s switch off and then back on after shutting down THEC64 forces the WC to go back into wireless mode without unplugging or restarting it.
As an added bonus, the hub is powered and keeps the WC on 24-7 — provided that you change the “Power Save Timer” in the WC mobile app to “Never.” THEC64 did not recognize the WC when it was connected to the hub except when a power adapter was connected; THEC64 had no problem recognizing the stick when it was plugged in directly.
WIRELESS CHANNEL
There is an option in the WC’s web interface to change the wireless channel of its built in AP. Strangely, this option isn’t present in the mobile app.
I noticed that by default the channel was identical to my network’s AP, which is obviously not great.
However, when I changed the channel, the WC started dropping off my network. I suspect that it’s incapable of functioning on two separate channels (i.e., one for its own AP and another for the AP it connects to).
If you change the wireless channel you will need to delete your access point from the WC and add it again.
BACKGROUND
The Sandisk Wireless Connect (WC) is advertised as a USB stick that functions as an access point, which can be accessed via the manufacture’s mobile app or through a web interface. Less clear is that the device can join a previously existing network and be accessed by WebDAV, which can make managing files for THEC64 easier.
SETTING UP THE WIRELESS CONNECT
Begin by updating the WC’s firmware (charging it beforehand is probably a good idea). The firmware can be downloaded from Sandisk. In my case, the device refused to join any networks after doing so, which required me to do a hard reset (hold down the power button for 15 seconds to accomplish this).
Once you’re up to date, you’ll need to begin configuring the device. Remove it from your computer (you can leave it connected to a charger if you wish). It will appear as an open wireless network. Some options can be configured through the device’s web interface, but many things are missing (like the option to have it join a preexisting wireless network).
To access all of the options you’ll want to grab the WC’s mobile app. Once you have it, begin by changing the device’s SSID (under “Change Drive Name”) and giving it a password (“Set Password to Drive”). The same password will be used for accessing the device through WebDAV or the web interface later on.
Now, go to “Internet Connection” in the WC app and enter the details for your network. Note that the device cannot connect to 5ghz access points.
Unfortunately, there’s no way to assign an IP address manually — so you’ll need to do that through your router. Go to “About” under settings to find the WC’s MAC address and then assign it an IP address in your router’s configuration page (oftentimes you’ll find this option under DHCP settings).
After a static IP address has been set, reboot the WC. It should then grab the IP address you assigned it in the router. To verify this, go back to “About.”
[Note: If you don’t mind connecting to the WC access point on the device you intend to manage THE64 with it is not necessary to have it join your network. In that case, the WC can be accessed via 172.25.63.1.]
ACCESSING THE WIRELESS CONNECT
There are three ways to manage the WC: through the mobile app, via a web browser, or using WebDAV.
The web interface allows let you add/delete files and create folders, but lacks some of the more sophisticated options you’d find in a file manager (like the ability to open files in an editor and save them on the fly).
To access the WC by its web interface go to the following address:
http://X.X.X.X/myconnectThe username is “owner” and the password is identical to the wireless password. Replace the Xs with the WC’s actual IP address.
To access the WC using WebDAV (preferred) grab Cyberduck, which is available for both macOS and Windows. For some reason, the newest version of Cyberduck does not work properly with the WC. The following versions are confirmed to work:
If you’re adventurous, try and find the newest version that works properly — I didn’t have enough patience. The newest release will connect to the WC, but fail when transferring files.
Likewise, the WebDAV client built into Windows File Explorer doesn’t play nice with the WC. Using “Add a network location” produces an error stating that the entered folder is not valid — even though it most certainly is. On the other hand, using “Map network drive” yields some success — but only temporarily in my experience.
Finder’s built in WebDAV client in macOS can access the WC, but unfortunately only in read-only mode.
I did some rudimentary testing in Linux with Xfce in Debian 10 and had mixed (i.e., unpredictable) results. Perhaps someone can suggest a suitable Linux client or share their outcomes in other desktop environments.
[Edit: I’ve since had successful results in Linux with the cadaver command line app.]
The iOS app FileBrowser connects to the WC without issue.
CONFIGURING CYBERDUCK
The main benefit of Cyberduck over the web interface is that it allows you to edit files on the WC. For example, a .cjm file can be opened in Notepad++ or a .D64 file can be opened in DirMaster — provided that file associations are set up properly in Windows Explorer.
To configure the WC in Cyberduck create a WebDAV bookmark that specifies the server (set to the WC’s IP address) and path (set to /files under “More Options”). In addition, it’s probably a good idea to set “Transfer Files” to “Use browser connection.” That should prevent Cyberduck from opening multiple connections simultaneously, which the WC might not be able to handle.
Like when accessing the web interface, enter the username “owner” and your wireless password. Strangely, I couldn’t find the username in any of Sandisk’s official documents.
USB VS. WIRELESS MODE, POWER, AND THEC64
Wireless remains active on the WC even when it is mounted. However, access to the filesystem over wireless is disabled.
Oddly, THEC64 doesn’t unmount the WC when it’s shut off. For that reason, I bought a USB hub with switches. Flipping the port’s switch off and then back on after shutting down THEC64 forces the WC to go back into wireless mode without unplugging or restarting it.
As an added bonus, the hub is powered and keeps the WC on 24-7 — provided that you change the “Power Save Timer” in the WC mobile app to “Never.” THEC64 did not recognize the WC when it was connected to the hub except when a power adapter was connected; THEC64 had no problem recognizing the stick when it was plugged in directly.
WIRELESS CHANNEL
There is an option in the WC’s web interface to change the wireless channel of its built in AP. Strangely, this option isn’t present in the mobile app.
I noticed that by default the channel was identical to my network’s AP, which is obviously not great.
However, when I changed the channel, the WC started dropping off my network. I suspect that it’s incapable of functioning on two separate channels (i.e., one for its own AP and another for the AP it connects to).
If you change the wireless channel you will need to delete your access point from the WC and add it again.
