Re: [Emc-developers] Dev-environment setup
On Tue, 19 Apr 2022 at 04:07, Thaddeus Waldner wrote: > > As of now, I am testing it by using the print() statement and running > LinuxCNC from the command line. I can't really help much with the question, as I basically use Geany and print for all my dev work. (This is a hangover from mainly working in the realtime driver layers, where that's the only option for debug) -- atp "A motorcycle is a bicycle with a pandemonium attachment and is designed for the especial use of mechanical geniuses, daredevils and lunatics." — George Fitch, Atlanta Constitution Newspaper, 1912 ___ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
Re: [Emc-developers] suggestions to improve HOMECOMP/HOMEMOD custom homing infrastructure
> 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