New installation - consistently overextruding though calibrated
-
My my. That's a bit of an unnecessary rant isn't it?
Well, the Duet needs to default to either relative or absolute extrusion. Whichever one it is set to will upset people like you who use the opposite, so it's a no win situation as far as the Duet firmware is concerned.
For info, the default in Slic3r is relative, not absolute as you state.
However, it is such a simple thing to change that I really can't understand why you are so upset about it. Whatever the Duet defaults to, all you have to do is put either M83 or M82 in your slicers start code to tell it what to expect.
Take a few deep breaths and calm down - life is too short to get wound up about such a trivial thing IMO.
-
Maybe slizers are different?
-
My my. That's a bit of an unnecessary rant isn't it?
Well, the Duet needs to default to either relative or absolute extrusion. Whichever one it is set to will upset people like you who use the opposite, so it's a no win situation as far as the Duet firmware is concerned.
For info, the default in Slic3r is relative, not absolute as you state.
However, it is such a simple thing to change that I really can't understand why you are so upset about it. Whatever the Duet defaults to, all you have to do is put either M83 or M82 in your slicers start code to tell it what to expect.
Take a few deep breaths and calm down - life is too short to get wound up about such a trivial thing IMO.
It wasn't a rant. If you see that as a rant, I think you should take a few deep breaths and calm down - life is too short to get wound up about such trivial thing IMO.
It was constructive input that happened to pick apart the arguments used to defend a bad solution for the majority of the 3D community.
For some reason a lot of people just can't handle valid arguments used in a dicussion.
Edit:
@decingman:However, it is such a simple thing to change that I really can't understand why you are so upset about it. Whatever the Duet defaults to, all you have to do is put either M83 or M82 in your slicers start code to tell it what to expect.
Problem is, that M83 is not the norm, far from, and it's not documented anywhere either in a way people can figure out what it is. Means -> it's not pointed out as something you must check.
I suggested it be listed as an active choice.. which means the (minority) using this method can actively choose it for their builds, and the rest aren't confounded by a setting which aren't compatible with default settings of all the most normally used slizers.
Nope, not a rant either
Edit 2: Stop telling people they should calm down.. it's really very derogatory.
It's a multilingual forum and I myself is Danish, so I might be using words that should be substituted with something else, but well… I'm not naitively English speaking, so I might not have the intuitive understanding for the finer nuances.Telling me, that my arguments are invalid because of the tone is degrading to yourself.. come up with arguments against it instead.
-
Maybe slizers are different?
Yes, they are, but none of the slizers I listed (Cura, S3D, sliz3r) are using relative extrusion by default. It means the argument that "most people use relative extrusion" is plainly not correct.
Which is why I asked who all those people might be
This is not a rant either, in case anyone mistake it as such.
-
My goodness. Still wound up about such a trivial thing?
Let's put it another way. The default configuration for RepRap firmware has always been to set extrusion to relative. That stems from the very early 0.6 boards that RepRap pro used and when Adrian Bower wrote the original firmware, through the 0.8.5 boards to the latest WiFi and Ethernet versions. So everyone who has bought a Duet board up to this point in time, has got used to it. What you are proposing is that it should now be changed to default to absolute because that is what you want to use.
For info, I believe that by default, if no M83 of M82 parameter is used in the configuration file, the Duet will use absolute extrusion, which is what you want anyway. It's only the default configuration that sets it to relative and what goes into the configuration file is entirely up to the user. Rather than ranting on about developers or small groups of people choosing a particular mode of operation, you should be applauding them for giving you the freedom to select whichever option you prefer to use.
Your comments about slicers are much the same thing. That is to say that by default, many of them are set to use absolute but many can be changed to use relative instead.
That's the beauty of it all. Users can have whatever they want but whichever one they decide on, the Duet needs to "know" - it hasn't yet been fitted with crystal ball to foresee what any particular user may require.
Edit. Regarding the merits of absolute and relative extrusion, they are essentially the same thing. An absolute extrusion move is essentially a relative move. That is to say that it is a move relative to the start of the print whereas relative extrusion is relative to the last move. In fact, absolute extrusion moves must be converted to relative in order to extrude the correct amount of filament for a particular move. With absolute extrusion, it is vitally important that the extruder be zeroed at the start of the print otherwise the entire print will be thrown out. With relative extrusion, it doesn't matter if the extruder was zeroed at the start of a print.
-
Just to round off this thread
I'm not wound up btw - I just put forth valid objective arguments for my points of view. It's hard for a certain kind of people online to be met with real arguments I know, but it doesn't mean I'm wound up or anything. It's rather demeaning starting to attack people's state of mind, just because you don't agree (not directed at any particular person, but just in general).
Making counter arguments to dismiss what I'm saying is just silly… the goal is to find a solution to work for everyone, not phase out one or the other.[h]How to use Cura in conjunction with RepRapfirmware.[/h]
In Config.g you need to comment out M83 AND in Cura startup.gcode you need to put in M82 to make it work.
The Gcode Flavor to use should also be listed : RepRap (Marlin/Sprinter)[h]How to use Firmware retract in Cura[/h]
If you need Firmware retract you still need to do the above M83 and M82.
You need to insert M200 + relevant parameters in config.g and change Gcode Flavor in Cura to RepRap (Volumetric)¨
Also need to use firmware 1.19 (or newer)[h]Real Problem[/h]
The real problem is the lack of documentation on this issue, which is the the core issue I'm trying to point out.
For most people the absolute or relative extrusion is just babble, and is not cause for speculation when encountering this Extrusion problem.
It's a fundamental setup point which must match, and it should be pointed out in wiki, on each machine configuration examples AND in gcode wiki as well.[h]How to document:[/h]
Not just to tell what Absolute and Relative does an expect people to figure out the combination of M83 an M82, but make real setup examples like I just did above with Cura.Edits: Added info etc.
-
Actually it's only necessary to put M82 in the slicer start gcode to use absolute extrusion.
Absolute extrusion is a huge pain in the butt from a firmware development perspective. It bears no direct relation to the amount of movement made by the extruder stepper except in the simple case of a machine with only one extruder drive, the extrusion factor set to 1.0, and no G92 E0 received since starting to extrude. So all the calculations have to be done after converting to relative extrusion anyway. OTOH the firmware code for pause/restore, resume after power fail and filament change procedures all needs to have unnecessary complications added to handle incoming gcode with absolute extruder coordinates.
It looks like Cura will support relative extruder coordinates in the near future, at which point the advice and documentation can be just to set your extruder to use relative extruder coordinates.
