6 ms·
I enjoyed this article, but perhaps not for the reasons the author hoped. This quote, "With some tweaks to my G code and use of a nozzle that is more suited for
by ChuckMcM 10y ago
I enjoyed this article, but perhaps not for the reasons the author hoped. This quote, "With some tweaks to my G code and use of a nozzle that is more suited for higher resolution prints I am confident that I could produce a part that would be very close to the quality of the Stratasys produced part." really summed it up. It sums to "I can tweak my setup and get this part to be good enough relative to the expensive machine." and that is great. What is missing is it is every friggin' part. Seriously, all of the $2,000 printers have quirks that hit based on part geometry, especially in ABS. Part too long? need to add hold down tabs to prevent warping. Too many overhangs? extra supports. Too long a tool travel? Up the hotend temperature so that the extruded material doesn't cool down to much.
You can make great parts but every machine is different, and every part you make has a slightly different requirements. "Real" manufacturing tools are all about the repeatability and setup. Pretty much any machining center can take a gcode file, look at it, and adjust itself to make the best possible rendition, or warn you if it can't do so and meet its advertised tolerances. A hobby machine you print it, you tweak the parameters, you print it again, maybe you tweak the gcode a bit, and finally you print a really nice part.
What gets you repeatability? measuring. There are so many things that you can measure and hobby machines don't. Who puts glass slides (accurate to a tenth of a micron) providing position feedback on the x, y, and z stages on a hobby machine? Nobody, the slides and readers cost $1K just by themselves. There has been some motion toward monitoring the feed of the filament to give a "stripped filament" warning, but who measures the actual flow? the temperature of the melt chamber and feed path?
I really enjoy my 3D printer, I'm printing out a damper for a meat smoker as I write this, its going to be glorious, but its also the 3rd time I've printed this particular part to tune it up. We'll see how it works on the smoker.
- baq 10y agoi haven't ever used or owned a 3d printer and this part >This quote, "With some tweaks to my G code and use of a nozzle that is more suited for higher resolution prints I am confident that I could produce a part that would be very close to the quality of the Stratasys produced part." really summed it up. It sums to "I can tweak my setup and get this part to be good enough relative to the expensive machine." and that is great. What is missing is it is every friggin' part. is sooo true regardless of discipline. /rant on sure, you can make vim/emacs/sublime or macos/linux/windows behave just like you want, but you have to do this on every box you ever touch (disclaimer: i use vim). as i get older, the more i want my tools to just work, without tweaking for hours that requires deep knowledge about the system i'm customizing, to the point of willing to pay money to get the customizing part done for me. in this case, the $200k machine most likely isn't used by a single person who knows everything about its quirks, so it's all the more important for it to work correctly without tweaking, on the first try. i wish more software was like that. /rant off
- drawnwren 10y agoThere are tools out there that address your specific complaint re: software repeatability. A combination of Ansible/Emacs/Git dot files can yield a consistent environment across machines. Howard Abrams has some great material on how he does this with Emacs (howardism.org).
- geerlingguy 10y agoWhy stop at your editor? Automate your entire workstation so every last config is identical across computers: https://github.com/geerlingguy/mac-dev-playbook https://github.com/geerlingguy/mac-dev-playbook
- paulryanrogers 10y agoBecause automation takes time. Typically more than just doing it manually every time you move boxes. And sometimes the steps take hours worth of bandwidth when sneaker-net would suffice.
- vinceguidry 10y agoI applaud the effort, but this is not the best way to save the few hours it takes me to get a new machine up and running that I have to take every year or so. What happens if your build script breaks? You have to work around it then troubleshoot the problem. Already there goes your time savings. I keep my dotfiles in a repo, that seems to be at the appropriate level of abstraction. Easy to set up, easy to add to, I can understand everything its doing, if it breaks I can localize the problem and fix it exactly where it's happening. Trying to expand the scope to include arbitrary package management? I don't think the tooling is there yet, that will make this sort of thing very painful. The dotfile convention has been brewing for decades. Trying this will inevitably force you to make compromises, and compromises defeat the whole point. The work it does is fundamentally equivalent to a package manager, and existing package managers haven't managed to get it done yet. If every Mac developer can be convinced to use a package manager, and every package manager can be scripted, (looking at you, Mac App Store) and every app with a modular architecture also either plugs into an existing system or implements its own package manager, then this becomes viable. But you still need a modular and easy-to-manage way to manage app configuration too. If you can get them all to use dotfiles, awesome. But they don't now. Right now, invariably you're reduced to a pile of hacky workarounds. Any automation will have been done at the wrong level and will break constantly. The last time I needed to set one of these up, I started to write down a checklist of things to do. I gave up after I realized that I was just pulling the checklist from memory, it already exists and writing it down wasn't going to do much good.
- jacquesm 10y agoWelcome to the wonderful world of quality control :) Making something is easy, making something with a high repeat accuracy and very low fail percentage is super hard. I learned this the hard way myself with an IO expander for the Atari ST that I designed. I needed it to drive the lathe/mill controller, the ST simply had too little IO capacity so with a bunch of decoders and latches I was able to drive a much larger number of motors and relays. The first one worked like a charm. So did the second and the third. But the fourth, we couldn't get it to work no matter what. Part variability led to some signal arriving just that much earlier causing the latches to remember data that was still stale. The reason was - in retrospect - quite simple, the design had assumed that the input to the latches had long stabilized before the latch pulse was sent. But because on the ST the latch pulse took a different route as well there could occur a tricky situation where the output of the buffer driving the data bus on the far side would still be rising. To make things worse, this would not happen repeatably, only with certain patterns of 1's and 0's. In the end, a single buffer in line with the latch pulse caused enough delay to stabilize the input to the latches and that solved the problem. (Of course not with every board...). Anyway, that was electronics, this is mechanics but the same principles apply. Something funny is happening in youtube land, classical music. There are a whole pile of 'youtube wonders' that can play an enormous variety of material but that have never in their lives done a live concert. It took a long time before one of those miracle people owed up to the recipe: record hundreds, or even thousands of times. Pick the best. That's the difference between an actual pianist and youtube miracle workers: a pianist can do what they do repeatably, youtube miracle workers would end up being booed out of actual performances. Repeat accuracy is very hard, mechanics, electronics, playing the piano, the subject hardly matters. I've been reading all kinds of books and articles about quality control last year and I believe that in a mature market it is the only absolutely critical element in any production process. If all your competitors are doing good QC and you don't you're dead. Everything else can be fixed but without repeat accuracy you'll be fighting a lost battle. Another way to look at this is that for real world stuff where there is a whole company dependent on the output of the 3D printer the cheap one is too expensive, and the expensive one probably is cheap. That's because if you were allowed to make a million parts with each and you could take the best part from each set of parts they'd be very close. The 'best' part of those two might even be from the crappy machine. But if you needed just 50000 parts that would simply work your cheap printer (or even a small army of them) would wear out long before completing the order, and that's what makes them expensive.
- pipio21 10y agoAs the article says, if you want precision and repeatability, you don't use a FDM in the first place, you will mechanize the piece. As an engineer I use my FDM machines in order to detect "bugs" in my design, easily and cheaply. I don't need to cut a block of aluminum that volumetrically encloses the piece I want, unless I am certain the design is perfect. The great advantage of FDM is the ability to print with support material anything, not just 2.5 D designs like normal milling. 5D milling is way more expensive and complex. tenths of a micron in FDM? You are lucky if you get real 5 micron accuracy in a FDM printer. I print most of my designs 2x or 3x oversized to really understand the prototypes. In the end I will use SLA machines lost wax and machining to finish the process.
- 8note 10y agothe tenths of a micron are such that you can get the micron measurements from the glass and thus the 5 micron prints
- ahoka 10y ago"It sums to "I can tweak my setup and get this part to be good enough relative to the expensive machine." and that is great. What is missing is it is every friggin' part. Seriously, all of the $2,000 printers have quirks that hit based on part geometry, especially in ABS. Part too long? need to add hold down tabs to prevent warping. Too many overhangs? extra supports. Too long a tool travel? Up the hotend temperature so that the extruded material doesn't cool down to much." This is called 'mechanical engineering'. :-)
- rfrey 10y agoNo, this is like the crusty machinist who knows just how to wiggle his hips and shake his elbow to get a 1/2 thou on the worn-out bridgeport in the corner. FDM should let engineers make prototypes without bothering that guy (whose time is probably 3x more valuable than theirs, even if his pay doesn't reflect it). This sounds like the printer is just a more compact version of the worn-out mill. Plus you have to account for the printer's quirks right in your 3d model which is annoying and error-prone. (Yes, I know every package has a way to segregate those changes, etc. but still.)
- TD-Linux 10y agoThe RepRap project and the derived printers tend to share the opposite philosophy - the original idea was to print parts for more printers, so naturally parts were designed to be 3D printed. The RepRap logo is a compromise design for part holes without support (no longer necessary, though). Most RepRap owners ('hobbyists') are using the 3D printer as the end manufacturing method, not just for prototypes, so this is a pretty reasonable tradeoff. Note that the original article fell into this category - the 3D printed part was not a prototype, but a jig used in production. (looking at that part, it could have been designed to not require any support material at all)
- justinclift 10y ago> Nobody, the slides and readers cost $1K just by themselves. Yeah, I was looking at the components recently for a self-build CNC machine. Accuracy costs. eg: http://www.mitutoyo.co.uk/digital-scale-and-dro-systems/linear-scales http://www.mitutoyo.co.uk/digital-scale-and-dro-systems/line... Though in smaller sizes, the cost isn't completely over the top. Pity I'm not after "smaller sizes". :/