Influence of pid tuning to CPU

Hello,
I just did the pid tuning for a machine with glass scales and old velocity ac servo drives with tacho feedback. The Gui is gmoccapy and the latency on this pc is very good, under 20k.
The tuning is very good the machine is perfectly exact now.
But I recognized that typing in the MDI window is very lame, the reaction from my keyboard is very slow now.

I think this really comes from the PID tuning, I did not recognized this behaviour before.

The config was made with pnc config, base period is not mentioned in the ini and my servo period is 1000000.

I read somewhere that old vel drives with a high servo period can cause trouble, should I slow down my servo period or base period ?

Thank you very much !!

REEEN wrote: I think this really comes from the PID tuning, I did not recognized this behaviour before.

The PID component takes the same amount of CPU whether it is tuned or untuned. It runs in the servo-thread and is not especially CPU-intensive.

What do you have running in the base thread? Do you even need a base thread?

Hello Andy,
I don't have anything in my Base thread, so I think I don't need one.

I have several conponents running in the servo thread, a very big one for the tool changer.

About 2500 lines of code.

REEEN wrote: I have several conponents running in the servo thread, a very big one for the tool changer.

Is that one that you wrote yourself?

Realtime components need to run very quickly, typically they do one thing, or nothing, then exit. Then next time they may do a different thing.

If there is _any_ wait loop in your component, then that is bad.

The carousel component is an example of how to wait for a toolchanger without waiting, a state-machine built from a switch statement.
git.linuxcnc.org/gitweb?p=linuxcnc.git;a...96d546b0f9a7a16e4806

Hello Andy,

I don't exactly know what youean with wait loop ?

I also use switch case todo the steps.

At the beginning I often have some if states to encode things or set some variables or else, but most of the code uses case.

The carousel changer is very similar built.
I see there is if !enable return in the first switch. What does the return do, I don't use return.

Thanks

REEEN wrote: I don't exactly know what youean with wait loop ?

A realtime component must never wait for anything, it should exit then look again next invocation.
It sounds like you already understand this.

You might find it useful to look at the thread and function times, see if any component functions are running longer than expected.