noob

Simple PID explanation

8 posts in this topic

I am using Cx-programmer version 9.4 and i was wondering if anyone could clarify how to use the PIDAT (191). Been searching online but im not really sure how to work it. im not sure how to implement all the parameters needed to use this function so if anyone can help me out that would be awesome. :helpme:

Share this post


Link to post
Share on other sites

First try reading manual!! Then come back with your questions! Note that PIDAT is the same as PID with the added Auto Tuning capability.

OMRON PID PIDAT.pdf

Share this post


Link to post
Share on other sites
Bits N Bytes is correct.... RTFM first.... and i think there is a PIDAT FB in the download section. as for the selection of the P I and D parameters and the T constant.. well i suggest getting an understanding of PID first... the one thing that Omron is a little different is that P is Proportional Band - in other PLCs P is Gain... the Proportional Band is the Inverse of Proportional Gain ie PB = 100/PG and PG=100/PB google PID and there is a wealth of info... if you are stuck at trying to determine a base P I D value then look at a Omron temp controller and look at the default settings for P I and D....

Share this post


Link to post
Share on other sites

i cannot find the "PIDAT" function block example in the download section.

Please share link.

thanks.

Share this post


Link to post
Share on other sites

Chou, there was issues with a recent site update.  I have added it back to the post for you.

Share this post


Link to post
Share on other sites

Dear Michael,

May i know why the PID is not function when i set the SETPOINT value to negative ? (let say -55)

thanks.

Chou

Share this post


Link to post
Share on other sites

Sorry arsenen8, I just saw this post.  Somehow I missed it.  The function block is designed to work with a positive feedback value (an analog input for instance) and is therefore looking for positive numbers.  If you treat -55 as an unsigned integer, it is 65481.  This number is likely larger than the number of bits that you have selected for your feedback, so it stops working.  As a fix to your issue, you could always apply an offset to your input and to your setpoint to compensate.  For instance, if your values range from -500 to 500, then you could add 500 to your feedback and then set your setpoint from 0 to 1000.

 

 

Share this post


Link to post
Share on other sites

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