Basic probe fails on latch return

More
1 year 2 months ago #334018 by cmorley
Are you saying that the spindle-at-speed signal interrupted the probe routines?

Please Log in or Create an account to join the conversation.

More
1 year 2 months ago #334024 by h_munktell
Sort of. It looks like Spindle-at-speed needs to be true for motion commands to executed. And since there are G1 commands in the probe routine, and the inconsistency in hy_vfd mentioned in my previous post, execution was halted in probe latch return (G1 move) and the timeout error occurs.

To be clear, I do not see any fault or bug in the probing routine. And I think the way linuxcnc is handling spindle-at-speed signal is correct for motion.

The docs of hy_vfd sais:
Code:
spindle-at-speed (bit, out) True when the current spindle speed is within .spindle-at-speed-tolerance of the commanded speed.

But the source code for hy_vfd mentions that the spindle also needs to be turned on for this signal to work
Code:
hal_bit_t       *spindle_at_speed;   // (out) True when spindle is on and at commanded speed

github.com/LinuxCNC/linuxcnc/blob/27706f...ng-vfd/hy_vfd.c#L123  

As I hade net hy_vfd.spindle-at-speed to spindle.0.at-speed, after a spindle start and stop, this signal never got TRUE when the spindle stopped, and all subsequent movements where halted. 

Interestingly, G38 moves is not dependent of spindle-at-speed signal, do not know if this is intentional or a bug in linuxcnc code.

Please Log in or Create an account to join the conversation.

More
1 year 2 months ago #334045 by andypugh

Code:
[code]Interestingly, G38 moves is not dependent of spindle-at-speed signal, do not know if this is intentional or a bug in linuxcnc code.
[/code]
That does seem inconsistent, but at the same time you almost always _don't_ want the spindle to spin with the probe loaded. Especially if it's a wired probe. 
 

Please Log in or Create an account to join the conversation.

More
1 year 2 months ago #334046 by andypugh
For other random probe failures, see also github.com/LinuxCNC/linuxcnc/pull/3537

Please Log in or Create an account to join the conversation.

More
1 year 2 months ago #334047 by wusel0464
Hello,

For me, he basically does the first (rough measurement) until the step comes back, this is no longer carried out, regardless of whether the workpiece height or tool length and the whole sporadically.
It happens that I finish several parts with the same program and the first or two run through and then it caught or just caught.
If you wait, a timeout comes as described.
At the moment I only come out when I end Linuxcnc, I haven't tried something else yet.
I suspect something swallows in the order.
I have already discharged the trial entrance, but that was also unsuccessful.
I'll try to implement this with the spindle and see what happens.

Until then, greetings to everyone, Frank

Please Log in or Create an account to join the conversation.

Moderators: cmorley
Time to create page: 0.327 seconds
Powered by Kunena Forum