On 03/17/2018 07:42 PM, Gene Heskett wrote:
Which is why, when I'm working on a hal file, a copy of that section of the docs is open in another workspace. I'm getting better, but far from perfect myself. But I didn't write the hal stack, so you'll see me asking questions too. So don't think you are too far afield when adding something to your machine and have to ask for a howto. Its the nature of the beast. I am, by the week, discovering some of the things linuxcnc can do that I hadn't a clue it could do, yet properly programmed, it just works. Its humbling to me, for sure. Andy touched on something in a previous msg in this thread, an item I may have been tempted to suggest, and that is the order of signal names, argument #1 to a net statement. To explain it from my view: net netname src target That establishes the netname as a copy of the src signal, and the src of the signal, which needs to be the first encountered when reading in the .hal file. >From that point on, the netname is re-usable with this syntax: net netname target [target] [target] etc, etc. This will then distribute the src to all the named targets, and if you run out of line room to hit all the targets, then another: net netname target target target just expands the number of targets. It can get confusing when there is 500+ LOC between the statements, but hal doesn't care.
Oh yeah, I have a copy of the doccy's open too, along with the man page for that particular thing I'm trying to implement. It's kinda like recursion though. You don't understand recursion unless you understand recursion. ;-)
Mark ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
