Smart Effector issue
-
What does the fan shroud look like when on?
-
-
Ah, so quite large then.
-
Jay has been using this model without problems, so go figure.
-
Interesting. I wonder if it's a sensitivity problem then.
I assume it's been disassembled and reassembled already?
-
Still as in latest picture = no duct.
Total weight is 84grams with 3 fans, printed in PETG. -
@phaedrux that duct design (which is mine) works fine for me on my smart effector v3 so i doubt thats the issue. I still think its a mechanical issue with effector tilt
-
Have found my main issue = the printed effector adapter is way too small = too short rods.
Back to the drawing board!
-
A bit larger adapter
-
One violent move and this is the result.
-
So some days has gone and I am now trying to get the Smart Effector to work = no go!
New non 3D printed effector adapter (original in alu with slight modifications)
Area of bed 9 to 3 down to 6 can be probed G30 and 0,0 towards back about 50mm works
Out of that area the smart effector is not sensitive enough as the effector needs to tilt a lot before it triggers.
I find this a bit odd as the trigger LED on head moves. All set to default values. -
Your dive speed seems to be half the recommended value. M558 F600 vs M558 F1200
https://docs.duet3d.com/en/Duet3D_hardware/Accessories/Smart_Effector#configuring-firmware
M558 P8 R0.8 C"probe+servo0" H10 F600 T2000
M558 P8 R0.4 F1200
So perhaps it's not striking with enough force to reliably trigger.
-
And looks like that, had to go all way up to 2500 to get reliable trig.
Where do I set hotend offset and where to set effector offset?
Looking from front X0/Y0 effector is to left and the hotend is a bit left too. -
@tecno said in Smart Effector issue:
Where do I set hotend offset and where to set effector offset?
Looking from front X0/Y0 effector is to left and the hotend is a bit left too.I'm not sure what you mean.
-
FWIW we've identified a modification to the Smart Effector version 3 that improves the signal-to-noise ratio, which in turn allows you to use a higher sensitivity unless fan noise etc. prevents that. The modification is to remove capacitor C8. This can be done using a soldering iron with a bit large enough to cover both pads. Alternatively, you could use a small twist drill bit to remove a thin sliver of copper around the adjacent via that connects one end of the capacitor to the ground plane.
This image is as viewed from the top of the PCB, so you need to invert it when looking at the bottom.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@phaedrux said in Smart Effector issue:
@tecno said in Smart Effector issue:
Where do I set hotend offset and where to set effector offset?
Looking from front X0/Y0 effector is to left and the hotend is a bit left too.I'm not sure what you mean.
; Tools
M563 P0 D0 H1 F0 ; define tool 0
G10 P0 X-4 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0Fixed offset issue
-
@dc42 said in Smart Effector issue:
FWIW we've identified a modification to the Smart Effector version 3 that improves the signal-to-noise ratio, which in turn allows you to use a higher sensitivity unless fan noise etc. prevents that. The modification is to remove capacitor C8. This can be done using a soldering iron with a bit large enough to cover both pads. Alternatively, you could use a small twist drill bit to remove a thin sliver of copper around the adjacent via that connects one end of the capacitor to the ground plane.
This image is as viewed from the top of the PCB, so you need to invert it when looking at the bottom.
So far during my tests no fans are used, good to know when adding fans.
-
Still some issues with false trig = does not go down but LED lights up = trig.
How to solve this?
-
When and where was it purchased?
-
Warning: Skipping grid point X=40.0, Y=60.0 because Z probe cannot reach it
37 points probed, min error -0.260, max error 0.240, mean -0.026, deviation 0.113
Height map saved to file 0:/sys/heightmap.csvFrom where does this X=40.0, Y=60.0 coordinate originate?
