PID setpoint tracking about node-red-contrib-easy-pid-controller HOT 14 CLOSED

It should work. Please test it.

from node-red-contrib-easy-pid-controller.

I am very new in Node Red, I know what I want to do but not how to do it.

I planned to find me in your block the connection points for SV, PV, and out.

But I think they are not directly accessible, can it be?

You could help me generate a generic code and I already tried to adapt it later.

Thank you!

from node-red-contrib-easy-pid-controller.

Check here for template

https://github.com/hj91/node-red-contrib-easy-pid-controller/blob/main/examples/easy-pid-controller.json

from node-red-contrib-easy-pid-controller.

Thank you!! I have been able to write the SV and PV values from the MQTT Explorer, but I am not able to connect my MQTT Solar Power to SV input.

Forgive my awkwardness!

flows.json

from node-red-contrib-easy-pid-controller.

No problem. Replace this node by real pid controller hardware in case things dont work out well as your requirement.

from node-red-contrib-easy-pid-controller.

I have already managed to inject SV and PV with an external variable through MQTT.

Now I would have to scale the variables.

SV and PV from 0-2kW

And the OUT would need to be configured from 0-100%
flows.json

from node-red-contrib-easy-pid-controller.

HI @hj91

Let's see if you can clarify for me what I'm doing wrong.

I'm messing around with your example, and I can't understand why the output VALUE value doesn't increase when PV is lower than SV. I've noticed that it takes the same value as the PV input.

The OUTPUT does increase as expected.

flows.json

from node-red-contrib-easy-pid-controller.

Adjust the values of p, I, d to suite the system.... The values I provided in sample are for theory only.

Let me add that pid tuning is another time consuming exercise one needs to do for their system. And there is no one single magic way to do it in one attempt.

from node-red-contrib-easy-pid-controller.

Yes, I know that the PID issue is complex and an art to tune it, but what is happening is that I set the values I set for P I D, the Value output is always equal to the PV.

from node-red-contrib-easy-pid-controller.

Try adjusting the values and check the response of your system - usually it aims to make sure pv is approx equeal or close to sv.

from node-red-contrib-easy-pid-controller.

Hi @hj91

Indeed, the PV must ultimately be the same or as close as possible to the SV.

But what I am commenting on is although I have tried different ways to tune the PID, the value that enters PV is as if I copied it to msg.payload.Value. It's always the same.

And the normal thing is that if the PV is below the SV, the value of msg.payload.Value should increase so that the PV gets closer to the SV.

In fact, the msg.payload.Output value does integrate and increase its value.

Thanks!!

But I understand that control output of 0-10V or 4-20mA is collected from msg.payload.Value with a range of 0-100%?

from node-red-contrib-easy-pid-controller.

Hi @hj91

I have been reading this post

#2

And now I have clarified myself!! The same thing happened to this colleague as me, please you have to correct the documentation and specify that the OUTPUT is the output and not the VALUE, it gives rise to error for us "non-experts"

What I do find strange is the behavior of OUTPUT, should it be limited between 0-100%, what could I do for this?

The msg.payload.Output will be sent to the Shelly Dimmer (this expects a range of 0-100%) and then in proportion it will act with 0-10v on the regulator where the resistance that heats the water is connected.

from node-red-contrib-easy-pid-controller.

ok, i guess its time rewrite the code

from node-red-contrib-easy-pid-controller.

Thank you! We all wait patiently for her.

from node-red-contrib-easy-pid-controller.