Hi All!
I hereby want to introduce you to the Ingenuity Extruder, designed for the smart effector.

It's a direct drive extruder which features a hollow-shaft Nema-14 stepper motor, Bondtech LGX drive gear, an eccentric breach which is self-locking, an idler wheel where the spokes act as a tensioning spring and a hypoid bevel gear pair, archiving a gear ratio of 37:7.

https://www.youtube.com/watch?v=eI0tD69wD18

The whole mechanism features only 4 moving parts: two gears, the idler wheel and the breach-lever:

I am currently looking for beta-testers, and if there's enough demand I'm hoping to make this a kit sometime in the future! If you're interested in helping please hit me up.

Hi all,
small rant about the search in the new wiki:
I really dislike how when I search for a gcode on the wiki search, there's often other articles displayed before it. Say I forgot the gcode (or parameters) for setting motor current, and I search for "set motor current", then the right entry only shows up on the 3rd spot: (meaning I can't just press enter to open it)

I wish there was a dedicated search for gcodes only.

Also: The search engine can't deal with typos at all, and every single one of the words in the query has to match. How is this better than just using ctrl+f?

I really like the new wiki, but please overhaul the search

I found the issue:

I have another axis defined, which I don't use for normal printing.
If this axis is not homed then pause.g isn't executed.
Homing all axis solves my issue

@chrishamm Love it!

Two things I'd like to be improved:

• The configurator looks a bit cluttered and dense, I think it would be more readable with more whitespace between the individual sections

• Currently it's not possible to set mixxing ratios for a tool with more than one extruder

@dc42 In case the new smart effector becomes a reality, can we have an accelerometer on it to help with the detection of a crash or ringing? (Similar to this)
I don't know how feasible that is but one could even use it for the delta calibration by measuring effector tilt. (Maybe it could even replace the strain gauge if precise enough?)

Might be a nice addition for the "normal" toolboards too.

Hi all,
The wiki entry for M567: Set tool mix ratios is missing information on the P parameter.
I think it should be mentioned that leaving the P parameter out will default to the active tool:

Pnnn Tool number. If this parameter is not provided, the current tool is used.

I'd love to see an accelerometer on the smart effector. It could be used for:

• Finding optimal values for acceleration and jerk (maybe implement a routine to do that automatically)
• Detecting resonance frequencies
• Help with delta calibration by measuring effector tilt
• Detect crashes (easy when magball comes loose, harder when one of the steppers misses a step)
• Replacing the strain gauge z probe

The Klipper firmware has some of the feature already:
https://www.klipper3d.org/Measuring_Resonances.html#mounting-the-accelerometer
https://www.klipper3d.org/Resonance_Compensation.html

I know some of these have been discussed already (and disapproved),
I think it's worth a shot though.

I just set up my Home Assistant Dashboard. Cool stuff!
But I noticed that while there is support for Octoprint, there is no Integration for the Duet framework.

I only found a plugin for the DSF which exposes the Object Model on MQTT, but that also doesn't provide the same functionality as the Octoprint integration. I'd like to pause and abort the print from the Home Assistant Dashboard for example.

Anyone else interested in this functionality?

@droftarts Way ahead of you

https://www.youtube.com/watch?v=eI0tD69wD18

@droftarts I followed a blender tutorial hahaha. The math is done here for you: http://www.otvinta.com/hypoid.html

I want to open source this design under Creative Commons, so any help is appreciated!

I'm actually looking for beta testers, and maybe we can make this a kit!

@o_lampe You could retract/deploy the ball with an electromagnet. Altough I wouldn't use a ball but a rod with a spherical end. I don't think this kind of zprobe needs a "rolling" element.

@elmoret Nothing stopping you from using a 24V heater at 36V XD
You'd get 2.25 times more power out of it!
(and a fire hazard lol)

@oliof thank you, that's very useful to know!

@Adrian52 can you post your config?
I also had a look at the changelog between beta2 and beta3, but I don't see any change that might cause your problem. Maybe have a look yourself: https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x-Beta#reprapfirmware-350beta3

@MihaiDesigns I can already see the expression on your face when you talk about this in an upcoming video ^^

Some time ago I also configured sensorless homing for XY on a coreXY. After after a while I had it dialed in quite nicely. Then the next day it didn't work at all (I haven't changed any settings). Turns out some gcode I ran adjusted the travel acceration, and with the higher acceleration the sensorless homing would give me false positives. So maybe reduce your accelerations for the duration of the homing sequence?

@dc42 I tried that but M400 introduces a weird stutter:

Same gcode, left one uses G4 before M569.4, right one uses M400

@Adrian52 what are the print-times for both firmwares? If 3.5.0-rc1 is lower then @o_lampe might be onto something. Be sure to check the print times in the webinterface, not in the slicer.

@dc42 I should have clarified this better: I'm not trying to put the extruder motor into torque mode but a different driver (U axis). The whole gcode snipped would look closer to this:

G1 X147.351 Y89.291 F9000      ;move to coordinate
M569.4 P21.0 T-0.3      ; apply negative torque on U axis
G1 E-1 F4200            ; retract while negative torque is applied
M569.4 P21.0 T0.5       ; apply positive torque on U axis
...continue printing with positive torque applied

At the moment I need to prefix every torque change with G4 to synchronise the change in torque and the retraction.

@nikscha I found a workaround for now, by inserting a G4 just before the M569.4.
Note that a supposedly equivalent M400 introduces stutters.

@dc42 I see, I expected the file to be "reloaded" after saving and then not being found afterwards because of the renaming. Thank you for the solution!