2014-05-11 5:30 GMT+03:00 Jon Elson <[email protected]>: > As I understand it, the first net line that creates > a signal needs to have an output pin in the list. >
Not necessarily. My estop loop signal is created in main hal file and has connected only its target to it. Source is specified in second hal file. Erik, it is just one of those small things that create the learning curve for LinuxCNC. I personally really like the current way of creating a signal and giving it a particular name, because, like it was mentioned before, it is then very easy to add more targets for particular signal with one more line in hal file. And giving my own name also helps to understand, what is the meaning of signal, because one year later it is not that easy to remember, which particular button is connected to gpio.065 pin; self-assigned signal names help a lot. Sometimes, when I know that particular signal will have several targets, I intentionally break it down to several lines so that it is not one long line, this way it seems easier to understand, what is going on. Viesturs ------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
