> -----Original Message-----
> From: John Dammeyer [mailto:[email protected]]
> Now if a different probing operation has used that F20 rapid speed then
the
> probe travels at that speed across the cylinder. Not only that it makes
it all
> the way across and successfully completes the entire probing operation.
So
> there was a timeout involved.
>
> def error_poll(self):
> if "axis" in self.display:
> # AXIS polls for errors every 0.2 seconds, so we wait slightly
longer to
> make sure it's happened.
> time.sleep(0.25)
> error_pin = Popen(
> "halcmd getp probe.user.error ", shell=True, stdout=PIPE
> ).stdout.read()
>
> But even before that we have this call:
> self.command.wait_complete()
>
> So why does this return when in fact at F10 the command wasn't complete.
> I can't find the code for wait_complete().
>
> John
>
Here we go:
https://www.forum.linuxcnc.org/38-general-linuxcnc-questions/43474-wait-comp
lete
I'm not the only one who has had this problem. I'll try the 'fix' posted by
'natester' on 20Oct2024 and report back.
This still doesn't explain why the F20 doesn't show up on the console output
from the python code
if "G1 " in l:
l += " F#<_ini[TOOLSENSOR]RAPID_SPEED>"
doesn't work.
because entering F#<_ini[TOOLSENSOR]RAPID_SPEED> into the mdi command line
does change the F setting to F20.
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users
