Missed Servo Moves
Please Log in or Create an account to join the conversation.
John
Please Log in or Create an account to join the conversation.
The Fanuc patch is a must as far as I am concerned in fact I think it should be taken farther simply because the standard is there. I am loving Linux and have already started another retrofit on a larger Turning center I just hope we are not too far ahead of the development of LinuxCNC to continue using it. I don't think we have the knowledge to write patches and help in the process. I don't want to be a thorn but I will continue to ask nicely that more work is done in the tool offset area. Like separate pages for Geometry and Wear offsets, that wear offsets can be entered in Diameter instead of radius and maybe even a GUI that has tabs for both. There has to be other commercial shops that do or will need this to integrate linuxcnc easier into the shop with a format that hired hands can come in and run without too much difference.
I already know that we may have to help in the process, I just hope we can figure out how to help........
Please Log in or Create an account to join the conversation.
John
Please Log in or Create an account to join the conversation.
Running a part today in our recently retrofitted Turning center. We were about 50 pieces into the run when the turret did not go out to tool change position and decided to change tools right on the part.
That sounds messy.
How is the tool-change-request to tool-changed handshake handled?
Is there any chance that you got unlucky with electrical noise?
Maybe a (software) debounce on the status lines is needed?
Please Log in or Create an account to join the conversation.
(mechanical switch debounce may be an issue as well)
some delays, debouncing and I/O redundancy/sanity checking
might be in order.
Please Log in or Create an account to join the conversation.
Using Classic Ladder for the Turret logic.
Please Log in or Create an account to join the conversation.
Thanks for the input. I am not too sure exactly what debounce is but I will do some checking on that.
Classically switch bounce is exactly that. as the contacts come together they physically bound and instead of off-on you yet off-on-off-on-off-on…on. Keyboards do it, and hardware/software has to be included to distinguish between bouncing contacts and multiple key presses.
In the case of LinuxCNC there is a "debounce" function that can be set up in HAL and linked to any signals where you absolutely want to make sure that the switch is really on or off. All it does is keep the output the same until is has seen the input hold the same value for a certain number of servo cycles.
I am thinking that perhaps some electrical noise (or even a mechanical vibration) might have set the "tool change finished" signal far too early.
debounce is a slightly odd component to get your head around.
www.linuxcnc.org/docs/html/man/man9/debounce.9.html
You can have multiple channels in multiple groups. Each group can have a different debounce time. Each group needs to be added to a thread separately.
Please Log in or Create an account to join the conversation.