vibration at lowspeed.

I'm developing a feature that is called "admittance control", it's a method to control motor base on external force.
The system workflow is:

External force (from ft sensor)-> admittance module (100Hz update rate) -->joint cmd--> simple_tp/limit3 (1Khz) -> ethercat -> driver motor

The admittance module will convert external force to joint-cmd to control motor. Everything look fine except vibration at low speed like this chart

 

The velocity input look fine but the output velocity-cmd (derivative from position) is not smooth at low speed. Is this problem come from simple_tp/limit3 component? I look at linuxcnc code note and see cubic interpolator is using. Should i rewrite a cubic interpolator to replace simple_tp/limit3 or try to increase admittance update rate to 1 Khz and skip interpolator?

Are you using steppers or servos?
It's possible you are observing  low speed stepper harmonics. If that's the case, the solution would be to alter the motor gearing to avoid low motor speeds in the harmonics range.

i'm using servos, i don't think it comes from the motor side because jogging from LinuxCNC is still smooth. Just look at the figures i attached, the input velocity before the simple_tp module is still smooth but the output velocity from this module is not.
 

Something that happens every 100 ms it seems like.
You can see a small change or step in joint_vel and the servos are responding to that. At least where the main spikes are.
So what are you doing every 100 ms?

It's the admittance module update rate that will update new position cmd
I'm wrong, admittance update rate is 10ms not 100ms.

I would think a faster update rate will decrease the steps.
You will get more steps but less in magnitude.
I guess you have some gain parameter between force and position.
Maybe try higher gain at low speeds? Since it seems to be a bit off, I mean.

I tried to adjust gain of admittance module before but no luck.

I understand your point about increasing the update rate to reduce step magnitude while potentially increasing the number of steps.

However, if steps were the primary issue, I would expect the problem to be more pronounced at higher speeds, yet that doesn’t seem to be the case here. Additionally, I’ve noticed a sudden velocity drop that fails to meet the required speed, causing vibrations. This issue occurs simultaneously across all four motors and seems to happen approximately every 100ms. While it appears random, I haven’t yet identified the source of this cycle (admittance module is 10ms update rate), which makes it quite puzzling.

Is your module real time? I have seen similar issues with non-real time
functions being affected by LinuxCNC periodic screen update. 

You are right image missing /media/kunena/emoticons/w00t.png, i tried changing screen update and the vibration spikes up at the same rate.
My module is not real-time, it's a Python module and is built as an embedded tab of Lcnc. I dont think real-time is needed but i may need to find another way for it to not get affected by screen update.