5bar scara Problem configuring z probe using fsr switch
-
Have you tried using probe type 1 or 3?
What particular problem are you having?
Thanks.
Frederick
-
@fcwilt thanks for the fast response.
So I’m using type 5,(I followed the configurator tool, and the forum), and I set the input pin of the probe as the same as the z endstop(on the endstop pin not the probe). -
@gnmrc_ the thing i cannot find on the documents is how to make a z endstop switch run as z probe.
-
@gnmrc_ said in Problem configuring z probe using fsr switch:
@gnmrc_ the thing i cannot find on the documents is how to make a z endstop switch run as z probe.
The configurator tool is not great - it generates some wonky code at times.
A Z endstop and a Z probe are two totally different things. You can have one or the other or both.
As to the probe type of 5, that is for a "switch" with two states - on or off. Is that what you want the FSR to behave like?
You have to include two commands to configure a Z probe: M558 and G31
Do you have these? What do they look like?
Frederick
-
@fcwilt yes at the moment i want to run the fsr as an on of switch,this is my code at the moment:
; Endstops
M574 X2 S1 P"!xstop" ; configure switch-type (e.g. microswitch) endstop for high end on X via pin !xstop
M574 Y2 S1 P"!ystop" ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin !ystop
M574 Z1 S1 P"!zstop" ; configure switch-type (e.g. microswitch) endstop for low end on Z via pin !zstop; Z-Probe
M558 P5 C"!zstop" H5 F1800 T6000 ; set Z probe type to switch and the dive height + speeds
G31 P500 X0 Y0 Z0 ; set Z probe trigger value, offset and trigger height
M557 X-100:100 Y-100:100 S5 ; define mesh grid -
Comment out the line for the Z endstop and see if the Z probe works as expected. I don't think you can have two devices connected to the same input.
Frederick
-
@fcwilt, it works, thank you so much!!!
But now I have another problem, when I say to the machine to go to 0,0 it overshoots the target for no apparent reason, I also checked the code and it seems correct, do you have any idea? -
@gnmrc_ said in Problem configuring z probe using fsr switch:
@fcwilt, it works, thank you so much!!!
But now I have another problem, when I say to the machine to go to 0,0 it overshoots the target for no apparent reason, I also checked the code and it seems correct, do you have any idea?I thought about a step-per-degree error but I have checked and it's correct, 200(steps per revolutio)*128(microstepping)*25(reduction)/360=1777.777778
-
@gnmrc_ said in Problem configuring z probe using fsr switch:
@gnmrc_ said in Problem configuring z probe using fsr switch:
@fcwilt, it works, thank you so much!!!
But now I have another problem, when I say to the machine to go to 0,0 it overshoots the target for no apparent reason, I also checked the code and it seems correct, do you have any idea?I thought about a step-per-degree error but I have checked and it's correct, 200(steps per revolutio)*128(microstepping)*25(reduction)/360=1777.777778
When you say you checked it, do you mean the math above OR did you actually measure a known length of movement to see if it is correct.
For example, if the current X position is reported as 0, note the point on the bed where it is and then move to X=100. Measure from the 0 point to the 100 point.
Then do the same for Y.
In your math you show a 25 reduction - what is that?
Thanks.
Frederick
-
@fcwilt the reduction is used to increase the steps needed to complete a 1degree move(all 5barscaras actuated by steppers use this). The movement to the x0y0 is wrong because it moves outside the print area, while the 0,0 should be in the center.
-
@gnmrc_ said in Problem configuring z probe using fsr switch:
@fcwilt the reduction is used to increase the steps needed to complete a 1degree move(all 5barscaras actuated by steppers use this). The movement to the x0y0 is wrong because it moves outside the print area, while the 0,0 should be in the center.
Is whatever part is moving, moving in the wrong direction?
Post your config.g file please.
Frederick
-
@fcwilt no everything works as it should directionally-wise.
This is the config file: config.g
and this is the homing file:home5barscara.gThank you so much for the help!
-
@gnmrc_ said in Problem configuring z probe using fsr switch:
@fcwilt no everything works as it should directionally-wise.
This is the config file: config.g
and this is the homing file:home5barscara.gThank you so much for the help!
Unrelated to your problem but just FYI:
If you put M92 before M350 in the config file AND then use the values in M92 that are correct for 16x micro-stepping, any values you put in M350 make the needed adjustments to the M92 values "internally". So any future changes need only be made to M350.
Back to the problem:
So if everything is moving in the correct direction is it simply that it is not moving far enough?
Thanks.
Frederick
-
@fcwilt no it’s the opposite it overshoots the target.
-
@gnmrc_ said in Problem configuring z probe using fsr switch:
@fcwilt no it’s the opposite it overshoots the target.
Does it home correctly to each axis?
Frederick
-
@fcwilt yes it homes the left and right actuator, than want to home z positioning the arm at the center of the bed using G1 x0 y0 s2, but it completely overshoots the position
-
@gnmrc_ said in Problem configuring z probe using fsr switch:
@fcwilt yes it homes the left and right actuator, than want to home z positioning the arm at the center of the bed using G1 x0 y0 s2, but it completely overshoots the position
How do things behave if you use the axes "jog" buttons of the Dashboard on the Duet web interface?
Frederick
-
@fcwilt I cannot jog the machine due to insufficient axis homed. But I can say that the machine knows its homed position relative to bed 0,0
-
@gnmrc_ said in Problem configuring z probe using fsr switch:
@fcwilt I cannot jog the machine due to insufficient axis homed. But I can say that the machine knows its homed position relative to bed 0,0
You can execute G92 Z## where ## is some position that the Z could reach in the real world.
Once you did that Z would be considered homed.
Or you can execute M564 H0 S0. The H0 means "ignore the homed state". The S0 means "ignore the axes limits". H1 means "respect the homed state". S1 means "respect the axes limits". You can use H or S alone or together. And all axes are affected.
So you could home X and Y and then use G92 or M564 to allow Z to be jogged.
Frederick
-
@fcwilt so I tried to position the arm to the home position and input the offsets manually with g92, now if I move the arm to the 0,0 position it works as it should.
If in the homing file I add a g92 x0 y0 than move the arm it should work, for sure is not the cleanest solution but seems reasonable.
Tell me what you think.Gianmarco
