The coverage isn’t even, particularly in the direction I can neither see nor reach with the hot end still in the printer, but it’s wayless hassle than recalibrating the Z=0 position. The very thin layer over the brass around the nozzle will vanish immediately on the skirt surrounding the first part.
I should definitely recoat the nozzle more often, because PETG doesn’t stick to silicone nearly as well as it does to brass: a nice new coat makes the PETG burned-snot problem Just Go Away.
Being that type of guy, I’m reasonably sure I would not have bought what’s now clearly labeled as an OXO Radial Pepper Grinder for use as a salt mill:
Mary recalls we got it at Target, back when one could go places and buy things, and I vaguely recall contemplating a wall of OXO gadgets. It’s been a while and I neglected to save the packaging for future reference.
Obviously not stainless steel, but not lethal, so we’ll continue abusing it.
I was all set to add reinforcing pins and whatnot, then came to my senses and just made the whole thing a few millimeters larger:
Customer feedback indicates white blends better with the background.
I made a few minor tweaks to the original design, including slightly larger bumps to hold it against the towel bar that, regrettably, put corresponding gouges into the bar. Who knew they used such soft plastic back in the day?
Although the Dell Latitude E7250 allegedly had Bluetooth capability and the Blueman applet tried connecting to my Bluetooth headsets, the connection aways failed and nothing worked. There’s a WLAN module stuck in an M.2 socket inside the laptop providing both WiFi and Bluetooth:
A bit of searching suggested the driver wasn’t loading properly, which became obvious after I knew where to look:
dmesg | grep -i blue
… snippage …
[ 5.678610] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1572
[ 5.678851] bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0a5c-216f.hcd failed with error -2
[ 5.678853] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0a5c-216f.hcd not found
[ 10.854607] Bluetooth: RFCOMM TTY layer initialized
[ 10.854613] Bluetooth: RFCOMM socket layer initialized
[ 10.854619] Bluetooth: RFCOMM ver 1.11
Without having the proper firmware / patch loaded, the module won’t work, even though the TTY / socket layers know it’s present, which explains why Blueman did everything except actually connect to the headsets.
More searching suggested you must extract the firmware HEX file from the Windows driver. Feeding the Service Tag into the Dell support site, then feeding “Bluetooth” and “Windows 8.1, 64-bit” (preinstalled on the laptop) into the Drivers & Downloads tab gets you the relevant EXE file: Dell Wireless 1550/1560 Wi-Fi and Bluetooth Driver. It turns out to be a self-extracting ZIP file (in Windows, anyway), so unzip it all by yourself:
This produces a blizzard of HEX files in the newly created Drivers/production/Windows8.1-x64 directory. Each firmware HEX file is keyed to the USB Product Code identifying the unique USB gadget, found with lsusb:
… snippage …
Bus 002 Device 003: ID 0a5c:216f Broadcom Corp. BCM20702A0 Bluetooth
… snippage …
The DW1560 apparently has a USB RAM interface, with the specific HEX file identified in the CopyList stanza of the INF file corresponding to that USB Product Code: