Yes, its one of those things. I waffled when I started this years ago between emc and mach3, and chose emc, still glad I did.
I don't think the current state of documentation is sufficient though. I spent half an hour trying to find information on comp, ultimately found it while holding my mouth just right and googling it. I know its all *free*, so we can't expect developers to want to do stuff for free. Perhaps there are others however, that would or could pitch in if some of the documentation was brought together better. From a programmers perspective, any time you download a library from any language, say c or c#, there is going to be documentation, or perhaps a struct that you can pinpoint with info, which is basically what comp is. Why then can't it be the same way for linuxcnc, you have one manual, it tells you some minimal info needed to use it. The manual(Not sure which now) just says comp is for comparison, where 4 more lines could give the in0,in1,out,hyst "struct" definitions it took so long to find elsewhere. On Sun, May 11, 2014 at 3:29 AM, Viesturs Lācis <viesturs.la...@gmail.com>wrote: > 2014-05-11 5:30 GMT+03:00 Jon Elson <el...@pico-systems.com>: > > > 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 > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users > ------------------------------------------------------------------------------ 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 Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
