@oliof Deltas would likely want wildly different IS compensation for Z versus XY since Z is the one axis where everything's going the same direction, but assuming per-axis IS settings become a thing in RRF, there might be a case there!
@dc42 I've yet to design a proper way to mount my rat's nest of components, the amplitude error goes away when I hold the coil some millimeters above the print bed.
Considering the individual cost of a Sammy C21, LDC1612, and an accelerometer, the SZP is both cheaper and more convenient (-:
@gloomyandy the values I quote are as used in my config.g, so yes there is a unit confusion error here. Which would put massive limits on e acceleration (although it is not entirely clear to me what happens if E acceleration exceeds the limit of E jerk/PA).
EDIT: OR the limits are to be computed as above and the unit confusion is irrelevant. One for @dc42 to clarify.
@tas no worries. In your case I would have assumed bad signal, but your signal strength is pretty decent at -55dBm. Nonetheless, if your antenna is in an enclosure or close to a wall, consider reloacting it.
@sebkritikel my individual IDEX heads are pretty light (two EVA toolheads, can run 20k and more acceleration on other machines) and only run in X (its still an i3 style bed slinger), so I think I am good on the weight front.
I guess I need to actually put an accelerometer on mine since the Klipper test print shows almost nothing in terms of ringing. if that gives me weird graphs, I will go hunt for things that move when they shouldn't.
@T3P3Tony thanks, I will give it a whirl and share something here. @sebkritikel that is the plan, get "toolmode" from slicer or prompt for it in start.g using the new M291 method, and then swap things around.
Prusa MK3 firmware's thermal modeling is making some great advances, able to detect thermal anomalies that could indicate a blob of filament building up on the nozzle, and allowing for continuation. We'll get those enhancements into MPCTEMP and our own thermal protection at some point. Prusa developers on Slack are a little cagey about when they will contribute Marlin patches, but at least they are asking about it.