7i95 Encoder counter error

When I use 3 axes to move simultaneously, such as G0 X3000 Y3000 Z3000, and reciprocate from 0-3000, the encoder counts normally
But as soon as I move only one axis, any one, the encoder counts become inaccurate

All parameter settings for the three axes are the same

Can you post your hal and ini files?

Of course, forgot to mention that the encoder count comes from the servo drive

Not quite sure what you are trying to do here:You have velocity feedback from
the encoder (with a typo that probably doesn't matter)

net jonit-1-vel-fb <=> hm2_[MESA](BOARD).0.encoder.01.velocity => pid.y.feedback-deriv

but local position feedback from the stepgen:

net joint-1-pos-fb <=> joint.1.motor-pos-fb <= hm2_[MESA](BOARD).0.stepgen.01.position-fb => pid.y.feedback

and the encoder position values are not used

If I use encoder position feedback I get a follow error
So I use stepgen feedback to view the encoder count in halshow

I would expect a following error because the PID tuning for encoder
feedback would be very different than the PID tuning for local stepgen
feedback (this is because of the significant delays between a commanded
step and the actual motion) It also depends on getting the encoder feedback
scaled properly in the the correct direction.

Also homing to index will not work with stepgen feedback unless
you use firmware that supports stepgen index. Without this
firmware, you must use encoder feedback to home to index.


 

At first I thought it was a delay or something that caused the encoder counting error, but when I made the three axes move rapidly simultaneously, the encoder counting would not go wrong. This is what confused me.

about index, if the encoder feedback cannot be used to make a closed loop, I will use a grating ruler to connect the servo driver to make a closed loop without going through the mesa card, and the mesa card only connects the Z signal of the servo driver for homing, and the driver and the machine tool achieve a closed loop, but the driver Open the loop with Mesa. Obviously, this is not the optimal way to close the loop.

Encoder feedback can be used to close the loop. To check this
you would need to lower the P term to say 10 and widen the following error
limits to see the system behavior using halscope.

If you only use index, you must have firmware that implements stepgen index
to be able to home to index, since the stepgen feedback position must be zeroed
at index occurrence, and this requires special stepgen hardware.

Also note that you must disconnect the encoder velocity feedback from
the PID in this case (actually this should always be disconnected even if encoder
feedback is used)

Here is 7I95 firmware that implements step/dir index:

 

Note that with this firmware, there are now 2 index enable pins,
encoder.xx.index-enable and stepgen.xx.index-enable
and the proper one must be used in hal based on the feedback source

This firmware may require LinuxCNC 2.9 or master

Oh, you are the best, thank you very much for your help

But just using the index is the last resort, I think the closed loop from the mesa card to the drive is the optimal solution (is it?)

I will try to continue debugging the PID to achieve full speed operation without following errors