Bed leveling Anycubic Predator Delta
-
I'm stumped on this.
I upgraded recently to RRF3.0. Applied all of my parameters to the RRF configtool:
I run auto calibration and the z probe isnt diving and delivers Error: Z-probe already triggered at start of probing move.
I'm using the original anycubic predator microswitch z-probe.
; Configuration file for Duet WiFi (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v2.1.8 on Fri Apr 03 2020 13:10:48 GMT-0400 (Eastern Daylight Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Anycubic Predator" ; set printer name M665 R225 L440 B177 H452.25 ; Set delta radius, diagonal rod length, printable radius and homed height M666 X0 Y0 Z0 ; put your endstop adjustments here, or let auto calibration find them ; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0 S1 ; physical drive 0 goes forwards M569 P1 S1 ; physical drive 1 goes forwards M569 P2 S1 ; physical drive 2 goes forwards M569 P3 S1 ; physical drive 3 goes forwards M584 X0 Y1 Z2 E3 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z80.00 E663.00 ; set steps per mm M566 X1200.00 Y1200.00 Z1200.00 E1200.00 ; set maximum instantaneous speed changes (mm/min) M203 X18000.00 Y18000.00 Z18000.00 E1200.00 ; set maximum speeds (mm/min) M201 X1000.00 Y1000.00 Z1000.00 E1000.00 ; set accelerations (mm/s^2) M906 X1000 Y1000 Z1000 E800 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 Z0 S1 ; set minimum Z ; Endstops M574 X2 S1 P"xstop" ; configure active-high endstop for high end on X via pin xstop M574 Y2 S1 P"ystop" ; configure active-high endstop for high end on Y via pin ystop M574 Z2 S1 P"zstop" ; configure active-high endstop for high end on Z via pin zstop ; Z-Probe M558 P5 C"zprobe.in+zprobe.mod" H5 F120 T6000 ; set Z probe type to switch and the dive height + speeds M558 H30 ;*** Remove this line after delta calibration has been done and new delta parameters have been saved G31 P500 X0 Y0 Z16.95 ; set Z probe trigger value, offset and trigger height M557 R160 S20 ; define mesh grid ; Heaters M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0temp M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1 M143 H1 S280 ; set temperature limit for heater 1 to 280C M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit ; 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 ; Tools M563 P0 D0 H1 F0 ; 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 ; Custom settings are not defined ; Miscellaneous M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss ; bed.g ; called to perform automatic delta calibration via G32 ; ; generated by RepRapFirmware Configuration Tool v2.1.8 on Fri Apr 03 2020 13:10:48 GMT-0400 (Eastern Daylight Time) M561 ; clear any bed transform ; Probe the bed at 6 peripheral and 6 halfway points, and perform 6-factor auto compensation ; Before running this, you should have set up your Z-probe trigger height to suit your build, in the G31 command in config.g. G30 P0 X0 Y169.9 H0 Z-99999 G30 P1 X147.14 Y84.95 H0 Z-99999 G30 P2 X147.14 Y-84.95 H0 Z-99999 G30 P3 X0 Y-169.9 H0 Z-99999 G30 P4 X-147.14 Y-84.95 H0 Z-99999 G30 P5 X-147.14 Y84.95 H0 Z-99999 G30 P6 X0 Y84.9 H0 Z-99999 G30 P7 X73.53 Y42.45 H0 Z-99999 G30 P8 X73.53 Y-42.45 H0 Z-99999 G30 P9 X0 Y-84.9 H0 Z-99999 G30 P10 X-73.53 Y-42.45 H0 Z-99999 G30 P11 X-73.53 Y42.45 H0 Z-99999 G30 P12 X0 Y0 H0 Z-99999 S6 ; Use S-1 for measurements only, without calculations. Use S4 for endstop heights and Z-height only. Use S6 for full 6 factors ; If your Z probe has significantly different trigger heights depending on XY position, adjust the H parameters in the G30 commands accordingly. The value of each H parameter should be (trigger height at that XY position) - (trigger height at centre of bed) -
@gperman said in Bed leveling Anycubic Predator Delta:
M558 P5 C"zprobe.in+zprobe.mod" H5 F120 T6000 ; set Z probe type to switch and the dive height + speeds
I think you may need to invert the probe signal pin. Which I think in your case would be
M558 P5 C"!zprobe.in+zprobe.mod" H5 F120 T6000
-
inverting the probe signal worked to make the effector dive but it kept diving well after the probe triggered and kept going. Had to perform an emergency shutoff.
Now to figure out why the steppers didn't cut off after the probe triggered.I tested the probe, it passes a continuity test and shows to be normally closed and is connected to e0 as per the config tool's instructions.
perhaps the extra M558 command is messing something up. Going to remove and try again.
-
Removing M558 H30 did not solve the issue.
I am currently running g29 and triggering the probe prematurely to see if it stops the carriage which it does not. Otherwise, I believe it would continue on and crash into the bed. I would not like to find that out the hard way.Can someone define or walk me through how to actually level a bed using an Anycubic Predator microswitch Z probe?
I assume the main function for determine the level of the bed is g29 which appears in the dropdown menu of Auto Calibration.
I have tried multiple codes in the config m558 P4, P5, C"e0stop", C3...
on duet web control the e0 endstop hit shows no change. The z probe stays at 1000, no change.Tested the switch through the harness all the way to the connector that shows normally closed still and switching when pressed. Plus the e0 LED blinks when the switch is pressed. It's just not recognized in the software.
-
Is that a probe that you have to attach to the print head before using it?
-
@Phaedrux yes.
Also, i got the probe to recognize and change values in the interface by depinning and connecting it to the z probe connector on the board instead of e0.
It starts at 0 and displays 1000 when triggered.
Have not seen an effect on anything from adding ! As suggested.
I need to try and see if the single z probe g code command works. I’m going to have to risk it potentially ramming into the bed i guess.Triggering the z probe whilst manually jogging the axes down does not stop the effector which is not encouraging.
Ran G32 which did not touch the bed. Perhaps i am misunderstanding "probing." does the effector just glide along the bed? It doesn't stop at each point, dive down until the probe triggers then rise again like it did on the factory firmware/board.
I assumed setting up the config tool using a microswitch would result in a behavior similar to the factory setup.
I lowered G31 Z16.95 to Z12. The probe touches the bed now but I get an Error: Z probe already triggered at start of probing move.
-
Yea, still havent figured this out. Ran bed.g as a macro, ran G29, G30, G31, G32. The probe just moves around to the XY coordinates but doesnt stop, doesnt dive, doesnt probe.
I have no idea why.
-
Is the switch normally open or normally closed?
Do you have it connected to the in and ground terminals of the z probe connector?Use,
M558 P5 C"zprobe.in" H5 F120 T6000
I don't think you need the modulation pin because this isn't an analogue probe. -
-
I'm just going from this: https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_Mode_Num_5
-
@Phaedrux said in Bed leveling Anycubic Predator Delta:
Is the switch normally open or normally closed?
Do you have it connected to the in and ground terminals of the z probe connector?Use,
M558 P5 C"zprobe.in" H5 F120 T6000
I don't think you need the modulation pin because this isn't an analogue probe.YES! This solved it! Thank you so much. This was a huge headache.
Removing the zprobe.mod allowed it to recognize as a digital switch instead of analogue and now it probes.
-
Glad that worked. I think the issue is that the configurator has the zmod pin selected by default and it's not easy to know beforehand what it is and why it's selected and that you should actually unassign it.
I think I'm going to suggest that it is unassigned by default in the configurator.
-
Or selectable by a check box in the z probe section under endstops.
