Jump to content

AbeFM

Dormant
  • Posts

    277
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by AbeFM

  1. Well underway. So far so good. If you set acceleration values in a print profile, will it effect the predicted print time, even if you don't "enable" acceleration control?
  2. Really, I'd be utterly happy making a profile from scratch. I'd heard there's some new stuff under the hood for defining printers so I thought it would be a good time to do this. Little of the original printer remains, at a certain point, I just want a Cartesian, dual extruder printer I can set the bed size on. It would be nice to base it on the CR-10s, but since the extruders, gantry and firmware are mostly homebrew, much of the stock numbers inapplicable now. I feel like there's a "known method" or manual out there I don't know about. If so, could you point me there? 🙂
  3. Somewhat related: I too have weird settings, and frankly, I'm not 100% attached to them except it took half an afternoon of tweaking files and experimenting. That makes me think maybe I did something wrong. I don't want to clutter this thread, but any help in creating a Future-Proof printer definition would really help!
  4. Here are the files from the 3.5 directory with the printer defs. AbeCuraTemp.zip and the ones from 3.6 (no logs) 36setings.zip
  5. I'm not sure if you've tried it, but I thought there were improvements in the combing in 3.5.1. Depending how far back you got that impression, it may be worth trying the feature again.
  6. Hey, thanks! I most certainly can... I mean, I most certainly want to. What should I upload that would be the most helpful? Really it isn't about saving what I have (I know my bed dimensions and such), but it would be nice to put one in that will have some future-proofing. There's no nozzle offset, really nothing special at all, it's just a CR10s with lower accelerations (heavier head) and a second extruder. I was hoping I might take a built in profile and just make a couple changes and hit "save as". (Aside: I don't think I remember the #2's being in the window. But unsure.) Attaching a .3mf export, not sure if it has settings. AbeSettingsChiMara351.3mf
  7. I've not been using CURA much lately, no good Mk3 profile and limited support for the MMU (Prusa's mutli material unit). But I'll be doing more now. ?
  8. Speaking of "mutating", perhaps one could rock the (spacial) frequency back and forth just a bit if a stretch is more than XXXmm - making the wavelength longer like a cubic 3D infill? Probably too much to keep track of, but it's a thought - as would be slowing/speeding the head every wave or two? I think you're right just to watch out for it, but perhaps it could be avoided altogether. Thanks for adding it!
  9. Oh, I was thinking it was just because the dialog "remembers" its settings once you export something with them. If you just make changes and don't save a file, they get lost.
  10. Howdy folks! I've been using a few printers with CURA over the past years, including a dual extrusion machine based on a CR-10S with a Chimera+ from E3D (Dual extruder, Dual nozzle). Every time I update CURA I end up losing all my settings. I still have something working on 3.5.1, but would like to use the machine with 3.6.0b, and hopefully do it in a way that I don't have to redo everything with each version of CURA to be released. Is there some simple way to do this?
  11. Is this memory leak new to 3.6? You make it sound like it's in 3.5.1 as well? What OS are you running?
  12. CURA 3.5.1 Win10x64 I used Pause At Height set to 2.5 mm, but it pauses too early: ;FLAVOR:Marlin ;TIME:816 ;Filament used: 0.946513m, 0.0138939m ;Layer height: 0.24 ;POSTPROCESSED ;TYPE:CUSTOM ; -- Pause at height (2.10 mm) -- M25 ; Pauses the print and waits for the user to resume it ;Generated with Cura_SteamEngine 3.5.1 T0 M140 S40 I think the action of putting in the pause is happening where the "processed with XXXX script" might go.
  13. It looks like XY-overides-Z is only for the tops, not the bottoms, and ruining the prints.
  14. I see quite a gap on the support floors. I'll try to track this down.
  15. I have some complex models with curved/spherical areas where my PVA support should stick, and allow a tower to support features above. (simplified test piece) I had decent success, a recent print had all but one area supported correctly, so I made some changes hoping to perfect it: I dropped Speed, Accel, and Jerk for Floors, increase floor density and changed the pattern to "lines" And not a single support worked! I'm not sure what's useful to provide but I'd sure love some advice. Using a CR-10s with a Chimera+ (i.e. two fixed independent extruders)
  16. I'd taken a vacation from CURA, and I forgot about this. Still there, still annoying. There are worse problems, but this remains.
  17. It is likely I'm misunderstanding something here, but.... I'm not sure why this window pops up when I press that button. CURA 3.5.1 / WIN10
  18. FINALLY trying this. Notes: In the extruder file: I think "extruder_nr": { "default_value": 0 }, should be 1 as well, as in: "overrides": { "extruder_nr": { "default_value": 1 }, "machine_nozzle_size": { "default_value": 0.4 }, "material_diameter": { "default_value": 1.75 } } ------------------------ The other issue: { "0": "creality_cr10_dual_extruder_0", "1": "creality_cr10_dual_extruder_1" } You need a comma between the two entries in that ... list? array? Thing with bendy brackets. ? Thanks again, going to try this out.
  19. 1) Thanks thanks thanks for adding this!!!! It's super useful!!! 2) It's all too easy to set this to a terrible number. I propose it it forced to an integer multiple of the spacing. Perhaps just a spacing factor (1/4,1/3,1/2,1,2,3,4) 2.6 Support Distance / 1.2 Initial Layer 2.6 Supp/ 1.3 Initial Layer Notice how the integer number doesn't leave support basically touching 1 mm^2 over the whole layer. 3) Changing this setting does not invalidate the slicing - you can't hit "slice" without first triggering it by making another qualifying change (such as turning on-then-off-again "use towers"). VERY excited about all the changes in 3.5.
  20. You were ok before? You might just need some more priming, but perhaps it's been (inadvertently) removed? I was pointing out that mine started with a temperature NOT defined under EXT0 at all, in the hopes this helps developers track it down. Mine was most definitely printing with the EXT1 standby temp on the BRIM printed with EXT1.
  21. OMG thanks for that!!!!!! This is something I've been fighting for a long, long time, and more or less given up on. I'll try it out. Even the firmware can't seem to keep "is the second extruder #1 or #2" straight, but I think I can manage.
  22. Agreed. But setting something you count on AFTER the start code instead of before it seems like it would make more sense, hence the suggestion. I'm just pointing it out, I've already fixed my issue.
  23. Haven't touched this in a while. Let me know if there's something to try. I try to stick with mm (metric) since the slicers like it, but either is ok. I typically use Deviation: 0.01 (minimum 0.00592755 mm) Angle: 1.0 (minimum 0.50000 deg) I've noticed saving in AMF can cause weird issues - I get warnings about material type in SW 2016 sp3 -Abe.
  24. Your printer has the fancy moving nozzles, right? I don't know when UM started doing that (UM3?) The issue I have is the PVA "strings" end up being "PVA-row-of-holes-in-your-part" once you wash it. Awesome print, BTW
  25. The real issue is the printer needs to be aware of the second nozzle in a meaningful sense. Even so it's hard to eliminate. It's just a challenge with dual nozzle prints.
×
×
  • Create New...