error upgrading

PeterA

When using the configurator the z option for piezo remains greyed out. So i used the old settings???

Veti

post the output of M119

fcwilt

it works either way.

M574 Z1 S2
is what the configurator creates for z probe on version 3.

but as i said more important is the homing script.

Son of a gun. That's confusing.

Turns out, at least on 3.2 that M574 Z0 or M574 Z1 S2 or M574 Z2 S2 works.

It even worked with no M574 referencing Z at all.

Thanks.

Frederick

Phaedrux

@fcwilt said in error upgrading:

It even worked with no M574 referencing Z at all.

Which makes complete sense since G30 only cares about M558 and G31. M574 is for endstops.

Phaedrux

@PeterA said in error upgrading:

; ##### Z-Probe Precision Piezo #####
; ===================
M558 P5 C"^zprobe.in" H5 F450 T5000 ; set Z probe type to switch and the dive height + speeds
G31 P500 X0 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 X10:328 Y10:210 S20 ; define mesh grid
; ==============================================
; ##### Z-Probe old 2.05 Firmware working Settings #####
;==============================================
; M558 P8 R1 I1 H5 F450 T5000 ; Set Z probe type to inverted, unfiltered piezo and the dive height + speeds
; G31 P500 X0 Y0 Z0 ; Set Z probe trigger value, offset and trigger height
; M557 X10:328 Y10:210 P5 ; Define mesh grid

In your 2.05 config for the piezo you have it inverted and P8 probe type. To do the same in 3.2 you'd add a ! to the pin name. Try this.

M558 P8 C"^!zprobe.in" H5 F450 T5000 R1

That would match your previous settings.

You should also check your config.g syntax by sending M98 P"config.g" This will report any errors that may get lost during startup.

PeterA

Sorry guys had an internet issue. Bust testing now

fcwilt

@Phaedrux said in error upgrading:

Which makes complete sense since G30 only cares about M558 and G31. M574 is for endstops.

I agree but when homing with z probe the documentation states that for v2 M574 Z1 S2 is needed and for v3 M574 Z0 is needed.

So something is out of sync - the firmware is right and the docs wrong or vice versa.

Curious. Thanks.

Frederick

PeterA

@Phaedrux
Thanks. Sorry I've been making so many changes following some of the other guys. Just getting seriously lost.
I tried your suggestion and now i at least get an error:
When homing the Z it says :

1/21/2021, 6:44:30 PM Error: Z probe already triggered at start of probing move
Error: Homing failed

I'm really getting a bit lost. Can you see any mistakes ?

Also the M98 P"config.g" reports this;
1/21/2021, 6:52:01 PM M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled

So I've changed my config.g to the following:

; ##### Endstops ######
;======================
M574 X1 S1 P"!xstop" ; configure active-high endstop for low end on X via pin !xstop
M574 Y1 S1 P"!ystop" ; configure active-high endstop for low end on Y via pin !ystop
M558 P8 C"^zprobe.in" H5 F450 T5000 R1 ; set Z probe type to switch and the dive height + speeds

; ##### Z-Probe Precision Piezo #####
; ==================================
G31 P500 X0 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 X10:328 Y10:210 S20 ; define mesh grid
; M557 X10:328 Y10:210 P5 ; Define mesh grid

and my homeall.g looks like this

; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.2.2 on Thu Jan 21 2021 05:12:36 GMT+0200 (South Africa Standard Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-370 Y-250 F1800 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 H2 X5 Y5 F6000 ; go back a few mm
G1 H1 X-370 Y-250 F1800 ; move slowly to X and Y axis endstops once more (second pass)
G90 ; absolute positioning
G1 X10 Y10 F6000 ; go to first bed probe point and home Z
G30 ; home Z by probing the bed

; Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning

Veti

@PeterA said in error upgrading:

M558 P8 C"^zprobe.in" H5 F450 T5000 R1 ; set Z probe type to switch and the dive height + speeds

as phaedrux says change to
M558 P8 C"^!zprobe.in" H5 F450 T5000 R1 ; set Z probe type to switch and the dive height + speeds

when you issue M119 you can see that the probe is already triggerd. the ! inverts the signal

PeterA

@Veti said in error upgrading:

M558 P8 C"^!zprobe.in" H5 F450 T5000 R1

Yes Awesome !!!! it works,
Cant thank you all enough for being helpful. Now i can sleep.

Phaedrux

@fcwilt said in error upgrading:

I agree but when homing with z probe the documentation states that for v2 M574 Z1 S2 is needed and for v3 M574 Z0 is needed.
So something is out of sync - the firmware is right and the docs wrong or vice versa.

Where does it say that?

In the notes for M574 in the wiki it has this:

The S2 option of M574 is intended for use only when axes other than Z are using the Z probe for homing. The only printers known that do this using Duet electronics are the RepRapPro Ormerod, Huxley Duo, and Mendel Tricolour machines. When using the Z probe to home Z, M574 Z0 should be used.

And even that has an asterix, because you can define an endstop (for zmax for instance) and use either the probe or the endstop depending on what you call to home at the time. G1 H1 or G30.

PeterA

Great Product and fantastic help.

fcwilt

@Phaedrux said in error upgrading:

Where does it say that?

The S2 option of M574 is intended for use only when axes other than Z are using the Z probe for homing. The only printers known that do this using Duet electronics are the RepRapPro Ormerod, Huxley Duo, and Mendel Tricolour machines. When using the Z probe to home Z, M574 Z0 should be used.

Or am I misreading what it says?

Frederick

Phaedrux

@fcwilt Yes it does. I'll complete that sentence to include, unless you have another use for the z endstop, such as homing to Z max. Technically it could be left undefined. M574 doesn't have any bearing over the probe setup itself.

Veti

i find the M574 Z1 S2 setup helpful when reading other peoples config.
it tells me that they generated the config with a z probe.

if left empty they could have selected none.

Phaedrux

@Veti Yes, and I think that's why the config tool sets it that way for clarity more than anything else.

fcwilt

@Phaedrux said in error upgrading:

@Veti Yes, and I think that's why the config tool sets it that way for clarity more than anything else.

Rather than say it should be something specific like M574 Z0 (which does nothing) perhaps the docs should simply state what is actually true with regards to how the firmware uses M574.

Including superfluous code is not my idea of clarifying things.

Thanks.

Frederick

Phaedrux

@fcwilt It now says

When using the Z probe to home Z, M574 Z has no bearing on the probe setup or usage. A Z probe and a Z endstop can both be configured at the same time. G30 calling the probe setup with M558, and G1 H1 Z moves calling the endstop configured with M574 Z.

fcwilt

@Phaedrux said in error upgrading:

@fcwilt It now says

When using the Z probe to home Z, M574 Z has no bearing on the probe setup or usage. A Z probe and a Z endstop can both be configured at the same time. G30 calling the probe setup with M558, and G1 H1 Z moves calling the endstop configured with M574 Z.

That seems to clear up things nicely.

Good job and thanks.

Frederick