Giter VIP home page Giter VIP logo

kickstarter-autodesk-3d's Introduction

Using the Autodesk x Kickstarter FDM 3D Printer Assessment

Background and Rationale

Autodesk and Kickstarter have developed a common standard that enables people to assess the performance of FDM 3D printers. (You can read more about why we undertook this initiative here.) The features composing this geometry are largely based off the collaboration between Andreas Bastian and Make Magazine to develop Make Magazine’s early 3D printer shootout benchmarking protocol.

The geometry we’ve developed tests how well a printer’s hardware and software are calibrated to a given material by stressing the system to the point of failure. The failures lead to the creation of witness features that can be used to assess the performance of the slicer, the extruder, and the motion system. While this geometry and protocol can reveal many different types of problems in a system, fixing the exposed problems is out of scope for this basic assessment protocol.

It’s important to create dedicated test features and to calibrate those features to guarantee at least partial process failure: causing failure allows you to confirm that you’ve actually reached the limits of a process, and provides something discrete to measure and compare as relevant variables are changed.

Having discrete tests that each are calibrated to cause process failure, however, can become difficult to manage as the number of specialized tests grows, so having a consolidated geometry makes the process of testing a new 3D printer more manageable. We designed geometry to group non-interfering test features in the lower half of the print and places the riskier feature at the top of the print so that it doesn’t interfere with earlier test features.

Contributing

We’re releasing with version 4 of this geometry and would like to work with the community of testers and creators to continue to refine and build upon both this test geometry and the test protocol, both for FDM and soon for SLA, SLS, and metal AM machines as well. Please share comments, suggestions for improvements, and other ideas by opening an issue on this repo or submitting a pull request. And, be sure to tag photos of your prints with #FDMtest!

kickstarter-autodesk-3d's People

Contributors

andreasbastian avatar marhar avatar pencerw avatar tiegz avatar zachdunham avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

kickstarter-autodesk-3d's Issues

LCD / DLP test Ideas

Here's the test I've developed for the Anycubic Photon LCD printer.

https://github.com/altLab/photon-resin-calibration

This is one of the steps to find the best resin settings. if you want to integrate something alike in the SLS/DLP section feel free to pull ideas from there I'm also open to collaborate with you guys if you want.

Best Regards

SLA Test Form

The team at formlabs who created the Form2 SLA machine have a jacad generated STL to test machines:

https://pastebin.com/XsYbhss9

The resulting testform object is very good at quantifying SLA performance down to high resolution features.

From the code you should see that it generates:

  • Positive features (wires, walls, etc).
  • Negative features (holes, slots, etc.).
  • Structural features (bridges, overhangs, etc.).
  • Dimensional accuracy (small dimensions, larger dimensions).

More explicitly:

  • bridges on 2 axis
  • internal thread
  • hole geometry
  • column geometry
  • unsupported walls on 2 axis
  • slots on 2 axis
  • overhang angles on 2 axis
  • text rendering
  • hex stud
  • external thread
  • base definition test (print directly to build surface)

Surely it is a good candidate for comparing such machines - where each must be tested individually.

Horizontal hole feature

One issue we have is horizontal holes experiencing sagging during cure/cooling process.
Any chance of adding a horizontal hole feature (maybe to the pillar?)

Adding a sphere

How about adding a spherical shape?

I have noticed spheres tend to expose all sorts of smoothness issues.

Bad method of calculating dimensional accuracy

In presented example, X error and Y error values are presented as positive or negative values, while they should be presented as absolute values. For example, let's assume we've got following X measurements: 26mm, 19mm, 15mm, 9.5mm, 4.5mm, then, using current method X Error (X Error=Measuerd X - Target) will be: 1mm, -1mm, 0mm, -0.5mm, 0.5mm, and then average error will be 0, while real error is huge. Method should be changed to use absolute values as X Error and Y Error values (X,Y Error=abs(Measured X,Y - Target)

Where to collect the results?

There should be a unified place where users can submit results. Something very simple as this board would do, currently its hard to hunt down the results.

Additional specifications

Specifically regarding the FFF (FDM) comparison, if the goal is to get an apples-to-apples comparison between printers, then we should also specify the nozzle diameter and layer height to be used.

Revisit standard settings discussion: I don't know what layer height I _should_ use?

Relating to issues: #7 #8 #10 #27

It's...fairly difficult to gain a baseline level of understanding of the 3D printing world, and adding information like what is being asked for in these issues to a benchmark project like this would go a long way to helping create that easily accessible reference of basic knowledge that often permeates other hobbies.

If you'll pardon me to plead my case:

Having just setup my printer, done a few of the pre-compiled models that had prebuilt gcode bundled on an SD card, I decided I wanted to try this kickstarter test shape and compare to the known score for the model printer I have so I can see how well I've set the thing up as compared to the factory-assembled version. Unfortunately no one seems willing or able to provide the standard settings that were used to slice the model when creating that benchmark.

In a comment for closing #10, @andreasbastian wrote "Standard settings are the settings that a printer/slicer/materials manufacturer/provider prescribe for using their product." but this doesn't actually answer any of the questions being asked or help understand how to use the model. I've consulted every manual I can find for my printer and slicer, and nowhere does anything suggest an "optimal", "default", or "standard" layer height, infill %, infill pattern, or value for any parameter that might impact the quality or time taken to print.

I use PrusaSlicer and this is further complicated by several fairly equally recommended quality profiles ranging from "Ultradetail" to "Draft". These profiles vary estimated print times between 2 hours and 22 hours. The layer height settings of these profiles varies between 0.05mm and 0.3mm. Whether supports are printed is also up in the air but doesn't vary by profile.

I think they should be printed without support material and that adding supports would defeat the point of the overhang and bridging tests, but no one will write anything down to confirm or deny, officially, how I'm supposed to print this model. The only real evidence I have is the DrVax youtube videos comparing Ender 5 and Prusa MK3 where he shows removing the print from the sheet. In his video he doesn't have any support material on these, which are implied to be fresh from the printer.

But presumably layer height resolution can also impact how a lot of model features score like fine flow control, negative space, maybe even bridging and overhangs but I'm just guessing. So when the readme says something like "Prusa i3 MK3 scores 22.5"...what settings were used to get that score? At very least what basic profile or layer height? If you included how long it took to print I could at least pick the quality profile that's nearest to that length but as it stands I am completely in the dark here.

Obviously there is almost infinite tweakability in printer and slicer settings but just by picking a different built-in profile and not knowing anything I can make a Prusa take over a day to print this model, but no one will say whether that's the right way to do it. And measuring print time like suggested in #8 is almost useless without this baseline assumption of the resolution the model is being printed at since even small changes to that layer height value change the print time dramatically.

tl;dr: Please for Pete's sake, just include the most basic print parameters for most slicers in the readme, it'll help out the newbies immeasurably and really increase consistency in benchmark data.

Print Time

If we are looking to get a true apples-to-apples comparison between printers, the amount of time spent printing the objects should also be taken into comparison.

Just my two cents, but I would suggest that additional points be allocated towards print speed with a faster time to completion being awarded more points than slower printing. (and this should be the actual print time - not the theoretical time calculated by the slicer)

White on White Model Image

Please consider changing the model image to something other than a White Model on a White Background. Please see the difference in the images below.

image
image

Include 3MF versions?

3MF is lightweight, portable, and a heck of a lot better than STL ;) @andreasbastian, let me know if I can help generating the files (if you're open to including them)!

3D in STP format

Can you provide stp format so we can edit?
we can't use the availabe format for editing

FDM Protocol Text Error

Looks like a score might be missing in the FDM Protocol, under "Overhangs". 1, 3, 4, and 5 are listed, but not 2. The photo above shows a print with a score of 2.

negative features plug labelling error

Looks like the rightmost 2 negative features plugs are not properly labelled.
They read 0.3 and 0.5 instead of 0.5 and 0.6 (or 0.7 may be?) respectively.

Results - Ultimaker 2+

We ran the test print on an Ultimaker 2 which has been upgraded with Ultimaker 2+ parts set. Part was placed and prepared using Cura 3.5.1

File: ksr_fdmtest_v4.stl

Material: PLA

Nozzle: 0.4mm

Layer Height: 0.1mm

Infill: 20%

Generate supports: No

Print time: 9h 31min

20181107_085306
20181107_085313
20181107_085319
20181107_085327
20181107_085526
20181107_085539
20181107_085545
20181107_085554
20181107_085600
20181107_085616
20181107_085626
20181107_085655
20181107_085707
20181107_085715

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.