View Single Post
  #1   Spotlight this post!  
Unread 09-04-2016, 20:21
plnyyanks's Avatar
plnyyanks plnyyanks is offline
Data wins arguments.
AKA: Phil Lopreiato
FRC #1124 (The ÜberBots), FRC #2900 (The Mighty Penguins)
Team Role: College Student
 
Join Date: Apr 2010
Rookie Year: 2010
Location: NYC/Washington, DC
Posts: 1,114
plnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond repute
Re: PIDController + Latency - related issues

Quote:
Originally Posted by Alan Anderson View Post
The built-in PID in LabVIEW is not like most other implementations. It uses the academic form, with a single overall gain and a pair of times for the Integral and Derivative parameters. There is no feedforward provided.
For those curious about how the LV PID constants work, I'll quote a previous post of mine explaining it...

Quote:
Originally Posted by plnyyanks View Post
If you take a look at the implementation, it explains how the time constants relate to the traditional ones.

Here's the overall function:


The P component (Kc * error):


I [(Kc / Ti)integral(e)]:


D (Kc * Td * d(error)/dt ):




So, if you take a simple version of the formula like below...

Then:
Kp = Kc
Ki = Kc / Ti
Kd = Kc * Td
__________________
Phil Lopreiato - "It's a hardware problem"
Team 1124 (2010 - 2013), Team 1418 (2014), Team 2900 (2016)
FRC Notebook The Blue Alliance for Android
Reply With Quote