On 8 September 2015 at 16:22, Chris Radek <[email protected]> wrote: >> My proposal is that the homing code would search the INI file for a >> [SPINDLE*] stanza (which already exists in many configs) and if it >> finds one that contains a homing sequence number it would assert the >> spindle-index-enable output and run the spindle at >> [SPINDLE]HOME_VELOCITY until the index enable went false. This is a >> very abbrieviated sequence, but I think it covers most requirements. > > I agree with your proposal. I do think you need explicit homing if > you want to be able to specify the direction of orient - I couldn't > come up with a way to cheat. (I don't know if direction is ever > actually important, but it's the design we have)
I was recently reminded of this, and decided to look into it. homing,c gets its information from the joints array of joint_t which is populated by ini_joints. I could probably access the INI from inside homing.c, but I think that I probably shouldn't, it feels like a kludge. In fact what I think I should do is add a spindle_t and an ini_spindles and leave open the possibility of multiple spindles in the future. (I don't know how that would work, perhaps an S-word on the same line as an M3.2 turns on the third spindle at that speed, and a bare S-word affects all spindles?) But, that doesn't need to be done now, I am just asking whether adding a spindles array is sensible (num_spindles then becomes a motion modparam) It's probably worth doing it right and doing it once. -- atp If you can't fix it, you don't own it. http://www.ifixit.com/Manifesto ------------------------------------------------------------------------------ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
