Smarteffector problems with 3.11 ( update from 2.04)

[Veti]

@fragle

does a g30 work? a g32 can fail if your height is incorrect.

[Carlo]

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

M558 P5 C"zprobe.in+zprobe.mod" X0 Y0 Z0 H5 R0.4 F1200 T6000

M558 P5 C"zprobe.in+zprobe.mod" X0 Y0 Z0 H35 R0.4 F1200 T6000
try changing the probe height higher as above

[fragle]

G30 is working, the rods go down, hit the surface and go to +35mm Z
The heigh settings should be correct, the complete system was running for nearly 16 months with the settings on 2.xx

To change H35 has nothing changed on the behavior

[Carlo]

@fragle

M558 P5 C"zprobe.in+zprobe.mod" X0 Y0 Z0 Z- for an sm effector

[Veti]

home and manually check with G0 Z0 if the height is correct

[jay_s_uk]

This should be the valid entry in config.g for the smart effector

M558 P8 H4 F1000 T12000 R0.2 S0.02 A5 C"zprobe.in+zprobe.mod"

Run each line individually

G28
G30 X0 Y0
G32
M500

This will home the machine, probe the centre of the bed to determine 0, then run delta calibration and finally save the results.
Make sure you have M501 at the end of your config.g

[fragle]

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

M558 P8 H4 F1000 T12000 R0.2 S0.02 A5 C"zprobe.in+zprobe.mod"

G28 reports only an "Operation has been cancelled" error

[jay_s_uk]

@fragle sounds like you have homing issues then as M558 doesn't interact with homing (G28)

[fragle]

I have found the mistake, there is an optical endstop with some loose contact.
now it .

Changed to a news one , and your settings are working.

But now if i try to run a mesh compensation ( G29), the noozle drives down and then stay around 10mm over the heatplate and stops.

If i use the old additional Setting for the Z-probe, than the print head crashes into the Heatplate

31 P100 X0 Y0 Z-0.000 ; Set Z probe trigger value, offset and trigger height
M557 R150 S20 ; Define mesh grid
G29 S1 ; Load the heightmap

[jay_s_uk]

@fragle can you post your current complete config please. Which delta is it as well?

[fragle]

It is a Anycubic Predator with a smart effector and default rods

; Configuration file for Duet WiFi (firmware version 1.21)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2 on Tue Feb 26 2019 21:31:01 GMT+0000 (Greenwich Mean Time)
 
; General preferences
G90                                         				; Send absolute coordinates...
M83                                         				; ...but relative extruder moves
 
; Delta Settings
M665 L440.000 R227 H430.0 B185.0 						 	; Set delta radius, diagonal rod length, printable radius and homed height
M666 X0 Y0 Z0 A0.00 B0.00               			     	; Put your endstop adjustments here, or let auto calibration find them
 
; Network
M550 P"Anycubic Predator"                     				; Set machine name
M551 P""                         							; Set password
M552 S1
M552 P192.168.178.10  	                        				; Enable network and acquire dynamic address via DHCP
M553 P255.255.255.0
M554 P192.168.178.1
M586 P0 S1                                  				; Enable HTTP
M586 P1 S0                                  				; Disable FTP
M586 P2 S0                                  				; Disable Telnet
 
; Drives
M569 P0 S0                                  				; Drive 0 goes forwards
M569 P1 S0                                  				; Drive 1 goes forwards
M569 P2 S0                                  				; Drive 2 goes forwards
M569 P3 S0                                  				; Drive 3 goes forwards
M350 X32 Y32 Z32 E16 I1                     				; Configure microstepping with interpolation
M92 X160.00 Y160.00 Z160.00 E415.00             				; Set steps per mm
M566 X1000 Y1000 Z1000 E1000    	            			; Set maximum instantaneous speed changes (mm/min)
M203 X12000.00 Y12000.00 Z12000.00 E10000 					; Set maximum speeds (mm/min)
M201 X3000.00 Y3000.00 Z3000.00 E3000.00    				; Set accelerations (mm/s^2)
M906 X1000.00 Y1000.00 Z1000.00 E1000.00 I30 				; Set motor currents (mA) and motor idle factor in per cent
;M666 X3 Y0 Z0
M84 S45                                     				; Set idle timeout
 
; Retraction
M207 S4.0 F5000 R-0.025 T2500 Z0.5							; Firmware retraction
 
; Axis Limits
M208 Z0 S1                                  				; Set minimum Z
 
; Endstops
M574 X1 S1 P"xstop"   ; X min active high endstop switch
M574 Y1 S1 P"ystop"   ; Y min active high endstop switch
M574 Z1 S1 P"zstop"   ; Z min active high endstop switch
M574 U2 S1 P"e0stop"  ; U max active high endstop switch
 
; Z-Probe
M558 P8 H4 F1000 T12000 R0.2 S0.02 A5 C"zprobe.in+zprobe.mod" 
 
G31 P100 X0 Y0 Z-0.000                      					; Set Z probe trigger value, offset and trigger height
M557 R150 S20                               				; Define mesh grid
G29 S1														; Load the heightmap
 
; Heaters
M308 S0 P"bed_temp" Y"thermistor" T100000 B3950 ; define bed temperature sensor
M308 S1 P"e0_temp" Y"thermistor" T100000 B4725 C7.06e-8 ; define E0 temperature sensor
M950 H0 C"bed_heat" T0 ; heater 0 uses the bed_heat pin, sensor 0
M950 H1 C"e0_heat" T1 ; heater 1 uses the e0_heat pin and sensor 1
M140 H0 ; the bed heater is heater 0
 
M143 H0 S130								; Set temperature limit for heater 0 to 120C
M143 H1 S280								; Set temperature limit for heater 1 to 280C
 
; Fans
M950 F0 C"fan0" Q500                           ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1                                 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500                           ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1 T45                              ; set fan 1 value. Thermostatic control is turned on
 
;M106 P0 S0 I0 F100 H-1 C"Print Cooling"     ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
;M106 P1 S1 I0 F100 H1 T45 C"Heatsink"       ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
 
; Tools
M563 P0 D0 H1                               				; Define tool 0
G10 P0 X0 Y0 Z0                             				; Set tool 0 axis offsets
G10 P0 R0 S0                                				; Set initial tool 0 active and standby temperatures to 0C
 
; Automatic saving after power loss is not enabled
 
; Custom settings are not configured
M572 D0 S0.1												; Pressure Advance
;M591 D0 P2 C4 S1											; Activate filament sensor
M404 N1.75 													; Set for print monitor
M592 D0 A0.07772 B-0.00029 									; Nonlinear extrusion. Set parameters for extruder drive 0
 
; Miscellaneous
M501                                               			; Load saved parameters from non-volatile memory

[Phaedrux]

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

G29 S1

Don't load the heightmap in config.g. It should only ever be loaded or freshly created after probing the bed with G30 to set Z0.

What do you have in bed.g and homedelta.g?

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