[solved] BL-Touch deploy only one time with 2.03RC1
-
Hi there, (Hi DC)
I'm trying the last RC1 build but I faced this issue. ( On this printer https://forum.duet3d.com/topic/8397/tevo-little-monster-duetwifi-touch7-my-conversion)
When I launch the calibration the BL-Touch produce the fist trigger (down and up the pistil) (in general are at least 2 cycle) ,then stop retracted . The consequence is that in the second attempt the head crash on the glass. At that time the STOP button didn't work and I have to power down the printer.
Is not a nice view see the nozzle dig for the glass.
Is not possible add a "real" stop on the 7" touch also during the calibration?
I can reproduce all this.
On the 2.02 stable this don't occur. -
When I launch the calibration the BL-Touch produce the fist trigger (down and up the pistil) (in general are at least 2 cycle) ,then stop retracted . The consequence is that in the second attempt the head crash on the glass. At that time the STOP button didn't work and I have to power down the printer.
Check that you don't have any explicit deploy or retract commands in your bed.g file.
Is not possible add a "real" stop on the 7" touch also during the calibration?
I think your PanelDue firmware is out of date.
-
My bed.g
Do you see something wrong? (sorry i dont talk G-Code so much
); bed.g
; called to perform automatic delta calibration via G32
;
M280 P3 S160 I1 ; clear all BL-touch errors
M561 ; clear any bed transform , all g32 previous calibrations
G29 S2 ; disable bed compensation , must come after M561 and are related.
G28 ; home all tower
;G0 Z400 ; Move while giving the BLTouch time to clear the error
; Before running this, you should have set up your Z-probe trigger height to suit your build, in the G31 command in config.g.
M98 Pdeployprobe.g ; (this in the file M280 P3 S90 I1 ); For G30: 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 center of bed); Bed center, main trigger height 1.xxx - sottrarre all'altezza centrale le altezze per ciascun punto e mettere la differenza positiva o negativa come altezza nei vari G30.
; bed.g file for RepRapFirmware, generated by Escher3D calculator
; 16 points, 6 factors, probing radius: 140, probe offset (0, 20)
G30 P0 X0.00 Y122.50 Z-99999 H0.074 ; 1.255-1.181=0.074
G30 P1 X80.84 Y96.34 Z-99999 H0.21 ; 1.391-1.181=0.21
G30 P2 X133.29 Y23.50 Z-99999 H0.102 ; 1.283-1.181=0.102
G30 P3 X121.24 Y-70.00 Z-99999 H0.084 ; 1.265-1.181=0.084
G30 P4 X47.88 Y-131.56 Z-99999 H-0.014 ; 1.167-1.181=-0.014
G30 P5 X-47.88 Y-131.56 Z-99999 H-0.123 ; 1.058-1.181=-0.123
G30 P6 X-121.24 Y-70.00 Z-99999 H-0.1 ; 1.003-1.181=-0.178 schiaccia troppo quindi -0.1
G30 P7 X-133.29 Y23.50 Z-99999 H-0.1 ; 0.975-1.181=-0.206 schiaccia troppo quindi -0.1
G30 P8 X-80.84 Y96.34 Z-99999 H-0.133 ; 1.048-1.181=-0.133 schiaccia troppo quindi 0.05
G30 P9 X0.00 Y54.44 Z-99999 H0.057 ; 1.238-1.181=0.057
G30 P10 X51.84 Y29.93 Z-99999 H0.113 ; 1.294-1.181=0.113
G30 P11 X60.62 Y-35.00 Z-99999 H0.03 ; 1.211-1.181=0.03
G30 P12 X0.00 Y-70.00 Z-99999 H-0.038 ; 1.143-1.181=-0.038
G30 P13 X-60.62 Y-35.00 Z-99999 H-0.139 ; 1.042-1.181=-0.139 ???
G30 P14 X-51.84 Y29.93 Z-99999 H-0.05 ; 1.131-1.181=-0.05 ???
G30 P15 X0 Y0 Z-99999 S6 ; 1.181 or S9 for diagonal rod calculation and more parameters; 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 center of bed)M98 Pretractprobe.g ; (this in the file M280 P3 S90 I1)
;G29 run mesh grid compensation. Grid calibration. And cannot be used if the H parameter are necessary
G28
;G1 X0 Y0 Z150 F15000 S2You are right , my version is 1.17.
I checked the new version here ... https://github.com/dc42/PanelDueFirmware/releases
I'll update it now.Thanks
-
@giostark said in BL-Touch deploy only one time with 2.03RC1:
M98 Pdeployprobe.g ; (this in the file M280 P3 S90 I1 )
Try removing this.
-
Following instructions here https://miscsolutions.wordpress.com/paneldue/
Update success to the 1.23.2!Thanks Phaedrux , you nailed it
I read somewhere in the "whats-new " that during the probe some deploy and retraction now are automated. Is correct?
I had an old configuration that add a surplus command that block the proper triggering , right?
Just for understand what happened.Thanks again.
I'll mark the 3d as solved.
-
@giostark said in [solved] BL-Touch deploy only one time with 2.03RC1:
I read somewhere in the "whats-new " that during the probe some deploy and retraction now are automated. Is correct?
That's correct. For some types of probe, when running bed.g you want to deploy and retract the probe just once in the entire sequence, which you can do using M401 near the start of bed.g and M402 near the end. But that's not the case for BLTouch, which needs to be deployed separately before every probe point. So leave the firmware to deploy/retract it automatically.
