I had my ScanSnap ix500 – on which I wrote before – connected to a WiFi network that supported 2.4GHz and 5GHz.
Since there is too much trouble on the 2.4GHz band (too many access points around me running at too much power, and having even more trouble around meal times, so likely one or more badly shielded Microwave devices in the neighbourhood) I turned it off in my WiFi access points.
Now I have a separate access point indicating it is 2.4Ghz, so I had to use the Wireless Configuration Tool (which requires a USB connection to the ix500) to reconfigure it.
When one of the machine isn’t active for a while it seems to disappear. Even when it’s active some of the machines have intermittent errors pinging it as like every 10-30 seconds one of these ping results appear:
92 bytes from tl-er5120 (192.168.71.1): Redirect Host(New addr: 192.168.71.193)
Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 00 0054 05de 0 0000 40 01 644d 192.168.71.108 192.168.71.193
At the recent Embedded Linux Conference and OpenIoT Summit, Mozilla Technical Evangelist Dietrich Ayala proposed a simple and affordable solution to home automation: A discarded smartphone can handle some of the most useful home automation tasks without requiring expensive hubs and sensors — or risking data security in the cloud.
It’s in my main virtualisation workhorse, uses little power, has loads of disk (SAS/SATA) ports, IPMI, two network connections and enough slots for memory and I/O to be extensible.
I use it for most of my software development even when on the road: VPN home over one of the fiber connections and it screams.
Some links, as SuperMicro tends to hide them behind POST requests:
That moment you facepalm yourself because you forgot that particular machine won’t read SD cards because they are too big for the SD card reader in it: SD goes up to 4 gigabyte, anything bigger (nowadays basically everything) requires SDXC or SDHC compatible readers.
However, older host devices do not recognize SDHC or SDXC memory cards, although some devices can do so through a firmware upgrade.[11] Older Windows operating systems released before Windows 7 require patches or service packs to support access to SDHC cards.[12][13][14]
Older host devices generally do not support newer card formats, and even when they might support the bus interface used by the card,[6]there are several factors that arise:
A newer card may offer greater capacity than the host device can handle (over 4 GB for SDHC, over 32 GB for SDXC).
A newer card may use a file system the host device cannot navigate (FAT32 for SDHC, exFAT for SDXC)
Use of an SDIO card requires the host device be designed for the input/output functions the card provides.
The hardware interface of the card was changed starting with the version 2.0 (new high-speed bus clocks, redefinition of storage capacity bits) and SDHC family (Ultra-high speed (UHS) bus)
UHS-II has physically more pins but is backwards compatible to UHS-I and non-UHS for both slot and card.[27]
Some vendors produced SDSC cards above 1GB before the SDA had standardized a method of doing so.