On Saturday, May 05, 2012 01:37:42 PM Kent A. Reed did opine: > On 5/4/2012 10:41 PM, gene heskett wrote: > > Greetings; > > > > As I read the hal manuals getting started section, where the keywords > > loadrt, setp, addf, and net are defined, I didn't understand at first > > that arg[3], arg[4] arg[5] etc of a "net" commend can be repeated to > > add sending something from arg[2] to more than one load. But I can't > > name a previously used output and send it to the 2nd place it needs > > to go. Its s show stopper error. > > > > Is this intentional, or do I likely have a deeper miss-understanding? > > > > What I am trying to do is incorporate the > > "Closed_Loop_Spindle_Speed_Control" hal bits& pieces into an existing > > hal file that already controls the speed just fine from the gui or in > > an .ngc program. The existing speed control however isn't that > > 'stiff' down at the ranges one uses for threading, so the speed > > control needs more low speed gain. > > > > I am assuming of course that the 'net' is arg[0] for that line of hal, > > and that the next argument, arg[1] is an arbitrary name for the 'net' > > signal, arg[2] then is the source of the signal or data, arg[3] is > > the first of a list of places to send that signal. No mention of a > > "fanout" limit if there is one. > > Gene: > > I'm not sure I understand what you are asking here. I'm a tad confused > by the arg[x] notation. > Typical C construct came crawling out of the dust in the attic. :)
> "But I can't name a previously used output and send it to the 2nd place > it needs to go." - huh? > > Look at: > net sig1 someout somein > net sig1 someotherin > > Here I've connected the output pin "someout" to both "somein" and > "someotherin" input pins using the signal "sig1". Is this what you mean? THat is what I was trying to do, but must have mucked up the syntax. Line 38 name-of-variable already defined. But if I can do the above, problem solved. I think what I was trying to do was to use someout in the sig1 position. I think. Lemme see if the ssh -Y works. Yup, error is: my-lathe.hal:36: Pin 'pwmgen.0.enable' was already linked to signal 'spindle-enable' and the fix then should be to reuse the sig1 from the line above it, and remove the pwmgen.0.enable. effectively sending spindle-enable => pid.0.enable. Or just add pid.0.enable to the line above it. And that worked. That was in line 35 now, 36 is gone and the next error is in line 59. my-lathe.hal:59: Pin 'motion.spindle-speed-out' was already linked to signal 'spindle-cmd' so I likely have a similar error there. Looks somewhat like a dup of effort but the routing in the first instance is thru abs.0. This thing will eventually use a DPDT relay for reverse. > net connects a signal with one or more pins. It is nearly irresistible > not to think of electrical networks, but we're talking software here. > Simplistically a pin defines a memory location and the pin's sex---in, > out, bi---is defined by whether the content of the memory location is > written internally by its component or externally by copying the content > of some other location through the magic of hal. There is no fanout > limit in any practical sense. > > I'm still uncomfortable with the notion of bidirectional pins. So am I. > Try > putting together all the lines of text that mention them and see if you > get a complete explanation. I keep feeling there's a bit of chicanery > here but I guess I can live with it. > > That's the way I see it. If I'm wrong, then I'm sure I'll be swiftly > corrected:-) > > Regards, > Kent > 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> Help stamp out and abolish redundancy and repetition. ------------------------------------------------------------------------------ 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
