So, I finally got annoyed at having to mess with the cable tie in order to remove/replace the BerdAir in order to swap nozzle and such. So, I scavenged the springs from two old ball point pens. It works quite nicely. Here's a video of said "hack".

https://youtu.be/cMkjLRHmXe4

So, now that we're starting to see accelerometer support in firmware. Would it not be plausible to use that to detect "catastropic tilt" in delta effectors?
I mean, if a rod pop, belt snap or similar, the effector will tilt out of whack in a non to subtle fashion, which would be nice to be able to detect?

(I suppose it could also be used to detect general "impacts" regardless of kinematic? Even "lack of even an approximate expectation of tool movement" if a kinematic fail was to occurr?

@felt342 The normal 540-size brushed 24V. If i had more money I'd try a Kamover KVP8. If I had even MORE moneis i would try an airbrush compressor with a servo valve

So, the doc is pretty clear https://docs.duet3d.com/en/User_manual/Connecting_hardware/Fans_connecting#connecting-fans-to-duet-fan-pins states that it expects Intel spec fans, as in two pulses per revolution.

I happen to use a blower that has a signal at which 1Hz means 60rpm. Any way to fudge the value so that the DWC shows the actual value?

@Danal Ah. Thank you for the clarification.

I decided that I'd see what happen if i use a "default" Cura profile and just change retracts and temps. Just to see what it will do.

I have a feeling that 3 years of "tinkering" probably has accumulated a lot of issues and "tweaks for issues that causes new issues" ... so to speak

@o_lampe I have no idea what the overhead would be. But again, I suppose an interval check would be better then no check.

Magnet field sensor on a smart effector with Hayden rods.. That would be fun readings

@fcwilt Noooooooooooo... (or rather yes)....

Yeah, that's spot on... at Z0.32 I can now get a 0.30 feeler in. At Z0.28 I can not.

So, that was flipping silly of me..... Especially as this means that my start script was correct, but my manual testing was (really) flawed... Sigh.

Nothing to see here... move on...

Thank you.

@dc42 THank you for confirming. I've added such a request now, while at the same time understanding that this is in every way a cosmetical low priority wish

@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.

@Phaedrux Thank you for the comment on refurbed units. I do however think that I will not put any more money into smart effector until (maybe) such a time as the mythical updated version may become available. I have a fairly reliable machine, and I know how to use a feeler gauge.

@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

In the end, i ended up at PA of 0.12

@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)