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