=candcnc_pinout.hal
=my-mill.hal
2d1
loadrt scope_rt
4,5c3,5
loadrt hal_parport cfg=0x0378
loadrt motmod base_period_nsec=6 servo_period_nsec=100
traj_period_nsec=1000 key=111 num_joints=3
---
loadrt hal_parport cfg=0x378
loadrt probe_parport
loadrt motmod
On Tue, Dec 11, 2007 at 05:43:42PM +, Alan Condit wrote:
Can anyone see what is keeping the x axis from running???
Well what did you do that fixed Y?
-
SF.Net email is sponsored by:
Check out the new SourceForge.net
Chris Radek [EMAIL PROTECTED] writes:
On Tue, Dec 11, 2007 at 05:43:42PM +, Alan Condit wrote:
Can anyone see what is keeping the x axis from running???
Well what did you do that fixed Y?
Chris,
I rebooted the machine. Honestly, one time when I would start it up Y would work
and
I had an interference problem that was corrected by putting a filter on
the power input to the spindle VFD (HNC lathe). Only the spindle index
was showing a problem. I am thinking that different systems have
different thresholds of susceptibility. Maybe the source of your problem
has a threshold
Kirk Wallace [EMAIL PROTECTED] writes:
I had an interference problem that was corrected by putting a filter on
the power input to the spindle VFD (HNC lathe). Only the spindle index
was showing a problem. I am thinking that different systems have
different thresholds of susceptibility.
Alan Condit [EMAIL PROTECTED] writes:
After reading the documentation, I believe that I had mis-interpreted the
meaning of dirsetup and dirhold.
I tried these parameters for my drives:
steplen = 25000
stepspace = 25000
dirsetup = 2000
dirhold =
