Is something up with 2.9.7 (joint errors)

More
21 Nov 2025 19:17 #338916 by 1911ut
Hi Have 1995 Tsugami Swiss that I converted over to.
Linuxcnc, ClearPath, Mesa 6i25,7i76,7i85 closed loop on 1 micron scales.

LinuxCNC going back as far as 2.7 which was tested up to 300 inches a minute.
(Which was too fast for me.)

Never had a problem running 180 inches a minute until 2.9.7 update
Now I can't get more than 130 inches a minute without getting joint errors.
I get  180 inches a minute on LinuxCNC 2.10-pre0 on Mint 22.1 
LinuxCNC 2.9.4 runs  just fine as well.

I never upgraded to 2.9.5 or 2.9.6 but I have used the same config going back to 2.8
Anyone else seeing this?
 

Please Log in or Create an account to join the conversation.

More
21 Nov 2025 19:31 #338919 by andypugh
Replied by andypugh on topic Is something up with 2.9.7 (joint errors)
Is everything else the same? Same OS same kernel?

It wouldn't expect anything to have changed, the release notes are here, and I don't think that motion was touched.

github.com/LinuxCNC/linuxcnc/blob/2.9/debian/changelog

If you _could_ try 2.9.5 that would eliminate some changes from the list of possibilities.

Please Log in or Create an account to join the conversation.

  • rodw
  • rodw's Avatar
  • Away
  • Platinum Member
  • Platinum Member
More
22 Nov 2025 07:45 - 22 Nov 2025 07:46 #338951 by rodw
Can you tell about your computer hardware and how you installed linuxcnc?  What Linux version?  What does a latency-histogram --nobase --sbins 1000 display? There could be network latency issues on newer Debian versions, but that only affects Mesa ethernet cards. I would be looking more at secure boot, isolcpus and BIOS settings.
Last edit: 22 Nov 2025 07:46 by rodw.

Please Log in or Create an account to join the conversation.

More
22 Nov 2025 18:37 #338992 by 1911ut
Replied by 1911ut on topic Is something up with 2.9.7 (joint errors)
Thanks for you help.

I found the problem, I guess I am getting too old. (72)
It was a new install and I copied the wrong hal configuration.
I do regular backups and name folders by date (2025-11-11)
I must have read the folder wrong.
Culprit was
setp pid.x.maxerror 0.0005

Every thing is back to normal

Please Log in or Create an account to join the conversation.

Time to create page: 0.065 seconds
Powered by Kunena Forum