motor-0-position error beim Abbremsen aus 4-7,5 m/min

More
27 Apr 2025 20:06 #327182 by PCW
Actually, having a small amount of FF2 improves the following error
(the actual amount should be the time between reading the position and updating the output
though 0.005 seems large)

It may be necessary to take a look at the following error to diagnose the issue
(this will also allow for tuning of the FF2 value)

Increasing the following error limits should not hurt either
The following user(s) said Thank You: Muftijaja

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

More
27 Apr 2025 21:02 #327185 by Muftijaja
Hi tommylight, i just followed the advice from PCW in an earlier posting: "...and change all joint PID "P" terms to 666"
OK, i will do that and also correct the stepgen max velocityto 160.
FF2 has been also an advive from PCW - I have Servos with integrated drivers, no feedback to the MEsa card.
"You might try plotting the following error and perhaps tuning by adding a little
FF2 (say .0003 to start) to the PID loop (using the calibrate menu so you can do this live) "
I'm just doing what I've been said to.
Thanks for your hints!
Greets Hanno

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

More
27 Apr 2025 21:09 #327187 by Muftijaja
Hi PCW,
well I have had FF2 at 0,003 when the errors began and just tried 0,005, then 0,008, just not knowing what it does. I point out, that my servos (OMC 400W integrated drivers) do not send any feedback to the Mesa card, they have closed Loop Drivers/Encoders.
I can see the following error in the tuning software from OMC, but the numbers are not in any correlation to numbers in LCNC and INI file.
Is it better to leave FF2 at 0 or less than 0,003?
INcreasing FERROR = 0.1 or MIN_FERROR = 0.01? What could help more?

Thanks for your advice!
Greets, Hanno

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

More
27 Apr 2025 21:10 #327188 by rodw
I think you may have moved past this but the only network latency issue I can think of is that energy efficient Ethernet is enabled. This can cause intermittent latency spikes you are experiencing. The method to fix is different between Intel and Realtek device but I do mention them here
docs.google.com/document/d/1jeV_4VKzVmOI...diY/edit?usp=sharing 
The following user(s) said Thank You: Muftijaja

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

  • tommylight
  • tommylight's Avatar
  • Away
  • Moderator
  • Moderator
More
27 Apr 2025 21:10 #327189 by tommylight

Hi tommylight, i just followed the advice from PCW in an earlier posting: "...and change all joint PID "P" terms to 666"

That was correct back then when you had the servo period set at 1.5 million, it is not correct when you changed the period to 2 million.
1 million = P 1000
2 million = P 500
0.5 million = P 2000
etc.
And sorry, i missed the part with FF2.
The following user(s) said Thank You: Muftijaja

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

More
27 Apr 2025 21:12 #327190 by PCW
Also setting FF2 should be done with halscope.
The following user(s) said Thank You: Muftijaja

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

More
27 Apr 2025 21:45 #327193 by Muftijaja
Hi rodw,
thank you, I have the DKMS r8168 driver installed weeks ago. I try this tomorrow:
Optional kernel settings (install using grub-customizer as per
isolcpus setting)
r8168.aspm=0 r8168.eee_enable=0 pcie_aspm=off loglevel=3
I did not test them individually to see which helped but I suspect that disabling the "Energy Efficient Ethernet" mode might be a good culprit.
Ethernet efficiency mode has to be switched off in BIOS, right? OR is it in the network settings in Linux/Debian Network manager?

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

Time to create page: 0.086 seconds
Powered by Kunena Forum