MIN_SPINDLE_OVERRIDE = 0.5 CUESTION

why the MIN_SPINDLE_OVERRIDE of the .INI file in axis does not respond. ?

I have tested it on linuxcnc 2.8 and 2.8.1on AXIS

when I run in G code I can set the spindle speed to zero. but I have the MIN_SPINDLE_OVERRIDE set to 50% . Is it made for some reason this way?

thank you


. video


MAX_SPINDLE_OVERRIDE WORKS PERFECT !!!

Axis doesn't even look for min_spindle_override.

github.com/LinuxCNC/linuxcnc/blob/76e1f2...cripts/axis.py#L3300

Is there any real use for it? I can definitely see a need for a minimum absolute speed command, but not so much for a minimum (proportional) override.

Many other user interfaces do look for MIN_SPINDLE_OVERRIDE:
github.com/LinuxCNC/linuxcnc/search?l=Py...MIN_SPINDLE_OVERRIDE

I must report a collision between tool and part.
Linuxcnc continues executing the program even if the spindle is off.
In this case, the operator made the mistake of lowering it and collided.
I think that for safety the spindle turn should be limited to a minimum override turn.

I went to see how Fanuc has implemented it and I found this that I show in the image

PICTURE

I think a security issue.

That's exactly why it was added.

I can imagine that even half-speed could break tools.

If you want to use Axis rather than a different GUI which does support min_spindle_override, then I can see a couple of options:

1) Do something with the logic of spindle-at-speed, so that it is false if the spindle is not moving at a certain minimum speed, even if it is at the commanded speed. But be aware that when waiting for spindle-at-speed the system doesn't give much clue as to why it is doing nothing
2) Modify Axis to support minimum_spindle_override. Axis is written in Python, so it can be edited, and the changes will take effect. There is no need to recompilr or to have the rest of the source code.
2a) Persuade someone to make the changes in LinuxCNC itself. But that would take longer to filter down to your production machine.

I understand all the options. I have sent a security notification to all the users of my automation jobs so that they are aware of this possible situation due to an operation error.

I also understand how hard it is for developers to change something that was always like this.

I will try to see how I can give a solution while it does not happen by the developers.

thank you very much for all the answers

RobotMatic wrote: I also understand how hard it is for developers to change something that was always like this.

It isn't developer inertial in this case, it is just that you seem to be the first to have been troubled by the fact that Axis doesn't do this.

Hey, here, you can add this to your .axisrc or usercommand.py file

in the example, 50 is the min override percentage , since theres nothing for it in axis it should be safe to use

since we are on the topic, you can adjust the override increments aswell

Hello,

i had the same problem on a machine in the past,
this is the patch for this. it is not migrated to 2.8 yet, but this should be an easy task.


github.com/dbraun1981/linuxcnc_patches_2...indle_override.patch

Thank you very much for all the proposed solutions !!!!

as can be proposed for this patch to be native. ?

How do you tell the development group to analyze putting it?

is it possible that the next update 2.8.2 will have it ???