Upgraded to 2.7.13 -- W T F --

I will try to change SERVO_PERIOD and report back asap.

Sorry, that made it even worse as did 300000. With 200000 I can get into Axis but no other setting it fails directly.
With 200000 I can jog slow via keyboard but shift+arrow = hell is loose as it is with MPG



So there is something odd with servo thread speed, is this LCNC 13 issue or is OS related?


With 2.7.12 I could get rocket speed with MPG to stall my motors but that is nothing I want at all but I could
Now I barely touch the wheel and all hell is loose.


ps. the realtime delay on task 0 issue is also new with 2.7.13 = yes I know my PC is on the boarder

You seem to have lost some zeros.

Try 1,000,000 (or 1.000.000 if that's how you write it in your country)

I´m lost

So 2000000 (2 million) is not the correct way to express this figure as set in INI now that has been working OK.

Should i write 2.000.000 and change it to 1.000.000 instead of 1000000?

In your last message you said that neither 100000 or 300000 worked properly, but I wouldn't expect them to.

With a P-Gain of 1000 I would expect a servo thread period of 1000000, but I wrote it as 1,000,000 to make it clear how many zeros there should be.

The INI file will not work with any form of thousands separator.

OK, I follow what you say.

So is it time to play with new numbers on P = 1000 on each axis and SERVO_PERIOD ?

tecno wrote: OK, I follow what you say.

So is it time to play with new numbers on P = 1000 on each axis and SERVO_PERIOD ?

1000000 or 1.000.000 without dots, that is one million,
On your reply you used one hundred thousand and three hundred thousand, that will not work properly.

tommylight wrote:

tecno wrote: OK, I follow what you say.

So is it time to play with new numbers on P = 1000 on each axis and SERVO_PERIOD ?

1000000 or 1.000.000 without dots, that is one million,
On your reply you used one hundred thousand and three hundred thousand, that will not work properly.

That was a typo in my reply

Here a new test this morning

First part is with 1000000 setting and from line 100 the setting is 2000000



this picture with 2000000 and only keyboard jogging and it fails after a while.

This is all quite weird as the differences between 2.7.12 and 2.7.13 are not that significant and not related to Ethernet communications at all. I think something else must have changed when you updated, perhaps specific to your PC

Can you run a latency test on you PC to make sure something bad has not happened to real time...

something like

latency-histogram --nobase

and run it for 1/2 hour or so then use latency-histograms screenshot option to get the image and post it here

Also if you have an Intel MAC you need to set irq coalescing off (if you did not automate this setting you would lose it when you re-booted)