Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

5 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I tried to match as many settings between extruders as I could (I have to tell you *that* is tedious, it takes so long to switch between setting lists, if dual extrusion becomes popular, people are going to flee cura faster than you can say "do you think this extruder's settings will load any time this week?") In some of the previews it looked like the infill was aligned, but that could be coincidental 😞
  2. @tinkergnome see my response a couple replies above, which has an example model pair. I tried messing with the per-model settings but there was nothing I found that produce settings equivalent to simply switching nozzles while rendering the parts of a the letters. I should note that unlike the simple X model, there's actually some other stuff on my original (a border, etc) that would preclude my simply changing nozzles at layer N 😞 Where do I find the "Merge Origins" option??? Lastly, I tried making the models not actually overlap and separated them by .1, .5, 1.0 and 1.1x layer height, all to no avail. I've carefully made as many of the non-material settings the same across the two nozzles as I could, but no effect.
  3. Here's a trimmed down version of the two models. X-Base.stl X-Fore.stl
  4. Turning off Remove Mesh Intersection entirely seems(*) to have fixed it (although, that seems backwards) (It created a different problem: it tries to print layers for both models at the same time instead)
  5. That didn't fix it, but it did affect alternate mesh removal's impact: But it still produces two surfaces where the letters meet:
  6. Even with the letters above the baseplate it generates surfaces between the two, that was what lead me to try recessing them. Hmm. Maybe I should recess them but not cut the recesses out of the baseplate.
  7. I have a model which is a 3mm thick square with raised letters above it. The idea was to print it using dual extrusion, so I made it two models, assigned each to an extruder, and grouped them. But when I look at the preview, it's burning a whole lot of time creating skins at the interface. How can I stop it doing this? (Pardon the colors, I gave up fighting cura on choosing what color non-ultimaker filaments are)
  8. 11 hours into a print, a piece of the skirt separated from the build pate and got onto the top surface. I selected Pause so I could remove the debris, but it's not accepting Resume from the front button or from cura connect. It's keeping the print bed at 85c but the print head has now cooled to ambient, and it continues to just sit there 😞 - Printing single Extruder with nGen, bed 85, ext 240, Only thing different about this and previous pauses is that I had manually adjusted the extruder 1 temperature -1 degrees. Hour later: still no resume =(
  9. That's a tricky print, but a pleasing result, but btw the "Printing Guidelines" link just takes you to the product page now. Question: Would this be a good candidate for the BB print core? Also, it would be awesome to have a way to leverage the way these kinds of filament react to temperature variations to produce grain effects. You can do that with post-processing but that's just flat layer-by-layer and the end result is an mdf/plywood effect rather than grain.
  10. @Matioupi It's controlled by this, if you don't have it visible, search settings for it: Infact, search for "horizontal expansion" to make sure you don't have the regular one set too.
  11. I've been noticing "random" behaviors. The other day I did something routine and it suddenly started unloading printcore 1. @gr5 told me there is an issue preventing printing the calibration chart because the printer over-retracts print core 2, but then support told me that he's wrong, the bug prevents anyone printing a calibration chart. Except, I've been able to print a calibration chart by doing nothing more than print->power cycle->print. I was able to print once and then it lost the calibration (even tho it has the settings). With active leveling set to manual, it will occasionally still do active leveling on me. There's just this long list of weird things the printer has been doing since the last firmware. I know I could downgrade, but physical, forced, firmware kludges have bricked too many devices for me in the past, and I can get about 70-80% of the prints I want with single extrusion, and I haven't seen any kind of disclaimer that if I brick my printer following the firmware recovery instructions I won't be out of warranty... @SandervG I'd rather than they put the old firmware up on the testing channel and let people choose to "up"-downgrade to it.
  12. My solution was just to reduce the first layer height and width. TPLAs inherent adhesion is good enough without needing to crush it against the plate. Also results in a more consistent glossy finish. No curling, no elephants foot. The line width may not even need reducing but I found it made the gloss a little less shiny-polished, and for the piece I'm printing that was a better look. The other thing you might consider: if you have one of the newer build plates, the side of the plate with the heat sticker on it has better adhesion. Flipping the build plate with give you slightly less adhesion, but again, TPLA is already good.
  13. Guys - fuzzy skin has only one thing keeping it from kicking ass: there doesn't seem to be any way to restrict which surfaces get fuzzed. For example: it doesn't hurt, but you might not want to waste print time on fuzzing the never-to-be-seen underside of your model; or you might not want to fuzz joints/connections. Ironing likewise would be nice to have finer control - perhaps the option to paint which surfaces you want each applied to? Hats off to you on both of those features, btw, printed a set of steps for our 15yo cat to get in/out of the litter pan with a bit of dignity, and she'd have nothing to do with the test print, but the fuzzed skin version she liked so much I printed her several other steps and pieces 🙂 They also look spectacular with some materials. LayStone with fuzz keeps fooling people into thinking they're touching a chunk of limestone or pumice 🙂
  14. I hadn't, but that looks interestingly close to what I was considering, except I'd want it all the way thru the height of the model. In Simplify3d I'd probably just have multiple processes and split the high-fidelity parts out to a separate process.
  15. PS: - "def __init__(self) -> None:" init doesn't return None, it actually doesn't return anything, so at some point having the "-> None" will break your code. - if you make your function-entry comments into strings, python will automatically use them as the function's __doc__ property, so that they are documented by help(function_name, and will the life of anyone who looks at your code as well as your own a lot easier 🙂 > ipython Python 3.7.1 (default, Dec 10 2018, 22:54:23) [MSC v.1915 64 bit (AMD64)] Type 'copyright', 'credits' or 'license' for more information IPython 7.2.0 -- An enhanced Interactive Python. Type '?' for help. In [1]: def getSettingDataString(self): ...: """ You may either use the normal getSettingDataString function or the getSettingDataStringWithInfo ...: the latter will add a comment setting in which you can enter any relevant information ...: you want to insert at the beginning of the GCode file """ ...: pass ...: In [2]: help(getSettingDataString) Help on function getSettingDataString in module __main__: getSettingDataString(self) You may either use the normal getSettingDataString function or the getSettingDataStringWithInfo the latter will add a comment setting in which you can enter any relevant information you want to insert at the beginning of the GCode file In [3]: If you'd like to experiment with gcode without always having to remember the gcode names ... it's very preliminary, I've only been hacking at it for a few hours: https://github.com/kfsone/pymcode. If you have a UM3, there's a "ultimaker3.py" script you can run that drops you into an ipython repl with "um3" configured as a connection to your printer and "ops" having all of the command aliases. Or you can then type "repl()" and it will go into a mode where you can basically either type '"M104' to send raw gcode, or you can just use the command names: Cmd> "M105 Cmd> set_bedtemp 65 Cmd> "T0 Cmd> set_hotendtemp 200 Cmd> wait_hotendtemp 190 Cmd> go There's a "help" command to list the repl commands.
  • Create New...

Important Information

Welcome to the Ultimaker Community of 3D printing experts. Visit the following links to read more about our Terms of Use or our Privacy Policy. Thank you!