Configuration Z-Probe

peirof

Think... that this can't use it....

i'd like check if Z-Probe stops the movements, with calibrate...no stops... but i wat check if, with normal movements, G1, the zprobe stops the head movement. I have cheked, that Z-Probe(Mini Ir) is reconiced by Duet, when i close some object to Mini IR, in DWC, can see how the field Zprobe raises until 46x... but.... when i calibrate the printer... and trigger Zprobe, dont stops the movement....

For this .... i want check, with G1 flag, in Zprobe is well reconiced...

Its supposed, with cartesian printer type, if gcode, G1 Z-200 S1, move the head 200 mm downwards, if Zprobe its triggered, the movement must stop. No? but with a Delta printer, this flag S1 don't work.... There is similar flag for a Delta?

dc42

You are confusing an endstop switch with a Z probe. G1 S1 commands are for use with endstop switches, not with a Z probe.

Stealthy_TT

@dc42

And iirc s2 is for z probe right? I’m not home to check my config for it but that’s what I believe i set for mine.

dc42

To use a Z probe for Z homing, use a G30 command, not a G1 S2 command. See the first item in https://duet3d.dozuki.com/Wiki/FAQ.

Stealthy_TT

@dc42

You are correct but I’m sure you already knew that haha. I have a g30 command in homeall.g

peirof

Hi,

after some test... i have cheked when i send G30 S-1, and put an obstacle in ZProbe.... *** STOPS THE HEAD MOVEMENT***... this discards a fault to Zprobe, and bad conection....

IF:

When printer power on, ZProbe blinks correct.
When by console send G30 S-1, printer head stops with a obstacle
When try calibrate, Zprobe DON'T stops printer head movement...

Why?

A- Something is wrong in bed.g?
B- Something is wrong in config.g?
C- Le falla "lajuntadelatrocola"

What can i do?

Latest test are made with Mini IR

Copy bed.g i am using

*; bed.g
; called to perform automatic delta calibration via G32

M561 ; clear any bed transform, otherwise homing may be at the wrong height
G28 ; home the printer

; bed.g file for RepRapFirmware, generated by Escher3D calculator
; 16 points, 6 factors, probing radius: 140, probe offset (0, 0)
; bed.g file for RepRapFirmware, generated by Escher3D calculator
; 16 points, 6 factors, probing radius: 125, probe offset (0, 0)

G30 P0 X-67,5 Y117 Z-9999 H0
G30 P1 X67,5 Y117 Z-9999 H0
G30 P2 X135 Y0 Z-9999 H0
G30 P3 X67,5 Y-117 Z-9999 H0
G30 P4 X-67,5 Y-117 Z-9999 H0
G30 P5 X-135 Y0 Z-9999 H0
G30 P6 X0 Y-90 Z-9999 H0
G30 P7 X-77,95 Y-45 Z-9999 H0
G30 P8 X-77,95 Y45 Z-9999 H0
G30 P9 X0 Y90 Z-9999 H0
G30 P10 X77,95 Y45 Z-9999 H0
G30 P11 X77,75 Y-45 Z-9999 H0
G30 P12 X0 Y45 Z-9999 H0
G30 P13 X22,5 Y0 Z-9999 H0
G30 P14 X-22,5 Y0 Z-9999 H0
G30 P15 X0 Y0 Z-9999 S6*

Stealthy_TT

@peirof said in Configuration Z-Probe:

Hi,

after some test... i have cheked when i send G30 S-1, and put an obstacle in ZProbe.... *** STOPS THE HEAD MOVEMENT***... this discards a fault to Zprobe, and bad conection....

IF:

When printer power on, ZProbe blinks correct.

When by console send G30 S-1, printer head stops with a obstacle

When try calibrate, Zprobe DON'T stops printer head movement...

Why?

A- Something is wrong in bed.g?
B- Something is wrong in config.g?
C- Le falla "lajuntadelatrocola"

What can i do?

Latest test are made with Mini IR

Copy bed.g i am using

*; bed.g
; called to perform automatic delta calibration via G32

M561 ; clear any bed transform, otherwise homing may be at the wrong height
G28 ; home the printer

; bed.g file for RepRapFirmware, generated by Escher3D calculator
; 16 points, 6 factors, probing radius: 140, probe offset (0, 0)
; bed.g file for RepRapFirmware, generated by Escher3D calculator
; 16 points, 6 factors, probing radius: 125, probe offset (0, 0)

G30 P0 X-67,5 Y117 Z-9999 H0
G30 P1 X67,5 Y117 Z-9999 H0
G30 P2 X135 Y0 Z-9999 H0
G30 P3 X67,5 Y-117 Z-9999 H0
G30 P4 X-67,5 Y-117 Z-9999 H0
G30 P5 X-135 Y0 Z-9999 H0
G30 P6 X0 Y-90 Z-9999 H0
G30 P7 X-77,95 Y-45 Z-9999 H0
G30 P8 X-77,95 Y45 Z-9999 H0
G30 P9 X0 Y90 Z-9999 H0
G30 P10 X77,95 Y45 Z-9999 H0
G30 P11 X77,75 Y-45 Z-9999 H0
G30 P12 X0 Y45 Z-9999 H0
G30 P13 X22,5 Y0 Z-9999 H0
G30 P14 X-22,5 Y0 Z-9999 H0
G30 P15 X0 Y0 Z-9999 S6*

Did you also place the code for z probe in homedelta?

Dougal1957

@peirof why is there a * on the s6 param on the last line ?

peirof

Hi,

In homedelta.g... it's mecessary place code? Homing a Delta, there is with endstops, No?...

Delta dont use Zprobe for Homing. No?

Dougal1957

@peirof No delta doesn't use the Z Probe for homing.

peirof

@dougal1957

eee... i have try to put that text in Italic, with forum web app... but dont reconised...

the *, there isn't in bed.g...

Dougal1957

@peirof OK it just looked strange!

dc42

Please test the Z probe with a G30 command as described at https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe.

Stealthy_TT

@dougal1957 said in Configuration Z-Probe:

@peirof No delta doesn't use the Z Probe for homing.

Makes sense, like I said above I don’t have a delta. Now I know.

Dougal1957

@stealthy_tt yeah on a delta it always homes to max Z so the probe can't be any further away from the bed if you tried but if you've never had one then you wouldn't know that fact

peirof

@dc42

Hi... I haved do these test, send by console G30 S1... and zprobes WORKS.. Míni Ir and Bltouch.... But calibrate dont works

peirof

What test i can do for discard problems?

So far, from the tests I have done, I think two things can be ruled out:

1- That the z-probes (both BlTouch / Mini IR) are damaged
2- That is a problem of the wiring

It seems an error in the configuration .... but I have checked it several times, and it seems that everything is fine ....

One test I can do is change the firmware, although I do not think that's the case, since the Z-Probes, were working with this.

dc42

So bed probing works when you do a single G30 without parameters - correct?

If yes, but the hot end crashes into the bed when you run G32 to auto-calibrate a delta, then the crash is probably occurring not when actually probing, but when the firmware positions the probe at the desired XY coordinates with Z=dive height. The solution is:

Check that your tower steps/mm is correct. 200mm of commanded Z movement should produce 200mm of movement.
Check that the homed height (H parameter in the M665 command) is equal to the height of the nozzle above the bed when all 3 endstop switches are triggered, to within 10mm or better. Make sure the value in config.g is not being overridden by another M665 command in config-override.g.
Until you have determined the correct M665 parameters, increase the dive height (H parameter in M558) to a large value, for example 50mm.

peirof

@dc42 said in Configuration Z-Probe:

the hot end crashes into the bed when you run G32 to auto-calibrate a delta, then the crash is probably occurring not when actually probing, but when the firmware positions the probe at the desired XY

Hi,

until 1 hour ago, i have no test.... but seems to be this

"...Until you have determined the correct M665 parameters, increase the dive height (H parameter in M558) to a large value, for example 50mm...."

thanks Steve....

P.D.: If you come to Valencia (Spain), you are invited to a" Paella Valenciana".

dc42

@peirof said in Configuration Z-Probe:

P.D.: If you come to Valencia (Spain), you are invited to a" Paella Valenciana".

The black rice one? My favourite sort!