On 5/5/2012 2:03 PM, Jeff Epler wrote: > Are we talking about this documentation? > http://linuxcnc.org/docs/2.5/html/hal/basic_hal.html#_net_a_id_sub_net_a > if so, the syntax > net<signal-name> <pin-name> <opt-direction> <opt-pin-name> > doesn't really reflect what "net" will actually accept. I've revised > the documentation to hopefully improve things: > > 1.4 net > <..>
Thanks for chiming in, Jeff. I think your rewrite reads very well. Although the following A) and B) are consequences of the rules you state, generalizing from Gene's query I think it might be useful to mention explicitly A) the connection of all the pins associated with a given signal may be accomplished with a single instance of the net command or many. B) there is no requirement about the order of pins within a single net command or the order of net commands in a hal configuration. The OUT (source) pin does not have to come first, eg, a signal may be defined and connected to one or more IN pins, then connected to an OUT pin, then connected to more IN pins, either in a single net command or across many. What matters is the network that halcmd creates out of the totality of commands it reads. C) there is no requirement that a signal connect both OUT (e.g., source) pin and IN (e.g., target) pins. Examples of this abound in the example configurations, where signals are defined solely (so far as I can tell) for possible monitoring and troubleshooting. Things that do matter are 1) the rules you state, and 2) commonality of type across the various pins connected by a signal. As you can see, even now I can't write this as clearly as you. Regards, Kent ------------------------------------------------------------------------------ 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
