On Saturday, May 05, 2012 06:03:17 PM Kent A. Reed did opine: [...] > OOPS I was in a hurry to get to the store and left out an important > thought. The order of the pins in a net command is not significant. > Their mode is defined elsewhere, not by their order of occurrence in the > net command. halcmd has to sort out whether an utterance is legal based > on its knowledge of components. > > If you look through some of the hal configurations distributed with > LinuxCNC (or least with older EMC2 dists; I haven't looke recently) > you'll see usage like > > net somesig pina <= pinb => pinc > > which *implies* pinb is an output and pina and pinc are inputs, although > the direction of the arrows is actually irrelevant since they are > ignored by halcmd. Another broad hint is the frequent use of "in" and > "out" in the names of pins, although that can confuse the unwary who use > parports. I am assuming the any 'pin' named .out is a signal source, and that any pin labeled .in is a place to put a signal.
> Only halcmd knows for sure, which is why my context-free parser was a > challenge. > > Regards, > Kent I can well imagine. However, I did get the closed loop spindle speed control working, very well except for the 1/2 second response time before it discovers I grabbed the back end of a piece of 5/8" rod sticking out of the back of the spindle and stopped it from about 1/2 rps. Then the power comes on and I can't hold it. That's nice, and has the side effect of making the plus and minus buttons work in much finer increments, which is something else I wanted. However I now have a real head scratcher. test-G76.ngc, set to cut air off the end of the workpiece about 2" to the right, now goes to the commanded position in this file to establish the 'drive line' which is correct, then rapids to the first cut pass radii (which is wrong, my using radii instead of diameter in the G76 for the outside of the thread is obviously wrong) and then sits there forever waiting on an encoder.0.index pulse (which is good) forever, like the encoder.0.index pulse isn't going anywhere. Is there some place it needs to go to make g76 work that I accidentally removed? encoder.0.counter-mod is false, but the man page doesn't say much about the index, which I can see in hal-meter just fine if its running slow enough. Are there any clues to be spared on this? And it's past dinner here so I am getting distracted. Thanks Kent. Cheers, Gene -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) My web page: <http://coyoteden.dyndns-free.com:85/gene> "How should I know if it works? That's what beta testers are for. I only coded it." (Attributed to Linus Torvalds, somewhere in a posting) ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
