LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Ramp setpoint profile in PID controller suddenly jumped to later (wrong) steps

Solved!
Go to solution

This is a heating test labview program.

The power source heats the sample and is controlled by a PID controller per the desired setpoint profile. 

The setpoint profile is a ramp and hold profile: 5C increase per step in 5 mins, then hold the temperature for 15 mins, until eventually the temperature goes to 320 C. 

However, when the setpoint temperature was at the step where the sample was held at 90 degree C, the set point temperature suddenly went to 190 C, then continued (see below). Has anyone met a similar problem before? 

 

Erene123_0-1621597901825.png

 

 

0 Kudos
Message 1 of 14
(3,191 Views)

Hi Erene,

 


@Erene123 wrote:

However, when the setpoint temperature was at the step where the sample was held at 90 degree C, the set point temperature suddenly went to 190 C, then continued (see below). Has anyone met a similar problem before? 


I don't think so - most probably the problem is in your VI or in your profile definition…

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 2 of 14
(3,184 Views)

Hi GerdW, 

   I have confirmed the defined profile is correct. One column is the elapsed time, the other column is the desired temperature. I wonder what could be the problem in the VI. I thought the VI was standard by NI. 

0 Kudos
Message 3 of 14
(3,178 Views)

Hi Erene,

 


@Erene123 wrote:

I have confirmed the defined profile is correct. One column is the elapsed time, the other column is the desired temperature. I wonder what could be the problem in the VI. I thought the VI was standard by NI. 


The problem probably is in your VI, where you call the RampProfile function.

As you did not attach your VI we cannot debug it!

 

When the profile output (your setpoint) changes so much, then the profile input (most probably time) has also changed that much…

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 4 of 14
(3,171 Views)

Hi GerdW,

   Please see attached the VI. Thank you.

0 Kudos
Message 5 of 14
(3,148 Views)
Solution
Accepted by topic author Erene123

I assume you have to work on the values in your setpoint profile control from your VI:

 

JensG69_0-1621605649786.png

 

Regards, Jens

Kudos are welcome...
Message 6 of 14
(3,125 Views)

Hi Jens,

 

I just verified the profile again. I still could not trace those values in my profile that have caused the sudden jump to 190 degrees. Can you please suggest a way to resolve it? 

 

Also, I have created a new setpoint profile in a different VI. Can you please help in checking if this issue happens here as well? 

0 Kudos
Message 7 of 14
(3,109 Views)

Hi Ravi,

 

now the setpoint array is empty…

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 8 of 14
(3,096 Views)

Sorry about the trouble.

Please find the new file below.

It has the same jump in temperature problem.

0 Kudos
Message 9 of 14
(3,092 Views)

Still exactly the same, and I just copied your setpoint profile to a new VI and connected to an XY-graph for visualization:

JensG69_0-1621610323366.png

Regards, Jens

Kudos are welcome...
Message 10 of 14
(3,086 Views)