Well I think I found the main culprit, after going through and tweaking all my accels and retraction settings, at least in PrusaSlicer.
I had "Only retract when crossing perimeters" turned on, which caused a bunch of my oozing.

But getting my acceleration and travel moves better tuned also proved benificial.
I found I could bump up all the accelerations by quite a bit, as well as the travel move speed which improved stringing as well.

Still have slight gaps inbetween the gyroid layers, but that could be because it's only 5% infill.
Thanks for your input Phaedrux.

I'm not really sure what I am doing wrong.
After fixing a bad thermistor/hot end connection, I thought I was back on track getting decent print quality.
I just changed nozzles from 0.4 to 0.6 mm on a print (layer height kept the same) and the quality was drastically worse.
On the 0.4 mm nozzle prints I was getting some striations, which I thought was strange, but could live with it. With the 0.6 mm nozzle prints, it looks like layer shifting but everything physical with the printer is in order (belts are tensioned, I don't notice skipping, etc).
The blobbing is me still needing to get retraction tuned properly, but would appreciate any advice.
0.6mm Nozzle


0.4mm nozzle, same object

Printer base is a Seemecnc RostockMaxV2 (Delta)

RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.0 or 1.01
Board ID: 08DAM-999TL-MQ4S8-6J1FL-3SN6S-9QBRX

Config here:

; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.0 on Thu Aug 05 2021 19:10:57 GMT-0700 (Pacific Daylight Time)

; General preferences
G90                                               ; send absolute coordinates...
M83                                               ; ...but relative extruder moves
M550 P"M-Automation"                              ; set printer name
M665 R138.543 L290.8 B140 H592.5 X0.714 Y1.066 Z0.000     ; Set delta radius, diagonal rod length, printable radius and homed height
M666 X-0.353 Y-0.422 Z0.775 A-0.48 B0.30          ; put your endstop adjustments here, or let auto calibration find them

; Network
M552 S1                                           ; enable network
M586 P0 S1                                        ; enable HTTP
M586 P1 S0                                        ; disable FTP
M586 P2 S0                                        ; disable Telnet

; Drives
M569 P0 S0                                        ; physical drive 0 goes backwards
M569 P1 S1                                        ; physical drive 1 goes forwards
M569 P2 S0                                        ; physical drive 2 goes backwards
M569 P3 S1                                        ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3                                  ; set drive mapping
M350 X16 Y16 Z16 E16 I1                           ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z80.00 E416.78859                  ; set steps per mm
M566 X1000.00 Y1000.00 Z1000.00 E3000.00 P1         ; set maximum instantaneous speed changes (mm/min)
M203 X15000.00 Y15000.00 Z15000.00 E3000.00       ; set maximum speeds (mm/min)
M201 X8300.00 Y8300.00 Z8300.00 E10000.00       ; set accelerations (mm/s^2)
M906 X1400 Y1400 Z1400 E1400 I30                  ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                           ; Set idle timeout

; Axis Limits
M208 Z-0.2 S1                                     ; set minimum Z

; Endstops
M574 X2 S1 P"xstop"                               ; configure active-high endstop for high end on X via pin xstop
M574 Y2 S1 P"ystop"                               ; configure active-high endstop for high end on Y via pin ystop
M574 Z2 S1 P"zstop"                               ; configure active-high endstop for high end on Z via pin zstop

; Z-Probe
M558 P8 C"^zprobe.in" H2.5 F300:150 A015 S0.02 T15000           ; set Z probe type to switch and the dive height + speeds
G31 P1000 X0 Y0 Z-0.04                             ; set Z probe trigger value, offset and trigger height
M557 R120 S15                                     ; define mesh grid

; Heaters
M308 S0 P"duex.e4temp" Y"thermistor" T95205 B3285 ; configure sensor 0 as thermistor on pin duex.e4temp
M950 H0 C"bedheat" T0                             ; create chamber heater output on bedheat and map it to sensor 0
M307 H0 A19.0 C18.4 D1.6 S1.00 V12.7 B0           ; disable bang-bang mode for the chamber heater and set PWM limit
M141 H0                                           ; map chamber to heater 0
M143 H0 S105                                      ; set temperature limit for heater 0 to 105C
M308 S1 P"e0temp" Y"thermistor" T108341 B4527     ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1                              ; create nozzle heater output on e0heat and map it to sensor 1
M307 B0 R2.201 C212.1 D6.73 S1.00 V12.7			  ; disable bang-bang mode for heater  and set PWM limit
M143 H1 S280                                      ; set temperature limit for heater 1 to 280C
M308 S2 P"e1temp" Y"thermistor" T108341 B4527     ; configure sensor 2 as thermistor on pin e1temp
M950 H2 C"e1heat" T2                              ; create bed heater output on e1heat and map it to sensor 2
M307 H2 A190.3 C949.5 D1.2 S1.00 V12.8 B0         ; enable bang-bang mode for the bed heater and set PWM limit
M140 H2                                           ; map heated bed to heater 2
M143 H2 S125                                      ; set temperature limit for heater 2 to 125C
M308 S3 P"bedtemp" Y"thermistor"  A"Chamber Temp"  T103972 B10191 C4.825776e-7 R4700                     ; set thermistor + ADC parameters for chamber thermistor

; Fans
M950 F0 C"fan0" Q50000                            ; create fan 0 on pin fan0 and set its frequency
M106 P0 C"CPU Fan" S0.25 H0 T30                   ; set fan 0 name and value. Thermostatic control is turned on
M950 F1 C"fan1" Q0                                ; create fan 1 on pin fan1 and set its frequency
M106 P1 C"Hot End" S1 H1 T45                      ; set fan 1 name and value. Thermostatic control is turned on
M950 F2 C"fan2" Q500                              ; create fan 2 on pin fan2 and set its frequency
M106 P2 C"Chamber Heater" S0.25 H1 T35            ; set fan 2 name and value. Thermostatic control is turned on

; 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

; Custom settings
;CPU Temp compensation
M912 P0 S-2.4
;Driver Temp Flag
M305 P101 S"Drivers"

;Retraction
M207 S2.0 R0.10 F6000 T4500 Z0
M572 D0 S0

; Miscellaneous
M501                                              ; Load saved parameters from non-volatile memory
T0                                                ; Select first tool

Let me know if it is useful to have the gcode files, as they are ~12 mb in size, so too large to upload directly to the forum.

@chrishamm said in DWC2 Uploading large Gcode files results in network error:

Please try to upgrade to DWC 2.0.5. The new version no longer relies on the "axios" library for HTTP calls but uses native AJAX calls instead, so I hope this will solve your problem.

I've haven't been able to test it for a while, but I've since upgraded to 2.0.7 and while I do have a higher success rate, the odd time the upload still fails.

I've attached 3 wireshark traces of failed uploads here: https://1drv.ms/u/s!AgTPtiCYHi3hh8oNZ5d6wYz7VkdVzQ?e=pKpMUd

I seem to be unable to upload larger >3 MB with DWC2, I always get a network error.
I have no issues uploading the same file when I revert to DWC1.

I'm running 2.05 (just went from 2.04 in case that was the problem) but I have the same issues.
I know the wifi signal strength is on the 'low' side, but if I have no issues uploading in DWC1, then why can't I upload with DWC2?

Board: Duet WiFi 1.0 or 1.01
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 2.05 (2019-12-13b1)
Duet WiFi Server Version: 1.23

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05 running on Duet WiFi 1.0 or 1.01
Board ID: 08DAM-999TL-MQ4S8-6J1FL-3SN6S-9QBRX
Used output buffers: 1 of 24 (10 max)
=== RTOS ===
Static ram: 25712
Dynamic ram: 92696 of which 304 recycled
Exception stack ram used: 272
Never used ram: 12088
Tasks: NETWORK(ready,628) HEAT(blocked,1232) MAIN(running,3800) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:07:28 ago, cause: software
Last software reset at 2020-01-08 11:06, reason: User, spinning module GCodes, available RAM 12396 bytes (slot 2)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 12.0MBytes/sec
SD card longest block write time: 166.0ms, max retries 0
MCU temperature: min 32.0, current 32.6, max 34.0
Supply voltage: min 12.7, current 12.8, max 13.0, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2020-01-09 10:32:44
Cache data hit count 1403011763
Slowest loop: 53.11ms; fastest: 0.06ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = 2 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 2 allocated, 0 in use
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
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 189.51ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
- WiFi -
Network state is running
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.23
WiFi MAC address 5c:cf:7f:2b:eb:38
WiFi Vcc 3.38, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 25936
WiFi IP address 192.168.0.56
WiFi signal strength -67dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0

I saw that in the above M122, the SD card longest block write time: 166.0ms is pretty long, but I did a few subsequent M122 and the longest block write time is 0ms

Well I think I found the main culprit, after going through and tweaking all my accels and retraction settings, at least in PrusaSlicer.
I had "Only retract when crossing perimeters" turned on, which caused a bunch of my oozing.

But getting my acceleration and travel moves better tuned also proved benificial.
I found I could bump up all the accelerations by quite a bit, as well as the travel move speed which improved stringing as well.

Still have slight gaps inbetween the gyroid layers, but that could be because it's only 5% infill.
Thanks for your input Phaedrux.

@Phaedrux said in Infill slight underextrusion:

Do you notice the same thing on other infill patterns that don't have unsupported overhangs? Like grid, or cubic?

I tried grid, and at first glance it is better, but where the extruder starts the grid pattern there is still underextrustion, but it is much harder to see. And hard to photograph:

But I think the issue is probably with my retraction settings. I did go through the 'wizard' in KISSlicer, but it still needs tweaking. Do you happen to have a link to a good guide for that? I never spotted the guide for the volumetric extrusion but it's much easier to follow than others I found.

@Phaedrux said in Infill slight underextrusion:

@jrjones88 said in Infill slight underextrusion:

I had found the max volumetric flowrate for my hot end to be ~7.5mm^3/sec

PrusaSlicer allows you to set a volumetric speed limit on the speeds tab. This would cap your movement speeds to automatically stay within the limit.

I had forgotten I had set that a while ago in Prusaslicer...

Printed it out again with the max speeds set to 45mm/sec, and I guess the volumetric speed limit was in play for the previous prints as I can't really see too much of a difference.

Thanks!
I had found the max volumetric flowrate for my hot end to be ~7.5mm^3/sec (long bowden) but hadn't calculated the max speeds for that before.

Would make my max speed 44.6 mm/s so I'll try dropping the speeds a bit.

I always thought I was printing slow because other Rostock users self reported speeds of up to 100mm/sec.

I can't seem to get the infill in my prints to come out nicely. They always are a bit underextruded.
I've calibrated the extruder, and the solid layers and perimeters print out as I expect.

Just on infill, and I've noticed it on support structures a bit too, it seems to be underextruding.
I've used PrusaSlicer, KISSlicer, Cura, and I seem to get the same results.
I thought that the issue was adaptive layer heights, but I still get it a little bit with that feature turned off.

Any tips/ideas of how to improve this?
I thought I had my speeds on the conservative side (45 mm/s perimeters, 60mm/s infill)
Some pictures:

Gcode of the print:Circle Test.gcode
Printer settings: config.g
Duet Firmware:
Board: Duet WiFi 1.0 or 1.01
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 2.04RC1 (2019-07-14b1)
Duet WiFi Server Version: 1.23

My printer is a Rostock Max V2

@exerqtor
Where I have my printer connected to is similar, and I'm not getting any issues uploading, so I would say that -70dBm is good enough.

I have -71dBm connected through a Ubiquiti AP-AC-LR
Unifi reports a -65 dBm signal and a TX rate of 65 Mbps
I have speeds of around 200-250 kb/s as well, which I had before too located closer to an AP.

FYI my phone connected to the same AP has a self reported signal of -65dBM and a TX rate of 130 Mbps, while Unifi reports it has a -82 dBm signal and TX rate of 234 Mbps. My phone is about 4 meters further away from the AP.

@wyvern said in Yet another cast aluminum plate topic...:

Not to take over the thread, but has anyone used 3M 468MP to attach a mirror to an aluminum bed?

I hate hate hate hate hate clips or the likes, they get in the way and reduce build area.

I restrain my glass plate in 3 directions from the side. I still need to modify (improve) it since the heat cycling loosens the screws over time, but the aluminum is flat enough that after polishing it, if I lift only the glass, the aluminum sticks to it for a few seconds and is lifted up as well.
I usually have to slide the glass plate off the aluminum plate to separate them.
I was using the binder clips before but found that it warped the glass slightly because they clamped at the very edge of the glass.