kizzard

Does anyone have any tips or tools to help with managing slicer profiles using inheritance? I primarily use SuperSlicer but have been dabbling with Orca Slicer recently.

I want to make a master printer profile, then have child profiles for specific purposes (production / draft, different layer heights, etc) that only override specific settings.

SuperSlicer has profile inheritance but if you make a change to the master profile, you have to manually propagate it into every child profile which is painful and error prone.

Orca Slicer also appears to have inheritance but you don't seem to be able to choose a user profile as the parent profile (only the immutable system profiles), which makes it useless.

I am thinking about creating a makefile driven system or python script to generate the child Super Slicer INI profiles... but it kind of pains me to have to use a separate system instead of managing it from the slicer UI.

Videos:

• Short - just driving through the duct
• Long - more pictures and voiceover

I threw together this robot in a couple of days to inspect my HVAC duct and pull a cable (side note: I’m aware it’s generally advised against to run a cable through a duct, but I live in LA and we don’t have heating in our HVAC system so I don’t see it as a problem)

It's a pretty bare-bones platform, designed to be as simple as possible for a quick design + build using parts I had on-hand.

The vehicle is powered by small geared 28BYJ-48 Stepper motors driven by ULN2003 drivers, controlled with an ESP32 Cam development board. It’s a decent board for the application as it has wifi, a camera and a bright forward facing LED. The board does not have the necessary 8 GPIO pins to drive the ULN chips, so I used a 8 bit shift register.

I originally intended it to be powered by an 18650 battery but I had problems using a boost converter to get the required current to drive the electronics at 5v. the board is pretty power hungry, and coupled with the steppers and high power LED, it wouldn't even boot. I resorted to using 2 lithium polymer batteries in series to achieve 7.2v with no boost converter, which worked well enough. Even then, use of the LED kept causing brown-outs and reboots so I resorted to lowering it to 1/4 duty cycle which fixed the problem.

I used Micropython and the Picoweb framework to serve a REST API for rover control and a web page to provide a UI:

The rover was designed in FreeCAD and printed on my Voron 0 using PLA. The tires were printed in NinjaFlex TPU which is a very flexible rubber like plastic, in order to provide more traction.

The rover suffered from the aforementioned brown-outs due to the LED power requirements and also struggled to turn in certain locations in the ducts due to traction limitations and as side effect of being 2WD, but ultimately succeeded at what I needed.

Recently I've been having feelings about moving away from Fusion 360. The combination of cloud app / filesystem and their demonstrated willingness to remove features and add arbitrary limitations (eg. 10 editable model limit) makes me feel uneasy about using it. To be clear I'm grateful that AutoDesk provide a free license at all, and it's an incredible piece of software, but I have a sense of vulnerability while using and honing my skills in it. If you've ever rented a house you'll know the feeling - you quite don't feel like it's really your home, if the landlord wants to make renovate or redecorate you don't have any choice and you could be evicted at any moment.

So I tried FreeCAD. At first, I have to say that it felt a little like stepping out of a spaceship (Fusion) and banging rocks together like a caveman. It's not that you can't do (most) of the same things as an enterprise CAD package, but the killer feature of Fusion is the level of intuitiveness and "it just works" that makes FreeCAD seem like trying to write Latin.

After a week of on-and-off learning I was not sure I wanted to continue. Even after getting comfortable with the basics, frustration levels would spike to 11 sometimes. The main issue I kept running into was that altering a previous feature would break everything that came after, requiring a varying amount of work to fix. The FreeCAD wiki suggests ways to mitigate this but many of them are un-intuitive and/or inconvenient. After some googling this seems to be caused by a pretty difficult to solve issue called the "Topological Naming Problem" (where FreeCAD can't keep track of surfaces / edges / vertexes in a stable fashion when features are changed). Then I came across this blog post that pointed out a fix has actually been developed earlier this year. A developer by the name of RealThunder has created a fork of FreeCAD called "Link Branch" which can track topology in a (more) stable fashion.

I tried this branch and was blown away by how much more usable it is. Not only can it handle changes to past features almost perfectly, but I can create multiple bodies from a single sketch (not possible before) and there are other UI tweaks that make creating features easier such as the ability to preview fillets and chamfers at the same time as selecting their edges. I'm not totally sure which of these features are unique to Link branch vs which might be pre-release in the main branch, but certainly the topology naming fix is unique to Link.

So if you have tried FreeCAD in the past and been frustrated, or if Fusion's past free license changes or price increases are making you uneasy, give the Link Branch a try! Downloads are available in the releases page.