Re: Cura 14.01 March 17, 2014 11:37AM |
Registered: 10 years ago Posts: 14,672 |
Re: Cura 14.01 March 17, 2014 01:18PM |
Registered: 10 years ago Posts: 147 |
Re: Cura 14.01 March 17, 2014 01:56PM |
Registered: 10 years ago Posts: 2,472 |
Re: Cura 14.01 March 17, 2014 02:03PM |
Registered: 10 years ago Posts: 2,472 |
Quote
dc42
I would point out that when using absolute extruder positioning, rounding errors will start to accumulate after about 500mm of filament have been extruded, until Cura issues a G92 command to reset the extruder position. This is because the Duet firmware uses 32-bit floating point arithmetic, which has only 7.2 decimal digits of precision, and AFAIR Cura outputs extrusion distances in mm with 5 decimal places. So the print quality may still be better with the plugin.
Re: Cura 14.01 March 17, 2014 02:07PM |
Registered: 10 years ago Posts: 147 |
Re: Cura 14.01 March 17, 2014 03:47PM |
Registered: 10 years ago Posts: 578 |
Quote
dmould
The plugin is still necessary anyway, because Cura puts Z moves in the same command as X & Y moves, and these need to be separated.
Dave
(#106)
// Restrict maximum feedrates; assumes xy overrides e overrides z FIXME?? if(movementType & xyMove) nextMove[DRIVES] = fmin(nextMove[DRIVES], platform->MaxFeedrate(X_AXIS)); // Assumes X and Y are equal. FIXME? else if(movementType & eMove) nextMove[DRIVES] = fmin(nextMove[DRIVES], platform->MaxFeedrate(AXES)); // Picks up the value for the first extruder. FIXME? else // Must be z nextMove[DRIVES] = fmin(nextMove[DRIVES], platform->MaxFeedrate(Z_AXIS));if instead of trickling down to Z it explicitly checked for Z at the beginning and set the maximum feedrate accordingly (ie YES!!! in answer to the question " // Restrict maximum feedrates; assumes xy overrides e overrides z FIXME??" , it would slow down X and Y for that move, but Z would be able to keep up. Something like this:
if(movementType & zMove) nextMove[DRIVES] = fmin(nextMove[DRIVES], platform->MaxFeedrate(Z_AXIS)); else if(movementType & xyMove) nextMove[DRIVES] = fmin(nextMove[DRIVES], platform->MaxFeedrate(X_AXIS)); // Assumes X and Y are equal. FIXME? else if(movementType & eMove) nextMove[DRIVES] = fmin(nextMove[DRIVES], platform->MaxFeedrate(AXES)); // Picks up the value for the first extruder. FIXME?
Re: Cura 14.01 March 17, 2014 04:06PM |
Registered: 10 years ago Posts: 14,672 |
Re: Cura 14.01 March 17, 2014 04:17PM |
Registered: 10 years ago Posts: 578 |
Re: Cura 14.01 March 18, 2014 05:39AM |
Registered: 10 years ago Posts: 57 |
Re: Cura 14.01 March 18, 2014 06:11AM |
Registered: 10 years ago Posts: 1,230 |
Quote
Cash
Hi Paul,
I am sorry, but I think there is something wrong if M-Codes are included in the lines that contains also X Y and Z values. I thought I changed this already!
Please try the attached version of the Plugin, I will commit the changes this evening to Github!
Re: Cura 14.01 March 18, 2014 07:17AM |
Registered: 10 years ago Posts: 147 |
Quote
Cash
Hi Paul,
I am sorry, but I think there is something wrong if M-Codes are included in the lines that contains also X Y and Z values. I thought I changed this already!
Please try the attached version of the Plugin, I will commit the changes this evening to Github!
Cheery, Frank
Edit: Ok, I used a wrong version for the github repository, sorry again!
Re: Cura 14.01 March 18, 2014 07:34AM |
Registered: 10 years ago Posts: 57 |
Re: Cura 14.01 March 18, 2014 07:47AM |
Registered: 10 years ago Posts: 147 |
Re: Cura 14.01 March 18, 2014 08:01AM |
Registered: 10 years ago Posts: 1,230 |
Re: Cura 14.01 March 18, 2014 08:25AM |
Registered: 10 years ago Posts: 57 |
Quote
ormerod168
Quote
Cash
Possibly you changed something inside the start-gcode (added M-Commands)?
Cheers, Frank
If you were referring to me, no change to settings in Cura whatsoever, just substituted old EAtoR.py with the newly posted one and sliced the same file again (zombies.stI)
Erik
Quote
PaulHam
Why would it start to cause problems on Monday night? When I have been using it without problems for a couple of weeks now?
Re: Cura 14.01 March 18, 2014 08:37AM |
Registered: 10 years ago Posts: 2,472 |
Re: Cura 14.01 March 18, 2014 02:02PM |
Registered: 10 years ago Posts: 57 |
Re: Cura 14.01 March 20, 2014 03:48PM |
Registered: 10 years ago Posts: 135 |
Re: Cura 14.01 March 20, 2014 06:32PM |
Registered: 10 years ago Posts: 1,230 |
Re: Cura 14.01 March 21, 2014 08:47PM |
Registered: 10 years ago Posts: 135 |
Re: Cura 14.01 March 22, 2014 05:08PM |
Registered: 10 years ago Posts: 31 |
M203 X6000 Y6000 Z500 E3000 ; Allows 100mm/s speeds
G1 F1800.000 E-1.0 G1 Z500 E3000.00000 M203 X6000 Y6000 G1 F1800.000 E1.0
Re: Cura 14.01 March 22, 2014 06:09PM |
Registered: 10 years ago Posts: 147 |
Re: Cura 14.01 March 22, 2014 07:06PM |
Registered: 10 years ago Posts: 31 |
Re: Cura 14.01 March 23, 2014 05:05AM |
Registered: 10 years ago Posts: 65 |
Re: Cura 14.01 March 23, 2014 04:55PM |
Registered: 10 years ago Posts: 57 |
Re: Cura 14.01 March 24, 2014 12:51PM |
Registered: 10 years ago Posts: 65 |
Re: Cura 14.01 March 24, 2014 06:53PM |
Registered: 10 years ago Posts: 38 |
Re: Cura 14.01 March 24, 2014 07:04PM |
Registered: 10 years ago Posts: 38 |
Re: Cura 14.01 March 25, 2014 12:38PM |
Registered: 10 years ago Posts: 57 |
Re: Cura 14.01 March 25, 2014 05:04PM |
Registered: 10 years ago Posts: 38 |