I guess my biggest issue is I don't name the components themselves. Then
when I try to describe what a signal is connecting it's connecting some
terribly named thing, with another terribly named thing, so my signals end
up not being very usefully named thing like SigNot2And27 or whatever
nonsense occurs to me at the time. I guess I should start with my
components and maybe the the rest might fall more into place.
On Thu, 14 May 2020 07:57:55 -0400, andy pugh <bodge...@gmail.com> wrote:
On Thu, 14 May 2020 at 05:42, David Berndt <ber...@uberwin.com> wrote:
Wondering if anyone cares to share with me a useful naming convention
for
your signals? Do you also use the name parameters to name your
components
or do you just stick with and2.0 thru and2.x?
I like to give them names that include what they are and what they do.
and.sp_intrlk for the spindle interlock, that sort of idea.
I think it is important to leave some clue what the component function
is.
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users
