Posts made by JenPet

@dc42 I have lowered the PA value to 0.04 from 0.08 and now it looks better. I tried the same thing a few days ago but there was no inprovement. I think is was my mistake, sorry. Thank you for support.

@dc42 the two contour lines get thinner and thinner at the end so that there is a gap between them.
Now I try to lower PA value again.

@dc42 I dont know if the quality is equal to RRF 3.3.
I have tested different setting with input shaping an PA.
I tried different PA values, acceleration values, jerk values and speed values but I always get the issue on the picture.
But when I turn PA off, the issue is gone.

@dc42 I'm testing with input shaping.
There is always not enough material at the end of lines. Maybe PA is not working right by deacceleration.

@dc42 I have checked verison but everything is okay. I had also no step errors.

=== Move ===
DMs created 83, segments created 42, maxWait 236506ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 2873, completed moves 2873, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1

@dc42 Thank you but I still get the issue

@dc42 M572 is in the start script of gcode

@dc42 Firmware date is ok

M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.4.0beta2-inputshaping ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2021-08-02 16:26:18

config.g
40x40x40_Cube_140mms0.08.gcode

@dc42 PA is still not working for me.

=== Move ===
DMs created 83, segments created 42, maxWait 206756ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 2700, completed moves 2700, hiccups 0, stepErrors 578, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1

@dc42 I have also tested new version but can't see any improvement

@dc42 I also tested the new version and couldn't see any improvement.
The issue only happens when PA is on. As soon as PA is off, the extrusion is correct.
It's a problem with PA even without input shaping.

=== Move ===
DMs created 83, segments created 42, maxWait 11789ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 3006, completed moves 3006, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1

@dc42 I have tested the updated firmware but see no improvement in my problem with extrusion

@dc42 With Input Shaping mode zvdd @ 55Hz

@dc42 The extrusion issue with PA is still there. A single wall line starts at my testprint at 0.45 and the line ends at 0.30 thickness.

@mikes I am using lower values, I would try it
M566 X300.00 Y300.00 Z24.00 E300.00 P1 ; set maximum instantaneous speed changes (mm/min)

@mikes I tried 7000 to 2000 acceleration but the issue is still there. I have tried zvdd and ei2.

I had a similar issue like in your video. Which jerk values do you use?

I have tried the new uploaded firmware but I have still the issue, that at the end of an move is not enough material when PA is on.
Here M122:
=== Move ===
DMs created 83, segments created 42, maxWait 226006ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 3997, completed moves 3997, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1

@dc42 Hi I still have the issue that the extruder extrudes not enought filament at the end of of a line/move. This happens only when PA (0.08) is enabled. Im printing with input shaper ZVDD F55.0. I thing there is still a bug in firmware. I use Duet2Wifi and extruder is connected to main board.