deployprobe.g for Euclid not running
-
@fcwilt actually I use too, its changed to only a signal Y.
sorry some old notes still linger -
@jay_s_uk yeah its weird.
I restarted the machine. did home all.
ran the macro and nothing.
not even the first echo statement showed up in console -
I copied the entire deployprobe.g code into a macro and it runs on its own
so it seems like the deployprobe.g itself isnt being run when asked with
M401 P1 ;Deployprobe -
Just to provide another point of view.
I no longer home things as needed because I found I did not like homing taking place unexpectedly because I had tried to do something that required the printer to be homed, like mount the probe.
So now I just check that the printer is homed and abort if it is not.
I have a Euclid on one of my printers but I don't use the deploy/retract feature that is part of the firmware. I call my routines to mount/unmount the probe as needed. I have found that for normal operations I can keep the probe mounted except during actual printing. Any operation that needs the probe, such as setting the Z=0 Datum, mounts the probe and leaves it mounted. In the print start code just before actual printing begins the probe is unmounted.
Just food for thought.
Frederick
-
@adamfilip said in deployprobe.g for Euclid not running:
so it seems like the deployprobe.g itself isnt being run when asked with
M401 P1 ;DeployprobeDoesn't the firmware track the state of the probe and only run the deploy/retract routines when it thinks it needs to?
Frederick
-
@adamfilip If the euclid is your only probe, drop the
P1
and only run M401. Alternately, try P0 because your probe definition assignes ID 0. -
@oliof Thank you both M401 and M401 P0 worked!
-
@adamfilip only other error im getting in console is
Probe Pickup complete
Warning: G3000: Command is not supported -
G90 ; absolute positioning G0 X150 Y150 G3000 ; move to the center of the bed M400 ; wait for moves to finish
-
@adamfilip probably just a typo and should be F
-
-