- Posts: 77
- Thank you received: 2
Please publish your solution in full, including function declarations such as loadrt + everything, everything, everything. So that I can repeat it.without my M64/M65-flipflop solution,
Please Log in or Create an account to join the conversation.
The updates in 2.9.7 fix (hopefully) a bug where the "probe triggered during non-probe move" error was raised when the machine was actually probing (due to probe contact bounce).It kinda improved, but the „probe triggered“ fault is still happening.
I was not able to finish even shorter milling programs (<5 mins).
Please Log in or Create an account to join the conversation.
Am i understanding this correctly:The updates in 2.9.7 fix (hopefully) a bug where the "probe triggered during non-probe move" error was raised when the machine was actually probing (due to probe contact bounce).
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Not really. The problem was that LinuxCNC was setting the status to "not probing" before the end of the deceleration stage of a probe move. In cases where the probe triggers more than once (as many will) this led to a "non probe move" error during a probe move.
Am i understanding this correctly:
A software solution was implemented in LinuxCNC for a hardware problem/issue ?
It does seem like it, or what am i missing?
Please Log in or Create an account to join the conversation.