Is there any plan of eventually removing internal homing and only using a homing component?
I know it is a big ball of mud in there but perhaps separating motion's homing logic out from the motion module would be less code overall and also allow custom homing schemes as well. On Tue, Apr 19, 2022 at 8:50 AM Dewey Garrett <dgarr...@panix.com> wrote: > > > 1. Could the normal component period variable be > > implemented in a HOMECOMP? Currently its not supported. > > servo_period is included in the homing.h:homing_init() function: > Ref: > https://github.com/LinuxCNC/linuxcnc/blob/master/src/emc/motion/homing.h#L43 > > A user-built homing module that supports custom homing > functionality for some joints *and* conventional/legacy > LinuxCNC functions for other joints has required > replicating many parts of homing.c in the custom module. > > i have been working on a new branch that simplifies > inclusion of code from homing.c to allow unmodified > and/or augmented use of any of the base homing api > functions. > > The example homecomp.comp has been updated to > demonstrate methods to select conventional or custom > api functions for each joint according to hal pin > settings. > > Ref: https://github.com/LinuxCNC/linuxcnc/commits/dgarr/homebase > > (lightly tested, runtests passes) > (The api (homing.h) is not changed) > > -- > Dewey Garrett > > > > _______________________________________________ > Emc-developers mailing list > Emc-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-developers > _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
