S3D (and other slicers)
-
I could easily be wrong but I don't think the acceleration options in Cura are compatible with the current Duet firmware.
Also, I don't think it supports firmware retraction for all printers.
However, I am using the Cura master branch at the moment and getting pretty good results.
I have S3D also, I hate it!
Does firmware retraction really add that much in terms of quality ? Doesn't it basically just retract if not printing ? Seams like the delay the slicer would add for the retracts shouldn't be noticed with the Duet WiFi speed.
Trying to solve this issue at the moment with Any slicer at all, as you can see it's trying to print a top layer over top of a hole with nothing to connect to. This just makes a complete mess.
Know any tricks in Cura to not have this happen ? So far it appears to have the same flaw S3D does in this area.
Thanks,
Jeff
-
Well, quite some time back, I wrote an email to the S3D technical support people complaining about how it failed miserably because it didn't extend skin far enough under perimeters that are placed above. It's essentially the same problem as you have. At that time, the only slicer that seemed to get this right was slic3r. I haven't used that for quite a while but it's probably worth a try.
-
At least Cura is open source and so we have the possibility of fixing stuff we don't like. I have been making some trivial contributions to it. It has occurred to me that a fix to this problem would be really good so I shall go back to thinking about a solution.
-
Yes for mixing type hotends firmware retraction is an absolute must
-
A Search on there Web page gives no results for firmware retraction therefore it is a no go for me with Cura
-
Well, quite some time back, I wrote an email to the S3D technical support people complaining about how it failed miserably because it didn't extend skin far enough under perimeters that are placed above. It's essentially the same problem as you have. At that time, the only slicer that seemed to get this right was slic3r. I haven't used that for quite a while but it's probably worth a try.
I actually tried the same scenario/part with slic3r and it failed in the same way. I've wasted more filament then I care to mention or ended up with terrible looking parts because of this exact issue. I do lots of ABS work and I'm not about to print too dense and have stuff try to curl or delaminate. I'm going to mess with the beta version of Cura for a bit and see what I can do. The S3D folks just don't seem to care anymore, if they do they are failing to relay that to the customers very well.
Jeff
-
A Search on there Web page gives no results for firmware retraction therefore it is a no go for me with Cura
I see an option to disable retraction, isn't it possible to just disable the software retraction and enable firmware retraction on the start script or is it another G code that needs to be sent in place of normal retracts ?
-
Yep needs other G-Codes to be sent
-
Hi Jeff, I have just spent some time working on Cura to come up with a solution for the skin above sparse infill problem and (amazingly) appear to have something that looks like it's doing the right thing. I have submitted it to the Cura devs. Even if they like it (or some later version) it won't make it into Cura for a good while yet but if you are up to building Cura yourself then you could give it a try. I only use Linux and building Cura on that is reasonably straightforward and I can provide some hints as to what to do.
-
Hmmm was just about to blir $150 on S3D.. So its not worth going for it? I'm kinda happy with Craftware to be honest, but this bug that the bed settings are reset each time I close the program is driving me nuts
I'd also like to be able to print with different settings at different height and craftware doesn't support that. -
Hi Jeff, I have just spent some time working on Cura to come up with a solution for the skin above sparse infill problem and (amazingly) appear to have something that looks like it's doing the right thing. I have submitted it to the Cura devs. Even if they like it (or some later version) it won't make it into Cura for a good while yet but if you are up to building Cura yourself then you could give it a try. I only use Linux and building Cura on that is reasonably straightforward and I can provide some hints as to what to do.
What engine are you working with ? This is a pretty good potential fix for sure. My thought was to grow under the skin (i.e. support it) however growing outwards might be a better choice.
Jeff
-
Cura is split into two parts: 'Cura' is the front end user interface. 'CuraEngine' is the back end that actually does the slicing.
Without the mod, Cura behave like S3D: when a skin runs under a raised feature, the skin stops almost immediately (under the perimeters of the raised feature). What the mod does is grow the skin so that it will extend under the perimeters by at least the distance between the infill lines. Assuming the raised feature is tall enough, further infill will be placed on top of the skin which will end up being sandwiched by infill. It's work in progress but does appear to handle the simple cases OK.
-
Furrher to my January 27th post on this topic:
I have tpost1.g as M116 P1 and tpost2.g as M116 P2 and I had the extruders as T0 and T1
However for a dual colour test print on tool change it is not waiting for the new tool to heat up.
I think the issue could be because S3D denotes the hot bed temperature id as T0
so I think I must therefore denote the extruders as T1 and T2.
Very confusing.
Can anyone else who has done two colour printing in S3D shine some light on my dilema?
Thanks -
solved my S3D issue by deleting the S3D temperature controller for both extruders T0 and T1 and re-entering them.
Now all is well -
solved my S3D issue by deleting the S3D temperature controller for both extruders T0 and T1 and re-entering them.
Now all is wellBeen there, done that. Glad it worked out.
-
Given up on S3D for the second time (got a full refund) as dual extrusion still seems very iffy, even though slicing is extremely fast.
I'm going back to MATTER HACKER which can produce a prime tower and or wipe brim.
This has no parameter to enable firmware retraction so I'm using their g code 'before tool change', 'after tool change', 'before layer change', 'after layer change' feature.
I still have the M116 Pn in my Tpostn.g files and have put G10 in 'before tool change' and G11 'after tool change'
along with an appropriate M207 line in config.g, of course.
Is this the correct approach, as things do not look quite right?
The print head is still dwellling too long before it moves to the primer tower, and leaves its mess on the print.
I tried using Tpren.g as DC42 suggested but that just left the head in the wrong place and the co-ordinates just went awry from then on.
Can anyone help me with the gcodes for the TpreN.g files or in the before/after g code sections ?
Thanks -
@ Merlin,
You posed the question about using firmware retraction which I answered in this thread on 20th Jan. Are you still using the Chimera with separate nozzles? If so, you should not be using be using firmware retraction.
-
got it. I'm eagerly waiting for my cyclops head to arrive.
-
got it. I'm eagerly waiting for my cyclops head to arrive.
I have the legends pack, I've not done much with my cyclops yet however you'll like it. I gave up on the chimera concept and just use one head at a time. I just got sooo tired of collisions no matter how much time I spent trying to level everything. I've recently changed out all the rod in my printer, belts, pulley, etc. This might help, guess I should try again. The cyclops is a better concept then using two hot ends in many cases..IMO.
Jeff
-
I should update here that I'm now doing z-hop out of firmware while using S3D, with great results on 1.17+
