Jump to content
Ultimaker Community of 3D Printing Experts

rexipus

Member
  • Content Count

    8
  • Joined

  • Last visited

Community Reputation

0 Neutral

Personal Information

  • Country
    US
  1. rexipus

    2.4 beta 2 nozzle temperature bug

    To reinforce, or perhaps just to reiterate, this addition of 5 C to my nozzle temperature could actually have damaged my print head, because I was already running a nozzle temperature that was already right on the line between what the PTFE liner could sustain, while printing PETG, and what it couldn't sustain without cooking the PTFE liner. I'd be pretty upset if my liners got cooked, and a nozzle clogged up and ruined a print, and necessitated me taking my print head again just to replace a cooked PTFE liner, just because someone on the Cura team thought it would be really clever to add 5 C to my nozzle temperature without asking me if this was OK. No, it's not OK. To steal a meme from the social justice warriors (not knocking them), "consent is mandatory!"
  2. rexipus

    2.4 beta 2 nozzle temperature bug

    Oh wow, I had no idea. Yeah, adding 5 C by default to the starting temperature is just ludicrous. Why 5 C? What about different materials? What about different build surfaces? What about the fact that people have already tweaked their settings and arrived at settings and profiles and whatnot that work for them? And then the new Cura version steps in and makes a decision for them and changes things up. Wow. If this is in any way a democracy, then I vote NO. Don't ever, EVER change my settings by default with a new version of the program. Just don't do it. If you want to give me new options that's great. But don't change my settings by default with a new added feature. That's completely bogus.
  3. I recently switched from 2.4 beta to 2.4 beta 2, and I've started seeing a new problem that I've never before seen in the 6 or 7 months I've been using Cura. The nozzle temperature is showing up in the gcode file 5 C higher than it was set in Cura 2.4 beta 2. I routinely set my PETG nozzle temp to 245 C, and was surprised to see my temp was at 250 C. I manually set it to 245 and continued that print. Then my next print was at 250 C, and my next. I have looked around inside of Cura to make sure that I was doing it correctly, and I was. The bottom line is I am having either to manually set my nozzle temp to 240 C in Cura so that it appears in the gcode as 245 C, or else I leave it at 245 C and then manually edit the M104 and M109 commands from 250 back down to 245. Anyone else seeing this? This has been quite a bother for me, because I keep forgetting to manually correct the temps to 245 C, so my Duet Wifi controller will heat up the nozzle to 250 before it drops back to 245 when I manually set the temp to 245 in the Duet Wifi control page. The problem with this is that I'm still using my stock hot end with a PTFE nozzle, and 250 C is really too high, and threatens to damage my PTFE liner. It's tolerating 245 C, but just barely: I cooked a PTFE liner experimenting with 255 C before, so this is right on, or just over the line.
  4. The Cubic Subdivision feature, one of the marquee features of the 2.4 Beta, still doesn't work on my machine. Others chimed in saying they saw this too. I uninstalled the original 2.4 Beta version and installed the new version that came up a week ago. On my machine all that shows up of the infill, when set to Cubic Subdivision, regardless of the percentage, is a single line in the upper left arm of this quadcopter body. My machine is an Intel i7 6900 with 32gb of RAM running Windows 10 64-bit, anniversary addition with all the latest Microsoft updates. Video card is NVidia 1080 with most recent drivers.
  5. Hmm, I wonder what could be different about the devs' machines that makes this feature work, but on our machines it simply doesn't work at all. This is a brand new installation, and my settings aren't unreasonable at all. It's really strange. They wouldn't have released this beta and announced this feature if it didn't appear to them to be working, yet for at least some of us it simply fails to work, and doesn't announce any errors or anything. It's just not there. I actually installed the 2.4 beta specifically for this feature. I use Cura most of the time for most of my prints, but I also use Slic3r, Craftware, or Simplify3D if they can do something I want with a specific print better than the others can. I'd been printing this frame most recently with Simplify3D, but it's process model is broken for what I want (has to do with top and bottom layers and how they (don't) work with S3D processes). Cura's gradual infill option is really cool for what I'm doing, and this cubic subdivision would have taken what I gain from gradual infill and extended it in all directions inside the model, which is just great. The model shown is a quadcopter frame. On a quadcopter frame one must balance weight and structural rigidity and strength. The cubic subdivision would allow me to move more or the infill structure out closer to the walls, where it would increase rigidity (and help top or overhanging layers go down better), while hollowing out the center, which reduces weight. This is literally the only feature that made me go through the crap of uninstalling the previous version of Cura (2.3.0) and removing the data directory*. If I can't get this feature working properly I'll continue printing this model using Simplify3D, which can do a couple of things that I actually need better than Cura**. *this is what I had to do to get Cura 2.4 to launch at all, since Cura still, at this date in 2016, hasn't figured out how to get along with other versions of itself on a user's machine **one of those is specifying two-layer brim for adhesion. The Taulman Alloy 910 nylon I'm using to print these frames likes to lift up a little around the edges of the ends of the arms if only single-layer brim is specified, but a two-layer brim locks it down pretty well
  6. rexipus

    Cura 2.4 beta is here!

    Same was happening for me. I uninstalled 2.3 and then moved out the directory under Users/name/appdata/local/cura (or whatever, I'm going from memory). Then it came up fine. I'm still not seeing cubic subdivision infill show up though in the layer view. This is a bummer, because this feature is the only reason I uninstalled 2.3 and installed 2.4 beta to begin with.
  7. First, thanks for your reply! No it's not a typo. Cubic and Cubic Subdivision are two separate infill types. When I have infill set to Cubic or any other of the usual infill types they show up in layer view, the model weight reflects the infill material, etc. Only when set to Cubic Subdivision does the infill simply not show up at all. Here are screenshots. First shot shows normal cubic infill as displayed partway through this model in layer view. Next shot shows cubic subdivision infill type selected, and nothing shows up but some strange line through the upper left arm of the quadcopter frame:
  8. I just got Cura 2.4 Beta installed and running, and am eager to test out cubic subdivision. When I set that as my infill type, then view the model in layer view, I see no infill lines at all. Also the calculated weight of the print is what it would be if there were no infill. When I change infill type to cubic or any other type of infill I see the infill in layer view as I would expect. Is there something I'm missing here? If Cubic Subdivision obviously didn't work they wouldn't have shipped the 2.4 Beta with it as if it were working, so something's going wrong here. What I haven't tested yet is whether a print is actually using cubic subdivision infill and it's just not showing up in Cura, or whether the infill really isn't being generated at all. I tested this with two different, completely unrelated models, both of which I have previously printed just fine using Cura 2.3.0. With neither model was I able to see any infill when set to Cubic Subdivision.
×

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!