> >
> We/I have. So while I'm still rowing with a toothpick here, I do not see
> the need to further the complexity of motion. The tools to build the 3
> level suicide braking system for my lathe are right there in hal today.
>
Thanks for your comments.
I'm not understanding which side you're voting for Gene.
I am not adding complexity to motion, I am adding two pins.
This simplifies HAL code for other people.
My changes are to simplify a common configuration problem.
This didn't just pop up yesterday from someone using obscure
equipment. I've dealt with it a few times, what finally prompted me
to build a patch was a comment from Peter Wallace about it in the
forum. The devs and power users on the forum tend to see the common
problems for users. If it's easy and makes some sense I like to try
and eliminate recurring end user problems.
I most say with a HAL file of what almost 300 lines I think you said, I
hardly think adding complexity is your primary worry ! :) You must
eat and breathe HAL code now!
My change will not affect you what so ever.
Removing all the extra spindle pins from motion and using another
component most likely will and in fact most likely will for everyone,
past, present and of course future.
As I said if we were starting clean, or didn't care about current users,
It would make some sense to pull out the pins.
But there is little upside other then feeling good about motion being
less prickly with pins.
When Michael rewrites motion and remove NML etc that would probably
be a time when we can say hey lets not worry too much about breaking
configs because (My guess ) lots of things will need changes.
That is the time to remove extra motion pins and add a generic spindle
control component.
All MHO of course.
Chris M
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
