Option to lock out single axis homing. about fluidnc HOT 6 CLOSED

It just seems to me that blanket lockout of single axis homing is less useful than letting you do it one by one if you want, then clearing the alarm when all axes have been homed. Maybe we should not add any new config stuff, but if the global must-home: is true, then you have to eventually home all of the home-able axes before the alarm auto-clears.

from fluidnc.

Another idea - instead of locking out single axis homing, have a list of axes that must be homed before the alarm goes off.

from fluidnc.

It could be structured as a per-axis "must_home:" item. must_home: could be per-axis instead of in the start: section.

from fluidnc.

I doubt this is a high priority. I added it to Trello as reminder that we left an old feature unresolved.

POG allows you to lock out single axis homing, but you can still $X to clear the homing alarm.

Here is an idea to allow a basic mimic of POG.

axes:
  shared_stepper_disable_pin: gpio.13:high
  allow_single_axis_homing: true 
  
  x:
  ...

from fluidnc.

POG is different The feature just locks out $H.

The understanding behind the feature is for a makerspace or company that says, just do $H. $X seems to be a loophole, that they would not like.

I think we should wait for a real world request.

from fluidnc.

Another alternative is to have a homing cycle of -1 designate the axis as not to be homed. 0 would mean it is not part of $H.

from fluidnc.