@jay_s_uk

That was it !
Thanks for pointing me to it.

Im still quite a newbie in this realm and i guess the amount of variables are getting to me

Backstory is I have a zesty nimble, which worked amazing but had 2 issues I cannot solve

1. Ripples in the surface finish - Company is still working on a fix
2. blobs at the end of a layer creating terrible Z seam scars

Tried all the ideas such as coast and wipe, but they have their own issues such as only available in some slicers, cannot be used with firmware retraction, etc.

Pressure advance by the sounds of it should eliminate the blobs at end of layer, but any attempt to use PA with a nimble due to its required low jerk values caused my prints to slow to about 3x the time. Was painful to watch.
Although, with the nimble I was able to get a great calibration part from the above enclosed script.

With the nimble, the calibration part has easily discernible reversing thick areas, and one can find the "best" setting of 0.12, but pressure advance was unusable for me in combination with the nimble.

So I order a Bondtech BMG and use a capricorn bowden tube of about 650mm paired with an E3D 0.9 degree stepper.

Now i get the Esteps all setup at E808, run some retraction calibration parts, and i still get blobs due to pressure at the end of a layer.
Run the above scripts on a Pressure Advance test and..... The results do not make sense to me.

Before the extruded line ever gets to an optimal state, the extrusion is messed up. It gets to the point where nothing is coming out of the nozzle at all. I was at 5-100 print speed so ran again at 20-80 which is the speeds I actually print at (E3D volcano, 0.6mm X nozzle)
And again the part never gets to the optimal PA value without the PA settings making the filament retract so much it doesn't print.

What am i doing wrong? Any suggestions?

Duet Wifi, Smart Effector, newest firmware, Delta printer based smilar to DC42's large kossel

Config is as follows :
M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
M92 X200 Y200 Z200 E808; Set steps per mm original
M566 X1200 Y1200 Z1200 E2000 ; Set maximum instantaneous speed changes (mm/min)
M203 X18000 Y18000 Z18000 E3600 ; Set maximum speeds (mm/min)
M201 X1000 Y1000 Z1000 E3000 ; Set accelerations (mm/s^2)
M906 X1000 Y1000 Z1000 E900 I30 ; Set motor currents (mA) and motor idle factor in per cent

@jay_s_uk

Probably, so I just removed the daemon.g completely and its running fine.
When I get time I'll try to find why the G4 S1 is causing a pause instead of just reloading macro, its also recommended in the documentation to have such a command.

@dc42

In my post I mentioned most of what you suggest.

I have swapped out the thermistor/heater for a backup, no change.

at room temp it matches the temp of the 2 other thermistors in the system, all 3 read 19.2 C.

Yes I agree a handheld laser thermometer is not great, but it happens to read the nozzle temp accurately at room temp, and when I set it to 160 it only reads 75. its such a deviation that I think any inaccuracy is accounted for.

I also already switched thermistor inputs to E3 on the duex board, no change.

I agree that clogs happen by lack of heat, but I added a brand new, unused nozzle, and cannot get hand fed filament to come out. The nozzle is not heating to melt temp even though the UI on both panel due and dwc says its at temp.

It was working, it stopped working, my config didn't change. Asking if the board itself which is now old could possibly be the cause,

Is it possible my Duet wifi is failing and causing my thermistor issues ?

I have a voron 2.4, running on a duet wifi + duex5, with a hartk toolhead board and a revo PZ hotend.
I was printing asa at 260 and HF obsidian nozzle clogged. Put in a new non hf nozzle, and was using sun cleaning filament to make sure it was clean before printing and it clogged.

I think the nozzle is not actually getting to the temp it's stating. So it's clogging because its only at say 210 instead of 260.

I changed the revo 60w heater to my old 40w heater thinking the thermistor was at fault, same thing. Heat to 260, can't get any flow, just a small amount coming out like it's barely hot enough. Now when I heat to 260 I get heater faults. I did rerun pid.

I can't believe I had 2 thermistors fail right after one another with minutes, so suspect it may be the Duet Wifi board. Is that possible ? Would moving the sensor from E0 to E1 help ?

Edit : using an infrared thermometer I measure 76c on the nozzle when I have the hotted set to 160c, so im only getting about half the temp.

Edit 2: moved HE thermistor to E3 on duex board, no change. I read a 75C nozzle when set to 160C. At room temp it reads correctly. The bed temp, he temp and chamber temp thermistors all read the same at room temp. the bed and chamber read correctly at printing temps. It's just the HE only gets to half what I have it set for, even though it shows its at full temp. Im stumped.....

Edit3: measured resistance of the 40w heater/thermistor is 119 K ohms at 21C.

Config :
;; Hotend
;RRF 3.x
M308 S1 P"e0temp" Y"thermistor" T100000 B4725 C7.06e-8 ; sensor 1
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M143 H1 S280 ; set temperature limit for heater 1 to 280C
M307 H1 R3.691 K0.426:0.000 D1.81 E1.35 S1.00 B0 V24.1 ; Revo 40W-

m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.3 (2024-09-18 11:25:32) running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DDM-9FAM2-LW4SD-6JTF0-3SJ6J-TLZHY
Used output buffers: 3 of 26 (18 max)
=== RTOS ===
Static ram: 23376
Dynamic ram: 75984 of which 112 recycled
Never used RAM 11080, free system stack 116 words
Tasks: NETWORK(2,nWait 6,13.8%,217) HEAT(3,nWait 5,0.1%,168) Move(4,nWait 5,0.0%,300) DUEX(5,nWait 5,0.0%,23) MAIN(1,running,86.1%,742) IDLE(0,ready,0.1%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:21:10 ago, cause: software
Last software reset at 2024-12-15 12:19, reason: User, Gcodes spinning, available RAM 11728, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 25.9, current 33.3, max 34.6
Supply voltage: min 23.9, current 24.2, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/25, heap memory allocated/used/recyclable 2048/1120/800, gc cycles 0
Events: 1 queued, 1 completed
Driver 0: standstill, SG min 0
Driver 1: standstill, SG min 0
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5: standstill, SG min 0
Driver 6: standstill, SG min 0
Driver 7: standstill, SG min 0
Driver 8: standstill, SG min 0
Driver 9: standstill, SG min n/a
Driver 10:
Driver 11:
Date/time: 2024-12-15 12:48:02
Cache data hit count 4294967295
Slowest loop: 31.37ms; fastest: 0.18ms
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.4ms, write time 32.5ms, max retries 0
=== Move ===
DMs created 83, segments created 3, maxWait 533242ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
no step interrupt scheduled
Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
=== DDARing 0 ===
Scheduled moves 29, completed 29, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 5], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Movement locks 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
Q0 segments left 0
Code queue 0 is empty
=== Filament sensors ===
check 0 clear 5118572
Extruder 0 sensor: ok
=== DueX ===
Read count 1, 0.05 reads/min
=== Network ===
Slowest loop: 77.57ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
=== WiFi ===
Interface state: active
Module is connected to access point
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 2.1.0
MAC address 5c:cf:7f:a4:a1:64
Module reset reason: Turned on by main processor, Vcc 3.41, flash size 4194304, free heap 37948
WiFi IP address 192.168.2.232
Signal strength -54dBm, channel 6, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

@jay_s_uk

Probably, so I just removed the daemon.g completely and its running fine.
When I get time I'll try to find why the G4 S1 is causing a pause instead of just reloading macro, its also recommended in the documentation to have such a command.

Recent upgrades to my printer, but same board and firmware as previous.

Slicer is Superslicer Version: 2.4.58.5, which I used prior also with no issues.

Doing parts now I get blobs and zits on my part, even in vase mode
I can watch it in vase mode with no layer changes or retractions and it pauses/stutters whenever it's doing arcs or circles.

Issue is very similar to https://youtu.be/Hvw3DrVAeTA

edit :
https://youtu.be/ZM1MYbsC5Aw
this is the same problem, and zits on parts, except I have power recovery off so his solution does not work.
I also reduced resolution to 0.5mm in slicer, so that round egg shape is now low poly looking, but same problem,

Is there a setting with RRF that helps this situation or is this purely slicer based ?

System:
Board: Duet 2 WiFi (2WiFi)
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.3+ (2022-10-06)
Duet WiFi Server Version: 1.27

Edit 2: Turns out to be related to daemon.g
When I did my upgrades I added neopixels to printhead which change based on different input status.
Have not figured out just what in the macros was causing the pauses.
Daemon was only 2 lines G4 1 , and a P98 to run the led macro.

@jay_s_uk

That was it !
Thanks for pointing me to it.

@Phaedrux

M122 shows the firmware is 3.4.3 but does not show the wifi version. I only have paneldue to connect and it doesnt seem to show all the info

Duet 2 wifi
was on 3.3, with wifi server 1.26 and DWC 3.3.0

updated by uploading Duet2and3Firmware-3.4.3.zip in DWC, let it upload, pressed yes to update firmware, and after it uploaded, updated, and rebooted it no longer can connect.

Through paneldue i can see its upgraded to 3.4.3
it connects to wifi and gives me an ip address, i can ping the ip address.
i cannot access DWC via name.local or via IP address.
I have removed SD card, deleted www folder and replaced with the contents of DuetWebControl-SD.zip

Still cannot connect to DWC on multiple bowsers tried.

Any suggestions ?

in the patch notes it states :
"If you configure a Z probe using multiple M558 commands instead of a single one, you must make sure that only the first one has a P parameter. This is because M558 with a P parameter now sets default values before processing the other parameters of the M558 command."

My Config file has the following. :

; Z probes
M558 K0 P8 C"^zprobe.in" T18000 A5 H5 R0.2 S0.01 F600 B1 ;
G31 K0 P500 X0 Y25 Z2.557 ; inductive probe offset,

M558 K1 P8 C"^zstop" T18000 H5 R0.2 S0.005 F120 A10 B0 ;
G31 K1 P500 X0 Y0 Z0.730 ; Z switch offset

If on the second M558 command I remove the P8, when I do a G30 I get an error message of
"Error: in file macro line 47: G30: Z probe 1 not found"

So I do not understand the patch note of only having one with a P parameter, or am I doing something incorrect in my M558 commands ?

Cheers, thanks !
That was it

uploaded dwc3.11 on my duet 2, and now the DWC is a blank white page.
Tried 2 different browsers, nada.

I used the github page, download DWC Zip, it downlaoded as DuetWebControl-master.zip
Used DWC to upload, and now all white, when i connect via name or ip