LinuxCNC S-Curve Accelerations

More
1 year 6 months ago - 1 year 6 months ago #326389 by rodw
Replied by rodw on topic LinuxCNC S-Curve Accelerations

HI Rod,A tester send me this :Debian 10 : jitter max 45200Debian 12:jitter max 29000Debian13:jitter max 522000Ir looks very bad.
I think something is wrong with his setup. He needs to review my Google drive doc to optimise the  performance.I thought I had Debian 13 running here at home but it is on my work computer.But even so,  his Debian 12 latency seems high. Ethercat is installed on this PC 
 
Last edit: 1 year 6 months ago by rodw.
The following user(s) said Thank You: Grotius

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

More
1 year 6 months ago #326391 by rodw
Replied by rodw on topic LinuxCNC S-Curve Accelerations
Please ignore the custom kernel here but follow all other optimisations
docs.google.com/document/d/1jeV_4VKzVmOI.../edit?usp=drive_link

There are many new features like energy efficient Ethernet that need setting for best latency
The following user(s) said Thank You: Grotius

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

More
1 year 6 months ago #326392 by rodw
Replied by rodw on topic LinuxCNC S-Curve Accelerations
ANd also try installing this 6.12 kernel another user built
drive.google.com/drive/folders/16Xlry00L...SlwznPLv?usp=sharing
The following user(s) said Thank You: Grotius

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

More
1 year 6 months ago #326396 by Grotius
Thanks,

Will give it a try tomorrow.

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

More
1 year 6 months ago #326433 by Grotius
Hi,

Before starting to change kernels etc. I thought maybe first do the latency-histogram test.
I did this on 2 different pc's.

From what i read here : max us > 100 = is bad.
Is this value both the same for base- & servo-thread?
Or maybe i am reading the histogram not correct.

 
 
 

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

More
1 year 6 months ago #326435 by tommylight
Always use --show at the end of latency histogram, it will show the number of excursions that are not inside the visible area of the histogram, but they can be seen as multicolored columns on both sides of the histogram.
Also, use --nobase if there is no need for the base period, it adds more timing strains to CPU that will mess with the servo period latency results.
For both periods
Code:
latency-histogram --show
For servo period only
Code:
latency-histogram --nobase --sbinsize 1000 --show
The following user(s) said Thank You: akb1212, Grotius

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

Time to create page: 0.802 seconds
Powered by Kunena Forum