@T3P3Tony This is only semi-on-topic because I have a 713-maker effector plate on my Rostock Max v2, not a Smart Effector.

But I have cobbled together a real-world implementation of an LDO Orbiter V2.0 on that effector. My solution was to rotate (20º) and raise the extruder (25mm) to clear the arms. A short length of bowden tubing within the extender keeps the filament guided between motor and extruder. It turned out that this arrangement cut down on the build envelope more than desired (allowed the motor to hit the arms at the top extreme of the plate) so I moved all of the effector's arm attachment points outward by 13mm (increasing the size of the effector plate).

Raising and rotating the motor might have deleterious effects on momentum/vibration/tilt that outweigh the fact that it allows for a slightly smaller effector plate that still fits the motor between the arms. But it's working for me for the moment.

I upgraded my Rostock Max v3's Duet 2 Wifi to a recent firmware (3.2-RC2) in an attempt to fix some wifi connectivity reliability issues, and quickly realize it was necessary to do some major updates to my config.g in order to function on Reprap Firmware 3.

I got it working and set to making a bunch of prints. Then when doing some bridging test prints I realized that the hotend fan that blows on the newly-extruded filament to lower its temperature was not running at all, and its gcode seemed to be instead controlling the fan that blows into the heatsink of the hotend (which I'd normally have running constantly). Oops.

I took a look at my old config.g to see how the fans were set up, and the only line I saw that seemed to relate to fans was this one:

; Fans
M106 P1 T45 H1				; thermostatic mode for fan 1

That's it, that's all I could find. But on the printer there's both a cooling fan for the filament and a fan for the hotend itself, and they both used to function just fine without additional specification. Maybe the older firmware (I neglected to note the version number but it was a couple years old and was either in the v1 or v2 series) included assumptions about those two fans so they didn't need defining?

In my current config.g I've got the fan(s) set up as follows, my obviously incorrect attempt to translate the previous config.g's fan instructions into gcode for RRF3.x.

; Fans
M950 F1 T1 C"fan1"
M106 P1 C"Extruder" S1 H1 T45

Is it obvious to anyone what I need to do to get both of the fans on my hotend functioning as before? I'd guess this is something everyone upgrading to RRF3.0 has already managed to accomplish.

Thanks for any help or information.

Might have been inadvisable, but I decided the likely worst thing that would happen if I got it wrong was that it wouldn't detect the plate and would crash through it, and I was ready to cut the power in that case, so I went with C"^zprobe.in". It's been fine.

Hi, I've got a Rostock Max v3 with the Ultibots FSR Kit installed, which means the FSR sensors are connected to a "JohnSL FSR Endstop Controller" and then that to the probe pin of a Duet 2 Wifi.

It's been a day of work figuring out all of the things needed to change in my config.g to get the delta up and running with the latest RRF3 firmware. I think the last step may be figuring out how to properly set up for my FSR sensors.

The question is, should my M558 line be:

M558 P5 C"zprobe.in" H5 F600 T2400

or

M558 P5 C"^zprobe.in" H5 F600 T2400

Thanks for any help or information.