Print quality
-
Hello guys,
I recently designed and built myself a new printer mostly based on the Ratrig.
Getting it running was pretty easy but getting it tuned isn't as easy as I hoped. The printer is designed to run faster and print more accurately and uses a duet2wifi.On straight parts it is getting pretty good although I get some lines in the layer height that i cant quite explain. Maybe I am getting too precise with that. But looking at corners I have quite some bad print qualities. I posted some pictures below and my config code to make it more clearly because it is hard too explain but the pictures show it nicely. (all printed with 0.6mm nozzle, 0.2 layer height, 100mm/s print speed, wall speed 60mm/s). I just added a acceleratometer too look at vibrations, dont seem too bad with the naked eye but it is possible of course. But I just see those sensors weren't supported at 3.2 so tomorrow I will update my duet. Furthermore my webconsole is giving more problems lately. Suddenly it got problems with wifi signal, M122 gives low dbm of like 70 but like 2 weeks before it worked just fine. I just placed an extra range extender and now the dbm is like 54 so a lot better but still the web console is slow often and uploading files it gets often stuck on the 100% for like a minute. Connecting is a bit better though now.
So my most important question to you guys:
Do you have tips on what part I need to work to print more nicely?
; Configuration file for Duet WiFi (firmware version 3.3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.3.10 on Mon Jan 10 2022 20:32:35 GMT+0100 (Central European Standard Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Wid A6" ; set printer name M669 K1 ; select CoreXY mode M950 S0 C"exp.heater3" ; Duet 2 WiFi/Ethernet M575 P2 B9600 S0 ; USER EDIT add serial communication M955 P0 C"spi.cs4+spi.cs3" ; USER EDIT accel meter ; Network M550 P"3D_Wid" M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0 S1 ; physical drive 0 goes forwards M569 P1 S1 ; physical drive 1 goes forwards M569 P2 S1 ; physical drive 2 goes forwards M569 P3 S1 ; physical drive 3 goes forwards M584 X0 Y1 Z2 E3 ; set drive mapping M350 X16 Y16 Z16 I1 ; configure microstepping with interpolation M350 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z1600.00 E860.00 ; Set steps per mm M566 X450.00 Y450.00 Z12.00 E800.00 ; Set maximum instantaneous speed changes (mm/min) M203 X12000.00 Y12000.00 Z600.00 E8000.00 ; Set maximum speeds (mm/min) M201 X2000.00 Y2000.00 Z20.00 E500.00 ; Set accelerations (mm/s^2) M906 X1100.00 Y1100.00 Z1000.00 E800.00 I30 ; Set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X-50 Y-50 Z0 S1 ; set axis minima M208 X220 Y220 Z250 S0 ; set axis maxima M206 X0 Y42 Z0 ; Endstops M574 X1 S1 P"xstop" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin xstop M574 Y1 S1 P"!ystop" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin ystop M574 Z1 S1 P"!zstop" ; configure switch-type (e.g. microswitch) endstop for low end on Z via pin zstop ;M591 P3 S1 ; filament monitor connected to E0_stop ;M591 D0 P3 C"e0_stop" S1 R70:130 L24.8 E3.0 ; Duet3D rotating magnet sensor for extruder drive 0 is connected to E0 endstop input, enabled, sensitivity 24.8mm.rev, 70% to 130% tolerance, 3mm detection length ;M591 D0 ; display filament sensor parameters for extruder drive 0 ; Z-Probe ; Z-Probe M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch M558 P9 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds G31 P500 X0 Y0 Z3.37 ; set Z probe trigger value, offset and trigger height lower number means higher offset, higher number is lower offset. M557 X15:215 Y15:170 S20 ; define mesh grid ;M558 P7 H3 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed ;M558 P9 C"^zprobe.in" H5 F120 T6000 ; Duet 2 WiFi/Ethernet, DueX2/5 ;M557 X15:215 Y15:195 S20 ; define mesh grid ; Heaters M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0 M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit M307 H0 R0.314 C215.9 D2.97 S1.00 V11.8 M140 H0 ; map heated bed to heater 0 M143 H0 S80 ; set temperature limit for heater 0 to 80C M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0temp M950 J1 C"e1stop" ;USER EDIT, define e1 endstop as pin M950 H1 C"e1heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1 M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M307 H1 R2.877 C131.4:130.2 D5.23 S1.00 V11.9 ; Autotuning heater done in winter 12-1-22 M143 H1 S280 ; set temperature limit for heater 1 to 280C ; Fans M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency M106 P1 S1 H-1 ; set fan 1 value. Thermostatic control is turned off ; Tools M563 P0 D0 H1 F0 ; define tool 0 G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C M581 P1 T0 C0 S0 ; USER EDIT, emergency button ; Custom settings are not defined M501
-
@bierent said in Print quality:
it gets often stuck on the 100% for like a minute.
Please update your firmware to 3.4.1 and see if there is an improvement.
-
@phaedrux
I have just updated to 3.4.1 however my connection issues continue. It also happens with just browsing the webcontrol. Like sending codes in the console can have a delay of like 10 seconds. Also simple G0 commands. Furhtermore the connection falls away often. Sometimes the Duet needs like a minute to reconnect to a wifi after startup. However the dbm seems fine. Just randomly webcontrol also has to reconnect. Next to updating the firmware I also just update the wifi and webcontrol.I did try to add an antena like explained here link text
but that didn't help.My m122 code:
m122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.1 (2022-06-01 21:05:28) running on Duet WiFi 1.02 or later Board ID: 08DGM-9T6BU-FG3SN-6J9F4-3SD6J-TUZMF Used output buffers: 3 of 26 (24 max) === RTOS === Static ram: 23860 Dynamic ram: 77052 of which 48 recycled Never used RAM 11048, free system stack 124 words Tasks: NETWORK(ready,13.2%,237) ACCEL(notifyWait,0.1%,246) HEAT(notifyWait,0.0%,329) Move(notifyWait,0.0%,294) MAIN(running,86.7%,432) IDLE(ready,0.1%,30), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:13:17 ago, cause: reset button or watchdog Last software reset at 2022-08-27 20:10, reason: User, GCodes spinning, available RAM 15172, slot 2 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Step timer max interval 0 MCU temperature: min 28.2, current 32.5, max 32.9 Supply voltage: min 11.7, current 12.1, max 12.2, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0 Driver 1: standstill, SG min 0 Driver 2: standstill, SG min 0 Driver 3: standstill, SG min n/a Driver 4: standstill, SG min n/a Driver 5: Driver 6: Driver 7: Driver 8: Driver 9: Driver 10: Driver 11: Date/time: 2022-08-28 14:50:42 Cache data hit count 4294967295 Slowest loop: 552.78ms; fastest: 0.19ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 1.2ms, write time 79.3ms, max retries 0 === Move === DMs created 83, segments created 3, maxWait 482945ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 21, completed 21, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 6], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 Heater 0 is on, I-accum = 0.3 Heater 1 is on, I-accum = 0.3 === GCodes === Segments left: 0 Movement lock held by null HTTP is idle in state(s) 0 Telnet is idle in state(s) 0 File is idle 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 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty === Network === Slowest loop: 199.85ms; fastest: 0.08ms Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 1 of 8 - WiFi - Network state is active WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 1 WiFi firmware version 1.26 WiFi MAC address 84:f3:eb:83:42:df WiFi Vcc 3.39, reset reason Turned on by main processor WiFi flash size 4194304, free heap 25280 WiFi IP address 192.168.2.164 WiFi signal strength -54dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 2 4 0 0 0 0 0 0
-
@bierent said in Print quality:
I did try to add an antena like explained here link text
but that didn't help.So you've modified the wifi module to add an antenna?
-
@phaedrux
Yes, I tried it to get better wifi. Before it was also bad.
The board today with the new firmware also gives this popup when it's first connected.Failed to connect to 192.168.2.164 Unexpected token '<', "
-
Where do you see that message?
-
@phaedrux
On the bottom when starting up, although it does disappear quickly.
-
Maybe I better make a new topic with the right topic name.
-
@bierent said in Print quality:
Maybe I better make a new topic with the right topic name.
Not a bad idea.
I would also try refreshing your firmware and DWC files by uploading the full 3.4.1 zip file again.
https://github.com/Duet3D/RepRapFirmware/releases/download/3.4.1/Duet2and3Firmware-3.4.1.zip