3D Printing a battery box holder for a mason jar style firefly light

We put together some firefly light jars for some accent lighting.  The light is an LED string dropped into a jar powered by an AA battery pack.  We originally just dropped the whole package into the mason jar. Using them without a cover was kind of cumbersome because you had to reach your hand into the jar every time you wanted to turn them off.  

I found a plan on Thingverse and adapted it to better fit our needs and battery pack.  The design attached the jar like any of the two-part lids.  We just drop the lid part and retain the threaded attachments.

The Plans - The Video and All That

In Use - On the Jar

Drop the string of lights into the jar.  Slide the battery pack into the slot at the top. Push the wire into the slot on the side of the lid.  Insert the mount with the batter pack into the jar. Screw it down with a canning lid


It might look a little better printed with a clear filament inside the jar.  The black works fine though.

Prototyping different sizes

The battery packs slide into the top in the same way on all three versions. 

The original design is the one on the right in all three pictures.  I had problems with it because of the wide tolerances for the opening on the ball jars.  It wouldn't insert all the way in most of my jars.

The second design is on the left.  It is the same height as the original but the wide section extends as far down as the end of the mouth. This seemed to avoid the tight-neck bottle problems.  

After creating the second design I realized that my battery pack slid too far down into the unit essentially blocking the switch in the off position on the lip.

The third design is in the middle. It is 20mm (or is it 30mm) shorter than the other two.  This lets the switch still be accessible while the battery pack sits on the bottom of the plug.


These pictures show the sizing problem with the IKEA battery pack being too short for the original design.



Revision History

Created 2023 03





Comments

Post a Comment

Popular posts from this blog

Understanding your WSL2 RAM and swap - Changing the default 50%-25%

Image
The Windows Subsystem for Linux operates as a virtual machine that can dynamically grow the amount of RAM to a maximum set at startup time.  Microsoft sets a default maximum RAM available to 50% of the physical memory and a swap-space that is 1/4 of the maximum WSL RAM.  You can scale those numbers up or down to allocate more or less RAM to the Linux instance. The first drawing shows the default WSL memory and swap space sizing. The images below show a developer machine that is running a dev environment in WSL2 and Docker Desktop.  Docker Desktop has two of its own WSL modules that need to be accounted for.  You can see that the memory would actually be oversubscribed, 3 x 50% if every VM used its maximum memory.  The actual amount of memory used is significantly smaller allowing every piece to fit. Click to Enlarge The second drawing shows the memory allocation on my 64GB laptop. WSL Linux defaults to a maximum RAM size of 5
Read more

Installing the RNDIS driver on Windows 11 to use USB Raspberry Pi as network attached

Image
I do a lot of my development and configuration via ssh into my Raspberry Pi Zero over the RNDIS connection. Some models of the Raspberry PIs can be configured with  gadget drivers  that let the Raspberry pi emulate different devices when plugged into computers via USB. My favorite gadget  is the network profile that makes a Raspberry Pi look like an RNDIS-attached network device.  All types of network services travel over an RNDIS device without knowing it is a USB hardware connection. A Raspberry Pi shows up as a Remote NDIS (RNDIS) device when you plug the Pi into a PC or Mac via a USB cable. The gadget  in the Windows Device Manager picture shows this RNDIS Gadget connectivity between a Windows machine and a Raspberry Pi. The Problem Windows 11 and Windows 10 no longer auto-installs the RNDIS driver that makes magic happen. Windows recognizes that the Raspberry Pi is some type of generic USB COM device. Manually running W indows Update  or  Update Driver  does  not  install the RNDI
Read more

DNS for Azure Point to Site (P2S) VPN - getting the internal IPs

Image
I wanted to access all my Azure resources without making any of them visible to the Internet.   The easiest give my local machine access to everything on my Azure Virtual Network (VNET) was to connect to it over VPN. It turns out creating Azure VPN gateways and connecting to Azure VPN endpoints is easy.  There are some subtleties in getting DNS name resolution to work that can confuse when first starting out. Setting the Stage There are a few ways to get to Azure endpoints and resources that are blocked from the internet.  We can  Create a Point-to-Site connection from our local machines to Azure Network Gateways Create a Site-to-Site network connection from our local networks to Azure Network Gateways. Use Bastion Hosts Use Cloud Shell Leave everything open to the internet. I chose a Point-to-Site (P2S) VPN connection that connects from my laptop to a VNet Gateway.  That joins my laptop
Read more