I further checked the setup & realize that the PT1000 sensor is 30mm in length with 4mm diameter. But the Biqu extruder slot for hotend & sensor is of 15mm.
This means half the sensor is outside sensor slot & not in contact with hotend.
Shouldn't this affect the PID learning & heater behaviour?
@droftarts : I understand your suggestion; for abs I might need 260degC.However, if I want to claim 300degC of extruder, I must tune it to that max limit. If I just tune to 210degC, then at times it will struggle to even reach 280/290degC . I plan to include chamber heater too.
My only concern is to understand this tuning well, so that there are not heater warnings/faults ., other wise on power up this predicted warning generates a doubt to user.
(I don't face this with bondtech set up, but with biqu extruder only).
NOTE: I user Duet 2 wifi board.
@dc42 :
Increasing R parameter, in my case, does not change the overshoot problem.
I tried decreasing R parameter, by 20-40%, then overshoot only reduces by 2 degC. i.e. earlier overshoot was 14degC, then it changed to 12degC, but cooling rate reduced.
What to do further , any suggestion?
Printer1:
M307 H1 R1.991 K0.759:0.048 D11.88 S1 B0 V23.9 E1.35 P7.5 I0.120 D44
This printer, does not give any warning on power up pf prediction, though overshoots at first by 14degC, but settles & then on fan on, temperature drop seen is just 4-5degC but manages reach target.
Printer2, same extruder, Biqu.
M307 H1 R2.457 K0.290:0.132 D11.88 S1 B0 V24.1 E1.35 P5.1 I0.0.085 D43.8
This printer, on power on, gives predicted temperature warning (511degC), temperature overshoots only by 6degC, but settles & on fan on, temperature drop behaviour is same as that of printer 1.
Why same sensor & heater type in same extruder type, behave so differently ? One overshoots only by 6degC, but other overshoots by 14degC.
note: Both tuned at same ambient, using "M303 T0 S300".
For manual adjustment, it brings me back to the 1st post in this thread. Can you answer the following for me to try :
following links,
David suggests to increase 'R' paramater.
https://forum.duet3d.com/topic/31038/overshoot-and-really-unstable-hotend-temperature/2?=1721909615387
https://forum.duet3d.com/topic/31038/overshoot-and-really-unstable-hotend-temperature/2?=1721909615382
But literature says, to decrease in case of overshoot:
https://docs.duet3d.com/User_manual/Connecting_hardware/Heaters_tuning
Can you please confirm whether to increase or decrease "R" value ?
Thanks.
I tried this "M303 T0 S300".
values after tune : M307 H1 R1.991 K0.759:0.048 D11.88 S1 B0 V23.9 E1.35.
On power up, prediction warning no longer appears.
On setting 210degC for PLA, temperature still, at first overshoots by 14degC but stabilizes after 2 mins. And on switching on Cooling fan, temperature drops by 5degC but heater manages to pick up. (in a nutshell, the I no longer get any heater warnings.
The question I have is :
M303 H1 S300 P1
If I keep cooling fan at 0% fan during autotune, then I get the learned values as below & temperature with these values overshoots only by 6degC. BUT, the moment FAN starts, temperature drops by 5degC & I get a warning that predicted temperature can go beyond 500degC/700degC at times.
The values I get are:
M307 H1 R2.876 C238.464:338.464 D10.36 S1.00 V23.4 B0 I0
Image of hotend:
Hi,
I am using a 50W heater with Biqu H2 extruder. I am able to auto-tune heater at different part cooling fan speeds. (tried from 20% to 100% fan speed). But when I set temperature, even with 100% fan ON, I see extruder overshoots the target temperature by >15degC .
I found few links, but there is some ambiguity in the documentation literature & the forum link.
following links, David asks to increase 'R' paramater.
https://forum.duet3d.com/topic/31038/overshoot-and-really-unstable-hotend-temperature/2?=1721909615387
https://forum.duet3d.com/topic/31038/overshoot-and-really-unstable-hotend-temperature/2?=1721909615382
But literature says, to decrease in case of overshoot:
https://docs.duet3d.com/User_manual/Connecting_hardware/Heaters_tuning
Can you please confirm whether to increase or decrease?
I have tried increasing R parameter, still the problem of overshoot persists.
Should I try tuning to 90% PWM?
@droftarts , @dc42 : What do you suggest?
NOTE: I am using latest firmware & didn't face such problem with Bondtech extruders & slice engineering heaters.
@dc42 : Heater fault in my case was due to some interference from BLtouch wire., not due to RRF 3.5.1.. There was a change in wiring in addition to RR3.5.1 upgrade, but when I debugged further, the root cause was as stated.
@droftarts :
I see this is happening only with 1/2 versions of cura generated Gcode. If I use latest Cura version gcode, I don't see this problem much. However, I will see if stopping the log , helps anyway.
Also, I do see that this problem does not appear in previous versions of RRF. May be something is changed w.r.t certain gcode interpretation.
@Phaedrux : Please mark this as solved.
@Notepad :
On resume, at times I see in 3.5.1, I see heater fault "temperature rising too slowly". This happens when after resuming on power failure, I set extruder temperature to 210degC. NOTE: This happens only during this resume sequence with 3.5.X. It does not happen in 3.4.6 ,...
@droftarts said in RRF[3.5.1]/RRF[3.5.0] : Gcode bad command error:
I notice you are not enabling networking. Are you running the simulation from a PanelDue?
Yes, I ran simulation via PanelDue, not from DWC.
Thanks for trying. If gcode simulated well, ***Will try with new SD card.
@droftarts said in RRF[3.5.1]/RRF[3.5.0] : Gcode bad command error:
Is there a reason you're running debug logging? This will impact performance, and means a lot of writes to the SD card. It could be that the level of logging has increased in 3.5.1, and is causing what was a marginal problem on the SD card to become a real one.
Is that so for 3.5.1? I am writing to SD card with debugging enabled, to debug problems if faced during printing. This log file helps me to understand at times if the print fails or there are problems w.r.t gcode, if dwc isn't connected.
What solution do you propose then? Is there a way to create log some other memory place?
@droftarts : Please see config below. I am not using daemon.g
; General preferences
G90
M83
M550 P"INFD300s"
M551 P"INFD300"
; Network
;M552 S1
M552 S-1
M586 P0 S1
M586 P1 S0
M586 P2 S0
; Drives
M569 P0 S1
M569 P1 S1
M569 P2 S1
M569 P3 S1
M569 P4 S1
M569 P5 S1
M584 X0 Y1 Z2:3:4 E5
M350 X32 Y32 I0
M350 Z16 E16 I1
M92 X160.0 Y160.0 Z2133.33 E932.00
;change as per machine
M566 X720.00 Y720.00 Z300.00 E600.00
M203 X8400.00 Y8400.00 Z420.00 E8400.00
M201 X3000.00 Y3000.00 Z30.00 E250.00
;M-curr
M906 X2200 Y2200 Z1600 E800 I50
M84 S30
; Axis Limits
M208 X0 Y0 Z0 S1
M208 X300 Y300 Z304.1 S0
; filament Sensor
M591 D0 P7 C"exp.e3stop" R15:300 L7 E17 S1
; Endstops
M574 X1 S1 P"xstop"
M574 Y1 S1 P"ystop"
M574 Z1 S1 P"zstop+e0_stop+e1_stop"
; Z-Probe
M950 S0 C"exp.heater3"
M558 P9 C"^zprobe.in" H5 F120 T6000
G31 P500 X0 Y0 Z1.038
; Auto level, coordinates as per motor order in M584
M671 X-17.66:297.34:140.00 Y-5.00:-5.00:327.61 S5.0 ;points position with left right ¢er
; define mesh grid
M557 X30:300 Y30:300 S20
M376 H5
; End Limits
M950 J1 C"exp.e4stop"
M581 P1 T2 R0 S1
M582 T2
M581 P-1 T2
M581 P1 T0 R0 S1
;PA
M572 D0 S0.055
; Bed Heater
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138
M950 H0 C"bedheat" T0
M307 H0 B0 S1.00
M140 H0
M143 H0 S105
; Extuder Heater
M308 S1 P"e0temp" Y"pt1000"
M950 H1 C"e0heat" T1
M307 H1 B0 S1.00
M143 H1 S320
; cooling Fans
M950 F0 C"fan0" Q500
M106 P0 S0 H-1
M950 F1 C"fan1" Q500
M106 P1 S0 H-1
; Tools
M563 P0 D0 H1 F0
G10 P0 X0 Y0 Z0
G10 P0 R0 S0
; Miscellaneous
M575 P1 S1 B57600
M501
M911 S21 R22.5 P"M913 X0 Y0 G91 M83 G1 Z5 E-5 F1000"
M929 S3 P"/macros/log/DEBUG.txt"
M17
@droftarts :
I will check on this , however...If its SD card issue, then why don't I get same problem when I flash 3.5 RC4/3 or on older version of RRF, for the same gcode file?
Can you try to simulate them in your printer with RRF3.5.1 for once, with Duet 2 wifi?
@Phaedrux : @chrishamm : It uploaded well please see with RRF 3.5.1version.
I am using Duet 2 wifi. Will share a few gcode files. As stated, this problem isn't in 3.5 RC4 much.
I am not able to upload gcode file directly. How do I share?.
If I simulate the gcode, I get some errors like bad command or message box stating expected integer after Y.
Sometimes error says "C1 " instead of G1. When I look back at the line number in Gcode, Line looks ok.
Because when I run it the second time, or simulate second time, bad command error either does not come at all, or it comes at a different line.
My problems are similar as posted in the thread :
https://forum.duet3d.com/topic/35553/bad-command-error-using-rrf-3-5-0-and-3-5-1-using-duet2-wifi/2
@Notepad :
I noticed this too. I had set some extraction in pause.g to resume well. Now it creates blob.
IF you resume after power fail, does it resume well for you ?