On 10/19/2009 11:53 PM, kestreltom wrote:
> Thomas Kaiser writes:
>
>> Hey
>>
>> Does anybody on this list use the "UHU Servocontroller"
>> [http://www.uhu-servo.de/]?
>> If so, what are the experience with this? What motors you are using?
>>
>> I am just interested at anything somebody did with
There's a new version of hidcomp available from here
http://hidcomp.sourceforge.net This adds a Socket interface so updates can
be made to the LCD from an external program (like a hal user space python
component).
Also released is an update of GenericHID
(http://generichid.sourceforge.net/). Thi
Thomas Kaiser writes:
>
> Hey
>
> Does anybody on this list use the "UHU Servocontroller"
> [http://www.uhu-servo.de/]?
> If so, what are the experience with this? What motors you are using?
>
> I am just interested at anything somebody did with this .
>
> Thomas
>
> ---
Hey
Does anybody on this list use the "UHU Servocontroller"
[http://www.uhu-servo.de/]?
If so, what are the experience with this? What motors you are using?
I am just interested at anything somebody did with this ;-).
Thomas
---
>>net or newsig command. This also lets you give the signal a name which
means something to you:
net lube-level-critical parport.0.pin-03-in-not.
I didn't think you could do that. I thought you had to do a newsig signalname.
So is the signal name used to break the connection also? I must hav
Dave wrote:
> Great Jeff. Thanks for the explanation.
>
> Why is a signal name required?
>
Several HAL programs such as HalScope, halmeter, and halshow need a
signal name
to display with the status of that signal. It would be possible to use
sequential names
(Net_001) but that would be m
Dave wrote:
> Guys,
>
> I'm a little confused about the Net command and how it actually
> functions. I think I read the manual properly but I still don't get the
> direction arrows.
>
> I also don't understand the format where a signal name has to be placed
> after the Net command even though i
Dave wrote:
>Great Jeff. Thanks for the explanation.
>
>Why is a signal name required?
>
>
HAL requires unique names for each signal. The reason is that there
needs to be a way of connecting or disconnecting pins later on. Of
course, it also helps to see a useful name when you want to l
Great Jeff. Thanks for the explanation.
Why is a signal name required?
For instance: Why doesn't this work:
net outputpin inputpin
From what I understand this is required:
net signalname outputpin inputpin
From what I have seen, if a signalname does not exist that can be used,
on
On Mon, Oct 19, 2009 at 09:17:30AM -0400, Dave wrote:
> Are the direction arrows actually used by the Net command? IE => <=
> <=> etc?
>
> I thought that I had read that they do not matter but are simply for
> human clarification..
That's correct. You can remove the arrows from a net or li
That resolved it. I just wish I understood it properly :-)
Thank you.
Richard
Jeff Epler wrote:
> You probably need to connect the index-enable signal between the motion
> controller and the encoder counter:
> net Xindex-enable axis.0.index-enable <=>
> hm2_5i20.0.encoder.00.index-enable
>
>
Guys,
I'm a little confused about the Net command and how it actually
functions. I think I read the manual properly but I still don't get the
direction arrows.
I also don't understand the format where a signal name has to be placed
after the Net command even though it seems to be irrelevant o
You probably need to connect the index-enable signal between the motion
controller and the encoder counter:
net Xindex-enable axis.0.index-enable <=> hm2_5i20.0.encoder.00.index-enable
(this is equivalent to the old-style
newsig Xindex-enable
linksp Xindex-enable axis.0.index-enable
As you suspected, index-enable is high while searching for the index.
http://imagebin.org/68396
How do I invert the index-enable for homing?
I am confused with the use of the index for homing and/or spindle index.
This is a mill set-up I'm looking at now, but I would like to do a
lathe. I've r
14 matches
Mail list logo
