For items that aren't easily named, a comment line (#comment) in the hal file
can be useful.
Todd Zuercher
P. Graham Dunn Inc.
630 Henry Street
Dalton, Ohio 44618
Phone: (330)828-2105ext. 2031
-Original Message-
From: David Berndt
Sent: Thursday, May 14, 2020 12:39 AM
To: emc-users@l
On Thursday 14 May 2020 12:12:26 Roland Jollivet wrote:
> Just add a comment at the top referencing a text file where you have
> it all described?
>
Shirley (or Roland) you jest. It makes far more sense to clutter up your
hal files with comment blocks for function headers that explain that, I
fi
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
no
On Thu, 14 May 2020 at 05:42, David Berndt 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 th
On Thursday 14 May 2020 00:39:28 David Berndt 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?
>
> My hal config works fine, but I worry abo
> On 14 May 2020, at 2:39 pm, David Berndt 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?
FWIW I try to give components a name re
