The auto-tune look how long it takes to heat the system up to the set-point and how fast it cools down. It then does this a few time to get an average image of the behavior. After it’s done (can take a day or 30 min depends on the system) you’ll have an message in the log. Just enter the values you get from there as if you would not use auto-tune and restart.
You have to create one entry for ever heating system, else you would control all system as one. If you do that u can auto-tune as many system as you can with your server. (This program can take a lot of ram, if your interval is small.)
How I figure it out which K’s values belongs to which heating system?
What do you mean? Please consider reading the help on github, for a deeper understanding of pid controllers and heatingsystems.
I’ve studied this for 2 years and still don’t really understand everything. I can just recommend not using the auto-tune for now, as it’s not really well integrated in the program. Get yourself a general idea how the p, i and d works and what the individually do. Just enter some ziglers values and look how it perform, then adjust it.
I working on a opensource project to make heating system with industrial standards available for everyone and easy to use. (image a nest, but it’s just software). You can wait for that or even help me. Sadly I have a ton of work right now, so I can’t tell when I’ll finish an alpha.
You can write down your experience of using a pid controller for the first time. That could help me so I get an idea of how people look at this. (not how it was to install it and get it running, just configuration and performance)