multiple Z-Probe trigger heights in config-override.g

benecito

@fcwilt In theory you are right
But there are occasions where you might want to (or need to) change them. And I don't want my customers to go into config or alike but only use G-Code commends. And they will most likely need to change them at some point.

fcwilt

@benecito said in multiple Z-Probe trigger heights in config-override.g:

@fcwilt In theory you are right
But there are occasions where you might want to (or need to) change them. And I don't want my customers to go into config or alike but only use G-Code commends. And they will most likely need to change them at some point.

So you think that limiting customers to executing G-code commands will prevent them from messing things up?

Never underestimate the power of a customer to mess things up. Some of them seem to view it as a challenge

Frederick

benecito

@fcwilt said in multiple Z-Probe trigger heights in config-override.g:

So you think that limiting customers to executing G-code commands will prevent them from messing things up?

Never underestimate the power of a customer to mess things up. Some of them seem to view it as a challenge

Well, the beautiful thing about my setup is, they need a password for it. But I'm sure someone will try hard enough to manage to mess something up
Still I don't want to make it too easy

benecito

So there is no way to do this? I mean you can set it in config-override for one probe and you can create multiple probes. Would it not make sense to store the values for all the probes in config-override?
Not jet implemented, not planned or did I do something wrong?
@dc42 @Phaedrux

Phaedrux

I'm not sure if the mechanism for M500 P31 to save multiple probes is implemented yet. The multiprobe feature is still quite new. I'll see where it's at.

dc42

@phaedrux said in multiple Z-Probe trigger heights in config-override.g:

I'm not sure if the mechanism for M500 P31 to save multiple probes is implemented yet. The multiprobe feature is still quite new. I'll see where it's at.

Yes the code is written to save the trigger heights of multiple Z probes.

dc42

... and it is working for me:

; config-override.g file generated in response to M500 at 2021-07-27 19:07
; This is a system-generated file - do not edit
; Delta parameters
M665 L361.676:361.676:361.676 R180.659 H470.213 B150.0 X-0.308 Y-0.171 Z0.000
M666 X-1.052 Y0.116 Z0.936 A0.37 B0.07
; Heater model parameters
M307 H0 R0.197 C1182.100:1182.100 D2.40 S1.00 V0.0 B0 I0
M307 H1 R8.030 C99.000:99.000 D0.70 S1.00 V24.0 B0 I0
; Z probe parameters
G31 K0 P100 X0.0 Y0.0 Z-0.10
G31 K1 P500 X0.0 Y0.0 Z0.70
; Workplace coordinates
G10 L2 P1 X0.00 Y0.00 Z0.00
G10 L2 P2 X0.00 Y0.00 Z0.00
G10 L2 P3 X0.00 Y0.00 Z0.00
G10 L2 P4 X0.00 Y0.00 Z0.00
G10 L2 P5 X0.00 Y0.00 Z0.00
G10 L2 P6 X0.00 Y0.00 Z0.00
G10 L2 P7 X0.00 Y0.00 Z0.00
G10 L2 P8 X0.00 Y0.00 Z0.00
G10 L2 P9 X0.00 Y0.00 Z0.00

benecito

@dc42
Is it working in the 3.4 beta or in 3.3 as well? I tried on 3.3 the day I posted it, but it didn‘t work for me - if I had two probes it only saved one on them.
But if it should work on 3.3 I‘ll try again!

dc42

@benecito I tested in 3.4beta, however I don't recall changing that area of code between 3.3 and 3.4beta.

benecito

@dc42
Thanks I‘ll try as soon as I find time and get back to you if needed.