Smarteffector problems with 3.11 ( update from 2.04)

[jay_s_uk]

@fragle you've probably got play in your system with the default arms. Try increasing the S value on M558 to something like 0.05

[fragle]

I will try the suggestions today, but i do not thing, that it is an hardware problem, because the system is running on fw 2.04 without any problems.

[fragle]

small update

if i use G32, than i am getting

Calibrated 8 factors using 16 points, (mean, deviation) before (-0.004, 0.067) after (-0.000, 0.053)
Repeating calibration because deviation is too high (0.053mm)
too many auto calibration attempts

[jay_s_uk]

@fragle so change the S value to 0.06 (or even slightly higher)
Currently, any value above 0.05 (originally 0.02) will cause it to fail.
Its due to the sloppy eyes they use on the rods on the predator.

[fragle]

G32 is now successful after the second run

I have set the sensitivtiy to 10 for the smart effector, but i am wondering, why the display of the Z probe switches to "1000" around every third contact to the print plate.

The other 2 hits, there was no "1000" release on the display ( even tough the nozzle hits the plate and withdraw correct.

[jay_s_uk]

@fragle DWC generally doesn't catch up enough to fully display every probe. If it works, don't worth about it.

[fragle]

I have crosschecked the predator with my old 2.04 settings, everything is working fine.

Back to 3.1.1

Now i can run G32 and G29 without error.

I i try to print something i use as start script
G28
G32

During the G32 from the gcode i am getting always an
Error: Z Probe already triggered at atrt of probing mode

I have reset the sensififity to 131:131 ( default setting)

i ve tried some configs starting from here https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe to some hints in the forum, but nothing worked.

[dc42]

@fragle said in Smarteffector problems with 3.11 ( update from 2.04):

Error: Z Probe already triggered at atrt of probing mode

There are a few possible reasons for this:

1. The Smart Effector is triggering when it shouldn't. If this is happening, you will see the green LED on the effector flashing. But if you are sure that it works under RRF 2.05.1, that can't be the problem.
2. Vibration or deceleration after the positioning move is causing the effector to trigger. If it's vibration, reducing the sensitivity will help. If it's deceleration after the positioning move, increase the M558 R parameter.
3. The effector output wire is picking up interference from an adjacent stepper motor wire. If that is the cause, and you are using probe type 5 in M558, increasing the G50 P parameter may help.

Are you using exactly the same parameter values (except for the ones where the command format has changed) in 3.1.1 as in 2.04, in your M558, M201, M203, M566, M906 and M569 commands in config.g?

[fragle]

small update:

I ve upgraded to firmware 3.2 an now i can print, but i have to adjust the Printhead at printing with 0,2mm babysteps.

If i try to calibrate the Z Probe as described here https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe i am getting -0,01 . Nothing change if i will change the z value to 0,2

[Phaedrux]

@fragle said in Smarteffector problems with 3.11 ( update from 2.04):

i am getting -0,01

It should be slightly negative because it's pressing into the bed. Why do you want to use 0.2?

[fragle]

if i use -0.01my print noozle is to close to the print bed, it is so close, that it would scratch the surface

[Carlo]

@fragle
If you G1 Z0.1 does it hit the bed before you calibrate G32?
You need to set your height currently H430.00 can't be correct also take out ;M501
don't want config_override at this point as it isn't helping.
Heat the bed to 60c nozzle 130c then home G28
don't calibrate just lower the nozzle to a piece of paper on the bed or .1 feeler gauge
that's your height minus off what's above zero/0.1 from M665 H parameter then reboot and G1 Z0.1 should be 0.1 above the bed then set your probe trigger height to -0.1 reboot and calibrate