Random underextrusion Problem
-
@Veti ok, I increase extruder gear pressure
Filament used: extrudr durapro asa
Nozzle 250
Bed 100 -
@Frederik said in Random underextrusion Problem:
Filament used: extrudr durapro asa
asa is more difficult to print.
see
https://www.matterhackers.com/articles/how-to-succeed-when-3d-printing-with-asa-filament -
@Veti thanks for this link
-
@Veti
Interesting article!The artefacts occurring again. I have increased the extruder gear pressure until the end of the screw
-
@Frederik said in Random underextrusion Problem:
Is it possible to create secure zones where the print head would collide with something?for example: if I home y and the print head is at X0 my spindles would collide with my bltouch. So I want a zone perhaps 50x30 where the tool head automatically goes around or alters the X position +50??
no
for filamant config see
https://duet3d.dozuki.com/Wiki/Filaments -
@Veti the underextrusion occurs again. I have increased the pressure until the end of the screw of an original bmg.
-
do you have pressure advance? RRF 3.2 has communication issues with the LC1 especially with pressure advance activated. You may try to install the alpha version 3.3
-
@matt3o No Pressure Advance, its defined in my config with 0.000
I was trying to update to 3.3 but than i got massive DWC reconnect Problems and had to flash a new pi image and reset the mainboard firmware via usb
-
@Frederik can you try to momentarily connect the extruder motor to the main duet3 board and see if it works that way?
-
@matt3o that would be no problem. i got a spare cable thats long enough
-
Is your bed PID tuned? Perhaps it's the cyclical heating and cooling expand contract on the bed causing the Z gap to change.
-
@Phaedrux it is PID Tuned to 100 degree C. The same temp I was printing. The bed is a 4mm aluminium plate with a 4mm borosilicate plate on top. I let the temperatures stabilize bevor printing perhaps 15 to 20 min. Then a g32 +g29
Taper is set to 0, so it should be applied to the hole print.I also print in a heated chamber with 70 C
-
-
I am running now the first test print on 3.3 beta + LC1
here is a m122 from main and Toolboard at the start of the print
m122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.3beta running on Duet 3 MB6HC v1.01 or later (SBC mode) Board ID: 08DJM-956BA-NA3TN-6J9DL-3S46S-99AUT Used output buffers: 1 of 40 (11 max) === RTOS === Static ram: 149784 Dynamic ram: 60720 of which 204 recycled Never used RAM 139964, free system stack 139 words Tasks: Linux(ready,119) HEAT(blocked,299) CanReceiv(blocked,861) CanSender(blocked,346) CanClock(blocked,326) TMC(blocked,16) MAIN(running,922) IDLE(ready,20) Owned mutexes: HTTP(MAIN) === Platform === Last reset 00:09:29 ago, cause: software Last software reset at 2021-01-31 18:05, reason: User, none spinning, available RAM 139964, slot 0 Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task Linu Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 Aux1 errors 0,0,0 MCU temperature: min 48.8, current 49.4, max 49.6 Supply voltage: min 24.0, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.1, current 12.1, max 12.1, under voltage events: 0 Driver 0: position 64448, ok, reads 45610, writes 0 timeouts 0, SG min/max 0/538 Driver 1: position 14935, ok, reads 45610, writes 0 timeouts 0, SG min/max 0/324 Driver 2: position 1720, standstill, reads 45610, writes 0 timeouts 0, SG min/max 0/93 Driver 3: position 0, standstill, reads 45610, writes 0 timeouts 0, SG min/max 0/111 Driver 4: position 0, standstill, reads 45610, writes 0 timeouts 0, SG min/max 0/95 Driver 5: position 0, standstill, reads 45610, writes 0 timeouts 0, SG min/max not available Date/time: 2021-01-31 18:14:39 Slowest loop: 218.06ms; fastest: 0.02ms === Storage === Free file entries: 10 SD card 0 not detected, interface speed: 37.5MBytes/sec SD card longest read time 0.0ms, write time 0.0ms, max retries 0 === Move === DMs created 125, maxWait 111ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 6027, completed moves 6009, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state 3 === AuxDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = 2 -1 -1 -1 Heater 0 is on, I-accum = 0.1 === GCodes === Segments left: 1 Movement lock held by null HTTP* is doing "M122" in state(s) 0 Telnet is idle in state(s) 0 File* is doing "G1 F3000 X255.895004 Y155.307999 E0.221520" in state(s) 0 USB is idle in state(s) 0 Aux is idle in state(s) 0 Trigger* is idle in state(s) 0 Queue* is idle in state(s) 0 LCD is idle in state(s) 0 SBC is idle in state(s) 0 Daemon is idle in state(s) 0 Aux2 is idle in state(s) 0 Autopause* is idle in state(s) 0 Code queue is empty. === Filament sensors === Extruder 0: no data received === CAN === Messages queued 3220, send timeouts 0, received 3083, lost 0, longest wait 7ms for reply type 6029, peak Tx sync delay 222, free buffers 48 (min 45) === SBC interface === State: 4, failed transfers: 0 Last transfer: 1ms ago RX/TX seq numbers: 22987/22987 SPI underruns 0, overruns 0 Number of disconnects: 0, IAP RAM available 0x2d584 Buffer RX/TX: 400/1864-0 === Duet Control Server === Duet Control Server v3.2.0 File: Buffered code: G1 F3000 X255.895 Y155.308 E0.22152 Buffered code: G1 X255.965 Y155.378 Buffered code: G0 F7200 X254.977 Y154.986 Buffered code: G1 F3000 X258.423 Y151.54 E0.14912 Buffered code: G1 X258.493 Y151.47 Buffered code: G0 F7200 X259.331 Y149.693 Buffered code: G1 F3000 X254.199 Y144.56 E0.2221 Buffered code: G1 X254.129 Y144.49 Buffered code: G0 F7200 X254.158 Y144.517 Buffered code: G0 X254.109 Y146.803 Buffered code: G1 F3000 X261.14 Y139.772 E0.30426 Buffered code: G1 X261.21 Y139.702 Buffered code: G0 F7200 X261.201 Y139.702 Buffered code: G0 X258.481 Y139.792 Buffered code: G1 F3000 X261.14 Y142.45 E0.11504 Buffered code: G1 X261.21 Y142.52 Buffered code: G0 F7200 X261.201 Y142.52 Buffered code: G0 X261.14 Y144.297 Buffered code: G1 F3000 X260.009 Y145.428 E0.04894 Buffered code: G0 F7200 X259.64 Y145.476 Buffered code: G1 F3000 X256.34 Y142.176 E0.1428 Buffered code: G1 X256.27 Y142.106 Buffered code: G0 F7200 X256.299 Y142.133 Buffered code: G0 X259.64 Y145.797 Buffered code: G1 F3000 X256.746 Y148.691 E0.12523 Buffered code: G1 X256.676 Y148.761 Buffered code: G0 F7200 X256.697 Y148.759 Buffered code: G0 X256.613 Y149.748 Buffered code: G0 X256.045 Y150.932 Buffered code: G1 F3000 X259.02 Y153.908 E0.12876 Buffered code: G1 X259.09 Y153.978 Buffered code: G0 F7200 X259.349 Y155.139 ==> 1472 bytes Code buffer space: 2232 Configured SPI speed: 8000000 Hz Full transfers per second: 41.83 Maximum length of RX/TX data transfers: 2808/1616 File /opt/dsf/sd/gcodes/bltouch.gcode is selected, processing
M122 b121
m122 b121 Diagnostics for board 121: Duet TOOL1LC firmware version 3.3beta (2021-01-21 11:34:37) Bootloader ID: SAMC21 bootloader version 2.2 (2021-01-16b1) Never used RAM 3620, free system stack 0 words Move 90 HEAT 91 CanAsync 66 CanRecv 74 CanClock 66 TMC 56 MAIN 197 AIN 62 Last reset 00:44:52 ago, cause: power up Last software reset time unknown, reason: OutOfMemory, available RAM 15632, slot 1 Software reset code 0x01c0 ICSR 0x00000000 SP 0x20003578 Task MAIN Freestk 747 ok Stack: 20000d10 00011ceb 20000d10 0001df61 00000000 00004008 20000d10 0001ded5 20000d0c 00004000 a5a5a5a5 a5a5a5a5 00000000 0001dd9d 00004000 00018b21 a5a5a5a5 00018b3d a5a5a5a5 00011b39 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 Driver 0: position 331894, 859.0 steps/mm, standstill, SG min/max 0/496, read errors 0, write errors 0, ifcnt 19, reads 12002, writes 0, timeouts 0, DMA errors 0, steps req 109046 done 109046 Moves scheduled 6688, completed 6688, in progress 0, hiccups 0, step errors 0, maxPrep 498, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0 Peak sync jitter 4, peak Rx sync delay 214, resyncs 0, no step interrupt scheduled VIN: 23.5V MCU temperature: min 41.6C, current 66.4C, max 68.0C Ticks since heat task active 204, ADC conversions started 2684508, completed 2684507, timed out 0 Last sensors broadcast 0x00000002 found 1 210 ticks ago, loop time 0 CAN messages queued 3626, send timeouts 0, received 4384, lost 0, free buffers 36, min 36, error reg 0 dup 0, oos 0, bm 0, wbm 0 === Filament sensors === Interrupt 4 to 49us, poll 9 to 706us Driver 0: pos 5.74, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0
-
Did it help with theunder extrusion?
-
@Phaedrux i cant tell at the moment. with the new firmware my heater is going crazy
after 2-3 Minutes into the Print the Temp sensor starting to jump from 250 to 18-25 °C and my toolfan starts and stops accordingly to the temperature... when under 50°C it stops , above it starts.
-
Sounds like a bad connection on the thermistor
-
that was my first idea too, but when no print is running the temp is stable
-
@Frederik said in Random underextrusion Problem:
but when no print is running the temp is stable
Yes, because when no print is running, the cables are stationary.
-
@Phaedrux definetly not the cables
i resetted the Toolboard with the 2 knobs and restarted the same file:
absolute stable, nothing touched on the cables