Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

cyclic interrupt OB30-PID

Created by: muha_mag at: 8/21/2017 1:16 PM (19 Replies)

Rating (3)

Thanks 3

Result pages:: |; 1 | 2; |

20 Entries

Entries per page: 10 | all

8/21/2017 1:16 PM	Rate (0)
muha_mag Posts: 80 Rating: (1)	Hello, I use the TIA portal and PLC S7-1200, I created a cyclic interrupt OB30, in which PID_compact is the temperature regulator. The problem is that output_PWM will not turn on, but input_PER is less than the setpoint. When I'm on the CPU online and when I start PID then everything works
muha_mag Posts: 80 Rating: (1)
Suggestion To thank Quote Answer

8/21/2017 1:22 PM	Rate (0)
mopS04 Platinum Expert Joined: 3/5/2014 Last visit: 8/5/2022 Posts: 5521 Rating: (1054)	hi muha_mag, how do you see this when you are not online? can you share some Screenshots of this? regards,
	FCK WAR! Be nice!
Suggestion To thank Quote Answer

8/21/2017 1:26 PM	Rate (0)
muha_mag Posts: 80 Rating: (1)	It should turn on the digital output Q0.0 if the current temperature is less than the setpoint. And this outputQ0.0 is not included. And when I go online Q0.0 is not included, only when I start PID then turn on.Q0.0
muha_mag Posts: 80 Rating: (1)
Suggestion To thank Quote Answer

8/21/2017 7:55 PM	Rate (0)
0_Einstein Diamond Expert Joined: 7/7/2010 Last visit: 11/15/2024 Posts: 15402 Rating: (2443)	Are you trying to do this in the simulator? muha_mag Hello, I use the TIA portal and PLC S7-1200, I created a cyclic interrupt OB30, in which PID_compact is the temperature regulator. The problem is that output_PWM will not turn on, but input_PER is less than the setpoint. When I'm on the CPU online and when I start PID then everything works
	science guy
Suggestion To thank Quote Answer

8/22/2017 1:24 PM	Rate (1)
Mach11 Experienced Member Joined: 3/19/2015 Last visit: 7/2/2024 Posts: 90 Rating: (29)	Hi, if you are using PLCSIM for 1200 this will not work because PID simulation is not supported there according to online help (only PLCSIM 1500 can be used with PID). If PID_Compact does not start after download, have a look at parameter Mode. For automatic mode it should be 3, but default configuration is 4 (manual mode with manual value 0.0 so nothing would happen). When CPU changes from Stop to Run then PID_Compact changes to the operating mode that is stored at parameter Mode automatically. You can observe the currently effective operating mode at parameter State. If you want to change the operating mode during operation, use parameter Mode and a rising edge at ModeActivate. Regards

Suggestion To thank Quote Answer
This contribution was helpful to 2 thankful Users 0_Einstein Arasan

8/25/2017 11:43 AM	Rate (0)
muha_mag Posts: 80 Rating: (1)	It does not allow to change the Mode parameter in 3 (printscreen and attachment) Attachment pid.png (256 Downloads)
muha_mag Posts: 80 Rating: (1)
Suggestion To thank Quote Answer

8/25/2017 11:45 AM	Rate (0)
muha_mag Posts: 80 Rating: (1)	Not on the simulator, I tried on the PLC itself
muha_mag Posts: 80 Rating: (1)
Suggestion To thank Quote Answer

8/28/2017 7:27 AM	Rate (0)
Mach11 Experienced Member Joined: 3/19/2015 Last visit: 7/2/2024 Posts: 90 Rating: (29)	Hi muha_mag, "Mode" is an In/Out parameter, so you can't assign constants here. You could - use a move block that writes 3 into "Mode" before the PID call. You also have to change "ModeActivate" from FALSE to TRUE. - write 3 into "Mode" of the offline PID datablock and download it (because "Mode" is Retain, you should do a download and reset via online menu in the toolbar, otherwise it won't become effective). "ModeActivate" is not necessary here, because the controller changes to the value stored in "Mode" each time the CPU changes from STOP to RUN. - use the watchtable to change "Mode" and "ModeActivate" for test purposes. Regards

Suggestion To thank Quote Answer

8/29/2017 7:39 AM	Rate (0)
muha_mag Posts: 80 Rating: (1)	I did it, but again I have the same problem. I noticed when Input_PER (integer) is less than the setpoint then it works. It behaves as if it matches the setpoint and Input_PER, and should compare the setpoint and the Scaleinput
muha_mag Posts: 80 Rating: (1)
Suggestion To thank Quote Answer

8/30/2017 7:18 AM	Rate (0)
Mach11 Experienced Member Joined: 3/19/2015 Last visit: 7/2/2024 Posts: 90 Rating: (29)	You have to assign your process value to one of the two input parameters: - Input: if your process value is already available in REAL format. Set Config.InputPerOn = FALSE then. - Input_PER: if your process value comes from an InputWord of an analog input module. Set Config.InputPerOn = TRUE then. ScaledInput is an output parameter that shows you the process value that is processed by the PID algorithm. If Input is used it's equal to Input, if Input_PER is used it shows the process value after scaling. The scaling function can be configured in configuration. If this is not the problem a screenshot of DB-Editor or ParameterView with activated monitoring (so the online values in CPU are visible) might help us to understand this issue.
	Last edited by: Mach11 at: 8/30/2017 7:24:24 AM
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on