Jump to content

Recommended Posts

For some time I get complaints from my customers that my PID controlled heater loops overshoot a lot at the beginning of the operation, and then functions OK. Talking about V570.

PID is connected to a physical output driving SSR thru a PWM FB. At the begining of the heating cycle PID Control Value is 100% and PWM output bit is permanently ON, of course. But later on, as the temperature rises, CV naturally starts to fall (99%, 98%, ..., 57%, ...) but PWM output bit is still permanently holding ON state, without any blinking, so my SSR is fully open, providing 100% average power to the hater, overshooting the setpoint a lot. Then, when CV becomes 0, output bit is finnaly reset, and from that moment everything is working fine - the temperature is falling, CV is rising, PWM is producing modulated pulses and the temperature is finaly under control.

Also, I searched for something else that could keep output bit clamped to ON - absolutely nothing, because it occurs only two times in my program - in PWM block, and in a plain different net, driving the physical output. Also, PWM scan FB is placed in the Main Routine, so it executes all the time.

This is why I added a few ladder nets that are forcing CV to zero for 0.1 second every 10 seconds during initial heating of the system, and that solves the problem, i.e. PWM output bit is pulsing immediately after CV decreases below 100%, so the regulation is fine all the time, without noticable overshoot.

The question is why such a strange behaviour?

(Of course, I use VisiLogic 9.3.0 with the latest OS 3.4.0)

Link to comment
Share on other sites

  • 2 weeks later...

We were able to simulate the problem here. Our R&D repaired it. We expect to issue the improvement with the comming very soon VisiLogic V9.3.1 and comming with it OS.

Meantime - very simple temporary workaround - set PID output range to 998 (with 999 the problem still occure). I guess 0.2% of the power will not make any visible change in the system.

Anyway - very soon te fix will be realized.

Link to comment
Share on other sites

We were able to simulate the problem here. Our R&D repaired it. We expect to issue the improvement with the comming very soon VisiLogic V9.3.1 and comming with it OS.

Meantime - very simple temporary workaround - set PID output range to 998 (with 999 the problem still occure). I guess 0.2% of the power will not make any visible change in the system.

Anyway - very soon te fix will be realized.

Emil,

It can't come soon enough. I am just finishing up a couple multizone temperature control systems that will exhibit the same issue. Would be nice not to have to submit the program with the above patch.

Damian

Link to comment
Share on other sites

  • 5 months later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

This site uses cookies. By clicking I accept, you agree to their use.