Advanced Search

Thank you for your answer
I can change the speed with a potentiometer, but if I change it while the axes are moving, it doesn't take effect. I have to stop the axes, change the speed, and then move the axes again. What I want is to be able to change the speed while the axes are moving.

I'm going to run some tests this weekend.
To be honest, I'm having trouble understanding the purpose of the FF0, FF1, and FF2 terms. Are these offsets of the PID terms?

Are you saying you cannot set x-index-enable true in halshow?

hm2_7i80.0.encoder.00.input-index pin staying true may be OK as this just reflects its
polarity, and you are unlikely to catch the actual index with halscope because of its narrow width
(especially at 500 ms/division where halscope throws away most samples)

Unless you can set x-index-enable it will be difficult to diagnose


 

No, something is wrong.
the  hm2_7i80.0.encoder.00.input-index pin permanently stays true and
the  x-index-enable signal permanently stays false. The pictures show the state they are in and also when moving the axis by G1 F10 X 0 to 10 and back nothing changes
And the index-enable does not go high when the home switch trips (when homing)
 

 

There are pins to change jog speed using counts (eg for encoder) and for using analog value (eg for potentiometer):
linuxcnc.org/docs/html/gui/gmoccapy.html...cities_and_overrides

I'm trying to execute an M100 from this toolchange subroutine, whithout M100 works. Here is the M100 and it works in MDI, what can cause the hang? 

#!/bin/bash
# M100 Orient Spindle (Homing function)
halcmd sets s-index-zero-for-ATC true
exit 0

 
 

Thank you Andy, but I can not gain access to the X-Motor or spindle- probably to the Z spindle and move the Z-axis, I will try. So jogging the X-axis slowly must do the job.
Sigi