Servo deployed probe on Duet Maestro
-
@Phaedrux said in Servo deployed probe on Duet Maestro:
@Veti said in Servo deployed probe on Duet Maestro:
change to C"^zprobe.in"
Veti suggested that, but you still have
@Blacksheep99 said in Servo deployed probe on Duet Maestro:
C"^!zprobe.in"
I tried it but when i then test G30 it fails immediately and tells me the probe is already triggered. Is this in relation to the G31 P500?
-
As I'm not familiar with this probe we might have to wait for Veti to weigh in as I'm not sure why it would be always detecting as triggered or never detecting as triggered.
-
@Phaedrux Can I just ask clarification on two things. H for Dive height. I have this set to 150 which is the height of the build volume. My reasoning is that the Z needs to raise 150 to meet the print heads but should stop when it triggers the probe?
Trigger height, is this the height of the probe above the nozzles when contact is made?
Thanks for helping, i really appreciate it
FYI. Retracted is 1000 (red box), deployed is 0 (grey background)
-
That's pretty excessive for dive height. As I mentioned before, the dive height should be just slightly more than your trigger height. So if your probe triggers when the nozzle is 3mm above the bed G31 Z3), you'd want you dive height to be at least 4mm for example (M558 H4).
-
@Blacksheep99 said in Servo deployed probe on Duet Maestro:
FYI. Retracted is 1000 (red box), deployed is 0 (grey background)
I'm not familiar enough with the probe to say if that is normal or not. I would have guessed that it should stay as untriggered regardless of deploy or retract status and only shown triggered when actually pushed up to break the optical beam.
-
@Phaedrux said in Servo deployed probe on Duet Maestro:
@Blacksheep99 said in Servo deployed probe on Duet Maestro:
FYI. Retracted is 1000 (red box), deployed is 0 (grey background)
I'm not familiar enough with the probe to say if that is normal or not. I would have guessed that it should stay as untriggered regardless of deploy or retract status and only shown triggered when actually pushed up to break the optical beam.
That logic makes sense. The way it looks to operate is that when retracted it is breaking the end stop beam (essentially triggered) but one deployed it is not and hence the state changes. One the probe is touched it causes the flag to break the beam and state changes to triggered.
-
When I home X,Y,Z are all 0,0,0 on the dashboard. Setting a low dive height only moves the bed up that height when I run G30. I should be aiming for the tip of the nozzles to be 0 for Z surely? Would this explain the issue?
-
The triggered status really only matters when doing the G30. So perhaps your probe isn't getting deployed early enough? When exactly are you getting the probe is triggered at start of probing move error?
What do you have in your homeall now? Remember that you are in control of the deploy and retract state now, which is a bit different than the BLTouch which automates that.
For homing and dive height you can also in control of how the print head is positioned before probing. If you need to raise the Z axis a bit to ensure that the probe has room you can do that in your homeall. It's already common to raise it a bit for clearance for X Y to home. Normally you'd only want to raise it just slightly more than the dive height to ensure there is clearance for the pin to drop.
-
look at the homeall script i posted
you need to run a M401 before the G30 and run a M402 afterwards.
I'm not familiar enough with the probe to say if that is normal or not. I would have guessed that it should stay as untriggered regardless of deploy or retract status and only shown triggered when actually pushed up to break the optical beam.
the probe is always triggerd in the retracted state. this is a good thing because if you forget to deploy or there is a problem it does not cause damage as it is triggered immediately
-
@Veti said in Servo deployed probe on Duet Maestro:
look at the homeall script i posted
you need to run a M401 before the G30 and run a M402 afterwards.
I'm not familiar enough with the probe to say if that is normal or not. I would have guessed that it should stay as untriggered regardless of deploy or retract status and only shown triggered when actually pushed up to break the optical beam.
the probe is always triggerd in the retracted state. this is a good thing because if you forget to deploy or there is a problem it does not cause damage as it is triggered immediately
So sorry to clarify things but I'm changing a few things.
I've done as you originally said and removed the inverted pin in the config.g for zprobe it now reports 1000 (red).
; Z-Probe M574 Z1 S1 ; Set endstops controlled by probe M950 S0 C"^zprobe.mod" ; create servo pin 0 for BLTouch M558 P8 C"^zprobe.in" H150 F900 T6000 ; Set Z probe type to switch and the dive height + speeds G31 P50 X-50 Y-8 Z1.5 ;Set Z probe trigger value, offset and trigger height M557 X15:265 Y15:135 S20 ; define mesh gridMy home all
G91 ; relative positioning G1 H2 Z5 F6000 ; lift Z relative to current position G1 H1 X-285 Y-155 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-285 Y-155 F360 ; move slowly to X and Y axis endstops once more (second pass) G1 H1 Z-155 F360 ; move Z down stopping at the endstop G90 ; absolute positioning M402 G92 Z0 ; set Z position to axis minimum (you may want to adjust this)When you say run M401 then G30 are you talking via the console to test its function? I just tried that and it reversed the bed down hitting the end stop and kept trying to go, I had to hit stop.
-
Your homeall isn't using the probe at all at this point, still just the endstop. Trying to control the probing manually isn't going to work very well. Better to script it out in the homing file at this point.
If you want to continue to use the Z endstop, that's fine. Here's what I would add.
M402 ; retract the pin just incase G91 ; relative positioning G1 H2 Z5 F6000 ; lift Z relative to current position G1 H1 X-285 Y-155 F1800 ; move quickly to X and Y axis endstops and stop there (first pass) G1 X5 Y5 F6000 ; go back a few mm G1 H1 X-285 Y-155 F360 ; move slowly to X and Y axis endstops once more (second pass) G1 H1 Z-155 F360 ; move Z down stopping at the endstop G90 ; absolute positioning G1 X105 Y150 Z5 F6000 ; move probe into position at bed center M401 ; deploy the probe G30 ; probe the bed M402 ; retract probe G1 X10 Y10 Z10 ; return to parked position -
@Phaedrux said in Servo deployed probe on Duet Maestro:
Your homeall isn't using the probe at all at this point, still just the endstop. Trying to control the probing manually isn't going to work very well. Better to script it out in the homing file at this point.
If you want to continue to use the Z endstop, that's fine. Here's what I would add.
M402 ; retract the pin just incase G91 ; relative positioning G1 H2 Z5 F6000 ; lift Z relative to current position G1 H1 X-285 Y-155 F1800 ; move quickly to X and Y axis endstops and stop there (first pass) G1 X5 Y5 F6000 ; go back a few mm G1 H1 X-285 Y-155 F360 ; move slowly to X and Y axis endstops once more (second pass) G1 H1 Z-155 F360 ; move Z down stopping at the endstop G90 ; absolute positioning G1 X105 Y150 Z5 F6000 ; move probe into position at bed center M401 ; deploy the probe G30 ; probe the bed M402 ; retract probe G1 X10 Y10 Z10 ; return to parked positionI feel stupid as the logic doesn't fit with my understanding. Home for the bed should be as far away from the nozzle as possible to my mind?
I've just tried your homeall and I get the probe already triggered message.
G28 Error: Z probe already triggered at start of probing moveWhy do I need the G30 at all in the homeall? It's homeall just to park the head and bed out of the way?
When I run a print that's when the printer should probe the bed shouldn't it? I thought this was G29 though.
-
try a G4 P500 after the M401
this will wait 500msec for the probe to deploy
-
@Veti said in Servo deployed probe on Duet Maestro:
G4 P500
Probe deploys okay now with no error however the bed goes down not up towards the print head. have to hit stop
-
Home is where the endstop is. You have a Z min endstop defined, so to trigger it, the nozzle must go to the bed.
Most basically G30 is how the probe is used to find the bed surface. It lets the firmware know where the bed is in relation to the nozzle, much the same way as the endstop, except that it's mobile in X and Y, so it can be used for other things as well such as creating a heightmap of the bed surface to adjust for.
Usually when you have a probe you don't use a Z endstop at all unless you want to use a Z max endstop for trying to recover after a power loss.
@Blacksheep99 said in Servo deployed probe on Duet Maestro:
however the bed goes down not up towards the print head. have to hit stop
I think your z axis is backwards. Your conception of homing away from the bed has confused you.
Can you post a photo of your bed?
Where is the Z endstop located?
Z- should make the bed and nozzle move closer together
Z+ should make them go farther apart. -
@Blacksheep99 said in Servo deployed probe on Duet Maestro:
Probe deploys okay now with no error however the bed goes down not up towards the print head. have to hit stop
have you made sure that you z movement is correct?
-
@Phaedrux said in Servo deployed probe on Duet Maestro:
Home is where the endstop is. You have a Z min endstop defined, so to trigger it, the nozzle must go to the bed.
Most basically G30 is how the probe is used to find the bed surface. It lets the firmware know where the bed is in relation to the nozzle, much the same way as the endstop, except that it's mobile in X and Y, so it can be used for other things as well such as creating a heightmap of the bed surface to adjust for.
Usually when you have a probe you don't use a Z endstop at all unless you want to use a Z max endstop for trying to recover after a power loss.
@Blacksheep99 said in Servo deployed probe on Duet Maestro:
however the bed goes down not up towards the print head. have to hit stop
I think your z axis is backwards. Your conception of homing away from the bed has confused you.
Can you post a photo of your bed?
Where is the Z endstop located?
Z- should make the bed and nozzle move closer together
Z+ should make them go farther apart.Okay I think the problem is between the printer and the PC! I had it in my head that +Z should move the bed towards the head not the other way around.
I'm using the Z switch for home as that is how the printer was built. I'm trying to repair it.
-
@Blacksheep99 said in Servo deployed probe on Duet Maestro:
I'm using the Z switch for home as that is how the printer was built. I'm trying to repair it.
with a z probe you dont need the switch anymore
-
@Veti said in Servo deployed probe on Duet Maestro:
@Blacksheep99 said in Servo deployed probe on Duet Maestro:
I'm using the Z switch for home as that is how the printer was built. I'm trying to repair it.
with a z probe you dont need the switch anymore
Okay, great so disconnect it and redefine things in my config.g? I noticed the first line of your zprobe commands had a line to define Z Endstops by zprobe, this is what you are referring to then?
-
Ok, that should help things a bit. Change the direction of rotation for the Z axis driver in your config.g with the M569 command
The endstop switch could be repurposed for a Z max endstop switch for using in power loss recovery. See what I mean here:
https://duet3d.dozuki.com/Guide/Ender+3+Pro+and+Duet+Maestro+Guide+Part+5:+Upgrades/54#s212
