Advanced Search

You can test the index-enable system by hand.

Open halshow (this is "show machine configuration" in Axis, in some other interfaces you may need to open a terminal and "halcmd loadusr halshow"

Add the x-index-enable signal to the Watch tab. I think you should see a button that allows you to set it.

Then rotate the motor by hand, and see if the index-enable signal ever goes false.

Hint, the colour scheme of halshow is eccentric. dark red = 0 / false and yellow = 1 / true

Are the stepper motors locked or free when they should move and don't?

There is a "quirk" in Stepconf that "Test axes" doesn't set the drive "enable" pins.
(Running the full system would, if the enables are configured)

Many stepper drivers have a "not-enable" input, which turns the drive off when high. (It's typically a waste of an IO pin with stepper motors)

If the motors are locked then the drives are enabled, and for some reason the step pulses are not being seen. If they are free then suspect the enable logic.

Hi,
I'm manually adjusting the max_output values ​​and the others now, but if I wanted to do everything in pncconfig, where can I find these values?
Thanks.
Milko

Changes pushed to 2.9 won't be accessible unless the devs issue a point release. eg 2.9.5
You would probably be better off upgading to master 2.10 branch so you get changes as they happen.
QT dragon is a pretty new GUI and Chris has been beavering away improving it all the time.....

Afaik you need to re-compile the ethercat sever with the --disable-eoe option.