Euclid facility
-
@sgk this thread is getting long and I have lost track of what the current problem is. Can you state it again?
To clarify how we intend a deployable probe such as the Euclid to be used:
- Put the GCode movement commands needed to deploy or pick up the probe in file sys/deployprobe.g on the SD card, and nowhere else
- Put the GCode movement commands needed to retract or stow the probe in file sys/retractprobe.g on the SD card, and nowhere else
- Then if you run M401 it should pick up the probe. If you run M401 again then it will not repeat the pickup moves, but it will increment an internal counter
- If you run M402 it will stow the probe, unless the internal counter indicates that M401 was run more than once without an intervening M402; in which case it just decrements the counter
- When you have that working, if you command the nozzle to a XY position over the bed and execute G30, it should pick up the probe, return to the original position, probe the bed, and stow the probe
- Running G29 S0 should pick up the probe, run mesh probing (assuming you have used M557 to define the grid), and stow the probe
- The only time you need to use M401 and M402 explicitly is in a bed.g file that contains multiple G30 commands. If you don't use M401 then it will pick up and stow the probe for every probe point. If you use M401 before the first G30 command then it will pick up the probe once at the start and stow it once at the end.
- Never invoke deployprobe.g or retractprobe.g directly. That would pick up or stow the probe without adjusting the internal counter, which RRF uses to keep track of whether the probe is deployed or stowed.
HTH David
-
@dc42 to put it simply since I installed the euclid probe when I run the g32 or g29 command nothing happens, that is to say the probe does not palpate the bed.
I followed the euclid probe instructions. Deploy and retract config.g homeall home z. I'll make another video to see better. -
@jumpedwithbothfeet When I go home all she goes to get the probe and pats the center of the bed.
Yes I can move all my axes. -
@sgk lets start a fresh shall we? please post the contents of the following files.
-
config.g
-
homez.g
-
homeall.g
-
deployprobe.g
-
retractprobe.g
-
bed.g
-
-
retractprobe.g homez.g homeall.g deployprobe.g config.g bed.g
want the files in raw or it goes in ZIP
-
My bed 350x350x350 and prob euclid X0 y8. 5
-
M558 K0 P5 C"^io2.in" H8 F300 60 T9000 A3 S0.01
G31 K0 P500 X-27.955 Y-18.716 Z1.033If you include K0, you need to use K0 everywhere else the probe is called. You only have a single probe, so remove K0 from your config where you have it.
In your bed.g and home all you have a bunch of moves to pick the probe but then you also call the probe deploy. Your pickup moves should just be in the deploy macro.
G1 Y8.5 F6000 ; Pick Up Klicky G1 X20 F2000 ; G1 X0 F1000 ; Pick Up Klicky G1 Y30 F1000 ; G1 Y50 F6000 ; Pick Up Klicky M401 ; deploy Z probe (omit if using bltouch)
-
@phaedrux ok thank you I have to change the probe control in the bed m558 and g31?
-
as this
-
https://youtu.be/9wJ2RCimWXU
it gives me that -
@sgk said in Euclid facility:
as this
No. That's not what I meant at all. Your deploy and retract macros seem fine. You just need to call them with M401 and M402 in your bed.g and homeall.g files when you want to pick up or two away the probe. You don't need the manual G1 moves to pick it up there.
Did you remove the K0?
-
@phaedrux k0 deleted
-
I'm really sorry I'm completely lost at this point
-
And return your deployprobe.g macro to how it was before?
With K0 removed, does G28, G32, and G29 function now?
-
@phaedrux
I deleted my deploy and retract and I didn't save -
@sgk said in Euclid facility:
retractprobe.g homez.g homeall.g deployprobe.g config.g bed.g
want the files in raw or it goes in ZIP
Good thing you uploaded them here.
-
@phaedrux yes nice
-
it works but not very well every time the probe feels it comes home
-
I will make a video
-
and above all it does not balance the left and right bed