They’re recognizably robins now, covered in young-bird speckle camouflage.
Feeding continued apace:
After feeding, robin nestlings produce fecal sacs, which the parents either eat or carry away:
Robins aren’t big on facial expressions, but, speaking from personal experience, anything to do with diapers isn’t the high point of a parent’s day.
And then there were none:
The gazillion black dots on the soffit are pinpoint-sized insects / mites / ticks infesting the nest and, presumably, the birds. The earlier pictures don’t show them, so perhaps these missed the last bird off the nest and are now regretting their life choices.
A bit of continuity testing shows the green and white data wires are also reversed, so whoever assembled the cable simply soldered the proper wire color sequence backwards onto both connectors. As long as you don’t cut the cable to reuse the connectors, it’s all good.
The strip mall down the road recently sprouted ersatz stone pillars around the steel posts holding up the roof:
Six days later, more slabs have fallen off the first pillar in the row:
And the second pillar:
Those fancy(-ish) bases consist of a wood frame covered with a mortar layer holding tiles of imitation stonework. From what little I know of stonework, mortar works only in compression, so you can’t glue tiles onto the side of a concrete lump using mortar.
I’ve been putting this type of support structure inside screw holes & suchlike for years:
It’s basically a group of small rectangles rotated around the hole’s axis and about one thread thickness shorter than the overhanging interior.
I’ve found that incorporating exactly the right support structure eliminates Slic3r’s weird growths, eases removal, and generally works better all around.
So doing this for the baseplate of the Glass Tile frame came naturally:
This OpenSCAD snippet plunks one of those asterisks in each of four screw holes:
for (i=[-1,1], j=[-1,1])
translate([0,0,(Screw[LENGTH] - ThreadThick)/2])
cube([Screw[OD] - 2*ThreadWidth,2*ThreadWidth,Screw[LENGTH] - ThreadThick],center=true);
The “cubes” overlap in the middle, with no completely coincident faces or common edges, so it’s 2-manifold. Slic3r, however, produces a weird time estimate whenever the model includes those structures:
NaN stands for Not A Number and means something horrible has happened in the G-Code generation. Fortunately, the G-Code worked perfectly and produced the desired result, but I’m always uneasy when Something Seems Wrong.
Messing around with the code produced a slightly different support structure:
The one thread thick square on the bottom helps glue the structure to the platform and four ribs work just as well as eight in the octagonal hole:
Fin = [Screw[OD]/2 - 1.5*ThreadWidth,2*ThreadWidth,ScrewRecess - ThreadThick];
if (Inserts && SupportInserts)
for (i=[-1,1], j=[-1,1])
translate([Fin.x/2 + ThreadWidth/2,0,(ScrewRecess - ThreadThick)/2])
Which changed the NaN time estimates into actual numbers.
One key difference may be the small hole in the middle. The four ribs (not two!) now overlap by one thread width around the hole, so they’re not quite coincident and Slic3r produces a tidy model:
The hole eliminates a smear of infill from the center, which may have something to do with the improvement.
In any event, I have an improved copypasta recipe for the next screw holes in need of support, even if I don’t understand why it’s better.
She’s surprisingly tolerant of our comings and goings, as well as garage door openings and closings:
We’re trying to stay out of her way as much as possible.
The gallery pix come from my phone, held against the soffit over the nest, and aimed entirely by feel, while standing on the Greater Ladder. If I had access to the top of the soffit, I’d drill a webcam hole, but …