Euclid facility

A Former User

there is something that I did not understand guys is that I must put the command m 401 and m 402 in deploy and retract or in home z and bed?

dc42

@sgk you should only need to use M401 at the start of bed.g and M402 at the end. That will pick up the probe once and put it down once only, instead before/after every probe point. Also they are useful for testing pickup and release of the probe.

A Former User

OK i understand thank you

jumpedwithbothfeet

@sgk can you post your Homeall.g, homez.g, deployprobe.g, retractprobe.g, and bed.g put these in quotes (thats the little </> button above the reply box) I suspect your using a mish mash of different configurations which is causing the issue as @DC42 is alluding too.

A Former User

@jumpedwithbothfeet
hello it's true that I'm a little lost. thank you all for your patience and your help.

retractprobe.g homez.g homeall.g deployprobe.g config.g bed.g

sinned6915

@sgk all of this is pretty well addressed in the Euclid docs.

https://euclidprobe.github.io/06_macros_overview.html

there are annotated picures and macro files.

if you need more help, the euclid discord might be faster, i dont come here often.

and just so you know, Euclid does not like it when you call it klicky

Nurgelrot

This post is deleted!

jumpedwithbothfeet

@sgk in bed.g comment out M401 and M402 just like below and try it again

; bed.g
; called to perform automatic bed compensation via G32
;
; generated by Ben Levi - BLV developer as a basic version

M561 												; clear any bed transform
G91               									; relative positioning
G1 H2 Z5 F6000   									; lift Z relative to current position
G90              									; absolute positioning
G28 												; home all
;G30 P0 X10 Y175 Z-99999 							; probe near a leadscrew, half way along Y axis
;G30 P1 X330 Y175 Z-99999 S2 						; probe near a leadscrew and calibrate 2 motors
G29 S0                                              ; probe the bed and enable compensation
M291 P"Leveling finished !" R"Probing.." S1 T2

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)
G30 P0 X10 Y175 Z-99999 							; probe near a leadscrew, half way along Y axis
G30 P1 X330 Y175 Z-99999 S2 						; probe near a leadscrew and calibrate 2 motors
;M402 ; retract probe (omit if using bltouch)                  
G1 Y250 F6000 ; Drop Klicky
G1 X0 F6000 ; Drop Klicky
G1 Y8.5 F6000 ; Drop Klicky
G1 X170 F6000 ; Drop Klicky
G1 Y170 F6000 ;

A Former User

@jumpedwithbothfeet Ha OK I will modify and I will let you know thank you

jumpedwithbothfeet

@sgk I have just realised you should also move the M291 to the bottom of the file and also comment G29 S0 out, just like this -

; bed.g
; called to perform automatic bed compensation via G32
;
; generated by Ben Levi - BLV developer as a basic version

M561 												; clear any bed transform
G91               									; relative positioning
G1 H2 Z5 F6000   									; lift Z relative to current position
G90              									; absolute positioning
G28 												; home all
;G30 P0 X10 Y175 Z-99999 							; probe near a leadscrew, half way along Y axis
;G30 P1 X330 Y175 Z-99999 S2 						; probe near a leadscrew and calibrate 2 motors
;G29 S0                                              ; probe the bed and enable compensation
;M291 P"Leveling started!" R"Probing.." S1 T2

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)
G30 P0 X10 Y175 Z-99999 							; probe near a leadscrew, half way along Y axis
G30 P1 X330 Y175 Z-99999 S2 						; probe near a leadscrew and calibrate 2 motors
;M402 ; retract probe (omit if using bltouch)                  
G1 Y250 F6000 ; Drop Klicky
G1 X0 F6000 ; Drop Klicky
G1 Y8.5 F6000 ; Drop Klicky
G1 X170 F6000 ; Drop Klicky
G1 Y170 F6000 ;
M291 P"Leveling finished !" R"Probing.." S1 T2

A Former User

@jumpedwithbothfeet yes OK thank you

A Former User

@jumpedwithbothfeet The m 401 and m 402 I have to leave like this with [;]

jumpedwithbothfeet

@sgk yes that’s the quickest way to get you up and running, but it’s not the conventional way, it all depends on how you what to use your Euclid probe, I think most people would use M401 and M402 in which case you would need to remove the G1 codes from bed.g, homeall.g, and homez.g, see how you get on, the best thing about rrf is it’s flexible, there are multiple ways of achieving the same thing.

A Former User

@jumpedwithbothfeet I will already change and see how it works.

A Former User

@jumpedwithbothfeet
hello I changed but it's the same nothing to change when I do home and after g29 or g32 it doesn't probing the bed.

jumpedwithbothfeet

@sgk in homez.g remove or comment out -

G1 X152 Y166.4 F6000 ; go to first probe point
G30                 ; home Z by probing the bed

in homeall.g remove or comment out -

G1 X170 Y180 F6000	    ; go to first probe point X11.5 Y65.8 Z0 The coordinate put the Z sensor in the center of the bed.
G30 					; Probe

repost both files once you have changed them

A Former User

@jumpedwithbothfeet I will change and see

A Former User

I changed but when I run g32 or g29 it doesn't work

jumpedwithbothfeet

@sgk ok back to the beginning, when you home all axis, the printer does this? the euclid probe is detected and you can move all axes of the printer independently?

dc42

@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