Advanced Search

I'm running latency-histogram with nothing else going on. I realize lots should be going on to figure out usable software stepping latency numbers, but I found something odd and wanted to simplify.
I ran these two commands:
latency-histogram --sbins 1000
latency-histogram --nobase --sbins 1000
The second result quickly diverged from the first servo results, and has a different shape:
-14.1 to 13.0
-22.0 to 18.1
It looks to me like there is a difference in the two servo measurements. This is odd.

A question: If I'm using software stepping, which one matters, base or servo (or both)?

No it is not divide by 0 bug.I have tested that fix in mesa_modbus.c.tmpl code but problem not fixed.I have set update-hz 0.1 in hal file and does not work.
Only 0 works but if modbus is working encoder reads crazy data.
Encoder stop read crazy data only if modbus
does not work.
Can't work both encoder and modbus.
But the problem appears when there are 5 encoders not only 4