On 11/30/2013 1:28 PM, Dewey Garrett wrote: > > I think modularity is a good thing and will plug the option for > twopass processing that can be specified in an ini file as: > > [HAL] > TWOPASS=[on][verbose][nodelete]
Again, my issue is not with HAL, but with the INI file itself. I can already do plenty of crafty tricks to get modular HAL files. <WARNING: wandering into dev-list territory> Perhaps I'm after the wrong thing...instead of trying to enhance the INI file processing so it can match the flexibility of HAL, perhaps the constraints I'm wanting to modularize should just get pushed into HAL instead of living in the INI file. I've been extremely annoyed on occasion that I can't do things like change the acceleration and velocity limits w/o closing and restarting LinuxCNC. If those became HAL parameters, *PRESTO* both my annoyance and my modular INI file problems are solved... So why *ARE* some machine constants in the INI file while others live in HAL? Couldn't motion just export a bunch of HAL parameters that get set like anything else (ie: PID servo settings and all other HAL stuff), or is there a reason these settings have to live outside HAL in an INI file? -- Charles Steinkuehler [email protected]
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk
_______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
