Need help with my delta please.
-
Then you need to update your G31 Z value with your trigger height as well as the XY offsets.
-
This post is deleted! -
@phaedrux how i can send you a vid3o ?
-
-
What commands are you running in that video? G32?
-
@phaedrux I only select the auto calibrate option in the DWB I suppose it is G32
-
Are you getting any error messages along with whatever is happening at the end of the video?
Have you updated your G31 in config.g to reflect the Z probe trigger height you measured of 0.7? That value also seems very low for a BLTouch. The Bltouch should be mounted with the base of the probe body ~8mm above the nozzle tip which leads to a trigger height of ~2mm.
You should remove these commands from your bed.g
M98 Pretractprobe.g
M98 Pdeployprobe.g -
@phaedrux I already removed the lines from bed.g
In the calibration it performs 5 calibration points and then fails.
I got the height of the probe going down to z5 and then sending G30 S-1 and it gives me that result.I already removed the lines from bed.g
In the self-calibration, it performs 5 calibration points and then fails.
I got the height of the probe going down to z5 and then sending G30 S-1 and it gives me that result
Is there any chance that one of the motors is damaged?
-
You've used this to get the trigger height?
Do the motors seem to move correctly otherwise?
If you remove the G29 from the end of bed.g does it complete successfully?
-
@phaedrux
yes I adjust the height of the probe with those instructions.here is the problem that repeats and repeats always.
https://drive.google.com/file/d/1CRUkoarxwDTyzyN0s4D9dpJEInlRXRzh/view?usp=sharing
im delet G29 from bed.g and nothing change
-
If looks like you're having some mechanical binding issues on that one tower. If you disconnect the belts are you able to move the carriage freely? If you disconnect the rods you can use G1 H2 commands to test individual towers.
A good place to start would be double checking all assembly and wiring.
https://docs.duet3d.com/en/User_manual/Tuning/Delta_calibration
-
2 weeks ago I had already been able to print, but I had a problem in z that did not go up correctly and the nozzle collided with the print.
From that I started to make modifications, updates and that was when it started to fail like this -
This post is deleted! -
when I individually move the motors if they work, that's why I think the problem may be in the code
-
@phaedrux
something new, try to print something and this happens:17/2/2022, 17:25:22 Error: Probe was not triggered during probing move
Error: in GCode file line 43: M280: missing parameter 'P'
17/2/2022, 17:24:52 Error: in GCode file line 31: M280: missing parameter 'P'
17/2/2022, 17:24:50 Error: in GCode file line 27: M280: missing parameter 'P' -
@fcwilt said in Need help with my delta please.:
Does your deployprobe.g file still have the M280 160 in it?
If so remove that line and remove the I1 from the line above it. -
@alankilian
im delete that line and this happen:17/2/2022, 17:41:37 Error: Probe was not triggered during probing move
Error: in GCode file line 43: M280: missing parameter 'P'
17/2/2022, 17:41:10 Error: Bad command: deploy BLTouch
17/2/2022, 17:41:07 Error: in GCode file line 31: M280: missing parameter 'P'
17/2/2022, 17:41:05 Error: in GCode file line 27: M280: missing parameter 'P' -
So this happens when you start a print?
Please post the first 40 lines of your print GCODE.
-
;FLAVOR:Repetier
;TIME:822
;MINX:-13.8
;MINY:-13.8
;MINZ:0.3
;MAXX:13.8
;MAXY:13.8
;MAXZ:19.9
;Generated with Cura_SteamEngine 4.2.1
M190 S60
M104 S200
M109 S200
M82 ;absolute extrusion mode
M280 S10.6
G28
M280 S3
G1 Z50 F25000
G92 E0
G1 F200 E3
G92 E0
G30 Z1.2
M280 S7
G1 X0 Y0 Z100
M42
M141 S28
G92 E0
G92 E0
G1 F1800 E-5
;LAYER_COUNT:99
;LAYER:0
M107
G0 F4320 X13.8 Y-10 Z0.3
;TYPE:SKIRT
G1 F1800 E0
G1 X13.8 Y10 E0.9978
G1 X13.76 Y10.55 E1.02532
G1 X13.641 Y11.088 E1.05281
G1 X13.445 Y11.603 E1.0803
G1 X13.177 Y12.084 E1.10777
G1 X12.843 Y12.522 E1.13525 -
@azaelaguirre OK, see those M280 commands in there?
You'll need to go to your slicer and figure out why its putting them in there and stop that action.
OR if they are required, modify your slicer code to add the pin number appropriately.
