@droftarts Oh crap.. I just realized that I sent M122 while disconnected.... So that would explain "didn't return anything". As in hitting enter at the end of M122 restarted the serial link.
Sorry,. I guess we'll never know what it thought it was doing 
@droftarts M122 didn't return anything. But, refresh was an instant success. Thank you
M997 S1
Trying to connect at 230400 baud: success, found ESP8266
Erasing 8192 bytes…
Erasing 690688 bytes…
Uploading file…
5% complete
10% complete
15% complete
20% complete
25% complete
30% complete
35% complete
40% complete
45% complete
50% complete
55% complete
60% complete
65% complete
70% complete
75% complete
80% complete
85% complete
90% complete
95% complete
Upload successful
ok
WiFi module started
WiFi module is connected to access point Mitt, IP address 172.25.74.150
So, I was running 3.6.0B1 on my Duet2Wifi and decided to upgrade.
I uploaded Duet2CombinedFirmware.bin, that brought up the warining about "Please use matching versions" (or some such), that was expected
I then uploaded
DuetWiFiModule_32S3.bin
DuetWiFiServer.bin
Dialog box asked "Upgrade wifi firmware"? (or similar, can not remember exact wording). the checkbox was "yes" as default
I accepted.
Printer rebooted. But never came back on network.
Serial terminal shows wifi module being stuck in starting.
Any advice?
M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.6.0-beta.1 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2024-09-24 10:07:04
ok
M552
WiFi module is being started
ok
M552
WiFi module is being started
ok
M552
WiFi module is being started
ok
M552
WiFi module is being started
ok
@droftarts Dropping R down to 480 allows me (so far) reliable initial heating, with only about 0.8C overshoot on the initial run to 70C. That is fully acceptable for me.
So, thank you for pointing me into the proper direction.
@droftarts A tad closer I'd say (with 10% reduction)
Here is the M307
M307 H0
Heater 0: heating rate 0.570, cooling rate 0.296, dead time 7.54, max PWM 1.00, mode PID
Predicted max temperature rise 162°C
PID parameters: heating P41.5 I0.783 D219.2, steady P41.5 I1.821 D219.2
If I set the bed to heat from cold to (95C) is happily rockets past 70. So, it does seem to be something with the parameters.
After having read the doc you linked, I did do a significant bump of firmware a while back. When 3.5 was released, I did go from 3.2 -> 3.5
So, whatever changed in 3.2 - 3.4, I have not experienced.
@droftarts even a 10% diff lands me with
Heater 0 fault: temperature rising too slowly: expected 0.39°C/sec measured 0.09°C/sec
@droftarts Thank you. Not sure how I managed to NOT see that one.
@droftarts Thank you. Will try after current printing batch.
Also, from where is that advice to reduce by 5-10%? I honesrtly thought that I had done my homework.
@droftarts My config override line is in my orginal post?
But here is the full file
; config-override.g file generated in response to M500 at 2024-10-27 16:11
; This is a system-generated file - do not edit
; Delta parameters
M665 L360.200:360.200:360.200 R179.731 H452.215 B150.0 X-0.440 Y-0.372 Z0.000
M666 X-1.338 Y-0.148 Z1.486 A0.60 B0.18
; Heater model parameters
M307 H0 R0.631 K0.296:0.000 D7.54 E1.35 S1.00 B0
M307 H1 R2.825 K0.402:0.000 D7.27 E1.35 S1.00 B0 V24.2
; Workplace coordinates
G10 L2 P1 X0.00 Y0.00 Z0.00
G10 L2 P2 X0.00 Y0.00 Z0.00
G10 L2 P3 X0.00 Y0.00 Z0.00
G10 L2 P4 X0.00 Y0.00 Z0.00
G10 L2 P5 X0.00 Y0.00 Z0.00
G10 L2 P6 X0.00 Y0.00 Z0.00
G10 L2 P7 X0.00 Y0.00 Z0.00
G10 L2 P8 X0.00 Y0.00 Z0.00
G10 L2 P9 X0.00 Y0.00 Z0.00
@jay_s_uk Ah, sorry for missing that bit.
Same behaviour in 3.5.3 and 3.6.0-beta.1
So, I have a delta with a 310mm buildplate, 10mm milled aluminum with a 400W AC heater. The SSR is a genuine brand name far as I know. (Purchased from reputable dealer in Sweden (ELFA))
After PID tuning to 70C I end up with the following in config-override
M307 H0 R0.631 K0.296:0.000 D7.54 E1.35 S1.00 B0
I do have M501 in config.g
The bed heats up as expected initially, but as it approaches the target temperature I do notice the rate of increase dropping, I assume this is expected as the PID would be backing of the power. (If I set the bed to BangBang it shoots past the target without looking back, so I say that the heater has enough power)
Then I get the "Temp rising to low. Expected 0.4C/s, Observed 0.02C/s" message (Not word for word, as I am quoting from memory)
I have redone the tune a few time, making sure that I go from ambient (yes, I have let the bed 'rest' overnight before each attempt)
Looking in the forum, it seem the main advice is "Select a proper frequency for your SSR" and I believe that 10Hz should be reasonable. I have also tried both 2Hz, 50Hz and 1000Hz. Yes, I know how AC and SSR works, yes 1000Hz was a typo as I was aiming to try 100Hz 
)
If I just reset the heater fault and resume, it operates as expected.
What could I do to fix this issue?
My heaters are defined like this.
; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4400 R4700 ; Orignal was 3950, but curve did not match, actual temp was too low. configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 Q10 ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
;M308 S1 P"e0temp" Y"thermistor" C7.060000e-8 B4725 ; configure sensor 1 as thermistor on pin e0temp (E6Extruder)
M308 S1 P"e0temp" Y"thermistor" T100000 B4680 C6.455513e-8 ; 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 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M308 S2 Y"drivers" A"DRIVERS" ; configure sensor 2 as temperature warning and overheat flags on the TMC2660 on Duet
M308 S3 Y"mcu-temp" A"MCU" ; configure sensor 3 MCU Temp
@dc42 said in Slow after changing extruder:
@janjoh your pressure advance value 0.25 looks way too high for an extruder mounted on the hot end, which I presume your Orbiter is.
No. Flying extruder. Approx 20cm of bowden above a Smart effector.
HOIWEVER. Something must have been really off with the previous extruder, because "The Ellis Guide" gave me 0.25 PA.
As it looks now, i seem to be in the 0.04 range. (and yes, i am CERTAIN that the old extruder landed at 0.25 and not 0.025.. I promise)
Groaaaan.. I stared at only the extruder settings as such for too long. I THOUGHT i had disabled PA and was going to re-tune after shake down.. Yeah, need to retune that and prolly go a bit higher on M566 orbiter says "Up to 600mm/s"
Thank you.
Or "WHat accel / jerk / speed setting have i messed up now?"
I replaced my old extruder with a Orbiter 2.0, and used the recommended settings from their wiki.
BUt, for some reason my printer is now extremely slow on (especially) gyroid infill. And I can't figure out what I may have misconfigured.
Here's my current config
; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.1.3 on Sun Jun 21 2020 17:39:49 GMT+0200 (Central European Summer Time)
; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Full Metal Delta" ; set printer name
M665 R179.774 L360.2 B150 H460 ; Set delta radius, diagonal rod length, printable radius and homed height
M666 X0 Y0 Z0 ; 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 S1 ; enable 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 S0 ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
;Main kinematics
M92 X160.00 Y160.00 Z160.00
M566 X1200.00 Y1200.00 Z1200.00 ; set maximum instantaneous speed changes (mm/min)
M203 X25000.00 Y25000.00 Z15000.00 ; set maximum speeds (mm/min)
M201 X3000.00 Y3000.00 Z3000.00 ; set accelerations (mm/s^2)
M906 X1500 Y1500 Z1500 I20 ; set motor currents (mA) and motor idle factor in per cent
M84 S120 ; Set idle timeout
;Orbiter V2
M92 E690
M203 E7200
M566 E300
M201 E3000
M906 E1200 I10
;M207 S1.5 F7200 Z0.2
;Pressure advance
M572 D0 S0.25
; Axis Limits
M208 Z0 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 R0.4 C"zprobe.in+zprobe.mod" H3.0 F1300 T12000 A16 S0.025 ; set Z probe type to effector and the dive height + speeds
G31 P500 X0 Y0 Z-0.06 ; set Z probe trigger value, offset and trigger height
M557 R140 S40 ; define mesh grid
; Filament sensor
M591 P3 C"e0_stop" S1 R20:200 L24.8 E6.0 D0
; Accelerometer
;M955 P0 C"spi.cs4+spi.cs3" I25
; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4400 R4700 ; Orignal was 3950, but curve did not match, actual temp was too low. 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 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
;M308 S1 P"e0temp" Y"thermistor" C7.060000e-8 B4725 ; configure sensor 1 as thermistor on pin e0temp (E6Extruder)
M308 S1 P"e0temp" Y"thermistor" T100000 B4680 C6.455513e-8 ; 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 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M308 S2 Y"drivers" A"DRIVERS" ; configure sensor 2 as temperature warning and overheat flags on the TMC2660 on Duet
M308 S3 Y"mcu-temp" A"MCU" ; configure sensor 3 MCU Temp
; Fans
M950 F1 C"fan1" Q100 ; create fan 1 on pin fan1 and set its frequency
M106 P1 C"Heat sink" X0.65 H1 T65 ; set fan 1 name and value. Thermostatic control is turned on
M950 F2 C"!Fan2" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P2 C"Chassi Fan" H2:3 X1 B0.5 T45:55 ; set fan 1 name and value. Thermostatic control is turned on
M950 F3 C"exp.heater3+exp.e3stop" Q10000
M106 P3 C"Blower" H-1 X1 B0.1 L0.19
; Fans - Nozzle led.
;M950 F0 C"fan0" Q2000 ; create fan 0 on pin fan0 and set its frequency
;M106 P0 C"Nozzle LED" H1 T120 X1 ; Nozzle led, on when tool0 >= 120C
;Floodlight LED
M950 F4 C"e1heat" Q2000
M106 P4 C"Floodlights"
; Tools
M563 P0 D0 H1 F3 ; 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
;Input Shaping
M593 P"zvddd" F46
; Custom settings are not defined
; Miscellaneous
M912 P0 S-23 ; Set Temperature offset for MCU.
M501 ; load saved parameters from non-volatile memory
It seem to be a TPU thing. WHen loading Ninjaflex, it seem to just not grip the filament enough, leading to these unreasonable values.
Well, I guess I can live with that..
Yeah, why NOT define it as a fan and get a nice slider all automatically...
Thank you, I was JUST about to update that I made the same realization. "If this is not a supported LED type, then what else can it be?"
And yes, I did order a 24V strip especially because I intended to use the e1 for this purpose
950 P4 C"e1heat"
M42 P4 S1 ; And all of a sudden I need to wear my shades inside.
Now to figure out the best way to add a button / slider / something to DWC for this. Heh.. I suppose I COULD define it as a fan instead...
DUet 2 Wifi / 3.5.2
So,I'd like to repurpose e1 heater as a LED strip, using a "Standard 24V COB strip".
Looking at M950 i see
"Tn (optional) LED type: 0 = DotStar, 1 = RGB Neopixel (default), 2 = RGBW Neopixel. DotStar LEDs can normally be assigned only to an output intended for them."
I do not see a value for a "Plain jane" LED strip here. But i do see that "T" is optional, but no mention of what omitting it would default to.
So, I guess that I can not define a PWM Led in this fashion? (Unless omitting T would achieve this)
TL;DR: How to repurpose e1.heat as a PWM LED Driver?
Understood. Thanks. So, does that mean that whatever is in cancel.g supersedes whatever may be in the movement buffer?