Smarteffector problems with 3.11 ( update from 2.04)

fragle

bed.g

; bed.g file for RepRapFirmware, generated by Escher3D calculator
; 16 points, 6 factors, probing radius: 160, probe offset (0, 0)
G28
G30 P0 X0.00 Y160.00 Z-99999 H0
G30 P1 X102.85 Y122.57 Z-99999 H0
G30 P2 X157.57 Y27.78 Z-99999 H0
G30 P3 X138.56 Y-80.00 Z-99999 H0
G30 P4 X54.72 Y-150.35 Z-99999 H0
G30 P5 X-54.72 Y-150.35 Z-99999 H0
G30 P6 X-138.56 Y-80.00 Z-99999 H0
G30 P7 X-157.57 Y27.78 Z-99999 H0
G30 P8 X-102.85 Y122.57 Z-99999 H0
G30 P9 X0.00 Y80.00 Z-99999 H0
G30 P10 X69.28 Y40.00 Z-99999 H0
G30 P11 X69.28 Y-40.00 Z-99999 H0
G30 P12 X0.00 Y-80.00 Z-99999 H0
G30 P13 X-69.28 Y-40.00 Z-99999 H0
G30 P14 X-69.28 Y40.00 Z-99999 H0
G30 P15 X0 Y0 Z-99999 S6

homedelta.g

; homedelta.g
; called to home all towers on a delta printer
;
; generated by RepRapFirmware Configuration Tool v2 on Tue Feb 26 2019 21:31:01 GMT+0000 (Greenwich Mean Time)
G91                        ; relative positioning
G1 H1 X470 Y470 Z470 F1800 ; move all towers to the high end stopping at the endstops (first pass)
G1 H1 X10 Y10 Z10 F360     ; move all towers up once more (second pass)
G90                        ; absolute positioning

jay_s_uk

@fragle ok
Few issues I can see if your config.
M350 only supports Interpolation of microsteps at x16, so I suggest you change back to x16 and the steps per mm to 80.
Secondly, your endstop settings are incorrect. You have them set as being on the low end when infact they are on the high end. The correct settings are

M574 X2 S1 P"xstop"
M574 Y2 S1 P"ystop"
M574 Z2 S1 P"zstop"

Your G31 should have z set as -0.1

Here is my predator config for reference https://github.com/jaysuk/Anycubic-Predator-Duet/tree/SmartEffectorRRF3

jay_s_uk

@fragle your homing file is also incorrect as it doesn't move the towers down before trying to home again.
This is what it should contain.

G91                        ; relative positioning

G1 H1 X470 Y470 Z470 F1800 ; move all towers to the high end stopping at the endstops (first pass)
G1 X-5 Y-5 Z-5 F1800 H2    ; go down a few mm
G1 H1 X10 Y10 Z10 F360     ; move all towers up once more (second pass)
G1 Z-5 F6000               ; move down a few mm so that the nozzle can be centred
G90                        ; absolute positioning
G1 X0 Y0 F6000             ; move X+Y to the centre

fragle

I ve adaped my config to your settings, now G32 is working well, but with the mesh compensation i am getting an G29 error Z probe readings are not consistent

At G29 the printhead goes down correctly, make some soft touches to the print plate and after around 4 or 5 point he stand still.

M557 set mesh parameter said 175 radius and 16 spacing

fragle

oh i forgot, i have an whambam printplate over the normal print plate

Phaedrux

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

At G29 the printhead goes down correctly, make some soft touches to the print plate and after around 4 or 5 point he stand still.

Might need sensitivity adjusted for the smart effector? Higher probe speed?

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:

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.
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.
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