The Smell of Molten Projects in the Morning

Ed Nisley's Blog: Shop notes, electronics, firmware, machinery, 3D printing, laser cuttery, and curiosities. Contents: 100% human thinking, 0% AI slop.

Tag: Improvements

Making the world a better place, one piece at a time

  • Seedling Starter Pot Bottoms

    Seedling Starter Pot Bottoms

    One of Mary’s gardening compadres teaches a kid’s class which involves starting seedlings in “pots” made from the cardboard tubes found in paper towels and toilet paper. Cutting four slits in the bottom of the tube and folding the flaps inward puts a bottom on the pot, but what’s the fun in that?

    Draw a 42 mm circle, set the layer to cut corrugated cardboard, turn the circle into suitable arrays, flatten some boxes from the heap, and Fire the Laser:

    Seedling starter pot bottoms
    Seedling starter pot bottoms

    Collect the fallen disks from the chip tray and jam one in place as a serving suggestion, where it fits like it was custom-made:

    TP roll seedling starter pot bottom
    TP roll seedling starter pot bottom

    You’d still want to fold some flaps over the disk to keep it in place, but now your pot has a real bottom.

    I have no idea if 42 mm is a Galactic Constant, but it worked for the pile of tubes we had on hand.

    That was easy …

  • Danger Zone Earrings: MVP

    Danger Zone Earrings: MVP

    Some geometry review and a bit of fiddling with LightBurn produced regularized patterns suitable for laser cuttery:

    Danger Zone Earrings - radioactive - handful
    Danger Zone Earrings – radioactive – handful

    A key trick: circumscribe the figure with a circle on a tool layer, then group the whole mess together, so that the center of the circle coincides with the desired center of the figure. In particular, the geometric center of an equilateral triangle is not at the center of its vertical extent:

    Danger Zone Earrings - radioactive - LB layout
    Danger Zone Earrings – radioactive – LB layout

    The dark blue layer engraves the surface, the red layer cuts through 3 mm acrylic, and the light blue layer is the tooling.

    I like the edge-lit ones, although the simplicity of laser-cut clear acrylic is hard to beat:

    Danger Zone Earrings - radioactive - white light
    Danger Zone Earrings – radioactive – white light

    Wearing them in a place flooded with UV radiation would set you apart:

    Danger Zone Earrings - radioactive - GITD UV
    Danger Zone Earrings – radioactive – GITD UV

    The careful observer will note stress cracking in the two clear earrings in the middle row. Those came from the vintage paper-covered acrylic sheet and I used alcohol to clean off the not-quite-vaporized glue just to see if isopropyl alcohol would behave differently than denatured alcohol. Nope, the cracks appear instantly.

    Peeling the paper and engraving the bare surface produced the clear-frosted earring in the upper right, with the radiation symbol cut out of the sheet. Engraving without surface protection tends to deposit vaporized acrylic dust everywhere, so it would require hand cleaning without the cutouts.

    The cutouts get 0.1 mm inward offsets to slightly increase the wall thickness around that central circle.

    One combination I didn’t try: engrave the triangle perimeter for emphasis and cut out the symbol for contrast with edge-lit acrylic.

    Dropping other symbols into place should be straightforward, with the center of the circumcircle as the snap target.

    The LightBurn SVG layout as a GitHub Gist:

    Loading
    Sorry, something went wrong. Reload?
    Sorry, we cannot display this file.
    Sorry, this file is invalid so it cannot be displayed.
  • Copying Action Camera Video Files: Now With Arrays

    Copying Action Camera Video Files: Now With Arrays

    Using Bash arrays is an exercise in masochism, but I got to recycle most of the oddities from the previous script, so it wasn’t a dead loss.

    The cameras use individually unique / screwy / different filesystem layouts, so the script must have individual code to both copy the file and decapitalize the file extensions. This prevents using a single tidy function, although laying out the code in case statements keyed by the camera name helps identify what’s going on.

    My previous approach identified the MicroSD cards by their UUIDs, which worked perfectly right up until the camera reformats the card while recovering from a filesystem crash and installs a randomly generated UUID. Because there’s no practical way to modify an existing UUID on a VFAT drive, I’m switching to the volume label as needed:

    #-- action cameras and USB video storage
    UUID=B40C6DD40C6D9262	/mnt/video	ntfs	user,noauto,uid=ed	0	0
    UUID=B257-AE02		/mnt/Fly6	vfat	user,noauto,uid=ed	0	0
    #UUID=0000-0001		/mnt/M20	vfat	user,noauto,uid=ed	0	0
    UUID=3339-3338		/mnt/M20	vfat	user,noauto,uid=ed	0	0
    LABEL=AS30V		/mnt/AS30V	exfat	user,noauto,uid=ed	0	0
    LABEL=C100-0001		/mnt/C100_1	vfat	user,noauto,uid=ed	0	0
    LABEL=C100-0002		/mnt/C100_2	vfat	user,noauto,uid=ed	0	0
    UUID=0050-0001		/mnt/M50	vfat	user,noauto,uid=ed	0	0
    

    In particular, note the two UUIDs for the M20 camera: there’s a crash and reformat in between those two lines. The two C100 cameras started out with labels because the M20 taught me the error of my ways.

    The script simply iterates through a list array of the cameras and tries to mount the corresponding MicroSD card for each one: the mount points are cleverly chosen to match the camera names in the array. Should the mount succeeds, an asynchronous rsync then slurps the files onto the bulk video drive.

    With all the rsync operations running, the script waits for all of them to complete before continuing. I don’t see much point in trying to identify which rsync just finished and fix up its files while the others continue to run, so the script simply stalls in a loop until everything is finished.

    All in all, the script scratches my itch and, if naught else, can serve as a Bad Example™ of how to get the job done.

    A picture to keep WordPress from reminding me that readers respond positively to illustrated posts:

    A pleasant day for a ride - 2023-06-01
    A pleasant day for a ride – 2023-06-01

    Ride on!

    The Bash script as a GitHub Gist:

    #!/bin/bash
    # This uses too many bashisms for dash
    source /etc/os-release
    echo 'Running on' $PRETTY_NAME
    if [[ "$PRETTY_NAME" == *Manjaro* ]] ; then
    ren='perl-rename'
    dm='sudo dmesg'
    elif [[ "$PRETTY_NAME" == *Ubuntu* ]] ; then
    ren='rename'
    dm='dmesg'
    else
    echo 'New distro to me:' $PRETTY_NAME
    echo ' … which rename command is valid?'
    exit
    fi
    echo Check for good SD card spin-up
    $dm | tail -50
    echo … Ctrl-C to bail out and fix / Enter to proceed
    read junk
    thisdate=$(date –rfc-3339=date)
    echo Date: $thisdate
    # MicroSD / readers / USB drive defined in fstab
    # … with UUID or PARTID as appropriate
    echo Mounting bulk video drive
    sudo mount /mnt/video
    if [ $? -ne 0 ]; then
    echo '** Cannot mount video storage drive'
    exit
    fi
    # Show starting space available
    df -h /mnt/video
    # list the cameras
    declare -a cams=( AS30V Fly6 M20 M50 C100_1 C100_2 )
    declare -A targets=( \
    [AS30V]=/mnt/video/AS30V/$thisdate \
    [Fly6]=/mnt/video/Fly6/DCIM \
    [M20]=/mnt/video/M20/$thisdate \
    [M50]=/mnt/video/M50/$thisdate \
    [C100_1]=/mnt/video/C100_1/$thisdate \
    [C100_2]=/mnt/video/C100_2/$thisdate \
    )
    declare -A PIDs
    declare -A Copied
    echo Iterating through cameras: ${cams[*]}
    Running=0
    for cam in ${cams[*]} ; do
    printf "\nProcessing: $cam\n"
    mpt="/mnt/$cam"
    target=${targets[$cam]}
    sudo mount $mpt
    if [ $? -eq 0 ]; then
    echo " Start $cam transfer from $mpt"
    echo " Make target directory: $target"
    mkdir $target
    case $cam in
    ( AS30V )
    rsync -ahu –progress –exclude "*THM" $mpt/MP_ROOT/100ANV01/ $target &
    ;;
    ( Fly6 )
    rsync -ahu –progress $mpt /mnt/video &
    ;;
    ( M20 )
    n=$( ls $mpt/DCIM/Photo/* 2> /dev/null | wc -l )
    if [ $n -gt 0 ] ; then
    echo " copy M20 photos first"
    rsync -ahu –progress $mpt/DCIM/Photo/ $target
    fi
    echo " cmd: rsync -ahu –progress $mpt/DCIM/Movie/ $target"
    rsync -ahu –progress $mpt/DCIM/Movie/ $target &
    ;;
    ( M50 )
    n=$( ls $mpt/DCIM/PHOTO/* 2> /dev/null | wc -l )
    if [ $n -gt 0 ] ; then
    echo " copy M50 photos first"
    rsync -ahu –progress $mpt/DCIM/PHOTO/ $target
    fi
    rsync -ahu –progress $mpt/DCIM/MOVIE/ $target &
    ;;
    ( C100_1 | C100_2 )
    n=$( ls $mpt/DCIM/Photo/* 2> /dev/null | wc -l )
    if [ $n -gt 0 ] ; then
    echo " copy $cam photos first"
    rsync -ahu –progress $mpt/DCIM/Photo/ $target
    fi
    rsync -ahu –progress $mpt/DCIM/Movie/ $target &
    ;;
    ( * )
    printf "\n**** Did not find $cam in list!\n"
    ;;
    esac
    PIDs[$cam]=$!
    echo " PID for $cam: " "${PIDs[$cam]}"
    Copied[$cam]=1
    (( Running++ ))
    else
    echo " skipping $cam"
    Copied[$cam]=0
    fi
    done
    printf "\n—– Waiting for all rsync terminations\n"
    echo PIDs: "${PIDs[*]}"
    if [ $Running -eq 0 ] ; then
    echo No rsyncs started, force error
    rcsum=9999
    else
    rcsum=0
    while [ $Running -gt 0 ] ; do
    echo " waiting: $Running"
    wait -n -p PID
    rc=$?
    rcsum=$(( rcsum+$rc ))
    echo RC for $PID: $rc
    (( Running– ))
    done
    echo All rsyncs finished
    fi
    if [ $rcsum -eq 0 ] ; then
    echo '—– Final cleanups'
    for cam in ${cams[*]} ; do
    if [ "${Copied[$cam]}" -eq 1 ] ; then
    echo Cleanup for: $cam
    mpt=/mnt/$cam
    target=${targets[$cam]}
    echo Target dir: $target
    case $cam in
    ( Fly6 )
    find $target -name \*AVI -print0 | xargs -0 $ren -v -f 's/AVI/avi/'
    rm -rf $mpt/DCIM/*
    ;;
    ( AS30V )
    find $target -name \*MP4 -print0 | xargs -0 $ren -v -f 's/MP4/mp4/'
    rm $mpt/MP_ROOT/100ANV01/*
    ;;
    ( M50 )
    find $target -name \*MP4 -print0 | xargs -0 $ren -v -f 's/MP4/mp4/'
    rm $mpt/DCIM/MOVIE/*
    n=$( ls $mpt/DCIM/PHOTO/* 2> /dev/null | wc -l )
    if [ $n -gt 0 ] ; then
    echo placeholder $cam
    rm $mpt/DCIM/PHOTO/*
    fi
    ;;
    ( * )
    find $target -name \*MP4 -print0 | xargs -0 $ren -v -f 's/MP4/mp4/'
    find $target -name \*JPG -print0 | xargs -0 $ren -v -f 's/JPG/jpg/'
    rm $mpt/DCIM/Movie/*
    n=$( ls $mpt/DCIM/Photo/* 2> /dev/null | wc -l )
    if [ $n -gt 0 ] ; then
    echo placeholder $cam
    rm $mpt/DCIM/Photo/*
    fi
    ;;
    esac
    sudo umount $mpt
    else
    echo No cleanup for: $cam
    fi
    done
    echo '—– Space remaining on video drive'
    df -h /mnt/video
    sudo umount /mnt/video
    date
    echo Done!
    else
    echo Whoopsie! Total RC: $rcsum
    fi
  • Tour Easy: Another SJCAM C100+ Mount

    Tour Easy: Another SJCAM C100+ Mount

    Eight years of progress in the action camera world gets you from a rather expensive Cycliq Fly6:

    Tour Easy - Fly6 image
    Tour Easy – Fly6 image

    To an SJCAM C100+ camera costing the better part of fifty bucks on closeout:

    Tour Easy - C100 image
    Tour Easy – C100 image

    The camera is mounted on the side of the seat frame on Mary’s Tour Easy:

    Tour Easy C100 mount - side rail
    Tour Easy C100 mount – side rail

    The slightly tilted picture comes from the frame rail’s incline. My C100+ camera mounts on the horizontal part of the rail:

    Tour Easy C100 mount - rear rail
    Tour Easy C100 mount – rear rail

    As expected, the internal battery does not last for our usual hour-long rides, so the cameras now operate in “car mode”: recording starts when we plug in the USB battery pack and stops shortly after unplugging.

    I started with the waterproof case on my bike:

    Tour Easy - SJCAM C100 mount - installed
    Tour Easy – SJCAM C100 mount – installed

    Which (obviously) does not allow for an external battery, so they’re now in the “frame” mount. The hatch covering the MicroSD card and USB Micro-B connector (and a Reset button!) is on the bottom of the camera, but (fortunately) the whole affair mounts up-side-down and the settings include an image flip mode.

    Putting the camera on the side required changing the mount angle from -20° to +35°:

    SJCAM C100 Mount - 35 degree solid model
    SJCAM C100 Mount – 35 degree solid model

    The ergonomics / user interface of this whole setup is terrible:

    • The camera’s flexible hatch is recessed inside the frame far enough that it cannot be opened without using a small & sharp screwdriver
    • The USB jack is slightly off-center, so lining the plug up with the camera body doesn’t align it with the jack
    • The MicroSD card is in a push-to-release socket, but its raised ridge faces the hatch flap and cannot be reached by a fingernail. I added a small tab that helps, but it’s difficult to grasp.

    Extracting the video files from the camera through the app is an exercise in frustration. Having already figured out how to do this for the other cameras in the fleet, it’s easier to fumble with the MicroSD card.

    I devoutly hope we never really need any of the videos.

  • HW Bucked Lithium AA Cells

    HW Bucked Lithium AA Cells

    The trail camera uses two parallel banks of four series AA cells to get enough oomph for its IR floodlight. I’m not convinced using bucked lithium AA cells in that configuration is a Good Idea, but it’s worth investigating.

    These are labeled HW, rather than Fuvaly, because it seems one cannot swim twice in the same river:

    HW bucked Li AA cells
    HW bucked Li AA cells

    In any event, they come close to their claimed 2.8 W·hr capacity:

    HW bucked Li AA - 2023-05
    HW bucked Li AA – 2023-05

    The lower pair of traces (red & black) are single cells at 2.7-ish W·hr, the blue trace is a pair at 5.4 W·hr, and the green trace is a quartet at 9.8 W·hr. Surprisingly close, given some previous results in this field.

    Recharging the cells after those tests shows they all take 3 hours ± a few minutes to soak up 730 mA·hr ± a few mA·hr, so they’re decently matched.

    Measuring the terminal voltage with a 10 mA load after that charge lets me match a pair of quartets to 1 mV, which is obviously absurd:

    HW bucked Li cells - initial charge 2023-05-05
    HW bucked Li cells – initial charge 2023-05-05

    The numbers in the upper left corner show the initial charge of four cells at a time required the same time within a minute and the same energy within 4%.

    Sticking them in the trail camera must await using up the current set of alkaline AA cells.

    Bonus: a lithium fire in a trail camera won’t burn down the house.

    After all, pictures like this are definitely worth the hassle:

    Young Buck in velvet - 2023-05-03
    Young Buck in velvet – 2023-05-03

    Looks like a pair of WiFi antennas …

  • Bafang vs. Tour Easy: Chain Guide

    Bafang vs. Tour Easy: Chain Guide

    After adding the Bafang motor to my Tour Easy, the chain has fallen off the chainring a few times, prompting the gap filler between the motor and the chainring spider. That this has never happened to Mary’s essentially identical Tour Easy suggests I have a different shift technique, but adding a chain catcher seemed easier than re-learning shifting:

    Chain Catcher - top view
    Chain Catcher – top view

    It’s more properly called a “chain guide” and is basically a shifter cage minus the mechanism:

    Chain Catcher - side view
    Chain Catcher – side view

    Because the Tour Easy frame has a 25 mm tube where the guide’s clamp expects a minimum 31.8 mm tube, a 3D printed adapter fills the gap:

    Chain Catcher adapter ring - solid model
    Chain Catcher adapter ring – solid model

    The hole is off-center because it seemed like a good idea, although it’s not strictly necessary. The flange helps align the pieces while tightening the clamp screw.

    The guide cage clears the chain on all sides while up on the work stand, but there’s nothing like getting out on the road to find out why something doesn’t work as you expect.

    The OpenSCAD source code as a GitHub Gist:

    // Chain catcher adapter ring
    // Ed Nisley – KE4ZNU – 2023-05
    /* [Hidden] */
    ThreadThick = 0.25;
    ThreadWidth = 0.40;
    HoleWindage = 0.2;
    Protrusion = 0.1; // make holes end cleanly
    function IntegerMultiple(Size,Unit) = Unit * ceil(Size / Unit);
    ID = 0;
    OD = 1;
    LENGTH = 2;
    inch = 25.4;
    //———————-
    // Dimensions
    TubeOD = 26.0; // frame tube with silicone tape
    Clamp = [35.0,39.0,12.0]; // Chain catcher clamp ring
    Flange = [Clamp[ID],Clamp[OD],3*ThreadThick];
    Kerf = 1.0;
    Offset = (Clamp[ID] – TubeOD)/2 – 3*ThreadWidth;
    NumSides = 2*3*4;
    //———————–
    $fn=NumSides;
    difference() {
    union() {
    cylinder(d=Flange[OD],h=Flange[LENGTH]);
    cylinder(d=Clamp[ID],h=Clamp[LENGTH]+Flange[LENGTH]);
    }
    cube([2*Flange[OD],Kerf,3*Clamp[LENGTH]],center=true);
    translate([0,Offset,0])
    cylinder(d=TubeOD,h=3*Clamp[LENGTH],center=true);
    }
  • Bafang Motor: Chain Gap Filler

    Bafang Motor: Chain Gap Filler

    When the chain falls off the top of the chainring toward the motor, the part remaining engaged with the chainring will inevitably drag the rest into the gap between the motor and the chainring spider, whereupon it will jam firmly in place and be almost impossible to extract. Preventing this means filling the gap, which required several iterations:

    Bafang motor gap filler - prototypes
    Bafang motor gap filler – prototypes

    The Bafang motor has a cover held in place by seven M3 flat-head screws, shown here below a test filler using pan head screws:

    Bafang motor gap filler - installed
    Bafang motor gap filler – installed

    Contrary to what you might think, the five screws that obviously sit on five points of a hexagon do not in fact sit 60° apart. How you find this out is by making the obvious layout, including the two screws bracketing the pinion gear in the lower right, then applying windage:

    Bafang motor housing gap filler - hole adjustments
    Bafang motor housing gap filler – hole adjustments

    That’s one of the paper templates seen above, with laser-cut holes 60° apart and ugly holes punched at the actual screw locations. Then you scan and overlay that image with the LightBurn layout and twiddle the hole locations to make the answer come out right:

    Bafang motor housing gap filler - hole adjustments - LB overlay
    Bafang motor housing gap filler – hole adjustments – LB overlay

    With that in hand, I cut a 1 mm acrylic shape to measure the clearance between the motor + filler and the chainring spider, with pan-head screws replacing the original flat-head screws:

    Bafang motor gap filler - top view
    Bafang motor gap filler – top view

    That’s a single piece of 2.5 mm acrylic I used after discovering a pair of the 1 mm acrylic shapes fit with space to spare: hooray for rapid prototyping.

    A test chain drop suggested it might suffice:

    Bafang motor gap filler - test
    Bafang motor gap filler – test

    If I were so inclined, 3 mm acrylic with countersunk holes and slightly longer flat-head screws would probably work, but I’ll use this until it fails to prevent a chain snag.

    The careful observer will have noted the stress crack extending radially inward from the upper-right screw, which I am carefully avoiding doing anything about, pending the aforementioned failure.

    The LightBurn layout as a GitHub Gist:

    Loading
    Sorry, something went wrong. Reload?
    Sorry, we cannot display this file.
    Sorry, this file is invalid so it cannot be displayed.