3D printing for prototyping part 2: embracing failure

In part 1, I set up the Anycubic Mono and printed out the demo model which went OK. Not perfect, but good enough as a learning experience. Now I want to move on to reproducing the existing SmartShepherd parts before modifying them.

Step one: Turn a step file into something the Anycubic understands

The overall process sounds simple enough: take your CAD file (generally a STEP file), export that as an STL file (which describes the surface of your model), import that into a slicer, get the slicer to generate a file tailored for your 3D printer.

The original CAD models were built with SolidWorks, a fabulous bit of software that has a jaw-dropping pricetag. There are alternatives but all of them seem to suck. FreeCAD sounds great, but I can't get it to reliably select parts of my model without crashing. Varicad ($910USD per year with a 30 day trial period) seems much easier to use and respects the part grouping that was originally created in SolidWorks, unlike FreeCAD. Varicad is a lot more stable and runs fine on Debian or Windows (or a mac I guess). However, I stuck with FreeCAD for this simple job. The file produced is an "STL" file, you turn the objects of your STEP model into a surface area model suitable for printing (or machining for that matter).

FreeCAD showing the base part of the SmartShepherd pod, ready to be exported as an STL file.

Anycubic provide slicer software, but it doesn't run on Linux. I'm probably making my life more difficult at this point and should just suck it up and buy a Macintosh, but nobody is that desperate. There are good slicers available for Linux and I chose Lychee Slicer. At this point I'm going to embarrass myself and say that the only reason I chose Lychee Slicer is that is reminded me of an old, off colour joke about a guy who got fired for, well, something to do with the pickle slicer.

Lychee Slicer with the imported STL file, ready to slice!

With the file suitably sliced, I probably should have stopped to think how it would print, given that the Anycubic is a little fussy about how the layers get released from the exposure plate, but my impatience got the better of me at this point. The following picture shows why that was stupid.

Yikes

In this picture you can see the aftermath. The slices went pretty well and the model printed really well right up until it got to the loop where the nylon collar goes though. At that point, the end facing part of the model failed to release from the base of the resin chamber and the whole thing went to 3D printing hell. So, apparently, you can't just point the thing at your model, you have to think about it a bit, how it will release each layer, what each new layer is going to be stuck to and a whole lot of stuff that is giving me a headache, which might be from huffing 3D printer resin which I managed to spill all over the floor. Good thing we moved to a proper workshop!

Popular posts from this blog

Tailscale ate my network (and I love it)

Image
No matter where you go, there you are If you're like me, you travel occasionally. Access to your office from home, or from an airport lounge, or from a hotel room is paramount to being productive for most of us now. While I had a fairly simple Tailscale setup that got me into my test machines in the office, what I really wanted was to integrate my AWS production VPC into that system. It's surprisingly simple. Tailscale AWS instructions What do you want to do that for? In the "before tailscale" times, if I needed to test against the production AWS resources or connect dBeaver for database maintenance, I would edit the security group to add my IP address, do my testing, edit the security group to remove myself. This is as error prone as it sounds. I quite often forgot to remove my IP address from the allowed addresses, a major potential security risk when you are travelling. Tailscale has an extremely nifty way to get around it: if you run up a small ec2 ins
Read more

That magical word: Workstation

Image
Or how I came to own a HP 8760w 17" laptop I am reading a lot of retro-computing articles lately, I grew up in the 8 bit era and I have strong nostalgia for it. It does help to be realistic though, for all the love that things like the Amiga get, they were a dead end in terms of computing. What really ate the world was the boring old IBM-PC: flickery, interlaced multi-sync monitors, beige boxes and productivity software. There was another, relatively brief path the industry could have gone down though. The Workstation was king In retrospect, it might be a bit tough to put a circle around what constituted a workstation . Is a PERQ a workstation? Probably. Xerox Alto and Star? Definitely. Symbolics Lisp machines? Not sure. Probably? The real success stories came out of Apollo , Sun, HP,IBM,NeXT,DEC and Silicon Graphics. For a time it was a hot market, especially in what was known then as technical computing: research, manufacturing, CAD, graphics, simulations. If
Read more

Time machine: Solaris 2.6 on QEMU

Image
You can never go home A big chunk of my professional career in the 1990s was spent with a Sparcstation on my desk. Before that the 68000 Sun2 and Sun3 floated past my sticky fingers but the Sparc machines quickly superseded those. I don't remember too much about which ones: pretty sure there was at least one IPX, one Sparcstation 5, a Sparcstation 10 and then the last one was most likely an Ultra 1 or maybe even an Ultra 5. It was a long time ago. Every now and again I think about how productive those machines were and do a little Ebay digging on how much one would be worth to have around. Except I don't have the room for more machines and the idea of trying to revive 25 year old hardware from that era is well beyond my electronic capabilities. Never fear, QEMU is here. Following these excellent instructions from Adafruit , you too can install Solaris 2.6 and have your very own emulated machine. Note that there is one instruction in there I am not sure you need. A
Read more