Loading

Slic3r Thing-O-Matic Fix

by teppic, published

Slic3r Thing-O-Matic Fix by teppic Dec 2, 2012

Description

***I now consider this to be obsolete. I get great results with a recent version of Slic3r, in combination with sailfish on my thing-o-matic, without any additional hacks. Try it out!***

---

This is my Slic3r settings for Thing-O-Matic, including a postprocessing script to create the correct extrusion commands.

These settings works great for me, although I haven't really measured and calibrated the result yet. Feel free to share your experience and improvements!

Files are also available in this gist:
gist.github.com/4250182

Recent Comments

view all

Hmm, I wouldn't think that this script would cause such error message. I can't really say what it means though... Nice to hear that it (sort of) works however!

Tested it works fine just gives red error driver replicatorg.drivers.gen3.Makerbot4GAlternateDriver@1c98c1bis not an instance of IntractiveDisplay. every min but not effecting build.

 I'm glad that you like it! Make sure that it generates all three of the commands: M101, M102, M103.

You need to make sure that "use relative e-distances" is checked in the extrusion settings. Otherwise the script won't work.

The script never modifies the extrusion speed. The speed is set once in the start.gcode. Perhaps that is the problem. You can always try modifying the extrusion speed there though. I'll try to fix this in a later version.

More from 3D Printer Accessories

view more

Makes

Liked By

view all
CIMG1165.JPG

Give a Shout Out

If you print this Thing and display it in public proudly give attribution by printing and displaying this tag. Print Thing Tag

Instructions

1. Load the ini-file
2. Place tomfix.py in the same directory as Slic3r.exe (on Linux you might have to add the entire absolute path to the script in slic3r's config)
3. tweak your speeds and anything else you might want to.
4. Generate g-code and check that the post-process script ran correctly (the first line should contain the following: "Processed with tomfix.py", otherwise you will have to check your console output for errors.
4. Load g-code into ReplicatorG and press Build

Please note that the speeds are adapted for accelerated build with the jetty firmware. If you use the vanilla firmware, you will probably have to decrease the speeds a bit.

Comments

You must be logged in to post a comment.

Bazaff on Jul 17, 2013 said:

Tested it works fine just gives red error driver replicatorg.drivers.gen3.Makerbot4GAlternateDriver@1c98c1bis not an instance of IntractiveDisplay. every min but not effecting build.

teppic on Jul 22, 2013 said:

Hmm, I wouldn't think that this script would cause such error message. I can't really say what it means though... Nice to hear that it (sort of) works however!

Coin3 on Dec 12, 2012 said:

I can confirm that the updated script does work on Windows. Thank you very much for this, I have been wanting to try out Slic3r with the TOM for quite a while now!

The settings had to be changed a bit for my machine of course, and now it prints great. But retraction doesn't seem to be working. There is very obvious stringing in all places that it should retract. Do you know how to fix that?

teppic on Dec 12, 2012 said:

 I'm glad that you like it! Make sure that it generates all three of the commands: M101, M102, M103.

You need to make sure that "use relative e-distances" is checked in the extrusion settings. Otherwise the script won't work.

The script never modifies the extrusion speed. The speed is set once in the start.gcode. Perhaps that is the problem. You can always try modifying the extrusion speed there though. I'll try to fix this in a later version.

teppic on Dec 9, 2012 said:

If anyone is wondering, I have done some modifications to the script to make it work on Windows. Will post the updated script and instructions soon!

teppic on Dec 10, 2012 said:

The script and configuration updated to work in Windows now. I'd be glad to know if this works, or if you have any problems.

wishmaker on Dec 9, 2012 said:

will it work for a cupcake or if you could make one for my botmill glider 3.0 I would appreciate it. 

teppic on Dec 9, 2012 said:

I suppose it will work for the cupcake. As far as I can tell, the G-Codes are compatible, so the post process script will work. However, you will most likely have to tweak the speed settings and the start and end gcodes.
You'll have to try it, and see what works for you. I'ts hard to know what to do without access to the printer.
Don't know anything about the Glider, so i'm afraid i can't help there.

PolygonPusher on Dec 2, 2012 said:

Thanks for this, and keeping stuff up-to-date for us Thing-O-Matic operators. :)

Top