Jump to content

LabVIEW discrete transfer function


Recommended Posts

I’m having trouble with the discrete transfer function implementation for a while now. So I discretized my PID controller with 100 us and Tustin method in MATLAB, and checked the response to a 1 Hz wave in discrete time using Simulink, with the discrete response as attached. Then I tried doing the same with Discrete transfer function VI in FPGA Labview, taking care to factorise the large numerator coefficients so that it respects the input limits of the VI, and then will multiply the coefficient later after the response of the VI. I also made sure the sampling time in the FPGA code is the same as the sampling time of the discrete controller. Despite this the response saturates to its minimum and doesn’t recover. I attach my LabView code and also the response I got (response before multiplying with the large numerator coefficient).
 
I also tried to do this with a simple integrator, and with this case it actually worked. I attach the results with integrator as well.
 
Could someone help please?

simulation response to 1 Hz wave.PNG: Simulation results

discretized transfer function.PNG: Discretized PID

input and output from PID.PNG: Response of PID in Labview

input and output with integrator.PNG: Response of Integrator in Labview

discretetransferfunction.zip

Edited by aldosebastian
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.